Michel Thanks a lot for answering.
On Sun, May 28, 2006 at 02:12:06PM +0200, Michel Dänzer wrote: > On Sat, 2006-05-27 at 01:38 +0200, Wolfgang Pfeiffer wrote: > > > > On an updated unstable Debian, PB5,8, X only starts now with > > Load "dri" > > disabled in xorg.conf. What's the Debian package that is responsible > > for the broken (?) dri driver: libgl1-mesa-dri? I've Version 6.4.1-0.4 > > installed. > > libgl1-mesa-dri is only involved when you run an OpenGL app. The culprit > here is most likely xserver-xorg-video-ati, Oh, I already filed a bug report some hours ago against libgl1-mesa-dri : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369167 > but it's a known problem anyway. It should work with radeon DRM 1.23 > or newer. I'm not sure what you mean by DRM 1.23: But a just a few days old relatively fresh git kernel here says this in kern.log (when rebooting after the mentioned crash probably --> the wrong 'Jan 1' date): Jan 1 01:00:53 debby1-6 kernel: Inspecting /boot/System.map-2.6.17-rc3-gf358166a-dirty Jan 1 01:00:53 debby1-6 kernel: Loaded 19106 symbols from /boot/System.map-2.6.17-rc3-gf358166a-dirty. [ ... ] Jan 1 01:12:08 debby1-6 kernel: [ 715.607451] [drm] Initialized drm 1.0.1 20051102 Jan 1 01:12:08 debby1-6 kernel: [ 715.640230] [drm] Initialized radeon 1.24.0 20060225 on minor 0 Does the above mean that this kernel still has drm 1.0.1 ? Or is it old xorg stuff that is being loaded at the time of the kern.log above? $ zgrep DRM /proc/config.gz CONFIG_DRM=m # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set CONFIG_DRM_RADEON=m # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_DRM_SAVAGE is not set So I'm not even sure what was going on when the system crashed: Were the kernel DRM modules from above loaded, or some DRM from xorg? Actually I'd bet now they were part of an xorg package ... :) Because the sources for the running kernel, in drivers/char/drm/radeon_drv.h, say * 1.24- Add general-purpose packet for manipulating scratch registers (r300) But I can only guess ... :) > The only way to > 'fix' it will be to disable the DRI with an older DRM anyway, so this is > basically a case of 'don't do that' for now. > > > > If I don't disable dri on that machine it can damage the system: > > After one crash that happened an hour ago when I tried to start KDM, > > time on reboot was reset to something like Jan 1, 2004, IIRC. > > I think you mean 1904. Yes and No :) No: I really thought I saw some date of 2004 when rebooting. I was wondering about that as I was used to see something like 1904 in situations like that. Yes: After having a look to my log files I'm not sure of that anymore, as one kdm.log clearly has one line with that: (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 1 01:12:07 1904 Thanks in anticipation Wolfgang -- Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/ http://profiles.yahoo.com/wolfgangpfeiffer Key ID: E3037113 http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
