Up to 2.1.104 using built-in instead of modular sound drivers solved the
problem and everything worked fine. I suspected a configuration problem
and wondered whether the reorganisation of the sound system would solve
the problem. Instead, 2.1.105 made things worse: Now built-in drivers
expose the same problem.
Still, no initialisation errors.
The modular configuration used is:
#
# Sound
#
CONFIG_SOUND=m
CONFIG_SOUND_OSS=m
# CONFIG_SOUND_PAS is not set
CONFIG_SOUND_SB=m
CONFIG_SOUND_ADLIB=m
# CONFIG_SOUND_GUS is not set
# CONFIG_SOUND_MPU401 is not set
# CONFIG_SOUND_PSS is not set
# CONFIG_SOUND_MSS is not set
# CONFIG_SOUND_SSCAPE is not set
# CONFIG_SOUND_TRIX is not set
# CONFIG_SOUND_MAD16 is not set
# CONFIG_MAD16_OLDCARD is not set
# CONFIG_SOUND_CS4232 is not set
# CONFIG_SOUND_MAUI is not set
# CONFIG_SOUND_SGALAXY is not set
# CONFIG_SOUND_OPL3SA1 is not set
# CONFIG_SOUND_SOFTOSS is not set
CONFIG_SOUND_YM3812=m
# CONFIG_SOUND_VMIDI is not set
# CONFIG_SOUND_UART6850 is not set
#
# Additional low level sound drivers
#
# CONFIG_LOWLEVEL_SOUND is not set
for the built-in drivers tested, replace "m" by "y".
The corresponding output of /dev/sndstat is
OSS/Free:3.8s2++-971130
Load type: Driver loaded as a module
Kernel: Linux tos20.trin.cam.ac.uk 2.1.105 #5 Wed Jun 10 13:30:40 BST 1998 i586
Config options: 0
Installed drivers:
Card config:
Audio devices:
0: ESS ES1688 AudioDrive (rev 11) (3.1)
Synth devices:
Midi devices:
Timers:
0: System clock
Mixers:
0: Sound Blaster
Both the hardware and the configuration settings are unlikely to be at
fault since everything works flawlessly in 2.0.x and in 2.1.x, x < 105,
with built-in drivers.
Any suggestions where to start investigating the problem?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu