Ah -- moving the firmware to /lib/firmware seems to have helped.
modprobe -v says the driver is loaded, and so does insmod.
Everythig shows up in Yast as it should now -- excep tthe wlan0
interface. I will keep tryng. Thanks for th ehelp so far.
On Fri, 11 Mar 2005 07:46:49 +0100, steve
On Friday 11 March 2005 00:22, Ken Schneider wrote:
On Thu, 2005-03-10 at 18:09, Ken Schneider wrote:
On Thu, 2005-03-10 at 16:12, Andrew Brown wrote:
I have run into the sand trying to get a opci wireless card to work under suse 9.1. It is a dlink 520+, with an acx100 chipset, and correclty identified by yast2. Thats to say, when I ask t to identify a network card, it does so, correctly. But then I would expect there to be an interface, like wlan 0 and this just doesn't appear.
Googling around shows lots of struff about ndisdrivers; YOU suggests downloading a script to dowlnoad the acx100 drivers. I have done this. I have run the script. Still no dice. I have tried modprobe -v acx100_pci. I get silence.
After reading for the third time, if you get silence when loading a module that usually means it was successful. After doing the modprobe do lsmod and see if the module was loaded. If it was try to configure using YaST again.
Our Dlink card expects the firmware in /lib/firmware. It's a 111 but maybe the 100 expects it to be there too.
Maybe worth a try. Steve.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Andrew Brown What I do: www.darwinwars.com What I'm up to: www.thewormbook.com/helmintholog/