Launchpad has imported 22 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=596557.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2010-05-26T23:48:07+00:00 Adam wrote: I have here a Sony Vaio Z laptop. It's a fairly new model with switchable graphics: it has both a GeForce and an Intel integrated graphics chipset. I can configure the BIOS so I can enable only one card during any given boot, using the selector switch on the laptop. At this point it ought to be just like dealing with a single adapter for the OS, so we should be able to cope with driving either adapter using nouveau or intel (respectively). In fact, neither work. Here's the report for the intel adapter. As soon as i915 gets loaded with KMS enabled, the screen goes blank (with the backlight on). If I load i915 without KMS, it succeeds, but obviously this is no use for actually running X now the UMS support is gone from the X driver. I will attach relevant sections from /var/log/messages , and the lspci -nn output. Xorg.0.log doesn't seem useful in this case as the failure is earlier. Chip is: 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/0 ------------------------------------------------------------------------ On 2010-05-26T23:49:00+00:00 Adam wrote: Created attachment 417065 lspci output on the affected system Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/1 ------------------------------------------------------------------------ On 2010-05-26T23:54:02+00:00 Adam wrote: By the looks of the logs, the following appears in /var/log/messages when loading i915 *without* KMS: May 26 16:39:05 vaioz kernel: [drm] Initialized drm 1.1.0 20060810 May 26 16:39:05 vaioz kernel: pci 0000:00:02.0: power state changed by ACPI to D0 May 26 16:39:05 vaioz kernel: pci 0000:00:02.0: power state changed by ACPI to D0 May 26 16:39:05 vaioz kernel: pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 26 16:39:05 vaioz kernel: mtrr: no more MTRRs available May 26 16:39:05 vaioz kernel: [drm] MTRR allocation failed. Graphics performance may suffer. May 26 16:39:05 vaioz kernel: acpi device:00: registered as cooling_device4 May 26 16:39:05 vaioz kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 May 26 16:39:05 vaioz kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) May 26 16:39:05 vaioz kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 May 26 16:39:05 vaioz kernel: modprobe used greatest stack depth: 3176 bytes left when loading i915 *with* KMS, nothing at all appears in the logs. There's nothing in /var/log/messages between where boot is complete, and when the next boot starts up. I will attach the entire /var/log/messages . Here's my timing notes. All refer to today, May 26th: 16:36:28 - boot complete ~16:37 - modprobe i915 , screen blank with backlight on 16:38:35 - second boot complete ~16:39 - modprobe i915 modeset=0, screen fine -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/2 ------------------------------------------------------------------------ On 2010-05-26T23:55:15+00:00 Adam wrote: Created attachment 417066 /var/log/messages from the affected system Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/3 ------------------------------------------------------------------------ On 2010-05-26T23:55:48+00:00 Adam wrote: if you're wondering why the adapter apparently disappears entirely outside of these couple of test boots, to actually *use* the system I boot with the NVIDIA adapter selected, and use the NVIDIA proprietary driver (which works). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/4 ------------------------------------------------------------------------ On 2010-05-27T00:00:28+00:00 Adam wrote: Final note - this happens with both 2.6.34-2.fc14.x86_64 and 2.6.33.4-95.fc13.x86_64 . -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/5 ------------------------------------------------------------------------ On 2010-05-28T20:42:34+00:00 Adam wrote: with thanks to the inhabitants of #fedora-devel, I'll attach the drm debug messages (with drm.debug=0x06 as directed by ajax). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/6 ------------------------------------------------------------------------ On 2010-05-28T20:43:00+00:00 Adam wrote: Created attachment 417742 drm debug messages from a load of i915 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/7 ------------------------------------------------------------------------ On 2010-08-20T18:19:46+00:00 Adam wrote: This is still the case with the latest F14 kernel (2.6.35.2-9.fc14) - same behaviour, as soon as KMS kicks in, the system hangs with backlight on. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/32 ------------------------------------------------------------------------ On 2010-08-26T18:12:02+00:00 Adam wrote: *** Bug 618481 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/57 ------------------------------------------------------------------------ On 2010-09-28T18:49:07+00:00 Adam wrote: Upstream: https://bugs.freedesktop.org/show_bug.cgi?id=29141 Jesse Barnes apparently now has a matching system and is working on this. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/91 ------------------------------------------------------------------------ On 2010-10-08T16:29:50+00:00 Adam wrote: Jesse's posted fixes to his edp-hacks branch which others have tested with positive results - see the upstream bug. I'm trying to patch the fixes onto an F15 kernel build to test right now. I'm fairly sure the fixes are the commits: 17 hours ago Jesse Barnes drm/i915/dp: more broken sequencing fixes edp-hacks commit | commitdiff | tree | snapshot 43 hours ago Jesse Barnes drm/i915/dp: broken eDP power sequencing bits commit | commitdiff | tree | snapshot 43 hours ago Jesse Barnes drm/i915/dp: wait for panel idle when enabling/disablin... commit | commitdiff | tree | snapshot Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/94 ------------------------------------------------------------------------ On 2010-10-08T16:32:11+00:00 Adam wrote: that's: * http://git.kernel.org/?p=linux/kernel/git/jbarnes/drm- intel.git;a=commit;h=f0c744bbce33c64bedbe15d9785efafd5380c58c * http://git.kernel.org/?p=linux/kernel/git/jbarnes/drm- intel.git;a=commit;h=050486e2f3f8aa97c5f8afdc9b898b00a7114493 * http://git.kernel.org/?p=linux/kernel/git/jbarnes/drm- intel.git;a=commit;h=4da9b7d2917beb1f8aa9e7e4f6d4f10338b0f637 i think the other changes in the branch are not directly related to this bug, but haven't checked yet, it would probably be best to ask Jesse. Proposing this as NTH for final. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/95 ------------------------------------------------------------------------ On 2010-10-08T18:57:02+00:00 Adam wrote: Discussed at the blocker/NTH review meeting today, given the ickiness of making changes to panel code this late, we decided not to take it as NTH. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/96 ------------------------------------------------------------------------ On 2010-10-08T22:28:00+00:00 Adam wrote: so I'm sucking at making these patches apply to the f15 kernel and build. But they have gone into drm-intel-next as part of a giant change set (just look at all the commits from Jesse dated together, late on 7th Oct). ajax, could you possibly just pull that whole change set into the f15 kernel (note: f15 not f14) for me to try? thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/97 ------------------------------------------------------------------------ On 2010-10-09T18:47:01+00:00 Adam wrote: OK, so I couldn't get a clean patch against a Fedora kernel, but I just built a kernel straight from the upstream drm-intel-next tree and confirmed that it works great. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/98 ------------------------------------------------------------------------ On 2010-11-02T01:18:22+00:00 Adam wrote: -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/104 ------------------------------------------------------------------------ On 2010-11-29T18:21:09+00:00 Adam wrote: bumping this to at least 14 because i don't see it being backported to 13; it may eventually only be fixed in rawhide/15. it was fixed briefly in rawhide by a backport of drm-intel-next/edp- fixes but that was backed out apparently for causing other problems, so current status is that it's still broken everywhere. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/109 ------------------------------------------------------------------------ On 2011-01-03T01:13:49+00:00 Claes wrote: I had similar problems on a Lenovo U160 with integrated Intel graphics. linux-2.6.37-rc8 fixes the problem for me. Have you tried it? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/120 ------------------------------------------------------------------------ On 2011-01-03T12:26:46+00:00 Adam wrote: Yes, and no. When it comes to graphics, 'similar' problems are generally not similar at all. I'm already well aware of all relevant changes for this bug. But thanks. The reason this report isn't changing much is that all the interesting stuff is happening on the upstream report. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/121 ------------------------------------------------------------------------ On 2011-01-03T12:28:31+00:00 Adam wrote: -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/122 ------------------------------------------------------------------------ On 2012-08-16T16:56:39+00:00 Fedora wrote: This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/608907/comments/146 ** Changed in: fedora Status: Unknown => Won't Fix ** Changed in: fedora Importance: Unknown => High ** Bug watch added: freedesktop.org Bugzilla #29141 https://bugs.freedesktop.org/show_bug.cgi?id=29141 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/608907 Title: [i915] Lenovo U160 Intel i7 620UM blank screen Status in Linux: Invalid Status in OEM Priority Project: Invalid Status in OEM Priority Project oneiric series: Invalid Status in linux package in Ubuntu: Fix Released Status in Fedora: Won't Fix Bug description: Hi, I tried to run Ubuntu 10.04 amd64 on my new Lenovo U160. Inside the Lenovo U160 works a Intel Core i7 620UM (arrandale) with integratet graphics. The error looks like this: https://bugs.launchpad.net/gentoo/+bug/554569 but the Kernel in post #98 did not solve my problem. I know an other Lenovo U160 with Intel core i5 520UM which has the same problem. I only can use it with the kernel boot parameter i915.modeset=0 in vesa-mode. I am at my wit's end. thx for your help Sascha To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/608907/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
