RE: [Discuss-gnuradio] GNU-Radio GUI applications freeze

[Paul Mathews]

It's the "scope frame decimation factor". Try -n100 to start with...
Paul Mathews


> -----Original Message-----
> From: Paul Mathews [mailto:address@hidden
> Sent: Tuesday, September 23, 2008 6:58 PM
> To: Raul Siles; address@hidden
> Subject: RE: [Discuss-gnuradio] GNU-Radio GUI applications freeze
>
>
> Use the optional parameter in usrp_oscope.py that slows down the
> data rate to where wx can handle it....your screen will then not
> freeze. I can't remember off-hand what it needs to be set to...
> Paul Mathews
>
> > -----Original Message-----
> > From: address@hidden
> > [mailto:address@hidden Behalf Of
> > Raul Siles
> > Sent: Tuesday, September 23, 2008 5:19 PM
> > To: address@hidden
> > Subject: Re: [Discuss-gnuradio] GNU-Radio GUI applications freeze
> >
> >
> > Just in case anyone is interested, I'm experiencing the same behavior
> > (GNU Radio USRP graphical tools freeze, such as usrp_oscope.py) when
> > running Fedora 9 inside VMware 6.x (it includes USB 2.0 support).
> > --
> > Raul Siles
> >
> >
> > On Sat, Sep 20, 2008 at 1:50 AM, Raul Siles
> <address@hidden> wrote:
> > > Hello again,
> > > After hearing about success cases of GNU Radio and the USRP GUI tools
> > > on Fedora 8 and 9, and after reviewing and retesting the previously
> > > described setup, I've reinstalled my whole GNU Radio environment under
> > > Fedora 9 (vs Fedora 8) using the same laptop. Fedora 9 has been fully
> > > updated today. I'm using GNU Radio 3.1.3 but I'm still suffering the
> > > same GUI-based tools freeze issue.
> > >
> > > When running "usrp_oscope.py" (or other GUI tools, like
> > > "usrp_wfm_rcv.py") I get the following warning messages:
> > >
> > > # usrp_oscope.py -f 2.412G
> > >
> > > ** (python:2988): WARNING **: IPP request failed with status 1030
> > >
> > > ** (python:2988): WARNING **: IPP request failed with status 1030
> > > uOuOuOuOuOuOuOuOuOuOuOuOuOuOuOKilled
> > > #
> > >
> > > After some searching, I didn't find how to remove and solve them,
> > > although they seem to be related with wxPython (and perhaps the issue
> > > I'm suffering). Could anyone confirm this?
> > >
> > > I've tried to run other (non GNU Radio) wxPython basic examples, such
> > > as "/usr/share/doc/wxPython-2.8.7.1/samples/wxProject/wxProject.py",
> > > and they work fine.
> > >
> > > Some details about the current setup:
> > >
> > > - wxPython versions:
> > > # rpm -aq | grep -i wx
> > > wxPython-devel-2.8.7.1-5.fc9.i386
> > > wxBase-2.8.7-2.fc9.i386
> > > wxGTK-gl-2.8.7-2.fc9.i386
> > > wxGTK-devel-2.8.7-2.fc9.i386
> > > wxPython-2.8.7.1-5.fc9.i386
> > > wxGTK-2.8.7-2.fc9.i386
> > >
> > >
> > > - CPU:
> > > # cat /proc/cpuinfo
> > > processor       : 0
> > > vendor_id       : GenuineIntel
> > > cpu family      : 15
> > > model           : 2
> > > model name      : Genuine Intel(R) CPU 2.80GHz
> > > stepping        : 9
> > > cpu MHz         : 1596.000
> > > cache size      : 512 KB
> > > fdiv_bug        : no
> > > hlt_bug         : no
> > > f00f_bug        : no
> > > coma_bug        : no
> > > fpu             : yes
> > > fpu_exception   : yes
> > > cpuid level     : 2
> > > wp              : yes
> > > flags           : fpu vme de pse tsc msr pae mce cx8 mtrr pge
> > mca cmov pat
> > > pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts cid
> > > xtpr
> > > bogomips        : 3196.88
> > > clflush size    : 64
> > > power management:
> > >
> > >
> > > - Graphical card and USB bus/ports: (I'm using the USB 2.0 bus/port)
> > > # lspci
> > > 00:00.0 Host bridge: ATI Technologies Inc RS200/RS200M AGP Bridge [IGP
> > > 340M] (rev 02)
> > > 00:01.0 PCI bridge: ATI Technologies Inc PCI Bridge [IGP 340M]
> > > 00:0b.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> > > Controller (rev 50)
> > > 00:0b.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> > > Controller (rev 50)
> > > 00:0b.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
> > > 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP
> > > 330M/340M/350M
> > >
> > > - Kernel version:
> > > # uname -a
> > > Linux aereo 2.6.26.3-29.fc9.i686 #1 SMP Wed Sep 3 03:42:27 EDT 2008
> > > i686 i686 i386 GNU/Linux
> > >
> > >
> > > Any suggestion about how to troubleshoot this GUI issue? I'm starting
> > > to think it is related to the hardware I'm using.
> > > Thanks for your help!
> > > --
> > > Raul Siles
> > >
> > >
> > > On Tue, Sep 9, 2008 at 2:02 AM, Robert McGwier
> > <address@hidden> wrote:
> > >> As Matt is so fond of pointing,  I LOVE to install new toys.
> > >>
> > >> I have F 8,9, Ubuntu 8.04 with F8 and F9 on x86, x86_64, PPC, and
> > >> Cell.  I have Ubuntu 8.04 on x86, x86_64.
> > >>
> > >> They all do gnuradio.
> > >>
> > >> Bob
> > >>
> > >>
> > >> On Mon, Sep 8, 2008 at 7:56 PM, Eric Blossom <address@hidden> wrote:
> > >>
> > >>> Fedora 7, 8, and 9 are known to work fine.  I us them.
> > >>>
> > >>> Eric
> > >>>
> > >>
> > >
> >
> >
> > _______________________________________________
> > Discuss-gnuradio mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio