-
Posts
233 -
Joined
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by c0rnelius
-
The defconfigs are also just one piece of the problem here. There are patches getting applied to Sunxi for the Rockchip platform, why? Patches for the Pinephone, why? Last I checked that's not supported in either standard or community. Allwinner on Armbian has also been plagued with Bluetooth issues for years. I would venture to guess this is related to unchecked and unverified patching along with a defconfig that looks like a 5 year old went through and just ticked everything on. You tell me. Who wants to deal with this? Who wants to help fix it? and whom would want to do any work in this muddled up environment.
-
Could do that. Or you could do a PR and turn on what is now missing from the defconfiigs that is required for your use case. Probably more productive than endlessly complaining. Nothing got intentionally disabled or turned off. They are two new defconfigs that are getting re-worked so everyone with in the community can profit. Not just the OPi crew.
-
Chromium is not the best for playing videos. Try mplayer or mpv or something alike. I doubt you'll get great performance beyond 720p though. Might not even get it in some cases with 720p? If I wanna use an SBC as a media player, I either use LibreELEC or CoreELEC and don't use Alllwinner, but Amlogic. Good luck.
-
The DRM / GPU patches are from mainline. I'm sure there are or will be some updates, hacks and tweaks that eventually come down the road. But that's beyond the scope of bringing up the board.
-
@ScoreABSM https://github.com/armbian/build/pull/8394 I enabled gpu via overlay. Looking fine on my end. Tested using Chromium and Youtube. Still not sure about that audio dmesg error. Audio does work though. Image I ran test with: https://github.com/pyavitz/binary/releases/download/images/Armbian-unofficial_25.08.0-trunk_Bananapim4zero_bookworm_current_6.12.35_xfce_desktop.img.xz dmesgandmisc.txt
-
@ScoreABSM I have no clue what the HDMI audio errors are in the dmesg. I noticed them before as well. I know mainline doesn't actually have HDMI audio support yet. I'm not sure where these HDMI audio patches originated, but I assume the OrangePI repo. Of course, I could just be doing something wrong here on a DTS level? Strange your getting chanspec errors. This was resolved on my end by updating the wireless-regdb. You can try resolving it with this: "Put in your COUNTRYCODE" extraargs=cfg80211.ieee80211_regdom=US or this echo "options cfg80211 ieee80211_regdom=US" > /etc/modprobe.d/cfg80211.conf I'll disable the gpu by default. No. I don't see how removing those RTC patches would be creating these errors. The chanspec one is well known. Also happens on RPI's. I have a HACK patch that disables the error, but thats not really a fix. When I ran tests with the GPU before I never saw those errors and that GPU patch was pulled from mainline. I believe? Pretty sure it is the same patch I use in my personal builds. II'll say this. This is becoming endless. I'm getting ready to toss this SBC in the garbage
-
@ScoreABSM https://github.com/pyavitz/binary/releases/download/images/Armbian-unofficial_25.08.0-trunk_Bananapim4zero_trixie_current_6.12.35.img.xz
-
You could attempt to recover ur current install by adding the required DTB to the SDCARD and see if the unit boots. Once booted, mount the eMMC and again copy the DTB to the required dir. DTB DIR: /boot/dtb/rockchip/ rk3566-nanopi-r3s-lts.dtb
-
According to ur log. It's pulling down an older kernel. This kernel does not have the DTB required so it's failing to boot. After purging the kernel on the current IMG available and installing the kernel from apt. https://paste.armbian.com/orokufexik The result is a missing DTB. root@nanopi-r3s-lts:~# ls /boot/dtb/rockchip/rk3566-nanopi-* /boot/dtb/rockchip/rk3566-nanopi-r3s.dtb
-
Long Boot Delay on Banana Pi M5 in Headless Mode
c0rnelius replied to alex_laco's topic in Banana Pi M5
Yeah it applies. [🔨] ├───────────────────────────┼─────────────────────┼───────────────── [🔨] │ REVERT-clk-meson-g12a-Fix │ (+6/-6)[1M] g12a.c │ Martijn van Deve [🔨] │ -kernel-warnings-when-no- │ │ clk: meson: g12a [🔨] │ display-attached │ │ kernel warnings [🔨] │ │ │ display attached [🔨] ├───────────────────────────┼─────────────────────┼───────────────── -
Long Boot Delay on Banana Pi M5 in Headless Mode
c0rnelius replied to alex_laco's topic in Banana Pi M5
I've seen this HDMI issue on some SM1 units, "TV Boxes". There is a REVERT floating around which resolves it, but was not accepted. https://lore.kernel.org/linux-arm-kernel/001401db8ed4$392ef030$ab8cd090$@martijnvandeventer.nl/T/ I've been currently using it on 6.12.y. I have no clue if the current STABLE kernel also has this problem. REVERT-clk-meson-g12a-Fix-kernel-warnings-when-no-display-attached.patch -
@ScoreABSM https://github.com/armbian/build/pull/8368
-
Kernel 6.12.20 Banana Pi M2 zero USB doesn't work
c0rnelius replied to Bernd's topic in Allwinner sunxi
Ur welcome. -
Kernel 6.12.20 Banana Pi M2 zero USB doesn't work
c0rnelius replied to Bernd's topic in Allwinner sunxi
Tried creating an overlay and changing it to; peripheral? /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h2-plus", "allwinner,sun8i-h3"; fragment@0 { target = <&usb_otg>; __overlay__ { dr_mode = "peripheral"; }; }; }; -
The issue appears to be two things. These two patches and the current defconfig(s) being used. drv-rtc-sun6i-support-RTCs-without-external-LOSCs.patch drv-rtc-sun6i-Add-Allwinner-H616-support.patch When I disable those patches and use my own defconfig everything works as it should. https://paste.armbian.com/tixixocubu The hard part here would be figuring out exactly what in the defconfig(s) are either breaking things or missing. Also if I disable those patches, what does it break on other units? I'm under the impression these patches were rejects from the original h616 bring up in mainline. But I could be wrong?
-
@ScoreABSM Sorry I had to revert that PR. It seemed to initially work, but in the end it started hitting fails more than it functioned. https://github.com/armbian/build/pull/8344 I'm still on the case.
-
Whatever garbage ones I can find on ebay for cheap. In this case: KIOXIA 256GB SSD BG5 M.2 2230 NVMe PCIe Gen4 x4 KBG50ZNS256G https://www.ebay.com/itm/176432690192
-
I use a 12v 3a PSU "Barrel" patrick@bananapif3:~$ dmesg | grep pcie [ 0.322772] k1x-dwc-pcie ca400000.pcie: has no power on gpio. [ 0.325025] k1x-dwc-pcie ca400000.pcie: host bridge /soc/pcie@ca400000 ranges: [ 0.325065] k1x-dwc-pcie ca400000.pcie: IO 0x009f002000..0x009f101fff -> 0x009f002000 [ 0.325088] k1x-dwc-pcie ca400000.pcie: MEM 0x0090000000..0x009effffff -> 0x0090000000 [ 0.425212] k1x-dwc-pcie ca400000.pcie: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 4G [ 0.525297] k1x-dwc-pcie ca400000.pcie: PCIe Gen.2 x2 link up [ 0.525837] k1x-dwc-pcie ca400000.pcie: PCI host bridge to bus 0001:00 [ 0.543059] pcieport 0001:00:00.0: PME: Signaling with IRQ 65 [ 0.543510] pcieport 0001:00:00.0: AER: enabled with IRQ 65 [ 0.544202] k1x-dwc-pcie ca800000.pcie: has no power on gpio. [ 0.546446] k1x-dwc-pcie ca800000.pcie: host bridge /soc/pcie@ca800000 ranges: [ 0.546484] k1x-dwc-pcie ca800000.pcie: IO 0x00b7002000..0x00b7101fff -> 0x00b7002000 [ 0.546510] k1x-dwc-pcie ca800000.pcie: MEM 0x00a0000000..0x00afffffff -> 0x00a0000000 [ 0.546525] k1x-dwc-pcie ca800000.pcie: MEM 0x00b0000000..0x00b6ffffff -> 0x00b0000000 [ 0.646655] k1x-dwc-pcie ca800000.pcie: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 4G [ 1.647016] k1x-dwc-pcie ca800000.pcie: Phy link never came up [ 1.647233] k1x-dwc-pcie ca800000.pcie: PCI host bridge to bus 0002:00 [ 1.654489] pcieport 0002:00:00.0: PME: Signaling with IRQ 69 [ 1.654939] pcieport 0002:00:00.0: AER: enabled with IRQ 69 patrick@bananapif3:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk2 179:0 0 14.6G 0 disk ├─mmcblk2p1 179:1 0 508M 0 part └─mmcblk2p2 179:2 0 14.1G 0 part mmcblk2boot0 179:8 0 4M 1 disk mmcblk2boot1 179:16 0 4M 1 disk zram0 250:0 0 1.9G 0 disk [SWAP] nvme0n1 259:0 0 238.5G 0 disk ├─nvme0n1p1 259:1 0 508M 0 part /boot └─nvme0n1p2 259:2 0 238G 0 part /
-
sudo modprobe i2c-dev ?
-
@ScoreABSM https://github.com/armbian/build/pull/8339
-
@KrzyPac You apply the patch to the kernel source-tree, In this case we will use meson64 as an example. Add the patch to: patch/kernel/archive/meson64-6.12/ Enable in the defconfig: echo "CONFIG_OPENVFD=m" >> config/kernel/linux-meson64-current.config Build a new IMG or KERNEL as one normally would for your unit. general-drv-auxdisplay-Add-openvfd-driver.patch
-
As far as I know openvfd needs to be re-worked to support 6.12.y and up.
-
Here is a more vanilla build of the kernel. patrick@bananapim4zero:~$ ls /dev/ttyS* /dev/ttyS0 /dev/ttyS3 /dev/ttyS5 /dev/ttyS7 /dev/ttyS2 /dev/ttyS4 /dev/ttyS6 patrick@bananapim4zero:~$ sudo rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 unblocked unblocked 1 wlan phy0 unblocked unblocked patrick@bananapim4zero:~$ bluetoothctl hci0 new_settings: powered bondable ssp br/edr le secure-conn Agent registered [CHG] Controller AC:6A:A3:3B:D9:D6 Pairable: yes [bluetoothctl]> exit patrick@bananapim4zero:~$ uname -a Linux bananapim4zero 6.12.32 #1 SMP Sat Jun 7 17:23:51 EDT 2025 aarch64 GNU/Linux patrick@bananapim4zero:~$ dmesg | grep brcm [ 9.007064] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 9.007614] usbcore: registered new interface driver brcmfmac [ 9.303238] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 9.303576] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Aug 29 2023 01:47:08 version 7.45.265 (28bca26 CY) FWID 01-b677b91b [ 9.430799] Bluetooth: hci0: BCM4345C0 'brcm/BCM4345C0.sinovoip,bpi-m4-zero.hcd' Patch As you can see the Bluetooth works fine. If I add these two patches it breaks bluetooth on this kernel build. drv-rtc-sun6i-support-RTCs-without-external-LOSCs.patch drv-rtc-sun6i-Add-Allwinner-H616-support.patch I'm still investigating in my spare time, but I'm not 100% on anything. Could be I need to take another approach to the bluetooth node in Armbian? So this is where am at. If anyone has any thoughts I'm all ears.
-
@ScoreABSM I don't think that is the reason? No, I haven't solved the Bluetooth issue. I have theories, but I still haven't cracked the nut. You are more than welcome to give it a whirl