Stuck on 100%, GUI won’t open

[cudeata]

The UEFI has no legacy and i’m booting from a USB created using Rufus with the 64 bit .img file from the shredOS github, I’ve disabled secureboot as well and the UEFI is updated. The PC does boot shredOS from the flash drive but stays stuck on a loading screen at 100%, the GUI never shows up, the “_” at the top left does not blink either. The line at the top of the screen is as follows (without the quotation marks of course): “ [ shredos 218.11MiB 100% 48.81MiB/s ] “

Computer is an HP Omen 30L desktop GT13, Intel Core i7-10700k with 16gb of memory.

[PartialVolume]

Does adding nomodeset or noapic to the kernel command line solve the problem?

[PartialVolume]

This motherboard may have Intel integrated graphics on the motherboard, if it has a graphics card as well, try removing the graphics card and boot using the intel integrated graphics.

[Mazolei]

I seem to be having this same issue, on an omen 40L GT21 desktop. This board doesn't have integrated graphics, and adding nomodeset and noapic to the command line doesn't seem to have helped, assuming I did it correctly (I will admit that my knowledge of linux is limited, so I may very well have done it wrong)

[PartialVolume]

I seem to be having this same issue, on an omen 40L GT21 desktop. This board doesn't have integrated graphics, and adding nomodeset and noapic to the command line doesn't seem to have helped, assuming I did it correctly (I will admit that my knowledge of linux is limited, so I may very well have done it wrong)

Feel free to post a photo of grub.cfg and I'll check it's correct.

[Mazolei]

Feel free to post a photo of grub.cfg and I'll check it's correct.

This is how I've got it now, and I've changed grub.cfg in both locations

[PartialVolume]

Feel free to post a photo of grub.cfg and I'll check it's correct.

This is how I've got it now, and I've changed grub.cfg in both locations

No, you have the two commands in the wrong place. It should look like this:

set default="0"
set timeout="0"

menuentry "shredos" {
    linux /boot/shredos console=tty3 loglevel=3 nomodeset noapic
}

[Mazolei]

No, you have the two commands in the wrong place. It should look like this:

set default="0"
set timeout="0"

menuentry "shredos" {
  linux /boot/shredos console=tty3 loglevel=3 nomodeset noapic
}

Haha, gotcha, that was my first instinct, I should have went with it. I'll try that and let you know how it goes

[PartialVolume]

If it doesn't work with both then try it with one then the other:

set default="0"
set timeout="0"

menuentry "shredos" {
    linux /boot/shredos console=tty3 loglevel=3 nomodeset
}

or

set default="0"
set timeout="0"

menuentry "shredos" {
    linux /boot/shredos console=tty3 loglevel=3 noapic
}

[Mazolei]

Running with both seems to have worked! I got some error about a qla2xxx trace instance, but the GUI loads and it seems functional

[PartialVolume]

That's great. Don't worry about the qla2xxx trace instance, it's a benign error related to a fibre driver that's not needed.

I just had a quick look at the spec and it looks like you have a display port and HDMI output on that system. There is some issue sometimes with display port so if it hadn't worked I was going to ask you to try HDMI but maybe you are already using that to connect to the monitor.

Glad it's all working :+1:

[Mazolei]

That's great. Don't worry about the qla2xxx trace instance, it's a benign error related to a fibre driver that's not needed.

I just had a quick look at the spec and it looks like you have a display port and HDMI output on that system. There is some issue sometimes with display port so if it hadn't worked I was going to ask you to try HDMI but maybe you are already using that to connect to the monitor.

Glad it's all working 👍

Well, I seem to have run into some other issue; The GUI boots, but the drive I'm trying to clear doesn't appear, and the UI doesn't respond to any of my inputs. I was using a display port before, but swapping to my HDMI monitor alone doesn't seem to have helped.

[PartialVolume]

Do you have noapic on the Kernel command line? If you do try removing it so you've just got nomodeset.

[Mazolei]

Do you have noapic on the Kernel command line? If you do try removing it so you've just got nomodeset.

That seems to have done it for real this time! Thank you very much for the help

[PartialVolume]

Do you have noapic on the Kernel command line? If you do try removing it so you've just got nomodeset.

That seems to have done it for real this time! Thank you very much for the help

No problem, hopefully with the updated graphics drivers in the next release, adding nomodeset won't be necessary with some of these systems.

[PartialVolume]

@Mazolei If you get a chance, can you do me a favour and type ALT F1 to switch to the second virtual terminal and type the command lspci and post a photo of the output. This will display details of the graphics card being used. Thanks.

ALT F1 to switch back to the nwipe screen.