I recently upgraded Feisty to Gutsy in Kubuntu. It was a pretty rough upgrade. I followed the instructions here:
First, I should describe my hardware. I have a laptop computer from System76. It's the Serval model with an Intel Core2 Duo processor, an NVidia graphics card, 2GB RAM and an 80GB hard drive.
- I had some issues during the upgrade. Adept couldn't update some of the packages. I didn't document exactly what messages that I saw but I remember Adept freezing up once. I also got an error about a problem with the version of a package. I had to go to the command line and use apt-get to finish the updates.
- My next problem was that after rebooting I couldn't get into XFree86. I found an error message in the dmesg log about conflicting versions of the NVidia driver. I had to uninstall and reinstall the NVidia packages. I found information for this at the following URL:
Based on this, I ran the following commands:
- At this point I was able to boot up and log in to the 386 kernel. Now I had 3 kernels in grub and each had a different problem:
sudo apt-get purge nvidia-glx nvidia-kernel-common
sudo aptitude install nvidia-glx
1.Ubuntu 7.10, kernel 2.6.22-14-386 - I could boot and log in but I had the following problems:
a. I had no sound. I was seeing a "no mixer" error in KDE when I hovered the mouse over the volume control.
b. My wireless internet was not working. When I ran "ifconfig" I didn't even see a wireless card available.
c. I was only seeing one processor when I hovered over the battery icon. I used to see 2 since I have the Core2 Duo processor.
2. Ubuntu 7.10, kernel 2.6.22-14-generic - This kernel locked up when I booted. I just saw the Kubuntu logo and a tiny part of the progress bar was completed.
3. Ubuntu 7.10, kernel 2.6.20-16-generic - I couldn't bring up XFree86. I was taken straight to the command line.
I did various web searches and found that others were having similar problems. Based on what I read, I decided to try to get the 2nd kernel working. My understanding is that the 386 kernel wouldn't support my sound card, wireless internet and the 2nd processor but that the generic kernel would.
I tried booting the generic kernel into recovery mode but it just stopped after displaying some USB messages. However, I discovered that after about 5 minutes (!) I would get the following message:
I just ran an "ls" to confirm that the /dev/mapper/ubuntu-root partition was not mounted. I then did some more research and noticed that my ext3 module was not running under this kernel. I ran "modprobe -l" for my 386 and generic kernels and noticed that I had ext3 for the 386 kernel but not for the generic kernel. My configuration for the ext3 module looked the same for the 2 kernels. After doing some more research I ran across this post:
Check root = bootlog cat /proc/cmdline
or missing modules, devices: cat /proc/modules ls /dev
ALERT! /dev/mapper/ubuntu-root does not exist. Dropping to a shell!
Busybox v1.1.3 (Debian 1:1.1.3-5ubuntu7) Build-in shell (ash)
Enter 'help' for a list of built in commands.
This post suggests generating an new initrd image for the kernel. So I used Adept to install yaird and ran the following commands:
After regenerating the kernel image I was able to boot using the generic kernel! Also, the 3 problems that I had with the 386 kernel were all fixed! The only remaining thing that I did was to change my menu.1st file to make the generic kernel the default.
sudo mv /boot/initrd.img-2.6.22-14-generic /boot/initrd.img-2.6.22-14-generic.bk
sudo yaird -o /boot/initrd.img-2.6.22-14-generic 2.6.22-14-generic
The only "problem" that I have now is that I don't see the Kubuntu logo and status bar when I boot up using the generic kernel. I guess that I don't have that in the image that I generated. I'm a geek though so I like seeing the text of what's going on anyway.
I hope that this post can be helpful to anyone else who is having trouble with their upgrade.