Jump to content

paradigman

Members
  • Posts

    88
  • Joined

  • Last visited

Everything posted by paradigman

  1. Can someone help me how I can fix my kernel build system? Whatever image I flash on my board, the armbian-config -> "install kernel headers" function does not install everything needed to compile the kernel.
  2. @Jean-Francois Lessard : could you share with us the compiled objects (*.o) and the kernel object (*.ko)? I have been unable to compile kernel on armbian for a week because there is some general error at the system level (kernel headers).
  3. @Jean-Francois Lessard: First of all, I would like to thank you for your great work with the tm16xx display driver. I would like to ask for your help on how I can avoid the warnings below when compiling? scripts/Makefile.build:403: warning: overriding recipe for target 'built-in.a' Makefile:1168: warning: ignoring old recipe for target 'built-in.a' scripts/Makefile.build:418: warning: overriding recipe for target 'modules.order' Makefile:1848: warning: ignoring old recipe for target 'modules.order' scripts/Makefile.build:403: warning: overriding recipe for target 'built-in.a' Makefile:1168: warning: ignoring old recipe for target 'built-in.a' scripts/Makefile.build:418: warning: overriding recipe for target 'modules.order' Makefile:1848: warning: ignoring old recipe for target 'modules.order' scripts/Makefile.build:403: warning: overriding recipe for target 'built-in.a' Makefile:1168: warning: ignoring old recipe for target 'built-in.a' scripts/Makefile.build:418: warning: overriding recipe for target 'modules.order' Makefile:1848: warning: ignoring old recipe for target 'modules.order' scripts/Makefile.build:403: warning: overriding recipe for target 'built-in.a' Makefile:1168: warning: ignoring old recipe for target 'built-in.a' scripts/Makefile.build:418: warning: overriding recipe for target 'modules.order' Makefile:1848: warning: ignoring old recipe for target 'modules.order'
  4. For some reason I can't install the kernel headers in the latest minimal image. I tried the usual way with armbian-confi, but the modules build directory always remained empty. Where can I download the headers for the latest current image in .deb format?
  5. @dfahren : "it works like never before! Even Wifi and Bluetooth.". Please share with us this image. "how I can accelerate xfce desktop". I suggest to you try install cinnamon. With cinnamon you get wayland too... and probaly that will good.
  6. I'm curious when rolling images are expected to be made with kernel 6.10 or 6.12?
  7. @maka: "Success with amazingfate rockchip_ vdec2 activartion". Please describe the necessary steps for it. Also write down exactly which image you used. Thanks.
  8. @Hqnicolas there is problem with Mainline images above trunk 205. Those don't boot after flash mode v1.1.
  9. @Hqnicolas I tried flas to eMMc your POP OS images, but to the 4/32 don't able because too big the image for that eMMC, on 8/64 don't boot after flash. I tried with the v1.1 mode.
  10. Hi @Hqnicolas , I'm very interested in this "pop" image, but unfortunatelly the file is corrupt (and very large).
  11. I also want to try the latest images, but I don't see it described anywhere, which method should be used to flash either these special editions or the mainline images to the emmc?
  12. Could someone make an update image that already has Wayland pre-installed, with working acceleration?
  13. @Martynas Skapas : I have already played through this problem with another rockchip box. The problem there was that the manufacturer unexpectedly replaced the 6334 chip with the 2734C. Here is my post about it from the past: https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=143890
  14. @hotnikq: I want to thank you for your wonderful work. I finally managed to install the latest EMMC: V1.0 Release Version on my device. I have been waiting for this moment for a year, I am very happy.
  15. @hotnikq "because I'm lazy and I don't want to work on that damn FIT image anymore" Please to make the FIT image for this project. Many more of us could use your excellent work if we didn't have to flash the image in several steps and using many hacks. Thanks
  16. @Kenneth Hidalgo: if you share your working image with us so that we can install it, I will tell you the answer to your question. 😕 Otherwise: sudo resize2fs /dev/drive_to_grow
  17. @hotnikq: many thanks for sharing this content, many people will benefit from it! Just so that even a beginner can have a sense of success, why not share the last image you compiled? I saw you had pretty good results with the last one. Just to make people want to go through the 219 steps described by shaggy013.
  18. @hotnikq: thanks for the encouraging words, but this is too little information for a beginner. I would like to get involved in this project, I would test images and functions, but first I need the basic information. The "shaggy013" link is not accessible, even with registration. However, I found out that building a FIT image requires a .its file and a kernel file.
  19. can someone describe in a few steps how I can cook myself a flashable ROM for H96 Max v56? I already realized that due to the lack of an SD slot, only the RK Dev tools can be used, but it can only handle images in android format (partitions). Thanks.
  20. how to install armbian images on this device if there is no CD card slot? I can't find a description for it.
  21. I'm very like the libreelec patched 5.19.15 version. Where can I find the correct header .deb file for it?
  22. really? This is a bit saddening, because now all media applications are lagging and I thought there was a way to speed up browsing and playing YouTube videos.
  23. thank you for the reassuring answer. Unfortunately, I have no experience in installing Linux drivers. Can someone explain how I can activate the lima driver?
  24. is there a driver available and usable for the Mali GPU? I miss the hardware acceleration in the desktop versions.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines