|
Ubuntu 8.04 Realtek 8187 on Tishiba A215-S7414
I've posted a similar thread in Ubuntu forums and have gotten some advice, but so far, no good. Here's the scoop:
So, if anybody has any suggestions, please let me know. If you need output from the various *config commands, let me know. I would really like to be wrieless soon for Linux. Thanks in advance, LynDawg |
RTL 8187B USB Wireless problems Toshiba A210, helppp Please!
I am a total newbie and trying to get away from MS, Yeah!!!!
I tried to install it with something called ndiswrapper,and a windows XP driver for Linux, with no success. It is recognized in the hardware as a USB device, so at least that's a start. Is there anywhere an explanation of very basic step by step instructions to help me in this critical phase, thanks,Ack |
Here is how to fix this problem...
go to this website http://www.datanorth.net/~cuervo/blo...te-a215-s7407/ and follow the instructions there.
You have to extract it and then using a command line as root, change to the directory and use the command "chmod a+rwx" with the file name, one by one, to make all the files executable. Then you go to type "./makedrv" and it will compile all the drivers for you. Then you type "./wlan0up" and hit enter and the interface will be recognized by the system as a real wireless card. I go into the System<Administration menu and click on the Network menu item and I click on unlock and type in the root password or administrative password and then I highlight the wireless connection menu item, and then click on properties, and then click on network name and using the drop-down menu, I select the network/router name as the ESSID name and then I go down to connection settings and click on configuration using the drop-down menu, I select automatic configuration (DHCP) and then I click OK and then I uncheck and recheck the box next to wireless connection and a small box will appear saying changing the interface configuration. Keep checking with your web browser for an internet connection by typing a web address in the address bar such as http://www.google.com and seeing if a web site comes up. If it does then you are online. If not, then between checking and rechecking the box next to the highlighted wireless connection menu item, type "./wlan0dhcp" in the terminal as root and see if it gets an IP address for your computer. If it does then it is connected to the wireless router. Between all this it should work. If you reboot all you have to do is open a root terminal and type the command to change to the directory where the wireless driver was compiled and type the command "./wlan0up" and hit enter and your wireless internet connection should be up and running and you should be able to surf the internet, as it is already configured. If you go to another place such as a public library with wireless internet, then you repeat all the steps to connect to the internet. You will not have to recompile the drivers by typing "./makedrv" unless you install a newer kernel. The MODIFIED wireless drivers come in 2 forms...the original modified one that works only with 2.6.22 kernels and a newer one by jadams which works with 2.6.24 kernels. I am typing this on my Toshiba A215-7437 laptop with the Realtek 8187b wireless card which is right now working successfully, using the modified jadams/realtek driver with Ubuntu 8.04-i386 on my laptop as its only operating system. I could not stand Windoze Vista and removed it from my laptop as it is slow as molasses and had me tearing my hair out in frustation. Hope this helps. I tried Ndiswrapper. It was a miserable failure and did not live up to the hype. I tried the Win 98 driver as well as all other Windoze drivers and it never worked and never even detected the Realtek wireless card at all. It said it did not exist. So much for that useless trash called "Ndiswrapper". Don't even bother with it as it is a useless, worthless program that never works. |
hello GBH,
thanks over time you must have spent making that post. Optimism once again! my first question is this, he said to make all the files executable, is that all of these files, and did so in which order do I install them? * Parent Directory * 2.6.24.patch * FAQ.html * README * rtl8187b-modified-dist.tar.gz * rtl8187b-modified-jadams-2-1-2008.tar.gz * rtl8187b-unmodified-realtek.tar.gz I will try the modified-dist.GZ file first, and then the .patch file, here I go again, and thanks in advance!! Mark |
Thank you...
First, determine what kernel you have by typing "uname -a" in a terminal window, either normal or root terminal, and then you will decide which modified driver you will use.
The original modified driver by Johnny Cuervo is for 2.6.22 kernels only and will not work with any kernels greater than 2.6.22...such as 2.6.24. The modified driver by jadams will work with 2.6.24 kernels...I know this for a fact as I am typing this on my laptop which is running on a 2.6.24 Ubuntu kernel, the 32-bit one. First, you download the modified driver, and then you extract it. Then you enter the directory where it was extracted to and check the list of files and using the command line or the file manager Nautilus, you change the files to allow them to be executable. If you don't, and you then type "./makedrv" in a root terminal while you are in the directory where they are located, it will say "Permission denied". Anyway, you then wait for the command "./makedrv" to finish and then you start doing the rest of what I mentioned. Namely, typing "./wlan0up" and then using the Network menu item under the System<Administration menu. Eventually it will work. When "./makedrv" is running...when it finishes, look for any final error messages such as "Error 1" or Error 2. If you see any of that at the end of its compiling then it means the compiling failed for some reason. Otherwise you will see warnings about missing pointers or something about something incompatible but don't worry. As long as you don't see the error messages about "Error 1" or "Error 2" you are ok. Anymore questions, let me know. The original Realtek driver for Linux does not compile for some reason. Don't know why. Use only the modified drivers or maybe even the patch. I don't know about the patch. I used the original modified driver or the jadams modified driver successfully. I must try the patch someday. |
Thank you...
Double-posted because my high-speed internet got real slow and didn't want to post this as my connection was barely functioning due to my internet service provider.
Hope all this helps. It works fine for me. |
I found that the drivers from the post above did not work well for me and others have reports difficulties when upgrading a kernel. For me, the best solution was ndiswrapper with the Win98 windows drivers. It was very easy to set up and there is only one minor modification to the driver necessary to get it working. Also, there is a neat little GUI for loading the driver available for Ubuntu via Synaptic. If you are interested in this solution, I will post the directions and links to the solutions.
Bob |
Quote:
Code:
lsusbBob |
All I can tell you...
is that the MODIFIED realtek drivers work and the windoze drivers don't work and neither does that accursed, worthless, good-for-nothing Ndiswrapper.
I have tried Ndiswrapper several times and never could get it working. I gave up on it and trashed it and tried the modified realtek drivers which, for me, work FLAWLESSLY!!! I am typing this on my Toshiba A215-7437 laptop with Ubuntu 8.04-i386 with a 2.6.24 kernel with the jadams modified realtek driver and it works flawlessly. Ndiswrapper does not work...plain and simple and the modified drivers DO work. This is ALL that I know. |
Well, all I can say is that I am glad that it worked for you....that's the main goal: to get it working.
I have a Toshiba A210 with the Realtek 8187B usb chipset, and those drivers only partially worked for me. While it did connect, the signal strength was so low that I had to be within 20 feet of the router to get any kind of usable connection. I installed ndiswrapper, and with information found from googling, I installed the Win98 driver, modified it by adding one additional line to the .inf file, and it works beautifully. I also put a script in rc.d local so that it would be up and connected as soon as I booted up. I also have Slackware 12.1 installed as a second distro on this laptop and this method worked just as flawlessly for Slack as it did for Ubuntu. I have helped quite a number of others get this chipset working with this method. As I understand it, there is a prototype driver being tested for an upcoming kernel release (do not know when) so I am sure that sometime in the near future there will be a native driver for Realtek 8187b. Bob |
I tried Ndiswrapper and...
added the one line to the Windoze 98 driver and installed the Windoze 98 driver and it still did NOT work and did NOT even detect the Realtek 8187b wireless card. Ndiswrapper said that it did NOT exist. I tried several other Windoze drivers with the same result.
Ndiswrapper does NOT work at all...at least NOT for me. I have sworn off that trashy, useless program and stuck to the modified realtek drivers which for sure, DO work. I am using the jadams modified realtek driver with a 2.6.24 kernel under Ubuntu 8.04, the 32-bit version and the driver works flawlessly. Other than having to manually start it when I boot up Linux, and the winmodem does not work and I will someday bypass it with a hardware modem, everything is working flawlessly. Hope this helps. |
Damage Control
I gave up on this Realtek, and bought a Belkin N Expresscard wireless. Using the NDIS GUI in Ubuntu, it saw the hardware, but I never can get anything wireless to show-up in my Network box. So this brings me to my big concern: in my attempts to follow advice from the forums on RTL8187b and manually setting things up thru terminal commands, have I hosed things up real good?
I'm no Linux Guru, just a Winders dude trying to set myself free from the Windows Borg, using the hardware I have. I'm probably taking the Belkin back to Best Buy tomorrow since no one has answered any of my posts about getting IT to work. Frustrated in Indiana... Thanks in advance, LB |
OK Jean,
Man my frustration is mounting, grrrrrr I hope you r online as I am i week old in linux, please respond to my questions as such, I am in MORAN state, first I think I should remove my first driver that isn't functional as far as being recognized by "Network", BUT I GET "couldn't delete /etc/ndiswrapper/net8187b: Inappropriate ioctl for device", Do I need to get rid of this first if so HOWWW?? Secondly, w.r.t. "one by one, to make all the files executable" Do I make all the 6 "shell script" files executable in the "/home/ack/Desktop/rtl8187b-modified-jadams-2-1-2008.tar/rtl8187b-modified" dolder??? only as well as, any "shell script" in the 3 subfolders? as well as any "makefiles" files in the 3 subfolders? and what and how do I do anything with the .patch file? and to make things worse ubuntu isnt extracting any subfolder files in this jadams folder though it does in the other modified, what kind of glitch is this? arghhhh back at it, and thanks in advance, Mark |
First, extract the tar.gz or tar.bz2 file...
by highlighting it with your mouse curser and then right-clicking on it and selecting "extract here" and left-click it so it will extract it in the home directory.
Then you double-click on the directory/folder and it will show the contents in the window and then you highlight all the files, not the directories/folders in it, and right-click them and click on properties and then go to the one that says permissions and check the one that says the file(s) can be executable until you see a checkmark in the box next to the item at the bottom that says "allow executing file as program" and then close the properties box. Then open up a ROOT terminal and type "cd rtl8187b-modified" and hit enter. Then you type "ls" to get a listing of the files in the directory/folder. Then you type "./makedrv" and hit enter and watch the compiling start. Wait until you see it has stopped and you have a command line again as, for example: "root@jean-laptop:/home/jean/rtl8187b-modified#" This is what my command line looks like above here. Then you type "./wlan0up" and hit enter. Then you follow all the instructions in my previous posting. I use a network monitor applet on my top panel. I right-clicked on it and selected properties and then erased "lo" which is the loopback interface, and I typed "wlan0" in place of "lo" and then I clicked on close to close it and it will show the applet with a red square on it before you type "./wlan0up" and hit enter. After you type "./wlan0up" and hit enter, then it will show its normal self with another symbol next to it like some kind of signal-strength measurement or something. You have to type the commands in the directory where the files are. The original modified-driver by Johnny Cuervo works with a 2.6.22 kernel and the jadams-modified driver works with a 2.6.24 kernel. I don't know if it works also with a 2.6.25 or a 2.6.26 kernel. I have never tried. Hope all this helps. As for ndiswrapper, if necessary, re-install Ubuntu Linux from scratch to get a clean re-install and you will not have to worry about anything from ndiswrapper and you can start from scratch with these modified drivers. Hope all this helps. |
Re...
quote "as well as, any "shell script" in the 3 subfolders?
as well as any "makefiles" files in the 3 subfolders? and what and how do I do anything with the .patch file? and to make things worse ubuntu isnt extracting any subfolder files in this jadams folder though it does in the other modified, what kind of glitch is this? arghhhh" Only make the files in the main directory executable and don't worry about any subdirectories/subfolders. As long as you use a root terminal, "makedrv" will take care of the rest of things. Just make sure that the following files are changed to be executable...either with a command line in the root terminal or by using the file manager to highlight and click on them with your mouse... "makedrv release_note wlan0down ifcfg-wlan0 README.FIRST wlan0rmv install ReadMe.txt wlan0dhcp wlan0up" These are the files I make executable so they can be executed in a root terminal. The ones called "release_note" and "README.FIRST" and "ReadMe.txt" are probably not needed to be executable, so you can experiment with them to see what happens. You don't need to make anything in the 3 subdirectories executable. Don't worry about them. As for the .patch file...I would guess that it was intended for the original modified driver before the jadams modified driver came out or else it was intended to be used with the original modified driver or with the jadams modified driver if the jadams modified driver gave any problems. I will have to check it out. Also, I noticed that if I extracted the original modified driver and then the jadams modified driver, that the jadams modified driver was extracted to the same directory/folder as the original modified driver. So I just deleted the directory/folder where they were extracted to and started over. Extract one or the other but not both unless you put one of them in a different directory/folder such as "/usr/src/" or something...as long as they are in different directories you can separately extract them and compile both of them separately and try them out to see what happens. Hope this helps. The MODIFIED realtek drivers really do work and I could never get the ndiswrapper program to work with the windoze drivers so I gave up on ndiswrapper and trashed it and went with the modified realtek drivers. The original realtek drivers from realtek do not compile for some godawful reason and I don't know what that is. I just know that the original unmodified realtek driver(s) do not work nor do they compile. Maybe you can figure it out. Anyway, the programmers who modified the original realtek driver from realtek managed to get it working or else I am not typing this on this website and I am just hallucinating. Hope this helps. Jean Brown Harrell |
JEAN
i AM BACK AGAIN to try once more, firstly when I extract the jadams gz file i dont see anything in the subfolders.....FIGURED THAT OUT with properties, kinda silly it seems, well at least one uncertainty is gone u on line, I am going to try yet again |
YAHOOOOOO, I SEE A WIRELESS CONNECTION in my Network,
Jean, you have been amazing with your patience and even as important things are seeming to make sense, as I am getting used to the new lingo, greattttt !!!!!! my next challenge seems to be how to View Wireless Network Connections, and a hit has suggested "wifi radar", any suggestions, and Is it normal that when I am in wlan0 Properties with Enabled roaming mode checked, that everything else is greyed out??? and THANKS AGAIN!!! Mark |
OK so I should have guessed, more questions,
I don't seem to be able to view any available wireless networks and I know there are some around, and my friend says I should when I left click on the 2 monitors Network Connection icon on the top RHS, ???? Progress though, phewwwwww Mark |
Yahooo It's Working, from simply running ./wlan0up while in the modified folder, which I guess means
wlan0 "on", Is there any way to make it start automatically on bootup? |
Glad it helped...
now I am going to try working with that program "ndiswrapper" to see if I can make it work. That is my next project.
Have to go. Jean |
HMMMM, Jean
OK, I have been having a hard time re-enacting my previous success, w th e wireless, but now it is showing wireless networks again. AND as well a the icon top rhs taskbar showing the wireless options, BUT now it is freezing the computer when connecting, hmmmmm, again any straight forward solutions, argh Mark |
it"s Freezing, arghhhh
Jean Hi there
everything is working when I connect to a network that does NOT require a code, I am on one right now and the card and driver is working great. HOWEVER, when i try to connect to a network which DOES require a code it freezes as its is connecting, hmmmmmm any ideas, and as usual, I appreciate the help :-) !!!!!!!!!!!! Cheers, Mark |
I am still trying to figure this out,
Is there any replacement for the Network Manager in Ubuntu which may have bugs with Realtek drivers? ANYONE? Thanks in advance, and trying to say good riddance to MicroSoft, Mark |
I can't get on to any encrypted networks though non encrypted are no problem.
What the heck's up? ok, I even tried Wicd and though at least it doesn't crash when attempting to get on to any encrypted networks, it stop at the finding ipaddress. And I have tried many diff, networks with many types of encryption, and now I am trying even a different wireless card though as usual I am even having a huge hassle installing it(Linksys WUSB300N)with the ndiswrapper, arggghhhh the battle continues, helppppp! Thanks, Mark |
It Is Working, Hallelujah !!!!!!!!!!!!!!!!
YO,
My wireless is working Hallelujah, and I wish I know how I did it more specifically what was wrong before, after all these permutations and combinations. But this is what I did last.... I referred to beginners guide to installing NDISwrapper titled "My own Personal Ndiswraper Guide - Troubleshooting Tips Included" as I could not get a proper response from modprobe, and I reinstalled it with the intention to get my Linksys usb wireless card trying to function to eliminate another possibility. Well low and behold both cards are working fine and I am getting thru with both. The odd thing is that my RTL8187b driver was installed without NDISwrapper...!!!! Well I guess I should be thankful, and am, now let the games begin!!!!! So I Guess NDISwrapper ROCKS after all!!!!! Mark |
THANKS ALL especialy you JeanBrownHarrel
THANKS ALL especialy you JeanBrownHarrel
|
I have a probelm when installed my wifi Realtyek 8187
(My notebook is Toshiba Satelite A215-S7437) Here's my problem: suryo@suryo-laptop:~/rtl8187b-modified$ ./makedrv rm -fr *.mod.c *.mod *.o .*.cmd *.mod.* *.ko *.o *~ make -C /lib/modules/2.6.24-16-generic/build M=/home/suryo/rtl8187b-modified/ieee80211 CC=gcc modules make[1]: Entering directory `/usr/src/linux-headers-2.6.24-16-generic' CC [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.o /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c: In function ‘ieee80211_softmac_scan_wq’: /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:433: warning: initialization from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:432: warning: unused variable ‘dwork’ /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c: In function ‘ieee80211_probe_resp’: /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:710: warning: ISO C90 forbids mixed declarations and code /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:1554:4: warning: #warning CHECK_LOCK_HERE /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:1594:2: warning: #warning CHECK_LOCK_HERE /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c: In function ‘ieee80211_associate_retry_wq’: /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:2253: warning: initialization from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:2252: warning: unused variable ‘dwork’ /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c: In function ‘ieee80211_softmac_init’: /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:2475: warning: assignment from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:2476: warning: assignment from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:2477: warning: assignment from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:2478: warning: assignment from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:2479: warning: assignment from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:2480: warning: assignment from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c: In function ‘ieee80211_rx_frame_softmac’: /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:1666: warning: ‘chlen’ may be used uninitialized in this function /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:1554:4: warning: #warning CHECK_LOCK_HERE /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac.c:1594:2: warning: #warning CHECK_LOCK_HERE CC [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_rx.o CC [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_tx.o CC [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_wx.o CC [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_module.o CC [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_softmac_wx.o CC [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt.o CC [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp.o /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp.c: In function ‘ieee80211_ccmp_aes_encrypt’: /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp.c:87: warning: passing argument 1 of ‘crypto_cipher_encrypt_one’ from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp.c: In function ‘ieee80211_ccmp_init’: /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp.c:109: warning: assignment from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp.c:125: warning: passing argument 1 of ‘crypto_free_cipher’ from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp.c: In function ‘ieee80211_ccmp_deinit’: /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp.c:141: warning: passing argument 1 of ‘crypto_free_cipher’ from incompatible pointer type /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp.c: In function ‘ieee80211_ccmp_set_key’: /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp.c:423: warning: passing argument 1 of ‘crypto_cipher_setkey’ from incompatible pointer type CC [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_tkip.o CC [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_wep.o LD [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211-rtl.o LD [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt-rtl.o LD [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_wep-rtl.o LD [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_tkip-rtl.o LD [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp-rtl.o Building modules, stage 2. MODPOST 5 modules CC /home/suryo/rtl8187b-modified/ieee80211/ieee80211-rtl.mod.o LD [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211-rtl.ko CC /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt-rtl.mod.o LD [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt-rtl.ko CC /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp-rtl.mod.o LD [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_ccmp-rtl.ko CC /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_tkip-rtl.mod.o LD [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_tkip-rtl.ko CC /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_wep-rtl.mod.o LD [M] /home/suryo/rtl8187b-modified/ieee80211/ieee80211_crypt_wep-rtl.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-16-generic' rm -fr *.mod.c *.mod *.o .*.cmd *.ko *~ make -C /lib/modules/2.6.24-16-generic/build M=/home/suryo/rtl8187b-modified/rtl8187 CC=gcc modules make[1]: Entering directory `/usr/src/linux-headers-2.6.24-16-generic' CC [M] /home/suryo/rtl8187b-modified/rtl8187/r8187_core.o /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: In function ‘rtl8187_rx_urbsubmit’: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:934: warning: passing argument 6 of ‘usb_fill_bulk_urb’ from incompatible pointer type /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: In function ‘rtl8187_rx_manage_urbsubmit’: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:954: warning: passing argument 6 of ‘usb_fill_bulk_urb’ from incompatible pointer type /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: In function ‘rtl8180_rtx_disable’: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:1255: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘long unsigned int’ /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: In function ‘rtl8180_tx’: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2220: warning: passing argument 6 of ‘usb_fill_bulk_urb’ from incompatible pointer type /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2227: warning: passing argument 6 of ‘usb_fill_bulk_urb’ from incompatible pointer type /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: In function ‘rtl8187_usb_initendpoints’: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2277: warning: ISO C90 forbids mixed declarations and code /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2281: warning: ISO C90 forbids mixed declarations and code /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2310: warning: assignment from incompatible pointer type /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2256: warning: unused variable ‘i’ /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: In function ‘rtl8187_usb_deleteendpoints’: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2328: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘long unsigned int’ /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: At top level: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2435: warning: ‘struct struct_work’ declared inside parameter list /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2435: warning: its scope is only this definition or declaration, which is probably not what you want /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: In function ‘rtl8180_wmm_param_update’: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2437: warning: initialization from incompatible pointer type /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2439: warning: initialization from incompatible pointer type /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: In function ‘rtl8180_init’: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2654: warning: assignment from incompatible pointer type /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:2702: warning: assignment from incompatible pointer type /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: In function ‘rtl8180_adapter_start’: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:3054: warning: unused variable ‘bInvalidWirelessMode’ /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:3053: warning: unused variable ‘SupportedWirelessMode’ /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:3052: warning: unused variable ‘InitWirelessMode’ /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:3051: warning: unused variable ‘ieee’ /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c: In function ‘rtl8180_irq_rx_tasklet’: /home/suryo/rtl8187b-modified/rtl8187/r8187_core.c:3769: warning: ISO C90 forbids mixed declarations and code CC [M] /home/suryo/rtl8187b-modified/rtl8187/r8180_93cx6.o CC [M] /home/suryo/rtl8187b-modified/rtl8187/r8180_wx.o CC [M] /home/suryo/rtl8187b-modified/rtl8187/r8180_rtl8225.o CC [M] /home/suryo/rtl8187b-modified/rtl8187/r8180_rtl8225z2.o LD [M] /home/suryo/rtl8187b-modified/rtl8187/r8187.o Building modules, stage 2. MODPOST 1 modules WARNING: "ieee80211_wx_get_freq" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_softmac_start_protocol" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "free_ieee80211_rtl" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wlan_frequencies" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wake_queue_rtl" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_rx_rtl" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_is_shortslot" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_get_name_rtl" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_get_wap" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_set_scan" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_get_rate" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_is_54g" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_stop_queue_rtl" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_softmac_stop_protocol" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_set_rawtx" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_get_scan_rtl" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wpa_supplicant_ioctl" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_get_beacon" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_get_essid" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_set_mode" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_get_mode" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_set_encode_rtl" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_set_freq" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_set_rate" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_set_wap" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_get_encode_rtl" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_wx_set_essid" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "alloc_ieee80211_rtl" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! WARNING: "ieee80211_reset_queue" [/home/suryo/rtl8187b-modified/rtl8187/r8187.ko] undefined! CC /home/suryo/rtl8187b-modified/rtl8187/r8187.mod.o LD [M] /home/suryo/rtl8187b-modified/rtl8187/r8187.ko make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-16-generic' suryo@suryo-laptop:~/rtl8187b-modified$ ./wlan0up insmod: error inserting 'ieee80211_crypt-rtl.ko': -1 Operation not permitted insmod: error inserting 'ieee80211_crypt_wep-rtl.ko': -1 Operation not permitted insmod: error inserting 'ieee80211_crypt_tkip-rtl.ko': -1 Operation not permitted d insmod: error inserting 'ieee80211_crypt_ccmp-rtl.ko': -1 Operation not permitted d insmod: error inserting 'ieee80211-rtl.ko': -1 Operation not permitted insmod: error inserting 'r8187.ko': -1 Operation not permitted Please, give me a clue to solve this problem. I'll apreciate your help. Thanx |
I hope this is the solution...I would glad to be a help like Jean was for me....
re: permission denied.... type sudo before your command (Super User Do) i.e) sudo ./wlan0up Mark and P.S.has anyone found solutions to use encrypted wpa with the modified and patched 8187b... sad to say it still doesn't function with wpa's...arghhhh making it useless for a laptop!!!!!! |
Quote:
Argh, the problem not finish yet suryo@suryo-laptop:~/rtl8187b-modified$ sudo ./wlan0up sudo: unable to resolve host suryo-laptop suryo@suryo-laptop:~/rtl8187b-modified$ Please, give me another advice(I hope Jean may find the solution). Thanx |
I am just a NEWBY but this sounds similar to problems I had. WHen installing the driver with the make and make install commands, the folder (and more importantly) some files inside must have the permissions selected as execute (R. click -- properties -- permissions -- check execute) for example when installing the 8187 driver....
I dont know if that helps... just a thought. |
It is finally working even with WEP/WPA!/2
with the driver fileshare.ro_rtl_drivers.tar.gz,
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
WOW I have to say this is my first foray into Linux and now I see why no one wants to use it. I do not mean to dis a OS and I know how Linux users feel about Microsoft believe me I am right there with you. I have just purchased a T1631 Gateway Laptop it comes with RealTek Wired/Wireless built in. UBUNTU,MANDRIVIA,OPENSUSE all pickup the Wired none pick up the wireless. I run System,Admin, Hardware Testing, in UBUNTU and this is what it says. Realtek Semiconductor Co., Ltd. Unknown device 8199 (rev22) for the wireless card. By digging I find I have a RealTek 8187S card built in the only drivers I have found are the 8187B and 8187L neither seem to work. I have dual boot with vista and I am able to get the inf and sys file but even running NDSWrapper it does not help. So why would people use a OS when they cant even get their hardware to work with it. I must says I am more and more impressed with the GUI that UBUNTU and MANDRIVA have but what good is a PORCHE when you dont have a engine.
|
I thought it was working, NOPE!!!!!!!!
Well, I said in my last post it was working, but that was short lived.
Well, it's not working with any of the WPA encryptions, and any of the 50 permutations of ndiswrapper, modified, jardins, patched, unmodified, win97 altered and not alterd, xp etc etc Drivers!!!!!!! 1 month trying on my Toshiba A210, FOR ANYONE STARTING, forget Toshiba and Ubuntu, or but a USB wireless card that is known to work and DON'T WASTE YOUR TIMEEEE!!!!! MY STUBORNNESS HAS NOT PAID OFF BUT IF ANYONE has any NEW ideas, I sure would like to know, COL (CRY out loud) Mark |
I know that Jean does not like ndiswrapper, but I have to repeat that I have this same chip (8187B) and the same laptop (Toshiba A210), and I have tried the drivers you have been working with. I had the same issues others are having. But, I triple boot this laptop (Ubuntu, Slackware, and Suse11) and ALL of them work beautifully with ndiswrapper for this wireless. Now, I have no need for encryption, so I do not use it. But the wireless works great with a strong signal.
If no one is interested in using ndiswrapper, so be it. But if anyone would like me to give them the steps I used, I will be glad to try and help. Bob |
Hi Bob,
As a pilot I need a flexible laptop that can use many wireless connections that I have no control over and most these days are wpa1/2, and ndiswrapper rtl8187b just does not seem to be able to get past wpa, though WEP I am not sure of, is anyone having success with this on a A210 toshiba??? If so boy I would really appreciate it, Mark |
I had a lot of headache trying to get realtek's 8187b wireless working. I also tried ndiswrapper, and the modified driver. Everything looked OK when using the wireless tools (iwconfig, iwlist, etc.) but for some reason the d*** card still wouldn't associate with any AP.
What finally worked for me (flawlessly, I might add) was to compile/upgrade to the 2.6.27 kernel which now includes support for the 8187b! |
oops, multiple post, sorry...
|
No doubt the modified drivers and ndiswrapper make this card work for some, but I was never able to acheive full functionality on this toshiba laptop until I compiled and installed a new kernel. The 2.6.27 kernel has native support for the rtl8187b, and it is now working perfectly.
|
I have this card in my Tosiba A215 laptop running 64bit Gentoo (2.6.26-gentoo-r1) it works with the rtl8187b-modified-jadams-2-1-2008.tar.gz driver. I tried the modified win98 and ndiswrapper and the other modified driver from the same page as the jadams one. this was the only one I could get to work. I just: (as root)
Code:
tar xvzf rtl8187b-modified-jadams-2-1-2008.tar.gzCode:
./wlan0upthen it's just a simple matter of iwconfig and ifconfig to set it up to work with my network. |
| All times are GMT -5. The time now is 07:46 AM. |