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? -- Andrew Brown What I do: www.darwinwars.com What I'm up to: www.thewormbook.com/helmintholog/
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
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. -- 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
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.
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/
On Fri, 11 Mar 2005 08:48:48 +0000, Andrew Brown
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.
Nope. Rebooting doesn't help at all. stil get "no interface found". Balls, this is like Windows, but without the fun. -- Andrew Brown What I do: www.darwinwars.com What I'm up to: www.thewormbook.com/helmintholog/
On Friday 11 March 2005 09:48, Andrew Brown wrote:
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.
Good. You are nearly there. Next, try: /usr/lib/hotplug/firmware and are you sure it's not the 111 firmware you need? Steve.
OK. It' s finally working. Here's what I had to do, for the eye of google.
there are two problemss, the first is that the card doesn't come with
drivers, and the linux pcx100_pci drivers are complicated to unpack
and to get working. I think I may have very briefly got them working
for a moment yesterday, but then I reverted ndiswrappers, becasue
there was very good googleable information here:
http://nextgen.no-ip.org/~andrew/ndiswrapper/index.html
but the ndiswrappers that come with 9.1 have two problems. They won't
fit updated kernels, and they won't get loaded automatically. So it's
all a little more complicated than it should be.
What you need do is to install ndiswrappers from yast.
Then run YOU, which will offer to update them; accept.
Once you have the updated ndiswrappers, copy over the WinXP drivers
for the card into a linux folder created for the occasion. Make sure
that anything named *.bin is renamed to *.BIN
"sudo ndiswrappers -i /path/to/the/windows/drivers"
"ndiswrappers -l" should reply that there is a module (gplus, in my case)
"ndiswrappers -m" to tell modprobe what to do
"modprobe ndiswrappers" installs the drivers.
rcnetwork restart should show a wlan0 interface.
You may even get everything working at this point. But, since this is
LInux, there is one hideous pitfall waiting still. As soon as you
reboot, the thing will stop working. The command "modprobe
ndiswrappers" has to be repeated on every boot. What I did was to put
it into the /etc/boot.local file to ensure that the damn thing was
started before almost everything else.
Other things might have worked.
But now I can do what I had planned all along, which is to take the
machine into the cellar, switch it on, and leave it there,
administered from my office. But I have learnt enough about Linux
networking to realise there's one more step I whoudl take for y
sanity. Once the thing ids working donw there, I shall brick up the
entrance to the cellar door, in case I am tempted to fiddle with it
again.
On Fri, 11 Mar 2005 22:43:25 +0100, steve
On Friday 11 March 2005 09:48, Andrew Brown wrote:
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.
Good. You are nearly there. Next, try:
/usr/lib/hotplug/firmware
and are you sure it's not the 111 firmware you need? 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/
participants (3)
-
Andrew Brown -
Ken Schneider -
steve