• Content Count

  • Joined

  • Last visited

About tony013

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I finally was able to kill armbian-spammer, so don't need to search for other os any more :) No, I'm not interested in 4k. Don't have equipment for 4k. I'm happy with 2k and the equipment that I own. But I do have movies, that none of rockpi images is able to play (like inception). Some movies have wrong colors on playback or you see jpg-artifacts or the like ... But I couldn't detect any difference between armbian legacy and twisteros. Anyway - as I can't use twisteros any more, armbian legacy is the only desktop os with acceptable movie playback.
  2. Thank you for that pointer! That forum looks like a lovely place for users. Looks like you did a very good job. Very nice!
  3. I'm not convinced, that it is true. TwisterOS has same kodi-version like armbian legacy and movie playback gives the same impression like armbian legacy - smooth video and fresh sound. Firefox-implementation of armbian pushed me towards twisteros. ... and I'm already completely angry about firefox experience on armbian. Really, that sort of spam turns me into a spree killer :( Well, I tried it. Very disappointing experience. Kodi on armbian current is 3 generations back and has no hardware support for video and audio is the same very poor. I guess,
  4. Yes, but I found a way around that. I use the second bar with iconsize of 100 and changed conky to have all informations, I otherwise want in top bar ... With twister I could start cody from desktop without changing lightdm session. That was beautiful :) But as I can't use twister any longer, I have to live with your solution Sorry, I was unprecise. Of cause I tried the hints from #1 to disable lightdm, but I don't know, how to recover desktop. So I had to reinstall armbian from sdcard. Ok, I'll try that. Thank you
  5. @JMCC could you please explain me, how cody is startet, or what needs to be done to start kodi? After changing rockpi model, twisterOS does not boot anymore. Not even from a freshly prepared sdcard. So I had to step back to armbian legacy. Things work, but as I already wrote, top menu is outside of my screen. Therefore I would like to select between desktop and kodi by using different users or something like that. Could you please shine me a light for that way? Or would it be possible to start kody right from desktop, like twisterOS is doing it?
  6. Don't know - could it be possible, that some "misunderstandings" about edid could lead to disabled gpu?
  7. Hi, I startet with conky-grapes from TwisterOS, which I wanted to tweak to show cpu frequency for every core. But that showed, that conky is not able to do consistent text formatting, so I startet to write my own theme. As I like the armbian title font, I asked for the font, but it turned out, that it did not look as good as expected. So I discarded that variant and stayed with the previous selected fonts. Main purpose is to use that monitor in home cinema, therefore I used bigger fonts, which are readable from distance. Feedback is welcome.
  8. Thank you for showing your script. Beautiful work! I love verbose coding :) Thanks for that command! Haven't read about fdtoverlay before. That's a very nice way (with little additional scripting) to enable overlays for cases where dynamically overloading is not supported. Good job! This is by far the first reason for using "new" gpiod layer. Your key sample didn't convince me. I prefer "my" way of button handling. But finding pins by pin-name is sexy :) Do you mind to publish the source of your overlay? I asked dtc for th
  9. Hi, I have a really strange situation, which I don't understand and for so - I need help to solve it. I had 2 rockpi, one with sata hat which plays the nas role and one without sata drives, which is my frontend for home cinema (connected to AVR and beamer). Last few days I had the effect that the frontend froze and after close examination it turned out that all memory was used up. Fortunately, I already had a new rockpi with 1,4Gb memory. I thought I'd just change the eMMC and go on as before. But that was probably a big mistake. The new one did not start
  10. Sorry, but I don't understand your reply. You write that the pin should not be available for GPIO. I completely agree with you. But not with the output of gpioinfo! - gpioinfo states the pin as unused (and for so as available) Of cause - the pin is muxed - according radxa docs, the fan pwm line is the clock signal of a spi-channel Hm, that looks of cause very interesting. Is that an overlay or what is it? Who processes that file? I would not have that key labeled "Power-key". ... anyway: does that "wakeup-source" mean, that the ro
  11. Interestingly the pwm, which I use for fan control is not recognized by gpioinfo. Fan is attached to Pin 33, which is GPIO2_B4 or pin-num 76... So I looked at line 12 from chip2, but that is noted as unused ... Of cause. I did it - and the result is unbelievable ;) command: gpiomon gpiochip4 18 I counted the lines: 308 events for ONE single button press. Well the button is not of good quality and some kind of flaky, but that many events? Puh Now I understand, why I had so many problems in detecting the right button states ... :D
  12. That may of cause be true. ... but I can't follow your calculation. radxa writes: In my case GPIO4_C2 is 146 (you can find that number on the wiki-page from above) ... so I "only" need to take out the chip-calculation, which is 4*32 = 128 So 146 - 128 = 18 ... and forward calculation leads to: C (2) * 8 + Pin 2 => 16 + 2 = 18
  13. Some notes about why gpiod may not be the "right" tool for research and small user ideas ... I was curious about gpiod, installed it on my armbian rockpi4 and did the usual tests. gpioinfo shows all gpio lines and which of them are used ... Now I wanted to see, what gpio says about my penta-sata top-panel button. According to docs from radxa the button is connected to GPIO4_C2 - and following the pin numbering scheme from radxa, it has number 146 libgpiod breaks the numbering scheme and uses line-numbering for each chip. So I have to select chip4 -
  14. Thank you for insisting! I didn't paid attention to this on your first posting :( u r right - but if the pessimist would have been right, I could not have succeeded in my research. As I wanted to have driver support for penta-sata on LibreElec, I had to do things, I never wanted to ... LE does not have gpiod support. So I'm happy that sysfs stil works :) No, I wrote that shellscript just for you as a sample, how to test gpio pins without any use of foreign library ... If you're interested, my button-class to handle gpio buttons