I just installed OpenSuse 11.0, and I have a Dlink DWL-121. Yast Network Settings shows it as
Prism 2.x 802.11b Adapter (Not connected)
Now I know its connected, so I am not sure about all that, but then it says
Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details.
So I opened up a terminal and did a dmesg and found this section
Ok, so in short what do I need to do on my system to get my device to work. I should like to add the comment that my device is a DWL-121, which is technically non existent. I know in Windows XP you can use DWL-122 drivers and modify the INF files to get them to work. However I have tried NDISWrapper, with the same files that worked in XP and that bore no working results.
Also, note I had to put spaces everywhere where there was because it wanted to make that face. So : p is actually shouldn’t have a space, just so there is no confusion.
So, how do you ‘know its connected’? [You don’t show any output that would
make us agree with that, such as ‘ifconfig’, ‘iwconfig’, ‘route’]
I don’t own this device (tho I did in the distant past, and always used ndiswrapper
on it, under Mandrake-Linux)
I tend to believe that the msg about ‘missing firmware’…SUSE is known for
installing drivers, and then NOT installing the needed firmware to go with it.
But, that’s only a guess.
Your best bet is to try again to use ndiswrapper. Once you get the windows
driver installed in ndiswrapper, post the output of the cmd:
ndiswrapper -l
and then we’ll see whether the results of that look promising.
cookdav wrote:
> warbenekar1;1829781 Wrote:
>> I have a Dlink DWL-121. Yast Network Settings shows it as
>>
>> Prism 2.x 802.11b Adapter (Not connected)
>>
>> Now I know its connected, so I am not sure about all that,
>>
>> I know in Windows XP you can use DWL-122 drivers and modify the INF
>> files to get them to work. However I have tried NDISWrapper, with the
>> same files that worked in XP and that bore no working results.
>>
>>
>
> So, how do you ‘know its connected’? [You don’t show any output that
> would
> make us agree with that, such as ‘ifconfig’, ‘iwconfig’, ‘route’]
>
> I don’t own this device (tho I did in the distant past, and always used
> ndiswrapper
> on it, under Mandrake-Linux)
>
> I tend to believe that the msg about ‘missing firmware’…SUSE is known
> for
> installing drivers, and then NOT installing the needed firmware to go
> with it.
> But, that’s only a guess.
That is NOT SUSE’s fault. Most of the vendors do not allow any
distro to distribute firmware, which is why you need to go elsewhere
to get it.
> Your best bet is to try again to use ndiswrapper. Once you get the
> windows
> driver installed in ndiswrapper, post the output of the cmd:
>
> ndiswrapper -l
>
> and then we’ll see whether the results of that look promising.
You very well may need to use ndiswrapper; however, be aware that when
you do, you are loading a piece of Windows into your kernel and
allowing it to run with absolutely no restrictions and/or checking.
Any bugs in that driver will crash Linux!
I ran ifconfig, iwconfig, and route and got nothing. I mean that is to say the output implied there was no Internet connection which I knew there wouldn’t be. When I ran ndiswrapper the first time I did an ndiswrapper -l and it told me there were no installed drivers. Which makes sense, as there were none. Then I ran ndiswrapper -i and told it where to find the inf file, which was in my home directory. It seemed to install successfully, or at least it generated no errors, however after the fact I ran ndiswrapper -l again and I got nothing, but this time there was no output at all. So I waited and waited and waited, until 1/2 hour passed by. Still no output. I got tired of waiting and restarted my computer to see if that made a difference, but doing ndiswrapper -l still does the same thing.
Can anyone tell me why ndiswrapper -l doesn’t work? Also, assuming I installed it correctly is there a guide or something that can tell me what to do next? I don’t know anything at all about ndiswrapper really…
Here is everything in full. As I said ndiswrapper -l produces no output, although it does seem that the INF file worked lasttime as it says that netprism is already installed. So, now assuming that the driver is installed correctly, what do I have to do to make it work?
No the driver is NOT installed correctly, if it doesn’t display it’s name AND show
device/hardware PRESENT, when you run ‘ndiswrapper -l’.
The probable REASON that it isn’t showing up is that you are running the
64-bit kernel, but are (probably) installing the 32-bit Windows driver. If so,
either install 32-bit SUSE or find the 64-bit Windows driver.
More info here: Ndiswrapper - openSUSE NDISwrapper
& for 32-bit, you shall probably not need ndiswrapper!
try to install the linux only software. If DWL122 can work, i am very sure yours should also work fine…
i am just pasting my dlink h/w info, just incase its of some assistance:
I’m getting the same error. My adapter is SL-2511UB with an Intersil chip ISL3873. It worked with previous versions of openSUSE by installing wlan-ng. And it works ok in Ubuntu 8.04.
I sent a request support to Novell and they asked me to open a bug report on bugzilla.novell.com. I’ve opened 407689
because it wanted to make that face. So : p is actually shouldn’t have a space, just so there is no confusion.