-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Wednesday 2007-03-28 at 07:45 -0400, Carl Hartung wrote:
> On Wed March 28 2007 07:12, Carlos E. R. wrote:
> > and now it works! So, who on earth had my dsp that didn't show up in lsof?
> > Another tool to find out?
>
> Hi Carlos,
>
> I would think either your sound is not fully configured or there is a
> limitation/bug with the module.
I don't think it is that...
> My sound chip (SiS si7018) is fully supported. QAMix displays the chip number
> and revision in the title bar and all of the functions work: input selects,
> mutes, balances, levels, monitor mic or mix, stereo<>mono, capture level &
> mic boost enable, etc.... literally everything.
>
> The end result is I can run your sample command and hear festival
> pronouncing 'hello' while listening to an mp3. It is properly mixed, too, not
> one sound interrupting the other.
>
> In fact, I've only ever seen the type of problem you're describing when
> there's a real problem between the config or code and hardware. How deeply
> have you reviewed the module docs for your hardware?
None at all, not recently. It it Yast default config for it.
It normally works, but sometimes something leaves it "used" for ever and
festival stops working. It never was able to play two things
simultaneously on the same device (two dsps), but there is no problem ona
after the other. Right now something grabbed dsp for 24 hourss and hasn't
released it yet, and I can't know who/what. That's the problem.
Right now amarok doesn't work. It runs, but there is no icon. I have to
kill it. I try again from an xterm:
[EMAIL PROTECTED]:~> amarok
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use
amarokapp.
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for
PlaylistWindow/PlaylistWindow
QPainter::begin: Cannot paint null pixmap
Amarok: [Loader] Amarok is taking a long time to load! Perhaps something has
gone wrong?
Indeed something is wrong, but what? I restart alsa.
It is gnome desktop who is missbehaving... I have to log out :-/
[...]
It rejected to logout, it hung. I killed the session (ctrl-alt-bkspce),
init 3, init5... lot of processes that should be dead are not. I have to
do: "ps U cer u" as root to see them:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
cer 5531 0.0 0.0 3676 88 ? Ss Mar13 0:00
/usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6
cer 5569 0.0 0.1 8544 1044 ? S Mar13 0:00
/opt/gnome/sbin/gnome-vfs-daemon
cer 13503 0.0 0.0 10712 592 ? S Mar18 0:01
/opt/kde3/bin/artsd -F 10 -S 4096 -s 5 -m artsmessage -l 3
cer 14160 0.0 0.0 3684 88 ? Ss Mar18 0:00
/usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6
cer 14190 0.0 0.1 5264 1188 ? S Mar18 0:01 /usr/bin/esd
-nobeeps
cer 14212 0.0 0.1 8536 1040 ? S Mar18 0:00
/opt/gnome/sbin/gnome-vfs-daemon
cer 31276 0.0 0.0 3672 84 ? Ss Mar20 0:00
/usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6
cer 31325 0.0 0.1 8440 1204 ? S Mar20 0:00
/opt/gnome/sbin/gnome-vfs-daemon
cer 25617 0.0 0.0 3548 88 ? Ss Mar21 0:00
/usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6
cer 25656 0.0 0.1 8436 1200 ? S Mar21 0:00
/opt/gnome/sbin/gnome-vfs-daemon
cer 26392 0.0 0.0 3552 84 ? Ss Mar23 0:00
/usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6
cer 26431 0.0 0.1 8440 1184 ? S Mar23 0:00
/opt/gnome/sbin/gnome-vfs-daemon
cer 27090 0.0 0.0 3684 452 ? Ss Mar23 0:00
/usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6
cer 27133 0.0 0.1 8436 1560 ? S Mar23 0:00
/opt/gnome/sbin/gnome-vfs-daemon
cer 27202 0.0 1.4 65080 15096 ? Sl Mar23 5:40 beagled
/usr/lib/beagle/BeagleDaemon.exe --bg --autostarted
cer 27990 0.0 0.0 0 0 ? Z Mar23 0:01 [mono]
<defunct>
cer 27992 0.0 0.0 0 0 ? Z Mar23 0:01 [mono]
<defunct>
cer 21620 1.2 1.6 42096 16972 ? Sl 11:15 2:10 beagled-helper
/usr/lib/beagle/IndexHelper.exe
cer 22230 0.0 0.0 0 0 ? Z 11:17 0:01 [mono]
<defunct>
cer 22231 0.0 0.0 0 0 ? Z 11:17 0:01 [mono]
<defunct>
and then kill them all by hand...
nimrodel:~ # ps U cer u
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
cer 28203 0.0 0.1 4528 2036 tty3 Ss 14:04 0:00 -bash
cer 28224 1.1 0.3 8660 3448 tty3 S+ 14:04 0:03 pine
correct. Then a second user (who is not even logged in!):
nimrodel:~ # ps U zap u
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
zap 30810 0.0 0.0 3552 88 ? Ss Mar20 0:00
/usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6
zap 30855 0.0 0.0 8428 992 ? S Mar20 0:00
/opt/gnome/sbin/gnome-vfs-daemon
Huh? I also see rug running, and I had uninstalled it, so I thought!
root 6546 0.0 0.1 20504 1956 ? Sl Mar22 0:01 /usr/bin/mono
/usr/lib/rug/rug.exe ping
root 6691 0.0 0.1 20468 1936 ? Sl Mar22 0:01 /usr/bin/mono
/usr/lib/rug/rug.exe ping
root 6825 0.0 0.1 20420 1940 ? Sl Mar22 0:01 /usr/bin/mono
/usr/lib/rug/rug.exe --terse get-prefs security-level
root 6826 0.0 0.0 1904 32 ? S Mar22 0:00 cut -d| -f2
--only-delimited
root 6832 0.0 0.1 20408 2036 ? Sl Mar22 0:01 /usr/bin/mono
/usr/lib/rug/rug.exe set-prefs security-level none
root 6835 0.0 0.0 2936 36 ? S Mar22 0:00 sh -c export
TERM=dumb; /usr/bin/rug --no-abbrev --terse service-list | cut -d'|' -f5
--only-delimited; exit $?
root 6836 0.0 0.1 20464 1992 ? Sl Mar22 0:01 \_
/usr/bin/mono /usr/lib/rug/rug.exe --no-abbrev --terseservice-list
root 6837 0.0 0.0 1904 32 ? S Mar22 0:00 \_ cut -d|
-f5 --only-delimited
root 7209 0.0 0.1 21476 1984 ? Sl Mar22 0:01 /usr/bin/mono
/usr/lib/rug/rug.exe ping
root 7237 0.0 0.0 2936 36 ? S Mar22 0:00 sh -c export
TERM=dumb; /usr/bin/rug ping >/dev/null; exit $?
root 7238 0.0 0.1 20428 1620 ? Sl Mar22 0:01 \_
/usr/bin/mono /usr/lib/rug/rug.exe ping
Who started them? :-O :-/ Or maybe they did not die when I removed the
service... Right, there is no "/usr/lib/rug/rug.exe" file.
What a lot of rubish running I had!
But still, my session takes a long time to start, and it doesn't... seems
I'll have to reboot! :-/
I'll try init 1 first :-/
[...]
I had to reboot :-/
Ok, I have amarok playing (in gnome). I try to use festival, it fails
(normal in my system). I pause the play, festival works. This is how it
always did.
But sometimes, something somewhere gets stuck, and festival doesn't work.
It is usually festival, because I have a cron job with it to tell me the
time every half hour...
The funny thing is that lsof doesn't list /dev/dsp as being in use (but
amarok is using it, it is playing). How then can I know who/what has sound
in use?
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFGCmLftTMYHG2NR9URAuuhAKCY8KpSKVm1vEuv6INZZIQno07p6QCfcIxM
mOLS5SuMQjKizpZbvZknsi0=
=Golo
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
