Re: cannot logoff/shutdown properly
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 |
Reply to: