Kernel 5.19.x not working for me with media branch (rockchip64 works)

[fraz0815]

I planned to upgrade and skip current 5.18 (EOL) with edge 5.19 or just use LTS 5.15.

 

Offcial images 5.19/edge (e.g. Armbian_22.08.1_Nanopct4_sid_edge_5.19.5.img.xz) won't boot at all, maybe a short uboot screen.

Using uboot v22.04 like other rk3399 boards did not fix it.

SInce the nanopct4.conf is boardfamily=media but also works with rockchip64 (which was changed some time ago),

building with boardfamily=rockchip64 current 5.15 or edge 5.19 works fine, the cli builds boot as expected. 

 

Maybe a general question, which bordfamily fits now best to nanopct4. I remember exactly problems which were fixed bei 150balbes maintainer when pulling it to media.

Thankfully all patches found their way to rockchip64, which seems to be more active for rk3399 in general.

 

Do you have any plans to combine them again? 

 

[balbes150]

Use a clean installation of the system, all cores work in it. You cannot combine the "old" and "new" systems.

[fraz0815]

Hmm, i deleted mmcblk2 to be sure to have no remaining stuff on it, booting with any 5.18 image like Armbian_22.08.1_Nanopct4_jammy_current_5.18.19.img and dd it.

 

sudo dd if=/dev/zero of=/dev/mmcblk2 bs=1M

 

Then tried Armbian_22.08.1_Nanopct4_sid_edge_5.19.5.img again, here is a screenshot of uboot, after that the screen loses signal and device does not boot (checked through dhcp on router).

[balbes150]

10 часов назад, fraz0815 сказал:

5.19.5.

when switching from 5.19.4 to 5.19.5, the USB on T4 was broken in the main source code. when exiting >=5.19.10, this should be fixed.

[ScottP]

I just ran apt upgrade and ended up with 5.19.5 - Can it be taken out of the repo if its known to be broken? My root filesystem is now read only - so there are other issues than USB. Thanks

[fraz0815]

I built Armbian_22.08.2_Nanopct4_jammy_edge_5.19.10.img with following command, no changes made:
 

./compile.sh  BOARD=nanopct4 BRANCH=edge RELEASE=jammy BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img 

 

Same error, see screenshot.

As mentioned earlier when changing boardfamily to rockchip64, so their patch directories (kernel+uboot) are used to build the image instead of media, it works fine.

Maybe some patch is missing?

I also made a build from master branch, Armbian_22.11.0-trunk_Nanopct4_jammy_edge_5.19.10.img which also does not get beyond uboot.

[balbes150]

Provide the full log from the UART console.

[balbes150]

Try the versions from here

 

https://disk.yandex.ru/d/_CAf6mgtVDGS4A

[fraz0815]

Armbian_22.08.0-trunk_Nanopct4_sid_edge_5.19.0.img.xz from your link works fine.

Sorry, no UART yet, I should get one 😕

[balbes150]

Try these versions with kernel 5.19.10 and 6.0

https://disk.yandex.ru/d/wMCxLcZCGBY7Ig

 

 

28 минут назад, fraz0815 сказал:

Sorry, no UART yet, I should get one

look at these versions, if they run, the UART console is not needed.

[fraz0815]

Same problem, uboot show no usb error on these images but also fails to boot.

 

edit: could a connected nvme drive cause this? I did not open the case und dismount it physically

 

Edited September 24, 2022 by fraz0815

[balbes150]

there will be no UART solution without a log

[fraz0815]

Okay, thank you so far.

I will report back when i have UART access

[balbes150]

Try version 20220926, it has patch fixes added, but I haven't checked their work (I don't have a working T4 anymore)

[fraz0815]

Version 20220926 works!

Tested Armbian_22.11.0-trunk_Nanopct4_jammy_edge_6.0.0.img and Armbian_22.11.0-trunk_Nanopct4_jammy_current_5.19.11:

Both boot, show no dmesg errors and emmc install (boot+system) is fine.

 

I will receive my UART device tomorrow for future debugging.

[balbes150]

1 час назад, fraz0815 сказал:

will receive my UART device tomorrow for future debugging.

if everything works, debugging is no longer needed, then the patch has fixed the startup problem. 

[fraz0815]

Maybe next time something is wrong i should be able to provide UART (and learn some new stuff anyway to keep the T4 up and running) 😉

[balbes150]

2 минуты назад, fraz0815 сказал:

Maybe next time something is wrong i should be able to provide UART (and learn some new stuff anyway to keep the T4 up and running)

if there is a financial opportunity, it is reasonable.