search

PartialVolume / shredos.x86_64

Shredos Disk Eraser 64 bit for all Intel 64 bit processors as well as processors from AMD and other vendors which make compatible 64 bit chips. ShredOS - Secure disk erasure/wipe
Other
1.28k stars 52 forks source link

Unable to boot #212

Open MinecollYT opened 5 months ago

MinecollYT commented 5 months ago

Hi, sadly I'm unable to use shredos (again).

Might be releated to my first issue, but I'm not so sure about that. I've tried the normal and ventoy methodes:

Rufus + shredos-2023.08.2_25.0_x86-64_0.35_20231110.img + UEFI

Stops (the _ is still blinking) after shredos reaches 100% while booting and displays "qla2xxx [0000:00:00.0]-0001: : Unable to create qla2xxx trace instance, instace logging will be disabled."

Rufus + shredos-2023.08.2_25.0_x86-64_0.35_20231110.img + UEFI + nomodeset

Freezes when shredos reaches 100% while booting

Ventoy + shredos-2021.08.2_23_x86-64_0.34_20221231.iso + UEFI

Stops (the _ is still blinking) after shredos reaches 100% while booting and displays "qla2xxx [0000:00:00.0]-0001: : Unable to create qla2xxx trace instance, instace logging will be disabled."

Ventoy + shredos-2023.08.2_25.0_x86-64_0.35_20231110.img + UEFI

Screen goes blank after shredos reaches 100% while booting

PartialVolume commented 5 months ago

Might be releated to my first issue, but I'm not so sure about that.

You would have to remind me what your first issue was.

What's you hardware, make/model of system, make/model motherboard, lspci output, more /proc/cpuinfo. Method of connecting display to monitor, VGA, HDMI, DVI, Display Port?

Sounds like a framebuffer/DRM/Connector issue, however I see you did use nomodeset on your second Refus attempt. Did you apply nomodeset to both grub.cfg's /EFI/BOOT/grub.cfg and /boot/grub.cfg ?

MinecollYT commented 5 months ago

My first issue was #140

The problems occurred on a HP Elitebook 755 G5, both when using the internal screen and multiple screens conntected using a docking station.

Yes, I applied the changes to both files

PartialVolume commented 5 months ago

If a DP connection involved in any of the setup then that could be the issue. I believe DRM and the code involved in connecting a DP output doesn't work. On my Dell system with a Nvidia DP output you don't get any output. In my particular case adding nomodeset to the kernel stops it switching into DRM from simple framebuffer and then DP works correctly. I will shortly be updating buildroot and the kernel to the next release where I'm hoping this graphics issues got fixed.

Although the screen has frozen at 100% I suspect ShredOS hasn't frozen and is still running behind the scenes. Following the headless login on the ShredOS readme.md would prove that.

If you remove it from the docking station so you have no other monitors attached does it then work?

PartialVolume commented 5 months ago

In addition can you post the output of lspci, I'm just wondering whether it reported as VGA Intel UHD

PartialVolume commented 5 months ago

Sorry for the excessive posting, one last comment. I just googled it, looks like it has AMD integrated graphics with both HDMI and VGA outputs. If there is nothing coming up in the screen after it hits 100% you might want to see if it's coming out the VGA or HDMI connections. Like the Dell is there any setting in the Bios for how video switching is handled between VGA/HDMI and the docking station?

MinecollYT commented 5 months ago

If you remove it from the docking station so you have no other monitors attached does it then work? During the test above, I only used the internal screen, no docking station or external monitor

The docking station support 2x dp and 1x hdmi, the notebook only supports 1x hdmi output. I can try using the onboard hdmi output

MinecollYT commented 5 months ago

Nope, when using the normal rufus version it freezes at the qla2xxx point and when using nomodeset it freezes at 100 % shredos. Even when using the direct hdmi output

PartialVolume commented 5 months ago

Are you able to retrieve the lspci output by booting another distro like gparted or do a headless login to ShredOS?

PartialVolume commented 5 months ago

I see from your original issue #140 that this system has both Intel UHD and Nvidia graphics. Maybe it's the Intel UHD that's the issue has others have reported the same issue who also had Intel UHD graphics.

Kolli96 commented 5 months ago

I have the same problem with an HP EliteDesk 705 MINI G4 , AMD Ryzen 5 Pro 2400G , 16GB DDR4 machine. Shredos startup freezes in a black screen at 100%. Version v2021.08.2_23.1_x86-64_0.34 which has added AMDGPU, Radeon and GPU firmware does not help. And no other version either. Secure boot disabled and Legacy boot enabled.

PartialVolume commented 5 months ago

@Kolli96 its noticeable how often HP systems have an issue. Does nomodeset in the two grub files help? How do you create your boot stick, dd, rufus or Ventoy?

Kolli96 commented 5 months ago

@Kolli96On huomattava, kuinka usein HP-järjestelmissä on ongelmia. Auttaako nomodeset kahdessa grub-tiedostossa? Kuinka luot boot stick, dd, waste tai Ventoy?

I have tried all usb versions with the Rufus program.

Kolli96 commented 5 months ago

New information. If I disable the Legacy boot support and also the secure boot feature (Only UEFI allowed), Shredos version 2021.08.2_23.1_x86-64_0.34_20230320 startup normally! But then I have trouble getting into the HP bios again. The HP boot screen sometimes freezes at "entering boot menu". This did not happen if Legacy boot support is enabled and the secure boot feature disable

PartialVolume commented 5 months ago

Have you tried the latest version with both /boot/grub.cfg and /EFI/BOOT/grub.cfg having had nomodeset appended to the kernel command line using the latest version of ShredOS? And if that doesn't work try nomodeset noapic. Try all these variations in both legacy and UEFI boot.

Also, what type of connection do you have to the monitor. Is it VGA, DVI or Display Port?

Kolli96 commented 5 months ago

Have you tried the latest version with both /boot/grub.cfg and /EFI/BOOT/grub.cfg having had nomodeset appended to the kernel command line using the latest version of ShredOS? And if that doesn't work try nomodeset noapic. Try all these variations in both legacy and UEFI boot.

Also, what type of connection do you have to the monitor. Is it VGA, DVI or Display Port?

I haven't because I don't understand what they mean and how to change them. The monitor is connected with an HDMI cable. There is no other connection.

DaveMcCloud commented 2 months ago

I had a similar problem trying to wipe a laptop today. It stuck at 100%. The laptop was connected to a USB-C dock so reading this thread I tried it again disconnected from the dock and it launched fine - had that qla error mentioned but not an issue and it went past. Once booted I was able to plug the dock back in (for charging purposes). It is happily wiping away.

UEFI was enabled, Secure boot not if anyone was interested.