A yes, agwpe works great! Also allows for sound modem too man, this
works!
Wes
On Sun, Jun 22, 2008 at 5:57 PM, Curt, WE7U <[EMAIL PROTECTED]> wrote:
> On Sun, 22 Jun 2008, Wes Johnston, AI4PX wrote:
>
> > Since I'm having trouble getting andLinux to speak to a comport, and
> > and
--- On Sun, 6/22/08, Wes Johnston, AI4PX <[EMAIL PROTECTED]> wrote:
> From: Wes Johnston
> Subject: [Xastir] comport kludge
> To: "Xastir - APRS client software discussion"
> Date: Sunday, June 22, 2008, 5:41 PM
> Since I'm having trouble getting andLinux to speak to a
> comport, and
> andLin
On Sat, Jun 21, 2008 at 3:10 PM, Steve Friis <[EMAIL PROTECTED]> wrote:
> Lee Bengston wrote:
>>
>> Hello,
>>
>> Well, compiling looked good with OpenSUSE 11, but I have what appears
>> to be the same unreadable menu issue that has been reported
>> previously. This is not the slider menu problem w
On Jun 20, 2008, at 19:12, Tom Russo wrote:
Chip, what are the time stamps on your wx_alert log files?
Sorry, been out of touch for a couple of days ... Jun 20 for current
log file, Jun 20 for the first rotate file, Apr 12 for the next, and
Feb 29 for the oldest.
-- Chip
On Sun, 22 Jun 2008, Wes Johnston, AI4PX wrote:
> Since I'm having trouble getting andLinux to speak to a comport, and
> andLinux talks to the sound card via a network socket, why not install a
> comport to tcp driver under windows and let xastir talk to that. How can I
> setup a serial TNC
Since I'm having trouble getting andLinux to speak to a comport, and
andLinux talks to the sound card via a network socket, why not install a
comport to tcp driver under windows and let xastir talk to that. How can I
setup a serial TNC that talks to a telnet port rather than a /dev/ttySx
port
I went and edited the errant statement in /etc in the config files.
Rebooted and all is fine.
Thank all.
Richard, N6NKO
kc7zru wrote:
Very well known and documented issue. It's in the FAQ - 4.13
You can read it online or find a copy in your source directory (if you
use CVS)
http://xasti
Very well known and documented issue. It's in the FAQ - 4.13
You can read it online or find a copy in your source directory (if you
use CVS)
http://xastir.cvs.sourceforge.net/xastir/xastir/FAQ?revision=1.78&view=markup
73
Richard Polivka, N6NKO wrote:
echo $LANG -> "en_US.UTF-8"
changed L
There was no mention of any serial ports there. I thought that might
be the case, but it was probably worth checking.
Since andlinux is running under Windows, there may be some
configuration required to map the ports so that Linux can see them.
The andlinux forum is probably the best plac
I'm not familiar with the normal output of this command, so forgive for me
not trimming it down FWIW, this machine is dual boot and I can talk to
the TNC from mepis as ttyS0. My registration for andlinux forums was just
approved, I'm off to ask over there.
Wes
Linux version 2.6.22.18-co-0.7
What does 'dmesg /dev/ttyS*' report?
On Jun 22, 2008, at 8:31 AM, Wes Johnston, AI4PX wrote:
My serial port is indeed a "real" serial port. However, on the odd
chance
that my it might be "faked" on my motherboard like some laptops do,
I tried
ttyUSB0, no luck that locked up andLinux whi
My serial port is indeed a "real" serial port. However, on the odd chance
that my it might be "faked" on my motherboard like some laptops do, I tried
ttyUSB0, no luck that locked up andLinux which finally shut itself down
after 5 minutes.
I installed minicom and set it up for correct baud rat
Ok, that's not it.
Is your serial port hardware or a USB dongle? If a dongle, look at
/dev/ttyUSB0.
If you have minicom, jump pins 2 and 3 on the port and see if you get
data back on your port. At least this would see if linux is seeing the
port and able to use it.
73 from 807,
Richard,
THanks for the suggestion ls /dev/ttys0 -la shows crw-rw-rw- for
permissions. So I guess this isn't it.
Wes
On Sun, Jun 22, 2008 at 10:01 AM, Richard Polivka, N6NKO <
[EMAIL PROTECTED]> wrote:
> Check permissions. I would set it to 666 / rw-rw-rw- and see. I have had
> issues where that is
Check permissions. I would set it to 666 / rw-rw-rw- and see. I have had
issues where that is a fix.
It is a "dangerous" fix because of the permission issues, but it is
worth the experiment.
73 from 807,
Richard, N6NKO
Wes Johnston, AI4PX wrote:
Guys, I tried to get xastir to talk to my T
Guys, I tried to get xastir to talk to my TNC via ttyS0, and it appears to
open the port, but I never see any traffic coming in. So I opened the com1
with a windows app and sure enough there's lots of data streaming in. While
the windows app was open (tieing up the comport), I tried once again to
echo $LANG -> "en_US.UTF-8"
changed LANG = C
Issue gone. Running Fedora 8.
Hmmm..
73 from 807,
Richard, N6NKO
John Ronan wrote:
Hmm,
Doesn't this generally mean that the LANG environment variable is set
incorrectly for xastir?
Try
export LANG=C; xastir &
John
On 22 Jun 2008, at 13:2
Hmm,
Doesn't this generally mean that the LANG environment variable is set
incorrectly for xastir?
Try
export LANG=C; xastir &
John
On 22 Jun 2008, at 13:27, Richard Polivka, N6NKO wrote:
I am running the latest devel release here from a console window
and I am getting this message that
I am running the latest devel release here from a console window and I
am getting this message that is font related:
Warning:
Name: create_appshell text_output2
Class: XmTextField
Character '\260' not supported in font. Discarded.
I am sure that this message has been there for some ti
19 matches
Mail list logo
