On Saturday 24 April 2010 11:37:26 Katharina Haselhorst wrote: > > you have to deal with udev (external of busybox) or mdev (inside busybox) > > to load the module required by your hardware. > > I started udevd and issued a udevadm trigger and a udevadm settle. After > that, I get a eth0 device, as expected. But as I mentioned above, I > can't work with that interface. Which kernel module do I need? Atm I > don't have any modules included in the initramfs, but that's easy to > change.
When it's up, go: ls -l /sys/class/net/eth0/device/driver That symlink should point to a directory with the same name as the kernel module that's currently driving the device. (Once you know it, you can just insmod the sucker in a shell script or something, you only need the other stuff to probe sysfs and autodetect hardware you have modules for.) Rob -- Latency is more important than throughput. It's that simple. - Linus Torvalds _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
