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.
# 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
It is useful to know, but doing as instructed in post #69 you seem to have ignored.
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:"
My question was:
What do I have to do when there is no panic.
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.
I shall boot
stop with e
and print here the line starting with linux.
The line:
Code:
linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro quiet
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.
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:
Do you anticipate wishing to use resume function with this Debian installation?
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:
Code:
sudo sed -i 's/quiet/noresume quiet/g' /etc/default/grub
and follow up with:
Code:
sudo grub-mkconfig -o /boot/grub/grub.cfg
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:
Code:
sudo sed -i 's/quiet/noresume quiet/g' /boot/grub/grub.cfg
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.
Last edited by mrmazda; 01-11-2024 at 01:47 AM.
Reason: Last suggested process was incomplete, and still may be.
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.
Last edited by beginstart; 01-11-2024 at 10:52 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.