I tried both the regular and Nvidia boot options and got similar results, but will need to revisit later when I have more time and energy
I don’t recall having issues with the previous Mercury Neo ISO 
1 Like
If you have the time it would help to see the boot journal from booting the ISO.
By any chance does the device have hybrid graphics?
journalctl -k -b -0 | eos-sendlog and give me the short URL it creates for the pastebin.
My desktop has a GTX1060 also. It would be nice if you posted your total hardware output so we can see what other hardware you have. I will try the New ISO on my system and report what i find.
2 Likes
Could be also something related to how ISO is created on the USB.
https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/
if you can boot and share boot journal i would love to read a lot of logs all the time 
Boot Log:
Edit: This is booting on the Nvidia cards grub menu not the default.
Edit:
[liveuser@eos-2025.11.24 ~]$ inxi -Ga
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: none empty: HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0
chip-ID: 8086:3e92 class-ID: 0300
Device-2: NVIDIA GP104 [GeForce GTX 1060 6GB] vendor: ASUSTeK
driver: nvidia v: 580.105.08 alternate: nouveau,nvidia_drm
non-free: 550-580.xx+ status: current (as of 2025-08; EOL~2026-12-xx)
arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 2
speed: 5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s lanes: 16 ports:
active: none off: HDMI-A-3 empty: DP-1, DP-2, DVI-D-1, HDMI-A-4
bus-ID: 03:00.0 chip-ID: 10de:1b83 class-ID: 0300
Display: x11 server: X.Org v: 21.1.20 with: Xwayland v: 24.1.9
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia
alternate: fbdev,intel,nouveau,nv,vesa dri: iris
gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 92 s-size: 530x301mm (20.87x11.85")
s-diag: 610mm (24")
Monitor-1: HDMI-A-3 mapped: HDMI-0 note: disabled model: Samsung S24D330
serial: 1515869238 built: 2018 res: mode: 1920x1080 hz: 60 scale: 100% (1)
dpi: 92 gamma: 1.2 size: 531x299mm (20.91x11.77") diag: 609mm (24")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 25.2.7-arch1.1
glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 21.1.5 256 bits)
device-ID: ffffffff:ffffffff memory: 30.47 GiB unified: yes
API: Vulkan v: 1.4.328 layers: 2 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 1060 6GB driver: nvidia v: 580.105.08 device-ID: 10de:1b83
surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
I used this method to create the live USB
sudo dd bs=4M if=/path/to/endeavouros-x86_64.iso of=/dev/sdX conv=fsync oflag=direct status=progress
for the first time. I’ve only used Rufus in Win 10 previously
I used the default first option to boot the ISO from the USB thumbdrive
I wonder if it’s the new Nvidia auto select causing an issue?
I notice this?
Sorry, could you please provide the command that I should type into Konsole?
thats what i already mentioned on testing.. in case you have 2 GPUs it is using software rendering..
1 Like
Here is booting on the default grub menu.
[liveuser@eos-2025.11.24 ~]$ inxi -Ga
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1060 6GB] vendor: ASUSTeK
driver: nouveau v: kernel non-free: 550-580.xx+ status: current (as of
2025-08; EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3
speed: 8 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2,
DVI-D-1, HDMI-A-2 bus-ID: 01:00.0 chip-ID: 10de:1b83 class-ID: 0300
temp: 51.0 C
Display: x11 server: X.Org v: 21.1.20 with: Xwayland v: 24.1.9
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,nouveau,nv,vesa dri: nouveau gpu: nouveau display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Samsung S24D330
serial: 1515869238 built: 2018 res: mode: 1920x1080 hz: 60 scale: 100% (1)
dpi: 92 gamma: 1.2 size: 531x299mm (20.91x11.77") diag: 609mm (24")
ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
drv: nouveau inactive: wayland
API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 25.2.7-arch1.1 glx-v: 1.4
direct-render: yes renderer: NV134 device-ID: 10de:1b83 memory: 5.85 GiB
unified: no
API: Vulkan Message: No Vulkan data available.
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console, kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Edit: This looks even worse using preformatted text.
Edit: Now is okay!
I do have Intel CPU with graphics and dedicated Nvidia gpu.
please use codetags for code its very hard to read as format gets screwed
Code tags don’t seem to be working.
1 Like
inxi -Fxxc0z | eos-sendlog
is this from default boot or the nvidia boot option?
something changed on the forum software too i never saw these strange formatting:
in case you change format it gets screwed even more now
Yes…. something changed and I don’t know how to set it?
Edit: Before I always used three ~~~ tilde or three ``` back ticks?
Edit: Pre-formatted text also doesn’t work.
