I observe nothing there suggestive of trouble with normal booting.

I'm inserting here for reference the relevant portions of output from the latter two requested commands:Above is a match to comment #35 and looks fine.
Above is a match to fstab. The UUID for sda1 is a cursory match to all instances of UUID= in comment #31. IOW, I still see no evidence of reason why the default Grub stanza would cause kernel panic.

Is there only the Grub rescue boot selection that fails to panic, or do others besides the default also cause panic?

boot where filemanager is working,
open a terminal and post the output of the following:

Thank You for help.



$ ls /boot
config-4.9.0-18-686-pae System.map-4.9.0-18-686-pae
config-5.10.0-13-686-pae System.map-5.10.0-13-686-pae
config-5.10.0-15-686-pae System.map-5.10.0-15-686-pae
grub vmlinuz-4.9.0-18-686-pae
initrd.img-4.9.0-18-686-pae vmlinuz-5.10.0-13-686-pae
initrd.img-5.10.0-13-686-pae vmlinuz-5.10.0-15-686-pae
initrd.img-5.10.0-15-686-pae
$ uname -r
4.9.0-18-686-pae
$ cat /etc/issue
Debian GNU/Linux 11 \n \l


What does this mean?

"Is there only the Grub rescue boot selection that fails to panic, or do others besides the default also cause panic?"



I do boot normal: panic.

I do boot then change to rescue
everything is working
the whole day.

open a terminal and run the following:
If no errors, reboot

I did that:

update-initramfs -u -k 5.10.0-15-686-pae

update-initramfs: Generating /boot/initrd.img-5.10.0-15-686-pae



Then I did booting:
Panic
Sorry.

This shows that the running kernel is from Debian 9 "stretch", two releases behind, so you're getting panics, presumably only when booting 5.10? An incompatible ABI would explain why kernel 4.9 boots where 5.10 panics.

You said you ran upgrades from 7 to 8, you never mentioned upgrades to 9 and 10, though we can see that the upgrade to 9 was at least attempted, not sure about 10? You have no remnant kernels from the Debian 7,8 and 10, so I would suggest the upgrade to 10 was either skipped or never completed. Irrelevant now anyway.

I suspect that some part of the 9 to 10 upgrade was left incomplete and you most likely have some ABI incompatible remnants - it's possible that glibc and many other packages are well behind. You really should have bailed on this one months ago.
This CPU supports amd64: https://ark.intel.com/content/www/us...0-mhz-fsb.html

Consider clean installing 64 bit Debian. I suggest you start backing up your important data and reinstalling from scratch.

As you seem completely out of your depth, I would also suggest enlisting some help. This thread has had over 100 replies and you have been at it since the end of November last year and no further forward.

As several other LQ members have said it would be of great benefit to have the associated log files so that we may better assist you in solving your issue.

Did I understand?
The kernel is
DEBIAN 9
I do use DEBIAN 11--->result crash.

Is this right?
Question:
Do I have to update the kernel?

How can I do it?

I hope we did find my bug.

I did in one step
9 to 10 then to 11
then I did booting
so maybe this was my mistake.

Thank You.

Debian 11 should have 5.10 or 6.1 kernel. If your network is working using rescue boot, you may try in one session:

1. sudo apt clean
2. sudo apt update
3. sudo apt-get upgrade
4. sudo apt-get full-upgrade

This is how I have successfully upgraded my many Debians for many years.

Im sorry.
I do this every week.
No improving.

Explanation:
DEBIAN is doing a lot
but not updating of the kernel.

try this:
reboot

I ll try it. colorpurple21859



mrmazda I did it. Panic again.

Thank You.

This did happen:

mv /boot/initrd.img-5.10.0-15-686-pae/boot/initrd.img-5.10.0-15-686-pae.old

mv: Fehlender Zieldatei‐Operand hinter '/boot/initrd.img-5.10.0-15-686-pae/boot/initrd.img-5.10.0-15-686-pae.old'
„mv --help“ liefert weitere Informationen.
~#*

There is suppose to be a space between -pae and /boot

I would suggest that when someone gives you a command to enter, you copy/paste it to avoid problems such as this. Also, you should probably translate your results to English rather than expecting members here to do it as it is your problem.