Hello SuSE people, Running SuSE 10.0 AMD 64 bit. Have an MSI K8T Neo2 MB with a built in ethernet adaptor. Going to add a D-Link DI 604 router to the system so I can add my wife's computer to my new DSL connection. How do I figure out what this onboard ethernet chip is so I can configure it. Read the MB manual several times and there is no clue as to what it is. Yast does not see it and the list that Yast supplies to choose from is huge. I tried guessing at a couple of them with no luck. Can't access the router. Bob S.
On Monday 13 February 2006 9:55 pm, Bob S wrote:
Hello SuSE people,
Running SuSE 10.0 AMD 64 bit. Have an MSI K8T Neo2 MB with a built in ethernet adaptor. Going to add a D-Link DI 604 router to the system so I can add my wife's computer to my new DSL connection.
How do I figure out what this onboard ethernet chip is so I can configure it. Read the MB manual several times and there is no clue as to what it is. Yast does not see it and the list that Yast supplies to choose from is huge. I tried guessing at a couple of them with no luck. Can't access the router.
Look in the MB manual under mainboard specs (at the front of the manual, at least it is for my MSI K8TM). There should be a LAN section that lists the chip, mine is VIA VT8237. According to the MSI site, you have the same chipset... http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID=... Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-21.10-default x86_64 SuSE Linux 9.3 (x86-64)
On Tue, 2006-02-14 at 00:55 -0500, Bob S wrote:
Hello SuSE people,
Running SuSE 10.0 AMD 64 bit. Have an MSI K8T Neo2 MB with a built in ethernet adaptor. Going to add a D-Link DI 604 router to the system so I can add my wife's computer to my new DSL connection.
How do I figure out what this onboard ethernet chip is so I can configure it.
lspci or lspci -v should tell you all you need to know Hans
Bob S wrote:
How do I figure out what this onboard ethernet chip is so I can configure it. Read the MB manual several times and there is no clue as to what it is. Yast does not see it and the list that Yast supplies to choose from is huge. I tried guessing at a couple of them with no luck. Can't access the router.
That board has a VIA VT8237 chipset - according to the VIA website, this includes a PHY called VT6103 - but only for 10/100, not 1000. A little googling seems to suggest the via-rhine driver should work - did you try that? For GigE I would try the Realtek 8139 driver - that's what the MSI website says. /Per Jessen, Zürich
On Tuesday 14 February 2006 05:13, Per Jessen wrote:
Bob S wrote:
How do I figure out what this onboard ethernet chip is so I can configure it. Read the MB manual several times and there is no clue as to what it is. Yast does not see it and the list that Yast supplies to choose from is huge. I tried guessing at a couple of them with no luck. Can't access the router.
That board has a VIA VT8237 chipset - according to the VIA website, this includes a PHY called VT6103 - but only for 10/100, not 1000. A little googling seems to suggest the via-rhine driver should work - did you try that? For GigE I would try the Realtek 8139 driver - that's what the MSI website says.
Hello, Thanks to all who replied. As Scott suggested I looked at the board specs. It is listed as a Realtek 8110S Dual layout. I had tried the via-rhine driver before asking for help. After getting this info I then tried the Realtek 8139. No go on that either. Must have something to do with the way I have the card configured. Have never: ever tried to set up any type of network thing before. All brand new to me. The router is supposedly 192.168.0.1 If I type that into Konqueror I get this message: An error occurred while loading http://192.168.1.0: Could not connect to host 192.168.1.0. If I go to a Konsole as root and type in ifconfig eth0 192.168.1.10 netmask 255.255.255.0 up, I get this: EasyStreet:/ # ifconfig eth0 192.168.1.10 netmask 255.255.255.0 up SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCSIFNETMASK: No such device eth0: unknown interface: No such device Have looked at every /etc/ file that I can think of and am still lost. Bob S
Bob S wrote:
specs. It is listed as a Realtek 8110S Dual layout. I had tried the via-rhine driver before asking for help. After getting this info I then tried the Realtek 8139. No go on that either.
OK, try the Realtek 8169 driver instead then. If still no go, send us the output from "lspci".
Must have something to do with the way I have the card configured. Have never: ever tried to set up any type of network thing before. All brand new to me.
Forget the configuration - when the driver isn't loaded yet, there's nothing to configure. /Per Jessen, Zürich -- http://www.spamchek.com/ - managed anti-spam and anti-virus solution. Let us analyse your spam- and virus-threat - up to 2 months for free.
On Wednesday 15 February 2006 08:38, Per Jessen wrote:
Bob S wrote:
specs. It is listed as a Realtek 8110S Dual layout. I had tried the via-rhine driver before asking for help. After getting this info I then tried the Realtek 8139. No go on that either.
OK, try the Realtek 8169 driver instead then. If still no go, send us the output from "lspci".
Hello, Yast doesn't list the 8169 driver, only the 8129/8139, Spent over 4 hours googling for the 8169 driver this afternoon. Available for all flavors of Windoz and a few sites had it for Linux but were only for the 2.4 kernel. Some guys made a patch for it to work in 2.6 but I really don't want to get into that. EasyStreet:/ # lspci 00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] 00:0f.0 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV36.2 [GeForce FX 5700] (rev a1) EasyStreet:/ #
Afraid I am going to have to go buy a card. Correct? Someone reccomend one that will "just work" in 10.0? Bob S.
Bob S wrote:
Yast doesn't list the 8169 driver, only the 8129/8139,
Dunno about YaST, but I've got a 10.0 system with kernel 2.6.13-15.7-default and one of the gigabit drivers is: "Realtek 8169 gigabit ethernet support" I can load the module : "modprobe r8169", but I as don't have such a card, well :-)
the 2.4 kernel. Some guys made a patch for it to work in 2.6 but I really don't want to get into that.
It's already there. You may have to upgrade your kernel - YOU will do that for you, if necessary. Try this: modprobe r8169 - post the last few lines of dmesg
EasyStreet:/ # lspci [snip]
I don't understand - I saw no mention of any network controllers in that listing??
Afraid I am going to have to go buy a card. Correct?
There's something odd about your built-in NIC not showing up on lspci - are you sure the NIC is enabled in the BIOS? If it's not on lspci, there isn't much YaST (nor anyone else) can do. /Per Jessen, Zürich -- http://www.spamchek.com/ - managed anti-spam and anti-virus solution. Let us analyse your spam- and virus-threat - up to 2 months for free.
On Thursday 16 February 2006 06:28, Per Jessen wrote:
Bob S wrote:
First, I did a lot of cutting and rearranging of your message for clarity.
There's something odd about your built-in NIC not showing up on lspci - are you sure the NIC is enabled in the BIOS? If it's not on lspci, there isn't much YaST (nor anyone else) can do.
Duh....... You were correct. Hidden in the bowels of the bios I found that the lan was turned off. Turned it on and the proceeded with what you suggested.
Yast doesn't list the 8169 driver, only the 8129/8139,
Dunno about YaST, but I've got a 10.0 system with kernel 2.6.13-15.7-default and one of the gigabit drivers is:
OK, I have the same kernel.
"Realtek 8169 gigabit ethernet support"
I can load the module : "modprobe r8169", but I as don't have such a card, well :-)
OK, I did that and I can see it in /proc/modules
modprobe r8169 - post the last few lines of dmesg
OK, here the first look at dmesg: ip_tables: (C) 2000-2002 Netfilter core team r8169: eth0: link up eth0: no IPv6 routers present r8169: eth0: link down r8169: eth0: link up r8169: eth0: link up eth0: no IPv6 routers present r8169: eth0: link down r8169: eth0: link up r8169: eth0: link up CSLIP: code copyright 1989 Regents of the University of California PPP generic driver version 2.4.2 eth0: no IPv6 routers present EasyStreet:/ # I then had to turn the computer off for awhile. When I booted it up again I ran dmesg again. This is what I got the second time: (about half way down)
hub 2-0:1.0: 2 ports detected r8169 Gigabit Ethernet driver 2.2LK loaded ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 16 (level, low) -> IRQ 185 eth0: Identified chip type is 'RTL8169s/8110s'. eth0: RTL8169 at 0xffffc2000001ef00, 00:11:09:62:99:fc, IRQ 185 ACPI-0212: *** Warning: Device is not power manageable Another 60 or 70 lines further down I found this: r8169: eth0: link up And another 25 or so lines down, this: (about 25 lines from the end) eth0: no IPv6 routers present Soooo. Not sure where I stand now. Still can't see the router. If I type in the address 192.168.0.1 in Konqueror I get this: An error occurred while loading http://192.168.0.1/: Could not connect to host 192.168.0.1. Is there any other way to see if the ethernet port is open/working?? Bob S.
On Friday 17 February 2006 00:23, Bob S wrote:
Duh....... You were correct. Hidden in the bowels of the bios I found that the lan was turned off. Turned it on and the proceeded with what you suggested.
At this point, Bob, YaST can see... and /should/ recognize... the built-in NIC, in which case you should drop the CLI diagnostics and experiments and let YaST detect then configure it.
OK, I did that and I can see it in /proc/modules
If the nic isn't configured, yet, I suspect having the module loaded during the detection routine *may* confuse YaST and cause configuration to fail. I'd unload that module (modprobe -r, I believe) before configuring the adapter with YaST.
OK, here the first look at dmesg:
ip_tables: (C) 2000-2002 Netfilter core team r8169: eth0: link up eth0: no IPv6 routers present r8169: eth0: link down r8169: eth0: link up r8169: eth0: link up eth0: no IPv6 routers present r8169: eth0: link down r8169: eth0: link up r8169: eth0: link up CSLIP: code copyright 1989 Regents of the University of California PPP generic driver version 2.4.2 eth0: no IPv6 routers present EasyStreet:/ #
The IPv6 messages are informational only. But it looks like the module is trying to establish a connection but can't, probably because the config files are wrong or not created yet (you still haven't configured it with YaST.)
I then had to turn the computer off for awhile. When I booted it up again I ran dmesg again. This is what I got the second time: (about half way down)
hub 2-0:1.0: 2 ports detected r8169 Gigabit Ethernet driver 2.2LK loaded ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 16 (level, low) -> IRQ 185 eth0: Identified chip type is 'RTL8169s/8110s'. eth0: RTL8169 at 0xffffc2000001ef00, 00:11:09:62:99:fc, IRQ 185 ACPI-0212: *** Warning: Device is not power manageable
Another 60 or 70 lines further down I found this:
r8169: eth0: link up
And another 25 or so lines down, this: (about 25 lines from the end) eth0: no IPv6 routers present
Soooo. Not sure where I stand now. Still can't see the router. If I type in the address 192.168.0.1 in Konqueror I get this:
An error occurred while loading http://192.168.0.1/: Could not connect to host 192.168.0.1. Is there any other way to see if the ethernet port is open/working??
The hardware is being detected during boot so you're almost there. Run YaST to write the config files... accept the defaults... and you should be good to go. regards, Carl P.S. Good call, Per! No sign of the hw in lspci = check the bios ;-)
On Friday 17 February 2006 01:38, Carl Hartung wrote:
At this point, Bob, YaST can see... and /should/ recognize... the built-in NIC, in which case you should drop the CLI diagnostics and experiments and let YaST detect then configure it.
If the nic isn't configured, yet, I suspect having the module loaded during the detection routine *may* confuse YaST and cause configuration to fail. I'd unload that module (modprobe -r, I believe) before configuring the adapter with YaST.
The IPv6 messages are informational only. But it looks like the module is trying to establish a connection but can't, probably because the config files are wrong or not created yet (you still haven't configured it with YaST.)
The hardware is being detected during boot so you're almost there. Run YaST to write the config files... accept the defaults... and you should be good to go.
P.S. Good call, Per! No sign of the hw in lspci = check the bios ;-)
Thanks Carl & Per. Your help/suggestions/instructions got this thing going for me. Had a little trouble with DNS after I got the router recognized but Yast set that straight for me. Thanks again, Bob S.
participants (5)
-
Bob S
-
Carl Hartung
-
Hans du Plooy
-
Per Jessen
-
Scott Leighton