| 1 |
On 04/22/2015 12:17 PM, walt wrote: |
| 2 |
> I just did a huge update on an older ~amd64 machine, and now only |
| 3 |
> three out of a dozen or so kernel modules load during bootup, which |
| 4 |
> leaves a lot of hardware in an unusable state. |
| 5 |
|
| 6 |
Thanks to everyone who replied. The infuriating thing about this problem |
| 7 |
is that I'm sure I went through the same thing a few years ago and then |
| 8 |
forgot about it: |
| 9 |
|
| 10 |
Somehow (probably something stupid I did) these two symlinks got deleted |
| 11 |
somewhere in the middle of the big update: |
| 12 |
|
| 13 |
#ls -l /lib |
| 14 |
lrwxrwxrwx 1 root root 5 Feb 17 05:11 /lib -> lib64 |
| 15 |
#ls -l /usr/lib |
| 16 |
lrwxrwxrwx 1 root root 5 Jul 31 2013 /usr/lib -> lib64 |
| 17 |
|
| 18 |
After that happened, emerge created real directories /lib and /usr/lib and |
| 19 |
put files there instead of in /lib64 and /usr/lib64 where they belong. |
| 20 |
|
| 21 |
I suppose I should be thankful that the machine still boots even as far as |
| 22 |
rescue mode. (I'm not thankful, but that's not your problem ;) |
| 23 |
|
| 24 |
Thanks again for your excellent questions. They always give me new ideas |
| 25 |
for debugging problems like this one. |
Archives