pygr Posted December 16, 2023 Share Posted December 16, 2023 (edited) Armbian_23.11.1_Odroidn2_bookworm_current_6.1.63.img.xz was downloaded and flashed to SD card. System booted OK from the SD card and successfully started the OS. Then I used armbian-config to write the root file system to an SSD. After reboot, the system appears to get through the boot stage OK. It also proceeds to start up the OS OK, but then services fail to start. Further action stops temporarily, but pressing the escape key or a function key makes the screen go black for a second or so, returning with what's shown in the last image. No other keys have any effect. The system appears to be locked up and unusable at that point. Edited December 16, 2023 by pygr Merge text and images 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted December 19, 2023 Share Posted December 19, 2023 On 12/16/2023 at 8:59 PM, pygr said: No other keys have any effect. The system appears to be locked up and unusable at that point. Odroid N2 has poor USB implementation. You need to blacklist UAS support (which will slow things down) and it will work. Search forum (or Google) for tips how to do that. 0 Quote Link to comment Share on other sites More sharing options...
pygr Posted December 21, 2023 Author Share Posted December 21, 2023 Hi Igor, Thank you for your suggestion. Unfortunately I couldn't get it to work. 1) Flashed CLI Bookworm image to SD card. 2) Booted up and answered the first startup questions. 3) "lsusb -t" showed uas driver was being used. 4) Edited /boot/armbianEnv.txt, so it now has usbstoragequirks=0x174c:0x55aa:u. 5) Rebooted. "lsusb -t" showed usb-storage was being used instead of uas for an SSD attached through a powered hub. 6) Executed armbian-install. 7) Reboot showed the same behavior as shown in the first post in this thread. 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted December 21, 2023 Share Posted December 21, 2023 5 hours ago, pygr said: so it now has usbstoragequirks=0x174c:0x55aa:u. Perhaps it doesn't work. More resources / ideas / background: https://www.google.com/search?q=blacklist+USB+UAS+armbian https://www.cnx-software.com/2020/08/12/how-to-fix-unreliable-usb-hard-drives-stalled-transfers-linux-windows/ https://leo.leung.xyz/wiki/How_to_disable_USB_Attached_Storage_(UAS) 1 Quote Link to comment Share on other sites More sharing options...
c0rnelius Posted December 21, 2023 Share Posted December 21, 2023 What is the PSU AMPS? I would recommend at least 3A if you are attaching an external drive. 0 Quote Link to comment Share on other sites More sharing options...
pygr Posted December 22, 2023 Author Share Posted December 22, 2023 (edited) A prior version (Armbian_23.5.1_Odroidn2_bookworm_current_6.1.30.img.xz) doesn't show the failures shown in the original post. And for that older version, "lsusb -t" shows the uas driver is being used. To get U-boot to load the kernel, I modified boot.cmd so root_dev is set to the UUID of the SSD file system partition and recompiled with mkimage. I've bitten the bullet and ordered the UART to USB module to see if I can get some better diagnostics from the console. Edited December 22, 2023 by pygr 0 Quote Link to comment Share on other sites More sharing options...
Nitrax Posted December 22, 2023 Share Posted December 22, 2023 There are quite some linux kernel issues with Odroid N2 and USB, there are even issues with home assistant OS after kernel upgrades. Im not technical enough to find the solution so i just hope "someone" does somewhere on the interwebs, in the meantime i run older kernels 😏 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.