Arch Linux

General_Tso

Member

Registered: 2012-05-15

Posts: 14

Problem with eth0 in rc.conf after Recent Kernel/glibc Update [solved]

Hello, folks.

I thumbed through the various threads on issues after this recent upgrade, but I haven't found a solution.  I apologize in advance if this as been asked already.

I am running 32-bit Arch inside a VMware VM.  I upgrade per the instructions:

# pacman -Syu --ignore glibc
# pacman -Su

I do have to issue "pacman -Syu --ignore glibc" twice, because the system recommends I upgrade pacman first FWIW.  There are no errors issued, and everything seems to work.  However, when I reboot the system, I get an error telling me I have an unknown interface in rc.conf and I have no connectivity whatsoever.  Nothing seems out of the ordinary in my rc.conf, but I will let you folks be the judge:

# LOCALIZATION
# ------------
HARDWARECLOCK="UTC"
TIMEZONE="America/New_York"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
LOCALE="en_US.utf8"
DAEMON_LOCALE="yes"
USECOLOR="yes"

# HARDWARE
# --------
MODULES=(vmwgfx autofs4)
USEDMRAID="no"
USEBTRFS="no"
USELVM="no"

# NETWORKING
# ----------
HOSTNAME="arch"

interface=eth0
address=
netmask=
broadcast=
gateway=

NETWORK_PERSIST="no"

# DAEMONS
# -------
#
DAEMONS=(syslog-ng dbus alsa open-vm-tools ufw network crond autofs lxdm)

I had planned on trying netcfg anyway, so I tried installing and configuring that before I retried the upgrade.  (I restored a previous snapshot of the VM.)  While switching to netcfg got rid of the rc.conf error, I still had no connectivity.

It seems like everything is alright with /lib itself:

# ls -ld /lib
lrwxrwxrwx 1 root root 7 Jul  7 07:04 /lib -> usr/lib

I am guessing a module or something with the kernel screwed the pooch.  What say you, smart people?

Last edited by General_Tso (2012-12-24 02:30:42)

tweed

Member

Registered: 2011-03-18

Posts: 21

Re: Problem with eth0 in rc.conf after Recent Kernel/glibc Update [solved]

EXACT same issue here. running 32bit in VMware.  eth0 not recognized. ifconfig shows only lo.
During boot: "unknown interface ... ... eth0"
thanks.

Last edited by tweed (2012-07-19 23:50:37)

basementcat

Member

Registered: 2009-02-25

Posts: 10

Re: Problem with eth0 in rc.conf after Recent Kernel/glibc Update [solved]

I am not running on VMware, but the problems that you´ve mentioned also appear  in my system.

Last edited by basementcat (2012-07-20 00:11:49)

tweed

Member

Registered: 2011-03-18

Posts: 21

Re: Problem with eth0 in rc.conf after Recent Kernel/glibc Update [solved]

https://bbs.archlinux.org/viewtopic.php?id=145307

Guessing we'll get this sorted shortly.
no fix i believe base on the above link though prior to finding it
I wondered if VMware player allows other NIC types like VBox does.

So far I'm not finding any way to change the NIC type in VMware player.

tweed

Member

Registered: 2011-03-18

Posts: 21

Re: Problem with eth0 in rc.conf after Recent Kernel/glibc Update [solved]

http://communities.vmware.com/message/1820791

added the line right after the other ethernet0 lines in the YourVMname.vmx file in vmware data folder somewhere on your host PC:
ethernet0.virtualDev = "vmxnet3"

which supposedly changes the NIC to an e1000

all well now.

[BELOW: re-writing for the second time what appear not to have been saved. my error.]

on vbox it would be done through the GUI by changing the net card / NIC.

Last edited by tweed (2012-07-20 04:41:19)

General_Tso

Member

Registered: 2012-05-15

Posts: 14

Re: Problem with eth0 in rc.conf after Recent Kernel/glibc Update [solved]

http://communities.vmware.com/message/1820791

added the line right after the other ethernoet0 lines in the YourVMname.vmx file in vmware folder somewhere on your host PC:
ethernet0.virtualDev = "vmxnet3"

which supposedly changes the NIC to an e1000

all well now.

That did it!  Thanks, tweed!