(In reply to comment #14)
> As far as I remember in this distro (sarge) there was a file /etc/modprobe.conf
There should not have been. I assume that you created the file.
Normally you should not create an /etc/modprobe.conf file. If it
is present then modprobe ignores all the files in /etc/modprobe.d/.
> (not present anymore on hoary) in which I included the line options snd-via82xx
> dxs_support=4 because without this the sound was cracking.
It seems that the /etc/modprobe.conf file that you created fixed
the problem. That means that /etc/modprobe.d/alsa-base actually
inhibits the loading of snd-seq.
What happens if you _temporarily_ creat an /etc/modprobe.conf file
like the one that you had in sarge?
(In reply to comment #14)
> As far as I remember in this distro (sarge) there was a file /etc/modprobe.conf
There should not have been. I assume that you created the file.
Normally you should not create an /etc/modprobe.conf file. If it
is present then modprobe ignores all the files in /etc/modprobe.d/.
> (not present anymore on hoary) in which I included the line options snd-via82xx
> dxs_support=4 because without this the sound was cracking.
It seems that the /etc/modprobe.conf file that you created fixed d/alsa- base actually
the problem. That means that /etc/modprobe.
inhibits the loading of snd-seq.
What happens if you _temporarily_ creat an /etc/modprobe.conf file
like the one that you had in sarge?