Re: cannot logoff/shutdown properly

2007-08-25 Thread Florian Kulzer
On Fri, Aug 24, 2007 at 21:05:27 -0400, Manu Hack wrote:
 On 8/24/07, Florian Kulzer wrote:
  On Fri, Aug 24, 2007 at 10:46:13 -0400, Manu Hack wrote:
   On 8/24/07, Florian Kulzer wrote:
On Thu, Aug 23, 2007 at 22:38:27 -0400, Manu Hack wrote:
 On 8/23/07, Florian Kulzer wrote:
  On Wed, Aug 22, 2007 at 01:25:47 -0400, Manu Hack wrote:
   On 8/21/07, Florian Kulzer wrote:
On Tue, Aug 21, 2007 at 12:29:53 -0400, Manu Hack wrote:
 I finally have the chance to look at /var/log/Xorg.0.log in 
 recovery
 mode but it didn't have anything with (EE) or (WW).

 And in recovery mode, I can shutdown properly with shutdown 
 -h now.

[...]

This still looks like a crash of the graphics driver during mode
switching to me. (Did you also try this with the vesa driver?) If you
are at the graphical login screen, can you switch to a terminal with
CTRL + ALT + F1 (or F2, ..., F6)?
  
   I tried vesa, but the screen is not very stable and I can logoff once
   and then when I login again, I couldn't log off like I was using i810.
 
  I would still like to know whether your system hangs if you try to
  switch to a terminal without shutting down gdm.
 
 If I have a graphical login prompt and press CTRL + ALT + Back I can
 go to a text mode login prompt but immediately I will go back to the
 graphical login prompt.

I think that is the default behavior of gdm: It respawns X if X is
killed suddenly. So maybe this is not related to the graphics driver
after all. If you cannot find any further clues in

/var/log/syslog
/var/log/Xorg.0.log
~/.xsession-errors

(after a crash and a reboot into single-user mode) then I don't know
where to look next. If you have another computer on the same LAN then it
might be worthwhile to try if you can still log in remotely with ssh
after the problematic system freezes.

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-25 Thread s. keeling
Manu Hack [EMAIL PROTECTED]:
  On 8/24/07, Florian Kulzer [EMAIL PROTECTED] wrote:
 
  I would still like to know whether your system hangs if you try to
  switch to a terminal without shutting down gdm.
 
  If I have a graphical login prompt and press CTRL + ALT + Back I can
  go to a text mode login prompt but immediately I will go back to the

Use CTRL-ALT-F1 (or -F2, -F3, ...) to get to the console.  From there,
ALT-F7 goes back to X, which will still be running.


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)http://blinkynet.net/comp/uip5.html  Linux Counter #80292
- -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-24 Thread Andrei Popescu
Manu Hack [EMAIL PROTECTED] wrote:

  I think the next thing to try is if X blocks the shutdown or if
  something else in runlevel 2 is responsible. Shut down X and/or
  stop the graphical login manager with
 
  invoke-rc.d gdm stop
 
 Maybe a more detailed way to do so is helpful to me for if I run the
 above command the screen goes black and I lose control of everything.

If you don't get a login prompt then press Alt-F1 (or F2 - F6). Login
as root and run 'shutdown'.

HTH,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: PGP signature


Re: cannot logoff/shutdown properly

2007-08-24 Thread Giorgos Pallas
And my 2 (problem) cents here... I have debian lenny on my laptop with
KDE and since I installed it, there were two problems: It could not log
off everytime (right click and log-out sometimes was ignored, even if I
did it a hundred times), and second, acpi could not switch the laptop
off: the last messages on the screen were (something like):
unmounting local filesystems
shutdown
acpi power off called

and there it stayed. So, the first problem has not reappeared during the
last two months (a upgrade resolved it probably), as for the second, I
discovered that unloading the sound (??) modules before shutdown, lets
the laptop switch off...

modprobe -r snd-hda-intel
modprobe -r snd-hda-codec

Anyway...

G.


Andrei Popescu wrote:
 Manu Hack [EMAIL PROTECTED] wrote:

   
 I think the next thing to try is if X blocks the shutdown or if
 something else in runlevel 2 is responsible. Shut down X and/or
 stop the graphical login manager with

 invoke-rc.d gdm stop
   
 Maybe a more detailed way to do so is helpful to me for if I run the
 above command the screen goes black and I lose control of everything.
 

 If you don't get a login prompt then press Alt-F1 (or F2 - F6). Login
 as root and run 'shutdown'.

 HTH,
 Andrei
   


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-24 Thread Florian Kulzer
On Thu, Aug 23, 2007 at 22:38:27 -0400, Manu Hack wrote:
 On 8/23/07, Florian Kulzer wrote:
  On Wed, Aug 22, 2007 at 01:25:47 -0400, Manu Hack wrote:
   On 8/21/07, Florian Kulzer wrote:
On Tue, Aug 21, 2007 at 12:29:53 -0400, Manu Hack wrote:
 I finally have the chance to look at /var/log/Xorg.0.log in recovery
 mode but it didn't have anything with (EE) or (WW).

 And in recovery mode, I can shutdown properly with shutdown -h now.
   
That suggests to me that the shutdown problem might be related to the
video driver that you use for Xorg.
   
 Any more suggestion?
   
Did you try the vesa driver already? (as I suggested earlier)
  
   Yes, it turns out that similar problem is still there.
  
Which video card do you have and which driver do you normally use?
  
   I have been using i810 for a while and before it had no problem until
   an update months ago.
 
  Which Intel card is it? How is the driver configured? Are there any
  warnings or errors in xorg's log? Run the following commands and post
  the output:
 
  lspci | egrep -i 'vga|graphic|display|video'
 
 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated 
 Graphics Device (rev 02)
 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics 
 Device (rev 02)

I have the exact same hardware on my laptop and I don't have any
problems with shutting down or restarting X.

  awk '/Section (Device|Monitor)/,/EndSection/' /etc/X11/xorg.conf
 
 Section Device
 Identifier  Intel Corporation 82852/855GM Integrated
 Graphics Device
 Driver  i810
 BusID   PCI:0:2:0

I use intel instead of i810. This should not matter if you have the
newest version of the driver since the i810 is only a legacy symlink
nowadays which points to the intel module. What is your output for:

dpkg -l xserver-xorg-video-{intel,i810} | awk '/^[^D|+]/{print $1,$2,$3}'

 EndSection
 Section Monitor
 Identifier  Generic Monitor
 Option  DPMS
 EndSection
 
 
  egrep '^\((EE|WW)\)' /var/log/Xorg.0.log

[ snip: harmless fontpath noise ]

 (EE) intel(0): detecting sil164
 (EE) intel(0): Unable to read from DVOI2C_E Slave 112.
 (WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages failed

I see the same currently; this seems to be a regression of the new
driver for older cards. I have not found a way to fix this yet. The only
effect of this seems to be that X takes two tries to start up and then
works normally.

 (WW) AIGLX: 3D driver claims to not support visual 0x23

[ snip: similar warnings, counting up to 0x32 ] 

I see the same.

  X -version
 X Window System Version 1.3.0
 Release Date: 19 April 2007
 X Protocol Version 11, Revision 0, Release 1.3
 Build Operating System: Linux Debian (xorg-server 2:1.3.0.0.dfsg-12)
 Current Operating System: Linux debian 2.6.21-2-686 #1 SMP Wed Jul 11
 03:53:02 UTC 2007 i686
 Build Date: 09 August 2007
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
 Module Loader present

I run the same version.

Also, are there any interesting entries in /var/log/syslog around the
time of the crashes/freezes?
   I don't think so.
 
  I think the next thing to try is if X blocks the shutdown or if
  something else in runlevel 2 is responsible. Shut down X and/or stop the
  graphical login manager with
 
  invoke-rc.d gdm stop
 
 Maybe a more detailed way to do so is helpful to me for if I run the
 above command the screen goes black and I lose control of everything.

This still looks like a crash of the graphics driver during mode
switching to me. (Did you also try this with the vesa driver?) If you
are at the graphical login screen, can you switch to a terminal with
CTRL + ALT + F1 (or F2, ..., F6)?

Unless you can find a related message in either the syslog or the xorg
log I don't know how to track this down. The only other thing I can
think of right now is having a look at your loaded modules; what is
your output for

lsmod | egrep 'i(810|830|915)|drm|agp|i2c'

?

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-24 Thread Manu Hack
On 8/24/07, Florian Kulzer [EMAIL PROTECTED] wrote:
 On Thu, Aug 23, 2007 at 22:38:27 -0400, Manu Hack wrote:
  On 8/23/07, Florian Kulzer wrote:
   On Wed, Aug 22, 2007 at 01:25:47 -0400, Manu Hack wrote:
On 8/21/07, Florian Kulzer wrote:
 On Tue, Aug 21, 2007 at 12:29:53 -0400, Manu Hack wrote:
  I finally have the chance to look at /var/log/Xorg.0.log in recovery
  mode but it didn't have anything with (EE) or (WW).
 
  And in recovery mode, I can shutdown properly with shutdown -h now.

 That suggests to me that the shutdown problem might be related to the
 video driver that you use for Xorg.

  Any more suggestion?

 Did you try the vesa driver already? (as I suggested earlier)
   
Yes, it turns out that similar problem is still there.
   
 Which video card do you have and which driver do you normally use?
   
I have been using i810 for a while and before it had no problem until
an update months ago.
  
   Which Intel card is it? How is the driver configured? Are there any
   warnings or errors in xorg's log? Run the following commands and post
   the output:
  
   lspci | egrep -i 'vga|graphic|display|video'
 
  00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated 
  Graphics Device (rev 02)
  00:02.1 Display controller: Intel Corporation 82852/855GM Integrated 
  Graphics Device (rev 02)

 I have the exact same hardware on my laptop and I don't have any
 problems with shutting down or restarting X.

   awk '/Section (Device|Monitor)/,/EndSection/' /etc/X11/xorg.conf
 
  Section Device
  Identifier  Intel Corporation 82852/855GM Integrated
  Graphics Device
  Driver  i810
  BusID   PCI:0:2:0

 I use intel instead of i810. This should not matter if you have the
 newest version of the driver since the i810 is only a legacy symlink
 nowadays which points to the intel module. What is your output for:

 dpkg -l xserver-xorg-video-{intel,i810} | awk '/^[^D|+]/{print $1,$2,$3}'

ii xserver-xorg-video-i810 2:2.1.0-2
ii xserver-xorg-video-intel 2:2.1.0-2



 Also, are there any interesting entries in /var/log/syslog around the
 time of the crashes/freezes?
I don't think so.
  
   I think the next thing to try is if X blocks the shutdown or if
   something else in runlevel 2 is responsible. Shut down X and/or stop the
   graphical login manager with
  
   invoke-rc.d gdm stop
 
  Maybe a more detailed way to do so is helpful to me for if I run the
  above command the screen goes black and I lose control of everything.

 This still looks like a crash of the graphics driver during mode
 switching to me. (Did you also try this with the vesa driver?) If you
 are at the graphical login screen, can you switch to a terminal with
 CTRL + ALT + F1 (or F2, ..., F6)?


I tried vesa, but the screen is not very stable and I can logoff once
and then when I login again, I couldn't log off like I was using i810.


 Unless you can find a related message in either the syslog or the xorg
 log I don't know how to track this down. The only other thing I can
 think of right now is having a look at your loaded modules; what is
 your output for

 lsmod | egrep 'i(810|830|915)|drm|agp|i2c'

 ?
i915   21280  3
drm73908  4 i915
intel_agp  23004  1
agpgart32168  3 drm,intel_agp

Manu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-24 Thread Florian Kulzer
On Fri, Aug 24, 2007 at 10:46:13 -0400, Manu Hack wrote:
 On 8/24/07, Florian Kulzer wrote:
  On Thu, Aug 23, 2007 at 22:38:27 -0400, Manu Hack wrote:
   On 8/23/07, Florian Kulzer wrote:
On Wed, Aug 22, 2007 at 01:25:47 -0400, Manu Hack wrote:
 On 8/21/07, Florian Kulzer wrote:
  On Tue, Aug 21, 2007 at 12:29:53 -0400, Manu Hack wrote:
   I finally have the chance to look at /var/log/Xorg.0.log in 
   recovery
   mode but it didn't have anything with (EE) or (WW).
  
   And in recovery mode, I can shutdown properly with shutdown -h 
   now.
 
  That suggests to me that the shutdown problem might be related to 
  the
  video driver that you use for Xorg.

[...]

lspci | egrep -i 'vga|graphic|display|video'
  
   00:02.0 VGA compatible controller: Intel Corporation 82852/855GM 
   Integrated Graphics Device (rev 02)
   00:02.1 Display controller: Intel Corporation 82852/855GM Integrated 
   Graphics Device (rev 02)
 
  I have the exact same hardware on my laptop and I don't have any
  problems with shutting down or restarting X.
 
awk '/Section (Device|Monitor)/,/EndSection/' /etc/X11/xorg.conf
  
   Section Device
   Identifier  Intel Corporation 82852/855GM Integrated
   Graphics Device
   Driver  i810
   BusID   PCI:0:2:0
 
  I use intel instead of i810. This should not matter if you have the
  newest version of the driver since the i810 is only a legacy symlink
  nowadays which points to the intel module. What is your output for:
 
  dpkg -l xserver-xorg-video-{intel,i810} | awk '/^[^D|+]/{print $1,$2,$3}'
 
 ii xserver-xorg-video-i810 2:2.1.0-2
 ii xserver-xorg-video-intel 2:2.1.0-2

I have slightly newer versions right now since I track Sid, but I don't
recall any problems in the recent past.

  Also, are there any interesting entries in /var/log/syslog around 
  the
  time of the crashes/freezes?
 I don't think so.
   
I think the next thing to try is if X blocks the shutdown or if
something else in runlevel 2 is responsible. Shut down X and/or stop the
graphical login manager with
   
invoke-rc.d gdm stop
  
   Maybe a more detailed way to do so is helpful to me for if I run the
   above command the screen goes black and I lose control of everything.
 
  This still looks like a crash of the graphics driver during mode
  switching to me. (Did you also try this with the vesa driver?) If you
  are at the graphical login screen, can you switch to a terminal with
  CTRL + ALT + F1 (or F2, ..., F6)?
 
 I tried vesa, but the screen is not very stable and I can logoff once
 and then when I login again, I couldn't log off like I was using i810.

I would still like to know whether your system hangs if you try to
switch to a terminal without shutting down gdm.

  Unless you can find a related message in either the syslog or the xorg
  log I don't know how to track this down. The only other thing I can
  think of right now is having a look at your loaded modules; what is
  your output for
 
  lsmod | egrep 'i(810|830|915)|drm|agp|i2c'
 
 i915   21280  3
 drm73908  4 i915
 intel_agp  23004  1
 agpgart32168  3 drm,intel_agp

That looks OK to me. (I have compiled drm, intel_agp and agpgart into my
kernel, but that should not make a difference.) You do not seem to have
any i2c-related modules loaded. I am not sure if this is relevant, but
you do have these somewhat ominous DVOI2C errors in your xorg log. Does
your system have an SMBus? Post the output of 

lspci | egrep -i 'i2c|smb'

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-24 Thread Manu Hack
On 8/24/07, Florian Kulzer [EMAIL PROTECTED] wrote:
 On Fri, Aug 24, 2007 at 10:46:13 -0400, Manu Hack wrote:
  On 8/24/07, Florian Kulzer wrote:
   On Thu, Aug 23, 2007 at 22:38:27 -0400, Manu Hack wrote:
On 8/23/07, Florian Kulzer wrote:
 On Wed, Aug 22, 2007 at 01:25:47 -0400, Manu Hack wrote:
  On 8/21/07, Florian Kulzer wrote:
   On Tue, Aug 21, 2007 at 12:29:53 -0400, Manu Hack wrote:
I finally have the chance to look at /var/log/Xorg.0.log in 
recovery
mode but it didn't have anything with (EE) or (WW).
   
And in recovery mode, I can shutdown properly with shutdown -h 
now.
  
   That suggests to me that the shutdown problem might be related to 
   the
   video driver that you use for Xorg.

 [...]

 lspci | egrep -i 'vga|graphic|display|video'
   
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM 
Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated 
Graphics Device (rev 02)
  
   I have the exact same hardware on my laptop and I don't have any
   problems with shutting down or restarting X.
  
 awk '/Section (Device|Monitor)/,/EndSection/' /etc/X11/xorg.conf
   
Section Device
Identifier  Intel Corporation 82852/855GM Integrated
Graphics Device
Driver  i810
BusID   PCI:0:2:0
  
   I use intel instead of i810. This should not matter if you have the
   newest version of the driver since the i810 is only a legacy symlink
   nowadays which points to the intel module. What is your output for:
  
   dpkg -l xserver-xorg-video-{intel,i810} | awk '/^[^D|+]/{print $1,$2,$3}'
 
  ii xserver-xorg-video-i810 2:2.1.0-2
  ii xserver-xorg-video-intel 2:2.1.0-2

I'm hoping in the next update I won't have the same problem. :)


 I have slightly newer versions right now since I track Sid, but I don't
 recall any problems in the recent past.

   Also, are there any interesting entries in /var/log/syslog around 
   the
   time of the crashes/freezes?
  I don't think so.

 I think the next thing to try is if X blocks the shutdown or if
 something else in runlevel 2 is responsible. Shut down X and/or stop 
 the
 graphical login manager with

 invoke-rc.d gdm stop
   
Maybe a more detailed way to do so is helpful to me for if I run the
above command the screen goes black and I lose control of everything.
  
   This still looks like a crash of the graphics driver during mode
   switching to me. (Did you also try this with the vesa driver?) If you
   are at the graphical login screen, can you switch to a terminal with
   CTRL + ALT + F1 (or F2, ..., F6)?
 
  I tried vesa, but the screen is not very stable and I can logoff once
  and then when I login again, I couldn't log off like I was using i810.

 I would still like to know whether your system hangs if you try to
 switch to a terminal without shutting down gdm.

If I have a graphical login prompt and press CTRL + ALT + Back I can
go to a text mode login prompt but immediately I will go back to the
graphical login prompt.

   Unless you can find a related message in either the syslog or the xorg
   log I don't know how to track this down. The only other thing I can
   think of right now is having a look at your loaded modules; what is
   your output for
  
   lsmod | egrep 'i(810|830|915)|drm|agp|i2c'
  
  i915   21280  3
  drm73908  4 i915
  intel_agp  23004  1
  agpgart32168  3 drm,intel_agp

 That looks OK to me. (I have compiled drm, intel_agp and agpgart into my
 kernel, but that should not make a difference.) You do not seem to have
 any i2c-related modules loaded. I am not sure if this is relevant, but
 you do have these somewhat ominous DVOI2C errors in your xorg log. Does
 your system have an SMBus? Post the output of

 lspci | egrep -i 'i2c|smb'

No output for this one.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-23 Thread Florian Kulzer
On Wed, Aug 22, 2007 at 01:25:47 -0400, Manu Hack wrote:
 On 8/21/07, Florian Kulzer wrote:
  On Tue, Aug 21, 2007 at 12:29:53 -0400, Manu Hack wrote:
   I finally have the chance to look at /var/log/Xorg.0.log in recovery
   mode but it didn't have anything with (EE) or (WW).
  
   And in recovery mode, I can shutdown properly with shutdown -h now.
 
  That suggests to me that the shutdown problem might be related to the
  video driver that you use for Xorg.
 
   Any more suggestion?
 
  Did you try the vesa driver already? (as I suggested earlier)
 
 Yes, it turns out that similar problem is still there.
 
 
  Which video card do you have and which driver do you normally use?
 
 
 I have been using i810 for a while and before it had no problem until
 an update months ago.

Which Intel card is it? How is the driver configured? Are there any
warnings or errors in xorg's log? Run the following commands and post
the output:

lspci | egrep -i 'vga|graphic|display|video'

awk '/Section (Device|Monitor)/,/EndSection/' /etc/X11/xorg.conf

egrep '^\((EE|WW)\)' /var/log/Xorg.0.log

X -version

  Also, are there any interesting entries in /var/log/syslog around the
  time of the crashes/freezes?
 I don't think so.

I think the next thing to try is if X blocks the shutdown or if
something else in runlevel 2 is responsible. Shut down X and/or stop the
graphical login manager with

invoke-rc.d gdm stop

and check if you can shut down the system then. (Replace gdm with
kdm or xdm if necessary.)

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-23 Thread Manu Hack
On 8/23/07, Florian Kulzer [EMAIL PROTECTED] wrote:
 On Wed, Aug 22, 2007 at 01:25:47 -0400, Manu Hack wrote:
  On 8/21/07, Florian Kulzer wrote:
   On Tue, Aug 21, 2007 at 12:29:53 -0400, Manu Hack wrote:
I finally have the chance to look at /var/log/Xorg.0.log in recovery
mode but it didn't have anything with (EE) or (WW).
   
And in recovery mode, I can shutdown properly with shutdown -h now.
  
   That suggests to me that the shutdown problem might be related to the
   video driver that you use for Xorg.
  
Any more suggestion?
  
   Did you try the vesa driver already? (as I suggested earlier)
 
  Yes, it turns out that similar problem is still there.
 
  
   Which video card do you have and which driver do you normally use?
  
 
  I have been using i810 for a while and before it had no problem until
  an update months ago.

 Which Intel card is it? How is the driver configured? Are there any
 warnings or errors in xorg's log? Run the following commands and post
 the output:

 lspci | egrep -i 'vga|graphic|display|video'

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM
Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated
Graphics Device (rev 02)


 awk '/Section (Device|Monitor)/,/EndSection/' /etc/X11/xorg.conf

Section Device
Identifier  Intel Corporation 82852/855GM Integrated
Graphics Device
Driver  i810
BusID   PCI:0:2:0
EndSection
Section Monitor
Identifier  Generic Monitor
Option  DPMS
EndSection


 egrep '^\((EE|WW)\)' /var/log/Xorg.0.log

(WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist.
(WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
(WW) The directory /usr/X11R6/lib/X11/fonts/cyrillic does not exist.
(WW) The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist.
(WW) The directory /usr/X11R6/lib/X11/fonts/75dpi/ does not exist.
(WW) The directory /usr/X11R6/lib/X11/fonts/Type1 does not exist.
(WW) The directory /usr/X11R6/lib/X11/fonts/100dpi does not exist.
(WW) The directory /usr/X11R6/lib/X11/fonts/75dpi does not exist.
(WW) Including the default font path
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType.
(EE) intel(0): detecting sil164
(EE) intel(0): Unable to read from DVOI2C_E Slave 112.
(WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages failed
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32


 X -version
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Debian (xorg-server 2:1.3.0.0.dfsg-12)
Current Operating System: Linux debian 2.6.21-2-686 #1 SMP Wed Jul 11
03:53:02 UTC 2007 i686
Build Date: 09 August 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present



   Also, are there any interesting entries in /var/log/syslog around the
   time of the crashes/freezes?
  I don't think so.

 I think the next thing to try is if X blocks the shutdown or if
 something else in runlevel 2 is responsible. Shut down X and/or stop the
 graphical login manager with

 invoke-rc.d gdm stop

Maybe a more detailed way to do so is helpful to me for if I run the
above command the screen goes black and I lose control of everything.

Thanks a lot!!
\
Manu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-21 Thread Manu Hack
I finally have the chance to look at /var/log/Xorg.0.log in recovery
mode but it didn't have anything with (EE) or (WW).

And in recovery mode, I can shutdown properly with shutdown -h now.
Any more suggestion?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-21 Thread Florian Kulzer
[ You should leave some context in your messages, especially if you are
  reviving a thread which has been inactive for almost a month;
  otherwise people might mistake you for one of those special posters
  from debianhelp.org... ]

On Tue, Aug 21, 2007 at 12:29:53 -0400, Manu Hack wrote:
 I finally have the chance to look at /var/log/Xorg.0.log in recovery
 mode but it didn't have anything with (EE) or (WW).
 
 And in recovery mode, I can shutdown properly with shutdown -h now.

That suggests to me that the shutdown problem might be related to the
video driver that you use for Xorg.

 Any more suggestion?

Did you try the vesa driver already? (as I suggested earlier)

Which video card do you have and which driver do you normally use?

Also, are there any interesting entries in /var/log/syslog around the
time of the crashes/freezes?

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-08-21 Thread Manu Hack
On 8/21/07, Florian Kulzer [EMAIL PROTECTED] wrote:
 [ You should leave some context in your messages, especially if you are
   reviving a thread which has been inactive for almost a month;
   otherwise people might mistake you for one of those special posters
   from debianhelp.org... ]

will remember to do that next time!

 On Tue, Aug 21, 2007 at 12:29:53 -0400, Manu Hack wrote:
  I finally have the chance to look at /var/log/Xorg.0.log in recovery
  mode but it didn't have anything with (EE) or (WW).
 
  And in recovery mode, I can shutdown properly with shutdown -h now.

 That suggests to me that the shutdown problem might be related to the
 video driver that you use for Xorg.

  Any more suggestion?

 Did you try the vesa driver already? (as I suggested earlier)

Yes, it turns out that similar problem is still there.


 Which video card do you have and which driver do you normally use?


I have been using i810 for a while and before it had no problem until
an update months ago.

 Also, are there any interesting entries in /var/log/syslog around the
 time of the crashes/freezes?
I don't think so.

Manu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-07-27 Thread Jörg-Volker Peetz
From time to time I have a similar problem on a Compaq notebook with ATI
graphic card. In my case the display comes back after pushing the little
pin shortly which is pressed down by the lid when closing the notebook.
-- 
Regards,
Jörg-Volker.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cannot logoff/shutdown properly

2007-07-24 Thread Florian Kulzer
On Sun, Jul 22, 2007 at 09:46:04 -0400, Manu Hack wrote:
 Hi all,

 I'm running lenny.  recently after upgrade to 2.6.21, I found that I
 couldn't logoff/shutdown properly from KDE/GNOME/windowmaker.  By
 properly I mean whenever I choose logoff, usually KDM/GDM can take
 over and give me a login prompt but now it just goes blank and nothing
 can be done (including alt control back or F1) but pressing the power
 button to turn it off.

 What could go wrong?  Thank a lot.

 Let me know what further information you need to investigate the issue.

This could be a problem with the video driver which crashes the
computer. You could try to switch to the generic vesa driver.

You should also try to get a look at the Xorg log file after the crash.
The problem is that this file cleaned out when Xorg starts again, so you
have to keep Xorg from starting again when you switch the computer off
and on again after a crash. You could boot into single user mode, for
example. Then you can have a look at the end of the file

/var/log/Xorg.0.log

especially at lines that start with (EE) or (WW).

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]