Jump to content

erazer1

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Igor! Thanks for your response! I wonder how you come to the conclusion that this problem takes several weeks to fix? I have already invested not only few minutes but at least two mandays into testing different images, comparing kernel commits, reading forum posts, compiling device tree and testing images. Maybe another developer owning the board and interested in a solution can give hints so we can work out a fix together and integrate into the armbian code. This could be useful for other owners not having to go through the same hassle of finding out the board does not work correctly using the image. Regards, erazer1
  2. If you are sure that the uSD is correct, the partition going read only is a sure sign that the image is not working properly. I have tested many of the images from Radxa and most of them with newer kernels are not working correctly. Regards, erazer
  3. Hi! I can confirm that the problem exists on Rock4 SE using the latest Armbian. Image boots correct from uSD, but does not boot from eMMC. Verified the eMMC using different methods on desktop computer, it is definately not faulty. You can try images with kernel version 5.10 or lower, it may work for you, as it does for me. I have tested several archived older images - most do not work until this kernel or lower. F.e you can try: Armbian_21.08.1_Rockpi-4b_bullseye_current_5.10.60.img.xz, Armbian_21.05.1_Rockpi-4b_buster_current_5.10.35.img.xz, Armbian_21.02.1_Rockpi-4b_focal_current_5.10.12.img.xz which are working for me. The problem was already analyzed by PPl on the forum, see however, it seems the fix was not applied to the later kernels device tree overlays yet. I managed to apply the mentioned fix for booting the emmc and recompile the device tree overlay. After applying the compiled file to the image it was able to boot. However, i got filesystem errors later. Possibly the timeout mentioned in the solution was not high enough? Using the archived images above, the file system corruption does not occur. If anyone is willing to fix this I could help with testing/compiling etc. Regards, erazer
  4. Hi! I can confirm that for the Rockpi SE there must be some errors at least with the Device Tree Overlay. I have the problem, that I can not boot the device from emmc using the latest image (f.e. Armbian_23.02.2_Rockpi-4b_bullseye_current_5.15.93). The same image can however, boot successfully from uSD card. I have tried several (archived) images from the past, none of them work correctly until the kernel version is ~ 5.10 and below. For example you could try out Armbian_21.08.1_Rockpi-4b_bullseye_current_5.10.60, Armbian_21.05.1_Rockpi-4b_buster_current_5.10.35.img, Armbian_21.02.1_Rockpi-4b_focal_current_5.10.12.img which I found to be working for booting the emmc. I guess all those problems are related to the wrong device tree. There was a change in the device tree overlay for the board in the kernel versions afterwards. There is also a thread about it in the forum - look at Regards, erazer
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines