Mailinglist Archive: opensuse (3666 mails)

[Ken Schneider <suse-list@xxxxxxxxxxxxx>]

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. I put the windows firmware into a
> directory, changed all the lower-case extension to BIN, and tried
> again. Still absolutely nothing.
> 
> I can't begin to work out what isn't happenig, or what is. Can anyone help?
> 

Haven't used the d-link but will try to suggest compared to what I did
with the linksys.

Since you are able to download the driver using YOU make sure you use
the correct name when doing modprobe it may not be acx100_pci. Since I
don't have this card I can't check the name and what you used may be
correct.

When I installed the driver for the linksys card I mounted the driver
CD, did a cd /media/cdrom and then did ndiswrapper on the .inf file.
Next step is to load the ndiswrapper module: modprobe ndiswrapper. I was
then able to see the wlan0 entry using YaST and configure the card.
ndiswrapper --help will show the options available to save the
configuration (module info) for when you reboot. There is also good docs
under /usr/share/doc/packages/ndiswrapper


-- 
Ken Schneider
UNIX  since 1989, linux since 1994, SuSE  since 1998

* Only reply to the list please*

 "The day Microsoft makes something that doesn't suck is probably
  the day they start making vacuum cleaners." -Ernst Jan Plugge