Re: Depmod errors on 2.6.17.4/2.6.18-rc1/2.6.18-rc1-mm1

["Antonino A. Daplas" <adaplas@gmail.com>]

Matt Reuther wrote:
> On Monday 10 July 2006 11:58 am, Antonino A. Daplas wrote:
>> Matt Reuther wrote:
>>> Quoting "Antonino A. Daplas" <adaplas@gmail.com>:
>>>> CONFIG_FB=n, CONFIG_BACKLIGHT_CLASS_DEVICE=m should not be possible in
>>>> 2.6.18-rc1-mm1 and 2.6.18-rc1.  Can you run kconfig again?
>>>>
>>>> Tony
>>> I am not at the computer right now, but I will try later.
>>>
>>> Here is how I got config-2.6.18-rc1-mm1. I copied this config from
>>> 2.6.18-rc1, which I had created with 'make menuconfig'. I ran 'make
>>> oldconfig' on the config-2.6.18-rc1 and answered the new questions to
>>> generate config-2.6.18-rc1-mm1. I compiled it from there. Does 'make
>>> oldconfig' not work properly anymore?
>> I really don't know.  I have received several bug reports where the
>> main cause was that a kconfig option changed after upgrading kernels.
>>
>> I tested with make menuconfig, and it's not possible to set lcd/backlight
>> options if CONFIG_FB is not set.
>>
>> Tony
> 
> I ran 'make menuconfig' and I got the same warnings. Perhaps CONFIG_FB needs 
> to be part of the 'selects' line for any option that selects the backlight 
> support. I think the USB Apple Cinema display support, which I set as 
> modular, might have selected backlight. I don't need framebuffer support, so 
> I have that shut off. Here are the depmod warnings once again:

Yes, that's the culprit.  I've been thinking for some time to eliminate
the framebuffer dependency from lcd/backlight.  Can you try the patch I sent
in another thread?

Tony