Making an initrd if you can't boot your installation?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Another update: I built a new kernel (2.6.27.5) and initially, it wouldn't boot, complaining about /dev/hda3 not existing (the new kernels refer to the disk as /dev/sda, I believe this is a libata thing) and I didn't really know why. Someone suggested I check my fstab and sure enough, it had /dev/hda3 for my root partition and /dev/hda2 for my swap partition (since that's what the partitions were called under the old kernel). So, I had to mount my root partition under Ubuntu and edit the fstab. Rebooted and it boots fine, but I haven't tested how it works yet!
The messages that you describe appear to arise from the /etc/rc.d/rc.modules script.
Perhaps your hang is coming from module probing.
e.g.
Quote:
### Built-in PC parallel port support ###
# Generic setup example. Attempt to load by default, since it usually
# won't hurt. Some (most?) people may want to comment the line below
# and look into better functioning and performing hardware specific
# options as described later on in this section.
#
/sbin/modprobe -q parport_pc 2> /dev/null
You could try commenting out modules to see if the hang can be bypassed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.