VMWare Network Interface driver needed.
support at expertrepair.co.uk
Wed Apr 2 12:31:14 PDT 2008
Loren Foret wrote:
> What I mean by support tools is the VMware support tools cd. If you look in
> the vmware support directory. ie /usr/local/vmware, you will see several
> .iso images. mount the linux one and install the support tools .tar.gz
> source that's in there. Under your vmware console, click on VM-install
> support tools.
> Hope this helps clear that up.
> Loren Foret
> -----Original Message-----
> From: lfs-support-bounces at linuxfromscratch.org
> [mailto:lfs-support-bounces at linuxfromscratch.org] On Behalf Of Dan Barker
> Sent: Wednesday, April 02, 2008 12:20 PM
> To: 'LFS Support List'
> Subject: RE: VMWare Network Interface driver needed.
> Sent: Wednesday, April 02, 2008 10:03 AM
> To: lfs-support at linuxfromscratch.org
> Subject: VMWare Network Interface driver needed.
> I've moved my [working] LFS 6.3 from real SATA to VMWARE (Server 1.0.4)SCSI.
> I added the BusLogic SCSI support in the kernel and it boots fine.
> However, it can't find eth0.
> lspci says: "Ethernet controller: Advanced Micro Devices [AMD] 79c970
> [PCnet32 LANCE] (rev 10)".
> I've enabled all AMD<anything> I can find in the kernel, and no joy. Anyone
> know how to see the VMWare virtualized NIC?
> The LFS-Live CD sees it fine.
> Dan Barker
> Enabling them in the kernel should have done it. Try installing the support
> tools as they contain source for kernel modules for the PCNET and VLANCE
> Loren Foret
> Lovely word, "should".
> PCNET is enabled.
> LANC does not appear in my .config, on or off, except inside of BALANCE.
> I'm not sure what you mean by "support tools". net-tools, libtool and
> module-iinit-tools are all installed (I was deep into X in blfs before I had
> to move the machine).
> Is there a package I need to install to make VLANCE be there? What? Whatever
> it is, the Live CD doesn't need it. My old Slackware 2.4 doesn't need it.
> dmesg | grep eth shows "eth0: registered as Pcnet/PCI II 79C970A" which is
> encouraging, but the network won't activate ("eth0 not found").
If you have compiled the nic module into the kernel (amd pcnet32 from
memory for vmware workstation edition) then i'm guessing it could be
udev. Udev needs to create the device node and in lfs you set rules to
make the interface name consistent, during lfs you did this in the page:
by creating the rules based on MAC address. Now you have moved LFS from
a real machine to the VM, the MAC address has changed, I believe you are
probably loading the module fine, then not creating the device,
consequently no further operations designed to work on /dev/eth0 are
being carried out. Try recreating the rules for udev and let us know
how you get on.
More information about the lfs-support