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.
I don't believe rescue mode can allow you to do anything that recovery mode cannot.
It's possible some component in your 15 year old computer is failing that is not used or is not heavily used when you boot in recovery mode, possibly memory. In your advanced options section of your Grub menu there may be an option to test memory. If you have it, try using it for 4 or more hours. Letting it run overnight would be a good thorough test.
Let's be sure everyone equates the same meaning when you write "panic". Do you see the word "panic" on your screen when boot fails, or are you simply using "panic" to describe the failure of your login manager or other working GUI environment to appear on your screen? If the word "panic" does not appear, please describe what you mean when you write "panic".
It appears you have not yet told us which GPU your computer has. Please paste input/output here within code tags from running the command inxi -GSIaz. If this gives an error message other than command not found, try inxi -GSIxxxz instead. If command is not found, run command sudo apt install inxi and then try inxi -GSIaz or inxi -GSIxxxz again. You may redirect command output to file if necessary to make it easier to paste here instead of trying to type, thus: inxi -GSIaz > inxioutput.txt. We need to see English output, so you may need to prepend these commands with the parameter "LANG=C " (don't type the quotes).
Somebody here in the thread did check
the hardware,
it was said: OK.
Second:
Update
and this moment system was killed
so I think the update failed.
Third:
It was said
I do use the wrong kernel
to much old.
How to repair?
4th:
Suggest:
I burn LIVE CD
Debian 12 64 bit
I ll try to boot then.
Which one:
Code:
Installationsanleitung für 64-Bit-PC (AMD64)
Installationsanleitung für 64-Bit-ARM (AArch64)
Installationsanleitung für EABI ARM (armel)
Installationsanleitung für Hard Float ABI ARM (armhf)
Installationsanleitung für 32-Bit-PC (i386)
Installationsanleitung für MIPS (Little endian)
Installationsanleitung für 64-Bit MIPS (Little endian)
Installationsanleitung für POWER Prozessoren
Installationsanleitung für IBM System z
If the LIVE CD is not accepted
shall I start a new thread?
Yes.
Quote:
That LIVE CD
also contains LXDE?
64-Bit-PC (AMD64)
The limited information you provided makes it unreasonably difficult to answer this.
Quote:
Title: I cannot boot Debian?
Possibly, but better to provide a description of what actually does happen in lieu of what you expected.
Quote:
How to repair the bad kernel as written above.
Is this not possible?
It probably is possible, but your uncommon posting style makes it very difficult to understand what you did and didn't do, thus difficult to determine what processes should be recommended, proven by the enormous length of this thread. A fresh installation is much easier to describe, and is provided by Debian's own website.
uname -a, uname -r and inxi -S all report the booted kernel. dpkg-query -W | grep linux-image reports the installed kernel(s). 686-pae kernels are 32bit, for use on 32bit installations. amd64 kernels are 64bit. 64bit is the version of Debian 11 and Debian 12 that should be installed on computers that use the Intel E5200 CPU that yours has.
Post #31 suggests you have vmlinuz-5.10.0-15-686-pae already installed. The following comes from one of several Debian 11 installations I have here:
If you cannot properly boot your installed 5.10.0-15-686-pae linux image, it might be due to defective initrd, and thus regenerating it might solve your issue. It's also possible running sudo apt install linux-image-5.15.0-0.bpo.2-686 or sudo apt install linux-image-5.15.0-0.bpo.2-686-pae might solve your issue. sudo apt update && sudo apt-get full-upgrade is another possible solution. Installing the amd64 version of Debian 12 should also solve your issue.
#
# deb cdrom:[Debian GNU/Linux 8.0.0 _Jessie_ - Official i386 xfce-CD Binary-1 20150425-11:43]/ jessie main
# deb cdrom:[Debian GNU/Linux 8.0.0 _Jessie_ - Official i386 xfce-CD Binary-1 20150425-11:43]/ jessie main
# ++deb http://ftp.de.debian.org/debian/ jessie main
# ++deb-src http://ftp.de.debian.org/debian/ jessie main
# ++ deb http://security.debian.org/ jessie/updates main
# ++deb-src http://security.debian.org/ jessie/updates main
# jessie-updates, previously known as 'volatile'
# ++ deb http://ftp.de.debian.org/debian/ jessie-updates main
# ++ eb-src http://ftp.de.debian.org/debian/ jessie-updates main
deb http://deb.debian.org/debian/ bullseye main contrib non-free
#deb http://security.debian.org/debian-security bullseye/updates main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
Is the best and easy way for a newbie
to update
11 to 12?
I found 2 instructions.
Number 1
Code:
sudo apt-mark showhold
sudo apt-mark unhold [name]
sudo apt update && sudo apt full-upgrade
cat /etc/debian_version
deb http://deb.debian.org/debian bullseye main
deb http://deb.debian.org/debian bullseye-updates main
deb http://deb.debian.org/debian-security/ bullseye-security main
sudo sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list
sudo apt upgrade --without-new-pkgs
sudo apt full-upgrade
cat /etc/debian_version
deb http://deb.debian.org/debian buster main
deb-src http://deb.debian.org/debian buster main
deb http://security.debian.org/debian-security buster/updates main
deb-src http://security.debian.org/debian-security buster/updates main
This is mine.
Is the blank wrong?
Code:
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
Post #143 contains the sources.list that should work for Debian 11 Bullseye. This is one that should work:
Code:
deb http://deb.debian.org/debian/ bullseye main non-free contrib
deb http://security.debian.org/debian-security bullseye-security main non-free contrib
deb http://deb.debian.org/debian/ bullseye-updates main non-free contrib
All three lines are needed for an up-to-date and consistent working system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.