From: "Cédric Rivard" <cedric@rivard.info>
To: Heilmann@cdj.yemanja.net, Oliver <Oliver.Heilmann@drkw.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SIS AGP vs 2.6.6-rc2
Date: Sat, 8 May 2004 01:08:43 +0200 [thread overview]
Message-ID: <200405080108.43694.cedric@rivard.info> (raw)
Heilmann, Oliver wrote:
> Basically, if you have an SiS chipset and your machine freezes when you
> start X, try the -agp_sis_force_delay=1 option. If this fixes your
> problem add your PCI ID to sis_broken_chipsets in sis-agp.c
> Note to 746[FX] people: I'm still not sure what the differences between
> the two 746 versions and the 648 series are. If this patch does not work
> for you try playing with the agp_sis_agp_spec module option. Any
> feedback is greatly appreciated.
Hi Oliver,
SIS 655 does also require the delay workaround not to freeze.
Following, the relevant kernel log of my machine (SIS655TX with Radeon 9200):
cdj:~# dmesg |grep -i agp
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected SiS 655 chipset
agpgart: Maximum main memory to use for agp memory: 941M
agpgart: AGP aperture is 256M @ 0xe0000000
agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
agpgart: SiS delay workaround: giving bridge time to recover.
agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
Cheers,
Cédric Rivard
next reply other threads:[~2004-05-07 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 23:08 Cédric Rivard [this message]
[not found] <20040426082159.90513.qmail@web10102.mail.yahoo.com>
2004-04-26 9:32 ` [PATCH] SIS AGP clean up, blacklist and module options Heilmann, Oliver
2004-04-27 11:04 ` [PATCH] SIS AGP vs 2.6.6-rc2 Heilmann, Oliver
2004-04-27 17:29 ` Hemmann, Volker Armin
2004-04-27 19:00 ` Heilmann, Oliver
2004-04-27 19:40 ` Heilmann, Oliver
2004-04-27 20:22 ` Hemmann, Volker Armin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200405080108.43694.cedric@rivard.info \
--to=cedric@rivard.info \
--cc=Heilmann@cdj.yemanja.net \
--cc=Oliver.Heilmann@drkw.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.