[ARMedslack] Trouble with udev on busybox based system

2011-05-09 Thread Davide
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

Re: [ARMedslack] qemu raw image partition offset calculation

2011-05-09 Thread Stuart Winter
Yep this is all good stuff. ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/qemu-to-sheeva.txt I haven't digested everything you've put down but the above URL is how I bootstrapped armedslack onto the sheevaplug -- converting a qemu installation back to a bootable hard disk.

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

2011-05-09 Thread Davide
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:

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

2011-05-09 Thread Davide
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 louigi...@yahoo.it ha scritto: Da: Davide

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

2011-05-09 Thread 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 ---

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

2011-05-09 Thread Davide
Loking with more care at the verbose outout of udevd I found that things start to go wrong when this is issued: util_run_program: '/sbin/modprobe -v usb:v4586p1026d0050dc00dsc00dp00ic08isc06ip50' I tried at a command prompt and I get no error but also no module is loaded. I'm not actually sure