On Wed 14 Jan 2026 at 17:44:28 (-0600), [email protected] wrote: > 1. The system upgraded the Debian11 > 5.10.0-36-amd64 by creating 5.10.0-37-amd64.
My experience after doing that is recounted in: https://lists.debian.org/debian-user/2025/12/msg00188.html As you see there, booting the backup kernel, -36-, makes the problem go away while you sort out the NAS problem, if that's unrelated to the upgrade. > 2. After rebooting, the > login screen appeared on the monitor connected to the vga port (which is > common). If this a VC login prompt, or some Display Manager? > 3. When I tried to log into my user account, the screen went > black for almost a second, a screen flashed what appeared to be the screen > described below, and it went back to the log in window. > > 4. I logged in as > root (Old School) successfully. I'm very Old School. Logging in as root on a VC is fine, but I wouldn't do that in a DM. > 5. My user account's home directory was > on a NAS. I changed passwd file to use the local disk as the home > directory. > > 6. I then was successful in logging in as a user. Again, in a VC or with a DM? > 7. In > preparation of installing the NVIDIA drivers, I located the X process. > > 8. > After killing Xwayland, the screen was filled with a very small character > which looked like a small copyright symbols. So it seems likely that you were logged in graphically, and killed X to get back to a VC. The question is which VC. If you boot up and login at a VC, my experience is that VC1 looks normal, but none of the others does. However, in their weird state, they still accept and execute what you type as normal. So I would try circulating around the VCs with whichever keys do that, Alt-arrows or ⊞-arrows typically, and see whether you find a VC that looks normal. > 9. Whenever I typed > anything, it continued to appear as the copyright symbol. > > 10. I logged in > and out. Some of the characters turned green and the rest were either dim > or bright. > > When checking the log files I found the following: > > Warning: > Unsupported maximum keycode 569, clipping. This was reported in 2011 and > 2012. The other related messaged were also present. I assume this is something to do with X and wayland. (I've never used the latter.) > Trying to read, > write, or create a file on the NAS was DENIED. The user number of the file > matched the User's number. Again, does this relate to the upgrade, or is it still a problem when running the older kernel version? > This is my first Debian bug report. I would appreciate knowing to > which package the report should reference. https://lists.debian.org/debian-kernel/2025/12/msg00290.html is a better reference than that given, as there's been some work on finding exactly when this bug arose. (The thread starts at msg00209.html .) I don't know whether there will be a fix soon, but because of that discussion, I haven't filed a bug myself. I only have one machine still running bullseye, but all five heterogeneous machines showed the same problem with -37-. None has the problem when running bookworm or trixie, nor have I seen reports of the bug. Is upgrading the distribution an option for you? Cheers, David.
