Summary: | cardmgr does not seem to run support scripts for wlan-ng | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dan Noe <dpn> |
Component: | Current packages | Assignee: | Peter Johanson (RETIRED) <latexer> |
Status: | RESOLVED WONTFIX | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dan Noe
2003-04-26 03:56:58 UTC
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. |