Op zondag 28 februari 2016 14:23:49 schreef Michael Ströder:

guillaume.gardet@free.fr wrote:

...

I have a RPi2 running kodi with GPU working fine since a while.

Can you elaborate on which image you used to install it?

Because since quite a while no downloadable image works, neither for rpi1 nor for rpi2. (For rpi1 I saved old images which I can update via zypper dup.)

Ciao, Michael.

The current JeOS image, Build386.3 for RPi2 from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... works. Did not try the other images XFCE and LXQT. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op maandag 29 februari 2016 12:22:07 schreef u:

Freek de Kruijf wrote:

...

Op zondag 28 februari 2016 14:23:49 schreef Michael Ströder:

...

guillaume.gardet@free.fr wrote:

...

I have a RPi2 running kodi with GPU working fine since a while.

Can you elaborate on which image you used to install it?

Because since quite a while no downloadable image works, neither for rpi1 nor for rpi2. (For rpi1 I saved old images which I can update via zypper dup.)

The current JeOS image, Build386.3 for RPi2 from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ra spberryPi2/images/ works. Did not try the other images XFCE and LXQT.

Unfortunately Build386.3 is not available anymore.

Tried these without success (USB and eth0 does not work): openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-1.12.1-Build386.4.raw.xz openSUSE-Tumbleweed-ARM-XFCE-raspberrypi2.armv7l-1.12.1-Build386.4.raw.xz

Ciao, Michael.

Just tested that one too, indeed, no network. Also a restart shows an error message about a missing zImage. Will try to repair that. Later this day. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Montag, 29. Februar 2016 13:19:32 CET Michael Ströder wrote:

Freek de Kruijf wrote:

...

Op maandag 29 februari 2016 12:22:07 schreef u:

...

Tried these without success (USB and eth0 does not work): openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-1.12.1-Build386.4.raw.xz openSUSE-Tumbleweed-ARM-XFCE-raspberrypi2.armv7l-1.12.1-Build386.4.raw.xz

Just tested that one too, indeed, no network. Also a restart shows an error message about a missing zImage. Will try to repair that. Later this day.

Interesting that it seems to try a TFTP boot. Is such a TFTP boot really possible?

Ciao, Michael.

U-Boot recently enabled USB by default, so now DHCP/TFTP is possible ootb. Haven't tested this on RPi2, but on RPi1 it works. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 work: +49 2405 49936-424

Freek de Kruijf wrote:

The newest JeOS Build389.1 works again. I appreciate that the initial messages about booting from the FAT partition and from the ext3 partition are shown again.

HOORAY! I don't have to use Debian...! Thanks a lot. Ciao, Michael.

Op vrijdag 4 maart 2016 16:37:23 schreef ariel sabiguero yawelak:

Hi all. Is there any directory of "working images" for Pi 2? I downloaded several images over months and none of them worked on my devices. I already purchased a serial adapter in order to get debug info, but it is comming from China. Could you provide "proven" links to images?

best regards

ariel

El 01/03/16 a las 08:44, Michael Ströder escribió:

...

Freek de Kruijf wrote:

...

The newest JeOS Build389.1 works again. I appreciate that the initial messages about booting from the FAT partition and from the ext3 partition are shown again.

The above JeOS Build389.1 works headless. It comes from: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... However Build389.1 is no longer there. I assume openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2016.03.04-Build2.1.raw.xz will work. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Thanks for your e-mail, and sorry for the delay. I wanted to sum-up my tests. I tried recently -at least- with: -rw-r--r-- 1 asabigue users 672718948 feb 15 18:59 openSUSE-Tumbleweed-ARM-XFCE-raspberrypi2.armv7l-1.12.1-Build376.1.raw.xz -rw-r--r-- 1 asabigue users 245607708 feb 21 22:20 openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-1.12.1-Build376.2.raw.xz -rw-r--r-- 1 asabigue users 153361796 feb 25 20:46 openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-1.12.1-Build385.2.raw.xz -rw-r--r-- 1 asabigue users 575629708 feb 25 20:48 openSUSE-Tumbleweed-ARM-XFCE-raspberrypi2.armv7l-1.12.1-Build385.1.raw.xz -rw-r--r-- 1 asabigue users 552049368 feb 25 20:50 openSUSE-Tumbleweed-ARM-LXQT-raspberrypi2.armv7l-1.12.1-Build385.1.raw.xz -rw-r--r-- 1 asabigue users 153139772 feb 29 12:04 openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-1.12.1-Build386.4.raw.xz none of them worked. Then just hang on a black screen inmediately after de coloured square of video initialization flashes. After your e-mail I decided to go over my steps again and give another try to a fresh build and: -rw-r--r-- 1 asabigue users 177311392 mar 5 07:36 openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2016.03.04-Build3.1.raw.xz booted! correctly. Today I downloaded and tested the new -rw-r--r-- 1 asabigue users 177423536 mar 8 20:48 openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2016.03.07-Build2.2.raw.xz with a new failure. I rooled back to 03.04 and finally, I have a booting system! Summing up: only 1 of the 8 images I currently have on my HDD works. Thanks to your comment, I managed to download the working version. Anyway, it seems very, very unstable, making me wonder if it is a good idea to build a system on top of the R-PI2 regards ariel El 05/03/16 a las 08:16, Dirk Müller escribió:

Hi Ariel,

...

I downloaded several images over months and none of them worked on my devices. I already purchased a serial adapter in order to get debug info, but it is comming from China. Could you provide "proven" links to images? could you share a bit of information which image you used and what error you hit? there should be output on HDMI as well as on serial.

TIA, Dirk

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

Op woensdag 9 maart 2016 11:33:54 schreef Freek de Kruijf:

I tried openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2016.03.07-Build2.2.raw.xz like you and it worked. My setup is RPi 2 with micro SD card of 8 GB, HDMI device connected, Ethernet cable connected. After applying power I see messages about booting from the SD card till booting the initrd. After that the screen is black for several minutes. Finally a greeting message appears showing the version of Tumbleweed and a login prompt. I continue by accessing the system via ssh. I don't know anything about a connected touchscreen.

Indeed there is a problem. A new boot with the generated system does not succeed. The system is trying to boot from the network. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op woensdag 9 maart 2016 13:34:40 schreef Alexander Graf:

On 03/09/2016 01:18 PM, Freek de Kruijf wrote:

...

Op woensdag 9 maart 2016 11:33:54 schreef Freek de Kruijf:

...

I tried openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2016.03.07-Build2.2.raw. xz like you and it worked. My setup is RPi 2 with micro SD card of 8 GB, HDMI device connected, Ethernet cable connected. After applying power I see messages about booting from the SD card till booting the initrd. After that the screen is black for several minutes. Finally a greeting message appears showing the version of Tumbleweed and a login prompt. I continue by accessing the system via ssh. I don't know anything about a connected touchscreen.

Indeed there is a problem. A new boot with the generated system does not succeed. The system is trying to boot from the network.

So it doesn't find the boot.scr file? Does it exist?

Yes it exists in /boot/, which is the ext3 partition. I compared this build with the working Build389.1 and I do not see any obvious difference with what is on the vfat partitions and on the ext3 partitions. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op woensdag 9 maart 2016 14:40:58 schreef Alexander Graf:

On 03/09/2016 02:28 PM, Freek de Kruijf wrote:

...

Op woensdag 9 maart 2016 13:34:40 schreef Alexander Graf:

...

On 03/09/2016 01:18 PM, Freek de Kruijf wrote:

...

Op woensdag 9 maart 2016 11:33:54 schreef Freek de Kruijf:

...

I tried openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2016.03.07-Build2.2.ra w. xz like you and it worked. My setup is RPi 2 with micro SD card of 8 GB, HDMI device connected, Ethernet cable connected. After applying power I see messages about booting from the SD card till booting the initrd. After that the screen is black for several minutes. Finally a greeting message appears showing the version of Tumbleweed and a login prompt. I continue by accessing the system via ssh. I don't know anything about a connected touchscreen.

Indeed there is a problem. A new boot with the generated system does not succeed. The system is trying to boot from the network.

So it doesn't find the boot.scr file? Does it exist?

Yes it exists in /boot/, which is the ext3 partition. I compared this build with the working Build389.1 and I do not see any obvious difference with what is on the vfat partitions and on the ext3 partitions.

If you have both a working and a non-working image around, could you please compare the output of "printenv" on the u-boot command line on both and send the diff?

Hello Alex, I need more guidance here. I assume printenv needs to given on the RPi2 system. How can I give that command on a system that does not boot. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 09/03/2016 18:19, Alexander Graf a écrit :

...

Am 09.03.2016 um 18:02 schrieb Freek de Kruijf :

Op woensdag 9 maart 2016 14:40:58 schreef Alexander Graf:

...

...

Op woensdag 9 maart 2016 13:34:40 schreef Alexander Graf:

...

On 03/09/2016 01:18 PM, Freek de Kruijf wrote:

...

Op woensdag 9 maart 2016 11:33:54 schreef Freek de Kruijf: > I tried > openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2016.03.07-Build2.2.ra > w. > xz > like you and it worked. > My setup is RPi 2 with micro SD card of 8 GB, HDMI device connected, > Ethernet cable connected. After applying power I see messages about > booting > from the SD card till booting the initrd. After that the screen is > black > for several minutes. Finally a greeting message appears showing the > version > of Tumbleweed and a login prompt. > I continue by accessing the system via ssh. > I don't know anything about a connected touchscreen. Indeed there is a problem. A new boot with the generated system does not succeed. The system is trying to boot from the network. So it doesn't find the boot.scr file? Does it exist? Yes it exists in /boot/, which is the ext3 partition. I compared this build with the working Build389.1 and I do not see any obvious difference with what is on the vfat partitions and on the ext3 partitions. If you have both a working and a non-working image around, could you

On 03/09/2016 02:28 PM, Freek de Kruijf wrote: please compare the output of "printenv" on the u-boot command line on both and send the diff? Hello Alex,

I need more guidance here. I assume printenv needs to given on the RPi2 system. How can I give that command on a system that does not boot. U-boot comes up, right? In U-boot, press space to get a command prompt. On that prompt, type "printenv" :)

Alex, for RPi1, u-boot.bin differs between 1st boot and 2nd boot! Maybe it is the same here. How is it possible? Replacing broken u-boot by working one fixed the boot for me. Guillaume

Alex

...

-- fr.gr.

member openSUSE Freek de Kruijf

-- 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

Le 09/03/2016 22:41, Alexander Graf a écrit :

...

Le 09/03/2016 18:19, Alexander Graf a écrit :

...

...

Am 09.03.2016 um 18:02 schrieb Freek de Kruijf :

I need more guidance here. I assume printenv needs to given on the RPi2 system. How can I give that command on a system that does not boot. U-boot comes up, right? In U-boot, press space to get a command prompt. On that prompt, type "printenv" :) Alex, for RPi1, u-boot.bin differs between 1st boot and 2nd boot! Maybe it is the same here. How is it possible?

Replacing broken u-boot by working one fixed the boot for me. Can you dig out of rpm where the different versions come from? Maybe

On 09.03.16 22:38, Guillaume Gardet wrote: there's a typo in the efi enablement patches.

Well, in fact it was a 2016.03-rc2 (working) and a 2016.03-rc3 (broken). I think the problem is u-boot tries to boot EFI partition for Raspberry Pi. On 1st boot, 1st partition is hidden and after, 1st parition is labelled EFI. Upstream u-boot (latest GIT) is working, so I guess it is a problem with your EFI patches. ;) Could have a look, please? Guillaume

Alex

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

Le 09/03/2016 18:02, Freek de Kruijf a écrit :

Op woensdag 9 maart 2016 14:40:58 schreef Alexander Graf:

...

...

Op woensdag 9 maart 2016 13:34:40 schreef Alexander Graf:

...

On 03/09/2016 01:18 PM, Freek de Kruijf wrote:

...

Op woensdag 9 maart 2016 11:33:54 schreef Freek de Kruijf:

...

I tried openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2016.03.07-Build2.2.ra w. xz like you and it worked. My setup is RPi 2 with micro SD card of 8 GB, HDMI device connected, Ethernet cable connected. After applying power I see messages about booting from the SD card till booting the initrd. After that the screen is black for several minutes. Finally a greeting message appears showing the version of Tumbleweed and a login prompt. I continue by accessing the system via ssh. I don't know anything about a connected touchscreen. Indeed there is a problem. A new boot with the generated system does not succeed. The system is trying to boot from the network. So it doesn't find the boot.scr file? Does it exist? Yes it exists in /boot/, which is the ext3 partition. I compared this build with the working Build389.1 and I do not see any obvious difference with what is on the vfat partitions and on the ext3 partitions. If you have both a working and a non-working image around, could you

On 03/09/2016 02:28 PM, Freek de Kruijf wrote: please compare the output of "printenv" on the u-boot command line on both and send the diff? Hello Alex,

I need more guidance here. I assume printenv needs to given on the RPi2 system. How can I give that command on a system that does not boot.

Could you stop u-boot by pressing 'space' key and then type: setenv boot_prefixes '/ /boot/' boot For an unknown reason on my RPi1 boot_prefixes is defined in u-boot on 1st boot, but not on 2nd boot. :( Maybe the same happened here. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org