Add support for Sigmatel STAC9202/9250/9251 codecs.
Summary: Add support for Sigmatel STAC9202/9250/9251 codecs.
This patch adds support for Gateway laptops based on the Sigmatel STAC9250 codecs, as well as basic support for STAC9202/9250/9251 codecs. Some Gateway systems require probe_mask=1 to work. More work to be done prior to alsa 1.0.14 final.
Signed off by Tobin Davis <[email protected]>
Documentation/ALSA-Configuration.txt +7 -1
@@ -814,8 +814,9 @@ Prior to version 0.9.0rc4 options had a ALC882/885 3stack-dig 3-jack with SPDIF I/O - 6stck-dig 6-jack digital with SPDIF I/O + 6stack-dig 6-jack digital with SPDIF I/O arima Arima W820Di1 + macpro MacPro support auto auto-config reading BIOS (default) ALC883/888
@@ -888,6 +889,11 @@ Prior to version 0.9.0rc4 options had a ref Reference board 3stack D945 3stack 5stack D945 5stack + SPDIF + + STAC9202/9250/9251 + ref Reference board, base config + m2-2 Some Gateway MX series laptops + m6 Some Gateway NX series laptops STAC9227/9228/9229/927x ref Reference board
pci/hda/patch_sigmatel.c +140 -0
188 lines not on this page · raw message
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
At Tue, 02 Jan 2007 11:31:39 -0800,
Quoted 11 lines · Tobin Davis
Summary: Add support for Sigmatel STAC9202/9250/9251 codecs.
This patch adds support for Gateway laptops based on the Sigmatel STAC9250 codecs, as well as basic support for STAC9202/9250/9251 codecs. Some Gateway systems require probe_mask=1 to work. More work to be done prior to alsa 1.0.14 final.
Signed off by Tobin Davis <[email protected]>
Applied to ALSA HG tree now.
Since a part of the patch conflicted (it includes the change that was already merged), I fixed it manually.
Please check whether the latest HG tree is OK.
Thanks.
Takashi
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Hi. I'm a first time user of this newsgroup and a relatively new Linux user. I use the mx6453 model (which I believe leaves me with 9250) and have been dealing with no sound in Linux for a few weeks now. When I saw the previous threads concerning test patches for the Sigmatel codecs in this newsgroup, I was hoping it might fix the problem.
I tried installing the patch using the instructions you gave on
http://article.gmane.org/gmane.linux.alsa.devel/42922 for test patch 6.
However, once I added the module I was still getting invalid dep range
errors in the output from dmesg (I'd post it here, but I'm in Windows at the moment) I know you said more work needs to be done on this patch, but I thought there might also be the chance I did something wrong. Does applying the patch involve a different set of steps than test patch 6?
Also, konsole initially gave me this when I removed the snd_hda_codec and put it back in with modprobe
WARNING: Error inserting snd_hda_codec (/lib/modules/2.6.15-26-amd64-generic/kernel/sound/pci/hda/snd-hda-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.15-26-amd64-generic/kernel/sound/pci/hda/snd-hda-intel.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
A restart made reinserting the module run smoothly, but I can't kick the feeling I'm doing something wrong here. Again, I'm new to this newsgroup and Linux in general, so if I'm not supplying enough information about the issue, I'm sorry and I'll give you whatever else you need.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
What I found from other testers is that you need to add "probe_mask=1" to the driver when loading. This can be done a couple of ways. The easiest way to test it is with modprobe as follows:
modprobe snd-hda-intel probe_mask=1
The other method that makes this more permanent is to add probe_mask=1 to your modprobe.conf file. Since each distribution is different, the best I can tell you is to look in /etc for either a modprobe.conf or modules.conf file. There might also be variations of those files (i.e. modprobe.preload, modprobe.d/sound.conf, etc). Ther should be something like this:
alias sound-slot-0 snd-hda-intel
Add the following line to the same file, below the alias line:
options snd-hda-intel probe_mask=1
That should fix your dep range issues and give you working sound.
As a final note, the latest patch is available in alsa-driver-1.0.14rc2 available from alsa-project.org. The only issues I know of are crashes with the Gateway NX560XL, which are as of yet unresolved. I do have good reports of your model working though.
Tobin
Quoted 40 lines · Nicholas Taylor
Hi. I'm a first time user of this newsgroup and a relatively new Linux user. I use the mx6453 model (which I believe leaves me with 9250) and have been dealing with no sound in Linux for a few weeks now. When I saw the previous threads concerning test patches for the Sigmatel codecs in this newsgroup, I was hoping it might fix the problem.
I tried installing the patch using the instructions you gave on
http://article.gmane.org/gmane.linux.alsa.devel/42922 for test patch 6.
However, once I added the module I was still getting invalid dep range
errors in the output from dmesg (I'd post it here, but I'm in Windows at the moment) I know you said more work needs to be done on this patch, but I thought there might also be the chance I did something wrong. Does applying the patch involve a different set of steps than test patch 6?Also, konsole initially gave me this when I removed the
snd_hda_codecand put it back in with modprobeWARNING: Error inserting
snd_hda_codec(/lib/modules/2.6.15-26-amd64-generic/kernel/sound/pci/hda/snd-hda-codec.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error insertingsnd_hda_intel(/lib/modules/2.6.15-26-amd64-generic/kernel/sound/pci/hda/snd-hda-intel.ko):
Unknown symbol in module, or unknown parameter (see dmesg)A restart made reinserting the module run smoothly, but I can't kick the feeling I'm doing something wrong here. Again, I'm new to this newsgroup and Linux in general, so if I'm not supplying enough information about the issue, I'm sorry and I'll give you whatever else you need.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Signature · 1 line
Tobin Davis <[email protected]>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
At Tue, 16 Jan 2007 14:24:18 -0800,
Quoted 6 lines · Tobin Davis
What I found from other testers is that you need to add "probe_mask=1" to the driver when loading. This can be done a couple of ways. The easiest way to test it is with modprobe as follows:
modprobe snd-hda-intel probe_mask=1
This actually specifies to probe only the first codec. What else codec does this device have? You can see the codec_mask values by building with --with-debug=detect option.
I'm wondering why probing other codecs result in the dep range error (that basically means the communication failure between the controller and the codec chip).
Takashi
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
At Wed, 17 Jan 2007 19:02:14 -0800,
Quoted 4 lines · Tobin Davis
What I've seen in the codec reports from testers is the Sigmatel STAC9250 on codec#0,
the modem on codec#1, and garbage on codec#3 (see attached output). I've also
attached some of the dmesg output that was relevant to this issue.
Hm, actually the codecs supported should be up to #2.
So, the patch below should fix the problem. If it work, I'll push to ALSA tree.
Takashi
pci/hda/hda_intel.c +1 -1
@@ -199,7 +199,7 @@ enum { SDI0, SDI1, SDI2, SDI3, SDO0, SDO/* STATESTS int mask: SD2,SD1,SD0 */ #define STATESTS_INT_MASK 0x07 -#define AZX_MAX_CODECS 4 +#define AZX_MAX_CODECS 3/* SD_CTL bits */ #define SD_CTL_STREAM_RESET 0x01/* stream reset bit */
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV