Bug#670867: Still testing stuff for this bug
Hi! I did some more tests, today with current xserver and video drivers from testing and kernel 3.4 from experimental, still same old results, so I thought I'd give a try to the new xserver-xorg-video-intel 2:2.19.0-2 from unstable and the new aceleration, ... well, I didn't had the chance, as it segfaults when trying to start with the new unstable driver, maybe I should upgrade something else to unstable other than the intel driver, but dependencies should take care of that and didn't complain about it. Anyway, just in case it helps... find the log of xserver attached. Regards... -- Manty/BestiaTester -> http://manty.net [35.742] X.Org X Server 1.12.1.902 (1.12.2 RC 2) Release Date: 2012-05-19 [35.744] X Protocol Version 11, Revision 0 [35.744] Build Operating System: Linux 2.6.32-5-686-bigmem i686 Debian [35.745] Current Operating System: Linux ace 3.4-trunk-686-pae #1 SMP Wed Jun 6 15:11:31 UTC 2012 i686 [35.745] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.4-trunk-686-pae root=UUID=0de509ff-27a7-4ab9-bb3e-0c89402c2c44 ro quiet [35.746] Build Date: 20 May 2012 10:23:38AM [35.746] xorg-server 2:1.12.1.902-1 (Cyril Brulebois ) [35.746] Current version of pixman: 0.24.4 [35.747]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [35.747] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [35.750] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jun 14 19:13:45 2012 [35.750] (==) Using config file: "/etc/X11/xorg.conf" [35.750] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [35.751] (==) ServerLayout "Default Layout" [35.751] (**) |-->Screen "Default Screen" (0) [35.751] (**) | |-->Monitor "Configured Monitor" [35.752] (==) No device specified for screen "Default Screen". Using the first device section listed. [35.752] (**) | |-->Device "Configured Video Device" [35.753] (**) |-->Input Device "Generic Keyboard" [35.753] (**) |-->Input Device "Configured Mouse" [35.753] (**) |-->Input Device "Synaptics Touchpad" [35.753] (==) Automatically adding devices [35.753] (==) Automatically enabling devices [35.753] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [35.753]Entry deleted from font path. [35.753] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [35.753]Entry deleted from font path. [35.753] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [35.753]Entry deleted from font path. [35.753] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [35.753]Entry deleted from font path. [35.754] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [35.754]Entry deleted from font path. [35.754] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [35.754]Entry deleted from font path. [35.754] (WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not exist. [35.754]Entry deleted from font path. [35.754] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [35.754] (==) ModulePath set to "/usr/lib/xorg/modules" [35.754] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [35.754] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [35.754] (WW) Disabling Generic Keyboard [35.754] (WW) Disabling Configured Mouse [35.755] (II) Loader magic: 0xb77415a0 [35.755] (II) Module ABI versions: [35.755]X.Org ANSI C Emulation: 0.4 [35.755]X.Org Video Driver: 12.0 [35.755]X.Org XInput driver : 16.0 [35.755]X.Org Server Extension : 6.0 [35.757] (--) PCI:*(0:0:2:0) 8086:3577:1025:1024 rev 4, Mem @ 0x9800/134217728, 0x9010/524288 [35.757] (--) PCI: (0:0:2:1) 8086:3577:1025:1024 rev 0, Mem @ 0x8800/134217728, 0x8010/524288 [35.758] (II) Open ACPI successful (/var/run/acpid.socket) [35.758] (II) LoadModule: "extmod" [35.759] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [35.761] (II) Module extmod: vendor="X.Org Foundation" [35.761]compiled for 1.12.1.902, module version = 1.0.0 [35.761]Module class: X.Org Server Extension [35.761]ABI class: X.Org Server Extension, version 6.0 [35.761] (II) Loading extension SELinux [35.761] (II) Loading extension MIT-SCREEN-SAVER [35.761] (II) Loading extension XFree86-VidModeExtension [35.761] (II) Loading extension XFree86-DGA [35.761] (II) Loading extension DPMS [35.761] (II) Loading extension XVideo [35.761] (II) Loading extension XVideo-Motion
Bug#670867: More tests
I thought I could test with lower bpp depths so that less memory was needed (I seem to recall that at lower depth I could run without needing to specify the memory parameter on previous versions of xorg) but the results were exactly the same. I even tested 800x600 @ 16 bpp with same blue video output and same hangs :-( Is there any other tests I can run or any other info I could provide? Regards... -- Manty/BestiaTester -> http://manty.net -- 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/20120508041802.ga5...@www.manty.net
Bug#670867: xv video rendering doesn't work on i830M
> Did > > > [ 199.905] (EE) intel(0): Detected a hung GPU, disabling acceleration. > > [ 199.905] (EE) intel(0): When reporting this, please include > > i915_error_state from debugfs and the full dmesg. > > and > > > [ 199.864077] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer > > elapsed... GPU hung > > [ 199.864111] [drm] capturing error event; look for more information in > > /debug/dri/0/i915_error_state > > [ 199.878174] [drm:i915_wait_request] *ERROR* i915_wait_request returns > > -11 (awaiting 2086 at 2085, next 2087) > > > happen when playing the video, or before? when playing it, I have just tested and I could start mplayer with a blue screen and then exit it and dmesg for several times, only after letting it play for a while one of the times the mplayer window became unresponsive (pressing q wouldn't quit) and at that time the dmesg on exit showed the messages. Playing with mplayer the next time did output the: X11 error: BadAlloc (insufficient resources for operation) message on mplayer. Regards. -- Manty/BestiaTester -> http://manty.net -- 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/20120430164720.ga26...@www.manty.net
Bug#670867: xv video rendering doesn't work on i830M
Package: xserver-xorg-video-intel Version: 2:2.18.0-2 Severity: normal Playing back video on a i830M card shows a blue video the first time and X11 error: BadAlloc (insufficient resources for operation) the next times you try it. This is when using XV, if you try to render with X11 there is no problem at all. I have tested this on both mplayer and vlc, both behave similar. The computer is a Acer TravelMate 260 which used to work ok on squeeze (at least I seem to recall it was on squeeze). The only weird thing at that time was that I had to specify when using the i810 driver was "VideoRam 16384" which doesn't seem to exist anymore. After trying to play video several times one looses the text cursor, which makes it difficult to write this bugreport, as well as some other text artifacts on xterm :-( Don't know what else to add, if you feel I'm missing any info, just let me know. Regards. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Nov 20 16:36 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2044072 Mar 5 05:21 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 82830M/MG Integrated Graphics Controller [8086:3577] (rev 04) Xorg X server configuration file status: -rw-r--r-- 1 root root 1597 Mar 2 12:17 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "es" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "CorePointer" Option "TapButton1" "1" Option "TapButton2" "2" Option "TapButton3" "3" EndSection Section "Device" Identifier "Configured Video Device" #VideoRam16384 EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Synaptics Touchpad" EndSection /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.3.0-trunk-686-pae (Debian 3.3-1~experimental.1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Thu Mar 22 05:39:32 UTC 2012 Xorg X server log files on system: -- -rw-r--r-- 1 root root 25384 Apr 29 20:23 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [20.365] X.Org X Server 1.11.4 Release Date: 2012-01-27 [20.366] X Protocol Version 11, Revision 0 [20.366] Build Operating System: Linux 2.6.32-5-amd64 i686 Debian [20.366] Current Operating System: Linux ace 3.3.0-trunk-686-pae #1 SMP Thu Mar 22 05:39:32 UTC 2012 i686 [20.366] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.3.0-trunk-686-pae root=UUID=0de509ff-27a7-4ab9-bb3e-0c89402c2c44 ro quiet [20.366] Build Date: 05 March 2012 04:16:09AM [20.366] xorg-server 2:1.11.4-1 (Cyril Brulebois ) [20.366] Current version of pixman: 0.24.4 [20.366]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [20.366] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning,
Bug#477559: Still fails with current Lenny packages
> > I have just updated the machine to current Lenny and it still fails > > in the very same way as it used to. > > is it going any better with squeeze or higher? Nope, it is still failing at squeeze, I'm using the fb driver right now because of this. Do you want me to test upgrading to sid? any specific tests? Regards... -- Manty/BestiaTester -> http://manty.net -- 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/20110302212917.ga5...@vip.manty.net
Bug#571741: Kernel patch fixes this bug.
reassign 571741 linux-source-2.6.32 stop Hi! As far as I can tell it seems that the kernel upstream patch I was reporting about resolves this bug. I have tested the patch on our 2.6.32 for several days without any problem. I'm reasigning the bug to the kernel package as the problem is within the kernel, it is not 2.6.32 specific, as our 2.6.34 also exhibits this problem, don't know when the git patch will be mixed to mainline though, maybe it has been already applied to the 2.6.35 preseries. Only one problem remains here, it seems that at least on my machine kms on intel is incompatible with splashy on boot (you end up with a black screen instead of your X. However having splashy showing the splash on hibernation or restoring seems to work ok, and splashy isn't usefull with our new startup system anyway (no progress bar). If you happen to have any questions just ask them. Regards... -- Manty/BestiaTester -> http://manty.net -- 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/20100707191949.ga2...@vip.manty.net
Bug#571741: Upstream is sugesting a kernel patch to fix this
Hi! Upstream is sugesting that a Linus kernel patch is fixing this, I'm going to try to test this on Debian's 2.6.32 kernel and report back, if anybody else is willing to test, this is the commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=985b823b919273fe1327d56d2196b4f92e5d0fae I'll report in a few days if things go ok or probably sooner if it doesn't fix the problem. Regards... -- Manty/BestiaTester -> http://manty.net -- 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/20100704214513.ga10...@vip.manty.net
Bug#571741: Submitted upstream
Hi! I have just submitted it upstream, you can follow it here: http://bugs.freedesktop.org/show_bug.cgi?id=26825 Regards. -- 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/20100302000104.ga25...@vip.manty.net
Bug#571741: Another one
This time I was testing with 2.6.33 after upgrading libdrm, mesa, ... as Cyril Brulebois suggests on his "Where have you been" post at planet. After first pm-hibernate everything seemed fine, but after the second one I saw this: [ 1083.562662] PM: restore of devices complete after 1476.094 msecs [ 1083.572681] Restarting tasks ... done. [ 1083.596890] PM: Basic memory bitmaps freed [ 1083.654558] pm-hibernate[20033]: segfault at 7f2ca9f93500 ip 7f2ca9cb3800 sp 7fff48a1aa48 error 7 in libc-2.10.2.so[7f2ca9c46000+14a000] [ 1083.662057] anacron[20036]: segfault at 7f3b9a0cb500 ip 7f3b99deb800 sp 7fff1d3b32b8 error 7 in libc-2.10.2.so[7f3b99d7e000+14a000] [ 1083.768916] X[20037]: segfault at 7fe598944500 ip 7fe598664800 sp 7fff792dc648 error 7 in libc-2.10.2.so[7fe5985f7000+14a000] [ 1083.770968] 99video[20038]: segfault at 7fa97eb60500 ip 7fa97e880800 sp 7fffae18d6a8 error 7 in libc-2.10.2.so[7fa97e813000+14a000] [ 1083.775078] 98-video-quirk-[20039]: segfault at 7ff8d2f9f500 ip 7ff8d2cbf800 sp 7fffcdac0f48 error 7 in libc-2.10.2.so[7ff8d2c52000+14a000] [ 1083.777295] 95led[20040]: segfault at 7fa851bde500 ip 7fa8518fe800 sp 7fff6f4d3788 error 7 in libc-2.10.2.so[7fa851891000+14a000] [ 1083.783087] 95anacron[20041]: segfault at 7f0b8ab41500 ip 7f0b8a861800 sp 7fff02e0ebf8 error 7 in libc-2.10.2.so[7f0b8a7f4000+14a000] [ 1083.785305] 94cpufreq[20042]: segfault at 7f2f4af00500 ip 7f2f4ac20800 sp 7fff184c5e08 error 7 in libc-2.10.2.so[7f2f4abb3000+14a000] [ 1083.787303] 90clock[20043]: segfault at 7f998ee5b500 ip 7f998eb7b800 sp 7fff4b7bb408 error 7 in libc-2.10.2.so[7f998eb0e000+14a000] [ 1083.792744] 75modules[20044]: segfault at 7f67dcb3c500 ip 7f67dc85c800 sp 7fffdf946c48 error 7 in libc-2.10.2.so[7f67dc7ef000+14a000] Fallo de segmento So... still nothing not even upgrading the libs or the kernel :-( Regards. -- 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/20100228205629.ga22...@vip.manty.net
Bug#571741: DRI makes no difference
I just tried with the nodri line (checked it and DRI was effectively disabled) using 2.6.33-2 and same weird behaviour happened, at the xscreensaver I wasn't able to authenticate after the pm-hibernate and when I went to a tty it was not able to spawn a login and got some error about an assertion not ok, so I believe that again this points to the memory corruption thing. Again, KMS seems to be the only one to blame here. Regards. -- 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/20100228201321.ga21...@vip.manty.net
Bug#571741: explaining hardware
Like I said on the report the machine was going well on the -1 version of the intel driver, it was only then I upgraded to -2 that it started failing, furthermore, if I disable kms the machine is fine again. Machine is completely stable, there can be no poblem with any hardware, machine is completely ok. I think that the hypothesis of the video screwing the rest of the memory seems a good one. About the two tests you ask me to do... disabling the related .ko in the kernel doesn't make much sense to me, as only disabling the kms (commenting the options i915 modeset=1 line) makes the machine work perfectly, including DRM/DRI without any problem. About the second of the tests... disabling DRI on X... I'm perfectly running X with DRI without any problem if I disable KMS, so I don't think DRI has anything to do with this, but I'll try to test it anyway. BTW: It seems to me that you hadn't understood well that this was only happening when KMS was enabled, is the problem clear or should I explain it again? any particular thing that isn't clear? Regards. -- 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/20100228165142.ga17...@vip.manty.net
Bug#571741: tested with 2.6.32-3
Ok, I have started testing this new 2.6.32 and did a little bit better but I think this was only luck, nothing else. I could log on and saw this on dmesg: [ 396.756554] Restarting tasks ... [ 396.757030] klogd[1194]: segfault at cc9cd400 ip 7fe87ebb3c02 sp 7fffcc9ccf40 error 6 in libc-2.10.2.so[7fe87eb6f000+14a000] [ 396.770142] done. [ 396.786099] PM: Basic memory bitmaps freed [ 397.130452] [drm] TV-14: set mode NTSC 480i 0 [ 397.184644] syslogd[1185]: segfault at 664cb00 ip 7fe0a31bcc02 sp 7fff0664c5d0 error 6 in libc-2.10.2.so[7fe0a3178000+14a000] [ 397.448046] [drm] TV-14: set mode NTSC 480i 0 This kind of corruption tends to happen more likely if I have more ram used, I mean, if I only load my Xwindow environment (icewm and a couple of terms) it doesn't happen or happens only from time to time, but if I load iceweasel and pidgin it starts to happen almost all the time. Just a note so that you see how badly the system is right now... I just did this on a terminal: ma...@bat:~$ ps ax PID TTY STAT TIME COMMAND Signal 11 (SEGV) caught by ps (procps version 3.2.8). Please send bug reports to or Hope that helps. Regards. -- 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/20100228110809.ga11...@vip.manty.net
Bug#571741: same happens on linux-image-2.6.33-2-amd64 2.6.33-1~experimental.1
I have just tried that new kernel and the behaviour was the same. I could not log into the machine, not on ssh or the console. Let me explain what I was seing... the screen was locked with xscreensaver and it didn't recognice my password, so I switched to a VT and tried to log on there, but the getty could not launch the login, so as soon as I tried to enter my username I got to the username prompt again and after a couple of times I get a "respawning too fast" message and I cannot do anything, pressing the power button wich should halt the machine also doesn't seem to work. This is one of the typical scenarios I found, with 2.6.32 others I had found with 32 were even worst and computer was even less responsive, but on any of them I cannot log in or do a dmesg or similar. I'll also try to test the 2.6.32 recommended version and post the results around. Regards. -- 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/20100228002013.ga31...@vip.manty.net
Bug#559233: More doc
I see there are a lot of solutions for this, I'd like to explain how I did it and sugest that some comments of the ways to fix this and examples are added in a README.Debian or examples dir or similar. All I did was add this two sections to my xorg.conf: Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "CorePointer" Option "TapButton1" "1" Option "TapButton2" "2" Option "TapButton3" "3" EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Synaptics Touchpad" EndSection Hope this helps people out there. Regards. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#477559: Still fails with current Lenny packages
I have just updated the machine to current Lenny and it still fails in the very same way as it used to. I think I didn't mention that a normal kill doesn't kill the server and you need a kill -9 to kill it and it doesn't restore the text mode after that, the same totted X screen remains and keyboard doesn't seem to be working at that time. I can then start another X server (remotely as local keyboard and screen was broken) and same thing will happen again. Hope this helps. Regards... -- Manty/BestiaTester -> http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#481050: After coming from DPMS I get a black screen with working mouse pointer
Package: xserver-xorg-video-intel Version: 2:2.3.1-1 Severity: important I sent this bug already for version 2:2.2.0-1 but we had it closed as it seemed that the bug was gone, maybe some of the cases on which it was happening are now fixed, but it still happens on current versions of the driver. What comes now is a rewording of what I reported on the other bug (463633), however the configuration, logs and everything added by reportbug are new as I have started the xorg.conf from scratch to simplify it and the server is the new one on sid. The server works ok, but if I let it go into DPMS mode, when coming back I get a black screen, only the mouse pointer is shown then, I can move it and it is perfectly drawn, but the whole screen remains black. I can get the screen back to normal by going to a text VT and coming back to the X VT. The machine used to need Option "VBERestore" "true" on the old 810 driver to get the screen restored after getting back from a text VT, this has been like that since the XFree 4 era. This was not happening before with the xserver-xorg-video-i810 driver, only happens with the new xserver-xorg-video-intel. The machine is an Acer Travelmate 260 with a i830 chipset with this integrated card: (II) intel(0): Integrated Graphics Chipset: Intel(R) 830M (--) intel(0): Chipset: "i830" This is lspci output: 00:02.0 0300: 8086:3577 (rev 04) (prog-if 00 [VGA controller]) Subsystem: 1025:1024 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at 9800 (32-bit, prefetchable) [size=128M] Memory at 9010 (32-bit, non-prefetchable) [size=512K] Capabilities: I offer myself to do all the needed tests so that this gets fixed for lenny. Regards! -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2007-02-21 00:14 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1674940 2008-04-29 20:37 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82830 CGC [Chipset Graphics Controller] (rev 04) /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 1443 2008-05-08 23:02 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "es" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "CorePointer" EndSection Section "Device" Identifier "Configured Video Device" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Synaptics Touchpad" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 32100 2008-05-13 11:38 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.4.0.90 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080131-4) Current Operating System: Linux ace 2.6.25 #1 Mon Apr 21 14:13:48 CEST
Bug#463633: After coming from DPMS I get a black screen with working mouse pointer
> Ping? > > Please try with 2:2.2.0.90-2 which has been uploaded today. Sorry, I could not reply before, this seems to fix the problem at least for my system. The only weird thing I saw was that the server is coming up with a resolution bigger than the one on the laptop's screen, I solved this by setting a virtual resolution that limits the resolution to that of the screen. I suppose we can close this bug unless somebody else is still experiencing it. Should I post a new bug because of the resolution thing? Regards... -- Manty/BestiaTester -> http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#463633: After coming from DPMS I get a black screen with working mouse pointer
Package: xserver-xorg-video-intel Version: 2:2.2.0-1 Severity: important The server works ok, but if I let it go into DPMS mode, when coming back I get a black screen, only the mouse pointer is shown then, I can move it and it is perfectly drawn, but the whole screen remains black. I can get the screen back to normal by going to a text VT and coming back to the X VT. The machine needs Option "VBERestore" "true" to get the screen restored after getting back from a text VT, this has been like that since the XFree 4 era and I believe that this option is the one that is allowing me to restore the screen when it becomes black. This was not happening before with the xserver-xorg-video-i810 driver, only happens with the new xserver-xorg-video-intel. The machine is an Acer Travelmate 260 with a i830 chipset with this integrated card: (II) intel(0): Integrated Graphics Chipset: Intel(R) 830M (--) intel(0): Chipset: "i830" This is lspci output: 00:02.0 0300: 8086:3577 (rev 04) (prog-if 00 [VGA controller]) Subsystem: 1025:1024 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at 9800 (32-bit, prefetchable) [size=128M] Memory at 9010 (32-bit, non-prefetchable) [size=512K] Capabilities: I offer myself to do all the needed tests so that this gets fixed for lenny. Regards! -- 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 2007-02-21 00:14 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1673980 2008-02-01 05:06 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82830 CGC [Chipset Graphics Controller] (rev 04) /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 3670 2007-11-03 18:29 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type "man /etc/X11/xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/X11R6/lib/X11/fonts/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/X11R6/lib/X11/fonts/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/X11R6/lib/X11/fonts/Type1" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/X11R6/lib/X11/fonts/100dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/X11R6/lib/X11/fonts/75dpi" # path to defoma fonts FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "es" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "CorePointer" Option "Device""/dev/psaux" Option "Protocol" "auto-dev" Option "HorizScrollDelta" "0" EndSection Section "Device" Identifier "Intel Corporation 82830 CGC [Chipset Graphics Controller]" Driver "i810" BusID "PCI:0:2:0" VideoRam
Bug#455786: can't see video with swfdec on xserver-xorg but works on Xephyr
> It seems to work for me using the latest intel driver (thus using EXA). > Andreas Henriksson said he could reproduce this when using XAA, but not > using EXA (with the radeon driver), so I'm retitling it accordingly (and > tagging wontfix, because nobody seems interested in fixing XAA these > days). That's ok with me, I have tested this and EXA seems to work ok, so no problem with that, I'd like however to sugest that if XAA seems broken for current X, maybe EXA should be enabled by default whenever possible. Just for other people having this very same problem... to activate EXA you need to add Option "AccelMethod" "EXA" to the section on which you descrive your graphic card. Thanks for your help. Regards... -- Manty/BestiaTester -> http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455786: can't see video with swfdec on xserver-xorg but works on Xephyr
> Can you try xserver-xorg-video-ati 6.7.196-2 currently in experimental? I have tried it without any improvement, still no video if we use XAA. Regards... -- Manty/BestiaTester -> http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455786: can't see video with swfdec on xserver-xorg but works on Xephyr
> What did you upgrade when the breakage appeared? the whole Xorg from > testing to unstable? or did you just update your unstable? I hadn't realised of the problem as my amd64 was having it all the time as it is my develpment machine and runs unstable since I installed it not too long ago. What I did after testing the soft on a machine running testing was to downgrade all xserver-xorg* packages to testing and then swfdec worked ok. Upgrading them again showed the problem as expected. So, the machine runs current unstable and downgrading the packages named xserver-xorg to testing solves the issue (same X config is used on both setups). > Can you try xserver-xorg-video-ati 6.7.196-2 currently in experimental? I can and I'll do, but as I told on the bugreport I have tested with a Nvidia card using the nv driver and the problem was also shown there, so I don't expect this new version of the ati driver to solve anything. I'll report on this test as soon as I can do the upgrade and test it. Regards... -- Manty/BestiaTester -> http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455786: can't see video with swfdec on xserver-xorg but works on Xephyr
Package: xserver-xorg Version: 1:7.3+7 Severity: important The problem seems to be related to painting an image with cairo and maybe scaling. For example, trying to see a youtube video fails, also some swf files on which there is a bitmap mixed with some vector graphics, are seen ok on standard size, but when they are scaled up the bitmap dissapears, then if size is restored the bitmap is shown again. A silly url for you to test besides youtube can be: http://misc.manty.net/brit.html I have tested the same program with Xephyr instead of the xserver-xorg server and it works ok, it also works ok if I downgrade to xserver-xorg on testing. Even though the machine has an Ati card I have xchanged it with a Nvidia and it also behaved exactly the same way. Exporting the window through ssh from the failing machine to a machine running stable or testing let's swfdec work. Playing the files with swfplay (a program made for debugging swfdec) using the -i option which is descrived as: -i, --image use an intermediate image surface for drawing makes it work, but doing it without the -i option fails. I don't know anything about cairo, which is how swfdec communicates with X, talking with upstream on the bug he tried to explain to me the differences between the treatment of vectors and bitmaps, he stated this which didn't tell me anything but may point you on the right direction: [20:24] manty: it uses cairo_set_source(); cairo_append_path(); cairo_fill() in every case [20:25] manty: the problem is a) what is the source (image vs color) , b) what matrix is in use and c) what's the path I don't know what else to say, except that I'm open to test whatever you want to gather the info you may need to close this anoying bug. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2007-11-03 21:42 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1831520 2007-11-20 04:09 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] /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 1337 2007-12-04 18:01 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the manual page. # (Type "man " at the shell prompt.) # # This file is automatically updated on package upgrades *only* # if it has not been modified since the last upgrade of the # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc102" Option "XkbLayout" "es" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]" Driver "ati" EndSection Section "Monitor" Identifier "Configured Monitor" Option "DPMS" HorizSync 30-71 VertRefresh 56-75 EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]" DefaultDepth24 SubSection "Display" Modes "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 2638 2007-11-28 19:30 /var/log/Xorg.1.log -rw-r--r-- 1 root root 40013 2007-11-28 19:32 /var/log/Xorg.2.log -rw-r--r-- 1 root root 41757 2007-12-11 08:33 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20071119-1) Current Operating System: Linux dis 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64 Build Date: 20 November 2007 02:55:16AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemente
Bug#240581: Did you forget about this patch?
Hi!
I thought this patch would be applied on the new upload, but it seems it
wasn't, I have reworked it again so that it applies well against the new
packages and I'm sending it again to see if we have better luck next time
;-)
Regards...
--
Manty/BestiaTester -> http://manty.net
diff -r -u xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c
xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c
--- xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c
2004-04-30 14:04:58.0 +0200
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 2004-04-30
13:59:44.0 +0200
@@ -149,7 +149,8 @@
OPTION_CLONE_HSYNC,
OPTION_CLONE_VREFRESH,
OPTION_FBDEV,
-OPTION_VIDEO_KEY
+OPTION_VIDEO_KEY,
+OPTION_MIN_DOTCLOCK
} RADEONOpts;
const OptionInfoRec RADEONOptions[] = {
@@ -180,6 +181,7 @@
{ OPTION_CLONE_VREFRESH, "CloneVRefresh",OPTV_ANYSTR, {0}, FALSE },
{ OPTION_FBDEV, "UseFBDev", OPTV_BOOLEAN, {0}, FALSE },
{ OPTION_VIDEO_KEY, "VideoKey", OPTV_INTEGER, {0}, FALSE },
+{ OPTION_MIN_DOTCLOCK, "ForceMinDotClock", OPTV_FREQ,{0}, FALSE },
{ -1,NULL, OPTV_NONE,{0}, FALSE }
};
@@ -1728,6 +1730,7 @@
RADEONPLLPtr pll = &info->pll;
CARD16 bios_header;
CARD16 pll_info_block;
+double min_dotclock;
if (!info->VBIOS) {
@@ -1782,6 +1785,26 @@
pll->xclk = RADEON_BIOS16(pll_info_block + 0x08);
}
+/* (Some?) Radeon BIOSes seem too lie about their minimum dot
+ * clocks. Allow users to override the detected minimum dot clock
+ * value (e.g., and allow it to be suitable for TV sets).
+ */
+if (xf86GetOptValFreq(info->Options, OPTION_MIN_DOTCLOCK,
+ OPTUNITS_MHZ, &min_dotclock)) {
+ if (min_dotclock < 12 || min_dotclock*100 >= pll->max_pll_freq) {
+ xf86DrvMsg(pScrn->scrnIndex, X_INFO,
+ "Illegal minimum dotclock specified %.2f MHz "
+ "(option ignored)\n",
+ min_dotclock);
+ } else {
+ xf86DrvMsg(pScrn->scrnIndex, X_INFO,
+ "Forced minimum dotclock to %.2f MHz "
+ "(instead of detected %.2f MHz)\n",
+ min_dotclock, ((double)pll->min_pll_freq/1000));
+ pll->min_pll_freq = min_dotclock * 1000;
+ }
+}
+
xf86DrvMsg(pScrn->scrnIndex, X_INFO,
"PLL parameters: rf=%d rd=%d min=%d max=%d; xclk=%d\n",
pll->reference_freq,
diff -r -u xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon.man
xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.man
--- xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon.man 2004-04-30
14:04:58.0 +0200
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.man 2004-04-30
13:59:44.0 +0200
@@ -235,6 +235,17 @@
but not work correctly in some rare cases, hence the default is
.B off.
+.TP
+.BI "Option \*qForceMinDotClock\*q \*q" frequency \*q
+Override minimum dot clock. Some Radeon BIOSes report a minimum dot
+clock unsuitable (too high) for use with television sets even when they
+actually can produce lower dot clocks. If this is the case you can
+override the value here.
+.B Note that using this option may damage your hardware.
+You have been warned. The
+.B frequency
+parameter may be specified as a float value with standard suffixes like
+"k", "kHz", "M", "MHz".
.SH SEE ALSO
XFree86(1), XF86Config(__filemansuffix__), xf86config(1), Xserver(1),
X(__miscmansuffix__)
Bug#240581: Patch to add option for ATI Radeon to force the use of lower dotclocks
Package: xfree86
Severity: wishlist
Tags: patch
Hi!
I have found that my Radeon card as well as many others, says that it can
work from 20Mhz to 400Mhz, this would mean that it is not capable of
producing TV frequencies, which it is, I have found that this problem had
been reported on xfree86 bugtracking system as bug #831 and then added to
their cvs with some changes.
I have made the apropiate changes to the patch so that it could be applied
to our sources and have tested it, it works perfectly and is a clean patch,
I think that it would be good if you could apply it in a future version of
the packages.
Maybe it would also be good to upgrade Radeon's driver a little bit,
following the logs on the cvs there have been many enhancements as well as
bugfixes, new options, ...
Anyway, here are the patches, first the ones I got from the xfree86 cvs:
===
RCS file:
/xf86/anoncvs/cvs/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.man,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.man 2003/10/07
22:47:12 1.4
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon.man 2003/10/31
23:03:17 1.5
@@ -298,6 +298,17 @@
but not work correctly in some rare cases, hence the default is
.B off.
+.TP
+.BI "Option \*qForceMinDotClock\*q \*q" frequency \*q
+Override minimum dot clock. Some Radeon BIOSes report a minimum dot
+clock unsuitable (too high) for use with television sets even when they
+actually can produce lower dot clocks. If this is the case you can
+override the value here.
+.B Note that using this option may damage your hardware.
+You have been warned. The
+.B frequency
+parameter may be specified as a float value with standard suffixes like
+"k", "kHz", "M", "MHz".
.SH SEE ALSO
XFree86(1), XF86Config(__filemansuffix__), xf86config(1), Xserver(1),
X(__miscmansuffix__)
===
RCS file:
/xf86/anoncvs/cvs/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c,v
retrieving revision 1.110
retrieving revision 1.111
diff -u -r1.110 -r1.111
--- xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 2003/10/30
17:36:58 1.110
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 2003/10/31
23:03:17 1.111
@@ -1,4 +1,4 @@
-/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c,v
1.109 2003/10/11 00:29:57 daenzer Exp $ */
+/* $XFree86: xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c,v
1.110 2003/10/30 17:36:58 tsi Exp $ */
/*
* Copyright 2000 ATI Technologies Inc., Markham, Ontario, and
*VA Linux Systems Inc., Fremont, California.
@@ -138,7 +138,8 @@
OPTION_FBDEV,
OPTION_VIDEO_KEY,
OPTION_DISP_PRIORITY,
-OPTION_PANEL_SIZE
+OPTION_PANEL_SIZE,
+OPTION_MIN_DOTCLOCK
} RADEONOpts;
const OptionInfoRec RADEONOptions[] = {
@@ -173,6 +174,7 @@
{ OPTION_VIDEO_KEY, "VideoKey", OPTV_INTEGER, {0}, FALSE },
{ OPTION_DISP_PRIORITY, "DisplayPriority", OPTV_ANYSTR, {0}, FALSE },
{ OPTION_PANEL_SIZE, "PanelSize",OPTV_ANYSTR, {0}, FALSE },
+{ OPTION_MIN_DOTCLOCK, "ForceMinDotClock", OPTV_FREQ,{0}, FALSE },
{ -1,NULL, OPTV_NONE,{0}, FALSE }
};
@@ -1774,6 +1776,7 @@
RADEONPLLPtr pll = &info->pll;
CARD16 bios_header;
CARD16 pll_info_block;
+double min_dotclock;
if (!info->VBIOS) {
@@ -1825,6 +1828,26 @@
pll->min_pll_freq = RADEON_BIOS32(pll_info_block + 0x12);
pll->max_pll_freq = RADEON_BIOS32(pll_info_block + 0x16);
pll->xclk = RADEON_BIOS16(pll_info_block + 0x08);
+}
+
+/* (Some?) Radeon BIOSes seem too lie about their minimum dot
+ * clocks. Allow users to override the detected minimum dot clock
+ * value (e.g., and allow it to be suitable for TV sets).
+ */
+if (xf86GetOptValFreq(info->Options, OPTION_MIN_DOTCLOCK,
+ OPTUNITS_MHZ, &min_dotclock)) {
+ if (min_dotclock < 12 || min_dotclock*100 >= pll->max_pll_freq) {
+ xf86DrvMsg(pScrn->scrnIndex, X_INFO,
+ "Illegal minimum dotclock specified %.2f MHz "
+ "(option ignored)\n",
+ min_dotclock);
+ } else {
+ xf86DrvMsg(pScrn->scrnIndex, X_INFO,
+ "Forced minimum dotclock to %.2f MHz "
+ "(instead of detected %.2f MHz)\n",
+ min_dotclock, ((double)pll->min_pll_freq/1000));
+ pll->min_pll_freq = min_dotclock * 1000;
+ }
}
return TRUE;
And now the patch I made from those, changing them so that they could apply
cleanly to our sources:
--- xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon.man 2004-03-27
03:04:50.0 +0100
++
Re: i830 VT switch broken in 4.3.0-0pre1v5
> > If so I think I should probably build and test 4.3.0-0pre1v5 with > > 056_i810_make_i830_usable.diff instead of > > 000_stolen_from_HEAD_i830_driver.diff, what do you think? > > Sounds like a good plan. Please let us know how this turns out. Well, sorry for not reporting before, I have had trouble building from sources in my laptop, now I'm building in another machine, I don't know what happens to my laptop when building, it stops with an ld problem. Anyway, I have built it and the build also doesn't work in my laptop :-( I'm going to write to David about this, but I'd like to know what changes had been made to 000_post430.diff from one version to the other, for example, if this is a checkout of the xfree86 cvs, what dates, branches, ... are the patches for v4 and v5 based on :-? Regards... -- Manty/BestiaTester -> http://manty.net
Re: i830 VT switch broken in 4.3.0-0pre1v5
> You should probably let David Dawes know that the fixes that were > committed to xf-4_3-branch made things worse, not better. I was going to ask him about that, but I realised that asside the changes in the 000_post430.diff patch, which I suppose are the changes on the 4.3 branch, there is also 000_stolen_from_HEAD_i830_driver.diff, which incorporates the patch we had in v4's 056_i810_make_i830_usable.diff but adds some things which sound to me as important, could this be the cause and not the changes in the 000_post430.diff patch? If so I think I should probably build and test 4.3.0-0pre1v5 with 056_i810_make_i830_usable.diff instead of 000_stolen_from_HEAD_i830_driver.diff, what do you think? Regards... -- Manty/BestiaTester -> http://manty.net
i830 VT switch broken in 4.3.0-0pre1v5
Hi! I was happily using 4.3.0-0pre1v4 on my i830 based laptop and when I upgraded to 4.3.0-0pre1v5 VT switching broke. It is the typical effect descrived by David Dawes in his pages, this is: going from X to the text mode vts will make me loose the screen, which then, when going back to X will get recovered. I don't have any way to see the text console with 4.3.0-0pre1v5, only if I go back to 4.3.0-0pre1v4 and reboot I can make it work again. This means that changing to 4.3.0-0pre1v4 and restarting the server won't fix the text mode screen, 4.3.0-0pre1v5 messes up the screen and 4.3.0-0pre1v4 cannot undo that, only changing back to 4.3.0-0pre1v4 and rebooting can. I'm not subscrived to the list, so please Cc me on replies. Regards... -- Manty/BestiaTester -> http://manty.net
Bug#178600: xfree86: Support for the S3Trio64V2
> Why do you call it a "dummy" patch? It looks to me like it actually > does something. Yes, well the thing is that the patch is only a couple of defines and an if sentence. It works by allowing the 64V2 work like the other trios and setting the maximun clocks allowed (set using the values we've seen on X 3.3.6, we don't have data for this), we have not written any special code for the card as we don't have the specs, that is why I call it dummy ;-) > It applies cleanly to XFree86 4.2.1-5, so I am including it in the next Yep, I'm running 4.2.1-5 patched with this on one of our servers, it seems to work quite well. > release. I don't have any S3 cards, so I will have to rely on the user > community to let me know if this patch works for them, and that it > doesn't break anything. I don't think it will break anything, but I don't know the Xfree internals, we just put in the necesary stuff for it to work on this cards. And yes, I suppose you are gonna have to rely on the community for the testing. Regards... -- Manty/BestiaTester -> http://manty.net
Bug#178600: xfree86: Support for the S3Trio64V2
> Why do you call it a "dummy" patch? It looks to me like it actually > does something. Yes, well the thing is that the patch is only a couple of defines and an if sentence. It works by allowing the 64V2 work like the other trios and setting the maximun clocks allowed (set using the values we've seen on X 3.3.6, we don't have data for this), we have not written any special code for the card as we don't have the specs, that is why I call it dummy ;-) > It applies cleanly to XFree86 4.2.1-5, so I am including it in the next Yep, I'm running 4.2.1-5 patched with this on one of our servers, it seems to work quite well. > release. I don't have any S3 cards, so I will have to rely on the user > community to let me know if this patch works for them, and that it > doesn't break anything. I don't think it will break anything, but I don't know the Xfree internals, we just put in the necesary stuff for it to work on this cards. And yes, I suppose you are gonna have to rely on the community for the testing. Regards... -- Manty/BestiaTester -> http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#178600: xfree86: Support for the S3Trio64V2
Package: xfree86
Version: unavailable; reported 2003-01-27
Severity: wishlist
Tags: patch
Hi!
We have made this dummy patch so that the S3 Trio64V2 is recogniced by XFree
4.2.1 we have tested it a bit on our machine, the card seems to work ok and
we don't think it wil break anything as the code changes are really small.
I think it would be good if you if you could forward this upstream if you
feel like the patch is ok, if so tell me. I suppose that to get full support
of this card (we don't have any specs or anything) more specific code should
be written, but this allows X 4.2.1 to run on this card, which couldn't be
done before.
Well, hope this helps people with this cards.
Regards!
-- System Information:
Debian Release: 3.0
Architecture: i386
Kernel: Linux clandestino 2.4.20 #1 Mon Dec 2 09:30:53 CET 2002 i686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
--- s3trio64v2.diff
Patch to add dummy support for the S3 Trio64V2 DX or GX
By Santiago Garcia Mantinan and Javier Moran Rua
--- xc/programs/Xserver/hw/xfree86/drivers/s3/s3_driver.c.orig Fri Jan 24
14:40:44 2003
+++ xc/programs/Xserver/hw/xfree86/drivers/s3/s3_driver.c Fri Jan 24
14:48:06 2003
@@ -131,6 +131,7 @@
{ PCI_CHIP_968, "968" },
{ PCI_CHIP_TRIO,"Trio32/64" },
{ PCI_CHIP_AURORA64VP, "Aurora64V+" },
+ { PCI_CHIP_TRIO64V2_DXGX, "Trio64V2/DX or /GX" },
{ -1, NULL }
};
@@ -141,6 +142,7 @@
{ PCI_CHIP_968, PCI_CHIP_968, RES_SHARED_VGA },
{ PCI_CHIP_TRIO,PCI_CHIP_TRIO, RES_SHARED_VGA },
{ PCI_CHIP_AURORA64VP, PCI_CHIP_AURORA64VP,RES_SHARED_VGA },
+ { PCI_CHIP_TRIO64V2_DXGX,PCI_CHIP_TRIO64V2_DXGX,RES_SHARED_VGA },
{ -1, -1, RES_UNDEFINED }
};
@@ -526,6 +528,7 @@
case PCI_CHIP_964_0:
case PCI_CHIP_964_1:
case PCI_CHIP_TRIO:
+ case PCI_CHIP_TRIO64V2_DXGX:
case PCI_CHIP_AURORA64VP: /* ??? */
pS3->S3NewMMIO = FALSE;
break;
@@ -652,6 +655,18 @@
#if 0
pS3->CursorInit = S3_CursorInit;/* FIXME broken */
#endif
+ if (pS3->Chipset == PCI_CHIP_TRIO64V2_DXGX)
+ switch(pScrn->bitsPerPixel) {
+ case 8:
+ case 16:
+ pS3->MaxClock = 17;
+ break;
+ case 24:
+ case 32:
+ pS3->MaxClock = 135000;
+ break;
+ }
+ else
switch(pScrn->bitsPerPixel) {
case 8:
pS3->MaxClock = 135000;
@@ -1106,7 +1121,7 @@
if (pS3->Chipset == PCI_CHIP_968)
shift = 1; /* XXX IBMRGB */
- else if (pS3->Chipset == PCI_CHIP_TRIO)
+ else if ((pS3->Chipset == PCI_CHIP_TRIO) || (pS3->Chipset ==
PCI_CHIP_TRIO64V2_DXGX ))
shift = -(pS3->s3Bpp >> 1);
return shift;
--- xc/programs/Xserver/hw/xfree86/drivers/s3/s3.h.orig Fri Jan 24 14:40:23 2003
+++ xc/programs/Xserver/hw/xfree86/drivers/s3/s3.h Fri Jan 24 14:18:45 2003
@@ -240,6 +240,7 @@
#define S3_964_SERIES()((pS3->Chipset == PCI_CHIP_964_0) ||
\
(pS3->Chipset == PCI_CHIP_964_1))
#defineS3_TRIO_SERIES()((pS3->Chipset == PCI_CHIP_TRIO) ||
\
-(pS3->Chipset == PCI_CHIP_AURORA64VP))
+(pS3->Chipset == PCI_CHIP_AURORA64VP) || \
+(pS3->Chipset == PCI_CHIP_TRIO64V2_DXGX))
#endif /* _S3_H */
Bug#178600: xfree86: Support for the S3Trio64V2
Package: xfree86
Version: unavailable; reported 2003-01-27
Severity: wishlist
Tags: patch
Hi!
We have made this dummy patch so that the S3 Trio64V2 is recogniced by XFree
4.2.1 we have tested it a bit on our machine, the card seems to work ok and
we don't think it wil break anything as the code changes are really small.
I think it would be good if you if you could forward this upstream if you
feel like the patch is ok, if so tell me. I suppose that to get full support
of this card (we don't have any specs or anything) more specific code should
be written, but this allows X 4.2.1 to run on this card, which couldn't be
done before.
Well, hope this helps people with this cards.
Regards!
-- System Information:
Debian Release: 3.0
Architecture: i386
Kernel: Linux clandestino 2.4.20 #1 Mon Dec 2 09:30:53 CET 2002 i686
Locale: LANG=es_ES@euro, LC_CTYPE=es_ES@euro
--- s3trio64v2.diff
Patch to add dummy support for the S3 Trio64V2 DX or GX
By Santiago Garcia Mantinan and Javier Moran Rua
--- xc/programs/Xserver/hw/xfree86/drivers/s3/s3_driver.c.orig Fri Jan 24 14:40:44
2003
+++ xc/programs/Xserver/hw/xfree86/drivers/s3/s3_driver.c Fri Jan 24 14:48:06
+2003
@@ -131,6 +131,7 @@
{ PCI_CHIP_968, "968" },
{ PCI_CHIP_TRIO,"Trio32/64" },
{ PCI_CHIP_AURORA64VP, "Aurora64V+" },
+ { PCI_CHIP_TRIO64V2_DXGX, "Trio64V2/DX or /GX" },
{ -1, NULL }
};
@@ -141,6 +142,7 @@
{ PCI_CHIP_968, PCI_CHIP_968, RES_SHARED_VGA },
{ PCI_CHIP_TRIO,PCI_CHIP_TRIO, RES_SHARED_VGA },
{ PCI_CHIP_AURORA64VP, PCI_CHIP_AURORA64VP,RES_SHARED_VGA },
+ { PCI_CHIP_TRIO64V2_DXGX,PCI_CHIP_TRIO64V2_DXGX,RES_SHARED_VGA },
{ -1, -1, RES_UNDEFINED }
};
@@ -526,6 +528,7 @@
case PCI_CHIP_964_0:
case PCI_CHIP_964_1:
case PCI_CHIP_TRIO:
+ case PCI_CHIP_TRIO64V2_DXGX:
case PCI_CHIP_AURORA64VP: /* ??? */
pS3->S3NewMMIO = FALSE;
break;
@@ -652,6 +655,18 @@
#if 0
pS3->CursorInit = S3_CursorInit;/* FIXME broken */
#endif
+ if (pS3->Chipset == PCI_CHIP_TRIO64V2_DXGX)
+ switch(pScrn->bitsPerPixel) {
+ case 8:
+ case 16:
+ pS3->MaxClock = 17;
+ break;
+ case 24:
+ case 32:
+ pS3->MaxClock = 135000;
+ break;
+ }
+ else
switch(pScrn->bitsPerPixel) {
case 8:
pS3->MaxClock = 135000;
@@ -1106,7 +1121,7 @@
if (pS3->Chipset == PCI_CHIP_968)
shift = 1; /* XXX IBMRGB */
- else if (pS3->Chipset == PCI_CHIP_TRIO)
+ else if ((pS3->Chipset == PCI_CHIP_TRIO) || (pS3->Chipset ==
+PCI_CHIP_TRIO64V2_DXGX ))
shift = -(pS3->s3Bpp >> 1);
return shift;
--- xc/programs/Xserver/hw/xfree86/drivers/s3/s3.h.orig Fri Jan 24 14:40:23 2003
+++ xc/programs/Xserver/hw/xfree86/drivers/s3/s3.h Fri Jan 24 14:18:45 2003
@@ -240,6 +240,7 @@
#define S3_964_SERIES()((pS3->Chipset == PCI_CHIP_964_0) ||\
(pS3->Chipset == PCI_CHIP_964_1))
#defineS3_TRIO_SERIES()((pS3->Chipset == PCI_CHIP_TRIO) || \
-(pS3->Chipset == PCI_CHIP_AURORA64VP))
+(pS3->Chipset == PCI_CHIP_AURORA64VP) || \
+(pS3->Chipset == PCI_CHIP_TRIO64V2_DXGX))
#endif /* _S3_H */
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#137752: dirty patch
Package: xfree86v3 Version: unavailable; reported 2002-11-29 Followup-For: Bug #137752 This is a dirty patch that enables xfree86v3 to build on powerpc, the first part is to correct one of the patches to make it put the configuration for xfree68 on the correct place, this was done on xfree86 but not on 68. The second part is the dirty one and solves in a dirty way the problem that this bug addresses, so it should not be applied like that to the package, but may allow somebody to build it. diff -r -u v3standard/xfree86v3-3.3.6/debian/patches/077_xfree68_common_Imakefile_resync.diff xfree86v3-3.3.6/debian/patches/077_xfree68_common_Imakefile_resync.diff --- v3standard/xfree86v3-3.3.6/debian/patches/077_xfree68_common_Imakefile_resync.diff Wed Nov 27 23:16:20 2002 +++ xfree86v3-3.3.6/debian/patches/077_xfree68_common_Imakefile_resync.diff Thu Nov 28 01:15:19 2002 @@ -153,7 +153,7 @@ # if MicroTouchSupport SpecialObjectRule(xf86MuTouch.o,xf86MuTouch.c,$(SHARED_CFLAGS)) DynamicModuleTarget(xf86MuTouch.so,xf86MuTouch.o) -@@ -287,6 +302,11 @@ +@@ -287,10 +302,15 @@ DynamicModuleTarget(xf86Dial.so,xf86Dial.o) InstallDynamicModule(xf86Dial.so,$(MODULEDIR)) # endif @@ -164,7 +164,13 @@ +# endif # endif #endif - SpecialObjectRule($(XCONFIGSRC).o,$(XCONFIGSRC).c,'-DSERVER_CONFIG_FILE="$(LIBDIR)/$(XCONFIGFILE)"' $(MODULEDEFINES) $(EXT_DEFINES)) +-SpecialObjectRule($(XCONFIGSRC).o,$(XCONFIGSRC).c,'-DSERVER_CONFIG_FILE="$(LIBDIR)/$(XCONFIGFILE)"' $(MODULEDEFINES) $(EXT_DEFINES)) +-SpecialObjectRule(xf86DCConf.o,xf86DCConf.c,'-DSERVER_CONFIG_FILE="$(LIBDIR)/$(XCONFIGFILE)"' $(MODULEDEFINES) $(EXT_DEFINES)) ++SpecialObjectRule($(XCONFIGSRC).o,$(XCONFIGSRC).c,'-DSERVER_CONFIG_FILE="/etc/X11/$(XCONFIGFILE)"' $(MODULEDEFINES) $(EXT_DEFINES)) ++SpecialObjectRule(xf86DCConf.o,xf86DCConf.c,'-DSERVER_CONFIG_FILE="/etc/X11/$(XCONFIGFILE)"' $(MODULEDEFINES) $(EXT_DEFINES)) + SpecialObjectRule(xf86Init.o,xf86Init.c $(ICONFIGFILES),$(OSNAMEDEF) $(EXT_DEFINES) $(BETADEFS)) + SpecialCObjectRule(xf86Events,$(ICONFIGFILES),$(EXT_DEFINES) $(KEYB_DEFINES)) + SpecialCObjectRule($(KBD),$(ICONFIGFILES),$(KEYB_DEFINES)) @@ -323,6 +343,8 @@ LinkSourceFile(xf86Summa.c,$(XF86SRC)/common) LinkSourceFile(xf86AceCad.c,$(XF86SRC)/common) diff -r -u v3standard/xfree86v3-3.3.6/debian/rules xfree86v3-3.3.6/debian/rules --- v3standard/xfree86v3-3.3.6/debian/rules Wed Nov 27 23:16:19 2002 +++ xfree86v3-3.3.6/debian/rulesThu Nov 28 01:15:19 2002 @@ -286,6 +286,9 @@ done dh_installdebconf dh_installdirs + cp build-tree/xc/programs/Xserver/hw/xfree86/doc/* debian/tmp/usr/X11R6/lib/X11/doc/ | true + cp build-tree/xc/programs/Xserver/hw/xfree86/VGADriverDoc/* debian/tmp/usr/X11R6/lib/X11/doc/ | true + cp build-tree/xc/programs/Xserver/hw/xfree86/etc/* debian/tmp/usr/X11R6/lib/X11/etc/ | true dh_installdocs dh_installexamples dh_installmenu Hope this helps a bit. Regards!
Bug#137752: dirty patch
Package: xfree86v3 Version: unavailable; reported 2002-11-29 Followup-For: Bug #137752 This is a dirty patch that enables xfree86v3 to build on powerpc, the first part is to correct one of the patches to make it put the configuration for xfree68 on the correct place, this was done on xfree86 but not on 68. The second part is the dirty one and solves in a dirty way the problem that this bug addresses, so it should not be applied like that to the package, but may allow somebody to build it. diff -r -u v3standard/xfree86v3-3.3.6/debian/patches/077_xfree68_common_Imakefile_resync.diff xfree86v3-3.3.6/debian/patches/077_xfree68_common_Imakefile_resync.diff --- v3standard/xfree86v3-3.3.6/debian/patches/077_xfree68_common_Imakefile_resync.diff Wed Nov 27 23:16:20 2002 +++ xfree86v3-3.3.6/debian/patches/077_xfree68_common_Imakefile_resync.diff Thu +Nov 28 01:15:19 2002 @@ -153,7 +153,7 @@ # if MicroTouchSupport SpecialObjectRule(xf86MuTouch.o,xf86MuTouch.c,$(SHARED_CFLAGS)) DynamicModuleTarget(xf86MuTouch.so,xf86MuTouch.o) -@@ -287,6 +302,11 @@ +@@ -287,10 +302,15 @@ DynamicModuleTarget(xf86Dial.so,xf86Dial.o) InstallDynamicModule(xf86Dial.so,$(MODULEDIR)) # endif @@ -164,7 +164,13 @@ +# endif # endif #endif - SpecialObjectRule($(XCONFIGSRC).o,$(XCONFIGSRC).c,'-DSERVER_CONFIG_FILE="$(LIBDIR)/$(XCONFIGFILE)"' $(MODULEDEFINES) $(EXT_DEFINES)) +-SpecialObjectRule($(XCONFIGSRC).o,$(XCONFIGSRC).c,'-DSERVER_CONFIG_FILE="$(LIBDIR)/$(XCONFIGFILE)"' + $(MODULEDEFINES) $(EXT_DEFINES)) +-SpecialObjectRule(xf86DCConf.o,xf86DCConf.c,'-DSERVER_CONFIG_FILE="$(LIBDIR)/$(XCONFIGFILE)"' + $(MODULEDEFINES) $(EXT_DEFINES)) ++SpecialObjectRule($(XCONFIGSRC).o,$(XCONFIGSRC).c,'-DSERVER_CONFIG_FILE="/etc/X11/$(XCONFIGFILE)"' + $(MODULEDEFINES) $(EXT_DEFINES)) ++SpecialObjectRule(xf86DCConf.o,xf86DCConf.c,'-DSERVER_CONFIG_FILE="/etc/X11/$(XCONFIGFILE)"' + $(MODULEDEFINES) $(EXT_DEFINES)) + SpecialObjectRule(xf86Init.o,xf86Init.c $(ICONFIGFILES),$(OSNAMEDEF) $(EXT_DEFINES) +$(BETADEFS)) + SpecialCObjectRule(xf86Events,$(ICONFIGFILES),$(EXT_DEFINES) $(KEYB_DEFINES)) + SpecialCObjectRule($(KBD),$(ICONFIGFILES),$(KEYB_DEFINES)) @@ -323,6 +343,8 @@ LinkSourceFile(xf86Summa.c,$(XF86SRC)/common) LinkSourceFile(xf86AceCad.c,$(XF86SRC)/common) diff -r -u v3standard/xfree86v3-3.3.6/debian/rules xfree86v3-3.3.6/debian/rules --- v3standard/xfree86v3-3.3.6/debian/rules Wed Nov 27 23:16:19 2002 +++ xfree86v3-3.3.6/debian/rulesThu Nov 28 01:15:19 2002 @@ -286,6 +286,9 @@ done dh_installdebconf dh_installdirs + cp build-tree/xc/programs/Xserver/hw/xfree86/doc/* +debian/tmp/usr/X11R6/lib/X11/doc/ | true + cp build-tree/xc/programs/Xserver/hw/xfree86/VGADriverDoc/* +debian/tmp/usr/X11R6/lib/X11/doc/ | true + cp build-tree/xc/programs/Xserver/hw/xfree86/etc/* +debian/tmp/usr/X11R6/lib/X11/etc/ | true dh_installdocs dh_installexamples dh_installmenu Hope this helps a bit. Regards! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
