Another related favor I have to ask: can a Linux guru browse through my
journalctl -xblogs and give them a brief sanity check? If so, I have some related questions about how to discover modified EFI bootloaders, driver issues, etc, in addition to some fairly easy-to-notice ACPI/etc issues. Thanks! I'll post the relevant logs as soon as I can.
memavaild.service problems during boot
i've encountered this problem before and i can't remember how I resolved it.
some specifics on my system:
MacbookPro11,1has an i7 with a
GeForce GT 750M-- this chipset only supports
nvidia-390xx-*at the latest.
Unfortately, while the
GeForce GTX 750chipset supports the
Nvidia 455xxdrivers & featureset, its mobile counterpart
GeForce GT 750Mdoes not
I'm running KDE on Garuda Linux with some Garuda metapackages missing. Not exactly a standard set of Garuda packages.
In the past, I have removed some of these metapackages from my system to get around certain GUI App & userland depedency issues (like installing Zoom and trying to run a Wayland-first system). I'm running Wayland, a Wayland Firefox AUR build (which requires Pipewire).
Are my nvidia driver problems caused by a
Lacking this service could some problems later in boot when loading the nvidia driver modules. the result is that I quickly get a frozen boot image.
fortunately, i can edit the boot entry to remove the "splash" directive, giving me console output during boot and input-focus on the terminal ... which allows me to use the
ctrl-alt Fx shortcut to login to a new terminal session (where
So i have access to modify my system, load packages, etc without needing
I've tried the following:
None of these seem to affect the failure of
memavaild.service. i checked the Google-machine, but have found almost nothing about this service failure on boot.
booting from the last stable BtrFS snapshot. This works, but
sudo pacman -Syubreaks my system.
mhwd -i video-nvidia-390xx-*dkmsto try to add/remove the drivers, which didn't seem to affect the status of the modules being loaded during boot. to be clear,i was intermittently loading my initramdisk & its backup, so this could be responsible
mhwdfailed to remove removing
nvidia-390xx-*packages, since pacman could proceed with unmet dependencies. This required
sudo pacman -R gme python-py3nvmllib32-nvidia-390xx-utils nvidia-390xx-utils nvidia-390xx-settings nvidia-390xx-dkms
mhwdand etc to install video-linux drivers. i am unsure of whether they are being loaded as modules during boot. i can't validate whether
video-linuxdrivers are set as active. i tried referring to
mhwd-gpu --helpbut couldn't find where to set this checkbox via command-line.
Misc questions, notes, possibilities:
it may be that
memavaild.serviceis expected to be running to provide information to Linux about GPU memory stats and, lacking this service, loading the GPU modules fails. (i am a few pieces short of understanding how Kernel modules detect availablility of required services and/or interact with them on boot)
it may be that the
5.11.1-zenkernel is causing the failures.
I noticed a
mhwdwhich was installed the last time before I updated. I may be able to post my last
/var/log/pacman.log. Whether this metapackage is specifically what broke my system, i donno.
I had originally removed the
video-linuxdrivers from my system. I have noticed that they include
vulkanrelated dependencies, so I may want to try them in the future.
However, AFAIK, OBS cannot use the
NVENCGPU-assisted video encoding functionality without
nvidiadrivers. I have a 2013 MacbookPro with a GPU and this is a must-have for me. I livestream while using software like Krita and Julia -- OBS's CPU video encoding causes dropped frames to hover at 2% and spike at 25-75% during heavy CPU usage. Is there anything the
video-linuxdrivers can do to supplant this?
The other time I ran into a
memavaild.servicefailure during boot, I removed
tela-circle-icon-theme-gitpackage and perhaps some related dependencies ... and I think I remember this fixing my problems? I can't remember how i solved it, but I swear it had something to do with the
tela-circle-icon-theme-gitplugin -- which took me about 30 minutes to load after the package was downloaded? Regardless, whatever I did to solve this the first time, it seemed to be unrelated to the
There may be some problem with Arch/KDE's resume/hibernate functionality, but
swapon /dev/sdxNis showing that my swap is mapped during boot. How do I check this?
Can anyone provide a link or a quick overview on the differences b/w the
video-linuxdrivers?) I heard that Linux gaming just got an upgrade with kernel 5.11: something to do with beginning to implement anti-cheat capabilities into the Linux Kernel.
On the nvidia drivers: when reinstalling my
video-nvidiadrivers recently, the system initially installed
video-nvidia-390xx-*with support for nvidia drivers
390.141. then, before i was able to use
390.141, the system decided it needed to downgrade to
390.138-3. Does anyone know why this happened or which logs to search to discover why?
I've got to run for now, but I'll check back later tonight to add logs, etc... Thanks for your help!