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 feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
xalius has quit [Quit: Leaving]
archetech has quit [Quit: Konversation terminated!]
Flecks has joined #armbian
Fleck has quit [Ping timeout: 264 seconds]
<ArmbianTwitter> @cd1086 (suebo@ヤフオク禁止令解除): Enable g_serial USB OTG console Orange Pi on Armbian https://t.co/TI9T8oLp2p https://tinyurl.com/yez3y67b (7s ago)
lanefu has quit [Quit: WeeChat 3.2-dev]
chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #armbian
lanefu has joined #armbian
chewitt_ is now known as chewitt
attah has quit [Ping timeout: 264 seconds]
attah_ has joined #armbian
attah_ is now known as attah
jock has joined #armbian
<jock> Morning
wwilly has joined #armbian
lio_ has joined #armbian
e3ef13f4ff44 has joined #armbian
<e3ef13f4ff44> hello there
Toasty has joined #armbian
CrashTestDummy has quit [Quit: Leaving]
CrashTestDummy has joined #armbian
CrashTestDummy has quit [Client Quit]
CrashTestDummy has joined #armbian
CrashTestDummy has quit [Client Quit]
CrashTestDummy has joined #armbian
CrashTestDummy has quit [Read error: Connection reset by peer]
CrashTestDummy has joined #armbian
xalius has joined #armbian
xalius has quit [Changing host]
xalius has joined #armbian
bashrc has joined #armbian
wwilly_ has joined #armbian
wwilly has quit [Ping timeout: 268 seconds]
wwilly_ has quit [Quit: Leaving]
wwilly has joined #armbian
wwilly has quit [Client Quit]
wwilly has joined #armbian
wwilly has quit [Ping timeout: 268 seconds]
wwilly has joined #armbian
lio__ has joined #armbian
jock has quit [Ping timeout: 272 seconds]
wwilly has quit [Remote host closed the connection]
lio_ has quit [Ping timeout: 264 seconds]
wwilly has joined #armbian
lio_ has joined #armbian
jock has joined #armbian
wwilly has quit [Ping timeout: 264 seconds]
lio__ has quit [Ping timeout: 264 seconds]
wwilly has joined #armbian
lio__ has joined #armbian
lio_ has quit [Ping timeout: 272 seconds]
lio__ has quit [Quit: leaving]
wwilly_ has joined #armbian
wwilly has quit [Ping timeout: 272 seconds]
iav has joined #armbian
jock has quit [Ping timeout: 268 seconds]
kcz has quit [Quit: kcz]
kcz has joined #armbian
wwilly__ has joined #armbian
_whitelogger has joined #armbian
Fleck has joined #armbian
wwilly_ has quit [Ping timeout: 268 seconds]
Flecks has quit [Ping timeout: 268 seconds]
lanefu has quit [Ping timeout: 268 seconds]
lanefu-er has joined #armbian
flyback has quit [Ping timeout: 268 seconds]
iav_ has joined #armbian
iav has quit [Ping timeout: 268 seconds]
flyback has joined #armbian
bashrc has quit [*.net *.split]
attah has quit [*.net *.split]
bashrc has joined #armbian
attah has joined #armbian
jock has joined #armbian
Tenkawa has joined #armbian
nekomancer[m] has joined #armbian
<nekomancer[m]> woooh! :) at last.
* iav_ at #armbian:libera.chat
iav_ has quit []
iav has joined #armbian
<iav> too early to leave: need to compare logs in irc and matrix.
jock has quit [Quit: Leaving]
martinayotte49 has joined #armbian
martinayotte49 has quit [Client Quit]
<ArmbianTwitter> @youngyukari (Makusu 🌸): @armbian @kobol_io @armbian the issue ended up being in the build process of the 21.05.2 release that included a wrong file in the helios54 bsp package (details in the thread above). Should I open a github ticket? https://tinyurl.com/yzcwvkya (15s ago)
halfa has joined #armbian
<halfa> hello
<halfa> I was seeking guidance on how to signal an issue with a package in 21.05.2 (armbian-bsp-cli-helios64_21.05.2 was build with a wrong file)
<ArmbianTwitter> @seeteegee (Chris McGee): I have set up my #pinecube as an indoor security camera with armbian/motion and a script that uploads the videos when there's motion to my private matrix server (offsite backup, notifications, access control). It's working pretty well so far. https://tinyurl.com/yfs4n4c6 (7s ago)
<stipa> wb nekomancer[m]
<nekomancer[m]> stipa: glad to be there
<stipa> halfa: try in forum section that deals with helios or it's soc maybe
<halfa> I'm willing to debug this but I'm very unfamiliar with the armbian/build system
<stipa> cool cool, stick around, maybe someone else can help
<stipa> there are some peeps with helios here
<halfa> currently installing a debian VM so I can compile 21.05.2 and see what happened
<halfa> it's not really about my install really but more about the less savy users that will upgrade and loose their cooling system
<stipa> there's always some patching going on
<stipa> things break
<halfa> indeed
<stipa> halfa: also if you didn't see there's howto build armbian here https://docs.armbian.com/Developer-Guide_Build-Preparation/
<stipa> with ubuntu
<halfa> I wasn't sure if that was only the kernal or also the bsp packages?
<halfa> but will read in details, thanks for the pointer, I think I crossed it in the past and somehow forgot it
<stipa> you can choose some drivers
<stipa> in build process
<stipa> script guides you
<stipa> if it's something on lower layers than try to ask around in #armbian-devel
<halfa> hummm interestingly my system says I'm on 21.05.2 but https://armbian.hosthatch.com/dl/helios64/archive/ only lists 21.05.1 for focal
<halfa> those are supposed to be nighly if I understand correclty
<nekomancer[m]> <halfa "stipa: https://forum.armbian.com"> good research
iav has quit []
Tenkawa has quit [Quit: Leaving.]
willmore has quit [Ping timeout: 268 seconds]
willmore has joined #armbian
maknho has joined #armbian
<nekomancer[m]> again strange effects with docker.
<nekomancer[m]> host x64 ubuntu focal, target release hirsute, building with docker, failure — chroot can't do second stage, looks like old already workarounded in scripts bug.
<nekomancer[m]> during rootfs building
<nekomancer[m]> 2 days ago it works.
<c0rnelius> Sounds like a qemu error I came across not to long ago. Ubuntu I believe pushed an update for that and well... its broken.
<c0rnelius> On the host this is how I fixed it `docker run --rm --privileged multiarch/qemu-user-static --reset -p yes`
maknho has quit [Quit: WeeChat 2.3]
maknho has joined #armbian
maknho has quit [Remote host closed the connection]
maknho has joined #armbian
<nekomancer[m]> once?
maknho has quit [Quit: WeeChat 2.3]
<c0rnelius> I only did it once.
maknho has joined #armbian
<nekomancer[m]> try to do it
maknho has quit [Client Quit]
maknho has joined #armbian
maknho has quit [Client Quit]
maknho has joined #armbian
<nekomancer[m]> it's a magic! it work!!! c0rnelius , you are gorgeous!
maknho has quit [Remote host closed the connection]
<c0rnelius> nekomancer[m]: yw
maknho has joined #armbian
maknho has quit [Remote host closed the connection]
maknho has joined #armbian
maknho has quit [Remote host closed the connection]
maknho has joined #armbian
maknho has quit [Remote host closed the connection]
maknho has joined #armbian
wwilly__ has quit [Ping timeout: 264 seconds]
halfa has quit [Ping timeout: 265 seconds]
<[TheBug]> Ugh
<[TheBug]> messing with a pair of USB 3.0 2.6Gbit r8156b nics
<[TheBug]> I can breing them up on two boards
<[TheBug]> see they link at 2.5Gbit*
<[TheBug]> but as soon as traffic is passed over it for example by iperf
<[TheBug]> interface immediatly stops responding
<[TheBug]> [ 4] local 192.168.8.3 port 60050 connected with 192.168.8.2 port 5001
<[TheBug]> [ ID] Interval Transfer Bandwidth
<[TheBug]> [ 5] local 192.168.8.3 port 5001 connected with 192.168.8.2 port 39932
<[TheBug]> [ 4] 0.0- 1.0 sec 116 MBytes 116 MBytes/sec
<[TheBug]> [ 5] 0.0- 1.0 sec 47.1 MBytes 47.1 MBytes/sec
<[TheBug]> [ 4] 1.0- 2.0 sec 153 MBytes 153 MBytes/sec
<[TheBug]> [ 5] 1.0- 2.0 sec 46.0 MBytes 46.0 MBytes/sec
<[TheBug]> [ 4] 2.0- 3.0 sec 74.0 MBytes 74.0 MBytes/sec
<[TheBug]> [ 5] 2.0- 3.0 sec 25.4 MBytes 25.4 MBytes/sec
<[TheBug]> [ 4] 3.0- 4.0 sec 0.06 MBytes 0.06 MBytes/sec
<[TheBug]> just 0
<[TheBug]> Speed: 2500Mb/s
<[TheBug]> Duplex: Full
<[TheBug]> its too weird
<[TheBug]> starts out like its gonna work then just pukes
<[TheBug]> nothing in dmesg showing an actual issue
lvrp16 has quit [Read error: Connection reset by peer]
lvrp16 has joined #armbian
CrashTestDummy2 has joined #armbian
CrashTestDummy has quit [Ping timeout: 264 seconds]
bashrc has quit [Ping timeout: 268 seconds]
<lanefu-er> [TheBug]: 2.5 gb is the future
<c0rnelius> try connecting it to a powered hub. could be overheating?
Toasty has quit [Ping timeout: 264 seconds]
<lanefu-er> Good idea
maknho has quit [Ping timeout: 272 seconds]
<[TheBug]> is in a powered hub
<[TheBug]> something with this is weird
maknho has joined #armbian
<[TheBug]> I think its a driver issue
<[TheBug]> but can't nail it down
<[TheBug]> I am connecting adapters to each other cross over direct from one RockPI 4c to another
<[TheBug]> when it 'works' it will transfer only 1gigabit and it will only do it in one connection
<[TheBug]> it seems to lose negotiation
<[TheBug]> honestly, I have a 2.5Gbit switch coming tomorrow, may just wait and test more then
<[TheBug]> but guessing I may have to have a recompile with newer drivers or something
<c0rnelius> does it work as expected on a x86?
<[TheBug]> no idea
<[TheBug]> wouldn't be my use case anyways
<c0rnelius> Should try it though. Might give you more insight?
<c0rnelius> No harm in testing it.
<[TheBug]> hmm
<[TheBug]> starting to wonder if I have a bad adapter
<[TheBug]> one seems to work pushing data in one direction but anytime data goes the other it craps
<[TheBug]> for no reason
<[TheBug]> hmm
<[TheBug]> anyways time for some food will mess more after dinner I guess
<c0rnelius> What SoC(s)?
<[TheBug]> rk3399 on both ends
<[TheBug]> RockPi 4c
<[TheBug]> tested with and without powere usb 3.0 hub on both sides
<[TheBug]> that doesn't seem to make any change
<[TheBug]> though also wondering if the driver has crashed on the one
<[TheBug]> gonna try rebooting it after bit
<[TheBug]> see if any changes
<[TheBug]> anyways bbiab
<[TheBug]> (also wondering if its an old shitty driver)
<c0rnelius> Could be... Maybe the the interface needs patching on a kernel level to support such a load?
<c0rnelius> USB3 is a bit shifty on these arm boards.
<[TheBug]> could be
<[TheBug]> but no issue with tons of usb to sata traffic on same port
<[TheBug]> so would be a bit weird all sudden this has issue
<[TheBug]> but weirder things have happener
<c0rnelius> True.
<[TheBug]> whats odd is it comes up and links at 2.5Gbit pretend to work in one direction, fails the other no matter what
<[TheBug]> and when it fails its even more weird cause connection is lost physically between the adapters
<[TheBug]> not that you can visually see
<[TheBug]> it just stops responding till I phyiscally disconnect and reconnect the wire
<c0rnelius> To me that seems like a heating problem.
<[TheBug]> like link light on the adapter never changes
<c0rnelius> Like it just takes a shit and dies on you because ur pushing it.
<[TheBug]> lol thing is both are in AC cooled room and one specifically has air blowing on it passively
<[TheBug]> well it doesn't even get above 1gbit when it works
<[TheBug]> best reult
<[TheBug]> result:
<[TheBug]> er
<[TheBug]> was 80M/sec one way
<[TheBug]> looks like
<[TheBug]> [ 3] 0.0- 1.0 sec 78.4 MBytes 78.4 MBytes/sec
<[TheBug]> [ 3] 2.0- 3.0 sec 84.8 MBytes 84.8 MBytes/sec
<[TheBug]> [ 3] 1.0- 2.0 sec 81.9 MBytes 81.9 MBytes/sec
<[TheBug]> [ 3] 3.0- 4.0 sec 90.4 MBytes 90.4 MBytes/sec
<[TheBug]> [ 3] 4.0- 5.0 sec 84.9 MBytes 84.9 MBytes/sec
<[TheBug]> [ 3] 0.0- 5.0 sec 420 MBytes 83.9 MBytes/sec
<[TheBug]> thats best result and in only direction data will pass without it 'failing' immediately
<c0rnelius> yea thats not very good
<[TheBug]> and
<[TheBug]> even the one that works
<[TheBug]> if you go 30 seconds
<[TheBug]> [ 3] 16.0-17.0 sec 87.1 MBytes 87.1 MBytes/sec
<[TheBug]> [ 3] 19.0-20.0 sec 0.06 MBytes 0.06 MBytes/sec
<[TheBug]> [ 3] 18.0-19.0 sec 47.0 MBytes 47.0 MBytes/sec
<[TheBug]> [ 3] 20.0-21.0 sec 0.00 MBytes 0.00 MBytes/sec
<[TheBug]> [ 3] 17.0-18.0 sec 85.6 MBytes 85.6 MBytes/sec
<[TheBug]> [ 3] 21.0-22.0 sec 0.00 MBytes 0.00 MBytes/sec
<[TheBug]> drops to 0
<[TheBug]> means link 'failed'
<[TheBug]> so yeah somethign with driver and negotiation
<[TheBug]> I have one more thing to test later
<[TheBug]> but otherwise may wait till switch arrives tomorrow
<[TheBug]> just hoping not a huge waste of time in the end ;/
<c0rnelius> Me... When I don't care I usually take stuff out of its housing and look what they did. Especially after I've exhausted all driver and cooling related issues I can think of.