Mint black screen after boot

[rough marten]

This morning when I booted my pc Mint as I usually do it could not start, I was stuck with a black screen every time.

Then I held shift in the boot so that i could get the GRUB screen, and booted it in recovery mode. I tried doing the clean command. I tried the older kernel and the newer one too.

Recovery mode boot of the same kernel works, but i don't know what else i can do. Obviously I don't want to stay using this mode, because i can't empty the trash for some reason and the graphics drivers don't work properly (the recovery menu told me that to fix the graphics i need to perform an actual boot, but I can't do that).

I tried restoring a snapshot in timeshift but it didn't have an effect on the booting

[steep tartan]

Can you get into terminal by any way? Try performing a Filesystem check-up which can probably solve this issue

fsck -y /dev/sdaX

Replace /dev/sdaX with the actual root partition (/) of linux mint

Then after the process being completed do exit

[rough marten]

I think this was in the recovery menu and i did that

[steep tartan]

Worked?

If not then,

inxi -G

glxinfo | grep "OpenGL renderer string"

[rough marten]

What's the command to find the name of disk

Like sda what

[steep tartan]

sudo fdisk -l

Then check for mount point /

[steep tartan]

Have you performed file system check-upfsck -y/dev/sdaX

If so

Enter Resume normal boot

If the issue still persist let me know

[rough marten]

"fsck Check all file systems"

[steep tartan]

Enter

Sda1's Mount point is /?

Btw / means root partition

[rough marten]

What do you mean

[steep tartan]

Umm type
sudo fdisk -l

[rough marten]

I just did

[steep tartan]

You should do fsck in sdb3

That's where your Linux file system is

[rough marten]

I thought so, but you said sdaX so i figured it had to be sda

[steep tartan]

lol no problem there's no harm in it

Now try sdb3

[steep tartan]

Btw is it working now?

[rough marten]

Doesn't seem to be

[steep tartan]

I guess yes as I can see in ss

[rough marten]

No

[steep tartan]

So that Desktop?

[rough marten]

That is recovery mode normal boot

[steep tartan]

Taskbar applications

[steep tartan]

Is it after doing Resume normal boot?

Try rebooting it

See if the issue is solved or not

[rough marten]

The whole point of this is so that i can boot properly, not the recovery mode boot cuz that doesn't have everything

[steep tartan]

If no then do fs check-up for sdb3

[steep tartan]

Umm do a normal boot

do you have any idea what caused this issue? By any way

Like did something with graphical card

[steep tartan]

Not a (recovery mode boot)

[rough marten]

Recently i turned off the switch of the pc prematurely because i clicked suspend instead of shut down

[rough marten]

Proper boot doesn't work, black screen again

[steep tartan]

This is what I did while my pc was shifting into tty mode

[rough marten]

Tty?

[steep tartan]

Then same happened as you described black screen on booting

[steep tartan]

CLI

Terminal

[rough marten]

If this happened on windows it would just repair the disk and it'd be done

Or nothing actually

[steep tartan]

Yeah

Btw

Enter into recovery mode

Then fsck -y /dev/sdb3

Have you done this?

[rough marten]

Yes

[steep tartan]

This is how my issue got solved

[rough marten]

The same error as i had in the terminal program

[steep tartan]

Umm

Do you have a Live USB

Probably from that you can do this

[rough marten]

Yes, i tried that but somehow this time that gave another black screen

[steep tartan]

[steep tartan]

Don't even it shows mint logo on booting?

[rough marten]

Last time i used it to reinstall linux mint because of another system-affecting bug which turned my os into ubuntu gnome somehow

[rough marten]

It does

[steep tartan]

Damn this happened to me too

[rough marten]

No way

[steep tartan]

Exactly

I was trying to recover my system through live USB

I did something mount proc etc...

[rough marten]

I hate having to reinstall mint like i have spent so much months adapting to mint and configuring it to my liking, the built in backup tool wouldn't be enough to back up everything, but even if i tried it would take way too long to back up everything

[steep tartan]

That turned

Linux mint cinnamon 22.1 into Ubuntu

[rough marten]

Mine turned into ubuntu after i installed something i forgot

[steep tartan]

Umm

Are you getting something like intramfs

Xorg

Bro try

umount -l /dev/sdb3 through recovery mode then do fsck -y /dev/sdb3 then

exit resume normal boot or reboot

[steep tartan]

@rough marten

[rough marten]

What does mint use instead of wayland? Something like that

[steep tartan]

Then check try booting Linux mint

[steep tartan]

Xorg - by default
Wayland - experimental option

[rough marten]

I think it was a desktop environment but like it was totally unexpected i was just following a tutorial to install something for python

[steep tartan]

Or if it's not unmounting

Try booting into live USB

Open terminal
Do fsck -y /dev/sdb3

[steep tartan]

No it's not a Desktop environment

It's a Display server

[steep tartan]

Something for python? An IDE like idle?

[rough marten]

Idk man i vaguely remember now

[steep tartan]

umount is the correct

You typed unmount

[rough marten]

Ik i corrected it

After the error i typed umount

[steep tartan]

n is the difference

[rough marten]

Ik

Wth

[steep tartan]

Okok error it prompted

[rough marten]

It keeps getting more and more complicated

[steep tartan]

Ok last thing

[rough marten]

I'm thinking of going back to windows 10

[steep tartan]

Can you boot into live USB

[rough marten]

Mint was (kinda) fun while it lasted

[steep tartan]

that can be a option

[rough marten]

Same issue

[steep tartan]

should i call god level professionals? to help you?

gimme permission

[rough marten]

Sure

[steep tartan]

@odd blaze

@median umbra

[rough marten]

Wtf grub sees ubuntu now

[steep tartan]

wait like it happened before?

[rough marten]

I can't say if it happened exactly because i get a black screen obviously

[steep tartan]

can you now try getting into
advance option for ubuntu then recovery mode the try fsck -y /dev/sdb3?

its more like my issue

[steep tartan]

windows not listed in grub menu??

[rough marten]

Another problem but i can use the uefi for that

[steep tartan]

can you try this

also type update-grub in terminal that will scan for available images

[rough marten]

I'm giving up

[steep tartan]

one last try before giving up

with crossed fingers

[rough marten]

I did these

[steep tartan]

what had happened

[rough marten]

Nothing

[steep tartan]

same error or something else

[rough marten]

Same

[lusty cave]

While booting up, when showing the mint or ubuntu logo, press esc on the keyboard and make a video with what it shows on the screen. It should be a drive issue.

[steep tartan]

can you do

sudo mount /dev/sdb3

@rough martenbro

[rough marten]

every time, fsck says this: e2fsck: Cannot continue, aborting.

[steep tartan]

what about sudo mount /dev/sdb3

[rough marten]

Already mounted

[steep tartan]

nd is it still saying ubuntu

[rough marten]

Picture is taking ages to send

[rough marten]

No nvm that, i turned off CSM then turned it on again now

[steep tartan]

oh got it you can describe it in text format now

[lusty cave]

Who is CCBACK? (it says failed to mount /mnt/CCBACK).

Can you do cat /etc/fstab when it is in emergency mode?

[rough marten]

My secondary hard disk i use for data

[rough marten]

Yes

[lusty cave]

Can you show the file?

[odd blaze]

4th-last line in the file.

where is the efi partition line? it is gone.

is this legacy BIOS system?

also, put a # sign at the start of the 2nd-last line of the file. the one about ccback.

boot live usb to edit this. unless nano works from this terminal.

[lusty cave]

Comment the second-last line. With a #. You can use vi for this. Uncomment /boot/efi line.

vi /etc/fstab
Press i to go in insert mode
Go to the /boot/efi line and press delete on keyboard to delete the # in front.
Scroll to the line with CCBACK and put a # in front
Press esc to go out of insert mode
Press :wq to save
Then reboot.

[odd blaze]

the efi thing is missing

no UUID

this better be a legacy boot.

[lusty cave]

@rough marten share the output of blkid command.

[lusty cave]

Ok.

[rough marten]

Are you sure you want to uncomment the /boot/efi line? Because it looks like it's meant to be a comment sentence, not code

/boot/efi was on /dev/sdb2 during installation

[lusty cave]

Please dont uncomment it.

[rough marten]

Yeah i didn't

[odd blaze]

you gotta re-add the line about vfat. the UUID starting with 173A must be readded properly

UUID=173A-B689 /boot/efi vfat

may need a few extra parameters on that line for fstab to process it right

[rough marten]

Do you not know the extra parameters?

[odd blaze]

i dont have uefi so no, but u can just google a sample UEFI fstab file

[steep tartan]

"UEFI syntax for fstab - Linux Mint Forums" https://forums.linuxmint.com/viewtopic.php?t=294693

Can this help by any way?

[rough marten]

https://forums.linuxmint.com/viewtopic.php?t=294693

Jinx

[steep tartan]

Oh no

I didn't said it verbally so no jinx

[odd blaze]

UUID=753A-83BB /boot/efi vfat umask=0077 0 1

that is in the sample

thanks ice bear

[rough marten]

How many spaces are in there?

[steep tartan]

No problem!

[rough marten]

And what uuid do i use

[lusty cave]

Tabs. No spaces.

[rough marten]

Is that the right uuid or is that a sample?

If a sample then what is the right uuid

[lusty cave]

Check /dev/sdb2 from here

[rough marten]

Where

[steep tartan]

UUID here I guess

[lusty cave]

UUID=173A-B689

[steep tartan]

Do we have to uncomment that?

[rough marten]

173A-B689

[steep tartan]

How you got that

[rough marten]

blkid

[lusty cave]

blkid

[steep tartan]

okioki

Thing to be noted

[rough marten]

So this?

[lusty cave]

Looks good.

[odd blaze]

could have written that line right under the comment for it

[lusty cave]

Save and reboot.

[rough marten]

You didn't tell me, which line is that then?

[odd blaze]

there's literally a # line about efi

[rough marten]

Under which comment

Ok

Now what

Rebooting does nothing

[odd blaze]

.

did u save it properly?

[rough marten]

I did save and reboot

[steep tartan]

Ctrl + x
y
enter

[rough marten]

Write out and exit

[odd blaze]

do cat /etc/fstab

to see if it kept the changes.

[odd blaze]

no, in nano, it's ctrl-o to write out (save to disk) , then enter. then ctrl-x to exit

actually ur way would work too, nvm

[lusty cave]

You can just do ctrl+x and enter.

[steep tartan]

Umm
When we change something
And then do ctrl x it automatically asks us to save buffer first that's why

y
Then enter

Or there's anything else ?

[odd blaze]

good, edit it again dan, this time comment-out that last line about the gamedisk

[rough marten]

Did that

[odd blaze]

ok save it, and reboot again

[rough marten]

Did

Black screen

[odd blaze]

ok reboot again, do u see a grub menu ever?

you shouuld because i see a windows OS in the info

you should see this ^ (GRUB menu) for a few seconds on a dual boot.

press e when you do

[lusty cave]

Wait. It still fails to mount something.

Use the command journalctl -xb scroll through it until we see what fails to mount.

[rough marten]

Yes i manually get the grub menu by pressing shift

[steep tartan]

Press shift with booting if didn't got grub menu yet

[steep tartan]

Cool!

[steep tartan]

System logs

[odd blaze]

did you recently change graphics hardware or drivers?

[rough marten]

Not really

[odd blaze]

ok did u press e at grub?

[rough marten]

Yes

[lusty cave]

Do you got any idea what fails to mount?

[odd blaze]

put nomodeset with one space before it, right after the line in edit startup parameters, after quiet splash

[rough marten]

Where

[odd blaze]

press e at grub menu

then follow what I just wrote after

[lusty cave]

On the linux line at the end add a space and nomodeset keyword.

[rough marten]

Ok now what

[odd blaze]

read the bottom to boot

[lusty cave]

Press ctrl + x

[rough marten]

It booted

Now ccback is missing

[odd blaze]

so ur graphics got fuckd

show output of inxi -CGxx from terminal

[odd blaze]

did u allow a kernel update recently?

[rough marten]

Yes

[odd blaze]

that's what caused it

[rough marten]

I did that after this problem started in panic

No

[odd blaze]

oh after

how did u update the kernel if u couldn't boot?

[rough marten]

Recovery mode boot

[odd blaze]

the og problem was th fk'd up efi / fstab mess

then the kernel change made it worse

do uname -r

[rough marten]

6.8.0-52-generic

[odd blaze]

also windows.

did u turn windows fast startup off in control panel?

[rough marten]

wait so if graphics are f'd how do i unf them

amd

[odd blaze]

roll back to prior kernel

[rough marten]

windows itself or uefi?

[odd blaze]

windows

[rough marten]

i don't remember

also if i restart will boot work?

[odd blaze]

for now, open update manager

[rough marten]

or do i have to do that grub e thing every time?

[odd blaze]

then click the view menu

[lusty cave]

What is the logic?

[odd blaze]

kernel runs amd

[rough marten]

prior was 53

i can't find it

in update manager kernels

[odd blaze]

do u still have the stock -51 one showing installed?

[rough marten]

yes

53 is gone though

[odd blaze]

ok boot to windows now

so it doesnt interfere

[rough marten]

what about this

[lusty cave]

https://forums.linuxmint.com/viewtopic.php?t=355775

[odd blaze]

then boot linux n choose grub again n pick advanced

u wont have to later if 51 kernel works fine

[rough marten]

i want 53 back

i'm going to windows for now

[odd blaze]

OK

[rough marten]

for the fast startup thing

[odd blaze]

do that

[odd blaze]

see #1193345280733622272 message

post with hearts

even tho it's on a different disk, it might still mess with uefi somehow

[rough marten]

fast startup is off

[odd blaze]

alright. boot to mint,

get to grub again. select Mint Advanced options.

[rough marten]

Ok

[odd blaze]

yeh, then in advanced, u should see a list of all currently installed linux kernels.

[rough marten]

Yes

52 at top

[odd blaze]

this one doesnt seem too good for ur graphics

so pick another one

then i think F10 to boot it

[rough marten]

Can i download 53

[odd blaze]

i guess

[rough marten]

Where

[odd blaze]

if u reach desktop

[rough marten]

Update manager does not have it anymore

It used to

[odd blaze]

may have to do sudo apt update once it is in desktop.

[rough marten]

I got the kernel and i booted

[odd blaze]

what are u running now? uname -r ?

[rough marten]

I don't have internet connection

[odd blaze]

kek

what's uname -r say?

[rough marten]

53

[odd blaze]

so.. what did u boot using Mint Advanced in Grub?

use one that works, and that's it.

and lock it

[rough marten]

51 doesn't start

38 doesn't start

52 too??

Nothing else works

Only 53 ???!!!

[rough marten]

Whyy???????????

[odd blaze]

check inxi -SNxxx and show.

@rough marten

[odd blaze]

no ethernet driver. and no Wifi hardware shown AT ALL

are you using a USB wifi adapter?

[rough marten]

Idk rlly

Could be ethernet or wifi

[odd blaze]

no, read the information there for Device-1

that's Ethernet.

[rough marten]

Ok then ethernet

[odd blaze]

so you were always connecting to internet by wire?

[rough marten]

Yes

[lusty cave]

Please do this to dont add nomodeset everytime.

[rough marten]

It has never stopped connecting till now

[rough marten]

I don't need to do it now, it boots fine now

[odd blaze]

i dont recommend to keep nomodeset permanently

[rough marten]

It's just a lack of wifi

[odd blaze]

that creates no video drivers if u use nomodeset always

do u have smartphone, Dan?

[rough marten]

Yes i use it rn

It has connection but pc no

[odd blaze]

ok because it is using cellular data plan

[rough marten]

No

Wifi is there

[odd blaze]

wifi from ur house network then?

[rough marten]

Yes

It's a linux mint problem not network

[odd blaze]

ok look in phone settings for Tether via USB

turn on the usb hotspot/tether mode.

then plug it to computer with cable.. then check driver manager

[rough marten]

That's a temporary solution

[odd blaze]

if driver manager shows no special drivers after you get online.. then will have to wait for Jeremyb. he is network specialist for linux.

[rough marten]

Ping him

@sleek shell

Windows network connection works fine

[odd blaze]

also, when u booted with 6.08 -52, you had ethernet working, but you had to use "nomodeset" for it to load up right?

[rough marten]

Yes

That's how i could send you a screenshot with the pc itself

[odd blaze]

back here. u had ethernet then?

[rough marten]

Yes

Now 52 does not start

[odd blaze]

ah this .. right

[odd blaze]

because you had to start the system with nomodeset that time

[rough marten]

Mhm

[odd blaze]

i mean u could use it that way if u need to work, but it's on limited video capability

[rough marten]

Windows 10 is looking very handsome rn

[odd blaze]

[rough marten]

I might have to go back to using it

[odd blaze]

what about in Update Manager, u have 6.11 series available?

in View: Kernels

[rough marten]

I had that yes

[odd blaze]

give one of those a try

[rough marten]

But i removed it later

Because it didn't work

At that time

[odd blaze]

what was the symptom?

[rough marten]

Not starting

[odd blaze]

ah

[rough marten]

Do i do it anyways?

[odd blaze]

well, i think there's a few in the 6.11 series possibly

but how old is this computer? do inxi -M and check BIOS date.

[rough marten]

07/31/2019

[odd blaze]

that sounds reasonable

[rough marten]

I can't even download 6.11 kernel because no internet

I'll run recovery mode boot then

[odd blaze]

I thought u were booted to -52 which DID give u ethernet

[odd blaze]

or just plug ur phone in via usb to get the update

[sleek shell]

What is the wifi device? Nothing showed in inxi results?

[odd blaze]

it never was wifi. despite any misnomers.

[odd blaze]

network info.

[sleek shell]

Ok, the ethernet device is supported by the r8169 module but it isn't loaded

[steep tartan]

[median umbra]

If you still want my advice, please summarise. Not reading all of that.

[odd blaze]

basically this.

so the -52 kernel NEEDS nomodeset in order to get to a desktop.

and works with their ethernet

conversely, the -53 kernel boots to desktop fine without nomodeset, but has no network card support

[median umbra]

Sounds like another regression. The 6.8 branch appears to be swimming in those.

Bear in mind that 6.11 is available now on Mint 22.

[odd blaze]

specs ^

[median umbra]

Not great, but should work.

So if a solution is still being sought, my recommendation is switching to kernel 6.11 as a workaround.

[odd blaze]

so basically Danyeru: boot the machine with the -52 kernel, using the e key, and adding the nomodeset parameter. once there, go to update manager and install and run the 6.11 kernel(s) as what Curunir recommends. Then reboot.

@rough marten ^

[rough marten]

Where can i find and download this kernel and which kernel do you recommend?

Update manager prob doesn't have it

[odd blaze]

i think it does

just make sure u have net-access when u boot -52 as described

then do sudo apt update to get fresh software catalogue.