Am 20.08.2012 12:04, schrieb Dirk �:

Hi,

over the weekend we've built 12.2 images and smoke-tested them on one board (Panda). The images are here:

http://download.opensuse.org/repositories/openSUSE:/12.2:/ARM/images/

We plan to announce them later as Release Candiate 1. If you own a Pandaboard, BeagleBoard or an EfikaMX, please give them a try. the Vexpress ones are iirc also completely untested so far. Any feedback (positive or negative) is highly welcome.

Thanks! Dirk

Hi Dirk, just tried the image "LimeJeOS-openSUSE-12.2-ARM-panda.armv7l-1.12.2-Build9.4.raw.xz" on a Pandaboard ES. I have only checked if WLAN works. It does not. ifconfig does not list a wlan interface. I guess the error message "wl12xx: ERROR could not get nvs file ti-connectivity/wl1271-nvs.bin: -2" in the boot log could be a reason... Apart from that I found this error message in the log: "leds-gpio: probe of leds-gpio failed with error -16". Regards, endym -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am 26.08.2012 16:11, schrieb Alexander Graf:

On 26.08.2012, at 06:01, endym wrote:

...

Am 20.08.2012 12:04, schrieb Dirk �:

...

Hi,

over the weekend we've built 12.2 images and smoke-tested them on one board (Panda). The images are here:

http://download.opensuse.org/repositories/openSUSE:/12.2:/ARM/images/

We plan to announce them later as Release Candiate 1. If you own a Pandaboard, BeagleBoard or an EfikaMX, please give them a try. the Vexpress ones are iirc also completely untested so far. Any feedback (positive or negative) is highly welcome.

Thanks! Dirk

Hi Dirk,

just tried the image "LimeJeOS-openSUSE-12.2-ARM-panda.armv7l-1.12.2-Build9.4.raw.xz" on a Pandaboard ES. I have only checked if WLAN works. It does not. ifconfig does not list a wlan interface. I guess the error message "wl12xx: ERROR could not get nvs file ti-connectivity/wl1271-nvs.bin: -2" in the boot log could be a reason...

This looks like missing firmware. Where do we get this from?

Maybe here: http://omappedia.org/wiki/Mac80211_based_open_source_architecture#Firmware_a...

...

Apart from that I found this error message in the log: "leds-gpio: probe of leds-gpio failed with error -16".

Does the LED blink for you?

None blinking. Both LEDs are always on.

Alex

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 26.08.2012, at 10:19, endym wrote:

Am 26.08.2012 18:53, schrieb endym:

...

Am 26.08.2012 16:11, schrieb Alexander Graf:

...

On 26.08.2012, at 06:01, endym wrote:

...

Am 20.08.2012 12:04, schrieb Dirk �:

...

Hi,

over the weekend we've built 12.2 images and smoke-tested them on one board (Panda). The images are here:

http://download.opensuse.org/repositories/openSUSE:/12.2:/ARM/images/

We plan to announce them later as Release Candiate 1. If you own a Pandaboard, BeagleBoard or an EfikaMX, please give them a try. the Vexpress ones are iirc also completely untested so far. Any feedback (positive or negative) is highly welcome.

Thanks! Dirk

Hi Dirk,

just tried the image "LimeJeOS-openSUSE-12.2-ARM-panda.armv7l-1.12.2-Build9.4.raw.xz" on a Pandaboard ES. I have only checked if WLAN works. It does not. ifconfig does not list a wlan interface. I guess the error message "wl12xx: ERROR could not get nvs file ti-connectivity/wl1271-nvs.bin: -2" in the boot log could be a reason...

This looks like missing firmware. Where do we get this from?

Maybe here: http://omappedia.org/wiki/Mac80211_based_open_source_architecture#Firmware_a...

Could you please try and see if copying them to the firmware dir makes things work for you?

...

...

...

Apart from that I found this error message in the log: "leds-gpio: probe of leds-gpio failed with error -16".

Does the LED blink for you?

None blinking. Both LEDs are always on.

...

Alex

Regarding the LEDs: Maybe the GPIO numbers of the Pandaboard ES are different to the Pandaboard (without ES). For the ES the LEDs are GPIO_110 and GPIO_WK8. When I export gpio 110 in /sys/class/gpio/export I see that the direction is "in" instead of "out". After correcting this I can toggle the LED.

Hrm. That sounds like an upstream bug then. Usually the LEDs should blink for status indication. But it's unimportant enough to not be a major issue now I hope :). Wifi not working is definitely worse. Alex

Regards, endym

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am 27.08.2012 11:57, schrieb Dirk Müller:

On Sunday 26 August 2012, endym wrote:

...

"LimeJeOS-openSUSE-12.2-ARM-panda.armv7l-1.12.2-Build9.4.raw.xz" on a Pandaboard ES. I have only checked if WLAN works. It does not. ifconfig does not list a wlan interface. I guess the error message "wl12xx: ERROR could not get nvs file ti-connectivity/wl1271-nvs.bin: -2" in the boot log could be a reason...

Hi,

great, thanks for the feedback. does it work if you manually copy the firmware file over? we can package it then and add it to the default configuration of the image so that future versions will have it working.

Thanks, Dirk

Ok, i have done following: - git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git - cp linux-firmware/ti-connectivity/wl127* /lib/firmware/`uname -r`/ti-connectivity/ - reboot - "ifconfig -a" shows a wlan0 device now Then i wanted to install yast2 with "zypper in patterns-openSUSE-yast2_basis" but this leads to "Problem: patterns-openSUSE-yast2_basis-12.2-10.2.armv7hl benötigt yast2-ncurses-pkg, was aber nicht angeboten werden kann Nicht installierbare Anbieter: libyui-ncurses-pkg4-2.42.0-1.1.armv7hl[suse-factory]" Then I tried a little bit with wpa_supplicant and could establish a connection to my WPA2 secured AP! However it was a IP6 connection and maybe the reason, that I can't connect from my notebook to the pandaboard via WLAN. Nevertheless it seems to work basically. If you can tell me how to install yast, then I could try it again. Regards, endym -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 04.09.2012, at 09:19, Peter Czanik wrote:

On 08/20/2012 12:04 PM, Dirk Müller wrote:

...

Hi,

over the weekend we've built 12.2 images and smoke-tested them on one board (Panda). The images are here:

http://download.opensuse.org/repositories/openSUSE:/12.2:/ARM/images/

We plan to announce them later as Release Candiate 1. If you own a Pandaboard, BeagleBoard or an EfikaMX, please give them a try. the Vexpress ones are iirc also completely untested so far. Any feedback (positive or negative) is highly welcome. A bit late answer as I was on holidays, far and away from my machines: I just tested it on the EFIKA MX smarttop. I have a serial console. Booting stops here:

[...] ## Loading init Ramdisk from Legacy Image at 92000000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 27762078 Bytes = 26.5 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK

Starting kernel ...

As there is now video driver yet for 3.x I did not expect anything on the attached screen, but the serial should work, AFAIK.

Yeah, if you pass in the correct console=, it should show something. Could you please try to trim it down a bit? Check the cmdline, try booting w/o initrd, etc. Alex

Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 05.09.2012, at 08:15, Peter Czanik wrote:

On 09/05/2012 05:02 AM, Alexander Graf wrote:

...

On 04.09.2012, at 09:19, Peter Czanik wrote:

...

On 08/20/2012 12:04 PM, Dirk Müller wrote:

...

Hi,

over the weekend we've built 12.2 images and smoke-tested them on one board (Panda). The images are here:

http://download.opensuse.org/repositories/openSUSE:/12.2:/ARM/images/

We plan to announce them later as Release Candiate 1. If you own a Pandaboard, BeagleBoard or an EfikaMX, please give them a try. the Vexpress ones are iirc also completely untested so far. Any feedback (positive or negative) is highly welcome. A bit late answer as I was on holidays, far and away from my machines: I just tested it on the EFIKA MX smarttop. I have a serial console. Booting stops here:

[...] ## Loading init Ramdisk from Legacy Image at 92000000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 27762078 Bytes = 26.5 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK

Starting kernel ...

As there is now video driver yet for 3.x I did not expect anything on the attached screen, but the serial should work, AFAIK. Yeah, if you pass in the correct console=, it should show something. Could you please try to trim it down a bit? Check the cmdline, try booting w/o initrd, etc.

Checked many different combinations, but I got "Starting kernel ..." all the time. Should I go back to the ancient 2.6.31 based Genesi kernel?

Phew. Upstream should work really, but I can't debug it myself atm :(.

AFAIR somebody made a package out of it, but I can't find it...

It should be in openSUSE:Factory:ARM:EfikaMX. Alex

Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Tuesday 11 September 2012, Dirk Müller wrote:

Thanks, so this confirms that we were just missing kernel-firmware in the images. I've added that now, please test (the image hasn't rebuilt yet).

Hi, the new 12.2 images contain kernel-firmware now in the image. can you confirm that it resolves the wifi issues you were seeing ? http://download.opensuse.org/repositories/openSUSE:/12.2:/ARM/images/ Thanks, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am 02.10.2012 21:05, schrieb endym:

Am 11.09.2012 12:58, schrieb Dirk M�ller:

...

On Monday 27 August 2012, endym wrote:

Hi,

...

Ok, i have done following: - git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git - cp linux-firmware/ti-connectivity/wl127* /lib/firmware/`uname -r`/ti-connectivity/ - reboot - "ifconfig -a" shows a wlan0 device now

Thanks, so this confirms that we were just missing kernel-firmware in the images. I've added that now, please test (the image hasn't rebuilt yet).

...

Then i wanted to install yast2 with "zypper in patterns-openSUSE-yast2_basis" but this leads to "Problem: patterns-openSUSE-yast2_basis-12.2-10.2.armv7hl benötigt yast2-ncurses-pkg, was aber nicht angeboten werden kann Nicht installierbare Anbieter: libyui-ncurses-pkg4-2.42.0-1.1.armv7hl[suse-factory]"

right, thats another issue I can reproduce. Trying to fix..

Greetings, Dirk

Hi!

I've tested with "openSUSE-12.2-ARM-panda.armv7l-1.12.1-Build1.19.1.raw.xz" and "ifconfig -a" shows the wlan0 device now out of the box. :-) Unfortunately I have none WLAN Access Point and no internet connection right now to do further tests. I will test this next week.

Best regards, endym

Hi again! I did some further Wi-Fi tests on the pandaboard es, but I do not get an IP4 address for the wlan0 interface: Sep 6 02:26:21 linux ifup[3802]: wlan0 Sep 6 02:26:21 linux ifup-wireless[3851]: wlan0 warning: WPA configured, but is untested Sep 6 02:26:21 linux ifup-wireless[3851]: wlan0 warning: with this device Sep 6 02:26:21 linux ifup-wireless[3851]: wlan0 starting wpa_supplicant Sep 6 02:26:21 linux kernel: [ 1584.505737] wl12xx: firmware booted (Rev 6.3.5.0.98) Sep 6 02:26:21 linux kernel: [ 1584.513610] ADDRCONF(NETDEV_UP): wlan0: link is not ready Sep 6 02:26:22 linux ifup-dhcp[3872]: Starting DHCP4 client on wlan0 Sep 6 02:26:22 linux dhcpcd[3914]: wlan0: dhcpcd 3.2.3 starting Sep 6 02:26:22 linux dhcpcd[3914]: wlan0: hardware address = de:ad:be:ef:00:00 Sep 6 02:26:22 linux dhcpcd[3914]: wlan0: broadcasting for a lease Sep 6 02:26:22 linux ifup-dhcp[3872]: . Sep 6 02:26:23 linux kernel: [ 1586.384490] wlan0: authenticate with 00:24:fe:a5:94:55 Sep 6 02:26:23 linux kernel: [ 1586.394531] wlan0: send auth to 00:24:fe:a5:94:55 (try 1/3) Sep 6 02:26:23 linux kernel: [ 1586.399963] wlan0: authenticated Sep 6 02:26:23 linux kernel: [ 1586.401947] wlan0: associate with 00:24:fe:a5:94:55 (try 1/3) Sep 6 02:26:23 linux kernel: [ 1586.405975] wlan0: RX AssocResp from 00:24:fe:a5:94:55 (capab=0x431 status=0 aid=3) Sep 6 02:26:23 linux kernel: [ 1586.414459] wlan0: associated Sep 6 02:26:23 linux kernel: [ 1586.416259] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Sep 6 02:26:26 linux ifup-dhcp[3872]: . Sep 6 02:26:33 ifup-dhcp[3872]: last message repeated 2 times Sep 6 02:26:33 linux kernel: [ 1596.581542] wlan0: no IPv6 routers present Sep 6 02:26:37 linux ifup-dhcp[3872]: . Sep 6 02:26:41 linux ifup-dhcp[3872]: . Sep 6 02:26:42 linux dhcpcd[3914]: wlan0: timed out Sep 6 02:26:42 linux dhcpcd[3914]: wlan0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-wlan0.info' Sep 6 02:26:42 linux dhcpcd[3914]: wlan0: broadcasting for a lease Sep 6 02:26:45 linux ifup-dhcp[3872]: . Sep 6 02:26:48 linux ifup-dhcp[3872]: . Sep 6 02:26:50 linux ifup-dhcp[3872]: Sep 6 02:26:50 linux ifup-dhcp[3872]: wlan0 DHCP4 continues in background Sep 6 02:27:02 linux dhcpcd[3914]: wlan0: timed out Sep 6 02:27:02 linux dhcpcd[3914]: wlan0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-wlan0.info' Sep 6 02:27:02 linux dhcpcd[3914]: wlan0: broadcasting for a lease Sep 6 02:27:22 linux dhcpcd[3914]: wlan0: timed out *********************************************** cat /etc/sysconfig/network/ifcfg-wlan0 BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' WIRELESS_WPA_CONF='/etc/wpa_supplicant/wpa_supplicant.conf' *********************************************** cat /etc/wpa_supplicant/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ ssid="myssid" key_mgmt=WPA-PSK psk="mysecretkey" *********************************************** ifconfig wlan0 wlan0 Link encap:Ethernet Hardware Adresse DE:AD:BE:EF:00:00 inet6 Adresse: fe80::dcad:beff:feef:0/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:185 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:1000 RX bytes:2682 (2.6 Kb) TX bytes:52462 (51.2 Kb) *********************************************** Any help would be appreciated! Best regards, endym -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org