Following up on the message below, my two serial ports were indeed flipped
by VMware when set to auto-detect.
Changing the VMware vmx file entries as follows set them straight:
serial0.present = "TRUE"
serial0.fileName = "COM1"
serial0.autodetect = "FALSE"
serial1.present = "TRUE"
serial1.fileNa
On 6/12/07, Jason Winningham <[EMAIL PROTECTED]> wrote:
I had this and similar issues with VMware during my limited dealings
with it. I gave up guessing and just statically configured VMware to
assign the ports to the VM, as per the wiki instructions. Life got
much easier at that point.
Yea
On Tue, 12 Jun 2007, Tom Russo wrote:
> IMHO, the debugging output is almost useless for most segfault hunting,
> as it's generally been the case that the debugging output that's there was
> put there to find bugs in code that's already been fixed. New segfaults
> have almost invariably required
On Jun 12, 2007, at 11:58 AM, Tom Russo wrote:
It could be the case that VMware thinks that the modem is COM1 or
something
bizarre like that, so it assigns /dev/ttyS0 on the linux side to
COM2 on the
Losedows side.
I had this and similar issues with VMware during my limited dealings
wit
On Tue, Jun 12, 2007 at 07:27:50AM -0700, we recorded a bogon-computron
collision of the <[EMAIL PROTECTED]> flavor, containing:
> On Mon, 11 Jun 2007, Lee Bengston wrote:
>
> > Curiously, based on the Xastir/Linux settings, I was expecting the Linux
> > port to map to COM1 in Windows, but it'
On Tue, Jun 12, 2007 at 07:30:23AM -0700, we recorded a bogon-computron
collision of the <[EMAIL PROTECTED]> flavor, containing:
> On Tue, 12 Jun 2007, Tom Russo wrote:
>
> > If it didn't drop core (i.e. because ulimit -c isn't "unlimited"), you might
> > want to run xastir in the debugger to ca
On 6/12/07, Curt, WE7U <[EMAIL PROTECTED]> wrote:
What port did you use from Linux? /dev/ttyS0 or /dev/ttyS1?
Linux/Unix typically start numbering their ports at 0, not 1.
/dev/ttyS0 -> COM1
/dev/ttyS1 -> COM2
etc.
Yes, I saw that in the How-To's - the interface I set up in XASTIR for the
D
On Tue, 12 Jun 2007, Tom Russo wrote:
> If it didn't drop core (i.e. because ulimit -c isn't "unlimited"), you might
> want to run xastir in the debugger to catch the real problem. Again,
> look in README.Contributing for hints.
You can also run it with debugging messages turned on, which may o
On Mon, 11 Jun 2007, Lee Bengston wrote:
> Curiously, based on the Xastir/Linux settings, I was expecting the Linux
> port to map to COM1 in Windows, but it's actually using COM2. It's probably
> something simple like VMware thinks COM1 is already in use for some reason.
What port did you use
On 6/11/07, Jeremy Utley <[EMAIL PROTECTED]> wrote:
As I remember it, the KPC-9612 is an odd beast - it's a dual-port TNC
(both 1200 & 9600 baud modems in it). Xastir can't directly speak to
both ports at once via KISS as far as I know - you might be able to
get it to work without KISS. You co
Richard Polivka, N6NKO wrote:
A couple of ideas come to mind:
1) Was Fedora 7 used as an upgrade or clean install?
2) Was the disk/partitions wiped saving /home?
I have my HD partitioned into five sections: WinXP, /boot, /, swap,
/home.
This way, when I upgrade, all I wipe are the /boot, an
A couple of ideas come to mind:
1) Was Fedora 7 used as an upgrade or clean install?
2) Was the disk/partitions wiped saving /home?
I have my HD partitioned into five sections: WinXP, /boot, /, swap, /home.
This way, when I upgrade, all I wipe are the /boot, and / (root). /home
is not touched
On Mon, Jun 11, 2007 at 11:23:07PM -0600, we recorded a bogon-computron
collision of the <[EMAIL PROTECTED]> flavor, containing:
> Hi guys.
>
> I upgraded to F7 today, and installed Xastir with everything enabled except
> AX25.
>
> Building with AX25 . : no
>
13 matches
Mail list logo
