Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 159663 - x11-wm/beryl does not work w/ intel i915 DRI and 24bit color depth
Summary: x11-wm/beryl does not work w/ intel i915 DRI and 24bit color depth
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Joshua Jackson (RETIRED)
URL:
Whiteboard:
Keywords:
: 159664 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-01-01 18:02 UTC by David
Modified: 2007-01-03 05:45 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
this is the screenshoot of my problem (beryl1.png,56.83 KB, image/png)
2007-01-02 03:55 UTC, David
Details
my xorg.conf (xorg.conf,15.06 KB, text/plain)
2007-01-02 11:48 UTC, David
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David 2007-01-01 18:02:11 UTC
I'm using kde 3.5.5 with aixgl and intel 915 dri activated.
Beryl works well with 16bits using the gentoo-wiki guide to install it.
But wen I change the color to 24bits the middle of the screen turns white.
In the shell when I execute "beryl-manager" there are this log==>

kwin: Fatal IO error: client killed
libGL warning: 3D driver claims to not support visual 0x4b
beryl: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed.

** (process:13633): WARNING **: get_setting_is_integrated not found in backend ini

** (process:13633): WARNING **: get_setting_is_read_only not found in backend ini

** (process:13633): WARNING **: get_setting_is_integrated not found in backend ini

** (process:13633): WARNING **: get_setting_is_read_only not found in backend ini
Initiating splash
beryl: water: GL_ARB_fragment_program is missing
beryl: Failed to load slide: /usr/share/beryl/cubecaps.png
beryl: Failed to load slide: /usr/share/beryl/cubecaps.png
Reloading all options.
[SPLASH]: Could not load splash background image "/usr/share/beryl/splash_background.png" !
[SPLASH]: Could not load splash logo image "/usr/share/beryl/splash_logo.png" !
X connection to :0.0 broken (explicit kill or server shutdown).



in Xorg log ==>
cat /var/log/Xorg.0.log|grep WW
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): config file hsync range 43.8857-48.5053kHz not within DDC hsync ranges.
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): xf86AllocateGARTMemory: allocation of 16 pages failed
(WW) I810(0): xf86AllocateGARTMemory: allocation of 8 pages failed
(WW) I810(0): xf86AllocateGARTMemory: allocation of 1 pages failed
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-01-02 01:10:28 UTC
*** Bug 159664 has been marked as a duplicate of this bug. ***
Comment 2 David 2007-01-02 03:55:30 UTC
Created attachment 105148 [details]
this is the screenshoot of my problem
Comment 3 Joshua Jackson (RETIRED) gentoo-dev 2007-01-02 09:17:09 UTC
I have a intel 915gm chipset that doesn't have this issue at 16 or 24 bit. I will try to reproduce it but not sure if I'll be able to. I'd recommend that you try reemerging xorg-server, mesa, and xf86-video-i810 to see if that fixes the problem. Also, what version of the xf86-video-i810 driver are you running?

The errors in the xorg log are normal unfortunately, and not what I'd say are a cause of the problem. 

Another thing you might try, is to remove your .beryl and .emerald directories as I'm seeing at least one thing in the errors you reported that might be fixed by removing those. Let me know after you've tried all the steps if the white box of death is still there.
Comment 4 David 2007-01-02 11:46:56 UTC
I have tried to delete the directories .beryl and .emerald and the same.
I have tried to emerge de ~x86 version of x11-drivers/xf86-video-i810 and the same.
I have these packages ==>
x11-base/xorg-server-1.1.1-r1
media-libs/mesa-6.5.1-r1
x11-drivers/xf86-video-i810-1.7.3 befor I had the 1.6.5 and the same.
maybe It is my xorg.conf :S.

Comment 5 David 2007-01-02 11:48:23 UTC
Created attachment 105203 [details]
my xorg.conf
Comment 6 Alex 2007-01-02 11:51:28 UTC
Well from looking at your xorg.conf, not sure if this is why but you have to Option "DRI" "true". And your first display has a default depth of 24, but only has depth 16 configured..

I'm not an expert on multihead displays, so maybe that is valid, just doesn't look right.
Comment 7 David 2007-01-02 12:07:07 UTC
It's not a multihead display it's jus for using 16 or 24 bits,I have just write DefaultDepht 16 and xorg takes the 16bit conf.I have deleted the first configuration of 16 bits 
and delete the Option "DRI" "true" and I have the same problem with beryl :(.

Comment 8 Joshua Jackson (RETIRED) gentoo-dev 2007-01-02 17:01:21 UTC
Well some oddities like Option DRI true twice, and it should be defaulted to 16 bit mode as its your first option, and I believe if you don't define a mode it does 16 bit..don't quote me on that though.I don't believe those will cause the effect you are seeing. 

If you kill the kde window decorator and then start up beryl do you still exhibit the same issue?
Comment 9 David 2007-01-03 05:45:01 UTC
It works!! the problem was the    VideoRam    32768 it's less than that number.
I have commented #    VideoRam    32768 and It works well! 
thank you for everything.