The system refuses to boot on any computer (HP & Dell) that I use

[joekamprad]

Disk /dev/sdb =gpt UEFI

Disk /dev/sdc =dos legacy

so this can be your issue… system seems to be running in legacy mode… but EndeavourOS is installed in UEFI mode

[Marqui]

Ok, but was was it working fine since last week ? it seems incomprehensible.

[Marqui]

don’t read …

[Marqui]

Ok

[Marqui]

Is there any solution ?

[Root]

@Marqui

Is there any solution

I don’t think your different partition schemas is the cause of the issue - at least not my first impression.

I am running a system using Arch and a Nvicia Quadro P2000 graphics and I have no issues with the arch nvidia driver.

I am fairly convinced that my lack of issues is due to my chosen system which is not KDE - and for completeness not Gnome as well.

With the grub menu - I was referring to it as the means to load the base system and in the process bypass the display manager and in so process - boot to a commandline.

Booting to said commandline would verify that it is your graphical environment which is causing your issues.

Your issue is quite common ATM and I am fairly certain this is due to how KDE is handling graphics.

Those semi-annual breakages are common for KDE and Gnome on Arch based systems.

[Gilmage]

So I am the guy who posted that picture before, since then I am not using EndeavourOS but similar problems were consistent with Manjaro as well the solution for me, was to update my BIOS.

[Marqui]

Ok, thanks for your explanation. Back to XFCE ??

[Marqui]

Ok, thank you. I’ll try and come to update my BIOS; back for more comments.

[Root]

@Marqui

Back to XFCE

XFCE is the goto desktop environment - when you value stability.

My environment is fully customized enviroment which suits my workflow - and should I add - I am putting stability over pretty much everything.

[joekamprad]

03:00.0 VGA compatible controller: NVIDIA Corporation GF100GL [Quadro 6000] (rev a3) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation GF100GL [Quadro 6000]
Physical Slot: 2
Flags: bus master, fast devsel, latency 0, IRQ 30, NUMA node 0
Memory at f4000000 (32-bit, non-prefetchable) [size=32M]
Memory at e8000000 (64-bit, prefetchable) [size=128M]
Memory at f0000000 (64-bit, prefetchable) [size=64M]
I/O ports at e000 [size=128]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities:
Kernel driver in use: nouveau
Kernel modules: nouveau

may i over-read… but are you using the propritary Nvidia Drive ror open source Nouveau on installed system?

[jonathon]

@Marqui

I restarted my system (after update) and again, impossible to boot

[FAQ] Computer doesn’t boot, boots to a black screen, or stops at a message

While there are many potential reasons why your installation doesn’t boot to a desktop, the primary reason is that the graphics drivers haven’t loaded correctly so your login/display manager (DM) doesn’t start. This is why you get a “black screen” or stuck at an [ OK ] Started some service message. The normal reason for this is that you have the incorrect driver version for the kernel. This can happens when the mirror you are updating from is not fully synchronised, or times out, and so y…

I suspect that either the Nvidia driver did not build correctly, or it was updated and support for your GPU was removed.

@Marqui

the system refuses to boot on any computer (HP & Dell) that I use.

If you install and configure drivers for one PC then the OS won’t boot correctly on a system with different hardware. By leading with this you’ve sent everyone off on a “wild goose chase”. See also: http://mywiki.wooledge.org/XyProblem

[ricklinux]

Maybe you can boot on the live ISO and give the link to the following.

inxi -Faz --no-host | eos-sendlog

[antechdesigns]

@jonathon

If you install and configure drivers for one PC then the OS won’t boot correctly on a system with different hardware. By leading with this you’ve sent everyone off on a “wild goose chase”.

that’s how I read it, which is why I never replied

[fbodymechanic]

I run one.

In my test computer lol. Best $25 ever.