OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: dino on August 11, 2004, 06:29:33 pm
-
There is no fbvnc in the 3.3.5 feeds. I found one in the 3.2 feed. Will this one work? I also came across OZ fbvnc password fix (http://www.killefiz.de/zaurus/showdetail.php?app=1863) . Is this still necessary?
What software would I run on a Win2K box?
Thanks,
-
Yes this should work on OZ3.3.5.
Do you want a VNC server on your Z or just a client (if the later then use keypebble).
For Windows (client or server) grab the VNC software from here: http://www.realvnc.com/ (http://www.realvnc.com/)
I've no idea about the password fix, sorry.
Si
-
Is there a vnc server package, both server and client, that will work with the Hentges ROM? If so which one and where is it please?
Are there kernel dependencies?
Thanks,
Dan
-
It works! With keyboard and mouse support. But it did not work for me without a few modifications.
1) I downloaded fbvncserver_0.9-4_arm.ipk from the openzaurus 3.2 stable feed
2) I created a script in /etc/init.d called fbvncinput.sh
#!/bin/sh
/etc/init.d/fbvncinput start
3) I created a symlink from the script /etc/init.d/fbvncinput.sh to the directory /etc/rc2.d and named it S25fbvncinput.sh.
From what I have read, a program called tssimd must run before the gui. It sits between the screen input from the gui and kernel. The install did not allow fbvncinput (which launches tssimd) to run before Opie.
-
Progress. Thank you.
The display comes up; but the keyboard and mouse don't work from the
What have you found out about tssimd?
-
Could someone please provide the command to create the link I mentioned earlier? I cheated and used Midnight Commander
You probable do not have fbvncinput (tssimd) running.
From a shell type the command "ps" and see if the line "/usr/sbin/tssimd " shows up.
If not run "/etc/init.d/fbvncinput start". This should start tssimd along with the keyboard input program (I forget the name.)
Check again ("ps") to see if "/usr/sbin/tssimd" shows up.
Tap with the stylus on the top-left corner of the screen and then the bottom-right corner. This calibrates tssimd.
Try connecting with "VNC server w/ split panel" again. The keyboard should work and you should be able to click the mouse on buttons.
At this point clicking the mouse on the virtual screen of the Zaurus probably will not work. It actually froze my VNC connection up. NOTE: Windows would not launch another vnc conncection until I halted the vnc server on the zaurus.
The solution to the problem is to get "/etc/init.d/fbvncinput start" which runs tssimd to run BEFORE opie starts. This can be accomplished by following my previous instructions.
Note:
One of the biggest problems I've read about was not calibrating the fbvncinput. fbvncinput (tssimd) creates the calibration file "/etc/tssim_cal.conf" . The first time you run tssimd it looks for the first two taps on the screen which should be the top-left corner of the screen and then the bottom-right . You can delete "/etc/tssim_cal.conf" and run "/etc/init.d/fbvncinput start" to recalibrate. Once you have "/etc/init.d/fbvncinput start"
Sorry for the lengthy post, but it took me some pain to discover all this.
-
Creating a symlink:
ln -s from_here to_here
so in this case:
3) I created a symlink from the script /etc/init.d/fbvncinput.sh to the directory /etc/rc2.d and named it S25fbvncinput.sh.
ln -s /etc/init.d/fbvncinput.sh /etc/rc2.d/S25fbvncinput.sh
Si
-
if you want the fbvncserver to work with the keyboard I've compiled the kbdsim.o module for the 2.4.18 kernel in OZ 3.3.5,
i have put it on my site.
http://www.darkspace.org.uk/mirrors/ (http://www.darkspace.org.uk/mirrors/)
if you have got it loading fbvncinput on boot and have the mouse working, just plop this module in /usr/share/fbvncserver/
this was compiled for the sl5500 but 'should' work in the sl5600 too, as long as both are using the 2.4.18-rmk7-pxa3-embedix kernel.
:-)
Ian
-
oh, once you have copied the module you will have to reboot, this module has to be insmodded before opie starts
-
One step forward, one step back.
Here is the error message from vncviewer:
[dan@600e aa_sox]$ vncviewer 10.0.0.64
VNC viewer for X version 4.0b4 - built Sep 19 2003 09:18:55
Copyright © 2002-2003 RealVNC Ltd.
See http://www.realvnc.com (http://www.realvnc.com) for information on VNC.
Fri Aug 13 18:11:49 2004
main: unable to connect to host: Connection refused (111)
Here is the ps -A showing the process order
/sbin/cardmgr
437 root 1412 S /usr/sbin/sshd
514 root 360 S /usr/sbin/tssimd
536 root 484 S /usr/sbin/inetd
540 root 580 S /bin/sh /etc/rc2.d/S98opie start
588 root 2160 S /opt/QtPalmtop/bin/opie-login
589 root 664 S logger
590 root 552 S -sh /opt/QtPalmtop/share/opie-login/opie-session
637 root 7768 S /opt/QtPalmtop/bin/qpe
638 root 928 S /usr/bin/ssh-agent /opt/QtPalmtop/bin/qpe
652 root 4060 S N quicklauncher
711 root 580 S udhcpc -b -p /var/run/udhcpc.wlan0.pid -i wlan0 -H op
716 root 1652 S sshd: root@pts/0
718 root 764 S -sh
729 root 676 R ps -A
#
Here is
-
upon re-reading:
The script did not start fbvncserver; it only started tssimd. Now it mostly works; the pointer is a bit off and the shift keys or the num keys don't work.
A question for lardman:
Isn' t the syntax for ln -s to-link from-link ??
Dan
-
if your mouse is a little off do this,
1. delete /etc/tssim_cal.conf
2. reboot your Z
3. when opie or opie_login starts, dont touch anything on screen
4. use the stylus to touch once in the top left and the once in the bottom right
5. login as normal and start the vnc server from one of the icons :-)
the syntax for ln to create a symbolic link is :-
ln -s <source> <new-link>
enjoy :-)
-
It all works except for keyboard errors. Letters work; however numbers display the letter below them.
I have tried to reconfigure the keyz but that has not effect. ??
Dan