Am 06.09.2016 um 16:01 schrieb Alexander Graf:

On 09/06/2016 03:30 PM, Guillaume Gardet wrote:

...

I noticed that latest ARM images running u-boot (e.g. JeOS-beagle) are broken because: * Mke2fs now creates file systems with the metadata_csum and 64bit features enabled by default See: https://build.opensuse.org/package/view_file/openSUSE:Factory/e2fsprogs/e2fs...

* But u-boot does not support it: See: http://lists.denx.de/pipermail/u-boot/2016-July/261417.html

What would be the easiest way to tell kiwi to not use those features?

I remember that Andreas opened a bugzilla about that. I'm sure he can give more insight :)

Stefan did, but I'm in CC. :) https://bugzilla.suse.com/show_bug.cgi?id=989284 HTH, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Dienstag, 6. September 2016 15:03:16 CEST Brüns, Stefan wrote:

On Dienstag, 6. September 2016 16:10:49 CEST Andreas Färber wrote:

...

Am 06.09.2016 um 16:01 schrieb Alexander Graf:

...

On 09/06/2016 03:30 PM, Guillaume Gardet wrote:

...

I noticed that latest ARM images running u-boot (e.g. JeOS-beagle) are broken because: * Mke2fs now creates file systems with the metadata_csum and 64bit features enabled by default See: https://build.opensuse.org/package/view_file/openSUSE:Factory/e2fsprogs /e 2fsprogs.changes?expand=1

64bit is enabled according /etc/mke2fs.conf

*Neither* uninit_bg (implying GDT checksums) *nor* metadata_csum are enabled, and filesystems created by mkfs.ext4 have neither RO_COMPAT_GDT_CSUM nor RO_COMPAT_METADATA_CSUM flags set, which is consistent.

* the changelog entry regarding checksums seems to be WRONG ! *

...

...

...

* But u-boot does not support it: See: http://lists.denx.de/pipermail/u-boot/2016-July/261417.html

What would be the easiest way to tell kiwi to not use those features?

I remember that Andreas opened a bugzilla about that. I'm sure he can give more insight :)

Stefan did, but I'm in CC. :)

https://bugzilla.suse.com/show_bug.cgi?id=989284

The curious reader of the U-Boot devel ML may have seen some ext4 patches. What I have *not* already submitted upstream are the actual 64bit patches, as these need some cleanup.

Anyway, all ext4 patches, including 64bit support are part of my U-Boot branch package: https://build.opensuse.org/package/show/ home:StefanBruens:branches:Base:System/u-boot

There should be available also an Rpi3 image, depending on the aarch64 builder backlog ... https://build.opensuse.org/project/monitor/ home:StefanBruens:branches:devel:ARM:Factory:Contrib:RaspberryPi3

Ok, the XFCE image built fine, and I have just booted it on my RPi3. Listing the ext4 root from U-Boot works, and first and second boot works too. JeOS image not currently available, but thats an unrelated problem: "have choice for genisoimage needed by kiwi-desc-oemboot-requires: genisoimage cdrtools-cdrkit-compat, have choice ..." https://build.opensuse.org/project/monitor?utf8=%E2%9C%93&commit=Filter %3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&locked=1&deleting=1&pkgname=JeOS&repo_factory=1&repo_images=1&repo_qemu=1&repo_qemu_accel=1&repo_standard=1&arch_aarch64=1&arch_armv6l=1&arch_armv7l=1&arch_local=1&arch_x86_64=1&project=openSUSE %3AFactory%3AARM&defaults=0 Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 work: +49 2405 49936-424 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Wed, Sep 7, 2016 at 9:13 AM, Andreas Schwab wrote:

On Sep 07 2016, Stefan Bruens wrote:

...

JeOS image not currently available, but thats an unrelated problem: "have choice for genisoimage needed by kiwi-desc-oemboot-requires: genisoimage cdrtools-cdrkit-compat, have choice ..."

Should be fixed now.

Do you mean images here: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... I am not new to openSUSE, but I am new to using it on a Raspberry PI 3. I have tried both the 32- and 64-bit images, following the instructions on https://en.opensuse.org/HCL:Raspberry_Pi3. I get no activity on the device. No DHCP request. No activity on any of the 4 USB ports (where there should be a console login?). The Raspberry NOOBS (2016-06-08) works fine. But nothing from either of these: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.08.20-Build1.4.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.09.06-Build6.1.raw.xz -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am 07.09.2016 um 21:37 schrieb Freek de Kruijf:

Op woensdag 7 september 2016 14:03:38 schreef Roger Oberholtzer:

...

I get no activity on the device. No DHCP request. No activity on any of the 4 USB ports (where there should be a console login?).

openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.08.20-Build1.4.raw.xz

I tried that one too. Only got a colored screen. From the list I learned that soon there will be one that works. I had a older one from June, which works and I updated that one with "zypper up" and it still works.

IIRC colored screen means the proprietary firmware was loaded okay from the FAT partition. So maybe a problem with config.txt? ext4 should have nothing to do with that symptom.

...

openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.09.06-Build6 .1.raw.xz

I don't think that one will ever work on a RPi3.

Why not? I seem to be running a 2016.06.12 image, updated with zypper. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op maandag 12 september 2016 14:52:54 CEST schreef Freek de Kruijf:

I tried the image 2016.09.06 but first it hanged on a connected USB storage device. After disconnecting the USB device it hangs on "stub: Exiting boot services and installing virtual address map..."

I tried the 2016.09.11 version, but after writing the image on the micro-SD I tried to mount the ext4 partition. I got the error message: mount: wrong fs type, bad option, bad superblock on /dev/sdg2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. The above command showed: EXT4-fs (sdg2): bad geometry: block count 317680 exceeds size of device (316656 blocks) # fdisk -l /dev/sdg Disk /dev/sdg: 7.5 GiB, 8068792320 bytes, 15759360 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x29f8afe8 Device Boot Start End Sectors Size Id Type /dev/sdg1 2048 411651 409604 200M c W95 FAT32 (LBA) /dev/sdg2 413696 2955136 2541441 1.2G 83 Linux -- 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 14 september 2016 12:29:55 schreef Brüns, Stefan:

On Mittwoch, 14. September 2016 11:15:47 CEST Freek de Kruijf wrote:

...

Op maandag 12 september 2016 14:52:54 CEST schreef Freek de Kruijf:

...

I tried the image 2016.09.06 but first it hanged on a connected USB storage device. After disconnecting the USB device it hangs on "stub: Exiting boot services and installing virtual address map..."

I tried the 2016.09.11 version, but after writing the image on the micro-SD

...

I tried to mount the ext4 partition. I got the error message: Can you please specify the full URL to the image? Thanks.

http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... image: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.09.11- Build6.1.raw.xz -- 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 Thu, Sep 8, 2016 at 1:54 AM, Stefan Bruens wrote:

Aside from the ext4 problems, the JeOS RPi3 aarch64 image works, tested myself. You can either (after writing the image to the SD) modify the ext4 partition to disable the 64bit feature, or use an image with a patched U-Boot which supports the 64bit feature.

I cannot get either image to work. I do have a number of other images (non openSUSE) and they all work. I am fairly certain I know what I am doing with respect to getting an image installed and accessing the device. All my working images get an IP address from my DHCP server and are available as expected. I was happy to see that one of the OS images even advertised itself with Avahi. They just work. But the openSUSE images are a different matter. I do not even see it request a DHCP address (DHCPDISCOVER). Since I only have the 4 USB ports, I cannot see what the console is telling. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Thu, Sep 8, 2016 at 12:35 PM, Freek de Kruijf wrote:

There is a problem with the current image, openSUSE-Tumbleweed-ARM-JeOS- raspberrypi3.armv7l-2016.08.20-Build1.4.raw.xz, and that problem now also exists after updating an older version of the RPI3 image. I used openSUSE- Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.06.28-Build1.5.raw.xz and did a "zypper up" after which I again only get the colored screen, where, without the update, the system was running properly.

I would be happy to try the older openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.06.28-Build1.5.raw.xz if I had it. But it is no longer available. At least not where I am looking. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op donderdag 8 september 2016 12:35:41 schreef u:

Op donderdag 8 september 2016 08:14:01 schreef Roger Oberholtzer:

...

Since I only have the 4 USB ports, I cannot see what the console is telling.

There is a device which connects to pins of the GPIO device with a USB interface at the other end. When connecting the USB to your laptop or desktop you have a true console on the RPi. The price of this device is around euro 15.

There is a problem with the current image, openSUSE-Tumbleweed-ARM-JeOS- raspberrypi3.armv7l-2016.08.20-Build1.4.raw.xz, and that problem now also exists after updating an older version of the RPI3 image. I used openSUSE- Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.06.28-Build1.5.raw.xz and did a "zypper up" after which I again only get the colored screen, where, without the update, the system was running properly.

So I am waiting for the newer image and updated Tumbleweed repository.

After booting the old image and locking u-boot-rpi2 and u-boot-tools, I could update the system from the already configured repositories and that system still boots. So the problem seems to be in one or both of these packages. However after updating rapsberrypi-firmware, which removes a version with openSUSE in its name, from the other repository the system does not boot anymore, I only get the colored screen. -- 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 07/09/2016 à 03:20, Stefan Bruens a écrit :

...

On Dienstag, 6. September 2016 16:10:49 CEST Andreas Färber wrote:

...

Am 06.09.2016 um 16:01 schrieb Alexander Graf:

...

On 09/06/2016 03:30 PM, Guillaume Gardet wrote:

...

I noticed that latest ARM images running u-boot (e.g. JeOS-beagle) are broken because: * Mke2fs now creates file systems with the metadata_csum and 64bit features enabled by default See: https://build.opensuse.org/package/view_file/openSUSE:Factory/e2fsprogs /e 2fsprogs.changes?expand=1 64bit is enabled according /etc/mke2fs.conf

*Neither* uninit_bg (implying GDT checksums) *nor* metadata_csum are enabled, and filesystems created by mkfs.ext4 have neither RO_COMPAT_GDT_CSUM nor RO_COMPAT_METADATA_CSUM flags set, which is consistent.

* the changelog entry regarding checksums seems to be WRONG ! *

...

...

...

* But u-boot does not support it: See: http://lists.denx.de/pipermail/u-boot/2016-July/261417.html

What would be the easiest way to tell kiwi to not use those features? I remember that Andreas opened a bugzilla about that. I'm sure he can give more insight :) Stefan did, but I'm in CC. :)

https://bugzilla.suse.com/show_bug.cgi?id=989284 The curious reader of the U-Boot devel ML may have seen some ext4 patches. What I have *not* already submitted upstream are the actual 64bit patches, as these need some cleanup.

Anyway, all ext4 patches, including 64bit support are part of my U-Boot branch package: https://build.opensuse.org/package/show/ home:StefanBruens:branches:Base:System/u-boot

There should be available also an Rpi3 image, depending on the aarch64 builder backlog ... https://build.opensuse.org/project/monitor/ home:StefanBruens:branches:devel:ARM:Factory:Contrib:RaspberryPi3 Ok, the XFCE image built fine, and I have just booted it on my RPi3. Listing

On Dienstag, 6. September 2016 15:03:16 CEST Brüns, Stefan wrote: the ext4 root from U-Boot works, and first and second boot works too.

JeOS image not currently available, but thats an unrelated problem: "have choice for genisoimage needed by kiwi-desc-oemboot-requires: genisoimage cdrtools-cdrkit-compat, have choice ..."

SR#425084 to fix that is on the way: https://build.opensuse.org/request/show/425084 Guillaume

https://build.opensuse.org/project/monitor?utf8=%E2%9C%93&commit=Filter %3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&locked=1&deleting=1&pkgname=JeOS&repo_factory=1&repo_images=1&repo_qemu=1&repo_qemu_accel=1&repo_standard=1&arch_aarch64=1&arch_armv6l=1&arch_armv7l=1&arch_local=1&arch_x86_64=1&project=openSUSE %3AFactory%3AARM&defaults=0

Kind regards,

Stefan

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