Sound On Titchylinux

[ZDevil]

*SNIPPED*
But, as I read the threads, it sounds like titchy isn't quite stable and working, though it is the coolest thing to come around in while.
*SNIPPED*

Honestly I am feeling rather differently. Debian is acutally very stable (it never hangs or crashes so far, not even once). Most debian packages just work. Upgrading and apt-get and the native toolchain works so beautifully.  (Well the Debian toolchain is way better than that for pdaX). And debian runs pretty fast too, just like pdaX, and much much smoother than using the pocketworkstation "in the old days" .
The biggest issue at hand now is sound. But before working out a solution we have to track down the origin of the issue.
neil says it's due to version incompatibility (Angstrom's zaurus-soundhack is alsa 1.0.14, while the default Etch is 1.0.13). I still find it a bit unclear to me: the Lenny alsa libraries are actually also 1.0.14. But sound is crippled. But it plays very well in games. I enjoy bery much the Ultima 7 tune in my Sangband package (will upload *very* soon  ). And I beat powermanga with full sound and music. Flobopuyo also plays great.

[Chero]

*SNIPPED*
But, as I read the threads, it sounds like titchy isn't quite stable and working, though it is the coolest thing to come around in while.
*SNIPPED*

Honestly I am feeling rather differently. Debian is acutally very stable (it never hangs or crashes so far, not even once). Most debian packages just work. Upgrading and apt-get and the native toolchain works so beautifully.  (Well the Debian toolchain is way better than that for pdaX). And debian runs pretty fast too, just like pdaX, and much much smoother than using the pocketworkstation "in the old days" .

I second this.
It is rock solid !

Chero.

[adf]

*SNIPPED*
But, as I read the threads, it sounds like titchy isn't quite stable and working, though it is the coolest thing to come around in while.
*SNIPPED*

Honestly I am feeling rather differently. Debian is acutally very stable (it never hangs or crashes so far, not even once). Most debian packages just work. Upgrading and apt-get and the native toolchain works so beautifully.  (Well the Debian toolchain is way better than that for pdaX). And debian runs pretty fast too, just like pdaX, and much much smoother than using the pocketworkstation "in the old days" .

I second this.
It is rock solid !

Chero.

I'll keep an eye on it, certainly. some flavor or other of debian is on everything else I have, it wouod be handy on my Z, too.

[ZDevil]

I hate to hijack the topic, so let me follow up on the issue discussed here:
https://www.oesf.org/forum/index.php?showto...mp;#entry169288

In short, the current pdaX r198, which also uses kernel 2.6.xx, also suffers from a similar sound problem.

koen says the kernel has already got the right sound driver, and the Angstrom alsa stuff should work with that. But the problem is the Angstrom ALSA binaries don't run in Debian (simply "file not found").  
My impression after browing the Angstrom package repositories is that the current Angstrom libraries have already turned EABI (according to the available architecture choices, though some packages are still named "armv5te" only), which means they don't run in the current ARM Debian.  I did try and got the "file not found" error, so the files are simply not recognized.
Or am i wrong about all this? Or should I look somewhere else?
I can't ask this in the Angstrom mailing list because this is for (ARM) Debian.

Again, does anyone understand what neils means by "installing the Angstrom bits" to make sound work, apart from the zaurus-suundhack package?

And has anyone got sound play thru the speaker and not just the headphone?

The mouse right click and brightness setting issues already have solutions (see the recent threads). With this fixed, we'll have a reasonably functioning Debian setup to work/play with.

[jpmatrix]

perhaps compiling wm8750 mixer would help ? i try!

[Chero]

http://bugs.openembedded.org/show_bug.cgi?id=2617
http://bugs.openembedded.org/show_bug.cgi?id=2657

There seems to be a bug in the Angstrom sound-system for Zaurus. Maybe problems will be solved when Angstrom does it's next release (If they can get altboot working again).

Chero.

[adf]

http://bugs.openembedded.org/show_bug.cgi?id=2617
http://bugs.openembedded.org/show_bug.cgi?id=2657

There seems to be a bug in the Angstrom sound-system for Zaurus. Maybe problems will be solved when Angstrom does it's next release (If they can get altboot working again).

Chero.

Just to be clear... Is there a 2.6 kernel for the Z that has sound functions comparable to the latest developments in 2.4? I bring this up both for clarification, and to emphasize (given that I'm right, of course--otherwise I'm just emphasizing that I missed something) that the problem seems endemic to 2.6 zaurus ports.

[koen]

Just to be clear... Is there a 2.6 kernel for the Z that has sound functions comparable to the latest developments in 2.4?

No, the 2.6 kernel in OE has far better functions, given that you use a proper userspace. Running an EABI kernel with OABI alsa is causing the crappy sounds due to struct differences between OABI and EABI. The people at Wolfson micro that write the drivers for alsa SoC are OE developers themselves, so you can't get any better than that.

[jpmatrix]

Just to be clear... Is there a 2.6 kernel for the Z that has sound functions comparable to the latest developments in 2.4?

No, the 2.6 kernel in OE has far better functions, given that you use a proper userspace. Running an EABI kernel with OABI alsa is causing the crappy sounds due to struct differences between OABI and EABI. The people at Wolfson micro that write the drivers for alsa SoC are OE developers themselves, so you can't get any better than that.

koen,
right now we're using the 2.6.22 kernel of Angstrom within Debian Tichy and the 2.6.22 modules. so i guess sound should work as fine as in real Angstrom no? (perhaps i'm mistaken?)

[koen]

Yes, you're mistaken, since you are using the OABI debian.

[jpmatrix]

Yes, you're mistaken, since you are using the OABI debian.

ok
so how could we get rid of that ? recompile the kernel ?? (excuse my linux newbie questions

[Dromede]

koen is right. i can't understand why are you using the titchy rootfs when you have a quite usable debian armel rootfs right here:
http://armel.applieddata.net/developers/li...root-fs.tar.bz2

[koen]

koen is right. i can't understand why are you using the titchy rootfs when you have a quite usable debian armel rootfs right here:
http://armel.applieddata.net/developers/li...root-fs.tar.bz2

The debian developers in the #oe irc channel asked that very same question

[tux]

koen is right. i can't understand why are you using the titchy rootfs when you have a quite usable debian armel rootfs right here:
http://armel.applieddata.net/developers/li...root-fs.tar.bz2

The debian developers in the #oe irc channel asked that very same question

 Thanks koen, dromede and xor for the helpful links.  

I feel, I am a thorough novice here. So I'm going to look at the file I'm downloading from the link above and take some time out to look at the information on the Wolfson site.

Your explanation of the problem seems to put it in clear perspective. Thanks for that.

Whilst you're in the giving vein: is there any particular place in the angstrom pages I would find helpful in understanding what you all have just pointed us to?

I've always been unlucky with the opie stuff up to date. Always felt that I was banging my head on a brick wall when I have tried it. So altough I downloaded the bitbake system I have been very reluctant to try it out. Do I need to get into using your build system in order to get on with this Titchy thing?   Or will those links allow me/us to make some progress with one of the nicer developments I have come across for a while? Perhaps using the native development tools?

I much prefer forum and Wiki for communication to buglists and irc.    But if you assure me that I'll learn from them I'll make the effort to look.  

Cheers

 

[koen]

koen is right. i can't understand why are you using the titchy rootfs when you have a quite usable debian armel rootfs right here:
http://armel.applieddata.net/developers/li...root-fs.tar.bz2

The debian developers in the #oe irc channel asked that very same question

 Thanks koen, dromede and xor for the helpful links.  

I feel, I am a thorough novice here. So I'm going to look at the file I'm downloading from the link above and take some time out to look at the information on the Wolfson site.

Your explanation of the problem seems to put it in clear perspective. Thanks for that.

Whilst you're in the giving vein: is there any particular place in the angstrom pages I would find helpful in understanding what you all have just pointed us to?

I've always been unlucky with the opie stuff up to date. Always felt that I was banging my head on a brick wall when I have tried it. So altough I downloaded the bitbake system I have been very reluctant to try it out. Do I need to get into using your build system in order to get on with this Titchy thing?   Or will those links allow me/us to make some progress with one of the nicer developments I have come across for a while? Perhaps using the native development tools?

I much prefer forum and Wiki for communication to buglists and irc.    But if you assure me that I'll learn from them I'll make the effort to look.  

Cheers

 

Use angstrom, sound works there (modulo weirdos using 31999Hz sample rates, but that doesn't work anywhere) and we can add packages you are missing, *if* you tell us what you need, either on the mailinglist or on bugzilla. BTW, opie is unsupported in angstrom, since in practice is has been unmaintained for two years (the 1.2.3 releases basically updates some icons, big deal).