lsof man page illustrates a -t option which lets you pipe terse output
to kill, which makes me suppose 'kill -9 pid' does not kill hanging
files belonging to processes.
raffaele
There's no such thing, that I know of, as 'kill hanging files'. 'lsof'
will give you process id's (PID
Raffaele Morelli wrote:
lsof man page illustrates a -t option which lets you pipe terse
output
to kill, which makes me suppose 'kill -9 pid' does not kill hanging
files belonging to processes.
raffaele
There's no such thing, that I know of, as
pkill is a better killall? it reminds me to the differences between top
and
htop (recently someone posted about it).
But how is it better?
Really don't know, my rule is the one which fits to your needs. I always
use killall and feel comfortable with. Sometimes I use kill, e.g. when
killing
Raffaele Morelli wrote:
pkill is a better killall? it reminds me to the differences
between top and
htop (recently someone posted about it).
But how is it better?
Really don't know, my rule is the one which fits to your needs. I
always use killall and feel comfortable
On Sun, 18 Mar 2007 09:52:22 +0100
Raffaele Morelli [EMAIL PROTECTED] wrote:
LAP:/# kill artsd
-su: kill: artsd: arguments must be process or job IDs
Ken, you need further manual reading about processes management.
man ps
man kill
man killall
Which makes me wonder:
LAP:/# kill artsd
-su: kill: artsd: arguments must be process or job IDs
Ken, you need further manual reading about processes management.
man ps
man kill
man killall
Which makes me wonder: what's the difference between killall and pkill?
pkill is a better killall? it reminds me to
If you are getting sound from that card using the cat, then I'm not
sure you need the isa stuff as the card is working and the kernel is
sending sound to it.
Ken pointed to alsa site, where it is said that without an isa-pnp module
the cards won't get properly configured.
In view the fact that the first thing everybody advised me to do was to
disable artsd. On examination I found out that artsd is a KDE creation
which wants to monopolize all sound operations to the exclusion of all
others, even others part of the KDE empire, such as KsCD and Kaffeine.
noatun
Ken Heard wrote:
[...]
I consequently installed four packages which had sdl in the name:
libsdl1.2debian, libsdl1.2debian-alsa, libsdl-net1.2 and
libsdl-sound1.2. I tried to purge these packages, but aptitude wanted
to remove a whole series of other packages including grub and icedove.
First, further to Andrew Sackville-West's (ASW) admonition Ken -- keep
on plugging away... you're getting closer, yes I am closer -- much
closer in fact -- but not out of the woods yet.
In view the fact that the first thing everybody advised me to do was to
disable artsd. On examination I
I haven't even read this entire (huge) thread, but it seems strange to me
that KDE applications don't work with arts.
Can it be that the apps are misconfigured to use ALSA directly but you are
running arts? You should either:
1)Leave arts on with application set up to use it
or
2)Set
On Saturday 17 March 2007 11:12, Ken Heard wrote:
Another factor may or may not be relevant. Two days ago I compiled
from source and installed dosemu-1.3.4. The installation was successful
in that it is allowing me to use my beloved dos based applications.
However, the last message returned
2007/3/16, Ken Heard [EMAIL PROTECTED]:
I assume that in alsamixer, at the bottom of each slide there should a
00 indication, not MM, to indicate open. The master and PCM
(What is PCM?) were 00 and full on, but not the others. For good
measure I changed them all to 00 and full on. I still
Raffaele Morelli wrote:
1. Try kill artsd deamon if running...
2. from a root shell /etc/alsa reload
2. lsmod | grep snd, so you are sure that snd modules are loaded
4. cat /dev/urandom /dev/audio do you hear something? (white noise)
5. if you got xine installed (dvd video player) try a DVD,
LAP:~# artsd stop
Link points to /tmp/ksocket-root
can't create mcop directory
I usually kill artsd
LAP:~# /etc/alsa reload
-su: /etc/alsa: is a directory
sorry, it was /etc/init.d/alsa reload
LAP:~# lsmod|grep snd
snd_opl3_synth 13924 0
snd_seq_instr 7392 1
Raffaele Morelli wrote:
LAP:~# artsd stop
Link points to /tmp/ksocket-root
can't create mcop directory
I usually kill artsd
I tried:
LAP:/# kill artsd
-su: kill: artsd: arguments must be process or job IDs
LAP:~# /etc/alsa reload
-su: /etc/alsa: is a directory
Also found the following:
LAP:/# find -iname isapnp
./sys/module/snd_opl3sa2/parameters/isapnp
./usr/src/linux-headers-2.6.18-4/drivers/pnp/isapnp
LAP:/#
Ken Heard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
LAP:/# kill artsd
-su: kill: artsd: arguments must be process or job IDs
Ken, you need further manual reading about processes management.
man ps
man kill
man killall
LAP:~# /etc/alsa reload
-su: /etc/alsa: is a directory
sorry, it was /etc/init.d/alsa reload
LAP:/#
On Friday 16 March 2007 15:26, Ken Heard wrote:
Raffaele Morelli wrote:
LAP:~# artsd stop
Link points to /tmp/ksocket-root
can't create mcop directory
I usually kill artsd
I tried:
LAP:/# kill artsd
-su: kill: artsd: arguments must be process or job IDs
You can disable
On Fri, Mar 16, 2007 at 03:52:46PM +0100, Raffaele Morelli wrote:
no isa-pnp module to load...
... I think you need some isa related tool to deal with this card or an
isa
capable kernel, i.e. recompile with isa support flag turned on.
I don't want to mislead you but I would go this way.
On Fri, 16 Mar 2007 15:52:46 +0100
Raffaele Morelli [EMAIL PROTECTED] wrote:
LAP:/# kill artsd
-su: kill: artsd: arguments must be process or job IDs
Ken, you need further manual reading about processes management.
man ps
man kill
man killall
Which makes me wonder: what's the
I have always known that sound was available on Linux. When I first
used Linux RH8 with KDE in a P4 box, I did not have sound on
installation in July 2003. At the time it was all I could do to get
working what I really needed; sound was not a priority. I did not
really miss it because I
On Thu, Mar 15, 2007 at 04:02:46PM +0700, Ken Heard wrote:
I have always known that sound was available on Linux. When I first
used Linux RH8 with KDE in a P4 box, I did not have sound on
installation in July 2003. At the time it was all I could do to get
working what I really needed;
2007/3/15, Ken Heard [EMAIL PROTECTED]:
I have always known that sound was available on Linux. When I first
used Linux RH8 with KDE in a P4 box, I did not have sound on
installation in July 2003. At the time it was all I could do to get
working what I really needed; sound was not a priority.
Raffaele Morelli wrote:
2007/3/15, Ken Heard [EMAIL PROTECTED]:
You miss alsa* packages, they are the only thing you need.
Just have a look to discover output to investigate if your laptop ships a
somewhat strange soundcard model.
you should also add the user to the group audio (and video
you should also add the user to the group audio (and video ?).
Yes, user must be in group 'audio' but I never did it manually...
Are you sure about the need of manual adds?
Or some post/pre installation scripts takes care about that?
regards
raffaele
On Thu, 15 Mar 2007 13:55:17 +0100
Raffaele Morelli [EMAIL PROTECTED] wrote:
you should also add the user to the group audio (and video ?).
Yes, user must be in group 'audio' but I never did it manually...
Are you sure about the need of manual adds?
Or some post/pre installation scripts
Celejar wrote:
The default groups to which new users are added (when created with
'adduser --add-extra-groups') is specified in '/etc/adduser.conf' by
the line beginning 'EXTRA_GROUPS'
Cool! I didn't know that. Just learned something. Thanks!
--
Kent West
http://kentwest.blogspot.com
Celejar wrote:
The default groups to which new users are added (when created with
'adduser --add-extra-groups') is specified in '/etc/adduser.conf' by
the line beginning 'EXTRA_GROUPS'; the default does include 'audio'. On
my Sid system, the (non-root) user that I created during install
On Thu, 15 Mar 2007 10:22:32 -0500
Kent West [EMAIL PROTECTED] wrote:
Celejar wrote:
The default groups to which new users are added (when created with
'adduser --add-extra-groups') is specified in '/etc/adduser.conf' by
the line beginning 'EXTRA_GROUPS'
Cool! I didn't know
On Thu, 15 Mar 2007 16:31:15 +0100
Johannes Wiedersich [EMAIL PROTECTED] wrote:
Celejar wrote:
The default groups to which new users are added (when created with
'adduser --add-extra-groups') is specified in '/etc/adduser.conf' by
the line beginning 'EXTRA_GROUPS'; the default does include
Johannes Wiedersich wrote:
you should also add the user to the group audio (and video ?).
as root:
# adduser your-user-name audio
# adduser your-user-name video
Both the users had already been added to those two groups, but not by me.
Regards,
Ken Heard
--
Kevin Mark wrote:
the alsa packages are needed.
IIRC alsa-base,alsa-tools,alsa-utils.
the run as root:
alsaconf
and it should do the rest.
I already had installed alsa-base and alsa-utils, but not alsa-tools; so
I installed alsa-tools and alsa-tool-gui; aptitude also installed one
lib file.
Ken Heard wrote:
I already had installed alsa-base and alsa-utils, but not alsa-tools; so
I installed alsa-tools and alsa-tool-gui; aptitude also installed one
lib file. I then ran as root alsaconf which did its thing, including
detecting the builtin sound card, and told me to enjoy.
On Fri, Mar 16, 2007 at 08:29:07AM +0700, Ken Heard wrote:
Kevin Mark wrote:
the alsa packages are needed.
IIRC alsa-base,alsa-tools,alsa-utils.
the run as root:
alsaconf
and it should do the rest.
I already had installed alsa-base and alsa-utils, but not alsa-tools; so
I installed
I assume that in alsamixer, at the bottom of each slide there should a
00 indication, not MM, to indicate open. The master and PCM
(What is PCM?) were 00 and full on, but not the others. For good
measure I changed them all to 00 and full on. I still could not open
an audio CD or a newscast.
Ken Heard wrote:
I then exited my user and entered it again. As instructed I ran
aplay /usr/share/sound/alsa/*.wav which returned the following:
aplay: main:550: audio open error: Device or resource busy
If you did this from within X (or with X running), shut down X
completely and try again.
Während es mit OpenOffic.org Impress 1.1.3 von SuSE 9.2 kein Problem
gab, den Sound einer Präsentation unter Windows abzuspielen, die
unter Linux erstellt wurde, funktioniert das unter Debian / Sarge
nicht.
Unter Debian sind diese Pakete installiert:
ii openoffice.org 1.1+20040420-2
-Original Message-
From: news [mailto:[EMAIL PROTECTED] Behalf Of Andreas Janssen
Sent: Saturday, February 28, 2004 5:02 PM
To: [EMAIL PROTECTED]
Subject: Re: Sound and Linux Kernel 2.6
Hello
MacNean Tyrrell ([EMAIL PROTECTED]) wrote:
Ok so I have Debian installed, and I like
Andreas Janssen, thanks so much, best help every. Sound now works. SO
happy. Thanks again.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Ok so I have Debian installed, and I like it a lot, but I cant get the
sound card to work, cant even get ALSA to work. So I decided to just run Knoppix from the CD drive, and it
successfully detects my sound card, and it works there. I really dont want to use Knoppix,
just want to use
Hello
MacNean Tyrrell ([EMAIL PROTECTED]) wrote:
Ok so I have Debian installed, and I like it a lot, but I can't get
the sound card to work, can't even get ALSA to work. So I decided to
just run Knoppix from the CD drive, and it successfully detects my
sound card, and it works there. I
Janssen
Sent: Saturday, February 28, 2004 5:02 PM
To: [EMAIL PROTECTED]
Subject: Re: Sound and Linux Kernel 2.6
Hello
MacNean Tyrrell ([EMAIL PROTECTED]) wrote:
Ok so I have Debian installed, and I like it a lot, but I can't get
the sound card to work, can't even get ALSA to work. So I decided
Hello,
I just want to express my appreciation for all the help I've gotten from the members of this list. I'm practically a Linux newbie, so all of the configuration that's needed to get it up and running is unfamiliar to me. I'd like to know how I could get my ESS Audiodrive sound card to work
Most SB compatibles mean the SB16 'standard'.
You need to add the lines
soundcore
sb
to /etc/modules to get it to load at boot.
and run insmod soundcore and insmod sb to get it to run now.
On Wed, Aug 22, 2001 at 06:53:35AM -0700, David Frischknecht scribbled...
Hello,
I just want to
On Wed, Aug 22, 2001 at 08:42:10AM -0700, Jason Majors wrote:
Most SB compatibles mean the SB16 'standard'.
You need to add the lines
soundcore
sb
to /etc/modules to get it to load at boot.
and run insmod soundcore and insmod sb to get it to run now.
On Wed, Aug 22, 2001 at 06:53:35AM
Am getting ready to reinstall onto my shiny empty 6G drive in a Compaq
Presario 4840, and would like to avoid the only problem I had last time -
the sound wouldn't work. No playing CD's :-( It auto-recognized the ATI Rage
Pro AGP, the Compaq DVD, everything, but the sound didn't function at all,
On Wed, 24 Mar 1999, Hogland, Thomas E. wrote:
Am getting ready to reinstall onto my shiny empty 6G drive in a Compaq
Presario 4840, and would like to avoid the only problem I had last time -
the sound wouldn't work. No playing CD's :-( It auto-recognized the ATI Rage
Pro AGP, the Compaq DVD,
I have just installed the new version of RealAudio, but there is no sound.
I get the following message in /usr/adm/messages:
Oct 16 09:25:32 OZ kernel: Sound error: Couldn't allocate DMA buffer
sound does work for me in RealAudio 3.0 and other application.
Any ideas?
-Oz
--
NAME Oz Dror,
On Thu, 16 Oct 1997, Oz Dror wrote:
I have just installed the new version of RealAudio, but there is no sound.
I get the following message in /usr/adm/messages:
Oct 16 09:25:32 OZ kernel: Sound error: Couldn't allocate DMA buffer
sound does work for me in RealAudio 3.0 and other
Oz Dror wrote:
I have just installed the new version of RealAudio, but there is no sound.
I get the following message in /usr/adm/messages:
Oct 16 09:25:32 OZ kernel: Sound error: Couldn't allocate DMA buffer
sound does work for me in RealAudio 3.0 and other application.
Any ideas?
51 matches
Mail list logo
