error fetching interface information: Device not found

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4781

sefs

26-04-2008 12:47:24

Hi all do these problems have anything with wlan0 not being configured / detected at boot time?

I can see as the lines scroll by

loading restricted drives (one of which is the rt73 daily snap shot from the 25th)
then immediately after that it goes to establishing daily networking

and then returns some error lines about wlan0 and not being able to get interface information...

I have to let the machine boot fully uplug the usb card, and replug then restart network.

You said we don't need this "pre-up ifconfig wlan0 up" anymore in our interfaces file, so for the daily snapshot from the 25th of april can i remove this?

P.S. is there a way to create a script that i can do this manual process automatically until I get a snapshot that works?

That is
1) simulate manually unpluging and re-pluging the usb adapter
2) restarting the network (this part i know what this would look like)

then i can run the script in the sessions startup spot.

Thanks.

Vern

26-04-2008 17:51:14

Hi sefs,

What is your actual failure symptom?

What is a restricted drive?

What happens if you plug the adapter in only after booting?

Thanks,

sefs

26-04-2008 23:23:15

sorry that should be restricted driver...

It looks like in Hardy ... when the rt73 is installed Hardy picks it up as a restricted driver and places it in the restricted driver interface to be enabled or disabled. If disabled ...its blacklisted and will not load... you have to go into the restricted driver interface and enable it and then its good to go.

The problem is the network card somehow is not detected at bootup.
The error lines I see, are

stopping firestarter firewall...
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found

starting firestarter firewall...
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found

and occurs right after I see the starting basic network line.

Therefore when the computer is fully booted the network is offline.

I have to manually unplug the usb adapter and plug it back in ... then the card is detected, and then I have to restart the network with

sudo /etc/init.d/networking restart

and only then do i have the network up and running.

I have to do this each time I start hardy up.

so somehow the between hardy and the driver something is going wrong during the boot process.

Can you elaborate one what you mean by "What is your actual failure symptom?" where can I get information on that to post here.

Thanks.

sefs

27-04-2008 00:06:02

What happens when i plug in after booting is exactly the same error messages as described above....

to be more specific this may give a clue...

these are the lines from the boot screen

.
.
.
something about loading restricted drivers
something about starting basic networking then....

stopping firestarter firewall...
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found

starting firestarter firewall
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found
wlan0 error fetching interface information Device not found
.
.
.

...then the boot process continues into gnome

I log in ... i note that the the device is off line from the network icon displayed in the gnome bar...

I plug it in...the icon changes to denote the card is detected and that it has picked up a wireless network... and then i restart networking so it can connect to that network.

Vern

27-04-2008 02:33:03

Hi sefs,

Thanks for the additional info. I don't have much distro- specific knowledge. What's a "restricted driver"?

It basically looks like the firewall is being set up before the driver module is loaded.

If your system is loading whatever "restricted drivers" are, before setting up firewalling, then maybe the rt73 needs to be a restricted driver.

If it is a restricted driver, does it name itself wlan0?

sefs

27-04-2008 05:41:46

Description of a restricted driver taken from ubuntu wiki
------------------------------------------------------------------
When you install Ubuntu, some Drivers may be required to make the components in your computer work. These Drivers may restrict your rights in some way, or remove functionality from the component. Rather than having to explain what precisely is 'wrong' with the supplied Driver which may well be an extremely technical argument, Ubuntu has chosen to group these Drivers together and call them Restricted Drivers. You are given the choice
to activate these Restricted Drivers, or not. Ultimately it is your choice.

https//wiki.ubuntu.com/RestrictedDrive ... drivers%29

the rt73 is set up to be enabled in the restricted driver manager...so since its there i guess ubuntu has flagged it as a restricted driver and treating it as such. There is one other driver there ... a nvidia driver.

The sequence of things that i see happening on the boot screen is

1) ubuntu loading files needed to boot system
2) ubuntu loading restricted drivers
3) ubuntu setting up basic networking
4) then the errors where the starting and stopping of firewall appears

so it does look as if its set up as a restricted driver and from the boot up process it does look as if its being loaded before the basic networking is started.

Edit
Yes I think it does name itself wlan0 as thats the value i see when i unplug and replug it when fully booted.

I always keep missing your questions at the bottom for some reason. I must be going blind.

Vern

30-04-2008 23:32:16

Hi sefs,

Re your post of Sat 4/26 If you get the same boot symptoms with and without the adapter plugged in, then it would seem that the rt73 module may not being loaded during the restricted driver load sequence. After booting, and before you take any recovery steps, what does "lsmod|egrep rt" say? What does "ifconfig wlan0" say?

As another possibility, are you maybe colliding with the nextgen driver? That is part of the kernel source as of kernel 2.6.24.

Thanks,

sefs

02-05-2008 01:55:45

Thanks for your response... here is that info...

[code21k2hg17]
:~$ lsmod|egrep rt
parport_pc 35108 1
parport 35912 3 ppdev,lp,parport_pc
rtc 13212 0
rt73 215424 0
gameport 14472 2 emu10k1_gp
agpgart 33328 2 nvidia,amd64_agp
usbcore 143724 5 rt73,uhci_hcd,ehci_hcd,ohci_hcd
[/code21k2hg17]

[code21k2hg17]
:~$ ifconfig wlan0
wlan0: error fetching interface information: Device not found
[/code21k2hg17]

/etc/modprobe.d/blacklist
[code21k2hg17]
# causes problems with ndiswrapper
#blacklist rt73
blacklist rt2x00lib
blacklist rt2x00pci
blacklist rt2x00usb
blacklist rt61pci
blacklist rt73usb
blacklist rt2400pci
blacklist rt2500pci
blacklist rt2500usb
blacklist rt2570
blacklist islsm_usb
blacklist islsm_device
blacklist islsm
blacklist ndiswrapper
[/code21k2hg17]

How can I find out what the nextgen driver is and disable it?

fatah

02-05-2008 02:08:08

I don't know if this helps.
last night, i try to use rt73 module from k2wrlz and I've ported to kernel 2.6.25. Due to nature of this module, it will never up, I think. Maybe, because of the interface doesn't has a MAC address before ifup and it can't be triggered with ifup/usb_rtusb_open() before a MAC address is assigned. So, I've changed the flow of the module and you can refer here.

http//fatah.afraid.org/files/rt73-project/

Editted I'm so sorry, I think the compilation will not success until do change on kernel version comparison from 2.6.25 to 2.6.24 in the code (rtmp_main.c), I guess. I only have kernel 2.6.20 and 2.6.25.

Vern

04-05-2008 19:53:24

Hi sefs,

[quote2vn1vu0f]How can I find out what the nextgen driver is and disable it?[/quote2vn1vu0f]The nextgen driver is rt73usb, shown in your copy of /etc/modprobe.d/blacklist. Looks like there's no collisions.

The "error fetching interface information" message is issued if the interface is not physically plugged in. What is the interface name supplied to the rt73 module?

"ifconfig -a" shows all the interfaces in your system, up or down. You might try that and see what shows up.

As an experiment, you could try uncommenting the rt73 module, and commenting out the rt73usb module in /etc/modprobe.d/blacklist and see what happens.

Thanks,

sefs

05-05-2008 12:50:04

ps. the is a ralink file in /etc/modprobe.d created by the rt73 module with the line

[codeqnaadtmz]
alias wlan* rt73
[/codeqnaadtmz]

here is the ifonfig
[codeqnaadtmz]
:~$ ifconfig -a

eth0 Link encap:Ethernet HWaddr 00:16:17:3e:ff:7b
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:20 Base address:0x4000

ham0 Link encap:Ethernet HWaddr 00:ff:a7:7a:26:50
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:500
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:9347 errors:0 dropped:0 overruns:0 frame:0
TX packets:9347 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11405371 (10.8 MB) TX bytes:11405371 (10.8 MB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:c0:00:01
inet addr:192.168.72.1 Bcast:192.168.72.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:c0:00:08
inet addr:172.16.163.1 Bcast:172.16.163.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr 00:08:a1:94:56:bc
inet addr:192.168.1.55 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:62688 errors:0 dropped:0 overruns:0 frame:0
TX packets:30932 errors:0 dropped:9 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:49456670 (47.1 MB) TX bytes:4868068 (4.6 MB)
[/codeqnaadtmz]


Now when i comment out rt73usb and uncomment rt73 I get similar behaviour but this time unplugging and replugging does not help interface stays inactive as if not plugged in. Also the ifconfig reports different names for the wireless interface...see below.

[codeqnaadtmz]
:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:17:3e:ff:7b
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:20 Base address:0x4000

ham0 Link encap:Ethernet HWaddr 00:ff:95:93:a6:84
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:500
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:54 errors:0 dropped:0 overruns:0 frame:0
TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2700 (2.6 KB) TX bytes:2700 (2.6 KB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:c0:00:01
inet addr:192.168.72.1 Bcast:192.168.72.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:c0:00:08
inet addr:172.16.163.1 Bcast:172.16.163.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan1 Link encap:Ethernet HWaddr 00:08:a1:94:56:bc
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)

wmaster0 Link encap:UNSPEC HWaddr 00-08-A1-94-56-BC-00-00-00-00-00-00-00-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)
[/codeqnaadtmz]

Vern

06-05-2008 01:24:22

Hi sefs,

According to what you pasted into your posting, "ifconfig -a" shows that wlan0 is up and that it has transmitted and received plenty of packets. So now I'm really confused as to why "ifconfig wlan0" should give a device not found error.

What happens if you immediately follow "ifconfig -a" with "ifconfig wlan0"?

Thanks,

sefs

07-05-2008 22:37:58

Hi again, that was ifconfig -a after i unplugged and replugged

But now here is ifconfig -a before i do the unplugged replugged

[code2rtnc7qq]
:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:17:3e:ff:7b
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:20 Base address:0x4000

ham0 Link encap:Ethernet HWaddr 00:ff:71:c1:db:54
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:500
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:182 errors:0 dropped:0 overruns:0 frame:0
TX packets:182 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9100 (8.8 KB) TX bytes:9100 (8.8 KB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:c0:00:01
inet addr:192.168.72.1 Bcast:192.168.72.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:c0:00:08
inet addr:172.16.163.1 Bcast:172.16.163.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan1 Link encap:Ethernet HWaddr 00:08:a1:94:56:bc
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)
[/code2rtnc7qq]

should i still go ahead and do the last bit of your thing now that i clarified the above?

Vern

08-05-2008 01:29:30

Hi sefs,

OK. Your "ifconfig -a" shows a driver that thinks it's "wlan1", not "wlan0". Furthermore, there's no driver that does think it's "wlan0". So naturally there will be a "device not found" error if you reference "wlan0".

Since lsmod shows rt73 is loaded, that is probably the driver that thinks it has interface "wlan1". For reasons I don't understand, it seems that unplugging and plugging back in has the effect of getting the name "wlan0" assigned.

Basically, there's a naming mismatch somewhere. You might try checking out if there's an ifname parameter used when the rt73 driver is modprobe'd.

sefs

08-05-2008 04:17:43

How would I do that? *novice here*

p.s. previous to most current driver which now uses /etc/modprobe.d/ralink to store aliases, where were aliases stored?

Vern

08-05-2008 18:21:50

Hi sefs,

Since this is an entirely different problem from what the thread started as, I've split discussion into a new thread.

As far as how to find the interface name problem goes, each distribution has its own ideosyncracies. Hopefully, someone more knowledgeable than I can jump in here.

Thanks,