Fresh Install Creates Broken Kernel, dist-upgrading From Edgy Works Fine
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubiquity
I'll preface this report by saying that this bug may not be in Ubiquity itself, but is certainly part of the install process:
I found was that my Netgear MA401 wireless card worked fine off the Live CD, but after installing, the kernel would panic if the card was installed when the system was booted. Playing a hunch, I installed Edgy. Everything worked. After dist-upgrading to the latest Feisty, wireless was still working. Finally, I reinstalled Feisty several times from the CDs (I tried Herd 4, 5, and the Beta), and each time the kernel would panic if the card was installed.
Ubiquity, or some other part of the installation process, adds kernel in such a way that PCMCIA and wireless (and perhaps other modules) are broken for many users out of box. At least, I'm assuming is part of the reason why wireless seems to work great for many, but is broken for others. You can find a more detailed description of the specific boot problems in this report:
https:/
Other things I did or noticed:
I used the Alternate Install CD for Herd 5. The kernel was still broken after installation. This leads me to believe some other part of the install process, and not Ubiquity specifically, is at fault.
I installed gnome-network-
My MA401 card (or any other part of the Dell Latitude C640 laptop I was testing) does not require any restricted drivers.
Changed in ubiquity: | |
status: | Incomplete → Confirmed |
I'm mystified; certainly the kernel ought to be the same either way. Could you compare the output of 'COLUMNS=200 dpkg -l | grep ^ii' in the two situations, to check that the same set of packages is installed?