Re: xcb_writev: Segmentation fault

2017-09-01 Thread YuGiOhJCJ Mailing-List 
OK, I found how to fix the problem: I need to use the '-O1' gcc optimization 
flag instead of '-O2' when building libxcb.
Well, in fact, it is just a workaround and not a fix because I prefer the '-O2' 
optimization flag but unfortunately I can't use it for building libxcb.
Thanks to Ilya Lipnitskiy (lipnitsk) for this idea: 
https://bugs.archlinux.org/task/49560

On Thu, 31 Aug 2017 16:54:44 +0200
YuGiOhJCJ Mailing-List <yugiohjcj-mailingl...@laposte.net> wrote:

> Hello,
> 
> I built libX11 1.6.5 32-bit on my 64-bit machine and I try to run a 32-bit 
> application:
> ---
> $ gdb 25Assist
> GNU gdb (GDB) 7.11.1
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-slackware-linux".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from 25Assist...(no debugging symbols found)...done.
> (gdb) run
> Starting program: /opt/25assist-20151223/25Assist 
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> warning: File "/usr/lib/libstdc++.so.6.0.23-gdb.py" auto-loading has been 
> declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
> To enable execution of this file add
>   add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.23-gdb.py
> line to your configuration file "/home/yugiohjcj/.gdbinit".
> To completely disable this security protection add
>   set auto-load safe-path /
> line to your configuration file "/home/yugiohjcj/.gdbinit".
> For more information about this security protection see the
> "Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
>   info "(gdb)Auto-loading safe path"
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, 
> requests=73) at xcb_out.c:405
> 405   c->out.request += requests;
> (gdb) bt
> #0  0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, 
> requests=73) at xcb_out.c:405
> #1  0xf767f85e in _XSend (dpy=0x82cb400, data=0x0, size=0) at xcb_io.c:486
> #2  0xf767fe19 in _XReply (dpy=0x82cb400, rep=0x9ec4, extra=0, discard=1) 
> at xcb_io.c:573
> #3  0xf767b943 in XSync (dpy=0x82cb400, discard=0) at Sync.c:44
> #4  0xf7a537b2 in IA__gdk_flush () at gdkevents-x11.c:2606
> #5  0xf7a23170 in alloc_scratch_image (image_info=) at 
> gdkimage.c:527
> #6  _gdk_image_get_scratch (screen=0x82da0b8, width=160, height=23, depth=24, 
> x=0x9fbc, y=0x9fc0) at gdkimage.c:592
> #7  0xf7a30fbe in gdk_draw_rgb_image_core (image_info=0x83f3bf8, 
> drawable=drawable@entry=0x82c6c00, gc=gc@entry=0x82d8e80, x=0, y=0, 
> width=160, height=23, 
> buf=0x840bc48 "\371\371\371nnn\022\022\022", pixstride=3, rowstride=480, 
> conv=0xf7a2f0a0 , cmap=0x0, xdith=0, ydith=0) at 
> gdkrgb.c:3327
> #8  0xf7a329e9 in IA__gdk_draw_rgb_image (drawable=0x82c6c00, gc=0x82d8e80, 
> x=0, y=0, width=160, height=23, dith=GDK_RGB_DITHER_MAX, rgb_buf=0x840bc48 
> "\371\371\371nnn\022\022\022", 
> rowstride=480) at gdkrgb.c:3393
> #9  0x0809d97e in ?? ()
> #10 0x081124a0 in ?? ()
> #11 0x081124d5 in ?? ()
> #12 0xf6252292 in ?? ()
> #13 0xf60cf138 in ?? ()
> #14 0xf60cf3a3 in ?? ()
> #15 0xf62d3f00 in ?? ()
> #16 0xf62ceb8b in ?? ()
> #17 0x0807077d in ?? ()
> #18 0x08070888 in ?? ()
> #19 0x08179267 in ?? ()
> #20 0xf6100128 in ?? ()
> #21 0x0816d65a in ?? ()
> #22 0x0816d64e in ?? ()
> #23 0x0816d75f in ?? ()
> #24 0xf668681b in ?? ()
> #25 0xf60b5308 in ?? ()
> #26 0xf60b53b4 in ?? ()
> #27 0xf6255333 in ?? ()
> #28 0xf60b5469 in ?? ()
> #29 0xf60b5024 in ?? ()
> #30 0x080d2592 in ?? ()
> #31 0x0816c1b1 in ?? ()
> #32 0xf72be4d3 in __libc_start_main () from /lib/libc.so.6
> #33 0x08052b21 in ?? ()
> (gdb) quit
> A debugging session is active.
> 
>   Inferior 1 [process 18645] will be killed.
> 
> Quit anyway? (y or n) y
> ---
> 
> As you can see I get a segmentation fault after the call to the xcb_writev 
>

xcb_writev: Segmentation fault

2017-08-31 Thread YuGiOhJCJ Mailing-List 
Hello,

I built libX11 1.6.5 32-bit on my 64-bit machine and I try to run a 32-bit 
application:
---
$ gdb 25Assist
GNU gdb (GDB) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-slackware-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 25Assist...(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/25assist-20151223/25Assist 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
warning: File "/usr/lib/libstdc++.so.6.0.23-gdb.py" auto-loading has been 
declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.23-gdb.py
line to your configuration file "/home/yugiohjcj/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/yugiohjcj/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"

Program received signal SIGSEGV, Segmentation fault.
0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, requests=73) 
at xcb_out.c:405
405 c->out.request += requests;
(gdb) bt
#0  0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, 
requests=73) at xcb_out.c:405
#1  0xf767f85e in _XSend (dpy=0x82cb400, data=0x0, size=0) at xcb_io.c:486
#2  0xf767fe19 in _XReply (dpy=0x82cb400, rep=0x9ec4, extra=0, discard=1) 
at xcb_io.c:573
#3  0xf767b943 in XSync (dpy=0x82cb400, discard=0) at Sync.c:44
#4  0xf7a537b2 in IA__gdk_flush () at gdkevents-x11.c:2606
#5  0xf7a23170 in alloc_scratch_image (image_info=) at 
gdkimage.c:527
#6  _gdk_image_get_scratch (screen=0x82da0b8, width=160, height=23, depth=24, 
x=0x9fbc, y=0x9fc0) at gdkimage.c:592
#7  0xf7a30fbe in gdk_draw_rgb_image_core (image_info=0x83f3bf8, 
drawable=drawable@entry=0x82c6c00, gc=gc@entry=0x82d8e80, x=0, y=0, width=160, 
height=23, 
buf=0x840bc48 "\371\371\371nnn\022\022\022", pixstride=3, rowstride=480, 
conv=0xf7a2f0a0 , cmap=0x0, xdith=0, ydith=0) at 
gdkrgb.c:3327
#8  0xf7a329e9 in IA__gdk_draw_rgb_image (drawable=0x82c6c00, gc=0x82d8e80, 
x=0, y=0, width=160, height=23, dith=GDK_RGB_DITHER_MAX, rgb_buf=0x840bc48 
"\371\371\371nnn\022\022\022", 
rowstride=480) at gdkrgb.c:3393
#9  0x0809d97e in ?? ()
#10 0x081124a0 in ?? ()
#11 0x081124d5 in ?? ()
#12 0xf6252292 in ?? ()
#13 0xf60cf138 in ?? ()
#14 0xf60cf3a3 in ?? ()
#15 0xf62d3f00 in ?? ()
#16 0xf62ceb8b in ?? ()
#17 0x0807077d in ?? ()
#18 0x08070888 in ?? ()
#19 0x08179267 in ?? ()
#20 0xf6100128 in ?? ()
#21 0x0816d65a in ?? ()
#22 0x0816d64e in ?? ()
#23 0x0816d75f in ?? ()
#24 0xf668681b in ?? ()
#25 0xf60b5308 in ?? ()
#26 0xf60b53b4 in ?? ()
#27 0xf6255333 in ?? ()
#28 0xf60b5469 in ?? ()
#29 0xf60b5024 in ?? ()
#30 0x080d2592 in ?? ()
#31 0x0816c1b1 in ?? ()
#32 0xf72be4d3 in __libc_start_main () from /lib/libc.so.6
#33 0x08052b21 in ?? ()
(gdb) quit
A debugging session is active.

Inferior 1 [process 18645] will be killed.

Quit anyway? (y or n) y
---

As you can see I get a segmentation fault after the call to the xcb_writev 
function.
From this program stack, I am unable to guess what could be the problem.
Maybe a communication problem between libX11 and libxcb but why?
I was able to run this application in the past so I think I did something wrong 
when I built my 32-bit libX11 this time.

Can you guess where the problem is from this backtrace?

Thank you.
Best regards.

Remark: I rebuilt gtk+2, libX11 and libxcb with the '-g' flag to have a nice 
backtrace so that's why you see the debugging symbols.

32-bit programs used:
atk-2.20.0
cairo-1.14.10
expat-2.1.0
fontconfig-2.12.1
freetype-2.6.3
gdk-pixbuf2-2.36.6
glib2-2.52.3
glibc-2.23
gtk+2-2.24.30
harfbuzz-1.2.7
icu4c-56.1
libdrm-2.4.80
libffi-3.2.1
libjpeg-turbo-1.5.0
libpciaccess-0.13.5
libpng-1.6.25
libtiff-4.0.6
libX11-1.6.5
libXau-1.0.8
libxcb-1.12
libXcomposite-0.4.4
libXcursor-1.1.14
libXdamage-1.1.4
libXext-1.3.3
libXfixes-5.0.3
libXft-2.3.2
libXi-1.7.9
libXinerama-1.1.3
libXrandr-1.5.1
libXrender-0.9.10
libxshmfence-1.2
libXxf86vm-1.1.4
llvm-3.9.0
mesa-17.0.4
ncurses-5.9
pango-1.40.6
pcre-8.39
pixman-0.34.0
util-linux-2.27.1
zlib-1.2.8

Re: modeset(0): drmSetMaster failed: Permission denied

2017-05-01 Thread YuGiOhJCJ Mailing-List 
Do you mean 755 on /usr/bin/Xorg?

It is already set like that:
$ ls -l /usr/bin/Xorg 
-rwxr-xr-x 1 root root 2123272 Apr 30 23:26 /usr/bin/Xorg

Any other idea?

On Sun, 30 Apr 2017 22:08:45 -0700 (PDT)
Russ Whitaker <r...@ashlandhome.net> wrote:

> 
> 
> On Mon, 1 May 2017, YuGiOhJCJ Mailing-List wrote:
> 
> > Hello,
> >
> > I have built xorg-server, xauth, and xinit with their dependencies.
> > When I do startx I get "xf86OpenConsole: Cannot open virtual console 7 
> > (Permission denied)".
> > So, I change the permissions on /dev/tty7 to 660.
> > Now, when I do startx I get "modeset(0): drmSetMaster failed: Permission 
> > denied".
> >
> > I read in the web that some people use SUID on /usr/bin/Xorg to solve this 
> > problem but I am not sure if it is safe to do that and maybe there is a 
> > better way.
> > Same thing for my permissions on /dev/tty7, I would prefer to not change 
> > permissions if possible.
> > With the Xorg provided by my distro, there is no SUID on /usr/bin/Xorg and 
> > only 0620 on /dev/tty7 which is better, and it works fine.
> > So, I am wondering why it does not work with my own Xorg.
> >
> > Any idea please?
> 
> Set permissions to 755
> 
> >
> > Thank you.
> > Best regards.
> >
> > ---
> >
> > Distro: Slackware64 14.2
> > Kernel: Linux 4.9.24
> > Built and installed packages:
> > -bigreqsproto-1.1.2
> > -compositeproto-0.4.2
> > -damageproto-1.2.1
> > -dri2proto-2.8
> > -dri3proto-1.0
> > -fixesproto-5.0
> > -fontsproto-2.1.3
> > -glproto-1.4.17
> > -inputproto-2.3.2
> > -kbproto-1.0.7
> > -libdrm-2.4.80
> > -libepoxy-1.4.1
> > -libfontenc-1.1.3
> > -libICE-1.0.9
> > -libpciaccess-0.13.5
> > -libpthread-stubs-0.1
> > -libSM-1.2.2
> > -libvdpau-1.1.1
> > -libX11-1.6.5
> > -libXau-1.0.8
> > -libxcb-1.12
> > -libXdamage-1.1.4
> > -libXext-1.3.3
> > -libXfixes-5.0.3
> > -libXfont2-2.0.1
> > -libxkbfile-1.0.9
> > -libXmu-1.1.2
> > -libxshmfence-1.2
> > -libXt-1.1.5
> > -mesa-17.0.4
> > -mesa-demos-8.3.0
> > -pixman-0.34.0
> > -presentproto-1.1
> > -randrproto-1.5.0
> > -recordproto-1.14.2
> > -renderproto-0.11.1
> > -resourceproto-1.2.0
> > -scrnsaverproto-1.2.2
> > -videoproto-2.3.3
> > -xauth-1.0.10
> > -xcb-proto-1.12
> > -xcmiscproto-1.2.2
> > -xextproto-7.3.0
> > -xf86driproto-2.1.1
> > -xineramaproto-1.2.1
> > -xinit-1.3.4
> > -xorg-server-1.19.3
> > -xproto-7.0.31
> > -xtrans-1.3.5
> > ___
> > xorg@lists.x.org: X.Org support
> > Archives: http://lists.freedesktop.org/archives/xorg
> > Info: https://lists.x.org/mailman/listinfo/xorg
> > Your subscription address: %(user_address)s
> >
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

modeset(0): drmSetMaster failed: Permission denied

2017-04-30 Thread YuGiOhJCJ Mailing-List 
Hello,

I have built xorg-server, xauth, and xinit with their dependencies.
When I do startx I get "xf86OpenConsole: Cannot open virtual console 7 
(Permission denied)".
So, I change the permissions on /dev/tty7 to 660.
Now, when I do startx I get "modeset(0): drmSetMaster failed: Permission 
denied".

I read in the web that some people use SUID on /usr/bin/Xorg to solve this 
problem but I am not sure if it is safe to do that and maybe there is a better 
way.
Same thing for my permissions on /dev/tty7, I would prefer to not change 
permissions if possible.
With the Xorg provided by my distro, there is no SUID on /usr/bin/Xorg and only 
0620 on /dev/tty7 which is better, and it works fine.
So, I am wondering why it does not work with my own Xorg.

Any idea please?

Thank you.
Best regards.

---

Distro: Slackware64 14.2
Kernel: Linux 4.9.24
Built and installed packages:
-bigreqsproto-1.1.2
-compositeproto-0.4.2
-damageproto-1.2.1
-dri2proto-2.8
-dri3proto-1.0
-fixesproto-5.0
-fontsproto-2.1.3
-glproto-1.4.17
-inputproto-2.3.2
-kbproto-1.0.7
-libdrm-2.4.80
-libepoxy-1.4.1
-libfontenc-1.1.3
-libICE-1.0.9
-libpciaccess-0.13.5
-libpthread-stubs-0.1
-libSM-1.2.2
-libvdpau-1.1.1
-libX11-1.6.5
-libXau-1.0.8
-libxcb-1.12
-libXdamage-1.1.4
-libXext-1.3.3
-libXfixes-5.0.3
-libXfont2-2.0.1
-libxkbfile-1.0.9
-libXmu-1.1.2
-libxshmfence-1.2
-libXt-1.1.5
-mesa-17.0.4
-mesa-demos-8.3.0
-pixman-0.34.0
-presentproto-1.1
-randrproto-1.5.0
-recordproto-1.14.2
-renderproto-0.11.1
-resourceproto-1.2.0
-scrnsaverproto-1.2.2
-videoproto-2.3.3
-xauth-1.0.10
-xcb-proto-1.12
-xcmiscproto-1.2.2
-xextproto-7.3.0
-xf86driproto-2.1.1
-xineramaproto-1.2.1
-xinit-1.3.4
-xorg-server-1.19.3
-xproto-7.0.31
-xtrans-1.3.5
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Am I using the ati or vesa driver?

2014-08-10 Thread YuGiOhJCJ Mailing-List 
  So, maybe a bad option or a missing dependency when I try to compile 
  xorg-server-16.0.
  
  You can see here the full output for the configure line:
  http://pastebin.com/wYpk5ek4
 
 (In the future, the config.log file would be more useful)
 
 The problem is this:
 
  checking for GBM... no
 
 Looking at xserver's configure.ac, it actually requires GBM from Mesa
 10.2 or newer for building glamor. I think this should be made clearer
 in the configure output.
 
 If you can't use Mesa 10.2, you'll have to use the standalone glamor
 tree for now.
 

Thank you.
Upgrading from mesa-9.1.7 (official package in Slackware 14.1) to mesa-10.0.2 
was not enough.
So, I have upgraded to mesa-10.2.5.
And very important: the --enable-gbm option!
Here is my configure line:
$ ./configure --prefix=/usr --with-egl-platforms=x11,drm 
--with-gallium-drivers=radeonsi --enable-gbm --enable-shared-glapi 
--enable-glx-tls --sysconfdir=/etc --libdir=/usr/lib --mandir=/usr/man 
--docdir=/usr/doc/mesa-${VERSION} 
--with-dri-driverdir=/usr/lib/xorg/modules/dri --with-dri-drivers=i915,i965 
--disable-llvm-shared-libs

After this, I have compiled xorg-server-1.16.0 and glamor is available now:
$ find /tmp/xorg-server-1.16.0/ -name *glamor*
/tmp/xorg-server-1.16.0/usr/include/xorg/glamor.h
/tmp/xorg-server-1.16.0/usr/lib/xorg/modules/libglamoregl.so
/tmp/xorg-server-1.16.0/usr/lib/xorg/modules/libglamoregl.la

OK, so now I have direct rendering:
$ grep Direct /var/log/Xorg.0.log
[16.450] (II) RADEON(0): Direct rendering enabled

It works :)
Problem solved.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Am I using the ati or vesa driver?

2014-08-09 Thread YuGiOhJCJ Mailing-List 
On Sat, 09 Aug 2014 13:13:46 +0900
Michel Dänzer mic...@daenzer.net wrote:

 On 08.08.2014 20:23, YuGiOhJCJ Mailing-List wrote:
 
  The full log is here:
  http://pastebin.com/a51DRWg6
 
   (II) Loading sub module glamoregl
   (II) LoadModule: glamoregl
   (WW) Warning, couldn't open module glamoregl
   (II) UnloadModule: glamoregl
   (II) Unloading glamoregl
   (EE) RADEON: Failed to load module glamoregl (module does not exist, 0)
 
  Looks like libglamoregl.so isn't installed, at least not in 
  /usr/lib/xorg/modules.
 
  
  I have not installed glamor from the glamor tree.
  I want to use glamor from the xorg-server tree.
  
  So, I build and install xorg (with the --enable-glamor option), then 
  after this I build and install the xf86-video-ati driver.
  But what is strange, is that as you can see before, a libglamoregl.so 
  shared library is required when I type startx.
  Why?
  
  I have said that I would like to use the glamor from the xorg-server tree, 
  so I have not a libglamoregl.so installed file.
  Indeed, the libglamoregl.so file is provided by glamor from the glamor tree 
  only.
  Are you agree?
 
 No, xserver with --enable-glamor also produces libglamoregl.so. It
 sounds like either something went wrong building xserver with
 --enable-glamor, or maybe you didn't specify --prefix=/usr for the
 xserver build, so it was installed to /usr/local/.
 

OK so yeah it is sure that libglamoregl.so is not present after building 
xorg-server-16.0:
$ tar tvf xorg-server-1.16.0-i486-1_ygo.txz | grep glamor
-rw-r--r-- root/root 20481 2014-08-07 13:04 usr/include/xorg/glamor.h

So, maybe a bad option or a missing dependency when I try to compile 
xorg-server-16.0.

You can see here the full output for the configure line:
http://pastebin.com/wYpk5ek4

An interesting line is:
configure: DRI3 disabled because dri3proto not found.

Do you think DRI3 is required to have 3d acceleration with radeon?
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Am I using the ati or vesa driver?

2014-08-09 Thread YuGiOhJCJ Mailing-List 
   The full log is here:
   http://pastebin.com/a51DRWg6
  
(II) Loading sub module glamoregl
(II) LoadModule: glamoregl
(WW) Warning, couldn't open module glamoregl
(II) UnloadModule: glamoregl
(II) Unloading glamoregl
(EE) RADEON: Failed to load module glamoregl (module does not exist, 
   0)
  
   Looks like libglamoregl.so isn't installed, at least not in 
   /usr/lib/xorg/modules.
  
   
   I have not installed glamor from the glamor tree.
   I want to use glamor from the xorg-server tree.
   
   So, I build and install xorg (with the --enable-glamor option), then 
   after this I build and install the xf86-video-ati driver.
   But what is strange, is that as you can see before, a libglamoregl.so 
   shared library is required when I type startx.
   Why?
   
   I have said that I would like to use the glamor from the xorg-server 
   tree, so I have not a libglamoregl.so installed file.
   Indeed, the libglamoregl.so file is provided by glamor from the glamor 
   tree only.
   Are you agree?
  
  No, xserver with --enable-glamor also produces libglamoregl.so. It
  sounds like either something went wrong building xserver with
  --enable-glamor, or maybe you didn't specify --prefix=/usr for the
  xserver build, so it was installed to /usr/local/.
  
 
 OK so yeah it is sure that libglamoregl.so is not present after building 
 xorg-server-16.0:
 $ tar tvf xorg-server-1.16.0-i486-1_ygo.txz | grep glamor
 -rw-r--r-- root/root 20481 2014-08-07 13:04 usr/include/xorg/glamor.h
 
 So, maybe a bad option or a missing dependency when I try to compile 
 xorg-server-16.0.
 
 You can see here the full output for the configure line:
 http://pastebin.com/wYpk5ek4
 
 An interesting line is:
 configure: DRI3 disabled because dri3proto not found.
 
 Do you think DRI3 is required to have 3d acceleration with radeon?

No, with dri3proto, same problem:
$ find /tmp/xorg-server-1.16.0/ -name *glamor*
/tmp/xorg-server-1.16.0/usr/include/xorg/glamor.h

Do you see something strange in my full output for the configure line? 
(previous message)
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Am I using the ati or vesa driver?

2014-08-07 Thread YuGiOhJCJ Mailing-List 
  - xorg-server-1.16.0
  - glamor-egl-0.6.0
 
 With xserver 1.16.0 or later, you should use glamor from the xserver
 tree, not from the separate glamor tree.


Yes, for xorg-server-1.16.0, no problem I can use the embedded glamor.
When I am compiling xorg-server-1.16.0, I do:
$ ./configure --prefix=/usr --libdir=/usr/lib --sysconfdir=/etc 
--localstatedir=/var --infodir=/usr/info --mandir=/usr/man --disable-static 
--with-pic --with-int10=x86emu --with-default-font-path=${DEF_FONTPATH} 
--with-module-dir=/usr/lib/xorg/modules --with-xkb-path=/etc/X11/xkb 
--with-xkb-output=/var/lib/xkb --enable-config-udev --disable-config-hal 
--enable-glamor
I think that the --enable-glamor option means I will use the 
xorg-server-1.16.0 embedded (internal) glamor version, isn't it?

Now, the problem is that without the external glamor, I got an error from the 
radeon driver:
[ 44144.759] (EE) RADEON(0): glamor not available
And I again no have 3d acceleration:
[ 44144.801] (WW) RADEON(0): Direct rendering disabled

The full log is here:
http://pastebin.com/a51DRWg6

Why I have no 3D acceleration please?
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Am I using the ati or vesa driver?

2014-08-05 Thread YuGiOhJCJ Mailing-List 
  But I see a last problem: I have no 3d acceleration!
  As you can see here:
  $ cat /var/log/Xorg.0.log | grep Direct
  [  7567.271] (WW) RADEON(0): Direct rendering disabled
  
  The full xorg log is available here: http://pastebin.com/hSKjXsvL
  
  Do you know how to have 3d acceleration please?
 
 To overcome
 
 http://pastebin.com/raw.php?i=AwPnpSJ7
 
 which you pasted on IRC, you need to compile Mesa with:
 
   --with-egl-platforms=drm

Are you speaking about the segmentation fault + backtrace problem?
I have built mesa-10.0.2 with the --with-egl-platforms=drm option but I 
have again this segmentation fault + backtrace problem.
It does not solved this problem.

Here is the exact configuration line I have used:
./configure --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --mandir=/usr/man 
--docdir=/usr/doc/mesa-10.0.2 --with-dri-driverdir=/usr/lib/xorg/modules/dri 
--with-dri-drivers=i915,i965 --enable-shared-glapi --with-egl-platforms=drm

I am building and installing packages in this order:
- libdrm-2.4.56
- mesa-10.0.2
- mesa-demos-8.1.0
- fontsproto-2.1.3
- glproto-1.4.17
- libepoxy-1.2
- xextproto-7.3.0
- xproto-7.0.26
- xtrans-1.3.4
- xorg-server-1.16.0
- glamor-egl-0.6.0
- xf86-video-ati-7.4.0
- xf86-video-intel-2.99.912
- xf86-video-vesa-2.3.3

Anyway, if I keep the official packages from Slackware 14.1, I have not this 
segmentation fault + backtrace problem.
So, currently I am using:
- libdrm-2.4.46
- mesa-9.1.7
- mesa-demos-8.1.0
- fontsproto-2.1.2
- glproto-1.4.16
- libepoxy-1.2
- xextproto-7.2.1
- xproto-7.0.24
- xtrans-1.2.7
- xorg-server-1.14.3
- glamor-egl-0.6.0
- xf86-video-ati-7.2.0
- xf86-video-intel-2.21.15
- xf86-video-vesa-2.3.3

In this second case, the problem is that I have no direct rendering.
As you can see here:
$ cat /var/log/Xorg.0.log | grep Direct
[  7567.271] (WW) RADEON(0): Direct rendering disabled

The full xorg log is available here: http://pastebin.com/hSKjXsvL

Maybe, it is just a permission problem, a xorg configuration problem, or 
something like that.

What can I do to get direct rendering please?
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Am I using the ati or vesa driver?

2014-08-04 Thread YuGiOhJCJ Mailing-List 
On Thu, 31 Jul 2014 23:14:34 +0900
Michel Dänzer mic...@daenzer.net wrote:

 On 31.07.2014 19:47, YuGiOhJCJ Mailing-List wrote:
 
  I give you my full Xorg.0.log here:
  http://pastebin.com/fsPBgt5P
 
  If you find an interesting line telling me what driver I am using please 
  highlight it for me.
 
  The radeon driver fails to initialize because of this:
 
  [  1684.773] (II) [KMS] drm report modesetting isn't supported.
 
  Check the dmesg output for why the radeon kernel driver isn't active.
  
  Indeed, this problem is because my radeon module is not loaded:
  $ lsmod | grep radeon
  
  So, I load it:
  $ sudo modprobe radeon
  
  Then after it I restart X, then I got:
  $ sudo dmesg | grep drm
  [ 5516.131529] [drm] Initialized drm 1.1.0 20060810
  [ 5516.191147] [drm] radeon kernel modesetting enabled.
  
  So, it seems to be good now.
 
 No, there should be a lot more output. I suspect the kernel is too old
 to support your Kabini GPU.

Indeed, my kernel was too old.
I have upgraded from linux-3.10.17 to linux-3.15.8 and now it works:
$ sudo dmesg | grep drm
[7.256525] [drm] Initialized drm 1.1.0 20060810
[7.356838] [drm] radeon kernel modesetting enabled.
[7.359272] [drm] initializing kernel modesetting (KABINI 0x1002:0x9839 
0x1043:0x141D).
[7.359484] [drm] register mmio base: 0xFEB0
[7.359607] [drm] register mmio size: 262144
[7.359781] [drm] doorbell mmio base: 0xD000
[7.359903] [drm] doorbell mmio size: 8388608
[7.360705] [drm] Detected VRAM RAM=512M, BAR=256M
[7.360882] [drm] RAM width 128bits DDR
[7.361827] [drm] radeon: 512M of VRAM memory ready
[7.361951] [drm] radeon: 1024M of GTT memory ready.
[7.362102] [drm] Loading KABINI Microcode
[7.444224] [drm] Internal thermal controller without fan control
[7.445271] [drm] radeon: dpm initialized
[   39.111953] [drm] GART: num cpu pages 262144, num gpu pages 262144
[   39.134989] [drm] PCIE GART of 1024M enabled (table at 0x00277000).
[   39.139336] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   39.139466] [drm] Driver supports precise vblank timestamp query.
[   39.139855] [drm] radeon: irq initialized.
[   39.143992] [drm] ring test on 0 succeeded in 3 usecs
[   39.144211] [drm] ring test on 1 succeeded in 3 usecs
[   39.144368] [drm] ring test on 2 succeeded in 3 usecs
[   39.144825] [drm] ring test on 3 succeeded in 3 usecs
[   39.144964] [drm] ring test on 4 succeeded in 2 usecs
[   39.201193] [drm] ring test on 5 succeeded in 2 usecs
[   39.221352] [drm] UVD initialized successfully.
[   39.221990] [drm] ib test on ring 0 succeeded in 0 usecs
[   39.222412] [drm] ib test on ring 1 succeeded in 0 usecs
[   39.222815] [drm] ib test on ring 2 succeeded in 0 usecs
[   39.223238] [drm] ib test on ring 3 succeeded in 0 usecs
[   39.223653] [drm] ib test on ring 4 succeeded in 0 usecs
[   39.244927] [drm] ib test on ring 5 succeeded
[   39.282221] [drm] radeon atom DIG backlight initialized
[   39.282369] [drm] Radeon Display Connectors
[   39.282497] [drm] Connector 0:
[   39.282623] [drm]   LVDS-1
[   39.282746] [drm]   HPD1
[   39.282873] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 
0x653c
[   39.283071] [drm]   Encoders:
[   39.283217] [drm] LCD1: INTERNAL_UNIPHY
[   39.283345] [drm] Connector 1:
[   39.283470] [drm]   HDMI-A-1
[   39.283593] [drm]   HPD2
[   39.283717] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 
0x654c
[   39.283915] [drm]   Encoders:
[   39.284040] [drm] DFP1: INTERNAL_UNIPHY
[   39.284166] [drm] Connector 2:
[   39.284301] [drm]   VGA-1
[   39.284427] [drm]   DDC: 0x65c0 0x65c0 0x65c4 0x65c4 0x65c8 0x65c8 0x65cc 
0x65cc
[   39.284626] [drm]   Encoders:
[   39.284751] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[   39.386891] [drm] fb mappable at 0xC047B000
[   39.387031] [drm] vram apper at 0xC000
[   39.387156] [drm] size 4325376
[   39.387287] [drm] fb depth is 24
[   39.387411] [drm]pitch is 5632
[   39.387731] fbcon: radeondrmfb (fb0) is primary device
[   39.440530] radeon :00:01.0: fb0: radeondrmfb frame buffer device
[   39.453620] [drm] Initialized radeon 2.38.0 20080528 for :00:01.0 on 
minor 0

Now, all my previous problems are solved:
- 1 screen only used (the external VGA screen): solved! (the two screens are 
working together)
- the font is too big: solved! (the font size is normal)
- the xrandr command tells me Failed to get size of gamma for output 
default: solved! (this message is not displayed anymore)

But I see a last problem: I have no 3d acceleration!
As you can see here:
$ cat /var/log/Xorg.0.log | grep Direct
[  7567.271] (WW) RADEON(0): Direct rendering disabled

The full xorg log is available here: http://pastebin.com/hSKjXsvL

Do you know how to have 3d acceleration please?

Thank you.
Best regards.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org

Re: Am I using the ati or vesa driver?

2014-07-31 Thread YuGiOhJCJ Mailing-List 
  [...]
  So, I think that I am using the vesa Xorg driver for generic VESA video
  cards instead of the ati video driver.
 
  How to be sure about that?
 
  Have a look at Xorg logs, usually /var/log/Xorg.0.log.
  -- 
  
  Yeah, but it seems to load both drivers (and other drivers too):
  $ cat /var/log/Xorg.0.log | grep LoadModule
  [...]
  [  1684.745] (II) LoadModule: ati
  [  1684.746] (II) LoadModule: radeon
  [  1684.748] (II) LoadModule: vesa
  [  1684.749] (II) LoadModule: fbdev
  [...]
  
  I give you my full Xorg.0.log here:
  http://pastebin.com/fsPBgt5P
  
  If you find an interesting line telling me what driver I am using please 
  highlight it for me.
 
 The radeon driver fails to initialize because of this:
 
 [  1684.773] (II) [KMS] drm report modesetting isn't supported.
 
 Check the dmesg output for why the radeon kernel driver isn't active.

Indeed, this problem is because my radeon module is not loaded:
$ lsmod | grep radeon

So, I load it:
$ sudo modprobe radeon

Then after it I restart X, then I got:
$ sudo dmesg | grep drm
[ 5516.131529] [drm] Initialized drm 1.1.0 20060810
[ 5516.191147] [drm] radeon kernel modesetting enabled.

So, it seems to be good now.

But I think I am again using vesa drivers because:
$ cat /var/log/Xorg.0.log | grep LoadModule
[  6993.222] (II) LoadModule: glx
[  6993.249] (II) LoadModule: ati
[  6993.251] (II) LoadModule: radeon
[  6993.258] (II) LoadModule: vesa
[  6993.260] (II) LoadModule: modesetting
[  6993.267] (II) LoadModule: fbdev
[  6993.298] (II) LoadModule: vbe
[  6993.299] (II) LoadModule: int10
[  6993.370] (II) LoadModule: ddc
[  6993.476] (II) LoadModule: shadow
[  6993.477] (II) LoadModule: fb
[  6993.480] (II) LoadModule: int10
[  6995.208] (II) LoadModule: evdev

This is my new full Xorg.0.log file:
http://pastebin.com/krvwi0rd

Do you see why I am on vesa instead of ati?
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Am I using the ati or vesa driver?

2014-07-30 Thread YuGiOhJCJ Mailing-List 
Hello,

My computer is an ASUS x102ba [1].

When I type:
$ startx

I see that my display is strange:
- 1 screen only used (the external VGA screen)
- the font is too big
- the xrandr command tells me Failed to get size of gamma for output default

So, I think that I am using the vesa Xorg driver for generic VESA video cards 
instead of the ati video driver.

How to be sure about that?

Thank you.
Best regards.

[1] http://www.asus.com/Notebooks_Ultrabooks/X102BA/specifications/
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Am I using the ati or vesa driver?

2014-07-30 Thread YuGiOhJCJ Mailing-List 
 [...]
  So, I think that I am using the vesa Xorg driver for generic VESA video
  cards instead of the ati video driver.
  
  How to be sure about that?
 
 Have a look at Xorg logs, usually /var/log/Xorg.0.log.
 -- 

Yeah, but it seems to load both drivers (and other drivers too):
$ cat /var/log/Xorg.0.log | grep LoadModule
[...]
[  1684.745] (II) LoadModule: ati
[  1684.746] (II) LoadModule: radeon
[  1684.748] (II) LoadModule: vesa
[  1684.749] (II) LoadModule: fbdev
[...]

I give you my full Xorg.0.log here:
http://pastebin.com/fsPBgt5P

If you find an interesting line telling me what driver I am using please 
highlight it for me.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: upgraded from CPU Intel Celeron G440 to G1630

2014-07-18 Thread YuGiOhJCJ Mailing-List 
Solved!
I have just upgraded to xf86-video-intel-2.99.912.

On Sat, 5 Jul 2014 08:28:11 +0200
YuGiOhJCJ Mailing-List yugiohjcj-mailingl...@laposte.net wrote:

 Hello,
 
 I have upgraded from CPU Intel Celeron G440 to G1630 and I encounter some 
 graphical problems [1] (part of text missing on my screen)... So, I have 
 upgraded to linux-3.15.3 but the problem is again here. Do you have a 
 solution please?
 
 (I  am on Slackware 14.0 with mesa-10.0.2 and xorg-server-1.12.3)
 
 Thank you.
 Best regards.
 
 [1] https://lut.im/jEF4ikaC/fc9NHBbd
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

upgraded from CPU Intel Celeron G440 to G1630

2014-07-05 Thread YuGiOhJCJ Mailing-List 
Hello,

I have upgraded from CPU Intel Celeron G440 to G1630 and I encounter some 
graphical problems [1] (part of text missing on my screen)... So, I have 
upgraded to linux-3.15.3 but the problem is again here. Do you have a solution 
please?

(I  am on Slackware 14.0 with mesa-10.0.2 and xorg-server-1.12.3)

Thank you.
Best regards.

[1] https://lut.im/jEF4ikaC/fc9NHBbd
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: xmodmap 1.0.7: left shift + right shift + comma keys

2014-03-13 Thread YuGiOhJCJ Mailing-List 
On Wed, 12 Mar 2014 21:14:26 +0100
Thomas Lübking thomas.luebk...@gmail.com wrote:

 On Mittwoch, 12. März 2014 20:15:51 CEST, YuGiOhJCJ Mailing-List wrote:
 
  What is a bit strange is that my keyboard can handle the left 
  shift + right shift + exclam but is not able to handle the 
  left shift + right shift + comma that seems to be similar 
  (same number of keys pushed at the same time).
 
 ? is where qwerty/z keyboards have the M and no special char - this might 
 be relevant (for the sublying electronics being re-used from an original 
 qwerty keyboard design)
 You're looking for ¿, right? Is it not on AltGr+Shift+, (ie. AltGr+?) 
 anyway? (unless you've special reasons for the specific double-shift combo)
 

Yes I am looking for the ¿ character.
I don't want the Spanish characters to be on a AltGr combination because for 
the É Spanish character, it will overwrite my € character (done with 
AltGr+E).
I never use the right shift key when I am typing on my keyboard, so I prefer to 
put all my Spanish characters with this key.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

xmodmap 1.0.7: left shift + right shift + comma keys

2014-03-12 Thread YuGiOhJCJ Mailing-List 
Hello,

I have a problem with xmodmap 1.0.7 because it should write a question down 
character when I push the left shift + right shift + comma keys but 
nothing is written.

My keyboard map is fr + my ~/.xmodmaprc [1] file.

Do you see something wrong in my ~/.xmodmaprc file?

Thank you.
Best regards.

[1]$ cat ~/.xmodmaprc 
! ~/.xmodmaprc
! keycode keysym = key shift+key mode_switch+key 
mode_switch+shift+key altgr+key altgr+shift+key

clear shift
add shift = Shift_L

add mod3 = Scroll_Lock

! Spanish keys
keycode 24 = a A aacute Aacute ae AE ae
keycode 26 = e E eacute Eacute EuroSign cent EuroSign
keycode 30 = u U uacute Uacute downarrow uparrow downarrow
keycode 31 = i I iacute Iacute rightarrow idotless rightarrow
keycode 32 = o O oacute Oacute oslash Oslash oslash
keycode 57 = n N ntilde Ntilde n N n
keycode 58 = comma question comma questiondown dead_acute dead_doubleacute 
dead_acute
keycode 61 = exclam section exclamdown section dead_belowdot dead_abovedot 
dead_belowdot

! Maps the Mode key to the Alt key
!keycode 64 = Mode_switch

! Maps the Mode key to the Alt Gr key
! keycode 108 = Mode_switch

! Maps the Mode key to the Right Shift key
keycode 62 = Mode_switch
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: xmodmap 1.0.7: left shift + right shift + comma keys

2014-03-12 Thread YuGiOhJCJ Mailing-List 
On Wed, 12 Mar 2014 19:59:08 +0100
wettstein...@solnet.ch wrote:

  I have a problem with xmodmap 1.0.7 because it should write a
  question down character when I push the left shift + right shift
  + comma keys but nothing is written.
 
 This might be a hardware problem.  Most keyboards cannot handle
 arbitrary combination of more than two keys.  To check, you could use
 xev to see whether an event is generated.  If not, it is hardware.
 
 Andreas
 

Indeed, with xev, there are no event when I press the third key of this 
combination.
What is a bit strange is that my keyboard can handle the left shift + right 
shift + exclam but is not able to handle the left shift + right shift + 
comma that seems to be similar (same number of keys pushed at the same time).

So, I don't like this combination, but I have no choice:
keycode 61 = exclam section exclamdown questiondown dead_belowdot dead_abovedot 
dead_belowdot

Instead of typing left shift + right shift + comma for my question down 
character it will be left shift + right shift + exclam.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s