You are Here:
Linux Lite 7.0 Final Released - See Release Announcement Section



Boot problems - have to use recovery mode every time

Author (Read 5957 times)

0 Members and 2 Guests are viewing this topic.

Re: Boot problems - have to use recovery mode every time
« Reply #4 on: June 06, 2024, 01:04:59 AM »
 

stevef

  • Global Moderator
  • Gold Level Poster
  • *****
  • 915
    Posts
  • Reputation: 162
  • Linux Lite Member
    • View Profile

  • CPU: Intel Core i5-4460

  • MEMORY: 16Gb

  • Kernel: 5.x
Quote
I followed your instructions, after a dry run through in compatibility mode to see how long it took to be able to type, and then, after a 20s pause held the off button down till the system shut down.

After you'd done the 'blind' commands and pressed Ctrl Alt F2 did anything happen ?
If not, it may suggest that the system is not responsive enough for the blind commands to have done anything, which is supported by the lack of the report.txt file.

Quote
This Laptop used to work fine on default install, and then I upgraded from 5.15.0-28. That's when this lot started.
Can you clarify this ?

As Linux Lite 6.0 was released in June 2022 with 5.15.0-33 it's not clear how you were on 5.15.0-28 so need to understand what you are doing.
clueless
 

Re: Boot problems - have to use recovery mode every time
« Reply #3 on: June 05, 2024, 05:58:31 PM »
 

01pjf

  • New to Forums
  • *
  • 4
    Posts
  • Reputation: 0
  • Linux Lite Member
    • View Profile

  • CPU: AMD A6

  • MEMORY: 8Gb

  • VIDEO CARD: Radeon R4
Many thanks for your answer.
I have discovered a couple of things tonight.
Linux mint standard live install does the same thing, with flashing writhing on the screen (but different)
The only way out from Mint or LL default boot is to press and hold the shut-down button and re-start.

This Laptop used to work fine on default install, and then I upgraded from 5.15.0-28. That's when this lot started. It is a bit familiar, as I get the same thing when I try to install Raspian on my Raspberry Pi4. I've ended up trying all the Raspian versions on the live web install system with the same result, and installed Ubuntu on my Pi which runs fine.

So on my Laptop, I invoked LL default boot, and everything was fine until I typed in my password, when it played the tinkly jingle, briefly displayed my desktop screen image, then went to flashy, writhy mode, followed by blank screen of death with backlight on.
No mouse cursor, or panels visible.
I followed your instructions, after a dry run through in compatibility mode to see how long it took to be able to type, and then, after a 20s pause held the off button down till the system shut down. Then I rebooted into compatibility mode and looked for the tee report.txt file in Home.
I was sad to see that it was not present, so it appears that there is no activity behind the scenes, I think. Or I got the timing wrong, but I don't think so.
A shame - I was hopeful of some way forward.
Thanks for your help, though
Pad

PS when I'm in compatibility mode, inxi  reports
Device-1: Advanced Micro Devices [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] driver: N/A
           Display: x11 server: X.Org 1.21.1.4 driver: ati,vesa unloaded: fbdev,modesetting,radeon resolution: 1920x1080~77Hz
           OpenGL: renderer: llvmpipe (LLVM 15.0.7 256 bits) v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2

Does that help?


Has this set up ever worked properly without the flash and writhe and dark display ?
If so, what changed ?
How do you exit from this state ?

If you think the system may be working under the dark display you could try things 'blindly'

For example
Press Ctrl Alt T together
Type in
Code: [Select]
inxi -Fxxx | tee report.txtFollowed by return

Then try pressing Ctrl Alt F2 together.
If things are working, this may switch from the GUI to a terminal type login at which you can enter your credentials.
If it doesn't access the desktop using the recovery mode.

Either way, check for the file called report.txt in your home directory.
If it is there, it proves the system is working blindly and may show what graphics drivers are loading in non-recovery mode.
The command you run blindly can be adapted to get other diagnostic information.
« Last Edit: June 05, 2024, 06:02:43 PM by 01pjf »
 

Re: Boot problems - have to use recovery mode every time
« Reply #2 on: June 04, 2024, 07:51:06 AM »
 

stevef

  • Global Moderator
  • Gold Level Poster
  • *****
  • 915
    Posts
  • Reputation: 162
  • Linux Lite Member
    • View Profile

  • CPU: Intel Core i5-4460

  • MEMORY: 16Gb

  • Kernel: 5.x
Has this set up ever worked properly without the flash and writhe and dark display ?
If so, what changed ?
How do you exit from this state ?

If you think the system may be working under the dark display you could try things 'blindly'

For example
Press Ctrl Alt T together
Type in
Code: [Select]
inxi -Fxxx | tee report.txtFollowed by return

Then try pressing Ctrl Alt F2 together.
If things are working, this may switch from the GUI to a terminal type login at which you can enter your credentials.
If it doesn't access the desktop using the recovery mode.

Either way, check for the file called report.txt in your home directory.
If it is there, it proves the system is working blindly and may show what graphics drivers are loading in non-recovery mode.
The command you run blindly can be adapted to get other diagnostic information.
clueless
 

Boot problems - have to use recovery mode every time
« Reply #1 on: June 04, 2024, 04:15:18 AM »
 

01pjf

  • New to Forums
  • *
  • 4
    Posts
  • Reputation: 0
  • Linux Lite Member
    • View Profile

  • CPU: AMD A6

  • MEMORY: 8Gb

  • VIDEO CARD: Radeon R4
Dear all,
I have a HP HP-Laptop-15-db0xxx which dual boots with windows 10 or Linux Lite 6.6
It defaults to Windows on boot.
I am running Linux-lite and Ununtu 5.15.0-107-generic
To get into Linux, I press esc, wait for the boot loader to pick it up, then F9 to go to the options menu.
I can chose windows, ubuntu or something else that I can't remember.
I chose Ubuntu, and then get an option to run 5.15.0-107, or its recovery mode, and an earlier package or its recovery mode.
The other package doesn't run, so I will delete it in tweaks.
If I boot straight into 5.15.0-107, it loads, but after I type in my password, the screen starts to flash and writhe, and is totally unreadable. After a while it goes dark, but the back light is still on. There is no sign of response to the mouse or the keyboard.
If I boot into 5.15.0-107 recovery mode, and change nothing, then exit recovery mode into Linux from that menu, everything works fine (although I do have to unplug my USB mouse and plug it in again or it doesn't see it.
I think the problem is the screen driver which loads after the password is entered. But I have no idea how to change it to the default one that I'm left with when I boot through recovery mode.
My explanation could be totally up the wrong path, so I would be very happy to hear from anyone who can help this. I'd like to default boot into LL, but I need to correct this error first.

lspci gives me (I hope its' helpful - this is the report after booting through recovery mode. I have no idea what driver is being used when it boots normally, as I can't see what's going on. Caps lock still works, so something is definitely happening; it's just that I can't see it.)

00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) I/O Memory Management Unit
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] (rev ea)

Many thanks,
01PF
 

 

-->
X Close Ad

Linux Lite 7.0 Final Released - See Release Announcement Section