Walter Zambotti

I have been trying to diagnose a QHYCCD camera problem on a N2 running INDI server. Everything appears to work fine but after several minutes the device fails to respond. The device is only supported by QHY on a true USB3 slot. Looking on other forums USB and cable stability are a common problem with these QHY devices so falling onto the wrong USB bus would definitely be a problem. However looking at lsusb I can see the device has dropped onto the wrong USB bus: $ lsusb Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04a9:3217 Canon, Inc. Canon Digital Camera Bus 001 Device 008: ID 1618:0716 QHYCCD QHY715U3G20-20230106 Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics CH340 serial converter Bus 001 Device 005: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey] Bus 001 Device 004: ID 0483:5740 STMicroelectronics Virtual COM Port Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The QHYCCD is showing up on USB bus 1 (which I'm sure is the USB2 480M) Confirmed here by lsusb -ttv $ lsusb -ttv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 1: Dev 4, If 0, Class=Communications, Driver=cdc_acm, 12M ID 0483:5740 STMicroelectronics Virtual COM Port |__ Port 1: Dev 4, If 1, Class=CDC Data, Driver=cdc_acm, 12M ID 0483:5740 STMicroelectronics Virtual COM Port |__ Port 2: Dev 5, If 0, Class=Vendor Specific Class, Driver=rtl88x2bu, 480M ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey] |__ Port 3: Dev 6, If 0, Class=Vendor Specific Class, Driver=ch341, 12M ID 1a86:7523 QinHeng Electronics CH340 serial converter |__ Port 4: Dev 8, If 0, Class=Vendor Specific Class, Driver=usbfs, 480M ID 1618:0716 |__ Port 2: Dev 2, If 0, Class=Imaging, Driver=usbfs, 480M ID 04a9:3217 Canon, Inc. I'm running the Armbian version of Ubuntu 22.04 with kernel 6.12.22 Linux odroidn2-1 6.12.22-current-meson64 #1 SMP PREEMPT Mon Apr 7 08:08:37 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux. Further : This only occurs if the USB3 device is connected during boot. If the same USB3 device is plugged in well after boot it is correctly detected as a HIGH speed USB device. I'm looking for any ideas on forcing this device to be detected as a high speed USB3 device during boot time. So I don;t have to keep remembering to unplug and plug it back in. Also posted in the Odroid and INDI forums. Further update : More testing shows the boot selection for USB bus is random. Sometimes the device is detected as USB2 and other times USB3. Walter Zambotti N2 - 22.04 Armbian xfce desktop N2+ - CoreElec KODI

I'm such a dill. armbian-config system add-headers Downloaded the correct headers.

I'm a little confused. I went to repeat this for another board but it built the headers for entirely different version 6.12.16 instead of 6.6.63. Where in the compile.sh command is the required version specified or determined?

@Solskogen You didn't mention whether you also did the final apt upgrade after changing the line /boot/armbianEnv.txt. Did you?

I know have my qhyccd drivers installed and working. Thanks so much

I am having trouble installing specific hardware dkms because the dkms requires the linux header files for the installed kernel version which are not available or do not exist. Armbian 23.05.1 Ubuntu 22.04 desktop version is build with kernel 6.6.63 but an apt search for the relevant headers finds none. Headers exist for 6.2, 6.5 and 6.8 but not for 6.6. How can I address this?

After an update to Armbian 23.05.1 Ubuntu one of my Wifi adapters no longer sees any access point and can't be forced to connect blindly. The two adapters are very similar: The two adapters are very similar: Working Wifi Module 5B: |__ Port 2: Dev 9, If 2, Class=Vendor Specific Class, Driver=rtl8821cu, 480M ID 0bda:c820 Realtek Semiconductor Corp. /sys/bus/usb/devices/1-1.2 /dev/bus/usb/001/009 Not working Wifi Module 5A: |__ Port 4: Dev 10, If 0, Class=Vendor Specific Class, Driver=rtl88XXau, 480M ID 0bda:a811 Realtek Semiconductor Corp. RTL8811AU 802.11a/b/g/n/ac WLAN Adapter /sys/bus/usb/devices/1-1.4 /dev/bus/usb/001/010``` nmcli shows both devices nmcli device DEVICE TYPE STATE CONNECTION wlx200bd04dc584 wifi connected asuszamb 2 wlx40a5eff399ea wifi disconnected -- p2p-dev-wlx200bd04dc584 wifi-p2p disconnected -- p2p-dev-wlx40a5eff399ea wifi-p2p disconnected -- eth0 ethernet unavailable -- lo loopback unmanaged -- wlx40a5eff399ea is the device that has stopped working. if I display the access points visible to each device: nmcli device wifi list ifname wlx200bd04dc584 IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY 3C:7C:3F:6B:EA:2C asuszamb Infra 36 540 Mbit/s 95 ▂▄▆█ WPA2 3C:7C:3F:6B:EA:28 asuszamb Infra 2 405 Mbit/s 74 ▂▄▆_ WPA2 32:46:9A:FF:E2:B9 asuszamb_EXT Infra 10 130 Mbit/s 64 ▂▄▆_ WPA2 4C:0F:6E:AD:AB:07 PS3-1880660 Infra 10 54 Mbit/s 39 ▂▄__ WPA1 6A:19:4D:28:72:DD -- Infra 161 540 Mbit/s 25 ▂___ WPA2 B0:92:4A:C7:E2:BD OPTUS_C7E2BBM Infra 11 540 Mbit/s 20 ▂___ WPA2 WPA3 72:19:4D:28:72:DC OPTUS_C7E2BBM Infra 11 130 Mbit/s 17 ▂___ WPA2 WPA3``` The other adapter should show the same access points but: nmcli device wifi list ifname wlx40a5eff399ea IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY Attempting to make a connection via the not working adapter results in: nmcli con up 175a67a0-d58d-4ebe-8d02-6f3c741c460b ap 3C:7C:3F:6B:EA:2C ifname wlx40a5eff399ea Error: device 'wlx40a5eff399ea' not compatible with connection 'asuszamb'.

I would like to update/upgrade to the latest dist for the Armbian N2 without completely re-installing. Is this supported and possible?In order to update to the latest Armbian

The problem turns out to be the kernel version. The minimal image comes with 6.1.30 which provides a new video device (called None-1) and the desktop image comes with 6.1.11 which does not have this mystery video device. All working with the reverted kernel.

Seems the fix is to use kernel 6.1.11 that comes with the desktop version and not 6.1.30 that comes with the minimal version.

it turns out this mystery video device (None-1) is provided by Kernel 6.1.30 and revertiong back to 6.1.11removes the device.

So I edited the boot.cmd file and added this line after each of the setenv bootarg ... lines : setenv bootargs "${bootargs} video=None-1:d" recompiled with sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr checked the lines had made it to boot.scr and rebooted. But the None-1 video device still persists and xrandr still shows that device is being used by Xorg!!!

I am unable to configure Xorg to ignore (and stop using as its default) the None-1 video device causing me not to be able to display a desktop via the HMDI-1-1 device. It has been suggested (https://ubuntu-mate.community/t/how-to-configure-xorg/26732/3) that I disable this device in the kernel, hopefully, via a kernel option such as : video=None-1:d Does anyone know where (which file) and how (specific method) I should do this?

Armbian 23.5 Ubuntu Not sure what I touched but my OpenGL has reverted from the Mali-G52 hardware accelerated renderer back to the llvmpipe. How can I changed this?

I have multiple n2s and I don't want them all to be called odroidn2. What is the recommended way to change the hostname of an armbian system?