tony013

  • Posts

    57
  • Joined

  • Last visited

Everything posted by tony013

  1. No worries. I am already an adult. To be more precise, I'm already over 60 years old. To use your words, I was scared by the tone and expectations of you developers. It's the first forum I've experienced that was designed for developers and not for users (3 of 18 sections are for users). A beginner has to come to terms with that first. You constantly write about how much effort the development is and that you want support - but when one is ready to cooperate, he will be left out in the cold. It is not yet 3 months since I bought my first rockpi4. Before that I had no contact at all with such small parts- and for so, I don't know anything about its requirements or handling. From there - my question was meant seriously. But I also do not have to impose myself. I have almost reached my goals, so I am quite satisfied.
  2. some more feedback about stumbling around NAS and mediaplayer ... I was running rockpi4 and penta-sata-tower with armbian current, whereas the mediaplayer is a rockpi4 with armbian legacy multimedia. As I already wrote, NAS got frozen sometimes watching movies When it happened 3 out of 5 times, I kicked armbian from the NAS and startet testing official images from radxa. I started with ubuntu focal server. Streaming works pretty stable - no freezes any more. But - ubuntu wasn't able to shutdown the NAS. Very anoying, as I had to unplug power stage to turn of the NAS. I did some more tests and found out, that shutdown on ubuntu works having the hat connected but no drives attached. As soon as I attach the drives, no more shutdown. So I checked official debian - but that behaves the same. Hm, on armbian shutdown worked without issue. So I started to build a server image of armbian. Long time tests have to show, whether I could get a system that does not freeze ... On the mediaplayer front I did lot of testings too. Lately I thought, that LE has the best player support, but that's not true. I have few movies with VC-1 codec and armbian legacy multimedia is the only one, that plays the movies some kind of acceptable (stil some freezes, but overall experience is more than movie than diashow). But change between kodi and desktop is unusable for me (my beamer screen misses about 10% on top and bottom, so no menubar ...). That was the trigger to start searching for alternatives. Sadly I had to realize, that there was none - so I had to develop one on my own. With all that testing, I killed two sdcards and an emmc ... but I almoust met my expectations.
  3. The greeter can be downloaded from github.
  4. Hi, I did some more tests and it turned out, that there is little difference between LE and armbian legacy for x264 or avc movies - but I found no movieplayer, that worked half as good as armbian legacy with vc-1 movies. Don't have that many movies with vc-1 but some much-loved like inception ... I already wrote, that I use rockpi as movieplayer together with a beamer, so session selection of armbian legacy is suboptimal for me, as about 10-15% on top and bottom of the screen are invisible (outside of screen). Lightdm/xfce is so dumb, that icons in topbar will not be scaled to bar height, which works fine for second bar ... Sadly I didn't find any other greeter, that runs on armbian and is more attractive like lightdm-gtk-greeter. So I started to build my own, which took lot more of time than expected ... any way - I finally have a working sample: is uses gtk too, so it works with armbian. I check the available sessions and if there's no session definition for kody-gbm, the kodi-button will be disabled (as in the screenshot taken from my desktop computer). Font- and button-size have been increased for a screen distance of 3m approximately. Last login will be cached, so user will be prefilled and hitting ENTER in the password field will login to the last session. Left most button starts kody and right most button the desktop.
  5. 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. I found the settings for login top bar and changed fontsize to 100 or so, now I can use the menu. Having that bar moveable like it is possible for the second bar would be wonderful. I'll keep searching.
  6. Thank you for that pointer! That forum looks like a lovely place for users. Looks like you did a very good job. Very nice!
  7. 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, you should give twisteros a try. They use current kernel (same version like armbian current and LE) and have hardware acceleration for video and desktop - and best of all, switch between desktop and kodi in a wink. Don't know, if that propaganda is true, but from twisterOS you can read: Latest PanfrostGPU drivers with desktop hardware accelerationKodi and MPV media players with built-in hardware acceleration support
  8. 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
  9. @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?
  10. Don't know - could it be possible, that some "misunderstandings" about edid could lead to disabled gpu?
  11. 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.
  12. 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 the source, and it looks terrible. Can't believe, that you had to write such ugly stuff. Do you know about a way to find conflicts between muxed modules, which share the same pin? A developer told me, that pwm-pin for the fan control of penta-sata-hat conflicts with hdmi sound (I2S ?). I'd like to verify that. But I can't I use both - the fancontrol on the same rockpi4 which generates the sound for my AVR (over HDMI) and I can't confirm any conflicts as I don't hear any problems.
  13. 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 at all with the eMMC from the 1.2Gb rockpi. That's why I thought I had to completely rebuild the bigger one. So I inserted the backup on sd card - and nothing did. I tried little by little all test sd cards, but with none started the rockpi. At least that's what I thought. When I opened the network overview, the rockpi was reported as active and lo and behold, I could log in via ssh. On the screen still dead pants. Then I tried the computer in the home theater and there I had a picture. So connected to a computer monitor - no picture, connected to a beamer - picture is ok. Thought, well, maybe the monitor is over. So I connected the monitor to the NAS. Clean picture including startup procedure - everything as usual. Thought maybe I just imagined it, so ran all the tests again - same picture. Just no picture! Stupidly, the previous frontend also no longer has a picture on the computer monitor. Only on the beamer. I am glad about every tip!
  14. 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 rockpi4 is able to wakeup on keypress after issuing a "poweroff"? and last not least - how can I act on key-events in userspace? Actually I recognize 3 different button states in my driver: single key press, double press and long hold press. Together with the config file, it is possible to call a python function, or a system process So I can execute 3 different things with a single button. Is that possible with gpio-keys too?
  15. 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
  16. 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
  17. 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 - which reduces the pin-number from above by 4*32 and leads to 18 Looking at output from gpioinfo, line 18 is used by "sysfs" and gpiomon fails with gpiomon: error waiting for events: Device or resource busy My button class from last post works without issues. If I want to achieve the same with gpiod, I probably have to modify kernel or at least some kernel modules - which is nothing I want to play with :(
  18. 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
  19. You won't need external tools. You can do all you need with tools provided by any system. to enable a gpio pin with number 13: echo 13 > /sys/class/gpio/export to verify the pin direction: cat /sys/class/gpio/gpio13/direction Result should be "in" (the default) to check the gpio pin state (value): cat /sys/class/gpio/gpio13/value From what I read so far, 3V should be a reasonable voltage for digital pins (1.8V for analog pins). The button from tower works with a pullup resistor, so default value of unpressed button is "1" Pressed button results in "0" When your test pin has a default value of "0", check whether active_low is enabled cat /sys/class/gpio/gpio13/active_low active_low should have a value of "0" A 10k resistor between gpio-pin and 3V will activate the pin and the switch should connect the pin with GND. You could solder the resistor and the switch with a cable from connection between switch and resistor, so you have 3 cables. Connect resistor to 3V and switch to GND, then the intermediate cable is your pin-checker. Last not least a little helper script, so you don't have to repeat the cat command: #!/bin/bash while grep -q 1 /sys/class/gpio/gpio13/value do echo -n . sleep 1 done echo 'Ok, got it'
  20. A quick look showed available packages from ali, pollin and tabius Availability changes - but *afaik* unavailable does not mean out of production - especially on tabius it was out of stock and few days later in stock again. I have a 2GB rockpi variant in the nas - and in the beginning (default installation) it freezes after serving some movies. I thought about small memory or possible issues with zram-logging - not sure. My driver generates frequent log messages, so stresses zram logging by far ... So I removed zram and zram logging and never had an issue again. Actually I'm thinking about connecting a relay to an gpio pin ... So I'm researching same issue like you
  21. Right. But - I don't know anything about dtb or gpio or kernel ... Just succeeded by trial and error. From all linux images I tested on rockpi4 - armbian multimedia legacy is the only linux, where gpio did not work ootb. I used overlays, but only to enable pwm for fancontrol. Not for gpio. Other linux work with config-file to enable specific overlays, but there I haven't to change a bit neither. Yes, I found lot of docs with wrong pinnumbers too. I can only recommend, try everything you can. Well, in my case it was easier, as I wanted to find out the gpio-name of the provided button of the stata tower. So I only had to enable the gpio pin and look, whether the value changes, when I press the button. In your case, you want to use the gpiopin as output. That's bit harder. ... but may be, you could attach a button to see, whether you can see value changes at button press. If so, then you can flip the direction and use it as output pin.
  22. Hi, I had the same problem, when I started to write a driver for penta-sata HAT of rockpi4 Many docs with contrary informations, must of them absolutely useless :( I don't know anything about odroid, but I can tell you, how I succeeded: First you need so docs from manufacturer, that tells you the pin numbering. See the formula to calculate the gpio pin names for linux. When you have the right number/name, you can test, whether gpio-handling of that pin works on your system. Here's a nice shellscript template for gpio usage. You'll see, that it uses sysfs. You might consider sysfs as outdated, but if sysfs works, it works with any linux image (presupposed you have the right dtb-file). Higher level libraries don't work on every linux ... Therefor I used sysfs in my driver. Some systems like LE don't have a real bash, so I'd had to code some python ... If the gpio for your pin does not work as expected, try different linux systems. I did so, to narrow the problems and find out, how to deal with hardware expectations. Finally I found out, that dtb from armbian was best to support all lowlevel modules I wanted to use. I just had to replace the dtb from twisteros with the one from armbian and all things worked as expected :) good luck!
  23. Oh yes! Mailinglist would be great for outdated guys like me :)
  24. I had bought the kit because I got attracted by its compact size. I had problems with my old media pc so good opportunity to tackle something new. I thought, my requirements for a media server would be quite low/easy to fulfill: smooth playback of 1080p movies clean multichannel sound access to firefox After testing all avaliable images on the rockpi, it was clear, that actually only LE offers exciting movie enjoyment. I had to realize, that my ideas are quite demanding after all. So it was clear, I had to get the driver from radxa working on LE. Why? well, hardware design of rockpi4 with extension HATs is somehow stupid. The flat cable needs to go from plugged board below systemboard to HAT above system board, so sdcard could not be changed any more. and as shown here: sd-card cannot be used together with the tower. Only emmc-support for boot. But emmc module is not exchangeable. That is why I had to start this odyssey. I tested the driver with officially supported images: on debian (linaro) the driver could be installed and the fan runs. Neither button nor display works. on ubuntu driver install scripts tells, that nothing has to be done, but nothing works ootb. No fan, no button, no display on armbian or LE the install script reffers to the git archive. I started with self compiled LE, but I'm not skilled to port lowlevel libraries to unknown system. Quite hard going Then I discovered posting of PetrozPL and JackR. Both scripts worked on armbian - well, I had some problems, getting into it, but ... anyway: trying the scripts on LE showed - no way. LE has no bash and busybox does not support arrays ... So I researched, how I could drive the fan using only tools avaliable at LE. Unfortunately LE has no reasonable interpreter for scripting. Only python :( I never wrote a line in python before! I first had to check, whether the kernel of LE supports fan control. LE has no dtb-overlay support for rockpi. So had to change dtb manually like this: copy dtb-file to writable location decompile with dtc -I dtb -O dts -o rk3399-rock-pi-4a.dtb rk3399-rock-pi-4a.dts find sections named pwm@ff420000 and pwm@ff420010 change status "disabled" into status = "okay" recompile dts with dtc -O dtb -o rk3399-rock-pi-4a.dtb -b O -@ rk3399-rock-pi-4a.dts copy dtb file back to original location (/flash) After reboot, fan works as with armbian - so I could write my fan-driver. Now system was ready to assemble the tower. I tested the driver with all other test images. Had to change code to work with older python releases and had some troubles with the button. But now driver runs stable and - as far as I can judge so far, where my driver does not run, other drivers will fail too. Well, my work with LE had the background, that I could get multiboot into play. But that seems pretty impossible. So I startet again researching, what could fulfill my ideas. Multimedia legacy - kodi works, movies are enjoyable. But no button support armbian current - no kodi, vlc works fine. Fan control works with button support debian/ubuntu - Fancontrol works with button support, but video playback is disgusting twisterOS - kodi works, movies are enjoyable, but no fan, no button I like twisterOS and the gimmick with the circles, but the text was unreadable for me. So I tweaked the gimmick and now I have it usable on my desktop as well on plain armbian. Using armbian instead of twisterOS has the benefit, that I don't have to flood the boot media with rubbish I never use (like openoffice and all that gaming stuff) Actually my armbian current looks like this: or a bit busy with firefox: So the open jobs (next steps) are: get multiboot into play (then I could use LE together with armbian) get another kernel on twisteros, that supports pwm - then I could use twisteros get a recent kodi on current armbian, then I could forget about all others