| 1 |
Well, after some additional crappy support from Netraverse, I decided to |
| 2 |
dig deeper into the whole mouse synchronization problem. At first, all |
| 3 |
the information I found about it indicated the problem to be with the |
| 4 |
emulated video driver (from what I understood, anyway) and that the |
| 5 |
solution would be found there and required fixing the video driver. I |
| 6 |
decided to email the folks at RealVNC to see if maybe there was just |
| 7 |
something going on with the VNC server/client--since QEMU/Bochs work |
| 8 |
fine from the console, it made sense that there may be something missing |
| 9 |
or wrong with the VNC software (I happen to use the free RealVNC). They |
| 10 |
responded... |
| 11 |
|
| 12 |
They suggested that RealVNC Personal or Enterprise would correct the |
| 13 |
problem, so I grabbed the free trials of Enterprise. It actually |
| 14 |
resolved the issue--there's a feature called Relative Pointer Motion |
| 15 |
that, when enabled, syncs the local cursor perfectly to the cursor in |
| 16 |
QEMU and Bochs. |
| 17 |
|
| 18 |
I thought this one might be useful to others having the same problem. |
| 19 |
|
| 20 |
~ Tom |
| 21 |
|
| 22 |
Tom Smith wrote: |
| 23 |
|
| 24 |
>Man, I tell you what... |
| 25 |
> |
| 26 |
>Bochs built correctly and the RFB stuff worked... Sort of. There seems |
| 27 |
>to be an issue with both QEMU and Bochs when used via VNC. Both of them |
| 28 |
>were fairly easy to setup and get running and they work fine when I'm |
| 29 |
>sitting at the console. The problem is when I try to use them over a VNC |
| 30 |
>session on a virtual console (using vncserver). From what I can find, |
| 31 |
>there's an issue with mouse synchronization--an issue that pretty much |
| 32 |
>excludes these great products from being used in a Terminal Server-like |
| 33 |
>environment. |
| 34 |
> |
| 35 |
>Neil Bothwick wrote: |
| 36 |
> |
| 37 |
> |
| 38 |
> |
| 39 |
>>On Wed, 18 Jan 2006 14:52:26 -0700, Tom Smith wrote: |
| 40 |
>> |
| 41 |
>> |
| 42 |
>> |
| 43 |
>> |
| 44 |
>> |
| 45 |
>>>Well, I tried that and get the same error--">>PANIC<< bochsrc.txt: |
| 46 |
>>>display library 'rfb' not available". |
| 47 |
>>> |
| 48 |
>>> |
| 49 |
>>> |
| 50 |
>>> |
| 51 |
>>OK, so this isn't one of "most ebuilds" |
| 52 |
>> |
| 53 |
>> |
| 54 |
>> |
| 55 |
>> |
| 56 |
>> |
| 57 |
>>>So I tried to edit the ebuild file and add "--with-rfb" and get the |
| 58 |
>>>emerge error: |
| 59 |
>>> |
| 60 |
>>>"!!! Digest verification Failed: |
| 61 |
>>>!!! /usr/portage/app-emulation/bochs/bochs-2.2.1-r1.ebuild |
| 62 |
>>>!!! Reason: Filesize does not match recorded size" |
| 63 |
>>> |
| 64 |
>>>Is there a way I can override this behavior? (The file size obviously |
| 65 |
>>>doesn't match because I added an additional ./configure option to it. |
| 66 |
>>> |
| 67 |
>>> |
| 68 |
>>> |
| 69 |
>>> |
| 70 |
>>Add --digest to the emerge command. |
| 71 |
>> |
| 72 |
>> |
| 73 |
>> |
| 74 |
>> |
| 75 |
>> |
| 76 |
>>>>EXTRA_ECONF="--foo" emerge bar - works with most ebuilds. |
| 77 |
>>>> |
| 78 |
>>>> |
| 79 |
>>>> |
| 80 |
>>>> |
| 81 |
>> |
| 82 |
>> |
| 83 |
>> |
| 84 |
>> |
| 85 |
-- |
| 86 |
gentoo-user@g.o mailing list |
Archives