Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Thank you for reporting back. Glad you got it solved.
  3. This. Just use the tools that were intended for software installation.
  4. I suggest you simply try. What is holding you back?
  5. Thank you for your question, @Jacob Burckhardt I do not use tags and FWIW, I do not see them on my main laptop, running Ubuntu Noble, either. Is this a Debian thing? Is your Armbian user space Debian?
  6. Thank you for coming back and sharing your "solution". It is always good to hear when things work out in the end, no matter the reason.
  7. Yesterday
  8. Att, my board broken after trying to update, idk why but it crashes and system doenst start i have installed the last trunk.
  9. Hello everyone, I have a problem, I hope you can help me. I have a TV box sold here in Brazil that has an H316 processor. I tried to use the images that were made available, but I only managed to boot successfully when I compiled my own after downloading the build from Git. Now I can boot from the SD card, create a user and passwords, use the sudo armbian-install command, but after that, a message appears saying "Counting files... few seconds" and freezes on that screen. Could someone tell me what I can change in the img compilation to fix this?
  10. Hi @Heisath, I think i can make a pull request from here: https://github.com/armbian/build/compare/main...djurny:build:patch-1, but would like to see someone else besides me test and scrutinize change. If positive results are in, I would very happy to finally contribute something! Groetjes,
  11. I am still here but as we all know our time is precious and I am currently using all my time for other projects. So I am not currently maintaining this board. On the whole I think armbian is moving too fast, for me, with new features in the build system and kernel which has somewhat discouraged me from further investing my time. ARM is IMHO not a stable platform, unfortunately. @djurny solution looks good - I might test this later and try to integrate it. But everyone else, if you can, please make it a PR on github It should only be necessary to adjust this file https://github.com/armbian/build/blob/main/config/bootscripts/boot-mvebu.cmd
  12. Is this an error in the build or installing jammy?
  13. The directory is incorrectly specified
  14. Try again with Linux 6.10 or older if you have an armbian img. Two things I found needed for linux 6.12+: 1. Define the pinctrl-names and pinctrl-0 parameters 2. MAYBE: rebuild Armbian in your computer, with one less Armbian patch As seen in: https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-216779 In this thread, you can see how I detected miscofigurations of the SPI GPIO: https://forum.armbian.com/topic/50418-dont-use-kernel-61216-on-sunxi64/page/2/#findComment-216924 WDR_s: did you try upgrading to Linux 6.12? (you could get H264 acceleration if you upgrade)
  15. What’s the error this time?
  16. Hi all, @Igor @0r31 I managed to come up with a more structural solution that should work for future increased sizes of the kernel/inital ramdisk as well. Let me know if you are interested in testing this out before I attempt to make a pull request, as some instructions are required to test this out. Changes are all in `boot.cmd` so no rebuilding or updating of U-Boot required. Based on the load addresses in U-Boot, reshuffled the loading of DT, kernel and initial ramdisk last. After loading the DT it will calculate the kernel load address based on the DT `totalsize`. After loading the kernel it will calcuiate the initial ramdisk load address based on the kernel filesize. Some other minor changes are also incorporated; `fdt resize <extrasize>` adter re-loading original DT when applying the overlays has failed. Skip the `fdt apply` and `fdt resize` for the SPI-SATA workaround. Results on my Helios4 with an old U-Boot 2018.11 below: Comments are welcome, Groetjes, boot-mvebu.cmd
  17. it didn't help, it threw up errors
  18. Thanks for investigating this. I have seen this issue reported quite a bit recently. I assumed it was something that had changed at the dtb level. Knowing this helps provide guidance to others in the same situation.
  19. You need jammy installed https://releases.ubuntu.com/jammy/
  20. windows10 virtuization system. ubuntu 24.04.2lts codname: nobe
  21. @svyatoslav are you using Ubuntu jammy? https://releases.ubuntu.com/jammy/
  22. Viken

    Viken

  23. I have a laptop with virtual Ubuntu. Who can help? I can connect via anydesk to help with the build.
  24. hello, I have ran into this issue recently with two different X96 mini boxes. One box which had a 8GB Samsung KLM8G1GEME-B041 NAND chip which worked fine, the other box's had a 16GB SK hynix H26M52103FMR and it failed to mount as eMMC. I investigated both chips and it turns out KLM8G1GEME-B041 supports HS200 bus speed mode, but H26M52103FMR does not. I found in the the .dtb file I was using it will try to use HS200 mode. So I decompiled the .dtb file and commented out the HS200 bus speed line in mmc and it successfully mounted as eMMC afterwards. mmc@74000 { compatible = "amlogic,meson-gx-mmc\0amlogic,meson-gxbb-mmc"; reg = <0x00 0x74000 0x00 0x800>; interrupts = <0x00 0xda 0x04>; status = "okay"; clocks = <0x03 0x60 0x03 0x7d 0x03 0x04>; clock-names = "core\0clkin0\0clkin1"; resets = <0x11 0x2e>; pinctrl-0 = <0x29 0x2a>; pinctrl-1 = <0x2b>; pinctrl-names = "default\0clk-gate"; bus-width = <0x08>; cap-mmc-highspeed; max-frequency = <0xbebc200>; non-removable; disable-wp; mmc-ddr-1_8v; //mmc-hs200-1_8v; // <- Comment out this line mmc-pwrseq = <0x2c>; vmmc-supply = <0x2d>; vqmmc-supply = <0x25>; phandle = <0xa0>; }; That worked for me, so I'm submitting this finding to give back as I have had relied on community help trying to get started. But I really don't want to get any further into TV boxes, this is once again yet another problem caused by cost cutting measures of manufacturing cheap TV boxes and there will only be more problems trying to get further.
  1. Load more activity
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines