saa7134-alsa appears to be broken

saa7134-alsa appears to be broken

[P. van Gaans]

On my Asus P7131 (DVB-T+analog+radio) I can't listen to FM radio anymore 
with a recent v4l-dvb or multiproto. If I go back to the v4l-dvb that 
comes with the kernel (2.6.24-19) I do get sound. Not completely without 
problems, have to restart aplay/arecord now and then but at least it 
works. With the recent v4l-dvb/multiproto it doesn't work at all.

dmesg has something to say (took out the interesting part):

[   31.155028] saa7133[0]: registered device video0 [v4l2]
[   31.155043] saa7133[0]: registered device vbi0
[   31.155055] saa7133[0]: registered device radio0
[   31.247453] saa7134_alsa: disagrees about version of symbol 
saa7134_tvaudio_setmute
[   31.247457] saa7134_alsa: Unknown symbol saa7134_tvaudio_setmute
[   31.247542] saa7134_alsa: disagrees about version of symbol 
saa_dsp_writel
[   31.247544] saa7134_alsa: Unknown symbol saa_dsp_writel
[   31.247808] saa7134_alsa: disagrees about version of symbol 
saa7134_dmasound_init
[   31.247809] saa7134_alsa: Unknown symbol saa7134_dmasound_init
[   31.247884] saa7134_alsa: disagrees about version of symbol 
saa7134_dmasound_exit
[   31.247886] saa7134_alsa: Unknown symbol saa7134_dmasound_exit
[   31.248165] saa7134_alsa: disagrees about version of symbol 
saa7134_set_dmabits
[   31.248167] saa7134_alsa: Unknown symbol saa7134_set_dmabits
[   31.320315] DVB: registering new adapter (saa7133[0])

I don't know if this also causes my problem but it possibly does. The 
saa7134 audio device is not recognized at all.

And yes, I have the firmware (required for DVB-T so irrelevant but 
anyway) installed.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: saa7134-alsa appears to be broken

[P. van Gaans]

On 07/26/2008 09:28 PM, P. van Gaans wrote:
> On my Asus P7131 (DVB-T+analog+radio) I can't listen to FM radio anymore 
> with a recent v4l-dvb or multiproto. If I go back to the v4l-dvb that 
> comes with the kernel (2.6.24-19) I do get sound. Not completely without 
> problems, have to restart aplay/arecord now and then but at least it 
> works. With the recent v4l-dvb/multiproto it doesn't work at all.
> 
> dmesg has something to say (took out the interesting part):
> 
> [   31.155028] saa7133[0]: registered device video0 [v4l2]
> [   31.155043] saa7133[0]: registered device vbi0
> [   31.155055] saa7133[0]: registered device radio0
> [   31.247453] saa7134_alsa: disagrees about version of symbol 
> saa7134_tvaudio_setmute
> [   31.247457] saa7134_alsa: Unknown symbol saa7134_tvaudio_setmute
> [   31.247542] saa7134_alsa: disagrees about version of symbol 
> saa_dsp_writel
> [   31.247544] saa7134_alsa: Unknown symbol saa_dsp_writel
> [   31.247808] saa7134_alsa: disagrees about version of symbol 
> saa7134_dmasound_init
> [   31.247809] saa7134_alsa: Unknown symbol saa7134_dmasound_init
> [   31.247884] saa7134_alsa: disagrees about version of symbol 
> saa7134_dmasound_exit
> [   31.247886] saa7134_alsa: Unknown symbol saa7134_dmasound_exit
> [   31.248165] saa7134_alsa: disagrees about version of symbol 
> saa7134_set_dmabits
> [   31.248167] saa7134_alsa: Unknown symbol saa7134_set_dmabits
> [   31.320315] DVB: registering new adapter (saa7133[0])
> 
> I don't know if this also causes my problem but it possibly does. The 
> saa7134 audio device is not recognized at all.
> 
> And yes, I have the firmware (required for DVB-T so irrelevant but 
> anyway) installed.
> 
> -- 
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
> 

Ok, so I've probably done something wrong since there's no reply (and 
saa7134-alsa isn't that rare). If anyone would mind to tell me what it 
is so I can tell you and hopefully this bug can be fixed..

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: saa7134-alsa appears to be broken

[hermann pitton]

Hi,

Am Samstag, den 26.07.2008, 21:28 +0200 schrieb P. van Gaans: 
> On my Asus P7131 (DVB-T+analog+radio) I can't listen to FM radio anymore 
> with a recent v4l-dvb or multiproto. If I go back to the v4l-dvb that 
> comes with the kernel (2.6.24-19) I do get sound. Not completely without 
> problems, have to restart aplay/arecord now and then but at least it 
> works. With the recent v4l-dvb/multiproto it doesn't work at all.
> 

for what I read, on recent v4l-dvb all relevant outstanding patches are
applied and the driver should be in a sane state

To avoid further drift of the known status, I made some testing early
morning yesterday.

The saa7133/35/31e radio over RIF (amux = TV) is OK on v4l-dvb as of
head 8325 with only the proposed patch for fixing user tuner setting
applied, which Mauro picked up now. Thanks!

It is also fine on vanilla 2.6.26, radio and TV sound at 32000Hz, 16bit
stereo, up-sampled to what ever or not.

I currently only have one remaining card with a saa7134 chip in the
slots with a FMD1216ME/I MK3 on an old nforce2. That one showed, since
used, opposite to prior boards is use, soon sync drifting on saa7134
radio with tda9887, no matter of sampling rate. External analog TV sound
to the sound card is fine.

Audacity is equally bad for TV sound as radio on that one using the alsa
OSS emulation at 32000HZ, but sox in the same emulation mode has no
issues for TV sound. I suspect board/sound driver specific issues, but
would have to revive some old machines for further testing.
Also the audio clock at the one might be worse than seen on my prior
cards, but we always had such reports from time to time.

Likely you kept some old module loaded or it is reloaded.
Exported symbols for saa7134-tvaudio used by saa7134-alsa and videobuf
dma stuff are out of sync and for sure cause trouble.

Try "make rminstall", still old modules around in /lib/modules/...?

Or try "modprobe -v saa7134" to see if your distribution is playing
games with you and from where maybe duplicate and out of sync modules
are loaded.

If that doesn't help, we might start to use the same v4l-dvb snapshot
next. Currently i only have the P7131 Dual and the prior Asus Tiger.

On which P7131 you are exactly? (dmesg for subsystem, gpio init, eeprom)
It is a whole bunch of different cards meanwhile and external firmware
loading started with the P7131 Hybrid. Yes, radio is not related, but
there is also some board specific antenna input switching and LNA stuff
I can't test.  

Cheers,
Hermann

> dmesg has something to say (took out the interesting part):
> 
> [   31.155028] saa7133[0]: registered device video0 [v4l2]
> [   31.155043] saa7133[0]: registered device vbi0
> [   31.155055] saa7133[0]: registered device radio0
> [   31.247453] saa7134_alsa: disagrees about version of symbol 
> saa7134_tvaudio_setmute
> [   31.247457] saa7134_alsa: Unknown symbol saa7134_tvaudio_setmute
> [   31.247542] saa7134_alsa: disagrees about version of symbol 
> saa_dsp_writel
> [   31.247544] saa7134_alsa: Unknown symbol saa_dsp_writel
> [   31.247808] saa7134_alsa: disagrees about version of symbol 
> saa7134_dmasound_init
> [   31.247809] saa7134_alsa: Unknown symbol saa7134_dmasound_init
> [   31.247884] saa7134_alsa: disagrees about version of symbol 
> saa7134_dmasound_exit
> [   31.247886] saa7134_alsa: Unknown symbol saa7134_dmasound_exit
> [   31.248165] saa7134_alsa: disagrees about version of symbol 
> saa7134_set_dmabits
> [   31.248167] saa7134_alsa: Unknown symbol saa7134_set_dmabits
> [   31.320315] DVB: registering new adapter (saa7133[0])
> 
> I don't know if this also causes my problem but it possibly does. The 
> saa7134 audio device is not recognized at all.
> 
> And yes, I have the firmware (required for DVB-T so irrelevant but 
> anyway) installed.
> 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: saa7134-alsa appears to be broken

[Lars Oliver Hansen]

Hi,

I experience the same problem: the sound part of the saa7134 driver
doesn't load.

Ususally I get such symbol errors with MadWiFis snapshot driver after
every application installation which configured some kernel stuff. I
then unload the MadWiFi driver and do a clean install according to their
description.

I'm new to Linux and thus don't know the options I have for and how to
make a clean install in general. Hermann suggested to do a make
rminstall in his response. Could anyone help me here as how to do this
with the saa7134 experimental driver (it's cloning the relevant
Mercurial repository) or what else I could try?

As I installed the sound driver after make-ing the TV card driver I
guess an update of some dependancies may be necessary. I don't know
anything about the relations there at all. Would someone shed some light
on this? Thanks for taking time for this issue and for a possible answer
in advance!

Kind Regards,

Lars


P.s.: here's the dmesg output again:

[    0.000000] saa7134_alsa: disagrees about version of symbol
saa7134_tvaudio_setmute
[    0.000000] saa7134_alsa: Unknown symbol saa7134_tvaudio_setmute
[    0.000000] saa7134_alsa: disagrees about version of symbol
saa_dsp_writel
[    0.000000] saa7134_alsa: Unknown symbol saa_dsp_writel
[    0.000000] saa7134_alsa: disagrees about version of symbol
saa7134_pgtable_alloc
[    0.000000] saa7134_alsa: Unknown symbol saa7134_pgtable_alloc
[    0.000000] saa7134_alsa: disagrees about version of symbol
saa7134_pgtable_build
[    0.000000] saa7134_alsa: Unknown symbol saa7134_pgtable_build
[    0.000000] saa7134_alsa: disagrees about version of symbol
saa7134_pgtable_free
[    0.000000] saa7134_alsa: Unknown symbol saa7134_pgtable_free
[    0.000000] saa7134_alsa: disagrees about version of symbol
saa7134_dmasound_init
[    0.000000] saa7134_alsa: Unknown symbol saa7134_dmasound_init
[    0.000000] saa7134_alsa: disagrees about version of symbol
saa7134_dmasound_exit
[    0.000000] saa7134_alsa: Unknown symbol saa7134_dmasound_exit
[    0.000000] saa7134_alsa: disagrees about version of symbol
saa7134_set_dmabits
[    0.000000] saa7134_alsa: Unknown symbol saa7134_set_dmabits

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: saa7134-alsa appears to be broken

[hermann pitton]

Hi Lars,

Am Samstag, den 02.08.2008, 17:17 +0200 schrieb Lars Oliver Hansen:
> Hi,
> 
> I experience the same problem: the sound part of the saa7134 driver
> doesn't load.
> 
> Ususally I get such symbol errors with MadWiFis snapshot driver after
> every application installation which configured some kernel stuff. I
> then unload the MadWiFi driver and do a clean install according to their
> description.
> 
> I'm new to Linux and thus don't know the options I have for and how to
> make a clean install in general. Hermann suggested to do a make
> rminstall in his response. Could anyone help me here as how to do this
> with the saa7134 experimental driver (it's cloning the relevant
> Mercurial repository) or what else I could try?
> 
> As I installed the sound driver after make-ing the TV card driver I
> guess an update of some dependancies may be necessary. I don't know
> anything about the relations there at all. Would someone shed some light
> on this? Thanks for taking time for this issue and for a possible answer
> in advance!
> 
> Kind Regards,
> 
> Lars
> 

please report this again from a 2.6.26.1 or every other vanilla kernel
of you choice.

We had some minor issues, but I refuse to investigate what others
deliberately add.

Cheers,
Hermann

BTW: in kernel drivers follow the kernel versions since ever.

> P.s.: here's the dmesg output again:
> 
> [    0.000000] saa7134_alsa: disagrees about version of symbol
> saa7134_tvaudio_setmute
> [    0.000000] saa7134_alsa: Unknown symbol saa7134_tvaudio_setmute
> [    0.000000] saa7134_alsa: disagrees about version of symbol
> saa_dsp_writel
> [    0.000000] saa7134_alsa: Unknown symbol saa_dsp_writel
> [    0.000000] saa7134_alsa: disagrees about version of symbol
> saa7134_pgtable_alloc
> [    0.000000] saa7134_alsa: Unknown symbol saa7134_pgtable_alloc
> [    0.000000] saa7134_alsa: disagrees about version of symbol
> saa7134_pgtable_build
> [    0.000000] saa7134_alsa: Unknown symbol saa7134_pgtable_build
> [    0.000000] saa7134_alsa: disagrees about version of symbol
> saa7134_pgtable_free
> [    0.000000] saa7134_alsa: Unknown symbol saa7134_pgtable_free
> [    0.000000] saa7134_alsa: disagrees about version of symbol
> saa7134_dmasound_init
> [    0.000000] saa7134_alsa: Unknown symbol saa7134_dmasound_init
> [    0.000000] saa7134_alsa: disagrees about version of symbol
> saa7134_dmasound_exit
> [    0.000000] saa7134_alsa: Unknown symbol saa7134_dmasound_exit
> [    0.000000] saa7134_alsa: disagrees about version of symbol
> saa7134_set_dmabits
> [    0.000000] saa7134_alsa: Unknown symbol saa7134_set_dmabits
> 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: saa7134-alsa appears to be broken

[hermann pitton]

Hallo Lars,

I send a copy to the list anyway, even you seem to prefer German.

Am Sonntag, den 03.08.2008, 12:43 +0200 schrieb Lars Oliver Hansen:
> Hallo Herrmann,
> 
> Am Sonntag, den 03.08.2008, 01:32 +0200 schrieb hermann pitton: 
> > Hi Lars,
> > 
> > Am Samstag, den 02.08.2008, 17:17 +0200 schrieb Lars Oliver Hansen:
> > > Hi,
> > > 
> > > I experience the same problem: the sound part of the saa7134 driver
> > > doesn't load.
> .... 
> > 
> > please report this again from a 2.6.26.1 or every other vanilla kernel
> > of you choice.
> > 
> > We had some minor issues, but I refuse to investigate what others
> > deliberately add.
> > 
> > Cheers,
> > Hermann
> > 
> > BTW: in kernel drivers follow the kernel versions since ever.
> 
> Ich verwende Ubuntu 8.04 und weiß noch nicht, wie ich den Kernel
> upgraden kann ohne Abhängigkeiten in Ubuntu zu verlieren. Überhaupt
> weiß ich noch nicht, wie ich ein Kernel von Kernel.org compilieren
> muss, was ich alles tun muss und brauche, damit jeder Bestandteil
> meiner Ubuntu Installation noch funktioniert :-).
> Wenn ich hier irgendeinen Test ausführen kann oder hier irgendwelche
> Informationen abrufen kann, die dir/euch weiterhelfen, tue ich das
> gerne!
> 
> Grüße,
> 
> Lars

Leider geht das jetzt schon seit Monaten so mit Ubuntu und alsa.

Habe es nicht, aber sie verwenden wohl eine alsa Version, die mit der im
regulären Kernel nicht kompatibel ist.

Es gibt wohl Möglichkeiten aktuelles v4l-dvb mit saa7134-alsa trotzdem
erfolgreich zu kompilieren, aber dazu muss man sich mit dem build system
dort beschäftigen. Es scheint zu genügen zu den richtigen lum alsa
headers zu linken.

Zuerst fehlte saa7134-alsa wohl komplett, dann wurde gegen inkompatible
header gelinkt. Sollte mit aktuellem Ubuntu Kernel jetzt in Ordnung
sein. Ab 2.6.24-16 Hardy Heron RC ?

Probiere mal Google mit "ubuntu saa7134-alsa".

Hier ist ein Link zum Fix von Tim Gardner.
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/192559

Das vorher von mir empfohlene "make rminstall" bezieht sich auf
aktuelles v4l-dvb von linuxtv.org.

Nach "make" sollte man mit "make rmmod" zunächst alle Module entladen.
Falls das Skript auf wirklich alten Kernen nicht mehr alles erwischt, 
sollte man später einen Reboot in Erwägung ziehen oder selbst nachhelfen.

Wenn man einen älteren Kernel hat, also nicht 2.6.27-rc1 oder wenigstens
2.6.26, kann es vorkommen, dass dort noch alte Module, die kürzlich
umbenannt oder komplett entfernt wurden, vorhanden sind und vom
aktuellen "make rminstall" auch nicht entfernt werden.

Etwa das früher video-buf.ko genannte Modul auf <= 2.6.23 blieb eine
Weile zurück, wird aber jetzt erfasst. 
Das als veraltet entfernte saa7134-oss behält man dagegen immer noch. 

Falls vorhanden, muss man solche dann selbst entfernen.

Das gilt auch für saa7134-alsa, das etwa bei einer früheren Kompilierung
aktiviert war, jetzt aber mit zum Beispiel make xconfig/menuconfig
abgewählt ist. Ohne "make rminstall" könnte ein inkompatibles älteres
saa7134-alsa Modul zurück bleiben.

Man kann auch einfach nach "make rmmod" den
kompletten /lib/modules/Deine_Kernelversion/kernel/drivers/media
Ordner löschen oder für ein Backup verschieben.

Das ist eine ziemlich sichere Methode :) und die zeigt auch sofort
eventuell fehlende Module, die gerade auf einem sehr alten Kernel
vielleicht nicht mehr alle mit "make" (all) automatisch bereit gestellt
werden oder die Inkompatibilitäten mit "make xconfig" und Selektivität
haben können. 

Ein 2.6.24 sollte aber definitiv keine besonderen Probleme haben.
Das weiß man aber erst dann wirklich, nachdem _alle_ möglichen Varianten
getestet sind.

Mit "make install", welches am Ende auch das beim Verändern von Modulen
immer notwendige "depmod -a" ausführt, hat man dann aber auch auf einem
älteren Kernel ein konsistentes und aktuelles v4l-dvb.

Als Restrisiko bleibt, dass eine Distribution Module in einem anderen
Ordner als media haben kann oder man kann auch noch Module von einem
anderen Anbieter irgendwo sonst installiert haben, die immer noch nicht
entfernt sind.

In der Regel hilft es hier modprobe mit der -v Option zu verwenden.

So sieht man von wo die Module geladen werden und auch ob andere
Einstellungen, eingetragen etwa durch Anwendungen, die bei der
Systemkonfiguration helfen sollen, die eigene Kommandozeile beim Laden
überschreiben.

Viel Glück und einen schönen Sonntag,

Hermann


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list