soundmodem and fedora c3

soundmodem and fedora c3

[Ron, VE3DTT]

On Tue., 8 Mar 2005, Luc Langehegermann wrote:

>Well, for soundmodem to work, you do not really need k-ax25. It is all >in 
>user space. You can see the soundmodem as an KISS-TNC, but with all in 
> >Software. Using an pipe, (pty/tty pair) you should be able to use it 
>without the >kernel


On Tue., 8 Mar 2005, Curt Mills, WE7U wrote:

>It just so happens that I configured soundmodem last night on SuSE
>9.1, and hooked Xastir to it.  I chose to configure it as a KISS
>interface instead of as an AX.25 kernel interface.  Used the
>user-mode soundmodem.  Worked great.  You don't need AX.25 in your
>kernel this way.  You don't need modules.

>In that case, set the soundmodemconfig program to KISS, and you'll
>end up using /dev/soundmodem0 as the interface name.

>In Xastir, create a new Serial KISS interface and type in
>/dev/soundmodem0 as the interface name.

>I also had to start the soundmodem interface.  Is SuSE it was
>"/etc/init.d/soundmodem start"

Thanks Curt and Luc,

It works! This is a terrific piece of software, I played with it for hours 
last night and it performed flawlessly. Curt advised me to try this on Mar. 
07, I did and it may have worked but it turns out that I had a secondary 
problem relating to an open chassis ground on my sound card. I didn't 
realize this until I removed the audio cord from the mic jack and noticed a 
lot of audio noise. This also might explain occasional missed signals on 
'agwpe' which I attributed to my volume settings.

On Tue., 8 Mar 2005, Richard Adams, wrote:

>On Tuesday 08 March 2005 19:20, Jeff Camp wrote:

>>Ron, I had the same problem with FC3 and soundmodem.  I solved it by
>>enabling MKISS support (CONFIG_MKISS) and rebuilding the kernel.  The
>>AX25 stuff was already there, but MKISS was not enabled by default.  It
>>works great now.

>I dont want to be a wet ass, however my fedora core kernel has # 
>CONFIG_HAMRADIO is not set
>which in turn means that there is no support for hamradio in fedora kernels 
>at all, that is if i see it correctly.

>To make it clear, my kernel is 2.6.9-1.681_FC3 which i do belive was 
>updated by up2date.

>Futher more i can see no support for AX25 in other kernels from fedora.

>On another note if i am correct, to configure mkiss in ´make menuconfig´ 
>one needs to check the box
>Device Drivers
>-> Networing Support
>Then check
>[ ] Amateur Radio support  --->

>Considering my .config file did not include an asterisk in that box i 
>presume that Fedore does not supply kernels with AX25 at all.

>Or am i incorrect in saying this.???


I still have a question which relates to the above postings by Richard Adams 
and Jeff Camp. My boot configuration tells me that I don't have ham radio 
support but menuconfig contains all asterisks in this area including ax.25, 
tellimg me that this is built-in. Is this a contradiction or am I 
misinterpreting it? Do I still have to re-build the kernel for ax.25 support 
or am I simply looking at a configuration issue?


On Tue., 8 Mar 2005, Mike Markowski, wrote:

>Just as a sanity check, did you remember to run soundmodemconfig so
>that it creates interface sm0?  And similarly, remember to actually run 
>soundmodem before starting xastir.  :-)  I know you probably did, but just 
>making sure all bases are covered!  After running soundmodem, make sure an 
>"ifconfig" shows that sm0 is up before starting xastir.

Good advice Mike!
There were a couple of times that I forgot. I know it sounds stupid but you 
can get a little punch drunk.

Thanks
73.
Ron VE3DTT

Re: soundmodem and fedora c3

[Jeff Camp]

This was bothering me so I took another look.  I loaded my original FC3 
  .config into menuconfig.  Amateur radio support was not enabled.  I 
loaded the .config I am currently using and it definitely was enabled, 
so I must have had to turn it on when I enabled KISS.

I hope I didn't confuse the issues with my previous post.  I don't think 
you  need AX25 support in the kernel to use soundmodem, but if you want 
MKISS then you have to enable AX25 to get it (unless you manually edit 
.config, which is a really, really bad idea).  The reason I needed AX25 
was that I have some other AX25 apps that require it.  I haven't tried 
routing between those devices and soundmodem, but I imagine you could do 
it with a pty/tty pair as Luc suggested.

Jeff




Ron, VE3DTT wrote:
> On Tue., 8 Mar 2005, Luc Langehegermann wrote:
> 
>> Well, for soundmodem to work, you do not really need k-ax25. It is all 
>> >in user space. You can see the soundmodem as an KISS-TNC, but with 
>> all in >Software. Using an pipe, (pty/tty pair) you should be able to 
>> use it without the >kernel
> 
> 
> 
> On Tue., 8 Mar 2005, Curt Mills, WE7U wrote:
> 
>> It just so happens that I configured soundmodem last night on SuSE
>> 9.1, and hooked Xastir to it.  I chose to configure it as a KISS
>> interface instead of as an AX.25 kernel interface.  Used the
>> user-mode soundmodem.  Worked great.  You don't need AX.25 in your
>> kernel this way.  You don't need modules.
> 
> 
>> In that case, set the soundmodemconfig program to KISS, and you'll
>> end up using /dev/soundmodem0 as the interface name.
> 
> 
>> In Xastir, create a new Serial KISS interface and type in
>> /dev/soundmodem0 as the interface name.
> 
> 
>> I also had to start the soundmodem interface.  Is SuSE it was
>> "/etc/init.d/soundmodem start"
> 
> 
> Thanks Curt and Luc,
> 
> It works! This is a terrific piece of software, I played with it for 
> hours last night and it performed flawlessly. Curt advised me to try 
> this on Mar. 07, I did and it may have worked but it turns out that I 
> had a secondary problem relating to an open chassis ground on my sound 
> card. I didn't realize this until I removed the audio cord from the mic 
> jack and noticed a lot of audio noise. This also might explain 
> occasional missed signals on 'agwpe' which I attributed to my volume 
> settings.
> 
> On Tue., 8 Mar 2005, Richard Adams, wrote:
> 
>> On Tuesday 08 March 2005 19:20, Jeff Camp wrote:
> 
> 
>>> Ron, I had the same problem with FC3 and soundmodem.  I solved it by
>>> enabling MKISS support (CONFIG_MKISS) and rebuilding the kernel.  The
>>> AX25 stuff was already there, but MKISS was not enabled by default.  It
>>> works great now.
> 
> 
>> I dont want to be a wet ass, however my fedora core kernel has # 
>> CONFIG_HAMRADIO is not set
>> which in turn means that there is no support for hamradio in fedora 
>> kernels at all, that is if i see it correctly.
> 
> 
>> To make it clear, my kernel is 2.6.9-1.681_FC3 which i do belive was 
>> updated by up2date.
> 
> 
>> Futher more i can see no support for AX25 in other kernels from fedora.
> 
> 
>> On another note if i am correct, to configure mkiss in ´make 
>> menuconfig´ one needs to check the box
>> Device Drivers
>> -> Networing Support
>> Then check
>> [ ] Amateur Radio support  --->
> 
> 
>> Considering my .config file did not include an asterisk in that box i 
>> presume that Fedore does not supply kernels with AX25 at all.
> 
> 
>> Or am i incorrect in saying this.???
> 
> 
> 
> I still have a question which relates to the above postings by Richard 
> Adams and Jeff Camp. My boot configuration tells me that I don't have 
> ham radio support but menuconfig contains all asterisks in this area 
> including ax.25, tellimg me that this is built-in. Is this a 
> contradiction or am I misinterpreting it? Do I still have to re-build 
> the kernel for ax.25 support or am I simply looking at a configuration 
> issue?
> 
> 
> On Tue., 8 Mar 2005, Mike Markowski, wrote:
> 
>> Just as a sanity check, did you remember to run soundmodemconfig so
>> that it creates interface sm0?  And similarly, remember to actually 
>> run soundmodem before starting xastir.  :-)  I know you probably did, 
>> but just making sure all bases are covered!  After running soundmodem, 
>> make sure an "ifconfig" shows that sm0 is up before starting xastir.
> 
> 
> Good advice Mike!
> There were a couple of times that I forgot. I know it sounds stupid but 
> you can get a little punch drunk.
> 
> Thanks
> 73.
> Ron VE3DTT
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: soundmodem and fedora c3

[Richard Adams]

On Wednesday 09 March 2005 17:25, you wrote:
> This was bothering me so I took another look.  I loaded my original FC3
>   .config into menuconfig.  Amateur radio support was not enabled.  I
> loaded the .config I am currently using and it definitely was enabled,
> so I must have had to turn it on when I enabled KISS.

There is no support for Ham protocols in Fedora3 kernels, you need to make 
your own kernel if you require ham radio support.

>
> I hope I didn't confuse the issues with my previous post.  I don't think
> you  need AX25 support in the kernel to use soundmodem, but if you want
> MKISS then you have to enable AX25 to get it (unless you manually edit
> .config, which is a really, really bad idea).

Well some say it is bad but most know its the easyest way to change things.
If you simply delete the section for AX25 support and its sub protocols and 
then run make oldconfig it will automaticly stop and ask you if you want AX25 
support in the kernel or as modules, when you select one or the other you 
will then be asked about netrom, rose, mkiss, scc drivers and the likes.
As soon as the last question has been answered the config process will fly on 
to the end.

Good or bad idea, well i´ve done it that way for years and never had problems.

> The reason I needed AX25 
> was that I have some other AX25 apps that require it.  I haven't tried
> routing between those devices and soundmodem, but I imagine you could do
> it with a pty/tty pair as Luc suggested.
>
> Jeff

Ron VE3DTT wrote.

> I still have a question which relates to the above postings by Richard Adams 
> and Jeff Camp. My boot configuration tells me that I don't have ham radio 
> support but menuconfig contains all asterisks in this area including ax.25, 
> tellimg me that this is built-in. Is this a contradiction or am I 
> misinterpreting it? Do I still have to re-build the kernel for ax.25 support 
> or am I simply looking at a configuration issue?

You may well have changed things yourself, but if you did not compile and 
install another kernel then you dont have AX25 support anywhere.

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

soundmodem and fedora c3

[Ron- VE3DTT]

Thanks to all who responded to my query.

I am aware that 'soundmodem' is usermode software but I tried loading the 
modules anyway, out of desperation.

'make menuconfig' suggests that ax.25 is hard coded in my kernel.

I have this sample of an 'axport' file which addresses 'sm0':

"sm0 KA1FSB-8 1200 255 2 145.630 Mhz "Wellesley, MA" 1200
bps soundmodem"

but it doesn't help.  I've tried many variations on sample configurations 
with negative results.

'xastir' will allow me to bring up a 'kiss' device on any port I choose but 
none communicate with soundmodem. The xastir manual tells me to use ax25.

'Listen' informs me that my ax25 ports aren't active.

--
"Windows:  Microsoft's tax on computer illiterates." -- WE7U

I, reluctantly, must include myself among the computer illiterate and when I 
discovered that 'soundmodem' is available for windows  I downloaded 
'soundmodem', 'flexnet32' and 'paxon' and was decoding packets within 15 
minutes start to finish. In view of the time it takes to get anything up and 
running with Linux, I'm inclined to counter that, perhaps,

Linux is Life's tax on those of us who don't have one.

It has to be it's own reward. I'll keep trying things until something works.

Thanks again,
Ron
73 VE3DTT

Re: soundmodem and fedora c3

[Curt, WE7U]

On Tue, 8 Mar 2005, Ron- VE3DTT wrote:

> I am aware that 'soundmodem' is usermode software but I tried loading the
> modules anyway, out of desperation.
>
> 'make menuconfig' suggests that ax.25 is hard coded in my kernel.
>
> I have this sample of an 'axport' file which addresses 'sm0':
>
> "sm0 KA1FSB-8 1200 255 2 145.630 Mhz "Wellesley, MA" 1200
> bps soundmodem"
>
> but it doesn't help.  I've tried many variations on sample configurations
> with negative results.
>
> 'xastir' will allow me to bring up a 'kiss' device on any port I choose but
> none communicate with soundmodem. The xastir manual tells me to use ax25.
>
> 'Listen' informs me that my ax25 ports aren't active.

It just so happens that I configured soundmodem last night on SuSE
9.1, and hooked Xastir to it.  I chose to configure it as a KISS
interface instead of as an AX.25 kernel interface.  Used the
user-mode soundmodem.  Worked great.  You don't need AX.25 in your
kernel this way.  You don't need modules.

In that case, set the soundmodemconfig program to KISS, and you'll
end up using /dev/soundmodem0 as the interface name.

In Xastir, create a new Serial KISS interface and type in
/dev/soundmodem0 as the interface name.

I also had to start the soundmodem interface.  Is SuSE it was
"/etc/init.d/soundmodem start"

I had to have the interface stopped in order to run the diagnostics
in soundmodemconfig and adjust my mixer settings with a separate
mixer program.  Once I had it configured I killed soundmodemconfig,
restarted soundmodem, and connected Xastir to it.  I'm running in
receive-only mode that way right now at home.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

Re: soundmodem and fedora c3

[Mike Markowski]

Just as a sanity check, did you remember to run soundmodemconfig so that 
it creates interface sm0?  And similarly, remember to actually run 
soundmodem before starting xastir.  :-)  I know you probably did, but 
just making sure all bases are covered!  After running soundmodem, make 
sure an "ifconfig" shows that sm0 is up before starting xastir.

Mike  AB3AP

Ron- VE3DTT wrote on 03/08/05 12:35 ET:
> Thanks to all who responded to my query.
> 
> I am aware that 'soundmodem' is usermode software but I tried loading 
> the modules anyway, out of desperation.
> 
> 'make menuconfig' suggests that ax.25 is hard coded in my kernel.
> 
> I have this sample of an 'axport' file which addresses 'sm0':
> 
> "sm0 KA1FSB-8 1200 255 2 145.630 Mhz "Wellesley, MA" 1200
> bps soundmodem"
> 
> but it doesn't help.  I've tried many variations on sample 
> configurations with negative results.
> 
> 'xastir' will allow me to bring up a 'kiss' device on any port I choose 
> but none communicate with soundmodem. The xastir manual tells me to use 
> ax25.
> 
> 'Listen' informs me that my ax25 ports aren't active.
> 
> -- 
> "Windows:  Microsoft's tax on computer illiterates." -- WE7U
> 
> I, reluctantly, must include myself among the computer illiterate and 
> when I discovered that 'soundmodem' is available for windows  I 
> downloaded 'soundmodem', 'flexnet32' and 'paxon' and was decoding 
> packets within 15 minutes start to finish. In view of the time it takes 
> to get anything up and running with Linux, I'm inclined to counter that, 
> perhaps,
> 
> Linux is Life's tax on those of us who don't have one.
> 
> It has to be it's own reward. I'll keep trying things until something 
> works.
> 
> Thanks again,
> Ron
> 73 VE3DTT
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: soundmodem and fedora c3

[Jeff Camp]

Ron, I had the same problem with FC3 and soundmodem.  I solved it by 
enabling MKISS support (CONFIG_MKISS) and rebuilding the kernel.  The 
AX25 stuff was already there, but MKISS was not enabled by default.  It 
works great now.

73,
Jeff
N0WJP


Ron- VE3DTT wrote:
> Thanks to all who responded to my query.
> 
> I am aware that 'soundmodem' is usermode software but I tried loading 
> the modules anyway, out of desperation.
> 
> 'make menuconfig' suggests that ax.25 is hard coded in my kernel.
> 
> I have this sample of an 'axport' file which addresses 'sm0':
> 
> "sm0 KA1FSB-8 1200 255 2 145.630 Mhz "Wellesley, MA" 1200
> bps soundmodem"
> 
> but it doesn't help.  I've tried many variations on sample 
> configurations with negative results.
> 
> 'xastir' will allow me to bring up a 'kiss' device on any port I choose 
> but none communicate with soundmodem. The xastir manual tells me to use 
> ax25.
> 
> 'Listen' informs me that my ax25 ports aren't active.
> 
> -- 
> "Windows:  Microsoft's tax on computer illiterates." -- WE7U
> 
> I, reluctantly, must include myself among the computer illiterate and 
> when I discovered that 'soundmodem' is available for windows  I 
> downloaded 'soundmodem', 'flexnet32' and 'paxon' and was decoding 
> packets within 15 minutes start to finish. In view of the time it takes 
> to get anything up and running with Linux, I'm inclined to counter that, 
> perhaps,
> 
> Linux is Life's tax on those of us who don't have one.
> 
> It has to be it's own reward. I'll keep trying things until something 
> works.
> 
> Thanks again,
> Ron
> 73 VE3DTT
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

Re: soundmodem and fedora c3

[Richard Adams]

On Tuesday 08 March 2005 19:20, Jeff Camp wrote:
> Ron, I had the same problem with FC3 and soundmodem.  I solved it by
> enabling MKISS support (CONFIG_MKISS) and rebuilding the kernel.  The
> AX25 stuff was already there, but MKISS was not enabled by default.  It
> works great now.

I dont want to be a wet ass, however my fedora core kernel has 
# CONFIG_HAMRADIO is not set
which in turn means that there is no support for hamradio in fedora kernels at 
all, that is if i see it correctly.

To make it clear, my kernel is 2.6.9-1.681_FC3 which i do belive was updated 
by up2date.

Futher more i can see no support for AX25 in other kernels from fedora.

On another note if i am correct, to configure mkiss in ´make menuconfig´ one 
needs to check the box
 Device Drivers
-> Networing Support
Then check
 [ ] Amateur Radio support  ---> 

Considering my .config file did not include an asterisk in that box i presume 
that Fedore does not supply kernels with AX25 at all.

Or am i incorrect in saying this.???

Also to make it quite clear i dont use a soundmodem so i cannot really 
conribute anything else to this thread, i just thought it worth mentioning.
Hope you dont mind.

> 73,
> Jeff
> N0WJP
>
> Ron- VE3DTT wrote:
> > Thanks to all who responded to my query.
> >
> > I am aware that 'soundmodem' is usermode software but I tried loading
> > the modules anyway, out of desperation.
> >
> > 'make menuconfig' suggests that ax.25 is hard coded in my kernel.
> >
> > I have this sample of an 'axport' file which addresses 'sm0':
> >
> > "sm0 KA1FSB-8 1200 255 2 145.630 Mhz "Wellesley, MA" 1200
> > bps soundmodem"
> >
> > but it doesn't help.  I've tried many variations on sample
> > configurations with negative results.
> >
> > 'xastir' will allow me to bring up a 'kiss' device on any port I choose
> > but none communicate with soundmodem. The xastir manual tells me to use
> > ax25.
> >
> > 'Listen' informs me that my ax25 ports aren't active.
> >
> > --
> > "Windows:  Microsoft's tax on computer illiterates." -- WE7U
> >
> > I, reluctantly, must include myself among the computer illiterate and
> > when I discovered that 'soundmodem' is available for windows  I
> > downloaded 'soundmodem', 'flexnet32' and 'paxon' and was decoding
> > packets within 15 minutes start to finish. In view of the time it takes
> > to get anything up and running with Linux, I'm inclined to counter that,
> > perhaps,
> >
> > Linux is Life's tax on those of us who don't have one.
> >
> > It has to be it's own reward. I'll keep trying things until something
> > works.
> >
> > Thanks again,
> > Ron
> > 73 VE3DTT
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: soundmodem and fedora c3

[Luc Langehegermann]

Hi Folks,

Well, for soundmodem to work, you do not really need k-ax25. It is all in user 
space. You can see the soundmodem as an KISS-TNC, but with all in Software. 
Using an pipe, (pty/tty pair) you should be able to use it without the kernel 
ax25 support!

So, Xastir <--> soundmodem should NOT need an running k-ax25

73, Luc

On Tuesday 08 March 2005 21:07, Richard Adams wrote:
> On Tuesday 08 March 2005 19:20, Jeff Camp wrote:
> > Ron, I had the same problem with FC3 and soundmodem.  I solved it by
> > enabling MKISS support (CONFIG_MKISS) and rebuilding the kernel.  The
> > AX25 stuff was already there, but MKISS was not enabled by default.  It
> > works great now.
>
> I dont want to be a wet ass, however my fedora core kernel has
> # CONFIG_HAMRADIO is not set
> which in turn means that there is no support for hamradio in fedora kernels
> at all, that is if i see it correctly.
>
> To make it clear, my kernel is 2.6.9-1.681_FC3 which i do belive was
> updated by up2date.
>
> Futher more i can see no support for AX25 in other kernels from fedora.
>
> On another note if i am correct, to configure mkiss in ´make menuconfig´
> one needs to check the box
>  Device Drivers
> -> Networing Support
> Then check
>  [ ] Amateur Radio support  --->
>
> Considering my .config file did not include an asterisk in that box i
> presume that Fedore does not supply kernels with AX25 at all.
>
> Or am i incorrect in saying this.???
>
> Also to make it quite clear i dont use a soundmodem so i cannot really
> conribute anything else to this thread, i just thought it worth mentioning.
> Hope you dont mind.
>
> > 73,
> > Jeff
> > N0WJP
> >
> > Ron- VE3DTT wrote:
> > > Thanks to all who responded to my query.
> > >
> > > I am aware that 'soundmodem' is usermode software but I tried loading
> > > the modules anyway, out of desperation.
> > >
> > > 'make menuconfig' suggests that ax.25 is hard coded in my kernel.
> > >
> > > I have this sample of an 'axport' file which addresses 'sm0':
> > >
> > > "sm0 KA1FSB-8 1200 255 2 145.630 Mhz "Wellesley, MA" 1200
> > > bps soundmodem"
> > >
> > > but it doesn't help.  I've tried many variations on sample
> > > configurations with negative results.
> > >
> > > 'xastir' will allow me to bring up a 'kiss' device on any port I choose
> > > but none communicate with soundmodem. The xastir manual tells me to use
> > > ax25.
> > >
> > > 'Listen' informs me that my ax25 ports aren't active.
> > >
> > > --
> > > "Windows:  Microsoft's tax on computer illiterates." -- WE7U
> > >
> > > I, reluctantly, must include myself among the computer illiterate and
> > > when I discovered that 'soundmodem' is available for windows  I
> > > downloaded 'soundmodem', 'flexnet32' and 'paxon' and was decoding
> > > packets within 15 minutes start to finish. In view of the time it takes
> > > to get anything up and running with Linux, I'm inclined to counter
> > > that, perhaps,
> > >
> > > Linux is Life's tax on those of us who don't have one.
> > >
> > > It has to be it's own reward. I'll keep trying things until something
> > > works.
> > >
> > > Thanks again,
> > > Ron
> > > 73 VE3DTT
> > >
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-hams"
> > > in the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: soundmodem and fedora c3

[Curt, WE7U]

On Tue, 8 Mar 2005, Luc Langehegermann wrote:

> Well, for soundmodem to work, you do not really need k-ax25. It is all in user
> space. You can see the soundmodem as an KISS-TNC, but with all in Software.
> Using an pipe, (pty/tty pair) you should be able to use it without the kernel
> ax25 support!
>
> So, Xastir <--> soundmodem should NOT need an running k-ax25

Correct, and I set it up that way last night.  I do however have
AX.25 capability in the kernel on that system, and have used it
before, but in this instance I did it all without any kernel AX.25
support.  All user-space stuff, and Xastir connects directly to
/dev/soundmodem0 with a Serial KISS Interface (Xastir's name for
it).

The downside of doing it this way is that you have one TNC dedicated
to one application.  Sure, you can chain other APRS applications off
of Xastir, but if you want to run other types of software, you'd
have to stop the Xastir interface and then connect a different app
up to /dev/soundmodem0.

If you set up AX.25 networking, lots of apps can share the same TNC
at one time, plus you can route TCP/IP packets just like you do with
ethernet.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

Re: soundmodem and fedora c3

[Jeff Camp]

You're right.  I went through my original .config and it didn't have any 
hamradio support enabled.  I must have turned it on when I went to set 
the CONFIG_MKISS support.

At any rate, this was a difference I noticed moving from RedHat 9 to 
Fedora C3.

73,
Jeff


Richard Adams wrote:
> On Tuesday 08 March 2005 19:20, Jeff Camp wrote:
> 
>>Ron, I had the same problem with FC3 and soundmodem.  I solved it by
>>enabling MKISS support (CONFIG_MKISS) and rebuilding the kernel.  The
>>AX25 stuff was already there, but MKISS was not enabled by default.  It
>>works great now.
> 
> 
> I dont want to be a wet ass, however my fedora core kernel has 
> # CONFIG_HAMRADIO is not set
> which in turn means that there is no support for hamradio in fedora kernels at 
> all, that is if i see it correctly.
> 
> To make it clear, my kernel is 2.6.9-1.681_FC3 which i do belive was updated 
> by up2date.
> 
> Futher more i can see no support for AX25 in other kernels from fedora.
> 
> On another note if i am correct, to configure mkiss in ´make menuconfig´ one 
> needs to check the box
>  Device Drivers
> -> Networing Support
> Then check
>  [ ] Amateur Radio support  ---> 
> 
> Considering my .config file did not include an asterisk in that box i presume 
> that Fedore does not supply kernels with AX25 at all.
> 
> Or am i incorrect in saying this.???
> 
> Also to make it quite clear i dont use a soundmodem so i cannot really 
> conribute anything else to this thread, i just thought it worth mentioning.
> Hope you dont mind.
> 
> 
>>73,
>>Jeff
>>N0WJP
>>
>>Ron- VE3DTT wrote:
>>
>>>Thanks to all who responded to my query.
>>>
>>>I am aware that 'soundmodem' is usermode software but I tried loading
>>>the modules anyway, out of desperation.
>>>
>>>'make menuconfig' suggests that ax.25 is hard coded in my kernel.
>>>
>>>I have this sample of an 'axport' file which addresses 'sm0':
>>>
>>>"sm0 KA1FSB-8 1200 255 2 145.630 Mhz "Wellesley, MA" 1200
>>>bps soundmodem"
>>>
>>>but it doesn't help.  I've tried many variations on sample
>>>configurations with negative results.
>>>
>>>'xastir' will allow me to bring up a 'kiss' device on any port I choose
>>>but none communicate with soundmodem. The xastir manual tells me to use
>>>ax25.
>>>
>>>'Listen' informs me that my ax25 ports aren't active.
>>>
>>>--
>>>"Windows:  Microsoft's tax on computer illiterates." -- WE7U
>>>
>>>I, reluctantly, must include myself among the computer illiterate and
>>>when I discovered that 'soundmodem' is available for windows  I
>>>downloaded 'soundmodem', 'flexnet32' and 'paxon' and was decoding
>>>packets within 15 minutes start to finish. In view of the time it takes
>>>to get anything up and running with Linux, I'm inclined to counter that,
>>>perhaps,
>>>
>>>Linux is Life's tax on those of us who don't have one.
>>>
>>>It has to be it's own reward. I'll keep trying things until something
>>>works.
>>>
>>>Thanks again,
>>>Ron
>>>73 VE3DTT
>>>
>>>
>>>-
>>>To unsubscribe from this list: send the line "unsubscribe linux-hams" in
>>>the body of a message to majordomo@vger.kernel.org
>>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-hams" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: soundmodem and fedora c3

[Richard Adams]

On Tuesday 08 March 2005 22:25, Jeff Camp wrote:
> You're right.  I went through my original .config and it didn't have any
> hamradio support enabled.  I must have turned it on when I went to set
> the CONFIG_MKISS support.
>
> At any rate, this was a difference I noticed moving from RedHat 9 to
> Fedora C3.

Well it suprised me as well, but with fedora we all get suprosed in some way 
or another.

> 73,
> Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: soundmodem and fedora c3

[oz6bl]

Hi Ron

I think that some of your problems arise out of a slight misconception
which I also made when I started:

>
> I have this sample of an 'axport' file which addresses 'sm0':
>
> sm0 KA1FSB-8 1200 255 2 145.630 Mhz "Wellesley, MA" 1200
> bps soundmodem

The 'sm0' in the line above does *not* reference an interface, it's just a
name you give this particular port. The binding between an ax.25 port
defined in axports and an interface is made based on the callsign you use.
Since you assign port sm0 to "KA1FSB-8" you must also use "KA1FSB-8" when
you create your sound interface (hwaddr="KA1FSB-8")

I hope this is of help.

Best 73 de Bent/OZ6BL

soundmodem and fedora c3

[ronald schultz]

Help!

I'm ready to toss the bath water et.al.

I can't make 'soundmodem' work with my FC3 package and although it makes a 
nice oscilloscope and sets up a conf file in /etc/ax25, I can't get it to 
function with "ax25", 'xastir' or 'linpac'.

Addressing is a problem, I have no 'sm' or 'soundmodem modules'. I tried to 
insmod 'bsd_comp.o', 'hdlcdrv.o' and 'soundmodem.o' as instructed, at Thomas 
Sailer's site, but received an invalid file type error with each of them.

Part of the problem or maybe all of the problem is in configuring the 
'ax25d.conf' and 'axports' files. The instructions are pretty clear except 
for the 'exec' part of 'ax25d.conf', I don't know which program I'm 
addressing here "soundmodem", 'xastir', 'linpac', 'ax25d'? All of them seem 
to be required. However until I can get 'soundmodem' to associate my 
callsign with something valid other than 'sm0' then the info in 'axports' is 
meaningless.

I've spent seven days and have printed out over 80 pages of documents trying 
to get a handle on this and I'm sure that I'm missing something 
embarrassingly obvious.

Thanks

Ron VE3DTT
73

Re: soundmodem and fedora c3

[Curt, WE7U]

On Mon, 7 Mar 2005, ronald schultz wrote:

> I can't make 'soundmodem' work with my FC3 package and although it makes a
> nice oscilloscope and sets up a conf file in /etc/ax25, I can't get it to
> function with "ax25", 'xastir' or 'linpac'.
>
> Addressing is a problem, I have no 'sm' or 'soundmodem modules'. I tried to
> insmod 'bsd_comp.o', 'hdlcdrv.o' and 'soundmodem.o' as instructed, at Thomas
> Sailer's site, but received an invalid file type error with each of them.
>
> Part of the problem or maybe all of the problem is in configuring the
> 'ax25d.conf' and 'axports' files. The instructions are pretty clear except
> for the 'exec' part of 'ax25d.conf', I don't know which program I'm
> addressing here "soundmodem", 'xastir', 'linpac', 'ax25d'? All of them seem
> to be required. However until I can get 'soundmodem' to associate my
> callsign with something valid other than 'sm0' then the info in 'axports' is
> meaningless.

linpac and Xastir are applications.  ax25d is a daemon that looks
for incoming AX.25 connections, so you can probably skip that one
for now too while you're trying to get your port working.  Focus on
the /etc/ax25/axports file.

I've found that example files from someone's working AX.25 setup
work wonders.  All I have set up here is a dummy interface for
injecting binary OpenTrac packets, so I can't help you with my files
from here much, except to show the general format.  Hopefully
someone will give you a working example shortly.  Here's what I have
though:


> cat axports
# /etc/ax25/axports
#
# The format of this file is:
#
# name callsign speed paclen window description
#
#1      OH2BNS-1        1200    255     2       144.675 MHz (1200 bps)
#2      OH2BNS-9        38400   255     7       TNOS/Linux  (38400 bps)
#
#
opentrac we7u-3         4800    255     7       OpenTrac Testing Port
#
#



> I've spent seven days and have printed out over 80 pages of documents trying
> to get a handle on this and I'm sure that I'm missing something
> embarrassingly obvious.

The AX.25 HOWTO document is probably the best start, but it often is
not quite up-to-date with the current software.  Therefore working
configs are best to start from.

As I recall there are two ways of configuring soundmodem:


    *) Using Kernel AX.25
    *) As a serial KISS device


Configuring the former is sometimes a trick.  Your linux kernel has
to have been compiled with AX.25 support.  If it hasn't, you won't
be able to get it working unless you compile a new kernel that does,
or replace your kernel with one which does.

If you use the first method, try the "listen" program to see if your
port is working.  I think I had to run listen as root in order to
have it open the port.  The listen program would be the minimum test
setup you need in order to verify functionality.

Configuring the latter is easier, not requiring kernel AX.25
support, but then you won't be able to share the port among multiple
applications at once.  Since it is easier, you might want to attempt
that first though.  I know of people running soundmodem on Solaris
boxes, which don't have AX.25 kernel support, by using this method.

Once you're sure your port is working I can help you get Xastir
going (or subscribe to the Xastir mailing list and get more people
helping you).

There are also two variations of soundmodem:  kernel mode and
usermode.  Don't get them confused.  I think the supported one these
days is the usermode soundmodem.  Correct?

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

Re: soundmodem and fedora c3

[Tomi Manninen]

On Mon, 2005-03-07 at 19:03, Curt, WE7U wrote:

> There are also two variations of soundmodem:  kernel mode and
> usermode.  Don't get them confused.  I think the supported one these
> days is the usermode soundmodem.  Correct?

Yes. In fact kernel soundmodem was completely removed from
2.6 kernels so usermode is what Ronald needs. Forget the
soundmodem modules...

-- 
Tomi Manninen / OH2BNS / KP20JF74