ArchThis Forum is for the discussion of Arch 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.
Dear Archers, resently i upgradet the system with the well known pacman -Syu
During this, the kernel was automatically upgraded from 2.6.3-scsi to 2.6.4-scsi. Aften the upgrade was succesfully done, i ran lilo.
Now the system won't boot.
Can someone please explain to me what I did wrong?
I checked the /boot patition and my lilo.conf by booting on the Arch cd, and cdroot into my installed linux. Both the lilo.conf and the /boot looks fine.
I have forgotten to run lilo after a kernel upgrade in the past, and the symptom is exactly like you say. Since that is not it, I hope someone else has some ideas for you.
Well I have been looking a bit into it.
It seems that under a normal Arch installation, it uses the file "map". After upgrading there is a file called "system.map26" could that have something to do with it?
Anyway I tried to add the map=/boot/system.map26 in lilo, ran the lilo command re reboot. Same result... Strange.
What if I used grub instead? How dows one update the grub interfaces?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.