OpenSUSE Install :: During Boot Hangs About 4 Min At Udev?
Mar 17, 2010
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: '/sbin/modprobe' (stderr) 'FATAL: Error inserting ipmi_si (/lib/modules/18.104.22.168-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: '/sbin/modprobe' (stderr) 'FATAL: Module input:b0019v0000p0001e0000_e0,1,k74,ramlsfw not found.'
Mar 17 11:35:36 mira udevd-work: '/sbin/modprobe' (stderr) 'FATAL: Module
I want to try the new 11.1. When I start the installation (x86_64 DVD), the startup is hanging. The last message is "Starting udev...". Keyboard is completely frozen, only reset button is working. Mobo is an Intel DG965WH with 4GB RAM and ATI Graphic card (ASUS1950pro). My opensuse 11.0 runs without any problems.
where the install hangs at the "Starting udev..." and nothing seems to be able to get the system to run the install. I have tried starting the install with edd=off, apci=off, noapic, apci=ht, and a variety of other options listed on posts. I have tried versions 11.0, 11.1, 11.2, and 10.2 with no success with any of these. With 10.2 it does not hard lock the system so I am able to Alt-F4 to see some debugging info and I am getting the following "it trap divide error rip:2b6b0c281123 rsp:7fff9e95fdf0 error 0". With any of the version 11 installs the system completely hard locks with "Starting udev..." I have verified the installation media of all distros, re-downloaded the iso files, and burned using the slowest setting all with the same results. I have gone into the bios of my machine and disabled the APCIMCFG, High Precision Event Timer, SW Mem Hole Remap, and UnGanged Enabled. I have also tried to enable this IOMMU option for the memory but still nothing. I have tried using just one of the SATA drives by unplugging the other 5 and same results. I did notice that from time to time I see something from squashfs.ko saying "Clocksource tsc unstable"
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.
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.
I've looked around the threads and can't find this exact problem. I'm on a Compaq Presario F700 running openSUSE 11.3. During boot it hangs in three different places, all of which I can clear up by clicking the mouse buttons or moving my finger on the pad.
The first place it hangs is after: doing fast boot ^[^[^[creating device nodes with udev
The second place is INIT version 2.88 booting
The third place is copying static /dev content.
Like I said, I can get through all three and everything else works great, I just hate having to watch my machine boot to catch these.
I've installed OpenSUSE 11.2 Gnome Live from a USB stick. The installation worked well, but after the first reboot, the graphical loader just hangs with the progress bar having moved only a couple of pixels. Only way to recover is to power-off - CTRL+ALT+DEL does nothing.
When I press 'Esc' on boot, to display the boot messages, I see the boot hangs at the following point:
"Loading drivers, configuring devices:"
trying again, this time adding the boot option "acpi=off" as recommended in another thread, gets me a little further, but the boot now fails at the following point:
"Set System Time to the current Hardware Clock"
Finally, booting in Failsafe mode gets all the way to a text mode login, but this is hardly a long-term work-around.
Has anyone got openSUSE 11.2 working on an HP Mini 110, or at least seen and solved this problem on another system? I can confirm openSUSE 11.2 works fine on my old Acer Aspire One A150, so I assume this is a specific issue on the HP.
Tried to install Suse 11.4 on Core 2 Duo 3.16 GHz 4 GB RAM PC alongside Win XP.Installation progress was fine. I rebooted. The gecko appeared and the process bar kept going just about 1/10, then froze. I saw that it froze at the Loading AppArmor Mounting security fs on /sys/kernel/security.I tried safe-mode and it also froze at the same step. tried installing suse 11.3 -- and ended up with the same problem.
I don't know why, but when i first boot openSUSE at the morning in my Aspire it hangs over and over again. I don't know why is this, but the gecko appear, the white bar appear, and moves 1cm, and then, puff no more blinking from the hard drive. Then i force te reboot, over and over until works.The message is: acerhdf: no Aspire One hardware foundWhen i first installed the mini with openSUSE it works perfect for a week, and then start this problem.I have tried with different kernel flavors (like desktop) and still nothing.
I just upgraded my OpenSuSE 11.2 system to 11.3 and have experienced the following problem:
My hard drive was encrypted beforehand, and after the upgrade(which went smoothly) will no longer decrypt. I type in my passphrase at the prompt, press enter and the start up process never resumes. I am able to access the filesystem from the Rescue System option in the install disk. What's strange is that this worked smoothly on another laptop of mine.
I have an old laptop (asus M6 ca. 6 year old) with dual boot linux windows. Untill Saturday linux=suse 11.0, Saturday I have made an upgrade to opensuse11.4. I have boot up/down many times almot everything was working properly except the battery status ... I have thought .. "I'll think about it later".
Then out of the blue on sunday my laptop does not boot anymore, the boot hangs. I then have realized taht the failsafe boot was working properly.... ok I have remembered the wrong battery signal and tried the normal boot + acpi=off .. and .. it boots!
OK, the acpi is the problem. I have never made an update of my BIOS (this means it is now old), but I do not really want to update it now. with suse 11.0 the acpi was working properly, I have never have touched the acpi boot option and I had all acpi functionality working (battery, suspend .. etc)
how to let acpi work (at least for the main features .. batetry, fan speed, HT ... etc)?
It can be that the old kernel boot was using some "specific flags", (an installation is cleverer than an upgrade ..?!?!) but unfortunatelly it looks to me that nothing has remained from the old installation .. so I do not know ...
I have updated to the new kernel that was available from 11.2 and now I cant use my system.
It boots up into kde 4.3.5 and then right when its just finishing it freezes everytime and I hear that last tone of the bootup sound ring continually until I force a shutdown. Anyone else have this issue with the update?
I installed 11.3 first as update from 11.2. The later described error occured.My first approach was to install 11.3 as full install from scratch, the following error did not disappear.System boots fine when doing boot option "confirm" and answer "no" to haldaemon service. Subsequently no usb devices are recognized by the system.
If i do not skip the haldaemon, either in normal as in failsafe mode,haldaemon reports a "NULL Pointer dereference", which is repeated very often.The system finally stops booting, the screen is full with the following three lines, which seemed to be repeated for about a minute.
I created an OpenSUSE 11.4 PV guest on XenServer 5.6, and about half the time, it fails to finish booting. it starts all the services, and fails immediately before it would display the login prompt. I've spent hours googling for this problem, and can't find any reference to it anywhere, meaning that I may be the first to experience it.
has anyone else done OpenSUSE 11.4 on XenServer 5.6 and had this problem? were you able to resolve it, and how?
Boot from DVD 11.4 586 32 bit is fine. Loads up and offers me install, boot from HD, check media, firmware etc. Select text output, no acpi, check media. Linux kernel loads, then black screen showing progress in white text.
At "Starting udev..." process hangs. Eventually (several minutes later) message is returned about "worker" not able to read from "sr0" which I believe is the DVD drive which it has been using to this point.
I'm running 11.3 normally, udev is not a problem on boot from HD. The DVD media works fine on a Windows laptop showing "Starting udev... ok" and continues. Media checks ok on this machine.
I'm thinking that no matter what medium I use to install from, HD, DVD, net etc this udev problem is going to hit me again unless there is a hint I can pass to the bootup process.
After reading about other experiences with this issue I removed all the non-standard hardware and no difference. The DVD drive seems to be the issue. Bootup is already using it, and yet udev cannot find it.
I've bougt a new pc (i5-2050k, Nvidia GeForce 560Ti) and wanted to install Linux beside Windows.But each Linux-distribution (exept the old ones from Mandriva) fails installing/starting als livecd/checking for installation errors/..... while initiating udev.Is there any known bugfix for this problem? Remind, there is just Windows, so don't give me any shellcode to execute
HW config is: AMD Athlon 64 X2 5000+ Black Edition, MSI 785GTM-E45, 2X 1Gb Kingston HyperX PC2-8500. I have set up GRUB to dualboot openSUSE 11.2 and WindowsXP. Initially i had set up system with defaults: CPU@2600MHz (200X13) and therefore RAM@800MHz. Both openSUSE 11.2 and WindowsXP worked just fine. Memtest86 found no problems.
But after a while i decided to change this setup to: CPU@2500MHz (250X10) and therefore RAM@1000MHz, as it promised better overall performance. And now Windows still boots and works better then before. Memtest86 still can't find any problem. But openSUSE 11.2 hangs at boot. I've suspected cpufreq governor, but changing from Ondemand to Conservative in /sys/devices/system/cpu/cpu0/cpufreq doesn't help.
I installed OpenSUSE 11.2 and manipultes Window Behavior from Personal Settings so I can't access to my account while login. I use kde. Now I can access the system from the root login. How can I restablish the kde default settings on my account from the root account?
I have just completed a dual boot installation of FC10. The install was done from CD's I downloaded from the Fedora website. The installation (seemed to have) went fine, and the machine still boots into XP if selected from the menu. The Fedora installation does not complete the boot process. I have three bars that move across the bottom of the screen, and the Fedora 10 graphic tuns white, and then the system hangs. I have let it sit at this screen for as long as 30 minutes. The screen will blank occasionally, but returns to the same place if I hit a key on the keyboard.
I have it installed on an old HP E800 netserver, running dual P3-866mHz processors, 2GB ram, a ATI Radeon 7000 video card, and three 36GB SCSI drives, non-raid. I know FC10 will run on this machine, as I have a friend running it on another E800 without any problems. This machine does have on-board video that is disabled only by plugging a different video card in (Phoenix BIOS).
Early in the boot process, system generates message "Creating nodes with udev." After a pause, CPU timeout dumps are listed on the display. Likely it is related to wthe display driver (Intel 845G) as the system can be brought up in failsafe mode. /etc/X11.conf is intact. The system was apparently successfully upgraded online from 11.3 using the zypper method. This issue has appeared a day following the upgrade, after restarting the 11.4 system.
I have encountered the same problem as indicated in this post: "udev hang after upgrade from 5.3 to 5.4"[URL]... I'm testing the upgrade path to centos 5.4 on several virtual machines prior to upgrading our production systems. I have upgraded centos 5.2 --> centos 5.4 and centos 5.3 to centos 5.4. In both cases udev hangs after the upgrade. The following message is displayed on the console: "Starting udev: Wait timeout. Will continue in the background [FAILED]"
I found another related post: "udev hangs on boot for a long time, suspect pam_console_apply"[URL]..So, I booted by VMs using the "udevdebug" option to grub and received the same error message - "udevd-event [###]: run_program: Waiting ## seconds for output of '/sbin/pam_console_apply /dev/..."
In my /etc/ldap.conf file "bind_policy hard" is commented out. I added a line "bind_policy soft" as described in the post and my VMs booted fine. NOTE: This problem is not encountered with a fresh install of CentOS 5.4 and the "bind_policy hard" option in the /etc/ldap.conf is commented out as in the upgraded systems. What is really causing this problem and how do I get it addressed? I have a couple hundred systems to update from various releases of CentOS 5 to the latest current version 5.4. It would be nice to get this bug squashed..
I recently tried to upgrade my openSuSe 11.1 system using the instructions at:
SDB:System upgrade - openSUSE
I successfully got the system to 11.2, but the upgrade from 11.2->11.3 went awry. The installation froze during the update, and I had to start it over. The first issue I had to deal with was the fact that rpm had been upgraded and zypper hadn't, so zypper wouldn't function because older rpm files that it would search for had been deleted. After rolling back rpm to a previous version, I managed to complete the upgrade to 11.3 and everything looked good. However, when I rebooted the system, it hangs at a blank screen. More precisely, the system seems to get through all of the BIOS stuff and then hang while loading the OS (I assume). Although I've worked on Windows boxes for a long time, I'm a complete novice at OS installations/upgrades for Linux systems, so I'm not even quite sure where to begin to troubleshoot this. Ideally, I'd like to be able to fix the installation on the system to save the data on the hard drives, but I realize this might not be possible. My first thought was to use a recovery tool that I'd seen on some Linux installation CDs, but I see that for openSuSe 11.3 and on that utility has been dropped. I can, however, use the disk to get to the "Rescue" command prompt, so maybe there's something I can do from there?
System is hanging during boot after a successful fresh install via netinstall disk. Never makes it to any GUI or prompt. However, it does still respond to CTRL-ALT-DEL (not completely frozen).Default debian installation with one exception - KDE checkbox was checked for installation. Everything else was default, with "use full disk with GRUB" option chosen.The boot process appears to hang during the service starts. It appears that the start job for "Create Static De..." is not actually ever completing. I don't know how to troubleshoot that any further than I have.
This is running on hardware, it is not a virtual machine. 480GB SSD, i7, 16GB of RAM, AMD R9 390 (I dunno if this is the problem, but it seems a likely culprit).There are no other disks attached. I have verified successful memtest completions (0 failures) and hard disk is intact and working fine (I have swapped for another disk, and the same thing happens as well).
My skill level with Linux is relatively low. I have proficiency using it and programming for it, but not much in the way of troubleshooting/ installation/ drivers.
Here is an album of "screenshots" (phone photos) of the boot sequence in debug: URL....I tried booting straight to console by removing "quiet" from boot options and changing to "text", but it does not alter the outcome in any discernible way.
I have a Dell Inspiron M5030 and ran the live Gnome CD. everything works until I install. The install goes fine and it boots fine but when i log in it just hangs at the desktop with a spinning cursor. No menus no nothing just the wallpaper?
the (almost) last message I see is"shutting down (remotefs) network nterfaceIf I then press Ctrl-Alt-Del the system goes on until:shutting down (localfs)network interface: eth0... and that's it - further go on possible,by any means.No complete shutdown possible.Until present I did at least get nojournal replay at the next startup
I performed a clean install of Fedora 15 from DVD and it goes fine until the end when the install program says to reboot the computer. Once I do that, the computer hangs before Grub loads, i.e. just after all of the BIOS messages, so there isn't any error message to indicate what is wrong. I had no issues with Fedora 14.
I've been using ubuntu for a couple of years rather successfully on my dual-boot Vista/Ubuntu. It upgraded to 8.0(4?) LTS, 10.04LTS and I kept it there until this afternoon I followed the instructions on the ubuntu site to open up a terminal and update-manager --somearg to provide me with a nice little "Upgrade" button on the update manager. I clicked said button per the instructions, let it do it's downloading and whatever else it does. The last step of the installation is a system reboot. I let it do that, and then my grub menu comes up as more-or-less this:
If I select the top one, I get: Code: Starting up ... with a blinking cursor under the S for a LONG time (used the power switch after ~40 mins). I tried the second 2.6.32-32 option for recovery mode. It spit a bunch of gibberish to the screen for a couple seconds and then stopped, presumably doing the same thing, just with 100% more gibberish. I tried booting into Vista, that worked fine. Just to reiterate, I've not yet seen a 10 LTS login screen or desktop, and can't get one yet (just a "Starting up ...") Just to add, I did try searching, but since the only info I had to go on was 8 LTS to 10 LTS upgrade, and "Starting up ...", well those are just hard keywords to get any meaningful info.