Gnome, esd and i810_audio-- they can work together
Currently, when configured to start the sound server, gnome-session starts esd with only the "-nobeeps" option. I have submitted a patch under http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=170843 that allows gnome-session to honor the ESD_SPAWN_OPTIONS variable. This is a very useful patch for people (like me) who have to run esd at a specific sample rate for esd to work at all. I have a laptop that uses the i810_audio driver, which would eventually hang when I enable sound under gnome. With the patch applied, I simply dropped: ESD_SPAWN_OPTIONS="-terminate -as 5 -nobeeps -r 48000" into /etc/environment, and I haven't had a gnome hang since. As the patch hasn't been accepted yet, I thought I would let other gnome and laptop users know about the patch. James Strandboge -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
Re: Gnome, esd and i810_audio-- they can work together
On Wed, 2002-12-11 at 15:16, Bas Zoetekouw wrote: > Hi James! > > You wrote: > > > enable sound under gnome. With the patch applied, I simply dropped: > > ESD_SPAWN_OPTIONS="-terminate -as 5 -nobeeps -r 48000" > > into /etc/environment, and I haven't had a gnome hang since. > > Uhm, why not just put the options in /etc/esound/esd.conf? > Because esd doesn't read esd.conf when its not in autospawn mode. Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
Re: Bug#170843: status of patch
On Wed, 2002-12-11 at 14:46, Christian Marillat wrote: > James D Strandboge <[EMAIL PROTECTED]> writes: > > > I was just wondering what is the status of this patch? I looked at > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=170843 and it doesn't > > look like anything is happening with it. I can say that it has been > > working flawlessly for 3 weeks now on my system. > > Because esound doesn't load is config file in /etc/esound/esd.conf > > And if your read gnome.bugzilla.org this bug has been already reported. > I read http://bugzilla.gnome.org/show_bug.cgi?id=88253, before which is why I came up with this patch in the first. If I understand correctly, esd.conf is supposed to be used for autospawn only. If you start up esd from the command line, or the way gnome does, esd.conf is not brought in. That esd only reads esd.conf in autospawn mode is an esd bug, and this patch doesn't fix this issue. > Then your patche is simply a workaround and not a definitive patche. > But, I do not agree that this is just a workaround. esd by itself will honor ESD_SPAWN_OPTIONS, but gnome-session doesn't because of the way esd is started. Since gnome-session is starting esd, isn't it reasonable to have gnome-session pass ESD_SPAWN_OPTIONS to esd? I think so. A separate esound patch regarding esd.conf should be made, but this patch addresses a different (albeit related) issue. Granted, if the esd.conf patch was there, we may not be having this conversation, but that doesn't necessarily mean that this isn't a proper fix. Both should happen. What is your thinking? Jamie PS-- because I was working with a debian package, I issued the report through the debian bug tracker. Is it your opinion that I should have issued it through bugzilla.gnome.org and just have upstream deal with it? I thought upstream would get a coppy of this based on what reportbug said. -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
Re: Bug#170843: status of patch
On Wed, 2002-12-11 at 21:25, Chipzz wrote: > On 11 Dec 2002, James D Strandboge wrote: > > > From: James D Strandboge <[EMAIL PROTECTED]> > > Subject: Re: Bug#170843: status of patch > > > But, I do not agree that this is just a workaround. esd by itself will > > honor ESD_SPAWN_OPTIONS, but gnome-session doesn't because of the way > > I think this option is horribly wrong. Why use it at all when you can > start esd with > 'esd `cat /etc/esound/esd.conf`' > ? Another option just adds to the copmplexity and will confuse the user. > Editing esd.conf is how he expects it to work, you clearly did ;), and > adding this option will require documentation. > Can you give a good reason why "yet another option (tm)" is a good > thing? > I think this is a far argument. The intent was not to introduce yet another option, but rather have gnome-session utilize an already existing esd option. Unfortunately, just editing esd.conf at this time does not work. Your 'cat' proposition is fine for the command line, but awkward in code IMO. I have thought about this issue more because of the feedback (which is why I sent the email to the list in the first place). Although I still think having gnome-session pass ESD_SPAWN_OPTIONS to esd is valid, gnome-session and esd are fairly tightly coupled with or without my patch. As such, I have implemented a patch for esd that makes it honor esd.conf if esd is called without arguments. This means that gnome-session doesn't have to do anything special for esd to work, and the user can put whatever is needed into esd.conf for his or her soundcard, and gnome and esd "will just work". Expect it, and an explanation shortly. Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
[patch] make esd read esd.conf when autospawn not enabled
This patch is sent to debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=172722 This patch also addresses these esd bugs: http://bugzilla.gnome.org/show_bug.cgi?id=97138 http://bugzilla.gnome.org/show_bug.cgi?id=88253 http://bugzilla.gnome.org/show_bug.cgi?id=3558 http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=125803 Provides a solution for these bugs: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=122627 http://bugzilla.gnome.org/show_bug.cgi?id=3558 and addresses this gnome-session bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=170843 When esd is called from within gnome or on the command line, and not setup to autospawn, esd ignores the contents of esd.conf (eg spawn_options=-nobeeps -r 48000). This patch makes esd read in esd.conf if it is called without arguments (and ESD_SPAWN_OPTIONS is unset). Though other behaviors are possible, this made the most sense to me: if the user supplies command line arguments, then assume the user knows what he or she is doing and don't merge in esd.conf. Likewise for ESD_SPAWN_OPTIONS. The benefits of this patch are twofold. 1. the user can adjust a single configuration file, rather than having to worry about environment variables and command line arguments. It also keeps users from wondering why adjusting esd.conf doesn't do anything when esd is not set to autospawn (its default behavior). 2. this patch decouples gnome-session from having to know what options are used to set esd (eg, '-nobeeps'). The esound packager can simply put in reasonable defaults into esd.conf, and gnome-session will just work. Because this patch only reads esd.conf if esd is called with no options, gnome-session would need to be recompiled to not pass esd any options (trivial). The patch is based on the existing code in esound. First, I created esd-config.h, and just pulled a couple of defines out of esd_config.c and put them into esd-config.h, so I could use them in esd.c. I did a small cleanup to get rid of a compilation warning for the strtok_r define. After that, the only change to esd_config.c is to include esd-config.h. The main part of the patch is a modification to esd.c, in main(). Basically, I reference esd_spawn_options in esd_config.c in the same manner that esdlib.c does (ie via extern). Then, if argc > 1, nothing is changed-- command line arguments are processed. If argc == 1, then I call esd_config_read() (from esd_config.c), tokenize esd_spawn_options and then they are processed with the same code that processes argv. To make the code cleaner, I made: num_opts = argc; opts = argv; and then just use num_opts and opts in place of argc and argv for parsing the arguments. The net effect is that if esd is called without arguments, I create arguments for it based on the 'spawn_options' line in esd.conf. Because I am using esd_config_read(), ESD_SPAWN_OPTIONS are also honored. To apply, save the patch to the directory that esound-0.2.28 is in, and do: cd esound-0.2.28 cat ../esound-0.2.28.esdconf.patch | patch -p1 Thanks, Jamie Strandboge PS-- If you are going to patch gnome-session like I suggested above, I killed esd, logged out of gnome, and then killed off gconf and oaf for good measure before logging back into gnome. Just logging out and back in kept the old esd options rather than the ones in esd.conf. -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A diff -Naur esound-0.2.28-old/esd-config.h esound-0.2.28/esd-config.h --- esound-0.2.28-old/esd-config.h Wed Dec 31 19:00:00 1969 +++ esound-0.2.28/esd-config.h Wed Dec 11 20:57:41 2002 @@ -0,0 +1,20 @@ +#ifndef ESD_CONFIG_H +#define ESD_CONFIG_H + +#include + +/* these are some defines to use in when reading + * esd.conf */ + +#define LINEBUF_SIZE 1024 + +/* use strtok_r if available */ +#ifdef HAVE_STRTOK_R +#define DO_STRTOK(S,DELIM) strtok_r(S,DELIM,strtok_state) +char *strtok_state[LINEBUF_SIZE]; +#else +#define DO_STRTOK(S,DELIM) strtok(S,DELIM) +#endif + +#endif + diff -Naur esound-0.2.28-old/esd.c esound-0.2.28/esd.c --- esound-0.2.28-old/esd.c Wed Dec 11 23:10:12 2002 +++ esound-0.2.28/esd.c Wed Dec 11 21:09:01 2002 @@ -1,4 +1,5 @@ #include "esd-server.h" +#include "esd-config.h" #include #include @@ -8,6 +9,8 @@ #include #include +#include + #ifndef HAVE_NANOSLEEP #include #include @@ -504,6 +507,14 @@ char *hostname=NULL; +/* from esd_config.c */ +extern char esd_spawn_options[]; + +char tmp_str[LINEBUF_SIZE]; +int num_opts = 0; +char **opts; +char *tok; + /* begin test scaffolding parameters */ /* int format = AFMT_U8; AFMT_S16_LE; */ /* int stereo = 0; */ /* 0=mono, 1=stereo */ @@ -518,100 +529,125 @@ programname = *argv; +/* use opts instead of modifying argv, because that is just + * too weird */ +opts = argv; +num_opts = argc; + +/* if we were called with no arguments, read
Re: X crashes if I'm idle
On Thu, 2003-01-23 at 14:17, Frank Trenkamp wrote: > Hi Ivan, > > > X is in VESA mode, as the Thinkpad has unsupported Radeon video. > > Mobility 7500 Radeon? You will most surely need XFree 4.2.x, by now > finally available in in unstable (and testing? dunno). I've been using an > install from binaries from XFree86.org - running fine for months now. > This is definitely true. There are woody debs available that work great too. > > If I'm in X (Gnome) and I'm idle for a while (10 mins?) X crashes. The > > error messages seem to be to do with trying to run a screensaver. Now, > > I have xscreensaver installed, but opening Gnome Control Center's > > screensaver tab causes X to crash instantly. Same thing happens when > > xscreensaver is not installed. I'm happy not to have a screensaver, > > and/or for the screen to just go blank like it does when in console mode. > The Star Wars screensaver (opengl believe it or not) always locked up my machine. Others may have too, but I pinpointed it to that one. Upgrading X solved it IIRC. Also try upgrading xscreensaver if you are using woody. I know for a while, I just made sure I didn't use opengl screensavers. Jamie Strandboge -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
Re: HDD not spinning down
On Sun, 2003-02-02 at 20:55, Jeff wrote: > René Seindal, 2003-Feb-02 09:33 +0100: > > I can't remember how you control the frequency of postfix queue runs. > Just add this to /etc/postfix/main.cf: defer_transports = smtp and then you can run 'sendmail -q' from cron at whatever interval you want. Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
Re: Setting up i810 audio ?!?
On Fri, 2003-02-21 at 03:05, Alberto Gonzalez Iniesta wrote: > On Thu, Feb 20, 2003 at 10:09:13PM +, Joao Pedro Clemente wrote: > > > > > > Can we get i810 audio hardware to work with the standart 2.4.18-bf24 > > > > kernel? > > > > > > # modprobe i810_audio > > > > > > Should do. It's included in 2.4.18-bf24, and I've been using the sound > > > card without problems for some time now. > > > > Wel, the funny thing is... I got that module inserted. > > The problem I'm facing is that KDE does not see any soundcard. xmms (over > > kde) fails reporting that there is no soundcar or soundcard is locked. > > > > Maybe this is one of those issues with arts (The kde sound daemon)? > > > > So, if the module is inserted, the audio should be fine? Any ideia on how > > to test it, besides using xmms? > > Yep, it seems to be a problem with Arts. The trick with most hardware using i810_audio is that it can only be used at the specific rate of 48000. I use esd, and it has a way to specify the rate. I am sure arts does too. Jamie Strandboge -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
Re: Setting up i810 audio ?!?
On Fri, 2003-02-21 at 22:25, Sunny Wu wrote: > Hi, > > Hmm, my i810 audio is fine under KDE3.1 if i only have one application using > the sound channel > at a time. Does anyone know if i can hve 2 apps making asound output at the > same time?? I > have tried aumix and still have the same problem? > This is the job of your sound server, artsd. It should be able to handle more than one app. If you disabled artsd, you can still use the soundcard, but only one app at a time. Is this consistent with your setup? Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
Re: Setting up i810 audio ?!?
On Sat, 2003-02-22 at 01:13, Sunny Wu wrote: > Yeah i tried to enable the arts soundserver. > But it still doesnt mix the sounds output from more than 1 app. > And not long after, it will show a "Fatal error: CPU Overload" error. > KDE users need to help more with this. You need to make sure that artsd uses i810_audio with a rate of 48000 only. You might look at duplex settings as well. Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
Re: dell inspiron 8200: fax suspend audio
On Thu, 2003-03-27 at 10:12, Marco Menchise wrote: > Hello, > > I have a Dell Inspiron 8200 - NVidia Ge Force 2 - kernel 2.4.20 - debian woody > > I managed to use all hardware with linux except: > > 1) suspend mode under X - I patched the NVidia driver, and I get the > notebook to suspend, but I can't resume session > This is possible if you come out of X first. You can script all of this too with the apm scripts if so desired. > 2) use the winmodem for sending and receiving fax > I haven't tried faxes, but the modem works fine with the hsflinmodem drivers > 3) using Intel AC'97 Audio card with RTP/VOIP application (I'm able to > play sound) Use alsa drivers. 0.9.0rc7 is the first version that I found where everything worked right. They are actually quite good. Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
Re: blank screen when trying to install woody
On Tue, 2002-09-10 at 16:58, TT logic wrote: > hi there > > when I try to install debian 3.0 when I boot from the cd and press Enter at > the boot prompt the screen becoms black and after a few seconds white and > nothing shows up ... I tryed with several kernels but its hte same ... my > laptop is Packard Bell (Easy One Silver) / video SiS 630/730 / 240Mb Ram / > Celeron 1.3GHz ... I think it is somthing with my videocard but Im sure it > has support under linux > Try something along the lines of (at the boot prompt after starting up with the 1st woody cd): boot: bf24 video=vga16:off and hopefully it will work. Jamie
Gnome, esd and i810_audio-- they can work together
Currently, when configured to start the sound server, gnome-session starts esd with only the "-nobeeps" option. I have submitted a patch under http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=170843 that allows gnome-session to honor the ESD_SPAWN_OPTIONS variable. This is a very useful patch for people (like me) who have to run esd at a specific sample rate for esd to work at all. I have a laptop that uses the i810_audio driver, which would eventually hang when I enable sound under gnome. With the patch applied, I simply dropped: ESD_SPAWN_OPTIONS="-terminate -as 5 -nobeeps -r 48000" into /etc/environment, and I haven't had a gnome hang since. As the patch hasn't been accepted yet, I thought I would let other gnome and laptop users know about the patch. James Strandboge -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Gnome, esd and i810_audio-- they can work together
On Wed, 2002-12-11 at 15:16, Bas Zoetekouw wrote: > Hi James! > > You wrote: > > > enable sound under gnome. With the patch applied, I simply dropped: > > ESD_SPAWN_OPTIONS="-terminate -as 5 -nobeeps -r 48000" > > into /etc/environment, and I haven't had a gnome hang since. > > Uhm, why not just put the options in /etc/esound/esd.conf? > Because esd doesn't read esd.conf when its not in autospawn mode. Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#170843: status of patch
On Wed, 2002-12-11 at 14:46, Christian Marillat wrote: > James D Strandboge <[EMAIL PROTECTED]> writes: > > > I was just wondering what is the status of this patch? I looked at > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=170843 and it doesn't > > look like anything is happening with it. I can say that it has been > > working flawlessly for 3 weeks now on my system. > > Because esound doesn't load is config file in /etc/esound/esd.conf > > And if your read gnome.bugzilla.org this bug has been already reported. > I read http://bugzilla.gnome.org/show_bug.cgi?id=88253, before which is why I came up with this patch in the first. If I understand correctly, esd.conf is supposed to be used for autospawn only. If you start up esd from the command line, or the way gnome does, esd.conf is not brought in. That esd only reads esd.conf in autospawn mode is an esd bug, and this patch doesn't fix this issue. > Then your patche is simply a workaround and not a definitive patche. > But, I do not agree that this is just a workaround. esd by itself will honor ESD_SPAWN_OPTIONS, but gnome-session doesn't because of the way esd is started. Since gnome-session is starting esd, isn't it reasonable to have gnome-session pass ESD_SPAWN_OPTIONS to esd? I think so. A separate esound patch regarding esd.conf should be made, but this patch addresses a different (albeit related) issue. Granted, if the esd.conf patch was there, we may not be having this conversation, but that doesn't necessarily mean that this isn't a proper fix. Both should happen. What is your thinking? Jamie PS-- because I was working with a debian package, I issued the report through the debian bug tracker. Is it your opinion that I should have issued it through bugzilla.gnome.org and just have upstream deal with it? I thought upstream would get a coppy of this based on what reportbug said. -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#170843: status of patch
On Wed, 2002-12-11 at 21:25, Chipzz wrote: > On 11 Dec 2002, James D Strandboge wrote: > > > From: James D Strandboge <[EMAIL PROTECTED]> > > Subject: Re: Bug#170843: status of patch > > > But, I do not agree that this is just a workaround. esd by itself will > > honor ESD_SPAWN_OPTIONS, but gnome-session doesn't because of the way > > I think this option is horribly wrong. Why use it at all when you can > start esd with > 'esd `cat /etc/esound/esd.conf`' > ? Another option just adds to the copmplexity and will confuse the user. > Editing esd.conf is how he expects it to work, you clearly did ;), and > adding this option will require documentation. > Can you give a good reason why "yet another option (tm)" is a good > thing? > I think this is a far argument. The intent was not to introduce yet another option, but rather have gnome-session utilize an already existing esd option. Unfortunately, just editing esd.conf at this time does not work. Your 'cat' proposition is fine for the command line, but awkward in code IMO. I have thought about this issue more because of the feedback (which is why I sent the email to the list in the first place). Although I still think having gnome-session pass ESD_SPAWN_OPTIONS to esd is valid, gnome-session and esd are fairly tightly coupled with or without my patch. As such, I have implemented a patch for esd that makes it honor esd.conf if esd is called without arguments. This means that gnome-session doesn't have to do anything special for esd to work, and the user can put whatever is needed into esd.conf for his or her soundcard, and gnome and esd "will just work". Expect it, and an explanation shortly. Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[patch] make esd read esd.conf when autospawn not enabled
This patch is sent to debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=172722 This patch also addresses these esd bugs: http://bugzilla.gnome.org/show_bug.cgi?id=97138 http://bugzilla.gnome.org/show_bug.cgi?id=88253 http://bugzilla.gnome.org/show_bug.cgi?id=3558 http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=125803 Provides a solution for these bugs: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=122627 http://bugzilla.gnome.org/show_bug.cgi?id=3558 and addresses this gnome-session bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=170843 When esd is called from within gnome or on the command line, and not setup to autospawn, esd ignores the contents of esd.conf (eg spawn_options=-nobeeps -r 48000). This patch makes esd read in esd.conf if it is called without arguments (and ESD_SPAWN_OPTIONS is unset). Though other behaviors are possible, this made the most sense to me: if the user supplies command line arguments, then assume the user knows what he or she is doing and don't merge in esd.conf. Likewise for ESD_SPAWN_OPTIONS. The benefits of this patch are twofold. 1. the user can adjust a single configuration file, rather than having to worry about environment variables and command line arguments. It also keeps users from wondering why adjusting esd.conf doesn't do anything when esd is not set to autospawn (its default behavior). 2. this patch decouples gnome-session from having to know what options are used to set esd (eg, '-nobeeps'). The esound packager can simply put in reasonable defaults into esd.conf, and gnome-session will just work. Because this patch only reads esd.conf if esd is called with no options, gnome-session would need to be recompiled to not pass esd any options (trivial). The patch is based on the existing code in esound. First, I created esd-config.h, and just pulled a couple of defines out of esd_config.c and put them into esd-config.h, so I could use them in esd.c. I did a small cleanup to get rid of a compilation warning for the strtok_r define. After that, the only change to esd_config.c is to include esd-config.h. The main part of the patch is a modification to esd.c, in main(). Basically, I reference esd_spawn_options in esd_config.c in the same manner that esdlib.c does (ie via extern). Then, if argc > 1, nothing is changed-- command line arguments are processed. If argc == 1, then I call esd_config_read() (from esd_config.c), tokenize esd_spawn_options and then they are processed with the same code that processes argv. To make the code cleaner, I made: num_opts = argc; opts = argv; and then just use num_opts and opts in place of argc and argv for parsing the arguments. The net effect is that if esd is called without arguments, I create arguments for it based on the 'spawn_options' line in esd.conf. Because I am using esd_config_read(), ESD_SPAWN_OPTIONS are also honored. To apply, save the patch to the directory that esound-0.2.28 is in, and do: cd esound-0.2.28 cat ../esound-0.2.28.esdconf.patch | patch -p1 Thanks, Jamie Strandboge PS-- If you are going to patch gnome-session like I suggested above, I killed esd, logged out of gnome, and then killed off gconf and oaf for good measure before logging back into gnome. Just logging out and back in kept the old esd options rather than the ones in esd.conf. -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A diff -Naur esound-0.2.28-old/esd-config.h esound-0.2.28/esd-config.h --- esound-0.2.28-old/esd-config.h Wed Dec 31 19:00:00 1969 +++ esound-0.2.28/esd-config.h Wed Dec 11 20:57:41 2002 @@ -0,0 +1,20 @@ +#ifndef ESD_CONFIG_H +#define ESD_CONFIG_H + +#include + +/* these are some defines to use in when reading + * esd.conf */ + +#define LINEBUF_SIZE 1024 + +/* use strtok_r if available */ +#ifdef HAVE_STRTOK_R +#define DO_STRTOK(S,DELIM) strtok_r(S,DELIM,strtok_state) +char *strtok_state[LINEBUF_SIZE]; +#else +#define DO_STRTOK(S,DELIM) strtok(S,DELIM) +#endif + +#endif + diff -Naur esound-0.2.28-old/esd.c esound-0.2.28/esd.c --- esound-0.2.28-old/esd.c Wed Dec 11 23:10:12 2002 +++ esound-0.2.28/esd.c Wed Dec 11 21:09:01 2002 @@ -1,4 +1,5 @@ #include "esd-server.h" +#include "esd-config.h" #include #include @@ -8,6 +9,8 @@ #include #include +#include + #ifndef HAVE_NANOSLEEP #include #include @@ -504,6 +507,14 @@ char *hostname=NULL; +/* from esd_config.c */ +extern char esd_spawn_options[]; + +char tmp_str[LINEBUF_SIZE]; +int num_opts = 0; +char **opts; +char *tok; + /* begin test scaffolding parameters */ /* int format = AFMT_U8; AFMT_S16_LE; */ /* int stereo = 0; */ /* 0=mono, 1=stereo */ @@ -518,100 +529,125 @@ programname = *argv; +/* use opts instead of modifying argv, because that is just + * too weird */ +opts = argv; +num_opts = argc; + +/* if we were called with no arguments, rea
Re: X crashes if I'm idle
On Thu, 2003-01-23 at 14:17, Frank Trenkamp wrote: > Hi Ivan, > > > X is in VESA mode, as the Thinkpad has unsupported Radeon video. > > Mobility 7500 Radeon? You will most surely need XFree 4.2.x, by now > finally available in in unstable (and testing? dunno). I've been using an > install from binaries from XFree86.org - running fine for months now. > This is definitely true. There are woody debs available that work great too. > > If I'm in X (Gnome) and I'm idle for a while (10 mins?) X crashes. The > > error messages seem to be to do with trying to run a screensaver. Now, > > I have xscreensaver installed, but opening Gnome Control Center's > > screensaver tab causes X to crash instantly. Same thing happens when > > xscreensaver is not installed. I'm happy not to have a screensaver, > > and/or for the screen to just go blank like it does when in console mode. > The Star Wars screensaver (opengl believe it or not) always locked up my machine. Others may have too, but I pinpointed it to that one. Upgrading X solved it IIRC. Also try upgrading xscreensaver if you are using woody. I know for a while, I just made sure I didn't use opengl screensavers. Jamie Strandboge -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: HDD not spinning down
On Sun, 2003-02-02 at 20:55, Jeff wrote: > René Seindal, 2003-Feb-02 09:33 +0100: > > I can't remember how you control the frequency of postfix queue runs. > Just add this to /etc/postfix/main.cf: defer_transports = smtp and then you can run 'sendmail -q' from cron at whatever interval you want. Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Setting up i810 audio ?!?
On Fri, 2003-02-21 at 03:05, Alberto Gonzalez Iniesta wrote: > On Thu, Feb 20, 2003 at 10:09:13PM +, Joao Pedro Clemente wrote: > > > > > > Can we get i810 audio hardware to work with the standart 2.4.18-bf24 > > > > kernel? > > > > > > # modprobe i810_audio > > > > > > Should do. It's included in 2.4.18-bf24, and I've been using the sound > > > card without problems for some time now. > > > > Wel, the funny thing is... I got that module inserted. > > The problem I'm facing is that KDE does not see any soundcard. xmms (over > > kde) fails reporting that there is no soundcar or soundcard is locked. > > > > Maybe this is one of those issues with arts (The kde sound daemon)? > > > > So, if the module is inserted, the audio should be fine? Any ideia on how > > to test it, besides using xmms? > > Yep, it seems to be a problem with Arts. The trick with most hardware using i810_audio is that it can only be used at the specific rate of 48000. I use esd, and it has a way to specify the rate. I am sure arts does too. Jamie Strandboge -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Setting up i810 audio ?!?
On Fri, 2003-02-21 at 22:25, Sunny Wu wrote: > Hi, > > Hmm, my i810 audio is fine under KDE3.1 if i only have one application using > the sound channel > at a time. Does anyone know if i can hve 2 apps making asound output at the > same time?? I > have tried aumix and still have the same problem? > This is the job of your sound server, artsd. It should be able to handle more than one app. If you disabled artsd, you can still use the soundcard, but only one app at a time. Is this consistent with your setup? Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Setting up i810 audio ?!?
On Sat, 2003-02-22 at 01:13, Sunny Wu wrote: > Yeah i tried to enable the arts soundserver. > But it still doesnt mix the sounds output from more than 1 app. > And not long after, it will show a "Fatal error: CPU Overload" error. > KDE users need to help more with this. You need to make sure that artsd uses i810_audio with a rate of 48000 only. You might look at duplex settings as well. Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dell inspiron 8200: fax suspend audio
On Thu, 2003-03-27 at 10:12, Marco Menchise wrote: > Hello, > > I have a Dell Inspiron 8200 - NVidia Ge Force 2 - kernel 2.4.20 - debian woody > > I managed to use all hardware with linux except: > > 1) suspend mode under X - I patched the NVidia driver, and I get the > notebook to suspend, but I can't resume session > This is possible if you come out of X first. You can script all of this too with the apm scripts if so desired. > 2) use the winmodem for sending and receiving fax > I haven't tried faxes, but the modem works fine with the hsflinmodem drivers > 3) using Intel AC'97 Audio card with RTP/VOIP application (I'm able to > play sound) Use alsa drivers. 0.9.0rc7 is the first version that I found where everything worked right. They are actually quite good. Jamie -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
