Update:

> Pixel wrote:
> > 
> > Pierre Fortin <[EMAIL PROTECTED]> writes:
> > 
> > > the current partition table which should be similar if not identical to how it
> > > looked when 7.0 killed hda1's mbr.
> > 
> > [...]
> > 
> > > /dev/hda1             1        13    104391   82  Linux swap
> > > /dev/hda2   *        14       166   1228972+   6  FAT16
> > 
> > wow, you're telling me windows uses the hda1 MBR to boot!??!!
> > or is that a typo?
> 
> Neither...  I said earlier the problem was on 7.0 and 7.1 was "similar". 
> Remember, 7.1 so badly hosed that laptop that it's gone unused for 98 days; I
> likely deleted the FAT partition in my attempts to restore it 3 months ago.
> 
> I finally got 7.2b3 downloaded and just tried to install on the laptop via
> ftp...  I have a Nat.Semi. NE4100 InfoMover PCMCIA card which works under 7.1
> with ne.o; but b3 can't find the hardware which is at 0x300,3
> 
> DAMN!  Just tried to reboot into 7.1 and got a lot of "[<c0119500>]" type output
> followed by:
>  Code: 8b 4a 04 85 c9 74 22 8b 5a 18 8b 02 89 01 8b 0a 85 c9 74 08
>  Aiee, killing interrupt handler
>  Kernel panic: Attempted to tkill the idle task!
>  In interrupt handler - not synching
> 
> Rebooting, fsck forced on all partitions, BOOM!  Well, looks like 7.2b3 has
> taken another step in the wrong direction...  Just starting the install, only to
> the point of trying to find the ether adapter clobbers the existing system... 
> Looks like network.img is not ready for prime time.

network.img appears to destroy the existing system before even finding a network
adapter.  I've tried my boot floppy (incl. "rescue") and all die after fsck'ing
the partitions; not sure exactly when because when the panic hits, everything
scrolls too fast.  I've tried stepping with xon/xoff; but this gets to the
user/group quota stuff and hangs.  This hang may be due to the clobbered system,
so don't worry about that for now.

Booting grub failsafe...  failed.  Actually, I was trying to read the screen
when it went into non-interactive mode and walked right into the panic.  I think
failsafe should WAIT for input for the user, even to continue.  I'm trying to
restore this system while mailing and browsing; failsafe should not assume
continue until I've decided that's the course of action I wish to take...

pcmcia.img does not see the NE4100 either; I was hoping to avoid cutting CDs for
betas...

The README should be changed from:

  network.img:
          install from ftp/nfs/http
  pcmcia.img:
          install from pcmcia devices

to something like:

  pcmcia.img:
          install from pcmcia devices, including networking.
  network.img:
          install from ftp/nfs/http (non-pcmcia devices)

Pierre

PS:  Can't report this at this time; bugzilla is not responding.

Reply via email to