Why is my WiFi card unclaimed by drivers in UbuntuMATE?












0















My Realtek 802.11n WiFi card isn't being claimed by the drivers from here. I installed led the drivers using the install.sh script given in the decompressed tar.gz. UbuntuMATE is running on a Raspberry Pi 2.



*-usb:4 UNCLAIMED
description: Generic USB device
product: 802.11n NIC
vendor: Realtek
physical id: 5
bus info: usb@1:1.5
version: 2.00
serial: 00e04c000001
capabilities: usb-2.10
configuration: maxpower=500mA speed=480Mbit/s


Above is the result of sudo lshw in terminal, which shows the unclaimed USB device, the WiFi card.



harrycburn@RPi:~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

harrycburn@RPi:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:3a:b4:5a
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:542 errors:0 dropped:0 overruns:0 frame:0
TX packets:542 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:45957 (45.9 KB) TX bytes:45957 (45.9 KB)


Running lsusb:



harrycburn@RPi:~$ lsusb
Bus 001 Device 012: ID 0bda:818b Realtek Semiconductor Corp.
Bus 001 Device 013: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 007: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 004: ID 1bcf:0005 Sunplus Innovation Technology Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Running lspci (I'm not even sure if this is relevant) gives:



pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method


Running install.sh gives the error:



tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/wpa1.conf: time stamp 2012-04-05 03:42:09 is 1333588869.902553677 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/wpa1.conf: Cannot change ownership to uid 400, gid 401: Operation not permitted
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c: time stamp 2012-04-05 03:42:13 is 1333588873.89712326 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c: Cannot change ownership to uid 400, gid 401: Operation not permitted
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c: time stamp 2012-04-05 03:42:13 is 1333588873.891775552 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit: time stamp 2012-04-05 03:42:13 is 1333588873.890704718 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405: time stamp 2012-04-05 03:42:18 is 1333588878.889988364 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: Exiting with failure status due to previous errors
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405
Authentication requested [root] for make clean:
bash: make: command not found
Authentication requested [root] for make driver:
bash: make: command not found
##################################################
Compile make driver error: 127
Please check error Mesg
##################################################


As I'm new to Linux in general, I have no idea as to where to go from here, so I'd appreciate any help. If you need any more information, just ask and I'll post it.










share|improve this question

























  • Yea I know this is kinda ironic, but using drivers from hardware manufacture's site is rarely to be a good idea, as the they're usually out-dated like in your case: the latest kernel they support is 3.9, and you're using 3.19 (I guess, pls provide this info). And we also need your card serie (is that rtl8712?) And where did you get your driver installation script? Try reinstall make, install build-essential, checkinstall and try again.

    – McSinyx
    Jul 31 '15 at 2:49











  • The install script is the one provided in the driver download. Not sure what series, the packaging was really minimalist and of low quality (guess that shoulda' been a warning to me!) It may be rtl8721. Running uname -r gives 3.18.0-20-rpi2. The issue with installing from apt-get is that requires internet connection, something I'm trying to get to work.

    – HarryCBurn
    Jul 31 '15 at 13:26
















0















My Realtek 802.11n WiFi card isn't being claimed by the drivers from here. I installed led the drivers using the install.sh script given in the decompressed tar.gz. UbuntuMATE is running on a Raspberry Pi 2.



*-usb:4 UNCLAIMED
description: Generic USB device
product: 802.11n NIC
vendor: Realtek
physical id: 5
bus info: usb@1:1.5
version: 2.00
serial: 00e04c000001
capabilities: usb-2.10
configuration: maxpower=500mA speed=480Mbit/s


Above is the result of sudo lshw in terminal, which shows the unclaimed USB device, the WiFi card.



harrycburn@RPi:~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

harrycburn@RPi:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:3a:b4:5a
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:542 errors:0 dropped:0 overruns:0 frame:0
TX packets:542 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:45957 (45.9 KB) TX bytes:45957 (45.9 KB)


Running lsusb:



harrycburn@RPi:~$ lsusb
Bus 001 Device 012: ID 0bda:818b Realtek Semiconductor Corp.
Bus 001 Device 013: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 007: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 004: ID 1bcf:0005 Sunplus Innovation Technology Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Running lspci (I'm not even sure if this is relevant) gives:



pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method


Running install.sh gives the error:



tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/wpa1.conf: time stamp 2012-04-05 03:42:09 is 1333588869.902553677 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/wpa1.conf: Cannot change ownership to uid 400, gid 401: Operation not permitted
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c: time stamp 2012-04-05 03:42:13 is 1333588873.89712326 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c: Cannot change ownership to uid 400, gid 401: Operation not permitted
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c: time stamp 2012-04-05 03:42:13 is 1333588873.891775552 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit: time stamp 2012-04-05 03:42:13 is 1333588873.890704718 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405: time stamp 2012-04-05 03:42:18 is 1333588878.889988364 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: Exiting with failure status due to previous errors
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405
Authentication requested [root] for make clean:
bash: make: command not found
Authentication requested [root] for make driver:
bash: make: command not found
##################################################
Compile make driver error: 127
Please check error Mesg
##################################################


As I'm new to Linux in general, I have no idea as to where to go from here, so I'd appreciate any help. If you need any more information, just ask and I'll post it.










share|improve this question

























  • Yea I know this is kinda ironic, but using drivers from hardware manufacture's site is rarely to be a good idea, as the they're usually out-dated like in your case: the latest kernel they support is 3.9, and you're using 3.19 (I guess, pls provide this info). And we also need your card serie (is that rtl8712?) And where did you get your driver installation script? Try reinstall make, install build-essential, checkinstall and try again.

    – McSinyx
    Jul 31 '15 at 2:49











  • The install script is the one provided in the driver download. Not sure what series, the packaging was really minimalist and of low quality (guess that shoulda' been a warning to me!) It may be rtl8721. Running uname -r gives 3.18.0-20-rpi2. The issue with installing from apt-get is that requires internet connection, something I'm trying to get to work.

    – HarryCBurn
    Jul 31 '15 at 13:26














0












0








0








My Realtek 802.11n WiFi card isn't being claimed by the drivers from here. I installed led the drivers using the install.sh script given in the decompressed tar.gz. UbuntuMATE is running on a Raspberry Pi 2.



*-usb:4 UNCLAIMED
description: Generic USB device
product: 802.11n NIC
vendor: Realtek
physical id: 5
bus info: usb@1:1.5
version: 2.00
serial: 00e04c000001
capabilities: usb-2.10
configuration: maxpower=500mA speed=480Mbit/s


Above is the result of sudo lshw in terminal, which shows the unclaimed USB device, the WiFi card.



harrycburn@RPi:~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

harrycburn@RPi:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:3a:b4:5a
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:542 errors:0 dropped:0 overruns:0 frame:0
TX packets:542 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:45957 (45.9 KB) TX bytes:45957 (45.9 KB)


Running lsusb:



harrycburn@RPi:~$ lsusb
Bus 001 Device 012: ID 0bda:818b Realtek Semiconductor Corp.
Bus 001 Device 013: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 007: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 004: ID 1bcf:0005 Sunplus Innovation Technology Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Running lspci (I'm not even sure if this is relevant) gives:



pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method


Running install.sh gives the error:



tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/wpa1.conf: time stamp 2012-04-05 03:42:09 is 1333588869.902553677 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/wpa1.conf: Cannot change ownership to uid 400, gid 401: Operation not permitted
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c: time stamp 2012-04-05 03:42:13 is 1333588873.89712326 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c: Cannot change ownership to uid 400, gid 401: Operation not permitted
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c: time stamp 2012-04-05 03:42:13 is 1333588873.891775552 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit: time stamp 2012-04-05 03:42:13 is 1333588873.890704718 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405: time stamp 2012-04-05 03:42:18 is 1333588878.889988364 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: Exiting with failure status due to previous errors
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405
Authentication requested [root] for make clean:
bash: make: command not found
Authentication requested [root] for make driver:
bash: make: command not found
##################################################
Compile make driver error: 127
Please check error Mesg
##################################################


As I'm new to Linux in general, I have no idea as to where to go from here, so I'd appreciate any help. If you need any more information, just ask and I'll post it.










share|improve this question
















My Realtek 802.11n WiFi card isn't being claimed by the drivers from here. I installed led the drivers using the install.sh script given in the decompressed tar.gz. UbuntuMATE is running on a Raspberry Pi 2.



*-usb:4 UNCLAIMED
description: Generic USB device
product: 802.11n NIC
vendor: Realtek
physical id: 5
bus info: usb@1:1.5
version: 2.00
serial: 00e04c000001
capabilities: usb-2.10
configuration: maxpower=500mA speed=480Mbit/s


Above is the result of sudo lshw in terminal, which shows the unclaimed USB device, the WiFi card.



harrycburn@RPi:~$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

harrycburn@RPi:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:3a:b4:5a
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:542 errors:0 dropped:0 overruns:0 frame:0
TX packets:542 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:45957 (45.9 KB) TX bytes:45957 (45.9 KB)


Running lsusb:



harrycburn@RPi:~$ lsusb
Bus 001 Device 012: ID 0bda:818b Realtek Semiconductor Corp.
Bus 001 Device 013: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 007: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 004: ID 1bcf:0005 Sunplus Innovation Technology Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Running lspci (I'm not even sure if this is relevant) gives:



pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method


Running install.sh gives the error:



tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/wpa1.conf: time stamp 2012-04-05 03:42:09 is 1333588869.902553677 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/wpa1.conf: Cannot change ownership to uid 400, gid 401: Operation not permitted
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c: time stamp 2012-04-05 03:42:13 is 1333588873.89712326 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl8712_xmit.c: Cannot change ownership to uid 400, gid 401: Operation not permitted
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c: time stamp 2012-04-05 03:42:13 is 1333588873.891775552 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit/rtl871x_xmit.c: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit: time stamp 2012-04-05 03:42:13 is 1333588873.890704718 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/xmit: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405: time stamp 2012-04-05 03:42:18 is 1333588878.889988364 s in the future
tar: rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405: Cannot change ownership to uid 400, gid 401: Operation not permitted
tar: Exiting with failure status due to previous errors
rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405
Authentication requested [root] for make clean:
bash: make: command not found
Authentication requested [root] for make driver:
bash: make: command not found
##################################################
Compile make driver error: 127
Please check error Mesg
##################################################


As I'm new to Linux in general, I have no idea as to where to go from here, so I'd appreciate any help. If you need any more information, just ask and I'll post it.







ubuntu wifi drivers






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 15 at 5:19









Rui F Ribeiro

40.7k1479137




40.7k1479137










asked Jul 30 '15 at 21:33









HarryCBurnHarryCBurn

1035




1035













  • Yea I know this is kinda ironic, but using drivers from hardware manufacture's site is rarely to be a good idea, as the they're usually out-dated like in your case: the latest kernel they support is 3.9, and you're using 3.19 (I guess, pls provide this info). And we also need your card serie (is that rtl8712?) And where did you get your driver installation script? Try reinstall make, install build-essential, checkinstall and try again.

    – McSinyx
    Jul 31 '15 at 2:49











  • The install script is the one provided in the driver download. Not sure what series, the packaging was really minimalist and of low quality (guess that shoulda' been a warning to me!) It may be rtl8721. Running uname -r gives 3.18.0-20-rpi2. The issue with installing from apt-get is that requires internet connection, something I'm trying to get to work.

    – HarryCBurn
    Jul 31 '15 at 13:26



















  • Yea I know this is kinda ironic, but using drivers from hardware manufacture's site is rarely to be a good idea, as the they're usually out-dated like in your case: the latest kernel they support is 3.9, and you're using 3.19 (I guess, pls provide this info). And we also need your card serie (is that rtl8712?) And where did you get your driver installation script? Try reinstall make, install build-essential, checkinstall and try again.

    – McSinyx
    Jul 31 '15 at 2:49











  • The install script is the one provided in the driver download. Not sure what series, the packaging was really minimalist and of low quality (guess that shoulda' been a warning to me!) It may be rtl8721. Running uname -r gives 3.18.0-20-rpi2. The issue with installing from apt-get is that requires internet connection, something I'm trying to get to work.

    – HarryCBurn
    Jul 31 '15 at 13:26

















Yea I know this is kinda ironic, but using drivers from hardware manufacture's site is rarely to be a good idea, as the they're usually out-dated like in your case: the latest kernel they support is 3.9, and you're using 3.19 (I guess, pls provide this info). And we also need your card serie (is that rtl8712?) And where did you get your driver installation script? Try reinstall make, install build-essential, checkinstall and try again.

– McSinyx
Jul 31 '15 at 2:49





Yea I know this is kinda ironic, but using drivers from hardware manufacture's site is rarely to be a good idea, as the they're usually out-dated like in your case: the latest kernel they support is 3.9, and you're using 3.19 (I guess, pls provide this info). And we also need your card serie (is that rtl8712?) And where did you get your driver installation script? Try reinstall make, install build-essential, checkinstall and try again.

– McSinyx
Jul 31 '15 at 2:49













The install script is the one provided in the driver download. Not sure what series, the packaging was really minimalist and of low quality (guess that shoulda' been a warning to me!) It may be rtl8721. Running uname -r gives 3.18.0-20-rpi2. The issue with installing from apt-get is that requires internet connection, something I'm trying to get to work.

– HarryCBurn
Jul 31 '15 at 13:26





The install script is the one provided in the driver download. Not sure what series, the packaging was really minimalist and of low quality (guess that shoulda' been a warning to me!) It may be rtl8721. Running uname -r gives 3.18.0-20-rpi2. The issue with installing from apt-get is that requires internet connection, something I'm trying to get to work.

– HarryCBurn
Jul 31 '15 at 13:26










1 Answer
1






active

oldest

votes


















2














I've just found out that your chip is actually rtl8192eu. As far as I know, there is no driver for it in Ubuntu's repo. However, as v0yAgEr mentioned on OSMC forums, there is driver for that chip works for kernel version 3.18 on GitHub. I modified v0yAgEr's tutorial to a way hopefully would work for you:





  1. Install build-essential:




    • From the computer have Internet access, go to Ubuntu Packages, download build-essential, its dependencies and its dependencies' dependencies to a folder called bldessen

    • Copy that folder to your Pi, then install all the debs by sudo cd bldessen && dkpg --install *.deb



  2. Download the driver from GitHub (click the Download Zip button), copy to your Pi, then extract it: unzip rtl8192eu-master.zip



  3. Compile your driver:



    cd rtl8192eu-master
    make ARCH=arm
    sudo make ARCH=arm install
    sudo bash -c 'echo "options 8192eu rtw_power_mgnt=0 rtw_enusbss=0">/etc/modprobe.d/8192eu.conf'



  4. Test if the driver loaded:



    modprobe 8192eu
    modinfo 8192eu







share|improve this answer


























  • Spent a few (3-4) hours installing dependencies. Finally got make to work, and got an error when trying to build. I've pasted it here. Any ideas?

    – HarryCBurn
    Aug 1 '15 at 23:54











  • I've no idea why it failed. But make install need to be ran with root permission, i.e. via sudo or su -c.

    – McSinyx
    Aug 2 '15 at 13:57











  • Installed linux-headers, compiled fully.

    – HarryCBurn
    Aug 3 '15 at 19:00











  • So @HarryCBurn is your problem solved now? If my answer helpful then I'd be really grateful to see it got accepted.

    – McSinyx
    Aug 5 '15 at 13:25











  • Still having , but they're on my end, so I've accepted. Thanks!

    – HarryCBurn
    Aug 5 '15 at 13:32











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f219362%2fwhy-is-my-wifi-card-unclaimed-by-drivers-in-ubuntumate%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














I've just found out that your chip is actually rtl8192eu. As far as I know, there is no driver for it in Ubuntu's repo. However, as v0yAgEr mentioned on OSMC forums, there is driver for that chip works for kernel version 3.18 on GitHub. I modified v0yAgEr's tutorial to a way hopefully would work for you:





  1. Install build-essential:




    • From the computer have Internet access, go to Ubuntu Packages, download build-essential, its dependencies and its dependencies' dependencies to a folder called bldessen

    • Copy that folder to your Pi, then install all the debs by sudo cd bldessen && dkpg --install *.deb



  2. Download the driver from GitHub (click the Download Zip button), copy to your Pi, then extract it: unzip rtl8192eu-master.zip



  3. Compile your driver:



    cd rtl8192eu-master
    make ARCH=arm
    sudo make ARCH=arm install
    sudo bash -c 'echo "options 8192eu rtw_power_mgnt=0 rtw_enusbss=0">/etc/modprobe.d/8192eu.conf'



  4. Test if the driver loaded:



    modprobe 8192eu
    modinfo 8192eu







share|improve this answer


























  • Spent a few (3-4) hours installing dependencies. Finally got make to work, and got an error when trying to build. I've pasted it here. Any ideas?

    – HarryCBurn
    Aug 1 '15 at 23:54











  • I've no idea why it failed. But make install need to be ran with root permission, i.e. via sudo or su -c.

    – McSinyx
    Aug 2 '15 at 13:57











  • Installed linux-headers, compiled fully.

    – HarryCBurn
    Aug 3 '15 at 19:00











  • So @HarryCBurn is your problem solved now? If my answer helpful then I'd be really grateful to see it got accepted.

    – McSinyx
    Aug 5 '15 at 13:25











  • Still having , but they're on my end, so I've accepted. Thanks!

    – HarryCBurn
    Aug 5 '15 at 13:32
















2














I've just found out that your chip is actually rtl8192eu. As far as I know, there is no driver for it in Ubuntu's repo. However, as v0yAgEr mentioned on OSMC forums, there is driver for that chip works for kernel version 3.18 on GitHub. I modified v0yAgEr's tutorial to a way hopefully would work for you:





  1. Install build-essential:




    • From the computer have Internet access, go to Ubuntu Packages, download build-essential, its dependencies and its dependencies' dependencies to a folder called bldessen

    • Copy that folder to your Pi, then install all the debs by sudo cd bldessen && dkpg --install *.deb



  2. Download the driver from GitHub (click the Download Zip button), copy to your Pi, then extract it: unzip rtl8192eu-master.zip



  3. Compile your driver:



    cd rtl8192eu-master
    make ARCH=arm
    sudo make ARCH=arm install
    sudo bash -c 'echo "options 8192eu rtw_power_mgnt=0 rtw_enusbss=0">/etc/modprobe.d/8192eu.conf'



  4. Test if the driver loaded:



    modprobe 8192eu
    modinfo 8192eu







share|improve this answer


























  • Spent a few (3-4) hours installing dependencies. Finally got make to work, and got an error when trying to build. I've pasted it here. Any ideas?

    – HarryCBurn
    Aug 1 '15 at 23:54











  • I've no idea why it failed. But make install need to be ran with root permission, i.e. via sudo or su -c.

    – McSinyx
    Aug 2 '15 at 13:57











  • Installed linux-headers, compiled fully.

    – HarryCBurn
    Aug 3 '15 at 19:00











  • So @HarryCBurn is your problem solved now? If my answer helpful then I'd be really grateful to see it got accepted.

    – McSinyx
    Aug 5 '15 at 13:25











  • Still having , but they're on my end, so I've accepted. Thanks!

    – HarryCBurn
    Aug 5 '15 at 13:32














2












2








2







I've just found out that your chip is actually rtl8192eu. As far as I know, there is no driver for it in Ubuntu's repo. However, as v0yAgEr mentioned on OSMC forums, there is driver for that chip works for kernel version 3.18 on GitHub. I modified v0yAgEr's tutorial to a way hopefully would work for you:





  1. Install build-essential:




    • From the computer have Internet access, go to Ubuntu Packages, download build-essential, its dependencies and its dependencies' dependencies to a folder called bldessen

    • Copy that folder to your Pi, then install all the debs by sudo cd bldessen && dkpg --install *.deb



  2. Download the driver from GitHub (click the Download Zip button), copy to your Pi, then extract it: unzip rtl8192eu-master.zip



  3. Compile your driver:



    cd rtl8192eu-master
    make ARCH=arm
    sudo make ARCH=arm install
    sudo bash -c 'echo "options 8192eu rtw_power_mgnt=0 rtw_enusbss=0">/etc/modprobe.d/8192eu.conf'



  4. Test if the driver loaded:



    modprobe 8192eu
    modinfo 8192eu







share|improve this answer















I've just found out that your chip is actually rtl8192eu. As far as I know, there is no driver for it in Ubuntu's repo. However, as v0yAgEr mentioned on OSMC forums, there is driver for that chip works for kernel version 3.18 on GitHub. I modified v0yAgEr's tutorial to a way hopefully would work for you:





  1. Install build-essential:




    • From the computer have Internet access, go to Ubuntu Packages, download build-essential, its dependencies and its dependencies' dependencies to a folder called bldessen

    • Copy that folder to your Pi, then install all the debs by sudo cd bldessen && dkpg --install *.deb



  2. Download the driver from GitHub (click the Download Zip button), copy to your Pi, then extract it: unzip rtl8192eu-master.zip



  3. Compile your driver:



    cd rtl8192eu-master
    make ARCH=arm
    sudo make ARCH=arm install
    sudo bash -c 'echo "options 8192eu rtw_power_mgnt=0 rtw_enusbss=0">/etc/modprobe.d/8192eu.conf'



  4. Test if the driver loaded:



    modprobe 8192eu
    modinfo 8192eu








share|improve this answer














share|improve this answer



share|improve this answer








edited Jul 23 '17 at 16:43









George Udosen

1,248320




1,248320










answered Aug 1 '15 at 10:26









McSinyxMcSinyx

556313




556313













  • Spent a few (3-4) hours installing dependencies. Finally got make to work, and got an error when trying to build. I've pasted it here. Any ideas?

    – HarryCBurn
    Aug 1 '15 at 23:54











  • I've no idea why it failed. But make install need to be ran with root permission, i.e. via sudo or su -c.

    – McSinyx
    Aug 2 '15 at 13:57











  • Installed linux-headers, compiled fully.

    – HarryCBurn
    Aug 3 '15 at 19:00











  • So @HarryCBurn is your problem solved now? If my answer helpful then I'd be really grateful to see it got accepted.

    – McSinyx
    Aug 5 '15 at 13:25











  • Still having , but they're on my end, so I've accepted. Thanks!

    – HarryCBurn
    Aug 5 '15 at 13:32



















  • Spent a few (3-4) hours installing dependencies. Finally got make to work, and got an error when trying to build. I've pasted it here. Any ideas?

    – HarryCBurn
    Aug 1 '15 at 23:54











  • I've no idea why it failed. But make install need to be ran with root permission, i.e. via sudo or su -c.

    – McSinyx
    Aug 2 '15 at 13:57











  • Installed linux-headers, compiled fully.

    – HarryCBurn
    Aug 3 '15 at 19:00











  • So @HarryCBurn is your problem solved now? If my answer helpful then I'd be really grateful to see it got accepted.

    – McSinyx
    Aug 5 '15 at 13:25











  • Still having , but they're on my end, so I've accepted. Thanks!

    – HarryCBurn
    Aug 5 '15 at 13:32

















Spent a few (3-4) hours installing dependencies. Finally got make to work, and got an error when trying to build. I've pasted it here. Any ideas?

– HarryCBurn
Aug 1 '15 at 23:54





Spent a few (3-4) hours installing dependencies. Finally got make to work, and got an error when trying to build. I've pasted it here. Any ideas?

– HarryCBurn
Aug 1 '15 at 23:54













I've no idea why it failed. But make install need to be ran with root permission, i.e. via sudo or su -c.

– McSinyx
Aug 2 '15 at 13:57





I've no idea why it failed. But make install need to be ran with root permission, i.e. via sudo or su -c.

– McSinyx
Aug 2 '15 at 13:57













Installed linux-headers, compiled fully.

– HarryCBurn
Aug 3 '15 at 19:00





Installed linux-headers, compiled fully.

– HarryCBurn
Aug 3 '15 at 19:00













So @HarryCBurn is your problem solved now? If my answer helpful then I'd be really grateful to see it got accepted.

– McSinyx
Aug 5 '15 at 13:25





So @HarryCBurn is your problem solved now? If my answer helpful then I'd be really grateful to see it got accepted.

– McSinyx
Aug 5 '15 at 13:25













Still having , but they're on my end, so I've accepted. Thanks!

– HarryCBurn
Aug 5 '15 at 13:32





Still having , but they're on my end, so I've accepted. Thanks!

– HarryCBurn
Aug 5 '15 at 13:32


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f219362%2fwhy-is-my-wifi-card-unclaimed-by-drivers-in-ubuntumate%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to make a Squid Proxy server?

Is this a new Fibonacci Identity?

19世紀