#blackscreen while booting after update

1 messages · Page 1 of 1 (latest)

hybrid plover
#

Booting in recovery mode works but if i try to boot normally I just get a black screen. Last time I used the Device I used the Update Manager to update. I'm running dual boot with grub. I've been using it for around 3 months with no issues. How can i fix/find out what the issue is?

dim cape
#

the only way i could boot into normal mode without the black screen was adding the parameter 'nomodeset' , altho the forums advice not to use it as a permanent solution, i can't still find another way so until i find out what wrong that's what i'm relying on

hybrid plover
#

Ive read about that too but I didnt manage to get it working. Im Not sure tho If i set the Parameter right. What worked for me was using a version with another kernel. I think its the one with 115 at the end.

dim cape
#

can i ask what you did exactly?

hybrid plover
#

Sure i'll get back to you in Like 30 minutes

dim cape
#

that's ok take your time, i'm very thankful if you're willing to help :))

#

also yeah i just checked and my my kernel has 112 in it not 115

brisk wing
#

The nomodeset option can help with the black screen issue. Once you are booted into the system, you want to look at Driver Manager and see if it has any alternative drivers for you. Spoiler: nvidia users usually want the official nvidia one, but there is a reason many Linux users hate it.

ebon gate
#

try -> sudo ubuntu-drivers devices

#

then do -> sudo apt-get install "nvidia_(Versionnr)"

hybrid plover
brisk wing
ebon gate
#

try pressing alt +F3 to get textconsole if you have black screen. then do "startx" and look for returned errors

brisk wing
hybrid plover
ebon gate
#

check your home folder permission rights

brisk wing
hybrid plover
ebon gate
#

often on update the rights for Xconfig goes to trash

#

then the xserver cant start properly

brisk wing
ebon gate
#

oh on boot? or on login?

brisk wing
#

This sounds like the recent nvidia driver regression. It hit some users with specific configurations.

ebon gate
#

if it is on boot then your grubs conf is broken maybe

#

try reinstall grubs and do grup update

dim cape
brisk wing
ebon gate
#

try booting with "amdgpu.dc=0"

dim cape
brisk wing
# ebon gate try booting with "amdgpu.dc=0"

I appreciate you trying to help, but you really should try to get some information about the system before you tell people to change settings. Unless you are certain you found the issue.

brisk wing
brisk wing
#

Are you on Linux Mint?

ebon gate
#

Been dealing with a blank screen right after boot on the same cause for days (different versions of Ubuntu-Kubuntu-LinuxMint-CentOS (both 32 and 64 bits), until I read a post on Reddit and passed this kernel parameter at boot time:

amdgpu.dc=0

dim cape
#

my bad i misspelled it forgot an x omggg

ebon gate
#

this should help ->
To temporarily add a boot parameter to a kernel
Start your system and wait for the GRUB menu to show (if you don't see a GRUB menu, press and hold the left Shift key right after starting the system).
Now highlight the kernel you want to use, and press the e key. You should be able to see and edit the commands associated with the highlighted kernel.
Go down to the line starting with linux and add your parameter foo=bar to its end.
Now press Ctrl + x to boot.
To make this change permanent
From a terminal (or after pressing Alt + F2) run:

gksudo gedit /etc/default/grub
(or use sudo nano if gksudo or gedit are not available) and enter your password.

Find the line starting with GRUB_CMDLINE_LINUX_DEFAULT and append foo=bar to its end. For example:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash foo=bar"
Save the file and close the editor.

Finally, start a terminal and run:

sudo update-grub
to update GRUB's configuration file (you probably need to enter your password).

On the next reboot, the kernel should be started with the boot parameter. To permanently remove it, simply remove the parameter from GRUB_CMDLINE_LINUX_DEFAULT and run sudo update-grub again.

To verify your changes, you can see exactly what parameters your kernel booted with by executing cat /proc/cmdline.

hybrid plover
brisk wing
ebon gate
#

lol read my text its exactly your problem

brisk wing
ebon gate
#

do boot temporary with the kernel parameter i wrote

#

then so the steps in the text abouve

#

to fix this permanentlky

dim cape
#

Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
vendor: Lenovo driver: N/A pcie: speed: 8 GT/s lanes: 16 bus-ID: 02:00.0
chip-ID: 1002:15d8 class-ID: 0300
Device-2: Syntek Integrated Camera type: USB driver: uvcvideo
bus-ID: 1-5:2 chip-ID: 174f:1176 class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,vesa
unloaded: fbdev,modesetting,radeon gpu: N/A display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
s-diag: 414mm (16.3")
Monitor-1: default res: 1366x768 hz: 76 size: N/A
OpenGL: renderer: llvmpipe (LLVM 15.0.7 256 bits)
v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes

#

here's the output

ebon gate
hybrid plover
ebon gate
#

look for the green hook

brisk wing
hybrid plover
#

ok sure, im just weirded out because it has been working fine for over 2 months. thanks anyway

brisk wing
brisk wing
brisk wing
# dim cape yes

You probably have Secure Boot or Fast Startup enabled, which tends to lock up your system and cause issues with Linux.

dim cape
dim cape
#

ok i made sure secure boot is off and disabled fast startup, if i go back into mint and remove nomodeset parameter it should boot just fine?

brisk wing
#

It might. Your Vega iGPU usually runs flawlessly with Linux.

#

If it does not, you may want to upgrade your kernel to a newer version. But test it first.

dim cape
#

ok one minute

#

moment of truth i'm rebooting rn

#

haha nope

#

black screen again

dim cape
brisk wing
#

In Update Manager, select "View > Linux kernels". You will see that you are up-to-date on the branch you are using, but there are newer branches.

dim cape
#

or, one more thing, on the grub menu there are 4 options 2 being linux 5.15.0-112 generic ( and recovery) and the other 2 linux 5.15.0-91, i havent tried the 91 one

brisk wing
#

That is just an older version of the 5.15 LTS kernel you used previously. If that one worked, you can keep using it.

dim cape
#

oh it worked

dim cape
#

i will stick to this solution until an update is available i guess

brisk wing
#

You can use the 6.5 kernel, I use it on all my Mint installs. Or stick with the known working one.

dim cape
dim cape
brisk wing
#

Sure. Please make sure to make your own thread next time, even if somebody else's issue looks similar to yours.

dim cape
brisk wing
#

No worries, just remember it next time.