Skip to contentSkip to conversation

Dual via-rhine on EPIA PD6000E

DISCUSSION Wojciech Kromer 2 participants 5 messages Jun 5, 2006 – Jun 6, 2006

lore
Share & tools
lore
#0 lore raw

Hi. I have two differnent via-rhine on EPIA board. Second one is now working on my 2.6.15 kernel.

Why there are different io adresses in lspci dmesg and ifconfig? Any idea why it's not working???

Here are some additional info:

#lspci -v
...
0000:00:0f.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 8b)
Subsystem: VIA Technologies, Inc.: Unknown device 0106
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at d000 [size=256]
Memory at de000000 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] Power Management version 2
....
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev
74)
Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded
Ethernet Con
troller on VT8235
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at e400 [size=256]
Memory at de002000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2

#ifconfig

eth0 Link encap:Ethernet HWaddr 00:40:63:DB:86:85

         inet addr:192.168.6.156  Bcast:192.168.6.255  Mask:255.255.255.0
         inet6 addr: fe80::240:63ff:fedb:8685/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:2323562 errors:0 dropped:0 overruns:0 frame:0
         TX packets:474569 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:3145097604 (2.9 GiB)  TX bytes:98221200 (93.6 MiB)
         Interrupt:10 Base address:0xe000

eth1 Link encap:Ethernet HWaddr 00:40:63:DB:86:88
UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:11 Base address:0x4000

#dmesg
...
...
eth0: VIA Rhine III at 0xde000000, 00:40:63:db:86:85, IRQ 10.
eth0: MII PHY found at address 1, status 0x7869 advertising 05e1 Link 41e1.
ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
eth1: VIA Rhine II at 0xde002000, 00:40:63:db:86:88, IRQ 11.
eth1: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000
.....

PS now second cable is disconnected, but there was a link on eth1 too

#1 lore raw
Quoted 2 lines

Hi. I have two differnent via-rhine on EPIA board. Second one is *NOT* working on my 2.6.15 kernel.

#2 lore raw
In reply to Wojciech Kromer
Quoted 2 lines

Why there are different io adresses in lspci dmesg and ifconfig?

There is a difference between ioports and iomem.

/proc/iomem:
cfffc000-cfffcfff : 0000:00:04.0
cfffc000-cfffcfff : sis900
/proc/ioports:
d400-d4ff : 0000:00:04.0
d400-d4ff : sis900
ifconfig:
eth1 Link encap:Ethernet HWaddr 00:0A:E6:98:ED:D7

          Interrupt:201 Base address:0xd400 
Quoted 1 line

Any idea why it's not working???

"Not working" is vague. No packet transmission even though the link is active?

Quoted 2 lines

I/O ports at e400 [size=256]
Memory at de002000 (32-bit, non-prefetchable) [size=256]

^^ ioports vs iomem!

Jan Engelhardt

#3 lore raw
Quoted 4 lines

There is a difference between ioports and iomem.

Of course I know, but look at this:

# cat /proc/ioports
d000-d0ff : 0000:00:0f.0
 d000-d0ff : via-rhine
e400-e4ff : 0000:00:12.0
 e400-e4ff : via-rhine
# cat /proc/iomem  de000000-de0000ff : 0000:00:0f.0
 de000000-de0000ff : via-rhine
de002000-de0020ff : 0000:00:12.0
 de002000-de0020ff : via-rhine

from ifoconfig:
eth0: Interrupt:10 Base address: *0xe000*
eth1: Interrupt:11 Base address: *0x4000* <<is it I/O or mem ???

Quoted 3 lines

"Not working" is vague. No packet transmission even though the link is active?

#mii-tool
eth0: negotiated 100baseTx-FD flow-control, link ok
eth1: negotiated 100baseTx-FD flow-control, link ok

Huh! Now it started. But it's first time from four days. Before it i had no frames received.

#4 lore raw
Quoted 10 lines
Quoted 2 lines

There is a difference between ioports and iomem.

Of course I know, but look at this:

# cat /proc/ioports
d000-d0ff : 0000:00:0f.0
d000-d0ff : via-rhine
e400-e4ff : 0000:00:12.0
e400-e4ff : via-rhine
Quoted 8 lines
# cat /proc/iomem  de000000-de0000ff : 0000:00:0f.0
de000000-de0000ff : via-rhine
de002000-de0020ff : 0000:00:12.0
de002000-de0020ff : via-rhine

from ifoconfig:
eth0: Interrupt:10 Base address: *0xe000*
eth1: Interrupt:11 Base address: *0x4000* <<is it I/O or mem ???

ioport.
ioports only go up to 0xffff, and iomem does not normally start below 0xffff.

0x4000 and 0xe000 look strange though (they don't match /proc/ioports).

Jan Engelhardt