On January 5, 2017 4:54:02 PM GMT+01:00, Daniel Frey <[email protected]> wrote: >On 01/05/2017 06:12 AM, Corbin Bird wrote: >> >> On 01/04/2017 10:52 PM, Daniel Frey wrote: >>> So I updated my nvidia driver and got the following: >>> >>> [ 75.557567] nvidia-nvlink: Nvlink Core is being initialized, >major >>> device number 247 >>> [ 75.557583] NVRM: loading NVIDIA UNIX x86_64 Kernel Module >375.26 >>> Thu Dec 8 18:36:43 PST 2016 (using threaded interrupts) >>> [ 75.701289] nvidia-modeset: Loading NVIDIA Kernel Mode Setting >Driver >>> for UNIX platforms 375.26 Thu Dec 8 18:04:14 PST 2016 >>> [ 75.769472] nvidia_drm: Unknown symbol >>> drm_atomic_helper_plane_destroy_state (err 0) >>> [ 75.769479] nvidia_drm: Unknown symbol drm_kms_helper_poll_fini >(err 0) >>> [ 75.769491] nvidia_drm: Unknown symbol >drm_kms_helper_poll_disable >>> (err 0) >>> [ 75.769497] nvidia_drm: Unknown symbol drm_kms_helper_poll_init >(err 0) >>> [ 75.769514] nvidia_drm: Unknown symbol >>> drm_atomic_helper_disable_plane (err 0) >>> [ 75.769527] nvidia_drm: Unknown symbol >>> drm_atomic_helper_cleanup_planes (err 0) >>> [ 75.769531] nvidia_drm: Unknown symbol drm_helper_hpd_irq_event >(err 0) >>> [ 75.769538] nvidia_drm: Unknown symbol >>> drm_atomic_helper_crtc_destroy_state (err 0) >>> [ 75.769565] nvidia_drm: Unknown symbol drm_atomic_helper_check >(err 0) >>> [ 75.769567] nvidia_drm: Unknown symbol >>> drm_atomic_helper_connector_destroy_state (err 0) >>> [ 75.769573] nvidia_drm: Unknown symbol >>> drm_atomic_helper_plane_duplicate_state (err 0) >>> [ 75.769603] nvidia_drm: Unknown symbol >drm_atomic_helper_plane_reset >>> (err 0) >>> [ 75.769606] nvidia_drm: Unknown symbol >>> drm_atomic_helper_prepare_planes (err 0) >>> [ 75.769610] nvidia_drm: Unknown symbol >drm_helper_mode_fill_fb_struct >>> (err 0) >>> [ 75.769622] nvidia_drm: Unknown symbol >drm_atomic_helper_set_config >>> (err 0) >>> [ 75.769624] nvidia_drm: Unknown symbol >>> drm_atomic_helper_connector_duplicate_state (err 0) >>> [ 75.769630] nvidia_drm: Unknown symbol >drm_atomic_helper_crtc_reset >>> (err 0) >>> [ 75.769636] nvidia_drm: Unknown symbol >drm_kms_helper_hotplug_event >>> (err 0) >>> [ 75.769644] nvidia_drm: Unknown symbol >drm_atomic_helper_swap_state >>> (err 0) >>> [ 75.769646] nvidia_drm: Unknown symbol >drm_atomic_helper_page_flip >>> (err 0) >>> [ 75.769648] nvidia_drm: Unknown symbol >>> drm_atomic_helper_connector_reset (err 0) >>> [ 75.769653] nvidia_drm: Unknown symbol >>> drm_atomic_helper_crtc_duplicate_state (err 0) >>> [ 75.769656] nvidia_drm: Unknown symbol >drm_atomic_helper_update_plane >>> (err 0) >>> >>> I've traced this to needing KMS helper support in the kernel. >>> >>> For the life of me, I can't find it to enable it. When searching the >>> kernel, it shows up but doesn't say exactly where it is. >>> >>> Surely someone else has run across this and has a way to enable: >>> >>> CONFIG_DRM_KMS_HELPER >>> CONFIG_DRM_KMS_FB_HELPER >>> CONFIG_DRM_FBDEV_EMULATION >>> >>> ?? >>> >>> I am thinking it needs something as a prerequisite but I can't grok >that >>> line in the kernel. >>> >>> Dan >>> >> >> More info, please. >> >> Question #1 : is this a (U)EFI based system? > >No, it's an old BIOS based system. > >> Question #2 : which FB(s) are enabled? >> > >I just looked, the EFI-based one is the only one selected. nvidia >doesn't like the nvidia framebuffer, so I had to deselect it. > >Dan
Actually. Nvidia complains about all framebuffers. I do use the EFI framebuffer as I want to be able to fall back to the text consoles when necessary. I have not encountered any major issues with this. Might occur if I switch between X and text regularly. Which I generally don't. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
