PineBook Pro update and upgrade to 5.18.12: unable to boot

sndwvs · 07-27-2022, 10:49 AM

no, there were no new patches, the question was more whether the kernel was vanilla.
that is, at the moment the new image is launched without problems, but the kernel itself does not want to work in a hard system?

then you need to look at dtb and the core itself.

wowbaggerHU · 07-28-2022, 07:17 AM

Okay, so I booted from the micro-SD card, and chrooted into my installed environment.
Then I upgraded the kernel, and all related packages, so I'm currently working with 5.18.14.
Then I updated the installed packages on the installed system, so the code running there should be the latest version available.

The problem is that after init is started, it just seems to hang there. Also, the screen is still blank. All I'm seeing during boot with respect to the installed system is through the serial console.

sndwvs · 07-28-2022, 09:52 AM

Quote:

Originally Posted by wowbaggerHU

The problem is that after init is started, it just seems to hang there. Also, the screen is still blank. All I'm seeing during boot with respect to the installed system is through the serial console.

that's the point that the kernel is workable, the difference is only in the location and type of fs. I think the system on the map will boot even without an initrd.

wowbaggerHU · 07-28-2022, 09:54 AM

Quote:

Originally Posted by sndwvs

that's the point that the kernel is workable, the difference is only in the location and type of fs. I think the system on the map will boot even without an initrd.

What do you mean by map? The internal storage/emmc?

sndwvs · 07-28-2022, 10:01 AM

Quote:

Originally Posted by wowbaggerHU

What do you mean by map? The internal storage/emmc?

Yes.
Аnd changes were made to fstab the same as uEnv.txt? also for more output can be added to uEnv.txt extraargs=dyndbg="file * +p" (info)

wowbaggerHU · 07-28-2022, 10:16 AM

Quote:

Originally Posted by sndwvs

Yes.
Аnd changes were made to fstab the same as uEnv.txt?

What do you mean exactly?
The system has been running for more than half a year now.
The fstab should be unchanged, from its previous state, and should contain f2fs for the root fs entry.
But I will double check it tomorrow to be on the safe side.

sndwvs · 07-28-2022, 10:24 AM

Quote:

Originally Posted by wowbaggerHU

What do you mean exactly?
The system has been running for more than half a year now.
The fstab should be unchanged, from its previous state, and should contain f2fs for the root fs entry.
But I will double check it tomorrow to be on the safe side.

As far as I understand, when switching to the 5.18.14 kernel, we changed rootdev in uEnv.txt, the same section should be in fstab.

wowbaggerHU · 07-29-2022, 05:36 AM

This is what I have in /etc/fstab

Code:

#
# /etc/fstab: static file system information
#
# <file system>        <mount point>   <type>   <options>                        <dump> <pass>
shm                    /dev/shm        tmpfs    defaults                         0      0
devpts                 /dev/pts        devpts   noexec,nosuid,gid=tty,mode=0620  0      0
sysfs                  /sys            sysfs    defaults                         0      0
proc                   /proc           proc     defaults                         0      0

/dev/mmcblk2p2         /               f2fs     noatime,nodiratime,defaults      0      1
/dev/mmcblk2p1         /boot           ext4     noatime,nodiratime,data=writeback,errors=remount-ro       0       1
/swapfile              none            swap     defaults,pri=0                                            0       0
/dev/nvme0n1p1         /home           f2fs     defaults,noatime,nodiratime                               0       0
tmpfs                  /tmp            tmpfs    rw,nodev,nosuid,noexec,size=2G          0      0

and /boot/uEnv.txt

Code:

verbosity=8
console=both
fdtfile=rockchip/rk3399-pinebook-pro.dtb
rootdev=/dev/mmcblk2p2
rootfstype=f2fs
overlays=rockchip-rk3399-opp-2ghz rockchip-pcie-gen2
overlay_prefix=rockchip

These settings aling well to the changes I've made: I added an ext4 /boot partition and moved / to f2fs, plus I added an NVME SSD.
I only copied the

Code:

overlays=rockchip-rk3399-opp-2ghz rockchip-pcie-gen2
overlay_prefix=rockchip

part of uEnv.txt as only that part was missing. The rest seems to be just fine.
But even after doing this change, the screen will stay off and the boot process will stop.

I will now try the extraargs parameter you suggested.

wowbaggerHU · 07-29-2022, 06:20 AM

This is what I got as boot log:

https://drive.google.com/file/d/1MAv...ew?usp=sharing

sndwvs · 07-29-2022, 07:08 AM

While I see mmc0 (mmc1, as I understand it, this is a memory card that is not inserted) and nvme0n1p1, so the root partition cannot be mmcblk2p2, it must be mmcblk0p2 and is registered in fstab and uEnv.txt

wowbaggerHU · 07-29-2022, 07:14 AM

This is when I booted from the SD card:

lsblk:

Code:

NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
mtdblock0     31:0    0    16M  0 disk 
mmcblk1      179:0    0  59.5G  0 disk 
`-mmcblk1p1  179:1    0  59.5G  0 part /
mmcblk2      179:32   0  58.2G  0 disk 
|-mmcblk2p1  179:33   0   128M  0 part 
`-mmcblk2p2  179:34   0  58.1G  0 part 
mmcblk2boot0 179:64   0     4M  1 disk 
mmcblk2boot1 179:96   0     4M  1 disk 
nvme0n1      259:0    0 465.8G  0 disk 
`-nvme0n1p1  259:1    0 465.8G  0 part

blkid:

Code:

/dev/nvme0n1p1: LABEL="home" UUID="8a507586-2762-4c63-afda-763ba48f46f6" BLOCK_SIZE="4096" TYPE="f2fs" PARTUUID="93662112-c166-7d4b-b5df-ad4432b9a40a"
/dev/mmcblk2p2: LABEL="root" UUID="2d5e08d9-b3c8-4d48-a17c-a74e47cbb27a" BLOCK_SIZE="4096" TYPE="f2fs" PARTUUID="af9494f7-02"
/dev/mmcblk2p1: LABEL="boot" UUID="64dc5c4e-cc36-4ee5-aa7f-67f3808db687" BLOCK_SIZE="1024" TYPE="ext4" PARTUUID="af9494f7-01"
/dev/mmcblk1p1: LABEL="linuxroot" UUID="dc8178df-f720-497b-8b01-a555b0fedc70" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="794733d8-01"

This arrangement has been like this until now, and apparently is so even now as I am getting this with your latest SD card image.
Plus if it would be mmcblk0pX, then the root partition would not mount even in ro mode, which would result in a kernel panic.

sndwvs · 07-29-2022, 07:50 AM

and in boot on EMMC a new kernel?

wowbaggerHU · 07-29-2022, 08:39 AM

Yes /boot resides on mmcblk2p1, and it holds the kernel, initrd and dtbs.

sndwvs · 07-29-2022, 08:53 AM

then it’s strange, it’s loaded from the sdcard but not from eMMC, but the difference is in the location and fs.

wowbaggerHU · 07-31-2022, 08:08 AM

I copied some files from the SD card image to the emmc card that were old on the emmc, and were not updated during the kernel upgrades.
These were:

Code:

root@janos-work:~# LANG=en_US ls -l /media/janos/linuxroot/boot/
total 49792
-rw-r--r-- 1 root root     2568 Jul 24 03:41 boot.cmd
-rw-r--r-- 1 root root     2640 Jul 24 03:41 boot.scr
-rw-r--r-- 1 root root   172032 Jul 24 00:16 idbloader.img
-rw-r--r-- 1 root root  4194304 Jul 24 00:16 rkspi_loader.img
-rw-r--r-- 1 root root  1005968 Jul 24 00:16 u-boot.itb
root@janos-work:~#

Currently the boot fails with the following:

Code:

U-Boot TPL 2020.10-rk3399 (Dec 10 2020 - 15:55:26)
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
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.10-rk3399 (Dec 10 2020 - 15:55:26 +0100)
Trying to boot from MMC2
   
   
U-Boot 2020.10-rk3399 (Dec 10 2020 - 15:57:06 +0100)
   
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
   
In:    serial
Out:   serial
Err:   serial
Model: Pine64 Pinebook Pro
Net:   No ethernet found.
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2640 bytes read in 12 ms (214.8 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
Failed to load '/boot/uEnv.txt'
Failed to load '/boot/dtb/rockchip/rk3399-pinebook-pro.dtb'
Failed to load '/boot/Image'
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr'
Failed to load '/boot/uInitrd'
Bad Linux ARM64 Image magic!
SCRIPT FAILED: continuing...

Device 0: Vendor: 0x15b7 Rev: 211070WD Prod: 200125803728        
            Type: Hard Disk
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
... is now current device
** Unrecognized filesystem type **
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
USB is stopped. Please issue 'usb start' first.
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rk3399-pinebook-pro-rk3399
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rk3399
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
Bus dwc3: Failed to get PHY0 for dwc3
Port not available.
No ethernet found.
No ethernet found.
Invalid bus 0 (err=-19)
Failed to initialize SPI flash at 0:0 (error -19)

Is there perhaps something that I have to update in these files?