SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
After upgrading to latest set of changes, my Slackware64 installation is hanging upon trying to start desktop environment - for example, I can see KDE loading, but keyboard and mouse are not responding. It's really vanilla installation, with NVIDIA binary driver added only (that I reinstalled after this upgrade, but this didn't help), on ThinkPad W520 laptop. So far, the only suspicious thing I've found is that t the end of boot, after gpm loaded, following message is printed:
O0o.oops(): [server_tools.c(76)]: Could not open (null)
After upgrading to latest set of changes, my Slackware64 installation is hanging upon trying to start desktop environment...
After downgrading to udev-175, I am able now to start KDE properly (in particular, keyboard and mouse are responding).
On the other side, I've checked dmesg, and I can see:
[ 5.792041] udev: starting version 165
[ 7.014032] udevd: starting version 175
there - don't know is this supposed to be this way, or I should do something to disable starting version 165?
Thanks, that fixed it indeed. Out of curiosity - how users were supposed to know this?
On one hand, that's a legitimate question. On the other hand, this is not a new release of Slackware - we're talking about the development branch that's intended for users who either know how the system fits together or want to *learn* how it fits together. If you're not in one of those groups, then you should wait for the release, after which rebuilding the initrd will be an obvious step due to the kernel upgrade.
Now, which of those two hands has the most appropriate answer? I'm not sure; I think they're both appropriate. :-)
Just to clarify it here: I was intending to say that udev-182 upgrade worked fine, once I ran mkinitrd after doing the upgrade.
@rworkman: I don't know... I consider myself knowledgeable user, for >10 years I'm using Slackware only; but for example, even that I'm using generic kernels from long ago, I still don't know exactly after which upgrades mkinitrd should be run (except, of course, after kernel upgrade), nor where/how to found this info.
Understood. Even though I didn't elaborate on it as much, I really did mean it when I said that it was a legitimate question. I'm still trying to figure out how to best document an answer (and where to document it).
Thanks, CONFIG_DEVTMPFS fixed it for me. I was also testing 3.4.x and 3.5.x, and had not known about that kernel parameter. Like the last poster, I've also seen some episodes of slowness. Reboot again and its fine. Testing too much stuff at once so I can't attribute it to the kernel or udev. I'm leaning towards udev though. Doesn't fill me with confidence for systemd.