Bug#1050994: xutils-dev: Please add support for loong64
Source: xutils-dev Version: 1:7.7+6.1 Severity: normal User: debian-de...@lists.debian.org Usertags: loong64 X-Debbugs-Cc: debian-de...@lists.debian.org,zhangjial...@loongson.cn,zhangdan...@loongson.cn Hi! Multiple X packages currently fail to build from source on loong64 due to missing architecture support in xutils-dev [1]: gcc: warning: LinuxMachineDefines: linker input file unused because linking not done gcc: error: LinuxMachineDefines: linker input file not found: No such file or directory This should be fixed in a similar fashion for loong64 as it has been done for riscv64 in [2]. I have CC'ed two engineers from Loongson to make them aware of the bug so they can work on a patch to add loong64 support. Thanks, Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=xaw3d=loong64=1.5%2BF-1.1=1693526902=0 > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026002 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1002143: xserver-xorg-video-qxl: FTBFS: xf86Opt.h:44:10: error: two or more data types in declaration specifiers
Hello! There is an upstream fix available which fixes the FTBFS, see [1]. Adrian > [1] > https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/merge_requests/6 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Maintaining older xorg driver packages by Debian Ports
On 4/21/20 3:09 PM, Julien Cristau wrote: >> After some xorg driver packages were removed from the archive in #955603 [1] >> that we still need for Debian Ports, I was wondering whether it's okay when >> I take over maintainership and upload the packages to unstable as we need >> them. >> >> I understand that the timing is a bit unfortunate, but I wasn't aware of the >> removal bug otherwise, I would have asked for some of the drivers to stay. >> >> But I can just maintain the driver packages myself if that's ok? >> > If they're needed by debian-ports, then may I suggest you maintain them > there? Maintaining them in Debian Ports is completely manual and therefore very cumbersome. The packages cannot be built automatically unless they are part of the main archive. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Maintaining older xorg driver packages by Debian Ports
Hi! After some xorg driver packages were removed from the archive in #955603 [1] that we still need for Debian Ports, I was wondering whether it's okay when I take over maintainership and upload the packages to unstable as we need them. I understand that the timing is a bit unfortunate, but I wasn't aware of the removal bug otherwise, I would have asked for some of the drivers to stay. But I can just maintain the driver packages myself if that's ok? Thanks, Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955603 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#955603: RM: xserver-xorg-input-aiptek -- ROM; unmaintained, obsolete, or both
Hello! > xserver-xorg-video-ast > xserver-xorg-video-geode > xserver-xorg-video-mach64 > xserver-xorg-video-neomagic > xserver-xorg-video-r128 > xserver-xorg-video-savage > xserver-xorg-video-siliconmotion > xserver-xorg-video-sisusb > xserver-xorg-video-tdfx > xserver-xorg-video-trident The r128 driver is actually required for older Apple hardware and there was just a user reporting a missing video driver on his iMac. Would there be any problems if I maintained the driver myself if necessary? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#887444: mesa: Please build with optimization level -O1 on sh3 and sh4
Source: mesa Version: 17.3.2-1 Severity: normal Tags: patch User: debian-sup...@lists.debian.org Usertags: sh3 sh4 Hello! mesa currently FTBFS on sh4 (and consequently sh3) due to a bug in upstream gcc which hasn't been resolved yet [1]. To work around this bug, it's enough to add "-O1" to the extra C/C++ build flags on sh3/sh4 which sets "-freorder-blocks-algorithm=simple" Just passing "-freorder-blocks-algorithm=simple" doesn't unfor- tunately work as gcc would just crash the qemu buildd. This might be a bug in qemu. For the time being, we will be happy with just passing "-O1" to fix the FTBFS. Patch attached. Thanks, Adrian > [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83143 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 diff -Nru old/mesa-17.3.2/debian/rules new/mesa-17.3.2/debian/rules --- old/mesa-17.3.2/debian/rules2018-01-16 16:00:16.0 +0100 +++ new/mesa-17.3.2/debian/rules2018-01-16 16:50:14.789910395 +0100 @@ -10,13 +10,19 @@ DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS) DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU) -ifeq (,$(filter $(DEB_HOST_ARCH), armhf)) +ifeq (,$(filter $(DEB_HOST_ARCH), armhf sh3 sh4)) buildflags = \ $(shell DEB_CFLAGS_MAINT_APPEND=-Wall DEB_CXXFLAGS_MAINT_APPEND=-Wall dpkg-buildflags --export=configure) else -# Workaround for a variant of LP: #725126 -buildflags = \ + ifneq (,$(filter $(DEB_HOST_ARCH), armhf)) + # Workaround for a variant of LP: #725126 + buildflags = \ $(shell DEB_CFLAGS_MAINT_APPEND="-Wall -fno-optimize-sibling-calls" DEB_CXXFLAGS_MAINT_APPEND="-Wall -fno-optimize-sibling-calls" dpkg-buildflags --export=configure) + else + # Workaround for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83143 + buildflags = \ + $(shell DEB_CFLAGS_MAINT_APPEND="-Wall -O1" DEB_CXXFLAGS_MAINT_APPEND="-Wall -O1" dpkg-buildflags --export=configure) + endif endif # keep a list of files we don't install (yet), but since it's a bit
Bug#860347: xserver-xorg-core: can't produce script.log for running X server
Hi! The problem is that you're trying to run the script with 'sudo' which doesn't work. Becoming root first, then running the script works as expected though: glaubitz@ikarus:~$ sudo /usr/share/bug/xorg/script 3>/tmp/script.log /usr/share/bug/xorg/script: 19: /usr/share/bug/xorg/script: 3: Bad file descriptor glaubitz@ikarus:~$ sudo -i root@ikarus:~# /usr/share/bug/xorg/script 3>/tmp/script.log root@ikarus:~# head /tmp/script.log /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) /etc/X11/xorg.conf does not exist. root@ikarus:~# Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#859725: x11-common: Each time my screen standby, system crash
Control: tags -1 moreinfo Hi Alexandre! > In my syslog i have this lines : Nothing from your syslog excerpt indicates a problem with your X server. > Kernel: Linux 4.10.0-trunk-amd64 (SMP w/4 CPU cores) Is there a reason why you are using Debian pre-release kernel? The official kernel for Debian Stretch and Sid is still based on the 4.9 series. Could you please reboot your machine with the latest 4.9 kernel. Did you actually verify that your machine crashed? What about logging in through SSH over the network? Just because the screen is black doesn't mean the machine actually crashed. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#857450: libxcb1: many segfaults -gnome and such- related to libxcb
Control: tags -1 unreproducible Control: tags -1 moreinfo Hi Gregory! There are some issues with your bug report. First of all, I cannot reproduce your problem on Debian unstable, so you will have to provide a little more input about your environment. For example, have you verified it's not a hardware issue by running memtest on your machine? These random segfaults are more an indicator of memory problems. > Version: libxcb.so.1.1.0 This isn't correct. The package version is 1.12-1, not 1.1.0. That's the ABI version of this library. > Tags: upstream I'm not sure whether you're tagging this as "upstream" as your bug report does not provide enough information to justify that. Do you have a link to an upstream bug report? Is it an issue known upstream? Currently your bug report has insufficient data and may just be closed again. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#856662: xorg: starting X within X without specifying -vt destroys current X session
Control: tags -1 unreproducible Control: tags -1 moreinfo Hello! First of all, I'm not sure whether this is a valid bug report. You are basically trying to shoot yourself into the foot and you are surprised that you get hit. Independent from that, I cannot reproduce your problem on KDE with SDDM: glaubitz@ikarus:~$ X :1 X.Org X Server 1.19.2 Release Date: 2017-03-02 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian Current Operating System: Linux ikarus 4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-28) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-amd64 root=UUID=8d61a11d-7005-4415-8831-07b626b8d8bd ro quiet Build Date: 03 March 2017 03:14:41PM xorg-server 2:1.19.2-1 (https://www.debian.org/support) Current version of pixman: 0.34.0 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: "/home/glaubitz/.local/share/xorg/Xorg.1.log", Time: Fri Mar 3 20:24:18 2017 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied) (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/home/glaubitz/.local/share/xorg/Xorg.1.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. glaubitz@ikarus:~$ startx -- :1 X.Org X Server 1.19.2 Release Date: 2017-03-02 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian Current Operating System: Linux ikarus 4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-28) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-amd64 root=UUID=8d61a11d-7005-4415-8831-07b626b8d8bd ro quiet Build Date: 03 March 2017 03:14:41PM xorg-server 2:1.19.2-1 (https://www.debian.org/support) Current version of pixman: 0.34.0 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: "/home/glaubitz/.local/share/xorg/Xorg.1.log", Time: Fri Mar 3 20:24:35 2017 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied) (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/home/glaubitz/.local/share/xorg/Xorg.1.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. ^Cxinit: giving up xinit: unable to connect to X server: Connection refused xinit: unexpected signal 2 Couldn't get a file descriptor referring to the console glaubitz@ikarus:~$ Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#856039: xserver-xorg-core: no keyboard and no mouse
On 02/27/2017 10:50 AM, Michel Dänzer wrote: > On 27/02/17 06:42 PM, John Paul Adrian Glaubitz wrote: >> On 02/27/2017 10:17 AM, Michel Dänzer wrote: >>> The client side has no impact on which drivers Xorg loads, or when. It >>> looks like simply neither xserver-xorg-input-libinput nor >>> xserver-xorg-input-evdev is installed. >> >> Yes, but it's usually these "not using a modern desktop or systemd" >> setups where things break in very interesting ways. > > Maybe so, but not like this. :) It works here, it doesn't work for Toni. And this issue is blocking the release. I want to close or resolve this issue as soon as possible, that's why I am asking these questions. Arguing that "X or Y" cannot cause this problem don't get us any further. I want to know the details of the setup so I can try to reproduce this problem. Otherwise, I'll just close this bug. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#856039: xserver-xorg-core: no keyboard and no mouse
On 02/27/2017 10:17 AM, Michel Dänzer wrote: > The client side has no impact on which drivers Xorg loads, or when. It > looks like simply neither xserver-xorg-input-libinput nor > xserver-xorg-input-evdev is installed. Yes, but it's usually these "not using a modern desktop or systemd" setups where things break in very interesting ways. I haven't seen such problems with KDE, GNOME or MATE. Hence I was asking. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#856039: xserver-xorg-core: no keyboard and no mouse
Hi! Do you have the evdev kernel module loaded? evdev is required for X.Org to get data from input devices through the kernel. This indicates that evdev may be missing: [ 9670.895] (II) config/udev: Adding input device USB Keyboard (/dev/input/event0) [ 9670.895] (II) No input driver specified, ignoring this device. [ 9670.895] (II) This device may have been added with another device file. Are you by any chance using a very old window manager or running X by typing "startx"? If yes, this might not load "evdev" automatically and you have to take care of that yourself. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#789100: mesa: FTBFS on sh4 due to missing files in dh_install
Source: mesa Version: 10.5.7-1 Severity: normal Hello! mesa currently fails to build from source on sh4 due to at least one file missing when dh_install is invoked at the end of the build: # Copy the hardlinked vdpau drivers correctly. install -m755 -d debian/mesa-vdpau-drivers/usr/lib/sh4-linux-gnu/vdpau/ mv debian/tmp/dri/usr/lib/sh4-linux-gnu/vdpau/libvdpau*.so* \ debian/mesa-vdpau-drivers/usr/lib/sh4-linux-gnu/vdpau/ dh_install -s --fail-missing dh_install: dri/usr/lib/sh4-linux-gnu/dri/gallium_drv_video.so exists in debian/tmp but is not installed to anywhere dh_install: missing files, aborting make: *** [binary-arch] Error 2 debian/rules:259: recipe for target 'binary-arch' failed dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 The problem can probably fixed by ignoring gallium_drv_video.so on sh4 and probably all other architectures which do not support Gallium. If I remember correctly, Gallium requires a working port of the llvm infrastructure which is not available on a couple of non-x86 architectures which is why it might probably a good idea to check all possibly affected architectures. The full build log can be obtained in [1]. Thanks, Adrian [1] http://buildd.debian-ports.org/status/fetch.php?pkg=mesaarch=sh4ver=10.5.7-1stamp=1434561462 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150617210125.4251.48368.report...@jessie64.physik.fu-berlin.de
Bug#728053: [Mesa-dev] Updated debdiff for mesa to compile on m68k
Hi Ilia! On 07/17/2014 04:35 PM, Ilia Mirkin wrote: Thanks! Munged the commit description a little and pushed to the master branch. I think the patches for 10.2.4 have already been selected, so it should make its way into 10.2.5. Awesome, thank you so much! Glad we could finally this one :). Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53c7e04a.6050...@physik.fu-berlin.de
Bug#728053: Updated debdiff for mesa to compile on m68k
Hi Thorsten! On 07/16/2014 01:03 PM, Thorsten Glaser wrote: updated debdiff attached. Package compiles fine with it (on i386 and m68k), and the invalid alignment assumptions were made explicit with no ABI breakage. Awesome! That's great to hear! Please apply. Absolutely. Could the upstream Mesa developers maybe apply the patch as well? We're putting lots of efforts into the m68k port and we have many users who love running Debian on retro m68k hardware and emulators and we even got some official funding through Debian to buy hardware. Even Greg Kroah-Hartman says he appreciates the port when I asked him about on LinuxTag, it helps spotting regressions :). So, please help us and apply Thorsten's patch provided it won't break anything else. Thanks! Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53c65d83.5040...@physik.fu-berlin.de
Bug#715278: Any attempt to have intel-gpu-tools 1.6 which fixes this bug ?
Hi! Is there any attempt to get intel-gpu-tools 1.6 which fixes the bug ? Not really, no. Do you guys need help? Updating the package to the latest upstream version should be a no-brainer using the Debian git packaging tools unless I am missing something here. I'd be happy to NMU. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53711ca4.1060...@physik.fu-berlin.de
Bug#724576: libgl1-mesa-glx: libGL error: failed to load driver: nouveau
On 10/25/2013 10:07 PM, Sven Joachim wrote: Well, I haven't figured out yet why exactly the module fails to load. I just know that it does when using libgl1-mesa-dri from experimental. I'll maybe check if I can get more verbose debugging output with the libgl1-mesa-dri-dbg package instead. So, do you still have that problem with mesa 9.2.2-1? Yes, still seeing the problem unfortunately. Just did a full dist-upgrade which updated mesa to 9.2.2-1 and the problem still persists. I did lots of testing already before I could localize it to that particular package. Granted, I wasn't working purposively when doing that, but I was trying to resolve different issues with the PowerMac G5 I was testing this on, too. I would expect this to be a powerpc specific problem, but Thomas is actually running amd64. OTOH, mesa 9.2.2 has been in unstable for three days now, and apparently nobody else has complained so far. Well, I'll meet Thomas in a few days during an open source meetup and ask him about the status. And, I'd rather think it's a problem specific to the nVidia card in use. I have GeForce 210 on my main desktop running unstable and I don't see the problem there. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- 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/52753147.6010...@physik.fu-berlin.de
Bug#724576: libgl1-mesa-glx: libGL error: failed to load driver: nouveau
On 10/21/2013 09:08 PM, Sven Joachim wrote: I have also reported this issue upstream [1], even though I don't think this is an upstream issue but with the particular Debian package. Could you please send the link for [1], it's not included in your mail. Oops, my bad: https://bugs.freedesktop.org/show_bug.cgi?id=70135 Maybe rebuilding fixes the issue? How so, what would be wrong in the build environment on the buildds? Well, I haven't figured out yet why exactly the module fails to load. I just know that it does when using libgl1-mesa-dri from experimental. I'll maybe check if I can get more verbose debugging output with the libgl1-mesa-dri-dbg package instead. I did lots of testing already before I could localize it to that particular package. Granted, I wasn't working purposively when doing that, but I was trying to resolve different issues with the PowerMac G5 I was testing this on, too. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- 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/5265a606.2040...@physik.fu-berlin.de
Bug#651965: xserver-xorg-video-nouveau: corrupt glyphs and icons in gnome-shell on NV34 [GeForce FX 5200]
Hi Daniel! I'm seeing corrupted text glyphs and icons in the latest gnome-shell (from either unstable or experimental). I believe it's a problem with the nouveau driver (maybe specific to this particular model of card?) I have been playing around with an old PowerMac G5 which I borrowed as a PPC porterbox and it happens to have this particular video adapter as well. Initially, I installed Debian Wheezy onto the Mac and ran into many rendering issues with nouveau and gnome-shell and the latter happened to crash very often. However, upgrading everything to unstable resolved both the rendering issues as well as the gnome-shell crashes. I think Mesa upstream fixed many nouveau issues in the newer Mesa releases, so you should definitely give that a try in case you still have this machine around, so we might be able to close this bug ;). Additionally, it would be interesting to know whether 3D hardware acceleration works on your laptop after upgrading to the Mesa version in experimental (9.2.1-1). I figured out that after upgrading to 9.2.1-1, Mesa could no longer load the nouveau_dri.so module which I could resolve by downgrading libgl1-mesa-dri to 9.1.7-1 again (I didn't have to downgrade the rest of Mesa). Cheers across the big lake ;) Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- 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/52644d55.9040...@physik.fu-berlin.de
Bug#724576: libgl1-mesa-glx: libGL error: failed to load driver: nouveau
Hi Thomas! error: XDG_RUNTIME_DIR not set in the environment. libGL error: failed to load driver: nouveau libGL error: Try again with LIBGL_DEBUG=verbose for more details. error: XDG_RUNTIME_DIR not set in the environment. Versions of packages xserver-xorg recommends: ii libgl1-mesa-dri 9.2-1 I am seeing the exact same issue on an Apple PowerMac G5 (A1047) with has a GeForce FX 5200 Ultra (NV34) video adpater. This problem was present only with the Mesa DRI version from experimental (9.2.1-1). Downgrading just the DRI package libgl1-mesa-dri from 9.2.1-1 to 9.1.7-1 resolved the issue for me. I'm attaching the output of glxinfo for both versions of libgl1-mesa-dri with LIBGL_DEBUG=verbose set if that's of any help for the mesa maintainers. I have also reported this issue upstream [1], even though I don't think this is an upstream issue but with the particular Debian package. Maybe rebuilding fixes the issue? Could you try downgrading just this package and report back? Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/nouveau_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/nouveau_dri.so libGL: Can't open configuration file /home/glaubitz/.drirc: No such file or directory. libGL: Can't open configuration file /home/glaubitz/.drirc: No such file or directory. libGL: Can't open configuration file /home/glaubitz/.drirc: No such file or directory. name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: nouveau OpenGL renderer string: Gallium 0.4 on NV34 OpenGL version string: 1.5 Mesa 9.1.7 OpenGL extensions: GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_elements_base_vertex, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_shader_objects, GL_ARB_shading_language_100, GL_ARB_shadow, GL_ARB_sync, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar
Bug#724576: libgl1-mesa-glx: libGL error: failed to load driver: nouveau
Btw, Sven, That might be http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722930. Have you looked at that bug yet? Could be the same bug. At least http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722930#15 this is the same error. I do not think that Thomas' problem is related to the bug report you are mentioning here. The problem Thomas (and I) see is that Mesa is unable to load the DRI module for nouveau even though the module is actually present. I might just try rebuilding Mesa locally and see if that fixes the problem. I'm not sure why Mesa can't load the DRI module as even with debug enabled, I don't see any error message reasoning why the module couldn't be loaded. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- 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/5264515e@physik.fu-berlin.de
Re: [PATCH 00/18] Xfbdev Atari and Amiga support
On 03/27/2013 02:20 PM, Geert Uytterhoeven wrote: This patch series revives some of the support for Atari and Amiga that existed in XF68_FBDev, but got lost after XFree86 3.x. Whoa, that's pretty cool, thanks for that! I saw an older posting from you on debian-68k [1] that you'd be working on that and now it's actually done, very cool. Too bad my Amiga 1200 currently crashes when trying to boot any of the Debian m68k releases :(. Adrian [1] http://lists.debian.org/debian-68k/2010/03/msg4.html -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- 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/51530258.2070...@physik.fu-berlin.de
Bug#576612: xserver-xorg-video-radeon: New upstream release 6.13.0, please package
On Tue, Apr 06, 2010 at 03:36:20AM +0200, Cyril Brulebois wrote: Adrian Glaubitz glaub...@physik.fu-berlin.de (06/04/2010): Today, this version has finally tagged as stable and has been released as 6.13.0 by upstream. It would be nice if it would be packaged as soon as possible. Speechless: | Subject: Accepted xserver-xorg-video-ati 1:6.13.0-1 (source amd64) | Date: Mon, 05 Apr 2010 19:36:21 +0200 If you care so much to write such a long mail, why the fucking fuck don't you check what's in the archive, or what's in git on our side? Seriously, calm down. There is no reason to be that upset because of a stupid bug report. I filed this wishlist report because 6.13.0 was just announced this weekend and usually Debian always takes several days to get packages uploaded, your team seems to be the famous exception. When I filed the bug, I checked the archives and, of course, it wasn't there yet because you uploaded it just 4 hours earlier and it didn't appear anywhere. I always check the version numbers before reporting any bugs. True, I should have checked the PTS for the package also. But still that doesn't justify to freak out that much and to defame me in public on a mailing list, you could have sent me an email in private and write a tempered reply on the mailing list. This is not the way how people in the open source community should treat each other and especially not grown up people. Best Regards, Adrian -- 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/20100406085358.ga27...@physik.fu-berlin.de
Bug#576612: xserver-xorg-video-radeon: New upstream release 6.13.0, please package
On Tue, Apr 06, 2010 at 01:39:56PM +0200, Cyril Brulebois wrote: Adrian Glaubitz glaub...@physik.fu-berlin.de (06/04/2010): Seriously, calm down. Seriously, stop telling people what they must do; bonus points if you can also get rid of “as soon as possible”; double bonus points if you manage to do that when you're late. Hæh, I filed that report under wishlist, that's just a pretty normal thing to do as the bug reporting system provides that option. It does not convey that someone actually has to fulfill my wish, that's the whole idea of a wishlist. You can simply ignore the request or even cancel it and no-one will be upset. […], you could have sent me an email in private and write a tempered reply on the mailing list. It *was* tempered. As for public/private replies, why the fuck should they be different? You're behaving like an impatient child (see, I can mock people for not being grown up, too) publicly, and don't want to read public replies to that behaviour? Too bad. Well, if that was tempered then I don't want to see you in a rage. That's really not the way to treat people. Again, calm down. It was just a bug report and I did it in error and I already admitted that I should have checked PTS as well. There is absolutely no reason to freak out that much. Swearing around like you did usually is a sign that someone is not willing or able to discuss on a rational basis. But I know that within the anonymity many people forget about their manners. This is not the way how people in the open source community should treat each other and especially not grown up people. Yay, more patronizing and more telling people what they should do. That's the way the open source community should treat each other and especially grown up people‽ I beg to differ. Where am I telling people what to do? It was on the *wishlist*, if you don't want to do it, just ignore request but don't flame people for using a feature of the bug report system. Meh, was that really necessary?! I really don't like fights like these :(. Adrian -- 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/20100406120114.ga3...@physik.fu-berlin.de
Bug#576612: xserver-xorg-video-radeon: New upstream release 6.13.0, please package
On Tue, Apr 06, 2010 at 02:36:19PM +0200, Cyril Brulebois wrote: (Yay, different yet similar private/public mails.) Yes, my bad. I happened to be too stupid to use mutt today, twice ;). Sorry! Adrian Glaubitz glaub...@physik.fu-berlin.de (06/04/2010): Meh, was that really necessary?! […] I probably should have ignored you from the very beginning; fixing my behaviour. Ok, and I promise that I will check both the archives *and* PTS/your git before reporting something next time! No worries ;). Adrian -- 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/20100406124924.ge32...@physik.fu-berlin.de
Bug#576612: xserver-xorg-video-radeon: New upstream release 6.13.0, please package
Hi, On Tue, Apr 06, 2010 at 04:34:00PM +0200, Brice Goglin wrote: Adrian Glaubitz wrote: Hæh, I filed that report under wishlist, that's just a pretty normal thing to do as the bug reporting system provides that option. It does not convey that someone actually has to fulfill my wish, that's the whole idea of a wishlist. You can simply ignore the request or even cancel it and no-one will be upset. FWIW, I don't like such wishlists when they are reported so fast (i.e. within a couple days after the upstream release). If we ever forget to upload a new upstream release, such a wishlist may help. But in the vast majority of cases, we are subscribed to upstream mailing lists, we know we have to upload a new package anytime soon, but we have a real life so we can't always upload within less 2 hours after the upstream release. Good. I fully agree with that policy and I will respect that in future. I just didn't understand why Cyril was so upset of my report. I certainly did not mean to harass anyone but just let you know in case you missed the announcement. As I said before, I have made experiences with other maintainers who missed several new upstream releases. You guys are a great example of someone who is really fast and always up-to-date with upstream, so I don't need to worry about future releases. Again, I didn't mean to push anyone here but just wanted to let you guys know in case someone missed it. I am very sorry for all the noise I produced. And thanks a lot for the very fast packaging, Cyril! Seriously ;). Adrian -- 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/20100406150953.gf32...@physik.fu-berlin.de
Bug#558788: add nouveau in squeeze, please
Package: xserver-xorg-video-nouveau Severity: normal Hi, there are a few problems which will probably prevent nouveau from being added to Squeeze: First, Squeeze is certainly going to be shipped with 2.6.32 since it is a kernel with long-term support from upstream. Since Debian puts a strong emphasis on stability and long-term stable support, it is very likely that it will be shipped with 2.6.32. The problem now is that nouveau modesetting and drm support is not in 2.6.32 but it was first introduced with 2.6.33. Thus, in order to use nouveau together with Squeeze, the nouveau drm and modesetting code will have to be backported from 2.6.33 which Ubuntu did for their due 10.04 release. Secondly, even if the nouveau code gets backported to 2.6.32, there is still the problem that the nouveau xorg driver has received significant changes in the drm API which are incompatible to all drm code prior to 2.6.34. Thus, the current upstream nouveau version cannot be used without a lot of efforts of backporting or people will have to stick to the current version of nouveau from experimental which, however, still needs the backporting of the drm code from 2.6.32 to 2.6.33. My suggestion therefore is to drop nouveau for Squeeze and rather wait until 2.6.34 is released and makes it into unstable. At this point, the kernel will provide all necessary drm and modesetting code in a hopefully mature state. Adrian -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20100327232354.28775.23635.report...@z6.physik.fu-berlin.de
Bug#567999: Please compile with kernel-based modesetting (KMS) enabled
Package: xserver-xorg-video-radeon Severity: normal Hi Brice, I have installed the version you have uploaded now and will give it some intense testing. So far, it runs very smooth like I already experienced on my Ubuntu Lucid laptop. If I see anything serious, I will give you a feedback. Adrian -- 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 24 2009 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1864832 Jan 21 00:37 /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 RV370 [Sapphire X550 Silent] /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1077 Sep 6 20:52 /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 EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 31847 Feb 23 15:41 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.4 Release Date: 2010-01-08 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.4-dsa-amd64 x86_64 Debian Current Operating System: Linux z6 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=a09c284d-51c2-476e-9edd-a66813c26b17 ro quiet Build Date: 20 January 2010 11:36:07PM xorg-server 2:1.7.4-2 (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: Tue Feb 23 15:37:13 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 (==) Automatically adding devices (==) Automatically enabling devices (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/cyrillic, /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: 0x7c1600 (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:2:0:0) 1002:5b63:174b:3000 ATI Technologies Inc RV370 [Sapphire X550 Silent] rev 0, Mem @ 0xe800/134217728, 0xfddf/65536, I/O @ 0xcc00/256, BIOS @ 0x/131072 (--) PCI: (0:2:0:1) 1002:5b73:174b:3001 ATI Technologies Inc RV370 secondary [Sapphire X550 Silent] rev 0, Mem @ 0xfdde/65536 (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.4, module version = 1.0.0 Module class: X.Org Server
Bug#567999: closed by Brice Goglin bgog...@debian.org (Bug#567999: fixed in xserver-xorg-video-ati 1:6.12.99+git20100201.a887818f-1)
Hi Brice, On Mon, Feb 01, 2010 at 11:39:24PM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the xserver-xorg-video-radeon package: #567999: xserver-xorg-video-radeon: Please compile with kernel-based modesetting (KMS) enabled It has been closed by Brice Goglin bgog...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Brice Goglin bgog...@debian.org by replying to this email. Thanks for uploading the latest version of xserver-xorg-video-radeom so quickly. I will test this version as soon as it is available. Thanks, Adrian -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567999: xserver-xorg-video-radeon: Please compile with kernel-based modesetting (KMS) enabled
Hi Brice, thanks for your fast reply! On Mon, Feb 01, 2010 at 08:15:47PM +0100, Brice Goglin wrote: Yes, KMS cannot be enabled in current 6.12 packages, we need a snapshot of git master. I am thinking of working on this in the next days and upload it to experimental. Ah, that would be great. Please let me know once the package is in experimental. Last time I tried, I had some problems with the radeon kernel driver being loaded too late (see [1]). What do you use on Ubuntu in /etc/modprobe.d/ or on the kernel command line ? Yes, older versions of the driver were quite prone to crash with KMS enabled. X would just die out of nothing when clicking on a window. It was extremely hard to reproduce but at least there were some error messages in the logs, so I guess Airlie and others have finally fixed it. On the current Ubuntu 10.04, it's enabled by default in the kernel: r...@oslo:/boot grep RADEON_KMS config-`uname -r` CONFIG_DRM_RADEON_KMS=y It's neither set on the command line nor in /etc/initramfs-tools/modules Adrian -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514817: Similar backtrace at random crash on Q45/Q43
Hi, one of my colleagues seems to have the same crash, I am attaching the Xorg.0.log. His desktop is a Dell Optiplex 760 with Q45/43, see lspci below. On another machine, Dell Optiplex 745, the problem does not occur, chipset is Q965. Setup which crashes randomly: r...@jongleur:~ lspci 00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03) 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) 00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI Controller (rev 03) 00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER Controller (rev 03) 00:03.3 Serial controller: Intel Corporation 4 Series Chipset Serial KT Controller (rev 03) 00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02) 00:1a.0 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #4 (rev 02) 00:1a.1 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #5 (rev 02) 00:1a.2 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #6 (rev 02) 00:1a.7 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB2 EHCI Controller #2 (rev 02) 00:1b.0 Audio device: Intel Corporation 82801JD/DO (ICH10 Family) HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801JD/DO (ICH10 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation 82801JD/DO (ICH10 Family) PCI Express Port 2 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB UHCI Controller #3 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801JD/DO (ICH10 Family) USB2 EHCI Controller #1 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a2) 00:1f.0 ISA bridge: Intel Corporation 82801JD (ICH10D) LPC Interface Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801JD/DO (ICH10 Family) SATA AHCI Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801JD/DO (ICH10 Family) SMBus Controller (rev 02) Working setup on the other machine: r...@burns:~ lspci 00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) 00:02.1 Display controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02) 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02) 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02) 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2) 00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02) 00:1f.5 IDE interface: Intel Corporation 82801H (ICH8 Family) 2 port SATA IDE Controller (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit Ethernet PCI Express (rev 02) Xorg.0.log from crash is attached. Adrian X.Org X Server 1.6.4 Release Date: 2009-9-27 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.31 i686 Debian Current Operating System: Linux jongleur 2.6.30-1-686 #1 SMP Sat Aug 15 19:11:58 UTC 2009 i686 Build Date: 30 September 2009 08:45:15PM xorg-server 2:1.6.4-2 (bgog...@debian.org) 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: Tue Oct 27 16:10:41 2009 (II) Loader magic: 0x6c0 (II) Module ABI
Bug#536842: compiz-gtk: No window decorations using gtk-window-decorator
Hi, I had the same problem today and I could solve it by opening the compizconfig settings manager then choosing effects and selecting window decoration. In window decoration window select Enable Window Decoration on the left hand side. The compiz configuration in Debian has apparently a poor default configuration. Besides the missing window decoration, on my Debian Squeeze system essential things like Resize Window and Move Window (both in Window Management) aren't enabled by default as well. Also Gnone Compatibility in the General section is disabled as well. The initial compiz configuration in Ubuntu is a good example of a sensible default configuration. Adrian -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#496747: xserver-xorg-video-ati: multi-head virtualsize and direct rendering not working with two different monitor resolutions
Hello, since the original poster is a good friend of mine and I know his setup, I'd like to make some additions: The above Xorg.log-file was taken when he had 2 displays with the same resolution connected, but in fact the problem only appears when using two displays with different resolution: Setup 1: Display 1: 1280x1024, Benq, TFT, Connected with VGA Display 2: 1600x1080, DELL, TFT, COnnected with DVI Results: Direct Rendering does *not* work. glxinfo shows Direct Rendering: No. When starting X, the displays have, as already mentioned, have the same virtual display size (both using 1600x1080). Thus the 1280-display having the 1600-resolution, too. When checking the monitors display-menu though, the 1280-display is running at it's native 1280x1024. Calling xrandr --output VGA-0 --auto from an xterm immediately fixes that situation so both displays run with a virtual resolution matching their native hardware-resolution. Setup 2: Display 1: 1280x1024, Benq, TFT, Connected with VGA Display 2: 1280x1024, Samsung, TFT, Connected with DVI Results: Direct Rendering works, glxinfo shows Direct Rendering: Yes. Both displays have proper virtual resolution. Display controller: ATI Technologies Inc RV370 [Radeon X300SE] Regards, Adrian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390913: xserver-xorg-video-i810: blank screen after suspend
Hello, On Mon, Jun 25, 2007 at 10:14:34PM +0200, Brice Goglin wrote: But why would I still need to pass the extra kernel command-line, can't you take care of this within the driver code ? I don't know exactly, but I guess acpi_sleep=s3_bios changes the way the kernel restores things. The Xorg driver is far away from this kernel code (it does not run in kernel space, and it's very late in resume process). I think it's very common (not intel-chipset specific) to have to pass such an option to get resume to work. I understand, then this also could be BIOS-related. An update of the BIOS might fix it, too. But I don't won't to hassle with that. I'd also called this bug fixed. Apart from that, I sometimes experience an apparent total freeze upon logout from X (LCD totally dark, no pattern visible, system does not respond anymore). I don't know whether this is related to the 2.x-version of the Intel-driver or anything else. I will try to reproduce it and see whether this is related to the driver. Regards, Adrian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390913: xserver-xorg-video-i810: blank screen after suspend
Hello Brice, On Sat, Jun 23, 2007 at 10:02:12AM +0200, Brice Goglin wrote: It would be good if all of you could try with the latest xserver-xorg-video-intel driver (2:2.0.0-5 currently in experimental). It is supposed to resume well. Ok, I have installed the version from experimental (2:2.0.0-5). The problem still persists, i.e. the screen is blank (it's just the LCD backlight which is not turned on, you can a dim picture) upon resume but I can get it back with vbetool post *and* switching to and fro a text-console (vbetool alone won't do it). Passing acpi_sleep=s3_bios will also fix it and *without* the need of extra console-switching. So 2:2.0.0-5 + acpi_sleep=s3_bios work perfectly :). But why would I still need to pass the extra kernel command-line, can't you take care of this within the driver code ? My Hardware: IBM ThinkPad X40 2371-7JG lspci: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Packages: [EMAIL PROTECTED]:~ dpkg -l xserver-xorg-video-i\* | grep -e '^i' ii xserver-xorg-video-i128 1:1.2.1-2 X.Org X server -- i128 display driver ii xserver-xorg-video-i740 1:1.1.0-3 X.Org X server -- i740 display driver ii xserver-xorg-video-i810 2:2.0.0-5 X.Org X server -- Intel i8xx, i9xx display d ii xserver-xorg-video-imstt 1:1.1.0-3 X.Org X server -- IMSTT display driver ii xserver-xorg-video-intel 2:2.0.0-5 X.Org X server -- Intel i8xx, i9xx display d PS: Video overlay on the LCD also works for me with the 2.x-driver now. Thanks alot for your work ! Adrian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390913: Problem still present in 2.0.0-1
Hello, since there are opposite reports about this problem, I'd like to let you know that this problem still persists, using: xserver-xorg 7.2-3 xserver-xorg-core1.3.0.0.dfsg-3 xserver-xorg-video-i810 2.0.0-1 The problem instantly disappears after downgrading to 1.7.2-4 from testing, though even with this version, suspending has the sideeffect, that the mouse-cursor becomes invisible, so I have to restart gdm to use my mouse again. Adrian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421847: No xv-video with mplayer/totem (blue screen only)
Package: xserver-xorg-video-i810 Version: 2.0.0-1 I can get no video output using the xv-driver with mplayer,totem,etc when using version 2.0.0-1 of the xserver-xorg-video-i810 driver, the screen remains blue. Audio is fine. Downgrading to version 1.7.2-4 (testing) fixes this problem immediately. Packages: dpkg -l xserver-xorg\* |grep ^ii ii xserver-xorg 7.2-3the X.Org X server ii xserver-xorg-core1.3.0.0.dfsg-3 X.Org X server -- core server ii xserver-xorg-input-all 7.2-3the X.Org X server -- input driver metapacka ii xserver-xorg-input-evdev 1.1.2-6 X.Org X server -- evdev input driver ii xserver-xorg-input-kbd 1.1.0-4 X.Org X server -- keyboard input driver ii xserver-xorg-input-mouse 1.1.1-3 X.Org X server -- mouse input driver ii xserver-xorg-input-synaptics 0.14.6-1 Synaptics TouchPad driver for X.Org/XFree86 ii xserver-xorg-input-wacom 0.7.4.1-6X.Org X server -- wacom input driver ii xserver-xorg-video-all 7.2-3the X.Org X server -- output driver metapack ii xserver-xorg-video-apm 1.1.1-3 X.Org X server -- APM display driver ii xserver-xorg-video-ark 0.6.0-3 X.Org X server -- ark display driver ii xserver-xorg-video-ati 6.6.3-2 X.Org X server -- ATI display driver ii xserver-xorg-video-chips 1.1.1-4 X.Org X server -- Chips display driver ii xserver-xorg-video-cirrus1.1.0-3 X.Org X server -- Cirrus display driver ii xserver-xorg-video-cyrix 1.1.0-4 X.Org X server -- Cyrix display driver ii xserver-xorg-video-dummy 0.2.0-3 X.Org X server -- dummy display driver ii xserver-xorg-video-fbdev 0.3.1-1 X.Org X server -- fbdev display driver ii xserver-xorg-video-glint 1.1.1-3 X.Org X server -- Glint display driver ii xserver-xorg-video-i128 1.2.0-3 X.Org X server -- i128 display driver ii xserver-xorg-video-i740 1.1.0-3 X.Org X server -- i740 display driver ii xserver-xorg-video-i810 1.7.2-4 X.Org X server -- Intel i8xx, i9xx display d ii xserver-xorg-video-imstt 1.1.0-3 X.Org X server -- IMSTT display driver ii xserver-xorg-video-mga 1.4.6.1.dfsg.1-2 X.Org X server -- MGA display driver ii xserver-xorg-video-neomagic 1.1.1-5 X.Org X server -- Neomagic display driver ii xserver-xorg-video-newport 0.2.0-3 X.Org X server -- Newport display driver ii xserver-xorg-video-nsc 2.8.1-3 X.Org X server -- NSC display driver ii xserver-xorg-video-nv2.0.2-1 X.Org X server -- NV display driver ii xserver-xorg-video-rendition 4.1.0.dfsg.1-4 X.Org X server -- Rendition display driver ii xserver-xorg-video-s30.4.1-5 X.Org X server -- legacy S3 display driver ii xserver-xorg-video-s3virge 1.9.1-3 X.Org X server -- S3 ViRGE display driver ii xserver-xorg-video-savage2.1.2-3 X.Org X server -- Savage display driver ii xserver-xorg-video-siliconmotion 1.4.1-4 X.Org X server -- SiliconMotion display driv ii xserver-xorg-video-sis 0.9.1-4 X.Org X server -- SiS display driver ii xserver-xorg-video-sisusb0.8.1-3 X.Org X server -- SiS USB display driver ii xserver-xorg-video-tdfx 1.3.0-1 X.Org X server -- tdfx display driver ii xserver-xorg-video-tga 1.1.0-3 X.Org X server -- TGA display driver ii xserver-xorg-video-trident 1.2.3-1 X.Org X server -- Trident display driver ii xserver-xorg-video-tseng 1.1.0-3 X.Org X server -- Tseng display driver ii xserver-xorg-video-v4l 0.1.1-3 X.Org X server -- Video 4 Linux display driv ii xserver-xorg-video-vesa 1.3.0-1 X.Org X server -- VESA display driver ii xserver-xorg-video-vga 4.1.0-3 X.Org X server -- VGA display driver ii xserver-xorg-video-via 0.2.1-6 X.Org X server -- VIA display driver ii xserver-xorg-video-vmware10.13.0-3X.Org X server -- VMware display driver ii xserver-xorg-video-voodoo1.1.0-4 X.Org X server -- Voodoo display driver dpkg -l mplayer\* |grep ^ii ii mplayer 1.0-rc1svn20070225-0.3 The Ultimate Movie Player For Linux ii mplayer-skin-blue 1.6-1 blue skin for mplayer Kernel version is 2.6.21.1, but this also occurs with the current Debian stock-kernel (linux-image-2.6.18-4-686) and 2.6.19.1 and 2.6.20.6 (tested). Using
