![](https://seccdn.libravatar.org/avatar/549da6534616b470e0ed4a137f111a1f.jpg?s=120&d=mm&r=g)
And verily, didst Andrew Halliwell announce to the hordes:
From ah@gnd.com Thu Dec 18 13:19:57 2003 Return-Path:
Received: (from ah@localhost) by gndsys.gnd.domain (8.11.6/8.11.6/SuSE Linux 0.5) id hBIDJuS08433 for ah@gndsys.gnd.domain; Thu, 18 Dec 2003 13:19:56 GMT From: Andrew Halliwell Message-Id: <200312181319.hBIDJuS08433@gndsys.gnd.domain> Subject: Re: [suse-amd64] FYI: Tyan S2885 with more than 4GB: New BIOS To: ah@gndsys.gnd.domain (ah) Date: Thu, 18 Dec 2003 13:19:42 +0000 (GMT) In-Reply-To: from "ah" at Oct 23, 2003 11:49:26 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on gndsys.gnd.domain X-Spam-Status: No, hits=-96.7 required=5.0 tests=MSGID_FROM_MTA_SHORT, USER_IN_WHITELIST autolearn=no version=2.60 X-Spam-Level:
And verily, didst Marcus Barkowsky announce to the hordes:
Hi!
That's a very good bios. I have not discovered any new problems yet.
The graphics system using an NVIDIA 5600 card got a speed-up from 10fps to 50fps (720x576 pixel) when using plain x11 and 20fps to >100fps when using sdl. AGP is now automatically detected and used (NVIDIA_GLX and NVIDIA_kernel). 6GB are detected and used.
(Gah! I'm so used to just hitting reply for a mailing list to reply TO it rather than have to piss around cut/pasting addresses into the To: line, or hitting reply and then realising, and having to forward the mail again to the list... why such a silly setup?) Anyway... Got an S2885 here. With 2 1 gig ECC Reg DIMMs, it's fine. With 4, 6 or 8, BANG, kernel panic (when under heavy load of a kernel loop running with -j30 and copying a 2 gig file repeatedly). We found two of the 8 however were duff, cos they paniced the machine even with 2 in. But now we've just got a fresh batch of RAM, and it's still doing it. Can anyone say if this BIOS would resolve the problem I'm having? (although, it's "more than 2 gig" in my case) Or perhaps would the new 2.6.0 be more forgiving of whatever's causing it? We're VERY wary of trying to flash the bios. We tried it last week with the 1.01 first release BIOS and ended up with a dead motherboard.