Arch Linux

ktatar156

Member

Registered: 2012-10-01

Posts: 79

Cannot boot USB arch key

Hello,

I'm having problem with booting USB arch installation image.

I've prepared USB key by:

# dd bs=4M if=/path/to/archlinux.iso of=/dev/sdx status=progress oflag=sync

I'm starting my computer, booting USB key (UEFI and legacy mode, tried both). The system seems to be booting, and suddenly (when command line ready should appear) GPU fans turn on with speed 100% for 1 second, turn off after that and I get black screen.

What can I check/do?

My computer:

CPU: 2600X
Motherboard: MSI B450M Gaming Plus
GPU: XFX RX 590

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,333

Website

Re: Cannot boot USB arch key

What does "seems to be booting" mean?  Do you get past the syslinux menu?  If so, try modifying the kernel command line to add the parameter 'nomodeset' as an initial test.

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

ktatar156

Member

Registered: 2012-10-01

Posts: 79

Re: Cannot boot USB arch key

Firstly, I get that screen:

system is loading and right before I should get login to root, I get only black screen. I tested also Ubuntu image - the same problem. Could be a graphic card not supported yet and it crash the system? If yes, why it shows boot menu?

I added at boot menu (by clicking 'e') 'nomodeset' at the end of the line and clicked 'enter' to boot with this - no help.

Last edited by ktatar156 (2018-12-08 21:35:54)

ktatar156

Member

Registered: 2012-10-01

Posts: 79

Re: Cannot boot USB arch key

EDIT: Sorry, my mistake, I added 'nomodset' - typo. now it working, thanks! I checked that there are some problems with RX 590
https://www.phoronix.com/scan.php?page= … t-Progress

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,333

Website

Re: Cannot boot USB arch key

nomodeset should be fine for the installation iso and will allow you to install.  You will likely need it again to boot your freshly installed system (until the kernel catches up with your hardware).  However, 'nomodeset' is a bit of a chainsaw when you should really use a scalpel: it is a temporary workaround and not a good long-term (or even medium-term) solution.  Perhaps there is a more precise parameter that could be passed to the kernel to avoid the problem with fewer side effects.

Last edited by Trilby (2018-12-08 21:56:22)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman