Alexander Graf wrote:
On 09.10.14 05:31, Alex Armstrong wrote:
-- 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.
I haven't noticed this error on subsequent boots. And it's easy enough to set multi-user.target as the default after first login - I agree we can ignore this for now.
--
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
I tried again with build: openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build235.11.raw on 17 Oct. 14 This time I started it up with keyboard, monitor, net plugged in. I had the same network error and an additional error ('firstboot_language_keyboard cannot import namespace GfxMenu'). But using the 'Next' button allowed me to set the time zone and root password as well as the authentication method. After which I got to a working login prompt. At this point it seems to work fine, network ssh login, local login and serial login are all good. So, it seems to be working alright, just a few rough edges on first boot. I'm afraid I don't have time to chase the YaST bugs right now. I think the underlying problem has been fixed, and we can mark this thread as solved. -ARA -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org