Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

shredOS terminal compressed to top line of screen on multi GPU laptop [fixed] #52

Closed
Ryan-A-Bradley opened this issue Nov 17, 2021 · 125 comments
Assignees
Labels
bug Something isn't working

Comments

@Ryan-A-Bradley
Copy link

Ryan-A-Bradley commented Nov 17, 2021

Thank you for fixing this! :D

17/11/2021: shredOS hangs (or crashes) during launch [fixed].

18/11/2021: added new drivers to shredOS.
18/11/2021: shredOS now working on some newer machines but GUI is not loading properly [fixed].
27/11/2021: shredOS GUI loading properly.

analysis: missing drivers for 10th and 11th gen CPU's and GPU's [fixed].

i7-10750H
i7-11800H

[fixed]
I've tried booting with USB; the 32-bit and 64-bit .img files both hang at recal with _.
I've tried using an external cd writer/reader with the 64-bit .iso, disc spins up but fails to boot to the black screen.

ACER Predator Helios 300 15.6" Gaming Laptop - Intel® Core™ i7, RTX 3070, 1 TB SSD

Laptop SN look-up link for exact specifications:

https://snlookup.com/acer-predator-ph315-53-notebook-nh-qatek-001-p382646?sn=NHQATEK001120026843400#ffs-tabbed-17|tab6

example of the hanging (or crash) [fixed]:
142283314-6c147bed-fdcf-41ba-9554-b745ed7a1123

example of shredOS working with new drivers but GUI isn't loading properly [fixed]:
142498192-01b226e3-8092-4404-8f68-300e47700288

@Firminator
Copy link

Is there an option in the BIOS/UEFI setup to change from UEFI mode to Legacy/BIOS mode?

@Ryan-A-Bradley
Copy link
Author

shredOS works on my other laptop and on my desktop pc (both have older hardware than the new laptop). I was hoping to use shredOS to wipe all 3 machines. :o

I just don't have much knowledge about how hardware and bootable software needs to be programmed to work.

Laptop is UEFI boot by default (tested boot with secure boot on/off). For some reason, I'm unable to switch it from UEFI so I'm under the impression this BIOS doesn't support legacy? I'll look into this now.

@Ryan-A-Bradley
Copy link
Author

Apparently, I should be able to change the boot setting to legacy after setting a password (which I tried). However, I'll try a bit more right now as I have the laptop currently with me on the desk.

@Firminator
Copy link

Sure. Give it a try and let us know.

@PartialVolume
Copy link
Owner

If this document applies to your model you may have to enable a setting that trusts the USB device to boot UEFI, not only that but the actual file name.
Screenshot_20211117_194707

@Ryan-A-Bradley
Copy link
Author

Also, this is the BIOS except mine says v2.02. I got this image from google
1 mpMZ0z-zqZ4IA6ylZOwA3w
.

@PartialVolume
Copy link
Owner

@PartialVolume
Copy link
Owner

PartialVolume commented Nov 17, 2021

Possibly under 'advanced settings'

@Ryan-A-Bradley
Copy link
Author

It says, on this BIOS system you can press CTRL+S on the tab "Main" in advanced settings to access special settings regarding SATA mode (which is apparently needed to switch it to legacy). I've changed it from RAID to AHCI and still unable to change the boot mode to Legacy.

@Ryan-A-Bradley
Copy link
Author

https://community.acer.com/en/discussion/615614/no-sata-mode-in-my-bios-predator-helios-300-ph315-53

tried this for help but doesn't seem to let me switch the boot mode. :/

@PartialVolume
Copy link
Owner

If this document applies to your model you may have to enable a setting that trusts the USB device to boot UEFI, not only that but the actual file name. Screenshot_20211117_194707

Any luck finding this setting that lets you set a trusted UEFI device?

@Ryan-A-Bradley
Copy link
Author

I've added the .efi to the trusted files for execution and it does the same thing. It boots to a black screen and then shows:

RecalBox
_

@Ryan-A-Bradley
Copy link
Author

EFI file boot 0: shredos

it's now displaying the file in the boot priority. i've named it "shredos". set shredos to 1st slot in priority order.

selected f12 to choose from boot order and attempted booting shredos.

loads a black screen and then shows:

RecalBox
_

@PartialVolume
Copy link
Owner

Has it got two discs in raid configuration or two separate device in non raid mode. Nwipe in shredos will only work in non raid mode.

It's also possible shredos doesn't have the latest driver, however if you loaded ubuntu 18.10 on it and it worked then shredos should work too.

@Ryan-A-Bradley
Copy link
Author

I'm able to switch it between the SATA modes:

ACHI
Optane without RAID
Optane with RAID

Same issue happens on all settings. And I'm unable to switch it from UEFI to Legacy no matter what SATA mode I choose.

I haven't tried installing Ubuntu 18.10 or later so I will download Ubunutu now and format it onto a USB to see if it works.

Note: This laptop was bought with Windows preinstalled on it and has the product key on the hardware (It wasn't manufactured with Linux on it and has never been tested with Linux on it). I'll begin the process now.

@Ryan-A-Bradley
Copy link
Author

Currently downloading https://old-releases.ubuntu.com/releases/18.10/

@Ryan-A-Bradley
Copy link
Author

Ryan-A-Bradley commented Nov 17, 2021

Just a quick example of what the hang looks like when I boot. I made it in Microsoft Paint while waiting for Ubuntu to download.
Untitled

@Ryan-A-Bradley
Copy link
Author

Update regarding Ubuntu 18.10: Currently using Rufus to format Ubuntu onto a USB.

@Firminator
Copy link

This is basically a known issue. See #34 and #48 (comment)

So far it's happening only on very new devices unless more reports are coming in from other people reporting the opposite.

@Ryan-A-Bradley
Copy link
Author

Ubuntu 18.10 successfully installed.

I will check the comment links now, Firminator. Thank you to both of you for helping me try to solve this issue and then further explaining that it's likely due to it being a very new device.

@PartialVolume
Copy link
Owner

PartialVolume commented Nov 17, 2021

I've noticed that shredos is lacking the /device/fb0 ( the frame buffer ). That used to work as I had used fbgrab etc to grab screenshots in the past. I've got a feeling the frame buffer may have got disabled when I started loading video drivers. Before I build tonights shredos I'll take a look at enabling the frame buffer. That would certainly cause this problem.

@Firminator
Copy link

Ryan,
Do you have an NVMe drive installed in that Acer laptop?

@Ryan-A-Bradley
Copy link
Author

Just wiped Ubuntu off it.

I'm also not sure what an NVMe drive is. If NVMe means "do you have an SSD in your laptop?", I have a 1TB SSD installed on the laptop.

@Ryan-A-Bradley
Copy link
Author

By the way, the main post of this thread is like half wrong because I accidentally posted specs for a different laptop.

My laptop is the ACER Predator Helios 300 15.6" Gaming Laptop - Intel® Core™ i7, RTX 3070, 1 TB SSD.

I accidentally posted Acer Predator Triton, which isn't the same laptop. I've edited the main post now so it's correct.

@PartialVolume
Copy link
Owner

Can you try this version of shredos. It's a version prior to me adding the video drivers and so the frame buffer may be working
https://github.com/PartialVolume/shredos.x86_64/releases/download/v2020.05.009_x86-64_0.30.001/shredos-2020.05.009_x86-64_0.30.001_20210217.img

@Ryan-A-Bradley
Copy link
Author

I will try it now. :D

@Ryan-A-Bradley
Copy link
Author

Ryan-A-Bradley commented Nov 17, 2021

Crashed again at this screen in the same way.

RecalBox
_
Untitled

@Firminator
Copy link

Yes same here.
What's your CPU and GPU?

@PartialVolume
Copy link
Owner

I just checked, the frame buffer isn't available in that version either. I'll go back further and check an earlier release.

@Firminator
Copy link

Mine is 11th gen Intel Core aka Tigerlake and it comes with this GPU:
https://en.wikipedia.org/wiki/Tiger_Lake#GPU
I don't have a dedicated GPU in this box.

@Firminator
Copy link

Firminator commented Nov 19, 2021

@Firminator Those other systems you said don't boot, are they the same, over 2 or 3 minutes to boot?

No. They don't finish booting at all. Just showing Recalbox and/or blinking cursor. I tested on 2 different devices that only have Intel CPU w/ GPU and no other GPU.

I have a lot of different devices that I can test on, but it's getting confusing now. As of now I think the issue is limited to Intel GPU not being recognized which could be addressed by testing different drivers, kernel, and grub settings. This surely is a rabbithole.

Adding SSH might be a good idea, but that would only help if the system actually finishes booting. As I see it some of the devices I tried on just freeze or (not visibly) crash.

@Firminator
Copy link

I think I'll upgrade to the latest buildroot and see if that sorts it out. I need to do that anyway. It may take a week or so before I can give you something to test due to work commitments.

Yes I think that's our best bet for now. Take it easy. We don't need you burned out. Thanks for providing ShredOS to us. I wish I had more experience and time to mess with configuring and compiling buildroot to help out here. Maybe over time I get a hang of it but it surely is a steep learning curve.

@Ryan-A-Bradley
Copy link
Author

Ryan-A-Bradley commented Nov 19, 2021

also, you said something about Nouveau.

the funny thing is, when i was installing ubuntu there was an initial kernel screen with 3 lines of text before the OS loaded and one of the lines said something about Nouveau.

i can't remember what it said though, would you like me to download ubuntu 18.10 and reinstall it to see the exact message?

@PartialVolume
Copy link
Owner

i can't remember what it said though, would you like me to download ubuntu 18.10 and reinstall it to see the exact message?

That will be for the Nvidia card. If you think it might of said something about the Intel GPU it might give us a clue.

Trouble with open source there's no revenue stream otherwise I would go out and buy the same laptop as you so I had something to work on.

@PartialVolume
Copy link
Owner

PartialVolume commented Nov 19, 2021

Yes I think that's our best bet for now. Take it easy. We don't need you burned out. Thanks for providing ShredOS to us. I wish I had more experience and time to mess with configuring and compiling buildroot to help out here. Maybe over time I get a hang of it but it surely is a steep learning curve.

Thanks, I also don't want to get too side tracked by ShredOS when I could be adding features into nwipe. I can add features far quicker to nwipe than I can diagnose weird kernel driver issues. That's not to say I don't want to fix those issues just itching to finally get secure erase and HPA/DSO into nwipe. 😁

@PartialVolume
Copy link
Owner

@Firminator
Copy link

Yes I think that's our best bet for now. Take it easy. We don't need you burned out. Thanks for providing ShredOS to us. I wish I had more experience and time to mess with configuring and compiling buildroot to help out here. Maybe over time I get a hang of it but it surely is a steep learning curve.

Thanks, I also don't want to get too side tracked by ShredOS when I could be adding features into nwipe. I can add features far quicker to nwipe than I can diagnose weird kernel driver issues. That's not to say I don't want to fix those issues just itching to finally get secure erase and HPA/DSO into nwipe. grin

I'm with you. We'll get the ShredOS booting issue figured out eventually. Bunch of people here on Github that might jump in and help.

@Firminator
Copy link

On this one particular machine I was testing this morning I finally drilled it down to one setting in the BIOS: CSM support.
Turn it on and it boots fine (although showing Recalbox) and then starts nwipe. No issues. 7 second boot. Done.
Turn CSM off and it stalls during boot and never finsihes.

2 additional settings I used:

  • Secure Boot off (we all know that Secure Boot needs to be off.)
  • Many BIOS also allow to choose between UEFi boot, Legacy Boot, and both (and then you have to choose which one is to be tried first). I left it at UEFI only. and it still worked with CSM on.

The thing is that more and more (modern) platforms have no Legacy mode anymore, and are UEFI-only... unless you coreboot'ed them to free them from the shackles :)

@PartialVolume
Copy link
Owner

That's interesting, it would imply there's a more pure UEFI, maybe one that's signed by Microsoft?, but then you would have thought that was what the secure boot switch was all about. I wonder what CSM is actually providing compatibility for?

@Firminator
Copy link

Firminator commented Nov 19, 2021

CSM is magic. That's all I know. Support for older hardware. There is probably documentaion on the UEFI.org site, but I never bothered to read this.

I think this might just be a buildroot issue. The way it's compiled or build. And what settings have to be set. I looked at this once and found this pretty intimidating. Is buildroot your choice of building the underlying OS and you would never consider abandoning it? I'm asking since I looked at other projects in the past and found some that looked promising.
[This is just inquiring here. Not a call to throw everything away and start all over.]

@PartialVolume
Copy link
Owner

I've also used cubic in the past to built a Ubuntu live that contains the latest nwipe. Cubic

I could also build a custom gparted live however the USB size is about 300MB compared to the current ShredOS of 51MB.

I do like how small and fast ShredOS is and I'm quite familiar with working my way around buildroot. I've just got to figure out why some Intel hybrid systems don't boot. I've got about 10 different PCs/laptops to test on and all except that Sony VAIO boot ShredOS perfectly but none are newer than 5 years old. Even boots perfectly on a MAC.

There's been a lot of updates to buildroot since the 2020.05 release so fingers crossed maybe an update will help. I'm planning on updating to the 2021.08.02 release sometime next week.

@PartialVolume
Copy link
Owner

One other thing about the most recent releases, I noticed that a 10 minute screen saver (blank screen) had some how become enabled. Press any key to un-blank. I don't know whether you've noticed that?

@Firminator
Copy link

Interesting. I know of gparted live (but had no idea that you can build your own). Never heard of Cubic ( Custom Ubuntu ISO Creator ) but it's appealing. I'd take a look at both and see if I can get something going just to gain some experience. Yocto seemed to have a steep learning curve, while minimal linux might be something I could get going.

Sounds like you have enough devices to keep you busy with testing. Glad you know your way around with buildroot. I was definitely overwhelmed with all the options in there. Had no idea that it works on a mac, too.
Yes keep it small by all means.

I haven't noticed the screensaver yet. Since all the changes with adding framebuffer drivers I wonder if some default video/screensaver setting got enabled. Maybe revert back to the old build?

@PartialVolume PartialVolume changed the title shredOS hanging (or crashing) during launch shredOS terminal compressed to top line of screen on multi GPU laptop Nov 20, 2021
@PartialVolume PartialVolume self-assigned this Nov 20, 2021
@PartialVolume PartialVolume added the bug Something isn't working label Nov 20, 2021
@PartialVolume
Copy link
Owner

PartialVolume commented Nov 21, 2021

@Firminator I'd rather not revert back to the old way unless there is a big disadvantage to using fbdev. Having /dev/fb0, fb1, fb2 etc enables the following features that weren't available before:

  1. Adjust the screen resolution via grub.cfg. In UEFI boot where it adopts the highest resolution of the monitor that can sometimes make the text too small, especially noticeable on a MAC, using the gfxpayload command you can alter the resolution to something more comfortable. Also possible in legacy where the text is too large and you want a higher resolution
  2. Snapshot the terminal to png file using fbgrab image.png. Or if you want to snapshot a specific virtual terminal from a different virtual terminal. fbgrab -cX image.png where X is 1, 2 or 3 on Shredos.
  3. Create a mp4 of the terminal using the command ffmpeg -f fbdev -framerate 30 -i /dev/fb0 output.mp4. This wasn't possible before. ffmpeg is included in the next release (also nvme-cli). For me this is really useful as I can easily produce the demo videos of nwipe which is what I used to create the demo video on the nwipe & Shredos github main pages. Kdenlive was used for the post processing effects, fade in/out, crop etc.
  4. Using setterm you can set up screen blanking (default 10 mins), fonts, resolution etc.

How to make a persistent change to the terminal resolution in Shredos

With the systems that just show the RecalBox and nothing else and also Ryan's problem with the terminal compressed to top of the screen, I think it's got everything to do with the system switching the framebuffer from the embedded Intel GPU to the secondary GPU. From what I've read so far, using the correct software we should be able to access the frame buffer correctly for the secondary GPU. When we see the Recalbox message, I think it's quite possible nwipe is running in the secondary framebuffer that we're not seeing. Apparently in some BIOS's you can disable one or the other GPU so it doesn't perform the switch, i.e it continues to use the same framebuffer it started with.

@Firminator @Ryan-A-Bradley Something that suddenly occurred to me. Does you laptop have a HDMI output? And can you plug that into a monitor? I was just wondering whether you would see nwipe appear on the HDMI output and the blank RecalBox on the laptop screen ?

@PartialVolume
Copy link
Owner

@PartialVolume
Copy link
Owner

@Firminator Are any of those systems you have that just show the blank Recalbox screen, do they happen to have a discreet secondary GPU that can be removed? If it then works it would seem to confirm there is issue accessing the secondary framebuffer.

If I plug a secondary graphics card into my Dell which has onboard graphics, even if you connect a VGA lead to the on board graphics saying something to the effect that you have a secondary card, you can't connect to the onboard GPU. Maybe some bios's don't bother giving the user that warning so you are left wondering why your screen is blank after the initial boot up text. With the Dell I think you can override auto selection of the GPU and just use embedded or onboard.

@Ryan-A-Bradley
Copy link
Author

if it does have HDMI output (which it probably will), i'll be testing it later on today connected up to a monitor.

@Firminator
Copy link

Firminator commented Nov 22, 2021

The devices I tested on have no secondary GPU. Just Intel GPU. The Recalbox message and then halting/crashing/stalling ShredOS working as intended (but without a working screen output!) is a problem that stems from UEFI/CSM. Use LegacyBIOS mode (if the BIOS provides that) and the issue goes away. Someone else reported this back in June @ #34

I also tested on a device with an NVIDA card and no Intel GPU and ShredOS boots fine. But this device has no UEFI, so it's no surprise.

The other issue (this thread) is multi GPUs (NVIDIA or ATI AND Intel GPU build-into CPU). I guess you can test that using an HDMI output. That's a good idea. I don't have a device to test this currently.

@Firminator
Copy link

Firminator commented Nov 23, 2021

#34 reported the same I'm now realizing (edited my comment above also). Turn CSM off and it fails to output video. Turn CSM on and it works. Regardless this is an UEFI problem since most recent devices are UEFI-only with no CSM option in the BIOS anymore.

@PartialVolume
Copy link
Owner

I'm hoping the new frame buffer software will fix this, if not I'll need to dig deeper into Recalbox and possible alternatives like clover. On a different subject, as I've been working through the new build, I realised previous version had the hibernate code (sleep to disc) installed, rather than sleep to RAM. Important for unfreezing SSDs and may have been why I was having problems with waking from sleep as part of the SSD secure erase process.

@PartialVolume
Copy link
Owner

@Ryan-A-Bradley Can you download this .img file. Shredos 2021.08.2 legacy and UEFI bootable It's the latest 2021.08.2 development release. It should hopefully resolve this issue. Please let us know how it goes. Thanks.

@Ryan-A-Bradley
Copy link
Author

@PartialVolume it's fixed! working 100%. i'm even using it to wipe the other laptop right now. thank you so much! :D

@Ryan-A-Bradley Ryan-A-Bradley changed the title shredOS terminal compressed to top line of screen on multi GPU laptop shredOS terminal compressed to top line of screen on multi GPU laptop [fixed] Nov 27, 2021
@PartialVolume
Copy link
Owner

@Ryan-A-Bradley Excellent, glad it's working.

@PartialVolume
Copy link
Owner

PartialVolume commented Nov 27, 2021

Just to clarify for others reading this. This problem is fixed in the development version 2021.08.2 of ShredOS that hasn't been officially released yet. The development version will be officially released in the next few days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants