Hi
I have setup a new PI-5 with X11 and Bookworm. RealVNC's issues with Wayland has forced me to go that way. Anyway. I have had it working but have somehow borked the booting process. I have been booting the unit and I have had no real issues until I added another user. The second user I want to have admin privileges and not the regular user. I wanted to have a logon remotely that did not wake the unit as my grand daughter uses it and all I want is to administer it remotely once and awhile.
So that is the background. I had all that working (solely from the SSD, MicroSD removed) until I tried to login, remotely, as admin which always awakened her display. Trying to solve that got me in trouble. From an earlier version I moved from a 64GB MicroSD to a 240GB SSD. That was faster and larger, so I like the new setup. I have today booted from the older MicroSD and it opened into a GUI for one user. Using the same ' cmdline.txt ' on the SSD (newer version) it boots me into a console like CLI. (I removed the MicroSD, so the partition UUID would not be confusing the OS).
I though it would work but it did not. I will set out the contents of ' cmdline.txt ' here for clarity. ' console=tty1 root=PARTUUID=11e3941c-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=CA apparmor=1 security=apparmor '. I have done a few upgrades/updates but I thought that would not affect a simple booting setup. I guess I am wrong. Any insight would be appreciated.
Robert
I have setup a new PI-5 with X11 and Bookworm. RealVNC's issues with Wayland has forced me to go that way. Anyway. I have had it working but have somehow borked the booting process. I have been booting the unit and I have had no real issues until I added another user. The second user I want to have admin privileges and not the regular user. I wanted to have a logon remotely that did not wake the unit as my grand daughter uses it and all I want is to administer it remotely once and awhile.
So that is the background. I had all that working (solely from the SSD, MicroSD removed) until I tried to login, remotely, as admin which always awakened her display. Trying to solve that got me in trouble. From an earlier version I moved from a 64GB MicroSD to a 240GB SSD. That was faster and larger, so I like the new setup. I have today booted from the older MicroSD and it opened into a GUI for one user. Using the same ' cmdline.txt ' on the SSD (newer version) it boots me into a console like CLI. (I removed the MicroSD, so the partition UUID would not be confusing the OS).
I though it would work but it did not. I will set out the contents of ' cmdline.txt ' here for clarity. ' console=tty1 root=PARTUUID=11e3941c-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=CA apparmor=1 security=apparmor '. I have done a few upgrades/updates but I thought that would not affect a simple booting setup. I guess I am wrong. Any insight would be appreciated.
Robert
Statistics: Posted by robertdaleweir — Wed Feb 18, 2026 11:09 pm — Replies 0 — Views 16