ArchThis Forum is for the discussion of Arch Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've used the guide on wikiarch, the beryl guide, i've even change my driver from fglrx to the opensource radeon, which i like better btw :P
So when i insert beryl and emerald into my .xinitrc it just won't load, it loads a bit, even shows my cursor theme, to just crash on something called and error 11.
When i change to ny openbox in .xinitrc it works fine, i am infact writing from my openbox right now.
So any helpful ideas how to make beryl run?
I think you and I may have similar problems, even though we're probably using completely different hardware.
Do me a favor and try this out. Revert back to your original wm (kxm/kwin/kde or whatever it is that you use). Do a console login (hit ALT+N at the login screen). Login, and then "startx" and get into to KDE/Gnome.
Open up konsole and type glxinfo | grep "Render" to make sure Direct Rendering is working.
Also check "/var/log/Xorg.0.log" and look for any (EE) or (WW) lines to give you a better idea of what might be wrong and to again make sure DRI and AIGLX are both enabled properly.
Anyway, once you're sure everything is working properly, close any open windows, and bring the Konsole window to the centre of the screen. Move the mouse to an empty part of the screen so it's not touching any icon or window. Then run "beryl-manager" from konsole, and DO NOT MOVE THE MOUSE OR PRESS ANY KEY.
If you do it this way, does Beryl load up properly? It should go through the entire splash screen and load the window decorations. If it works, press a key, and it should crash the X server and put you back out to the console. Alternatively, move the mouse so it touches an icon or a window, and the X server will again crash.
If this happens then you and I have got the same problem. Let me know so I can figure a solution.
Otherwise, if you do not have the same symptoms, then you should post your /etc/X11/xorg.conf file and your /var/log/Xorg.0.log files so we can go thru them.
By the way, I'm running gentoo on a really old Compaq with a built in i810e graphics chip. Beryl loads up fine but crashes the X server as soon as I press a key on the keyboard or the mouse touches any icon, panel or window on the screen. I have no idea what the problem is, and it's driving me nuts! Not to mention that I can ONLY enable DRI in 16bit...
Hehe i am running two things that auto update so when i activate beryl-manager it only takes a few milliseconds before it crashes. I use openbox as my wm, my machine is an amd turion 64 1,7ghz with radeon X200M graphics with 16-128mb ram shared with the 384-496mb ram.
What i have learned so far is that AIGLX is only supported by default in the radeon driver(not fglrx), but the radeon driver only supports DRI from radeon 9600 and downwards. I am using the fglrx driver and DRI is running on my machine, another oddity i found out is that two almost similar xorg.conf files with a few options to differ, have the strange behavior of one not running DRI and one do. They both have the so called required DRI settings, but as said one works and one doesn't? Link to thread: DRI
If you would want to discuss this at a faster rate to find a solution, as noone else seems to want to, i can be found on irc.quakenet.org @ #wdi and #hackerlounge
I am o irc almost 24-7, but i will also check in here every once in a while. If you should not be needing my help, then happy hunting
...another oddity i found out is that two almost similar xorg.conf files with a few options to differ, have the strange behavior of one not running DRI and one do.
Hmm... it's not related to bit depth? If you go thru your /var/log/Xorg.0.log, I'm sure you'll find the answer within a few minutes.
After reading your posts, I think we have different problems. I bet I'm probably using incompatible builds, or crossing builds, or maybe I'm unable to allocate enough memory to run beryl. who knows. I've given up for now until I can scrounge up some more memory from somewhere.
However, I really think the best bet for you is to go thru the Xorg.0.log file and see if you find any warnings or errors.
i know it's not a problem with the bit's anyway, as they both use same bit number...
but thx for the answer, how much memory do you have?
I currently have 256megs system ram of which I can allocate 12megs to the onboard i810 video card (assigning more doesn't seem to work in xorg.conf). On top of that, I am unable to have DRI in anything other than 16-bit-depth mode. I wonder if that's my problem with beryl...?
...I'm going to be upgrading to a new computer soon, so I don't think I'll get to the bottom of my problem.
BTW, did you find the solution to your problem? Did you go thru all the Xorg.?.log files in your /var/log ?