network fail

Fou · 2009-10-31 04:22:59

Hi,

My network does not work at all. It fail when i start my pc.

In my log files, this is what i can find:

ADDRCONF(NETDEV_UP): eth1: link is not ready

though, i followed the wiki on the network configuration

help ! !

Last edited by Fou (2009-11-01 19:38:08)

Fou · 2009-10-31 04:51:07

please

Last edited by Fou (2009-11-01 19:38:39)

Fou · 2009-11-01 20:09:11

when i do this command

lspci | grep Ethernet

it find two Ethernet controller

is it ok ?

Fou · 2009-11-02 02:56:30

anybody?

My network work or do not work, intermitenttly......I really don't no know what to do ....

fukawi2 · 2009-11-02 04:13:33

Give us more information... Starting with:
1) your network config in rc.conf
2) the output of the following commands:

lspci | grep Ethernet
ip a s

Also, bumping your own post 30 minutes after opening the thread is frowned upon around here. Have a read over the forum etiquette:
http://wiki.archlinux.org/index.php/Forum_Etiquette

Fou · 2009-11-02 22:35:07

fukawi2 wrote:

Give us more information... Starting with:
1) your network config in rc.conf
2) the output of the following commands:
lspci | grep Ethernet
ip a s
Also, bumping your own post 30 minutes after opening the thread is frowned upon around here. Have a read over the forum etiquette:
http://wiki.archlinux.org/index.php/Forum_Etiquette

Sorry for the bumping ! !

2)
02:00.0 Ethernet controller: MArvel Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
05:02.0 Ethernet controller: MArvel Technology Group Ltd. 88E8001 PCI-E Gigabit Ethernet Controller (rev 14)

The #1) come soon, sorry i'm a bit noob and i don't have x server install yet.

thank you

Fou · 2009-11-02 22:40:25

#
# /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"
#
# 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.UTF-8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="America/Montreal"
KEYMAP="us"
CONSOLEFONT=
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=(fuse)

# 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
#
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
lo="127.0.0.1"
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
#
#NET_PROFILES=(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 hal fam)

Thank you

fukawi2 · 2009-11-02 23:11:43

So is it eth0 or eth1 that you use to connect? The error you posted is on eth1, but your rc.conf has eth0 configured.

After you boot, what is the output of:

ip a s
route -n
cat /etc/resolv.conf

Fou · 2009-11-03 01:11:26

fukawi2 wrote:

So is it eth0 or eth1 that you use to connect? The error you posted is on eth1, but your rc.conf has eth0 configured.
After you boot, what is the output of:
ip a s
route -n
cat /etc/resolv.conf

I use eth0

Fou · 2009-11-03 01:25:21

ip a s

command not found. And i don't know it's suppose to do

route -n

192.168.1.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 202 0 0 eth0

cat /etc/resolv.conf

24.200.241.37
24.201.245.77
24.200.243.189

But after the reboot, my network was working fine.So i don't know if this can help. Probably after a couple of reboot, my network will be down again.

fukawi2 · 2009-11-03 01:38:15

Sorry, you need the 'iproute2' package for that first command.

Next time it's not working, post the output of those and we'll see what we can see

brando56894 · 2009-11-03 05:13:36

If its intermittent it might a problem with your DHCP/DNS server or your router and not with your arch install, I could be wrong though.

Fou · 2009-11-03 22:43:33

brando56894 wrote:

If its intermittent it might a problem with your DHCP/DNS server or your router and not with your arch install, I could be wrong though.

It certainly not my router.

Fou · 2009-11-04 01:10:23

fukawi2 wrote:

Sorry, you need the 'iproute2' package for that first command.
Next time it's not working, post the output of those and we'll see what we can see

Ok.. stay tuned.

soggydoggy · 2009-11-04 20:58:35

I had this issue and I had 2 network cards also.

What it seemed to be was assigning Eth0 to one card when it booted up, but then at the next boot it might assign Eth1 to that card and Eth0 to the second one.
Not sure if it's HAL causing the inconsistency or what (don't really know about any of the other hardware detection tools to comment).

In the end I just removed the second NIC out of sheer laziness, but a colleague mentioned something about UDEV and specifying the MAC address of each card in its config somewhere (I think? Wasn't really listening to him as I'd already removed the second NIC).

Sorry if that's a completely different thing to what you have, but though I'd share my 2 penneth.

Cheers!
Soggy.

Arch Linux

#1 2009-10-31 04:22:59

network fail

#2 2009-10-31 04:51:07

Re: network fail

#3 2009-11-01 20:09:11

Re: network fail

#4 2009-11-02 02:56:30

Re: network fail

#5 2009-11-02 04:13:33

Re: network fail

#6 2009-11-02 22:35:07

Re: network fail

#7 2009-11-02 22:40:25

Re: network fail

#8 2009-11-02 23:11:43

Re: network fail

#9 2009-11-03 01:11:26

Re: network fail

#10 2009-11-03 01:25:21

Re: network fail

#11 2009-11-03 01:38:15

Re: network fail

#12 2009-11-03 05:13:36

Re: network fail

#13 2009-11-03 22:43:33

Re: network fail

#14 2009-11-04 01:10:23

Re: network fail

#15 2009-11-04 20:58:35

Re: network fail

Board footer