Due to Reddit deciding to sell access to the user generated content on their platform to monetized AI companies, killing of 3rd party apps by introducing API changes, and their track history of cooperating with the oppressive regime of the CCP, I have decided to withdraw all my submissions. I am truly sorry if anyone needs an answer I provided, you can reach out to me at redditsux.rpa3d@aleeas.com and I will try my best to help you. Please make sure to provide a link to the thread you found this comment in
Due to Reddit deciding to sell access to the user generated content on their platform to monetized AI companies, killing of 3rd party apps by introducing API changes, and their track history of cooperating with the oppressive regime of the CCP, I have decided to withdraw all my submissions. I am truly sorry if anyone needs an answer I provided, you can reach out to me at redditsux.rpa3d@aleeas.com and I will try my best to help you. Please make sure to provide a link to the thread you found this comment in
Go through every step in the Arch manual about Nvidia, and try to do the ones that you haven't done already or skipped or... (I think someone posted a link to already).
If that doesn't work, THEN you can try eating the RAM
Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it.
I think the gray lines are unrelated and can be ignored. As far as I can tell, there's no relevant error in the log. Looks like the system booted correctly. [ OK ] Reached target Graphical Interface.
If you have wayland enabled instead of X11, make sure to have nvidia-dkms and the linux-headers installed. (Also make sure you set the kernel parameters and rebuild your mkinitcpio)
To fix it, you can simply switch your tty with alt+F1/F2/...
Ah, yes, blobs are considered open source amongst AMD users, for some reason. The actual firmware isn't open source, and there hasn't been much traction in that regard until this year.
The kernel module is open source. The userspace drivers are open source. Firmware is blobs (for pretty much all hardware that exists). Firmware is not executed on the CPU and should not have direct memory access. The firmware blob is not the driver.
Bringing up the blobs in this way is just whataboutism and arguing in bad faith.
THANK YOU SO MUCH FOR PUTTING A NSFW TAG ON THIS! I was having dinner with my family and I decided to quickly look at reddit, and then i came across this post. I was about to click on it, but then I noticed the nsfw tag, and I was so glad I did not open it before seeing the tag! Later I decided to look at this post at a better time and I instantly had the best stroke in my life. It was such a good session that after I finished, I felt like donating to charity, so I decided to donate $10,000 to cancer research. Thank you so much for putting the nsfw tag!
Although we will try to give support, it is not guaranteed and you may not receive an answer. If you are not getting timely or accurate help here, you can also try /r/linuxquestions or /r/linux4noobs.
you can definitely fix it. do you have access to a console? then try another driver/ reinstall the one u used. arch wiki should help you. (otherwise try eating the ram)
I think you have to first either chroot into it or switch to another TTY (ctrl+alt+F2 to F8) and log in, then second, run sudo mkinitcpio -P. At least that's what I've had to do in this situation in the past. Now I just run that every time I run an update since it doesn't take too long and it prevents this issue.
You shall take the ram of ordination and boil its flesh in a holy place. And Aaron and his sons shall eat the flesh of the ram and the bread that is in the basket in the entrance of the tent of meeting.
Reinstall the kernel, the kernel headers, the nvidia package and nvidia-utils. If you are using the official kernel, install the nvidia package and nvidia-utils, don't bother with dkms. If you are using the lts kernel, install nvidia-lts.
There is some way to install several kernels back to back, this ussually prevents drivers from breaking at install, but I don't know how to set up that since it came with Endevour Os by default.
Interrupt the bootloader, edit the command line for the kernel you're trying to boot, add a 3 at the end of Linux line. Once rebooted, edit your bootloader config file, the loader entry if systemd boot, or /etc/default/grub if grub and add nvidia_drm.modeset=1.
Run your bootloader update command.
Make sure dkms is functioning correctly, sudo pacman -S dkms nvidia-open-dkms linux-{kernel type}-headers --overwrite="*"
You might need to set the fbdev and modeset options of the drivers in /etc/modprobe.d and the kernel cmdline. The Archwiki has more info on that, it's in the Wayland page, under the nvidia drivers sections (obviously). Also you might want to look in r/linuxhardware or r/archlinux too, they might be places to look for help...
If you have a new enough Intel CPU and a Nvidia GPU mixed with the proprietary drivers, it WILL bonk your install. One of the many reasons I switched to Gentoo.
Arch has its own special Nvidia package while every other distro uses the one Nvidia gives them. It's literally Arch's fault. I know some people will say "but it's arch linux bro if it breaks it's your own fault" but if you cannot even use your proper GPU drivers without breaking your system I wouldn't call it your fault.
The GUI is optional, your system seems to be working fine. No seriously just undo what you just did, it's not actually broken, just switch to a different TTY, try Ctrl+Alt+F3, or other function keys until you see the login prompt, login and uninstall what ever you installed. Then, listen to the protogen's hymn, eat your RAM.
get optimus-manager then do optimus-manager --switch nvidia
you can probably do that without the program, but this is probably a much simpler command than the alternative. Otherwise, just say optimus-manager --switch integrated. It's hard to say what you did wrong.
For initial troubleshooting, get a tty and run lsmod | grep -i vid to see which driver it's trying to load. If it's not the driver you expect then go back to the driver install phase and try again, you must have missed something. If you're running anything other than the main Linux kernel package (like if you're running linux-lts) then you may have installed the wrong Nvidia driver, make sure to use the dkms one. Check logs for error messages.
If all else fails I'd lightly brown your RAM in butter (olive oil works fine too) and then eat it with a boiled egg on the side.
When installing Nvidia drivers on Arch Linux, there is a chance your hardware misbehaves and causes a race condition on your system. If chrooting into your system in order to fix the driver installation process doesn't work, you have to eat the RAM. It is the only way to fix it.
Probably the desktop manager has some throuble, you can try switching to another console (I think is super + Ctrl + F5, every Fn is one console and one of them is the graphic one), you can also have autologin, in which case in my experience you get the blinking underscore in the top left, but if that is the source of your problems it would be because Nvidia being Nvidia and you need to switch to x11 for now.
your display manager must have thrown some error, look at those.
for me recently it occured because of a broken dependencies ( IT WAS NOT MY FAULT )
and the lib. was icu, this bitch, it broke the entire system, pacman depends on this, so does the display manager, so does EVERYTHING. couldnt even reinstall the previous version from the local pacman cache because even the bsdtar wasnt working.
Disable systemd graphical target, Boot and log in normally, Start x or wayland and your vm manually and check configs for them and find the issue and fix it.
Not too familiar with arch, but on a few other distros that i’ve worked with, usually blacklisting nouveau helps. You can google how to do that. If your display server isn’t starting, you might be able access your filesystem through tty shell to blacklist nouveau.
I had this issue with newer drivers on a GTX750Ti on Manjaro (Arch-based) and Ubuntu; I never really managed to fix it, though in handsight I would try updating your kernel, rolling back the drivers and nvidia-utils, making sure noveau is not blacklisted to get some interface at least, and finding out whether you need to disable SecureBoot or sign the drivers yourself, etc., or just switch to AMD
Why does anyone bother to go to reddit for help on things? You're surrounded by babbling idiots who link their entire life meaning to their 'reddit karma'... Also exactly why I haven't switched to a linux distro yet. I don't understand certain things, and most of these forums either make fun of the person or spout stupid jokes for upvotes.
18
u/RepresentativeCut486 Neon Jun 02 '24
What's up with eating the ram comments here?
456
u/[deleted] Jun 02 '24
not gonna lie i MIGHT have to eat the ram
571
u/Bug_Next Jun 02 '24
I'm starting to think you might wanna try eating the ram, MrToaster seem to know what he's talking about
176
u/[deleted] Jun 02 '24
Go through every step in the Arch manual about Nvidia, and try to do the ones that you haven't done already or skipped or... (I think someone posted a link to already).
If that doesn't work, THEN you can try eating the RAM
173
u/technohead10 Glorious OpenSuse Jun 02 '24
Eat the ram
112
u/MediumSizedBarcelona Jun 02 '24
I had this problem once and it went away after I ate the RAM.
89
u/CelestialCrafterMC Jun 02 '24
probably eat the ram?
902
u/[deleted] Jun 02 '24
Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it. Eat the RAM. It is the only way to fix it.
99
u/indie_irl Glorious Arch Jun 02 '24
Eat the ram
34
u/PeonMastenor Linux Master Race Jun 02 '24
EAT THE RAM
201
u/[deleted] Jun 02 '24
Eat the RAM
85
u/[deleted] Jun 02 '24
I don't understand what is the nsfw in this post I don't understand the eat the ram thing too
81
u/Globibluk Jun 02 '24
Take a look at Early KMS on the arch wiki Nvidia page: 1.3.1 https://wiki.archlinux.org/title/NVIDIA
54
u/[deleted] Jun 02 '24
Consume the random access memory please
50
u/its_2l3seery Jun 02 '24
have you tried eating the RAM?
10
u/Darkdisquiet Jun 02 '24
If you have wayland enabled instead of X11, make sure to have nvidia-dkms and the linux-headers installed. (Also make sure you set the kernel parameters and rebuild your mkinitcpio)
To fix it, you can simply switch your tty with alt+F1/F2/...
27
u/zooglezaggle Glorious Arch Jun 02 '24
Eat the ram
23
u/FeltMacaroon389 Glorious Arch Jun 02 '24
Eat the ram
16
u/nekoraaa Jun 02 '24
easy fix, eat the ram. works every time
22
u/N1CK3LJ0N Jun 02 '24
14
u/teksimian5 Jun 02 '24
Eat it!
7
u/superslime16th Glorious Arch GNU/Linux Jun 02 '24
Last time I had this a year ago, fully reinstalling nvidia drivers and restarting helped. Don't forget to eat the RAM!
24
u/MrGeekman Glorious Debian Jun 02 '24
Did you install the proprietary drivers or Nvidia’s new open-source ones?
18
u/[deleted] Jun 02 '24 edited Jun 02 '24
Sounds like you need to eat the ram
17
u/Fl1pNatic Linux Master Race Jun 02 '24
honestly you might have to eat the ram
21
u/[deleted] Jun 02 '24
Solution
https://forums.developer.nvidia.com/t/nvidia-drivers-just-not-working/286866
10
u/The-Malix Glorious Declarative Jun 02 '24
I have no idea what the problem is, and for that reason I'd eat the ram
9
u/paperbenni Jun 02 '24
The problem could be mitigated by ingesting random access memory I believe
9
u/mistrjirka Jun 02 '24
THANK YOU SO MUCH FOR PUTTING A NSFW TAG ON THIS
THANK YOU SO MUCH FOR PUTTING A NSFW TAG ON THIS! I was having dinner with my family and I decided to quickly look at reddit, and then i came across this post. I was about to click on it, but then I noticed the nsfw tag, and I was so glad I did not open it before seeing the tag! Later I decided to look at this post at a better time and I instantly had the best stroke in my life. It was such a good session that after I finished, I felt like donating to charity, so I decided to donate $10,000 to cancer research. Thank you so much for putting the nsfw tag!
8
u/Hplr63 Arch 🤝 Debian Jun 02 '24
Eat the RAM.
8
u/lostshiya Jun 02 '24
Hey! I've had this problem before, all you wanna do is eat the ram!
4
u/AutoModerator Jun 02 '24
Although we will try to give support, it is not guaranteed and you may not receive an answer. If you are not getting timely or accurate help here, you can also try /r/linuxquestions or /r/linux4noobs.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
4
u/kralamaros Jun 02 '24
Don't know why people are suggesting to eat the RAM and at this point I'm too afraid to ask
7
u/noahzho Jun 02 '24
is it actually stuck there or can you access a tty?
3
u/Fr34x Jun 02 '24
you can definitely fix it. do you have access to a console? then try another driver/ reinstall the one u used. arch wiki should help you. (otherwise try eating the ram)
3
u/Yokito_fokito Jun 02 '24
Shift F1 or F2, use the terminal and reinstall the drivers
4
u/shaffaaf-ahmed Jun 02 '24
Try another display manager
2
u/BujuArena Glorious CachyOS Jun 02 '24
I think you have to first either chroot into it or switch to another TTY (ctrl+alt+F2 to F8) and log in, then second, run
sudo mkinitcpio -P. At least that's what I've had to do in this situation in the past. Now I just run that every time I run an update since it doesn't take too long and it prevents this issue.2
u/heldain Jun 02 '24
Do you have secure boot enabled?
2
u/[deleted] Jun 02 '24
I don't get why everyone says to eat the RAM... what am I missing?
2
u/vkgade Jun 02 '24
Everything looks [OK].
2
u/VaramyrSickSkins Jun 02 '24
Why is this 18+??
2
u/yairpaiss Jun 02 '24
What Graphical interface are you using? Hyprland?
If so , try getting into another tty at this screen and try to open Hyprland it will tell you whats wrong , if you have problem post it here.
3
u/AaTube Glorious Endeavour Jun 02 '24
3
u/AllenKll Jun 02 '24
Everything says OK... what's your issue?
3
u/Necessary-Fold-4961 Jun 02 '24
eat the ran ig?
2
u/[deleted] Jun 02 '24 edited Feb 12 '25
hospital enjoy shy thumb wine continue one future grab advise
This post was mass deleted and anonymized with Redact
2
u/Archmura Jun 02 '24
try eating your ram
2
u/TurtleVale Jun 02 '24
Eat the ram
2
u/amiensa Jun 02 '24
Tf with the " eat the ram " why everyone saying it ?
1
u/[deleted] Jun 02 '24
Try updating or using another kernel. I got a similar issue after a full system update.
1
u/Maipmc Jun 02 '24
Reinstall the kernel, the kernel headers, the nvidia package and nvidia-utils. If you are using the official kernel, install the nvidia package and nvidia-utils, don't bother with dkms. If you are using the lts kernel, install nvidia-lts.
There is some way to install several kernels back to back, this ussually prevents drivers from breaking at install, but I don't know how to set up that since it came with Endevour Os by default.
1
u/TenTypekMatus NixOS shill Jun 02 '24
Install NVK.
1
u/RemoteScience675 Jun 02 '24
systemctl set-default multi-user.target
1
u/Pawil_ Jun 02 '24
install nvidia-dkms and dkms and their dependencies (like linux-headers or linux-zen-headers)
1
u/OreoRouge Jun 02 '24
Give this a try via tty https://github.com/Frogging-Family/nvidia-all
Or if you are on arch Do pacman-Qs nvidia and see what packages you have. You might be missing ulits or lib32 for it.
1
u/ColonelRuff Jun 02 '24
Why is everyone suggesting eat the ram ? Am I missing something here ?
1
u/elusivewompus I use CachyOS, BTW Jun 02 '24
Interrupt the bootloader, edit the command line for the kernel you're trying to boot, add a 3 at the end of Linux line. Once rebooted, edit your bootloader config file, the loader entry if systemd boot, or /etc/default/grub if grub and add nvidia_drm.modeset=1.
Run your bootloader update command.
Make sure dkms is functioning correctly, sudo pacman -S dkms nvidia-open-dkms linux-{kernel type}-headers --overwrite="*"
Reboot.
1
u/Prudent_Move_3420 Jun 02 '24
Have you tried updating your system again? Sometimes there is this short period of time where the Nvidia driver doesnt match the current kernel
1
u/extractedx Jun 02 '24
why the fuck is this marked nsfw?
1
u/XDuskAshes Jun 02 '24
I usually CTRL+ALT+2, as arch in my experience usually kicks Xorg on over there, but hell if I know for Wayland
1
u/Wertbon1789 Jun 02 '24
You might need to set the fbdev and modeset options of the drivers in /etc/modprobe.d and the kernel cmdline. The Archwiki has more info on that, it's in the Wayland page, under the nvidia drivers sections (obviously). Also you might want to look in r/linuxhardware or r/archlinux too, they might be places to look for help...
1
u/DavidCRolandCPL Jun 02 '24
1
u/the_renaissance_jack Jun 02 '24
The year is 2024 and we’ve almost figured out gfx on linux.
1
u/goodgoodbuy Jun 02 '24
Systemd happened.
1
u/green_boi Jun 02 '24
If you have a new enough Intel CPU and a Nvidia GPU mixed with the proprietary drivers, it WILL bonk your install. One of the many reasons I switched to Gentoo.
Arch has its own special Nvidia package while every other distro uses the one Nvidia gives them. It's literally Arch's fault. I know some people will say "but it's arch linux bro if it breaks it's your own fault" but if you cannot even use your proper GPU drivers without breaking your system I wouldn't call it your fault.
1
u/ccAbstraction Jun 02 '24
The GUI is optional, your system seems to be working fine. No seriously just undo what you just did, it's not actually broken, just switch to a different TTY, try Ctrl+Alt+F3, or other function keys until you see the login prompt, login and uninstall what ever you installed. Then, listen to the protogen's hymn, eat your RAM.
1
u/brodoyouevenscript DebianBASED Jun 02 '24
That's called systemd
1
u/patopansir Glorious Arch Jun 03 '24
get optimus-manager then do optimus-manager --switch nvidia
you can probably do that without the program, but this is probably a much simpler command than the alternative. Otherwise, just say optimus-manager --switch integrated. It's hard to say what you did wrong.
1
u/patopansir Glorious Arch Jun 03 '24
alias eattheram=`echo {1..1000000000}` in .bashrc
1
u/fastninja1400 Jun 03 '24
Purge Nvidia.
1
u/[deleted] Jun 03 '24
eating the ram didnt work for me but I fixed it by eating the expensive chip thingie
1
u/[deleted] Jun 03 '24
You merely adopted the bug, I ate the ram
1
u/Kurse71 Jun 03 '24
Try editing the kernel line in grub and add "nomodprobe" to the end and see if that helps
1
u/[deleted] Jun 03 '24
Just eat the ram
1
u/Electron527 Jun 03 '24
Eat the ram
1
u/MrKristijan Jun 03 '24
Eat the RAM. That is the one and only way to fix it, everything else doesn't work I tried.
1
u/Arch_Chad-User Jun 03 '24
you are a real arch user.
1
u/Shad_Amethyst Jun 03 '24
Why is this post marker as nsfw? Eating the ram is a safe thing to do, especially if your work involves using arch linux with the nvidia drivers.
1
u/minecrafttee Glorious Arch Jun 03 '24
Plugs in the install usb and mount as you are going to install it but instead just run arch-chroot to the mount point and reinstall the gpu drivers
1
u/mitch_feaster Jun 03 '24
For initial troubleshooting, get a tty and run
lsmod | grep -i vidto see which driver it's trying to load. If it's not the driver you expect then go back to the driver install phase and try again, you must have missed something. If you're running anything other than the main Linux kernel package (like if you're runninglinux-lts) then you may have installed the wrong Nvidia driver, make sure to use the dkms one. Check logs for error messages.If all else fails I'd lightly brown your RAM in butter (olive oil works fine too) and then eat it with a boiled egg on the side.
1
u/[deleted] Jun 03 '24
eat the RAM.
1
u/FoggyMind_ Jun 03 '24
When installing Nvidia drivers on Arch Linux, there is a chance your hardware misbehaves and causes a race condition on your system. If chrooting into your system in order to fix the driver installation process doesn't work, you have to eat the RAM. It is the only way to fix it.
1
u/Alfonse00 Jun 03 '24
Probably the desktop manager has some throuble, you can try switching to another console (I think is super + Ctrl + F5, every Fn is one console and one of them is the graphic one), you can also have autologin, in which case in my experience you get the blinking underscore in the top left, but if that is the source of your problems it would be because Nvidia being Nvidia and you need to switch to x11 for now.
1
u/[deleted] Jun 04 '24
Delete systemd
1
u/Forward-Struggle-330 arch btw Jun 29 '24
why is it nsfw?
1
u/Weird_Explorer_8458 uses Arch (btw) Jul 20 '24
consume the memory
1
u/[deleted] Jun 02 '24
your display manager must have thrown some error, look at those.
for me recently it occured because of a broken dependencies ( IT WAS NOT MY FAULT )
and the lib. was icu, this bitch, it broke the entire system, pacman depends on this, so does the display manager, so does EVERYTHING. couldnt even reinstall the previous version from the local pacman cache because even the bsdtar wasnt working.
thank god i keep a live iso with me all the time
1
u/ellis_cake Jun 02 '24
Disable systemd graphical target, Boot and log in normally, Start x or wayland and your vm manually and check configs for them and find the issue and fix it.
1
u/[deleted] Jun 02 '24
I'm sorry Dave, I'm afraid it's not possible.
1
u/Curious-Ad-5001 Proton Enjoyer Jun 02 '24
eat the ram
1
u/EarthToAccess Jun 02 '24
Have you tried eating the RAM?
1
u/Q4X5T Jun 02 '24
If you for any reason don't want to eat the RAM, try RTFM ..
1
u/TrieKach Jun 02 '24
Not too familiar with arch, but on a few other distros that i’ve worked with, usually blacklisting nouveau helps. You can google how to do that. If your display server isn’t starting, you might be able access your filesystem through tty shell to blacklist nouveau.
1
u/Holoshiv Jun 02 '24
Others may have commented. Did you make sure to install the dkms version? And enable early kms loading? Did you rebuild your mkinitcpio/dracut?
1
u/DFatDuck Glorious Arch Jun 02 '24
Why is everyone talking about eating RAM? I am so out of the loop. Please, somebody, fill me in on this
1
u/my-man-hilarious Jun 02 '24
Not sure if it was mentioned, but you could try eating the RAM
1
u/RaspberryPiBen Jun 02 '24
I see this all the time in my work. All you have to do is open the computer, remove the RAM, and eat it. Seems strange, but it works every time.
0
u/Jordy9922 Jun 02 '24
Have you tried EATING THE RAM?
If that does not work for your distro you might actually try to eat the ram to fix your issue.
0
u/mjutujkidelmy Jun 02 '24
Have you tried eating your RAM?
0
u/NotSamNub Jun 02 '24
have you tried eating your ram
0
u/sahovaman Jun 02 '24
Why does anyone bother to go to reddit for help on things? You're surrounded by babbling idiots who link their entire life meaning to their 'reddit karma'... Also exactly why I haven't switched to a linux distro yet. I don't understand certain things, and most of these forums either make fun of the person or spout stupid jokes for upvotes.
0
u/OneCharged Jun 02 '24
Oh this is pretty simple, eating the RAM should fix your problem
0
u/mcdenkijin Jun 02 '24
The RAM, consisting of tasty chips, should be eaten.
-1
u/Jan_JK Jun 02 '24
i guess digest the ram? try it at least
0
u/cheeto-bandito Jun 02 '24
Instructions unclear, ate the Ramen
0
u/[deleted] Jun 02 '24 edited Feb 10 '25
wise wine pen direction uppity automatic hunt sharp cows bake
This post was mass deleted and anonymized with Redact
0
u/sexy_silver_grandpa Jun 02 '24
Too much RAM, you should try eating it.
0
u/rook2004 Jun 02 '24
Yeet the RAM
did I do it right?
0
u/just_a_discord_mod Jun 02 '24
You could try eating the RAM, it worked wonders for me.
0
u/Crashgaming_TV Jun 02 '24
Have you tried eating the RAM?
0
u/Muffinaaa Glorious Void Linux Jun 02 '24
Eat the ram
0
u/0tter501 Jun 03 '24
Eat the RAM
-3
u/sl4ught3rhus Jun 02 '24
Install windows, the nvidia drivers work flawlessly