Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Jan 2005 09:29:41 -0600
From:      Jonathan Fosburgh <syjef@mdanderson.org>
To:        freebsd-stable@freebsd.org
Subject:   Support for Sis 755 AGP WAS: Fwd: Radeon DRI problems after system upgrade
Message-ID:  <200501110929.46471.syjef@mdanderson.org>

next in thread | raw e-mail | index | archive | help
--nextPart1445383.oKZgXBjeCX
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Below is a message I posted to x11@ regarding an apparent problem I am havi=
ng=20
with a new mobo and getting DRI support.  At the very least, it appears tha=
t=20
my AGP is not being probed correctly, and I hope that is where my DRI probl=
em=20
lies.  The mobo is an ECS 755-A2 (Athlon 64 socket 754, but I am running=20
i386, not amd64, and this is a fairly recent 5.3-STABLE) using the SiS 755=
=20
chipset.  I do not find this listed in src/sys/pci/agp_sis.c  It appears a=
=20
guess is being made that this is a SiS 650 chipset, based on the output fro=
m=20
pciconf -lv: device   =3D 'SiSM650? Host-to-PCI Bridge' .

The device ID for that chipset (taken from agp_sis.c) is 0x06501039, but=20
pciconf shows mine to be 0x07551039.  Presumably I can add another conditio=
n=20
to the case statement the generates that information and it will at least I=
D=20
correctly, but I've never done that and I want to make sure I do it correct=
ly=20
before trying it.  I would think something along the lines of:

case 0x07551039:
                return ("SiS 755 host to AGP bridge");

but is all that going to accomplish is fixing the ID or is there more that=
=20
needs to be done?

=2D---------  Forwarded Message  ----------

Subject: Radeon DRI problems after system upgrade
Date: Monday 10 January 2005 07:45
=46rom: Jonathan Fosburgh <jonathan@fosburgh.org>
To: freebsd-x11@freebsd.org

I recently (this weekend) upgraded my aging P-III system to an AMD Athlon 64
(still running the i386 version of FreeBSD) and DRI has stopped working.  I
am running a recent 5.3-STABLE with Xorg 6.8.1 and the current graphics/dri
from ports.  AGP is compiled into the kernel.  The chipset is SiS 755.  I
receive the following error now when drm0 loads:

Jan  9 04:27:17 gw kernel: agp0: binding memory at bad offset 0
Jan  9 04:27:17 gw kernel: error: [drm:pid688:radeon_cp_init] *ERROR*
radeon_cp_init called without lock held
Jan  9 04:27:17 gw kernel: error: [drm:pid688:radeon_unlock] *ERROR* Process
688 using kernel context 0

=46rom postings to mailing lists, this indicates that AGP is not loaded, bu=
t I
made sure to build it statically into the kernel when I first noticed the
problem.  Here are some particulars:

Jan  9 04:27:17 gw kernel: drm0: <ATI Radeon QY RV100 7000/VE> port
0xd000-0xd0ff mem 0xe8020000-0xe802ffff,0xe0000000-0xe7ffffff irq 16 at
device 0.0 on pci1
Jan  9 04:27:17 gw kernel: info: [drm] AGP at 0xd8000000 128MB
Jan  9 04:27:17 gw kernel: info: [drm] Initialized radeon 1.11.0 20020828 on
minor 0


pciconf -lv reports the following for AGP:

agp0@pci0:0:0:  class=3D0x060000 card=3D0x18911019 chip=3D0x07551039 rev=3D=
0x01
hdr=3D0x00
    vendor   =3D 'Silicon Integrated Systems (SiS)'
    device   =3D 'SiSM650? Host-to-PCI Bridge'
    class    =3D bridge
    subclass =3D HOST-PCI
and for drm0:

drm0@pci1:0:0:  class=3D0x030000 card=3D0x2081148c chip=3D0x51591002 rev=3D=
0x00
hdr=3D0x00
    vendor   =3D 'ATI Technologies Inc.'
    device   =3D 'RV100 Radeon 7000 / Radeon VE'
    class    =3D display
    subclass =3D VGA


DRI used to work with this release of Xorg and the same -STABLE sources.=20
 From old syslogs:

Dec 27 21:09:44 gw kernel: agp0: <VIA 82C691 (Apollo Pro) host to PCI bridg=
e>
mem 0xe4000000-0xe7ffffff at device 0.0 on pci0

Dec 27 21:10:00 gw kernel: drm0: <ATI Radeon QY RV100 7000/VE> port
0xd800-0xd8ff mem 0xd7000000-0xd700ffff,0xd8000000-0xdfffffff irq 11 at
device 0.0 on pci1
Dec 27 21:10:00 gw kernel: info: [drm] AGP at 0xe4000000 64MB
Dec 27 21:10:00 gw kernel: info: [drm] Initialized radeon 1.11.0 20020828 on
minor 0


My only guess is that this has something to do with AGP support for this
chipset.  Does anyone have a suggestion?


=2D-
Jonathan Fosburgh
AIX and Storage Administrator
UT MD Anderson Cancer Center
Houston, TX

=2D------------------------------------------------------

=2D-=20
Jonathan Fosburgh
AIX and Storage Administrator
UT MD Anderson Cancer Center
Houston, TX=20

--nextPart1445383.oKZgXBjeCX
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQBB4/DqqUvQmqp7omYRAmw0AKC57AEVPZaudeZsg8w3vLyH2iJ+3ACbBnKs
JanPNtqtzKYZe8wmMQOeBsM=
=1cFx
-----END PGP SIGNATURE-----

--nextPart1445383.oKZgXBjeCX--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501110929.46471.syjef>