Bug#397438: Panel stays blank in MergedFB mode
This is fixed for me in the latest unstable packages. Now if only I didn't have to patch my xserver with the workaround in comment #16 from here: https://bugs.freedesktop.org/show_bug.cgi?id=7770 Thanks, Bryan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#406373: xserver-xorg-video-ati: [ia64] No direct rendering w/ Radeon R300 [FireGL X1]
Alex Deucher wrote: On 1/11/07, Bryan Stillwell <[EMAIL PROTECTED]> wrote: However, when running in mergedfb mode, the right ~1/3rd of the second monitor doesn't work properly. The first monitor and the first ~2/3rds of the second monitor work great. Have you seen anything like that before, or should I file a separate bug on that? The best way I could describe it is garbage, but it seems like some of the graphics are trying to be displayed. How wide is your mergedfb desktop? There are some width and height limitations in the 3D engine. It is 3200x1200. I would say the 3D engine appears to have problems when X is between ~2667 and 3199. What are the limits? Are they in the card or in the driver? Thanks, Bryan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#406373: xserver-xorg-video-ati: [ia64] No direct rendering w/ Radeon R300 [FireGL X1]
Michel Dänzer wrote: This looks like https://bugs.freedesktop.org/show_bug.cgi?id=7770 . You're absolutely right. I tried the workaround (https://bugs.freedesktop.org/attachment.cgi?id=6560), and it works great for me! I'm getting about 3100FPS with glxgears! However, when running in mergedfb mode, the right ~1/3rd of the second monitor doesn't work properly. The first monitor and the first ~2/3rds of the second monitor work great. Have you seen anything like that before, or should I file a separate bug on that? The best way I could describe it is garbage, but it seems like some of the graphics are trying to be displayed. Thanks again for the help Michel! Bryan
Bug#406373: xserver-xorg-video-ati: [ia64] No direct rendering w/ Radeon R300 [FireGL X1]
Brice Goglin wrote: Bryan Stillwell wrote: (EE) AIGLX error: drmOpen failed (Operation not permitted) (EE) AIGLX: reverting to software rendering I am way less familiar with these problems. It looks like it opens /dev/dri/card0 earlier fine and then fails here. Could you send "ls -l /dev/dri/" to check the permissions ? Nothing obvious there: [EMAIL PROTECTED]:~$ ls -l /dev/dri/ total 0 crw-rw-rw- 1 root root 226, 0 2007-01-10 14:07 card0 I've attached the new Xorg.0.log file, lsmod output, and the information you requested. Thanks but most of them might be useless now that AGP works ;) Yeah, thanks for the help pointing out my oversight! :) Bryan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#406373: xserver-xorg-video-ati: [ia64] No direct rendering w/ Radeon R300 [FireGL X1]
Package: xserver-xorg-video-ati Version: 1:6.6.3-2 Severity: normal I'm attempting to get accelerated OpenGL working on my R300-based FireGL X1 card that's in my HP zx2000 workstation (ia64). As I understand it, the radeon driver in Debian unstable has beta OpenGL support for R300-based cards, but I'm unable to get it working. The key failure appears to be around this point in Xorg.0.log: (WW) RADEON(0): [agp] AGP not available (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. I have both agpgart and radeon kernel modules loaded, so I'm unsure of why AGP isn't available. Here's my xorg.conf and Xorg.0.log files: - begin xorg.conf - Section "Files" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/share/fonts/X11/75dpi" EndSection Section "Module" Load"i2c" Load"bitmap" Load"ddc" Load"dri" Load"drm" Load"extmod" Load"freetype" Load"glx" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "ATI Technologies Inc Radeon R300 NG [FireGL X1]" Driver "radeon" BusID "PCI:0:0:0" EndSection Section "Monitor" Identifier "HP 2035" HorizSync 30.0 - 76.0 VertRefresh 48.0 - 85.0 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies Inc Radeon R300 NG [FireGL X1]" Monitor "HP 2035" DefaultDepth24 SubSection "Display" Depth 24 Modes "1600x1200" EndSubSection Option "NoInt10" "True" EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection Section "DRI" Mode0666 EndSection - end xorg.conf - - begin Xorg.0.log - X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: UNKNOWN Current Operating System: Linux chiaki 2.6.18-3-mckinley #1 SMP Sun Dec 10 20:28:23 UTC 2006 ia64 Build Date: 07 July 2006 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 10 11:21:28 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "HP 2035" (**) | |-->Device "ATI Technologies Inc Radeon R300 NG [FireGL X1]" (**) |-->Input Device "Generic Keyboard" (**) |-->Input Device "Configured Mouse" (**) FontPath set to: /usr/share/fonts/X11/misc, /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 (==) RgbPath set to "/etc/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (II) Open ACPI successful (/var/run/acpid.socket) (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.0 X.Org XInput driver : 0.6 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0
Bug#397438: Panel stays blank in MergedFB mode
Michel, I also ran into this problem with a FireGL X1 (R300-based) on a Debian unstable machine. I would like to track down the changeset that introduced this problem using git-bisect, however, I would like some guidance on the best method to go about doing this. So far this is what I believe the process looks like (please add your opinion to each step below if you would be so kind): 1. Get the latest code from the git repository. a. Do I just use git_xorg? b. Do I need xcb too? c. Modular or monolith? 2. Remove the current x.org Debian packages to avoid conflicts. 3. Build x.org from the lastest git code. a. build.sh ? b. jhbuild ? c. ./autogen.sh --prefix=/tmp/modular && make && make install ? 4. Test the results to see if the second monitor starts. a. startx -- /tmp/modular/bin/Xorg ? 5. If it doesn't work, start using git-bisect. a. Find an older changeset that didn't have the problem (I've heard 6.8.2 worked, but I haven't confirmed. Any guesses?) b. git bisect start git bisect bad master git bisect good ORIG_CHANGESET 6. Do a 'make clean' here? 7. Repeat steps 3 and 4 8. Run 'git bisect good' if it worked and 'git bisect bad' if it didn't. 9. Repeat steps 6-8 until git tells me which commit is the culprit. Thanks, Bryan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
