Can't rotate (Default) screen on Raspberry Pi3 running Manjaro with X11 - raspberry-pi

I’m running the latest version of Manjaro ARM i3 on a Raspberry Pi3 (Image: Raspberry Pi 4 I3 20.10). I can’t for the love of me get the screen to rotate. I recently switched from Manjaro Wayland to this version because of Synergy support.
What I tried:
Using xrandr to rotate the screen. xrandr only sees a “Default” screen and when I try to rotate it I get the error:
$ xrandr --output default --rotate inverted
xrandr: output default cannot use rotation "inverted" reflection "none"
Using ARandR to rotate the screen. This will show my desktop in the GUI tool but the options to Rotate are greyed out. My main screen shows up as 'Default' here to.
Using the Raspberry PI config file at /boot/config.txt to set the rotation. This does also not work.
I’m running the Stock version with no extra software. Any tips on how to get the screen to rotate?

I was able to solve this by disabling the vc4-fkms-v3d drivers. You can do this using the following steps:
Open you config file at /boot/config.txt
Using a #, comment out the line: vc4-fkms-v3d
Add the rotation to the config like:
display_rotate=1 - for 90 degree rotation
display_rotate=2 - for 180 degree rotation
display_rotate=3 - for 270 degree rotation
Reboot
Your screen should now be rotated. Please note that this disables the vc4-fkms-v3d video card drivers which could have other unforeseen effects. Also keep in mind that this is the case for a RPi3.

I eventually found a even better solution thanks to the user BashCrash over at the Manjaro Forum
The steps are as followed (with vc4-fkms-v3d enabled in the /boot/config.txt):
Boot into Manjaro i3
Open a terminal
Go to to /etc/X11/xorg.conf.d (cd /etc/X11/xorg.conf.d)
Move the file 99-fbturbo.conf.d with mv 99-fbturbo.conf.d 99-fbturbo.conf.d.old
Reboot
After the reboot you xrandr should list the correct outputs (HDMI-1 in my case). You can then rotate the screen using:
xrandr --output HDMI-1 --rotate left
You can make this setting permanent by adding it to you .i3/config file. Add the following line:
exec xrandr --output HDMI-1 --rotate left
The trade off with the original method is that the screen will rotate after boot and login. More in depth explanation on potential trade-off's can be found here: https://forum.manjaro.org/t/i3-on-raspberry-pi-4-with-dual-monitors/20996/9

Related

Cannot connect to Coral Dev Board (Edge TPU)

While following the instructions on Get Started with Edge TPU Dev Board, I can't get past Step 2:
$ screen /dev/ttyUSB0 115200
The issue is that screen immediately returns
[screen is terminating]
I have verified the contents of /etc/udev/rules.d/65-edgetpu-board.rules, verified the dmesg output, tried different USB ports, verified that all screen instances are closed, etc.
Solution = run screen command with sudo:
$ sudo screen /dev/ttyUSB0 115200
First you should flash your iptables
Coammands:
sudo iptables -F
mdt devices

RPi Zero with RTC DS1307 - Remote I/O Error

EDIT: This problem is solved! the problem was a script running on the pi, which occupied the SCL pin (in my case a script listening for a shutdown button). So it was not able to read the rtc.
I'm currently following this tutorial to connect my Raspberry Pi Zero W running Jessie Lite to the RTC DS1307.
The rtc is being recognized when running sudo i2cdetect -y 1 with "UU", so everything fine until this point.
But when entering sudo hwclock -D -r I'm getting an error:
Does anybody have any experience or hints with this error? I was researching for 1 1/2 day now, but could not find a working solution. Any help is appreciated.
Back then I was not able to answer my own question. I have already edited the main post, but to close this question:
This problem is solved! the problem was a script running on the pi, which occupied the SCL pin (in my case a script listening for a shutdown button). So it was not able to read the rtc.

Serial console in Raspberry Pi 3 for testing FONA 808

I'm trying to set up a FONA 808 to connect to the internet to a Raspberry Pi 3, but when I run the serial console "sudo screen / dev / serial0 115200" I'm sometimes answered with "OK" and in others the console displays the message as if it were electromagnetic noise, and at other times the console simply crashes Is this normal? How can I solve that?
I am using a Fona 808 Arduino Shield connected to 5V and the TX and RX ports pass through a level logic shifter to convert the logic of 5V of the fona to logic of 3.3V of the raspberry
I am following this tutorial:
https://learn.adafruit.com/fona-tethering-to-raspberry-pi-or-beaglebone-black/setup
Blocked console:
Electric noise display:
Check your /boot/cmdline.txt file.
This is how I solve my pi with the same error.
nano /boot/cmdline.txt or sudo nano /boot/cmdline.txt
copy the script below and paste this in your cmdline.txt
dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
make sure "console=ttyAMA0,115200" is not on the script.
Make sure you have your original script. Test your pi if it reboot correctly. If it doesn't you can change back the cmdline.txt directly on your sd card and paste your original script.
This command should work with the response back
sudo screen /dev/serial0 115200
AT
ok
This should be a comment but I don't have the reputation to comment so...
Couple of things to try that might help.
1) You shouldn't need the level logic shifter. I don't know exactly what FOAN board you are using but they normally have a Vio pin that sets the voltage of the logic. So in this case you just connect the Vio pin to 3.3V on the Raspberry Pi and the RX and TX will be working at 3.3V.
2) Check your wire connections. Might just be a case of a bad connection.
3) I had better luck with minicom than screen So a command like this should work to connect the bard. sudo minicom -b 115200 -o -D /dev/ttyS0

How can I Increase Memory of Beaglebone Black?

everyone. I have been trying to increase the memory of my BleagleBone Black rev c without success.
I have followed these instructions in order to increase the memory of my BBB with a 16GB microSD card. I have already tried burning 2 different images Debian 9.1 2017-08-31 4GB SD LXQT and Debian 8.7 2017-03-19 4GB SD LXQT (without flashing the eMMc) .
The steps that I have been using are listed below.
What I first did was to burn the image into the microSD card using
Etcher.
Then I inserted the microSD into the BBB, I pushed the boot button
and then I plugged it into my computer to turn it on.
After that, I logged into my BBB using ssh and I checked for the
Debian version and it was correct. Indicating that the boot from the
microSD card was correct, but when I tried to check disk space I
couldn´t find the partition for the microSD.
As you can see in the image below it is supposed to show the rootfs where I have the new BBB image and the 16GB extra space, but I´m not able to see the extra partition. Does anyone know what I could be possibly doing wrong?
I am facing with the same issue and I end up with
Login to your BBB by ssh
Run this command
nano grow_partition.sh
copy code from here then paste it on the terminal
save file by pressing control + o then enter
Exit from nano editor by pressing control + x
Run this command sudo ./grow_partition.sh
Reboot BBB
Enjoy :)
I have a beaglebone black (original with 512MB mem) and I was able to use a different method to add swap memory successfully (unfortunately user3680704's method didn't work for me).
I got the idea from this post which basically says the following:
You can check your current memory with
free -h
And you can create the swap memory by running these commands. Again a more detailed better explanation is in the link above, but in case that ever goes dead you can follow these:
sudo fallocate -l 1G /swapfile
ls -lh /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
Next open the fstab file by running
vi /etc/fstab
and add the following line to the file
/swapfile swap swap defaults 0 0
You can then check your swap by running
swapon --show
This worked well for me, added 1G of swap. You can add more or less by changing the 1G value

RPI kiosk mode fullscreen epiphany

I have a raspberry pi 2 model B with Raspbian that i want to boot into fullscreen browser.
I can get it boot into the browser with the right url, but not in fullscreen.
I am using ths command line to boot it up.
epiphany-browser http://mylink.com
What should i do to get it into fullscreen?
install xautomation first:
sudo apt-get install xautomation
and then you can put this in a shell script:
#/!/bin/bash
epiphany-browser http://mylink.com &
sleep 15
xte "key F11" -x:0
Got it from link