I have the same problem on my Samsung Q45 Laptop which I have since yesterday (yay!).
I installed Widows XP fairly successfully for compatibility reasons and wanted to go Sabayon next. The boot CD (4.0-r1 x86) hangs at that exact position, no matter what kernel boot options from the Cheat Codes page from the SL wiki I add.
I went ahead and tried multiple different boot cds. both x86 and x86_64 versions of both 3.4 mini and 4.0-r1 and the x86_64 version of 3.4f hang waiting for uevents to be processed. Hang as in: the cursor (the little underscore thingy) that blinks while booting stops blinking (it either stays on or off, whichever it is at that moment), and the caps lock key doesn't change the led any more and I have to unpower the laptop to restart it (holding down the power button for 5secs).
I also tried different other distro cd's/dvd's that I had lying around. I did a debian netinstall but I disliked the hardware support (wouldn't even find my wireless) and the feel of apt. xubuntu stuck somewhere in the boot process, too, but I couldn't find out where. I was able, however, to boot into a gentoo minimal install cd. I then booted the (fully functional) SL DVD on my main computer, with most hard drives unplugged to have it as simple as possible, installed on a spare hard drive with my desired hostname and config, then logged into the gentoo livecd on the laptop, formatted the linux partition and copied the installation over:
- Code: Select all
sabayon /mnt/gentoo # tar -cf- * | ssh ${laptop} tar -C /mnt/gentoo -xvf-
with 9.7G used space, this took a while, obviously, but it worked ok. I then adjusted the UUIDs in /boot/grub/grub.conf and /etc/fstab and figured I'd try rebooting. It stuck. Again. Same spot: "waiting for uevents to be processed". Which, by the way, is a point in the bootup process at which pressing "I" for interactive boot mode doesn't work yet.
So... is there any way to cause the bootup process to be more verbose in what happens while uevents are being processed? maybe something I could do to ... bypass that? or at least limit what it does?
I really WANT SL to work on that laptop box. Alternative would be bare gentoo, but I dread forcing that cute little CPU to compile an entire system. I like the way SL combines gentoo with out-of-the-box functionality, which is why my main computer is running SL now, too.
Any help GREATLY appreciated!