Engenius EUB9603H driver - need help

[eskull]

Running Centos 6.2.

Trying to get the driver for the EUB9603.

Have spent better part of two days trying to figure this out (I'm slow).

Some sort of driver that has to be compiled was included on the install CD.

My attempts at building have failed.

I will try to upload the makefile. The following events are closely tied to that file.

When I first ran make in the Engenius folder where i extracted the driver rar, got

sudo make
[sudo] password for brick1:
makefile:8: /config: No such file or directory
make: *** No rule to make target `/config'. Stop.

which I believe corresponded to the following makefile line:
include $(TOPDIR) config

I commented that out since there wasn't a /config folder. There is a config file however.

Re-ran make, got :

sudo make
cp: cannot stat `/autoconf_rtl8712_usb_linux.h': No such file or directory
make: Nothing to be done for `all'.

Don't know how to get past this.


Meanwhile, rummaging thru forums, tried various things to figure out what I have:

Compared dmesg output with and without usb wireless plugged in:
$ diff dmesg.txt dmesg_plugged.txt
610a611,617
> usb 1-2: new full speed USB device using ohci_hcd and address 3
> usb 1-2: New USB device found, idVendor=1740, idProduct=9603
> usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-2: Product: RTL8188S WLAN Adapter
> usb 1-2: Manufacturer: Manufacturer Realtek
> usb 1-2: SerialNumber: 00e04c000001
> usb 1-2: configuration #1 chosen from 1 choice


Further queries:

$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.


$ sudo modprobe 8188s
FATAL: Module 8188s not found.


$ uname -r
2.6.32-220.el6.i686


NOTE: I see rtl818x in /lib/modules/2.6.32-220.el6.i686/kernel/drivers/net/wireless
where x = 0 and 7


From:
http://elrepo.org/tiki/FAQ

/sbin/lspci -nn | grep -i net
00:0a.0 Ethernet controller [0200]: 3Com Corporation 3c905 100BaseTX [Boomerang] [10b7:9050]

did not show the EUB. Also tried,

$ for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1 }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done
00:0a.0 "Ethernet controller" "3Com Corporation" "3c905 100BaseTX [Boomerang]" "" ""
00:0a.0 0200: 10b7:9050

Still didn't show the EUB.

Also, from Elpro:

By using the Vendor & Device numbers from an ID pairing, you can check to see if your system contains an appropriate driver module for that particular device:

$ grep -i VendorID /lib/modules/*/modules.alias | grep -i DeviceID,
with VendorID and DeviceID replaced w/1740, 9603

returned nothing.

I'm not well experienced with Linux so would appreciate any detailed guidance.

Thank you.

[TrevorH]

Your first step is to upgrade from 6.2 to 6.6 as 6.2 is ancient, unsupported, contains many high severity security vulnerabilties and also, has less hardware support than 6.6.

You attempted to find your device's vendor id and device id but you used lspci and this is a usb device so you would really need to list it using lsusb.

I did look through a number of the kmod-rt* packages that ELRepo provide but I did not find your 1740:9603 vendor:device id pair in any of the ones I tried. It might be worth asking on their bug tracker if a suitable package could be created though.

[eskull]

Hi TrevorH,

Thank you for the quick response.

Re. the lspci; well duh. I should have realized that was not applicable. I did run lsusb; IIRC, it reported the device chip set for the wlan. I'm not home so can't look at my notes.

Re. upgrade to 6.6, can you point me in the right direction on the best way to do this upgrade?

Re. ElRepo, I posted there, but the pessimist in me is not too hopeful.

I saw a couple of Ubuntu forums that showed how to get this device working. I may switch to that OS if I can't get a Centos driver running (I would prefer to stay with Centos tho).


Thank you again for taking the time to respond, and your help.

ES.

[AlanBartlett]

Re. ElRepo, I posted there, but the pessimist in me is not too hopeful.

Where exactly did you post? I have looked in the bug tracker to see if you had opened an RFE and also checked the mailing list archive. In both locations nothing was found.

[eskull]

Well dang, appears my post was removed, or I did something wrong, but it isn't there, as you noted.
Also, the login account I created is no longer active. Jeezzz.
I had received a registration activation email, followed the link, entered PW. Then logged in and posted my case.
Guess someone there didn't like me?

Will try again, maybe it will work this time.

Sorry for causing any wasted time here.

Can anyone tell me the most straight fwd path to follow do upgrade Centos 6.2 to the current version - just need to be pointed in the right direction.


Thank you all for the replies.

ES.

[AlanBartlett]

Can anyone tell me the most straight fwd path to follow do upgrade Centos 6.2 to the current version - just need to be pointed in the right direction.

With a working connection to the Internet, issuing a simple yum update, as root, would do the deed. Could you set-up a temporary wired Ethernet connection while you could perform the upgrade?

Checking against the kernel-lt package available from the ELRepo Project, I see that your USB based wireless device should be supported by that kernel. The relevant module is r8712u.

Code: Select all

[Duo2 ~]$ grep 1740 /lib/modules/*/modules.alias | grep 9603
/lib/modules/3.10.79-1.el6.elrepo.x86_64/modules.alias:alias usb:v1740p9603d*dc*dsc*dp*ic*isc*ip*in* r8712u
[Duo2 ~]$

[eskull]

HI AlanBartlett,

Thank you so much for the detailed reply.

I will try the update tonight if I get home early enough.

And I will check out the r8712u module at ElRepo.com.


Will post outcome when I get there.

Thank you again.

ES.

[eskull]

I updated to Centos 6.6 as directed.

Then did the following:
(sorry if this is too verbose; it is the entire sequence of steps I have followed. Also, http://scientificlinuxforum.org/index.p ... topic=2661 was very helpful)

From Centos forum support, was directed to install the ElRepo kernel-lt package from,

http://elrepo.org/tiki/tiki-index.php


Installed ElRepo for RHEL6, and then installed the kernel-lt.

Running,

sudo rpm -qa kernel\* | grep -vE 'fir|hea' | sort

outputs,

kernel-2.6.32-220.el6.i686
kernel-2.6.32-504.16.2.el6.i686
kernel-devel-2.6.32-504.16.2.el6.i686
kernel-lt-3.10.79-1.el6.elrepo.i686

Running,

sudo grep -i 0bda /lib/modules/*/modules.alias | grep -iE '8171|8172' | sort

produces:

/lib/modules/3.10.79-1.el6.elrepo.i686/modules.alias:alias usb:v0BDAp8171d*dc*dsc*dp*ic*isc*ip*in* r8712u
/lib/modules/3.10.79-1.el6.elrepo.i686/modules.alias:alias usb:v0BDAp8172d*dc*dsc*dp*ic*isc*ip*in* r8712u


Was told in this forum, for my vendor_id:device_id, the r8712u driver should work.

After reboot, ran dmseg

Reported for the EUB: (filtered down for usb/wifi related)
--------------------------------------------------------------------------------------------------------------------------
Jun 3 11:38:32 localhost kernel: usb 1-2: new full speed USB device number 2 using ohci_hcd
Jun 3 11:38:32 localhost kernel: udev: starting version 147
Jun 3 11:38:32 localhost kernel: usb 1-2: New USB device found, idVendor=1740, idProduct=9603
Jun 3 11:38:32 localhost kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 3 11:38:32 localhost kernel: usb 1-2: Product: RTL8188S WLAN Adapter
Jun 3 11:38:32 localhost kernel: usb 1-2: Manufacturer: Manufacturer Realtek
Jun 3 11:38:32 localhost kernel: usb 1-2: SerialNumber: 00e04c000001
Jun 3 11:38:32 localhost kernel: usb 1-2: configuration #1 chosen from 1 choice
Jun 3 11:38:32 localhost kernel: [drm] Initialized drm 1.1.0 20060810

Jun 3 11:38:38 localhost NetworkManager[1273]: <info> WiFi enabled by radio killswitch; enabled by state file
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> WWAN enabled by radio killswitch; enabled by state file
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> WiMAX enabled by radio killswitch; enabled by state file
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> Networking is enabled by state file
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): carrier is OFF
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): new Ethernet device (driver: '3c59x' ifindex: 2)
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): now managed
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [1 2 2]
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): bringing up device.
Jun 3 11:38:38 localhost kernel: eth0: setting full-duplex.
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): carrier now ON (device state 2)
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): preparing device.
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): deactivating device (reason 'managed') [2]
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> Added default wired connection 'Auto eth0' for /sys/devices/pci0000:00/0000:00:0a.0/net/eth0
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): carrier now OFF (device state 2)
Jun 3 11:38:38 localhost NetworkManager[1273]: <info> (eth0): carrier now ON (device state 2)
--------------------------------------------------------------------------------------------------------------------------

$ cd /lib/modules/3.10.79-1.el6.elrepo.i686/kernel/drivers/staging/rtl8712
$ ls -al
total 208
drwxr-xr-x. 2 root root 4096 Jun 3 14:58 .
drwxr-xr-x. 9 root root 4096 Jun 3 14:58 ..
-rwxr--r--. 1 root root 201960 May 18 11:58 r8712u.ko


$ sudo modinfo -F firmware /lib/modules/3.10.79-1.el6.elrepo.i686/kernel/drivers/staging/rtl8712/r8712u.ko
rtlwifi/rtl8712u.bin

----- This file must be in location /lib/firmware/rtlwifi/


Downloaded rtl8712u.bin from,

http://git.kernel.org/cgit/linux/kernel ... ee/rtlwifi

Then put the file into the following new folder,
sudo mkdir -p /lib/firmware/rtlwifi/
cd /lib/firmware/rtlwifi/
sudo cp ~/Downloads/Software/Engenius/rtl8712u.bin .

Then run,

modprobe r8712u

returned something like not found (didnt' capture msg).


Edit the system's /etc/sysconfig/kernel file and change the very last line to be --

DEFAULTKERNEL=kernel-lt

Reboot.

During boot, blu LED began blinking on the EUB.

Disconnect wired cable, ran Firefox. No connection.

Switched back to wired.

Run,


modprobe r8712u

returned nothing. Nothing was reported at the tail end of /var/log/messages

Ran,

cat /var/log/messages > msg_cap

and gedit, search of 8712:
--------------------------------------------------------------------------------------------------------------------------
Jun 3 18:52:06 localhost kernel: r8712u: module is from the staging directory, the quality is unknown, you have been warned.
Jun 3 18:52:06 localhost kernel: r8712u: Staging version
Jun 3 18:52:06 localhost kernel: r8712u: register rtl8712_netdev_ops to netdev_ops
Jun 3 18:52:06 localhost kernel: usb 1-2: r8712u: USB_SPEED_LOW with 4 endpoints
Jun 3 18:52:06 localhost kernel: usb 1-2: r8712u: Boot from EFUSE: Autoload OK
Jun 3 18:52:06 localhost kernel: usb 1-2: r8712u: CustomerID = 0x0000
Jun 3 18:52:06 localhost kernel: usb 1-2: r8712u: MAC Address from efuse = 88:dc:96:23:57:b8
Jun 3 18:52:06 localhost kernel: usb 1-2: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
Jun 3 18:52:06 localhost kernel: usbcore: registered new interface driver r8712u


Jun 3 18:52:11 localhost NetworkManager[1310]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...
Jun 3 18:52:11 localhost NetworkManager[1310]: <info> WiFi enabled by radio killswitch; enabled by state file
Jun 3 18:52:11 localhost NetworkManager[1310]: <info> WWAN enabled by radio killswitch; enabled by state file
Jun 3 18:52:11 localhost NetworkManager[1310]: <info> WiMAX enabled by radio killswitch; enabled by state file
Jun 3 18:52:11 localhost NetworkManager[1310]: <info> Networking is enabled by state file
Jun 3 18:52:11 localhost NetworkManager[1310]: <info> (wlan0): driver does not support SSID scans (scan_capa 0x00).
Jun 3 18:52:11 localhost NetworkManager[1310]: <info> (wlan0): new 802.11 WiFi device (driver: 'r8712u' ifindex: 2)
Jun 3 18:52:11 localhost NetworkManager[1310]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0
Jun 3 18:52:11 localhost NetworkManager[1310]: <info> (wlan0): now managed
Jun 3 18:52:11 localhost NetworkManager[1310]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [1 2 2]
Jun 3 18:52:11 localhost NetworkManager[1310]: <info> (wlan0): bringing up device.
Jun 3 18:52:11 localhost rpc.statd[1343]: Version 1.2.3 starting
Jun 3 18:52:11 localhost sm-notify[1344]: Version 1.2.3 starting
Jun 3 18:52:12 localhost kernel: r8712u 1-2:1.0 wlan0: 1 RCR=0x153f00e
Jun 3 18:52:12 localhost kernel: r8712u 1-2:1.0 wlan0: 2 RCR=0x553f00e
Jun 3 18:52:12 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 3 18:52:12 localhost NetworkManager[1310]: <info> (wlan0): preparing device.
Jun 3 18:52:12 localhost NetworkManager[1310]: <info> (wlan0): deactivating device (reason 'managed') [2]
Jun 3 18:52:12 localhost NetworkManager[1310]: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
Jun 3 18:52:12 localhost NetworkManager[1310]: <info> (eth0): carrier is OFF
--------------------------------------------------------------------------------------------------------------------------

So, does this mean the driver won't work with my device, or is there another step I missed?

Also, spent some time looking at info on grub. But haven't figured out how to make kernel-lt boot by default. Only way I can get it to boot this way is via the grub menu. Any hints appreciated.


Thank you again for everyone's time and help.

ES.

[AlanBartlett]

To make kernel-lt the boot default, take a look in your /etc/grub.conf file. There you will see a line that begins default= with a number appended. That number is the index to the boot default kernel. The numbering sequence begins at zero and increments for each successive kernel listed.

I suspect the line currently reads as

default=1

and that kernel-lt is referenced in position zero.

So just edit the default= line to point to the kernel-lt entry.

Once you have sorted out the kernel boot default problem then make use of NetworkManager to correctly configure the wireless interface.