On Mon, Feb 29, 2016 at 03:41:59PM +, Sharma, Shashank wrote:
> No problems, I guessed the mail situation :)
Ok, caught up now, at least on dri-devel. There's 2 bug report mail
threads:
- A new one from Oleksandr, still being investigated.
- This one here where Sonika asked for some logs from
No problems, I guessed the mail situation :)
Regards
Shashank
-Original Message-
From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
Sent: Monday, February 29, 2016 9:12 PM
To: Sharma, Shashank
Cc: Daniel Vetter; Ville Syrjälä; Oleksandr Natalenko; Vetter, Daniel
On Mon, Feb 29, 2016 at 03:16:08PM +, Sharma, Shashank wrote:
> Please see the latest mail chain, Sonika has already started on it.
Ah ok, crawling through 1k mails after one week of vacation, so I'm still
catching up ;-) My apologies for the confusion.
Thanks, Daniel
>
> Regards
> Shashank
Please see the latest mail chain, Sonika has already started on it.
Regards
Shashank
-Original Message-
From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
Sent: Monday, February 29, 2016 8:44 PM
To: Sharma, Shashank
Cc: Ville Syrjälä; Oleksandr Natalenko; Vette
On Wed, Feb 24, 2016 at 06:07:25AM +, Sharma, Shashank wrote:
> Hi Ville,
> We will look into this in sometime. Right now team is slightly loaded due to
> project milestone.
> Last time I looked into this, we dint have this HW to reproduce this issue.
This is an upstream regression. Either
Hi Ville,
We will look into this in sometime. Right now team is slightly loaded due to
project milestone.
Last time I looked into this, we dint have this HW to reproduce this issue.
Regards
Shashank
-Original Message-
From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com]
Sent: Tue
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
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
On 2/23/2016 8:38 PM, Ville Syrjälä wrote:
On Mon, Feb 22, 2016 at 02:32:32PM +0200, Oleksandr Natalenko wrote:
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.
Unfortunately I'm out of
On Mon, Feb 22, 2016 at 02:32:32PM +0200, Oleksandr Natalenko wrote:
> 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.
Unfortunately I'm out of ideas for now. Daniel is on vacation.
A
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:
Ville
Here is full dmesg with verbose patch on 4.4.1 and dual-link DVI-HDMI
cable: [1]
Dual-link works OK:
===
лют 16 17:46:38 pfactum.lanet kernel: port C live status
##
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
On Tue, Feb 16, 2016 at 12:58:56PM +0200, Oleksandr Natalenko wrote:
> 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 L
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 ———
On Mon, Feb 15, 2016 at 04:42:35PM +0200, Ville Syrjälä wrote:
> On Mon, Feb 15, 2016 at 10:55:33AM +0200, Oleksandr Natalenko wrote:
> > 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.
> >
> > Comp
On Mon, Feb 15, 2016 at 10:55:33AM +0200, Oleksandr Natalenko wrote:
> 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 DV
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
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
On Fri, Feb 12, 2016 at 09:52:03AM +0200, Oleksandr Natalenko wrote:
> 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 :).
>
My life would have be
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:
On Thu, Feb 11, 2016 at 01:16:53PM +0200, Oleksandr Natalenko wrote:
> Ville,
>
> here is another dmesg: [1]
>
> I've reconnected HDMI cable three times.
>
> Forgot to note, it is HDMI monitor plugged into machine's DVI with
> HDMI-DVI cable. I guess this should matter as well.
Shouldn't reall
Ville,
here is another dmesg: [1]
I've reconnected HDMI cable three times.
Forgot to note, it is HDMI monitor plugged into machine's DVI with
HDMI-DVI cable. I guess this should matter as well.
[1] https://gist.github.com/7057ea8512b9aa7ee5bd
11.02.2016 11:26, Ville Syrjälä написав:
On Thu
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 an IVB. So no
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 09:45:17AM +0200, Oleksandr Natalenko wrote:
> 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.
Please boot with
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
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
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
On Mon, Feb 08, 2016 at 12:17:07PM +0200, Oleksandr Natalenko wrote:
> 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: [d
30 matches
Mail list logo
