Re: busybox modprobe does not respect /etc/modprobe.d/ entries

Hi;

On So, 2020-09-13 at 22:03 +0200, Erich Titl wrote:
> Am 13.09.2020 um 14:15 schrieb KP Kirchdoerfer via leaf-devel:
> > Hi Erich;
> > 
> > On Do, 2020-09-10 at 15:42 +0200, Erich Titl wrote:
> > > Hi Folks
> > > 
> > > I found a rather unpleasant behaviour in busybox's modprobe. It
> > > appears
> > > not to respect 'install' lines in files in /etc/modprobe.d.
> > 
> > Indeed a limitation of busybox AFAIK.
> > 
> > > This is annoying in the case of the module leds_gpio which may
> > > depend
> > > on
> > > the underlying gpio driver, but which is not depending on it in
> > > modules.dep (it cannot know what the dependency could be).
> > > 
> > > Ideas?
> > 
> > I usually add such "missing/unkown" modules in /etc/modules
> 
> Unfortunately this does not do the job because leds_gpio is loaded
> automagically _before_ the underlying driver gets loaded. I testet
> this
> with an ALIX board.
> 
> The way to fix this is to rmmod leds_gpio and modprobe leds_gpio.
> With a
> _real_ modprobe this could be configured if this _real_ modprobe was
> available it init.

Ok,

what module is missing?

According to kernel documentation GPIO_CS5535 & LEDS_GPIO needs to be
loaded.
Looking at my old ALIX box with 4.14 kernel I see

gpio_cs5535 16384 3 - Live 0xb885c000
leds_gpio 16384 0 - Live 0xb889a000

detected by hwdetect without any changes elsewhere.

Though I've never tested to play with the LEDs on this box.
What's the output of lsmod on your box?

And what's going wrong?

kp

> cheers
> 
> ET
>