From: Martin on
Clemens Ladisch wrote:

> Kurt Kehler wrote:
>> On Tue, 06 Apr 2010 13:13:47 +0200, Clemens Ladisch <clemens(a)ladisch.de>
>> wrote:
>> > The snd-hda-intel driver should log some error message when it does not
>> > attach to the device. Kurt, plase look at the end of the output of
>> > "dmesg" after running "rmmod snd-hda-intel; modprobe snd-hda-intel".
>>
>> I tried "rmmod snd-hda-intel; modprobe snd-hda-intel" and it made
>> no change in dmesg's output.
>
> This indicates that the driver doesn't even try to attach to the
> device. Since the device is there, according to lspci, this means
> that some other driver has grabbed it.
>
>> I have added linuxant's driver to make a Conexant Systems, HSF
>> softmodem work with linux.
>
> The hardware of softmodems is a cheap 8 kHz sound card that uses the
> same interface as normal onboard sound cards. However, a proper
> softmodem driver would not try to attach to normal devices; it should
> be possible to configure it to ignore your sound device.
>
>> Disabling the modem software didn't bring the sound back.
>
> It's likely that the softmodem driver did not get removed.
>
>
> Regards,
> Clemens

Btw, lspci has an option -k that should tell you which module has attached
to a PCI device.

Martin

From: Kurt Kehler on
On Wed, 07 Apr 2010 20:52:09 +0200, Martin <no(a)spam.invalid> wrote:
> Clemens Ladisch wrote:
>
>> Kurt Kehler wrote:
>>> On Tue, 06 Apr 2010 13:13:47 +0200, Clemens Ladisch <clemens(a)ladisch.de>
>>> wrote:
>>> > The snd-hda-intel driver should log some error message when it does not
>>> > attach to the device. Kurt, plase look at the end of the output of
>>> > "dmesg" after running "rmmod snd-hda-intel; modprobe snd-hda-intel".
>>>
>>> I tried "rmmod snd-hda-intel; modprobe snd-hda-intel" and it made
>>> no change in dmesg's output.
>>
>> This indicates that the driver doesn't even try to attach to the
>> device. Since the device is there, according to lspci, this means
>> that some other driver has grabbed it.
>>
>>> I have added linuxant's driver to make a Conexant Systems, HSF
>>> softmodem work with linux.
>>
>> The hardware of softmodems is a cheap 8 kHz sound card that uses the
>> same interface as normal onboard sound cards. However, a proper
>> softmodem driver would not try to attach to normal devices; it should
>> be possible to configure it to ignore your sound device.
>>
>>> Disabling the modem software didn't bring the sound back.
>>
>> It's likely that the softmodem driver did not get removed.
>>
>>
>> Regards,
>> Clemens
>
> Btw, lspci has an option -k that should tell you which module has attached
> to a PCI device.
>
> Martin

Thanks Clemens and Martin. This helped. I got the audio to work
by uninstalling the linuxant hsfmodem and rebooting. I'd like
to be able to eliminate the rebooting.

I've edited 'lspci -k' to show only the audio device and the modem.

After 'make install' and rebooting sound does not work:

lspci -k
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
03:00.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem
Kernel driver in use: hsfpcibasic2
Kernel modules: hsfpcibasic2

After 'make uninstall' and reboot sound works:

00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
03:00.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem

After 'make install', reboot, 'make uninstall', there is still no sound
but a kernel module has appeared:

00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
Kernel modules: snd-hda-intel
03:00.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem

lspci shows the kernel module for the audio device, but not the
kernel driver. Is it possible to force the kernel driver 'HDA
Intel' to load without having to reboot?

I've tried 'modprobe snd-hda-intel' with no luck.

Thanks,
Kurt Kehler
kmk at pa dot net
From: Clemens Ladisch on
Kurt Kehler wrote:
> [...]
> After 'make install', reboot, 'make uninstall', there is still no sound
> but a kernel module has appeared:
>
> 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
> Kernel modules: snd-hda-intel
> 03:00.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem
>
> lspci shows the kernel module for the audio device, but not the
> kernel driver. Is it possible to force the kernel driver 'HDA
> Intel' to load without having to reboot?
>
> I've tried 'modprobe snd-hda-intel' with no luck.

Try rmmod first to force it to load again.

If the kernel thinks that this is the right module and if the driver is
loaded, if should try to attach to the device. If that fails, there
should be an error message in the log.

If rebooting helps, it's likely that the hsfpcibasic2 driver changes the
audio device's configuration. However, it might be possible to tell the
snd-hda-intel driver to initialize its device properly.


Regards,
Clemens
From: Kurt Kehler on
On Fri, 16 Apr 2010 09:27:46 +0200, Clemens Ladisch <clemens(a)ladisch.de> wrote:
> Try rmmod first to force it to load again.
>
> If the kernel thinks that this is the right module and if the driver is
> loaded, if should try to attach to the device. If that fails, there
> should be an error message in the log.
>
> If rebooting helps, it's likely that the hsfpcibasic2 driver changes the
> audio device's configuration. However, it might be possible to tell the
> snd-hda-intel driver to initialize its device properly.

I found a solution. The driver comes with a shell script called
hsfconfig, which must be run after 'make install' to complete
the installation.

hsfconfig asks:
Would you like to use the replacement HDA modules? [yes]

I typed 'no' and all is fine, the audio survives a reboot.
Previously I had always selected the default 'yes' option.

hsfconfig also has (among others) these options:
-r, --remove Remove serial devices and kernel modules
-k, --kernel Build and install kernel modules
-s, --serial Install serial port devices

By playing with these, rmmod'ing all the sound modules
and rerunning /etc/rc.d/rc.alsa it is possible to make
the audio work even if you answer 'yes' to the above.

Thanks for you help.

Kurt