OESF Portables Forum

Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: daniel3000 on October 06, 2006, 08:10:21 am

Title: Kernel Modules / Audio
Post by: daniel3000 on October 06, 2006, 08:10:21 am

Hello,

the current topic about kernel module comüilatoin mde me think of this:

There is the known bug that when the Z is suspended while XMMS is running, the audio device is blocked until the next reboot.

The audio driver seems to be compiled into the kernel, as no module is loaded for audio.

Couldn't we simply compile a kernel with audio drivers compiled as modules instead of built into the kernel, and unload the modules during suspend and reload them after resume in order to fix that problem?


daniel

Title: Kernel Modules / Audio
Post by: pelrun on October 06, 2006, 10:37:56 am

I think it'd be much simpler to write a suspend.d script to pause xmms and set a flag so that a resume.d script would know to unpause it.

But I'm pretty sure that when I've gotten into that state I've been able to get out of it again by kill -9'ing xmms and esd...

Title: Kernel Modules / Audio
Post by: daniel3000 on October 06, 2006, 10:51:53 am

Quote

I think it'd be much simpler to write a suspend.d script to pause xmms and set a flag so that a resume.d script would know to unpause it.

But I'm pretty sure that when I've gotten into that state I've been able to get out of it again by kill -9'ing xmms and esd...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143322\"][{POST_SNAPBACK}][/a][/div]

aha, good to know. WIll try it.
However, do you think pausing XMMS is what's needed?
I thought we get into that state even if XMMS is already paused and just open...
I could be wring though. Will have to try it out.

daniel

Title: Kernel Modules / Audio
Post by: pelrun on October 07, 2006, 10:39:42 pm

Xmms has never gotten into a bad state for me whilst paused.

Title: Kernel Modules / Audio
Post by: karlto on October 08, 2006, 04:36:10 pm

Also make sure that xmms is using esound and not oss

Title: Kernel Modules / Audio
Post by: daniel3000 on October 09, 2006, 07:13:39 am

Quote

Also make sure that xmms is using esound and not oss
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143469\"][{POST_SNAPBACK}][/a][/div]

oh, I have reconfigured it to use oss because esound didn't work when I tried it the first time. Now, when I retry, esound works fine. Stange.
What's the reason for using esound rather than oss?

Thanks
daniel

Title: Kernel Modules / Audio
Post by: karlto on October 09, 2006, 02:49:16 pm

Quote

Quote

Also make sure that xmms is using esound and not oss
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143469\"][{POST_SNAPBACK}][/a][/div]

oh, I have reconfigured it to use oss because esound didn't work when I tried it the first time. Now, when I retry, esound works fine. Stange.
What's the reason for using esound rather than oss?

Thanks
daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143509\"][{POST_SNAPBACK}][/a][/div]

OSS uses the mixer device directly (and locks it so other programs can't use it at the same time). Esound is a daemon that allows all programs to share the sound device, so even if XMMS crashes, the sound shouldn't be locked out.