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 ;-)