[opensuse-arm] Tests of latest images for RPi1
Build336.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the SD is partitioned and the resulting system boots. However the Ethernet connection does not become active. The lights stay off. I could not find a method to list the journal on the SD partition on a system where the SD is mounted. Build325.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/ does the low level boot, but after that, like before, can't find the boot image on the 3rd partition. Upgrading a system build earlier with a working image works OK. Finally the problem using the command "yast lan" is solved. -- 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 dinsdag 1 september 2015 22:31:43 schreef Freek de Kruijf:
Build336.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the SD is partitioned and the resulting system boots. However the Ethernet connection does not become active. The lights stay off. I could not find a method to list the journal on the SD partition on a system where the SD is mounted.
I also tried Build336.3, but that one produces a corrupt ext4 partition like earlier images. -- 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 dinsdag 1 september 2015 22:31:43 schreef Freek de Kruijf:
Build336.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the SD is partitioned and the resulting system boots. However the Ethernet connection does not become active. The lights stay off. I could not find a method to list the journal on the SD partition on a system where the SD is mounted.
Finally found the method to analyze the journal on the SD card. I mount the SD
card on my desktop and use the command "journalct --file
Op donderdag 3 september 2015 13:34:06 schreef Freek de Kruijf:
Op dinsdag 1 september 2015 22:31:43 schreef Freek de Kruijf:
Build336.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the SD is partitioned and the resulting system boots. However the Ethernet connection does not become active. The lights stay off. I could not find a method to list the journal on the SD partition on a system where the SD is mounted.
I also tried Build336.3, but that one produces a corrupt ext4 partition like earlier images.
Tried the latest Build339.4 from RasberryPi:/upstream. It produces a corrupt ext4 partition, but it runs, but no Ethernet connection. Tried the latest Build327.4 from RasberryPi. U-boot can't find a bootable system in /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
Op vrijdag 11 september 2015 22:47:37 schreef Freek de Kruijf:
Op donderdag 3 september 2015 13:34:06 schreef Freek de Kruijf:
Op dinsdag 1 september 2015 22:31:43 schreef Freek de Kruijf:
Build336.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the SD is partitioned and the resulting system boots. However the Ethernet connection does not become active. The lights stay off. I could not find a method to list the journal on the SD partition on a system where the SD is mounted.
I also tried Build336.3, but that one produces a corrupt ext4 partition like earlier images.
Tried the latest Build339.4 from RasberryPi:/upstream. It produces a corrupt ext4 partition, but it runs, but no Ethernet connection.
Tried Build340.3 same problem a corrupt ext4 partition. The latest working image is Build330.10 from August 6, 2015.
Tried the latest Build327.4 from RasberryPi. U-boot can't find a bootable system in /boot.
I filed a bug report for this problem. https://bugzilla.opensuse.org/show_bug.cgi?id=947675 -- 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
Am 26.09.2015 um 11:56 schrieb Freek de Kruijf:
Op vrijdag 11 september 2015 22:47:37 schreef Freek de Kruijf:
Op donderdag 3 september 2015 13:34:06 schreef Freek de Kruijf:
Op dinsdag 1 september 2015 22:31:43 schreef Freek de Kruijf:
Build336.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the SD is partitioned and the resulting system boots. However the Ethernet connection does not become active. The lights stay off. I could not find a method to list the journal on the SD partition on a system where the SD is mounted.
I also tried Build336.3, but that one produces a corrupt ext4 partition like earlier images.
Tried the latest Build339.4 from RasberryPi:/upstream. It produces a corrupt ext4 partition, but it runs, but no Ethernet connection.
Tried Build340.3 same problem a corrupt ext4 partition. The latest working image is Build330.10 from August 6, 2015.
Tried the latest Build327.4 from RasberryPi. U-boot can't find a bootable system in /boot.
I filed a bug report for this problem. https://bugzilla.opensuse.org/show_bug.cgi?id=947675
The last few weeks I have been getting error mails that kpartx hangs during :RaspberryPi and :RaspberryPi:upstream image builds. $ osc jobhist devel:ARM:Factory:Contrib:RaspberryPi:upstream JeOS-raspberrypi images armv6l [...] 2015-09-24 23:37:02 CET JeOS-raspberrypi meta change succeeded 1h 41m 53s cloud124:1 2015-09-28 19:09:43 CET JeOS-raspberrypi source change failed 8h 46m 10s cloud123:1 2015-09-30 13:34:30 CET JeOS-raspberrypi meta change failed 9h 15m 25s build21:11 2015-11-01 08:49:26 CET JeOS-raspberrypi source change failed 9h 3m 55s cumulus3:3 2015-11-03 13:32:05 CET JeOS-raspberrypi meta change failed 8h 34m 43s build74:3 2015-11-03 23:15:43 CET JeOS-raspberrypi meta change failed 9h 22m 42s build34:1 2015-11-05 18:34:54 CET JeOS-raspberrypi source change failed 8h 28m 3s build80:2 2015-11-06 20:25:13 CET JeOS-raspberrypi meta change failed 8h 29m 28s build85:4 2015-11-07 11:49:41 CET JeOS-raspberrypi meta change failed 9h 29m 23s build21:5 2015-11-09 02:09:09 CET JeOS-raspberrypi meta change failed 8h 51m 41s cloud111:1 2015-11-09 17:14:08 CET JeOS-raspberrypi meta change failed 8h 41m 1s build85:1 2015-11-10 21:29:05 CET JeOS-raspberrypi meta change failed 9h 54m 53s build13:5 2015-11-12 08:36:23 CET JeOS-raspberrypi source change failed 8h 49m 46s cloud124:3 2015-11-12 20:40:39 CET JeOS-raspberrypi source change failed 8h 32m 51s build81:1 2015-11-13 11:12:44 CET JeOS-raspberrypi meta change failed 9h 37m 20s cumulus3:10 2015-11-14 00:34:20 CET JeOS-raspberrypi meta change failed 8h 33m 48s build72:3 2015-11-14 09:46:28 CET JeOS-raspberrypi meta change failed 9h 12m 3s build33:10 2015-11-16 00:30:03 CET JeOS-raspberrypi meta change failed 9h 28m 33s build34:2 I believe it may be related to several errors like this: [ 5646s] Unsupported ioctl: cmd=0x5331 (0) ... which would hint at parted using a new ioctl (CDROM_GET_CAPABILITY) that's not yet implemented for qemu-arm binary. Might also just be symptoms of the previously reported ext4 corruption... Also, dtb-armv6l kept failing for lack of bcm2708*.dts files, meaning that kernel and dtb packages were out of sync. Why has no Raspberry Pi downstream-kernel user taken care of fixing that for months?! https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryP... 2015-08-17 16:12:19 CET dtb-armv6l new build succeeded 10m 27s cloud130:4 2015-08-17 16:25:36 CET dtb-armv6l source change failed 5m 5s build82:1 2015-08-21 21:47:33 CET dtb-armv6l meta change failed 17m 27s build21:9 2015-08-25 15:20:56 CET dtb-armv6l meta change failed 7m 33s cloud120:2 2015-09-01 03:58:46 CET dtb-armv6l meta change failed 15m 18s build21:6 2015-09-04 04:14:30 CET dtb-armv6l meta change failed 7m 55s cloud115:3 2015-09-09 05:37:59 CET dtb-armv6l meta change failed 5m 51s build75:4 2015-09-11 16:27:02 CET dtb-armv6l meta change failed 4m 35s build77:4 2015-09-17 00:49:05 CET dtb-armv6l meta change failed 11m 3s build21:7 2015-09-20 17:34:20 CET dtb-armv6l meta change failed 7m 54s cloud130:2 2015-09-25 22:20:45 CET dtb-armv6l meta change failed 4m 35s build81:3 2015-10-02 23:33:08 CET dtb-armv6l meta change failed 5m 11s build75:2 2015-10-07 02:28:53 CET dtb-armv6l meta change failed 14m 3s build24:1 2015-10-15 09:12:29 CET dtb-armv6l meta change failed 7m 11s morla1:24 2015-10-20 17:54:06 CET dtb-armv6l meta change failed 11m 1s cloud118:4 2015-10-22 21:19:39 CET dtb-armv6l meta change failed 7m 32s cloud111:3 2015-10-29 09:03:23 CET dtb-armv6l meta change failed 5m 42s build84:2 2015-11-06 12:45:49 CET dtb-armv6l meta change failed 10m 1s cloud123:1 2015-11-08 10:38:21 CET dtb-armv6l source change failed 7m 47s cloud102:3 I've reverted Guillaume's changes to local dtb-source, so that it just packages bcm2835*.dts, like Base:System dtb-source does. Only diff is the two *.changes entries now. https://build.opensuse.org/request/show/344714 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
participants (2)
-
Andreas Färber -
Freek de Kruijf