Latest updates break kubuntu boot

[aiiee]

today. Installed latest patches, including a new kernel. Now my Wubi install of 9.10 goes to Grub editor rather than booting!
It worked fine earlier this morning, now I cannot get in at all. This must be happening to many many others. What do I need to do to fix this latest gaff?

[aiiee]

odd. I would have thought people would be running into this a lot. I guess I'll go check around and make sure grub is pointing to the new kernel. If there is a new kernel. Not sure what happened. I just know I let kpackagewhatever run updates and a kernel was referenced as it was updating. bleagh. :'(

[GreyGeek]

odd. I would have thought people would be running into this a lot. ....


Well, you gave them only an hour to respond before your last post! Folks on this forum are fast, but generally not that fast, except for SnowHog --- he lives here! ;D

A link showing common Grub2 problems and how to fix them is here. (http://kubuntuforums.net/forums/index.php?topic=3081671.0) Notice especially Sections 2, 3 and 4.

[Snowhog]

except for SnowHog --- he lives here! ;D

What? Did I just hear my name? Hmm.

[tnorris]

Just Great! The little "restart required" icon has been staring at me all day since I installed the updates this morning. Now you've got me scared to death to click it. :-\ :-\ :-\ ;D

[aiiee]

odd. I would have thought people would be running into this a lot. ....


Well, you gave them only an hour to respond before your last post! Folks on this forum are fast, but generally not that fast, except for SnowHog --- he lives here! ;D

A link showing common Grub2 problems and how to fix them is here. (http://kubuntuforums.net/forums/index.php?topic=3081671.0) Notice especially Sections 2, 3 and 4.


I just meant if it was the update's fault , lots of people would be yelling, and they're not, so it's something I did :o

thanks for the pointer. After thinking about it, I might have added a non standard repository..... aiiiiiee!

[aiiee]

Just Great! The little "restart required" icon has been staring at me all day since I installed the updates this morning. Now you've got me scared to death to click it. :-\ :-\ :-\ ;D


ut oh. Was a new kernel in your update?

[tnorris]

Yeah, the new kernel was in there. I didn't even pay much attention to what all it updated since I was multi-tasking at the time.

Here's the apt log of what was updated:


Log started: 2009-11-23 13:15:22
Selecting previously deselected package linux-image-2.6.31-15-generic.
(Reading database ... 45%
(Reading database ... 90%
(Reading database ... 141353 files and directories currently installed.)
Unpacking linux-image-2.6.31-15-generic (from .../linux-image-2.6.31-15-generic_
2.6.31-15.50_i386.deb) ...
Done.
Preparing to replace avahi-autoipd 0.6.25-1ubuntu5 (using .../avahi-autoipd_0.6.
25-1ubuntu5.1_i386.deb) ...
Unpacking replacement avahi-autoipd ...
Preparing to replace libavahi-common-data 0.6.25-1ubuntu5 (using .../libavahi-co
mmon-data_0.6.25-1ubuntu5.1_i386.deb) ...
Unpacking replacement libavahi-common-data ...
Preparing to replace libavahi-common3 0.6.25-1ubuntu5 (using .../libavahi-common
3_0.6.25-1ubuntu5.1_i386.deb) ...
Unpacking replacement libavahi-common3 ...
Preparing to replace libavahi-core6 0.6.25-1ubuntu5 (using .../libavahi-core6_0.
6.25-1ubuntu5.1_i386.deb) ...
Unpacking replacement libavahi-core6 ...
Preparing to replace avahi-daemon 0.6.25-1ubuntu5 (using .../avahi-daemon_0.6.25
-1ubuntu5.1_i386.deb) ...
avahi-daemon stop/waiting
Unpacking replacement avahi-daemon ...
Preparing to replace libavahi-client3 0.6.25-1ubuntu5 (using .../libavahi-client
3_0.6.25-1ubuntu5.1_i386.deb) ...
Unpacking replacement libavahi-client3 ...
Preparing to replace avahi-utils 0.6.25-1ubuntu5 (using .../avahi-utils_0.6.25-1
ubuntu5.1_i386.deb) ...
Unpacking replacement avahi-utils ...
Preparing to replace easytag 2.1.6-1 (using .../easytag_2.1.6-1ubuntu0.1_i386.de
b) ...
Unpacking replacement easytag ...
Preparing to replace libavahi-compat-libdnssd1 0.6.25-1ubuntu5 (using .../libava
hi-compat-libdnssd1_0.6.25-1ubuntu5.1_i386.deb) ...
Unpacking replacement libavahi-compat-libdnssd1 ...
Preparing to replace libavahi-glib1 0.6.25-1ubuntu5 (using .../libavahi-glib1_0.
6.25-1ubuntu5.1_i386.deb) ...
Unpacking replacement libavahi-glib1 ...
Preparing to replace libavahi-qt3-1 0.6.25-1ubuntu5 (using .../libavahi-qt3-1_0.
6.25-1ubuntu5.1_i386.deb) ...
Unpacking replacement libavahi-qt3-1 ...
Preparing to replace libgstreamer-plugins-base0.10-0 0.10.25-2ubuntu1 (using ...
/libgstreamer-plugins-base0.10-0_0.10.25-2ubuntu1.1_i386.deb) ...
Unpacking replacement libgstreamer-plugins-base0.10-0 ...
Preparing to replace libindicate3 0.2.3-0ubuntu1 (using .../libindicate3_0.2.3-0
ubuntu2_i386.deb) ...
Unpacking replacement libindicate3 ...
Preparing to replace linux-firmware 1.24 (using .../linux-firmware_1.25_all.deb)
...
Unpacking replacement linux-firmware ...
Preparing to replace linux-generic 2.6.31.14.27 (using .../linux-generic_2.6.31.
15.28_i386.deb) ...
Unpacking replacement linux-generic ...
Preparing to replace linux-image-generic 2.6.31.14.27 (using .../linux-image-gen
eric_2.6.31.15.28_i386.deb) ...
Unpacking replacement linux-image-generic ...
Selecting previously deselected package linux-headers-2.6.31-15.
Unpacking linux-headers-2.6.31-15 (from .../linux-headers-2.6.31-15_2.6.31-15.50
_all.deb) ...
Selecting previously deselected package linux-headers-2.6.31-15-generic.
Unpacking linux-headers-2.6.31-15-generic (from .../linux-headers-2.6.31-15-gene
ric_2.6.31-15.50_i386.deb) ...
Preparing to replace linux-headers-generic 2.6.31.14.27 (using .../linux-headers
-generic_2.6.31.15.28_i386.deb) ...
Unpacking replacement linux-headers-generic ...
Preparing to replace linux-libc-dev 2.6.31-14.48 (using .../linux-libc-dev_2.6.3
1-15.50_i386.deb) ...
Unpacking replacement linux-libc-dev ...
Processing triggers for man-db ...
Processing triggers for sreadahead ...
Setting up linux-image-2.6.31-15-generic (2.6.31-15.50) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.31-15-generic
Running postinst hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.31-15-generic
Found kernel: /boot/vmlinuz-2.6.31-14-generic
Found kernel: /boot/vmlinuz-2.6.28-11-generic
Found kernel: /boot/memtest86+.bin
Replacing config file /var/run/grub/menu.lst with new version
Updating /boot/grub/menu.lst ... done

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/nvidia-common

Setting up avahi-autoipd (0.6.25-1ubuntu5.1) ...

Setting up libavahi-common-data (0.6.25-1ubuntu5.1) ...
Setting up libavahi-common3 (0.6.25-1ubuntu5.1) ...

Setting up libavahi-core6 (0.6.25-1ubuntu5.1) ...

Setting up avahi-daemon (0.6.25-1ubuntu5.1) ...
Installing new version of config file /etc/init/avahi-daemon.conf ...
avahi-daemon start/running, process 18040

Setting up libavahi-client3 (0.6.25-1ubuntu5.1) ...

Setting up avahi-utils (0.6.25-1ubuntu5.1) ...
Setting up easytag (2.1.6-1ubuntu0.1) ...

Setting up libavahi-compat-libdnssd1 (0.6.25-1ubuntu5.1) ...

Setting up libavahi-glib1 (0.6.25-1ubuntu5.1) ...

Setting up libavahi-qt3-1 (0.6.25-1ubuntu5.1) ...

Setting up libgstreamer-plugins-base0.10-0 (0.10.25-2ubuntu1.1) ...

Setting up libindicate3 (0.2.3-0ubuntu2) ...

Setting up linux-firmware (1.25) ...
Setting up linux-image-generic (2.6.31.15.28) ...
Setting up linux-generic (2.6.31.15.28) ...
Setting up linux-headers-2.6.31-15 (2.6.31-15.50) ...
Setting up linux-headers-2.6.31-15-generic (2.6.31-15.50) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/nvidia-common

Setting up linux-headers-generic (2.6.31.15.28) ...
Setting up linux-libc-dev (2.6.31-15.50) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Log ended: 2009-11-23 13:16:56

[tnorris]

OK, here goes. I'm about to reboot...Hopefully I'll be back in a few minutes. <crosses fingers>

Edit: All went well. No problems to report here.

[bobcollard]

today. Installed latest patches, including a new kernel. Now my Wubi install of 9.10 goes to Grub editor rather than booting!
It worked fine earlier this morning, now I cannot get in at all. This must be happening to many many others. What do I need to do to fix this latest gaff?

You're not alone if you are talking about a kernel panic? I had one this morning after an update. Ended up reinstalling because i could not get past it. Been at it all day. (Off and on) I got better things to do.

[aiiee]

today. Installed latest patches, including a new kernel. Now my Wubi install of 9.10 goes to Grub editor rather than booting!
It worked fine earlier this morning, now I cannot get in at all. This must be happening to many many others. What do I need to do to fix this latest gaff?

You're not alone if you are talking about a kernel panic? I had one this morning after an update. Ended up reinstalling because i could not get past it. Been at it all day. (Off and on) I got better things to do.



Not a panic. It just dumps me into grub when I try to boot. It's a Wubi install. I bet yours is too. Are those who aren't having problems non-wubi? sheesh. Wubi does not appear to have a menu.lst in /boot/grub. Off to check the Wubi home page. Don't those who maintain these updates test with Wubi? Or is it me? I can't tell...

[vinnywright]

you are not alone.......my system is a regular install (NOT wubi) and the new kernel (vmlinuz-2.6.31-15-generic) is causing wireless and audio problems for me.

fortunetley I have the old kernel's still installed and working just fine :) on the vmlinuz-2.6.31-14-generic now


vinny@desktop:/boot$ ls
abi-2.6.28-11-generic memtest86+.bin
abi-2.6.28-15-generic System.map-2.6.28-11-generic
abi-2.6.31-12-generic System.map-2.6.28-15-generic
abi-2.6.31-13-generic System.map-2.6.31-12-generic
abi-2.6.31-14-generic System.map-2.6.31-13-generic
abi-2.6.31-15-generic System.map-2.6.31-14-generic
config-2.6.28-11-generic System.map-2.6.31-15-generic
config-2.6.28-15-generic vmcoreinfo-2.6.28-11-generic
config-2.6.31-12-generic vmcoreinfo-2.6.28-15-generic
config-2.6.31-13-generic vmcoreinfo-2.6.31-12-generic
config-2.6.31-14-generic vmcoreinfo-2.6.31-13-generic
config-2.6.31-15-generic vmcoreinfo-2.6.31-14-generic
grub vmcoreinfo-2.6.31-15-generic
initrd.img-2.6.28-11-generic vmlinuz-2.6.28-11-generic
initrd.img-2.6.28-15-generic vmlinuz-2.6.28-15-generic
initrd.img-2.6.31-12-generic vmlinuz-2.6.31-12-generic
initrd.img-2.6.31-13-generic vmlinuz-2.6.31-13-generic
initrd.img-2.6.31-14-generic vmlinuz-2.6.31-14-generic
initrd.img-2.6.31-15-generic vmlinuz-2.6.31-15-generic
vinny@desktop:/boot$

;D

@aiiee befor your updats broke the system (wubi) were you using grub?? or as I'v read the windows boot loader??

I dont know eneything about wubi I am just cureus

VINNY

[aiiee]

you are not alone.......my system is a regular install (NOT wubi) and the new kernel (vmlinuz-2.6.31-15-generic) is causing wireless and audio problems for me.

fortunetley I have the old kernel's still installed and working just fine :) on the vmlinuz-2.6.31-14-generic now


vinny@desktop:/boot$ ls
abi-2.6.28-11-generic memtest86+.bin
abi-2.6.28-15-generic System.map-2.6.28-11-generic
abi-2.6.31-12-generic System.map-2.6.28-15-generic
abi-2.6.31-13-generic System.map-2.6.31-12-generic
abi-2.6.31-14-generic System.map-2.6.31-13-generic
abi-2.6.31-15-generic System.map-2.6.31-14-generic
config-2.6.28-11-generic System.map-2.6.31-15-generic
config-2.6.28-15-generic vmcoreinfo-2.6.28-11-generic
config-2.6.31-12-generic vmcoreinfo-2.6.28-15-generic
config-2.6.31-13-generic vmcoreinfo-2.6.31-12-generic
config-2.6.31-14-generic vmcoreinfo-2.6.31-13-generic
config-2.6.31-15-generic vmcoreinfo-2.6.31-14-generic
grub vmcoreinfo-2.6.31-15-generic
initrd.img-2.6.28-11-generic vmlinuz-2.6.28-11-generic
initrd.img-2.6.28-15-generic vmlinuz-2.6.28-15-generic
initrd.img-2.6.31-12-generic vmlinuz-2.6.31-12-generic
initrd.img-2.6.31-13-generic vmlinuz-2.6.31-13-generic
initrd.img-2.6.31-14-generic vmlinuz-2.6.31-14-generic
initrd.img-2.6.31-15-generic vmlinuz-2.6.31-15-generic
vinny@desktop:/boot$

;D

@aiiee befor your updats broke the system (wubi) were you using grub?? or as I'v read the windows boot loader??

I dont know eneything about wubi I am just cureus

VINNY


as I understand it, may be wrong, but it looks like the windows boot loader calls grub. I get the grub boot choices screen ( normally ) when I choose Kubuntu at the windows boot screen. Then, instead of going to the normal grub menu it dumps me into the grub editor. I need to capture the error text and paste it here. Wubi home page was no help.

[vinnywright]

AA well then you nead to read up on grub2 .....you should be abell to find post's on it hear.

and you should be abell to fix it frome the grub screen you'r geting dumped to.....I think I dont know about grub2 yet......all my boxes use legacy grub.

VINNY

[aiiee]

AA well then you nead to read up on grub2 .....you should be abell to find post's on it hear.

and you should be abell to fix it frome the grub screen you'r geting dumped to.....I think I dont know about grub2 yet......all my boxes use legacy grub.

VINNY


so grub2 then. From the looks of things it kind of appears that the windows boot loader passes a kernel name to grub2 and grub2 can't find it because kpackageupdate woofed the kernel update. Soooooo, look at grub2 then to find out what happened to the kernel naming/passing thing, stuff. maybe.

[Qqmike]

aiiee, here's a how-to on GRUB 2, but I wouldn't spend too much time reading it just yet (maybe just scan the Table of Contents). Thing is, you have Wubi, and I have no clue how that works; how you get "inside" the Wubi thing to make surgical corrections. But, anyway, I'm not sure that this is GRUB's fault, but ... fwiw ...

GRUB 2 A Guide for Users
http://kubuntuforums.net/forums/index.php?topic=3106368.0

[aiiee]

fuggit. I'm restoring from backup and making sure I don't have any funky repositories checked in kpackageupdate. If it happens again, I'll worry about it then.

[aiiee]

aiiee, here's a how-to on GRUB 2, but I wouldn't spend too much time reading it just yet (maybe just scan the Table of Contents). Thing is, you have Wubi, and I have no clue how that works; how you get "inside" the Wubi thing to make surgical corrections. But, anyway, I'm not sure that this is GRUB's fault, but ... fwiw ...

GRUB 2 A Guide for Users
http://kubuntuforums.net/forums/index.php?topic=3106368.0



thank you! Not much help on the wubi site that I can find. Windows Boot Loader calls wubildr.mbr, and [big black box here] grub2 is called. feh. This shouldn't have happened.

[aiiee]

[REDACTED] ???

[aiiee]

Ok, from your most excellent guide which I threw away once, yet managed to read the second time it was handed me, I find the following example entry for grub.cfg:

### BEGIN /etc/grub.d/10_Linux ###
menuentry "Ubuntu 8.04.3 LTS, kernel 2.6.24-24-generic" {
set root=(hd1,2)
linux /boot/vmlinuz-2.6.24-24-generic root=UUID=0df17bc5-0056-4ef7-bfca-251194b6eb44 ro quiet splash
initrd /boot/initrd.img-2.6.24-24-generic
}
### END /etc/grub.d/10_Linux ###

so, if the update to the kernel did not rewrite this properly, then grub won't be able to find a kernel, which is what appears to be happening. This is what I will look at next.

[Qqmike]

(aside ... IF you could get booted into Kubuntu and run sudo update-grub, that would automatically update the boot menu (/boot/grub/grub.cfg) to the latest kernels; but ... as I say, the Wubi thing is greek to me; another command for doing the same thing is sudo grub-mkconfig -o /boot/grub/grub.cfg, again run from inside Kubuntu)

[GreyGeek]

OK, here goes. I'm about to reboot...Hopefully I'll be back in a few minutes. <crosses fingers>

Edit: All went well. No problems to report here.


I got notified today, too, and the new kernel updated and runs just fine.

[aiiee]

thx qqmike. The wubi documentation is a bit confusing. The wubi documentation refers to 'grub4dos' being used. I guess that is instead of grub2???? I think I will wait until I finish my backup to get into the os and poke around. I was at a grub command line before and it sure looked like grub2. very confusing. I'm pretty sure I'll be trying your grub-update suggestion soon enough.

[Qqmike]

sounds like you might need a grub4dos tutorial ... should be plenty of those around (google)

[aiiee]

sounds like you might need a grub4dos tutorial ... should be plenty of those around (google)


yes, but the problem is, what is being used, grub4dos or grub2? The wubi documentation looks like it hasnt been updated since 8.10...

[Qqmike]

I really have no idea without studying it, sorry. WAG: Grub4DOS may be passing control to GRUB 2? That's my guess.

[Detonate]

A different problem with the updates. Does anyone else have virtualbox installed? On boot to the -15 kernel I get a bunch of error messages about the vbox drivers and "Performance Counters", the it goes to a CLI Login, with a flashing screen, but won't take a login. I can reboot to the -14 kernel OK.

[GreyGeek]

A different problem with the updates. Does anyone else have virtualbox installed? On boot to the -15 kernel I get a bunch of error messages about the vbox drivers and "Performance Counters", the it goes to a CLI Login, with a flashing screen, but won't take a login. I can reboot to the -14 kernel OK.


That's what I learned to dislike about VitualBox -- the need to recompile the kernel headers when it is installed. Since it is installed specifically for the existing headers subsequent upgrades to a newer kernel fail to boot IF VirtualBox can't recognise the new headers and trigger a recompile. In that case perhaps it would be easier to run the previous kernel, make a backup of your guest OS files, remove VirtualBox, reboot into the new kernel (if it will) and then reinstall VirtualBox, which will rebuild the headers for the new kernel, then reinstall your guest OS files.

[Snowhog]

That's why I like VMPlayer. When a new kernel is installed, it 'recognizes' this and rebuilds the modules it uses when you launch it.

[vinnywright]

A different problem with the updates. Does anyone else have virtualbox installed? On boot to the -15 kernel I get a bunch of error messages about the vbox drivers and "Performance Counters", the it goes to a CLI Login, with a flashing screen, but won't take a login. I can reboot to the -14 kernel OK.


yes I have vbox and the -15 kernel .............the first time I rebooted after installing the -15 kernel and all the rest of the 32 or so updates my wireless wouldent work and I got the (one or more devices on your system are no longer pluged in would you like kde to permenentley forget about them) this is allwase the sound and is allwase a duplacet entry after a kernel upgrade and is safe to click yes forget it.....but I dident

a second boot and the duplacet sound entrey was gone but wirless still a no go.

a therd boot and all was well and I'm on the new kernel now .......at no time did vbox give me eney trouble and I just fired up the 9.10 .ISO with it and it's working ok.

vbox-3.0.8 KDE-4.3.3 kernal-2.6.31-15-generic

VINNY

[skunk]

???

My Karmic install has dkms installed and the vbox* and nvidia modules recompile themselves automatically whenever the kernel is upgraded

[skunk]

In fact, the error message displayed by VirtualBox is

"
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing

‘/etc/init.d/vboxdrv setup’

as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary."

[Detonate]

Yes, no need to completely reinstall virtualbox. I booted to the -14 kernal. edited the correct vboxdrv entry in rc.2 so it would not load, rebooted to the -15 kernel, ran vboxdrv setup, now everything is OK. Also had to recompile my 190 Nvidia driver kernel because updated installed and update to the 185 driver which reinstalled the 185 driver. I forgot to uninstall it.

[aiiee]

I really have no idea without studying it, sorry. WAG: Grub4DOS may be passing control to GRUB 2? That's my guess.



Well fwiw, I did find a way in the Wubi docs to fsck the root.disk file, which is the entire kubuntu installation file . It gave me a file system error which it said there was no way to fix, so I wiped everything and started over, for the third time I think, after kernel panic errors in my last instance. 9.10 / Wubi has not been as stable as 9.04, which is too bad because other than that it is a good improvement over 9.04.

Anyway, thanks for all your help.

[Qqmike]

Thanks for the feedback. Glad you got it "solved."

[sithlord48]

got the kernel update myself yesterday, still starts up correctly. and on top of that dkms handled the upgrading (or recompiling ) of vbox drivers (non ose if that matters) and the ati driver.

@aiiee idk how many people here will know about the in's and outs of the wubi boot process, i think most of us have it installed on a partition. or as the only os on the machine.