Forums
-
Armbian
-
- No posts here yet
-
-
Community
-
- 633
- posts
-
- 4.2k
- posts
-
- 883
- posts
-
- 10.1k
- posts
-
-
Using Armbian
-
- 19.6k
- posts
-
- 1.1k
- posts
-
- 16.1k
- posts
-
-
Standard support
-
- 2.4k
- posts
-
- 2.9k
- posts
-
- 9.6k
- posts
-
- 1.9k
- posts
-
-
Community maintained / Staging
-
- 25.3k
- posts
-
- 2.5k
- posts
-
- 39.6k
- posts
-
- 3.6k
- posts
-
- 13.1k
- posts
-
- 2.4k
- posts
-
-
Upcoming Events
-
Volunteering positions
-
Code reviewer
Position: Framework maintainerNumber of places: UnlimitedApplicants: 9
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Popular Now
-
-
Activity Stream
-
75
Efforts to develop firmware for H96 MAX M9 RK3576 TV Box 8G/128G
It seems that this time they excluded the passive components from the board, look at the v56 board SD reader, you will need to add 2 ceramic capacitors to the board i think. and also check the Reader body 4 large GND pads if it's sodered. no device is needed to use the SD reader you must have a TTL connected to the board to debug, clear the EMMC with this method: using the T95 Method On android ROM flash the Wipe_part on Boot partition flash the Wipe_part on Recovery partition Connect the power cord... wait 1 second and in a fraction of second, connect the sd-Card on device..... if it doesn't boot, try again in a different timming 2 seconds after power. Based on this example -
289
Helios64 - Armbian 23.08 Bookworm issues (solved)
Could you check if the 'rtl8156a-2 v2' firmware is loaded (dmesg | grep r8152) ? I did not see that during my tests. Thanks ! -
8
NanoPi Neo2 V1.1 / how to control OTG port power with GPIO 354?
Thanks for the information and the links. I'll dive into it the next days... Yes, the part in the board schematics which controls the chip to power the OTG micro USB port is 100% identical between a NanoPi Neo and a NanoPi Neo2. Same GPIO pin on the SOC. The strange thing is, that the used Kernel would support to enable the sysfs "export" of a GPIO number from userspace: $ zcat /proc/config.gz | grep CONFIG_GPIO_SYSFS CONFIG_GPIO_SYSFS=y I analyzed further the diffs of the device trees and found below (excerpt again) line marked with ** **, which is not in the H3 device tree. The usb0-vbus def is in the H3 tree as well, but not referenced. Tomorrow I'll create an overlay which sets the status of usb0-vbus to "disabled" (as I just read that delete does not exist). Maybe it works 🙃 phy@1c19400 { ** usb0_vbus-supply = <0x19>; ** usb0-vbus { phandle = <0x19>; -
0
Odroid M1: USB disk not detected after kernel upgrade 6.6.63->6.12.9
On my Odroid M1 which used to run kernel 6.6.63 / armbian 24.11.3 noble from NVME, an update to kernel 6.12.9 arrived this morning. Afterwards the machine failed to detect an external USB disk. There are some messages in the logs of the 6.12.9 boot that look suspicious to me: [ 2.670354] rockchip-naneng-combphy fe820000.phy: error -ENOENT: failed to get phy reset [ 2.670392] rockchip-naneng-combphy fe820000.phy: probe with driver rockchip-naneng-combphy failed with error -2 [ 20.458737] platform fc800000.sata: deferred probe pending: platform: supplier fe840000.phy not ready [ 20.458786] platform fcc00000.usb: deferred probe pending: platform: supplier fe820000.phy not ready [ 20.458812] platform fd000000.usb: deferred probe pending: platform: supplier fe830000.phy not ready The USB disk shows up as "ID 2537:1066 Norelsys NS1066" on the USB bus with the 6.6.63 kernel, no trace of its USB ID shows up with the newer kernel. The ID coincides with the ones contained in the kernel command line: usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Does anybody know how to get the USB disk working with that newer kernel? I downgraded to 6.6.63 for now. Regards Mathias 6.6.63-armbian-hardware-monitor.log 6.12.9-armbian-hardware-monitor.log -
5
Kodi problem with MCE remote
Yes, now it's work great, the problem was solved this way .
-
-
Member Statistics
