As i said the driver is out on the Nvidia site but it will have to go through testing on Arch first.
Edit: I hope this all makes sense to you?
@cameron
Can you also run the log tool from the Welcome app or EndeavourOS log tool and give us the install logs.
@cameron
Hope this isn’t causing you more issues.
Sure, but it will have to be tomorrow morning, as I’m currently going to be busy until late tonight.
It isn’t at the moment. Fingers crossed though.
If your ISO is already working, you can skip this post. But if not, please continue! 
Found a bug near the end of the log. It is trying to install nvidia related packages but fails:
"==> installing if missing: nvidia-installer-dkms nvidia-inst nvidia-hook nvidia-dkms\n"
Package nvidia-installer-dkms has been removed, so it fails to install also other nvidia packages.
To work around this, you can modify file
/etc/calamares/scripts/chrooted_cleaner_script.sh
by removing this one package from the list where they are installed:
_install_needed_packages nvidia-installer-dkms nvidia-inst nvidia-hook nvidia-dkms
This needs to be done before starting the install. After modifying the file, restart eos-welcome and install again.
Note that this package removal is automatically done when using the latest official EndeavourOS ISO. Unfortunately is not supported with ISOs built otherwise.
That was my doing as i removed nvidia-dkms and replaced it with nvidia in the packages list. I wasn’t sure what i was doing but when i tried running an test install it said nvidia-dkms was missing just like the packages ipw2100 and ipw2200 so i changed it. The main thing I was trying to do was to get the nvidia 520.xx series drivers booting off the live ISO. Im just unsure how it all works so i was winging it.
Edit: EndeavourOS did install but still booted to black screen so the OP switched to the onboard amdgpu drivers which works. I was trying to get the OP to install the 525.xx beta drivers which are in the AUR. On the nvidia site they are now released but obviously not in the Arch repo yet as they probably have to go through testing. I only see another newer 520.xx series driver in testing in the Arch testing repo.
Edit2: I suggested the OP try the nvidia-beta-dkms version
Edit3: Still not sure if it’s a driver issue or some other hardware issue with this RTX 4090 card?
No worries mate!
The problem is caused by how the hotfixes work.
But I just modified the hotfixes, and if I didn’t forget anything, hotfixes remove those problematic packages for all ISOs now. 
2 Likes
My problem is i don’t understand exactly how all this stuff is being done. @joekamprad has helped me with some of it but i still lack knowledge and understanding.
The installer is rather complicated. We are constantly making it more modular in structure and thus less complicated. There’s lots of work involved, but it is getting better all the time.
1 Like
Should I still use the AUR nvidiabeta-dkms ppackage and install it?
Edit: Also, do I install it with the Nvidia GPU deactivated or activated?
I would try installing it while booted into installed system.
yay -S nvidia-beta-dkms
Then after it installs i would reboot still using the amdgpu and see. Then if it doesn’t mess up the boot then shut down and switch over to the nvidia graphics card and boot on it. You may have to set the UEFI bios or not. If it’s set on Auto for the GPU it should be okay because you will be hooked to the nvidia card anyway and disconnected from the internal graphics on the processor which only outputs from the motherboard connections. Or you could set UEFI Bios to the dedicated gpu. I’m not sure this is going to work or not because i don’t know if it’s a driver issue or some other hardware issue with the card. It’s up to you if you want to try this or not?
My question is how is it working on the amdgpu anyway?
It’s working fine with only the AMD GPU, likely because it’s an open-source driver for AMD. Of course, I don’t dare run Steam on it, even though I want to play Spider Man Miles Morales on it; I’m waiting to see if the issue is fixed.
I’ll try your suggestions tomorrow. I’ll be sure to keep you up to date.
I’m not sure this is going to work or not because i don’t know if it’s a driver issue or some other hardware issue with the card.
I think it’s been pretty stable with Windows 11; the only BSOD was due to a flashdrive screwing up a Zoom call after booting from sleep; after 10 minutes, and about 5 minutes into the Zoom call, the BSOD occurred.
Looking at the MEMORY.DMP dump file, it was caused by a Windows kernel module dealing with SCSI drives, like my flashdrive that was plugged in at the time of “death”.
To sum it up, I think it’s going to be fine, but I’m going to wait until tomorrow to try the fix as then I:
- Won’t be tired.
- Will have more time.
Or you can just wait until these drivers are actually out on Arch to try them.
Edit: They have to go through the testing repo first.
Considering the AMD iGPU really only is good for displaying an output, I do need these relatively soon. I’m going to try the beta drivers.
1 Like
And… It works! Unlike Kubuntu which was janky even though it was (somewhat) working, on EndeavourOS with the beta drivers, it’s so smooth on X11! (Haven’t tried Wayland yet.) Thank you so much @ricklinux & @manuel for your help!
1 Like
Do you still dare try the latest official driver by Arch?
Can you post this output?
inxi -Ga
Edit: This driver will be on Arch as soon as it gets through testing repo.
Edit:2
@manuel because this is currently an AUR package how does the OP install the regular 525.xx version once available?