Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can confirm, that for legacy, both the base and xfce root images build okay.
However for next, the kernel compilation fails:
Code:
CC arch/arm64/kernel/asm-offsets.s
In file included from ./include/linux/ktime.h:239,
from ./include/linux/timer.h:6,
from ./include/linux/workqueue.h:9,
from ./include/linux/mm_types.h:16,
from ./include/linux/mmzone.h:21,
from ./include/linux/gfp.h:6,
from ./include/linux/xarray.h:14,
from ./include/linux/radix-tree.h:18,
from ./include/linux/idr.h:15,
from ./include/linux/kernfs.h:13,
from ./include/linux/sysfs.h:16,
from ./include/linux/kobject.h:20,
from ./include/linux/of.h:17,
from ./include/linux/irqdomain.h:35,
from ./include/linux/acpi.h:13,
from ./include/acpi/apei.h:9,
from ./include/acpi/ghes.h:5,
from ./include/linux/arm_sdei.h:8,
from arch/arm64/kernel/asm-offsets.c:10:
./include/linux/timekeeping32.h: In function 'get_monotonic_boottime':
./include/linux/timekeeping32.h:16:2: error: dereferencing pointer to incomplete type 'struct timespec'
16 | *ts = ktime_to_timespec(ktime_get_boottime());
| ^~~
./include/linux/timekeeping32.h:16:8: error: implicit declaration of function 'ktime_to_timespec'; did you mean 'ktime_to_timespec64'? [-Werror=implicit-function-declaration]
16 | *ts = ktime_to_timespec(ktime_get_boottime());
| ^~~~~~~~~~~~~~~~~
| ktime_to_timespec64
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:101: arch/arm64/kernel/asm-offsets.s] Error 1
make: *** [Makefile:1113: prepare0] Error 2
|err | details /home/user/slackbuild/slackware_arm_build_kit/build/source/build.log
If all goes well, I will be able to test my legacy and next images tomorrow with a serial cable.
So after all, it seems that it is trying to boot from the on-board eMMC flash...
I found these messages suspicious:
Code:
Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
...
do_boot_rockchip: Could not find mmcsda2 part
Checking for mmc dev 1...
RKPARM: Invalid parameter part table
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1 for bootable partitions...
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Checking for nvme dev 0...
Isn't the rootfs formatted as ext4 by default? Isn't u-boot expecting ext2?
As far as I understand it expects an ext2 formatted bootable partition with extlinux installed on it, and it should also hold the kernel and the dtb file. At least based on this:
Code:
Device 0: unknown device
Checking for mmc dev 0...
RKPARM: Invalid parameter part table
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0 for bootable partitions...
Scanning mmc 0:1 for extlinux or boot scripts...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
911 bytes read in 18 ms (48.8 KiB/s)
boot prev kernel
1: PINEBOOKPRO
2: PINEBOOKPRO-prev-kernel
Enter choice: 1: PINEBOOKPRO
Retrieving file: /Image
reading /Image
25421832 bytes read in 1311 ms (18.5 MiB/s)
append: console=ttyS2,1500000n8 rw root=/dev/mmcblk1p2 rootwait rootfstype=ext4 panic=10 init=/sbin/init coherent_pool=1M ethaddr=0e:0d:34:e7:5d:a5 eth1addr=0e:0d:34t
Retrieving file: /rk3399-pinebookpro.dtb
reading /rk3399-pinebookpro.dtb
100269 bytes read in 21 ms (4.6 MiB/s)
Isn't the rootfs formatted as ext4 by default? Isn't u-boot expecting ext2?
As far as I understand it expects an ext2 formatted bootable partition with extlinux installed on it, and it should also hold the kernel and the dtb file. At least based on this:
Turns out I was wrong with my assumptions above.
So, I removed the on-board eMMC from my Pinebook Pro, and hooked up the serial console adapter, and these are the outputs I got:
with slarm64-current-aarch64-base-rootfs-20200118-4.4.215-pinebook_pro-build-20200307.img:
Code:
U-Boot TPL 2020.01-rk3399 (Mar 07 2020 - 11:17:40)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.01-rk3399 (Mar 07 2020 - 11:17:40 +0100)
Trying to boot from MMC1
U-Boot 2020.01-rk3399 (Mar 07 2020 - 11:18:23 +0100)
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0
In: serial@ff1a0000
Out: serial@ff1a0000
Err: serial@ff1a0000
Model: Pine64 Pinebook Pro
## Error: Can't overwrite "serial#"
## Error inserting "serial#" variable, errno=1
rockchip_dnl_key_pressed: adc_channel_single_shot fail!
Net: No ethernet found.
Hit any key to stop autoboot: 1 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
1354 bytes read in 6 ms (219.7 KiB/s)
## Executing script at 00500000
U-boot loaded from SD
57 bytes read in 5 ms (10.7 KiB/s)
94423 bytes read in 22 ms (4.1 MiB/s)
20385800 bytes read in 2141 ms (9.1 MiB/s)
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
ERROR: reserving fdt memory region failed (addr=0 size=0)
Loading Device Tree to 00000000f5e9d000, end 00000000f5f1cfff ... OK
Starting kernel ...
[ 0.143203] Failed to find legacy iommu devices
[ 0.203021] vcc5v0_host: regulator get failed, ret=-517
[ 0.842093] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[ 0.842126] rockchip-pcie f8000000.pcie: deferred probe failed
[ 0.845045] rk-vcodec ff650000.vpu_service: could not find power_model node
[ 0.846671] rk-vcodec ff660000.rkvdec: could not find power_model node
[ 0.877135] rockchip-dwc3 usb0: failed to get drvdata dwc3
[ 0.882077] rockchip-dwc3 usb1: fail to get drvdata hcd
[ 1.109590] rk_tsadcv2_temp_to_code: Invalid conversion table: code=1023, temperature=2147483647
[ 1.114792] cpu cpu0: Failed to get pvtm
[ 1.116290] cpu cpu4: Failed to get pvtm
[ 1.208724] rockchip-dmc dmc: unable to get devfreq-event device : dfi
[ 1.238217] rockchip-vop ff900000.vop: missing rockchip,grf property
[ 1.239193] rockchip-vop ff8f0000.vop: missing rockchip,grf property
[ 1.240131] [drm:rockchip_dp_bind] *ERROR* failed to find panel
[ 1.240667] rockchip-drm display-subsystem: failed to bind ff970000.edp (ops 0xffffff8008bda778): -517
[ 1.464710] rockchip-dmc dmc: Failed to get leakage
[ 1.465972] rockchip-dmc dmc: Failed to get pvtm
[ 1.469234] rockchip-dmc dmc: failed to get vop pn to msch rl
[ 1.470430] rockchip-dmc dmc: could not find power_model node
[ 1.614776] rockchip-vop ff900000.vop: missing rockchip,grf property
[ 1.616214] rockchip-vop ff8f0000.vop: missing rockchip,grf property
[ 1.618004] rockchip-dp ff970000.edp: no DP phy configured
[ 1.642371] i2c i2c-9: of_i2c: modalias failure on /edp@ff970000/ports
[ 1.645410] i2c i2c-10: of_i2c: modalias failure on /dp@fec00000/ports
[ 3.122542] rockchip-saradc ff100000.saradc: failed to get voltage
[ 4.011058] mali ff9a0000.gpu: Failed to get pvtm
with slarm64-current-aarch64-base-rootfs-20200118-5.6.0-rc4-pinebook_pro-build-20200307.img:
Code:
U-Boot TPL 2020.01-rk3399 (Mar 07 2020 - 17:57:17)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.01-rk3399 (Mar 07 2020 - 17:57:17 +0100)
Trying to boot from MMC1
U-Boot 2020.01-rk3399 (Mar 07 2020 - 17:57:59 +0100)
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0
In: serial@ff1a0000
Out: serial@ff1a0000
Err: serial@ff1a0000
Model: Pine64 Pinebook Pro
## Error: Can't overwrite "serial#"
## Error inserting "serial#" variable, errno=1
rockchip_dnl_key_pressed: adc_channel_single_shot fail!
Net: No ethernet found.
Hit any key to stop autoboot: 1 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
1354 bytes read in 7 ms (188.5 KiB/s)
## Executing script at 00500000
U-boot loaded from SD
57 bytes read in 6 ms (8.8 KiB/s)
80505 bytes read in 16 ms (4.8 MiB/s)
21225984 bytes read in 2229 ms (9.1 MiB/s)
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Device Tree to 00000000f5ea1000, end 00000000f5f1cfff ... OK
Starting kernel ...
[ 0.670374] OF: graph: no port node found in /i2c@ff3d0000/fusb30x@22
[ 1.518023] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
U-Boot TPL 2020.01-rk3399 (Mar 10 2020 - 18:04:38)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.01-rk3399 (Mar 10 2020 - 18:04:38 +0200)
Trying to boot from MMC1
U-Boot 2020.01-rk3399 (Mar 10 2020 - 18:06:42 +0200)
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0
In: serial@ff1a0000
Out: serial@ff1a0000
Err: serial@ff1a0000
Model: Pine64 Pinebook Pro
## Error: Can't overwrite "serial#"
## Error inserting "serial#" variable, errno=1
rockchip_dnl_key_pressed: adc_channel_single_shot fail!
Net: No ethernet found.
Hit any key to stop autoboot: 1 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
1354 bytes read in 7 ms (188.5 KiB/s)
## Executing script at 00500000
U-boot loaded from SD
80 bytes read in 6 ms (12.7 KiB/s)
80505 bytes read in 16 ms (4.8 MiB/s)
21225984 bytes read in 2230 ms (9.1 MiB/s)
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Device Tree to 00000000f5ea1000, end 00000000f5f1cfff ... OK
Starting kernel ...
[ 0.661971] OF: graph: no port node found in /i2c@ff3d0000/fusb30x@22
[ 1.500292] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[ 2.780331] rockchip-dp ff970000.edp: no DP phy configured
=======================================================================
if you want to transfer the system to SD card to internal memory (eMMC or NAND),
follow setup
login: root
password: password
=======================================================================
Slackware GNU/Linux (ttyS2)
Kernel 5.6.0-rc4-MANJARO-ARM (aarch64)
pinebook-pro login: root
Password:
_ ___ ___
___ | | ___ ___ _____ | _|| | |
|_ -|| || .'|| _|| || . ||_ |
|___||_||__,||_| |_|_|_||___| |_|
_ _ _
___ |_| ___ ___ | |_ ___ ___ | |_ ___ ___ ___
| . || || || -_|| . || . || . || '_| | . || _|| . |
| _||_||_|_||___||___||___||___||_,_| | _||_| |___|
|_| |_|
Last login: Sat Jan 19 09:19:29 +0000 2013 on /dev/tty1.
You have mail.
Support: fail.pp.ua
Creating new account. Please provide a username (eg. your forename): ^Croot@pinebook-pro:~#
root@pinebook-pro:~# logout
After the first boot it resized the root partition to use the full capacity of the SD card, and rebooted without any user interaction. On the second boot it came up without any issues, and presented me with the login prompt.
Thanks for your help!
Last edited by wowbaggerHU; 03-11-2020 at 06:20 AM.
Sorry, but there is one thing I need to add. I tried building the images with the legacy and next kernels, but in case of legacy, the build failed with the following (build.log and then the script output):
Code:
Executing install script for libdrm-2.4.100-aarch64-1mara.txz.
Package libdrm-2.4.100-aarch64-1mara.txz installed.
Package libdrm-2.4.100-aarch64-1 upgraded with new package /home/user/slackbuild/slackware_arm_build_kit/build/pkg/rk3399/aarch64/x/libdrm-2.4.100-aarch64-1mara.txz.
|----------- delimiter ----------- "setting" "default settings xfce" -----------|
|info| download package x/libdrm-2.4.100-aarch64-1mara.txz
|info| install package l/mpp
|info| install package x/libgl-rk3399
|info| install package x/libdrm
|info| setting default settings xfce
sed: can't read /home/user/slackbuild/slackware_arm_build_kit/build/source/slarm64-current-aarch64-xfce-rootfs-20200118-4.4.215-pinebook_pro-build-20200311/etc/inittab: No such file or directory
root@slackbuild:/home/user/slackbuild/slackware_arm_build_kit#
Last edited by wowbaggerHU; 03-11-2020 at 02:21 PM.
Sorry, but there is one thing I need to add. I tried building the images with the legacy and next kernels, but in case of legacy, the build failed with the following (build.log and then the script output):
I once again have to correct myself, as the problem I described in my previous comment seems to have been a temporary one, as I wasn't able to reproduce it, and so now I have successfully built a set of legacy and next pineboot-pro images, both base and xfce.
I tried using the xfce (next) image, but unfortunately it seemed to switch the display into an unsupported mode, and so neither the GUI, nor the text console was usable. All I could do was pressing Ctrl+Alt+Delete to initiate a reboot, but the same problem arose after the reboot, so I switched back to the base (next) image.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
