ambiamber

Thanks. $ curl -I https://apt.armbian.com/ HTTP/2 302 server: nginx/1.18.0 date: Mon, 21 Nov 2022 03:21:43 GMT location: https://mirror-us-stl1.armbian.airframes.io/apt/ x-geo-distance: 1156601.990045 $ sudo traceroute -T -p 80 mirror-us-stl1.armbian.airframes.io | tail -n 1 9 vmi1019518.contaboserver.net (154.38.161.119) 39.270 ms 39.239 ms giga-hostin.ear7.chicago2.level3.net (4.1.49.166) 38.339 ms $ sudo traceroute -T -p 80 mirror.albony.xyz | tail -n 1 11 172.67.136.25 (172.67.136.25) 14.596 ms 14.433 ms 15.490 ms The reflector selected mirror-us-stl1.armbian.airframes.io but mirror.albony.xyz has less than half as much latency, but more hops.

Thanks. It's not stated that you can filter on regions using jq: curl -s http://apt.armbian.com/mirrors | jq -r '.NA[]' http://armbian.tnahosting.net/apt/ http://mirror-us-sea2.armbian.airframes.io/apt/ http://mirror-us-sea1.armbian.airframes.io/apt/ http://mirror.albony.xyz/armbian/ http://mirror-us-stl1.armbian.airframes.io/apt/ http://mirror-us-phx1.armbian.airframes.io/apt/ http://mirrors.jevincanders.net/armbian/apt/ http://armbian.chi.auroradev.org/apt/ http://armbian.lv.auroradev.org/apt/

Not a feature request, I'm just curious about why things are like this. Context around the error message Line 170: tries to enable ACS but CONFIG_ACS disabled 1 errors found in configuration file '/etc/hostapd/hostapd-5.conf' Failed to set up interface with /etc/hostapd/hostapd-5.conf Failed to initialize interface Most relevant part of hostapd-5.conf ... hw_mode=any ... channel=acs_survey ... Probably the root cause of this $ apt source hostapd ... $ grep CONFIG_ACS wpa-2.10/hostapd/defconfig #CONFIG_ACS=y So my question is, why is CONFIG_ACS disabled when having Automatic Channel Selection (ACS) is useful? Thanks, KES

Two things about my virt-manager setup: Every time the kernel package(s) get updated you will need to do the virt-copy-out extraction and update the Kernel path, etc. in virt-manager. I tried to use UEFI but I got stuck at the UEFI shell with no fs0:> (does anyone have any suggestions about how to configure the qemu images to use UEFI?)

I am able to use virt-manager with Armbian_22.11.0-trunk_Virtual-qemu_sid_current_5.10.148.img Since I could not find anything about that I'll post what I did to make it work. You will need the edk2 firmware, guestfish and qemu-system-aarch64 programs. Find the names of the kernel and initrd $ sudo virt-ls -a Armbian_22.11.0-trunk_Virtual-qemu_sid_current_5.10.148.img /boot/ | grep -E 'vmlinuz|initrd.img' initrd.img-5.10.148-virtual vmlinuz-5.10.148-virtual Copy them out of the qcow2 $ sudo virt-copy-out -a Armbian_22.11.0-trunk_Virtual-qemu_sid_current_5.10.148.img /boot/vmlinuz-5.10.148-virtual /boot/initrd.img-5.10.148-virtual . Find the UUID of the root file system $ sudo virt-cat -a Armbian_22.11.0-trunk_Virtual-qemu_sid_current_5.10.148.img /etc/fstab UUID=99cf7ecb-0abb-48cb-a603-475171df5fc3 / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 Create a VM using virt-manager: New-> Import disk image and Architecture options aarch64 Provide the exiting storage path: use the file browser to select the img file. Choose the operating system you are installing: debian-testing (there isn't a sid option as of yet). On the Ready to begin installation screen check the Customize configuration before install In virt-manager: Show Hardware Details (View->details or click the lightbulb icon) -> Boot options -> check Enable direct kernel boot Fill in the Kernel path and Initrd path with the files you got from virt-copy-out. Fill in the Kernel args with earlyprintk loglevel=8 root=UUID=99cf7ecb-0abb-48cb-a603-475171df5fc3 rw rootfstype=ext4 But use the UUID from the fstab. At this point you can start the VM.

Either that or the base installation should not have the haveged package installed anymore, unless there are special cases where the kernel version is less than 5.6.

The official GitHub page for haveged says: Fedora and Arch both have a test for the kernel version in haveged.service: ConditionKernelVersion=<5.6 I put a complete example of haveged.service in this GitHub Gist for the convenience of anyone reading this post. https://gist.github.com/ambiamber/0d99cc5c8f79a72633acf39c443f5f2f I got here because on a fresh installation "systemctl status" showed "degraded" because haveged failed to start (which is correct because it shouldn't start). Upstream bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999811

Thanks but the answer turned out to be that I was using u-boot-clearfog-base-mmc.kwb But the DSA switch requires u-boot-clearfog-pro-mmc.kwb U-Boot 2013.01-g1e88e63-dirty (Jul 20 2016 - 21:38:48) Marvell version: 2015_T1.0p11 I have to admit that eth1 is up now but I didn't do anything to bring it up. $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1024 link/ether 02:b3:7f:ac:38:c4 brd ff:ff:ff:ff:ff:ff inet 10.10.10.10/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0 valid_lft 29704sec preferred_lft 29704sec inet6 fdee:207b:f0ce::6ba/128 scope global dynamic noprefixroute valid_lft 28424sec preferred_lft 28424sec inet6 fdee:207b:f0ce:0:7b29:63c:40fc:4405/64 scope global noprefixroute valid_lft forever preferred_lft forever inet6 fe80::e1d8:2674:2151:93fc/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1508 qdisc mq state UP group default qlen 1024 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff inet6 fe80::107b:c0f4:532e:9166/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1024 link/ether 00:50:43:0d:19:18 brd ff:ff:ff:ff:ff:ff 5: lan5@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 6: lan4@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 7: lan3@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 8: lan2@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 9: lan1@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 10: lan6@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff inet6 fe80::a2ae:94e4:ccf5:6673/64 scope link noprefixroute valid_lft forever preferred_lft forever $ cat /etc/network/interfaces source /etc/network/interfaces.d/* # Network is managed by Network manager auto lo iface lo inet loopback $ ls /etc/network/interfaces.d $ (nothing)

Hello to you! I was using Arch Linux ARM on my Clearfog Pro for years. Then things got bad. I think it's a bad combination to have a distro with the most up-to-date software while developers are rapidly abandoning and not testing 32-bit Linux software. First wget became incompatible with gnutls and then programs in coreutils that use utmp started malfunctioning. The last straw was the system became unbootable, issuing a message about ext4 "ext4fs_devread read outside partition 18446744073709551440". I switched to Armbian but now I'm at a loss as to how to configure DSA on the Clearfog Pro. I installed the mv88e6xxx but the LAN ports on the DSA switch did not come to life. sudo modprobe mv88e6xxx Module Size Used by +mv88e6xxx 139264 0 +dsa_core 61440 1 mv88e6xxx +hsr 28672 1 dsa_core +bridge 163840 2 mv88e6xxx,dsa_core +stp 16384 1 bridge +llc 16384 2 bridge,stp rfkill 20480 1 lz4hc 16384 0 lz4 16384 0 $ networkctl -a WARNING: systemd-networkd is not running, output will be incomplete. IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback n/a unmanaged 2 eth0 ether n/a unmanaged 3 eth1 ether n/a unmanaged 4 eth2 ether n/a unmanaged 4 links listed. $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1024 link/ether 02:b3:7f:ac:38:c4 brd ff:ff:ff:ff:ff:ff inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0 valid_lft 39361sec preferred_lft 39361sec inet6 fdee:207b:f0ce::6ba/128 scope global dynamic noprefixroute valid_lft 39363sec preferred_lft 39363sec inet6 fdee:207b:f0ce:0:7b29:63c:40fc:4405/64 scope global noprefixroute valid_lft forever preferred_lft forever inet6 fe80::e1d8:2674:2151:93fc/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1024 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1024 link/ether 00:50:43:0d:19:18 brd ff:ff:ff:ff:ff:ff Back when it was working on Arch Linux ARM I would see this $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 4e:ea:ed:f3:18:fb brd ff:ff:ff:ff:ff:ff inet 192.168.0.8/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever inet6 2601:14a:600:6420:4cea:edff:fef3:18fb/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 3069586540sec preferred_lft 3069586540sec inet6 fe80::4cea:edff:fef3:18fb/64 scope link valid_lft forever preferred_lft forever 3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 532 link/ether 00:50:43:00:05:01 brd ff:ff:ff:ff:ff:ff 4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff inet6 fe80::250:43ff:fe00:1/64 scope link valid_lft forever preferred_lft forever 5: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 532 link/ether 00:50:43:05:00:00 brd ff:ff:ff:ff:ff:ff 6: lan5@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff 7: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:c0:ca:95:8b:89 brd ff:ff:ff:ff:ff:ff 8: lan4@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff 9: lan3@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff 10: lan2@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff 11: lan1@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff 12: lan6@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff Does anyone know what I should do to bring up the DSA? Best Regards, KES