You can set the sort order of messages? Just click on the link in the date column. Your preferences will be remembered, so you don't have to do it again when you return.
My apologies for taking so long to get this project out. It really was vaporware for a while. I'll be checking in here to offer support. Its free, unless you want to develop - then you need the full version of Max. I'd be very interested to get any feedback, complaints, suggestions. I demonstrated it at the Cycling74 expo at NYUpoly in Brooklyn last month - almost got arrested while stringing up a dipole using the suspicious looking EZ-hang device. Anyway have fun & thanks to all the developers whose code I 'used' to get the device drivers running.
I am running Ubuntu 11.10 64 bit and having a few problems with Gqrx.
After a few false starts and dead ends I managed to get Gqrx compiled from git.
For some reason my pc then decided to set the FCD as device 0, i.e. hw:0, which
Gqrx didn't seem to like. I got the system to set the FCD as hw:2 last night and
Gqrx started working well. This morning, after switching the pc on my FCD once
again got set to hw:0 so I unplugged it, rebooted and plugged it back in so it
was hw:2. However Gqrx is now giving the same results as when the FCD was on
hw:0, see below:
simon@simon-desktop:~$ /home/simon/gqrx-build-desktop/gqrx
(gqrx:2914): Gtk-WARNING **: Unable to locate theme engine in module_path:
"pixmap",
(gqrx:2914): Gtk-WARNING **: Unable to locate theme engine in module_path:
"pixmap",
(gqrx:2914): Gtk-WARNING **: Unable to locate theme engine in module_path:
"pixmap",
(gqrx:2914): Gtk-WARNING **: Unable to locate theme engine in module_path:
"pixmap",
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
>>> gr_fir_ccc: using SSE
resampler_ff:
inter: 1
decim: 2
>>> gr_fir_fff: using SSE
aOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaO\
aOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaO\
aOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaO\
aOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaO\
aOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaO.......and so on for ever until I
kill the process.
The syslog shows this error:
Nov 17 10:28:56 simon-desktop kernel: [ 2331.278341] cannot submit datapipe for
urb 0, error -28: not enough bandwidth
Running the pre-compiled binary version of Gqrx and running one of the FCD
examples in gnuradio-companion also gives the same result.
Has anyone else experienced this problem and/or can suggest a solution?
Regards
Simon
G0FCU.
Concerning the audio overrun (aOaO...) issue, I have seen it a few times on a laptop but it always disappears after reboot. I suspect it is a hardware and/or driver issue but I don't have sufficient info to find out more about it.
I am working on a new audio backend for gqrx which will hopefully eliminate both the aO issue and the problem with changing device names.
Alex
On Thu, Nov 17, 2011 at 11:44 AM, g0fcu <simon@...> wrote:
I am running Ubuntu 11.10 64 bit and having a few problems with Gqrx.
After a few false starts and dead ends I managed to get Gqrx compiled from git. For some reason my pc then decided to set the FCD as device 0, i.e. hw:0, which Gqrx didn't seem to like. I got the system to set the FCD as hw:2 last night and Gqrx started working well. This morning, after switching the pc on my FCD once again got set to hw:0 so I unplugged it, rebooted and plugged it back in so it was hw:2. However Gqrx is now giving the same results as when the FCD was on hw:0, see below:
(gqrx:2914): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
(gqrx:2914): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
(gqrx:2914): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
(gqrx:2914): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
Could not resolve property : pattern10600
>>> gr_fir_ccc: using SSE
resampler_ff:
inter: 1
decim: 2
>>> gr_fir_fff: using SSE
aOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaOaO.......and so on for ever until I kill the process.
The syslog shows this error:
Nov 17 10:28:56 simon-desktop kernel: [ 2331.278341] cannot submit datapipe for urb 0, error -28: not enough bandwidth
Running the pre-compiled binary version of Gqrx and running one of the FCD examples in gnuradio-companion also gives the same result.
Has anyone else experienced this problem and/or can suggest a solution?
unfortunately it doesn't disappear after a reboot here, but the
problem with the FCD taking device 0 is annoying because it seems
that other programs, like Quisk, expect the output sound device to
be on hw:0. It seems like an entry in a file in /etc/modprobe.d can
fix that but I haven't looked into it enough to work out how.
I look forward to your new audio backend.
Simon.
On 17/11/11 17:24, Alexandru Csete wrote:
Hi Simon,
Concerning the audio overrun (aOaO...) issue, I have seen
it a few times on a laptop but it always disappears after
reboot. I suspect it is a hardware and/or driver issue but
I don't have sufficient info to find out more about it.
I am working on a new audio backend for gqrx which will
hopefully eliminate both the aO issue and the problem with
changing device names.
you may be pleased to hear that I've successfully built Gqrx
(and GNU Radio 3.4.2) from source under Ubuntu 11.04, and
listened to the local 23cm beacon &c.
However, there is a problem with Ubuntu 11.10
(Oneiric). For some reason the GNU Radio header files are not being
picked up, which results in a major compile error! That can be fixed
to some extent in the qgrx.pro file, with similar lines to add an
INCLUDEPATH to those used for OS/X. However, that is not enough for
a successful compilation. (And I do not really wish to revert to
Ubuntu 11.04 or install Debian!) [One suspects/is very sure that
this problem is because of a bug in pkg-config:
Ubuntu bug #853126.]
As part of this activity I have prepared a set of instructions as to
how, under Ubuntu, to:
Compile GNU Radio
Compile gr-fcd
Set up access to GitHub
Compile Gqrx
How do you prefer bugs against your Gqrx builds to be reported?
Via this group, directly, or some other way?
I have to say that building Gqrx under Qt Creator was very easy,
once everything else had been set up.
it does build under Ubuntu 11.10 (64 bit), I have to export the
following variables before running qtcreator (from the same shell):
export
PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
export LD_LIBRARY_PATH=/usr/local/lib/python2.7/dist-packages/fcd
Unfortunately, when I run it I get audio overrun, which seems to be
related to the fact that I'm finding it difficult to get my system
to allocated anything other than hw:0 to the FCD.
Regards
Simon
G0FCU.
On 26/11/11 16:36, Robin Gape (FCD) wrote:
Â
Alex, and the rest of the group,
you may be pleased to hear that I've successfully built Gqrx
(and GNU Radio 3.4.2) from source under Ubuntu 11.04,
and listened to the local 23cm beacon &c.
However, there is a problem with Ubuntu 11.10
(Oneiric). For some reason the GNU Radio header files are
not being picked up, which results in a major compile
error! That can be fixed to some extent in the qgrx.pro
file, with similar lines to add an INCLUDEPATH to those
used for OS/X. However, that is not enough for a
successful compilation. (And I do not really wish to
revert to Ubuntu 11.04 or install Debian!) [One
suspects/is very sure that this problem is because of a bug
in pkg-config: Ubuntu bug #853126.]
As part of this activity I have prepared a set of
instructions as to how, under Ubuntu, to:
Compile GNU Radio
Compile gr-fcd
Set up access to GitHub
Compile Gqrx
How do you prefer bugs against your Gqrx builds to
be reported? Via this group, directly, or some other
way?
I have to say that building Gqrx under Qt Creator was very
easy, once everything else had been set up.
I'm interested to know more about the problem, but if it is a bug in pkg-config package of Ubuntu then I'm not sure it should be fixed in gqrx? I am, however, puzzled because I have no problems with building and running gqrx on Ubuntu 11.10 64 bit and I don't do anything different from what I do in 11.04 and 10.10. Maybe you have multiple installations of GNU Radio and the build picks up the wrong one.
Alex
On Sat, Nov 26, 2011 at 5:36 PM, Robin Gape (FCD) <fcd@...> wrote:
Alex, and the rest of the group,
you may be pleased to hear that I've successfully built Gqrx
(and GNU Radio 3.4.2) from source under Ubuntu 11.04, and
listened to the local 23cm beacon &c.
However, there is a problem with Ubuntu 11.10
(Oneiric). For some reason the GNU Radio header files are not being
picked up, which results in a major compile error! That can be fixed
to some extent in the qgrx.pro file, with similar lines to add an
INCLUDEPATH to those used for OS/X. However, that is not enough for
a successful compilation. (And I do not really wish to revert to
Ubuntu 11.04 or install Debian!) [One suspects/is very sure that
this problem is because of a bug in pkg-config:
Ubuntu bug #853126.]
As part of this activity I have prepared a set of instructions as to
how, under Ubuntu, to:
Compile GNU Radio
Compile gr-fcd
Set up access to GitHub
Compile Gqrx
How do you prefer bugs against your Gqrx builds to be reported?
Via this group, directly, or some other way?
I have to say that building Gqrx under Qt Creator was very easy,
once everything else had been set up.
You can add those export lines to the end of the .bashrc file in the home directory and they will be executed automatically every time you open a new terminal.
Concerning the audio devices, I have pushed some changes to the master repository so that gqrx now tries to autodetect the FCD device. You can try it by doing a "git pull" then rebuild.
Alex
On Sat, Nov 26, 2011 at 6:13 PM, Simon Kennedy <simon@...> wrote:
Robin,
it does build under Ubuntu 11.10 (64 bit), I have to export the
following variables before running qtcreator (from the same shell):
export
PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
export LD_LIBRARY_PATH=/usr/local/lib/python2.7/dist-packages/fcd
Unfortunately, when I run it I get audio overrun, which seems to be
related to the fact that I'm finding it difficult to get my system
to allocated anything other than hw:0 to the FCD.
Regards
Simon
G0FCU.
On 26/11/11 16:36, Robin Gape (FCD) wrote:
Alex, and the rest of the group,
you may be pleased to hear that I've successfully built Gqrx
(and GNU Radio 3.4.2) from source under Ubuntu 11.04,
and listened to the local 23cm beacon &c.
However, there is a problem with Ubuntu 11.10
(Oneiric). For some reason the GNU Radio header files are
not being picked up, which results in a major compile
error! That can be fixed to some extent in the qgrx.pro
file, with similar lines to add an INCLUDEPATH to those
used for OS/X. However, that is not enough for a
successful compilation. (And I do not really wish to
revert to Ubuntu 11.04 or install Debian!) [One
suspects/is very sure that this problem is because of a bug
in pkg-config: Ubuntu bug #853126.]
As part of this activity I have prepared a set of
instructions as to how, under Ubuntu, to:
Compile GNU Radio
Compile gr-fcd
Set up access to GitHub
Compile Gqrx
How do you prefer bugs against your Gqrx builds to
be reported? Via this group, directly, or some other
way?
I have to say that building Gqrx under Qt Creator was very
easy, once everything else had been set up.
I've downloaded and built the new code but I don't think it is
detecting the FCD correctly. Will it try to detect it and override
the value in the .config file? If so, the master version I have got
from git is not working correctly.
I still get the audio overrun problem anyway :-(
Simon.
On 26/11/11 18:01, Alexandru Csete wrote:
Hi Simon,
You can add those export lines to the end of the .bashrc
file in the home directory and they will be executed
automatically every time you open a new terminal.
Concerning the audio devices, I have pushed some changes
to the master repository so that gqrx now tries to
autodetect the FCD device. You can try it by doing a "git
pull" then rebuild.
thanks for that. I'll try your suggestion tomorrow (Sunday).
Alex: pkg-config should have picked out the location of the
GNU Radio header files &c. Since it didn't, and there is already
a similar bug report against pkg-config for Ubuntu 11.10, I'm
inclined to think that pkg-config has a problem. And to allay your
concern, there is only one build of GNU Radio on both test
machines: 3.4.2 stable!
There are other issues with GNU Radio, and it seems easiest to stick
with a stable build, rather than going through an 80 or 40 minute
compile wait on the two machines!
Simon: did you de-activate the FCD from the normal pulse
audio system? (In Ubuntu (and probably Fedora), deselect the FCD
from the Sound Preference Hardware Tab.)
73 all
Robin, G8DQX
On 26/11/11 17:13, Simon Kennedy wrote:
Â
Robin,
it does build under Ubuntu 11.10 (64 bit), I have to
export the following variables before running qtcreator
(from the same shell):
export
PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
export
LD_LIBRARY_PATH=/usr/local/lib/python2.7/dist-packages/fcd
Unfortunately, when I run it I get audio overrun, which
seems to be related to the fact that I'm finding it
difficult to get my system to allocated anything other
than hw:0 to the FCD.
Regards
Simon
G0FCU.
On 26/11/11 16:36, Robin Gape (FCD) wrote:
Â
Alex, and the rest of the group,
you may be pleased to hear that I've successfully
built Gqrx (and GNU Radio 3.4.2) from source
under Ubuntu 11.04, and listened to the local
23cm beacon &c.
However, there is a problem with Ubuntu
11.10 (Oneiric). For some reason the GNU Radio
header files are not being picked up, which results in
a major compile error! That can be fixed to some
extent in the qgrx.pro file, with similar lines to add
an INCLUDEPATH to those used for OS/X. However, that
is not enough for a successful compilation. (And I do
not really wish to revert to Ubuntu 11.04 or install
Debian!) [One suspects/is very sure that this problem
is because of a bug in pkg-config:
Ubuntu bug #853126.]
As part of this activity I have prepared a set of
instructions as to how, under Ubuntu, to:
Compile GNU Radio
Compile gr-fcd
Set up access to GitHub
Compile Gqrx
How do you prefer bugs against your Gqrx builds
to be reported? Via this group, directly, or
some other way?
I have to say that building Gqrx under Qt Creator was
very easy, once everything else had been set up.
I hadn't but I have tried this and it doesn't make any difference.
Simon.
On 27/11/11 01:32, Robin Gape (FCD) wrote:
Â
Simon: did you de-activate the FCD from the normal
pulse audio system? (In Ubuntu (and probably Fedora),
deselect the FCD from the Sound Preference Hardware Tab.)
Yes, in the current state it simply ignores what you put in the "Input device" field. It looks in /proc/asound/cards and extracts the device ID from there (the same process people were supposed to do before).
Maybe the problem is with the audio output. Do you use pulse as output device? The audio output rate is currently fixed at 48 kHz, but that shouldn't matter when using pulse device.
Alex
On Sat, Nov 26, 2011 at 11:29 PM, Simon Kennedy <simon@...> wrote:
Alex,
I've downloaded and built the new code but I don't think it is
detecting the FCD correctly. Will it try to detect it and override
the value in the .config file? If so, the master version I have got
from git is not working correctly.
I still get the audio overrun problem anyway :-(
Simon.
On 26/11/11 18:01, Alexandru Csete wrote:
Hi Simon,
You can add those export lines to the end of the .bashrc
file in the home directory and they will be executed
automatically every time you open a new terminal.
Concerning the audio devices, I have pushed some changes
to the master repository so that gqrx now tries to
autodetect the FCD device. You can try it by doing a "git
pull" then rebuild.
In many out of the box linux distributions, pkg-config will know about libraries and headers that are installed in /usr/lib(64) and /usr/include but not necessarily what is installed in /usr/local/lib(64) and /usr/local/include. This is unfortunate because packages compiled from source are by default installed in /usr/local/. Therefore, one must add /usr/local/lib/pkgconfig or /usr/local/lib64/pkgconfig to the $PKG_CONFIG_PATH:
The bug you referred to seems to be something different. It concerns incorrect compiler and linker flags returned by pkg-config for the gio package.
Alex
On Sun, Nov 27, 2011 at 2:32 AM, Robin Gape (FCD) <fcd@...> wrote:
Simon,
thanks for that. I'll try your suggestion tomorrow (Sunday).
Alex: pkg-config should have picked out the location of the
GNU Radio header files &c. Since it didn't, and there is already
a similar bug report against pkg-config for Ubuntu 11.10, I'm
inclined to think that pkg-config has a problem. And to allay your
concern, there is only one build of GNU Radio on both test
machines: 3.4.2 stable!
There are other issues with GNU Radio, and it seems easiest to stick
with a stable build, rather than going through an 80 or 40 minute
compile wait on the two machines!
Simon: did you de-activate the FCD from the normal pulse
audio system? (In Ubuntu (and probably Fedora), deselect the FCD
from the Sound Preference Hardware Tab.)
73 all
Robin, G8DQX
On 26/11/11 17:13, Simon Kennedy wrote:
Robin,
it does build under Ubuntu 11.10 (64 bit), I have to
export the following variables before running qtcreator
(from the same shell):
export
PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
export
LD_LIBRARY_PATH=/usr/local/lib/python2.7/dist-packages/fcd
Unfortunately, when I run it I get audio overrun, which
seems to be related to the fact that I'm finding it
difficult to get my system to allocated anything other
than hw:0 to the FCD.
Regards
Simon
G0FCU.
On 26/11/11 16:36, Robin Gape (FCD) wrote:
Alex, and the rest of the group,
you may be pleased to hear that I've successfully
built Gqrx (and GNU Radio 3.4.2) from source
under Ubuntu 11.04, and listened to the local
23cm beacon &c.
However, there is a problem with Ubuntu
11.10 (Oneiric). For some reason the GNU Radio
header files are not being picked up, which results in
a major compile error! That can be fixed to some
extent in the qgrx.pro file, with similar lines to add
an INCLUDEPATH to those used for OS/X. However, that
is not enough for a successful compilation. (And I do
not really wish to revert to Ubuntu 11.04 or install
Debian!) [One suspects/is very sure that this problem
is because of a bug in pkg-config:
Ubuntu bug #853126.]
As part of this activity I have prepared a set of
instructions as to how, under Ubuntu, to:
Compile GNU Radio
Compile gr-fcd
Set up access to GitHub
Compile Gqrx
How do you prefer bugs against your Gqrx builds
to be reported? Via this group, directly, or
some other way?
I have to say that building Gqrx under Qt Creator was
very easy, once everything else had been set up.
Hmmmm ok but how can we solve that ?!?
Next firmware please :-)
I thought that the firmware was setting the correct filter
But I did not check the whole fcd bands ...
I only used it on 2m and 70 cm yet
After I have seen the other mail about 868100I checked and
found the other
fault (100kc lower lowest uhf filter used)
I thought that the switching in the fcd was correct ...
now think about a
user that uses only the simple frontend (small gui) ... he
would never
notice WHY his fcd in deaf on some frequencies ...
So developers : would it be possible to make a firmware
that takes the
correct filters???
Greetz
Sigi
Dg9bfc
> -----Ursprüngliche Nachricht-----
> Von: FCDevelopment@...
> [mailto:FCDevelopment@...]
Im Auftrag von Alexandru Csete
> Gesendet: Dienstag, 9. August 2011 18:11
> An: FCDevelopment@...
> Betreff: Re: [FCDevelopment] Re: New firmware (18i)
to try out...
>
>
>
> On Tue, Aug 9, 2011 at 7:55 PM, Siegfried Jackstien
> <siegfried.jackstien@...<mailto:siegfried.jackstien%40freenet.de>
> > wrote:
> > Maybe howard could give some light on it
> > 868000 = 360 bpf ... and you can change from 360
up to 970
> > (yes there is a 840 and 890 filter but not
selected)
> > 868100 = 1300 bpf ... and you can change from
1300 to 1750
> > What I do not understand is that 868100 takes
the 1300 filter and only
> 0.1
> > .megs lower on 868000 the soft takes the lowest
uhf filter (360 megs)
> ....
> > maybe there is a firmware fault?!?
>
> Actually, there are 4 filter banks for different
bands: VHF II and
> III, UHF and L-band. The band selection determines
which filters are
> available and now I remember that it is in fact the
band selection
> that goes wrong on the FCD and causes a switch to
incorrect filter.
> FIY here is the list of filters for each band:
> https://github.com/csete/qthid/blob/newctl/mainwindow.cpp#L65
>
> >> You can anyway reset that filter in your
code, based on the frequency
> >> chosen by the user.
> >> I tried that in my experimental code, and it
works.
>
> Alberto: I prefer not to do full compensation in
workarounds because
> then the real issue will never be fixed ;-)
>
> Alex
>
>
>
As far as i know not yet
Dg9bfc
Sigi
> -----Ursprüngliche Nachricht-----
> Von: FCDevelopment@...
> [mailto:FCDevelopment@...] Im Auftrag von neo
> Gesendet: Mittwoch, 30. November 2011 17:27
> An: FCDevelopment@...
> Betreff: Re: [FCDevelopment] Re: New firmware (18i) to try out...
>
>
>
> Hi,
>
> are there any news on that topic?
>
>
> Am 10.08.2011 00:05, schrieb Siegfried Jackstien:
>
>
>
> Hmmmm ok but how can we solve that ?!?
> Next firmware please :-)
> I thought that the firmware was setting the correct filter
> But I did not check the whole fcd bands ...
> I only used it on 2m and 70 cm yet
> After I have seen the other mail about 868100I checked and found the
> other
> fault (100kc lower lowest uhf filter used)
> I thought that the switching in the fcd was correct ... now think
> about a
> user that uses only the simple frontend (small gui) ... he would
> never
> notice WHY his fcd in deaf on some frequencies ...
> So developers : would it be possible to make a firmware that takes
> the
> correct filters???
> Greetz
> Sigi
> Dg9bfc
>
> > -----Ursprüngliche Nachricht-----
> > Von: FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk>
> > [mailto:FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk> ] Im Auftrag von Alexandru
> Csete
> > Gesendet: Dienstag, 9. August 2011 18:11
> > An: FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk>
> > Betreff: Re: [FCDevelopment] Re: New firmware (18i) to try out...
> >
> >
> >
> > On Tue, Aug 9, 2011 at 7:55 PM, Siegfried Jackstien
> > <siegfried.jackstien@...
> <mailto:siegfried.jackstien%40freenet.de>
> <mailto:siegfried.jackstien%40freenet.de>
> <mailto:siegfried.jackstien%40freenet.de>
> > > wrote:
> > > Maybe howard could give some light on it
> > > 868000 = 360 bpf ... and you can change from 360 up to 970
> > > (yes there is a 840 and 890 filter but not selected)
> > > 868100 = 1300 bpf ... and you can change from 1300 to 1750
> > > What I do not understand is that 868100 takes the 1300 filter
> and only
> > 0.1
> > > .megs lower on 868000 the soft takes the lowest uhf filter (360
> megs)
> > ....
> > > maybe there is a firmware fault?!?
> >
> > Actually, there are 4 filter banks for different bands: VHF II and
> > III, UHF and L-band. The band selection determines which filters
> are
> > available and now I remember that it is in fact the band selection
> > that goes wrong on the FCD and causes a switch to incorrect
> filter.
> > FIY here is the list of filters for each band:
> > https://github.com/csete/qthid/blob/newctl/mainwindow.cpp#L65
> >
> > >> You can anyway reset that filter in your code, based on the
> frequency
> > >> chosen by the user.
> > >> I tried that in my experimental code, and it works.
> >
> > Alberto: I prefer not to do full compensation in workarounds
> because
> > then the real issue will never be fixed ;-)
> >
> > Alex
> >
> >
> >
>
>
>
>
>
Folks
Release 18j available here:
http://www.funcubedongle.com/MyImages/export18j.pro.bin
This has a fix for the incorrect filter preselection between 868MHz and 1GHz.
This was also built within a completely new development environment, so please
let me know any problems!
Many thanks, Howard
Thanks howard for new firmware
Seems to work (after short test)
Uploading was a snap :-) worked without error in first try
Just a few mouse-clicks and job was done (start full hid, reset to bl-mode,
start boot-loading soft, upload new firmware, reset to app)
Start hdsdr and see the filter chage while setting new qrg
Also switching bias from v/u band to l band worked ... so seems as you made
a good work (AGAIN!)
Greetz
Dg9bfc
Sigi
> -----Ursprüngliche Nachricht-----
> Von: FCDevelopment@...
> [mailto:FCDevelopment@...] Im Auftrag von
> hlong@...
> Gesendet: Donnerstag, 1. Dezember 2011 13:38
> An: FCDevelopment@...
> Betreff: [FCDevelopment] Firmware 18j
>
>
>
> Folks
>
> Release 18j available here:
> http://www.funcubedongle.com/MyImages/export18j.pro.bin
>
> This has a fix for the incorrect filter preselection between 868MHz and
> 1GHz.
>
> This was also built within a completely new development environment, so
> please let me know any problems!
>
> Many thanks, Howard
>
>
>
>
A new version of my FCD-Scanner application can be downloaded here
http://www.sa0and.com/MyRigSoftware.html at your own risk.
The new version is developed in Visual Basic 2010 Express and is only tested
with Windows 7 64 bit OS.
The utility include now a simple squelch function.
--- In FCDevelopment@..., "Adam" <fraga@...> wrote:
>
>
>
> Ok here is an application with source code to use FCD as a scanner for the
VHF/UHF/AIR bands. Its developed in Visual basic 6 and uses FCD as receiver and
the SpectraVue software for demodulation. Any suggestions for improving it is
welcome even source code is welcome if anybody is converting it to visual basic
2010. Use the code at Your own risk.
> The application can be downloaded here
> http://www.sa0and.com/MyRigSoftware.html
> /SA0AND
>
>
> --- In FCDevelopment@..., "Adam" <fraga@> wrote:
> >
> > Is there any applications written for funcube dongle in visual basic and
there the source code is open?
> > I am lazy and does not want to invent the wheel again
> > /SA0AND
> >
>
Following
from my initial success with Gqrx, and then problems caused by
audio overrun in Ubuntu 11.10 I installed Kubuntu 11.10 in a
separate partition on my machine tonight. After the clean
install I installed Synaptic and then the dependencies listed in
the pre-compiled Gqrx binary README file. I created the udev
rule etc. and ran Gqrx. It complained about a missing portaudio
library so I installed that and it started without complaint.
When I pressed the receive button all I got was
"a0a0a0a0......." - audio overrun.
As this was a clean install I have come to the conclusion that
this is either a problem with my machine at a hardware level
(CPU is an Intel Core i5-2400) or with Ubuntu/Kubuntu 11.10
release generally. If I have the enthusiasm I'll try and install
11.04, which I know Linrad and Quick worked with.
Unless anyone has any killer cure for this problem?!
This works great for me Adam. Will be testing on Win7 32 bit and Vista this week
as time allows.
--Jeff
--- In FCDevelopment@..., "Adam" <fraga@...> wrote:
>
>
>
> A new version of my FCD-Scanner application can be downloaded here
> http://www.sa0and.com/MyRigSoftware.html at your own risk.
> The new version is developed in Visual Basic 2010 Express and is only tested
with Windows 7 64 bit OS.
> The utility include now a simple squelch function.
>
>
> --- In FCDevelopment@..., "Adam" <fraga@> wrote:
> >
> >
> >
> > Ok here is an application with source code to use FCD as a scanner for the
VHF/UHF/AIR bands. Its developed in Visual basic 6 and uses FCD as receiver and
the SpectraVue software for demodulation. Any suggestions for improving it is
welcome even source code is welcome if anybody is converting it to visual basic
2010. Use the code at Your own risk.
> > The application can be downloaded here
> > http://www.sa0and.com/MyRigSoftware.html
> > /SA0AND
> >
> >
> > --- In FCDevelopment@..., "Adam" <fraga@> wrote:
> > >
> > > Is there any applications written for funcube dongle in visual basic and
there the source code is open?
> > > I am lazy and does not want to invent the wheel again
> > > /SA0AND
> > >
> >
>
I've been having this issue persistently on an EEE-901 netbook running
Crunchbang Linux Statler distro (a derivative of Debian Squeeze).
The FCD seems to work on the netbook OK with gnuradio-companion, but I
get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
after failing with gqrx and its all good.
Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.
I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
familiar enough with the process. I've been building gqrx from git in
QT-Creator.
The netbook didn't formerly have pulseaudio installed. I satisfied the
build deps by installing it, but otherwise have done nothing special to
configure pulse on the netbook.
Can you offer any clues? If you're making changes to gqrx to mitigate
this issue, and need beta testers, I'd be happy to help.
Cheers,
Darren, G0HWW
--- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>
> Hi Alex,
>
> unfortunately it doesn't disappear after a reboot here, but the
problem
> with the FCD taking device 0 is annoying because it seems that other
> programs, like Quisk, expect the output sound device to be on hw:0. It
> seems like an entry in a file in /etc/modprobe.d can fix that but I
> haven't looked into it enough to work out how.
>
> I look forward to your new audio backend.
>
> Simon.
>
> On 17/11/11 17:24, Alexandru Csete wrote:
> >
> > Hi Simon,
> >
> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
> > times on a laptop but it always disappears after reboot. I suspect
it
> > is a hardware and/or driver issue but I don't have sufficient info
to
> > find out more about it.
> >
> > I am working on a new audio backend for gqrx which will hopefully
> > eliminate both the aO issue and the problem with changing device
names.
> >
> > Alex
> >
> >
>
You are right, it all looks like it compiled OK but i get random segfaults when qthid is opened.
I have tried to explain the issue to the developer of the software but i guess i've been just an annoyance.
(no user, no cry! :D )Â
a week ago i was told this:
Reply  Alex Csete 6 days ago
Ok, now it makes more sense: It builds fine but crashes at runtime. Note that the "frequency hopping" code was indeed causing crash on linux so I removed it again from the latest code in the git repository.
First and foremost, I would recommend you to try to build and execute the latest official release 3.1. If it builds and runs fine we would at least know that your installation is fine and it is indeed changes in the qthid code that cause crashes.
In order to get debug information in qthid you can try the following: - Ensure that the selected target id "Debug" and not release (one of the buttons in the lower left corner) - Execute qthid within the qtcreator debugger (the run button in the lower left corner with the little bug on it)
---
I've sent some debug info but got no answer yet and the git sources have not been updated yet, last one happened on: Â csete authored January 01, 2012
so I guess I will just have to wait and see if some other debian wheezy users hit the same wall.
I had compiled many times the git sources under (X)(K)Bubuntu but after their latest version I had no other option than migrating to debian. Where i have compiled many other qt applications and even got wine from git so to use spectravue to control the FCD.
I have to be quick on setting the freq before qthid segfaults, and this happens with the latest stable binary version also.
So yes, in my experience qthid compiles under ubuntu but not under debian.. for sure is something related to versions.. i will try getting the sources from Nokia.
1.1. Re: failing to compile qthid (from git sources) under debian stable
  From: g0hww
2.1. Re: Gqrx problem
  From: g0hww
Messages
________________________________________________________________________
1.1. Re: failing to compile qthid (from git sources) under debian stable
  Posted by: "g0hww" darren.long@... g0hww
  Date: Mon Jan 9, 2012 10:19 pm
Hi,
I've not actually compiled qthid on Debian Squeeze myself, but I have just compiled all of gnuradio and gqrx and that all built OK on Crunchbang Linux, which is a derivative of Debian Squeeze. To do this, I had to get the QT SDK installer direct from Nokia and installed QT 4.7 that way.
Anyway, to the point. Â Are you sure your build failed? Â In the build output in your post I see a bunch of warnings, but no errors, and the last few lines:
---
g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
show the object files being linked into the binary and make returning success. Â I'd be tempted to think that it all worked.
What makes you think otherwise?
Cheers,
Darren, G0HWW
--- In FCDevelopment@..., "le_lectro" <alejoduque@...> wrote:
>
> hi all, im looking for some guidelines and help on getting to compile qthid under debian x86_64
>
> my current libqt4 version is: 4:4.7.3-5 Â (It failed to compile with versions 4.6 under aka sid).
>
> sudo aptitude show libqt4-dev
> Package: libqt4-dev
> State: installed
> Automatically installed: no
> Version: 4:4.7.3-5
> Priority: optional
> Section: libdevel
> Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@...>
> Uncompressed Size: 19.6 M
> Depends: libqt4-dbus (= 4:4.7.3-5), libqt4-declarative (= 4:4.7.3-5), libqt4-designer (= 4:4.7.3-5), libqt4-help
> Â Â Â Â Â (= 4:4.7.3-5), libqt4-network (= 4:4.7.3-5), libqt4-qt3support (= 4:4.7.3-5), libqt4-script (=
> Â Â Â Â Â 4:4.7.3-5), libqt4-scripttools (= 4:4.7.3-5), libqt4-sql (= 4:4.7.3-5), libqt4-svg (= 4:4.7.3-5),
> Â Â Â Â Â libqt4-test (= 4:4.7.3-5), libqt4-xml (= 4:4.7.3-5), libqt4-xmlpatterns (= 4:4.7.3-5), libqtcore4 (=
> Â Â Â Â Â 4:4.7.3-5), libqtgui4 (= 4:4.7.3-5), qt4-linguist-tools (= 4:4.7.3-5), qt4-qmake (= 4:4.7.3-5), libc6
> Â Â Â Â Â (>= 2.3), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1), zlib1g (>= 1:1.1.4)
> Recommends: libqt4-opengl-dev (= 4:4.7.3-5), libqtwebkit-dev (>= 2.0~)
> Suggests: firebird2.1-dev, libmysqlclient-dev, libpq-dev, libsqlite0-dev, libsqlite3-dev, qt4-dev-tools,
> Â Â Â Â Â qt4-doc, unixodbc-dev
> Breaks: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Replaces: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Description: Qt 4 development files
> Â Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide
> Â standard GUI functionality.
>
> Â This package contains the header development files and development programs used for building Qt 4
> Â applications.
> Homepage: http://qt.nokia.com/
>
> When i try to build all, under qtcreator i get this errors:
>
> mainwindow.cpp:568: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
>
> freqctrl.cpp:639: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:337: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
>
> hid-libusb.c:720: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:1088: warning: unused parameter `dev' [-Wunused-parameter]
>
>
> here is the full log based on the most recent git sources taken from here https://github.com/csete/qthid:
>
> Running build steps for project qthid...
> Starting: /usr/bin/qmake-qt4 /home/alejo/sat-a-ware/funcube/qthid_git/qthid.pro -spec linux-g++-64 -r CONFIG+=debug
> Exited with code 0.
> Starting: /usr/bin/make -w
> make: Entering directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> /usr/bin/uic-qt4 iqbalance.ui -o ui_iqbalance.h
> /usr/bin/uic-qt4 mainwindow.ui -o ui_mainwindow.h
> /usr/bin/uic-qt4 fcddiagram.ui -o ui_fcddiagram.h
> /usr/bin/uic-qt4 firmware.ui -o ui_firmware.h
> /usr/bin/uic-qt4 dockifgain.ui -o ui_dockifgain.h
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o mainwindow.o mainwindow.cpp
> mainwindow.cpp: In member function `void MainWindow::enableControls()':
> mainwindow.cpp:611:11: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o main.o main.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcd.o fcd.c
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o freqctrl.o freqctrl.cpp
> freqctrl.cpp: In member function `void CFreqCtrl::DrawDigits(QPainter&)':
> freqctrl.cpp:639:6: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o iqbalance.o iqbalance.cc
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcddiagram.o fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o firmware.o firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o dockifgain.o dockifgain.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o hid-libusb.o hid-libusb.c
> hid-libusb.c: In function `get_usb_string':
> hid-libusb.c:337:12: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> hid-libusb.c: In function `hid_open_path':
> hid-libusb.c:720:10: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
> hid-libusb.c: In function `hid_error':
> hid-libusb.c:1088:68: warning: unused parameter `dev' [-Wunused-parameter]
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. mainwindow.h -o moc_mainwindow.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_mainwindow.o moc_mainwindow.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. freqctrl.h -o moc_freqctrl.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_freqctrl.o moc_freqctrl.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. iqbalance.h -o moc_iqbalance.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_iqbalance.o moc_iqbalance.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. fcddiagram.h -o moc_fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_fcddiagram.o moc_fcddiagram.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. firmware.h -o moc_firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_firmware.o moc_firmware.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. dockifgain.h -o moc_dockifgain.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_dockifgain.o moc_dockifgain.cpp
> /usr/bin/rcc -name qthid qthid.qrc -o qrc_qthid.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o qrc_qthid.o qrc_qthid.cpp
> g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
> make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> Exited with code 0.
>
>
> Is there anyone out there running this software under debian?
>
> TIA,
> /a
>
Messages in this topic (2)
________________________________________________________________________
________________________________________________________________________
2.1. Re: Gqrx problem
  Posted by: "g0hww" darren.long@... g0hww
  Date: Mon Jan 9, 2012 11:37 pm
I've been having this issue persistently on an EEE-901 netbook running
Crunchbang Linux Statler distro (a derivative of Debian Squeeze).
The FCD seems to work  on the netbook OK with gnuradio-companion, but I
get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
after failing with gqrx and its all good.
Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.
I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
familiar enough with  the process.  I've been building gqrx from git in
QT-Creator.
The netbook didn't formerly have pulseaudio installed. Â I satisfied the
build deps by installing it, but otherwise have done nothing special to
configure pulse on the netbook.
Can you offer any clues? Â If you're making changes to gqrx to mitigate
this issue, and need beta testers, I'd be happy to help.
Cheers,
Darren, G0HWW
--- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>
> Hi Alex,
>
> unfortunately it doesn't disappear after a reboot here, but the
problem
> with the FCD taking device 0 is annoying because it seems that other
> programs, like Quisk, expect the output sound device to be on hw:0. It
> seems like an entry in a file in /etc/modprobe.d can fix that but I
> haven't looked into it enough to work out how.
>
> I look forward to your new audio backend.
>
> Simon.
>
> On 17/11/11 17:24, Alexandru Csete wrote:
> >
> > Hi Simon,
> >
> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
> > times on a laptop but it always disappears after reboot. I suspect
it
> > is a hardware and/or driver issue but I don't have sufficient info
to
> > find out more about it.
> >
> > I am working on a new audio backend for gqrx which will hopefully
> > eliminate both the aO issue and the problem with changing device
names.
> >
> > Alex
> >
> >
>
Messages in this topic (4)
------------------------------------------------------------------------
Yahoo! Groups Links
I've just built qthid 3.1 from git source on the netbook and it seems to be working ok for me. I've just done a quick functional check using baudline to show the spectrum and it seems to have tuned to the frequency ok.
Just to confirm, this is built with Nokia's QT SDK 4.7.4 on Crunchbang Statler which is effectively Debian Squeeze. FCD FW is 18.09.
Cheers
Darren, G0HWW
On 10 Jan 2012, at 16:19, alejo d <alejoduque@...> wrote:
Hi Darren, many thanks for your reply,
You are right, it all looks like it compiled OK but i get random segfaults when qthid is opened.
I have tried to explain the issue to the developer of the software but i guess i've been just an annoyance.
(no user, no cry! :D )
a week ago i was told this:
Reply Alex Csete 6 days ago
Ok, now it makes more sense: It builds fine but crashes at runtime. Note that the "frequency hopping" code was indeed causing crash on linux so I removed it again from the latest code in the git repository.
First and foremost, I would recommend you to try to build and execute the latest official release 3.1. If it builds and runs fine we would at least know that your installation is fine and it is indeed changes in the qthid code that cause crashes.
In order to get debug information in qthid you can try the following: - Ensure that the selected target id "Debug" and not release (one of the buttons in the lower left corner) - Execute qthid within the qtcreator debugger (the run button in the lower left corner with the little bug on it)
---
I've sent some debug info but got no answer yet and the git sources have not been updated yet, last one happened on: csete authored January 01, 2012
so I guess I will just have to wait and see if some other debian wheezy users hit the same wall.
I had compiled many times the git sources under (X)(K)Bubuntu but after their latest version I had no other option than migrating to debian. Where i have compiled many other qt applications and even got wine from git so to use spectravue to control the FCD.
I have to be quick on setting the freq before qthid segfaults, and this happens with the latest stable binary version also.
So yes, in my experience qthid compiles under ubuntu but not under debian.. for sure is something related to versions.. i will try getting the sources from Nokia.
1.1. Re: failing to compile qthid (from git sources) under debian stable
From: g0hww
2.1. Re: Gqrx problem
From: g0hww
Messages
________________________________________________________________________
1.1. Re: failing to compile qthid (from git sources) under debian stable
Posted by: "g0hww" darren.long@... g0hww
Date: Mon Jan 9, 2012 10:19 pm
Hi,
I've not actually compiled qthid on Debian Squeeze myself, but I have just compiled all of gnuradio and gqrx and that all built OK on Crunchbang Linux, which is a derivative of Debian Squeeze. To do this, I had to get the QT SDK installer direct from Nokia and installed QT 4.7 that way.
Anyway, to the point. Are you sure your build failed? In the build output in your post I see a bunch of warnings, but no errors, and the last few lines:
---
g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
show the object files being linked into the binary and make returning success. I'd be tempted to think that it all worked.
What makes you think otherwise?
Cheers,
Darren, G0HWW
--- In FCDevelopment@..., "le_lectro" <alejoduque@...> wrote:
>
> hi all, im looking for some guidelines and help on getting to compile qthid under debian x86_64
>
> my current libqt4 version is: 4:4.7.3-5 (It failed to compile with versions 4.6 under aka sid).
>
> sudo aptitude show libqt4-dev
> Package: libqt4-dev
> State: installed
> Automatically installed: no
> Version: 4:4.7.3-5
> Priority: optional
> Section: libdevel
> Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@...>
> Uncompressed Size: 19.6 M
> Depends: libqt4-dbus (= 4:4.7.3-5), libqt4-declarative (= 4:4.7.3-5), libqt4-designer (= 4:4.7.3-5), libqt4-help
> (= 4:4.7.3-5), libqt4-network (= 4:4.7.3-5), libqt4-qt3support (= 4:4.7.3-5), libqt4-script (=
> 4:4.7.3-5), libqt4-scripttools (= 4:4.7.3-5), libqt4-sql (= 4:4.7.3-5), libqt4-svg (= 4:4.7.3-5),
> libqt4-test (= 4:4.7.3-5), libqt4-xml (= 4:4.7.3-5), libqt4-xmlpatterns (= 4:4.7.3-5), libqtcore4 (=
> 4:4.7.3-5), libqtgui4 (= 4:4.7.3-5), qt4-linguist-tools (= 4:4.7.3-5), qt4-qmake (= 4:4.7.3-5), libc6
> (>= 2.3), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1), zlib1g (>= 1:1.1.4)
> Recommends: libqt4-opengl-dev (= 4:4.7.3-5), libqtwebkit-dev (>= 2.0~)
> Suggests: firebird2.1-dev, libmysqlclient-dev, libpq-dev, libsqlite0-dev, libsqlite3-dev, qt4-dev-tools,
> qt4-doc, unixodbc-dev
> Breaks: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Replaces: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Description: Qt 4 development files
> Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide
> standard GUI functionality.
>
> This package contains the header development files and development programs used for building Qt 4
> applications.
> Homepage: http://qt.nokia.com/
>
> When i try to build all, under qtcreator i get this errors:
>
> mainwindow.cpp:568: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
>
> freqctrl.cpp:639: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:337: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
>
> hid-libusb.c:720: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:1088: warning: unused parameter `dev' [-Wunused-parameter]
>
>
> here is the full log based on the most recent git sources taken from here https://github.com/csete/qthid:
>
> Running build steps for project qthid...
> Starting: /usr/bin/qmake-qt4 /home/alejo/sat-a-ware/funcube/qthid_git/qthid.pro -spec linux-g++-64 -r CONFIG+=debug
> Exited with code 0.
> Starting: /usr/bin/make -w
> make: Entering directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> /usr/bin/uic-qt4 iqbalance.ui -o ui_iqbalance.h
> /usr/bin/uic-qt4 mainwindow.ui -o ui_mainwindow.h
> /usr/bin/uic-qt4 fcddiagram.ui -o ui_fcddiagram.h
> /usr/bin/uic-qt4 firmware.ui -o ui_firmware.h
> /usr/bin/uic-qt4 dockifgain.ui -o ui_dockifgain.h
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o mainwindow.o mainwindow.cpp
> mainwindow.cpp: In member function `void MainWindow::enableControls()':
> mainwindow.cpp:611:11: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o main.o main.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcd.o fcd.c
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o freqctrl.o freqctrl.cpp
> freqctrl.cpp: In member function `void CFreqCtrl::DrawDigits(QPainter&)':
> freqctrl.cpp:639:6: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o iqbalance.o iqbalance.cc
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcddiagram.o fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o firmware.o firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o dockifgain.o dockifgain.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o hid-libusb.o hid-libusb.c
> hid-libusb.c: In function `get_usb_string':
> hid-libusb.c:337:12: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> hid-libusb.c: In function `hid_open_path':
> hid-libusb.c:720:10: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
> hid-libusb.c: In function `hid_error':
> hid-libusb.c:1088:68: warning: unused parameter `dev' [-Wunused-parameter]
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. mainwindow.h -o moc_mainwindow.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_mainwindow.o moc_mainwindow.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. freqctrl.h -o moc_freqctrl.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_freqctrl.o moc_freqctrl.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. iqbalance.h -o moc_iqbalance.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_iqbalance.o moc_iqbalance.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. fcddiagram.h -o moc_fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_fcddiagram.o moc_fcddiagram.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. firmware.h -o moc_firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_firmware.o moc_firmware.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. dockifgain.h -o moc_dockifgain.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_dockifgain.o moc_dockifgain.cpp
> /usr/bin/rcc -name qthid qthid.qrc -o qrc_qthid.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o qrc_qthid.o qrc_qthid.cpp
> g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
> make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> Exited with code 0.
>
>
> Is there anyone out there running this software under debian?
>
> TIA,
> /a
>
Messages in this topic (2)
________________________________________________________________________
________________________________________________________________________
2.1. Re: Gqrx problem
Posted by: "g0hww" darren.long@... g0hww
Date: Mon Jan 9, 2012 11:37 pm
I've been having this issue persistently on an EEE-901 netbook running
Crunchbang Linux Statler distro (a derivative of Debian Squeeze).
The FCD seems to work on the netbook OK with gnuradio-companion, but I
get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
after failing with gqrx and its all good.
Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.
I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
familiar enough with the process. I've been building gqrx from git in
QT-Creator.
The netbook didn't formerly have pulseaudio installed. I satisfied the
build deps by installing it, but otherwise have done nothing special to
configure pulse on the netbook.
Can you offer any clues? If you're making changes to gqrx to mitigate
this issue, and need beta testers, I'd be happy to help.
Cheers,
Darren, G0HWW
--- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>
> Hi Alex,
>
> unfortunately it doesn't disappear after a reboot here, but the
problem
> with the FCD taking device 0 is annoying because it seems that other
> programs, like Quisk, expect the output sound device to be on hw:0. It
> seems like an entry in a file in /etc/modprobe.d can fix that but I
> haven't looked into it enough to work out how.
>
> I look forward to your new audio backend.
>
> Simon.
>
> On 17/11/11 17:24, Alexandru Csete wrote:
> >
> > Hi Simon,
> >
> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
> > times on a laptop but it always disappears after reboot. I suspect
it
> > is a hardware and/or driver issue but I don't have sufficient info
to
> > find out more about it.
> >
> > I am working on a new audio backend for gqrx which will hopefully
> > eliminate both the aO issue and the problem with changing device
names.
> >
> > Alex
> >
> >
>
Messages in this topic (4)
------------------------------------------------------------------------
Yahoo! Groups Links
On 10 Jan 2012, at 20:35, Darren Long <darren.long@...> wrote:
Hi again.
I've just built qthid 3.1 from git source on the netbook and it seems to be working ok for me. I've just done a quick functional check using baudline to show the spectrum and it seems to have tuned to the frequency ok.
Just to confirm, this is built with Nokia's QT SDK 4.7.4 on Crunchbang Statler which is effectively Debian Squeeze. FCD FW is 18.09.
Cheers
Darren, G0HWW
On 10 Jan 2012, at 16:19, alejo d <alejoduque@...> wrote:
Hi Darren, many thanks for your reply,
You are right, it all looks like it compiled OK but i get random segfaults when qthid is opened.
I have tried to explain the issue to the developer of the software but i guess i've been just an annoyance.
(no user, no cry! :D )
a week ago i was told this:
Reply Alex Csete 6 days ago
Ok, now it makes more sense: It builds fine but crashes at runtime. Note that the "frequency hopping" code was indeed causing crash on linux so I removed it again from the latest code in the git repository.
First and foremost, I would recommend you to try to build and execute the latest official release 3.1. If it builds and runs fine we would at least know that your installation is fine and it is indeed changes in the qthid code that cause crashes.
In order to get debug information in qthid you can try the following: - Ensure that the selected target id "Debug" and not release (one of the buttons in the lower left corner) - Execute qthid within the qtcreator debugger (the run button in the lower left corner with the little bug on it)
---
I've sent some debug info but got no answer yet and the git sources have not been updated yet, last one happened on: csete authored January 01, 2012
so I guess I will just have to wait and see if some other debian wheezy users hit the same wall.
I had compiled many times the git sources under (X)(K)Bubuntu but after their latest version I had no other option than migrating to debian. Where i have compiled many other qt applications and even got wine from git so to use spectravue to control the FCD.
I have to be quick on setting the freq before qthid segfaults, and this happens with the latest stable binary version also.
So yes, in my experience qthid compiles under ubuntu but not under debian.. for sure is something related to versions.. i will try getting the sources from Nokia.
1.1. Re: failing to compile qthid (from git sources) under debian stable
From: g0hww
2.1. Re: Gqrx problem
From: g0hww
Messages
________________________________________________________________________
1.1. Re: failing to compile qthid (from git sources) under debian stable
Posted by: "g0hww" darren.long@... g0hww
Date: Mon Jan 9, 2012 10:19 pm
Hi,
I've not actually compiled qthid on Debian Squeeze myself, but I have just compiled all of gnuradio and gqrx and that all built OK on Crunchbang Linux, which is a derivative of Debian Squeeze. To do this, I had to get the QT SDK installer direct from Nokia and installed QT 4.7 that way.
Anyway, to the point. Are you sure your build failed? In the build output in your post I see a bunch of warnings, but no errors, and the last few lines:
---
g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
show the object files being linked into the binary and make returning success. I'd be tempted to think that it all worked.
What makes you think otherwise?
Cheers,
Darren, G0HWW
--- In FCDevelopment@..., "le_lectro" <alejoduque@...> wrote:
>
> hi all, im looking for some guidelines and help on getting to compile qthid under debian x86_64
>
> my current libqt4 version is: 4:4.7.3-5 (It failed to compile with versions 4.6 under aka sid).
>
> sudo aptitude show libqt4-dev
> Package: libqt4-dev
> State: installed
> Automatically installed: no
> Version: 4:4.7.3-5
> Priority: optional
> Section: libdevel
> Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@...>
> Uncompressed Size: 19.6 M
> Depends: libqt4-dbus (= 4:4.7.3-5), libqt4-declarative (= 4:4.7.3-5), libqt4-designer (= 4:4.7.3-5), libqt4-help
> (= 4:4.7.3-5), libqt4-network (= 4:4.7.3-5), libqt4-qt3support (= 4:4.7.3-5), libqt4-script (=
> 4:4.7.3-5), libqt4-scripttools (= 4:4.7.3-5), libqt4-sql (= 4:4.7.3-5), libqt4-svg (= 4:4.7.3-5),
> libqt4-test (= 4:4.7.3-5), libqt4-xml (= 4:4.7.3-5), libqt4-xmlpatterns (= 4:4.7.3-5), libqtcore4 (=
> 4:4.7.3-5), libqtgui4 (= 4:4.7.3-5), qt4-linguist-tools (= 4:4.7.3-5), qt4-qmake (= 4:4.7.3-5), libc6
> (>= 2.3), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1), zlib1g (>= 1:1.1.4)
> Recommends: libqt4-opengl-dev (= 4:4.7.3-5), libqtwebkit-dev (>= 2.0~)
> Suggests: firebird2.1-dev, libmysqlclient-dev, libpq-dev, libsqlite0-dev, libsqlite3-dev, qt4-dev-tools,
> qt4-doc, unixodbc-dev
> Breaks: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Replaces: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Description: Qt 4 development files
> Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide
> standard GUI functionality.
>
> This package contains the header development files and development programs used for building Qt 4
> applications.
> Homepage: http://qt.nokia.com/
>
> When i try to build all, under qtcreator i get this errors:
>
> mainwindow.cpp:568: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
>
> freqctrl.cpp:639: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:337: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
>
> hid-libusb.c:720: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:1088: warning: unused parameter `dev' [-Wunused-parameter]
>
>
> here is the full log based on the most recent git sources taken from here https://github.com/csete/qthid:
>
> Running build steps for project qthid...
> Starting: /usr/bin/qmake-qt4 /home/alejo/sat-a-ware/funcube/qthid_git/qthid.pro -spec linux-g++-64 -r CONFIG+=debug
> Exited with code 0.
> Starting: /usr/bin/make -w
> make: Entering directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> /usr/bin/uic-qt4 iqbalance.ui -o ui_iqbalance.h
> /usr/bin/uic-qt4 mainwindow.ui -o ui_mainwindow.h
> /usr/bin/uic-qt4 fcddiagram.ui -o ui_fcddiagram.h
> /usr/bin/uic-qt4 firmware.ui -o ui_firmware.h
> /usr/bin/uic-qt4 dockifgain.ui -o ui_dockifgain.h
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o mainwindow.o mainwindow.cpp
> mainwindow.cpp: In member function `void MainWindow::enableControls()':
> mainwindow.cpp:611:11: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o main.o main.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcd.o fcd.c
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o freqctrl.o freqctrl.cpp
> freqctrl.cpp: In member function `void CFreqCtrl::DrawDigits(QPainter&)':
> freqctrl.cpp:639:6: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o iqbalance.o iqbalance.cc
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcddiagram.o fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o firmware.o firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o dockifgain.o dockifgain.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o hid-libusb.o hid-libusb.c
> hid-libusb.c: In function `get_usb_string':
> hid-libusb.c:337:12: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> hid-libusb.c: In function `hid_open_path':
> hid-libusb.c:720:10: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
> hid-libusb.c: In function `hid_error':
> hid-libusb.c:1088:68: warning: unused parameter `dev' [-Wunused-parameter]
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. mainwindow.h -o moc_mainwindow.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_mainwindow.o moc_mainwindow.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. freqctrl.h -o moc_freqctrl.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_freqctrl.o moc_freqctrl.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. iqbalance.h -o moc_iqbalance.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_iqbalance.o moc_iqbalance.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. fcddiagram.h -o moc_fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_fcddiagram.o moc_fcddiagram.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. firmware.h -o moc_firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_firmware.o moc_firmware.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. dockifgain.h -o moc_dockifgain.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_dockifgain.o moc_dockifgain.cpp
> /usr/bin/rcc -name qthid qthid.qrc -o qrc_qthid.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o qrc_qthid.o qrc_qthid.cpp
> g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
> make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> Exited with code 0.
>
>
> Is there anyone out there running this software under debian?
>
> TIA,
> /a
>
Messages in this topic (2)
________________________________________________________________________
________________________________________________________________________
2.1. Re: Gqrx problem
Posted by: "g0hww" darren.long@... g0hww
Date: Mon Jan 9, 2012 11:37 pm
I've been having this issue persistently on an EEE-901 netbook running
Crunchbang Linux Statler distro (a derivative of Debian Squeeze).
The FCD seems to work on the netbook OK with gnuradio-companion, but I
get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
after failing with gqrx and its all good.
Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.
I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
familiar enough with the process. I've been building gqrx from git in
QT-Creator.
The netbook didn't formerly have pulseaudio installed. I satisfied the
build deps by installing it, but otherwise have done nothing special to
configure pulse on the netbook.
Can you offer any clues? If you're making changes to gqrx to mitigate
this issue, and need beta testers, I'd be happy to help.
Cheers,
Darren, G0HWW
--- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>
> Hi Alex,
>
> unfortunately it doesn't disappear after a reboot here, but the
problem
> with the FCD taking device 0 is annoying because it seems that other
> programs, like Quisk, expect the output sound device to be on hw:0. It
> seems like an entry in a file in /etc/modprobe.d can fix that but I
> haven't looked into it enough to work out how.
>
> I look forward to your new audio backend.
>
> Simon.
>
> On 17/11/11 17:24, Alexandru Csete wrote:
> >
> > Hi Simon,
> >
> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
> > times on a laptop but it always disappears after reboot. I suspect
it
> > is a hardware and/or driver issue but I don't have sufficient info
to
> > find out more about it.
> >
> > I am working on a new audio backend for gqrx which will hopefully
> > eliminate both the aO issue and the problem with changing device
names.
> >
> > Alex
> >
> >
>
Messages in this topic (4)
------------------------------------------------------------------------
Yahoo! Groups Links
Now, Alejo... I've told you last time that I have rolled back some changes that were causing qthid to crash. So please, instead of speculating when the code was last updated, just go ahead and get the latest code from the repository. If you don't know how to do it with git, you can always get the latest code as a .zip or .tar.gz from github: https://github.com/csete/qthid/downloads
You'll see that it will generate a file called csete-qthid-v3.1-26-g91cb1a85.tar.gz, meaning that it is 4 commits ahead of v3.1-22-g67ddac88 which you used to generate the crash report.
Also please ensure that any binaries from the previous builds are removed, best is to remove the qthid-build-desktop directory before you load the updated qthid.pro in qtcreator.
Alex
On Tue, Jan 10, 2012 at 9:35 PM, Darren Long <darren.long@...> wrote:
Hi again.
I've just built qthid 3.1 from git source on the netbook and it seems to be working ok for me. I've just done a quick functional check using baudline to show the spectrum and it seems to have tuned to the frequency ok.
Just to confirm, this is built with Nokia's QT SDK 4.7.4 on Crunchbang Statler which is effectively Debian Squeeze. FCD FW is 18.09.
Cheers
Darren, G0HWW
On 10 Jan 2012, at 16:19, alejo d <alejoduque@...> wrote:
Hi Darren, many thanks for your reply,
You are right, it all looks like it compiled OK but i get random segfaults when qthid is opened.
I have tried to explain the issue to the developer of the software but i guess i've been just an annoyance.
(no user, no cry! :D )
a week ago i was told this:
Reply Alex Csete 6 days ago
Ok, now it makes more sense: It builds fine but crashes at runtime. Note that the "frequency hopping" code was indeed causing crash on linux so I removed it again from the latest code in the git repository.
First and foremost, I would recommend you to try to build and execute the latest official release 3.1. If it builds and runs fine we would at least know that your installation is fine and it is indeed changes in the qthid code that cause crashes.
In order to get debug information in qthid you can try the following: - Ensure that the selected target id "Debug" and not release (one of the buttons in the lower left corner) - Execute qthid within the qtcreator debugger (the run button in the lower left corner with the little bug on it)
---
I've sent some debug info but got no answer yet and the git sources have not been updated yet, last one happened on: csete authored January 01, 2012
so I guess I will just have to wait and see if some other debian wheezy users hit the same wall.
I had compiled many times the git sources under (X)(K)Bubuntu but after their latest version I had no other option than migrating to debian. Where i have compiled many other qt applications and even got wine from git so to use spectravue to control the FCD.
I have to be quick on setting the freq before qthid segfaults, and this happens with the latest stable binary version also.
So yes, in my experience qthid compiles under ubuntu but not under debian.. for sure is something related to versions.. i will try getting the sources from Nokia.
1.1. Re: failing to compile qthid (from git sources) under debian stable
From: g0hww
2.1. Re: Gqrx problem
From: g0hww
Messages
________________________________________________________________________
1.1. Re: failing to compile qthid (from git sources) under debian stable
Posted by: "g0hww" darren.long@... g0hww
Date: Mon Jan 9, 2012 10:19 pm
Hi,
I've not actually compiled qthid on Debian Squeeze myself, but I have just compiled all of gnuradio and gqrx and that all built OK on Crunchbang Linux, which is a derivative of Debian Squeeze. To do this, I had to get the QT SDK installer direct from Nokia and installed QT 4.7 that way.
Anyway, to the point. Are you sure your build failed? In the build output in your post I see a bunch of warnings, but no errors, and the last few lines:
---
g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
show the object files being linked into the binary and make returning success. I'd be tempted to think that it all worked.
What makes you think otherwise?
Cheers,
Darren, G0HWW
--- In FCDevelopment@..., "le_lectro" <alejoduque@...> wrote:
>
> hi all, im looking for some guidelines and help on getting to compile qthid under debian x86_64
>
> my current libqt4 version is: 4:4.7.3-5 (It failed to compile with versions 4.6 under aka sid).
>
> sudo aptitude show libqt4-dev
> Package: libqt4-dev
> State: installed
> Automatically installed: no
> Version: 4:4.7.3-5
> Priority: optional
> Section: libdevel
> Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@...>
> Uncompressed Size: 19.6 M
> Depends: libqt4-dbus (= 4:4.7.3-5), libqt4-declarative (= 4:4.7.3-5), libqt4-designer (= 4:4.7.3-5), libqt4-help
> (= 4:4.7.3-5), libqt4-network (= 4:4.7.3-5), libqt4-qt3support (= 4:4.7.3-5), libqt4-script (=
> 4:4.7.3-5), libqt4-scripttools (= 4:4.7.3-5), libqt4-sql (= 4:4.7.3-5), libqt4-svg (= 4:4.7.3-5),
> libqt4-test (= 4:4.7.3-5), libqt4-xml (= 4:4.7.3-5), libqt4-xmlpatterns (= 4:4.7.3-5), libqtcore4 (=
> 4:4.7.3-5), libqtgui4 (= 4:4.7.3-5), qt4-linguist-tools (= 4:4.7.3-5), qt4-qmake (= 4:4.7.3-5), libc6
> (>= 2.3), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1), zlib1g (>= 1:1.1.4)
> Recommends: libqt4-opengl-dev (= 4:4.7.3-5), libqtwebkit-dev (>= 2.0~)
> Suggests: firebird2.1-dev, libmysqlclient-dev, libpq-dev, libsqlite0-dev, libsqlite3-dev, qt4-dev-tools,
> qt4-doc, unixodbc-dev
> Breaks: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Replaces: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Description: Qt 4 development files
> Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide
> standard GUI functionality.
>
> This package contains the header development files and development programs used for building Qt 4
> applications.
> Homepage: http://qt.nokia.com/
>
> When i try to build all, under qtcreator i get this errors:
>
> mainwindow.cpp:568: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
>
> freqctrl.cpp:639: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:337: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
>
> hid-libusb.c:720: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:1088: warning: unused parameter `dev' [-Wunused-parameter]
>
>
> here is the full log based on the most recent git sources taken from here https://github.com/csete/qthid:
>
> Running build steps for project qthid...
> Starting: /usr/bin/qmake-qt4 /home/alejo/sat-a-ware/funcube/qthid_git/qthid.pro -spec linux-g++-64 -r CONFIG+=debug
> Exited with code 0.
> Starting: /usr/bin/make -w
> make: Entering directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> /usr/bin/uic-qt4 iqbalance.ui -o ui_iqbalance.h
> /usr/bin/uic-qt4 mainwindow.ui -o ui_mainwindow.h
> /usr/bin/uic-qt4 fcddiagram.ui -o ui_fcddiagram.h
> /usr/bin/uic-qt4 firmware.ui -o ui_firmware.h
> /usr/bin/uic-qt4 dockifgain.ui -o ui_dockifgain.h
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o mainwindow.o mainwindow.cpp
> mainwindow.cpp: In member function `void MainWindow::enableControls()':
> mainwindow.cpp:611:11: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o main.o main.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcd.o fcd.c
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o freqctrl.o freqctrl.cpp
> freqctrl.cpp: In member function `void CFreqCtrl::DrawDigits(QPainter&)':
> freqctrl.cpp:639:6: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o iqbalance.o iqbalance.cc
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcddiagram.o fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o firmware.o firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o dockifgain.o dockifgain.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o hid-libusb.o hid-libusb.c
> hid-libusb.c: In function `get_usb_string':
> hid-libusb.c:337:12: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> hid-libusb.c: In function `hid_open_path':
> hid-libusb.c:720:10: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
> hid-libusb.c: In function `hid_error':
> hid-libusb.c:1088:68: warning: unused parameter `dev' [-Wunused-parameter]
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. mainwindow.h -o moc_mainwindow.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_mainwindow.o moc_mainwindow.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. freqctrl.h -o moc_freqctrl.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_freqctrl.o moc_freqctrl.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. iqbalance.h -o moc_iqbalance.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_iqbalance.o moc_iqbalance.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. fcddiagram.h -o moc_fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_fcddiagram.o moc_fcddiagram.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. firmware.h -o moc_firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_firmware.o moc_firmware.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. dockifgain.h -o moc_dockifgain.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_dockifgain.o moc_dockifgain.cpp
> /usr/bin/rcc -name qthid qthid.qrc -o qrc_qthid.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o qrc_qthid.o qrc_qthid.cpp
> g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
> make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> Exited with code 0.
>
>
> Is there anyone out there running this software under debian?
>
> TIA,
> /a
>
Messages in this topic (2)
________________________________________________________________________
________________________________________________________________________
2.1. Re: Gqrx problem
Posted by: "g0hww" darren.long@... g0hww
Date: Mon Jan 9, 2012 11:37 pm
I've been having this issue persistently on an EEE-901 netbook running
Crunchbang Linux Statler distro (a derivative of Debian Squeeze).
The FCD seems to work on the netbook OK with gnuradio-companion, but I
get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
after failing with gqrx and its all good.
Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.
I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
familiar enough with the process. I've been building gqrx from git in
QT-Creator.
The netbook didn't formerly have pulseaudio installed. I satisfied the
build deps by installing it, but otherwise have done nothing special to
configure pulse on the netbook.
Can you offer any clues? If you're making changes to gqrx to mitigate
this issue, and need beta testers, I'd be happy to help.
Cheers,
Darren, G0HWW
--- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>
> Hi Alex,
>
> unfortunately it doesn't disappear after a reboot here, but the
problem
> with the FCD taking device 0 is annoying because it seems that other
> programs, like Quisk, expect the output sound device to be on hw:0. It
> seems like an entry in a file in /etc/modprobe.d can fix that but I
> haven't looked into it enough to work out how.
>
> I look forward to your new audio backend.
>
> Simon.
>
> On 17/11/11 17:24, Alexandru Csete wrote:
> >
> > Hi Simon,
> >
> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
> > times on a laptop but it always disappears after reboot. I suspect
it
> > is a hardware and/or driver issue but I don't have sufficient info
to
> > find out more about it.
> >
> > I am working on a new audio backend for gqrx which will hopefully
> > eliminate both the aO issue and the problem with changing device
names.
> >
> > Alex
> >
> >
>
Messages in this topic (4)
------------------------------------------------------------------------
Yahoo! Groups Links
Hi Darren,
It can also be an issue with the output device. Note that the recent
code autodetects the FCD and it doesn't matter what you type in the
input device field.
Try in grc the simple dial tone flow graph at 48 kHz, then if it works
use the same output device in gqrx.
Since gqrx doesn't do any interfacing to audio hardware or drivers (it
only uses gnuradio), the only thing I can do about it is to debug the
obsolete interface in gnuradio or to write my own audio backend. I
have planned to do the latter but given how much time I have left for
coding these days, I doubt it will happen anytime soon.
Alex
On Tue, Jan 10, 2012 at 12:36 AM, g0hww <darren.long@...> wrote:
> I've been having this issue persistently on an EEE-901 netbook running
> Crunchbang Linux Statler distro (a derivative of Debian Squeeze).
>
> The FCD seems to work on the netbook OK with gnuradio-companion, but I
> get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
> pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
> after failing with gqrx and its all good.
>
> Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.
>
> I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
> familiar enough with the process. I've been building gqrx from git in
> QT-Creator.
>
> The netbook didn't formerly have pulseaudio installed. I satisfied the
> build deps by installing it, but otherwise have done nothing special to
> configure pulse on the netbook.
>
> Can you offer any clues? If you're making changes to gqrx to mitigate
> this issue, and need beta testers, I'd be happy to help.
>
> Cheers,
>
> Darren, G0HWW
>
>
>
> --- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>>
>> Hi Alex,
>>
>> unfortunately it doesn't disappear after a reboot here, but the
> problem
>> with the FCD taking device 0 is annoying because it seems that other
>> programs, like Quisk, expect the output sound device to be on hw:0. It
>> seems like an entry in a file in /etc/modprobe.d can fix that but I
>> haven't looked into it enough to work out how.
>>
>> I look forward to your new audio backend.
>>
>> Simon.
>>
>> On 17/11/11 17:24, Alexandru Csete wrote:
>> >
>> > Hi Simon,
>> >
>> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
>> > times on a laptop but it always disappears after reboot. I suspect
> it
>> > is a hardware and/or driver issue but I don't have sufficient info
> to
>> > find out more about it.
>> >
>> > I am working on a new audio backend for gqrx which will hopefully
>> > eliminate both the aO issue and the problem with changing device
> names.
>> >
>> > Alex
>> >
>> >
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
Thanks for the response. Sorry to bother you with this.
I tried the dial_tone example in grc at 48kHz. I let it use the default audio device and it worked ok, as does the FM receiver example. I then explicitly set the sink to hw:0 in grc which should be the same as the default, and that worked too.
Using hw:1 as input and hw:0 as output in gqrx still results in aUaO chars and the pink waterfall as before even after a reboot.
Just for a change, I plugged my SignalinkUSB in and selected the new hw:2 device for output in gqrx, which gave the same results as before. It seemed to work ok in grc but no change from before in gqrx.
Cheers,
Darren
On 10 Jan 2012, at 22:15, Alexandru Csete <oz9aec@...> wrote:
Hi Darren,
It can also be an issue with the output device. Note that the recent
code autodetects the FCD and it doesn't matter what you type in the
input device field.
Try in grc the simple dial tone flow graph at 48 kHz, then if it works
use the same output device in gqrx.
Since gqrx doesn't do any interfacing to audio hardware or drivers (it
only uses gnuradio), the only thing I can do about it is to debug the
obsolete interface in gnuradio or to write my own audio backend. I
have planned to do the latter but given how much time I have left for
coding these days, I doubt it will happen anytime soon.
Alex
On Tue, Jan 10, 2012 at 12:36 AM, g0hww <darren.long@...> wrote:
> I've been having this issue persistently on an EEE-901 netbook running
> Crunchbang Linux Statler distro (a derivative of Debian Squeeze).
>
> The FCD seems to work on the netbook OK with gnuradio-companion, but I
> get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
> pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
> after failing with gqrx and its all good.
>
> Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.
>
> I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
> familiar enough with the process. I've been building gqrx from git in
> QT-Creator.
>
> The netbook didn't formerly have pulseaudio installed. I satisfied the
> build deps by installing it, but otherwise have done nothing special to
> configure pulse on the netbook.
>
> Can you offer any clues? If you're making changes to gqrx to mitigate
> this issue, and need beta testers, I'd be happy to help.
>
> Cheers,
>
> Darren, G0HWW
>
>
>
> --- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>>
>> Hi Alex,
>>
>> unfortunately it doesn't disappear after a reboot here, but the
> problem
>> with the FCD taking device 0 is annoying because it seems that other
>> programs, like Quisk, expect the output sound device to be on hw:0. It
>> seems like an entry in a file in /etc/modprobe.d can fix that but I
>> haven't looked into it enough to work out how.
>>
>> I look forward to your new audio backend.
>>
>> Simon.
>>
>> On 17/11/11 17:24, Alexandru Csete wrote:
>> >
>> > Hi Simon,
>> >
>> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
>> > times on a laptop but it always disappears after reboot. I suspect
> it
>> > is a hardware and/or driver issue but I don't have sufficient info
> to
>> > find out more about it.
>> >
>> > I am working on a new audio backend for gqrx which will hopefully
>> > eliminate both the aO issue and the problem with changing device
> names.
>> >
>> > Alex
>> >
>> >
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
after my initial success with the FCD and gqrx on Ubuntu 11.04 (but
now upgraded to 11.10) a few months ago I then inexplicably found
that I got the a0 overflow message constantly. After seeing these
recent messages and that Alex has updated qthid I have had another
look at it tonight.
I experienced the same overflow problem tonight in gnuradio so know
this is not a gqrx problem. After a bit of Googling I found
references that suggested the problem might lie with the USB port. I
have had the FCD plugged into the USB ports on the front of the
case, which is connected to the USB header on the motherboard.
I also have a multi-card reader for CF/MC/SD etc etc which has 3 USB
ports. I plugged the FCD into one of these ports and it works in
gnuradio :-)
Another night I'll try to compile gqrx but I think I'll go back to
first principles and install everything from scratch to make sure it
has a clean build.
Not the same problem as you have but thought I'd add my experience
and I'm very pleased that I might be able to get the FCD working on
Ubuntu again.
Regards
Simon.
On 10/01/12 23:11, Darren Long wrote:
Â
Hi Alex,
Thanks for the response. Â Sorry to bother you with
this.Â
I tried the dial_tone example in grc at 48kHz. I let it
use the default audio device and it worked ok, as does the
FM receiver example. I then explicitly set the sink to
hw:0 in grc which should be the same as the default, and
that worked too.
Using hw:1 as input and hw:0 as output in gqrx still
results in aUaO chars and the pink waterfall as before
even after a reboot.
Just for a change, I plugged my SignalinkUSB in and
selected the new hw:2 device for output in gqrx, which
gave the same results as before. It seemed to work ok in
grc but no change from before in gqrx.