Bug#593432: Black screen with kms and i915
retitle 593432 [i830] Black screen with kms and i915 kthxbye On Wed, Aug 18, 2010 at 07:53:29 +0200, san...@zedat.fu-berlin.de wrote: When booting the screen goes black at the moment the frame buffer is switched on. Booting continues until the 'login prompt', but the screen remains black. When switching to a text screen, the screen gets darker for a second, but no text login appears. I can then, however, login blind and the machine works. For example, I can reboot it when logging in as root and calling 'shutdown' (all blind, of course). The problem goes away when adding the line options i915 modeset=0 to the file /etc/modprobe.d/i915-kms.conf, so I guess it is a kms problem. If I wasn't a newbie I'd mark this bug as 'important', because it left a freshly installed machine more or less completely unusable. Is this a regression from a previous revision? Can you attach the dmesg from a kms boot? Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#593432: Black screen with kms and i915
Processing commands for cont...@bugs.debian.org: retitle 593432 [i830] Black screen with kms and i915 Bug #593432 [linux-2.6] Black screen with kms and i915 Changed Bug title to '[i830] Black screen with kms and i915' from 'Black screen with kms and i915' kthxbye Stopping processing here. Please contact me if you need assistance. -- 593432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128211817528495.transcr...@bugs.debian.org
Bug#593432: Black screen with kms and i915
I have a i830 also.. If you turn off KMS the old framebuffer driver works fine obviously, this means 2.6.34 and beyond are unusable at this point in time on the i830 although I did get the blacklight on in the terminal using 2.6.35 with KMS on My Toshiba 1200-S212 i830 only has 8 megs of video ram, which I concluded was not enough to run the new drmframebuffer drivers... Than intel introduced the virtual memory stuff, but AFAICT it's not active on the i830 yet from memory (so forgive the incomplete description) both pipe A and pipe B are active when cloning the xorg.conf device and [screen or monitor] sections... but I also haven't attached an external monitor to look at how it behaves... 1there are only so many (24) hours in one day [-) ... - Original Message From: Julien Cristau jcris...@debian.org To: san...@zedat.fu-berlin.de; 593...@bugs.debian.org Sent: Wed, August 18, 2010 8:55:35 AM Subject: Bug#593432: Black screen with kms and i915 retitle 593432 [i830] Black screen with kms and i915 kthxbye On Wed, Aug 18, 2010 at 07:53:29 +0200, san...@zedat.fu-berlin.de wrote: When booting the screen goes black at the moment the frame buffer is switched on. Booting continues until the 'login prompt', but the screen remains black. When switching to a text screen, the screen gets darker for a second, but no text login appears. I can then, however, login blind and the machine works. For example, I can reboot it when logging in as root and calling 'shutdown' (all blind, of course). The problem goes away when adding the line options i915 modeset=0 to the file /etc/modprobe.d/i915-kms.conf, so I guess it is a kms problem. If I wasn't a newbie I'd mark this bug as 'important', because it left a freshly installed machine more or less completely unusable. Is this a regression from a previous revision? Can you attach the dmesg from a kms boot? Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/855539.98275...@web35604.mail.mud.yahoo.com
Bug#593432: Black screen with kms and i915
Strange. Last night's update must have changed the default behavior. All of a sudden the content of /etc/modprobe.d/i915-kms.conf doesn't seem to matter anymore: kms is always off. The only way to trigger the problem is to add modeset=1 to the boot options. I guess this makes the problem less grave, because the default behavior works now. For your questions: I installed the machine from scratch using a netinstall cd in late July. From the date, the kernel must have been 2.6.32-15. The bug was there. Before, I had been using Lenny, and that worked fine. However, that's pre-kms anyways, so I don't know whether that really counts as a regression. Here's the dmesg output with kms: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-20) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Thu Aug 12 13:38:27 UTC 2010 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] NSC Geode by NSC [0.00] Cyrix CyrixInstead [0.00] Centaur CentaurHauls [0.00] Transmeta GenuineTMx86 [0.00] Transmeta TransmetaCPU [0.00] UMC UMC UMC UMC [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009e800 (usable) [0.00] BIOS-e820: 0009e800 - 000a (reserved) [0.00] BIOS-e820: 000c - 000d4000 (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - 176b7000 (usable) [0.00] BIOS-e820: 176b7000 - 176e (ACPI NVS) [0.00] BIOS-e820: 176e - 176f (ACPI data) [0.00] BIOS-e820: 176f - 1770 (ACPI NVS) [0.00] BIOS-e820: 1770 - 1778 (usable) [0.00] BIOS-e820: 1778 - 1800 (reserved) [0.00] BIOS-e820: ff80 - ffc0 (reserved) [0.00] BIOS-e820: fff0 - 0001 (reserved) [0.00] DMI 2.3 present. [0.00] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it. [0.00] e820 update range: - 0001 (usable) == (reserved) [0.00] last_pfn = 0x17780 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C7FFF write-protect [0.00] C8000-E uncachable [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask FF000 write-back [0.00] 1 base 01000 mask FF800 write-back [0.00] 2 base 017F8 mask 8 uncachable [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] PAT not supported by CPU. [0.00] initial memory mapped : 0 - 0180 [0.00] init_memory_mapping: -1778 [0.00] 00 - 40 page 4k [0.00] 40 - 001740 page 2M [0.00] 001740 - 001778 page 4k [0.00] kernel direct mapping tables up to 1778 @ 1-16000 [0.00] RAMDISK: 1113f000 - 1194891c [0.00] ACPI: RSDP 000f6300 00014 (v00 PTLTD ) [0.00] ACPI: RSDT 176ea420 00034 (v01 PTLTDRSDT 0604 LTP ) [0.00] ACPI: FACP 176efdf3 00074 (v01 DELL X200 0604 PTL 004B) [0.00] ACPI: DSDT 176ea454 0599F (v01 DELLX2000604 MSFT 010D) [0.00] ACPI: FACS 176fcfc0 00040 [0.00] ACPI: SSDT 176efe67 000BC (v01 PTLTD ACPICST1 0604 LTP 0001) [0.00] ACPI: SSDT 176eff23 000B5 (v01 PTLTD ACPIPST1 0604 LTP 0001) [0.00] ACPI: BOOT 176effd8 00028 (v01 PTLTD $SBFTBL$ 0604 LTP 0001) [0.00] 0MB HIGHMEM available. [0.00] 375MB LOWMEM available. [0.00] mapped low ram: 0 - 1778 [0.00] low ram: 0 - 1778 [0.00] node 0 low ram: - 1778 [0.00] node 0 bootmap 00012000 - 00014ef0 [0.00] (9 early reservations) == bootmem [00 - 001778] [0.00] #0 [00 - 001000] BIOS data page == [00 - 001000] [0.00] #1 [001000 - 002000]EX TRAMPOLINE == [001000 - 002000] [0.00] #2 [006000 - 007000] TRAMPOLINE == [006000 - 007000] [0.00] #3 [000100 - 00014c6b94]TEXT DATA BSS == [000100 - 00014c6b94] [0.00] #4 [001113f000 - 001194891c] RAMDISK == [001113f000 - 001194891c] [
Bug#593432: Info received (Bug#593432: Black screen with kms and i915)
Forget what I said about the default behavior having changed. This machine is a can full of Heisenbugs! After the fifth reboot, kms came back with a vengeance. Currently not even the conf file won't stop it. The only way I have to use the machine is the kernel from Ubuntu 10.4 that I hand-copied onto it. Apparently they have kms disabled for the i915 by some brute force method. The dmesg output contains the line /i915/ disabling kernel modesetting for known /bad device/.
