[opensuse-arm] Some tests with RPi 1 images
I tested Build319.9 in /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/ This image shows an error message about not finding the boot device and reboots again after 120 sec., etc. So there is something wrong in the partition boot. None of the images in this repository works. I tested Build330.7 in upstream /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ which still contains the bug in yast in bug report https://bugzilla.opensuse.org/show_bug.cgi?id=936788 When booting I see an error message about an error in a udev rule, but the system still boots. This system appears usable. I tested Build330.8 in upstream /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ which boots, but shows an error about /home and finally reboots again after a wait time of 120 sec., so does not work. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Tests with RPi2 images
I tested Build320.12 from the repository: /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2/ which works OK. I tested Build321.14 from the repository: /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2:/Staging/ which works OK. Both these images do NOT show any message on the screen after the initial boot. As soon as the openSUSE boot image is used the screen blanks and only the final prompt is shown. It would be more instructive to see how the partitions are expanded and configured. When starting the image for the first time the date/time is set, apparently at about the date/time the image is build (Aug 05 02:00 CEST). Booting the image the next time this date/time is Jan 1 1970 02:00 CEST. I wonder if it is possible to preserve the shutdown time so that the next boot gets that time. In that case date/time in logs are ascending. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Some tests with RPi 1 images
Op donderdag 6 augustus 2015 14:43:35 schreef Freek de Kruijf: > I tested Build319.9 in > /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/ > This image shows an error message about not finding the boot device and > reboots again after 120 sec., etc. So there is something wrong in the > partition boot. > > None of the images in this repository works. Also the newest Build319.11 does not work. > I tested Build330.7 in upstream > /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ > which still contains the bug in yast in bug report > https://bugzilla.opensuse.org/show_bug.cgi?id=936788 > When booting I see an error message about an error in a udev rule, but the > system still boots. > > This system appears usable. > > I tested Build330.8 in upstream > /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ > which boots, but shows an error about /home and finally reboots again after > a wait time of 120 sec., so does not work. But the newest Build330.10 works again. The bug is not solved. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Re: USB WLAN interface fails when booting
Michael Ströder wrote: > Michael Ströder wrote: >> Michael Ströder wrote: >>> It seems kernel 4.1.3 has landed in Factory repo for armv6 but I have some >>> doubts about package dtb-bcm2835: >>> >>> v | openSUSE-Factory-repo-oss | dtb-bcm2835 | >>> 4.0.5-41.1 >>> | 4.1.2-45.1| armv6hl >>> v | openSUSE-Factory-repo-oss | kernel-default| >>> 4.0.5-3.1 >>> | 4.1.3-1.1 | armv6hl >>> >>> As you can see its version is 4.1.2-45.1. Does that fit kernel 4.1.3? >> >> I've successfully re-installed a problematic rpi1 installation with image >> openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build330.4.raw with >> kernel 4.1.3. >> >> But it does not setup the USB WLAN interface right during boot. wlan0 is >> bridged together with eth0, hostapd is listening on wlan0 for access point >> function. I can manually configure the bridged interface on console after >> login without problems though. >> >> This setup used to work without any issues with kernel 4.0.5. All other >> systems using only eth0 are working without any issues. FYI: Finally dtb-bcm2835-4.1.3-47.1 reached this system and now it works. Ciao, Michael. smime.p7s Description: S/MIME Cryptographic Signature
