Prior to a recent emerge -u world, cardmgr would run the linux-wlan-ng support scripts to bring up the device after loading the module. Now, it appears the scripts are not being executed at all. Cardmgr emits two quick beeps when the card is inserted, indicating that the configuration process is immediately completed. The interface is never brought up, and the wlanctl-ng stuff is never done. The module is being loaded correctly. Reproducible: Always Steps to Reproduce: 1. Insert card 2. Driver loads 3. Support scripts don't run. Actual Results: Two quick beeps from cardmgr, no output from scripts. Expected Results: Wireless should have associated with the nearest access point and brought net.wlan0 up. Here is what cardmgr logs when the card is inserted: Apr 26 03:51:16 gryphon cardmgr[28942]: socket 0: NETGEAR MA401RA 11Mbps 802.11 WLAN Card Apr 26 03:51:16 gryphon cardmgr[28942]: product info: "NETGEAR MA401RA Wireless PC", "Card", "ISL37300P", "Eval-RevA" Apr 26 03:51:16 gryphon cardmgr[28942]: manfid: 0x000b, 0x7300 function: 6 (network) Apr 26 03:51:16 gryphon cardmgr[28942]: executing: 'modprobe prism2_cs' Apr 26 03:51:16 gryphon init_module: prism2_cs.o: 0.2.1-pre2 Loaded Apr 26 03:51:16 gryphon init_module: dev_info is: prism2_cs Apr 26 03:51:16 gryphon cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x3c0-0x3df 0x4d0-0x4d7 Apr 26 03:51:16 gryphon cs: IO port probe 0x0380-0x03bf: clean. Apr 26 03:51:16 gryphon cs: IO port probe 0x03e0-0x04cf: clean. Apr 26 03:51:16 gryphon cs: IO port probe 0x04d8-0x04ff: clean. Apr 26 03:51:16 gryphon cs: IO port probe 0x0800-0x08ff: clean. Apr 26 03:51:16 gryphon cs: IO port probe 0x0a00-0x0aff: clean. Apr 26 03:51:16 gryphon cs: IO port probe 0x0c00-0x0cff: clean. Apr 26 03:51:16 gryphon prism2_cs: index 0x01: Vcc 5.0, irq 11, io 0x0100-0x013f
Okay, some additional investigation: I am extremely puzzled. The line below is from wlan-ng.conf, and is definitely being read by cardmgr. If I change the "prism2_cs" to "foo" it fails with an appropriate error message in the logs. However, no matter what I do to change the wlan-ng, nothing happens. cardmgr never reads that, or reads it and ignores it. device "prism2_cs" class "wlan-ng" module "prism2_cs" If I move the wlan-ng.conf file aside so cardmgr uses the orinoco drivers, the orinoco network startup script is executed flawlessly. Apr 26 12:49:12 gryphon cardmgr[18124]: executing: './network start eth1' I am extremely confused. The wlan-ng.conf file is fine.. and I haven't touched it. I've tried remerging wlan-ng and pcmcia_cs countless times, even trying to merge earlier versions (which doesn't work because of the way the wlan-ng ebuild works).
Okay, downgrading to linux-wlan-ng-0.2.1_pre1 but leaving the same pcmcia-cs version fixed the problem. But... I can't figure out why! The only etc-update is to /etc/wlan/shared, ... I don't get it!
I want to second this. I'm having the same problem. orinoco_cs works fine if I rename wlan.conf and restart pcmcia. I can't however get the prism2_cs module to work manually either. I have the exact same card. Dan, where you able to get the wlan-ng drivers working manually?
Good to see someone else is having the same problem! I merged an older version (the one being used before the emerge -u world) like this: emerge /usr/portage/net-wireless/linux-wlan-ng/linux-wlan-ng-0.2.1_pre1.ebuild This fixed the problem, although in a kludgey way.
as this seems to be an error w/ the _pre1 version, marking this as WONTFIX. will be commiting the latest _pre5 soon. _pre5 and _pre4 have had major overhauls though, and i'm unsure of their stability.
