New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Works in console, stops working in desktop env #200
Comments
Disabled kms and fkms. Problem solved. Is it though?
|
I think this is an Octopi issue, since this works on Raspberry Pi OS. At an absolute guess it doesn't do any of the weird monkeying with /usr/share/dispsetup.sh that Pi OS uses to make displays work. Do you see anything if you What Window manager/desktop environment does Without kms you're at the behest of whatever window manager you're using to handle rotation in software, effectively, which isn't very desirable. |
The only way I have been able to get this to work on the pi3a is disabling kms and fkms. I've spent two+ days on this. The pi3b+\pi4 method actually works but I couldn't get the screen to rotate in ratpoison. Tell me what you need and I will supply it. I've got two identical pi3a's with this setup right now that I can play with. I also discovered that enabling i2c breaks the display the same way. i2c on, blank screen with backlight. i2c off, normal operation. |
PLEASE NOTE
Our software team are smol and busy, and you will not receive a timely response.
If you're having a hardware issue with your Hyperpixel 4, you should contact support@pimoroni.com.
Describe the bug
The display works perfect until I set the pi to start into desktop. I can see it goes through the boot sequence but once it startx it goes black (but still backlit). I've skinned this cat 9 different ways and every variation produces the same results. Console good, X bad.
To Reproduce
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
sudo apt clean
sudo reboot
sudo /home/addohm/scripts/install-desktop
sudo reboot
git clone https://github.com/pimoroni/hyperpixel4 -b pi4
cd hyperpixel4
sudo ./install.sh
edit /boot/config.txt - dtoverlay=vc4-fkms-v3d
sudo reboot
(Display works at this point)
sudo raspi-config - boot to desktop
(Display stops working once boot reaches startx)
Your HyperPixel 4
Let us know which HyperPixel 4 board you're using. Note: if you're having a problem with the original HyperPixel you should go to: https://github.com/pimoroni/hyperpixel
Last week
Directly using the riser header
Your Raspberry Pi
Give as much detail about your Pi and OS as possible. We only officially support Raspbian, but might be able to point you in the right direction if the problem is with another OS.
What model of Raspberry Pi are you using (the result of
cat /proc/cpuinfo | grep Revision
can tell us this exactlyRevision : b03115
Which OS release are you using:
lsb_release --description
anduname -r
Description: Raspbian GNU/Linux 11 (bullseye)
Is this a fresh OS setup, or one you might have previously installed scripts/add-ons on?
"Other specific purpose OS" > Octopi
Extra debugging information
If you're having a problem with touch, try checking
dmesg
for related errors:dmesg | grep Goodix
for HyperPixel 4.0" Rectangular*[ 7.119080] Goodix-TS 22-0014: supply AVDD28 not found, using dummy regulator
[ 7.119487] Goodix-TS 22-0014: supply VDDIO not found, using dummy regulator
[ 7.126802] Goodix-TS 22-0014: Error reading 1 bytes from 0x8140: -6
[ 7.154612] Goodix-TS 22-0014: Error reading 1 bytes from 0x8140: -6
[ 7.181055] Goodix-TS 22-0014: I2C communication failure: -6
dmesg | grep ft5
for HyperPixel 4.0" SquareAnd check i2c is working:
ls /dev/i2c-*
/dev/i2c-22
You should see something like:
And your HyperPixel 4 touch is showing up (there should be an address blocked out with UU in the below command):
i2cdetect -y X
( where X is the number of i2c bus found in the command above)For example:
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- 5d -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
The text was updated successfully, but these errors were encountered: