armv6 and realtek firmware

[stephanmg]

Code: [Select]

$ wget http://tinycorelinux.net/11.x/x86_64/tcz/firmware-atheros.tcz
$ wget http://tinycorelinux.net/11.x/x86_64/tcz/firmware-atheros.tcz.md5.txt
$ mv firmware-atheros.tcz* /mnt/mmcblk0p2/tce/optional
$ tce-load -i firmware-atheros

Okay, but, just wondering this says x86_64 not arm, right? After I downloaded this, then I can load the wifi extension (wifi.tcz) from here http://distro.ibiblio.org/tinycorelinux/11.x/armv6/tcz/

[Juanito]

Affirmative

[stephanmg]

Affirmative

Ok, I'll test this out when I'm back from work, probably in the evening. Thanks for your assistance!

[aus9]

reply 13 from OP

1a2c:0e24

1a2c  China Resource Semico Co., Ltd.......Vendor ID known
   http://www.linux-usb.org/usb.ids

but a search of the product draws a blank so maybe it is?

Maybe OP could post their full lsusb output?

[Juanito]

piCore has busybox lsusb in the base, which gives this:

Code: [Select]

$ lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:ec00
Bus 001 Device 002: ID 0424:9514
The full lsusb is more useful:

Code: [Select]

$ tce-load -i usbutils
$ /usr/local/bin/lsusb
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


[aus9]

I was trying to suggest to OP that we need the full lsusb. On my RPi I just happen to look at my lsusb and I have the exact device that the OP might be claiming is a network device.Its a multimedia keyboard brand JBurrows in Australia. Might be called something else overseas.

Code: [Select]

lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1a2c:0e24 China Resource Semico Co., Ltd --------------------its a kb
Bus 001 Device 003: ID 04f3:0235 Elan Microelectronics Corp. Optical Mouse
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[aus9]

I should add some trivia, I did not know I had this USB id keyboard until just then.

What happened was, got tired of swapping my usb kb to a recently purchased RPi which I have only owned for a number of days. So only just bought the  cheapest kb for the RPI and thats when I discovered the id issue.

this is what my tower ids look like

Code: [Select]

lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0000:3825 
Bus 001 Device 010: ID c0f4:04c0 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Yep I buy cheap

[stephanmg]

Hello yes, I will provide full lsusb output. I didn't know I need to first tce-load something.

Btw.: The adapter is definitely an Atheros WLAN USB stick, which I bought years back as it was advertised to be supported by on RPi OOTB.

Will later post the lsusb output.

best,
Stephan

[stephanmg]

Can I somehow upload an image to the forum?

Unfortunately after loading the usbutils it reports:
Cannot find shared library libusb-1.0.so.0.

I figured out that I missed depdencies: here it comes.

Bus 001 Device 004: Edimax Techonology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUs].

So I take everything back I said: It seems to be Realtek. Sorry!

[stephanmg]

Driver registered in dmesg output. lsmod shows also the RTL module inserted.

However,
sudo wifi.sh,
yields
No "wireless devices".

What am I missing here?

Best wishes,
Stephan

[Juanito]

Does dmesg say anything about missing firmware for your device?

[stephanmg]

No all is good now, I had to load additional modules.
As a reference, maybe also for future TCL users and in particular for me, here is what I did:

Install stable release for ARMv6 (http://tinycorelinux.net/11.x/armv6/releases/RPi/)

Then I installed the following packages (http://distro.ibiblio.org/tinycorelinux/11.x/armv6/tcz/):

Code: [Select]

firmware-rpi-wifi
libnl
libudev
libusb
usb-ids
wifi
wireless-4.19.81-piCore
wireless_tools
wpa_supplicant
Created a shell script:

Code: [Select]

#!/bin/sh
tce-load -i firmware-rpi-wifi
tce-load -i libnl
tce-load -i libudev
tce-load -i libusb
tce-load -i usb-ids
tce-load -i wifi
tce-load -i wireless-4.19.81-piCore
tce-load -i wireless_tools
tce-load -i wpa_supplicant

Next I verified my device with

Code: [Select]

lsusb and

Code: [Select]

dmesg | tail -20 as well as

Code: [Select]

lsmod
Enabling my wireless interface via

Code: [Select]

sudo ifconfig wlan0 up (The interface can be found with `iwlist`)
Next, use

Code: [Select]

iwlist wlan0 scan to scan for wireless networks.

Use

Code: [Select]

wpa_passphrase to generate with ESSID and Passphrase a configuration, make sure you follow precisely the output provided by

Code: [Select]

iwlist for the fields

Code: [Select]

key_mgmt and

Code: [Select]

pairwise and

Code: [Select]

group Check if access point (AP) uses WPA1 or WPA2, uncomment the field proto maybe. (My AP said WPA2 but it really seems to be WPA1... then you get a Skip RSN/WPA proto mismatch error during running

Code: [Select]

wpa_supplicant in debug mode. Store in some location, I stored my config in /home/tc as wpa_supplicant.conf.

Next execute

Code: [Select]

wpa_supplicant -i wlan0 -D wext -c /home/tc/config -d & to authenticate with AP.

Check with

Code: [Select]

iwconfig if authenticated with AP, then use

Code: [Select]

udhcpc -i wlan0 to aquire an IP address. (Make sure that your AP has your device added. I use a Macfilter in my AP to allow only certain devices).

The last step in this tutorial is to add it to the boot configuration, which I right now do not know how to do, so I created a small script

Code: [Select]

wlan.sh

Code: [Select]

#!/bin/sh
sudo wpa_supplicant -i wlan0 -D wext -c /home/tc/config -d &
sudo udhcpc -i wlan0
Which I execute in my .ashrc configuration file.

Hit

Code: [Select]

backup then

Code: [Select]

reboot
Wireless LAN should be made available automatically now.

Best wishes,
Stephan

[stephanmg]

I presume I could add the scripts to

Code: [Select]

/opt/bootlocal.sh
Correct?

[Rich]

Hi stephanmg
Yes, you can add them to  /opt/bootlocal.sh.

[stephanmg]

Is this the best option?

I presume this is not the TCL-idomatic way, since I am learning TCL right now.

Hi stephanmg
Yes, you can add them to  /opt/bootlocal.sh.