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.
Distribution: Slackware 12.2, Slackware Current 32/64
Posts: 138
Rep:
Not much to go with here. If the system hangs and does not continue from this point, you will have to disable udev (assume this is the fault). To do this, boot with a startup cd, mount the drive that has etc and remove execute permission from rc.udev
Code:
chmod 644 <mount point>/etc/rc.d/rc.udev
NOTE: <mount point> is the point which the disk was mounted.
Reboot.
If the system starts, you can try to start udev manually to look for errors.
I experienced a similar problem. Since 12.1, I cannot boot with the huge kernel and my HVR-1250 TV card installed. For the short duration when updating the system until I compile a new kernel, I have to blacklist the CX-23885 module. Black listing allows me to get through the initial updating phase until I roll a new kernel.
Presuming you are suffering a similar problem, and if you know which hardware is causing the freeze, then you can use the installation CD/DVD to boot the system and blacklist the device module. If you do not know which device might be the problem, boot with the installation CD/DVD and then disable various rc.d services to allow booting without the installation CD/DVD. Thereafter you will have to troubleshoot to determine the misbehaving module.
Then again, you mentioned updating the kernel headers. That might be the problem too.
Location: @ /home & @ my blog at http://saurabh-nigam.blogspot.com/
Distribution: Slackware , Fedora , Ubuntu
Posts: 35
Original Poster
Rep:
today i used slackware12.2 dvd & found that i had 2 udev entries namely
/etc/rc.d/rc.udev
/etc/rc.d/rc.udev.new
@tux_dude
I did what you said ie. changed permissions of rc.udevd & it booted comletely but then i couldn't access Internet from there
& mouse is not working
rc.dev was halting the system(i think so) & rc.udevd.new was working fine
so i linked rc.udev-->rc.udev.new
but boot again hanged at
.........
Code:
/dev/ttyS?:No such file or directory
Using /etc/random-seed to initialize /dev/urandom
Intel ISA PCIC probe:not found
Databook TCIC-2 PCMCIA probe:not found
help
Last edited by saurabh nigam; 10-21-2009 at 12:09 PM.
Unless you have a specific reason otherwise, standard Slackware practice is to rename rc.udev.new to rc.udev.
Now that you have shared the information about updating from 12.1 to 12.2, you do need to rename the file. Leave the renamed script executable (chmod +x).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.