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 | Type 'help' for help | Logs: -> irc.armbian.com
The_Loko has quit [Quit: Leaving]
sunshavi has quit [Remote host closed the connection]
lanefu has quit [Quit: kernel update]
Unit193 has quit [Read error: Connection reset by peer]
Unit193 has joined #armbian
CrashTestDummy has joined #armbian
CrashTestDummy3 has quit [Ping timeout: 268 seconds]
CrashTestDummy2 has joined #armbian
CrashTestDummy has quit [Ping timeout: 244 seconds]
CrashTestDummy has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 252 seconds]
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #armbian
indy has quit [Read error: Connection reset by peer]
indy has joined #armbian
peterm6881 has joined #armbian
<peterm6881>
Morning all. If I was building an sbc from scratch whats the best suited, cheapest, most readily available and best documented / supported SoC for Armbian? What's the best compromise SoC between all those factors?
<buZz>
peterm6881: allwinner h3 is pretty available and documented and supported
stipa has quit [Quit: MOW MOW MOW YOUR MOWER]
wwilly has joined #armbian
wwilly has quit [Quit: Leaving]
wwilly has joined #armbian
plntyk has quit [Remote host closed the connection]
plntyk has joined #armbian
willmore has quit [Ping timeout: 268 seconds]
vegii has quit [Ping timeout: 272 seconds]
CrashTestDummy2 has joined #armbian
mnd999_ has joined #armbian
CrashTestDummy has quit [Ping timeout: 252 seconds]
<stipa>
all crap i have had with network is drivers
<stipa>
many drivers are like publicized as stable but that's far from it
<stipa>
maybe it's stable for devs who run it for 3 minutes but not so if you run it for 3 days
<stipa>
new stuff suffers alot of that effect
<stipa>
and years are passing by in hope someone will fix it
<stipa>
seemy like wuality of driver devs is declining
<stipa>
quality*
<stipa>
my network is like running on fumes
<stipa>
10 % of it's capacity
<stipa>
theoretical capacity*
<stipa>
and every update of the driver i'm like happy like a kid
<stipa>
it's finaly time, the driver has come, i'm going to have awesome speedz
<stipa>
awesome speedz my ass
<stipa>
lanefu: try to put it into 100 Mbit mode
<stipa>
maybe it's overheating in 1000 Mbit mode
<stipa>
they suck more power when set faster
<stipa>
just by idling
<lanefu>
stipa: nah its idling and it happens at the same time everyday
<stipa>
maybe the thing it's connected to via eth cable is sending some signals to it
<stipa>
agreements and stuff
<stipa>
maybe you could catch the packet tomorrow
<lanefu>
Nope pretty sure its hardware clock and chrony reconciling something and freaking out
<lanefu>
Allwinner has a reputation of spontaneous clock changes
<stipa>
hmm
<stipa>
you mean cpu freqency?
<stipa>
try static one
<stipa>
or is there some oscillator?
<stipa>
to wich everything is synced
<stipa>
which*
<lanefu>
nope. i mean real time clock
<lanefu>
sysgtem time
<stipa>
idk, could you monitor which app could trip that time at that moment of "freakout" ?
<lanefu>
i don't have a lot of logs.. the crons don't totaly align.. but i have logs of teh apps tha tfreaked out because of it
<lanefu>
and there'sa 30 minute tiem correction
<lanefu>
i'd have to attac ha serial console and log to find more info most likely
tonymac32 has joined #armbian
<stipa>
yeah, if that's the only way to do it why not
<stipa>
hope that's not some hardware black magic going on
<stipa>
not visible to the software
<lanefu>
cuz the sbc is in a case i my rack and is my like "headless workstation" so i dont want to dismantle
<lanefu>
i'm gonan try to recreate the issue on an an identical sbc
<stipa>
right right
<lanefu>
i've got another board with kernel 5.10.21-ish with 69 days of uptime
<stipa>
i have that kerenl too
<stipa>
on opi lite2
<stipa>
yeah, last stable one
<stipa>
i guess you should have the same bug on 5.10
<stipa>
but that 69 days uptime board doesn't spit that error?
<lanefu>
nope
<lanefu>
i had similar uptime on this board until i changed kernel
<lanefu>
both same sbc
<stipa>
so the kerne ldevs fucked something up
<stipa>
or maybe it's a hardware fault
<lanefu>
i'm suspicious of a kernel patch for H616 clock
<lanefu>
..but i havnet proven its applied to older kernel or not
<stipa>
hmmm, so H6 and H616 have the same clock hardware?
<stipa>
probably not if you're right
<jschwart>
hi all, might the latest tinkerboard (rk3288) updates be borked?
<jschwart>
I just did an upgrade and the result is booting to a kernel stacktrace
<stipa>
if it happens to someone else it could be
<stipa>
watch an eye to the forum
<stipa>
or even better, break the ice and make a post
lanefu has quit [Quit: break from computering..]
<jschwart>
yeah I don't know whether IRC or the forum is faster here, but I'll drop this in the forum too, thanks!
<stipa>
yeah, if it's fresh stuff it'll start popping when peeps do an update
<IgorPec>
nobody is working today ;)
<IgorPec>
so it will certainly not be fast
<jschwart>
yeah I'll try to copy some stuff from the backtrace and see
<jschwart>
in the past I managed to chroot mount into the root fs from another armbian install (with the broken installation SD in an extra SD card reader hooked up to USB) do chroot and then armbian-config to switch to another kernel
<jschwart>
maybe simply running apt update && apt upgrade would already work as well if a newer kernel would be released by then
<jschwart>
so I'm not too concerned on getting it back in shape, but it all starts with a report at least :)
<stipa>
let's hope your post won't be flagged as [invalid]
<jschwart>
it seems I'd best charge my camera so I can take a photo of the TV screen
<jschwart>
or maybe I actually have a way to take a screenshot through the TV itself...., let me check that :)
<stipa>
super hi res screenshot
<stipa>
TVs are almost computers nowadays
<jschwart>
yeah I can ssh into the tv
<stipa>
TV manufacturers will maybe make computers i nnear future
<jschwart>
it could use an armbian port ;)
<stipa>
sick
<stipa>
computers with tv cards and arm
<stipa>
decade ago it was funny seeing peeps using HD lcd TV's as monitors
<stipa>
like oversized monitor on a desk iwth super bix pixels
<stipa>
with super big*
<stipa>
now it's cool
<stipa>
early adopters
<jschwart>
yeah it's arm based indeed
<jschwart>
samsung tv from 2014
<jschwart>
Mali GPU too
<jschwart>
I rooted it with samygo
CrashTestDummy3 has joined #armbian
<jschwart>
and indeed have a screenshot now with the full output
CrashTestDummy2 has quit [Ping timeout: 240 seconds]
<IgorPec>
our tinkerboard for automated testing survived upgrade http://ix.io/3qtd
<IgorPec>
but is ofc headless
<jschwart>
hmm, but I can't ssh in either
<IgorPec>
well, hard to say.
<jschwart>
I can try rebooting again
diederik has quit [Quit: No Ping reply in 180 seconds.]
diederik has joined #armbian
<jschwart>
that worked
<jschwart>
now it fully boots up
salvaa has joined #armbian
salvaa has quit [Client Quit]
wwilly_ has joined #armbian
<jschwart>
IgorPec: you mention headless, but might it be useful to hook them up to a capture device for certain tests?
wwilly has quit [Ping timeout: 244 seconds]
<IgorPec>
this is what we have, boards are somewhere in a rack and having a remove power on/off and console is already a luxury
<IgorPec>
s/remove/remote
<ArmbianHelper>
IgorPec meant to say: this is what we have, boards are somewhere in a rack and having a remote power on/off and console is already a luxury
<jschwart>
ah yeah I can imagine a serial console is even more useful
<jschwart>
maybe at some point there will be cheap HDMI to USB capture devices that could be helpful
<[TheBug]>
I imagine if you really wanted you could buy a box of those cheap 1080p30 USB HDMI capture sticks and could tie them all to a single machine and connect HDMI to the devices and be able to us it kinda like pikvm
<[TheBug]>
s/us/use
<ArmbianHelper>
[TheBug] meant to say: I imagine if you really wanted you could buy a box of those cheap 1080p30 USB HDMI capture sticks and could tie them all to a single machine and connect HDMI to the devices and be able to use it kinda like pikvm
<[TheBug]>
probably wouldn't cost a whole lot but the time it would take to setup would likely be a glut
<[TheBug]>
since they were selling those usb sticks for like 5-15$
<[TheBug]>
and they are USB 2 if I recall
<[TheBug]>
so not like you need a fancy hub either
<[TheBug]>
unless you intend to use multiple at once I guess maybe
<IgorPec>
that is 20 usd + 16 + good usb hub
<IgorPec>
20 * 16
<jschwart>
ah yeah full blown kvm, I don't know what would be cheaper
<IgorPec>
i have 8 ch version and works quite well, also have that cheap hdmi grabber
<jschwart>
but in theory you could connect two boards to each other's USB in tandem
<jschwart>
to save on the USB hub :)
<IgorPec>
yeah right ;)
<IgorPec>
usb is crap without improvising ;)
<jschwart>
hehehe
<buZz>
do you guys have usbcondoms in your standard carry-along hw collection?
f476 has quit [Remote host closed the connection]
f476 has joined #armbian
f476 has quit [Remote host closed the connection]
f476 has joined #armbian
wwilly_ has quit [Ping timeout: 265 seconds]
Tables has joined #armbian
ikmaak has quit [Read error: Connection reset by peer]
ikmaak has joined #armbian
mnd999_ has quit [Ping timeout: 272 seconds]
Tables has quit [Ping timeout: 258 seconds]
peetah has joined #armbian
<peetah>
hello, I don't know if that is to be fixed from the armbian side, but just in case, it seems the regression described here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990072 also affects the 21.05.4 kernel compared to the 21.05.1 kernel, at least on my odroid C4.
<peetah>
as in the bug report, downgrading linux-image and linux-dtb packages also temporarily solves this issue
peterm6881 has quit [Remote host closed the connection]