On Tuesday 17 December 2002 19:11, Elliott Martin wrote:
> Hello,
> I have just stumbled upon a bug in harddrake2 that I feel should be
> reported.
>
> I have harddrake-ui-9.1-0.3mdk installed, and when I open up the Module
> Configuration dialog for my Ensoniq ES1371 [AudioPCI-97] soundcard and
> enter a value for the joystick address, the address is added correctly as
> 'options joystick=0x200' to /etc/modules.conf, however if I open the same
> dialog again it does not read that line in from the modules.conf and if I
> do put anything in the joystick feild it is appended to the modules.conf
> (instead of overwriting that line).
>
> Thanks for all your work!
> -Elliott Martin
I hate having to reply to my own post, but these things must be done. The line
added to modules.conf, was not correct, as a matter of fact there is no
joystick option for the snd-ens1371 module (which I'm using). So there still
is a bug with harddrake2, it's just a little different from the one I
reported. This leads me to another point...
Is there anyway the whole endeavour of setting up a joystick in mandrake linux
could be simplified? The only way I could see to enable the gameport on my
sound card was to store the current alsa config to a file (`alsactl store -f
/etc/asound.state`), modify the part about the gameport being
disabled('control.1->value = true'), and then restore that config file so I
could load the ns558 module, then I could load the module for my joystick
(analog js=175003).
This all could be a little simpler if there was a 'default' alsa config file,
or if there was an existing asound.state file, which should get loaded each
time the alsa service starts (right?).
Maybe all that's really needed is some documentation on the procedure (which
I'm working on), because finding information about this is like finding a
needle in a haystack even with google on your side.
-Elliott
