Since the last two kernel updates (2.6.31.12 and 2.6.31.8) I have a problem with KDE4 Desktop Effects, before that it worked OK.
This started when I upgraded the kernel from 2.6.31.5 to 2.6.31.8. I wanted to upgrade KDE from 4.3 to 4.4 beta 2 or RC1 (I don’t remember the exact version), but the kernel update was also selected when I triggered the “update of all packages if newer version is available”.
If I remember correctly I also had to reinstall the fglrx driver because of the kernel upgrade (X server didn’t start).
When I logged in the KDE session I noticed that the desktop effects were turned off, so I tried to enable them and noticed that the check box was grayed out and it said: “Compositing is not supported on your system.”. As far as I have seen on the Internet there is usually some additional description why the desktop effects are not supported, but in my case this was all it said.
Since I simultaneously upgraded KDE and kernel I am not sure which one caused the problem. Currently I have the latest KDE 4.4, the latest kernel and also the latest fglrx driver.
What could be the solution to this problem?
I am not new to Linux so you don’t have to simplify solving the problem for me
That file should tell everything you need to know. My crystal ball run out of batteries today, could you please post what you find relevant from that log ?
I had that as well when I (inadvertently) upgraded from 2.6.31.8 to 2.6.31.12, because I also used “update of all packages if newer version is available”.
Same thing here, after a reboot my compositing was disabled.
You need to rebuild the graphics driver after a kernel upgrade.
Open a konsole window, become root with su, and enter the following to install the required stuff (requires an internet connection):
zypper in kernel-source linux-kernel-headers kernel-syms module-init-tools make gcc
Then, enter init 3 to get to a text-only interface. There, enter the command to rebuild fglrx for the new kernel:
fglrx-kernel-build.sh
Reboot by entering init 6.
This fixed things for me, and I had proper compositing again.
I ran the fglrx-kernel-build.sh but it still doesn’t work.
I should probably mention this earlier, I think that the driver 3D part of the driver works, at least this is what the glxinfo and fglrxinfo command tell me and also the glxgears and fgl_glxgears test work correctly.
@nmarques78: I’ll try to recharge the batteries for your crystal ball
There is no errors (EE) in the log, but there are some warnings (WW) that mention fglrx:
(WW) Falling back to old probe method for fglrx
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): could not detect X server version (query_status=-1)
(WW) fglrx(0): Option “VideoOverlay” is not used
(WW) fglrx(0): Option “FSAAEnable” is not used
(WW) fglrx(0): Option “FSAAScale” is not used
(WW) fglrx(0): Option “CalcAlgorithm” is not used
(WW) fglrx(0): Option “PreferredMode” is not used
Here is everything from /var/log/Xorg.0.log file concerning fglrx (the whole log file is too big for the forum):
(II) Loading sub module “fglrxdrm”
(II) LoadModule: “fglrxdrm”
(II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) Module fglrxdrm: vendor=“FireGL - ATI Technologies Inc.”
(II) LoadModule: “fglrx”
(II) Loading /usr/lib/xorg/modules//drivers/fglrx_drv.so
(II) Module fglrx: vendor=“FireGL - ATI Technologies Inc.”
(II) Loading sub module “fglrxdrm”
(II) LoadModule: “fglrxdrm”
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(WW) Falling back to old probe method for fglrx
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
(II) fglrx(0): pEnt->device->identifier=0x822c950
(II) fglrx(0): === [atiddxPreInit] === begin
(II) fglrx(0): PCI bus 1 card 0 func 0
() fglrx(0): Depth 24, (–) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
() fglrx(0): Option “Capabilities” “0x00000000”
() fglrx(0): Option “OpenGLOverlay” “off”
() fglrx(0): Option “DPMS”
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB
() fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(II) Loading sub module “fglrxdrm”
(II) LoadModule: “fglrxdrm”
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(–) fglrx(0): Chipset: “ATI Radeon HD 4300/4500 Series” (Chipset = 0x954f)
(–) fglrx(0): (PciSubVendor = 0x1787, PciSubDevice = 0x2271)
(–) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
(–) fglrx(0): Linear framebuffer (phys) at 0xe0000000
(–) fglrx(0): MMIO registers at 0xfeae0000
(–) fglrx(0): I/O port at 0x0000d000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) fglrx(0): AC Adapter is used
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 3.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
(II) fglrx(0): VESA VBE OEM Software Rev: 11.12
(II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
(II) fglrx(0): VESA VBE OEM Product: RV710
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
(–) fglrx(0): Video RAM: 524288 kByte, Type: DDR2
(II) fglrx(0): PCIE card detected
(–) fglrx(0): Using per-process page tables (PPPT) as GART.
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(II) fglrx(0): Using adapter: 1:0.0.
(II) fglrx(0): [FB] MC range(MCFBBase = 0xf00000000, MCFBSize = 0x20000000)
(II) fglrx(0): Interrupt handler installed at IRQ 28.
(II) fglrx(0): IRQ 28 Enabled.
(II) fglrx(0): RandR 1.2 support is enabled!
(II) fglrx(0): RandR 1.2 rotation support is enabled!
(==) fglrx(0): Center Mode is disabled
(II) fglrx(0): Finished Initialize PPLIB!
(II) fglrx(0): Display: ConnectedDisplayTypes=0x00000400, disabled=0x00000000
(II) fglrx(0): Connected Display1: DFP 5 [dfp5]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: SAM Model: 302 Serial#: 1346712112
(II) fglrx(0): Year: 2007 Week: 40
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Digital Display Input
(II) fglrx(0): Max Image Size [cm]: horiz.: 46 vert.: 30
(II) fglrx(0): Gamma: 2.20
(II) fglrx(0): DPMS capabilities: Off
(II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.651 redY: 0.333 greenX: 0.277 greenY: 0.614
(II) fglrx(0): blueX: 0.145 blueY: 0.082 whiteX: 0.313 whiteY: 0.329
(II) fglrx(0): Supported established timings:
(II) fglrx(0): 720x400@70Hz
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 640x480@67Hz
(II) fglrx(0): 640x480@72Hz
(II) fglrx(0): 640x480@75Hz
(II) fglrx(0): 800x600@56Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 800x600@72Hz
(II) fglrx(0): 800x600@75Hz
(II) fglrx(0): 832x624@75Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): 1024x768@70Hz
(II) fglrx(0): 1024x768@75Hz
(II) fglrx(0): 1280x1024@75Hz
(II) fglrx(0): 1152x870@75Hz
(II) fglrx(0): Manufacturer’s mask: 0
(II) fglrx(0): Supported standard timings:
(II) fglrx(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
(II) fglrx(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) fglrx(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
(II) fglrx(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
(II) fglrx(0): Supported detailed timing:
(II) fglrx(0): clock: 119.0 MHz Image Size: 459 x 296 mm
(II) fglrx(0): h_active: 1680 h_sync: 1728 h_sync_end 1760 h_blank_end 1840 h_border: 0
(II) fglrx(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1080 v_border: 0
(II) fglrx(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
(II) fglrx(0): Monitor name: SyncMaster
(II) fglrx(0): Serial No: HS3PA00507
(II) fglrx(0): EDID (in hex):
(II) fglrx(0): 00ffffffffffff004c2d020330324550
(II) fglrx(0): 28110103802e1e782ad105a655479d25
(II) fglrx(0): 155054bfef80b30081808140714f0101
(II) fglrx(0): 0101010101017c2e90a0601a1e403020
(II) fglrx(0): 3600cb281100001a000000fd00384b1e
(II) fglrx(0): 510e000a202020202020000000fc0053
(II) fglrx(0): 796e634d61737465720a2020000000ff
(II) fglrx(0): 00485333504130303530370a202000d8
(II) fglrx(0): End of Display1 EDID data --------------------
(II) fglrx(0): Output DFP5 using monitor section Monitor[0]
() fglrx(0): Option “PreferredMode” “1680x1050”
(II) fglrx(0): Output CRT1 has no monitor section
(II) fglrx(0): Output CRT2 has no monitor section
(II) fglrx(0): Output TV has no monitor section
(II) fglrx(0): Output COMPONENT_VIDEO has no monitor section
(II) fglrx(0): EDID vendor “SAM”, prod id 770
(II) fglrx(0): Using hsync ranges from config file
(II) fglrx(0): Using vrefresh ranges from config file
(II) fglrx(0): Printing DDC gathered Modelines:
(II) fglrx(0): Output DFP5 connected
(II) fglrx(0): Output CRT1 disconnected
(II) fglrx(0): Output CRT2 disconnected
(II) fglrx(0): Output TV disconnected
(II) fglrx(0): Output COMPONENT_VIDEO disconnected
(II) fglrx(0): Using user preference for initial modes
(II) fglrx(0): Output DFP5 using initial mode 1680x1050
(II) fglrx(0): Display dimensions: (460, 300) mm
(II) fglrx(0): DPI set to (92, 88)
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): QBS disabled
(==) fglrx(0): PseudoColor visuals disabled
(==) fglrx(0): NoAccel = NO
(==) fglrx(0): NoDRI = NO
() fglrx(0): Capabilities: 0x00000000
() fglrx(0): CapabilitiesEx: 0x00000000
(==) fglrx(0): OpenGL ClientDriverName: “fglrx_dri.so”
(==) fglrx(0): UseFastTLS=0
(==) fglrx(0): BlockSignalsOnLock=1
(II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906
(WW) fglrx(0): could not detect X server version (query_status=-1)
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing swlDriScreenInit
(II) fglrx(0): swlDriScreenInit for fglrx driver
(II) fglrx(0): [uki] DRM interface version 1.0
(II) fglrx(0): [uki] created “fglrx” driver at busid “PCI:1:0:0”
(II) fglrx(0): [uki] added 8192 byte SAREA at 0x2000
(II) fglrx(0): [uki] mapped SAREA 0x2000 to 0xb7180000
(II) fglrx(0): [uki] framebuffer handle = 0x3000
(II) fglrx(0): [uki] added 1 reserved context for kernel
(II) fglrx(0): swlDriScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.69.4
(II) fglrx(0): Date: Dec 11 2009
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.31.12-0.1-default
(II) fglrx(0): Build-Kernel MODVERSIONS: no
(II) fglrx(0): Build-Kernel SMP: yes
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [uki] register handle = 0x00004000
(II) fglrx(0): Display width adjusted to to 1792 due to alignment constraints
(II) fglrx(0): DRI initialization successfull!
(II) fglrx(0): FBADPhys: 0xf00000000 FBMappedSize: 0x010a0000
(II) fglrx(0): FBMM initialized for area (0,0)-(1792,2432)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1792,1792) (front color buffer - assumption)
(II) fglrx(0): Largest offscreen area available: 1792 x 640
(==) fglrx(0): Backing store disabled
(II) Loading extension FGLRXEXTENSION
() fglrx(0): DPMS enabled
() fglrx(0): Textured Video is enabled.
(II) fglrx(0): GLESX enableFlags = 94
(*) fglrx(0): Option “XaaNoOffscreenPixmaps” “true”
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
(II) fglrx(0): GLESX is enabled
(II) fglrx(0): UVD2 feature is available
(II) fglrx(0): Enable composite support successfully
(WW) fglrx(0): Option “VideoOverlay” is not used
(WW) fglrx(0): Option “FSAAEnable” is not used
(WW) fglrx(0): Option “FSAAScale” is not used
(WW) fglrx(0): Option “CalcAlgorithm” is not used
(WW) fglrx(0): Option “PreferredMode” is not used
(II) fglrx(0): X context handle = 0x1
(II) fglrx(0): [DRI] installation complete
(==) fglrx(0): Silken mouse enabled
(==) fglrx(0): Using HW cursor of display infrastructure!
(==) fglrx(0): Using software cursor
(II) fglrx(0): Disabling in-server RandR and enabling in-driver RandR 1.2.
(II) AIGLX: Loaded and initialized /usr/X11R6/lib/modules/dri/fglrx_dri.so
(II) fglrx(0): Enable the clock gating!
(II) fglrx(0): Setting screen physical size to 459 x 296
(II) fglrx(0): Restoring Recent Mode via PCS is not supported in RANDR 1.2 capable environments
(II) fglrx(0): EDID vendor “SAM”, prod id 770
(II) fglrx(0): Using hsync ranges from config file
(II) fglrx(0): Using vrefresh ranges from config file
(II) fglrx(0): Printing DDC gathered Modelines:
(II) fglrx(0): EDID vendor “SAM”, prod id 770
(II) fglrx(0): Using hsync ranges from config file
(II) fglrx(0): Using vrefresh ranges from config file
(II) fglrx(0): Printing DDC gathered Modelines:
(II) fglrx(0): EDID vendor “SAM”, prod id 770
(II) fglrx(0): Using hsync ranges from config file
(II) fglrx(0): Using vrefresh ranges from config file
(II) fglrx(0): Printing DDC gathered Modelines:
I just found out it might be a KDE problem after all.
If I manually enable compositing with command “kwriteconfig --file kwinrc --group Compositing --key Enabled --type bool true” it works (I had to switch from OpenGL to XRender and back to OpenGL for it to work).
I will open a bug report with KDE for resolving the problem, since it appears it is a problem with detecting the capabilities of the graphics card in kwin…
Hi Djuro
I’ve been having the same issue since the last kernel update, a few weeks ago. I also think I may have seen the bug you reported @KDE. Basically, my setup is the same as yours, and the compositing works ONLY when manually started as you described.
Still, the Desktop effects says the same, “Compositing is not supported on your system”, although the effects work fine. The problem is, I have no access to the effects (none are showing in the Effects tab), which is understandable since KDE thinks they aren’t supported. This is also fine, since the system remembered my effect settings from before the update…
To workaround the issue (of having to manually start compositing), I modified my /etc/bash.bashrc, by adding the command to the end of it. So now, upon restart, the compositing is started “automatically”.
I would appreciate it if you posted a follow up on the situation, if you ever get any resolution from the KDE team. Thanks for all the info you provided!
