On 23.11.14 15:22, Freek de Kruijf wrote:
Op zondag 23 november 2014 00:10:14 schreef u:
Please just dd the image onto your sd card and then boot it up straight from there. The first boot will fix up the gpt headers and repartition the card :).
Thanks Alex,
indeed the SD card gets initialized, like I did. I also see the lights coming up, so apparently the Ethernet interface comes up. However the system does not get an IP address. Inspecting the /var/log/messages later shows that wicked gets started, however there no log entry it gets an IP address.
Do you happen to have a ttl serial cable you could connect to the board to see what it's doing?
No. I don't have such a thing, but the /var/log/messages gives some information. See above.
Meh. I just tried to run 13.2 locally on a RPi as well and it looks like Andreas' analysis is correct: Network doesn't work because yast2 firstboot didn't finish yet. You have a few options: 1) Attach a monitor using HDMI and finish yast2 firstboot or 2) Remove the file /var/lib/YaST2/reconfig_system from the target rootfs 3) Attach a serial cable to the uart GPIOs and kill the firstboot process I think in your case, option 2 is the easiest. I'm not really sure how to properly deal with this in our image creation. Some users have a serial cable / monitor attached and want to set the root password on first boot, others don't. How can we accomodate both? Maybe we should add a timeout to the firstboot screen? That way if nobody pressed anything for say 60 seconds, it would automatically quit and leave all the default settings. Bootup could then continue, network would come up and you'd just run using the default password at first. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org