All Activity

Why do you delete my post? I don't wanna argue with anybody. Please don't change defconfig at will . Just simply do these, everything will works: git checkout d502356 config/kernel/linux-sunxi64-current.config git checkout d502356 config/kernel/linux-sunxi64-edge.config No any other modification. The patches from Mr Pyavtiz will break this system call: pin->file_descriptor = socket(PF_NETLINK, SOCK_RAW , NETLINK_CONNECTOR);

Maybe some further notes on w.r.t. running HAOS in a VM: As indicated, the process is described for Intel, see https://www.home-assistant.io/installation/alternative For ARM, people have selected RaspberryPi and then ask why it does not work. That is because RPi uses proprietary bootloader (not U-Boot, nor EFI). You need the haos_generic-aarch64 build/image, see https://github.com/home-assistant/operating-system/releases I do not use qcow2, but just a flat img. That is easy to mount as loop device in case some changes are needed to partitions or so. I extracted the .img.xz file and changed the storage (VirtIO Disk) of my existing HA VM to use the new native HAOS instead of my old Debian+supervised_HA. It started without issues and I get to the webpage from where the rest is a standard 'HA getting started', e.g. restore its backup so all devices stats etc are back again. I know many people ask for VMware or Proxmox (or some for VirtualBox), but Linux has anyway all the low-level stuff build-in and a GUI as well: root@rock5b:~# apt install virt-manager virt-manager is already the newest version (1:5.0.0-5). I have this running on ARM64 since Debian Buster 64-bit beta RPi (and 1st early 64-bit Ubuntu server image for RPi4 and also Opensuse Tumbleweed 64-bit) so the commercial ones I dropped long time ago. Above is latest Trixie. Kernel is Armbian vendor currently, but that is only because I want video HW accel (ffmpeg codecs) to work. Otherwise Armbian edge or current offers better stability IMO. Simple tests show that DRAM speed for RK3588 is same or better as for old Intel Core I7, so with also up to 32GB, is great KVM server and desktop same as that old Intel boxes, but 4 Watt idle instead of 40 Watt or so. 40W means about 40 * 9000 is 360 kWh per year, that is 108 Euros per year for my energy contract (30 cents per kWh).

This is the current normal version output: Linux orangepizero3 5.4.125 #1.0.8 SMP Wed Mar 19 23:35:12 CST 2025 aarch64 aarch64 aarch64 GNU/Linux To investigate this issue, I continued to use Armbian_25.5.2_Orangepizero3_bookworm_current_6.12.30-homeassistant_minimal.img Then uname -a output: Linux orangepizero3 6.12.30-current-sunxi64 #2 SMP Thu May 22 12:29:54 UTC 2025 aarch64 GNU/Linux

The historical archive of armbian orange pi zero 3 seems to have been lost. I am currently using the 5.4 official image.

anything 'interesting' in dmesg? and what is the Armbian / kernel version? e.g. uname -a btw 'real' armbian is currently at linux version 6.12.x https://www.armbian.com/orange-pi-zero-3/ btw I disabled wpa_supplicant when I run hostapd, I'm not sure if it'd affect anything, normally hostapd should work with wpa_supplicant running should be 'no problem'. wpa_supplicant is 'connecting out', while hostapd is an AP hotspot.

It depends on what kind of- and if- HW I/O is used. USB can be redirected. PCI-E can be re-allocated from host to VM when proper IOMMU (HW) is there, that I only go working for Intel PCs, there is interest in it for ARM64, but so far haven't seen anyone got that working. Other typical SBC HW I/O like SPI, 1-wire, GPIO high-low toggle, etc, can not be virtualized, so not available to a VM. Same for video codecs HW accell blocks. Storage and networking, all things typically relevant for enterprise/servers, is no issue.

Has anyone encountered this problem? I reproduced this problem on the 6.1 kernel image, and finally I returned to the 5.4 historical image, and hostapd ran normally.

I tried the following commands, but none of them worked. Only when I rebooted the device did hostapd start correctly. ip link set wlan0 down ip link set wlan0 up rfkill unblock wifi systemctl stop NetworkManager systemctl stop wpa_supplicant

It doesn't work. The wlan0 status is on. I think it's a kernel driver problem.

Welcome / Witaj! Plenty of options for quick and easy start: https://docs.armbian.com/User-Guide_Armbian-Software/ Those small things can do big things

try ip link set wlan0 up

I hope you have realistic expectations - I can only share tips and ideas - fixing is common problem in best effort way. This is most likely related to PCI driver. Which was done badly, its fragile since the day one. Try alternative kernels - and if you find a stable one, report back to forums. This might help nail down this problem.

Here you should have all the debs, you will have to install them manually. Start with media-buster-legacy-rk3328, and then install manually all the deps https://mega.nz/file/RnBQWbBJ#bpVSDcqjatbpwIlKMRopnzSh01ebOxzbMRh1UJ2zBBE

Every time the device is turned on, I can start hostapd for the first time. When I ctrl-terminate, the next time I start hostapd, I get an error message: Failed to set beacon parameters Interface initialization failed wlan0: interface state UNINITIALIZED->DISABLED wlan0: AP-DISABLED wlan0: Unable to setup interface. wlan0: interface state DISABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING hostapd_free_hapd_data: Interface wlan0 wasn't started nl80211: deinit ifname=wlan0 disabled_11b_rates=0

I have seen other threads where they recompile mesa to get an updated so module for X11, related to LCD panels and DRM. I haven't had time for that yet.

Testing under 6.15-sunxi and unable to load the module at all. ryan@pcduino3:~/exp-drivers/hello$ sudo insmod hello.ko insmod: ERROR: could not insert module hello.ko: Invalid module format ryan@pcduino3:~/exp-drivers/hello$ sudo dmesg | tail -n 1 [ 2002.550246] module hello: .gnu.linkonce.this_module section size must match the kernel's built struct module size at run time ryan@pcduino3:~/exp-drivers/hello$ I am now wonder Is this tied to a configuration issue? Or is it something more deeper routed? One other thing I will try is bumping up GCC as AI suggest it could be a mismatch issue as the Build system uses GCC 13 but Debian comes with GCC 12. I will also try building with an Ubuntu distro as well.

The Tanix-tx6s-axp313 image goes straight to fel, no serial logs

Ok, I'll try all of them. I'll report back tomorrow.

Hi wel7on, I see based on the image provided that you have an unpopulated serial console port (RX, TX and GND labels). If you are up for it I would recommend soldering a header to it and if you dont already buy a usb to serial converter. Makes it easier to identify why the board may not appear to be booting. You can use a program such as putty to recieve the serial debug output. Best of luck Ryzer

Try the Transpeed, vontar, x98h orTanix-acp313 images. There might be few other boxes that use axp313 chip in the list.

Alright, that took a little bit to find, that chip is small! AXP313A pc21BAA 64N1

Would this be a viable pathway to run Frigate NVR with HA/HAOS?

And here is an armbian-monitor with verbosity set to 7: https://paste.armbian.com/ubuxilosap

Thank you for your reply Igor, I have not changed anything, its using the same power supply it has been using for the past years! I had the SSH terminal open on it and just saw this random output: Message from syslogd@nanopim4v2 at Jul 24 20:22:20 ... kernel:[169328.590321] Internal error: Oops: 0000000096000004 [#2] PREEMPT SMP Message from syslogd@nanopim4v2 at Jul 24 20:22:20 ... kernel:[169328.616489] Code: 54000088 14000011 f9400273 b40001f3 (b9401a63) Not sure if it helps, but afterwards I took a new armbian-monitor capture: https://paste.armbian.com/huzanoyifi

I Know this thread is old but i installer buster on my rk3318 box and the media-buster-legacy-rk3328 package does not exist anymore does anyone have a archive of it