ice
> himbeere@rather ~ $
>
> Downgrading to 5.11 solves the issue for me. Any ideas?
Does [1] fix your issue?
[1]
https://cgit.freedesktop.org/drm-tip/patch/?id=acca7762eb71bc05a8f28d29320d193150051f79
--
Oleksandr Natalenko (post-factum)
__
4.5-rc3 is affected as well:
===
kernel: [drm] Initialized drm 1.1.0 20060810
kernel: [drm] Memory usable by graphics device = 2048M
kernel: [drm] Replacing VGA console driver
kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
kernel: [drm] Driver supports precise vblank timestam
Hi.
With Linux 4.4 external HDMI-attached monitor in not discovered by i915
driver. Here is boot log related to drm and i915 for Linux 4.4/4.4.1
kernel:
===
kernel: [drm] Initialized drm 1.1.0 20060810
kernel: [drm] Memory usable by graphics device = 2048M
kernel: [drm] Replacing VGA console
Daniel,
I do confirm that this hacky patch:
https://lkml.org/lkml/2016/1/19/637
works around my issue. I understand that this is improper fix, so let me
know how could I debug my issue further.
Thanks.
09.02.2016 12:11, Daniel Vetter wrote:
Can you please retest with latest -rc? There's bee
Daniel,
I've already tried Ville's patch you've mentioned with no luck.
Kindly find unpatched v4.5-rc3 dmesg with drm debug enabled here: [1]
[1] https://gist.github.com/efb44b7c6bc325978b80
11.02.2016 10:21, Daniel Vetter wrote:
Please boot with drm.debug=0xe and attach the dmesg. Also please
писав:
On Thu, Feb 11, 2016 at 10:54:08AM +0200, Oleksandr Natalenko wrote:
Daniel,
I've already tried Ville's patch you've mentioned with no luck.
Kindly find unpatched v4.5-rc3 dmesg with drm debug enabled here: [1]
[1] https://gist.github.com/efb44b7c6bc325978b80
That's
Ville,
I've applied patch you've provided and did couple of replugging with
intel_reg in between. Here are the results.
I used additional VGA cable to see what actually I type in console :).
Both HDMI and VGA cables plugged: [1]
Both HDMI and VGA cables unplugged: [2]
Only HDMI cable plugged:
Hi, Ville.
13.02.2016 01:23, Ville Syrjälä wrote:
Few other ideas:
- Was the monitor sleeping when you tried this? Can you maybe push
some button on it and then immediately run the intel_reg read command
again?
Nope. It just goes to sleep mode after (I suppose) drm module is loaded.
Befor
13.02.2016 01:23, Ville Syrjälä wrote:
- Do you have another monitor to try?
- Do you have another cable to try?
More on this.
Computer DVI —— old DVI-HDMI cable —— old monitor HDMI == not working
Computer DVI —— another DVI-HDMI cable —— old monitor HDMI == not
working
Computer DVI —— DVI-D
Ville, Daniel,
I've just got another monitor and another DVI-HDMI cable, and here what
I've got.
===Single Link DVI-D cable with 3 different monitors===
Computer DVI ——— DVI-D (Single Link)/HDMI cable ——— HDMI LG 23MP65HQ-P
=== not working
Computer DVI ——— DVI-D (Single Link)/HDMI cable ———
16.02.2016 14:54, Daniel Vetter wrote:
Computer DVI ——— DVI-D (Single Link)/HDMI cable ——— HDMI LG 23MP65HQ-P
===
not working
I presume the above LG screen is what you've called previously "old
monitor"?
Correct.
Computer DVI ——— DVI-D (Dual Link)/HDMI cable ——— HDMI LG 23MP65HQ-P
===
wor
(0x000c2020): 0x60004000
===
Let me know if you need more info.
[1] https://gist.github.com/dfbf237e74ed6e0b1bf7
16.02.2016 14:54, Daniel Vetter wrote:
On Tue, Feb 16, 2016 at 12:58:56PM +0200, Oleksandr Natalenko wrote:
Ville, Daniel,
I've just got an
Ville, Daniel,
any additional info I could provide? I have to return dual-link DVI
cable back, so let me know if I could reveal more details if necessary.
Regards,
Oleksandr
16.02.2016 14:54, Daniel Vetter написав:
On Tue, Feb 16, 2016 at 12:58:56PM +0200, Oleksandr Natalenko wrote
23.02.2016 17:08, Ville Syrjälä написав:
In the meantime I think as a workaround I think you could use
something like video=HDMI-A-1:e on the kernel command line (not sure
I got the connector name right for your system). I think that should
result in the live status check to be skipped, at least
24.02.2016 06:40, Jindal, Sonika написав:
Do you have logs for the failure with the single link hdmi cable and
the register dump which you have given for the working case?
If not, can you please capture the logs and register dump.
Also which platform is this?
If it is live status related issue, w
to make the issue more visible.
Please help.
Thanks.
[1] https://gitlab.freedesktop.org/drm/intel/-/issues/9256
--
Oleksandr Natalenko (post-factum)
signature.asc
Description: This is a digitally signed message part.
/cc Matthew Wilcox and Andrew Morton because of folios (please see below).
On sobota 2. září 2023 18:14:12 CEST Oleksandr Natalenko wrote:
> Hello.
>
> Since v6.5 kernel the following HW:
>
> * Lenovo T460s laptop with Skylake GT2 [HD Graphics 520] (rev 07)
> * Lenovo
/cc Bagas as well (see below).
On úterý 19. září 2023 10:26:42 CEST Oleksandr Natalenko wrote:
> /cc Matthew Wilcox and Andrew Morton because of folios (please see below).
>
> On sobota 2. září 2023 18:14:12 CEST Oleksandr Natalenko wrote:
> > Hello.
> >
> > Since v
Thank you.
Please consider correcting the title though. Lenovo T14s (Tiger Lake) is not
affected. Affected are: Lenovo T460s (Skylake) and Lenovo T490s (WhiskeyLake)
--
Oleksandr Natalenko (post-factum)
signature.asc
Description: This is a digitally signed message part.
Hello.
On úterý 19. září 2023 17:43:40 CEST Matthew Wilcox wrote:
> On Tue, Sep 19, 2023 at 10:26:42AM +0200, Oleksandr Natalenko wrote:
> > Andrzej asked me to try to revert commits 0b62af28f249, e0b72c14d8dc and
> > 1e0877d58b1e, and reverting those fixed the i915 cr
20 matches
Mail list logo
