You are not logged in.
Pages: 1
Hi! I just updated linux-3.0.1 and after rebooting, GRUB says:
Error 15: File not found.
I can't boot the system, I'm writing from my phone.
Maybe I should change the vmlinuz26 or the kernel26.img names in GRUB lines.
Any ideas? Thanks in advance
Offline
you should really subscribe to arch-dev-public
Give what you have. To someone, it may be better than you dare to think.
Offline
If you use testing, you should watch the mailing list. The upgrade path from 3.0-2 to 3.0.1-1 is not completely smooth. You need to change the kernel image name from vmlinuz26 to vmlinuz-linux (you can do that from within grub).
Offline
Thank you very much. My Arch box is booting now. I'm going to subscribe right now.
Thanks again for you help
Offline
Pardon my ignorance, but shouldn't grub (/boot/grub/menu.lst) have been updated along with the linux package?
menu.lst is pointing to vmlinuz26 which is no longer created by the linux package.
If I'm wrong about this, what is the reason for not updating grub?
Offline
Pardon my ignorance, but shouldn't grub (/boot/grub/menu.lst) have been updated along with the linux package?
menu.lst is pointing to vmlinuz26 which is no longer created by the linux package.
If I'm wrong about this, what is the reason for not updating grub?
it was updated in the grub package but for sure was installed as menu.lst.pacnew. we don't touch users configuration at update. never!
Give what you have. To someone, it may be better than you dare to think.
Offline
Are you sure?
kernel /vmlinuz26 root=/dev/sda3 ro
Offline
Same, just pulled 3.0.1 and the .pacnew has vmlinuz26.
I know 'read the mailing list' and so on, but for a significant change that will bork your boot couldn't there be a PostInstall pacman message like:
### IMPORTANT - You really need to check the pacnew file and merge! ###
Offline
I don't agree with you entirely, Wittfella. If .pacnew files are created pacman already tells you about it. That's fine.
But it's beside the point. As I mentioned in my previous post grub is not updated, so there is no .pacnew to merge.
The real problem here is, as far as I can see, that grub was/is not updated along with the update for linux 3.0.1-1.
Last edited by Lars Stokholm (2011-08-07 11:25:06)
Offline
so there is no .pacnew to merge.
Oh my mistake, that might have been an old menu.lst.pacnew. I thought I merged/cleared all the pacnew files recently, must have missed that one.
Well in that case, some sort of PostInstall pacman message would be even more relevant, if there is no related pacnew.
Offline
Slightly relevant bug report
Not that anyone ever reads the pacman output anyway.
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
I just had this problem.I had to figure it out myself.You have to do what @brain0 said:rename vmlinuz27 to vmlinuz-linux in the menu.lst.
Offline
Grub has been updated. Problem solved.
Offline
If I might add my two cents: first, I regularly read arch-dev-public, and I usually keep my system configs properly updated. Still, I think that this change more than warranted a warning in pacman's output. The reason is that most file config changes, if left (temporarily) unattended---instead of being taken care of *right now*---will not make your system unable to boot. Thus, it is something that most users, even testing users, might not expect. And that's the reason why I think a warning should have been outputted by pacman. After all, if we don't do so in important situations like this one, why does such a feature exist at all?
Last edited by gauthma (2011-08-07 19:18:13)
Offline
Pages: 1