Bug#405085: installation-report: Unable to install on Lenovo z61t laptop.
Package: installation-reports
Version: 2.23
Severity: important
-- Package-specific info:
Boot method: network
Image version:
1st try: http://http.us.debian.org/debian/dists/etch/main/installer-amd64/current/images/netboot/netboot.tar.gz dated 2 Nov 06
2nd try:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-businesscard.iso dated 30 Dec 06
Date: 30 Dec 06, 1900 GMT
Machine: IBM Thinkpad Z61t
Partitions:
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [E]
Detect network card: [O]
Configure network: [E]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]
Comments/Problems:
Using AMD64 netboot.tar.gz, boot hangs at the following point:
PCI: Using MMCONFIG at f0000000
ACPI: Subsystem revision 20060127
ACPI: Found ECDT
The system boots using AMD 2.6.18 from the daily build (see above), but
networking doesn't work. There seems to be a bug in the tg3 driver used by the
Broadcom BCM5752m NIC. A CD install would probably work but there seems little
point if networking doesn't work (there is wireless but no WAP at the moment).
The 2.6.15 kernel on Kubuntu 6.06 can use the NIC without problems.
The 2.6.17 kernel on KNOPPIX 5.0.1 also has problems. The card gets an IP from
DHCP but then is non-functional (no packets go out). Running ethtool -t eth0
causes the card to start working again. If the NIC is brought down, the tg3
module must be reloaded, the NIC brought up, and ethtool run again.
During install, no DHCP packets are sent and manually configuring the network
doesn't help.
mii-tool, ethtool, and logs don't show any errors.
Although I don't exactly mind using ethtool as a workaround, it isn't available
during install.
There seem to be several tg3 patches in 2.6.20-rc2 but I'm not sure they relate
to this problem. I would submit a bug against the kernel but I don't have a
Debian live CD to use.
I don't expect anything can be done about this until the kernel is fixed, though
I may try to build d-i with an older kernel (that would have to be i386 since I
don't have an AMD64 machine to build on). Just wanted to document my
experience in case anyone else tries the same thing.
--
Reply to: