piter75

Members
  • Content Count

    181
  • Joined

  • Last visited

1 Follower

About piter75

  • Rank
    Elite member

Recent Profile Visitors

741 profile views
  1. Did you use the w same image for ROCK Pi 4C and 4B? 4C needs different images for all usb ports to work properly. You could also adjust the currently burnt image by editing fdtfile setting in /boot/armbianEnv.txt. Make sure fdtfile contains 4c and not 4b and reboot. All usb ports should be working after the reboot.
  2. To tell you the truth I did not pay much attention to wifi when bringing ROCK Pi S to Armbian ;-) One thing is certain - Radxa's image is plagued by the same issue. Care to test this image? It was built with Armbian's master and a bit fresher wifi driver. For me it still has stalls but they are much shorter - ~1s vs ~6s currently.
  3. What is your setup? What board revision is it? What image did you use before upgrading? Do you boot it with SD or eMMC? If eMMC - what are the markings on your module? That is odd indeed. I just tested fresh install of v20.05.4 (kernel 5.4.46 / focal / cli) from https://archive.armbian.com/rockpro64/archive/ with my unit (v2.1). I then upgraded it to v20.08.2 (kernel 5.8.6) and it boots fine. The issue obviously affects only some specific hardware configurations.
  4. Yes. IMHO by far the easiest option is flashing the image to SD card, booting it with SD (and eMMC module inserted). After booting you can run "nand-sata-install" command and choose "Boot from eMMC / system on eMMC option there. Some other options: if you have eMMC to USB or eMMC to SD adapter then you can flash it directly to eMMC module if you have USB-A to USB-A cable and then you can use the maskrom mode install
  5. There are no specific overlays for rk3308 in Armbian mainline builds for ROCK Pi S, yet. Remember also that this branch is very experimental for this board and YMMV. You can try downloading overlay straight from Radxa and install it with "armbian-add-overlay rk3308-i2c0.dts" command.
  6. Filesystem of your SD card has different UUID than the one in eMMC and the UUID is used to find root fs. Definitely. The root/boot partition should start at 16MiB and it needs u-boot images at correct locations. Maybe (most probably) there is some easier way but I believe you could be more successful this way: flash Armbian to SD and boot it; boot from eMMC and make new fs on the SD partition (be careful to not erase your eMMC partition); mount it at /mnt/sd and run rsync -avx / /mnt/sd/ run "lsblk -o PATH,UUID" to find the UUID of your new fs on SD; modify UUID value in /mnt/sd/boot/armbianEnv.txt (rootdev=UUID=...) and /mnt/sd/etc/fstab (UUID=.... for / mountpoint) to the one found on SD; unmount and try to boot from SD No warranty it works for you but the chance is definitely higher ;-)
  7. At this point I do not recommend running M4v2 with mainline linux. The reason for this instabilities and the remedy are yet to be discovered The board runs stable with legacy though.
  8. Rather not. This happens before eMMC is even probed. It could. At this point it is unfortunately a mystery to me what the real cause of this issue is.
  9. Yup. When you boot 5.7 or 5.8 from eMMC there is not much to see in the logs. I would like to see eMMC initialisation while you boot from SD and have eMMC and possibly NVMe connected. This may (possibly) shed some light at why you cannot boot with eMMC.
  10. Can you try to capture the verbose bootlog once again while booting from SD but with eMMC still inserted? I checked your previous logs but they were probably captured without eMMC module. You will most probably have to break the boot sequence at u-boot (just hit space bar around the time that Model: RockPro64 is printed) and run the following commands at u-boot prompt: setenv devnum 1 run mmc_boot
  11. It certainly requires some additional patching before building. This patch is for sure missing in our kernel for ROCK Pi S: https://github.com/radxa/kernel/commit/70a0bbccf001a06ae08f1dd4855059c2966dbe8b I remember omitting it because of lack of interest in Bluetooth. I may get back to that... Contributions are also welcome
  12. We need to work a bit on our download page for ROCK Pi 4 boards as I see you used 4B images - and these are the only ones easily accessible on the download page (CC: @Igor) For current use the images from here: https://dl.armbian.com/rockpi-4c/archive/ - all USB ports should work there. In legacy they will not work right now. I have it on my TODO list so it is possible that with the next point release all USB ports will work in legacy too.
  13. The original issue of blacklisting needed modules is indeed fixed in your image. Did it work before with v20.05.x? What's your display resolution?
  14. Use the Armbian way Add the following line to /boot/armbianEnv.txt overlays=pwm2 pwm3