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>
<stonededge> Hi all, I’m currently trying to get the ILI9881C driver working in Armbian with the Orange Pi 5 but I am struggling to understand what I have done wrong. I suppose my first question is MIPI enabled on the official version of Armbian? Let me attach some debug logs, as well as the Orange Pi 5 DSI connector pinout and my driver board connector pinout. Any help appreciated
<DC-IRC>
<stonededge> I’m currently trying to get the ILI9881C driver working in Armbian with the Orange Pi 5 but I am struggling to understand what I have done wrong. I suppose my first question is MIPI enabled on the official version of Armbian? Let me attach some debug logs, as well as the Orange Pi 5 DSI connector pinout and my driver board connector pinout. Any help appreciated
<DC-IRC>
<stonededge> Hi all,
<DC-IRC>
<stonededge> I’m currently trying to get the ILI9881C driver working in Armbian with the Orange Pi 5 but I am struggling to understand what I have done wrong. I suppose my first question is MIPI DSI enabled by default on the official version of Armbian for the Orange Pi 5? Let me attach some debug logs, as well as the Orange Pi 5 DSI connector pinout and my driver board connector pinout. Any help appreciated
<DC-IRC>
<stonededge> Hi all,
<DC-IRC>
<stonededge> I’m currently trying to get the ILI9881C driver working in Armbian with the Orange Pi 5 but I am struggling to understand what I have done wrong. I suppose my first question is MIPI DSI enabled by default on the official version of Armbian for the Orange Pi 5? Let me attach some debug logs, as well as the Orange Pi 5 DSI connector pinout and my driver board connector pinout. An <clipped message>
<DC-IRC>
<stonededge> y help appreciated!
<DC-IRC>
<stonededge> I’m wondering if I’ve screwed up the GPIO mappings in my device tree overlay as per the OPi5 schematics
<DC-IRC>
<gambl0r> See if it matches what you've got
<DC-IRC>
<stonededge> This is referring to the OPi5 header, not the DSI connector pinout.
<DC-IRC>
<gambl0r> Apologies
<DC-IRC>
<marty1938> Hi folks, Im trying to wrap my head around mac definition for rock3a for the eth0 interface. Anyone got some hints for me? seems to change when a new image is flashed to emmc.
<DC-IRC>
<amazingfate> mac address is stored in uboot partition, so it will change if you flash the uboot partition.
<DC-IRC>
<marty1938> ok got it, and how is it generated?
<DC-IRC>
<ucrafear> This may not be helpful, but - A lot of systems now default to random mac and bluetooth addresses by default now, especially those with Android. It could be if your unit orignally came with Android something may have been set to randomize the mac at each boot. Is that something that could get saved to the SPI flash?
<DC-IRC>
<ucrafear> If you are running Debian or Bookworm and a desktop gui you can right click your network icon in the tray and go to your IP4 or IP6 tab and look for a check box to randomize the mac address. If it is checked it will do so. To turn that off uncheck it. I am sure you can do the same at the command line or via a config file I just do not know what that is.
<DC-IRC>
<infinity_q> I just had a major head-scratching-moment when I plugged a rtl8812 USB WiFi module for the first time on a custom-installed OS AND IT WORKED WITHOUT ANY SETUP OR HACKS
<DC-IRC>
<tenkawa42> rtl8812au drivers have been in most os distributions/builds for a long time
<DC-IRC>
<tenkawa42> That model/spec has been around since 2008
<DC-IRC>
<igorpec> "The rtl8812au chipset is an aging chipset that will likely never be supported by an in-kernel driver which leaves users dependent on Realtek to release future out-of-kernel source code. "
<DC-IRC>
<tenkawa42> @igorpec not according to the info I just looked up
<DC-IRC>
<tenkawa42> Yes.. its not in by default.. but the "chipset" has been around forever
<DC-IRC>
<igorpec> yes, chip is old, that is correct
<DC-IRC>
<tenkawa42> morrow just took old code
<DC-IRC>
<tenkawa42> it was rebased from an old archive that was used 3-4 years ago
<DC-IRC>
<igorpec> well, not saying that driver is the best
<DC-IRC>
<igorpec> just saying that this doesn't just work in random distro
<DC-IRC>
<tenkawa42> yeah.. I wouldn't touch them... just like the one last CU adapter..
<DC-IRC>
<igorpec> we have seen worse 😉
<DC-IRC>
<igorpec> i was playing with this chip a while ago and it was actually performing decent
<DC-IRC>
<tenkawa42> the 12AU or the CU?
<DC-IRC>
<tenkawa42> my CU overheats
<DC-IRC>
<igorpec> AU
<DC-IRC>
<infinity_q> I have a BU it seems
<DC-IRC>
<tenkawa42> The new ac bu's are fairly decent
<DC-IRC>
<tenkawa42> I like the TP-Link Archer
<DC-IRC>
<tenkawa42> this one works well (it does need USB3 though to fully get its best)... 2357:012d TP-Link Archer T3U [Realtek RTL8812BU]
<DC-IRC>
<c0rnelius77> I actually made a patch for the AU based on aircrack with one commit removed so 5GHZ works.
<DC-IRC>
<tenkawa42> nice
<DC-IRC>
<tenkawa42> oh the old au?
<DC-IRC>
<c0rnelius77> yeah
<DC-IRC>
<tenkawa42> it works on the xxau already
<DC-IRC>
<tenkawa42> I think
<DC-IRC>
<lanefu> @c0rnelius77 has infinite powers
<DC-IRC>
<c0rnelius77> That way you don't need to pull from github. Just patch the kernel and done.
<DC-IRC>
<tenkawa42> but still no ml for xxau yet... no idea why...
<DC-IRC>
<c0rnelius77> Something to do with it needing to be added the rtlwifi and not rtw88 and no one has stepped up to do it.
<DC-IRC>
<tenkawa42> oh yeah that's right
<DC-IRC>
<c0rnelius77> So far just talk.
<DC-IRC>
<lanefu> those who havent stepped up to do it are weak--like me
<DC-IRC>
<c0rnelius77> you and I both
<DC-IRC>
<tenkawa42> @lanefu I think it might be that there's like 50 rtl wifi chips
<DC-IRC>
<c0rnelius77> I've looked it at, but it does look daunting
<DC-IRC>
<tenkawa42> they made way too many
<DC-IRC>
<lanefu> remember when there use to be sure-thing wifi chips
<DC-IRC>
<c0rnelius77> Which is the nice thing about just jacking aircrack. That one module supports a lot.
<DC-IRC>
<tenkawa42> then take that 50*unique adapters
<DC-IRC>
<lanefu> wow so aircrack ships a module with just a bunch of modded drivers already crammed in?
<DC-IRC>
<c0rnelius77> yeah. 8811/12/14/21
<DC-IRC>
<c0rnelius77> I don't hve a 14 so not sure how well that works.
<DC-IRC>
<c0rnelius77> I don't have a 14 so not sure how well that works.
<DC-IRC>
<c0rnelius77> Even on Armbian I sitll only get 2.4GHZ.
<DC-IRC>
<c0rnelius77> Once I remove it that PR, it just works.
<DC-IRC>
<c0rnelius77> Once I remove ithat PR, it just works.
<DC-IRC>
<tenkawa42> I think looking at the diff the frequency changes would need a crda patch too
<DC-IRC>
<c0rnelius77> Once I remove that PR, it just works.
<DC-IRC>
<c0rnelius77> Yeah something is a miss there.
<DC-IRC>
<c0rnelius77> Well I should correct myself. It works flawless on a 5.15 kernel, on 6.x.y I need to hack `net/wireless/nl80211.c` and remove the `warning` and `trace` from the file to prevent dmesg ugliness. So it isn't perfect, but at least it work. Something to do with `cfg80211_ch_switch_started_notify`.
<DC-IRC>
<c0rnelius77> Which is the same dmesg junk I also saw when using the rtl8822cs github module.
<DC-IRC>
<tenkawa42> yeah they changed the cfg80211 in 6 a lot