Thorsten Mühlfelder wrote: > OK, here is my dmesg output: > > natsemi dp8381x driver, version 2.1, Sept 11, 2006 > originally by Donald Becker <[EMAIL PROTECTED]> > 2.4.x kernel port by Jeff Garzik, Tjeerd Mulder > natsemi eth0: NatSemi DP8381[56] at 0xa4000000 (0000:01:00.0), > 00:00:24:ca:3c:84, IRQ 10, port TP. > natsemi eth1: NatSemi DP8381[56] at 0xa4001000 (0000:01:01.0), > 00:00:24:ca:3c:85, IRQ 7, port TP. > natsemi eth2: NatSemi DP8381[56] at 0xa4002000 (0000:01:02.0), > 00:00:24:ca:3c:86, IRQ 10, port TP. > natsemi eth3: NatSemi DP8381[56] at 0xa4003000 (0000:01:03.0), > 00:00:24:ca:3c:87, IRQ 7, port TP. > via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker > eth4: VIA Rhine III (Management Adapter) at 0xa0004000, 00:00:24:ca:da:e4, > IRQ 11. > eth4: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000. > eth5: VIA Rhine III (Management Adapter) at 0xa0004100, 00:00:24:ca:da:e5, > IRQ 5. > eth5: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000. > eth6: VIA Rhine III (Management Adapter) at 0xa0004200, 00:00:24:ca:da:e6, > IRQ 9. > eth6: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000. > eth7: VIA Rhine III (Management Adapter) at 0xa0004300, 00:00:24:ca:da:e7, > IRQ 12. > eth7: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000. ^^^^^^^^^^^^ eth4, eth5, eth6, eth7 ^^^^^^^^^^^^^^^^^^^
> > > As I can see now, eth1 and eth3 should have IRQ 7 but in /proc/interrupts > there is only "mfgpt-timer" on this IRQ. I have to check out what this is. > > > Greetings > Thorsten > > On Tue, 4 Nov 2008 11:39:41 -0500 > Mike Chirico <[EMAIL PROTECTED]> wrote: > > >>What's the result of a dmesg? For example, here's the output that I >>get. Maybe the correct modules are not enabled or loaded in the >>Kernel. >> >> >>natsemi dp8381x driver, version 2.1, Sept 11, 2006 >> originally by Donald Becker <[EMAIL PROTECTED]> >> 2.4.x kernel port by Jeff Garzik, Tjeerd Mulder >>natsemi eth0: NatSemi DP8381[56] at 0xa4000000 (0000:01:00.0), >>00:00:24:c9:af:a0, IRQ 10, port TP. >>natsemi eth1: NatSemi DP8381[56] at 0xa4001000 (0000:01:01.0), >>00:00:24:c9:af:a1, IRQ 7, port TP. >>natsemi eth2: NatSemi DP8381[56] at 0xa4002000 (0000:01:02.0), >>00:00:24:c9:af:a2, IRQ 10, port TP. >>natsemi eth3: NatSemi DP8381[56] at 0xa4003000 (0000:01:03.0), >>00:00:24:c9:af:a3, IRQ 7, port TP. >>via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker >>eth4: VIA Rhine III (Management Adapter) at 0x1e100, 00:00:24:c9:a8:64, IRQ >>11. >>eth4: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. >>eth5: VIA Rhine III (Management Adapter) at 0x1e200, 00:00:24:c9:a8:65, IRQ 5. >>eth5: MII PHY found at address 1, status 0x786d advertising 05e1 Link 41e1. >>eth6: VIA Rhine III (Management Adapter) at 0x1e300, 00:00:24:c9:a8:66, IRQ 9. >>eth6: MII PHY found at address 1, status 0x786d advertising 05e1 Link c5e1. >>eth7: VIA Rhine III (Management Adapter) at 0x1e400, 00:00:24:c9:a8:67, IRQ >>12. >>eth7: MII PHY found at address 1, status 0x786d advertising 05e1 Link c5e1. >> >> >>I'm using the following: >> >># uname -a >>Linux 2.6.27.2 #1 Mon Oct 20 09:32:15 EDT 2008 i586 i586 i386 GNU/Linux >> >>The following are set in the kernel config. >> >>CONFIG_VIA_RHINE=y >>CONFIG_NATSEMI=y >> >>Regards, >> >>Mike Chirico >>_______________________________________________ >>Soekris-tech mailing list >>[email protected] >>http://lists.soekris.com/mailman/listinfo/soekris-tech > > _______________________________________________ > Soekris-tech mailing list > [email protected] > http://lists.soekris.com/mailman/listinfo/soekris-tech > > Thorsten, It looks like linux is naming your ethx device as eth4, eth5, eth6, eth7 not eth0, eth1, eth2, eth3 _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
