You are not logged in.

#1 2010-09-15 19:00:16

stev3
Member
Registered: 2010-09-14
Posts: 13

up: error fetching interface information: device not found

Hello smile

So.... wifi-select blew up. I could connect fine last night, now it wont connect to anything (Authentication fail), or if it does connect... it hasn't, I can't ping anything.


I get this at boot:

:: Starting Network
up: error fetching interface information: Device not found

rc.conf:

wlan0="dhcp"
INTERFACES=(wlan0)

lspci | grep Network

Network Controller: Broadcom Corporation BCM4312 802.11b/g

I installed the b43 drivers

MODULES=( b43 !b43legacy )


thanks big_smile

Offline

#2 2010-09-15 19:23:52

codycarey
Member
Registered: 2009-08-21
Posts: 154

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

After you start up, what does 'ifconfig -a' say?

Offline

#3 2010-09-15 20:06:40

stev3
Member
Registered: 2010-09-14
Posts: 13

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

Sorry for the slow reply,

eth0      Link encap:Ethernet  HWaddr 00:24:81:52:EF:B5  
          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:17 

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)

wlan0     Link encap:Ethernet  HWaddr 00:24:2B:AE:50:C1  
          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)

Offline

#4 2010-09-15 20:11:51

codycarey
Member
Registered: 2009-08-21
Posts: 154

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

And can you manually start it up once you're logged in?

sudo iwconfig wlan0 essid <SSID of your wireless>
sudo ifconfig wlan0 up
sudo dhcpcd wlan0

EDIT: Fixed 'iwconfig'

Last edited by codycarey (2010-09-15 22:22:45)

Offline

#5 2010-09-15 20:36:41

stev3
Member
Registered: 2010-09-14
Posts: 13

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

wlan0: waiting for carrier
timed out

Offline

#6 2010-09-15 20:43:08

codycarey
Member
Registered: 2009-08-21
Posts: 154

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

Did you make sure to set the essid with iwconfig? If you did, make sure that essid actually exists on a network by doing the following:

sudo iwlist wlan0 scan | grep ESSID

That'll give you a list of the ESSIDs being broadcasted.

Offline

#7 2010-09-15 20:44:58

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

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

Interface needs to be up before issuing iwconfig commands.

Offline

#8 2010-09-15 20:52:02

codycarey
Member
Registered: 2009-08-21
Posts: 154

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

tomk wrote:

Interface needs to be up before issuing iwconfig commands.

No, the interface just needs to be recognized by 'ifconfig -a'. You can set the essid with iwconfig regardless of whether it's up or down.

Offline

#9 2010-09-15 21:30:48

stev3
Member
Registered: 2010-09-14
Posts: 13

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

codycarey wrote:

Did you make sure to set the essid with iwconfig? If you did, make sure that essid actually exists on a network by doing the following:

sudo iwlist wlan0 scan | grep ESSID

That'll give you a list of the ESSIDs being broadcasted.

Thanks, the essid is correct though.

The only thing I changed was putting 'wlan0' in the first command

sudo iwconfig wlan0 essid internets
sudo ifconfig wlan0 up
sudo dhcpcd wlan0

Offline

#10 2010-09-15 22:21:48

codycarey
Member
Registered: 2009-08-21
Posts: 154

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

stev3 wrote:

The only thing I changed was putting 'wlan0' in the first command

sudo iwconfig wlan0 essid internets
sudo ifconfig wlan0 up
sudo dhcpcd wlan0

Doh, forgetting the iface was my fault. tongue

By chance is this a new install that you just did last night?

Offline

#11 2010-09-15 22:25:01

stev3
Member
Registered: 2010-09-14
Posts: 13

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

codycarey wrote:
stev3 wrote:

The only thing I changed was putting 'wlan0' in the first command

sudo iwconfig wlan0 essid internets
sudo ifconfig wlan0 up
sudo dhcpcd wlan0

Doh, forgetting the iface was my fault. tongue

By chance is this a new install that you just did last night?

Yeah, pretty much.

It was working for a good few reboots/hours though.

Offline

#12 2010-09-16 12:43:15

stev3
Member
Registered: 2010-09-14
Posts: 13

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

It's weird - I can connect to a few of my neighbour's routers fine, just not mine. My HTC connects fine though.

WPA Authentication/Association Failed

Security is WPA 2 Personal, and the password is correct, I even tried removing it.

So in my profile, could it be something to do with

security="wpa"

?

Maybe drivers?

Offline

#13 2010-09-16 18:38:29

codycarey
Member
Registered: 2009-08-21
Posts: 154

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

Post the output of 'lspci -nnvv' relevant to your wireless and ethernet hardware.

Are the neighbors you're able to connect to using WPA(2) on their networks or are they unsecured?

Offline

#14 2010-09-16 21:21:30

stev3
Member
Registered: 2010-09-14
Posts: 13

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

Thanks for the reply big_smile

01:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
    Subsystem: Hewlett-Packard Company Device [103c:1508]
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 32 bytes
    Interrupt: pin A routed to IRQ 16
    Region 0: Memory at feafc000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: <access denied>
    Kernel driver in use: b43-pci-bridge
    Kernel modules: wl, ssb

02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller [11ab:4354]
    Subsystem: Hewlett-Packard Company Device [103c:361a]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Interrupt: pin A routed to IRQ 42
    Region 0: Memory at febfc000 (64-bit, non-prefetchable) [disabled] [size=16K]
    Region 2: I/O ports at ec00 [disabled] [size=256]
    Capabilities: <access denied>
    Kernel driver in use: sky2
    Kernel modules: sky2

Neighbour's net is unsecured.

Offline

#15 2010-09-18 14:58:58

stev3
Member
Registered: 2010-09-14
Posts: 13

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

Any more ideas guys? sad

Offline

Board footer

Powered by FluxBB