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
Related
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.
I'm working on a game written in pyglet. On my dev laptop using Fedora23 when I run it I can hear music/fx coming out my analog port, I have the default windows manager gnome3.
As test I installed it in a PC that will be used once it's finished.
We use a basic installation Fedora 23, with only X11 basic Desktop OpenBox (I guess), and all the packages to run the game.
Game starts but no audio at all, if I run "aplay /test.mp3" inside a terminal windows I can hear the music, it's like default audio is not set correctly inside X11.
Alsamixer has high volume, use pulseaudio as Card/Chip, I can select other card Realteck ALC283 still high volume, but still no sound, I'm logged in as root. I'm lost.
RESOLVED: I use avlib as library in my pyglet game. The game seems to start and work having the lib inside the same folder, but once moved to another PC I realize that it was not sufficient. After checking and comparing with my PC and the new one, I come across the FFMpeg library that after installed fixed my issue.
I started this project with a Raspberry Pi, but realized that the Banana's hardware set is a much better fit for what I'm doing. Unfortunately, it appears that, even though LeMaker (the group behind the BPi) offers just about every OS imaginable pre-optimized for the Banana, only Bananian supports all the hardware that I need, and it doesn't come with a GUI of any kind.
So, given a Debian-derivative on an ARM chip that will never see a physical display and has root SSH functional by default, how can I make it boot to an auto-logged-in VNC server?
Here's what I've done so far, as root over SSH:
# bananian-config
# bananian-update
# apt-get update
# apt-get upgrade
# adduser pi
# passwd root
# apt-get install task-lxde-desktop
(the first two are announced in the SSH welcome message and are used to initially setup the generic image for this variation of the board)
Then I uncommented these lines in /etc/lightdm/lightdm.conf:
autologin-user=pi
autologin-user-timeout=0
[VNCServer]
enabled=true
command=Xvnc
port=5900
width=1024
height=768
depth=8
At this point, I rebooted and tried to connect with VNC, but the client gave the same error as when the server doesn't exist. SSH still works as root and now the "pi" user also, except that the "pi" user doesn't know sudo.
At this point, I'm lost. I don't know if there's a desktop waiting for me on the HDMI plug or not, or whether I need an explicit VNC server like x11vnc or tightvnc, or if there's something else wrong.
This is all I've done so far. I can re-flash the image if needed; I want to make this part work before adding anything project-specific.
Okay, I noticed in LeMaker's own instructions to make Wifi work that they included Android and Lubuntu too, and that someone on their forum had made VNC work on Lubuntu. I didn't see before that some other OS's would support the WiFi chip.
So I switched to Lubuntu, which already has a working desktop, installed x11vnc per its instructions, and it basically just worked.
Then I backed up the SD card and spent all of Saturday trying different ways to make it a WiFi access point, which usually resulted in kicking myself out and restoring the backup to try again. And finally that works too. So I backed up the card again and now I can work on the real functionality.
I would like to setup a small computer (Raspberry Pi) running Arch Linux to accept remote X sessions. Doing this usually means setting up Xorg server and running one of the Display Managers. I have done this before, and I will go this route if I have to. However, since the machine is very underpowered, and it is actually not connected to a physical monitor, I was hoping to setup the X server to accept only remote sessions. This way no memory would be wasted on managing the local graphics card, video memory etc, since they are not being used. Is it possible to setup the X server to accept only remote sessions without going into local graphical mode? And how?
It's possible to set up a *ix to remote display to a system you're sitting in front of, without an X server on the machine running the app.
You need X11 libraries, one or more X11 applications, and you probably want openssh set up for remote X11 forwarding - all on the raspberry pi. You'll also want an X server running on the machine you're sitting in front of.
On the Raspberry Pi, change your sshd_config to include "X11Forwarding yes". After making this change, restart sshd or reboot.
Then apt-get or yum your X11 libraries and app(s).
When you connect to the Raspberry Pi machine, use "ssh -Y" instead of just ssh to pass along xauth data.
Good luck!
Disable automatic start of the login manager and X server, instructions are googlable, say http://www.debianadmin.com/howto-boot-debian-in-text-mode-instead-of-graphical-mode-gui.html. From personal experience running X apps on raspberry remotely is not too good either.
In the spirit of being helpful, this is a problem I had and solved, so I will answer the question here.
Problem
I have:
An application that has to be installed on on Redhat or SuSE enterprise.
It has huge system requirements and requires OpenGL.
It is part of a suite of tools that need to operate together on one machine.
This application is used for a time intensive task in terms of man hours.
I don't want to sit in the server room working on this application.
So, the question came up... how do I run this application from a remote windows machine?
I'll outline my solution. Feel free to comment on alternatives. This solution should work for simpler environments as well. My case is somewhat extreme.
Solution
I installed two pieces of software:
PuTTY
XMing-mesa The mesa part is important.
PuTTY configuration
Connection->Seconds Between Keepalives: 30
Connection->Enable TCP Keepalives: Yes
Connection->SSH->X11->Enable X11 forwarding: Yes
Connection->SSH->X11->X display location: localhost:0:0
Lauching
Run Xming which will put simply start a process and put an icon in your system tray.
Launch putty, pointing to your linux box, with the above configuration.
Run program
Hopefully, Success!
If you want the OpenGL rendering to be performed on your local machine, using a Windows X server, like Xming is a good solution. However, if you want rendering to be done on the remote end with just images sent to the local machine, you want a specialized VNC system that can handle remote OpenGL rendering, like VirtualGL.
You could also use VNC ( like cross platform remote desktop )
X is more efficent since it only sends draw commands rather than pixels, but if you are using opengl it is likely that most of the data is a rendered image anyway.
Another big advantage of VNC is that you can start the program locally on the server and then connect to it with VNC, drop the connection, reconnect from another machine etc without disturbing the main running program.
For OpenGL, running an X server is definitely a better solution. Just make sure the application is developed to be networked. It should NOT use immediate mode for rendering and textures should be RARELY transferred.
Why is X server a better solution in this case (as opposed to VNC)? Because you get acceleration on workstation, while VNC'ed solution is usually not even accelerated on the mainframe. So as long as data is buffered on the X server (using vertex arrays, vertex buffer objects, texture objects, etc) you should get much higher speed than using VNC, especially with complex scenes since VNC has to analyze, transfer and decode them as pixels.
If you need server glx version 1.2 the free version of Xming (Mesa 2007) works fine. But if your application needs version 1.4, example qt5, the X Server from Cygwin works free to run it use this commands:
[On server]
sudo vi /etc/ssh/ssh_config
Add:
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalHost no
AllowTcpForwarding yes
TCPKeepAlive yes
ClientAliveInterval 30
ClientAliveCountMax 10000
sudo vi ~/.bashrc
Add:
export DISPLAY=ip_from_remote:0
Now restart ssh server
[On Client slide]
Install Cygwin64 (with support to X package) after that run this command:
d:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; /usr/bin/xinit /etc/X11/xinit/startxwinrc -- /usr/bin/XWin :0 -ac -multiwindow -listen tcp"
Now execute ssh client:
d:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico -e /usr/bin/ssh -Y user_name#ip_from_server