Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If this hasn't already been tried (I'm not going to read the whole thread again), OP should boot the kernel that does boot, then try building a new initrd.img for the 5.10.0-28-686-pae kernel. Start by logging in as root, then opening /etc/initramfs-tools/initramfs.conf in a text editor, then ensuring that MODULES=most, rather than MODULES=dep, editing if necessary. After than is done, then do:
Code:
update-initramfs -u -k 5.10.0-28-686-pae
then reboot using the default 5.10.0-28-686-pae Grub selection without changing anything.
" /etc/initramfs-tools/initramfs.conf in a text editor, then ensuring that MODULES=most, rather than MODULES=dep, editing if necessary. After than is done, then do:
Code:
update-initramfs -u -k 5.10.0-28-686-pae
then reboot using the default 5.10.0-28-686-pae Grub selection without changing anything. "
Maybe
when there is panic
what do I have to do?
Shall I edit initramfs.conf again the term "MODULES" back?
Thank You.
Last edited by beginstart; 04-20-2024 at 09:21 AM.
I wanted to see that the initrd sizes were appropriately full of possible needs. 63,787,533 should have everything possibly needed.
Try booting by adding nosmp where you had previously put nomodeset at the end of the linu line in the Grub edit menu. If that doesn't help, try again using maxcpus=0 instead.
It sounds to me like the OPs machine may have been in middle of either starting or finishing an up date and getting inpatient the OP may have either performed the ctrl+alt+delete which might be the reason he is having this issue.
The other cause might be that there may have been an un met package dependency which may have had something to do with a file(s) needed at boot time.
Can you take a picture of the entire panic screen and attach it here? There could be a clue there. If not, I'm out of suggestions, other than that your CPU supports the amd64 version of Debian, and the time is overdue to install it in place of the current failing 32bit installation.
Kernel panic can be caused by failing hardware. Your computer is roughly 16 years old. You may investigate obvious hardware failure by removing the cover, then inspecting each of the 7mm diameter or wider electrolytic capacitors for oozing, leaking, or top surfaces that are no longer perfectly flat. Visit badcaps.net to see examples of failures. Any of these you might find are indications of failure. The PSU also contains the same types of caps subject to the same type of failure. Usually one would expect that if any kernel works without panic, then every kernel should work as well. However, there are exceptions to general rules, and this could be one of them.
It's also possible, though unlikely, memory deterioration could lead to panic due to the boot process claiming more RAM with the newer kernels, and always hitting a same bad spot. Memtest86 or memtest86+ tests can reveal whether RAM remains in usable condition. If more than one RAM device is installed, one or more may be temporarily removed in turn to see whether it affects behavior.
While the cover is off, ensure there is no dust accumulation that could cause component overheating, and see to it that all fans work with no broken plastic parts to interfere with cooling and lead to overheat damage.
So do buy a new PC?
But why is Debian running.
At the beginning of this thread there was made a hardware check: No problem.
Ideas:
Clean HD with bleachbit or other cleaning tool?
Update to 12.
And why did appear the problem during/after update?
Does LINUX every step save in a file?
Can we read this file?
Thank You for patient help.
PS
I do clean the PC inside every 6 months.
Only a little bit of dust.
Last edited by beginstart; 04-28-2024 at 06:18 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
