Ubuntu
linux package

  1. Bug #349314
  2. Comment #140

Comment 140 for bug 349314

Revision history for this message
Tommy Trussell (tommy-trussell) wrote :

I have installed the 2.6.28-14-generic kernel, and so far it is working very well on my ASUS Eee PC 900. SO if anyone is needing confirmation that the kernel works and it fixes the graphics slowdowns in the NBR launcher, YES! It works!

I did have some difficulties installing the package (as Andrew Manson expressed above) but I finally was able to get the package installed. My apologies to everyone who already knows this but it had me stumped for days. SO I'm writing this out hoping it helps someone else.

1) Activate the jaunty-proposed archive as described in https://wiki.ubuntu.com/Testing/EnableProposed -- basically add the following line to the end of /etc/apt/sources.list --

deb http://archive.ubuntu.com/ubuntu/ jaunty-proposed restricted main multiverse universe

2) Update your local package cache using your favorite method (such as "sudo aptitude update").

Note: No matter what I did I did NEVER saw the new kernel proposed as an update to the existing kernel, whether using Synaptic, Aptitude or the "apt-cache policy" command. The only way I could even SEE that the new kernel was available was by searching for it. For example, the terminal command "aptitude search linux-image-generic" showed it was available.

3) Install the kernel explicitly. The easiest method is to use this terminal command:

    sudo apt-get install linux-image-2.6.28-14-generic

4) After installing the kernel, you can undo step 1 -- disable the jaunty-proposed archive by commenting out the line you added in /etc/apt/sources.list --

# deb http://archive.ubuntu.com/ubuntu/ jaunty-proposed restricted main multiverse universe

4) When you reboot, press the Esc key to display the grub boot menu and make sure the new 2.6.28-14 kernel will be the version that gets booted.

Note: Since I have been using experimental kernels I use the "default saved" option in grub so it automatically boots from the last kernel selected. For some reason, after I installed the -14 kernel, it defaulted to the -13 kernel rather than using the -14 version I just installed or the -11 kernel I booted before.

I hope that helps someone who was having as much trouble as I was.