walkeraj
June 16th, 2008, 07:32 PM
Healthy Warning: While there is very little risk of doing anything catastrophic or unreversible to your system by following these instructions, you ARE doing things that are a little outside of the norm by pulling from an older repository and, for all I know, this will make your laptop explode, killing you and everyone who loves you. It works fairly well for me, but your mileage may vary. Caveat emptor.
So, yes. It seems as if the 2.6.24 (Hardy) kernel series is borked and no one knows why. Hopefully this will be remedied in the near future, but it can definitely be annoying given that it's Hardy's default kernel. You can go back to Gutsy, or you can just install the Gutsy kernel/modules (2.6.22) and use those in the meantime.
In order to do this, you'll need to pull them from the gutsy repositories, because 2.6.22 isn't supported in Hardy.
the simplest way to do this is from the commandline:
echo "deb http://us.archive.ubuntu.com/ubuntu gutsy main">/tmp/gutsy.list
sudo mv /tmp/gutsy.list /etc/apt/sources.list.d
sudo apt-get update
sudo apt-get install linux-image-2.6.22-14-generic
sudo apt-get install linux-ubuntu-modules-2.6.22-14-generic
sudo apt-get install linux-backports-modules-2.6.22-14-generic
sudo rm /etc/apt/sources.list.d/gutsy.list
sudo apt-get update
The reason we run apt-get update twice is so that synaptic won't bother you with "updates" from the gutsy repository. If you've made changes to your /boot/grub/menu.lst, it may attempt to overwrite the file with a more generic version. It should be safe to let it, but, before you reboot, you might want to edit the default boot image to your "new" 2.6.22-14 kernel, otherwise you'll have to hit escape every time you boot in order to chose the older kernel. To do this, just issue:
sudo gedit /boot/grub/menu.lst
Ensure that your 2.6.22-14-generic entry reads something like this (except with your UUID):
title Ubuntu 8.04, kernel 2.6.22-14-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx ro quiet splash ec_intr=0
initrd /boot/initrd.img-2.6.22-14-generic
quiet
You'll probably have to add "ec_intr=0" to the end. This kernal option ensures that power management works better on your DarU2. Depending on where the installation places this entry in your menu.lst, you'll need to change the value of "default" (which is towards the beginning of the file) accordingly. Just remember that the entries start at 0, so if your new kernel is the third set of options down, the line should read:
default 2
Restart your machine, and it should boot into the new (but actually older) kernel. Your system should function better, but will include some of the older annoyances like brightness levels that do nothing and maybe some problems with hibernate. The upswing is that you'll be able to remain up-to-date with the rest of Hardy as it moves forward.
Once we actually get a working 2.6.24-series kernel (whenever that may be) you can remove the packages from synaptic or the command line by issuing:
sudo apt-get purge linux-image-2.6.22-14-generic
Which will also uninstall the module packages. In the meantime, until the all-clear is given, I'd avoid taking any kernel updates from synaptic unless you want to test them out. If you take any kernel updates, they'll probably change the value of default in /boot/grub/menu.lst, and you'll have to change it back if you want it to automatically boot into the 2.6.22 kernel.
So, yeah. That will give you a Hardy install with a Gutsy kernel, and it's probably totally unsupportable, but at least it works better, right?
So, yes. It seems as if the 2.6.24 (Hardy) kernel series is borked and no one knows why. Hopefully this will be remedied in the near future, but it can definitely be annoying given that it's Hardy's default kernel. You can go back to Gutsy, or you can just install the Gutsy kernel/modules (2.6.22) and use those in the meantime.
In order to do this, you'll need to pull them from the gutsy repositories, because 2.6.22 isn't supported in Hardy.
the simplest way to do this is from the commandline:
echo "deb http://us.archive.ubuntu.com/ubuntu gutsy main">/tmp/gutsy.list
sudo mv /tmp/gutsy.list /etc/apt/sources.list.d
sudo apt-get update
sudo apt-get install linux-image-2.6.22-14-generic
sudo apt-get install linux-ubuntu-modules-2.6.22-14-generic
sudo apt-get install linux-backports-modules-2.6.22-14-generic
sudo rm /etc/apt/sources.list.d/gutsy.list
sudo apt-get update
The reason we run apt-get update twice is so that synaptic won't bother you with "updates" from the gutsy repository. If you've made changes to your /boot/grub/menu.lst, it may attempt to overwrite the file with a more generic version. It should be safe to let it, but, before you reboot, you might want to edit the default boot image to your "new" 2.6.22-14 kernel, otherwise you'll have to hit escape every time you boot in order to chose the older kernel. To do this, just issue:
sudo gedit /boot/grub/menu.lst
Ensure that your 2.6.22-14-generic entry reads something like this (except with your UUID):
title Ubuntu 8.04, kernel 2.6.22-14-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx ro quiet splash ec_intr=0
initrd /boot/initrd.img-2.6.22-14-generic
quiet
You'll probably have to add "ec_intr=0" to the end. This kernal option ensures that power management works better on your DarU2. Depending on where the installation places this entry in your menu.lst, you'll need to change the value of "default" (which is towards the beginning of the file) accordingly. Just remember that the entries start at 0, so if your new kernel is the third set of options down, the line should read:
default 2
Restart your machine, and it should boot into the new (but actually older) kernel. Your system should function better, but will include some of the older annoyances like brightness levels that do nothing and maybe some problems with hibernate. The upswing is that you'll be able to remain up-to-date with the rest of Hardy as it moves forward.
Once we actually get a working 2.6.24-series kernel (whenever that may be) you can remove the packages from synaptic or the command line by issuing:
sudo apt-get purge linux-image-2.6.22-14-generic
Which will also uninstall the module packages. In the meantime, until the all-clear is given, I'd avoid taking any kernel updates from synaptic unless you want to test them out. If you take any kernel updates, they'll probably change the value of default in /boot/grub/menu.lst, and you'll have to change it back if you want it to automatically boot into the 2.6.22 kernel.
So, yeah. That will give you a Hardy install with a Gutsy kernel, and it's probably totally unsupportable, but at least it works better, right?