On Monday 03 May 2010 02:45:39 Katharina Haselhorst wrote: > Hello, > > On 04/27/2010 06:50 AM, Rob Landley wrote: > > 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.) > > It seems to be a xen related problem. I tried the same setting with a > different xen version and everything works without problems. Thx, for > your ideas, I'll look at it and see if I can solve the issue on the > other xen version as well. > > K. Haselhorst
I've had better luck with KVM, but I'm aware people don't always get to choose... 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
