[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#270599: no help from using a different mirror or using "unstable" version



On Sat, 2004-09-11 at 01:04, Rick_Thomas wrote:
> On Fri, 2004-09-10 at 17:57, Frans Pop wrote:
> > On Friday 10 September 2004 23:04, Rick Thomas wrote:
> > > When it asked, I chose the
> > > uchicago mirror as usual, and it loaded the installer-components
> > > list (I think -- I didn't get the exact words) after which it
> > > *again* complained about not finding any kernel modules!  I told it
> > > to continue anyway, and it started downloading and unpacking
> > > installer components from the uchicago mirror (presumably).
> > 
> > Ignoring this message will mean your installation is always going to fail as 
> > the installer won't recognize your disk.
> > 
> > Missing installer modules probably means you are using an incorrect 
> > distribution on your mirror.
> > You probably need to select 'unstable' instead of using the default 'testing'.
> > 
> > You can do this by backing up to the menu (for example from country-chooser), 
> > changing debconf priority to medium, and then choose 'unstable' when you are 
> > selecting your mirror.
> > 
> > The reason is there are kernel-changes happening ATM and the version the 
> > floppies are build with is probably not yet available in testing.
> 
> Well... these were the 2.4 floppies.  Does that make a difference?
> 
> I'll try it with a different mirror.  That's easy to do.
> 

Well... I tried with "ftp.us.debian.org" as the mirror, and "version to
install" as "unstable"

Same result -- no disks recognized by the kernel, so none to partition.

I tried "save debug logs to floppy".  Per instructions, I fed it a
formatted floppy (Mac [HFS] formatted.  Would PC [FAT] formatted or
Linux [ext2] formatted have been better?) it made a few seconds of
floppy read/write noises then declared that it was "unable to find any
floppy device".  (The use of the word "device" here makes me think that
regardless of the format, I would have had the same results.  Or am I
assuming too much linguistic precision on the part of the person who
wrote that error message?)

After I rebooted into a working system I examined the floppy.  Nothing
had been written to it.

Hope some of this helps!

Rick





Reply to: