no grub entry for kernel 3.7.1

[tom_]

I installed a few days ago a MGA3B1 kde dvd live 64bit on wmware,
then I made all the proposed updates.

I have just seen that I'm not running the latest downloaded kernel as it has no entry in the grub menu,
only the kernel 3.7.0 is bootable.
I'm missing something?

Code: Select all

[root@localhost tom]# uname -r
3.7.0-desktop-1.mga3


Code: Select all

[root@localhost tom]# rpm -qa | grep ^kernel
kernel-desktop-latest-3.7.1-1.mga3
kernel-desktop-3.7.1-1.mga3-1-1.mga3
kernel-firmware-20121030-1.mga3
kernel-firmware-nonfree-20121030-1.mga3.nonfree
kernel-userspace-headers-3.7.1-1.mga3
kernel-desktop-3.7.0-1.mga3-1-1.mga3


Code: Select all

[root@localhost tom]# cat /boot/grub/menu.lst
timeout 3
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 0

title linux
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=a83c5170-4d62-40bc-a608-3b8da262fc2d  splash quiet resume=UUID=ab550e90-7869-4b0e-bacd-a03b15f45b39 vga=788
root (hd0,0)
initrd /boot/initrd.img

title linux-nonfb
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=a83c5170-4d62-40bc-a608-3b8da262fc2d  resume=UUID=ab550e90-7869-4b0e-bacd-a03b15f45b39
root (hd0,0)
initrd /boot/initrd.img

title failsafe
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=a83c5170-4d62-40bc-a608-3b8da262fc2d  failsafe
root (hd0,0)
initrd /boot/initrd.img


Code: Select all

[root@localhost tom]# ll /boot/
total 38616
-rw-r--r-- 1 root root      440 Dec 27 12:07 boot.backup.sda
lrwxrwxrwx 1 root root       27 Dec 29 15:12 config -> config-3.7.0-desktop-1.mga3
-rw-r--r-- 1 root root   135724 Dec 11 12:00 config-3.7.0-desktop-1.mga3
-rw-r--r-- 1 root root   135707 Dec 18 09:13 config-3.7.1-desktop-1.mga3
drwxr-xr-x 2 root root     4096 Dec 21 13:28 dracut/
-rwxr-xr-x 1 root root   527360 Dec 27 12:07 gfxmenu*
drwxr-xr-x 2 root root     4096 Dec 29 15:22 grub/
drwxr-xr-x 6 root root     4096 Dec 27 12:40 grub2/
-rw-r--r-- 1 root root 20243036 Dec 27 11:51 initrd-3.7.0-desktop-1.mga3.img
-rw------- 1 root root  7366332 Dec 27 12:37 initrd-3.7.1-desktop-1.mga3.img
lrwxrwxrwx 1 root root       31 Dec 27 12:37 initrd-desktop.img -> initrd-3.7.1-desktop-1.mga3.img
lrwxrwxrwx 1 root root       31 Dec 17 21:24 initrd.img -> initrd-3.7.0-desktop-1.mga3.img
-rw-r--r-- 1 root root   308314 May 15  2011 mageia.bmp
-rw-r--r-- 1 root root   183064 Dec 11 12:00 symvers-3.7.0-desktop-1.mga3.xz
-rw-r--r-- 1 root root   183064 Dec 18 09:13 symvers-3.7.1-desktop-1.mga3.xz
lrwxrwxrwx 1 root root       31 Dec 27 12:29 System.map -> System.map-3.7.0-desktop-1.mga3
-rw-r--r-- 1 root root  2306144 Dec 11 12:00 System.map-3.7.0-desktop-1.mga3
-rw-r--r-- 1 root root  2306147 Dec 18 09:13 System.map-3.7.1-desktop-1.mga3
lrwxrwxrwx 1 root root       28 Dec 17 21:24 vmlinuz -> vmlinuz-3.7.0-desktop-1.mga3
-rw-r--r-- 1 root root  2901184 Dec 11 12:00 vmlinuz-3.7.0-desktop-1.mga3
-rw-r--r-- 1 root root  2899280 Dec 18 09:13 vmlinuz-3.7.1-desktop-1.mga3
lrwxrwxrwx 1 root root       28 Dec 27 12:37 vmlinuz-desktop -> vmlinuz-3.7.1-desktop-1.mga3


[gohlip]

Good catch!

Modify

Code: Select all

kernel (hd0,0)/boot/vmlinuz   ..............
initrd (hd0,0)/boot/initrd.img    .........


to

Code: Select all

kernel (hd0,0)/boot/vmlinuz-desktop    ..............
initrd (hd0,0)/boot/initrd-desktop.img  .........

[gohlip]

Good catch!

It is more than a good catch!
"nokmsboot" is no longer necessary for this kernel boot and that's great!

It seems that when Mageia does its initramfs update, it only does so for its latest kernel and not for all its kernels, requiring a "nokmsboot" for older kernels.
Ah, I can like Mageia more now.

ps: hope Mageia developers correct initramfs update to include dkms in all kernels. Thanks.

[doktor5000]

ps: hope Mageia developers correct initramfs update to include dkms in all kernels. Thanks.

You hope? Have you reported that as a bug?

[gohlip]

You hope? Have you reported that as a bug?

https://bugs.mageia.org/show_bug.cgi?id=8545

You hope?

Isn't that a bit harsh to ask?
Ah...so I see...

Code: Select all

Disclaimer: Beware of grumpy contributor in general and harsh-sounding forum posts in particular (which are not my intent)

It is offputting for people here trying to help and such attitude would definately turn off many people less thick-skinned than me, and I am sure there are much more people less thick skinned than me.
However I too have a disclaimer...

Code: Select all

Disclaimer: Beware of impolite poster in forum  (which are not my intent) who normally would be expremely friendly (except when driving)

No hard feelings. doktor?

[doktor5000]

Nope, no hard feelings at all. My point was just: Hoping is not enough if no developer knows about the bug
Didn't think about if that sounds harsh or not, as that's what i'm doing normally:
Write straight what i'm thinking, hence my signature, for those that may misinterpret that.

Also, i like your disclaimer! Works for me

[gohlip]

Also, i like your disclaimer! Works for me

LOL

Ha ha ha. I only hope that with me (and you, ha ha) in this forum, we won't turn away many people who otherwise would like to write in with helpful suggestions and issues.

Cheers. Grüße.

[doktor5000]

I only hope that with me (and you, ha ha) in this forum, we won't turn away many people who otherwise would like to write in with helpful suggestions and issues.

Well, i have a different point of view on that one. As i'm doing this in my spare time for free,
and since i'm also a user asking in forums for help, and since i'm doing this linux support thing for more than 5 years now,
i've got quite some expectations how users should ask for help, and what manners users should show
if they want to be helped properly, and what they can expect from me.

If somebody is turned away, in 99% of all cases that is deserved (often trollish users). The other 1% definitely deserves an excuse,
even if it was not really my fault. So this may sound harsh, but it works quite well, and i think this is rather fair.

... says someone with ~20.000 support-type posts (only counting Mandriva & Mageia linux there)

[waferhead]

uninstalling grub2 fixes grub entry updating, although i need to look at the kernel arg issue, but the /boot/vmlinux and /boot/initrd.img links appear to be still getting updated, so the first entry is always the most recent kernel/initrd as always AFAIK.
Tis effectively preserves any kernel args you set up for the "liniux" entry at the top, assuming that is still your default.
(The symlink update was also was not working with the default grub+grub2 setup)

[gohlip]

(The symlink update was also was not working with the default grub+grub2 setup)

see
https://bugs.mageia.org/show_bug.cgi?id=8463#c9
Personally, I think there should only be one instance of grub, (but there are some who disagree)
To update grub.cfg in grub2, add

Code: Select all

alias update-grub='grub-mkconfig2 -o boot/grub2/grub.cfg'

as root. in ~/.bashrc

Cheers.

[waferhead]

...So if you have 4 flavors of linux you are testing with, which one manages your grub.cfg?
You trust Ubuntu to get it right for Debian/Suse/Fedora or different versions of itself?

I have never once sucessfully managed to install grub2 to a partition.
I have never once had an issue doing so with grub.

I'm happy you are familiar enough with grub2 that you can manually genmerate a working grub.cfg.
I will never be.

[aranud87]

Hi,

As 3.8 today... only 3.7.1 for boot (only and by default):(

kernel.png (131.13 KiB) Viewed 4615 times

thank you

[gohlip]

my "uname -a" gives me..
Linux localhost 3.8.0-desktop-0.rc3.1.mga3 #1 .......
Did you use vmlinuz or vmlinuz-desktop?

Modify

Code: Select all

kernel (hd0,0)/boot/vmlinuz   ..............
initrd (hd0,0)/boot/initrd.img    .........


to

Code: Select all

kernel (hd0,0)/boot/vmlinuz-desktop    ..............
initrd (hd0,0)/boot/initrd-desktop.img  .........

If you use correctly and still gives 3.7.1, then you can point to it directly instead of the symlinks..

Code: Select all

kernel (hd0,0)/boot/vmlinuz-3.8.0-desktop-0.rc3.1.mga3    ..............
initrd (hd0,0)/boot/initrd-3.8.0-desktop-0.rc3.1.mga3.img .........

see
https://bugs.mageia.org/show_bug.cgi?id=8463#c9

[waferhead]

I just did yet another reinstall of mga3b1, selected grub2 on initial install, rebooted, updated all, uninstalled both grubs then reinstalling grub2 gave me a fully working setup.
(both actually booting and showing new boot kernel entries)
lilo is still installed as it comes in handy occasionally to generate clean MBRs, but did not test.
Still not a huge fan of grub2 based on past experience but it is working for now, although the 2 grubs stepping on each other still needs fixed.

[gohlip]

Just wondering....if grub2 works and grub-legacy does not, why are so many here 'huge fans' of grub-legacy?
It's okay, no response necessary. Just thinking aloud. Do not wish to start a 'preference' war; we are all entitled to our poison.

Cheers.

[waferhead]

Simple:
There was no problem with grub legacy until grub2 was (badly) integrated on the installer cd just for mga3b1.
Have had major issues with grub2 on other distros, as have many.
(over many YEARS)

If lilo didn't have the limitations it does I'd still be running it.
I want a boot loader, not yet another OS.

[gohlip]

Okay, thanks for sharing.
Good to know you've got this Mageia 3 booting right.

Cheers.

[waferhead]

Okay, thanks for sharing.
Good to know you've got this Mageia 3 booting right.

Cheers.

It actually ate itself shortly afterwards after digesting a large batch of updates this AM, I don't suspect grub related, but I'm out of time to play again, back to mga2.
(partclone is my friend)

[waferhead]

Picked up my long neglected Itronix Gobook3 and charged/updated it/rebooted with zero issues.

It is running cooker, installed off the 32 bit version of mga3b1.
(Pentium M---32-bit non PAE only)

Realized that it had no issues with the grub1+grub2 setup, and did NOT eat itself (fail to reboot due to module/config/grub errors)

Possibly the issues are relevant to x64 only? Or resolved with recent updates?
'
OT, kinda

Tried installing Fedora 18, as it has been many, many moons since i tried it.
(like ~core1 ish, and get off my lawn)
I got as far as the installer, it will not allow installation of grub2 to a partition, and appears to be a general POS.
There are no other options.

They REALLY need to borrow a decent installer, the old text more redhat 7 era installer was more effective.

The Mdv/mga installer blows ~everything else away as far as power and ease of use.
(Suse and Ubuntus aren't horrible, haven't tried (true) Debian in awhile)

[waferhead]

Just tried it again on the Lenovo X300, x86 works fine simply "uninstalling" grub2 while in livecd prior to install.

of course B2 is out (and downloading) so we get try it again ...tomorrow.