Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Problem with the latest nvidia drivers
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Aradayn
n00b
n00b


Joined: 16 Jul 2017
Posts: 8

PostPosted: Fri Oct 12, 2018 5:16 am    Post subject: Reply with quote

Here you are:

https://pastebin.com/rNT6ugE2

Thank you for your time, I really appreciate it. This was working in the past, with an earlier version of this kernel configuration. I guess my problem has nothing to do with the latest driver anyway. I've tried running through the Nvidia driver wiki page again, but no luck, exactly the same results.
Back to top
View user's profile Send private message
Cthulhu666
Apprentice
Apprentice


Joined: 02 Apr 2004
Posts: 195

PostPosted: Fri Oct 12, 2018 8:18 am    Post subject: Reply with quote

No problem, only happy to help.

I'll take a look at the log when time allows it.

If you still have the old kernel config, you could try diff'ing the old and the new and see if anything you have removed stands out (PCI, ACPI, etc...).
_________________
A certified Gentoo lover!
Got 4 Gentoo boxes (2 desktops, 1 laptop and a server/MythTV HTPC).

Bought a computer bundled with windows? Don't want to use windows? Demand a refund!
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 6855

PostPosted: Fri Oct 12, 2018 9:54 am    Post subject: Reply with quote

Your log is showing at second 100 that a new usb device was add, showing the boot has been complete (at 8rd second) and a new usb device has been plug, a sign everything is working.
And your log show nvidia-drivers version 396.54 in use.

I don't think showing anyone a kernel.log of a working nvidia drivers and kernel would help anyone.
Back to top
View user's profile Send private message
Aradayn
n00b
n00b


Joined: 16 Jul 2017
Posts: 8

PostPosted: Sat Oct 13, 2018 3:31 am    Post subject: Reply with quote

Should I move this to a different thread? Like I said earlier, my problem appears to not actually be related to the latest drivers.
And should I keep this in Kernel & Hardware? I kind of think so since my video card is not showing up when I run lspci.
Back to top
View user's profile Send private message
Aradayn
n00b
n00b


Joined: 16 Jul 2017
Posts: 8

PostPosted: Mon Oct 15, 2018 3:37 am    Post subject: Reply with quote

My problem was unrelated. (I was disabling some PCI devices in the local script, and since a hardware configuration change this included my graphics card.)
Additionally, the latest drivers work fine for me without any issue.
Back to top
View user's profile Send private message
i4dnf
Apprentice
Apprentice


Joined: 18 Sep 2005
Posts: 264
Location: Bucharest, Romania

PostPosted: Thu Oct 25, 2018 5:29 am    Post subject: Reply with quote

Follow-up on this:

The problem appears to be the nvidia module hanging if loaded too early in the boot process.
Blacklisting the nvidia modules so that they only get loaded later, when X starts, is a usable workaround for now, at least in my case.
(Only blacklisting 'nvidia' doesn't work, the other nvidia-* modules need to be blacklisted too, as they pull 'nvidia' if they get loaded)

There's also what seems to be a related bug report: #667362
_________________
"The only difference between me and a madman is that I am not MAD" (SALVATOR DALI)
Back to top
View user's profile Send private message
ct85711
Veteran
Veteran


Joined: 27 Sep 2005
Posts: 1660

PostPosted: Thu Oct 25, 2018 6:18 am    Post subject: Reply with quote

Just curious, but did you try adding haveged to your startup. My thinking is that this may be related similar to the slow startup due to insufficient entropy. In this case, the system isn't timing out the module loading (hence the hanging part).
Back to top
View user's profile Send private message
i4dnf
Apprentice
Apprentice


Joined: 18 Sep 2005
Posts: 264
Location: Bucharest, Romania

PostPosted: Thu Oct 25, 2018 7:34 am    Post subject: Reply with quote

No, I didn't, but the problem still manifested on a 4.19.0 kernel with RANDOM_TRUST_CPU=y which prevents the entropy related delay, so I don't think that has any relevance.
_________________
"The only difference between me and a madman is that I am not MAD" (SALVATOR DALI)
Back to top
View user's profile Send private message
pickd.mask
n00b
n00b


Joined: 02 Aug 2011
Posts: 16

PostPosted: Wed Oct 31, 2018 9:42 pm    Post subject: Reply with quote

Problem still exists with nvidia-drivers-410.73 and 410.66 with both 4.18.16 and 4.19.0 kernels.

Blacklisting nvidia modules doesn't help.
I get same stuff as mentioned here: https://bugs.gentoo.org/667362#c0

Quote:
timeout 'nvidia-udev.sh add'
slow: 'nvidia-udev.sh add'
timeout: killing 'nvidia-udev.sh add'
slow: 'nvidia-udev.sh add'


And sometimes udevd says that "specified group 'kvm' unknown".
Applying the patch from https://devtalk.nvidia.com/default/topic/1043346/linux/nvidia-driver-v410-73-fails-to-build-functional-modules/ doesn't help too, so I guess, I have to wait until devs from Nvidia will fix it.
IF they're about to fix it, of course.

Sometimes I think that Linus was right about Nvidia :D
Back to top
View user's profile Send private message
pickd.mask
n00b
n00b


Joined: 02 Aug 2011
Posts: 16

PostPosted: Fri Nov 09, 2018 6:24 pm    Post subject: Reply with quote

Here's what I did to solve it. Works for me.

Also thank you all guys for posting about your issues and thoughts, it helped me to find out what was going on.

Link https://bugs.gentoo.org/670340#c8

I'll copypaste it here, just in case

Quote:
So it appears that I was able to circumwent that issue by rethinking all comments about blacklisting modules coming from wise people.

At last I noticed that IF I blacklist all modules to prevent them from loading (by udev, from what I know), I can actually load modules manually via modprobe and somehow that works perfectly. NOTE: I couldn't load or remove nvidia modules if I haven't blacklisted them.

After that the solution was simple. Probably it's not the best way, maybe it's plain dumb way, but it works for me.

So here's what I did:

1. Added the in /etc/modprobe.d/blacklist.conf following lines:
Code:
blacklist nvidia
blacklist nvidia_drm
blacklist nvidia_modeset


(basically, I just blacklisted all nvidia modules that usually are loaded, which you can see by typing 'lsmod | grep -i nvidia' when your DE works)

2. Created file /etc/local.d/nvidia-udev-workaround.start
Added the following lines in it:
Code:
#!/bin/sh

echo "NVIDIA WORKAROUND IN PROGRESS";
modprobe nvidia_drm;


3. Made that script executable by:
Code:
chmod +x /etc/local.d/nvidia-udev-workaround.start


4. Made sure that local appears in default runlevel:
Code:
rc-update show default


If there's no "local", in order to try that workaround, you should add it by
Code:
rc-update add local default


Then reboot.

Works for me with 410.73 and 415.13 nvidia-drivers, with 4.18.17 and 4.19.1 kernels.
Back to top
View user's profile Send private message
Utsuho Reiuji
Apprentice
Apprentice


Joined: 03 Apr 2013
Posts: 153

PostPosted: Sat Nov 10, 2018 6:07 pm    Post subject: Reply with quote

how do you prevent xdm to start before local was invoked? Your fix also works for me, but I have to restart xdm before I get to use my DE.

Edit: On a second look, I noticed that xdm actually doesn't start automatically using this fix. Still better than no desktop...
Back to top
View user's profile Send private message
pickd.mask
n00b
n00b


Joined: 02 Aug 2011
Posts: 16

PostPosted: Sat Nov 10, 2018 10:45 pm    Post subject: Reply with quote

Utsuho Reiuji wrote:
how do you prevent xdm to start before local was invoked? Your fix also works for me, but I have to restart xdm before I get to use my DE.

Edit: On a second look, I noticed that xdm actually doesn't start automatically using this fix. Still better than no desktop...


On my system everything autostarts just fine. I didn't make any particular setup related to boot order or something. Maybe you should try to add line with "sleep 10;" to delay modprobe. Just a wild guess.

Here's some info about my runlevels:

Code:
ivan@pc ~ $ rc-update show boot
               binfmt | boot
             bootmisc | boot
          consolefont | boot
                 fsck | boot
             hostname | boot
              hwclock | boot
              keymaps | boot
           localmount | boot
             loopback | boot
              modules | boot
                 mtab | boot
   opentmpfiles-setup | boot
               procfs | boot
                 root | boot
                 swap | boot
               sysctl | boot
            syslog-ng | boot
         termencoding | boot
              urandom | boot
ivan@pc ~ $ rc-update show default
               cronie | default
                cupsd | default
                 dbus | default
              elogind | default
             iptables | default
                local | default
             net.eth0 | default
             netmount | default
              openvpn | default
                  xdm | default


Also I have #rc_parallel="NO" (commented) in /etc/rc.conf. Nothing else about parallel boot is present. That might be the case.
It also worth mentioning that I use kde and sddm.

Maybe something could be helpful.
Back to top
View user's profile Send private message
Utsuho Reiuji
Apprentice
Apprentice


Joined: 03 Apr 2013
Posts: 153

PostPosted: Sun Nov 11, 2018 2:13 am    Post subject: Reply with quote

Thanks for your reply, pickd.mask, this helps a bit. I need to finish this massive update 1st to test things, but I'll try using rc_parallel="NO" just in case.
Not sure if that was the cause, but I noticed that /etc/init.d/local had
Code:
depend()
{
       after *
        keyword -timeout
}
in it. Maybe uncommenting that "after *" bit will help. I also added "after local" to /etc/init.d/xdm in the same section.

Edit: that worked.
Back to top
View user's profile Send private message
pickd.mask
n00b
n00b


Joined: 02 Aug 2011
Posts: 16

PostPosted: Mon Nov 12, 2018 2:09 am    Post subject: Reply with quote

Utsuho Reiuji wrote:

Edit: that worked.


That's great :-)
BTW, I checked my /etc/init.d/local and that line was uncommented by default, I never touched it.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum