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.
I've spent the last 24 hours trying to do a fresh install of 13.37 (64bit) and then "upgrade" (Ha) to -current. I've made at least 3 attempts from scratch. Might be four. At this point I'm so tired I don't remember. Each time there was a problem and I finally figured it out....
But this is the last straw... I had everything working well, except Xfce, but KDE 4.8.4 was working OK. NetworkManager still doesn't work, but wicd is doing the job for now.
Just when I thought all was nearly done, I fired up KDE and the whole desktop went upside down and backwards. You can see it start from the splash screen. It happens to both user and root.
Picture attached. I didn't crop out the HP logo so you can see this isn't some sort of trick.
I've had this problem before. You'll have to rebuild your nvidia drivers I suppose.
I fired up KDE and the whole desktop went upside down and backwards. You can see it start from the splash screen. It happens to both user and root.
Picture attached. I didn't crop out the HP logo so you can see this isn't some sort of trick.
If you are using a binary video driver, have you reinstalled it?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Rep:
Quote:
Originally Posted by TommyC7
No offense to you cwizardone (I know you're having a real problem), but that's hilarious. There seems to be a lot of things with SCSI drivers though, and I've run into one of them too it seems...
If you like that one, you'll love this one. This was back on 8 May 2012. I started a fresh install and went to the corner market for a few minutes. I came back, grabbed a cup of coffee, and sat down in front of the monitor to find the installation had frozen and this is what was on the screen. Seems there are some bugs or old data hidden in the installation software somewhere.
I deleted the ~.kde directory and re-started. So far, so good.
I had the upside down reverse screen a few months ago.
It happened when messing with the Nvidia driver.
I normally use nouveau.
I remember deleting the .kde directory and doing a:
"upgradepkg --reinstall" kde, x, and maybe l also. I really don't remember anymore. It certainly was shocking. I immediately thought some one was playing a cruel joke
Not sure if this is a result of the latest upgrades, everything is running smoothly here but noticed that the /dev/root link is not there anymore, found out when running lilo after compiling a custom 3.4 kernel, it failed since lilo.conf has "boot = /dev/root", workaround is easy but why has /dev/root disappeared?
Thanks.
Quote:
# ls -lh /dev/root
/bin/ls: cannot access /dev/root: No such file or directory
Not sure if this is a result of the latest upgrades, everything is running smoothly here but noticed that the /dev/root link is not there anymore, found out when running lilo after compiling a custom 3.4 kernel, it failed since lilo.conf has "boot = /dev/root", workaround is easy but why has /dev/root disappeared?
Thanks.
How did "boot = /dev/root" end up in lilo.conf? Did liloconfig do that somehow?
Upstream udev dropped the /dev/root symlink because it was really never supposed to be used for anything. Frankly, I'm not sure why the kernel ever provided it in the first place. It used to know what the actual root partition was without requiring an initrd to figure it out, but perhaps that's because the kernel used to need to be prepped with "rdev", which is long obsolete.
How did "boot = /dev/root" end up in lilo.conf? Did liloconfig do that somehow?
Upstream udev dropped the /dev/root symlink because it was really never supposed to be used for anything. Frankly, I'm not sure why the kernel ever provided it in the first place. It used to know what the actual root partition was without requiring an initrd to figure it out, but perhaps that's because the kernel used to need to be prepped with "rdev", which is long obsolete.
Running liloconfig fails on my machine with the message below, so I copied (a very old) lilo.conf, edited it manually and ran lilo. That old copy had "boot = /dev/root" in it.
Code:
# liloconfig
liloconfig: couldn't open /tmp/lilotmp1: No such file or directory
You could try mkinitrd with -f ext4 -r /dev/sda5 and see if your initrd error goes away.
Thanks hocthili, that did the trick.
I did "cat /boot/initrd-tree/rootdev" before running mkinitrd again and it returned /dev/
I guess you are right, at first mkinitrd tried to resolve /dev/root but failed as /dev/root did not exist.
EDIT I just looked at /sbin/mkinitrd and can confirm your assumption
Code:
# If $ROOTDEV and $ROOTFS are not set, assume we want the
# values for the currently mounted /
# (unless we find that values are already set in the initrd-tree):
if [ -z "$ROOTDEV" -a -z "$(cat $SOURCE_TREE/rootdev 2>/dev/null)" ]; then
ROOTDEV=$(mount | grep ' on / ' | cut -f 1 -d ' ')
if [ "$ROOTDEV" = "/dev/root" ]; then # find real root device
ROOTDEV="/dev/$(readlink /dev/root)"
fi
fi
In my case $ROOTDEV was not set and the source tree didn't exist yet, but "mount" returned /dev/root as / filesystem hence $(readlink /dev/root) was null and $ROOTDEV was set to /dev/
So the real problem seems to be "why do the mount command return /dev/root as filesystem for / here?"
PS for Pat: maybe the script could issue a warning in case $(readlink /dev/root) be null? Or look at /etc/fstab in that case?
PS2 I notice that whilst a generic kernel is used "mount" report the real device name for / (in my case /dev/sda5). Unfortunately chances are that mkinitrd be run whilst using a huge kernel...
Last edited by Didier Spaier; 07-21-2012 at 05:53 PM.
Reason: Added EDIT ...
My luks container never gets unlocked. If I try to run 'cryptsetup' from that shell, the error message is 'Cannot initialize crypto RNG backend.'
At this point I'm beginning to think that my kernel config is the problem. I'm seeing that some things I've always built as modules (i.e. ext4, mbcache, etc.) are now built into the kernel.
Quote:
Originally Posted by catfoo
Up and running 3.4.6 now after using the default /boot/config-generic-smp-3.2.23-smp file.
I do find it curious that the new /boot/initrd-tree/dev folder still doesn't have the random and urandom nodes. I'll just assume it has to do with differences in the kernel configuration until someone tells me otherwise.
Thanks for the help.
Is CONFIG_DEVTMPFS disabled in the kernel that is failing ?
udevd (according to the manpage) should copy the devices from /lib/udev/devices so /dev/urandom should be in /dev. However, for some reason it doesn't get copied (at least in my case and yours) and cryptsetup fails. If CONFIG_DEVTMPFS is enabled (as it is in the generic slackware kernel) then the devices are present and everything works fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.