Ben, Michel: Seems things are becoming a bit more clear now ... :)
On Sat, Jun 10, 2006 at 10:57:52AM +1000, Benjamin Herrenschmidt wrote: > On Thu, 2006-06-08 at 11:48 +0200, Michel Dänzer wrote: [ ... ] > > (II) RADEON(0): [dri] Found DRI library version 1.2.0 and kernel module > > version 1.25.0 > > > > Ben, any idea how this can result in the DRM using the old memory map, > > as seen above? Do you agree that the breakage might be related to this? > > I don't know about the breakage cause but yeah.. I would have expected > this to be the new memory map, maybe it's a bug with UseFBDev ? Yes. It looks like switching off 'UseFBDev' in xorg.conf helps getting DRI running: I restarted the system, restarted the xserver from the KDM login menu, a few times: No crashes so far with DRI being enabled: I only once got some strange distorted colored console screen just after the system was started to reboot: This lasted on for a few seconds, but shortly before the usual boot up console messages stopped, this 'distorted' screen normalised, and I got a console prompt. On X now: -------------------------- $ glxinfo | grep -i render *********************************WARN_ONCE********************************* File r300_state.c function r300Enable line 456 TODO - double side stencil ! *************************************************************************** No ctx->FragmentProgram._Current!! direct rendering: Yes OpenGL renderer string: Mesa DRI R300 20040924 AGP 4x TC --------------------------------- xorg.conf [ excerpts ] for the working DRI from above: ---------------------------- [ ... ] Section "Module" Load "bitmap" Load "dbe" Load "ddc" Load "dri" Load "extmod" Load "freetype" Load "glx" Load "int10" Load "record" Load "type1" Load "v4l" Load "vbe" Load "evdev" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "macintosh" Option "XkbLayout" "de" Option "XkbVariant" "nodeadkeys" Option "XkbOptions" "lv3:lwin_switch" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "false" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents" "true" Option "Device" "/dev/input/mice" Option "Protocol" "auto-dev" Option "LeftEdge" "0" Option "RightEdge" "850" Option "TopEdge" "0" Option "BottomEdge" "645" Option "MinSpeed" "0.4" Option "MaxSpeed" "1" Option "AccelFactor" "0.02" Option "FingerLow" "55" Option "FingerHigh" "60" Option "MaxTapMove" "20" Option "MaxTapTime" "100" Option "HorizScrollDelta" "0" Option "VertScrollDelta" "30" Option "SHMConfig" "on" EndSection Section "Device" Identifier "ATI Technologies, Inc. Radeon R250 Lf [FireGL 9000]" Driver "ati" BusID "PCI:0:16:0" # Option "UseFBDev" "true" Option "AGPSize" "16" Option "AGPMode" "4" Option "EnablePageFlip" Option "DRIReinit" "true" Option "BackingStore" "True" EndSection Section "Monitor" Identifier "Color LCD" # DisplaySize 323 216 DisplaySize 321 214 Option "DPMS" EndSection [ ... ] ------------------------------ $ apt-cache policy xserver-xorg-video-fbdev xserver-xorg-video-fbdev: Installed: 1:0.1.0.5-2 Candidate: 1:0.1.0.5-2 $ zgrep FB /proc/config.gz | grep -v ^# CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y CONFIG_FB_MACMODES=y CONFIG_FB_MODE_HELPERS=y CONFIG_FB_CONTROL=y CONFIG_FB_PLATINUM=y CONFIG_FB_VALKYRIE=y CONFIG_FB_RADEON=y CONFIG_FB_RADEON_I2C=y $ uname -a Linux debby1-6 2.6.17-rc3-gf358166a-dirty #1 Fri May 12 01:13:36 CEST 2006 ppc GNU/Linux So is it a buggy kernel and/or buggy xserver-xorg-video-fbdev? Again: Thanks to both of you for your time. Best Regards 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]