I'm writing for my brother who was running Karmic on a Microtel desktop.He'd been having trouble with blank cds (data cds and dvds didn't cause this problem) crashing his box so he uninstalled and then installed udev package.Now when he tries to boot the box goes into a memory test and then reboots into the memory test over and over. He tried to check the installed kernels to choose one that might boot but there are none listed (he pressed "esc" to see the list-it's empty).He tried booting from a live cd and that won't work either. The cd drive spins but nothing else.
I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Code:
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
I have been trying plop floppy to boot a bootable cdrom from a mobile USB cdrom reader, but the usb cdrom are not recognized.I was thinking that with grub or grub2 or syslinux that would be possible, no ?
In Ubuntu 910 on my Asus EEE-PC1005HA, I notice that during boot, when the screen is dark between the plain Ubuntu logo and the animated purple screen, there is a brief message:udev[488] cannot read file (rest of message goes by too fast for me)This doesn't seem to hurt anything. My system has been working just fine for a long time. I don't know how long the message has been there. Perhaps it merely lengthens boot time? Should I care? If I should care, where might the message be logged (so that I don't have to photograph the screen)?
This morning I had the courage to run an apt-get autoremove which took some 275 packages off my hard drive, and now I am experiencing a delay of about 40 seconds at boot, after grub, before the plymouth splash appears. The cursor blinks on a black screen while the hard drive churns away. Finally two error messages appear too quickly to be read, and then the bootsplash kicks in. I can find the instant in the dmesg where the delay happens, but can't locate the cause. Here's what my dmesg looks like:
[Code]....
The laptop is an Acer Timeline X 3820TG, with the dual GPU "switchable graphics." These dual graphics cards have given me enough trouble in the past that I wouldn't be surprised if they were the problem. But the hard drive action sounds like a 'fsck,' and seems to be contemporaneous with the dmesg notice that the root partition is mounted.
Incidentally, my boot wasn't all that fast before; I would not be surprised if this delay was preexisting, but used to happen after the plymouth boot screen was already on screen. Still, if I can get rid of this one ugly delay, I can have a fast (c. 10 secs) boot time.
So, I have an old laptop that used to have windows/ubuntu until the drive got fubarred (no physical damage). I shoved the laptop as side as I didn't use it much anymore (it's an old, loud 2.4GHz desktop p4 in a dell--mostly toshiba--laptop. pcmcia atheros based wifi card and an ATI m6 graphics card. Laptop was new back in 2002-03 maybe).The Cdrom drive had died a while back, and it's not worth buying a replacement. The bios doesn't support boot to USB. What are my options for getting Ubuntu on there (9.10 preferably)? The drive has been formatted already, so there is nothing to boot into right now.
I can pull the drive and hook it up to my desktop (windows 7 machine only right now) via USB, and partition it from there, but I'm not sure how to get the installer on there. The MBR of the laptop drive will also have to be rewritten. Is there a way I can create a dos partition, load it with files, and start a linux install that way (maybe with grub4dos or something)?Or can I somehow boot into an ISO image on a partition?The only other thought I have is creating a floppy disk that will allow a network boot, but I haven't looked into that. I basically just want something to bring with on vacation that I can get online with. Browsing from the phone leaves a little bit to be desired.
During the boot process the machine (Fujitsu Celsius M470) hangs about 4 min at udev:loading drivers. After that it continues and I can work with the OpenSuse 11.2 system without problems.I activated the debug log in /etc/udev/udev.confthen I see that it is doing a lot in that time, at the end I see the message:udevadm settle timeout queue contains: a long list of pci/usb entries (no entries in any log for this)
in the logfile I find:udevd-work[1071]: '/sbin/modprobe' (stderr) 'FATAL: Error inserting ipmi_si (/lib/modules/2.6.31.12-0.1-desktop/kernel/drivers/char/ipmi/ipmi_si.ko): No such device'there is no ipmi. how can I deactivate the loading of this module?
udevd-work[412]: '/sbin/modprobe' (stderr) 'FATAL: Module input:b0019v0000p0001e0000_e0,1,k74,ramlsfw not found.' Mar 17 11:35:36 mira udevd-work[418]: '/sbin/modprobe' (stderr) 'FATAL: Module
I am trying to make gentoo boot faster and in my searching I came across this article http://lwn.net/Articles/299483/. One of the things they did was revert to a "persistent, old-school /dev directory so that boot doesn't depend on udev". I would like to know how to do this, but when I searched for disabling udev all the forums say that its a bad idea. All I want to know is how to make a static /dev directory.
I've been having problems with start_udev on my machine post kernel 2.6.18-162 on my CentOS machine. A previous install would work on the old kernelut not the newer ones. I recently did a completely fresh install of CentOS 5.5o see if maybe there was a orruption in my install when it upgraded,t I still have the problem of udev hanging on startup.Using the rescue option on the disk, I've managed to track the problem down to the 50-udev.rules file. Through trial and error, I moved all the .rules files out of the rules.d directory, and added them back one at a time to see which one(s) caused the system to hang, and which ones it carried on booting as normal with. The only one that causes it to hang is the 50-udev.rules.
From what I can tell, this rules file is responsible for letting udev check various pieces of hardware. I think that it is failing whent runs modprobe on a pci device address.Only problem is I don't understand the rules file syntax, so I don't know if I can simply comment out or change a line in this file to skip the device that its looking for.Can anybody help me track down the specific device/line that is doing this?(I've kept the file out of the folder for now and my system appears to continue operating, but I get the occasional problem that for all I know could be due to udev not having a complete start up).
I have done a fresh text-only installation of Fedora 10 on a Dell Dimension E521 for the purpose of setting up a server. After installation I ran yum update to bring the system up to date. After the update, I rebooted the computer, but the boot process froze. I recycled power and pressed "I" after the Dell BIOS screen and the GRUB bootloader appeared. I selected the most current version, edited the kernel line by deleting "rhgb quiet" and replacing it with "3." After making this change, I continued with the boot and the computer stopped at "Starting udev:" I have two fedora 10 revisions showing in the GRUB bootloader, the original installation and the update after running yum.
I repeatedly tried rebooting both versions and, after about 30 attempts, the computer finished booting and got me to the command prompt. Reading through the forums indicated there might be some issue with my nVidia GeForce 6150 onboard video and fedora 10. So, when I got to the command prompt, I followed the instructions in the forums [URL] to load the rpmfusion drivers. This appeared to be successful and when I looked at /etc/X11/xorg.conf it appeared to be correct for the new nVidia drivers. After loading these new drivers I tried rebooting. Unfortunately, I have been trying now over and over to get back to the command prompt, but simply can't get past "Starting udev."
i'm heaving the following message at boot time: "Starting udev: udevd[114]: unknown key 'DEVTYPE' in /etc/udev/rules.d/70-cups-libusb.rules:6", i guess it's something about usb printing support but i am not sure, and i don't know how to fix it, does any of you guys know what this exactly means and how to fix it
I'm trying to configure gpsd 2.96 to start automatically from udev rule on a Slack 13.37 box.1. I've compiled and installed gpsd from sources and made sure it starts manually.2. I've copied the /lib/udev/gpsd.hotplug and /lib/udev/gpsd.hotplug.wrapper scripts in their places from the source tree and made them executable.3. I've copied the gpsd.rules file from sources into /etc/udev/rules.d4. I renamed it 99-persistent-gpsd.rules to run late in the bootup process.5. I've copied the /etc/default/gpsd file from sources and made sure it has the right settings inside.
Now, for the results. If I plug the gps usb dongle in while the system runs, it starts gpsd if it is not started, and it connects to it just as it should. But if I start the system with the dongle in, gpsd doesn't get started during boot. I can't find any relevant message in /var/log/syslog or /var/log/messages for boot time. There is stuff there from when I plug the dongle in while the system is running though. It's like udev ignores the rules for it at boot time.Is there something in the Slackware boot scripts that would prevent running those scriptssd.hotplug.wrapper which in turn runs /lib/udev/gpsd.hotplug which is a Python script)?Here is the contents of 99-persistent-gpsd.rules (ignore the comments referring to Debian, it was meant for a Debian box). My usb gps adapter is the first one - the Prolific chipset one:
I have just installed slack-13.1 on an acer aspire one netbook from a usb stick by booting the install kernel with noudev. I was able to do a complete install including lilo but upon rebooting my boot hangs when encountering my webcam.I see enough info to note the id as 0c45:62c0. This is a microdia webcam which I may be able to do something about later but in the first instance I'd like to be able to boot my system. The bios is very basic and there is no way to disable devices.
Have just installed 5.4 64 bit on an AMD64 x2 system with 4 GB ram running ESXi4.Text based install went fine, but on reboot starting up it gets as far as 'Starting udev' and just hangs. Checking the performance in ESXi it appears to be using 100% cpu.I have left it for half an hour and it does not progress and the only thing to do is to power cycle the VM.I have searched and found a few suggestions for kernel parameters but they did not make any difference. I can't even get in to a command line as it doesn't boot up far enough.I have reinstalled it several times and also checked the MD5 of the downloaded file and all appears Ok.
I just performed an update thru the Update Manager, & on re-boot got this message: ( Ubuntu 10.04.1 LTS, kernel 2.6.32-24-386 ) udevadm trigger is not permitted while udev is unconfigured. Gave up waiting for root device. Common problems :
- Boot args ( cat /proc/cmdline ) - Check root delay= ( did the system wait long enough? ) - Check root= ( did the system wait for the right device? ) - missing modules ( cat /proc/modules; ls /dev )
ALERT! /dev/disk/by-uuid/df0200e3-e6e9-439a-922f-100d92af0c58 does not exist. Dropping to a shell!. BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built in shell (ash) (initramfs)_ Info: I can boot into older version: Ubuntu 10.04.1 LTS, kernel 2.6.32-23-386. The Update Manager does not seem to want to show any updates that are available.
I upgraded to the last ubuntu last week and since I get the error: "udevadm trigger is not permitted while udev is unconfigured."I followed different posts on the forums but none helped: [URL]I did the sequence:
"1. Boot liveCD 2. "sudo fdisk -l" to find your boot disk, in my case it is /dev/sda5. 3. "sudo mkdir /media/newroot"
My computer have Windows XP installed and now I want to install suse 9.0. I insert the boot disk (disk 1) and reboot my machine.Then on the boot option window, I select 'installation'. Then comes the error: cannot find SUSE installation CD. Activating Manual.... Then 'English'-->'English(US)'-->'Installation'. Then comes another error: Cannot mount CD-ROM.
I have successfully setup a FOG server to image my Windows clients, so I have tftp, pxe and anything else related to booting to a pxe server setup and rocking. What I'm trying to do now, is use the CentOS net install files to setup CentOS on an old server with no USB boot option, and a broken scsi cdrom drive (it's a Dell PowerEdge 2400, with a single PIII 733 and 1.25GB ram).
Using the FOG Projects gparted wiki entry (adding gparted to the pxe boot menu) I was actually successfully able to pull the net install files over to the PE, and install CentOS 5.5 via local ftp server. At first it kept erroring out (I kept picking and choosing individual packages from the package groups), so I thought it may be an issue with the GUI install (the python script kept spitting back errors forcing a reboot). In any case, I finally got through the GUI install, but now I need / want to know how to force a text mode install.
[Code]....
the bolded "append" line is where I thought I could force the text mode install script, but that didn't work. The vmlinuz and initrd.img files were both pulled form the net install iso, NOT the livecd. Would that have made a difference? If not, what / where / how should I force the text mode install script?
I'm hoping someone knows about this one... I'm running the latest CentOS 5.4 with kernel 2.6.18-164.15.1.el5 (x86_64).When I boot the machine, it gets to the udev starting bit, hangs for like 5 minutes, then prints a message "Failed, will continue in the background." Then it boots OK after that.I tried booting again with the kernel option (from grub) "udevdebug", and what I saw when it tried again was a million messages saying it was waiting for "/sbin/pam_console_apply" to return, but I guess it wasn't returning... ;) Again, after 5 minutes, it gave up and finished booting.Now, this host is an LDAP client.
I figured that may have something to do with it as it is likely that pam_console_apply tries to make an LDAP lookup, which is wrong, because networking hasn't even started yet. If I disable LDAP (by removing ldap lookups in nsswitch.conf), I get no pam_console_apply errors from udev and it boots quickly. But that's a bummer, I need LDAP on this box, and I don't want my boot time to be 7-8 minutes. ;)Presumably before, when LDAP was enabled and it waited 5 minutes and then notified me that it will "continue in the background", that it was eventually successful after networking started. LDAP otherwise works fine on this box, just like all the other servers we have.This is new behavior, I've not seen it with CentOS 5.3 and below. Has anyone seen this? Any hints on what I can do to avoid it? It seems like a pam bug or something, but I don't know for sure.
Fedora 12 randomly crashes after a fresh install.Everything is left at its default during the installation except I install KDE and not Gnome.When I try to boot I hit esc at the splash screen to see where it hangs, but it never hangs at the same spot twice. Sometimes it hangs and sometimes it restarts. Its crashed everywhere from starting udev to the login screen.
I've been using kubuntu for the past year because I have the same problem with F10 and F11. I dual boot with Windows 7 for games.
System specs: Motherboard: MSI P45 Platinum Processor: Intel Core 2 Duo E8500 Video Card: Radeon HD4850 Memory: 4GB (2x2GB) Patriot HDD: Main: 250GB SATA Western Digital code....
I have been trying to get my Toshiba L300 to dual-boot Fedora 12 and Vista, which it came pre-installed with. I shrunk my existing partitions to create some unallocated space, then installed F12 on it from the 64bit Live CD. Everything seemed to go fine, and I was able to boot into Fedora as normal. However if I tried to boot into Vista, I would get a message to the effect of:BOOTMGR is missingRather annoyed but undeterred, I decided to cross that bridge when I came to it, and went back into Fedora to start configuring it properly. I installed the latest version of WINE, and the mp3 support, then shut down. When I tried to boot into Fedora later on, everything started as normal, then it hung on a black terminal style screen, where I can type and press return for a new line, but nothing actually happens. Pressing ctrl-alt-del restarts the computer however.
To get out of this no-working-OS-limbo, I had to break out my Vista recovery console and run fixboot. This has got rid of the bootloader and now Windows starts up fine, but obviously this does not solve the problem of not being able to boot Vista while Fedora is also installed, and not being able to run Fedora presumably (but not for certain) after I have installed WINE
I went through so many post but I haven't found the proper answer yet hope you have an Idea1. Grub2 saves only Linux OS as last selected no Windows OS2.It is possible to boot into a cdrom (drive)?
I have an alienware m17x laptop with 2 hardrives, on primary is win7 and on secondary is ubuntu 9.10. The problem I have is if I boot (using Grub) into linux it crashes before the ubuntu logo pops up and locks up completely, needing a hard reset. If I boot linux again, all is fine. I can't copy the text that comes up when it crashes, is this logged anywhere so that I can post it? The same thing kind of happens in win7, on first boot (via Grub) I get the windows logo for about a second then BSOD and it reboots (so fast I can't see the error). If i boot again into win7 it boots fine.
I am on dual boot alongside windows 7 (which works fine). However, when I try to boot into linux I get a few minutes of the ubuntu icon. (sorry for lack of technical terminology). After a few minutes i get terminal sort of screen saying: fsck from util-linux-ng- 2.16 /dev/sda5: clean, 165561/625856 files, 984444/2502115 blocks I have attempted to boot from the live cd I installed from and there is no system response from it. How to either uninstall linux from here or just to get it to boot.
When booting Fedora 11, my system hangs for a very long time on starting udev. Sometimes I get an I/O error. However, my hardware is fine. I do eventually get in to the system.
