From: "Simon Garner" <sgarner@expio.co.nz>
To: <linux-kernel@vger.kernel.org>
Subject: Asus CUR-DLS SMP motherboard
Date: Tue, 10 Apr 2001 15:17:19 +1200 [thread overview]
Message-ID: <01af01c0c16c$ce0bc340$1400a8c0@expio.net.nz> (raw)
Hello,
I'm wondering if anyone has used this motherboard and can confirm if it
works under 2.4.3 or not. Having been burned by the Via-based CUV4X-D not
working under Linux, I'm keen to find out if this ServerWorks-based board
works or not, before throwing away my money.
Asus CUR-DLS, ATX, ServerWorks ServerSet III LE, FC-PGA,LAN/SCSI/VGA
Specifications:
CPU: FCPGA PIII 500-866+MHz/SMP (Symmetical Multi-Processor) dual
processors, Socket 370, Chipset: ServerWorks (RCC) ServerSet III LE, Slots:
2 x PCI-64bit/66MHz, 5 x PCI-32bit/33MHz , 1 x ASMS socket (reserved for
IPMI/EMP), 4x DIMM. Formfactor: ATX, 66/100/133MHz FSB, DMA-33, PC133 memory
support (supports Registered DIMM only, ECC based 64MB to 1GB memory
capacity). Built in Intel 82559 LAN, LSI dual channel Ultra160 SCSI
controller, ATI Rage-XL graphics with 4MB PC100 SDRAM
Any anecdotes?
Alternatively, is anyone working on a patch for the Via 694XDP problems?
Thanks in advance,
Simon Garner
reply other threads:[~2001-04-10 3:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='01af01c0c16c$ce0bc340$1400a8c0@expio.net.nz' \
--to=sgarner@expio.co.nz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox