snd-ice1712: no sound if SPDIF is unplugged

[ktulu77]

Hi, I am on ubuntu jaunty x64 with all updates installed.

I have installed a M-Audio Audiophile 24/96 on my computer.

I have no sound with it if SPDIF is unplugged.
If I try to launch gnome-sound-properties, it hangs and I have don't have the speaker icon on my dashboard.

As you can see in comment 5 the bug affetc -generic and -rt kernels.

This is a piece of my syslog.

Thank you

[Alessio Igor Bogani (abogani)]

@ktulu77,

Using lspci -v could you report exactly what is the kernel driver involved?

Thanks!

[ktulu77 (ktulu-highwaytoacdc)]

I have done some other tests, it seems random, now, I have also this problem on generic kernel.
The sound works for example when I launch rhythmbox.

But I still don't have the sound icon in my dashboard (even if I add a new one on it) and the gnome-sound-properties is still hanging.

I have tried to remove the .pulse folder of my personnal folder. Is there some other files I need to remove to reset audio configuration ? (Even if I have not touch it before).

lspci -v :
01:09.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02)
 Subsystem: VIA Technologies Inc. Device d634
 Flags: bus master, medium devsel, latency 32, IRQ 19
 I/O ports at ac00 [size=32]
 I/O ports at a800 [size=16]
 I/O ports at a400 [size=16]
 I/O ports at a000 [size=64]
 Capabilities: <access denied>
 Kernel driver in use: ICE1712
 Kernel modules: snd-ice1712

[Alessio Igor Bogani (abogani)]

@ktulu77,

Please could you test mainline version as reported in https://wiki.ubuntu.com/KernelMainlineBuilds ?

Thanks!

[ktulu77 (ktulu-highwaytoacdc)]

Ok, I have found the cause of the problem : I had no sound when my instrument was NOT plugged in the SPDIF socket or if my instrument was not turned-on. (This is what it seemed to be a random bug)

Very strange, if I turned-on my instrument, I had sound and all was fine. I tried to uninstall pulseaudio but It was the same.

I have done a new fresh install from jaunty x64 beta and this problem is gone.

Anyway I still don't understand why I had no sound if nothing was plugged in the SPDIF socket. The opposite would have been more logical.

Thanks

[Alessio Igor Bogani (abogani)]

This bug affect also -generic.

[ktulu77 (ktulu-highwaytoacdc)]

Ok, I am still with my last install of ubuntu, yesterday, I have tried to use the jackd server, I have done some changes in the gnome sound manager, and now, the problem is back !

If I don't turn on the instrument plugged in the SPDIF-IN, I have no sound.

I think this problem can be related to the alsa driver, because the only changes I maid is to add my user to the disk group, and change some settings in the gnome volume manager.

I don't think this problem is from pulseaudio.

I will try as soon as possible the test mainline version of the kernel.

[ktulu77 (ktulu-highwaytoacdc)]

I have tried with the kernel mainline version, the problem is still here.

[ktulu77 (ktulu-highwaytoacdc)]

I don't find what I have changed to have the bug reappear. I have no sound when GDM start before I open my session, so I don't think this is a problem related to my personal settings.

I have tried to remove pulseaudio, the problem is still here.

This is the last actions I did when the problem appeared :

sudo gedit /etc/security/limits.conf
sudo adduser theo audio
sudo adduser theo disk

And this is the history of my synaptic from this same period :

04/05/2009

following packages updated :
acpid (1.0.6-9ubuntu4.9.04.2) to 1.0.6-9ubuntu4.9.04.3
bluetooth (4.32-0ubuntu4) to 4.32-0ubuntu4.1
bluez (4.32-0ubuntu4) to 4.32-0ubuntu4.1
bluez-alsa (4.32-0ubuntu4) to 4.32-0ubuntu4.1
bluez-cups (4.32-0ubuntu4) to 4.32-0ubuntu4.1
bluez-gstreamer (4.32-0ubuntu4) to 4.32-0ubuntu4.1
bluez-utils (4.32-0ubuntu4) to 4.32-0ubuntu4.1
checkbox (0.7.1) to 0.7.2
checkbox-gtk (0.7.1) to 0.7.2
consolekit (0.3.0-2ubuntu3) to 0.3.0-2ubuntu4
cups (1.3.9-17ubuntu2) to 1.3.9-17ubuntu3
cups-bsd (1.3.9-17ubuntu2) to 1.3.9-17ubuntu3
cups-client (1.3.9-17ubuntu2) to 1.3.9-17ubuntu3
cups-common (1.3.9-17ubuntu2) to 1.3.9-17ubuntu3
evolution-exchange (2.26.0-0ubuntu2) to 2.26.0-0ubuntu3
libbluetooth3 (4.32-0ubuntu4) to 4.32-0ubuntu4.1
libck-connector0 (0.3.0-2ubuntu3) to 0.3.0-2ubuntu4
libcups2 (1.3.9-17ubuntu2) to 1.3.9-17ubuntu3
libcupsimage2 (1.3.9-17ubuntu2) to 1.3.9-17ubuntu3
libpam-ck-connector (0.3.0-2ubuntu3) to 0.3.0-2ubuntu4
libudev0 (141-1) to 141-1.1
libvolume-id1 (141-1) to 141-1.1
libwmf0.2-7 (0.2.8.4-6ubuntu1) to 0.2.8.4-6ubuntu1.1
libwmf0.2-7-gtk (0.2.8.4-6ubuntu1) to 0.2.8.4-6ubuntu1.1
ubuntu-docs (9.04.9) to 9.04.10
udev (141-1) to 141-1.1
update-manager (1:0.111.8) to 1:0.111.9
update-manager-core (1:0.111.8) to 1:0.111.9

following packages installed :
ardour (1:2.7.1-2ubuntu1)
libaubio2 (0.3.2-2ubuntu3)
libgnomecanvasmm-2.6-1c2a (2.23.1-1)
liblo0ldbl (0.23-2.2)
libvamp-hostsdk2 (1.3-1)
libvamp-sdk1 (1.3-1)
python-crypto (2.0.1+dfsg1-2.3ubuntu5)
python-twisted (8.2.0-2)
python-twisted-conch (1:8.2.0-2)
python-twisted-lore (8.2.0-0ubuntu1)
python-twisted-mail (8.2.0-2)
python-twisted-names (8.2.0-0ubuntu1)
python-twisted-news (8.2.0-2)
python-twisted-runner (8.2.0-0ubuntu1)
python-twisted-words (8.2.0-2)
gstreamer0.10-gnonlin (0.10.10-2)
jokosher (0.11.1-0ubuntu1)
python-setuptools (0.6c9-0ubuntu4)

05/05/2009
following packages installed :
boinc-client (6.2.18-3ubuntu1)
boinc-manager (6.2.18-3ubuntu1)

Do you have an idea where I cant investigate this problem ?

[ktulu77 (ktulu-highwaytoacdc)]

I have finally found the problem :

In gnome volume manager, I had set "Multi Track Internal Clock" to IEC958 Input.
I have change that value to 44100 and now, all is ok.

Perhaps, this could help someone ...

[penalvch (penalvch)]

ktulu77, this bug report is being closed due to your last comment regarding this being a configuration issue. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.