-
Posts
160 -
Joined
Community Answers
-
c0rnelius's post in Unable to get wireless recognized. was marked as the answer
Read the post and check the PR link
and or follow the fellas post below.
The IMGs need to be updated, so currently that's the only remedy as far as I know.
-
c0rnelius's post in Wifi setup was marked as the answer
@Eloy Bote Falcon
Try this pre-compiled binary. I'm gonna need to re-write some of that patch to work with armbian.
sun50i-h618-bananapi-m4-zero-v2.dtb
-
c0rnelius's post in Slow WiFi speeds on Banana Pi CM4 was marked as the answer
@vimal
try this patch with the github driver.
0001-sdio-wifi-fixups.patch
-
c0rnelius's post in No Armbian images are working was marked as the answer
I suspect the issue is the version of U-Boot currently on the eMMC. When the board boots, if U-Boot is found on the eMMC, that is what will be used to do the initial boot. If an SDCARD is detected with a viable OS, it will then attempt to load it. It may be that the version of U-Boot "BSP?" on the eMMC is not compatible with Armbian and needs to be dd'd off.
I just flashed this to SD to test. Came up fine.
____ ____ _ __ __ ____ ____ | __ )| _ \(_) | \/ |___ \/ ___| | _ \| |_) | | | |\/| | __) \___ \ | |_) | __/| | | | | |/ __/ ___) | |____/|_| |_| |_| |_|_____|____/ Welcome to Armbian 24.5.3 Bookworm with Linux 6.6.36-current-meson64 System load: 10% Up time: 1 min Memory usage: 4% of 3.69G IP: CPU temp: 37°C Usage of /: 4% of 29G [ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ]
-
c0rnelius's post in 64 MB less total memory on 24.2.1 was marked as the answer
Try adding it this way.
extraargs=swiotlb=0
-
c0rnelius's post in Kali Linux as supported distro was marked as the answer
Kali is in a lot of ways a polished SID with all of their own custom bits added. It can be debootstrap'd just like Debian, Devuan and Ubuntu. I did find some services didn't work on boot; 'ssh avahi bluetooth ntp'. But there could be some option they have I'm not aware of to allow those services to start out of the box. Creating a custom service to start those does the trick though.
I would think adding this as an option could be doable, but the question then becomes who wants to handle the support required to maintain it?
-
c0rnelius's post in how to force audio on 3.5 jack on headless bullseye was marked as the answer
sudo nano /etc/asound.conf
pcm.!default { type hw card 2 } ctl.!default { type hw card 2 } save and reboot
https://www.alsa-project.org/wiki/Asoundrc
-
c0rnelius's post in Radxa Pi Zero does not boot from eMMC if USB drive is connected was marked as the answer
It is more than likely a u-boot issue caused by a specific patch; https://github.com/armbian/build/blob/main/patch/u-boot/v2022.10/meson64-boot-usb-nvme-scsi-first.patch
https://github.com/armbian/build/blob/main/config/boards/radxa-zero.conf#L17
You would need to build u-boot with this patch disabled, flash it to the unit and see if it solves the problem.
-
c0rnelius's post in BananaPi CM4: Add force USB host mode capability was marked as the answer
Give it a whirl and let me know.
lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 001 Device 003: ID 0bda:a811 Realtek Semiconductor Corp. RTL8811AU 802.11a/b/g/n/ac WLAN Adapter Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
meson-g12b-bananapi-cm4-waveshare-usb.dts