Stephen Black wrote:
I have installed Suse Linux on my new computer with a Realtek RTL8111B
ethernet controler.
I have not had any success in connecting to the net and would like to know
if there is a way to test my ethernet port to see if it is compatable with
the OS (which seems likely as SUSE supports 5 other similar chipsets but
mine is not mentioned)
You can check support for PCI devices very easily.
List the PCI bus, noting the address of the device
# lspci
...
02:05.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit
Ethernet (rev 02)
List it again, grabbing the value of the PCI device ID for that address (in
this case 02:05.0).
Each make and model of PCI device has a differing device ID.
# lspci -n
...
02:05.0 0200: 14e4:16a7 (rev 02)
Expand that PCI ID into two 32-bit values, like this:
14e4:16a7 --> 0x000014e4 0x000016a7
Now search your kernel for support for that device
# grep '0x000014e4 0x000016a7' /lib/modules/`uname -r`/modules.pcimap
tg3 0x000014e4 0x000016a7 0xffffffff 0xffffffff 0x00000000
0x00000000 0x0
You can see that this Linux has a tg3 module which supports the PCI device with
device ID 14e4:16a7.
You can check to see if that module got installed:
# lsmod
Module Size Used by
...
tg3 105413 0
and if the module issued any log messages
# dmesg
tg3.c:v3.65 (August 07, 2006)
eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-bit)
10/100/1000BaseT Ethernet 00:00:e2:**:**:**
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[769f4000] dma_mask[64-bit]
PM: Writing back config space on device 0000:02:05.0 at offset b (was 164714e4,
writing 26f1014)
PM: Writing back config space on device 0000:02:05.0 at offset 3 (was 4000,
writing 4008)
PM: Writing back config space on device 0000:02:05.0 at offset 2 (was 2000000,
writing 2000002)
PM: Writing back config space on device 0000:02:05.0 at offset 1 (was 2b00000,
writing 2b00146)
PM: Writing back config space on device 0000:02:05.0 at offset 0 (was 164714e4,
writing 16a714e4)
ADDRCONF(NETDEV_UP): eth1: link is not ready
tg3: eth1: Link is up at 1000 Mbps, full duplex.
tg3: eth1: Flow control is off for TX and off for RX.
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
and if the result was a network interface
# ifconfig -a
...
eth1 Link encap:Ethernet HWaddr 00:00:E2:...
inet addr:... Bcast:... Mask:...
inet6 addr: 2001:388:1:.../64 Scope:Global
inet6 addr: fe80::200:.../64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:62600 errors:0 dropped:0 overruns:0 frame:0
TX packets:14223 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:71110906 (67.8 MiB) TX bytes:1451738 (1.3 MiB)
Interrupt:177
Since yours is not yet attached to anything it won't have a IPv4 or IPv6
address. The traffic counters will be 0.
I don't yet have a broadband account but I have noticed that the phone line
will connect to the ethernet port (RJ45) and I was wondering if I could use
the port to dial into the internet as a temporary measure untill I get some
broadband action happening
Ethernet uses a different set of voltages to the phone network, so this isn't
a good idea. The 802.3 standard which defines Ethernet encourages, but
does not require, interfaces to be resilient to PSTN voltages.
Cheers, Glen
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
