Bug#411012: more info
I just modified the control file for compiz 0.3.6-1 from unstable to remove the conflict then recompiled on my sid system and it seems to be working fine. libmetacity-dev/libmetacity0 are at version 1:2.18.2-3. -- James Healy Fri, 11 May 2007 13:45:25 +1000 signature.asc Description: Digital signature
Bug#423090: xserver-xorg-input-evdev: selecting evdev for keyboard driver crashes
severity 423090 important thank you Please don't use very very high severity without a good reason. Obviously, a crash of the X server does not break the whole system. A crash of the X server is generally considered "important". See http://www.debian.org/Bugs/Developer#severities > When selecting evdev for keyboard my Xorg crashes and won't start. It might be related to https://bugs.freedesktop.org/show_bug.cgi?id=5807 However, I think I have seen a case where a wrong config of evdev leads to a crash of the server. Please check your evdev config for the keyboard. The "basic configurations" section of the manpage should help. > Selecting kbd as driver for keyboard nad evdev for mouse, Xorg starts, > but returns wrong keycodes for up key and others. For up key for > example returns Print etc. This looks strange to me. You should be able to use evdev for mouse and kbd for keyboard at the same time. I think lots of people are doing so. Are you sure that your mouse/evdev Section in xorg.conf is correct? If it is wrong, it might be sending random events to the server... I am not familiar with evdev config, but I think you need to add evBits/relBits/... lines as in the manpage examples. > I need evdev driver for mouse, because without it my MX1000 doesn't > return 6,7 for tilt wheel. You might want to look at https://bugs.freedesktop.org/show_bug.cgi?id=5578 for evdev problems with this mouse. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Bug#423090: xserver-xorg-input-evdev: selecting evdev for keyboard driver crashes
Processing commands for [EMAIL PROTECTED]: > severity 423090 important Bug#423090: xserver-xorg-input-evdev: selecting evdev for keyboard driver crashes Severity set to `important' from `critical' > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#372079: DVI on G550, some bad news, some good news
On Tue, May 08, 2007 at 02:45:52PM -0700, t takahashi wrote: > On 5/8/07, Nikolaus Schulz <[EMAIL PROTECTED]> wrote: > >I'll probably try Linux 2.6.18 with matroxfb after upgrading to Etch. > > can you let us on this bug (i seem to be on its forward list, which is > good and i hope will continue to be the case after any mergings) know > the results? Okay, I've tested 2.6.8 on my Sarge testbed for now. DVI indeed works with matroxfb enabled, but without Matrox' hallib there's an annoying flicker. If this cannot be improved with a better kernel configuration or a later kernel, then I won't use it. See below for the kernel configuration I've tested. > i can try the same by setting the right things and installing etch on > a new disk, if i know what to set and can do so without debug > iterations. I do not know if the setup I've tested is entirely correct. > unfortunately, i am too ignorant about x stuff. i don't > even know: > > which kernel option is relevant, > what enabling in the console means, Yeah, I feel pretty much stuck, either. The documentation is not very great here, I think. > whether anything would be required in the x conf file, Don't think so. > what a framebuffer is exactly, *sigh* Yes, I've myself tried to figure that out several times, without success. Well... > and even what "dfp" means. (i guess "digital flat panel".) 'dict dfp' tells me you're right :-) > icih, the last time i tried fixing this was a while back, but it was > probably a 2.6 kernel. here is my current kernel. > > (1) 08-Tue-14-16-11 ~# uname -a;gunzip -c /proc/config.gz | grep -i matrox > Linux debian 2.6.18myver #1 SMP Sun Mar 11 14:33:06 MST 2007 i686 GNU/Linux > CONFIG_FB_MATROX=m Hm, I think this works only compiled in. Not sure, though. (If a module doesn't cut it, then why does the stock Debian kernel provide one?) > # CONFIG_FB_MATROX_MILLENIUM is not set > # CONFIG_FB_MATROX_MYSTIQUE is not set > CONFIG_FB_MATROX_G=y > # CONFIG_FB_MATROX_MULTIHEAD is not set My Kernel 2.6.8 setup with DVI (badly) working: cut here # CONFIG_FB_VGA16 is not set # CONFIG_FB_VESA is not set CONFIG_FB_MATROX=y # CONFIG_FB_MATROX_MILLENIUM is not set # CONFIG_FB_MATROX_MYSTIQUE is not set CONFIG_FB_MATROX_G450=y CONFIG_FB_MATROX_G100=y # CONFIG_FB_MATROX_I2C is not set # CONFIG_FB_MATROX_MULTIHEAD is not set # CONFIG_FB_VIRTUAL is not set CONFIG_FRAMEBUFFER_CONSOLE=y cut here I hope I've got the relevant options. Kernel commandline: video=matroxfb:vesa:0x1BB,fv:60 Here 0x1BB is the code for a 1280x1024 resolution. You will need to tune these for your needs, see /usr/src/linux/Documentation/fb/matroxfb.txt for your options. Nikolaus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xorg-server: Changes to 'debian-unstable'
debian/changelog |7 +++
debian/patches/24_hurd_ioperm_fix.diff | 64 +
debian/patches/series |1
3 files changed, 72 insertions(+)
New commits:
commit 6d548942f58f6e6ff0ac89f82100c0bb056d9499
Author: Brice Goglin <[EMAIL PROTECTED]>
Date: Fri May 11 02:45:25 2007 +0200
Add 24_hurd_ioperm_fix.diff to fix xf86Enable/DisableIO on Hurd with recent
GNU Mach.
diff --git a/debian/changelog b/debian/changelog
index 63eb057..c38ff5e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+xorg-server (2:1.3.0.0.dfsg-5) UNRELEASED; urgency=low
+
+ * Add 24_hurd_ioperm_fix.diff to fix xf86Enable/DisableIO on Hurd with
+recent GNU Mach. Thanks Samuel Thibault!
+
+ -- Brice Goglin <[EMAIL PROTECTED]> Fri, 11 May 2007 02:37:19 +0200
+
xorg-server (2:1.3.0.0.dfsg-4) unstable; urgency=low
* Cherry-pick patch from upstream git to fix security issue in the Xrender
diff --git a/debian/patches/24_hurd_ioperm_fix.diff
b/debian/patches/24_hurd_ioperm_fix.diff
new file mode 100644
index 000..d2ff452
--- /dev/null
+++ b/debian/patches/24_hurd_ioperm_fix.diff
@@ -0,0 +1,64 @@
+--- a/hw/xfree86/os-support/hurd/hurd_video.c.orig 2007-05-08
18:28:21.000842117 +
b/hw/xfree86/os-support/hurd/hurd_video.c 2007-05-08 18:27:37.000381314
+
+@@ -117,49 +117,29 @@
+ /**
+ * I/O Permissions section
+ ***/
+-mach_port_t io_port;
++
++/*
++ * Due to conflicts with "compiler.h", don't rely on to declare
++ * this.
++ */
++extern int ioperm(unsigned long __from, unsigned long __num, int __turn_on);
+
+ Bool
+ xf86EnableIO()
+ {
+-mach_port_t device;
+-kern_return_t err;
+-
+-err = get_privileged_ports(NULL, &device);
+-if( err )
+-{
+- errno = err;
+- FatalError("xf86EnableIO() can't get_privileged_ports.
(%s)\n",strerror(errno));
+-}
+-err = device_open(device,D_READ|D_WRITE,"io",&io_port);
+-mach_port_deallocate(mach_task_self(), device);
+-if( err )
+-{
+- errno = err;
+- FatalError("xf86EnableIO() can't device_open. (%s)\n",strerror(errno));
+-}
+-
+-err = i386_io_port_add(mach_thread_self (), io_port);
+-if( err )
+-{
+- errno = err;
+- FatalError("xf86EnableIO() can't i386_io_port_add.(io_port)
(%s)\n",strerror(errno));
++if (ioperm(0, 0x, 1)) {
++ FatalError("xf86EnableIO: ioperm() failed (%s)\n", strerror(errno));
++ return FALSE;
+ }
++ioperm(0x40,4,0); /* trap access to the timer chip */
++ioperm(0x60,4,0); /* trap access to the keyboard controller */
+ return TRUE;
+ }
+
+ void
+ xf86DisableIO()
+ {
+-kern_return_t err;
+-
+-err = i386_io_port_remove(mach_thread_self (), io_port);
+-if( err )
+-{
+- errno = err;
+- FatalError("xf86DisableIO() can't i386_io_port_remove.(io_port)
(%s)\n",strerror(errno));
+-}
+-mach_port_deallocate(mach_task_self(), io_port);
++ioperm(0,0x,0);
+ return;
+ }
+
diff --git a/debian/patches/series b/debian/patches/series
index e5b2a45..0a454ae 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -12,6 +12,7 @@
16_s390_fix.diff
21_glx_align_fixes.patch
23_kfreebsd_support.diff
+24_hurd_ioperm_fix.diff
32_disable_sparc_pci_bridge.diff
34_xorg.conf_man_typos.patch
39_alpha_build_flags.patch -p0
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 211765 to xorg-server, merging 211765 368564
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.4 > reassign 211765 xorg-server Bug#211765: xfree86: material under GLX Public License and SGI Free Software License B is not DFSG-free Bug reassigned from package `xserver-xorg' to `xorg-server'. > merge 211765 368564 Bug#211765: xfree86: material under GLX Public License and SGI Free Software License B is not DFSG-free Bug#368564: xorg-server: material under GLX Public License and SGI Free Software License B is not DFSG-free Merged 211765 368564. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#179647: SIGALRM spinning still exists
reassign 179647 xserver-xorg-core found 179647 2:1.3.0.0.dfsg-4 severity 179647 normal thanks On Thu, 10 May 2007, Brice Goglin wrote: > Don Armstrong wrote: > > Yeah, most likely. The annoying thing is that it only occurs > > randomly, and when it just happened I didn't have enough time to > > trigger a core dump and really check it out. [Had to get some > > "real" work done. ;-)] > > > > Which xserver-xorg-core are you using? I will reassign the bug > accordingly then. There's only one, and I've reassigned it. > Could you send the output of > /usr/share/bug/xserver-xorg-core/script 3>&1 > so that we see your config and log? There's nothing terribly useful in them; the machine is using xinerama which is the only "odd thing", but I've attached them anyway. > The log right after a crash might help too, but the best would be a > backtrace from either attaching gdb before the crash (through ssh) > or later with a coredump (see [1] for details). Clearly; if I had time I would have done this. Next time it happens I'll trigger a core. Don Armstrong -- Your village called. They want their idiot back. -- xkcd http://xkcd.com/c23.html http://www.donarmstrong.com http://rzlab.ucr.edu Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2006-04-13 19:30 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1698800 2007-05-09 02:59 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 05:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400/G450 (rev 85) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 4949 2006-07-22 17:10 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (Xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the 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 commands as root: # # cp /etc/X11/xorg.conf /etc/X11/xorg.conf.custom # md5sum /etc/X11/xorg.conf >/var/lib/xfree86/xorg.conf.md5sum # dpkg-reconfigure xserver-xorg Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/share/fonts/X11/CID" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/share/fonts/X11/75dpi" EndSection Section "Module" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "false" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "MGA" Driver "mga" BusID "PCI:05:00:00" Screen 0 Option "AGPMode" "1" Option "OldDmaInit" "On" Option "MGASDRAM" "True" Option "PciRetry" "true" Option "NoHal""true" # Option "Overlay" "8,24" Option "TexturedVideo" "true" # Option "UseFBDev" "true" Option "ForcePCIDma" "true" EndSection Section "Device" Identifier "MGA2" Driver "mga" BusID "PCI:05:00:00" # Comment out screen 1 below to mirror Screen 1 Option "AGPMode" "1" Option "OldDmaI
Processed: Re: Bug#179647: SIGALRM spinning still exists
Processing commands for [EMAIL PROTECTED]: > reassign 179647 xserver-xorg-core Bug#179647: xserver-xfree86: SIGALRM spinlock freezes X server Bug reassigned from package `xserver-xfree86' to `xserver-xorg-core'. > found 179647 2:1.3.0.0.dfsg-4 Bug#179647: xserver-xfree86: SIGALRM spinlock freezes X server Bug marked as found in version 2:1.3.0.0.dfsg-4. > severity 179647 normal Bug#179647: xserver-xfree86: SIGALRM spinlock freezes X server Severity set to `normal' from `important' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324500: mga: G550 Dualhead
Adrian von Bidder wrote: > * after boot, only one screen is active (same as before). Switching to > Text mode and back solves this problem. > * which monitor is seen at which port, and signal for which monitor is > generated to which port, has apparently been randomly switched around. > > My setup is a Hitachi and a BenQ, I usually drive the Hitachi at 1440x1080 > (picture gets very bad at 1600x1200 though it's in the specs...), the BenQ > at 1280x1024 (TFT, hardware res). > > With the xorg.conf below, the best I can get is the BenQ running just fine > and the Hitachi running at a ghastly 1440x1050 at 60Hz, within the clock > spec of the BenQ. I could, of course, give the video signal destined for > the Hitachi to the BenQ but it doesn't like that much. In other words: > apparently the DDC monitor detection applies to the wrong video output. > (Is there no option to just tell Xorg to generate 200MHz even though it > thinks the monitor only does 140MHz?) > > Swapping the "Screen 0" and "Screen 1" identifiers gives me variations on > the same topic, as does physically swapping monitor plugs. But one thing > stays: the right video signal is never generated for the correct monitor. > Fortunately, the upcoming randr 1.2 support for MGA might help for all this. > Oh, yeah: moving back to just the old mga_drv.so does *not* work, this time, > so I fear the bug is somewhere deeper in Xorg this time :-/ > It might be related to the upgrade of xserver-xorg-core 1.3 currently in unstable. Could you try to downgrade to xserver-xorg-core 2:1.1.1-21 (the one in Etch/stable and testing)? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#390630: With xserver-xorg-video-savage 1:2.1.2-5 and EXA X.org shows garbled display
Martin Steigerwald wrote: > Yes. It also hangs with XAA disabled. > You mean EXA disabled and XAA enabled? Or XAA and EXA disabled (ie NoAccel)? > KDM after reboot is working correctly. Its about KDM after logout. It > doesn't display a login screen then. > > I was logged into the machine via SSH to be able to do some diagnostics > and I tried /etc/init.d/kdm restart in order to get a login screen. Then > it told me that KDM was not running before it tried to start it again. > Starting it again didn't work also. I have to reboot the machine twice > cause of that. > You should try to start X without kdm in this case. Sometimes, the display manager has trouble when trying to restart because a problem occurred during the previous stop. Something like 'startx /usr/bin/xterm' is good way to check to X server. > I am using VESA framebuffer driver, not the Savage one, cause I read von > savage mailinglist that the framebuffer driver and the X.org one do not > handle resetting registers gracefully. > > I am using this self compiled kernel > > [EMAIL PROTECTED]:~> cat /proc/version > Linux version 2.6.21.1-tp23-cfs-v11-sws2-2.2.9.13 ([EMAIL PROTECTED]) (gcc > version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 PREEMPT Thu May > 10 14:40:21 CEST 2007 > > with these kernel options: > > root=/dev/sda5 ro resume2=swap:/dev/sda7 resume=/dev/sda7 vga=792 > atapi_enabled=1 > You could possibly try with a regular kernel without any framebuffer driver, but I am not sure it will help here. > I just could use a bit of guidance on how to proceed with testing and > reporting and I will take the time to do so as could as I can without > neglecting higher priority stuff. > It's hard to distinguish all the problems here. EXA should probably be avoided for the beginning. And the respawn problem after logout debugged first. If you want to debug all this, it would probably be easier to discuss directly with upstream, assuming you find a maintainer that really wants to work on it... Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409289: marked as done (xserver-xorg-video-nv: xserver-x.org becomes sluggish and keyboard unresponsive)
Your message dated Fri, 11 May 2007 01:30:13 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#409289: xserver-xorg-video-nv: xserver-x.org becomes sluggish and keyboard unresponsive has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xorg-video-nv Version: 1:1.2.0-3 Severity: normal Fresh, New Etch install as of 1/25 - from daily build CD All updates taken (libc6, locales) this AM and rebooted xorg takes up 99.7% of CPU as reported by TOP xorg sluggish or has "Dramatic pauses" when using IceDove xorg locked up in rdesktop session after 2 minutes of using it mouse pointer moves, clicks do nothing, keyboard locked up. Couldnt ctrl-alt-f1 into console. Had to remotely log in with ssh and kill xorg This system is a Dell Precision 370 lspci output: io:/net/home/mbw/admin# lspci 00:00.0 Host bridge: Intel Corporation 925X/XE Express Memory Controller Hub (rev 04) 00:01.0 PCI bridge: Intel Corporation 925X/XE Express PCI Express Root Port (rev 04) 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3) 00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FR/FRW (ICH6R/ICH6RW) SATA Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: nVidia Corporation NV37GL [Quadro FX 330/Quadro NVS280] (rev a2) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01) io:/net/home/mbw/admin# -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg-video-nv depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii xserver-xorg-core 2:1.1.1-15 X.Org X server -- core server xserver-xorg-video-nv recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Matt Weatherford wrote: > > Brice, > > Im using the Etch Stable release now on x86 hardware with the NVidia > card, > it seems to be ok... sometimes I get dramatic pauses in Icedove, but > im not sure what app is responsible for that & havent had a chance to > profile it. > > I dont use unstable. > > Thanks for asking... I hope you find some good testers for this. Ok thank you for replying. I am closing this bug for now since there doesn't seem to be any actual bug anymore. If anybody ever reproduces, feel free to reopen. Thanks, Brice --- End Message ---
Bug#377847: xserver-xorg-video-nv: No way to set 1600x1200 resolution.
Sergei Organov wrote: > Brice Goglin <[EMAIL PROTECTED]> writes: > >> Hi, >> >> Several months ago, you reported a bug to the Debian BTS regarding the >> nv driver refusing to set 1600x1200 resolution. Did you reproduce this >> problem recently? With the latest xserver-xorg-video-nv driver 2.0.2 in >> unstable? >> > > Sorry, I didn't check 2.0.2 as I'm running "testing" where > xserver-xorg-video-nv package is at version 1:1.2.0-3. > You were using driver 1:1.0.1.5-2 when you reported the bug. Does it still happen with your current 1:1.2.0-3 driver ? If you ever have a chance to upgrade to 2.0.2 or later, either by taking packages in unstable, or by rebuilding it against Etch, please let us know if the bug gets fixed. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: retitle 391872 to xserver-xorg-video-mga: rendering artifacts with GL applications
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.2 > retitle 391872 xserver-xorg-video-mga: rendering artifacts with GL > applications Bug#391872: compiz: Compiz makes my computer lock up - only hard reboot possible Changed Bug title to xserver-xorg-video-mga: rendering artifacts with GL applications from compiz: Compiz makes my computer lock up - only hard reboot possible. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422077: xserver-xorg: Fatal server error on sparc: xf86MapPciMem failed
Here's a summary of what happen about this PCI breakage during the last days: Since umount /sys fixed the problem, it is clear that the bug is in the sys-based PCI domain code. Jim rebuilt the server using David Woodhouse's patch [1] which is applied in Fedora and disables the sysfs code on architecture that don't have PCI domains. However, it didn't fix anything (apparently because sparc exports domain number in /proc/bus/pci/ even if when there is no actual domains). So Jim replaced the patch with the following one, which disables the sysfs code on all architectures and it worked: --- xorg-server-1.3.0.0.dfsg.orig/hw/xfree86/os-support/bus/linuxPci.c 2007-05-10 21:51:55.0 +0200 +++ xorg-server-1.3.0.0.dfsg/hw/xfree86/os-support/bus/linuxPci.c 2007-05-10 21:52:13.0 +0200 @@ -148,7 +148,7 @@ int domain, bus, dev, func; charfile[64]; struct stat ignored; - static int is26 = -1; + static int is26 = 0; domain = PCI_DOM_FROM_TAG(tag); bus = PCI_BUS_NO_DOMAIN(PCI_BUS_FROM_TAG(tag)); In the meantime, David Miller told me he needed a patch like this one and some others (sometimes ugly) to get Xorg and the Radeon driver to work on his sparc. Mathias Hopf also applies this patch for powerpc in Suse. By the way, about powerpc, #422095 is probably fixed by this patch too (since the problem disappears when /sys is umounted). Upstream did not apply it because they want to fix the sysfs-code instead of reverting to the old /proc code. However, they didn't say anything bad about this patch (see [2], comments #21 and below). Also, Bill Nottingham (who committed the sysfs code) told me that it is just an optimization and should not fix anything. So disabling it entirely should be fine. I just tried it on x86 without seeing any breakage. So, we have different solutions: a) Always use sysfs, as currently: Breaks at least on sparc, and probably on powerpc too. b) No sysfs on any arch: Apply the patch above and assume it won't break on any arch. c) No sysfs only when it is known to break in Debian: Apply the patch above only for sparc to fix #422077 for now, and possibly to powerpc once somebody confirms that it fixes #422095 too. d) No sysfs on arch that got problems (not only in Debian): Apply the patch above for sparc and powerpc, and also [1] since it fixed some problems in Fedora. I know some people are afraid of touching the PCI code, but since nobody found an actual problem with (b), I would vote for (b) and see what happens (revert to (c) or (d) if something ever breaks). Thanks again to Jim for spending hours to rebuild the server several times on his sparc :) Brice [1] http://david.woodhou.se/xorg-x11-server-1.2.99-unbreak-domain.patch [2] https://bugs.freedesktop.org/show_bug.cgi?id=7248 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#423255: Laptop Crash Following Hibernation/Suspension
On Thu, May 10, 2007 at 17:53:15 -0400, Craig Huffstetler wrote: > Error/Problem: On Lenovo Z60m (among other laptops this was tested on) after > hibernation and/or shutting the laptop the screen/session of Xorg crashes > and a full restart is required. > Please run "/usr/share/bug/xserver-xorg-core/script 3>&1" and send the output to this bug. Thanks, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#423255: Laptop Crash Following Hibernation/Suspension
Package: xorg-server Version: 7.1.1 Linux tiny 2.6.18-4-686 #1 SMP Wed Apr 18 09:55:10 UTC 2007 i686 GNU/Linux APT-Prefers: stable Attached please find dmsg and lspci-vvnn. Error/Problem: On Lenovo Z60m (among other laptops this was tested on) after hibernation and/or shutting the laptop the screen/session of Xorg crashes and a full restart is required. Craig Huffstetler | xarquid | xq [EMAIL PROTECTED] -- Craig Huffstetler Linux version 2.6.18-4-686 (Debian 2.6.18.dfsg.1-12etch1) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Wed Apr 18 09:55:10 UTC 2007 BIOS-provided physical RAM map: BIOS-e820: - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 000d - 000d4000 (reserved) BIOS-e820: 000dc000 - 0010 (reserved) BIOS-e820: 0010 - 7f6e (usable) BIOS-e820: 7f6e - 7f6f5000 (ACPI data) BIOS-e820: 7f6f5000 - 7f70 (ACPI NVS) BIOS-e820: 7f70 - 8000 (reserved) BIOS-e820: e000 - f000 (reserved) BIOS-e820: f0008000 - f000c000 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fed14000 - fed1a000 (reserved) BIOS-e820: fed2 - fed9 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ff00 - 0001 (reserved) 1142MB HIGHMEM available. 896MB LOWMEM available. On node 0 totalpages: 521952 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 225280 pages, LIFO batch:31 HighMem zone: 292576 pages, LIFO batch:31 DMI present. ACPI: RSDP (v002 IBM ) @ 0x000f6a90 ACPI: XSDT (v001 IBMTP-770x1220 LTP 0x) @ 0x7f6e670a ACPI: FADT (v003 IBMTP-770x1220 IBM 0x0001) @ 0x7f6e6800 ACPI: SSDT (v001 IBMTP-770x1220 MSFT 0x010e) @ 0x7f6e69b4 ACPI: ECDT (v001 IBMTP-770x1220 IBM 0x0001) @ 0x7f6f4dd9 ACPI: TCPA (v001 IBMTP-770x1220 PTL 0x0001) @ 0x7f6f4e2b ACPI: MADT (v001 IBMTP-770x1220 IBM 0x0001) @ 0x7f6f4e5d ACPI: MCFG (v001 IBMTP-770x1220 IBM 0x0001) @ 0x7f6f4eb7 ACPI: BOOT (v001 IBMTP-770x1220 LTP 0x0001) @ 0x7f6f4fd8 ACPI: DSDT (v001 IBMTP-770x1220 MSFT 0x010e) @ 0x ACPI: PM-Timer IO Port: 0x1008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 6:13 APIC version 20 ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 8800 (gap: 8000:6000) Detected 1496.342 MHz processor. Built 1 zonelists. Total pages: 521952 Kernel command line: root=/dev/mapper/tiny-root ro mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 16384 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 2061136k/2087808k available (1544k kernel code, 25384k reserved, 577k data, 196k init, 1170304k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 2995.85 BogoMIPS (lpj=5991700) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: afe9fbff 0010 CPU: After vendor identify, caps: afe9fbff 0010 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 1024K CPU: After all inits, caps: afe9fbff 0010 0040 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to e000. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 16k freed ACPI: Core revision 20060707 CPU0: Intel(R) Celeron(R) M processor 1.50GHz stepping 08 Total of 1 processors activated (2995.85 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 Brought up 1 CPUs migration_cost=0 checking if image is initramfs... it is Freeing initrd memory: 5557k
Processed: bug 422077 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=7248 ...
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.2 > forwarded 422077 https://bugs.freedesktop.org/show_bug.cgi?id=7248 Bug#422077: xserver-xorg: Fatal server error on sparc: xf86MapPciMem failed Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=7248. > forwarded 422095 https://bugs.freedesktop.org/show_bug.cgi?id=7248 Bug#422095: xserver-xorg-core: fails to start, no devices detected Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=7248. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#422353: tcm - FTBFS: error: conflicts with new declaration with 'C' linkage
Processing commands for [EMAIL PROTECTED]: > reassign 422353 libxt-dev Bug#422353: tcm - FTBFS: error: conflicts with new declaration with 'C' linkage Bug reassigned from package `tcm' to `libxt-dev'. > found 422353 1:1.0.5-2 Bug#422353: tcm - FTBFS: error: conflicts with new declaration with 'C' linkage Bug marked as found in version 1:1.0.5-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 [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#390630: With xserver-xorg-video-savage 1:2.1.2-5 and EXA X.org shows garbled display
Am Donnerstag 10 Mai 2007 schrieb Brice Goglin: > Hi Martin, > > Thanks you for your answers, but it is not clear for me whether the > initial bug report is fixed on not. So: > Does Xorg still hang on logout ? even with EXA *disabled* ? Hello Brice! Yes. It also hangs with XAA disabled. > > Well, no, KDM doesn't start at all. X is running, but the garbled > > display actually was tty1. Rebooted now. > Why would KDM refuse to start at all if X is running? Or is KDM running > but not displaying anything because of a problem in X? > What about this problem if EXA is *disabled*? > Are you talking of KDM right after logout, or KDM after reboot? KDM after reboot is working correctly. Its about KDM after logout. It doesn't display a login screen then. I was logged into the machine via SSH to be able to do some diagnostics and I tried /etc/init.d/kdm restart in order to get a login screen. Then it told me that KDM was not running before it tried to start it again. Starting it again didn't work also. I have to reboot the machine twice cause of that. > > Anyway, EXA does not seem to be usable. > > This looks like a different issue, we should open a new bug about this. > Some screen corruptions on savage with EXA have been reported upstream > at [1]. Does the screenshot [2] look like what you are seeing? Not quite... I attached a screenshot to my last mail to this bug report. Should I open a new bug report or should we clone this one? Actually I had this screen corruption even without EXA. But it just happened once I tried to logout and tried to restart KDM or when I tried to switch between TTY1 and X after I tried to logout. It has gotten worse, cause with the older version I restarting KDM brought the login screen back. Now I get that complete screen garbage and have to reboot the machine as soon as I need more than a SSH login to it. I am using VESA framebuffer driver, not the Savage one, cause I read von savage mailinglist that the framebuffer driver and the X.org one do not handle resetting registers gracefully. I am using this self compiled kernel [EMAIL PROTECTED]:~> cat /proc/version Linux version 2.6.21.1-tp23-cfs-v11-sws2-2.2.9.13 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 PREEMPT Thu May 10 14:40:21 CEST 2007 with these kernel options: root=/dev/sda5 ro resume2=swap:/dev/sda7 resume=/dev/sda7 vga=792 atapi_enabled=1 I did my testing after a fresh boot, so there has not been a snapshot cycle before that. I sent a mail to upstream mailinglist, mentioning my bug report. I am a bit unsure on how to go on. It seems there are several issues and it would be good to isolate them and put them into different bug reports. There are a lot of different combinations to test and it will be difficult for me to take enough time to do this testing. That said, the issues are not really urgent to me - so we could go through it step by them and take the time it needs. Since I got an T42 my T23 mainly serves as Amarok based music jukebox and as long as graphics display works after a snapshot cycle it will work for me. I only need 2D graphics anyway. I just could use a bit of guidance on how to proceed with testing and reporting and I will take the time to do so as could as I can without neglecting higher priority stuff. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 pgpGFJQzZbZdV.pgp Description: PGP signature
Bug#423014: console's last three lines become inaccessible once xdm start up
Hi again Julien, Everone else went home, so I have a chance to break things^W^W experiment. Upon re-booting and actually checking what resize and $LINES say when the X server hasn't messed things up, I find that I've mis-described this bug. The normal state does in fact have 28 lines; when the X server starts up, something causes the console to be only able to display 25 of them; I think these are slightly taller, since they fill the same amount of screen. None the less, screen resizing via the hardware controls doesn't help. So something has changed the console - maybe its font ? Any idea how I can ask it about that ? So, sorry about having it partially back-to front; but the same consequences flow from it ! >> I'm guessing that if I run dpkg-reconfigure on the xserver package, >> it'll ask me to select a driver and I can change from vesa to i810. > > That, or replace vesa with i810 in /etc/X11/xorg.conf and restart X. I had to reboot anyway (to restore normal mode), so might as well use the brute force approach and let the system do any updates it deems prudent. This also meant that I saw that the part of the configuration which offered me a choice between using the frame buffer and not using it was set to not use it. I left it that way. Interestingly, the reconfigure has put my Modes lines into the usual order, with 1600x1200 first, and xdm has no problem starting up; so clearly whatever problem it was having (before I bodged the order as described previously) has been solved. >> Please suggest a command that'll reveal whether I have an fb console. > Maybe lsmod will show whether a fb driver is loaded. lsmod | grep fb yielded no output. The full output of lsmod contained 58 lines but I have no delusions of understanding it. Do you want to see it all ? lsmod | grep i810 yielded i810_audio 32916 0 ac97_codec 17196 1 i810_audio soundcore 9248 2 i810_audio,snd Rebooting without xdm (and confirming that I was still in normal mode), I logged in as a non-privileged user (me) and ran startx (with no args); it started up X just fine, and all my consoles went into "only displaying 25 lines" mode, as before. So your guess that xdm is not the culprit is vindicated. I'm now running (and was when testing startx) with Section "Device" Identifier "Intel Corporation 82915G/GV/910GL Integrated Graphics Controller" Driver "i810" BusID "PCI:0:2:0" EndSection and I still get the (++) using VT number 7 (WW) xf86OpenConsole: setpgid failed: Operation not permitted (WW) xf86OpenConsole: setsid failed: Operation not permitted which you deemed weird earlier. If you want full output from your earlier script, just ask and I can do that again. Eddy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362434: xserver-xorg-video-nv: nv has problems with xcursor-themes
Package: xserver-xorg-video-nv Version: 1:2.0.2-1 Followup-For: Bug #362434 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just an update, the bug is still there in the latest version available. - -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target unchanged from checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2006-04-12 14:05 /etc/X11/X -> /usr/bin/Xorg - -rwxr-xr-x 1 root root 1698800 2007-05-09 11:59 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 03:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800] (rev a1) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: - -rw-r--r-- 1 root root 3795 2007-05-10 20:52 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (Xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the 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 commands as root: # # cp /etc/X11/xorg.conf /etc/X11/xorg.conf.custom # md5sum /etc/X11/xorg.conf >/var/lib/xfree86/xorg.conf.md5sum # dpkg-reconfigure xserver-xorg Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/share/fonts/X11/75dpi" # path to defoma fonts FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" Load"bitmap" Load"dbe" Load"ddc" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"type1" Load"v4l" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" Option "XkbVariant""nodeadkeys" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "false" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Ati-Remote" Driver "mouse" Option "Device""/dev/lircm" Option "Protocol" "IntelliMouse" Option "SendCoreEvents" EndSection Section "Device" Identifier "NVIDIA Corporation NV40 [GeForce 6800]" Driver "nvidia" BusID "PCI:3:0:0" Option "HWCursor" "true" Option "RenderAccel" "true" Option "AllowGLXWithComposite" "true" Option "NoLogo""true" Option "AddARGBGLXVisuals" "true" Option "TwinView" "true" Option "TwinViewOrientation" "RightOf" Option "MetaModes" "1280x1024,1280x1024; 1024x768,1024x768" Option "ConnectedMonitors" "DFP,DFP" EndSection #Section "Device" # Identifier "NVIDIA Corporation NV40 [GeForce 6800]" # Driver "nv" # Option "HWCursor" "true" #EndSection Section "Extensions" Option "Composite" "Enable" EndSection Section "Monitor" Identifier "Standardbildschirm" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "NVIDIA Corporation NV40 [GeForce 6800]" Monitor "Standardbildschirm" DefaultDepth24 SubSection "Display" Depth 1
Bug#392312: xserver-xorg-core: [sparc] Freezes system and causes severe data loss
> it seems that the bug is back in the experimental version of this package. > please see: > https://launchpad.net/ubuntu/+source/xorg-server/+bug/93041 I don't think it is related to this bug. I don't see anything about a freeze or data loss in the Ubuntu bug above. I would rather say that it is related to #422077. So, to be clear, I don't think anybody reproduced the freeze+dataloss since the patch has been applied in the Debian package, even in Xserver 1.3. And, by the way, the fix finally got committed upstream today. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420281: xserver-xorg-video-intel: xv playback crashes X server
Brice Goglin wrote: > [EMAIL PROTECTED] wrote: >> Yes, please apply those patches. >> > > These patches didn't get applied upstream and I am not even sure they > got reviewed by the maintainer of the Intel driver. It looks like they > fix a crash, but [1] says that the XV overlay is always on LVDS (while > it was always to VGA before). So even if they improve things, they don't > look very good to me. > > I would rather at least wait for upstream's opinion before applying > anything. > > Brice > > [1] https://bugs.freedesktop.org/show_bug.cgi?id=10466 > Upstream has said that they are not clean enough for inclusion, and that they will be doing a proper fix. However, upstream did not say there was anything particularly broken about the patches. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#179647: SIGALRM spinning still exists
Don Armstrong wrote: > On Thu, 10 May 2007, Michel Dänzer wrote: > >> On Thu, 2007-05-10 at 02:30 -0700, Don Armstrong wrote: >> >>> I still am seeing this bug occasionally, although not as recently as >>> previously. [I just ran into it a few minutes ago while using >>> xdosemu.] >>> >> Could be https://bugs.freedesktop.org/show_bug.cgi?id=10747 . >> > > Yeah, most likely. The annoying thing is that it only occurs randomly, > and when it just happened I didn't have enough time to trigger a core > dump and really check it out. [Had to get some "real" work done. ;-)] > Which xserver-xorg-core are you using? I will reassign the bug accordingly then. Could you send the output of /usr/share/bug/xserver-xorg-core/script 3>&1 so that we see your config and log? The log right after a crash might help too, but the best would be a backtrace from either attaching gdb before the crash (through ssh) or later with a coredump (see [1] for details). Thanks, Brice [1] http://wiki.debian.org/XStrikeForce/XserverDebugging
Bug#423014: console's last three lines become inaccessible once xdm start up
On Thu, May 10, 2007 at 17:31:34 +0200, Edward Welbourne wrote: > >> Section "Device" > >>Identifier "Intel 82915G/GV/910GL" > >>Driver "vesa" > >>BusID "PCI:0:2:0" > >> EndSection > >> > > Did you try the "i810" driver instead of "vesa"? > > Also, do you use a fb console? > > This is the point where I should point out that I am not a sysadmin. > (I *have* been using X since the early '90s, so I can work out how to > use startx manually, though.) > > Consequently, it'll be worth going into slightly more detail when > asking me for more information, so I know what to do to discover the > answers you need. Relevant command-lines should suffice. > > I'm guessing that if I run dpkg-reconfigure on the xserver package, > it'll ask me to select a driver and I can change from vesa to i810. > That, or replace vesa with i810 in /etc/X11/xorg.conf and restart X. > However, I've no idea how to find out whether I'm using an fb console. > I have six virtual consoles and an X session, accessible by Alt+F[1-7], > with help from Ctrl if coming from the X session. > Please suggest a command that'll reveal whether I have an fb console. > Maybe lsmod will show whether a fb driver is loaded. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#390630: With xserver-xorg-video-savage 1:2.1.2-5 and EXA X.org shows garbled display
Hi Martin, Thanks you for your answers, but it is not clear for me whether the initial bug report is fixed on not. So: Does Xorg still hang on logout ? even with EXA *disabled* ? > Well, no, KDM doesn't start at all. X is running, but the garbled display > actually was tty1. Rebooted now. > Why would KDM refuse to start at all if X is running? Or is KDM running but not displaying anything because of a problem in X? What about this problem if EXA is *disabled*? Are you talking of KDM right after logout, or KDM after reboot? > Anyway, EXA does not seem to be usable. > This looks like a different issue, we should open a new bug about this. Some screen corruptions on savage with EXA have been reported upstream at [1]. Does the screenshot [2] look like what you are seeing? Brice [1] https://bugs.freedesktop.org/show_bug.cgi?id=10037 [2] https://bugs.freedesktop.org/attachment.cgi?id=8784&action=view -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420281: xserver-xorg-video-intel: xv playback crashes X server
[EMAIL PROTECTED] wrote: > Yes, please apply those patches. > These patches didn't get applied upstream and I am not even sure they got reviewed by the maintainer of the Intel driver. It looks like they fix a crash, but [1] says that the XV overlay is always on LVDS (while it was always to VGA before). So even if they improve things, they don't look very good to me. I would rather at least wait for upstream's opinion before applying anything. Brice [1] https://bugs.freedesktop.org/show_bug.cgi?id=10466 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xserver-xorg-video-intel: Changes to 'debian-unstable'
debian/changelog |3 ++- debian/control |4 ++-- 2 files changed, 4 insertions(+), 3 deletions(-) New commits: commit 80399c57cff82dd56ea8eeca261187c55e2ee2d4 Author: Julien Cristau <[EMAIL PROTECTED]> Date: Thu May 10 18:11:54 2007 +0200 Mention i965 chipsets in the long description. diff --git a/debian/changelog b/debian/changelog index 10cab2d..0a303e9 100644 --- a/debian/changelog +++ b/debian/changelog @@ -3,11 +3,12 @@ xserver-xorg-video-intel (2:2.0.0-2) UNRELEASED; urgency=low [ Julien Cristau ] * Build xserver-xorg-video-i810 in binary-indep instead of binary-arch (closes: #420240). Thanks, Aaron M. Ucko! + * Mention i965 chipsets in the long description. [ Timo Aaltonen ] * Replaces/Conflicts: xserver-xorg-driver-i810. - -- Timo Aaltonen <[EMAIL PROTECTED]> Tue, 24 Apr 2007 13:30:27 +0300 + -- Julien Cristau <[EMAIL PROTECTED]> Thu, 10 May 2007 18:11:11 +0200 xserver-xorg-video-intel (2:2.0.0-1) unstable; urgency=low diff --git a/debian/control b/debian/control index ebde864..d6fb06e 100644 --- a/debian/control +++ b/debian/control @@ -16,8 +16,8 @@ Replaces: xserver-xorg (<< 6.8.2-35), xserver-xorg-video-i810 (<< 2:1.9.91-1), x Conflicts: xserver-xorg-video-i810 (<< 2:1.9.91-1), xserver-xorg-video-i810-modesetting, xserver-xorg-video-intel-modesetting, xserver-xorg-driver-i810 Description: X.Org X server -- Intel i8xx, i9xx display driver This package provides the driver for the Intel i8xx and i9xx family - of chipsets, including i810, i815, i830, i845, i855, i865, i915, and - i945 series chips. + of chipsets, including i810, i815, i830, i845, i855, i865, i915, i945 + and i965 series chips. . This package also provides an XvMC (XVideo Motion Compensation) driver for the same chipsets. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 423129 is serious ...
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.4 > severity 423129 serious Bug#423129: Undefined symbol prevents glint driver from loading Severity set to `serious' from `normal' > forwarded 423129 https://bugs.freedesktop.org/show_bug.cgi?id=10906 Bug#423129: Undefined symbol prevents glint driver from loading Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=10906. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#423014: console's last three lines become inaccessible once xdm start up
>> Section "Device" >> Identifier "Intel 82915G/GV/910GL" >> Driver "vesa" >> BusID "PCI:0:2:0" >> EndSection >> > Did you try the "i810" driver instead of "vesa"? > Also, do you use a fb console? This is the point where I should point out that I am not a sysadmin. (I *have* been using X since the early '90s, so I can work out how to use startx manually, though.) Consequently, it'll be worth going into slightly more detail when asking me for more information, so I know what to do to discover the answers you need. Relevant command-lines should suffice. I'm guessing that if I run dpkg-reconfigure on the xserver package, it'll ask me to select a driver and I can change from vesa to i810. However, I've no idea how to find out whether I'm using an fb console. I have six virtual consoles and an X session, accessible by Alt+F[1-7], with help from Ctrl if coming from the X session. Please suggest a command that'll reveal whether I have an fb console. > This is weird... ah. Well, let's see where it goes ... Thanks for your help, Eddy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#423014: console's last three lines become inaccessible once xdm start up
On Thu, May 10, 2007 at 16:18:03 +0200, Edward Welbourne wrote: > Julien Cristau <[EMAIL PROTECTED]> said: > > > Please send the output of /usr/share/bug/xserver-xorg-core/script 3>&1 > > to this bug. > > Output follows. > I'll attempt the startx experiment when I'm a little less busy (it > involves re-booting, disrupting my access to e-mail from colleagues > needing help ...) > Thanks. > Section "Device" > Identifier "Intel 82915G/GV/910GL" > Driver "vesa" > BusID "PCI:0:2:0" > EndSection > Did you try the "i810" driver instead of "vesa"? Also, do you use a fb console? > Contents of most recent Xorg X server log file > /var/log/Xorg.0.log: > > X Window System Version 7.1.1 > Release Date: 12 May 2006 > X Protocol Version 11, Revision 0, Release 7.1.1 > Build Operating System: UNKNOWN > Current Operating System: Linux whorl 2.6.18-4-686 #1 SMP Wed Apr 18 09:55:10 > UTC 2007 i686 > ... > (++) using VT number 7 > > (WW) xf86OpenConsole: setpgid failed: Operation not permitted > (WW) xf86OpenConsole: setsid failed: Operation not permitted This is weird... Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422095: xserver-xorg-core: fails to start, no devices detected
Zoho Vignochi wrote: > Ok, I umounted /sys and X started up. Here is the log: > > > (II) PCI: 01:00:0: chip 11ab,6460 card , rev 03 class 06,00,00 > hdr 00 > (II) PCI: 01:08:0: chip 1002,5960 card 148c,2094 rev 01 class 03,00,00 > hdr 80 > (II) PCI: 01:08:1: chip 1002,5940 card 148c,2095 rev 01 class 03,80,00 > hdr 00 > Great, thanks, the PCI scan is correct now. So this bug is somehow related to #422077 with different symptoms. The sysfs-based PCI code is broken. Umounting /sys tells the server to revert to /proc instead of /sys. I am discussing this problem in other emails and we might apply a fix very soon. In the meantime, if you want to debug this a little bit more, you could rebuild xorg-server 1.3 after applying the following patch. It fixed Jim's problem on Sparc in #422077 and somebody told me that it helps on powerpc too. Obviously, you should NOT umount /sys before testing this patch :) Brice Index: xorg-server-1.3.0.0.dfsg/hw/xfree86/os-support/bus/linuxPci.c === --- xorg-server-1.3.0.0.dfsg.orig/hw/xfree86/os-support/bus/linuxPci.c 2007-05-10 15:21:30.0 +0200 +++ xorg-server-1.3.0.0.dfsg/hw/xfree86/os-support/bus/linuxPci.c 2007-05-10 15:21:37.0 +0200 @@ -148,7 +148,7 @@ int domain, bus, dev, func; char file[64]; struct stat ignored; - static int is26 = -1; + static int is26 = 0; domain = PCI_DOM_FROM_TAG(tag); bus = PCI_BUS_NO_DOMAIN(PCI_BUS_FROM_TAG(tag));
Bug#422095: xserver-xorg-core: fails to start, no devices detected
On Thu, 2007-10-05 at 00:31 +0200, Brice Goglin wrote: > Since your problem is related to PCI and Xserver 1.3 is now known to > have big problems with PCI on non-x86 architectures, here's a wild guess: > umount /sys before starting Xorg. If umount complains that /sys is busy, > try "umount -l /sys". Then start X and send us the log (especially the > PCI scan). It helped understanding some problems on sparc. I could help > for you too... > > You might want to remove the BusID line that I told you to add earlier, > since it did not help. > > > Bric Ok, I umounted /sys and X started up. Here is the log: X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Linux Debian Current Operating System: Linux subotai 2.6.18-4-powerpc #1 Mon Mar 26 09:11:14 CEST 2007 ppc Build Date: 09 May 2007 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 May 10 10:04:48 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Samsung SyncMaster 940B" (**) | |-->Device "Radeon 9200 PRO" (**) |-->Input Device "Generic Keyboard" (**) |-->Input Device "Configured Mouse" (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) RgbPath set to "/etc/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (II) No APM support in BIOS or kernel (II) Loader magic: 0x101ef738 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 11ab,6460 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,3044 card 1106,3044 rev 46 class 0c,00,10 hdr 00 (II) PCI: 00:05:0: chip 1033,0035 card 1033,0035 rev 43 class 0c,03,10 hdr 80 (II) PCI: 00:05:1: chip 1033,0035 card 1033,0035 rev 43 class 0c,03,10 hdr 00 (II) PCI: 00:05:2: chip 1033,00e0 card 9710,1906 rev 04 class 0c,03,20 hdr 00 (II) PCI: 00:06:0: chip 1814,0201 card 1814,2560 rev 01 class 02,80,00 hdr 00 (II) PCI: 00:0c:0: chip 1106,8231 card , rev 10 class 06,01,00 hdr 80 (II) PCI: 00:0c:1: chip 1106,0571 card , rev 06 class 01,01,8f hdr 00 (II) PCI: 00:0c:2: chip 1106,3038 card 0925,1234 rev 1e class 0c,03,00 hdr 00 (II) PCI: 00:0c:3: chip 1106,3038 card 0925,1234 rev 1e class 0c,03,00 hdr 00 (II) PCI: 00:0c:4: chip 1106,8235 card , rev 10 class 06,80,00 hdr 00 (II) PCI: 00:0c:5: chip 1106,3058 card , rev 40 class 04,01,00 hdr 00 (II) PCI: 00:0c:6: chip 1106,3068 card , rev 20 class 07,80,00 hdr 00 (II) PCI: 00:0d:0: chip 1106,3065 card 3065,1106 rev 51 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 11ab,6460 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 01:08:0: chip 1002,5960 card 148c,2094 rev 01 class 03,00,00 hdr 80 (II) PCI: 01:08:1: chip 1002,5940 card 148c,2095 rev 01 class 03,80,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:12:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) Host-to-PCI bridge: (II) Bus 1: bridge is at (1:0:0), (1,1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (--) PCI:*(1:8:0) ATI Technologies Inc RV280 [Radeon 9200 PRO] rev 1, Mem @ 0xc000/27, 0xc800/16, I/O @ 0x1000/8,
Bug#377847: xserver-xorg-video-nv: No way to set 1600x1200 resolution.
Brice Goglin <[EMAIL PROTECTED]> writes: > Hi, > > Several months ago, you reported a bug to the Debian BTS regarding the > nv driver refusing to set 1600x1200 resolution. Did you reproduce this > problem recently? With the latest xserver-xorg-video-nv driver 2.0.2 in > unstable? Sorry, I didn't check 2.0.2 as I'm running "testing" where xserver-xorg-video-nv package is at version 1:1.2.0-3. -- Sergei. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420679: wrong screensize
On Thu, May 10, 2007 at 09:58:19AM +0200, Michel Dänzer wrote: > On Sat, 2007-05-05 at 11:10 +0200, David Weinehall wrote: > > > > When I start X on my x60s from the dock (where I also have an external > > screen connected), both the internal and external display will get the > > resolution from the external display; before it'd use the resolution of > > the internal display. This is highly annoying, since the external > > display has higher resolution than the internal. So when I undock again > > I'm left with a laptop that I cannot use in a sane manner because 25% or > > so of the desktop is outside of the physical screen. > > You can't reduce the virtual resolution with xrandr at that point? Probably; but it's still a nuisance, since there's no way to execute xrandr from gdm (for instance), so until I log in I cannot change the resolution. The only reasonable *default* IMHO is to use the lower resolution for both screens when using mirrored mode, since that's the only option that will made things look mirrored (or possible to use the resolution of the main screen). Having the configurable is fine by me (I guess some people might find it useful), but manually invoking xrandr isn't... Regards: David -- /) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
Bug#179647: SIGALRM spinning still exists
On Thu, 2007-05-10 at 03:20 -0700, Don Armstrong wrote: > On Thu, 10 May 2007, Michel Dänzer wrote: > > On Thu, 2007-05-10 at 02:30 -0700, Don Armstrong wrote: > > > > > > I still am seeing this bug occasionally, although not as recently as > > > previously. [I just ran into it a few minutes ago while using > > > xdosemu.] > > > > Could be https://bugs.freedesktop.org/show_bug.cgi?id=10747 . > > Yeah, most likely. The annoying thing is that it only occurs randomly, > and when it just happened I didn't have enough time to trigger a core > dump and really check it out. Can you try the fix suggested in the upstream report? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#179647: SIGALRM spinning still exists
On Thu, 10 May 2007, Michel Dänzer wrote: > On Thu, 2007-05-10 at 02:30 -0700, Don Armstrong wrote: > > > > I still am seeing this bug occasionally, although not as recently as > > previously. [I just ran into it a few minutes ago while using > > xdosemu.] > > Could be https://bugs.freedesktop.org/show_bug.cgi?id=10747 . Yeah, most likely. The annoying thing is that it only occurs randomly, and when it just happened I didn't have enough time to trigger a core dump and really check it out. [Had to get some "real" work done. ;-)] Don Armstrong -- It has always been Debian's philosophy in the past to stick to what makes sense, regardless of what crack the rest of the universe is smoking. -- Andrew Suffield in [EMAIL PROTECTED] http://www.donarmstrong.com http://rzlab.ucr.edu
Bug#179647: SIGALRM spinning still exists
On Thu, 2007-05-10 at 02:30 -0700, Don Armstrong wrote: > > I still am seeing this bug occasionally, although not as recently as > previously. [I just ran into it a few minutes ago while using > xdosemu.] Could be https://bugs.freedesktop.org/show_bug.cgi?id=10747 . -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#390630: With xserver-xorg-video-savage 1:2.1.2-5 and EXA X.org shows garbled display
Hello! Well, no, KDM doesn't start at all. X is running, but the garbled display actually was tty1. Rebooted now. Anyway, EXA does not seem to be usable. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: SIGALRM spinning still exists
Processing commands for [EMAIL PROTECTED]: > reopen 179647 ! Bug#179647: xserver-xfree86: SIGALRM spinlock freezes X server Bug reopened, originator set to Don Armstrong <[EMAIL PROTECTED]>. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#179647: SIGALRM spinning still exists
reopen 179647 ! thanks I still am seeing this bug occasionally, although not as recently as previously. [I just ran into it a few minutes ago while using xdosemu.] Don Armstrong -- I may not have gone where I intended to go, but I think I have ended up where I needed to be. -- Douglas Adams _The Long Dark Tea-Time of the Soul_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#390630: With xserver-xorg-video-savage 1:2.1.2-5 and EXA X.org shows garbled display
Hello! With the new driver version 1:2.1.2-5 and EXA enabled X.org shows a garbled display when KDM displays its login screen. When EXA is switched off - like before - the driver display KDM login screen and everything else correctly. Well actually I can easily live without EXA, so I do not bother. If you want me to test something or provide a digicam photo of the garbled display tell me. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403556: xserver-xorg-video-mga: VT switch dims 16-bit-color screen 0 when screen 1 is 24-bit
Version: 1:1.4.6.1.dfsg.1-2 Brice Goglin <[EMAIL PROTECTED]> writes: > My "Xorg/Etch" basically meant Xorg 7.1 with Xserver 2:1.1.1-21 and MGA > driver 1:1.4.4.dfsg.1-2. Okay, I built and tested some combinations. xserver-xorg-core 2:1.1.1-11 with xserver-xorg-video-mga 1:1.4.4.dfsg.1-2 has this bug. xserver-xorg-core 2:1.1.1-21 with xserver-xorg-video-mga 1:1.4.4.dfsg.1-2 has this bug. xserver-xorg-core 2:1.3.0.0.dfsg-3 with xserver-xorg-video-mga 1:1.4.4.dfsg.1-2 has this bug. xserver-xorg-core 2:1.3.0.0.dfsg-3 with xserver-xorg-video-mga 1:1.4.6.1.dfsg.1-2 has this bug. pgphRy0nrEIOT.pgp Description: PGP signature
Bug#422095:
On Wed, May 9, 2007 at 13:13:50 -0300, Zoho Vignochi wrote: > This is the /etc/X11/xorg.conf created by dpkg-reconfigure xserver-xorg > > ... > Section "Device" > Identifier "Radeon 9200 PRO" > Driver "ati" > BusID "PCI:1:8:0" > VideoRam128000 > EndSection > Try removing (or commenting out) the BusID directive in this section. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420281: xserver-xorg-video-intel: xv playback crashes X server
Yes, please apply those patches. Ahora también puedes acceder a tu correo Terra desde el móvil. Infórmate pinchando aquí.
Processed: retitle 422077 to xserver-xorg: Fatal server error on sparc: xf86MapPciMem failed
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.2 > retitle 422077 xserver-xorg: Fatal server error on sparc: xf86MapPciMem failed Bug#422077: xserver-xorg: Fatal server error: xf86MapPciMem Changed Bug title to xserver-xorg: Fatal server error on sparc: xf86MapPciMem failed from xserver-xorg: Fatal server error: xf86MapPciMem. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420679: wrong screensize
On Sat, 2007-05-05 at 11:10 +0200, David Weinehall wrote: > > When I start X on my x60s from the dock (where I also have an external > screen connected), both the internal and external display will get the > resolution from the external display; before it'd use the resolution of > the internal display. This is highly annoying, since the external > display has higher resolution than the internal. So when I undock again > I'm left with a laptop that I cannot use in a sane manner because 25% or > so of the desktop is outside of the physical screen. You can't reduce the virtual resolution with xrandr at that point? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#415543: xorg: same for power macintosh 6500
On Wed, 2007-05-09 at 23:25 +0200, rob homsi wrote: > > startx works however after opening an application such as dillo, x crashes. > I have to kill X with ctrl+alt+backspace. If that works, then X didn't crash. What exactly are the symptoms that prompt you to hit that combo? > I've also included my Xorg.log.0 as well as xorg.conf. Is the log file from an X server that exhibited the problem? It doesn't seem to show anything out of the ordinary. Anyway, as Brice pointed out, it looks like your kernel is having issues, it would probably be good to clear those first. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
