Bug 2175

The exact card is RTL8187SE/RTL8101E/RTL8102E (well, that's what's showing in lspci) with r8180 and r8169 driver modules.

It's also not working with kernel 3.2.3-2.fc16.

Still failing in 3.26. Please let me know anything I can do to assist with resolving this.

(In reply to comment #1)
> The exact card is RTL8187SE/RTL8101E/RTL8102E (well, that's what's showing in
> lspci) with r8180 and r8169 driver modules.

r8169 is for a LAN chip; I don't know any r8180; do you mean rtl8180? That driver is part of the kernel. 

What does "lspci -nn | grep -i net" give out on your system.

But even if it is one of the staging drivers: From what I see I can't help much here; staging drivers are known to have problems, that's why they are not part of the regular kernel packages in Fedora; nevertheless they are of use for some users, that's why we provide them. If you have problems then it's best to talk to the upstream developers about it (if there are any), as they know the hardware and the drivers.

(In reply to comment #3)
> (In reply to comment #1)
> > The exact card is RTL8187SE/RTL8101E/RTL8102E (well, that's what's showing in
> > lspci) with r8180 and r8169 driver modules.
> 
> r8169 is for a LAN chip; I don't know any r8180; do you mean rtl8180? That
> driver is part of the kernel. 
> 
> What does "lspci -nn | grep -i net" give out on your system.

Thanks Thorsten,

lspci -nn | grep -i net gives me
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8187SE Wireless LAN Controller [10ec:8199] (rev 22)
(that's when booted from working 3.2.2)

lspci -a run on 3.2.5 gave me
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8187SE Wireless LAN Controller (rev 22)
	Subsystem: Micro-Star International Co., Ltd. Device 6894
	Flags: bus master, fast devsel, latency 0, IRQ 17
	I/O ports at ec00 [size=256]
	Memory at febfc000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number 00-00-d2-2a-48-21-24-00
	Kernel driver in use: r8180
	Kernel modules: r8187se

I'm not sure where it's coming from - I was assuming it was from kmod-staging. Do you have any suggestions how I can figure out where I'm getting it from (I can't recall manually installing it)? For a long time I was using ndiswrapper, but when there was a long hiatus in kernel compatibility for it, I disabled it, installed kmod-staging,and found that the wlan was working. I didn't think to confirm that that was the source of the driver.

find * -name '*r8187se*' -print
modules/3.2.2-1.fc16.i686/extra/staging/r8187se.ko
modules/3.2.5-3.fc16.i686/extra/staging/r8187se.ko
modules/3.2.3-2.fc16.i686/extra/staging/r8187se.ko
modules/3.2.6-3.fc16.i686/extra/staging/r8187se.ko

I have same problem with my Realtek rtl8187se wireless card after last kernel updates ((( It's not work...

NetworkManager don't see any wireless networks.

ifconfig command do not shows wlan0 interface, but iwconfig command shows it... Are there some config problem?

yum install kmod-staging throws up this:
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_storvsc.ko needs unknown symbol vmbus_driver_unregister
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_storvsc.ko needs unknown symbol vmbus_sendpacket
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_storvsc.ko needs unknown symbol vmbus_close
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_storvsc.ko needs unknown symbol vmbus_recvpacket
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_storvsc.ko needs unknown symbol vmbus_open
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_storvsc.ko needs unknown symbol vmbus_sendpacket_multipagebuffer
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_storvsc.ko needs unknown symbol __vmbus_driver_register
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_netvsc.ko needs unknown symbol vmbus_driver_unregister
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_netvsc.ko needs unknown symbol vmbus_sendpacket
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_netvsc.ko needs unknown symbol vmbus_teardown_gpadl
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_netvsc.ko needs unknown symbol vmbus_close
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_netvsc.ko needs unknown symbol vmbus_recvpacket_raw
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_netvsc.ko needs unknown symbol vmbus_open
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_netvsc.ko needs unknown symbol __vmbus_driver_register
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_netvsc.ko needs unknown symbol vmbus_establish_gpadl
WARNING: /lib/modules/3.2.6-3.fc16.x86_64/extra/staging/hv_netvsc.ko needs unknown symbol vmbus_sendpacket_pagebuffer

FYI, r8180 is part of the rtl8187se driver (think of it as "sub-driver"  of rrl8187se).

But I have not idea where the problem lies; seems the drivers hasn't been touched much over the past few months:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=history;f=drivers/staging/rtl8187se;hb=HEAD

So either something in other parts of the kernel changed and broke the driver for you or some changes in NetworkManager are the reason. Whatever it is: I can't help you much, sorry, as I don't have the hardware :-/

BTW, the hv_netvsc.ko messages should not have anything to do with this

I'm adding this in case it's useful to anyone searching: this problem seems to have been resolved in kernel 3.3, I'm typing this on such a connection.

Yes, it works fine in 3.3! Fixed