Ask Your Question
1

Fedora 29 (KDE Spin) LIVE USB; install hangs

asked 2019-01-25 15:42:07 -0500

xxdressielxx gravatar image

updated 2019-01-26 06:31:00 -0500

o folks

I created an USB Stick with Fedora Media Writer and i tryed for 2h to install Fedora on this machine https://www.zotac.com/us/product/mini...

If i select the first option --> "Start Fedora Live 29" I get a system hang on "Started Load/Save RF Kill Switch Status"

If i select troubleshooting and pick the first one, i get a system hang on "Starting Hold until boot process finishes up"

I just dont know what to do

(The install Process on my other machine --> Haswell Intel NUC worked flawlessly)

Thank you in advance for any help

EDIT:

First off, big thx for the replys @ K7AAY, loboedu

@loboedu I tryed:

  1. several USB Pen Drives --> NoName, SanDisk etc
    • created Live USB Pen wit Fedora Image Writer on Win10 Machine vs Fedora 29 KDE Spin Machine (Haswell NUC)
    • disabled Secure Boot, switching from UEFI to Legacy BIOS
    • switched integrated INTEL Graphic from "auto" to "enabled"

nothing worked @ K7AAY so you suggest to install an ARM Spin on a Intel Chip ? doesnt make sense to me. But i just tryed another Spin ....actually i tryed just Fedora 29 Workstation (Standard Gnome). It passed the "Started Load/Save RF Kill Switch Status" but hangs on the next line "Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling..."

If i select troubleshooting and pick the first one, it shows at the end "Started GNOME Display Manager." ....after that its just an blackscreen with a blinking mark on the top left corner, nothing happend.

IF i delete the "quit" param .... it hangs here:

- [OK] Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling
- ACPI Warning: \SB.PCI0.PEG0.XVS0._DSM: Argument #4 type mismatch - Found Buffer
ACPI requires [Package] (20180531/nsarguments -66)
-ACPI:\_SB_.PCI0.PEG0.XVS0 : failed to evaluate _DSM
- iwlwifi 0000:04:00.0 : detected Intel (R) Dual BandWireless AC 3165. Rev=0x210
- fb : switching to nouveaufb from EFI VGA

after some research i flashed the bios of the mobo... then again IF i delete the "quit" param .... it hangs here:

- ACPI Warning: \SB.PCI0.PEG0.XVS0._DSM: Argument #4 type mismatch - Found Buffer
ACPI requires [Package] (20180531/nsarguments -66)
-ACPI:\_SB_.PCI0.PEG0.XVS0 : failed to evaluate _DSM
- fb : switching to nouveaufb from EFI VGA

Under Troubleshooting it hangs on

-Starting Terminate Plymouth Boot Screen

SO im stuck and running out of ideas

edit retag flag offensive close merge delete

Comments

Please test another Spin, such as https://spins.fedoraproject.org/xfce/ then come back here, click [edit], and let us know if the XFCE Spin worked OK or not. Also, when GRUB2 starts to load, please interrupt it with 'e' and remove ;quiet' from the kernel loading line; where does it stall?

K7AAY gravatar imageK7AAY ( 2019-01-25 17:20:11 -0500 )edit
1

Have you tried verifying the ISO or repeating the process of image creation on the USB Stick? In which phase does the boot hold?

loboedu gravatar imageloboedu ( 2019-01-25 18:54:27 -0500 )edit

I was suggesting you use an x64 Spin, not an ARM spin. The XFCE Spins page has x64, i386 (32-bit),, and ARM, so please use the x64 version.

K7AAY gravatar imageK7AAY ( 2019-01-29 18:11:46 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted
2

answered 2019-02-02 05:52:16 -0500

xxdressielxx gravatar image

Finally finished the setup. I used the Net.Install Img . The Install switched instantly into the text mode (bc no nvidia drv nor nouveau could work). After the install is complete i was greeted with command line (tty), here i could easily install nvidia drv via rpm fusion repo (akmod).

After reboot in Command Line (tty)

systemctl set-default graphical.target

startx

And i was presented with a graphical interface and could LogIn. Done and Happy like a 5y old kiddo at Christmas

edit flag offensive delete link more
0

answered 2019-01-26 08:25:08 -0500

loboedu gravatar image

Jee man... it looks like an NVIDIA issue. I'm sorry, but I don't know much about it, although it sure looks like an issue with your NVIDIA GPU and the driver Fedora uses for them as default (nouveau). However, I couldn't tell why such an error is coming up. I use an NVIDIA GPU, too, but I have never had such an error.

I'm sorry I can't help you more...

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2019-01-25 15:42:07 -0500

Seen: 415 times

Last updated: Feb 02