[driverloader] Building driver loader from sources fails for FC5 kernel 2.6.18 + exponentially growing modprobe.conf

[Linuxant support (Jonathan)]

Hi,

you mean that only saving the file with a text editor when the file 
contains trailing comments is enough to trigger the problem? If this is 
the case, then it's very unlikely DriverLoader which is making these 
changes. DriverLoader will only modify the file when:

1) DriverLoader was assigned to drive a new wireless device by the 
kernel, this generally happen when the DriverLoader module is inserted 
in the kernel in most cases.
2) When DriverLoader is uninstalled from the system.

Since most users are not affected by this problem and we never saw this 
problem on our systems, it is quite possible that this is a problem in a 
3rd party software which is either not part of Fedora Core or at least, 
not in the base install.

You could perhaps attempt to find the problematic software on your 
system with a SELinux rule for example.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com



Henrik Nilsson wrote:
> Ho Jonathan,
> 
>  > DriverLoader 2.34 is not compatible with 2.6.18 kernels. Patches to
>  > solve this issue can be installed with the 'dldrconfig --patch'
> 
> OK, thanks.
> 
>  > We have seen the problem you have reported with the 
> /etc/modprobe.conf > file in the dump provided by a few users. This 
> problem seems to be
>  > specific to Fedora Core and unfortunately, we were not able to
>  > reproduce this problem on our systems.
>  > ...
>  > It is also possible that this is another program which is the cause of
>  > the problem.
> 
> Indeed, maybe that's the most likely explanation!
> 
> I did a few experiments.
> 
> First, I removed all trailing comments from "/etc/modprobe.conf".
> Then the file does not grow when I save.
> 
> Then I changed the comment introduced by "dldrconfig".
> Whatever I changed it to got replicated when I saved.
> That probably means that the "dldrconfig" script is
> not the one that introduces extra stuff? At least not
> in any obvious way.
> 
> Finally, I added an empty trailing comment ("#") to each line in
> "/etc/modprobe.conf". After four saves, the result was the enclosed
> file. Thus, some comments do not grow, some grow linearly, and some
> exponentially! Very strange indeed!
> 
>  From this (e.g. taking the module names of the lines where comments
> grow into account), would you say that some other program rather
> than "dldrconfig" is likely to blame?
> 
> Best,
> 
> /Henrik
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> alias eth0 tg3 #
> alias snd-card-0 snd-intel8x0 #
> options snd-card-0 index=0 #  #  #  #  #
> options snd-intel8x0 index=0 #  #  #  #  #
> remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0 # # # # # # # # # # # # # # # #
> install bcm43xx /bin/true # # # # # # # # # # # # # # # #
> alias eth1 driverloader #
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader