upgrade to hardy didn't install linux-ubuntu-modules for -386 kernel

Bug #203295 reported by Jerome Lacoste
8
Affects Status Importance Assigned to Milestone
linux-ubuntu-modules-2.6.24 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

(Somewhat similar to 151283)

1. upgrade to hardy
2. reboot. i386 kernel selected by default (why ? but this is another problem)
3. no SMP (obvisouly), but worse: no sound, no wireless,...

Installing linux-ubuntu-modules-2.6.24-12-386 (through linux-image-386) solves the problem.

For info, linux-ubuntu-modules-2.6.24-generic are properly installed during upgrade.

Revision history for this message
Brian Pontarelli (brian-pontarelli) wrote :

Had the exact same problem. It seems as though Hardy upgrade is selecting the wrong kernel. My guess is that you had a number of kernels installed on your system. I had about 20 or so going back to 2.6.18 days or before. After I upgraded to Hardy my system was only configured (insmod, initramfs, ldconfig, etc) for the 386 kernel, which is almost completely useless on a desktop/laptop system.

The solution I found was to follow these steps:

1. Uninstall all my old kernels including 2.6.24.12-generic but level the 386 kernels installed (in case these go horribly wrong, 386 will almost always boot).

2. Uninstall linux-generic, linux-image-generic, linux-headers-generic, linux-restricted-*, etc.

3. Re-install all of the latest generic using this command:

sudo apt-get install linux-generic

What this does is to re-install, re-configure and re-compile a working generic kernel. After I rebooted and selected that kernel, I was able to get into linux fine and then re-install all my other restricted drivers. Sound, video, networking all work decently well. After things are running smoothly, you can safely remove all the 386 packages.

This is really, really critical to fix for the full release because non-technical users will be completely lost since they usually have no clue what a kernel is and how to install and configure them. I'd make this a blocker for release if I were the Ubuntu team.

Let me know if you you need logs or files from my system. I'll wait a week or so before making and huge changes in case you need something.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Just curious if anyone has tried upgrading to Intrepid and if this issue still exists?

Changed in linux-ubuntu-modules-2.6.24:
status: New → Incomplete
Revision history for this message
Ralph Janke (txwikinger) wrote :

Is this symptom still reproducible in 9.04 and 9.10 beta?

Revision history for this message
Brian Pontarelli (brian-pontarelli) wrote :

I haven't done the same upgrade on those versions, so I can't tell you. I would assume that if the upgrade is working for anyone it is fixed.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-ubuntu-modules-2.6.24 (Ubuntu) because there has been no activity for 60 days.]

Changed in linux-ubuntu-modules-2.6.24 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.