Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. No, i gave up compiling on Armbian, i installed the debian bookworm server image provided by orangepi instead
  3. Today
  4. I was having some pretty substantial problems with several different builds before developing this hold pattern, Werner
  5. IIRC until like half a year ago this also worked just fine. I assume then this check was introduced upstream which caused this - more or less cosmetical - error.
  6. @JohnTheCoolingFan any clue?
  7. If I hold those packages I don't see any issues at all.
  8. moved. All boards using rk3588/s soc most likely work best with either vendor or edge kernel. Current has limited functionality since when this kernel became LTS only basic support was there. All further enhancements regarding hardware featureless were upstreamed later.
  9. I think there are some directories in /etc which contain initramfs pre/post scripts. I don't have hw on hand to check right now but I believe there was some script starting with z50- filename that contained this check and there should be a 2nd one from Armbian that actually does what the upstream script refuses to do.
  10. @0jay it should also happen for your build as well since I'm using generic Raspberry Pi build on RPi5. Or you never see it because of the "hold"? @Werner That's good to know. May I know if there's any way for me to check for certain? Thanks a lot!
  11. Yep... that looks like the method I had thought about: get the source from https://github.com/philipl/mpv.git#branch=v4l2request and compile it with the v4l2request option I have old experience making redhat rpms, but I need to learn how to make debian debs
  12. Thanks! we hope this guy could get the time to do it, I will be here for every testing need ! 😁 I already installed Armbien on an orange Pi zero 3, and I'm running pihole on it. Works fantastic! At least this allows me have some experiencie with Armbian
  13. Hi @robertoj The stock mpv-0.40.0 from alarm-repo does not seem to support v4l2request so downloaded mpv-full-git with v4l2request from @junari (manjaro-arm user) https://drive.google.com/drive/folders/1hAr_PB52fIBcZOgtx2WoGghv63H1-JzB. Also downloaded the ffmpeg-v4l2request. Wtih the ffmpeg-v4l2request and mpv-full-git from @junari mpv vpu hardware acceleration works. Did not build/compile mpv-full-git (no experience in compliling/build packages in Linux) downloaded mpv-full-git. According to @jnuari, the mpv-full-git PKGBUILD: https://github.com/iuncuim/manjaro-h616/blob/main/mpv-v4l2request/PKGBUILD Hopefully you can modified this PKGBUILD to compile on Debian Trixie.
  14. On an orangepi 5 this image failed to post. Armbian_25.8.2_Orangepi5_noble_vendor_6.1.115.img.xz worked just fine via balena etcher and booting from a nvme.
  15. Yesterday
  16. Are there any chances to enable i2c? I use the tv-box as a 3d printing server (klipper) openvfb is working fine, and I also managed to configure the G-Code Shell Command to display the remaining print time. I want to connect the g-sensor via the i2c bus, please tell me if possible. klipper@transpeed-8k618-t:~$ dmesg | grep i2c [ 1.374462] mv64xxx_i2c 5002c00.i2c: can't get pinctrl, bus recovery not supported [ 1.683314] axp20x-i2c 2-0036: AXP20x variant AXP313a found [ 1.683791] axp20x-i2c 2-0036: AXP20X driver loaded klipper@transpeed-8k618-t:~$ sudo /sbin/i2cdetect -l klipper@transpeed-8k618-t:~$
  17. Did you mean that you had success getting HW acceleration in Arch Linux+mpv-0.40.0? Which github page did you use, and did you use the standard official instructions in that github page, to build?
  18. Now the issue is it doesn't want to boot from SD (eMMC unplugged). I bought a brand new µSD as a last resort but nothing. I get a fast double blink on the status LED. Tried Armbian_community_25.5.0-trunk.131_Rockpi-4a_bookworm_current_6.12.16_minimal and Armbian_community_25.11.0-trunk.273_Rockpi-4a_trixie_current_6.12.49_minimal. Where can I find old Armbian-supported builds ? Because I'm sure those work. I'll try the last supported build and report. (can't delete this post)
  19. Experiencing the same issue, wifi fails to activate for about 4 out of 5 boots or so.
  20. It sounds like you're much more familiar with Linux than I am... especially on a deep level. It does have its strengths. I am grateful that it's a working alternative to anything from Microsoft or Apple. But I'm a firm believer that whether hardware or software (or any kind of design), simpler is better. Complication only arises from lack of clarity and understanding. One of the hallmarks of a good operating system is to provide complete support and essentially get itself out of the way - to make the computer an immediately usable tool for what you intend to use it for.... to be a clear conduit for that intention.
  21. @Totof le Belge Is there any chance you could give an in-depth explanation of the user-overlay script? I'm trying to use a speaker that uses I2S with the GPIO pins.
  22. Hi, TallMan, ...And here was me thinking I was all alone with my disillusionment of the way software has developed! I have to agree with most of your sentiments, with one exception. I have been a long time user of Linux (I stress user, as opposed to developer). This came about because more years ago than I care to remember, I worked for two major German companies on development of what was then known as Point-to-Multipoint communications, which later became the foundation for modern mobile phone network backbone communications. As part of this work, we had to carry out network planning for what are now the major phone network operators. Basically this consisted of predicting whether links would work under varying conditions (this was at frequencies up to 20 GHz). The tools we had to do this were the usual company Microsoft computer setups, satellite photographs of the area (in digital format), and a software tool written in Unix which used this data to predict lines of communication in 3 dimensions. This was my first experience of Unix, and it became a bit of a life-changer. Those of us who had to learn our way round it (as users), eventually all realised very quickly how much better/faster/more reliable it was than anything from anyone else, especially Microsoft. Of course, getting Unix for personal use at the time was not really on, but eventually Linus Torvalds produced Linux, and I for one never looked back. I'm well aware that users of Linux are regarded as nerds, and I'm happy with that, even if I try not to be one! As I got older, I eventually began to lose my interest in programming (another story!), but I am still a Linux user, and always will be. Its true it has its problems - but then all OS's have problems. In my opinion, sadly, these problems are not really the software as such - its almost always down to lack of information, or the proliferation of false and misleading information - after all, until recent years, developers set out with good intentions. Perhaps I can draw a parallel with my experiences in this thread using Armbian - While information and help does exist (Armbian documentation, for example), it is limited, and by no means comprehensive. It seems to be very difficult to make people understand that an OS is a tool, and should be usable, just like a screwdriver or a hammer, yet all too often the information to make productive use of the OS is simply not available. Instead, people like me rely on the good offices of people such as yourself - yet where would we be if the Internet didn't exist?. I do agree with you that even Linux is becoming 'overburdened' - but to some extent, that is one of its virtues - I have been able to make ancient computers run using Linux - Windows can't even make the transition from Windows 10 to Windows 11 unless the user buys a new machine. At least Linux has never declared good equipment obsolete, like Microsoft. It is easy for me to see a very close similarity between Armbian and Linux - I know this is intended, because of the Debian connection, so for people like me thats no bad thing. I can also see the attraction of RISC-V (probably too late for me to take it up), but one can hope these develop in a more organised, less monetised way than some OS's. Great to hear about the Commodore - a classic!. I still have my very first personal computers - a Sinclair Z80, which still works, although its keyboard has troubles. I got it around 1981, and it was one of the early self-assembly versions without a case. No-one was more surprised than me when the thing worked. Maybe I'll find another keyboard for it - I also have books giving its full ROM listing, and a circuit diagram, and 'advanced' programming - or BASIC in other words. Then I moved on to an Oric Atmos, produced in 1984 by Tangerine Computers (Shades of Orange!). It was a 'real' computer, with a proper keyboard, and used a Rockwell 6502. I did a lot of machine code programming on it, and very quickly changed the processor to a 65C02, which has a better, expanded instruction set. (in ths days, the 650s was often cited as having the first Reduced Instruction Set). I also still have it in working condition, plus a full ROM listing/circuit, and books on programming it (machine code). The BASIC it used was also very good. Later machines included a Dragon, Atari520 and some forgotten (perhaps for the best) . Like you the OPi is my first ARM device (actually given to me by a friend). I was interested in a Raspberry PI 5 (I have an old RasPi3), but they were so hard to get and expensive, I gave up. (I think the friend gave up on the OPi, which was why I ended up with it)! I also would have like to have seen most modern OS's lead to development of better systems, but I guess it won't happen in my lifetime, but at least I can support work on things like ARM and RISC-V. Incidentally, did you see that Qualcom won a case brought against them by ARM because techniques developed by ARM were allegedly used by Qualcom in their mobile phone processors? - probably not a good thing for ARM. And finally...I'm still stuck with this confounded stray icon on my Armbian installation, so another night searching for it.I 'm quite impressed otherwise - it seems very fast and efficient, (compared to my Ryzen7 Desktop machine) so I'll keep at it - It has most of the software on it that I need for now, so its definitely usable. I know about the hidden and system folders in Linux, and they are fairly easy to access in Linux Mint, but a search doesn't throw it up (yet) - I'll keep trying. Thanks for the Help, Keith
  23. @Werner I agree that it's more convenient for everyone, but it took me some time to find out how and testing it in an image. https://github.com/armbian/build/pull/8707/commits
  24. I transferred it on two consoles using armbian-config. There were no problems.
  25. Hi @Dominik Wójt, Thank you for your time looking into this. I was really stuck in a loop looking for solutions and this is the conclusion I also came to: The issue is with the kernel, not with DTBs, config, distro, monitor or anything else. I got the output to work on a regular image by installing "linux-image-edge-meson" but still no access to NAND and the device does not run smoothly. Best experience I've had was with an old image with kernel 3.10.108 which had everything working and running smoothly. I would like to try these patches you mentioned but unfortunately I don't have the knowledge on how to do so, then how to put this into armbian during the build process... I've now given up on this. Installed LibreELEC with and old kernel and donated the box away. Though I want to thank you again for your suggestions and for your help.
  26. @guenter Test Image: Armbian-unofficial_25.11.0-trunk_H96-tvbox-3566_bookworm_edge_6.16.10_gnome_desktop.xz data for H96 Max RK3566 Box: No external drivers, no external app, just pure mainline..... https://github.com/armbian/build/pull/8708
  27. Werner : thanks for you best effort, will try it as soon as im back home ,cheers
  28. It would make more sense to send a PR to fix this so it is included in all upcoming images/releases.
  1. Load more activity
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines