xorg-server: Changes to 'ubuntu'
debian/changelog |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit ec83b5b0fb9b646e4f0c7c98668935061f2b Author: Timo Aaltonen Date: Thu Mar 25 09:32:24 2010 +0200 Finalize the changelog. diff --git a/debian/changelog b/debian/changelog index d18b4b2..e1f84f9 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -xorg-server (2:1.7.6-1ubuntu1) UNRELEASED; urgency=low +xorg-server (2:1.7.6-1ubuntu1) lucid; urgency=low [Timo Aaltonen] * Merge from Debian unstable. -- 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/e1nuhyx-0003iw...@alioth.debian.org
Processed: retitle 575274 to xserver-xorg-video-radeon: Not fit for testing migration yet
Processing commands for cont...@bugs.debian.org: > retitle 575274 xserver-xorg-video-radeon: Not fit for testing migration yet Bug #575274 [xserver-xorg-video-radeon] xserver-xorg-video-radeon: not ready for testing yet Changed Bug title to 'xserver-xorg-video-radeon: Not fit for testing migration yet' from 'xserver-xorg-video-radeon: not ready for testing yet' > thanks 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.126950481824876.transcr...@bugs.debian.org
Bug#575287: Same here even with 2.6.32-4-amd64
On Don, 2010-03-25 at 03:15 +0100, Vedran Furač wrote: > Source: xserver-xorg-video-ati > Version: 1:6.12.192-2 > > Current Operating System: Linux antares 2.6.32-4-amd64 > (II) [KMS] drm report modesetting isn't supported. > (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version > mismatch. > [dri] This chipset requires a kernel module version of 1.17.0, > [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy > modesetting, upgrade your kernel. > [dri] If using kernel modesetting, make sure your module is > [dri] loaded prior to starting X, and that this driver was built > [dri] with support for KMS. > [dri] Disabling DRI. The above means that the X driver is using UMS whereas KMS is enabled in the kernel. This results in a conflict for hardware access and cannot work properly. It's usually caused by the radeon kernel module being loaded too late. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- 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/1269506863.441.2617.ca...@thor.local
xorg-server: Changes to 'ubuntu'
debian/changelog |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 7e36c6970756c82f4a9e417fca85eb2226caaa51 Author: Bryce Harrington Date: Thu Mar 25 01:40:11 2010 -0700 Finalize changelog diff --git a/debian/changelog b/debian/changelog index d18b4b2..4fa335c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -xorg-server (2:1.7.6-1ubuntu1) UNRELEASED; urgency=low +xorg-server (2:1.7.6-1ubuntu1) lucid; urgency=low [Timo Aaltonen] * Merge from Debian unstable. @@ -13,7 +13,7 @@ xorg-server (2:1.7.6-1ubuntu1) UNRELEASED; urgency=low (LP: #401045) * Renumber patch 201_armel-drv-fallbacks.patch to 111 - -- Bryce Harrington Wed, 24 Mar 2010 11:47:58 -0700 + -- Bryce Harrington Wed, 24 Mar 2010 12:04:20 -0700 xorg-server (2:1.7.6-1) unstable; urgency=low -- 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/e1nuich-0002ft...@alioth.debian.org
Bug#575287: Same here even with 2.6.32-4-amd64
On Thu, Mar 25, 2010 at 09:47:43 +0100, Michel Dänzer wrote: > The above means that the X driver is using UMS whereas KMS is enabled in > the kernel. This results in a conflict for hardware access and cannot > work properly. > > It's usually caused by the radeon kernel module being loaded too late. > With the latest sid kernel udev should load the module on boot. dmesg would give a clue as to why that didn't happen here. Cheers, Julien signature.asc Description: Digital signature
Bug#575287: Same here even with 2.6.32-4-amd64
On Thu, Mar 25, 2010 at 11:21:45 +0100, Xavier Bestel wrote: > On Thu, 2010-03-25 at 10:53 +0100, Julien Cristau wrote: > > On Thu, Mar 25, 2010 at 09:47:43 +0100, Michel Dänzer wrote: > > > > > The above means that the X driver is using UMS whereas KMS is enabled in > > > the kernel. This results in a conflict for hardware access and cannot > > > work properly. > > > > > > It's usually caused by the radeon kernel module being loaded too late. > > > > > With the latest sid kernel udev should load the module on boot. dmesg > > would give a clue as to why that didn't happen here. > > If you mean loading in the initrd, I think there's still a bug with the > firmware not being present. > I don't. Cheers, Julien signature.asc Description: Digital signature
Bug#575287: Same here even with 2.6.32-4-amd64
On Thu, 2010-03-25 at 10:53 +0100, Julien Cristau wrote: > On Thu, Mar 25, 2010 at 09:47:43 +0100, Michel Dänzer wrote: > > > The above means that the X driver is using UMS whereas KMS is enabled in > > the kernel. This results in a conflict for hardware access and cannot > > work properly. > > > > It's usually caused by the radeon kernel module being loaded too late. > > > With the latest sid kernel udev should load the module on boot. dmesg > would give a clue as to why that didn't happen here. If you mean loading in the initrd, I think there's still a bug with the firmware not being present. Xav -- 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/1269512505.24334.143.ca...@skunk
Re: Backported features from xserver 1.8
Ok, since this made the headlines on Phoronix I should probably correct some misconceptions and explain a bit more to the greater public. First of all, backporting xorg.conf.d/inputclass was discussed already in December when the support was merged upstream. I backported these then and tried them out, and it worked fine. I think the only blocker, as Debian is concerned, was that the video driver autoconfig fallbacks had never worked when there was an xorg.conf present, and with xorg.conf.d config snippets, that condition would've always been true. The new patch from SUSE seems to fix that, so the blocker is gone (and release blockers remain ;). Debian & Ubuntu have shipped an older version of the udev support patch-set by Julien Cristau for months now. The main diff versus the upstream version is that the vendor/driver matching is done by udev rules and not by xorg.conf.d config snippets as in 1.8 (where udev config is ignored). So the way how the input drivers are loaded has not been changed here, only the mechanism of telling the xserver about the drivers (and which is already used by Fedora 13 and openSUSE, possibly others). There's more to 1.8 than just these features. Here's the diffstat of only these patches applied on top of 1.7.6: Xi/stubs.c |3 config/Makefile.am | 20 + config/config-backends.h | 21 + config/config.c | 77 +++ config/dbus.c|2 config/hal.c | 97 +++-- configure.ac | 27 ++ cpprules.in |3 hw/dmx/dmxinput.c|3 hw/kdrive/src/kinput.c | 11 - hw/xfree86/common/xf86AutoConfig.c | 79 --- hw/xfree86/common/xf86Config.c | 172 +++- hw/xfree86/common/xf86Globals.c |3 hw/xfree86/common/xf86Init.c | 15 + hw/xfree86/common/xf86Option.c | 25 -- hw/xfree86/common/xf86Priv.h |1 hw/xfree86/common/xf86Xinput.c | 223 +++-- hw/xfree86/doc/man/Xorg.man.pre | 34 ++- hw/xfree86/doc/man/xorg.conf.man.pre | 196 +- hw/xfree86/parser/Configint.h|2 hw/xfree86/parser/Layout.c | 79 +-- hw/xfree86/parser/Makefile.am|1 hw/xfree86/parser/configProcs.h |4 hw/xfree86/parser/read.c |8 hw/xfree86/parser/scan.c | 370 ++- hw/xfree86/parser/write.c|2 hw/xfree86/parser/xf86Parser.h | 48 +++- hw/xfree86/parser/xf86tokens.h | 14 + hw/xquartz/darwinXinput.c|3 hw/xwin/InitOutput.c |3 hw/xwin/winconfig.c | 40 +++ hw/xwin/winconfig.h |1 hw/xwin/winprocarg.c | 18 + include/dix-config.h.in |6 include/input.h | 17 + include/misc.h |3 include/xorg-config.h.in |3 os/utils.c | 40 +++ 39 files changed, 1348 insertions(+), 344 deletions(-) the libudev change alone is 415 insertions, 81 deletions - roughly a third of the total, and something we already had. Compare that to the diff between 1.7.6 and 1.7.99.902 (diff'ing the git tags): 608 files changed, 12060 insertions(+), 56398 deletions(-) So it's not like there's nothing else in 1.8 ;) The backport was not hard to create, it's just a bunch of commits on top of each other. The tagging support needed one cleanup commit, so it's included to minimize the diff and effort. The only real change was to not bump the input ABI in the inputclass diff just because of the wacom driver - the driver only needs to drop the check for the new ABI (and build-depend on the new headers). TTBOMK, there are no other input drivers needing the same. Here's the full list of the backported patches with a short description of what it does: config-xorg-conf-d.diff "Merge dbn/xorg.conf.d" inputclass-sans-abi9.diff "Merge dbn/inputclass" config-libudev-backend.diff "config: add libudev config backend" config-dont-filter-input-subsys.diffudeb backend fix (already in D/U) xfree86-move-sanitycheck.diff inputclass fix xfree86-init-pointer-feedback.diff more pointer accel defaults xfree86-replace-true-false.diff xkb cleanup for the tagging support xfree86-make-docs-match-reality.diffIgnore and tagging support 1/7 xfree86-handle-files-without-newline.diff 2/7 xfree86-add-ignore-option.diff 3/7 xfree86-allow-multiple-args.diff4/7 xfree86-set-fnmatch-pathname-flag.diff 5/7 add-xstrtokenize-to-the-dix.diff6/7 add-tag-matching-to-attrs.diff 7/7 xfree86-reorder-option-priorities.diff fixes config priority o
Bug#575391: xserver-xorg-video-intel: Xorg crash and GPU lockup with 2.6.33 KMS
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 (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 8 (--) PCI:*(0:0:2:0) 8086:27a2:1028:01bd Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xeff0/524288, 0xd000/268435456, 0xefec/262144, I/O @ 0xeff8/8 (--) PCI: (0:0:2:1) 8086:27a6:1028:01bd Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xeff8/524288 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.7.5, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loa
Bug#568168: xserver-xorg-video-nouveau needs nouveau bits from libdrm
On 2010-03-24 02:53 +0100, Cyril Brulebois wrote: > Sven Joachim (23/03/2010): >> I have some good news, since (after fixing #568162) I indeed managed >> to build a working package. At least X has been running for about >> two hours which is a promising start. :-) > > I'd like to echo Julien's thanks. BTW: Do you plan to maintain nouveau > on a regular basis or is that just a one-time shot? Well, I have not quite made up my mind about it, which you can probably understand when I tell you that Wednesday was the first time I have ever _used_ nouveau. My overall impression is quite good, but there are some things that are mid-term obstacles: - I like to run upstream kernels and do in general not use or even install Debian kernels. While I will test the latest sid kernel in the next days, my primary kernel for the next 2-3 months will be 2.6.33.x. And then… - …The recent big ABI break in libdrm 2.4.18 (to be reverted in the Debian 2.4.18-4 version) and Linux 2.6.34 make it impossible¹ to run anything newer than 2.6.33 with the xserver-xorg-video-nouveau package that's intended for Squeeze. Being stuck with an unsupported 2.6.33 or the Debian 2.6.32 kernel for the next 9-12 months is not a very appealing prospect to me. > I'm currently > wondering whether to order some hardware to make sure I have some > boards to reproduce user-reported issues, and to check for regressions > when packaging new versions, but I might skip nvidia stuff if you're > going to work on it. :) I will happily test new versions, as long as they work with a kernel that is supported upstream, including -rcx kernels with x >= 2. Which means that there needs to be a libdrm version in experimental that works with 2.6.34 (or 2.6.35-rcx) when 2.6.33 support ends upstream. I would be happy to help packaging that, too. As far as the current nouveau version is concerned, I cannot support it until the Squeeze release, much less beyond that. It is also going to break on partial upgrades, as the only kernel that is going to work with it is the Debian Squeeze kernel. IMO it still belongs in experimental because of the reckless ABI breaks, despite Fedora and Ubuntu releasing with it. The only remedy for that would be if the Debian kernel team could pull nouveau drm from 2.6.34 rather than 2.6.33. They are probably not going to do that, but I'd have a good argument for it. The 2.6.33 nouveau module needs non-free firmware blobs called ctxprogs to initialize the GPU. It works without them, but there won't be any acceleration then. In 2.6.34, the driver has code to do that itself, so the firmware is no longer necessary. Of course, as long as nouveau is in staging, there is no guarantee that there won't be another flag day that requires users to upgrade the kernel, libdrm, mesa and what not in lock-step. >> I think I don't want to trample over any of your existing branches >> yet, so I would prefer to use a new branch, or publish my work on my >> joachim-guest account on Alioth where you can pull from at your >> leisure. > > Feel free to publish it there as a first step, so that other folks can > have a look at it. :) Available here: git://git.debian.org/users/joachim-guest/xserver-xorg-video-nouveau.git http://git.debian.org/?p=users/joachim-guest/xserver-xorg-video-nouveau.git Cheers, Sven ¹ http://lwn.net/Articles/377953/ -- I think the real problem was that Fedora and the Neauveu community are acting incredibly selfishly. They only care about their narrow point of view, and don't care about the pain they are inflicting on the kernel development process and other kernel developers. This is _legal_. It is, however, anti-social. -- Theodore Ts'o -- 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/87fx3oo2hf@turtle.gmx.de
Bug#568168: xserver-xorg-video-nouveau needs nouveau bits from libdrm
On 2010-03-24 09:20 +0100, Julien Cristau wrote: > On Tue, Mar 23, 2010 at 22:19:20 +0100, Sven Joachim wrote: > >> I'm not sure how to do the merge. While merging upstream-ubuntu into >> upstream-experimental is a trivial fast-forward, and merging >> upstream-experimental into debian-experimental is also a no-brainer, >> merging ubuntu into debian-experimental resulted in quite a few things >> that needed to be backed out; for instance their patch 02_nouveau_bgnr >> leads to FTBFS on Debian, and I'm not sure you want all the Ubuntu >> history in debian/changelog either. >> >> So it might be better to "merge --squash" that branch, since otherwise >> we might create problems for Ubuntu (in their later merges) if we revert >> many of their actions. What do you think? >> > I think I'd just apply the relevant parts of the ubuntu diff manually > instead of doing it as a git merge. Hopefully that won't be too hard to > extract, and that way we don't import the unrelated changes you mention. > merge --squash and revert the changes we don't want before committing > looks like would do that (I didn't know about merge --squash, thanks for > the pointer!). I've done that, cherry-picking one of their commits (xsfbs update) before squash-merging. What was left after reverting were basically only changes to debian/control, I split these into several commits. The results can be seen here: git://git.debian.org/users/joachim-guest/xserver-xorg-video-nouveau.git http://git.debian.org/?p=users/joachim-guest/xserver-xorg-video-nouveau.git There are some rough edges left: - We need something like Ubuntu's 01_include_snapshot_date patch to ensure that NV_DRIVER_DATE is set to something meaningful when building outside the Git repository. NV_DRIVER_DATE is only used to print the driver date into Xorg's log file, so setting it to the empty string is not the end of the world, but still not nice. - Shipping an upstream changelog would be useful (could probably be achieved with a suitable invocation of "git log"). - There are 132 warnings from dpkg-shlibdeps about unresolvable references in nouveau_drv.so. But overall, the package already works quite okay. I have yet to test it with a Debian kernel, though (running self-compiled 2.6.33.1 ATM). Sven -- 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/87pr2so2p7@turtle.gmx.de
Processed: Re: Bug#567328: xserver-xorg-video-radeon: rendering duplication across dual-head setup
Processing commands for cont...@bugs.debian.org: > found 567328 1:6.12.6-1 Bug #567328 [xserver-xorg-video-radeon] xserver-xorg-video-radeon: rendering duplication across dual-head setup Bug Marked as found in versions xserver-xorg-video-ati/1:6.12.6-1. > found 567328 1:6.12.192-2 Bug #567328 [xserver-xorg-video-radeon] xserver-xorg-video-radeon: rendering duplication across dual-head setup Bug Marked as found in versions xserver-xorg-video-ati/1:6.12.192-2. > thanks 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.126953256422188.transcr...@bugs.debian.org
Bug#575415: xserver-xorg-video-r128: DRI Not available on G3 12" iBook (PPC)
Package: xserver-xorg-video-r128 Version: 6.8.0-1 Severity: important A fresh install of Debian Testing PPC generates a number of xorg issues. This one: there's no accelleration at all. DRI is loaded, but driconf returns the card does not support DRI. Result is a painfully slow desktop experience. -- 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 5 2009 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1718548 Feb 19 2009 /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 M7 LW [Radeon Mobility 7500] /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1612 Feb 23 22:32 /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" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" Driver "radeon" Option "DRI" "on" Option "DMAForXv" "true" Option "EnablePageFlip" "true" Option "AGPMode" "4" # Option "AccelMethod" "EXA" Option "DynamicClocks" "on" Option "DirectRendering" "on" Option "XAANoOffscreenPixmaps" "true" Option "AGPFastWrite" "true" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection Section "Module" Load "dri" Load "glx" Load "dbe" Load "extmod" Load "int10" Load "ddc" Load "v4l" EndSection Section "DRI" Mode 0666 EndSection Section "Extensions" Option "Composite" "1" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 44194 Mar 20 09:22 /var/log/Xorg.1.log -rw-r--r-- 1 root root 49419 Mar 25 09:38 /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-11) Current Operating System: Linux laptop 2.6.26-2-686 #1 SMP Sun Jun 21 04:57:38 UTC 2009 i686 Build Date: 20 February 2009 03:06:29AM 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: Thu Mar 25 09:37:32 2010 (==) 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/x
Bug#575415: xserver-xorg-video-r128: DRI Not available on G3 12" iBook (PPC)
On Thu, 2010-03-25 at 09:56 -0700, mpapet wrote: > Package: xserver-xorg-video-r128 > Version: 6.8.0-1 > Severity: important > > A fresh install of Debian Testing PPC generates a number of xorg issues. > > This one: there's no accelleration at all. DRI is loaded, > but driconf returns the card does not support DRI. > > Result is a painfully slow desktop experience. The X log file shows the radeon driver successfully initializing the DRI. If you're really having issues with the r128 driver on another machine, please provide the corresponding log file. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- 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/1269538100.4395.117.ca...@thor.local
Bug#575416: Default xorg on G3 12" iBook (Testing install) is broken
Package: xserver-xorg-video-r128
Version: 6.8.0-1
Severity: important
*** Please type your report below this line ***
A fresh install of Debian Testing PPC generates a number of xorg issues.
This one: an xorg.conf file is required. ('Xorg -configure' creates one)
The LCD panel on an iBook is not detected correctly. Result is a crazy-looking
display that isn't drawn right at all.
Section "Monitor" *requires* at minimum
HorizSync 30-82
VertRefresh 56-75
To get the display to fill the LCD correctly. Web searches suggest modeline
entries might do the same thing.
-- 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 5 2009 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1718548 Feb 19 2009 /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 M7 LW
[Radeon Mobility 7500]
/var/lib/x11/xorg.conf.md5sum does not exist.
Xorg X server configuration file status:
-rw-r--r-- 1 root root 1612 Feb 23 22:32 /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" "pc104"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
EndSection
Section "Device"
Identifier "Configured Video Device"
Driver "radeon"
Option "DRI" "on"
Option "DMAForXv" "true"
Option "EnablePageFlip" "true"
Option "AGPMode" "4"
# Option "AccelMethod" "EXA"
Option "DynamicClocks" "on"
Option "DirectRendering" "on"
Option "XAANoOffscreenPixmaps" "true"
Option "AGPFastWrite" "true"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
EndSection
Section "Module"
Load "dri"
Load "glx"
Load "dbe"
Load "extmod"
Load "int10"
Load "ddc"
Load "v4l"
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "1"
EndSection
Xorg X server log files on system:
-rw-r--r-- 1 root root 44194 Mar 20 09:22 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 49419 Mar 25 09:38 /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-11)
Current Operating System: Linux laptop 2.6.26-2-686 #1 SMP Sun Jun 21 04:57:38
UTC 2009 i686
Build Date: 20 February 2009 03:06:29AM
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: Thu Mar 25 09:37:32 2010
(==) 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/10
Bug#573000: DRI/GLX Broken in Testing PPC on ibook
A default install of Testing on a G3 12" iBook generated similar issues. 1. An xorg.conf is required. Otherwise, the ibook locks up. 2. The xorg.conf needs a disable glx stanze. I can enable dri and dri2. Enable glx and the ibook is not recoverable without a power switch shutdown. 3. driconf reports that the video card is not DRI capable. (Maybe because there's no GLX???) Desktop is painfully slow without acceleration. -- 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/233286.90630...@web62007.mail.re1.yahoo.com
Bug#575287: Same here even with 2.6.32-4-amd64
On 25.03.2010 10:53, Julien Cristau wrote: > On Thu, Mar 25, 2010 at 09:47:43 +0100, Michel Dänzer wrote: > >> The above means that the X driver is using UMS whereas KMS is enabled in >> the kernel. This results in a conflict for hardware access and cannot >> work properly. >> >> It's usually caused by the radeon kernel module being loaded too late. >> > With the latest sid kernel udev should load the module on boot. dmesg > would give a clue as to why that didn't happen here. Nope, it isn't loaded on boot and I can't find anything related in dmesg output. Anyway, loading it manually before starting X rectifies issues in this report and it works more/less as expected. Regards, Vedran -- http://vedranf.net | a8e7a7783ca0d460fee090cc584adc12 <>
Bug#575287: Additional info
It indeed fixes the problem. Best regards, -- Nicolas DEGAND -- 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/201003252153.36263.nico...@degand.net
Re: [ubuntu-x] Backported features from xserver 1.8
On Thu, Mar 25, 2010 at 03:49:47PM +0200, Timo Aaltonen wrote: > > Ok, since this made the headlines on Phoronix I should probably correct > some misconceptions and explain a bit more to the greater public. For the record, I'm not opposed to this but given how late things have gotten in the cycle it seems rather ambitious. I definitely agree it's not something we would want to diverge with Debian on. In particular, I'm concerned about the number of packages which would need to be updated for this change, since we could easily miss something or introduce a typo, and time is short to get sufficient testing, triaging, and patching done prior to release. Also, while configuration fixes can be easy to apply, review, and sru, certain kinds of configuration changes can cause problems during installation, so if we don't get all such issues fixed before the CD's are cut, it could make for a lot of buggy installation experiences. I do not know how large to quantify this risk though. Perhaps its minor. On the other hand, I do agree that the udev approach for configuration is funky. The syntax style of the configuration files is quite a bit different than people are used to and will be irritating for people who have to maintain both LTS systems and Lucid+N systems. From our end, there will be some differences in maintaining things, but I'm less concerned here: I think it'll play out that for the next 3-4 months we'll be doing fixes for Lucid, then after that will focus on Lucid+1 and the amount of udev-rules patching we do will probably drop off quite a bit. I expect a lot of the LTS X maintenance work will be done by the new hardware enablement X person, so as long as they understand how to do udev and xorg.conf.d rules, we should be ok on our end. Bryce -- 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/20100325212330.gu3...@bryceharrington.org
Bug#575287: marked as done (Xorg displays blank screen at boot since last upgrade)
Your message dated Thu, 25 Mar 2010 22:44:55 +0100 with message-id <4babd957.2010...@ens-lyon.org> and subject line Re: Bug#575287: Additional info has caused the Debian Bug report #575287, regarding Xorg displays blank screen at boot since last upgrade 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.) -- 575287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-radeon Version: 1:6.12.192-2 Severity: grave Tags: sid Since this upgrade, when booting, X fails to display. My monitor flickers between sleep and active mode, but does not display a thing (see the Xorg.0.log attached, it seems to append something everytime it flickers). Trying to switch VT through ctrl-alt-Fx does not work. Reverting to 6.12.5 solves the problem. -- 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 13 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: 02:00.0 VGA compatible controller: ATI Technologies Inc RV790 [Radeon HD 4800 Series] /etc/X11/xorg.conf does not exist. Xorg X server log files on system: -rw-r--r-- 1 root root 40433 Jan 2 20:22 /var/log/Xorg.1.log -rw-r--r-- 1 root root 41977 Mar 24 19:16 /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.6 Release Date: 2010-03-17 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-2-amd64 x86_64 Debian Current Operating System: Linux Charles-de-Gaulle 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=c507a375-0b60-4c3c-8064-a8e23dfea622 ro quiet Build Date: 23 March 2010 04:00:24PM xorg-server 2:1.7.6-1 (Cyril Brulebois ) 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: Wed Mar 24 19:16:36 2010 (II) Loader magic: 0x7c3240 (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:2:0:0) 1002:9460:174b:e115 ATI Technologies Inc RV790 [Radeon HD 4800 Series] rev 0, Mem @ 0xd000/268435456, 0xfbde/65536, I/O @ 0xce00/256, BIOS @ 0x/131072 (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier "Builtin Default ati Device 0" Driver "ati" EndSection Section "Screen" Identifier "Builtin Default ati Screen 0" Device "Builtin Default ati Device 0" EndSection Section "Device" Identifier "Builtin Default vesa Device 0" Driver "vesa" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 0" Device "Builtin Default vesa Device 0" EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default ati Screen 0" Screen "Builtin Default vesa Screen 0" Screen "Builtin Default fbdev Screen 0" EndSection (==) --- End of built-in configuration --- (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default ati Screen 0" (0) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default ati Device 0" (==) No monitor specified for screen "Builtin Default ati Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default vesa Screen 0" (1) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default vesa Device 0" (==) No monitor specified for screen "Builti
Re: [ubuntu-x] Backported features from xserver 1.8
On Thu, 25 Mar 2010, Bryce Harrington wrote: On Thu, Mar 25, 2010 at 03:49:47PM +0200, Timo Aaltonen wrote: Ok, since this made the headlines on Phoronix I should probably correct some misconceptions and explain a bit more to the greater public. For the record, I'm not opposed to this but given how late things have gotten in the cycle it seems rather ambitious. I definitely agree it's not something we would want to diverge with Debian on. In particular, I'm concerned about the number of packages which would need to be updated for this change, since we could easily miss something or introduce a typo, and time is short to get sufficient testing, triaging, and patching done prior to release. Actually that's the least of my concerns :), there are only a handful of input drivers with udev rules: evdev, synaptics, wacom, joystick, vmmouse. Only vmmouse is not converted yet, and evtouch is trivial to add. ..but the one I _am_ concerned about is the autoconfig fallback patch which is quite fresh, and seems to have triggered some bugs (thread on xorg-devel@). I haven't been able to reproduce the crasher though, tried on my laptop (intel) and desktop (nvidia/nouveau/nv). But if it can't be made to work 100% then I don't think it's good enough for us at this point, and we can all move on :) -- Timo Aaltonen Systems Specialist IT Services, Aalto University School of Science and Technology -- 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/alpine.deb.2.00.1003252356110.29...@deckard.hut.fi
