piCore 5.1rc3

[sbp]

My TP-LINK TL-WN721N adapter with Atheros AR9271 chip works fine.

Hi bmarkus.

Do you need to load any special firmware to use this wifi adaptor?

Steen

[bmarkus]

Hi Steen

thanks for trying it. Freezed rc3, no more kernel changes before release.

Bela

[bmarkus]

My TP-LINK TL-WN721N adapter with Atheros AR9271 chip works fine.

Hi bmarkus.

Do you need to load any special firmware to use this wifi adaptor?

Steen

It requires a firmware but nothing special, it is in the repo:

Code: [Select]

[    2.914527] usb 1-1.2: new high-speed USB device number 4 using dwc_otg
[    3.036057] usb 1-1.2: New USB device found, idVendor=0cf3, idProduct=9271
[    3.036089] usb 1-1.2: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[    3.036106] usb 1-1.2: Product: USB2.0 WLAN
[    3.036119] usb 1-1.2: Manufacturer: ATHEROS
[    3.036135] usb 1-1.2: SerialNumber: 12345
...
[  249.013448] cfg80211: Calling CRDA to update world regulatory domain
[  249.611017] usb 1-1.2: ath9k_htc: Firmware htc_9271.fw requested
[  249.622481] usbcore: registered new interface driver ath9k_htc
[  256.647694] usb 1-1.2: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
[  256.892371] ath9k_htc 1-1.2:1.0: ath9k_htc: HTC initialized with 33 credits
[  257.324557] ath9k_htc 1-1.2:1.0: ath9k_htc: FW Version: 1.3
[  257.324623] ath: EEPROM regdomain: 0x809c
[  257.324636] ath: EEPROM indicates we should expect a country code
[  257.324650] ath: doing EEPROM country->regdmn map search
[  257.324660] ath: country maps to regdmn code: 0x52
[  257.324676] ath: Country alpha2 being used: CN
[  257.324710] ath: Regpair used: 0x52
[  257.335897] ieee80211 phy0: Atheros AR9271 Rev:1


[sbp]

Hi bmarkus

Just checked the repro:
http://distro.ibiblio.org/tinycorelinux/4.x/armv6/tcz/ .... which is the link obtained from the front page.
or
http://tinycorelinux.net/4.x/armv6/tcz/ ... Which is the link obtained from the top of the forum page marked Download

I can only find:

Code: [Select]

firmware-ralinkwifi.tcz

But not 

Code: [Select]

firmware-rtlwifi.tcz
which previously was available

Also where is the firmware for your TP-Link firmware?

Steen

[bmarkus]

firmware-atheros.tcz

Maybe you need to delete cached repo data and recheck (/tmp/md5.db /tmp/tags.db)

[Alligadi]

Thanks a lot for this great ARM port!! It works flawlessly. Next weekend I will maybe compile some extensions: fluxbox, wmctrl, volumeicon. xpdf, roxfiler, midori, (and maybe mplayer but I'm not sure if I will be able to achieve that with hardware acceleration) and commit them.

[bmarkus]

Thanks a lot for this great ARM port!! It works flawlessly. Next weekend I will maybe compile some extensions: fluxbox, wmctrl, volumeicon. xpdf, roxfiler, midori, (and maybe mplayer but I'm not sure if I will be able to achieve that with hardware acceleration) and commit them.

Thanks! Contributions to repo are welcome. If you have something send it to picoresubmit@gmail.com

[bmarkus]

According to feedback and my own experience using rc3 intensively it is ready for final release. I'm preparing 5.1 release now.

[Gerrelt]

Nice work Bmarkus! 

[sbp]

Hi bmarkus

To follow up on the wifi issue - I just received a new wifi dongle "Edimax EW-7811UN 150Mbps Wireless Nano USB Adapter" it is working perfectly with piCore 5.1rc3

Using the 8192cu module just as my now retired comfast wifi dongle

Steen 

[Paul_123]

Finally got around to testing these.   I could not get my keyboard to work with this image.    The image would boot to the command prompt, just no keyboard......of course with no keyboard, I could not get any diagnostics.

Never had this problem with any Picore image or Rasbian.

[bmarkus]

Finally got around to testing these.   I could not get my keyboard to work with this image.    The image would boot to the command prompt, just no keyboard......of course with no keyboard, I could not get any diagnostics.

Never had this problem with any Picore image or Rasbian.

What is the keybord make/model?

Is it connected directly to Pi or via USB hub?

[Paul_123]

What is the keybord make/model?

Is it connected directly to Pi or via USB hub?
[/quote]

Asus AK1D.   I tried it plugged it directly into the Pi, and a usb hub.

Here is how it is recognized on a working system

Code: [Select]

[16164.075207] usb 1-1.2: new low-speed USB device number 6 using dwc_otg
[16164.185908] usb 1-1.2: New USB device found, idVendor=04f2, idProduct=1125
[16164.185939] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[16164.185957] usb 1-1.2: Product: Asus Keyboard
[16164.185973] usb 1-1.2: Manufacturer: CHICONY
[16164.272195] input: CHICONY Asus Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/input/input1
[16164.273204] chicony 0003:04F2:1125.0002: input: USB HID v1.11 Keyboard [CHICONY Asus Keyboard] on usb-bcm2708_usb-1.2/input0
[16164.295169] input: CHICONY Asus Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.1/input/input2
[16164.297976] chicony 0003:04F2:1125.0003: input,hiddev0: USB HID v1.11 Device [CHICONY Asus Keyboard] on usb-bcm2708_usb-1.2/input1


[Mithotyn]

I have the same problem with a wireless Logitech K400r plugged in directly. It is working on Raspbian. Die not tried any other piCore release.

Happy new year from germany!
Joachim

[bmarkus]

I have the same problem with a wireless Logitech K400r plugged in directly. It is working on Raspbian. Die not tried any other piCore release.

Happy new year from germany!
Joachim

Thanks, Happay New Year too!

See http://forum.tinycorelinux.net/index.php/topic,16439.0.html