Re: intel text mode restore problem
Hi all, (please Cc) On Wed, 10 Dec 2008, Eric Anholt wrote: > > There are two problems with this laptop: The first is that often (or > > better always) when I start X and run it for some time (no idea what is > > necessary), and then switch to the console the text mode is not > > restored. The effect is that on the top of the screen there is probably > > one of maybe two screen lines of the characters shown (screen lines > > means 1 pixel lines) and the whole screen is flashing. The rest of the > > screen is dark/grey and flashing. [...] > For the first issue, it's often hard to tell what's going wrong as the > registers will be the same as far as we can see between success and > failure. The difficulty of recovering text mode is one of the reasons > that text mode is going away with kernel modesetting (planned for > 2.6.29). intel_reg_dumper from the 2d driver build tree may help debug > what's different between success and failure of vt switching today. Ok, here are four times the output of intel_reg_dumper: - intel-reg-in-X-pre-switch Computer has booted, I am working in X and have *never* before switched to the console now I switch to the console which is garbled - intel_console_bad the command has been run on the console which was garbled switching back to X and back to console gives me a working console - intel_console_good switching back to X and calling the dumper a last time in X - intel-reg-in-X-after-fixed-switch The diff between the two console dumps is quite small: --- intel_console_bad 2008-12-17 22:18:39.0 +0100 +++ intel_console_good 2008-12-17 22:18:39.0 +0100 @@ -45,7 +45,7 @@ (II): FBC_COMMAND: 0x (II): FBC_STATUS: 0x (II): FBC_CONTROL2: 0x -(II):FBC_FENCE_OFF: 0x1100 +(II):FBC_FENCE_OFF: 0x8202c500 (II): FBC_MOD_NUM: 0x (II): FPA0: 0x00031108 (n = 3, m1 = 17, m2 = 8) (II): FPA1: 0x00031108 (n = 3, m1 = 17, m2 = 8) @@ -166,10 +166,10 @@ (II): CR09: 0x4f (II): CR0a: 0x0d (II): CR0b: 0x0e -(II): CR0c: 0x04 -(II): CR0d: 0x10 -(II): CR0e: 0x0b -(II): CR0f: 0x90 +(II): CR0c: 0x00 +(II): CR0d: 0x50 +(II): CR0e: 0x07 +(II): CR0f: 0xd0 (II): CR10: 0x9c (II): CR11: 0x8e (II): CR12: 0x8f but I have no way to interpret that. Hope that helps. BTW, is there anything about the other problem and the mal-detection of an external monitor which caused gdm to start in a strange mode? Best wishes Norbert --- Dr. Norbert Preining Vienna University of Technology Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- WHAPLODE DROVE (n.) A homicidal golf stroke. --- Douglas Adams, The Meaning of Liff (II): DumpRegsBegin (II):VCLK_DIVISOR_VGA0: 0x00031108 (n = 3, m1 = 17, m2 = 8) (II):VCLK_DIVISOR_VGA1: 0x00031406 (n = 3, m1 = 20, m2 = 6) (II):VCLK_POST_DIV: 0x00020002 (vga0 p1 = 4, p2 = 2, vga1 p1 = 2, p2 = 2) (II):DPLL_TEST: 0x00010001 () (II): CACHE_MODE_0: 0x6820 (II): D_STATE: 0x (II):DSPCLK_GATE_D: 0x1004000c (clock gates disabled: VRHUNIT DSSUNIT OVRUNIT OVCUNIT) (II): RENCLK_GATE_D1: 0x (II): RENCLK_GATE_D2: 0x02c0 (II):SDVOB: 0x0018 (disabled, pipe A, stall disabled, not detected) (II):SDVOC: 0x0018 (disabled, pipe A, stall disabled, not detected) (II): SDVOUDI: 0x (II): DSPARB: 0x (II): DSPFW1: 0x3f8f0f0f (II): DSPFW2: 0x150f0f0f (II): DSPFW3: 0x (II): ADPA: 0x0c00 (disabled, pipe A, -hsync, -vsync) (II): LVDS: 0xc2008300 (enabled, pipe B, 18 bit, 1 channel) (II): DVOA: 0x (disabled, pipe A, no stall, -hsync, -vsync) (II): DVOB: 0x0018 (disabled, pipe A, no stall, +hsync, +vsync) (II): DVOC: 0x0018 (disabled, pipe A, no stall, +hsync, +vsync) (II): DVOA_SRCDIM: 0x (II): DVOB_SRCDIM: 0x (II): DVOC_SRCDIM: 0x (II): PP_CONTROL: 0x0001 (power target: on) (II):PP_STATUS: 0xc008 (on, ready, sequencing idle) (II): PFIT_CONTROL: 0x (II): PFIT_PGM_RATIOS: 0x071c0666 (II): PORT_HOTPLUG_EN: 0x0120 (II):PORT_HOTPLUG_STAT: 0x0400 (II): DSPACNTR: 0x58000400 (disabled, pipe A) (II
Re: intel text mode restore problem
On Sun, 14 Dec 2008, Julien Cristau wrote: > you can install the xserver-xorg-video-intel-dbg package, or build the > reg dumper from the xf86-video-intel source tree. Great, thanks! Best wishes Norbert --- Dr. Norbert Preining Vienna University of Technology Debian Developer Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- which will engulf the Galaxy in fire and destruction, and possibly bring the Universe to a premature doom. I mean it,' he added. with luck I'll be drunk enough not to notice.' --- Ford ensuring everyone knew where his priorities lay. --- Douglas Adams, The Hitchhikers Guide to the Galaxy -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: intel text mode restore problem
On Fri, 2008-12-12 at 20:14 +0100, Norbert Preining wrote: > Where can I get this intel_reg_dumper from? Is there a tree to check > out, or a ready made binary from x86_64 (Debian/unstable)? > you can install the xserver-xorg-video-intel-dbg package, or build the reg dumper from the xf86-video-intel source tree. Cheers, Julien -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: intel text mode restore problem
Norbert Preining wrote: > Where can I get this intel_reg_dumper from? Is there a tree to check > out, or a ready made binary from x86_64 (Debian/unstable)? > It is residing in the git repository of the intel driver. Cheers, Johannes. -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: intel text mode restore problem
On Tue, 2008-12-09 at 19:11 +0100, Norbert Preining wrote: > Dear all, > > (please Cc) > > I would like to report two problems with the following system: > > Hardware: > Sony Vaio VGN-Z11 > Chipset Mobile Intel® GM45 Express Chipset found > (and in addition a nVidia chipset, both built into the laptop, > but via switch only intel one is selected) > > Software: > kernel 2.6.28-rc7 (and several kernels before) > Debian/sid: > xorg 7.3, xserver 1.4.2 > > There are two problems with this laptop: The first is that often (or > better always) when I start X and run it for some time (no idea what is > necessary), and then switch to the console the text mode is not > restored. The effect is that on the top of the screen there is probably > one of maybe two screen lines of the characters shown (screen lines > means 1 pixel lines) and the whole screen is flashing. The rest of the > screen is dark/grey and flashing. > > Interestingly. Doing from the text console a switch to X and back fixes > that for some time. But waiting a bit doing things in X and switching > again to the Console makes the effect re-appear. > > The other problem is that sometimes, hard to reproduce but it happens > again and again, gdm starts up with a bit strange dimensions: It > occupies a considerably smaller portion of the screen, as shown in the > attached screenshot. > > It would be great if we can track down the issues of that, or if that is > the wrong contact point please let me know who is responsible. If you > need any further data (dmesg, kernel config, X log file, ...) please let > me know. > > Thanks a lot and all the best For the first issue, it's often hard to tell what's going wrong as the registers will be the same as far as we can see between success and failure. The difficulty of recovering text mode is one of the reasons that text mode is going away with kernel modesetting (planned for 2.6.29). intel_reg_dumper from the 2d driver build tree may help debug what's different between success and failure of vt switching today. Second issue sounds like sometimes you get DDC and sometimes you don't, but when you don't there isn't BIOS data to fall back on so you end up using the console mode (which has a small active area, and we don't set scaling because we assume that that's the real 1:1 native mode). Xorg.0.log between success and failure would be the way to tell. -- Eric Anholt [EMAIL PROTECTED] [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
