Am Freitag, 25. Mai 2007 20:48 schrieben Sie: > On Fri, 25 May 2007 17:59:29 +0200, Uwe Bugla wrote: > > Perhaps someone reading this could try to reproduce that problem on his > > machine. > > Now who of the readers owes a Broadcom 4401 NIC and can please try to > > test kernel 2.6.22-rc2-mm1? > > > > Those NICs have been used very very often as onboard controllers, > > especially on ASUS boards. > > I've been using 2.6.22-rc2 for some time and now I compiled 2.6.22-rc2- > mm1 and both work fine with the BCM4401 in my laptop. > > Maxi Hello Maxi, That may be true for your Laptop, but it unfortunately isn't true for my ASUS mainboard onboard controller. Unfortunately I cannot confirm this: My broadcom 4401 driver is not part of a notebook, but instead part of an ASUS P4PE mainboard. At my second attempt I went the conventional path (i. e. ignoring the fact that "Broadcom 4400 ethernet support appears twice in section "Network device support": Whether you leave out "EISA, VLB, PCI and on board controllers" or not it simply appears twice in kernel config! This is bug number 1. Conventional path means: EISA, VLB, PCI and on board controllers Y Broadcom 4400 ethernet support m Broadcom 4400 PCI device support Y This configuration binds: Sonics Silicon Backplane Support m Support for SSB on PCI-bus host SSB PCI core driver This time I do get a "good" interrupt: IRQ 21 for the the device. BUT: Trying to ping another machine fails saying: "destination host unreachable" That means, Although the interrupt is fine now, the device is still not functionable. This is bug number 2. Cheers Uwe P. S.: Michael, Andrew, if you need additional information to resolve that issue please tell / ask me. - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
