Re: [Discuss-gnuradio] Mouse/keyboard events not working raspberry pi 2

[Patrick Sathyanathan]

Hi Tom,

Thanks much, that was exactly what was happening ! I tried with a sample rate 
of 250k and the window responds just fine to keyboard/mouse. That's great since 
I don't know much about keyboard/mouse event handling and was dreading having 
to debug it.

The Raspberry pi 2 has a quad core processor and as long as the flow-graph does 
not take more than ~25-28% CPU (one entire processor) with nothing else running 
the GUI window responds fine. Go above that and it stops responding.

I am new to the Pi 2 and having seen this issue reported on the Pi 2 forums 
thought it was an obscure software bug.

--Patrick

________________________________
> From: address@hidden 
> Date: Tue, 27 Oct 2015 10:23:23 -0400 
> Subject: Re: [Discuss-gnuradio] Mouse/keyboard events not working  
> raspberry pi 2 
> To: address@hidden 
> CC: address@hidden 
>  
> On Mon, Oct 26, 2015 at 6:10 PM, Patrick Sathyanathan  
> <address@hidden<mailto:address@hidden>> wrote: 
> Hi, 
>  
>  
> I managed to build gnuradio from source using pybombs on a raspberry pi  
> 2 machine running raspbian. It took many tries and the build itself  
> took a day and only worked after increasing the swapfile size to 2GB. 
>  
>  
> I am able to run osmocom_fft at 2.4Msps sample rate with an rtl-sdr  
> dongle plugged in. However, the window does not respond to keyboard or  
> mouse interactions. I unable to change the frequency in the text box.  
> Nor can I move the slider. I have verified that gnuradio-companion  
> works fine and accepts mouse/keyboard inputs. However, flowgraphs  
> generated using GRC do not accept mouse/keyboard. 
>  
>  
> Any idea what the problem could be ? If I switch to other windows when  
> osmocom_fft is running the keyboard/mouse work just fine. I am using a  
> wireless mouse and keyboard that share a single usb dongle. 
>  
>  
> Thanks for any help, 
>  
>  
> --Patrick 
>  
>  
> It's quite possible that you are just overloading the rpi2's processor.  
> What if you take the sample rate down to 250 ksps? 
>  
> Tom 
>