From owner-freebsd-hardware@FreeBSD.ORG  Thu Jan  1 01:30:34 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4C2A016A4CE
	for <freebsd-hardware@freebsd.org>;
	Thu,  1 Jan 2004 01:30:34 -0800 (PST)
Received: from s42.q.p80.net (s46.q.p80.net [217.75.96.46])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A271E43D53
	for <freebsd-hardware@freebsd.org>;
	Thu,  1 Jan 2004 01:30:32 -0800 (PST)
	(envelope-from magnus.benngard@port80.se)
Received: from [81.26.235.3] ([81.26.235.3])
	by s42.q.p80.net (8.12.9/8.11.0) with ESMTP id i019UU1M024693
	for <freebsd-hardware@freebsd.org>; Thu, 1 Jan 2004 10:30:30 +0100
From: Magnus Benngard <magnus.benngard@port80.se>
To: freebsd-hardware@freebsd.org
Content-Type: text/plain
Message-Id: <1072949422.3304.18.camel@mabe.port80.se>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Thu, 01 Jan 2004 10:30:22 +0100
Content-Transfer-Encoding: 7bit
Subject: Wildcard TE410P
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jan 2004 09:30:34 -0000

Hi!

Does anyone knows if there ara any efforts in adding
Wildcard TE410P support for FreeBSD?

/Magnus

From owner-freebsd-hardware@FreeBSD.ORG  Thu Jan  1 02:04:13 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 06CA416A4CE
	for <freebsd-hardware@freebsd.org>;
	Thu,  1 Jan 2004 02:04:13 -0800 (PST)
Received: from ntx.netvision.net.il (ananas1.netvision.net.il
	[199.203.100.202])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9839043D5E
	for <freebsd-hardware@freebsd.org>;
	Thu,  1 Jan 2004 02:04:10 -0800 (PST)
	(envelope-from cypher@netvision.net.il)
Received: from Internal Mail-Server by ananas1 with SMTP;
	1 Jan 2004 12:03:36 +0200
Received: from ntx2.forest.netvision.net.il ([172.20.30.33]) by
	ntx1.forest.netvision.net.il with Microsoft SMTPSVC(5.0.2195.6713);
	Thu, 1 Jan 2004 12:02:03 +0200
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 1 Jan 2004 12:02:03 +0200
Message-ID: <560FC34DB0095B459060688A7818E04F037539@ntx2.forest.netvision.net.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: SCSI backup tape problem
thread-index: AcPQTpNQUchQnp6lSdGmkmLGlrHQlA==
From: "Denis Prezhevalsky" <cypher@netvision.net.il>
To: <freebsd-hardware@freebsd.org>
X-OriginalArrivalTime: 01 Jan 2004 10:02:03.0621 (UTC)
	FILETIME=[4E4D2150:01C3D04E]
Subject: Re: SCSI backup tape problem
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jan 2004 10:04:13 -0000

> Hello,
>
> I recently installed FreeBSD 5.1-RELEASE on HP DL380 G3.
> The problem is that that FreeBSD not probing/recognizing my external =
Compaq AIT 35 SCSI tape
> connected to the SCSI port located on the back of the server (built-in =
SCSI LVD).=20
>
> # RAID & SCSI
> device          ciss           =20
> device          scbus          =20
> device          ch             =20
> device          da             =20
> device          pass          =20
> device          ses            =20
> device          sa             =20
>=20

> I don't see where your LVD controller is probed/
>  recognised? Or is that part of the Compaq Raid card?

This is a part of Compaq Smart Array 5i [ciss].=20
mail kernel: ciss0: <Compaq Smart Array 5i> port 0x3000-0x30ff mem =
0xf7cf0000-0xf7cf3fff,0xf7dc0000-0xf7dfffff irq 5 at device 3.0 on pci1


	Denis Prezhevalsky
	Colocation System Department,
	NetVision Ltd.=20
	=
_________________________________________________________________________=
_
	cypher@netvision.net.il  Tel: 04-8560550 | Fax: 972-3-5201923 | =
www.netvision.net.il



From owner-freebsd-hardware@FreeBSD.ORG  Thu Jan  1 02:17:58 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3531616A4CF
	for <freebsd-hardware@freebsd.org>;
	Thu,  1 Jan 2004 02:17:58 -0800 (PST)
Received: from ns1.dns-server.nu (www1.networksab.com [62.181.89.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F0A7B43D5A
	for <freebsd-hardware@freebsd.org>;
	Thu,  1 Jan 2004 02:17:55 -0800 (PST)
	(envelope-from sm7wqo@sk7dd.com)
Received: from wqomain [82.212.64.233] by ns1.dns-server.nu
  (SMTPD32-6.05) id A46B36B0016; Thu, 01 Jan 2004 11:20:27 +0100
Message-Id: <4.1.20040101111818.0184ad40@pop.networksab.com>
X-Sender: sm7wqo@sk7dd.com@pop.networksab.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 01 Jan 2004 11:18:24 +0100
To: freebsd-hardware@freebsd.org
From: =?iso-8859-1?Q?Bj=F6rn?= =?iso-8859-1?Q?_P=E5lsson?= <sm7wqo@sk7dd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: CompactFlash
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jan 2004 10:17:58 -0000

HI,
I need a solution to read and write CompactFlash on my 4.9 BSD. I am not a
fan of USB but I have it.

Any suggestions what to buy?

// B 

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 02:00:31 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id D550F16A4CF; Fri,  2 Jan 2004 02:00:31 -0800 (PST)
Received: from server.vk2pj.dyndns.org
	(c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id AA67743D41; Fri,  2 Jan 2004 02:00:29 -0800 (PST)
	(envelope-from peterjeremy@optushome.com.au)
Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org
	[127.0.0.1])i02A0S7B000893;	Fri, 2 Jan 2004 21:00:28 +1100 (EST)
	(envelope-from peter@server.vk2pj.dyndns.org)
Received: (from peter@localhost)
	by server.vk2pj.dyndns.org (8.12.10/8.12.10/Submit) id i02A0Sgo000892;
	Fri, 2 Jan 2004 21:00:28 +1100 (EST)
	(envelope-from peter)
Date: Fri, 2 Jan 2004 21:00:28 +1100
From: Peter Jeremy <peterjeremy@optushome.com.au>
To: Marc Fonvieille <blackend@freebsd.org>
Message-ID: <20040102100028.GA868@server.vk2pj.dyndns.org>
References: <20031230210742.GA50195@cirb503493.alcatel.com.au>
	<20031230221025.B93424@abigail.blackend.org>
	<20031230224010.GD84164@server.vk2pj.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031230221025.B93424@abigail.blackend.org>
User-Agent: Mutt/1.4.1i
cc: freebsd-hardware@freebsd.org
Subject: Re: Problem writing VCD with burncd
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 10:00:31 -0000

On Tue, Dec 30, 2003 at 10:10:25PM +0100, Marc Fonvieille wrote:
>To burn VCD you should use cdrdao, it runs fine.
>You will find an example in this article:
>http://bsdnews.org/01/vcd.php

Once I added atapicam, cdrdao works.  Thanks for that.

Of course, it still leaves the question as to why I can't use the
(documented) vcd burning facility in burncd via ATAPI.

Peter

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 08:26:22 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 698A416A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 08:26:22 -0800 (PST)
Received: from moe.ilimit.es (38.Red-213-96-13.pooles.rima-tde.net
	[213.96.13.38])	by mx1.FreeBSD.org (Postfix) with ESMTP id A3E9843D48
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 08:26:18 -0800 (PST)
	(envelope-from d.ortiz@in.ilimit.es)
Received: from dani.ilimit.lan ([192.168.1.57] helo=in.ilimit.es)
	by moe.ilimit.es with smtp (Exim 3.35 #1 (Debian))
	id 1AcS7i-0004sw-00
	for <freebsd-hardware@freebsd.org>; Fri, 02 Jan 2004 17:26:06 +0100
Received: by in.ilimit.es (sSMTP sendmail emulation);
	Fri,  2 Jan 2004 17:26:14 +0100
Date: Fri, 2 Jan 2004 12:41:56 +0100
From: Daniel Ortiz <d.ortiz@in.ilimit.es>
To: freebsd-hardware@freebsd.org
Message-ID: <20040102114156.GB7190@in.ilimit.es>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="E39vaYmALEf/7YXx"
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Resent-From: Daniel Ortiz <d.ortiz@in.ilimit.es>
Resent-Date: Fri, 2 Jan 2004 17:26:14 +0100
Resent-To: freebsd-hardware@freebsd.org
Resent-Message-Id: <E1AcS7i-0004sw-00@moe.ilimit.es>
X-ILIMIT-MailScanner-Information: ILIMIT Comunicacions
X-ILIMIT-MailScanner: Found to be clean
Subject: atacontrol/udma
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 16:26:22 -0000


--E39vaYmALEf/7YXx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi ppl and happy new year,

(Sorry for my poor english, it isn't my native language)

I have some questions about a sata controller.

I've a 'tyan i875p (s5102)' motherboard (with SATA 150), with a FreeBSD
4.9-STABLE installed, the kernel detects the hardware fine.
The cable it's a fully working serial ata cable.

atapci0: <Intel ICH5 SATA150 controller> port
0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 5 at device 31.2 on pci0
ichsmb0: <Intel 82801EB (ICH5) SMBus controller> port 0x500-0x51f irq 11
at device 31.3 on pci0

But atacontrol always says me that it uses UDMA33 instead of SATA-150 or
other (I can't set UDMA66/100/133/150), in bios I tried to use legacy,
combined and enhaced modes but always work in UDMA33.

ad0: DMA limited to UDMA33, non-ATA66 cable or device
ad1: DMA limited to UDMA33, non-ATA66 cable or device

Iozone, bonnie and bonnie++ always report a maximum transfer of
32MB/Sec.

The question is: How I can set the transfer to any other UDMA? FreeBSD
detects ther hardware but I can't use that features without ATAng? Any
patch/solution/idea?

Thanks in advance
--=20
--

Daniel Ortiz
d.ortiz@in.ilimit.es

--E39vaYmALEf/7YXx
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/9VkEPprEQTARuLoRAgDWAKC3X1owW6ZzTBdy+YVG5yAoFECLfQCgoy7q
Y/3zZT1D0XKpcs3ZAVKm9VA=
=UxPc
-----END PGP SIGNATURE-----

--E39vaYmALEf/7YXx--

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 08:45:18 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id AB46D16A4CE; Fri,  2 Jan 2004 08:45:18 -0800 (PST)
Received: from mv.milwaukeevalve.com (mail.milwaukeevalve.com [66.84.180.13])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id D6D4B43D58; Fri,  2 Jan 2004 08:45:16 -0800 (PST)
	(envelope-from linux@MILWAUKEEVALVE.COM)
Received: (from root@localhost)
	by mv.milwaukeevalve.com (8.11.6/8.11.6) id i02GfZj29441;
	Fri, 2 Jan 2004 10:41:35 -0600
Received: from Pmjalex ([192.168.2.189])
	(authenticated)
	by mv.milwaukeevalve.com (8.11.6/8.11.6) with ESMTP id i02Gepe28097;
	Fri, 2 Jan 2004 10:40:52 -0600
From: "michael Alexander" <linux@MILWAUKEEVALVE.COM>
To: "'Scott Long'" <scottl@freebsd.org>
Date: Fri, 2 Jan 2004 10:40:50 -0600
Message-ID: <006a01c3d14f$2fc8dba0$bd02a8c0@Pmjalex>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <20031229160108.P93734@pooker.samsco.home>
X-scanner: scanned by Inflex 1.0.12.7
cc: freebsd-scsi@freebsd.org
cc: freebsd-hardware@freebsd.org
Subject: RE: Problems installing onto DAC960 (Mylex Acceleraid250)
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 16:45:18 -0000



> -----Original Message-----
> From: owner-freebsd-hardware@freebsd.org=20
> [mailto:owner-freebsd-hardware@freebsd.org] On Behalf Of Scott Long
> Sent: Monday, December 29, 2003 5:07 PM
> To: michael Alexander
> Cc: freebsd-scsi@freebsd.org; freebsd-hardware@freebsd.org
> Subject: RE: Problems installing onto DAC960 (Mylex Acceleraid250)
>=20
>=20
> On Mon, 29 Dec 2003, michael Alexander wrote:
> >
> > Ok, downloaded the 5.2RC2-i386-miniinst.iso, no luck.
> > BIOS has an option of
> > "PCI IRQs to IO-APIC Mapping"  (enabled/disabled)
> > I didn't see anything else relating to APIC, or APCI(?)
> >
> > I set that to disabled.  No luck, Then I left it disabled=20
> and tried install
> > w/o apic, still no luck.  Then I ran with logging and have=20
> the following
> > messages on screen after the Waiting 15 seconds....
>=20
> Did you select the 'Boot with ACPI disabled' option from the=20
> boot menu on
> the CD?  Sorry if this is a dumb question, but people often transpose
> 'apic' and 'acpi', so I want to make sure.  I would try=20
> toggling both the
> BIOS 'IO_APIC Mapping' option and the ACPI option on the CD boot menu.
> If all four combinations fail to work, the only thing left to=20
> do is set
> up a serial console and capture the boot output and email it out.  The
> boot serial console is enabled by escaping from the CD boot menu and
> typing 'boot -Dhv'
>=20
> Scott

Yes, I did try using the boot with acpi disabled option, and it didn't =
help.

I got another message off-list, that stated that FreeBSD currently =
doesn't
work with the zero channel raid in this configuration, maybe not in any
configuration?  Because I do not have the proper cabling to connect the =
card
and the raid chassis, it appears that for now FreeBSD is a dead end for =
this
hardware.

Thanks for the assistance though.
-Mike

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 09:19:44 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3DB3516A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 09:19:44 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.176])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7E63243D5E
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 09:19:18 -0800 (PST)
	(envelope-from Stefan.Esser@se-it-security.de)
Received: from [212.227.126.208] (helo=mrelayng7.kundenserver.de)
	by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
	id 1AcSx9-0001K5-00; Fri, 02 Jan 2004 18:19:15 +0100
Received: from [80.132.237.122] (helo=Gatekeeper.FreeBSD.org)
	by mrelayng7.kundenserver.de with asmtp (Exim 3.35 #1)
	id 1AcSx9-000127-00; Fri, 02 Jan 2004 18:19:15 +0100
Received: by Gatekeeper.FreeBSD.org (Postfix, from userid 10000)
	id 8DEA56043; Fri,  2 Jan 2004 18:35:46 +0100 (CET)
Received: from StefanEsser.FreeBSD.org (StefanEsser [192.168.0.10])
	by Gatekeeper.FreeBSD.org (Postfix) with ESMTP
	id 894D15F27; Fri,  2 Jan 2004 18:17:31 +0100 (CET)
Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200)
	id DD8082303; Fri,  2 Jan 2004 18:17:30 +0100 (CET)
Date: Fri, 2 Jan 2004 18:17:30 +0100
From: Stefan =?iso-8859-1?Q?E=DFer?= <Stefan.Esser@SE-IT-Security.de>
To: Daniel Ortiz <d.ortiz@in.ilimit.es>
Message-ID: <20040102171730.GB11022@StefanEsser.FreeBSD.org>
References: <20040102114156.GB7190@in.ilimit.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040102114156.GB7190@in.ilimit.es>
User-Agent: Mutt/1.5.5.1i
X-Provags-ID: kundenserver.de abuse@kundenserver.de
	auth:fa3fae9b6ca38d745862a668565919f6
cc: freebsd-hardware@freebsd.org
Subject: Re: atacontrol/udma
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 17:19:44 -0000

On 2004-01-02 12:41 +0100, Daniel Ortiz <d.ortiz@in.ilimit.es> wrote:
> But atacontrol always says me that it uses UDMA33 instead of SATA-150 or
> other (I can't set UDMA66/100/133/150), in bios I tried to use legacy,
> combined and enhaced modes but always work in UDMA33.
> 
> ad0: DMA limited to UDMA33, non-ATA66 cable or device
> ad1: DMA limited to UDMA33, non-ATA66 cable or device
                              ^^^^^^^^^^^^^^^

You need to use an 80 wire cable for higher transfer speeds 
than UDMA33. (Your cable appears to be of the 40 wire kind).

Regards, STefan

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 09:29:16 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 01A0F16A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 09:29:16 -0800 (PST)
Received: from moe.ilimit.es (38.Red-213-96-13.pooles.rima-tde.net
	[213.96.13.38])	by mx1.FreeBSD.org (Postfix) with ESMTP id 629D143D48
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 09:29:01 -0800 (PST)
	(envelope-from d.ortiz@in.ilimit.es)
Received: from dani.ilimit.lan ([192.168.1.57] helo=in.ilimit.es)
	by moe.ilimit.es with smtp (Exim 3.35 #1 (Debian))
	id 1AcT6J-0005V5-00
	for <freebsd-hardware@freebsd.org>; Fri, 02 Jan 2004 18:28:43 +0100
Received: by in.ilimit.es (sSMTP sendmail emulation);
	Fri,  2 Jan 2004 18:28:38 +0100
Date: Fri, 2 Jan 2004 18:28:38 +0100
From: Daniel Ortiz <d.ortiz@in.ilimit.es>
To: freebsd-hardware@freebsd.org
Message-ID: <20040102172838.GB211@in.ilimit.es>
References: <20040102114156.GB7190@in.ilimit.es>
	<20040102171730.GB11022@StefanEsser.FreeBSD.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="+pHx0qQiF2pBVqBT"
Content-Disposition: inline
In-Reply-To: <20040102171730.GB11022@StefanEsser.FreeBSD.org>
User-Agent: Mutt/1.4.1i
X-ILIMIT-MailScanner-Information: ILIMIT Comunicacions
X-ILIMIT-MailScanner: Found to be clean
Subject: Re: atacontrol/udma
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 17:29:16 -0000


--+pHx0qQiF2pBVqBT
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 02, 2004 at 06:17:30PM +0100, Stefan E=DFer wrote:
> You need to use an 80 wire cable for higher transfer speeds=20
> than UDMA33. (Your cable appears to be of the 40 wire kind).

A serial ata cable doesn't work?

--=20
--

Daniel Ortiz
d.ortiz@in.ilimit.es

--+pHx0qQiF2pBVqBT
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/9apGPprEQTARuLoRAiGEAKCukKYaZtTTSn1gd9GG+owc05TYmgCgw8KC
JnTDfmHoQtqBbPIjDuMhLSY=
=7saO
-----END PGP SIGNATURE-----

--+pHx0qQiF2pBVqBT--

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 09:44:23 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CB83B16A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 09:44:23 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.177])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1223243D64
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 09:44:21 -0800 (PST)
	(envelope-from Stefan.Esser@se-it-security.de)
Received: from [212.227.126.206] (helo=mrelayng5.kundenserver.de)
	by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
	id 1AcTLK-0004TT-00; Fri, 02 Jan 2004 18:44:14 +0100
Received: from [80.132.237.122] (helo=Gatekeeper.FreeBSD.org)
	by mrelayng5.kundenserver.de with asmtp (Exim 3.35 #1)
	id 1AcTLK-0007mU-00; Fri, 02 Jan 2004 18:44:14 +0100
Received: from StefanEsser.FreeBSD.org (StefanEsser [192.168.0.10])
	by Gatekeeper.FreeBSD.org (Postfix) with ESMTP
	id 197055F18; Fri,  2 Jan 2004 18:44:12 +0100 (CET)
Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200)
	id 8F3A72303; Fri,  2 Jan 2004 18:44:12 +0100 (CET)
Date: Fri, 2 Jan 2004 18:44:12 +0100
From: Stefan =?iso-8859-1?Q?E=DFer?= <Stefan.Esser@SE-IT-Security.de>
To: Daniel Ortiz <d.ortiz@in.ilimit.es>
Message-ID: <20040102174412.GA11623@StefanEsser.FreeBSD.org>
References: <20040102114156.GB7190@in.ilimit.es>
	<20040102171730.GB11022@StefanEsser.FreeBSD.org>
	<20040102172838.GB211@in.ilimit.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <20040102172838.GB211@in.ilimit.es>
User-Agent: Mutt/1.5.5.1i
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: kundenserver.de abuse@kundenserver.de
	auth:fa3fae9b6ca38d745862a668565919f6
cc: freebsd-hardware@freebsd.org
Subject: Re: atacontrol/udma
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 17:44:23 -0000

On 2004-01-02 18:28 +0100, Daniel Ortiz <d.ortiz@in.ilimit.es> wrote:
> On Fri, Jan 02, 2004 at 06:17:30PM +0100, Stefan E=DFer wrote:
> > You need to use an 80 wire cable for higher transfer speeds=20
> > than UDMA33. (Your cable appears to be of the 40 wire kind).
>=20
> A serial ata cable doesn't work?

Sorry, seems I didn't read the relevant lines of your message.

Serial ATA works on my mainboard (with a Promise PDC20376 chip).
The probe message talks about UDMA100 instead of SATA150:

atapci0: <Promise PDC20376 SATA150 controller> port 0xa800-0xa87f,0xb000-=
0xb00f,0xb400-0xb43f mem 0xcd800000-0xcd81ffff,0xce000000-0xce000fff irq =
17 at device 8.0 on pci0
ad4: 157066MB <HDS722516VLSA80> [319120/16/63] at ata2-master UDMA100

Can't tell what's wrong in your case.

Regards, STefan

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 10:12:59 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id F36A816A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 10:12:58 -0800 (PST)
Received: from moe.ilimit.es (38.Red-213-96-13.pooles.rima-tde.net
	[213.96.13.38])	by mx1.FreeBSD.org (Postfix) with ESMTP id B0AAF43D2D
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 10:12:51 -0800 (PST)
	(envelope-from d.ortiz@in.ilimit.es)
Received: from dani.ilimit.lan ([192.168.1.57] helo=in.ilimit.es)
	by moe.ilimit.es with smtp (Exim 3.35 #1 (Debian))
	id 1AcTmq-00061i-00
	for <freebsd-hardware@freebsd.org>; Fri, 02 Jan 2004 19:12:40 +0100
Received: by in.ilimit.es (sSMTP sendmail emulation);
	Fri,  2 Jan 2004 19:12:47 +0100
Date: Fri, 2 Jan 2004 19:12:47 +0100
From: Daniel Ortiz <d.ortiz@in.ilimit.es>
To: freebsd-hardware@freebsd.org
Message-ID: <20040102181247.GC211@in.ilimit.es>
References: <20040102114156.GB7190@in.ilimit.es>
	<20040102171730.GB11022@StefanEsser.FreeBSD.org>
	<20040102172838.GB211@in.ilimit.es>
	<20040102174412.GA11623@StefanEsser.FreeBSD.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="WplhKdTI2c8ulnbP"
Content-Disposition: inline
In-Reply-To: <20040102174412.GA11623@StefanEsser.FreeBSD.org>
User-Agent: Mutt/1.4.1i
X-ILIMIT-MailScanner-Information: ILIMIT Comunicacions
X-ILIMIT-MailScanner: Found to be clean
Subject: Re: atacontrol/udma
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 18:12:59 -0000


--WplhKdTI2c8ulnbP
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 02, 2004 at 06:44:12PM +0100, Stefan E=DFer wrote:
> Serial ATA works on my mainboard (with a Promise PDC20376 chip).
> The probe message talks about UDMA100 instead of SATA150:
>=20
> atapci0: <Promise PDC20376 SATA150 controller> port 0xa800-0xa87f,0xb000-=
0xb00f,0xb400-0xb43f mem 0xcd800000-0xcd81ffff,0xce000000-0xce000fff irq 17=
 at device 8.0 on pci0
> ad4: 157066MB <HDS722516VLSA80> [319120/16/63] at ata2-master UDMA100

I'm must use FreeBSD 4.8 or 4.9 with this server for use H-Sphere
(doesn't support 5.x branch).

The motherboard has an Intel ICH5 chipset and all motherboard devices
are supported and detected by the kernel.
In /usr/src/sys/dev/ata/ata-pci.c and ata-dma.c appears to be supported.

[taik0@dani][~]# grep  ICH5 /usr/src/sys/dev/ata/*
/usr/src/sys/dev/ata/ata-dma.c:    case 0x24db8086:     /* Intel ICH5 */
/usr/src/sys/dev/ata/ata-dma.c:    case 0x24d18086:     /* Intel ICH5
SATA */
/usr/src/sys/dev/ata/ata-pci.c: return "Intel ICH5 SATA150 controller";
/usr/src/sys/dev/ata/ata-pci.c: return "Intel ICH5 ATA100 controller";
/usr/src/sys/dev/ata/ata-pci.c:    case 0x24d18086:     /* Intel ICH5
SATA150 */

I must can set any UDMA mode with atacontrol, but doesn't work always
return the UDMA33 mode.

Do you have any special option in your kernel configuration or a setting
in sysctl?

Thanks in advance
--=20
--

Daniel Ortiz
d.ortiz@in.ilimit.es

--WplhKdTI2c8ulnbP
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/9bSfPprEQTARuLoRAqj0AKC5uxri7auBACdiwL7ITgt7iIY04gCeOKmt
ZIsJHiXho/h8Pzm4U+rDalc=
=kOHn
-----END PGP SIGNATURE-----

--WplhKdTI2c8ulnbP--

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 10:25:54 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 61F8D16A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 10:25:54 -0800 (PST)
Received: from helium.xe.net (helium.xe.net [216.220.37.68])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3C1AB43D45
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 10:25:53 -0800 (PST)	(envelope-from bfarmer@xe.com)
Received: from [192.168.1.100] (ws-gw.tor.xe.net [216.220.37.73])
	by helium.xe.net (8.12.8/8.12.8) with ESMTP id i02IPpKM076088;
	Fri, 2 Jan 2004 13:25:52 -0500 (EST)
Date: Fri, 02 Jan 2004 13:25:52 -0500
From: Beric Farmer <bfarmer@xe.com>
To: Daniel Ortiz <d.ortiz@in.ilimit.es>
Message-ID: <13654202.1073049952@[192.168.1.100]>
In-Reply-To: <20040102114156.GB7190@in.ilimit.es>
References: <20040102114156.GB7190@in.ilimit.es>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
cc: freebsd-hardware@freebsd.org
Subject: Re: atacontrol/udma
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 18:25:54 -0000


--On January 02, 2004 12:41 +0100 Daniel Ortiz <d.ortiz@in.ilimit.es> 
wrote:

>
> The question is: How I can set the transfer to any other UDMA?
> FreeBSD detects ther hardware but I can't use that features without
> ATAng? Any patch/solution/idea?
>

My understanding is that 4.x doesn't have support for SATA. 
Evidently, the developers have been focusing on 5.x, and the 
necessary changes are non-trivial and not straightforward to apply to 
4.x.

>From what I've read, you'll need to use 5.x in order to get support 
for your SATA drives.

I ran into this problem under 4.9-RELEASE.  As a test, I booted from 
the 5.1-RELEASE CD and the SATA drives were properly detected, and 
not downgraded to UDMA33.

I've sort of been waiting for the official word that 5.x is ready for 
production usage before I run with it (the documentation still 
recommends that "conservative users" not upgrade).

Hope this helps.

Beric

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 10:49:07 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 78A4516A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 10:49:07 -0800 (PST)
Received: from mail.johnrshannon.com (mail.johnrshannon.com [69.20.155.49])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D47C843D31
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 10:49:03 -0800 (PST)
	(envelope-from john@johnrshannon.com)
Received: by mail.johnrshannon.com (Postfix, from userid 1003)
	id CC97B124AF; Fri,  2 Jan 2004 11:49:02 -0700 (MST)
Received: from colleen.internal.johnrshannon.com
	(colleen.internal.johnrshannon.com [192.168.1.39])
	by mail.johnrshannon.com (Postfix) with ESMTP id D423312499
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 11:48:59 -0700 (MST)
Received: by colleen.internal.johnrshannon.com (Postfix, from userid 1000)
	id ECD3D10505; Fri,  2 Jan 2004 11:48:59 -0700 (MST)
From: "John R. Shannon" <john@johnrshannon.com>
To: freebsd-hardware@freebsd.org
Date: Fri, 2 Jan 2004 11:48:58 -0700
User-Agent: KMail/1.5.4
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Description: clearsigned data
Content-Disposition: inline
Message-Id: <200401021148.59704.john@johnrshannon.com>
Subject: umass conflicts with scsi disk drives
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: john@johnrshannon.com
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 18:49:07 -0000

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

SuperMicro 370DE6 motherboard
dual P3

I'm experiencing a problem where umass is appropriating da0 and da1 after=20
these have been assigned to SCSI hard-drives. This is only a problem if the=
=20
Sandisk CF card reader is attached when the system boots; otherwise, device=
=20
assignment looks correct.

Dmesg output, CF reader inserted after system boot, follows:

=46reeBSD 5.2-CURRENT #0: Thu Jan  1 14:37:39 MST 2004
    root@pablo.internal.johnrshannon.com:/usr/obj/usr/src/sys/MYKERNEL
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0770000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc077026c.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel Pentium III (999.52-MHz 686-class CPU)
  Origin =3D "GenuineIntel"  Id =3D 0x686  Stepping =3D 6
  Features=3D0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE=
,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory  =3D 1073676288 (1023 MB)
avail memory =3D 1045360640 (996 MB)
ACPI APIC Table: <RCC    RCCNILE >
=46reeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0 <Version 1.1> irqs 0-15 on motherboard
ioapic1 <Version 1.1> irqs 16-31 on motherboard
Pentium Pro MTRR support enabled
    ACPI-0671: *** Warning: Type override - [DEB_] had invalid type (Intege=
r)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [MLIB] had invalid type (Intege=
r)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [IO__] had invalid type (Intege=
r)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [DATA] had invalid type (String=
)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [SIO_] had invalid type (String=
)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [SB__] had invalid type (String=
)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [PM__] had invalid type (String=
)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [ICNT] had invalid type (String=
)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [ACPI] had invalid type (String=
)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [OSB4] had invalid type (String=
)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [PM__] had invalid type (String=
)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [BIOS] had invalid type (Intege=
r)=20
for Scope operator, changed to (Scope)
    ACPI-0671: *** Warning: Type override - [CMOS] had invalid type (Intege=
r)=20
for Scope operator, changed to (Scope)
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
acpi0: <RCC    RCCNILE > on motherboard
acpi0: Power Button (fixed)
acpi0: Sleep Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
pcibios: BIOS version 2.10
Using $PIR table, 10 entries at 0xc00f5350
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
acpi_cpu0: <CPU> on acpi0
acpi_cpu1: <CPU> on acpi0
acpi_cpu1: Failed to attach throttling P_CNT
acpi_cpu2: <CPU> on acpi0
device_probe_and_attach: acpi_cpu2 attach returned 6
acpi_cpu2: <CPU> on acpi0
device_probe_and_attach: acpi_cpu2 attach returned 6
acpi_button0: <Sleep Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib0: slot 15 INTA is routed to irq 10
pcib1: <ACPI PCI-PCI bridge> at device 0.1 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
ohci0: <OPTi 82C861 (FireLink) USB controller> mem 0xfeafc000-0xfeafcfff ir=
q=20
16 at device 1.0 on pci0
usb0: OHCI version 1.0, legacy support
usb0: <OPTi 82C861 (FireLink) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pci0: <multimedia, audio> at device 2.0 (no driver attached)
ahc0: <Adaptec 3960D Ultra160 SCSI adapter> port 0xc400-0xc4ff mem=20
0xfeafd000-0xfeafdfff irq 28 at device 4.0 on pci0
aic7899: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs
ahc1: <Adaptec 3960D Ultra160 SCSI adapter> port 0xc800-0xc8ff mem=20
0xfeafe000-0xfeafefff irq 29 at device 4.1 on pci0
aic7899: Ultra160 Wide Channel B, SCSI Id=3D7, 32/253 SCBs
ahc2: <Adaptec aic7899 Ultra160 SCSI adapter> port 0xd000-0xd0ff mem=20
0xfeadc000-0xfeadcfff irq 26 at device 5.0 on pci0
aic7899: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs
ahc3: <Adaptec aic7899 Ultra160 SCSI adapter> port 0xd800-0xd8ff mem=20
0xfeadf000-0xfeadffff irq 27 at device 5.1 on pci0
aic7899: Ultra160 Wide Channel B, SCSI Id=3D7, 32/253 SCBs
fxp0: <Intel 82559 Pro/100 Ethernet> port 0xd400-0xd43f mem=20
0xfe900000-0xfe9fffff,0xfeadd000-0xfeaddfff irq 31 at device 6.0 on pci0
fxp0: Ethernet address 00:30:48:10:79:16
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0: <PCI-ISA bridge> port 0x580-0x58f at device 15.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <ServerWorks ROSB4 UDMA33 controller> port 0xffa0-0xffaf at device=
=20
15.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
ohci1: <OHCI (generic) USB controller> mem 0xfeaff000-0xfeafffff irq 10 at=
=20
device 15.2 on pci0
usb1: OHCI version 1.0, legacy support
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 4 ports with 4 removable, self powered
pcib2: <ACPI Host-PCI bridge> on acpi0
pci2: <ACPI PCI bus> on pcib2
atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
fdc0: cmd 3 failed at out byte 1 of 3
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppbus0: <Parallel port bus> on ppc0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
acpi_cpu2: <CPU> on acpi0
device_probe_and_attach: acpi_cpu2 attach returned 6
acpi_cpu2: <CPU> on acpi0
device_probe_and_attach: acpi_cpu2 attach returned 6
fdc0: cmd 3 failed at out byte 1 of 3
orm0: <Option ROMs> at iomem 0xcd000-0xd2fff,0xcc000-0xccfff,0xc0000-0xcaff=
f=20
on isa0
pmtimer0 on isa0
fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> at port=20
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=3D0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 10.000 msec
Waiting 15 seconds for SCSI devices to settle
acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0%
GEOM: create disk cd0 dp=3D0xc5fe6600
GEOM: create disk da0 dp=3D0xc601b050
GEOM: create disk da1 dp=3D0xc5fd8c50
GEOM: create disk da2 dp=3D0xc6002c50
GEOM: create disk da3 dp=3D0xc6028050
da0 at ahc2 bus 0 target 0 lun 0
da0: <SEAGATE ST318452LW 0004> Fixed Direct Access SCSI-3 device
da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing=20
Enabled
da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
SMP: AP CPU #1 Launched!
da1 at ahc3 bus 0 target 1 lun 0
da1: <IBM DNES-318350W SA30> Fixed Direct Access SCSI-3 device
da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing=20
Enabled
da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
da2 at ahc3 bus 0 target 8 lun 0
da2: <IBM DNES-318350W SA30> Fixed Direct Access SCSI-3 device
da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing=20
Enabled
da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
da3 at ahc3 bus 0 target 9 lun 0
da3: <IBM DNES-318350W SA30> Fixed Direct Access SCSI-3 device
da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing=20
Enabled
da3: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
cd0 at ahc0 bus 0 target 5 lun 0
cd0: <YAMAHA CRW2100S 1.0H> Removable CD-ROM SCSI-2 device
cd0: 20.000MB/s transfers (20.000MHz, offset 7)
cd0: cd present [65191 x 2048 byte records]
Mounting root from ufs:/dev/da0s1a
fxp0: Microcode loaded, int_delay: 1000 usec  bundle_max: 6
fxp0: Microcode loaded, int_delay: 1000 usec  bundle_max: 6
umass0: SanDisk Corporation ImageMate CF-SM, rev 1.10/1.00, addr 2
GEOM: create disk da4 dp=3D0xc5e0cc50
da4 at umass-sim0 bus 0 target 0 lun 0
da4: <SanDisk ImageMate CF-SM 0100> Removable Direct Access SCSI-0 device
da4: 1.000MB/s transfers
da4: Attempt to query device size failed: NOT READY, Medium not present
(da4:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da4:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da4:umass-sim0:0:0:0): SCSI Status: Check Condition
(da4:umass-sim0:0:0:0): NOT READY asc:3a,0
(da4:umass-sim0:0:0:0): Medium not present
(da4:umass-sim0:0:0:0): Unretryable error
Opened disk da4 -> 6
(da4:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da4:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da4:umass-sim0:0:0:0): SCSI Status: Check Condition
(da4:umass-sim0:0:0:0): NOT READY asc:3a,0
(da4:umass-sim0:0:0:0): Medium not present
(da4:umass-sim0:0:0:0): Unretryable error
Opened disk da4 -> 6
GEOM: create disk da5 dp=3D0xc5e5b850
da5 at umass-sim0 bus 0 target 0 lun 1
da5: <SanDisk ImageMate CF-SM 0100> Removable Direct Access SCSI-0 device
da5: 1.000MB/s transfers
da5: Attempt to query device size failed: NOT READY, Medium not present
(da5:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0
(da5:umass-sim0:0:0:1): CAM Status: SCSI Status Error
(da5:umass-sim0:0:0:1): SCSI Status: Check Condition
(da5:umass-sim0:0:0:1): NOT READY asc:3a,0
(da5:umass-sim0:0:0:1): Medium not present
(da5:umass-sim0:0:0:1): Unretryable error
Opened disk da5 -> 6
(da5:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0
(da5:umass-sim0:0:0:1): CAM Status: SCSI Status Error
(da5:umass-sim0:0:0:1): SCSI Status: Check Condition
(da5:umass-sim0:0:0:1): NOT READY asc:3a,0
(da5:umass-sim0:0:0:1): Medium not present
(da5:umass-sim0:0:0:1): Unretryable error
Opened disk da5 -> 6

=2D --=20

John R. Shannon
john@johnrshannon.com
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iEYEARECAAYFAj/1vRoACgkQOKbCxya4HYuA6gCgnd7IZvzYrjXYd5nOJ2njUl8X
gaAAoK7Y+yTXn/rEAcTgClor55pQgiVC
=3DE/PB
=2D----END PGP SIGNATURE-----

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 10:57:47 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 618)
	id 29C2116A4CF; Fri,  2 Jan 2004 10:57:47 -0800 (PST)
To: freebsd-current@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG
Date: Fri, 2 Jan 2004 10:57:47 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <20040102185747.29C2116A4CF@hub.freebsd.org>
From: wpaul@FreeBSD.ORG (Bill Paul)
Subject: Re: Intel 'Centrino' WLAN and Project Evil: how you can help
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 18:57:47 -0000


FYI:

A kind individual has stepped forward to donate an Intel 2100 card
and miniPCI carrier board, which should hopefully arrive at Project
Evil Laboratories within the next week or so. Thanks to all who
responded. :)

Project Evil: it's what's for breakfast.

-Bill

--
=============================================================================
-Bill Paul            (510) 749-2329 | Senior Engineer, Master of Unix-Fu
                 wpaul@windriver.com | Wind River Systems
=============================================================================
              <adamw> you're just BEGGING to face the moose
=============================================================================

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 11:15:46 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 49AC316A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 11:15:46 -0800 (PST)
Received: from mail.johnrshannon.com (mail.johnrshannon.com [69.20.155.49])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1ACFB43D53
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 11:15:41 -0800 (PST)
	(envelope-from john@johnrshannon.com)
Received: by mail.johnrshannon.com (Postfix, from userid 1003)
	id 906DB124A1; Fri,  2 Jan 2004 12:15:40 -0700 (MST)
Received: from colleen.internal.johnrshannon.com
	(colleen.internal.johnrshannon.com [192.168.1.39])
	by mail.johnrshannon.com (Postfix) with ESMTP id CD76912499
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 12:15:35 -0700 (MST)
Received: by colleen.internal.johnrshannon.com (Postfix, from userid 1000)
	id 181C910505; Fri,  2 Jan 2004 12:15:36 -0700 (MST)
From: "John R. Shannon" <john@johnrshannon.com>
To: freebsd-hardware@freebsd.org
Date: Fri, 2 Jan 2004 12:15:34 -0700
User-Agent: KMail/1.5.4
References: <200401021148.59704.john@johnrshannon.com>
In-Reply-To: <200401021148.59704.john@johnrshannon.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: clearsigned data
Content-Disposition: inline
Message-Id: <200401021215.35921.john@johnrshannon.com>
Subject: Re: umass conflicts with scsi disk drives
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: john@johnrshannon.com
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 19:15:46 -0000

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It appears that I misinterpreted the events because they scroll by so quick=
ly.=20
The disk assignments are simply changing depending on whether the umass=20
device is attached or not.

Question: How do I fix the device assignments (da) so that the system disk=
=20
will always have the same device number?

On Friday 02 January 2004 11:48 am, John R. Shannon wrote:
> SuperMicro 370DE6 motherboard
> dual P3
>
> I'm experiencing a problem where umass is appropriating da0 and da1 after
> these have been assigned to SCSI hard-drives. This is only a problem if t=
he
> Sandisk CF card reader is attached when the system boots; otherwise, devi=
ce
> assignment looks correct.
>
> Dmesg output, CF reader inserted after system boot, follows:
>
> FreeBSD 5.2-CURRENT #0: Thu Jan  1 14:37:39 MST 2004
>     root@pablo.internal.johnrshannon.com:/usr/obj/usr/src/sys/MYKERNEL
> Preloaded elf kernel "/boot/kernel/kernel" at 0xc0770000.
> Preloaded elf module "/boot/kernel/acpi.ko" at 0xc077026c.
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel Pentium III (999.52-MHz 686-class CPU)
>   Origin =3D "GenuineIntel"  Id =3D 0x686  Stepping =3D 6
> =20
> Features=3D0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE=
,MCA
>,CMOV,PAT,PSE36,MMX,FXSR,SSE> real memory  =3D 1073676288 (1023 MB)
> avail memory =3D 1045360640 (996 MB)
> ACPI APIC Table: <RCC    RCCNILE >
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
>  cpu0 (BSP): APIC ID:  0
>  cpu1 (AP): APIC ID:  1
> ioapic0 <Version 1.1> irqs 0-15 on motherboard
> ioapic1 <Version 1.1> irqs 16-31 on motherboard
> Pentium Pro MTRR support enabled
>     ACPI-0671: *** Warning: Type override - [DEB_] had invalid type
> (Integer) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [MLIB] had invalid type
> (Integer) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [IO__] had invalid type
> (Integer) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [DATA] had invalid type
> (String) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [SIO_] had invalid type
> (String) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [SB__] had invalid type
> (String) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [PM__] had invalid type
> (String) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [ICNT] had invalid type
> (String) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [ACPI] had invalid type
> (String) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [OSB4] had invalid type
> (String) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [PM__] had invalid type
> (String) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [BIOS] had invalid type
> (Integer) for Scope operator, changed to (Scope)
>     ACPI-0671: *** Warning: Type override - [CMOS] had invalid type
> (Integer) for Scope operator, changed to (Scope)
> npx0: [FAST]
> npx0: <math processor> on motherboard
> npx0: INT 16 interface
> acpi0: <RCC    RCCNILE > on motherboard
> acpi0: Power Button (fixed)
> acpi0: Sleep Button (fixed)
> Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
> pcibios: BIOS version 2.10
> Using $PIR table, 10 entries at 0xc00f5350
> acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
> acpi_cpu0: <CPU> on acpi0
> acpi_cpu1: <CPU> on acpi0
> acpi_cpu1: Failed to attach throttling P_CNT
> acpi_cpu2: <CPU> on acpi0
> device_probe_and_attach: acpi_cpu2 attach returned 6
> acpi_cpu2: <CPU> on acpi0
> device_probe_and_attach: acpi_cpu2 attach returned 6
> acpi_button0: <Sleep Button> on acpi0
> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> pci0: <ACPI PCI bus> on pcib0
> pcib0: slot 15 INTA is routed to irq 10
> pcib1: <ACPI PCI-PCI bridge> at device 0.1 on pci0
> pci1: <ACPI PCI bus> on pcib1
> pci1: <display, VGA> at device 0.0 (no driver attached)
> ohci0: <OPTi 82C861 (FireLink) USB controller> mem 0xfeafc000-0xfeafcfff
> irq 16 at device 1.0 on pci0
> usb0: OHCI version 1.0, legacy support
> usb0: <OPTi 82C861 (FireLink) USB controller> on ohci0
> usb0: USB revision 1.0
> uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> pci0: <multimedia, audio> at device 2.0 (no driver attached)
> ahc0: <Adaptec 3960D Ultra160 SCSI adapter> port 0xc400-0xc4ff mem
> 0xfeafd000-0xfeafdfff irq 28 at device 4.0 on pci0
> aic7899: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs
> ahc1: <Adaptec 3960D Ultra160 SCSI adapter> port 0xc800-0xc8ff mem
> 0xfeafe000-0xfeafefff irq 29 at device 4.1 on pci0
> aic7899: Ultra160 Wide Channel B, SCSI Id=3D7, 32/253 SCBs
> ahc2: <Adaptec aic7899 Ultra160 SCSI adapter> port 0xd000-0xd0ff mem
> 0xfeadc000-0xfeadcfff irq 26 at device 5.0 on pci0
> aic7899: Ultra160 Wide Channel A, SCSI Id=3D7, 32/253 SCBs
> ahc3: <Adaptec aic7899 Ultra160 SCSI adapter> port 0xd800-0xd8ff mem
> 0xfeadf000-0xfeadffff irq 27 at device 5.1 on pci0
> aic7899: Ultra160 Wide Channel B, SCSI Id=3D7, 32/253 SCBs
> fxp0: <Intel 82559 Pro/100 Ethernet> port 0xd400-0xd43f mem
> 0xfe900000-0xfe9fffff,0xfeadd000-0xfeaddfff irq 31 at device 6.0 on pci0
> fxp0: Ethernet address 00:30:48:10:79:16
> miibus0: <MII bus> on fxp0
> inphy0: <i82555 10/100 media interface> on miibus0
> inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> isab0: <PCI-ISA bridge> port 0x580-0x58f at device 15.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <ServerWorks ROSB4 UDMA33 controller> port 0xffa0-0xffaf at devi=
ce
> 15.1 on pci0
> ata0: at 0x1f0 irq 14 on atapci0
> ata0: [MPSAFE]
> ata1: at 0x170 irq 15 on atapci0
> ata1: [MPSAFE]
> ohci1: <OHCI (generic) USB controller> mem 0xfeaff000-0xfeafffff irq 10 at
> device 15.2 on pci0
> usb1: OHCI version 1.0, legacy support
> usb1: <OHCI (generic) USB controller> on ohci1
> usb1: USB revision 1.0
> uhub1: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub1: 4 ports with 4 removable, self powered
> pcib2: <ACPI Host-PCI bridge> on acpi0
> pci2: <ACPI PCI bus> on pcib2
> atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
> atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
> kbd0 at atkbd0
> psm0: <PS/2 Mouse> irq 12 on atkbdc0
> psm0: model Generic PS/2 mouse, device ID 0
> fdc0: cmd 3 failed at out byte 1 of 3
> sio0 port 0x3f8-0x3ff irq 4 on acpi0
> sio0: type 16550A
> sio1 port 0x2f8-0x2ff irq 3 on acpi0
> sio1: type 16550A
> ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0
> ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
> ppc0: FIFO with 16/16/8 bytes threshold
> ppbus0: <Parallel port bus> on ppc0
> lpt0: <Printer> on ppbus0
> lpt0: Interrupt-driven port
> ppi0: <Parallel I/O> on ppbus0
> acpi_cpu2: <CPU> on acpi0
> device_probe_and_attach: acpi_cpu2 attach returned 6
> acpi_cpu2: <CPU> on acpi0
> device_probe_and_attach: acpi_cpu2 attach returned 6
> fdc0: cmd 3 failed at out byte 1 of 3
> orm0: <Option ROMs> at iomem
> 0xcd000-0xd2fff,0xcc000-0xccfff,0xc0000-0xcafff on isa0
> pmtimer0 on isa0
> fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> at port
> 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
> fdc0: FIFO enabled, 8 bytes threshold
> fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> sc0: <System console> at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=3D0x300>
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> Timecounters tick every 10.000 msec
> Waiting 15 seconds for SCSI devices to settle
> acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0%
> GEOM: create disk cd0 dp=3D0xc5fe6600
> GEOM: create disk da0 dp=3D0xc601b050
> GEOM: create disk da1 dp=3D0xc5fd8c50
> GEOM: create disk da2 dp=3D0xc6002c50
> GEOM: create disk da3 dp=3D0xc6028050
> da0 at ahc2 bus 0 target 0 lun 0
> da0: <SEAGATE ST318452LW 0004> Fixed Direct Access SCSI-3 device
> da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing
> Enabled
> da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
> SMP: AP CPU #1 Launched!
> da1 at ahc3 bus 0 target 1 lun 0
> da1: <IBM DNES-318350W SA30> Fixed Direct Access SCSI-3 device
> da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
> Enabled
> da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
> da2 at ahc3 bus 0 target 8 lun 0
> da2: <IBM DNES-318350W SA30> Fixed Direct Access SCSI-3 device
> da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
> Enabled
> da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
> da3 at ahc3 bus 0 target 9 lun 0
> da3: <IBM DNES-318350W SA30> Fixed Direct Access SCSI-3 device
> da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
> Enabled
> da3: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
> cd0 at ahc0 bus 0 target 5 lun 0
> cd0: <YAMAHA CRW2100S 1.0H> Removable CD-ROM SCSI-2 device
> cd0: 20.000MB/s transfers (20.000MHz, offset 7)
> cd0: cd present [65191 x 2048 byte records]
> Mounting root from ufs:/dev/da0s1a
> fxp0: Microcode loaded, int_delay: 1000 usec  bundle_max: 6
> fxp0: Microcode loaded, int_delay: 1000 usec  bundle_max: 6
> umass0: SanDisk Corporation ImageMate CF-SM, rev 1.10/1.00, addr 2
> GEOM: create disk da4 dp=3D0xc5e0cc50
> da4 at umass-sim0 bus 0 target 0 lun 0
> da4: <SanDisk ImageMate CF-SM 0100> Removable Direct Access SCSI-0 device
> da4: 1.000MB/s transfers
> da4: Attempt to query device size failed: NOT READY, Medium not present
> (da4:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
> (da4:umass-sim0:0:0:0): CAM Status: SCSI Status Error
> (da4:umass-sim0:0:0:0): SCSI Status: Check Condition
> (da4:umass-sim0:0:0:0): NOT READY asc:3a,0
> (da4:umass-sim0:0:0:0): Medium not present
> (da4:umass-sim0:0:0:0): Unretryable error
> Opened disk da4 -> 6
> (da4:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
> (da4:umass-sim0:0:0:0): CAM Status: SCSI Status Error
> (da4:umass-sim0:0:0:0): SCSI Status: Check Condition
> (da4:umass-sim0:0:0:0): NOT READY asc:3a,0
> (da4:umass-sim0:0:0:0): Medium not present
> (da4:umass-sim0:0:0:0): Unretryable error
> Opened disk da4 -> 6
> GEOM: create disk da5 dp=3D0xc5e5b850
> da5 at umass-sim0 bus 0 target 0 lun 1
> da5: <SanDisk ImageMate CF-SM 0100> Removable Direct Access SCSI-0 device
> da5: 1.000MB/s transfers
> da5: Attempt to query device size failed: NOT READY, Medium not present
> (da5:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0
> (da5:umass-sim0:0:0:1): CAM Status: SCSI Status Error
> (da5:umass-sim0:0:0:1): SCSI Status: Check Condition
> (da5:umass-sim0:0:0:1): NOT READY asc:3a,0
> (da5:umass-sim0:0:0:1): Medium not present
> (da5:umass-sim0:0:0:1): Unretryable error
> Opened disk da5 -> 6
> (da5:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0
> (da5:umass-sim0:0:0:1): CAM Status: SCSI Status Error
> (da5:umass-sim0:0:0:1): SCSI Status: Check Condition
> (da5:umass-sim0:0:0:1): NOT READY asc:3a,0
> (da5:umass-sim0:0:0:1): Medium not present
> (da5:umass-sim0:0:0:1): Unretryable error
> Opened disk da5 -> 6

=2D --=20

John R. Shannon
john@johnrshannon.com
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iEYEARECAAYFAj/1w1YACgkQOKbCxya4HYtcpgCcCQVzSeQng9OqnfR+Qro/4DPi
2vMAmwb0EetFJg9R3WN0hFi6BWWmorbv
=3DOlUc
=2D----END PGP SIGNATURE-----

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 16:01:13 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A2C2016A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 16:01:13 -0800 (PST)
Received: from ns.ixx.ru (ixx.ru [80.255.136.106])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4C16743D39
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 16:01:12 -0800 (PST)	(envelope-from km@ixx.ru)
Received: from kocatka.ircop.ru (KocaTKa.ircop.ru [217.28.82.25])
	by ns.ixx.ru (Postfix) with SMTP id 0FD252176
	for <freebsd-hardware@freebsd.org>;
	Sat,  3 Jan 2004 07:00:58 +0700 (KRAT)
Date: Sat, 3 Jan 2004 07:01:11 +0700
From: Kirill Pushkaryov <km@ixx.ru>
To: freebsd-hardware@freebsd.org
Message-Id: <20040103070111.248d5556.km@ixx.ru>
X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i386-unknown-freebsd5.1)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: onboard soundcard problem (SiS 7012)
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Jan 2004 00:01:13 -0000

Hello!

I apologize if such problem have been discussed here already, but in
mailing list archive I've found no solution for it.

I've got Asus P4S800 (SiS 648FX chipset) motherboard and met some
problems with its' onboard soundcard on FreeBSD 5.1-RELEASE (i386).

The card is SiS7012 PCI Audio Accelerator with ADI AD1980 AC'97 Codec.

Symptoms: despite of correct device detection by kernel no sound can be
produced through it (I've tried mpg123 and amp mpeg players). Even "echo
"some stuff" > /dev/dsp" produces no clicks or tones.

I've compiled my kernel with following devices:
device          pcm
device          midi
device          seq

Device files have been automatically created:
audio0.0
audio0.1
dsp0.0
dsp0.1
dspW0.0
dspW0.1
dspr0.0
mixer0

cat /dev/sndstat
FreeBSD Audio Driver (newpcm) Installed devices: pcm0:
<SiS 7012> at io 0xa400, 0xa000 irq 12 bufsz 16384 (1p/1r/0v channels
duplex default)

The device itself is detected on boot correctly as I see:
pcm0: <SiS 7012> port 0xa000-0xa07f, 0xa400-0xa4ff irq 12 at device 2.7
on pci0
pcm0: <Analog Devices AD1980 AC97 Codec>

"pciconf -lv" yields:
pcm0@pci0:2:7:  class=0x040100 card=0x80b01043 chip=0x70121039 rev=0xa0
hdr=0x00
    vendor   = 'Silicon Integrated Systems (SiS)'
    device   = 'SiS7012 PCI Audio Accelerator'
    class    = multimedia
    subclass = audio

mixer levels are set to 75

I know it maybe looks very strange, but I have sound under Windows. Can anybody advise me how to solve this problem or give some
references?

-- 
WBR, Kirill Pushkaryov		mailto:km@ixx.ru

From owner-freebsd-hardware@FreeBSD.ORG  Fri Jan  2 18:22:32 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D3CAF16A4CE
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 18:22:32 -0800 (PST)
Received: from smtp.covadmail.net (mx05.covadmail.net [63.65.120.65])
	by mx1.FreeBSD.org (Postfix) with SMTP id 4CA8443D49
	for <freebsd-hardware@freebsd.org>;
	Fri,  2 Jan 2004 18:22:31 -0800 (PST)
	(envelope-from strick@covad.net)
Received: (covad.net 8957 invoked from network); 3 Jan 2004 02:22:25 -0000
Received: from unknown (HELO covad.net) (strick@covad.net@67.101.99.81)
  by sun-qmail10 with SMTP; 3 Jan 2004 02:22:25 -0000
Message-ID: <3FF62760.1030302@covad.net>
Date: Fri, 02 Jan 2004 18:22:24 -0800
From: Dan Strick <strick@covad.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: d.ortiz@in.ilimit.es, freebsd-hardware@freebsd.org,
	strick@covad.net
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: atacontrol/udma
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Jan 2004 02:22:33 -0000

On Fri, 2 Jan 2004, Daniel Ortiz wrote:
 >>
 > I've a 'tyan i875p (s5102)' motherboard (with SATA 150), with a FreeBSD
 > 4.9-STABLE installed, the kernel detects the hardware fine.
 > The cable it's a fully working serial ata cable.
 >
 > ...
 >
 > But atacontrol always says me that it uses UDMA33 instead of SATA-150 or
 > other (I can't set UDMA66/100/133/150), in bios I tried to use legacy,
 > combined and enhaced modes but always work in UDMA33.
 >
 > ad0: DMA limited to UDMA33, non-ATA66 cable or device
 > ad1: DMA limited to UDMA33, non-ATA66 cable or device
 >
 > Iozone, bonnie and bonnie++ always report a maximum transfer of
 > 32MB/Sec.
 >
 > The question is: How I can set the transfer to any other UDMA? FreeBSD
 > detects ther hardware but I can't use that features without ATAng? Any
 > patch/solution/idea?
 >>

The 4.9-STABLE driver does not particularly understand Serial ATA, but
this is not a problem here.  If the driver configures your SATA drive
for any kind of dma (e.g. UDMA33), your particular SATA controller (on
the ICH5 chip in the Intel 875P cpu support chipset) will do dma at
SATA150 dma rates.

I don't know why your I/O benchmarks report only 32 MB/sec.  Perhaps
this is natural for these benchmarks and your particular drives.
You might try "dd if=/dev/ad0 of=/dev/null bs=128k" while running
"iostat 5".  (The 128k buffer size may be necessary.)  I get about
56 MB/sec even though the driver thinks it has configured the drive
for UDMA33.

Dan Strick
strick@covad.net


From owner-freebsd-hardware@FreeBSD.ORG  Sat Jan  3 16:53:55 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9EDF316A4CE
	for <freebsd-hardware@freebsd.org>;
	Sat,  3 Jan 2004 16:53:55 -0800 (PST)
Received: from smtp.easystreet.com (smtp.easystreet.com [206.26.36.40])
	by mx1.FreeBSD.org (Postfix) with ESMTP id ADE4443D55
	for <freebsd-hardware@freebsd.org>;
	Sat,  3 Jan 2004 16:53:54 -0800 (PST)
	(envelope-from tashchuk@easystreet.com)
Received: from easystreet.com (dsl-209-162-218-66.dsl.easystreet.com
	[209.162.218.66])	by smtp.easystreet.com (Postfix) with ESMTP
	id AAD78845F5D; Sat,  3 Jan 2004 16:53:57 -0800 (PST)
Message-ID: <3FF76457.4070700@easystreet.com>
Date: Sat, 03 Jan 2004 16:54:47 -0800
From: Bohdan Tashchuk <tashchuk@easystreet.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.6b) Gecko/20031208
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-hardware@freebsd.org
References: <3FF62760.1030302@covad.net>
In-Reply-To: <3FF62760.1030302@covad.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: Dan Strick <strick@covad.net>
cc: d.ortiz@in.ilimit.es
Subject: Re: atacontrol/udma
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Jan 2004 00:53:55 -0000

Dan Strick wrote:

> I don't know why your I/O benchmarks report only 32 MB/sec.  Perhaps
> this is natural for these benchmarks and your particular drives.
> You might try "dd if=/dev/ad0 of=/dev/null bs=128k" while running
> "iostat 5".  (The 128k buffer size may be necessary.)  I get about
> 56 MB/sec even though the driver thinks it has configured the drive
> for UDMA33.

This might not be related to original problem, but I've seen an approx 
2:1 disk transfer speed ratio on various IDE drives from outer tracks to 
inner tracks.

On the outside I've seen close to 60 MB/sec using dd but this slows to 
about 30 MB/sec on inner tracks.

Also in my experience with FreeBSD 4.x it IS necessary to set a buffer 
size when using dd. The default is very small. But setting something 
larger than the 128k max of raw IDE, for example bs=1024k, seems to be OK.