Bug#567475: xserver-xorg-video-intel: The latest update to testing broke some functionality on 855GM cards
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2010-10-02 14:05, Cyril Brulebois wrote: Hi, LN2 mbfmau...@gmail.com (29/01/2010): If you need any further information/testing please feel free to contact me. please could you report with 2.12 from sid or 2.13 from experimental with sid's kernel? Details about versions can be read in: http://ikibiki.org/blog/2010/10/02/October-X-update/ Mraw, KiBi. Hi, I came around testing the xserver-xorg-video-intel 2.12 and 2.13 versions with the unstable kernel as requested. Both versions of the package start the X-server (that is already an improvement over the current linux-image-2.6.32-5-686/xserver-xorg-video-intel combination in testing) and the issues initially reported in the bug are gone, i.e. shutdown, reboot, hibernate, logout all seem to work. The video acceleration seems to work, too. I have however had some issues with the xserver-xorg-video-intel 2.12 that don't occur with the 2.13 version. Using any application that tries to switch the screen resolution (like running dosbox or wine with a game with non-native resolution in fullscreen mode) kills X which is then promptly restarted and asks for a user log-in. The easiest way to reproduce this bug is to start dosbox and press Alt+Return for fullscreen mode which seems to trigger this bug 100% of the time. The 2.12 version apparently does not like 3D-Applications either, since Tux Racer crashed the X-server to in a very reproducible fashion. The 2.13 version doesn't have quite the same problems. It handles screen resolution changes fine, and start games like Tux Racer and Scorch3D, nevertheless I had a few crashes of the X-server with 2.13, too. This bug was a little harder to trigger, but opening enough applications including 3D ones usually did the trick and killed X. After the bug was triggered once though, trying to start a 3D application always killed X and trying to play a movie with mplayer showed a blue window instead of the movie. So hope this helps. If you want me to test something else, let me know. LN2 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyqGM0ACgkQ5/YQEZwskCAHPACfVwK5cN4ye+42hl29y2AjNRyr MqoAn12sHfdNhzb+AI/z4w/oRmsrAYGa =5PcQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567475: xserver-xorg-video-intel: The latest update to testing broke some functionality on 855GM cards
Hi Michael. On 10/04/2010 08:11 PM, Michael Maurer wrote: Both versions of the package start the X-server (that is already an improvement over the current linux-image-2.6.32-5-686/xserver-xorg-video-intel combination in testing) and the issues initially reported in the bug are gone, i.e. shutdown, reboot, hibernate, logout all seem to work. The video acceleration seems to work, too. So, since the original problem were solved, maybe it would be more appropriate to close this bug and start another one. I have however had some issues with the xserver-xorg-video-intel 2.12 that don't occur with the 2.13 version. I have an i855 too and for me 2.13 was a big improvement, particularly on the stability front. I'm not a gamer and i don't use suspend/hibernate, but i use this computer everyday for many hour and i haven't seen a crash or an hang since i've installed it. Both with kernel 2.6.32 and 2.6.35. And on the speed front i haven't noted performance regression (even if seems there are). The 2.13 version doesn't have quite the same problems. It handles screen resolution changes fine, and start games like Tux Racer and Scorch3D, nevertheless I had a few crashes of the X-server with 2.13, too. This bug was a little harder to trigger, but opening enough applications including 3D ones usually did the trick and killed X. After the bug was triggered once though, trying to start a 3D application always killed X and trying to play a movie with mplayer showed a blue window instead of the movie. Good analisys. Me too now can now put Youtube video fullscreen without make X crash. Would be perfect if we could find a set of reproducible step to induce one of this bug, so that we could file a precise bug report. If you find it, let me know, so we can compare the results. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567475: xserver-xorg-video-intel: The latest update to testing broke some functionality on 855GM cards
On Mon, Oct 4, 2010 at 20:11:25 +0200, Michael Maurer wrote: I have however had some issues with the xserver-xorg-video-intel 2.12 that don't occur with the 2.13 version. Using any application that tries to switch the screen resolution (like running dosbox or wine with a game with non-native resolution in fullscreen mode) kills X which is then promptly restarted and asks for a user log-in. The easiest way to reproduce this bug is to start dosbox and press Alt+Return for fullscreen mode which seems to trigger this bug 100% of the time. That should be fixed with unstable's xserver-xorg-core package (which should move to testing very soon). The 2.12 version apparently does not like 3D-Applications either, since Tux Racer crashed the X-server to in a very reproducible fashion. Could you file a separate bug for that, including the X log from the crash? Thanks, Julien signature.asc Description: Digital signature
Bug#567475: xserver-xorg-video-intel: The latest update to testing broke some functionality on 855GM cards
Hi, LN2 mbfmau...@gmail.com (29/01/2010): If you need any further information/testing please feel free to contact me. please could you report with 2.12 from sid or 2.13 from experimental with sid's kernel? Details about versions can be read in: http://ikibiki.org/blog/2010/10/02/October-X-update/ Mraw, KiBi. signature.asc Description: Digital signature
Bug#567475: xserver-xorg-video-intel: The latest update to testing broke some functionality on 855GM cards
Package: xserver-xorg-video-intel Version: 2:2.9.1-2 Severity: important Since the latest update of xserver-xorg-video-intel to debian testing, I have experienced a number of problems. Shutdown, Reboot, Hibernate, Logout cause the system to freeze with a blank screen. The Alt+SysRq key combination does not work (I have not tried ssh yet). Trying to switch to a text terminal with Ctrl+Alt+(F1 ... F6) causes the system to freeze. The video acceleration with the xv driver seems to have stopped working, e.g. mplayer -vo xv does not work. If you need any further information/testing please feel free to contact me. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Jan 9 02:05 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1710344 Jan 21 00:01 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) /etc/X11/xorg.conf does not exist. Xorg X server log files on system: -rw-r--r-- 1 root root 30609 Jan 29 11:33 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.4 Release Date: 2010-01-08 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-trunk-686 i686 Debian Current Operating System: Linux wichtel 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686 root=UUID=9b23d674-90d8-44e7-95a2-eba5dc7bd600 ro noquiet Build Date: 20 January 2010 10:52:55PM xorg-server 2:1.7.4-2 (bgog...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Jan 29 11:33:23 2010 (II) Loader magic: 0x81e7680 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:0:2:0) 8086:3582:1028:0164 Intel Corporation 82852/855GM Integrated Graphics Device rev 2, Mem @ 0xf000/134217728, 0xfaf8/524288, I/O @ 0xc000/8 (--) PCI: (0:0:2:1) 8086:3582:1028:0164 Intel Corporation 82852/855GM Integrated Graphics Device rev 2, Mem @ 0xe800/134217728, 0xfaf0/524288 (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section Device Identifier Builtin Default intel Device 0 Driver intel EndSection Section Screen Identifier Builtin Default intel Screen 0 Device Builtin Default intel Device 0 EndSection Section Device Identifier Builtin Default vesa Device 0 Driver vesa EndSection Section Screen Identifier Builtin Default vesa Screen 0 Device Builtin Default vesa Device 0 EndSection Section Device Identifier Builtin Default fbdev Device 0 Driver fbdev EndSection Section Screen Identifier Builtin Default fbdev Screen 0 Device Builtin Default fbdev Device 0 EndSection Section ServerLayout Identifier Builtin Default Layout Screen Builtin Default intel Screen 0 Screen Builtin Default vesa Screen 0 Screen Builtin Default fbdev Screen 0 EndSection (==) --- End of built-in configuration --- (==) ServerLayout Builtin Default Layout (**) |--Screen Builtin Default intel Screen 0 (0) (**) | |--Monitor default monitor (**) | |--Device Builtin Default intel Device 0 (==) No monitor specified for screen Builtin Default intel Screen 0. Using a default monitor configuration. (**) |--Screen Builtin Default vesa Screen 0 (1) (**) | |--Monitor default monitor (**) | |--Device Builtin Default vesa Device 0 (==) No monitor specified for screen Builtin Default vesa Screen 0. Using a default monitor configuration. (**) |--Screen Builtin Default fbdev Screen 0 (2) (**) | |--Monitor default monitor (**) | |--Device Builtin Default fbdev Device 0 (==) No monitor specified for screen Builtin Default fbdev Screen 0. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist.