[gentoo-user] Xorg confusion and no glxinfo

[gentoo-user] Xorg confusion and no glxinfo

[Mick]

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

Hi All,

I cleared out some xorg related packages at some point because my machine will 
not shutdown without a kernel oops when it is trying to unload the radeon 
driver.  It now seems I can no longer find glxgears/info.  What have I 
removed that I shouldn't have?

I remember unmerging xorg-x11 (there was advice in this list that this is not 
needed when using Fluxbox or other lightweight window managers).

When I moved to x11-base/xorg-server-1.5.3-r* I also unmerged 
x11-drivers/xf86-video-ati.  I recall concluding at the time that the new 
xorg-server did not need such an external driver - is that right?

I have set radeon as the video card in my /etc/make.conf, but Xorg.0.log shows 
ati_drv.so - should it be so?

# less /var/log/Xorg.0.log | grep driver
        X.Org XInput driver : 2.1
(==) Matched ati for the autoconfigured driver
New driver is "ati"
(II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
(II) Loading /usr/lib/xorg/modules/drivers//radeon_drv.so
(II) AIGLX: enabled GLX_texture_from_pixmap with driver support

# lsmod | grep radeon
radeon                145696  2 
drm                   141892  3 radeon

Your views?
-- 
Regards,
Mick

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

[gentoo-user] Re: Xorg confusion and no glxinfo

[Mick]

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

On Monday 06 July 2009, Mick wrote:
> Hi All,
>
> I cleared out some xorg related packages at some point because my machine
> will not shutdown without a kernel oops when it is trying to unload the
> radeon driver.  It now seems I can no longer find glxgears/info.  What have
> I removed that I shouldn't have?
>
> I remember unmerging xorg-x11 (there was advice in this list that this is
> not needed when using Fluxbox or other lightweight window managers).
>
> When I moved to x11-base/xorg-server-1.5.3-r* I also unmerged
> x11-drivers/xf86-video-ati.  I recall concluding at the time that the new
> xorg-server did not need such an external driver - is that right?
>
> I have set radeon as the video card in my /etc/make.conf, but Xorg.0.log
> shows ati_drv.so - should it be so?
>
> # less /var/log/Xorg.0.log | grep driver
>         X.Org XInput driver : 2.1
> (==) Matched ati for the autoconfigured driver
> New driver is "ati"
> (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
> (II) Loading /usr/lib/xorg/modules/drivers//radeon_drv.so
> (II) AIGLX: enabled GLX_texture_from_pixmap with driver support
>
> # lsmod | grep radeon
> radeon                145696  2
> drm                   141892  3 radeon
>
> Your views?

I hope it's not bad form to reply to my own message ...

When I unmerged xorg-x11 I depclean removed a number of packages including 
x11-apps/mesa-progs - which contains glxinfo and glxgears.

So, this leaves the question - do I need x11-drivers/xf86-video-ati?
-- 
Regards,
Mick

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

[gentoo-user] Re: Xorg confusion and no glxinfo

[walt]

On 07/06/2009 03:29 AM, Mick wrote:
> Hi All,
>
> I cleared out some xorg related packages at some point because my machine will
> not shutdown without a kernel oops when it is trying to unload the radeon
> driver.

Hm. There is no reason to unload any driver or module just to shut down.  Are
you sure that's the reason for the oops?

> It now seems I can no longer find glxgears/info.  What have I
> removed that I shouldn't have?

glxgears is part of mesa-progs.

> I remember unmerging xorg-x11 (there was advice in this list that this is not
> needed when using Fluxbox or other lightweight window managers).

That's a meta-package, which just pulls in a bunch of other packages.  Meta-
packages are never needed, they're just for your convenience.

> When I moved to x11-base/xorg-server-1.5.3-r* I also unmerged
> x11-drivers/xf86-video-ati.  I recall concluding at the time that the new
> xorg-server did not need such an external driver - is that right?

No, xorg-server will always need a specific driver for a specific video card,
it's just a matter of figuring out which one your card needs.  OTOH most cards
will work at a very basic level with just the vesa driver -- but that's most
likely not what you want.

> I have set radeon as the video card in my /etc/make.conf, but Xorg.0.log shows
> ati_drv.so - should it be so?

> # less /var/log/Xorg.0.log | grep driver
>          X.Org XInput driver : 2.1
> (==) Matched ati for the autoconfigured driver
> New driver is "ati"
> (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
> (II) Loading /usr/lib/xorg/modules/drivers//radeon_drv.so
> (II) AIGLX: enabled GLX_texture_from_pixmap with driver support
>
> # lsmod | grep radeon
> radeon                145696  2
> drm                   141892  3 radeon

I don't know enough about ati products to answer.  The xorg-server is pretty
good at picking the right driver by itself.  If you type "X -logverbose" at
a command prompt and look at the X logfile you may see that the server has
loaded multiple drivers and then unloads the ones it doesn't need -- strange
behavior but that's the way it's designed, apparently.

Re: [gentoo-user] Re: Xorg confusion and no glxinfo

[Mick]

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

On Monday 06 July 2009, walt wrote:
> On 07/06/2009 03:29 AM, Mick wrote:

> > I cleared out some xorg related packages at some point because my machine
> > will not shutdown without a kernel oops when it is trying to unload the
> > radeon driver.
>
> Hm. There is no reason to unload any driver or module just to shut down. 
> Are you sure that's the reason for the oops?

Well, no, but when I Ctrl+Alt+F1 to a console and shutdown from there there 
are no oops with the usual messages about "vblank_disable_fn+0x79/0xd0 [drm]" 
and "EIP: [<e0cc14fe>] radeon_get_vblank_counter+0x7e/0xd0 [radeon]".

> > When I moved to x11-base/xorg-server-1.5.3-r* I also unmerged
> > x11-drivers/xf86-video-ati.  I recall concluding at the time that the new
> > xorg-server did not need such an external driver - is that right?

> No, xorg-server will always need a specific driver for a specific video
> card, it's just a matter of figuring out which one your card needs.  OTOH
> most cards will work at a very basic level with just the vesa driver -- but
> that's most likely not what you want.

I recall that when I unmerged xf86-video-ati, glxgears still performed as 
before and therefore I assumed that the new xorg-server had access to all it 
needed to run my video card.  Should I emerge it again?
-- 
Regards,
Mick

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

[gentoo-user] Re: Xorg confusion and no glxinfo

[walt]

On 07/06/2009 04:39 AM, Mick wrote:
> On Monday 06 July 2009, walt wrote:
>> On 07/06/2009 03:29 AM, Mick wrote:
>
>>> I cleared out some xorg related packages at some point because my machine
>>> will not shutdown without a kernel oops when it is trying to unload the
>>> radeon driver.
>>
>> Hm. There is no reason to unload any driver or module just to shut down.
>> Are you sure that's the reason for the oops?
>
> Well, no, but when I Ctrl+Alt+F1 to a console and shutdown from there there
> are no oops with the usual messages about "vblank_disable_fn+0x79/0xd0 [drm]"
> and "EIP: [<e0cc14fe>] radeon_get_vblank_counter+0x7e/0xd0 [radeon]".

Wait, when exactly do you see the 'usual' oops messages?

> I recall that when I unmerged xf86-video-ati, glxgears still performed as
> before and therefore I assumed that the new xorg-server had access to all it
> needed to run my video card.  Should I emerge it again?

It's a reasonable question but I don't know the answer. Your original post said:

(II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
(II) Loading /usr/lib/xorg/modules/drivers//radeon_drv.so

The server apparently loaded both drivers without errors but it may have unloaded
the ati driver later on.  You won't know unless you do the 'X -logverbose' test I
suggested and look through the X log file.

I would re-emerge the ati driver, do the verbose logging test and see for yourself
if the X server unloads the ati driver after loading it.  If so, then you don't
need the ati driver.  (I suspect you don't, but I'm just guessing.)

Re: [gentoo-user] Re: Xorg confusion and no glxinfo

[Mick]

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

On Monday 06 July 2009, walt wrote:
> On 07/06/2009 04:39 AM, Mick wrote:
> > On Monday 06 July 2009, walt wrote:
> >> On 07/06/2009 03:29 AM, Mick wrote:
> >>> I cleared out some xorg related packages at some point because my
> >>> machine will not shutdown without a kernel oops when it is trying to
> >>> unload the radeon driver.
> >>
> >> Hm. There is no reason to unload any driver or module just to shut down.
> >> Are you sure that's the reason for the oops?
> >
> > Well, no, but when I Ctrl+Alt+F1 to a console and shutdown from there
> > there are no oops with the usual messages about
> > "vblank_disable_fn+0x79/0xd0 [drm]" and "EIP: [<e0cc14fe>]
> > radeon_get_vblank_counter+0x7e/0xd0 [radeon]".
>
> Wait, when exactly do you see the 'usual' oops messages?

When I try to shutdown the machine they come up on the console - currently 
running 2.6.29-gentoo-r5.  Typically, the oops occurs after the wireless 
driver and alsasound modules are unloaded and occasionally after syslog-ng is 
stopped.  No oops take place if I exit X and then issue a shutdown command 
from the console.  I am waiting for a newer kernel to see if this problem has 
been fixed.
-- 
Regards,
Mick

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

[gentoo-user] Re: Xorg confusion and no glxinfo

[walt]

On 07/06/2009 04:23 PM, Mick wrote:
> On Monday 06 July 2009, walt wrote:
>> On 07/06/2009 04:39 AM, Mick wrote:
>>> On Monday 06 July 2009, walt wrote:
>>>> On 07/06/2009 03:29 AM, Mick wrote:
>>>>> I cleared out some xorg related packages at some point because my
>>>>> machine will not shutdown without a kernel oops when it is trying to
>>>>> unload the radeon driver.
>>>>
>>>> Hm. There is no reason to unload any driver or module just to shut down.
>>>> Are you sure that's the reason for the oops?
>>>
>>> Well, no, but when I Ctrl+Alt+F1 to a console and shutdown from there
>>> there are no oops with the usual messages about
>>> "vblank_disable_fn+0x79/0xd0 [drm]" and "EIP: [<e0cc14fe>]
>>> radeon_get_vblank_counter+0x7e/0xd0 [radeon]".
>>
>> Wait, when exactly do you see the 'usual' oops messages?
>
> When I try to shutdown the machine they come up on the console - currently
> running 2.6.29-gentoo-r5.  Typically, the oops occurs after the wireless
> driver and alsasound modules are unloaded and occasionally after syslog-ng is
> stopped...

Okay, I know about the alsa modules stuff, but not the wireless.  The alsa
modules should *not* be unloaded on shutdown because there is no reason to
do it and it causes problems if you try. (And I'm guessing that wireless is
the same.)

Look at /etc/conf.d/alsasound.  You should have two lines there as follows:

# Deprecated options:
# Upstream feels, and we wholehartedly agree, that this was a silly idea
UNLOAD_ON_STOP="no"
KILLPROC_ON_STOP="no"

When I'm more awake I'll take a look at wireless.

Re: [gentoo-user] Re: Xorg confusion and no glxinfo

[Mick]

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

On Tuesday 07 July 2009, walt wrote:
> On 07/06/2009 04:23 PM, Mick wrote:
> > On Monday 06 July 2009, walt wrote:
> >> On 07/06/2009 04:39 AM, Mick wrote:
> >>> On Monday 06 July 2009, walt wrote:
> >>>> On 07/06/2009 03:29 AM, Mick wrote:
> >>>>> I cleared out some xorg related packages at some point because my
> >>>>> machine will not shutdown without a kernel oops when it is trying to
> >>>>> unload the radeon driver.
> >>>>
> >>>> Hm. There is no reason to unload any driver or module just to shut
> >>>> down. Are you sure that's the reason for the oops?
> >>>
> >>> Well, no, but when I Ctrl+Alt+F1 to a console and shutdown from there
> >>> there are no oops with the usual messages about
> >>> "vblank_disable_fn+0x79/0xd0 [drm]" and "EIP: [<e0cc14fe>]
> >>> radeon_get_vblank_counter+0x7e/0xd0 [radeon]".
> >>
> >> Wait, when exactly do you see the 'usual' oops messages?
> >
> > When I try to shutdown the machine they come up on the console -
> > currently running 2.6.29-gentoo-r5.  Typically, the oops occurs after the
> > wireless driver and alsasound modules are unloaded and occasionally after
> > syslog-ng is stopped...
>
> Okay, I know about the alsa modules stuff, but not the wireless.  The alsa
> modules should *not* be unloaded on shutdown because there is no reason to
> do it and it causes problems if you try. (And I'm guessing that wireless is
> the same.)
>
> Look at /etc/conf.d/alsasound.  You should have two lines there as follows:
>
> # Deprecated options:
> # Upstream feels, and we wholehartedly agree, that this was a silly idea
> UNLOAD_ON_STOP="no"
> KILLPROC_ON_STOP="no"
>
> When I'm more awake I'll take a look at wireless.

Thanks walt, but this problem is *not* related either to the usual alsasound 
culprit, or wireless.  I have tried it with and without wireless and with and 
without unloading alsasound.  All the errors are about radeon, nothing to do 
with anything else.

As a side note, the new xorg server has caused 3d rendering (when I still had 
installed glxinfo and could compare speeds) to run like a dog.  Until the 
2.6.29 versions I never had kernel oops, or at least not without compiling 
something really inappropriate in the kernel.
-- 
Regards,
Mick

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