Wireless network?

[fvdw]

where did you put the .fw file ?

[fvdw]

it should be looking in the right place (/lib/firmware), but Jocko made some change in udev rules need to check if that still works ok. Wait a few minutes

[fvdw]

I found the problem, its a bug we forgot to include a script to load the firmware :mrgreen:

Unpack the attached file (firmware.sh) and put it in the /sbin folder
Make it executable

Code: Select all

chmod 755 /sbin/firmware.sh

now try again with the 1.3 version firmware you downloaded

[steean]

Success!

Code: Select all

[ 6703.534909] usb 1-1: new high-speed USB device number 6 using orion-ehci
[ 6703.705922] usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
[ 6703.712601] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[ 6703.719991] usb 1-1: Product: USB2.0 WLAN
[ 6703.723986] usb 1-1: Manufacturer: ATHEROS
[ 6703.728094] usb 1-1: SerialNumber: 12345
[ 6703.735534] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
[ 6704.087933] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
[ 6704.323182] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
[ 6704.534435] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
[ 6704.539844] ath: EEPROM regdomain: 0x809c
[ 6704.539856] ath: EEPROM indicates we should expect a country code
[ 6704.539869] ath: doing EEPROM country->regdmn map search
[ 6704.539880] ath: country maps to regdmn code: 0x52
[ 6704.539891] ath: Country alpha2 being used: CN
[ 6704.539901] ath: Regpair used: 0x52
[ 6704.547177] ieee80211 phy0: Atheros AR9271 Rev:1

This is from the webgui:

Code: Select all

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  6 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1
P:  Vendor=0cf3 ProdID=9271 Rev=01.08
S:  Manufacturer=ATHEROS
S:  Product=USB2.0 WLAN
S:  SerialNumber=12345
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 6 Cls=ff(vend.) Sub=00 Prot=00 Driver=ath9k_htc

[fvdw]

well it means you dongle is ready for use

to see if it work you can give this command

Code: Select all

ifconfig wlan0 up

after that just give command

Code: Select all

ifconfig

to see if the wlan0 interface comes up

[steean]

Code: Select all

wlan0     Link encap:Ethernet  HWaddr 64:66:B3:1A:B5:F2 
          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)

Should I just write the kernel now, before proceeding?

[fvdw]

yes you can write the kernel to /dev/sda6, its more handy then every time loading it as external kernel

I trust that you know how to set up the rest using wpa-supplicant and so on. If not just let me know

[steean]

I guess I could, but I really don't want to mess up anything and make my NAS unreachable on the LAN..
But I guess I don't have to disable Ethernet..

If you could write something up, I'd appreciate it (as may many others), but no hassle. And thanks so much for your help so far!

[fvdw]

There is no risk that it gets unreachable in the network as long as you leave the boot scripts alone ;)
So far only the driver is loaded and eth0 (fixed LAN cable) is still up
I will write something together in next days

[fvdw]

for info

I released a new version of the fvdw-sl console that is compatible with windows 8.1, so the error messages are gone.
there is even a 64bits version available now.

The how to for wireles will follow