Hi @ FriendlyELEC,
this is to notify you that at least the USB update image
RK3588-FriendlyElec -> 01_Official images -> 03_USB upgrade images -> (at least)
a) rk3588-usb-debian-bullseye-core-arm64-20230403.zip and
b) rk3588-usb-debian-bullseye-core-arm64-20230412.zip
is unusable, because direct root user login seems to be disabled (which is a good thing), but the "pi" user (which is existing) seems to have a password different from the documented "pi" - at least, all attempts to log in via console do fail - and sshd seems not to be running yet in the "core" image.
So basically what you get is a login prompt, but logging in "pi" fails, and no other user is allowed to login => system is unusable.
So please fix this using either of two alternatives:
a) provide the correct password for "pi" for the existing image (which must be something other than "pi"...), or
b) provide a new fixed Debian 11 "core" image which has been double-checked before publishing that password of user "pi" now indeed is "pi" as it should have been.
Many thanks in advance for addressing/fixing this!
Best regards,
awl29
this is to notify you that at least the USB update image
RK3588-FriendlyElec -> 01_Official images -> 03_USB upgrade images -> (at least)
a) rk3588-usb-debian-bullseye-core-arm64-20230403.zip and
b) rk3588-usb-debian-bullseye-core-arm64-20230412.zip
is unusable, because direct root user login seems to be disabled (which is a good thing), but the "pi" user (which is existing) seems to have a password different from the documented "pi" - at least, all attempts to log in via console do fail - and sshd seems not to be running yet in the "core" image.
So basically what you get is a login prompt, but logging in "pi" fails, and no other user is allowed to login => system is unusable.
So please fix this using either of two alternatives:
a) provide the correct password for "pi" for the existing image (which must be something other than "pi"...), or
b) provide a new fixed Debian 11 "core" image which has been double-checked before publishing that password of user "pi" now indeed is "pi" as it should have been.
Many thanks in advance for addressing/fixing this!
Best regards,
awl29