2012/5/15 Colin Guthrie <[email protected]>: > 'Twas brillig, and Simple . at 15/05/12 14:30 did gyre and gimble: >> 2012/5/15 Simple . <[email protected]>: >>> 2012/5/15 Pascal Terjan <[email protected]>: >>>> On Tue, May 15, 2012 at 2:23 PM, Simple . <[email protected]> wrote: >>>>> 2012/5/15 Colin Guthrie <[email protected]>: >>>>>> 'Twas brillig, and Simple . at 14/05/12 12:05 did gyre and gimble: >>>>>>> Hi, >>>>>>> >>>>>>> In boot i always get this: >>>>>>> >>>>>>> udevd[206]: Error running install command for sdhci_pci >>>>>>> >>>>>>> When entering /etc/modprobe.preload i saw that there was 2 sdhci_pci >>>>>>> entries, that was strange, anyway i did erase one entry and put the >>>>>>> other as a comment. >>>>>>> But that did not make any difference, since the entry sdhci_pci was >>>>>>> added again 2 times, and i continue getting the same error in boot. >>>>>>> >>>>>>> How can this be fixed? >>>>>> >>>>>> modprobe.preload* is not an "install rule". >>>>>> >>>>>> You have to look in /etc/modprobe.d/* for install rules. >>>>> >>>>> its in /etc/modprobe.d/01_mga-config.conf thats a symlink to >>>>> /etc/modprobe.conf >>>>> >>>>> but the problem is that it fails to install. >>>> >>>> Install is a command to run when loading the module, which is in a >>>> configuration file >>>> That command is failing >>>> You need to report what is the command >>> >>> install sdhci_pci /sbin/modprobe --first-time --ignore-install >>> sdhci_pci && { /sbin/modprobe mmc_block; /bin/true; } > > Yup that's the interesting bit. > >> i didnt paste the entire output: >> >> ~]# install sdhci_pci /sbin/modprobe --first-time --ignore-install >> sdhci_pci && { /sbin/modprobe mmc_block; /bin/true; } >> install: unrecognized option '--first-time' > > No, you do not "run" that command. It's a syntax that it's understood by > modprobe during module insertion. The actual command line utility > "install" is totally different. > > > > I'd just remove the --first-time option. > > Having rules that use --first-time is actually kinda tricky anyway as it > causes the second part of the install rule to not run if the first > module is loaded, but this can report incorrect status back up the stack. > > I'd just use: > install sdhci_pci /sbin/modprobe --ignore-install sdhci_pci && { > /sbin/modprobe mmc_block; /bin/true; } > > > I don't think our tools add this to the file, so this looks like some > kind of customisation on your part anyway.
There is NOT no customization on my part.
