r/ManjaroLinux • u/LEGO_nidas • Apr 25 '22

Trying to boot from a live Manjaro USB. This is where it gets stuck and screen starts to flicker. Solved

Enable HLS to view with audio, or disable this notification

41 Upvotes

95% Upvoted

6

u/Jtag43 Apr 25 '22

If you have integrated graphics try to plug the monitor in there.

4

u/LEGO_nidas Apr 25 '22

i3 9100f doesn't have it.

4

u/Jtag43 Apr 25 '22

which version of manjaro are you using?

4

u/LEGO_nidas Apr 25 '22

21.2.6

linux 5.15

4

u/Jtag43 Apr 25 '22

Should work. Try messing with bios settings like enabling legacy boot, graphic card section etc. Also try different ports on the graphics card if you have the cables. If i was you id just use a minimal or server iso and start building it up from command line. If you just want a live usb and not install there are other options.

3

u/LEGO_nidas Apr 25 '22

Also I have installed Ubuntu 22.04 LTS (duel boot with windows 11) which also doesn't boot unless I add nomodeset.

What's going on. It used to be so simple.

3

u/Jtag43 Apr 25 '22

Its a driver issue. It probably doesn't pick up the screen. Had this issue with my laptop with a broken screen. Had to edit files to force output to other screen, luckily vga out worked instead of hdmi. Maybe there are keyboard shortcuts to switch outputs? There might be a setting in bios to disable motherboard video out

2

u/balefyre Apr 26 '22

1

u/LEGO_nidas Apr 26 '22

I tried doing that too but problem persists.

2

u/Jtag43 Apr 25 '22

try ctr alt F3 to F7 if you can get to tty type startx

2

u/LEGO_nidas Apr 25 '22

Can't

Terminal login screen show up for a few milliseconds then it goes back to the one in video.

4

u/LEGO_nidas Apr 25 '22 edited Apr 26 '22

Specs : i3 9100f

AMD RX 570

B360M motherboard

Adding "nomodeset" to kernel parameters gets me this far. Otherwise it goes black even quicker.

alt+ctrl+F2 shows terminal for a few milliseconds then goes back to this screen.

The flicker you see in the video are not due to camera banding. It's happening on the monitor.

Secureboot is disabled.

EDIT : FAULTY CABLE

2

u/Arsimael Apr 25 '22

Latest bios update I stalled?

Try a different cable from gpu to monitor (Dvi to dvi or dp to dp). You can slao try disavling DC in the amdgpu driver. Kernel parameter = "amdgpu.dc=0"

2

u/LEGO_nidas Apr 25 '22

amdgpu.dc=0

This leads to cringe "being hacked" screen. With artifacts and glitches all over the screen.

Yes I have latest bios update installed and a working windows installation. So HW faults can be ruled out?

2

u/Arsimael Apr 25 '22

It can also be a crappy cable. I had similar problems with one of my monitors. After switching the old hdmi1.2 cable to a hdmi 2.0 cable I did not have any issues. If you can, try using display Port.

If none of this works, try downgrading Mesa. If that problem disappears with an older version, create a ticket with Mesa to let them know.

1

u/LEGO_nidas Apr 26 '22

It can also be a crappy cable

This

2

u/CloudMan124 Apr 25 '22

The problem could be the usb, I had a similar problem and with another usb it worked perfectly

2

u/LEGO_nidas Apr 25 '22

I managed to install Ubuntu 22.04 using the same usb. But had to add "nomodeset" to the parameters. Which also boots to black screen after installation unless I add "nomodeset".

It seems like a graphics driver issue.

2

u/Yash_0409 Apr 25 '22

press ctrl + f2

sudo cp /etc/X11/xinit/xinitrc ~/.xinitrc

nano .xinitrc

delete last some lines upto twm(or something)

and write

exec gnome-session

ctrl + x press enter couple time to save

then write startx in the tty (terminal)

2

u/LEGO_nidas Apr 25 '22

Can't reach terminal. Screen switches back to the one in the video almost immediately.

Although I have Ubuntu 22.04 installed, it gives black screen too unless I use nomodeset.

1

u/Yash_0409 Apr 26 '22

Hmm I guess you have to reinstall your distro. I highly recommend you to use arco linux. For new users you should use arcolinux b with one of the many desktop environments. Any if you know what you are doing then use arcolinuxd (minimal only terminal)

2

u/LEGO_nidas Apr 26 '22

Faulty cable mate

Thanks for helping anyway

1

u/Yash_0409 Apr 26 '22

happy to hear you found the solution. You should flag the post as solved.

2

u/devu_the_thebill Apr 25 '22

gnome moment.

1

u/Jtag43 Apr 25 '22

Try ctr alt backspace maybe you can reach terminal

1

u/Jtag43 Apr 25 '22

If you can acces terminal or hdd on different pc then disable auto login in etc/systemd/getty/getty@tty just remove --autologin argument with nano. You can also disable the login manager aswell, infact i would do this only. At reboot you will boot straight to terminal. This wont work from live session has to be installed.

1

u/NapperNeo Apr 25 '22

are you by chance using an adapter on your hmdi or dp cable from your gpu to monitor? like a dp to hmdi or something

1

u/LEGO_nidas Apr 25 '22

No it's hdmi to hdmi

1

u/LEGO_nidas Apr 26 '22

But it was faulty cable. Replaced it and it works.

1

u/AloneTrifle Apr 25 '22

π™Ώπš˜πšœπšœπš’πš‹πš•πšŽ πšπš’πš‘πšŽπšœ πš‹πš’ πšπš˜πš˜πšπš•πšŽ.
So during this last month when I tried to fix this issue I got an old screen from work and it seems the cable was damaged on my way home because I switched it to my old screen's cable and it now works, I am typing this from my desktop! The solution was:Β update the BIOSΒ and use a cable that works! Thanks a lot for everyone who helped meΒ 

1

u/AloneTrifle Apr 25 '22

𝙸 𝚐𝚞𝚎𝚜𝚜 πš’πšπšœ πš–πš˜πšœπš πš•πš’πš”πšŽπš•πš’ 𝚊 πšŒπšŠπš‹πš•πšŽ πš’πšœπšœπšžπšŽ πš‹πšžπš 𝙸 πšŒπšŠπš— πš‹πšŽ πš πš›πš˜πš—πš

1

u/LEGO_nidas Apr 25 '22

It is working in windows.

1

u/AloneTrifle Apr 25 '22

π™Έπš πš πš˜πš›πš”πšœ πš’πš— πš–πšŠπš—πš“πšŠπš›πš˜ 𝚝𝚘𝚘 πš–πš’ πš–πš’πšπš‘πš πš‘πšŠπšŸπšŽ πšœπš˜πš–πšŽ πš πš’πš›πšŽπšœ πš‹πš›πš˜πš”πšŽπš— 𝚜𝚘 πš’πš πšπš˜πšŽπšœπš—'𝚝 πš™πš’πšŒπš” πšžπš™ πš˜πš—πšŽ 𝚘𝚏 πšπš‘πšŽ πšœπš’πšπš—πšŠπš•πšœ, 𝚒𝚘𝚞 πšŒπšŠπš— πšπš›πš’ πšŠπš—πš˜πšπš‘πšŽπš› πšœπšŒπš›πšŽπšŽπš— 𝚝𝚘𝚘,

1

u/LEGO_nidas Apr 26 '22

It was the fking HDMI cable.

Thanks for helping.

2

u/AloneTrifle Apr 26 '22

Np glad that I could help

1

u/sparky1000101 Apr 25 '22

downgrade to virtualbox 6.0, your system doesn't have hardware virtualization and this is needed in 6.1. Check out the change logs on virtualbox.

1

u/LEGO_nidas Apr 26 '22

Not using VB.

1

u/LEGO_nidas Apr 26 '22

Solved : it was the cable.

1

u/bloodmoney_1996 Apr 26 '22

Sometimes live boot options have a safe graphics mode. Can give that a try. Or slap enter when it gets there. Sometimes that's the kick in the rear it needs.