Wireless: No "wlan0" in new kernel?

Phk

Hi there!

This is a little issue with a wireless PCMCIA card, and the new 2.6.5-r3 kernel.

I have eveything configured properly (i think), and wireless works perfectly in my 2.6.1 kernel. NOW, with 2.6.5, and with equal configurations in the kernel's .config file, the problem is: DHCPCD WLAN0 quits instantly with no error, nor new IP...

The card is correctly detected, i run "cardmgr" after boot, and then "dhcpcd wlan0"... but in 2.6.5 it does nothing..

Where is wlan0 in kernel 2.6.5 ?

I bet this is a simple question

_________________
"# cat /dev/urandom >> /tmp/life"

Evil Dark Archon · Posted: Tue Apr 27, 2004 1:27 am Post subject:

navigate sysfs, most likely its interface name begins with eth, if you convert your system to udev (if you haven't already), you can use a udev rule to change the name from eth* to wlan*, its really pretty simple, here is a sample, SYSFS{address}=(insert MAC address here, you can find it out using udevinfo), NAME=wlan0
_________________
This post has been over explained for newb-informing purposes.

Registered Linux user 347334
Abit AV8-3rd eye, AMD Athlon64 3500+ 90nm, ATI Radeon x850 pro

Phk · Posted: Tue Apr 27, 2004 2:56 am Post subject:

Sorry.......... This might seem VERY stupid, but what is udev? What's that "upgrade" you talked about? It seemed gooood

[]'s
_________________
"# cat /dev/urandom >> /tmp/life"

smart · Guru Joined: 19 Nov 2002 Posts: 455

Well, have a look about udev and decide for yourself on that one. But per se, you don't need it and it makes me feel you would be killing a fly with a modern remake of SDI.
Maybe first verify where your interface went. If it simply doesn't work right now, udev won't mjust make it reappear. All it would od in your case is make it possible to give it the name you are used to.
Just try iwconfig (without interface name) to see if it has a new name. If it's not there somehow your driver is missing or not recognizing your card. You shoudl fix that first. If it has a new name, you might simply want to go on with that instead of performing an organ transplantation of your system for renaming your network device.

brodo · Guru Joined: 15 Apr 2003 Posts: 319

Phk · Posted: Tue Apr 27, 2004 3:50 pm Post subject:

(Well, there is a "eth1" under sysfs.. However, i don't know how to use it!)

Found a possible explanation:
Cardmgr detects my card, but fails to bind (load) module "prism2_cs.o"... This module doesn't exist! (i've searched it everywhere...)

I've selected everything equally in the 2.6.5 tree, but this module is never built... only "orinoco" and others...

What can this be? how can i build "prism2_cs"?

[]'s
_________________
"# cat /dev/urandom >> /tmp/life"

smart · Guru Joined: 19 Nov 2002 Posts: 455

the _cs variants are those for pcmica. Seems you have enabled the chipsets but not their PCMCIA option. So you get pci card drivers, but not hte PCMCIA ones.

Phk · Posted: Wed Apr 28, 2004 10:09 am Post subject:

Yes... I've noticed that already...

But where in the world is (carmen sandiego, lol) prism2_cs.c, so i can build the prism2_cs.o ?
_________________
"# cat /dev/urandom >> /tmp/life"

smart · Guru Joined: 19 Nov 2002 Posts: 455

Ooos, actually verifying with kernel 2.6.5 configs, i found that there is the prism54 module, which is expected to work for both, PCI and PCMCIA cards, given that this driver supports your card at all. Despite it's name it will also serve some 802.11a/b cards. Firmware i guess you have prepared if you need it ?

Phk · Posted: Wed Apr 28, 2004 4:36 pm Post subject:

Nope......
I've built prism54 driver, but cardmgr still tries to load prism2_cs.o

Anyone, please!! Find me a "prism2_cs.o" !!! :cry:

_________________
"# cat /dev/urandom >> /tmp/life"

brodo · Guru Joined: 15 Apr 2003 Posts: 319

smart · Guru Joined: 19 Nov 2002 Posts: 455

Wait a sec, at that point 2 things are involved.

First, try manually (modprobe prism54) if that gives you (any) wireless device. If so and it works, that will be your driver !
If cardmgr wants to load a different driver then, cardmgr is not up to date. There seems to be no orinoco (named) driver in 2.6 series and if that prism54 is like an update or a replacement for wlan-ng, that's perfectly valid and you should upgrade/modify cardmgr (my opinion) otherwise you might try wlan-ng.
If you want to adopt cardmgr to load prism54, first i'd try a simple reemerge/update, otherwise, update /etc/pcmcia, most likeliy the "config" file. YOu know about that one ?

Phk · Posted: Thu Apr 29, 2004 7:44 am Post subject:

4smart: Yes.. I know that conf file.. Thanks for the tip, i'll try this option first today, when i reach my campus!

4frodo: Your a 2 word man (lol)! But hey, if that works, i'll certainly be grateful and thanking you

"I'll be back"

_________________
"# cat /dev/urandom >> /tmp/life"