On Tue, Nov 04, 2008 at 05:11:57PM +0100, Thorsten Mühlfelder wrote:
> Hi
> 
> I've got an net5501 wit a lan1641. I'm running a 2.6.27.4 kernel on it,
> but 2 ethernet ports don't work. I've tried to start a dhcpcd on all ports.
> This is the message from syslog:
> Nov  4 16:54:41 (none) dhcpcd[3335]: eth3: ioctl SIOCSIFFLAGS: Device or 
> resource busy
> Nov  4 16:56:15 (none) dhcpcd[3336]: eth1: ioctl SIOCSIFFLAGS: Device or 
> resource busy
> 
> eth1 and eth3 are on the lan1641 PCI board and they get no interrupt:
> root[~]# cat /proc/interrupts 
>            CPU0       
>   0:         23    XT-PIC-XT        timer
>   2:          0    XT-PIC-XT        cascade
>   3:       2006    XT-PIC-XT        serial
>   4:        614    XT-PIC-XT        serial
>   5:          0    XT-PIC-XT        eth5
>   7:     135161    XT-PIC-XT        mfgpt-timer
>   8:          0    XT-PIC-XT        rtc0
>   9:          0    XT-PIC-XT        eth6
>  10:        947    XT-PIC-XT        eth0, eth2
>  11:          0    XT-PIC-XT        eth4
>  12:          0    XT-PIC-XT        eth7
>  14:      24580    XT-PIC-XT        ide0
>  15:          0    XT-PIC-XT        ide1
> NMI:          0   Non-maskable interrupts
> LOC:          0   Local timer interrupts
> SPU:          0   Spurious interrupts
> ERR:          0
> MIS:          0
> 
> But they are present in /sys/class/net/

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

Reply via email to