Bug#489495: update?
is this still a problem with the newer radeon driver from squeeze? If so, could you try getting the even newer one from sid (you'll need a newer kernel as well, either 2.6.32-10 from sid or 2.6.33-1 from experimental). For this you will need to enable Kernel modesetting. add *radeon* to /etc/modules and put *options radeon modeset=1* in /etc/modprobe.d/radeon-kms.conf (you'll probably need to create the file). let us know Andres
Bug#495367: update?
Franck is this still a problem with the newer radeon driver from squeeze (or are you still running lenny)? If so, could you try getting the even newer one from sid (you'll need a newer kernel as well, either 2.6.32-10 from sid or 2.6.33 from experimental). For this you will need to enable Kernel modesetting. add *radeon* to /etc/modules and put *options radeon modeset=1*in /etc/modprobe.d/radeon-kms.conf (you'll probably need to create the file). Andres
Bug#492912: is this still an issue?
Hi Stefan, Do you still have lenny on the laptop or you continued using testing (now squeeze)? I actually installed debian lenny on this same laptop not too long ago. Gnome tends to overrule your xrandr configuration (only in lenny, squeeze doesn't have this problem with the computer I've tried). Try disabling gnome xrandr plugin. To do this, go to gconf-editor, browse /apps/gnome-settings-daemon/ plugins/xrandr and uncheck the "active" entry (Important, you will have to place a file with an appropiate xrandr initial configuration in /etc/X11/Xsession.d/ a sample is given in the link below). You could also try a simpler xorg.conf. Try NO options for the external monitor and set everything up in the xrandr conf file If you want more info, this helped me a great deal: http://www.jejik.com/articles/2008/10/setting_up_dual_monitors_system-wide_with_xrandr_on_debian_lenny/ Unfortunately radeon in lenny couldn't handle using the 2 monitors at the same time well, so I opted to have a launcher on the desktop for use of TV only and one for use of laptop screen only. I don't recall if I ever closed the lid on my laptop after choosing only to use tv as output but I have the feeling I did try it. You could also go to System > Preferences > Power Management and choose "do nothing" or "blank screen" for the option of what to do when laptop lid is closed. To try to solve these problems I ended up installing squeeze on that laptop. It works much much better. However, I still find the using of only tv / laptop screen appealing so I've kept the launchers on the desktop. I will try closing the lid. If you have problems, please try getting a newer radeon driver from sid (you'll need a newer kernel as well, either 2.6.32-10 from sid or 2.6.33 from experimental). For this you will need to enable Kernel modesetting. add *radeon* to /etc/modules and put *options radeon modeset=1* in /etc/modprobe.d/radeon-kms.conf (you'll probably need to create the file). I have this set up in the laptop and it works pretty well. (Please also get firmware-linux firmware-linux-nonfree libdrm-radeon1). Hope this helps Andres
Bug#546609: maybe?
Perhaps this is nothing and it just stems from my lack of knowledge, but I saw that the output of your uname -a command yielded: Linux imladris 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 GNU/Linux Kernel 2.6.32-trunk was removed from sid a while ago. You should have the latest: http://packages.debian.org/sid/linux-image-2.6.32-4-amd64. This last one has many bugfixes for enable KMS with radeon. Let me know what happens Andres
Bug#575391: xserver-xorg-video-intel: Xorg crash and GPU lockup with 2.6.33 KMS
On Fri, 2010-04-02 at 00:21 +0200, Cyril Brulebois wrote: > Agreed. I won't forget about it anyway, I got a coworker having his > laptop crash all the time in a similar way (though reproducibly and > with traces). Ah, bummer. > As for X fixing the GPU, I've been told yesterday it only works with > recent hardware (like in: if yours is 1-2 year old, you're screwed > already; which matches my local experience). Gah, fucking embedded non-free blobs. This just makes me a more rabid FLOSS zealot and supporter of DFSG #2. I should do a talk about the DFSG at DebConf and just rant about embedded non-free blobs for an hour. Grr! > Good luck until we have a fix… I'm not holding my breath ;) Thanks for all the info. -- bye, pabs http://bonedaddy.net/pabs3/ signature.asc Description: This is a digitally signed message part
Bug#576183: Mouse sometimes erratically jumps around, locks X server, when crossing Xinerama edges
Hi, martin f krafft (01/04/2010): > Recently, I've had to restart X sometimes several times per hour > because I'd move the mouse across a Xinerama edge onto another > screen, and it would get stuck there, erratically jumping back and > forth between the screens. I could still move the mouse and > influence the pointer a bit, but the system would be unusable. (apologies, I know nothing about Xinerama, and I'm currently onboard a train so cannot check right now, but) isn't a WM involved in this kind of things? In which case, does trying another one help? When you say lock, I assume the server isn't actually deadlocked, it's “just” you're switching quickly between 2 (or a limited number of) positions on screen, and input being directed once here once there? Mraw, KiBi. signature.asc Description: Digital signature
Bug#575391: marked as done (xserver-xorg-video-intel: Xorg crash and GPU lockup with 2.6.33 KMS)
Your message dated Fri, 2 Apr 2010 00:21:13 +0200 with message-id <20100401222113.gd3...@debian.org> and subject line Re: Bug#575391: xserver-xorg-video-intel: Xorg crash and GPU lockup with 2.6.33 KMS has caused the Debian Bug report #575391, regarding xserver-xorg-video-intel: Xorg crash and GPU lockup with 2.6.33 KMS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 575391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-intel Version: 2:2.9.1-2 Severity: normal During a period of heavy load (multiple pbuilder runs), Xorg crashed and would no longer start until after a reboot. Looks like the GPU hung, I thought Xorg was capable of rebooting the GPU when its firmware got itself tangled up? -- 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 Jul 31 2008 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1866912 Feb 16 18:25 /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 Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r- 1 root root 706 Jan 18 05:13 /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 "Device" Identifier "Configured Video Device" Option "XvMC" "true" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 48487 Dec 11 14:14 /var/log/Xorg.20.log -rw-r--r-- 1 root root 21061 Mar 25 21:52 /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.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.8-dsa-amd64 x86_64 Debian Current Operating System: Linux chianamo 2.6.33-2-amd64 #1 SMP Wed Mar 17 18:41:49 UTC 2010 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.33-2-amd64 root=/dev/mapper/chianamo-root ro quiet loglevel=0 Build Date: 16 February 2010 10:23:38AM xorg-server 2:1.7.5-1 (bui...@brahms.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: Thu Mar 25 21:52:41 2010 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |-->Screen "Default Screen Section" (0) (**) | |-->Monitor "" (==) No device specified for screen "Default Screen Section". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) No monitor specified for screen "Default Screen Section". 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. (==) 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, built-ins (==) ModulePath set to "/usr/lib/xorg/modules" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x7c1e20
Bug#546609: is this still a problem?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, Perhaps this is not the same bug, but I have/had the same problem. Not only has it not gone away, after a recent upgrade the desktop doesn't appear at all. Oddly, changing to vt1 then vt7 works, and shows the desktop, but once only. After this, switching back to vt1 results in no display (monitor goes to standby). KMS settings are configured as discussed. I'm running sid: co...@imladris:~$ uname -a Linux imladris 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 GNU/Linux co...@imladris:~$ dpkg --list | grep xserver-xorg ii xserver-xorg 1:7.5+5 the X.Org X server ii xserver-xorg-core2:1.7.6-1 Xorg X server - core server ii xserver-xorg-dev 2:1.7.6-1 Xorg X server - development files ii xserver-xorg-input-evdev 1:2.3.2-4 X.Org X server -- evdev input driver ii xserver-xorg-input-kbd 1:1.4.0-1 X.Org X server -- keyboard input driver ii xserver-xorg-input-mouse 1:1.5.0-1 X.Org X server -- mouse input driver ii xserver-xorg-input-synaptics 1.2.1-1 Synaptics TouchPad driver for X.Org server ii xserver-xorg-input-wacom 0.10.3+20100109-1 X.Org X server -- Wacom input driver ii xserver-xorg-video-all 1:7.5+5 the X.Org X server -- output driver metapack ii xserver-xorg-video-apm 1:1.2.2-1 X.Org X server -- APM display driver ii xserver-xorg-video-ark 1:0.7.2-1 X.Org X server -- ark display driver ii xserver-xorg-video-ati 1:6.12.192-2 X.Org X server -- AMD/ATI display driver wra ii xserver-xorg-video-chips 1:1.2.2-1 X.Org X server -- Chips display driver ii xserver-xorg-video-cirrus1:1.3.2-1 X.Org X server -- Cirrus display driver ii xserver-xorg-video-fbdev 1:0.4.1-2 X.Org X server -- fbdev display driver ii xserver-xorg-video-i128 1:1.3.3-1 X.Org X server -- i128 display driver ii xserver-xorg-video-intel 2:2.9.1-3 X.Org X server -- Intel i8xx, i9xx display d ii xserver-xorg-video-mach646.8.2-2 X.Org X server -- ATI Mach64 display driver ii xserver-xorg-video-mga 1:1.4.11.dfsg-2 X.Org X server -- MGA display driver ii xserver-xorg-video-neomagic 1:1.2.4-2 X.Org X server -- Neomagic display driver ii xserver-xorg-video-nv1:2.1.17-1 X.Org X server -- NV display driver ii xserver-xorg-video-openchrome1:0.2.904+svn827-1 X.Org X server -- VIA display driver ii xserver-xorg-video-r128 6.8.1-2 X.Org X server -- ATI r128 display driver ii xserver-xorg-video-radeon1:6.12.192-2 X.Org X server -- AMD/ATI Radeon display dri ii xserver-xorg-video-radeonhd 1.3.0-2 X.Org X server -- AMD/ATI r5xx, r6xx display ii xserver-xorg-video-rendition 1:4.2.3-1 X.Org X server -- Rendition display driver ii xserver-xorg-video-s31:0.6.3-1 X.Org X server -- legacy S3 display driver ii xserver-xorg-video-s3virge 1:1.10.4-1 X.Org X server -- S3 ViRGE display driver ii xserver-xorg-video-savage1:2.3.1-1 X.Org X server -- Savage display driver ii xserver-xorg-video-siliconmotion 1:1.7.3-1 X.Org X server -- SiliconMotion display driv ii xserver-xorg-video-sis 1:0.10.2-2 X.Org X server -- SiS display driver ii xserver-xorg-video-sisusb1:0.9.3-1 X.Org X server -- SiS USB display driver ii xserver-xorg-video-tdfx 1:1.4.3-1 X.Org X server -- tdfx display driver ii xserver-xorg-video-trident 1:1.3.3-1 X.Org X server -- Trident display driver ii xserver-xorg-video-tseng 1:1.2.3-1 X.Org X server -- Tseng display driver ii xserver-xorg-video-v4l 1:0.2.0-4 X.Org X server -- Video 4 Linux display driv ii xserver-xorg-video-vesa 1:2.3.0-1 X.Org X server -- VESA display driver ii xserver-xorg-video-vmware1:10.16.9-1 X.Org X server -- VMware display driver ii xserver-xorg-video-voodoo1:1.2.3-1 X.Org X server -- Voodoo display driver CT. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAku1CzQACgkQ0SwfPjLnaZZ4SACfZqj+djD4CEQvGNxuymzmllGd rn4AoMCsfT6cm4TPbR7ZRmOOphdKBgdW =RAi/ -END PGP SIGNATURE- -- 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/4bb50b35.1030...@piglets.com
Bug#575585: xserver-xorg-video-radeon: [KMS] Crashes when switching VTs
Le jeudi 01 avril 2010 à 21:55 +0200, Josselin Mouette a écrit : > Le jeudi 01 avril 2010 à 12:19 -0700, Will Set a écrit : > > Hi Josselin, > > I omitted the x-mailing-list to reduce chatter a bit. > > I think if you have not already upgraded to kernel > > 2.6.32-4-amd64 that doing so may fix your issue.. > > I didn’t know there was a 2.6.32-4 kernel, it looks like it still isn’t > the default - probably because it includes the libata transition. > > However you are right: upgrading to it seems to fix the issue for good. After a few more tries, I’m a bit disappointed. The crash has gone, sure, but after a bit of juggling with several X servers, new X servers still refuse to start with the same error as before. -- .''`. Josselin Mouette : :' : `. `' “If you behave this way because you are blackmailed by someone, `-[…] I will see what I can do for you.” -- Jörg Schilling signature.asc Description: This is a digitally signed message part
Bug#575585: xserver-xorg-video-radeon: [KMS] Crashes when switching VTs
Le jeudi 01 avril 2010 à 12:19 -0700, Will Set a écrit : > Hi Josselin, > I omitted the x-mailing-list to reduce chatter a bit. > I think if you have not already upgraded to kernel > 2.6.32-4-amd64 that doing so may fix your issue.. I didn’t know there was a 2.6.32-4 kernel, it looks like it still isn’t the default - probably because it includes the libata transition. However you are right: upgrading to it seems to fix the issue for good. Thanks, -- .''`. Josselin Mouette : :' : `. `' “If you behave this way because you are blackmailed by someone, `-[…] I will see what I can do for you.” -- Jörg Schilling signature.asc Description: This is a digitally signed message part
Bug#576229: Warn about missing firmware files
Package: xserver-xorg-video-radeon
Version: 1:6.12.192-2
Severity: wishlist
Tags: patch
#include
This is followup to bug #575945. I should mention the fact that I
_had_ a lot of radeon firmware files in /lib/firmware/$(uname
-r)/radeon/, therefore it was not obvious to look for firmware issues.
The firmware-linux package was suggested, sure, but its description
only talks about "modules from kernel source" and I obviously HAD them
installed.
The kernel log mentioned the missing firmware but that message was hard
to spot among other udev/framebuffer/... spam. The Xorg.0.log mentioned
a fallback to shadowfb but did not tell why, and even that thin line is
printed below tons of unrelated messages.
So, sorry, say what you want but locating the reason for the trouble is
not as simple as it may appear. Therefore, I offer the attached patch
which tries to detect a such situation and prints a more prominently
looking text block in the X log.
Regards,
Eduard.
diff --git a/src/radeon_kms.c b/src/radeon_kms.c
index 15e5e3f..d18a1ce 100644
--- a/src/radeon_kms.c
+++ b/src/radeon_kms.c
@@ -231,6 +231,24 @@ static Bool RADEONPreInitAccel_KMS(ScrnInfoPtr pScrn)
(!RADEONIsAccelWorking(pScrn))) {
xf86DrvMsg(pScrn->scrnIndex, X_INFO,
"GPU accel disabled or not working, using shadowfb for KMS\n");
+
+ /*
+ * Tell the user about what's (possibly) causing the problem.
+ *
+ * Checking whether required ucode files are present on the system
+ * in the location used by at least Debian and Mandriva.
+ */
+ if( access("/lib/firmware/radeon/R600_rlc.bin", R_OK) ||
+ access("/lib/firmware/radeon/R700_rlc.bin", R_OK))
+ {
+ xf86DrvMsg(pScrn->scrnIndex, X_INFO,
+ "This symptom may indicate an incompletely initialized firmware,\n"
+ "\tand apparently some firmware files are missing in the\n"
+ "\t/lib/firmware/radeon/ directory.\n"
+ "\tInstalling firmware-linux package and reloading the radeon\n"
+ "\tkernel module might solve the problem (reboot if needed).\n");
+ }
+
info->r600_shadow_fb = TRUE;
if (!xf86LoadSubModule(pScrn, "shadow"))
info->r600_shadow_fb = FALSE;
Bug#556548: is this still a problem?
Hi, I was getting similar problems with a laptop I have, but it was resolved a couple of radeon updates back. Is this still a problem with the newer radeon driver from squeeze (also newer kernel and mesa)? (make sure you have libdrm-radeon1, firmware-linux-nonfree and firmware-linux installed). If problem persists, could you try getting the even newer one from sid (you'll need a newer kernel as well, either 2.6.32-10 from sid or 2.6.33 from experimental). For this you will need to enable Kernel modesetting. add *radeon* to /etc/modules and put *options radeon modeset=1* in /etc/modprobe.d/radeon-kms.conf (you'll probably need to create the file). What Desktop environment are you running? If gnome I recommend you don't do your dual screen setup in your xorg.conf file. If you specify enough virtual size as you've done, gnome should do it automatically for you (this is what happens with a couple of laptops I have). You can also simply use xrandr. Simply put the "right" command in a file in /etc/X11/Xsession.d/ (I assume this would work perfectly in KDE and others). This is a valuable resource: http://www.jejik.com/articles/2008/10/setting_up_dual_monitors_system-wide_with_xrandr_on_debian_lenny/ Hope this helps, Andres
Bug#575585: xserver-xorg-video-radeon: [KMS] Crashes when switching VTs
Le samedi 27 mars 2010 à 14:39 +0100, Michel Dänzer a écrit :
> On Sat, 2010-03-27 at 12:52 +0100, Josselin Mouette wrote:
> >
> > I don’t really know how to obtain a better backtrace. I haven’t managed
> > to make it dump core, and using gdb directly on it prevents me from
> > switching VTs when the server crashes.
>
> Usually it's best to run gdb from a remote shell.
OK here we go.
Thread 1 (Thread 0x7fefb49ce6f0 (LWP 2431)):
#0 memcpy () at ../sysdeps/x86_64/memcpy.S:191
No locals.
#1 0x7fefb08ad2aa in RADEONUploadToScreenCS (pDst=,
x=, y=, w=,
h=, src=0xa0 ,
src_pitch=160) at ../../src/radeon_exa_funcs.c:535
pScrn =
driver_priv =
scratch = 0xc5cd10
dst = 0x7fefb49e5000
datatype =
dst_domain = 32751
dst_pitch_offset =
bpp =
scratch_pitch = 192
r =
i = 1
__func__ = "RADEONUploadToScreenCS"
#2 0x7fefb01c8222 in exaHWCopyNtoN (pSrcDrawable=,
pDstDrawable=, pGC=,
pbox=0x7fffbbfdf770, nbox=0, dx=-596, dy=-527, reverse=0, upsidedown=0)
at ../../exa/exa_accel.c:527
src_stride = 160
pSrcPixmap = 0x16efbb0
pDstPixmap = 0x971c10
pSrcExaPixmap = 0x16f0ef0
src_off_x = 0
src_off_y = 0
dst_off_x = 0
dst_off_y = 0
srcregion = 0xc17a90
dstregion = 0xc6c5b0
ret =
#3 0x7fefb01c832d in exaCopyNtoN (pSrcDrawable=,
pDstDrawable=0x9776d0, pGC=,
pbox=, nbox=, dx=-596, dy=-527,
reverse=0, upsidedown=0, bitplane=0, closure=0x0)
at ../../exa/exa_accel.c:574
No locals.
#4 0x0054cc0d in miCopyRegion (pSrcDrawable=0x16efbb0,
pDstDrawable=0x0, pGC=0xa0, pDstRegion=, dx=-596,
dy=, copyProc=0x7fefb01c8240 ,
bitPlane=0, closure=0xa0) at ../../mi/micopy.c:138
reverse = 40
upsidedown = 7
pbox = 0x7fffbbfdf770
nbox = 1
pboxNew1 =
pboxNew2 =
pboxBase =
pboxNext =
pboxTmp =
#5 0x0054d11a in miDoCopy (pSrcDrawable=0x16efbb0,
pDstDrawable=0x9776d0, pGC=0x1818470, xIn=0, yIn=0,
widthSrc=, heightSrc=40, xOut=596, yOut=527,
copyProc=0x7fefb01c8240 , bitPlane=0, closure=0x0)
at ../../mi/micopy.c:338
prgnSrcClip = 0x0
freeSrcClip = 0
prgnExposed =
rgnDst = {extents = {x1 = 596, y1 = 527, x2 = 636, y2 = 567},
data = 0x0}
dx = 12870
dy = 5279744
box_x1 =
box_y1 =
box_x2 =
box_y2 =
fastSrc =
fastDst =
fastExpose = 1
#6 0x7fefb01c6763 in exaCopyArea (pSrcDrawable=0x16efbb0,
pDstDrawable=0x9776d0, pGC=0x1818470, srcx=0, srcy=,
width=, height=40, dstx=596, dsty=527)
at ../../exa/exa_accel.c:598
No locals.
#7 0x004c84e8 in damageCopyArea (pSrc=0x16efbb0, pDst=0x9776d0,
pGC=0x1818470, srcx=, srcy=,
width=40, height=40, dstx=596, dsty=527)
at ../../../miext/damage/damage.c:949
ret =
pGCPriv = 0x16f1770
oldFuncs = 0x7c1860
#8 0x0054763d in miDCRestoreUnderCursor (pDev=,
pScreen=0x936180, x=, y=527, w=40,
h=) at ../../mi/midispcur.c:592
pBuffer =
pSave = 0x16efbb0
pWin = 0x9776d0
#9 0x0056d809 in miSpriteRemoveCursor (pDev=0xa88a80,
pScreen=0x936180) at ../../mi/misprite.c:995
pScreenPriv = 0x949bf0
pCursorInfo = 0xa9c800
#10 0x0056eded in miSpriteReportDamage (pDamage=,
pRegion=0x7fffbbfdfa40, closure=)
at ../../mi/misprite.c:278
pScreen = 0x936180
pCursorInfo =
pDev = 0xa88a80
#11 0x004c575c in damageReportDamage (pDamage=0x949c90,
pDamageRegion=0x7fffbbfdfa40) at ../../../miext/damage/damage.c:134
tmpRegion = {extents = {x1 = -10480, y1 = 168, x2 = 0, y2 = 0},
data = 0x7fefb2b0b9bc}
#12 0x004c5af6 in damageRegionAppend (pDrawable=,
pRegion=, clip=,
subWindowMode=) at ../../../miext/damage/damage.c:363
pScrPriv = 0x949b70
pDamage = 0x949c90
pNext = 0x0
clippedRec = {extents = {x1 = 0, y1 = 0, x2 = 1280, y2 = 1024},
data = 0xc6a040}
pDamageRegion = 0x7fffbbfdfa40
pixClip = {extents = {x1 = 0, y1 = 0, x2 = 1280, y2 = 1024},
data = 0x0}
draw_x =
draw_y = 0
screen_x = 0
screen_y = 0
#13 0x004c5c28 in damageDamageBox (pDrawable=0x7fefb49e5000,
pBox=, subWindowMode=)
at ../../../miext/damage/damage.c:425
region = {extents = {x1 = 0, y1 = 0, x2 = 1280, y2 = 1024},
data = 0xc69e80}
#14 0x004c6d40 in damagePolyFillRect (pDrawable=0x9776d0,
pGC=0x974400, nRects=12, pRects=0xc5e2c0)
at ../../../miext/damage/damage.c:1402
box = {x1 = 0, y1 = 0, x2 = 1280, y2 = 1024}
pRectsTmp =
nRectsTmp =
pGCPriv = 0x971e90
oldFuncs = 0x7c1860
#15 0x0
Bug#573118: marked as done (radeon: Suspend/hibernate don't wake up xpress 200m (rc410))
Your message dated Thu, 1 Apr 2010 13:38:23 -0400 with message-id and subject line resolved has caused the Debian Bug report #573118, regarding radeon: Suspend/hibernate don't wake up xpress 200m (rc410) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 573118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-radeon Version: 1:6.12.191-1 Severity: important I've tried suspending with both the version in squeeze (with user modesetting) and experimental (with KMS). The result is always the same, goes into suspend mode but when waking up, display is blank (the LCD screen doesn't even turn on). I also tried with 2.6.33 kernel in experimental, but the result was the same. This message appears with all versions tried: [drm:rs400_gart_adjust_size] *ERROR* Forcing to 32M GART size (because of ASIC bug ? ) -- 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 Mar 2 22:01 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1866912 Feb 16 05:25 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 445 Mar 6 18:48 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section "ServerLayout" Identifier "Default Layout" Screen "Screen 0" EndSection Section "Device" Identifier "ATI Radeon Xpress 200M IGP" Driver "radeon" BusID "PCI:1:5:0" Option "AccelMethod" "EXA" Option "AccelDFS" "1" Option "EnablePageFlip""1" EndSection Section "Monitor" Identifier "LVDS" EndSection Section "Screen" Identifier "Screen 0" Device "ATI Radeon Xpress 200M IGP" Monitor "LVDS" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 28735 Mar 8 23:43 /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.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.8-dsa-amd64 x86_64 Debian Current Operating System: Linux debturion 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64 root=UUID=a34090d4-6bd6-45ea-8e76-8aaad107fb24 ro quiet Build Date: 16 February 2010 10:23:38AM xorg-server 2:1.7.5-1 (bui...@brahms.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: Mon Mar 8 23:42:55 2010 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Screen 0" (0) (**) | |-->Monitor "LVDS" (**) | |-->Device "ATI Radeon Xpress 200M IGP" (==) 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/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to "/usr/lib/xorg/modules" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x7c1e20 (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:1:5:0) 1002:5955:103c:30a4 ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE) rev 0, Mem @ 0xc800/134217728, 0xc010/65536, I/O @ 0x9000/256, BIOS @ 0x/
Bug#556159: suggestion
I'm not very knowledgeable, but I've had my share of problems with ATI Xpress 200m rc410. My card is actually detected as: ATI Radeon xpress 200m PCIE 5955 by lspci In my case a fresh installed of Squeeze a few months back had none of the problems you're having, but I did get this error in xorg0.log you are getting: (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM [dri] Disabling DRI. This is easily solved now, by installing firmware-linux-nonfree, firmware-linux and libdrm-radeon1. DRI should work now and you won't need to disable it in the xorg.conf file. I doubt this is your only issue, but try it. In my case, this provides 2d and 3d accel fine, but I still get a blank screen upon waking up from suspend and hangs before going into hibernation. Some xpress-200m-people have been able to solve "all" their radeon problems by using newer kernel from sid or experimental + Kernel modesetting: try getting the newer radeon driver from sid (you'll need a newer kernel as well, either 2.6.32-10 from sid or 2.6.33 from experimental). For this you will need to enable Kernel modesetting. add *radeon* to /etc/modules and put *options radeon modeset=1* in /etc/modprobe.d/radeon-kms.conf (you'll probably need to create the file). Report back when you can with your results Andres
Bug#523972: update
On 1 April 2010 16:27, Andres Cimmarusti wrote: > Hello Michal and Mark, > > @Mark: > > I don't know if this will help: Gnome tends to overrule your xrandr Not running Gnome here. > configuration (only in lenny, squeeze doesn't have this problem with the > computer I've tried). Try disabling gnome xrandr plugin. To do this, go to > gconf-editor, browse /apps/gnome-settings-daemon/plugins/xrandr and uncheck > the "active" entry (Important, you will have to place a file with an > appropiate xrandr initial configuration in /etc/X11/Xsession.d/ a sample is > given in the link below). > > You could also try a simpler xorg.conf. Try NO options for the external > monitor and set everything up in the xrandr conf file > > If you want more info, this helped me a great deal: > http://www.jejik.com/articles/2008/10/setting_up_dual_monitors_system-wide_with_xrandr_on_debian_lenny/ > > @Michal: > > Is this still a problem with the newer radeon driver from squeeze? If so, > could you try getting the even newer one from sid (you'll need a newer > kernel as well, either 2.6.32-10 from sid or 2.6.33-1 from experimental). I am no longer using the card. I got an older one which has support for acceleration and thus screen rotation. > For this you will need to enable Kernel modesetting. add radeon to > /etc/modules and put options radeon modeset=1 in > /etc/modprobe.d/radeon-kms.conf (you'll probably need to create the file). > You don't really need modesetting, even with these newer drivers. Actually it usually causes more trouble than it solves on Radeon with the current drivers and kernels in Debian but YMMV. The collection of bugs you get with KMS is certainly different from the one you get with UMS. Thanks Michal -- 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/v2ua5d587fb1004010857ka12906f6k7ef010e61462b...@mail.gmail.com
Bug#576211: xserver-xorg-input-synaptics: ValuatorAxis limits are set from device limits
Package: xserver-xorg-input-synaptics Version: 1.2.1-1 Severity: important Tags: upstream patch Hello, the synaptics driver set the ValuatorAxis limits to the device limits (like an absolute axis device - synaptics driver sends relative events) and the X pointer position can obtain only discrete values. The cursor moves by stairs. Example: X-resolution: 1920 Touchpad: x-axis range 32 - 544 Only every 1920 / (544 - 32) = 3.75 column can be hit Next simple patch disables setup of the ValuatorAxis limits and after applying the patch the cursor moves smoothly with a pixel precision. Regards, Tibor Zenis --- xserver-xorg-input-synaptics-1.2.1/src/synaptics.c 2010-04-01 16:32:13.0 +0200 +++ xserver-xorg-input-synaptics-1.2.1_fix/src/synaptics.c 2010-04-01 16:17:47.0 +0200 @@ -922,7 +922,8 @@ DeviceInit(DeviceIntPtr dev) #if GET_ABI_MAJOR(ABI_XINPUT_VERSION) >= 7 axes_labels[0], #endif -min, max, priv->resx * 1000, 0, priv->resx * 1000); +//min, max, priv->resx * 1000, 0, priv->resx * 1000); +-1, -1, 1, 0, 1); xf86InitValuatorDefaults(dev, 0); /* Y valuator */ @@ -940,7 +941,8 @@ DeviceInit(DeviceIntPtr dev) #if GET_ABI_MAJOR(ABI_XINPUT_VERSION) >= 7 axes_labels[1], #endif -min, max, priv->resy * 1000, 0, priv->resy * 1000); +//min, max, priv->resy * 1000, 0, priv->resy * 1000); +-1, -1, 1, 0, 1); xf86InitValuatorDefaults(dev, 1); #if GET_ABI_MAJOR(ABI_XINPUT_VERSION) == 0 -- 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 Aug 29 2009 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1866784 Mar 23 17:10 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M] /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 5257 Apr 1 16:26 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/xorg.conf (xorg 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 /etc/X11/xorg.conf manual page. # (Type "man /etc/X11/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 "Files" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/share/fonts/X11/75dpi" # path to defoma fonts FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"type1" Load"v4l" Load"vbe" EndSection Section "ServerFlags" Option "HandleSpecialKeys" "Always" Option "DontZap""False" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" # Option "XkbLayout" "sk_tz" Option "XkbOptions" "ctrl:nocaps" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents""true" Option "Device""/dev/psaux" Option "Protocol" "auto-dev" # Option "HorizScrollDelta" "0" EndSection Section "InputDevice" Identifier "Touchpad" Driver "synaptics" Option "Device""/dev/input/mouse0" Option
Bug#551840: I have no problems with this card
I have an old Compaq laptop with this card: ATI Mobility Radeon 7500. I did a fresh Squeeze install about a couple of months ago. I experienced some problems with the radeon driver currently in squeeze (but I never got crashes), but upon switching to kernel 2.6.33+KMS everything went away. Please try this: Get the newer radeon driver from sid (you'll need a newer kernel as well, either 2.6.32-10 from sid or 2.6.33 from experimental). For this you will need to enable Kernel modesetting. add *radeon* to /etc/modules and put *options radeon modeset=1* in /etc/modprobe.d/radeon-kms.conf (you'll probably need to create the file). (NOTE: if not installed already, get libdrm-radeon1, firmware-linux-nonfree and relevant mesa packages). Report back! Andres
Bug#552324: is this still a problem?
David, I have the same problem with my video card (also based on RC410). It doesn't wake up from suspend/hibernate. However, some people have been able to make it work: Is this still a problem with the newer radeon driver from squeeze? If so, could you try getting the even newer one from sid (you'll need a newer kernel as well, either 2.6.32-10 from sid or 2.6.33 from experimental). For this you will need to enable Kernel modesetting. add *radeon* to /etc/modules and put *options radeon modeset=1* in /etc/modprobe.d/radeon-kms.conf (you'll probably need to create the file). Let me know, so we can send this upstream Similar bugs: 573118 Andres
Bug#546609: is this still a problem?
Hi Boris, Is this still a problem with the newer radeon driver from squeeze? If so, could you try getting the even newer one from sid (you'll need a newer kernel as well, either 2.6.32-10 from sid or 2.6.33-1 from experimental). For this you will need to enable Kernel modesetting. add *radeon* to /etc/modules and put *options radeon modeset=1* in /etc/modprobe.d/radeon-kms.conf (you'll probably need to create the file). Let us know, Andres
Bug#523972: update
Hello Michal and Mark, @Mark: I don't know if this will help: Gnome tends to overrule your xrandr configuration (only in lenny, squeeze doesn't have this problem with the computer I've tried). Try disabling gnome xrandr plugin. To do this, go to gconf-editor, browse /apps/gnome-settings-daemon/plugins/xrandr and uncheck the "active" entry (Important, you will have to place a file with an appropiate xrandr initial configuration in /etc/X11/Xsession.d/ a sample is given in the link below). You could also try a simpler xorg.conf. Try NO options for the external monitor and set everything up in the xrandr conf file If you want more info, this helped me a great deal: http://www.jejik.com/articles/2008/10/setting_up_dual_monitors_system-wide_with_xrandr_on_debian_lenny/ @Michal: Is this still a problem with the newer radeon driver from squeeze? If so, could you try getting the even newer one from sid (you'll need a newer kernel as well, either 2.6.32-10 from sid or 2.6.33-1 from experimental). For this you will need to enable Kernel modesetting. add *radeon* to /etc/modules and put *options radeon modeset=1* in /etc/modprobe.d/radeon-kms.conf (you'll probably need to create the file). Let me know if these things work out for you guys. We need to help debian X clean up de RC bugs! Andres
xserver-xorg-input-synaptics: Changes to 'debian-unstable'
debian/changelog |6 ++ debian/local/10-synaptics.conf |1 + 2 files changed, 7 insertions(+) New commits: commit b063ef38cdc976fdc09eda4b79084b60a97c1a06 Author: Timo Aaltonen Date: Thu Apr 1 14:40:47 2010 +0300 10-synaptics.conf: Use 'MatchDevicePath "/dev/input/event*"'. diff --git a/debian/changelog b/debian/changelog index ba9f6f3..337a1ab 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +xserver-xorg-input-synaptics (1.2.2-2) UNRELEASED; urgency=low + + * 10-synaptics.conf: Use 'MatchDevicePath "/dev/input/event*"'. + + -- Timo Aaltonen Thu, 01 Apr 2010 14:40:18 +0300 + xserver-xorg-input-synaptics (1.2.2-1) unstable; urgency=low [ Timo Aaltonen ] diff --git a/debian/local/10-synaptics.conf b/debian/local/10-synaptics.conf index 22949b3..fb22e7d 100644 --- a/debian/local/10-synaptics.conf +++ b/debian/local/10-synaptics.conf @@ -1,5 +1,6 @@ Section "InputClass" Identifier "touchpad catchall" MatchIsTouchpad "on" + MatchDevicePath "/dev/input/event*" Driver "synaptics" EndSection -- 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/e1nxilt-00078s...@alioth.debian.org
xserver-xorg-input-synaptics: Changes to 'ubuntu'
debian/changelog |6 ++ debian/local/10-synaptics.conf |3 +++ 2 files changed, 9 insertions(+) New commits: commit 1d7ad94a394e96312fc38a9b3d2eddbf15e41760 Author: Timo Aaltonen Date: Thu Apr 1 14:34:31 2010 +0300 Release 1.2.2-1ubuntu2 diff --git a/debian/changelog b/debian/changelog index f868f77..2bddd31 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,8 @@ -xserver-xorg-input-synaptics (1.2.2-1ubuntu2) UNRELEASED; urgency=low +xserver-xorg-input-synaptics (1.2.2-1ubuntu2) lucid; urgency=low * 10-synaptics.conf: Use 'MatchDevicePath "/dev/input/event*"'. - -- Timo Aaltonen Thu, 01 Apr 2010 14:30:29 +0300 + -- Timo Aaltonen Thu, 01 Apr 2010 14:34:20 +0300 xserver-xorg-input-synaptics (1.2.2-1ubuntu1) lucid; urgency=low commit 3e42b144eceb69c5fd11cad0d4941150770552e6 Author: Timo Aaltonen Date: Thu Apr 1 14:31:15 2010 +0300 10-synaptics.conf: Use 'MatchDevicePath "/dev/input/event*"'. diff --git a/debian/changelog b/debian/changelog index cc71bf4..f868f77 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +xserver-xorg-input-synaptics (1.2.2-1ubuntu2) UNRELEASED; urgency=low + + * 10-synaptics.conf: Use 'MatchDevicePath "/dev/input/event*"'. + + -- Timo Aaltonen Thu, 01 Apr 2010 14:30:29 +0300 + xserver-xorg-input-synaptics (1.2.2-1ubuntu1) lucid; urgency=low * Merge from Debian unstable. (LP: #546933) diff --git a/debian/local/10-synaptics.conf b/debian/local/10-synaptics.conf index c25f30f..bc2b898 100644 --- a/debian/local/10-synaptics.conf +++ b/debian/local/10-synaptics.conf @@ -1,12 +1,14 @@ Section "InputClass" Identifier "touchpad catchall" MatchIsTouchpad "on" + MatchDevicePath "/dev/input/event*" Driver "synaptics" EndSection Section "InputClass" Identifier "Dell Inspiron quirks" MatchTag "inspiron_1011|inspiron_1012" + MatchDevicePath "/dev/input/event*" Driver "synaptics" Option "JumpyCursorThreshold" "90" Option "AreaBottomEdge" "4100" @@ -15,6 +17,7 @@ EndSection Section "InputClass" Identifier "HP Mininote quirks" MatchTag "mininote_1000" + MatchDevicePath "/dev/input/event*" Driver "synaptics" Option "JumpyCursorThreshold" "20" EndSection -- 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/e1nxikc-0006oh...@alioth.debian.org
xorg: Changes to 'ubuntu'
debian/changelog | 29 + debian/control |2 +- debian/local/Xreset | 34 ++ debian/local/Xreset.d/README |4 debian/rules |2 ++ debian/x11-common.dirs |1 + debian/x11-common.install|2 ++ 7 files changed, 73 insertions(+), 1 deletion(-) New commits: commit 423b289052524eccf2d4d973cbc0984ad4149dd8 Author: Timo Aaltonen Date: Thu Apr 1 14:32:26 2010 +0300 Release 1:7.5+5ubuntu1 diff --git a/debian/changelog b/debian/changelog index fb64239..cb93002 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +xorg (1:7.5+5ubuntu1) lucid; urgency=low + + * Merge from Debian unstable. + + -- Timo Aaltonen Thu, 01 Apr 2010 14:27:16 +0300 + xorg (1:7.5+5) unstable; urgency=low * Fix typo in Xsession.d/50x11-common_determine-startup, closes: #573899. commit b93b220a340ec41e36eb9a4d6a5f7c9fad8aa621 Author: Brice Goglin Date: Sun Mar 14 22:45:14 2010 +0100 Prepare changelog for upload diff --git a/debian/changelog b/debian/changelog index beed34f..54fab9e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,9 +1,9 @@ -xorg (1:7.5+5) UNRELEASED; urgency=low +xorg (1:7.5+5) unstable; urgency=low * Fix typo in Xsession.d/50x11-common_determine-startup, closes: #573899. * Bump Standards-Version to 3.8.4, no changes needed. - -- Brice Goglin Sun, 14 Mar 2010 22:41:20 +0100 + -- Brice Goglin Sun, 14 Mar 2010 22:45:09 +0100 xorg (1:7.5+4) unstable; urgency=low commit f07e8e0de64aaf4916b7b32c0dd8eafe8b82cf8d Author: Brice Goglin Date: Sun Mar 14 22:48:17 2010 +0100 Bump Standards-Version to 3.8.4 diff --git a/debian/changelog b/debian/changelog index 59e409d..beed34f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,6 +1,7 @@ xorg (1:7.5+5) UNRELEASED; urgency=low * Fix typo in Xsession.d/50x11-common_determine-startup, closes: #573899. + * Bump Standards-Version to 3.8.4, no changes needed. -- Brice Goglin Sun, 14 Mar 2010 22:41:20 +0100 diff --git a/debian/control b/debian/control index 3d22056..731c839 100644 --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Section: x11 Priority: optional Maintainer: Debian X Strike Force Uploaders: David Nusinow , Drew Parsons , Brice Goglin -Standards-Version: 3.8.3 +Standards-Version: 3.8.4 Build-Depends: dpkg (>= 1.7.0), po-debconf, debhelper (>= 7) Package: x11-common commit 094b3111bf3374dca6f364dd213941b79d91800b Author: Brice Goglin Date: Sun Mar 14 22:43:46 2010 +0100 Fix typo in Xsession.d/50x11-common_determine-startup diff --git a/debian/changelog b/debian/changelog index 7a58436..59e409d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +xorg (1:7.5+5) UNRELEASED; urgency=low + + * Fix typo in Xsession.d/50x11-common_determine-startup, closes: #573899. + + -- Brice Goglin Sun, 14 Mar 2010 22:41:20 +0100 + xorg (1:7.5+4) unstable; urgency=low * Add Xreset and Xreset.d support, closes: #230422. diff --git a/debian/local/Xsession.d/50x11-common_determine-startup b/debian/local/Xsession.d/50x11-common_determine-startup index 4ed7a32..cd9e4d3 100644 --- a/debian/local/Xsession.d/50x11-common_determine-startup +++ b/debian/local/Xsession.d/50x11-common_determine-startup @@ -7,7 +7,7 @@ # executable, fall back to looking for a user's custom X session script, if # allowed by the options file. if [ -z "$STARTUP" ]; then - if has_option allow-user-session; then + if has_option allow-user-xsession; then for STARTUPFILE in "$USERXSESSION" "$ALTUSERXSESSION"; do if [ -e "$STARTUPFILE" ]; then if [ -x "$STARTUPFILE" ]; then @@ -36,7 +36,7 @@ fi # If we still have not found a startup program, give up. if [ -z "$STARTUP" ]; then ERRMSG="unable to start X session ---" - if has_option allow-user-session; then + if has_option allow-user-xsession; then ERRMSG="$ERRMSG no \"$USERXSESSION\" file, no \"$ALTUSERXSESSION\" file," fi errormsg "$ERRMSG no session managers, no window managers, and no terminal" \ commit c3a8249d58deeba4b9d163a768e792a1d044ce8b Author: Brice Goglin Date: Sun Mar 14 11:15:20 2010 +0100 Prepare changelog for upload diff --git a/debian/changelog b/debian/changelog index 442a8d6..7a58436 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -xorg (1:7.5+4) UNRELEASED; urgency=low +xorg (1:7.5+4) unstable; urgency=low * Add Xreset and Xreset.d support, closes: #230422. * Improve startup speed of Xsession.d scripts by eliminating all unnecessary @@ -12,7 +12,7 @@ xorg (1:7.5+4) UNRELEASED; urgency=low unlikely (like "~/.Xresources exists") outside, to avoid running the other tests (like "xrdb exists") on systems which don't use Xresources. - -- Brice Goglin Sat, 06 Mar 2010 16:15:01 +0100 + -- Brice Goglin Sun, 14 Mar 2010 11:15:07 +0100 xorg (1:7.5+3) unstable; urgency=low
mesa: Changes to 'ubuntu'
ChangeLog | 495 ++ Makefile |2 debian/changelog | 17 debian/control|4 docs/news.html|9 docs/relnotes-7.7.1.html | 24 src/gallium/auxiliary/util/u_debug.c | 51 + src/gallium/drivers/softpipe/sp_tile_cache.c |7 src/gallium/drivers/svga/svga_context.c |5 src/gallium/drivers/svga/svga_state_rss.c | 13 src/gallium/drivers/svga/svga_winsys.h|3 src/gallium/state_trackers/dri/dri_screen.c | 91 +-- src/gallium/state_trackers/xorg/xorg_crtc.c | 24 src/gallium/state_trackers/xorg/xorg_dri2.c | 14 src/gallium/state_trackers/xorg/xorg_driver.c | 94 ++- src/gallium/state_trackers/xorg/xorg_exa.c|3 src/gallium/state_trackers/xorg/xorg_renderer.c |2 src/gallium/state_trackers/xorg/xorg_renderer.h |2 src/gallium/state_trackers/xorg/xorg_tracker.h| 13 src/gallium/state_trackers/xorg/xorg_xv.c | 14 src/gallium/winsys/drm/vmware/core/vmw_context.c | 20 src/gallium/winsys/drm/vmware/core/vmw_context.h |3 src/gallium/winsys/drm/vmware/core/vmw_screen.c | 10 src/gallium/winsys/drm/vmware/core/vmw_screen.h | 12 src/gallium/winsys/drm/vmware/core/vmw_screen_dri.c |2 src/gallium/winsys/drm/vmware/core/vmw_screen_ioctl.c |6 src/gallium/winsys/drm/vmware/xorg/vmw_screen.c | 46 + src/glx/x11/glx_pbuffer.c |3 src/glx/x11/indirect_vertex_array.c |3 src/mesa/drivers/dri/i915/intel_tris.c|4 src/mesa/drivers/dri/intel/intel_reg.h|4 src/mesa/drivers/dri/r200/r200_cmdbuf.c |3 src/mesa/drivers/dri/r200/r200_tcl.c | 56 +- src/mesa/drivers/dri/r300/r300_state.c| 21 src/mesa/drivers/dri/r600/r600_context.c |9 src/mesa/drivers/dri/r600/r600_texstate.c | 28 - src/mesa/drivers/dri/r600/r700_render.c | 18 src/mesa/drivers/dri/r600/r700_state.c|6 src/mesa/drivers/dri/radeon/radeon_chipset.h |1 src/mesa/drivers/dri/radeon/radeon_screen.c |1 src/mesa/drivers/dri/swrast/swrast_span.c |2 src/mesa/drivers/dri/swrast/swrast_spantemp.h | 17 src/mesa/main/extensions.c| 15 src/mesa/main/hash.c | 36 - src/mesa/main/renderbuffer.c |3 src/mesa/main/texrender.c |5 src/mesa/main/version.h |2 src/mesa/state_tracker/st_cb_drawpixels.c | 29 - src/mesa/state_tracker/st_cb_fbo.c|5 src/mesa/state_tracker/st_cb_texture.c|2 src/mesa/state_tracker/st_framebuffer.c | 53 - src/mesa/state_tracker/st_public.h|3 src/mesa/vbo/vbo_split_copy.c |2 53 files changed, 1059 insertions(+), 258 deletions(-) New commits: commit daf5b5aa08aa40cfd0951cc94d7743cf790b07f4 Author: Timo Aaltonen Date: Thu Apr 1 14:27:59 2010 +0300 Release 7.7.1-1ubuntu1. diff --git a/debian/changelog b/debian/changelog index 7f9982d..bb85f35 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,11 +1,11 @@ -mesa (7.7.1-1ubuntu1) UNRELEASED; urgency=low +mesa (7.7.1-1ubuntu1) lucid; urgency=low - [Alberto Milone] + [ Alberto Milone ] * debian/rules: pass --with-dri-searchpath=/usr/lib/dri:/usr/lib32/dri to confflags-dri on i386 so that /usr/lib32/dri is used for 32 bit compatibility on 64 bit systems (LP: #248392). - -- Alberto Milone Wed, 10 Mar 2010 13:26:38 +0100 + -- Timo Aaltonen Thu, 01 Apr 2010 13:31:09 +0300 mesa (7.7.1-1) unstable; urgency=low commit 8d98d7832011d7ba490cbc18247508469ce21ddb Author: Brice Goglin Date: Tue Mar 30 17:15:15 2010 +0200 Prepare changelog for upload diff --git a/debian/changelog b/debian/changelog index dad803e..e336418 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -mesa (7.7.1-1) UNRELEASED; urgency=low +mesa (7.7.1-1) unstable; urgency=low [ Brice Goglin ] * Remove Thierry Reding from Uploaders, closes: #572539. @@ -7,7 +7,7 @@ mesa (7.7.1-1) UNRELEASED; urgency=low [ Timo Aaltonen ] * New upstream release. - -- Brice Goglin Thu, 04 Mar 2010 20:51:29 +0100 + -- Brice Goglin Tue, 30 Mar 2010 17:15:09 +0200 mesa (7.7-4) unstable; urgency=low commit ce01e79d7bd1a13928cc7a2cf6cc8816c2c47695 Author: Brice Goglin Date: Tue Mar 30 17:14:41
Bug#472108: Similar but not identical here
I am getting this with 2.6.32-4-686-bigmem but not with 2.6.31-1-686-bigmem. I cannot get back to X with Alt-F7. I have to do a hard reset with the power button. -- Anthony Campbell - a...@acampbell.org.uk Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles) -- 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/20100401085923.ga2...@acampbell.org.uk
Bug#576183: Mouse sometimes erratically jumps around, locks X server, when crossing Xinerama edges
Package: xorg Version: 1:7.5+5 Severity: normal Recently, I've had to restart X sometimes several times per hour because I'd move the mouse across a Xinerama edge onto another screen, and it would get stuck there, erratically jumping back and forth between the screens. I could still move the mouse and influence the pointer a bit, but the system would be unusable. Keyboard input also seems to be affected. When this happens, the only remedy is kill -KILL of the Xorg process via SSH. A normal KILL will not work. I'll gladly try to help debug this if you tell me what to look for. Thanks, -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xorg depends on: ii libgl1-mesa-dri 7.7-4 A free implementation of the OpenG ii libgl1-mesa-glx [libgl1] 7.7-4 A free implementation of the OpenG ii libglu1-mesa 7.7-4 The OpenGL utility library (GLU) ii rxvt-unicode-ml [x-terminal-e 9.07-1 multi-lingual terminal emulator wi ii x11-apps 7.5+5 X applications ii x11-session-utils 7.5+1 X session utilities ii x11-utils 7.5+3 X11 utilities ii x11-xfs-utils 7.4+1 X font server utilities ii x11-xkb-utils 7.5+2 X11 XKB utilities ii x11-xserver-utils 7.5+1 X server utilities ii xauth 1:1.0.4-1 X authentication utility ii xfonts-100dpi 1:1.0.1100 dpi fonts for X ii xfonts-75dpi 1:1.0.175 dpi fonts for X ii xfonts-base 1:1.0.1standard fonts for X ii xfonts-scalable 1:1.0.1-1 scalable fonts for X ii xfonts-utils 1:7.5+2X Window System font utility progr ii xinit 1.2.0-1X server initialisation tool ii xkb-data 1.8-1 X Keyboard Extension (XKB) configu ii xorg-docs-core1:1.5-1Core documentation for the X.org X ii xserver-xorg 1:7.5+5the X.Org X server ii xterm [x-terminal-emulator] 256-1 X terminal emulator xorg recommends no packages. Versions of packages xorg suggests: pn xorg-docs (no description available) -- debconf-show failed -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#575966: 2.6.33 seems to be at fault
I can confirm that both these bugs seem to relate to 2.6.33. Booting 2.6.32 fix the Xvideo issue for me. I never had a problem with acceleration, but since KiBi pseudo-merged the bugs, I'll write to both. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Processed: Re: Bug#575681: xserver-xorg-video-radeon: shows severe artifacts since switching to KMS
Processing commands for cont...@bugs.debian.org: > reassign 575681 linux-2.6 Bug #575681 [xserver-xorg-video-radeon] xserver-xorg-video-radeon: shows severe artifacts since switching to KMS Bug reassigned from package 'xserver-xorg-video-radeon' to 'linux-2.6'. Bug No longer marked as found in versions xserver-xorg-video-ati/1:6.12.192-2. > kthxbye Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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/handler.s.c.127011166010154.transcr...@bugs.debian.org
Bug#570447: Acknowledgement (x11-common: Optimize speed of Xsession.d scripts)
Hello Julien, Julien Cristau [2010-03-14 12:04 +0100]: > > +- Use shell built in "type" instead of external "which" to test for > > + programs. > > There's no guarantee that /bin/sh has a 'type' built-in, as far as I can > tell from SUSv3 and policy). I'd suggest command -v, but apparently > posh doesn't like that either, so I don't know. Hm, it's present in dash and bash, anyway. But if you like command -V better, I'm fine with that. > > +- 30x11-common_xresources: Swap the order of tests to keep the most > > + unlikely (like "~/.Xresources exists") outside, to avoid running the > > + other tests (like "xrdb exists") on systems which don't use > > Xresources. > > + > > I'm not sure about this one. x11-common installs a file in > /etc/X11/Xresources, so you'll end up looking for xrdb on pretty much > every system regardless. Right, it's a minor case, if someone decides to remove /etc/X11/Xresources/x11-common. But I still think it's a tad less likely to be true than the existence of xrdb. > And then the reordering means you're looking for it twice (granted, > with 'type' the shell can cache the result of the first lookup, but > still). Hm, I don't understand? The second type is only done if [ -f "$USRRESOURCES" ], and ~/.Xresources should exist pretty seldomly these days? Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#575681: xserver-xorg-video-radeon: shows severe artifacts since switching to KMS
reassign 575681 linux-2.6
kthxbye
On Thu, 2010-04-01 at 09:32 +0200, Fabian Greffrath wrote:
> Am 31.03.2010 14:34, schrieb Michel Dänzer:
> > Not sure how it could be. Your symptoms are really weird. One thing I
> > wonder:
> > [6.093152] [drm] radeon: 2 quad pipes, 1 Z pipes initialized.
> > Maybe only one of your quad pipes is working properly? I think that
> > might explain the checkerboard pattern.
>
> Hm, no idea what this means. Is there anything I can do about it?
Looking at the Mesa code confirmed my suspicion, the attached kernel
patch should fix it. Reassigning to the kernel.
> > There's no mode switch if X and the console are using the same mode, but
> > that's probably not the case since you're using a custom modeline.
>
> I meant, maybe it is a "problem" that I have forced a different
> resolution in X than the one the kernel wants to set (and actually
> does in the VTs) via KMS.
I understood that and said this was unlikely: the artifacts looked to be
related to the rendering engine, and the display engine is generally
completely separate from that.
--
Earthling Michel Dänzer |http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
From ac8c8618c625039ec29870c2a9c36733695ecd56 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Michel=20D=C3=A4nzer?=
Date: Thu, 1 Apr 2010 10:18:09 +0200
Subject: [PATCH] drm/radeon: R300 AD only has one quad pipe.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Gleaned from the Mesa code.
Signed-off-by: Michel Dänzer
---
drivers/gpu/drm/radeon/r300.c |6 +++---
drivers/gpu/drm/radeon/radeon_cp.c | 10 ++
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/radeon/r300.c b/drivers/gpu/drm/radeon/r300.c
index 219d410..3dae012 100644
--- a/drivers/gpu/drm/radeon/r300.c
+++ b/drivers/gpu/drm/radeon/r300.c
@@ -327,12 +327,12 @@ void r300_gpu_init(struct radeon_device *rdev)
{
uint32_t gb_tile_config, tmp;
- /* FIXME: rv380 one pipes ? */
- if ((rdev->family == CHIP_R300) || (rdev->family == CHIP_R350)) {
+ if ((rdev->family == CHIP_R300 && rdev->pdev->device != 0x4144) ||
+ (rdev->family == CHIP_R350)) {
/* r300,r350 */
rdev->num_gb_pipes = 2;
} else {
- /* rv350,rv370,rv380 */
+ /* rv350,rv370,rv380,r300 AD */
rdev->num_gb_pipes = 1;
}
rdev->num_z_pipes = 1;
diff --git a/drivers/gpu/drm/radeon/radeon_cp.c b/drivers/gpu/drm/radeon/radeon_cp.c
index dc6eba6..419630d 100644
--- a/drivers/gpu/drm/radeon/radeon_cp.c
+++ b/drivers/gpu/drm/radeon/radeon_cp.c
@@ -417,8 +417,9 @@ static int radeon_do_wait_for_idle(drm_radeon_private_t * dev_priv)
return -EBUSY;
}
-static void radeon_init_pipes(drm_radeon_private_t *dev_priv)
+static void radeon_init_pipes(struct drm_device *dev)
{
+ drm_radeon_private_t *dev_priv = dev->dev_private;
uint32_t gb_tile_config, gb_pipe_sel = 0;
if ((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_RV530) {
@@ -436,11 +437,12 @@ static void radeon_init_pipes(drm_radeon_private_t *dev_priv)
dev_priv->num_gb_pipes = ((gb_pipe_sel >> 12) & 0x3) + 1;
} else {
/* R3xx */
- if (((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_R300) ||
+ if (((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_R300 &&
+ dev->pdev->device != 0x4144) ||
((dev_priv->flags & RADEON_FAMILY_MASK) == CHIP_R350)) {
dev_priv->num_gb_pipes = 2;
} else {
- /* R3Vxx */
+ /* RV3xx/R300 AD */
dev_priv->num_gb_pipes = 1;
}
}
@@ -736,7 +738,7 @@ static int radeon_do_engine_reset(struct drm_device * dev)
/* setup the raster pipes */
if ((dev_priv->flags & RADEON_FAMILY_MASK) >= CHIP_R300)
- radeon_init_pipes(dev_priv);
+ radeon_init_pipes(dev);
/* Reset the CP ring */
radeon_do_cp_reset(dev_priv);
--
1.7.0.3
Bug#575681: xserver-xorg-video-radeon: shows severe artifacts since switching to KMS
Am 31.03.2010 14:34, schrieb Michel Dänzer: Not sure how it could be. Your symptoms are really weird. One thing I wonder: [6.093152] [drm] radeon: 2 quad pipes, 1 Z pipes initialized. Maybe only one of your quad pipes is working properly? I think that might explain the checkerboard pattern. Hm, no idea what this means. Is there anything I can do about it? There's no mode switch if X and the console are using the same mode, but that's probably not the case since you're using a custom modeline. I meant, maybe it is a "problem" that I have forced a different resolution in X than the one the kernel wants to set (and actually does in the VTs) via KMS. - Fabian -- 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/4bb44bff.5090...@greffrath.com
