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.