| View previous topic :: View next topic |
| Author |
Message |
merrak
n00b
Joined: 02 Mar 2007
Posts: 64
Location: Raleigh, North Carolina
|
 Posted: Sun Mar 04, 2007 8:11 pm Post subject: Beryl: Just a White Screen [Solved] |
 |
|
I've searched up and down and haven't found anything that quite matches what I've received when trying to start 'Beryl' from terminal.
| Quote: | **************************************************************
* Beryl system compatiblity check *
**************************************************************
Detected xserver : XGL
Checking Display :0.0 ...
Checking for XComposite extension : passed (v0.3)
Checking for XDamage extension : passed
Checking for RandR extension : passed
Checking for XSync extension : passed
Reloading options
beryl: pixmap 0x2200042 can't be bound to texture
beryl: Couldn't bind redirected window 0xe00003 to texture
beryl: pixmap 0x2200044 can't be bound to texture
beryl: Couldn't bind redirected window 0x200000f to texture |
The pixmap errors continue. And of course, the screen goes white. I've only salvaged these error messages from "ctrl-c"ing out of the white screen. Anyone have any ideas?
(Relevant?) system specs: AMD64, Gnome 2.16, Kernel 2.6.19-gentoo-r5 (used genkernel)
nvidia - driver version 1.0.9631
Last edited by merrak on Thu Mar 08, 2007 5:27 pm; edited 1 time in total |
|
| Back to top |
|
 |
thestick
Guru
Joined: 07 Apr 2006
Posts: 531
Location: /dev/urandom
|
|
| Back to top |
|
|
merrak
n00b
Joined: 02 Mar 2007
Posts: 64
Location: Raleigh, North Carolina
|
| Posted: Sun Mar 04, 2007 11:04 pm Post subject: No Luck |
|
|
| Beryl does autostart but after going through those three steps it behaves the same. Same error messages also. |
|
| Back to top |
|
|
thestick
Guru
Joined: 07 Apr 2006
Posts: 531
Location: /dev/urandom
|
|
| Back to top |
|
|
merrak
n00b
Joined: 02 Mar 2007
Posts: 64
Location: Raleigh, North Carolina
|
| Posted: Mon Mar 05, 2007 6:13 pm Post subject: |
|
|
I have: NVidia GeForce4 MX 4000 (128MB Video RAM)
Using Gnome
I've tried both compiz and beryl, and both have the same error. So I am thinking the problem has to be with something they both share. (OpenGL related?)
The same error messages still persist. It also seems that when I can ctrl-c out of the white screen, all but one of Gnome's four desktops (on the bottom right corner of screen) disappear, and newly opened applications fail to open correctly (they freeze with their displays open). There's a variety of other weird results that ultimately require a restart to fix. This one really has me stumped. |
|
| Back to top |
|
|
thestick
Guru
Joined: 07 Apr 2006
Posts: 531
Location: /dev/urandom
|
| Posted: Mon Mar 05, 2007 7:49 pm Post subject: |
|
|
save this as startxgl.sh
chmod +x startxgl.sh
| Code: |
#!/bin/bash
X :$1 &
eval `dbus-launch --exit-with-session --sh-syntax` &
sleep 3 &
DISPLAY=:$1 xterm &
DISPLAY=:$1 dbus-launch beryl --replace --force-nvidia &
DISPLAY=:$1 dbus-launch emerald &
|
./startxgl.sh 1
you should get a xterm with decorations. |
|
| Back to top |
|
|
merrak
n00b
Joined: 02 Mar 2007
Posts: 64
Location: Raleigh, North Carolina
|
| Posted: Mon Mar 05, 2007 8:48 pm Post subject: |
|
|
No white screen this time  . But I'm not sure if it's working. I got a gray and black screen with an "X" mouse cursor. Nothing else shows up and there is no way out I can find other than a restart. I logged some output running the script >> out.txt, I get the following message twice.
| Quote: | **************************************************************
* Beryl system compatiblity check *
**************************************************************
**************************************************************
* Beryl system compatiblity check *
**************************************************************
|
|
|
| Back to top |
|
|
thestick
Guru
Joined: 07 Apr 2006
Posts: 531
Location: /dev/urandom
|
| Posted: Mon Mar 05, 2007 10:06 pm Post subject: |
|
|
you can stop that with ctrl + alt + backspace // kills X
ok
modified the script a little.
| Code: |
#!/bin/bash
X :$1 &
eval `dbus-launch --exit-with-session --sh-syntax` &
sleep 3 &
DISPLAY=:$1 gnome-terminal &
DISPLAY=:$1 dbus-launch beryl --replace --force-nvidia &
DISPLAY=:$1 dbus-launch emerald & |
you can test if beryl is working by pressing ctrl + alt + left arrow.
ctrl +alt + backspace to exit |
|
| Back to top |
|
|
merrak
n00b
Joined: 02 Mar 2007
Posts: 64
Location: Raleigh, North Carolina
|
| Posted: Tue Mar 06, 2007 1:11 am Post subject: |
|
|
Same result, but I think I got some more useful output at least!
Here is what comes out. I've tried best I could to only keep relevant messages here. Hopefully nothing important is missing.
| Quote: |
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/RLWCPU6422:1
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
|
| Quote: |
(==) Using config file: "/etc/X11/xorg.conf"
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc(pc104)+us" };
xkb_geometry { include "pc(pc104)" };
|
| Quote: |
eval `dbus-launch --exit-with-session --sh-syntax`
|
| Quote: |
AUDIT: Mon Mar 5 15:06:35 2007: 8409 X: client 1 rejected from local host
AUDIT: Mon Mar 5 15:06:35 2007: 8409 X: client 2 rejected from local host
AUDIT: Mon Mar 5 15:06:35 2007: 8409 X: client 3 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
(gnome-terminal:8412): Gtk-WARNING **: cannot open display:
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
(emerald:8424): Gtk-WARNING **: cannot open display:
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
xvinfo: Unable to open display :1
AUDIT: Mon Mar 5 15:06:35 2007: 8409 X: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
xdpyinfo: unable to open display ":1".
**************************************************************
* Beryl system compatiblity check *
**************************************************************
AUDIT: Mon Mar 5 15:06:35 2007: 8409 X: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
Error: unable to open display (null)
Relaunching beryl with __GL_YIELD="NOTHING"
[4] Exit 1 DISPLAY=:$1 gnome-terminal
[6]+ Exit 1 DISPLAY=:$1 dbus-launch emerald
|
| Quote: |
AUDIT: Mon Mar 5 15:06:35 2007: 8409 X: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
xvinfo: Unable to open display :1
AUDIT: Mon Mar 5 15:06:35 2007: 8409 X: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
xdpyinfo: unable to open display ":1".
**************************************************************
* Beryl system compatiblity check *
**************************************************************
AUDIT: Mon Mar 5 15:06:35 2007: 8409 X: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
Error: unable to open display (null)
RLWCPU6422 gnomest # AUDIT: Mon Mar 5 15:06:35 2007: 8409 X: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
beryl: Couldn't open display :1
[5]+ Exit 1 DISPLAY=:$1 dbus-launch beryl --replace --force-nvidia
|
| Quote: |
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
|
|
|
| Back to top |
|
|
thestick
Guru
Joined: 07 Apr 2006
Posts: 531
Location: /dev/urandom
|
| Posted: Tue Mar 06, 2007 7:37 am Post subject: |
|
|
this is very strange.
try syncing and
emerge -NvDu world.
after that,
run only this script
script.sh
| Code: |
#!/bin/bash
X :$1 &
sleep 3 &
DISPLAY=:$1 gnome-terminal &
|
./script.sh 1
this has GOT to show up an terminal.
if you can type from within it , run
beryl --force-nvidia & |
|
| Back to top |
|
|
merrak
n00b
Joined: 02 Mar 2007
Posts: 64
Location: Raleigh, North Carolina
|
| Posted: Wed Mar 07, 2007 1:10 am Post subject: |
|
|
Same results it looks like... gray and black screen.
Could this be a problem with X not being configured right? Neither Beryl nor Compiz work |
|
| Back to top |
|
|
merrak
n00b
Joined: 02 Mar 2007
Posts: 64
Location: Raleigh, North Carolina
|
| Posted: Wed Mar 07, 2007 1:45 am Post subject: |
|
|
Actually, I have a different set of error messages this time
| Quote: |
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/RLWCPU6422:1
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux RLWCPU6422 2.6.19-gentoo-r5 #1 SMP Sun Mar 4 15:49:04 EST 2007 x86_64
Build Date: 04 March 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Tue Mar 6 15:45:38 2007
(==) Using config file: "/etc/X11/xorg.conf"
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc(pc104)+us" };
xkb_geometry { include "pc(pc104)" };
AUDIT: Tue Mar 6 15:45:41 2007: 6221 X: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
(gnome-terminal:6223): Gtk-WARNING **: cannot open display:
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
[3] Done X :$1
[4]- Done sleep 3
[5]+ Exit 1 DISPLAY=:$1 gnome-terminal
|
The two "Xlib" errors toward the end (connection refused by sever, no protocol specificed) I've seen just about every time. |
|
| Back to top |
|
|
thestick
Guru
Joined: 07 Apr 2006
Posts: 531
Location: /dev/urandom
|
| Posted: Wed Mar 07, 2007 6:29 am Post subject: |
|
|
does your X server work in a normal mode (without beryl / emerald / compiz / xgl / aiglx) ?
you have X xorg aiglx glitz cairo is your use flags?
did you update your system with emerge -NvDu world?
backup your /etc/X11/xorg.conf
| Code: |
cp /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
|
and run xorgconfig. |
|
| Back to top |
|
|
FGA
Apprentice
Joined: 07 Apr 2004
Posts: 179
|
| Posted: Wed Mar 07, 2007 1:11 pm Post subject: |
|
|
I had the white screen problem and it wad that I had disabled direct rendering.
Do a | Code: | | $ glxinfo | grep -i "direct rendering" |
I had it disbled because I reemerged xorg-server. An "eselect opengl set nvidia" fixed the problem |
|
| Back to top |
|
|
merrak
n00b
Joined: 02 Mar 2007
Posts: 64
Location: Raleigh, North Carolina
|
| Posted: Wed Mar 07, 2007 5:30 pm Post subject: |
|
|
As far as I can tell X server works in normal mode fine. The script only shows the error message
| Quote: |
AUDIT: Wed Mar 7 07:25:07 2007: 6200 X: client 1 rejected from local host
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
(gnome-terminal:6202): Gtk-WARNING **: cannot open display:
|
The use flags are set and system updated as you suggested. I re-ran xorgconfig but ended up with the exact same config file I had before. Maybe this is relevant - my video card does not show up in its database, and X does fail to start unless I hand-edit the file to use "nvidia" as the driver. "nv" doesn't work.
My direct rendering is still disabled. I did "eselect opengl set nvidia", yet it remains disabled. |
|
| Back to top |
|
|
thestick
Guru
Joined: 07 Apr 2006
Posts: 531
Location: /dev/urandom
|
| Posted: Wed Mar 07, 2007 6:04 pm Post subject: |
|
|
this is the relevant part is xorg.conf.
| Code: |
Section "Device"
Identifier "geforcef4mx"
Driver "nvidia"
Option "NoLogo" "True"
Option "RenderAccel" "True"
Option "AllowGLXWithComposite" "True"
Option "AddARGBGLXVisuals" "True"
EndSection
...
Section "Extensions"
Option "Composite" "Enable"
EndSection
|
this is my last idea : use ~x86 , it is fairy stable for a desktop system.
ACCEPT_KEYWORDS="~x86" in /etc/make.conf and emerge -NvuD world |
|
| Back to top |
|
|
FGA
Apprentice
Joined: 07 Apr 2004
Posts: 179
|
| Posted: Wed Mar 07, 2007 9:48 pm Post subject: |
|
|
| Are you using nvidia-legacy-drivers? I think it's needed for the geforce 4 mx |
|
| Back to top |
|
|
merrak
n00b
Joined: 02 Mar 2007
Posts: 64
Location: Raleigh, North Carolina
|
| Posted: Thu Mar 08, 2007 5:27 pm Post subject: Slick! |
|
|
| Adding those options to xorg.conf seems to have done the trick. Thanks for all your help |
|
| Back to top |
|
|
|
Desktop Environments
