Mailinglist Archive: opensuse (3666 mails)

< Previous Next >
Re: [SLE] Re: dlink 520+ wireless card problems
  • From: Andrew Brown <seatrout@xxxxxxxxx>
  • Date: Sat, 12 Mar 2005 13:53:41 +0000
  • Message-id: <4da3dd205031205535bc88337@xxxxxxxxxxxxxx>
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:

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

On Fri, 11 Mar 2005 22:43:25 +0100, steve <mail@xxxxxxxxxxxx> wrote:
> 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@xxxxxxxx
> Also check the archives at
> Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Andrew Brown
What I do:
What I'm up to:

< Previous Next >