When I type on my keyboard ctrl+alt+T or ctrl+alt+F1,2,3 and so on nothing happens.
I have raspbian Buster lite. And I've estblished raspberry to kiosk mode by adding chromium to /etc/xdg/openbox/autostart
Where should I see to find something that doesn't allow to go to terminal?
I found my mistake. In the file /boot/cmdline.txt was fbcon=map:2 when I removed it, everything became OK
Related
I'm able to ssh into pi from MacOS using ssh pi#raspberrypi.local or ssh pi#ip_address. I have been doing this for a long period of time. Now I installed Manjaro Linux along with the MacOS but I can't ssh in pi from Manjaro. ssh pi#raspberrypi.local returns name not found error while the other command times out. Works as expected when I switch back to MacOS. I've been stuck on this for a while now, I've tried multiple solutions but nothing seem to work. I have also tried re-installing and starting sshd but no luck.
You should check the information of /var/log/message on Raspberry PI, where the problem has been checked
The problem was in the Network adapter driver. If you are facing this problem check which driver are you using. If it is anything other than the Broadcom driver delete it and install the Broadcom driver and should work fine.
When you try share screen or use screen recorder in Arch Linux or Manjaro, the screen is blinking like in here: https://imgur.com/7dzeiXr
How to solve?
If you use x11, then to solve this problem :
Uninstall package: xf86-video-intel
Remove file (if it exists): /etc/X11/xorg.conf.d/20-intel.conf
Reboot your system
Try your screencast again...
I try to build a reproducible automated build environment based on Debian 8.1 Jessie.
I created a boot iso image based on a netinstall image and put a preseed.cfg file in int for automatic installation.
I managed to get it bootable with BIOS and UEFI and can install a KDE Developer Debian in VMWare Workstation 11 fully automated.
I have also a server iso image to install a debian Server with Jenkins, both with BIOS and UEFI Boot.
But after the installation, the Version with UEFI Boot shows a black Screen when started.
I can blindly log in, start the gui with "startx" and see my installed xfce desktop. When i quit xfce the console is usable and visible.
I tried suggested bootparameters "nomodeset" and "vga=Linux" that i found with google to no avail.
I also tried to debug the boot prozess, to find out which command leads to a blank screen, but i did not find the right place to delay the processes at bootup so i can see when the messages dissapear (quiet bootparameter was removed :-)
I also tried to reset the console to no avail.
Can anybode point me to a tool that does the same "switching" like X so the console is useable?
Can anybody give me some hints how to debug the bootprocess to find out which command is causing this behaviour?
I dont want to install X because this should be a headless server system later.
I managed to get my system to boot using the kernel command line modprobe.blacklist=vmwgfx, or placing 'blacklist vmwgfx' in /etc/modprobe.d/*.conf
I assume it is some bug in the vmwgfx module, however as this workaround works for me I have no immediate need to investigate further.
I have set up some Raspberry Pi's in my corporation with Screenly inside. It has simple overlay to show a webpage with some slides.
My problem is the screensaver that turns on when I'm not at work. I tried to add a reboot command to the crontab, edit boot settings with screensaver, etc.
When testing it for few (6-8) hours, the screen never turns black, but overnight when I'm gone, the screen turns black. What can I do to stop this?
There was a similar question posted on the Raspberry Pi StackExchange.
There they suggest installing x11-xserver-utils (with apt-get install), and adding these lines to your ~/.xinitrc file:
xset s off # don't activate screensaver
xset -dpms # disable DPMS (Energy Star) features.
xset s noblank # don't blank the video device
Restart X, and your problem should be solved.
I have a raspberry pi running arch linux connected to the TV and want to run commands on that screen by SSH'ing from my Ubuntu machine elsewhere.
I have tried running the command SSH -Y root# and starting xclock as a test. However I get the following error:
No protocol specified
Error: Can't open display: :0
I then tried running "export DISPLAY=:0" on the arch machine, but this doesn't solve the issue.
I have X running fine and can see it on the TV and I have edited the file /etc/ssh/ssh_config to allow X11 forwarding.
Anyone know what I am doing wrong?
Many thanks
The ArchLinux wiki has some good instructions on setting things up. I struggled for a while until I found them, but for me the key was to set up SSH forwarding within sshd_config (most distros seem to enable this by default, but Arch doesn't).
Once you've enabled X forwarding in SSHD, I also found it helpful to install the dummy video driver for Xorg ("pacman -S xf86-video-dummy"), which gets rid of irritating errors about missing the RANDR extension. This might not be necessary if you already have it running a real X server locally on the Pi - personally, I'm running mine completely headless.
I've found that I don't have to worry about setting up the DISPLAY variable, or xhost, when running with 'ssh -X' from an iMac. I'd expect Ubuntu to behave the same.
looks like an authentication problem. The answer used to be
xhost +
on the console of the X display. Might help.
You probably want to set
export DISPLAY=[IP_ADDRESS_OF_ARCH_BOX]:0
on your Ubuntu box, then when you run xclock from your Ubuntu box, it'll forward the screen to the Arch box.