FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu User

 
 
LinkBack Thread Tools
 
Old 01-16-2011, 11:10 PM
Nicolas Calderon
 
Default Screen blanks on lid close, never comes back

I have installed Ubuntu 10.10 on my ThinkPad R51 laptop, but have been having issues where the screen goes blank when I close the lid but never comes back. The computer is not crashed though, as I can still ssh in.




I tried 3 settings in power management: do nothing, blank screen and suspend.
To set power manager to do nothing, I had to set through gconf, so I'm not sure that option is valid.




Blank screen is a given option in power manager, and results in the described issue time after time.
Suspend can also lead to the issue if the lid is reopened too quickly (the laptop doesn't have the time to go to sleep).





I am left with the impression that this is a software issue (debian did not do that and I had it just before installing Ubuntu, but debian could not suspend) that leaves the video card state broken. I tried following instruction on to force pipe a quirck (https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen#Problem: Lockup When Closing Lid with Intel Graphics) because I have an intel graphics card, but xorg tells me this option is not used (WW in xorg.conf). I attached the output to a few files or command outputs:




lspci -vvnn | grep "VGA Compat":00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA controller])

�� � � �Subsystem: IBM Device [1014:0557]�� � � �Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-�� � � �Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+

�� � � �Latency: 0�� � � �Interrupt: pin A routed to IRQ 11�� � � �Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]�� � � �Region 1: Memory at d0000000 (32-bit, non-prefetchable) [size=512K]

�� � � �Region 2: I/O ports at 1800 [size=8]�� � � �Expansion ROM at <unassigned> [disabled]�� � � �Capabilities: [d0] Power Management version 1�� � � � � � � �Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

�� � � � � � � �Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-�� � � �Kernel driver in use: i915�� � � �Kernel modules: i915
/var/log/Xorg.0.log.old

http://pastebin.com/55uX0D1rNotable errors:[ � �24.110] (EE) VESA: Kernel modesetting driver in use, refusing to load

[ � �24.110] (WW) Falling back to old probe method for vesaand a few hundreds of:[ � �24.456] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument



intel_reg_dumper (good and bad state)attached, and here is the diff:110c110< � � � � � � VGACNTRL: 0x22040000 (enabled)---> � � � � � � VGACNTRL: 0x80000000 (disabled)


It might be worth noting that whenever I close the lid and reopen it (or just press the lid button), the screen comes visible for a fraction of second, but long enough for me to see that whatever needs to be shown gets updated (If I kill my gnome session through ssh, I can see gdm logging in that fraction of seconds). Also, it's not just an issue with the backlight as it does come back on on lid open, and stays on.



Someone on #ubuntu (Freenode) suggested it might have to do with ACPI. I tried moving /etc/acpi/lid.sh to /etc/acpi/lid.sh.bak, but it didn't seem to make a diffrence. I don't know enough about ACPI to rule it out though.



Thanks in advance,
--
Nicolas Calderon







DCC: 0x00000000 (single channel, XOR randomization: enabled, XOR bit: 11)
CHDECMISC: 0x00000000 (none, ch2 enh disabled, ch1 enh disabled, ch0 enh disabled, flex disabled, ep not present)
C0DRB0: 0x00000000 (0x0000)
C0DRB1: 0x00000000 (0x0000)
C0DRB2: 0x00000000 (0x0000)
C0DRB3: 0x00000000 (0x0000)
C1DRB0: 0x00000000 (0x0000)
C1DRB1: 0x00000000 (0x0000)
C1DRB2: 0x00000000 (0x0000)
C1DRB3: 0x00000000 (0x0000)
C0DRA01: 0x00000000 (0x0000)
C0DRA23: 0x00000000 (0x0000)
C1DRA01: 0x00000000 (0x0000)
C1DRA23: 0x00000000 (0x0000)
PGETBL_CTL: 0x3fee0001
VCLK_DIVISOR_VGA0: 0x00021207 (n = 2, m1 = 18, m2 = 7)
VCLK_DIVISOR_VGA1: 0x00031406 (n = 3, m1 = 20, m2 = 6)
VCLK_POST_DIV: 0x0000888b (vga0 p1 = 13, p2 = 4, vga1 p1 = 10, p2 = 4)
DPLL_TEST: 0x00000000 (, DPLLA input buffer disabled, DPLLB input buffer disabled)
CACHE_MODE_0: 0x00000000
D_STATE: 0x0000030f
DSPCLK_GATE_D: 0x00000000 (clock gates disabled
RENCLK_GATE_D1: 0x00000001
RENCLK_GATE_D2: 0x00000000
SDVOB: 0x00000000 (disabled, pipe A, stall disabled, not detected)
SDVOC: 0x00000000 (disabled, pipe A, stall disabled, not detected)
SDVOUDI: 0x00000000
DSPARB: 0x00015455
DSPFW1: 0x00000000
DSPFW2: 0x00000000
DSPFW3: 0x00000000
ADPA: 0x00000c00 (disabled, pipe A, -hsync, -vsync)
LVDS: 0xc0000300 (enabled, pipe B, 18 bit, 1 channel)
DVOA: 0x00000000 (disabled, pipe A, no stall, -hsync, -vsync)
DVOB: 0x00000000 (disabled, pipe A, no stall, -hsync, -vsync)
DVOC: 0x00000000 (disabled, pipe A, no stall, -hsync, -vsync)
DVOA_SRCDIM: 0x00000000
DVOB_SRCDIM: 0x00000000
DVOC_SRCDIM: 0x00000000
PP_CONTROL: 0x00000001 (power target: on)
PP_STATUS: 0xc0000008 (on, ready, sequencing idle)
PP_ON_DELAYS: 0x00fa09c4
PP_OFF_DELAYS: 0x00fa09c4
PP_DIVISOR: 0x0030d304
PFIT_CONTROL: 0x00000008
PFIT_PGM_RATIOS: 0x00000000
PORT_HOTPLUG_EN: 0x00000000
PORT_HOTPLUG_STAT: 0x00000000
DSPACNTR: 0x40000000 (disabled, pipe A)
DSPASTRIDE: 0x00000000 (0 bytes)
DSPAPOS: 0x00000000 (0, 0)
DSPASIZE: 0x01df027f (640, 480)
DSPABASE: 0x00000000
DSPASURF: 0x00000000
DSPATILEOFF: 0x00000000
PIPEACONF: 0x80000000 (enabled, single-wide)
PIPEASRC: 0x027f01df (640, 480)
PIPEASTAT: 0x80000207 (status: FIFO_UNDERRUN VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS)
PIPEA_GMCH_DATA_M: 0x00000000
PIPEA_GMCH_DATA_N: 0x00000000
PIPEA_DP_LINK_M: 0x00000000
PIPEA_DP_LINK_N: 0x00000000
CURSOR_A_BASE: 0x00000000
CURSOR_A_CONTROL: 0x00000000
CURSOR_A_POSITION: 0x00000000
FPA0: 0x0004140e (n = 4, m1 = 20, m2 = 14)
FPA1: 0x0004140e (n = 4, m1 = 20, m2 = 14)
DPLL_A: 0x90860000 (enabled, non-dvo, default clock, DAC/serial mode, p1 = 8, p2 = 4)
DPLL_A_MD: 0x00000000
HTOTAL_A: 0x033f027f (640 active, 832 total)
HBLANK_A: 0x033f027f (640 start, 832 end)
HSYNC_A: 0x02bf0297 (664 start, 704 end)
VTOTAL_A: 0x020701df (480 active, 520 total)
VBLANK_A: 0x020701df (480 start, 520 end)
VSYNC_A: 0x01ea01e8 (489 start, 491 end)
BCLRPAT_A: 0x00000000
VSYNCSHIFT_A: 0x00000000
DSPBCNTR: 0xd9000000 (enabled, pipe B)
DSPBSTRIDE: 0x00001000 (4096 bytes)
DSPBPOS: 0x00000000 (0, 0)
DSPBSIZE: 0x02ff03ff (1024, 768)
DSPBBASE: 0x00800000
DSPBSURF: 0x00000000
DSPBTILEOFF: 0x00000000
PIPEBCONF: 0x80000000 (enabled, single-wide)
PIPEBSRC: 0x03ff02ff (1024, 768)
PIPEBSTAT: 0x00000202 (status: VSYNC_INT_STATUS VBLANK_INT_STATUS)
PIPEB_GMCH_DATA_M: 0x00000000
PIPEB_GMCH_DATA_N: 0x00000000
PIPEB_DP_LINK_M: 0x00000000
PIPEB_DP_LINK_N: 0x00000000
CURSOR_B_BASE: 0x00000000
CURSOR_B_CONTROL: 0x00000000
CURSOR_B_POSITION: 0x00000000
FPB0: 0x0007140f (n = 7, m1 = 20, m2 = 15)
FPB1: 0x0007140f (n = 7, m1 = 20, m2 = 15)
DPLL_B: 0x90016000 (enabled, non-dvo, spread spectrum clock, LVDS mode, p1 = 1, p2 = 14)
DPLL_B_MD: 0x00000000
HTOTAL_B: 0x053f03ff (1024 active, 1344 total)
HBLANK_B: 0x053f03ff (1024 start, 1344 end)
HSYNC_B: 0x049f0417 (1048 start, 1184 end)
VTOTAL_B: 0x032502ff (768 active, 806 total)
VBLANK_B: 0x032502ff (768 start, 806 end)
VSYNC_B: 0x03080302 (771 start, 777 end)
BCLRPAT_B: 0x00000000
VSYNCSHIFT_B: 0x00000000
VCLK_DIVISOR_VGA0: 0x00021207
VCLK_DIVISOR_VGA1: 0x00031406
VCLK_POST_DIV: 0x0000888b
VGACNTRL: 0x22040000 (enabled)
TV_CTL: 0x00000000
TV_DAC: 0x00000000
TV_CSC_Y: 0x00000000
TV_CSC_Y2: 0x00000000
TV_CSC_U: 0x00000000
TV_CSC_U2: 0x00000000
TV_CSC_V: 0x00000000
TV_CSC_V2: 0x00000000
TV_CLR_KNOBS: 0x00000000
TV_CLR_LEVEL: 0x00000000
TV_H_CTL_1: 0x00000000
TV_H_CTL_2: 0x00000000
TV_H_CTL_3: 0x00000000
TV_V_CTL_1: 0x00000000
TV_V_CTL_2: 0x00000000
TV_V_CTL_3: 0x00000000
TV_V_CTL_4: 0x00000000
TV_V_CTL_5: 0x00000000
TV_V_CTL_6: 0x00000000
TV_V_CTL_7: 0x00000000
TV_SC_CTL_1: 0x00000000
TV_SC_CTL_2: 0x00000000
TV_SC_CTL_3: 0x00000000
TV_WIN_POS: 0x00000000
TV_WIN_SIZE: 0x00000000
TV_FILTER_CTL_1: 0x00000000
TV_FILTER_CTL_2: 0x00000000
TV_FILTER_CTL_3: 0x00000000
TV_CC_CONTROL: 0x00000000
TV_CC_DATA: 0x00000000
TV_H_LUMA_0: 0x00000000
TV_H_LUMA_59: 0x00000000
TV_H_CHROMA_0: 0x00000000
TV_H_CHROMA_59: 0x00000000
FBC_CFB_BASE: 0x00000000
FBC_LL_BASE: 0x00000000
FBC_CONTROL: 0x00000000
FBC_COMMAND: 0x00000000
FBC_STATUS: 0x20000000
FBC_CONTROL2: 0x00000000
FBC_FENCE_OFF: 0x00000000
FBC_MOD_NUM: 0x00000000
MI_MODE: 0x00000000
MI_ARB_STATE: 0x00000000
MI_RDRET_STATE: 0x00000000
ECOSKPD: 0x00000307
DP_B: 0x00000000
DPB_AUX_CH_CTL: 0x00000000
DPB_AUX_CH_DATA1: 0x00000000
DPB_AUX_CH_DATA2: 0x00000000
DPB_AUX_CH_DATA3: 0x00000000
DPB_AUX_CH_DATA4: 0x00000000
DPB_AUX_CH_DATA5: 0x00000000
DP_C: 0x00000000
DPC_AUX_CH_CTL: 0x00000000
DPC_AUX_CH_DATA1: 0x00000000
DPC_AUX_CH_DATA2: 0x00000000
DPC_AUX_CH_DATA3: 0x00000000
DPC_AUX_CH_DATA4: 0x00000000
DPC_AUX_CH_DATA5: 0x00000000
DP_D: 0x00000000
DPD_AUX_CH_CTL: 0x00000000
DPD_AUX_CH_DATA1: 0x00000000
DPD_AUX_CH_DATA2: 0x00000000
DPD_AUX_CH_DATA3: 0x00000000
DPD_AUX_CH_DATA4: 0x00000000
DPD_AUX_CH_DATA5: 0x00000000
AUD_CONFIG: 0x00000000
AUD_HDMIW_STATUS: 0x00000000
AUD_CONV_CHCNT: 0x00000000
VIDEO_DIP_CTL: 0x00000000
AUD_PINW_CNTR: 0x00000000
AUD_CNTL_ST: 0x00000000
AUD_PIN_CAP: 0x00000000
AUD_PINW_CAP: 0x00000000
AUD_PINW_UNSOLRESP: 0x00000000
AUD_OUT_DIG_CNVT: 0x00000000
AUD_OUT_CWCAP: 0x00000000
AUD_GRP_CAP: 0x00000000
FENCE 0: 0x00000000 (disabled)
FENCE 1: 0x00000000 (disabled)
FENCE 2: 0x00000000 (disabled)
FENCE 3: 0x00000000 (disabled)
FENCE 4: 0x00000000 (disabled)
FENCE 5: 0x00000000 (disabled)
FENCE 6: 0x00000000 (disabled)
FENCE 7: 0x00000000 (disabled)
FENCE 8: 0x00000000 (disabled)
FENCE 9: 0x00000000 (disabled)
FENCE 10: 0x00000000 (disabled)
FENCE 11: 0x00000000 (disabled)
FENCE 12: 0x00000000 (disabled)
FENCE 13: 0x00000000 (disabled)
FENCE 14: 0x00000000 (disabled)
FENCE 15: 0x00000000 (disabled)
INST_PM: 0x00000000
pipe A dot 31500 n 4 m1 20 m2 14 p1 8 p2 4
pipe B dot 66523 n 7 m1 20 m2 15 p1 1 p2 14
DCC: 0x00000000 (single channel, XOR randomization: enabled, XOR bit: 11)
CHDECMISC: 0x00000000 (none, ch2 enh disabled, ch1 enh disabled, ch0 enh disabled, flex disabled, ep not present)
C0DRB0: 0x00000000 (0x0000)
C0DRB1: 0x00000000 (0x0000)
C0DRB2: 0x00000000 (0x0000)
C0DRB3: 0x00000000 (0x0000)
C1DRB0: 0x00000000 (0x0000)
C1DRB1: 0x00000000 (0x0000)
C1DRB2: 0x00000000 (0x0000)
C1DRB3: 0x00000000 (0x0000)
C0DRA01: 0x00000000 (0x0000)
C0DRA23: 0x00000000 (0x0000)
C1DRA01: 0x00000000 (0x0000)
C1DRA23: 0x00000000 (0x0000)
PGETBL_CTL: 0x3fee0001
VCLK_DIVISOR_VGA0: 0x00021207 (n = 2, m1 = 18, m2 = 7)
VCLK_DIVISOR_VGA1: 0x00031406 (n = 3, m1 = 20, m2 = 6)
VCLK_POST_DIV: 0x0000888b (vga0 p1 = 13, p2 = 4, vga1 p1 = 10, p2 = 4)
DPLL_TEST: 0x00000000 (, DPLLA input buffer disabled, DPLLB input buffer disabled)
CACHE_MODE_0: 0x00000000
D_STATE: 0x0000030f
DSPCLK_GATE_D: 0x00000000 (clock gates disabled
RENCLK_GATE_D1: 0x00000001
RENCLK_GATE_D2: 0x00000000
SDVOB: 0x00000000 (disabled, pipe A, stall disabled, not detected)
SDVOC: 0x00000000 (disabled, pipe A, stall disabled, not detected)
SDVOUDI: 0x00000000
DSPARB: 0x00015455
DSPFW1: 0x00000000
DSPFW2: 0x00000000
DSPFW3: 0x00000000
ADPA: 0x00000c00 (disabled, pipe A, -hsync, -vsync)
LVDS: 0xc0000300 (enabled, pipe B, 18 bit, 1 channel)
DVOA: 0x00000000 (disabled, pipe A, no stall, -hsync, -vsync)
DVOB: 0x00000000 (disabled, pipe A, no stall, -hsync, -vsync)
DVOC: 0x00000000 (disabled, pipe A, no stall, -hsync, -vsync)
DVOA_SRCDIM: 0x00000000
DVOB_SRCDIM: 0x00000000
DVOC_SRCDIM: 0x00000000
PP_CONTROL: 0x00000001 (power target: on)
PP_STATUS: 0xc0000008 (on, ready, sequencing idle)
PP_ON_DELAYS: 0x00fa09c4
PP_OFF_DELAYS: 0x00fa09c4
PP_DIVISOR: 0x0030d304
PFIT_CONTROL: 0x00000008
PFIT_PGM_RATIOS: 0x00000000
PORT_HOTPLUG_EN: 0x00000000
PORT_HOTPLUG_STAT: 0x00000000
DSPACNTR: 0x40000000 (disabled, pipe A)
DSPASTRIDE: 0x00000000 (0 bytes)
DSPAPOS: 0x00000000 (0, 0)
DSPASIZE: 0x01df027f (640, 480)
DSPABASE: 0x00000000
DSPASURF: 0x00000000
DSPATILEOFF: 0x00000000
PIPEACONF: 0x80000000 (enabled, single-wide)
PIPEASRC: 0x027f01df (640, 480)
PIPEASTAT: 0x80000207 (status: FIFO_UNDERRUN VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS)
PIPEA_GMCH_DATA_M: 0x00000000
PIPEA_GMCH_DATA_N: 0x00000000
PIPEA_DP_LINK_M: 0x00000000
PIPEA_DP_LINK_N: 0x00000000
CURSOR_A_BASE: 0x00000000
CURSOR_A_CONTROL: 0x00000000
CURSOR_A_POSITION: 0x00000000
FPA0: 0x0004140e (n = 4, m1 = 20, m2 = 14)
FPA1: 0x0004140e (n = 4, m1 = 20, m2 = 14)
DPLL_A: 0x90860000 (enabled, non-dvo, default clock, DAC/serial mode, p1 = 8, p2 = 4)
DPLL_A_MD: 0x00000000
HTOTAL_A: 0x033f027f (640 active, 832 total)
HBLANK_A: 0x033f027f (640 start, 832 end)
HSYNC_A: 0x02bf0297 (664 start, 704 end)
VTOTAL_A: 0x020701df (480 active, 520 total)
VBLANK_A: 0x020701df (480 start, 520 end)
VSYNC_A: 0x01ea01e8 (489 start, 491 end)
BCLRPAT_A: 0x00000000
VSYNCSHIFT_A: 0x00000000
DSPBCNTR: 0xd9000000 (enabled, pipe B)
DSPBSTRIDE: 0x00001000 (4096 bytes)
DSPBPOS: 0x00000000 (0, 0)
DSPBSIZE: 0x02ff03ff (1024, 768)
DSPBBASE: 0x00800000
DSPBSURF: 0x00000000
DSPBTILEOFF: 0x00000000
PIPEBCONF: 0x80000000 (enabled, single-wide)
PIPEBSRC: 0x03ff02ff (1024, 768)
PIPEBSTAT: 0x00000202 (status: VSYNC_INT_STATUS VBLANK_INT_STATUS)
PIPEB_GMCH_DATA_M: 0x00000000
PIPEB_GMCH_DATA_N: 0x00000000
PIPEB_DP_LINK_M: 0x00000000
PIPEB_DP_LINK_N: 0x00000000
CURSOR_B_BASE: 0x00000000
CURSOR_B_CONTROL: 0x00000000
CURSOR_B_POSITION: 0x00000000
FPB0: 0x0007140f (n = 7, m1 = 20, m2 = 15)
FPB1: 0x0007140f (n = 7, m1 = 20, m2 = 15)
DPLL_B: 0x90016000 (enabled, non-dvo, spread spectrum clock, LVDS mode, p1 = 1, p2 = 14)
DPLL_B_MD: 0x00000000
HTOTAL_B: 0x053f03ff (1024 active, 1344 total)
HBLANK_B: 0x053f03ff (1024 start, 1344 end)
HSYNC_B: 0x049f0417 (1048 start, 1184 end)
VTOTAL_B: 0x032502ff (768 active, 806 total)
VBLANK_B: 0x032502ff (768 start, 806 end)
VSYNC_B: 0x03080302 (771 start, 777 end)
BCLRPAT_B: 0x00000000
VSYNCSHIFT_B: 0x00000000
VCLK_DIVISOR_VGA0: 0x00021207
VCLK_DIVISOR_VGA1: 0x00031406
VCLK_POST_DIV: 0x0000888b
VGACNTRL: 0x80000000 (disabled)
TV_CTL: 0x00000000
TV_DAC: 0x00000000
TV_CSC_Y: 0x00000000
TV_CSC_Y2: 0x00000000
TV_CSC_U: 0x00000000
TV_CSC_U2: 0x00000000
TV_CSC_V: 0x00000000
TV_CSC_V2: 0x00000000
TV_CLR_KNOBS: 0x00000000
TV_CLR_LEVEL: 0x00000000
TV_H_CTL_1: 0x00000000
TV_H_CTL_2: 0x00000000
TV_H_CTL_3: 0x00000000
TV_V_CTL_1: 0x00000000
TV_V_CTL_2: 0x00000000
TV_V_CTL_3: 0x00000000
TV_V_CTL_4: 0x00000000
TV_V_CTL_5: 0x00000000
TV_V_CTL_6: 0x00000000
TV_V_CTL_7: 0x00000000
TV_SC_CTL_1: 0x00000000
TV_SC_CTL_2: 0x00000000
TV_SC_CTL_3: 0x00000000
TV_WIN_POS: 0x00000000
TV_WIN_SIZE: 0x00000000
TV_FILTER_CTL_1: 0x00000000
TV_FILTER_CTL_2: 0x00000000
TV_FILTER_CTL_3: 0x00000000
TV_CC_CONTROL: 0x00000000
TV_CC_DATA: 0x00000000
TV_H_LUMA_0: 0x00000000
TV_H_LUMA_59: 0x00000000
TV_H_CHROMA_0: 0x00000000
TV_H_CHROMA_59: 0x00000000
FBC_CFB_BASE: 0x00000000
FBC_LL_BASE: 0x00000000
FBC_CONTROL: 0x00000000
FBC_COMMAND: 0x00000000
FBC_STATUS: 0x20000000
FBC_CONTROL2: 0x00000000
FBC_FENCE_OFF: 0x00000000
FBC_MOD_NUM: 0x00000000
MI_MODE: 0x00000000
MI_ARB_STATE: 0x00000000
MI_RDRET_STATE: 0x00000000
ECOSKPD: 0x00000307
DP_B: 0x00000000
DPB_AUX_CH_CTL: 0x00000000
DPB_AUX_CH_DATA1: 0x00000000
DPB_AUX_CH_DATA2: 0x00000000
DPB_AUX_CH_DATA3: 0x00000000
DPB_AUX_CH_DATA4: 0x00000000
DPB_AUX_CH_DATA5: 0x00000000
DP_C: 0x00000000
DPC_AUX_CH_CTL: 0x00000000
DPC_AUX_CH_DATA1: 0x00000000
DPC_AUX_CH_DATA2: 0x00000000
DPC_AUX_CH_DATA3: 0x00000000
DPC_AUX_CH_DATA4: 0x00000000
DPC_AUX_CH_DATA5: 0x00000000
DP_D: 0x00000000
DPD_AUX_CH_CTL: 0x00000000
DPD_AUX_CH_DATA1: 0x00000000
DPD_AUX_CH_DATA2: 0x00000000
DPD_AUX_CH_DATA3: 0x00000000
DPD_AUX_CH_DATA4: 0x00000000
DPD_AUX_CH_DATA5: 0x00000000
AUD_CONFIG: 0x00000000
AUD_HDMIW_STATUS: 0x00000000
AUD_CONV_CHCNT: 0x00000000
VIDEO_DIP_CTL: 0x00000000
AUD_PINW_CNTR: 0x00000000
AUD_CNTL_ST: 0x00000000
AUD_PIN_CAP: 0x00000000
AUD_PINW_CAP: 0x00000000
AUD_PINW_UNSOLRESP: 0x00000000
AUD_OUT_DIG_CNVT: 0x00000000
AUD_OUT_CWCAP: 0x00000000
AUD_GRP_CAP: 0x00000000
FENCE 0: 0x00000000 (disabled)
FENCE 1: 0x00000000 (disabled)
FENCE 2: 0x00000000 (disabled)
FENCE 3: 0x00000000 (disabled)
FENCE 4: 0x00000000 (disabled)
FENCE 5: 0x00000000 (disabled)
FENCE 6: 0x00000000 (disabled)
FENCE 7: 0x00000000 (disabled)
FENCE 8: 0x00000000 (disabled)
FENCE 9: 0x00000000 (disabled)
FENCE 10: 0x00000000 (disabled)
FENCE 11: 0x00000000 (disabled)
FENCE 12: 0x00000000 (disabled)
FENCE 13: 0x00000000 (disabled)
FENCE 14: 0x00000000 (disabled)
FENCE 15: 0x00000000 (disabled)
INST_PM: 0x00000000
pipe A dot 31500 n 4 m1 20 m2 14 p1 8 p2 4
pipe B dot 66523 n 7 m1 20 m2 15 p1 1 p2 14
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 01-17-2011, 07:24 AM
Colin Law
 
Default Screen blanks on lid close, never comes back

On 17 January 2011 00:10, Nicolas Calderon
<nicolas.calderon.asselin@gmail.com> wrote:
> I have installed Ubuntu 10.10 on my ThinkPad R51 laptop, but have been
> having issues where the screen goes blank when I close the lid but never
> comes back. The computer is not crashed though, as I can still ssh in.
> I tried 3 settings in power management: do nothing, blank screen and
> suspend.

Where in Power Management are you setting this? The options I have on
the Mains and Battery tabs for "When laptop lid is closed" are
Suspend, Hibernate and Shutdown.

Assuming that you want it to suspend, if you select Suspend from the
shutdown menu directly, without closing the lid, does that work ok?
If not then the issue is to do with suspend rather than the lid
operation.

Colin

> To set power manager to do nothing, I had to set through gconf, so I'm not
> sure that option is valid.
> Blank screen is a given option in power manager, and results in the
> described issue time after time.
> Suspend can also lead to the issue if the lid is reopened too quickly (the
> laptop doesn't have the time to go to sleep).
>
> I am left with the impression that this is a software issue (debian did not
> do that and I had it just before installing Ubuntu, but debian could not
> suspend) that leaves the video card state broken. I tried following
> instruction on to force pipe a quirck
> (https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen#Problem: Lockup When
> Closing Lid with Intel Graphics) because I have an intel graphics card, but
> xorg tells me this option is not used (WW in xorg.conf). I attached the
> output to a few files or command outputs:
> lspci -vvnn | grep "VGA Compat":
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
> Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA
> controller])
> ** * * *Subsystem: IBM Device [1014:0557]
> ** * * *Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> ** * * *Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx+
> ** * * *Latency: 0
> ** * * *Interrupt: pin A routed to IRQ 11
> ** * * *Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
> ** * * *Region 1: Memory at d0000000 (32-bit, non-prefetchable) [size=512K]
> ** * * *Region 2: I/O ports at 1800 [size=8]
> ** * * *Expansion ROM at <unassigned> [disabled]
> ** * * *Capabilities: [d0] Power Management version 1
> ** * * * * * * *Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> ** * * * * * * *Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> ** * * *Kernel driver in use: i915
> ** * * *Kernel modules: i915
> /var/log/Xorg.0.log.old
> http://pastebin.com/55uX0D1r
> Notable errors:
> [ * *24.110] (EE) VESA: Kernel modesetting driver in use, refusing to load
> [ * *24.110] (WW) Falling back to old probe method for vesa
> and a few hundreds of:
> [ * *24.456] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
>
> intel_reg_dumper (good and bad state)
> attached, and here is the diff:
> 110c110
> < * * * * * * VGACNTRL: 0x22040000 (enabled)
> ---
>> * * * * * * VGACNTRL: 0x80000000 (disabled)
> It might be worth noting that whenever I close the lid and reopen it (or
> just press the lid button), the screen comes visible for a fraction of
> second, but long enough for me to see that whatever needs to be shown gets
> updated (If I kill my gnome session through ssh, I can see gdm logging in
> that fraction of seconds). Also, it's not just an issue with the backlight
> as it does come back on on lid open, and stays on.
> Someone on #ubuntu (Freenode) suggested it might have to do with ACPI. I
> tried moving /etc/acpi/lid.sh to /etc/acpi/lid.sh.bak, but it didn't seem to
> make a diffrence. I don't know enough about ACPI to rule it out though.
> Thanks in advance,
> --
> Nicolas Calderon
>
>
>
> --
> ubuntu-users mailing list
> ubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
>

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 01-17-2011, 08:32 PM
Nicolas Calderon
 
Default Screen blanks on lid close, never comes back

The issue is not with suspending but with screen blanking.
Power Manager (AC and Battery) do not offer the option to do nothing on lid close ("When lid is closed"), but I tried it by setting it in gconf.*


As far as suspend goes, I was simply saying that I observe the same issue if I close and reopen the lid quickly. If I let the laptop suspend and resume, the screen comes back correctly. But I don't want my laptop to suspend when the lid is closed.


--
Nicolas Calderon




On Mon, Jan 17, 2011 at 3:24 AM, Colin Law <clanlaw@googlemail.com> wrote:



On 17 January 2011 00:10, Nicolas Calderon

<nicolas.calderon.asselin@gmail.com> wrote:

> I have installed Ubuntu 10.10 on my ThinkPad R51 laptop, but have been

> having issues where the screen goes blank when I close the lid but never

> comes back. The computer is not crashed though, as I can still ssh in.

> I tried 3 settings in power management: do nothing, blank screen and

> suspend.



Where in Power Management are you setting this? *The options I have on

the Mains and Battery tabs for "When laptop lid is closed" are

Suspend, Hibernate and Shutdown.



Assuming that you want it to suspend, if you select Suspend from the

shutdown menu directly, without closing the lid, does that work ok?

If not then the issue is to do with suspend rather than the lid

operation.



Colin



> To set power manager to do nothing, I had to set through gconf, so I'm not

> sure that option is valid.

> Blank screen is a given option in power manager, and results in the

> described issue time after time.

> Suspend can also lead to the issue if the lid is reopened too quickly (the

> laptop doesn't have the time to go to sleep).

>

> I am left with the impression that this is a software issue (debian did not

> do that and I had it just before installing Ubuntu, but debian could not

> suspend) that leaves the video card state broken. I tried following

> instruction on to force pipe a quirck

> (https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen#Problem: Lockup When

> Closing Lid with Intel Graphics) because I have an intel graphics card, but

> xorg tells me this option is not used (WW in xorg.conf). I attached the

> output to a few files or command outputs:

> lspci -vvnn | grep "VGA Compat":

> 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM

> Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA

> controller])

> ** * * *Subsystem: IBM Device [1014:0557]

> ** * * *Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-

> Stepping- SERR- FastB2B- DisINTx-

> ** * * *Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-

> <TAbort- <MAbort- >SERR- <PERR- INTx+

> ** * * *Latency: 0

> ** * * *Interrupt: pin A routed to IRQ 11

> ** * * *Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]

> ** * * *Region 1: Memory at d0000000 (32-bit, non-prefetchable) [size=512K]

> ** * * *Region 2: I/O ports at 1800 [size=8]

> ** * * *Expansion ROM at <unassigned> [disabled]

> ** * * *Capabilities: [d0] Power Management version 1

> ** * * * * * * *Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA

> PME(D0-,D1-,D2-,D3hot-,D3cold-)

> ** * * * * * * *Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-

> ** * * *Kernel driver in use: i915

> ** * * *Kernel modules: i915

> /var/log/Xorg.0.log.old

> http://pastebin.com/55uX0D1r

> Notable errors:

> [ * *24.110] (EE) VESA: Kernel modesetting driver in use, refusing to load

> [ * *24.110] (WW) Falling back to old probe method for vesa

> and a few hundreds of:

> [ * *24.456] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument

>

> intel_reg_dumper (good and bad state)

> attached, and here is the diff:

> 110c110

> < * * * * * * VGACNTRL: 0x22040000 (enabled)

> ---

>> * * * * * * VGACNTRL: 0x80000000 (disabled)

> It might be worth noting that whenever I close the lid and reopen it (or

> just press the lid button), the screen comes visible for a fraction of

> second, but long enough for me to see that whatever needs to be shown gets

> updated (If I kill my gnome session through ssh, I can see gdm logging in

> that fraction of seconds). Also, it's not just an issue with the backlight

> as it does come back on on lid open, and stays on.

> Someone on #ubuntu (Freenode) suggested it might have to do with ACPI. I

> tried moving /etc/acpi/lid.sh to /etc/acpi/lid.sh.bak, but it didn't seem to

> make a diffrence. I don't know enough about ACPI to rule it out though.

> Thanks in advance,

> --

> Nicolas Calderon

>

>

>

> --

> ubuntu-users mailing list

> ubuntu-users@lists.ubuntu.com

> Modify settings or unsubscribe at:

> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

>

>



--

ubuntu-users mailing list

ubuntu-users@lists.ubuntu.com

Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 01-17-2011, 09:02 PM
Colin Law
 
Default Screen blanks on lid close, never comes back

On 17 January 2011 21:32, Nicolas Calderon
<nicolas.calderon.asselin@gmail.com> wrote:

Please don't top post, it makes it difficult to folllow the thread,
insert your reply at appropriate points in previous message. Thanks.

> The issue is not with suspending but with screen blanking.
> Power Manager (AC and Battery) do not offer the option to do nothing on lid
> close ("When lid is closed"), but I tried it by setting it in gconf.
> As far as suspend goes, I was simply saying that I observe the same issue if
> I close and reopen the lid quickly. If I let the laptop suspend and resume,
> the screen comes back correctly. But I don't want my laptop to suspend when
> the lid is closed.

In that case I am confused. Is the screen blanking by itself or is it
the screensaver or what? Please try and explain simply (so I can
understand) what you do and what happens.

I think there might be heating issues if you were allowed to do
nothing on lid closure.

Colin

> --
> Nicolas Calderon
>
>
>
> On Mon, Jan 17, 2011 at 3:24 AM, Colin Law <clanlaw@googlemail.com> wrote:
>>
>> On 17 January 2011 00:10, Nicolas Calderon
>> <nicolas.calderon.asselin@gmail.com> wrote:
>> > I have installed Ubuntu 10.10 on my ThinkPad R51 laptop, but have been
>> > having issues where the screen goes blank when I close the lid but never
>> > comes back. The computer is not crashed though, as I can still ssh in.
>> > I tried 3 settings in power management: do nothing, blank screen and
>> > suspend.
>>
>> Where in Power Management are you setting this? *The options I have on
>> the Mains and Battery tabs for "When laptop lid is closed" are
>> Suspend, Hibernate and Shutdown.
>>
>> Assuming that you want it to suspend, if you select Suspend from the
>> shutdown menu directly, without closing the lid, does that work ok?
>> If not then the issue is to do with suspend rather than the lid
>> operation.
>>
>> Colin
>>
>> > To set power manager to do nothing, I had to set through gconf, so I'm
>> > not
>> > sure that option is valid.
>> > Blank screen is a given option in power manager, and results in the
>> > described issue time after time.
>> > Suspend can also lead to the issue if the lid is reopened too quickly
>> > (the
>> > laptop doesn't have the time to go to sleep).
>> >
>> > I am left with the impression that this is a software issue (debian did
>> > not
>> > do that and I had it just before installing Ubuntu, but debian could not
>> > suspend) that leaves the video card state broken. I tried following
>> > instruction on to force pipe a quirck
>> > (https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen#Problem: Lockup
>> > When
>> > Closing Lid with Intel Graphics) because I have an intel graphics card,
>> > but
>> > xorg tells me this option is not used (WW in xorg.conf). I attached the
>> > output to a few files or command outputs:
>> > lspci -vvnn | grep "VGA Compat":
>> > 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
>> > Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA
>> > controller])
>> > ** * * *Subsystem: IBM Device [1014:0557]
>> > ** * * *Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>> > ParErr-
>> > Stepping- SERR- FastB2B- DisINTx-
>> > ** * * *Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
>> > <TAbort- <MAbort- >SERR- <PERR- INTx+
>> > ** * * *Latency: 0
>> > ** * * *Interrupt: pin A routed to IRQ 11
>> > ** * * *Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
>> > ** * * *Region 1: Memory at d0000000 (32-bit, non-prefetchable)
>> > [size=512K]
>> > ** * * *Region 2: I/O ports at 1800 [size=8]
>> > ** * * *Expansion ROM at <unassigned> [disabled]
>> > ** * * *Capabilities: [d0] Power Management version 1
>> > ** * * * * * * *Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA
>> > PME(D0-,D1-,D2-,D3hot-,D3cold-)
>> > ** * * * * * * *Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>> > ** * * *Kernel driver in use: i915
>> > ** * * *Kernel modules: i915
>> > /var/log/Xorg.0.log.old
>> > http://pastebin.com/55uX0D1r
>> > Notable errors:
>> > [ * *24.110] (EE) VESA: Kernel modesetting driver in use, refusing to
>> > load
>> > [ * *24.110] (WW) Falling back to old probe method for vesa
>> > and a few hundreds of:
>> > [ * *24.456] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
>> >
>> > intel_reg_dumper (good and bad state)
>> > attached, and here is the diff:
>> > 110c110
>> > < * * * * * * VGACNTRL: 0x22040000 (enabled)
>> > ---
>> >> * * * * * * VGACNTRL: 0x80000000 (disabled)
>> > It might be worth noting that whenever I close the lid and reopen it (or
>> > just press the lid button), the screen comes visible for a fraction of
>> > second, but long enough for me to see that whatever needs to be shown
>> > gets
>> > updated (If I kill my gnome session through ssh, I can see gdm logging
>> > in
>> > that fraction of seconds). Also, it's not just an issue with the
>> > backlight
>> > as it does come back on on lid open, and stays on.
>> > Someone on #ubuntu (Freenode) suggested it might have to do with ACPI. I
>> > tried moving /etc/acpi/lid.sh to /etc/acpi/lid.sh.bak, but it didn't
>> > seem to
>> > make a diffrence. I don't know enough about ACPI to rule it out though.
>> > Thanks in advance,
>> > --
>> > Nicolas Calderon
>> >
>> >
>> >
>> > --
>> > ubuntu-users mailing list
>> > ubuntu-users@lists.ubuntu.com
>> > Modify settings or unsubscribe at:
>> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>> >
>> >
>>
>> --
>> ubuntu-users mailing list
>> ubuntu-users@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
>

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 01-18-2011, 02:02 AM
Nicolas Calderon
 
Default Screen blanks on lid close, never comes back

On Mon, Jan 17, 2011 at 5:02 PM, Colin Law <clanlaw@googlemail.com> wrote:
>
> On 17 January 2011 21:32, Nicolas Calderon
> <nicolas.calderon.asselin@gmail.com> wrote:
>
> Please don't top post, it makes it difficult to folllow the thread,
> insert your reply at appropriate points in previous message. *Thanks.
>
> > The issue is not with suspending but with screen blanking.
> > Power Manager (AC and Battery) do not offer the option to do nothing on lid
> > close ("When lid is closed"), but I tried it by setting it in gconf.
> > As far as suspend goes, I was simply saying that I observe the same issue if
> > I close and reopen the lid quickly. If I let the laptop suspend and resume,
> > the screen comes back correctly. But I don't want my laptop to suspend when
> > the lid is closed.
>
> In that case I am confused. *Is the screen blanking by itself or is it
> the screensaver or what? *Please try and explain simply (so I can
> understand) what you do and what happens.
>
> I think there might be heating issues if you were allowed to do
> nothing on lid closure.
>
> Colin
>
> > --
> > Nicolas Calderon
> >
> >
> >
> > On Mon, Jan 17, 2011 at 3:24 AM, Colin Law <clanlaw@googlemail.com> wrote:
> >>
> >> On 17 January 2011 00:10, Nicolas Calderon
> >> <nicolas.calderon.asselin@gmail.com> wrote:
> >> > I have installed Ubuntu 10.10 on my ThinkPad R51 laptop, but have been
> >> > having issues where the screen goes blank when I close the lid but never
> >> > comes back. The computer is not crashed though, as I can still ssh in.
> >> > I tried 3 settings in power management: do nothing, blank screen and
> >> > suspend.
> >>
> >> Where in Power Management are you setting this? *The options I have on
> >> the Mains and Battery tabs for "When laptop lid is closed" are
> >> Suspend, Hibernate and Shutdown.
> >>
> >> Assuming that you want it to suspend, if you select Suspend from the
> >> shutdown menu directly, without closing the lid, does that work ok?
> >> If not then the issue is to do with suspend rather than the lid
> >> operation.
> >>
> >> Colin
> >>
> >> > To set power manager to do nothing, I had to set through gconf, so I'm
> >> > not
> >> > sure that option is valid.
> >> > Blank screen is a given option in power manager, and results in the
> >> > described issue time after time.
> >> > Suspend can also lead to the issue if the lid is reopened too quickly
> >> > (the
> >> > laptop doesn't have the time to go to sleep).
> >> >
> >> > I am left with the impression that this is a software issue (debian did
> >> > not
> >> > do that and I had it just before installing Ubuntu, but debian could not
> >> > suspend) that leaves the video card state broken. I tried following
> >> > instruction on to force pipe a quirck
> >> > (https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen#Problem: Lockup
> >> > When
> >> > Closing Lid with Intel Graphics) because I have an intel graphics card,
> >> > but
> >> > xorg tells me this option is not used (WW in xorg.conf). I attached the
> >> > output to a few files or command outputs:
> >> > lspci -vvnn | grep "VGA Compat":
> >> > 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
> >> > Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA
> >> > controller])
> >> > ** * * *Subsystem: IBM Device [1014:0557]
> >> > ** * * *Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> >> > ParErr-
> >> > Stepping- SERR- FastB2B- DisINTx-
> >> > ** * * *Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> >> > <TAbort- <MAbort- >SERR- <PERR- INTx+
> >> > ** * * *Latency: 0
> >> > ** * * *Interrupt: pin A routed to IRQ 11
> >> > ** * * *Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
> >> > ** * * *Region 1: Memory at d0000000 (32-bit, non-prefetchable)
> >> > [size=512K]
> >> > ** * * *Region 2: I/O ports at 1800 [size=8]
> >> > ** * * *Expansion ROM at <unassigned> [disabled]
> >> > ** * * *Capabilities: [d0] Power Management version 1
> >> > ** * * * * * * *Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA
> >> > PME(D0-,D1-,D2-,D3hot-,D3cold-)
> >> > ** * * * * * * *Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> >> > ** * * *Kernel driver in use: i915
> >> > ** * * *Kernel modules: i915
> >> > /var/log/Xorg.0.log.old
> >> > http://pastebin.com/55uX0D1r
> >> > Notable errors:
> >> > [ * *24.110] (EE) VESA: Kernel modesetting driver in use, refusing to
> >> > load
> >> > [ * *24.110] (WW) Falling back to old probe method for vesa
> >> > and a few hundreds of:
> >> > [ * *24.456] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> >> >
> >> > intel_reg_dumper (good and bad state)
> >> > attached, and here is the diff:
> >> > 110c110
> >> > < * * * * * * VGACNTRL: 0x22040000 (enabled)
> >> > ---
> >> >> * * * * * * VGACNTRL: 0x80000000 (disabled)
> >> > It might be worth noting that whenever I close the lid and reopen it (or
> >> > just press the lid button), the screen comes visible for a fraction of
> >> > second, but long enough for me to see that whatever needs to be shown
> >> > gets
> >> > updated (If I kill my gnome session through ssh, I can see gdm logging
> >> > in
> >> > that fraction of seconds). Also, it's not just an issue with the
> >> > backlight
> >> > as it does come back on on lid open, and stays on.
> >> > Someone on #ubuntu (Freenode) suggested it might have to do with ACPI. I
> >> > tried moving /etc/acpi/lid.sh to /etc/acpi/lid.sh.bak, but it didn't
> >> > seem to
> >> > make a diffrence. I don't know enough about ACPI to rule it out though.
> >> > Thanks in advance,
> >> > --
> >> > Nicolas Calderon
> >> >
> >> >
> >> >
> >> > --
> >> > ubuntu-users mailing list
> >> > ubuntu-users@lists.ubuntu.com
> >> > Modify settings or unsubscribe at:
> >> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> >> >
> >> >
> >>
> >> --
> >> ubuntu-users mailing list
> >> ubuntu-users@lists.ubuntu.com
> >> Modify settings or unsubscribe at:
> >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> >
> >
>
> --
> ubuntu-users mailing list
> ubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

With the option "Blank screen" for the "When laptop lid is closed"
setting in "Power Management Preferences": I close the lid, I reopen
it, the screen stays blank, and the only way I can get it to work
again is by restarting the laptop.

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 01-18-2011, 06:38 AM
Colin Law
 
Default Screen blanks on lid close, never comes back

On 18 January 2011 03:02, Nicolas Calderon
<nicolas.calderon.asselin@gmail.com> wrote:
> ...
> With the option "Blank screen" for the "When laptop lid is closed"
> setting in "Power Management Preferences": I close the lid, I reopen
> it, the screen stays blank, and the only way I can get it to work
> again is by restarting the laptop.
>

If you select Put display to sleep when inactive, in Power Management
does it blank and recover ok then?

Colin

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 01-18-2011, 05:28 PM
Nicolas Calderon
 
Default Screen blanks on lid close, never comes back

On Tue, Jan 18, 2011 at 2:38 AM, Colin Law <clanlaw@googlemail.com> wrote:
> On 18 January 2011 03:02, Nicolas Calderon
> <nicolas.calderon.asselin@gmail.com> wrote:
>> ...
>> With the option "Blank screen" for the "When laptop lid is closed"
>> setting in "Power Management Preferences": I close the lid, I reopen
>> it, the screen stays blank, and the only way I can get it to work
>> again is by restarting the laptop.
>>
>
> If you select Put display to sleep when inactive, in Power Management
> does it blank and recover ok then?
>
> Colin
>
> --
> ubuntu-users mailing list
> ubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>

Yes, Put display to sleep when inactive does blank and recover the
screen correctly.

As a side note, I noticed in the battery power menu that there was a
Do Nothing option on When laptop lid is closed. It did not do nothing,
and caused the same issue I observed as Blank screen on AC (the
problem I described before).

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 01-18-2011, 07:39 PM
Colin Law
 
Default Screen blanks on lid close, never comes back

On 18 January 2011 18:28, Nicolas Calderon
<nicolas.calderon.asselin@gmail.com> wrote:
> On Tue, Jan 18, 2011 at 2:38 AM, Colin Law <clanlaw@googlemail.com> wrote:
>> On 18 January 2011 03:02, Nicolas Calderon
>> <nicolas.calderon.asselin@gmail.com> wrote:
>>> ...
>>> With the option "Blank screen" for the "When laptop lid is closed"
>>> setting in "Power Management Preferences": I close the lid, I reopen
>>> it, the screen stays blank, and the only way I can get it to work
>>> again is by restarting the laptop.
>>>
>>
>> If you select Put display to sleep when inactive, in Power Management
>> does it blank and recover ok then?
>>
>> Colin
>>
>> --
>> ubuntu-users mailing list
>> ubuntu-users@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>>
>
> Yes, Put display to sleep when inactive does blank and recover the
> screen correctly.
>
> As a side note, I noticed in the battery power menu that there was a
> Do Nothing option on When laptop lid is closed. It did not do nothing,
> and caused the same issue I observed as Blank screen on AC (the
> problem I described before).

Have you had a look in the logs to see if anything is there (System >
Administration > Log File Viewer)

Do you get a terminal window if you enter Ctrl Alt F1 (Ctrl Alt F7
should take you back). If you do then at least you can login and
restart with
sudo shutdown -h now

Has anyone else any ideas? Otherwise I think you may have to submit a bug.

Colin

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 01-18-2011, 08:38 PM
Nicolas Calderon
 
Default Screen blanks on lid close, never comes back

On Tue, Jan 18, 2011 at 3:39 PM, Colin Law <clanlaw@googlemail.com> wrote:
> On 18 January 2011 18:28, Nicolas Calderon
> <nicolas.calderon.asselin@gmail.com> wrote:
>> On Tue, Jan 18, 2011 at 2:38 AM, Colin Law <clanlaw@googlemail.com> wrote:
>>> On 18 January 2011 03:02, Nicolas Calderon
>>> <nicolas.calderon.asselin@gmail.com> wrote:
>>>> ...
>>>> With the option "Blank screen" for the "When laptop lid is closed"
>>>> setting in "Power Management Preferences": I close the lid, I reopen
>>>> it, the screen stays blank, and the only way I can get it to work
>>>> again is by restarting the laptop.
>>>>
>>>
>>> If you select Put display to sleep when inactive, in Power Management
>>> does it blank and recover ok then?
>>>
>>> Colin
>>>
>>> --
>>> ubuntu-users mailing list
>>> ubuntu-users@lists.ubuntu.com
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>>>
>>
>> Yes, Put display to sleep when inactive does blank and recover the
>> screen correctly.
>>
>> As a side note, I noticed in the battery power menu that there was a
>> Do Nothing option on When laptop lid is closed. It did not do nothing,
>> and caused the same issue I observed as Blank screen on AC (the
>> problem I described before).
>
> Have you had a look in the logs to see if anything is there (System >
> Administration > Log File Viewer)
>
> Do you get a terminal window if you enter Ctrl Alt F1 *(Ctrl Alt F7
> should take you back). *If you do then at least you can login and
> restart with
> sudo shutdown -h now
>
> Has anyone else any ideas? * Otherwise I think you may have to submit a bug.
>
> Colin
>
> --
> ubuntu-users mailing list
> ubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>

I will look at those logs when I get home. I did look at some logs
though. My Xorg log was posted in my orignial message.

Switching to a tty ( Ctrl Alt F1) does not fix the issue. Sysreq
(alt-sysreq-k) either. If I want to restart softly, I just ssh and
sudo shutdown -r now.

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 01-18-2011, 09:24 PM
Colin Law
 
Default Screen blanks on lid close, never comes back

On 18 January 2011 21:38, Nicolas Calderon
<nicolas.calderon.asselin@gmail.com> wrote:
> [...]
> I will look at those logs when I get home. I did look at some logs
> though. My Xorg log was posted in my orignial message.

Sorry, I missed that. Do any of these look like they might apply?

https://launchpad.net/+search?field.text=%28EE%29+FBDEV%280%29%3A+FBIOPU TCMAP%3A+Invalid+argument+intel&field.actions.sear ch=Search

Colin

>
> Switching to a tty ( Ctrl Alt F1) does not fix the issue. Sysreq
> (alt-sysreq-k) either. If I want to restart softly, I just ssh and
> sudo shutdown -r now.
>

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 

Thread Tools




All times are GMT. The time now is 10:36 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org