INstalled new Graphics card-system won't boot now

General system Kernel, boot, graphics & hardware
1

Hey Everyone,

Well, just when things were going great with EndeavourOS I randomly popped into a PC store and they had a 5080 in stock.

The 5080 works fine in Windows. Played games on it all last night. No issues.
The two times I tried to boot into Linux the boot process got hung up on detecting graphics…

I left it at this for 30 minutes each time I tried. Once with normal boot and once with fail safe.

Each time I ended up shutting down the system and going back into Windows.

A pick of where it gets hung up:

Hung up loading graphic profile

I am also making an EndeavourOS live-boot so I can attempt to boot from it and grab some graphics card info in case this will help resolve the issue.

2

a 5080 what?
what did you replace? (Nvidia, Amd or other?)

3

Does it work if you choose the fallback kernel image to boot from?

4

I assume you mean the recently released nvidia rtx 5080.

It’s a very new card, might not work with nouveau yet so it’s possible you have to install the nvidia driver before inserting the card (e.g. pop the card out, boot into linux, install the driver, shut down, re-insert card, and then try again)

I believe the standard way to install nvidia drivers on eos is through nvidia-inst but I might be misremembering.

Edit: If it stopped on graphical target that is indicative of graphic driver issues further supporting my idea, however it could also depending on your setup just be simple misconfiguration.

Especially if you’re using X and not Wayland.

5

Hi Guys,

Sorry for my lack of info on the initial posting.

Nvidia 5080

I only tried to boot with what I seen was available

normal boot and fallback boot (is this the same as fallback kernel boot?)

I did live-boot from last releases live-boot (kernel 6.10) and so, some info below.
I am unsure what is useful info or not so posting it all and sorry for the large amount of probably useless info included:

I have but did not include glxgears info as it is based on the nouveau driver used by the liveboot.
IF you want it just ask :slight_smile:

[liveuser@eos-2024.09.22 ~]$ sudo lspci
00:00.0 Host bridge: Intel Corporation Device a700 (rev 01)
00:01.0 PCI bridge: Intel Corporation Raptor Lake PCI Express 5.0 Graphics Port (PEG010) (rev 01)
00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 01)
00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 Gb/s) XHCI Host Controller (rev 11)
00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #0 (rev 11)
00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 (rev 11)
00:17.0 SATA controller: Intel Corporation Raptor Lake SATA AHCI Controller (rev 11)
00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #21 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Raptor Point-S PCH - PCI Express Root Port 3 (rev 11)
00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 (rev 11)
00:1d.4 PCI bridge: Intel Corporation Device 7a34 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 11)
00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio Controller (rev 11)
00:1f.4 SMBus: Intel Corporation Raptor Lake-S PCH SMBus Controller (rev 11)
00:1f.5 Serial bus controller: Intel Corporation Raptor Lake SPI (flash) Controller (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 2c02 (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 22e9 (rev a1)
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
05:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN770 / PC SN740 256GB / PC SN560 (DRAM-less) NVMe SSD (rev 01)
06:00.0 Non-Volatile memory controller: Intel Corporation SSD 660P Series (rev 03)
[liveuser@eos-2024.09.22 ~]$

[liveuser@eos-2024.09.22 ~]$ sudo dmesg -rl warn,err,crit
<4>[    0.184605]   #1  #3  #5  #7  #9 #11 #13 #15
<4>[    0.609752] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
<4>[    0.891836] ata8.00: supports DRM functions and may not be fully accessible
<4>[    0.897941] ata8.00: supports DRM functions and may not be fully accessible
<4>[    1.212699] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
<3>[    4.790259] Module pcspkr is blacklisted
<3>[    5.421113] nouveau 0000:01:00.0: unknown chipset (1b3000a1)
<3>[    5.964893] Module nvidia is blacklisted
<3>[    6.021828] Module nvidia is blacklisted
<4>[    6.235094] kauditd_printk_skb: 63 callbacks suppressed
<4>[    7.653932] nzxt_kraken3 0003:1E71:2007.0004: fw version request failed with -110
<4>[   13.124498] kauditd_printk_skb: 8 callbacks suppressed
<4>[   18.381260] kauditd_printk_skb: 49 callbacks suppressed
<3>[   31.947956] Module nvidia is blacklisted
<3>[   32.001070] Module nvidia is blacklisted
<3>[   32.062578] Module nvidia is blacklisted
<3>[   32.579808] Module nvidia is blacklisted
<3>[   32.646272] Module nvidia is blacklisted
<3>[   32.940646] Module nvidia is blacklisted
<3>[   33.067412] Module nvidia is blacklisted
<3>[   33.198928] Module nvidia is blacklisted
<3>[   33.277899] Module nvidia is blacklisted
<4>[   34.687535] block nvme0n1: No UUID available providing old NGUID
<3>[   35.453615] Module nvidia is blacklisted
<3>[   35.515749] Module nvidia is blacklisted
<3>[   35.593384] Module nvidia is blacklisted
<3>[   35.996284] Module nvidia is blacklisted
<4>[   36.078829] warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
<3>[   36.091521] Module nvidia is blacklisted
<3>[   36.673107] Module nvidia is blacklisted
<3>[   36.731494] Module nvidia is blacklisted
<4>[   37.024609] kauditd_printk_skb: 2 callbacks suppressed
[liveuser@eos-2024.09.22 ~]$


[liveuser@eos-2024.09.22 ~]$ sudo lspci  -v -s  $(lspci | grep ' VGA ' | cut -d" " -f 1)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 2c02 (rev a1) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Device 89e0
        Flags: fast devsel, IRQ 16
        Memory at 74000000 (32-bit, non-prefetchable) [size=64M]
        Memory at 4000000000 (64-bit, prefetchable) [size=16G]
        Memory at 4400000000 (64-bit, prefetchable) [size=32M]
        I/O ports at 4000 [size=128]
        Expansion ROM at 78000000 [disabled] [size=512K]
        Capabilities: [40] Power Management version 3
        Capabilities: [48] MSI: Enable- Count=1/16 Maskable+ 64bit+
        Capabilities: [60] Express Legacy Endpoint, IntMsgNum 0
        Capabilities: [9c] Vendor Specific Information: Len=14 <?>
        Capabilities: [b0] MSI-X: Enable- Count=9 Masked-
        Capabilities: [100] Secondary PCI Express
        Capabilities: [12c] Latency Tolerance Reporting
        Capabilities: [134] Physical Resizable BAR
        Capabilities: [140] Virtual Resizable BAR
        Capabilities: [14c] Data Link Feature <?>
        Capabilities: [158] Physical Layer 16.0 GT/s <?>
        Capabilities: [188] Physical Layer 32.0 GT/s <?>
        Capabilities: [1b8] Advanced Error Reporting
        Capabilities: [200] Lane Margining at the Receiver
        Capabilities: [248] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [250] Single Root I/O Virtualization (SR-IOV)
        Capabilities: [290] L1 PM Substates
        Capabilities: [2a4] Vendor Specific Information: ID=0001 Rev=1 Len=014 <?>
        Capabilities: [2bc] Power Budgeting <?>
        Capabilities: [2f4] Device Serial Number 3c-bd-db-e1-bc-2d-b0-48
        Kernel modules: nouveau, nvidia_drm, nvidia

[liveuser@eos-2024.09.22 ~]$
6

Is there a way for me to choose to drop to a terminal boot and run the information commands from my own install instead of the liveboot disk?

This way I can probably get pertinent boot-logs etc,etc.

7

Hi Rabcor-ty for responding.

I am using the latest NVIDIA driver, my old card is a Nvidia 3070ti

I did the windows install first which of course was trivial.
I didn’t even remove any drivers.
I simply took out old card, popped in new card and windows booted and used the existing driver and all good. Played games literally all night on the new card.

When I tried to boot into Linux I just assumed the new card would be use the existing NVIDIA driver on the system which is exactly the same for the 3070ti-the most recent driver.

8

https://discovery.endeavouros.com/system-rescue/how-to-boot-without-a-graphical-environment/2021/03/

1 Like
9

I suggest you boot into the liveusb and from there chroot into your installation if you want to access it’s terminal. You could from there disable the automatic startup of your gui (e.g. your display/login manager, or your desktop environment however it’s set up on your pc).

Which would then allow you to boot the pc to a tty and from there you could experiment with trying to open an X session or wayland compositor and see what causes the freeze.

10

Might be a bit then. I need to go read about chroot. I’ve done it once a LONG time ago. Can’t remember anything about it.

11

Well now. I probably should have read this before going through the trouble of creating an up-to-date Endeavour live boot. However, since I AM in the live boot. I’d like to at least try to get something from here as it makes rebooting to post onto the forum a non-issue.

1 Like
12

Gotta go out for about an hour or so. Wife is going out with the girls tonight.

13

Maybe because of this?

<3>[   31.947956] Module nvidia is blacklisted
<3>[   32.001070] Module nvidia is blacklisted
<3>[   32.062578] Module nvidia is blacklisted
<3>[   32.579808] Module nvidia is blacklisted
<3>[   32.646272] Module nvidia is blacklisted
<3>[   32.940646] Module nvidia is blacklisted
<3>[   33.067412] Module nvidia is blacklisted
<3>[   33.198928] Module nvidia is blacklisted

Edit: It’s using nouveau and has blacklisted nvidia? :thinking:

14

Yes-that’s the live-user and it is doing just that.

When trying to boot into my installed Endeavour it just fails at loading graphic profile.

I’ve just did arch-chroot into my local istall and am starting to gether some info.

Took me a bit of reading and I ahd to drive my son to a PC store as his Audi is giving an error about oil levels-even though the levels are fine.

Audi is trash-not worth the money you pay for them. I had a mechanic tell me if you buy one it’s a 3-5 year car-after that the troubles ALWAYS start.

I currently prefer Mazda’s but that’s just me. Anyhoo…yah a bit off topic.

I’ll post some info soon’ish.

15

Okay … I see. :wink:

16 
[liveuser@eos-2025.02.08 ~]$ sudo arch-chroot /run/media/liveuser/endeavouros
[root@EndeavourOS /]# sudo lspci
00:00.0 Host bridge: Intel Corporation Device a700 (rev 01)
00:01.0 PCI bridge: Intel Corporation Raptor Lake PCI Express 5.0 Graphics Port (PEG010) (rev 01)
00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 01)
00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 Gb/s) XHCI Host Controller (rev 11)
00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #0 (rev 11)
00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 (rev 11)
00:17.0 SATA controller: Intel Corporation Raptor Lake SATA AHCI Controller (rev 11)
00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #21 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Raptor Point-S PCH - PCI Express Root Port 3 (rev 11)
00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 (rev 11)
00:1d.4 PCI bridge: Intel Corporation Device 7a34 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 11)
00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio Controller (rev 11)
00:1f.4 SMBus: Intel Corporation Raptor Lake-S PCH SMBus Controller (rev 11)
00:1f.5 Serial bus controller: Intel Corporation Raptor Lake SPI (flash) Controller (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation GB203 [GeForce RTX 5080] (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 22e9 (rev a1)
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
05:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN770 / PC SN740 256GB / PC SN560 (DRAM-less) NVMe SSD (rev 01)
06:00.0 Non-Volatile memory controller: Intel Corporation SSD 660P Series (rev 03)
[root@EndeavourOS /]#

hhhmmmmm
perhaps you were exactly correct Rick.
I assumed it was the live user as it as using the nouveau driver and NVIDIA was blacklist
but below comes from a chroot environment:

root@EndeavourOS /]# sudo dmesg -rl warn,err,crit
<4>[    0.055504] Booted with the nomodeset parameter. Only the system framebuffer will be available
<4>[    0.181480]   #1  #3  #5  #7  #9 #11 #13 #15
<4>[    0.611851] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
<4>[    0.878743] ata8.00: Model 'Samsung SSD 870 EVO 1TB', rev 'SVT02B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati
<4>[    0.878948] ata8.00: supports DRM functions and may not be fully accessible
<4>[    0.884491] ata8.00: supports DRM functions and may not be fully accessible
<4>[    1.235036] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
<3>[    9.236469] Module nvidia is blacklisted
<3>[    9.300480] Module nvidia is blacklisted
<4>[   15.846815] kauditd_printk_skb: 86 callbacks suppressed
<4>[   21.892102] kauditd_printk_skb: 91 callbacks suppressed
<4>[   35.233364] nvme nvme0: using unchecked data buffer
<4>[   35.265717] block nvme0n1: No UUID available providing old NGUID
<4>[   38.775498] warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
<4>[   42.027725] kauditd_printk_skb: 3 callbacks suppressed
<4>[ 6072.158634] ntfs3(sdc3): ino=197f7, Correct links count -> 2.
<4>[ 6072.160836] ntfs3(sdc3): ino=197db, Correct links count -> 2.
<4>[ 6072.291436] ntfs3(sdc3): ino=3f, Correct links count -> 2.
<4>[ 6072.292817] ntfs3(sdc3): ino=1ad1f, Correct links count -> 2.
<4>[ 6072.345572] ntfs3(sdc3): ino=4b20c, Correct links count -> 2.
<4>[ 6072.362464] ntfs3(sdc3): ino=4b2de, Correct links count -> 2.
<4>[ 6072.364037] ntfs3(sdc3): ino=4b2df, Correct links count -> 2.
<4>[ 6072.486000] ntfs3(sdc3): ino=4b161, Correct links count -> 2.
<4>[ 6072.486314] ntfs3(sdc3): ino=4b169, Correct links count -> 2.
<4>[ 6072.486450] ntfs3(sdc3): ino=4b1c0, Correct links count -> 2.
[root@EndeavourOS /]#

I am unsure if the next is helpful or just a reproduciton of some info already posted above.
The website suggested it so here it.

root@EndeavourOS /]# sudo lspci -v -s $(lspci | grep ' VGA ' | cut -d" " -f 1)
01:00.0 VGA compatible controller: NVIDIA Corporation GB203 [GeForce RTX 5080] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Device 89e0
        Flags: fast devsel, IRQ 255
        Memory at 74000000 (32-bit, non-prefetchable) [size=64M]
        Memory at 4000000000 (64-bit, prefetchable) [size=16G]
        Memory at 4400000000 (64-bit, prefetchable) [size=32M]
        I/O ports at 4000 [size=128]
        Expansion ROM at 78000000 [disabled] [size=512K]
        Capabilities: [40] Power Management version 3
        Capabilities: [48] MSI: Enable- Count=1/16 Maskable+ 64bit+
        Capabilities: [60] Express Legacy Endpoint, IntMsgNum 0
        Capabilities: [9c] Vendor Specific Information: Len=14 <?>
        Capabilities: [b0] MSI-X: Enable- Count=9 Masked-
        Capabilities: [100] Secondary PCI Express
        Capabilities: [12c] Latency Tolerance Reporting
        Capabilities: [134] Physical Resizable BAR
        Capabilities: [140] Virtual Resizable BAR
        Capabilities: [14c] Data Link Feature <?>
        Capabilities: [158] Physical Layer 16.0 GT/s <?>
        Capabilities: [188] Physical Layer 32.0 GT/s <?>
        Capabilities: [1b8] Advanced Error Reporting
        Capabilities: [200] Lane Margining at the Receiver
        Capabilities: [248] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [250] Single Root I/O Virtualization (SR-IOV)
        Capabilities: [290] L1 PM Substates
        Capabilities: [2a4] Vendor Specific Information: ID=0001 Rev=1 Len=014 <?>
        Capabilities: [2bc] Power Budgeting <?>
        Capabilities: [2f4] Device Serial Number 3c-bd-db-e1-bc-2d-b0-48
lspci: Unable to load libkmod resources: error -2

[root@EndeavourOS /]#
17

Is this just a case of regenerating initramfs?

and if so can I do this from arch-chroot or should I amend boot to the single user as suggest somewhere above and do it from there?

IF this is the case can someone please post the proper initramfs regeneration command. (dam my memory)

I think it is this but who know:

update-initramfs -c -k $(uname -r)

18

I’m not sure but in my way of thinking the hardware is different. It most likely has a different ID number. So what i would do is in chroot revert to nouveau and see if it boots on the kernel module. Then install the nvidia drivers again.

To revert to nouveau

nvidia-inst -n

Reboot and see.

Then reinstall the latest nvidia drivers if it boots on nouveau.

nvidia-inst

19

root@EndeavourOS /]# nvidia-inst -n
2025-03-08 18:38:04: Error: This program must be started as a non-root user.

Is where I should boot normally to my Linux local install, highlight the default grub entry, hit enter and add (space) 1 to the boot entry and then run this: nvidia-inst -n

Actually that won’t work either if I need to run it as normal user - correct?

Could I maybe change the run-level to 3 and boot to term as a normal user? Would that work?

Here is some fresh info about graphics card: I know redundant, but, it might save someone from scrolling up:

root@EndeavourOS /]# lspci -nnk | grep NVIDIA
lspci: Unable to load libkmod resources: error -2
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GB203 [GeForce RTX 5080] [10de:2c02] (rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22e9] (rev a1)
        Subsystem: NVIDIA Corporation Device [10de:0000]
[root@EndeavourOS /]#
20

OK Back into Windows 11.

What I did:

change run-level to 3
reboot into run level 3
ran nvidia-inst -n
I watch it swap out to the nouveau driver

after completion message and prompt to reboot I did that and same issue - gets hung up on loading graphics profile.

I then thought, why not just install the NVIDIA drier again but from run level 3

so back into run level three: I received dependency errors that I do not understand so posting a pic as below:

dependacy issue

IS this due to the fact that NVIDIA removed 32 bit shit from the drivers for the 5000 series?
Cause this card is going right the F&*K back if it is and I’ll grab me a 9080XT instead.
Apologies for language but NVIDIA has been miffing me off as much as MS is lately.

I mean it is only supposed to affect 32bit games but who knows with these people.