Bug 79146

Summary: [IVB eDP] i3-3227U's HD4000 fails to work
Product: DRI Reporter: Shen Li <etkids>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: critical    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmsg with drm.debug=6
none
dmesg without nomodeset on kernel 3.15-rc8 none

Description Shen Li 2014-05-23 17:53:56 UTC 
The model of my laptop is Acer V7-481 which comes with an [B]i3-3227U[/B] CPU and [B]NO[/B] graphic card.

When I was installing ubuntu 12.04 for the first time, the laptop booted up in a black screen

The only solution to this is to add a boot parameter nomodeset or something to disable the KMS.

Other solutions I found are useless, including acpi related and adjust the backlight using shortcuts etc.


Now, my laptop can ONLY boot with NOMODESET but I don't think the integrated graphic card is functioning normally.

NOTE:This happens on distros that doesn't have a GUI

1. I cannot connect to a second monitor via HDMI and Display Port
2. unity is running in 2d mode
3. can't use 3d hardware acceleration
4. cannot change backlight with shortcuts

The back light is on without nomodeset and can be adjusted by keyboard shortcut

however, with nomodest, I can't change the back light.

out put of `uname -a`

`Linux v7 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux`

out put of `lshw -c video`

```
*-display UNCLAIMED     
   description: VGA compatible controller
   product: 3rd Gen Core processor Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@0000:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list
   configuration: latency=0
   resources: memory:c0000000-c03fffff memory:b0000000-bfffffff ioport:3000(size=64)
```
Comment 1 Chris Wilson 2014-05-25 11:56:04 UTC 
What we need is the drm.debug=6 dmesg (append drm.debug=6 to the kernel command line in grub) for the faulty boot with KMS enabled. Please also use a recent kernel, 3.14 or preferrably a 3.15-rc to be closer to upstream wrt bugfixes.
Comment 2 Shen Li 2014-05-25 12:56:09 UTC 
Created attachment 99765 [details]
dmsg with drm.debug=6

This is a text file that contains the information you required.
Comment 3 Jani Nikula 2014-05-27 11:10:51 UTC 
Please try video.use_native_backlight=1 module parameter.
Comment 4 Shen Li 2014-05-27 13:00:46 UTC 
(In reply to comment #3)
> Please try video.use_native_backlight=1 module parameter.

Well after add this to grub, I still can't get it work without nomodeset.
Actually, this parameter disabled the shortcuts that was able to change the backlight without nomodeset
Comment 5 Jani Nikula 2014-05-27 13:21:02 UTC 
If you drop all the extra kernel/module parameters, incl. nomodeset, what do you have in /sys/class/backlight? Can you enable backlight by echoing the value in max_brightness to brightness? Is the backlight the only thing that fails?
Comment 6 Shen Li 2014-05-27 13:26:00 UTC 
(In reply to comment #5)
> If you drop all the extra kernel/module parameters, incl. nomodeset, what do
> you have in /sys/class/backlight? Can you enable backlight by echoing the
> value in max_brightness to brightness? Is the backlight the only thing that
> fails?

well, without nomodeset I can see nothing but a grey screen, the backlight of  which can be adjusted.
However, with nomodeset, I can't adjust the backlight
Comment 7 Jani Nikula 2014-05-27 14:19:06 UTC 
(In reply to comment #6)
> (In reply to comment #5)
> > If you drop all the extra kernel/module parameters, incl. nomodeset, what do
> > you have in /sys/class/backlight? Can you enable backlight by echoing the
> > value in max_brightness to brightness? Is the backlight the only thing that
> > fails?
> 
> well, without nomodeset I can see nothing but a grey screen, the backlight
> of  which can be adjusted.
> However, with nomodeset, I can't adjust the backlight

Ah. We don't support nomodeset for your hardware, so the backlight is not the issue. The issue is getting something on screen.
Comment 8 Shen Li 2014-05-29 01:34:38 UTC 
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #5)
> > > If you drop all the extra kernel/module parameters, incl. nomodeset, what do
> > > you have in /sys/class/backlight? Can you enable backlight by echoing the
> > > value in max_brightness to brightness? Is the backlight the only thing that
> > > fails?
> > 
> > well, without nomodeset I can see nothing but a grey screen, the backlight
> > of  which can be adjusted.
> > However, with nomodeset, I can't adjust the backlight
> 
> Ah. We don't support nomodeset for your hardware, so the backlight is not
> the issue. The issue is getting something on screen.

So, does this mean that I have to wait for another update to get my graphic to work normally?
I know the backlight is not an issue and I don't care much about that, but using nomodeset is the only way to get something on screen, in which way the graphic is pretty slow.
Comment 9 Jani Nikula 2014-06-02 14:10:11 UTC 
(In reply to comment #8)
> So, does this mean that I have to wait for another update to get my graphic
> to work normally?
> I know the backlight is not an issue and I don't care much about that, but
> using nomodeset is the only way to get something on screen, in which way the
> graphic is pretty slow.

Now we'll need to debug why there's nothing on screen. The first suggestion from Chris was to try a recent kernel, preferrably 3.15-rc8, and paste the dmesg with drm.debug=0xe module parameter running that.
Comment 10 Jani Nikula 2014-06-02 14:10:36 UTC 
(In reply to comment #9)
> dmesg with drm.debug=0xe module parameter running that.

or drm.debug=6 as long as the kernel is new.
Comment 11 Shen Li 2014-06-03 16:13:22 UTC 
Created attachment 100362 [details]
dmesg without nomodeset on kernel 3.15-rc8
Comment 12 Shen Li 2014-06-03 16:16:49 UTC 
(In reply to comment #11)
> Created attachment 100362 [details]
> dmesg without nomodeset on kernel 3.15-rc8

Hi, I updated the kernel to 3.15-rc8(which can't fix this problem) and posted the dmesg info as an attachment.
I hope that helps.
Comment 13 Shen Li 2014-08-10 16:43:57 UTC 
Well, just FYI, I've updated the kernel to the most up-to-date beta version, and this problem still exists
Comment 14 Shen Li 2014-11-14 22:09:52 UTC 
I updated the kernel to 3.18 rc4. And now it works fine.
I didn't try 3.17 though
Comment 15 Daniel Vetter 2014-11-18 10:25:30 UTC 
Thanks a lot for this bug report and the testing feedback, closing this one. If you want you could attempt a reverse bisect and if it's just a small patch we could backport it. But given that 3.18 will release soonish probably not worth the effort.

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.