I’m confused, you went from “kernel panic” to You got it fixed?

No it is not fixed.

I boot. Crash in panic.

I do boot in rescue mode,
all ist working GIMP Firefox and so on.

Questions:
Could this help?
https://www.debian.org/releases/stab...h08s06.en.html

Is it logic
I do update
then panic
so I did wrong update to Debian 11.

Every week I do "normal" update
also this is working.

Im sorry.

Maybe one of these will help:
https://www.cyberciti.biz/faq/update...n-11-bullseye/
https://phoenixnap.com/kb/upgrade-debian-10-to-11

It is useful to know, but doing as instructed in post #69 you seem to have ignored.

Ib did follow these instructions.

Is the sources.list wrong?

Yes.
Im sorry.

"Login. Is there a login prompt on each of the screens reached by doing Alt-F6, Alt-F4, Alt-F5, Alt-F3 or Alt-F2? If you can login, then do so as root, not your regular username, and try just the following to start with:"


...because there is no login prompt.

Previously you wrote:I was referring to such a situation. Not having panic is good. What exactly happened to cause no panic as you wrote in #67, and what then was on the screen? Only black? What you wrote suggested you did something different before a boot attempt and no panic resulted. Did I misunderstand your post #67?

Sorry,
for bad language.
I wanted to know
if there is no panic,
what do I have to do.
But until now every "normal" booting is panic
abd rescue booting is fine.
Is sources.list ok?
Thank You.

The grub menu entry that allows you to boot and all is working, press e, post what is on the linux line.

According to this handbook, all look OK. Line 2, like the lines I did not quote, is inert, a comment, not used by the packaging system.

There is one difference that I believe should not matter between yours and mine. Where you have on line 3, I haveI don't believe your sources.list has any correlation to your boot problem.

Shall I change sources.list?

I shall boot
stop with e
and print here the line starting with linux.
Thank You.

The line:

linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro quiet

I suggest not.

That looks mostly like we would expect to work if something else is not broken. However, usually there is another parameter that starts with "resume=". Not having that could be producing your trouble. So to test if that is the case, on next boot, pretend to do the same thing, but instead of printing that line here, remove "quiet" from that line and put "noresume" in its place before proceeding to boot with F10 key or Ctrl-X keys, and then tell us how boot went along.

Then if that did not help, or not help enough, on next boot try instead adding "nomodeset" and tell us how it went. Then on another boot, try adding both "nomodeset" and "noresume" and tell us how that went.

linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro quiet

Thank You

I manipulate this line
after saying "e".
So

one by one.



linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro noresume

If crash then

linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro nomodeset

If crash then
linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro nomodeset noresume



And if it workes
one of these

I do login with

NAME
password.

The PC has only one user and admin is this user.

Sounds like you have made progress, but your reply falls short of enough detail to recommend what to do next. If noresume alone was adequate to task, then testing further was not necessary. Did noresume alone allow login? If yes, then next step is to answer this question:


If the answer is no, then an expeditious fix would be to edit the file /etc/default/grub's GRUB_CMDLINE_LINUX_DEFAULT= line to include noresume within the quotes, like so:and follow up with:At this point you should be able to complete a normal boot.

If the answer to my question was yes, the best way forward I'm unsure about, because we don't know why the problem occurred. What would work at least until the next kernel upgrade would be this:Follow this by rebooting normally. In this configuration, resuming from suspend will not work. It will be necessary to have noresume be replaced with a proper resume=UUID= parameter in /boot/grub/grub.cfg for resume functionality to be restored. It's possible the next automatic regeneration of /boot/grub/grub.cfg would do that. Easiest way to deal with this may be to simply wait until the next kernel update is installed, then check to see if it was restored to /boot/grub/grub.cfg.

Sorry.

2 questions:
1
Do you anticipate wishing to use resume function with this Debian installation?

What does this mean?

2
Shall I follow post 69
or 89.

Post 69 with questions:




What do I have to do when there is no panic.
Login. Is there a login prompt on each of the screens reached by doing Alt-F6, Alt-F4, Alt-F5, Alt-F3 or Alt-F2?


Isnt it F10?


If you can login, then do so as root, not your regular username, and try just the following to start with:

I do boot in the morning always as root.

Name
password.


Code:
cat /var/log/Xorg.0.log | pastebinit

I do read this file and then I ll do it post here.



Show us exactly what appears on the screen when you do that.


I ll make copy+paste to edit txt file.


It should show a URL. If it does, it's all we need to have in order to see the content of that log file. If you get an error message instead of the URL, we need to see the message.

OK.



Next try this:
Code:
journalctl -b -1 | grep aile | pastebinit
This too should provide a URL that you can show us.

I ll try it.


EDIT:
Sorry I forgot.



linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro noresume

If crash then

linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro nomodeset

If crash then
linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro nomodeset noresume

All 3
made panic.