public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wojciech Kromer <wojciech.kromer@dgt.com.pl>
To: linux-kernel@vger.kernel.org
Subject: Dual via-rhine on EPIA PD6000E
Date: Mon, 05 Jun 2006 16:26:03 +0200	[thread overview]
Message-ID: <44843EFB.4030704@dgt.com.pl> (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





             reply	other threads:[~2006-06-05 14:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05 14:26 Wojciech Kromer [this message]
2006-06-05 14:28 ` Dual via-rhine on EPIA PD6000E Wojciech Kromer
2006-06-05 14:32 ` Jan Engelhardt
2006-06-06  7:38   ` Wojciech Kromer
2006-06-06 10:06     ` Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44843EFB.4030704@dgt.com.pl \
    --to=wojciech.kromer@dgt.com.pl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox