Hi,

I decided to take a look around after managing to run the demo nitpicker via "make run/demo" and so now I did a cd into the "GENODE_DIR\repos\ports\run" folder and found some ".run" scripts inside. I changed them to 777 permission as I noticed the permissions do not allow execute somehow and did a "./virtualbox.run" to test out the script. It threw me a

line 7: core: command not found
line 8: drivers/framebuffer: No such file or directory
line 9: drivers/timer: No such fole or directory
line 10: syntax error near unexpected token '}'
line 10: '}'

Am I running it to correct manner ?

On 7 Sep 2015 1:43 pm, "Thotheolh Tay" <twzgerald@...9...> wrote:

Hi Norman,

I have successfully managed to launch the NOVA in demo with your suggestions.

What other run options do I have besides demo ?

On 4 Sep 2015 10:41 pm, "Thotheolh Tay" <twzgerald@...188......> wrote:
Hi,

I have not tried the workaround yet.

My environment is a LinuxMint 17.2 64 bit in VirtualBox with Qemu which is the same as yours.


On Fri, Sep 4, 2015 at 9:26 PM, Norman Feske <norman.feske@...1...> wrote:
Hi Thotheolh,

On 04.09.2015 15:08, Thotheolh Tay wrote:
> Do you need me to open a bug on the Github for this ?

just out of curiosity, did my workaround work for you?

I investigated the symptom a bit further by instrumenting Qemu
(hw/input/ps2.c). The function 'ps2_mouse_event' is called with bogus
arguments for dx and dy. It receives relative motion values in the order
of thousands. Normally one would expect single-digit numbers. Qemu now
tries to convert those values into a sequence of PS/2 packets. Because
the values are so extreme, a flood of PS/2 packets is generated, which
eventually triggers the overrun of an internal queue in our PS/2 driver.
This would never occur at a normal rate of events. The problem stems
from the fact that Qemu receives bogus motion events unless SDL's
DGAMOUSE parameter is set to 0. I am afraid that we won't be able to
solve or work around it within Genode. The problem lies somewhere in
libSDL or Qemu. Hence, opening an issue at our issue tracker seems futile.

I guess that the problem only occurs when executing Qemu within a guest
OS. E.g., I am running Qemu on Linux inside VirtualBox. Is this similar
to your setup?

Cheers
Norman

--
Dr.-Ing. Norman Feske
Genode Labs

http://www.genode-labs.com · http://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

------------------------------------------------------------------------------
_______________________________________________
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main



--
,----------------------------------------------------------,
  PGP Secure Email Key ID:6FBFC19D
      7721 3E54 FA6D B79D AFE6
      AC45 8885 F995 6FBF C19D
'----------------------------------------------------------'