When I rebooted my machine after pacman -Syu, I got a kernel panic error (don't remember what it said). Maybe my problem is about this http://archlinux.org/news.php#178
Where it says: "the /dev/discs entries will not work anymore on boot prompt. Please change it according to kernel26 install message."
What I have to change exactly?
if grub starts. chooese "e" for edit and edit the line to /dev/hda2 or /dev/sda2
or whatever it si in your case. then continuee the boot process with "b"
If you´re then in arch change the lines in grub
change it in /boot/grub/menu.lst
root=/dev/discs/disc0/part4 ---> root=/dev/hda4
I see this as possibly being a problem that will come up for many people. The frontpage should include a few extra simple lines telling people exactly what to change. (instead of having to come search in the forums)
Nerds: the frontpage tells users for ages udev will replace devfs with the coming release. It tells you since ages you won't be able to boot if you don't edit the config files, and it tells you which they are.
So .... how you dare doing such a big update without knowing what it is about? ... this is not debian or another linx distro that does everything for the user. This is arch, this is KISS - you have to read, and be prepared. You will learn a lot, and if you are ready for arch, you will like it.
DevFS is leaving posted by Judd
June 13, 2005
Just so you're aware, DevFS support will soon be removed from the 2.6 kernel. If you are using the 2.6 kernel and haven't migrated to uDev yet,
you should really think about doing so. When DevFS leaves the vanilla kernel, we will no longer support it on 2.6.
There is a brief uDev HOWTO here.
Frumpus ♥ addict
Even the kernel upgrade itself tells what needs to be done, as it posts a clear message about it right on the screen. Maybe some people aren't noticing it during the upgrade process.
Perhaps any potentially fatal problems could be posted in red print and be accompanied by a beep, or something similar.
Frumpus ♥ addict
Yeah, that ought to do it!
Actually, though, it might be better if the fireworks happened "after" the updates are successfully implemented without problems/errors.
This happened to me and I had to come here to the forums to figure out how to fix it. Why? Because I hardly ever come check the website to see if the next upgrade will break things. I've just been doing the "pacman -Syu" thing for about a year now, usually every weekend and haven't had many issues... except this one... which was solved quick enough. I guess I've grown too accustomed to having the upgrade just work that I'm taking it for granted. I usually just run the upgrade command and come back later to reboot. Read the install messages? Ha.
Read the install messages? Ha.
I'd have read it, but pacman downloaded and installed 400MB of upgrades for me ... the kernel install message was lost in the noise, you could say.
The post on the web site isn't very helpful. In the end, I re-installed the kernel package to read the install message as mentioned in the news post as that was quicker than trying to find it in the pacman.log ...