[Bug 76327] Re: Edgy's DRI performance halved
** Attachment added: xorg.conf http://librarian.launchpad.net/5445378/xorg.conf -- Edgy's DRI performance halved https://launchpad.net/bugs/76327 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76327] Re: Edgy's DRI performance halved
** Attachment added: Xorg.0.log http://librarian.launchpad.net/5445379/Xorg.0.log -- Edgy's DRI performance halved https://launchpad.net/bugs/76327 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76327] Re: Edgy's DRI performance halved
** Attachment added: dmesg log http://librarian.launchpad.net/5445382/dmesg.log -- Edgy's DRI performance halved https://launchpad.net/bugs/76327 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74751] Multiple new issues with 855GM, Dapper - Edgy
Public bug reported: Binary package hint: xserver-xorg-video-i810 System: Dell Inspiron 510m, 256mb RAM, Intel 82855GM graphics chipset, Edgy final all updates I am having multiple issues with my graphics card since (clean) upgrading from Dapper to Edgy. Although these could be split into separate bugs, it's unclear as to whether they are the combined symptoms of one bug or not, so I'm keeping them together for now. Here are the issues with my system since upgrading to Edgy: 1. When logging in or restarting X, garbage is displayed on-screen for a second before the server starts, sometimes showing evidence of previous graphical activity (e.g. a distorted image from a movie that was previously playing). Additionally, restarting X too many times will result in a non-starting X server (I'll reproduce that in logs if requested). 2. In Edgy, 3D performance has worsened. I know glxgears is not a benchmark, but on the same system in [EMAIL PROTECTED], Dapper achieves ~900fps, whilst Edgy gets ~530fps by default (16bit has a similar performance gap). If I disable powernowd in Edgy, I can improve the score to ~670fps, but Dapper exhibits equal fps rates when powernowd (CPU scaling, supported by my processor) is enabled or disabled. Performance is noticeably sluggish in games, running compiz/beryl, etc. Enabling or disabling Composite/AIGLX seems to make no significant difference, and I will do more thorough benchmarks logging if necessary. Note that 2D performance is unchanged. 3. Specifying Option SWCursor true in xorg.conf seems to totally break DRI. I'm not sure if this is normal behaviour. 4. While in [EMAIL PROTECTED] mode, switching to a VT, resuming from suspend, or even closing and reopening the lid will result in an invisible cursor when X re-initializes. The cursor is still functioning - buttons become highlighted as the cursor (presumably) passes over them, and it is possible to click, drag and so on. This problem does not seem to occur in [EMAIL PROTECTED] mode. 5. With Edgy's i810 driver, I received several warnings in my Xorg.0.log: (WW) I810(0): xf86AllocateGARTMemory: allocation of 8 pages failed This line repeated several times, with the page count increasing each time. I'll produce a log of this if required, but it is identical to this user's log: http://www.ubuntuforums.org/showpost.php?p=1682450postcount=1 Regarding bug #45: I have compiledinstalled the latest drm and xf86 -video-intel from git (using checkinstall for a relatively clean upgrade). This has solved bug #45 (the cursor restores correctly, and Xorg.0.log no longer warns about allocation failures), but not the others. I have also attempted to compileinstall Mesa from cvs, but performance was unchanged. (I compiled xf86-video-intel from the master branch; modesetting did not properly illuminate the LCD screen when X started) Any assistance would be much appreciated. Below is my /proc/mtrr output, I will shortly post my xorg.conf, Xorg.0.log and dmesg output from my system running Edgy with the latest drm xf86-video-i810 from git installed (not exhibiting bug #45). Let me know what other logs would be useful. /proc/mtrr: reg00: base=0x ( 0MB), size= 256MB: write-back, count=1 reg01: base=0x0ff0 ( 255MB), size= 1MB: uncachable, count=1 reg02: base=0xfeda (4077MB), size= 128KB: write-through, count=1 reg03: base=0xf000 (3840MB), size= 128MB: write-combining, count=1 ** Affects: xserver-xorg-video-i810 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Multiple new issues with 855GM, Dapper - Edgy https://launchpad.net/bugs/74751 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74751] Re: Multiple new issues with 855GM, Dapper - Edgy
** Attachment added: xorg.conf (Edgy, using 1.7.2git, drm 2.0.3git) http://librarian.launchpad.net/5295568/xorg.conf -- Multiple new issues with 855GM, Dapper - Edgy https://launchpad.net/bugs/74751 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74751] Re: Multiple new issues with 855GM, Dapper - Edgy
** Attachment added: Xorg.0.log (Edgy, using 1.7.2git, drm 2.0.3git) http://librarian.launchpad.net/5295570/Xorg.0.log -- Multiple new issues with 855GM, Dapper - Edgy https://launchpad.net/bugs/74751 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74751] Re: Multiple new issues with 855GM, Dapper - Edgy
** Attachment added: dmesg output (Edgy, using 1.7.2git, drm 2.0.3git) http://librarian.launchpad.net/5295571/dmesg.log -- Multiple new issues with 855GM, Dapper - Edgy https://launchpad.net/bugs/74751 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74751] Re: Multiple new issues with 855GM, Dapper - Edgy
Just to correct the typo in the above attachments, I meant to write drm 2.3.0git. I've also neglected to mention that under all circumstances, I verified that direct rendering was enabled via glxinfo, so it's not a simple configuration issue. Additionally, the bugs are still evident with the stock version of xorg.conf that Edgy generates on first install (except #4, until DefaultDepth is changed to 24). -- Multiple new issues with 855GM, Dapper - Edgy https://launchpad.net/bugs/74751 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68485] Re: Intel 855GM DRI initialization error
** Attachment added: dmesg output http://librarian.launchpad.net/4937596/dmesg.log -- Intel 855GM DRI initialization error https://launchpad.net/bugs/68485 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68485] Intel 855GM DRI initialization error
Public bug reported: System Specs: Dell Inspiron 510m w/256mb ram, BIOS Revision A11, Intel 855GM chipset, fresh Edgy Final install. Using driver i810 in 16 bit mode results in functional DRI (reported in Xorg.0.log / glxinfo, visible in glxgears), but in 24 bit mode it will not work at all. I tried setting the VideoRAM parameter to 65536, to no avail. I will attach the contents of dmesg, xorg.conf and Xorg.0.log while attempting to set the resolution to 24 bit - please let me know if more information is needed. *Note: using xserver-xorg-video-intel xorg.conf's 'Driver intel' allows DRI to function properly in 24 bit, but it seems slow unusable on this laptop due to bad flickering - despite running at 60Hz - the same as the i810 driver (which never has this problem). ** Affects: xserver-xorg-video-i810 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Intel 855GM DRI initialization error https://launchpad.net/bugs/68485 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68485] Re: Intel 855GM DRI initialization error
Sorry, it seems that after a reboot DRI is now functioning properly. I have two desktop systems with an 865G and 945G chipset and never encountered this problem. I'll post my xorg.conf and Xorg.0.log as-is (i.e., with DRI enabled), just in case someone wants to see if anything odd is happening. Otherwise, close the bug I'm sorry for the hassle ;) ** Attachment added: xorg.conf http://librarian.launchpad.net/4937651/xorg.conf -- Intel 855GM DRI initialization error https://launchpad.net/bugs/68485 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68485] Re: Intel 855GM DRI initialization error
** Attachment added: Xorg.0.log http://librarian.launchpad.net/4937652/Xorg.0.log -- Intel 855GM DRI initialization error https://launchpad.net/bugs/68485 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32963] Re: Xv movies on 810/i945 gives horrible color, Gamma
** Attachment added: xvattr output immediately following playback of movie in totem(-gstreamer) http://librarian.launchpad.net/4532753/xvattr_gstreamer.log ** Also affects: totem (upstream) Importance: Undecided Status: Unconfirmed -- Xv movies on 810/i945 gives horrible color, Gamma https://launchpad.net/bugs/32963 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32963] Re: Xv movies on 810/i945 gives horrible color, Gamma
Hi, This is a bug with a combination of the xserver-xorg-i810 driver and totem (-xine and -gstreamer backends). I'll attach two logs to illustrate: 1. xvattr_boot.log - xvattr output after a fresh reboot 2. xvattr_gstreamer.log - xvattr output after playing a movie in totem (-gstreamer). Note that using the totem-xine causes the same difference as in this log. A fix is to run xvattr -a XV_COLORKEY -v 66046;xvattr -a XV_CONTRAST -v 64 *during* movie playback in totem to restore the proper defaults and give a good quality picture. Setting it beforehand won't work, and running totem again will reset the values back to bad non-default values. I have two separate systems running Edgy (although I've had this same problem with Dapper too), both with Intel chipsets (865G and 945G). On the latter system I use DVI input, but I tested analog and it's the same, so it's a software issue. I installed an NVIDIA card in my older system, and never experience such a bug, nor have I seen any problems with my old Inspiron 8000 laptop with a Mobility M4 (ati/r128) chipset. Why am I sure it's totem's fault? Do a fresh reboot and immediately play a movie in vlc (using Xvideo output) or mplayer -vo xv and you'll see that the xvattr variables are untouched - and picture quality is fine; only totem seems to change these values once started and thus create problems with picture quality (until proper defaults are re-set). ** Attachment added: xvattr output immediately following reboot http://librarian.launchpad.net/4532752/xvattr_boot.log -- Xv movies on 810/i945 gives horrible color, Gamma https://launchpad.net/bugs/32963 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32963] Re: Xv movies on 810/i945 gives horrible color, Gamma
A little followup: using totem's preferences to manually set the contrast slider to 64 (using xvattr -a XV_CONTRAST in a terminal to monitor exactly when it reaches 64), totem saves and remembers the setting each time it's subsequently run. So it may be a problem with totem's internal contrast handling that's to blame. So a fix is to manually set the contrast slider to 64, but there's still a bug somewhere that should be fixed to avoid this headache for others. -- Xv movies on 810/i945 gives horrible color, Gamma https://launchpad.net/bugs/32963 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
