[ARMedslack] R: R: R: Trouble with udev on busybox based system

[Davide]

Ok that got some module loading working automatically:
the ethernet nic now comes up correctly at boot time and some usb stuff is also activated.
But when I plug in a usb storage stick the device file does not get cteated and not all the modules get pulled in.

Any ideas ?

Regards
David
 

--- Lun 9/5/11, Davide <louigi600 at yahoo.it> ha scritto:

> Da: Davide <louigi600 at yahoo.it>
> Oggetto: [ARMedslack] R:  R:  Trouble with udev on busybox based system
> A: "Slackware ARM port" <armedslack at lists.armedslack.org>
> Data: Lunedì 9 maggio 2011, 08:42
> Could not grep modprobe in the udev
> scripts nor in the binary (with the aid of strings) ... so I
> looked in the rules.d and there it was.
> 
> But busybox modprobe does not support blacklists ... hope
> it won't hurt.
> 
> Regards
> David
> 
> --- Lun 9/5/11, Davide <louigi600 at yahoo.it>
> ha scritto:
> 
> > Da: Davide <louigi600 at yahoo.it>
> > Oggetto: [ARMedslack] R:  Trouble with udev on
> busybox based system
> > A: "Slackware ARM port" <armedslack at lists.armedslack.org>
> > Data: Lunedì 9 maggio 2011, 08:32
> > Ok ... I started udevd with --debug
> > and dumped stderr to somewhere I could read it. This
> is what
> > came out (the intresting part):
> > 5584.430610 [1032] udev_rules_apply_to_event: RUN
> > '/sbin/modprobe -bv $env{MODA
> > LIAS}' /lib/udev/rules.d/80-drivers.rules:5
> > 5584.430746 [1032] util_run_program: '/sbin/modprobe
> -bv
> > usb:vFFEEp0100d0100dc0
> > 0dsc00dp00ic08isc06ip50' started
> > 5584.435842 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) '/sbin/modprobe:
> >  invalid option -- 'b''
> > 5584.459928 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) 'BusyBox v1.18.4
> >  (2011-04-20 14:04:26 BST)'
> > 5584.460090 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) ' multi-call bin
> > ary.'
> > 5584.460178 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) ''
> > 5584.460204 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) 'Usage: '
> > 5584.460278 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) 'modprobe'
> > 5584.460379 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) ' '
> > 5584.460464 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) '[-qfwrsv] MODUL
> > E [symbol=value]...'
> > 5584.460489 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) ''
> > 5584.460509 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) 'Options:'
> > 5584.460530 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) '        -r
> >         Remove MODULE (stacks) or do
> > autoclean'
> > 5584.460550 [1032] util_run_program: '/sbin/modprobe'
> > (stderr) '        -q
> > 
> > It looks like udev is modprobing with options busybox
> > modprobe does not understand.
> > 
> > Is this stuff hard coded in the source or is it in
> some
> > script ?
> > 
> > Regards
> > David
> > 
> > --- Lun 9/5/11, Davide <louigi600 at yahoo.it>
> > ha scritto:
> > 
> > > Da: Davide <louigi600 at yahoo.it>
> > > Oggetto: [ARMedslack] Trouble with udev on
> busybox
> > based system
> > > A: armedslack at lists.armedslack.org
> > > Data: Lunedì 9 maggio 2011, 07:41
> > > Ok this is a little off topic but
> > > since I'm trying to make it look as close as
> possible
> > to a
> > > slackware system I thaught it could fit here
> anyway.
> > > 
> > > Although I did my best to adapt all the scripts
> > around
> > > /etc/rc.d and /lib/udev to work correctly with
> busybox
> > (sh
> > > and slightly different PATH): udev is not doing
> it's
> > work
> > > correctly.
> > > 
> > > udevd start apparently correctly but none of the
> > modules
> > > that should be loaded automatically actually get
> > loaded.
> > > For instance in order to see the Ethernet nic
> I;ve to
> > load
> > > manually mv643xx_eth, or if I want to use a usb
> flash
> > stick
> > > I've to do quite a bit of manual module loading.
> > > Having a look at armedslack's rc.modules I see
> that
> > > basically it's empty as far as dockstar is
> concerned
> > so all
> > > the modules do get auto loaded correctly.
> > > No as far as kernel is concerned I'm using the
> exact
> > same
> > > setup on the busybox environment that is on the
> > armedslack
> > > miniroot system on onboard flash (I stopped using
> the
> > kernel
> > > I compiled) and both boot without initrd so no
> module
> > > loading can be done by initrd.
> > > 
> > > Anyone have any idea how I could go about
> debugging
> > this
> > > issue ? or even better have any idea howto fix it
> ?
> > > 
> > > Regards
> > > David
> > > _______________________________________________
> > > ARMedslack mailing list
> > > ARMedslack at lists.armedslack.org
> > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > > 
> > _______________________________________________
> > ARMedslack mailing list
> > ARMedslack at lists.armedslack.org
> > http://lists.armedslack.org/mailman/listinfo/armedslack
> > 
> _______________________________________________
> ARMedslack mailing list
> ARMedslack at lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>