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 feed: #armbian-rss | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
<aasami_>
IgorPec: Explanation: I lost quit old machine with absolut all data on it while installing D12 and with many interruption while AC-interrupion so neither booting is possible nor any system could be brougt up. Very important data are gone ...
<IgorPec>
oh, sad to hear this
Tazy has joined #armbian
danilogondolfo has joined #armbian
bastelfreak has quit [Quit: WeeChat 3.8]
bastelfreak has joined #armbian
alekksander has quit [Quit: Konversation terminated!]
MrFixIt has quit [Ping timeout: 252 seconds]
MrFixIt has joined #armbian
kolla has quit [Quit: %fog relay%]
kolla has joined #armbian
archetech has joined #armbian
oida has joined #armbian
Tazy has quit [Ping timeout: 246 seconds]
<JyZyXy>
im trying the Armbian_23.8.0-trunk.56_Orangepi5-plus_lunar_legacy_5.10.160_xfce_desktop.img.xz but the serial terminal is only working sporadically with constant random pauses. whats the deal with that?
<JyZyXy>
the green led is doing two blinks every second so something must be going on
<DC-IRC>
<.richn> thats called the heartbeaat
<DC-IRC>
<.richn> it just says the unit is alive
<JyZyXy>
the serial was working just fine in the debian bookworm image
Tazy has joined #armbian
Tazy has quit [Ping timeout: 246 seconds]
Tazy has joined #armbian
Tazy has quit [Ping timeout: 246 seconds]
<JyZyXy>
might've been just a case of bad usb extension cable for the UART adapter
alekksander has joined #armbian
lyri has joined #armbian
lyri has quit [Ping timeout: 240 seconds]
lyri has joined #armbian
kyle__ has joined #armbian
archetech has quit [Quit: Konversation terminated!]
<kyle__>
So, I just updated my orangepizero to bookworm (23.05.1 armv7l), and lost wifi? Did the required packages change between versions? For wifi?
archetech has joined #armbian
<DC-IRC>
<tenkawa42> kyle__: do a dmesg | grep firmware and see if you get any nessages back
<DC-IRC>
<tenkawa42> like -2 errors
<DC-IRC>
<tenkawa42> I doubt it but curious
<kyle__>
Nothing now. There was a copmlaint about regulatory.db ( I think?) failing to load in firmware when I tried to manually install a module I thought might be the driver, and I fixed that.
<kyle__>
But no joy
<DC-IRC>
<tenkawa42> you possibly can check sudo rfkill and see if its showing up and unblocked ie:
<DC-IRC>
<tenkawa42> ID TYPE DEVICE SOFT HARD
<DC-IRC>
<tenkawa42> 0 bluetooth bt_default unblocked unblocked
<DC-IRC>
<tenkawa42> (this is from one of my other boxes)
<kyle__>
Yeah, nothing on rfkill either.
<kyle__>
even lshw and lsusb don't show anything. So I was thinking something could be blacklisted?
<kyle__>
All I found was the video decoding driver for that though.
<DC-IRC>
<tenkawa42> that will just blacklist the driver... not the hardware itself.... sounds almost like a dtb issue
<kyle__>
dtb?
<DC-IRC>
<tenkawa42> device tree blob... it connects the hardware to the os
<kyle__>
Ahh.
<kyle__>
Looks like I've got linux-dtb-current-sunxi 23.05.1--6.1.30-Sa343-D8bc9-P73a0-C162eHfe66-HK01ba-V014b-B9c18
<kyle__>
I assume that needs to be in lockstep with the kernel?
<DC-IRC>
<tenkawa42> need to find who works on that specific piece of hardware to see what the current status is.. let me see who maintains it
<DC-IRC>
<tenkawa42> which orange pi zero model/
<DC-IRC>
<tenkawa42> er ?
<kyle__>
zero with 512MB of ram. Um....
<DC-IRC>
<tenkawa42> the original zero?
<kyle__>
????
<kyle__>
I think so.
<DC-IRC>
<tenkawa42> Ok. I ask because there's a Zero, Zero2 and Zero+
<kyle__>
*sigh* also the cli utility I wrote for looking up emoji instead of typing them apparently doesn't play well with weechat.... that ws supposed to be a thinking face
<DC-IRC>
<tenkawa42> they all have separate builds, and 2 have diff maintainers and 1 has no maintainer currently
<DC-IRC>
<tenkawa42> The regular zero does but Bookworm is not a "tested" build.. only Jammy.. its in the auto builds only
<DC-IRC>
<tenkawa42> oh wait no.
<kyle__>
Humm. Well this has 1/100 so it's not a plus
<DC-IRC>
<tenkawa42> its been updated as of Jun 6
<DC-IRC>
<tenkawa42> let me check something
<DC-IRC>
<tenkawa42> did you see this?
<DC-IRC>
<tenkawa42> Onboard wireless module (XR819) has poor software support so wireless connection issues are expected
<kyle__>
Clever me slapped heatsyncs over the chips so i can't read them anymore :\
* kyle__
nods
jantones has joined #armbian
<kyle__>
I did. With the older version it wasn't great, but it was actually reliable if slow.
<kyle__>
older version of armbian that is.
<DC-IRC>
<tenkawa42> @igorpec if you see this I would need to defer this to you...
<DC-IRC>
<igorpec> we don't have xr819 driver on 6.1
<DC-IRC>
<igorpec> yet
<DC-IRC>
<tenkawa42> Ahh.. I kinda wondered
<kyle__>
Is it in tree or out? I don't mind building a module for myself if that's all that I need to get this going.
<kyle__>
(and if it were a dkms module, even easier!)
<DC-IRC>
<tenkawa42> I think I found a possible one...
tachi_ has joined #armbian
<DC-IRC>
<tenkawa42> they appear to have 6.1 updates