Hide Forgot
sndconfig fails when using the card ESS ES1869 PNP AudioDrive. The sound example is played correctly, but when trying to play the MIDI demo, the following error is displayed: The following error occurred running the modprobe program: /lib/modules/2.4.0-0.43.6/kernel/drivers/sound/opl3.o: init_module: No such device /lib/modules/2.4.0-0.43.6/kernel/drivers/sound/opl3.o: insmod /lib/modules/2.4.0-0.43.6/kernel/drivers/sound/opl3.o failed /lib/modules/2.4.0-0.43.6/kernel/drivers/sound/opl3.o: insmod midi failed sndconfig then says that automatic configuration failed, dropping me to manual configuration. Did choose ESS ES1868 there (1869 isn't listed) and did try various hardware settings, bot none worked.
This defect is considered MUST-FIX for Florence Gold release
What's your /etc/modules.conf look like?
*** Bug 23377 has been marked as a duplicate of this bug. ***
*** Bug 26860 has been marked as a duplicate of this bug. ***
Apparent kernel bug; the opl3 driver refuses to load, even with the correct parameters.
Arjan, if this is trivial and obvious to you, please fix it. Otherwise, assign it back to me and I'll hunt around for hardware and figure out who needs to work on it.
This is non-trivial. The midi paths in the 2.4 kernel are not well tested and several drivers are known broken with it. Will hunt for more info.
(goes and pokes at a machine with an SB16 with the same problem) It *appears* it's some sort of bizarre interaction with the isapnp support and initialization, and whether soundcore is loaded, and whether sound is loaded, and whether you ran isapnp, or used the kernel's isapnp code, or specified module parameters, and this is just really screwed up.
It *appears* that what's wrong here is that the sb driver, on unload, deactivates the isapnp configuration, so the IO port for the opl3 isn't active. Without running userspace isapnp tools, the only time you can load the opl3 module is while the sb module is loaded.
patch posted internally, waiting for comments.
*** Bug 29948 has been marked as a duplicate of this bug. ***
This is worked around in sndconfig-0.64.5-1; it will no longer cause this error.