[linrad] Re: linrad make errors

[Leif Asbrink <sm5bsz.com; leif@xxxxxxxxxxxxxxxx>]

Hi Dan,

> Thank you for the reply. NASM fixed the problem. xlinrad now builds and 
> loads, however it errors attempting to configure the sound card. The 
> audio controller is an Intel 82801DB/DBL/DBM on an IBM t41 laptop.

Do other sound programs run correctly?

Linrad just uses the device driver supplied by your system
and should not fail unless other applications also fail.

Now, in case you are using ALSA the above might not be quite true
because Linrad follows the specifications of OSS and Linux legacy 
sound. You must have alsa-oss installed, but unfortunately the
interface to the old specifications does not quite do what
it should. Among other things it does not tell the application
what capabilities your hardware has so you have to know that
yourself. Not as easy as one might think because rate conversions
may be done by the drive routine with sometimes odd results... 

In case you already have alsa-oss and other sound programs do
work, please give more details about what happens.
 
> My primary interest is HF SSB on 75 meters in the evening - a very noisy 
> environment. The introductory material seems to indicate a single 
> channel audio input is the place to start. Is this correct? How is 
> linrad on 'static' noise?
A single channel audio input means that you have to use a conventional
radio to feed the soundcard. In case you have a conventional radio
with 2.4 kHz bandwidth you would feed Linrad with a signal that is
stripped of all information about what happens outside the desired 
frequency range. Under such circumstances Linrad can not do anything
in SSB mode except giving you a narrower or steeper filter, none of
which will likely be beneficial.

You might find a better signal at the point where a modern 
radio has its A/D converter. Assuming your soundcard samples 
at 48 kHz any IF below 22 kHz or so would be fine for a single 
audio channel.

With some kind of direct conversion receiver you need two
audio channels. One for I and another for Q. That would
give a bandwidth of perhaps 45 kHz into the computer.
On the edges there may be false (alias) signals so all
the 48 kHz will not be useful.

With a reasonably wide bandwidth Linrad will remove local
QRN extremely efficiently. Lightening crasches that have
travelled a long distance that have smeared them out in time
and given each crasch a unique shape that is like white noise
can not be removed by subtraction since the waveform can not 
be known in advance. To what extent Linrad would be helpful
is unknown to me. The dumb blanker can be used to gate out
the crashes, but maybe it will work equally well to set
the AGC to maximum speed (both attack and release.) Another
thing that could help is to just allow the crashes to saturate
by running without AGC. If the SSB signal itself is allowed 
to saturate  a little (Linrad limits in Hilbert space, like 
a RF clipper) the sound will not go above the clip level
when the interference comes.

Maybe others can share their experiences with us on this list.
I have asked for difficult cases, but I do not have any
recording of an SSB signal that is difficult to copy.


73

Leif / SM5BSZ









> 
> Thanks - Dan
> 
> Roger Rehr wrote:
> > Hi, Dan,
> >
> > First of all, you need to install NASM.  You can get it with Synaptic, 
> > which FC6 would have I think, as I think Synaptic has RHL roots.  IF 
> > you don't have Synaptic, then do apt-get install nasm or sudo apt-get 
> > install nasm if you are not root.
> >
> > Once you do that, I think things should install fine.  The other no's 
> > are not a problem:
> >
> > As far as I know, none of the usual distros of Linux come with OSS 
> > installed by default at this time.  FC6 is no exception.   That is why 
> > you have the first set of no's.  I mostly run linrad on systems 
> > without OSS, though I have it on a few systems still.  Only install it 
> > if you have a problem you are very sure OSS will fix.
> >
> > The second set of no's are because you have not defined a 
> > users_hwaredriver.c file to run any special hardware you might have.  
> > There is no need to do so in all probability.  If you want to see an 
> > example of such a file go to:
> >
> > http://www.nitehawk.com/w3sz/users_hwaredriver.c
> >
> > This may not be an absolutely uptodate file;  I don't racall if it is 
> > the latest version I made or not.  I use it to send commands to my 
> > FT1000MP Mv V.  This version uses the serial port.  The windows 
> > version [wusers_hwaredriver.c] can send the commands over a network to 
> > another computer with a serial port hooked up to the FT1000.  I cheat 
> > and just write to a file and have another program I wrote send the 
> > data over the network.
> >
> > http://www.nitehawk.com/w3sz/wusers_hwaredriver.c , also not 
> > necessarily the latest file.
> >
> > vagl, etc are no's because you don't have svgalib installed.  You do 
> > not need it installed to use/run xlinrad which is what I run here 
> > these days.  I do not miss svgalib at all ;)
> >
> > Otherwise things look fine to me.  The important questions are all 
> > answered 'yes' as far as I can see.
> >
> > Leif has excellent infor on how to get going on his webpage.  If you 
> > need more, then check out the first 3 links [MS WORD document, MS WORD 
> > tables for the document, and figure 1] under the first heading, 
> > "General Review of DSP / SDR Techniques and VHF and Up Operating" on 
> > the webpage:
> >
> > http://www.nitehawk.com/w3sz/start.htm
> >
> > Good luck, and report back with any problems / questions.
> >
> >
> > 73,
> >
> > W3SZ
> > Roger Rehr
> > http://www.nitehawk.com/w3sz
> >
> >
> > Quoting Dan Sawyer <dansawyer@xxxxxxxxxxxxx>:
> >
> >> Good morning,
> >>
> >> Linrad fails to build on FC6. Below is the output. Configure had a 
> >> normal end but there seems to be lots of 'no' status.
> >>
> >> Thanks - Dan
> >>
> >> nasm -w-orphan-labels -felf -s hware.s -o hware.ol
> >> make: nasm: Command not found
> >> make: *** [hware.ol] Error 127
> >>
> >> checking for /usr/lib/oss/soundcard.h... no
> >> checking for /usr/local/lib/oss/soundcard.h... no
> >> checking for /lib/oss/soundcard.h... no
> >> checking for /var/lib/oss/soundcard.h... no
> >> checking for /opt/oss/soundcard.h... no
> >> checking for /root/oss/soundcard.h... no
> >> checking for /usr/lib/oss/include/sys/soundcard.h... no
> >> checking for /usr/local/lib/oss/include/sys/soundcard.h... no
> >> checking for /lib/oss/include/sys/soundcard.h... no
> >> checking for /var/lib/oss/include/sys/soundcard.h... no
> >> checking for /opt/oss/include/sys/soundcard.h... no
> >> checking for /root/oss/include/sys/soundcard.h... no
> >> checking for /dev/dsp... yes
> >> checking for /dev/sound/dsp... no
> >> checking for ./users_hwaredriver.c... no
> >> checking for ./users_hwaredriver.c... (cached) no
> >> checking for ./wusers_hwaredriver.c... no
> >> checking for ./wusers_hwaredriver.c... (cached) no
> >> checking for ./users_hwaredef.h... no
> >> checking for ./users_hwaredef.h... (cached) no
> >> checking for ./wusers_hwaredef.h... no
> >> checking for ./wusers_hwaredef.h... (cached) no
> >> checking for ./users_extra.c... no
> >> checking for ./users_extra.c... (cached) no
> >> checking for /etc/rc3.d/.... yes
> >> checking for /etc/init.d/rc3.d/.... no
> >> checking for /etc/rc.d/rc3.d/.... yes
> >> checking for gcc... gcc
> >> checking for C compiler default output file name... a.out
> >> checking whether the C compiler works... yes
> >> checking whether we are cross compiling... no
> >> checking for suffix of executables...
> >> checking for suffix of object files... o
> >> checking whether we are using the GNU C compiler... yes
> >> checking whether gcc accepts -g... yes
> >> checking for gcc option to accept ISO C89... none needed
> >> checking how to run the C preprocessor... gcc -E
> >> checking for grep that handles long lines and -e... /bin/grep
> >> checking for egrep... /bin/grep -E
> >> checking for ANSI C header files... yes
> >> checking for sys/types.h... yes
> >> checking for sys/stat.h... yes
> >> checking for stdlib.h... yes
> >> checking for string.h... yes
> >> checking for memory.h... yes
> >> checking for strings.h... yes
> >> checking for inttypes.h... yes
> >> checking for stdint.h... yes
> >> checking for unistd.h... yes
> >> checking vgagl.h usability... no
> >> checking vgagl.h presence... no
> >> checking for vgagl.h... no
> >> checking for /usr/src/linux... yes
> >> checking for /usr/src/linux-2.4... no
> >> configure: creating ./config.status
> >> config.status: creating Makefile
> >> config.status: creating conf.h
> >> config.status: creating lconf.h
> >> config.status: creating rusage.h
> >> config.status: creating ft245.c
> >> Normal End
> >>
> >>
> >>
> >> #############################################################
> >> This message is sent to you because you are subscribed to
> >>   the mailing list <linrad@xxxxxxxxxxxxxxxxxxxxx>.
> >> To unsubscribe, E-mail to: <linrad-off@xxxxxxxxxxxxxxxxxxxxx>
> >> To switch to the DIGEST mode, E-mail to 
> >> <linrad-digest@xxxxxxxxxxxxxxxxxxxxx>
> >> To switch to the INDEX mode, E-mail to 
> >> <linrad-index@xxxxxxxxxxxxxxxxxxxxx>
> >> Send administrative queries to  <linrad-request@xxxxxxxxxxxxxxxxxxxxx>
> >>
> >
> >
> > Roger Rehr
> > W3SZ
> > http://www.nitehawk.com/w3sz
> >
> 
> #############################################################
> This message is sent to you because you are subscribed to
>   the mailing list <linrad@xxxxxxxxxxxxxxxxxxxxx>.
> To unsubscribe, E-mail to: <linrad-off@xxxxxxxxxxxxxxxxxxxxx>
> To switch to the DIGEST mode, E-mail to <linrad-digest@xxxxxxxxxxxxxxxxxxxxx>
> To switch to the INDEX mode, E-mail to <linrad-index@xxxxxxxxxxxxxxxxxxxxx>
> Send administrative queries to  <linrad-request@xxxxxxxxxxxxxxxxxxxxx>
> 

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@xxxxxxxxxxxxxxxxxxxxx>.
To unsubscribe, E-mail to: <linrad-off@xxxxxxxxxxxxxxxxxxxxx>
To switch to the DIGEST mode, E-mail to <linrad-digest@xxxxxxxxxxxxxxxxxxxxx>
To switch to the INDEX mode, E-mail to <linrad-index@xxxxxxxxxxxxxxxxxxxxx>
Send administrative queries to  <linrad-request@xxxxxxxxxxxxxxxxxxxxx>


LINRADDARNIL