Absolute nightmare after install newest EndeavourOS

It’s the strangest thing. Sometimes, it works. Sometimes it does not. Sometimes the desktop environment wont load, sometimes it wont even boot. The oddest part about the whole thing, Is that it runs 100% perfectly on the Live USB!
I really don’t know where to begin with what is wrong, but the first and foremost pressing issue is PCIe error that spams my console. I believe this is causing issues with the install, crashing my DE before I can setup my GPU, and more fun awesome stuff. I will include the issue and any other things that may help, but I’ll have to do it on a iPhone because I’m having that much trouble, so I apologize in advance. Anyways, here’s problem number one


As you can see, the error is “corrected”, yet still spams my console. [dmesg] is absolutely flooded to a point where I cannot tell if there are any other issues.
I didn’t want to have to bug anyone with these issues but I’ve been exhausting options rapidly and I don’t know what to do. I cannot overstate how much any kind of help is appreciated.

Try disabling power saving features related to PCIE in your BIOS/UEFI, e.g. PCIE Active State Power Management (PCIE ASPM) and check if the problem persists.

3 Likes

No changes.

Can you post your full system specs?

1 Like

Please be a bit more specific. What do you mean sometimes it works sometimes it does not?
Is this a dual boot system?
Did you add any new hardware in the last couple of months?

as @HBR ask can you show us the results of
inxi -Fxxc0z --no-host

1 Like

Try adding the following kernel parameter to the command line.

pci=noaer

I’m assuming you are using the default systemd-boot?

https://discovery.endeavouros.com/installation/systemd-boot/2022/12/

1 Like

kernel…

LiveISO has older kernel… go install LTS kernel could resolve the issue…
Or loose connection…on a pcie device / cable …

1 Like

This is not a dual boot system. This is a total disk overwrite. Sometimes, The install works without issues, and sometimes, it doesn’t even boot into the kernel select when I power my computer on. I have added some different specs than the computer previously had (New RAM (tested), a SSD, and latest was a new GPU. The problem is, this was all long before I attempted to switch to Endeavour.
I have a paste of the command, but I don’t know how to format it, so forgive the big wall of text!!

specs
System:
  Kernel: 6.7.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 Console: pty pts/1 DM: SDDM
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop System: Dell product: XPS 8900 v: N/A serial: <filter> Chassis: type: 3
    serial: <filter>
  Mobo: Dell model: 0XJ8C4 v: A00 serial: <filter> UEFI: Dell v: 2.7.1 date: 11/22/2019
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 serial: <filter>
    charge: 55% (should be ignored) status: discharging
CPU:
  Info: quad core model: Intel Core i7-6700 bits: 64 type: MT MCP arch: Skylake-S rev: 3 cache:
    L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 1949 high: 3899 min/max: 800/4000 cores: 1: 3899 2: 3801 3: 800 4: 3899
    5: 800 6: 800 7: 800 8: 800 bogomips: 54417
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: ASUSTeK driver: nvidia v: 545.29.06
    arch: Pascal pcie: speed: 2.5 GT/s lanes: 16 ports: active: none off: HDMI-A-1,HDMI-A-2
    empty: DP-1,DP-2,DVI-D-1 bus-ID: 01:00.0 chip-ID: 10de:1c03
  Display: server: X.org v: 1.21.1.11 compositor: kwin_x11 driver: X: loaded: nvidia
    unloaded: modesetting alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch tty: 110x28
  Monitor-1: HDMI-A-1 model: Samsung S22E310 res: 1920x1080 dpi: 102 diag: 547mm (21.5")
  Monitor-2: HDMI-A-2 model: Acer X203W res: 1680x1050 dpi: 99 diag: 508mm (20")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia inactive: wayland,x11,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 23.3.3-arch1.1 note: console (EGL sourced)
    renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2, llvmpipe (LLVM 16.0.6 256 bits)
  API: Vulkan v: 1.3.274 surfaces: N/A device: 0 type: discrete-gpu driver: nvidia
    device-ID: 10de:1c03
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170
  Device-2: NVIDIA GP106 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    pcie: speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f1
  API: ALSA v: k6.7.1-arch1-1 status: kernel-api
  Server-1: PipeWire v: 1.0.1 status: n/a (root, process) with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Device-1: Intel Ethernet I219-V vendor: Dell driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
    chip-ID: 8086:15b8
  IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 02:00.0 chip-ID: 10ec:b723
  IF: wlan0 state: down mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 2.1 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-11:6 chip-ID: 0bda:b739
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0 lmp-v: 6
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 bus-ID: 00:17.0
    chip-ID: 8086:2822
Drives:
  Local Storage: total: 1.85 TiB used: 0 KiB (0.0%)
  ID-1: /dev/sda vendor: Seagate model: WDC WDS200T2B0A-00SM50 size: 1.82 TiB speed: 6.0 Gb/s
    serial: <filter>
  ID-2: /dev/sdb vendor: SanDisk model: Cruzer Blade size: 14.91 GiB type: USB rev: 2.0
    spd: 480 Mb/s lanes: 1 serial: <filter>
  ID-3: /dev/sdc vendor: Lexar model: USB Flash Drive size: 14.93 GiB type: USB rev: 2.0
    spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 10 GiB used: 102.3 MiB (1.0%) fs: overlay source: ERR-102
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 41.0 C pch: 48.5 C mobo: N/A
  Fan Speeds (rpm): cpu: 1201 mobo: 1002
Info:
  Processes: 271 Uptime: 5m Memory: total: 16 GiB available: 15.56 GiB used: 3.34 GiB (21.5%)
  Init: systemd v: 255 default: multi-user Compilers: gcc: 13.2.1 Packages: pm: pacman pkgs: 978
  Shell: Bash v: 5.2.26 running-in: pty pts/1 inxi: 3.3.31

I am attempting to try what ricklinux and some others across the internet have done but I’m having trouble understanding the linked webpages.
joekamprad made a good point but I would like that to be the nuclear option, as the hardware issues may still persist.

that’s not a nuclear option at all, and it’s always good to have LTS kernel to fall back to imho, you could try and install it.

The one built in did not work.

are you talking to boot process or the install process. I mean if it installs once successfully I see no need to do a reinstall.

you need to install the lts kernel yourself

pacman -S linux-lts linux-lts-headers

the lts kernel will support all but the latest hardware.

1 Like

Hindsight is 20/20. Too late now.
Also, what will this command do on a LiveUSB?

I’m no expert but I think you can’t really do that cause the change of kernel takes effect after you reboot. And of course when you reboot the live usb all the changes get canceled.
So I think you’d have to create your own ISO with the kernel you want on it if you’d really want to use the live usb with another kernel.
The real question is would you really want/need to do that…

you need to chroot into the system first sorry for the confusion.

1 Like

:point_up:
Ah yes I was confused too :grimacing: if you want to install another kernel on your existing bare metal system FROM the live usb you need to chroot into your system.

Hindsight is 20/20. Too late now.

Also, I hate to do this to you guys, but I really am struggling with this. I don’t know how to use chroot or get into the systemd boot parameters. I’ve tried for hours to find something but I can’t.

There is a newer Bios update for this system. I think it’s version 2.9.1 if i have the right model but can’t confirm without serial number. It may help or may not.

1 Like

i do not even see anye esult of at least one suggestion made… you are struggeling on find the suggestion you want to do?

And if system is working some boots take one of this boot and install LTS kernel reboot and choose the LTS kernel on boot menu to be used. (should be the default).
LTS kernel can be used side by side with the default one with no issue…

2 Likes

I don’t know how to do it dude.
Currently trying to figure out how to chroot and now the BIOS update

1 Like

https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/

arch-chroot

1 Like