lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> [Discord] <aprodigy> anyone in here using a rock5 with the A8 wifi module and lwfinger's (https://github.com/lwfinger/rtw89) kernel module for armbian noble with the 6.1.43 kernel with any success? noble's 6.1 doesn't seem to bring a fitting kernel module so i googled a bit around and stubled upon lwfinger's. compiling wasn't a problem and the device gets fully recognized now. scanning for networks i <clipped message>
<DC-IRC> [Discord] <aprodigy> s no problem either (via iw, nwcli et al.) but trying to authenticate fails with ``<info> [1718042431.1980] device (wlP2p33s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')`` even though ``nmcli dev wifi list`` does indeed show me both (2.5ghz / 5ghz) networks all fine. any idea is much appreciated.
<DC-IRC> [Discord] <aprodigy> anyone in here using a rock5 with the A8 wifi module and lwfinger's (https://github.com/lwfinger/rtw89) kernel module for armbian noble with the 6.1.43 kernel with any success? noble's 6.1 doesn't seem to bring a fitting kernel module so i googled a bit around and stubled upon lwfinger's. compiling wasn't a problem and the device gets fully recognized now. scanning for networks i <clipped message>
<DC-IRC> [Discord] <aprodigy> s no problem either (via iw, nmcli et al.) but trying to authenticate fails with ``<info> [1718042431.1980] device (wlP2p33s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')`` even though ``nmcli dev wifi list`` does indeed show me both (2.5ghz / 5ghz) networks all fine. any idea is much appreciated.
<DC-IRC> [Discord] <aprodigy> anyone in here using a rock5 with the A8 wifi module and lwfinger's (https://github.com/lwfinger/rtw89) kernel module for armbian noble with the 6.1.43 kernel with any success? noble's 6.1 doesn't seem to bring a fitting kernel module so i googled a bit around and stumbled upon lwfinger's. compiling wasn't a problem and the device gets fully recognized now. scanning for networks <clipped message>
<DC-IRC> [Discord] <aprodigy> is no problem either (via iw, nmcli et al.) but trying to authenticate fails with ``<info> [1718042431.1980] device (wlP2p33s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')`` even though ``nmcli dev wifi list`` does indeed show me both (2.5ghz / 5ghz) networks all fine. any idea is much appreciated.
<DC-IRC> [Discord] <aprodigy> okay... hehe... fixed it by myself with the help of a bit more from aunty google. the recent stable branch is obiously missing a fix (commit 0692fee) from last year. if anyone else runs into this, this is the working branch for anyone with my issue from above: https://github.com/lwfinger/rtw89/tree/0692feeda86bd150231950451ade3cc6cf03611e
<DC-IRC> [Discord] <aprodigy> ``wlP2p33s0: connected to atHome
<DC-IRC> [Discord] <aprodigy> "Realtek RTL8852BE 802.11ax"
<DC-IRC> [Discord] <aprodigy> wifi (rtw89_8852be), 2C:05:47:8E:50:7C, hw, mtu 1500
<DC-IRC> [Discord] <aprodigy> inet4 172.16.17.51/24``
<DC-IRC> [Discord] <aprodigy> but i'm still wondering about the "design decision" here. 6.1 does support hdmi-audio out but 6.8 doesn't. 6.1 doesn't support the A8 out of the box but 6.8 does, haha
<DC-IRC> [Discord] <mecoblock> 6.1 is a whole different branch. It’s coming from the SoC „vendor“ while anything above is upstream
<DC-IRC> [Discord] <aprodigy> ah, okay... finally got that, ty. so 6.1 is basically a radxa-one whereas 6.8 is a more fine-tuned thing (for whatever reason i'mma find out) from the armbian team then, i guess. fine, but why wasn't or couldn't the hdmi-audio out part from 6.1 not be a part of the 6.8 one then ? as i said, i'm just wondering
<DC-IRC> [Discord] <mecoblock> not yet as upstream linux kernel isn’t just a thrown together kernel that works but actually has quality standards and lots of testing involved. If you want full HW support you go with vendor if you want highest security / bleeding edge you go with upstream.
<DC-IRC> [Discord] <aprodigy> well, again, ty. that makes sense. do i consider the vendor one lts or the upstream one ? or none of em ? :D
<DC-IRC> [Discord] <aprodigy> and even tho, is there some discussion going on anywhere about that hdmi-out no being in the upstream one ? not so sure if it's seriously security related to leave that part out and i can't be the only one wondering about no stock hdmi-audio out with armbian 6.8. or am i ?
<DC-IRC> [Discord] <alexl83> I pulled the trigger and ordered a nanopi r5c 4gb, case, wifi, etc etc
<DC-IRC> [Discord] <alexl83> my frankenkali userpatches builder will get a new board support
<DC-IRC> [Discord] <aprodigy> k
<DC-IRC> [Discord] <alexl83> I still miss the buzzer/beeper tho
<DC-IRC> [Discord] <t1msu_87222> does somebody have a overlay for rk3588 spdif using vendor kernel?