Black screen after new installation reboot

General system EndeavourOS installation
21

These were my partitions

image-106
image-106847Ɨ168 18.1 KB

97.66 gb NTFS for endevourOS
19.53 gb FAT32 for the EFI system partition

22

I feel like this could work but idk what to tweek

23

It installed when i flagged the EFI and endevourOS partition as boot , sadly after rebooting into my ssd it still said ā€œinvalid partition!ā€ Iā€™m probably gonna give up on endevourOS if I canā€™t find a solution for this

24

can you please report

sudo parted -l
  • your disk is formatted MBR , you cant have more than 4 partitions
  • support extended partition is not useful here
  • i suggest first that to see under windows how to convert MBR to GPT disk in this situation,
  • do a backup before any convert or reinstall windows with UEFI

under GPT you can have more partitions.

25

I didnā€™t even know MBR had a partition limit thank you for bringing that to my attention

26

In Legacy Bios Mode you do not need EFI, and 19gb is way to big 2GB is recommended. But you are on MBR/legacy/Bios no need for EFI at all. Secondā€¦ NTFS is not a supported filesystem to install Linux in general.

On legacy mode you only need any Linux compatible partition with extra per example market bit the boot flag.

27

Thanks for the reply Iā€™ll be sure to keep that in mind and update you

28

see more with

1 Like
29

image-133
image-133608Ɨ224 78 KB

30

I still canā€™t boot windows with this even though 3 primary partitions with an extended partition and a logical partition inside it should not be stopping the boot (Iā€™m trying to access windows to backup my drive to convert it to GPT) , do I just need to get rid of another partition?

31

I checked my BIOS version and apparently itā€™s extremely outdatedā€¦whoops- , that might be why Iā€™m running into so many problems :sweat_smile:
The BIOS version is A01 btw

32

Usually you should not need to convert to gpt

we do not even know if your system supports uEFI.

33

Think it does support UEFI

Type: Laptop System: Dell product: Latitude E6330 v: 01
    serial: <superuser required> Chassis: type: 9 serial: <superuser required>
  Mobo: Dell model: 0NG17W v: A00 serial: <superuser required>
    uuid: <superuser required> UEFI: Dell v: A01 date: 04/25/2012
1 Like
34

The first few attempts at installing endevourOS I had launched the installer from my usb from the UEFI option and not legacy mode , but it just showed a blackscreen when I tried to launch endevourOS after installation from UEFI so idk might just be a BIOS issue since the BIOS updates effect operating systems

35

I could try to flash update my BIOS with another usb but itā€™s risky since Iā€™m jumping from A01 to A20

36

I could try running ā€œbootrec /fixbootā€ from windows 10 on a USB that seems like it would fix it , or atleast give me access to windows on my ssd

37

Tried the ā€œBoot existing OSā€ option when I boot from usb in legacy mode (this is on the usb that has endeavourOS) , I chose the partition that had windows on it , the error message reads : "Windows failed to start. A recent hardware or software change might be the cause. To fix the problem

  1. Insert your windows installation disc and restart your computer
  2. Choose your language settings , and then click ā€œNextā€
  3. Click ā€œRepair your computerā€

If you do not have this disc , contact your system administrator or computer manufacturer for assistance

File : BOOT/BCD
Status : 0xc000000f
Info : The boot configuration for your PC is missing or contains errors"

38

Tried to boot into a windows 10 usb to troubleshoot it with that but windows couldnā€™t fix the issue , so Iā€™ll just try to flash update my bios

39

Update : BIOS refuses to updateā€¦? , even when I type /forceit in DOS it just restarted without updating , I then got a bootable windows 10 usb and tried to check my C drive for errors , and from what I could tell when endeavourOS was trying to install itself it tried to write itself in my boot config file but because my BIOS is very outdated it just ended up not working , I think Iā€™ll have to manually fix my boot file , Iā€™ve already tried the ā€œRepair startupā€ option on the windows 10 USB , but it just said ā€œWindows couldnā€™t fix your issueā€ , then I tried from cmd in the usb these commands :

  1. bcdboot C:\Windows /S C:
  2. bootrec /rebuildbcd
  3. bootrec /fixboot
  4. bootrec /fixmbr
  5. bootsect /nt60 all /force

Most of these were responded with ā€œmissing operationā€ which leads me to believe that the boot file is just rendered unusable at the moment

If anyone else has any info or anything they would want me to try let me know

40

bcdboot C:\Windows /s C: /f BIOS if legacy installā€¦

1 Like