|
Re: jnos on my RPi keeps crashing -- help?
Hi again John... no, I'm not married to the idea of using jnos. Matter of fact I would be interested in trying BPQ32. I will give it a whirl.
Best,
jerome
|
--- On Thu, 2/14/13, John Wiseman wrote:
From: John Wiseman
Subject: RE: [Raspberry_Pi_4-Ham_RADIO] jnos on my RPi keeps crashing -- help?
To: Raspberry_Pi_4-Ham_RADIO@...
Date: Thursday, February 14, 2013, 9:51 AM
Ok, Jerome.
Do you particularly want to use nos? There is now a Linux
version of BPQ32.
73, John
Thanks John... yes, I kept a copy of the binary that was
made with all the debugging info in it, so that I could run gdb if
necessary. I'm not a coder, so I'm not sure how much sense the gdb output
is going to make to me, but I will try.
I'm getting more positive
that the problem is in the 'mbox' code, as I hashed out all the setup info
for the mbox, and it ran solid over night. No forwarding this way, but it
didn't drop out to the OS either.
Again thanks for your
suggestion..
jerome - ve7ass
--- On Thu, 2/14/13, John
Wiseman wrote:
From: John
Wiseman
Subject: RE:
[Raspberry_Pi_4-Ham_RADIO] jnos on my RPi keeps crashing -- help?
To:
Raspberry_Pi_4-Ham_RADIO@...
Date: Thursday, February 14,
2013, 2:31 AM
Jerome,
I can't help with jnos specifically, but
I suggest you run the program under the debugger (gdb). This
should at least show where the program is failing, and if it is always
in the same place.
gdb jnos2
r
if it stops within gdb, the bt copmmand will display a
stack trace.This may give a cluse, or at least give you something to
report to the jnos developer.
To get the most info, jnos has to be compiled with the
-g option - check the makefile to see if it is set.
73, John
Hi... I've been working on this for over a month, and I have
finally
run out of things to try, so I need some help. I've also
posted this to the Nos-BBS list.
The Problem:
I have
compiled from source (all defaults), various versions of Jnos for
the
RP and they all compile without error (lot's of warnings, but
no
fatal errors) and each produces a working executable. All jnos
functions
seem to work, but after anywhere from a few minutes to a
few hours (and
sometimes several days), Jnos crashes back to the
operating system. It
never hangs the pi, it just unceremoniously
exits.
In an effort to bisect the problem (hardware vs.
software), here's what
I've tried:
1. Power supplies, various:
from a 5v/1A wall wart to a lab-grade
regulated supply connected to
the GPIO 5v pins; no difference.
2. Burn a new SD card (tried
various brands); no difference.
3. Examined the jnos logs to see
if there was a pattern to the
activities before the crash. Results
don't seem to indicate anything
obvious. The actual crash could be
many minutes after a logged event. Of
course not all events are
logged, so that fact that all Mailbox activity
shows up a lot before
a crash, can't be pinned to anything. That said,
there's one command
that kicks jnos right out to the OS pronto and that
is 'mbox kick'.
Bang jnos quits. Maybe this is the big clue?
4. apt-get update
-> apt-get upgrade; then recompile and try new binary;
no
difference.
5. download latest image, burn new card and repeat 4
above; no
difference
6. Remove USB peripherals one by one and
rebooting; no difference.
7. Move jnos from SD card to memory
stick; no difference.
8. Run in GUI terminal/Run without GUI in
linux terminal; no difference.
What I have not tried:
1. I
have not swapped out the pi
2. I have not run any memory (ram)
diagnostics as I can't find any to
run. Help here?
In
conclusion, I have no indication from running different apps on
the
pi, that the pi is faulty -- no flakyness at all, except when
running
jnos. Of course I don't have any apps that continually
exercise the pi
the way jnos does. If you know of any I could try,
please let me know.
As well, is there anything I can try to
change in the compilation
process that might be useful? Has anyone
gotten their pi and jnos to work together?
Thanks for any
suggestions!
Jerome -
ve7ass
|
|
|
|
Re: jnos on my RPi crashing -- resolved
Hi John, and others following my original thread:
Just to let you know that I was able to locate where jnos was crashing; it was at the start of each forward cycle that I initiated. I have supplicated myself before the wizard and hope that he will respond.
My work around in the meantime was to change my forward file so that I did not poll my forwarding partners. That has worked now since yesterday. If they initiate a forward cycle everything is fine and the system is stable. Not exactly a fix, but all is operational with the Pi and jnos to an extent where it's almost 100%.
I noticed that in low traffic times, it would crash exactly every 15 minutes by itself. 15 minutes was the start of my forward cycle time. This aligns with my original clue, where I saw that manually starting a forward cycle crashed jnos.
Sill going to try
the debugger to see what I can learn from that.
Thanks again,
jerome - ve7ass
|
--- On Thu, 2/14/13, jerome schatten wrote:
From: jerome schatten
Subject: RE: [Raspberry_Pi_4-Ham_RADIO] jnos on my RPi keeps crashing -- help?
To: Raspberry_Pi_4-Ham_RADIO@...
Date: Thursday, February 14, 2013, 8:39 AM
Thanks John... yes, I kept a copy of the binary that was made with all the debugging info in it, so that I could run gdb if necessary. I'm not a coder, so I'm not sure how much sense the gdb output is going to make to me, but I will try.
I'm getting more positive that the problem is in the 'mbox' code, as I hashed out all the setup info for the mbox, and it ran solid over night. No forwarding this way, but it didn't drop out to the OS either.
Again thanks for your suggestion..
jerome - ve7ass
--- On Thu, 2/14/13, John Wiseman wrote:
From: John Wiseman
Subject: RE: [Raspberry_Pi_4-Ham_RADIO] jnos on my RPi keeps crashing -- help?
To:
Raspberry_Pi_4-Ham_RADIO@...
Date: Thursday, February 14, 2013, 2:31 AM
Jerome,
I can't help with jnos specifically, but I suggest you
run the program under the debugger (gdb). This should at least show where the
program is failing, and if it is always in the same place.
gdb
jnos2
r
if it
stops within gdb, the bt copmmand will display a stack trace.This may give a
cluse, or at least give you something to report to the jnos
developer.
To get
the most info, jnos has to be compiled with the -g option - check the makefile
to see if it is set.
73,
John
Hi... I've been working on this for over a month, and I have finally
run
out of things to try, so I need some help. I've also posted this to the Nos-BBS
list.
The Problem:
I have compiled from source (all defaults),
various versions of Jnos for
the RP and they all compile without error (lot's
of warnings, but no
fatal errors) and each produces a working executable. All
jnos functions
seem to work, but after anywhere from a few minutes to a few
hours (and
sometimes several days), Jnos crashes back to the operating
system. It
never hangs the pi, it just unceremoniously exits.
In an
effort to bisect the problem (hardware vs. software), here's what
I've
tried:
1. Power supplies, various: from a 5v/1A wall wart to a
lab-grade
regulated supply connected to the GPIO 5v pins; no
difference.
2. Burn a new SD card (tried various brands); no
difference.
3. Examined the jnos logs to see if there was a pattern to
the
activities before the crash. Results don't seem to indicate
anything
obvious. The actual crash could be many minutes after a logged
event. Of
course not all events are logged, so that fact that all Mailbox
activity
shows up a lot before a crash, can't be pinned to anything. That
said,
there's one command that kicks jnos right out to the OS pronto and
that
is 'mbox kick'. Bang jnos quits. Maybe this is the big clue?
4.
apt-get update -> apt-get upgrade; then recompile and try new binary;
no
difference.
5. download latest image, burn new card and repeat 4 above;
no
difference
6. Remove USB peripherals one by one and rebooting; no
difference.
7. Move jnos from SD card to memory stick; no
difference.
8. Run in GUI terminal/Run without GUI in linux terminal; no
difference.
What I have not tried:
1. I have not swapped out the
pi
2. I have not run any memory (ram) diagnostics as I can't find any
to
run. Help here?
In conclusion, I have no indication from running
different apps on the
pi, that the pi is faulty -- no flakyness at all,
except when running
jnos. Of course I don't have any apps that continually
exercise the pi
the way jnos does. If you know of any I could try, please let
me know.
As well, is there anything I can try to change in the
compilation
process that might be useful? Has anyone gotten their pi and jnos
to work together?
Thanks for any suggestions!
Jerome -
ve7ass
|
|
|
|
Re: jnos on my RPi keeps crashing -- help?
Kutche, Jerry (Mitchell) USA <JKutche@...>
Hi Mike... Ok, I was mainly into MSYS back then with 24/7
Radio Links.
with one Higher speed 9600 Baud RF Port linked to a
NOS Gateway K9IU... 35 Miles away, in Bloomington Indiana. on a 440 Beam
CrushCraft ...
other then that link we had the following
1) 220 9600 baud RF Backbone
2) VHF User ports
3) HF Skipnet Ports 20,30,40 meters..
Actually K9IU was a TNOS Gateway..
Off
list (See email below) please tell me more...
Yea, I
never really understood the Part Time aspect that some ops desired.. Seemed to
slow things even further.. I remember a lot of conflict in the mid 90s about
which way Packet Radio should grow, wheich the fighting helped kill it off... At
least in the Central Indiana Area..
My
System today an offshoot of the one above, due to a lack of interest at the
local club to continue.. (Went off air in 2002) I started building a clone and
then advanced it severely at my home.. Using my equipment money and sweat...
:)
73
Jerry Kutche
Electrical Supervisor
Lehigh Cement Company LLC
180 N. Meridian
Road
Mitchell, IN 47446
Phone:
(812) 849-2191 ext. 251
Fax: (812) 849-5007
Cell: (812)
583-0445
jkutche@...
www.lehighcement.com
This e-mail may contain confidential and/or legally privileged
information. If you are not the intended recipient (or have received this
e-mail in error) please notify the sender immediately and delete this
e-mail. Any unauthorized copying, disclosure or distribution of the
material in this e-mail is strictly forbidden.
Jerry,
Funny in the regard that the radio links those systems
operated on, were barely adequate then. Tampa had one of the largest
packet networks in the country, yet messages passed by the largest of systems
only numbered a few thousand per day, while the NOS based systems generally only
passed a few hundred. The dream of wireless networking was only achievable
for relatively small amounts of data. The RF layer needed to change in
order to provide something truly useful. The relatively low density of
hams willing to run a system 24/7 to support it, hampered things further.
73 Mike N4MHO (ex N4CNW, W4LNA)
toggle quoted messageShow quoted text
On Thu, Feb 14, 2013 at 11:18 AM, Kutche, Jerry
(Mitchell) USA <JKutche@...> wrote:
Hello Mike why
does it seem funny...
BPQ and FBB and
TNOS have beena round a long time
BPQ still in
active development (new to Linux) after 20+ Years
FBB I have seen
no updates in years.. Last update that works???
TNOS.. I have not
seen any there either at least in years... Last update I can find is
2010
Jnos
Just curious what is funny or
odd???
BPQ32 and JNOS Sysop.
73
Jerry
Seems funny that JNOS is being discussed again some 20 years since I last
used it on a Linux box. Depending on what you are trying to do with it,
there were alternatives out there, Brian Lantz's TNOS (optimized for BBS
use) and FBB. TNOS is available on a SourceForge site now I
think.
73
Mike N4MHO
|
|
|
Re: jnos on my RPi keeps crashing -- help?
Mike Murphree N4MHO
Jerry,
Funny in the regard that the radio links those systems operated on, were barely adequate then. Tampa had one of the largest packet networks in the country, yet messages passed by the largest of systems only numbered a few thousand per day, while the NOS based systems generally only passed a few hundred. The dream of wireless networking was only achievable for relatively small amounts of data. The RF layer needed to change in order to provide something truly useful. The relatively low density of hams willing to run a system 24/7 to support it, hampered things further.
73 Mike N4MHO (ex N4CNW, W4LNA)
On Thu, Feb 14, 2013 at 11:18 AM, Kutche, Jerry (Mitchell) USA <JKutche@...> wrote:
Hello Mike why does it seem funny...
BPQ and FBB and TNOS have beena round a long
time
BPQ still in active development (new to Linux) after 20+
Years
FBB I have seen no updates in years.. Last update that
works???
TNOS.. I have not seen any there either at least in years...
Last update I can find is 2010
Jnos
Just
curious what is funny or odd???
BPQ32 and JNOS
Sysop.
73
Jerry
Seems funny that JNOS is being discussed again some 20 years since I last
used it on a Linux box. Depending on what you are trying to do with it,
there were alternatives out there, Brian Lantz's TNOS (optimized for BBS
use) and FBB. TNOS is available on a SourceForge site now I
think.
73
Mike N4MHO
|
|
|
Re: jnos on my RPi keeps crashing -- help?
Ok, Jerome.
Do you particularly want to use nos? There is now a Linux
version of BPQ32.
73, John
Thanks John... yes, I kept a copy of the binary that was
made with all the debugging info in it, so that I could run gdb if
necessary. I'm not a coder, so I'm not sure how much sense the gdb output
is going to make to me, but I will try.
I'm getting more positive
that the problem is in the 'mbox' code, as I hashed out all the setup info
for the mbox, and it ran solid over night. No forwarding this way, but it
didn't drop out to the OS either.
Again thanks for your
suggestion..
jerome - ve7ass
|
toggle quoted messageShow quoted text
--- On Thu, 2/14/13, John
Wiseman wrote:
From: John
Wiseman
Subject: RE:
[Raspberry_Pi_4-Ham_RADIO] jnos on my RPi keeps crashing -- help?
To:
Raspberry_Pi_4-Ham_RADIO@...
Date: Thursday, February 14,
2013, 2:31 AM
Jerome,
I can't help with jnos specifically, but
I suggest you run the program under the debugger (gdb). This
should at least show where the program is failing, and if it is always
in the same place.
gdb jnos2
r
if it stops within gdb, the bt copmmand will display a
stack trace.This may give a cluse, or at least give you something to
report to the jnos developer.
To get the most info, jnos has to be compiled with the
-g option - check the makefile to see if it is set.
73, John
Hi... I've been working on this for over a month, and I have
finally
run out of things to try, so I need some help. I've also
posted this to the Nos-BBS list.
The Problem:
I have
compiled from source (all defaults), various versions of Jnos for
the
RP and they all compile without error (lot's of warnings, but
no
fatal errors) and each produces a working executable. All jnos
functions
seem to work, but after anywhere from a few minutes to a
few hours (and
sometimes several days), Jnos crashes back to the
operating system. It
never hangs the pi, it just unceremoniously
exits.
In an effort to bisect the problem (hardware vs.
software), here's what
I've tried:
1. Power supplies, various:
from a 5v/1A wall wart to a lab-grade
regulated supply connected to
the GPIO 5v pins; no difference.
2. Burn a new SD card (tried
various brands); no difference.
3. Examined the jnos logs to see
if there was a pattern to the
activities before the crash. Results
don't seem to indicate anything
obvious. The actual crash could be
many minutes after a logged event. Of
course not all events are
logged, so that fact that all Mailbox activity
shows up a lot before
a crash, can't be pinned to anything. That said,
there's one command
that kicks jnos right out to the OS pronto and that
is 'mbox kick'.
Bang jnos quits. Maybe this is the big clue?
4. apt-get update
-> apt-get upgrade; then recompile and try new binary;
no
difference.
5. download latest image, burn new card and repeat 4
above; no
difference
6. Remove USB peripherals one by one and
rebooting; no difference.
7. Move jnos from SD card to memory
stick; no difference.
8. Run in GUI terminal/Run without GUI in
linux terminal; no difference.
What I have not tried:
1. I
have not swapped out the pi
2. I have not run any memory (ram)
diagnostics as I can't find any to
run. Help here?
In
conclusion, I have no indication from running different apps on
the
pi, that the pi is faulty -- no flakyness at all, except when
running
jnos. Of course I don't have any apps that continually
exercise the pi
the way jnos does. If you know of any I could try,
please let me know.
As well, is there anything I can try to
change in the compilation
process that might be useful? Has anyone
gotten their pi and jnos to work together?
Thanks for any
suggestions!
Jerome -
ve7ass
|
|
|
Re: jnos on my RPi keeps crashing -- help?
Kutche, Jerry (Mitchell) USA <JKutche@...>
Hello Mike why does it seem funny...
BPQ and FBB and TNOS have beena round a long
time
BPQ still in active development (new to Linux) after 20+
Years
FBB I have seen no updates in years.. Last update that
works???
TNOS.. I have not seen any there either at least in years...
Last update I can find is 2010
Jnos
Just
curious what is funny or odd???
BPQ32 and JNOS
Sysop.
73
Jerry
Seems funny that JNOS is being discussed again some 20 years since I last
used it on a Linux box. Depending on what you are trying to do with it,
there were alternatives out there, Brian Lantz's TNOS (optimized for BBS
use) and FBB. TNOS is available on a SourceForge site now I
think.
73
Mike N4MHO
toggle quoted messageShow quoted text
On Thu, Feb 14, 2013 at 10:39 AM, jerome schatten <va7vv@...> wrote:
Thanks John... yes, I kept a copy of the binary that was
made with all the debugging info in it, so that I could run gdb if
necessary. I'm not a coder, so I'm not sure how much sense the gdb
output is going to make to me, but I will try.
I'm getting more
positive that the problem is in the 'mbox' code, as I hashed out all the
setup info for the mbox, and it ran solid over night. No forwarding this
way, but it didn't drop out to the OS either.
Again thanks for
your suggestion..
jerome - ve7ass
--- On Thu, 2/14/13, John
Wiseman <john.wiseman@...> wrote:
From:
John Wiseman <john.wiseman@...>
Subject: RE:
[Raspberry_Pi_4-Ham_RADIO] jnos on my RPi keeps crashing --
help?
To: Raspberry_Pi_4-Ham_RADIO@...
Date:
Thursday, February 14, 2013, 2:31 AM
Jerome,
I can't
help with jnos specifically, but I suggest you run the program
under the debugger (gdb). This should at least show where the program
is failing, and if it is always in the same place.
gdb
jnos2
r
if it stops within gdb, the
bt copmmand will display a stack trace.This may give a cluse, or at
least give you something to report to the jnos
developer.
To get the most info, jnos
has to be compiled with the -g option - check the makefile to see if
it is set.
73, John
Hi... I've been working on this for over a month, and I have
finally
run out of things to try, so I need some help. I've also
posted this to the Nos-BBS list.
The Problem:
I have
compiled from source (all defaults), various versions of Jnos
for
the RP and they all compile without error (lot's of warnings,
but no
fatal errors) and each produces a working executable. All
jnos functions
seem to work, but after anywhere from a few minutes
to a few hours (and
sometimes several days), Jnos crashes back to
the operating system. It
never hangs the pi, it just
unceremoniously exits.
In an effort to bisect the problem
(hardware vs. software), here's what
I've tried:
1. Power
supplies, various: from a 5v/1A wall wart to a lab-grade
regulated
supply connected to the GPIO 5v pins; no difference.
2. Burn a
new SD card (tried various brands); no difference.
3. Examined
the jnos logs to see if there was a pattern to the
activities
before the crash. Results don't seem to indicate anything
obvious.
The actual crash could be many minutes after a logged event.
Of
course not all events are logged, so that fact that all Mailbox
activity
shows up a lot before a crash, can't be pinned to
anything. That said,
there's one command that kicks jnos right out
to the OS pronto and that
is 'mbox kick'. Bang jnos quits. Maybe
this is the big clue?
4. apt-get update -> apt-get upgrade;
then recompile and try new binary;
no difference.
5.
download latest image, burn new card and repeat 4 above;
no
difference
6. Remove USB peripherals one by one and
rebooting; no difference.
7. Move jnos from SD card to memory
stick; no difference.
8. Run in GUI terminal/Run without GUI in
linux terminal; no difference.
What I have not tried:
1.
I have not swapped out the pi
2. I have not run any memory
(ram) diagnostics as I can't find any to
run. Help here?
In
conclusion, I have no indication from running different apps on
the
pi, that the pi is faulty -- no flakyness at all, except when
running
jnos. Of course I don't have any apps that continually
exercise the pi
the way jnos does. If you know of any I could try,
please let me know.
As well, is there anything I can try to
change in the compilation
process that might be useful? Has anyone
gotten their pi and jnos to work together?
Thanks for any
suggestions!
Jerome -
ve7ass
|
|
|
|
Re: jnos on my RPi keeps crashing -- help?
Mike Murphree N4MHO
Seems funny that JNOS is being discussed again some 20 years since I last used it on a Linux box. Depending on what you are trying to do with it, there were alternatives out there, Brian Lantz's TNOS (optimized for BBS use) and FBB. TNOS is available on a SourceForge site now I think.
73
Mike N4MHO
On Thu, Feb 14, 2013 at 10:39 AM, jerome schatten <va7vv@...> wrote:
Thanks John... yes, I kept a copy of the binary that was made with all the debugging info in it, so that I could run gdb if necessary. I'm not a coder, so I'm not sure how much sense the gdb output is going to make to me, but I will try.
I'm getting more positive that the problem is in the 'mbox' code, as I hashed out all the setup info for the mbox, and it ran solid over night. No forwarding this way, but it didn't drop out to the OS either.
Again thanks for your suggestion..
jerome - ve7ass
--- On Thu, 2/14/13, John Wiseman <john.wiseman@...> wrote:
From: John Wiseman <john.wiseman@...>
Subject: RE: [Raspberry_Pi_4-Ham_RADIO] jnos on my RPi keeps crashing -- help?
To:
Raspberry_Pi_4-Ham_RADIO@...
Date: Thursday, February 14, 2013, 2:31 AM
Jerome,
I can't help with jnos specifically, but I suggest you
run the program under the debugger (gdb). This should at least show where the
program is failing, and if it is always in the same place.
gdb
jnos2
r
if it
stops within gdb, the bt copmmand will display a stack trace.This may give a
cluse, or at least give you something to report to the jnos
developer.
To get
the most info, jnos has to be compiled with the -g option - check the makefile
to see if it is set.
73,
John
Hi... I've been working on this for over a month, and I have finally
run
out of things to try, so I need some help. I've also posted this to the Nos-BBS
list.
The Problem:
I have compiled from source (all defaults),
various versions of Jnos for
the RP and they all compile without error (lot's
of warnings, but no
fatal errors) and each produces a working executable. All
jnos functions
seem to work, but after anywhere from a few minutes to a few
hours (and
sometimes several days), Jnos crashes back to the operating
system. It
never hangs the pi, it just unceremoniously exits.
In an
effort to bisect the problem (hardware vs. software), here's what
I've
tried:
1. Power supplies, various: from a 5v/1A wall wart to a
lab-grade
regulated supply connected to the GPIO 5v pins; no
difference.
2. Burn a new SD card (tried various brands); no
difference.
3. Examined the jnos logs to see if there was a pattern to
the
activities before the crash. Results don't seem to indicate
anything
obvious. The actual crash could be many minutes after a logged
event. Of
course not all events are logged, so that fact that all Mailbox
activity
shows up a lot before a crash, can't be pinned to anything. That
said,
there's one command that kicks jnos right out to the OS pronto and
that
is 'mbox kick'. Bang jnos quits. Maybe this is the big clue?
4.
apt-get update -> apt-get upgrade; then recompile and try new binary;
no
difference.
5. download latest image, burn new card and repeat 4 above;
no
difference
6. Remove USB peripherals one by one and rebooting; no
difference.
7. Move jnos from SD card to memory stick; no
difference.
8. Run in GUI terminal/Run without GUI in linux terminal; no
difference.
What I have not tried:
1. I have not swapped out the
pi
2. I have not run any memory (ram) diagnostics as I can't find any
to
run. Help here?
In conclusion, I have no indication from running
different apps on the
pi, that the pi is faulty -- no flakyness at all,
except when running
jnos. Of course I don't have any apps that continually
exercise the pi
the way jnos does. If you know of any I could try, please let
me know.
As well, is there anything I can try to change in the
compilation
process that might be useful? Has anyone gotten their pi and jnos
to work together?
Thanks for any suggestions!
Jerome -
ve7ass
|
|
|
|
Re: jnos on my RPi keeps crashing -- help?
Thanks John... yes, I kept a copy of the binary that was made with all the debugging info in it, so that I could run gdb if necessary. I'm not a coder, so I'm not sure how much sense the gdb output is going to make to me, but I will try.
I'm getting more positive that the problem is in the 'mbox' code, as I hashed out all the setup info for the mbox, and it ran solid over night. No forwarding this way, but it didn't drop out to the OS either.
Again thanks for your suggestion..
jerome - ve7ass
|
--- On Thu, 2/14/13, John Wiseman wrote:
From: John Wiseman
Subject: RE: [Raspberry_Pi_4-Ham_RADIO] jnos on my RPi keeps crashing -- help?
To:
Raspberry_Pi_4-Ham_RADIO@...
Date: Thursday, February 14, 2013, 2:31 AM
Jerome,
I can't help with jnos specifically, but I suggest you
run the program under the debugger (gdb). This should at least show where the
program is failing, and if it is always in the same place.
gdb
jnos2
r
if it
stops within gdb, the bt copmmand will display a stack trace.This may give a
cluse, or at least give you something to report to the jnos
developer.
To get
the most info, jnos has to be compiled with the -g option - check the makefile
to see if it is set.
73,
John
Hi... I've been working on this for over a month, and I have finally
run
out of things to try, so I need some help. I've also posted this to the Nos-BBS
list.
The Problem:
I have compiled from source (all defaults),
various versions of Jnos for
the RP and they all compile without error (lot's
of warnings, but no
fatal errors) and each produces a working executable. All
jnos functions
seem to work, but after anywhere from a few minutes to a few
hours (and
sometimes several days), Jnos crashes back to the operating
system. It
never hangs the pi, it just unceremoniously exits.
In an
effort to bisect the problem (hardware vs. software), here's what
I've
tried:
1. Power supplies, various: from a 5v/1A wall wart to a
lab-grade
regulated supply connected to the GPIO 5v pins; no
difference.
2. Burn a new SD card (tried various brands); no
difference.
3. Examined the jnos logs to see if there was a pattern to
the
activities before the crash. Results don't seem to indicate
anything
obvious. The actual crash could be many minutes after a logged
event. Of
course not all events are logged, so that fact that all Mailbox
activity
shows up a lot before a crash, can't be pinned to anything. That
said,
there's one command that kicks jnos right out to the OS pronto and
that
is 'mbox kick'. Bang jnos quits. Maybe this is the big clue?
4.
apt-get update -> apt-get upgrade; then recompile and try new binary;
no
difference.
5. download latest image, burn new card and repeat 4 above;
no
difference
6. Remove USB peripherals one by one and rebooting; no
difference.
7. Move jnos from SD card to memory stick; no
difference.
8. Run in GUI terminal/Run without GUI in linux terminal; no
difference.
What I have not tried:
1. I have not swapped out the
pi
2. I have not run any memory (ram) diagnostics as I can't find any
to
run. Help here?
In conclusion, I have no indication from running
different apps on the
pi, that the pi is faulty -- no flakyness at all,
except when running
jnos. Of course I don't have any apps that continually
exercise the pi
the way jnos does. If you know of any I could try, please let
me know.
As well, is there anything I can try to change in the
compilation
process that might be useful? Has anyone gotten their pi and jnos
to work together?
Thanks for any suggestions!
Jerome -
ve7ass
|
|
|
Re: jnos on my RPi keeps crashing -- help?
Jerome,
I can't help with jnos specifically, but I suggest you
run the program under the debugger (gdb). This should at least show where the
program is failing, and if it is always in the same place.
gdb
jnos2
r
if it
stops within gdb, the bt copmmand will display a stack trace.This may give a
cluse, or at least give you something to report to the jnos
developer.
To get
the most info, jnos has to be compiled with the -g option - check the makefile
to see if it is set.
73,
John
Hi... I've been working on this for over a month, and I have finally
run
out of things to try, so I need some help. I've also posted this to the Nos-BBS
list.
The Problem:
I have compiled from source (all defaults),
various versions of Jnos for
the RP and they all compile without error (lot's
of warnings, but no
fatal errors) and each produces a working executable. All
jnos functions
seem to work, but after anywhere from a few minutes to a few
hours (and
sometimes several days), Jnos crashes back to the operating
system. It
never hangs the pi, it just unceremoniously exits.
In an
effort to bisect the problem (hardware vs. software), here's what
I've
tried:
1. Power supplies, various: from a 5v/1A wall wart to a
lab-grade
regulated supply connected to the GPIO 5v pins; no
difference.
2. Burn a new SD card (tried various brands); no
difference.
3. Examined the jnos logs to see if there was a pattern to
the
activities before the crash. Results don't seem to indicate
anything
obvious. The actual crash could be many minutes after a logged
event. Of
course not all events are logged, so that fact that all Mailbox
activity
shows up a lot before a crash, can't be pinned to anything. That
said,
there's one command that kicks jnos right out to the OS pronto and
that
is 'mbox kick'. Bang jnos quits. Maybe this is the big clue?
4.
apt-get update -> apt-get upgrade; then recompile and try new binary;
no
difference.
5. download latest image, burn new card and repeat 4 above;
no
difference
6. Remove USB peripherals one by one and rebooting; no
difference.
7. Move jnos from SD card to memory stick; no
difference.
8. Run in GUI terminal/Run without GUI in linux terminal; no
difference.
What I have not tried:
1. I have not swapped out the
pi
2. I have not run any memory (ram) diagnostics as I can't find any
to
run. Help here?
In conclusion, I have no indication from running
different apps on the
pi, that the pi is faulty -- no flakyness at all,
except when running
jnos. Of course I don't have any apps that continually
exercise the pi
the way jnos does. If you know of any I could try, please let
me know.
As well, is there anything I can try to change in the
compilation
process that might be useful? Has anyone gotten their pi and jnos
to work together?
Thanks for any suggestions!
Jerome -
ve7ass
|
|
|
jnos on my RPi keeps crashing -- help?
Hi... I've been working on this for over a month, and I have finally
run out of things to try, so I need some help. I've also posted this to the Nos-BBS list.
The Problem:
I have compiled from source (all defaults), various versions of Jnos for
the RP and they all compile without error (lot's of warnings, but no
fatal errors) and each produces a working executable. All jnos functions
seem to work, but after anywhere from a few minutes to a few hours (and
sometimes several days), Jnos crashes back to the operating system. It
never hangs the pi, it just unceremoniously exits.
In an effort to bisect the problem (hardware vs. software), here's what
I've tried:
1. Power supplies, various: from a 5v/1A wall wart to a lab-grade
regulated supply connected to the GPIO 5v pins; no difference.
2. Burn a new SD card (tried various brands); no difference.
3. Examined the jnos logs to see if there was a pattern to the
activities before the crash. Results don't seem to indicate anything
obvious. The actual crash could be many minutes after a logged event. Of
course not all events are logged, so that fact that all Mailbox activity
shows up a lot before a crash, can't be pinned to anything. That said,
there's one command that kicks jnos right out to the OS pronto and that
is 'mbox kick'. Bang jnos quits. Maybe this is the big clue?
4. apt-get update -> apt-get upgrade; then recompile and try new binary;
no difference.
5. download latest image, burn new card and repeat 4 above; no
difference
6. Remove USB peripherals one by one and rebooting; no difference.
7. Move jnos from SD card to memory stick; no difference.
8. Run in GUI terminal/Run without GUI in linux terminal; no difference.
What I have not tried:
1. I have not swapped out the pi
2. I have not run any memory (ram) diagnostics as I can't find any to
run. Help here?
In conclusion, I have no indication from running different apps on the
pi, that the pi is faulty -- no flakyness at all, except when running
jnos. Of course I don't have any apps that continually exercise the pi
the way jnos does. If you know of any I could try, please let me know.
As well, is there anything I can try to change in the compilation
process that might be useful? Has anyone gotten their pi and jnos to work together?
Thanks for any suggestions!
Jerome - ve7ass
|
|
|
Interesting Article About Tethering the RasPi to Cell Phone
|
|
|
Re: addon board on group photo
Ronny Julian <k4rjjradio@...>
I forgot that all China Post is stopped pretty much also. Hope to have an assembled before Field Day. Any way to pre-order? I would put in a Paypal now for a ready to use unit off the line.
toggle quoted messageShow quoted text
On Tue, Feb 12, 2013 at 5:13 AM, John Wiseman <john.wiseman@...> wrote:
Ronny,
They shouldn't be long. John is testing it at the moment, and
I understand the first few will be advertised soon. The main batch of boards may
be slightly delayed by the Chinese New Year.
73, John G8BPQ
John is this still on the way? Looking forward to it. Thanks!
Ronny
On Sat, Jan 19, 2013 at 6:41 AM, Ronny Julian <k4rjjradio@...> wrote:
Thanks!
I'll get a separate Pi for this and be ready for first run.
On Sat, Jan 19, 2013 at 6:16 AM, John Wiseman <john.wiseman@...> wrote:
Ronny,
There is a fair
bit of info on the TNC in this group's message archive, but to summarize,
the TNC will be supplied by John Hansen W2FS, the maker of the TNC-X, and
will be available, probably via the TNC-X website, in both kit and ready
made form. Price and delivery aren't yet finalised, but I expect the kit to
be in the $40-50 range, and availability in a few weeks.
73,
John
Are you going to have them on your site for sale as kits or completed
TNCs? I'd like to be in on the first run if you are taking pre-orders.
What is your expected price range?
Ronny
K4RJJ
On Sat, Jan 19, 2013 at 5:28 AM, John Wiseman <john.wiseman@...> wrote:
Kristoff,
The photo is
a standard TNC-X board, which I modified by supergluing a bit of matrix
board with a 26 way header to it. It is complete and functional - the
missing components are for the USB or RS232 interfaces that are not
needed. It connects to the async port on the PI header. This was the
prototype for the PI TNC which should soon be
available.
73, John
G8BPQ
Hi,
Perhaps a stupid question but can somebody say what is the
RPi addon
board on the photo of the group on yahoo?
(it doesn't
even seams to be complete)
73
Kristoff -
ON1ARF
|
|
|
Re: addon board on group photo
Ronny,
They shouldn't be long. John is testing it at the moment, and
I understand the first few will be advertised soon. The main batch of boards may
be slightly delayed by the Chinese New Year.
73, John G8BPQ
John is this still on the way? Looking forward to it. Thanks!
Ronny
toggle quoted messageShow quoted text
On Sat, Jan 19, 2013 at 6:41 AM, Ronny Julian <k4rjjradio@...> wrote:
Thanks!
I'll get a separate Pi for this and be ready for first run.
On Sat, Jan 19, 2013 at 6:16 AM, John Wiseman <john.wiseman@...> wrote:
Ronny,
There is a fair
bit of info on the TNC in this group's message archive, but to summarize,
the TNC will be supplied by John Hansen W2FS, the maker of the TNC-X, and
will be available, probably via the TNC-X website, in both kit and ready
made form. Price and delivery aren't yet finalised, but I expect the kit to
be in the $40-50 range, and availability in a few weeks.
73,
John
Are you going to have them on your site for sale as kits or completed
TNCs? I'd like to be in on the first run if you are taking pre-orders.
What is your expected price range?
Ronny
K4RJJ
On Sat, Jan 19, 2013 at 5:28 AM, John Wiseman <john.wiseman@...> wrote:
Kristoff,
The photo is
a standard TNC-X board, which I modified by supergluing a bit of matrix
board with a 26 way header to it. It is complete and functional - the
missing components are for the USB or RS232 interfaces that are not
needed. It connects to the async port on the PI header. This was the
prototype for the PI TNC which should soon be
available.
73, John
G8BPQ
Hi,
Perhaps a stupid question but can somebody say what is the
RPi addon
board on the photo of the group on yahoo?
(it doesn't
even seams to be complete)
73
Kristoff -
ON1ARF
|
|
|
Re: addon board on group photo
Ronny Julian <k4rjjradio@...>
John is this still on the way? Looking forward to it. Thanks! Ronny
On Sat, Jan 19, 2013 at 6:41 AM, Ronny Julian <k4rjjradio@...> wrote:
Thanks! I'll get a separate Pi for this and be ready for first run.
On Sat, Jan 19, 2013 at 6:16 AM, John Wiseman <john.wiseman@...> wrote:
Ronny,
There is a fair bit of info on the TNC in this group's message
archive, but to summarize, the TNC will be supplied by John Hansen W2FS, the
maker of the TNC-X, and will be available, probably via the TNC-X website, in
both kit and ready made form. Price and delivery aren't yet finalised, but I
expect the kit to be in the $40-50 range, and availability in a few
weeks.
73, John
Are you going to have them on your site for sale as kits or completed TNCs?
I'd like to be in on the first run if you are taking pre-orders.
What is your expected price range?
Ronny
K4RJJ
On Sat, Jan 19, 2013 at 5:28 AM, John Wiseman <john.wiseman@...> wrote:
Kristoff,
The photo is a
standard TNC-X board, which I modified by supergluing a bit of matrix board
with a 26 way header to it. It is complete and functional - the missing
components are for the USB or RS232 interfaces that are not needed. It
connects to the async port on the PI header. This was the prototype for the PI
TNC which should soon be available.
73, John
G8BPQ
Hi,
Perhaps a stupid question but can somebody say what is the RPi
addon
board on the photo of the group on yahoo?
(it doesn't even
seams to be complete)
73
Kristoff - ON1ARF
|
|
|
Tim,
Were you able to get DXSpider to run using v1.05 of the
instructions?
73, Bill
N6WS
toggle quoted messageShow quoted text
On 02/11/2013 03:29 AM, g3pjd wrote:
As I understand it, the contents of spider.new are copied
to /spider by this line, and the next line in the
procedure removes the directory spider.new.
If I am right, then this little glimmer of understanding
is clear progress for me!!
Not sure what a left field bleacher is, but it sounds
painful!
73
Tim
G3PJD
--- In Raspberry_Pi_4-Ham_RADIO@...,
Rusty Haddock wrote:
>
> K2DMS wrote:
> >CP -a /home/sysop/spider.new/ /spider
> >
> >maybe should be
> >
> >cp -a /home/sysop/spider.new/ /spider
> >
> >Unless CP is an alias to cp.
>
> I hafta ask -- why aren't you simply creating a
symbolic link?
>
> sudo ln -s /home/sysop/spider.new /spider
>
> Not sure how much file space is used by
~sysop/spider.new but
> it's getting duplicated with a 'cp'. A symbolic link
is simply
> a "pointer" yet effectively connects /spider to
~sysop/spider.new.
> On the other hand, if you want to keep the spider.new
directory
> pristine in case something goes wrong... 'cp' is not
a bad thing.
>
> Sorry for jumping in out of the left-field bleachers.
:)
>
> -Rusty-
> --
> _____ Rusty Haddock <=> AE5AE
> |\/ o \ o Way out yonder in the
> | ( -< O o Van Alstyne (TX) Metropolitan Area
> |/\__V__/ Math illiteracy affects 7 out of 5 people!
>
|
|
|
As I understand it, the contents of spider.new are copied to /spider by this line, and the next line in the procedure removes the directory spider.new.
If I am right, then this little glimmer of understanding is clear progress for me!!
Not sure what a left field bleacher is, but it sounds painful!
73
Tim
G3PJD
toggle quoted messageShow quoted text
--- In Raspberry_Pi_4-Ham_RADIO@yahoogroups.com, Rusty Haddock wrote:
K2DMS wrote:
>CP -a /home/sysop/spider.new/ /spider
>
>maybe should be
>
>cp -a /home/sysop/spider.new/ /spider
>
>Unless CP is an alias to cp.
I hafta ask -- why aren't you simply creating a symbolic link?
sudo ln -s /home/sysop/spider.new /spider
Not sure how much file space is used by ~sysop/spider.new but
it's getting duplicated with a 'cp'. A symbolic link is simply
a "pointer" yet effectively connects /spider to ~sysop/spider.new.
On the other hand, if you want to keep the spider.new directory
pristine in case something goes wrong... 'cp' is not a bad thing.
Sorry for jumping in out of the left-field bleachers. :)
-Rusty-
--
_____ Rusty Haddock <=> AE5AE
|\/ o \ o Way out yonder in the
| ( -< O o Van Alstyne (TX) Metropolitan Area
|/\__V__/ Math illiteracy affects 7 out of 5 people!
|
|
|
CP in caps is my typo in this posting. I typed it correctly when loading the SD.
Note to self: Read through more carefully before hitting 'SEND'!
73
Self
toggle quoted messageShow quoted text
--- In Raspberry_Pi_4-Ham_RADIO@yahoogroups.com, "K2DMS" wrote:
CP -a /home/sysop/spider.new/ /spider
maybe should be
cp -a /home/sysop/spider.new/ /spider
Unless CP is an alias to cp.
--- In Raspberry_Pi_4-Ham_RADIO@yahoogroups.com, "g3pjd" wrote:
Has anybody tried Bill, N6WS' procedure for installing DX Spider on Raspi? I have had two attempts, the second one after re-formatting and re imaging my SD, but both attempts failed at "CP -a /home/sysop/spider.new/ /spider" (my quote marks) with the error message 'cannot overwrite non-directory /spider with directory /home/sysop/spider.new/'
I am running 2012-12-16 Raspbian Wheezy on a 4GB SDHC and a Pi model B.
As I am new to Debian I am somewhat at a loss (English understatement for 'clueless'!).
Any help appreciated
73
Tim
G3PJD
|
|
|
Re: Eben Upton's Book "Raspberry PI User Guide"
Don't know if this is useful, but not having a Pi/book with me today I can't check it out.
I downloaded the Wordpress .deb from http://archive.raspbian.org/raspbian/pool/main/w/ & opened it (using an archive manager) and it contains the standard 3 files. Again open the data.tar.gz archive and under ./usr/share/doc/wordpress/examples/ you'll find
setup-mysql.gz
My assumption is that the file will be found at /usr/share/doc/wordpress/examples/ on the SD and MAY require decompressing.
Feel
free to heap scorn on my head if it's not there.
___________________________________________________________________________________
Disclaimers: I have entered into no agreements regarding mails erroneously sent to this address, and reserve the right to do as I wish with any such emails.
|
|
|
Re: A differant when running IRLPvCON
John
Bret,
I am of the understanding that this is error you will get until such time as Dave C. And the author of IRLPvCON ( www.k6ib.com/irlpvcon/ )get the code working on the Pi. Look on page 22 of the PiRLP manual.
John
W9KXQ
PiRLP Node 7410
toggle quoted messageShow quoted text
--- In Raspberry_Pi_4-Ham_RADIO@yahoogroups.com, "wx7y" wrote:
Hello to the group,
I DO KNOW that the IRLPvCON is fully compatable with the PiIRLP BUT I am
getting a differant error from a configuration problem.
I get the following Error Message in the "irlpvcon" page.
### The permission settings for Apache Server have prevented IRLPvCON
access to required resources.
### CHANGES TO LINUX APACHE ENVIRONMENT ARE REQUIRED.
Anyone know what I need to do to correct this Error in the Apache
Environment file???
Thanks
Bret
WX7Y
|
|
|
Re: A differant when running IRLPvCON
Teton Amateur Radio Repeater Association (TARRA)
toggle quoted messageShow quoted text
----- Original Message -----
From: "wx7y"
To: Raspberry_Pi_4-Ham_RADIO@...
Sent: Saturday, February 09, 2013 04:46:23 PM
Subject: [Raspberry_Pi_4-Ham_RADIO] A differant when running
IRLPvCON
>
> Hello to the group,
>
> I DO KNOW that the IRLPvCON is fully compatable with the
PiIRLP BUT I am
> getting a differant error from a configuration problem.
>
> I get the following Error Message in the "irlpvcon" page.
>
> ### The permission settings for Apache Server have prevented
IRLPvCON
> access to required resources.
>
> ### CHANGES TO LINUX APACHE ENVIRONMENT ARE REQUIRED.
>
> Anyone know what I need to do to correct this Error in the
Apache
> Environment file???
>
>
>
> Thanks
>
> Bret
>
> WX7Y
|
|
|
