Unable to install fresh Manjaro

[wind77]

@Kobold

TTY on your install could probably indicate what is running and what is not.

Hmm… do we have a misunderstanding here?
My current working Manjaro was installed with a >10 yr old dGPU.
My objective to install a fresh Manjaro is because I want to remove the dGPU and rely on the iGPU in my AMD 5700G.

If I simply remove the dGPU and try to boot into existing Manjaro using iGPU, the display would turn blank.

@Kobold

As far as i know, Secure Boot and TPM requires UEFI… and can’t work under Legacy anyways.

Legacy?
U referring to MBR or CSM?
in BIOS, when CSM is ON, the option to toggle Secure Boot is disable.
And with Ventoy, I can install W11 regardless of CSM status.
But again, let’s not venture into W11 in Manjaro forum.

@Kobold

So when you maybe have a broken system and you want to trouble shoot with Windows… it makes total sense to not use a Win OS which has even stronger incompatibility to Linux as Win11, and this is Win10.

I believe you are mentioning this as a general guide, rather than a troubleshooting step for my current issue?
Gotcha~

[BG405]

@wind77

the option to toggle Secure Boot is disabled

But is Secure Boot disabled? … maybe you need to disable it with CSM disabled, and then re-enable CSM? Although I don’t see what difference it would make if you are booting with EFI.

@wind77

U referring to MBR or CSM?

Legacy (traditional BIOS) boot normally uses MBR partition scheme, (U)EFI has to be GPT partition scheme (which is what you have).

CSM = Compatibility Support Module, or Mode, whatever; this allows a modern (U)EFI-based system to work with the older Legacy boot if required.

It is of course possible to install in Legacy mode on a GPT-partitioned disk, but this involves a couple of extra steps and not generally recommended (I have this machine set up that way, but I have my own reasons for that).

For reference:

• UEFI = Unified Extensible Firmware Interface (IIRC);
• Legacy = BIOS = Basic Input Output System (the “old” way)
• MBR = Master Boot Record partitioning scheme (limited to 4 primary partitions)
• GPT = GUID Partition Table → modern machines are generally EFI aware and GPT is needed for this mode to work.

If I’m not entirely accurate on this, I’d appreciate corrective advice (or action).

Are you using the “Install alongside …” (or whatever the wording is) or setting up the partitions yourself, for this install?

[wind77]

@BG405

Legacy (traditional BIOS) boot normally uses MBR partition scheme, (U)EFI has to be GPT partition scheme (which is what you have).

Ah, i see.
My motherboard is X570S, so the boot should be UEFI.

@BG405

But is Secure Boot disabled? … maybe you need to disable it with CSM disabled, and then re-enable CSM? Although I don’t see what difference it would make if you are booting with EFI.

I also have the same question: what difference it would make if I’m booting with EFI?
For the sake of eliminating potential “interference”, let me double check and verify.

@BG405

Are you using the “Install alongside …” (or whatever the wording is) or setting up the partitions yourself, for this install?

My issue is: i can’t even enter live media environment, so this question is irrelevant.
If this is merely your curiosity, my answer is: I’m plannng to do a manual partitioning - format a partition and install fresh Manjaro.

[Teo]

If you see something about raid0 in the bios, you have to disable that too.

[Mirdarthos]

@wind77

My motherboard is X570S, so the boot should be UEFI.

Assuming makes an ASS out of U and ME.

So don’t assume. Rather ensure.

[wind77]

@Teo

If you see something about raid0 in the bios, you have to disable that too.

Yup, Raid for nvme and SATA, are both disabled.

@Mirdarthos

So don’t assume. Rather ensure.

/sys/firmware/efi exists.
Is that confirmative?

[Mirdarthos]

@wind77

/sys/firmware/efi exists.

That mean it’s using UEFI yes. It also means that, theoretically, it should be using the GPT partitioning scheme. But confirm that first:

fdisk --list /dev/<disk> | grep 'type: '

Where <disk> is the partition you wish to install on.

Mine, for example:

$ fdisk --list /dev/nvme0n1 | grep 'type: '
Disklabel type: gpt

It should be GPT for UEFI. And then CSM (or legacy mode, or something) should be disabled.

[wind77]

@Mirdarthos

It should be GPT for UEFI.

This I can confirm through my current installation.

But my issue remains: I cannot boot into live media environment, so it is too early to talk about GPT or MBR selection.

[Mirdarthos]

The errors in your screenshot:

@wind77

…speak of an MD array, which you said is disabled. I’ve never before seen it, so while I’m not calling you a liar, it seems that it’s not disabled really. So double-check it.

[wind77]

@Mirdarthos

…speak of an MD array, which you said is disabled. I’ve never before seen it, so while I’m not calling you a liar, it seems that it’s not disabled really. So double-check it.

Hardware Raid on motherboard, is disabled.
MD array that you saw, is software raid.

[Mirdarthos]

@wind77

MD array that you saw, is software raid.

And that, that, that is probably the reason for your problems and I won’t be able to help, apart from pointing you at:

https://wiki.archlinux.org/title/RAID#Installing_Arch_Linux_on_RAID

[wind77]

@Mirdarthos

And that, that, that is probably the reason for your problems and I won’t be able to help, apart from pointing you at:

Another misunderstanding…

I’m trying to install fresh Manjaro on nvme stick (GPT, non-Raid), not Raid HDD.

And also, let me emphasize again:
when the installer tried to launch live media environment, the display went blank (monitor has HDMI signal, but no display).
Since I cannot “see” the live media environment, I cannot proceed to begin the installation.

So this is not a Raid issue.

[Mirdarthos]

It very well might not be. But it also might. Stop assuming. Rather confirm it by disconnecting the RAID discs. If you have 'em, you probably know how to add them afterwards.

But I know nothing of it.

[wind77]

@Mirdarthos

Rather confirm it by disconnecting the RAID discs.

When I started using Raid on Linux years ago, I had encountered various issues.
To summarise, if Raid is the culprit in the installation, then one of the following would happen:

a. it will hang during kernel loading step (the screenshot which u referred to earlier)
b. the kernel loading step encounters error and auto reboot
c. the selection of partition in live media would be affected.

Having blank screen is not one of the characteristics of Raid problem, this I can assure you.

[Mirdarthos]

Well, I know nothing more, and can’t suggest anything else. And…

no, it’s OK. I’ll shut my yap.

[Teo]

I guess some problems are just not to be solved. The only thing you can do if a live usb is not booting is to thinker with the kernel command line, but to do this you have to have some idea what is wrong. Otherwise…there is no chroot, no tty, no journal in this case.
A shot in the dark: you can try to once again check the hash of the iso and recreate the media in another way - balena, rufus, dd, ventoy…
And probably the last thing you can do before switching to another distro: find an older iso, with an older kernel and try that. Although it will then be a big pain to update, but at least you will know if it is the kernel, and you can then maybe go the way to create your own install iso with the older lts kernel, like 5.15 for example.

[dmt]

@wind77

My current working Manjaro was installed with a >10 yr old dGPU.
My objective to install a fresh Manjaro is because I want to remove the dGPU and rely on the iGPU in my AMD 5700G.

Have you tried this?

Switch over to the iGPU in the UEFI, then remove the dGPU, plug the monitor into the motherboard, and boot up. If you get a black screen then try switching to a tty, log in and install the driver, then reboot.

Configure Graphics Cards

EDIT:

Added missed step.

[soundofthunder]

Remove the dGPU.

If my presumption is correct, after removing the dGPU, it should switch automatically to the iGPU. If my presumption is incorrect, there will be a manual switch/toggle (of some kind) found in your BIOS; either that, or a priority mechanism.

From that point (if successful) you should be able to perform operations as expected; as suggested by @dmt

[dmt]

@soundofthunder

after removing the dGPU, it should switch automatically to the iGPU.

It might not, so as you say, best to switch first.

Thanks for catching that.

[wind77]

@Teo

A shot in the dark: you can try to once again check the hash of the iso and recreate the media in another way - balena, rufus, dd, ventoy…

The current Manjaro ISO is installed using Ventoy.
With dGPU, the ISO can be installed successfully.
So I guess both the ISO and Ventoy are functioning?

@Teo

And probably the last thing you can do before switching to another distro: find an older iso, with an older kernel and try that. Although it will then be a big pain to update, but at least you will know if it is the kernel, and you can then maybe go the way to create your own install iso with the older lts kernel, like 5.15 for example.

Alright, let me try this.
For older releases, is this GitHub - manjaro/release-review: Monthly Review-ISOs for Manjaro Linux the official place to download?

@dmt

Switch over to the iGPU in the UEFI, then remove the dGPU, plug the monitor into the motherboard, and boot up.

I tried 2 configurations:

1. Configured the BIOS to 1st boot on iGPU, shutdown, removed dGPU, rebooted. There was display till the Live Media Menu screen. Then, blank screen (have HDMI signal, but black screen).
2. Configured the BIOS to 1st boot on PCIe1, shutdown, removed dGPU, rebooted. There was display till the Live Media Menu screen. Then, blank screen (have HDMI signal, but black screen).

@dmt

If you get a black screen then try switching to a tty, log in and install the driver, then reboot.

sudo mhwd -a pci free 0300?
I’m using AMD 5700G.

@soundofthunder

If my presumption is correct, after removing the dGPU, it should switch automatically to the iGPU.

Correct.