| View previous topic :: View next topic |
| Author |
Message |
tatterdemalian
n00b
Joined: 21 Jul 2011
Posts: 46
|
 Posted: Wed Feb 13, 2019 7:55 pm Post subject: [SOLVED]Turning on CONFIG_HIGH_RES_TIMERS breaks nvidia... |
 |
|
Trying to get a new Gentoo GNOME installation set up on an Alienware 17 r5 laptop. Dual-boots to Windows 10 OEM installation using a 256GB SSD that Gentoo apparently can't even identify, let alone support. This severely limits what I can reconfigure in the BIOS, even changing the system time to UTC permanently was a trip and three tenths.
Right out of the gate, I found out that neither Wayland nor Nouveau can function with the integrated GeForce 1070. Not sure whether it's due to the barely Nouveau-supported card, or the nVidia Optimus tech that integrates an Intel Coffee Lake card. So I followed the nVidia Optimus guide to set up the Intel card for modesetting, and installed nvidia-drivers for use with GNOME.
This worked just fine, and in fact I'm using my perfectly functioning GNOME desktop right now to compose this message. The problem comes in when I try to address Pulseaudio's problem with the lack of high res timers by rebuilding the kernel with CONFIG_HIGH_RES_TIMERS=y. For some reason, this seemingly unrelated change makes nvidia-drivers crap itself during boot, resulting in GNOME not having any valid screens to start on, resulting in gdm.service endlessly trying to restart Xorg to the point of bricking the system.
| Quote: | | CONFIG_HIGH_RES_TIMERS=n |
| Code: | dmesg | grep -i "nvidia"
[ 3.340940] nvidia: loading out-of-tree module taints kernel.
[ 3.340946] nvidia: module license 'NVIDIA' taints kernel.
[ 3.356845] nvidia-nvlink: Nvlink Core is being initialized, major device number 250
[ 3.357068] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[ 3.457890] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 (using threaded interrupts)
[ 3.459688] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 415.27 Thu Dec 20 17:06:08 CST 2018
[ 3.460467] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[ 3.460468] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0 |
| Quote: | | CONFIG_HIGH_RES_TIMERS=y |
| Code: | dmesg | grep -i "nvidia"
[ 3.535292] nvidia: loading out-of-tree module taints kernel.
[ 3.535298] nvidia: module license 'NVIDIA' taints kernel.
[ 3.540845] nvidia: disagrees about version of symbol wake_up_process
[ 3.540846] nvidia: Unknown symbol wake_up_process (err -22)
[ 3.832452] nvidia: disagrees about version of symbol wake_up_process
[ 3.832453] nvidia: Unknown symbol wake_up_process (err -22)
[ 4.512287] nvidia: disagrees about version of symbol wake_up_process
[ 4.512289] nvidia: Unknown symbol wake_up_process (err -22)
[ 4.616826] nvidia: disagrees about version of symbol wake_up_process
[ 4.616827] nvidia: Unknown symbol wake_up_process (err -22)
[ 30.955246] nvidia: disagrees about version of symbol wake_up_process
[ 30.955248] nvidia: Unknown symbol wake_up_process (err -22)
[ 32.049971] nvidia: disagrees about version of symbol wake_up_process
[ 32.049973] nvidia: Unknown symbol wake_up_process (err -22)
[ 32.210294] nvidia: disagrees about version of symbol wake_up_process
[ 32.210296] nvidia: Unknown symbol wake_up_process (err -22)
[ 32.286767] nvidia: disagrees about version of symbol wake_up_process
[ 32.286770] nvidia: Unknown symbol wake_up_process (err -22) |
There are several other changes I would like to make to the kernel, like enabling iptables support, but these cause the same problems as turning on CONFIG_HIGH_RES_TIMERS. All I can figure is that some part of nvidia-drivers STILL isn't rebuilt with the latest version of GCC, and apparently it's a part that handles integration with around half the kernel settings needed to run anything beyond LiveCD utilities.
Anyone else know if this is the case, or is it just something dumb that I'm doing wrong (besides not messing around with Wayland/Nouveau any more)?
Last edited by tatterdemalian on Thu Feb 14, 2019 12:43 am; edited 1 time in total |
|
| Back to top |
|
 |
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Wed Feb 13, 2019 8:25 pm Post subject: |
|
|
| You changed your kernel without updating the kernel modules. emerge -1 @module-rebuild and reboot to fix it. |
|
| Back to top |
|
|
jburns
Veteran
Joined: 18 Jan 2007
Posts: 1227
Location: Massachusetts USA
|
| Posted: Wed Feb 13, 2019 8:29 pm Post subject: |
|
|
| Using sys-kernel/gentoo-sources-4.20.8 and x11-drivers/nvidia-drivers-418.30, I have no problem with CONFIG_HIGH_RES_TIMERS=y. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55015
Location: 56N 3W
|
| Posted: Wed Feb 13, 2019 8:35 pm Post subject: |
|
|
tatterdemalian,
When you rebuild the kernel, you must rebuild all external kernel modules against the new kernel.
The /usr/src/linux symlink must be correct as all external kernel modules follow it to find the kernel to build against.
It need not be your running kernel either.
| Code: | | emerge @module-rebuild |
rebuilds all of your out of tree kernel modules.
Its quite popular to build a new kernel but not install it correctly, usually because /boot is not mounted, so you end up with an old kernel and new modules too.
will tell the build time of the running kernel. If its not what you expect, investigate your kernel install process.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
tatterdemalian
n00b
Joined: 21 Jul 2011
Posts: 46
|
| Posted: Wed Feb 13, 2019 9:40 pm Post subject: |
|
|
| Ant P. wrote: | | You changed your kernel without updating the kernel modules. emerge -1 @module-rebuild and reboot to fix it. |
I *knew* it was something stupid I did wrong. Off to do that as soon as my USB bootstick backup finishes. Thanks to everyone that responded!
EDIT: Tested and working now, thanks again! |
|
| Back to top |
|
|
|
|
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
|
|
Kernel & Hardware
