Forum › Forums › New users › New Users and General Questions › Wait, it "does not work right", okay, that was aimed at the Wireless. (Driver)
Tagged: RTL8192CUS Driver Linux HELP
- This topic has 13 replies, 4 voices, and was last updated Jul 29-3:11 pm by GuruSR.
-
AuthorPosts
-
July 10, 2019 at 6:01 pm #24337Member
GuruSR
First, it’s not my first Linux, probably won’t be my last, but I had an old Compaq Armada M300 with 392MB of ram just sitting there with an empty IDE->CF adapter, so I stuck a 32GB one in (UDMA7 for speed) and went ahead and installed it (using the USB stick on a pc that won’t boot from it, using a CD disc that lets me boot from a USB stick, yeah, confusing as all). Tried it on the USB stick first, it worked, tried installing it and it stalled (the CD disc’s grub is a bit “temper-mental” a restart fixed it).
So, now I have it all basic 17.4.1 (386) Full, but I have a small Netis WF-2110 150N mini adapter plugged into a USB 2.0 PCMCIA card adapter (yeah, totally all upgraded here). Sadly, I tried to scan for a connection and after doing so, the only way I could get the machine to respond was pull the power cord and battery out (yep, tried killing everything, didn’t help).
So, I went looking for a driver, the original OS (not immediately available), had an in-house driver that worked with it, so no joy there, basic MS driver from Realtek, great. I did have the driver mini-cd and found the driver file (attached) for it, well, MacOS and Linux are the only two, so sadly, no joy in using the Windows Driver installer. But if someone out there can take a peek or tell me if there is another driver for this RTL8192CUS that I can plug a wire into the laptop and acquire it, I’ll do so, but it’s been a very very very very long while since my Unix days and I don’t recall installing linux drivers well enough, why I am attaching the file I have for it, see if someone here can take a peek at it and give me a suggestion on what to do with it, I already have it on the machine, just not sure the procedure of installing it or if the driver I have will even work in AntiX.
(Right now, Windows 10 build 1903 has yet again failed to install on my other laptop, so much joy it’s not funny.)
GuruSR.
July 11, 2019 at 4:12 am #24343Member
fatmac
::Normally, you would put a driver into /lib/firmware & reboot, the system should then find & use it.
Linux (& BSD) since 1999
July 11, 2019 at 4:25 am #24344Member
Xecure
::I just checked, and antiX17.4 brings rtl8192cu drivers and firmware included. No need to install them. It could mean that the usb device is not being detected.
Check to see if your usb device is detected
lsusb
You should see an entry mentioning RTL8192CU. If so, then check to see if the module is loaded:
lsmod | grep "rtl8192"
It should say something like “rtl_usb number 1 rtl8192cu”Finally, check to see if there is any info in dmesg
dmesg | grep "rtl8192"
If there is any error, you will see it there.If it says that it is correctly loaded and there are no errors, try to see if ceni detects it:
sudo ceni
wlanX (where X is a number) should appear with a description “wireless MAC:ADDRESS rtl8192cu 802.11n USB WLAN”. Select and try to connect. If it freezes again, you may have to check that the device really works on other hardware. If it does, maybe you have to upgrade your kernel.Even if the drivers are included in the 4.9 kernel, I experienced myself with one device that wifi would not work until upgrading to a newer kernel. As I have experienced problems with 5.xx kernels, I recommend you download the antiX 4.19 kernel here (as a .deb file). Choose the correct one for your device (Thank anticapitalista for always giving us the best kernels with all security patches included).
64 bits: http://repo.antixlinux.com/stretch/pool/main/l/linux-4.19.52-antix.1-amd64-smp/linux-image-4.19.52-antix.1-amd64-smp_4.19.52-antix.1-amd64-smp-1_amd64.deb
32 bits PAE: http://repo.antixlinux.com/stretch/pool/main/l/linux-4.19.52-antix.1-686-smp-pae/linux-image-4.19.52-antix.1-686-smp-pae_4.19.52-antix.1-686-smp-pae-1_i386.deb
32-bits NON PAE: http://repo.antixlinux.com/stretch/pool/main/l/linux-4.19.52-antix.1-486-smp/linux-image-4.19.52-antix.1-486-smp_4.19.52-antix.1-486-smp-1_i386.deb
Move the corresponding kernel to a USB device and load and install it in your antiX 17.4 system. Restart and again follow the previous steps. If all seems well, try connecting through ceni.Let us know how it goes.
- This reply was modified 3 years, 9 months ago by Xecure. Reason: Correcting wording
antiX Live system enthusiast.
General Live Boot Parameters for antiX.July 11, 2019 at 9:09 am #24357Forum Admin
rokytnji
::To add to xsecure good post. We include inxi in AntiX and you will get better help with a
inxi -Fxzreport included in this thread.
- This reply was modified 3 years, 9 months ago by rokytnji. Reason: improper command line
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsJuly 21, 2019 at 11:06 am #24815MemberGuruSR
::I just checked, and antiX17.4 brings rtl8192cu drivers and firmware included. No need to install them. It could mean that the usb device is not being detected.
Check to see if your usb device is detected
lsusb
You should see an entry mentioning RTL8192CU. If so, then check to see if the module is loaded:
lsmod | grep "rtl8192"
It should say something like “rtl_usb number 1 rtl8192cu”Finally, check to see if there is any info in dmesg
dmesg | grep "rtl8192"
If there is any error, you will see it there.If it says that it is correctly loaded and there are no errors, try to see if ceni detects it:
sudo ceni
wlanX (where X is a number) should appear with a description “wireless MAC:ADDRESS rtl8192cu 802.11n USB WLAN”. Select and try to connect. If it freezes again, you may have to check that the device really works on other hardware. If it does, maybe you have to upgrade your kernel.Even if the drivers are included in the 4.9 kernel, I experienced myself with one device that wifi would not work until upgrading to a newer kernel. As I have experienced problems with 5.xx kernels, I recommend you download the antiX 4.19 kernel here (as a .deb file). Choose the correct one for your device (Thank anticapitalista for always giving us the best kernels with all security patches included).
64 bits: http://repo.antixlinux.com/stretch/pool/main/l/linux-4.19.52-antix.1-amd64-smp/linux-image-4.19.52-antix.1-amd64-smp_4.19.52-antix.1-amd64-smp-1_amd64.deb
32 bits PAE: http://repo.antixlinux.com/stretch/pool/main/l/linux-4.19.52-antix.1-686-smp-pae/linux-image-4.19.52-antix.1-686-smp-pae_4.19.52-antix.1-686-smp-pae-1_i386.deb
32-bits NON PAE: http://repo.antixlinux.com/stretch/pool/main/l/linux-4.19.52-antix.1-486-smp/linux-image-4.19.52-antix.1-486-smp_4.19.52-antix.1-486-smp-1_i386.deb
Move the corresponding kernel to a USB device and load and install it in your antiX 17.4 system. Restart and again follow the previous steps. If all seems well, try connecting through ceni.Let us know how it goes.
I put the driver I have into /lib/firmware, but am trying to get away from Firefox, the Intel Pro 100 LAN on it, is stuck at 320K download speed which is painful. dmesg did report that the driver is erroring now (after I got it online via LAN and manually updated/upgraded, painfully slow at 320K) “rtl8192cu: probe of 4-1:1.0 failed with error -12”, it is downloading and installing the new kernel slooowly as I type.
July 21, 2019 at 1:46 pm #24828MemberGuruSR
::Okay, after restarting by way of battery pulling (didn’t like the Wireless Off in the wicd network manager, but I believe I found the major issue now, is the PCMCIA to USB 2.0 adapter, it sees the devices but talking to them through it is apparently “inconsistent”. I really want to use it because of 2.0 speeds as apposed to 1.1 speeds and there being only 1 USB 1.1 port on it.
I’ll list what I can here, all via the PCMCIA USB 2.0 adapter:
lusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter Bus 004 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 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub lsmod: rtl8192cu 65536 0 rtl_usb 20480 1 rtl8192cu rtl8192c_common 45056 1 rtl8192cu rtlwifi 65536 3 rtl_usb,rtl8192c_common,rtl8192cu mac80211 536576 3 rtl_usb,rtlwifi,rtl8192cu dmesg: [ 48.394201] rtl8192cu: Chip version 0x10 [ 48.489958] rtl8192cu: Board Type 0 [ 48.490509] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [ 48.517327] usbcore: registered new interface driver rtl8192cu [ 71.834620] rtl8192cu: MAC auto ON okay! [ 71.927501] rtl8192cu: Tx queue select: 0x05I was able to connect via the onboard USB 1.1 with the device, but it won’t communicate via the PCMCIA 2.0 adapter. The Full_info.txt is pre-reboot, the Inxi.txt is post reboot with the new driver and such.
GuruSR.
- This reply was modified 3 years, 9 months ago by rokytnji.
Attachments:
July 22, 2019 at 7:06 am #24864Member
Xecure
::I was able to connect via the onboard USB 1.1 with the device, but it won’t communicate via the PCMCIA 2.0 adapter
Good news that the Wifi works (even if on USB 1.1).
I believe I read somewhere that rokytnji had used a PCMCIA USB hub before. He may be able to help with that. Maybe you need a special driver to take full advantage of it.For now, I would test connecting that PCI card and a USB pendrive (for storage), restarting the computer (leave everything connected), and see of you have read/write access to that USB pendrive.
Sometimes, devices are recognized, mounted and configured during boot, so having them connected before starting up the computer may help to get them working properly.
If after a while you can still read and write, connect the USB Wifi device to your PCMCIA USB adapter, restart the computer, and try to see if the device is recognized:
iwconfig
If you can see the device there (pay attention to its wlanX name), test to see if it can see any networks:
iwlist wlan0 scan
I am using wlan0 in this example. Use the correct wlanX device name.If your computer gets stuck again, I am sorry (you would have to unplug again 🙁 ). Maybe rokytnji could give us more info about how he configured his.
If it works, then maybe now you can use wicd or ceni to connect to your network.At least for now, you have the device working (even if only on USB 1.1). I think someone recommended a PCI Wifi card for laptop that works on antiX, in case you ever consider it in the future.
Found it: https://www.antixforum.com/forums/topic/old-pcmcia-card/#post-5777antiX Live system enthusiast.
General Live Boot Parameters for antiX.July 22, 2019 at 9:21 am #24875MemberGuruSR
::iwconfig does indeed list wlan0 on the PCMCIA USB 2.0 adapter, iwlist wlan0 scan however complains: “Interface doesn’t support scanning : Device or resource busy”.
The device is “ON” (it has multiple LEDs in it, one for power, one for activation, that second one doesn’t seem to work on Linux).
The biggest issue is, anything below N in this area is not supported, so going to a cafe, N or higher, they’re all wanting the new WPA2 security only, so for me, G isn’t useful at all. Wonder how to work with this PCMCIA adapter (ZUN2200 Zonet Cardbus 32-bit PCMCIA to USB2.0 Adapter).
I pulled the USB adapter out, then the PCMCIA adapter out, plugged the N USB adapter back into the USB1.1 and am typing this, it reconnected to the wireless here.
Oddly enough, all my network speeds are limited to 320KB, up/down, wired/wireless. Missing something?
GuruSR.
July 22, 2019 at 6:56 pm #24888Forum Admin
rokytnji
::Wireless N pcmcia adapter I used to use in the past was made by SMC in China.
I was using it in older antiX releases so kernel should support it out of the box.
- This reply was modified 3 years, 9 months ago by rokytnji.
- This reply was modified 3 years, 9 months ago by rokytnji.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsJuly 22, 2019 at 10:15 pm #24900MemberGuruSR
::It actually does work fine on the USB 1.1, but not through the PCMCIA (Zonet ZUN2200) USB 2.0 adapter, the system sees and loads the drivers for them alright, but after that, all communication says it is busy, that would be the issue with the driver for the ZUN2200, which I am trying to track the box down as there was a disc with it, believe hopefully they did add a Linux driver to it, but all I am seeing are Windows ones listed online.
GuruSR.
July 24, 2019 at 1:04 pm #24935Member
Xecure
::Does the PCMCIA adaptor work well with USB pendrives? If it does, then the drivers work, but the communication with Wifi type USB devices is problematic. Test to see if you can normally read/write on USB drives to make sure.
If this works, then try to force the Wifi device to turn off and on when connected to the PCMCIA hub.
ifconfig wlan0 down ifconfig wlan0 upAnd again try to scan for wifi networks.
iwlist wlan0 scanIf this still doesn’t work, I am afraid I don’t know how to help.
Oddly enough, all my network speeds are limited to 320KB, up/down, wired/wireless. Missing something?
No idea. Are these kilobytes or kilobits? It is strange. I have no idea or know how to help with this. Maybe you can find something searching on the net.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.July 24, 2019 at 7:23 pm #24943MemberGuruSR
::Actually, what is happening is, the PCMCIA USB 2.0 adapter is recognizing the hardware plugged into it, the above items I listed via lsusb were from the USB 2.0 PCMCIA adapter:
Bus 004 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBut, the same goes for any USB device, it sees it, AND loads the drivers for them (as apparent in the dmesg grep I also did), but there just simply is no communication through the PCMCIA adapter for USB data. I mean it gets the hardware information for the devices just fine, but it is almost like there is hardware flow control or software flow control on that shouldn’t be.
GuruSR.
July 25, 2019 at 8:25 am #24961Member
Xecure
::Your best bet is:
sudo lspci -k
This should give you info about how the PCMCIA device is recognized as, and the kernel modules/drivers used.
Check dmesg for error messages for the modules/drivers:
dmesg | grep "module_name"
where module_name is the name of module/driver for PCMCIA reported by lspci output.Try again the same command after connecting a USB device to your PCMCIA 2.0 USB port.
If no errors, then you can look up on the net for the information about your device and the specific module/driver it uses. Maybe you can get even more info with
sudo lspci -v
which should give even more clues, (if any).I really have no other idea of how to help.
Let us know how it goes.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.July 29, 2019 at 3:11 pm #25128MemberGuruSR
::The PCMCIA adapter is just showing up as:
01:00.2 USB controller: VIA Technologies, Inc. USB 2.0 (rev 63) Subsystem: VIA Technologies, Inc. USB 2.0 Controller Kernel driver in use: ehci-pciThe Cardbus is using:
00:04.0 CardBus bridge: Texas Instruments PCI1211 Subsystem: Compaq Computer Corporation PCI1211 Kernel driver in use: yenta_cardbus Kernel modules: yenta_socketdmesg | grep "yenta_socket" (doing this first to see if it has an issue beforehand, listed nothing anyways) dmesg | grep "yenta_cardbus" [ 44.600016] yenta_cardbus 0000:00:04.0: CardBus bridge found [0e11:b103] [ 44.600043] yenta_cardbus 0000:00:04.0: Enabling burst memory read transactions [ 44.600053] yenta_cardbus 0000:00:04.0: Using CSCINT to route CSC interrupts to PCI [ 44.600060] yenta_cardbus 0000:00:04.0: Routing CardBus interrupts to PCI [ 44.600071] yenta_cardbus 0000:00:04.0: TI: mfunc 0x01001002, devctl 0x64 [ 44.836978] yenta_cardbus 0000:00:04.0: ISA IRQ mask 0x0438, PCI irq 11 [ 44.836991] yenta_cardbus 0000:00:04.0: Socket status: 30000020dmesg | grep "ehci-pci" [ 3.917920] ehci-pci: EHCI PCI platform driver [ 45.743212] ehci-pci 0000:01:00.2: EHCI Host Controller [ 45.743248] ehci-pci 0000:01:00.2: new USB bus registered, assigned bus number 4 [ 45.744659] ehci-pci 0000:01:00.2: irq 11, io mem 0x18000200 [ 45.751467] ehci-pci 0000:01:00.2: USB 2.0 started, EHCI 1.00 [ 1228.038431] usb 4-1: new high-speed USB device number 2 using ehci-pci [ 1261.673551] usb 4-1: reset high-speed USB device number 2 using ehci-pci [ 1283.382429] usb 4-1: reset high-speed USB device number 2 using ehci-pci [ 1304.886456] usb 4-1: reset high-speed USB device number 2 using ehci-pci [ 1316.134434] usb 4-1: reset high-speed USB device number 2 using ehci-pci [ 1327.418976] usb 4-1: new high-speed USB device number 3 using ehci-pci [ 1348.918442] usb 4-1: new high-speed USB device number 4 using ehci-pci [ 1370.734456] usb 4-1: new high-speed USB device number 5 using ehci-pci [ 1382.182476] usb 4-1: new high-speed USB device number 6 using ehci-pcilspci -v 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) Subsystem: Compaq Computer Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) Flags: bus master, medium devsel, latency 64, NUMA node 0 Memory at 50000000 (32-bit, prefetchable) 00:04.0 CardBus bridge: Texas Instruments PCI1211 Subsystem: Compaq Computer Corporation PCI1211 Flags: bus master, medium devsel, latency 168, IRQ 11, NUMA node 0 Memory at 7fffe000 (32-bit, non-prefetchable) Bus: primary=00, secondary=01, subordinate=04, sec-latency=176 Memory window 0: 14000000-17ffffff (prefetchable) Memory window 1: 18000000-1bffffff I/O window 0: 00001000-000010ff I/O window 1: 00001400-000014ff 16-bit legacy interface ports at 0001 Capabilities: [a0] Power Management version 1 Kernel driver in use: yenta_cardbus Kernel modules: yenta_socket 00:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 3D Rage LT PRO PCI (rev dc) (prog-if 00 [VGA controller]) Subsystem: Compaq Computer Corporation 3D Rage LT PRO PCI Flags: bus master, stepping, medium devsel, latency 66, IRQ 11, NUMA node 0 Memory at 40000000 (32-bit, non-prefetchable) I/O ports at 3000 Memory at 41080000 (32-bit, non-prefetchable) [virtual] Expansion ROM at 000c0000 [disabled] Capabilities: [5c] Power Management version 1 00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) Flags: bus master, medium devsel, latency 0, NUMA node 0 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering]) Flags: bus master, medium devsel, latency 64, NUMA node 0 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [virtual] Memory at 000003f0 (type 3, non-prefetchable) [virtual] Memory at 00000170 (32-bit, non-prefetchable) [virtual] Memory at 00000370 (type 3, non-prefetchable) I/O ports at 3820 Kernel driver in use: ata_piix 00:07.2 USB controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) Flags: bus master, medium devsel, latency 64, IRQ 11, NUMA node 0 I/O ports at 3800 Kernel driver in use: uhci_hcd 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) Flags: medium devsel, IRQ 9, NUMA node 0 Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4 00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10) Subsystem: Compaq Computer Corporation Armada M700/E500 Flags: bus master, medium devsel, latency 64, IRQ 11, NUMA node 0 I/O ports at 3400 Capabilities: [c0] Power Management version 2 Kernel driver in use: snd_es1968 Kernel modules: snd_es1968 00:09.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 09) Subsystem: Intel Corporation EtherExpress PRO/100+ MiniPCI Flags: bus master, medium devsel, latency 66, IRQ 11, NUMA node 0 Memory at 41180000 (32-bit, non-prefetchable) I/O ports at 2000 Memory at 41100000 (32-bit, non-prefetchable) [virtual] Expansion ROM at 1c000000 [disabled] Capabilities: [dc] Power Management version 2 Kernel driver in use: e100 Kernel modules: e100 00:09.1 Serial controller: LSI Corporation LT WinModem (prog-if 00 [8250]) Subsystem: Intel Corporation PRO/100+ MiniPCI (probably an Ambit U98.003.C.00 combo card) Flags: medium devsel, IRQ 11, NUMA node 0 I/O ports at 2040 Memory at 41200000 (32-bit, non-prefetchable) Capabilities: [dc] Power Management version 2 Kernel driver in use: serial 01:00.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 61) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller Flags: bus master, medium devsel, latency 22, IRQ 11, NUMA node 0 Memory at 18000000 (32-bit, non-prefetchable) I/O ports at 1000 Capabilities: [80] Power Management version 2 Kernel driver in use: uhci_hcd 01:00.1 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 61) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller Flags: bus master, medium devsel, latency 22, IRQ 11, NUMA node 0 Memory at 18000100 (32-bit, non-prefetchable) I/O ports at 1020 Capabilities: [80] Power Management version 2 Kernel driver in use: uhci_hcd 01:00.2 USB controller: VIA Technologies, Inc. USB 2.0 (rev 63) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0 Controller Flags: bus master, medium devsel, latency 22, IRQ 11, NUMA node 0 Memory at 18000200 (32-bit, non-prefetchable) Memory at 18000300 (32-bit, non-prefetchable) Capabilities: [80] Power Management version 2 Kernel driver in use: ehci-pciI’m beginning to wonder if the cardbus driver isn’t 100%.
GuruSR.
- This reply was modified 3 years, 9 months ago by rokytnji.
-
AuthorPosts
- You must be logged in to reply to this topic.