Re: [alsa-devel] Testers wanted: New SB X-Fi driver
At Thu, 16 Jul 2009 12:19:15 +0200, Frashman wrote:
Takashi Iwai schrieb:
At Wed, 15 Jul 2009 12:55:23 +0200, Frashman wrote:
Hi Takashi,
first of all, thank you for developing this driver. I tested it today. It works, so far.
But two annoying things. As you mentioned, I got problems, if the onboard sound modules are loaded. Then i get no sound out auf my xfi.
It's likely the collision of PCI device ID. Some X-Fi models support both HD-audio and emu20kx-native modes. The modes are switched by some magical sequence.
Anyway, please run alsa-info.sh with --no-upload option, and attach the generated file.
I let the kernel auto probe all sound modules and generated then the alsa-info.txt It's attached.
The PCI ID looks different from what snd-hda-intel driver supports. When compiled together with snd-ctxfi, snd-hda-intel only probes PCI ID 1002:0009.
Are you sure that it's hda-intel that interferes the xfi? Any relevant kernel messages or asound entry when this happens?
Takashi
Hi
Got it, there was a wrong default entry in /etc/modprobe.d/50-sound.conf ..made by alsaconf
alias snd-card-0 snd-ctxfi alias sound-slot-0 snd-ctxfi
moved it now to /etc/modprobe.d/modprobe.conf and chanced to:
alias snd-card-0 snd_ctxfi alias sound-slot-0 snd_ctxfi
now it's fine ... so ... no conflict ... sorry. but maybe someone could look, why alsaconf had done this.
The PCI ID looks different from what snd-hda-intel driver supports. When compiled together with snd-ctxfi, snd-hda-intel only probes PCI ID 1002:0009.
Are you sure that it's hda-intel that interferes the xfi? Any relevant kernel messages or asound entry when this happens?
Takashi
Found another problem ... maybe it isn't a bug ...
If I raise all volumes in alsamixer to 100% it starts to crackle while playing music ... If I lower one of the mixer volumes down to 90% it's fine. Maybe it's just overdriven ... but I'm relative sure, in windows I can gain everything to 100% without to be overdriven.
For now, I've set the PCM volume control to 90%, then I can do whatever I want with the master volume ;-)
Greetings Frank
At Mon, 20 Jul 2009 20:47:55 +0200, Frank Roth wrote:
Hi
Got it, there was a wrong default entry in /etc/modprobe.d/50-sound.conf ..made by alsaconf
alias snd-card-0 snd-ctxfi alias sound-slot-0 snd-ctxfi
moved it now to /etc/modprobe.d/modprobe.conf and chanced to:
alias snd-card-0 snd_ctxfi alias sound-slot-0 snd_ctxfi
now it's fine ... so ... no conflict ... sorry. but maybe someone could look, why alsaconf had done this.
The former file name is the requirement by the recent module-init-tools. The question is rather why it doesn't work on your system. Maybe modprobe.d/* itself doesn't work?
Anyway, alsaconf is nowadays no longer recommended. It's good for detecting some very old ISA devices without PnP, but not for other normal devices.
Takashi
The PCI ID looks different from what snd-hda-intel driver supports. When compiled together with snd-ctxfi, snd-hda-intel only probes PCI ID 1002:0009.
Are you sure that it's hda-intel that interferes the xfi? Any relevant kernel messages or asound entry when this happens?
Takashi
Found another problem ... maybe it isn't a bug ...
If I raise all volumes in alsamixer to 100% it starts to crackle while playing music ... If I lower one of the mixer volumes down to 90% it's fine. Maybe it's just overdriven ... but I'm relative sure, in windows I can gain everything to 100% without to be overdriven.
For now, I've set the PCM volume control to 90%, then I can do whatever I want with the master volume ;-)
Greetings Frank
participants (2)
-
Frank Roth -
Takashi Iwai