tony013

November 11, 2022

vor 8 Stunden schrieb CryBaby:

This is the real solution. Annoying passwords are only enforced at installation.

No, that is no acceptable solution.

apart from that, it's about the first impression during installation.

I have two NAS (rockpi4) both running armbian. The installation of the first one was a few years ago. I invested a lot of time to be able to control the fan of the tower. When I installed the second NAS, I found that the newer armbian prohibits PWM fan control. I then decided to use an external fan controller and stayed with armbian.

Recently I had to install a raspberry4 (for the company). Armbian was of course my first choice. But the new installation routine frustrated me so much that I threw armbian in the garbage can and switched to raspi os. Raspi OS allows one to switch the keyboard to language in use before having to enter a password. With the password, everything is accepted. You just get a hint that the password may be too insecure to operate on the internet. With Armbian, the first thing you have to do is enter a strong password. With a keyboard setting that you don't even know! And even after the installation it is still very very difficult to switch the keyboard. At least for someone who doesn't know Linux that well.

If you compare the impression the first installation leaves on the user, a raspi os says: Welcome. Thank you for using raspi os.

The message of armbian on the other hand is: fuck off! Armbian is not for you!

September 12, 2022

vor 2 Stunden schrieb Werner:

If they work independently fine but crash if they are connected both then it seems the PSU is too weak and drops voltage

Hm, the default power supply of the sata tower package has 60W and the old PC power supply has 500W

According to rockpi-wiki a ssd needs about 5W - so about 25W should already be enuf ...

I suspect that the problem is more likely to be voltage spikes that could be transmitted from one part to the other via the power supply line.
That's why I would have thought of diodes rather than capacitors.
What do you think?

September 12, 2022

Hi,

I built a second nas from rockpi4 and as I used the 12V plug to power the tower, I thought, I could use an old pc power supply to drive both.

But when I start both nas from the same power supply, both will crash.

Any idea, how I could avoid that crash and stil use only one power supply?

Maybe add some electronic components?

September 11, 2022

I used to have a real linux-server with raid-systems and there I had regular failures of this kind.
The problem is that the hard disks that are sold as single disks are getting worse and worse.
I had a few times even the case that a newly purchased disk was already defective. Well, I could exchange it via RMA, but that costs time and is annoying.

A while ago I discarded the server and built a NAS based on rockpi4 with sata-extension. 4x 2.5" SSD - and since then there is peace on the disk front. Everything works as desired.

August 28, 2022

Hi,

I installed a fresh Armbian_22.05.4_Rockpi-4a_sid_edge_5.18.0 first on SD-card, then I used nand-sata-install to copy system to emmc. After that I rebooted and set up the nas (rockpi-4a with 4 ssd-drives). I already used ssh remote shell to perform apt dist-upgrade and copying of about 6TB ...

When all setup was finished, I shutdown the system, closed the tower and restarted again.

On that restart, the network came up without inet-address. ifconfig showed eth0 and l0, but eth0 had a mac-address (not the one, I configured in armbianEnv.txt) but no ip-address.

Here are some lines from syslog:

Aug 28 15:57:01 mynas NetworkManager[1659]: <info>  [1661695021.5656] device (eth0): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Aug 28 15:57:02 mynas NetworkManager[1659]: <info>  [1661695022.7361] device (eth0): carrier: link connected
Aug 28 15:57:02 mynas NetworkManager[1659]: <info>  [1661695022.7370] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Aug 28 15:57:02 mynas kernel: [  327.420987] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Aug 28 15:57:02 mynas kernel: [  327.421037] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 28 15:57:02 mynas NetworkManager[1659]: <info>  [1661695022.7393] policy: auto-activating connection 'Armbian ethernet' (9362e2eb-3533-439f-acd4-3804f33c01a5)
Aug 28 15:57:02 mynas NetworkManager[1659]: <info>  [1661695022.7409] device (eth0): Activation: starting connection 'Armbian ethernet' (9362e2eb-3533-439f-acd4-3804f33c01a5)
Aug 28 15:57:02 mynas NetworkManager[1659]: <info>  [1661695022.7413] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 28 15:57:02 mynas NetworkManager[1659]: <info>  [1661695022.7425] manager: NetworkManager state is now CONNECTING
Aug 28 15:57:02 mynas NetworkManager[1659]: <warn>  [1661695022.7434] platform-linux: do-change-link[2]: failure changing link: failure 16 (Device or resource busy)
Aug 28 15:57:02 mynas kernel: [  327.429651] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down
Aug 28 15:57:02 mynas NetworkManager[1659]: <warn>  [1661695022.7460] platform-linux: do-change-link[2]: failure changing link: failure 99 (Cannot assign requested address)
Aug 28 15:57:02 mynas NetworkManager[1659]: <warn>  [1661695022.7461] device (eth0): set-hw-addr: failed to set-cloned MAC address to AB:CD:47:11:FE:D0 (AB:CD:47:11:FE:D0) (NME_UNSPEC)
Aug 28 15:57:02 mynas kernel: [  327.433545] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211E Gigabit Ethernet] (irq=POLL)
Aug 28 15:57:02 mynas kernel: [  327.484253] rk_gmac-dwmac fe300000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
Aug 28 15:57:02 mynas kernel: [  327.495328] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
Aug 28 15:57:02 mynas kernel: [  327.495354] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
Aug 28 15:57:02 mynas kernel: [  327.495370] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode
Aug 28 15:57:02 mynas NetworkManager[1659]: <info>  [1661695022.8109] device (eth0): state change: prepare -> failed (reason 'config-failed', sys-iface-state: 'managed')
Aug 28 15:57:02 mynas NetworkManager[1659]: <info>  [1661695022.8121] manager: NetworkManager state is now DISCONNECTED
Aug 28 15:57:02 mynas NetworkManager[1659]: <warn>  [1661695022.8128] device (eth0): Activation: failed for connection 'Armbian ethernet'
Aug 28 15:57:02 mynas NetworkManager[1659]: <info>  [1661695022.8139] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 28 15:57:08 mynas NetworkManager[1659]: <info>  [1661695028.8165] device (eth0): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')

I see the error, but I have no idea, what to do.

June 27, 2021

vor 7 Stunden schrieb Igor:

I hope I didn't scare you with pointing out to our testing rig

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.

June 26, 2021

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.

June 24, 2021

The greeter can be downloaded from github.

June 23, 2021

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:

Screenshot_preview.jpg.7017ce320e67489aca034c434457872b.jpg

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.

June 8, 2021

I finally was able to kill armbian-spammer, so don't need to search for other os any more :)

vor 9 Stunden schrieb JMCC:

Did you try 4k?

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.

Am 6.6.2021 um 19:24 schrieb JMCC:

create a custom LightDM configuration, with a menu in some place that you can see.

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.

June 7, 2021

vor 21 Stunden schrieb usual user:

I am running on fedora as can be seen here.

Thank you for that pointer!

That forum looks like a lovely place for users.

Looks like you did a very good job. Very nice!

June 7, 2021

vor 7 Stunden schrieb JMCC:

That's because it does not have VPU acceleration.

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 :(

vor 7 Stunden schrieb JMCC:

You can probably also do that in Armbian, simply by installing the regular Debian Kodi packages (never tried it myself)

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.

vor 7 Stunden schrieb JMCC:

If you want fullacceleration on this chip, you need to disable X server for GBM KMS to take exclusive control of the display block.

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 acceleration
Kodi and MPV media players with built-in hardware acceleration support

June 7, 2021

vor 8 Stunden schrieb JMCC:

If you want to use the desktop, you will miss the top panel and/or window bars anyway

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

vor 11 Stunden schrieb JMCC:

Please see post #1 of this thread

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.

vor 8 Stunden schrieb JMCC:

is to create a custom LightDM configuration, with a menu in some place that you can see. You can find instructions for that via Google.

Ok, I'll try that. Thank you

June 6, 2021

@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?

June 6, 2021

Don't know - could it be possible, that some "misunderstandings" about edid could lead to disabled gpu?

June 6, 2021

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.

June 6, 2021

good news :)

how can I help testing?

June 6, 2021

vor 13 Stunden schrieb lanefu:

In case its help i made a helper script for managing relays

Thank you for showing your script.

Beautiful work! I love verbose coding :)

vor 3 Stunden schrieb usual user:

I have also written a rk3399-rock-pi-4 one. It can be staticly applied to the base dtb like this

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.

vor 3 Stunden schrieb usual user:

because of the chosen name format (con1-## with ## = connector pin number) this is not relevant for user space any longer. E. g.: "gpioget $(gpiofind con1-11)" always finds the correct line

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.

June 5, 2021

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!

June 4, 2021

vor 38 Minuten schrieb usual user:

Of course not, it's probably pinmuxed on special pwm functionality and therefore no longer available for GPIO.

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

vor 41 Minuten schrieb usual user:

I would add something along this lines to the devicetree and leave anything else to the input event system:

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?

June 4, 2021

vor 24 Minuten schrieb usual user:

Your IO is exported by sysfs interface at that time, which probably prevents the use of gpiod. Only one user allowed at a time.

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 ...

vor 28 Minuten schrieb usual user:

Can you retry without sysfs export?

Of cause.

I did it - and the result is unbelievable ;)

command: gpiomon gpiochip4 18

Spoiler

event: FALLING EDGE offset: 18 timestamp: [     175.193702174]
event: RISING EDGE offset: 18 timestamp: [     175.216348958]
event: FALLING EDGE offset: 18 timestamp: [     175.220979585]
event: RISING EDGE offset: 18 timestamp: [     175.235161388]
event: FALLING EDGE offset: 18 timestamp: [     175.241295014]
event: RISING EDGE offset: 18 timestamp: [     175.255088599]
event: FALLING EDGE offset: 18 timestamp: [     175.261979703]
event: RISING EDGE offset: 18 timestamp: [     175.275359110]
event: FALLING EDGE offset: 18 timestamp: [     175.282158045]
event: RISING EDGE offset: 18 timestamp: [     175.295347280]
event: FALLING EDGE offset: 18 timestamp: [     175.302631854]
event: RISING EDGE offset: 18 timestamp: [     175.318293323]
event: FALLING EDGE offset: 18 timestamp: [     175.318306740]
event: RISING EDGE offset: 18 timestamp: [     175.318320157]
event: RISING EDGE offset: 18 timestamp: [     175.318332116]
event: RISING EDGE offset: 18 timestamp: [     175.318343783]
event: RISING EDGE offset: 18 timestamp: [     175.318360408]
event: FALLING EDGE offset: 18 timestamp: [     175.321495035]
event: FALLING EDGE offset: 18 timestamp: [     175.384892556]
event: FALLING EDGE offset: 18 timestamp: [     175.384940391]
event: FALLING EDGE offset: 18 timestamp: [     175.385011560]
event: FALLING EDGE offset: 18 timestamp: [     175.385022060]
event: FALLING EDGE offset: 18 timestamp: [     175.385033727]
event: FALLING EDGE offset: 18 timestamp: [     175.385045102]
event: FALLING EDGE offset: 18 timestamp: [     175.385056769]
event: FALLING EDGE offset: 18 timestamp: [     175.385073103]
event: FALLING EDGE offset: 18 timestamp: [     175.385111896]
event: FALLING EDGE offset: 18 timestamp: [     175.385122396]
event: FALLING EDGE offset: 18 timestamp: [     175.385133480]
event: FALLING EDGE offset: 18 timestamp: [     175.385144855]
event: FALLING EDGE offset: 18 timestamp: [     175.385156522]
event: FALLING EDGE offset: 18 timestamp: [     175.385170522]
event: FALLING EDGE offset: 18 timestamp: [     175.385181606]
event: FALLING EDGE offset: 18 timestamp: [     175.385193273]
event: FALLING EDGE offset: 18 timestamp: [     175.385223024]
event: FALLING EDGE offset: 18 timestamp: [     175.385234107]
event: FALLING EDGE offset: 18 timestamp: [     175.385247816]
event: FALLING EDGE offset: 18 timestamp: [     175.385259191]
event: FALLING EDGE offset: 18 timestamp: [     175.385298859]
event: FALLING EDGE offset: 18 timestamp: [     175.385349611]
event: FALLING EDGE offset: 18 timestamp: [     175.385403570]
event: RISING EDGE offset: 18 timestamp: [     175.385473572]
event: RISING EDGE offset: 18 timestamp: [     175.385522282]
event: RISING EDGE offset: 18 timestamp: [     175.385697578]
event: RISING EDGE offset: 18 timestamp: [     175.385750955]
event: RISING EDGE offset: 18 timestamp: [     175.385839624]
event: RISING EDGE offset: 18 timestamp: [     175.385869958]
event: RISING EDGE offset: 18 timestamp: [     175.385923334]
event: FALLING EDGE offset: 18 timestamp: [     175.388275982]
event: FALLING EDGE offset: 18 timestamp: [     175.388291441]
event: FALLING EDGE offset: 18 timestamp: [     175.390268703]
event: FALLING EDGE offset: 18 timestamp: [     175.390295537]
event: FALLING EDGE offset: 18 timestamp: [     175.390307787]
event: FALLING EDGE offset: 18 timestamp: [     175.390320621]
event: FALLING EDGE offset: 18 timestamp: [     175.390332288]
event: FALLING EDGE offset: 18 timestamp: [     175.390343955]
event: RISING EDGE offset: 18 timestamp: [     175.390384790]
event: RISING EDGE offset: 18 timestamp: [     175.390395582]
event: RISING EDGE offset: 18 timestamp: [     175.390411915]
event: RISING EDGE offset: 18 timestamp: [     175.390427957]
event: FALLING EDGE offset: 18 timestamp: [     175.865613754]
event: RISING EDGE offset: 18 timestamp: [     175.897626210]
event: RISING EDGE offset: 18 timestamp: [     175.898679448]
event: RISING EDGE offset: 18 timestamp: [     175.898699865]
event: FALLING EDGE offset: 18 timestamp: [     175.898711823]
event: RISING EDGE offset: 18 timestamp: [     175.898721449]
event: FALLING EDGE offset: 18 timestamp: [     175.898731074]
event: FALLING EDGE offset: 18 timestamp: [     175.898740408]
event: FALLING EDGE offset: 18 timestamp: [     175.898749741]
event: FALLING EDGE offset: 18 timestamp: [     175.898760241]
event: FALLING EDGE offset: 18 timestamp: [     175.898769575]
event: FALLING EDGE offset: 18 timestamp: [     175.898780367]
event: FALLING EDGE offset: 18 timestamp: [     175.898789701]
event: FALLING EDGE offset: 18 timestamp: [     175.898808368]
event: FALLING EDGE offset: 18 timestamp: [     175.898873120]
event: RISING EDGE offset: 18 timestamp: [     175.915135730]
event: FALLING EDGE offset: 18 timestamp: [     175.921932624]
event: RISING EDGE offset: 18 timestamp: [     175.934194625]
event: FALLING EDGE offset: 18 timestamp: [     175.942493934]
event: RISING EDGE offset: 18 timestamp: [     175.953832494]
event: FALLING EDGE offset: 18 timestamp: [     175.962845240]
event: RISING EDGE offset: 18 timestamp: [     175.973407361]
event: RISING EDGE offset: 18 timestamp: [     175.973412028]
event: FALLING EDGE offset: 18 timestamp: [     175.983014832]
event: RISING EDGE offset: 18 timestamp: [     175.993152275]
event: FALLING EDGE offset: 18 timestamp: [     176.003214174]
event: RISING EDGE offset: 18 timestamp: [     176.013069276]
event: FALLING EDGE offset: 18 timestamp: [     176.023134676]
event: RISING EDGE offset: 18 timestamp: [     176.032895276]
event: FALLING EDGE offset: 18 timestamp: [     176.043109429]
event: RISING EDGE offset: 18 timestamp: [     176.052728567]
event: FALLING EDGE offset: 18 timestamp: [     176.063099641]
event: RISING EDGE offset: 18 timestamp: [     176.072556899]
event: FALLING EDGE offset: 18 timestamp: [     176.083043769]
event: RISING EDGE offset: 18 timestamp: [     176.092405649]
event: FALLING EDGE offset: 18 timestamp: [     176.103067815]
event: RISING EDGE offset: 18 timestamp: [     176.112301942]
event: RISING EDGE offset: 18 timestamp: [     176.112314192]
event: FALLING EDGE offset: 18 timestamp: [     176.123070569]
event: RISING EDGE offset: 18 timestamp: [     176.332251734]
event: FALLING EDGE offset: 18 timestamp: [     176.342851773]
event: RISING EDGE offset: 18 timestamp: [     176.352522245]
event: FALLING EDGE offset: 18 timestamp: [     176.364046893]
event: RISING EDGE offset: 18 timestamp: [     176.374721309]
event: FALLING EDGE offset: 18 timestamp: [     177.504150203]
event: RISING EDGE offset: 18 timestamp: [     177.515901482]
event: FALLING EDGE offset: 18 timestamp: [     177.523356977]
event: FALLING EDGE offset: 18 timestamp: [     177.579378631]
event: FALLING EDGE offset: 18 timestamp: [     177.579392631]
event: FALLING EDGE offset: 18 timestamp: [     177.579419757]
event: FALLING EDGE offset: 18 timestamp: [     177.579425299]
event: FALLING EDGE offset: 18 timestamp: [     177.579446007]
event: FALLING EDGE offset: 18 timestamp: [     177.579449508]
event: FALLING EDGE offset: 18 timestamp: [     177.579453008]
event: FALLING EDGE offset: 18 timestamp: [     177.579457091]
event: FALLING EDGE offset: 18 timestamp: [     177.579464383]
event: RISING EDGE offset: 18 timestamp: [     177.579471675]
event: FALLING EDGE offset: 18 timestamp: [     177.579485092]
event: RISING EDGE offset: 18 timestamp: [     177.579490050]
event: FALLING EDGE offset: 18 timestamp: [     177.579493550]
event: FALLING EDGE offset: 18 timestamp: [     177.579497342]
event: FALLING EDGE offset: 18 timestamp: [     177.579508717]
event: FALLING EDGE offset: 18 timestamp: [     177.579512218]
event: RISING EDGE offset: 18 timestamp: [     177.579515718]
event: FALLING EDGE offset: 18 timestamp: [     177.579519218]
event: FALLING EDGE offset: 18 timestamp: [     177.579523010]
event: FALLING EDGE offset: 18 timestamp: [     177.579526801]
event: RISING EDGE offset: 18 timestamp: [     177.579530301]
event: FALLING EDGE offset: 18 timestamp: [     177.579534093]
event: FALLING EDGE offset: 18 timestamp: [     177.579537593]
event: FALLING EDGE offset: 18 timestamp: [     177.579546344]
event: RISING EDGE offset: 18 timestamp: [     177.579549552]
event: FALLING EDGE offset: 18 timestamp: [     177.579554219]
event: RISING EDGE offset: 18 timestamp: [     177.579565302]
event: RISING EDGE offset: 18 timestamp: [     177.579574344]
event: RISING EDGE offset: 18 timestamp: [     177.579593595]
event: RISING EDGE offset: 18 timestamp: [     177.579610220]
event: RISING EDGE offset: 18 timestamp: [     177.579630346]
event: RISING EDGE offset: 18 timestamp: [     177.579637638]
event: RISING EDGE offset: 18 timestamp: [     177.579668555]
event: RISING EDGE offset: 18 timestamp: [     177.579684014]
event: RISING EDGE offset: 18 timestamp: [     177.579707056]
event: RISING EDGE offset: 18 timestamp: [     177.579743516]
event: RISING EDGE offset: 18 timestamp: [     177.579814976]
event: RISING EDGE offset: 18 timestamp: [     177.579834226]
event: RISING EDGE offset: 18 timestamp: [     177.579853477]
event: RISING EDGE offset: 18 timestamp: [     177.579875936]
event: RISING EDGE offset: 18 timestamp: [     177.579925229]
event: RISING EDGE offset: 18 timestamp: [     177.579945938]
event: RISING EDGE offset: 18 timestamp: [     177.579963438]
event: RISING EDGE offset: 18 timestamp: [     177.579981814]
event: RISING EDGE offset: 18 timestamp: [     177.580000773]
event: RISING EDGE offset: 18 timestamp: [     177.580038690]
event: RISING EDGE offset: 18 timestamp: [     177.580046274]
event: RISING EDGE offset: 18 timestamp: [     177.580050649]
event: RISING EDGE offset: 18 timestamp: [     177.580055024]
event: RISING EDGE offset: 18 timestamp: [     177.580072233]
event: RISING EDGE offset: 18 timestamp: [     177.580092358]
event: RISING EDGE offset: 18 timestamp: [     177.580104900]
event: RISING EDGE offset: 18 timestamp: [     177.580131151]
event: RISING EDGE offset: 18 timestamp: [     177.580145152]
event: RISING EDGE offset: 18 timestamp: [     177.580166735]
event: RISING EDGE offset: 18 timestamp: [     177.580179277]
event: FALLING EDGE offset: 18 timestamp: [     177.580199986]
event: FALLING EDGE offset: 18 timestamp: [     177.580252779]
event: FALLING EDGE offset: 18 timestamp: [     177.580268530]
event: FALLING EDGE offset: 18 timestamp: [     177.580291281]
event: FALLING EDGE offset: 18 timestamp: [     177.580305573]
event: FALLING EDGE offset: 18 timestamp: [     177.580328032]
event: FALLING EDGE offset: 18 timestamp: [     177.580347574]
event: FALLING EDGE offset: 18 timestamp: [     177.580371783]
event: FALLING EDGE offset: 18 timestamp: [     177.590954613]
event: FALLING EDGE offset: 18 timestamp: [     177.590989614]
event: RISING EDGE offset: 18 timestamp: [     177.591000114]
event: RISING EDGE offset: 18 timestamp: [     177.591004198]
event: FALLING EDGE offset: 18 timestamp: [     177.591013240]
event: RISING EDGE offset: 18 timestamp: [     177.591017323]
event: FALLING EDGE offset: 18 timestamp: [     177.591026657]
event: RISING EDGE offset: 18 timestamp: [     177.591030740]
event: RISING EDGE offset: 18 timestamp: [     177.591040657]
event: RISING EDGE offset: 18 timestamp: [     177.591055532]
event: RISING EDGE offset: 18 timestamp: [     177.591059616]
event: FALLING EDGE offset: 18 timestamp: [     178.244940454]
event: RISING EDGE offset: 18 timestamp: [     178.256360974]
event: FALLING EDGE offset: 18 timestamp: [     178.261726037]
event: RISING EDGE offset: 18 timestamp: [     178.274053373]
event: FALLING EDGE offset: 18 timestamp: [     178.282787278]
event: RISING EDGE offset: 18 timestamp: [     178.293781078]
event: FALLING EDGE offset: 18 timestamp: [     178.303274212]
event: RISING EDGE offset: 18 timestamp: [     178.313289444]
event: FALLING EDGE offset: 18 timestamp: [     178.323016501]
event: RISING EDGE offset: 18 timestamp: [     178.332588678]
event: FALLING EDGE offset: 18 timestamp: [     178.342973170]
event: RISING EDGE offset: 18 timestamp: [     178.352253673]
event: FALLING EDGE offset: 18 timestamp: [     178.363029009]
event: RISING EDGE offset: 18 timestamp: [     178.372270719]
event: FALLING EDGE offset: 18 timestamp: [     178.383310020]
event: RISING EDGE offset: 18 timestamp: [     178.392885990]
event: FALLING EDGE offset: 18 timestamp: [     178.403400568]
event: RISING EDGE offset: 18 timestamp: [     178.413429800]
event: FALLING EDGE offset: 18 timestamp: [     178.423533409]
event: RISING EDGE offset: 18 timestamp: [     178.435154601]
event: FALLING EDGE offset: 18 timestamp: [     178.443933132]
event: RISING EDGE offset: 18 timestamp: [     178.454466670]
event: FALLING EDGE offset: 18 timestamp: [     178.464773576]
event: FALLING EDGE offset: 18 timestamp: [     178.475766501]
event: RISING EDGE offset: 18 timestamp: [     178.475788960]
event: FALLING EDGE offset: 18 timestamp: [     178.475799752]
event: FALLING EDGE offset: 18 timestamp: [     178.475811419]
event: RISING EDGE offset: 18 timestamp: [     178.475853128]
event: RISING EDGE offset: 18 timestamp: [     178.475868587]
event: RISING EDGE offset: 18 timestamp: [     178.482451975]
event: RISING EDGE offset: 18 timestamp: [     178.482474142]
event: RISING EDGE offset: 18 timestamp: [     178.482484642]
event: FALLING EDGE offset: 18 timestamp: [     178.482528977]
event: FALLING EDGE offset: 18 timestamp: [     178.482539477]
event: FALLING EDGE offset: 18 timestamp: [     178.482551144]
event: FALLING EDGE offset: 18 timestamp: [     178.482562520]
event: FALLING EDGE offset: 18 timestamp: [     178.482574187]
event: FALLING EDGE offset: 18 timestamp: [     178.482590812]
event: FALLING EDGE offset: 18 timestamp: [     178.488400679]
event: FALLING EDGE offset: 18 timestamp: [     178.488427805]
event: FALLING EDGE offset: 18 timestamp: [     178.488438597]
event: RISING EDGE offset: 18 timestamp: [     178.488451430]
event: RISING EDGE offset: 18 timestamp: [     178.488467472]
event: FALLING EDGE offset: 18 timestamp: [     178.488479139]
event: RISING EDGE offset: 18 timestamp: [     178.488491390]
event: RISING EDGE offset: 18 timestamp: [     178.488503057]
event: RISING EDGE offset: 18 timestamp: [     178.488557308]
event: RISING EDGE offset: 18 timestamp: [     178.488603393]
event: RISING EDGE offset: 18 timestamp: [     178.488613893]
event: FALLING EDGE offset: 18 timestamp: [     178.546438971]
event: RISING EDGE offset: 18 timestamp: [     178.555031705]
event: FALLING EDGE offset: 18 timestamp: [     178.563127426]
event: RISING EDGE offset: 18 timestamp: [     178.575401969]
event: FALLING EDGE offset: 18 timestamp: [     178.582575706]
event: RISING EDGE offset: 18 timestamp: [     178.594806207]
event: FALLING EDGE offset: 18 timestamp: [     178.602583127]
event: RISING EDGE offset: 18 timestamp: [     178.613862768]
event: FALLING EDGE offset: 18 timestamp: [     178.622871722]
event: RISING EDGE offset: 18 timestamp: [     178.634120738]
event: FALLING EDGE offset: 18 timestamp: [     178.643045981]
event: RISING EDGE offset: 18 timestamp: [     178.653734398]
event: FALLING EDGE offset: 18 timestamp: [     178.662930898]
event: RISING EDGE offset: 18 timestamp: [     178.673980700]
event: FALLING EDGE offset: 18 timestamp: [     178.683213952]
event: RISING EDGE offset: 18 timestamp: [     178.693526691]
event: FALLING EDGE offset: 18 timestamp: [     178.703090411]
event: RISING EDGE offset: 18 timestamp: [     178.713112934]
event: FALLING EDGE offset: 18 timestamp: [     178.723060497]
event: RISING EDGE offset: 18 timestamp: [     178.733035186]
event: FALLING EDGE offset: 18 timestamp: [     178.743070835]
event: RISING EDGE offset: 18 timestamp: [     178.752972896]
event: FALLING EDGE offset: 18 timestamp: [     178.763054338]
event: RISING EDGE offset: 18 timestamp: [     178.773044194]
event: FALLING EDGE offset: 18 timestamp: [     178.783031716]
event: RISING EDGE offset: 18 timestamp: [     178.793224578]
event: FALLING EDGE offset: 18 timestamp: [     178.802973510]
event: RISING EDGE offset: 18 timestamp: [     178.813009451]
event: FALLING EDGE offset: 18 timestamp: [     178.822944764]
event: RISING EDGE offset: 18 timestamp: [     178.832877743]
event: FALLING EDGE offset: 18 timestamp: [     178.843065063]
event: RISING EDGE offset: 18 timestamp: [     178.852684783]
event: FALLING EDGE offset: 18 timestamp: [     178.863014732]
event: RISING EDGE offset: 18 timestamp: [     178.872625994]
event: FALLING EDGE offset: 18 timestamp: [     178.883010777]
event: RISING EDGE offset: 18 timestamp: [     178.892592872]
event: FALLING EDGE offset: 18 timestamp: [     178.902925154]
event: RISING EDGE offset: 18 timestamp: [     178.912567625]
event: FALLING EDGE offset: 18 timestamp: [     178.922956200]
event: RISING EDGE offset: 18 timestamp: [     178.932694341]
event: FALLING EDGE offset: 18 timestamp: [     178.943003872]
event: RISING EDGE offset: 18 timestamp: [     178.952710220]
event: FALLING EDGE offset: 18 timestamp: [     178.963138171]
event: RISING EDGE offset: 18 timestamp: [     178.972762851]
event: FALLING EDGE offset: 18 timestamp: [     178.982992463]
event: RISING EDGE offset: 18 timestamp: [     178.992889566]
event: FALLING EDGE offset: 18 timestamp: [     179.003206681]
event: RISING EDGE offset: 18 timestamp: [     179.012799276]
event: FALLING EDGE offset: 18 timestamp: [     179.023012847]
event: RISING EDGE offset: 18 timestamp: [     179.032705778]
event: FALLING EDGE offset: 18 timestamp: [     179.042992850]
event: RISING EDGE offset: 18 timestamp: [     179.052674114]
event: FALLING EDGE offset: 18 timestamp: [     179.063025063]
event: FALLING EDGE offset: 18 timestamp: [     179.063066189]
event: RISING EDGE offset: 18 timestamp: [     179.072745120]
event: FALLING EDGE offset: 18 timestamp: [     179.082797102]
event: RISING EDGE offset: 18 timestamp: [     179.092881753]
event: FALLING EDGE offset: 18 timestamp: [     179.102879192]
event: RISING EDGE offset: 18 timestamp: [     179.112685293]
event: FALLING EDGE offset: 18 timestamp: [     179.122904697]
event: RISING EDGE offset: 18 timestamp: [     179.132617170]
event: FALLING EDGE offset: 18 timestamp: [     179.142897534]
event: RISING EDGE offset: 18 timestamp: [     179.152558381]
event: FALLING EDGE offset: 18 timestamp: [     179.162896204]
event: RISING EDGE offset: 18 timestamp: [     179.172538676]
event: FALLING EDGE offset: 18 timestamp: [     179.182917042]
event: RISING EDGE offset: 18 timestamp: [     179.192517512]
event: FALLING EDGE offset: 18 timestamp: [     179.202914838]
event: RISING EDGE offset: 18 timestamp: [     179.212492849]
event: FALLING EDGE offset: 18 timestamp: [     179.222934509]
event: RISING EDGE offset: 18 timestamp: [     179.232448935]
event: FALLING EDGE offset: 18 timestamp: [     179.242978972]
event: RISING EDGE offset: 18 timestamp: [     179.252436814]
event: FALLING EDGE offset: 18 timestamp: [     179.263145356]
event: RISING EDGE offset: 18 timestamp: [     179.273024084]
event: FALLING EDGE offset: 18 timestamp: [     179.283637540]
event: RISING EDGE offset: 18 timestamp: [     179.293549810]

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

June 4, 2021

vor 19 Minuten schrieb usual user:

You did your calculation wrong.

That may of cause be true.

... but I can't follow your calculation.

radxa writes:

Zitat

Rockchip RK3399 GPIO has 5 banks, GPIO0 to GPIO4, each bank has 32pins

GPIO4_D5 = 4*32 + 3*8 + 5 = 157 (A=0, B=1, C=2, D=3)

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

June 4, 2021

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 :(

June 4, 2021

vor 1 Stunde schrieb TRS-80:

Also, I was pretty sure I read that the /sys/class/... interface is (going to be? already is?) deprecated.

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 :)

vor 1 Stunde schrieb TRS-80:

I guess you start it once and it just publishes the events as they happen.

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

June 4, 2021

vor 53 Minuten schrieb TRS-80:

In fact, if I am correctly understanding what gpiomon (part of gpiod package) does ...

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

vor 53 Minuten schrieb TRS-80:

... it should be a snap just to go around with a properly[0] jumpered button hooked up pin by pin and map everthing out.

[0] minding voltage, etc.

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'

Sign In

Forums

Store

Crowdfunding

Applications

Events

Raffles

Community Map

Posts posted by tony013

Important Information