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.
Hello there. I have just compiled Kernel 2.6.24 on Slackware 12 however I have hit a problem. Quite early on in the boot sequence I come across this:
'error init udevd socket'
Then it says the kernel uevent path is /sbin/hotplug after that the computer is unresponsive so I have to reset it.
I have tried setting the kernel uevent path to /sbin/udevtrigger and /sbin/udevd however I am not really sure what to do since I have compiled and recompiled kernels for years and I have never come across this problem!
All I can say is that I hope someone knows the answer to this problem! I hate using the generic kernel that comes with Slackware!
I too was confused by the /sbin/hotplug thing, but I just left it alone (probably not the right thing to do, but a search turned up only one answer that said to probably leave it alone...) and my 2.6.24.2 kernel is up and running fine. However, I know literally nothing on the subject, so YOUR setup may require a real path or some other workaround. I'll just say that my setup is running while leaving UEVENT_HELPER_PATH at the default value of /sbin/hotplug, which doesn't exist. This is the only page I could find on the matter: http://linux.derkeiler.com/Mailing-L.../msg00972.html
Good luck -- and hopefully someone more knowledgeable than me (that would be a monkey) on the matter will be able to provide better help.
Thanks for that. I have changed it back but it is still happening. I haven't actually done anything to Slackware apart from amend the wireless config files so it can connect onto my network from my USB dongle!
Thanks for that. I have changed it back but it is still happening. I haven't actually done anything to Slackware apart from amend the wireless config files so it can connect onto my network from my USB dongle!
What kind of dongle is it, what driver does it use and is it connected so that it'll attempt to load during startup? And if so have you tried booting with it disconnected and the config file adjusted so that it won't attempt? (ie: not load the driver)
Leave the hotplug helper thing in kernel config alone - it doesn't affect us at all.
http://slackware.com/~rworkman/confi...ric-smp-2.6.24 has a kernel config that should "just work" for everyone. As you'll note from the name, it is a "generic" config that will require an initrd, just like the Slackware stock generic kernels. If you know enough to be worrying about building your own kernel, it should be obvious what is required to make it a non-generic config.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.