eth0: interface not found or invalid

crasdf · 2010-04-08 17:46:27

hello everyone
first of all im absolutely new to arch. but i wanna use it cuz its awsome :)

my problem is described through the line in the topic
i've been looking for possible solutions here on the forums and elsewhere but i couldnt find anything that helped me any further with my problem, the error message still stays the same
i have a brand new arch linux installation of the current image and made no changes whatsoever in the config files.
im feeling kinda desperate and am hoping that someone can help me
i will post various files/outputs i read about in other threads to supply information

output of ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:30:B4:00:00:00  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:18 Base address:0x4000 

eth1      Link encap:Ethernet  HWaddr 00:0A:E4:02:81:B0  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:19 Base address:0x4800 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

as you can see eth0 is at least being properly recognized

the output of dmesg | grep eth

Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
eth1: RealTek RTL8139 at 0xe0c04800, 00:0a:e4:02:81:b0, IRQ 19
eth1:  Identified 8139 chip type 'RTL-8101'
eth0: resetting device...
eth0: uploading firmware...
eth0: could not upload firmware ('isl3890')
eth0: islpci_reset: failure
eth0: resetting device...
eth0: uploading firmware...
eth0: could not upload firmware ('isl3890')
eth0: islpci_reset: failure

sadly i cant rhyme on any of that :/
output of lspci is

00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV34GLM [GeForce FX Go 5300] (rev a1)
03:04.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
03:04.1 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
03:04.2 FireWire (IEEE 1394): Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port PHY/Link-Layer Controller
03:04.3 Mass storage controller: Texas Instruments PCI7420/7620 Combo CardBus, 1394a-2000 OHCI and SD/MS-Pro Controller
03:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
03:06.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)

i did also check the REALTEK site in order to find some appropriate drivers, but there are no drivers to be found
instead its the info that the drivers should be built in with the kernel

i edited my rc.locale file with these lines:

dhcpcd -k eth0
dhcpcd -nd eth0

but that didnt lead to success too, just like killing dhcp with --release eth0 and leasing a new ip

last but not least i will post my rc.conf, although its quite standard atm

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK=""
USEDIRECTISA="no"
TIMEZONE="Europe/Berlin"
KEYMAP="de-latin1-nodeadkeys"
CONSOLEFONT="default8x16"
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="myhost"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond)

im willing to work on any possible solution if you guys could help me out on this
regards
crasdf

ewaller · 2010-04-08 18:21:32

I don't have that chip, but I bet you need the firmware. It might be provided by this AUR:

http://aur.archlinux.org/packages.php?ID=23622

Just a guess.

crasdf · 2010-04-09 16:31:10

thanks for the reply
first of all i have to point out that neither WLAN nor LAN is working
the link to the user reps seems to contain firmware for the wireless adaptor
but i'd like to start piece by piece and would be very interested in fixing the normal ethernet first
as the output of ifconfig -a has shown there isnt even a wlan device being listed
im mainly using my laptop in the university which of course has further encrypting than normal wlan that one has at home.
so i would like to get eth0 running so i can at least do a pacman -Syu
any ideas?

ewaller · 2010-04-09 19:52:43

Okay, but:

eth1: RealTek RTL8139 at 0xe0c04800, 00:0a:e4:02:81:b0, IRQ 19
eth1: Identified 8139 chip type 'RTL-8101'
eth0: resetting device...
eth0: uploading firmware...
eth0: could not upload firmware ('isl3890')

The wired NIC is mapped to eth1, and the wireless to eth0.

This is, of course, subject to the whims of HAL unless you create a rule to prevent arbitrary changes in mapping.

Rumor · 2010-04-09 20:03:02

I believe ewaller is correct, eth1 is configured just fine. Try changing these lines in your /etc/rc.conf:

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)

to say

eth1="dhcp"
INTERFACES=(eth1)

then restart your network (/etc/rc.d/network restart) and trying pinging an external site (ping -c 5 www.google.com)

If you get a reply, then you should be good to go.

Last edited by Rumor (2010-04-09 20:03:28)

crasdf · 2010-04-11 22:17:45

ok i solved the problem with the normal ethernet lan.
the 8139too module had to be loaded
its working fine also after pacman -Syu
as soon as i get X and fluxbux running i will turn to the wlan problem

Arch Linux

#1 2010-04-08 17:46:27

eth0: interface not found or invalid

#2 2010-04-08 18:21:32

Re: eth0: interface not found or invalid

#3 2010-04-09 16:31:10

Re: eth0: interface not found or invalid

#4 2010-04-09 19:52:43

Re: eth0: interface not found or invalid

#5 2010-04-09 20:03:02

Re: eth0: interface not found or invalid

#6 2010-04-11 22:17:45

Re: eth0: interface not found or invalid

Board footer