Red Hat Bugzilla – Bug 991707
Intel HD 4000 support regression
Last modified: 2013-10-08 12:31:54 EDT
Created attachment 782394 [details]
X log file
Description of problem:
Intel(R) Core(TM) i5-3570K
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
In Fedora 17, I could play video without screen tearing.
In Fedora 19, I cannot. The problem seems to be that the hardware is no longer being used directly.
Version-Release number of selected component (if applicable):
Fedora 19 with all updates applied.
Steps to Reproduce:
1. Install fedora 19 on a working system.
2. Try to play a video.
Watch a video stutter that a 10 year old cellphone could play smoothly.
Video play without screen tearing.
X-Video Extension version 2.2
no adaptors present
glxinfo | grep -i render
direct rendering: Yes
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 256 bits)
GL_NV_conditional_render, GL_NV_fog_distance, GL_NV_light_max_exponent,
After the failure with stock Fedora 19, I tried installing the latest intel drivers from here https://01.org/linuxgraphics/downloads/2013/intelr-linux-graphics-installer-version-1.0.2. Nothing changed.
In the attached X log you will see
open /dev/dri/card0: No such file or directory
[ 3.554] (WW) Falling back to old probe method for fbdev
[ 3.554] (II) Loading sub module "fbdevhw"
So there seems to be a problem recognizing the hardware, but there was no problem in Fedora 17.
I found a magic kernel incantation that fixes the problem. If I manually edit the kernel parameters to include "i915.modeset=1", Xorg runs as expected.
glxinfo | grep -i render
direct rendering: Yes
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop
GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_packed_depth_stencil,
GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_light_max_exponent,
I added the setting to a modprobe.d config file so hopefully I'm set.
I have a work around, but the issue is that Fedora should automatically figure out the right thing to do.
Could you attach the output of dmesg, so we can see what is on your kernel command line?
In Bug 986620, Comment 7, I noted that you were booting with nomodeset on the kernel command-line, so it seems like you are overriding that:
$ modinfo i915 | grep modeset
parm: modeset:Use kernel modesetting [KMS] (0=DRM_I915_KMS from .config, 1=on, -1=force vga console preference [default]) (int)
The kernel command-line arguments are configurable in /etc/default/grub.
After making changes to GRUB_CMDLINE_LINUX in /etc/default/grub, run:
$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
(It is probably a good idea to make a backup of grub.cfg first ...)
After that, reboot to see what you got ...
$ info grub2
$ rpm -qa 'grub2*' | sort
The kernel command-line has nomodeset on it.
Have you tried removing it with kernel 3.10.4-300?
Snippet from attached Xorg.0.log:
[ 3.538] Current Operating System: Linux localhost.localdomain 3.10.4-300.fc19.x86_64 #1 SMP Tue Jul 30 11:29:05 UTC 2013 x86_64
[ 3.538] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.4-300.fc19.x86_64 root=/dev/sda4 ro rootflags=subvol=root nomodeset rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 rhgb quiet LANG=en_US.UTF-8
I've previously tried removing nomodeset (not sure which kernel). Every time I get a garbled screen on boot and I can't switch virtual terminals.
Right now all the updates are applied and I am running kernel 3.10.5-201.
Created attachment 788112 [details]
Kernel-3.9.5 Xorg log
Gamaliel: Could you attach the output from dmesg and lspci too?
$ dmesg > dmesg-1.log
Also, could you please update your system:
$ sudo yum update
This is the install kernel:
[ 52.748] Current Operating System: Linux ETI-Saturn 3.9.5-301.fc19.x86_64 #1 SMP Tue Jun 11 19:39:38 UTC 2013 x86_64
The latest kernel is:
$ sudo repoquery kernel
Created attachment 788203 [details]
Xorg log 3.10.7 blind
I add the 3.10.7 xorg.log blindly, as well as the one with nomodeset. Without nomodeset, I cannot see anything, not even the plymouth bootscreen: the only thing working is the backlight. With nomodeset, I can see plymouth, but never boot into Xorg multi-user, I can only use getty. Contrast this with the 3.9.5 Xorg.
Created attachment 788204 [details]
Xorg log 3.10.7 nomodeset
Created attachment 788205 [details]
Created attachment 788206 [details]
Created attachment 788207 [details]
Thanks, Gamaliel. That's very helpful.
Did you try Mark's workaround: "i915.modeset=1"? (Comment 1)
The kernel command-line arguments are configurable in /etc/default/grub. (Comment 2)
Your dmesg shows:
[ 0.125562] smpboot: CPU0: Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz (fam: 06, model: 3a, stepping: 09)
The Intel web site shows:
Processor Graphics Intel® HD Graphics 4000
The lspci output is not so informative:
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
This might show more:
$ lspci -s 00:02.0 -vv -nn
Created attachment 788209 [details]
Lspci -s 00:02.0 -vv -nn 3.9.5
Created attachment 788210 [details]
Lspci -s 00:02.0 -vv -nn 3.10.7 nomodeset
Tried the i915.modeset=1, without success. I have to try to do it blindly again, with a reinstalled grub2. Will post later.
Thanks for the updated lspci output:
00:02.0 VGA compatible controller : Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:103d]
Kernel driver in use: i915
grub2-mkconfig just rebuilds the grub2 menu that you see when you boot and are given a list of kernels to boot. It does not reinstall grub2.
I believe Mark has *both* "nomodeset" and "i915.modeset=1" (Comment 1, Comment 2). He set "i915.modeset=1" in a /etc/modprobe.d/ config file, but I believe you could put both on the kernel command-line. To always boot with those options,
edit /etc/default/grub and run grub2-mkconfig (Comment 2).
Yes. I have both nomodeset and i915.modeset=1 set. When I have access to that machine again in a couple days, I will see if just the i915 setting alone works.
Let me know if any additional testing or information would help.
(In reply to Steve Tyler from comment #17)
> Thanks for the updated lspci output:
> 00:02.0 VGA compatible controller : Intel Corporation 3rd Gen Core
> processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA
> Subsystem: ASUSTeK Computer Inc. Device [1043:103d]
> Kernel driver in use: i915
> grub2-mkconfig just rebuilds the grub2 menu that you see when you boot and
> are given a list of kernels to boot. It does not reinstall grub2.
> I believe Mark has *both* "nomodeset" and "i915.modeset=1" (Comment 1,
> Comment 2). He set "i915.modeset=1" in a /etc/modprobe.d/ config file, but I
> believe you could put both on the kernel command-line. To always boot with
> those options,
> edit /etc/default/grub and run grub2-mkconfig (Comment 2).
(In reply to Mark Patton from comment #18)
> Yes. I have both nomodeset and i915.modeset=1 set. When I have access to
> that machine again in a couple days, I will see if just the i915 setting
> alone works.
> Let me know if any additional testing or information would help.
Thanks for clarifying that. It might be useful to have a photo of any display corruption you see.
These two posts show horizontal black lines:
Garbage screen with Intel Linux Graphics Installer + Ubuntu 12.04.2 64 bits + Samsung NP900X3E-A02US (HD 4000)
Display bug on Samsung Series 9 under X
Created attachment 789418 [details]
Lspci -s 00:02.0 -vv -nn log 3.10.7 (with KMS).
I found two or three things. First, my computer is an ASUS Taichi 21. As you may know, this laptop has two screens, one in the front, and a touchscreen in the back. I have never had any success configuring the back screen, especially its backlight, which never seems to map correctly to the brightness, and thus is always dark and unusable. Today, when trying to log in blindly, I looked at the back screen and there was output in it! All dark and barely noticeable, of course, but the Crypto-password thingy from plymouth was there. However, after I gave the password, both screens showed 0 output. This means that it is trying to configure the wrong screen on my setup (the bad touchscreen one instead of my real monitor).
Then, I booted Sabayon 13.08 with kernel 3.10, and it also opened the screen properly! Only that in Sabayon, the touchscreen was never recognized, and the display never appeared. So this may just be a particular configuration bug.
It seems to be more like an Xorg-based problem, don't you think?
Created attachment 789419 [details]
Xorg 3.10.7 (With KMS)
These logs, including the KMS lscpi one, were done by writing on paper the commands and logging via a getty console "blindly". No output was ever seen in the screen.
I boot from 3.9.5 to use my computer, and it recognizes everything but the back-screen's backlight.
I booted with only i915.modeset=1 and X ran perfectly. The corruption I see without that kernel parameter doesn't look like the cases linked. I'm out the door so don't have time to take a picture. IIRC most of the screen was black with a colored wavy pattern at the top.
(In reply to Steve Tyler from comment #19)
> (In reply to Mark Patton from comment #18)
> > Yes. I have both nomodeset and i915.modeset=1 set. When I have access to
> > that machine again in a couple days, I will see if just the i915 setting
> > alone works.
> > Let me know if any additional testing or information would help.
> Thanks for clarifying that. It might be useful to have a photo of any
> display corruption you see.
> These two posts show horizontal black lines:
> Garbage screen with Intel Linux Graphics Installer + Ubuntu 12.04.2 64 bits
> + Samsung NP900X3E-A02US (HD 4000)
> Display bug on Samsung Series 9 under X
Got another solution:
Just remove "nomodeset" from the kernel bootline and add "acpi_osi=Linux acpi_backlight=vendor" to its end.
My bootline looks like this:
linux /vmlinuz-3.10.7-200.fc19.x86_64 root=/dev/mapper/rfremix-root ro rd.lvm.lv=rfremix/root rd.md=0 rd.dm=0 rd.lvm.lv=rfremix/swap rd.luks=0 vconsole.keymap=us vconsole.font=latarcyrheb-sun16 rhgb quiet acpi_osi=Linux acpi_backlight=vendor
This also fixes "black screen on boot" issue and enables the backlight keys on a keyboard. Video performance is as expected - just fine :)
My system is similar as topic starter's one - Intel i5 Evy Bridge with HD4000 video. Fresh install of Fedora 19.
Hope this helps.
*********** MASS BUG UPDATE **************
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.
Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.