Re: soundmodem and fedora c3

[Jeff Camp <jcamp2@cox.net>]

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