You are not logged in.
So I did an upgrade last night and hosed my install completely. X didn't start up again, no eth0, no nothing.
According to https://wiki.archlinux.org/index.php/De … iki:usrlib, lib is now a link to /usr/lib. Something must have gone wrong on my system, since my /lib still is a real directory.
At any rate, my issue was that the modules directory was not flound by modprobe anymore, because of the /usr/lib change, I assume. When looking at /usr/lib/modules, I only found one directory "3.4.4-3-ARCH", even though my kernel version is frozen to 3.0-ARCH. So I created a symlink in /usr/lib/modules pointing to /lib/modules/3.0-ARCH, rebooted, and now everything works again.
Hope this helps someone else.
On a side note, anyone know what I need to do to properly upgrade such that my /lib becomes a symlink, or should I just leave things as is? Pacman never complained....
Last edited by awayand (2012-07-15 16:57:44)
Offline
It would be helpful if you mentioned which procedures you followed during the upgrade. /lib should have been done away with automatically if the upgrade was done properly, and symlinking should have been unnecessary (and is undesireable).
Offline
Did you ever read and follow this?
Your system otherwise may be in danger now.
To know or not to know ...
... the questions remain forever.
Offline
@bernarcher: yes, I did. I ran "pacman -Syu --ignore glibc", then I re-ran pacman -Syu, then I ran "pacman -Sd binutils gcc gcc-libs"
EDIT: I should also mention that I have frozen kernel upgrades because of wlan issues anything past the 3.0 kernel...
IgnorePkg = skype parcellite dwm wine linux postgresql
Last edited by awayand (2012-07-15 13:47:41)
Offline
works now. glibc did not update, my mistake.
Offline
You'll soon run into problems if you freeze the kernel version. Another option is to use linux-lts.
Offline