[opensuse-arm] Kernel 4.11-rc5 testing status
Hello, A little delayed, here's a first update on Kernel:HEAD 4.11. Executive summary: No regressions noticed so far. == aarch64 == Pine64 - boots now, but no built-in network (USB Ethernet works) Raspberry Pi 3 B - boots OK == armv7hl == (Tested using a home branch.) Beagle Bone Black - boots OK Cubietruck - boots OK Jetson TK1 - boots OK Raspberry Pi 2 B - boots OK == armv6hl == (Tested using a home branch - finished building today.) Raspberry Pi Zero - boots OK -rc6 should start building for armv7hl and armv6hl tomorrow. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Update: Since Friday's second revision of 4.11.rc6 serdev now works. Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel. Am 11.04.2017 um 01:42 schrieb Andreas Färber:
== aarch64 ==
Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut)
Pine64 - boots now, but no built-in network (USB Ethernet works)
Raspberry Pi 3 B - boots OK
Vega S95 Telos - boots OK (cf. Odroid-C2)
== armv7hl == [...] Beagle Bone Black - boots OK
Cubietruck - boots OK
Jetson TK1 - boots OK
NanoPi NEO - boots OK (still no built-in network)
Raspberry Pi 2 B - boots OK
UDOO Neo - still hanging No successful armv6hl -rc6 builds yet. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 15/04/17 09:48, Andreas Färber wrote:
Hi,
Update: Since Friday's second revision of 4.11.rc6 serdev now works.
Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel.
Am 11.04.2017 um 01:42 schrieb Andreas Färber:
== aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut)
Pine64 - boots now, but no built-in network (USB Ethernet works)
Raspberry Pi 3 B - boots OK Vega S95 Telos - boots OK (cf. Odroid-C2)
== armv7hl == [...] Beagle Bone Black - boots OK
Cubietruck - boots OK
Jetson TK1 - boots OK NanoPi NEO - boots OK (still no built-in network)
Raspberry Pi 2 B - boots OK UDOO Neo - still hanging
No successful armv6hl -rc6 builds yet.
Regards, Andreas
Hi Andreas, Which image boots on the ODROID-C2? I much prefer openSUSE to Ubuntu. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Sid, Am 18.04.2017 um 21:35 schrieb Sid Boyce:
On 15/04/17 09:48, Andreas Färber wrote:
Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel.
Am 11.04.2017 um 01:42 schrieb Andreas Färber:
== aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2?
Short answer: None, I have not created a JeOS image yet. Just today was U-Boot v2017.05-rc2 packaged, and it'll take a while for it to hit Factory. (https://build.opensuse.org/request/show/487710 is still pending for the previous v2017.03...) -rc2 still does not include all patches for a convenient boot from SD - we could queue some in our package of course. Binary-only ARM Trusted Firmware blobs are needed for booting, that are unlikely to ever reach Factory. So they would need to live in a Contrib. Next problem was that Hardkernel uses a binary-only x86 Amlogic tool for packing the ATF and U-Boot binaries into a bootable form. My solution for OBS/aarch64 was to piece together an Open Source tool: https://github.com/afaerber/meson-tools Currently that still requires the fip tool from downstream Hardkernel U-Boot (with its alignment magic), which didn't build with gcc5+. Cf. https://en.opensuse.org/HCL:OdroidC2 So... would it help to create a JeOS image without the bootloader? You could then dd the bootloader onto the SD card in a second step. The Factory 4.10 kernel booted okay, so no dependency on Kernel:HEAD. I've create a Contrib:OdroidC2, but it's still empty: https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:OdroidC2 Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 18/04/17 22:25, Andreas Färber wrote:
Hi Sid,
Am 18.04.2017 um 21:35 schrieb Sid Boyce:
On 15/04/17 09:48, Andreas Färber wrote:
Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel.
Am 11.04.2017 um 01:42 schrieb Andreas Färber:
== aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2? Short answer: None, I have not created a JeOS image yet.
Just today was U-Boot v2017.05-rc2 packaged, and it'll take a while for it to hit Factory. (https://build.opensuse.org/request/show/487710 is still pending for the previous v2017.03...) -rc2 still does not include all patches for a convenient boot from SD - we could queue some in our package of course.
Binary-only ARM Trusted Firmware blobs are needed for booting, that are unlikely to ever reach Factory. So they would need to live in a Contrib.
Next problem was that Hardkernel uses a binary-only x86 Amlogic tool for packing the ATF and U-Boot binaries into a bootable form. My solution for OBS/aarch64 was to piece together an Open Source tool: https://github.com/afaerber/meson-tools Currently that still requires the fip tool from downstream Hardkernel U-Boot (with its alignment magic), which didn't build with gcc5+.
Cf. https://en.opensuse.org/HCL:OdroidC2
So... would it help to create a JeOS image without the bootloader? You could then dd the bootloader onto the SD card in a second step.
The Factory 4.10 kernel booted okay, so no dependency on Kernel:HEAD.
I've create a Contrib:OdroidC2, but it's still empty: https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:OdroidC2
Regards, Andreas
Thanks Andreas, Looks like much work is left to do. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 19.04.2017 um 00:43 schrieb Sid Boyce:
On 18/04/17 22:25, Andreas Färber wrote:
Am 18.04.2017 um 21:35 schrieb Sid Boyce:
On 15/04/17 09:48, Andreas Färber wrote:
Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel.
Am 11.04.2017 um 01:42 schrieb Andreas Färber:
== aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2? Short answer: None, I have not created a JeOS image yet.
Just today was U-Boot v2017.05-rc2 packaged, and it'll take a while for it to hit Factory. (https://build.opensuse.org/request/show/487710 is still pending for the previous v2017.03...) -rc2 still does not include all patches for a convenient boot from SD - we could queue some in our package of course.
Binary-only ARM Trusted Firmware blobs are needed for booting, that are unlikely to ever reach Factory. So they would need to live in a Contrib.
Next problem was that Hardkernel uses a binary-only x86 Amlogic tool for packing the ATF and U-Boot binaries into a bootable form. My solution for OBS/aarch64 was to piece together an Open Source tool: https://github.com/afaerber/meson-tools Currently that still requires the fip tool from downstream Hardkernel U-Boot (with its alignment magic), which didn't build with gcc5+.
Cf. https://en.opensuse.org/HCL:OdroidC2
So... would it help to create a JeOS image without the bootloader? You could then dd the bootloader onto the SD card in a second step.
The Factory 4.10 kernel booted okay, so no dependency on Kernel:HEAD.
I've create a Contrib:OdroidC2, but it's still empty: https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:OdroidC2
Thanks Andreas,
Looks like much work is left to do.
My meson-tools are packaged in Contrib:OdroidC2 now, and I've applied a patch to u-boot-odroid-c2 in Base:System:Staging. The Wiki page above has been updated with how to build the bootloader from the Hardkernel blobs and our U-Boot package with my tool. Cheers, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 18.04.2017 um 23:25 schrieb Andreas Färber:
Hi Sid,
Am 18.04.2017 um 21:35 schrieb Sid Boyce:
On 15/04/17 09:48, Andreas Färber wrote:
Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel.
Am 11.04.2017 um 01:42 schrieb Andreas Färber:
== aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2?
Short answer: None, I have not created a JeOS image yet.
Just today was U-Boot v2017.05-rc2 packaged, and it'll take a while for it to hit Factory. [...] Binary-only ARM Trusted Firmware blobs are needed for booting, that are unlikely to ever reach Factory. So they would need to live in a Contrib.
Packaged as odroidc2-firmware in Contrib:OdroidC2.
Next problem was that Hardkernel uses a binary-only x86 Amlogic tool for packing the ATF and U-Boot binaries into a bootable form. My solution for OBS/aarch64 was to piece together an Open Source tool: https://github.com/afaerber/meson-tools Currently that still requires the fip tool from downstream Hardkernel U-Boot (with its alignment magic), which didn't build with gcc5+.
Found a workaround: fip_create actually builds fine without U-Boot. Packaged as odroidc2-firmware-tools for Leap 42.2 and Tumbleweed. odroidc2-firmware now builds u-boot.odroidc2 - boots OK when written to SD card as documented in the Wiki below. :) Thanks to everyone who supported the development of meson-tools! In particular a hint on "sha2" functions being used, which lead me to discover the right SHA256 check-sum algorithm, was invaluable.
Cf. https://en.opensuse.org/HCL:OdroidC2
So... would it help to create a JeOS image without the bootloader?
Only this final part is still missing.
You could then dd the bootloader onto the SD card in a second step.
The Factory 4.10 kernel booted okay, so no dependency on Kernel:HEAD.
I've create a Contrib:OdroidC2, but it's still empty: https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:OdroidC2
Regards, Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 20.04.2017 um 20:57 schrieb Andreas Färber:
Am 18.04.2017 um 23:25 schrieb Andreas Färber:
Hi Sid,
Am 18.04.2017 um 21:35 schrieb Sid Boyce:
On 15/04/17 09:48, Andreas Färber wrote:
Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel.
Am 11.04.2017 um 01:42 schrieb Andreas Färber:
== aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2?
JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Enjoy, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 21/04/17 09:13, Andreas Färber wrote:
Am 20.04.2017 um 20:57 schrieb Andreas Färber:
Am 18.04.2017 um 23:25 schrieb Andreas Färber:
Hi Sid,
Am 18.04.2017 um 21:35 schrieb Sid Boyce:
On 15/04/17 09:48, Andreas Färber wrote:
Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel.
Am 11.04.2017 um 01:42 schrieb Andreas Färber:
== aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2? JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2.
Enjoy, Andreas
Hi Andreas, Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. fsck'd both partitions to make sure they are clean. Results the same. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Sid, Am 21.04.2017 um 16:13 schrieb Sid Boyce:
On 21/04/17 09:13, Andreas Färber wrote:
JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2.
Hi Andreas, Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights.
It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT patches yet. Booting does not mean full-featured! Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up. On my home branch, before submitting JeOS, I had verified that also second boot works, thanks to the dracut config added. Regards, Andreas GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 312955 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 set vcck to 1100 mv set vddee to 1050 mv CPU clk: 1536MHz DDR channel setting: DDR0 Rank0+1 same DDR0: 2048MB(auto) @ 912MHz(2T)-13 DataBus test pass! AddrBus test pass! Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0 Sending bl30........................................OK. Run bl30... Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000018c0 Wait bl30...Done Sending bl301.......OK. Run bl301... 0, des: 0x10100000, size: 0x00011130 --- UART initialized after reboot --- [Reset cause: unknown] [Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04] bl30: check_permit, count is 1 bl30: check_permit: ok! chipid: ef be ad de d f0 ad ba ef bLoad bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x00055b50 e ad de not ES chip [0.427617 Inits done] secure task start! high task start! low task start! NOTICE: BL3-1: v1.0(debug):4d2e34d NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address = 0x1000000 INFO: BL3-1: Next image spsr = 0x3c9 U-Boot 2017.05-rc2 (Apr 21 2017 - 03:45:10 +0000) odroid-c2 DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 Using default environment In: serial@4c0 Out: serial@4c0 Err: serial@4c0 Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 => boot switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... 19109 bytes read in 28 ms (666 KiB/s) Found EFI removable media binary efi/boot/bootaa64.efi reading efi/boot/bootaa64.efi 731648 bytes read in 37 ms (18.9 MiB/s) ## Starting EFI application at 01080000 ... Scanning disk mmc@72000.blk... Card did not respond to voltage select! mmc_init: -95, time 10 Found 1 disks Welcome to GRUB! error: terminal `gfxterm' isn't found. error: no suitable video mode found. error: can't find command `terminal'. GNU GRUB version 2.02~rc2 ┌────────────────────────────────────────────────────────────────────────────┐ │ openSUSE [ VMX ] │ │*Failsafe -- openSUSE [ VMX ] │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └────────────────────────────────────────────────────────────────────────────┘ Use the ▲ and ▼ keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 21/04/17 15:40, Andreas F�rber wrote:
Hi Sid,
On 21/04/17 09:13, Andreas Färber wrote:
JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2.
Hi Andreas, Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT
Am 21.04.2017 um 16:13 schrieb Sid Boyce: patches yet. Booting does not mean full-featured!
Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up.
On my home branch, before submitting JeOS, I had verified that also second boot works, thanks to the dracut config added.
Regards, Andreas
GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 312955 no sdio debug board detected
BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton
Board ID = 8 set vcck to 1100 mv set vddee to 1050 mv CPU clk: 1536MHz DDR channel setting: DDR0 Rank0+1 same DDR0: 2048MB(auto) @ 912MHz(2T)-13 DataBus test pass! AddrBus test pass! Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0 Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0 Sending bl30........................................OK. Run bl30... Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000018c0 Wait bl30...Done Sending bl301.......OK. Run bl301... 0, des: 0x10100000, size: 0x00011130
--- UART initialized after reboot --- [Reset cause: unknown] [Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04] bl30: check_permit, count is 1 bl30: check_permit: ok! chipid: ef be ad de d f0 ad ba ef bLoad bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x00055b50 e ad de not ES chip [0.427617 Inits done] secure task start! high task start! low task start! NOTICE: BL3-1: v1.0(debug):4d2e34d NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address = 0x1000000 INFO: BL3-1: Next image spsr = 0x3c9
U-Boot 2017.05-rc2 (Apr 21 2017 - 03:45:10 +0000) odroid-c2
DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 Using default environment
In: serial@4c0 Out: serial@4c0 Err: serial@4c0 Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 => boot switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... 19109 bytes read in 28 ms (666 KiB/s) Found EFI removable media binary efi/boot/bootaa64.efi reading efi/boot/bootaa64.efi 731648 bytes read in 37 ms (18.9 MiB/s) ## Starting EFI application at 01080000 ... Scanning disk mmc@72000.blk... Card did not respond to voltage select! mmc_init: -95, time 10 Found 1 disks Welcome to GRUB!
error: terminal `gfxterm' isn't found. error: no suitable video mode found. error: can't find command `terminal'.
GNU GRUB version 2.02~rc2
┌────────────────────────────────────────────────────────────────────────────┐ │ openSUSE [ VMX ] │ │*Failsafe -- openSUSE [ VMX ] │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └────────────────────────────────────────────────────────────────────────────┘
Use the ▲ and ▼ keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line.
Hi Andreas, I have both the serial console on /dev/ttyUSB0 and HDMI screens connected. The blue LED never flashes on and no message appears on the serial connection. I am using one of the recommended Toshiba SD cards - 64 GB. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Am 21.04.2017 um 17:00 schrieb Sid Boyce:
On 21/04/17 15:40, Andreas Färber wrote:
JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz
On 21/04/17 09:13, Andreas Färber wrote: per instructions, does not boot. Only the red LED lights. It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT
Am 21.04.2017 um 16:13 schrieb Sid Boyce: patches yet. Booting does not mean full-featured!
Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up. [...] I have both the serial console on /dev/ttyUSB0 and HDMI screens connected.
Having HDMI connected didn't hurt here.
The blue LED never flashes on
For some reason the ledtrig-heartbeat module does not get loaded automatically. So the blue LED is unrelated to booting.
and no message appears on the serial connection.
Baudrate 115200? Working for your Ubuntu image?
I am using one of the recommended Toshiba SD cards - 64 GB.
32 GB SanDisk Ultra microSHDC Class 10 UHS-I here. Where did you read about recommended cards? http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438&tab_idx=2 "The ODROID-C2 can utilize the newer UHS-1 SD model, which is about 2 times faster than a normal class 10 card. Note that there are some cards which needs additional booting delay time around 30 seconds. According to our test, most Sandisk Micro-SD cards don't cause the booting delay. We will make a compatibility list soon." What they're selling is SanDisk 8 GB and 16 GB: http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145636129743 Note that the initial serial output comes from BL1, so is independent of any mainline U-Boot code specific to us. I doubt that meson-tools are at fault if the same image boots for me. So rather puzzling... Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 21/04/17 16:57, Andreas Färber wrote:
Hi,
Am 21.04.2017 um 17:00 schrieb Sid Boyce:
On 21/04/17 15:40, Andreas Färber wrote:
JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz
On 21/04/17 09:13, Andreas Färber wrote: per instructions, does not boot. Only the red LED lights. It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT
Am 21.04.2017 um 16:13 schrieb Sid Boyce: patches yet. Booting does not mean full-featured!
Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up. [...] I have both the serial console on /dev/ttyUSB0 and HDMI screens connected. Having HDMI connected didn't hurt here.
The blue LED never flashes on For some reason the ledtrig-heartbeat module does not get loaded automatically. So the blue LED is unrelated to booting.
and no message appears on the serial connection. Baudrate 115200? Working for your Ubuntu image?
I am using one of the recommended Toshiba SD cards - 64 GB. 32 GB SanDisk Ultra microSHDC Class 10 UHS-I here.
Where did you read about recommended cards?
http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438&tab_idx=2
"The ODROID-C2 can utilize the newer UHS-1 SD model, which is about 2 times faster than a normal class 10 card. Note that there are some cards which needs additional booting delay time around 30 seconds. According to our test, most Sandisk Micro-SD cards don't cause the booting delay. We will make a compatibility list soon."
What they're selling is SanDisk 8 GB and 16 GB:
http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145636129743
Note that the initial serial output comes from BL1, so is independent of any mainline U-Boot code specific to us. I doubt that meson-tools are at fault if the same image boots for me. So rather puzzling...
Regards, Andreas
http://magazine.odroid.com/wp-content/uploads/odroid-c2-user-manual.pdf - Page 24 Fully compatible microSD cards. I have left it powered up for around 2 hours, it still doesn't show any messages on the serial console -- 115200-8-N1. microSD card compatibility can be a real problem, I have 3 dead ones that is not sensed. I have a Sandisk Ultra XC-1 I shall try. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 22/04/17 00:08, Sid Boyce wrote:
On 21/04/17 16:57, Andreas Färber wrote:
Hi,
Am 21.04.2017 um 17:00 schrieb Sid Boyce:
On 21/04/17 15:40, Andreas Färber wrote:
On 21/04/17 09:13, Andreas Färber wrote:
JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz
per instructions, does not boot. Only the red LED lights. It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT
Am 21.04.2017 um 16:13 schrieb Sid Boyce: patches yet. Booting does not mean full-featured!
Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up. [...] I have both the serial console on /dev/ttyUSB0 and HDMI screens connected. Having HDMI connected didn't hurt here.
The blue LED never flashes on For some reason the ledtrig-heartbeat module does not get loaded automatically. So the blue LED is unrelated to booting.
and no message appears on the serial connection. Baudrate 115200? Working for your Ubuntu image?
I am using one of the recommended Toshiba SD cards - 64 GB. 32 GB SanDisk Ultra microSHDC Class 10 UHS-I here.
Where did you read about recommended cards?
http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438&tab_idx=2
"The ODROID-C2 can utilize the newer UHS-1 SD model, which is about 2 times faster than a normal class 10 card. Note that there are some cards which needs additional booting delay time around 30 seconds. According to our test, most Sandisk Micro-SD cards don't cause the booting delay. We will make a compatibility list soon."
What they're selling is SanDisk 8 GB and 16 GB:
http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145636129743
Note that the initial serial output comes from BL1, so is independent of any mainline U-Boot code specific to us. I doubt that meson-tools are at fault if the same image boots for me. So rather puzzling...
Regards, Andreas
http://magazine.odroid.com/wp-content/uploads/odroid-c2-user-manual.pdf - Page 24 Fully compatible microSD cards.
I have left it powered up for around 2 hours, it still doesn't show any messages on the serial console -- 115200-8-N1.
microSD card compatibility can be a real problem, I have 3 dead ones that is not sensed.
I have a Sandisk Ultra XC-1 I shall try.
Regards
Sid.
Same result with the Sandisk Ultra. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 22/04/17 00:08, Sid Boyce wrote:
On 21/04/17 16:57, Andreas Färber wrote:
Hi,
Am 21.04.2017 um 17:00 schrieb Sid Boyce:
On 21/04/17 15:40, Andreas Färber wrote:
On 21/04/17 09:13, Andreas Färber wrote:
JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz
per instructions, does not boot. Only the red LED lights. It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT
Am 21.04.2017 um 16:13 schrieb Sid Boyce: patches yet. Booting does not mean full-featured!
Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up. [...] I have both the serial console on /dev/ttyUSB0 and HDMI screens connected. Having HDMI connected didn't hurt here.
The blue LED never flashes on For some reason the ledtrig-heartbeat module does not get loaded automatically. So the blue LED is unrelated to booting.
and no message appears on the serial connection. Baudrate 115200? Working for your Ubuntu image?
I am using one of the recommended Toshiba SD cards - 64 GB. 32 GB SanDisk Ultra microSHDC Class 10 UHS-I here.
Where did you read about recommended cards?
http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438&tab_idx=2
"The ODROID-C2 can utilize the newer UHS-1 SD model, which is about 2 times faster than a normal class 10 card. Note that there are some cards which needs additional booting delay time around 30 seconds. According to our test, most Sandisk Micro-SD cards don't cause the booting delay. We will make a compatibility list soon."
What they're selling is SanDisk 8 GB and 16 GB:
http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145636129743
Note that the initial serial output comes from BL1, so is independent of any mainline U-Boot code specific to us. I doubt that meson-tools are at fault if the same image boots for me. So rather puzzling...
Regards, Andreas
http://magazine.odroid.com/wp-content/uploads/odroid-c2-user-manual.pdf - Page 24 Fully compatible microSD cards.
I have left it powered up for around 2 hours, it still doesn't show any messages on the serial console -- 115200-8-N1.
microSD card compatibility can be a real problem, I have 3 dead ones that is not sensed.
I have a Sandisk Ultra XC-1 I shall try.
Regards
Sid.
Hi Andreas, Looks like my SD card interface is broken as it does not boot with any distro. I normally run Ubuntu from a eMMC. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Sid, Am 27.04.2017 um 17:20 schrieb Sid Boyce:
Looks like my SD card interface is broken as it does not boot with any distro.
I normally run Ubuntu from a eMMC.
Did you detach the eMMC for SD testing? I don't have an eMMC module. If you're feeling like experimenting, you could back up your Ubuntu and try dd'ing the JeOS to eMMC. I'm not aware of any special blobs being needed for eMMC, so it might work... Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 30/04/17 13:03, Andreas Färber wrote:
Hi Sid,
Am 27.04.2017 um 17:20 schrieb Sid Boyce:
Looks like my SD card interface is broken as it does not boot with any distro.
I normally run Ubuntu from a eMMC. Did you detach the eMMC for SD testing?
I don't have an eMMC module. If you're feeling like experimenting, you could back up your Ubuntu and try dd'ing the JeOS to eMMC. I'm not aware of any special blobs being needed for eMMC, so it might work...
Regards, Andreas
Hi Andreas, Yes I did. I always remove the eMMC when testing SD cards. When you said you had no problems and no one else reported problems I thought I would try to boot other OS's from SD cards, all failed the same way. It can only be the SD card slot at fault. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Sid, On Fri, 21 Apr 2017, Sid Boyce wrote:
On 21/04/17 09:13, Andreas Färber wrote:
Am 20.04.2017 um 20:57 schrieb Andreas Färber:
Am 18.04.2017 um 23:25 schrieb Andreas Färber:
Am 18.04.2017 um 21:35 schrieb Sid Boyce:
On 15/04/17 09:48, Andreas Färber wrote:
Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel.
Am 11.04.2017 um 01:42 schrieb Andreas Färber: > == aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2? JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2.
Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. fsck'd both partitions to make sure they are clean. Results the same.
I had to wait several minutes before I could log in via ssh. No LED flashing, just the red one constantly on. Using a SanDisk Extreme 32GB (considerably faster than my other microSDs, but also more expensive). Nice work, btw. Thank you, Andreas. --Daniel.
On 22/04/17 12:32, Daniel Bischof wrote:
Sid,
On Fri, 21 Apr 2017, Sid Boyce wrote:
On 21/04/17 09:13, Andreas Färber wrote:
Am 20.04.2017 um 20:57 schrieb Andreas Färber:
Am 18.04.2017 um 23:25 schrieb Andreas Färber:
Am 18.04.2017 um 21:35 schrieb Sid Boyce:
On 15/04/17 09:48, Andreas Färber wrote: > Amlogic S905 MMC support has just landed in U-Boot last night, > allowing to finally migrate my two S905 devices over to our > openSUSE kernel. > > Am 11.04.2017 um 01:42 schrieb Andreas Färber: >> == aarch64 == > Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2? JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2.
Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. fsck'd both partitions to make sure they are clean. Results the same.
I had to wait several minutes before I could log in via ssh. No LED flashing, just the red one constantly on. Using a SanDisk Extreme 32GB (considerably faster than my other microSDs, but also more expensive).
Nice work, btw. Thank you, Andreas.
--Daniel. I have had it powered up ever since I last posted, "nmap -sT 192.168.10.0/24" does not see it. Regards Sid.
-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Daniel, Am 22.04.2017 um 13:32 schrieb Daniel Bischof:
On Fri, 21 Apr 2017, Sid Boyce wrote:
On 21/04/17 09:13, Andreas Färber wrote:
JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2.
Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. fsck'd both partitions to make sure they are clean. Results the same.
I had to wait several minutes before I could log in via ssh.
Glad it works for you.
No LED flashing, just the red one constantly on. [...]
You can run `modprobe ledtrig-heartbeat` to get the LED flashing. leds_gpio is not part of the initrd but gets loaded just fine; adding ledtrig-heartbeat to dracut's add_drivers did not help, nor did adding it to force_drivers load it (I did verify with lsinitrd that it's there after local config changes and subsequent `mkinitrd`). Nothing in dmesg. If you find any clues, let us know - the LED is no priority to me. ;)
Nice work, btw. Thank you, Andreas.
You're welcome. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hey, Using unmerged patches, I built a U-Boot for Orange Pi PC 2 and bootstrapped it from our Pine64 image (overwriting the bootloader with mine, and repeating that after first boot). Am 15.04.2017 um 10:48 schrieb Andreas Färber:
Am 11.04.2017 um 01:42 schrieb Andreas Färber:
== aarch64 ==
Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut)
Orange Pi PC 2 - stuck during earlycon * I enabled missing SUN8I_H3_CCU, should be in 4.11.rc7 later today. * We're still missing a pinctrl driver in 4.11 (PINCTRL_SUN50I_H5 in linux-next; http://linux-sunxi.org/H5#Mainline), which uart0 wants. * There's no sun50i-h5-orangepi-pc2.dts in 4.11, and linux-next branch isn't building dtb-allwinner yet (affects Pine64 and BananaPi M64, too). https://bugzilla.opensuse.org/show_bug.cgi?id=1034826
Pine64 - boots now, but no built-in network (USB Ethernet works)
Raspberry Pi 3 B - boots OK
Vega S95 Telos - boots OK (cf. Odroid-C2) [...]
-rc6 built for armv6hl by now. Raspberry Pi Zero - boots OK Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 19.04.2017 um 08:45 schrieb Andreas Färber:
Am 15.04.2017 um 10:48 schrieb Andreas Färber:
Am 11.04.2017 um 01:42 schrieb Andreas Färber:
== aarch64 ==
Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut)
Orange Pi PC 2 - stuck during earlycon * I enabled missing SUN8I_H3_CCU, should be in 4.11.rc7 later today. * We're still missing a pinctrl driver in 4.11 (PINCTRL_SUN50I_H5 in linux-next; http://linux-sunxi.org/H5#Mainline), which uart0 wants.
Still does not boot with v4.11-rc7, neither with U-Boot's built-in dtb nor with Contrib:Pine64's dtb-allwinner. Loading Linux 4.11.0-rc7-1.g6e80a14-default ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: ERROR: Could not determine UEFI Secure Boot status. EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.11.0-rc7-1.g6e80a14-default (geeko@buildhost) (gcc version 6.3.1 20170202 [gcc-6-branch revision 245119] (SUSE Linux) ) #1 SMP Wed Apr 19 00:49:59 UTC 2017 (6e80a14) [ 0.000000] Boot CPU: AArch64 Processor [410fd034] [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: EFI v2.05 by Das U-boot [ 0.000000] efi: SMBIOS=0x7af0a000 [ 0.000000] earlycon: uart0 at MMIO32 0x0000000001c28000 (options '115200n8') [ 0.000000] bootconsole [uart0] enabled [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000007fffffff] [ 0.000000] NUMA: Adding memblock [0x40000000 - 0x48003fff] on node 0 [ 0.000000] NUMA: Adding memblock [0x48005000 - 0x7af09fff] on node 0 [ 0.000000] NUMA: Adding memblock [0x7af0a000 - 0x7af0afff] on node 0 [ 0.000000] NUMA: Adding memblock [0x7af0b000 - 0x7ffa9fff] on node 0 [ 0.000000] NUMA: Adding memblock [0x7ffaa000 - 0x7ffaafff] on node 0 [ 0.000000] NUMA: Adding memblock [0x7ffab000 - 0x7fffffff] on node 0 [ 0.000000] NUMA: Initmem setup node 0 [mem 0x40000000-0x7fffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x7ffe2100-0x7ffe3bff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000040000000-0x000000007fffffff] [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x0000000048003fff] [ 0.000000] node 0: [mem 0x0000000048005000-0x000000007af09fff] [ 0.000000] node 0: [mem 0x000000007af0a000-0x000000007af0afff] [ 0.000000] node 0: [mem 0x000000007af0b000-0x000000007ffa9fff] [ 0.000000] node 0: [mem 0x000000007ffaa000-0x000000007ffaafff] [ 0.000000] node 0: [mem 0x000000007ffab000-0x000000007fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000007fffffff] [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv0.2 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] percpu: Embedded 24 pages/cpu @ffff80003ff4a000 s60696 r8192 d29416 u98304 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: enabling workaround for ARM erratum 845719 [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 258047 [ 0.000000] Policy zone: DMA [ 0.000000] Kernel command line: BOOT_IMAGE=/Image-4.11.0-rc7-1.g6e80a14-default root=UUID=28e561f9-2467-4ef3-ba34-5b6ac004ff2a earlycon console=ttyS0,115200n8 [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Memory: 1002744K/1048572K available (8252K kernel code, 1354K rwdata, 5816K rodata, 4480K init, 1010K bss, 45828K reserved, 0K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] modules : 0xffff000000000000 - 0xffff000008000000 ( 128 MB) [ 0.000000] vmalloc : 0xffff000008000000 - 0xffff7dffbfff0000 (129022 GB) [ 0.000000] .text : 0xffff000008080000 - 0xffff000008890000 ( 8256 KB) [ 0.000000] .rodata : 0xffff000008890000 - 0xffff000008e50000 ( 5888 KB) [ 0.000000] .init : 0xffff000008e50000 - 0xffff0000092b0000 ( 4480 KB) [ 0.000000] .data : 0xffff0000092b0000 - 0xffff000009402a00 ( 1355 KB) [ 0.000000] .bss : 0xffff000009402a00 - 0xffff0000094ff504 ( 1011 KB) [ 0.000000] fixed : 0xffff7dfffe7fd000 - 0xffff7dfffec00000 ( 4108 KB) [ 0.000000] PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000 ( 16 MB) [ 0.000000] vmemmap : 0xffff7e0000000000 - 0xffff800000000000 ( 2048 GB maximum) [ 0.000000] 0xffff7e0000000000 - 0xffff7e0001000000 ( 16 MB actual) [ 0.000000] memory : 0xffff800000000000 - 0xffff800040000000 ( 1024 MB) [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 64. [ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4 [ 0.000000] NR_IRQS:64 nr_irqs:64 0 [ 0.000000] arm_arch_timer: Architected cp15 timer(s) running at 24.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.000004] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.008440] Console: colour dummy device 80x25 [ 0.012932] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000) [ 0.023277] pid_max: default: 32768 minimum: 301 [ 0.028010] Security Framework initialized [ 0.032163] AppArmor: AppArmor initialized [ 0.036608] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 0.044642] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.051927] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes) [ 0.058620] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes) [ 0.066361] ftrace: allocating 29755 entries in 117 pages [ 0.117048] ASID allocator initialised with 65536 entries [ 0.123852] Remapping and enabling EFI services. [ 0.128525] EFI remap 0x000000007af0a000 => 000000002000a000 [ 0.134348] EFI remap 0x000000007ffaa000 => 000000002001a000 [ 0.140410] smp: Bringing up secondary CPUs ... [ 0.146158] Detected VIPT I-cache on CPU1 [ 0.146209] CPU1: Booted secondary processor [410fd034] [ 0.147029] Detected VIPT I-cache on CPU2 [ 0.147060] CPU2: Booted secondary processor [410fd034] [ 0.147846] Detected VIPT I-cache on CPU3 [ 0.147873] CPU3: Booted secondary processor [410fd034] [ 0.147925] smp: Brought up 1 node, 4 CPUs [ 0.179680] SMP: Total of 4 processors activated. [ 0.184375] CPU features: detected feature: 32-bit EL0 Support [ 0.190244] CPU: All CPU(s) started at EL2 [ 0.194349] alternatives: patching kernel code [ 0.199646] devtmpfs: initialized [ 0.205007] SMBIOS 3.0 present. [ 0.208155] DMI: sunxi sunxi/sunxi, BIOS 2017.05-rc2-00019-g00439be 04/18/2017 [ 0.215551] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.225404] futex hash table entries: 1024 (order: 5, 131072 bytes) [ 0.231932] pinctrl core: initialized pinctrl subsystem [ 0.237978] NET: Registered protocol family 16 [ 0.243330] cpuidle: using governor ladder [ 0.247501] cpuidle: using governor menu [ 0.251718] vdso: 2 pages (1 code @ ffff000008897000, 1 data @ ffff0000092b5000) [ 0.259108] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.266103] DMA: preallocated 256 KiB pool for atomic allocations [ 0.272308] Serial: AMBA PL011 UART driver [ 0.283762] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 0.290912] ACPI: Interpreter disabled. [ 0.295086] vgaarb: loaded [ 0.298019] SCSI subsystem initialized [ 0.302073] Registered efivars operations [ 0.306096] efivars: get_next_variable: status=8000000000000007 [ 0.312612] NetLabel: Initializing [ 0.316007] NetLabel: domain hash size = 128 [ 0.320363] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 0.326065] NetLabel: unlabeled traffic allowed by default [ 0.331845] clocksource: Switched to clocksource arch_sys_counter [ 0.386597] VFS: Disk quotas dquot_6.6.0 [ 0.390584] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.397817] AppArmor: AppArmor Filesystem Enabled [ 0.402663] pnp: PnP ACPI: disabled [ 0.412330] NET: Registered protocol family 2 [ 0.417133] TCP established hash table entries: 8192 (order: 4, 65536 bytes) [ 0.424274] TCP bind hash table entries: 8192 (order: 5, 131072 bytes) [ 0.430934] TCP: Hash tables configured (established 8192 bind 8192) [ 0.437397] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.443342] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.449858] NET: Registered protocol family 1 [ 0.454466] Unpacking initramfs... [ 3.076956] Freeing initrd memory: 7852K [ 3.081296] kvm [1]: 8-bit VMID [ 3.084464] kvm [1]: IDMAP page: 4087d000 [ 3.088465] kvm [1]: HYP VA range: 800000000000:ffffffffffff [ 3.095118] kvm [1]: Hyp mode initialized successfully [ 3.100280] kvm [1]: vgic-v2@1c84000 [ 3.103973] kvm [1]: vgic interrupt IRQ1 [ 3.107895] kvm [1]: virtual timer IRQ4 [ 3.112842] audit: initializing netlink subsys (disabled) [ 3.118390] audit: type=2000 audit(3.040:1): state=initialized audit_enabled=0 res=1 [ 3.118788] workingset: timestamp_bits=44 max_order=18 bucket_order=0 [ 3.132611] zbud: loaded [ 3.139101] Key type asymmetric registered [ 3.143221] Asymmetric key parser 'x509' registered [ 3.148166] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250) [ 3.155654] io scheduler noop registered [ 3.159568] io scheduler deadline registered [ 3.163891] io scheduler cfq registered (default) [ 3.171438] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 3.178953] dw-apb-uart 1c28000.serial: could not find pctldev for node /soc/pinctrl@01c20800/uart0@0, deferring probe [ 3.189809] Serial: AMBA driver [ 3.193149] msm_serial: driver initialized [ 3.197565] cacheinfo: Unable to detect cache hierarchy for CPU 0 [ 3.204086] libphy: Fixed MDIO Bus: probed [ 3.208432] mousedev: PS/2 mouse device common for all mice [ 3.214973] ledtrig-cpu: registered to indicate activity on CPUs [ 3.221063] EFI Variables Facility v0.08 2004-May-17 [ 3.226046] efivars: get_next_variable: status=8000000000000007 [ 3.232009] hidraw: raw HID events driver (C) Jiri Kosina [ 3.238067] NET: Registered protocol family 10 [ 3.258602] Segment Routing with IPv6 [ 3.262915] registered taskstats version 1 [ 3.267086] zswap: loaded using pool lzo/zbud [ 3.324962] Key type big_key registered [ 3.335945] Key type encrypted registered [ 3.339962] AppArmor: AppArmor sha1 policy hashing enabled [ 3.349818] dw-apb-uart 1c28000.serial: could not find pctldev for node /soc/pinctrl@01c20800/uart0@0, deferring probe [ 3.360685] hctosys: unable to open rtc device (rtc0)
* There's no sun50i-h5-orangepi-pc2.dts in 4.11, and linux-next branch isn't building dtb-allwinner yet (affects Pine64 and BananaPi M64, too). https://bugzilla.opensuse.org/show_bug.cgi?id=1034826
Pine64 - boots now, but no built-in network (USB Ethernet works)
Raspberry Pi 3 B - boots OK
Vega S95 Telos - boots OK (cf. Odroid-C2) [...]
No known problems elsewhere so far. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Andreas Färber -
Daniel Bischof -
Sid Boyce