no support for realtek rtl8187se

[Alex French]

The RTL8187SE is a miniPCI version of the Realtek 8187 wireless chipset. Until recently, it had no linux driver. A user on the msiwind.net forums emailed realtek about this, and they received a driver that was not listed on their site. The driver didn't compile for the 2.6.24 kernel included in ubuntu hardy, but after I made some modifications, it compiles and is reported to work.

I have attached the driver from realtek. I will attach a patch in the next post.

[Alex French (grackle)]

Here's the patch.

[Matthew (tigger-outgun)]

I can confirm that the compiled module from Alex works on an MSI Wind using WPA Personal and a WRT54GL router loaded with DD-WRT.

[Alex French (grackle)]

Hmm. Some users reported instability with WPA. How long have you been using
it?

Also, Realtek released a new driver, but I haven't been able to download it
yet. If someone has it and can upload it, I'd appreciate it.
-Alex

On Mon, Jul 14, 2008 at 8:50 AM, Matthew <email address hidden> wrote:

> I can confirm that the compiled module from Alex works on an MSI Wind
> using WPA Personal and a WRT54GL router loaded with DD-WRT.
>

[Neil Brown (u-launchpad-twistedsquare-com)]

On my Advent 4211 (rebadged MSI Wind, same hardware) I have had trouble connected to a WPA Enterprise network with the driver above. It discovers the network and begins connecting, but the DHCP request times out (could just be a problem with the server details) and after that the whole system is broken. I can't kill processes, new windows don't open and so on. Nothing obvious appears in the kernel logs indicating what's wrong. I have to forcefully power-off the machine to recover it. I did previously manage to connect to a WPA personal network with the same setup, without any such problems.

[Matthew (tigger-outgun)]

Alex,

WPA Personal was working fine for a fair while. Just now I am starting to see instabilities. It gets to a point where networkmanager hangs and I am forced to reboot.

I'm just searching for the new driver from Realtek now.

Matt

[Matthew (tigger-outgun)]

I just found this file uploaded on mediafire. Looks to be the later release. Attempting to compile now.

[Matthew (tigger-outgun)]

The new driver compiled fine, with no patches or environment variables set. The release notes specifically mention Ubuntu Hardy. I'm not sure if they took Alex's patch, applied it and released a new version, or if they did more.

I'm using the new modules now, seeing how long they're stable for.

[Matthew (tigger-outgun)]

Nope, it looks like the new version isn't just a patch job using Alex's patch. Attached is a diff of the new and old TKIP cryptography module, it doesn't match Alex's patch at all.

[bobange (bbontoux)]

I don't know if I post on the right forum, but I have an error make compiling the new (and the old) drivers.

scripts/Makefile.build:46: *** CFLAGS was changed in "/home/boris/rtl8187se_linux_26.1012.0331.2008/ieee80211/Makefile". Fix it to use EXTRA_CFLAGS. Arrêt.

If someone can help me ?

[semon (simon-renard)]

the new driver compiled fine for me. And it seems to work, i'll have to test it with WPA later today...

[Matthew (tigger-outgun)]

Well, the new drivers don't seem to be causing system crashes, which is good. They do, however, cause the wireless connection to drop out every now and then, requiring a restart. I get messages in dmesg similar to:
[ 307.961018] rtl8180: WW:No more TX desc, returning 33 of 33

The good news is, I have received a further updated driver directly from Realtek. I'll compile this one and see how it goes.

[Matthew (tigger-outgun)]

Once again, the drivers compiled fine, without any hacks. I've loaded them up and connected to my WPA secured network. Hopefully no dropouts this time.

[Alex French (grackle)]

Good to hear that they're continuing to work on it. I'll be curious to know
how well it works, as I don't have a realtek card in my wind anymore.

On Wed, Jul 16, 2008 at 5:03 PM, Matthew <email address hidden> wrote:

> Once again, the drivers compiled fine, without any hacks. I've loaded
> them up and connected to my WPA secured network. Hopefully no dropouts
> this time.
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux-meta" source package in Ubuntu: New
>
> Bug description:
> The RTL8187SE is a miniPCI version of the Realtek 8187 wireless chipset.
> Until recently, it had no linux driver. A user on the msiwind.net forums
> emailed realtek about this, and they received a GPL'd driver that was not
> listed on their site. The driver didn't compile for the 2.6.24 kernel
> included in ubuntu hardy, but after I made some modifications, it compiles
> and is reported to work.
>
> I have attached the driver from realtek. I will attach a patch in the next
> post.
>

[bobange (bbontoux)]

Hi,

I have to comment some lines in /usr/src/linux-headers-2.6.24-19-generic/scripts/Makefile.build to avoid the CFAGS error.

Now, I have a huge number of warnings and my last lines of ./makedrv are

WARNING: "ieee80211_reset_queue" [/home/boris/rtl8187se_linux_26.1012.0331.2008/rtl8185/r8180.ko] undefined!
WARNING: "ieee80211_wx_set_mlme" [/home/boris/rtl8187se_linux_26.1012.0331.2008/rtl8185/r8180.ko] undefined!
WARNING: "ieee80211_disassociate_rtl" [/home/boris/rtl8187se_linux_26.1012.0331.2008/rtl8185/r8180.ko] undefined!
WARNING: "ieee80211_wx_set_essid_rtl" [/home/boris/rtl8187se_linux_26.1012.0331.2008/rtl8185/r8180.ko] undefined!
WARNING: "ieee80211_start_protocol_rtl" [/home/boris/rtl8187se_linux_26.1012.0331.2008/rtl8185/r8180.ko] undefined!
  CC /home/boris/rtl8187se_linux_26.1012.0331.2008/rtl8185/r8180.mod.o
  LD [M] /home/boris/rtl8187se_linux_26.1012.0331.2008/rtl8185/r8180.ko
make[1]: quittant le répertoire « /usr/src/linux-headers-2.6.24-19-generic »

I don't understand ...

[Kyle Brandt (kyle-kbrandt)]

Matthew:

Is ...

http://launchpadlibrarian.net/16098501/rtl8187se_linux_26.1016.0716.2008.tar.gz

... the most current driver you have? If not can you post the most current, happy to help test!

-Kyle

[Matthew (tigger-outgun)]

Hi Kyle,

It most certainly is. The last 8 digits correspond to the date the driver was released, "0716.2008" meaning the 16th of July, 2008 - 2 days ago :)

The good news is that I haven't had a single problem with this new driver. No dropouts, or lockups. Realtek seem to be fairly heavily developing this driver, which is fantastic to see!

Matt

[Kyle Brandt (kyle-kbrandt)]

Hi Matt,

Thanks for the reply. I haven't had quite that luck. It does drop out for me after a while. Next time it happens I will see if dmesg has any useful info and post it.

-Kyle

[Neil Brown (u-launchpad-twistedsquare-com)]

Using the latest drivers on this thread (16th July) I initially managed to connect to a WPA Enterprise network, but ever since then I haven't managed it again. The authentication box keeps popping up over and over again, but I can connect to the same network from the same machine with what I believe are all the same settings in Windows. How can I get some useful debug output to work out what's going on?

[Julien Pecqueur (pecqueur.jp)]

Hi,

First i apologize for my bad english...

I have the same problem and i have to run ./wlan0up at every boot for activating wireless because if i depmod & modprobe the compiled driver i can't connect a wpa network AFTER rebooting.

Do you think this card will be supported by the next kernel? if not, i will think about buying a linux compatible one and replace it on my wind...

Regards,

Julien

[pablo.t89 (pablo.t89)]

Hi Julien,

Couldn't you just add "wlan0up" (or, more likely, some necessary extract from it) to your /erc/rc.local? I'm very much interested in getting MSI Wind, so this matter is interesting for me (however I still don't have this card to test it).

- Pawel

[Julien Pecqueur (pecqueur.jp)]

Hi Pablo,

I made a little script to launch ./wlan0up when i push a button i had place on the desktop. I will add it in the session startup

"System/Preferences/Sessions/" Add Program...

The wifi card works well like that!

I hope that the driver will be incorpored in the next kernel ;)

[Tomasz Dominikowski (dominikowski)]

Don't make scripts, just copy the relevent files to the relevent folders after compiling and you'll have it working without any silly scripts.

Copy *.ko from both rtl8187se_linux_26.1016.0716.2008/ieee80211/ and rtl8187se_linux_26.1016.0716.2008/rtl8185/ into /lib/modules/2.6.24-19-generic/kernel/drivers/net/wireless/ . Then run sudo depmod and sudo modprobe r8180.

That said, I just ordered an Intel 4965AGN module for the Wind to have reliable networking, better range and speed.

[Julien Pecqueur (pecqueur.jp)]

Tomasz,

If i follow your instruction, when i reboot, i can't connect my WPA network :( that is the reason why i do ./wlan0up at startup...

And after wifi works well!

Julien

[pablo.t89 (pablo.t89)]

Funny issue. So definitely, this driver is not mature enough for the official kernel :-). But, after Julien's trick - does it begin to work correctly?

Tomasz: Do you mean that the default module is slow/has a poor range?

[Julien Pecqueur (pecqueur.jp)]

It works nice :

ath0 802.11b/g linked ESSID:"Livebox-peck"
          Mode:Managed Frequency=2.457 GHz Access Point: 00:1A:6B:C3:04:B8
          Bit Rate=54 Mb/s
          Retry:on RTS thr:off Fragment thr:off
          Power Management timeout:0us mode:All packets received
          Link Quality=97/100 Signal level=-156 dBm Noise level=3 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

No deconnection - Full speed - WPA-TKIP

[Tomasz Dominikowski (dominikowski)]

@Julien

That's strange, I'm connected to my home WPA network with no problems using my "method".

@pablo

Yes to both. I'm currently transferring a lot of data from my bigger laptop to the Wind and the speed is about 1MB/s. My bigger laptop has the 4965AGN Intel card and the access point is an ASUS WL500W.

That said, I've transferred over 10GB already at this speed without any stability/reliability issues.

The range is also not very good. 4965AGN sees 8 available networks, the Realtek only 4 (when placed in the same spot).

This is why the best thing I can do to get as much range and speed is to get the Intel card for the Wind as well. I ordered it for 25 EUR (38 USD), new.

[Neil Brown (u-launchpad-twistedsquare-com)]

Doing as Julien suggested (deleting the modules in /lib/...) and using the wlan0up script (which would seem to have the same effect, since it just uses insmod and ifconfig), my wireless network then connected first time (using WPA Enterprise). Perhaps it is something to do with the boot sequence -- wireless must come last?

[pablo.t89 (pablo.t89)]

If so, then '/etc/rc.local' seems to be a nice place...

[Julien Pecqueur (pecqueur.jp)]

Hi,

I modified my /etc/rc.local :

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

/home/julien/Drivers/Wifi/start_wifi_rc

exit 0
# End of rc.local

and i made a little different start_wifi_rc script (attachement) and now my wifi is on at startup :)

everything is perfect !!!

thank you guys!

julien

[Angelos Kyriazis (angelos-ks)]

hi, I have the ahtec lug netbook, which uses the realtek 8187 wireless card.
After installing the rtl8187se_linux_26.1016.0716.2008 driver, the wireless network appears in the network settings, but it doesn't detect any networks.

[Neil Brown (u-launchpad-twistedsquare-com)]

I'd like to retract my previous comment... I haven't had any luck again since the first few times it worked. My wireless doesn't connect to a WPA Enterprise network regardless of when I run the wlan0up script etc, but in Windows on the same machine it works fine. Added to that, my wired networking seems a bit flaky with regards to DHCP - sometimes it can't allocate an address. I'm happy to try to give more debug information if someone can point out the right flag to enable.

[CirclingTheSun (circlingthesun)]

Mine "works". Only problems is that I have a ping of 4000ms on the lan :| Any suggestions?

[John Markh (dragonsol)]

I have complied a latest version of the drivers (posted by Kyle Brandt) without any problems at all (just couple of warning messages). The network is stable for a while until I start getting:
Aug 19 07:53:58 Ubuntu-laptop kernel: [39714.411945] rtl8180: WW:No more TX desc, returning 1e of 1e
and/or
Aug 19 07:55:38 Ubuntu-laptop kernel: [39814.299579] rtl8180: WW:No more TX desc, returning 2f of 2f
...
and the only way out of this is reboot. Does any one solve this issue?

I use WPA key, but have this in the kernel log:
Aug 19 08:27:19 Ubuntu-laptop kernel: [ 147.736456] rtl8180: Setting SW wep key

[CirclingTheSun (circlingthesun)]

It turns out none of my troubles were related to the driver. I'm currently typing this on my Msi Wind using the latest driver with a WPA connection. As far as I can tell it works 100% and would really like to see it included in Intrepid.

[Tito (tito-webtito)]

I've upgraded from 1012 to 1016 revision of your driver and since that my /var/log/messages is flooded with lines like this :
Aug 25 02:44:56 stormywind kernel: [ 107.906380] too short to sleep
Aug 25 02:44:56 stormywind kernel: [ 108.059743] too short to sleep
...

Any idea? I'll try to disable power management...

[Tito (tito-webtito)]

I tried to do
$ sudo iwconfig wlan0 power off
But my /var/log/messages is always flooded. None other power command seems to work with this driver

[Oguz Yarimtepe (oguzy)]

I have the same card but my system is lpia. I am using netbook remix on an atom based laptop and tried to compile the latest driver. Compilation were succesfull although i got some warnings but there was no wireless card detection after the module installation. I rebooted the system and nothing change. Here is the compiling output. I wonder whether this is because of the lpia compatibility or not of the driver.

[Goldenear (goldenear)]

The latest driver seems to work for me (on msi wind) , except that the connection is dropped some times and I have to unload, reload the module to get it work again... But this doesn't happen very often, only when the computer stay on for a long time.
Also I've fount that this driver has the same multicast bug as explained here :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/258882

I can't use avahi until it's fixed :(

[Oguz Yarimtepe (oguzy)]

After trying a bit i managed to compile the driver and load the modules. Copied the .ko files and add the modules to the/etc/modules file. At the start of the desktop, wireless adapter tried to connect to the mac authenticated wireless network, got an ip, but after a while th connection is dropped. When i tried to scan via iwlist i couldn't see any networks around. So it seems the latest driver has problems. Any soultion to this dropping problem?

[Oguz Yarimtepe (oguzy)]

After removing ieee related modules and just writing the r8180 module to the modules file i was able to get ip and see no disconnection. But i still don't have Internet connection and got "rtl8180 WW:No Rx descriptor available" messages at the syslog.

Any solution?

[Goldenear (goldenear)]

I've installed the new 2.6.27-1 kernel (and restricted modules) and 8187SE is not recognised :(
I really hope this driver will be include in Intrepid Ibex... and the multicast bug fixed.

[Neal:the_real (nmorrison)]

Yesterday I've installed Debian lenny on my Wind U100.
Today I started to configure my wlan card. But it will not run.
Compilation was no problem, but load the driver still not work.

I tried the debian vanilla 2.6.26-1-686 and a selfmade 2.6.26.3 kernel. With both I get the same error wenn i exec ./wlan0up:

insmod: error inserting 'r8180.ko': -1 Unknown symbol in module

In the end of dmesg:
[ 2447.694291] r8180: Unknown symbol ieee80211_wx_set_rawtx_rtl
[ 2447.694478] r8180: Unknown symbol ieee80211_get_beacon
[ 2447.694612] r8180: Unknown symbol ieee80211_wx_set_mode_rtl
[ 2447.694900] r8180: Unknown symbol DOT11D_GetMaxTxPwrInDbm
[ 2447.695031] r8180: Unknown symbol ieee80211_wpa_supplicant_ioctl
[ 2447.695172] r8180: Unknown symbol ieee80211_wx_get_scan_rtl
[ 2447.696144] r8180: Unknown symbol ieee80211_wx_get_essid_rtl
[ 2447.696144] r8180: Unknown symbol ieee80211_stop_send_beacons_rtl
[ 2447.696144] r8180: Unknown symbol ieee80211_wx_set_encode_ext
[ 2447.696144] r8180: Unknown symbol ieee80211_wx_set_scan_rtl
[ 2447.696144] r8180: Unknown symbol ieee80211_stop_queue_rtl
[ 2447.696144] r8180: Unknown symbol ieee80211_is_54g
[ 2447.696164] r8180: Unknown symbol ieee80211_wx_get_freq_rtl
[ 2447.696361] r8180: Unknown symbol ieee80211_ps_tx_ack
[ 2447.696495] r8180: Unknown symbol ieee80211_softmac_ips_scan_syncro
[ 2447.696637] r8180: Unknown symbol ieee80211_wx_set_rate_rtl
[ 2447.696801] r8180: Unknown symbol notify_wx_assoc_event_rtl
[ 2447.697028] r8180: Unknown symbol ieee80211_wx_get_rate_rtl
[ 2447.697189] r8180: Unknown symbol ieee80211_wx_get_name_rtl
[ 2447.697387] r8180: Unknown symbol ieee80211_wx_set_freq_rtl
[ 2447.697520] r8180: Unknown symbol ieee80211_is_shortslot
[ 2447.697660] r8180: Unknown symbol ieee80211_rx_rtl
[ 2447.697799] r8180: Unknown symbol ieee80211_wx_get_mode_rtl
[ 2447.697976] r8180: Unknown symbol ieee80211_wx_set_gen_ie
[ 2447.698137] r8180: Unknown symbol ieee80211_wake_queue_rtl
[ 2447.698278] r8180: Unknown symbol ieee80211_wx_get_wap_rtl
[ 2447.698417] r8180: Unknown symbol free_ieee80211_rtl
[ 2447.698558] r8180: Unknown symbol ieee80211_softmac_stop_protocol_rtl
[ 2447.698706] r8180: Unknown symbol ieee80211_wx_set_auth_rtl

Any ideas?
Did someon run these driver on 2.6.26?

[Neil Brown (u-launchpad-twistedsquare-com)]

Neal: I got exactly the same error messages when inserting the module with 2.6.26 on an earlier Ibex Alpha and on the latest Ibex (2.6.27-2) it doesn't build at all.

[tty82 (gjasfis)]

i want to use the wind with realtek wi-fi in a wpa2personal-aes network, compiled the driver fine but, as ndiswrapper did, i can see my network but no connection (wpa2) can be established.
 After i enter the passphrase in the connection gui it fails to connect while displayed that it's "Waiting for Network Key for wireless network ...."
as i'm not well informed, does wpa2 have large differences to wpa?
or the real question :
reading threads of people making it work on wpa networks means that if i try harder it should work in my wpa2?

[tty82 (gjasfis)]

ok i made it work
sorry for the misusage of lauchpad
thanks for the help

[Julien Barnier (julien-nozav)]

I've managed to load the module with a 2.6.26 kernel. The way to do it is the following :

cd rtk8187se_linux_26.1016.0716.2008/
cd ieee80211/
make
cp Module.symvers ../rtl8185/
cd ../rtl8185/
make
cd ..
sudo ./wlan0up

The important thing is to copy the Module.symvers file from the ieee80211 folder to the rtl8185 one before compiling the r8180 module.

Then I am able to load the module. The card is seen and it seems that I can connect to some networks (without WPA for the moment).

Hope that Helps,

Julien

[Neal:the_real (nmorrison)]

Brilliant. !!!

Now I can load the module and I see the wifi card (wlan0) with iwconfig and ifconfig.
Thanks for that Julian.

But I can not change the wlan parameter such as essid, mode, key and so one.

[Julien Barnier (julien-nozav)]

Are you sure your wifi is activated ?

It seems that it's working for me right now. However, I first copied the *.ko files into the /lib/modules tree, and it didn't work. But if I manually launch wlan0up, it seems ok.

And I also use wicd to manage the connections.

HTH,

Julien

[Patrice Vetsel (vetsel-patrice)]

This wifi card is used in MSI Wind U100, wich is a great success
http://www.msi-computer.fr/index.php?page=9&id_type_produit=&id_prod=754

Please consider to include this driver in Intrepid, to allow this notebook to work under Ubuntu 8.10

[Nicolas Pignier (nicolas-pignier-gmail)]

Hi,
when compiling driver with command "makedrv" in intrepid ibex alpha 5, it fails with an error on the line :

/home/nicolas/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_wx.c:234: error: too few arguments to function ‘iwe_stream_add_point’

full build log in attachment

thanks in advance

Nicolas

[Nicolas Pignier (nicolas-pignier-gmail)]

sorry, here is the FULL build log

[Nicolas Pignier (nicolas-pignier-gmail)]

Here is source code which can compile without errors.
but when trying to insert module into kernel there's the error :

FATAL: Error inserting r8180 (/lib/modules/2.6.27-3-generic/kernel/drivers/net/wireless/r8180.ko): Unknown symbol in module, or unknown parameter (see dmesg)

and dmesg says :

[10354.636416] r8180: no symbol version for ieee80211_wx_get_scan_rtl
[10354.636423] r8180: Unknown symbol ieee80211_wx_get_scan_rtl
[10354.636804] r8180: no symbol version for ieee80211_wx_get_essid_rtl
[10354.636812] r8180: Unknown symbol ieee80211_wx_get_essid_rtl
[10354.637247] r8180: no symbol version for ieee80211_stop_send_beacons_rtl
[10354.637255] r8180: Unknown symbol ieee80211_stop_send_beacons_rtl
[10354.637472] r8180: no symbol version for ieee80211_wx_set_encode_ext
[10354.637480] r8180: Unknown symbol ieee80211_wx_set_encode_ext
[10354.637692] r8180: no symbol version for ieee80211_wx_set_scan_rtl
[10354.637701] r8180: Unknown symbol ieee80211_wx_set_scan_rtl
[10354.637950] r8180: no symbol version for ieee80211_stop_queue_rtl
[10354.637957] r8180: Unknown symbol ieee80211_stop_queue_rtl
[10354.638282] r8180: no symbol version for ieee80211_is_54g
..... (many more)

[Nicolas Pignier (nicolas-pignier-gmail)]

Here is source code (in attachment) which can compile without errors (api changes)
but when trying to insert module into kernel there's the error :

FATAL: Error inserting r8180 (/lib/modules/2.6.27-3-generic/kernel/drivers/net/wireless/r8180.ko): Unknown symbol in module, or unknown parameter (see dmesg)

and dmesg says :

[10354.636416] r8180: no symbol version for ieee80211_wx_get_scan_rtl
[10354.636423] r8180: Unknown symbol ieee80211_wx_get_scan_rtl
[10354.636804] r8180: no symbol version for ieee80211_wx_get_essid_rtl
[10354.636812] r8180: Unknown symbol ieee80211_wx_get_essid_rtl
[10354.637247] r8180: no symbol version for ieee80211_stop_send_beacons_rtl
[10354.637255] r8180: Unknown symbol ieee80211_stop_send_beacons_rtl
[10354.637472] r8180: no symbol version for ieee80211_wx_set_encode_ext
[10354.637480] r8180: Unknown symbol ieee80211_wx_set_encode_ext
[10354.637692] r8180: no symbol version for ieee80211_wx_set_scan_rtl
[10354.637701] r8180: Unknown symbol ieee80211_wx_set_scan_rtl
[10354.637950] r8180: no symbol version for ieee80211_stop_queue_rtl
[10354.637957] r8180: Unknown symbol ieee80211_stop_queue_rtl
[10354.638282] r8180: no symbol version for ieee80211_is_54g
..... (many more)

[Johannes Baiter (terayamashuji)]

It seems Realtek released a new driver for Linux, a user on the msiwind.net forums just posted this link:
http://www.mediafire.com/download.php?pavvaazisj1
rtl8187se_linux_26[1].1022.0904.2008_Release.tar.gz

[Matthew (tigger-outgun)]

I just compiled that new driver (04/09), and it seems to work OK on Hardy. Still some warnings during compilation, though.

Having a look at modinfo, it seems that the driver is being developed by Andrea Merello - andreamrl [AT] tiscali.it. Maybe it is worth pointing him to this bug, so we can get the latest code as he develops it?

[Caroline Ford (secretlondon)]

I had it working fine in hardy, upgraded to intrepid and it won't compile..

secret@laptot:~$ uname -a
Linux laptot 2.6.27-3-generic #1 SMP Wed Sep 10 16:02:00 UTC 2008 i686 GNU/Linux

[Caroline Ford (secretlondon)]

02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:8199] (rev 22)
 Subsystem: Micro-Star International Co., Ltd. Device [1462:6894]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 10
 Region 0: I/O ports at b000 [size=256]
 Region 1: Memory at dfc00000 (32-bit, non-prefetchable) [size=16K]
 Capabilities: [40] Power Management version 3
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
  Address: 0000000000000000 Data: 0000
 Capabilities: [70] Express (v1) Legacy Endpoint, MSI 00
  DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
   ClockPM+ Suprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100] Advanced Error Reporting <?>
 Capabilities: [140] Virtual Channel <?>
 Capabilities: [160] Device Serial Number 00-1d-92-c5-d8-05-00-00

[Caroline Ford (secretlondon)]

The realtek driver has no licensing information with it - so we couldn't redistribute.

We have the source code, maybe someone should ask them to release it under the gpl?

[Caroline Ford (secretlondon)]

The september realtek drivers still don't compile in intrepid.

[Jordan (jordanu)]

The gentoo wiki has instructions for 2.6.27, I couldn't get them to work with intrepid's kernel but maybe this will help get someone closer:

http://gentoo-wiki.com/MSI_Wind#kernel_2.6.27

[Martin Capitanio (capnm)]

Caroline:
>The realtek driver has no licensing information with it
??
rtl8187se_linux_26.1022.0904.2008/rtl8185/license
says clearly GPL v2

[warmrobot (imfrolov)]

I can connect to several Wi-Fi networks, but not for all. Even can't connect to my home ASUS W500gp router. What encryption do you use fot that?

[warmrobot (imfrolov)]

Wireless working only when I erased passphrase and typed only HEX key for WEP 64-bit.

[niclone (4-launchpad-nicospam-sengena-com)]

Hi,

For intrepid, kernel 2.6.27

Here is a up to date patch that do some of the tricks seen here (thanks julien barnier !). Just download the latest driver (url somewhere on this page), rebuild you're kernel like described on the gentoo forum (url about this also somewhere on this page) ;) , then apply this patch, ./makedrv, and wifi should work (using shell commands iwconfig, etc.)

niclone

[niclone (4-launchpad-nicospam-sengena-com)]

Hi again ;)

Now, here is a hack that should make nm-applet working with this driver (without this, nm-applet see the card has a wired card, not a wireless card, making wep/etc. options unavailable)

Just put the attached file here:
/usr/share/hal/fdi/preprobe/10osvendor/

(yes this is a hack ...)
Work find for me, with WEP key (I didn't tested it with WPA). The only bug now (but i'm not sure this is related to this driver only) is that nm-applet won't save my WEP key after a reboot, i have to give it again everytime.

[Matthew (tigger-outgun)]

It is interesting. I'm running the latest version of the vanilla drivers from Realtek (rtl8187se_linux_26[1].1022.0904.2008_Release.tar.gz) on Hardy. They compiled easily with only a few warnings, no errors.

The performance so far has been flawless. Everything works - iwconfig, iwlist, nm-applet, the works. I also haven't had any unexpected dropouts like in the previous version.

My question is - Why are all of the hacks and patches needed to get the driver even working under Intrepid? And then when it is working, why are there still bugs and crashes?

[niclone (4-launchpad-nicospam-sengena-com)]

Hi Mattew,

The main difference between hardy and intrepid is the kernel version. It seem that there are some minor change on the wireless kernel api that broke compilation of this driver on it.
For bugs and crash, the driver work fine for me, I don't have any bug or crash with it, except the unsaved password bug, but this is certainly not related to the driver.

niclone

[David Rando (david-rando)]

I've applied that patch with the latest posted driver in the thread and compiled ok (with warning, but ok). Even network-manager catch it and connecte me to my wpa network.

I'm running it on intrepid beta (updated from alpha 6) on an advent 4211 netbook (realtek 8187se detected as 8199).

I have to run wlan0up to enable it, but the wireless on/off button works and if i switch it off, iwconfig keeps reporting it but it stops giving me wireless networking using iwlist or thru network manager.

Hope it runs out of the box in the next kernel releases (mandriva 2009 and sioux distro have it working actually).

Thanks for the info guys.

[Gérard Bigot (gerard-bigot)]

I just followed the previous instruction :

 - sudo apt-get install build-essential
 - wget http://www.mediafire.com/download.php?pavvaazisj1
 - tar -xzvf rtl8187se_linux_26[1].1022.0904.2008_Release.tar.gz
 - cd rtl8187se_linux_26.1022.0904.2008
 - wget http://launchpadlibrarian.net/18091767/rtl8187se_2.6.27.patch
 - patch -p1 < patch_rtl8187se_2.6.27
 - ./makedrv
 - sudo ./wlan0up

Wait a bit. You should see life on the side of your networkmanager ...

the link is strong, and stay strong.

It has worked on a freshly converted hardy to intrepid, on a MSI Wind U100

I'm happy.

Now, I'm looking to make the wifi connection come up during boot.

PS : It's better for me to write it down while it's fresh...

[niclone (4-launchpad-nicospam-sengena-com)]

Hi mangouste06,

Could you tell me if you have compiled you're own kernel before, or if this is using the kernel image from ubuntu?

to make you're connection available durring boot, you just have to copy the kernel modules where they should go, eg:

mkdir -p /lib/modules/$(uname -s)/rtl8185
cp ieee80211/*.ko rtl8185/*.ko /lib/modules/$(uname -s)/rtl8185/

[Gérard Bigot (gerard-bigot)]

On Fri, Oct 3, 2008 at 10:58 AM, niclone <email address hidden> wrote:
> Hi mangouste06,
>
> Could you tell me if you have compiled you're own kernel before, or if
> this is using the kernel image from ubuntu?

I didn't compile the kernel. I simply used the ubuntu kernel available
at that time.

I wrote all the taken actions in the little sum up from this morning.

By the way, the first wget won't work. you need to download it from
the file server.

>
> to make you're connection available durring boot, you just have to copy
> the kernel modules where they should go, eg:
>
> mkdir -p /lib/modules/$(uname -s)/rtl8185
> cp ieee80211/*.ko rtl8185/*.ko /lib/modules/$(uname -s)/rtl8185/
>

Thanks, I'll try this this afternoon.

G.

[Nicolas Pignier (nicolas-pignier-gmail)]

All is OK on a Msi wind U100
except that i had to change command lines of niclone into :

sudo mkdir -p /lib/modules/`uname -r`/rtl8185
sudo cp ieee80211/*.ko rtl8185/*.ko /lib/modules/`uname -r`/rtl8185/

[Goldenear (goldenear)]

It also works for me on a MSI Wind U100 but multicast still doesn't work... No IPV6 autoconf, no mdns browsing :(

[David Rando (david-rando)]

Any chances to have it included on the upcoming 2.6.27-5 kernel?

[Neil Brown (u-launchpad-twistedsquare-com)]

I tried the latest instructions (thanks niclone and mangouste06) and got the driver to build. First problem I had when running it was that ndiswrapper was getting in the way, so I scrubbed that from my system then tried again. Then I was able to load the driver and the network manager revealed various nearby wireless networks. But just as before, I was unable to connect to a WPA2 network (I can with Windows, so I'm fairly sure the settings must be correct). Any suggestions? Has anyone else managed to connect to a WPA2 network?

[Gérard Bigot (gerard-bigot)]

On Tue, Oct 7, 2008 at 1:20 PM, Neil Brown <email address hidden> wrote:
> I tried the latest instructions (thanks niclone and mangouste06) and got
> the driver to build. First problem I had when running it was that
> ndiswrapper was getting in the way, so I scrubbed that from my system
> then tried again. Then I was able to load the driver and the network
> manager revealed various nearby wireless networks. But just as before,
> I was unable to connect to a WPA2 network (I can with Windows, so I'm
> fairly sure the settings must be correct). Any suggestions? Has anyone
> else managed to connect to a WPA2 network?
>

I connect to WPA2 without problem. It needs an incredible amount of
time, when it connects. One just needs to be patient.

Could you send us the relevant part of /var/log/messages ?

I mean :

Open a shell,
type 'tail -f /var/log/messages' .
Try to connect.
When it fails, send what has appeared in the shell.
To quit 'tail -f', it's CTRL+c.

G.

[Neil Brown (u-launchpad-twistedsquare-com)]

Hi,

My log shows no obvious sign of a problem:

Oct 8 18:13:36 rogue kernel: [ 696.424315]
Oct 8 18:13:36 rogue kernel: [ 696.424320] Linux kernel driver for RTL8180 / RTL8185 based WLAN cards
Oct 8 18:13:36 rogue kernel: [ 696.424345] Copyright (c) 2004-2005, Andrea Merello
Oct 8 18:13:36 rogue kernel: [ 696.424352] rtl8180: Initializing module
Oct 8 18:13:36 rogue kernel: [ 696.424360] rtl8180: Wireless extensions version 22
Oct 8 18:13:36 rogue kernel: [ 696.424371] rtl8180: Initializing proc filesystem
Oct 8 18:13:36 rogue kernel: [ 696.428908] rtl8180: Configuring chip resources
Oct 8 18:13:36 rogue kernel: [ 696.428982] rtl8180 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Oct 8 18:13:36 rogue kernel: [ 696.440813] rtl8180: Channel plan is 0
Oct 8 18:13:36 rogue kernel: [ 696.440820]
Oct 8 18:13:36 rogue kernel: [ 696.440843] Dot11d_Init()
Oct 8 18:13:36 rogue kernel: [ 696.440859] rtl8180: MAC controller is a RTL8187SE b/g
Oct 8 18:13:36 rogue kernel: [ 696.440871] rtl8180: This is a PCI NIC
Oct 8 18:13:36 rogue kernel: [ 696.443393] rtl8180: usValue is 0x100
Oct 8 18:13:36 rogue kernel: [ 696.443399]
Oct 8 18:13:36 rogue kernel: [ 696.499781] rtl8180: EEPROM version 104
Oct 8 18:13:36 rogue kernel: [ 696.504923] rtl8180: WW:**PLEASE** REPORT SUCCESSFUL/UNSUCCESSFUL TO Realtek!
Oct 8 18:13:36 rogue kernel: [ 696.506115] rtl8180: IRQ 17
Oct 8 18:13:36 rogue kernel: [ 696.510863] rtl8180: Driver probe completed
Oct 8 18:13:36 rogue kernel: [ 696.510870]
Oct 8 18:13:36 rogue kernel: [ 696.537748] rtl8180: Bringing up iface
Oct 8 18:13:36 rogue kernel: [ 696.736268] rtl8180: Card successfully reset
Oct 8 18:13:37 rogue kernel: [ 697.473902] rtl8180: WIRELESS_MODE_G
Oct 8 18:13:37 rogue kernel: [ 697.473906]
Oct 8 18:13:37 rogue kernel: [ 697.495457] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 8 18:13:42 rogue kernel: [ 702.977213] rtl8180: Setting SW wep key
Oct 8 18:13:49 rogue kernel: [ 709.637405] Linking with eduroam: channel is 8
Oct 8 18:13:49 rogue kernel: [ 709.678026] Linking with eduroam: channel is 10
Oct 8 18:13:51 rogue kernel: [ 712.188178] Linking with eduroam: channel is 10
Oct 8 18:13:54 rogue kernel: [ 714.706945] Linking with eduroam: channel is 10
Oct 8 18:13:58 rogue kernel: [ 718.596172] Linking with eduroam: channel is 10
Oct 8 18:13:58 rogue kernel: [ 718.620420] Associated successfully
Oct 8 18:13:58 rogue kernel: [ 718.620443] Using G rates
Oct 8 18:13:58 rogue kernel: [ 718.635319] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Oct 8 18:14:00 rogue kernel: [ 721.129981] Linking with eduroam: channel is 10
Oct 8 18:14:00 rogue kernel: [ 721.172236] Linking with eduroam: channel is 10
Oct 8 18:14:02 rogue kernel: [ 723.188091] Linking with eduroam: channel is 10
Oct 8 18:14:04 rogue kernel: [ 724.546852] Associated successfully
Oct 8 18:14:04 rogue kernel: [ 724.546876] Using G rates
Oct 8 18:14:31 rogue kernel: [ 752.112825] Linking with eduroam: channel is 10
Oct 8 18:14:35 rogue kernel: [ 755.500130] Linking with eduroam: channel is 10
Oct 8 18:14:35 rogue kernel: [ 755.526548] Associated successfully
O...

[Neil Brown (u-launchpad-twistedsquare-com)]

I've now been able to perform some tests. Using the rtl8187se I can connect to a WEP network but not WPA personal nor enterprise. If I plug in a D-Link USB dongle, I can connect to all three networks without problem. So it's definitely a problem with the rtl8187se and WPA, but it's not obvious what, exactly.

[Kiran Jonnalagadda (jackerhack)]

I followed the instructions from mangouste06 and niclone above and now have functional wireless on an MSI Wind U100 with an rtl8187se / 8199. I am able to join WPA networks.

However, nm-applet doesn't detect the wireless being turned off and sometimes tries to connect to networks it is no longer in the range of (after suspend and resume). Overall, works fairly well.

[Jan-Niklas Meier (dschanoeh)]

I also downloaded and patched the driver for my MSI Wind U100 and can use it well after executing wlan0up. It works for me with WPA2 and with WPA2 enterprise.
I also have the issue of nm connecting to networks which are no longer in range. But i think this is more a problem with nm?

[David Rando (david-rando)]

Right now, after upgrading to the 2.6.27-7 kernel, the driver compiles, the kernel module installs (you can get the wlan0 interface if you run iwconfig) but you don't get any signal (if you run iwlist wlan0 scan you don't get any wireless network available).

Anyone have the same problem?

[Caroline Ford (secretlondon)]

When people say they have this working could they say whether it's
hardy or intrepid?

It certainly works in hardy for WEP. I can't get the driver to compile
in intrepid.

On 10/10/08, David Rando - Eversmann <email address hidden> wrote:
> Right now, after upgrading to the 2.6.27-7 kernel, the driver compiles,
> the kernel module installs (you can get the wlan0 interface if you run
> iwconfig) but you don't get any signal (if you run iwlist wlan0 scan you
> don't get any wireless network available).
>
> Anyone have the same problem?
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sent from Google Mail for mobile | mobile.google.com

[David Rando (david-rando)]

That's true. I think most of us in the latest comments are speaking about Intrepid, and its 2.6.27 kernel.

[Neil Brown (u-launchpad-twistedsquare-com)]

My comments about WPA not working refer to Intrepid, with the 2.6.27-5 kernel. I haven't yet upgraded to 2.6.27-7.

[brazz (brazz-ardent)]

I agree with @Caroline Ford : I am just having upgraded my Intrepid on MSI Wind with 2.6.27.8 kernel and I have exactly same errors when I run ./makedrv !

[brazz (brazz-ardent)]

Oups, sorry, my kernel is 2.6.27.7.8 ...

[brazz (brazz-ardent)]

Oh, I am confuse! I have ugraded with 2.6.27.7.8 kernel and after I re-patch and now makedrv and wlan0up works !

[MrGrieves (ceberge)]

Hi everyone. Thank you for your help. Thanks to you, my wifi connection works on my MSI Wind.

[brazz (brazz-ardent)]

Great, this works also for me. I put the *.ko in
/lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/ and
sudo depmod -a
sudo modprobe r8180
and never forget the Fn-F11 button !!!

[David Rando (david-rando)]

I recently contacted Realtek by myself, and they kindly sent me back a file that claims to be 2.6.27 compatible.

I have it compiled on intrepid with 2.6.27-7 driver and working without patching (lots of warnings during compile time btw like usual). Wifi working and all stuff with my wpa-psk connection (using it at the moment).

Here's the file attached to this message.

[MrGrieves (ceberge)]

Is it better to install this driver, or the patched one is the same ?

What happens with your driver when kernel update is done ?

[Gérard Bigot (gerard-bigot)]

On Tue, Oct 14, 2008 at 8:37 PM, MrGrieves <email address hidden> wrote:
> Is it better to install this driver, or the patched one is the same ?

I'd say this one. At least, you use the one adviced by the producer.

>
> What happens with your driver when kernel update is done ?

You have to re-compile, reinstall the driver ...

Until the driver is officially integrated into the kernel by the
ubuntu kernel team.

someone for a dkms package? Like the one for virtualbox?

G.

[David Rando (david-rando)]

What i said to the realtek support is they had a more updated version of the driver than the current listed here, and a driver compatible with the 2.6.27, and they sent me this one.

Like a mate said here, what i did was compile it, and then copy all the .ko files to:
/lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/

then:
depmod -a
modprobe rtl8180

After that, the driver comes to work every boot after the kernel load.

I hope the ubuntu kernel team integrate it somehow, or like mangouste06, a dkms entry for this or anything (that scapes to my knowledge).

Anyway, this method works ok actually. I've noticed some slowdowns downloading big files from internet (for instance, downloading an ubuntu image directly to the laptop starts ok, and then slows down to 20-30 kb/s, with stalls from time to time), i had to move the download to another computer to have it in a reasonable time.

[Gérard Bigot (gerard-bigot)]

On Wed, Oct 15, 2008 at 2:08 AM, Steve Langasek
<email address hidden> wrote:
> ** Changed in: linux-meta (Ubuntu)
> Status: New => Invalid
>
Why invalid ?

There's is still no out of the box support for realtek rtl8187se
minipci wifi hardware despite the fact we have a working kernel
module.

This hardware is the one found in all the msi wind U100, and the 27
clones. Netbook, you know?

G.

[Patrice Vetsel (vetsel-patrice)]

@mangouste06 : open your eyes ;) It' invalid for linux-meta not for linux (Confirmed/High)

[Oguz Yarimtepe (oguzy)]

About this driver we solved our problem using the below driver and changing the BIOS. Try the drive first. just ./makedrv and wlan0up should up your wireless. But if you are having a drop problem after the wireless adapter connected to AP then check your syslog: cat /var/log/syslog | grep "irqpoll"
If you see an explanation that suggests to use irqpoll. then add irqpoll parameter to kernel at boot time. Can be done either editing the grub menu boot time or from menu.lst. If it is working then a BIOS fix is required fir you also. But it doesn't harm you using in this way also.

[David Rando (david-rando)]

I've noticed running jockey-gtk recently that a driver is being used on my system, and says: "supported by ubuntu team" for realtek 8180/8185.

After all the 2.6.27-7 recent updates, i've noticed that the wifi was working without doing a thing. So after checking dmesg I see there's a kernel driver loaded at boot time that says:

[ 51.933807] Linux kernel driver for RTL8180 / RTL8185 based WLAN cards
[ 51.933816] Copyright (c) 2004-2005, Andrea Merello
[ 51.933822] rtl8180: Initializing module
[ 51.933828] rtl8180: Wireless extensions version 22
[ 51.933834] rtl8180: Initializing proc filesystem
[ 51.933899] rtl8180: Configuring chip resources
[ 51.933926] rtl8180 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 51.933940] rtl8180 0000:02:00.0: setting latency timer to 64
[ 52.018554] rtl8180: Channel plan is 2
[ 52.018558]
[ 52.018566] Dot11d_Init()
[ 52.018576] rtl8180: MAC controller is a RTL8187SE b/g
[ 52.018582] rtl8180: This is a PCI NIC
[ 52.020978] rtl8180: usValue is 0x100
[ 52.020982]
[ 52.076072] rtl8180: EEPROM version 104
[ 52.080859] rtl8180: WW:**PLEASE** REPORT SUCCESSFUL/UNSUCCESSFUL TO Realtek!
[ 52.081569] rtl8180: IRQ 17
[ 52.742490] rtl8180: Driver probe completed

So, is the rtl8187 (rtl8180/85) finally supported out of the box? Looks like it is ;-)

I've attached an screenshot of my jockey window (sorry, in spanish)

[Gérard Bigot (gerard-bigot)]

Yes david, you're right. Jockey takes de modules we put into /lib/modules/$(uname -s)/rtl8185 in consideration and acts on it.

Message 'Supported by ubuntu team' seems a location based message. And we put our modules in /lib/modules...

But this directory doesn't exist in the kernel modules right now.

I just removed rtl8185 from /lib/modules/$(uname -s).

***
The one created with :
      sudo mkdir -p /lib/modules/`uname -r`/rtl8185
      sudo cp ieee80211/*.ko rtl8185/*.ko /lib/modules/`uname -r`/rtl8185/
***

Reinstalled everything kernel related. No trace of modules related to 8187

According to Steve Langasek, we don't have any chance to get it in intrepid (all this invalid change).

G.

[David Rando (david-rando)]

Mmmmhh, i don't have that folder, nor in the place you comment, and not in the place i knew either /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless )

The only file i saw is a rtl8180.ko, same date and time as the others in that folder. The file i was copying before after compiling is named rt8180.ko (not rtl8180 as I see).

I've removed all those files i put there (easy, becasue all of them had different creation time).
I don't know if i misunderstood something that you said (i'm spanish you know ;-) ) or maybe i'm doing something wrong, and the files i compile are anywhere (for instance, i didn't take a look if the makedrv script put it there for me).

That why i would like to see if any of the users of those laptops with this wifi card or same chipset had it working properly. I'll test the final version from live cd once it's released.

Right now, the wifi is working, but i noticed a big bug on it: you start using it, but after a period, the connection rate drops to 2M and hangs you from internet.
If, after that, you commit something like: iwconfig wlan0 rate 48M, it starts to work just after you press enter. (i got some messages on dmesg too about this, i cannot reproduce it right now, because looks like it happens only on wpa/wpa2 connections, and now i'm using wep 64).

[brpaolo (brpaolo)]

mangouste06 wrote:
> According to Steve Langasek, we don't have any chance to get it in intrepid (all this invalid change).

Does that mean just for the initial release, or will it not be included until next year's Ubuntu (9.04 ?)?
If Intrepid updates will not include it at all, I am going to look into getting a replacement wireless card.

[Caroline Ford (secretlondon)]

Intrepid is now frozen as it's due out very soon. No new features.

Hopefully we will get support in jaunty, Ubuntu 9.04.

I'd get a new wireless card, I'm using a USB stick.

[CirclingTheSun (circlingthesun)]

brpaolo wrote:
> Does that mean just for the initial release, or will it not be included until next year's Ubuntu (9.04 ?)?
> If Intrepid updates will not include it at all, I am going to look into getting a replacement wireless card.
Thats not the way you get things done. You do it like this: "If Intrepid
updates will not include it at all, I am going to look into getting a
replacement *distro*." ;)

By the way can anyone confirm that WPA Enterprise is working yet? It
used to work most of the time with Hardy but now that im running
Intrepid I get nothing.

[rt (rtomanek)]

Caroline Ford wrote:
> Intrepid is now frozen as it's due out very soon. No new features.

Kernel freeze was only three days ago. It's a pity no one cared to add support for this chipset before that, especially that the driver is readily available since some time.

> I'd get a new wireless card, I'm using a USB stick.

And many will get a new distribution.

[warmrobot (imfrolov)]

My only problem on 2.6.24-12 is that wlan0 disappear after reboot.

I remove module r8180, then compile driver, then start up interface:
sudo ./wlan0up

Now it start working!
then

sudo cp -r ieee80211/*.ko /lib/modules/2.6.24-19-generic/kernel/drivers/net/wireless/
sudo cp rtl8185/r8180.ko /lib/modules/2.6.24-19-generic/kernel/drivers/net/wireless/

then

sudo depmod -a
sudo modprobe r8180

reboot and...do it all again :-( because interface wlan0 does not exist after starup. Why?

[warmrobot (imfrolov)]

Sorry, not on 12, on 21 of course. And all actions like cp *.ko I do to right kernel (21) not to 19. But it does not help.

[David Rando (david-rando)]

Well, we should start looking to "bother" for a better driver instead switching cards. Right now, (let's put the out-of-the-box mess apart), copying the .ko files to the kernel modules driver folder worked for me all the time in intrepid. If you, running the wlan0up script at startup is enough, and easy to do (on sessions control on gnome, making a simple script for rc.d startup..)

I'm going to take a look at what mandriva is using on the latest 2009 release, people is happy with it.

[Gérard Bigot (gerard-bigot)]

On Mon, Oct 20, 2008 at 10:00 AM, warmrobot <email address hidden> wrote:
> Sorry, not on 12, on 21 of course. And all actions like cp *.ko I do to
> right kernel (21) not to 19. But it does not help.
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I think you should recreate the module map : sudo depmod -ae

G.

[Kiran Jonnalagadda (jackerhack)]

@warmrobot: try adding r8180 to your /etc/modules.conf. I did that and it
works with every boot.

[warmrobot (imfrolov)]

mangouste06, what is the parameter "ae"? Anyway, I try it, with no success.
Kiran Jonnalagadda, do you mean /etc/modules ? Yes, I did that, but it doesn't help.

This is not only my problem. In MSI Wind forum this situation is now discussing.
I khow, that in 21 kernel some changes with 8187 USB were made. May be these things are associated?

[warmrobot (imfrolov)]

After reboot in .19 and with no wireless i typed:

sudo modprobe -v r8180
and it suddenly did the trick! Wow! Now I have wireless again.

but not on .21 :-(

In .21 I've got errors.

[Maxime (maxime-maximeweb)]

Sorry, I'm a new Linux user; I installed Ubuntu 8.10beta, but wireless modules for rtl8187se are not present. Wich one I've to install to make it works?
I can't do it in 8.10beta or I missunderstood?

[Luqe (luqeckr)]

anyone notice this folder ???

# ls /lib/modules/2.6.24-21-generic/ubuntu/wireless/rtl8187-usb/
ieee80211 rtl8187

it is a driver for rtl8187 and rtl8187b but not for rtl8187se

it has the same module name with ieee80211 on 8180 driver
so the module cannot load automatically even after copying to
/lib/modules/2.6.24-21-generic/kernel/driver/net/wireless

because it will load different ieee80211 modules...

[zajca (zajcaa)]

I have this BUG on MSI wind, Ubuntu HH 8.04.1 - 2.6.24-21
I use this manual "no errors" http://julienpecqueur.com/tutoriaux/install_driverwifi.html
I cant connect to my unsecurited wifi.

[Coffelius (coffelius)]

hi. if you have problems with authentication try with this fork of the driver
http://msi-wind-linux.googlecode.com/files/rtl8187se_linux-03.tar.bz2
let me know if it solved your problems. thanks

Make and interface up with
wget http://msi-wind-linux.googlecode.com/files/rtl8187se_linux-03.tar.bz2
tar xvjf rtl8187se_linux-03.tar.bz2
cd rtl8187se_coffee
./makedrv
./wlan0up

Then, to install in boot for ubuntu:
./install

[zajca (zajcaa)]

I have this error in ./makedrv

In file included from /home/zajca/rtl8187se_coffee/rtl8185/r8180_core.c:67:
/home/zajca/rtl8187se_coffee/rtl8185/r8180.h:46:29: error: linux/semaphore.h: No such file or directory
make[2]: *** [/home/zajca/rtl8187se_coffee/rtl8185/r8180_core.o] Error 1
make[1]: *** [_module_/home/zajca/rtl8187se_coffee/rtl8185] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-21-generic'
make: *** [modules] Error 2

[Gérard Bigot (gerard-bigot)]

I'm fully intrepid uptodate.

Yes, this driver compiles with zero error. And it works great.

But, once loaded with wlan0up, I'm flooded (as dmesg shows) with :

 1595.719670] rtl8180: Got last fragment
[ 1595.719674] rtl8180: yanked out crc, passing to the upper layer
[ 1595.727495] rtl8180: Alloc initial skb 76
[ 1595.727502] rtl8180: going to copy current payload 74
[ 1595.727507] rtl8180: current fragment skb copy complete
[ 1595.727511] rtl8180: Got last fragment
[ 1595.727515] rtl8180: yanked out crc, passing to the upper layer
[ 1595.754520] rtl8180: Alloc initial skb 6e
[ 1595.754529] rtl8180: going to copy current payload 6c
[ 1595.754536] rtl8180: current fragment skb copy complete
[ 1595.754542] rtl8180: Got last fragment
[ 1595.754548] rtl8180: yanked out crc, passing to the upper layer
[ 1595.755336] rtl8180: Alloc initial skb 10
[ 1595.755342] rtl8180: going to copy current payload e
[ 1595.755346] rtl8180: current fragment skb copy complete
[ 1595.755351] rtl8180: Got last fragment
[ 1595.755355] rtl8180: yanked out crc, passing to the upper layer
[ 1595.756857] rtl8180: Alloc initial skb 10
[ 1595.756863] rtl8180: going to copy current payload e
[ 1595.756868] rtl8180: current fragment skb copy complete
[ 1595.756872] rtl8180: Got last fragment
[ 1595.756876] rtl8180: yanked out crc, passing to the upper layer
[ 1595.764306] rtl8180: Alloc initial skb 5b
[ 1595.764313] rtl8180: going to copy current payload 59
[ 1595.764319] rtl8180: current fragment skb copy complete
[ 1595.764323] rtl8180: Got last fragment
[ 1595.764327] rtl8180: yanked out crc, passing to the upper layer
[ 1595.764710] rtl8180: Alloc initial skb 10
[ 1595.764715] rtl8180: going to copy current payload e
[ 1595.764720] rtl8180: current fragment skb copy complete
[ 1595.764724] rtl8180: Got last fragment
[ 1595.764728] rtl8180: yanked out crc, passing to the upper layer
[ 1595.772207] rtl8180: Alloc initial skb 76
[ 1595.772215] rtl8180: going to copy current payload 74
[ 1595.772220] rtl8180: current fragment skb copy complete

So, I'm back to the last driver in this bug report.

If I have time I'l try the version 2, before the backport ...

G.

On Sun, Oct 26, 2008 at 5:12 PM, Coffelius <email address hidden> wrote:
> hi. if you have problems with authentication try with this fork of the driver
> http://msi-wind-linux.googlecode.com/files/rtl8187se_linux-03.tar.bz2
> let me know if it solved your problems. thanks
>
> Make and interface up with
> wget http://msi-wind-linux.googlecode.com/files/rtl8187se_linux-03.tar.bz2
> tar xvjf rtl8187se_linux-03.tar.bz2
> cd rtl8187se_coffee
> ./makedrv
> ./wlan0up
>
> Then, to install in boot for ubuntu:
> ./install
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[zajca (zajcaa)]

I now try install 8.10 and this driver http://msi-wind-linux.googlecode.com/files/rtl8187se_linux-03.tar.bz2
and work perfect.

my last error is in hardy sry.

[Coffelius (coffelius)]

Solved
http://msi-wind-linux.googlecode.com/files/rtl8187se_linux-04.tar.bz2

[Gérard Bigot (gerard-bigot)]

regarding the last comment, I do agree.

Fully clean compilation.

And it seems to work great.

G.

[brpaolo (brpaolo)]

>> Fully clean compilation. And it seems to work great.

That does sound encouraging!

Please would it be possible for one of you who understands what you are doing to post a step by step guide to installing the driver Coffelius has posted?

[Gérard Bigot (gerard-bigot)]

>post a step by step guide to installing the driver Coffelius has posted?

Simple :

 - apt-get install build-essential
 - if you're running the -generic flavour of your kernel : apt-get install linux-header-generic . Otherwise, you should know which header you need. Maybe type 'uname -a' to find out ?

 - download http://msi-wind-linux.googlecode.com/files/rtl8187se_linux-04.tar.bz2 or the latest available on http://code.google.com/p/msi-wind-linux/
 - tar jcvf rtl8187se_linux-04.tar.bz2
 - cd rtl8187se_coffee/

 - ./makedrv
 - ./wlan0up
 - test all you want.
 - ./wlan0down

 - if it's good enough for you : ./install

My thanks go to coffelius for its work ...

[Coffelius (coffelius)]

ctwardy posted the following script at msi forums http://forums.msiwind.net/post51751.html
It downloads and install my fork. Remember "apt-get install build-essential" as mangouste06 said.

# Download, build, and install Coffelius' variant of the rtl8187
# driver. Originally noted in an Oct 17 post to:
# http://forums.msiwind.net/post50498.html by coffelius
# The code is available from:
# http://code.google.com/p/msi-wind-linux/

# Change this name to get a newer version
name=rtl8187se_linux-04.tar.bz2
dirname=rtl8187se_coffee

# Fetch if needed
if [[ ! -e $name ]]; then
  wget http://msi-wind-linux.googlecode.com/files/$name
  tar xvjf $name
fi

# Build and load
cd rtl8187se_coffee
./makedrv
sudo ./wlan0down
sudo ./wlan0up

# Install in boot for ubuntu, inserting a line into
# /etc/modules, if it's not already there.
sudo ./install
if grep r8180 /etc/modules > /dev/null;
  then sudo echo r8180 >>/etc/modules
fi

[brpaolo (brpaolo)]

Thanks to both of you (Mangouste and Coffelius)! Now all I need to do is to find a wireless network to try to connect the Wind to ;)

[Fernando (psnando)]

Hi all,
Just want to thank you guys... you rock!!! I've been following this thread in the last days because I'm a owner of a msi wind u100 laptop and was trying for the first time the Ubuntu 8.04 linux distribution. I was almost giving up of having wireless in it but tried building the driver following instructions as posted here... and what can I say... it works like a charm. I'm very happy with Ubuntu (only 1 week of experience so far)... maybe I won't go back to windows no more... :)

Kind regards
Fernando

[Erwin Olario (gowin)]

I'm on Ubuntu 64-bit Hardy and had this working on a previous kernel 2.6.19, now after an upgrade to 2.6.24 I lose the wifi settings every time I reboot.

Is there anything I'm missing here?

[Fernando (psnando)]

Hi,
In my case I had this working doing the following before building the driver:
1- First I removed the following libraries (backing up first of course) based on a comment by marc.milliien in http://forums.msiwind.net/post51751.html

sudo rm -rv /lib/modules/2.6.24-21-generic/kernel/drivers/net/wireless/rtl8187.ko
sudo rm -rv /lib/modules/2.6.24-21-generic/kernel/net/ieee80211
sudo rm -rv /lib/modules/2.6.24-21-generic/ubuntu/wireless/rtl8187-usb
sudo depmod

2- then I executed the procedure mentioned last by Coffelius and rebooted... I had the driver recognized and wireless this way

P.S. I'm using 2.6.24-21-generic as atested by command (sorry I'm kinda a newbie with linux kernel stuff)
fpereira@fpereira-laptop:~$ uname -a
Linux fpereira-laptop 2.6.24-21-generic #1 SMP Tue Oct 21 23:43:45 UTC 2008 i686 GNU/Linux

Hope it helps anyone. It surely helped me :)

Cheers
Fernando

[Erwin Olario (gowin)]

I lost my patience and took the easy route out - i reverted to the previous kernel. I'll try it again when I have the time.

[egil.bjarko (egil-bjarko)]

Hi folks,

When version 8.10 was released I really was hoping to be able to use it on my MSI Wind without having to fiddle around.
I am sorry to say that it didn´t work.

In the mean time I go for Mandriva 2009 which works perfectly out of the box with both wifi, and usb 3G modem.

/Egil

[warmrobot (imfrolov)]

Update to 8.10 and compiling from there: http://code.google.com/p/msi-wind-linux/
Everything is fine! Thanks for everyone!

[zajca (zajcaa)]

I have a little problem, when i connect to wifi with signal under 60% connection falling down (I lost ping, but connection manager "nm-applet and wicd to" are still shows "connection established" i must manual reconnect) second problem is with eduroam, I have 90% signal but nm-applet shows no signal and I can't connect. It's problem with driver or wifi card?

[Kyle Brandt (kyle-kbrandt)]

I can't seem to connect to my AP, it just keeps asking for the WPA key, the wpa_supplicant log shows:

Trying to associate with 00:18:39:c5:a1:de (SSID='daranet' freq=2442 MHz)
Association request to the driver failed
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS

Anyone have a suggestion?

This is with intrepid, and seems to hold true for all the driver posted here, using the coffe-4 one now

[boskicinek (boski-cinek)]

Try to change your AP channel to something lower and ESSID to something shorter. I have 2 APs, working on exactly the same hardware with the same configuration, except ESSID and channel. 1st have 12 letters in name and is using 2nd channel and the 2nd have 19 letters in ESSID and works on 8th channel. First one works like charm, but no matter what I do (turning your Wind off (reboot is not enough) and on solves problems with WiFi sometimes) I can't connect to 2nd one. Last working configuration for 2nd AP was Hardy with kernel 2.6.24-19 and RTL8185SE r1022 drivers.

[Kyle Brandt (kyle-kbrandt)]

Finally got it to work. What led to it working was upgrading from ddwrt 23-sp2 to 24-sp1 on my WRT54GL v1.1 on my router. When I did the upgrade I did not reset any settings so it would seem like the new firmware was the cause, but it could have been something else (not going to flash the firmware back again my to find out if it the new firmware :-P ). I also tested a BEFW11S4 and with its standard factory firmware and was able to connect without WPA but not with WPA.

[andre_uebe (uebe)]

I'm using Ubuntu 8.10 in MSI Wind

and I installed:
build-essentials
linux-headers-2.6.27-7-generic
subversion

and I tried to do ./makedrv and and error happened:

[code]
andre@uebe-msi:/opt/rtl8187se_linux_26.1016.0716.2008$ sudo ./makedrv
rm -f *.mod.c *.mod *.o .*.cmd *.ko
rm -rf /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/tmp
make -C /lib/modules/2.6.27-7-generic/build M=/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211 CC=gcc modules
make[1]: Entrando no diretório `/usr/src/linux-headers-2.6.27-7-generic'
  CC [M] /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/dot11d.o
In file included from /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/dot11d.h:4,
                 from /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/dot11d.c:11:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211.h: In function ‘ieee80211_priv’:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211.h:1490: warning: ‘netdev_priv’ is static but used in inline function ‘ieee80211_priv’ which is not static
  CC [M] /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_softmac.o
In file included from /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_softmac.c:17:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211.h: In function ‘ieee80211_priv’:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211.h:1490: warning: ‘netdev_priv’ is static but used in inline function ‘ieee80211_priv’ which is not static
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_softmac.c: In function ‘ieee80211_associate_complete’:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_softmac.c:1970: warning: array subscript is above array bounds
  CC [M] /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_rx.o
In file included from /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_rx.c:46:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211.h: In function ‘ieee80211_priv’:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211.h:1490: warning: ‘netdev_priv’ is static but used in inline function ‘ieee80211_priv’ which is not static
  CC [M] /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_tx.o
In file included from /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_tx.c:56:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211.h: In function ‘ieee80211_priv’:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211.h:1490: warning: ‘netdev_priv’ is static but used in inline function ‘ieee80211_priv’ which is not static
  CC [M] /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_wx.o
In file included from /opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_wx.c:37:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211.h: In function ‘ieee80211_priv’:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211.h:1490: warning: ‘netdev_priv’ is static but used in inline function ‘ieee80211_priv’ which is not static
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_wx.c: In function ‘ipw2100_translate_scan’:
/opt/rtl8187se_linux_26.1016.0716.2008/ieee80211/ieee80211_wx.c:57: warning: passing argument 1 of ‘iwe_stream_add_event’ from incompatible pointer type
...

[Jeffrey Seguerra (jepong)]

i found this .deb somewhere for the wireless of msi wind

[Jeffrey Seguerra (jepong)]

btw... attached .deb was used on intrepid

[boskicinek (boski-cinek)]

@jepong: it's useless to post single package for single version of kernel. I'm author of this packages and if someone need them to easy install rtl8178se on their Ubuntu I suggest to visit my homepage (http://boskastrona.ovh.org/index_en.html) and check for package build against newest kernel available (currently 2.6.27.8 in Intrepid). Anyway this doesn't solve the problem we discuss (no native support in ubuntu kernels).

[warmrobot (imfrolov)]

Thank you very much, boskicinek!

Now my wlan0 start to work automatically after startup.
I think I will not upgrade to 2.6.27.10 for a while because I don't want loose wi-fi again.

[boskicinek (boski-cinek)]

@warmrobot: don't be afraid, I've already built drivers for 2.6.27.10. Check my website or this forum thread:

http://forums.msiwind.net/debian/rtl8187se-drivers-for-ubuntu-and-deb-packages-t4954.html

I usually try to build packages for newest kernels as soon as possible.

[boskicinek (boski-cinek)]

After I sent a "love letter" to realtek, they sent me updated drivers (see attachment). Package is still named r1023, but the date has changed (from 0928 to 1118) and of course the source code. I'm using it right now and it works much more stable for me than the old one, although I'm still getting huge latencies from time to time.

You can also get deb package I prepared for 2.6.27.10 kernel:
http://boskastrona.ovh.org/download/[e-mail]

[Coffelius (coffelius)]

thanks :)
i'm going to check differences

On Sat, Nov 29, 2008 at 4:11 PM, boskicinek <email address hidden> wrote:
> After I sent a "love letter" to realtek, they sent me updated drivers
> (see attachment). Package is still named r1023, but the date has changed
> (from 0928 to 1118) and of course the source code. I'm using it right
> now and it works much more stable for me than the old one, although I'm
> still getting huge latencies from time to time.
>
> You can also get deb package I prepared for 2.6.27.10 kernel:
> http://boskastrona.ovh.org/download/[e-mail]
>
> ** Attachment added: "rtl8187se_linux_26.1023.1118.2008.tar.gz"
> http://launchpadlibrarian.net/20052864/rtl8187se_linux_26.1023.1118.2008.tar.gz
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gabriel Ortega <email address hidden> http://coffelius.bloggear.net

[brointhemix (q3storage-deactivatedaccount)]

boskicinek: Do you think that a proper "love letter" would make Realtek put the current and possible future versions of the driver on their website? I think it would be easier for everyone to find and download it if it was accessible from the manufacturer's homepage.

Anyways, thanks for the updated driver :).

Best Regards

[Coffelius (coffelius)]

Hi!
If there is some place where the driver has to be is in the linux
kernel mantained by the community.
I think we can do a nice work doing that with some kind of team work.
The changes between the versions of the driver are minimal. Reading
the code I can see actively no more than 2 developers. Well, I didn't
see the last version because I'm very busy right now.

Should we create a small campaign to recruit more developers to
prepare the driver to be proposed in the kernel?
We have the project at google code easy to contribute and packages for
ubuntu. With a couple of contributors we have more people working in
the driver than realtek.
What do you think?

On Sun, Nov 30, 2008 at 1:34 PM, brointhemix <email address hidden> wrote:
> boskicinek: Do you think that a proper "love letter" would make Realtek
> put the current and possible future versions of the driver on their
> website? I think it would be easier for everyone to find and download it
> if it was accessible from the manufacturer's homepage.
>
> Anyways, thanks for the updated driver :).
>
> Best Regards
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gabriel Ortega <email address hidden> http://coffelius.bloggear.net

[David Rando (david-rando)]

Awesome. Thanks for taking the time and sending the "love letter" ;-) gonna try it on my advent 4211 and see how it goes. Would be great if we can get some more people that knows about it on the project, and have it integrated on the kernel. Coffelius did a great job and his version fixed some problems.

I'll post how the driver goes for me. I can test it in different environments, wep128, wpa, and WPA2-EAP

I asked to the Three Wizard Kings (the equivalent of Santa Claus here in Spain) for a Intel 3945 card.... but if this driver works great before that... maybe they give me some other different upgrade... like a memory module for instance :-D

Regards.

[Goldenear (goldenear)]

I've just compiled and installed the latest driver from Realtek, but I still have a problem with multicast :(

Could somebody else confirm that multicast is not working ? for exemple, both avahi and ipv6 autoconf don't work.

Is there an email to report that to Realtek ?

[Artyom Pervukhin (logus)]

I confirm that multicast is not working. Atheros chipset card works with the same AP having multicast support, but RTL does not.

[boskicinek (boski-cinek)]

@Goldenear: <email address hidden>

[Jason (jxself)]

Looks like upstream kernel support is forthcoming...

"Looks like this is a MiniPCIE card, so the chip is essentially an RTL8187 or RTL8187B with the USB communication part replaced with a PCI Express one. Given the existence of this open-source driver, adding support for it into rtl818x should not really be a problem."

http://article.gmane.org/gmane.linux.kernel.wireless.general/25466

[Double12 (double12)]

Hi,

I installed the latest driver .deb for 2.6.27-9.
http://boskastrona.ovh.org/download/[e-mail]

Now, KNetworkManager and iwconfig at least see the wlan0 device. But KNetworkManager still doesn't list the available networks and when I try to connect manually, it doesn't work.

Does anyone have an idea what to do?

Thanks.

[boskicinek (boski-cinek)]

Double12 pisze:
> Hi,
>
> I installed the latest driver .deb for 2.6.27-9.
> http://boskastrona.ovh.org/download/[e-mail]
>
> Now, KNetworkManager and iwconfig at least see the wlan0 device. But
> KNetworkManager still doesn't list the available networks and when I try
> to connect manually, it doesn't work.
>
> Does anyone have an idea what to do?

Did you turn on your WiFi (Fn+F11 --> active "satellite" led)?

--
Greets, BeCe
(http://boskastrona.ovh.org)

[Coffelius (coffelius)]

The differences with the last version of realtek driver.
Changes to Makefiles and documents no included.

diff -r rtl8187se_linux_26.1023.0928.2008/ieee80211/ieee80211.h
rtl8187se_linux_26.1023.1118.2008/ieee80211/ieee80211.h
1487c1487
< extern inline void *ieee80211_priv(struct net_device *dev)
---
> static inline void *ieee80211_priv(struct net_device *dev)
Sólo en rtl8187se_linux_26.1023.0928.2008/ieee80211: ieee80211_rx.o
Sólo en rtl8187se_linux_26.1023.0928.2008/ieee80211: .ieee80211_rx.o.cmd
diff -r rtl8187se_linux_26.1023.0928.2008/ieee80211/ieee80211_softmac.c
rtl8187se_linux_26.1023.1118.2008/ieee80211/ieee80211_softmac.c
1100a1101,1106
> {
> if (ieee->iw_mode == IW_MODE_ADHOC)
> {//as Windows will set pairwise key same as the group key
which is not allowed in Linux, so set this for IOT issue. WB 2008.07.
07
> memcpy(&ieee->wpa_ie[14], &ieee->wpa_ie[8], 4);
> }
>
1101a1108,1109
> }
>
1467a1476,1477
> if (beacon->capability & WLAN_CAPABILITY_SHORT_PREAMBLE)
> hdr->capability |=
cpu_to_le16(WLAN_CAPABILITY_SHORT_PREAMBLE);
1969c1979
< ieee->seq_ctrl[i] = 0;
---
> //ieee->seq_ctrl[i] = 0;
diff -r rtl8187se_linux_26.1023.0928.2008/rtl8185/ieee80211.h
rtl8187se_linux_26.1023.1118.2008/rtl8185/ieee80211.h
1487c1487
< extern inline void *ieee80211_priv(struct net_device *dev)
---
> static inline void *ieee80211_priv(struct net_device *dev)

On Sat, Nov 29, 2008 at 4:11 PM, boskicinek <email address hidden> wrote:

> After I sent a "love letter" to realtek, they sent me updated drivers
> (see attachment). Package is still named r1023, but the date has changed
> (from 0928 to 1118) and of course the source code. I'm using it right
> now and it works much more stable for me than the old one, although I'm
> still getting huge latencies from time to time.
>
> You can also get deb package I prepared for 2.6.27.10 kernel:
>
> http://boskastrona.ovh.org/download/[e-mail]
>
> ** Attachment added: "rtl8187se_linux_26.1023.1118.2008.tar.gz"
>
> http://launchpadlibrarian.net/20052864/rtl8187se_linux_26.1023.1118.2008.tar.gz
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gabriel Ortega <email address hidden> http://coffelius.bloggear.net

[Coffelius (coffelius)]

svn upgraded
http://code.google.com/p/msi-wind-linux/source/detail?r=20
some upgrades from boskicinek lover letters response and some debugging flood
cleaned

[Coffelius (coffelius)]

hi. i uploaded another upgrade to the svn
http://code.google.com/p/msi-wind-linux/source/detail?r=21

I was working on problems with the adaptive rate. To fix some problems with my access point

Log message

few cleaning iwpriv cmds, iwpriv wlan0 forcerate works. workarround, start
linking with 11MB rate, and then use adaptive rate upgrade if forcerate is 0

[Sergei (Nolar) Vasilyev (nolar)]

Having a strange problem with that driver (all of [e-mail], [e-mail] and manually compiled rtl8187se_linux_26.1023.0928.2008) on a very fresh Intrepid Ibex. Tried with NetworkManager, wicd, and manually (sudo wpa_supplicant -ddddd -Dwext -iwlan0 so on...).

In all those variants, "lsmod" says I have r8180 loaded with all ieee-dependents; "sudo iwlist scan" CAN see wireless networks, including my own. But it does not connect with wpa/wpa2. It just prints a lot of its log messages, makes few timeouts ~5-10sec, and nothing happens.

Part of log file is uploaded to http://nolar.info/storage/wpa.log (my ssid is IxtiAndre, bssid is 00:1d:so...on...). Tuning ap_scan and other parameters in wpa_supplicant.conf makes no effect (though supplicant's behavior changes and log becomes different, no result achieved).

I can not guess why does this happen: fresh install, strandard routine from almost all wikis, and it doesnt work.

Any ideas? What to check? What to read?

PS: MSI Wind U100, Ubuntu 8.10, rtl8187se (via lspci).

[boskicinek (boski-cinek)]

Sergei (Nolar) Vasilyev wrote:

> I can not guess why does this happen: fresh install, strandard routine
> from almost all wikis, and it doesnt work.
>
> Any ideas? What to check? What to read?

It's because those drivers simply sucks. I have exactly the same
problem. I don't know why, but sometimes changing wireless channel in
your AP helps. You can also try to reset card/drivers with script I've
wrote (see attachment).

[Sergei (Nolar) Vasilyev (nolar)]

I've solved my first issue. WiFi-router (Asus WL500g premium) only supports WEP40 as a group cipher (can be seen in "iwlist scan"), and wicd default templates contain only CCMP+TKIP both for pairwise and group ciphers. Added WEP40 into /etc/wicd/encryption/templates/wpa (line with "group="), and it had connected.

Well, also I've updated to linux-2.6.27.11 from proposed updates and installed deb-package with the driver for this kernel version. But I think, something similar should help in default Intrepid Ibex installation. Will test a bit later.

Now I have another problem with wireless. It floods dmesg & /var/log/kern.log with these lines :

Jan 3 01:19:39 nolar-wind kernel: [12325.394582] CCMP: replay detected: STA=00:1d:60:33:60:07 previous PN 0000000810a1 received PN 0000000810a1
Jan 3 01:19:41 nolar-wind kernel: [12327.751327] CCMP: replay detected: STA=00:1d:60:33:60:07 previous PN 000000081af1 received PN 000000081af1
Jan 3 01:19:45 nolar-wind kernel: [12331.333683] CCMP: replay detected: STA=00:1d:60:33:60:07 previous PN 000000082b2a received PN 000000082b2a
Jan 3 01:19:47 nolar-wind kernel: [12333.996524] CCMP: replay detected: STA=00:1d:60:33:60:07 previous PN 00000008371e received PN 00000008371e
Jan 3 01:19:55 nolar-wind kernel: [12341.983993] CCMP: replay detected: STA=00:1d:60:33:60:07 previous PN 000000085a8c received PN 000000085a8c
Jan 3 01:19:59 nolar-wind kernel: [12345.260866] CCMP: replay detected: STA=00:1d:60:33:60:07 previous PN 0000000868d0 received PN 0000000868d0
Jan 3 01:20:00 nolar-wind kernel: [12346.694268] CCMP: replay detected: STA=00:1d:60:33:60:07 previous PN 000000086f3e received PN 000000086f3e
Jan 3 01:20:00 nolar-wind kernel: [12347.001842] CCMP: replay detected: STA=00:1d:60:33:60:07 previous PN 00000008708a received PN 00000008708a
Jan 3 01:20:04 nolar-wind kernel: [12350.483777] CCMP: replay detected: STA=00:1d:60:33:60:07 previous PN 00000008800c received PN 00000008800c
Jan 3 01:20:08 nolar-wind kernel: [12354.891909] CCMP: replay detected: STA=00:1d:60:33:60:07 previous PN 0000000893ea received PN 0000000893ea

Noticed only when actively using network (copying files, so on). Same for TKIP. Note that "previous" and "received" numbers are the same, but the distance between lines is not sequental (almost random).

Is this an issue with wpa_supplicant, this driver or maybe something other?

[mennendez (raimennendez)]

Hi,

I have a Msi Wind U100 with Ubuntu 8.10 and the version of kernel 2.6.27-9-generic; I installed the driver for my wireless card "rtl8187se_linux_26.1023.0928.2008": nothing worked; than I installed [e-mail] (Intrepid) and than on other time "rtl8187se_linux_26.1023.0928.2008". Now the wireless card works with the WEP encryption (I don't know if it works with wpa) but when I download something the card makes a very strange and bad noise. When I disable the wireless card this noise disappears. I attached the noise recorded.

Any idea?

[mennendez (raimennendez)]

Sorry, it was a bad configuration in the volume control.

[mennendez (raimennendez)]

the speaker circuitry is picking up RF from the card

[none (ubuntu-bugs-nullinfinity-deactivatedaccount)]

A version of this driver was recently added to the main kernel tree: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c8d86be38785705aca77e33933298c320a1bf2a5

[Adam McDaniel (adamrmcd)]

Interesting. Note the staging directory though. I think that this is a preliminary step before full support is available.

I'm curious to see how the linux kernel will merge the rtl8187se's ieee80211 stack with the existing kernel's stack.

I attempted such a merge once, but found that the rtl8187se's code relied on non-standard ieee80211 code (hence the alternative stack) and I was really uninterested in rewriting the entire driver to make it work. :T

[boskicinek (boski-cinek)]

Any chance to have this driver by default in Jaunty? It looks like nothing happens in this bugreport and it's strange, because from what I've heard Ubuntu team wants to focus on netbook market. Well, supporting this WLAN NIC is necessary to provide support for really many netbooks users.

[warmrobot (imfrolov)]

Yeah, that's very strange. And as I can see, today is FeatureFreeze day in Jaunty schedule. :-(
Before each update I have to check this(http://forums.msiwind.net/debian/rtl8187se-drivers-for-ubuntu-and-deb-packages-t4954.html) page for driver update. Good news that it is updated without delay. :-)

[Jeffrey Seguerra (jepong)]

I already upgraded to Kubuntu Jaunty Alpha 4 with linux kernel 2.6.28 and wireless is not yet detected out of the box. Does anyone have a compiled.deb for this?

[David Rando (david-rando)]

Well, my comment is not very useful (maybe a bit) but this card works terrible. What i've done is remove it from the laptop and buy a brand new intel 3945 for 20$ on ebay. Problem resolved. Ubuntu loads it out of the box and works great.

[Dax Solomon Umaming (knightlust)]

The source is available in Jaunty as rtl8187se-source
just need to create a module via module-assistant

[Yannick Defais (sevmek)]

You can use those commands:

sudo aptitude install rtl8187se-source
sudo m-a auto-install rtl8187se

[boskicinek (boski-cinek)]

Hi, I got another driver release from Realtek. See attachment and check my homepage (http://boskastrona.ovh.org) for Intrepid package and additional info.

[Jeffrey Seguerra (jepong)]

@Dax and Yannick

You tip works great! Thanks

[Jeffrey Seguerra (jepong)]

upgraded to kubuntu jaunty alpha 6 on my msi wind... wireless is already detected but I haven't tried to hook it up with a wifi device. anyone experience this as well?

[Sergei (Nolar) Vasilyev (nolar)]

In Ubuntu 9.04 alpha 6 it works out of the box even with WPA/WPA2. (MSI Wind U100)

[Jeffrey Seguerra (jepong)]

Kubuntu 9.04 beta. Wireless detected but I cannot connect to a unsecured wifi hotspot.

[Jostein Topland (topland)]

The latest drivers works perfectly fine with MSI Wind.
Though with Slackware, and possibly other GNU/Linux distros, DNS servers might be set up incorrectly. This is noticeable when opening websites with Firefox, and the status message says "Looking up..." for a loooong and painful time (~2min) when it ought to take less than a second.
To fix this edit /etc/resolve.conf(as root) and type the correct DNS server. You will get even more speed typing the DNS server from you ISP(not 192.168.0.1 or 10.0.0.1, typically). Log in to your router to find this DNS address. My /etc/resolve.conf has only one line: "nameserver 84.208.20.110". This is for Get in Norway.
Also, some programs edit this file when receiving new IP. In Slackware, dhclient does this. There is probably a command for the program for not letting it change the /etc/resolve.conf, or maybe you can set it to read-only. So watch out for that.

Jostein

[jtniehof (jtniehof)]

The stock kernel on Jaunty works fine for me on my Eee 900HD. Kernel 2.6.28-11.41. lspci -v gives "RTL8187SE Wireless LAN Controller (rev 22)" and "Kernel driver in use: rtl8180" "Kernel modules: rtl8187se"

Connected with unsecured, WPA2-PSK, and WPA2 802.1x, as well as vpnc on top of a wireless connection.

[Bryan Wu (cooloney)]

Hi all,

It seems that I am pretty new for this issue. But from a point view of Ubuntu kernel team, we prefer to encourage Realtek or people like you guys to merge the driver to upstream mainline. It is much easier for us maintain the driver. And It looks like Jaunty kernel works fine for you guys. If you can confirm that, I plan to set the status of this issue to "Fixed in release".

Thanks
-Bryan

[boskicinek (boski-cinek)]

Yes, it works out of the box, but they still give us some problems (especially after waking up from suspend and after longer period of time).

[Bryan Wu (cooloney)]

Great. I found the rtl8187se driver is in stage tree of Jaunty kernel. And also it requires too many changes to ieee80211 stack. So there is no reason for us to back port this big change to Hardy and Intrepid. Please use Jaunty. If you guys find any new issue about Jaunty, please fire new bug.

-Bryan

[Kiran Jonnalagadda (jackerhack)]

Just upgraded to Jaunty. It doesn't work for me. :(

dmesg indicates that the card has been detected and drivers have been loaded successfully, but I can neither see the WPA2 Personal network that I have here, nor connect to it by name. This was working until the upgrade; three other machines here continue to work with that network.

Running `sudo iwlist wlan0 scan` returns immediately with no results.

[boskicinek (boski-cinek)]

Kiran Jonnalagadda wrote:
> Just upgraded to Jaunty. It doesn't work for me. :(
>
> dmesg indicates that the card has been detected and drivers have been
> loaded successfully, but I can neither see the WPA2 Personal network
> that I have here, nor connect to it by name. This was working until the
> upgrade; three other machines here continue to work with that network.
>
> Running `sudo iwlist wlan0 scan` returns immediately with no results.

Well, this was happening from time to time also on intrepid and hardy.
Just power off your computer for a while (a minute or so) and try again.

--
Greets, BeCe
(http://boskastrona.ovh.org)

[Jostein Topland (topland)]

Kiran: Did you try 'sudo ifconfig wlan0 up', or whatever your wlan device is.

On Thu, Apr 30, 2009 at 8:16 AM, Kiran Jonnalagadda <email address hidden> wrote:
> Just upgraded to Jaunty. It doesn't work for me. :(
>
> dmesg indicates that the card has been detected and drivers have been
> loaded successfully, but I can neither see the WPA2 Personal network
> that I have here, nor connect to it by name. This was working until the
> upgrade; three other machines here continue to work with that network.
>
> Running `sudo iwlist wlan0 scan` returns immediately with no results.
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: Fix Released
> Status in “linux-meta” source package in Ubuntu: Invalid
>
> Bug description:
> The RTL8187SE is a miniPCI version of the Realtek 8187 wireless chipset. Until recently, it had no linux driver. A user on the msiwind.net forums emailed realtek about this, and they received a driver that was not listed on their site. The driver didn't compile for the 2.6.24 kernel included in ubuntu hardy, but after I made some modifications, it compiles and is reported to work.
>
> I have attached the driver from realtek. I will attach a patch in the next post.
>

[Kiran Jonnalagadda (jackerhack)]

Jostein: yes. the interface is up and dmesg says everything is fine, but network manager and iwscan can't find or join any wireless networks. Taking boskicinek's suggestion to try powering off for a while...

[Jostein Topland (topland)]

Kiran: if your compute is a laptop, do you have a Fn+F[1-12] function
for enabling the wireless network interface?

On Thu, Apr 30, 2009 at 11:41 AM, Kiran Jonnalagadda <email address hidden> wrote:
> Jostein: yes. the interface is up and dmesg says everything is fine, but
> network manager and iwscan can't find or join any wireless networks.
> Taking boskicinek's suggestion to try powering off for a while...
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: Fix Released
> Status in “linux-meta” source package in Ubuntu: Invalid
>
> Bug description:
> The RTL8187SE is a miniPCI version of the Realtek 8187 wireless chipset. Until recently, it had no linux driver. A user on the msiwind.net forums emailed realtek about this, and they received a driver that was not listed on their site. The driver didn't compile for the 2.6.24 kernel included in ubuntu hardy, but after I made some modifications, it compiles and is reported to work.
>
> I have attached the driver from realtek. I will attach a patch in the next post.
>

[Kiran Jonnalagadda (jackerhack)]

Jostein: I left my machine powered off for about an hour, tried again, and now it's working. Guess that fixes it for me.

However, it seems like multicast is still not supported with this driver, because Avahi's mdns-scan still can't find any services not running on localhost.

[mf (mat-fletcher)]

just wondering where the fix is? i'm still getting the dropout problem on ubuntu 9.10. does not seem to be fixed to me or have i missed something?

[joanna (jnnjaros)]

I have the same problem on MSI WInd U100 as mf. Where can I find the fix?

[mf (mat-fletcher)]

i have a new driver from realtek. It is not perfect and the bug is still
present but it is not quite as serious as the stock kernel module.

In short i have less timeouts on the newer driver.

You can get it by emailing realtek support and they will email the source to
you, or i can post it somewhere for you

On Fri, Dec 18, 2009 at 1:34 PM, joanna <email address hidden> wrote:

> I have the same problem on MSI WInd U100 as mf. Where can I find the
> fix?
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[mf (mat-fletcher)]

I contacted Realtek by email since nobody answered this bugtrack thread, whats the point in encouraging people to post here if nobody answers?

Anyway, they were fairly helpful and emailed me this driver to compile on Karmic, It works, i still get drop outs but it is not as bad as the stock driver. This is a better driver. I have found that it helps a lot to keep your connection alive by setting off a ping to somewhere (your router) and leaving it pinging all the time as a sort of crude keep alive.

i hope this helps

[LG Marcondes (lgmarcondes)]

Hi,

I'm using openSuse 11.2 and my drop out problems stops when I run the
following script:

>
> while [ 1 ]; do
    VALUE=`iwconfig wlan0 | grep -o "Bit Rate=54 Mb/s" | wc -l`
    if [ "$VALUE" -ne "1" ]; then
        echo "iwconfig wlan0 rate 54M"
        iwconfig wlan0 rate 54M
        sleep 10
    fi
done

>
>
It checks the result of the command iwconfig wlan0 and see if the bit rate
is low, if so sets to 54M. After 10 seconds it checks again.

I hope it could help someone...

---
Luiz Gustavo

On Sat, Dec 19, 2009 at 8:21 AM, mf <email address hidden> wrote:

> I contacted Realtek by email since nobody answered this bugtrack thread,
> whats the point in encouraging people to post here if nobody answers?
>
> Anyway, they were fairly helpful and emailed me this driver to compile
> on Karmic, It works, i still get drop outs but it is not as bad as the
> stock driver. This is a better driver. I have found that it helps a
> lot to keep your connection alive by setting off a ping to somewhere
> (your router) and leaving it pinging all the time as a sort of crude
> keep alive.
>
> i hope this helps
>
> ** Attachment added: "Better driver supplied by Realtek by email"
>
> http://launchpadlibrarian.net/36967697/rtl8187se_linux_26.1030.1201.2009.release.tar.gz
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Pablo Castellano (pablocastellano)]

My netbook uses rtl8187se and was automatically detected in ubuntu 10.04 beta1.
Unfortunately I'm also seeing that instability with WPA, but that's a different issue.
I think this bug can be closed.

[mf (mat-fletcher)]

it's still a bug until they fix it. It's not an ubuntu problem anyway, it's
realtek.

On Sat, Apr 10, 2010 at 5:26 AM, Pablo Castellano <email address hidden>wrote:

> My netbook uses rtl8187se and was automatically detected in ubuntu 10.04
> beta1.
> Unfortunately I'm also seeing that instability with WPA, but that's a
> different issue.
> I think this bug can be closed.
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Pablo Castellano (pablocastellano)]

@mf:
No, taking the bug title as reference:
It claims that there's "no support for realtek rtl8187se", which was true in the past. But I'm writing this answer from my netbook, using ubuntu and the rtl8187se driver.
A new bugreport should be opened

[mf (mat-fletcher)]

well ok, since you put it like that.

There has been partial support since 8.04. I think it's the same driver.
the problem is getting realtek to ackowledge that this is a bug - which they
do not., They will send you new drivers but they all have the same problem
where the 'rate' drops to 1Mpbs. The only way to use this driver is to use
a script to reset the rate to 54Mbps every 3 seconds. Not perfect but it
does allow you to use the driver.

On Sun, Apr 11, 2010 at 7:05 AM, Pablo Castellano <email address hidden>wrote:

> @mf:
> No, taking the bug title as reference:
> It claims that there's "no support for realtek rtl8187se", which was true
> in the past. But I'm writing this answer from my netbook, using ubuntu and
> the rtl8187se driver.
> A new bugreport should be opened
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Pablo Castellano (pablocastellano)]

 From my experience with realtek with another sound driver, I wouldn't
expect their answer.

BTW, I have tried with ndiswrapper and winxp drivers and it works like a
charm. No more disconnections :)

On 11/04/10 16:32, mf wrote:
> well ok, since you put it like that.
>
> There has been partial support since 8.04. I think it's the same driver.
> the problem is getting realtek to ackowledge that this is a bug - which they
> do not., They will send you new drivers but they all have the same problem
> where the 'rate' drops to 1Mpbs. The only way to use this driver is to use
> a script to reset the rate to 54Mbps every 3 seconds. Not perfect but it
> does allow you to use the driver.
>
>
> On Sun, Apr 11, 2010 at 7:05 AM, Pablo Castellano
> <email address hidden>wrote:
>
>
>> @mf:
>> No, taking the bug title as reference:
>> It claims that there's "no support for realtek rtl8187se", which was true
>> in the past. But I'm writing this answer from my netbook, using ubuntu and
>> the rtl8187se driver.
>> A new bugreport should be opened
>>
>> --
>> no support for realtek rtl8187se
>> https://bugs.launchpad.net/bugs/246141
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>>
>

[mf (mat-fletcher)]

with a steady 54Mbps?

i never got disconnections, just a drop in throughput that made it unusable

your right about realtek, they seem very uninterested at best.
On Sun, Apr 11, 2010 at 2:18 PM, Pablo Castellano <email address hidden>wrote:

> From my experience with realtek with another sound driver, I wouldn't
> expect their answer.
>
> BTW, I have tried with ndiswrapper and winxp drivers and it works like a
> charm. No more disconnections :)
>
> On 11/04/10 16:32, mf wrote:
> > well ok, since you put it like that.
> >
> > There has been partial support since 8.04. I think it's the same driver.
> > the problem is getting realtek to ackowledge that this is a bug - which
> they
> > do not., They will send you new drivers but they all have the same
> problem
> > where the 'rate' drops to 1Mpbs. The only way to use this driver is to
> use
> > a script to reset the rate to 54Mbps every 3 seconds. Not perfect but it
> > does allow you to use the driver.
> >
> >
> > On Sun, Apr 11, 2010 at 7:05 AM, Pablo Castellano
> > <email address hidden>wrote:
> >
> >
> >> @mf:
> >> No, taking the bug title as reference:
> >> It claims that there's "no support for realtek rtl8187se", which was
> true
> >> in the past. But I'm writing this answer from my netbook, using ubuntu
> and
> >> the rtl8187se driver.
> >> A new bugreport should be opened
> >>
> >> --
> >> no support for realtek rtl8187se
> >> https://bugs.launchpad.net/bugs/246141
> >> You received this bug notification because you are a direct subscriber
> >> of the bug.
> >>
> >>
> >
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Pablo Castellano (pablocastellano)]

On 12/04/10 00:16, mf wrote:
> with a steady 54Mbps?
>
> i never got disconnections, just a drop in throughput that made it
> unusable
>
> your right about realtek, they seem very uninterested at best.

Yes, that's what I meant, drop in throughput. And yes, 54Mbps, try it.

http://pablogubuntu.blogspot.com/2010/04/rtl8187se-y-realtek.html
(I don't know if it's ok to leave links here in launchpad, sorry if it's
not)

[mf (mat-fletcher)]

Thanks for the link Pablo, i dual boot with windows7 on my netbook and have
found that the range on the windows driver is much better, i can get a much
better signal than on ubuntu.

I'll try ndiswrapper maybe but the last time i did it borked my system.

Muchos Gracias amigo

On Mon, Apr 12, 2010 at 6:57 AM, Pablo Castellano <email address hidden>wrote:

> On 12/04/10 00:16, mf wrote:
> > with a steady 54Mbps?
> >
> > i never got disconnections, just a drop in throughput that made it
> > unusable
> >
> > your right about realtek, they seem very uninterested at best.
>
> Yes, that's what I meant, drop in throughput. And yes, 54Mbps, try it.
>
> http://pablogubuntu.blogspot.com/2010/04/rtl8187se-y-realtek.html
> (I don't know if it's ok to leave links here in launchpad, sorry if it's
> not)
>
> --
> no support for realtek rtl8187se
> https://bugs.launchpad.net/bugs/246141
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Hans Henrik (hanshenrik123)]

as posted previously, ubuntu does got support for RTL8187SE now, so this bug report should be closed.
However, due to the bugs (https://bugs.launchpad.net/ubuntu/+source/rtl8187se/+bugs?field.status:list=NEW), RTL8187SE is basically useless on ubuntu, primarily due to https://bugs.launchpad.net/ubuntu/+source/rtl8187se/+bug/416488
(i nearly have to sit on top of the router to get connection.. >.<)

[Pablo Castellano (pablocastellano)]

I have opened a bugreport in the kernel bugzilla. Follow it here:
https://bugzilla.kernel.org/show_bug.cgi?id=15932

[Alex French (grackle)]

­­ ­­­­­­­ ­­­­­*Your gi­­­­­rl_frie­­­­­­­nd w­­­i­­­ll f­­­­eel
t­­­­­­­he eff_ect­­*_<http://deivery-deliveyr4succeproudcts.vv.cc/752s4k.pl>­­­.
­­.

.

[jno (jnoster)]

Looks like something is broken again - just performed a routine update of 12.10 and have lost wifi connectivity...
Still digging...