#55 Aureal 8830 driver problem under KDE 3.1


Any plans to fix this problem? I'm running SuSE 8.1 pro.


Linux Driver/Soundcard: aureal8820, aureal8830 drivers
from sourceforge

Fails under: Kernel version 2.4.17

Remarks: driver triggers assertion / causes cpu
overload (see below)

13.3 What is wrong in the driver if I get the cpu
overload problem?

Usually, artsd uses select() to find out when to write
new data. Then, it uses an ioctl(...GETOSPACE...) to
find out how much data to write. Finally, it writes
this data.

A problem occurs if artsd is woken up either always or
if there are minimal amounts of data to write. The OSS
documentation specifies that select() only wakes up a
process if there is at least one fragment to write.
However, if artsd is woken up if there isn't data to
write, or very little, for instance one sample, then it
will keep writing little pieces of audio data, which
can be very costly, and eventually overload the cpu.

To fix this, the driver should wake up artsd only if
there is a full fragment to write.


  • EspeonEefi

    EspeonEefi - 2003-02-16

    Logged In: YES

    Just wanted to confirm that I'm running into this problem as
    well. I'm running KDE 3.1 under Debian sid. I've got a
    custom-compiled 2.4.20 kernel and an Intel 440BX AGPset
    chipset. I get this dialog box during start-up (note the
    strange len = -1):

    Title: Error - artsmessage

    Sound server fatal error:

    AudioSubSystem::handleIO: write failed

    len = -1, can_write = 4096, errno = 11 (Resource temporarily

    This might be a sound hardward/driver specific problem (see
    aRts FAQ)

  • Nobody/Anonymous

    Logged In: NO

    Just open kcontrol, select Sound system, Input/Output and
    choose Threaded Open Sound System. That solved everything
    for me.

  • Warren Chartier

    Warren Chartier - 2003-07-24

    Logged In: YES

    This explaination is ludicrous, the driver doesn't wake up
    artsd it's the other way around, artsd fragsize issue.

  • Warren Chartier

    Warren Chartier - 2003-07-24
    • status: open --> closed-rejected

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks