-
Notifications
You must be signed in to change notification settings - Fork 67
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
No console when external HDMI monitor connected #14
Comments
I don't have this problem on my skylake system. |
It's x1 carbon 6th, Intel Kaby Lake. |
After seeing #17, I tried booting with |
hw.i915kms.enable_psr is a tunable so you can't change it after booting with sysctl, kenv should work. |
BTW, tt is surprisingly that setting |
Should we have that setting by default (at least for Kaby Lake?), or was the setting changed around end of last year? |
I've made the setting default for us because I don't have hardware to reproduce the problem. |
Haven't updated to that version. I'll test and report here. |
@lwhsu ping ? Do you still have this issue with latest 13.0-ALPHA1 and latest drm-kmod ? |
Sorry that I still cannot update to newer -current because am busy at other projects. Will try out in the weekend. |
Tested again with 14.0-CURRENT c256325-g4f009328a247 and drm-devel-kmod-5.4.62.g20210118, looks good to me. |
I'm not sure if this is due to the system or drm-kmod, but now after I kldload i915kms.ko in console, the main monitor on my laptop hangs if there is an external HDMI monitor connected, all the following updates only display on the external monitor. If I disconnect the external monitor, the main monitor on the laptop will catch up all the updates. Under X, both monitors work fine.
Is this an intentional behavior? This is different than before and is a bit inconvenient if you want to do presentation.
System information:
FreeBSD x1c.lwhsu.org 13.0-CURRENT FreeBSD 13.0-CURRENT #19 r363121M: Mon Jul 13 18:41:40 CST 2020 [email protected]:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64
I've tested this with 5.3.g20200708 and 5.3.g20200710, both have this situation.
Wanted to revert to 5.3.g20200612 but it cannot compile on 13.0-CURRENT r363121 currently.
The text was updated successfully, but these errors were encountered: