> On Monday 29 August 2005 19:26, Christian Jordan wrote: > > Thanks for answering! I tried something like that already - but there > > were also networking issues (refer to Bug#324011 - sorry for not using > > the same bug number, I'm not really experienced in giving bug reports > > and feedback). > > tg3 should be included again in the 2.6.12 kernel, so that should work. Yes, I thougth so... I tried it (and we have other boards with a broadcom NIC, where it really works fine), but during install I _never_ got a working network connection and afterwards with my own 2.6.12.5-kernel the transfer rate was approx. 0.1-10 kB/s (on a 100MBit network) - seems only to deliver timeouts - response time (ping of a PC on the same switch) went up to 20000ms. Same happens during installation, but the DHCP-Timeout seems to be too low, so I never get a network uplink (also not at the vc2). But I mentioned somewhere already: The Knoppix-DVD (Version 4) also uses tg3 (as far as I remember it's a 2.6.11-kernel) - and there it works without any problem, the DHCP is found within seconds. Strange enough....
> Hmm, I'm confused: what module do you need for the network card? tg3 or > bcm57xx, or are both supported? Usually yes - Broadcom recommends their bcm57xx anyway. > I can't find bcm57xx in the kernel config. Is that is a free driver? If it > is not in the official kernel sources, it will not be included in Debian. The bcm57xx is a driver delivered directly from broadcom, there is also a debian (nonfree-)package for that (unfortunatly it did not work for me, no idea why), but I got the .tgz from broadcom (http://www.broadcom.com/drivers/driver-sla.php?driver=570x-Linux) Now I get the expected/usual performance and response time of the network... > We really need the info from 'lspci' and 'lspci -n' to trace your hardware > detection problems. Can you please send that? Ok, no problem anymore (but without network it is really a hardship) - lspci: 0000:00:00.0 Host bridge: ATI Technologies Inc: Unknown device 5950 (rev 01) 0000:00:01.0 PCI bridge: ATI Technologies Inc: Unknown device 5a3f 0000:00:06.0 PCI bridge: ATI Technologies Inc: Unknown device 5a38 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:19.0 PCI bridge: ALi Corporation M5249 HTT to PCI Bridge 0000:00:1c.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 0000:00:1c.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 0000:00:1c.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) 0000:00:1c.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01) 0000:00:1d.0 0403: ALi Corporation: Unknown device 5461 0000:00:1e.0 ISA bridge: ALi Corporation: Unknown device 1573 (rev 31) 0000:00:1e.1 Bridge: ALi Corporation M7101 Power Management Controller [PMU] 0000:00:1f.0 IDE interface: ALi Corporation M5229 IDE (rev c7) 0000:00:1f.1 RAID bus controller: ALi Corporation: Unknown device 5287 (rev 02) 0000:01:05.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5954 0000:02:00.0 Ethernet controller: Broadcom Corporation: Unknown device 169d (rev 11) 0000:03:15.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) lspci -n: 0000:00:00.0 0600: 1002:5950 (rev 01) 0000:00:01.0 0604: 1002:5a3f 0000:00:06.0 0604: 1002:5a38 0000:00:18.0 0600: 1022:1100 0000:00:18.1 0600: 1022:1101 0000:00:18.2 0600: 1022:1102 0000:00:18.3 0600: 1022:1103 0000:00:19.0 0604: 10b9:5249 0000:00:1c.0 0c03: 10b9:5237 (rev 03) 0000:00:1c.1 0c03: 10b9:5237 (rev 03) 0000:00:1c.2 0c03: 10b9:5237 (rev 03) 0000:00:1c.3 0c03: 10b9:5239 (rev 01) 0000:00:1d.0 0403: 10b9:5461 0000:00:1e.0 0601: 10b9:1573 (rev 31) 0000:00:1e.1 0680: 10b9:7101 0000:00:1f.0 0101: 10b9:5229 (rev c7) 0000:00:1f.1 0104: 10b9:5287 (rev 02) 0000:01:05.0 0300: 1002:5954 0000:02:00.0 0200: 14e4:169d (rev 11) 0000:03:15.0 0c00: 1106:3044 (rev 80) > Also the installation logs would be nice (gzipped please). That would be everything in /var/log/installer? > Are you willing to do further test installs to resolve issues? You will > not need to destroy your current installation; setting up a small (2GB) > partition for testing should do. I plan to buy a 2nd set with the same config (if my employer agrees to pay :-) - then I can "play" a little bit more. But at the moment I have all of the drive used for partitions, and the machine is my working PC, so I cannot reboot it so often (ideally never). But there are good chances, that the new one will come soon ;-) and then I will try to be at your service. > Can we close any of your reports? It would be good to concentrate > information in one report to keep things simple. > If you want to add information to an existing report, just email to: > <bug number>@bugs.debian.org. No problem for me if you close one - it was my mistake that the 2nd one was opened anyway. Best regards, Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
