Date: Mon, 23 Feb 2009 11:31:20 -0600 From: Robert Noland <rnoland@FreeBSD.org> To: Alexander Frolkin <avf@eldamar.org.uk> Cc: freebsd-x11@freebsd.org Subject: Re: Problem upgrading from X.org 1.4 to 1.5 Message-ID: <1235410280.1309.62.camel@widget.2hip.net> In-Reply-To: <20090223103605.GD24049@eldamar.org.uk> References: <20090223103605.GD24049@eldamar.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-hBMDXGiygcH9aM+9f8vz Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2009-02-23 at 11:36 +0100, Alexander Frolkin wrote: > Hi, >=20 > I'm not sure this is specific to FreeBSD, but here goes... I upgraded > xorg-server 1.4.2 to 1.5.3 yesterday, and then spent all day trying to > get the new X server to work until finally giving up and downgrading > back to 1.4.2. >=20 > I have a dual head setup --- an AGP Radeon 9200 and a PCI S3 Savage4. > The config which works fine with 1.4 gives either garbled output on the > Savage card or doesn't initialise it at all (depending on the NoInt10 > option). >=20 > What is particularly interesting is the following excerpt from > Xorg.0.log. First, the 1.4 version: >=20 > ----- > (II) SAVAGE(1): VESA BIOS detected > (II) SAVAGE(1): VESA VBE Version 2.0 > (II) SAVAGE(1): VESA VBE Total Mem: 8192 kB > (II) SAVAGE(1): VESA VBE OEM: S3 Incorporated. Savage4 > (II) SAVAGE(1): VESA VBE OEM Software Rev: 1.1 > (II) SAVAGE(1): VESA VBE OEM Vendor: S3 Incorporated. > (II) SAVAGE(1): VESA VBE OEM Product: Savage4 > (II) SAVAGE(1): VESA VBE OEM Product Rev: Rev B > ----- >=20 > And now the 1.5 version: >=20 > ----- > (II) SAVAGE(1): VESA BIOS detected > (II) SAVAGE(1): VESA VBE Version 2.0 > (II) SAVAGE(1): VESA VBE Total Mem: 131072 kB > (II) SAVAGE(1): VESA VBE OEM: ATI RADEON RV280 > (II) SAVAGE(1): VESA VBE OEM Software Rev: 1.0 > (II) SAVAGE(1): VESA VBE OEM Vendor: ATI Technologies Inc. > (II) SAVAGE(1): VESA VBE OEM Product: V280 > (II) SAVAGE(1): VESA VBE OEM Product Rev: 01.00 > ----- >=20 > The 1.4 version is correct, while the 1.5 version shows the info for my > other card! If you ask me, this is completely screwed up. :-) I guess > it also explains why 1.5 doesn't work for me. >=20 > Has anyone else come across this problem? Is this a known bug? Any > suggestions? :-) >=20 > My xorg.conf and the logs from 1.4 and 1.5 are attached. Multicard setups don't work now. In server 1.4, the server managed all the pci resources and handled arbitration between different cards with a big hammer approach. server 1.5 uses libpciaccess to deal with the pci bus. This is also an issue on linux afaik. Something needs to handle arbitration between the cards (libpciaccess isn't the right place). We need to deal with this in the kernel somewhere, but I haven't figured out quite the right place yet. robert. >=20 > Thanks! >=20 >=20 > Alex >=20 >=20 > _______________________________________________ > freebsd-x11@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" --=20 Robert Noland <rnoland@FreeBSD.org> FreeBSD --=-hBMDXGiygcH9aM+9f8vz Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEABECAAYFAkmi3WgACgkQM4TrQ4qfRONDAACeJHWUTd7QCbN/7lVCEEJi+bpd fncAn3x3N1Qy+8nWhS9CnDj+VBP1vZiP =ub03 -----END PGP SIGNATURE----- --=-hBMDXGiygcH9aM+9f8vz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1235410280.1309.62.camel>