You are not logged in.

Pages: 1

#1 2010-12-19 17:06:56

art84
Member
Registered: 2010-12-05
Posts: 41

up: error fetching interface information: Device not found

Hi

Solved one issue (https://bbs.archlinux.org/viewtopic.php?id=109968), but my adventures continue :)
Now there are other minor issues related to network.

1) The network works fine, but the max. speed which I've reached is ~18 MB/s.
The Gbit link theoretically must sustain 125 MB/s, but practically I think ~80 MB/s (never worked before; supposd this using the formuls 10 x 8 MB/s -  the max sustained speed by a 100 mbps Fast Ethernet connection).
Hoped for at least 50 MB/s.

Do you have some ideas what to do to reach a greater speed? or 18 MB/s is OK and I have not to worry?

2) The second issue: I get "up: error fetching interface information: Device not found" every time I start/restart the network service.
Basically, I get the following:

:: Stopping Network                                                     [DONE]
:: Starting Network                                                     [BUSY]
up: error fetching interface information: Device not found
                                                                        [DONE]

but the notworks works fine.

3) And the 3rd question, a noobish one: where could I find all the messages which are displayed when the Arch linux boots up? (displayed after pressing Power ON button untill the "login" prompt which cleans up the viewport)

Hardware/network configuration: 2 PC connected directly using a patch-cord; 1 Gbit connection; the second PC has a fresh console-based Arch 2010.05, RTL8111DL NIC, using r8169 (also tried r8168) module

Last edited by art84 (2010-12-19 18:00:25)

Offline

#2 2010-12-19 17:39:00

Mr Green
Forum Fellow
From: U.K.
Registered: 2003-12-21
Posts: 5,896
Website

Re: up: error fetching interface information: Device not found

Memory serves me right the scroll key during boot should help [might want to check that]

Mr Green

Offline

#3 2010-12-19 17:58:12

art84
Member
Registered: 2010-12-05
Posts: 41

Re: up: error fetching interface information: Device not found

Thank you, Mr Green
I guess your answer is for the 3rd question ... I've checked and it works like a "pause" button, but only while starting / stopping services (before services it doesn't work).
Anyway, it's not so easy to react. My PC is a 4-cores AMD 620 @ 3.20 GHz + 4 GB RAM and I'm not able to react so quickly. It dispalys technical data for a fraction of a second.
Maybe this info goes to a special file? or could be fetched somehow after it was displayed?

Offline

#4 2010-12-19 18:56:27

skunktrader
Member
From: Brisbane, Australia
Registered: 2010-02-14
Posts: 1,543

Re: up: error fetching interface information: Device not found

https://wiki.archlinux.org/index.php/Di … t_Messages

Offline

#5 2010-12-22 11:33:26

art84
Member
Registered: 2010-12-05
Posts: 41

Re: up: error fetching interface information: Device not found

any ideas about "up: error fetching interface information: Device not found" ?

Offline

#6 2010-12-22 15:23:22

Mr.Elendig
#archlinux@freenode channel op
From: The intertubes
Registered: 2004-11-07
Posts: 4,092

Re: up: error fetching interface information: Device not found

paste your rc.conf and ifconfig -a

Last edited by Mr.Elendig (2010-12-22 15:23:33)

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

Offline

#7 2010-12-22 18:19:30

art84
Member
Registered: 2010-12-05
Posts: 41

Re: up: error fetching interface information: Device not found

eth0      Link encap:Ethernet  HWaddr 00:19:66:xx:xx:xx
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:413 errors:0 dropped:0 overruns:0 frame:0
          TX packets:335 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:50844 (49.6 Kb)  TX bytes:33519 (32.7 Kb)
          Interrupt:26

eth1      Link encap:Ethernet  HWaddr 00:60:97:xx:xx:xx
          inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
          UP 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:21 Base address:0xe800

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)

rc.conf (comments deleted)

...
MOD_AUTOLOAD="yes"
MODULES=()

HOSTNAME="zion"

eth0="eth0 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255"
eth1="eth1 192.168.0.4 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(eth0 eth1 lo)

gateway="default gw 192.168.1.1"
ROUTES=(gateway)

DAEMONS=(syslog-ng network !netfs !sshd crond)
[root@zion etc]# ./rc.d/network restart
:: Stopping Network                                                                                                                                           [DONE]
:: Starting Network                                                                                                                                           [BUSY]
up: error fetching interface information: Device not found
eth0      Link encap:Ethernet  HWaddr 00:19:66:xx:xx:xx
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1970 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1997 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:212236 (207.2 Kb)  TX bytes:220923 (215.7 Kb)
          Interrupt:26

eth1      Link encap:Ethernet  HWaddr 00:60:97:xx:xx:xx
          inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
          UP 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:21 Base address:0xe800

                                                                                                                                                              [DONE]
[root@zion etc]#

Last edited by art84 (2010-12-22 18:23:52)

Offline

#8 2010-12-22 18:38:33

Mr.Elendig
#archlinux@freenode channel op
From: The intertubes
Registered: 2004-11-07
Posts: 4,092

Re: up: error fetching interface information: Device not found

remove lo from INTERFACES

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

Offline

#9 2010-12-22 19:28:14

art84
Member
Registered: 2010-12-05
Posts: 41

Re: up: error fetching interface information: Device not found

Mr.Elendig, thank you a lot
this helped to remove that message ... and I can't remember how "lo" got there smile

there is also a strange network behaviour: sometimes after boot/reboot my eth0 and eth1 are interchanged and don't work ... a reboot normally helps and every NIC takes its correct place and name
some ideas?

Offline

#10 2010-12-22 23:56:16

Mr.Elendig
#archlinux@freenode channel op
From: The intertubes
Registered: 2004-11-07
Posts: 4,092

Re: up: error fetching interface information: Device not found

https://wiki.archlinux.org/index.php/Ud … _Each_Boot

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

Offline

Pages: 1

Board footer

Powered by FluxBB