please I need some help with my suse 11 64Bit.
I’m trying to install a Wlan Stick from Realtek: RTL8187b
It works with the 32Bit Version of Suse properly by installing the Linux Driver on the CD.
When using this Linux Driver in the Suse 64Bit Version by typing “./makedrv” in the Terminal, there is a compillation error which tells me something like “CFLAGS were changed, can’t use EXTRA_FLAGS”.
Using the Windows Driver (I tried all windows versions) with ndiswrapper ends in nothing after modprobing ndiswrapper.
lsusb says that the Stick ist in USB Bus and lists its correct name.
yast doesnt recognize the stick at all.
I dont find a 64Bit Driver nowhere.
PLEASE HELP:confused:
If you want any information or outputs just tell me
Support for the 8187B has just been accepted into the wireless-testing git tree, and it will be in kernel 2.6.27. Note - 2.6.26 is not yet released, thus 2.6.27 will not be out for ~3 months. There are also patches for existing kernels, but these both require downloading kernel source, and building a new kernel.
As you have had success with the vendor driver, I suggest you repair the CFLAGS error. From the directory where you issue the ./makedrv, you will need to edit ieee80211/Makefile and rtl8187/Makefile. In each of those files, you will find lines that start with CFLAGS +=… In each case, change it to EXTRA_CFLAGS += … That will fix the immediate problem.
If you have further problems, we’ll try to work you around them.
For the record, I had little success with the vendor driver; however, the patched version works quite well.
In that case, it won’t help. The problem with the out-of-kernel driver is due to
changes in the kernel at 2.6.25, thus the 32-bit version of openSUSE 11.0 fails too.
Larry [who wouldn’t go back to 32-bit for any reason]
I took the comment to mean that no 64-bit WINDOWS
driver (for use with ndiswrapper) could be found.
[Also seemed to say he had it working under 32-bit!?]
I changed the both makefile. by executing ./makrdrv there is a warning that says "“ISO C90 forbids mixed declaration and code” and there is an error commented like this “implicit declaration of set_module_owner”. Both are in the file rtl8187/r8187_core.c
I tried to take out this code line, but this produces more errors.
Changing to a 32Bit System will make the system very slow, so I hope there another possibility.
Do you know a fixed version of the Stick driver for x64?
Thank you in advance
PHD
The RTL8187b make process will generate lots of warnings. Ignore them. You only
have to worry about errors.
The only place a kernel that is fixed for this device is at kernel.org in the
2.6.26-gitX code. You would need to download this and compile a totally new
kernel. I don’t recommend this as it is really 2.6.27-alpha0 - the most unstable
kind of Linux. I’m using it now, but it is not for the faint of heart.
Just wondering where I might get the patched driver from? I’m running 64-bit openSUSE 11.0 on kernel 2.6.25.11-0.1-default and am having problems with the same device.
Its not on a stick, its the internal wlan device but same chipset and registering as usb device.
I thought there was now native support for this device, but in Yast there are no kernel modules in the drop-down so I can’t even tell it which one to try to use!
Have had problems with ndiswrapper, the WinXP and Win 2000 drivers both complain as they’re 32-bit and I’m running a 64-bit kernel, the VistaX64 (long shot, I know but thought I’d give it a try!) driver gives out MANY errors on modprobe and ultimately fails. The X64 driver in the download seems to load ok, but causes other quite serious problems resulting in the ultimate hanging of the machine…
I’ve seen many “solutions” to this problem in Ubuntu forums but all using earlier kernels and so didn’t want to try them in case it caused more harm than good.
Any help would be very much appreciated…
output from lsusb :
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 0bda:8197 Realtek Semiconductor Corp. RTL8187B Wireless Adapter
Bus 005 Device 002: ID 04f2:b064 Chicony Electronics Co., Ltd
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ck iop wrote:
> Hi Folks,
>
> Just wondering where I might get the patched driver from? I’m running
> 64-bit openSUSE 11.0 on kernel 2.6.25.11-0.1-default and am having
> problems with the same device.
>
> Its not on a stick, its the internal wlan device but same chipset and
> registering as usb device.
>
> I thought there was now native support for this device, but in Yast
> there are no kernel modules in the drop-down so I can’t even tell it
> which one to try to use!
Native support starts with 2.6.27-rc3, or later.
You have two options: (1) Download the compat-wireless package, or (2)
download 2.6.27-rc4 and build a new kernel.
Thanks for the quick reply Larry, I downloaded the compat-wireless package and tried to make it and got a strange problem.
I should probably outline at this stage that although it must seem like I’m a nube, my first linux installation was Redhat 4.1, so am comfortable compiling kernels/modules, but I’ve been away from Linux for ~10 years and things seem to have grown up a little since then!!!
The error I get when compiling is as follows :
make -C /lib/modules/2.6.25.11-0.1-default/build M=/opt/compat-wireless/compat-wireless-2008-08-06 modules
make[1]: Entering directory `/usr/src/linux-2.6.25.11-0.1-obj/x86_64/default'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/usr/src/linux-2.6.25.11-0.1-obj/x86_64/default'
make: *** [modules] Error 2
I’ve looked in the src dir its complaining about and there are only two files, Module.symvers and makedumpfile.config.
I think at some point during the installation the kernel was upgraded, but I suspected it was a “packaged” upgrade and so now I need to download the source of the kernel so I can complete the task in hand.
Just really thinking out loud, but does that sound about right? if not, any ideas?!
Thanks for that! Ok, I have progress, having installed the correct rpm for compat-wireless (the ones on the previous link were for 2.6.25.5 and I’m running 2.6.25.11 and so downloaded the appropriate ones…) I now have a wlan0 device.
I have tried everything to get it to actually connect to a wireless network with no joy. At the moment the network is set to “open” to try to eliminate any problems with which encryption is being used, but I’m still not getting connected.
I’ve tried to trace events with iwevent and can see the correct settings being applied. iwconfig gives me all the (correct) info about the device. I have the device configured via Yast AND the network manager and still it is just NOT coming up.
/var/log/NetworkManager is not particularly enlightening :
Aug 31 14:47:41 CLAPTOP NetworkManager: <info> Activation (wlan0) starting connection 'AtTheEdge'
Aug 31 14:47:41 CLAPTOP NetworkManager: <info> (wlan0): device state change: 3 -> 4
Aug 31 14:47:41 CLAPTOP NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 31 14:47:41 CLAPTOP NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug 31 14:47:41 CLAPTOP NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug 31 14:47:41 CLAPTOP NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug 31 14:47:41 CLAPTOP NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug 31 14:47:41 CLAPTOP NetworkManager: <info> (wlan0): device state change: 4 -> 5
Aug 31 14:47:41 CLAPTOP NetworkManager: <info> (wlan0): bringing up device.
Aug 31 14:47:44 CLAPTOP NetworkManager: <WARN> nm_device_hw_bring_up(): (wlan0): device not up after timeout!
Aug 31 14:47:44 CLAPTOP NetworkManager: <info> (wlan0): device state change: 5 -> 9
Aug 31 14:47:44 CLAPTOP NetworkManager: <info> Activation (wlan0) failed for access point (AtTheEdge)
Aug 31 14:47:44 CLAPTOP NetworkManager: <info> Marking connection 'AtTheEdge' invalid.
Aug 31 14:47:44 CLAPTOP NetworkManager: <info> Activation (wlan0) failed.
Aug 31 14:47:44 CLAPTOP NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug 31 14:47:44 CLAPTOP NetworkManager: <info> (wlan0): device state change: 9 -> 3
Aug 31 14:47:44 CLAPTOP NetworkManager: <info> (wlan0): deactivating device
watching iwevent also doesn’t show anything during this time and running ifconfig wlan0 up from the command line simply yields the error :SIOCSIFFLAGS: Connection timed out
Any ideas at all where I might be able to get more information on the problem?
ck iop wrote:
> btw, the rest of the pertinent information is as follows :
> iwconfig :
>
> Code:
> --------------------
> wlan0 IEEE 802.11 ESSID:""
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Tx-Power=0 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> --------------------
>
> iwlist scan (think this might have something to do with the problem):
>
> Code:
> --------------------
>
> wmaster0 Interface doesn’t support scanning.
>
> wlan0 Interface doesn’t support scanning : Network is down
>
> --------------------
>
>
> Just this might help you help me!
In an effort to more closely align my set-up with the (obvious) expertise present in this forum I uninstalled the rpm I installed previously, downloaded the kernel sources and compiled and installed the compat-wireless package I downloaded the other day (dated 2008-08-06).
The results are much the same currently.
Can you help me figured out what I haven’t configured, I have set-up the device for an open access-point in Yast, I left the ESSID empty so it would (I read) assume “any”. I have also created the necessary connection in the desktop network manager (having enabled the device for the user to control in Yast…)
Just to make sure I issued :
iwconfig wlan0 essid AtTheEdge
iwconfig wlan0 enc open
iwconfig wlan0 key off
and the results of iwconfig are now :
wlan0 IEEE 802.11bg ESSID:"AtTheEdge"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
issuing ifconfig wlan0 up still yields the same error : SIOCSIFFLAGS: Connection timed out
What have I forgotten to configure?
Just to clarify, I issued the iwconfig commands to make sure I could see the results in an iwconfig, which is why the actual essid is showing above rather than the “any” I set it to in Yast…cl
So decided to reboot. I booted into Windows to read the hardware address off the device and sure enough it was different to the random one currently being used by the kernel. I noted it down to enter it into the Yast settings and rebooted into Linux.
When it came up I didn’t have the use of my keyboard and couldn’t shut down cleanly, this is exactly what happened when I installed the compat-wireless package rpm for kernel 2.6.25.5.
Had to shut-down via the power key too, currently running a filesystem check
ok, got everything running again, this time for dmesg | grep 8187 I have :
usb 1-4: Product: RTL8187B_WLAN_Adapter
rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage your
phy0: hwaddr 00:16:44:e5:94:0b, RTL8187BvE V0 + rtl8225z2
usbcore: registered new interface driver rtl8187
So looks pretty healthy to me now, the mac address is correct this time too… Still same situation on the config though, I’ve read lots and I haven’t seen any additional steps mentioned anywhere to get this up so if there’s any chance you might be able to tell me what I’ve forgotten I’d very much appreciate it.
Start with YaST and set your network devices to be configured with
Network Manager. Then use the NM applet to add a new connection.
Specify your Essid and encryption details there.
I have done exactly that (and had done the first time when it looked like the device wasn’t configured…). The results are exactly the same.
I have changed from a completely open access point to a WEP encrypted open system so that I could make some changes in the applet and see them being applied to the device. Now, according to the applet the connection contains all the correct settings, but when selecting the connection to use I ran iwevent to capture the config change NetworkManager should have completed, instead of seeing the keys and essid being set I see the following :
Waiting for Wireless Events from interfaces...
09:37:23.116063 wlan0 Set ESSID:off/any
09:37:23.116399 wlan0 Set Encryption key:off
This is why it looked like the device wasn’t configured. It seems there is some disconnect between the applet and what it is telling the device?
But having said that even configuring the device manually doesn’t bring up the network.
If I do :
iwconfig wlan0 essid AtTheEdge
iwconfig wlan0 key [1] 0066E33A57
iwconfig wlan0 key [1]
I see the following in iwevent :
Waiting for Wireless Events from interfaces...
09:52:08.122571 wlan0 Set ESSID:"AtTheEdge"
09:52:24.842019 wlan0 Set Encryption key:<too big> [47] Security mode:restricted Security mode:open
10:18:58.407977 wlan0 Set Encryption key:on
iwconfig now yields :
wlan0 IEEE 802.11bg ESSID:"AtTheEdge"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:0066-E33A-57 Security mode:open
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
With this, should my wireless card now simply connect, or is there something else I should issue to attempt to bring the network up on the new manually configured settings?
