Werner 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
<schwarz_Kat>
lanefu: on IRC earlier when I asked about wanting to try to restore the GPIO sysfs functionality to the orangepizeroplus.
<schwarz_Kat>
Unless I'm mistaken (newbie) the config used by orangepizeroplus is linux-sunxi64-current.config.
<schwarz_Kat>
At first I thought that the issue could be missing CONFIG_GPIO_SYSFS=y, but building with this didn't fix the issue.
<ArmbianHelper>
^ Error retrieving title. Check the log for more details.
<schwarz_Kat>
Then... **I found a build that I did a couple of months back that was kernel 5.15.25 and had a boot config-5.15.25-sunxi64 that matched the current build**.
<schwarz_Kat>
So I don't think that the issue is the kernel config. I tried to disect the differences between the two builds, but the one that I'm comparing with has had a whole lot of extra stuff installed, making it difficult. I couldn't find any significant differences in modules. Device tree on boot matches.
<schwarz_Kat>
I then tried to create a branch with head on an earlier commit. I wasn't able to go back far enough, though I've only recently started using git, so I'm still pretty clueless.
<schwarz_Kat>
I then thought that I could try and look at differences in patches between legacy and current... not even vaguely similar seems to have been completely reworked.
<schwarz_Kat>
Anyone able to offer some hints at what I should try next?
califax has quit [Remote host closed the connection]
califax has joined #armbian
<Armbian-Discord>
<lanefu> Is there an device tree overlay that needs to be enable via armbian-config to activate gpio?
<Armbian-Discord>
<RichN> what are you enabling 1 wire
<Armbian-Discord>
<RichN> you have to use the armbian-config > system > Hardware
<Armbian-Discord>
<RichN> and enable the 1 wire and maybe i2c
norwich_ has joined #armbian
norwich has quit [Ping timeout: 240 seconds]
norwich_ is now known as norwich
<Armbian-Discord>
<lanefu> They just want standard gpio over sysfs
<schwarz_Kat>
lanefu: I don't see a dto that would do that. In the 5.15.25 board that has the sysfs filesystem, there are no overlays set for that in armbianEnv.txt
TRS-80 has quit [Quit: WeeChat 3.0]
shoragan has quit [Ping timeout: 240 seconds]
<schwarz_Kat>
RichN: No not 1 wire. GPIO sysfs. Deprecated in the kernel, but still very much in use, and until now available on this board. I suspect that it dropped off with the latest version changes. It's available on a build that I did on what was then the edge build just before the change. Now it is only available on the legacy build. I'm trying to understand what has dropped off.
<lanefu>
So do you see the gpio flcjip in sysfs
<lanefu>
You do have to enable / export the pins manually they won't show up on their own
<schwarz_Kat>
lanefu: the main symptom is no /sys/class/gpio at all so no enable / export.
<Armbian-Discord>
<lanefu> Bummer. Yeah sorry I'm not closer to stuff to look around
<Armbian-Discord>
<lanefu> armbian monitor -m
<schwarz_Kat>
I will have to look at that tomorrow.
<schwarz_Kat>
Also going to try to find the device(s) and drivers on a working system. WML.
xoan8 has joined #armbian
xoan has quit [Ping timeout: 272 seconds]
xoan8 is now known as xoan
samythemany1 has joined #armbian
samythemany11 has joined #armbian
samythemany has quit [Ping timeout: 240 seconds]
samythemany1 has quit [Ping timeout: 240 seconds]
adeepv has joined #armbian
schwarz_Kat has left #armbian [Offline]
xoan5 has joined #armbian
<Armbian-Discord>
<Queen Fiona> Hey, am I correct in hearing the Orange Pi PC is no longer CSC?
<Armbian-Discord>
<Queen Fiona> Also, what's new in the 5.17 kernel where Armbian boards are concerned?
xoan has quit [Ping timeout: 260 seconds]
xoan5 is now known as xoan
archetech has joined #armbian
smcavoy has quit [Read error: Connection reset by peer]
<ArmbianHelper>
^ Fixing deboostrap fail due to too old ca-certificate package by igorpecovnik · Pull Request #3624 · armbian/build · GitHub
<IgorPec>
need review
archetech has quit [Quit: Konversation terminated!]
<Armbian-Discord>
<niccodemi> I am trying to compile image for Bananpi M1 board which has broken sd card detect pin. I added line CONFIG_MMC0_CD_PIN="" to the end of "Bananapi_defconfig" and created patch. When building image I get following warning "[\e[33mu\e0m u-boot-sunxi-current.patch failed wrn". Any idea what is the issue?
archetech_n2 has joined #armbian
SallyAhaj has quit [Remote host closed the connection]
<Armbian-Discord>
<rpardini> IgorPec: taking a look at AR-1140 (ca-certificate stuff on focal)
<ArmbianHelper>
AR-1140 [Bug] "Deboostrap fails due to too old ca-certificate package" reported by Igor Pecovnik at 2022-04-02. Status: In Progress
<Armbian-Discord>
<rpardini> it is a bit wierd, considering ca-certificates is not in restricted...
<IgorPec>
ha, strange. but this fix helps
<Armbian-Discord>
<rpardini> version in focal and focal-updates is actually the same
<Armbian-Discord>
<rpardini> my guess is error is random, 2 cert paths, one fails, adding restricted or not probably does not make a difference, just good/bad luck during the tries... 🤔
<IgorPec>
hm, tl;dr; what is the problem?
<IgorPec>
openssl version?
<Armbian-Discord>
<rpardini> dunno how/what is serving imola's 443 port... but I guess it is using old cacert or intermediaries
<Armbian-Discord>
<rpardini> cert itself is correct, but intermediaries not
<Armbian-Discord>
<rpardini> someone will for sure correct me
<IgorPec>
this is vm machine here at my server, i have setup this www some time ago
<IgorPec>
its pure ubuntu 20.04 and that python for auto cert renew
<Armbian-Discord>
<rpardini> certbot maybe?
<IgorPec>
yes
<IgorPec>
i think
<IgorPec>
there are two subdomains
<IgorPec>
what would be causing this. don't understand quite
<Armbian-Discord>
<rpardini> I am investigating a bit more
<Armbian-Discord>
<rpardini> comparing to some LE setups I have
<Armbian-Discord>
<rpardini> actually my setups are exactly the same 😐 so not a server problem indeed
<Armbian-Discord>
<rpardini> might be openssl version related
<Armbian-Discord>
<rpardini> (on the client/debootstrap)
<IgorPec>
then perhaps this is taken from restricted?
<Armbian-Discord>
<rpardini> still does not explain why adding restricted solves it though 😉
<Armbian-Discord>
<rpardini> lemme check
<IgorPec>
i have 10/10 runs with added restricted
<IgorPec>
always works, without always fail ;)
<Armbian-Discord>
<rpardini> yeah, gotta be libssl or something related
<Armbian-Discord>
<rpardini> what led you to try to add restricted in the first place? not a random try I guess
<IgorPec>
i saw after deebstrap finishes packages are getting updated
<IgorPec>
and this was one of the tries, more like why this is not there in first place
<IgorPec>
restricted repo we anyway have
<Armbian-Discord>
<rpardini> hmm, indeed, we add restricted afterwards anyway
<IgorPec>
and i ran into this problem on the machine
<IgorPec>
if you install some older image, you can't update from armbian repo without updatoing ca-certificates first
<IgorPec>
if this tells you anything
<Armbian-Discord>
<rpardini> approved PR, "why" is a bit over my head but makes sense.
<Armbian-Discord>
<rpardini> probably has to do with ca-certificates (list of certs) vs openssl (combining list of certs into big bundle during install)
<IgorPec>
probably.
<Armbian-Discord>
<IgorPec> btw, i have fixed that repository making in with github pages
<Armbian-Discord>
<rpardini> ahn, I had forgot about that with vacations (good sign)
<Armbian-Discord>
<rpardini> what was the problem in the end? I couldn't for the life of me find it
<Armbian-Discord>
<IgorPec> just wrong variable / secret name
<Armbian-Discord>
<rpardini> damn.
<Armbian-Discord>
<IgorPec> works now, update repo on code change. now in monday i have a meeting to start moving that armbian-config
<Armbian-Discord>
<rpardini> ahn ok!! found it, wrong name when passing $secret to crazymax's thingy
<Armbian-Discord>
<rpardini> damned that flew very low on my radar
<Armbian-Discord>
<IgorPec> this restricted hack works for me, but not in CI
<Armbian-Discord>
<rpardini> lemme build a focal see if I can reproduce
<Armbian-Discord>
<IgorPec> one possible relation is our redirector
<Armbian-Discord>
<IgorPec> there are some changes
<Armbian-Discord>
<rpardini> yeah, unlikely but could be, if redirecting randomly to something with a broken cert
<Armbian-Discord>
<IgorPec> testing now
<Armbian-Discord>
<rpardini> those PPA's, they come from BUILD_DESKTOP=yes I guess?
<Armbian-Discord>
<rpardini> btw great stuff with nvidia and chrome for amd64 desktops 👍
<Armbian-Discord>
<IgorPec> yes, also probably would be nice to add amd drivers
<Armbian-Discord>
<rpardini> we've already the open source ones and firmware in the -full version
<Armbian-Discord>
<rpardini> for amdgpu
<Armbian-Discord>
<IgorPec> build desktop yes are some, just one is on cli but just jammy / bullseye
<Armbian-Discord>
<IgorPec> aha ok
<Armbian-Discord>
<rpardini> I did for the Phythium a few months ago, don't remember if I pushed -full firmware though
<Armbian-Discord>
<rpardini> did yes.
<Armbian-Discord>
<rpardini> I've a radeon and works perfect out of the box first-boot
<Armbian-Discord>
<rpardini> nvidia used to require the dkms, but now you fixed that too 😉
<Armbian-Discord>
<IgorPec> i only have one nvidia here in the workstation
<Armbian-Discord>
<IgorPec> have to move to armbian one day 😉
<Armbian-Discord>
<rpardini> amd64 really helps with with userland development even for arm64
<Armbian-Discord>
<rpardini> I come up with a scheme useing qemu and pci passthrough
alekksander has quit [Ping timeout: 246 seconds]
<Armbian-Discord>
<rpardini> build amd64 image, boot it in qemu passing trhough an USB controller via pci passthrough
<Armbian-Discord>
<IgorPec> for gaming purposes ?
<stipa>
for userland dev
<Armbian-Discord>
<rpardini> ahn for gaming I do too, pci-e passthrough of the radeon, but guest is Windows
<Armbian-Discord>
<rpardini> (host is Armbian amd64 though so it counts)
<Armbian-Discord>
<IgorPec> yes that
<stipa>
what about those 3K ARM workstations, is that going to be supported ?
<stipa>
3K $
<IgorPec>
it probably just works, but no fine tunning
<stipa>
i see they always come and go
<IgorPec>
nobody send us any
<stipa>
may they expect that you'll buy some
<Armbian-Discord>
<rpardini> I've hearsay reports of it working on 128-core Amperes
<Armbian-Discord>
<rpardini> bare-metal
<Armbian-Discord>
<rpardini> I myself have no access to any yet
<IgorPec>
lanefu played something with that afaik
<IgorPec>
i think we have some arm server somewhere
<IgorPec>
but not 128c, something less
<stipa>
maybe 32
<Armbian-Discord>
<rpardini> someone reached out a time ago with good results on Altra Max, but when I asked for evidence/neofetch they disappeared
<stipa>
heh
<Armbian-Discord>
<rpardini> really if the boards uses decent UEFI (Tianocore / edk2) as most does it should just work.
<Armbian-Discord>
<rpardini> only board I've heard of problems with unfortunately was the SolidRun one
<stipa>
it's hard to tell without an access to a server like that, maybe it's mainline
<Armbian-Discord>
<rpardini> but that is 16x A-76
<Armbian-Discord>
<rpardini> they promised to send me a board to investigate, but it seems they're really 100% out of anything to sell much less give away
<IgorPec>
i heard they can't lead anything
<IgorPec>
but that's 6m old info
<stipa>
low interest probably
<IgorPec>
a combinatoion probably
<Armbian-Discord>
<rpardini> 4x 10Gbit SFP ports very much interest me, and others, but they seem to have supply problems
<Armbian-Discord>
<rpardini> as most everyone else.
<stipa>
yeah, but if the interest is so low i have no idea how they can even finance a prototype
<Armbian-Discord>
<rpardini> yeah. so right now my validation is still VMs. AWS Graviton2, OCI's Ampere all work. One day I might shell a few bucks to try on a bare-metal AWS Graviton2...
<Armbian-Discord>
<rpardini> stipa: ha, found the "3K" you mention, is rack version of SolidRun Honeycomb
<Armbian-Discord>
<rpardini> literally USD 3000
<Armbian-Discord>
<rpardini> so it's two of the honeycomb squashed together (2x 16-core A76)
<Armbian-Discord>
<rpardini> I guess problems would be exactly the same, requires patches to both kernel and userspace (libc!) to work
<ArmbianHelper>
^ build/general.sh at master · armbian/build · GitHub
<Armbian-Discord>
<rpardini> so redirector is sending http -> https in this case
<Armbian-Discord>
<IgorPec> correct
<Armbian-Discord>
<rpardini> which I guess it shouldn't to begin with...?
<Armbian-Discord>
<IgorPec> did you try with hard coded values to fixed host?
<Armbian-Discord>
<IgorPec> to bypass redirector
<Armbian-Discord>
<rpardini> gonna hardcode imola there now
<Armbian-Discord>
<rpardini> bypassed, but worked. rebuilding rootfs cache now
<Armbian-Discord>
<rpardini> bingo reproduced
<Armbian-Discord>
<rpardini> Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: ::1 3142]
<Armbian-Discord>
<rpardini> so it is only during rootfs cache rebuild
<Armbian-Discord>
<IgorPec> what is here different?
<Armbian-Discord>
<rpardini> nah, I'm an idiot.
<Armbian-Discord>
<rpardini> of course if I had previous working cache, then it would still work
<Armbian-Discord>
<IgorPec> yep 😉
<Armbian-Discord>
<rpardini> now investigating why this breaks now
<Armbian-Discord>
<rpardini> yeah, during debootstrap it's Retrieving ca-certificates 20190110ubuntu1
<Armbian-Discord>
<rpardini> which is ancient
<Armbian-Discord>
<rpardini> updated one is in security repo
<Armbian-Discord>
<rpardini> so bug was there for a decade
<Armbian-Discord>
<rpardini> redirector now sent http to https, and made it manifest
<Armbian-Discord>
<IgorPec> yeah, that is root cause, now what to do?
<Armbian-Discord>
<rpardini> we'd need to split this, do apt update+upgrade separately/before adding all the other sources
<Armbian-Discord>
<rpardini> so that security gets added and upgraded, ca-certificates fixed, then we add the other repos
<ArmbianHelper>
^ build/general.sh at master · armbian/build · GitHub
<Armbian-Discord>
<rpardini> that is fixed to http://
<Armbian-Discord>
<rpardini> but we're running into TLS cert trouble...
<Armbian-Discord>
<rpardini> not always
<Armbian-Discord>
<cats> I'm wondering if certain mirrors force https
<Armbian-Discord>
<cats> I can detect that and kick them out of the pool
<Armbian-Discord>
<rpardini> so it's a bit hard to pinpoint, but it seems imola was one http to https response
<Armbian-Discord>
<rpardini> also: if http to https response, we lose apt-cacher-ng cache's effectiveness
<Armbian-Discord>
<rpardini> hmm. by force https you mean the mirrors themselves redirect to https, not the redirector? 🤔
<Armbian-Discord>
<rpardini> goes testing again
<Armbian-Discord>
<cats> Yup, the mirrors themselves will
<Armbian-Discord>
<cats> the redirector passes through the scheme
<Armbian-Discord>
<rpardini> that is not the case, at least with imola; that keeps whatever I send it (by hardcoding / skipping redirector)
<Armbian-Discord>
<cats> hmmm
<Armbian-Discord>
<rpardini> I myself don't get redirected to imola... was happening to Igor
<Armbian-Discord>
<rpardini> but also in CI
<Armbian-Discord>
<rpardini> sorry for lack of evidence, should have collected a curl
<Armbian-Discord>
<cats> it's fine, I'm looking into potential edge cases
<Armbian-Discord>
<cats> the new redirector was meant to fix the inverse problem lol
<Armbian-Discord>
<rpardini> yeah, that's what I thought too
<Armbian-Discord>
<cats> is it only appearing when it's used by apt?
<Armbian-Discord>
<rpardini> yeah. but the symptom is a very far away, a TLS cert error due to ancient ca-certificates
<Armbian-Discord>
<rpardini> only on ancient focal and right after initial debootstrap, before first apt update
<Armbian-Discord>
<cats> I'm running the build script (if that'll reproduce it?) and I'll see if I can get the output of the packages
<Armbian-Discord>
<rpardini> so quite intricate, but the point is: it was supposed to be http and thus be a non-problem
<Armbian-Discord>
<cats> actually, would you be comfortable sharing your IP address in DM? I could probably check the logs to see which urls it hit and try to replicate it
<Armbian-Discord>
<rpardini> yeah but mine works!
<Armbian-Discord>
<rpardini> it's Igor's 😉 he's "physically moving things around" I think
<Armbian-Discord>
<cats> ahhh
<Armbian-Discord>
<rpardini> I'm gonna it now
<Armbian-Discord>
<rpardini> Ahn!
<Armbian-Discord>
<rpardini> it might be BETA or not too!
<Armbian-Discord>
<rpardini> (Igor uses that stuff, I don't, normally, unless trying to reproduce Igor)
<Armbian-Discord>
<cats> Igor had the pastebin earlier which is confirmed not working, perfect
<Armbian-Discord>
<cats> lol, VM I'm trying to build it on ran out of space, oops
<Armbian-Discord>
<rpardini> I just did a run with beta that worked too Get:1 http://beta.armbian.com focal/main amd64 linux-image-current-x86 amd64 22.05.0-trunk.0020 [69.2 MB]
<ArmbianHelper>
^ armbian storage
<Armbian-Discord>
<cats> beta is still using the old redirector
<Armbian-Discord>
<cats> perhaps next time we'll start with beta and archive lol
<Armbian-Discord>
<rpardini> I'm trying both...
<Armbian-Discord>
<rpardini> that desktop build is a monster though
<Armbian-Discord>
<cats> yeah, I gave my VM 64GB more space through some dirty fdisk editing lol
<Armbian-Discord>
<cats> I didn't feel like mounting a live cd to resize it
<Armbian-Discord>
<rpardini> eh. I've gotta one day deliver my ready-to-build VM image
<Armbian-Discord>
<rpardini> I made it work once, inception mode and all
<Armbian-Discord>
<cats> I haven't run into any issues yet
<Armbian-Discord>
<cats> just unpacked all the packages
<ArmbianHelper>
^ tyler/armbian-router: A simple http router for apt downloads based on GeoIP - armbian-router - Gitea: Git with a cup of tea
alekksander has quit [Quit: Konversation terminated!]
<Armbian-Discord>
<rpardini> nice stuff, I didn't know any of this existed
<Armbian-Discord>
<rpardini> armbian is infinite fun in all areas
<Armbian-Discord>
<cats> Yeah, this code is a bit more gross but it does geoip location redirection, not just country/continent
<Armbian-Discord>
<cats> So it takes the top x servers, balances requests to them based on weighting
<Armbian-Discord>
<cats> (so in theory we could prioritize better performing servers/servers with more capacity if there's a bottleneck at any point)
<Armbian-Discord>
<cats> and also live monitoring of statuses, so we shouldn't have any dead mirrors sitting in there for more than 60 seconds
<Armbian-Discord>
<rpardini> nice. so this listens http, some nginx in front terminates tls and proxies to it, X-Forwarded stuff et al?
<Armbian-Discord>
<cats> Yup
<Armbian-Discord>
<IgorPec> tl; dr; my workaround still needed?
<Armbian-Discord>
<cats> the imola fix yes
<Armbian-Discord>
<cats> tl;dr is that we need to make sure no mirrors use forced https redirects, but I've added monitoring for that on the redirector to kick those out of the pool
<Armbian-Discord>
<IgorPec> i can disable forced https redirect
<Armbian-Discord>
<cats> yup, mirrors will need to have it disabled sadly
<Armbian-Discord>
<cats> while forced https is good for security, it breaks http downloads for mirrors to handle that
<Armbian-Discord>
<rpardini> yeah, https negates the local/net cache we use, which is a proxy
<Armbian-Discord>
<cats> if you're forcing your build script to use a mirror, make sure it's http:// and not https:// as well
<Armbian-Discord>
<rpardini> yeah http:// is forced there since forever, it's hardcoded
<Armbian-Discord>
<rpardini> can't change it
<Armbian-Discord>
<cats> if it's a different mirror than default, that is
<Armbian-Discord>
<rpardini> it's required for the proxy to be effective
<Armbian-Discord>
<cats> idk if Igor has a local redirect to force build scripts to use his local setup
<Armbian-Discord>
<rpardini> (we've apt-cacher-ng proxy for builds)
<Armbian-Discord>
<rpardini> so in the end if https is used, cache is skipped and BW usage skyrockets
<Armbian-Discord>
<cats> makes sense
<Armbian-Discord>
<cats> when you're building 50 images it adds up lol
<Armbian-Discord>
<rpardini> I'm building 50 images per hour or more when working on this
<Armbian-Discord>
<cats> dang
<Armbian-Discord>
<rpardini> a CI run must build, dunno, 200 images
<Armbian-Discord>
<rpardini> Igor will know
<Armbian-Discord>
<IgorPec> yes, i do have
<Armbian-Discord>
<IgorPec> forcing local mirror to fasten things
<Armbian-Discord>
<rpardini> anyway it was Igor's own fault who called you here, ran away, fixed it sneakly and now is back laughing at me
<Armbian-Discord>
<cats> hahahaha
<Armbian-Discord>
<rpardini> 😄
<Armbian-Discord>
<rpardini> was fun we had a nice chat/debug session so thanks! 😄
<Armbian-Discord>
<IgorPec> yeah
<Armbian-Discord>
<cats> :twoboldSip:
<Armbian-Discord>
<lanefu> LOL
<Armbian-Discord>
<IgorPec> i have disabled https redirection on imola