Bug#944298: mesa: CVE-2019-5068
Hi, I backported and tried the patch for Debian LTS. The patch is trivial (basically s/0777/0600/). However, I could not find a way to reproduce the initial issue. The only way to get those 0777 shm in `ipcs` is to run Kali specifically in virt-manager or VirtualBox. I could not reproduce this issue with Debian. Any ideas? (Also, upstream patch was reviewed/approved at last:) https://lists.freedesktop.org/pipermail/mesa-dev/2019-November/223771.html Cheers! Sylvain
Bug#640854: libgl1-mesa-dri: Wrong variable used in shader with uses of multiple varying and gl_FrontFacing
Hi, On Thu, Sep 08, 2011 at 09:03:11AM +0200, Cyril Brulebois wrote: > Sylvain Beucler (08/09/2011): > > Package: libgl1-mesa-dri > > Version: 7.10.3-4 > > Severity: important > > any chance you could check what happens with 7.11? Wow, I was only 1-apt-day away from a fix! ;) It works correctly with that version, thanks. PS: give my regards to Duck when you see him :) -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110908072936.ga32...@perso.beuc.net
Bug#500495: Error "fire_buffer: DRM_VIA_PCICMD returned -22" on startup
On Tue, Jun 29, 2010 at 03:42:30PM +0100, Julien Cristau wrote: > On Tue, Oct 21, 2008 at 20:23:21 +0200, Sylvain Beucler wrote: > > > Hi, > > > > I confirm that this is a S3 UniChrome: > > 00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host > > Bridge > > 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 > > UniChrome] Integrated Video (rev 01) > > > > So apparently I do have 3D support on this box... which I probably > > didn't have in Etch :) > > > > > > FYI, I retried with Driver "openchrome" : > > > > $ titanion > > do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. > > Try adjusting the vblank_mode configuration parameter. > > Load bgm: ttn1.ogg > > Load bgm: ttn3.ogg > > Load bgm: ttn2.ogg > > Load SE: shot.wav > > Load SE: explosion1.wav > > Load SE: explosion2.wav > > Load SE: explosion3.wav > > Load SE: tractor.wav > > Load SE: flying_down.wav > > Load SE: player_explosion.wav > > Load SE: flick.wav > > Load SE: extend.wav > > fire_buffer: DRM_VIA_CMDBUFFER returned -22 > > > > > > The error is less verbose, and is slightly different (previous was: > > > > fire_buffer: DRM_VIA_PCICMD returned -22 > > ) > > > Does this still happen with mesa 7.7 or 7.8 and a recent kernel? Hi, Thanks for getting back to me. Unfortunately I don't have time to spend on this oldish bug report at the moment, especially since I use a modified hardware configuration. Considering that most 3D apps just crash when the 3D card doesn't meet all their requirements, and since this S3 card is very basic, I guess we can close the bug as wontfix. -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100629145957.ga29...@perso.beuc.net
Bug#583653: xserver-xorg-video-radeon: 15x-slower performance regression in KMS mode for 2D operations
On Sat, May 29, 2010 at 04:21:46PM +0200, Michel Dänzer wrote: > On Sam, 2010-05-29 at 15:02 +0200, Sylvain Beucler wrote: > > On Sat, May 29, 2010 at 01:05:36PM +0200, Michel Dänzer wrote: > > > On Sam, 2010-05-29 at 10:21 +0200, Sylvain Beucler wrote: > > > > > > > > The attached simple test runs at 17FPS in KMS mode on my computer, > > > > against 300FPS in non-KMS mode. > > > > > > Forgot to mention: sysprof or oprofile profiles of slow and fast runs > > > might be interesting, at least if the CPU is pegged during the runs. > > > > Here are 2 sysprof runs: > > - UMS / fast: > > - kernel 11.25% > > - X 77.20% > > - KMS / slow: > > - kernel 90.28% > > - X 5.79% > > Unfortunately, there's no information about where in the kernel the > cycles are burnt. This information should be available with sysprof > 1.1.x and a kernel with the performance counter/event framework. Quite a nice tool: __libc_start_main 0,00% 93,67% _start 0,02% 87,66% In file /usr/bin/Xorg 0,13% 87,64% In file /usr/lib/xorg/modules/libexa.so 0,04% 86,60% In file /usr/lib/xorg/modules/drivers/radeon_drv.so0,08% 86,48% radeon_bo_open 0,00% 79,87% In file /usr/lib/libdrm_radeon.so.1.0.00,00% 79,87% drmCommandWriteRead 0,00% 79,86% __kernel_vsyscall 0,00% 79,86% - - kernel - - 0,00% 79,86% on_each_cpu 36,81% 36,81% __purge_vmap_area_lazy20,31% 20,31% flush_all_zero_pkmaps 7,84% 7,84% vm_unmap_aliases 1,65% 1,65% What do you think that means? > Anyway, this probably means it's an issue in the kernel, not the X > driver. May be solved already in newer kernels, there have been some AGP > performance improvements which I'm not sure have made it into Debian's > 2.6.32 DRM backport. -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100529153352.ga2...@perso.beuc.net
Bug#583653: xserver-xorg-video-radeon: 15x-slower performance regression in KMS mode for 2D operations
Somebody suggested I run gtkperf. Results are much closer. UMS: GtkPerf 0.40 - Starting testing: Sat May 29 14:44:42 2010 GtkEntry - time: 0,17 GtkComboBox - time: 1,71 GtkComboBoxEntry - time: 1,20 GtkSpinButton - time: 0,28 GtkProgressBar - time: 0,17 GtkToggleButton - time: 0,37 GtkCheckButton - time: 0,24 GtkRadioButton - time: 0,44 GtkTextView - Add text - time: 0,78 GtkTextView - Scroll - time: 0,46 GtkDrawingArea - Lines - time: 2,34 GtkDrawingArea - Circles - time: 2,09 GtkDrawingArea - Text - time: 1,95 GtkDrawingArea - Pixbufs - time: 0,26 --- Total time: 12,47 KMS: GtkPerf 0.40 - Starting testing: Sat May 29 15:03:03 2010 GtkEntry - time: 0,19 GtkComboBox - time: 1,79 GtkComboBoxEntry - time: 1,20 GtkSpinButton - time: 0,30 GtkProgressBar - time: 0,19 GtkToggleButton - time: 0,38 GtkCheckButton - time: 0,26 GtkRadioButton - time: 0,48 GtkTextView - Add text - time: 0,81 GtkTextView - Scroll - time: 0,47 GtkDrawingArea - Lines - time: 2,62 GtkDrawingArea - Circles - time: 3,21 GtkDrawingArea - Text - time: 2,51 GtkDrawingArea - Pixbufs - time: 0,44 --- Total time: 14,86 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100529130736.gb2...@perso.beuc.net
Bug#583653: xserver-xorg-video-radeon: 15x-slower performance regression in KMS mode for 2D operations
Hi, On Sat, May 29, 2010 at 12:55:45PM +0200, Michel Dänzer wrote: > On Sam, 2010-05-29 at 10:21 +0200, Sylvain Beucler wrote: > > > > When using the R300 driver in KMS mode (current default), performances > > for 2D operations are 15x slower than without KMS mode (previous > > default). > > > > The attached simple test runs at 17FPS in KMS mode on my computer, > > against 300FPS in non-KMS mode. > > On a similar setup (RV350 in a PowerBook) here, it runs at about 60-70 > fps with compiz and just above 100 fps without compositing. For reference I get 130 FPS on a Radeon Mobility M6 and 80 FPS on a S3 ProSavage (Lenny w/o compositing). > BTW, are your UMS numbers from driver version 6.13? Yes, I get 300FPS with: $ cat /etc/modprobe.d/radeon-kms.conf options radeon modeset=0 > With EXA or XAA? Xorg.0.log says EXA is enabled. With KMS: I tried without both, then with EXA and then with XAA. AFAICT this didn't changed the performances. I mean I used: Option "AccelMethod" "EXA" or Option "AccelMethod" "XAA" in the configuration, possibly one of them is enabled by default. > > This makes most 2D games unplayable. > > I'm not sure the test app is really representative for 'most 2D games'. Sure. 'freedink', for instance, runs at < 10 FPS at 100% CPU with KMS (vs. 60 FPS with at 75% CPU usage without KMS), which results in choppy animation and sound. The scrolling title screen 2D intro of Cytadela (which is otherwise a 3D game) is jumpy too. I realized there was a problem when working on a small test game and checking the FPS. After blaming Python and writing the C test, I had to witness Python was not faulty this time ;) > Forgot to mention: sysprof or oprofile profiles of slow and fast runs > might be interesting, at least if the CPU is pegged during the runs. Indeed CPU is at 100%. Do you have instructions on how to best run sysprof or oprofile? -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100529114855.gc2...@perso.beuc.net
Bug#583604: xserver-xorg-video-radeon: Corrupt screen after playing Cytadela OpenGL game and then running Emacs
On Sat, May 29, 2010 at 09:54:48AM +0200, Brice Goglin wrote: > Le 29/05/2010 09:18, Sylvain Beucler a écrit : > > As the maintainer of the freedink package, which is a 2D game, I > > sincerely hope we'll find a way to provide good 2D performances by > > default in Squeeze, either by fixing KMS performances, either by > > fixing non-KMS display corruption. > > Squeeze will use KMS by default, so obviously we want to fix KMS > performance, and you want to open the corresponding bug report instead > of mixing it with this one :) I opened another bug report at #583653. A last question: suppose that you can't fix the performances for a reason or another (frozen kernel, etc.). What do you maintainers plan to do? -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100529082925.gb3...@perso.beuc.net
Bug#583653: xserver-xorg-video-radeon: 15x-slower performance regression in KMS mode for 2D operations
Package: xserver-xorg-video-radeon Version: 1:6.13.0-2 Severity: important When using the R300 driver in KMS mode (current default), performances for 2D operations are 15x slower than without KMS mode (previous default). The attached simple test runs at 17FPS in KMS mode on my computer, against 300FPS in non-KMS mode. This makes most 2D games unplayable. It's worth noting that disabling KMS mode is currently not an option, since non-KMS has display corruption (which didn't happen in the Lenny version) and is otherwise obsoleted. See #583604. -- 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 Jun 9 2006 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1725256 May 4 15:51 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1412 May 29 09:47 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "fr" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" # Xorg.0.log says XAA ain't supported anymore: # (II) RADEON(0): XAA Render acceleration unsupported on Radeon 9500/9700 and newer. Please use EXA instead. # Option "AccelMethod" "EXA" # Option "AccelMethod" "XAA" # Won't work: # Driver "radeonhd" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" # DefaultDepth16 EndSection Section "Extensions" Option "Composite" "enable" EndSection Kernel version (/proc/version): Linux version 2.6.32-5-686 (Debian 2.6.32-13) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-10) ) #1 SMP Wed May 19 19:51:54 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 37515 Jan 19 2008 /var/log/Xorg.20.log -rw-r--r-- 1 root root 47787 Apr 30 18:55 /var/log/Xorg.1.log -rw-r--r-- 1 root root 39446 May 29 09:50 /var/log/Xorg.2.log -rw-r--r-- 1 root root 39013 May 29 09:50 /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.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-4-686 i686 Debian Current Operating System: Linux dmc 2.6.32-5-686 #1 SMP Wed May 19 19:51:54 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=a345c5eb-4d62-4b33-9cb5-8c408482c916 ro Build Date: 04 May 2010 03:43:42PM xorg-server 2:1.7.7-1 (Julien Cristau ) 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: Sat May 29 09:50:48 2010 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defo
Bug#583604: xserver-xorg-video-radeon: Corrupt screen after playing Cytadela OpenGL game and then running Emacs
On Sat, May 29, 2010 at 09:30:15AM +0200, Brice Goglin wrote: > Le 29/05/2010 09:18, Sylvain Beucler a écrit : > > Hi, > > > > On Sat, May 29, 2010 at 08:56:38AM +0200, Brice Goglin wrote: > > > >> Le 29/05/2010 08:40, Sylvain Beucler a écrit : > >> > >>> reopen 583604 > >>> thanks > >>> > >>> To get the 2D performances back (300FPS vs. 17FPS) I had to disable > >>> KMS. In this case, the display corruption still happens with the > >>> newer driver and kernel. > >>> > >> We're not going to track bugs for 6.13 without KMS, this case isn't > >> recommended already and it won't be supported in the future. > >> > > Hmmm, you mentioned that 6.13 is what is planned to go in Squeeze. > > > > 6.13 with KMS. I would appreciate if you read my reply in its entirety instead of stopping at the first sentence, and answer accordingly, thanks. -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100529073757.ga2...@perso.beuc.net
Bug#583604: xserver-xorg-video-radeon: Corrupt screen after playing Cytadela OpenGL game and then running Emacs
Hi, On Sat, May 29, 2010 at 08:56:38AM +0200, Brice Goglin wrote: > Le 29/05/2010 08:40, Sylvain Beucler a écrit : > > reopen 583604 > > thanks > > > > To get the 2D performances back (300FPS vs. 17FPS) I had to disable > > KMS. In this case, the display corruption still happens with the > > newer driver and kernel. > > We're not going to track bugs for 6.13 without KMS, this case isn't > recommended already and it won't be supported in the future. Hmmm, you mentioned that 6.13 is what is planned to go in Squeeze. As the maintainer of the freedink package, which is a 2D game, I sincerely hope we'll find a way to provide good 2D performances by default in Squeeze, either by fixing KMS performances, either by fixing non-KMS display corruption. Otherwise this is a regression against Lenny. Let me know if I'm mistaken. I think this may be a Debian bug more than a Radeon bug. What do you think? I'm not rereopening to avoid an open/close war and wait for your input. > If KMS is slow, please open a different bug. Sure, I'll do that too. > Make sure you have firmware-linux installed (see in dmesg whether > some firmwares are missing). As I mentioned I installed the (sadly non-free) R300 2kB firmware. Apparently dmesg is happy: $ dmesg|grep -C2 firmware [ 109.840767] [drm] Setting GART location based on new memory map [ 109.840862] [drm] Loading R300 Microcode [ 109.841585] platform radeon_cp.0: firmware: requesting radeon/R300_cp.bin [ 109.909568] [drm] Num pipes: 1 [ 109.909581] [drm] writeback test succeeded in 1 usecs -- [ 427.525752] [drm] Setting GART location based on new memory map [ 427.525848] [drm] Loading R300 Microcode [ 427.526558] platform radeon_cp.0: firmware: requesting radeon/R300_cp.bin [ 427.536623] [drm] Num pipes: 1 [ 427.536636] [drm] writeback test succeeded in 1 usecs Cheers! -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100529071841.ga3...@perso.beuc.net
Bug#583604: xserver-xorg-video-radeon: Corrupt screen after playing Cytadela OpenGL game and then running Iceweasel
Hi again,
On Fri, May 28, 2010 at 10:40:00PM +0200, Brice Goglin wrote:
> Version: 1:6.13.0-2
>
> Le 28/05/2010 22:36, Sylvain Beucler a écrit :
> >
> >>You should try with 6.13.0 and KMS since that's what will be in Squeeze. So:
> >>* upgrade your kernel to linux-image-2.6.32-5-686
> >>* install xserver-xorg-video-radeon 6.13.0
> >I can't reproduce the screen corruption anymore, so I guess it's ok :)
>
> Good to know, closing.
You'll probably also want to know, although that's less good, that 2D
performances decreased quite a lot. I can only get < 10FPS in 2D
games now (used to be > 60FPS).
This following simple SDL app runs at 17FPS while, from memory, it ran
at least at 100FPS previously.
Shall I open another bug?
#include
#include "SDL.h"
int main(void)
{
SDL_Init(SDL_INIT_EVERYTHING);
SDL_Surface* screen = SDL_SetVideoMode(640,480, 0, SDL_DOUBLEBUF);
Uint32 start = SDL_GetTicks();
int nb_frames = 200;
int i = 0;
for (; i < nb_frames; i++)
{
SDL_Rect r = {10,10,40,60};
SDL_FillRect(screen, &r, SDL_MapRGB(screen->format, 0,0,255));
SDL_Flip(screen);
}
printf("%g\n", 1000.0 * nb_frames / (SDL_GetTicks() - start));
SDL_Quit();
}
/**
* Local Variables:
* compile-command: "gcc -ggdb $(sdl-config --cflags --libs) test.c -o test"
* End:
*/
--
Sylvain
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100528235035.ga3...@perso.beuc.net
Bug#583604: xserver-xorg-video-radeon: Corrupt screen after playing Cytadela OpenGL game and then running Iceweasel
On Fri, May 28, 2010 at 09:22:09PM +0200, Brice Goglin wrote: > Le 28/05/2010 20:50, Sylvain Beucler a écrit : > >Package: xserver-xorg-video-radeon > >Version: 1:6.12.6-1 > >Severity: normal > > > >Hi, > > > >I get a screen corruption: lots of horizontal lines on a big area of > >the screen. > > You should try with 6.13.0 and KMS since that's what will be in Squeeze. So: > * upgrade your kernel to linux-image-2.6.32-5-686 > * install xserver-xorg-video-radeon 6.13.0 I can't reproduce the screen corruption anymore, so I guess it's ok :) Thanks! -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100528203630.ga2...@perso.beuc.net
Bug#516890: xserver-xorg-video-ati: Black screen, work-around is forcing "radeon" driver
> > Now, where should this bug go? > > > > In a default Lenny install, Xorg uses 'radeonhd' while, given the > > state of the drivers in Lenny, it would better use 'radeon'. > > Maybe this can be a candidate fix for Debian 5.0.1. > > > I'm not sure. Maybe you can make a case about this to > debian-rele...@l.d.o and see what they think? First, I think we need to check that it can be done technically. Brice, do you think that patching the Lenny version to force using 'radeon' for a ATI HD 3430 is possible, and desirable? -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#516890: xserver-xorg-video-ati: Black screen, work-around is forcing "radeon" driver
On Tue, Feb 24, 2009 at 11:37:35AM +0100, Brice Goglin wrote: > Sylvain Beucler wrote: > > Package: xserver-xorg-video-ati > > Version: 1:6.9.0-1+lenny4 > > Severity: normal > > > > On a Radeon HD 3430, the screen goes black went starting X. > > By specifying: > > > > Section "Device" > > Identifier "Configured Video Device" > > Driver "radeon" > > EndSection > > > > the problem goes away. > > I guess it uses "radeonhd" by default. > > > > Why do you open a bug report against ati if you think radeonhd is used? > ati only contains radeon, radeonhd is a different package. Sorry, I thought that 'ati' was responsible for chosing between radeon and radeonhd. > Please remove the above Driver "radeon" in the config and send the > corresponding log. Attached. The 'RADEONHD' prefix is there. I also attached the 'radeon' log. > If the log confirms that radeonhd is loaded, please try the 1.2.4 > package from > http://people.debian.org/~bgoglin/rebuilds/radeonhd-1.2.4-Xserver1.4/ This version works fine. (other log attached) This module recompilation is really handy :) I'd be interested in documentation to do the same! Now, where should this bug go? In a default Lenny install, Xorg uses 'radeonhd' while, given the state of the drivers in Lenny, it would better use 'radeon'. Maybe this can be a candidate fix for Debian 5.0.1. -- Sylvain Xorg.log-radeon-1.6.9.gz Description: Binary data Xorg.log-radeonhd-1.2.1.gz Description: Binary data Xorg.log-radeonhd-1.2.4.gz Description: Binary data
Bug#516890: xserver-xorg-video-ati: Black screen, work-around is forcing "radeon" driver
Package: xserver-xorg-video-ati Version: 1:6.9.0-1+lenny4 Severity: normal On a Radeon HD 3430, the screen goes black went starting X. By specifying: Section "Device" Identifier "Configured Video Device" Driver "radeon" EndSection the problem goes away. I guess it uses "radeonhd" by default. Interestingly enough, the Lenny Live CD from last december worked fine directly. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 fév 23 15:06 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1718484 jan 9 04:11 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Device 95c2 /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1125 fév 23 16:16 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "fr" Option "XkbVariant""latin9" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" Driver "radeon" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 45158 fév 24 11:00 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-10) Current Operating System: Linux debian 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 Build Date: 09 January 2009 02:57:16AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present 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: Tue Feb 24 11:00:30 2009 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) |-->Input Device "Configured Mouse" (==) |-->Input Device "Generic Keyboard" (==) The core pointer device wasn't specified explicitly in the layout. Using the first mouse device. (==) The core keyboard device wasn't specified explicitly in the layout. Using the first keyboard device. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) RgbPath set to "/etc/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81e38c0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.2, module version = 1.0.0 ABI class: X.Org Video Driver, ver
Bug#504535: xserver-xorg-video-radeon: Freeze in 24bit and 16bit fullscreen (Radeon Mobility M6 LY)
On Thu, Feb 19, 2009 at 07:08:50AM +0100, Brice Goglin wrote: > Alex Deucher wrote: > > On Wed, Feb 18, 2009 at 4:06 AM, Sylvain Beucler wrote: > > > >>>> The new 'radeon' driver correctly detects 2x. It doesn't seem to > >>>> freeze. > >>>> > >>>> However, full-screen 640x480 mode is now a small display centered in > >>>> the full 1024x768 screen. Before it really switched resolution to > >>>> cover the full screen. > >>>> > >>> The scaling should default to full rather then center. Can attach the > >>> output of xrandr --verbose? > >>> > >> Here it is. > >> > > > > This should be fixed in git master. > > > > Alex > > > > Sylvain, > > Alex released driver 6.11.0 since then, it should solve your last > problem. Packages are in experimental, and also availabel for Lenny at > http://people.debian.org/~bgoglin/rebuilds/ati-6.11.0-Xserver1.4/ This fixed the !fullscreen issue. Thanks! -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#504535: xserver-xorg-video-radeon: Freeze in 24bit and 16bit fullscreen (Radeon Mobility M6 LY)
> > The new 'radeon' driver correctly detects 2x. It doesn't seem to > > freeze. > > > > However, full-screen 640x480 mode is now a small display centered in > > the full 1024x768 screen. Before it really switched resolution to > > cover the full screen. > > The scaling should default to full rather then center. Can attach the > output of xrandr --verbose? Here it is. -- Sylvain Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1024 x 1024 VGA-0 disconnected (normal left inverted right x axis y axis) Identifier: 0x5c Timestamp: 144086 Subpixel: no subpixels Clones: DVI-0 CRTCs: 0 1 load_detection: 1 (0x0001) range: (0,1) DVI-0 disconnected (normal left inverted right x axis y axis) Identifier: 0x5d Timestamp: 144086 Subpixel: horizontal rgb Clones: VGA-0 CRTCs: 0 1 scaler: off LVDS connected 1024x768+0+0 (0x60) normal (normal left inverted right x axis y axis) 0mm x 0mm Identifier: 0x5e Timestamp: 144086 Subpixel: horizontal rgb Clones: CRTC: 0 CRTCs: 0 scaler: full 1024x768 (0x60) 65.0MHz *current +preferred h: width 1024 start 1040 end 1176 total 1344 skew0 clock 48.4KHz v: height 768 start 770 end 771 total 806 clock 60.0Hz 1024x768 (0x61) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz S-video disconnected (normal left inverted right x axis y axis) Identifier: 0x5f Timestamp: 144086 Subpixel: no subpixels Clones: CRTCs: 0 1 tv_standard: ntsc tv_vertical_position: 0 (0x) range: (-5,5) tv_horizontal_position: 0 (0x) range: (-5,5) tv_horizontal_size: 0 (0x) range: (-5,5)
Bug#504535: xserver-xorg-video-radeon: Freeze in 24bit and 16bit fullscreen (Radeon Mobility M6 LY)
On Mon, Feb 16, 2009 at 07:40:55PM +0100, Brice Goglin wrote: > Alex Deucher wrote: > > Looks like we already have a quirk for this system. It should be > > handled properly in newer versions of the driver. > > > > > Sylvain, > > We have radeon driver 6.10.99.0 in experimental, but you'll have to > upgrade many Xorg packages to get it. > > I have rebuilt it for Lenny on i386, the packages are available at > http://people.debian.org/~bgoglin/rebuilds/ati-6.10.99.0-Xserver1.4/ > > Please try one of the above after removing AGPMode from your xorg.conf, > see what AGPMode the log now reports and whether it still freezes. I installed 'xserver-xorg-videon-radeon' (not sure about other packages). Logs: (==) RADEON(0): Using AGP 2x [ 4807.987333] agpgart: Found an AGP 2.0 compliant device at :00:00.0. [ 4807.987333] agpgart: Putting AGP V2 device at :00:00.0 into 2x mode [ 4807.987333] agpgart: Putting AGP V2 device at :01:00.0 into 2x mode [ 4808.323975] [drm] Setting GART location based on new memory map [ 4808.323975] [drm] Loading R100 Microcode [ 4808.323975] [drm] writeback test succeeded in 1 usecs The new 'radeon' driver correctly detects 2x. It doesn't seem to freeze. However, full-screen 640x480 mode is now a small display centered in the full 1024x768 screen. Before it really switched resolution to cover the full screen. -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#504535: xserver-xorg-video-radeon: Freeze in 24bit and 16bit fullscreen (Radeon Mobility M6 LY)
On Sun, Feb 01, 2009 at 05:52:29PM +0100, Brice Goglin wrote: > Sylvain Beucler wrote: > >> Does > >> > >>Option "AGPMode" "1" > >> > >> (or "2") help? Please verify for your tests that the option value is > >> reflected in the log line above. > >> > > > > Apparently this helps, but the freezes are not as easily reproduceable > > as I thought, so I can't say for sure. I'll run some more tests. > > > > Any news about this? > Once you'll have found a AGPMode value that works better, we'll ask > upstream to add a quirk for your machine. Apparently 2x works best. 24bit - 4x (==) RADEON(0): Using AGP 4x Feb 13 20:26:57 kobo kernel: [ 5112.044659] agpgart: Found an AGP 2.0 compliant device at :00:00.0. Feb 13 20:26:57 kobo kernel: [ 5112.044659] agpgart: Putting AGP V2 device at :00:00.0 into 4x mode Feb 13 20:26:57 kobo kernel: [ 5112.044659] agpgart: Putting AGP V2 device at :01:00.0 into 4x mode Feb 13 20:26:59 kobo kernel: [ 5113.556487] [drm] Setting GART location based on new memory map Feb 13 20:26:59 kobo kernel: [ 5113.556487] [drm] Loading R100 Microcode Feb 13 20:26:59 kobo kernel: [ 5113.695213] [drm] writeback test failed Sometimes very small horizontal lines all across the screen, sometimes it will crash. It probably depends on temperature / how intensively the card was used before. This is why the freezes aren't easy to reproduce in all situations. torus-troopers windowed: FREEZE if the card was stressed torus-troopers fullscreen: FREEZE guaranted after a little while title screen fonts: OK 24bit - 1x (**) RADEON(0): Using AGP 1x Feb 13 20:43:55 kobo kernel: [ 312.164131] agpgart: Found an AGP 2.0 compliant device at :00:00.0. Feb 13 20:43:55 kobo kernel: [ 312.164170] agpgart: Putting AGP V2 device at :00:00.0 into 1x mode Feb 13 20:43:55 kobo kernel: [ 312.164192] agpgart: Putting AGP V2 device at :01:00.0 into 1x mode Feb 13 20:43:56 kobo kernel: [ 313.673178] [drm] Setting GART location based on new memory map Feb 13 20:43:56 kobo kernel: [ 313.673178] [drm] Loading R100 Microcode Feb 13 20:43:56 kobo kernel: [ 313.812819] [drm] writeback test failed torus-troopers windowed: OK torus-troopers fullscreen: OK title screen fonts: MESSY 24bit - 2x (**) RADEON(0): Using AGP 2x Feb 13 21:23:53 kobo kernel: [ 1214.753137] agpgart: Found an AGP 2.0 compliant device at :00:00.0. Feb 13 21:23:53 kobo kernel: [ 1214.753137] agpgart: Putting AGP V2 device at :00:00.0 into 2x mode Feb 13 21:23:53 kobo kernel: [ 1214.753137] agpgart: Putting AGP V2 device at :01:00.0 into 2x mode Feb 13 21:23:54 kobo kernel: [ 1216.260518] [drm] Setting GART location based on new memory map Feb 13 21:23:54 kobo kernel: [ 1216.260518] [drm] Loading R100 Microcode Feb 13 21:23:54 kobo kernel: [ 1216.260518] [drm] writeback test succeeded in 1 usecs ==> not sure what this failed/succeeded means torus-troopers windowed: OK torus-troopers fullscreen: OK title screen fonts: OK At first glance, no freeze. When the card freezes, SSH is still functional, but the only way to get the screen back is to reboot. The mouse may still be functional though. -- Sylvain -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#504535: xserver-xorg-video-radeon: Freeze in 24bit and 16bit fullscreen (Radeon Mobility M6 LY)
On Wed, Nov 05, 2008 at 10:21:36AM +0100, Michel Dänzer wrote: > On Tue, 2008-11-04 at 22:18 +0100, Sylvain Beucler wrote: > > > > I just did a Etch->Lenny upgrade. > > The system locks up at the GDM prompt in 24bit after displaying half of the > > screen. > > In 16bit it goes well, unless I start a game in fullscreen (e.g. > > torus-trooper), in which case it will eventually > > lock in less than a few minutes. > > > > The video card worked in 24bit under Etch. > > > > I played little games and torus-trooper wasn't available under Etch so I > > can't > > say for sure that the _full-screen_ freeze couldn't happen before. > > 24bit 2D fullscreen sure worked ok though. > > [...] > > > (==) RADEON(0): Using AGP 4x > > Does > > Option "AGPMode" "1" > > (or "2") help? Please verify for your tests that the option value is > reflected in the log line above. Apparently this helps, but the freezes are not as easily reproduceable as I thought, so I can't say for sure. I'll run some more tests. Thanks, -- Sylvain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#504535: xserver-xorg-video-radeon: Freeze in 24bit and 16bit fullscreen (Radeon Mobility M6 LY)
Package: xserver-xorg-video-radeon Version: 1:6.9.0-1+lenny4 Severity: important Hi, I just did a Etch->Lenny upgrade. The system locks up at the GDM prompt in 24bit after displaying half of the screen. In 16bit it goes well, unless I start a game in fullscreen (e.g. torus-trooper), in which case it will eventually lock in less than a few minutes. The video card worked in 24bit under Etch. I played little games and torus-trooper wasn't available under Etch so I can't say for sure that the _full-screen_ freeze couldn't happen before. 24bit 2D fullscreen sure worked ok though. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 jun 21 19:25 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1718484 sep 30 02:06 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1262 nov 1 09:19 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "fr" Option "XkbVariant""latin9" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" Option "XAANoOffscreenPixmaps" "true" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" # Crashes: # DefaultDepth24 DefaultDepth16 EndSection Section "Extensions" Option "Composite" "enable" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 40348 jui 17 01:04 /var/log/Xorg.1.log -rw-r--r-- 1 root root 42073 nov 4 22:08 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-7) Current Operating System: Linux kobo 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 Build Date: 30 September 2008 01:48:58AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present 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: Tue Nov 4 22:07:56 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) |-->Input Device "Configured Mouse" (==) |-->Input Device "Generic Keyboard" (==) The core pointer device wasn't specified explicitly in the layout. Using the first mouse device. (==) The core keyboard device wasn't specified explicitly in the layout. Using the first keyboard device. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) RgbPath set to "/etc/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (**) Extension "Composite" is enabled (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81e
Bug#500495: Error "fire_buffer: DRM_VIA_PCICMD returned -22" on startup
Hi, I confirm that this is a S3 UniChrome: 00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01) So apparently I do have 3D support on this box... which I probably didn't have in Etch :) FYI, I retried with Driver "openchrome" : $ titanion do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. Try adjusting the vblank_mode configuration parameter. Load bgm: ttn1.ogg Load bgm: ttn3.ogg Load bgm: ttn2.ogg Load SE: shot.wav Load SE: explosion1.wav Load SE: explosion2.wav Load SE: explosion3.wav Load SE: tractor.wav Load SE: flying_down.wav Load SE: player_explosion.wav Load SE: flick.wav Load SE: extend.wav fire_buffer: DRM_VIA_CMDBUFFER returned -22 The error is less verbose, and is slightly different (previous was: fire_buffer: DRM_VIA_PCICMD returned -22 ) Some other games such as Extreme Tux Racer do work. -- Sylvain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
