December 16, 2022, 4:50pm
Failing at scanning bus usb@C9000000 for devices failed to get keyboard state from 1a2c:0e24
haha, it says press anykey to stop… but keyboard not found, funny! So it just proceeds to failure and command line after not finding the boot and stuff.
Using the recent s905 xz loaded to a SanDisc 12kgb Extreme Plus running off of laptop usb and micro 2.4 Apple charger. I used Disk Image Writer, appears to be Gnome, to create the sdhc.
Give a boomer a hand, maybe? But type slowly so I can keep up.
December 16, 2022, 6:34pm
Dumb boomer action. There IS a difference between -base- and -desktop-!
As you were, nothing to see here…
Ubuntu Base images offer our smallest and lightest images with just the bare essentials to manage the board hardware and connect to networks. It uses systemd for most basic system services. The default user credentials are as follows:
It will prompt you to change the password after login for security reasons.
Board specific bootloader which not listed in partition table
FAT32 EFI partition 1 with GRUB (/boot/efi)
BTRFS root partition 2 (/)
There shouldn’t be any difference in terms of booting Linux portion. The USB problem could be a power issue or a compatibility issue with that specific keyboard.
December 17, 2022, 12:36pm
For history sake, it was booting to the command line and I could log in.
The problem was my expectation of a friendly full screen of Ubuntu wonderful!
The desktop version fulfilled my dreams so PEBKAC!