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

Bug#245136:



Package: installation-reports

Debian-installer-version: 4/17/2004, Official Sarge Root/Boot Network Installation Floppies, from debian.org
uname -a: can't get that far
Date: 4/20/2004, around 3 PM
Method: Boot floppies, DSL from Verizon.net, using .nl mirrors

Machine: Toshiba Satellite A45-S250
Processor: Mobile Pentium 4, 2.8 GHz
Memory: 512 MB
Root Device: IDE, TOSHIBA MK6021GAS 60GB
Root Size/partition table:
/dev/hda1 NTFS 14.6GB (Windows XP)
/dev/hda5 EXT2  150MB (Minimal Slackware)
/dev/hda6 EXT2  300MB (/ for Debian; was also going to do a minimal install)

Output of lspci: can't get that far

Base System Installation Checklist:

Initial boot worked:    [Y]
Configure network HW:   [Y]
Config network:         [Y]
Detect CD:              [N/A]
Load installer modules: [Y]
Detect hard drives:     [Y]
Partition hard drives:  [Y]
Create file systems:    [Y] (installed on pre-partitioned by Partition-Magic partition)
Mount partitions:       [Y]
Install base system:    [N] (this is where it hung)
Install boot loader:    [N]
Reboot:                 [N]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

Hung while trying a download from the 'net.  I think it might have been interference from a wireless Mac in our local network (I had made my notebook wired so Debian could install, but normally it's wireless too).  I don't know how that could happen, but once you rule out the impossible, whatever remains, however unlikely, must be the truth...  Still, why didn't the Debian Installer time-out and restart the wget when it wasn't working?  I know that the network was still working as the Mac was working perfectly fine.

-Michael




Reply to: