Direct Rendering Infrastructure

[This e-mail has been automatically generated.] 
 
Please do not reply to this email. if you want to comment on the bug, go to the 
URL shown below and enter your comments there. 
  
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=314     
     




------- Additional Comments From theophile@...  2003-06-05 16:32 -------
No, I just don't know how to file a bug report. This is my first one. Sorry.     
     
     
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[This e-mail has been automatically generated.] 
 
Please do not reply to this email. if you want to comment on the bug, go to the 
URL shown below and enter your comments there. 
  
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=314     
     




------- Additional Comments From alanh@...  2003-07-06 18:03 -------
Try the new drivers which are compiled against the current CVS.

To get them goto http://www.xfree86.org/~alanh

     
     
     
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[This e-mail has been automatically generated.] 
 
Please do not reply to this email. if you want to comment on the bug, go to the 
URL shown below and enter your comments there. 
  
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=314     
     




------- Additional Comments From mharris@...  2003-07-06 18:33 -------
Hi Christopher,

The problem isn't that 3D isn't supported by DRI, but rather that the Linux
kernel does not yet support agpgart on Radeon IGP chipsets, and without working
agpgart, you have no DRI.  Theoretically it may be possible to use pcigart,
by using ForcePCIMode, but I've no idea if there are other problems that would
prevent that from working or not.

     
     
     
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

> ------- Additional Comments From mharris@...  2003-07-06 18:33 -------
> Hi Christopher,
>
> The problem isn't that 3D isn't supported by DRI, but rather that the Linux
> kernel does not yet support agpgart on Radeon IGP chipsets, and without working
> agpgart, you have no DRI.  Theoretically it may be possible to use pcigart,
> by using ForcePCIMode, but I've no idea if there are other problems that would
> prevent that from working or not.

Is this one of the many reasons why Radeon IGP 320/340M chips aren't yet
supported too?

	Luis

[This e-mail has been automatically generated.] 
 
Please do not reply to this email. if you want to comment on the bug, go to the 
URL shown below and enter your comments there. 
  
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=314     
     




------- Additional Comments From fredi@...  2003-07-08 08:33 -------
Alan, 
I tried your drivers and the only difference that I noticed is that the card 
gets detected with its real name looking  DRI, it's disabled for my card. 
glxgears goes ~ 220 fps, and 3d gl games are dog slow (2-5 fps). I tried with 
ForcePCIMode too. 
My gpu is an igp340. 
 
Hope this helps      
     
     
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[This e-mail has been automatically generated.] 
 
Please do not reply to this email. if you want to comment on the bug, go to the 
URL shown below and enter your comments there. 
  
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=314     
     




------- Additional Comments From alanh@...  2003-07-08 08:52 -------
Ah, sorry. I misread the subject. Indeed there is no 3D support for IGP. I 
don't know of anyone working on it either. Sorry.     
     
     
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[This e-mail has been automatically generated.] 
 
Please do not reply to this email. if you want to comment on the bug, go to the 
URL shown below and enter your comments there. 
  
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=314     
     




------- Additional Comments From agd5f@...  2003-07-08 09:43 -------
Dave Jones has the databooks for the ATI AGP controller (not the graphics chip),
but hasn't written agpgart support yet.  once that is done, I would imagine it
wouldn't be too hard to add DRI support to the chips. Then again, no one has IGP
databooks so who knows...     
     
     
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[This e-mail has been automatically generated.] 
 
Please do not reply to this email. if you want to comment on the bug, go to the 
URL shown below and enter your comments there. 
  
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=314     
     




------- Additional Comments From fredi@...  2003-07-08 10:05 -------
Alan, no problem, and thank you for your drivers anyway. 
Alex, yeah, I'm lurking in dri-devel for this problem and I noticed Dave 
Jones's email. And from his diary seems the linux agp driver for this thingie 
is 33% done, so let's hope ;) 
 
Anyway, if I can help with testing or everything I can do drop me a mail, 
fredi at e-salute dot it 
      
     
     
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From j.w.bijlsma@...  2003-17-07 18:31 -------
I have written an agpgart driver that probes the chipset (IGP320M) and sets up 
the GART in 1-level GATT mode, with the TLB and the GART cache disabled. 
 
I have no idea if it is useful in any way like this, but it works with the test 
programs from Dave Jones' website. Probably it isn't useful without the TLB 
enabled, but I haven't figured why this isn't working yet. 
 
	Wouter Bijlsma 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-19-07 11:11 -------
Here are the patches for the code on my system. It's in very early stage, 
for test only.
What's working:
    4x data rate on IGP320/340 internal graphics.
    Mesa demos, TuxRacer and Chromium run fine.
    Q3A has texture problem on some scenes.
What's not:
    1x and 2x data rate.
    external graphics (if you have a desktop version motherboard).
    RS300 (IGP9100) not finished.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-19-07 11:21 -------
Created an attachment (id=415)
 --> (http://bugs.xfree86.org/attachment.cgi?id=415&action=view)
Linux kernel patch for ATI IGP chipsets

The patch is built against the 2.4.18 on my system.
It uses default 2-level GART, most of code is identical to the code used 
for AMD Irongate. Make sure you have CONFIG_AGP_ATI turned on when compiling.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-19-07 11:32 -------
Created an attachment (id=416)
 --> (http://bugs.xfree86.org/attachment.cgi?id=416&action=view)
ATI IGP chipset DRI support 

This is built on top of current XFree86 CVS code.
Changes are made in all 2D, DRI kernel, and 3D client drivers, 
mostly for framebuffer base adjustment to fit into UMA on IGP chipset.
I haven't tested if this will break things on regular cards, so don't apply
this unless you want to test IGP320/340. 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From fredi@...  2003-22-07 07:21 -------
Thank you Hui for doing this, 
 
The kernel patch does not apply cleanly to vanilla 2.4.18 neither 2.4.19. I 
applied it by hand against 2.4.18(*) whitch is the most close with your patch. 
The patch against xfree-cvs does not applied cleanly too (obviously as it's 
against a cvs version) against cvs of yesterday (2003-07-21), so I applied it 
by hand too. 
 
Now the kernel during boot gives me this nice info :) : 
 
Jul 22 02:35:51 matrix kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann 
Jul 22 02:35:51 matrix kernel: agpgart: Maximum main memory to use for agp 
memory: 409M 
Jul 22 02:35:51 matrix kernel: agpgart: Detected ATI IGP330/340/345/350/M 
chipset 
Jul 22 02:35:51 matrix kernel: agpgart: AGP aperture is 64M @ 0xf4000000 
Jul 22 02:35:51 matrix kernel: [drm] AGP 0.99 on Unknown @ 0xf4000000 64MB 
Jul 22 02:35:51 matrix kernel: [drm] Initialized radeon 1.1.1 20010405 on 
minor 0 
 
But unfortunately after compiling xfree with the patch too, when starting X I 
get an kernel oops: 
 
Jul 22 02:36:17 matrix modprobe: modprobe: Can't locate module 
char-major-10-134 
Jul 22 02:36:22 matrix modprobe: modprobe: Can't locate module char-major-81 
Jul 22 02:36:22 matrix kernel: [drm:radeon_do_init_cp] *ERROR* could not find 
framebuffer! 
Jul 22 02:36:22 matrix kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 00000010 
Jul 22 02:36:22 matrix kernel:  printing eip: 
Jul 22 02:36:22 matrix kernel: c01c72e7 
Jul 22 02:36:22 matrix kernel: *pde = 1b721067 
Jul 22 02:36:22 matrix kernel: *pte = 00000000 
Jul 22 02:36:22 matrix kernel: Oops: 0000 
Jul 22 02:36:22 matrix kernel: CPU:    0 
Jul 22 02:36:22 matrix kernel: EIP:    0010:[radeon_do_cleanup_cp+55/320]    
Not tainted 
Jul 22 02:36:22 matrix kernel: EIP:    0010:[<c01c72e7>]    Not tainted 
Jul 22 02:36:22 matrix kernel: EFLAGS: 00013246 
Jul 22 02:36:22 matrix kernel: eax: 00000000   ebx: dd588180   ecx: 00000000   
edx: 00000000 
Jul 22 02:36:22 matrix kernel: esi: c1757800   edi: dc1b7f08   ebp: c1757800   
esp: dc1b7eb8 
Jul 22 02:36:22 matrix kernel: ds: 0018   es: 0018   ss: 0018 
Jul 22 02:36:22 matrix kernel: Process X (pid: 1071, stackpage=dc1b7000) 
Jul 22 02:36:22 matrix kernel: Stack: c01c38b0 c170f388 dc61db80 dc61db80 
dd588180 c01c6af6 c1757800 00000000 
Jul 22 02:36:22 matrix kernel:        000000c4 00000138 dc1b7f04 dc61dc40 
dc1b7f08 c1757800 dcfb4c80 dc292400 
Jul 22 02:36:22 matrix kernel:        c01c7466 c1757800 dc1b7f08 00000054 
00000001 00000898 00000000 40000000 
Jul 22 02:36:22 matrix kernel: Call Trace: [radeon_alloc+80/128] 
[radeon_do_init_cp+134/2112] [radeon_cp_init+118/128] [rade 
on_ioctl+205/304] [sys_ioctl+185/448] 
Jul 22 02:36:22 matrix kernel: Call Trace: [<c01c38b0>] [<c01c6af6>] 
[<c01c7466>] [<c01c1e0d>] [<c0143e39>] 
Jul 22 02:36:22 matrix kernel:    [system_call+51/56] 
Jul 22 02:36:22 matrix kernel:    [<c0107337>] 
Jul 22 02:36:22 matrix kernel: 
Jul 22 02:36:22 matrix kernel: Code: 8b 50 10 85 d2 74 0b 8b 40 04 85 c0 0f 85 
8a 00 00 00 8b 83 
 
Maybe I've forgotten to include something in the kernel build? I have the 
framebuffer compiled in the kernel (not modular), the selected driver is 
radeon, but the same happens with vesafb too. But FWIK the kernel's 
framebuffer driver is not used by xfree so I can not understand this oops. Any 
sugestions welkomed. BTW, as for your comments about the patch working in agp4 
only I added this in my XF86Config-4 (Including all the Device section for 
completeness): 
 
Section "Device" 
    Identifier "device1" 
    VendorName "ATI Technologies Inc" 
    BoardName "ATI Radeon" 
    Driver "radeon" 
    Option "DPMS" 
    Option "AGPMode" "4"		<- This is what I added 
EndSection 
 
 
I tried agptool too and here's the output with your patch: 
 
agptool by Dave Jones. <davej@...> 
Found AGP host bridge. 
1002:cab2 :-1002:cab2 
Host capabilities: 
 Compliant with version 2.0 of the AGP standard. 
 It is capable of doing x4 AGP, but AGP transfers are currently disabled. 
 
Found AGP graphics card. 
1002:4337 :-1002:4337 
Card capabilities: 
 Compliant with version 2.0 of the AGP standard. 
 It is capable of doing x4 AGP, but AGP transfers are currently disabled. 
System is capable of doing x4 AGP. 
rate before: f000217 
setting rate to f000214 
 
Here's the output without your patch: 
 
agptool by Dave Jones. <davej@...> 
Found AGP host bridge. 
1002:cab2 :-1002:cab2 
Host capabilities: 
 Compliant with version 2.0 of the AGP standard. 
 It is capable of doing x4 AGP, but is not initialised. 
 
Found AGP graphics card. 
1002:4337 :-1002:4337 
Card capabilities: 
 Compliant with version 2.0 of the AGP standard. 
 It is capable of doing x4 AGP, but is not initialised. 
System is capable of doing x4 AGP. 
Couldn't open /dev/agpgart 
 
 
(*) I tried the kernel patch to apply to vanilla 2.4.22-pre7 too but from 
kernel 2.4.21 there is no num_of_masks member to the agp_bridge_data struct. 
I'll look at the conversion of the other drivers, the change in the kernel 
happened during 2.4.21. 
 
Hope this helps, and of course if you need some test being done, just ask. 
 
Bye, 
Fredi 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From j.w.bijlsma@...  2003-22-07 09:04 -------
Hi Hui, 
 
I also tried your patches, but with different success. The kernel patch worked ok 
for me (vanilla 2.4.18, nu patch problems). AGP and DRM initialize fine. 
 
When I run the patched CVS X (4.3.99.8) it hardlocks on 2.4.18. I got it to load 
only once. When I checked the logfiles, there were some DRI/DRM error messages 
like '[drm] cannot open /dev/dri/card0: Device or resource busy' and '[dri] - 
driCreateScreen failed'. Or something like that. I haven't been able to reproduce 
the logs, because right now the whole thing hardlocks the system. The problem 
seems to be in the X build, because testgart and agptool work fine. Agptool 
output and XFree86 settings are exactly identical to Frederik Nosi's (see posting 
above). 
 
So I tried porting the agpgart driver to 2.5.73, which was pretty easy. Again no 
problems with testgart and agptool, and X starts without crashing. Sadly, still no 
direct rendering. The logfiles only said '[W] agp: AGP disabled' . Maybe this is 
because of a version check or something? 
 
Anyways I would like to keep testing new patches, especially with the driver 
ported to 2.5. Do you have an indication when your XFree patch is going to be 
merged into XFree-CVS? 
 
	Wouter 
 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-22-07 10:03 -------
Thanks for testing. One thing I can think of about the error you got is that 
you might have loaded the original radeon dri module come with the Linux kernel 
source. This module is not patched and should not be used. You should use the 
patched one inside XFree86 source tree (either replace radeon.o in your default
module path or insert the patched one manually). 
The kernel agpgart patch is built on the kernel source from a retail CD (just 
something handy on my system), it shouldn't be difficult to apply it manually 
as you did. The XFree radeon driver in CVS has been changed these two days, if 
you want the patch to be applied cleanly you can get the original version with 
xf-4_3_99_8 tag.




-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From fredi@...  2003-22-07 10:22 -------
> Thanks for testing. 
Thank you for your work Hui, 
 
> One thing I can think of about the error you got is that you might have 
> loaded the original radeon dri module come with the Linux kernel source. 
> This module is not patched and should not be used. 
 
Stupid me (good news for the patch :) ), I compiled (statically) the drm 
module of the kernel. Maybe I should not test things in 2:00 of the morning. 
 
> You should use the 
> patched one inside XFree86 source tree (either replace radeon.o in your 
> default module path or insert the patched one manually).  
 
Sure, expect my reports tomorrow as from now I'll be offline. 
About the patches, it was trivial applying by hand them, so no problem, it was 
just to inform you. I wonder how happened to Wouter to apply cleanly, just now 
I downloaded the 2.4.18 vanilla and I get rejects ;) 
 
I forgot to run the Oops through ksymoops, here is the output just in case: 
>>EIP; c01c72e7 <radeon_do_cleanup_cp+37/140>   <===== 
 
Trace; c01c38b0 <radeon_alloc+50/80> 
Trace; c01c6af6 <radeon_do_init_cp+86/840> 
Trace; c01c7466 <radeon_cp_init+76/80> 
Trace; c01c1e0d <radeon_ioctl+cd/130> 
Trace; c0143e39 <sys_ioctl+b9/1c0> 
Trace; c0107337 <system_call+33/38> 
 
Code;  c01c72e7 <radeon_do_cleanup_cp+37/140> 
00000000 <_EIP>: 
Code;  c01c72e7 <radeon_do_cleanup_cp+37/140>   <===== 
   0:   8b 50 10                  mov    0x10(%eax),%edx   <===== 
Code;  c01c72ea <radeon_do_cleanup_cp+3a/140> 
   3:   85 d2                     test   %edx,%edx 
Code;  c01c72ec <radeon_do_cleanup_cp+3c/140> 
   5:   74 0b                     je     12 <_EIP+0x12> 
Code;  c01c72ee <radeon_do_cleanup_cp+3e/140> 
   7:   8b 40 04                  mov    0x4(%eax),%eax 
Code;  c01c72f1 <radeon_do_cleanup_cp+41/140> 
   a:   85 c0                     test   %eax,%eax 
Code;  c01c72f3 <radeon_do_cleanup_cp+43/140> 
   c:   0f 85 8a 00 00 00         jne    9c <_EIP+0x9c> 
Code;  c01c72f9 <radeon_do_cleanup_cp+49/140> 
  12:   8b 83 00 00 00 00         mov    0x0(%ebx),%eax 
 
Bye, 
Fredi 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-22-07 10:32 -------
Hi Wouter, my previous message is the reply to Frederik Nosi (you got in before 
I sent). You may have the same problem as Frederik -- loaded the original radeon
DRI kernel module (radeon.o) from the Linux kernel tree. Make sure you used the 
patched one in xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/
As for when the patch is going to be merged into XFree-CVS, it probably won't 
until it's merged into DRI project first and tested there.
I used the XFree CVS code because that's somethng handy on my system.


-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-22-07 11:44 -------
The correct thing to do then would be to bump the DRM minor version and only
attempt to initialize the DRI on IGP chips if the DRM has high enough a minor
version.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-22-07 17:39 -------
This could become a backwards compatibility nightmare, as the framebuffer
aperture is currently hardcoded everywhere to be at 0. :\ At the very least, the
DRM minor version must be bumped, new entries must only be added at the end of
structs used for communication between components, and each component must be
careful only to use them if they are known to contain valid values.

However, as a different memory layout is desirable for other reasons like video
capturing, we should make another attempt at a discussion to get it right once
and for all, probably on dri-devel but at least including people like Ben
Herrenschmidt and Vladimir Dergachev as well.

Here's an idea for a scheme to preserve at least some level of backwards
compatibility: Add a new ioctl for the X server to tell the DRM 'I want to use
the new memory layout'. Unless this is called, everything keeps working as it is
now (i.e. things like DRI on IGP chips or video capturing won't work).
Otherwise, the DRM bumps its major version as well. The 3D driver is adapted to
cope with both major DRM versions. This would provide backwards compatibility
for the new 3D driver with old X servers / DRMs / hardware. Old 3D drivers would
stop working with the combination of new X server and new DRM, but this might be
as good as it gets in terms of backwards compatibility. Or maybe someone else
has a better idea?

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

I don't think we can get away with breaking older clients, though this does 
look like it would only break the situation where you have old 3d client with 
new 2d driver, which is a slightly unusual situation.

The real question is how much does the 3d client actually rely on the radeon 
memory layout?  It gets pointers to most things it cares about in the 
initialization messages, these could be adjusted to point to the correct 
places in the new layout.

Further, if a client is known to be old, the kernel can go through its 
commands & adjust them for the new layout (assuming we can't dupe the client 
into using the right values for itself).

I'd prefer this approach (in addition to the turn-on ioctl) to anything that 
involves bumping the major version.

Keith


> ------- Additional Comments From michel@...  2003-22-07 17:39 -------
> This could become a backwards compatibility nightmare, as the framebuffer
> aperture is currently hardcoded everywhere to be at 0. :\ At the very least, the
> DRM minor version must be bumped, new entries must only be added at the end of
> structs used for communication between components, and each component must be
> careful only to use them if they are known to contain valid values.
> 
> However, as a different memory layout is desirable for other reasons like video
> capturing, we should make another attempt at a discussion to get it right once
> and for all, probably on dri-devel but at least including people like Ben
> Herrenschmidt and Vladimir Dergachev as well.
> 
> Here's an idea for a scheme to preserve at least some level of backwards
> compatibility: Add a new ioctl for the X server to tell the DRM 'I want to use
> the new memory layout'. Unless this is called, everything keeps working as it is
> now (i.e. things like DRI on IGP chips or video capturing won't work).
> Otherwise, the DRM bumps its major version as well. The 3D driver is adapted to
> cope with both major DRM versions. This would provide backwards compatibility
> for the new 3D driver with old X servers / DRMs / hardware. Old 3D drivers would
> stop working with the combination of new X server and new DRM, but this might be
> as good as it gets in terms of backwards compatibility. Or maybe someone else
> has a better idea?
>

On Tue, 2003-07-22 at 23:53, Keith Whitwell wrote:
> I don't think we can get away with breaking older clients, though this does 
> look like it would only break the situation where you have old 3d client with 
> new 2d driver, which is a slightly unusual situation.

Yes, I think the 2D driver and in particular the DRM are much more
likely to be old.


> The real question is how much does the 3d client actually rely on the radeon 
> memory layout?  It gets pointers to most things it cares about in the 
> initialization messages, these could be adjusted to point to the correct 
> places in the new layout.

I'm afraid this doesn't work, e.g.

-   rmesa->hw.ctx.cmd[CTX_RB3D_COLOROFFSET] = rmesa->state.color.drawOffset;
+   rmesa->hw.ctx.cmd[CTX_RB3D_COLOROFFSET] = rmesa->state.color.drawOffset+rmesa->radeonScreen->fbBase;

and

	 rmesa->state.color.drawOffset = rmesa->radeonScreen->frontOffset;

but rmesa->state.color.drawOffset probably needs to stay the same for
software rendering? (it seems to be used as an offset into the
framebuffer mapping)


> Further, if a client is known to be old, the kernel can go through its 
> commands & adjust them for the new layout

This might actually work, nifty. :) I wonder how much effort this would
take and/or whether it would have an impact on performance though.

> I'd prefer this approach (in addition to the turn-on ioctl) to anything that 
> involves bumping the major version.

Well, if this works, we might actually get away without bumping the
major, which would be great... let's hope this works out taking into
consideration everything including video capturing, radeonfb, ...


-- 
Earthling Michel Dänzer   \  Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast  \     http://svcs.affero.net/rm.php?r=daenzer

Michel D=E4nzer wrote:
> On Tue, 2003-07-22 at 23:53, Keith Whitwell wrote:
>=20
>>I don't think we can get away with breaking older clients, though this =
does=20
>>look like it would only break the situation where you have old 3d clien=
t with=20
>>new 2d driver, which is a slightly unusual situation.
>=20
>=20
> Yes, I think the 2D driver and in particular the DRM are much more
> likely to be old.
>=20
>=20
>=20
>>The real question is how much does the 3d client actually rely on the r=
adeon=20
>>memory layout?  It gets pointers to most things it cares about in the=20
>>initialization messages, these could be adjusted to point to the correc=
t=20
>>places in the new layout.
>=20
>=20
> I'm afraid this doesn't work, e.g.
>=20
> -   rmesa->hw.ctx.cmd[CTX_RB3D_COLOROFFSET] =3D rmesa->state.color.draw=
Offset;
> +   rmesa->hw.ctx.cmd[CTX_RB3D_COLOROFFSET] =3D rmesa->state.color.draw=
Offset+rmesa->radeonScreen->fbBase;
>=20
> and
>=20
> 	 rmesa->state.color.drawOffset =3D rmesa->radeonScreen->frontOffset;
>=20
> but rmesa->state.color.drawOffset probably needs to stay the same for
> software rendering? (it seems to be used as an offset into the
> framebuffer mapping)
>=20
>=20
>=20
>>Further, if a client is known to be old, the kernel can go through its=20
>>commands & adjust them for the new layout
>=20
>=20
> This might actually work, nifty. :) I wonder how much effort this would
> take and/or whether it would have an impact on performance though.

A slight impact, but that's the price you pay for backwards compatibility=
.  If=20
people want max performance, they can upgrade to a newer 3d client.  In a=
ny=20
case, I doubt it would be measurable.

>=20
>>I'd prefer this approach (in addition to the turn-on ioctl) to anything=
 that=20
>>involves bumping the major version.
>=20
>=20
> Well, if this works, we might actually get away without bumping the
> major, which would be great... let's hope this works out taking into
> consideration everything including video capturing, radeonfb, ...

More than great - necessary.  We can't be bumping the major number withou=
t=20
very good reason, and I just don't see that here.

Keith

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-22-07 22:49 -------
The patch doesn't really break any existing code. You can apply the patch and 
all supported cards should still work (if not, it's a bug). I've tested a 7500 
breifly with the patch applied, everything worked properly. All it changes is a 
fb_offset added when sending a fb location related packet (like ColorOffset, 
DepthOffset, TxOffset). For all regular cards this fb_offset is set to zero and 
FB_LOCATION is not changed. I haven't tried any video capture thing though, but 
don't think there will be a big compatibity issue. All existing IGP boards only 
have TV-out, no video-in feature.


-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From matthieu.bonetti@...  2003-23-07 04:06 -------
I tried to apply your agp patch to a 2.4.21. I had to do it by hand and I get an
error while compiling at this line:
agp_bridge.num_of_masks = 1;
I read that there was some agp cleanup since the 2.4.20. I simply removed this
line from the source code and it compiles but my card (IGP 340M) is not detected
by the kernel.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-23-07 04:55 -------
If only it was this simple... :) You have to consider all possible combinations
of patched/unpatched X server, DRM and 3D driver.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From fredi@...  2003-23-07 05:25 -------
Hi Hui, I'm back online and with good news.  
  
Yes, after replacing the kernel's drm driver with the one from dri with your  
patch, my card works fine in AGP4!!!  
  
Dri is enabled, and glxinfo confirmes this. Now for the performance 
difference; 
 
x11perf - strange enough, seems faster without dri: 
 
with your changes: 
 
[fredi@... log]$ x11perf -repeat 1 -shmput500 
x11perf - X11 performance program, version 1.5 
The XFree86 Project, Inc server version 40399008 on :0.0 
from matrix 
Wed Jul 23 01:42:20 2003 
 
Sync time adjustment is 0.0350 msecs. 
 
    800 reps @   6.3488 msec (   158.0/sec): ShmPutImage 500x500 square 
 
before was: 
 
[fredi@... log]$ x11perf -repeat 1 -shmput500 
x11perf - X11 performance program, version 1.5 
The XFree86 Project, Inc server version 40399008 on :0.0 
from matrix 
Wed Jul 23 01:56:03 2003 
 
Sync time adjustment is 0.0281 msecs. 
 
   1200 reps @   5.5609 msec (   180.0/sec): ShmPutImage 500x500 square 
 
May this be caused by the kernel? the test without your changes is done with 
vanilla 2.4.22-pre6. 
 
ArmageTron: 11 - 30 fps, before was unplayable, 3 seconds to change a 
selection in the game's menu! 
Tuxracer: fine at 1024x768, before was unplayable 
glxgears: 370fps (~10% variation), before was max 240fps (~10% variation) 
 
Installed the wolfenstein's demo and it runs fine! Without your patches one 
needs 10 seconds to select a menu. FWIK this game uses Quake's engine, I never 
saw the texture problems that you were noticing. 
 
In XF86Config-4 I made this changes besides setting agp4: 
 
    Option "AGPFastWrite" "On" 
    Option "EnablePageFlip" "On" 
 
AGPFastWrite does not seem to make a big difference, but EnablePageFlip gives 
a noticeable speedup. 
 
No crashes, nothing strange at all. I dont know what other stress testing I 
can do to this, if you want other tests done just ask! 
 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-23-07 05:41 -------
Direct copies to the framebuffer may actually be faster than using the CP for
image writes on some systems. Can you also do the same comparison with different
ROPs though, e.g.

x11perf -rop GXxor -shmput500

The 3D performance looks reasonable.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From fredi@...  2003-23-07 06:14 -------
Michel, about the backwards compatibility it seems not a problem. With the 
same xfree/dri with Hui's patch but a different kernel (2.4.22-pre6) without 
the patch, Xfree works fine but without dri. During boot it does not find the 
gart driver so fallback's to soft accel for 3d. 2d performance is the same, 
nothing strange. With the kernel patch but with dri unpatched the situation is 
the same, no dri, nothing strange. Or you were talking about other things? 
 
And now the x11perf results, 
 
* without Hui's patch: 
 
Sync time adjustment is 0.0269 msecs. 
 
    280 reps @  20.0745 msec (    49.8/sec): (xor) ShmPutImage 500x500 square 
    280 reps @  20.0010 msec (    50.0/sec): (xor) ShmPutImage 500x500 square 
    280 reps @  20.1826 msec (    49.5/sec): (xor) ShmPutImage 500x500 square 
    280 reps @  19.9949 msec (    50.0/sec): (xor) ShmPutImage 500x500 square 
    280 reps @  19.9948 msec (    50.0/sec): (xor) ShmPutImage 500x500 square 
    1400 trep @  20.0496 msec (    49.9/sec): (xor) ShmPutImage 500x500 square 
 
* With Hui's patch: 
 
Sync time adjustment is 0.0326 msecs. 
 
   1200 reps @   5.5392 msec (   181.0/sec): (xor) ShmPutImage 500x500 square 
   1200 reps @   5.4970 msec (   182.0/sec): (xor) ShmPutImage 500x500 square 
   1200 reps @   5.4970 msec (   182.0/sec): (xor) ShmPutImage 500x500 square 
   1200 reps @   5.5270 msec (   181.0/sec): (xor) ShmPutImage 500x500 square 
   1200 reps @   5.4974 msec (   182.0/sec): (xor) ShmPutImage 500x500 square 
   6000 trep @   5.5115 msec (   181.0/sec): (xor) ShmPutImage 500x500 square 
 
* In another system with a matrox g400max drm enabled, xfree 4.3, lots of 
progs in the background and not optimized: 
 
Sync time adjustment is 0.1122 msecs. 
 
    200 reps @  28.3227 msec (    35.3/sec): (xor) ShmPutImage 500x500 square 
    200 reps @  28.2777 msec (    35.4/sec): (xor) ShmPutImage 500x500 square 
    200 reps @  28.2889 msec (    35.3/sec): (xor) ShmPutImage 500x500 square 
    200 reps @  28.7919 msec (    34.7/sec): (xor) ShmPutImage 500x500 square 
    200 reps @  30.5268 msec (    32.8/sec): (xor) ShmPutImage 500x500 square 
   1000 trep @  28.8416 msec (    34.7/sec): (xor) ShmPutImage 500x500 square 
 
Hope this helps. 
 
(BTW, what does mean CP?) 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-23-07 07:29 -------
Consider for example an unpatched X server with a patched DRM (only one of eight
scenarios to consider): the DRI will be enabled, but the DRM will read the new
fb_base field, which the X server has never initialized. Oops. Not to mention
that it will read garbage for lots of fields, as the order of the fields in the
struct has changed... an elegant solution might be to set the framebuffer
aperture base using a new ioctl, which would implicitly tell the DRM to use the
new memory layout. The clients could use another (or even the same?) ioctl to
tell the DRM what they think the framebuffer aperture base is, so the DRM can
fixup the client commands.

The x11perf results show that accelerated image writes do pay off for non-GXcopy
ROPs, I'll disable them for GXcopy. Thanks for testing.

CP stands for Command Processor, the Radeon DMA command engine, which is used
for issuing commands to the chip when the DRI is enabled.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From fredi@...  2003-23-07 11:06 -------
Michel, thank you for your explanation, now I understand the problem. Now if 
the field is added in the end of the struct, the old xfree does not read 
garbage when trying to get the other members. And because it's old and dont 
have the knowledge of the existence of the new field, does not touch it. Of 
course this works only inf the structure is passed _alwas_ by pointer. Hmm, 
but the drm will get garbage in that field. Can this dirty && ugly hack work? 
Anyway, your solution seems the right way, but it seems that it will take a 
lot of time to have the change included in the kernel, xfree and dri. 
 
BTW, now I noticed a problem with xfree 4.3.99.8 (cvs from 2003-07-21), 
whenever I try to start a x program using ssh to the remote computer which has 
the xfree from cvs, I get this message: 
 
_X11TransSocketOpen: socket() failed for tcp 
_X11TransSocketOpenCOTSClient: Unable to open socket for tcp 
_X11TransOpen: transport open failed for tcp/localhost:10 
Error: Can't open display: localhost:10.0 
 
trying a "telnet localhost 6010" I can connect. Trying the reverse, running 
from a ssh to the other computer with xfree 4.3.0 everything works as usual. 
This seems unrelated to this changes, is this some error in my compiling? 
Should I file a new bug? 
 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-23-07 12:19 -------
> If only it was this simple... :) You have to consider all possible 
combinations
> of patched/unpatched X server, DRM and 3D driver.

What I was trying to say is that the code doesn't break regular cards 
suppose all versions are matched. Of course there should be some version bump
or some other methods as you mentioned to keep things backward-compatible when
this code is ready to merge. Currently it's still in the early testing stage 
and there are many things are still not working properly.


-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-23-07 19:44 -------
As I said in an earlier comment, putting new fields at the end of structs is
only one of a number of requirements.

As for taking long, it doesn't have to if we keep making progress like this.
IMHO it's worth taking the time to get this right at any rate though. The next
XFree86 release isn't exactly around the corner yet. ;)

As for your problem with ssh, it's not related to this bug. It could be related
to the IPv6 problems being discussed on the devel list, or it could just be a
configuration issue.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From j.w.bijlsma@...  2003-24-07 08:30 -------
Hi Hui, 
 
I finally managed to test the patches thoroughly, only after I found out there was 
a problem with the USB-OHCI driver in 2.4, causing the keyboard to lock up if 'USB 
legacy support' was enabled in the BIOS. 
 
Anyways, everything works almost flawlessly: TuxRacer, NeHe OpenGL turorials, 
Java3D, Quake 3. Quake 3 had a lot of texture problems (missing/flickering 
textures, misaligned textures), but apart from that it ran smoothly in 800x600 with 
maximum detail. Thanks a lot! If you need XFree logs or x11perf benchmarks, I 
can send them. 
 
Michel: 
From the discussion about the fb pointer and the new memory layout I guess 
there's not much I can contribute to speed up getting the driver to work with 2.5? 
Do you think this wil be sorted out before 4.4.0 is released? I really need the 2.5 
ACPI and CPUFreq support, because my system runs really hot and eats batteries 
for lunch with 2.4 ;-( 
 
	Wouter 
 
  

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-24-07 08:59 -------
It shouldn't be hard to port the DRM changes to 2.6.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Am Donnerstag, 24. Juli 2003 14:30 schrieb bugzilla-daemon@...:
> http://bugs.xfree86.org/show_bug.cgi?id=314
>
>
>
>
>
> ------- Additional Comments From j.w.bijlsma@...  2003-24-07 08:30
> ------- Hi Hui,
>
> I finally managed to test the patches thoroughly, only after I found out
> there was a problem with the USB-OHCI driver in 2.4, causing the keyboard
> to lock up if 'USB legacy support' was enabled in the BIOS.
>
> Anyways, everything works almost flawlessly: TuxRacer, NeHe OpenGL
> turorials, Java3D, Quake 3. Quake 3 had a lot of texture problems
> (missing/flickering textures, misaligned textures), but apart from that it
> ran smoothly in 800x600 with maximum detail. Thanks a lot! If you need
> XFree logs or x11perf benchmarks, I can send them.
>
> Michel:
> From the discussion about the fb pointer and the new memory layout I guess
> there's not much I can contribute to speed up getting the driver to work
> with 2.5? Do you think this wil be sorted out before 4.4.0 is released? I
> really need the 2.5 ACPI and CPUFreq support, because my system runs really
> hot and eats batteries for lunch with 2.4 ;-(

Use the ACPI and CPUFreq patches, then.
Sensors is available, too.

Cheers,
	Dieter

BTW 2.4.22-pre7has ACPI patches in.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From diemumiee@...  2003-25-07 05:04 -------
I have problems getting the patched drivers to work. I recompiled the kernel (2.
4.21-ac4) with the patche applied. The AGPGART modules loads without problems. 
Then i compiled Xfree-4.3.99.8 with the dri patches.
So what next?
Do i have to change the  Xfreeconfig?
How should i replace the kernel radeon module?

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From fredi@...  2003-25-07 05:28 -------
Did the patch to the kernel applied cleanly? It was against 2.4.18. 
As for your question, swap the radeon.o module of the kernel with radeon.o 
from dri. 
This should do the trick (for me it works fine). 
When building dri in xfree, give it the path to the kernel sources that you 
patched, eg: 
 
make -f Makefile.linux LINUXDIR=/path/to/patched/kernel 
 
Next modify this way the "Device" section of your XF86Config-4 (it's a good 
idea to conserve a copy of the original XF86Config-4 BTW): 
 
Section "Device" 
    Identifier "device1" 
    VendorName "ATI Technologies Inc" 
    BoardName "ATI Radeon" 
    Driver "radeon" 
    Option "DPMS" 
    Option "AGPMode" "4" 
    Option "AGPFastWrite" "On" # defaults to off 
    Option "EnablePageFlip" "On" # defaults to off 
EndSection 
 
This should be the dri section of your XF86Config-4, the mode is dangerous as 
anyone can use dri, but as you are using experimental progs anyway: 
 
Section "DRI" 
    Mode 0666 
EndSection 
 
And remember to load the dri module, in XF86Config-4: 
 
Section "Module" 
 
[...] 
 
    Load "dri" # direct rendering 
EndSection 
 
Start xfree aand enjoy. 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From diemumiee@...  2003-25-07 08:42 -------
Oh I missed the part where i had to build the driver in the xfree source. It 
worked fine. The kernel patch did not work directly, since the ac tree as 
support for nforce chipsets too, and i had to patch the enum and the config 
files by hand. 

Ok now i do the enjoy part.
Thanks a lot!

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From matthieu.bonetti@...  2003-28-07 05:53 -------
Can anyone send me the binaries ? I have some problems compiling XFree86.
gcc says: radeon_dri.c:743: structure has no member named `IsIGP'
I am compiling it from the cvs from yesterday.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From fredi@...  2003-28-07 06:28 -------
Matthiew, if you want to try the new driver for IGP, as Hui sayed, use the 
xfree/dri sources with the xf-4_3_99_8 tag. 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From abe@...  2003-28-07 22:23 -------
Hi, Just wanted to share my positive experience with Hui Yu's patches.

I just bought a Sony VAIO FRV-25 (w/o the modem problem) running Gentoo, here's
an lspci after Hui's patches:

00:00.0 Host bridge: ATI Technologies Inc: Unknown device cbb2 (rev 02)
00:01.0 PCI bridge: ATI Technologies Inc PCI Bridge [IGP 340M]
00:03.0 Modem: ALi Corporation Intel 537 [M5457 AC-Link Modem]
00:04.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link
Controller Audio Device (rev 02)
00:06.0 Bridge: ALi Corporation M7101 PMU
00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV]
00:0a.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev aa)
00:0a.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev aa)
00:0a.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 02)
00:0c.0 USB Controller: VIA Technologies, Inc. USB (rev 50)
00:0c.1 USB Controller: VIA Technologies, Inc. USB (rev 50)
00:0c.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
00:0f.0 IDE interface: ALi Corporation M5229 IDE (rev c4)
00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP 340M

I successfully patched 2.4.20-gentoo-r5 with a little work.  It seems that some
of the ATI stuff gets inserted inside the ALI section in agpgart_be.c by accident.  

I also had to change agp.h in the ATI_RS200 section to cbb2 instead of cab2. 
Once I did that, all the kernel stuff came up!  :-)

Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 409M
agpgart: Detected ATI IGP330/340/345/350/M chipset
agpgart: AGP aperture is 64M @ 0xf4000000

Following that, I installed xfree-4.3.99.8, as suggested here.  This fixed a
problem I had with external monitors and 4.3.0 permanantly turning off the LCD.
 Thanks Hui Yu!  Great Job!  :))

I still get this line, but I'll continue to hack at it...
(II) RADEON(0): Direct rendering disabled

But I wanted you guys to know I appreciate your efforts and your progress has
not gone unnoticed.

Thanks!

abe@...




-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From martin.wiesner@...  2003-29-07 04:54 -------
I patched everything as described by Fredo, but DRI Rendering is still NO. Here
is why (I think), who can have a good guess/tip to solve this? 

drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "radeon"
(II) RADEON(0): [drm] drmOpen failed
(EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.
(II) RADEON(0): Memory manager initialized to (0,0) (1024,8191)
(II) RADEON(0): Reserved area from (0,768) to (1024,770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7421
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
	Screen to screen bit blits
	Solid filled rectangles
	8x8 mono pattern filled rectangles
	Indirect CPU to Screen color expansion
	Solid Lines
	Dashed Lines
	Scanline Image Writes
	Offscreen Pixmaps
	Setting up tile and stipple cache:
		32 128x128 slots
		32 256x256 slots
		16 512x512 slots
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7413
(**) Option "dpms"
(**) RADEON(0): DPMS enabled
(WW) RADEON(0): Option "Rotate" is not used
(II) RADEON(0): Direct rendering disabled

Thanks for all your work,
Martin

martin.wiesner@...

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From j.w.bijlsma@...  2003-29-07 07:18 -------
Please read all comments before posting. Both of you probably need to replace 
the DRM module that comes with the 2.4 kernel with the DRM module from the 
patched XFree. It's in 
xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/radeon.o. This has 
been posted 3 times already, reading before you post might free up some of Hui's 
time to develop the driver ;-) 
 
Regards, 
	Wouter Bijlsma  

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From martin.wiesner@...  2003-29-07 07:27 -------
The module is the right one. Fredi and me are working on this. It is sure that
the rigth module right place!! But the problem is this:

drmOpenDevice: node name is /dev/dri/card0

fredi made the proposal to do a: mknod /dev/dri/card0
but this is non persistent! and XF doesn't find it. 
Has anybody suggestion about this?

Martin

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From alan@...  2003-29-07 07:49 -------
Do "modprobe radeon" and figure out why it fails

When that works you can worry about the X stuff. 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From fredi@...  2003-29-07 08:08 -------
I rediffed the kernel patch against vanilla 2.4.22-pre8. I looked at the 
agpgart changes from 2.4.18 to 2.4.22-pre8 and adapted the patch accordingly 
(hopefully). this patch changes the kernel's extraversion to -pre8-igp so you 
can have -pre8 vanilla and the patched one installed at the same time. Now it 
works just fine but for a strange reason that I've not yet figured, the dri 
driver does not work when compiled against kernels newer than 2.4.21 (the -pre 
series). During insmod/modprobe it complains about the mmu_cr4_features being 
unresolved. But Looking at System.map it is present. Anyway, I "solved" this 
changing the version to a 2.4.21 kernel source to the newer one and building 
the dri module against it (so it will not complain during insmod about being 
compiled for another kernel version). 
Alan, as you are looking this thread, any hint about this? How does the patch 
look? 
 
Anyway, I'll continue to update the kernel side patch to newer kernels if I 
could. 
Patch attached. 
 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From fredi@...  2003-29-07 08:10 -------
Created an attachment (id=437)
 --> (http://bugs.xfree86.org/attachment.cgi?id=437&action=view)
The kernel patch for 2.4.22-pre8

The kernel patch for 2.4.22-pre8

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From drshatwell@...  2003-29-07 13:43 -------
First of all, thanks to everyone working on this code - my IGP320M based 
laptop now has accelerated 3D.

At least, some of the time. Other times it kernel panics.
After trying a few things - checking agpgart and radeon modules are loaded, 
that the XFree radeon rather than kernel radeon module is in use and 
everything else mentioned in this report is set up correctly - I have tracked 
it down to one thing: is the network connected. 

[After a few minutes experimentation, some network sniffing, and a lot of 
kernel panics...]

OK, it is a DNS problem. If the noteback can resolve its own name then it 
works. If the host name lookup fails then it panics.
Simple to fix: add entry in /etc/hosts
I'm sure it worked when running the previously running X (Mandrake 9.1 
installation with X 4.3.0) without a network connection, but it is unlikely to 
be the fault of the graphics driver code.

Thanks again for the 3d accel.




-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

bugzilla-daemon@... wrote:
> 
> ------- Additional Comments From abe@...  2003-28-07 22:23 -------
> Hi, Just wanted to share my positive experience with Hui Yu's patches.
> 
> I just bought a Sony VAIO FRV-25 (w/o the modem problem) running Gentoo, here's
> an lspci after Hui's patches:
> 
I had this working a few days ago. I recently bought a Sony VAIO FRV27
and created patches against 2.4.21 to get AGPGART and 3D working. I
have attached the patch and would like comments, specifically on the
PCI ID stuff. I do not have patches against X DRI. I also make changes
in the agpgart_be.c to get rid of compiler warnings. The lines with
#ifndef CONFIG_AGP_ATI was to get rid of warnings about unused
functions. Note the addition of PCI_DEVICE_ID_ATI_RS200M and the changes
that I made to the ALi PCI quirks. I also separated out the IGP 345M to
be by itself, since it obviously has a new PCI device ID. Comments
please?

-Steve

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From theophile@...  2003-29-07 14:41 -------
I've been watching this ever since I opened it. It's at the point where I'm
ready to try it out. Is there a patch for the 2.5 kernels? I'm running 2.5.69
now in order to support other hardware in my notebook. Thanks! 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

bugzilla-daemon@... wrote:
> 
> I just bought a Sony VAIO FRV-25 (w/o the modem problem) running Gentoo, here's
> an lspci after Hui's patches:
> 
And I just bought a FRV27. I had the patches for this stuff days ago, but I did
not get a chance to post them since I was at OLS. This patch is against 2.4.21
based off of Hui's 2.4.18 patch with added stuff for ATI and the 345M. Please
note the PCI ID additions that I would like to propose. Also notice the changes
to the ALi driver and PCI quirks. I felt that PCI_DEVICE_ID_ATI_RADEON_IGP was
poor naming since it is one of a number of IGP host controllers. I added in the
PCI_DEVICE_ID_ATI_RS200M for the Sony laptops and added checking for into the
agpgart_be.c file. I am curious if people are comfortable with the PCI ID and
naming scheme. I apologize for posting to the list, as I could not figure out
how to post using Bugzilla for DRI development.

-Steve

http://bugs.xfree86.org/show_bug.cgi?id=314


bero@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bero@...




-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From alan@...  2003-29-07 18:45 -------
Given the 2.4 code, which is now on my todo list the 2.5 code shouldn't be hard.
Might be worth asking Dave Jones


-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-29-07 18:55 -------
Alan, please hold off releasing this in any kernels until everything has been
properly integrated in the DRI tree.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From j.w.bijlsma@...  2003-29-07 19:59 -------
I already ported the agpgart driver to 2.5.73. It seems to work. I can post it if it 
might be helpful, probably it builds perfectly on 2.6.0-pre2 as well (haven't tested 
though). 
 
	Wouter 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From matthieu.bonetti@...  2003-30-07 10:35 -------
Neither the patch for the 2.4.18 kernel or the patch for the 2.4.22-pre8 are
working on my box. I didn't forget to select CONFIG_AGP_ATI and I am loading the
drm module from XFree86.
Here is what I have at boot time:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 380M
agpgart: Unsupported ATI chipset (device id: cbb2), you might want to try agp_tr
y_unsupported=1.
agpgart: no supported devices found.

And here with agptool:
Found AGP host bridge.
1002:cbb2 :-ATI Technologies Inc: Unknown device cbb2
Host capabilities:
 Compliant with version 2.0 of the AGP standard.
 It is capable of doing x4 AGP, but is not initialised.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From alan@...  2003-30-07 10:42 -------
Lots of people want working AGP. I don't see why it needs to wait ?


-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From bero@...  2003-30-07 10:44 -------
Matthieu: Does it work for you if you do 
 
modprobe agpgart agp_try_unsupported=1 
 
? 
 
If so, all we need to do to get it working for you without trouble is adding 
your PCI ID (cbb2) to the hardware list in agpgart_be.c... 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From sjhill@...  2003-30-07 11:00 -------
Created an attachment (id=439)
 --> (http://bugs.xfree86.org/attachment.cgi?id=439&action=view)
IGP 345M Kernel Patch for 2.4.21

This patch detects the IGP 345M with PCI ID 0xcbb2 found on Sony VAIO laptops
thus far.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314


sjhill@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sjhill@...




------- Additional Comments From sjhill@...  2003-30-07 11:02 -------
Mattheiu,

I have attached a patch against 2.4.21 that will properly detect your
chipset. Sorry I did post this sooner.

-Steve

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-30-07 11:17 -------
Sorry Alan, I mean the DRM part.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From matthieu.bonetti@...  2003-30-07 12:44 -------
Steven, thank you for your patch, it works on my box. It's still a little slow
but at least I have some 3d now.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From al@...  2003-31-07 01:11 -------
I patched the kernel with the new DRM and IGP AGP stuff and am using XFree86
compiled right from CVS with the patch from here. I'm happy to say it *almost*
works for me. DRI Rendering is still not working. The following is reported:

(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:5:0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xd151e000
(II) RADEON(0): [drm] mapped SAREA 0xd151e000 to 0x40012000
(II) RADEON(0): [drm] framebuffer handle = 0xd8000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(WW) RADEON(0): [agp] AGP not available
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xd151e000 at 0x40012000
 <snip>
(II) RADEON(0): Direct rendering disabled

I'm assuming the modules are the correct ones. Any ideas? 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-31-07 09:02 -------
Make sure the agpgart module is loaded before the radeon DRM module.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From al@...  2003-31-07 12:19 -------
I'm not sure if this is any help, but now I get an infinite loop of:

(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020
(EE) RADEON(0): GetBuffer timed out, resetting engine...
(EE) RADEON(0): RADEONCPGetBuffer: CP reset -1020
(EE) RADEON(0): RADEONCPGetBuffer: CP start -1020

This is before anything appears on the screen. I am clueless as to what to do
about it. BTW, This is on a Radeon IGP 340M. The DRM kernel module, AGP module,
and XFree86 stuff all seem to be the right versions and load without any problems.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-01-08 06:25 -------
Are you sure you're using the patched DRM?

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From a.lahun@...  2003-02-08 03:38 -------
I have agp 320M with packard bell laptop. tried with 2.4.22-pre4
and 2.6.0test2. No problem with agp no  problem with drm kernel module everything
is found but when i start X with dri enabled it hung . linux is not crashed,
connecting with ssh showing that Xfree eat 100 % cpu. Actually after my
investigations itis radeon.o which is responsible for this. Please advice me
how can i test and help ?

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From a.lahun@...  2003-02-08 04:22 -------
Some traces from 2.6.0-test2. Starting from modprobe radeon.o
Aug  2 10:10:10 chinky kernel: [drm] Initialized radeon 1.8.0 20020828 on minor
Aug  2 10:10:32 chinky kernel:
Aug  2 10:10:32 chinky kernel:  radeon_do_init_cp
Aug  2 10:10:32 chinky kernel: [drm] Before CP Start 140
Aug  2 10:10:32 chinky kernel: Call Trace:
Aug  2 10:10:32 chinky kernel:  [<c010ab9a>] __report_bad_irq+0x2a/0x90
Aug  2 10:10:32 chinky kernel:  [<c010acbe>] note_interrupt+0x9e/0xa0
Aug  2 10:10:32 chinky kernel:  [<c010af20>] do_IRQ+0x120/0x130
Aug  2 10:10:32 chinky kernel:  [<c0109408>] common_interrupt+0x18/0x20
Aug  2 10:10:32 chinky kernel:  [<c0114ad4>] delay_tsc+0x14/0x20
Aug  2 10:10:32 chinky kernel:  [<c01b6842>] __delay+0x12/0x20
Aug  2 10:10:32 chinky kernel:  [<ce9b8559>] radeon_do_cp_start+0x129/0x1f0 [rad
Aug  2 10:10:32 chinky kernel:  [<ce9c0f7f>] radeon_mem_init_heap+0x8f/0x110 [ra
Aug  2 10:10:32 chinky kernel:  [<ce9b99d1>] radeon_cp_start+0xe1/0x100 [radeon]
Aug  2 10:10:32 chinky kernel:  [<ce9b4746>] radeon_ioctl+0xc6/0x140 [radeon]
Aug  2 10:10:32 chinky kernel:  [<c0163b23>] sys_ioctl+0xf3/0x290
Aug  2 10:10:32 Aug  2 10:10:32 chinky kernel:
Aug  2 10:10:32 chinky kernel: Call Trace:
Aug  2 10:10:32 chinky kernel:  [<c010ab9a>] __report_bad_irq+0x2a/0x90
Aug  2 10:10:32 chinky kernel:  [<c010acbe>] note_interrupt+0x9e/0xa0
Aug  2 10:10:32 chinky kernel:  [<c010af20>] do_IRQ+0x120/0x130
Aug  2 10:10:32 chinky kernel:  [<c0109408>] common_interrupt+0x18/0x20
Aug  2 10:10:32 chinky kernel:  [<c0114ad4>] delay_tsc+0x14/0x20
Aug  2 10:10:32 chinky kernel:  [<c01b6842>] __delay+0x12/0x20
Aug  2 10:10:32 chinky kernel:  [<ce9b8565>] radeon_do_cp_start+0x135/0x1f0 [rad
Aug  2 10:10:32 chinky kernel:  [<ce9c0f7f>] radeon_mem_init_heap+0x8f/0x110 [ra
Aug  2 10:10:32 chinky kernel:  [<ce9b99d1>] radeon_cp_start+0xe1/0x100 [radeon]
Aug  2 10:10:32 chinky kernel:  [<ce9b4746>] radeon_ioctl+0xc6/0x140 [radeon]
Aug  2 10:10:32 chinky kernel:  [<c0163b23>] sys_ioctl+0xf3/0x290
Aug  2 10:10:32 chinky kernel:  [<c010929b>] syscall_call+0x7/0xb
Aug  2 10:10:32 chinky kernel:
Aug  2 10:10:32 chinky kernel: Call Trace:
Aug  2 10:10:32 chinky kernel:  [<c010ab9a>] __report_bad_irq+0x2a/0x90
Aug  2 10:10:32 chinky kernel:  [<c010acbe>] note_interrupt+0x9e/0xa0
Aug  2 10:10:32 chinky kernel:  [<c010af20>] do_IRQ+0x120/0x130
Aug  2 10:10:32 chinky kernel:  [<c0109408>] common_interrupt+0x18/0x20
Aug  2 10:10:32 chinky kernel:  [<c0114ad4>] delay_tsc+0x14/0x20
Aug  2 10:10:32 chinky kernel:  [<c01b6842>] __delay+0x12/0x20
Aug  2 10:10:32 chinky kernel:  [<ce9b857d>] radeon_do_cp_start+0x14d/0x1f0 [rad
Aug  2 10:10:32 chinky kernel:  [<ce9c0f7f>] radeon_mem_init_heap+0x8f/0x110 [ra
Aug  2 10:10:32 chinky kernel:  [<ce9b99d1>] radeon_cp_start+0xe1/0x100 [radeon]
Aug  2 10:10:32 chinky kernel:  [<ce9b4746>] radeon_ioctl+0xc6/0x140 [radeon]
Aug  2 10:10:32 chinky kernel:  [<c0163b23>] sys_ioctl+0xf3/0x290
Aug  2 10:10:32 chinky kernel:  [<c010929b>] syscall_call+0x7/0xb
Aug  2 10:10:32 chinky kernel:
Aug  2 10:10:32 chinky kernel: [drm] After CP Start 80010140

and so on . 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From a.lahun@...  2003-02-08 08:22 -------
sorry problem fixed

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314


sjhill@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|sjhill@...   |




-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From psycho_dad1@...  2003-04-08 09:08 -------
I have exactly the same problem as described in comment #61. I have the Amilo A
with the IGP 320M and SuSE 8.2 and use the patched drm kernel module. The reason
is the radeon.o module. I tried with 2.4.20 vanilla, 2.4.21 vanilla, 2.4.20SuSE
and 2.4.21SuSE. Has anybody an idea what to do? (andrei, you posted that you
fixed the problem) 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From j.w.bijlsma@...  2003-04-08 19:48 -------
Created an attachment (id=458)
 --> (http://bugs.xfree86.org/attachment.cgi?id=458&action=view)
AGPGART driver for 2.5.x

Here's Hui Yu's AGP driver ported to 2.5.x (A little late but I more or less
forgot about them because I was too busy with other things). Haven't tested it
with 2.6 yet, but It 'll probably work just fine. 

It is not a patch but the source + a really simple Makefile, since I haven't
bothered to figure out how to make a patch out of it (shame on me ;-). Anyways,
the advantage is that it should load on all newer 2.5 and 26 kernels. You need
the sources in /usr/src/linux-2.x.x

I tested it with the agp tools and it seems to work just fine, but as far as 3D
goes it is useless until the DRI/DRM stuff is done.

	Wouter Bijlsma

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From a.lahun@...  2003-05-08 14:51 -------
About 2.6 and ATI IGP
I have 2.6.0-test2 with working AGP and DRI
 i have 480 fps and play Warcraft3. Sorry i donot understand why 
 dri should not work with 2.5 it took 2 hours to port AGP driver
 and 20 minutes for radeon kernel module
 if somebody interested in this i can post patches.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From roguestar191@...  2003-05-08 18:09 -------
yes, please post the 2.6.0-test2 patch, I'd love to get DRI working, :)

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From a.lahun@...  2003-05-08 18:13 -------
Created an attachment (id=466)
 --> (http://bugs.xfree86.org/attachment.cgi?id=466&action=view)
ATI IGP patch for 2.6.0test2


-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314


a.lahun@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
    Attachment #466|ATI IGP patch for 2.6.0test2|agpgart ATI IGP patch for
        description|                            |2.6.0test2




-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From a.lahun@...  2003-05-08 18:15 -------
Created an attachment (id=467)
 --> (http://bugs.xfree86.org/attachment.cgi?id=467&action=view)
radeon kernel dri module patch for 2.6.0test2


-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From matthieu.bonetti@...  2003-06-08 05:58 -------
Created an attachment (id=468)
 --> (http://bugs.xfree86.org/attachment.cgi?id=468&action=view)
Patch for the 2.6.0-test2 kernel which support	ATI IGP 345M

Works fine on my box.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From roguestar191@...  2003-06-08 21:16 -------
problems compiling the patch for 2.6.0-test2 kernel

  CC      drivers/char/agp/ali-agp.o
  CC      drivers/char/agp/ati-agp.o
drivers/char/agp/ati-agp.c: In function `ati_create_page_map':
drivers/char/agp/ati-agp.c:58: warning: implicit declaration of function
`change_page_attr'
drivers/char/agp/ati-agp.c:258:17: warning: extra tokens at end of #undef directive
drivers/char/agp/ati-agp.c: In function `agp_ati_probe':
drivers/char/agp/ati-agp.c:460: warning: unused variable `hidden_1621_id'
  CC      drivers/char/agp/via-agp.o
  LD      drivers/char/agp/built-in.o
drivers/char/agp/ati-agp.o(.init.data+0x20): multiple definition of
`ali_agp_device_ids'
drivers/char/agp/ali-agp.o(.init.data+0x20): first defined here
ld: Warning: size of symbol `ali_agp_device_ids' changed from 160 to 128 in
drivers/char/agp/ati-agp.o
make[3]: *** [drivers/char/agp/built-in.o] Error 1
make[2]: *** [drivers/char/agp] Error 2
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2


Any help would be greatly appreciated

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From roguestar191@...  2003-07-08 00:47 -------
The problem was from me adding in ALI AGP support on accident as well as the
ATI. But now I have a new problem, every time I try to start the X server with
DRI enabled(I've used versions 4.3.99.8 as well as .10, with the same results) I
get something like this (my logs have been erased since I've booted twice
without DRI enabled)this

(EE) Radeon(00): RADEONCPGetBuffer: timed out -1007
(EE) Radeon(00): RADEONCPGetBuffer: reset cp -1007

Over and over again, until I force my computer to shut down. I had over 30000
lines of that.
I'm using kernel 2.6.0-test2 with XFre86 4.3.99.8 on my HP Pavilion ZE4145 with
the ATI IGP320
I've patched the kernel with the agpgart patch. I've also patched Xfree86 with
both the 2.6.0-test2 kernel patch and the ATI IGP chipset DRI support.
rebuilt the whole package and installed it.
When the kernel boots I get this happy message, :)

Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected Ati IGP320/M chipset
agpgart: Maximum main memory to use for agp memory: 379M
agpgart: AGP aperture is 64M @ 0xd4000000
[drm] Initialized radeon 1.9.0 20020828 on minor 0
Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing disabled


I'll restart the X server with DRI enabled so I can show the exact error message.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-07-08 04:50 -------
You aren't using the patched DRM. 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From fredi@...  2003-07-08 05:00 -------
Matthew, 
Give a try to alan's kernel as he included the dri and agp patches looking at 
the diff. The version to try is 2.4.22-pre10-ac1. 
 
Michel, 
at the said kernel patch I saw some ioctl changes in the dri part, seems there 
is the ioctl that returns the fb_offset. So does this mean that now there are 
no compactibility problems? 
 
Alan, thank you for including this! 

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From roguestar191@...  2003-07-08 05:11 -------
For those of you who can't seem to get DRI working, follow these steps, I laid
it out step by step. The only part I didn't cover was patching the kernel, or
patching and building the Xfree86 distrobution. But this is a MUST read for
anyone who can't figure it out.

Okay, ignore my last 2 posts, I finally figured out what was going on. I thought
I had the custom built module installed, but I didn't. Here's what to do for all
of those who were as confused as me. 

Include the ATI support in the kernel, but make the radeon a MODULE, do NOT
include it in the kernel itself.
Build the kernel and install it. Make the modules, and do make modules_install.
Switch to your xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel directory
Do make -f Makefile.linux LINUXDIR=/usr/src/linux
{That's assuming /usr/src/linux is the directory for your kernel source you have
already patched and built.}
Now I don't know about other kernels, but kernel 2.6.0-test2's modules have a
.ko extension.
Don't change directories, but do ls /lib/modules/(current kernel
version)/kernel/drivers/char/drm
there should be radeon.o or radeon.ko in there I'm not sure.
If it's radeon.o replace it with the radeon.o from the
xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel directory
if it's radeon.ko replace that with the radeon.ko respectivly.
now make sure the radeon module isn't already loaded (modprobe --remove radeon)
and load the new radeon modules (modprobe radeon)

It should all work, and you should now have DRI hopefully. For all of you who
had the 
(EE) RADEON(0): GetBuffer timed out, resetting engine...
(EE) RADEON(0): RADEONCPGetBuffer: CP reset -1007
(EE) RADEON(0): RADEONCPGetBuffer: CP start -1007
(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1007
(EE) RADEON(0): GetBuffer timed out, resetting engine...
errors, this will fix it. (this was because you were using the wrong radeon module.)
For all of you who were getting the 
(II) RADEON(0): Direct rendering disabled
error, this will fix it (that was because you had the radeon dri module built
into the kernel itself)

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From michel@...  2003-07-08 05:18 -------
As was stated many times already, the DRM and X server parts can't go in
anywhere in this form. Alan, if you really included the DRM part in your kernel,
please pull it again. This needs to be properly integrated in the DRI tree
first. Just read this bug for an idea of the compatibility headaches that will
arise otherwise. :)

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From roguestar191@...  2003-08-08 20:43 -------
after a while of spiffie 3d support i get this:

Message from syslogd@... at Fri Aug  8 18:39:02 2003 ...
localhost kernel: Disabling IRQ #10

And no more 3D support. In glxinfo it reports DRI is still enabled, but glxgears
drops down to 180 fps, and scaling for videos .. nope.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314


hy0@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #415 is|0                           |1
           obsolete|                            |




-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314


hy0@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #416 is|0                           |1
           obsolete|                            |




-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-08-08 23:05 -------
Here is the latest version on my system.
Changes in this version:
1. RS100/200/250 Q3A texture problem is worked around.
2. RS100/200/250 FW is okay and can be enabled.
3. RS300 (IGP9100) support is complete. I know probably nobody has this chipset
at present, but it's going to be much much more popular than all existing IGP
chipsets together. Everything is working fine on my system, including AGPv3 4x 
and 8x modes, and external graphics.
4. Improved backward compatibility. I haven't put in new ioctl and version bump,
just changed the way it's coded. For regular radeon cards, mixing patched 
version and non-patched version of 2D, 3D, and DRM shouldn't cause any problem. 
For IGP chips, mixing patched version and non-patched version of 2D and DRM will
cause DRI be disabled but normal 2D should still work. However if you use 
non-patched 3D client with patched 2D and DRM on a IGP chip, it will cause 
lockup. There is no good way to prevent this.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-08-08 23:26 -------
Created an attachment (id=478)
 --> (http://bugs.xfree86.org/attachment.cgi?id=478&action=view)
Radeon IGP DRI patch for XFree CVS 4.3.99.9

This is the patch for current XFree86 CVS code (4.3.99.9). I know it probably 
more appropriate to have a patch for DRI project code. But the 2D code in DRI 
tree is too different (it's still 4.30 based), I just don't have time to do it.

This patch includes the kernel DRM driver patch which should be used for 2.4.xx

kernel.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-08-08 23:31 -------
Created an attachment (id=480)
 --> (http://bugs.xfree86.org/attachment.cgi?id=480&action=view)
Linux kernel 2.4.21 agpgart patch for Radeon IGP chipsets

Patch for 2.4.21 AGPGART driver. Please use DRM driver in XFree86 patch.

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From hy0@...  2003-08-08 23:35 -------
Created an attachment (id=483)
 --> (http://bugs.xfree86.org/attachment.cgi?id=483&action=view)
Linux kernel 2.5.75 agpgart and drm driver patch for Radeon IGP chipsets

This patch includes changes for both agpgart driver and radeon DRM driver.
It should also work on linux-2.6.0-test2

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.xfree86.org/show_bug.cgi?id=314





------- Additional Comments From roguestar191@...  2003-09-08 17:09 -------
Hui, with the new patch for 2.6.75 (agpgart and drm) do you still have to use 
the DRI module built from the XFree86 Source? I tried using the module from the 
kernel and got the same errors I was getting before:


(EE) RADEON(0): GetBuffer timed out, resetting engine...
(EE) RADEON(0): RADEONCPGetBuffer: CP reset -1007
(EE) RADEON(0): RADEONCPGetBuffer: CP start -1007
(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1007


(That is when I use the new kernel module)
and when I use the other module built from the XFree86 source It works fine 
(until I get the Disabling IRQ 10 error message, then it slows to 190 fps in 
glxgears, but glxinfo shows that DRI is still on :-/)

I'm using an IGP320m (u1) with a 2.6.0-test2 kernel, XFree86 4.3.99.08.

Oh yes, and I tried to patch 4.3.99.09 with your new patch, it gave me 30 
rejected hunks in radeon.c.. :-/

-- 
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

hy0@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #478 is|0                           |1
           obsolete|                            |




------- Additional Comments From hy0@...  2003-12-08 00:11 -------
Created an attachment (id=495)
 --> (http://bugs.xfree86.org/attachment.cgi?id=495&action=view)
Radeon IGP DRI patch for XFree CVS 4.3.99.9

Oops, I probably messed up one file during making 4.3.99.9 patch. Thanks for 
catching this and please try this one.
The old patches (posted on July 19 and all other based on them) have some 
compatiblity issue. You shouldn't mix them with any other versions, including 
the drivers built with the new patches.
With the new patches, if you have kernel 2.5.75 or 2.6.0-test2, you'll need to 

use the DRM driver in the kernel (DRM driver in current XFree86 CVS is not
2.6.0 ready). If you have kernel 2.4.x, you'll need to use the DRM driver 
inside XFree86 CVS tree (because the 3D client in the XFree86 CVS code requires

higher version DRM than some 2.4.x linux kernels provided).
 
 
--  
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From espinosa@...  2003-13-08 14:41 -------
I successfully compiled kernel 2.6.0.test3 with Huy latest patch DRM+AGP 
(id=483) I successfully compiled XFree4.3.99.9 with IGP DRI patch for 4.3.99.9. 
(id=495) As recommended by Huy, in comment #83, I DID NOT overwrite kernel 
module radeon.ko, I even DID NOT compile this module in X source tree.

AGP is compiled into kernel and it is successfully initialized.
Radeon DRM driver is made as a separate module radeon.ko
Is it OK?

X works fine for me, AGP works, but DRI is disabled because of
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)

I did not include devfs into kernel at all. Does it matter?
I have directory /dev/dri but it is empty.
Should I made it manually, as I did for ALSA sound driver via MAKE.sound 
scritpt in kernel sources?
What are the right paramaters for 'mknod'?

Thanks for any help.


--- More info --------------------------------------------------
XFree86.log:
..
(==) RADEON(0): Write-combining range (0xf8000000,0x2000000)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 1
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 2
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 3
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 4
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 5
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 6
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 7
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 8
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 9
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 10
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 11
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 12
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 13
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 14
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
(II) RADEON(0): [drm] drmOpen failed
(EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.
..

dmesg:
..
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected ATI IGP320/M chipset
agpgart: Maximum main memory to use for agp memory: 175M
agpgart: AGP aperture is 64M @ 0xf4000000
..

Linux 2.6.0-test3 i686 athlon i386 GNU/Linux
laptop Fujitsu Siemens, Amilo D

00:01.0 PCI bridge: ATI Technologies Inc U1/A3 AGP Bridge [IGP 320M] (rev 01) 
(prog-if 00 [Normal decode])
        Flags: bus master, 66Mhz, medium devsel, latency 99
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=68
        I/O behind bridge: 0000b000-0000bfff
        Memory behind bridge: f0500000-f05fffff
        Prefetchable memory behind bridge: f8000000-fbffffff

01:05.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility U1 
(prog-if 00 [VGA])
        Subsystem: Unknown device 1734:100a
        Flags: bus master, stepping, fast Back2Back, 66Mhz, medium devsel, 
latency 66, IRQ 5
        Memory at f8000000 (32-bit, prefetchable) [size=64M]
        I/O ports at b000 [size=256]
        Memory at f0500000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at <unassigned> [disabled] [size=128K]
        Capabilities: [58] AGP version 2.0
        Capabilities: [50] Power Management version 2


 
 
--  
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From a.lahun@...  2003-13-08 15:47 -------
For people having problem with " Disabling IRQ xx error message"
put parameter "noirqdebug" in lilo.conf

With latest patch iteration i have a problem now.
If "pageflip" is on i see only black picture with glxgears.
if Off everything seem to ok but fps is not 480 but 420 . 
 
--  
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From a.lahun@...  2003-13-08 18:40 -------
Hmm something wrong with textures with Warcraft3 with this new patch.
So i will go back to previous  patch.
Did anybody tried -mm kernels? Why i always get 200 fps in glxgears if for
normal 2,6.0 test i get 400+ ? something strange here 
 
--  
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

hy0@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #495 is|0                           |1
           obsolete|                            |




------- Additional Comments From hy0@...  2003-14-08 00:27 -------
Created an attachment (id=502)
 --> (http://bugs.xfree86.org/attachment.cgi?id=502&action=view)
radeon IGP DRI patch for XFree CVS 4.3.99.9

This one fixed pageflip problem as Andrei pointed out (forgot patch one file). 

I haven't tested with Warcraft3, not sure about the texture problem there.
In the new patch I disabled multitexture extension because it causes texture 
problem with q3a. Andrei, maybe you can try to re-enable it (in 
radeon_context.c) and see if it's the cause with Warcraft3 problem.
Jan Uhlir, you can try to insert radeon.ko manually or compile it into the 
kernel. 
 
--  
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From a.lahun@...  2003-14-08 06:00 -------
yes Hui with latest patch page flip works again.
And about texture problems , when i enable that "GL_ARB_Multitexture" extension
problem with Warcraft disappear. Actually what i mean when u start Warcraft on
first screen
there several buttons, if i disable extension buttons just disappear. 
 
--  
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From edc17@...  2003-14-08 07:43 -------
Hey all, it's great to hear that someone has finally made some progress with
this!  I bought my laptop a couple of months ago, and have had to put up with
having windows on a partition! - Maybe I'll finally be rid of the curse! :)

Ok, my problem is that I can't seem to compile the kernel to include the agp
support (unless I have but just don't know it). I successfully patched the
kernel and saw the ati agp support feature which I turned on, but after
compiling and installing the kernel I didn't notice any changes from the
previous kernel I had installed. I've checked through the startup logs and
haven't seen and of the things like: 

Jul 22 02:35:51 matrix kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann 
Jul 22 02:35:51 matrix kernel: agpgart: Maximum main memory to use for agp 
memory: 409M 
Jul 22 02:35:51 matrix kernel: agpgart: Detected ATI IGP330/340/345/350/M 
chipset 
Jul 22 02:35:51 matrix kernel: agpgart: AGP aperture is 64M @ 0xf4000000 
Jul 22 02:35:51 matrix kernel: [drm] AGP 0.99 on Unknown @ 0xf4000000 64MB 
Jul 22 02:35:51 matrix kernel: [drm] Initialized radeon 1.1.1 20010405 on 
minor 0 

as previously mentioned. Or does this only appear after the xfree86 section of
the install has been completed??

I'm using the vanilla 2.4.21 kernel, and can't figure it out!

Thanks everyone for the time and effort you've all put in, I can't want to get
this going (and for full support to be accomplished). 
 
--  
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From michel@...  2003-14-08 10:54 -------
Hui, I like the current patch much better, it addresses most of the
compatibility issues indeed. The approach we've been discussing should also
allow old 3D drivers  to work with the new DRM and 2D driver though. And I think
this should definitely go into the DRI tree first.

Jan, it looks like the X server isn't able to load the radeon kernel module for
you. Do you have the module-init-tools required for using modules with 2.6
kernels installed? What happens when you try to run modprobe radeon manually?

Erlend, you need to use the patched radeon kernel module built from the XFree86
tree. 
 
--  
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From edc17@...  2003-14-08 22:30 -------
Well, I got a little further, but still no joy... After compiling the entire
XFree86 tree, installing it, and then copying the radeon.o file from the
programs/Xsever/..... I receive the following in my XFree86 log file.

My X still loads up fine though (but without 3D rendering enabled (obviously, or
I probably wouldn't be writing this message!!!).

drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmGetBusid returned ''
(II) RADEON(0): [drm] loaded kernel module for "radeon" driver
(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:5:0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xcc8d2000
(II) RADEON(0): [drm] mapped SAREA 0xcc8d2000 to 0x40017000
(II) RADEON(0): [drm] framebuffer handle = 0xe0000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(WW) RADEON(0): [agp] AGP not available
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xcc8d2000 at 0x40017000
(II) RADEON(0): Memory manager initialized to (0,0) (1024,8191)
(II) RADEON(0): Reserved area from (0,768) to (1024,770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7421
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)

Additionally, I'm not sure if this is relavent, but I found this in my logs also
 (might just be a side effect of the first problem??)

(II) RADEON(0): I2C bus "DDC" initialized.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 2, Detected Type: 0
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 4, Detected Type: 0
(II) RADEON(0): Non-DDC laptop panel detected
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 3, Detected Type: 0
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 4, Detected Type: 0
(II) RADEON(0): Total number of valid DDC mode(s) found: 0    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From psycho_dad1@...  2003-15-08 04:01 -------
Hi, I think there is a problem with the usb-ohci module in 2.4x - kernels. 
With the module loaded and dri enabled I only get a black screen after typing 
startx. Without the module and dri enabled the windowmanager starts. This 
problem is related to the radeon.o module, because the system only hardlocks 
with this module loaded. I cant disable USB-Legacy Support because the bios of 
the Amilo A is very poor even in the latest version. Has somebody an idea or 
can somebody write a fix for the radeon.o module or the usb-ohci module? I 
have the Radeon IGP 320M and SuSE 8.2 
 
Thomas 
 
       
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From edc17@...  2003-15-08 07:00 -------
My expertise in linux is not yet that great (I'm learning quick, and loving
every minute of it though!). So could you please instruct me as to how I can
ensure one module is loaded before another?? Thanks a million!    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From michel@...  2003-15-08 06:54 -------
Erlend, you need to make sure that the (correct) agpgart module is loaded before
the radeon kernel module. The DDC snippets are unrelated and simply mean that
the driver doesn't detect any displays via DDC.

Thomas, do usb-ohci and the radeon DRM use the same IRQ?    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From michel@...  2003-15-08 07:28 -------
Apart from loading the agpgart module manually first, you can try this in
/etc/modules.conf:

below   radeon  agpgart    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From edc17@...  2003-15-08 07:57 -------
One additional thing I noticed is that this message appears in glxinfo, and when
loading opengl applications: disabling TCL support.    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From edc17@...  2003-15-08 07:41 -------
Hmmmmm, I tried this:

/sbin/modprobe --remove radeon
/sbin/modprobe agpgart
/sbin/modprobe radeon

Then killing X.

When things came back up I ran glxinfo and found that direct rendering was
apparently enabled! The only problem being that as soon as I run anything with
3D acceleration the whole system freezes. Even tried pinging from remove
computer, but with no response.

Anyone know what would cause the system to freeze up like this?? Am I doing
something else wrong now???    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From michel@...  2003-15-08 09:51 -------
Are you using the patched versions of all of the 2D driver (radeon_drv.o), the
DRM (radeon.o kernel module) and the 3D driver?

The message about disabling TCL support is normal if your graphics chip doesn't
have a TCL unit.    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From psycho_dad1@...  2003-15-08 10:50 -------
Michel, thank you for your comment. It could be possible that there is a irq 
conflict. Then i will play with the irq-settings in /etc/modules.conf. But I 
would really like to know what that has got to do with dri.      
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From espinosa@...  2003-15-08 13:55 -------
Is it possible to get the driver working with kernel 2.5/2.6 ???
I used Hui patch with X 4.3.99.9 and kernel 2.6.0.test3 (drm+agp patched) with
AGP compiled in and radeon as a module.
If I 'modprobe radeon', after 'startx' freezes with blank screen and system is
not responding anyway.
After booting with 'nousb nofirewire acpi=off nomce' the result is same.
Using X 4.3.99.10 (patching went with no problem) - the same result.
If I startx with radeon.ko not loaded, X runs OK, but no DRI and in log is 
error as mentioned in comment #84

If I try compile DRM driver in X (4.3.99.10) source, i get error:
make -C /lib/modules/2.6.0-test3/build  SUBDIRS=`pwd` DRMSRCDIR=`pwd` modules
make[1]: Entering directory `/usr/src/linux-2.6.0-test3'
make[2]: `arch/i386/kernel/asm-offsets.s' is up to date.
*** Warning: Overriding SUBDIRS on the command line can cause
***          inconsistencies
/usr/src/XFree86-4.3.99b/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/Makefile.kernel:50:
/usr/src/linux-2.6.0-test3/Rules.make: No such file or directory
make[2]: *** No rule to make target `/usr/src/linux-2.6.0-test3/Rules.make'.  Stop.
make[1]: ***
[/usr/src/XFree86-4.3.99b/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel]
Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.0-test3'
make: *** [modules] Error 2

Yes, as was stated, the X source is not kernel 2.6 ready. Is there another way
to build it for 2.6?

Re Michel Dänzer: Yes, you was right, radeon.ko was not loaded. I have right
module-init-tools,
but i have some problems with module autoloading, as I search through linux.kernel
newsgroups, I'm not alone (RedHat9 is somewhat blamed).

BTW: Amilo A laptop really has problems with USB. RH9 was not even possible to
install without 'nousb'. I encounter problems with both 2.4 and 2.6 kernels. It
also cause mouse or keyboard freezing after startup or hanging just before
power-off. With 2.6 it is MUCH better, it cause only PS mouse freezing, until I
manually load module 'ohci_hcd' (= ohci_usb in 2.4) then prints message:
"ACPI: No IRQ known for interrupt pin A of device 0000:00:02.0" and PS
mouse/touchpad is accesible after reloading module 'psmouse'. If I boot with
'nousb', there are no problems with it.

    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From edc17@...  2003-15-08 10:02 -------
Wow, I've actually got some 3D acceleration now. I disabled page-flipping and
the freezing ceased.

I do still on occasion get a lockup that requires me to ssh in and kill the
offending application. I'm only had this while resizing the the application
window though, and it only happens about 1 in 4 times (kind of annoying though).

The only graphical problems I've noticed so far was a little bit of missing
textures in tux-racer (tux's feet and face were white).

I think I downloaded the updated patch that didn't have page-flipping enabled,
so maybe this explains the freezing? I'll try that out soon.

Anyone else experience any freezing like I've described???


Just got your post then... I didn't explicitely copy them over if that's what
you mean? Do I need to copy over more than just the radeon.o module?? I
installed the patched XFree86, as well as copying the radeon.o module over, but
nothing else.    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From martin.wiesner@...  2003-15-08 16:19 -------
Hi folks,

thanks again for the great progress that has been made with this problem. We are
on a good way. I'd like to ask everybody to put this "BUG" higher on the task
list. If more people wrote there experiences and problems or whatever could
help, progress could be even faster. 

As Thomas, I myself own an FSC Amilo A 7600. He has come closer to the lockups
reasons than me. We checked nearly everything, but my system hangs (HARDLOCKS)
when starting X. Everytime, with or without USB/ETH0... Don't know why. Perhaps
some of the core developers/experts could take a closer look at this notebook.
Thomas and me could provide some output of hardware things and so on... when needed.

Please feel free to mail one of us. So far, since now I never got this message:
DRI ENABLED :-(

Thanks for your efforts,
Martin    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From clee@...  2003-15-08 17:30 -------
Jan: In comment #101, your problems seem to be (1) You didn't do a 'make (menu|x|g|old)
config in your kernel directory, or your kernel source is somehow incomplete, and (2) You 
should probably disable "Legacy USB support" in your bios to make things work better. The 
"Legacy USB support" option caused problems for me as well on my laptop (an HP 
ze4420us). 
 
However, I have successfully gotten DRI acceleration working on 2.6.0-test3 with 
attachment #466, attachment #467, and attachment #502. I applied #502 to the 
XFree-4.3.99.9 source tree, it compiled cleanly, and glxinfo reports that direct rendering is 
enabled.     
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From clee@...  2003-15-08 17:37 -------
Ok, as an addendum to my own comment... 
 
Direct rendering fails after a little while, with the "Disabling IRQ 10" message that everyone 
else has described here. 
 
Messages from dmesg show that apparently, the radeon module is not behaving properly. 
 
handlers: 
[<dd98e3b0>] (radeon_dma_service+0xa0 [radeon]) 
irq event 10: bogus return value e199b000 
Call trace: 
 [<c010cc8b>] __report_bad_irq+0x2b/0x90 
 [<c010cdb2>] note_interrupt+0x92/0xa0 
 [<c010d033>] do_IRQ+0x143/0x160 
 [<c010b4b8>] common_interrupt+0x18/0x20 
 
There's more, if anybody's interested. Email me at clee@....     
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From edc17@...  2003-15-08 21:33 -------
The latest news from me is that pageflipping now doesn't freeze the system as
before (using the second patch with pageflipping fixed). However, everything on
X except the mouse freezes at some point after resizing an opengl window, it
seems to be more likely to freeze when the video card is drawing more stuff. The
only way to regain control of the system again is to ssh in and kill the opengl
program, or to restart with the power button.

I'll have a play around and see what else I can turn up on the problem. Anyone
else got any ideas??    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From edc17@...  2003-16-08 22:21 -------
Hmmmmm, another problem that's bugging me, maybe you guys can help me. Before
finding this page I was running the original version of XFree86 that came with
redhat 9 (might have updated with apt-get since, not sure), but then I
downloaded the latest cvs snapshots in order to use these drivers. I've noticed
an additional problem on top of the fact that X freezes occasionally when under
a heavy load (normally only with opengl, but I don't think it's exclusive to
it), when I try alt-tabing, or ctl-alt-right, the box with the window list comes
up, but doesn't go away until I press another button, ctl-alt-right does move to
another workspace, but alt-tabing doesn't change focus (shows the outline, but
doesn't after pressing a key to remove the box it doesn't move it forward).

I don't think this is related to the new drivers, but I could be wrong.    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From edc17@...  2003-16-08 23:19 -------
I tried replacing the file /usr/X11R6/lib/modules/drivers/radeon_drv.o with the
radeon_drv.o modules created when calling "make -f Makefile.linux
LINUXDIR=/usr/src/linux" in addition to replacing the radeon.o module. But then
I get the following error when trying to load X:

(II) LoadModule: "radeon"
(II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o
(EE) LoadModule: Module radeon does not have a radeonModuleData data object.
(II) UnloadModule: "radeon"
(II) Unloading /usr/X11R6/lib/modules/drivers/radeon_drv.o
(EE) Failed to load module "radeon" (invalid module, 0)

Am I meant to replace the radeon_drv.o module as I've done, or do I use the one
that installing XFree86 copied over??

Thanks, I'll wait for some replies before posting again, as I think I've
overdone it a little :P    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From michel@...  2003-17-08 08:35 -------
Erlend:

The lockups on moving 3D windows may be 3D driver bugs (BTW, I forgot to mention
in an earlier comment that the 3D driver is radeon_dri.so or r200_dri.so), the
drivers in DRI CVS may work better.

The keyboard problem is definitely unrelated to video drivers.

That radeon_drv.o is a part of the radeon.o kernel module and has nothing to do
with the 2D driver, sorry for the confusion.    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to the URL 
shown below and enter your comments there.   
  
http://bugs.xfree86.org/show_bug.cgi?id=314    
    




------- Additional Comments From edc17@...  2003-18-08 07:32 -------
When you say the drivers from DRI CVS, I assume you're talking about the ones in
xc/exports/lib/modules/dri/radeon_dri.so, and not the ones in
xc/lib/GL/mesa/src/drv/radeon/radeon_dri.so, and if so, what's the difference???

I think the freezing problem that caused everything to freeze only happens with
glut programs (and I think it happened with a screensaver or something a while
ago also). Can anyone else test this out and see if it's just me or not?? The
problem only ever happens when my application is drawing quite a few triangles
to the screen, so you'll need to test it under a heavy load...

I still haven't figured out how to fix the alt-tabbing problem though! Anyone
got any ideas? Could it be because I need to update any of the other things
(like gnome for example)? The problem is the same in both gnome and KDE too. Are
there any other components that need updating??? Thanks!    
    
--     
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email    
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From michel@...  2003-18-08 09:10 -------
They're the same, xc/exports/lib/modules/dri/radeon_dri.so is a symlink to
xc/lib/GL/mesa/src/drv/radeon/radeon_dri.so . Don't forget to apply the patch
for building though. ;)

You're not alone with window movement causing lockups. AFAIK it should be better
if not fixed in DRI CVS.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From edc17@...  2003-18-08 17:01 -------
Quote: AFAIK it should be better if not fixed in DRI CVS

Are you saying that the problem SHOULD be fixed, or IS fixed? If the second is
true, then isn't the file I'm using the one in the DRI CVS??? Or is there CVS
project with more up-to-date source code???     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From michel@...  2003-18-08 17:21 -------
You're using XFree86 CVS, DRI CVS is http://sourceforge.net/cvs/?group_id=387 .     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From edc17@...  2003-19-08 06:40 -------
Do I need to apply the same patch to the DRI CVS also??     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From michel@...  2003-19-08 07:11 -------
Yes.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From psycho_dad1@...  2003-19-08 14:03 -------
The good message: I have dri working on my Amilo A. Smoothly Tux slides down the
           hills in tuxracer...   
The bad message:  I have no no usb-mouse (usb-ohci.o), no sound (trident.o) and
no network (8139too alias eth0). All these modules got IRQ No.11 and lead to a
system crash when they are used. The radeon.o module that causes these crashs
has IRQ No.5. I tried to change IRQs (Compiling the kernel with
PCI Access_Mode=Direct and setting the option pci=nobios in the Bootprompt).
Then I tried to change the IRQs of the modules in /etc/modules.conf. But linux
did not care about and always uses the "IRQ router ALI". This is a piece of the
bootlog (dmesg):


<6>PCI: Using configuration type 1
<6>PCI: Probing PCI hardware
<4>PCI: ACPI tables contain no PCI IRQ routing entries
<4>PCI: Probing PCI hardware (bus 00)
<6>PCI: Using IRQ router ALI [10b9/1533] at 00:07.0

Has someone an idea how to outfox the IRQ router? Or another idea how to get
these modules working with dri enabled? 

Thomas Riedel     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From edc17@...  2003-19-08 23:41 -------
WOOT!!! Well, I patched the dri cvs (as opposed to the xfree86 dri cvs tree)
code this morning - took a couple of hours (and the odd typo that needed fixing
during compilation took another half hour or so), but now I've got 3D
acceleration with windows that don't lock up when I move/resize them anymore!!!

I might have made a few mistakes with the patching, but haven't noticed any
problems as of yet. There was one section that I didn't update because I
couldn't find any functions that fitted with it, I think it was in
radeon_context.c, and it was to do with the radeonInitExtensions function.
Anyone know what that section of code does, the comments say it's a work-around
for the IGP chip multi-texturing problem.

I still haven't figured out why alt-tabing and the like doesn't work properly
anymore, so I intend to reinstall redhat and get it working just right (I've
tried everything I can think of!! Including screwing other things up in the
process (hehe, have to manually start gnome and X now, and dont have anything in
my start menu!!)).     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From edc17@...  2003-19-08 16:01 -------
hmmmmmm.... So am I going to nee to apply the patch manually to the DRI CVS
tree??? If I try "patch -p0 <x4.3.99.9_radeon_igp_dri.diff" I get several failed
hunks. This was tried with the latest DRI CVS tree.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From thambj@...  2003-21-08 14:13 -------
FYI, alt-tabbing in GNOME/Metacity has not worked in CVS XFree86 since at least
the 4th CVS tarball (we are now at the 10th).  This glitch must have crept into
DRI CVS in some merge.  I put up a bug report on the bugzilla:
http://bugs.xfree86.org/show_bug.cgi?id=616     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From edc17@...  2003-21-08 18:53 -------
That's good to know - that it's not just me!

I have managed to get everything working now!! 3D acceleration with no freezing
up when moving/resizing windows, and alt-tab works fine now!

I did a fresh install of redhat 9 (what I had on before, but I couldn't figure
out the problem), I then installed the xfree86 cvs again and the problem came
straight back! Luckily I made a backup of the /usr/X11R6 folder this time, so I
could restore the original setup - which worked. Then I tried using only the
dri-cvs. Acceleration came, no more freezing, and alt-tab works fine!!!

So to conclude... If anyone else can't stand the alt-tab not working, or the
freezing of windows when moving/resizing an opengl window, then get yourself the
dri-cvs instead (note that you'll have to apply the patch manually, as it
doesn't apply cleanly - unless I missed something!).     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From edc17@...  2003-23-08 00:26 -------
I take it that the radeon IGP 320M doesn't have a TCL chip??     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From mika@...  2003-24-08 09:39 -------
I just don't get it, I have Amilo A 7600 and 
I've patched attachments 466, 467 and 502 successfully.
Compiled xfree cvs 4.3.99.9 and kernel 2.6.0-test3, loaded agpgart module before
radeon module. And still I get this:

glxinfo: 

name of display: :0.0
Xlib:  extension "XFree86-DRI" missing on display ":0.0".
display: :0  screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
GLX extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL vendor string: Mesa project: http://www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.3 Mesa 4.0.4
OpenGL extensions:
    GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp, 
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add, 
    GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3, 
    GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color, 
    GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add, 
    GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, 
    GL_EXT_texture_lod_bias
glu version: 1.3
glu extensions:
    GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

and:

(--) Chipset ATI Radeon IGP320M (U1) 4336 found
(WW) RADEON(0): Direct rendering not yet supported on IGP320/330/340/350, 7000,
9000 integrated chips <-- ???
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7413
(**) Option "dpms"
(**) RADEON(0): DPMS enabled
(II) RADEON(0): Direct rendering disabled
     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From mharris@...  2003-24-08 13:33 -------
Hint:

> Xlib:  extension "XFree86-DRI" missing on display ":0.0".
         ^^^^^^^^^^^^^^^^^^^^^^^

The *EXTENSION* is not configured to load.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From michel@...  2003-24-08 19:35 -------
> (--) Chipset ATI Radeon IGP320M (U1) 4336 found
> (WW) RADEON(0): Direct rendering not yet supported on IGP320/330/340/350, 7000,
9000 integrated chips <-- ???

Looks like you're not using the patched 2D driver, or you didn't patch it
correctly, or the patch still doesn't support your chip.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From mika@...  2003-24-08 22:29 -------
Yes, that was my own stupidity, I wanted to see which files that one patch
updates and used --dry-run, okay, you now know did I run it again without it :)

However, still direct rendering: No

(WW) RADEON(0): Mismatched FB location. Incorrect version of DRM kernel driver
is used.

And Thomas, did you find any way to fix that IRQ conflict problem?
And strange, this must have something to do with my new mouse problem, even that
synaptics driver isnt helping this time.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From michel@...  2003-25-08 09:47 -------
Same problem with the DRM (radeon kernel module)?     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From mika@...  2003-26-08 04:58 -------
No, everything successfully patched now.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From bugzilla@...  2003-26-08 14:38 -------
sonic kernel # make -f Makefile.linux
rm -f linux
ln -s . linux
+ mv -f Makefile Makefile._xx_
+ ln -s Makefile.linux Makefile
make -C /lib/modules/2.6.0-test4-mm1/build  SUBDIRS=`pwd` DRMSRCDIR=`pwd` 
modules
make[1]: Entering directory `/usr/src/linux-2.6.0-test4-mm1'
make[2]: `arch/i386/kernel/asm-offsets.s' is up to date.
*** Warning: Overriding SUBDIRS on the command line can cause
***          inconsistencies
/var/tmp/portage/xfree-4.3.99.9/work/xc/programs/Xserver/hw/xfree86/os-
support/linux/drm/kernel/Makefile.kernel:50: /usr/src/linux-2.6.0-test4-
mm1/Rules.make: No such file or directory
make[2]: *** No rule to make target `/usr/src/linux-2.6.0-test4-
mm1/Rules.make'.  Stop.
make[1]: *** [/var/tmp/portage/xfree-
4.3.99.9/work/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel] Error 
2
make[1]: Leaving directory `/usr/src/linux-2.6.0-test4-mm1'
make: *** [modules] Error 2

sonic kernel # pwd
/var/tmp/portage/xfree-4.3.99.9/work/xc/programs/Xserver/hw/xfree86/os-
support/linux/drm/kernel

sonic kernel # uname -a
Linux sonic 2.6.0-test4-mm1 #1 Tue Aug 26 09:35:03 PDT 2003 i686 Mobile Intel
(R) Celeron(R) CPU 1.60GHz GenuineIntel GNU/Linux

sonic kernel # dmesg | grep AGP
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
agpgart: AGP aperture is 64M @ 0xe4000000

     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From a.lahun@...  2003-26-08 15:02 -------
Kevin .
Please remember that you for 2.5/2.6 kernel
you should use radeon kernel drivers from kernel after patching it
with AGP/DRI patch. And you cannot use patched sources from X tree for 2.5
without patching it.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From a.lahun@...  2003-26-08 15:10 -------
Jist for information.
After moving to 2.6.0-test4 
fps in glxgears moved from 480 to 200
For me <export RADEON_NO_IRQS=1> fixed this problem.
Also i think with this parameter people will not lose IRQ with 2.6 kernel      
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From a.lahun@...  2003-26-08 15:08 -------
Created an attachment (id=541)
 --> (http://bugs.xfree86.org/attachment.cgi?id=541&action=view)
Patch for drm in xfree tree to work with 2.6.0+ kernels
     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From a.lahun@...  2003-26-08 15:04 -------
Created an attachment (id=540)
 --> (http://bugs.xfree86.org/attachment.cgi?id=540&action=view)
ATI/DRI patch for kernels 2.6.0-test4+
     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From bugzilla@...  2003-26-08 15:38 -------
So I should apply patch #540 to the kernel tree, compile it. Then apply patche 
#541 to xfree 4.3.99-9 (will it work for -10 also) and compile that too. Do I 
need any other patches?     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From a.lahun@...  2003-26-08 15:50 -------
No u will use #540 if u want to patch kernel
or #541 if u want to use radeon kernel driver from Xfree tree(if you do not want
to repatch every time you upgrade to new 2.6 kernel).
simply use #540 with your kernel tree and then choose ATI AGP and radeon drm
support .     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     

seemant@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |seemant@...


     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     

eich@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jfabra@...




------- Additional Comments From eich@...  2003-27-08 05:05 -------
*** Bug 630 has been marked as a duplicate of this bug. ***     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From psycho_dad1@...  2003-27-08 13:20 -------
I did not made progress with the hangings on Amilo A. But what is the effect of 
<export RADEON_NO_IRQS=1> ? And where to insert this? XF86Config, modules.conf
or anywhere else?     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From a.lahun@...  2003-27-08 14:33 -------
export in shell of course
put it in /etc/profile /etc/environment
whatever used by your shell and distribution     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From bugzilla@...  2003-28-08 16:31 -------
Ok, so I compiled 2.6.0-test4-mm2 w/ patch #540 and xfree 4.3.99-10. Everything 
applied and compiled just fine. I go to startup X and I get this...

agpgart: Detected Ati IGP330/340/345/350/M chipset
agpgart: Maximum main memory to use for agp memory: 380M
agpgart: AGP aperture is 64M @ 0xe4000000
[drm] Initialized radeon 1.9.0 20020828 on minor 0

Linux sonic 2.6.0-test4-mm2 #3 Wed Aug 27 23:10:29 PDT 2003 i686 Mobile Intel
(R) Celeron(R) CPU 1.60GHz GenuineIntel GNU/Linux

(--) Chipset ATI Radeon IGP330M/340M/350M (U2) 4337 found
(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) RADEON(0): PCI bus 1 card 5 func 0
(**) RADEON(0): Depth 16, (--) framebuffer bpp 16
(II) RADEON(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(**) RADEON(0): Option "AGPMode" "4"
(**) RADEON(0): Option "AGPFastWrite" "on"
(**) RADEON(0): Option "EnablePageFlip" "on"
(--) RADEON(0): Chipset: "ATI Radeon IGP330M/340M/350M (U2) 4337" (ChipID = 
0x4337)
(**) RADEON(0): Using AGP 4x mode
(**) RADEON(0): Enabling AGP Fast Write
(II) RADEON(0): Depth moves disabled by default
(WW) RADEON(0): Failed to set up write-combining range (0xe8000000,0x4000000)
(WW) RADEON(0): Direct rendering not yet supported on IGP320/330/340/350, 7000,
9000 integrated chips
(II) RADEON(0): Memory manager initialized to (0,0) (1024,8191)
(II) RADEON(0): Reserved area from (0,768) to (1024,770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7421
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7413
(**) Option "dpms"
(**) RADEON(0): DPMS enabled
(II) RADEON(0): Direct rendering disabled


Relevent part of XF86Config

Section "Device"
    Identifier  "ATI IGP 340m"
    Driver      "radeon"
    Option      "DPMS"
    Option      "AGPMode"       "4"
    Option      "AGPFastWrite"  "on"
    Option      "EnablePageFlip"        "on"
    BusID       "PCI:1:5:0"
EndSection     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     

j.w.bijlsma@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #458 is|0                           |1
           obsolete|                            |


     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From martin.wiesner@...  2003-29-08 14:19 -------
Hi folks!!

Great news for all Amilo Users. Thomas mastered these strange hard-lockups on
Amilo A7600 series. After applying the patches the normal way, he changed the
following file:

/<whereyoursourcesare>/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/radeon.h

He changed:

/* DMA customization:  */
#define __HAVE_DMA                         1
#define __HAVE_DMA_IRQ               1
#define __HAVE_VBL_IRQ	              1
#define __HAVE_SHARED_IRQ       1

into:

/* DMA customization:  */
#define __HAVE_DMA                         1
#define __HAVE_DMA_IRQ               1
#define __HAVE_VBL_IRQ	              1
#define __HAVE_SHARED_IRQ       0

THAT WAS THE REASON! Due to SharedIRQ enabled, the system locked when launching
X with DRI turned on, while USB, Sound Network,..., everything @ IRQ11 was
loaded.  Afterwards you have to recompile the module against your kernel as
described above. Then copy the recompiled module to 
/lib/modules/<your_kernel>/kernel/drivers/char/drm

Now everything works great. Performance could be a bit better, but I am happy to
report that 3D is now running on his and my Amilo A7800.

Perhaps it also helps on other notebooks troubling with IRQ hardlocks.

THANKS THOMAS, THANKS EVERYBODY :-)     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From michel@...  2003-29-08 15:17 -------
This probably just works around the problem by preventing the DRM from using the
IRQ?

I'd expect the problems when sharing the IRQ to be caused by one of the other
drivers using it, or I'd be very interested how the IRQ handling of the radeon
DRM can cause problems.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From a.lahun@...  2003-30-08 04:41 -------
Kevin you forgot to apply patch #502
on your Xfree sources, it will add support of DRI to user space drivers of Xfree
and #540 for kernel space part. When is said trat #502 is enough i assumed
you already patched you Xfree sources     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From martin.wiesner@...  2003-30-08 05:45 -------
To correct my last post: It works on Amilo A7600 :-)

Don't know why it is up to the radeon module that sharing IRQs causes problems 
on this notebook. But this work-around helps. I am using XFree86-4.3.99.8 
patched. Thomas uses XFree86-4.3.99.10 patched with DRI-Patch ...99.9 For him 
it also worked perfectly. Now you don't have to unload any modules anymore 
before "startx". And I have tested some 3D, no errors so far.

Greets
Martin     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From psycho_dad1@...  2003-31-08 10:25 -------
Hi all,

I do not think its the fault of the other modules. I tested with acpi enabled. 
The sound and usb module were on irq 10 then and it worked. Only the network 
module was on irq 11 and it crashed when I tried to establish a internet 
connection. Its not the problem that these modules are loaded, the problem 
occurs only if they use irq 11. The strange thing is that radeon.o used irq 5.
With this change it uses no irq. But no matter why, 3D works fine on the 
Amilo A with the change in radeon.h. Thank you for writing this driver!

Thomas Riedel
  

     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From espinosa@...  2003-31-08 18:49 -------
3D works for Amilo A, hurrrray!
Good work guys!

XFree 4.3.99.11 w/patch #502
kernel 2.6.0.test4 w/patch #540
export RADEON_NO_IRQS=1   ..in /etc/profile, without this, X hangs up system!


The only problem is with network card.
[espinosa@... espinosa]$ modprobe 8139too
Message from syslogd@... at Mon Sep  1 00:04:44 2003 ...
home kernel: Disabling IRQ #11

[espinosa@... espinosa]$ sudo /sbin/modprobe -r 8139too
Segmentation fault

sub-comment:
XFree 4.3.99.11 (dev.snapshot) have stupid bug in parsing confing in input
section (core pointer error). See mailing list for simple patch.

sub-comment:
TCL support is disabled. Is it necesarry?     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From jsublette@...  2003-01-09 00:06 -------
hardware hp pavilion ze5200
kernel 2.6.0-test4
agp patch - http://bugs.xfree86.org/attachment.cgi?id=540&action=view
Edited   /usr/src/linux-2.6.0-test4/include/linux/pci_ids.h
	change cab2 to cbb2

XFree86-4.3.99.11
	Applied config patch at:
	http://www.mail-archive.com/devel@...>
	fps with glxgears is 540

XF86Config section is:
        Identifier  "Card0"
        Driver      "ati"
        VendorName  "ATI Technologies Inc"
        BoardName   "Radeon IGP 340M"
        BusID       "PCI:1:5:0"
        Option      "DMPS"
        Option     "AGPMode"  "4"               # <i>
        Option     "AGPFastWrite" "on"          # [<bool>]
        Option     "EnablePageFlip"  "on"       # [<bool>]
EndSection     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From martin.wiesner@...  2003-01-09 07:30 -------
Hi,

found some strange things: When DRI enabled glxgears gives mit only 100FPS!!!
Without it is approx. 280 FPS. 

Here the relevant part of XF86Config:

Section "Device"
  BoardName    "Radeon Mobility IGP 320M"
  Driver       "radeon"
  Identifier   "Device[0]"
  Option       "DPMS"
  Option        "AGPFastWrite" "on"
  Option        "AGPMode" "4"
  Option        "EnablePageFlip" "on"
  Screen       0
  Option       "Rotate" "off"
  VendorName   "ATI"
EndSection

Could this be due to IRQ workaround?? See above my previos postings. Or what is
going on here...?

Greets Martin     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From lmulcahy@...  2003-01-09 23:55 -------
Created an attachment (id=555)
 --> (http://bugs.xfree86.org/attachment.cgi?id=555&action=view)
Patch for 2.4.20 Kernel (Tested with RedHat 9 Default Kernel)

This applies cleanly to the RedHat 9 default kernel 2.4.20-8 .. I thought
somenoe out there might be interested. It also may work for 2.4.21/22 kernels..
I am successfully running with AGPGart support on my Compaq N1020v.

Currently trying to get the X stuff happening, but can't seem to get things to
compile (agh!).     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From psycho_dad1@...  2003-02-09 10:28 -------
Hi, 
 
With my Amilo A the framerate with glxgears without 3D was 432fps, with 3D it 
dropped to 60fps. 
This also happened without editing radeon.h and simply deleting the 
interfering trident.o, usb-ohci.o and 8139too.o. But applications using 3D run 
smooth. The line "export RADEON_NO_IRQS=1" in /etc/profile didn´t work for me, 
radeon.o took irq 5 nevertheless and after changing radeon.h and recompiling 
the module I could delete the line "export RADEON_NO_IRQS=1" without radeon.o 
taking an irq. 
 
Greets Thomas Riedel          
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From lmulcahy@...  2003-03-09 03:23 -------
Hey Everyone,

I have tried to compile X source a few times with no success.. I keep getting 
compile errors in parts of the code unrelated to the DRI/DRM Patch. I think 
there is something wrong with the way I am compiling.

I have tried checking out both xf-4_3_99_8 and xf-4_3_99_9 tags from the cvs 
repository and get build errors in different places in both. Can someone tell 
me what I am doing wrong? or perhaps recommend some exact steps on what i need 
to do once I've got the X source with the patch applied. (I have AGPGart going 
already)

Currently I am checking out the xc module and applying the relavent patch ( I 
have tried both Hui's original against xf 4.3.99.8 and the updated patch 
against 4.3.99.9)..

The patch applies successfully and I begin a make World of xc (I assume you 
need to compile all of X??) with the following command:
make World -WORLDOPTS= 2>&1 | tee build.log

The build starts successfully and begins compiling and what not but later fails 
with a compile error (different depending on the tag) (unfortunately I 
accidently overwrote my build.log so I'll have to do the compile again and 
capture the exact error to post).

I have setup a host.def file in xc/config/cf setting ProjectRoot, 
NothingOutsideProjectRoot and EtcX11Directory so that the custom build will not 
conflict with my existing X Server install. ( I will post both my host.def file 
and exact compile error tonight after I run the build again )


If it helps:
I am currently running RedHat 9 with a 2.4.20-8 custom kernel including the 
ACPI patch, a patch for my Wireless Card (Netgear WG511) and the AGPGart patch 
I posted earlier. I have XFree 4.3.0-2 RedHat packages installed.

I am running gcc version 3.2.2 20030222 ( RedHat Linux 3.2.2-5)
"Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --
infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-
checking --with-system-zlib -enable-__cxa_atexit --host=i386-redhat-linux
Thread model: posix"

My Machine is a Compaq N1020V, P4 2.4GHz, 256M RAM and plenty of disk space to 
play with.


Do I need to be compiling the whole of X for this? If so, how is everyone else 
able to build this, yet I am not. Am I perhaps missing some C flags?

If anyone can shed some light on this I'd really appreciate it,

cheers
Lachlan     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From edc17@...  2003-03-09 08:06 -------
Did you run "make depend"?     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From espinosa@...  2003-03-09 10:37 -------
Strange, I had deleted "export RADEON_NO_IRQS=1" from /etc/profile and X didn't
crash, may be, it's really not needed for Amilo A.

Re: Lachlan Mulcahy
Did you use code directy from CVS? Generally, using sources from CVS may lead to
compilation errors. I used developers snapshot (X4.3.99.11) which would be able
to compile at least.

I also have bad experience with setting NothingOutsideProjectRoot and
EtcX11Directory, and even changing destination directory, other than /usr (I
can't start xfs after that) Destination is somewhat hardcoded in some programs.
Yes, everything is settable via command line parameters (I hope) but expect
problems with standard scripts, like "/etc/init.d/xfs start" etc.

To prevent from destroing original X:
- copy  /usr/X11R6 -> /usr/X11R6_old,    rm -fr /usr/X11R6
- save font configuration from /etc and /etc/X11 (1+2 files)
- save in /usr/lib/ libGL and libGLU (4 files ??)
  (WHY they are not in /usr/X11R6/lib as other XFree libs??? is it a bug?)

  The files described above are the only ones to be overwrited during
  make install. 
  /etc/X11/XF86Config will NOT be overwrited or modified.

- compile and install XFree to /usr

In order to return to old XFree, just:
mv /usr/X11R6 -> /usr/X11R6_new OR remove it :-)
mv /usr/X11R6_old -> /usr/X11R6

...well, this is definitly NOT the smartest way, but it's working
     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From lmulcahy@...  2003-03-09 19:18 -------
Re: Erland Cleveland

I'll try doing that before build.. 

Re: Jan Uhlir

I checked out the code tagged at xf-4_3_99_9 and xf-4_3_99_9.. Where did you 
download your developers snapshot for .11 from? (I'll have a look on the xfree 
sites to see if I can find it in the mean time).

I tried compiling xf-4_3_99_9 with the patch applied last night again to 
capture what exactly the compile error is.. I have attached my build.log and 
host.def files.. I realised that when I had previously attempted to compile xf-
4_3_99_9 i had forgotten to put the host.def file in. After putting the file in 
and attempting compile I received the exact same compile error as I did when 
attempting to build 4_3_99_8 .. 

If anyone can suggest changes I could make to the host.def that would be great, 
in the meantime i'll hunt down the .11 snapshot as suggested and give that a go.

thanks for your help,
Lachlan     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From lmulcahy@...  2003-03-09 19:28 -------
Created an attachment (id=562)
 --> (http://bugs.xfree86.org/attachment.cgi?id=562&action=view)
Lachlan Mulcahy's host.def from xf-4_3_99_9

My host.def file.. can you suggest anything wrong with it?     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From lmulcahy@...  2003-03-09 19:33 -------
Created an attachment (id=563)
 --> (http://bugs.xfree86.org/attachment.cgi?id=563&action=view)
Lachlan Mulcahy's build.log from compiling xf-4_3_99_9

My build.log .. Can anyone figure out why I get this error?     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     

lmulcahy@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
    Attachment #563|text/plain                  |application/x-gzip
          mime type|                            |


     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From espinosa@...  2003-04-09 05:57 -------
http://www.xfree86.org/develsnaps/ (actual dev.snap.)
ftp://ftp.xfree86.org/pub/XFree86/develsnaps/ (also older dev.snaps.)
I have to emphasize again, I did NOT compile and copy DRM driver (radeon.ko)
from X src. tree, bud I use kernel with patch #540     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From michel@...  2003-05-09 06:58 -------
Martin and Thomas: glxgears isn't a meaningful benchmark, but the low framerates
may indeed be related to not using the IRQ. Try setting the
R{200,ADEON}_NO_USLEEPS environment variable and make sure that
LIBGL_{SYNC,THROTTLE}_REFRESH aren't set (the latter only applies if the IRQ
hasn't been disabled in the DRM).

Lachlan, you're telling it to use the system provided Freetype2, which seems to
cause the build failure. Try not to

#define HasFreetype2		YES

You shouldn't generally need such an extensive host.def BTW, most settings have
sane defaults.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From mika@...  2003-05-09 18:14 -------
Finally direct rendering: yes!

I'm using now 4.3.99.11 w/ 502
and 2.6.0-test4-mm2 w/ 540
I did that modification mentioned in bug #138
(changed that __HAVE_SHARED_IRQ 0 then make -f Makefile.linux LINUXDIR=..., 
copied radeon.ko to /lib/modules/2.6.0-test4/kernel/drivers/char/drm/radeon.ko
and reloaded that module)
But still that problem kernel: Disabling IRQ #11

Any ideas what to do?     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From mika@...  2003-05-09 18:16 -------
Err, I mean comment #138     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     

jslupski@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jslupski@...


     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From ldecicco@...  2003-11-09 03:32 -------
I have kernel 2.4.21 patched with 439 & 480, and XFree86 4.3.99.9 patched with 
502. I recompiled kernel and XFree86 (had some problems here but finally i get 
it compiled). I also compiled radeon.o from xc tree and put it in /lib/
modules/2.4.21/... . These are my problems: 
 
1) I got no Direct Rendering (IRQ Problem mentioned by Mika) 
2) If i switch to console and then back to XFree my laptop freezes. I actually  
ssh'd from my other box and saw that X got 99.9% of CPU. After some 
investigation i found out that agpgart is responsible of this behaviour. 
 
Any hints? 
 
HW: 
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility U1 
00:01.0 PCI bridge: ATI Technologies Inc U1/A3 AGP Bridge [IGP 320M] (rev 01) 
 
Thank you in advance, 
Luca       
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From espinosa@...  2003-11-09 06:25 -------
I have done some tests:
XFree 4.3.99.11 w/patch #502

kernel 2.6.0.test4 w/patch #540 
  ..working, as I wrote before, except network card, IRQ11

NEW TESTS:
kernel 2.6.0.test5 w/patch #540  
  ..system hangs after startx, black screen 
  I didn't use patched driver from X tree
kernel 2.6.0.test4 w/patch #540 acpi=off
  ..system hangs after startx, black screen
kernel 2.6.0.test4 w/patch #540 pci=noacpi
  ..system hangs after startx, black screen

Is there anybody who get kernel 2.6.0.test5 to work??
According to kernel changelog, there is a lot of bugfixes in 8139too network
driver, so it's very promising for me to get networking to work with 2.6     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     

bero@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|No 3D support for Radeon IGP|
                   |chips                       |




------- Additional Comments From bero@...  2003-11-09 14:38 -------
IGP320M works perfectly for me in 2.4.x using the modules from XFree86 CVS 
(and XFree86 itself from CVS) with patch 502; using the same DRI source [with 
slight adaptions to make it compile due to the remap_page_range API change] 
with 2.6.0-test5-mm1 works for 2D, using 3D fails with 
 
[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held 
[drm:radeon_unlock] *ERROR* Process 1482 using kernel context 0 
 
      
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From bero@...  2003-11-09 14:41 -------
Created an attachment (id=603)
 --> (http://bugs.xfree86.org/attachment.cgi?id=603&action=view)
Make the modules from CVS compile [though unfortunately not yet work, at least
on my HW] with 2.6.0-test5-mm1
     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From philippe_coval@...  2003-11-09 16:47 -------
hi, 
As other amilo users said
It seems that the network module (8139too) 
and agp do not share IRQs friendly (*)

both work on 2.6.0-test4 but separatly

Also w/ test4 the psmouse module needs to be reloaded 
after X is started to use the touchpad.

I will release the binaries if some of want to test 3D.
Contact me in the mailing list about Amilo, IGP, etc
http://groups.yahoo.com/group/amilo/


----
(*)

# dmesg
...
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:05.0 into 4x mode
eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
irq 11: nobody cared!
Call Trace:
 [] __report_bad_irq+0x2b/0x90
 [] note_interrupt+0x64/0xa0
 [] do_IRQ+0xe9/0xf0
 [] common_interrupt+0x18/0x20
 [] handle_IRQ_event+0x20/0x70
 [] do_IRQ+0x7c/0xf0
 [] common_interrupt+0x18/0x20
 [] do_softirq+0x43/0xa0
 [] do_IRQ+0xd0/0xf0
 [] common_interrupt+0x18/0x20

handlers:
[] (rtl8139_interrupt+0x0/0x130 [8139too])
Disabling IRQ #11
...
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 30  dirty entry 26.
eth0:  Tx descriptor 0 is 00002000.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     

mharris@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mharris@...


     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     

michel@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|                            |3D support for Radeon IGP
                   |                            |chips




------- Additional Comments From michel@...  2003-14-09 07:23 -------
Restore summary, Bernhard cleared it accidentally.     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From espinosa@...  2003-14-09 17:09 -------
I'm still surprised, why DRI is not working when ACPI is disabled? What have
ACPI and DRI in common? (kernel-2.6.0.test4)     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to 
the URL shown below and enter your comments there.    
   
http://bugs.xfree86.org/show_bug.cgi?id=314     
     




------- Additional Comments From psycho_dad1@...  2003-17-09 10:37 -------
ACPI is also alloting IRQs. With ACPI disabled the ALI IRQ router does this and
sets lan, sound and usb on IRQ 11. With ACPI enabled only lan is on IRQ 11,
sound and usb have other IRQs then. 

Thomas Riedel     
     
--      
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

michel@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |flavien.lory@...




------- Additional Comments From michel@...  2003-19-09 08:12 -------
*** Bug 709 has been marked as a duplicate of this bug. ***      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From roguestar191@...  2003-25-09 22:19 -------
I'm also trying to get it to work on 2.6.0-test5.
I really don't have any clue what's wrong, I tried with 99.8 as well as 99.13, 
all I get is a blank screen... even with DRI disabled. I can reboot with 
ctrl+alt+delete, so I know the system isn't locked up completely, and I can 
remotely ssh in. I've patched the kernel, and the XFree86 Source tree using 
the appropriate patches. I did have it working before with test2 and test3. Me 
thinks it's in the XFree86 radeon_drv.o, and not in DRM, but I'm probobly 
wrong. Anywho, when is this all going to get integrated into the appropriate 
trees so we don't have to patch everything to get it running? I sure hope 
soon. thnx      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From roguestar191@...  2003-26-09 23:29 -------
I now believe the problem I've been having may be related to the kernel patch, 
and nothing to do with XFree86. When I boot into the default 2.4.20 kernel 
that's installed with RedHat 9.0 the patched Radeon driver works just fine. 
And I say this because I've tried using the old vesa driver, and the same 
problem occurs, blank screen. My system is still running, and the logs don't 
seem to show any problems. 

Offhand note:
I need to learn to debug... :-P       
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From michel@...  2003-26-09 19:09 -------
The problem is unlikely with the DRM if it also happens with DRI disabled.

As for getting this integrated, at the very least the patches need to be cleaned
up and merged to DRI CVS.

I personally don't consider old 3D clients causing lockups acceptable either,
and I'd really like the memory layout transition to be right the first time
though, maybe you can point the GATOS developers to this bug and ask them to
discuss the proposed solution?      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From andre@...  2003-05-10 04:48 -------
I have got the ATI Radeon Mobility 7000 on my Compaq Presario 2100Z. The 
notebook is running Gentoo Linux, xFree 4.3.99.9 with two of the patches above 
and Linux kernel 2.6.0-test6. 
 
It works 2D and 3D. Tuxracer, GlxGears and even Enemy Territory (Wolfenstein) 
look just fine. However, Americas Army Operations looks not fine. All 3D 
textures are messed up. Here's an example: 
https://bugzilla.icculus.org/attachment.cgi?id=92&action=view 
 
Is this because the card doesn't support "TCL" (?) or is this something which 
needs to be worked out in the driver? 
 
Thanks for all the efforts - you guys are the best!       
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From guillaume@...  2003-07-10 15:13 -------
I've tried:
 - XFree 4.3.99.11 and 4.3.99.13 with the patch #502
 - linux 2.6.0-test4 and 2.6.0-test6 with the patch #540 (with somme change for
2.6.0-test6)
 - with and without the two environement variables in /etc/profile

XFree is installed in /usr/local/X11, seems to work well without the kernel
patch (software OpenGL) with both version.

linux have a patch to change dsdt (acpi), and I've troubles with irq 10.

When I use XFree with dri, logs say that I've dri, glxinfo too. But, when I use
a 3D apps (glxgear and foobillard), XFree freeze. I can kill it with the magic
key, and reboot with the power button (acpid), but It's take a long time, so I
think that a prossessus use all the resources. I don't think that it's have any
link with my problem with irq10 because this trouble freeze totaly the computer.

If you need more info, ask.

Thanks for your job.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From guillaume@...  2003-07-10 15:15 -------
I've tried:
 - XFree 4.3.99.11 and 4.3.99.13 with the patch #502
 - linux 2.6.0-test4 and 2.6.0-test6 with the patch #540 (with somme change for
2.6.0-test6)
 - with and without the two environement variables in /etc/profile

XFree is installed in /usr/local/X11, seems to work well without the kernel
patch (software OpenGL) with both version.

linux have a patch to change dsdt (acpi), and I've troubles with irq 10.

When I use XFree with dri, logs say that I've dri, glxinfo too. But, when I use
a 3D apps (glxgear and foobillard), XFree freeze. I can kill it with the magic
key, and reboot with the power button (acpid), but It's take a long time, so I
think that a prossessus use all the resources. I don't think that it's have any
link with my problem with irq10 because this trouble freeze totaly the computer.

If you need more info, ask.

Thanks for your job.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From guillaume@...  2003-08-10 21:40 -------
I give some more informations :

 - My laptop is a Compaq Presario 2141ea (French model)

texitoi@...:~$ lspci
00:00.0 Host bridge: ATI Technologies Inc: Unknown device cab0 (rev 13)
00:01.0 PCI bridge: ATI Technologies Inc U1/A3 AGP Bridge [IGP 320M] (rev 01)
00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link
Controller Audio Device (rev 02)
00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV]
00:08.0 Modem: ALi Corporation Intel 537 [M5457 AC-Link Modem]
00:0a.0 CardBus bridge: O2 Micro, Inc. OZ6912 Cardbus Controller
00:10.0 IDE interface: ALi Corporation M5229 IDE (rev c4)
00:11.0 Bridge: ALi Corporation M7101 PMU
00:12.0 Ethernet controller: National Semiconductor Corporation DP83815
(MacPhyter) Ethernet Controller
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility U1
texitoi@...:~$ 

seems to be very close to Fujtisu Amilo.

 - My changes to linux 2.6.0-test6 was very small :
s/dev_priv->agp/dev_priv->gart/g to the patch. I say that from memory, because
when I've tryed that kernel, I didn't think it can work... I'm using this kernel
now.

I'm repeating, I've done the same tests with 2.6.0-test4, so my change is not
the troubles, because it don't work with 2.6.0-test4 too...

If I can (and have the motivation), I'll try to connect to my laptop with ssh to
see what happen.

If you want more informations, answer.

Sorry to have posted 2 times my bug report.

Thanks.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From guillaume@...  2003-09-10 15:46 -------
Created an attachment (id=706)
 --> (http://bugs.xfree86.org/attachment.cgi?id=706&action=view)
My change to attachement #540 for 2.6.0-test6

Here is my change to attachement #540.

On my box, it does the same thing than #540 on kernel 2.6.0-test4 (freezing...)      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From espinosa@...  2003-11-10 17:01 -------
I have some success with running 2.6.0-test7 kernel with TeXitoi patch #706.
Thank you, TeXitoi!

First impresions:
- KDE is hanging up during startup (initializing periphetals); Gnome goes well
- network still not working (IRQ 11 problem)  


Another question. New XFree development snapshot is out! And some changes refers
to Radeon:
<snip>
478. Radeon driver fixes (Hui Yu@...)
      - 9200 DVI fix and TMDS_PLL initialization for all chips
      - New chips support (9800XT/SE, 9600XT/SE, M11, T2/X2 etc.)
      - Cleanup unused/secondary chip ids
      - Autodetect PCI cards
      - Add BusType to override PCI card autodetect
      - Add display bandwidth calculation routine to fix flickering/tearing
        display problem
      - Workaround for corrupted BIOS image causing incorrect panel size
      - Fix the LCD table reading loop
      - Various small changes (including improving DDC reliability and
        CRTC_MORE_CNTL initialization)
</snip>

Hui, is there somem change for us - Radeon IGP users?
Is it worth to compile new snapshot? 
Still have to use patch #541 ? 
Anyway, thank you for all your work.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From michel@...  2003-11-10 19:34 -------
As you'll see when you do a cvs update, IGP DRI support hasn't been integrated
yet. I've started working on it though, hopefully I'll have something to test
after this weekend. (I also hope it'll make it into 4.4, but that'll be tight,
so don't put your hopes too high - there's always the DRI snapshots :)      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

jasonthomasdolan@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jasonthomasdolan@...


      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From jasonthomasdolan@...  2003-12-10 05:02 -------
That'd be awesome, Michel.  I was unable to build 4.3.99_9 (with or without the
various patches from this page, actually), and I was also unable to merge the
patches to later XFree snapshots which do compile for me.  I've been waiting to
see these patches cleanly merged into CVS..that'd be great :)  

If you'd like any help testing or whatever, I've got the 4.3.99_14 source and
nothing to do tomorrow.  My laptop has the 320M (4336), and I'm running kernel
2.6.0-test6 (I can upgrade to test7 if you'd like, too).      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From bero@...  2003-12-10 08:50 -------
Created an attachment (id=723)
 --> (http://bugs.xfree86.org/attachment.cgi?id=723&action=view)
Make it compile (and work) with CVS HEAD as of 2003/10/12

Attached new patch relative to current (2003/10/12) XFree86 CVS HEAD.
      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From jsublette@...  2003-12-10 11:38 -------
kernel 2.6.0-test7
XFree86 version: 4.3.99.14
XFree patch attachment: 723
kernel patch attachment: 706

glxgears = 2792 frames in 5.0 seconds = 558.400 FPS

Direct render is enabled.  Really nice job. thanks.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From jasonthomasdolan@...  2003-12-10 13:52 -------
Your patch applied cleanly to the 4.3.99_14 snapshot, TeXitui's patch applied
cleanly to 2.6.0-test6, everything compiled and DRI is enabled, but my
framerates aren't quite where I'd expect them to be.  Here's a little more info:

System:
Athlon XP 2.4
512MB
64MB shared IGP 320 (4336)

XF86Config-4:
Driver      "radeon"
Option      "dpms"
Option      "AGPMode" "4"
Option      "PageFlip" "on"
Option      "AGPFastWrite" "on"

glxgears: ~200fps
Quake2: ~30fps @ 640x480

Any ideas?  I'm going to turn down my bpp from 24 to 16 and see if that makes a
huge difference.

Still, thank you so much for all of this!
      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From jasonthomasdolan@...  2003-12-10 15:09 -------
On further inspection, doesn't this look like something's "capping" my framerate?

$ glxgears 
disabling TCL support
853 frames in 5.0 seconds = 170.600 FPS
1000 frames in 5.0 seconds = 200.000 FPS
998 frames in 5.0 seconds = 199.600 FPS
1002 frames in 5.0 seconds = 200.400 FPS
1000 frames in 5.0 seconds = 200.000 FPS
1000 frames in 5.0 seconds = 200.000 FPS
1000 frames in 5.0 seconds = 200.000 FPS
1000 frames in 5.0 seconds = 200.000 FPS

It seems like once the system stabilizes, it stays right at 200fps with
absolutely no fluctuation.  That's really strange, no?  This hardware is very
capable of 500fps+.  Also, the QuakeForge project is still using Mesa Indirect
rendering (software OpenGL, 4fps) while Quake2 uses DRI.  That's wierd, too,
isn't it?  I'm going to install Q2Hack to get fullscreen working, and see if
PageFlip helps out at all.  Any ideas or advice would be much appreciated!
      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

michael@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michael@...


      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From jasonthomasdolan@...  2003-14-10 22:03 -------
Someone (sincere appologies for not remembering who) emailed me with a solution
for my performance issues.  If you're having similar issues, add the following
to /etc/profile:

export RADEON_NO_IRQS=1
export RADEON_NO_USLEEPS=1

My glxgears framerate is now ~450, while my Quake2 and QuakeForge framerates are
very playable (~70 @ 640x480x24bpp).

I'd really like to thank everyone who contributed to these patches.  For a
little while I was starting to regret purchasing my laptop..I'm very happy now.
 I can program in Java3D oncemore :)      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From michael@...  2003-15-10 18:17 -------
I just wanted to add my thanks to the people working on these patches. 
Currently I am running 4.3.99.14 with patch 723 and 2.4.22-ac4 with no patch. 
DRI works fine and glxgears reports around 450 fps.

      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From roguestar191@...  2003-17-10 22:37 -------
I've been having a problem with XFree86 Randomly locking up. I'm running 
kernel 2.6.0-test7 with XFree86 4.3.99.14. It seems to happen when I'm running 
xscreensaver with an opengl screensaver, and at times running 3D games. Could 
this be related to the patch?
HP ZE4145
ATI Radeon IGP320
AMD Athlong XP 1800+ / 512m ddr sdram.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From jasonthomasdolan@...  2003-18-10 03:23 -------
I'm not really sure.. I've not had a single lockup, and I've really put this
thing through it's paces.  I have a very similar setup to yours (IGP320, kernel
2.6.0-test7, xfree 4.3.99_14).  Some of the "tests" I've done: I let Quake2
timedemo for a few hours, I've edited Q2 maps using GtkRadiant (OpenGL enabled)
and started/exited Quake2 to test my maps while Gtk was up.  I've played the
QuakeForge for a few hours also.  The patches seem to work great for me :/  Is
there any info in you log files?      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From roguestar191@...  2003-18-10 08:11 -------
no, there's nothing in my log files. I'm wondering if it could be the way I've 
got my kernel set up. I just freshly installed RedHat 9(again..), and 
installed all this stuff. The first time I did it I couldn't get many programs 
to run in XFree86, they'd start then use 100% of the CPU and never open. Some 
programs like my window manager, Blackbox, would run, but gnome, kde, and all 
the programs related to them wouldn't start, and I couldn't find any problems. 
I tried running them with gdb, no luck. Do you think it'd be possible to send 
me a copy of your .config file? I have a feeling that could be the problem. If 
it's not, then I'll screw around with it longer to try to figure it all out. 
Thanks, :).       
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From jasonthomasdolan@...  2003-18-10 10:08 -------
Created an attachment (id=740)
 --> (http://bugs.xfree86.org/attachment.cgi?id=740&action=view)
Linux 2.6.0-test7 .config (no modules)

Sure, here you go.  I run a monolithic kernel (no modules), but I think module
support is still enabled (ya, I suck).

Honestly, I would suggest trying a tighter distro.  I moved away from RedHat
just this past summer.	I was sick of not being able to compile anything
because of dated libs, not understanding what half the stuff in /etc did, and
feeling like my machine was some mess that miraculously worked 90% of the time.
 I'm running CRUX (http://www.crux.nu) right now, and I couldn't be happier. 
i686 optimized, simple but adequate package management, and no bloat. 
Everything works; everything's easy to understand.  Not to mention a *full*
install is like 300MB ;)      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From roguestar191@...  2003-18-10 20:15 -------
Thanks but no thanks, I like my redhat. I've figured out what most of the /etc 
files do, and I like the security. I've also never had any real problems 
compiling anything, and when I did I took the time to figure it out, thus 
learning more about linux, :). It's amazing what you can learn and what you can 
find trying to install 1 single program, :-P. I think I've got the problem 
squared away, I took out a bunch of things, and found I accidently left a couple 
things out of the kernel that should have been there. Thanks still, and I'm 
taking a look at your kernel config.. btw, that's how I do it too, no modules, 
except USB stuff. I think my 3D Acceleration is working properly now, if not 
I'll take a look at crux, otherwise I'm sticking to redhat, :). Kudos!      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From edc17@...  2003-19-10 00:35 -------
I'm not sure if this is related, but I had a very similar problem.

It mainly appeared when moving or resizing a window. But I did notice it
freezing up my comp every now and then with the xscreensaver's.

If you look back in the posts here you'll see a more detailed description of the
problem I was having. The fix was to use the DRI version of the 3D (and 2D? Not
sure) drivers. As opposed to the XFree drivers. This involved downloading the
DRI CVS, and applying the whole patch by hand (as a few things are different).
After that, no more problems! Haven't had a single lock up since. Apparently its
a bug with the XFree CVS or something... who knows!

Anyway, good luck - and if you have actually fixed the problem, good for you!      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From misc_internet@...  2003-19-10 08:00 -------
Hi,
I have a presario 905eu with the IGP320M chipset and thanks to the great work
you are doing I've got 3D acceleration working on my laptop. I'am using kernel
2.4.21 patched with attachement 480 and xfree 4.3.99.14 with either 502 or 723
patches. The 502 patch gives around 340 fps while the patch 723 gives up to 403
fps. The same gears application under windows is giving around 700 fps. In my
case, the exports in /etc/profile do not make any difference. Another problem
I've detected is that texture sizes of 1024 do not work and I have a little
problem with double buffering. 

Are these performances "normal" ?

Thanks      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From paul@...  2003-21-10 18:43 -------
Thanks to everyone in here i'm looking at fluxbox running glgears at 400fps
whilst emerging firebird on my nice gentoo development-sources box

Linux laptop 2.6.0-test6 #1 Sat Oct 18 20:09:32 BST 2003 i686 mobile AMD
Athlon(tm) XP 2000+   AuthenticAMD GNU/Linux


Thanks a lot, this is brilliant.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From guillaume@...  2003-21-10 17:07 -------
There is news for my problem :

I use kernel 2.6.0-test7 with patch #706 and XFree86 4.3.99.14 with patch #723
on a compaq presario 2141ea (IGP 320M)

I've done a ssh connexion during a 3D test :

When the system freeze, I have glxgear that takes all the resources CPU. When I
kill it with KILL signal, XFree86 takes all the resources CPU, and I can't kill
it (root with KILL signal). TERM signal does nothing on both processi. I can reboot.

If anyone have an idea, I'd like to use 3D...

If you have more questions, or you have any debug idea, I can do it without
problems.

Thanks for you're job.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From theophile@...  2003-22-10 09:36 -------
I need a little help getting this working.

I have 2.4.22-ac4 unpatched and X 4.3.99.14 with patch 723.

I have DRI, glx and radeon in my X config file.

'startx' gives this in /var/log:

(==) RADEON(0): Write-combining range (0xe0000000,0x4000000)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "radeon"
(II) RADEON(0): [drm] drmOpen failed
(EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.

I have a feeling I;ve forgotten something simple.

BTW, glxgears segfaults.

What have I missed?

Thanks!      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From jasonthomasdolan@...  2003-22-10 10:20 -------
What does "ls -l /dev/dri" show?  Are you running devfs?      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From paul@...  2003-22-10 18:18 -------
"I have 2.4.22-ac4 unpatched"

You have no module in the kernel for support of the radeon, either compile the
Xfree module seperately then insmod it, or use the kernel patch.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

mharris@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|mharris@...    |


      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From theophile@...  2003-23-10 08:22 -------
"You have no module in the kernel for support of the radeon, either compile the
Xfree module seperately then insmod it, or use the kernel patch."

Is there a patch for 2.4.22-ac4? Patch 437 doesn't seem to patch properly.

How do I compile the Xfree module? Is the source in the X source tree?      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From theophile@...  2003-23-10 08:35 -------
Okay, sorry. I read some of the earier comments and I got the new radeon.o
compiled and installed.

But DRI still fails to load becuse of no AGP support. I ge tthe following when
trying to 'modprobe agpgart':

/lib/modules/2.4.22-ac4/kernel/drivers/char/agp/agpgart.o: init_module: No such
device
/lib/modules/2.4.22-ac4/kernel/drivers/char/agp/agpgart.o: Hint: insmod errors
can be caused by incorrect module parameters, including invalid IO or IRQ
parameters.
      You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-ac4/kernel/drivers/char/agp/agpgart.o: insmod
/lib/modules/2.4.22-ac4/kernel/drivers/char/agp/agpgart.o failed
/lib/modules/2.4.22-ac4/kernel/drivers/char/agp/agpgart.o: insmod agpgart failed

      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

raharu@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |raharu@...


      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From other@...  2003-25-10 17:32 -------
I realize this may not be the proper place to ask this, but has anybody had any
luck with MergedFB http://bugs.xfree86.org/show_bug.cgi?id=276 on an igp320. I
have just been making a few posts over there today. Basically my second head
isn't getting a signal, even though mergedfb is enabled. I would greatly
appreciate any advice you can offer.

Thanks
-David Smith      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From espinosa@...  2003-23-10 11:50 -------
I have done some some tests:

kernel 2.6.0-test8 w/patch #703
XFree 4.3.99.14 w/patch #723 (I do not use DRM driver from X source but the
patched from kernel)
FujitsuSiemens Amilo A, Athlon XP +1400

- I have to clean /etc/modprobe.conf (all lines commented)
  It was formely generated by modutils. If I didn't do it, XFree hangs on during
startup.
  In 2.6.0-test7 my modprobe.conf causing only KDE freezing during "initializing
periphetals",
  Gnome went well, in 2.6.0-test8 freezes all XFree.
  I have full driver management in  my hands, using only modprobe.

- SOUND NOT WORKING if DRI is enabled
  modprobe snd-ali5451 (for alsa) cause system freezing immediately
  modprobe trident (for OSS) cause system freezing immediately
  If DRI is disabled the statements above work well.

- network card not working if DRI is enabled (it's well known problem for Amilo A)
  modprobe 8139too (nothing suspicious happen, module is loaded)
  ifconfig eth0 up   ...error message appears from kernel: disabling IRQ #11,
  but system goes on well, except network, but nothing freezing.

- DRI works well, gives me around 400FPS in glxgears.
  Tuxracer have slight distortions in first screen, like big one-pixel-thin
screen-wide cross, or like
  screen to be assembled from 4 smaller pictures. But then continues well.
  Quake3Arena Demo - nearly no problem, only some textures slightly flickering
when I directly
  facing them, but it's not a big problem.

- setting or unsetting in /etc/profile
  export RADEON_NO_IRQS=1
  export RADEON_NO_USLEEPS=1
  ..seems to have no efect

Kerner 2.6.0-test4-patch540 DRI works still best for Amilo:
no problems with sound,
any screen distortions.
only the network is the problem (I have to switch between two XF86Configs)
It's independent on  XFree version 4.3.99.14 or 4.3.99.11 or 4.3.99.12.

I much prefer 2.6 kernel, for desktop/laptop users is really better, it's
significant.

I will give a try to DRM driver from X source in the next tests.
      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

rick@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rick@...


      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From rick@...  2003-26-10 21:01 -------
Running kernel 2.6.0-test7 with patch #706 (compiled in atm, but no speed diff)
Running XFree86 4.3.99-14 with patch #723 (installed with make World && su -c
"make install"; XFree86 -version gets proper one though)

I can get DRI working (tuxracer works great, glxgears up to ~200, nwn ~3fps
tops).  Glxgears without dri are about ~180-220, but CPU usage makes it obvious
that dri does in fact work in the former case.  Preemtive option in the kernel
makes no difference.

At one point in the past, I had X saying that dri was enabled in my logs and
glxinfo claiming it was not (should be unrelated to this though).  This line in
particular I think might indicate the problem, but most references refered to it
as a 2D problem: "(WW) RADEON(0): Failed to set up write-combining range
(0xe0000000,0x4000000)".  Also, I get a "disabling TCL support" in whatever
terminal I try to run an app that uses OpenGL.  KDE also crashes near the end of
it's startup, so I'm using IceWM atm (noticed that this seems to be kernel
dependant behavior but not yet narrowed down the cause).

The base distro I started with is Mandrake 9.2 download edition.  The hardware
is a Compaq 2100 series (AMD Mobile 2200+, 512MB ram, 320M graphics).

from dmsg:
*******************************************
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected Ati IGP320/M chipset
agpgart: Maximum main memory to use for agp memory: 379M
agpgart: AGP aperture is 64M @ 0xd4000000
[drm] Initialized radeon 1.9.0 20020828 on minor 0

from /etc/X11/XF86Config-4
*******************************************
dri, glx, etc all enabled higher up
....
Section "Device"
    Identifier "device1"
    VendorName "ATI Technologies Inc"
    BoardName "Radeon Mobility U1"
    Driver "radeon"
    Option "AGPMode" "4"
    Option "AGPFastWrite" "True"
#    Option "EnablePageFlip" "True" #makes no speed difference
    Option "DPMS"

from /var/log/XFree86.0.log
****************************************
(II) RADEON(0): PCI bus 1 card 5 func 0
(**) RADEON(0): Depth 16, (--) framebuffer bpp 16
(II) RADEON(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(**) RADEON(0): Option "AGPMode" "4"
(**) RADEON(0): Option "AGPFastWrite" "True"
(==) RADEON(0): RGB weight 565
(II) RADEON(0): Using 6 bits per RGB (8 bit DAC)
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/X11R6/lib/modules/linux/libint10.a
(II) Module int10: vendor="The XFree86 Project"
	compiled for 4.3.99.14, module version = 1.0.0
	ABI class: XFree86 Video Driver, version 0.7
(II) RADEON(0): initializing int10
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
(--) RADEON(0): Chipset: "ATI Radeon IGP320M (U1) 4336" (ChipID = 0x4336)
(--) RADEON(0): Linear framebuffer at 0xe0000000
(--) RADEON(0): VideoRAM: 65536 kByte (64 bit DDR SDRAM)
(II) RADEON(0): AGP card detected
...
(II) RADEON(0): Page flipping disabled
(!!) RADEON(0): For information on using the multimedia capabilities
 of this adapter, please see http://gatos.sf.net.
...
(WW) RADEON(0): Failed to set up write-combining range (0xe0000000,0x4000000)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmGetBusid returned ''
(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:5:0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xdd929000
(II) RADEON(0): [drm] mapped SAREA 0xdd929000 to 0x44269000
(II) RADEON(0): [drm] framebuffer handle = 0xe0000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(II) RADEON(0): [agp] Mode 0x0f000214 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]
(II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001
(II) RADEON(0): [agp] ring handle = 0xd4000000
(II) RADEON(0): [agp] Ring mapped at 0x4426b000
(II) RADEON(0): [agp] ring read ptr handle = 0xd4101000
(II) RADEON(0): [agp] Ring read ptr mapped at 0x4436c000
(II) RADEON(0): [agp] vertex/indirect buffers handle = 0xd4102000
(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x4436d000
(II) RADEON(0): [agp] GART texture map handle = 0xd4302000
(II) RADEON(0): [agp] GART Texture map mapped at 0x4456d000
(II) RADEON(0): [drm] register handle = 0xd0100000
(II) RADEON(0): [dri] Visual configs initialized
(II) RADEON(0): CP in BM mode
(II) RADEON(0): Using 8 MB GART aperture
(II) RADEON(0): Using 1 MB for the ring buffer
(II) RADEON(0): Using 2 MB for vertex/indirect buffers
(II) RADEON(0): Using 5 MB for GART textures
(II) RADEON(0): Memory manager initialized to (0,0) (1024,8191)
(II) RADEON(0): Reserved area from (0,768) to (1024,770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7421
(II) RADEON(0): Will use back buffer at offset 0x600000
(II) RADEON(0): Will use depth buffer at offset 0x780000
(II) RADEON(0): Will use 56320 kb for textures at offset 0x900000
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
	Screen to screen bit blits
	Solid filled rectangles
	8x8 mono pattern filled rectangles
	Indirect CPU to Screen color expansion
	Solid Lines
	Dashed Lines
	Scanline Image Writes
	Offscreen Pixmaps
	Setting up tile and stipple cache:
		32 128x128 slots
		32 256x256 slots
		16 512x512 slots
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7413
(**) Option "dpms"
(**) RADEON(0): DPMS enabled
(II) RADEON(0): X context handle = 0x00000001
(II) RADEON(0): [drm] installed DRM signal handler
(II) RADEON(0): [DRI] installation complete
(II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
(II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
(II) RADEON(0): [drm] dma control initialized, using IRQ 9
(II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
(II) RADEON(0): Direct rendering enabled
(==) RandR enabled

glxinfo output
***********************************
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, 
    GLX_SGI_make_current_read
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, 
    GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, 
    GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, 
    GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
    GLX_SGIX_visual_select_group
GLX extensions:
    GLX_ARB_get_proc_address, GLX_EXT_import_context, GLX_EXT_visual_info, 
    GLX_EXT_visual_rating, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, 
    GLX_SGI_video_sync
OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI Radeon 20030328 AGP 4x x86/MMX+/3DNow!+/SSENO-TCL
OpenGL version string: 1.2 Mesa 5.0.2
OpenGL extensions:
    GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, 
    GL_ARB_texture_border_clamp, GL_ARB_texture_compression, 
    GL_ARB_texture_env_add, GL_ARB_texture_env_combine, 
    GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, 
    GL_ARB_transpose_matrix, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, 
    GL_EXT_blend_color, GL_EXT_blend_logic_op, GL_EXT_blend_minmax, 
    GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, 
    GL_EXT_compiled_vertex_array, GL_EXT_convolution, GL_EXT_copy_texture, 
    GL_EXT_draw_range_elements, GL_EXT_histogram, GL_EXT_packed_pixels, 
    GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color, 
    GL_EXT_separate_specular_color, GL_EXT_subtexture, GL_EXT_texture, 
    GL_EXT_texture3D, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, 
    GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, 
    GL_EXT_texture_filter_anisotropic, GL_EXT_texture_object, 
    GL_EXT_texture_lod_bias, GL_EXT_vertex_array, GL_APPLE_packed_pixels, 
    GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once, 
    GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, 
    GL_MESA_ycbcr_texture, GL_MESA_window_pos, GL_NV_blend_square, 
    GL_NV_texture_rectangle, GL_NV_texgen_reflection, GL_SGI_color_matrix, 
    GL_SGI_color_table, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, 
    GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod
glu version: 1.3
glu extensions:
    GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x23 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x24 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  8  0  0  0  0  0 0 None
0x25 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x26 16 tc  0 16  0 r  .  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x27 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x28 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 None
0x29 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x2a 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x2b 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x2c 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  8  0  0  0  0  0 0 None
0x2d 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x2e 16 dc  0 16  0 r  .  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow
0x2f 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x30 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 None
0x31 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16  0  0 0 Slow
0x32 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 Slow


suspect unrelated, but still curious
***********************************
In /var/log/XFree86.0.log, I get some of these.  Anyone know offhand how to
disable this check?  My hardware does not support APM.

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From theophile@...  2003-27-10 01:02 -------
Richard, could I get your .config file?

I'm having a hard time getting my 2.6 kernel past the INIT point (it keeps
locking up).      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From psycho_dad1@...  2003-27-10 06:34 -------
There is a laptop kernel-patch for 2.4.22 including IGP-Chipset support under
http://www.sonarnerd.net/projects/linux (2.4.22-jl15.patch.bz2). It has acpi,
cpufreq and many other useful updates for laptops too. Works good for me with
the XFree86-patch from 2003-10-18 and the development snapshot 4.3.99.14. The
framerates in games (not in glxgears) with 4.3.99.14 are higher (ca. 30%)
compared with 4.3.99.13 and lower. Network, Sound, USB and all other modules
work too at the same time changing radeon.h disabling IRQ-sharing.

Thomas       
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From rick@...  2003-27-10 13:56 -------
Created an attachment (id=772)
 --> (http://bugs.xfree86.org/attachment.cgi?id=772&action=view)
My Compaq 2100 series .config for test7 with #706

I have been compiling with the default gcc shipping with Mandrake 9.2 (3.3
something).  I know this kernel isn't perfect and is missing support for some
things the hardware supports (possibly floppy, parallel, serial, modem, etc). 
It does however boot for me.  I get errors starting X that might be MTRR
related and do get very poor performance for many apps, but dri is working. 
Keep in mind this is the AMD Athlon Mobile 2200+ processor and Compaq has
additional BIOS flaws that affect powernow in the later Barton cores.  Also
note that KDE crashes on this kernel atm w/ 4.3.99-14 Xfree86 + #723 (trying to
track down which option does it, didn't used to crash for me before I changed
some kernel options).      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

rick@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
    Attachment #772|application/octet-stream    |text/plain
          mime type|                            |


      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

For Neverwinter Nights on my radeon 8500 I have to use the R200_NO_TCL=1
to get the game to be playable.   How do I set the same command for and
old Radeon AIW (R100)?

Thanks
CuZnDragon

On Mon, 27 Oct 2003 16:03:42 -0600
Robin Cook <rcook@...> wrote:

> For Neverwinter Nights on my radeon 8500 I have to use the R200_NO_TCL=1
> to get the game to be playable.   How do I set the same command for and
> old Radeon AIW (R100)?

That depends on the driver version. With a pre-config build it's

RADEON_TCL_FORCE_DISABLE=1

With the new configuration infrastructure the commandline way would be:

tcl_mode=0

Using ~/.drirc is recommended, though.

> 
> Thanks
> CuZnDragon
> 

Felix

------------    __\|/__    ___     ___       -------------------------
 Felix       ___\_e -_/___/ __\___/ __\_____   You can do anything,
   Kühling  (_____\Ä/____/ /_____/ /________)  just not everything
 fxkuehl@...       \___/   \___/   U        at the same time.

Not sure which driver version.  I am using the DRM driver from the
2.6.0-test9 kernel and the DRI driver that is in xfree86 4.3.99.14.

Thanks for the info.
CuZnDragon

On Mon, 2003-10-27 at 16:35, Felix K=FChling wrote:
> On Mon, 27 Oct 2003 16:03:42 -0600
> Robin Cook <rcook@...> wrote:
>=20
> > For Neverwinter Nights on my radeon 8500 I have to use the R200_NO_TC=
L=3D1
> > to get the game to be playable.   How do I set the same command for a=
nd
> > old Radeon AIW (R100)?
>=20
> That depends on the driver version. With a pre-config build it's
>=20
> RADEON_TCL_FORCE_DISABLE=3D1
>=20
> With the new configuration infrastructure the commandline way would be:
>=20
> tcl_mode=3D0
>=20
> Using ~/.drirc is recommended, though.
>=20
> >=20
> > Thanks
> > CuZnDragon
> >=20
>=20
> Felix
>=20
> ------------    __\|/__    ___     ___       -------------------------
>  Felix       ___\_e -_/___/ __\___/ __\_____   You can do anything,
>    K=FChling  (_____\=C4/____/ /_____/ /________)  just not everything
>  fxkuehl@...       \___/   \___/   U        at the same time.
>=20

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

edc17@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |edc17@....
                   |                            |nz


      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From fredi@...  2003-03-11 16:58 -------
Hi people, 
Does anyone know if the changes to xfree needed for this driver are going to 
be merged (or better yet, are merged) before xfree 4.4 ? 
 
Thank you, 
Fredi       
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From michel@...  2003-03-11 21:32 -------
I have committed
http://penguinppc.org/~daenzer/DRI/applied/radeon-memory-transition.diff to DRI
CVS; now http://penguinppc.org/~daenzer/DRI/radeon-igp.diff is all that should
be needed for IGP DRI support, please test.

As for whether it'll make it into 4.4.0, that's up to Kevin E. Martin, but I'm
afraid it's unlikely.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From martin@...  2003-03-11 21:54 -------
Michel, I looked over your patches, and they look fine, but it is too large of a
change to get into 4.4 at this late stage; however, let's get it checked in
right after 4.4 goes out so that it can get maximum exposure/testing for the
following release.  This can either be handled via the DRI tree, which I hope
will be resync'd with XFree86 shortly after 4.4 goes out, or you can check it
directly into XFree86.
      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

daf@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daf@...


      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From espinosa@...  2003-05-11 08:03 -------
some more tests for kernels 2.6:

kernel 2.6.0-test9 w/patch #703 (serial and paralel drivers as modules)
XFree 4.3.99.14 w/patch #723 + modify radeon.h as in comment #138
FujitsuSiemens Amilo A, Athlon XP +1400
Now I use radeon.ko from xfree source, copied to
/lib/modules/2.6.0-test9/kernel/drivers/char/drm

But the result was the same, whatever takes IRQ 11, system freezes (soundcard)
or just something stops working (network). Setting env. variable RADEON_NO_IRQS
makes no difference. There is no difference, if I disable IRQ sharing in
radeon.h or enable it. If I enable IRQ for Radeon, it takes IRQ 5, not IRQ 11!
What is so peculiar with IRQ 11 & DRI? 

There is also the same distortion in tuxracer (not seen in 2.6-test4)

More precisely
1/
modprobe snd-ali5451 (for alsa) cause system freezing immediately.
Problem is, that as from test7 (??) alsa driver for ali5451 soundcard stops
using irq 10 and now use irq 11 and there is no module parameter to change it
as far as I know.

2/
modprobe 8139too (nothing suspicious happen, module is loaded)
ifconfig eth0 up   ...error message appears from kernel: disabling IRQ #11,
but system goes on well, except network, but nothing freezing.

3/ everything is OK if dri is not enabled in XF86Config

I also try set/unset  for other values in radeon.h
/* DMA customization:  */
#define __HAVE_DMA                         1
#define __HAVE_DMA_IRQ               1
#define __HAVE_VBL_IRQ	              1
#define __HAVE_SHARED_IRQ       0
..but every change to 0, except __HAVE_SHARED_IRQ, ends up in compilation error.

Some more info (.config,dmesg,interrupts..):
http://espinosa.webz.cz/debugging/

Some suspicious lines from dmesg:
...
ACPI: PCI Interrupt Link [LNKE] (IRQs 5 9 *10 11)
ACPI: PCI Interrupt Link [LNKF] (IRQs 5 9 10 11)
ACPI: PCI Interrupt Link [LNKG] (IRQs 5 9 10 *11)
ACPI: PCI Interrupt Link [LNKH] (IRQs 5 9 10 *11)
    ACPI-1120: *** Error: Method execution failed [\_SB_.PCI0.LPCB.LNKU._CRS]
(Node c127f700), A
E_AML_UNINITIALIZED_LOCAL
    ACPI-0098: *** Error: Method execution failed [\_SB_.PCI0.LPCB.LNKU._CRS]
(Node c127f700), A
E_AML_UNINITIALIZED_LOCAL
...
PnPBIOS: 17 nodes reported by PnP BIOS; 17 recorded by driver
    ACPI-1120: *** Error: Method execution failed [\_SB_.PCI0.LPCB.LNKU._CRS]
(Node c127f700), A
E_AML_UNINITIALIZED_LOCAL
    ACPI-0098: *** Error: Method execution failed [\_SB_.PCI0.LPCB.LNKU._CRS]
(Node c127f700), A
E_AML_UNINITIALIZED_LOCAL
....
ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 11
ACPI: No IRQ known for interrupt pin A of device 0000:00:04.0
...
ALI15X3: IDE controller at PCI slot 0000:00:04.0
ACPI: No IRQ known for interrupt pin A of device 0000:00:04.0
...

P.S.
If someone encounter problems with KDE freezing during startup, try check
modules.conf (for 2.4 kernels) or modprobe.conf (for 2.6 kernels) try comment
all (as I did) or just aliases related to soundcard.
      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From espinosa@...  2003-05-11 08:28 -------
To: Michel Dänzer (re: Comment #209)

So, if I
1/
take dev. snapshot (sorry, I can't use CVS, I'm behind restrictive firewall) of
DRI from:
http://dri.sourceforge.net/snapshots/
something like:
radeon-20031104-linux.i386.tar.bz2 
(this should contain your commited patch
http://penguinppc.org/~daenzer/DRI/applied/radeon-memory-transition.diff  )
2/
Unpack it and apply your patch from:
http://penguinppc.org/~daenzer/DRI/radeon-igp.diff
3/
install DRI driver as it's described in read.me in the package

No need to patch kernel with #706 or xfree with #723 ?
Just vanilla 2.6-test9 kernel and vanilla xfree 4.3.99.14 ?

I'm I right?

Do you thing, can your new patches helps with problems with IRQ 11 (comment #211)? 

BTW:
Can be your patch included in RedHats/Fedora version XFree4.4 ?
They use a lot of their own patches anyway.

Thanks' everybody for all the work!
      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From michel@...  2003-05-11 10:10 -------
I haven't made any IRQ specific changes so it's unlikely to make a difference
I'm afraid.

Note that you can't test my patch with a binary snapshot, you need to rebuild
the 2D and 3D drivers.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From espinosa@...  2003-07-11 09:22 -------
Yes, I really didn't notice it's binary driver, only kernel side (DRM) are sources! 

Is there no chance to get the DRI sources without CVS?
Well ..I can wait until DRI sources will be synchronized and included in XFree.
Can't your patches be applied to latest XFree snapshot? They synchronize with
DRI project time-to-time..      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From michel@...  2003-07-11 19:12 -------
Well, I'd like to know if it actually works before checking it in. :) But if
nobody tests it, I'll probably do it anyway after a while...

DRI CVS is only merged into XFree86 CVS about once before a release, the merge
for 4.4.0 was earlier. You can try applying the prerequisite patch to XFree86
CVS as well, but I have no idea how well or badly it applies.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From psycho_dad1@...  2003-08-11 12:38 -------
I do not know what the effects of changing the line
#define __HAVE_SHARED_IRQ       1  to
#define __HAVE_SHARED_IRQ       0 
in /where your sources are/
/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel 
radeon.h with 2.6.x -kernels are, i never tested it.
I can only confirm that it solves the problem of the freezing when radeon.o is
loaded together with a module that takes IRQ 11 for kernel 2.4.22 patched with 
http://www.sonarnerd.net/linux/2.4.22-jl15.patch.bz2 and probably some other
kernels from the 2.4.x series on the Amilo A with latest bios.

Thomas Riedel      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From psycho_dad1@...  2003-08-11 12:58 -------
And its not only that the computer doesnt freeze, the device on IRQ 11 (the
ethernet for me) does its job (connecting me to the internet) at the same time
when I use 3D applications.

Thomas      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

mharris@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |NOTABUG




------- Additional Comments From mharris@...  2003-09-11 05:36 -------
This "metabug" is a horrible abuse of the purpose of bugzilla, which is
to track defects.  This bug report has turned into both a virtual mailing
list of sorts, and a web based tech support forum.  Neither of which belong
in bugzilla, so I'm closing this.

Please continue these discussions on dri-devel or dri-users mailing list
instead.  If neither of those mailing lists is considered good enough,
I will gladly create a brand new mailing list on freedesktop.org to host
the future discussion of this development, and technical support for people
having problems with it.

Please don't abuse bugzilla for what it wasn't intended for.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

michel@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOTABUG                     |




------- Additional Comments From michel@...  2003-09-11 08:06 -------
> This "metabug" is a horrible abuse of the purpose of bugzilla, which is
> to track defects.  

If that's true, what's the 'enhancement' severity for?

> This bug report has turned into both a virtual mailing list of sorts, and a
> web based tech support forum. 

I disagree. The only problem is that people tend to throw in random problems not
related directly to the bug's topic. They should file new bugs about those instead.

> Neither of which belong in bugzilla, so I'm closing this.

What a wonderful timing, after all this time, now that it's almost done...

> Please continue these discussions on dri-devel or dri-users mailing
> list instead.  

Well, this is already aired on dri-devel. :) In particular, the gory technical
details have always been discussed there, not here.

> If neither of those mailing lists is considered good enough, I will gladly
> create a brand new mailing list on freedesktop.org to host the future
> discussion of this development, and technical support for people having
> problems with it.

No such thing is needed, thank you. I think bugzilla is perfectly well suited
for this kind of thing, some people just need to get over the notion of a 'bug'
being something evil that needs to be gotten rid of ASAP, no matter how.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From mharris@...  2003-09-11 09:22 -------
> If that's true, what's the 'enhancement' severity for?

Requesting enhancements.  I don't consider a 220 comment bug report necessary
for requesting an enhancement though.  It's a huge morass of crap in here,
most of which is unrelated to the actual request.  Developmental discussion
should be in a mailing list, and tech support problems and similar in mail
also, not in a bug report.

>> This bug report has turned into both a virtual mailing list of sorts, and a
>> web based tech support forum. 
>
>I disagree. The only problem is that people tend to throw in random problems
>not related directly to the bug's topic. They should file new bugs about those
>instead.

There's 220 comments!  Read through this bug report and try to find useful
relevant bits and filter it from the junk!  It's next to impossible.  The
majority of content is mailing list type of content, not bug report data.

>> Neither of which belong in bugzilla, so I'm closing this.
>
>What a wonderful timing, after all this time, now that it's almost done...

It's irritated me for quite a while actually, and I've mentioned that
before.

>> Please continue these discussions on dri-devel or dri-users mailing
>> list instead.  
>
>Well, this is already aired on dri-devel. :) In particular, the gory technical
>details have always been discussed there, not here.

Yes, but this is a black morass nonetheless.


>No such thing is needed, thank you. I think bugzilla is perfectly well suited
>for this kind of thing, some people just need to get over the notion of a 'bug'
>being something evil that needs to be gotten rid of ASAP, no matter how.

If bugzilla is full of all kinds of crap, that makes it hard for people to
find real actual bug reports.  Bugzilla was set up to track bugs.

You've reopened it again, fair enough.  I'll leave it at that then, and
respectfully agree to disagree.  No harm done.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From eta@...  2003-10-11 22:31 -------
Created an attachment (id=807)
 --> (http://bugs.xfree86.org/attachment.cgi?id=807&action=view)
patch to add Radeon IGP PCI IDs to DRI CVS's DRM.

Can someone take a look, does this look like the right set of PCI IDs?      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      




------- Additional Comments From j.w.bijlsma@...  2003-11-11 03:40 -------
I'm having the same problem some other people are reporting here, where the 
Radeon DRM tries to 'share' an IRQ with another device (in my case IRQ9, which 
is also taken by usb-ohci). After a while of 3D work my USB mouse completely 
stops responding, but 3D acceleration still works ok (PS/2 mouse as well). 
This is on an IGP320M /w patches 540 & 541, XFree-4.3.99.9. 
 
Changing to __HAVE_SHARED_IRQ 0 in radeon.h solves the problem for me. 
 
I'm using 2.6.0-test3-bk1 here (went back from 2.6.0-test9 because of the same 
problem, it should probably work with test9 right now). I don't remember 
having any problems with the patch on 2.4.x or 2.5.x kernels. 
 
This is my /proc/interrupts (after disabling shared IRQ's). The weird thing is 
that the radeon DRM always wants IRQ9, as opposed to IRQ11 as reported by 
others (never had any problems with networking while using 3D): 
 
           CPU0        
  0:    1217537          XT-PIC  timer 
  1:       3262          XT-PIC  i8042 
  2:          0          XT-PIC  cascade 
  5:        818          XT-PIC  ALI 5451 
  8:          2          XT-PIC  rtc 
  9:      19162          XT-PIC  acpi, ohci-hcd 
 11:       3985          XT-PIC  eth0 
 12:      14204          XT-PIC  i8042 
 14:      12230          XT-PIC  ide0 
 15:          6          XT-PIC  ide1 
NMI:          0  
ERR:          0 
 
XFree says: 
 
(II) RADEON(0): [drm] failure adding irq handler, there is a device already 
using that irq 
[drm] falling back to irq-free operation 
(II) RADEON(0): [drm] Initialized kernel agp heap manager, 5111808 
(II) RADEON(0): Direct rendering enabled 
 
What effect does it have running without IRQ's, what is wrong with IRQ 
sharing, and why (???) does the radeon module not just grab IRQ10 for example 
(I think it takes IRQ10 in Windows). 
 
	Wouter Bijlsma       
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=314      
      

michel@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stefanonafets@...




------- Additional Comments From michel@...  2003-16-11 07:04 -------
*** Bug 875 has been marked as a duplicate of this bug. ***      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From mcgrof@...  2003-12-04 00:34 -------
Michel,

I've tested your patch with the latest CVS co of the DRI trunk. You forgot a few
PCI IDs for the radeon kernel module. Anholt supplied the patch. Here you can
find the merged patch:

http://prism54.org/~mcgrof/dri-igp/mcgrof-radeon-igp.diff

This will use r200_dri.so for 3D accel for RS300 Family only. I believe you
forgot to add the RS100, RS200 and RS250 families to a specific radeon 3d
library. By using the patch above by default RS100, RS200 and RS250 Family
Chipsets will default to using radeon_dri.so I tried the above patch and
radeon.o loaded fine but running glxgears hangs my box (RS200 0x4337). I tried
with and without TCL with the same result.

Seeing that you had added RS300 Family to use r200_dri.so, I put together a
patch that makes all IGP Chipset families use it to test if that would do it for
me. The patch is here:

http://prism54.org/~mcgrof/dri-igp/mcgrof-radeon-igp-v2.diff

Unfortunatley this also hung my box both with and without TCL.

Can someone tell me which DRI 3d library is supposed to be used for each Family
Chipset? I can add them to the corresponding library myself and provide a patch.
Or be my guest and supply a patch yourself ;)

Perhaps the layout is like this:
R100(radeon_dri.so): RS100, RS200
R200(r200_dri.so): RS250, RS300

Fixes or hints as to how to proceed is appreciated. I'm willing to help as much
as I can to get IGP 3D support commited into DRI CVS.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From rscheidegger@...  2003-12-04 07:27 -------
(In reply to comment #224)

RS100, RS200 and RS250 are radeon based (more specifically, their graphic core
is very similar to RV100, the radeon VE/7000 (1 pixel pipeline, no TCL)).
The RS300 (and the supposed RS380 for AMD CPU's, though this thing seems to have
vanished completely and may never exist) is R200 based (more exactly, it's a
cut-down RV280, only 2 pixel pipelines instead of four and vertex shader / TCL
removed).       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From espinosa@...  2003-12-04 13:55 -------
None of the given patches is applicable to newest XFree snapshot 4.3.99.901 :(
DRI was merged with X tree.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From lainknives@...  2003-12-05 12:12 -------
(In reply to comment #163)
> IGP320M works perfectly for me in 2.4.x using the modules from XFree86 CVS 
> (and XFree86 itself from CVS) with patch 502; using the same DRI source [with 
> slight adaptions to make it compile due to the remap_page_range API change] 
> with 2.6.0-test5-mm1 works for 2D, using 3D fails with 
>  
> [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held 
> [drm:radeon_unlock] *ERROR* Process 1482 using kernel context 0 
>  
>  

I have this exact same problem when trying to use DRI, in addition to this
having to do with AGP, so says dmesg: 

Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Unsupported Ati chipset (device id: cbb2)

This is a report from XFree86.0.log:

(WW) RADEON(0): [agp] AGP not available.

I am using the 2.6 kernel series(test10-mm1 to be specific) and the patch
attatchment #723 with XFree 4.3.99.16. The patch applies fine. I was told this
could be an IRQ issue with the Sony Vaio(mine is a vaio FRV27) so I disabled irq
sharing in radeon.h before making the module and still no go. I was ALSO told
that it would help to compile ati-agp and agpgart built into the kernel and that
didn't work either. I'm using ACPI. Any ideas on this? The chip is a 340m. Thanks.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From twalter@...  2003-12-05 13:40 -------
(In reply to comment #226) 
> None of the given patches is applicable to newest XFree snapshot 
4.3.99.901 :( 
> DRI was merged with X tree. 
 
I *really* wish I had read this comment *prior* to trying out the latest 
snapshot! ;)  When I try and apply the current radeon snapshot patch against 
this tree, about 50% of it completes (but xfree compilation craps out exactly 
at that module.)  3D acceleration worked (~380fps in GLXGEARS with USLEEPS=1 
and NO_IRQ=1, 4.3.99.11 + Hui's patch, 2.4.22-ac4) but wasn't exactly speedy 
(which is fine as I really only need OpenGL occasionally.)  I've tried walking 
through the patch to see what's going on but it's beyond my capacity to 
follow.  Is it always borked in the same spot when the xfree rev changes?          
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

twalter@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |twalter@...


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From bero@...  2003-12-05 13:43 -------
Created an attachment (id=860)
 --> (http://bugs.xfree86.org/attachment.cgi?id=860&action=view)
Updated patch to apply with XFree86 CVS as of 2003/12/05

I'm attaching a patch that applies cleanly to the current XFree86 CVS tree;
it's 100% untested though because I don't have test hardware ATM.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

bero@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #860 is|0                           |1
           obsolete|                            |




------- Additional Comments From bero@...  2003-12-05 14:08 -------
Created an attachment (id=861)
 --> (http://bugs.xfree86.org/attachment.cgi?id=861&action=view)
Fixed version of patch 860

Ok, this didn't even compile, here's one that does       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From bero@...  2003-12-05 16:56 -------
Created an attachment (id=862)
 --> (http://bugs.xfree86.org/attachment.cgi?id=862&action=view)
This one actually works

There was another bug in 861; this one compiles and X starts up (no further
testing done yet)       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From chris@...  2003-12-05 19:59 -------
(In reply to comment #163)
> IGP320M works perfectly for me in 2.4.x using the modules from XFree86 CVS 
> (and XFree86 itself from CVS) with patch 502; using the same DRI source [with 
> slight adaptions to make it compile due to the remap_page_range API change] 
> with 2.6.0-test5-mm1 works for 2D, using 3D fails with 
>  
> [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held 
> [drm:radeon_unlock] *ERROR* Process 1482 using kernel context 0 
>  
>  

That sounds like the exact same problem I was having with the mach64 when I was
booting a 2.4 kernel with the software suspend patch applied -- perhaps it would
be advantageous to see if software suspend is enabled in your 2.6 kernel and if
it is try re-compiling with it disabled?       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From mcgrof@...  2003-12-05 22:49 -------
OK Well I've fixed it for RS200. :-D My patch is intended to fix RS100, RS200,
RS250. I can only test RS200 cards since that is what I have. Can some of you
test the others and post results? Note: this patch is for DRI CVS xc trunk. If
you don't have it, it's simple as:

http://prism54.org/~mcgrof/dri-igp/get_dri_xfree_install.txt

My Version 3 patch can be found here:
http://prism54.org/~mcgrof/dri-igp/mcgrof-radeon-igp-v3.diff

Here's a a list of cards we need tested:

0x1002 0x4136 - "ATI Radeon RS100 IGP 320M"
0x1002 0x4137 - "ATI Radeon RS200 IGP"
0x1002 0x4237 - "ATI Radeon RS250 IGP"
0x1002 0x4336 - "ATI Radeon RS100 Mobility U1"
0x1002 0x4337 - "ATI Radeon RS200 Mobility IGP 340M" - TESTED OK!
0x1002 0x4437 - "ATI Radeon RS250 Mobility IGP"
0x1002 0x5834 - "ATI Radeon RS300 Mobility IGP"
0x1002 0x5835 - "ATI Radeon RS300 IGP"
0x1002 0x5836 - "ATI Radeon RS300 IGP"
0x1002 0x5837 - "ATI Radeon RS300 IGP"

My benchmarks: (1024x768 Resolution @ 16bpp)
glxgears default window size: 483 FPS
glxgears fullscreen size: 71 FPS
glxgears minimized to the size of a thumb: 3300 FPS

(Get the rest from mesademos (debian as "mesademos" package))
tunnel fullscreen size: 61 FPS
fire fullscreen size: 25.6 FPS
--

I don't know why but full sreen apps like tuxracer, armagetron look as if the
screen shifted to the side or so... there is only like 1/6 of a screen you can
actually see stuff. The rest is blurry with lines going straight down. If you
know why this may be please let me know.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From andreas.zuber@...  2003-12-06 11:13 -------
(In reply to comment #233)

Thanks for your patch Howto, this is important for testing.

Some Weeks I tested Huy's patches, now I have tested your patch with the DRI
cvs. The Kernel and the XF86Config is the same.

Hardware:
ATI Radeon RS200 Mobility IGP 340M (I know this is allready tested)

Resolution 1400x1050

The performance is with both patches the same -> glxgears ~360FP (Isn't realy
usable for games). With Huy's Patches there wer allways some Flares on the
screen with some applications (mplayer, pingus). With the new patches the Flares
are away and the Switch between X and a tty is much faster as before.
Unfortunately now I can't change the resolution of the X-Server. I allways get a
blackscreen if i try to change the resolution with ctrl alt +/- or if an
application trys to switch.

Thanks for your work and sorry for my bad english. :-)

Andreas Zuber       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

andreas.zuber@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andreas.zuber@...


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From mike_magua@...  2003-12-08 00:18 -------
hi i get an error message when i do: make -f Makefile.linux radeon.o

it sais that it cannot find a kernel config file...?       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From mcgrof@...  2003-12-08 01:13 -------
Michael,

you want to have a kernel compiled and your ln -s /usr/src/linux /path/kernel.
Or I believe you can also use TREE=/path/kernel for the make.

--

I just tested Quake III Arena and it works just great.
640 x 480 @ 16 bpp: 
Average: 70 FPS
Busy areas: as low as 45 FPS
Looking at pitch black-sky: 93 FPS

bzflag runs perfect @ 1024x768.

There seems to be a persisting problem @ 1024x768 @ 16bpp with some games. The
only problem is the 1/6 of screen viewable. Not yet sure what it is. If someone
may have an idea of what may be causing this please post.

       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From mike_magua@...  2003-12-08 01:45 -------
Quote:

Michael,

you want to have a kernel compiled and your ln -s /usr/src/linux /path/kernel.
Or I believe you can also use TREE=/path/kernel for the make.
------------------------------------------------------------------------------

Could you explain that a bit more to me? I'm currently using Fedora Core 1.  
I'm still quite new to Linux, so what must i type before i do the make -f 
Makefile.linux radeon.o command?

If you could just show me a bit more I'd really appreciate it :))

Regards,

Michael.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From psycho_dad1@...  2003-12-08 08:19 -------
The Patch http://bugs.xfree86.org/attachment.cgi?id=723&action=view
with XFree-4.3.99.16 works fine, thank you. Then I get this in
/var/log/XFree86.0.log:

drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmGetBusid returned ''

But now tried to patch XFree86-4.3.99.901 with
http://bugs.xfree86.org/attachment.cgi?id=862&action=view
but I get no 3D.


The log with 4.3.99.901 shows that drmOpenDevice fails:
 
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed

and so on

At the patching one hunk in 
lib/GL/mesa/src/drv/r200/radeon_screen.c fails.
I have a Radeon IGP 320M chip.

Thomas Riedel       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From jbremer@...  2003-12-08 11:28 -------
(In reply to comment #231)
> Created an attachment (id=862)
 --> (http://bugs.xfree86.org/attachment.cgi?id=862&action=view)
> This one actually works
> 
> There was another bug in 861; this one compiles and X starts up (no further
> testing done yet)

This patch (862) does not work on an IGP320M. The screen initialize but the
freezes the complete machine very hard. The first 100 lines or so get really
distorted while the rest seems to be OK. Patch 723 worked OK here. Also dri_cvs
with latest patch works fine.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From mike_magua@...  2003-12-08 14:26 -------
Hi.

Can someone still exp[lain to me what to do if i get the message that it cannot 
find a kernel config file after i run make -f Makefile.linux radeon.o?

I have the IGP 340M.  Im still new to Linux as I said earlier, so if someone 
could just tell me what command to type to get it all working correctly?  I'm 
using Fedora Core 1.

Much appreciated,

Michael.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From agd5f@...  2003-12-08 14:34 -------
you need to have a copy of the kernel source available so that the kernel module
can be built (it needs to know how you've configured the kernel and some of the
headers).  if you are using an custom kernel you need a copy of your source in
/usr/src/linux or if you are using an rpm based distro, you need to install the
kernel source code rpm.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From dennis@...  2003-12-08 16:34 -------
(In reply to comment #239)
> (In reply to comment #231)
> > Created an attachment (id=862)
 --> (http://bugs.xfree86.org/attachment.cgi?id=862&action=view)
> > This one actually works
> > 
> > There was another bug in 861; this one compiles and X starts up (no further
> > testing done yet)
> 
> This patch (862) does not work on an IGP320M. The screen initialize but the
> freezes the complete machine very hard. The first 100 lines or so get really
> distorted while the rest seems to be OK. Patch 723 worked OK here. Also 
dri_cvs
> with latest patch works fine.

I also have IGP 320M.
 4.3.99.16 -> patch succeeded but compile failed
 4.3.99.901 -> patch succeeded, compile succeeded.

Module can be inserted into kernel, XFree works but dri does not work.
Also, if I try glxgears I get a segmentation fault.  Happy to provide more 
information if requested.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

bero@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #861 is|0                           |1
           obsolete|                            |


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From mike_magua@...  2003-12-09 12:51 -------
ok people, i have uninstalled Fedora as it is very buggy, I now installed SuSE 
9 and so far i am much happier with it, it picks up my igp 340m but doesnt have 
3d available, only 2d works, later on tonight at work i will go through 
patching process and hopefully i will have a much successfull install. Does 
anybody else here use SuSE? if so please let me know!  Anyways, i will post 
later on and see everything...

I know that Xfree86 4.4 is going to be released soon? in this next release will 
there be drivers and 3d available for igp 340m or will we still have to patch?

Also, once i have patched dri etc, do i have to recompile my kernel? or can i 
just leave everything as is with /usr/src/linux?

speak soon,

Mixhael.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From psycho_dad1@...  2003-12-09 15:03 -------
Hi Michael,

I am on SuSE 9.0 with an IGP 320M. Installation process should be the same for
you. You have to patch and compile a kernel with IGP-Support and you have to
patch and compile the XFree86-Sources e.g.
(ftp://ftp.xfree86.org/pub/XFree86/develsnaps/XFree86-4.3.99.16.tar.bz2 with
http://bugs.xfree86.org/attachment.cgi?id=723&action=view).
There will be no 3D support in XFree86 4.4 because feature freeze is over.

Thomas       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

eta@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #807 is|0                           |1
           obsolete|                            |




------- Additional Comments From eta@...  2003-12-16 04:29 -------
(From update of attachment 807)
patch is obsolete because PCI IDs have been added.
       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From roguestar191@...  2003-12-17 00:17 -------
Dennis, I'm having the same problem. In my XFree86.0.log I see:
(II) RADEON(0): X context handle = 0x00000001
(II) RADEON(0): [drm] installed DRM signal handler
(II) RADEON(0): [DRI] installation complete
(WW) RADEON(0): Mismatched FB location. Incorrect version of DRM kernel driver is used.
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xdf8c7000 at 0x44144000
(II) RADEON(0): Direct rendering disabled
***************************************************************
I've compiled it correctly, I've done it 3 times to make sure.
I was also having problems before with the module GLCore loading. It seemed to work just fine before the way it was, but it wouldn't work until I changed it to GLcore (lowercase c). Dunno why this was.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From vies@...  2003-12-17 08:43 -------
(In reply to comment #246)
> Dennis, I'm having the same problem. In my XFree86.0.log I see:
> (II) RADEON(0): X context handle = 0x00000001
> (II) RADEON(0): [drm] installed DRM signal handler
> (II) RADEON(0): [DRI] installation complete
> (WW) RADEON(0): Mismatched FB location. Incorrect version of DRM kernel driver
is used.
> (II) RADEON(0): [drm] removed 1 reserved context for kernel
> (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xdf8c7000 at 0x44144000
> (II) RADEON(0): Direct rendering disabled
> ***************************************************************
> I've compiled it correctly, I've done it 3 times to make sure.
> I was also having problems before with the module GLCore loading. It seemed to
work just fine before the way it was, but it wouldn't work until I changed it to
GLcore (lowercase c). Dunno why this was.

I had the same problem, then I found we need to use the radeon dri module
provided with xfree and not the one provided with the kernel.
I tried it, but the new module can't open the device... in fact the device do
not exist and i don't know th minor and the major associated...
       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From roguestar191@...  2003-12-18 02:26 -------

>I had the same problem, then I found we need to use the radeon dri module
>provided with xfree and not the one provided with the kernel.
>I tried it, but the new module can't open the device... in fact the device do
>not exist and i don't know th minor and the major associated...

I did patch dri in the xfree86 4.3.99.16. used make -f Makefile.linux 
LINUXDIR=/usr/src/linux-2.6.0-test11
builds fine, I copy the module to /lib/modues/2.6.0-test11/blah blah replacing 
the old radeon.ko, load the module with insmod, start up xfree86, and no dri. 

I have an IGP320M.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

sigra@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sigra@...


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From ry00@...  2003-12-23 22:36 -------
im using IGP M340, DRI enabled.  
recently, I often get error "BadAlloc: not enough resource ....", then exit, when 
running mplayer to play a movie files. while in xine, it plays, but only audio with 
blank blue screen, no vidio. 
I experience this after applying patch XFree86-4.4-20031205-igp.patch to 
xfree-4.3.99.16. there is no such thing when i was running xfree-4.3.99.9 with the 
patch for 4.3.99.9 
 
any idea or pointer to what may be the cause ?        
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From agd5f@...  2003-12-23 23:35 -------
This is likey do to the fact that too much memory is reserved for 3D leaving
none for Xv.  This is due to the current memory manager situation in xfree86.  I
believe Alan Hourihane and others were looking to rework the 2D/3D memory
manager(s) post 4.4.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From ry00@...  2003-12-24 22:05 -------
which igp-kernel-patch does work for 2.4.23 ? 
 
Thanks,        
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From leinfidel@...  2003-12-25 01:14 -------
(In reply to comment #251)
> which igp-kernel-patch does work for 2.4.23 ? 
>  
> Thanks, 

I don't think either one does, I've tried the two above that were against 2.4.21
and even manually correcting the rejects, 2.4.23 will not compile.  Also it
looks like the content of those patches has largley been moved into 2.4.23
source, you can choose IGP support natively in 2.4.23. 

However in my case i have
ATI Technologies Inc Radeon IGP 340M
PCI: 00:00:0: chip 1002,cbb2 card 0000,0000 rev 02 class 06,00,00 hdr 00
in an hp pavilion ze5300 laptop.

agpgart would not detect this with the stock 2.4.23 kernel and IGP enabled, I
don't know if it truly doesn't support it yet or cbb2 identifier got overlooked.
 I *seemed* to have gotten around this by simply replacing "cab2" with "cbb2" in
these files.

drivers/char/agp/agp.h
drivers/pci/pci.ids

I did this because I noticed looking at the patches that the cbb2 is for RS_200M
and cab2 is for RS200, and those are both in the original pci.ids RS200/RS200M
AGP Bridge [IGP 340M]. I'm just guessing that the same code could be used for
both, and perhaps the cbb2 just didn't make it in.

In anycase everything seems to be working great at the moment,  I'm now
compiling the XFree snap shop with IGP patch.

Currently I'm using rpm based X 4.3 with an IGP patch and radeon driver, created
per the instructions here

http://www.rexursive.com/articles/linuxonhpze4201.html

Which has been working fine for sometime, but glxinfo shows with my current
config dri is not working, thus i'm compiling the x snapshot with igp patch.

Hope that's of some help, if you have cbb2 340M as well, only do what I did at
your own risk of course :)       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From vies@...  2003-12-27 04:44 -------
(In reply to comment #248)
> >I had the same problem, then I found we need to use the radeon dri module
> >provided with xfree and not the one provided with the kernel.
> >I tried it, but the new module can't open the device... in fact the device do
> >not exist and i don't know th minor and the major associated...
> 
> I did patch dri in the xfree86 4.3.99.16. used make -f Makefile.linux 
> LINUXDIR=/usr/src/linux-2.6.0-test11
> builds fine, I copy the module to /lib/modues/2.6.0-test11/blah blah replacing 
> the old radeon.ko, load the module with insmod, start up xfree86, and no dri. 
> 
> I have an IGP320M.

I wonder if someone made the dri work with an IGP320...       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From ry00@...  2003-12-29 23:41 -------
DRI was enabled when i aplied this patch XFree86-4.4-20031205-igp.patch to 
xfree.4.3.99.16, but when the same patch i applied to XFree86-4.3.99.902 , there is 
no DRI enabled. It's complaining of not able open the drm device under /dev  and I 
couldn't find any relevant change in the change.log that may be the problem. 
 
so i did some experiment modprobing the old radeon.o, lsmod shows that agpgart is 
used. but when i modprobe the new radeon.o , agpgart is unused.   
 
what may be the problem ?        
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

z3p@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |z3p@...


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From andre@...  2004-01-02 21:44 -------
Well, to answer a previous question, yes, I do have 3D running (well) on an 
IGP 320 chipset (Compaq 2100 with ATI Radeon Mobility). Running an unpatched 
Kernel 2.6.0 (been running since -test8) and Xfree 4.3.99.16 with one of the 
patches above for the radeon.ko module. No problems at all. 
 
Seems like development has slowed down for this patch? Hope it will make it 
into Xfree86 4.4 ? 
 
This might be unrelated, but do any of the driver developers know how one 
could enable the TV-out on this card ? 
 
Thanks (again) for you hard work guys! 
 
Cheers, 
  André        
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From vies@...  2004-01-04 08:47 -------

> This might be unrelated, but do any of the driver developers know how one 
> could enable the TV-out on this card ? 
>  
> Thanks (again) for you hard work guys! 
>  
> Cheers, 
>   André 

hi,

I found this project that enable TV-out on old radeon and mach64 cards.
You can use it on an ati igp by forcing the radeon or the mach64 option.

you can find the project here :
http://www.stud.uni-hamburg.de/users/lennart/projects/atitvout/
       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

eta@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From eta@...  2004-01-05 18:23 -------
Patches for IGP support have been committed to Mesa and DRI CVS.  Please update
to the very latest of those and the DRM before submitting additional bug
reports.  Future bug reports on IGP issues should be filed as new bugs based on
with the code mentioned above and not as followups to this bug report.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From gustavo.michels@...  2004-01-06 15:24 -------
(In reply to comment #257)
> Patches for IGP support have been committed to Mesa and DRI CVS.  Please 
update
> to the very latest of those and the DRM before submitting additional bug
> reports.  Future bug reports on IGP issues should be filed as new bugs based 
on
> with the code mentioned above and not as followups to this bug report.

Sorry for my extremely dumb question, but would this be the right way to get the 
DRI CVS?

cvs checkout dri xc
       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From michael@...  2004-01-06 16:21 -------
(In reply to comment #258)
> Sorry for my extremely dumb question, but would this be the right way to get 
> the DRI CVS?
> cvs checkout dri xc

If you want the DRI CVS have a look at

http://dri.sourceforge.net/cgi-bin/moin.cgi/Download

It explains the whole process fairly well.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From bruce.c@...  2004-01-06 19:42 -------
(In reply to comment #252)
> (In reply to comment #251)
> > which igp-kernel-patch does work for 2.4.23 ? 
> >  
> > Thanks, 
> 
> I don't think either one does, I've tried the two above that were against 2.4.21
> and even manually correcting the rejects, 2.4.23 will not compile.  Also it
> looks like the content of those patches has largley been moved into 2.4.23
> source, you can choose IGP support natively in 2.4.23. 
> 
> However in my case i have
> ATI Technologies Inc Radeon IGP 340M
> PCI: 00:00:0: chip 1002,cbb2 card 0000,0000 rev 02 class 06,00,00 hdr 00
> in an hp pavilion ze5300 laptop.
> 
> agpgart would not detect this with the stock 2.4.23 kernel and IGP enabled, I
> don't know if it truly doesn't support it yet or cbb2 identifier got overlooked.
>  I *seemed* to have gotten around this by simply replacing "cab2" with "cbb2" in
> these files.
> 
> drivers/char/agp/agp.h
> drivers/pci/pci.ids
> 
> I did this because I noticed looking at the patches that the cbb2 is for RS_200M
> and cab2 is for RS200, and those are both in the original pci.ids RS200/RS200M
> AGP Bridge [IGP 340M]. I'm just guessing that the same code could be used for
> both, and perhaps the cbb2 just didn't make it in.
> 
> In anycase everything seems to be working great at the moment,  I'm now
> compiling the XFree snap shop with IGP patch.
> 
> Currently I'm using rpm based X 4.3 with an IGP patch and radeon driver, created
> per the instructions here
> 
> http://www.rexursive.com/articles/linuxonhpze4201.html
> 
> Which has been working fine for sometime, but glxinfo shows with my current
> config dri is not working, thus i'm compiling the x snapshot with igp patch.
> 
> Hope that's of some help, if you have cbb2 340M as well, only do what I did at
> your own risk of course :)


In case it isn't obvious to others (it wasn't obvious to me when I read the
above comments), the following approach can be used to get DRI working on a
2.4.23 kernel:

1) Configure the kernel for ATI IGP chipset support (CONFIG_AGP_ATI=y) and for
ATI Radeon module support under DRM 4.1 drivers (CONFIG_DRM_RADEON=m).

2) Build the kernel.

3) If you don't already have it, get and build a RadeonIGP patched version of
XFree86 CVS (4.3.99.9 or greater).

4) Find the xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel branch of
the XFree86 tree (from above) and do a make -f Makefile.linux
LINUXDIR=/usr/src/linux-2.4.23 (or whatever your 2.4.23 kernel source location is).

5) Copy the radeon.o file produced in the branch in step 4) to
/lib/modules/2.4.23/kernel/drivers/char/drm.  This replaces the radeon module
installed by the 2.4.23 kernel.

6) Reboot or do whatever to restart your xserver and replace the original kernel
radeon driver module with the new one.

This procedure is basically the same as what most of us have done previously
with 2.4.20 or 2.4.21 kernels, except that we don't have to patch the 2.4.23
kernel for agpgart support.  I'm using XFree86 4.3.99.9 with a Radeon IGP 340M
on an HP ze4100 system.  This procedure should work with later XFree86 CVS
snapshots, probably with later kernels, and presumably with other Radeon IGP
hardware.  I encourage others to test this out and report back.  

I've identified a few lines that I think need to be added/changed in the 2.4.23
kernel source for radeon_cp.c in order for the stock kernels to work without
need for building a radeon.o module in the XFree86 tree.  If I can get that to
work, I'll post a patch here.

Bruce       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

caraffi@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Additional Comments From caraffi@...  2004-02-16 05:42 -------
I have installed XFree 4.3.99.16 patched and kernel 2-4-23-pre9, following Bruce
instructions. The Acceleration started to work, for example Tuxracer works fine.
But in the application I am working at, we use some OpenGL windows and it always
happens that after two or three frames the output of one window is showed in ALL
the windows, making the acceleration unuseful. If I shut down the acceleration,
the program work properly (only very slow). I have compiled the program with
efence, and run it with ddd, here it is what I obtain:

Yesterday:

Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 32771 (LWP 18645)]
0x42499658 in _mesa_test_os_sse_exception_support () from
/usr/X11R6/lib/modules/dri/radeon_dri.so
(gdb) stepi
0x4249965b in _mesa_test_os_sse_exception_support () from
/usr/X11R6/lib/modules/dri/radeon_dri.so
(gdb) stepi
0x4249965f in _mesa_test_os_sse_exception_support () from
/usr/X11R6/lib/modules/dri/radeon_dri.so
(gdb) stepi
0x42499660 in _mesa_test_os_sse_exception_support () from
/usr/X11R6/lib/modules/dri/radeon_dri.so
(gdb) stepi
0x424993b2 in check_os_sse_support () from /usr/X11R6/lib/modules/dri/radeon_dri.so
(gdb) step
Single stepping until exit from function check_os_sse_support,
which has no line number information.
0x424994f0 in _mesa_init_all_x86_transform_asm () from
/usr/X11R6/lib/modules/dri/radeon_dri.so
(gdb) step
Single stepping until exit from function _mesa_init_all_x86_transform_asm,
which has no line number information.
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  20 (X_GetProperty)
  Resource id in failed request:  0x2200002
  Serial number of failed request:  124
  Current serial number in output stream:  124

Program exited with code 01.



then program crashes. 




Today: (I don't know exactly what I changed, maybe I fixed something with GL
Libraries, I am sure now I am using the right ones)

[Switching to Thread 32771 (LWP 8713)]
0x424f1658 in _mesa_test_os_sse_exception_support () from
/usr/X11R6/lib/modules/dri/radeon_dri.so
(gdb) step
Single stepping until exit from function _mesa_test_os_sse_exception_support,
which has no line number information.
0x424f13b2 in check_os_sse_support () from /usr/X11R6/lib/modules/dri/radeon_dri.so
(gdb) step
Single stepping until exit from function check_os_sse_support,
which has no line number information.
0x424f14f0 in _mesa_init_all_x86_transform_asm () from
/usr/X11R6/lib/modules/dri/radeon_dri.so
(gdb) step
Single stepping until exit from function _mesa_init_all_x86_transform_asm,
which has no line number information.
disabling TCL support
New OGLW Created: 1-1


and then program blocks waiting until GDB gets ready (it never happens)
If I don'use ddd, the program continue to work but not properly (as I said, in
no time one sequence of images enters in all the windows) and exits (when asked
to do that) with a segmentation fault. Our program works with different threads,
one of them executes elaborations, and another draws the result of the
elaboration in Open GL Windows. We use libglut functions (I have installed the
last one, 3.7.1). Lines are drawn in the right windows, but images are not. Our
program works properly in all the other accelerated computers.
If you need other informations just ask.
Thank you!
Claudio       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

caraffi@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |caraffi@...


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

michel@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From michel@...  2004-02-16 13:10 -------
Those problems are off topic for this bug. If there are problems with current
DRI CVS (where IGP support has been properly integrated), please open another
bug or post to the dri-devel mailing list.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

mhall@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Additional Comments From mhall@...  2004-02-16 18:52 -------
I have tried patch 862 and the DRI kernel module from the XC tree. I used
developer's snapshot 4.3.99.16. I am using an eMachines M5310 with Radeon IGP
320M Mobility U1 chipset.

DRI appears to open successfully, but glxinfo claims DRI is not active, and
glxgears fails with a segmentation fault.

Can someone tell me what I missed here? This is very frustrating, I have spent
hours compiling and installing different builds of X to try to get this to work
and it just won't.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From jasonthomasdolan@...  2004-02-17 00:05 -------
I have your same laptop and have everything working perfectly:

Linux 2.6.2 w/706, ATI chipset support, Radeon DRM support, no modules
XFree86-4.3.99-14 w/723

In /etc/profile:
export RADEON_NO_IRQS=1
export RADEON_NO_USLEEPS=1

Email me at jasonthomasdolan@... if you'd like my 2.6.2 .config.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

twalter@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|twalter@... |


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

bolzano@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bolzano@...


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From boris_s@...  2004-03-01 17:35 -------
Sorry if this is an incorrect place to ask.
since 4.4.0 is released, did 3D IGP patch for Xfree86  make it into the release
or not ?
The release notes explicitely state that Radeon IGP is only supported in 2D.

if it didn't make it, can somebody provide us with the correct patch for the
released version ?

Thanks       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From agd5f@...  2004-03-01 18:02 -------
(In reply to comment #265)
> Sorry if this is an incorrect place to ask.
> since 4.4.0 is released, did 3D IGP patch for Xfree86  make it into the release
> or not ?
> The release notes explicitely state that Radeon IGP is only supported in 2D.
> 
> if it didn't make it, can somebody provide us with the correct patch for the
> released version ?

IGP support did not make it into 4.4.  IGP support is available in the DRI tree.
 see this page for access to the source from cvs and binary snapshots:
http://dri.sourceforge.net/cgi-bin/moin.cgi/Download


> 
> Thanks

       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From jasonthomasdolan@...  2004-03-03 10:15 -------
As there are still people having a hard time getting DRI working for their IGP
cards, and some of the XFree86 folks are complaining that this bug report is an
abuse of Bugzilla, I have created a very brief How-To for the Radeon IGP
available at http://jaydolan.com.  I'll gladly incorporate any additions and/or
revisions you see fit, and I do not mind answering any questions via email that
I can.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From lilnana@...  2004-03-05 22:59 -------
Created an attachment (id=1130)
 --> (http://bugs.xfree86.org/attachment.cgi?id=1130&action=view)
Enable 3D acceleration in XFree86-4.4.0

I have managed to port attachment #723 work in the new version of
XFree86-4.4.0.	3D acceleration works if you patch your kernel with the
relevant version of the IGP patch.

I have also compiled rpms for Redhat 9 and Fedora Core 1 and Fedora Core 2
(test version). Since I have no where to put them for general download, feel
free to email me or if someone has space on the web, I can upload them there
for all you

My Current X log:
XFree86 Version 4.4.0 (Custom Build: 4.4.0-3)
Release Date: 29 February 2004
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.3-4.rc2 i686 [ELF] 
Current Operating System: Linux pavilion.home.org 2.6.3-4.rc2 #1 SMP Thu Mar 4
07:43:42 EST 2004 i686
Build Date: 06 March 2004
Changelog Date: 29 February 2004
Build Host: pavilion.home.org
 
	Before reporting problems, check http://www.XFree86.Org/
	to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.3-4.rc2 (root@...) (gcc version
3.3.3 20040216 (Red Hat Linux 3.3.3-2)) #1 SMP Thu Mar 4 07:43:42 EST 2004 F
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/XFree86.0.log", Time: Sat Mar	6 14:37:32 2004
(==) Using config file: "/etc/X11/XF86Config"
(==) ServerLayout "single head configuration"
(**) |-->Screen "Screen0" (0)
(**) |	 |-->Monitor "Monitor0"
(**) |	 |-->Device "Videocard0"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to "unix/:7100"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(WW) Open APM failed (/dev/apm_bios) (No such device)
(II) Module ABI versions:
	XFree86 ANSI C Emulation: 0.2
	XFree86 Video Driver: 0.7
	XFree86 XInput driver : 0.4
	XFree86 Server Extension : 0.2
	XFree86 Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	Module class: XFree86 Font Renderer
	ABI class: XFree86 Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	ABI class: XFree86 Video Driver, version 0.7
(++) using VT number 7

(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x8000900c, mode1Res1 = 0x80000000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1002,cab2 card 0000,0000 rev 02 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1002,7010 card 0000,0000 rev 00 class 06,04,00 hdr 01
(II) PCI: 00:02:0: chip 10b9,5237 card 103c,002a rev 03 class 0c,03,10 hdr 00
(II) PCI: 00:06:0: chip 10b9,5451 card 103c,002a rev 02 class 04,01,00 hdr 00
(II) PCI: 00:07:0: chip 10b9,1533 card 10b9,1533 rev 00 class 06,01,00 hdr 00
(II) PCI: 00:08:0: chip 10b9,5457 card 103c,002a rev 00 class 07,03,00 hdr 00
(II) PCI: 00:0a:0: chip 1217,6972 card 1c01,0000 rev 00 class 06,07,00 hdr 02
(II) PCI: 00:10:0: chip 10b9,5229 card 103c,002a rev c4 class 01,01,fa hdr 00
(II) PCI: 00:11:0: chip 10b9,7101 card 103c,002a rev 00 class 06,80,00 hdr 00
(II) PCI: 00:12:0: chip 100b,0020 card 3c08,5400 rev 00 class 02,00,00 hdr 00
(II) PCI: 01:05:0: chip 1002,4337 card 103c,002a rev 00 class 03,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
	[0] -1	0	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set)
(II) Bus 1 I/O range:
	[0] -1	0	0x00009000 - 0x000090ff (0x100) IX[B]
	[1] -1	0	0x00009400 - 0x000094ff (0x100) IX[B]
	[2] -1	0	0x00009800 - 0x000098ff (0x100) IX[B]
	[3] -1	0	0x00009c00 - 0x00009cff (0x100) IX[B]
(II) Bus 1 non-prefetchable memory range:
	[0] -1	0	0xe4300000 - 0xe43fffff (0x100000) MX[B]
(II) Bus 1 prefetchable memory range:
	[0] -1	0	0xec000000 - 0xefffffff (0x4000000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(II) PCI-to-CardBus bridge:
(II) Bus 2: bridge is at (0:10:0), (0,2,5), BCTRL: 0x0080 (VGA_EN is cleared)
(--) PCI:*(1:5:0) ATI Technologies Inc Radeon IGP 340M rev 0, Mem @
0xec000000/26, 0xe4300000/16, I/O @ 0x9000/8
(II) Addressable bus resource ranges are
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
	[1] -1	0	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
	[0] -1	0	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[1] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[2] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[3] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[4] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[5] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[6] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xe8000000 from 0xebffffff to
0xe7ffffff
(II) PCI Memory resource overlap reduced 0xe4005000 from 0xe4005fff to
0xe4004fff
(II) Active PCI resource ranges:
	[0] -1	0	0xe4004000 - 0xe4004fff (0x1000) MX[B]
	[1] -1	0	0xe4002000 - 0xe4002fff (0x1000) MX[B]
	[2] -1	0	0xe4000000 - 0xe4000fff (0x1000) MX[B]
	[3] -1	0	0xe4005000 - 0xe4004fff (0x0) MX[B]O
	[4] -1	0	0xe8000000 - 0xe7ffffff (0x0) MX[B]O
	[5] -1	0	0xe4300000 - 0xe430ffff (0x10000) MX[B](B)
	[6] -1	0	0xec000000 - 0xefffffff (0x4000000) MX[B](B)
	[7] -1	0	0x00002400 - 0x000024ff (0x100) IX[B]
	[8] -1	0	0x00002000 - 0x0000200f (0x10) IX[B]
	[9] -1	0	0x00001400 - 0x000014ff (0x100) IX[B]
	[10] -1 0	0x00001000 - 0x000010ff (0x100) IX[B]
	[11] -1 0	0x00009000 - 0x000090ff (0x100) IX[B](B)
(II) Inactive PCI resource ranges:
	[0] -1	0	0xe4001000 - 0xe4001fff (0x1000) MX[B]
(II) Active PCI resource ranges after removing overlaps:
	[0] -1	0	0xe4004000 - 0xe4004fff (0x1000) MX[B]
	[1] -1	0	0xe4002000 - 0xe4002fff (0x1000) MX[B]
	[2] -1	0	0xe4000000 - 0xe4000fff (0x1000) MX[B]
	[3] -1	0	0xe4005000 - 0xe4004fff (0x0) MX[B]O
	[4] -1	0	0xe8000000 - 0xe7ffffff (0x0) MX[B]O
	[5] -1	0	0xe4300000 - 0xe430ffff (0x10000) MX[B](B)
	[6] -1	0	0xec000000 - 0xefffffff (0x4000000) MX[B](B)
	[7] -1	0	0x00002400 - 0x000024ff (0x100) IX[B]
	[8] -1	0	0x00002000 - 0x0000200f (0x10) IX[B]
	[9] -1	0	0x00001400 - 0x000014ff (0x100) IX[B]
	[10] -1 0	0x00001000 - 0x000010ff (0x100) IX[B]
	[11] -1 0	0x00009000 - 0x000090ff (0x100) IX[B](B)
(II) Inactive PCI resource ranges after removing overlaps:
	[0] -1	0	0xe4001000 - 0xe4001fff (0x1000) MX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
	[0] -1	0	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[1] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[2] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[3] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[4] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[5] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[6] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
	[0] -1	0	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[1] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[2] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[3] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[4] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[5] -1	0	0xe4004000 - 0xe4004fff (0x1000) MX[B]
	[6] -1	0	0xe4002000 - 0xe4002fff (0x1000) MX[B]
	[7] -1	0	0xe4000000 - 0xe4000fff (0x1000) MX[B]
	[8] -1	0	0xe4005000 - 0xe4004fff (0x0) MX[B]O
	[9] -1	0	0xe8000000 - 0xe7ffffff (0x0) MX[B]O
	[10] -1 0	0xe4300000 - 0xe430ffff (0x10000) MX[B](B)
	[11] -1 0	0xec000000 - 0xefffffff (0x4000000) MX[B](B)
	[12] -1 0	0xe4001000 - 0xe4001fff (0x1000) MX[B]
	[13] -1 0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[14] -1 0	0x00000000 - 0x000000ff (0x100) IX[B]
	[15] -1 0	0x00002400 - 0x000024ff (0x100) IX[B]
	[16] -1 0	0x00002000 - 0x0000200f (0x10) IX[B]
	[17] -1 0	0x00001400 - 0x000014ff (0x100) IX[B]
	[18] -1 0	0x00001000 - 0x000010ff (0x100) IX[B]
	[19] -1 0	0x00009000 - 0x000090ff (0x100) IX[B](B)
(II) LoadModule: "dbe"
(II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a
(II) Module dbe: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	Module class: XFree86 Server Extension
	ABI class: XFree86 Server Extension, version 0.2
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a
(II) Module extmod: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	Module class: XFree86 Server Extension
	ABI class: XFree86 Server Extension, version 0.2
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension FontCache
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "fbdevhw"
(II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a
(II) Module fbdevhw: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 0.0.2
	ABI class: XFree86 Video Driver, version 0.7
(II) LoadModule: "glx"
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.a
(II) Module glx: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	ABI class: XFree86 Server Extension, version 0.2
(II) Loading sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a
(II) Module GLcore: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	ABI class: XFree86 Server Extension, version 0.2
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/X11R6/lib/modules/extensions/librecord.a
(II) Module record: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.13.0
	Module class: XFree86 Server Extension
	ABI class: XFree86 Server Extension, version 0.2
(II) Loading extension RECORD
(II) LoadModule: "freetype"
(II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a
(II) Module freetype: vendor="The XFree86 Project & the After X-TT Project"
	compiled for 4.4.0, module version = 2.1.0
	Module class: XFree86 Font Renderer
	ABI class: XFree86 Font Renderer, version 0.4
(II) Loading font FreeType
(II) LoadModule: "type1"
(II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a
(II) Module type1: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.2
	Module class: XFree86 Font Renderer
	ABI class: XFree86 Font Renderer, version 0.4
(II) Loading font Type1
(II) Loading font CID
(II) LoadModule: "dri"
(II) Loading /usr/X11R6/lib/modules/extensions/libdri.a
(II) Module dri: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	ABI class: XFree86 Server Extension, version 0.2
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/X11R6/lib/modules/linux/libdrm.a
(II) Module drm: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	ABI class: XFree86 Server Extension, version 0.2
(II) Loading extension XFree86-DRI
(II) LoadModule: "synaptics"
(II) Loading /usr/X11R6/lib/modules/input/synaptics_drv.o
(II) Module synaptics: vendor="The XFree86 Project"
	compiled for 4.2.0, module version = 1.0.0
	Module class: XFree86 XInput Driver
	ABI class: XFree86 XInput driver, version 0.3
(II) LoadModule: "radeon"
(II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o
(II) Module radeon: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 4.0.1
	Module class: XFree86 Video Driver
	ABI class: XFree86 Video Driver, version 0.7
(II) LoadModule: "ati"
(II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o
(II) Module ati: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 6.5.6
	Module class: XFree86 Video Driver
	ABI class: XFree86 Video Driver, version 0.7
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	Module class: XFree86 XInput Driver
	ABI class: XFree86 XInput driver, version 0.4
(II) LoadModule: "synaptics"
(II) Reloading /usr/X11R6/lib/modules/input/synaptics_drv.o
(II) ATI: ATI driver (version 6.5.6) for chipsets: ati, ativga
(II) R128: Driver for ATI Rage 128 chipsets:
	ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP),
	ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP),
	ATI Rage 128 Pro GL PA (PCI/AGP), ATI Rage 128 Pro GL PB (PCI/AGP),
	ATI Rage 128 Pro GL PC (PCI/AGP), ATI Rage 128 Pro GL PD (PCI),
	ATI Rage 128 Pro GL PE (PCI/AGP), ATI Rage 128 Pro GL PF (AGP),
	ATI Rage 128 Pro VR PG (PCI/AGP), ATI Rage 128 Pro VR PH (PCI/AGP),
	ATI Rage 128 Pro VR PI (PCI/AGP), ATI Rage 128 Pro VR PJ (PCI/AGP),
	ATI Rage 128 Pro VR PK (PCI/AGP), ATI Rage 128 Pro VR PL (PCI/AGP),
	ATI Rage 128 Pro VR PM (PCI/AGP), ATI Rage 128 Pro VR PN (PCI/AGP),
	ATI Rage 128 Pro VR PO (PCI/AGP), ATI Rage 128 Pro VR PP (PCI),
	ATI Rage 128 Pro VR PQ (PCI/AGP), ATI Rage 128 Pro VR PR (PCI),
	ATI Rage 128 Pro VR PS (PCI/AGP), ATI Rage 128 Pro VR PT (PCI/AGP),
	ATI Rage 128 Pro VR PU (PCI/AGP), ATI Rage 128 Pro VR PV (PCI/AGP),
	ATI Rage 128 Pro VR PW (PCI/AGP), ATI Rage 128 Pro VR PX (PCI/AGP),
	ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP),
	ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI),
	ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (PCI/AGP),
	ATI Rage 128 4X SF (PCI/AGP), ATI Rage 128 4X SG (PCI/AGP),
	ATI Rage 128 4X SH (PCI/AGP), ATI Rage 128 4X SK (PCI/AGP),
	ATI Rage 128 4X SL (PCI/AGP), ATI Rage 128 4X SM (AGP),
	ATI Rage 128 4X SN (PCI/AGP), ATI Rage 128 Pro ULTRA TF (AGP),
	ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP),
	ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?),
	ATI Rage 128 Pro ULTRA TU (AGP?)
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
	ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
	ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ (AGP/PCI),
	ATI Radeon Mobility M7 LW (AGP),
	ATI Mobility FireGL 7800 M7 LX (AGP),
	ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
	ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP320M (U1) 4336,
	ATI Radeon IGP330/340/350 (A4) 4137,
	ATI Radeon IGP330M/340M/350M (U2) 4337,
	ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon Mobility 7000 IGP 4437,
	ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
	ATI Radeon 9100 QM (AGP), ATI Radeon 8500 AIW BB (AGP),
	ATI Radeon 8500 AIW BC (AGP), ATI Radeon 7500 QW (AGP/PCI),
	ATI Radeon 7500 QX (AGP/PCI), ATI Radeon 9000/PRO If (AGP/PCI),
	ATI Radeon 9000 Ig (AGP/PCI), ATI FireGL Mobility 9000 (M9) Ld (AGP),
	ATI Radeon Mobility 9000 (M9) Lf (AGP),
	ATI Radeon Mobility 9000 (M9) Lg (AGP),
	ATI Radeon 9100 IGP (A5) 5834,
	ATI Radeon Mobility 9100 IGP (U3) 5835,
	ATI Radeon 9200PRO 5960 (AGP), ATI Radeon 9200 5961 (AGP),
	ATI Radeon 9200 5962 (AGP), ATI Radeon 9200SE 5964 (AGP),
	ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
	ATI Radeon Mobility 9200 (M9+) 5C63 (AGP), ATI Radeon 9500 AD (AGP),
	ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
	ATI FireGL Z1 AG (AGP), ATI Radeon 9700 Pro ND (AGP),
	ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9700 NF (AGP),
	ATI FireGL X1 NG (AGP), ATI Radeon 9600 AP (AGP),
	ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
	ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP),
	ATI FireGL RV360 AV (AGP), ATI Radeon Mobility 9600 (M10) NP (AGP),
	ATI Radeon Mobility 9600 (M10) NQ (AGP),
	ATI Radeon Mobility 9600 (M11) NR (AGP),
	ATI Radeon Mobility 9600 (M10) NS (AGP),
	ATI FireGL Mobility T2 (M10) NT (AGP),
	ATI FireGL Mobility T2 (M11) NV (AGP), ATI Radeon 9800SE AH (AGP),
	ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
	ATI FireGL X2 AK (AGP), ATI Radeon 9800PRO NH (AGP),
	ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP),
	ATI Radeon 9800XT NJ (AGP)
(II) Primary Device is: PCI 01:05:0
(--) Chipset ATI Radeon IGP330M/340M/350M (U2) 4337 found
(II) resource ranges after xf86ClaimFixedResources() call:
	[0] -1	0	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[1] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[2] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[3] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[4] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[5] -1	0	0xe4004000 - 0xe4004fff (0x1000) MX[B]
	[6] -1	0	0xe4002000 - 0xe4002fff (0x1000) MX[B]
	[7] -1	0	0xe4000000 - 0xe4000fff (0x1000) MX[B]
	[8] -1	0	0xe4005000 - 0xe4004fff (0x0) MX[B]O
	[9] -1	0	0xe8000000 - 0xe7ffffff (0x0) MX[B]O
	[10] -1 0	0xe4300000 - 0xe430ffff (0x10000) MX[B](B)
	[11] -1 0	0xec000000 - 0xefffffff (0x4000000) MX[B](B)
	[12] -1 0	0xe4001000 - 0xe4001fff (0x1000) MX[B]
	[13] -1 0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[14] -1 0	0x00000000 - 0x000000ff (0x100) IX[B]
	[15] -1 0	0x00002400 - 0x000024ff (0x100) IX[B]
	[16] -1 0	0x00002000 - 0x0000200f (0x10) IX[B]
	[17] -1 0	0x00001400 - 0x000014ff (0x100) IX[B]
	[18] -1 0	0x00001000 - 0x000010ff (0x100) IX[B]
	[19] -1 0	0x00009000 - 0x000090ff (0x100) IX[B](B)
(II) Loading sub module "radeon"
(II) LoadModule: "radeon"
(II) Reloading /usr/X11R6/lib/modules/drivers/radeon_drv.o
(II) resource ranges after probing:
	[0] -1	0	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[1] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[2] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[3] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[4] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[5] -1	0	0xe4004000 - 0xe4004fff (0x1000) MX[B]
	[6] -1	0	0xe4002000 - 0xe4002fff (0x1000) MX[B]
	[7] -1	0	0xe4000000 - 0xe4000fff (0x1000) MX[B]
	[8] -1	0	0xe4005000 - 0xe4004fff (0x0) MX[B]O
	[9] -1	0	0xe8000000 - 0xe7ffffff (0x0) MX[B]O
	[10] -1 0	0xe4300000 - 0xe430ffff (0x10000) MX[B](B)
	[11] -1 0	0xec000000 - 0xefffffff (0x4000000) MX[B](B)
	[12] -1 0	0xe4001000 - 0xe4001fff (0x1000) MX[B]
	[13] 0	0	0x000a0000 - 0x000affff (0x10000) MS[B]
	[14] 0	0	0x000b0000 - 0x000b7fff (0x8000) MS[B]
	[15] 0	0	0x000b8000 - 0x000bffff (0x8000) MS[B]
	[16] -1 0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[17] -1 0	0x00000000 - 0x000000ff (0x100) IX[B]
	[18] -1 0	0x00002400 - 0x000024ff (0x100) IX[B]
	[19] -1 0	0x00002000 - 0x0000200f (0x10) IX[B]
	[20] -1 0	0x00001400 - 0x000014ff (0x100) IX[B]
	[21] -1 0	0x00001000 - 0x000010ff (0x100) IX[B]
	[22] -1 0	0x00009000 - 0x000090ff (0x100) IX[B](B)
	[23] 0	0	0x000003b0 - 0x000003bb (0xc) IS[B]
	[24] 0	0	0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) RADEON(0): MMIO registers at 0xe4300000
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 0.1.0
	ABI class: XFree86 Video Driver, version 0.7
(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000

(II) RADEON(0): PCI bus 1 card 5 func 0
(**) RADEON(0): Depth 24, (--) framebuffer bpp 32
(II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(**) RADEON(0): Option "AGPFastWrite" "On"
(**) RADEON(0): Option "EnablePageFlip" "On"
(==) RADEON(0): RGB weight 888
(II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/X11R6/lib/modules/linux/libint10.a
(II) Module int10: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	ABI class: XFree86 Video Driver, version 0.7
(II) RADEON(0): initializing int10
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
(--) RADEON(0): Chipset: "ATI Radeon IGP330M/340M/350M (U2) 4337" (ChipID =
0x4337)
(--) RADEON(0): Linear framebuffer at 0xec000000
(II) RADEON(0): Video RAM override, using 32768 kB instead of 32768 kB
(**) RADEON(0): VideoRAM: 32768 kByte (64 bit DDR SDRAM)
(II) RADEON(0): AGP card detected
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	ABI class: XFree86 Video Driver, version 0.7
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Loading /usr/X11R6/lib/modules/libi2c.a
(II) Module i2c: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.2.0
	ABI class: XFree86 Video Driver, version 0.7
(II) RADEON(0): I2C bus "DDC" initialized.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 2, Detected Type: 0
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 4, Detected Type: 0
(II) RADEON(0): Non-DDC laptop panel detected
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 3, Detected Type: 0
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 4, Detected Type: 0
(II) RADEON(0): Displays Detected: Monitor1--Type 2, Monitor2--Type 0

(II) RADEON(0): 
(II) RADEON(0): Primary Display == Type 2
(II) RADEON(0): Panel ID string: 1024x768		 
(II) RADEON(0): Panel Size from BIOS: 1024x768
(II) RADEON(0): BIOS provided dividers will be used.
(==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0)
(II) RADEON(0): Validating modes on Primary head ---------
(II) RADEON(0): Total number of valid DDC mode(s) found: 0
(II) RADEON(0): Valid mode using on-chip RMX: 1024x768
(II) RADEON(0): Valid mode using on-chip RMX: 800x600
(II) RADEON(0): Valid mode using on-chip RMX: 640x480
(II) RADEON(0): Total number of valid FP mode(s) found: 3
(--) RADEON(0): Virtual size is 1024x768 (pitch 1024)
(**) RADEON(0): *Mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz,
60.0 Hz
(II) RADEON(0): Modeline "1024x768"   65.00  1024 1040 1176 1344  768 770 776
806
(**) RADEON(0): *Mode "800x600": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0
Hz
(II) RADEON(0): Modeline "800x600"   65.00  800 1040 1176 1344	600 770 776 806

(**) RADEON(0): *Mode "640x480": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0
Hz
(II) RADEON(0): Modeline "640x480"   65.00  640 1040 1176 1344	480 770 776 806

(**) RADEON(0):  Default mode "640x350": 65.0 MHz (scaled from 0.0 MHz), 48.4
kHz, 60.0 Hz
(II) RADEON(0): Modeline "640x350"   65.00  640 1040 1176 1344	350 770 776 806

(**) RADEON(0):  Default mode "640x400": 65.0 MHz (scaled from 0.0 MHz), 48.4
kHz, 60.0 Hz
(II) RADEON(0): Modeline "640x400"   65.00  640 1040 1176 1344	400 770 776 806

(**) RADEON(0):  Default mode "720x400": 65.0 MHz (scaled from 0.0 MHz), 48.4
kHz, 60.0 Hz
(II) RADEON(0): Modeline "720x400"   65.00  720 1040 1176 1344	400 770 776 806

(**) RADEON(0):  Default mode "832x624": 65.0 MHz (scaled from 0.0 MHz), 48.4
kHz, 60.0 Hz
(II) RADEON(0): Modeline "832x624"   65.00  832 1040 1176 1344	624 770 776 806

(==) RADEON(0): DPI set to (75, 75)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/X11R6/lib/modules/libfb.a
(II) Module fb: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	ABI class: XFree86 ANSI C Emulation, version 0.2
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/X11R6/lib/modules/libramdac.a
(II) Module ramdac: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 0.1.0
	ABI class: XFree86 Video Driver, version 0.7
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.1.0
	ABI class: XFree86 Video Driver, version 0.7
(**) RADEON(0): Enabling AGP Fast Write
(II) RADEON(0): Depth moves disabled by default
(II) Loading sub module "shadowfb"
(II) LoadModule: "shadowfb"
(II) Loading /usr/X11R6/lib/modules/libshadowfb.a
(II) Module shadowfb: vendor="The XFree86 Project"
	compiled for 4.4.0, module version = 1.0.0
	ABI class: XFree86 ANSI C Emulation, version 0.2
(II) RADEON(0): Page flipping enabled
(!!) RADEON(0): For information on using the multimedia capabilities
 of this adapter, please see http://gatos.sf.net.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
	[0] 0	0	0xe4300000 - 0xe430ffff (0x10000) MX[B]
	[1] 0	0	0xec000000 - 0xefffffff (0x4000000) MX[B]
	[2] -1	0	0xffe00000 - 0xffffffff (0x200000) MX[B](B)
	[3] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[4] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[5] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[6] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[7] -1	0	0xe4004000 - 0xe4004fff (0x1000) MX[B]
	[8] -1	0	0xe4002000 - 0xe4002fff (0x1000) MX[B]
	[9] -1	0	0xe4000000 - 0xe4000fff (0x1000) MX[B]
	[10] -1 0	0xe4005000 - 0xe4004fff (0x0) MX[B]O
	[11] -1 0	0xe8000000 - 0xe7ffffff (0x0) MX[B]O
	[12] -1 0	0xe4300000 - 0xe430ffff (0x10000) MX[B](B)
	[13] -1 0	0xec000000 - 0xefffffff (0x4000000) MX[B](B)
	[14] -1 0	0xe4001000 - 0xe4001fff (0x1000) MX[B]
	[15] 0	0	0x000a0000 - 0x000affff (0x10000) MS[B](OprU)
	[16] 0	0	0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU)
	[17] 0	0	0x000b8000 - 0x000bffff (0x8000) MS[B](OprU)
	[18] 0	0	0x00009000 - 0x000090ff (0x100) IX[B]
	[19] -1 0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[20] -1 0	0x00000000 - 0x000000ff (0x100) IX[B]
	[21] -1 0	0x00002400 - 0x000024ff (0x100) IX[B]
	[22] -1 0	0x00002000 - 0x0000200f (0x10) IX[B]
	[23] -1 0	0x00001400 - 0x000014ff (0x100) IX[B]
	[24] -1 0	0x00001000 - 0x000010ff (0x100) IX[B]
	[25] -1 0	0x00009000 - 0x000090ff (0x100) IX[B](B)
	[26] 0	0	0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
	[27] 0	0	0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(WW) RADEON(0): Failed to set up write-combining range (0xec000000,0x2000000)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmGetBusid returned ''
(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:5:0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xd78f9000
(II) RADEON(0): [drm] mapped SAREA 0xd78f9000 to 0xb5ea7000
(II) RADEON(0): [drm] framebuffer handle = 0xec000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(II) RADEON(0): [agp] Mode 0x0f000214 [AGP 0x1002/0xcab2; Card 0x1002/0x4337]
(II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001
(II) RADEON(0): [agp] ring handle = 0xe8000000
(II) RADEON(0): [agp] Ring mapped at 0xb5da6000
(II) RADEON(0): [agp] ring read ptr handle = 0xe8101000
(II) RADEON(0): [agp] Ring read ptr mapped at 0xb5da5000
(II) RADEON(0): [agp] vertex/indirect buffers handle = 0xe8102000
(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0xb5ba5000
(II) RADEON(0): [agp] GART texture map handle = 0xe8302000
(II) RADEON(0): [agp] GART Texture map mapped at 0xb56c5000
(II) RADEON(0): [drm] register handle = 0xe4300000
(II) RADEON(0): [dri] Visual configs initialized
(II) RADEON(0): CP in BM mode
(II) RADEON(0): Using 8 MB GART aperture
(II) RADEON(0): Using 1 MB for the ring buffer
(II) RADEON(0): Using 2 MB for vertex/indirect buffers
(II) RADEON(0): Using 5 MB for GART textures
(II) RADEON(0): Memory manager initialized to (0,0) (1024,8191)
(II) RADEON(0): Reserved area from (0,768) to (1024,770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7421
(II) RADEON(0): Will use back buffer at offset 0x900000
(II) RADEON(0): Will use depth buffer at offset 0xc00000
(II) RADEON(0): Will use 17408 kb for textures at offset 0xf00000
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
	Screen to screen bit blits
	Solid filled rectangles
	8x8 mono pattern filled rectangles
	Indirect CPU to Screen color expansion
	Solid Lines
	Scanline Image Writes
	Offscreen Pixmaps
	Setting up tile and stipple cache:
		32 128x128 slots
		32 256x256 slots
		16 512x512 slots
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7417
(**) Option "dpms"
(**) RADEON(0): DPMS enabled
(II) RADEON(0): X context handle = 0x00000001
(II) RADEON(0): [drm] installed DRM signal handler
(II) RADEON(0): [DRI] installation complete
(II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
(II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
(II) RADEON(0): [drm] dma control initialized, using IRQ 10
(II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
(II) RADEON(0): Direct rendering enabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(**) Option "Protocol" "IMPS/2"
(**) Mouse1: Device: "/dev/input/mice"
(**) Mouse1: Protocol: "IMPS/2"
(**) Option "AlwaysCore"
(**) Mouse1: always reports core events
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "no"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse1: ZAxisMapping: buttons 4 and 5
(**) Mouse1: Buttons: 5
(II) Synaptics touchpad driver version 0.12.4
Mouse0 no synaptics event device found
(**) Option "Device" "/dev/psaux"
(**) Option "SHMConfig" "on"
(**) Option "LeftEdge" "1900"
(**) Option "RightEdge" "5400"
(**) Option "TopEdge" "1900"
(**) Option "BottomEdge" "4000"
(**) Option "FingerLow" "25"
(**) Option "FingerHigh" "30"
(**) Option "MaxTapTime" "180"
(**) Option "MaxTapMove" "220"
(**) Option "VertScrollDelta" "100"
(**) Option "Repeater" "/dev/ps2mouse"
(**) Option "Device" "/dev/ps2mouse"
Query no Synaptics: 6003C8
(--) Mouse0 no synaptics touchpad, data piped to repeater fifo
(**) Option "CorePointer"
(**) Mouse0: Core Pointer
(II) Keyboard "Keyboard0" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
Synaptics DeviceInit called
SynapticsCtrl called.
(II) Mouse1: ps2EnableDataReporting: succeeded
Synaptics DeviceOn called
Query no Synaptics: 6003C8
(--) Mouse0 no synaptics touchpad, data piped to repeater fifo
SynapticsCtrl called.
SynapticsCtrl called.
AUDIT: Sat Mar	6 14:38:51 2004: 1349 X: client 4 rejected from local host

Just for your information, I am running kernel-2.6.3-rc2       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Am Samstag, 6. M=E4rz 2004 04:59 schrieb bugzilla-daemon@...:

> ------- Additional Comments From lilnana@...  2004-03-05 22:59
> ------- Created an attachment (id=3D1130)
>  --> (http://bugs.xfree86.org/attachment.cgi?id=3D1130&action=3Dview)
> Enable 3D acceleration in XFree86-4.4.0
>
> I have managed to port attachment #723 work in the new version of
> XFree86-4.4.0.	3D acceleration works if you patch your kernel with the
> relevant version of the IGP patch.

> (--) Chipset ATI Radeon IGP330M/340M/350M (U2) 4337 found

> (--) RADEON(0): Chipset: "ATI Radeon IGP330M/340M/350M (U2) 4337" (ChipID=
 =3D
> 0x4337)

What about IGP 320M?

Thanks,
	Dieter

=2D-=20
Dieter N=FCtzel
@home: <Dieter.Nuetzel () hamburg ! de>

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From apoking@...  2004-03-12 06:36 -------
hi people,
 i use xfree 4.4 with patch
http://bugs.xfree86.org/attachment.cgi?id=1130&action=view,
kernel 2.6.3 and the latest dri package in drm-module-trunk.deb (i'm in debian Sid).
Apparently all work fine
glxgears show ~400 fps and glxinfo result direct rendering: Yes but when i want
to use  a game that use openGL (ut or Pete's mesa GPU in epsxe) this crash with
error
drmCommandWrite: -22
drmRadeonCmdBuffer: -22 (exiting).
any ideas? what's the kind of problem? thk!       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

z3p@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|z3p@...       |


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From bugzilla@...  2004-03-13 02:22 -------
Is there 3D support without installing an xfree cvs. Is there a backport for xfree 4.3.0 or is it not even possible?       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From keith.hassen@...  2004-03-20 19:46 -------

Hi all,

I have XFree86 v. 4.3.99.902 built with the radeon patch (id 862 in the list
above) on a gentoo laptop with kernel 2.6.3-rc2-mm1.  My laptop is an HP ze5300
with an ATI Radeon IGP 340M chip.

Using the patched radeon driver has enabled direct rendering, and I get ~500
with glxgears.  However, in trying to run ut2003 or tuxracer, I receive:

drmCommandWrite: -22
drmRadeonCmdBuffer: -22 (exiting)

I cannot seem to find documentation on this sort of behaviour anywhere.

It would be very appreciated to hear some comments on this.  Perhaps I should
repatch with the new XFree86-4.4.0?

       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

michel@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|michel@...          |
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From michel@...  2004-03-21 18:48 -------
This bug has been obsolete for a while. Get the code from DRI CVS. Most if not
all of the patches attached to this bug are incomplete and not expected to work
with the current DRM.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

shpalsam@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




------- Additional Comments From shpalsam@...  2004-03-22 15:08 -------
(In reply to comment #271)
> Hi all,
> 
> I have XFree86 v. 4.3.99.902 built with the radeon patch (id 862 in the list
> above) on a gentoo laptop with kernel 2.6.3-rc2-mm1.  My laptop is an HP ze5300
> with an ATI Radeon IGP 340M chip.
> 
> Using the patched radeon driver has enabled direct rendering, and I get ~500
> with glxgears.  However, in trying to run ut2003 or tuxracer, I receive:
> 
> drmCommandWrite: -22
> drmRadeonCmdBuffer: -22 (exiting)
> 
> I cannot seem to find documentation on this sort of behaviour anywhere.
> 
> It would be very appreciated to hear some comments on this.  Perhaps I should
> repatch with the new XFree86-4.4.0?
> 
> 

On my HP pavilion 4288, IGP320 patch works fine for Xfree 4.3.99.14, but when i
installa xfree 4.4.0 with the patch, glxgears works, glxinfo tells me that there
is DRI but Unreal Tournament and Quake 3 don't work (try to load and i obtain
just a black screen --> crash).
I'll don't use xfree 4.4.0 for the moment.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From keith.hassen@...  2004-03-22 20:02 -------
(In reply to comment #272)
> This bug has been obsolete for a while. Get the code from DRI CVS. Most if not
> all of the patches attached to this bug are incomplete and not expected to work
> with the current DRM.


I rebuilt the radeon.o module using the latest DRI CVS source, but upon
restarting the X server I no longer get direct rendering capability.  Is there a
patch required, or some source-specific settings I need to configure in order to
enable this?


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From flavien.lory@...  2004-03-30 06:32 -------
I've got a IGP345M gpu with kernel 2.6.4 + bk4 + dri patch  from attachement 1130.
Xfree is up to date with XFree4.4.0. I rebuild radeon.ko with dri CVS.
All the log looks fine, i just notice this change :
(WW) RADEON(0): Failed to set up write-combining range (0xd8000000,0x4000000)

before i was under 2.4.22-bk60 / xfree4.3.99.9 this many patchs ( 3D ok and
fully functionnal ):
(==) RADEON(0): Write-combining range (0xd8000000,0x4000000)

Acceleration is enable, 
- glxgears OK
- euphoria ( frame rate is good, but the testure mapping is tilted
- tuxracer ( I see only solid color, no mouse,no menu, ground is black ...)

       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From lilnana@...  2004-04-05 03:02 -------
Hi folks,
Sorry for the long silence.  I have been busy with exams and other stuff.  I am
working towards correcting the bug in XFree86-4.40 regarding the
drmCommandWrite: -22
drmRadeonCmdBuffer: -22 (exiting)
reported here.  It doesn't seem to happen with my card, so I don't know what is
happening.  I now have some free time at hand. 

On the other hand, if someone knows more about this bug than I do, please feel
free to correspond with me so we can correct this bug and all of us can enjoy
full functional 3D.

I have rebuilt my rpms with the current Xfree86-4.4.99.2 snap shots.  There is
signficant improvement.  Synaptics drivers is no longer needed for touchpad.

As stated here, I don't have a dedicated server, so I have no where to upload
the files.  Again, if anyone has a webspace to spare, I can upload the files so
we can all test it out. 

In addition, all my rpms are optimized for Pentium III and above.  If you have a
different class processor, you can rebuild the rpm yourself with

[root@... root]# rpmbuild --rebuild <srpm file> 

This will rebuild the rpm to suit your architecture.

I hope this answers some of the questions I have been receiving in emails

(In reply to comment #274)
> (In reply to comment #272)
> > This bug has been obsolete for a while. Get the code from DRI CVS. Most if not
> > all of the patches attached to this bug are incomplete and not expected to work
> > with the current DRM.
> 
> 
> I rebuilt the radeon.o module using the latest DRI CVS source, but upon
> restarting the X server I no longer get direct rendering capability.  Is there a
> patch required, or some source-specific settings I need to configure in order to
> enable this?
> 
> 
> 

       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From lilnana@...  2004-04-06 03:44 -------
Hi again,

Thanks to Dan at planetmirror.com, we have been able to upload the files onto
their server.  You can find the files at

http://planetmirror.com/pub/radeonigp/
ftp://ftp.planetmirror.com/pub/radeonigp/

Please do read the REAME file first.  It will save you a lot of trouble.

A big thank you, one again, to Dan

(In reply to comment #276)
> Hi folks,
> Sorry for the long silence.  I have been busy with exams and other stuff.  I am
> working towards correcting the bug in XFree86-4.40 regarding the
> drmCommandWrite: -22
> drmRadeonCmdBuffer: -22 (exiting)
> reported here.  It doesn't seem to happen with my card, so I don't know what is
> happening.  I now have some free time at hand. 
> 
> On the other hand, if someone knows more about this bug than I do, please feel
> free to correspond with me so we can correct this bug and all of us can enjoy
> full functional 3D.
> 
> I have rebuilt my rpms with the current Xfree86-4.4.99.2 snap shots.  There is
> signficant improvement.  Synaptics drivers is no longer needed for touchpad.
> 
> As stated here, I don't have a dedicated server, so I have no where to upload
> the files.  Again, if anyone has a webspace to spare, I can upload the files so
> we can all test it out. 
> 
> In addition, all my rpms are optimized for Pentium III and above.  If you have a
> different class processor, you can rebuild the rpm yourself with
> 
> [root@... root]# rpmbuild --rebuild <srpm file> 
> 
> This will rebuild the rpm to suit your architecture.
> 
> I hope this answers some of the questions I have been receiving in emails
> 
> (In reply to comment #274)
> > (In reply to comment #272)
> > > This bug has been obsolete for a while. Get the code from DRI CVS. Most if not
> > > all of the patches attached to this bug are incomplete and not expected to
work
> > > with the current DRM.
> > 
> > 
> > I rebuilt the radeon.o module using the latest DRI CVS source, but upon
> > restarting the X server I no longer get direct rendering capability.  Is there a
> > patch required, or some source-specific settings I need to configure in order to
> > enable this?
> > 
> > 
> > 
> 
> 

       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

michel@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From michel@...  2004-04-07 09:44 -------
From http://public.planetmirror.com/pub/radeonigp/README_First:

> 3.	I get the following error when I run tuxracer and Chromium even though
> 	X says Direct Rendering is enabled.
> 
>    	drmCommandWrite: -22
>    	drmRadeonCmdBuffer: -22 (exiting)
> 
> Ans:	This is known to happen with some cards.  I am currently investigating
> 	the cause of this bug. It seems the problem is from the libGLU
>       libraries.

No, as I said before, these are 3D driver bugs due to the patches attached here
not being complete. Get the fixed code from DRI/Mesa CVS.


> 4.	What about us who run Debian?  Do you build Debian packages as well?
> 
> Ans:	At the moment, no, but it's on the agenda.  For the mean time, debian
> 	users can convert the rpm packages to debain packages using
> 	Alien Package Converter http://www.kitenet.net/programs/alien/
> 	Slackware users can do the same.

Or just use the snapshot packages which I've been providing for ages and which
are linked from the dri.sf.net download page.


And please don't reopen this bug again. That stopped being funny a long time ago.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From roguestar191@...  2004-04-07 18:02 -------
Michel Dänzer, I have tried that past 15-20 dri snapshots from the sourceforge 
website, up to march 31. I get weird errors every time I try to run any app 
that using DRI, and a crash. I'm not using any of the patches here, I've done 
everything from upgrading the kernel to re-downloading XFree86, recompiling it, 
and reinstalling it... again. The latest DRI snapshots simply do_not_work with 
the igp320. I have one from way back in 2003 that works, sometimes, but I get 
segfaults with a lot of dri apps even with that patch.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From flavien.lory@...  2004-04-09 04:15 -------
(In reply to comment #275)

Fixed with 2.6.5-mm1 and XFree4.4.99.2 and last DRI Snapshot.
Thanks a lot.
       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From Stunbmun@...  2004-04-12 23:33 -------
(In reply to comment #277)
Help... I'm pretty new to Linux in general, I have compiled my kernel and built
the patched XFree for my IGP320 from the how-to on jaydolan.com.  I think I'm
getting the same problem described by a few people where everything appears to
be working, but anytime I run tuxracer, chromium, or any other somewhat decent
game, my computer locks up.  I've tried to build the rpms mentioned in #277 but
I'm running Gentoo and I get all kinds of errors trying to build from the
sources.  Could anyone who knows Gentoo ebuilds, create one for the rpm found at
the link to planetmirror.  I've tried emerging rpm and running rpmbuild on the
sources but I get all kind of dependency errors on things that are already
installed via emerge.  

> http://planetmirror.com/pub/radeonigp/
> ftp://ftp.planetmirror.com/pub/radeonigp/       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From lilnana@...  2004-04-16 06:00 -------
Hi folks,

I am back.  I have been able to get full 3D acceleration by replacing my DRI,
DRM and Mesa modules and libraries with one from dri cvs.  This fully enables 3D
on ATI Radeon IGP 340M.

This should work on both XFree86-4.4 and those of you new running Xorg X11R6.7.0.  

I have all the compiled modules.  I will be talking to Dan again to see if I can
upload them onto the planner mirror site.  I will also include instructions on
how to backup your old modules and libraries and replace them with this new one.
 Please report success or failure when you have tried them.   

Thanks all for your support       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From lilnana@...  2004-04-19 03:12 -------
I have uploaded the update libraries and drivers on planetmirror, thanks again
to Dan. Please visit

http://public.planetmirror.com/pub/radeonigp/radeon-igp-3D.tar.bz2
ftp://ftp.planetmirror.com/pub/radeonigp/radeon-igp-3D.tar.bz2

The the script is well documented.  Please read the README file too.  I have
tested it with both XFree86-4.4.x and Xorg X11 from Fedora rawhide.  3d works
very well.

Thanks all for your support once again.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From andreas.zuber@...  2004-04-19 16:34 -------
Hi

I have tested the drivers from planetmirror with my 340M Chip on my Laptop and
got the same Problems I had with the dri-cvs version.

This are the Patches I tried:

Xfree86 4.3.0 from gentoo and Xfree86 4.3.99.? with dri trunk
- dri enabled
- glxgears ~360 FPS
- only one resolution (1400x1050) works

Xfree86 4.3.99.? patched with 
http://bugs.xfree86.org/attachment.cgi?id=1130&action=view
- dri enabled
- glxgears ~330 FPS
- all resolutions work

Xfree86.4.3.99.? and the tar.bz2 from Nana Kofi Asumadu
- dri enabled
- glxgears ~300 FPS
- only one resolution (1400x1050) works

Once I talked to someone in the dri irc channel aboute the problem with the
resolution and he told me that the code for the detection of the TFT modelines
is a part of the xfree86 and not of the dri project. Thats all I know about this
problem.

About the performance. I don't know how fast the 340M is but I think it can
render more than 360 FPS in glxgears if the driver works well. Is there someone
with better results?

I have no Idea what I should post to help you fixing this bug. Please say what
you need and I will upload the files to a webserver as fast as possible.

Finaly something about this Buglist. Some People are not happy that this Buglist
is used as a forum. But there are no other possibilities for non-developers to
post their problems with a driver or someting else. Nobody subscribes to a
maillist if he is interrested in just one driver. I think a web-forum on the dri
page isn't the worst idea.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From bitti@...  2004-05-08 00:46 -------
I just patched XFree86 4.4.0 sources with
XFree86-4.4.0-radeon-igp.patch.
First of all, is there a typo in line 569: unsigned long fb_location; ?
shouldn't it be unsigned long fb_base; ? anyway, the drm-module didn't
compile before i changed fb_location => fb_base. The drm-module radeon.ko loads
ok (eg. no error messages), but it doesnt work. XFree86.log.0:

(II) Primary Device is: PCI 01:05:0
(--) Assigning device section with no busID to primary device
(--) Chipset ATI Radeon IGP320M (U1) 4336 found

drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed

(II) RADEON(0): [drm] drmOpen failed
(EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.
(II) RADEON(0): Direct rendering disabled

lsmod:
radeon                128960  0
ati_agp                 6348  1

And yes, the radeon.ko which modprobe loads, is the same than
xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/radeon.ko.

I tryed to use the radeon.ko which ships with my kernel (2.6.5), and it
reported something when loaded with modprobe:
[drm] Initialized radeon 1.9.0 20020828 on minor 0
Even the XFree86.0.log says everything is fine for a while:

drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmGetBusid returned ''
(II) RADEON(0): [drm] created "radeon" driver at busid "PCI:1:5:0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xdd910000
(II) RADEON(0): [drm] mapped SAREA 0xdd910000 to 0x44267000
(II) RADEON(0): [drm] framebuffer handle = 0xf0000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(II) RADEON(0): [agp] Mode 0x0f000204 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]
(II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001
(II) RADEON(0): [agp] ring handle = 0xec000000
(II) RADEON(0): [agp] Ring mapped at 0x44269000
(II) RADEON(0): [agp] ring read ptr handle = 0xec101000
(II) RADEON(0): [agp] Ring read ptr mapped at 0x4436a000
(II) RADEON(0): [agp] vertex/indirect buffers handle = 0xec102000
(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x4436b000
(II) RADEON(0): [agp] GART texture map handle = 0xec302000
(II) RADEON(0): [agp] GART Texture map mapped at 0x4456b000
(II) RADEON(0): [drm] register handle = 0xe8500000
(II) RADEON(0): [dri] Visual configs initialized
(II) RADEON(0): [drm] installed DRM signal handler
(II) RADEON(0): [DRI] installation complete

(WW) RADEON(0): Mismatched FB location. Incorrect version of DRM kernel driver $
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xdd910000 at 0x44267000
(II) RADEON(0): Direct rendering disabled

Any hints?       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From jasonthomasdolan@...  2004-05-08 15:25 -------
The patch is bogus.  You need NEED _NEED_ **NEED** to get the code from DRI CVS
if you want an IGP card to work properly with XFree86 4.4.0.  How many times do
you have to hear it?

The How-To at http://jaydolan.com has been updated with instructions for
building and installing everything properly for Linux 2.6.5 and XFree86 4.4.0,
and I assure you it can work because I have a 320m myself.       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From dfal@...  2004-05-11 00:03 -------
Could someone please make some general .deb packages for less experienced users???       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From michel@...  2004-05-11 08:55 -------
(In reply to comment #287)
> Could someone please make some general .deb packages for less experienced users???

As mentioned before in this very bug, I've been doing that for a while:
http://dri.sourceforge.net/cgi-bin/moin.cgi/Download       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       




------- Additional Comments From verwilst@...  2004-06-14 18:16 -------
Could anybody tell me when this will be in the actual release of Xfree/Xorg? I would really like to  
use it in my distro without having to bend over backwards to make it work ;) Thanks!         
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

ddemidov@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ddemidov@...


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Please do not reply to this email: if you want to comment on the bug, go to   
the URL shown below and enter your comments there.      
     
http://bugs.xfree86.org/show_bug.cgi?id=314       
       

michael@... changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|michael@...           |


       
       
--        
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email       
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.