Help with realtek USB 802.11 N

I’ve tried many things, just starting off in Linux.
Running latest updates of SUSE KDE (GNOME needs updating but same issues).

my lsusb is:
Bus 001 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN
Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

my lsmod is:
Module Size Used by
fuse 80332 3
xt_tcpudp 12757 2
xt_pkttype 12457 3
xt_LOG 17248 10
xt_limit 12542 10
af_packet 30682 0
ip6t_REJECT 12827 3
nf_conntrack_ipv6 14061 3
nf_defrag_ipv6 13691 1 nf_conntrack_ipv6
ip6table_raw 12604 1
ipt_REJECT 12486 3
iptable_raw 12599 1
xt_CT 12630 4
iptable_filter 12707 1
ip6table_mangle 12621 0
nf_conntrack_netbios_ns 12586 0
nf_conntrack_broadcast 12542 1 nf_conntrack_netbios_ns
nf_conntrack_ipv4 14502 3
nf_defrag_ipv4 12650 1 nf_conntrack_ipv4
ip_tables 17988 2 iptable_raw,iptable_filter
xt_conntrack 12665 6
nf_conntrack 80684 6 nf_conntrack_ipv6,xt_CT,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ipv4,xt_conntrack
ip6table_filter 12712 1
ip6_tables 17970 3 ip6table_raw,ip6table_mangle,ip6table_filter
x_tables 26125 15 xt_tcpudp,xt_pkttype,xt_LOG,xt_limit,ip6t_REJECT,ip6table_raw,ipt_REJECT,iptable_raw,xt_CT,iptable_filter,ip6table_mangle,ip_tables,xt_conntrack,ip6table_filter,ip6_tables
mperf 12604 0
tg3 142751 0
shpchp 32156 0
pci_hotplug 33982 1 shpchp
ppdev 17399 0
joydev 17162 0
sg 35636 0
sr_mod 21873 0
parport_pc 36450 0
iTCO_wdt 17653 0
button 13627 0
snd_intel8x0 33101 2
snd_ac97_codec 113846 1 snd_intel8x0
ac97_bus 12671 1 snd_ac97_codec
snd_pcm 97003 2 snd_intel8x0,snd_ac97_codec
snd_seq 63595 0
snd_timer 24319 2 snd_pcm,snd_seq
snd_seq_device 14138 1 snd_seq
parport 40727 2 ppdev,parport_pc
floppy 59447 0
cdrom 41399 1 sr_mod
iTCO_vendor_support 13503 1 iTCO_wdt
serio_raw 13156 0
i2c_i801 17500 0
pcspkr 12631 0
snd 70562 10 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_seq,snd_timer,snd_seq_device
soundcore 14600 1 snd
snd_page_alloc 14037 2 snd_intel8x0,snd_pcm
microcode 22851 0
autofs4 33270 2
hid_logitech_dj 18144 0
usbhid 51476 1 hid_logitech_dj
hid 81709 2 hid_logitech_dj,usbhid
ohci_hcd 36280 0
uhci_hcd 35656 0
radeon 869516 3
ttm 70075 1 radeon
ehci_hcd 59456 0
drm_kms_helper 45454 1 radeon
drm 232083 5 radeon,ttm,drm_kms_helper
i2c_algo_bit 13198 1 radeon
i2c_core 33926 5 i2c_i801,radeon,drm_kms_helper,drm,i2c_algo_bit
usbcore 194042 5 usbhid,ohci_hcd,uhci_hcd,ehci_hcd
processor 43535 0
thermal_sys 19936 1 processor
usb_common 12526 1 usbcore
hwmon 12912 2 radeon,thermal_sys
scsi_dh_rdac 17172 0
scsi_dh_alua 12845 0
scsi_dh_hp_sw 12746 0
scsi_dh_emc 17062 0
scsi_dh 14214 4 scsi_dh_rdac,scsi_dh_alua,scsi_dh_hp_sw,scsi_dh_emc
ata_generic 12780 0
ata_piix 26360 2
ahci 25497 0
libahci 29902 1 ahci
libata 196330 4 ata_generic,ata_piix,ahci,libahci

I’ve gotten close using an ubuntu forum editing the blacklist.conf file pointing to the rt2800 ralink driver, the system saw my device, had LED activity and got as close as attempting to connect, but it would never resolve.

Some assistance would be much appreciated for this newbie!

Thanks!

http://linuxwireless.org/en/users/drivers/rtl819x looks like the rtl8192cu driver should work with my device?!? Can’t figure out the implementation though.

Thanks again!

On 03/14/2013 04:36 PM, rpmtech wrote:
>
> http://linuxwireless.org/en/users/drivers/rtl819x looks like the
> rtl8192cu driver should work with my device?!? Can’t figure out the
> implementation though.

No, that is NOT the correct driver. It is rtl8192cu, which is a regular part of
the kernel.

There is a major bug in that driver that was just found. It will be some time
before the fix percolates through the system. If you cannot wait, you will need
to patch the kernel sources and build your own kernel. If that is what you want
to do, let me know.