ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum/Twitter feed: #armbian-rss | Logs: -> irc.armbian.com
xoan725450 has joined #armbian
xoan72545 has quit [Ping timeout: 268 seconds]
xoan725450 is now known as xoan72545
<stipa>
TRS-80: you're the best hacker
<TRS-80>
stipa: I'm honored, and aspire to the title, but not sure I deserve it yet. :)
<stipa>
TRS-80: to be humble is the trait the best of the best
<stipa>
of the*
<TRS-80>
I got further, but bombed out at 'Unable to locate package nala', so I am trying again with `NO_APT_CACHER=no`.
<stipa>
good luck man
<TRS-80>
Maybe I have an image ready by the time my new PBP arrives in a couple more days. :)
<stipa>
yeah lanefu chimed that 3D works good on the newest kernel or smthn
<stipa>
on that machine
<stipa>
touchpad doesn't work or smthn like that
<TRS-80>
stipa: Did you know that lanefu's raving about PBP like 2 years ago in this very channel is what got me to even look at PINE64 in the first place? lol I never paid any attention to them prior to that.
<TRS-80>
I thought they were just another random RPi knock off mfr.
<TRS-80>
Now I own several of their devices.
<TRS-80>
And become somewhat of a fan, one of the few in Armbian organization. lol
<stipa>
yeah, it's a fancy hardware
<TRS-80>
Some people say their hardware is junk, some times I wonder. lol
<TRS-80>
I just don't see anyone else making innovative devices like they do.
<ArmbianHelper>
^ Alternatives / Replacements for Helios4? - Helios 4 - Armbian Community Forums
<lanefu>
Thoughts on what?
<Unit193>
Sid Xfce of course. :D
<lanefu>
It was good!
<lanefu>
Trackpad tweaks missing tho
<lanefu>
And possibly the vol control
<lanefu>
But yeah felt good
<lanefu>
VLC worked great
<lanefu>
YouTube fine
<Unit193>
Sounds like you should add xfce4-pulseaudio-plugin to your panel, and ensure xserver-xorg-input-libinput is installed.
<lanefu>
Sounds like someone needs to go fix all the tweaks I put in place 2 years ago in the Armbian repo
<Armbian-Discord>
<thedude58> I want to connect a BTT PiTFT to a OrangePi 4B running armbian, but can’t figure it out
<TRS-80>
lanefu: Why you aren't PBP maintainer? No time I suppose.
<stipa>
he has M1
<TRS-80>
but I get the sense he loves his PBP
<lanefu>
Yeah I maintain nothing.
<Unit193>
I have my own tweaks on this, actually a settings package. :P
<Mangix>
huh M1
<Mangix>
wonder if a NAS can be set up with that
<stipa>
it's a BSD i guess
<TRS-80>
Mangix: I agree with Weerner's reply in the thread you linked, I have a long thread about NAS but his reply is essentially the tl;dr.
<stipa>
i use syncthing
<stipa>
and samba
<Unit193>
lanefu: If you can, may I suggest trying out the 4.17 builds from experimental?
<TRS-80>
Samba, eww
<Mangix>
hmmmm mac mini supports two thunderbolts
<lanefu>
4.17?
<stipa>
TRS-80: it's ok for my needs, win and linux works ok with my "backup" system
<Unit193>
Xfce 4.17, development builds.
<TRS-80>
stipa: Yeah, if you have Win in the mix, that's the way to go I guess (I no longer do).
<lanefu>
Unit193: you're giving me too much credit
<stipa>
TRS-80: yeah, i keep it as compatible with everything else as i can
<TRS-80>
Hmm, `DOWNLOAD_MIRROR=china` got me over the previous hump, but now that one's not working (for me, anyway) either. On to the other one, I suppose...
<ArmbianHelper>
^ build/config/desktop/sid/environments/xfce at master · armbian/build · GitHub
<TRS-80>
stipa: My experience was, once I had all GNU/Linux boxen on my network, everything magically 'just worked'.
<TRS-80>
Luckily I no longer need Windows for anything.
<stipa>
TRS-80: windows network by itself rarely works
<steev>
woo, 6.0-rc1 tagged
<stipa>
TRS-80: mixed one is ok in my case
<stipa>
TRS-80: but win machines aren't serving anything impportant
<Mangix>
TRS-80: Samba > NFS. Change my mind.
<Unit193>
Last time I used NFS, was on an XP "server" :D
<Unit193>
lanefu: Not giving too much credit, just figured you might be interested in trying out what's comeing up next. :)
<TRS-80>
Mangix: Samba is only needed on mixed networks. On a Linux only network, NFS will work much better.
Tenkawa has joined #armbian
<TRS-80>
other than that, NFS is F/LOSS, and Samba proprietary (pretty sure) which is reason alone not to use it
<Mangix>
uhhh, what?
<lanefu>
Unit193: ah! Yeah I wish I had more time to tinker around with that stuff. I don't even know what version xfce I'm using now lol
<Mangix>
TRS-80: if you want performance, there's ksmbd
<lanefu>
Im actually a mate fanboy
<Unit193>
lanefu: From unstable, that'd be 4.16.
<Unit193>
(I sort of maintain Xfce in Debian, so yeah I'm pretty aware of who uploads what. :P)
<stipa>
TRS-80: "Samba is an open source implementation of the Server Message Block (SMB) protocol."
<TRS-80>
Yeah, I mis-spoke. SMB is proprietary. Which is why it probably had to be reverse engineered, and can have problems. I have never used it. Why? It's better to simply avoid Windows altogether.
<stipa>
yeah, it's a win thing, probably reverse engineered
<stipa>
ah, no win, IBM
<Mangix>
the opposite actually. microsoft provides documentation and employees contribute to the kernel
<stipa>
?
<stipa>
you mean win devs work on samba?
<TRS-80>
Please. M$ tried to kill F/LOSS for many years. They lost. Now they are putting on a show, so as not to become completely irrelevant. Leopard doesn't change their spots. Let me know when they release Officer or Windows under a F/LOSS license. lol
<stipa>
as long as it does the job
<TRS-80>
Is it common to have problem retrieving release files? I seem to keep bombing out at that stage, on 2 different mirrors now.
<stipa>
it doesn't really matter which OS it is
<TRS-80>
Maybe not to you.
<TRS-80>
But I like to actually own and be in control of the things I spend my hard-earned money on. lol
<Mangix>
stipa: samba and CIFS
<Mangix>
the latter is the filesystem driver
<stipa>
TRS-80: i'm more concerned with reliability
<TRS-80>
Maybe they do now, but according to Wikipedia article I just skimmed, it seems it was reverse engineered at first. Which sounds about right to me, back then.
<TRS-80>
stipa: *nix win there, too, lol
<stipa>
Mangix: yeah, i've seen CIFS around, i use it to mount the samba from remote location in a filesystem of a machine i'm working on
<TRS-80>
brb, changing IP address
TRS-80 has quit [Quit: WeeChat 3.0]
TRS-80 has joined #armbian
<stipa>
Mangix: but i'm being spoiled by the 'syncthing'
<Mangix>
I use nextcloud on my helios4. It's quite slow...
<Mangix>
I think the container uses THUMB
<stipa>
yeah, nextcloud could be an alternative to syncthing i guess
<stipa>
i have no ida what the 'THUMB' is
<TRS-80>
Slow how? I mean, Helios4 might be underpowered for Nextcloud. If you just need file sync, Syncthing is much more lightweight and faster (DAV moves entire files upon change, Syncthing only changed blocks). Also Syncthing is decentralized. A really fascinating piece of software, actually.
<TRS-80>
I used to run Nextcloud, but switched to Radicale and Syncthing instead, which covered my needs. I never used the web based features of Nextcloud (YMMV, of course).
<Mangix>
stipa: how do I put this... imagine running 32-bit binaries on a 64-bit OS.
<Mangix>
that''s the best equivalent I can think of
<stipa>
it's a 32bit emulator on a 64 bit chip?
<Mangix>
no, there's no emulation
<TRS-80>
THUMB has something do do with instruction set and arch, I forgot details though.
<TRS-80>
maybe memory
<Mangix>
TRS-80: it's an ARM thing. Basically, THUMB allows to tradeoff binary size for speed
<TRS-80>
it's some extension IIRC
<Mangix>
Unfortunately all I want is speed so THUMB is useless to me.
<stipa>
need for speed
<TRS-80>
I mean, going to 64-bit opens up some advanced filesystems like ZFS, too. Why I think RockPro64 is recommended for NAS now. Besides the fact it has a real PCIe slot.
<Mangix>
uhhh what?
<TRS-80>
What what?
<Mangix>
THUMB has nothing to do with 64-bit
<Mangix>
THUMB instructions are actually 16-bit. That's how they save size.
<TRS-80>
No, but use-case of Helios4 is NAS. I thought you were looking to replace it with something faster/newer.
<TRS-80>
also wtf with these mirrors, I even changed IP
<Mangix>
TRS-80: yeah ARM32 is practically deprecated
<TRS-80>
IMO better to DIY, but maybe you don't want to.
<stipa>
what about older RPI stuff?
<TRS-80>
stipa: bad throughput because of dumb design with USB and Ethernet on same bus, etc.
<TRS-80>
esp. for NAS use-case
<TRS-80>
I think this is less true for newer versions, but I am still not a fan of RPi in general
<Armbian-Discord>
<lanefu> Yeah helios4 really is only good for a NAS....
<Mangix>
TRS-80: it's interesting. Most other solutions use a PCIe to SATA adapter (limited to 4gbps for PCIe 2.0). The Helios4 uses SerDes for the SATA ports, which is limited to 15gbps IIRC
<Armbian-Discord>
<lanefu> Really well done tho
<TRS-80>
Right. Then maybe you want to start to do other things, which is why I say just go RK3399, as you will have more power when you want it.
<TRS-80>
Mangix: I am unfamiliar with SerDes, but I actually like the fact that you can buy a cheap and standardized PCIe to SATA adapter, keep spares, etc.
<Armbian-Discord>
<lanefu> Helios4 used an industrial compute module.or a Marvell soc and was just a carrier board
<TRS-80>
This fact alone is why RockPro64 rises above all other RK3399 based NAS options, all the rest have some weird proprietary adapter, or you have to fiddle with ribbons, etc...
<Armbian-Discord>
<lanefu> Serdes is uses for high band width low latency channels for embedded SoCs for switches and a routers etc
<TRS-80>
Do people really connect their NAS via Wi-Fi?
<Mangix>
good question. I don't think so
<stipa>
i do
<TRS-80>
I consider it a plus it doesn't have Wi-Fi.
<stipa>
i mean, it's a hybrid network
<stipa>
it depends
<Mangix>
I was more ccommenting about ac, which is typically buggy as hell
<stipa>
there are few chips that are ok on linux
<Mangix>
few = 2. That's about right. Intel and Mediatek
<TRS-80>
Mangix: In the post I linked, I go thorough a long dissertation about alternatives, history, etc. and how I finally arrived at conclusion of RockPro64. In other words, not without quite a lot of consideration, over period of years.
<ArmbianHelper>
^ GitHub - morrownr/88x2bu-20210702: Linux Driver for USB WiFi Adapters that are based on the RTL8812BU and RTL8822BU Chipsets - v5.13.1
<Tenkawa>
I have a Realtek AC driver that does 800+MB perfectly fine
<Tenkawa>
yeah the BU's
<Mangix>
seems that module is bluetooth 4.2, not 5
<Tenkawa>
I have several of those running together in my current wifi setup
<stipa>
yeah, if the USB is stable they're fine
<Tenkawa>
indeed
<Tenkawa>
you "must" have stable USB (mine are USB3)
<Tenkawa>
(the dongles)
<stipa>
yeah, otherwise it's just crashes without logs and stuff
<Tenkawa>
first ones I've seen that actually can fully utilize usb3
<stipa>
yeah, i don't have a stable USB3
<stipa>
to check
<Tenkawa>
ah
<stipa>
i mean i have on the AP
<stipa>
but none of the clients have it
<Tenkawa>
I've been very lucky in that dept
<Tenkawa>
Even the machine I'm typing on right now is my converted PBBP
<Tenkawa>
er PBP
<stipa>
but, i'm connected with ethernet cable to the AP so NAS is fast enough
<stipa>
it's a USB HDD connected to the USB3 on the AP
<Tenkawa>
nod... My Odroid-M1 is eth too... that thing has some major IO
<stipa>
around 40MBs on a good day
<stipa>
mine is laptop upside down
<stipa>
the network node
<stipa>
AP, NAS, runs debian DE
<stipa>
few ethernet ports
<Tenkawa>
heheh
<stipa>
i would like to get the full speed AC
<stipa>
but as time is passing stability is the hing i'm wanting more and more
<stipa>
speed and stability is a luxury i think
<Tenkawa>
I hear ya..
<TRS-80>
stipa: Why not get something cheap, supported by OpenWrt/LibreCmc, it would probably be more reliable?
<stipa>
i like felxibility
<TRS-80>
OpenWrt is quite flexible
<stipa>
i've been there a decade ago
<stipa>
the hing with those is the lack of resources on them
<TRS-80>
I guess. But that is what we have SBCs for? :)
<stipa>
yeah, they can do it
<Mangix>
OpenWrt is fun
<TRS-80>
after using dd-wrt for many years, I am really enjoying OpenWrt now. It's much more like regular Linux. I keep my configs in a git repo, etc.
<stipa>
yea, new ones should be fine for light stuff
<stipa>
+ serving the WiFi
<Mangix>
fun fact: OpenWrt doesn't do THUMB
<TRS-80>
I guess I am of opinion to let a dedicated device route packets, and then use SBC (on the LAN) for more processor or storage intensive tasks.
Tenkawa has left #armbian [#armbian]
<TRS-80>
a lot of OpenWrt devices are running other arch than Arm
<stipa>
TRS-80: yeah or that, i like to cram as much of stuff in one machine
<stipa>
and network them
<TRS-80>
different strokes for different folks :)
* TRS-80
pulls out hair
<TRS-80>
wtf with these mirrors
<TRS-80>
I have changed IP, mirror, etc. and it just keeps bombing out
<TRS-80>
must be something on my end
<stipa>
or wait devs from Europe to wake up
<stipa>
they usually fix that up
<TRS-80>
yeah maybe it's not me
<stipa>
probably not
<TRS-80>
got close enough to get excited I guess, lol
<TRS-80>
I think it was almost done
<Mangix>
TRS-80: ARM and MIPS are the most popular architectures
<Mangix>
the latter is used for cheaper stuff
<TRS-80>
that's the one, MIPS, couldn't think of it at the moment
<TRS-80>
I never saw so many MIPS devices until I started poking around OpenWrt
<Mangix>
yeah. cost is the reason for its use
<Mangix>
hardware acceleration is very common.
<Armbian-Discord>
<Tonymac32> If you can't do it on a TRS-80 it doesn't need done
<Armbian-Discord>
<Tonymac32> Said the local ladies, I don't trust them
* TRS-80
pours a cold one and slides it down the bar towards Tonymac32
norwich has joined #armbian
buZz has quit [Ping timeout: 244 seconds]
<TRS-80>
kernel headers can be installed from armbian-config?
slacker_HD has joined #armbian
<Armbian-Discord>
<lanefu> See if it's broken or not
<ArmbianHelper>
^ Kernel Headers for 5.10.110 - NanoPi R5S - Armbian Community Forums
<TRS-80>
I guess my answer was more or less correct?
<TRS-80>
was just trying to make sure before spreading bs
slacker_HD has quit [Quit: Connection closed]
<c0rnelius>
Armbian making imgs for that board yet? I didn't think so.
* TRS-80
just realized what section it's in
<c0rnelius>
I assumed that was a guy from Dietpi who stumbled in, seeing as they are making imgs based on the FE there and can't find headers he figured he would ask in Armbian.
<c0rnelius>
Just my guess though.
slacker_HD has joined #armbian
slacker_HD has quit [Quit: Connection closed]
slacker_HD has joined #armbian
xoan725458 has joined #armbian
xoan72545 has quit [Ping timeout: 268 seconds]
xoan725458 is now known as xoan72545
<Armbian-Discord>
<Tonymac32> rockchip 5.10 = 🤮
<TRS-80>
lolwut?
<Armbian-Discord>
<MicroLinux (Salva)> By ancientware
<Armbian-Discord>
<Tonymac32> it's worse than that
Snuupy has quit [Quit: leaving]
Snuupy has joined #armbian
<TRS-80>
I thought they contributed to kernel a lot? Or was that in the before times?
<TRS-80>
I meant, was this 5.10 kernel from the before times.
<Armbian-Discord>
<Tonymac32> no, they did mainline stuff in their 4.4 days because Google required it
<Armbian-Discord>
<Tonymac32> for their Chromebook processors
<Armbian-Discord>
<Tonymac32> however their personal kernel is absolute shit
indy_ has joined #armbian
indy has quit [Ping timeout: 268 seconds]
<TRS-80>
I mean, aren't most of them?
cheakoirccloud has joined #armbian
indy_ has quit [Ping timeout: 268 seconds]
<Armbian-Discord>
<Tonymac32> in 4.4 it was terrible
<Armbian-Discord>
<Tonymac32> by their 5.10 abomination it is an inexcusable dumpster fire
TRS-80 has quit [Quit: WeeChat 3.0]
TRS-80 has joined #armbian
Fleck has quit [*.net *.split]
ced117 has quit [*.net *.split]
IgorPec has quit [*.net *.split]
invisiblek has quit [*.net *.split]
kcz has quit [*.net *.split]
tomreyn has quit [*.net *.split]
kcz has joined #armbian
invisiblek has joined #armbian
Fleck has joined #armbian
tomreyn has joined #armbian
indy has joined #armbian
Armbian-Discord has quit [*.net *.split]
blathijs has quit [*.net *.split]
TRS-80 has quit [Quit: WeeChat 3.0]
alekksander has joined #armbian
indy has quit [Ping timeout: 268 seconds]
indy has joined #armbian
rpardini has joined #armbian
slacker_HD has quit [Quit: Connection closed]
samythemany1 has joined #armbian
samythemany has quit [Ping timeout: 268 seconds]
xoan725450 has joined #armbian
xoan72545 has quit [Ping timeout: 252 seconds]
xoan725450 is now known as xoan72545
samythemany1 has quit [Remote host closed the connection]
samythemany1 has joined #armbian
samythemany1 has quit [Remote host closed the connection]
samythemany1 has joined #armbian
Lope has joined #armbian
<Lope>
hey folks has anyone managed to make a H2+ H3 H5 or H6 hardware accelerated AES VPN?
alekksander has quit [Ping timeout: 248 seconds]
alekksander has joined #armbian
<montjoie>
Lope: openvpn, ipsec or wireguard ?
<Lope>
montjoie, well, I want to use the H3's HW acceleration
<Lope>
I don't know if ipsec supports AES? I don't know anything about ipsec.
<Lope>
But Wireguard doesn't support AES
<Lope>
I'm busy setting up OpenVPN now for a test.
<montjoie>
H3 could only do AES (ipsec can do AES)
<montjoie>
openvpn is userspace, so you need AF_ALG (or cryptodev)
<Lope>
is IPsec something you can use to make a VPN with?
<Lope>
montjoie, thanks, I'll look up AF_ALG
<montjoie>
for me, IPSec is the origin of VPN
<montjoie>
but IPSEC IS DANGEROUS for you mind
<Lope>
So far I only found something about "engine aes-ni" or something like that, but that would be the intel AES HW accelerator, so that might not work on ARMv7
<montjoie>
Lope: using hw crypto from userspace bring a perf hit
<Lope>
montjoie, I don't mind a perf hit, I will test and see if it's adequate.
<Lope>
montjoie, do you know what to add to a openvpn conf file to make it use the ARMv7 HW AES accelerator?
<montjoie>
I am interested in feedback:)
<Lope>
I will give feedback for sure
<Lope>
I've got a basic VPN connected to a H5 SoC right now
<Lope>
I'm going to run an iperf now thru it.
<montjoie>
probably openssl already could use HW AES instruction
<Lope>
then will try changing config to use AES or whatever.
<Lope>
I'm testing with a static key at the moment.
<Lope>
I've only got H2+ H3 and H5 to test with (also A20 but it doesn't have much HW accel so not worth testing)
<montjoie>
A20 have AES hw
<Lope>
I've also got a RbPi 4 so I might test wireguard on it. Though I've already read online that it can do 870Mbit/s with no other load.
<Lope>
montjoie, well, it has some HW accel, but compare it to H3 and H5 it looks very inferior?
<montjoie>
perhaps your VPN use a cipher unsupported by the hw, like GCM ?
<montjoie>
or openssl isnt using the AF_ALG engine
<Lope>
montjoie, ok I changed from a TCP connection to UDP, it didn't improve speed. Then I specified cipher AES-256-CBC and now it's going faster now 112Mbit/s Still very slow compared to `cryptsetup benchmark --cipher aes-xts;`
pmp-p has joined #armbian
<Lope>
Getting this message. Cipher 'AES-256-GCM' mode not supported
<Lope>
I tried AES-128-CBC, it's the same speed as AES-256-CBC
<montjoie>
you cannot compare CBC and XTS (and futhermore VPN will use different buffer size than a LUKS/cryptsetup)
<montjoie>
Could you check /sys/kerne/debug/sun8i-ce/stats to check it is used ? (anyway for GCM, sun8i-ce does not support it)
xoan725456 has joined #armbian
xoan72545 has quit [Ping timeout: 248 seconds]
xoan725456 is now known as xoan72545
<Lope>
interestingly I was getting 112Mbit/s with OpenVPN AES-128-CBC and I tried cipher none, I got 142Mbit/s only. So I'm checking if setting the MTU improves it, then I'll probably test wireguard. But it's looking like this SBC is too slow to use as a VPN.
alekksander has quit [Ping timeout: 256 seconds]
<Lope>
While doing the test, 2 CPU cores peg at 100% load.
<montjoie>
increasing MTU could increase thoughput, bigger buffer so less crypto request
<Lope>
montjoie, yes.
<Lope>
there must be some IO issues, it only hits 61% while maxing out the board with just iperf at 410Mbit/s. So I've decided not to use this for a VPN/router. It's too slow.
<Lope>
I ran iperf from the board to my PC directly, without involving openvpn.
lemonzest has joined #armbian
alekksander has joined #armbian
indy has quit [Ping timeout: 256 seconds]
indy has joined #armbian
samythemany11 has joined #armbian
samythemany1 has quit [Ping timeout: 268 seconds]
stipa has quit [Read error: Connection reset by peer]
stipa_ has joined #armbian
stipa_ is now known as stipa
yang has joined #armbian
Armbian-Discord has joined #armbian
xoan725453 has joined #armbian
xoan72545 has quit [Ping timeout: 248 seconds]
xoan725453 is now known as xoan72545
samythemany11 has quit [Remote host closed the connection]