After my findings re the Compiling of WSPR on various platforms I decided to try an older already Compiled version to see if I could prove if it is a failing of the O/S that is causing the ‘Blindness’ (no waterfall) seen in my last post or the WSPR code.
It is proven. With latest development code I cannot repeat my previous successful Compiles. Two errors show up, one with a message ‘cannot connect to display’ and a crash. the other with the lack of Waterfall.
I suspect that the source code has been broken somewhere between Version 1.01 and 1.1.
Meanwhile I took another look at G4ILO compile for the EeePC and got it running, I like some of his personalising particularly the band map background hue change, it makes it so much more readable.
Hey I can do that, here is my personalised WSPR – Linux on test receiving my Multimode MEPT and decoding the WSPR section every 6 minutes. Previously the report labels were not complete and out of alignment, now neatly arranged. I am not one for re inventing the wheel for the sake of it so I used the same colours as G4ILO for the band map.
I have never programmed in Python Language this was an interesting little intro.
I have it working on two different Distro’s. Next step can we get it working away from the Debian and closely related Platforms.
I have completed my look into the Compiling of WSPR on LInux. Tonight I decided to give a compile a run on 80m.
My search was for a Linux Release that would do all the Ham modes. I have that running but no with Fldigi for PSK31 etc. GMFSK has to fill that role. If you didn’t get a range of modes all working on one Linux you face the situation where to change Mode you have to change Computer. Totally unsatisfactory.
I have Compiled WSPR on 12 Releases of the Linux Operating System. There are 5 common fail mechanisms across the range. ‘Segmentation Fault’ Error Message – ‘Don’t know how to Compile Fortran on this Platform’ Error Message – ‘Cant find Audio library file’ Error Message – ‘Compiles but does not work in various ways’ You get no clues for these.
Finally there is the works fine in all aspects but is missing something or the labels and fonts are awry.
Below is an example in the final group. I spotted signals from the UK, Germany and Poland, my 100mW made it to the received stations excepting the Polish one, but then his Power was 20dB higher than mine.
Fortran problems stem from the original Windows Compile which did not Compile with the available Linux Compilers, only the old 95 version.
Audio Library problems are due to new Library versions being released and used on the newer Linux Releases and WSPR not being written to use them.
To sum up, its a mess and and getting worse. My first successful compile aka OH2GQC is no longer repeatable, maybe due to a revision in the source code. The Latest Ubuntu and other new releases fail, for me anyway.
The on going debate.
I don’t see that the attractive layout of Ubuntu 8.10 has any reflection on the operation of Ham Radio Software no matter how processor intensive the application is. In the non 3D version it has an X11 static desktop, there can’t be much different from any other Linux screen. Just ’cause its plain ugly dose not mean its efficient.
8.10 is an efficient slim O/S. I wish I could finger the cause of the problems being experienced.
The blame put on Vista by those who have not tried it is justified because the problems are widespread, well documented and obvious.
You can’t say the same for Intrepid I have tried it, it is fast.
What have done to my Linux Ma
What have they done to my Linux
It should be the one to put Vista to shame
But its turned out all wrong
What have they done to my Linux
What a shame I had really high hopes for the latest Ubuntu. As it is, WSJT which used to fall over with a ‘Segmentation Fault’ on 8.04 installs perfectly on 8.10.
WSPR didn’t Compile properly on Ubuntu 8.04, now it Compiles OK but falls over with a ‘Segmentation Fault’.
This is not just me, it is a wide spread problem. It may well be that WSJT and WSPR are lacking fundamentally in compatibility. It does seem odd that two programs out of the same branch of the tree do different things on different Releases of Ubuntu.
I have scrapped my 8.04, re-installed and gone through it all again. What I can say it is NOT due to are.
1)The WSPR version Number.
2)The need to compile with an old obsolete Fortran Compiler.
3)Conflicts with Portaudio0 and Portaudio-v19 in the Compile.
I have both WSJT and WSPR running on a Debian Distro agian. As you go away from Debian then the problems start.
I was hoping for better news today. A full suite of working Amateur Radio Programs on Linux.
WSJT installs on Ubuntu at last. I had Digimodes, Fax, SSTV and WSJT all working on a Hard Drive Desktop and a USB stick or two. Thinking laterally I thought now WSPR will Compile easily on the 8.10 platform.
Right click on this pretty picture and select View image for full size.
I spent a lot of time and it is refusing blow it, I have WSPR Compiled on 8.04, WSJT crashes on that. What a shame Linux nearly got to evicting a shack computer, it is always nearly with Linux though.
I won’t give up.
Still investigating the EeePC and Ham Radio I have about concluded my investigations into what can be done and how I would approach the subject if I had one.
Much talk is of using Ubuntu external to the Eee. On a USB Hard Drive this may work, no tests done at this end.
Full Ubuntu running on a USB Stick I have tried. Using the method available Ubuntu is not like the Debian Install in my previous post, it soon starts to run too slowly as data clogs it up. Just like Microsoft, only it happened much faster,
The cut down Ubuntu version will need installing in place of the Xandros on the SSD Memory. It seems to run OK and I have used Fldigi Multimode on it on my Desktop Computer.
Here is the Desktop.
Installation in the absence of a USB CD Drive would involve installing Ubuntu on a USB stick and installing to the SSD from there.
I see no reason why it should not work, I actually have got to like the Live USB version I am running.
Here is Fldigi on air, it runs full screen.
I have tried WSJT and it crashes, this is normal for Ubuntu, if the ‘Linux Gurus’ cant sort that then I am not going to try.
I tried the G4ILO compilation of WSPR for the EeePC, that fails demanding library files I couldn’t find for download, I won’t spend too much time on it as any changes I make are lost on switch off on my version.
The Internet Browser is Firefox, like all the Linux USB installs I have it goes like a rocket. Here is my blog, previous page, full screen grab.
That about concludes what I can do without an actual machine. I am surprised that there does not seem to be more from users on the web.
I still think that Asus with the EeePC has done Linux no good. The trouble lies with calling it a PC, it isn’t, it is a Web Browser come Notebook. I wonder how many people appreciate the fact that they have a grand safe Web Browser courtesy of Linux and a machine doing what it says on the box, or how many blame Linux for its lack of versatility.
Hams have purchased them with the intent of using them as a portable PC for the hobby and hit a brick wall. An approach to overcome the short falls has been to use a USB Flash Drive and put a ‘decent’ Linux Distro on there. The problems then encountered are with the Drivers for the EeePC and the Screen Resolution.
I am still showing an unhealthy interest in the EeePC. As a Web browser when I am on my travels it would be handy.I have found the thought of Linux Comms from a Stick interesting so I just had to try it.
Fldigi working in RX TX mode off a Stick, no Hard Drive at all. It was quite a bit of work, there are many pitfalls, it is not going to work on the EeePC, my machines work on Linux anyway.
There is all sorts of info available on the Web, I have got to say the same as OH2GQC, “no guarantees no nothing”.