1 |
On 01/05/2017 05:31 PM, Corbin Bird wrote: |
2 |
> |
3 |
> On 01/05/2017 09:54 AM, Daniel Frey wrote: |
4 |
>> On 01/05/2017 06:12 AM, Corbin Bird wrote: |
5 |
>>> On 01/04/2017 10:52 PM, Daniel Frey wrote: |
6 |
>>>> So I updated my nvidia driver and got the following: |
7 |
>>>> |
8 |
>>>> [ 75.557567] nvidia-nvlink: Nvlink Core is being initialized, major |
9 |
>>>> device number 247 |
10 |
>>>> [ 75.557583] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 375.26 |
11 |
>>>> Thu Dec 8 18:36:43 PST 2016 (using threaded interrupts) |
12 |
>>>> [ 75.701289] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver |
13 |
>>>> for UNIX platforms 375.26 Thu Dec 8 18:04:14 PST 2016 |
14 |
>>>> [ 75.769472] nvidia_drm: Unknown symbol |
15 |
>>>> drm_atomic_helper_plane_destroy_state (err 0) |
16 |
>>>> [ 75.769479] nvidia_drm: Unknown symbol drm_kms_helper_poll_fini (err 0) |
17 |
>>>> [ 75.769491] nvidia_drm: Unknown symbol drm_kms_helper_poll_disable |
18 |
>>>> (err 0) |
19 |
>>>> [ 75.769497] nvidia_drm: Unknown symbol drm_kms_helper_poll_init (err 0) |
20 |
>>>> [ 75.769514] nvidia_drm: Unknown symbol |
21 |
>>>> drm_atomic_helper_disable_plane (err 0) |
22 |
>>>> [ 75.769527] nvidia_drm: Unknown symbol |
23 |
>>>> drm_atomic_helper_cleanup_planes (err 0) |
24 |
>>>> [ 75.769531] nvidia_drm: Unknown symbol drm_helper_hpd_irq_event (err 0) |
25 |
>>>> [ 75.769538] nvidia_drm: Unknown symbol |
26 |
>>>> drm_atomic_helper_crtc_destroy_state (err 0) |
27 |
>>>> [ 75.769565] nvidia_drm: Unknown symbol drm_atomic_helper_check (err 0) |
28 |
>>>> [ 75.769567] nvidia_drm: Unknown symbol |
29 |
>>>> drm_atomic_helper_connector_destroy_state (err 0) |
30 |
>>>> [ 75.769573] nvidia_drm: Unknown symbol |
31 |
>>>> drm_atomic_helper_plane_duplicate_state (err 0) |
32 |
>>>> [ 75.769603] nvidia_drm: Unknown symbol drm_atomic_helper_plane_reset |
33 |
>>>> (err 0) |
34 |
>>>> [ 75.769606] nvidia_drm: Unknown symbol |
35 |
>>>> drm_atomic_helper_prepare_planes (err 0) |
36 |
>>>> [ 75.769610] nvidia_drm: Unknown symbol drm_helper_mode_fill_fb_struct |
37 |
>>>> (err 0) |
38 |
>>>> [ 75.769622] nvidia_drm: Unknown symbol drm_atomic_helper_set_config |
39 |
>>>> (err 0) |
40 |
>>>> [ 75.769624] nvidia_drm: Unknown symbol |
41 |
>>>> drm_atomic_helper_connector_duplicate_state (err 0) |
42 |
>>>> [ 75.769630] nvidia_drm: Unknown symbol drm_atomic_helper_crtc_reset |
43 |
>>>> (err 0) |
44 |
>>>> [ 75.769636] nvidia_drm: Unknown symbol drm_kms_helper_hotplug_event |
45 |
>>>> (err 0) |
46 |
>>>> [ 75.769644] nvidia_drm: Unknown symbol drm_atomic_helper_swap_state |
47 |
>>>> (err 0) |
48 |
>>>> [ 75.769646] nvidia_drm: Unknown symbol drm_atomic_helper_page_flip |
49 |
>>>> (err 0) |
50 |
>>>> [ 75.769648] nvidia_drm: Unknown symbol |
51 |
>>>> drm_atomic_helper_connector_reset (err 0) |
52 |
>>>> [ 75.769653] nvidia_drm: Unknown symbol |
53 |
>>>> drm_atomic_helper_crtc_duplicate_state (err 0) |
54 |
>>>> [ 75.769656] nvidia_drm: Unknown symbol drm_atomic_helper_update_plane |
55 |
>>>> (err 0) |
56 |
>>>> |
57 |
>>>> I've traced this to needing KMS helper support in the kernel. |
58 |
>>>> |
59 |
>>>> For the life of me, I can't find it to enable it. When searching the |
60 |
>>>> kernel, it shows up but doesn't say exactly where it is. |
61 |
>>>> |
62 |
>>>> Surely someone else has run across this and has a way to enable: |
63 |
>>>> |
64 |
>>>> CONFIG_DRM_KMS_HELPER |
65 |
>>>> CONFIG_DRM_KMS_FB_HELPER |
66 |
>>>> CONFIG_DRM_FBDEV_EMULATION |
67 |
>>>> |
68 |
>>>> ?? |
69 |
>>>> |
70 |
>>>> I am thinking it needs something as a prerequisite but I can't grok that |
71 |
>>>> line in the kernel. |
72 |
>>>> |
73 |
>>>> Dan |
74 |
>>>> |
75 |
>>> More info, please. |
76 |
>>> |
77 |
>>> Question #1 : is this a (U)EFI based system? |
78 |
>> No, it's an old BIOS based system. |
79 |
>> |
80 |
>>> Question #2 : which FB(s) are enabled? |
81 |
>>> |
82 |
>> I just looked, the EFI-based one is the only one selected. nvidia |
83 |
>> doesn't like the nvidia framebuffer, so I had to deselect it. |
84 |
>> |
85 |
>> Dan |
86 |
>> |
87 |
> |
88 |
> Link : https://wiki.gentoo.org/wiki/NVidia/nvidia-drivers |
89 |
> |
90 |
> Quotes from the Wiki : |
91 |
>> Be warned that enabling /efifb/ support in kernel (|CONFIG_FB_EFI=y|) |
92 |
>> causes intermittent problems with the initialization of the NVIDIA |
93 |
>> drivers. |
94 |
>> Device Drivers ---> |
95 |
>> Graphics support ---> |
96 |
>> Frame buffer Devices ---> |
97 |
>> <*> Support for frame buffer devices ---> |
98 |
>> < > nVidia Framebuffer Support |
99 |
>> < > nVidia Riva support |
100 |
>> Device drivers ---> |
101 |
>> Graphics support ---> |
102 |
>> < > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) |
103 |
> |
104 |
> The standard "old" VESA VGA not enabled? |
105 |
|
106 |
No, I don't think I ever had it enabled. We're talking years (maybe even |
107 |
more than a decade) here. I probably turned all that off when installing |
108 |
the Nvidia drivers for the first time. |
109 |
|
110 |
> |
111 |
> You have a BIOS based system. You might want to enable it and recompile. |
112 |
> If memory is correct ... the console and X terminals need it ( or the |
113 |
> EFI variant for UEFI based systems ). |
114 |
> |
115 |
> It should not interfere with the nvidia drivers. |
116 |
> |
117 |
> Look for this option as well : |
118 |
>> Bus options (PCI etc.) ---> |
119 |
>> [*] Mark VGA/VBE/EFI FB as generic system framebuffer |
120 |
> |
121 |
> Nvidia has really changed since my last Nvidia based card. |
122 |
> |
123 |
> |
124 |
|
125 |
I think I fixed it by accident. I couldn't find the KMS helpers to |
126 |
enable for an external module in the kernel, so I built the Intel driver |
127 |
with KMS support and it dragged in the KMS helper bits (confirmed by |
128 |
grepping .config). Why can't we just turn that option on directly in |
129 |
menuconfig for external modules? This is in gentoo-sources. |
130 |
|
131 |
I've rebooted and the problem has gone away, go figure. |
132 |
|
133 |
Dan |