I am trying to SSH into my raspberry pi from my windows machine, and the terminal environment WAS working fine, but the GUI is acting really crappy. There is no Xming window that opens up when Xming starts (but it is running according to the task manager). The taskbar in Raspbian doesn't move around (and covers up the windows taskbar), and there is a bunch of little glitches with the desktop. My motors are also being weird: when I turn on my Pi one of them starts moving. The same thing happens when I turn off my Pi (but not the H-Bridge Board). Everything (including the motors) work perfectly fine when I use my Pi with a TV via HDMI. I have the model 2 Raspberry Pi running Raspbian, Windows 10 on my computer, and am using Putty. I'm pretty new to this, so I will appreciate any help.
Do you need the GUI? If not, I would suggest turning off X11 forwarding in putty (Connection - SSH - X11) and just using the console.
Related
I have a small project using a Raspberry Pi Zero W. This is just a small Node.js server that I would like to be running at all times. I am using Raspberry Pi OS Lite (no desktop)
The whole thing works perfectly fine but after some time, let's say one night of no use, it stops working, until the Pi is rebooted.
I am thinking if there is any sleep mode that I am not aware of and, if that is the case, how to disable it. If not the case, I would like to hear about other possible root causes.
On the RPi Zero-W, go to Raspi Configuration --> Display option. Then disable screen blanking.
The goal is to open a web browser in my home network from a from a remote location with ssh tunnelling.
SSH tunnel is okay, I just want to somehow run a browser on my RPI3 in my home network.
Is it possible somehow?
I use my pi as a media server, only kodi is running on it, there isn't any GUI operating system on it (raspbian for example).
All kind of solution is interested.
I'm connected to my Raspberry PI via SSH (Rasbian). Now I want to start an Application from it that uses a Graphical Interface. That Application is a simple Mono Window. It should be displayed on the PI's Display
I can't do it because it tells me that is has no DISPLAY set (thats true, since I use SSH)
When I'm starting it from the terminal app on the PI's Desktop it works as expected.
My querstion is now: What do I have to do, that I can start this app over SSH and the window pops up on the PI's desktop?
If you're trying to start the X application on the remote X server, see https://serverfault.com/questions/142244/how-do-i-start-a-x-application-on-remote-server-over-ssh
If you're trying to start the X application on the Pi, but show its window on your local desktop (you'll need X11 on your local desktop), use ssh -X.
I have a laptop, and I want to force the native screen to display 1080p. I know the display driver is capable of that because I have connected it to a 1080p screen before and it worked.
I am doing this because I want to establish a remote connection from my Raspberry Pi to the laptop. The Pi (an ARM linux machine) is connected to the 1080p screen. At the moment, the remote connection only covers part of the screen, as the laptop is only displaying 1366x768 (or something).
I want a software solution, if possible. Also, I want a server-side solution (that is, on the windows machine) as finding and using Linux software that works on the pi is a bit of a nightmare!
I am using TightVNC, though am prepared to try any package is free and which works well, as a server for Windows and client for ARM Linux.
Solutions I have tried that don't work:
'show all modes' on control panel (still didn't show the mode 1920x1080, which I know the graphics adapter can do)
ZoneScreen OS (wouldn't let me create a higher resolution)
Demoforge Mirage (um... didn't do anything. Maybe I didn't get how you're supposed to use it)
To force the raspberry pi to have a certain display. Go on boot folder cd /boot/
After that, open the config file with your editor (I use geany sudo apt-get install geany)
sudo geany config.txt
In this file, it should have two line that you have to uncomment it:
framebuffer_width=800
framebuffer_height=600
Just change the values of those variables and save the file.
You may have to reboot your raspberry pi
The problem:
I have a scrambled keyboard while using VMware Player on Linux from NX Client on a MacBook Pro. Letters are numbers, numbers are letters, delete is comma, e is delete; it's pure madness. I asked Google but it seems just as confused as me.
Note:
I am using an old-school mac keyboard with number pad plugged into my MBP and an additional monitor.
Things I've tried:
Altering my Linux keyboard settings (Layout: USA, USA Macintosh. Model: Apple, MBP, Apple Aluminum)
Altering my MBP keyboard settings (actually didn't see any settings that would affect this)
Unplugging my old-school keyboard with number pad and only using my MBP keyboard
Have the same issue, but with virt-manager (NX client runs on my Mac 10.6.8, connects to an Ubuntu 10.10 server and all is well, but if I run virt-manager and open a virtual machine, the keystrokes sent to the VM are all messed up).
I guess it has something to do with the Mac NX client and the VNC client (built into virt-manager) on the linux server. I tested the same setup in a Windowx XP virtual machine and it worked flawlessly. So it's got to be the Mac NX Client somehow.
As a workaround I've found that if I create an SSH with a port-forward from the remote linux-server (where I used to run virt-manager to access a VM running on another server) to the server with the VM and I forward a local port to the VM's vnc-server, then I can start up a VNC client (on the linux-server that I connect to via NX) and connect to the VM via the SSH tunnel and keys work just fine. So in my case the problem is somehow with the Mac NX Client + virt-manager's embedded VNC client.
I'm just guessing here, but VMware Player might use an embedded VNC server+client as well to show you the VM's screen. And both the reason for the problem and the workaround might be the same. Ie. try to use a separate VNC client to connect to the VM.
Update: I've got the solution to my problem, it's a KVM bug. The KVM machine starts the VNC server for the VM without specifying the correct keymap to use. See: http://blog.loftninjas.org/2010/11/17/virt-manager-keymaps-on-os-x/
The solution for VMware Player might be just as simple. A little googling revealed that VMware supports connections to a VM via VNC. Here's how to specify a keyboard layout for a VM's VNC server: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004815
Probably you just have to:
shut down the VM
open the VMX file in an editor
add the proper keyboard layout to the file as described on the page linked above (I guess you should specify the layout that your Linux server uses, eg. en-us)
start the VM and test with a VNC client
Of course it'd be better if you could tweak the Player's console to handle keycodes properly, but I did not find a fix for that.