Found it! WTF, Twitter? And the new RTL8187B driver
Okay, I finally found a decent picture of me in that parade. Yay.
(That’s me in the back.)
Twitter’s fucking down again, which is too bad, because I just wrote a mail handler to tell me who’s following me. Woot, looks like it just came back up.
And, finally, I need reports on the new version of the RTL8187B driver that Mister Adams sent me, please. Does it compile? Does it work? Does it turn your computer into Oprah?
It also supports forcing the card ID. If your card doesn’t work, you may
want to try with “force_card=0×8189″ or “force_card=0×8187″.
To get it running (as root):
* ./makedrv (will compile with many warnings)
* ./wlan0up
* ifconfig/iwconfig/ifup/whatever as usual.
Also (since people keep asking), to get the changes persistent across
boots, assuming you’re using ifupdown, add the following to
/etc/network/interfaces:
iface wlan0 inet dhcp
wireless-essid your-ssid
wireless-mode managed
wireless-key1 s:yourpw
pre-up /path/to/wlan0up
post-down /path/to/wlan0down
I’ve only gotten the device to work in managed and ad-hoc modes.
Master (AP) mode …well, it sucks. I haven’t figured out why yet.
Use at your own risk.
Cuervo
09 Oct 2007
==============================================================
Am a no–too–good with all these lines, I tot I just got a driver to install and move on with other things. Am new to this feild and I just need a step by step move on how to try these downloads.
My boss’s already preparing my reward for this staunt. PLLLLLSSSS
Unpack it:
tar xvfz rtl8187b-modified-dist.tar.gzMove into the build root:
cd rtl8187b-modifiedCompile it (ignore the warnings, unless you get *** [foo] Error X):
./makedrvAnd, finally, load the modules.
./wlan0upI downloaded the driver by Mister Adams, it DOES build under 2.6.24, but upon getting an address, instant kernel panic. The same happens with your -modified-dist driver, and, as you’d expect, the “reference” RTL driver (unmodified) does build and loads just fine, except that I have a 0BDA:8197, which the reference driver doesn’t support. Looking through 8187_core.c, I believe the problem lies in the idProduct switch and the priv->rf_chip switch within it, but I am no kernel hacker nor device driver hacker.
Well I’m running this driver on my Satellite A215-s7416.. Distro is Debian Lenny with kernel 2.6.24-amd64 (a debian made kernel not a custom build)
As for the reports: It compiled just fine and works just fine … The only thing that doesn’t work for me is neither WEP or WPA… When I enter the WEP key into config the system just hardlocks…
but it doesn’t meter for me right now as I secured my home network by mac filtering which is more then enough …
Anyway big thanks for this driver and let’s hope rtl8187b will get into kernel soon.
I just tried the update on my Toshiba A215-S7437 with Fedora Core and the 2.6.24 kernel and got the same results as gmureddu. Everything compiles fine, but when it attempts to actually connect to the network I got kernel panic.
I had complete success with the older kernel and with your modified driver before. Thanks for your contributions!
Although it has already been confirmed, yes it compiles on my Toshiba A215, it runs and I can browse wireless networks, but I cannot connect. Truth be told, I haven’t tried unsecure, but I got a kernel panic with WEP.
I hope an update is released soon, I need this going =)
Mister Adams’ driver compiles and runs just fine on my 64-bit Arch Linux under kernel 2.26.4.3. Haven’t tried encryption, though. The laptop is Toshiba Satellite a215-s7422.
Thank you, Mister Adams for your contribution!
Mister Adams’ driver gives kernel panic upon connection to WEP secured network also here on Fedora 8 with kernel 2.6.24.3-50.fc8 and 8197 card from realtek. Haven’t tried insecure, but as val-gaav suggested mac filter could be enough for a home network…
Cuervo’s driver still works fine on 2.6.23 kernel, so thanks anyway for your contributions, Cuervo & Adams!
Hi, please did anybody make the unmodified.dist driver works with the change mac option, ifconfig wlan0 hw ether 00:XX:XX:XX:XX:XX ??? is something wrong in the driver or is it something else? Thanks…