[opensuse-arm] BananaPi: Leap and sata
Hello to all, yesterday I installed Leap from this source: http://download.opensuse.org/ports/armv7hl/distribution/leap/42.2/appli ances/ The first boot finished with a black screen - nothing happened even after a few minutes!? After this: poweroff an poweron - the second boot was fine. :-) Then I tried to copy the root-partition from the sd-card to a ssd like I did with the Tumbleweed-Images. I changed the bootargs in the boot.script and created a new boot.scr. But the boot isn't possible - see below the last lines of the log. Now my questions: - Why is the first boot with Leap not ok? - Is the u-boot of Leap without ahci-support? Thanks a lot Stefan ... Jan 01 01:00:14 linux systemd[1]: Starting Create Static Device Nodes in /dev... Jan 01 01:00:14 linux systemd[1]: Starting Apply Kernel Variables... Jan 01 01:00:14 linux systemd[1]: Started Create Static Device Nodes in /dev. Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'dev/cdrom/autoclose', ignoring: No such file or directory Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file o Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or Jan 01 01:00:14 linux systemd[1]: Started Apply Kernel Variables. Jan 01 01:00:14 linux systemd[1]: Started dracut cmdline hook. Jan 01 01:00:14 linux systemd[1]: Starting udev Kernel Device Manager... Jan 01 01:00:14 linux systemd-udevd[170]: Network interface NamePolicy= disabled by default. Jan 01 01:00:14 linux systemd[1]: Started udev Kernel Device Manager. Jan 01 01:00:14 linux systemd[1]: Starting udev Coldplug all Devices... Jan 01 01:00:15 linux systemd[1]: Started udev Coldplug all Devices. Jan 01 01:00:15 linux systemd[1]: Reached target Remote File Systems (Pre). Jan 01 01:00:15 linux systemd[1]: Reached target Remote File Systems. Jan 01 01:00:15 linux systemd[1]: Mounting Configuration File System... Jan 01 01:00:15 linux systemd[1]: Mounted Configuration File System. Jan 01 01:00:16 linux kernel: usbcore: registered new interface driver usbfs Jan 01 01:00:16 linux kernel: usbcore: registered new interface driver hub Jan 01 01:00:16 linux kernel: usbcore: registered new device driver usb Jan 01 01:00:16 linux kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jan 01 01:00:16 linux kernel: ehci-platform: EHCI generic platform driver Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: No vqmmc regulator found Jan 01 01:00:16 linux kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Jan 01 01:00:16 linux kernel: ohci-platform: OHCI generic platform driver Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: Got CD GPIO Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: base:0xf08fe000 irq:28 Jan 01 01:00:16 linux kernel: mmc0: host does not support reading read-only switch, assuming write-enable Jan 01 01:00:16 linux kernel: mmc0: new high speed SDHC card at address e624 Jan 01 01:00:16 linux kernel: mmcblk0: mmc0:e624 SU08G 7.40 GiB Jan 01 01:00:16 linux kernel: mmcblk0: p1 p2 p3 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am I the once who want to install on a ssd? Is the u-boot of Leap without ahci-support? Thanks a lot Stefan -------- Weitergeleitete Nachricht -------- Von: Stefan Mack <mack.stefan@web.de> An: opensuse-arm@opensuse.org Betreff: [opensuse-arm] BananaPi: Leap and sata Datum: Sat, 07 Jan 2017 16:34:24 +0100 Hello to all, yesterday I installed Leap from this source: http://download.opensuse.org/ports/armv7hl/distribution/leap/42.2/appli ances/ The first boot finished with a black screen - nothing happened even after a few minutes!? After this: poweroff an poweron - the second boot was fine. :-) Then I tried to copy the root-partition from the sd-card to a ssd like I did with the Tumbleweed-Images. I changed the bootargs in the boot.script and created a new boot.scr. But the boot isn't possible - see below the last lines of the log. Now my questions: - Why is the first boot with Leap not ok? - Is the u-boot of Leap without ahci-support? Thanks a lot Stefan ... Jan 01 01:00:14 linux systemd[1]: Starting Create Static Device Nodes in /dev... Jan 01 01:00:14 linux systemd[1]: Starting Apply Kernel Variables... Jan 01 01:00:14 linux systemd[1]: Started Create Static Device Nodes in /dev. Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'dev/cdrom/autoclose', ignoring: No such file or directory Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file o Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or Jan 01 01:00:14 linux systemd[1]: Started Apply Kernel Variables. Jan 01 01:00:14 linux systemd[1]: Started dracut cmdline hook. Jan 01 01:00:14 linux systemd[1]: Starting udev Kernel Device Manager... Jan 01 01:00:14 linux systemd-udevd[170]: Network interface NamePolicy= disabled by default. Jan 01 01:00:14 linux systemd[1]: Started udev Kernel Device Manager. Jan 01 01:00:14 linux systemd[1]: Starting udev Coldplug all Devices... Jan 01 01:00:15 linux systemd[1]: Started udev Coldplug all Devices. Jan 01 01:00:15 linux systemd[1]: Reached target Remote File Systems (Pre). Jan 01 01:00:15 linux systemd[1]: Reached target Remote File Systems. Jan 01 01:00:15 linux systemd[1]: Mounting Configuration File System... Jan 01 01:00:15 linux systemd[1]: Mounted Configuration File System. Jan 01 01:00:16 linux kernel: usbcore: registered new interface driver usbfs Jan 01 01:00:16 linux kernel: usbcore: registered new interface driver hub Jan 01 01:00:16 linux kernel: usbcore: registered new device driver usb Jan 01 01:00:16 linux kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jan 01 01:00:16 linux kernel: ehci-platform: EHCI generic platform driver Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: No vqmmc regulator found Jan 01 01:00:16 linux kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Jan 01 01:00:16 linux kernel: ohci-platform: OHCI generic platform driver Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: Got CD GPIO Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: base:0xf08fe000 irq:28 Jan 01 01:00:16 linux kernel: mmc0: host does not support reading read-only switch, assuming write-enable Jan 01 01:00:16 linux kernel: mmc0: new high speed SDHC card at address e624 Jan 01 01:00:16 linux kernel: mmcblk0: mmc0:e624 SU08G 7.40 GiB Jan 01 01:00:16 linux kernel: mmcblk0: p1 p2 p3 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Stefan, 42.2 is definitely using an older U-Boot version than Tumbleweed. We just compile using the upstream defaults, so maybe AHCI is not enabled yet / broken / disabled / something there? As an easy workaround, you could just keep your /boot partition on the SD card though. Performance wise that should make very little difference, as the booted system will still be able to use the AHCI attached SATA disk. Alex On 01/10/2017 01:15 PM, Stefan Mack wrote:
Am I the once who want to install on a ssd? Is the u-boot of Leap without ahci-support?
Thanks a lot Stefan
-------- Weitergeleitete Nachricht -------- Von: Stefan Mack <mack.stefan@web.de> An: opensuse-arm@opensuse.org Betreff: [opensuse-arm] BananaPi: Leap and sata Datum: Sat, 07 Jan 2017 16:34:24 +0100
Hello to all,
yesterday I installed Leap from this source: http://download.opensuse.org/ports/armv7hl/distribution/leap/42.2/appli ances/ The first boot finished with a black screen - nothing happened even after a few minutes!?
After this: poweroff an poweron - the second boot was fine. :-)
Then I tried to copy the root-partition from the sd-card to a ssd like I did with the Tumbleweed-Images. I changed the bootargs in the boot.script and created a new boot.scr. But the boot isn't possible - see below the last lines of the log.
Now my questions: - Why is the first boot with Leap not ok? - Is the u-boot of Leap without ahci-support?
Thanks a lot Stefan
... Jan 01 01:00:14 linux systemd[1]: Starting Create Static Device Nodes in /dev... Jan 01 01:00:14 linux systemd[1]: Starting Apply Kernel Variables... Jan 01 01:00:14 linux systemd[1]: Started Create Static Device Nodes in /dev. Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'dev/cdrom/autoclose', ignoring: No such file or directory Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file o Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or Jan 01 01:00:14 linux systemd[1]: Started Apply Kernel Variables. Jan 01 01:00:14 linux systemd[1]: Started dracut cmdline hook. Jan 01 01:00:14 linux systemd[1]: Starting udev Kernel Device Manager... Jan 01 01:00:14 linux systemd-udevd[170]: Network interface NamePolicy= disabled by default. Jan 01 01:00:14 linux systemd[1]: Started udev Kernel Device Manager. Jan 01 01:00:14 linux systemd[1]: Starting udev Coldplug all Devices... Jan 01 01:00:15 linux systemd[1]: Started udev Coldplug all Devices. Jan 01 01:00:15 linux systemd[1]: Reached target Remote File Systems (Pre). Jan 01 01:00:15 linux systemd[1]: Reached target Remote File Systems. Jan 01 01:00:15 linux systemd[1]: Mounting Configuration File System... Jan 01 01:00:15 linux systemd[1]: Mounted Configuration File System. Jan 01 01:00:16 linux kernel: usbcore: registered new interface driver usbfs Jan 01 01:00:16 linux kernel: usbcore: registered new interface driver hub Jan 01 01:00:16 linux kernel: usbcore: registered new device driver usb Jan 01 01:00:16 linux kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jan 01 01:00:16 linux kernel: ehci-platform: EHCI generic platform driver Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: No vqmmc regulator found Jan 01 01:00:16 linux kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Jan 01 01:00:16 linux kernel: ohci-platform: OHCI generic platform driver Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: Got CD GPIO Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: base:0xf08fe000 irq:28 Jan 01 01:00:16 linux kernel: mmc0: host does not support reading read-only switch, assuming write-enable Jan 01 01:00:16 linux kernel: mmc0: new high speed SDHC card at address e624 Jan 01 01:00:16 linux kernel: mmcblk0: mmc0:e624 SU08G 7.40 GiB Jan 01 01:00:16 linux kernel: mmcblk0: p1 p2 p3
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello Alex, thanks for your reply. That's the way I do with Tumbleweed: I move the root-partition (and perhaps swap) on the ssd, the boot-partition stays on the sd-card. But with Leap that's unfortunately not possible, the log stops with ...linux kernel: mmc0: new high speed SDHC card at address e624 ...linux kernel: mmcblk0: mmc0:e624 SU08G 7.40 GiB ...linux kernel: mmcblk0: p1 p2 p3 With the Leap standard installation (root-partition on sd-card, too) the ssd is recogniced later. What can I do? Stefan -------- Weitergeleitete Nachricht -------- Von: Alexander Graf <agraf@suse.de> An: Stefan Mack <mack.stefan@web.de>, opensuse-arm@opensuse.org Betreff: Re: [opensuse-arm] BananaPi: Leap and sata Datum: Tue, 10 Jan 2017 13:18:52 +0100 Hi Stefan, 42.2 is definitely using an older U-Boot version than Tumbleweed. We just compile using the upstream defaults, so maybe AHCI is not enabled yet / broken / disabled / something there? As an easy workaround, you could just keep your /boot partition on the SD card though. Performance wise that should make very little difference, as the booted system will still be able to use the AHCI attached SATA disk. Alex On 01/10/2017 01:15 PM, Stefan Mack wrote:
Am I the once who want to install on a ssd? Is the u-boot of Leap without ahci-support?
Thanks a lot Stefan
-------- Weitergeleitete Nachricht -------- Von: Stefan Mack <mack.stefan@web.de> An: opensuse-arm@opensuse.org Betreff: [opensuse-arm] BananaPi: Leap and sata Datum: Sat, 07 Jan 2017 16:34:24 +0100
Hello to all,
yesterday I installed Leap from this source: http://download.opensuse.org/ports/armv7hl/distribution/leap/42.2/app li ances/ The first boot finished with a black screen - nothing happened even after a few minutes!?
After this: poweroff an poweron - the second boot was fine. :-)
Then I tried to copy the root-partition from the sd-card to a ssd like I did with the Tumbleweed-Images. I changed the bootargs in the boot.script and created a new boot.scr. But the boot isn't possible - see below the last lines of the log.
Now my questions: - Why is the first boot with Leap not ok? - Is the u-boot of Leap without ahci-support?
Thanks a lot Stefan
... Jan 01 01:00:14 linux systemd[1]: Starting Create Static Device Nodes in /dev... Jan 01 01:00:14 linux systemd[1]: Starting Apply Kernel Variables... Jan 01 01:00:14 linux systemd[1]: Started Create Static Device Nodes in /dev. Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'dev/cdrom/autoclose', ignoring: No such file or directory Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file o Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or Jan 01 01:00:14 linux systemd[1]: Started Apply Kernel Variables. Jan 01 01:00:14 linux systemd[1]: Started dracut cmdline hook. Jan 01 01:00:14 linux systemd[1]: Starting udev Kernel Device Manager... Jan 01 01:00:14 linux systemd-udevd[170]: Network interface NamePolicy= disabled by default. Jan 01 01:00:14 linux systemd[1]: Started udev Kernel Device Manager. Jan 01 01:00:14 linux systemd[1]: Starting udev Coldplug all Devices... Jan 01 01:00:15 linux systemd[1]: Started udev Coldplug all Devices. Jan 01 01:00:15 linux systemd[1]: Reached target Remote File Systems (Pre). Jan 01 01:00:15 linux systemd[1]: Reached target Remote File Systems. Jan 01 01:00:15 linux systemd[1]: Mounting Configuration File System... Jan 01 01:00:15 linux systemd[1]: Mounted Configuration File System. Jan 01 01:00:16 linux kernel: usbcore: registered new interface driver usbfs Jan 01 01:00:16 linux kernel: usbcore: registered new interface driver hub Jan 01 01:00:16 linux kernel: usbcore: registered new device driver usb Jan 01 01:00:16 linux kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jan 01 01:00:16 linux kernel: ehci-platform: EHCI generic platform driver Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: No vqmmc regulator found Jan 01 01:00:16 linux kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Jan 01 01:00:16 linux kernel: ohci-platform: OHCI generic platform driver Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: Got CD GPIO Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: base:0xf08fe000 irq:28 Jan 01 01:00:16 linux kernel: mmc0: host does not support reading read-only switch, assuming write-enable Jan 01 01:00:16 linux kernel: mmc0: new high speed SDHC card at address e624 Jan 01 01:00:16 linux kernel: mmcblk0: mmc0:e624 SU08G 7.40 GiB Jan 01 01:00:16 linux kernel: mmcblk0: p1 p2 p3
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 16.01.2017 um 17:50 schrieb Stefan Mack <mack.stefan@web.de>:
Hello Alex,
thanks for your reply.
That's the way I do with Tumbleweed: I move the root-partition (and perhaps swap) on the ssd, the boot-partition stays on the sd-card. But with Leap that's unfortunately not possible, the log stops with
...linux kernel: mmc0: new high speed SDHC card at address e624 ...linux kernel: mmcblk0: mmc0:e624 SU08G 7.40 GiB ...linux kernel: mmcblk0: p1 p2 p3
With the Leap standard installation (root-partition on sd-card, too) the ssd is recogniced later.
That probably means that the kernel module needed for the sata rootfs is not in your initrd. Try $ mkinitrd -A Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello Alex, that was it, thanks! The boot time after mkinitrd -A and copying the root-partition on the ssd is 34s (see my config below) and with only sd-card 32s. Stefan vdrbanana:/boot # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 119,2G 0 disk ├─sda1 8:1 0 1,5G 0 part [SWAP] ├─sda2 8:2 0 20G 0 part / └─sda3 8:3 0 90G 0 part /archiv mmcblk0 179:0 0 7,4G 0 disk ├─mmcblk0p1 179:1 0 196M 0 part /boot ├─mmcblk0p2 179:2 0 6,7G 0 part └─mmcblk0p3 179:3 0 485,5M 0 part vdrbanana:/boot # poweroff -------- Weitergeleitete Nachricht -------- Von: Alexander Graf <agraf@suse.de> An: Stefan Mack <mack.stefan@web.de> Kopie: opensuse-arm@opensuse.org Betreff: Re: [opensuse-arm] BananaPi: Leap and sata Datum: Mon, 16 Jan 2017 18:12:58 +0100
Am 16.01.2017 um 17:50 schrieb Stefan Mack <mack.stefan@web.de>:
Hello Alex,
thanks for your reply.
That's the way I do with Tumbleweed: I move the root-partition (and perhaps swap) on the ssd, the boot-partition stays on the sd-card. But with Leap that's unfortunately not possible, the log stops with
...linux kernel: mmc0: new high speed SDHC card at address e624 ...linux kernel: mmcblk0: mmc0:e624 SU08G 7.40 GiB ...linux kernel: mmcblk0: p1 p2 p3
With the Leap standard installation (root-partition on sd-card, too) the ssd is recogniced later.
That probably means that the kernel module needed for the sata rootfs is not in your initrd. Try $ mkinitrd -A Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Alexander Graf -
Stefan Mack