Julien Cristau writes:
> Does the package at http://people.debian.org/~jcristau/522747/ work
> better?
>
> Its sha1sum is 95b0beda410bb0508d3079fcb161776f5ca67c0c.
This works.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
I've upraded to Wheezy. The bug is reproducible.
--
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/87sj3quo1e@tochka.ru
I will try to reproduce this issue. I just need to upgrade to Wheezy.
--
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/87boaewd6b@tochka.ru
Cyril Brulebois writes:
> why are you submitting this bug against the s3 driver? You seem to be
> running the radeon driver
Perhaps the original poster meant ACPI S3 mode and decided to put bug
here. Need to reassign either to radeon or to kernel.
--
To UNSUBSCRIBE, email to debian-x-requ...
John Talbut writes:
> Package: xserver-xorg-video-s3
> Version: 1:0.6.0-1
> Severity: important
>
> As soon as X is started the screen switches to power saving mode, the
> same when running gdm or xorg. If I use the vesa driver this does not
> happen (but it is slow).
> This happened after insta
I've written and committed to the upstream the manual page for S3.
Should I rework it for Lenny and prepare patch? Is the man page the
subject for proposed updates? I'm asking because the changes can be
slightly complicated for proposed updates as it's needed to change
configure.ac and /debian fi
Franklin Piat writes:
> The screen looks too wide and corrupted, when ran in 24 bits mode.
I close this bug in upstream. The problem was partially solved in 0.6.1
version (available in Debian) and finally solved in upstream by fixing
interlaced mode which is needed to set up 1024x768 resolution
Shaddy Baddah writes:
> (II) Bus 1: bridge is at (0:1:1), (0,1,1), BCTRL: 0x0023 (VGA_EN is cleared)
> (--) PCI:*(1:2:0) ATI Technologies Inc 3D Rage Pro 215GP rev 92, Mem @
> 0xe100/24, 0xe200/12, BIOS @ 0xe102/0
> (--) PCI: (2:1:0) S3 Inc. 86c764/765 [Trio32/64/64V+] rev 84, Mem @
>
Brice Goglin <[EMAIL PROTECTED]> writes:
> Evgeni, From what I see, you've been involved with upstream s3
> recently. So, does this patch matter for s3 0.6 as well ? do you plan
> to apply it upstream?
This patch is intended only for 0.4.0 version and can not be applied to
0.6.0 as there was some
> I can put the S3 back in and get the lspci output for you, but it will
> be a few days before I can do so. The card itself and the bus it goes
> into is working, as OpenVMS on the same system does correctly
> initialize and use the display with the S3 card in place.
I've searched in Google the
You logs are incomplete. They are broken before the ScreenInit
section. I think that the hanging occurs before that moment. After the
place where your logs are ended up there must be something like this:
(==) s3(0): Write-combining range (0xf400,0x20)
(==) s3(0): Backing store disabled
(
"Evgeny M. Zubok" <[EMAIL PROTECTED]> writes:
> What is your full lspci -v output? If you had got such strange picture
> when X was started then probably S3 displayed some other place in
> memory. Your log shows that framebuffer's start address is 0x0900
> -
What is your full lspci -v output? If you had got such strange picture
when X was started then probably S3 displayed some other place in
memory. Your log shows that framebuffer's start address is 0x0900
- 0x097f. So X server will put the image there.
(II) resource ranges after preInit:
Sorry for my previous dirty hack for Makefile.am. My previous message
should be ignored. Now I present new correct version of patch. It also
possibly closes bug #377386 which was merged with this bug.
Infomation for maintainer. This patch replaces(!!!) my previous patch
01_enable_new_mmio.diff. I
I resolved (i hope) the incosistences with the old S3 chipsets. Thanks to
Eugene Konev for his report. Now s3_accel.c compiled twice: with and without
S3_NEWMMIO and then object files s3_accel_newmmio.o and s3_accel_pio.o
are linked together.
Infomation for maintainer. This patch replaces(!!!) my
Sorry, I see what you are talking about.
When Xorg was moved from imake building system the old building rules was
not incorporated into Xorg 7.0/7.1 source tree. I'll try to change this
issue.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EM
What chip you are talking about? In the s3 driver source code there are
only following supported chips:
Without New MMIO:
PCI_CHIP_964_0
PCI_CHIP_964_1
PCI_CHIP_TRIO
PCI_CHIP_AURORA64VP,
With New MMIO:
PCI_CHIP_968
PCI_CHIP_TRIO64UVP
PCI_CHIP_TRIO64V2_DXGX
As I remember there is always one com
--- orig/configure.ac 2006-02-13 03:48:46.0 +
+++ new/configure.ac2006-10-08 02:31:54.0 +
@@ -62,6 +62,8 @@
# Checks for header files.
AC_HEADER_STDC
+AC_DEFINE(S3_NEWMMIO, 1, [Enable support for the new MMIO])
+
AC_SUBST([XORG_CFLAGS])
AC_SUBST([moduledir])
A
I have the same issue. See #370382
and https://bugs.freedesktop.org/show_bug.cgi?id=7112
I discovered that the problem is in acceleration.
Workaround is to disable acceleration :(
Section "Device"
Identifier "s3_trio64v2"
Driver "s3"
Option "noaccel"
^^ ^^^
Package: xserver-xorg
Version: 1:7.0.22
Severity: normal
First of all I take some configurations and logs
|= X font Server =
/etc/X11/fs/config contains:
[skip]
catalogue = /usr/share/fonts/X11/misc/,
/usr/share/fonts/X11/100dpi/:unscaled,
Package: xserver-xorg-video-all
Version: 1:7.0.20
Severity: important
Subj. I have old S3 Trio64v2 videocard. I placed the same bug into
freedesktop.org bugtracking system with xorg.conf and Xorg.0.log. Here:
https://bugs.freedesktop.org/show_bug.cgi?id=7112
-- System Information:
Debian Relea
21 matches
Mail list logo
