[gutsy 7.10 tribe 3]: system cant find cdrom modules

Bug #39508 reported by Andrea Veri
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
Colin Watson

Bug Description

i got an error message during ubuntu server flight 6 installation, the messege said :

kernel modules not found ,maybe they are different between the ones you're installing and archive ones

I finished the installation without problems but when i have to use apt-get command to install a package that is inside flight6 cdrom nothing can be done. System ask me to change the cd and put inside the correct one ,i put that inside and i get alwais the same message :

Media change :please insert the disc labeled
ubuntu server 6.06 dapper drake etc

Revision history for this message
Jouni Mettala (jouni-mettala) wrote : Re: Ubuntu Server flight6: system cant find cdrom modules

This is quite old and happening with development version. Could you tell if this is still problem with feisty or some gutsy tribe?

Revision history for this message
Schmirrwurst (schmirrwurst) wrote : gutsy tribe3: system cant find cdrom modules

I have the same problem under gutsy tribe 3
I ve downloaded the kubuntu alternate image and the hdmedia kernel and initrd today

Revision history for this message
Schmirrwurst (schmirrwurst) wrote :

the problem is that the kernel in :
is not the same as the one in the last cd-image from gutsy

it worked using

I think there should be a mechanism so that current, always points to the kernel used in the last cdrom-image, or there should be another link with the name of the cdrom-image...
I think having the last hd-media kernel make no sence, if there is no alternative cdrom image corresponding

Revision history for this message
Colin Watson (cjwatson) wrote :

This is not a problem if you're using the final release. I'm not intending to "fix" this for the development release; it's more important to make it move smoothly than to make it stable at every step, and the two goals are in conflict in this case.

Generally speaking, during a development release the current symlink in the archive will contain an installer image that matches the current *archive* (not necessarily the CD). This may be untrue for short periods of time but generally only measured in hours. Anyone with more stringent stability requirements than that should use a stable release.

Changed in debian-installer:
assignee: nobody → kamion
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments