Package: busybox-cvs-udeb Severity: normal Tags: d-i The busybox insmod seems to be failing to pass module parameters into the kernel, either with d-i's 2.4.25 (where I have to explicitly tell tulip to use 10BaseT for my network card) or with my main system's 2.4.26.
Here is an example (the loop module gives a simple log message telling us what parameter it received - 8 being the default): [EMAIL PROTECTED]:/lib/modules/2.4.26/kernel/drivers/block# /sbin/insmod loop.o max_loop=12 [EMAIL PROTECTED]:/lib/modules/2.4.26/kernel/drivers/block# tail -n 1 /var/log/syslog Apr 23 20:17:47 henry kernel: loop: loaded (max 12 devices) [EMAIL PROTECTED]:/lib/modules/2.4.26/kernel/drivers/block# rmmod loop [EMAIL PROTECTED]:/lib/modules/2.4.26/kernel/drivers/block# /home/l4545/src/debian-installer/trunk/installer/build/tmp/floppy/root/tree/sbin/insmod loop.o max_loop=12 Using loop.o [EMAIL PROTECTED]:/lib/modules/2.4.26/kernel/drivers/block# tail -n 1 /var/log/syslog Apr 23 20:17:55 henry kernel: loop: loaded (max 8 devices) [EMAIL PROTECTED]:/lib/modules/2.4.26/kernel/drivers/block# rmmod loop busybox-cvs 20040408-1 works fine. -- Martin Orr Linux Administrator, Methodist College Belfast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
