Bug#414683: d-i RC2 installation report
Package: installation-reports
Boot method: floppy
Image version: http://people.debian.org/~joeyh/d-
i/images/daily/floppy/
Date: 12.03.2007 20:00-23:40
Machine: Acer Tecra 508T Laptop
Processor:Intel Celeron
Memory:128MB
Partitions: still one NTFS partition (did not get far enough to
overwrite)
Output of lspci -nn and lspci -vnn:
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card: [O]
Configure network: [O]
Detect CD: [ ]
Load installer modules: [E]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]
Comments/Problems: Network was set up automatically by DHCP
The machine could be pinged from inside the network, other PCs in the
same net were able to reach the Internet and the mirrors tried (e.g.
debian.inode.at, ftp.at.debian.org), but I could not download the
Release file.
I tried switching to another console, ifconfig gave me a loopback
device that was up and eth0 (via PCMCIA-Xircom card) that was up and
in the correct subnet with netmask 255.255.255.0
ping and dig are not available in this shell, so I could not find
out, whether I was able to get anywhere :-( I do not know my way
around the sh shell.
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
I tried the daily built floppies as well as the RC2-floppies with the
same result.
I take it there would have been an expert mode, but as I am no
expert, it might not have helped me ...
I am just now downloading the netinstall CD-image out of the daily-
build repository and will give it a new try this evening.
PS: I installed sarge via boot floppies and netinstall on another
laptop some months ago without problems, so I thought i'd be
experienced enough to give etch a try, I just hope the learning curve
is steep :-)
I am still not sure my failure was not due to a misconfigured
network/router but the D-Link DI-524 used usually works fine for me.
greetings
Nikolaus
--
Nikolaus Gaberszig
Reply to: