...I cant access the internet with SuSE 11.0...I run a dual-boot...XP & SuSE 11.0. I can access the www with XP but not SuSE 11.0...My router, nic card, cable all seem/are fine. I took my dual-boot machine and connected to my wifes ethernet connection and the same happen...xp= yes
linux= no.

So apparently when I switched out my old Reltek nic card something went amiss....I have been playing around with Yast and Firewall settings so I might have made the situation worse. After install of new card I was able to receive email and my firewall updated itself...but no Firefox....now, since I changed settings within Yast and Firewall nothing works. I am writing this with a linux live cd/dvd of OpenSuSE 11.2...the www works great with the live cd/dvd but not when I boot into 11.0.

So, should I just scratch my 11.0 install and go with 11.2 ?(but would that clear up my www woes?)...I hate to do that since I just reinstall 11.0 in Jan...or, what do I do to make my 11.0 system see my new/same card?

When I go into Yast | Network Devices | Network Settings I see the new/same adapter but I cant assign a zone (external) to it because I get a message at the bottom of that window that says "Unable to configure the network card because the Kernal device is not present"....I have no idea what this means or where to go for advice. The edit button is greyed out...I dont know how to delete this entry...only the add button is active.

Dhcp-client= installed, dns= installed, driver for nic (I think, but am not sure its installed)

Recap: Wife's ethernet connection xp = y linux = n
My ethernet connection xp = y linux = n
Live CD/DVD linux = y

Thanks for your patience in reading this...thoughts/suggestions?
Sincerely!!! Thanks!

If you have the hwinfo utility installed, run "/usr/sbin/hwinfo --netcard". It should identify your NIC. At the bottom of the output, it should also give you Driver Info. In that section, it will tell you which driver is needed, if the driver is active, and the command to run to load the driver if it isn't active.

but not at the moment...will find and install it.

lshal is installed and probably has lots to say about your network card. Sounds like you're missing a kernel module.

..as a driver...and if I am missing this module how do I get it installed? thanks again!

for business kid...lshal return a wealth of info but sadly no network card. ???
I scanned the info several times...allot about sound card, hard drives, mouse...etc
but no network card...???...not sure what that means.

for bigrigdriver...hwinfo returned the following:

12: PCI 0a.0: 0200 Ethernet controller
[Created at pci.310]
UDI: /org/freedesktop/Hal/devices/pci_10ec_8139
Unique ID: bSAa.IQxIdIhhuH7
SysFS ID: /devices/pci0000:00/0000:00:0a.0
SysFS BusID: 0000:00:0a.0
Hardware Class: network
Model: "Realtek RT8139"
Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
Device: pci 0x8139 "RTL-8139/8139C/8139C+"
SubVendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
SubDevice: pci 0x8139 "RT8139"
Revision: 0x10
I/O Ports: 0xc000-0xc0ff (rw)
Memory Range: 0xcffffe00-0xcffffeff (rw,non-prefetchable)
IRQ: 10 (no events)
Module Alias: "pci:v000010ECd00008139sv000010ECsd00008139bc02sc00i00"
Driver Info #0:
Driver Status: 8139too is not active
Driver Activation Cmd: "modprobe 8139too"
Driver Info #1:
Driver Status: 8139cp is active
Driver Activation Cmd: "modprobe 8139cp"
Config Status: cfg=no, avail=yes, need=no, active=unknown


The problem seems to be two drivers installed...8139cp I believe is for my old card...but not positive...and my new card is 8139too...the question that I cant answer is if I dont know which driver goes with which card "how can I delete both entries, have linux rescan the device and install the proper driver" ??? Isnt this info listed in some file that I can edit???

If I removed the card from my system, would that put a zero value for the network card...and then reinstall it and linux would install the proper driver? Or how do I edit the values/data?

To sort the modules, remove them both with rmmod -f as root.
Then install one and try lspci. If no joy, remove that and try the other.

Once you have found out, tidy the entries in /etc/modprobe.d and put the module you don't want in /etc/modprobe.d/blacklist