Hello,
I just compiled 2.6.25-rc1 so I could use my wireless card (ID 148f:257=
3 Ralink Technology, Corp. RT2501USB Wireless Adapter). With 2.6.25-rc=
1 when I plug it in I don't get any error messages like I did with 2.6.=
24. When I plug it in I get the following in /var/log/messages:
=46eb 13 19:06:31 (none) kernel: usb 1-1: new full speed USB device usi=
ng ohci_hcd and address 3
=46eb 13 19:06:31 (none) kernel: usb 1-1: configuration #1 chosen from =
1 choice
=46eb 13 19:06:31 (none) kernel: usb 1-1: New USB device found, idVendo=
r=3D148f, idProduct=3D2573
=46eb 13 19:06:31 (none) kernel: usb 1-1: New USB device strings: Mfr=3D=
1, Product=3D2, SerialNumber=3D0
=46eb 13 19:06:31 (none) kernel: usb 1-1: Product: 802.11 bg WLAN
=46eb 13 19:06:31 (none) kernel: usb 1-1: Manufacturer: Ralink
=46eb 13 19:06:31 (none) kernel: phy0 -> rt2x00_set_chip: Info - Chipse=
t detected - rt: 1300, rf: 0002, rev: 0002573a.
=46eb 13 19:06:31 (none) kernel: usbcore: registered new interface driv=
er rt73usb
However no rt73usb device is created. Why isn't this working? =20
Thanks,
_________________________________________________________________
Climb to the top of the charts!=A0Play the word scramble challenge with=
star power.
http://club.live.com/star_shuffle.aspx?icid=3Dstarshuffle_wlmailtextlin=
k_jan
On Fri, Feb 15, 2008 at 03:27:51PM -0500, Adam Turk wrote:
>
> > You need to enable KMOD. Otherwise you must manually preload
> > the relevant modules.
>
> I thought that was what udev was for? Anyway I recompiled with KMOD enabled and I have partial success. I nolonger get any errors when I plug in my wireless card.
No udev provides auto-loading for device drivers of e.g., PCI
devices. KMOD loads things like network protocols or crypto
algorithms that are not device-backed.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
On , [email protected] wrote:
> On Thu, Feb 14, 2008 at 10:49:34AM +0100, Ivo Van Doorn wrote:
>> Hi,
>>
>>> phy0: Failed to initialize wep
>>
>> I see this message popping up more frequently lately.
>>
>> Do any of the mac80211 people know when and why mac80211 fails to
>> load the wep module? Is there some dependency missing for mac80211?
>
> I don't know, but it seems like there must be something like that.
> It might be helpful to post the .config for the failing kernel?
We have also seen that modprobe sometimes do not resolve all the
dependecies. What works when we get this error is to load the following
modules manually before loading the wifi driver.
blkcipher aes arc4 ecb cryptomgr crypto_algapi
Reinette
On Thu, Feb 14, 2008 at 03:31:51PM +0100, Johannes Berg wrote:
>
> call to fail? We're doing
>
> select CRYPTO
> select CRYPTO_ECB
> select CRYPTO_ARC4
>
> which afaik should be fine.
Yes I think so too. Could you forward me the complete config
file please?
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
On Thu, Feb 14, 2008 at 10:49:34AM +0100, Ivo Van Doorn wrote:
> Hi,
>
> > phy0: Failed to initialize wep
>
> I see this message popping up more frequently lately.
>
> Do any of the mac80211 people know when and why mac80211
> fails to load the wep module?
> Is there some dependency missing for mac80211?
I don't know, but it seems like there must be something like that.
It might be helpful to post the .config for the failing kernel?
Thanks,
John
--
John W. Linville
[email protected]
On Fri, Feb 15, 2008 at 03:27:51PM -0500, Adam Turk wrote:
>
> > You need to enable KMOD. Otherwise you must manually preload
> > the relevant modules.
>
> I thought that was what udev was for? Anyway I recompiled with KMOD enabled and I have partial success. I nolonger get any errors when I plug in my wireless card.
> dmesg says:
> usbcore: registered new interface driver rt73usb
>
> I do a ifconfig rt73usb up and I get a device not found.
> I do a ifconfig -a and see the card is called wlan0 and wmaster0.
> So there is a disparity having somewhere. wlan0 or rt73usb? Which is it?
wlan0
--
John W. Linville
[email protected]
> You are completely missing the point of the concept "modules",
> the module rt73usb is intended to support devices with the rt73 chips=
et.
>
> The rt73usb driver registers the device and creates an network interf=
ace
> inside the kernel. This interface is visible to you as user. The name=
of this
> interface is wlan, depending on the number of wireless network cards =
in
> your system the interface number is attached to it so in your case wl=
an0.
Yep, I could be missing the concept of modules entirely. =20
The driver I was using before had the interface name of rt73. When I s=
ee=20
usbcore: registered new interface driver rt73usb
I think the interface name is rt73usb. Maybe change the line to read=20
usbcore: registered new interface driver rt73usb using name wlan0
so there is no confusing us newbies. =20
Thanks,
_________________________________________________________________
Need to know the score, the latest news, or you need your Hotmail=AE-ge=
t your "fix".
http://www.msnmobilefix.com/Default.aspx
On Fri, Feb 15, 2008 at 9:08 PM, Adam Turk <[email protected]> wrote:
>
> > You are completely missing the point of the concept "modules",
> > the module rt73usb is intended to support devices with the rt73 chipset.
> >
> > The rt73usb driver registers the device and creates an network interface
> > inside the kernel. This interface is visible to you as user. The name of this
> > interface is wlan, depending on the number of wireless network cards in
> > your system the interface number is attached to it so in your case wlan0.
>
> Yep, I could be missing the concept of modules entirely.
>
> The driver I was using before had the interface name of rt73. When I see
>
> usbcore: registered new interface driver rt73usb
> I think the interface name is rt73usb. Maybe change the line to read
> usbcore: registered new interface driver rt73usb using name wlan0
> so there is no confusing us newbies.
You are mixing module name with whatever resource this module provides.
"usbcore: registered new interface driver rt73usb" simply means that
an "interface driver" called rt73usb (the module name) has registered
some device name (wlan0 in your case) with the "usbcore" subsystem.
As simple as that!
Luis Correia
rt2x00 project admin
> Do any of the mac80211 people know when and why mac80211
> fails to load the wep module?
No.
> Is there some dependency missing for mac80211?
Not as far as I can tell.
Herbert, has anything recently changed in the crypto code that would
cause a
crypto_alloc_blkcipher("ecb(arc4)", 0, CRYPTO_ALG_ASYNC)
call to fail? We're doing
select CRYPTO
select CRYPTO_ECB
select CRYPTO_ARC4
which afaik should be fine.
johannes
On Friday 15 February 2008, Adam Turk wrote:
>
> > You are completely missing the point of the concept "modules",
> > the module rt73usb is intended to support devices with the rt73 chipset.
> >
> > The rt73usb driver registers the device and creates an network interface
> > inside the kernel. This interface is visible to you as user. The name of this
> > interface is wlan, depending on the number of wireless network cards in
> > your system the interface number is attached to it so in your case wlan0.
>
> Yep, I could be missing the concept of modules entirely.
>
> The driver I was using before had the interface name of rt73. When I see
> usbcore: registered new interface driver rt73usb
Seriously, I wonder with what driver you managed to pull that off.
As far as I know there is no rt73 driver that registers an interface called rt73.
Neither the Ralink drivers, the rt73 legacy driver or the rt73usb driver ever
did such a thing.
Granted the name did change. The Ralink driver and early legacy drivers
did create the interface with the name "rausb", this is still not the same
as "rt73".
Additionally:
> usbcore: registered new interface driver rt73usb
Using a different rt73 driver would also produce this line (replacing rt73usb
with rt73 or whatever the name of the driver was).
But like I said earlier, I know of no rt73 driver that registered a network
interface named rt73. It is either "wlan" or "rausb". Unless off course you
edited the /etc/modprobe.conf file to load the driver with the rt73 interface name,
but that can be considered "user configuration".
Ivo
> From: [email protected]
>> On Wed, 2008-02-13 at 20:14 -0500, Adam Turk wrote:
>
>> However no rt73usb device is created. Why isn't this working?
>
> Network devices don't have corresponding device nodes under /dev. The=
y
> can be seen with "ifconfig -a", and the wireless properties can be
> examined and changed with iwconfig.
>
> The messages may be different because you changed the debug level or
> because the device is not brought up by some reason. By the way, it's
> better to examine kernel messages with the dmesg command, because is
> shows all messages, whereas syslog can suppress some of them.
Ok. nothing listed in ifconfig -a. Here is the dmesg output. Still t=
he same error message as 2.6.24.
drivers/usb/core/inode.c: creating file '002'
usb 1-1: New USB device found, idVendor=3D148f, idProduct=3D2573
usb 1-1: New USB device strings: Mfr=3D1, Product=3D2, SerialNumber=3D0
usb 1-1: Product: 802.11 bg WLAN
usb 1-1: Manufacturer: Ralink
hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0002
rt73usb 1-1:1.0: usb_probe_interface
rt73usb 1-1:1.0: usb_probe_interface - got id
phy0 -> rt73usb_validate_eeprom: EEPROM recovery - NIC: 0xffef
phy0 -> rt73usb_validate_eeprom: EEPROM recovery - Led: 0xe000
phy0 -> rt73usb_validate_eeprom: EEPROM recovery - RSSI OFFSET BG: 0x00=
00
phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 1300, rf: 0002, =
rev: 0002573a.
phy0: Selected rate control algorithm 'pid'
phy0: Failed to initialize wep
phy0 -> rt2x00lib_probe_dev: Error - Failed to initialize hw.
rt73usb: probe of 1-1:1.0 failed with error -12
usbcore: registered new interface driver rt73usb
What is wrong with thing?
Thanks,
_________________________________________________________________
Climb to the top of the charts!=A0Play the word scramble challenge with=
star power.
http://club.live.com/star_shuffle.aspx?icid=3Dstarshuffle_wlmailtextlin=
k_jan
On Wed, 2008-02-13 at 20:14 -0500, Adam Turk wrote:
> However no rt73usb device is created. Why isn't this working?
Network devices don't have corresponding device nodes under /dev. They
can be seen with "ifconfig -a", and the wireless properties can be
examined and changed with iwconfig.
The messages may be different because you changed the debug level or
because the device is not brought up by some reason. By the way, it's
better to examine kernel messages with the dmesg command, because is
shows all messages, whereas syslog can suppress some of them.
--
Regards,
Pavel Roskin
> You need to enable KMOD. Otherwise you must manually preload
> the relevant modules.
I thought that was what udev was for? Anyway I recompiled with KMOD en=
abled and I have partial success. I nolonger get any errors when I plu=
g in my wireless card. =20
dmesg says:
usbcore: registered new interface driver rt73usb
I do a ifconfig rt73usb up and I get a device not found.
I do a ifconfig -a and see the card is called wlan0 and wmaster0.
So there is a disparity having somewhere. wlan0 or rt73usb? Which is =
it?
Thanks,
=20
_________________________________________________________________
Need to know the score, the latest news, or you need your Hotmail=AE-ge=
t your "fix".
http://www.msnmobilefix.com/Default.aspx
Hi,
> phy0: Failed to initialize wep
I see this message popping up more frequently lately.
Do any of the mac80211 people know when and why mac80211
fails to load the wep module?
Is there some dependency missing for mac80211?
Ivo
>> The driver I was using before had the interface name of rt73. When I=
see
>> usbcore: registered new interface driver rt73usb
>
> Seriously, I wonder with what driver you managed to pull that off.
> As far as I know there is no rt73 driver that registers an interface =
called rt73.
> Neither the Ralink drivers, the rt73 legacy driver or the rt73usb dri=
ver ever
> did such a thing.
>
> Granted the name did change. The Ralink driver and early legacy drive=
rs
> did create the interface with the name "rausb", this is still not the=
same
> as "rt73".
>
> Additionally:
>> usbcore: registered new interface driver rt73usb
>
> Using a different rt73 driver would also produce this line (replacing=
rt73usb
> with rt73 or whatever the name of the driver was).
> But like I said earlier, I know of no rt73 driver that registered a n=
etwork
> interface named rt73. It is either "wlan" or "rausb". Unless off cour=
se you
> edited the /etc/modprobe.conf file to load the driver with the rt73 i=
nterface name,
> but that can be considered "user configuration".
Ok. Upon further investigation the name was rausb0. The rt73 was setu=
p in /etc/modprobe.conf. So is the name going to be wlan0 from now on?
The short version:
I am stuck on a project where the last guy setup everything, didn't doc=
ument anything, and left. I am now trying to figure all of this stuff =
out. I am stuck using Slackware. A hybrid of 9 and 10. I am a Fedora=
user so very little is where I except it to be. I am trying to figure=
everything out and move to centos with a 2.6.24.x kernel (needed for t=
he new hardware this monstrosity of an application is moving to). =20
Thanks,
_________________________________________________________________
Climb to the top of the charts!=A0Play the word scramble challenge with=
star power.
http://club.live.com/star_shuffle.aspx?icid=3Dstarshuffle_wlmailtextlin=
k_jan
On Friday 15 February 2008, Adam Turk wrote:
>
> > You need to enable KMOD. Otherwise you must manually preload
> > the relevant modules.
>
> I thought that was what udev was for? Anyway I recompiled with KMOD enabled and I have partial success. I nolonger get any errors when I plug in my wireless card.
> dmesg says:
> usbcore: registered new interface driver rt73usb
>
> I do a ifconfig rt73usb up and I get a device not found.
> I do a ifconfig -a and see the card is called wlan0 and wmaster0.
> So there is a disparity having somewhere. wlan0 or rt73usb? Which is it?
You are completely missing the point of the concept "modules",
the module rt73usb is intended to support devices with the rt73 chipset.
The rt73usb driver registers the device and creates an network interface
inside the kernel. This interface is visible to you as user. The name of this
interface is wlan, depending on the number of wireless network cards in
your system the interface number is attached to it so in your case wlan0.
Ivo