On 09.10.14 05:31, Alex Armstrong wrote:
Alexander Graf wrote:
Ok, I think I've squashed all issues with the upstream image. Things are still building, but once they settled down, please give it another try.
While fiddling with the image there's a good chance I fixed or broke the downstream image along the way. I'm not overly interested in downstream code, so whoever maintains that one, please stand up and check that things still work :).
Alex
Thanks for taking a look at this. I've tested image: openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build235.5.raw.xz
from: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp...
on 8 Oct. 14 and it boots to a functioning system, but has two failures.
Here is the breakdown: U-Boot loads and runs /boot.scr. Kernel loads and starts. All subsystems and modules load without failures. GPT starts , reads the SD card, checks the file system and resizes the root partition automatically. Systemd starts and begins loading units.
-- Here there is one failure -- [ 470.707495] systemd[1]: Found device /dev/disk/by-uuid/8b8c21e8-7bbe-41dd-a2a0-233eea2c7a2b. [ 470.728403] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. [ 470.760556] systemd[1]: Starting Remote File Systems (Pre).
Ah, I guess systemd wants to boot up to the graphical multiuser target which demands a display manager. But JeOS doesn't include any. I'm not sure whether it's a good idea to change the default target on JeOS. Maybe we're better off ignoring the error report above.
--
Then I get to a login prompt on the serial terminal. I can login as root and execute normal system commands.
-- However, on the graphical display I have a second failure -- YaST starts in ncurses mode, but gives this error:
"Calling the YaST module 'firstboot_setup_dhcp' has failed."
*Note that I didn't have network (or even a keyboard) hooked up on this run.
Connecting a keyboard at this point works fine. 'Retrying' from the YaST error dialog fails again, and using the 'Back' button drops you to a working login prompt. The error says to check /var/log/YaST2/y2log.
I guess that's because of the missing network link :(. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org