[Ubuntu-x-swat] [Bug 397617] Re: brightness no more working on karmic (KMS)

2009-10-09 Thread Thomas Markus
The new xserver-xorg-video-intel - 2:2.9.0-1ubuntu1 does make xbacklight _report_ the display brightness, but there is no way to actually change it using xbacklight/gnome-brightness-applet. This problem occurs a samsung x360 laptop. -- brightness no more working on karmic (KMS)

[Ubuntu-x-swat] [Bug 441776] [NEW] [karmic] Speed regression

2009-10-03 Thread Markus Thielmann
Public bug reported: Binary package hint: xorg When I installed Karmic, it was *really* fast compared to all previous installations of Ubuntu. With last night updates (from 02. to 03. Oct), the system is back to normal speed. I guess it might be related to either xorg or the kernel, but I'm not

[Ubuntu-x-swat] [Bug 441776] Re: [karmic] Speed regression

2009-10-03 Thread Markus Thielmann
*** This bug is a duplicate of bug 436342 *** https://bugs.launchpad.net/bugs/436342 I was able to fix this bug by enabling NEW_FAIR_SLEEPERS again. echo NEW_FAIR_SLEEPERS /sys/kernel/debug/sched_features ** This bug has been marked a duplicate of bug 436342 Consider disabling

[Ubuntu-x-swat] [Bug 397617] Re: brightness no more working on karmic (KMS)

2009-09-17 Thread Thomas Markus
I have the brightness issues on Karmic with kms as well with a Samsung x360 laptop. /sys/class/backlight/... is populated and looks okay, but there is no visible change in brightness when altering the values. Booting the kernel with 'nomodeset' makes brightness work again. xbacklight says No

[Ubuntu-x-swat] [Bug 355021] Re: Unplugging USB tablet crashes xserver (Jaunty)

2009-08-03 Thread Markus Birth
Just wanted to add that for me (Jaunty, all updates as of today) X/GDM won't start correctly if the tablet is plugged in. Also I got X crashing when trying to start a new console (Terminator) while the tablet is plugged in. And yes, unplugging the tablet also hangs and then restarts X. --

[Ubuntu-x-swat] [Bug 355021] Re: Unplugging USB tablet crashes xserver (Jaunty)

2009-08-03 Thread Markus Birth
Forgot to add: I'm using an Aiptek SlimTablet 600U (Model WCK-C121) and have NOT installed xserver-xorg-input-aiptek but xserver-xorg-input- wacom (the tablet also uses the wacom kernel module). The problem seems to be the same though. So it might have nothing to do with the specific input driver.

[Ubuntu-x-swat] [Bug 363238] Re: very poor Xorg performance on various older graphics HW - XAA solves this

2009-07-17 Thread Markus Birth
I just installed the PPA version again and had a closer look. With and without XAA my Xorg defaults to VESA?!? The latest xserver-xorg seems to not recognize this card anymore. To force it to use the ati driver, add the line Driver ati to the Section Device in your /etc/X11/xorg.conf . --

[Ubuntu-x-swat] [Bug 392531] Re: [R580] Black screen with artefacts after boot

2009-07-15 Thread Markus
I downloaded the newest (14.07.2009) Karmic iso with kernel 2.6.30-8 but I still get a black screen when booting from the CD. After I installed with save graphics mode and removed xorg.conf I again get a black screen with a garbled mouse pointer. After doing a dist-upgrade (kernel 2.6.31-2) I

[Ubuntu-x-swat] [Bug 392531] Re: [R580] Black screen with artefacts after boot

2009-07-15 Thread Markus
** Attachment added: Xorg.0.log_2.6.30-8 http://launchpadlibrarian.net/29039346/Xorg.0.log_2.6.30-8 -- [R580] Black screen with artefacts after boot https://bugs.launchpad.net/bugs/392531 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 392531] Re: [R580] Black screen with artefacts after boot

2009-07-15 Thread Markus
** Attachment added: Xorg.0.log_2.6.31-2 http://launchpadlibrarian.net/29039350/Xorg.0.log_2.6.31-2 -- [R580] Black screen with artefacts after boot https://bugs.launchpad.net/bugs/392531 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 330906] Re: MASTER: GMA-500 lacks driver for 8.10 (poulsbo works only on 8.04)

2009-06-30 Thread Markus Heberling
@metalfan Use the ddcprobe workaround I descibed above. That sould fix this error. I have the following i my xorg.conf and it works fine: Section Monitor Identifier Configured Monitor HorizSync 30-81 VertRefresh 56-85 EndSection -- MASTER: GMA-500 lacks

[Ubuntu-x-swat] [Bug 366757] Re: [HD 3870] Display Preferences causes 100% CPU usage and does not open correctly

2009-06-26 Thread Markus Lindenberg
Bryce, i can confirm that the new fglrx version from the xorg-edgers PPA fixes the problem on Jaunty. (I'm using a RV610 [Radeon HD 2400 XT] on amd64) Thanks for that! Also, shouldn't this bug be merged with #348400 ? -- [HD 3870] Display Preferences causes 100% CPU usage and does not open

[Ubuntu-x-swat] [Bug 348400] Re: Multi-Display not working ATI

2009-06-26 Thread Markus Lindenberg
Bryce, i can confirm that the new fglrx version from the xorg-edgers PPA fixes the problem on Jaunty. (I'm using a RV610 [Radeon HD 2400 XT] on amd64) Thanks for that! -- Multi-Display not working ATI https://bugs.launchpad.net/bugs/348400 You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 392531] [NEW] Black screen with artefacts after boot

2009-06-26 Thread Markus
Public bug reported: Binary package hint: xserver-xorg-video-ati When booting from the install CD, a black screen with artefacts is shown after the startup progress bar (when Gnome or GDM should be displayed). The mouse cursor is movable but garbled. Switching to terminal with Ctrl + Alt + F1

[Ubuntu-x-swat] [Bug 392531] Re: Black screen with artefacts after boot

2009-06-26 Thread Markus
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/28415375/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/28415376/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/28415377/Dependencies.txt **

[Ubuntu-x-swat] [Bug 392531] Re: Black screen with artefacts after boot

2009-06-26 Thread Markus
This bug really seems to have similar symptoms. Adding OptionDRI off to the Device section resulted in a black screen. However the mouse pointer was not corrupted here and changed when moving where the login text field should be displyed. Logging in seemed to work but the screen

[Ubuntu-x-swat] [Bug 330906] Re: MASTER: GMA-500 lacks driver for 8.10 (poulsbo works only on 8.04)

2009-06-25 Thread Markus Heberling
I got it working by adding HorizSync and VertRefresh in the Monitor section in my xorg.conf. You can get the correct values by running sudo ddcprobe after installing the xresprobe package. Look for monitorrange in the output. Seems like the driver is unable to detect that itself and then fails

[Ubuntu-x-swat] [Bug 330906] Re: MASTER: GMA-500 lacks driver for 8.10 (poulsbo works only on 8.04)

2009-06-16 Thread Markus Heberling
I have tried the driver from ppa on a fresh jaunty install on a FIT-PC2. X fails to start. I have attached the xorg log. ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/28003792/Xorg.0.log -- MASTER: GMA-500 lacks driver for 8.10 (poulsbo works only on 8.04)

[Ubuntu-x-swat] [Bug 363238] Re: [r100-rv200] very poor Xorg performance - XAA solves this

2009-05-24 Thread Markus Birth
@Timo Jyrinki: On my Mobility M6 LY (16MB), EXA with both of your optimizations is still slower than XAA. Using EXA, showing the selection list of Gnome Do (down arrow) is presented in 3 hard steps whereas using XAA it is smoothly animated. Same goes for expanding the playlist in VLC player.

[Ubuntu-x-swat] [Bug 363238] Re: [r100-rv200] very poor Xorg performance - XAA solves this

2009-05-16 Thread Markus Birth
Also tried it. With the default screen size of 1024x768 (notebook TFT panel) it's still nothing near the XAA speed. When switching to dual- screen resolution 2304x1024, some options (like ColorTiling) get disabled according to Xorg.log because the card can't handle it at this resolution. And

<    1   2