Clonazepunk
-
Posts
36 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Clonazepunk
-
-
Ok, i'm stupid
The firmware for this board is missing.[ 9.020401] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.amlogic,p281.bin failed with error -2
[ 9.020401] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.amlogic,p281.bin failed with error -2the file brcmfmac4330-sdio.amlogic,p281.bin simply doesn't exist
Wonder if it works if i borrow it from Android...
EDIT: Found a workaround! I'll leave this thread for other user's further research
cp /usr/lib/firmware/brcm/brcmfmac4330-sdio.bin /usr/lib/firmware/brcm/brcmfmac4330-sdio.amlogic,p281.binFor some reason, the kernel won't use the default firmware, and want the specific board version. It works now!
-
Hello guys!
First of all, i couldn't find a topic about the same problem im having, so, if this is a duplicate, just let me know and i'll delete it
So, i just installed Armbian Lunar Edge (Kernel 6.2.9) on my box. The WiFi chip is properly recognized, but the firmware for it won't load
This is the dmesg output[ 8.897269] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 8.898654] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 8.899871] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 8.899910] cfg80211: failed to load regulatory.db [ 8.912366] Adding 988264k swap on /dev/zram0. Priority:5 extents:1 across:988264k SSFS [ 8.993849] systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch. [ 9.000207] brcmfmac: F1 signature read @0x18000000=0x16044330 [ 9.017810] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4 [ 9.019051] usbcore: registered new interface driver brcmfmac [ 9.020401] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.amlogic,p281.bin failed with error -2 [ 9.035609] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.clm_blob failed with error -2Given that the board is recognized, i dont think its a big deal. Still investigating the problem, but until that, can someone give me some tips on how to solve it?
Thanks in advance!
EDIT: I am an advanced user, and intend to give official support for this hardware. A lot of people own similar boxes
-
Hi! Have you tried the linux-firmware package?
It provides drivers for many wifi chips
Try it with sudo apt install linux-firmware
Hope it works!
-
51 minutes ago, MrCoolAndroid said:
I would like to try another DTBs, the problem is that Armbian is installed on the eMMC haha, anyways I think I'm just gonna buy a WiFi adapter or try with what @uropb said, and don't worry it's all good, stay safe!
But that's no problem
You still can edit the extlinux.conf file, inside the boot partition
Just take care of not setting up any invalid option in it, else you'll break your system
(Though it's easy to recover)
-
2 hours ago, uropb said:
From forum.manlaro :
I got RTL8189ETV (may also works with rtl8189es) working with jwrdegoede/rtl8189ES_linux:
(kernel : 5.13.12-1-MANJARO-ARM #1 SMP Wed Aug 18 07:36:58 UTC 2021 aarch64 GNU/Linux)git clone https://github.com/jwrdegoede/rtl8189ES_linux.git
sudo pacman -S linux-headers
cd /usr/lib/modules/5.13.12-1-MANJARO-ARM/build/arch
sudo mv arm armold
sudo mv arm64 arm
cd ~/rtl8189ES_linux/
make -j4 ARCH=arm KSRC=/usr/lib/modules/5.13.12-1-MANJARO-ARM/build
sudo cp 8189es.ko /usr/lib/modules/5.13.12-1-MANJARO-ARM/kernel/drivers/net/wireless/realtek/
sudo depmod -a sudo modprobe 8189es
Check with nmtui or ip addr and rename arm&arm64 back.
Manjaro is a good choice
It works out of the box with my S905W board!
Thanks for pointing out. I forgot that
-
18 hours ago, MrCoolAndroid said:
Yes I was thinking on getting a WiFi adapter, and I have the p281 dtb, it's the S905W one
That's good to know
Before trying anything else, you should try other dtb files, as stated by @SteeMan.
I was lucky. My S905W box works like a charm with a realtek chip as well.
you can do it without recompiling the kernel by using @balbes150images. There's a plenty of files to try out
make sure you have the p281 board, of doesn't, try other dtb files
if you're sure your board is a p281 (which also means it's defective from factory, with different hardware), then you should try to compile the drivers from the git you found
ok, that's a lot of info. I'll keep helping you through this post, and sorry for the late replies. I suffer from some conditions that keeps me away from staying too much on the PC
Hope It works!
-
Well, to help you with the headers, I need to know which kernel exactly are you using.
Show me the output of the command "uname -a", please
Also, installing the package by itself should be enough to make the interface wlan0 to show up. But don't panic. Let's see the headers issue first
-
Hi!
If I remember, your wifi chip is already supported by Armbian.
Try installing the package armbian-firmware-full
it should do the trick, and save you a lot of time compiling the drivers from source
Hope it helps!
-
Hi!
@balbes150 provided a working image for a RK3399 box. Maybe you should give it a shot.
Good luck!
-
Hi!
@hexdump is right
I think the best way to figure it out is first, to find out what wifi chip the board has. If the package armbian-firmware-full has support to it, you're good to go
I had good experiences with rockchip boxes. They're the cheapest ever, and always with the same two supported wifi chips (ssv6051 or ssv6252). If you want to bet on one of those cheap Chinese boxes,put your bets on MX9 or MX10 boxes.
MXQ boxes has a good chance to come with a rockchip CPU, but there arr fake ones with the AllWinner H3 CPU (whose wifi isn't supported). But it also worthy trying
Take your time finding a box and come back if you need support with it!
Good luck.
(You'll need it lol)
-
Hi!
We are here to help, but first we need more info from you
Which Armbian build are you using? Can you tell?
As the log says, the error is in the U-Boot parameters, but can me something more.
Can you detail your problem a bit more? Starting from the image download
-
Just to add: You have a powerfull toy with you. It's a waste to use it as a paper weigth!
-
On 6/24/2021 at 3:05 AM, masteripper said:
I think is dead....tried yesterday the UART connection and while i got again the boot output...i couldn't interrupt it...so..
After some research, i realized the same error happened when users tried to update their ROM from a LPDDR3 memory to a DDR3 Box, or vice versa
Uploading software on Amlogic CPUs is like a surgery. I think that's why the Meson support is kinda poor compared to Rockchip CPUs.
Well... There's no unbrickable device. Maybe you should try the short pin method and skip the boot from e-MMC, or even more radical: Remove the e-MMC chipI was able to save a fully bricked (surprisingly) rockchip box using this method. It's always my last resource
If you need any tips about the electronics, feel free to ask! -
Hi!
Those boxes play flawlessly on Android. I think it's a matter of time and better drivers will come up
The best results i got was using Arch Linux and lima (open source drivers for Mali GPUs). Maybe you should give it a try.
PM me if you need help with this!
Good luck -
9 hours ago, hanguofu said:
If the uart port is not connected , the u-boot stop after "Hit any key to stop autoboot: 2 1 0 " ---- it is just what I guessed. If I hooked up the uart port with a debug board , I saw no output from screen. But if I press "Enter" key , the u-boot shows "=>" and ready for commands . A "reset" command can make the u-boot to reboot .
If the uart port is connected before power up , the u-boot boots normally.
I had the same problem with some versions of the Amlogic S905W processor
My workaround was to short the UART TX pin to ground using a small resistor. It fakes a UART connection and the boot continues
If the step fails, try the same with the RX pin.
Good luck!
-
Hi!
This screen says your board is booting properly.
See? The U-Boot starts, finds your extlinux.conf file and starts the kernel as well
If the screen blanks after a while, it's probably a HDMI fault. Try to connect your box to a serial console via UART (open the case, and you'll find the pins)
To do this, you'll need a Serial to USB converter (such as CH340 or FT232. Both cheap as heck)
You'll notice that the boot continues from there.
If so, you'll need extra configuration to your HDMI inside your extlinux.conf file.
Try the serial and send us the terminal output. We're here to help!
Good luck!
-
5 hours ago, Logicpro8_user said:
Hi everyone, long term lurker to this site, however I see a whole trend in S905X Android TV boxes with sound issues. As far as I understand the SPDIF and AV ports are not supported with Armbian, however, HDMI Audio is I think. My box Rupa Pyramid A5x with the Amlogic S905X CPU boots great, followed the guides to the letter. Graphics are great, performance is as expected, 4K video is a little struggle sometimes, I suspect this is Firefox though, I actually use this same box for many years as a headless Plex/Docker server and it was amazing for this! I mean really really good. 4/5/6 steams at the same time to TVs, iPads, phones and then some more!.
The issue I am having is related to HDMI sound, many posts about this, but to real resolution. Is HDMI sound even supported on this CPU?. The Arabian UI sound section shows output in the volume bars, bit nothing works from the display sound wise, I tested 3 monitors with build in speakers now, nothing, tested new HDMI cables as well, still no sound.
I am using Armbian_20.10_Arm-64_bullseye_current_5.9.0_desktop.img as my install with the meson-gxbb-nexbox-a95x.dtb file and have also tested meson-gxl-s905x-p212.dtb without success. Could my issues be related to Armbian 5.9? does anyone know if past version had HDMI sound?. I really want to use this box as a mini desktop, this one missing step is really annoying
Thanks in advance,
W
Hi!
Did you check alsamixer?
Had the same problem on my S905W box.
I just needed to alternate between I2S / SPDIF and it worked like magic
If you have any doubts, post an image of how your alsamixer screen looks like
-
Just now, masteripper said:
Thanks for reply man... tried SD but no luck...is dead in the water.
I read somewhere that the last resort is to do flashing via UART but i am not sure of the procedureThat's weird. What happened before that? Did you try to update the bootloader or something like that?
The bootloader should first look for a SD Card bootable system.So, flashing it through UART is not possible, although you still can flash an Armbian image via USB using aml-flash-tools
Also, burning the stock android image would also do the trick. with the stock ROM working, it'll begin to boot from SD againFor Android, use this tool:
https://androidmtk.com/download-amlogic-flash-tool
-
Hi!
The simple fact that it still shows serial output and running the bootloader mean that the box isn't totally dead. Something is corrupted inside the eMMC installed system. Did you already try to boot it via SD Card?
The Amlogic CPUs try the SD card before the eMMC storage (at least the ones I have).
I don't know anyone who's supporting S905x3, but maybe you can find a booting image for it in this forum. Burn it to a SD Card and see if your box responds.
Hope it helps somehow
Good luck!
-
Well...I can't explain why it worked with me
You have a point
-
Try the PhoenixSuit solution
Your box doesn't need root accees on Android. There's a button somewhere in your board that triggers FEL mode
Every Allwinner processor has it
More info at https://linux-sunxi.org/FEL
When in FEL mode, you can plug your board on your PC using a USB male to male cable. It allows direct access to the internal memory, thus allowing to dump it
I found the cable available online, but with two old USB cables and some electric tape you can build your own lol
Besides the PhoenixSuit, there is also the sunxi-fel tool. It allows the memory dump. Just tried with Allwinner H3 and Allwinner F1C100 and it works like a charm
-
That's not true
We have a lot of people who could boot Armbian on their boxes by using the original DTB file.
Sometimes, is the only way
-
So, Allwinner chips have a flashing tool called PhoenixSuit
I'm not sure, by maybe you can dump the image through it
It worth the test
-
Hi!
Well, directly to your questions
The first step to compile a operating system to any ARM board is to know your board's Device Tree (DTB file)
You can extract the DTBs from the stock Android ROM. I do it on Linux using the tool binwalk to lookup the image and find the DTBs
There are other methods you can search
About the u-boot, you can't use the Android u-boot. Android uses very old kernels, so it's U-Boot release Is made to boot those.
You need a modern U-Boot release, so that's your first step
To bring Linux to a new board, you'll need to compile U-Boot from source and use the DTB file you just extracted from the stock Android ROM.
After that, you can use the Armbian kernel and use any Armbian image or even use your own custom rootfs
My boxes are running Arch Linux ARM actually!
If you get stuck in one of those steps, just post it here or, if you want to, PM me
Good luck!
Tanix TX3 Mini (Amlogic S905W) Broadcom WiFi issue
in General Chat
Posted · Edited by Clonazepunk
Sorry for that, @SteeMan, i'd give him support in my original thread, but they closed it...
@basodo, pm me.