I can't boot from a BlackArch USB device on an MSI laptop

[osprey]

Maybe F6 is disabled, try also CTRL+ALT+F3 and CTRL+ALT+F4, or try every one from F1 to F12 while pressing CTRL+ALT

If it's still not working what could make it work is booting in recovery mode and try again, but your boot menu doesn't have this option.


It's not typo, his laptop model is UCX not UC.
Anyway your nouveau link doesn't explicitly list RTX 2050 either.

Sorry to mislead. Following the link in post #7 led to UDX but I was unable to find similar specs on UCX, and knowing how such things are inconsistent, was left with inadequate information.

It's not clear to me what the current state of affairs with the machine is, what all the things that have been tried and what succeeded or failed. Hence, some questions for @Ali711:

What is on the drive on the machine?
Is there an existing installation on it?
Have all attempts at installing a distro on this machine, other than Kali mentioned in post #1, failed?
When Kali was tried and succeeded, was there a GUI login that succeeded?

If all subsequent attempts at installation have failed with an installation usb stick that is known to be good, then an alternative approach may be necessary.

In the case where nothing can install, it may be possible to boot up a live disk, or a rescue disk such as systemrescue, and do some work. Since a live disk or rescue disk can work totally in RAM, it can gather information about the computer such as its graphics card, the drive etc., and can also be used to wipe the disk clean so that no left-over software on it can interfere with a new installation. The health of the computer's drive can also be tested from a live disk or rescue disk.

If after cleaning the disk, installation still fails, then it's likely the drive is the problem.

The details of how all the work can be accomplished can be outlined in detail, but first readers would be best informed of the actual latest situation.

 

[CaffeineAddict]

Following the link in post #7 led to UDX but I was unable to find similar specs on UCX, and knowing how such things are inconsistent, was left with inadequate information.

That's strange, I get 3 columns with models when clicking on link, UCX states this:

 

[Ali711]

Is the machine able to boot to a text prompt as outlined in the link in post #11?

I can access GRUB via the command.

nomodeset i915.modeset=0 nouveau.modeset=0

image hosted at ImgBB

Image image hosted in ImgBB

ibb.co

Note the typo in post #7 (the webpage shows RTX 3050 not 2050).

There are three versions of the MSI Thin GF63 laptop, you can find out from the link in post #7 by clicking right/left.

The problem is that manufactures do alter hardware at times with inconsistent attention to model numbers, so the only valid means of determining what the graphics card actually is to run a command such as the following:

lspci -nnk | grep -i vga -A3

That command will also show if a driver is actually loaded.

I executed the command and this is what appeared.

image hosted at ImgBB

Image image hosted in ImgBB

ibb.co

 

[osprey]

Thanks for that correction. You are correct! I missed the right arrow head to access the other screens where the information existed in my haste. Fortunately, the consequences are not an issue at this point for the original poster, but I take the lesson

 

[Ali711]

Maybe F6 is disabled, try also CTRL+ALT+F3 and CTRL+ALT+F4, or try every one from F1 to F12 while pressing CTRL+ALT

If it's still not working what could make it work is booting in recovery mode and try again, but your boot menu doesn't have this option.


It's not typo, his laptop model is UCX not UC.
Anyway your nouveau link doesn't explicitly list RTX 2050 either.

I tried all the commands.
CTRL+ALT +F1~F12 & DEL & Fn
Nothing happened.

 

[CaffeineAddict]

According to screenshot on the link below you may be able to edit boot options by pressing TAB key:

Blackarch install

How to install Blackarch on hard drive or virtualbox

www.blackarch.org

If yes you can try add GRUB_CMDLINE_LINUX="nomodeset" which means:

Hardware Compatibility: Sometimes, certain hardware components may cause issues during boot. You can use kernel command - line arguments to disable or modify the behavior of these components. For example, if you are experiencing problems with your graphics card, you can add the nomodeset argument to disable the kernel’s attempt to set a graphical mode.

Understanding and Utilizing `grub_cmdline_linux`

In the realm of Linux systems, GRUB (Grand Unified Bootloader) plays a pivotal role in the boot process. It allows users to select the operating system and kernel to boot into. One of the key aspects of GRUB configuration is the `grub_cmdline_linux` parameter. This parameter enables users to...

linuxvox.com

GRUB_CMDLINE_LINUX

• Entries on this line are added to the end of the 'linux' command line (GRUB legacy's "kernel" line) for both normal and recovery modes. It is used to pass options to the kernel.

Grub2/Setup - Community Help Wiki

This means if editing options is not possible with TAB key you can run EFI shell option from boot menu to manually boot and then for the linux command append nomodset to disable video.

Don't ask me how, I know how to manually boot from grub shell but not from EFI shell.

 

[Ali711]

What is on the drive on the machine?
Is there an existing installation on it?
Have all attempts at installing a distro on this machine, other than Kali mentioned in post #1, failed?
When Kali was tried and succeeded, was there a GUI login that succeeded?

Windows 11

Yes

I don't want to install the distro on my laptop, I want to boot from the USB Flash Drive.

The default interface is 3 options: Live Boot, Persistence, and some other options. I was presented with a default interface for booting from USB Flash Drive in a successful way

If all subsequent attempts at installation have failed with an installation usb stick that is known to be good, then an alternative approach may be necessary.

In the case where nothing can install, it may be possible to boot up a live disk, or a rescue disk such as systemrescue, and do some work. Since a live disk or rescue disk can work totally in RAM, it can gather information about the computer such as its graphics card, the drive etc., and can also be used to wipe the disk clean so that no left-over software on it can interfere with a new installation. The health of the computer's drive can also be tested from a live disk or rescue disk.

I don't want to install BlackArch Linux as a platform but as a Live Boot System via USB Flash Drive.

 

[osprey]

Windows 11

Yes

I don't want to install the distro on my laptop, I want to boot from the USB Flash Drive.

The default interface is 3 options: Live Boot, Persistence, and some other options. I was presented with a default interface for booting from USB Flash Drive in a successful way

I don't want to install BlackArch Linux as a platform but as a Live Boot System via USB Flash Drive.

Thanks for the clarification. I understand now that you wish to run a "Live Boot System via USB Flash Drive." I take it then that the usb won't boot to RAM so that you can use it.

Presumably the MS installation on the disk works as intended.

It may be that the absence of the proprietary nvidia graphics drivers in the usb you are using is the issue. In that case, you would likely need a usb with persistence, boot to a text console, set the network up, and download the nvidia drivers either from the distro repository (which is usually recommended) or from nvidia, and install them on the persistent usb.

It may be necessary to add a boot option to get the usb to boot to a text console. Not being familiar with the usb you are using, I can't provide instructions on how to do that, but there may be a means.

 

[CaffeineAddict]

Or even better use some other live distro that works so you save yourself the trouble.

 

[f33dm3bits]

I don't want to install BlackArch Linux as a platform but as a Live Boot System via USB Flash Drive.

I didn't get that until now.

It may be that the absence of the proprietary nvidia graphics drivers in the usb you are using is the issue.

I have an Nvidia gpu as well, so I just created a usb flash drive with Black Arch and booted it. It wouldn't launch the display manager but I was able to switch ttys.

Boot from USB flash stuck here, does anyone know how to solve this

image hosted at ImgBB

Image image hosted on ImgBB

ibb.co

Here's where it gets stuck for me.

So after the display manager is started nothing happens for me either, it doesn't switch to a login screen. So I'm going to say it's the Nvidia gpu that's the problem.

 

[osprey]

I didn't get that until now.

I have an Nvidia gpu as well, so I just created a usb flash drive with Black Arch and booted it. It wouldn't launch the display manager but I was able to switch ttys.


Here's where it gets stuck for me.
View attachment 27385
So after the display manager is started nothing happens for me either, it doesn't switch to a login screen. So I'm going to say it's the Nvidia gpu that's the problem.

Thanks for that investigation @f33dm3bits . It did take some time for @Ali711 to provide the clarity readers needed, but I think you have nailed it!

 

[f33dm3bits]

@Ali711
I think our system also seems to have an integrated intel gpu chip but not sure?

Intel UHD Graphics Xe G4 48EUs

If that's the case you could try disabling your Nvidia gpu that way making it force to use the intel video chip.

Going to test out one last thing.

 

[f33dm3bits]

I think our system also seems to have an integrated intel gpu chip but not sure?
If that's the case you could try disabling your Nvidia gpu that way making it force to use the intel video chip.

@Ali711 Never mind this.

Going to test out one last thing.

I just tried one last thing which is before having the iso boot I added "modeset=0" to the boot menu by pressing "e" then adding that and pressing enter to boot. After that it does start/switch over to the graphical environment.

So you can try that as well, booting with either "modeset=0" or "nvidia-drm.modeset=0" should also work for you.

 

[Brickwizard]

I don't want to install the distro on my laptop, I want to boot from the USB Flash Drive.

we have been running round in circles for most of the week, so
switch off windows quick start [and temporary secure boot]
do a full power re-boot not re-start
now you need 2 clean USB sticks, one at least 8gb with the bootable ISO and one at least 32gb for the live drive.
put the 2 drives in the machine
switch on tickling the short boot menu key [usually F12, but varies by make]
from the short boot menu find the USB with the ISO and open... if all goes well you will now be in test mode
connect to wi-fi in test mode
select install,
when it gets to partitioning select use complete disc, NOW THE BIT YOU MUST BE CAREFUL WITH
from the drive selection box [currently showing your onboard main drive, click the dropdown box and select the second USB that you want to install to and press then continue
it should now install your Linux to the destination pen drive
once installed you can re-enable secure boot, but not quick start'
to use, open the full bios/UEFI and make sure boot from USB is enabled, and in the master boot it has USB first then HDD and the rest

now if everything has gone to plan when you put your usb with the distribution in the machine and switch on it should boot straight away

 

[f33dm3bits]

we have been running round in circles for most of the week, so

I already figure it out because I ran into the same when booting the Black Arch iso.

booting with either "modeset=0" or "nvidia-drm.modeset=0" should also work for you.

 

[theLegionWithin]

I just tried one last thing which is before having the iso boot I added "modeset=0" to the boot menu by pressing "e" then adding that and pressing enter to boot. After that it does start/switch over to the graphical environment.

So you can try that as well, booting with either "modeset=0" or "nvidia-drm.modeset=0" should also work for you.

I was curious about why this sort of thing is occurring - when I was using nvidia hardware on my old rig (using Arch) I'd never run into this sort of issue. now, granted I was using a somewhat older nvidia architecture, but it got me curious so poked around for a bit and found the following:

=================================================================================
The Nvidia GeForce RTX 2050 is based on the Ampere architecture - though it is branded as part of the RTX 20 series, which primarily uses the Turing architecture, the RTX 2050 utilizes the GA107 graphics processor, which is an Ampere-based chip (the same silicon found in the RTX 3050 and RTX 3050 Ti Mobile, but with some features disabled to meet the RTX 2050's target specifications).

If BlackArch Linux installation hangs at the graphical interface upon booting when using an NVIDIA GeForce RTX 2050 without the modeset=0 kernel parameter in GRUB, here's a likely explanation:
- The proprietary NVIDIA drivers for Linux utilize a feature called Kernel Mode Setting (KMS) for direct control of the display hardware. However, this implementation can be problematic, especially with newer hardware and certain kernel/driver combinations. When KMS is enabled (which it is by default unless explicitly disabled), the NVIDIA driver attempts to configure the display early in the boot process. If this process encounters an incompatibility or a bug, it can lead to the system hanging before the graphical environment can fully load.

- Adding modeset=0 to your GRUB configuration disables NVIDIA's KMS implementation, forcing the system to fall back to a different display mode. This allows the system to bypass the potentially problematic KMS initialization and proceed to a console login or a fallback graphical environment, even if it's not the optimal display configuration.
=================================================================================

these new-fangled "AI" search bots often hallucinate and/or provide incorrect information but with proper and specific prompting getting a summarization sure does save some time.

 

[f33dm3bits]

I was curious about why this sort of thing is occurring - when I was using nvidia hardware on my old rig (using Arch) I'd never run into this sort of issue. now, granted I was using a somewhat older nvidia architecture, but it got me curious so poked around for a bit and found the following:

OP is running BlackArch which has a live environment, you probably installed Arch how you normally do and install and configure everything you need so that's why you haven't run into it. Same reason why I haven't run into it with my own Arch installation but did when booting the Black Arch live iso.

Kernel mode setting - ArchWiki

 

[Ali711]

Thanks for that investigation @f33dm3bits . It did take some time for @Ali711 to provide the clarity readers needed, but I think you have nailed it!

I apologize for this English is not my native language.

I used translation software most of the time.

 

[Ali711]

So you can try that as well, booting with either "modeset=0" or "nvidia-drm.modeset=0" should also work for you.

It didn't work for me, are there other ways?

 

[Ali711]

OP is running BlackArch which has a live environment, you probably installed Arch how you normally do and install and configure everything you need so that's why you haven't run into it. Same reason why I haven't run into it with my own Arch installation but did when booting the Black Arch live iso.

Kernel mode setting - ArchWiki

Finally, arrived in the long-awaited graphic environment via the command

nouveau.modeset=0 rd.driver.blacklist=nouveau

Now how can I solve the problem?
Or do I have to write the above command every time?