Ticket #62 (closed enhancement: fixed)

Opened 5 years ago

Last modified 5 years ago

padsp unknow ioctl

Reported by: mariodebian Owned by: lennart
Milestone: Component: clients
Keywords: Cc:

Description

I'm trying to run rdesktop sound (OSS) in a thin client. Thin client have a SB16 compatible sound card and pulseaudio running, tryin to exec rdesktop like this:

# padsp -d -s localhost -n rdesktop rdesktop -r sound -a 16 -f -k es WINDOWS_REMOTE_IP

This is debug output:

utils/padsp.c: dsp_open()
utils/padsp.c: fd_info_new()
utils/padsp.c: dsp_open() succeeded, fd=5
utils/padsp.c: SNDCTL_DSP_RESET
utils/padsp.c: SNDCTL_DSP_SYNC
utils/padsp.c: Draining.
utils/padsp.c: SNDCTL_DSP_SETFMT: 16
utils/padsp.c: SNDCTL_DSP_STEREO: 1
utils/padsp.c: SNDCTL_DSP_SPEED: 22050
utils/padsp.c: ss: s16le 2ch 22050Hz
utils/padsp.c: SNDCTL_DSP_SETFRAGMENT: 0x000c000c
utils/padsp.c: SNDCTL_DSP_GETOSPACE
utils/padsp.c: fragsize=4096, fragstotal=12, bytes=49152, fragments=12
utils/padsp.c: unknown ioctl 0xc0044d04
MIXER_WRITE(SOUND_MIXER_PCM): Invalid argument
utils/padsp.c: stream established.
utils/padsp.c: mixer_open()
utils/padsp.c: fd_info_new()
utils/padsp.c: mixer_open() succeeded, fd=9
utils/padsp.c: SOUND_MIXER_WRITE_IGAIN
utils/padsp.c: freeing fd info (fd=9)
utils/padsp.c: Draining.
utils/padsp.c: unknown ioctl 0xc0044d04

I remember "unknow ioctl" was on java padsp bug too, and was solved.

Change History

Changed 5 years ago by ossman

  • owner changed from lennart to ossman
  • component changed from module-esound-* to clients

Odd, that ioctl is SOUND_MIXER_WRITE_PCM which padsp has supported since 0.9.0. Sure your system is up to date?

Changed 5 years ago by mariodebian

I'm running 0.9.5 svn snapshot of 20070213

I will try with a more recent snapshot...

Changed 5 years ago by lennart

  • owner changed from ossman to lennart
  • status changed from new to assigned
  • type changed from defect to enhancement

This is caused by calling SOUND_MIXER_WRITE_PCM on the dsp fd -- and not on the mixer fd. That is perfectly valid behaviour. (actually we do the same when accessing OSS)

Changed 5 years ago by ossman

  • status changed from assigned to closed
  • resolution set to fixed

Solved in r1473.

Note: See TracTickets for help on using tickets.