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
> drm                    73908  4 i915
> intel_agp              23004  1
> agpgart                32168  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]

Reply via email to