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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
All I have managed to do is make the timeout 45 secs which helps a little but is still too long. Anything less than 45 secs and dhcp is not able to get an ip address and hangs indefinitely in rc.inet1 until I give the 3 fingered salute. I'm guessing that it's because udev hasn't found or initiated my NIC yet(?)
I really don't know where to go from here except to downgrade udev and test, downgrade, test, etc.
If anyone has any thoughts on this or has anything to add please do.
Did you check your '/etc/udev/rules.d/75-network-devices.rules' for the NIC? What about the '/etc/rc.d/rc.inet1.conf' file, settings correct for the device(s)?
All I have managed to do is make the timeout 45 secs which helps a little but is still too long. Anything less than 45 secs and dhcp is not able to get an ip address and hangs indefinitely in rc.inet1 until I give the 3 fingered salute. I'm guessing that it's because udev hasn't found or initiated my NIC yet(?)
I really don't know where to go from here except to downgrade udev and test, downgrade, test, etc.
If anyone has any thoughts on this or has anything to add please do.
You simply wait for the udev guys to fix this. This is a bit of a "known problem" at this point. It should go away if you actually have a carrier (i.e., a network plugged into) on the ethernet interfaces when it's probing them because that's what it's waiting for.
Yes, it's annoying, but we're Linux users so we don't reboot very often.
Did you check your '/etc/udev/rules.d/75-network-devices.rules' for the NIC? What about the '/etc/rc.d/rc.inet1.conf' file, settings correct for the device(s)?
Yep all seems correct.
Quote:
Originally Posted by evilDagmar
You simply wait for the udev guys to fix this. This is a bit of a "known problem" at this point. It should go away if you actually have a carrier (i.e., a network plugged into) on the ethernet interfaces when it's probing them because that's what it's waiting for.
Yes, it's annoying, but we're Linux users so we don't reboot very often.
Yeah mine is on practically 24/7 anyway now, but it is annoying when I used to boot in 30 secs or so.
I do have a carrier from my cable modem afaik (all the leds are on as normal). Strange thing is I tried udev 097 package, but with the rc.udev from 116 and the problem went away. But I had quite a few dhcpd errors and also an error because 097 udevtrigger doesn't seem to recognise the '--retry-failed' switch. But taking this out just made boot up freeze at rc.inet1. Strange.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.