interesting results with beryl
Posts: 26
I have noticed two different behaviors with beryl.
If I specify 3D (beryl) at login, I get black windows if the window (or combinations of windows) are too big. For example, I open firefox at 1/4 the area of my desktop, it displays correctly. If I increase the size to almost the entire desktop, it goes black. If I shrink it to about half, it displays again. If I then open another window, it goes black. If I make both around 1/4 the desktop size, minimize each, then restore each, both display properly.
If I do not chose 3D at login but instead use the beryl manager to initial 3D, it works will.
Before either, I modified the berly environment to Force AIGLX, and set visual effects (ed effects - checked, animation - checked, blur effects - unchecked, fading windows - checked, trailfocus - unchecked, window decoration - checked, wobbly window - unchecked.
I have an hp pavillion notebook, dv6113us. It has an amd64-x2, 1gb, 80gb, dvd burner, dell 1390 wireless, and nvidia 6150 video. Now, how much memory the 6150 video is using, I am not certain. It can use 32mb-256mb, but it is not configurable in the bios. The bios says it is configured dynamically in the driver. I could not identify how much it is using and how to adjust it.
Any thoughts?
Strange that the black
Posts: 2299
Strange that the black screen only happens when you start at logon. However, Warren has supplied that option, since launching Beryl Manager from within KDE can lead to erratic behaviour. I can vouch for that from first hand experience.
I think you can set the RAM to use in xorg.conf, device section: VideoRam = 262144
Newbie or not Newbie, there's always a question
just wait
Posts: 26
Another observation: If I try to start the beryl manager immediately after booting, it fails. I can try this 3 or 4 times right away, it still fails (meaning the cursor changes to an hourglass wait cursor with a bouncing beryl diamond icon, but after bouncing for a few seconds, it disappears and no new icon appears in the system tray).
If I wait for a couple of minutes, then try to start the beryl manager, it works first time. Then I can restart the beryl windows manager, and everything works perfectly.
Anyone else have any similar experiences? Any ideas why this works so?