dlink dwa-121 and dwa-131 with realtek 8192cu chipset

Yes i found out it did also where talking to one of my friends he's a Linux coder and i told him about my problem with my dwa-140 and that they don't Work with wpa/wpa2 encryption, and the only thing he says is that it is bad software coding = blackhole image but where can i se with kernel you are using in latest bh image ?
 
tango110 said:
Yes i found out it did also where talking to one of my friends he's a Linux coder and i told him about my problem with my dwa-140 and that they don't Work with wpa/wpa2 encryption, and the only thing he says is that it is bad software coding = blackhole image but where can i se with kernel you are using in latest bh image ?
Click to expand...

I don't know if you are joking or not.
rtl8192cu driver is very stable and works like a charm: tested personally with Vu+ dongles and some D-Link who uses that chipset.
If you refer to Ralink chipset, you have posted in the wrong thread.
In any cases before release the driver into a BH image I test carefully them with all devices I have in my home and I've A LOT of wireless dongles and not only one or twos and I buy some new dongles for testing purposes only.

If your friend want to register here, we can start talk about code ...

I want to remember that BH images uses open sources wireless drivers and they are tested with some dongles, as reported above, and with some Access Points and Wireless routers/modems and in any cases the properly working of devices is confirmed by the fact the new Ralink driver was included some versions ago in the production image.
If a driver has a bug, we can TRY to fix it but WITHOUT a case test able to reproduce the error, it's IMPOSSIBLE for me (or other Team mebers who works on code) to determine the real cause of the problem.

I hope this post can be very clear for everyone who think that BH software is bad: DRIVER can be bad. Image has strongest structure built during YEARS.
 
angelofsky1980 said:
I don't know if you are joking or not.
rtl8192cu driver is very stable and works like a charm: tested personally with Vu+ dongles and some D-Link who uses that chipset.
If you refer to Ralink chipset, you have posted in the wrong thread.
In any cases before release the driver into a BH image I test carefully them with all devices I have in my home and I've A LOT of wireless dongles and not only one or twos and I buy some new dongles for testing purposes only.

If your friend want to register here, we can start talk about code ...

I want to remember that BH images uses open sources wireless drivers and they are tested with some dongles, as reported above, and with some Access Points and Wireless routers/modems and in any cases the properly working of devices is confirmed by the fact the new Ralink driver was included some versions ago in the production image.
If a driver has a bug, we can TRY to fix it but WITHOUT a case test able to reproduce the error, it's IMPOSSIBLE for me (or other Team mebers who works on code) to determine the real cause of the problem.

I hope this post can be very clear for everyone who think that BH software is bad: DRIVER can be bad. Image has strongest structure built during YEARS.
Click to expand...


i agree that bh image is one of the best images around and the ralink driver may suffer af problem at the moment i'am using the vu+ wifi dongle that comes with vu+ ultimo in my solo2 with usb extender cable and it Works great and a dlink dwa-121 to muy vu+ duo so i'am sorry if i mislead you with the realtek 8192cu chipset because they Works great. so please dont take it personally and have a nice weekend angelofsky :-)
 
You must log in or register to reply here.
Back
Top