An update on the new chainloader u-boot-n2.bin, it works consistently on GT King Pro (just like the previous chainloader u-boot).
Have updated to the latest Stable Updated 2021-04-27 with linux-5.12.0-1 (from unstable branch) all works well except the network connection seems to take a bit longer to start up (both ethernet or wifi). Reboot and Shutdown issues still remains with mainline 5.12.0-1
Hello world, newbie here.
I have a x96 mini resting in a drawer and tried running Manjaro on it. But even with the p281 dtb i always get " failed to map file " error when trying to update. Any workaround this one if youâve zver faced it?
Well as instructed on the guide: flashed the .img on a 16gb sd card , renamed the s905x u boot into " u-boot.ext" , opened the âuenvwhatchamacallitâ file and pasted the s905w-p281.dtb, then went into recovery mode, chise flash from ext and aml-thingy and error.tried the reset switch and the update app but whenever it accesses recovery it gives me the same error . It happened with manjaro and armbian. I suspect that a former trial of running emuelec might have messed something, think iâll flash a normal rom to reset the rom partition
I tried to do that for X88 King (with the valuable help of @TheMojoMan) but it seems to be more difficult than I could imagine. And I was just trying to enable the USB ports-everything else seemed to be perfect using the dtbs from other similar TVboxes with the S922.
But you have nothing to lose to try it.
i try manjaro from âugoos blogâ But my Ugoos Am6 plus not boot from USB flash. Please help me. I press recovery botton, but manjaro not boot. I look recovery screen
I just wanted to inform you that yesterday I have migrated from linux-vim (5.11.13) to linux-amlogic-512 kernel (5.12.0-1-ARCH) on my X96Max+ (S905X3, Mali G31).
The box booted up without problems and sound is working! When running glmark2-es2 I get a score of about 225 (using XFCE and mesa-git) which is the same as using the linux-vim kernel.
The only problem I had was that internal wifi was broken because chewitts rtl8822cs driver did not compile anymore.
But fortunately after some research I found a solution and therefore I have built a new driver package that you can download here: 3.58 MB file on MEGA
You can install and activate the driver like this:
Please notice that linux-amlogic-512-headers has to be installed before running above commands for the driver to install correctly. You can install it with
sudo pacman -S linux-amlogic-512-headers
Thumps up to @spikerguy for bringing us another set of new kernels!
Oh, sorry! I did not realize that it was not packed by you and does not belong to the manjaro repo.
So I had another look and it is chewitts Amlogic branch from archlinuxdroid repo at http://archlinuxdroid.tk/archlinuxdroid/aarch64 which I added to my pacman.conf a long time ago.
I mistakenly thought that it was your 5.12 kernel that you have been talking about some posts ago.
Iâm running a khadas vim3 image on my x96 max+ with mt7661rsn WiFi chip (figured it out after opening the back cover). Obviously, wifi doesnât work and thatâs why Iâm here.
For some reason, Android identifies the chip as mt7663 (which should be supported by the mt76 driver since 5.8, according to the linux wireless wiki). Perhaps itâs possible to instruct mt76 to work with that mt7661 chip just like if it was mt7663?
Also, I found some *.bin and *.dat files in androidâs /vendor/firmware/, like WIFI_RAM_CODE_MT7663.bin and so on, but I have no idea what to do with them.
I tried just copying android firmware to /usr/lib/firmware and at the same time copy-pasting wifi-related dts pieces from android dts, but that of course didnât work.
dmesg shows nothing mt76*-relevant.
Doing modprobe -a mt76 doesnât print anything to dmesg.
Maybe worth mentioning, I installed the system according to this guide, with the only difference being that right now Iâm using a minimal image, not a kde-plasma one. Anyway, that doesnât matter as the problem exists regardless of dts/image/whatever.
So, any idea how to bring the wifi up?
Iâm not a Stallman fanatic, so proprietary firmware extracted from android will do, as long as everything works.
A quick search (including the link to the wireless wiki) shows that the chip is connected via the SDIO bus. Since the dmesg output doesnât show anything mt76* relevant, this suggests that the communication over the bus is not functional (i.e. the chip isnât even detected on the SDIO bus). (I had a similar problem with the WiFi/BT chip on my Ugoos AM6 plus, you can search the forums for info relating that.) Thatâs the help I can offer.
Is this what youâre talking about?
Do I understand it correctly that, if I do the same thing to my board, wifi will be fixed?
Anyway, how do you know what to edit and how to edit? I mean, how to find correct values for all that 0xCrap and correct filenames for firmware?