restricted modules aren't upgraded when kernel is

Bug #28606 reported by Ramon de Ruiter
6
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.15 (Ubuntu)
Wishlist
Unassigned

Bug Description

I've had this issue several times. Most recently when i upgraded from Breezy to Dapper and yesterday Dapper's kernel was upgraded.
It would be nice that when the kernel is upgraded to x.y.z, linux-restricted-modules-x.y.z is also installed. And the previous version should also be uninstalled.

Revision history for this message
TuxInvader (tuxinvader) wrote :

I have experienced the same problem. It would be easily fixed if the installer installed the linux-restricted-modules-<cpu> package, rather than the current kernel version.

On an Athlon box install linux-restricted-modules-k7 rather than linux-restricted-modules-2.6.15-23-k7.

Revision history for this message
Ramon de Ruiter (won) wrote :

Hmm i was going to report that i don't experience this bug anymore. I have install the linux-restricted-modules-<my-arch> package. As tuxinvader mentioned, this package absolutely should be installed by default!

Revision history for this message
Marco Rodrigues (gothicx) wrote :

That works fine at Feisty!

Changed in linux-restricted-modules-2.6.15:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers