On 10 Jul 2016, at 04:12, Stefan Bruens
wrote: On Sonntag, 10. Juli 2016 03:17:06 CEST you wrote:
Am 10.07.2016 um 00:57 schrieb Stefan Bruens
: On Sonntag, 10. Juli 2016 00:47:47 CEST Stefan Bruens wrote:
On Freitag, 8. Juli 2016 12:05:33 CEST Alexander Graf wrote:
On 08.07.16 12:02, Peter Czanik wrote: Hi,
After quite a bit of delay, my Pine64 is here. The boards boots with the Android image, so I wanted to give openSUSE a try. I downloaded the image from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib: / Pi ne64:/Downstream/images/openSUSE-Tumbleweed-ARM-JeOS-pine64.aarch64.raw . xz as this one is supposed to have graphics, but after about 15 minutes the screen is still blank. Is it normal? Did anyone test the image recently?
IIRC I added console=ttyAMA0 to the default kernel command line. You do see grub2 coming up?
Alex
Just switched power supplies, no I get:
Booting `openSUSE-Tumbleweed-ARM-JeOS-pine64'
Loading Linux 3.10.65-1-pine64aw ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: UEFI Secure Boot is enabled. [ 0.000000] script buffer is NULL! [ 27.735603] axp81x_board_init: axp regl_devs num = 23 [ 27.988108] Warning: can not find np for pmu1. [ 27.988441] add_sys_pwr_dm: get ldo name for id: vcc-lpddr failed [ 27.988718] Warning: can not find np for dynamic_standby_para. [ 32.063459] hci: ERR: sunxi_ehci is null [ 32.063470] hci: ERR: sunxi_ohci is null [ 32.063504] hci: ERR: sunxi_ehci is null [ 32.063515] hci: ERR: sunxi_ohci is null [ 34.186102] Failed to alloc md5 [ 34.484571] get() with no identifier [ 34.488470] get() with no identifier [ 34.492365] get() with no identifier [ 34.560263] Call trace: [ 34.562972] plugout_end:switch:0 [ 34.583294] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 52, RTO !! [ 34.590853] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 52, RTO !! [ 34.602220] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !! [ 34.612782] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !! [ 34.620154] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !! [ 34.627519] sunxi-mmc 1c0f000.sdmmc: smc 0 p0 err, cmd 5, RTO !! [ 34.713047] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RE !! [ 34.719938] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 52, RE !! [ 34.730274] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 8, RE !! [ 34.737065] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RE !! [ 34.743879] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RE !! [ 34.750633] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RE !! [ 34.757368] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 5, RE !! [ 34.764119] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RE !! [ 34.770965] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RE !! [ 34.777793] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RE !! [ 34.784634] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 55, RE !! [ 34.791568] sunxi-mmc 1c10000.sdmmc: smc 1 p1 err, cmd 1, RE !! [ 34.900927] systemd[1]: Failed to start Load Kernel Modules. [FAILED] Failed to start Load Kernel Modules. See 'systemctl status systemd-modules-load.service' for details.
Starting Apply Kernel Variables... Starting Create Static Device Nodes in /dev...
[ OK ] Started Apply Kernel Variables. [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started Journal Service. [ OK ] Started dracut cmdline hook.
Starting udev Kernel Device Manager...
[ OK ] Started udev Kernel Device Manager.
Starting udev Coldplug all Devices... Mounting Configuration File System...
[ OK ] Mounted Configuration File System. [ OK ] Started udev Coldplug all Devices. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ TIME ] Timed out waiting for device dev-di...L64G_0x70c31c5f \x2dpart3.device. [DEPEND] Dependency failed for Resume from h...y-id/mmc-SL64G_0x70c31c5f- part3. [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. [ OK ] Reached target System Initialization. [ OK ] Reached target Basic System. [** ] A start job is running for dev-disk...rt2.device (1min 48s / no limit)^C ... [ ***] A start job is running for dev-disk...rt2.device (7min 22s / no limit)
I think this indicates a previous failed firstboot run. Please try to reflash the original image onto your sd card, then try again with your known-good power supply :). Keep in mind that first boot may take a few minutes (just remove the quiet option from the kernel cmdline to see what's going on).
Alex
Tried again with a fresh SD install:
On first boot attempt, after loading of the kernel/initrd, the "screen" is is cleared, and after about 2 minutes the boot commences with the normal systemd messages about started services.
After a reboot, the GPT seems to be broken:
U-Boot reports:
Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device GUID Partition Table Entry Array CRC is wrong: 0xb58bf7a3 != 0x5c9246a8 get_partition_info_efi: *** ERROR: Invalid GPT *** get_partition_info_efi: *** Using Backup GPT ***
This indicates that we’re writing the SPL/boot0 to the SD card, but didn’t resize the GPT properly to make space for it. The code that should have done this is here at line 287: https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM/JeOS/uboot-image-install.in?expand=1&rev=446 I guess using the absolute path /usr/src/packages/KIWIROOT-oem/usr/sbin/gdisk in the firstboot script isn’t the smartest idea. Instead we should just set PATH accordingly. I’ve checked in an updated version of the description that hopefully build correct images: https://build.opensuse.org/package/rdiff/openSUSE:Factory:ARM/JeOS?linkrev=base&rev=447 Please give it a try once you see the new build emerge :). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org