Bug 108826 - [GLK DSI] Black screen after grub - Ubuntu 18.04 - kernel latest tip 21.11.2018
Summary: [GLK DSI] Black screen after grub - Ubuntu 18.04 - kernel latest tip 21.11.2018
Status: NEEDINFO
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged, ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-21 23:39 UTC by Miroslaw
Modified: 2019-04-20 06:37 UTC (History)
7 users (show)

See Also:
i915 platform: GLK
i915 features: display/DSI


Attachments
kernel log (285.64 KB, text/plain)
2018-11-21 23:39 UTC, Miroslaw
no flags Details
drm.debug=0x1e (335.55 KB, text/plain)
2018-11-22 23:12 UTC, Miroslaw
no flags Details
igt-gpu-tools - dump i915.modeset=0_dump.txt (17.00 KB, text/plain)
2018-11-28 00:40 UTC, Miroslaw
no flags Details
igt-gpu-tools - dump fully_working_gpu_driver_black_screen_dump.txt (17.00 KB, text/plain)
2018-11-28 00:41 UTC, Miroslaw
no flags Details
Attached pic showing logo after grub (3.62 MB, image/jpeg)
2019-01-29 10:28 UTC, Stanislav Lisovskiy
no flags Details
Kernel boots after modeset with Tux logo on E Tab (4.02 MB, image/jpeg)
2019-01-29 10:32 UTC, Stanislav Lisovskiy
no flags Details
Ubuntu desktop (4.03 MB, image/jpeg)
2019-01-31 14:26 UTC, Stanislav Lisovskiy
no flags Details
kernel config for ubuntu (46.57 KB, application/octet-stream)
2019-02-01 15:30 UTC, Miroslaw
no flags Details
xrandr output for Lenovo D330 laptop screen (1.21 KB, text/plain)
2019-02-17 05:24 UTC, Mark Wynn Garcia
no flags Details
Lenovo D330 with HD screen N5000 CPU vbt (5.62 KB, application/octet-stream)
2019-02-17 05:46 UTC, Mark Wynn Garcia
no flags Details
Lenovo D330 with HD screen N5000 CPU dmesg with drm.debug=0x1e (125.53 KB, text/plain)
2019-02-17 06:07 UTC, Mark Wynn Garcia
no flags Details
D330 dmesg unpatched 4.20.8 (245.97 KB, text/plain)
2019-02-17 07:50 UTC, Mark Wynn Garcia
no flags Details
D330 dmesg patched 4.20.8 (246.56 KB, text/plain)
2019-02-17 07:51 UTC, Mark Wynn Garcia
no flags Details
kernel_5.0-rc4-no-pathed--screen_a.txt (243.30 KB, text/plain)
2019-03-08 11:57 UTC, Jani Nikula
no flags Details
kernel_5.0-rc4-not-pathed-screen_b.txt (67.89 KB, text/plain)
2019-03-08 11:58 UTC, Jani Nikula
no flags Details
kernel_5.0-rc4-pathed--screen_a.txt (241.47 KB, text/plain)
2019-03-08 11:58 UTC, Jani Nikula
no flags Details
kernel_5.0-rc4-pathed_screen_b.txt (67.64 KB, text/plain)
2019-03-08 11:58 UTC, Jani Nikula
no flags Details
panel a i915_vbt (5.59 KB, application/octet-stream)
2019-04-05 00:10 UTC, Miroslaw
no flags Details
panel b i915_vbt (5.59 KB, application/octet-stream)
2019-04-05 00:10 UTC, Miroslaw
no flags Details
full drm/0 panel a (130.01 KB, application/x-7z-compressed)
2019-04-05 00:12 UTC, Miroslaw
no flags Details
full drm/0 panel b (115.21 KB, application/x-7z-compressed)
2019-04-05 00:13 UTC, Miroslaw
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Miroslaw 2018-11-21 23:39:54 UTC
Created attachment 142557 [details]
kernel log

The screen after the grub is getting black ( backlight is still working ).  
System is booting normally - after that backlight screen is working .. and black all the time.
I can control brightness by shortcuts.
If connect HDMI cable then on the new via HDMI the screen works perfect but on the device screen is still black unfortunately .

I attached the kernel.



- edid from windows 10 

Monitor
  Model name............... WLY-10102FHD
  Windows description...... Generic PnP Monitor
  Manufacturer............. AUO
  Plug and Play ID......... AUO17D8
  Serial number............ n/a
  Manufacture date......... 2013, ISO week 11
  Filter driver............ None
  -------------------------
  EDID revision............ 1.4
  Input signal type........ Digital
  Color bit depth.......... 8 bits per primary color
  Color encoding formats... RGB 4:4:4, YCrCb 4:4:4
  Screen size.............. 140 x 220 mm (10,3 in)
  Power management......... Active off/sleep
  Extension blocs.......... None
  -------------------------
  DDC/CI................... n/a

Color characteristics
  Default color space...... sRGB
  Display gamma............ 3,55
  Red chromaticity......... Rx 0,625 - Ry 0,340
  Green chromaticity....... Gx 0,285 - Gy 0,605
  Blue chromaticity........ Bx 0,148 - By 0,063
  White point (default).... Wx 0,281 - Wy 0,309
  Additional descriptors... None



Thanks for any help.
Comment 1 Lakshmi 2018-11-22 07:28:54 UTC
Miroslaw, How often you see this issue? CAn you reproduce this issue?
Can you attach cat /sys/kernel/debug/dri/0/i915_edp_psr_status

Imre, any comments here?
Comment 2 Imre Deak 2018-11-22 07:43:17 UTC
Miroslaw, could you post a dmesg log booting with drm.debug=0x1e ?

I see that there's a suspend followed by a second kernel boot with the nomodeset kernel parameter. Is that some kexec thing? nomodeset will disable the i915 driver:

Nov 21 20:25:43 qq-ETP101WL64 kernel: [  117.478108] [drm:gen9_set_dc_state [i915]] Setting DC state from 01 to 00
Nov 21 20:25:43 qq-ETP101WL64 kernel: [  117.743131] PM: suspend entry (deep)
Nov 21 20:26:59 qq-ETP101WL64 kernel: [    0.000000] microcode: microcode updated early to revision 0x28, date = 2018-05-22
Nov 21 20:26:59 qq-ETP101WL64 kernel: [    0.000000] Linux version 4.20.0-994-generic (kernel@tangerine) (gcc version 8.2.0 (Ubuntu 8.2.0-9ubuntu1)) #201811202101 SMP Wed Nov 21 02:04:29 UTC 2018
Nov 21 20:26:59 qq-ETP101WL64 kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.20.0-994-generic root=UUID=c52e7968-edfb-425b-996c-93790fe96a5f ro quiet splash nomodeset vt.handoff=1
Comment 3 Miroslaw 2018-11-22 10:15:06 UTC
I think you see second boot because I had to boot device with the nomodeset parameter second time ( then screen is working but this is software mode )   to copy data log from /var/log ...because without this parameter the screen is black ( only backlight works ) .

I forgot to remove second log data from kernel.log file .
Comment 4 Jani Nikula 2018-11-22 10:53:29 UTC
(In reply to Lakshmi from comment #1)
> Can you attach cat /sys/kernel/debug/dri/0/i915_edp_psr_status

It's a MIPI DSI panel, that file is not relevant.
Comment 5 Jani Saarinen 2018-11-22 10:59:11 UTC
I see our GLK DSI on CI generally happy on BAT:
https://intel-gfx-ci.01.org/tree/drm-tip/fi-glk-dsi.html
Comment 6 Miroslaw 2018-11-22 11:31:22 UTC
This is MIPI DSI panel - yes 
Device is a tablet ..so works on battery - yes
Comment 7 Miroslaw 2018-11-22 15:52:08 UTC
Do you need more details ?
Comment 8 Imre Deak 2018-11-22 15:58:43 UTC
(In reply to Miroslaw from comment #7)
> Do you need more details ?

Could you provide the dmesg log booting with drm.debug=0x1e? Please capture the log right after booting, when the screen is blank.
Comment 9 Miroslaw 2018-11-22 23:12:36 UTC
Created attachment 142580 [details]
drm.debug=0x1e

log with param drm.debug=0x1e
Comment 10 Stanislav Lisovskiy 2018-11-23 07:15:36 UTC
Did that start to happen only with recent kernel? Can you please also attach kernel log with drm.debug with a working kernel?
Comment 11 Miroslaw 2018-11-23 09:58:42 UTC
There is no working kernel .
I tested from 4.15 up to 4.20-rc1 ... akways the same - black screen after grub ( backlight works ) .
Comment 12 Miroslaw 2018-11-23 20:23:23 UTC
Hi

Any ideas how to fix it ?
Comment 13 Jani Nikula 2018-11-26 07:21:49 UTC
One idea for debugging this:

1) boot *without* loading i915
2) get register dump using intel_reg (from the igt-gpu-tools [1])
3) modprobe i915 (presumably screen goes black at this point)
4) repeat the register dump

Alas I think intel_reg dump still falls short for MIPI DSI register dumps. Someone from our side should provide a register spec file to use with intel_reg to include all the relevant registers. (One of the reasons we're not dumping the DSI registers by default is that reading them hangs the machine if DSI isn't properly powered and clocks enabled.)

[1] https://cgit.freedesktop.org/drm/igt-gpu-tools/
Comment 14 Miroslaw 2018-11-27 01:35:52 UTC
Hi

I'm trying to compile igt-gpu-tools for debugging
but have problems with dependencies 

Dependency xmlrpc found: NO
Dependency xmlrpc_util found: NO
Dependency xmlrpc_client found: NO
Dependency xv found: NO
Program rst2man-3 found: NO

I can't find those dependencies ...
I'm trying to build it on Ubuntu 18.04 what system are you using for it ?

Thank for help
Comment 15 Jani Saarinen 2018-11-27 06:37:11 UTC
+ Petri and Arek to comment deps.
Comment 16 Jani Saarinen 2018-11-27 07:01:34 UTC
Miroslaw, have you read README.md. Does it help?
Comment 17 Miroslaw 2018-11-27 10:05:02 UTC
Reading readme was the first thing what I did .
I installed all dependencies from readme.md.

But still missing 

Dependency xmlrpc found: NO
Dependency xmlrpc_util found: NO
Dependency xmlrpc_client found: NO
Dependency xv found: NO
Program rst2man-3 found: NO

I tried installed those missing by myself but can't find it .

As I said - I'm using Ubuntu 18.04 ... maybe is not compatible. What system are you using for build this app ? .
Comment 18 Petri Latvala 2018-11-27 10:13:48 UTC
(In reply to Miroslaw from comment #14)
> Hi
> 
> I'm trying to compile igt-gpu-tools for debugging
> but have problems with dependencies 
> 
> Dependency xmlrpc found: NO
> Dependency xmlrpc_util found: NO
> Dependency xmlrpc_client found: NO
> Dependency xv found: NO
> Program rst2man-3 found: NO
> 
> I can't find those dependencies ...
> I'm trying to build it on Ubuntu 18.04 what system are you using for it ?
> 
> Thank for help


Those dependencies are for Chamelium support (xmlrpc), intel-gpu-overlay (xv) and man pages (rst2man-3).

xmlrpc in Debian and Ubuntu are old enough to not have pkg-config support. The NO you're seeing for them is not finding its pkg-config files. If those fail, the build system is using xmlrpc-config.

Overlay has two variants, with xv or with xlib.

rst2man-3 is a binary in Fedora for its python3 version. On Ubuntu, rst2man is used.

In a nutshell: All those missing dependencies are for particular variants, and even if you don't have the other variants, the disabled build artifacts are not related to the intel_reg tool.

The Debian packages that are used in gitlab CI should also work for Ubuntu, check out Dockerfile.debian.
Comment 19 Miroslaw 2018-11-28 00:40:23 UTC
Created attachment 142638 [details]
igt-gpu-tools - dump i915.modeset=0_dump.txt
Comment 20 Miroslaw 2018-11-28 00:41:06 UTC
Created attachment 142639 [details]
igt-gpu-tools - dump fully_working_gpu_driver_black_screen_dump.txt
Comment 21 Miroslaw 2018-11-28 00:48:24 UTC
I added 2 dumps from igt-gpu-tools

command : intel_reg dump 

Without loaded gpu driver and with working gpu driver.
Of course with working gpu driver I have black screen.

If you need more data please ask.
Thanks
Comment 22 Miroslaw 2018-11-29 21:15:55 UTC
So 
Any ideas ?  ;-)

Thanks
Comment 23 Jani Nikula 2018-11-30 11:54:15 UTC
Just to double check, are you booting in UEFI mode and not in legacy BIOS mode?
Comment 24 Miroslaw 2018-11-30 13:39:19 UTC
I'm sure on 100 % - booting from  UEFI
Comment 25 Miroslaw 2018-11-30 13:40:38 UTC
And no legacy BIOS mode.
Comment 26 Miroslaw 2018-12-12 14:53:03 UTC
So do I got any support about my problem ?
Comment 27 Lakshmi 2018-12-17 05:08:16 UTC
Jani, attached register dumps are helpful?
Comment 28 Jani Nikula 2018-12-19 07:42:39 UTC
(In reply to Lakshmi from comment #27)
> Jani, attached register dumps are helpful?

See comment #13.
Comment 29 Miroslaw 2018-12-21 00:08:10 UTC
(In reply to Jani Nikula from comment #28)
> (In reply to Lakshmi from comment #27)
> > Jani, attached register dumps are helpful?
> 
> See comment #13.

I did dumps and attached here ...
What's you want now  ?
Comment 30 Miroslaw 2018-12-21 00:11:53 UTC
Apart from that your team has the tablet in the hands - Etab pro .

Thanks for any solution .
Comment 31 Stanislav Lisovskiy 2018-12-27 08:58:45 UTC
Can you try the most recent drm-tip kernel? Yesterday I tried to boot from Ubuntu Live CD, the 4.15 kernel which is included obviously didn't work(blank screen as mentioned), however once I've substituted that kernel to 4.20.0-rc7, I could see the kernel boot messages and modesetting worked.
Comment 32 Stanislav Lisovskiy 2018-12-27 08:59:56 UTC
PS: I tried all mentioned above with E Tab pro.
Comment 33 Jani Saarinen 2018-12-27 10:24:42 UTC
HI,
So you are saying that latest RC7 worked on that tablet and no black screen? 

> -----Original Message-----
> From: intel-gfx-bugs [mailto:intel-gfx-bugs-bounces@lists.freedesktop.org] On
> Behalf Of bugzilla-daemon@freedesktop.org
> Sent: torstai 27. joulukuuta 2018 11.00
> To: intel-gfx-bugs@lists.freedesktop.org
> Subject: [Bug 108826] [GLK DSI] Black screen after grub - Ubuntu 18.04 - kernel
> latest tip 21.11.2018
> 
> Comment # 32 <https://bugs.freedesktop.org/show_bug.cgi?id=108826#c32>
> on bug 108826 <https://bugs.freedesktop.org/show_bug.cgi?id=108826>  from
> Stanislav Lisovskiy <mailto:stanislav.lisovskiy@intel.com>
> PS: I tried all mentioned above with E Tab pro.
> 
> ________________________________
> 
> You are receiving this mail because:
> 
> *	You are on the CC list for the bug.
> *	You are the assignee for the bug.
> *	You are the QA Contact for the bug.
Comment 34 Stanislav Lisovskiy 2018-12-27 10:52:19 UTC
I could see a modeset during boot and kernel messages as well as Ubuntu logo. It didn't boot further(couldn't find init) as I didn't update LiveCD filesystem which is squashfs, however I'm pretty sure it will boot, if I will do that. I will try to install Ubuntu to flash drive completely and then try with the recent kernel to confirm this.
Comment 35 Miroslaw 2018-12-27 19:08:41 UTC
I try the new kernel in 4th of January ...as I'm on holiday now .
Comment 36 Miroslaw 2019-01-08 00:19:11 UTC
> Stanislav Lisovskiy 2018-12-27 10:52:19 UTC
>  I could see a modeset during boot and kernel  
> messages as well as Ubuntu logo. It didn't boot 
> further (couldn't find init) as I didn't update  
> LiveCD filesystem which is squashfs, however I'm 
> pretty sure it will boot, if I will do that. I 
> will try to install Ubuntu to flash drive 
> completely and then try with the recent kernel to 
> confirm this.

Hi 

I tested full 4.20 kernel ( not rc ) 

Still black screen is like it was ... 
Nothing changed ...
Tomorrow I will test newst tlp kernel kernel .
Comment 37 Stanislav Lisovskiy 2019-01-13 20:25:53 UTC
(In reply to Miroslaw from comment #36)
> > Stanislav Lisovskiy 2018-12-27 10:52:19 UTC
> >  I could see a modeset during boot and kernel  
> > messages as well as Ubuntu logo. It didn't boot 
> > further (couldn't find init) as I didn't update  
> > LiveCD filesystem which is squashfs, however I'm 
> > pretty sure it will boot, if I will do that. I 
> > will try to install Ubuntu to flash drive 
> > completely and then try with the recent kernel to 
> > confirm this.
> 
> Hi 
> 
> I tested full 4.20 kernel ( not rc ) 
> 
> Still black screen is like it was ... 
> Nothing changed ...
> Tomorrow I will test newst tlp kernel kernel .

Ok, I will check it again then.
Comment 38 Miroslaw 2019-01-24 02:31:02 UTC
Hi 
...so did you check it again ? ... another week passed :-/
Comment 39 Stanislav Lisovskiy 2019-01-29 10:28:10 UTC
Created attachment 143247 [details]
Attached pic showing logo after grub
Comment 40 Stanislav Lisovskiy 2019-01-29 10:30:59 UTC
(In reply to Miroslaw from comment #38)
> Hi 
> ...so did you check it again ? ... another week passed :-/

Sorry, we had some severe bug to address. I checked it again - and with 4.20-rc7 I can see modeset, kernel log and Xubuntu logo after booting. I had also even attached a pics with that. Probably we need to figure out what is the difference still.
Comment 41 Stanislav Lisovskiy 2019-01-29 10:32:39 UTC
Created attachment 143248 [details]
Kernel boots after  modeset with Tux logo on E Tab
Comment 42 Miroslaw 2019-01-31 10:45:39 UTC
Ok again :) 

Look on the video with the panel "a" where we have problem 

https://streamable.com/uc5ct

And second vieo with panel "b" here is ok .

https://streamable.com/qkwjr


Only difference between them is a screen panel .


Stanislav Lisovskiy - on the early stage the screen is rotated to the left ( like on your screenshot ) but later ( after kms or initiate DRM GPU driver ) screen is rotated ( must be ) to the right .

So you see only a very early booting process ...and nothing more .

I replaced boot kernel and in the squash.sfs to 4.20... problem is still exist .

And why you're trying Kubuntu not Ubuntu ? .
Comment 43 Stanislav Lisovskiy 2019-01-31 14:26:27 UTC
Created attachment 143262 [details]
Ubuntu desktop

Just as I expected, I was able to boot into Ubuntu desktop with E Tab Pro. It required a few
tweaks like using overlay fs instead of aufs, rebuilding live cd image to use recent drm-tip kernel(basically I guess anything which starts from 4.20-rc7 would work, checked 4.20-rc7 and 5.0.0-rc3). Please see pics in the attachment. The touchscreen and mouse pointer do not work properly though, however the system is usable.
Comment 44 Jani Nikula 2019-01-31 14:45:24 UTC
(In reply to Miroslaw from comment #42)
> Ok again :) 
> 
> Look on the video with the panel "a" where we have problem 
> 
> https://streamable.com/uc5ct
> 
> And second vieo with panel "b" here is ok .
> 
> https://streamable.com/qkwjr
> 
> 
> Only difference between them is a screen panel .

Are you saying you have two models with different panels, and one of them has the problem and the other one doesn't? And presumably we've got a working model?
Comment 45 Miroslaw 2019-01-31 14:54:00 UTC
As far as I know you have "a" screen panel type .
This panel has a problem .

I tried 4.20 ( not RC ) and the panel wasn't work .
Today I try kernel 5.0 and tip so ... try to confirm it ...
Comment 46 Stanislav Lisovskiy 2019-01-31 14:57:33 UTC
(In reply to Miroslaw from comment #42)
> Ok again :) 
> 
> Look on the video with the panel "a" where we have problem 
> 
> https://streamable.com/uc5ct
> 
> And second vieo with panel "b" here is ok .
> 
> https://streamable.com/qkwjr
> 
> 
> Only difference between them is a screen panel .
> 
> 
> Stanislav Lisovskiy - on the early stage the screen is rotated to the left (
> like on your screenshot ) but later ( after kms or initiate DRM GPU driver )
> screen is rotated ( must be ) to the right .
> 
> So you see only a very early booting process ...and nothing more .
> 
> I replaced boot kernel and in the squash.sfs to 4.20... problem is still
> exist .
> 
> And why you're trying Kubuntu not Ubuntu ? .

(In reply to Miroslaw from comment #45)
> As far as I know you have "a" screen panel type .
> This panel has a problem .
> 
> I tried 4.20 ( not RC ) and the panel wasn't work .
> Today I try kernel 5.0 and tip so ... try to confirm it ...


Well for me it works, I can use Ubuntu desktop from there. I have sent a USB stick image to Ilya. Mostly the whole thing was just LiveCD tweaking, like squashfs, adding support for FUSE, OVERLAY_FS.
Comment 47 Miroslaw 2019-01-31 15:01:03 UTC
Touch screen works or not ? 
It should be only inverted.
Also rotation should works.
Can you confirm it ?
Comment 48 Miroslaw 2019-01-31 15:10:11 UTC
Just tell me if touch screen works .
If not then you have to add support for
 Gemini lake in the kernel config....because without it for me screen also works
But without GEMINI lake support rotation and touchscreen doesn't work .
Comment 49 Stanislav Lisovskiy 2019-01-31 15:30:06 UTC
(In reply to Miroslaw from comment #48)
> Just tell me if touch screen works .
> If not then you have to add support for
>  Gemini lake in the kernel config....because without it for me screen also
> works
> But without GEMINI lake support rotation and touchscreen doesn't work .

This is something new. I didn't check it. Touch screen doesn't work. As I understood from previous conversation for this panel you had only blank screen, also in the video.
Comment 50 Stanislav Lisovskiy 2019-01-31 15:32:24 UTC
(In reply to Miroslaw from comment #11)
> There is no working kernel .
> I tested from 4.15 up to 4.20-rc1 ... akways the same - black screen after
> grub ( backlight works ) .

I thought this was a problem. I see no mentioning about the touchscreen in the bug description.
Comment 51 Miroslaw 2019-01-31 15:39:37 UTC
Because touch screen is working :-) and also rotation .

Your kernel config is not proper.
Add pin ctrl for gemini lake ( we have such platform ) 
Rebuild kernel and try then .

If Gemini lake config ( pin ctrl )  is "on" everything works except screen.
But on device with "b" screen everything works including screen.
Comment 52 Jani Nikula 2019-01-31 15:41:54 UTC
Please have the exact same setup on both a and b device, add drm.debug=14 module parameter, and attach dmesg all the way from boot.
Comment 53 Stanislav Lisovskiy 2019-01-31 15:48:27 UTC
> If Gemini lake config ( pin ctrl )  is "on" everything works except screen.
> But on device with "b" screen everything works including screen.

You should have described this in the beginning.
The bug originally was:


"The screen after the grub is getting black ( backlight is still working ).  
System is booting normally - after that backlight screen is working .. and black all the time.
I can control brightness by shortcuts.
If connect HDMI cable then on the new via HDMI the screen works perfect but on the device screen is still black unfortunately .

I attached the kernel.



- edid from windows 10 

Monitor
  Model name............... WLY-10102FHD
  Windows description...... Generic PnP Monitor
  Manufacturer............. AUO
  Plug and Play ID......... AUO17D8
  Serial number............ n/a
  Manufacture date......... 2013, ISO week 11
  Filter driver............ None
  -------------------------
  EDID revision............ 1.4
  Input signal type........ Digital
  Color bit depth.......... 8 bits per primary color
  Color encoding formats... RGB 4:4:4, YCrCb 4:4:4
  Screen size.............. 140 x 220 mm (10,3 in)
  Power management......... Active off/sleep
  Extension blocs.......... None
  -------------------------
  DDC/CI................... n/a

Color characteristics
  Default color space...... sRGB
  Display gamma............ 3,55
  Red chromaticity......... Rx 0,625 - Ry 0,340
  Green chromaticity....... Gx 0,285 - Gy 0,605
  Blue chromaticity........ Bx 0,148 - By 0,063
  White point (default).... Wx 0,281 - Wy 0,309
  Additional descriptors... None



Thanks for any help."

And no mentioning about that. I'm really happy to help, however don't have telepathy skills unfortunately :)
Comment 54 Miroslaw 2019-01-31 16:17:54 UTC
Gemini lake config is on in standard Ubuntu config for 18.04 .
I didn't know you are using different config so why I had to mention about it ? 
Just make a config copy from kernel boot partition of Ubuntu 18.04...
Comment 55 Stanislav Lisovskiy 2019-01-31 16:42:03 UTC
(In reply to Miroslaw from comment #54)
> Gemini lake config is on in standard Ubuntu config for 18.04 .
> I didn't know you are using different config so why I had to mention about
> it ? 
> Just make a config copy from kernel boot partition of Ubuntu 18.04...

I just used default kernel config. To be honest it wasn't obvious to me that I have to use that one. However at least now I know. :)

I will try then enabling it, then repeat again all this sequence and tell you the results.
Comment 56 Stanislav Lisovskiy 2019-01-31 16:52:02 UTC
(In reply to Miroslaw from comment #11)
> There is no working kernel .
> I tested from 4.15 up to 4.20-rc1 ... akways the same - black screen after
> grub ( backlight works ) .

That was basically what confused me actually, I thought you had no working kernel, as of this comment.
Comment 57 Jani Nikula 2019-02-01 08:27:56 UTC
Miroslaw, please attach /sys/kernel/debug/dri/0/i915_vbt for each device type, with display a and with display b.

The VBT contains display sequences to run at specific stages of display control, including changing GPIO states. This probably conflicts with pin control.
Comment 58 Miroslaw 2019-02-01 11:39:08 UTC
I tested newest tip kernel and 5.0rc4 - black screen ...
vbt 915 logs I will attach later today .
Comment 59 Stanislav Lisovskiy 2019-02-01 11:54:46 UTC
(In reply to Miroslaw from comment #58)
> I tested newest tip kernel and 5.0rc4 - black screen ...
> vbt 915 logs I will attach later today .

It was with PINCTRL_GEMINILAKE=y I suppose? 

If so, can you try to patch intel_dsi_vbt with this patch:

diff --git a/drivers/gpu/drm/i915/intel_dsi_vbt.c b/drivers/gpu/drm/i915/intel_dsi_vbt.c
index 06a11c35a784..9b3c68a2f75c 100644
--- a/drivers/gpu/drm/i915/intel_dsi_vbt.c
+++ b/drivers/gpu/drm/i915/intel_dsi_vbt.c
@@ -371,7 +371,7 @@ static const u8 *mipi_exec_gpio(struct intel_dsi *intel_dsi, const u8 *data)
                 vlv_exec_gpio(dev_priv, gpio_source, gpio_number, value);
         else if (IS_CHERRYVIEW(dev_priv))
                 chv_exec_gpio(dev_priv, gpio_source, gpio_number, value);
-       else
+       else if (!IS_GEMINILAKE(dev_priv))
                 bxt_exec_gpio(dev_priv, gpio_source, gpio_index, value);
 
         return data;

---

With this patch from Jani, I can boot into Ubuntu desktop and PINCTRL_GEMINILAKE is turned on. However... touchscreen still doesn't work.
Comment 60 Stanislav Lisovskiy 2019-02-01 12:15:50 UTC
Also at least now I'm able to manually rotate screen and also manipulate with mouse, even though it is inverted:

https://streamable.com/at6ik
Comment 61 Miroslaw 2019-02-01 15:30:50 UTC
Created attachment 143270 [details]
kernel config for ubuntu

Strange ... touch screen and auto rotation should works at one.
Here is my config for kernel ( standard config for ubuntu 18.04 )
Comment 62 Miroslaw 2019-02-02 01:32:31 UTC
THE PATH HELPED.
The "a" screen works finally.
Also tested with "b" screen also is ok .

You should add the path to the main kernel branch .

Thanks for help
Comment 63 Jani Nikula 2019-02-05 08:09:23 UTC
Can I have the VBT and full dmesg with both panel types attached please? See comment #52 and comment #57.
Comment 64 Jani Nikula 2019-02-08 08:52:23 UTC
(In reply to Jani Nikula from comment #63)
> Can I have the VBT and full dmesg with both panel types attached please? See
> comment #52 and comment #57.

Miroslaw?
Comment 65 Miroslaw 2019-02-12 01:54:22 UTC
Sorry I'm very busy lately.
I make it tomorrow.
Comment 66 Michael Matta 2019-02-15 09:34:31 UTC
(In reply to Miroslaw from comment #65)
> Sorry I'm very busy lately.
> I make it tomorrow.

Hello Miroslaw, i'm sorry but can you please not forget to resume with the team? There is a number of users unable to get Linux on their Ideapad D330 for the same issue stated here, we are waiting for the fix patiently.
Comment 67 Mark Wynn Garcia 2019-02-17 05:24:55 UTC
Created attachment 143387 [details]
xrandr output for Lenovo D330 laptop screen
Comment 68 Mark Wynn Garcia 2019-02-17 05:29:22 UTC
Comment on attachment 143387 [details]
xrandr output for Lenovo D330 laptop screen

I've been following this bug as I have the exact device, Lenovo D330 with N5000 CPU and 1280x800 screen. https://forums.lenovo.com/t5/Linux-Discussion/Linux-on-Ideapad-D330/td-p/4296738/

I'm currently able to run vanilla Arch (4.20.8) with an external monitor without modeset and setting GRUB's gfxpayload. Still having the same problem as the others, with no display on the laptop screen but with [controllable] backlight. xrandr also is able to read the modes, please see attached file.

I've applied and tested the above patch. Unfortunately it doesn't fix the problem. There is one instance though that arch's login prompt showed for a brief moment before the screen blanking. This is with video=800x1280.
Comment 69 Mark Wynn Garcia 2019-02-17 05:46:39 UTC
Created attachment 143388 [details]
Lenovo D330 with HD screen N5000 CPU vbt

Jani, if this could also help I've attached my device's vbt.
Comment 70 Mark Wynn Garcia 2019-02-17 06:07:09 UTC
Created attachment 143389 [details]
Lenovo D330 with HD screen N5000 CPU dmesg with drm.debug=0x1e

Also dmesg with drm.debug=0x1e with no other boot parameter modifications (no nomodeset or grub gfxpayload). This is with external monitor connected, which is DP (through USB-C dongle probably converting USB-C DP alternate mode to HDMI). Laptop screen is DSI.

Additional details with laptop screen, Windows 10 detects an "active signal resolution" of 800x1280 but weirdly @ ~75 hz (which isn't included in the xrandr output). Sorry I won't be able to give more Windows 10 info as I nuked everything when I installed arch.
Comment 71 Mark Wynn Garcia 2019-02-17 07:50:15 UTC
Created attachment 143390 [details]
D330 dmesg unpatched 4.20.8

Sorry for previous dmesg attachment. Here's the proper one, with unpatched kernel v 4.20.8 from arch.
Comment 72 Mark Wynn Garcia 2019-02-17 07:51:18 UTC
Created attachment 143391 [details]
D330 dmesg patched 4.20.8

And here's for the patch, on same base kernel version.
Comment 73 Jani Nikula 2019-02-20 10:21:51 UTC
I don't know what made anyone think this bug has anything to do with Lenovo D330. AFAIK the report is *not* about Lenovo D330.

If the patch that helps the original reporter does not help you, it's also a clue you have a different bug. Please file a different bug.

Miroslaw, we're still waiting for the details from you.
Comment 74 Miroslaw 2019-02-21 01:54:43 UTC
Here you go 

kernel_5.0-rc4-pathed--screen_a
https://pastebin.com/0qg18CMi

kernel_5.0-rc4-no-pathed--screen_a
https://pastebin.com/EvCUPsBa

kernel_5.0-rc4-pathed_screen_b
https://pastebin.com/CCzLsPX1

kernel_5.0-rc4-not-pathed-screen_b
https://pastebin.com/Y2jAV6UV


I remind :
The same device with 2 different screens

Ssreen a - had a problem  after kms with a "blank screen" .. path solved it
Screen b - is ok no problems at all

If you need more data just ask .
Comment 75 Lakshmi 2019-02-22 11:43:53 UTC
Based on the Comment 66, priority of this bug is set to Highest as many users are unable to get Linux on  Ideapad D330.
Comment 76 Jani Nikula 2019-02-25 11:02:19 UTC
(In reply to Lakshmi from comment #75)
> Based on the Comment 66, priority of this bug is set to Highest as many
> users are unable to get Linux on  Ideapad D330.

Please see comment #73 and reconsider. File a new bug for D330, this is not the one.
Comment 77 Lakshmi 2019-02-25 11:18:24 UTC
(In reply to Mark Wynn Garcia from comment #68)
> Comment on attachment 143387 [details]
> xrandr output for Lenovo D330 laptop screen
> 
> I'm currently able to run vanilla Arch (4.20.8) with an external monitor
> without modeset and setting GRUB's gfxpayload. Still having the same problem
> as the others, with no display on the laptop screen but with [controllable]
> backlight. xrandr also is able to read the modes, please see attached file.

Can you please file a new bug for this case? That will help and speed up the investigation.
Comment 78 Danni Uptlen 2019-02-26 23:35:32 UTC
To stop any further messing with the thread, D330 bug has been filed already at:
https://bugs.freedesktop.org/show_bug.cgi?id=109267
Comment 79 Jani Nikula 2019-03-08 11:57:46 UTC
Created attachment 143589 [details]
kernel_5.0-rc4-no-pathed--screen_a.txt

Upload from comment #74.
Comment 80 Jani Nikula 2019-03-08 11:58:08 UTC
Created attachment 143590 [details]
kernel_5.0-rc4-not-pathed-screen_b.txt
Comment 81 Jani Nikula 2019-03-08 11:58:32 UTC
Created attachment 143591 [details]
kernel_5.0-rc4-pathed--screen_a.txt
Comment 82 Jani Nikula 2019-03-08 11:58:52 UTC
Created attachment 143592 [details]
kernel_5.0-rc4-pathed_screen_b.txt
Comment 83 Jani Nikula 2019-03-08 12:01:25 UTC
(In reply to Miroslaw from comment #74)
> Here you go 
> 
> kernel_5.0-rc4-pathed--screen_a
> https://pastebin.com/0qg18CMi
> 
> kernel_5.0-rc4-no-pathed--screen_a
> https://pastebin.com/EvCUPsBa
> 
> kernel_5.0-rc4-pathed_screen_b
> https://pastebin.com/CCzLsPX1
> 
> kernel_5.0-rc4-not-pathed-screen_b
> https://pastebin.com/Y2jAV6UV
> 
> 
> I remind :
> The same device with 2 different screens
> 
> Ssreen a - had a problem  after kms with a "blank screen" .. path solved it
> Screen b - is ok no problems at all
> 
> If you need more data just ask .

Miroslaw, please attach /sys/kernel/debug/dri/0/i915_vbt for each device type, with display a and with display b.

The VBT contains display sequences to run at specific stages of display control, including changing GPIO states. This probably conflicts with pin control.

For future reference, please *attach* all logs and binaries etc. instead of using pastebin. The pastebins will go away eventually.
Comment 84 Miroslaw 2019-04-05 00:10:01 UTC
Created attachment 143866 [details]
panel a i915_vbt
Comment 85 Miroslaw 2019-04-05 00:10:46 UTC
Created attachment 143867 [details]
panel b i915_vbt
Comment 86 Miroslaw 2019-04-05 00:12:32 UTC
Created attachment 143868 [details]
full drm/0 panel a
Comment 87 Miroslaw 2019-04-05 00:13:12 UTC
Created attachment 143869 [details]
full drm/0 panel b
Comment 88 Miroslaw 2019-04-05 00:24:14 UTC
Hi

Sorry I answer so late but I was very busy lately.
I attach i915_vbt  ... but looks exactly identical.
So I also attach whole folders dri/0 for both panels.

That not working properly panel "a" works ok now with the path ... until I sleep device...when I wake up device the screen is totally black not even backlight works only restart device helps ... until I sleep device again...
I have the same result on panel "b" ( with that path but panel do not need it - just for test )...  waking up device from sleep  - ... only black screen.


Without the path:
- panel "a" only works until kernel starts loading drm driver then is black but backlight works.
- panel "b" - everything is ok.. no problems.
Comment 89 Jani Saarinen 2019-04-05 06:52:05 UTC
Please also notice (if using rc1) https://bugs.freedesktop.org/show_bug.cgi?id=109516 currently DSI systems in CI broken too.
Comment 90 Miroslaw 2019-04-05 22:45:44 UTC
So ...
You even have this tablet ( device ) and still now solved it.

Have any idea how to fix it permanently ? 
Screen works only when GEMINILAKE config is is off ... 
But we can't awake the screen after sleep system - s3/s4 state ( ubuntu / android ).
Comment 91 Mark Wynn Garcia 2019-04-07 02:06:38 UTC
Looking at Miroslaw's VBT files, looks like another case of "PPS GPIO Pins: Using PMIC". Is there any way for Intel devs to know what Windows and its iGPU driver does right with these hardware?
Comment 92 Lakshmi 2019-04-10 07:24:55 UTC
Jani N, any further comments here?
Comment 93 Microtech 2019-04-15 19:17:35 UTC
(In reply to Jani Nikula from comment #83)
> (In reply to Miroslaw from comment #74)
> > Here you go 
> > 
> > kernel_5.0-rc4-pathed--screen_a
> > https://pastebin.com/0qg18CMi
> > 
> > kernel_5.0-rc4-no-pathed--screen_a
> > https://pastebin.com/EvCUPsBa
> > 
> > kernel_5.0-rc4-pathed_screen_b
> > https://pastebin.com/CCzLsPX1
> > 
> > kernel_5.0-rc4-not-pathed-screen_b
> > https://pastebin.com/Y2jAV6UV
> > 
> > 
> > I remind :
> > The same device with 2 different screens
> > 
> > Ssreen a - had a problem  after kms with a "blank screen" .. path solved it
> > Screen b - is ok no problems at all
> > 
> > If you need more data just ask .
> 
> Miroslaw, please attach /sys/kernel/debug/dri/0/i915_vbt for each device
> type, with display a and with display b.
> 
> The VBT contains display sequences to run at specific stages of display
> control, including changing GPIO states. This probably conflicts with pin
> control.
> 
> For future reference, please *attach* all logs and binaries etc. instead of
> using pastebin. The pastebins will go away eventually.

Hi Jani, I write for the first time because I would like to say thanks you to you and your colleagues for the work you did until now. 
I ask you a little additional effort because the tablet still don't work properly, since there is some pending issue. You have this device in your hands, I think, so you can debug it easily because you can test everything. 
Please help us to close this ticket. Now we really need to close it because we are stopped on this project from December and we can't go ahead.
Comment 94 Miroslaw 2019-04-15 23:53:52 UTC
Stanislav Lisovskiy and Jani Nikula

You're Intel devs ...why you still not solved it ( who will do that if you not )? 

You have that tablet in you hands and have skill to fix it.
Please help us with it
Comment 95 Stanislav Lisovskiy 2019-04-16 11:36:49 UTC
(In reply to Miroslaw from comment #62)
> THE PATH HELPED.
> The "a" screen works finally.
> Also tested with "b" screen also is ok .
> 
> You should add the path to the main kernel branch .
> 
> Thanks for help

Hi again Miroslaw. To be honest, I stopped following this bug(we have plenty of other stuff also) after this comment above you made. I thought everything was fine after this. 

Can you please summarize again what doesn't work for you, because I thought everything worked fine as mentioned that "patch solved it". 

Need now again to grab this E-Tab back to my table..

Do I understand correctly that now you have a different issue related to suspend/resume?

Jani Nikula: did you find anything suspicious from i915_vbt logs that you requested?
Comment 96 Miroslaw 2019-04-16 19:36:29 UTC
Panel "a" works ok now with the path ... until I sleep device ( Android or Linux ) ...when I wake up device the screen is totally black even backlight no works - only restart device helps ... until I sleep device again...
I have the same result on panel "b" ( with that path but panel do not need it - just for test )...  waking up device from sleep  - ... only black screen..( when path is applied ) 

Summarize: 

Without the path:
- panel "a" only works until kernel starts loading drm driver then is black but backlight works.
- panel "b" - everything is ok.. no problems.

With the path
- panel "a" works until you sleep device ( s3 or s4 for instance  ) then you have totally black screen - even backlight not working.


- panel "b" works until you sleep device ( s3 or s4 for instance  ) then you have totally black screen - even backlight not working.
Comment 97 Stanislav Lisovskiy 2019-04-17 08:27:58 UTC
(In reply to Miroslaw from comment #96)
> Panel "a" works ok now with the path ... until I sleep device ( Android or
> Linux ) ...when I wake up device the screen is totally black even backlight
> no works - only restart device helps ... until I sleep device again...
> I have the same result on panel "b" ( with that path but panel do not need
> it - just for test )...  waking up device from sleep  - ... only black
> screen..( when path is applied ) 
> 
> Summarize: 
> 
> Without the path:
> - panel "a" only works until kernel starts loading drm driver then is black
> but backlight works.
> - panel "b" - everything is ok.. no problems.
> 
> With the path
> - panel "a" works until you sleep device ( s3 or s4 for instance  ) then you
> have totally black screen - even backlight not working.
> 
> 
> - panel "b" works until you sleep device ( s3 or s4 for instance  ) then you
> have totally black screen - even backlight not working.

Can you please share your kernel config, that you use(which works)? Or I see there is one in attachment - can I use that one?
Comment 98 Miroslaw 2019-04-17 08:41:12 UTC
Yes I'm using that config from the attachment I provided.
Make sure Gemini lake pin config is active .
Thanks for help .
Comment 99 Jani Nikula 2019-04-18 09:13:02 UTC
The VBT blocks for the two panels are identical. Are the specs for the two panels identical?

The VBT contains lots of configuration for the panel DPHY, initialization and enable/disable sequences. Are the requirements for the two panels identical?

Has the VBT DSI configuration been tailored for the platform, board and panels? The sequences contain GPIO toggles and DSI DCS commands. Any generic VBT will not work.

What is the origin of the VBT configuration? Did someone provide it to you or did you use the BMP tool to adjust and generate it?
Comment 100 Miroslaw 2019-04-20 06:37:45 UTC
We are using standard vbt config like kernel provides nothing more.
Problem exist only on panel "a" ..panel "b" is ok.

On windows panel "a" works ok like panel "b".
Problem exist only in Linux / Android .
I remind that you have that device so you can make any tests as you needs.

Cheers


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.