Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.raspberry-pi > #9120 > unrolled thread
| Started by | Maurice SAAB <morisaab@yahoo.fr> |
|---|---|
| First post | 2015-07-15 08:12 +0300 |
| Last post | 2015-07-22 19:10 +0200 |
| Articles | 12 — 9 participants |
Back to article view | Back to comp.sys.raspberry-pi
how to use laptop keyboard, mouse and screen? Maurice SAAB <morisaab@yahoo.fr> - 2015-07-15 08:12 +0300
Re: how to use laptop keyboard, mouse and screen? Dom <domafp@blueyonder.co.uk> - 2015-07-15 06:36 +0100
Re: how to use laptop keyboard, mouse and screen? Dave Farrance <DaveFarrance@OMiTTHiSyahooANDTHiS.co.uk> - 2015-07-15 13:01 +0100
Re: how to use laptop keyboard, mouse and screen? Another Dave <dmarsden@nospam.com> - 2015-07-15 15:28 +0100
Re: how to use laptop keyboard, mouse and screen? David <wibble@btintenet.com> - 2015-07-19 17:55 +0000
Re: how to use laptop keyboard, mouse and screen? Another Dave <dmarsden@nospam.com> - 2015-07-19 19:36 +0100
Re: how to use laptop keyboard, mouse and screen? Rob Morley <nospam@ntlworld.com> - 2015-07-19 20:37 +0100
Re: how to use laptop keyboard, mouse and screen? Coos Haak <chforth@hccnet.nl> - 2015-07-19 22:02 +0200
Re: how to use laptop keyboard, mouse and screen? Coos Haak <chforth@hccnet.nl> - 2015-07-20 14:26 +0200
Re: how to use laptop keyboard, mouse and screen? Coos Haak <chforth@hccnet.nl> - 2015-07-22 12:41 +0200
Re: how to use laptop keyboard, mouse and screen? stephen@mpeforth.com (Stephen Pelc) - 2015-07-20 12:45 +0000
Re: how to use laptop keyboard, mouse and screen? pippo2@disney.com (Jack) - 2015-07-22 19:10 +0200
| From | Maurice SAAB <morisaab@yahoo.fr> |
|---|---|
| Date | 2015-07-15 08:12 +0300 |
| Subject | how to use laptop keyboard, mouse and screen? |
| Message-ID | <mo4q3j$uv4$1@speranza.aioe.org> |
Hello: how to configure RPi to use laptop keyboard, mouse and screen instead of separate ones? thank you
[toc] | [next] | [standalone]
| From | Dom <domafp@blueyonder.co.uk> |
|---|---|
| Date | 2015-07-15 06:36 +0100 |
| Message-ID | <kjmpx.71447$KG6.66098@fx04.am4> |
| In reply to | #9120 |
On 15/07/15 06:12, Maurice SAAB wrote: > Hello: > how to configure RPi to use laptop keyboard, mouse and screen instead of > separate ones? > > thank you Use SSH to connect to the Pi over the network from the Laptop. If the laptop is running Linux you can use ssh -Y to enable X forwarding and then start whichever apps you want. I believe "lxsession" starts a desktop, but I don't run a GUI on any of my Pi. There are Windows clients which support X, like xming. Otherwise you could use a VNC or RDP server on the Pi and suitable client on the laptop.
[toc] | [prev] | [next] | [standalone]
| From | Dave Farrance <DaveFarrance@OMiTTHiSyahooANDTHiS.co.uk> |
|---|---|
| Date | 2015-07-15 13:01 +0100 |
| Message-ID | <fkhcqaldqh6ccoj4bn9vb5l888oon69lvp@4ax.com> |
| In reply to | #9120 |
Maurice SAAB <morisaab@yahoo.fr> wrote: >how to configure RPi to use laptop keyboard, mouse and screen instead of >separate ones? I see that you're using Windows 7. I've not used Windows in years but I can suggest some Google search terms. Raspbian (the preferred Pi OS) has an SSH server so that's the first thing to try. Google something like "ssh tutorial for windows" and looks for suggestions of well-regarded but free SSH clients for Windows. For connecting to the Pi, Google for something like "Raspberry Pi SSH tutorial". Note that this will only give you a text terminal. Setting up a remote graphics desktop is also possible, but you only want to do that if you're really familiar with Linux. If it *is* the desktop that you want, then I suggest that getting a monitor, keyboard and mouse for the Pi would be far less trouble. Keyboards and mice are cheap, and you can usually find a non-widescreen monitor with a DVI interface very cheaply if you search a few second-hand shops, for which you buy a DVI to HDMI adaptor cable.
[toc] | [prev] | [next] | [standalone]
| From | Another Dave <dmarsden@nospam.com> |
|---|---|
| Date | 2015-07-15 15:28 +0100 |
| Message-ID | <mo5qj4$p4o$1@dont-email.me> |
| In reply to | #9120 |
On 15/07/2015 06:12, Maurice SAAB wrote: > Hello: > how to configure RPi to use laptop keyboard, mouse and screen instead of > separate ones? > > thank you Connect your Pi to your router with the RJ45 socket (preferably not wireless at this stage). Download Putty SSH client to your Windows machine. http://www.putty.org Raspbian has an SSH server enabled by default. You need the IP address of you Pi which you can get by a. connecting a TV to the Pi and watching what IP it says when it boots Or, better, b. bring up the web page of your modem router in your browser. I don't know what router you have but you can Google the IP address of the router. Try 192.168.1.254 for starters. You should then be able to find the IP of your Pi without the need to connect a TV. Type the IP of your Pi into Putty and it should give you a User/Password prompt. Once (if?) you've connected you can download a VNC server to the Pi by typing sudo apt-get install tightvncserver run it by typing vncserver :1 -geometry 1280x800 -depth 16 -pixelformat rgb565 On Windows download UltraVNC http://www.uvnc.com/ Run it and type PiIPaddress:1 into the box. PiIPaddress is the address of the Pi you got from the router previously. You should, after a short (10 secs) pause get the GUI on your windows machine' Bonne chance Another Dave -- Change nospam to gmx
[toc] | [prev] | [next] | [standalone]
| From | David <wibble@btintenet.com> |
|---|---|
| Date | 2015-07-19 17:55 +0000 |
| Message-ID | <d126k2Fone1U2@mid.individual.net> |
| In reply to | #9124 |
On Wed, 15 Jul 2015 15:28:10 +0100, Another Dave wrote: > On 15/07/2015 06:12, Maurice SAAB wrote: >> Hello: >> how to configure RPi to use laptop keyboard, mouse and screen instead >> of separate ones? >> >> thank you > Connect your Pi to your router with the RJ45 socket (preferably not > wireless at this stage). > > Download Putty SSH client to your Windows machine. > > http://www.putty.org > > Raspbian has an SSH server enabled by default. You need the IP address > of you Pi which you can get by > > a. connecting a TV to the Pi and watching what IP it says when it boots > > Or, better, > > b. bring up the web page of your modem router in your browser. I don't > know what router you have but you can Google the IP address of the > router. Try 192.168.1.254 for starters. You should then be able to find > the IP of your Pi without the need to connect a TV. > > Type the IP of your Pi into Putty and it should give you a User/Password > prompt. > > Once (if?) you've connected you can download a VNC server to the Pi by > typing > > sudo apt-get install tightvncserver > > run it by typing > > vncserver :1 -geometry 1280x800 -depth 16 -pixelformat rgb565 > > On Windows download UltraVNC > > http://www.uvnc.com/ > > Run it and type PiIPaddress:1 > > into the box. PiIPaddress is the address of the Pi you got from the > router previously. You should, after a short (10 secs) pause get the GUI > on your windows machine' I installed TightVNC on my Pi and although I could connect to it from a Windows PC also running TightVNC I found I couldn't close down the Pi and a forced close down or power off corrupted the SD card. All a bit of a pain, because TightVNC works well between Windows PCs and seemed an ideal solution. Cheers Dave R -- Windows 8.1 on PCSpecialist box
[toc] | [prev] | [next] | [standalone]
| From | Another Dave <dmarsden@nospam.com> |
|---|---|
| Date | 2015-07-19 19:36 +0100 |
| Message-ID | <mogql1$snc$1@dont-email.me> |
| In reply to | #9129 |
On 19/07/2015 18:55, David wrote: > I installed TightVNC on my Pi and although I could connect to it from a > Windows PC also running TightVNC I found I couldn't close down the Pi and > a forced close down or power off corrupted the SD card. > > All a bit of a pain, because TightVNC works well between Windows PCs and > seemed an ideal solution. > I usually have both VNC and Putty working at the same time. I use sudo halt (either in Putty or a terminal in the GUI) to close down. Another Dave -- Change nospam to gmx
[toc] | [prev] | [next] | [standalone]
| From | Rob Morley <nospam@ntlworld.com> |
|---|---|
| Date | 2015-07-19 20:37 +0100 |
| Message-ID | <20150719203740.29fa26d4@ntlworld.com> |
| In reply to | #9129 |
On 19 Jul 2015 17:55:15 GMT David <wibble@btintenet.com> wrote: > I installed TightVNC on my Pi and although I could connect to it from > a Windows PC also running TightVNC I found I couldn't close down the > Pi and a forced close down or power off corrupted the SD card. > Could you not shutdown -h now ?
[toc] | [prev] | [next] | [standalone]
| From | Coos Haak <chforth@hccnet.nl> |
|---|---|
| Date | 2015-07-19 22:02 +0200 |
| Message-ID | <1ijkrk3tj22lh$.99hib9sydcy9$.dlg@40tude.net> |
| In reply to | #9132 |
Op Sun, 19 Jul 2015 20:37:40 +0100 schreef Rob Morley: > On 19 Jul 2015 17:55:15 GMT > David <wibble@btintenet.com> wrote: > >> I installed TightVNC on my Pi and although I could connect to it from >> a Windows PC also running TightVNC I found I couldn't close down the >> Pi and a forced close down or power off corrupted the SD card. >> > Could you not > shutdown -h now > ? From a terminal window within TightVNC, yes. Of course, a terminal with putty (windows) or ssh (e.g. cygwin) simply does the job too. groet Coos
[toc] | [prev] | [next] | [standalone]
| From | Coos Haak <chforth@hccnet.nl> |
|---|---|
| Date | 2015-07-20 14:26 +0200 |
| Message-ID | <egctygyep1x2$.1vri67vobpwq4.dlg@40tude.net> |
| In reply to | #9133 |
Op 20 Jul 2015 10:42:55 GMT schreef David: > On Sun, 19 Jul 2015 22:02:02 +0200, Coos Haak wrote: > >> Op Sun, 19 Jul 2015 20:37:40 +0100 schreef Rob Morley: >> >>> On 19 Jul 2015 17:55:15 GMT David <wibble@btintenet.com> wrote: >>> >>>> I installed TightVNC on my Pi and although I could connect to it from >>>> a Windows PC also running TightVNC I found I couldn't close down the >>>> Pi and a forced close down or power off corrupted the SD card. >>>> >>> Could you not shutdown -h now ? >> >> From a terminal window within TightVNC, yes. >> Of course, a terminal with putty (windows) or ssh (e.g. cygwin) >> simply does the job too. >> >> groet Coos > > Unfortunately it is the shutdown command which doesn't seem to complete > when issued from a TightVNC window. > > A while since I tried this so I don't know if it was a passing problem. > > I will try using putty as well when my tuit is sufficiently round. > > Cheers > > Dave R With 2015-05-05-raspbian-wheezy I installed TightNVC by using http://www.neil-black.co.uk/the-updated-raspberry-pi-beginners-guide. But I found it disturbing that I was root when logging in with TightVNC. I reverted to 2015-02-16-raspbian-wheezy using the install for TightVNC as described by http://www.neil-black.co.uk/raspberry-pi-beginners-guide Now I was a normal user in TightVNC. I don't know if this helps to solve your problem. groet Coos
[toc] | [prev] | [next] | [standalone]
| From | Coos Haak <chforth@hccnet.nl> |
|---|---|
| Date | 2015-07-22 12:41 +0200 |
| Message-ID | <1g5erecbsm80n$.td9a5dini8eg$.dlg@40tude.net> |
| In reply to | #9138 |
Op Tue, 21 Jul 2015 20:16:27 +0000 (UTC) schreef Martin Gregorie: > On Tue, 21 Jul 2015 13:33:17 +0200, Coos Haak wrote: > >> Next to VNC I can open a ssh console with putty *) or cygwin, but what >> how can I monitor a file that does not exist? >> What is AS corruption? Nothing to do with assembler I presume? >> > A fit of double typos here: > > AS corruption was meant to be SD corruption. Since this thread mentioned > (always?) corrupting the SD card when attempting to issue a 'shutdown -h' > [1] command from VNC I wondered if that was why you couldn't see the log > file. > > My other typo was to misname it: I meant /var/log/messages. I just fired > up mine to check: using the default logging parameters it is writing the > messages logfile as I'd expected, so the command > > sudo less /var/log/messages > > should show the last shut down followed by the current boot up sequence > if you run it after a restart. My log shows: > > Jul 17 20:05:22 rpi shutdown[2362]: shutting down for system halt > > after I ran 'sudo halt' last time. Alternatively, if you ran: > > sudo tail -f /var/log/messages > > from a second VNC or SSH console window and then shut the RPi down, you > should see everything that got logged between issuing the shutdown > command and the point when the kernel stops tail or the network > connection (whichever is stopped first - probably tail. > >> *) As I have Vista, there were problems with Putty 064. >> 065 pre-release works. >> > Not a problem here: I just ssh into my RPi from this laptop, which is > running the Fedora 22 release of Red Hat Linux. I haven't used Windows > seriously since 2004. > > [1] If the poster who complained about 'shutdown -h' not working under VNC > really ran just 'shutdown -h' instead of 'shutdown -h now' then I'm not > surprised his RPi didn't halt, because 'shutdown -h' just slaps your > wrist and tells you to use valid parameters. > > This may be a RaspberryPi special because Fedora 22 still uses the > traditional shut down procedure: 'shutdown -h' is equivalent to > 'shutdown -h 1', IOW it broadcasts a message about imminent shutdown and > waits 1 minute before shutting down. This allows for finger trouble > because the command 'shutdown -c' can be used to cancel the pending > shutdown. It seems that you have mistaken me for somebody else. I never have had any problem shutting down my rPi from VNC. groet Coos
[toc] | [prev] | [next] | [standalone]
| From | stephen@mpeforth.com (Stephen Pelc) |
|---|---|
| Date | 2015-07-20 12:45 +0000 |
| Message-ID | <55acebf3.269151176@news.eternal-september.org> |
| In reply to | #9133 |
On 20 Jul 2015 10:42:55 GMT, David <wibble@btintenet.com> wrote: >Unfortunately it is the shutdown command which doesn't seem to complete >when issued from a TightVNC window. I regularly shut down and reboot a Pi from a terminal in a Windows TightVNC Pi terminal. Nearly all the problems I have had with Pi's have been to do with cheap power supplies and cheap SD cards. Some clients have reported that the Linux insistence on writing log files to the SD card causes problems, especially on the older units with full-size SD slots. Since the clients moved to a custom Linux running in RAM, their reliability issues have gone away. Stephen -- Stephen Pelc, stephenXXX@mpeforth.com MicroProcessor Engineering Ltd - More Real, Less Time 133 Hill Lane, Southampton SO15 5AF, England tel: +44 (0)23 8063 1441, fax: +44 (0)23 8033 9691 web: http://www.mpeforth.com - free VFX Forth downloads
[toc] | [prev] | [next] | [standalone]
| From | pippo2@disney.com (Jack) |
|---|---|
| Date | 2015-07-22 19:10 +0200 |
| Message-ID | <1m7z6fu.33441k15pnt90N%pippo2@disney.com> |
| In reply to | #9139 |
The Natural Philosopher <tnp@invalid.invalid> wrote: > But perhaps the easiest thing is to mount a bit of spinning rust or > something less fragile on /var, or /var/log > just put /var/log in RAM: http://www.zdnet.com/article/raspberry-pi-extending-the-life-of-the-sd-card/ https://www.debian-administration.org/article/661/A_transient_/var/log you use a little of ram, the logs will be deleted if you turn off the rpi, but the sd cards will not wears out prematurely. Bye Jack -- Yoda of Borg am I! Assimilated shall you be! Futile resistance is, hmm?
[toc] | [prev] | [standalone]
Back to top | Article view | comp.sys.raspberry-pi
csiph-web