Re: [gentoo-user] nvidia driver missing symbols

[Daniel Frey]

On 01/05/2017 05:31 PM, Corbin Bird wrote:
> 
> On 01/05/2017 09:54 AM, Daniel Frey 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
>>
> 
> Link : https://wiki.gentoo.org/wiki/NVidia/nvidia-drivers
> 
> Quotes from the Wiki :
>> Be warned that enabling /efifb/ support in kernel (|CONFIG_FB_EFI=y|)
>> causes intermittent problems with the initialization of the NVIDIA
>> drivers.
>> Device Drivers --->
>> Graphics support --->
>> Frame buffer Devices --->
>> <*> Support for frame buffer devices --->
>> < >   nVidia Framebuffer Support
>> < >   nVidia Riva support
>> Device drivers --->
>> Graphics support --->
>> < > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
> 
> The standard "old" VESA VGA not enabled?

No, I don't think I ever had it enabled. We're talking years (maybe even
more than a decade) here. I probably turned all that off when installing
the Nvidia drivers for the first time.

> 
> You have a BIOS based system. You might want to enable it and recompile.
> If memory is correct ... the console and X terminals need it ( or the
> EFI variant  for UEFI based systems ).
> 
> It should not interfere with the nvidia drivers.
> 
> Look for this option as well :
>> Bus options (PCI etc.)  --->
>> [*] Mark VGA/VBE/EFI FB as generic system framebuffer
> 
> Nvidia has really changed since my last Nvidia based card.
> 
> 

I think I fixed it by accident. I couldn't find the KMS helpers to
enable for an external module in the kernel, so I built the Intel driver
with KMS support and 

Re: [gentoo-user] nvidia driver missing symbols

[Corbin Bird]

On 01/05/2017 09:54 AM, Daniel Frey 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
>

Link : https://wiki.gentoo.org/wiki/NVidia/nvidia-drivers

Quotes from the Wiki :
> Be warned that enabling /efifb/ support in kernel (|CONFIG_FB_EFI=y|)
> causes intermittent problems with the initialization of the NVIDIA
> drivers.
> Device Drivers --->
> Graphics support --->
> Frame buffer Devices --->
> <*> Support for frame buffer devices --->
> < >   nVidia Framebuffer Support
> < >   nVidia Riva support
> Device drivers --->
> Graphics support --->
> < > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)

The standard "old" VESA VGA not enabled?

You have a BIOS based system. You might want to enable it and recompile.
If memory is correct ... the console and X terminals need it ( or the
EFI variant  for UEFI based systems ).

It should not interfere with the nvidia drivers.

Look for this option as well :
> Bus options (PCI etc.)  --->
> [*] Mark VGA/VBE/EFI FB as generic system framebuffer

Nvidia has really changed since my last Nvidia based card.

[gentoo-user] Re: nvidia driver missing symbols

[Nikos Chantziaras]

On 01/05/2017 07:28 PM, J. Roeleveld wrote:

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.


It only complains when the graphics card was initialized using BIOS. 
This is true even in UEFI mode. It's recommended to disable the CSM 
(Compatibility Support Module) in the BIOS setup. Not all mainboards 
have that option though. But if you disable it, the graphics card will 
be initialized by UEFI on startup, which is fully supported by the 
driver (and the warning message will disappear.)

Re: [gentoo-user] nvidia driver missing symbols

[J. Roeleveld]

On January 5, 2017 4:54:02 PM GMT+01:00, Daniel Frey  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.

Re: [gentoo-user] nvidia driver missing symbols

[Daniel Frey]

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

Re: [gentoo-user] nvidia driver missing symbols

[Corbin Bird]

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?
Question #2 : which FB(s) are enabled?

Re: [gentoo-user] depclean missing packages

[Róbert Čerňanský]

On Wed, 4 Jan 2017 21:32:50 +0100
Arve Barsnes  wrote:

> On 4 January 2017 at 21:25, Daniel Frey  wrote:
> 
> > I always do `emerge -uDN world`. Which is --update --deep
> > --newuse... I've just never had that happen with depclean before.
> > Odd, no?
> >
> > I usually do:
> >
> > `emerge -uDN world`
> >
> > and
> >
> > `emerge -ac` to depclean afterwards.
> >
> > As I use --deep all the time, I'm still confused as to why needed
> > packages weren't installed.
> >
> >  
> I've also always used --deep, but I've seen this many times. I've
> recently started using "--with-bdeps=y" as well, and I don't think
> I've seen this happen since then, so I'm guessing binary deps are the
> culprit.

I think so too.  Since Dan does not use --with-bdeps this is what
might happen:

'qtdeclarative', 'qtxml' and 'qtcore' were updated from 5.6.1 to a
higher version.  However 'linguist-tools', being only a build
dependency, was not updated and remains at version 5.6.1.  Since
'linguist-tools-5.6.1' depends on 'qtdeclarative-5.6.1', 'qtxml-5.6.1'
and 'qtcore-5.6.1' --depclean resolves those as missing packages.

So as Arve is saying - using --with-bdeps should prevent this.  There
are two ways how to use it:

- As 'emerge -uDN --with-bdeps=y world' - in this case build
dependencies will be updated as well.

- As 'emerge -ac --with-bdeps=n' - in this case build dependencies
will be depcleaned (removed).  Notice there is 'n' in --with-bdeps.

I prefer second option since this leaves a clean system where only
packages required to run it are installed.  Disadvantage is that upon
next update the build dependencies are emerged again, so it takes more
time to update the system.

Robert


-- 
Róbert Čerňanský
E-mail: ope...@tightmail.com
Jabber: h...@jabber.sk

Re: [gentoo-user] samba as AD DC on gentoo

[Stefan G. Weichinger]

Am 2017-01-05 um 07:42 schrieb J. Roeleveld:
>> I am still using using samba3 for my NAS.
>> Samba4 has been planned for a while, but with it wanting it's own LDAP and
>> tree layout, I have a few more things to organise.
>>
>> Other projects keep getting a higher priority.
> 
> Scratch that.
> I am actually using Samba 4.2.11, but using the same config as I did with 
> Samba-3.

You don't need to change your priorities: as I found out yesterday night
samba-4.x is not yet ready to provide AD-DC services on gentoo.

I found out while researching another issue related to smbclient and
german umlauts (popping up when I run backups with amanda).

I wrote to the samba- and the amanda-users-ml, and bgo:

https://bugs.gentoo.org/show_bug.cgi?id=593486

tl;dr ::

* samba in portage is quite old, 4.2.x is EOL upstream (4.6.rc1 released
already upstream)

* samba in portage does not yet provide the bundled heimdal version that
upstream samba works with (in terms of AD-DC services, other stuff works
with mit-krb5 as well).

* there's a test ebuild which uses that internal heimdal-version, see
Comment 9 in the mentioned bug.

But to me that is too unstable and risky to move a whole Windows domain
to already.

[gentoo-user] Re: nvidia driver missing symbols

[Nikos Chantziaras]

On 01/05/2017 08:05 AM, wabe wrote:

Make sure that you have also enabled CONFIG_DRM.

CONFIG_DRM=y
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_KMS_FB_HELPER=y
CONFIG_DRM_FBDEV_EMULATION=y


Eh, no. For nvidia, these need to be all disabled. Disable all KMS and 
DRM options. Then it should work.

Re: [gentoo-user] depclean missing packages

[Dale]

Alan McKinnon wrote:
> On 05/01/2017 06:46, Dale wrote:
>> Alan McKinnon wrote:
>>> On 04/01/2017 22:25, Daniel Frey wrote:
 On 01/04/2017 08:30 AM, Neil Bothwick wrote:
> On Wed, 4 Jan 2017 18:11:10 +0200, Alan McKinnon wrote:
>
>>> Using the --deep switch can / does pull in a lot of seemingly extra
>>> packages.  
>> --deep is practically *required* to do a full proper update.
>>
>> Say A is in world, and A depends on B which depends on C.
>> C is updated in the tree, and usually you will want C updated.
>>
>> However, update world will NOT update C.
>> Why? Because "world" is not a synonym for "everything",
>> "world" is something quite literal - the exact contents of
>> /var/lib/portage/world (and /var/lib/portage/world_sets if present)
>> "update world" updates that list only.
> That's not quite true, according to the man page. Without --deep portage
> considers only the specified files and their immediate dependencies
> (deps that are listed in the package's ebuild). So without --deep,
> updates to B as well a A would be picked up, but not C.
>
>> Adding --deep follows the
>> dependencies of the list, basically meaning
>>
>> "update --deep world" IS a synonym for "everything"
 I always do `emerge -uDN world`. Which is --update --deep --newuse...
 I've just never had that happen with depclean before. Odd, no?

 I usually do:

 `emerge -uDN world`

 and

 `emerge -ac` to depclean afterwards.

 As I use --deep all the time, I'm still confused as to why needed
 packages weren't installed.

 Dan

>>> s/I always do/I always do except this once when I forgot and then forgot
>>> that I forgot/g
>>>
>>>
>> This is why adding some options to make.conf is a good idea as you
>> already know.  I added -1 ages ago.  Why?  I would be trying to get a
>> update done and needed to do a few by hand and would forget the -1
>> option.  One can only imagine what the world file looked like.  lol 
>> Since I added -1 to make.conf, nothing has went into the world file that
>> I didn't add there on purpose.  Of course, one has to remember to use
>> --select y to add those new packages but in general, I may do that a few
>> times a year where I average updating about twice a week.  Plus, when
>> you do -a --depclean and it spits out the list, you will see it and slap
>> your forehead and then go add it if you really want to keep it around. 
>>
>> In all honesty, I can't imagine how a person can keep a Gentoo install
>> up to date without adding that or having a really crappy looking world
>> file.  ;-)
>>
>> I wonder why the -1 isn't there by default???  I would think it would be
>> a problem only when doing the initial install, when you want to add a
>> lot of packages to the world file since most likely, nothing is there. 
>> Just a thought. 
> -1 isn't there by default because the purpose of emerge is to build and
> install something, then remember you did it.
>
> What -1 does is build and install something then neglect to record you
> did it.
>
> -1 cannot ever possibly be a good default.
>
>


That's true but for the purpose I was speaking of, once your install is
done, most emerges then are either updates or trying to update doing one
package at a time, to avoid conflicts etc.  If I built a new rig and was
doing a fresh install, then I would want everything I install recorded
in the world file.  Once I get the install done and I'm to the point
that I'm mostly updating, I don't generally want individual packages
recorded. 

I see the point and during a install, no one would want that as a
default.  That's likely the reason it isn't. 

Dale

:-)  :-)