NIC Not Loading - YAST reports error message

I have tried to load OpenSUSE ver. 11.3 & 11.4 using VMWare Ver. 7.1.4, and have noted that my NIC has failed to get configured properly both times - here is the message that YAST is reporting:

79c970 [PCnet32 LANCE]BusID : 0000:02:01.0

Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details.

This is an onboard NIC - a VIA RHINE II Fast Ethernet Adapter which the OpenSUSE HCL indicates is supported by the default Linux Kernel. The interesting thing is that I have loaded two versions of Ubuntu (10.04 & 11.04), two versions of Centos (5.6 & 6.0), and the SUSE Linux Enterprise 11, and all have loaded the NIC properly with no problem. While I am not a Linux expert, I have worked with UNIX machines for several years (mostly Solaris), so I’m not new to UNIX.

Before I try a previous version, if anyone has any ideas why I am having this issue and how to resolve it that would be quite helpful, as I’m trying to get back to a UNIX type position and my work on all these flavors of Linux has been very helpful, so that is why I would like more experience with OpenSUSE.

I appreciate any help anyone can provide.

Thanks.

Is this error taking place post install
I mean have do you have the OS up and running and you have started Yast > Network Devices > Network Settings?

Did you say you are actually running openSUSE in a VM?

The device you quote, should just work.

On 09/23/2011 11:56 PM, caf4926 wrote:

> Did you say you are actually running openSUSE in a VM?
>
> The device you quote, should just work.

In a VM, you normally use the virtual network device provided by the
virtualization program (KVM, VirtualBox, or VMWare). Access to the real network
of the host is provided with NAT or bridging of that virtual device to the real
network. The choice depends on whether you only want access to the network
outside the host, or if you wish to network multiple VMs. I never want the latter,

I don’t use VMWare or KVM, but network setup for a guest is trivial in
VirtualBox. The only other setup I use is when testing USB wifi devices on the
guest using USB passthru in the host. The guest is then connected directly to my
wifi network.

On 24.09.2011 07:46, gregdes2k11 wrote:
>
> I have tried to load OpenSUSE ver. 11.3& 11.4 using VMWare Ver. 7.1.4,
> and have noted that my NIC has failed to get configured properly both
> times - here is the message that YAST is reporting:
>
> 79c970 [PCnet32 LANCE]BusID : 0000:02:01.0
>
> Unable to configure the network card because the kernel device (eth0,
> wlan0) is not present. This is mostly caused by missing firmware (for
> wlan devices). See dmesg output for details.i

I think that the guest OS installed in the vm may be just right.

Is it possible that you have not included the NIC(s) to its “hardware”.

It’s quite some time ago when I switched from VMWare to Vbox so I can’t
remember clearly how it’s done in VMWare configuration, but normally you
need to configure the virtual machine’s “hardware” including the nic
when you “build” the “machine” like you would in real iron.

When you then install the guest OS it will find the nic like it would in
some real iron.

You can add nics also afterwards to a virtual machine, like you can in
real iron:

Turn off the virtual machine and add the nic(s) in the virtual machine
configuration. Define which card you let it use and which one it will be
(eth0, eth1). See that you get this part right.

Once it’s (they’re) there start the vm.

Then go to YaST and configure the network device(s) there normally.
It should see some very common, known-to-work type of network device(s).

>
> This is an onboard NIC - a VIA RHINE II Fast Ethernet Adapter which the
> OpenSUSE HCL indicates is supported by the default Linux Kernel.

The virtual machine will find the nic the way VMWare represents it to it.

The Virtual machines live “in a perfect world”, that is, if the host OS
can run the hardware, the virtual machine will have suitable
“out-of-the-box-hardware” represented to it.

The nics that the virtual machines think they run are always very much
of compatible, known-to-work types, not the real ones on the real iron
the the host has.

That’s why the VM’s are portable, they can be moved from any machine to
any other that can run the virtual machine host.
And they never have hardware issues because the iron is always the same.

Vahis

http://waxborg.servepics.com
openSUSE 11.2 (x86_64) 2.6.31.14-0.8-default “Evergreen” main host
openSUSE 12.1 Milestone 5 (x86_64) 3.1.0-rc6-2-desktop in VBox
openSUSE 11.4 (i586) 3.0.4-43-desktop “Tumbleweed” in EeePC 900

What do you mean “Failled to get configured?”
It sounds like the virtual NIC is installed in your GuestOS (PCNet32) but it isn’t configured by DHCP for networking, ie IP address, DNS, DG, etc?

If that’s the case, a number of things can cause that, eg

  • On a multi-homed Host, the virtual NIC is bound to the wrong physical NIC
  • Your NIC config type is incorrect (Bridging, NAT, Hosts Only)
  • Virtual Address Network is setup incorrectly (Starting with v7, this changes with every new install)

HTH,
Tony