Hi, thanks for Your prompt reply I (just) built and tested cvs xorg, results are below:
On Monday 08 of August 2005 00:01, Vladimir Dergachev wrote: > Hi Michal, > > The first thing to would be to separate Mesa driver issues from drm > issues. > > Could you do the following: > > * get latest X.org CVS tree (monolithic, i.e. xc), compile it and > check that it works without drm module It does > * get DRM from DRI CVS (i.e. freedesktop CVS) and check that the > module loads fine, e-mail us any kernel messages it produces > (should be at least a few) [drm] Initialized drm 1.0.0 20040925 PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device 0000:01:00.0 [drm] Initialized radeon 1.17.0 20050720 on minor 0: ATI Technologies Inc RV350 AS [Radeon 9600 AS] [drm] Initialized radeon 1.17.0 20050720 on minor 1: ATI Technologies Inc RV350 ?? [Radeon 9550] (Secondary) [drm] Used old pci detect: framebuffer loaded > * try starting X like this: > > X >& xorg.log & sleep 10 ; xterm & twm & while [ x=x ] ; do > sleep 1 ; sync ; done > > make sure these are all on the same command line, or you can make > a small shell script that does the same. > > The purpose here is to start X in minimal environment (only xterm > and twm) and make sure the system syncs to disk every second. > > You should be able to see hard disk light blink each second as > the result of sync - this is also an indicator that the system > is still alive. > Let us know whether you can see xterm and whether it is usable. Well, still blank screen. xorg.log attached. (I could and I can ssh to the machine) > Also, please post your results to dri-devel@ - this way they are > archived so search engines can find them for other people. [email protected] I guess? Thanks, Michal > thank you ! > > Vladimir Dergachev > > On Sun, 7 Aug 2005, [iso-8859-2] Micha³ Pytasz wrote: > > Hi, > > > > I'm sorry for bothering, I found Your e-mail address in readme file of > > cvs-downloaded r300 sources. > > On the website You were asking for tests of the > > driver. I'm sorry if I'm writting to a wrong address. > > Well I have problems making driver work. > > > > Well, I managed to build mesa sources (dowloaded from cvs at > > dri.freedesktop.org) as well as drm module, I installed it all on xorg > > built with (gentoo) ebuild xorg-x11-6.8.99.15 (according to which it's > > using cvs version from 29.07.2005). > > Unfortunately (when xorg.log says I have direct rendering) all I see is a > > blank screen (both with dvi as well as vga output) just as if xorg froze > > just before it managed to display anything (monitor does detect signal, > > the screen is just blank). > > > > To build mesa I needed to add r300 to Mesa/configs/linux-dri-x86-64 (make > > linux-dri was exitting with assembler errors). > > > > > > I configured xorg to use radeon driver, xorg.conf attached. > > I built it on a winchester athlon64, kernel 2.6.12.3 using gcc 3.4.4, > > system is running in native 64 bit mode with multilib support. > > > > my lspci says: > > > > 0000:00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge > > 0000:00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge > > 0000:00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge > > 0000:00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge > > 0000:00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge > > 0000:00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge > > 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge > > [K8T800/K8T890 South] > > 0000:00:07.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI > > Video and Audio Decoder (rev 03) > > 0000:00:07.1 Multimedia controller: Conexant: Unknown device 8811 (rev > > 03) 0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > > RTL-8169 Gigabit Ethernet (rev 10) > > 0000:00:0f.0 IDE interface: VIA Technologies, Inc. > > VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) > > 0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB > > 1.1 Controller (rev 81) > > 0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB > > 1.1 Controller (rev 81) > > 0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB > > 1.1 Controller (rev 81) > > 0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB > > 1.1 Controller (rev 81) > > 0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) > > 0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge > > [KT600/K8T800/K8T890 South] > > 0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. > > VT8233/A/8235/8237 AC97 Audio Controller (rev 60) > > 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 > > [Athlon64/Opteron] HyperTransport Technology Configuration > > 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 > > [Athlon64/Opteron] Address Map > > 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 > > [Athlon64/Opteron] DRAM Controller > > 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 > > [Athlon64/Opteron] Miscellaneous Control > > 0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AS > > [Radeon 9600 AS] > > 0000:01:00.1 Display controller: ATI Technologies Inc RV350 ?? [Radeon > > 9550] (Secondary) > > > > > > lspci -n: > > > > 0000:00:00.0 Class 0600: 1106:0282 > > 0000:00:00.1 Class 0600: 1106:1282 > > 0000:00:00.2 Class 0600: 1106:2282 > > 0000:00:00.3 Class 0600: 1106:3282 > > 0000:00:00.4 Class 0600: 1106:4282 > > 0000:00:00.7 Class 0600: 1106:7282 > > 0000:00:01.0 Class 0604: 1106:b188 > > 0000:00:07.0 Class 0400: 14f1:8800 (rev 03) > > 0000:00:07.1 Class 0480: 14f1:8811 (rev 03) > > 0000:00:0b.0 Class 0200: 10ec:8169 (rev 10) > > 0000:00:0f.0 Class 0101: 1106:0571 (rev 06) > > 0000:00:10.0 Class 0c03: 1106:3038 (rev 81) > > 0000:00:10.1 Class 0c03: 1106:3038 (rev 81) > > 0000:00:10.2 Class 0c03: 1106:3038 (rev 81) > > 0000:00:10.3 Class 0c03: 1106:3038 (rev 81) > > 0000:00:10.4 Class 0c03: 1106:3104 (rev 86) > > 0000:00:11.0 Class 0601: 1106:3227 > > 0000:00:11.5 Class 0401: 1106:3059 (rev 60) > > 0000:00:18.0 Class 0600: 1022:1100 > > 0000:00:18.1 Class 0600: 1022:1101 > > 0000:00:18.2 Class 0600: 1022:1102 > > 0000:00:18.3 Class 0600: 1022:1103 > > 0000:01:00.0 Class 0300: 1002:4153 > > 0000:01:00.1 Class 0380: 1002:4173 > > > > I am attaching xorg.log > > > > Among loaded modules I have: > > radeon 112000 0 > > drm 92584 1 radeon > > agpgart 37220 1 drm > > > > For some unknown (to me) reason I do not see amd64-agp (although it is > > probed on startup and no error message is displayed) and agpgart is > > loaded through module dependencies of amd64-agp. > > > > Anyway, when I "blow up" dri support (for example by removing drm module) > > xorg starts propperly (I can see the picture). > > > > Please let me know if You would need further details, or if I am writting > > to a wrong address. > > Michal
This is a pre-release version of the The X.Org Foundation X11. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the The X.Org Foundation "monolithic tree" CVS repository hosted at http://www.freedesktop.org/Software/xorg/ X Window System Version 6.8.99.15 Release Date: 16 July 2005 + cvs X Protocol Version 11, Revision 0, Release 6.8.99.15 Build Operating System: Linux 2.6.12-gentoo-r7 x86_64 [ELF] Current Operating System: Linux pytasz 2.6.12-gentoo-r7 #1 Mon Aug 1 12:12:35 CEST 2005 x86_64 Build Date: 08 August 2005 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: Mon Aug 8 10:16:54 2005 (==) Using config file: "/etc/X11/xorg.conf" (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (WW) ****INVALID IO ALLOCATION**** b: 0xc800 e: 0xc900 correcting
