On Jul 8, 2007, at 7:12 PM, Chip G. wrote:
is it certain to he the driver?
Nope. I was getting pretty wound up trying to solve a similar
problem. It eventually occurred to me that my faithful Keyspan
device might actually be dead. It was.
-Jason
kg4wsv
___
--- "Chip G." <[EMAIL PROTECTED]> wrote:
> I'd love to hear other suggestions. If the problem
> does relate to the
> USB adapter, is there any chance it relates to the
> Xastir code? Or is
> it certain to he the driver?
I doubt it's Xastir because Xastir doesn't really know
it's a USB device.
On Jul 5, 2007, at 07:34, N1OFZ wrote:
I have had Xastir running here for over a month and I've had it run
even longer with no usb dongles. I ONLY use Keyspan usb -> serial
adapters on the Mac. I have others that are Prolific based and
have had varying success, though they run fine under
Hi Chip,
I have had Xastir running here for over a month and I've had it run
even longer with no usb dongles. I ONLY use Keyspan usb -> serial
adapters on the Mac. I have others that are Prolific based and have
had varying success, though they run fine under Linux. Last year I
did a 5
On Jul 4, 2007, at 15:46, Chip G. wrote:
It made it at least 4.5 hours, but it did eventually freeze. So it
wasn't the bleeding edge release since the stable release is having
the same problem. The latest version of the USB driver has the same
problem. I guess the next step will be to resta
On Jul 4, 2007, at 09:02, Jason Winningham wrote:
On Jul 4, 2007, at 4:30 AM, Chip G. wrote:
So far I've changed two things. I recompiled with a stable
release. I installed an updated USB driver. We'll see if the two
help. If everything is stable I'll try going back to the latest
release.
On Jul 2, 2007, at 9:34 PM, Curt Mills wrote:
Note: I'm not a Mac user, but _am_ a Unix and Linux user/SysAdmin,
me too...
so I'm not sure how fragile a Mac is these days. I would think not
very fragile...
nope, not at all. I personally rank it just below solaris and above
linux in r
On Mon, 2 Jul 2007, Chip G. wrote:
> A couple of notes. Do not fixate on the kill command format used here. I had
> just randomly found that a -4 would at least get it to try and quit (I'm
> assuming that's what the parenthesis mean), no other command would even cause
> a change.
Just for future
On Mon, 2 Jul 2007, Chip G. wrote:
> And locked up again between 9:55PM and 10:08PM while writing the email. It is
> completely unusable again on this end, at least on that machine. I'm going to
> have to spend an entire day trying to clean things and reinstall everything
> again.
Reinstall what?
On Mon, Jul 02, 2007 at 09:41:36PM -0500, we recorded a bogon-computron
collision of the <[EMAIL PROTECTED]> flavor, containing:
>
> > 1. Why are three processes starting every time Xastir runs and what are the
> > other processes doing?
>
> I dunno, but they are supposed to be there. add dif
On Jul 2, 2007, at 9:06 PM, Chip G. wrote:
I have no idea what some of that stuff means ... time to RTFM for ps.
USER PID %CPU %MEM VSZRSS TT STAT STARTED TIME
COMMAND
jdw232 2.1 0.056044476 p1 RFri06AM 103:52.88
xastir
jdw231 0.8
On Jul 2, 2007, at 22:06, Chip G. wrote:
3. Why does the latest CVS builds on Xastir lockup after only a
couple of hours operating?
And locked up again between 9:55PM and 10:08PM while writing the
email. It is completely unusable again on this end, at least on that
machine. I'm going to h
I've written about this before. Never did get resolution. Now it's a
problem again. Xastir is locking up on me after only a couple of
hours of operation. This is a royal PITA because when it locks up I
can't get it to quit unless I reboot the computer. I've tried kill
and killall commands.
13 matches
Mail list logo
