From owner-freebsd-hardware  Mon Nov  6  4:12:14 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from lupinella.troll.no (lupinella.troll.no [213.203.59.59])
	by hub.freebsd.org (Postfix) with ESMTP id 2E01337B479
	for <freebsd-hardware@freebsd.org>; Mon,  6 Nov 2000 04:12:12 -0800 (PST)
Received: from breiflabb.troll.no ([213.203.59.91]:53006 "HELO breiflabb"
        ident: "NO-IDENT-SERVICE[2]") by trolltech.com with SMTP
        id <S114583AbQKFMLx>; Mon, 6 Nov 2000 13:11:53 +0100
Message-ID: <034701c047ea$740c33d0$5b3bcbd5@breiflabb>
From: "Erik H. Bakke" <ebakke@trolltech.com>
To: "Ray Qiu" <ray_qiu@yahoo.com>, <freebsd-hardware@freebsd.org>
References: <20001103181825.32921.qmail@web9103.mail.yahoo.com>
Subject: Re: Sound card
Date: Mon, 6 Nov 2000 13:09:46 +0100
MIME-Version: 1.0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> Hi,
>
> I have a PCI sound card that is sound blaster PRO
> compatible.  But FreeBSD could not recognize this
> card.
> I did recompile the kernel but I could not create the
> /dev/snd0 using "sh MAKEDEV snd0".
> Please tell me how to solve this problem.

The kernel should recognize the card if the sound driver is
compiled in, or the module is loaded at boot time.

If it is really SB Pro compatible on the hardware level, then
all that should be needed is to add the cards ID's to the probing
code if it is a PnP card.  If it is not, and the card and the
driver agrees on the resources, then you're probably out of luck.

If the card is SB Pro compatible in the marketing departments
minds, (read: softwarebased emulation) then you will have to
find a driver that supports the actual chipset that is used.

---
Erik H. Bakke

Don't ask "Who invented time?", the real question is "When was time
invented?"




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Nov  6  9:46: 5 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from teapot23.domain2.bigpond.com (teapot23.domain2.bigpond.com [139.134.5.165])
	by hub.freebsd.org (Postfix) with SMTP id 2256C37B4C5
	for <freebsd-hardware@freebsd.org>; Mon,  6 Nov 2000 09:46:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by teapot23.domain2.bigpond.com (NTMail 3.02.13) with ESMTP id ua913348 for <freebsd-hardware@freebsd.org>; Tue, 7 Nov 2000 03:45:58 +1000
Received: from per-ppp-102.tpgi.com.au ([203.12.166.102]) by mail2.bigpond.com (Claudes-Kaleidoscopic-MailRouter V2.9c 3/1877106); 07 Nov 2000 03:45:56
From: Shaun Dwyer <sldwyer@bigpond.com>
Reply-To: sldwyer@bigpond.com
To: freebsd-hardware@FREEBSD.ORG
Subject: Parallel LCD support
Date: Tue, 7 Nov 2000 01:49:32 +0800
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <00110701501104.01538@neptune.ctnet.org.au>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi everyone...

First of all, as I am not subscribed to the mailing lists, please email me
directly (sldwyer@bigpond.com)

Right.. down to business...

I have just put together an mp3 playing machine to stick in the boot of my car.

Presently, it runs Linux, but I would love to 'upgrade' to FreeBSD :-)

Really, the only thing stopping me is the lack of a driver for a HD44780 
LCD display (runs off a parallel port) similar to Michael Selivanov's driver.
(available from: http://www4.infi.net/~cpinkham/cajun/code/lcd-0.2c.tar.gz).

The software used for control is Cajun (http://cajun.sourceforge.net).
It is all written in perl, so i'm sure even I could get it running on FreeBSD.

Michael's Driver emulates a Matrix-Orbital LCD display (an overly expensive
serial LCD display), and provides a /dev/lcd which Cajun can talk to quite
easily.


I had a look in /usr/src/share/examples/ppi/ppilcd.c
It appears to be something capable of talking to a HD44780 display, however, I
was unable to compile it. make generated a pile of errors and bombed out.


I would be most greatful if some one would port Michael's Driver, or provide
some form of 'driver' that works that I can use. Unfortunately, I am unable to
code in C, otherwise I would do it myself. I want to learn some C in the near
future... but time is against me. I'll have to wait untill the TEE is over (in
Australia thats the final High-school exams).


One of the _many_ reasons I want to use FreeBSD over linux for this is because
I am having stability problems with Linux. Its not as though I'm running cheap
hardware either. Asus P55T2P4 motherboard, P200, Adaptec 1542CF (yes, slow ISA
scsi card... but its stable under FreeBSD and works well), Vibra16 soundcard,
Dec Tulip chipset nic, etc etc.

another reason is i know FreeBSD like the back of my hand. I can do just about
anything in it, where as Linux is a hell of a lot harder. Its much more
dificult to set up, and the kernel... I want to throttle some one every time I
have to rebuild one.

Any way, I'm rambling on a bit now... so I think I will stop :-)

Thanks in advance to any one who wants to help.


Shaun



-- 
----------------------
Shaun Dwyer
sldwyer@bigpond.com
Zeus@quakeclan.net
----------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Nov  6 10:43:54 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222])
	by hub.freebsd.org (Postfix) with ESMTP id 932F937B479
	for <freebsd-hardware@FreeBSD.org>; Mon,  6 Nov 2000 10:43:52 -0800 (PST)
Received: from laptop.baldwin.cx (john@dhcp241.osd.bsdi.com [204.216.28.241])
	by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eA6IhKH17958;
	Mon, 6 Nov 2000 10:43:20 -0800 (PST)
	(envelope-from jhb@FreeBSD.org)
Message-ID: <XFMail.001106104342.jhb@FreeBSD.org>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <011301c04683$1c98a600$9e0e1b18@austin.rr.com>
Date: Mon, 06 Nov 2000 10:43:42 -0800 (PST)
From: John Baldwin <jhb@FreeBSD.org>
To: "Brandon S. DeYoung" <brandon@schoolpeople.net>
Subject: RE: SMP
Cc: FreeBSDHW <freebsd-hardware@FreeBSD.org>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


On 04-Nov-00 Brandon S. DeYoung wrote:
>     Hi Guys,
>     What's the maximum number of CPU's (x86) supported by FreeBSD?

Theoretically I think it is 15, but I don't think there is any common hardware
out there that supports that many.

> Thanks,
> ~B

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Nov  6 11:16:29 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77])
	by hub.freebsd.org (Postfix) with ESMTP id 71ECB37B479
	for <freebsd-hardware@FREEBSD.ORG>; Mon,  6 Nov 2000 11:16:24 -0800 (PST)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA6JL5F19109;
	Mon, 6 Nov 2000 11:21:18 -0800 (PST)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200011061921.eA6JL5F19109@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: sldwyer@bigpond.com
Cc: freebsd-hardware@FREEBSD.ORG
Subject: Re: Parallel LCD support 
In-reply-to: Your message of "Tue, 07 Nov 2000 01:49:32 +0800."
             <00110701501104.01538@neptune.ctnet.org.au> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 06 Nov 2000 11:21:05 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> Really, the only thing stopping me is the lack of a driver for a HD44780 
> LCD display (runs off a parallel port) similar to Michael Selivanov's driver.
> (available from: http://www4.infi.net/~cpinkham/cajun/code/lcd-0.2c.tar.gz).

See /usr/share/examples/ppi for a generic LCD interface program with a 
driver for the HD44780 using the 'ppi' "geek port" driver over the 
parallel port.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Mon Nov  6 11:46:44 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1])
	by hub.freebsd.org (Postfix) with ESMTP id 757D637B4C5
	for <freebsd-hardware@FreeBSD.ORG>; Mon,  6 Nov 2000 11:46:40 -0800 (PST)
Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1])
	by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id NAA55747;
	Mon, 6 Nov 2000 13:46:31 -0600 (CST)
	(envelope-from cdillon@wolves.k12.mo.us)
Date: Mon, 6 Nov 2000 13:46:31 -0600 (CST)
From: Chris Dillon <cdillon@wolves.k12.mo.us>
To: Shaun Dwyer <sldwyer@bigpond.com>
Cc: freebsd-hardware@FreeBSD.ORG
Subject: Re: Parallel LCD support
In-Reply-To: <00110701501104.01538@neptune.ctnet.org.au>
Message-ID: <Pine.BSF.4.21.0011061319520.54856-100000@mail.wolves.k12.mo.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 7 Nov 2000, Shaun Dwyer wrote:

> I had a look in /usr/src/share/examples/ppi/ppilcd.c It appears to
> be something capable of talking to a HD44780 display, however, I
> was unable to compile it. make generated a pile of errors and
> bombed out.

Just tried that myself...  To get it to compile, copy ppbconf.h and
ppi.h out of /usr/src/sys/dev/ppbus into the same directory as
ppilcd.c and its Makefile.  Then make depend && make all.  You'll get
an executable called ppilcd.  What you do with it from there is up to
you.  :-)

P.S.  You can read the code to pretty easily find out the commandline
parameters it supports.  The usage() function isn't called when no
paramaters are given, so you'll have to give it an unused parameter
like -x to get its usage.


-- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net
   FreeBSD: The fastest and most stable server OS on the planet.
   For IA32 and Alpha architectures. IA64 and PowerPC under development.
   http://www.freebsd.org




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Tue Nov  7  4:37:35 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from smtp2.port.ru (mx2.port.ru [194.67.23.33])
	by hub.freebsd.org (Postfix) with ESMTP id 013E637B4CF
	for <freebsd-hardware@freebsd.org>; Tue,  7 Nov 2000 04:37:32 -0800 (PST)
Received: from ip86.jeo.ru ([194.84.157.86] helo=myname.my.domain)
	by smtp2.port.ru with smtp (Exim 3.14 #30)
	id 13t80H-0002hR-00
	for freebsd-hardware@freebsd.org; Tue, 07 Nov 2000 15:37:30 +0300
Message-ID: <3A0934E9.59E2B600@mail.ru>
Date: Wed, 08 Nov 2000 11:11:37 +0000
From: Eugeni Doljenko <edoljenko@mail.ru>
X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.2-RELEASE i386)
MIME-Version: 1.0
To: freebsd-hardware@freebsd.org
Subject: Working ESS1868 Sound Card under FreeBSD 3.2-RELEASE.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

My ESS1868 work's fine, but i get :

dmesg:

CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: @@@0000
[0x00000000]
ESS1868 (rev 11)
pcm1 (ESS1868 <ESS1868> sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 on isa
...
pcm0 not probed due to drq conflict with pcm1 at 1 #!!!

In my kernel:

controller      pnp0 
device          pcm0 at isa? port? tty irq 5 drq 1 flags 0x15

cat /dev/sndstat:

FreeBSD Audio Driver (981002) Nov  6 2000 20:03:20
Installed devices:
pcm1: <SoundBlaster Pro 3.1> at 0x220 irq 5 dma 1:1

All the devices were made by the command "sh /dev/MAKEDEV snd1"

When I don't include line:
device          pcm0 at isa? port? tty irq 5 drq 1 flags 0x15 or
device		pcm0
Luigi driver doesn't include into kernel.

How to include Luigi driver into kernel and do not include line
device          pcm0 at isa? port? tty irq 5 drq 1 flags 0x15   ???

Application like xaudio, mpg123, gmix, etc. work good, but

cat hello.au >/dev/audio 
will print:

/kernel: timeout flushing dbuf_out, chan 1 cnt 0x7875 flags 0x00000441

It mean, that correctly work only /dev/dsp?

How to fix this bug?


			Thank!
				Doljenko Eugeni, Russia, Rostov-on-Don.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Tue Nov  7 10:15:44 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from homer.bus.miami.edu (homer.bus.miami.edu [129.171.39.247])
	by hub.freebsd.org (Postfix) with ESMTP id 5305037B479
	for <freebsd-hardware@freebsd.org>; Tue,  7 Nov 2000 10:15:42 -0800 (PST)
Received: from localhost by homer.bus.miami.edu (8.8.8/1.1.19.2/08Mar98-0513AM)
	id NAA0000005236; Tue, 7 Nov 2000 13:15:41 -0500 (EST)
Date: Tue, 7 Nov 2000 13:15:41 -0500 (EST)
From: Adam Blake <blake@sba.miami.edu>
X-Sender: blake@homer.bus.miami.edu
To: freebsd-hardware@freebsd.org
Subject: TRENDnet TE-16XP NIC and FreeBSD
Message-ID: <Pine.OSF.4.10.10011071314570.1735-100000@homer.bus.miami.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Does FreeBSD 4.1 support the TRENDnet TE-16XP 10Base-T 
ethernet card?  I am trying to use this card with FreeBSD 4.1
and the hardware probing at boot-up is not finding this device.

The TRENDnet website says that this particular card is
"Fully NE2000 Compatible" so I am hoping that it will work.

Has anyone else even heard of this NIC or had any experience with
it at all?  Any input would be greatly appreciated.

Here is the website with all the info on the card...

http://www.trendware.com/products/10Mbps/adapter/spec-te16xp.htm

-Adam




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Tue Nov  7 14:16:34 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from gabriel.schoolpeople.net (gabriel.schoolpeople.net [216.34.170.167])
	by hub.freebsd.org (Postfix) with ESMTP id 254DC37B479
	for <freebsd-hardware@FreeBSD.ORG>; Tue,  7 Nov 2000 14:16:32 -0800 (PST)
Received: from dopey (evity.com [216.60.130.10] (may be forged))
	by gabriel.schoolpeople.net (8.9.3/8.9.3) with SMTP id QAA51956
	for <freebsd-hardware@FreeBSD.ORG>; Tue, 7 Nov 2000 16:16:27 -0600 (CST)
	(envelope-from brandon@schoolpeople.net)
Message-ID: <001201c04908$5c489300$5b02a8c0@schoolpeople.net>
From: "Brandon DeYoung" <brandon@schoolpeople.net>
To: <freebsd-hardware@FreeBSD.ORG>
Subject: 3Ware RAID (RELEASE4.2)
Date: Tue, 7 Nov 2000 16:16:21 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000F_01C048D6.110DEB60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C048D6.110DEB60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

    Will 3ware's RAID controllers <ever> allow rebuilding a degraded =
array without rebooting the server? (I'm hoping this is added to the 4.2 =
RELEASE). What's the target launch date for 4.2?

Thanks,
~B


------=_NextPart_000_000F_01C048D6.110DEB60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; Will 3ware's RAID =
controllers=20
&lt;ever&gt; allow rebuilding a&nbsp;degraded&nbsp;array without =
rebooting the=20
server? (I'm hoping this is added to the 4.2 RELEASE). What's =
the&nbsp;target=20
launch date for 4.2?</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial>~B</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_000F_01C048D6.110DEB60--



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Tue Nov  7 14:36:16 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77])
	by hub.freebsd.org (Postfix) with ESMTP id D13E237B479
	for <freebsd-hardware@FreeBSD.ORG>; Tue,  7 Nov 2000 14:36:13 -0800 (PST)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA7Mf4F33362;
	Tue, 7 Nov 2000 14:41:10 -0800 (PST)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200011072241.eA7Mf4F33362@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Brandon DeYoung" <brandon@schoolpeople.net>
Cc: freebsd-hardware@FreeBSD.ORG
Subject: Re: 3Ware RAID (RELEASE4.2) 
In-reply-to: Your message of "Tue, 07 Nov 2000 16:16:21 CST."
             <001201c04908$5c489300$5b02a8c0@schoolpeople.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 07 Nov 2000 14:41:03 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>     Will 3ware's RAID controllers <ever> allow rebuilding a degraded =
> array without rebooting the server? (I'm hoping this is added to the 4.2 =
> RELEASE).

This requires 3ware's '3dm' tool.  You should bug them about it; they 
have a FreeBSD version in beta right now.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Tue Nov  7 15: 3:55 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from angryfist.fasttrackmonkey.com (angryfist.fasttrackmonkey.com [216.223.217.166])
	by hub.freebsd.org (Postfix) with ESMTP id D096537B479
	for <freebsd-hardware@freebsd.org>; Tue,  7 Nov 2000 15:03:52 -0800 (PST)
Received: by angryfist.fasttrackmonkey.com (Postfix, from userid 1001)
	id 329104EEF; Tue,  7 Nov 2000 18:06:54 -0500 (EST)
Date: Tue, 7 Nov 2000 18:06:54 -0500 (EST)
From: spork@fasttrackmonkey.com
To: freebsd-hardware@freebsd.org
Subject: Server-class mobo's
Message-ID: <Pine.GSO.4.20.0011071802500.12944-100000@frothy.fasttrackmonkey.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

Anyone have any ideas on who besides Intel uses this Phoenix BIOS that
integrates a full serial console (from power on to OS boot)?

http://www.phoenix.com/platform/serverbios.html

The only feature that intrigues me is the serial console; very useful for
colo'd servers.  It allows you into the normal BIOS screens as well as any
SCSI controller/RAID controller setups.

Intel is a bit pricey for the current 133MHz bus boards...

Thanks,

Charles



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Tue Nov  7 15:14:25 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77])
	by hub.freebsd.org (Postfix) with ESMTP id 129D937B479
	for <freebsd-hardware@freebsd.org>; Tue,  7 Nov 2000 15:14:24 -0800 (PST)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA7NJBF33525;
	Tue, 7 Nov 2000 15:19:19 -0800 (PST)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200011072319.eA7NJBF33525@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: spork@fasttrackmonkey.com
Cc: freebsd-hardware@freebsd.org
Subject: Re: Server-class mobo's 
In-reply-to: Your message of "Tue, 07 Nov 2000 18:06:54 EST."
             <Pine.GSO.4.20.0011071802500.12944-100000@frothy.fasttrackmonkey.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 07 Nov 2000 15:19:11 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> Hi,
> 
> Anyone have any ideas on who besides Intel uses this Phoenix BIOS that
> integrates a full serial console (from power on to OS boot)?
> 
> http://www.phoenix.com/platform/serverbios.html
> 
> The only feature that intrigues me is the serial console; very useful for
> colo'd servers.  It allows you into the normal BIOS screens as well as any
> SCSI controller/RAID controller setups.
> 
> Intel is a bit pricey for the current 133MHz bus boards...

Tyan are doing this on the S2500 and S2510 boards, which BSDi are 
building into our current family of 1U and 2U server systems.

Note that most of these BIOS-serial designs are of the screen-scraper 
variety, so you still need a video card.  Ugh.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Tue Nov  7 15:57: 7 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from engr.orst.edu (ENGR.ORST.EDU [128.193.54.1])
	by hub.freebsd.org (Postfix) with ESMTP id BE0BF37B479
	for <freebsd-hardware@freebsd.org>; Tue,  7 Nov 2000 15:57:04 -0800 (PST)
Received: from eel.ENGR.ORST.EDU (eel.ENGR.ORST.EDU [128.193.55.69])
	by engr.orst.edu (8.9.3/8.9.3) with ESMTP id PAA25061
	for <freebsd-hardware@freebsd.org>; Tue, 7 Nov 2000 15:56:58 -0800 (PST)
Received: (from shepard@localhost)
	by eel.ENGR.ORST.EDU (8.9.3/8.9.3) id PAA06983
	for freebsd-hardware@freebsd.org; Tue, 7 Nov 2000 15:56:58 -0800 (PST)
Date: Tue, 7 Nov 2000 15:56:58 -0800
From: Darren Shepard <shepard@engr.orst.edu>
To: freebsd-hardware@freebsd.org
Subject: Matrox G450 /w XF86 3.3.6
Message-ID: <20001107155658.E776@eel.ENGR.ORST.EDU>
Reply-To: Darren Shepard <dss@orst.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.2i
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Has anyone tried using a Matrox G450 under XF86 3.3.6?  There's no
official support AFAIK, but I'm curious to know if it will work as a 
G400 with the existing SVGA/mga driver.

-- 
Darren Shepard | dss@orst.edu


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Tue Nov  7 23:27:14 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from averroe.polito.it (averroe.polito.it [130.192.4.32])
	by hub.freebsd.org (Postfix) with SMTP id E8C5037B479
	for <freebsd-hardware@freebsd.org>; Tue,  7 Nov 2000 23:27:08 -0800 (PST)
Received: (qmail 35693 invoked by uid 10003); 8 Nov 2000 07:27:00 -0000
Received: from demostene.polito.it (130.192.4.73)
  by averroe.polito.it with SMTP; 8 Nov 2000 07:27:00 -0000
Message-Id: <5.0.0.25.0.20001108082653.00aa51b0@averroe.polito.it>
X-Sender: tealdi@averroe.polito.it
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Wed, 08 Nov 2000 08:27:00 +0100
To: freebsd-hardware@freebsd.org
From: Paolo Tealdi <tealdi@sb.polito.it>
Subject:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org




Ing. Paolo Tealdi         Library & News System Administrator
Politecnico Torino        Phone : +39-11-5646714 , FAX : +39-11-5646799
C.so D. degli Abruzzi, 24 - 10129 Torino - ITALY  Email: tealdi@sb.polito.it



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8  7:57:32 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from raven.ravenbrook.com (raven.ravenbrook.com [193.82.131.18])
	by hub.freebsd.org (Postfix) with ESMTP
	id 98FC637B4C5; Wed,  8 Nov 2000 07:57:10 -0800 (PST)
Received: from raven.ravenbrook.com (nb@raven.ravenbrook.com [193.82.131.18])
	by raven.ravenbrook.com (8.9.3/8.9.3) with ESMTP id PAA04478;
	Wed, 8 Nov 2000 15:57:21 GMT
From: Nick Barnes <Nick.Barnes@pobox.com>
To: freebsd-multimedia@freebsd.org, freebsd-hardware@freebsd.org
Subject: Intel D815EEA motherboard sound and network
Date: Wed, 08 Nov 2000 15:57:10 +0000
Message-ID: <4453.973699030@raven.ravenbrook.com>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I have a new PC with an Intel D815EEA motherboard.  This comes with
onboard sound, network, and display.  I have a Matrox graphics card so
I don't care about the onboard display.

The motherboard doc claims that the network is compatible with Intel
Pro 100, so I expected it to show up as fxp0; it didn't.  Archives of
freebsd-hardware suggest this is known and unlikely to be fixed.  Oh
well. I've put a RealTek NIC in instead.

The motherboard doc also claims that the sound is compatible with
SoundBlaster PCI 128.  I've never used sound under FreeBSD, so I'm a
bit of a novice here.  Can someone advise me what I need in my kernel
config to drive this?  I've tried a couple of things (pcm, snd) with
no visible effect on the dmesg.

Here's a verbose boot with GENERIC.  Note also the "Bad PnP BIOS data
checksum" message.

Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.1-RELEASE #0: Fri Jul 28 14:30:31 GMT 2000
jkh@ref4.freebsd.org:/usr/src/sys/compile/GENERIC
Calibrating clock(s) ... TSC clock: 797557265 Hz, i8254 clock: 1193154 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254"  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
CPU: Pentium III/Pentium III Xeon/Celeron (797.58-MHz 686-class CPU)
Origin = "GenuineIntel"  Id = 0x686  Stepping = 6
Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM>
real memory  = 268173312 (261888K bytes)
Physical memory chunk(s):
0x00001000 - 0x0009efff, 647168 bytes (158 pages)
0x00426000 - 0x0ffb7fff, 263790592 bytes (64402 pages)
avail memory = 256700416 (250684K bytes)
bios32: Found BIOS32 Service Directory header at 0xc00fda60
bios32: Entry = 0xfda74 (c00fda74)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xda95
pnpbios: Bad PnP BIOS data checksum
Other BIOS signatures found:
ACPI: 000ff980
Preloaded elf kernel "kernel.GENERIC" at 0xc040d000.
Pentium Pro MTRR support enabled
md0: Malloc disk
Creating DISK md0
Math emulator present
pci_open(1):    mode 1 addr port (0x0cf8) is 0x8000005c
pci_open(1a):   mode1res=0x80000000 (0x80000000)
pci_cfgcheck:   device 0 [class=060000] [hdr=00] is there (id=11308086)
npx0: <math processor> on motherboard
npx0: INT 16 interface
pci_open(1):    mode 1 addr port (0x0cf8) is 0x00000000
pci_open(1a):   mode1res=0x80000000 (0x80000000)
pci_cfgcheck:   device 0 [class=060000] [hdr=00] is there (id=11308086)
pcib0: <Host to PCI bridge> on motherboard
found-> vendor=0x8086, dev=0x1130, revid=0x02
class=06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0        secondarybus=0
map[10]: type 1, range 32, base f8000000, size 26
found-> vendor=0x8086, dev=0x1131, revid=0x02
class=06-04-00, hdrtype=0x01, mfdev=0
subordinatebus=2        secondarybus=2
found-> vendor=0x8086, dev=0x244e, revid=0x01
class=06-04-00, hdrtype=0x01, mfdev=0
subordinatebus=1        secondarybus=1
found-> vendor=0x8086, dev=0x2440, revid=0x01
class=06-01-00, hdrtype=0x00, mfdev=1
subordinatebus=0        secondarybus=0
found-> vendor=0x8086, dev=0x244b, revid=0x01
class=01-01-80, hdrtype=0x00, mfdev=0
subordinatebus=0        secondarybus=0
map[20]: type 1, range 32, base 0000ffa0, size  4
found-> vendor=0x8086, dev=0x2442, revid=0x01
class=0c-03-00, hdrtype=0x00, mfdev=0
subordinatebus=0        secondarybus=0
intpin=d, irq=11
map[20]: type 1, range 32, base 0000ef40, size  5
found-> vendor=0x8086, dev=0x2443, revid=0x01
class=0c-05-00, hdrtype=0x00, mfdev=0
subordinatebus=0        secondarybus=0
intpin=b, irq=9
map[20]: type 1, range 32, base 0000efa0, size  4
found-> vendor=0x8086, dev=0x2444, revid=0x01
class=0c-03-00, hdrtype=0x00, mfdev=0
subordinatebus=0        secondarybus=0
intpin=c, irq=10
map[20]: type 1, range 32, base 0000ef80, size  5
found-> vendor=0x8086, dev=0x2445, revid=0x01
class=04-01-00, hdrtype=0x00, mfdev=0
subordinatebus=0        secondarybus=0
intpin=b, irq=9
map[10]: type 1, range 32, base 0000e800, size  8
map[14]: type 1, range 32, base 0000ef00, size  6
pci0: <PCI bus> on pcib0
pcib1: <PCI to PCI bridge (vendor=8086 device=1131)> at device 1.0 on pci0
found-> vendor=0x102b, dev=0x0525, revid=0x04
class=03-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0        secondarybus=0
intpin=a, irq=11
map[10]: type 1, range 32, base f2000000, size 25
map[14]: type 1, range 32, base feafc000, size 14
map[18]: type 1, range 32, base fe000000, size 23
pci2: <PCI bus> on pcib1
pci2: <Matrox MGA G400 AGP graphics accelerator> (vendor=0x102b, dev=0x0525) at 0.0 irq 11
pcib2: <PCI to PCI bridge (vendor=8086 device=244e)> at device 30.0 on pci0
found-> vendor=0x8086, dev=0x2449, revid=0x01
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0        secondarybus=0
intpin=a, irq=11
map[10]: type 1, range 32, base fd9fe000, size 12
map[14]: type 1, range 32, base 0000df00, size  6
found-> vendor=0x10ec, dev=0x8139, revid=0x10
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0        secondarybus=0
intpin=a, irq=11
map[10]: type 1, range 32, base 0000d800, size  8
map[14]: type 1, range 32, base fd9ffc00, size  8
pci1: <PCI bus> on pcib2
pci1: <unknown card> (vendor=0x8086, dev=0x2449) at 8.0 irq 11
rl0: <RealTek 8139 10/100BaseTX> port 0xd800-0xd8ff mem 0xfd9ffc00-0xfd9ffcff irq 11 at device 13.0 on pci1
rl0: Ethernet address: 00:50:fc:01:f4:0e
miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
bpf: rl0 attached
isab0: <PCI to ISA bridge (vendor=8086 device=2440)> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Generic PCI ATA controller> port 0xffa0-0xffaf at device 31.1 on pci0
ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0
ata0: mask=03 status0=50 status1=00
ata0: mask=03 status0=50 status1=00
ata0: devices = 0x1
ata0: at 0x1f0 irq 14 on atapci0
ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8
ata1: mask=03 status0=50 status1=00
ata1: mask=03 status0=10 status1=00
ata1: devices = 0x4
ata1: at 0x170 irq 15 on atapci0
uhci0: <UHCI (generic) USB controller> port 0xef40-0xef5f irq 11 at device 31.2 on pci0
uhci0: (New UHCI DeviceId=0x24428086)
using shared irq11.
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: (0x24428086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub0: port 1 power on failed, IOERROR
uhub0: port 2 power on failed, IOERROR
pci0: <unknown card> (vendor=0x8086, dev=0x2443) at 31.3 irq 9
uhci1: <UHCI (generic) USB controller> port 0xef80-0xef9f irq 10 at device 31.4 on pci0
uhci1: (New UHCI DeviceId=0x24448086)
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: (0x24448086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhub1: port 1 power on failed, IOERROR
uhub1: port 2 power on failed, IOERROR
pci0: <unknown card> (vendor=0x8086, dev=0x2445) at 31.5 irq 9
Trying Read_Port at 203
Trying Read_Port at 243
Trying Read_Port at 283
Trying Read_Port at 2c3
Trying Read_Port at 303
Trying Read_Port at 343
Trying Read_Port at 383
Trying Read_Port at 3c3
ata-: ata0 exists, using next available unit number
ata-: ata1 exists, using next available unit number
isa_probe_children: disabling PnP devices
isa_probe_children: probing non-PnP devices
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
bt0: Failed Status Reg Test - fe
bt_isa_probe: Probe failed at 0x330
bt0: Failed Status Reg Test - ff
bt_isa_probe: Probe failed at 0x334
bt0: Failed Status Reg Test - ff
bt_isa_probe: Probe failed at 0x230
bt0: Failed Status Reg Test - ff
bt_isa_probe: Probe failed at 0x234
bt0: Failed Status Reg Test - ff
bt_isa_probe: Probe failed at 0x130
bt0: Failed Status Reg Test - ff
bt_isa_probe: Probe failed at 0x134
aha0: status reg test failed fe
aha0: status reg test failed ff
ated 4 times
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
atkbd: the current kbd controller command byte 0065
atkbd: keyboard ID 0x41ab (2)
kbdc: RESET_KBD return code:00fa
kbdc: RESET_KBD status:00aa
kbd0 at atkbd0
kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000
psm0: current command byte:0065
kbdc: TEST_AUX_PORT status:0000
kbdc: RESET_AUX return code:00fa
kbdc: RESET_AUX status:00aa
kbdc: RESET_AUX ID:0000
psm: status 00 02 64
psm: status 00 00 64
psm: status 00 03 64
psm: status 00 03 64
psm: data 08 06 05
psm: data 08 01 00
psm: status 00 02 64
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3-00, 3 buttons
psm0: config:00000000, flags:00000000, packet size:4
psm0: syncmask:08, syncbits:08
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
fb0: vga0, vga, type:VGA (5), flags:0x7007f
fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000
fb0: init mode:24, bios mode:3, current mode:24
fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k
VGA parameters upon power-up
50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
VGA parameters in BIOS for mode 24
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
EGA/VGA parameters to be used for mode 24
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sc0: fb0, kbd0, terminal emulator: sc (syscons terminal)
pcic1: not probed (disabled)
sio0: irq maps: 0x41 0x51 0x41 0x41
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: irq maps: 0x41 0x49 0x41 0x41
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
sio2: not probed (disabled)
sio3: not probed (disabled)
ppc0: parallel port found at 0x378
ppc0: using extended I/O port range
ppc0: ECP SPP ECP+EPP SPP
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppi0: <Parallel I/O> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
plip0: <PLIP network interface> on ppbus0
bpf: lp0 attached
isa_probe_children: probing PnP devices
BIOS Geometries:
0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors
0 accounted for
Device configuration finished.
bpf: sl0 attached
bpf: ppp0 attached
new masks: bio 68cc40, tty 63109a, net 67189a
bpf: lo0 attached
bpf: gif0 attached
bpf: gif1 attached
bpf: gif2 attached
bpf: gif3 attached
bpf: faith0 attached
ad0: <IBM-DTLA-307045/TX6OA60A> ATA-5 disk at ata0 as master
ad0: 43979MB (90069840 sectors), 89355 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 32 depth queue, BIOSDMA
ad0: piomode=4 dmamode=2 udmamode=4 cblid=1
Creating DISK ad0
Creating DISK wd0
ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1
ata1-master: success setting up PIO4 mode on generic chip
acd0: <SAMSUNG CD-ROM SC-152C/CS02> CDROM drive at ata1 as master
acd0: read 171KB/s (8937KB/s), 128KB buffer, PIO4
acd0: Reads: CD-R, CD-RW, CD-DA stream, packet
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked
Mounting root from ufs:/dev/ad0s1a
ad0s1: type 0xa5, start 63, end = 41929649, size 41929587 : OK
start_init: trying /sbin/init


--
FreeBSD 2.2.8-RELEASE: up 6 days, 5:09
last reboot Thu Nov 2 10:55 (lightning strike)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8  8:41:35 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166])
	by hub.freebsd.org (Postfix) with ESMTP
	id 748D537B4CF; Wed,  8 Nov 2000 08:41:32 -0800 (PST)
Received: by arg1.demon.co.uk (Postfix, from userid 300)
	id E42879B0F; Wed,  8 Nov 2000 16:41:26 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by arg1.demon.co.uk (Postfix) with ESMTP
	id DC9F35D08; Wed,  8 Nov 2000 16:41:26 +0000 (GMT)
Date: Wed, 8 Nov 2000 16:41:26 +0000 (GMT)
From: Andrew Gordon <arg@arg1.demon.co.uk>
X-Sender: arg@server.arg.sj.co.uk
To: Mike Smith <msmith@freebsd.org>
Cc: spork@fasttrackmonkey.com, freebsd-hardware@freebsd.org
Subject: Re: Server-class mobo's 
In-Reply-To: <200011072319.eA7NJBF33525@mass.osd.bsdi.com>
Message-ID: <Pine.BSF.4.21.0011081636160.30937-100000@server.arg.sj.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 7 Nov 2000, Mike Smith wrote:
> > 
> > Anyone have any ideas on who besides Intel uses this Phoenix BIOS that
> > integrates a full serial console (from power on to OS boot)?
> > 
> > http://www.phoenix.com/platform/serverbios.html
> > 
> > The only feature that intrigues me is the serial console; very useful for
> > colo'd servers.  It allows you into the normal BIOS screens as well as any
> > SCSI controller/RAID controller setups.
> > 
> > Intel is a bit pricey for the current 133MHz bus boards...
> 
> Tyan are doing this on the S2500 and S2510 boards, which BSDi are 
> building into our current family of 1U and 2U server systems.
> 
> Note that most of these BIOS-serial designs are of the screen-scraper 
> variety, so you still need a video card.  Ugh.

The version used in Intel's own 1U servers
(http://www.intel.com/network/products/isp1100.htm) is indeed a
screen-scraper, but you _don't_ need a video card installed: there's
no on-board video, but it still works.  I guess that it maps in some of
the main DRAM using the same technique as used for shadowing the BIOS ROM
- but since it works without problems, I haven't investigated too deeply.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8  9:12:58 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from elvis.mu.org (elvis.mu.org [207.154.226.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6415337B479; Wed,  8 Nov 2000 09:12:42 -0800 (PST)
Received: by elvis.mu.org (Postfix, from userid 1000)
	id 0239D2B261; Wed,  8 Nov 2000 11:12:36 -0600 (CST)
Date: Wed, 8 Nov 2000 09:12:36 -0800
From: Paul Saab <paul@mu.org>
To: Nick Barnes <Nick.Barnes@pobox.com>
Cc: freebsd-multimedia@freebsd.org, freebsd-hardware@freebsd.org
Subject: Re: Intel D815EEA motherboard sound and network
Message-ID: <20001108091236.A41632@elvis.mu.org>
References: <4453.973699030@raven.ravenbrook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <4453.973699030@raven.ravenbrook.com>; from Nick.Barnes@pobox.com on Wed, Nov 08, 2000 at 03:57:10PM +0000
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

You need to run 4-stable or wait for 4.2-RELEASE to come out to support
the onboard ethernet on the Intel 815 board.  I am going to try and get
Cameron an 815 board so he can do the sound support, but that is taking
a bit of time to get the hardware for him.

Nick Barnes (Nick.Barnes@pobox.com) wrote:
> I have a new PC with an Intel D815EEA motherboard.  This comes with
> onboard sound, network, and display.  I have a Matrox graphics card so
> I don't care about the onboard display.
> 
> The motherboard doc claims that the network is compatible with Intel
> Pro 100, so I expected it to show up as fxp0; it didn't.  Archives of
> freebsd-hardware suggest this is known and unlikely to be fixed.  Oh
> well. I've put a RealTek NIC in instead.
> 
> The motherboard doc also claims that the sound is compatible with
> SoundBlaster PCI 128.  I've never used sound under FreeBSD, so I'm a
> bit of a novice here.  Can someone advise me what I need in my kernel
> config to drive this?  I've tried a couple of things (pcm, snd) with
> no visible effect on the dmesg.
> 
> Here's a verbose boot with GENERIC.  Note also the "Bad PnP BIOS data
> checksum" message.
> 
> Copyright (c) 1992-2000 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD 4.1-RELEASE #0: Fri Jul 28 14:30:31 GMT 2000
> jkh@ref4.freebsd.org:/usr/src/sys/compile/GENERIC
> Calibrating clock(s) ... TSC clock: 797557265 Hz, i8254 clock: 1193154 Hz
> CLK_USE_I8254_CALIBRATION not specified - using default frequency
> Timecounter "i8254"  frequency 1193182 Hz
> CLK_USE_TSC_CALIBRATION not specified - using old calibration method
> CPU: Pentium III/Pentium III Xeon/Celeron (797.58-MHz 686-class CPU)
> Origin = "GenuineIntel"  Id = 0x686  Stepping = 6
> Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM>
> real memory  = 268173312 (261888K bytes)
> Physical memory chunk(s):
> 0x00001000 - 0x0009efff, 647168 bytes (158 pages)
> 0x00426000 - 0x0ffb7fff, 263790592 bytes (64402 pages)
> avail memory = 256700416 (250684K bytes)
> bios32: Found BIOS32 Service Directory header at 0xc00fda60
> bios32: Entry = 0xfda74 (c00fda74)  Rev = 0  Len = 1
> pcibios: PCI BIOS entry at 0xda95
> pnpbios: Bad PnP BIOS data checksum
> Other BIOS signatures found:
> ACPI: 000ff980
> Preloaded elf kernel "kernel.GENERIC" at 0xc040d000.
> Pentium Pro MTRR support enabled
> md0: Malloc disk
> Creating DISK md0
> Math emulator present
> pci_open(1):    mode 1 addr port (0x0cf8) is 0x8000005c
> pci_open(1a):   mode1res=0x80000000 (0x80000000)
> pci_cfgcheck:   device 0 [class=060000] [hdr=00] is there (id=11308086)
> npx0: <math processor> on motherboard
> npx0: INT 16 interface
> pci_open(1):    mode 1 addr port (0x0cf8) is 0x00000000
> pci_open(1a):   mode1res=0x80000000 (0x80000000)
> pci_cfgcheck:   device 0 [class=060000] [hdr=00] is there (id=11308086)
> pcib0: <Host to PCI bridge> on motherboard
> found-> vendor=0x8086, dev=0x1130, revid=0x02
> class=06-00-00, hdrtype=0x00, mfdev=0
> subordinatebus=0        secondarybus=0
> map[10]: type 1, range 32, base f8000000, size 26
> found-> vendor=0x8086, dev=0x1131, revid=0x02
> class=06-04-00, hdrtype=0x01, mfdev=0
> subordinatebus=2        secondarybus=2
> found-> vendor=0x8086, dev=0x244e, revid=0x01
> class=06-04-00, hdrtype=0x01, mfdev=0
> subordinatebus=1        secondarybus=1
> found-> vendor=0x8086, dev=0x2440, revid=0x01
> class=06-01-00, hdrtype=0x00, mfdev=1
> subordinatebus=0        secondarybus=0
> found-> vendor=0x8086, dev=0x244b, revid=0x01
> class=01-01-80, hdrtype=0x00, mfdev=0
> subordinatebus=0        secondarybus=0
> map[20]: type 1, range 32, base 0000ffa0, size  4
> found-> vendor=0x8086, dev=0x2442, revid=0x01
> class=0c-03-00, hdrtype=0x00, mfdev=0
> subordinatebus=0        secondarybus=0
> intpin=d, irq=11
> map[20]: type 1, range 32, base 0000ef40, size  5
> found-> vendor=0x8086, dev=0x2443, revid=0x01
> class=0c-05-00, hdrtype=0x00, mfdev=0
> subordinatebus=0        secondarybus=0
> intpin=b, irq=9
> map[20]: type 1, range 32, base 0000efa0, size  4
> found-> vendor=0x8086, dev=0x2444, revid=0x01
> class=0c-03-00, hdrtype=0x00, mfdev=0
> subordinatebus=0        secondarybus=0
> intpin=c, irq=10
> map[20]: type 1, range 32, base 0000ef80, size  5
> found-> vendor=0x8086, dev=0x2445, revid=0x01
> class=04-01-00, hdrtype=0x00, mfdev=0
> subordinatebus=0        secondarybus=0
> intpin=b, irq=9
> map[10]: type 1, range 32, base 0000e800, size  8
> map[14]: type 1, range 32, base 0000ef00, size  6
> pci0: <PCI bus> on pcib0
> pcib1: <PCI to PCI bridge (vendor=8086 device=1131)> at device 1.0 on pci0
> found-> vendor=0x102b, dev=0x0525, revid=0x04
> class=03-00-00, hdrtype=0x00, mfdev=0
> subordinatebus=0        secondarybus=0
> intpin=a, irq=11
> map[10]: type 1, range 32, base f2000000, size 25
> map[14]: type 1, range 32, base feafc000, size 14
> map[18]: type 1, range 32, base fe000000, size 23
> pci2: <PCI bus> on pcib1
> pci2: <Matrox MGA G400 AGP graphics accelerator> (vendor=0x102b, dev=0x0525) at 0.0 irq 11
> pcib2: <PCI to PCI bridge (vendor=8086 device=244e)> at device 30.0 on pci0
> found-> vendor=0x8086, dev=0x2449, revid=0x01
> class=02-00-00, hdrtype=0x00, mfdev=0
> subordinatebus=0        secondarybus=0
> intpin=a, irq=11
> map[10]: type 1, range 32, base fd9fe000, size 12
> map[14]: type 1, range 32, base 0000df00, size  6
> found-> vendor=0x10ec, dev=0x8139, revid=0x10
> class=02-00-00, hdrtype=0x00, mfdev=0
> subordinatebus=0        secondarybus=0
> intpin=a, irq=11
> map[10]: type 1, range 32, base 0000d800, size  8
> map[14]: type 1, range 32, base fd9ffc00, size  8
> pci1: <PCI bus> on pcib2
> pci1: <unknown card> (vendor=0x8086, dev=0x2449) at 8.0 irq 11
> rl0: <RealTek 8139 10/100BaseTX> port 0xd800-0xd8ff mem 0xfd9ffc00-0xfd9ffcff irq 11 at device 13.0 on pci1
> rl0: Ethernet address: 00:50:fc:01:f4:0e
> miibus0: <MII bus> on rl0
> rlphy0: <RealTek internal media interface> on miibus0
> rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> bpf: rl0 attached
> isab0: <PCI to ISA bridge (vendor=8086 device=2440)> at device 31.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <Generic PCI ATA controller> port 0xffa0-0xffaf at device 31.1 on pci0
> ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0
> ata0: mask=03 status0=50 status1=00
> ata0: mask=03 status0=50 status1=00
> ata0: devices = 0x1
> ata0: at 0x1f0 irq 14 on atapci0
> ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8
> ata1: mask=03 status0=50 status1=00
> ata1: mask=03 status0=10 status1=00
> ata1: devices = 0x4
> ata1: at 0x170 irq 15 on atapci0
> uhci0: <UHCI (generic) USB controller> port 0xef40-0xef5f irq 11 at device 31.2 on pci0
> uhci0: (New UHCI DeviceId=0x24428086)
> using shared irq11.
> usb0: <UHCI (generic) USB controller> on uhci0
> usb0: USB revision 1.0
> uhub0: (0x24428086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> uhub0: port 1 power on failed, IOERROR
> uhub0: port 2 power on failed, IOERROR
> pci0: <unknown card> (vendor=0x8086, dev=0x2443) at 31.3 irq 9
> uhci1: <UHCI (generic) USB controller> port 0xef80-0xef9f irq 10 at device 31.4 on pci0
> uhci1: (New UHCI DeviceId=0x24448086)
> usb1: <UHCI (generic) USB controller> on uhci1
> usb1: USB revision 1.0
> uhub1: (0x24448086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub1: 2 ports with 2 removable, self powered
> uhub1: port 1 power on failed, IOERROR
> uhub1: port 2 power on failed, IOERROR
> pci0: <unknown card> (vendor=0x8086, dev=0x2445) at 31.5 irq 9
> Trying Read_Port at 203
> Trying Read_Port at 243
> Trying Read_Port at 283
> Trying Read_Port at 2c3
> Trying Read_Port at 303
> Trying Read_Port at 343
> Trying Read_Port at 383
> Trying Read_Port at 3c3
> ata-: ata0 exists, using next available unit number
> ata-: ata1 exists, using next available unit number
> isa_probe_children: disabling PnP devices
> isa_probe_children: probing non-PnP devices
> fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
> fdc0: FIFO enabled, 8 bytes threshold
> fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> bt0: Failed Status Reg Test - fe
> bt_isa_probe: Probe failed at 0x330
> bt0: Failed Status Reg Test - ff
> bt_isa_probe: Probe failed at 0x334
> bt0: Failed Status Reg Test - ff
> bt_isa_probe: Probe failed at 0x230
> bt0: Failed Status Reg Test - ff
> bt_isa_probe: Probe failed at 0x234
> bt0: Failed Status Reg Test - ff
> bt_isa_probe: Probe failed at 0x130
> bt0: Failed Status Reg Test - ff
> bt_isa_probe: Probe failed at 0x134
> aha0: status reg test failed fe
> aha0: status reg test failed ff
> ated 4 times
> atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
> atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
> atkbd: the current kbd controller command byte 0065
> atkbd: keyboard ID 0x41ab (2)
> kbdc: RESET_KBD return code:00fa
> kbdc: RESET_KBD status:00aa
> kbd0 at atkbd0
> kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000
> psm0: current command byte:0065
> kbdc: TEST_AUX_PORT status:0000
> kbdc: RESET_AUX return code:00fa
> kbdc: RESET_AUX status:00aa
> kbdc: RESET_AUX ID:0000
> psm: status 00 02 64
> psm: status 00 00 64
> psm: status 00 03 64
> psm: status 00 03 64
> psm: data 08 06 05
> psm: data 08 01 00
> psm: status 00 02 64
> psm0: <PS/2 Mouse> irq 12 on atkbdc0
> psm0: model IntelliMouse, device ID 3-00, 3 buttons
> psm0: config:00000000, flags:00000000, packet size:4
> psm0: syncmask:08, syncbits:08
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> fb0: vga0, vga, type:VGA (5), flags:0x7007f
> fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000
> fb0: init mode:24, bios mode:3, current mode:24
> fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k
> VGA parameters upon power-up
> 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
> bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 
> b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
> 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
> VGA parameters in BIOS for mode 24
> 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
> bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
> b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
> 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
> EGA/VGA parameters to be used for mode 24
> 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
> bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
> b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
> 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
> sc0: <System console> at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x300>
> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal)
> pcic1: not probed (disabled)
> sio0: irq maps: 0x41 0x51 0x41 0x41
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A
> sio1: irq maps: 0x41 0x49 0x41 0x41
> sio1 at port 0x2f8-0x2ff irq 3 on isa0
> sio1: type 16550A
> sio2: not probed (disabled)
> sio3: not probed (disabled)
> ppc0: parallel port found at 0x378
> ppc0: using extended I/O port range
> ppc0: ECP SPP ECP+EPP SPP
> ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
> ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
> ppc0: FIFO with 16/16/8 bytes threshold
> ppi0: <Parallel I/O> on ppbus0
> lpt0: <Printer> on ppbus0
> lpt0: Interrupt-driven port
> plip0: <PLIP network interface> on ppbus0
> bpf: lp0 attached
> isa_probe_children: probing PnP devices
> BIOS Geometries:
> 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors
> 0 accounted for
> Device configuration finished.
> bpf: sl0 attached
> bpf: ppp0 attached
> new masks: bio 68cc40, tty 63109a, net 67189a
> bpf: lo0 attached
> bpf: gif0 attached
> bpf: gif1 attached
> bpf: gif2 attached
> bpf: gif3 attached
> bpf: faith0 attached
> ad0: <IBM-DTLA-307045/TX6OA60A> ATA-5 disk at ata0 as master
> ad0: 43979MB (90069840 sectors), 89355 cyls, 16 heads, 63 S/T, 512 B/S
> ad0: 16 secs/int, 32 depth queue, BIOSDMA
> ad0: piomode=4 dmamode=2 udmamode=4 cblid=1
> Creating DISK ad0
> Creating DISK wd0
> ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1
> ata1-master: success setting up PIO4 mode on generic chip
> acd0: <SAMSUNG CD-ROM SC-152C/CS02> CDROM drive at ata1 as master
> acd0: read 171KB/s (8937KB/s), 128KB buffer, PIO4
> acd0: Reads: CD-R, CD-RW, CD-DA stream, packet
> acd0: Audio: play, 255 volume levels
> acd0: Mechanism: ejectable tray
> acd0: Medium: no/blank disc inside, unlocked
> Mounting root from ufs:/dev/ad0s1a
> ad0s1: type 0xa5, start 63, end = 41929649, size 41929587 : OK
> start_init: trying /sbin/init
> 
> 
> --
> FreeBSD 2.2.8-RELEASE: up 6 days, 5:09
> last reboot Thu Nov 2 10:55 (lightning strike)
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hardware" in the body of the message

-- 
Paul Saab
Technical Yahoo
paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org
Do You .. uhh .. Yahoo!?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8 10:54:57 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77])
	by hub.freebsd.org (Postfix) with ESMTP
	id D02C237B479; Wed,  8 Nov 2000 10:54:54 -0800 (PST)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA8J0MF03063;
	Wed, 8 Nov 2000 11:00:23 -0800 (PST)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200011081900.eA8J0MF03063@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Andrew Gordon <arg@arg1.demon.co.uk>
Cc: Mike Smith <msmith@freebsd.org>, spork@fasttrackmonkey.com,
	freebsd-hardware@freebsd.org
Subject: Re: Server-class mobo's 
In-reply-to: Your message of "Wed, 08 Nov 2000 16:41:26 GMT."
             <Pine.BSF.4.21.0011081636160.30937-100000@server.arg.sj.co.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 08 Nov 2000 11:00:22 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> > > Anyone have any ideas on who besides Intel uses this Phoenix BIOS that
> > > integrates a full serial console (from power on to OS boot)?
...
> > Note that most of these BIOS-serial designs are of the screen-scraper 
> > variety, so you still need a video card.  Ugh.
> 
> The version used in Intel's own 1U servers
> (http://www.intel.com/network/products/isp1100.htm) is indeed a
> screen-scraper, but you _don't_ need a video card installed: there's
> no on-board video, but it still works.  I guess that it maps in some of
> the main DRAM using the same technique as used for shadowing the BIOS ROM
> - but since it works without problems, I haven't investigated too deeply.

As far as I can tell, it doesn't.  If you check the documentation you'll 
find that the system BIOS is OK without a video card, but you're SOL if 
you want to use the BIOS on an add-in card.  (Since there's only 1.5 
slots, that makes things really awkward...)

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8 10:56:20 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77])
	by hub.freebsd.org (Postfix) with ESMTP
	id 76AC937B479; Wed,  8 Nov 2000 10:56:15 -0800 (PST)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA8IvvF03041;
	Wed, 8 Nov 2000 10:57:58 -0800 (PST)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200011081857.eA8IvvF03041@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Nick Barnes <Nick.Barnes@pobox.com>
Cc: freebsd-multimedia@freebsd.org, freebsd-hardware@freebsd.org
Subject: Re: Intel D815EEA motherboard sound and network 
In-reply-to: Your message of "Wed, 08 Nov 2000 15:57:10 GMT."
             <4453.973699030@raven.ravenbrook.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 08 Nov 2000 10:57:57 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> I have a new PC with an Intel D815EEA motherboard.  This comes with
> onboard sound, network, and display.  I have a Matrox graphics card so
> I don't care about the onboard display.
> 
> The motherboard doc claims that the network is compatible with Intel
> Pro 100, so I expected it to show up as fxp0; it didn't.  Archives of
> freebsd-hardware suggest this is known and unlikely to be fixed.  Oh
> well. I've put a RealTek NIC in instead.

You should check the archives more closely.  It is supported by the fxp 
driver; should be picked up in 4.1.1 or later.

> The motherboard doc also claims that the sound is compatible with
> SoundBlaster PCI 128.  I've never used sound under FreeBSD, so I'm a
> bit of a novice here.  Can someone advise me what I need in my kernel
> config to drive this?  I've tried a couple of things (pcm, snd) with
> no visible effect on the dmesg.

I don't think this is the case; there's support for the ICH2 in the 
pipeline though.

> Here's a verbose boot with GENERIC.  Note also the "Bad PnP BIOS data
> checksum" message.

You gotta love Intel for that one.  Don't worry about it too much.
-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8 10:57:25 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from satan.freebsdsystems.com (unknown [24.69.168.5])
	by hub.freebsd.org (Postfix) with ESMTP
	id 536B037B4C5; Wed,  8 Nov 2000 10:57:04 -0800 (PST)
Received: from wired (wired.CyberTouch.org [24.69.168.3])
	by satan.freebsdsystems.com (8.11.1/8.11.0) with ESMTP id eA8Iv1E03429;
	Wed, 8 Nov 2000 13:57:01 -0500 (EST)
From: "Lanny Baron" <lnb@FreeBSDsystems.COM>
Organization: Freedom Technologies Corporation
To: Paul Saab <paul@mu.org>, freebsd-multimedia@FreeBSD.ORG,
	freebsd-hardware@FreeBSD.ORG, Nick Barnes <Nick.Barnes@pobox.com>
Date: Wed, 8 Nov 2000 13:57:02 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Intel D815EEA motherboard sound and network
Reply-To: lnb@FreeBSDsystems.COM
Message-ID: <3A095BAE.10310.76336B@localhost>
In-reply-to: <20001108091236.A41632@elvis.mu.org>
References: <4453.973699030@raven.ravenbrook.com>; from Nick.Barnes@pobox.com on Wed, Nov 08, 2000 at 03:57:10PM +0000
X-mailer: Pegasus Mail for Win32 (v3.12c)
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi, 
We build Network Servers, and not really home systems 
(http://freebhsdsystems.com). As an IPD I will  contact Intel and 
see if I can get a demo unit. If not I do have a brand new (still 
boxed) D815EEAL and will build a home system (with Systium 
Chassis) and tell you (and Intel as Intel does not list FreeBSD as a 
validated and supported OS, to which I am talking to people at Intel 
to get them to certify FreeBSD as a validated OS) if any, problems 
occur.

I have built several Network servers already mainly for ISP's in the 
U.S. (we are in Canada) and have reported back to Intel, the fact 
that the servers run perfectly without the need to update BIOS 
when Micro$oft OS is installed the reverse is true.

Regards,

Lanny
On 8 Nov 2000, at 9:12, Paul Saab wrote:

> You need to run 4-stable or wait for 4.2-RELEASE to come out to support
> the onboard ethernet on the Intel 815 board.  I am going to try and get
> Cameron an 815 board so he can do the sound support, but that is taking
> a bit of time to get the hardware for him.
> 
> Nick Barnes (Nick.Barnes@pobox.com) wrote:
> > I have a new PC with an Intel D815EEA motherboard.  This comes with
> > onboard sound, network, and display.  I have a Matrox graphics card so
> > I don't care about the onboard display.
> > 
> > The motherboard doc claims that the network is compatible with Intel
> > Pro 100, so I expected it to show up as fxp0; it didn't.  Archives of
> > freebsd-hardware suggest this is known and unlikely to be fixed.  Oh
> > well. I've put a RealTek NIC in instead.
> > 
> > The motherboard doc also claims that the sound is compatible with
> > SoundBlaster PCI 128.  I've never used sound under FreeBSD, so I'm a
> > bit of a novice here.  Can someone advise me what I need in my kernel
> > config to drive this?  I've tried a couple of things (pcm, snd) with
> > no visible effect on the dmesg.
> > 
> > Here's a verbose boot with GENERIC.  Note also the "Bad PnP BIOS data
> > checksum" message.
> > 
> > Copyright (c) 1992-2000 The FreeBSD Project.
> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> > The Regents of the University of California. All rights reserved.
> > FreeBSD 4.1-RELEASE #0: Fri Jul 28 14:30:31 GMT 2000
> > jkh@ref4.freebsd.org:/usr/src/sys/compile/GENERIC
> > Calibrating clock(s) ... TSC clock: 797557265 Hz, i8254 clock: 1193154 Hz
> > CLK_USE_I8254_CALIBRATION not specified - using default frequency
> > Timecounter "i8254"  frequency 1193182 Hz
> > CLK_USE_TSC_CALIBRATION not specified - using old calibration method
> > CPU: Pentium III/Pentium III Xeon/Celeron (797.58-MHz 686-class CPU)
> > Origin = "GenuineIntel"  Id = 0x686  Stepping = 6
> > Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,
XMM>
> > real memory  = 268173312 (261888K bytes)
> > Physical memory chunk(s):
> > 0x00001000 - 0x0009efff, 647168 bytes (158 pages)
> > 0x00426000 - 0x0ffb7fff, 263790592 bytes (64402 pages)
> > avail memory = 256700416 (250684K bytes)
> > bios32: Found BIOS32 Service Directory header at 0xc00fda60
> > bios32: Entry = 0xfda74 (c00fda74)  Rev = 0  Len = 1
> > pcibios: PCI BIOS entry at 0xda95
> > pnpbios: Bad PnP BIOS data checksum
> > Other BIOS signatures found:
> > ACPI: 000ff980
> > Preloaded elf kernel "kernel.GENERIC" at 0xc040d000.
> > Pentium Pro MTRR support enabled
> > md0: Malloc disk
> > Creating DISK md0
> > Math emulator present
> > pci_open(1):    mode 1 addr port (0x0cf8) is 0x8000005c
> > pci_open(1a):   mode1res=0x80000000 (0x80000000)
> > pci_cfgcheck:   device 0 [class=060000] [hdr=00] is there (id=11308086)
> > npx0: <math processor> on motherboard
> > npx0: INT 16 interface
> > pci_open(1):    mode 1 addr port (0x0cf8) is 0x00000000
> > pci_open(1a):   mode1res=0x80000000 (0x80000000)
> > pci_cfgcheck:   device 0 [class=060000] [hdr=00] is there (id=11308086)
> > pcib0: <Host to PCI bridge> on motherboard
> > found-> vendor=0x8086, dev=0x1130, revid=0x02
> > class=06-00-00, hdrtype=0x00, mfdev=0
> > subordinatebus=0        secondarybus=0
> > map[10]: type 1, range 32, base f8000000, size 26
> > found-> vendor=0x8086, dev=0x1131, revid=0x02
> > class=06-04-00, hdrtype=0x01, mfdev=0
> > subordinatebus=2        secondarybus=2
> > found-> vendor=0x8086, dev=0x244e, revid=0x01
> > class=06-04-00, hdrtype=0x01, mfdev=0
> > subordinatebus=1        secondarybus=1
> > found-> vendor=0x8086, dev=0x2440, revid=0x01
> > class=06-01-00, hdrtype=0x00, mfdev=1
> > subordinatebus=0        secondarybus=0
> > found-> vendor=0x8086, dev=0x244b, revid=0x01
> > class=01-01-80, hdrtype=0x00, mfdev=0
> > subordinatebus=0        secondarybus=0
> > map[20]: type 1, range 32, base 0000ffa0, size  4
> > found-> vendor=0x8086, dev=0x2442, revid=0x01
> > class=0c-03-00, hdrtype=0x00, mfdev=0
> > subordinatebus=0        secondarybus=0
> > intpin=d, irq=11
> > map[20]: type 1, range 32, base 0000ef40, size  5
> > found-> vendor=0x8086, dev=0x2443, revid=0x01
> > class=0c-05-00, hdrtype=0x00, mfdev=0
> > subordinatebus=0        secondarybus=0
> > intpin=b, irq=9
> > map[20]: type 1, range 32, base 0000efa0, size  4
> > found-> vendor=0x8086, dev=0x2444, revid=0x01
> > class=0c-03-00, hdrtype=0x00, mfdev=0
> > subordinatebus=0        secondarybus=0
> > intpin=c, irq=10
> > map[20]: type 1, range 32, base 0000ef80, size  5
> > found-> vendor=0x8086, dev=0x2445, revid=0x01
> > class=04-01-00, hdrtype=0x00, mfdev=0
> > subordinatebus=0        secondarybus=0
> > intpin=b, irq=9
> > map[10]: type 1, range 32, base 0000e800, size  8
> > map[14]: type 1, range 32, base 0000ef00, size  6
> > pci0: <PCI bus> on pcib0
> > pcib1: <PCI to PCI bridge (vendor=8086 device=1131)> at device 1.0 on pci0
> > found-> vendor=0x102b, dev=0x0525, revid=0x04
> > class=03-00-00, hdrtype=0x00, mfdev=0
> > subordinatebus=0        secondarybus=0
> > intpin=a, irq=11
> > map[10]: type 1, range 32, base f2000000, size 25
> > map[14]: type 1, range 32, base feafc000, size 14
> > map[18]: type 1, range 32, base fe000000, size 23
> > pci2: <PCI bus> on pcib1
> > pci2: <Matrox MGA G400 AGP graphics accelerator> (vendor=0x102b, dev=0x0525) at 0.0 irq 11
> > pcib2: <PCI to PCI bridge (vendor=8086 device=244e)> at device 30.0 on pci0
> > found-> vendor=0x8086, dev=0x2449, revid=0x01
> > class=02-00-00, hdrtype=0x00, mfdev=0
> > subordinatebus=0        secondarybus=0
> > intpin=a, irq=11
> > map[10]: type 1, range 32, base fd9fe000, size 12
> > map[14]: type 1, range 32, base 0000df00, size  6
> > found-> vendor=0x10ec, dev=0x8139, revid=0x10
> > class=02-00-00, hdrtype=0x00, mfdev=0
> > subordinatebus=0        secondarybus=0
> > intpin=a, irq=11
> > map[10]: type 1, range 32, base 0000d800, size  8
> > map[14]: type 1, range 32, base fd9ffc00, size  8
> > pci1: <PCI bus> on pcib2
> > pci1: <unknown card> (vendor=0x8086, dev=0x2449) at 8.0 irq 11
> > rl0: <RealTek 8139 10/100BaseTX> port 0xd800-0xd8ff mem 0xfd9ffc00-0xfd9ffcff irq 11 at device 
13.0 on pci1
> > rl0: Ethernet address: 00:50:fc:01:f4:0e
> > miibus0: <MII bus> on rl0
> > rlphy0: <RealTek internal media interface> on miibus0
> > rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > bpf: rl0 attached
> > isab0: <PCI to ISA bridge (vendor=8086 device=2440)> at device 31.0 on pci0
> > isa0: <ISA bus> on isab0
> > atapci0: <Generic PCI ATA controller> port 0xffa0-0xffaf at device 31.1 on pci0
> > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0
> > ata0: mask=03 status0=50 status1=00
> > ata0: mask=03 status0=50 status1=00
> > ata0: devices = 0x1
> > ata0: at 0x1f0 irq 14 on atapci0
> > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8
> > ata1: mask=03 status0=50 status1=00
> > ata1: mask=03 status0=10 status1=00
> > ata1: devices = 0x4
> > ata1: at 0x170 irq 15 on atapci0
> > uhci0: <UHCI (generic) USB controller> port 0xef40-0xef5f irq 11 at device 31.2 on pci0
> > uhci0: (New UHCI DeviceId=0x24428086)
> > using shared irq11.
> > usb0: <UHCI (generic) USB controller> on uhci0
> > usb0: USB revision 1.0
> > uhub0: (0x24428086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub0: 2 ports with 2 removable, self powered
> > uhub0: port 1 power on failed, IOERROR
> > uhub0: port 2 power on failed, IOERROR
> > pci0: <unknown card> (vendor=0x8086, dev=0x2443) at 31.3 irq 9
> > uhci1: <UHCI (generic) USB controller> port 0xef80-0xef9f irq 10 at device 31.4 on pci0
> > uhci1: (New UHCI DeviceId=0x24448086)
> > usb1: <UHCI (generic) USB controller> on uhci1
> > usb1: USB revision 1.0
> > uhub1: (0x24448086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> > uhub1: 2 ports with 2 removable, self powered
> > uhub1: port 1 power on failed, IOERROR
> > uhub1: port 2 power on failed, IOERROR
> > pci0: <unknown card> (vendor=0x8086, dev=0x2445) at 31.5 irq 9
> > Trying Read_Port at 203
> > Trying Read_Port at 243
> > Trying Read_Port at 283
> > Trying Read_Port at 2c3
> > Trying Read_Port at 303
> > Trying Read_Port at 343
> > Trying Read_Port at 383
> > Trying Read_Port at 3c3
> > ata-: ata0 exists, using next available unit number
> > ata-: ata1 exists, using next available unit number
> > isa_probe_children: disabling PnP devices
> > isa_probe_children: probing non-PnP devices
> > fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
> > fdc0: FIFO enabled, 8 bytes threshold
> > fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> > bt0: Failed Status Reg Test - fe
> > bt_isa_probe: Probe failed at 0x330
> > bt0: Failed Status Reg Test - ff
> > bt_isa_probe: Probe failed at 0x334
> > bt0: Failed Status Reg Test - ff
> > bt_isa_probe: Probe failed at 0x230
> > bt0: Failed Status Reg Test - ff
> > bt_isa_probe: Probe failed at 0x234
> > bt0: Failed Status Reg Test - ff
> > bt_isa_probe: Probe failed at 0x130
> > bt0: Failed Status Reg Test - ff
> > bt_isa_probe: Probe failed at 0x134
> > aha0: status reg test failed fe
> > aha0: status reg test failed ff
> > ated 4 times
> > atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
> > atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
> > atkbd: the current kbd controller command byte 0065
> > atkbd: keyboard ID 0x41ab (2)
> > kbdc: RESET_KBD return code:00fa
> > kbdc: RESET_KBD status:00aa
> > kbd0 at atkbd0
> > kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000
> > psm0: current command byte:0065
> > kbdc: TEST_AUX_PORT status:0000
> > kbdc: RESET_AUX return code:00fa
> > kbdc: RESET_AUX status:00aa
> > kbdc: RESET_AUX ID:0000
> > psm: status 00 02 64
> > psm: status 00 00 64
> > psm: status 00 03 64
> > psm: status 00 03 64
> > psm: data 08 06 05
> > psm: data 08 01 00
> > psm: status 00 02 64
> > psm0: <PS/2 Mouse> irq 12 on atkbdc0
> > psm0: model IntelliMouse, device ID 3-00, 3 buttons
> > psm0: config:00000000, flags:00000000, packet size:4
> > psm0: syncmask:08, syncbits:08
> > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> > fb0: vga0, vga, type:VGA (5), flags:0x7007f
> > fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000
> > fb0: init mode:24, bios mode:3, current mode:24
> > fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k
> > VGA parameters upon power-up
> > 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
> > bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 
> > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
> > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
> > VGA parameters in BIOS for mode 24
> > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
> > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
> > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
> > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
> > EGA/VGA parameters to be used for mode 24
> > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
> > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
> > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
> > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
> > sc0: <System console> at flags 0x100 on isa0
> > sc0: VGA <16 virtual consoles, flags=0x300>
> > sc0: fb0, kbd0, terminal emulator: sc (syscons terminal)
> > pcic1: not probed (disabled)
> > sio0: irq maps: 0x41 0x51 0x41 0x41
> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> > sio0: type 16550A
> > sio1: irq maps: 0x41 0x49 0x41 0x41
> > sio1 at port 0x2f8-0x2ff irq 3 on isa0
> > sio1: type 16550A
> > sio2: not probed (disabled)
> > sio3: not probed (disabled)
> > ppc0: parallel port found at 0x378
> > ppc0: using extended I/O port range
> > ppc0: ECP SPP ECP+EPP SPP
> > ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
> > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
> > ppc0: FIFO with 16/16/8 bytes threshold
> > ppi0: <Parallel I/O> on ppbus0
> > lpt0: <Printer> on ppbus0
> > lpt0: Interrupt-driven port
> > plip0: <PLIP network interface> on ppbus0
> > bpf: lp0 attached
> > isa_probe_children: probing PnP devices
> > BIOS Geometries:
> > 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors
> > 0 accounted for
> > Device configuration finished.
> > bpf: sl0 attached
> > bpf: ppp0 attached
> > new masks: bio 68cc40, tty 63109a, net 67189a
> > bpf: lo0 attached
> > bpf: gif0 attached
> > bpf: gif1 attached
> > bpf: gif2 attached
> > bpf: gif3 attached
> > bpf: faith0 attached
> > ad0: <IBM-DTLA-307045/TX6OA60A> ATA-5 disk at ata0 as master
> > ad0: 43979MB (90069840 sectors), 89355 cyls, 16 heads, 63 S/T, 512 B/S
> > ad0: 16 secs/int, 32 depth queue, BIOSDMA
> > ad0: piomode=4 dmamode=2 udmamode=4 cblid=1
> > Creating DISK ad0
> > Creating DISK wd0
> > ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1
> > ata1-master: success setting up PIO4 mode on generic chip
> > acd0: <SAMSUNG CD-ROM SC-152C/CS02> CDROM drive at ata1 as master
> > acd0: read 171KB/s (8937KB/s), 128KB buffer, PIO4
> > acd0: Reads: CD-R, CD-RW, CD-DA stream, packet
> > acd0: Audio: play, 255 volume levels
> > acd0: Mechanism: ejectable tray
> > acd0: Medium: no/blank disc inside, unlocked
> > Mounting root from ufs:/dev/ad0s1a
> > ad0s1: type 0xa5, start 63, end = 41929649, size 41929587 : OK
> > start_init: trying /sbin/init
> > 
> > 
> > --
> > FreeBSD 2.2.8-RELEASE: up 6 days, 5:09
> > last reboot Thu Nov 2 10:55 (lightning strike)
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-hardware" in the body of the message
> 
> -- 
> Paul Saab
> Technical Yahoo
> paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org
> Do You .. uhh .. Yahoo!?
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hardware" in the body of the message
> 


Lanny Baron

Microsoft: "Where would you like to go today"
Linux: "Where would you like to go tomorrow"
FreeBSD: "Hey,when are you guys going to catch up"


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8 13:19:22 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from angryfist.fasttrackmonkey.com (angryfist.fasttrackmonkey.com [216.223.217.166])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1709237B479; Wed,  8 Nov 2000 13:19:20 -0800 (PST)
Received: by angryfist.fasttrackmonkey.com (Postfix, from userid 1001)
	id 6DF944EEF; Wed,  8 Nov 2000 16:22:28 -0500 (EST)
Date: Wed, 8 Nov 2000 16:22:27 -0500 (EST)
From: spork@fasttrackmonkey.com
To: Mike Smith <msmith@freebsd.org>
Cc: freebsd-hardware@freebsd.org
Subject: Re: Server-class mobo's 
In-Reply-To: <200011072319.eA7NJBF33525@mass.osd.bsdi.com>
Message-ID: <Pine.GSO.4.20.0011081620330.13973-100000@frothy.fasttrackmonkey.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 7 Nov 2000, Mike Smith wrote:

> Tyan are doing this on the S2500 and S2510 boards, which BSDi are 
> building into our current family of 1U and 2U server systems.
> 
> Note that most of these BIOS-serial designs are of the screen-scraper 
> variety, so you still need a video card.  Ugh.

Thanks for the info...  "screen-scraper"??  Does this basically mean I'm
SOL if I want to twiddle with the Raid card remotely?  If so, then I guess
it's back to the PC Weasel...

I also had a hard time finding any mention of the serial BIOS feature in
Tyan's docs.  I wonder how many other mobo makers have this feature and
don't mention it...

Thanks,

Charles
 
> -- 
> ... every activity meets with opposition, everyone who acts has his
> rivals and unfortunately opponents also.  But not because people want
> to be opponents, rather because the tasks and relationships force
> people to take different points of view.  [Dr. Fritz Todt]
>            V I C T O R Y   N O T   V E N G E A N C E
> 
> 
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8 13:24:40 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8B1B237B479; Wed,  8 Nov 2000 13:24:37 -0800 (PST)
Received: by arg1.demon.co.uk (Postfix, from userid 300)
	id 295F59B0F; Wed,  8 Nov 2000 21:24:36 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by arg1.demon.co.uk (Postfix) with ESMTP
	id 21B6B5D08; Wed,  8 Nov 2000 21:24:36 +0000 (GMT)
Date: Wed, 8 Nov 2000 21:24:36 +0000 (GMT)
From: Andrew Gordon <arg@arg1.demon.co.uk>
X-Sender: arg@server.arg.sj.co.uk
To: Mike Smith <msmith@freebsd.org>
Cc: spork@fasttrackmonkey.com, freebsd-hardware@freebsd.org
Subject: Re: Server-class mobo's 
In-Reply-To: <200011081900.eA8J0MF03063@mass.osd.bsdi.com>
Message-ID: <Pine.BSF.4.21.0011082113310.31290-100000@server.arg.sj.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


On Wed, 8 Nov 2000, Mike Smith wrote:

> > > > Anyone have any ideas on who besides Intel uses this Phoenix BIOS that
> > > > integrates a full serial console (from power on to OS boot)?
> ...
> > > Note that most of these BIOS-serial designs are of the screen-scraper 
> > > variety, so you still need a video card.  Ugh.
> > 
> > The version used in Intel's own 1U servers
> > (http://www.intel.com/network/products/isp1100.htm) is indeed a
> > screen-scraper, but you _don't_ need a video card installed: there's
> > no on-board video, but it still works.  I guess that it maps in some of
> > the main DRAM using the same technique as used for shadowing the BIOS ROM
> > - but since it works without problems, I haven't investigated too deeply.
> 
> As far as I can tell, it doesn't.  If you check the documentation you'll 
> find that the system BIOS is OK without a video card, but you're SOL if 
> you want to use the BIOS on an add-in card.  (Since there's only 1.5 
> slots, that makes things really awkward...)

The documentation says:

  Video is redirected by scanning and sending changes in text video
  memory. Thus, console redirection is unable to redirect video in
  graphics mode.

The only caveat is:

  Console redirection is a Real Mode BIOS extension, and does not
  operate outside of Real Mode. Console redirection does not work
  once an operating system or a driver such as EMM386 takes the
  processor into Protected Mode. If an application takes the processor
  in and out of Protected Mode, it should inhibit redirection before
  entering Protected Mode and restart it once back into Real Mode.

One of my units has an Adaptec 29160 in it (the second slot is empty - no
video card), and I have no problem accessing the Adaptec BIOS via the
serial redirection.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8 19: 8:56 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
	by hub.freebsd.org (Postfix) with ESMTP id 4EE2937B4C5
	for <freebsd-hardware@FreeBSD.org>; Wed,  8 Nov 2000 19:08:55 -0800 (PST)
Received: from DIMENSION ([64.164.135.50])
 by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with SMTP id <0G3Q00A03LWI1L@mta5.snfc21.pbi.net> for
 freebsd-hardware@FreeBSD.org; Wed,  8 Nov 2000 19:05:06 -0800 (PST)
Date: Wed, 08 Nov 2000 19:05:56 -0800
From: "William E. Blum" <wblum@pacbell.net>
Subject: Micron BIOS
To: freebsd-hardware@FreeBSD.org
Message-id: <LAEILMMDBDPFKEPLIMEFKEBJCAAA.wblum@pacbell.net>
MIME-version: 1.0
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Priority: 3 (Normal)
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I'm trying to install FreeBSD 4.1 on a Micron with a Phoenix BIOS dated
1994.  I'm getting an error at boot time: "Bad BIOS32 Service Directory!".
Is there a workaround?



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8 21: 9: 8 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from web10307.mail.yahoo.com (web10307.mail.yahoo.com [216.136.130.85])
	by hub.freebsd.org (Postfix) with SMTP id 27C3937B4C5
	for <freebsd-hardware@FreeBSD.ORG>; Wed,  8 Nov 2000 21:09:05 -0800 (PST)
Message-ID: <20001109050905.87034.qmail@web10307.mail.yahoo.com>
Received: from [128.165.7.6] by web10307.mail.yahoo.com; Thu, 09 Nov 2000 18:09:05 NZDT
Date: Thu, 9 Nov 2000 18:09:05 +1300 (NZDT)
From: =?iso-8859-1?q?Graham=20Guttocks?= <graham_guttocks@yahoo.co.nz>
Subject: query CD-ROM status from within a program?
To: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Greetings,

I'm looking for a way to manipulate a CD-ROM drive from within a shell
script (ksh, perl, python, whatever).  I need to be able to eject the
tray, and also query whether the tray contains a disc or is empty from
within the program.  The first is easily accomplished with a utility like
"eject", but how about the latter?  Is there an easy way to tell whether
a FreeBSD system's CD-ROM drive contains a disk or not?

Regards,
Graham

_____________________________________________________________________________
http://clubs.yahoo.com.au - Yahoo! Clubs
- Join a club or build your own!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Wed Nov  8 23:36:14 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from averroe.polito.it (averroe.polito.it [130.192.4.32])
	by hub.freebsd.org (Postfix) with SMTP id C276A37B479
	for <freebsd-hardware@freebsd.org>; Wed,  8 Nov 2000 23:36:03 -0800 (PST)
Received: (qmail 44207 invoked by uid 10003); 9 Nov 2000 07:35:56 -0000
Received: from demostene.polito.it (130.192.4.73)
  by averroe.polito.it with SMTP; 9 Nov 2000 07:35:56 -0000
Message-Id: <5.0.0.25.0.20001109083543.00a9a6a0@averroe.polito.it>
X-Sender: tealdi@averroe.polito.it
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Thu, 09 Nov 2000 08:35:55 +0100
To: freebsd-hardware@freebsd.org, freebsd-smp@freebsd.org
From: Paolo Tealdi <tealdi@sb.polito.it>
Subject: Compaq DL370 [long]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

As i already asked in the list, i'm trying to understand if FreeBSD support 
the hardware in subject.
I tried to install FreeBSD on a system at my vendor's home and i found some 
interesting (and funny) things.

The system was a
single / double processor 733 MHz
128 MB memory
standard COMPAQ SCSI controller (symbios)
standard COMPAQ ETHERNET controller

S.O. : FBSD 4.1 RELEASE

1) First, i tried to start booting directly from Fbsd CDROM.
The system seemed to start, system recognized the scsi controller, but 
when  checked the hard disk suddendly presented an error (seemed a parity 
error on SCSI, if i remember well )and the installation program aborted as 
it didn't find any disk.

2)consequently I loaded the COMPAQ SYSTEM INSTALLATION CDROM, I configured 
the system for an "other operating system" and i tried again to start with 
FreeBSD CDROM. This time all went OK. I installed the system, booted 
sometimes and all seemed well (also network controller was found).

3) Unfortunately the hardware the vender gave me was a single processor but 
i would like to buy a double processor system, so the vendor told me that 
he managed to receive one more and continue the test.And so we did.

4) Yesterday the vendor contacted me the processor was arrived and that i 
could go to do the final testing, and so i did.

5)The vendor told me that he didn't touched the original system (it is an 
NT guru and doesn't know ANYTHING about *nix ) and we installed the second 
processor. The system bootstrapped, all seemed to go well, FreeBSD seemed 
to recognized the second processor (the last thing i did the first time was 
to rebuild the kernel with SMP support, and i did it only decommenting the 
option SMP , option APIC and default for NPROCS ... copying GENERIC 
configuration) but when it tried to load the root partition again i found 
the original error (parity on SCSI bus).

6) This time i suggested that there was an hardware problem, so we tried to 
install NT4 .After one hour of installation (it's not so quick as FBSD) the 
NT4 server seemed to be installed OK, without any error ( :-(( ) .

7) So i reinstalled FBSD, after server setup installation with two 
processor and again all seemed to go OK. I recompiled the kernel (again 
decommenting only SMP options) and this time (for three consecutive time ) 
FBSD hung on boot after APIC check, one time messaging that it got an 
uninspected interrupt (43) (kernel config defaults are for 25 interrupts) 
and the others two without any message.

8) I stopped any kernel rebuilding, as i'm not so skilled with SMP 
installation.

After this (very long) story i'd like to ask :

a) All these things are normal for a double processor system ?
b) Must i continue to try changing parameters in kernel configurations ?
c) Can be an hardware problem ?
d) It's normal for COMPAQ hardware ?
e) There are significant change on 4.2 for SMP that can avoid this problems ?
f) Anybody has found similar SCSI and double processor problems with Compaq 
or other vendors hardware ?

I installed FBSD on a variety of servers ( mostly compatible) but never 
happened to me these things ... In any case i have never installed a double 
processor system.

Sorry for the long story, and for my not so well english. ...

Best regards, Paolo Tealdi



Ing. Paolo Tealdi         Library & News System Administrator
Politecnico Torino        Phone : +39-11-5646714 , FAX : +39-11-5646799
C.so D. degli Abruzzi, 24 - 10129 Torino - ITALY  Email: tealdi@sb.polito.it



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Nov  9  1:19: 3 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77])
	by hub.freebsd.org (Postfix) with ESMTP id F1A9A37B4CF
	for <freebsd-hardware@FreeBSD.org>; Thu,  9 Nov 2000 01:18:59 -0800 (PST)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA99Of900598;
	Thu, 9 Nov 2000 01:24:41 -0800 (PST)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200011090924.eA99Of900598@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "William E. Blum" <wblum@pacbell.net>
Cc: freebsd-hardware@FreeBSD.org
Subject: Re: Micron BIOS 
In-reply-to: Your message of "Wed, 08 Nov 2000 19:05:56 PST."
             <LAEILMMDBDPFKEPLIMEFKEBJCAAA.wblum@pacbell.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 09 Nov 2000 01:24:41 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> I'm trying to install FreeBSD 4.1 on a Micron with a Phoenix BIOS dated
> 1994.  I'm getting an error at boot time: "Bad BIOS32 Service Directory!".
> Is there a workaround?

This isn't a fatal error.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Nov  9  4:41:57 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id 0A95D37B479
	for <freebsd-hardware@freebsd.org>; Thu,  9 Nov 2000 04:41:54 -0800 (PST)
Received: from zippy.hexanet.fr (zippy.hexanet.fr [194.98.140.166])
	by ns1.hexanet.fr (8.9.3/8.9.3) with ESMTP id NAA54249
	for <freebsd-hardware@freebsd.org>; Thu, 9 Nov 2000 13:41:49 +0100 (CET)
	(envelope-from nighty@hexanet.fr)
Received: from zippy (localhost [127.0.0.1])
	by zippy.hexanet.fr (8.11.1/8.11.1) with ESMTP id eA9Cg1Y02739
	for <freebsd-hardware@freebsd.org>; Thu, 9 Nov 2000 13:42:01 +0100 (CET)
	(envelope-from nighty@zippy.hexanet.fr)
Message-Id: <200011091242.eA9Cg1Y02739@zippy.hexanet.fr>
Reply-To: chris@hexanet.fr
From: "Christophe Prevotaux" <chris@hexanet.fr>
X-Mailer: NMH 1.0.4 
To: freebsd-hardware@freebsd.org
Subject: Nsine PCI , USB etc.. drivers
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2736.973773721.1@zippy>
Date: Thu, 09 Nov 2000 13:42:01 +0100
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

http://www.nsine.com/

I would like to know if anyone is planning to devellop
drivers for NSINE's products , they offer support and 
I think some source code to help open source driver
devellopment

I would really like to use these hardware
and they already have a linux driver for it

unfortunately I am not a good enough programmer
to do this myself.





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Nov  9  4:55:45 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77])
	by hub.freebsd.org (Postfix) with ESMTP id 3769E37B479
	for <freebsd-hardware@freebsd.org>; Thu,  9 Nov 2000 04:55:42 -0800 (PST)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA9D1H901640;
	Thu, 9 Nov 2000 05:01:19 -0800 (PST)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200011091301.eA9D1H901640@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: chris@hexanet.fr
Cc: freebsd-hardware@freebsd.org, webmaster@nsine.com
Subject: Re: Nsine PCI , USB etc.. drivers 
In-reply-to: Your message of "Thu, 09 Nov 2000 13:42:01 +0100."
             <200011091242.eA9Cg1Y02739@zippy.hexanet.fr> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 09 Nov 2000 05:01:17 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> http://www.nsine.com/
> 
> I would like to know if anyone is planning to devellop
> drivers for NSINE's products , they offer support and 
> I think some source code to help open source driver
> devellopment

I have no idea, and I couldn't comment further without access to their 
website, which is impossible because it's flash-only. 

> I would really like to use these hardware
> and they already have a linux driver for it
> 
> unfortunately I am not a good enough programmer
> to do this myself.

If Nsine are interested in attracting the interest of the non-Windows 
developer community, they will need to start by producing a 
standards-compliant website, or possibly publish the relevant information 
in some other, less hostile format.

Should an Nsine representative wish to contact me to discuss these issues 
further, they are naturally encouraged to do so.

Regards,
Mike Smith
Principal Engineer
FreeBSD Test Labs
BSDi OSS

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Nov  9  5:35:17 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from srv13-poa.poa.terra.com.br (srv13-poa.poa.zaz.com.br [200.248.149.91])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5C9EA37B479; Thu,  9 Nov 2000 05:35:12 -0800 (PST)
Received: from srv7-poa.poa.terra.com.br (srv7-poa.poa.terra.com.br [200.248.149.15])
	by srv13-poa.poa.terra.com.br (8.9.3/8.9.3) with ESMTP id LAA13921;
	Thu, 9 Nov 2000 11:34:30 -0200
Received: from br.zoing.net (cm-net-C8B02AC8.poa.terra.com.br [200.176.42.200])
	by srv7-poa.poa.terra.com.br (8.9.3/8.9.3) with ESMTP id LAA15834;
	Thu, 9 Nov 2000 11:34:30 -0200
Message-ID: <XFMail.001109113434.floripa@zoing.net>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <200011091301.eA9D1H901640@mass.osd.bsdi.com>
Date: Thu, 09 Nov 2000 11:34:34 -0200 (EDT)
Organization: http://www.showZ.com.br
From: Antonio Carlos Venancio Junior <floripa@zoing.net>
To: Mike Smith <msmith@FreeBSD.ORG>
Subject: Re: Nsine PCI , USB etc.. drivers
Cc: webmaster@nsine.com, freebsd-hardware@FreeBSD.ORG,
	chris@hexanet.fr
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Mike,


        And that applies to CMI's onboard sound cards too?
        I have a lot of machines since 2.2.8 using this chip and without
support. ;/

On 09-Nov-00 Mike Smith wrote:
>> http://www.nsine.com/
>> 
>> I would like to know if anyone is planning to devellop
>> drivers for NSINE's products , they offer support and 
>> I think some source code to help open source driver
>> devellopment
> 
> I have no idea, and I couldn't comment further without access to their 
> website, which is impossible because it's flash-only. 
> 
>> I would really like to use these hardware
>> and they already have a linux driver for it
>> 
>> unfortunately I am not a good enough programmer
>> to do this myself.
> 
> If Nsine are interested in attracting the interest of the non-Windows 
> developer community, they will need to start by producing a 
> standards-compliant website, or possibly publish the relevant information 
> in some other, less hostile format.
> 
> Should an Nsine representative wish to contact me to discuss these issues 
> further, they are naturally encouraged to do so.
> 
> Regards,
> Mike Smith
> Principal Engineer
> FreeBSD Test Labs
> BSDi OSS
> 
> -- 
> ... every activity meets with opposition, everyone who acts has his
> rivals and unfortunately opponents also.  But not because people want
> to be opponents, rather because the tasks and relationships force
> people to take different points of view.  [Dr. Fritz Todt]
>            V I C T O R Y   N O T   V E N G E A N C E
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hardware" in the body of the message


Cya


Antonio
[ floripa@zoing.net | antonio@inf.ufsc.br ]
[ http://floripa.zoing.net | http://www.showZ.com.br ]
[ ICQ# 9253680 | Floripa | MySQL | PHP | FreeBSD - The Power to Serve ]
---
When more and more people are thrown out of work, unemployment
results.
		-- Calvin Coolidge



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Nov  9  5:42:34 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77])
	by hub.freebsd.org (Postfix) with ESMTP id BAE8237B479
	for <freebsd-hardware@FreeBSD.ORG>; Thu,  9 Nov 2000 05:42:31 -0800 (PST)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA9Dm2901814;
	Thu, 9 Nov 2000 05:48:02 -0800 (PST)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200011091348.eA9Dm2901814@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Antonio Carlos Venancio Junior <floripa@zoing.net>
Cc: freebsd-hardware@FreeBSD.ORG, chris@hexanet.fr
Subject: Re: Nsine PCI , USB etc.. drivers 
In-reply-to: Your message of "Thu, 09 Nov 2000 11:34:34 -0200."
             <XFMail.001109113434.floripa@zoing.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 09 Nov 2000 05:48:02 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> Mike,
> 
> 
>         And that applies to CMI's onboard sound cards too?
>         I have a lot of machines since 2.2.8 using this chip and without
> support. ;/

I have no idea; if we're talking about sound, then you'll want to talk to 
Cameron Grant (cg@freebsd.org).

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Nov  9 11:29:47 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5758437B4C5; Thu,  9 Nov 2000 11:29:38 -0800 (PST)
Received: (from ken@localhost)
	by panzer.kdm.org (8.9.3/8.9.1) id MAA32118;
	Thu, 9 Nov 2000 12:26:26 -0700 (MST)
	(envelope-from ken)
Date: Thu, 9 Nov 2000 12:26:26 -0700
From: "Kenneth D. Merry" <ken@kdm.org>
To: Graham Guttocks <graham_guttocks@yahoo.co.nz>
Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
Subject: Re: query CD-ROM status from within a program?
Message-ID: <20001109122625.A32056@panzer.kdm.org>
References: <20001109050905.87034.qmail@web10307.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20001109050905.87034.qmail@web10307.mail.yahoo.com>; from graham_guttocks@yahoo.co.nz on Thu, Nov 09, 2000 at 06:09:05PM +1300
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Thu, Nov 09, 2000 at 18:09:05 +1300, Graham Guttocks wrote:
> Greetings,
> 
> I'm looking for a way to manipulate a CD-ROM drive from within a shell
> script (ksh, perl, python, whatever).  I need to be able to eject the
> tray, and also query whether the tray contains a disc or is empty from
> within the program.  The first is easily accomplished with a utility like
> "eject", but how about the latter?  Is there an easy way to tell whether
> a FreeBSD system's CD-ROM drive contains a disk or not?

You can eject the CD with camcontrol:

camcontrol eject cd0

Or with cdcontrol:

cdcontrol -f /dev/cd0c eject

You can determine whether the drive is ready with camcontrol:

camcontrol tur cd0 -v -C 2 -E

Or with cdcontrol:

cdcontrol -f /dev/cd0c status

It might be easier to use camcontrol in a script, since it will exit with
a non-zero status if the drive isn't ready.

Ken
-- 
Kenneth Merry
ken@kdm.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Nov  9 13: 5: 1 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from front2.grolier.fr (front2.grolier.fr [194.158.96.52])
	by hub.freebsd.org (Postfix) with ESMTP
	id 48A3B37B479; Thu,  9 Nov 2000 13:04:52 -0800 (PST)
Received: from nas15-167.vlt.club-internet.fr (nas15-167.vlt.club-internet.fr [195.36.165.167])
	by front2.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA23855;
	Thu, 9 Nov 2000 22:04:30 +0100 (MET)
Date: Thu, 9 Nov 2000 21:04:56 +0100 (CET)
From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr>
X-Sender: groudier@linux.local
To: Paolo Tealdi <tealdi@sb.polito.it>
Cc: freebsd-hardware@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG
Subject: Re: Compaq DL370 [long]
In-Reply-To: <5.0.0.25.0.20001109083543.00a9a6a0@averroe.polito.it>
Message-ID: <Pine.LNX.4.10.10011092049290.1381-100000@linux.local>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org



I don't know about SMP, but could you please let me know what driver is
attaching your SYMBIOS controller. Could be either `sym' or `ncr', but
they differ regarding parity checking handling.

OTOH, are you sure it is a SCSI parity error that is reported. When using
the `sym' driver, PCI parity errors are also reported.

Now, if this PCI|SCSI parity error is a real parity error, you should,
IMHO, check if NT would not be working for the reason it wouldn't care
about SCSI|PCI parity checking being _actually_ enabled. It may be
unbelievable that COMPAQ is selling hardware that fails parity, but this
should be checked, in my opinion.

Btw, the latest nasty parity problem I have had to work around in `sym'
driver was a PCI parity problem that occurs on some systems using SYMBIOS
PCI-SCSI chips. Latest `sym' driver in -RELENG4 and -current does detect
that, WARN USER ABOUT, and disable PCI parity checking by the master.

  G=E9rard.

On Thu, 9 Nov 2000, Paolo Tealdi wrote:

> As i already asked in the list, i'm trying to understand if FreeBSD suppo=
rt=20
> the hardware in subject.
> I tried to install FreeBSD on a system at my vendor's home and i found so=
me=20
> interesting (and funny) things.
>=20
> The system was a
> single / double processor 733 MHz
> 128 MB memory
> standard COMPAQ SCSI controller (symbios)
> standard COMPAQ ETHERNET controller
>=20
> S.O. : FBSD 4.1 RELEASE
>=20
> 1) First, i tried to start booting directly from Fbsd CDROM.
> The system seemed to start, system recognized the scsi controller, but=20
> when  checked the hard disk suddendly presented an error (seemed a parity=
=20
> error on SCSI, if i remember well )and the installation program aborted a=
s=20
> it didn't find any disk.
>=20
> 2)consequently I loaded the COMPAQ SYSTEM INSTALLATION CDROM, I configure=
d=20
> the system for an "other operating system" and i tried again to start wit=
h=20
> FreeBSD CDROM. This time all went OK. I installed the system, booted=20
> sometimes and all seemed well (also network controller was found).
>=20
> 3) Unfortunately the hardware the vender gave me was a single processor b=
ut=20
> i would like to buy a double processor system, so the vendor told me that=
=20
> he managed to receive one more and continue the test.And so we did.
>=20
> 4) Yesterday the vendor contacted me the processor was arrived and that i=
=20
> could go to do the final testing, and so i did.
>=20
> 5)The vendor told me that he didn't touched the original system (it is an=
=20
> NT guru and doesn't know ANYTHING about *nix ) and we installed the secon=
d=20
> processor. The system bootstrapped, all seemed to go well, FreeBSD seemed=
=20
> to recognized the second processor (the last thing i did the first time w=
as=20
> to rebuild the kernel with SMP support, and i did it only decommenting th=
e=20
> option SMP , option APIC and default for NPROCS ... copying GENERIC=20
> configuration) but when it tried to load the root partition again i found=
=20
> the original error (parity on SCSI bus).
>=20
> 6) This time i suggested that there was an hardware problem, so we tried =
to=20
> install NT4 .After one hour of installation (it's not so quick as FBSD) t=
he=20
> NT4 server seemed to be installed OK, without any error ( :-(( ) .
>=20
> 7) So i reinstalled FBSD, after server setup installation with two=20
> processor and again all seemed to go OK. I recompiled the kernel (again=
=20
> decommenting only SMP options) and this time (for three consecutive time =
)=20
> FBSD hung on boot after APIC check, one time messaging that it got an=20
> uninspected interrupt (43) (kernel config defaults are for 25 interrupts)=
=20
> and the others two without any message.
>=20
> 8) I stopped any kernel rebuilding, as i'm not so skilled with SMP=20
> installation.
>=20
> After this (very long) story i'd like to ask :
>=20
> a) All these things are normal for a double processor system ?
> b) Must i continue to try changing parameters in kernel configurations ?
> c) Can be an hardware problem ?
> d) It's normal for COMPAQ hardware ?
> e) There are significant change on 4.2 for SMP that can avoid this proble=
ms ?
> f) Anybody has found similar SCSI and double processor problems with Comp=
aq=20
> or other vendors hardware ?
>=20
> I installed FBSD on a variety of servers ( mostly compatible) but never=
=20
> happened to me these things ... In any case i have never installed a doub=
le=20
> processor system.
>=20
> Sorry for the long story, and for my not so well english. ...
>=20
> Best regards, Paolo Tealdi
>=20
>=20
>=20
> Ing. Paolo Tealdi         Library & News System Administrator
> Politecnico Torino        Phone : +39-11-5646714 , FAX : +39-11-5646799
> C.so D. degli Abruzzi, 24 - 10129 Torino - ITALY  Email: tealdi@sb.polito=
=2Eit
>=20
>=20
>=20
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-smp" in the body of the message



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Nov  9 14:44:22 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from juice.shallow.net (node16229.a2000.nl [24.132.98.41])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2774C37B479; Thu,  9 Nov 2000 14:44:07 -0800 (PST)
Received: from localhost (joshua@localhost)
	by juice.shallow.net (8.9.3/8.9.3) with ESMTP id XAA74829;
	Thu, 9 Nov 2000 23:43:35 +0100 (CET)
	(envelope-from joshua@roughtrade.net)
Date: Thu, 9 Nov 2000 23:43:34 +0100 (CET)
From: Joshua Goodall <joshua@roughtrade.net>
To: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr>
Cc: adrian@freebsd.org, Paolo Tealdi <tealdi@sb.polito.it>,
	freebsd-hardware@freebsd.org, freebsd-smp@freebsd.org
Subject: Re: Compaq DL370 [long]
In-Reply-To: <Pine.LNX.4.10.10011092049290.1381-100000@linux.local>
Message-ID: <Pine.BSF.4.21.0011092341150.64333-100000@juice.shallow.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8BIT
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


We had some trouble with frisbee on DL380's which Adrian Chadd sorted out
for us... although not, I believe, working alone, so I'll let him reply to
this <g>.

J

On Thu, 9 Nov 2000, [ISO-8859-1] Gérard Roudier wrote:

> 
> 
> I don't know about SMP, but could you please let me know what driver is
> attaching your SYMBIOS controller. Could be either `sym' or `ncr', but
> they differ regarding parity checking handling.
> 
> OTOH, are you sure it is a SCSI parity error that is reported. When using
> the `sym' driver, PCI parity errors are also reported.
> 
> Now, if this PCI|SCSI parity error is a real parity error, you should,
> IMHO, check if NT would not be working for the reason it wouldn't care
> about SCSI|PCI parity checking being _actually_ enabled. It may be
> unbelievable that COMPAQ is selling hardware that fails parity, but this
> should be checked, in my opinion.
> 
> Btw, the latest nasty parity problem I have had to work around in `sym'
> driver was a PCI parity problem that occurs on some systems using SYMBIOS
> PCI-SCSI chips. Latest `sym' driver in -RELENG4 and -current does detect
> that, WARN USER ABOUT, and disable PCI parity checking by the master.
> 
>   Gérard.
> 
> On Thu, 9 Nov 2000, Paolo Tealdi wrote:
> 
> > As i already asked in the list, i'm trying to understand if FreeBSD support 
> > the hardware in subject.
> > I tried to install FreeBSD on a system at my vendor's home and i found some 
> > interesting (and funny) things.
> > 
> > The system was a
> > single / double processor 733 MHz
> > 128 MB memory
> > standard COMPAQ SCSI controller (symbios)
> > standard COMPAQ ETHERNET controller
> > 
> > S.O. : FBSD 4.1 RELEASE
> > 
> > 1) First, i tried to start booting directly from Fbsd CDROM.
> > The system seemed to start, system recognized the scsi controller, but 
> > when  checked the hard disk suddendly presented an error (seemed a parity 
> > error on SCSI, if i remember well )and the installation program aborted as 
> > it didn't find any disk.
> > 
> > 2)consequently I loaded the COMPAQ SYSTEM INSTALLATION CDROM, I configured 
> > the system for an "other operating system" and i tried again to start with 
> > FreeBSD CDROM. This time all went OK. I installed the system, booted 
> > sometimes and all seemed well (also network controller was found).
> > 
> > 3) Unfortunately the hardware the vender gave me was a single processor but 
> > i would like to buy a double processor system, so the vendor told me that 
> > he managed to receive one more and continue the test.And so we did.
> > 
> > 4) Yesterday the vendor contacted me the processor was arrived and that i 
> > could go to do the final testing, and so i did.
> > 
> > 5)The vendor told me that he didn't touched the original system (it is an 
> > NT guru and doesn't know ANYTHING about *nix ) and we installed the second 
> > processor. The system bootstrapped, all seemed to go well, FreeBSD seemed 
> > to recognized the second processor (the last thing i did the first time was 
> > to rebuild the kernel with SMP support, and i did it only decommenting the 
> > option SMP , option APIC and default for NPROCS ... copying GENERIC 
> > configuration) but when it tried to load the root partition again i found 
> > the original error (parity on SCSI bus).
> > 
> > 6) This time i suggested that there was an hardware problem, so we tried to 
> > install NT4 .After one hour of installation (it's not so quick as FBSD) the 
> > NT4 server seemed to be installed OK, without any error ( :-(( ) .
> > 
> > 7) So i reinstalled FBSD, after server setup installation with two 
> > processor and again all seemed to go OK. I recompiled the kernel (again 
> > decommenting only SMP options) and this time (for three consecutive time ) 
> > FBSD hung on boot after APIC check, one time messaging that it got an 
> > uninspected interrupt (43) (kernel config defaults are for 25 interrupts) 
> > and the others two without any message.
> > 
> > 8) I stopped any kernel rebuilding, as i'm not so skilled with SMP 
> > installation.
> > 
> > After this (very long) story i'd like to ask :
> > 
> > a) All these things are normal for a double processor system ?
> > b) Must i continue to try changing parameters in kernel configurations ?
> > c) Can be an hardware problem ?
> > d) It's normal for COMPAQ hardware ?
> > e) There are significant change on 4.2 for SMP that can avoid this problems ?
> > f) Anybody has found similar SCSI and double processor problems with Compaq 
> > or other vendors hardware ?
> > 
> > I installed FBSD on a variety of servers ( mostly compatible) but never 
> > happened to me these things ... In any case i have never installed a double 
> > processor system.
> > 
> > Sorry for the long story, and for my not so well english. ...
> > 
> > Best regards, Paolo Tealdi
> > 
> > 
> > 
> > Ing. Paolo Tealdi         Library & News System Administrator
> > Politecnico Torino        Phone : +39-11-5646714 , FAX : +39-11-5646799
> > C.so D. degli Abruzzi, 24 - 10129 Torino - ITALY  Email: tealdi@sb.polito.it
> > 
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-smp" in the body of the message
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hardware" in the body of the message
> 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Nov  9 16:10:10 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from equity.freerealtime.com (rampagemedia.com [209.67.31.44])
	by hub.freebsd.org (Postfix) with ESMTP id 0461737B479
	for <freebsd-hardware@freebsd.org>; Thu,  9 Nov 2000 16:10:07 -0800 (PST)
Received: from nik (sc-24-130-153-133.socal.rr.com [24.130.153.133])
	by equity.freerealtime.com (8.9.3+Sun/8.9.3) with SMTP id TAA24978
	for <freebsd-hardware@freebsd.org>; Thu, 9 Nov 2000 19:10:10 -0500 (EST)
From: "Nikolaus Spence" <nspence@corp.freerealtime.com>
To: <freebsd-hardware@freebsd.org>
Subject: RE: Server-class mobo's 
Date: Thu, 9 Nov 2000 16:08:41 -0800
Message-ID: <NEBBIBNDCLAAECJHLLFOAEMOCDAA.nspence@corp.freerealtime.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-reply-to: <200011072319.eA7NJBF33525@mass.osd.bsdi.com>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Most server grade motherboards have VGA BIOS on board anyways so you don't
lose any space.

Nikolaus

-----Original Message-----
From: owner-freebsd-hardware@FreeBSD.ORG
[mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf Of Mike Smith
Sent: Tuesday, November 07, 2000 3:19 PM
To: spork@fasttrackmonkey.com
Cc: freebsd-hardware@FreeBSD.ORG
Subject: Re: Server-class mobo's


> Hi,
>
> Anyone have any ideas on who besides Intel uses this Phoenix BIOS that
> integrates a full serial console (from power on to OS boot)?
>
> http://www.phoenix.com/platform/serverbios.html
>
> The only feature that intrigues me is the serial console; very useful for
> colo'd servers.  It allows you into the normal BIOS screens as well as any
> SCSI controller/RAID controller setups.
>
> Intel is a bit pricey for the current 133MHz bus boards...

Tyan are doing this on the S2500 and S2510 boards, which BSDi are
building into our current family of 1U and 2U server systems.

Note that most of these BIOS-serial designs are of the screen-scraper
variety, so you still need a video card.  Ugh.

--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Thu Nov  9 17:57:36 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from mail0.bna.bellsouth.net (mail0.bna.bellsouth.net [205.152.150.12])
	by hub.freebsd.org (Postfix) with ESMTP id 15F6B37B479
	for <hardware@freebsd.org>; Thu,  9 Nov 2000 17:57:34 -0800 (PST)
Received: from bellsouth.net (adsl-63-164-15.bna.bellsouth.net [208.63.164.15])
	by mail0.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id UAA05426
	for <hardware@freebsd.org>; Thu, 9 Nov 2000 20:57:33 -0500 (EST)
Message-ID: <3A0B5877.FBAA3DA8@bellsouth.net>
Date: Thu, 09 Nov 2000 20:07:52 -0600
From: Drew Sanford <lauasanf@bellsouth.net>
X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: hardware@freebsd.org
Subject: Some MB questions
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Has anyone had any experience running FreeBSD on an Asus A7V revision
1.02? Specifically, do the UDMA 100 controlers work properly with
-STABLE? This board is going to be my next platform regardless of the
answer, I'm just curious about the status of it's support.

-- 
Drew Sanford
lauasanf@bellsouth.net or drew@planetwe.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Fri Nov 10  9: 7:29 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from roaming.cacheboy.net (roaming.cacheboy.net [203.56.168.69])
	by hub.freebsd.org (Postfix) with ESMTP
	id 52D8637B4C5; Fri, 10 Nov 2000 09:07:25 -0800 (PST)
Received: (from adrian@localhost)
	by roaming.cacheboy.net (8.11.0/8.11.0) id eAAH74U30105;
	Fri, 10 Nov 2000 18:07:04 +0100 (CET)
	(envelope-from adrian)
Date: Fri, 10 Nov 2000 18:07:04 +0100
From: Adrian Chadd <adrian@freebsd.org>
To: Joshua Goodall <joshua@roughtrade.net>
Cc: =?iso-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr>,
	Paolo Tealdi <tealdi@sb.polito.it>, freebsd-hardware@freebsd.org,
	freebsd-smp@freebsd.org
Subject: Re: Compaq DL370 [long]
Message-ID: <20001110180703.A30058@roaming.cacheboy.net>
References: <Pine.LNX.4.10.10011092049290.1381-100000@linux.local> <Pine.BSF.4.21.0011092341150.64333-100000@juice.shallow.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.4i
In-Reply-To: <Pine.BSF.4.21.0011092341150.64333-100000@juice.shallow.net>; from joshua@roughtrade.net on Thu, Nov 09, 2000 at 11:43:34PM +0100
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Thu, Nov 09, 2000, Joshua Goodall wrote:
> 
> We had some trouble with frisbee on DL380's which Adrian Chadd sorted out
> for us... although not, I believe, working alone, so I'll let him reply to
> this <g>.
> 
> J

I suggest you try a single CPU in the DL380. I installed 4.2-RC1 on a
DL380 (euro, I believe the euro and US versions are different!) without
any trouble. It has an "ida" raid controller, not a straight symbios card.

I haven't tried it in SMP yet, but I've heard bad things about SMP on the
DL series (and the lack of extra CPU/rectifier might prevent me trying :)

I'll email you a dmesg on Monday if you'd like.


(thanks for dobbing me in josh :)

adrian

-- 
Adrian Chadd			"Programming is like sex:
<adrian@freebsd.org>		   One mistake and you have to support for
				    a lifetime." -- rec.humor.funny



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Fri Nov 10 12:16:12 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11])
	by hub.freebsd.org (Postfix) with ESMTP id EFF2A37B479
	for <hardware@freebsd.org>; Fri, 10 Nov 2000 12:16:06 -0800 (PST)
Received: (from jin@localhost)
	by portnoy.lbl.gov (8.11.1/8.11.1) id eAAKG6k21569
	for hardware@freebsd.org; Fri, 10 Nov 2000 12:16:06 -0800 (PST)
Date: Fri, 10 Nov 2000 12:16:06 -0800 (PST)
From: Jin Guojun (DSD staff) <jin@george.lbl.gov>
Message-Id: <200011102016.eAAKG6k21569@portnoy.lbl.gov>
To: hardware@freebsd.org
Subject: motherboard with 32-bit/66MHz PC
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I am looking for a motherboard that has a PCI bus better than 32-bit/33MHz.
It looks like there is no 64-bit PCI bus for non server based motherboard.
So, does any one know any MB maker makes 32-bit/66MHz PCI motherboard?

Thanks,

	-Jin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Fri Nov 10 15:26:28 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169])
	by hub.freebsd.org (Postfix) with ESMTP id 286AD37B479
	for <hardware@FreeBSD.ORG>; Fri, 10 Nov 2000 15:26:26 -0800 (PST)
Received: (from ken@localhost)
	by panzer.kdm.org (8.9.3/8.9.1) id QAA42779;
	Fri, 10 Nov 2000 16:26:23 -0700 (MST)
	(envelope-from ken)
Date: Fri, 10 Nov 2000 16:26:23 -0700
From: "Kenneth D. Merry" <ken@kdm.org>
To: Jin Guojun <jin@george.lbl.gov>
Cc: hardware@FreeBSD.ORG
Subject: Re: motherboard with 32-bit/66MHz PC
Message-ID: <20001110162622.A42746@panzer.kdm.org>
References: <200011102016.eAAKG6k21569@portnoy.lbl.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <200011102016.eAAKG6k21569@portnoy.lbl.gov>; from jin@george.lbl.gov on Fri, Nov 10, 2000 at 12:16:06PM -0800
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Fri, Nov 10, 2000 at 12:16:06 -0800, Jin Guojun wrote:
> I am looking for a motherboard that has a PCI bus better than 32-bit/33MHz.
> It looks like there is no 64-bit PCI bus for non server based motherboard.
> So, does any one know any MB maker makes 32-bit/66MHz PCI motherboard?

Supermicro (www.supermicro.com) has some boards that might do the trick.

I'm not sure why you don't want a server board.  In any case, the
Supermicro 370DL3 or the Supermicro 370DE6 might do the trick.  I don't
think they're shipping the 370DE6 yet, but I think I've seen 370DL3
around.

Either board would do for a high end workstation, although the 370DE6 might
be better since it has an AGP slot.

I haven't used either one, so I can't comment on how they work with
FreeBSD, etc.

Ken
-- 
Kenneth Merry
ken@kdm.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message


From owner-freebsd-hardware  Fri Nov 10 16:15: 8 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11])
	by hub.freebsd.org (Postfix) with ESMTP id AD64F37B479
	for <hardware@FreeBSD.ORG>; Fri, 10 Nov 2000 16:15:05 -0800 (PST)
Received: (from jin@localhost)
	by portnoy.lbl.gov (8.11.1/8.11.1) id eAB0F5306677;
	Fri, 10 Nov 2000 16:15:05 -0800 (PST)
Date: Fri, 10 Nov 2000 16:15:05 -0800 (PST)
From: Jin Guojun (DSD staff) <jin@george.lbl.gov>
Message-Id: <200011110015.eAB0F5306677@portnoy.lbl.gov>
To: ken@kdm.org
Subject: Re: motherboard with 32-bit/66MHz PC
Cc: hardware@FreeBSD.ORG
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Kenneth Merry <ken@kdm.org> wrote:
> > I am looking for a motherboard that has a PCI bus better than 32-bit/33MHz.
> > It looks like there is no 64-bit PCI bus for non server based motherboard.
> > So, does any one know any MB maker makes 32-bit/66MHz PCI motherboard?
> 
> Supermicro (www.supermicro.com) has some boards that might do the trick.
> 
> I'm not sure why you don't want a server board.  In any case, the
> Supermicro 370DL3 or the Supermicro 370DE6 might do the trick.  I don't
> think they're shipping the 370DE6 yet, but I think I've seen 370DL3
> around.

Price, and I do not need 64-bit/66MHz bandwidth. The 370DLE and 370DLR seem
have a price in between, so I will look into it.

> Either board would do for a high end workstation, although the 370DE6 might
> be better since it has an AGP slot.
> 
> I haven't used either one, so I can't comment on how they work with
> FreeBSD, etc.

If I can get a better price on these boards, I will order them, do some test,
and post the result to the list.

	-Jin



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message