[my ordeal with rockpi4 and Penta Sata Hat + Tower]

Am 1.6.2021 um 00:29 schrieb TRS-80:

I was ready to buy one, but at that time, those Penta SATA HATs were unavailable.

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

[Getting started with GPIO, using "new" gpiod interface]

vor 50 Minuten schrieb TRS-80:

So, you are saying you did not need to enable any "overlays" as discussed in the Docs I linked above?

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.

 

vor 54 Minuten schrieb TRS-80:

Also, the docs that manufacturer (ODROID) provide all only show the stupid and useless WiringPi numbers, instead of the actual ones. 

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.

[Getting started with GPIO, using "new" gpiod interface]

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!

[Patch Management Process]

Oh yes! Mailinglist would be great for outdated guys like me :)

[my ordeal with rockpi4 and Penta Sata Hat + Tower]

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.

Spoiler

 

and as shown here:

 

Spoiler

 

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:

Spoiler

 

or a bit busy with firefox:

Spoiler

 

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

 

[NFS protocol not supported?]

vor 14 Stunden schrieb Igor:

And ofc any area from Jira / "Help wanted" section. Some tasks are trivial - just to break the ice.

Ok, I created my first pull-request with a network section in troubleshooting guide.

 

With Jira - I don't know, seems not to work. I read, that communication about a topic should happen in Jira, so I created an account. But probably you have to grant me some permissions to enable participating ...

 

So how should I start with Jira topics? For example, AR-735 is a topic, that sounds interesting. I use that pwm overlay on armbian as well as patches at LE ...

What needs to be done?

 

by the way: we're quite off topic already. Where's the right place for this kind of questions?

[NFS protocol not supported?]

vor 13 Minuten schrieb Igor:

Then someone, who we lack the most, has to find the time to do something about ...

Well, I would be willing to write some docs, but ...

1. - I guess, I need some permission to do so

2. - I'm absolutely not qualified to talk about network or system internals

... but if that's ok, I could write about my experience

 

vor 15 Minuten schrieb Igor:

Isn't it only important that MAC is set before talking to the DHCP server. 

That's the point - I suspect (can't proove it, its only like a feeling), that DHCP server responds to armbians mac address before using "my" mac-address. When I try to access internet right after connecting with ssh to rockpi, I have no permission to do so.

Waiting a few seconds, the ssh-connection breaks.

At reconnect, ssh rants about suspicious address entry. I accept that warning by writing "yes" and ssh-connections is established second time. This time internet access works fine.

When I'm to lazy in starting ssh-connection, the above will not happen.

 

 

vor 22 Minuten schrieb Igor:

A choice for Network manager lies in simpler usage for its users.

Everything you know is easy - the rest is hard stuff

 

 

vor 23 Minuten schrieb Igor:

<rant>

I appreciate your rants, as they show the other side of the game ...

 

vor 24 Minuten schrieb Igor:

People just want to have professional support and professional software without giving anything for.

Well, that's not true for everybody.

I'm willing to learn and do the job on my own, but I've almost no glue about it. So I need a helping hand, some pushes into the right direction, whatever helps.

I don't expect others to solve my problem.

I don't know, what's a resonable way of living together. I'm just a user and I wasn't able to compile armbian on my own (following your documentation). I know, my questions are steeling your time - but what can I give back?

You can count my experience with rockpi in hours - not in years.

[NFS protocol not supported?]

vor 5 Stunden schrieb tparys:

What boot script you're using is a mystery as you've not provided any information about your board (armbianmonitor -u)

Just wanted to upload that information for you, but ...

root@rockpi-4a:~# armbianmonitor -u
System diagnosis information will now be uploaded to Please post the URL in the forum where you've been asked for.

root@rockpi-4a:~# ping armbian.com
PING armbian.com(stuff.armbian.com (2605:7900:20::5)) 56 data bytes
64 bytes from stuff.armbian.com (2605:7900:20::5): icmp_seq=1 ttl=51 time=166 ms
64 bytes from stuff.armbian.com (2605:7900:20::5): icmp_seq=2 ttl=51 time=164 ms
64 bytes from stuff.armbian.com (2605:7900:20::5): icmp_seq=3 ttl=51 time=164 ms
^C
--- armbian.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 5ms
rtt min/avg/max/mdev = 164.301/164.886/166.041/0.816 ms
root@rockpi-4a:~# armbianmonitor -u
System diagnosis information will now be uploaded to Please post the URL in the forum where you've been asked for.

So - its not only for being impatient, the tool seems not to work as it should - or I'm stil to dumb to use it. The ping is just to proove, that I have internet access enabled.

I attached the output to this post

vor 5 Stunden schrieb tparys:

And it's probably using ifupdown. You can switch if you'd like.

That's not the question.

As a common user, you won't care which tool provides network support as long as the network works. So I guess, its not common to know about these options.

Having a problem - you search around and most (at least what I did) was trial and error.

Therefore I would have been happy to find a network section in armbian documentation which lists the issues or links to related forum discussions.

 

by the way: mac-address of Network-manager is established very late in boot process, so wrong ip-address with all that conflicts will stil happen. So mac-address by Network-manager is just a poor workaround, no final solution!

Don't know, where the information is collected from, armbianmonitor does not show the final mac address ...

rockpi-4a.armbianmonitor1.7z

[NFS protocol not supported?]

Just for sake of documentation: setting mac address in /etc/network/interfaces works on TwisterOS

[NFS protocol not supported?]

Hi,

 

having identified the evil, I found lots of postings about this issue.

Unfortunately the given workarounds don't work.

 

• setting ethaddr in /boot/armbianEnv.txt does not change anything
• same with modifying /etc/network/interfaces - no effect.

What worked with armbian current (kernel 5.10.35) is changing configuration of Network-Manager.

That configuration can be found at /etc/Networkmanager/system-connections

I have a file-entry like this: 'Wired connection 1.nmconnection'. Format is common ini-file format of linux.

There's a group called [ethernet], which contains an entry "cloned-mac-address", which gets used on every  reboot.

 

Changing that number, changes mac-address and for so the address received from dhcp server.

 

@developers

As there are so many postings regarding this issue, what about adding a "network" section to "Troubleshooting" of armbian documentation?

[NFS protocol not supported?]

just an idea: what about taking uuid of root partition, if cpuid is zero or undefined?

[NFS protocol not supported?]

vor 2 Minuten schrieb arox:

6e is odd !!!

I don't think, that my dhcp-server does validate the mac-address. I guess, it takes the number as is and uses it as token ...

 

anyway: looks like I found the problem.

I guess, any linux has some individual hardcoded portion ...

this is output from twisteros:

 eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
	    link/ether ea:69:c3:92:45:fc brd ff:ff:ff:ff:ff:ff

its different to armbian native - but also constant - so two boxes with twister would fail too

[NFS protocol not supported?]

After some further research - it looks like armbian generates mac-address from cpuid - but rockpi has no cpuid ...

 

excerpt from ifconfig:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 6e:e4:fe:d4:82:6d brd ff:ff:ff:ff:ff:ff

 

Is there a way to fake/set/overwrite static part from cpuid or cpuid ?

[NFS protocol not supported?]

vor 10 Stunden schrieb Werner:

armbianmontor -u will provide you with a link to a website where the debug logs have been pushed to.

Thank you, Werner, for the explanation!

Patience is not my strong point. So I killed the program before it could tell me any link.

I thought, I have to enter some address or path ...

Being more patient, it works ;)

 

vor 14 Stunden schrieb lanefu:

for grins try added -o vers=3

does not change anything.

 

vor einer Stunde schrieb arox:

There are a number of issues with the numerous versions of nfs, locking, architecture and export path on server with nfsV4 ... and I wouldn't trust error messages.

Hm, I do not want to use version 4, nor do i have an export root stored anywhere. Thus it is difficult for me to assign the error to this category.

 

anyway ...

 

... since the error only occurs when both server and client are running armbian, I had a suspicion.
So I started the client (armbian recent) with ssh connection to my main machine. When I then turned on the NAS, the ssh connection was interrupted with the following error message:
"Connection to ... port 22: Broken pipe"

When I then looked at the list of active machines, only the NAS was listed. The client (with armbian) was gone.

Could it be, that the MAC address is generated by the operating system and thus two different machines get the same MAC address?

 

That would explain a lot.

[NFS protocol not supported?]

Thank you all for your support!

 

vor 7 Stunden schrieb lanefu:

can you do the following

zgrep -i nfs /proc/config.gz

Oh, didn't know, that config is available that way (on my desktop debian it is not)

 

Here's the result:

CONFIG_USB_FUNCTIONFS=m
CONFIG_USB_FUNCTIONFS_ETH=y
CONFIG_USB_FUNCTIONFS_RNDIS=y
CONFIG_USB_FUNCTIONFS_GENERIC=y
CONFIG_XENFS=y
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_KERNFS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V2=m
CONFIG_NFS_V3=m
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=m
CONFIG_NFS_SWAP=y
CONFIG_NFS_V4_1=y
CONFIG_NFS_V4_2=y
CONFIG_PNFS_FILE_LAYOUT=m
CONFIG_PNFS_BLOCK=m
CONFIG_PNFS_FLEXFILE_LAYOUT=m
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org"
CONFIG_NFS_V4_1_MIGRATION=y
CONFIG_NFS_V4_SECURITY_LABEL=y
CONFIG_NFS_FSCACHE=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFS_DEBUG=y
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
CONFIG_NFS_V4_2_READ_PLUS=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_PNFS=y
CONFIG_NFSD_BLOCKLAYOUT=y
CONFIG_NFSD_SCSILAYOUT=y
CONFIG_NFSD_FLEXFILELAYOUT=y
# CONFIG_NFSD_V4_2_INTER_SSC is not set
CONFIG_NFSD_V4_SECURITY_LABEL=y
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y

 

And this is "grep -i nfs /boot/config-5.10.0-0.bpo.3-amd64" from my desktop debian

CONFIG_USB_FUNCTIONFS=m
CONFIG_USB_FUNCTIONFS_ETH=y
CONFIG_USB_FUNCTIONFS_RNDIS=y
CONFIG_USB_FUNCTIONFS_GENERIC=y
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_KERNFS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V2=m
CONFIG_NFS_V3=m
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=m
CONFIG_NFS_SWAP=y
CONFIG_NFS_V4_1=y
CONFIG_NFS_V4_2=y
CONFIG_PNFS_FILE_LAYOUT=m
CONFIG_PNFS_BLOCK=m
CONFIG_PNFS_FLEXFILE_LAYOUT=m
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org"
# CONFIG_NFS_V4_1_MIGRATION is not set
CONFIG_NFS_V4_SECURITY_LABEL=y
CONFIG_NFS_FSCACHE=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFS_DEBUG=y
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
# CONFIG_NFS_V4_2_READ_PLUS is not set
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_PNFS=y
CONFIG_NFSD_BLOCKLAYOUT=y
# CONFIG_NFSD_SCSILAYOUT is not set
# CONFIG_NFSD_FLEXFILELAYOUT is not set
# CONFIG_NFSD_V4_2_INTER_SSC is not set
CONFIG_NFSD_V4_SECURITY_LABEL=y
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y

 

vor 7 Stunden schrieb lanefu:

and also armbianmontor -u

I beg your pardon, but I'm too stupid for that tool.

I read a lot about it (in other threads), skimmed the docs for it, but I don't know, what to enter, when it asks for a target.

So if you tell me what output you want, I could deliver any on my own.

I know my debian well - as a user. Not as a developer.

 

vor einer Stunde schrieb tparys:

I've hit this error when trying to mount a NFS share from a Windows system

I don't have/use any windows systems. My PCs run all debian stable without any experiments.

Only with rockpi I started to use others and find a usable base ...

 

vor 3 Stunden schrieb lanefu:

what's your mount target...

I don't understand your question.

I have two rockpi sata towers, one runs armbian multimedia legacy with emmc and boot from usb-drive, the other (not assembled yet) is my testbox, where I can switch sdcards.

 

In this case, armbian multimedia legacy is the nfs server and armbian current was the client (target?)

[NFS protocol not supported?]

Hi,

 

I just updated my armbian current to 5.10.35 and I'm quite excited, as pwm and gpio works as with LE :)

Then I tried to mount some nfs-shares from nas. Usually I only have to install nfs-common.

I did that on armbian, but when I try to mount a share, I get the error message, that nfs protocol (version) is not supported.

 

The used command work on every other system I have (desktop and rockpi).

I just use 'nfs' as filesystem type - no version specified/requested.

 

Is there something special on armbian, to have nfs support enabled?

[change kernel of TwisterOS?]

Hi Werner,

 

thank you very much for your attention!

 

vor 12 Stunden schrieb Werner:

Maybe try to get in touch with the guys via their Discord or Matrix channels

Sorry, but I'm to old for that shit :(

I know how to write emails or participate in a forum, but chat is not my media.

Beside that, I'm a friend of asynchronous communication.

 

Maybe you'd like to shine me a light, how I would do that on plain armbian?

Content of boot directory looks quite similar to armbian - beside the version numbers.

On plain linux I would issue something like update-grub which then generates/updates all required files for boot.

 

Things are more complicated with the little bastards. I read, that (some?) u-boot expect kernel and initrd at fixed partition location (block number?), so normal copy operations might fail.

I guess, that current armbian has evolved u-boot, so that boot requirements are more relaxed, but I don't know anything.

 

I guess, as LE boots with just kernel and system file from special partition, the kernel will run without dynamically loaded modules. So a replacement should be possible. But I don't know, how to get around with u-boot.

 

So any hint or link to read is appreciated a lot.

[change kernel of TwisterOS?]

I'm pretty disillusioned. No system for the rockpi meets all my expectations. But TwisterOS comes very close. Even though I don't play computer games, I like the desktop and also the gimmick with the circles. Most of all I like that I can run Kodi and firefox from the same login. This is exactly what I was looking for.

Unfortunately the hardware PWM does not work under TwisterOS. Neither via overlay, nor with manually changed dtb file.

I discovered that TwisterOS and LE use the same kernel version. Under LE my driver works, so I would like to try copying the kernel from LE to TwisterOS.

 

Now both systems boot completely different. What do I need to consider to get the kernel from LE to work under TwisterOS? I guess, at least I have to generate a new uInitrd, but I don't know, how to do that.

 

[NanoPi M4V2: Standard PCIe Devices Anyone?]

vor 7 Stunden schrieb TCB13:

Are you going to use it with the NanoPI?

No - but look:  from what I read, your nanopi is a big size nanopi and is a rk3399 device.

I have a rockpi - normal size - and a rk3399 device too. So I think, both have more in common, than they differ.

I guess, we build the same image but may have different dtb and uboot.

Some pi software (like pigpio) does not work on my rockpi - and I guess, same is true for yours.

I try many os images, to find out, what the hardware supports, and what is software limitations.

For example - I build LE images on my own, but failed to build armbian. Images supported by radxa are pretty old. Twister is the most recent one, that seems to fulfill my needs. But my driver only works on LE. With armbian the button does not work and with twister the pwm does not work. So I have to start mixing my own flavour.

[NanoPi M4V2: Standard PCIe Devices Anyone?]

vor 15 Stunden schrieb TCB13:

Does anyone has a similar setup?

Well - not similar from assembly, but similar in use case

I have Sata Tower from radxa. I have 4 ssd attached, but I didn't run any benchmarks. I love the small form factor, and its going to be useful after I ported driver from radxa.

[RK3399 Legacy Multimedia Framework]

vor 6 Stunden schrieb EndlessEden:

Thats a Firefox "Feature"(Firefox Home Content) not armbian exclusive. only older builds of firefox allow you to switch your "home page", and "about:blank" was treated like a incorrect URL

I'm new to armbian, but not new to linux. I use linux for several years now and I'm talking about this legacy framework, which means, its old stuff too. I never ever had a linux, where I could not reset homepage to blank.

... and even the most recent TwisterOS allows that.

So its hard for me to believe, that the armbian behaviour is not by intention.

 

I am firmly convinced that friendship, affection and esteem cannot be created through coercion. These values exist only voluntarily or not at all.

 

I wasn't convinced, that TwisterOS is worth a try. Bad webpage, extremly slow download, feature list attractive for playground kiddies, but not for old man ...

... but this behaviour with forced firefox homepage made me try it anyway - and what should I say: lot of crap flooded the disk, but things that I estimate are quite better, than with armbian. So may be, I stay with it.

Well LE is unbeaten anyway, so still researching for multiboot support ...

[RK3399 Legacy Multimedia Framework]

Ah I forgot - with testing I used armbian with display again and a very very annoying point is, that it is impossible to change firefox to start with an empty page.

I accept that advertising is necessary, but this is really going too far. Makes me abandon armbian altogether, even though I liked using it.
Nah, so that's not possible at all!

[RK3399 Legacy Multimedia Framework]

vor 11 Minuten schrieb JMCC:

Does it work with Raxda image?

Sorry, but no - of cause not! Radxa only supports its own debian (linaro) and ubuntu - but on ubuntu the driver does not install and for so, it does not work. On debian only fancontrol works ...

 

I wouldn't do such grunt work, if I could have avoid it.

I never wrote a single line in python and I didn't want that. But as python is the only language, that works on LE, I had to jump in the mud ...

LE does not support overlays for rockchips, so have to change dtb manually.

Anyway - pwm works on armbian with overlay on LE with manual editing of dtb ...

... but gpio works on LE without touching dtb, so I thought, it should/could? work the same way on armbian too.

Gpio-entries of sysfs behave the same way, as in LE - the problem (my problem): pin-number in armbian seems to be different.

[RK3399 Legacy Multimedia Framework]

vor 17 Stunden schrieb JMCC:

If you do, we'll get hundreds of people running their RK3399 boards at 2.2 GHz,

serious question: what is the benefit of overclocking regarding home-cinema? Do the unsupported formats play smooth? I won't use blender or 7zip at that moviebox.

 

@JMCC I worked out a driver for pentasata hat of rockpi, which runs at LE. Works so far.

Now I wanted to use the same stuff at armbian legacy, which I currently use as nas - but the gpio pins don't work as with LE.

From radxa wiki the pin numbering scheme is for kernel 4.4 - but gpio-pins don't work with kernel 4.4 but do work with kernel 5.10.30 (LE).

Any idea, how I could use the gpio at your legacy multimedia system?

 

[Armbian v21.05 (Jerboa) Release Thread]

vor 15 Stunden schrieb lanefu:

Comments like this are insulting to me and probably other devs as well.

I beg your pardon.

I didn't want to insult anybody!