On Sat, 29 Jan 2005 13:32:47 +0100, Bernd Eckenfels wrote:
> it is not a permission thing, it tells you, that you have not card14 - and i
> dont know the dri interface but it looks unlikely that there ever will be
> one .)
I figured (maybe incorrectly) that oo was just going thru the dri card*
files:
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card8", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card9", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card10", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card11", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card12", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card13", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card14", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
munmap(0x9b4838, 8192) = -1 EINVAL (Invalid argument)
munmap(0x9d55248, 3219928560) = -1 EINVAL (Invalid argument)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
from 0 to 14 until it found a card that it could use. The root cause
has to be that it can't use dri/card* because of access permissions.
Note, that strace glxgears gives exactly the same output, going from 0 to
14 and then seg-faulting, so it's *not just a oo problem*.
Richard Hughes
--
http://www.hughsie.com/PUBLIC-KEY
On Sat, 29 Jan 2005 12:49:16 +0000, Richard Hughes wrote:
> Note, that strace glxgears gives exactly the same output, going from 0 to
> 14 and then seg-faulting, so it's *not just a oo problem*.
I know it's bad to answer your own post, but here goes.
I changed my /etc/udev/permissions.d/50-udev.permissions config to read:
dri/*:root:root:0666
changing it from
dri/*:root:root:0660
And oowriter and glxgears work from bootup. Shall I file a bug with udev?
Richard Hughes
--
http://www.hughsie.com/PUBLIC-KEY
On Sat, 29 Jan 2005 13:02:51 +0000, Richard Hughes <[email protected]> wrote:
> On Sat, 29 Jan 2005 12:49:16 +0000, Richard Hughes wrote:
> > Note, that strace glxgears gives exactly the same output, going from 0 to
> > 14 and then seg-faulting, so it's *not just a oo problem*.
>
> I know it's bad to answer your own post, but here goes.
>
> I changed my /etc/udev/permissions.d/50-udev.permissions config to read:
>
> dri/*:root:root:0666
>
> changing it from
>
> dri/*:root:root:0660
>
> And oowriter and glxgears work from bootup. Shall I file a bug with udev?
Interesting. On my FC2 (without udev) under 2.6.11-rc2-bk5
both programs work fine with /dev/dri/card0 in its default
permissions - 666 (obviously).
However, if I manually chmod /dev/dri/card0 to 660 I don't
get a SEGV, but rather
[asuardi@incident asuardi]$ glxgears
libGL error: failed to open DRM: Operation not permitted
libGL error: reverting to (slow) indirect rendering
711 frames in 5.0 seconds = 142.200 FPS
X connection to :0.0 broken (explicit kill or server shutdown).
[asuardi@incident asuardi]$ ooffice
libGL error: failed to open DRM: Operation not permitted
libGL error: reverting to (slow) indirect rendering
And both still work.
Relevant strace portion from glxgears says
read(3, "\1\355\21\0\3\0\0\0\0\200\204\370\0\0\0\0\t\0\0\0\33\0"..., 32) = 32
readv(3, [{"PCI:1:0:0", 9}, {"\0\0\0", 3}], 2) = 12
geteuid32() = 41
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/dev/dri/card0", {st_mode=S_IFCHR|0660, st_rdev=makedev(226,
0), ...}) = 0
open("/dev/dri/card0", O_RDWR) = -1 EACCES (Permission denied)
open("/dev/dri/card0", O_RDWR) = -1 EACCES (Permission denied)
unlink("/dev/dri/card0") = -1 EACCES (Permission denied)
geteuid32() = 41
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/dev/dri/card1", 0xbffff0dc) = -1 ENOENT (No such file or directory)
...
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/dev/dri/card14", 0xbffff0dc) = -1 ENOENT (No such file or directory)
write(2, "libGL error: failed to open DRM:"..., 57libGL error: failed
to open DRM: Operation not permitted
) = 57
write(2, "libGL error: reverting to (slow)"..., 52libGL error:
reverting to (slow) indirect rendering
) = 52
mmap2(NULL, 266240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0xb7b68000
write(3, "\222\3\2\0\0\0\0\0\220\24$\2\1\0\0\0\2\0\0\0\200\10\0\0"...,
2544) = 2544
This with libGL and glxgears from FC2 updated RPMs
xorg-x11-Mesa-libGL-6.7.0-11
xorg-x11-tools-6.7.0-11
--alessandro
"And every dream, every, is just a dream after all"
(Heather Nova, "Paper Cup")
On Sat, 29 Jan 2005 13:02:51 +0000, Richard Hughes <[email protected]> wrote:
> On Sat, 29 Jan 2005 12:49:16 +0000, Richard Hughes wrote:
> > Note, that strace glxgears gives exactly the same output, going from 0 to
> > 14 and then seg-faulting, so it's *not just a oo problem*.
>
> I know it's bad to answer your own post, but here goes.
>
> I changed my /etc/udev/permissions.d/50-udev.permissions config to read:
>
> dri/*:root:root:0666
>
> changing it from
>
> dri/*:root:root:0660
>
> And oowriter and glxgears work from bootup. Shall I file a bug with udev?
Your user ID needs to belong to group DRI.
--
Jon Smirl
[email protected]
For the record, this has nothing to do with my crash. Mine still crashes
all the time if I try to save a new document.
Trever
On Sat, 2005-01-29 at 14:25 -0500, Jon Smirl wrote:
> On Sat, 29 Jan 2005 13:02:51 +0000, Richard Hughes <[email protected]> wrote:
> > On Sat, 29 Jan 2005 12:49:16 +0000, Richard Hughes wrote:
> > > Note, that strace glxgears gives exactly the same output, going from 0 to
> > > 14 and then seg-faulting, so it's *not just a oo problem*.
> >
> > I know it's bad to answer your own post, but here goes.
> >
> > I changed my /etc/udev/permissions.d/50-udev.permissions config to read:
> >
> > dri/*:root:root:0666
> >
> > changing it from
> >
> > dri/*:root:root:0660
> >
> > And oowriter and glxgears work from bootup. Shall I file a bug with udev?
>
> Your user ID needs to belong to group DRI.
>
--
Legal Warning: Anyone sending me unsolicited/commercial email WILL be
charged a $100 proof-reading fee. See US Code Title 47,
Sec.227(a)(2)(B), Sec.227(b)(1)(C) and Sec.227(b)(3)(C).
On Sat, 2005-01-29 at 14:25 -0500, Jon Smirl wrote:
>
> > And oowriter and glxgears work from bootup. Shall I file a bug with udev?
>
> Your user ID needs to belong to group DRI.
>
Stupid question: what the heck does OO use DRI for? I googled and came
up empty.
Lee
* Lee Revell ([email protected]) wrote:
>
> Stupid question: what the heck does OO use DRI for? I googled and came
> up empty.
It does pointless 3D objects in its drawing package.
Dave
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
On Saturday 29 January 2005 14:25, Jon Smirl wrote:
>On Sat, 29 Jan 2005 13:02:51 +0000, Richard Hughes
<[email protected]> wrote:
>> On Sat, 29 Jan 2005 12:49:16 +0000, Richard Hughes wrote:
>> > Note, that strace glxgears gives exactly the same output, going
>> > from 0 to 14 and then seg-faulting, so it's *not just a oo
>> > problem*.
>>
>> I know it's bad to answer your own post, but here goes.
>>
>> I changed my /etc/udev/permissions.d/50-udev.permissions config to
>> read:
>>
>> dri/*:root:root:0666
>>
>> changing it from
>>
>> dri/*:root:root:0660
>>
>> And oowriter and glxgears work from bootup. Shall I file a bug
>> with udev?
>
>Your user ID needs to belong to group DRI.
Humm, scratching head here. My /etc/group file contains no references
to dri, but as root at least, it works just fine, X-6.8.1 here.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.32% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
On Sat, 2005-01-29 at 20:40 +0000, Dr. David Alan Gilbert wrote:
> * Lee Revell ([email protected]) wrote:
> >
> > Stupid question: what the heck does OO use DRI for? I googled and came
> > up empty.
>
> It does pointless 3D objects in its drawing package.
>
Thanks. I knew it had to be something really clever, or something
really stupid ;-)
Lee
Dr. David Alan Gilbert wrote:
>* Lee Revell ([email protected]) wrote:
>
>
>>Stupid question: what the heck does OO use DRI for? I googled and came
>>up empty.
>>
>>
>
>It does pointless 3D objects in its drawing package.
>
>
Another stupid question :)
Does it mean DRI is only used for doing 3D? How about normal, 2D stuff?
I thought X uses DRI for both 2D and 3D if it is available...
On Sat, 2005-01-29 at 15:57 -0500, Parag Warudkar wrote:
> Dr. David Alan Gilbert wrote:
>
> >* Lee Revell ([email protected]) wrote:
> >
> >
> >>Stupid question: what the heck does OO use DRI for? I googled and came
> >>up empty.
> >>
> >>
> >
> >It does pointless 3D objects in its drawing package.
> >
> >
> Another stupid question :)
> Does it mean DRI is only used for doing 3D? How about normal, 2D stuff?
> I thought X uses DRI for both 2D and 3D if it is available...
>
No, XAA is normally used for 2D acceleration. This is hardware
accelerated but doesn't use DRI, X does 2D accel by talking directly to
the hardware without the kernel's involvement.
This is an area where the proprietary guys are a little ahead but there
are some interesting developments like the Xgl server.
Lee
>
> No, XAA is normally used for 2D acceleration. This is hardware
> accelerated but doesn't use DRI, X does 2D accel by talking directly to
> the hardware without the kernel's involvement.
>
well not totally true, X on radeon/r200/r300 cards needs the DRM to
load the microcode for the command processor, this enables some major
speedups in the 2D code (it still talk direct to the card, but needs
the CP loading...) but X runs as root so it has no worries opening the
device...
the issue is with using having the perms set to 0660 since the drm
started supporting sysfs and udev... normally X created the dri
devices and set the permissions to what was in the X config, normally
666.... or 660 with a dri group...
Dave.
My problem is some things changed in the installed package changed and
some things in my home directory in .openoffice (setup and soffice) were
incorrect. I erased the symlinks and my problem is over. I would
suggest others having problems try the same. This may have NOTHING to do
with the kernel (as in my case).
Trever
On Sat, 2005-01-29 at 12:57 -0700, Trever L. Adams wrote:
> For the record, this has nothing to do with my crash. Mine still crashes
> all the time if I try to save a new document.
>
> Trever
>
> On Sat, 2005-01-29 at 14:25 -0500, Jon Smirl wrote:
> > On Sat, 29 Jan 2005 13:02:51 +0000, Richard Hughes <[email protected]> wrote:
> > > On Sat, 29 Jan 2005 12:49:16 +0000, Richard Hughes wrote:
> > > > Note, that strace glxgears gives exactly the same output, going from 0 to
> > > > 14 and then seg-faulting, so it's *not just a oo problem*.
> > >
> > > I know it's bad to answer your own post, but here goes.
> > >
> > > I changed my /etc/udev/permissions.d/50-udev.permissions config to read:
> > >
> > > dri/*:root:root:0666
> > >
> > > changing it from
> > >
> > > dri/*:root:root:0660
> > >
> > > And oowriter and glxgears work from bootup. Shall I file a bug with udev?
> >
> > Your user ID needs to belong to group DRI.
> >
> --
> Legal Warning: Anyone sending me unsolicited/commercial email WILL be
> charged a $100 proof-reading fee. See US Code Title 47,
> Sec.227(a)(2)(B), Sec.227(b)(1)(C) and Sec.227(b)(3)(C).
--
"The Master doesn't talk, he acts. When his work is done, the people
say, 'Amazing: we did it, all by ourselves!'" -- Lao-tzu