You are not logged in.

#1 2011-05-18 04:04:15

gnuub
Member
Registered: 2011-05-17
Posts: 11

Device not found on network start, but recogized in lspci -v

I am admittedly very new to Arch but have read a few threads on similar problems and tried a few things I saw.

When i type the command lspci -v my ADMtek NC100 Network Everywhere Fast Ethernet shows up, says its using the tulip driver.

However, when i type the command /etc/rc.d/network start i get :

^Cup: error fetching interface information: Device not found      with a listing for eth0 and lo, which i can type out full if necessary.

also, when i type iwconfig,    lo, eth0, and eth1 say no wireless connections.

If i have missed something please let me know, i have tried to search google and the forum with little luck. thanks in advance.

Offline

#2 2011-05-18 18:46:52

gnuub
Member
Registered: 2011-05-17
Posts: 11

Re: Device not found on network start, but recogized in lspci -v

So i added eth1 to my interfaces in rc.conf, as eth1 showed up when i typed ifconfig. Now when i boot the computer network does not fail (with no wired internet connected) however i tried pinging google (still not sure what pinging is, just have read people do it to test connections) and still get the unknown host error.

pacman -Syu still fails to update (no servers configured for repository)

Any suggestions or any more information needed?

Last edited by gnuub (2011-05-18 20:30:45)

Offline

#3 2011-05-18 21:24:08

Stebalien
Member
Registered: 2010-04-27
Posts: 1,237
Website

Re: Device not found on network start, but recogized in lspci -v

You need to configure a dns server.
If you are using dhcp, this should be done automatically. If you are not, try adding the following to /etc/resolv.conf:

nameserver 208.67.222.222
nameserver 208.67.220.220

Last edited by Stebalien (2011-05-18 21:26:21)


Steven [ web : git ]
GPG:  327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C
Do not email: honeypot@stebalien.com

Offline

#4 2011-05-19 00:39:16

gnuub
Member
Registered: 2011-05-17
Posts: 11

Re: Device not found on network start, but recogized in lspci -v

Stebalien wrote:

You need to configure a dns server.
If you are using dhcp, this should be done automatically. If you are not, try adding the following to /etc/resolv.conf:

nameserver 208.67.222.222
nameserver 208.67.220.220

I added both of these and got the same result. When typing the command 'ping google.com' it took a while to receive the unknown host error, as if it was connected to something?
Also go the same error as listed above from pacman.

Tried switching eth1 to dhcp and couldnt even get the network to start like i could when listing it as a static ip.

The wireless card does also have an ethernet port in it, could this be the problem? it is registering as the jack instead of the wireless?

The wireless network i am trying to join also has a wep hex code, which I created a profile for in /etc/network.d as instructed by this guide (https://wiki.archlinux.org/index.php/Netcfg) not sure if i did it correctly though.

Thanks for the reply Stebalien.

Offline

#5 2011-05-22 19:05:32

gnuub
Member
Registered: 2011-05-17
Posts: 11

Re: Device not found on network start, but recogized in lspci -v

No one?

Offline

#6 2011-05-22 20:15:54

Stebalien
Member
Registered: 2010-04-27
Posts: 1,237
Website

Re: Device not found on network start, but recogized in lspci -v

Netcfg and the network daemon are completely different. If you want something simple that just works, try installing wicd.


Steven [ web : git ]
GPG:  327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C
Do not email: honeypot@stebalien.com

Offline

#7 2011-05-23 00:44:10

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,804

Re: Device not found on network start, but recogized in lspci -v

I think you are getting the cart before the horse here.

What is the output of ifconfig -a  ??


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#8 2011-05-26 05:45:15

gnuub
Member
Registered: 2011-05-17
Posts: 11

Re: Device not found on network start, but recogized in lspci -v

eth0      Link encap:Ethernet  HWaddr 00:04:5A:52:5B:AE 
          inet addr:192.168.1.101  Bcast:192.168.1.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:22 Base address:0x2000

eth1      Link encap:Ethernet  HWaddr 00:02:55:3B:C0:67 
          inet addr:192.168.1.101  Bcast:192.168.1.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)

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)

Offline

#9 2011-05-26 14:59:28

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,804

Re: Device not found on network start, but recogized in lspci -v

Okay what is wrong with this picture?
Hint: Both of your interfaces (eth0 and eth1)  are configured to the same IP address.  Thats a bad way to try to network.

Tell us a little more about how the addresses are being assigned (Are you defining static addresses?  I cannot believe these addresses came from a DHCP server)
What kind of router are you using?  Are you the administrator of that router?

HWaddr 00:04:5A:xx:xx:xx  is a LinksysG
HWaddr 00:02:55:xx:xx:xx  is an IBM address hmm

I think your wireless is eth0 right now.  I would also bet that eth0 and eth1 are arbitrarily assigned to the wired / wireless at boot and are free to swap at boot time, but we will get back to that later.

Try this.  Please post the output of:
iwlist scan
and of
iwconfig

Also, as an experiment, lets try:
sudo eth0 down
sudo dhcpcd eth1
ifconfig -a

edit: Fixed commands

Last edited by ewaller (2011-05-26 15:00:33)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#10 2011-05-26 15:39:04

gnuub
Member
Registered: 2011-05-17
Posts: 11

Re: Device not found on network start, but recogized in lspci -v

ewaller wrote:

Okay what is wrong with this picture?
Hint: Both of your interfaces (eth0 and eth1)  are configured to the same IP address.  Thats a bad way to try to network.

Tell us a little more about how the addresses are being assigned (Are you defining static addresses?  I cannot believe these addresses came from a DHCP server)
What kind of router are you using?  Are you the administrator of that router?

I have/had very little idea what I was doing so I just tried manually placing the information I found in the "Connection Information" tab from the wireless running on my Fedora Laptop, into rc.conf. I only did this after being unable to get it working using dhcp.

I am using a Linksys router, the WRT160n V3 model and do have administrative access.


ewaller wrote:

HWaddr 00:04:5A:xx:xx:xx  is a LinksysG
HWaddr 00:02:55:xx:xx:xx  is an IBM address hmm

I think your wireless is eth0 right now.  I would also bet that eth0 and eth1 are arbitrarily assigned to the wired / wireless at boot and are free to swap at boot time, but we will get back to that later.

Try this.  Please post the output of:
iwlist scan

I get "Interface doesn't support scanning." for lo, eth0, and eth1.


ewaller wrote:

and of
iwconfig

I get " no wireless extensions." for lo, eth0, and eth1.

ewaller wrote:

Also, as an experiment, lets try:
sudo eth0 down
sudo dhcpcd eth1

for these i get -bash: sudo: command not found.


Thanks for taking the time to help!

Offline

#11 2011-05-26 15:47:41

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,804

Re: Device not found on network start, but recogized in lspci -v

Okay hmm

How about the output of lspci -nn   (that is two n's, not a single 'm')


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#12 2011-05-26 21:55:01

gnuub
Member
Registered: 2011-05-17
Posts: 11

Re: Device not found on network start, but recogized in lspci -v

ewaller wrote:

How about the output of lspci -nn   (that is two n's, not a single 'm')

00:00.0 Host bridge [0600]: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge [8086:1a30] (rev 03)
00:01.0 PCI bridge [0604]: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge [8086:1a31] (rev 03)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 12)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801BA ISA Bridge (LPC) [8086:2440] (rev 12)
00:1f.1 IDE interface [0101]: Intel Corporation 82801BA IDE U100 Controller [8086:244b] (rev 12)
00:1f.2 USB Controller [0c03]: Intel Corporation 82801BA/BAM USB Controller #1 [8086:2442] (rev 12)
00:1f.3 SMBus [0c05]: Intel Corporation 82801BA/BAM SMBus Controller [8086:2443] (rev 12)
00:1f.4 USB Controller [0c03]: Intel Corporation 82801BA/BAM USB Controller #1 [8086:2444] (rev 12)
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801BA/BAM AC'97 Audio Controller [8086:2445] (rev 12)
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV6 [Vanta/Vanta LT] [10de:002c] (rev 15)
02:08.0 Ethernet controller [0200]: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller [8086:2449] (rev 03)
02:0e.0 Ethernet controller [0200]: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 [1317:0985] (rev 11)

Offline

#13 2011-05-26 22:32:40

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,804

Re: Device not found on network start, but recogized in lspci -v

Are you sure that card provides both wired and wireless?  I've never seen one.  Your system does not see it as a wireless card, and I cannot find anything on line to suggest a dual interface.

It appears to me that you have two wired interfaces.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#14 2011-05-26 23:21:04

gnuub
Member
Registered: 2011-05-17
Posts: 11

Re: Device not found on network start, but recogized in lspci -v

The guy who gave it to me told me it was a wireless card and i found a few places online where others were having trouble getting it to work (maybe because its only a wired card). Now i feel like a complete idiot!

Offline

Board footer

Powered by FluxBB