-
Notifications
You must be signed in to change notification settings - Fork 5.2k
No signal after Xorg startup #4695
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
Comments
Buster was working fine. |
OK, this is weird. Wiped the SD card and re-loaded the same image, had the exact same problem on first boot. Decided to:
In both cases I did an apt-get update && apt-get dist-upgrade (the original and this one). So I am running with 5.10.63-v8+ kernel at the moment. I was thinking maybe it was an issue with the splash screen from Plymouth (?), so I went through and add quiet splash back in cmdline and it's still fine. I can't imagine it's enable_uart=1. |
Test without that. It can have the effect of forcing core clock higher which could potentially be beneficial for hdmi. |
@popcornmix Yep, that was it. Last thing I would have thought, but now it makes sense as I had a similar problem testing 5.15 on LE10 (no issue with the current kernel they push). It started up with no display, and I enabled uart to see what was going on and it worked fine there too -- but there was other issues on 5.15 with video playback. Is this one of the known issues? Any other recommended workaround other than enable_uart=1? |
|
Yeah, that seems to work as well. What's interesting is according to bcmstat.sh the core freq is 550 once X is up. This is also one of the Pi4's with that newer voltage regulator (which I guess is basically all 8G models?), so the ARM freq max is 1800. All of my 2 gig models have the older circuit design, which I don't overclock. https://www.raspberrypi.com/news/bullseye-bonus-1-8ghz-raspberry-pi-4/ |
Seems to be resolved as of commit e13d4e9 |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Running latest bullseye image,
I saw initially in dmesg it was complaining about this:
So did that, result is the same. Next decided to try 5.15 kernel, ran BRANCH=next rpi-update, reboot, result is the same. Figured had nothing to lose at this point, threw in an arm_64bit=1 in config.txt, and well no change.
Oddly the first time it booted on the fresh bullseye image (previously was on buster with fkms), did see the desktop for a brief second but it had a lot of artifacts.
System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:
Which model of Raspberry Pi?
Pi 4B 8G
Which OS and version (
cat /etc/rpi-issue
)?Raspberry Pi reference 2021-10-30
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 288b21fc27e128ea6b330777aca68e0061ebf4fe, stage4
Which firmware version (
vcgencmd version
)?Nov 5 2021 19:46:11
Copyright (c) 2012 Broadcom
version b99321a10f46c9bd662fc87998419c5d6974927a (clean) (release) (start)
Which kernel version (
uname -a
)?Linux raspberrypi 5.15.1-v8+ #1483 SMP PREEMPT Wed Nov 10 13:00:40 GMT 2021 aarch64 GNU/Linux
also 5.10.63-v7l+ (initial kernel)
Logs
dmesg after enabling 4kp60:
modetest:
The text was updated successfully, but these errors were encountered: