Closing
]]>That is normal and you should remember it when you get actual instabilities. I run nvidia together with efifb and experience no problems so far.
Anyway, I seem to have solved the problem for me, just create two files:
# /etc/udev/rules.d/99-make-udev-drm-aware.rules SUBSYSTEM=="drm", TAG+="systemd"
# /etc/systemd/system/kdm.service.d/10-wait-for-card.conf [Unit] Wants=dev-dri-card0.device After=dev-dri-card0.device
I do apologize for bumping an old thread, but I cannot find this answer anywhere I've looked. I do not use KDE nor kdm, thus I have "kdm.service.d" directory. So where exactly should I put the 10-wait-for-card.conf file so that it starts automatically with systemd? Thanks for any help.
]]>brain0 wrote:dwightjl wrote:Is this something NVIDIA has to fix, or is it on our end?
If in doubt, it's nvidia's fault.
But why did it work OK before ?
Ask nvidia.
]]>dwightjl wrote:Is this something NVIDIA has to fix, or is it on our end?
If in doubt, it's nvidia's fault.
But why did it work OK before ?
]]>Is this something NVIDIA has to fix, or is it on our end?
If in doubt, it's nvidia's fault.
]]>I encountered this same issue last night when I tried a fresh Arch install. I tried the fixes in this thread, but without success. I'm not using KDM, but GDM and Gnome 3, so maybe those fixes don't apply to me.
The 304.xx drivers work fine. Is there any word on a real fix for this problem? Ubuntu 14.04 with Kernel 3.13.1 and the 331.38 drivers works fine, why not Arch? Lots of new users will be discouraged by this problem.
Is this something NVIDIA has to fix, or is it on our end?
Are you sure you have the same problem? I also have GDM/Gnome and adding nvidia to the modules in /etc/mkinitcpio.conf and rebuild the kernel image solved the problem for me perfectly. Have you done all steps?
]]>I encountered this same issue last night when I tried a fresh Arch install. I tried the fixes in this thread, but without success. I'm not using KDM, but GDM and Gnome 3, so maybe those fixes don't apply to me.
The 304.xx drivers work fine. Is there any word on a real fix for this problem? Ubuntu 14.04 with Kernel 3.13.1 and the 331.38 drivers works fine, why not Arch? Lots of new users will be discouraged by this problem.
Is this something NVIDIA has to fix, or is it on our end?
I'd like to know this also. Is this a NVIDIA driver problem or just systemd / kernel ?
]]>The 304.xx drivers work fine. Is there any word on a real fix for this problem? Ubuntu 14.04 with Kernel 3.13.1 and the 331.38 drivers works fine, why not Arch? Lots of new users will be discouraged by this problem.
Is this something NVIDIA has to fix, or is it on our end?
]]>Too quickly system
Fresh installation , no ntfs4 mount in fstab
But added ntfs4 mount in fstab ,boot prosses slow bit and kdm start rigt.
Amazing i have too quick speed the ligt speed system.
]]>kdm [399]: X server died during startup
kdm [399]: X server for display :0 cannot be started, session disabled
Is this still bug ??
Solution is add nvidia as a module in mkinitpio.conf
]]>Edit: Actually now it is enough to add nvidia as a module; i deleted the two other files.
Edit2: The new nvidia Version from the official repo seems to work fine without any hack necessary
]]>blackout23 wrote:mangus wrote:yeah, sure it works thank you, much better than my horrible hack.
So, in my case, it's just a matter of adding nvidia module to the mkinitcpio modules array for an early device creation.
I have kms and drm disabled in my system so the files posted by brain0 are not relevant in my case , I think.
Thanks to everyoneJust remember that you have it in there. When you pacman -Syu and you get an update for nvidia and linux it might install linux first and run mkinitcpio before having the new nvidia module installed which will cause mkinitcpio to fail. So you simply have to run mkinitcpio again after -Syu is finished and the new nvidia module is installed.
I use this method on both my computers and never had an issue with nvidia and the kernel in years.
yay, thanks for the tip! give this man a thank button pls!
As pointed out: This also works. You just have to remember rebuilding your init image, when your driver is being updated!
]]>The file /etc/systemd/system/kdm.service.d/10-wait-for-card.conf didn't exist for me, so I had to add the contents of that file to the [Unit] sections of my /etc/systemd/system/display-manager.service
[Unit] Description=K Display Manager After=systemd-user-sessions.service Wants=dev-dri-card0.device After=dev-dri-card0.device [Service] ExecStart=/usr/bin/kdm -nodaemon [Install] Alias=display-manager.service
Please learn to read. You are supposed to create the file, and you are supposed to add exactly the contents I posted, not blindly copy the whole kdm.service unit.
]]>saty wrote:When I was trying to figure this on my own I found some "Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console." messages in the log files. They probably have been there forever but I haven't bothered with them since now.
That is normal and you should remember it when you get actual instabilities. I run nvidia together with efifb and experience no problems so far.
Anyway, I seem to have solved the problem for me, just create two files:
# /etc/udev/rules.d/99-make-udev-drm-aware.rules SUBSYSTEM=="drm", TAG+="systemd"
# /etc/systemd/system/kdm.service.d/10-wait-for-card.conf [Unit] Wants=dev-dri-card0.device After=dev-dri-card0.device
If you have more than one nvidia card, also plug in card1 etc.
Your workarround worked also (sort of) for me.
The file /etc/systemd/system/kdm.service.d/10-wait-for-card.conf didn't exist for me, so I had to add the contents of that file to the [Unit] sections of my /etc/systemd/system/display-manager.service
[Unit]
Description=K Display Manager
After=systemd-user-sessions.service
Wants=dev-dri-card0.device
After=dev-dri-card0.device
[Service]
ExecStart=/usr/bin/kdm -nodaemon
[Install]
Alias=display-manager.service
mangus wrote:blackout23 wrote:Shouldn't adding MODULES="nvidia" to /etc/mkinitcpio.conf and rebuilding initramfs with #mkinitcpio -p linux work, too?
yeah, sure it works thank you, much better than my horrible hack.
So, in my case, it's just a matter of adding nvidia module to the mkinitcpio modules array for an early device creation.
I have kms and drm disabled in my system so the files posted by brain0 are not relevant in my case , I think.
Thanks to everyoneJust remember that you have it in there. When you pacman -Syu and you get an update for nvidia and linux it might install linux first and run mkinitcpio before having the new nvidia module installed which will cause mkinitcpio to fail. So you simply have to run mkinitcpio again after -Syu is finished and the new nvidia module is installed.
I use this method on both my computers and never had an issue with nvidia and the kernel in years.
yay, thanks for the tip! give this man a thank button pls!
]]>