[gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Hi everyone,

I've been using Xgl for quite a long time without any serious problems.
Recently I've tried to launch America's Army (emerged one, version
2.5.0) on my box, but...

~ armyops
Xlib:  extension "XFree86-DRI" missing on display ":1.0".
Cheat protection disabled
open /dev/[sound/]mixer: No such file or directory
WARNING: ALC_EXT_capture is subject to change!
Either GL_EXT_bgra or glDrawRangeElements not supported- bailing out.
History:
Exiting due to error

Being quite disappointed I verified the first line of the output above
with glxinfo. And so...

~ glxinfo
name of display: :1.0
Xlib:  extension "XFree86-DRI" missing on display ":1.0".
display: :1  screen: 0
direct rendering: No
<snip>

It sounds rather unbelievably. I've got running Xgl with Beryl's
dazzling animations and I'm informed that despite having over 4000 FPS
on glxgears I have not got direct rendering. What the...?

Few days later I've accidentally launched Xorg (using startx script)
instead of my Xgl. When I entered my old, two-dimension desktop I
thought that trying America's Army over here, without Xgl, could tell me
something more (i.e. that something's wrong with my configuration or
whatever else). So I typed armyops in the terminal... And surprisingly
enough the game has started. Furthermore, the framerate was quite
satisfactory.

After this quite long introduction I'll finally get to the point. I have
got two questions.

1. Is it possible to enable somehow direct rendering on Xgl, therefore
allowing OpenGL apps to work as ought to.

2. If the answer to the first questions is "NO", then is there a method
of choosing which Xserver to use? Can I choose whether I'd like to
launch Xorg or Xgl? Or maybe I can even enable such choice in GDM login
screen?

If you need any further information regarding by box please don't
hesitate to ask. Any support would be highly appreciated.

Best regards,
Jan Stępień

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Hemmann, Volker Armin]

On Thursday 18 January 2007 18:32, Jan Stępień wrote:
> Hi everyone,
>
> I've been using Xgl for quite a long time without any serious problems.
> Recently I've tried to launch America's Army (emerged one, version
> 2.5.0) on my box, but...
>
> ~ armyops
> Xlib:  extension "XFree86-DRI" missing on display ":1.0".
> Cheat protection disabled
> open /dev/[sound/]mixer: No such file or directory
> WARNING: ALC_EXT_capture is subject to change!
> Either GL_EXT_bgra or glDrawRangeElements not supported- bailing out.
> History:
> Exiting due to error
>
> Being quite disappointed I verified the first line of the output above
> with glxinfo. And so...
>
> ~ glxinfo
> name of display: :1.0
> Xlib:  extension "XFree86-DRI" missing on display ":1.0".
> display: :1  screen: 0
> direct rendering: No
> <snip>
>
> It sounds rather unbelievably. I've got running Xgl with Beryl's
> dazzling animations and I'm informed that despite having over 4000 FPS
> on glxgears I have not got direct rendering. What the...?

glxgears is not a benchmark.
it might be unbelievable, but it is true. If you use Xgl, no direct rendering 
there.


>
> Few days later I've accidentally launched Xorg (using startx script)
> instead of my Xgl. When I entered my old, two-dimension desktop I
> thought that trying America's Army over here, without Xgl, could tell me
> something more (i.e. that something's wrong with my configuration or
> whatever else). So I typed armyops in the terminal... And surprisingly
> enough the game has started. Furthermore, the framerate was quite
> satisfactory.

that is normal too.

>
> After this quite long introduction I'll finally get to the point. I have
> got two questions.
>
> 1. Is it possible to enable somehow direct rendering on Xgl, therefore
> allowing OpenGL apps to work as ought to.

nope. It isn't.
Xgl and direct rendering are exclusive. One or the other.

>
> 2. If the answer to the first questions is "NO", then is there a method
> of choosing which Xserver to use? Can I choose whether I'd like to
> launch Xorg or Xgl? Or maybe I can even enable such choice in GDM login
> screen?

Yes. 

Or you can start a second X with xinit. So you would have one desktop (on F7) 
with Xgl and one (F8) with 'normal' X.

Any reason, you are using Xgl? No Aiglx with your card?


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

On 18 Sty, 19:50, "Hemmann, Volker Armin"
<volker.armin.hemm...@tu-clausthal.de> wrote:
> nope. It isn't.
> Xgl and direct rendering are exclusive. One or the other.
>

Pity. That would be lovely.

>
> Yes.
>
> Or you can start a second X with xinit. So you would have one
> desktop (on F7)
> with Xgl and one (F8) with 'normal' X.
>

This method sounds interesting, but I have some doubts. Won't two
separate X servers be too big challenge for my box? I've got an Athlon
XP 3000+ (working at 2167 MHz) plus a GB of RAM. Having Xgl loaded in
the background could be deadly for performance in OpenGL apps on Xorg.
Please correct me if I'm wrong.

> Any reason, you are using Xgl? No Aiglx with your card?
>

Actually, I haven't though about it. I've got an ATI Radeon 9600XT
running on proprietary drivers (emerged ati-drivers). It works fine, as
long as you can tell that Radeon works fine on Linux; I haven't got any
experience with NVidia's hardware. Returning to the topic, I haven't got
an idea neither whether Aiglx works with my Radeon nor why I'm not using
Aiglx. When I've started to play with fancy 3D servers I was using
Debian, and I found an article describing quite precisely how to get Xgl
running on unstable Debian. Worked fine, so I've found Xgl a nice
choice. Am I mistaken?

Thanks for your feedback,

Best regards,
Jan Stępień
-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Novensiles divi Flamen]

On Friday 19 January 2007 09:17, Jan Stępień wrote:
> >
> > Or you can start a second X with xinit. So you would have one
> > desktop (on F7)
> > with Xgl and one (F8) with 'normal' X.
>
> This method sounds interesting, but I have some doubts. Won't two
> separate X servers be too big challenge for my box? I've got an Athlon
> XP 3000+ (working at 2167 MHz) plus a GB of RAM. Having Xgl loaded in
> the background could be deadly for performance in OpenGL apps on Xorg.
> Please correct me if I'm wrong.
>
I use a script called xlaunch:

http://forums.gentoo.org/viewtopic-t-483004-highlight-xlaunch.html

I run it on my laptop and have absolutely no problems, the xserver alone won't 
kill your performance.

- Noven
-- 
>-- Novensiles divi Flamen --<
>---- Miles Militis Fons ----<

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Hemmann, Volker Armin]

On Thursday 18 January 2007 23:47, Jan Stępień wrote:
> On 18 Sty, 19:50, "Hemmann, Volker Armin"
>
> <volker.armin.hemm...@tu-clausthal.de> wrote:
> > nope. It isn't.
> > Xgl and direct rendering are exclusive. One or the other.
>
> Pity. That would be lovely.
>
> > Yes.
> >
> > Or you can start a second X with xinit. So you would have one
> > desktop (on F7)
> > with Xgl and one (F8) with 'normal' X.
>
> This method sounds interesting, but I have some doubts. Won't two
> separate X servers be too big challenge for my box? I've got an Athlon
> XP 3000+ (working at 2167 MHz) plus a GB of RAM. Having Xgl loaded in
> the background could be deadly for performance in OpenGL apps on Xorg.
> Please correct me if I'm wrong.

well, I played ut2004 on my amd64 3200+/gf6600. One instance of Xgl one with 
naked X (and a xterm). Worked well enough.

>
> > Any reason, you are using Xgl? No Aiglx with your card?
>
> Actually, I haven't though about it. I've got an ATI Radeon 9600XT
> running on proprietary drivers (emerged ati-drivers). It works fine, as
> long as you can tell that Radeon works fine on Linux; I haven't got any
> experience with NVidia's hardware. Returning to the topic, I haven't got
> an idea neither whether Aiglx works with my Radeon nor why I'm not using
> Aiglx. When I've started to play with fancy 3D servers I was using
> Debian, and I found an article describing quite precisely how to get Xgl
> running on unstable Debian. Worked fine, so I've found Xgl a nice
> choice. Am I mistaken?

I don't know which drivers support AIGLX, but with aiglx (or nvidia), you can 
go from eye-candy-to-fast-to-eye-candy with two mouseclicks. (start 
beryl-manager, choose beryl from the menu for eye candy or your other wm, for 
speed).

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Fredrik Tolf]

On Thu, 2007-01-18 at 23:47 +0100, Jan Stępień wrote:
> On 18 Sty, 19:50, "Hemmann, Volker Armin"
> <volker.armin.hemm...@tu-clausthal.de> wrote:
> > nope. It isn't.
> > Xgl and direct rendering are exclusive. One or the other.
> 
> Pity. That would be lovely.

I'm no expert, but as far as I know, that's the reason why AIGLX
succeeded Xgl. So if you ask me, I think AIGLX (if it works with ATI)
would be the solution to your problem.

Fredrik Tolf




-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Novensiles divi Flamen napisał(a):
> I use a script called xlaunch:
>
> http://forums.gentoo.org/viewtopic-t-483004-highlight-xlaunch.html
>
> I run it on my laptop and have absolutely no problems, the xserver
alone won't
> kill your performance.
>
> - Noven

Thanks, sounds interesting.

Hemmann, Volker Armin napisał(a):
>
> I don't know which drivers support AIGLX, but with aiglx (or nvidia),
> you can
> go from eye-candy-to-fast-to-eye-candy with two mouseclicks. (start
> beryl-manager, choose beryl from the menu for eye candy or your
> other wm, for
> speed).
>

Fredrik Tolf napisał(a):
> I'm no expert, but as far as I know, that's the reason why AIGLX
> succeeded Xgl. So if you ask me, I think AIGLX (if it works with ATI)
> would be the solution to your problem.
> 

Fair enough. Firstly I'll check whether AIGLX will be working with my
video card, and in case of failure I'll give xlaunch a shot.

Thanks for support, guys,

Regards,
Jan Stępień

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Jan Stępień napisał(a):
> 
> Fair enough. Firstly I'll check whether AIGLX will be working with my
> video card, and in case of failure I'll give xlaunch a shot.
> 

I've reemerged Xorg adding "aiglx" to USE variable, modified
/etc/X11/xorg.conf (actually I've been following these instructions:
http://gentoo-wiki.com/HOWTO_AIGLX) and tried to launch Xorg with AIGLX.
Unfortunately efforts were fruitless. Accordingly to article mentioned
above I have to enable composite in xorg.conf:

Section "Extensions"
        Option         "Composite"   "Enable"
EndSection

After launching X server with this setting it results in using Mesa
instead of fglrx, which means NO direct rendering, as proved by glxinfo.
Beryl cannot be launched because of lack of DRI.

If I turn composite off, the X server is driven by fglrx, which gives me
direct rendering and Beryl's refusal to start because of lack of
composite extension.

It's all quite suspicious, taking into account fact that Radeons are
listed at the website above as video cards able of running AIGLX. But
maybe only on FOSS drivers...?

Afterwards I've downloaded xlaunch. When trying to launch an app (in
this case armyops) starting xlaunch in a terminal in an existing X
server the screen blacks out, probably trying to launch new X session
and suddenly restarts GDM, meanwhile killing my original session.

I've also tried to use xlaunch in a text console having my previous X
server turned on. Results are the same.

Have you got any suggestions?

Best regards,
Jan Stępień

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Hemmann, Volker Armin napisał(a):
> On Thursday 18 January 2007 23:47, Jan Stępień wrote:
>> On 18 Sty, 19:50, "Hemmann, Volker Armin"
>>>
>>> Or you can start a second X with xinit. So you would have one
>>> desktop (on F7)
>>> with Xgl and one (F8) with 'normal' X.
>> This method sounds interesting, but I have some doubts. Won't two
>> separate X servers be too big challenge for my box? I've got an Athlon
>> XP 3000+ (working at 2167 MHz) plus a GB of RAM. Having Xgl loaded in
>> the background could be deadly for performance in OpenGL apps on Xorg.
>> Please correct me if I'm wrong.
> 
> well, I played ut2004 on my amd64 3200+/gf6600. One instance of Xgl one with 
> naked X (and a xterm). Worked well enough.
> 

I managed to launch two X servers at one time, however I'm still far
from being successful. My /usr/share/gdm/defaults.conf

<snip>

[servers]
0=Standard
1=Xgl

[server-Standard]
name=Standard server
command=/usr/bin/X -audit 0
priority=0

[server-Xgl]
name=Xgl
command=/usr/bin/Xgl :1 -ac -accel glx:pbuffer -accel xv:pbuffer
flexible=true
chooser=false
handled=true
priority=0

<snip>

When entering default runlevel GDM starts and launches both servers.
First one, Standard, has got direct rendering turned on and OpenGL is
rendered by fglrx driver. OpenGL apps work fine. On the other hand
second server, Xgl, has not got direct rendering, and what is most
suspicious, it uses Mesa drivers, which cause Beryl to run at an
absolutely unacceptable performance. Why both servers are not rendered
using fglrx? Have you got any ideas how to do it?

Regards,
Jan

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Richard Fish]

On 1/19/07, Jan Stępień <jan@stepien.com.pl> wrote:
> When entering default runlevel GDM starts and launches both servers.
> First one, Standard, has got direct rendering turned on and OpenGL is
> rendered by fglrx driver. OpenGL apps work fine. On the other hand
> second server, Xgl, has not got direct rendering, and what is most
> suspicious, it uses Mesa drivers, which cause Beryl to run at an
> absolutely unacceptable performance. Why both servers are not rendered
> using fglrx? Have you got any ideas how to do it?

Have you checked your /var/log/Xorg.*.log files?  They should reflect
why the Xgl server is not being accellerated.

Also, one other option may be to try the opensource radeon driver.
You can lookup your card's pci ID (use lspci && lspci -n) in
/usr/src/linux/drivers/char/drm/drm_pciids.h to see if it is supported
or not.  If so, you should be able to get aiglx working with
opensource drivers.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Richard Fish napisał(a):
> Have you checked your /var/log/Xorg.*.log files?  They should reflect
> why the Xgl server is not being accellerated.

Got it! Somewhere around 92% of /var/log/Xorg.94.log, which is logging
Xgl, I've found:

(EE) fglrx(0): Hardware has already been locked.
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0x2000 at 0xb7f7b000
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed!                  *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO)             *
(WW) fglrx(0): * no 3D acceleration available                *
(WW) fglrx(0): ********************************************* *

Hardware's locked? Do they mean that I can render only one X server
simultaneously? They must be kidding...

And near the end of this file:

(EE) AIGLX: Screen 0 is not DRI capable

No doubt about it.

What's also interesting at the 96th per cent of Xorg.0.log, standard
server's log, I've got:

(EE) AIGLX error: dlopen of /usr/lib/dri/fglrx_dri.so failed
(/usr/lib/dri/fglrx_dri.so: cannot open shared object file: No such file
or directory)
(EE) AIGLX: reverting to software rendering

Did portage forgotten about something while emerging ati-drivers? Or
maybe it's my mistake to force AIGLX to start ('Option  "AIGLX" "true"'
in xorg.conf)?

> Also, one other option may be to try the opensource radeon driver.
> You can lookup your card's pci ID (use lspci && lspci -n) in
> /usr/src/linux/drivers/char/drm/drm_pciids.h to see if it is supported
> or not.  If so, you should be able to get aiglx working with
> opensource drivers.

Found it. In the section radeon_PCI_IDS I've found the following line:

{0x1002, 0x4152, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350}, \

Please verify my plan. I should recompile my kernel with device drivers
-> character devices -> radeon built in (or as a module) and in
xorg.conf set driver to "radeon". Am I right?

Thanks for your feedback,
Jan

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Hemmann, Volker Armin]

On Friday 19 January 2007 15:01, Jan Stępień wrote:
> Jan Stępień napisał(a):
> > Fair enough. Firstly I'll check whether AIGLX will be working with my
> > video card, and in case of failure I'll give xlaunch a shot.
>
> I've reemerged Xorg adding "aiglx" to USE variable, modified
> /etc/X11/xorg.conf (actually I've been following these instructions:
> http://gentoo-wiki.com/HOWTO_AIGLX) and tried to launch Xorg with AIGLX.
> Unfortunately efforts were fruitless. Accordingly to article mentioned
> above I have to enable composite in xorg.conf:
>
> Section "Extensions"
>         Option         "Composite"   "Enable"
> EndSection
>
> After launching X server with this setting it results in using Mesa
> instead of fglrx, which means NO direct rendering, as proved by glxinfo.
> Beryl cannot be launched because of lack of DRI.
>
> If I turn composite off, the X server is driven by fglrx, which gives me
> direct rendering and Beryl's refusal to start because of lack of
> composite extension.
>
> It's all quite suspicious, taking into account fact that Radeons are
> listed at the website above as video cards able of running AIGLX. But
> maybe only on FOSS drivers...?
>
> Afterwards I've downloaded xlaunch. When trying to launch an app (in
> this case armyops) starting xlaunch in a terminal in an existing X
> server the screen blacks out, probably trying to launch new X session
> and suddenly restarts GDM, meanwhile killing my original session.
>
> I've also tried to use xlaunch in a text console having my previous X
> server turned on. Results are the same.
>
> Have you got any suggestions?

Sounds like you are out of luck. The open drivers with AIGLX support don't 
support your card and the closed ones don't support AIGLX.

So your only hope: Xgl and a second X. That is a little bit sad. Send 
your 'thank yous' to ATI.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Richard Fish]

On 1/19/07, Jan Stępień <jan@stepien.com.pl> wrote:
> Please verify my plan. I should recompile my kernel with device drivers
> -> character devices -> radeon built in (or as a module) and in
> xorg.conf set driver to "radeon". Am I right?

Yeah, I think that will work.  Good luck!

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Novensiles divi Flamen]

On Saturday 20 January 2007 00:31, Jan Stępień wrote:
> After launching X server with this setting it results in using Mesa
> instead of fglrx, which means NO direct rendering, as proved by glxinfo.
> Beryl cannot be launched because of lack of DRI.
>
> If I turn composite off, the X server is driven by fglrx, which gives me
> direct rendering and Beryl's refusal to start because of lack of
> composite extension.
>
> It's all quite suspicious, taking into account fact that Radeons are
> listed at the website above as video cards able of running AIGLX. But
> maybe only on FOSS drivers...?
>
It might be a proprietary drive issue. I use an intel chipset - composite on, 
direct rendering, AIGLX and Beryl all working together. Just as the wiki 
tells you to do.

> Afterwards I've downloaded xlaunch. When trying to launch an app (in
> this case armyops) starting xlaunch in a terminal in an existing X
> server the screen blacks out, probably trying to launch new X session
> and suddenly restarts GDM, meanwhile killing my original session.
>

> I've also tried to use xlaunch in a text console having my previous X
> server turned on. Results are the same.
>
> Have you got any suggestions?
>
Try turning off GDM, logging in via console and then running startx. Then from 
inside that xserver use xlaunch to start the game, see if the results are any 
different. Xlaunch works perfectly for me from within KDE or enlightenment, 
although I've never had GDM running (or even installed) on this machine.

- Noven
-- 
>-- Novensiles divi Flamen --<
>---- Miles Militis Fons ----<

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Richard Fish napisał(a):
> On 1/19/07, Jan Stępień <jan@stepien.com.pl> wrote:
>> Please verify my plan. I should recompile my kernel with device drivers
>> -> character devices -> radeon built in (or as a module) and in
>> xorg.conf set driver to "radeon". Am I right?
> 
> Yeah, I think that will work.  Good luck!
> 
> -Richard
> 

New problems came up.

# modprobe radeon
WARNING: Error inserting drm
(/lib/modules/2.6.18-gentoo-r4/kernel/drivers/char/drm/drm.ko): Cannot
allocate memory
FATAL: Error inserting radeon
(/lib/modules/2.6.18-gentoo-r4/kernel/drivers/char/drm/radeon.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

# dmesg | grep radeon
radeonfb: Found Intel x86 BIOS ROM Image
radeonfb: Retrieved PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=500.00 Mhz,
System=297.00 MHz
radeonfb: PLL min 20000 max 40000
radeonfb: Monitor 1 type CRT found
radeonfb: EDID probed
radeonfb: Monitor 2 type no found
radeonfb (0000:01:00.0): ATI Radeon AR
radeon: Unknown symbol drm_open
radeon: Unknown symbol drm_fasync
radeon: Unknown symbol drm_poll
radeon: Unknown symbol drm_get_resource_len
radeon: Unknown symbol drm_core_get_reg_ofs
radeon: Unknown symbol drm_irq_uninstall
radeon: Unknown symbol drm_ioctl
radeon: Unknown symbol drm_exit
radeon: Unknown symbol drm_debug
radeon: Unknown symbol drm_core_get_map_ofs
radeon: Unknown symbol drm_init
radeon: Unknown symbol drm_addmap
radeon: Unknown symbol drm_ioremapfree
radeon: Unknown symbol drm_ioremap
radeon: Unknown symbol drm_get_resource_start
radeon: Unknown symbol drm_vbl_send_signals
radeon: Unknown symbol drm_ati_pcigart_init
radeon: Unknown symbol drm_mmap
radeon: Unknown symbol drm_order
radeon: Unknown symbol drm_ati_pcigart_cleanup
radeon: Unknown symbol drm_core_reclaim_buffers
radeon: Unknown symbol drm_release
radeon: Unknown symbol drm_open
radeon: Unknown symbol drm_fasync
radeon: Unknown symbol drm_poll
radeon: Unknown symbol drm_get_resource_len
radeon: Unknown symbol drm_core_get_reg_ofs
radeon: Unknown symbol drm_irq_uninstall
radeon: Unknown symbol drm_ioctl
radeon: Unknown symbol drm_exit
radeon: Unknown symbol drm_debug
radeon: Unknown symbol drm_core_get_map_ofs
radeon: Unknown symbol drm_init
radeon: Unknown symbol drm_addmap
radeon: Unknown symbol drm_ioremapfree
radeon: Unknown symbol drm_ioremap
radeon: Unknown symbol drm_get_resource_start
radeon: Unknown symbol drm_vbl_send_signals
radeon: Unknown symbol drm_ati_pcigart_init
radeon: Unknown symbol drm_mmap
radeon: Unknown symbol drm_order
radeon: Unknown symbol drm_ati_pcigart_cleanup
radeon: Unknown symbol drm_core_reclaim_buffers
radeon: Unknown symbol drm_release

Any ideas?

Regards,
Jan

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Richard Fish]

On 1/20/07, Jan Stępień <jan@stepien.com.pl> wrote:
> (/lib/modules/2.6.18-gentoo-r4/kernel/drivers/char/drm/drm.ko): Cannot
> allocate memory

Try searching dmesg for drm.  My guess is either the radeonfb module
is conflicting, or the fglrx module.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

Richard Fish napisał(a):
> On 1/20/07, Jan Stępień <jan@stepien.com.pl> wrote:
>> (/lib/modules/2.6.18-gentoo-r4/kernel/drivers/char/drm/drm.ko): Cannot
>> allocate memory
> 
> Try searching dmesg for drm.  My guess is either the radeonfb module
> is conflicting, or the fglrx module.
> 
> -Richard
> 

In fact the  radeon module conflicts with fglrx. I've unloaded fglrx, 
modprobed radeon (verified by lsmod) and relaunched gdm. But it's still 
refusing to use the new module:

(EE) Failed to load module "radeon" (module does not exist, 0)

Actually it does exist, it is loaded and besides listed in xorg.conf to 
be bound to my Radeon 9600XT. I'm can't get it. Any suggestions?

Thankful for your support so far and still asking for help, sincerely yours,

Jan

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Mick]

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

On Monday 22 January 2007 17:29, Jan Stępień wrote:

> In fact the  radeon module conflicts with fglrx. I've unloaded fglrx,
> modprobed radeon (verified by lsmod) and relaunched gdm. But it's still
> refusing to use the new module:
>
> (EE) Failed to load module "radeon" (module does not exist, 0)
>
> Actually it does exist, it is loaded and besides listed in xorg.conf to
> be bound to my Radeon 9600XT. I'm can't get it. Any suggestions?

Did you try remerging xorg with the radeon VIDEO_DEVICE flag after you removed 
the fglrx module?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Richard Fish]

On 1/22/07, Jan Stępień <jan@stepien.com.pl> wrote:
> In fact the  radeon module conflicts with fglrx. I've unloaded fglrx,
> modprobed radeon (verified by lsmod) and relaunched gdm. But it's still
> refusing to use the new module:
>
> (EE) Failed to load module "radeon" (module does not exist, 0)
>
> Actually it does exist, it is loaded and besides listed in xorg.conf to
> be bound to my Radeon 9600XT. I'm can't get it. Any suggestions?

Hmm, can you post your current xorg.conf and dmesg outputs?

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Boyd Stephen Smith Jr.]

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

On Monday 22 January 2007 11:29, Jan Stępień <jan@stepien.com.pl> wrote 
about 'Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg 
or Xgl, sir?'':
> In fact the  radeon module conflicts with fglrx. I've unloaded fglrx,
> modprobed radeon (verified by lsmod) and relaunched gdm. But it's still
> refusing to use the new module:
>
> (EE) Failed to load module "radeon" (module does not exist, 0)
>
> Actually it does exist, it is loaded and besides listed in xorg.conf to
> be bound to my Radeon 9600XT. I'm can't get it. Any suggestions?

Okay, this might not, be helpful but I just want to do a sanity check here:  

1. Check your xorg.log and make sure you are using the xorg.conf you think 
you are.

2. Make sure the required kernel module is in place.  It can be loaded by 
modprobe and that action confirmed by lsmod.  It will be somewhere 
under /lib/modules (sounds like you've already done this).

3. Make sure you aren't confusing a kernel module/driver with a X11 driver.  
Generally the later depends on the former, but they are provided by 
different packages and located differently on the filesystem -- and 
generally kernel modules are not listed by name in xorg.conf.

-- 
Boyd Stephen Smith Jr.             ,= ,-_-. =. 
bss03@volumehost.net              ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy   `-'(. .)`-' 
http://iguanasuicide.org/              \_/     

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Mick napisał(a):
> On Monday 22 January 2007 17:29, Jan Stępień wrote:
> 
>> In fact the  radeon module conflicts with fglrx. I've unloaded fglrx,
>> modprobed radeon (verified by lsmod) and relaunched gdm. But it's still
>> refusing to use the new module:
>>
>> (EE) Failed to load module "radeon" (module does not exist, 0)
>>
>> Actually it does exist, it is loaded and besides listed in xorg.conf to
>> be bound to my Radeon 9600XT. I'm can't get it. Any suggestions?
> 
> Did you try remerging xorg with the radeon VIDEO_DEVICE flag after you removed 
> the fglrx module?

Actually I haven't heard about this flag. I've just googled for it but
without any reasonably results. Could you tell me more about it or send
me a link to a proper website which could enlighten me?

Thanks in advance,

Jan

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

[-- Attachment #1.1: Type: text/plain, Size: 754 bytes --]

Richard Fish napisał(a):
> On 1/22/07, Jan Stępień <jan@stepien.com.pl> wrote:
>> In fact the  radeon module conflicts with fglrx. I've unloaded fglrx,
>> modprobed radeon (verified by lsmod) and relaunched gdm. But it's still
>> refusing to use the new module:
>>
>> (EE) Failed to load module "radeon" (module does not exist, 0)
>>
>> Actually it does exist, it is loaded and besides listed in xorg.conf to
>> be bound to my Radeon 9600XT. I'm can't get it. Any suggestions?
> 
> Hmm, can you post your current xorg.conf and dmesg outputs?
> 
> -Richard
> 

Of course. Output of dmesg and xorg.conf attached.

Regards,
Jan

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl

[-- Attachment #1.2: xorg.conf --]
[-- Type: text/plain, Size: 2564 bytes --]

Section "ServerLayout"
	Identifier     "Simple Layout"
	Screen      0  "aticonfig-Screen[0]" 0 0
	InputDevice    "Mouse1" "CorePointer"
	InputDevice    "Keyboard1" "CoreKeyboard"
#	Option	"AIGLX"	"true"
EndSection

Section "Files"
#    FontPath   "/usr/share/fonts/TTF/"
#    FontPath   "/usr/share/fonts/OTF"
#    FontPath   "/usr/share/fonts/CID/"
#    FontPath   "/usr/lib/X11/fonts/local/"
#    FontPath   "/usr/lib/X11/fonts/misc/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/lib/X11/fonts/Type1/"
#    FontPath   "/usr/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/lib/X11/fonts/freefont/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/"
#    FontPath   "/usr/lib/X11/fonts/100dpi/"
	FontPath     "/usr/share/fonts/misc/"
	FontPath     "/usr/share/fonts/Type1/"
	FontPath     "/usr/share/fonts/100dpi/"
	FontPath     "/usr/share/fonts/75dpi/"
EndSection

Section "Module"
	Load        "type1"
	Load        "speedo"
	Load  "dbe"  	# Double buffer extension
	SubSection "extmod"
		Option	    "omit xfree86-dga"   # don't initialise the DGA extension
	EndSubSection
	Load  "freetype"
	Load  "xtt"
	Load  "dri"
	Load  "glx"
EndSection

Section "InputDevice"

	Identifier  "Keyboard1"
	Driver      "kbd"
	Option	    "AutoRepeat" "500 30"
	Option	    "XkbRules" "xorg"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "pl"
EndSection

Section "InputDevice"
	Identifier  "Mouse1"
	Driver      "mouse"
	Option	    "Protocol" "ExplorerPS/2"	# Explorer PS/2
	Option	    "Device" "/dev/psaux"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection

Section "Device"
	Identifier  "aticonfig-Device[0]"
#	Driver      "radeon"
	Driver      "fglrx"
	Option	"UseInternalAGPGART" "no"
	Option "VideoOverlay"   "on"
	Option "OpenGLOverlay"  "off"
#	Option "DRI" "on"
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]"
	Device     "aticonfig-Device[0]"
	Monitor    "aticonfig-Monitor[0]"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1280x1024" "1024x768" "800x600" "640x480"
	EndSubSection
EndSection

Section "dri"
	Mode 0666
EndSection

#Section "Extensions"
#	Option "Composite" "Enable"
#EndSection

[-- Attachment #1.3: dmesg --]
[-- Type: text/plain, Size: 12981 bytes --]

Linux version 2.6.19-gentoo-r4 (root@jano-desktop-gentoo) (gcc version 4.1.1 (Gentoo 4.1.1-r3)) #1 Sun Jan 21 23:34:32 CET 2007
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000003fffc000 (usable)
 BIOS-e820: 000000003fffc000 - 000000003ffff000 (ACPI data)
 BIOS-e820: 000000003ffff000 - 0000000040000000 (ACPI NVS)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Warning only 896MB will be used.
Use a HIGHMEM enabled kernel.
896MB LOWMEM available.
Entering add_active_range(0, 0, 229376) 0 entries of 256 used
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->   229376
early_node_map[1] active PFN ranges
    0:        0 ->   229376
On node 0 totalpages: 229376
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 1760 pages used for memmap
  Normal zone: 223520 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 ASUS                                  ) @ 0x000f5e20
ACPI: RSDT (v001 ASUS   A7V8X-X  0x42302e31 MSFT 0x31313031) @ 0x3fffc000
ACPI: FADT (v001 ASUS   A7V8X-X  0x42302e31 MSFT 0x31313031) @ 0x3fffc0b2
ACPI: BOOT (v001 ASUS   A7V8X-X  0x42302e31 MSFT 0x31313031) @ 0x3fffc030
ACPI: MADT (v001 ASUS   A7V8X-X  0x42302e31 MSFT 0x31313031) @ 0x3fffc058
ACPI: DSDT (v001   ASUS A7V8X-X  0x00001000 MSFT 0x0100000b) @ 0x00000000
ACPI: PM-Timer IO Port: 0xe408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:10 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Detected 2154.048 MHz processor.
Built 1 zonelists.  Total pages: 227584
Kernel command line: root=/dev/hda3 video
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 905480k/917504k available (2233k kernel code, 11548k reserved, 964k data, 160k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xfffb7000 - 0xfffff000   ( 288 kB)
    vmalloc : 0xf8800000 - 0xfffb5000   ( 119 MB)
    lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
      .init : 0xc0422000 - 0xc044a000   ( 160 kB)
      .data : 0xc032e41c - 0xc041f434   ( 964 kB)
      .text : 0xc0100000 - 0xc032e41c   (2233 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4310.63 BogoMIPS (lpj=21553175)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000420 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(TM) XP 3000+ stepping 00
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf1960, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs *3 4 5 6 7 9 10 11 12)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12) *15, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *9
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region e400-e47f claimed by vt8235 PM
PCI quirk: region e800-e80f claimed by vt8235 SMB
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Bridge: 0000:00:01.0
  IO window: d000-dfff
  MEM window: bf000000-bfffffff
  PREFETCH window: c0000000-efffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Simple Boot Flag at 0x3a set to 0x1
Machine check exception polling timer started.
io scheduler noop registered
io scheduler cfq registered (default)
lp: driver loaded but no devices found
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected VIA KT400/KT400A/KT600 chipset
agpgart: AGP aperture is 128M @ 0xf0000000
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
radeonfb: Found Intel x86 BIOS ROM Image
radeonfb: Retrieved PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=500.00 Mhz, System=297.00 MHz
radeonfb: PLL min 20000 max 40000
i2c_adapter i2c-1: unable to read EDID block.
i2c_adapter i2c-1: unable to read EDID block.
i2c_adapter i2c-1: unable to read EDID block.
radeonfb: Monitor 1 type CRT found
radeonfb: EDID probed
radeonfb: Monitor 2 type no found
Console: switching to colour frame buffer device 160x64
radeonfb (0000:01:00.0): ATI Radeon AR 
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
lp0: using parport0 (polling).
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
via-rhine.c:v1.10-LK1.4.2 Sept-11-2006 Written by Donald Becker
ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 23 (level, low) -> IRQ 17
eth0: VIA Rhine II at 0x1a400, 00:0e:a6:8a:a6:36, IRQ 17.
eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1.
Linux video capture interface: v2.00
saa7130/34: v4l2 driver version 0.2.14 loaded
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:11.1
ACPI: Unable to derive IRQ for device 0000:00:11.1
ACPI: PCI Interrupt 0000:00:11.1[A]: no GSI
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
    ide0: BM-DMA at 0xa800-0xa807, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xa808-0xa80f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: MAXTOR 6L040J2, ATA DISK drive
hdb: SAMSUNG SP0802N, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: HL-DT-STDVD-ROM GDR8163B, ATAPI CD/DVD-ROM drive
hdd: HL-DT-ST GCE-8525B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 78177792 sectors (40027 MB) w/1819KiB Cache, CHS=65535/16/63, UDMA(33)
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
hdb: max request size: 512KiB
hdb: 156368016 sectors (80060 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(33)
hdb: cache flushes supported
 hdb: hdb1 hdb2 < hdb5 hdb6 >
hdc: ATAPI 52X DVD-ROM drive, 256kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 52X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
ACPI: PCI Interrupt 0000:00:10.3[D] -> GSI 21 (level, low) -> IRQ 18
ehci_hcd 0000:00:10.3: EHCI Host Controller
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.3: irq 18, io mem 0xbe800000
ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 18, io base 0x0000b800
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.1[B] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 18, io base 0x0000b400
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.2[C] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 18, io base 0x0000b000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
it87: Found IT8712F chip at 0x290, revision 5
Advanced Linux Sound Architecture Driver Version 1.0.13 (Tue Nov 28 14:07:24 2006 UTC).
input: AT Translated Set 2 keyboard as /class/input/input0
ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 18 (level, low) -> IRQ 19
ALSA device list:
  #0: SBLive 5.1 [SB0060] (rev.7, serial:0x80611102) at 0xa000, irq 19
ip_conntrack version 2.4 (7168 buckets, 57344 max) - 176 bytes per conntrack
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
Time: tsc clocksource has been installed.
input: ImExPS/2 Logitech Wheel Mouse as /class/input/input1
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 160k freed
EXT3 FS on hda3, internal journal
[drm] Initialized drm 1.0.1 20051102
[drm] Initialized radeon 1.25.0 20060524 on minor 0
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1004020k swap on /dev/hda5.  Priority:-1 extents:1 across:1004020k
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[drm:drm_unlock] *ERROR* Process 5256 using kernel context 0

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Boyd Stephen Smith Jr.]

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

On Monday 22 January 2007 14:59, Jan Stępień <jan@stepien.com.pl> wrote 
about 'Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg 
or Xgl, sir?'':
> I've enabled an option in my kernel called
> CONFIG_DRM_RADEON and compiled it as a loadable module. Then I've added
> it to list in /etc/modules.autoload/2.6 (or at least something which
> sounds similar to that one)

IIRC, this is the kernel module required for DRI with the in-tree, libre 
drivers for ATI hardware.  The matching x11-driver is "ati" or "radeon".

> commenting out the fglrx module to assure 
> myself that "radeon" is going to be loaded at each boot up and "fglrx"
> will not be loaded". /etc/X11/xorg.conf has been modified - "fglrx" has
> been replaced with "radeon". That's all. Check xorg.conf I've posted in
> the other mail for details.

You other mail had this in the attachment:
> Section "Device"
>         Identifier  "aticonfig-Device[0]"
> #       Driver      "radeon"
>         Driver      "fglrx"
>         Option  "UseInternalAGPGART" "no"
>         Option "VideoOverlay"   "on"
>         Option "OpenGLOverlay"  "off"
> #       Option "DRI" "on"
> EndSection
which indicates that you are attempting to use the fglrx x11-driver, and 
not the radeon x11-driver.

If you use the CONFIG_RADEON_DRM kernel module, you also need to use 
the "ati" or "radeon" x11 driver.  If your use the fglrx out-of-tree, 
esclavitud kernel module (at least I think there's a kernel module by this 
name) you'll alsa need to use the "fglrx" x11 driver.

You seem to be running into a simple misconfiguration at this point.

-- 
Boyd Stephen Smith Jr.             ,= ,-_-. =. 
bss03@volumehost.net              ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy   `-'(. .)`-' 
http://iguanasuicide.org/              \_/     

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Boyd Stephen Smith Jr. napisał(a):
> You other mail had this in the attachment:
>> Section "Device"
>>         Identifier  "aticonfig-Device[0]"
>> #       Driver      "radeon"
>>         Driver      "fglrx"
>>         Option  "UseInternalAGPGART" "no"
>>         Option "VideoOverlay"   "on"
>>         Option "OpenGLOverlay"  "off"
>> #       Option "DRI" "on"
>> EndSection
> which indicates that you are attempting to use the fglrx x11-driver, and 
> not the radeon x11-driver.
> 
> If you use the CONFIG_RADEON_DRM kernel module, you also need to use 
> the "ati" or "radeon" x11 driver.  If your use the fglrx out-of-tree, 
> esclavitud kernel module (at least I think there's a kernel module by this 
> name) you'll alsa need to use the "fglrx" x11 driver.
> 
> You seem to be running into a simple misconfiguration at this point.
> 

I'm sorry, I've forgotten to modify this line while attaching xorg.conf.
When I was trying to launch Xorg with radeon driver I obviously
commented out the "fglrx" driver and uncommented "radeon" driver's line
- inversely to what I have actually attached. So it should be:

>         Driver      "radeon"
> #       Driver      "fglrx"

And to make it even more precise - while entering default init level
fglrx is NOT loaded and radeon is loaded.

Regards,
Jan

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Richard Fish]

On 1/22/07, Jan Stępień <jan@stepien.com.pl> wrote:
> [drm:drm_unlock] *ERROR* Process 5256 using kernel context 0

Hmm, looks like kernel DRM is still having some issues.

Try changing your xorg.conf back to Driver "radeon", comment out the
"Option" lines, and then do a full reboot.  You might want to
"rc-update -d xdm" before this so that you boot into a console, and
can then try things with a plain old "startx".

HTH,
-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Iain Buchanan]

On Mon, 2007-01-22 at 21:47 +0100, Jan Stępień wrote:
> Mick napisał(a):
> > Did you try remerging xorg with the radeon VIDEO_DEVICE flag after you removed 
> > the fglrx module?
> 
> Actually I haven't heard about this flag. I've just googled for it but
> without any reasonably results. Could you tell me more about it or send
> me a link to a proper website which could enlighten me?

try these exact searches in google (include the site.. bit)

INPUT_DEVICES VIDEO_CARDS site:http://www.gentoo.org
and
INPUT_DEVICES VIDEO_CARDS site:http://www.gentoo-wiki.org

cya,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Of what you see in books, believe 75%.  Of newspapers, believe 50%.  And of
TV news, believe 25% -- make that 5% if the anchorman wears a blazer.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Iain Buchanan napisał(a):
> On Mon, 2007-01-22 at 21:47 +0100, Jan Stępień wrote:
> 
> try these exact searches in google (include the site.. bit)
> 
> INPUT_DEVICES VIDEO_CARDS site:http://www.gentoo.org
> and
> INPUT_DEVICES VIDEO_CARDS site:http://www.gentoo-wiki.org

I visited gentoo.org and skimmed the documentation. What I've read
doesn't make me cheerful at all. Quoting from
http://www.gentoo.org/doc/en/ati-faq.xml :

GPU             Common Name          Support
<snip>
R300,R400,R500  Radeon 9500 - x800   xorg 2D, ATI DRI

If I understand it correctly, this means that if I want a 3D
acceleration I've got to use closed ATI's fglrx, and if I'd like to have
an open driver from Xorg I am forced to accept 2D only. So no fglrx is
no 3D at all. Please tell me that I'm mistaken.

Regards,
Jan

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Direct rendering on a Radeon

[Benno Schulenberg]

Jan Stępień wrote:
> If I understand it correctly, this means that if I want a 3D
> acceleration I've got to use closed ATI's fglrx,

No, there is constant development on the R300 front.  What versions 
of Mesa, x11-drm, and libdrm do you have installed?

For which apps run for sure with 3D accel on an R300 see:

  http://dri.freedesktop.org/wiki/R300Application

For more info and configuration see:

  http://dri.freedesktop.org/wiki/ATIRadeon

Benno

-- 
Cetere mi opinias ke ne ĉio tradukenda estas.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

As far as I can see there is no chance neither to get my Radeon to
cooperate with open source driver nor to turn on AIGLX with my fglrx, at
least at the moment of writing. It's a pity, but allow me then to return
to the secondary topic of this thread.

Is it possible to enable some kind of a chooser which would allow me to
choose whether I'd like to launch Xgl or Xorg? While working on my
/usr/share/gdm/default.conf I've spotted a server called 'chooser'.
Could you tell me what is this server doing and could it be a solution
for my problem?

Of course the choice doesn't have to be done in GDM. It could be a tiny
bash script or a simple C++ application run in the default runlevel
which would ask me for pressing a specific key to run Xorg - otherwise
it will run Xgl - for example changing the line "0=Standard" in the file
I've mentioned above. Have you got ideas or do I have to write such an
app by myself?

Regards,
Jan Stępień

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Albert Hopkins]

On Sat, 2007-01-27 at 08:58 +0100, Jan Stępień wrote:
[...]

> Is it possible to enable some kind of a chooser which would allow me to
> choose whether I'd like to launch Xgl or Xorg? While working on my
> /usr/share/gdm/default.conf I've spotted a server called 'chooser'.
> Could you tell me what is this server doing and could it be a solution
> for my problem?
> 

A "chooser" in the GDM/XDMCP sense is a program that lists available
hosts to log into (via XDMCP).

I'm not aware of any program that will allow you to choose between X
servers any more than I'm aware of a program that will allow you to pick
MTAs.  The simplest solution is to just pick one.  Why would you want to
bounce back and forth between X servers?

> Of course the choice doesn't have to be done in GDM. It could be a tiny
> bash script or a simple C++ application run in the default runlevel
> which would ask me for pressing a specific key to run Xorg - otherwise
> it will run Xgl - for example changing the line "0=Standard" in the file
> I've mentioned above. Have you got ideas or do I have to write such an
> app by myself?
> 
> Regards,
> Jan Stępień
> 

Why should you need to write anything.  Forget GDM and if you want to
run X then type "X [ENTER]".  If you want Xgl then "Xgl [ENTER]".  But
again, why would you want to complicate your life with 2 different X
servers?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Albert Hopkins napisał(a):
> A "chooser" in the GDM/XDMCP sense is a program that lists available
> hosts to log into (via XDMCP).

Thanks. It may be useful some day.

> Why should you need to write anything.  Forget GDM and if you want to
> run X then type "X [ENTER]".  If you want Xgl then "Xgl [ENTER]".  But
> again, why would you want to complicate your life with 2 different X
> servers?

I've begun this thread because of my difficulties with running some
OpenGL applications, e.g. Americas Army, on my Xgl. If you'd like to
read any details you can take a look at first posts of this topic.

Regards,
Jan Stępień

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Albert Hopkins]

On Sat, 2007-01-27 at 15:06 +0100, Jan Stępień wrote:
[...]

> I've begun this thread because of my difficulties with running some
> OpenGL applications, e.g. Americas Army, on my Xgl. If you'd like to
> read any details you can take a look at first posts of this topic.

Then you probably don't want to use GDM or any other DM as they are
primarily designed to "manage" displays that are already selected.  What
you want is more of a chicken-and-egg issue for a display manager.

What you likely need is something to be run from the command line (i.e.
*before* X is started).  startx (or xinit) are perfect for this.  No
need to write any fancy program, it can pretty much do what you're
asking:

$ startx /path/to/program/that/needs/X.org -- /usr/bin/X
$ startx -- /usr/bin/Xgl

or whatever. There's probably a dozen other ways to do it.  See the
startx man page for details.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Albert Hopkins napisał(a):
> $ startx /path/to/program/that/needs/X.org -- /usr/bin/X
> $ startx -- /usr/bin/Xgl
> 
> or whatever. There's probably a dozen other ways to do it.  See the
> startx man page for details.

Thanks, I'll take a look at the manual and give it a shot.

Regards,
Jan

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Matthias Bethke]

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

Hi Jan,
on Saturday, 2007-01-27 at 15:06:32, you wrote:
> I've begun this thread because of my difficulties with running some
> OpenGL applications, e.g. Americas Army, on my Xgl.

I reckon most in America's army would love to have your problems.

SCNR! =^>
	Matthias
-- 
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0  8DEF 48D9 1700 FAC3 7665

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Jan Stępień]

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

Albert Hopkins napisał(a):
> Then you probably don't want to use GDM or any other DM as they are
> primarily designed to "manage" displays that are already selected.  What
> you want is more of a chicken-and-egg issue for a display manager.
> 
> What you likely need is something to be run from the command line (i.e.
> *before* X is started).  startx (or xinit) are perfect for this.  No
> need to write any fancy program, it can pretty much do what you're
> asking:
> 
> $ startx /path/to/program/that/needs/X.org -- /usr/bin/X
> $ startx -- /usr/bin/Xgl

Thanks, now it works flawlessly. I can easily launch a slick desktop
with Xgl and Beryl, and if I require direct rendering I simply log out
and launch Xorg.

Now I'll try to find a clever solution and make this method a little bit
more automatic. We'll see what I'll be able to find around the web.

Thanks once again.

Regards,
Jan Stępień

-- 
Mail 	jan at stepien com pl
Jabber 	jano at jabber aster pl
GG 	1894343
Web	http://stepien.com.pl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Martins]

You may choose to start X or Xgl generic way using startx or startxgl scripts. 
Out there are some.

m


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Xgl and direct rendering or 'Would you like Xorg or Xgl, sir?'

[Alan McKinnon]

On Saturday 27 January 2007 09:58, Jan Stępień wrote:

> Is it possible to enable some kind of a chooser which would allow me
> to choose whether I'd like to launch Xgl or Xorg? While working on my
> /usr/share/gdm/default.conf I've spotted a server called 'chooser'.
> Could you tell me what is this server doing and could it be a
> solution for my problem?

I use a workaround to accomplish something similar. You'll have to adapt 
it as I use startx not a display manager. I have two ServerLayout 
sections in xorg.conf (RADEON and FGLRX), and xinit takes a -layout 
argument to choose between them. Like this:

startx -- -layout RADEON

The -- is required so that startx won't try and process the following 
arguments, but rather pass them through to xinit.

alan


-- 
gentoo-user@gentoo.org mailing list