Hi @Igor, I was looking at configng repo and I found this issue: https://github.com/armbian/configng/issues/225. I think that's why I could not find a place to create the sway section in the desktop. In the same I found this in not being planned yet to be made, if ever. Should I look at the Armbian build and try there instead?

What does lsinitramfs say? Is the usb_storage in? This is how it looks here: $ lsinitramfs /boot/initrd.img-6.6.108-current-odroidxu4 | grep usb usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/hid/usbhid usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/hid/usbhid/usbhid.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/i2c/busses/i2c-tiny-usb.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/aqc111.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/asix.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/ax88179_178a.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/catc.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/cdc_eem.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/cdc_ncm.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/ch9200.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/dm9601.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/int51x1.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/kaweth.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/lan78xx.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/mcs7830.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/pegasus.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/rndis_host.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/rtl8150.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/smsc75xx.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/smsc95xx.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/sr9700.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/net/usb/sr9800.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/host usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/host/ehci-fsl.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/host/fsl-mph-dr-of.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/uas.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-alauda.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-cypress.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-datafab.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-eneub6250.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-freecom.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-isd200.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-jumpshot.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-karma.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-onetouch.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-realtek.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-sddr09.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-sddr55.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/ums-usbat.ko usr/lib/modules/6.6.108-current-odroidxu4/kernel/drivers/usb/storage/usb-storage.ko usr/lib/systemd/network/73-usb-net-by-mac.link usr/lib/udev/rules.d/50-usb-realtek-net.rules

Long time no see! This doesn't look right. I checked docents of commits and so far couldn't find anything that would stand out. nand-sata-install only copies / rsync file-system, recreate boot scripts and flash boot-loader if necessary. If usb_storage is missing from initird, its normal that it doesn't boot. Its as module: https://github.com/armbian/build/blob/main/config/kernel/linux-odroidxu4-current.config#L1274 I would say its something to do with initird generation. Could be on the build / distro tools side. @belegdol perhaps knows something?

I've had an OrangePi4 LTS with a 7-inch IPS LCD HDMI jRP7007 external display for three years. Always used it with the stock OrangePi operating system: Debian Bullseye xfce (2022). I had Home Assistant installed and used a desktop client to view cameras and control lights from the touchscreen. Always looked good, and the only problem I had was that Debian didn't have power options, so I couldn't turn off the display; I had to do it manually with a button. The October Home Assistant update completely broke my H.A., it stopped running completely, and when I tried to reinstall it, it threw up errors due to broken dependencies. I tried to repair them, but nothing worked. I simply started looking for a newer version, since the current requirements for H.A. are at least Debian 12. I decided to try Harmony 13 with the XFCE desktop. Everything works great. I installed H.A., Plex, Samba, etc. It took me three days straight to get my entire home automation system back up and running in H.A. H.A.'s encrypted backups took me hours until I found where the key was stored. It later turned out that the full backup wasn't much use since all the sensors had a different ID, and 90% of the things were broken, and the add-ons weren't even in the backup. After a week of struggling, I managed to get everything 100% working. Debian 13 can turn my screen off and back on by touching it with a finger. This is great for quickly interacting with H.A. The screen looks terrible and there are no resolution modes. By default, Debian boots at 1024x768@60Hz. On the Orangepi OS, it runs perfectly at this resolution and everything looks great. It also has another 16:9 resolution mode at 848x480@60Hz. But in Armbian, I only have two modes: 1024x768@60 800x600@60 The first mode, which looks great on OrangePi OS, here has a shaky, blurry image. The second mode, 800x600, looks perfect, but it's too small. The monitor displays signal information. In Armbian, when it boots at 1024x768@60, it appears to be in a different resolution: 987x768@57Hz. That's why it looks so bad. When running at 57Hz, the image shakes, and when rescaling, the screen loses all detail. I followed many tutorials and none of them worked: Use cvt to calculate different resolutions and xrandr to create them. However, any resolution created results in an error when trying to use it. sudo apt install xrandr cvt 1024 600 60 # 1024x600 59.85 Hz (CVT) hsync: 37.35 kHz; pclk: 49.00 MHz Modeline "1024x600_60.00" 49.00 1024 1064 1168 1312 600 603 613 624 -hsync +vsync xrandr --newmode "1024x600_60.00" 49.00 1024 1064 1168 1312 600 603 613 624 -hsync +vsync xrandr --addmode HDMI-1 "1024x600_60.00" xrandr --output HDMI-1 --mode "1024x600_60.00" Use CVT and GTF to calculate the resolutions. I've tried countless resolutions, and it always fails and reverts to the previous one. I can't find a way to make the screen look the way it should. Does anyone have any ideas on how to fix this? I suspect this is a kernel-level issue. Sorry, but I'm using Google Translate. ------------------------------------------------------------------------------------ v25.11 rolling for Orange Pi 4 LTS running Armbian Linux 6.12.53-current-rockchip64 Packages: Debian stable (trixie) Support: for advanced users (rolling release) Containers: addon_491eb00d_hamh, addon_core_duckdns, addon_core_mosquitto, hassio_multicast, hassio_audio, hassio_dns, hassio_cli, homeassistant, hassio_observer, hassio_supervisor Performance: Load: 2% Uptime: 15:06 Memory usage: 56% of 2.90G Zram usage: 7% of 1.45G CPU temp: 38°C Usage of /: 23% of 57G RX today: 184 MiB -------------------------------------------------------------------------------------

Hey! So, when i enter the multitool link it says 404 not found... Is there any new link or smth?