[gentoo-user] struggling with dri

[gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 6555 bytes --]

Hi,
I know this is a well discussed topic.. but I can't find answer to my
problem.. and I'm completely lost in all mails/forums..

I have a ATI Technologies Inc Radeon Mobility M6 LY and I been using
"radeon" driver from kernel.
In order to enable rendering, I been looking around and after no success I
was told that I should use fglrx driver from proprietary ATI-drivers! Tried
it, but no deal! Then I was again told that these drivers were not to my
card, and that radeon should made it.
So, I'm back to radeon but still no rendering. However, there's noting
saying the opposite unless:
# glxinfo | grep -i rendering
direct rendering: No

Xorg log says:
(...)
(II) RADEON(0): initializing int10
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
(--) RADEON(0): Chipset: "ATI Radeon Mobility M6 LY (AGP)" (ChipID = 0x4c59)
(--) RADEON(0): Linear framebuffer at 0x88000000
(--) RADEON(0): BIOS at 0x80520000
(--) RADEON(0): VideoRAM: 32768 kByte (64 bit DDR SDRAM)
(II) RADEON(0): AGP card detected
(...)

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
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
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(II) RADEON(0): [drm] loaded kernel module for "radeon" driver
(II) RADEON(0): [drm] DRM interface version 1.2
(II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0"
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe2079000
(II) RADEON(0): [drm] mapped SAREA 0xe2079000 to 0xb5c6e000
(II) RADEON(0): [drm] framebuffer handle = 0x88000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(II) RADEON(0): [agp] Mode 0x1f000201 [AGP 0x8086/0x1a30; Card
0x1002/0x4c59]
(II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001
(II) RADEON(0): [agp] ring handle = 0xe0000000
(II) RADEON(0): [agp] Ring mapped at 0xb5b6d000
(II) RADEON(0): [agp] ring read ptr handle = 0xe0101000
(II) RADEON(0): [agp] Ring read ptr mapped at 0xb5b6c000
(II) RADEON(0): [agp] vertex/indirect buffers handle = 0xe0102000
(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0xb596c000
(II) RADEON(0): [agp] GART texture map handle = 0xe0302000
(II) RADEON(0): [agp] GART Texture map mapped at 0xb548c000
(II) RADEON(0): [drm] register handle = 0x80500000
(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) (1408,5957)
(II) RADEON(0): Reserved area from (0,1050) to (1408,1052)
(II) RADEON(0): Largest offscreen area available: 1408 x 4905
(II) RADEON(0): Will use back buffer at offset 0xb70000
(II) RADEON(0): Will use depth buffer at offset 0x1114000
(II) RADEON(0): Will use 9472 kb for textures at offset 0x16c0000
(II) RADEON(0): Render acceleration enabled
(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
15 512x512 slots
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 1052)
(II) RADEON(0): Largest offscreen area available: 1408 x 4902
(**) 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 11
(II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
(II) RADEON(0): Direct rendering enabled

So... it says enable... so is not?

dmesg says:

radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=175.00 Mhz, System=175.00MHz
radeonfb: PLL min 12000 max 35000
Non-DDC laptop panel detected
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type no found
radeonfb: panel ID string: Samsung LTN150P1-L02
radeonfb: detected LVDS panel size from BIOS: 1400x1050
radeondb: BIOS provided dividers will be used
radeonfb: Dynamic Clock Power Management enabled
radeonfb (0000:01:00.0): ATI Radeon LY
vesafb: abort, cannot reserve video memory at 0x88000000
vesafb: framebuffer at 0x88000000, mapped to 0xe1900000, using 5120k, total
32768k
vesafb: mode is 1280x1024x16, linelength=2560, pages=11
vesafb: protected mode interface info at c000:5229
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
fb1: VESA VGA frame buffer device
(...)
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel i845 Chipset.
agpgart: AGP aperture is 256M @ 0xe0000000
(...)
[drm] Initialized drm 1.0.0 20040925
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [PILA] -> GSI 11 (level, low) ->
IRQ 11
[drm] Initialized radeon 1.16.0 20050311 on minor 0:
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
(...)

My xorg has:
# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"

Section "Device"
Identifier "ATI"
Driver "radeon"
#VideoRam 131072
# Insert Clocks lines here if appropriate
Option "ForcePCIMode" "True"
EndSection

Section "dri"
Mode 0666
EndSection

And I think that's all...
So, is there anyone that can give me a "hand" on this?
All seems to be right but glxinfo does not agree..

ohh, btw,
# glxgears
832 frames in 5.0 seconds = 166.400 FPS
1320 frames in 5.0 seconds = 264.000 FPS
840 frames in 5.0 seconds = 168.000 FPS
840 frames in 5.0 seconds = 168.000 FPS

Cheers,
Fernando

[-- Attachment #2: Type: text/html, Size: 8404 bytes --]

Re: [gentoo-user] struggling with dri

[Ow Mun Heng]

On Sun, 2005-10-09 at 22:44 +0200, Fernando Meira wrote:

> 
> Section "dri"
>    Mode 0666
> EndSection


Please check if permissions of /dev/dri/cardX is really 0666.

Mine has to be changed.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 656 bytes --]

On 10/10/05, Ow Mun Heng <Ow.Mun.Heng@wdc.com> wrote:
>
> On Sun, 2005-10-09 at 22:44 +0200, Fernando Meira wrote:
>
> >
> > Section "dri"
> > Mode 0666
> > EndSection
>
>
> Please check if permissions of /dev/dri/cardX is really 0666.
>
> Mine has to be changed.


Yes, they were not 0666 but instead 0660. I changed them, rebooted, and
they're back to 0660 :(
Anyway, I don't think it is a permissions problem, because I get the same
result if I run glxinfo with root... or is it?
Also, I did not emerge x11-drm, the howto said that it was not necessary
(even un-supported) with kernel 2.6.. can this be a problem?

TIA,
Fernando

[-- Attachment #2: Type: text/html, Size: 1010 bytes --]

Re: [gentoo-user] struggling with dri

[Frank Schafer]

On Mon, 2005-10-10 at 10:13 +0200, Fernando Meira wrote:
> On 10/10/05, Ow Mun Heng <Ow.Mun.Heng@wdc.com> wrote:
>         On Sun, 2005-10-09 at 22:44 +0200, Fernando Meira wrote:
>         
>         >
>         > Section "dri"
>         >    Mode 0666
>         > EndSection
>         
>         
>         Please check if permissions of /dev/dri/cardX is really 0666.
>         
>         Mine has to be changed.
> 
> Yes, they were not 0666 but instead 0660. I changed them, rebooted,
> and they're back to 0660 :(

If you are running udev, make your (user) udev.rules file do make the
permissions permanent.


> Anyway, I don't think it is a permissions problem, because I get the
> same result if I run glxinfo with root... or is it?
> Also, I did not emerge x11-drm, the howto said that it was not
> necessary (even un-supported) with kernel 2.6.. can this be a problem?
> 
> TIA,
> Fernando
> 
> 
> 
> 
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Jason Cooper]

Fernando Meira (fmeira@gmail.com) scribbled:
> Yes, they were not 0666 but instead 0660. I changed them, rebooted, and
> they're back to 0660 :(

cd into /etc/udev/rules.d/ and make a file called 10-local.rules .  Add
the 'dri' lines from 50-udev.rules.  Append to the end of each line
"MODE=0666"

> Anyway, I don't think it is a permissions problem, because I get the same
> result if I run glxinfo with root... or is it?

Make sure the module for your agpgart is loaded _before_ the radeon
module.  

hth,

jason.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 862 bytes --]

On 10/10/05, Jason Cooper <gentoo@lakedaemon.net> wrote:
>
> Fernando Meira (fmeira@gmail.com) scribbled:
> > Yes, they were not 0666 but instead 0660. I changed them, rebooted, and
> > they're back to 0660 :(
>
> cd into /etc/udev/rules.d/ and make a file called 10-local.rules . Add
> the 'dri' lines from 50-udev.rules. Append to the end of each line
> "MODE=0666"
>
> > Anyway, I don't think it is a permissions problem, because I get the
> same
> > result if I run glxinfo with root... or is it?
>
> Make sure the module for your agpgart is loaded _before_ the radeon
> module.
>
> hth,
>
> jason.


Ok, I did so, now I have:
# ll /dev/dri/card0
crw-rw-rw- 1 root root 226, 0 Oct 10 2005 /dev/dri/card0

but still no rendering:
# glxinfo | grep rendering
direct rendering: No

anything else I should check?
Thanks,
Fernando

[-- Attachment #2: Type: text/html, Size: 1280 bytes --]

Re: [gentoo-user] struggling with dri

[Michael Taylor]

[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]

unsubscribe

On 10/10/05, Fernando Meira <fmeira@gmail.com> wrote:
>
> On 10/10/05, Jason Cooper <gentoo@lakedaemon.net> wrote:
>
> > Fernando Meira (fmeira@gmail.com) scribbled:
> > > Yes, they were not 0666 but instead 0660. I changed them, rebooted,
> > and
> > > they're back to 0660 :(
> >
> > cd into /etc/udev/rules.d/ and make a file called 10-local.rules . Add
> > the 'dri' lines from 50-udev.rules. Append to the end of each line
> > "MODE=0666"
> >
> > > Anyway, I don't think it is a permissions problem, because I get the
> > same
> > > result if I run glxinfo with root... or is it?
> >
> > Make sure the module for your agpgart is loaded _before_ the radeon
> > module.
> >
> > hth,
> >
> > jason.
>
>
> Ok, I did so, now I have:
> # ll /dev/dri/card0
> crw-rw-rw- 1 root root 226, 0 Oct 10 2005 /dev/dri/card0
>
> but still no rendering:
> # glxinfo | grep rendering
> direct rendering: No
>
> anything else I should check?
> Thanks,
> Fernando
>

[-- Attachment #2: Type: text/html, Size: 1892 bytes --]

Re: [gentoo-user] struggling with dri

[Richard Fish]

Michael Taylor wrote:

> unsubscribe
>
> On 10/10/05, *Fernando Meira* <fmeira@gmail.com 
> <mailto:fmeira@gmail.com>> wrote:
>
>     On 10/10/05, *Jason Cooper* <gentoo@lakedaemon.net
>     <mailto:gentoo@lakedaemon.net>> wrote:
>
>         Fernando Meira (fmeira@gmail.com <mailto:fmeira@gmail.com>)
>         scribbled:
>> Yes, they were not 0666 but instead 0660. I changed them,
>         rebooted, and
>> they're back to 0660 :(
>
>         cd into /etc/udev/rules.d/ and make a file called
>         10-local.rules .  Add
>         the 'dri' lines from 50-udev.rules.  Append to the end of each
>         line
>         "MODE=0666"
>
>> Anyway, I don't think it is a permissions problem, because I
>         get the same
>> result if I run glxinfo with root... or is it?
>
>         Make sure the module for your agpgart is loaded _before_ the
>         radeon
>         module.
>
>         hth,
>
>         jason.
>
>
>     Ok, I did so, now I have:
>     # ll /dev/dri/card0
>     crw-rw-rw-  1 root root 226, 0 Oct 10  2005 /dev/dri/card0
>
>     but still no rendering:
>     # glxinfo | grep rendering
>     direct rendering: No
>
>     anything else I should check?
>     Thanks,
>     Fernando
>
>

Well, I wouldn't do anything so drastic as unsubscribing... :-)

When you run glxinfo, what is your DISPLAY variable set to?  DRI doesn't 
work across a network, so it should be DISPLAY=:0.0

Also for reference, my "dri" section from xorg.conf:

Section "dri"
        Group "graphics"
        Mode 0660
EndSection

Notice that I specify the Group.  My account is then a member of the the 
"graphics" group.

HTH,
-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 4674 bytes --]

On 10/10/05, Richard Fish <bigfish@asmallpond.org> wrote:
>
> Michael Taylor wrote:
>
> > unsubscribe
> >
> > On 10/10/05, *Fernando Meira* <fmeira@gmail.com
> > <mailto:fmeira@gmail.com>> wrote:
> >
> > On 10/10/05, *Jason Cooper* <gentoo@lakedaemon.net
> > <mailto:gentoo@lakedaemon.net>> wrote:
> >
> > Fernando Meira (fmeira@gmail.com <mailto:fmeira@gmail.com>)
> > scribbled:
> >> Yes, they were not 0666 but instead 0660. I changed them,
> > rebooted, and
> >> they're back to 0660 :(
> >
> > cd into /etc/udev/rules.d/ and make a file called
> > 10-local.rules . Add
> > the 'dri' lines from 50-udev.rules. Append to the end of each
> > line
> > "MODE=0666"
> >
> >> Anyway, I don't think it is a permissions problem, because I
> > get the same
> >> result if I run glxinfo with root... or is it?
> >
> > Make sure the module for your agpgart is loaded _before_ the
> > radeon
> > module.
> >
> > hth,
> >
> > jason.
> >
> >
> > Ok, I did so, now I have:
> > # ll /dev/dri/card0
> > crw-rw-rw- 1 root root 226, 0 Oct 10 2005 /dev/dri/card0
> >
> > but still no rendering:
> > # glxinfo | grep rendering
> > direct rendering: No
> >
> > anything else I should check?
> > Thanks,
> > Fernando
> >
> >
>
> Well, I wouldn't do anything so drastic as unsubscribing... :-)
>
> When you run glxinfo, what is your DISPLAY variable set to? DRI doesn't
> work across a network, so it should be DISPLAY=:0.0
>
> Also for reference, my "dri" section from xorg.conf:
>
> Section "dri"
> Group "graphics"
> Mode 0660
> EndSection
>
> Notice that I specify the Group. My account is then a member of the the
> "graphics" group.
>
> HTH,
> -Richard


Wow.. unsubscribe is kinda drastic... I'd end up with no dri and no one to
ask for help :)

My display is 0.0 (as you can see bellow the complete output of glxinfo.
I don't have specified the group in xorg, but I added my user to "video" and
set the mode to 0666 which allows all users...
it's hard to believe that's something to do with permissions.. but anyway,
I'll try it.. i don't have anything to loose.. Thanks!

Meanwhile, any other ideas?

$ glxinfo
name of 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_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_OML_swap_method, GLX_SGI_make_current_read,
GLX_SGIS_multisample, GLX_SGIX_fbconfig
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float,
GLX_ATI_render_texture
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_multisample
OpenGL vendor string: Mesa project: www.mesa3d.org <http://www.mesa3d.org>
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)
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

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 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 1 0 None
0x24 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x25 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow
0x26 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow
0x27 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 1 0 None
0x28 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x29 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow
0x2a 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow
0x2b 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 1 0 None
0x2c 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x2d 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow
0x2e 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow
0x2f 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 1 0 None
0x30 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 1 0 None
0x31 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow
0x32 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow

[-- Attachment #2: Type: text/html, Size: 8493 bytes --]

Re: [gentoo-user] struggling with dri

[Kevin Hanson]

Fernando Meira wrote:

> Hi,
> I know this is a well discussed topic.. but I can't find answer to my 
> problem.. and I'm completely lost in all mails/forums..
>
> I have a ATI Technologies Inc Radeon Mobility M6 LY and I been using 
> "radeon" driver from kernel.
> In order to enable rendering, I been looking around and after no 
> success I was told that I should use fglrx driver from proprietary 
> ATI-drivers! Tried it, but no deal! Then I was again told that these 
> drivers were not to my card, and that radeon should made it.
> So, I'm back to radeon but still no rendering. However, there's noting 
> saying the opposite unless:
> # glxinfo | grep -i rendering
> direct rendering: No
>
I am following this thread w/ interest as I am having similar problems.  
Although I am seeing errors in my syslog file that indicate I'm not even 
able to get agp going.  Anyone seen something similar? 

[drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies 
Inc M9+ 5C61 [Radeon Mobility 9200 (AGP)]
[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
[drm:drm_unlock] *ERROR* Process 9513 using kernel context 0


I've got a radeon mobility 9200 in my laptop and have compiled 
CONFIG_AGP=m, CONFIG_AGP_INTEL=m, CONFIG_DRM=m, and CONFIG_DRM_RADEON=m. 

Interestingly enough, agpgart module loads at boot but intel_agp 
doesn't.  Modprobe of intel_agp produces no errors, but lsmod shows it's 
not loaded.  Nothing in log files either.  When X is started, drm and 
radeon modules load up, but dri still doesn't work, probably because agp 
isn't working.

Cheers,
Kevin
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Jason Cooper]

Kevin Hanson (tuxpert@comcast.net) scribbled:
> I've got a radeon mobility 9200 in my laptop and have compiled 
> CONFIG_AGP=m, CONFIG_AGP_INTEL=m, CONFIG_DRM=m, and CONFIG_DRM_RADEON=m. 
> 
> Interestingly enough, agpgart module loads at boot but intel_agp 
> doesn't.  Modprobe of intel_agp produces no errors, but lsmod shows it's 
> not loaded.  Nothing in log files either.  When X is started, drm and 
> radeon modules load up, but dri still doesn't work, probably because agp 
> isn't working.

Do you have agpgart in /etc/modules.autoload.d/kernel-2.6 ?  replace it
with intel_agp, then place radeon on the line following.  intel_agp will
draw in agpgart, and radeon must be loaded after those are in.

hth,

jason.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]

On 10/10/05, Jason Cooper <gentoo@lakedaemon.net> wrote:
>
> Kevin Hanson (tuxpert@comcast.net) scribbled:
> > I've got a radeon mobility 9200 in my laptop and have compiled
> > CONFIG_AGP=m, CONFIG_AGP_INTEL=m, CONFIG_DRM=m, and CONFIG_DRM_RADEON=m.
> >
> > Interestingly enough, agpgart module loads at boot but intel_agp
> > doesn't. Modprobe of intel_agp produces no errors, but lsmod shows it's
> > not loaded. Nothing in log files either. When X is started, drm and
> > radeon modules load up, but dri still doesn't work, probably because agp
> > isn't working.
>
> Do you have agpgart in /etc/modules.autoload.d/kernel-2.6 ? replace it
> with intel_agp, then place radeon on the line following. intel_agp will
> draw in agpgart, and radeon must be loaded after those are in.
>
> hth,
>
> jason.


I think I have radeon driver built-in the kernel.. does that mean that it is
loaded before agpgart?
agpgart and intel_agp are both modules...

should I them recompile my kernel and leave radeon as module?

Fernando

[-- Attachment #2: Type: text/html, Size: 1490 bytes --]

Re: [gentoo-user] struggling with dri

[Jason Cooper]

Fernando Meira (fmeira@gmail.com) scribbled:
> I think I have radeon driver built-in the kernel.. does that mean that it is
> loaded before agpgart?
> agpgart and intel_agp are both modules...
> 
> should I them recompile my kernel and leave radeon as module?

yes.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 566 bytes --]

On 10/10/05, Jason Cooper <gentoo@lakedaemon.net> wrote:
>
> Fernando Meira (fmeira@gmail.com) scribbled:
> > I think I have radeon driver built-in the kernel.. does that mean that
> it is
> > loaded before agpgart?
> > agpgart and intel_agp are both modules...
> >
> > should I them recompile my kernel and leave radeon as module?
>
> yes.


Ok, with this modules being loaded at boot:
agpgart
intel_agp
radeon

I still don't have rendering!
So, should I try to compile all built-in the kernel? Or should I go for
x11-drm?

Cheers,
Fernando

[-- Attachment #2: Type: text/html, Size: 932 bytes --]

Re: [gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

On 10/11/05, Fernando Meira <fmeira@gmail.com> wrote:
>
> On 10/10/05, Jason Cooper <gentoo@lakedaemon.net> wrote:
> >
> > Fernando Meira (fmeira@gmail.com) scribbled:
> > > I think I have radeon driver built-in the kernel.. does that mean that
> > it is
> > > loaded before agpgart?
> > > agpgart and intel_agp are both modules...
> > >
> > > should I them recompile my kernel and leave radeon as module?
> >
> > yes.
>
>
> Ok, with this modules being loaded at boot:
> agpgart
> intel_agp
> radeon
>
> I still don't have rendering!
> So, should I try to compile all built-in the kernel? Or should I go for
> x11-drm?
>
> Cheers,
> Fernando
>
Just to add a new question:

- I'll need to connect a projector to my laptop. What do I need to do so?
Does it connect as the second monitor? If so, then would I need to reboot to
make it work?

Thanks,
Fernando

[-- Attachment #2: Type: text/html, Size: 1714 bytes --]

Re: [gentoo-user] struggling with dri

[Holly Bostick]

Fernando Meira schreef:
> On 10/10/05, Jason Cooper <gentoo@lakedaemon.net> wrote:
> 
>> Fernando Meira (fmeira@gmail.com) scribbled:
>> 
>>> I think I have radeon driver built-in the kernel.. does that mean
>>>  that
>> 
>> it is
>> 
>>> loaded before agpgart? agpgart and intel_agp are both modules...
>>> 
>>> should I them recompile my kernel and leave radeon as module?
>> 
>> yes.
> 
> 
> 
> Ok, with this modules being loaded at boot: agpgart intel_agp radeon
> 
> I still don't have rendering! So, should I try to compile all 
> built-in the kernel? Or should I go for x11-drm?
> 
> Cheers, Fernando
> 

I'm not sure I understand what you're doing here.

As far as I know (and I must stress that I'm not that familiar with
either the radeon driver or how it works with the Mobility chips,
because I have a 9800SE that must use the fglrx drivers to get OpenGL/3D
hardware acceleration/direct rendering), the radeon driver is a 2D
driver that is used in combination with the kernel's DRM and the Mesa
libraries to get direct rendering/3D hardware acceleration enabled.

So my first question would be:

What is the status of DRM in your kernel?

Device Drivers=>Character Devices=>Direct Rendering Manager (XFree86
4.1.0 and higher DRI support)

Direct Rendering Manager (XFree86 4.1.0 and higher DRI support
  x CONFIG_DRM:

  x

  x Kernel-level support for the Direct Rendering Infrastructure (DRI)
  x introduced in XFree86 4.0. If you say Y here, you need to select
  x the module that's right for your graphics card from the list below.
  x These modules provide support for synchronization, security, and
  x DMA transfers. Please see <http://dri.sourceforge.net/> for more
  x details.  You should also select and configure AGP

  x (/dev/agpgart) support.

  x

  x Symbol: DRM [=m]
  x Prompt: Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
  x   Defined at drivers/char/drm/Kconfig:7
  x   Depends on: AGP || AGP=n
  x   Location:
  x     -> Device Drivers
  x       -> Character devices
  x


Now, I know that for the fglrx drivers to run, this kernel option must
be *unset*, but it's clear that you can't even have the 'radeon' module
if DRM is not set. However, in looking at these settings in my own
kernel (and assuming that the Mobility chipset in your lappy can use
these drivers to provide 3D hardware acceleration), I noticed that:

- when I had /dev/agpgart set as a module, I could only build DRM as a
module (the kernel gave me a message to this effect);

- setting /dev/agpgart to statically compiled (Y) allowed me to build
DRM statically compiled (but I could still build Radeon as a module, and
intel_agp as a module under agpgart).

Again, I'm no big expert on the radeon kernel drivers, but I find it
hard to believe that in this situation it can be a good thing for
/dev/agpgart and /DRM themselves to be compiled as loadable modules
rather than statically (although the sub-functions, intel_agp and
radeon, most likely *should* be compiled as modules).

So I would suggest that your kernel config "should" look like this:

<*> /dev/agpgart (AGP Support)
< >   ALI chipset support
< >   ATI chipset support
< >   AMD Irongate, 761, and 762 chipset support
< >   AMD Opteron/Athlon64 on-CPU GART support
<M>   Intel 440LX/BX/GX, I8xx and E7x05 chipset support
< >   NVIDIA nForce/nForce2 chipset support
< >   SiS chipset support
< >   Serverworks LE/HE chipset support
< >   VIA chipset support
< >   Transmeta Efficeon support
<*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
< >   3dfx Banshee/Voodoo3+ (NEW)
< >   ATI Rage 128 (NEW)
<M>   ATI Radeon
< >   Intel I810 (NEW)
< >   Intel 830M, 845G, 852GM, 855GM, 865G
< >   Matrox g200/g400 (NEW)
< >   SiS video cards (NEW)

For what it's worth. You could then take agpgart out of
/etc/modules.autoload.d/kernel-2.6 (since it's no longer a loadable
module, you can't load it that way anyway. but then intel_agp should
hopefully load correctly).

You would perhaps also want to check your build of xorg:

emerge -pv xorg-x11

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] x11-base/xorg-x11-6.8.2-r4  -3dfx +3dnow +bitmap-fonts
-cjk -debug -dlloader -dmx -doc +font-server -insecure-drivers -ipv6
-minimal +mmx +nls -nocxx +opengl -pam -sdk +sse -static +truetype-fonts
+type1-fonts (-uclibc) +xprint +xv 0 kB

As you see, opengl support is *optional*, and if not compiled,
presumably the Mesa libraries that allow X to render 3D for those
drivers that don't do so natively would also not be available.


Hope this helps,
Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 4794 bytes --]

On 10/11/05, Holly Bostick <motub@planet.nl> wrote:
>
> Fernando Meira schreef:
> > On 10/10/05, Jason Cooper <gentoo@lakedaemon.net> wrote:
> >
> >> Fernando Meira (fmeira@gmail.com) scribbled:
> >>
> >>> I think I have radeon driver built-in the kernel.. does that mean
> >>> that
> >>
> >> it is
> >>
> >>> loaded before agpgart? agpgart and intel_agp are both modules...
> >>>
> >>> should I them recompile my kernel and leave radeon as module?
> >>
> >> yes.
> >
> >
> >
> > Ok, with this modules being loaded at boot: agpgart intel_agp radeon
> >
> > I still don't have rendering! So, should I try to compile all
> > built-in the kernel? Or should I go for x11-drm?
> >
> > Cheers, Fernando
> >
>
> I'm not sure I understand what you're doing here.
>
> As far as I know (and I must stress that I'm not that familiar with
> either the radeon driver or how it works with the Mobility chips,
> because I have a 9800SE that must use the fglrx drivers to get OpenGL/3D
> hardware acceleration/direct rendering), the radeon driver is a 2D
> driver that is used in combination with the kernel's DRM and the Mesa
> libraries to get direct rendering/3D hardware acceleration enabled.
>
> So my first question would be:
>
> What is the status of DRM in your kernel?
>
> Device Drivers=>Character Devices=>Direct Rendering Manager (XFree86
> 4.1.0 and higher DRI support)


It was DRM [=m].
All (agpgart, inter_agp, DRM, radeon) were [M].

Now, I know that for the fglrx drivers to run, this kernel option must
> be *unset*, but it's clear that you can't even have the 'radeon' module
> if DRM is not set. However, in looking at these settings in my own
> kernel (and assuming that the Mobility chipset in your lappy can use
> these drivers to provide 3D hardware acceleration), I noticed that:
>
> - when I had /dev/agpgart set as a module, I could only build DRM as a
> module (the kernel gave me a message to this effect);
>
> - setting /dev/agpgart to statically compiled (Y) allowed me to build
> DRM statically compiled (but I could still build Radeon as a module, and
> intel_agp as a module under agpgart).
>
> Again, I'm no big expert on the radeon kernel drivers, but I find it
> hard to believe that in this situation it can be a good thing for
> /dev/agpgart and /DRM themselves to be compiled as loadable modules
> rather than statically (although the sub-functions, intel_agp and
> radeon, most likely *should* be compiled as modules).
>

So I would suggest that your kernel config "should" look like this:
>
> <*> /dev/agpgart (AGP Support)
> < > ALI chipset support
> < > ATI chipset support
> < > AMD Irongate, 761, and 762 chipset support
> < > AMD Opteron/Athlon64 on-CPU GART support
> <M> Intel 440LX/BX/GX, I8xx and E7x05 chipset support
> < > NVIDIA nForce/nForce2 chipset support
> < > SiS chipset support
> < > Serverworks LE/HE chipset support
> < > VIA chipset support
> < > Transmeta Efficeon support
> <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
> < > 3dfx Banshee/Voodoo3+ (NEW)
> < > ATI Rage 128 (NEW)
> <M> ATI Radeon
> < > Intel I810 (NEW)
> < > Intel 830M, 845G, 852GM, 855GM, 865G
> < > Matrox g200/g400 (NEW)
> < > SiS video cards (NEW)


Ok, so I do as you say, change agpgart and DRM to be statically and leave
inter_agp and radeon as modules.
Exactly as you mention.

For what it's worth. You could then take agpgart out of
> /etc/modules.autoload.d/kernel-2.6 (since it's no longer a loadable
> module, you can't load it that way anyway. but then intel_agp should
> hopefully load correctly).


Yes... done!

You would perhaps also want to check your build of xorg:
>
> emerge -pv xorg-x11


Yes, I have opengl USE flag active and xorg-x1 compiled with it.

Hope this helps,
> Holly


Well, I really appreciate it, but it's still not working. All the same, no
errors and no rendering.
Xorg.0.log does not report any error, dmesg reports:

 agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode

and lsmod:
radeon 60800 1
intel_agp 15260 1

So.. don't know what can be wrong...

To add: now I lost the booting report!! After disabling DRM, FM support
(vesa-fb + ati + ddc/I2C) for trying fglrx driver.. I can't get back the
booting screen.. just a black screen from Grub to login manager.. The funny
part is that I re-set all these kernel option.. well, all less one, support
for FB splash (inside /Device Drivers/Graphics Support/Support for
framebuffer devices/), which I can't find anymore.. weird.. very weird...

any clue? to any of the problems?

Thanks,
Fernando

[-- Attachment #2: Type: text/html, Size: 6729 bytes --]

Re: [gentoo-user] struggling with dri

[gentoo_falstaff]

When I was using kernel 2.6.12 all was fine with these configuration
options:

<M> /dev/agpgart (AGP Support)
< >   ALI chipset support
< >   ATI chipset support
< >   AMD Irongate, 761, and 762 chipset support
< >   AMD Opteron/Athlon64 on-CPU GART support
<M>   Intel 440LX/BX/GX, I8xx and E7x05 chipset support
< >   NVIDIA nForce/nForce2 chipset support
< >   SiS chipset support
< >   Serverworks LE/HE chipset support
< >   VIA chipset support
< >   Transmeta Efficeon support
<M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
< >   3dfx Banshee/Voodoo3+ (NEW)
< >   ATI Rage 128 (NEW)
<M>   ATI Radeon
< >   Intel I810 (NEW)
< >   Intel 830M, 845G, 852GM, 855GM, 865G
< >   Matrox g200/g400 (NEW)
< >   SiS video cards (NEW)

When I compiled kernel 2.6.13   the AGP support was not recognized anymore
after "modprobe agpgart" or "insmod agpgart" followed by chipset module;
I was still
not using x11-drm package or ati-drivers.


Trying to install ati-drivers I found that my card was not supported...
   (P.S. after unmerging the package I had to issue the command
   opengl-update xorg-x11
   to switch back to Mesa opengl, otherwise the simple command "glxinfo"
will exit with errors...)


Trying to install x11-drm I had to disable the following options in the
kernel:

< > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
< >   3dfx Banshee/Voodoo3+ (NEW)
< >   ATI Rage 128 (NEW)
< >   ATI Radeon
< >   Intel I810 (NEW)
< >   Intel 830M, 845G, 852GM, 855GM, 865G
< >   Matrox g200/g400 (NEW)
< >   SiS video cards (NEW)

and I had to setup the variable
  VIDEO_CARDS="radeon"
in /etc/make.conf to compile the package.

After a correct compilation of  kernel and x11-drm, DRI was not running yet!
I tried this options in the kernel:

<*> /dev/agpgart (AGP Support)
< >   ALI chipset support
< >   ATI chipset support
< >   AMD Irongate, 761, and 762 chipset support
< >   AMD Opteron/Athlon64 on-CPU GART support
<*>   Intel 440LX/BX/GX, I8xx and E7x05 chipset support
< >   NVIDIA nForce/nForce2 chipset support
< >   SiS chipset support
< >   Serverworks LE/HE chipset support
< >   VIA chipset support
< >   Transmeta Efficeon support
< > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
< >   3dfx Banshee/Voodoo3+ (NEW)
< >   ATI Rage 128 (NEW)
< >   ATI Radeon
< >   Intel I810 (NEW)
< >   Intel 830M, 845G, 852GM, 855GM, 865G
< >   Matrox g200/g400 (NEW)
< >   SiS video cards (NEW)

and all was fine... Direct Rendering up and running!

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Douglas James Dunn]

[-- Attachment #1: Type: text/plain, Size: 3795 bytes --]

I had problems getting 2.6.13 to get working with my vid card went back
to 12

On Wed, 2005-10-12 at 09:08 +0200, gentoo_falstaff wrote:
> When I was using kernel 2.6.12 all was fine with these configuration
> options:
> 
> <M> /dev/agpgart (AGP Support)
> < >   ALI chipset support
> < >   ATI chipset support
> < >   AMD Irongate, 761, and 762 chipset support
> < >   AMD Opteron/Athlon64 on-CPU GART support
> <M>   Intel 440LX/BX/GX, I8xx and E7x05 chipset support
> < >   NVIDIA nForce/nForce2 chipset support
> < >   SiS chipset support
> < >   Serverworks LE/HE chipset support
> < >   VIA chipset support
> < >   Transmeta Efficeon support
> <M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
> < >   3dfx Banshee/Voodoo3+ (NEW)
> < >   ATI Rage 128 (NEW)
> <M>   ATI Radeon
> < >   Intel I810 (NEW)
> < >   Intel 830M, 845G, 852GM, 855GM, 865G
> < >   Matrox g200/g400 (NEW)
> < >   SiS video cards (NEW)
> 
> When I compiled kernel 2.6.13   the AGP support was not recognized anymore
> after "modprobe agpgart" or "insmod agpgart" followed by chipset module;
> I was still
> not using x11-drm package or ati-drivers.
> 
> 
> Trying to install ati-drivers I found that my card was not supported...
>    (P.S. after unmerging the package I had to issue the command
>    opengl-update xorg-x11
>    to switch back to Mesa opengl, otherwise the simple command "glxinfo"
> will exit with errors...)
> 
> 
> Trying to install x11-drm I had to disable the following options in the
> kernel:
> 
> < > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
> < >   3dfx Banshee/Voodoo3+ (NEW)
> < >   ATI Rage 128 (NEW)
> < >   ATI Radeon
> < >   Intel I810 (NEW)
> < >   Intel 830M, 845G, 852GM, 855GM, 865G
> < >   Matrox g200/g400 (NEW)
> < >   SiS video cards (NEW)
> 
> and I had to setup the variable
>   VIDEO_CARDS="radeon"
> in /etc/make.conf to compile the package.
> 
> After a correct compilation of  kernel and x11-drm, DRI was not running yet!
> I tried this options in the kernel:
> 
> <*> /dev/agpgart (AGP Support)
> < >   ALI chipset support
> < >   ATI chipset support
> < >   AMD Irongate, 761, and 762 chipset support
> < >   AMD Opteron/Athlon64 on-CPU GART support
> <*>   Intel 440LX/BX/GX, I8xx and E7x05 chipset support
> < >   NVIDIA nForce/nForce2 chipset support
> < >   SiS chipset support
> < >   Serverworks LE/HE chipset support
> < >   VIA chipset support
> < >   Transmeta Efficeon support
> < > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
> < >   3dfx Banshee/Voodoo3+ (NEW)
> < >   ATI Rage 128 (NEW)
> < >   ATI Radeon
> < >   Intel I810 (NEW)
> < >   Intel 830M, 845G, 852GM, 855GM, 865G
> < >   Matrox g200/g400 (NEW)
> < >   SiS video cards (NEW)
> 
> and all was fine... Direct Rendering up and running!
> 
-- 
Douglas James Dunn            .-.
468 South 7th street          /v\    L   I   N   U   X
Indiana, PA 15701            // \\  >Phear the Penguin<
cell: (724) 316-8266        /(   )\
Indiana University           ^^-^^
of Pennsylvania 

()  The ASCII Ribbon Campaign - against HTML Email,
/\  vCards, and proprietary formats.

                                           .
     .vir.                                d$b
  .d$$$$$$b.    .cd$$b.     .d$$b.   d$$$$$$$$$$$b  .d$$b.      .d$$b.
  $$$$( )$$$b d$$$()$$$.   d$$$$$$$b Q$$$$$$$P$$$P.$$$$$$$b.  .$$$$$$$b.
  Q$$$$$$$$$$B$$$$$$$$P"  d$$$PQ$$$$b.   $$$$.   .$$$P' `$$$ .$$$P' `$$$
    "$$$$$$$P Q$$$$$$$b  d$$$P   Q$$$$b  $$$$b   $$$$b..d$$$ $$$$b..d$$$
   d$$$$$$P"   "$$$$$$$$ Q$$$     Q$$$$  $$$$$   `Q$$$$$$$P  `Q$$$$$$$P
  $$$$$$$P       `"""""   ""        ""   Q$$$P     "Q$$$P"     "Q$$$P"
  `Q$$P"                                  """

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] struggling with dri

[Kevin Hanson]

><*> /dev/agpgart (AGP Support)
>< >   ALI chipset support
>< >   ATI chipset support
>< >   AMD Irongate, 761, and 762 chipset support
>< >   AMD Opteron/Athlon64 on-CPU GART support
><*>   Intel 440LX/BX/GX, I8xx and E7x05 chipset support
>< >   NVIDIA nForce/nForce2 chipset support
>< >   SiS chipset support
>< >   Serverworks LE/HE chipset support
>< >   VIA chipset support
>< >   Transmeta Efficeon support
>< > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
>< >   3dfx Banshee/Voodoo3+ (NEW)
>< >   ATI Rage 128 (NEW)
>< >   ATI Radeon
>< >   Intel I810 (NEW)
>< >   Intel 830M, 845G, 852GM, 855GM, 865G
>< >   Matrox g200/g400 (NEW)
>< >   SiS video cards (NEW)
>
>and all was fine... Direct Rendering up and running!
>
>  
>
This is what finally worked for me.  I am on a 2.6.13 kernel and until I 
built *BOTH* agpgart and intel-agp into the kernel instead of as 
modules, I was unable to get dri working.

I emerged x11-drm with VIDEO_CARDS="radeon".  The radeon driver and drm 
get loaded automatically when I start X.

I think this is an issue with the 2.6.13 kernel not liking agp compiled 
as a module.

Cheers,
Kevin
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Kevin Hanson]

Jason Cooper wrote:

>Kevin Hanson (tuxpert@comcast.net) scribbled:
>  
>
>>I've got a radeon mobility 9200 in my laptop and have compiled 
>>CONFIG_AGP=m, CONFIG_AGP_INTEL=m, CONFIG_DRM=m, and CONFIG_DRM_RADEON=m. 
>>
>>Interestingly enough, agpgart module loads at boot but intel_agp 
>>doesn't.  Modprobe of intel_agp produces no errors, but lsmod shows it's 
>>not loaded.  Nothing in log files either.  When X is started, drm and 
>>radeon modules load up, but dri still doesn't work, probably because agp 
>>isn't working.
>>    
>>
>
>Do you have agpgart in /etc/modules.autoload.d/kernel-2.6 ?  replace it
>with intel_agp, then place radeon on the line following.  intel_agp will
>draw in agpgart, and radeon must be loaded after those are in.
>
>hth,
>
>jason.
>  
>
The problem I'm having is that when I load intel-agp, it loads agpgart 
(as it is dependent on that), but intel-agp is never loaded.  No errors, 
no log file entries, nada.

Cheers,
Kevin
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[W.Kenworthy]

I looked at this thread and found intel-agp wasnt loaded.  Added (in
order) to the modules.autoload.d/kernel-2.6:

intel-agp
agpgart
drm
radeon

Rebooting resulted in no display once X started.  Commenting out
intel-agp got the display back on reboot.

Any ideas?  I am getting 300fps tops, when at times I have had over
2000fps using glxgears in the past so it should be able to do better.

BilLK

On Mon, 2005-10-10 at 12:47 -0500, Kevin Hanson wrote:
> Jason Cooper wrote:
> 
> >Kevin Hanson (tuxpert@comcast.net) scribbled:
> >  
...
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[gentoo_falstaff]

On my laptop with a Mobility Radeon M7 on I noticed the same problem
after a kernel recompilation (2.6 series ~x86 flag); that is I had
Direct Rendering switched off.
I was compiling AGP as a kernel module.
Actually I solved the problem compiling AGP directly in the kernel with
the chipset code too.
I'm also using x11-drm to obtain the correct Radeon driver compiled as a
module.

I made an attempt to use ati-drivers package but I found that it doesn't
complain my card anymore.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

On 10/11/05, gentoo_falstaff <gentoo_falstaff@tiscali.it> wrote:
>
> On my laptop with a Mobility Radeon M7 on I noticed the same problem
> after a kernel recompilation (2.6 series ~x86 flag); that is I had
> Direct Rendering switched off.
> I was compiling AGP as a kernel module.
> Actually I solved the problem compiling AGP directly in the kernel with
> the chipset code too.
> I'm also using x11-drm to obtain the correct Radeon driver compiled as a
> module.


Ok, good.. I'll do the same!! That or leave it radeon as module and not
built in as it is now.
Hopefully I'll have time to try that this afternoon.
I'm using x11-drm because the HOWTO mentioned that for 2.6-kernel it should
be..
If the first option doesn't solve my problem, I'll also give x11-drm a
try...

I made an attempt to use ati-drivers package but I found that it doesn't
> complain my card anymore.


Yah, same problem here!

Cheers,
Fernando

[-- Attachment #2: Type: text/html, Size: 1429 bytes --]

Re: [gentoo-user] struggling with dri

[Robert Svoboda]

* Fernando Meira <fmeira@gmail.com> [2005-10-09 23:10]:
> Hi,

Hi,

> I know this is a well discussed topic.. but I can't find answer to my
> problem.. and I'm completely lost in all mails/forums..
> 
> I have a ATI Technologies Inc Radeon Mobility M6 LY and I been using
> "radeon" driver from kernel.

I have M7 LW but they are very similar I believe...

> In order to enable rendering, I been looking around and after no success I
> was told that I should use fglrx driver from proprietary ATI-drivers! Tried
> it, but no deal! Then I was again told that these drivers were not to my
> card, and that radeon should made it.

Yes, I think so. 

> So, I'm back to radeon but still no rendering. However, there's noting
> saying the opposite unless:
> # glxinfo | grep -i rendering
> direct rendering: No

[...]

Did you compile agp, drm, radeon into kernel or as modules?
There are some issues (or at least there were) with this.

Mine works like this:
CONFIG_AGP=y
CONFIG_AGP_INTEL=y
CONFIG_DRM=y
CONFIG_DRM_RADEON=y

(Some people suggest compiling radeon as module but it works
for me this way)

Any dmesg output?

Robert
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]

On 10/12/05, Robert Svoboda <r080@atlas.cz> wrote:
>
> * Fernando Meira <fmeira@gmail.com> [2005-10-09 23:10]:
> > Hi,
>
> Hi,
>
> > I know this is a well discussed topic.. but I can't find answer to my
> > problem.. and I'm completely lost in all mails/forums..
> >
> > I have a ATI Technologies Inc Radeon Mobility M6 LY and I been using
> > "radeon" driver from kernel.
>
> I have M7 LW but they are very similar I believe...
>
> > In order to enable rendering, I been looking around and after no success
> I
> > was told that I should use fglrx driver from proprietary ATI-drivers!
> Tried
> > it, but no deal! Then I was again told that these drivers were not to my
> > card, and that radeon should made it.
>
> Yes, I think so.
>
> > So, I'm back to radeon but still no rendering. However, there's noting
> > saying the opposite unless:
> > # glxinfo | grep -i rendering
> > direct rendering: No
>
> [...]
>
> Did you compile agp, drm, radeon into kernel or as modules?
> There are some issues (or at least there were) with this.
>
> Mine works like this:
> CONFIG_AGP=y
> CONFIG_AGP_INTEL=y
> CONFIG_DRM=y
> CONFIG_DRM_RADEON=y
>
> (Some people suggest compiling radeon as module but it works
> for me this way)


I've already tried this both sets:
CONFIG_AGP=m
CONFIG_AGP_INTEL=m
CONFIG_DRM=m
CONFIG_DRM_RADEON=m

and

CONFIG_AGP=y
CONFIG_AGP_INTEL=m
CONFIG_DRM=y
CONFIG_DRM_RADEON=m

with no success... I'll try what works for you.. thanks!!
I'll post the results as soon as I have them!

Any dmesg output?


For what I've tried until now, there's no sign of errors or weird stuff..
all looks fine..

Cheers,
Fernando

[-- Attachment #2: Type: text/html, Size: 2314 bytes --]

Re: [gentoo-user] struggling with dri

[Fernando Meira]

[-- Attachment #1: Type: text/plain, Size: 15926 bytes --]

On 10/12/05, Robert Svoboda <r080@atlas.cz> wrote:
>
> [...]
> > So, I'm back to radeon but still no rendering. However, there's noting
> > saying the opposite unless:
> > # glxinfo | grep -i rendering
> > direct rendering: No
>
> [...]
>
> Did you compile agp, drm, radeon into kernel or as modules?
> There are some issues (or at least there were) with this.
>
> Mine works like this:
> CONFIG_AGP=y
> CONFIG_AGP_INTEL=y
> CONFIG_DRM=y
> CONFIG_DRM_RADEON=y
>
> (Some people suggest compiling radeon as module but it works
> for me this way)


Ok, so here I am again! This was the last kernel configuration that I could
try.. and still rendering: no!! I think this rendering fellow just doesn't
like me :(

Any dmesg output?


# dmesg
Linux version 2.6.12-suspend2-r6 (root@nandux) (gcc version 3.4.4 (Gentoo
3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #5 Thu Oct 13 00:42:09 CEST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001ffe0000 (usable)
BIOS-e820: 000000001ffe0000 - 000000001fff8000 (ACPI NVS)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 131040
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 126944 pages, LIFO batch:31
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 Acer ) @ 0x000fe030
ACPI: RSDT (v001 Acer TMH2 0x00000001 Acer 0x00000000) @ 0x1ffe0000
ACPI: FADT (v001 Acer TMH2 0x00000001 Acer 0x00000000) @ 0x1ffe0054
ACPI: BOOT (v001 Acer TMH2 0x00000001 Acer 0x00000000) @ 0x1ffe002c
ACPI: DSDT (v001 H2 H2 0x00001000 MSFT 0x0100000d) @ 0x00000000
Allocating PCI resources starting at 20000000 (gap: 1fff8000:dfff8000)
Built 1 zonelists
Kernel command line: root=/dev/hda1 vga=0x31A resume2=swap:/dev/hda3
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 2400.046 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x50
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 515560k/524160k available (2208k kernel code, 8112k reserved, 620k
data, 148k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 4734.97 BogoMIPS (lpj=2367488)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebf9ff 00000000 00000000 00000000
00000400 00000000 00000000
CPU: After vendor identify, caps: bfebf9ff 00000000 00000000 00000000
00000400 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: After all inits, caps: bfebf9ff 00000000 00000000 00000080 00000400
00000000 00000000
CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 07
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ACPI: setting ELCR to 0200 (from 0c00)
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf0200, last bus=2
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20050309
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:01:00.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Link [PILA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [PILC] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILD] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILE] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILF] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILG] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILH] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: Embedded Controller [EC0] (gpe 29)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 11 devices
SCSI subsystem initialized
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
report
pnp: 00:0a: ioport range 0xf100-0xf17f could not be reserved
pnp: 00:0a: ioport range 0xf200-0xf23f has been reserved
pnp: 00:0a: ioport range 0x4d0-0x4d1 has been reserved
pnp: 00:0a: ioport range 0x580-0x587 has been reserved
Simple Boot Flag at 0x6e set to 0x1
inotify device minor=63
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
lp: driver loaded but no devices found
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel i845 Chipset.
agpgart: AGP aperture is 256M @ 0xe0000000
[drm] Initialized drm 1.0.0 20040925
ACPI: PCI Interrupt Link [PILA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [PILA] -> GSI 11 (level, low) ->
IRQ 11
[drm] Initialized radeon 1.16.0 20050311 on minor 0:
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [PILA] -> GSI 11 (level, low) ->
IRQ 11
radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=175.00 Mhz, System=175.00MHz
radeonfb: PLL min 12000 max 35000
Non-DDC laptop panel detected
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type no found
radeonfb: panel ID string: Samsung LTN150P1-L02
radeonfb: detected LVDS panel size from BIOS: 1400x1050
radeondb: BIOS provided dividers will be used
radeonfb: Dynamic Clock Power Management enabled
radeonfb (0000:01:00.0): ATI Radeon LY
vesafb: ATI Technologies Inc., P6 , 01.00 (OEM: ATI MOBILITY RADEON)
vesafb: VBE version: 2.0
vesafb: protected mode interface info at c000:5229
vesafb: pmi: set display start = c00c52bd, set palette = c00c5309
vesafb: pmi: ports = a010 a016 a054 a038 a03c a05c a000 a004 a0b0 a0b2 a0b4
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
vesafb: scrolling: redraw
vesafb: cannot reserve video memory at 0x88000000
vesafb: framebuffer at 0x88000000, mapped to 0xe1980000, using 600k, total
32768k
fb1: VESA VGA frame buffer device
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Lid Switch [LID]
ACPI: Thermal Zone [THR1] (27 C)
ACPI: Thermal Zone [THR2] (36 C)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: PCI Interrupt Link [PILB] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [PILB] -> GSI 10 (level, low) ->
IRQ 10
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP]
lp0: using parport0 (interrupt-driven).
mice: PS/2 mouse device common for all mice
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
PPP generic driver version 2.4.2
8139too Fast Ethernet driver 0.9.27
ACPI: PCI Interrupt 0000:02:05.0[A] -> Link [PILB] -> GSI 10 (level, low) ->
IRQ 10
eth0: RealTek RTL8139 at 0xe082a800, 00:00:e2:8f:5b:59, IRQ 10
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
Linux video capture interface: v1.00
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH2: IDE controller at PCI slot 0000:00:1f.1
ICH2: chipset revision 5
ICH2: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xbc90-0xbc97, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xbc98-0xbc9f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
input: AT Translated Set 2 keyboard on isa0060/serio0
hda: HITACHI_DK23DA-40, ATA DISK drive
Synaptics Touchpad, model: 1, fw: 5.8, id: 0x9248b1, caps: 0x904713/0x4000
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: SONY CD-RW/DVD-ROM CRX810E, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
hda: max request size: 128KiB
hda: 78140160 sectors (40007 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hda: cache flushes supported
hda: hda1 hda2 < hda5 > hda3 hda4
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 8192kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ieee1394: Initialized config rom entry `ip1394'
ACPI: PCI Interrupt Link [PILC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [PILC] -> GSI 11 (level, low) ->
IRQ 11
Yenta: CardBus bridge found at 0000:02:09.0 [1025:1027]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:09.0, mfunc 0x01001022, devctl 0x64
Yenta: ISA IRQ mask 0x0038, PCI irq 11
Socket status: 30000006
ACPI: PCI Interrupt Link [PILG] enabled at IRQ 11
ACPI: PCI Interrupt 0000:02:09.1[B] -> Link [PILG] -> GSI 11 (level, low) ->
IRQ 11
Yenta: CardBus bridge found at 0000:02:09.1 [1025:1027]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:09.1, mfunc 0x01001022, devctl 0x64
Yenta: ISA IRQ mask 0x0038, PCI irq 11
Socket status: 30000020
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v2.2
ACPI: PCI Interrupt Link [PILD] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1f.2[D] -> Link [PILD] -> GSI 11 (level, low) ->
IRQ 11
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: UHCI Host Controller
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1f.2: irq 11, io base 0x00008000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt Link [PILH] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1f.4[C] -> Link [PILH] -> GSI 11 (level, low) ->
IRQ 11
PCI: Setting latency timer of device 0000:00:1f.4 to 64
uhci_hcd 0000:00:1f.4: UHCI Host Controller
uhci_hcd 0000:00:1f.4: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1f.4: irq 11, io base 0x00008060
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usb 2-1: new low speed USB device using uhci_hcd and address 2
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver hiddev
input: USB HID v1.10 Mouse [CHESEN USB MOUSE] on usb-0000:00:1f.4-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP established hash table entries: 32768 (order: 6, 262144 bytes)
TCP bind hash table entries: 32768 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 32768 bind 32768)
IPv4 over IPv4 tunneling driver
ip_conntrack version 2.1 (4095 buckets, 32760 max) - 204 bytes per conntrack
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available
Software Suspend Core.
Software Suspend Compression Driver loading.
Software Suspend Encryption Driver loading.
Software Suspend Swap Writer loading.
ACPI wakeup devices:
SLPB OZ68 OZ69 OBLN OBMO ICH2 LID
ACPI: (supports S0 S3 S4 S4bios S5)
Resume block device is c14d0280.
Software Suspend 2.1.9.9 <http://2.1.9.9>: Swapwriter: Signature found.
Software Suspend 2.1.9.9 <http://2.1.9.9>: Suspending enabled.
ReiserFS: hda1: found reiserfs format "3.6" with standard journal
ReiserFS: hda1: using ordered data mode
ReiserFS: hda1: journal params: device hda1, size 8192, journal first block
18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda1: checking transaction log (hda1)
ReiserFS: hda1: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 148k freed
Adding 506036k swap on /dev/hda3. Priority:-1 extents:1
ndiswrapper version 1.2 loaded (preempt=no,smp=no)
ndiswrapper: driver lsbcmnds (The Linksys Group, Inc.,07/17/2003,
3.30.15.0<http://3.30.15.0>)
loaded
PCI: Enabling device 0000:07:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:07:00.0[A] -> Link [PILG] -> GSI 11 (level, low) ->
IRQ 11
PCI: Setting latency timer of device 0000:07:00.0 to 64
ndiswrapper: using irq 11
wlan0: ndiswrapper ethernet device 00:12:17:10:42:d0 using driver lsbcmnds,
configuration file 14E4:4320:1737:4320.5.conf
wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP
usbcore: registered new driver spca50x
/var/tmp/portage/spca5xx-20041224/work/spca5xx-20041224/drivers/usb/spca50x.c:
spca5xx driver 0.55 registered
ReiserFS: hda4: found reiserfs format "3.6" with standard journal
ReiserFS: hda4: using ordered data mode
ReiserFS: hda4: journal params: device hda4, size 8192, journal first block
18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda4: checking transaction log (hda4)
ReiserFS: hda4: Using r5 hash to sort names
cdrom: open failed.
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [PILB] -> GSI 10 (level, low) ->
IRQ 10
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 49420 usecs
intel8x0: clocking to 48000
ohci1394: $Rev: 1250 $ Ben Collins <bcollins@debian.org>
ACPI: PCI Interrupt Link [PILF] enabled at IRQ 11
ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [PILF] -> GSI 11 (level, low) ->
IRQ 11
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11] MMIO=[80100000-801007ff]
Max Packet=[2048]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[fffdb7a700000000]
eth1394: $Rev: 1247 $ Ben Collins <bcollins@debian.org>
eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0x100-0x4ff: excluding 0x380-0x38f
cs: IO port probe 0x100-0x4ff: excluding 0x380-0x38f
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0xa00-0xaff: clean.
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode

Even Xorg' log says:

(II) RADEON(0): Direct rendering enabled

This is just playing with me...

Fernando

[-- Attachment #2: Type: text/html, Size: 18403 bytes --]