It just seems to choke on that second module. I have to install the two modules for my joystick to function. It choked on joy-sidewinder.o, so I removed it and left joystick.o, which has to come first anyway. Now at boot it initialises that module right before isapnp and my daemons begin, and everything's cool. The boot message for the joystick initialization is: js: Version 1.2.7 using 0.83 MHz counter timer and 1.19 MHz PIT timer. I still have to "insmod joy-sidewinder.o" before I can use the joystick though. Here is the output from insertion of the second module: js0: SideWinder GamePad 2-axis 10-button joystick at 0x201 Odd, I wonder why it chokes on that second module at boot. I'm halfway there at least. Thanks for your assistance, I tried your advice, but I had less success than with boot.local. In boot.local I set up my IP accounting too. Currently in boot.local I have two lines that initialize my Ip accounting followed by one line initializing the joystick. I'm so close, it'll come, it has to be something really rudimentary. C. J. Kenneth Tan wrote:

Michael,

You mean you can manually type in the commands after login and it will be fine? If that is true, I don't see why you can't do it the way I told you. The thing is, if you put it into /sbin/init.d/boot.local, the command will be executed before anything else in /sbin/init.d/rc*.d . So if there are anything that has to be set prior to inserting the module for the joystick, it will not work if you put the commands into /sbin/init.d/boot.local . Executing a command from a script is no different than executing from command line.

-- ==================================================================== Michael Lankton <A HREF="http://tasteslikechicken.ml.org"><A HREF="http://tasteslikechicken.ml.org</A">http://tasteslikechicken.ml.org</A</A>> ==================================================================== - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e