You are not logged in.
So I have an Arch Linux installation and it gives me an error when I try to boot saying '
file '/boot/initramfs-linux.img' not found'. I have tried chrooting into it using a random Ubuntu 20.04 ISO to reinstall the kernel (which would run 'mkinitcpio', I guess), but it gives me another error saying '
ERROR: '/lib/modules/5.16.13-arch1-1' is not a valid kernel module directory'. Now I don't know what to do anymore.
Offline
Is /lib a symlink to usr/lib/?
Offline
Is /lib a symlink to usr/lib/?
I don't know. Should it?
Offline
Scimmia wrote:Is /lib a symlink to usr/lib/?
I don't know
file /libor
readlink /libLast edited by Irets (2022-03-09 18:14:14)
Offline
dabigwaffle wrote:Scimmia wrote:Is /lib a symlink to usr/lib/?
I don't know
file /libor
readlink /lib
The first one said '
/lib: directory' and the second one had no output. I guess it means there is no symlink.
Offline
That's a big problem. What's in there? Did you `sudo make install` something? Use pacman's --overwrite when you shouldn't have?
Offline
That's a big problem. What's in there? Did you `sudo make install` something? Use pacman's --overwrite when you shouldn't have?
I have used 'sudo make install' for dwm, but I don't remember ever using overwrite in pacman.
Offline
So again, what's in there? It's possible that dwm installation overwrote the symlink with a dir and put some of it's files in there.
Offline
So again, what's in there? It's possible that dwm installation overwrote the symlink with a dir and put some of it's files in there.
In '/lib'? There's a lot of library binaries. Same for '/usr/lib'.
Offline
If there's a lot in there, you've done more than install dwm. Your best bet may be to rename that dir and make the symlink to usr/lib, then you can go back and figure out what all is in that dir and broken later.
Offline
If there's a lot in there, you've done more than install dwm. Your best bet may be to rename that dir and make the symlink to usr/lib, then you can go back and figure out what all is in that dir and broken later.
I have just remembered that I have recently done something else... I have moved my installation from one hard drive to another. I might have messed something up during that process as well. The system used to boot up nicely after that, but once I updated the kernel, the issue started. I wonder if I should just reinstall after this whole thing...
Last edited by dabigwaffle (2022-03-09 20:27:51)
Offline
I'm guessing every symlink is now a copy of what it was pointing to. Reinstalling fresh would probably be the simplest solution at this point.
Offline
I'm guessing every symlink is now a copy of what it was pointing to. Reinstalling fresh would probably be the simplest solution at this point.
Ok, that's what I'm going to do.
Offline