[PlanetCCRMA] Re: [Jackit-devel] cannot connect to jack server - cannot connect to default JACK server

[Mark Knecht]

Steve,
   No, actually I know the machine isn't totally 'suspending' when the
monitor turns off since the machine runs setiathome 24 hours a day, and that
continues to process ET data even when the monitor is turned off. It does
make me curious whether setiathome could possibly be the cause of the
problem itself. Setiathome does not make much use of the disk, but uses lots
of CPU cycles. I run it 'niced' so that it gets out of the way (supposedly)
and running it does not cause any xruns, so I hadn't thought much about
removing it. I actually wanted it running to sort of simulate the computer
being very busy but showing that the underlying audio stuff (alsa/jack) is
stable even under a heavier load.

   I'm in the process of trying the tests again having done Tim's xset
modification. If that doesn't work, then the next test is BIOS.

Cheers,
Mark

-----Original Message-----
From: planetccrma-admin@ccrma.Stanford.EDU
[mailto:planetccrma-admin@ccrma.Stanford.EDU]On Behalf Of Steve Harris
Sent: Wednesday, October 23, 2002 10:32 AM
To: 'PlanetCCRMA (E-mail)'; 'Jackit-List (E-mail)'
Subject: Re: [PlanetCCRMA] Re: [Jackit-devel] cannot connect to jack
server - cannot connect to default JACK server


On Wed, Oct 23, 2002 at 10:19:14 -0700, Mark Knecht wrote:
> OK, the orange light seems to definitely correspond with when this problem
> starts, and doing things from the remote SSH terminal doesn't change the
> state of the light, so maybe I can try a few things more quickly from
here.

OK, it isn't suspending then, or you wouldn't be able to ssh in.
I'm stumped, I dont see how monitor power managment could affect the sound
system.

- Steve
_______________________________________________
PlanetCCRMA mailing list
PlanetCCRMA@ccrma.stanford.edu
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma