Created attachment 92965 [details] logs Chipset: i915 Arch: AMD64 XOrg version: xorg-server 2:1.14.3-3ubuntu2 Xf86-intel version: compiled for 1.14.5, module version = 2.99.904 MESA version 1.4 kernel: 3.11.0-12-generic Linux Distro: Ubuntu, same problem in Linux Mint, Fedora and OpenSuse Machine: Dell 3737 17 inch laptop Intel 4400 graphics, 4th Gen Core i5 4200U Display: laptop display, 17 incxorh, 1600x900 Easy to reproduce, happens with all modern distributions listed above Attached: Xorg log dmesg xrandr intel_reg_dumper output Colors seem to be inverted, and screen is blurry. Did not happen with OEM windows 8, but happens during linux install even after newest drivers from 01.org.
Just to try something completely insane: xrandr --output eDP1 --set audio off
xrandr --output eDP1 --set audio off had no effect. additionally I checked the hdmi port it operates correctly
Created attachment 93762 [details] Script to enable/disable pipe CSC Hmm. I wonder if the pipe CSC is misbehaving somehow. I'm not sure why it would do that for some displays only, but let's give try it anyway shall we. So just run the script like so to turn off the pipe CSC for all pipes: # pipe_csc.sh a disable # pipe_csc.sh b disable # pipe_csc.sh c disable
I also have a Dell 3737 with an Intel 4400 graphics card, and I observe the same symptoms running Xubuntu 13.10 with linux-3.11.0-15-generic. Reds show up as green, blues are purple, and the display is pixellated. Running the proposed pipe_csc.sh commands as root does not change the display appearance. I can try other commands or provide more data if it helps. Thanks! Antoine
Try running nomodeset and quiet splash grub options.. On Feb 13, 2014 8:42 PM, <bugzilla-daemon@freedesktop.org> wrote: > *Comment # 4 <https://bugs.freedesktop.org/show_bug.cgi?id=74167#c4> on > bug 74167 <https://bugs.freedesktop.org/show_bug.cgi?id=74167> from Antoine > le Bret <antoine_le_bret@yahoo.ca> * > > I also have a Dell 3737 with an Intel 4400 graphics card, and I observe the > same symptoms running Xubuntu 13.10 with linux-3.11.0-15-generic. > > Reds show up as green, blues are purple, and the display is pixellated. > > Running the proposed pipe_csc.sh commands as root does not change the display > appearance. I can try other commands or provide more data if it helps. > > Thanks! > Antoine > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
Booting linux with "nomodeset quiet splash" gives me better-looking consoles, but no graphical interface. This error briefly flashes on the screen: ---------- [ 12.193723] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart modu le. [ 12.193796] DRM: Fill_in_dev failed. ---------- Then dmesg tells me there was some unhappiness in the i915 driver: ---------- [ 12.278015] HDA driver get symbol successfully from i915 module [ 12.278021] ------------[ cut here ]------------ [ 12.278050] WARNING: CPU: 2 PID: 78 at /build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_pm.c:5098 i915_request_power_well+0x77/0x80 [i915]() [ 12.278078] Modules linked in: snd_hda_intel(+) snd_hda_codec snd_hwdep snd_pcm dell_laptop dcdbas arc4 snd_page_alloc ath9k snd_seq_midi snd_seq_midi_event ath9k_common ath9k_hw snd_rawmidi ath snd_seq microcode(+) mac80211 i915 ath3k(+) btusb psmouse bluetooth serio_raw snd_seq_device drm_kms_helper cfg80211 drm snd_timer mei_me snd i2c_algo_bit mei lpc_ich wmi soundcore lp parport mac_hid video ahci r8169 libahci mii [ 12.278082] CPU: 2 PID: 78 Comm: kworker/2:1 Not tainted 3.11.0-15-generic #25-Ubuntu [ 12.278083] Hardware name: Dell Inc. Inspiron 3737/0C6PRJ, BIOS A07 11/12/2013 [ 12.278091] Workqueue: events azx_probe_work [snd_hda_intel] [ 12.278095] 0000000000000009 ffff880155067d58 ffffffff816e7375 0000000000000000 [ 12.278099] ffff880155067d90 ffffffff81061dcd ffff88015551c228 0000000000000000 [ 12.278102] 0000000000000000 ffff88015551c000 0000000000000080 ffff880155067da0 [ 12.278103] Call Trace: [ 12.278111] [<ffffffff816e7375>] dump_stack+0x45/0x56 [ 12.278117] [<ffffffff81061dcd>] warn_slowpath_common+0x7d/0xa0 [ 12.278121] [<ffffffff81061eaa>] warn_slowpath_null+0x1a/0x20 [ 12.278145] [<ffffffffa02a5407>] i915_request_power_well+0x77/0x80 [i915] [ 12.278152] [<ffffffffa04beb22>] hda_display_power+0x32/0x40 [snd_hda_intel] [ 12.278157] [<ffffffffa04bd505>] azx_probe_continue+0x45/0x940 [snd_hda_intel] [ 12.278162] [<ffffffff810913c0>] ? finish_task_switch+0x50/0xf0 [ 12.278168] [<ffffffffa04be8d5>] azx_probe_work+0x15/0x20 [snd_hda_intel] [ 12.278172] [<ffffffff8107cfec>] process_one_work+0x17c/0x430 [ 12.278176] [<ffffffff8107dfac>] worker_thread+0x11c/0x3c0 [ 12.278179] [<ffffffff8107de90>] ? manage_workers.isra.25+0x2a0/0x2a0 [ 12.278183] [<ffffffff81084740>] kthread+0xc0/0xd0 [ 12.278187] [<ffffffff81084680>] ? kthread_create_on_node+0x120/0x120 [ 12.278193] [<ffffffff816f71ac>] ret_from_fork+0x7c/0xb0 [ 12.278197] [<ffffffff81084680>] ? kthread_create_on_node+0x120/0x120 [ 12.278200] ---[ end trace 21db90331deffc67 ]---
(In reply to comment #6) > Booting linux with "nomodeset quiet splash" gives me better-looking > consoles, but no graphical interface. This error briefly flashes on the > screen: > > ---------- > [ 12.193723] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart > modu > le. > [ 12.193796] DRM: Fill_in_dev failed. > ---------- These are just hallmarks of nomodeset. i915 won't initialize at all with that option. > [ 12.278015] HDA driver get symbol successfully from i915 module > [ 12.278021] ------------[ cut here ]------------ > [ 12.278050] WARNING: CPU: 2 PID: 78 at > /build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_pm.c:5098 > i915_request_power_well+0x77/0x80 [i915]() > [ 12.278078] Modules linked in: snd_hda_intel(+) snd_hda_codec snd_hwdep > snd_pcm dell_laptop dcdbas arc4 snd_page_alloc ath9k snd_seq_midi > snd_seq_midi_event ath9k_common ath9k_hw snd_rawmidi ath snd_seq > microcode(+) mac80211 i915 ath3k(+) btusb psmouse bluetooth serio_raw > snd_seq_device drm_kms_helper cfg80211 drm snd_timer mei_me snd i2c_algo_bit > mei lpc_ich wmi soundcore lp parport mac_hid video ahci r8169 libahci mii > [ 12.278082] CPU: 2 PID: 78 Comm: kworker/2:1 Not tainted > 3.11.0-15-generic #25-Ubuntu > [ 12.278083] Hardware name: Dell Inc. Inspiron 3737/0C6PRJ, BIOS A07 > 11/12/2013 > [ 12.278091] Workqueue: events azx_probe_work [snd_hda_intel] > [ 12.278095] 0000000000000009 ffff880155067d58 ffffffff816e7375 > 0000000000000000 > [ 12.278099] ffff880155067d90 ffffffff81061dcd ffff88015551c228 > 0000000000000000 > [ 12.278102] 0000000000000000 ffff88015551c000 0000000000000080 > ffff880155067da0 > [ 12.278103] Call Trace: > [ 12.278111] [<ffffffff816e7375>] dump_stack+0x45/0x56 > [ 12.278117] [<ffffffff81061dcd>] warn_slowpath_common+0x7d/0xa0 > [ 12.278121] [<ffffffff81061eaa>] warn_slowpath_null+0x1a/0x20 > [ 12.278145] [<ffffffffa02a5407>] i915_request_power_well+0x77/0x80 [i915] > [ 12.278152] [<ffffffffa04beb22>] hda_display_power+0x32/0x40 > [snd_hda_intel] > [ 12.278157] [<ffffffffa04bd505>] azx_probe_continue+0x45/0x940 > [snd_hda_intel] > [ 12.278162] [<ffffffff810913c0>] ? finish_task_switch+0x50/0xf0 > [ 12.278168] [<ffffffffa04be8d5>] azx_probe_work+0x15/0x20 [snd_hda_intel] > [ 12.278172] [<ffffffff8107cfec>] process_one_work+0x17c/0x430 > [ 12.278176] [<ffffffff8107dfac>] worker_thread+0x11c/0x3c0 > [ 12.278179] [<ffffffff8107de90>] ? manage_workers.isra.25+0x2a0/0x2a0 > [ 12.278183] [<ffffffff81084740>] kthread+0xc0/0xd0 > [ 12.278187] [<ffffffff81084680>] ? kthread_create_on_node+0x120/0x120 > [ 12.278193] [<ffffffff816f71ac>] ret_from_fork+0x7c/0xb0 > [ 12.278197] [<ffffffff81084680>] ? kthread_create_on_node+0x120/0x120 > [ 12.278200] ---[ end trace 21db90331deffc67 ]--- This one is the audio driver trying to ask from i915 for its power domain to be turned on. Sine i915 doesn't init at all, there won't be any power domain support either. A stop-gap solution would be to refuse loading the audio driver too in case of nomodeset. My bet is that BIOS leaves the power well enabled, so this shouldn't have any side effects besides the WARN.
Please attach a full dmesg from boot with drm.debug=0xe
Created attachment 94070 [details] dmesg with drm.debug=0xe The dmesg with drm.debug=0xe is attached.
Something else that is relatively easy to test: add i915.i915_enable_fbc=0 to your kernel command line.
I removed nomodeset from linux commandline and replace with i915.i915_enable_fbc=0 and it is no change from original set up. nomodeset does get to kde desktop on linuxminut kde, not sure if 3d is ok though. On Fri, Feb 14, 2014 at 8:11 AM, <bugzilla-daemon@freedesktop.org> wrote: > *Comment # 10 <https://bugs.freedesktop.org/show_bug.cgi?id=74167#c10> > on bug 74167 <https://bugs.freedesktop.org/show_bug.cgi?id=74167> from > Chris Wilson <chris@chris-wilson.co.uk> * > > Something else that is relatively easy to test: add i915.i915_enable_fbc=0 to > your kernel command line. > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
Created attachment 94108 [details] screenshot
Created attachment 94109 [details] Sshot with camera rgb chart up to show issue with color
Created attachment 94249 [details] intel_reg_dumper output from ubuntu 13.10 I booted the laptop with a ubuntu 13.10 USB stick - colours were inverted and the screen was fuzzy, Attached is the intel_reg_dumper output.
Created attachment 94250 [details] intel_reg_dumper output from ubuntu 13.10 with nomodeset Then I booted the laptop with the same Ubuntu 13.10 USB stick, adding the nomodeset kernel option. The colours are good and the display is sharp. The intel_reg_dumper output is quite different. I am not familiar with the i915 driver - perhaps there is a silver bullet in there. Antoine
Antoine, Running with nomodeset disbles 3d acceleration among other things and shouldn't be used as a permanent fix. On Mon, Feb 17, 2014 at 8:29 PM, <bugzilla-daemon@freedesktop.org> wrote: > *Comment # 15 <https://bugs.freedesktop.org/show_bug.cgi?id=74167#c15> > on bug 74167 <https://bugs.freedesktop.org/show_bug.cgi?id=74167> from > Antoine le Bret <antoine_le_bret@yahoo.ca> * > > Created attachment 94250 [details] <https://bugs.freedesktop.org/attachment.cgi?id=94250> [details] <https://bugs.freedesktop.org/attachment.cgi?id=94250&action=edit> > intel_reg_dumper output from ubuntu 13.10 with nomodeset > > Then I booted the laptop with the same Ubuntu 13.10 USB stick, adding the > nomodeset kernel option. The colours are good and the display is sharp. > > The intel_reg_dumper output is quite different. I am not familiar with the i915 > driver - perhaps there is a silver bullet in there. > > Antoine > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
(In reply to comment #0) > Created attachment 92965 [details] > logs > > Chipset: i915 > Arch: AMD64 > XOrg version: xorg-server 2:1.14.3-3ubuntu2 > Xf86-intel version: compiled for 1.14.5, module version = 2.99.904 > MESA version 1.4 > kernel: 3.11.0-12-generic > Linux Distro: Ubuntu, same problem in Linux Mint, Fedora and OpenSuse > Machine: Dell 3737 17 inch laptop Intel 4400 graphics, 4th Gen Core i5 4200U > Display: laptop display, 17 incxorh, 1600x900 > > Easy to reproduce, happens with all modern distributions listed above > > Attached: > Xorg log > dmesg > xrandr > intel_reg_dumper output > > Colors seem to be inverted, and screen is blurry. Did not happen with OEM > windows 8, but happens during linux install even after newest drivers from > 01.org. I experience the same problem (https://bugs.gentoo.org/show_bug.cgi?id=500706) Distro Gentoo Machine: Toshiba S70 series, Intel(R) Core(TM) i7-4700MQ CPU Display 17.3, 1600x900 Adam
I have the same problem -- inverted colors and pixellated graphics on a new Dell laptop running Mint 16. I just bought a Dell Inspiron 17 3737 with a Haswell core i3 processor and dual graphics -- Intel HD 4000 and either AMD Radeon HD 8730M or HD 7670M. The laptop came with Windows 8.1 installed, and I installed Linux Mint 16 in a dual boot configuration using about half of the 500GB drive. When booting, I get a grub boot menu (white letters on black background) that lets me boot either Mint or Windows, and both boot very well indeed, except for the Linux video problem. If anyone can give me instructions on how I can fix this video problem I'd be very grateful, even if its a temporary or partial fix that has drawbacks associated with 3D. I'd just like to get useable graphics. Thanks -- Charles
(In reply to comment #18) > If anyone can give me instructions on how I can fix this video problem I'd > be very grateful, even if its a temporary or partial fix that has drawbacks > associated with 3D. I'd just like to get useable graphics. You can try i915.modeset=0 to disable the Intel driver stack. You have to rely on UEFI or VESA actually working, but it will get you running - if a little sluggish.
(In reply to comment #19) > (In reply to comment #18) > > If anyone can give me instructions on how I can fix this video problem I'd > > be very grateful, even if its a temporary or partial fix that has drawbacks > > associated with 3D. I'd just like to get useable graphics. > > You can try i915.modeset=0 to disable the Intel driver stack. You have to > rely on UEFI or VESA actually working, but it will get you running - if a > little sluggish. I appreciate the suggestion very much, and I'd like to try it. Although I've been a Linux user for more than 10 years on several older machines, and have edited grub on occaision, I'm not expert enough to implement your advice. Can you be more specific on exactly which files I should edit, etc. In reality, I'm a near-noob. By the way, I'm running with UEFI enabled (not Legacy) and Secure Boot disabled. Thanks Charles
Hey Charles, you need to edit the grub config. For Linux Mint it should be in /etc/default. Look for the below line and change it, GRUB_CMDLINE_LINUX_DEFAULT="" change to GRUB_CMDLINE_LINUX_DEFAULT="i915.modeset=0" afterwards, you need to run update-grub2 as root. On Sun, Feb 23, 2014 at 9:35 AM, <bugzilla-daemon@freedesktop.org> wrote: > *Comment # 20 <https://bugs.freedesktop.org/show_bug.cgi?id=74167#c20> > on bug 74167 <https://bugs.freedesktop.org/show_bug.cgi?id=74167> from > Charles <charles_smee@yahoo.com> * > > (In reply to comment #19 <https://bugs.freedesktop.org/show_bug.cgi?id=74167#c19>) > > (In reply to comment #18 <https://bugs.freedesktop.org/show_bug.cgi?id=74167#c18>) > > > If anyone can give me instructions on how I can fix this video problem I'd > > > be very grateful, even if its a temporary or partial fix that has drawbacks > > > associated with 3D. I'd just like to get useable graphics. > > > > You can try i915.modeset=0 to disable the Intel driver stack. You have to > > rely on UEFI or VESA actually working, but it will get you running - if a > > little sluggish. > > > I appreciate the suggestion very much, and I'd like to try it. Although I've > been a Linux user for more than 10 years on several older machines, and have > edited grub on occaision, I'm not expert enough to implement your advice. Can > you be more specific on exactly which files I should edit, etc. In reality, > I'm a near-noob. By the way, I'm running with UEFI enabled (not Legacy) and > Secure Boot disabled. > > Thanks Charles > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
Thanks very much. I successfully performed the steps you suggested, and rebooted the computer. As another writer observed above, as the computer booted, the colors then appeared to be rendered correctly. The Linux Mint logo was the right color, and the black-background screen that came up had correctly colored text. But, the x-video system had a problem and would not load. So, no graphical interface, just a terminal screen, although a colorful one. I was able to re-install Mint without a problem, and the old version of grub is back. Any further thoughts on what I might do? Thanks Charles
I use Linux Mint kde and it is pretty usable with no crashes... try a few different distros with the grub option set. On Feb 23, 2014 2:17 PM, <bugzilla-daemon@freedesktop.org> wrote: > *Comment # 22 <https://bugs.freedesktop.org/show_bug.cgi?id=74167#c22> > on bug 74167 <https://bugs.freedesktop.org/show_bug.cgi?id=74167> from > Charles <charles_smee@yahoo.com> * > > Thanks very much. I successfully performed the steps you suggested, and > rebooted the computer. As another writer observed above, as the computer > booted, the colors then appeared to be rendered correctly. The Linux Mint logo > was the right color, and the black-background screen that came up had correctly > colored text. But, the x-video system had a problem and would not load. So, > no graphical interface, just a terminal screen, although a colorful one. I was > able to re-install Mint without a problem, and the old version of grub is back. > > Any further thoughts on what I might do? > > Thanks > > Charles > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
Thanks very much for the suggestion. I tried 8 other distros, and only one worked, but that one provided a correctly-colored graphical screen, just as it should have. That distro was Clonezilla 2.2.0.16 (December 2013). I used a Live-CD that contained an ISO image that I burned myself, and I employed it successfully on an old, former Vista machine. The ones that didn't work included a 64-bit version of Linux Mint 13 Mate which I created today; OSDisc.com versions of Linux Mint 13 Mate (32-bit which is running properly on the old Vista machine), and Parted Magic 2012_10_10; and versions of Wary Puppy 5.6; Puppy Linux 4.3.1; Precise Puppy 5.7.1; and Ubuntu 12.04, for all of which I downloaded ISO's and burned them to disks -- and all of these Live-CDs work properly on other, old machines. The problem with using these on the Dell Inspiron 17 3737 is that the UEFI disk boot system does not recognize that these disks are in the computer's DVD-RW drive. It is only the Linux Mint 16 (64-bit Mate) and the Clonezilla disk where the UEFI boot manager screen says that there's a DVD path to which the computer can boot. For the others, its as if the disk wasn't in the drive. However, booting the Dell with the mal-colored version of Lunix Mint 16 with each of these disks in the drive shows that Caja, Mint's file manager, recognizes each of these disks properly, and correctly identifies them by name or distribution number. And, the interesting question is why does the Clonezilla disk give correct screen colors, while the Linux Mint 16 Mate (64-bit) gives inverted colors and grainy pixellation? Thanks Charles
Very interested in this issue myself. New laptop, 3 distros (Ubuntu 12.04, Mageia 4, Kali Linux) and none have usable video. Kali seems to work the best with VESA, but it would be nice to be able to use the full feature set.
The "Live" versions of Korora 20 (Fedora), OpenSUSE 13.1 GNOME, and Linux Mint 13 (64-bit) load just fine from a USB key, but exhibit the same inverted colors and grainy pixellation. I didn't try Kali, since the description of its purpose seemed a little exotic for me. I'm hoping someone can respond with the magic formula to get a decently viewable screen with the Dell 17 3737, and other similar Intel/AMR dual-video laptops, while running Linux Mint 16, or some other easy-to-use distro.
I'd like to see a dump of a few more potentially interesting registers w/ i915.modeset=0: intel_reg_read 0x64000 0x6F400 0x6F410 0x7F008 0x70180 0x49010 0x49014 0x49018 0x4901c 0x49020 0x49024 0x49028 0x49030 0x49034 0x49038 0x49040 0x49044 0x49048 0x49080 0x43208 0x43408 0x4A480
I'd be delighted to provide them. How do I do it? Please bear in mind that when I edit grub to change GRUB_CMDLINE_LINUX_DEFAULT="" to GRUB_CMDLINE_LINUX_DEFAULT="i915.modeset=0" , and run update-grub as root, and then reboot, I'll get a black terminal screen, with properly colored text in the prompts. I don't know how to recover from that point, or how to perform additional grub edits after that point. Its tough when you know just enough to get yourself into serious trouble, but not enough to get out of it. Thanks Charles
Here you go: root@DellLaptop:~# cat /proc/cmdline && sh reg-read.sh root=UUID=3e5cbc54-3694-4062-a990-157897b7cb6a ro initrd=/install/gtk/initrd.gz quiet i915.modeset=0 0x64000 : 0x80000013 0x6F400 : 0x82214002 0x6F410 : 0x1 0x7F008 : 0xC0000010 0x70180 : 0x98000000 0x49010 : 0x0 0x49014 : 0x0 0x49018 : 0x0 0x4901C : 0x0 0x49020 : 0x0 0x49024 : 0x0 0x49028 : 0x0 0x49030 : 0x0 0x49034 : 0x0 0x49038 : 0x0 0x49040 : 0x0 0x49044 : 0x0 0x49048 : 0x0 0x49080 : 0x0 0x43208 : 0x0 0x43408 : 0x0 0x4A480 : 0x0 root@DellLaptop:~# uname -r 3.12-kali1-amd64
DellLaptop charles # cat /proc/cmdline && sh reg-read.sh BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=9f3431e8-8568-490c-8b86-8fcbf863cb38 ro quiet splash vt.handoff=7 sh: 0: Can't open reg-read.sh Stuck!
:) I had just made the requested registers into a small shell script, in case my gui didn't come back up with the boot argument change: root@DellLaptop:~# cat reg-read.sh for r in 0x64000 0x6F400 0x6F410 0x7F008 0x70180 0x49010 0x49014 0x49018 0x4901c 0x49020 0x49024 0x49028 0x49030 0x49034 0x49038 0x49040 0x49044 0x49048 0x49080 0x43208 0x43408 0x4A480;do intel_reg_read $r;done
Thanks, a cut and paste script is about right for someone at my skill level. I think I finally have the output, and hope you can make some sense of it. DellLaptop charles # for r in 0x64000 0x6F400 0x6F410 0x7F008 0x70180 0x49010 0x49014 0x49018 0x4901c 0x49020 0x49024 0x49028 0x49030 0x49034 0x49038 0x49040 0x49044 0x49048 0x49080 0x43208 0x43408 0x4A480;do intel_reg_read $r;done 0x64000 : 0x80000003 0x6F400 : 0x82210002 0x6F410 : 0x1 0x7F008 : 0xC0000010 0x70180 : 0xD9004400 0x49010 : 0x78000000 0x49014 : 0x0 0x49018 : 0x7800 0x4901C : 0x0 0x49020 : 0x0 0x49024 : 0x78000000 0x49028 : 0x0 0x49030 : 0x0 0x49034 : 0x0 0x49038 : 0x0 0x49040 : 0x0 0x49044 : 0x0 0x49048 : 0x0 0x49080 : 0x0 0x43208 : 0x90000000 0x43408 : 0x0 0x4A480 : 0x0 Thanks again Charles
(In reply to comment #32) > Thanks, a cut and paste script is about right for someone at my skill level. > I think I finally have the output, and hope you can make some sense of it. > > DellLaptop charles # for r in 0x64000 0x6F400 0x6F410 0x7F008 0x70180 > 0x49010 0x49014 0x49018 0x4901c 0x49020 0x49024 0x49028 0x49030 0x49034 > 0x49038 0x49040 0x49044 0x49048 0x49080 0x43208 0x43408 0x4A480;do > intel_reg_read $r;done > 0x64000 : 0x80000003 > 0x6F400 : 0x82210002 > 0x6F410 : 0x1 > 0x7F008 : 0xC0000010 > 0x70180 : 0xD9004400 > 0x49010 : 0x78000000 > 0x49014 : 0x0 > 0x49018 : 0x7800 > 0x4901C : 0x0 > 0x49020 : 0x0 > 0x49024 : 0x78000000 > 0x49028 : 0x0 > 0x49030 : 0x0 > 0x49034 : 0x0 > 0x49038 : 0x0 > 0x49040 : 0x0 > 0x49044 : 0x0 > 0x49048 : 0x0 > 0x49080 : 0x0 > 0x43208 : 0x90000000 > 0x43408 : 0x0 > 0x4A480 : 0x0 > > Thanks again > > Charles That looks like it's from i915. Can you repeat w/ modeset=0? Although Stew's register dump didn't show anything really suspicious, so I'm fairly stumped by this. Also can someone grab the latest intel-drm-nightly and grab the dmesg w/ drm.debug=0xe?
Thanks -- Please tell me how. Bear in mind, as I wrote in comment 22, after editing grub to insert modeset=0 as indicated in Comment 21, I got correct colors on the "LM" logo upon rebooting, but that disappeared and was replaced by a black terminal screen with correctly colored text in the prompts. No graphics at all. Charles
(In reply to comment #34) > Thanks -- Please tell me how. > > Bear in mind, as I wrote in comment 22, after editing grub to insert > modeset=0 as indicated in Comment 21, I got correct colors on the "LM" logo > upon rebooting, but that disappeared and was replaced by a black terminal > screen with correctly colored text in the prompts. No graphics at all. > > Charles It doesn't matter if X manages to start or not.
Out of curiosity, will there be a way for me to reedit the grub file from that black screen, or will I have to reinstall Mint? Charles
(In reply to comment #36) > Out of curiosity, will there be a way for me to reedit the grub file from > that black screen, or will I have to reinstall Mint? Just hit 'e' at the grub screen and edit the params before booting. This way they won't be saved permanently and will only affect the one boot.
This Dell 3737 is set up as dual boot with windows 8.1 and Mint 16. I can get to the grub screen during the reboot (it lists booting to mint, mint recovery, windows, and system setup). I can then hit "e", giving me what looks like a boot sequence for mint, or c, giving me a "c" giving me a command line from which a lot can obviously be done, as illustrated by c>help. But, its not apparent how I can edit /etc/default/grub, or the other two files that grub modifies, from that point. Thanks Charles
(In reply to comment #38) > This Dell 3737 is set up as dual boot with windows 8.1 and Mint 16. I can > get to the grub screen during the reboot (it lists booting to mint, mint > recovery, windows, and system setup). I can then hit "e", giving me what > looks like a boot sequence for mint, or c, giving me a "c" giving me a > command line from which a lot can obviously be done, as illustrated by > c>help. > > But, its not apparent how I can edit /etc/default/grub, or the other two > files that grub modifies, from that point. You hit 'e', move to the line that starts with "linux", and add the parameters to the end. Then you hit ctrl-x or F10 to boot, as instructed at the bottom of the screen. As I said, this way the changes won't be saved permanently to /etc/default/grub or anywhere in /boot, and will only be effective for this one boot. A little googling brings up e.g. http://members.iinet.net/~herman546/p20/GRUB2%20Edit%20Mode.html for further help. HTH.
OK. And thanks for the interesting references. I'll go through them in full later, so you don't have to wait forever while I try to reinvent this wheel. I entered the grub menu with "e" as you said, and appended i915.modeset=0 to the end of the line beginning "linx", with a space behind the last entry, which was "quiet splash $vt_handoff". Couldn't figure out how to append the "0x64000" parameters to the line. I got a correctly colored "Linux Mint" logo, and the message "Failed to start the x server"..."Would you like to view the X server output to diagnose the problem?". Please let me know what I should do next. Thanks Charles
(In reply to comment #40) > I got a correctly colored "Linux Mint" logo, and the message "Failed to > start the x server"..."Would you like to view the X server output to > diagnose the problem?". Ah, that sounds just like a missing driver. /var/log/Xorg.0.log will have the right information about the failure.
Unfortunately, after that event I must have fouled up grub as I was attempting to get the information requested in Comment 33. That caused the computer to shut down at the end of every boot cycle. So, I had to reinstall Mint and, in the process, the /var/log/Xorg.0.log file associated with the black screen when GRUB_CMDLINE_LINUX_DEFAULT="" is replaced by GRUB_CMDLINE_LINUX_DEFAULT="i915.modeset=0" was lost. Charles
No joy with the intel-nightly, assuming I got the right thing: stew@DellLaptop:~$ uname -a && cat /proc/cmdline Linux DellLaptop 3.14.0-rc3+ #1 SMP Sat Mar 1 00:28:31 EST 2014 x86_64 GNU/Linux root=UUID=3e5cbc54-3694-4062-a990-157897b7cb6a ro initrd=/install/gtk/initrd.gz quiet git://anongit.freedesktop.org/drm-intel What should be green is purple, what should be red is green, and everything is "fuzzy". Some of the other references to this issue mention that it's something to do with the backlight on this display. Like others, things are fine if I use HDMI to an external monitor. lspci: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device 05ec Flags: bus master, fast devsel, latency 0, IRQ 64 Memory at b0000000 (64-bit, non-prefetchable) [size=4M] Memory at a0000000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 Let me know if there's more info I can provide.
Assigning to your residential hsw display expert ... Maybe we also need to poke Art for what's likely wrong here.
Created attachment 95362 [details] Xorg.0.log Inverted colors Intel hd 4400/AMD Radeon HD8670M Chris -- the Xorg.0.log file you requested is attached. Sorry for the delay.
I was able to get normal graphics on my Dell Inspiron 17 3737 running Linux Mint 16 dual-booted with Windows 8.1, using UEFI with secure boot disabled. For the first time, I get normal, non-inverted colors while using all the Linux software packages I've tried, including applications, internet, and a commercial DVD movie with the VLC player. I did the following: 1) Installed fglrx-pxpress using the Software Manager. fglrx was already installed. This caused Xorg to fail to load, followed by a black screen. However, I rebooted into recovery mode. 2) While booting in recovery mode, saying yes to the question of accessing archived data packages. 3) At a stage in the recovery process, a menu appears that is headed by "resume". This menu allows me to run "dpkg" to repair broken packages. I do so. 4) After this, the same recovery menu reappears, and I run "resume". When the computer finishes booting, the graphics are normal. The resolution of the screen was reset to 1600x900 with a refresh rate of 77Hz (this is up from the 13??x??? value, with 60Hz refresh, that I set to make the "inverted colors" graphics more useable). Also, the monitor is no longer identified as "Seiko-Epson" but is now "Unknown". The fly in this marvelous ointment is that steps 2-4, above, must be followed every time I boot up. Also, trying to place the computer in either suspend or hibernate causes Xorg to fail, with a black screen. The only way to recover is rebooting in recovery mode as above. But, rebooting using steps 2-4, above, is abosolutely repeatable -- time after time. If anyone can make sense of what's happening here and, more importantly, how to make permanent the beneficial changes wrought by installing "fglrx-pxpress" and running "dpkg" while rebooting in recovery mode, I'd certainly be very pleased to know. But, what a pleasure it is to see images of strawberries that are red instead of green! Thanks in advance for a little more assistance from the knowledgeable, Charles
You've probably simply broken your intel gfx driver and now the systems is running in uefi fallback mode using the firmware driver. When you reboot you have the real intel gfx driver again. You can achieve this easier with i915.modeset=0 on your kernel cmdline, but that means hw accel for opengl, video or anything. Assigning to Paulo.
Yes, installing fglrx-pxpress and then adding "i915.modeset=0" to grub, as shown in comment 21 above, has done the trick. Now Mint 16 boots normally on my Dell 17 3737, and shows correct graphics in all modes, including DVD movies. Thanks to all for the help!!
Booting with i915.modeset=0 disables the intel driver completely, which means you're now definitely running with the efifb or vesa driver. Also fglrx is likely still causing no ends of harm. Can either of you please attempt to reproduce this on a _clean_ system with no fglrx installed and also no fancy boot options and other tricks pulled? Without that we can't really baseline this issue here.
Configuring partitions now, please advise what all information/logs to provide. I was planning on using ubuntu 13.10. On Fri, Apr 11, 2014 at 11:31 AM, <bugzilla-daemon@freedesktop.org> wrote: > Daniel Vetter <daniel@ffwll.ch> changed bug 74167<https://bugs.freedesktop.org/show_bug.cgi?id=74167> > What Removed Added Status ASSIGNED NEEDINFO > > *Comment # 50 <https://bugs.freedesktop.org/show_bug.cgi?id=74167#c50> > on bug 74167 <https://bugs.freedesktop.org/show_bug.cgi?id=74167> from > Daniel Vetter <daniel@ffwll.ch> * > > Booting with i915.modeset=0 disables the intel driver completely, which means > you're now definitely running with the efifb or vesa driver. > > Also fglrx is likely still causing no ends of harm. > > Can either of you please attempt to reproduce this on a _clean_ system with no > fglrx installed and also no fancy boot options and other tricks pulled? Without > that we can't really baseline this issue here. > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
My system is standard configuration. All I've done is add i915.modeset=0 to the kernel args to make it usable with vesa. The other 2 OS's with the same issue (Mageia, Ubuntu) are still on the system also. Will be happy to provide any information needed.
Not sure if this applies to all affected by this bug, but I was experiencing the issue on a Dell Inspirion 17, 3737 with Intel HD graphics 4400 and it is now working with linux kernel 3.15rc5. On Fri, Apr 11, 2014 at 6:38 PM, <bugzilla-daemon@freedesktop.org> wrote: > *Comment # 52 <https://bugs.freedesktop.org/show_bug.cgi?id=74167#c52> > on bug 74167 <https://bugs.freedesktop.org/show_bug.cgi?id=74167> from Stew > Benedict <stewbintn@gmail.com> * > > My system is standard configuration. All I've done is add i915.modeset=0 to the > kernel args to make it usable with vesa. The other 2 OS's with the same issue > (Mageia, Ubuntu) are still on the system also. > > Will be happy to provide any information needed. > > ------------------------------ > You are receiving this mail because: > > - You reported the bug. > >
Hmm, 3.15rc5 does indeed let me boot without extra arguments, but now it appears to be using fbdev: stew@dell:~$ uname -r && cat /proc/cmdline 3.15.0-031500rc5-generic root=UUID=3e5cbc54-3694-4062-a990-157897b7cb6a ro initrd=/install/gtk/initrd.gz quiet in /var/log/Xorg.0.log: [ 25.085] (==) Matched intel as autoconfigured driver 0 [ 25.085] (==) Matched vesa as autoconfigured driver 1 [ 25.085] (==) Matched fbdev as autoconfigured driver 2 [ 25.085] (==) Assigned the driver to the xf86ConfigLayout [ 25.085] (II) LoadModule: "intel" [ 25.086] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [ 25.456] (II) Module intel: vendor="X.Org Foundation" [ 25.456] compiled for 1.12.3.902, module version = 2.19.0 [ 25.456] Module class: X.Org Video Driver [ 25.456] ABI class: X.Org Video Driver, version 12.1 but... stew@dell:~$ grep -i loadmodule /var/log/Xorg.0.log [ 24.849] (II) LoadModule: "extmod" [ 24.968] (II) LoadModule: "dbe" [ 24.976] (II) LoadModule: "glx" [ 25.014] (II) LoadModule: "record" [ 25.018] (II) LoadModule: "dri" [ 25.075] (II) LoadModule: "dri2" [ 25.085] (II) LoadModule: "intel" [ 25.456] (II) LoadModule: "vesa" [ 25.493] (II) LoadModule: "fbdev" [ 25.507] (II) LoadModule: "fbdevhw" [ 25.567] (II) LoadModule: "fb" [ 25.638] (II) LoadModule: "shadow" [ 25.639] (II) UnloadModule: "vesa" [ 25.639] (II) UnloadModule: "intel" [ 28.995] (II) LoadModule: "evdev" [ 29.015] (II) LoadModule: "synaptics" root@dell:~# lsmod | grep '^i915' && sh reg-read.sh i915 873364 4 Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable Couldn't map MMIO region: Resource temporarily unavailable
(In reply to comment #54) > Hmm, 3.15rc5 does indeed let me boot without extra arguments, but now it > appears to be using fbdev: > > stew@dell:~$ uname -r && cat /proc/cmdline > 3.15.0-031500rc5-generic > root=UUID=3e5cbc54-3694-4062-a990-157897b7cb6a ro > initrd=/install/gtk/initrd.gz quiet > > in /var/log/Xorg.0.log: > > [ 25.085] (==) Matched intel as autoconfigured driver 0 > [ 25.085] (==) Matched vesa as autoconfigured driver 1 > [ 25.085] (==) Matched fbdev as autoconfigured driver 2 > [ 25.085] (==) Assigned the driver to the xf86ConfigLayout > [ 25.085] (II) LoadModule: "intel" > [ 25.086] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so > [ 25.456] (II) Module intel: vendor="X.Org Foundation" > [ 25.456] compiled for 1.12.3.902, module version = 2.19.0 > [ 25.456] Module class: X.Org Video Driver > [ 25.456] ABI class: X.Org Video Driver, version 12.1 Had you actually looked at the whole Xorg.0.log, or even attached it, you would have noticed that 2.19.0 lacks Haswell support because it is too old. Even generic support for all chipsets was not added until 2.20.0.
Created attachment 99276 [details] X log with 3.15rc5 My apologies. I did look at the whole log, but didn't see much else relevant, beside the unload. So in practical terms, this means I need to compile the latest X driver?
Debian testing has a recent enough xorg-xserver-video-intel driver for Haswell, you may want to try to that, although building from git is fairly trivial on debian (ask nicely and it will install all the relevant packages for you).
Created attachment 99280 [details] Xorg log using git driver build That seems to work, thanks. Intel is now loaded. glxinfo and glxgears don't seem happy though: stew@dell:~$ glxinfo name of display: :0.0 Unrecognized deviceID 0xa16 X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Serial number of failed request: 22 Current serial number in output stream: 25
You also need a more recent version of mesa (OpenGL drivers) to recognise Haswell.
Tried installing libgl1-mesa-glx:amd64 10.1.2-1 from debian-testing and it's deps, but apparently not new enough. At any rate, I think this specific bug is fixed for me. Presumably the distros will catch up at some point. For now I have a bit of a hybrid system :) /me just bought the wrong laptop.
Hmm, I believe you need libgl1-mesa-dri, so please check that is also installed.
(In reply to comment #54) > Hmm, 3.15rc5 does indeed let me boot without extra arguments, but now it > appears to be using fbdev: Sounds like we've resolved the original bug, yay! Thanks for reporting this and if anything else is broken please file a new bug report.
So what exactly fixed this? I can't think of anything apart from maybe some DP lane count change. But the logs show it using 2 lanes only even with older kernels so this theory seems a bit weak. Any chance someone could reverse bisect this?
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.