Jump to content

jock

Members
  • Posts

    1849
  • Joined

  • Last visited

Other groups

Contributor/Maintainer

Recent Profile Visitors

12757 profile views
  1. @Ikesankom sorry, I misunderstood your issue, which is not related to the rest of the thread. It looks like the kernel does not enumerate the partitions of the USB drive, I just tested the bootloader which is not related at all with your issue. It is weird though, because I have an rk3288 tvbox which boots from an external hard drive with ext4 partitions without issues. Could you please post the results of the suggested commands cat /proc/modules and ls /dev/sd* ?
  2. @astrosky @tERBO this may help you getting hardware decoded videos, but don't expect your browser work with them. Mixing hardware video decoding into browsers compositors is not an easy task.
  3. @Ikesankom I did a quick test jiggling with bootloader to try and test multiple cases with both sdcard and emmc. I found a little "bug": there is no "alias" for the mmc devices in the device tree, so sometimes at boot the emmc is mmcblk0 and sdcard il mmcblk2, sometimes they get swapped. Anyway, despite this bug, the installer never broke the existing bootloader, at most it could miss the right device (I should check the logic behind, as it is not so easy guess what is the booting device) if you have both emmc and sdcard plugged. It's not a big deal though: the bootloader has got no real updates in a while since it works fine and the important thing is that the script does not destroy anymore the existing bootloader 😁 Anyway, if the board is remotely installed and controls something important, and you want extra-safety, you can do apt-mark hold linux-u-boot-tinkerboard-current and prevent bootloader upgrades
  4. @Ikesankom hello, no I didn't test it yet. Actually, I have been busy with other issues and totally forgot to test for the upgrade path. If you have a bit of patience I may give it a shot in the next few days, probably tomorrow.
  5. @A9 they are not errors, just missing firmware files for various wifi devices that you don't really need
  6. @lucky62 looking with elixir, it turns out that the function was already deprecated in 6.6: https://elixir.bootlin.com/linux/v6.6.27/source/drivers/gpio/gpiolib.c#L1022 You could copy the body of the deprecated function in place of gpiochip_find About of_get_named_gpio_flags you should see if you can afford to use the suggested function
  7. @PLaume Hello! Well, a power loss is a power loss... you won't know what will be gone when the cache is not flushed. I read from the eMCP the code "JY941" or "JY94I", but according to micron part decoder (https://www.micron.com/sales-support/design-tools/fbga-parts-decoder), that chip does not exist. Perhaps it is a fake chinese chip with "micron" printed on it with unknown reliability? About the errors, the hdmi "error" is rather an information and does not affect any feature. The ssv6200 error instead says that the wifi chip does not work because the driver only support ssv6051p chip and not the ssv6256p your board has.
  8. @astrosky I can't recommend you an image you can just install and everything works... tvboxes have this little problem about the changing hardware and that's not so easy. I have repeated dozen of times that tvboxes are not the way to go, buy an SBC if you need reliability. About 6.6.25 kernel, now I understand that you repeated the procedure starting from 6.6.23 image and this time the board rebooted fine but still without HDMI, am I right?
  9. @astrosky mmmh, pretty weird that it broke your setup, it is a quite standard 6.6 kernel, also it does not touch the bootloader. Did you perhaps alter a device tree and changed it in /boot/armbianEnv.txt? because the /boot/dtb directory is replaced when the new dtb package gets installed.
  10. @Hqnicolas thanks for the instructions, but I already have a backup of my box I had taken with multitool. The problem that is puzzling me is why the box does not boot from sdcard when the emmc is empty, something which is absolutely normal for other rockchip devices.
  11. i have one of those boards, the silkprint on the PCB says RK3528_DDR3, that's the one I used to bring up the mutltool for rk3528. A major "problem" I have it is that the board does not boot from sdcard when the eMMC is blanked. I had no time to understand what is the reason behind. Though it should boot when a bootloader is available in eMMC.
  12. Hello, for anyone who is having difficulties with HDMI, I made an experimental 6.6.25 kernel with a very small number of patches from LibreELEC project available here. I can't test by myself because the rk3318 board I have was already working with my monitor, yet the patched kernel did no harm on my setup. If there are some successful reports, the patches will be merged into armbian and hopefully the HDMI issues will be fixed once and for all. Thanks!
  13. Hello; for anyone is still having issues with HDMI output, I have arranged a minimal set of patches that could go into mainline armbian. The .deb packages for an experimental 6.6.25 kernel and dtbs are here. Just install them with dpkg -i I can't test if they are effective by myself because I have no setup where HDMI fails, nonetheless they seem not to harm my current setup. If you can afford to try that experimental kernel, please report your experience, thanks!
  14. You can take a look to this thread also: it does not contain any solution, but there I posted an experimental image with kernel 6.3 and some patches cut out from libreelec patches set that solved the problem. The problem is that it is a wide number of patches to import to solve the issue, and since I don't have a setup with HDMI issues I can't do tests to reduce the number of patches to an essential set.
  15. I did not experience all the issues you had, and it is strange that so many issues appeared just with updated kernel revisions.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines