Date: Thu, 26 Jul 2007 21:12:45 -0700 (PDT) From: Doug Ambrisko <ambrisko@ambrisko.com> To: Mike Tancsa <mike@sentex.net> Cc: Takeharu KATO <takeharu1219@ybb.ne.jp>, =?ISO-8859-1?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>, freebsd-current@freebsd.org Subject: Re: ichwd for ICH8 Message-ID: <200707270412.l6R4CjQg049026@ambrisko.com> In-Reply-To: <200707270038.l6R0cLNV068524@lava.sentex.ca>
index | next in thread | previous in thread | raw e-mail
Mike Tancsa writes: | At 08:13 PM 7/26/2007, Dag-Erling Sm??rgrav wrote: | >Mike Tancsa <mike@sentex.net> writes: | > > OK, I tried it on current, but it sees the ichwd as ich5, where as its | > > 7 according to the other version | > | >No, the unpatched driver in -CURRENT has that bug (misidentifies ICH7 as | >ICH5) but the patched driver would identify it correctly and | >additionally print a line about the TCO version. You must have loaded | >the wrong module. | | Sorry, you are right. I can load it now on the | current box I have running, but it doesnt reboot | it, probably because of the BIOS setting. Atleast with older ICH chips the TCO reset can be disabled in hardware with a pull-up or pull-down resistor (I forget which) on one of the PC speaker lines. They did this on a Tyan MB but I was able to remove the resistor. The thing that was strange is they didn't know why they put the resistor on the board to disable it. Doug A.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707270412.l6R4CjQg049026>
