From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 1 02:53:07 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 275B816A403
for <freebsd-hardware@freebsd.org>;
Sun, 1 Oct 2006 02:53:07 +0000 (UTC)
(envelope-from youngbloodbenny@gmail.com)
Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.235])
by mx1.FreeBSD.org (Postfix) with ESMTP id 831A043D45
for <freebsd-hardware@freebsd.org>;
Sun, 1 Oct 2006 02:53:06 +0000 (GMT)
(envelope-from youngbloodbenny@gmail.com)
Received: by qb-out-0506.google.com with SMTP id a10so466466qbd
for <freebsd-hardware@freebsd.org>;
Sat, 30 Sep 2006 19:53:05 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:user-agent:date:subject:from:to:message-id:thread-topic:thread-index:mime-version:content-type:content-transfer-encoding;
b=o2x/Gg8iE46Zow1Oi9cYNYs3rklvtsL9JiEUUpP0sEO7jN4BrW1pOuzfXZkIdI/zihcVDVJtAcTvh6TtZXbhgr5dNmP9MQZPbAlnbnpiV71VgxVj0ct2/2pIn6Ll4eFqE8L9KfRiBo4FsVb+Wfl/jUN5UFDxNv0sS+cVAxYVHsM=
Received: by 10.70.87.9 with SMTP id k9mr3774353wxb;
Sat, 30 Sep 2006 19:53:04 -0700 (PDT)
Received: from ?192.168.1.102? ( [24.126.195.232])
by mx.gmail.com with ESMTP id 15sm78012wrl.2006.09.30.19.53.04;
Sat, 30 Sep 2006 19:53:04 -0700 (PDT)
User-Agent: Microsoft-Entourage/11.2.3.060209
Date: Sun, 01 Oct 2006 09:51:14 +0700
From: Benny Youngblood <youngbloodbenny@gmail.com>
To: "freebsd-hardware@freebsd.org" <freebsd-hardware@freebsd.org>
Message-ID: <C1454012.3ADC3%youngbloodbenny@gmail.com>
Thread-Topic: http://www.networkinghardware.net
Thread-Index: AcblBHV2s9t8QlD3EduHuwAUURZ9nA==
Mime-version: 1.0
Content-type: text/plain;
charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: http://www.networkinghardware.net
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 01 Oct 2006 02:53:07 -0000
http://www.networkinghardware.net
This is a great site for networking hardware
From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 1 05:34:08 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 8FF0116ABE0
for <freebsd-hardware@freebsd.org>;
Sun, 1 Oct 2006 05:31:56 +0000 (UTC) (envelope-from randy@psg.com)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by mx1.FreeBSD.org (Postfix) with ESMTP id 4AFCC43D5C
for <freebsd-hardware@freebsd.org>;
Sun, 1 Oct 2006 05:31:54 +0000 (GMT) (envelope-from randy@psg.com)
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
by rip.psg.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.62 (FreeBSD)) (envelope-from <randy@psg.com>)
id 1GTtvd-000COT-Ev; Sun, 01 Oct 2006 05:31:53 +0000
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
by roam.psg.com with esmtp (Exim 4.63 (FreeBSD))
(envelope-from <randy@psg.com>)
id 1GToMa-0002Iz-Es; Sat, 30 Sep 2006 13:35:20 -1000
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17694.65335.705182.734733@roam.psg.com>
Date: Sat, 30 Sep 2006 13:35:19 -1000
To: Benny Youngblood <youngbloodbenny@gmail.com>
References: <C1454012.3ADC3%youngbloodbenny@gmail.com>
Cc: "freebsd-hardware@freebsd.org" <freebsd-hardware@freebsd.org>
Subject: Re: http://www.networkinghardware.net
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 01 Oct 2006 05:34:08 -0000
> This is a great site for networking hardware
if you like doing business with spammers
From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 3 05:54:51 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 F00C316A403
for <freebsd-hardware@freebsd.org>;
Tue, 3 Oct 2006 05:54:50 +0000 (UTC) (envelope-from richw@richw.org)
Received: from smtp3.stanford.edu (smtp3.Stanford.EDU [171.67.20.26])
by mx1.FreeBSD.org (Postfix) with ESMTP id 8CE0A43D45
for <freebsd-hardware@freebsd.org>;
Tue, 3 Oct 2006 05:54:50 +0000 (GMT) (envelope-from richw@richw.org)
Received: from smtp3.stanford.edu (localhost.localdomain [127.0.0.1])
by localhost (Postfix) with SMTP id 197CB4C529
for <freebsd-hardware@freebsd.org>;
Mon, 2 Oct 2006 22:54:50 -0700 (PDT)
Received: from whodunit.richw.org (SW-90-716-276-1.Stanford.EDU
[171.66.155.243])
by smtp3.stanford.edu (Postfix) with ESMTP id D92944C494
for <freebsd-hardware@freebsd.org>;
Mon, 2 Oct 2006 22:54:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
by whodunit.richw.org (Postfix) with ESMTP id A06573C36D;
Mon, 2 Oct 2006 22:54:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at richw.org
Received: from whodunit.richw.org ([127.0.0.1])
by localhost (whodunit.richw.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id lgb+t6LokbEz; Mon, 2 Oct 2006 22:54:48 -0700 (PDT)
Received: from [172.29.0.21] (evilempire.richw.org [172.29.0.21])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "evilempire.richw.org", Issuer "richw.org" (verified OK))
(Authenticated sender: richw)
by whodunit.richw.org (Postfix) with ESMTP id B3E2B3C36B;
Mon, 2 Oct 2006 22:54:48 -0700 (PDT)
Date: Mon, 02 Oct 2006 22:54:48 -0700
From: Rich Wales <richw@richw.org>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: freebsd-hardware@freebsd.org
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <20061003055448.B3E2B3C36B@whodunit.richw.org>
Subject: Re: SATA-hdd or SATA-controller trouble.
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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: Tue, 03 Oct 2006 05:54:51 -0000
"Anton" wrote:
>> Aug 21 18:46:27 nrr kernel: ad4: TIMEOUT - READ_DMA retrying (2 retries left) LBA=344654303
>> Aug 21 18:46:32 nrr kernel: ad4: FAILURE - ATA_IDENTIFY timed out
>> Aug 21 18:46:37 nrr kernel: ad4: FAILURE - ATA_IDENTIFY timed out
>> Aug 21 18:46:37 nrr kernel: ad4: WARNING - removed from configuration
>> Aug 21 18:46:37 nrr kernel: ata2-master: FAILURE - READ_DMA timed out
"Veronica" replied:
> I have had similar messages when my ATA cable was damaged. So I suggest
> replacing your cable.
I've been seeing similar problems to Anton, with brand-new SATA cables that
are definitely not damaged. (Note that Anton was talking about a SATA disk,
with a completely different kind of data cable from old ATA drives.)
Veronica continued:
> Also you might want to check the temperature of the disk using the
> "smartmontools" utility from freebsd-ports. Harddrives should always
> be kept very cool < 40 degrees if possible. A higher risk of data loss
> and/or lower lifespan could be the result of a higher temperature.
> Smartmontools can also run self-tests (short or long ones) to check for
> problems with your drive.
Although it's possible that Anton could be having hardware problems due to
overheating or other drive flakiness, there have been lots of reports of
timeout problems with SATA drives on Promise controllers under heavy I/O
load, from many people, for quite some time now, and I would be surprised
if they were all due to overheating.
I'm currently running a "dd if=/dev/adXXX of=/dev/null bs=64k conv=noerror"
command on each of my two Seagate 300GB SATA drives simultaneously (with
"adXXX" replaced by the real drive device name in each case). I've got the
case open, with a large external fan blowing air onto the drives. Running
"smartctl -a /dev/adXXX" on each drive shows the temperature in each drive
to be around 35C. Earlier self-tests on both drives finished successfully.
Nevertheless, I'm seeing a bunch of timeout problems reported on both drives.
Something is messed up -- maybe in the Promise controller, maybe in the
FreeBSD driver, or (I'll admit for the sake of completeness) maybe in the
drives or elsewhere in the system. And as I said, lots of people on the
net have reported this problem, but no one (so far) has confessed to having
a clue as to what is causing it or how to fix it.
I'm running 6.1-RELEASE-p9 on an old 800-MHz Athlon (original "Slot A" CPU
type), in a DTK VAM-0070 motherboard. I've seen other people, though,
report this problem with much newer hardware.
Rich Wales
Palo Alto, CA, USA
richw@richw.org
http://www.richw.org
From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 3 12:02:40 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 D568A16A403
for <freebsd-hardware@freebsd.org>;
Tue, 3 Oct 2006 12:02:40 +0000 (UTC)
(envelope-from etc@fluffles.net)
Received: from auriate.fluffles.net (a83-68-3-169.adsl.cistron.nl
[83.68.3.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74DB643D49
for <freebsd-hardware@freebsd.org>;
Tue, 3 Oct 2006 12:02:40 +0000 (GMT)
(envelope-from etc@fluffles.net)
Received: from destiny ([10.0.0.21])
by auriate.fluffles.net with esmtpa (Exim 4.63 (FreeBSD))
(envelope-from <etc@fluffles.net>)
id 1GUiys-0000Bg-QH; Tue, 03 Oct 2006 14:02:38 +0200
Message-ID: <45225139.1010602@fluffles.net>
Date: Tue, 03 Oct 2006 14:02:01 +0200
From: Fluffles <etc@fluffles.net>
User-Agent: Thunderbird 1.5.0.7 (X11/20060917)
MIME-Version: 1.0
To: Rich Wales <richw@richw.org>, freebsd-hardware@freebsd.org
References: <20061003055448.B3E2B3C36B@whodunit.richw.org>
In-Reply-To: <20061003055448.B3E2B3C36B@whodunit.richw.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc:
Subject: Re: SATA-hdd or SATA-controller trouble.
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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: Tue, 03 Oct 2006 12:02:40 -0000
Rich Wales wrote:
> Although it's possible that Anton could be having hardware problems due to
> overheating or other drive flakiness, there have been lots of reports of
> timeout problems with SATA drives on Promise controllers under heavy I/O
> load, from many people, for quite some time now, and I would be surprised
> if they were all due to overheating.
>
Then it seems that you don't have a hardware problem but a software
problem; i always try to rule out any hardware problems first. That
includes a memory test (like memtest86). It's all too frustrating trying
to isolate a bug which eventually was hardware-related.
But it seems you have a driver problem indeed. All i can say is that i
have no problems with my onboard Promise controller; although its not
processing terribly much data. A different controller and/or software
RAID might be a solution/workaround.
- Veronica
From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 3 18:30:59 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 3C72C16A407;
Tue, 3 Oct 2006 18:30:59 +0000 (UTC)
(envelope-from dking@ketralnis.com)
Received: from ketralnis.com (melchoir.ketralnis.com [68.183.67.83])
by mx1.FreeBSD.org (Postfix) with ESMTP id BA28F43D45;
Tue, 3 Oct 2006 18:30:58 +0000 (GMT)
(envelope-from dking@ketralnis.com)
Received: from [10.0.0.237] (ayla.eth.int.ketralnis.com [10.0.0.237])
(authenticated bits=0)
by ketralnis.com (8.13.6/8.13.6) with ESMTP id k93IUwsd060559
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
Tue, 3 Oct 2006 11:30:58 -0700 (PDT)
(envelope-from dking@ketralnis.com)
In-Reply-To: <83ABA1D4-6451-461D-BB1B-5B9D0333B647@ketralnis.com>
References: <3692C07B-CCCC-4756-9B33-6DA724481FF2@ketralnis.com>
<000f01c6d033$3f447b80$bdcd7280$@com>
<68AD5D02-275C-43F0-B0DB-174EDD53702F@ketralnis.com>
<200609042230.51646.soralx@cydem.org>
<15F475AB-1304-4B1B-9B71-B874D237173B@ketralnis.com>
<83ABA1D4-6451-461D-BB1B-5B9D0333B647@ketralnis.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <59E3CE51-5926-42C8-AE34-4D2B9DFF1935@ketralnis.com>
Content-Transfer-Encoding: 7bit
From: David King <dking@ketralnis.com>
Date: Tue, 3 Oct 2006 11:30:51 -0700
To: freebsd-hardware@freebsd.org
X-Mailer: Apple Mail (2.752.3)
Cc: freebsd-smp@freebsd.org
Subject: Re: Quiet computer
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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: Tue, 03 Oct 2006 18:30:59 -0000
>>>> Yes, the Via's aren't the most performant, though. They would be
>>>> fine
>>>> for my purposes if they were slow but dual-core, unfortunately they
>>>> are just slow. I'm not looking for a game machine, though, I'm
>>> There is a dual-core version as well. I already mentioned that,
>>> AFAIR.
>>> http://www.via.com.tw/en/products/mainboards/mini_itx/vt_310dp/
>> Would you happen to know of anyone shipping systems with these
>> boards?
>> I can build one but it would be nice to pay someone else to do it
>> instead :)
> So I broke down and bought one of those boards. Does anyone on the
> list own one? Were there any initial setup difficulties with it?
> Does FreeBSD pick up the crypto hardware and second processor
> without any trouble?
For the archives, the VIA EPIA VT-310DP (<http://www.via.com.tw/en/
products/mainboards/mini_itx/vt_310dp/>) works *great* with FreeBSD
6.1. It's a dual-1GHz Via motherboard. The second processor is picked
up without trouble, and its padlock cryptography acceleration works,
or at least /dev/crypto is created with "device crypto" and "device
cryptodev" in the kernel config.
I didn't have to do anything special to get these things detected
except for the kernel config. In fact, I pulled a hard drive out of
another system and put it in here and it booted right up.
My dmesg is below.
FreeBSD 6.1-RELEASE-p7 #3: Fri Sep 29 21:45:34 PDT 2006
root@<censored>:/usr/obj/usr/src/sys/<censored>
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: VIA C3 Nehemiah+RNG+ACE (997.17-MHz 686-class CPU)
Origin = "CentaurHauls" Id = 0x69a Stepping = 10
Features=0x381ba3f<FPU,VME,DE,PSE,TSC,MSR,APIC,SEP,MTRR,PGE,CMOV,PAT,MMX
,FXSR,SSE>
real memory = 1054736384 (1005 MB)
avail memory = 1023025152 (975 MB)
ACPI APIC Table: <CN400 AWRDACPI>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0: Changing APIC ID to 2
ioapic0 <Version 0.3> irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: <CN400 AWRDACPI> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
agp0: <VIA PM800/PN800/PM880/PN880 host to PCI bridge> mem
0xe8000000-0xefffffff at device 0.0 on pci0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
wi0: <Intersil Prism2.5> mem 0xf6021000-0xf6021fff irq 16 at device
8.0 on pci0
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary (1.0.7), Station (1.3.6)
wi0: Ethernet address: 00:09:5b:40:b2:9f
fxp0: <Intel 82551 Pro/100 Ethernet> port 0xe000-0xe03f mem
0xf6020000-0xf6020fff,0xf6000000-0xf601ffff irq 17 at device 9.0 on pci0
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:e0:81:59:a3:1c
vge0: <VIA Networking Gigabit Ethernet> port 0xd000-0xd0ff mem
0xf6022000-0xf60220ff irq 18 at device 10.0 on pci0
miibus1: <MII bus> on vge0
ciphy0: <Cicada CS8201 10/100/1000TX PHY> on miibus1
ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
vge0: Ethernet address: 00:e0:81:59:a3:1a
atapci0: <VIA 8237 UDMA133 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe100-0xe10f at device 15.0 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
uhci0: <VIA 83C572 USB controller> port 0xdc00-0xdc1f irq 21 at
device 16.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xdd00-0xdd1f irq 21 at
device 16.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <VIA 83C572 USB controller> port 0xde00-0xde1f irq 21 at
device 16.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: <VIA 83C572 USB controller> on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3: <VIA 83C572 USB controller> port 0xdf00-0xdf1f irq 21 at
device 16.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <VIA 83C572 USB controller> on uhci3
usb3: USB revision 1.0
uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0: <VIA VT6202 USB 2.0 controller> mem 0xf6023000-0xf60230ff irq
21 at device 16.4 on pci0
ehci0: [GIANT-LOCKED]
usb4: waiting for BIOS to give up control
usb4: timed out waiting for BIOS
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4: <VIA VT6202 USB 2.0 controller> on ehci0
usb4: USB revision 2.0
uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
isab0: <PCI-ISA bridge> at device 17.0 on pci0
isa0: <ISA bus> on isab0
pci0: <multimedia, audio> at device 17.5 (no driver attached)
vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xd800-0xd8ff mem
0xf6024000-0xf60240ff irq 23 at device 18.0 on pci0
miibus2: <MII bus> on vr0
ukphy0: <Generic IEEE 802.3u media interface> on miibus2
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr0: Ethernet address: 00:e0:81:59:a3:1b
acpi_tz0: <Thermal Zone> on acpi0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10
on acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xef000-0xeffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on
isa0
Timecounters tick every 1.000 msec
Fast IPsec: Initialized Security Association Processing.
ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding
enabled, default to deny, logging limited to 10 packets/entry by default
ad0: 19569MB <WDC WD205AA-00BAA0 10.09K11> at ata0-master UDMA66
ad1: 152627MB <WDC WD1600JB-00GVA0 08.02D08> at ata0-slave UDMA100
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad0s1a
vge0: link state changed to UP
From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 4 11:55:35 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 E8B1516A415;
Wed, 4 Oct 2006 11:55:35 +0000 (UTC)
(envelope-from andymac@bullseye.apana.org.au)
Received: from smtp3.adl2.internode.on.net (smtp3.adl2.internode.on.net
[203.16.214.203])
by mx1.FreeBSD.org (Postfix) with ESMTP id 974BB43D7C;
Wed, 4 Oct 2006 11:55:17 +0000 (GMT)
(envelope-from andymac@bullseye.apana.org.au)
Received: from bullseye.apana.org.au (ppp58-48.lns1.cbr1.internode.on.net
[59.167.58.48])
by smtp3.adl2.internode.on.net (8.13.6/8.13.5) with ESMTP id
k94BtFUu011354; Wed, 4 Oct 2006 21:25:15 +0930 (CST)
(envelope-from andymac@bullseye.apana.org.au)
Received: from [192.168.63.10] (tenring.andymac.org [192.168.63.10])
by bullseye.apana.org.au (8.13.6/8.13.6) with ESMTP id k94Btco6042026;
Wed, 4 Oct 2006 21:55:39 +1000 (EST)
(envelope-from andymac@bullseye.andymac.org)
Message-ID: <4523937B.8090202@bullseye.andymac.org>
Date: Wed, 04 Oct 2006 21:56:59 +1100
From: Andrew MacIntyre <andymac@bullseye.apana.org.au>
User-Agent: Thunderbird 1.5.0.7 (OS/2/20060915)
MIME-Version: 1.0
To: freebsd-hardware@freebsd.org
References: <3692C07B-CCCC-4756-9B33-6DA724481FF2@ketralnis.com> <000f01c6d033$3f447b80$bdcd7280$@com> <68AD5D02-275C-43F0-B0DB-174EDD53702F@ketralnis.com> <200609042230.51646.soralx@cydem.org> <15F475AB-1304-4B1B-9B71-B874D237173B@ketralnis.com> <83ABA1D4-6451-461D-BB1B-5B9D0333B647@ketralnis.com>
<59E3CE51-5926-42C8-AE34-4D2B9DFF1935@ketralnis.com>
In-Reply-To: <59E3CE51-5926-42C8-AE34-4D2B9DFF1935@ketralnis.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-smp@freebsd.org
Subject: Re: Quiet computer
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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: Wed, 04 Oct 2006 11:55:36 -0000
David King wrote:
> For the archives, the VIA EPIA VT-310DP
> (<http://www.via.com.tw/en/products/mainboards/mini_itx/vt_310dp/>)
> works *great* with FreeBSD 6.1. It's a dual-1GHz Via motherboard. The
> second processor is picked up without trouble, and its padlock
> cryptography acceleration works, or at least /dev/crypto is created with
> "device crypto" and "device cryptodev" in the kernel config.
How successfully does it meet your requirements for a quiet system? (as I
think I read that both CPUs are actively cooled...)
--
-------------------------------------------------------------------------
Andrew I MacIntyre "These thoughts are mine alone..."
E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370
andymac@pcug.org.au (alt) | Belconnen ACT 2616
Web: http://www.andymac.org/ | Australia
From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 4 13:23:10 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 8A83B16A47E;
Wed, 4 Oct 2006 13:23:10 +0000 (UTC)
(envelope-from CoryStacyg@arcor-ip.net)
Received: from arcor-ip.net (dslb-088-073-196-004.pools.arcor-ip.net
[88.73.196.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 4D10343D5A;
Wed, 4 Oct 2006 13:23:09 +0000 (GMT)
(envelope-from CoryStacyg@arcor-ip.net)
Message-Id: <91397862771.0774185@arcor-ip.net>
From: "Jonathan Warren" <CoryStacyg@arcor-ip.net>
To: <freebsd-hardware-unsubscribe@freebsd.org>, <freebsd-hardware@freebsd.org>
Date: Wed, 04 Oct 2006 15:23:08 +0100
MIME-Version: 1.0
Cc: freebsd-help@freebsd.org, freebsd-hubs-owner@freebsd.org
Subject: cassandra cantonesef
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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: Wed, 04 Oct 2006 13:23:10 -0000
Energy Prices are near all time low, This is the best time to lock in a quality energy stock
Introducing : WBRS
Exchange Pinksheets
Price: 0.05
3 Day Estimated : .50 ( +1000%)
WILD BRUSH MAKES A MOVE!
Wild Brush Acquires Additional Powder River Oil & Gas Lease.
Who is Wild Brush?
Wild Brush Energy is a diversified energy company whose primary goal is to identify and develop Oil & Coalbed Methane sites within the State of Wyoming. In addition, Wild Brush Energy continues to evaluate clean air alternative energy producing technologies such as Wind Power. Wild Brush trades in the U.S. under the symbol "WBRS."
ADD THIS ENERGY STOCK TO YOUR LIST AND WATCH IT TRADE CLOSELY ON WEDNESDAY OCTOBER 4!
Get In NOW !!!
Up one side and down the other.
The season of goodwill.
A snail's pace.
Watered down.
The stronger the breeze the stronger the trees.
Tossed around like a hot potato.
When you get lemons, make lemonade.(When life gives you scraps make quilts.)
Ugly as a mud fence.
Waking up with the chickens.
That's a whole new can of worms.
Were you born in a barn?
The sun will shine into our yard to.
When it rains it pours.
Salt of the Earth.
From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 4 16:17:26 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 4CEB316A4D2
for <freebsd-hardware@freebsd.org>;
Wed, 4 Oct 2006 16:17:26 +0000 (UTC)
(envelope-from dking@ketralnis.com)
Received: from ketralnis.com (melchoir.ketralnis.com [68.183.67.83])
by mx1.FreeBSD.org (Postfix) with ESMTP id EEE8F43D7B
for <freebsd-hardware@freebsd.org>;
Wed, 4 Oct 2006 16:17:22 +0000 (GMT)
(envelope-from dking@ketralnis.com)
Received: from [192.168.1.33] (pix.xythos.com [64.154.218.194])
(authenticated bits=0)
by ketralnis.com (8.13.6/8.13.6) with ESMTP id k94GHJYG011044
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
for <freebsd-hardware@freebsd.org>; Wed, 4 Oct 2006 09:17:20 -0700 (PDT)
(envelope-from dking@ketralnis.com)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <4523937B.8090202@bullseye.andymac.org>
References: <3692C07B-CCCC-4756-9B33-6DA724481FF2@ketralnis.com> <000f01c6d033$3f447b80$bdcd7280$@com> <68AD5D02-275C-43F0-B0DB-174EDD53702F@ketralnis.com> <200609042230.51646.soralx@cydem.org> <15F475AB-1304-4B1B-9B71-B874D237173B@ketralnis.com> <83ABA1D4-6451-461D-BB1B-5B9D0333B647@ketralnis.com>
<59E3CE51-5926-42C8-AE34-4D2B9DFF1935@ketralnis.com>
<4523937B.8090202@bullseye.andymac.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FB5B3795-2451-4A8B-95DD-BE6C215538CA@ketralnis.com>
Content-Transfer-Encoding: 7bit
From: David King <dking@ketralnis.com>
Date: Wed, 4 Oct 2006 07:50:30 -0700
To: freebsd-hardware@freebsd.org
X-Mailer: Apple Mail (2.752.3)
Subject: Re: Quiet computer
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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: Wed, 04 Oct 2006 16:17:26 -0000
>> For the archives, the VIA EPIA VT-310DP
>> (<http://www.via.com.tw/en/products/mainboards/mini_itx/vt_310dp/>)
>> works *great* with FreeBSD 6.1
> How successfully does it meet your requirements for a quiet system?
> (as I
> think I read that both CPUs are actively cooled...)
(moved to freebsd-hardware only)
So far, it doesn't, since the power supply fan on the case I bought
is pretty loud (well, quieter than the old system, but not yet quiet
enough). But the manual for the motherboard indicates that it can run
fanless, and it has temperature sensors and a BIOS feature to shut it
down after it hits a critical temperature, so after some fidgeting I
suspect that I'll be able to quiet it down completely.
From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 5 02:40:01 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 79C6616A407
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 02:40:01 +0000 (UTC)
(envelope-from soralx@cydem.org)
Received: from pd2mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net
[24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DF9643D49
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 02:40:00 +0000 (GMT)
(envelope-from soralx@cydem.org)
Received: from pd3mr6so.prod.shaw.ca (pd3mr6so-qfe3.prod.shaw.ca [10.0.141.21])
by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15
2004)) with ESMTP id <0J6N00JF1621W180@l-daemon> for
freebsd-hardware@freebsd.org; Wed, 04 Oct 2006 20:39:37 -0600 (MDT)
Received: from pn2ml8so.prod.shaw.ca ([10.0.121.152])
by pd3mr6so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01
(built Mar
15 2004)) with ESMTP id <0J6N00BO3621VST0@pd3mr6so.prod.shaw.ca> for
freebsd-hardware@freebsd.org; Wed, 04 Oct 2006 20:39:37 -0600 (MDT)
Received: from soralx.cydem.org ([24.87.27.3])
by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15
2004)) with ESMTP id <0J6N003PM620SGY0@l-daemon> for
freebsd-hardware@freebsd.org; Wed, 04 Oct 2006 20:39:37 -0600 (MDT)
Date: Wed, 04 Oct 2006 19:39:34 -0700
From: soralx@cydem.org
In-reply-to: <FB5B3795-2451-4A8B-95DD-BE6C215538CA@ketralnis.com>
To: freebsd-hardware@freebsd.org
Message-id: <200610041939.35376.soralx@cydem.org>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <3692C07B-CCCC-4756-9B33-6DA724481FF2@ketralnis.com>
<4523937B.8090202@bullseye.andymac.org>
<FB5B3795-2451-4A8B-95DD-BE6C215538CA@ketralnis.com>
User-Agent: KMail/1.9.1
Cc: dking@ketralnis.com
Subject: Re: Quiet computer
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 05 Oct 2006 02:40:01 -0000
> >> For the archives, the VIA EPIA VT-310DP
> >> (<http://www.via.com.tw/en/products/mainboards/mini_itx/vt_310dp/>)
> >> works *great* with FreeBSD 6.1
> > How successfully does it meet your requirements for a quiet system?
...and performance? (i.e., `ubench`) :) Also, just curious... can you
test the speed of crypto? Yes, want to gape at some large numbers ;)
> > (as I
> > think I read that both CPUs are actively cooled...)
>
> So far, it doesn't, since the power supply fan on the case I bought
> is pretty loud (well, quieter than the old system, but not yet quiet
> enough). But the manual for the motherboard indicates that it can run
> fanless, and it has temperature sensors and a BIOS feature to shut it
> down after it hits a critical temperature, so after some fidgeting I
> suspect that I'll be able to quiet it down completely.
You might wants to consider using a low-power 'brick'-type AC->DC
PSU (~90W?) and a DC-DC voltage converter that plugs directly into
a mainboard's power connector. This will be quite noiseless.
Really, I'm rather impressed with FreeBSD yet again. Such an exotic
hardware, and all works right away. Huge kudos to the developers :)
[SorAlx] ridin' VN1500-B2
From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 5 02:46:25 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 77B4B16A415
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 02:46:25 +0000 (UTC)
(envelope-from mureninc@gmail.com)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.229])
by mx1.FreeBSD.org (Postfix) with ESMTP id 4E06D43D58
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 02:46:24 +0000 (GMT)
(envelope-from mureninc@gmail.com)
Received: by wx-out-0506.google.com with SMTP id i27so372132wxd
for <freebsd-hardware@freebsd.org>;
Wed, 04 Oct 2006 19:46:23 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
b=jRwXUMhi1hFxIH3HQnxRUq4rrxyFVw3Q0JQ8ZRxZehrR1PUKZDNkWUub5cJpb2+tBi/rcRySGC+vxLuqFUnuEYAylDFcqucNRBZX58DXGq1xCR4QowEdBLfI2qLv4z/XJWGcq5KXS2QpQl2Lzpf1toXslQ5IRAQedNrrpVCsE7U=
Received: by 10.70.76.11 with SMTP id y11mr2263625wxa;
Wed, 04 Oct 2006 19:46:23 -0700 (PDT)
Received: by 10.70.36.16 with HTTP; Wed, 4 Oct 2006 19:46:23 -0700 (PDT)
Message-ID: <f34ca13c0610041946h7dfaa05cyf3296798b215405e@mail.gmail.com>
Date: Wed, 4 Oct 2006 22:46:23 -0400
From: "Constantine A. Murenin" <mureninc@gmail.com>
To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: majid.awad@intel.com
Subject: ipw(4) and iwi(4): Intel's Pro Wireless firmware licensing problems
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 05 Oct 2006 02:46:25 -0000
Hi,
My acquaintance with Unix started with FreeBSD, which I used for quite
a while before discovering OpenBSD. I now mostly use OpenBSD, and I
was wondering of how many FreeBSD users are aware about the licensing
restrictions of Intel Pro Wireless family of wireless adapters?
Why are none of the manual pages of FreeBSD say anything about why
Intel Wireless devices do not work by default?
http://www.freebsd.org/cgi/man.cgi?query=ipw
http://www.freebsd.org/cgi/man.cgi?query=iwi
If you are curious as to why things are the way they are, I suggest
that you check the problems that are described in the misc@openbsd.org
mailing list, and contact Intel people and say what you think about
their user-unfriendly policy in regards to Intel Pro Wireless
firmwares, which are REQUIRED to be loaded from the OS before the
device functions, i.e. the OS developers must be allowed to freely
distribute the firmware in order for the devices to work
out-of-the-box.
For some recent information about Intel being an Open Source Fraud,
see http://marc.theaimsgroup.com/?l=openbsd-misc&m=115960734026283&w=2.
Cheers,
Constantine.
From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 5 12:53:17 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 2D9F116A40F
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 12:53:17 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net
[66.23.211.162])
by mx1.FreeBSD.org (Postfix) with ESMTP id 391AD43D5D
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 12:53:12 +0000 (GMT) (envelope-from jhb@freebsd.org)
Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7])
(authenticated bits=0)
by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k95Cr703043407;
Thu, 5 Oct 2006 08:53:09 -0400 (EDT) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-hardware@freebsd.org
Date: Thu, 5 Oct 2006 08:52:58 -0400
User-Agent: KMail/1.9.1
References: <f34ca13c0610041946h7dfaa05cyf3296798b215405e@mail.gmail.com>
In-Reply-To: <f34ca13c0610041946h7dfaa05cyf3296798b215405e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610050852.58943.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]);
Thu, 05 Oct 2006 08:53:10 -0400 (EDT)
X-Virus-Scanned: ClamAV 0.88.3/1997/Wed Oct 4 11:20:43 2006 on
server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00
autolearn=ham version=3.1.3
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx
Cc: "Constantine A. Murenin" <mureninc@gmail.com>
Subject: Re: ipw(4) and iwi(4): Intel's Pro Wireless firmware licensing
problems
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 05 Oct 2006 12:53:17 -0000
On Wednesday 04 October 2006 22:46, Constantine A. Murenin wrote:
> Hi,
>
> My acquaintance with Unix started with FreeBSD, which I used for quite
> a while before discovering OpenBSD. I now mostly use OpenBSD, and I
> was wondering of how many FreeBSD users are aware about the licensing
> restrictions of Intel Pro Wireless family of wireless adapters?
>
> Why are none of the manual pages of FreeBSD say anything about why
> Intel Wireless devices do not work by default?
>
> http://www.freebsd.org/cgi/man.cgi?query=ipw
> http://www.freebsd.org/cgi/man.cgi?query=iwi
>
> If you are curious as to why things are the way they are, I suggest
> that you check the problems that are described in the misc@openbsd.org
> mailing list, and contact Intel people and say what you think about
> their user-unfriendly policy in regards to Intel Pro Wireless
> firmwares, which are REQUIRED to be loaded from the OS before the
> device functions, i.e. the OS developers must be allowed to freely
> distribute the firmware in order for the devices to work
> out-of-the-box.
>
> For some recent information about Intel being an Open Source Fraud,
> see http://marc.theaimsgroup.com/?l=openbsd-misc&m=115960734026283&w=2.
Probably because all you have to do is install a port and it works. :)
In FreeBSD installing a port isn't too difficult for users to do. However,
you might want to ask Theo why he complains about Intel not giving him a
license for one binary blob (Intel wireless firmware) but complains about
Atheros providing a binary blob that he can distribute. Seems a bit of a
contradiction to me. However, you probably won't make any headway with
that argument because the other side won't be using reason and logic.
I think in practice that the distinction between a HAL and firmware is
blurry at best. Both are pre-built software to drive hardware and provide
a simplified interface to software (i.e. OS) for managing the hardware.
The only difference is which portion of RAM that it lives (some RAM chip
on the device or in the RAM of the host computer) and that distinction
really isn't all that noteworthy. If it's some argument about HAL's
encroaching on space needed by the OS, note that firmware has to be in
host RAM as well so it can be uploaded. In fact, for iwi(4) and ipw(4)
the drivers keep it around all the time to handle suspend/resume. The
implementation detail of HAL vs firmware is really just a reflection of
design choices made by the hardware vendor in where to draw the line
between actual hardware vs software to provide their public interface to
system software. For a software guy to claim that firmware is ok but
HALs mostly just serves to display how ignorant said person is of how
things work over in hardware land IMHO.
At this point I've said way more than I probably should as I have actual
work that I need to be getting done. :)
--
John Baldwin
From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 5 16:36:54 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 DF44216A403
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 16:36:53 +0000 (UTC)
(envelope-from mureninc@gmail.com)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239])
by mx1.FreeBSD.org (Postfix) with ESMTP id E753343D7C
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 16:34:34 +0000 (GMT)
(envelope-from mureninc@gmail.com)
Received: by wx-out-0506.google.com with SMTP id i27so552559wxd
for <freebsd-hardware@freebsd.org>;
Thu, 05 Oct 2006 09:34:18 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
b=JVC1l8jfY8fYAm4ZHJyExRrAcdGWUi6Az4ODTfTp/2vbOx7jdW5xDj1sa8nSXc4FJybpI1DhLMmSde4Clje5T4S6todtIzCnlSNZX7WfjlgegO8AZ7iTvcwXn2ZbK6Kqd5O1dudZeN4vGHfthenCPw/jYsSZ7NaPtfhSohJCyt4=
Received: by 10.70.32.10 with SMTP id f10mr3530012wxf;
Thu, 05 Oct 2006 09:34:17 -0700 (PDT)
Received: by 10.70.36.16 with HTTP; Thu, 5 Oct 2006 09:34:17 -0700 (PDT)
Message-ID: <f34ca13c0610050934n35191e52p2b856224fcee9a12@mail.gmail.com>
Date: Thu, 5 Oct 2006 12:34:17 -0400
From: "Constantine A. Murenin" <mureninc@gmail.com>
To: "John Baldwin" <jhb@freebsd.org>
In-Reply-To: <200610050852.58943.jhb@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f34ca13c0610041946h7dfaa05cyf3296798b215405e@mail.gmail.com>
<200610050852.58943.jhb@freebsd.org>
Cc: freebsd-hardware@freebsd.org
Subject: Re: ipw(4) and iwi(4): Intel's Pro Wireless firmware licensing
problems
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 05 Oct 2006 16:36:54 -0000
On 05/10/06, John Baldwin <jhb@freebsd.org> wrote:
> On Wednesday 04 October 2006 22:46, Constantine A. Murenin wrote:
> > Hi,
> >
> > My acquaintance with Unix started with FreeBSD, which I used for quite
> > a while before discovering OpenBSD. I now mostly use OpenBSD, and I
> > was wondering of how many FreeBSD users are aware about the licensing
> > restrictions of Intel Pro Wireless family of wireless adapters?
> >
> > Why are none of the manual pages of FreeBSD say anything about why
> > Intel Wireless devices do not work by default?
> >
> > http://www.freebsd.org/cgi/man.cgi?query=ipw
> > http://www.freebsd.org/cgi/man.cgi?query=iwi
> >
> > If you are curious as to why things are the way they are, I suggest
> > that you check the problems that are described in the misc@openbsd.org
> > mailing list, and contact Intel people and say what you think about
> > their user-unfriendly policy in regards to Intel Pro Wireless
> > firmwares, which are REQUIRED to be loaded from the OS before the
> > device functions, i.e. the OS developers must be allowed to freely
> > distribute the firmware in order for the devices to work
> > out-of-the-box.
> >
> > For some recent information about Intel being an Open Source Fraud,
> > see http://marc.theaimsgroup.com/?l=openbsd-misc&m=115960734026283&w=2.
>
> Probably because all you have to do is install a port and it works. :)
Oh yeah, so I can install a port to the installation media, so that I
could setup wireless right away and install all ports that are not
present on the install CD off an ftp or http mirror? :)
> In FreeBSD installing a port isn't too difficult for users to do. However,
So is in OpenBSD, in fact, they've recently made it even easier with a
"-u" option, where "pkg_add -u" automatically updates all packages to
the newest versions, works out of the box, only PKG_PATH needs to be
set.
> you might want to ask Theo why he complains about Intel not giving him a
> license for one binary blob (Intel wireless firmware) but complains about
> Atheros providing a binary blob that he can distribute. Seems a bit of a
> contradiction to me. However, you probably won't make any headway with
> that argument because the other side won't be using reason and logic.
Are you being serious? The distinction is rather clear -- Intel's
firmware is processor and operating system independent and runs on the
wireless microprocessor, whereas Atheros' HAL module is
processor-dependent, and runs on the main CPU in kernel mode with
unlimited priviledges (correct me if I'm wrong). Clear distinction
here, IMHO.
> I think in practice that the distinction between a HAL and firmware is
> blurry at best. Both are pre-built software to drive hardware and provide
> a simplified interface to software (i.e. OS) for managing the hardware.
> The only difference is which portion of RAM that it lives (some RAM chip
> on the device or in the RAM of the host computer) and that distinction
> really isn't all that noteworthy. If it's some argument about HAL's
> encroaching on space needed by the OS, note that firmware has to be in
> host RAM as well so it can be uploaded. In fact, for iwi(4) and ipw(4)
> the drivers keep it around all the time to handle suspend/resume. The
> implementation detail of HAL vs firmware is really just a reflection of
> design choices made by the hardware vendor in where to draw the line
> between actual hardware vs software to provide their public interface to
> system software.
I think there is a huge difference here in what area of the RAM of the
host computer these binary blobs live: in the case of firmware, they
live in a non-executable read-only part of RAM, whereas with a binary
HAL module the situation is just the opposite. And this IS the
difference that should concern security-paranoid people.
Cheers,
Constantine.
From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 5 17:06:59 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 2FB9A16A47B
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 17:06:59 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net
[66.23.211.162])
by mx1.FreeBSD.org (Postfix) with ESMTP id 9DC0B43D5F
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 17:06:53 +0000 (GMT) (envelope-from jhb@freebsd.org)
Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1])
(authenticated bits=0)
by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k95H6nj2044892;
Thu, 5 Oct 2006 13:06:51 -0400 (EDT) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: "Constantine A. Murenin" <mureninc@gmail.com>
Date: Thu, 5 Oct 2006 13:06:58 -0400
User-Agent: KMail/1.9.1
References: <f34ca13c0610041946h7dfaa05cyf3296798b215405e@mail.gmail.com>
<200610050852.58943.jhb@freebsd.org>
<f34ca13c0610050934n35191e52p2b856224fcee9a12@mail.gmail.com>
In-Reply-To: <f34ca13c0610050934n35191e52p2b856224fcee9a12@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610051306.58843.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]);
Thu, 05 Oct 2006 13:06:52 -0400 (EDT)
X-Virus-Scanned: ClamAV 0.88.3/1998/Thu Oct 5 10:55:28 2006 on
server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00
autolearn=ham version=3.1.3
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx
Cc: freebsd-hardware@freebsd.org
Subject: Re: ipw(4) and iwi(4): Intel's Pro Wireless firmware licensing
problems
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 05 Oct 2006 17:06:59 -0000
On Thursday 05 October 2006 12:34, Constantine A. Murenin wrote:
> > you might want to ask Theo why he complains about Intel not giving him a
> > license for one binary blob (Intel wireless firmware) but complains about
> > Atheros providing a binary blob that he can distribute. Seems a bit of a
> > contradiction to me. However, you probably won't make any headway with
> > that argument because the other side won't be using reason and logic.
>
> Are you being serious? The distinction is rather clear -- Intel's
> firmware is processor and operating system independent and runs on the
> wireless microprocessor, whereas Atheros' HAL module is
> processor-dependent, and runs on the main CPU in kernel mode with
> unlimited priviledges (correct me if I'm wrong). Clear distinction
> here, IMHO.
You do realize that on a PCI bus each device (like iwi(4), ipw(4), etc.) is a
busmaster, so the firmware on the hardware can DMA to anywhere in physical
memory? (Well, on some archs you have an IOMMU to deal with that can make
that a bit more tricky, but on i386 and amd64 you don't have that to worry
about.) Thus, malicious firmware could engage in kernel object modification,
etc. If you're worried about reviewing the source for security bugs, then
that worry should be applied to firmware as well as HALs. Taking that
argument even further, you really want to review the source for firmware the
OS never touches as well (such as on RAID controllers, em(4), etc.) since it
still has unmitigated access to all of RAM in the machine. That's still a
bit safer than firmware loaded by the OS (easier to sneak in rogue firmware
that way as it's loaded more often). In fact, brining up ath(4) vs. iwi(4)
specifically: I happen to know the person who compiled the ath(4) HAL
personally and trust Sam quite a bit. I haven't the foggiest clue who wrote
or built or reviewed the iwi(4) firmware. Running iwi(4) (which I do) takes
significantly more "blind faith" for me than ath(4).
> > I think in practice that the distinction between a HAL and firmware is
> > blurry at best. Both are pre-built software to drive hardware and provide
> > a simplified interface to software (i.e. OS) for managing the hardware.
> > The only difference is which portion of RAM that it lives (some RAM chip
> > on the device or in the RAM of the host computer) and that distinction
> > really isn't all that noteworthy. If it's some argument about HAL's
> > encroaching on space needed by the OS, note that firmware has to be in
> > host RAM as well so it can be uploaded. In fact, for iwi(4) and ipw(4)
> > the drivers keep it around all the time to handle suspend/resume. The
> > implementation detail of HAL vs firmware is really just a reflection of
> > design choices made by the hardware vendor in where to draw the line
> > between actual hardware vs software to provide their public interface to
> > system software.
>
> I think there is a huge difference here in what area of the RAM of the
> host computer these binary blobs live: in the case of firmware, they
> live in a non-executable read-only part of RAM, whereas with a binary
> HAL module the situation is just the opposite. And this IS the
> difference that should concern security-paranoid people.
Actually, I think you aren't _as_ paranoid and underestimate the security
implications of binary firmware that is by and large untrusted.
--
John Baldwin
From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 5 17:35:58 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 21EF516A40F
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 17:35:58 +0000 (UTC)
(envelope-from dking@ketralnis.com)
Received: from ketralnis.com (melchoir.ketralnis.com [68.183.67.83])
by mx1.FreeBSD.org (Postfix) with ESMTP id 296BA43D58
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 17:35:54 +0000 (GMT)
(envelope-from dking@ketralnis.com)
Received: from [192.168.1.76] (pix.xythos.com [64.154.218.194])
(authenticated bits=0)
by ketralnis.com (8.13.6/8.13.6) with ESMTP id k95HZQSX050169
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
for <freebsd-hardware@freebsd.org>; Thu, 5 Oct 2006 10:35:28 -0700 (PDT)
(envelope-from dking@ketralnis.com)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <200610041939.35376.soralx@cydem.org>
References: <3692C07B-CCCC-4756-9B33-6DA724481FF2@ketralnis.com>
<4523937B.8090202@bullseye.andymac.org>
<FB5B3795-2451-4A8B-95DD-BE6C215538CA@ketralnis.com>
<200610041939.35376.soralx@cydem.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0431EB40-6AF8-49A6-9F87-0B707B1DDC94@ketralnis.com>
Content-Transfer-Encoding: 7bit
From: David King <dking@ketralnis.com>
Date: Thu, 5 Oct 2006 10:35:18 -0700
To: freebsd-hardware@freebsd.org
X-Mailer: Apple Mail (2.752.3)
Subject: Re: Quiet computer
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 05 Oct 2006 17:35:58 -0000
>>>> For the archives, the VIA EPIA VT-310DP
>>>> (<http://www.via.com.tw/en/products/mainboards/mini_itx/vt_310dp/>)
>>>> works *great* with FreeBSD 6.1
>>> How successfully does it meet your requirements for a quiet system?
> ...and performance? (i.e., `ubench`) :) Also, just curious... can you
> test the speed of crypto? Yes, want to gape at some large numbers ;)
I'll try to do a ubench tonight.
I'd love to test the speed of the crypto, but I'm not exactly sure
how, nor even test if it's actually being used e.g. by openssl. All
I've confirmed is whether /dev/crypto exists :) I'd like to make sure
that at the very least, Apache from ports, and OpenSSH and OpenSSL in
the base system are using it, and ideally that OpenSSL from ports is
using it too. I'm working on getting IPsec up and running, and I have
FAST_IPSEC in the kernel, so it *should* use it, but again, I can't
think of an easy way to confirm this other than watching the device
node for opens/reads/writes
> You might wants to consider using a low-power 'brick'-type AC->DC
> PSU (~90W?) and a DC-DC voltage converter that plugs directly into
> a mainboard's power connector. This will be quite noiseless.
Do you have any recommendations? Ideally it would mount on the case
(<http://www.logicsupply.com/product_info.php/products_id/134>) like
the current power supply does but I'm open to other options
From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 5 19:42:49 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 02B0816A40F
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 19:42:49 +0000 (UTC)
(envelope-from joel@its.washington.edu)
Received: from autobahn.its.washington.edu (autobahn.its.washington.edu
[128.95.29.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id B04D943D66
for <freebsd-hardware@freebsd.org>;
Thu, 5 Oct 2006 19:42:48 +0000 (GMT)
(envelope-from joel@its.washington.edu)
Received: from sidewalk (sidewalk.ee.washington.edu [128.95.28.6])
by autobahn.its.washington.edu (8.13.6/8.13.6) with ESMTP id
k95JgcbC043995
for <freebsd-hardware@freebsd.org>; Thu, 5 Oct 2006 12:42:38 -0700 (PDT)
Message-Id: <4.2.2.20061005114011.00c0acd0@localhost>
X-Sender: joel@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2
Date: Thu, 05 Oct 2006 12:42:33 -0700
To: freebsd-hardware@freebsd.org
From: Joel Bradbury <joel@its.washington.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-MailScanner:
X-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-4.777,
required 3.5, AWL, BAYES_00)
Subject: Dell E521 won't boot FreeBSD
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 05 Oct 2006 19:42:49 -0000
Well, it seemed like a good deal -- the new Dell E521 with an AMD 64 Athlon
3200+, 1Gb memory, for $400 should make a decent, cheap server. But
FreeBSD just won't boot on it. I tried Release 6.1 (both amd64 and i386
versions), as well as Releases 5.5 and 4.11. All give the same result when
trying to boot from the install cd:
With the usb keyboard plugged in, the boot gets to a "panic:
ohci-add-done: addr 0x3bef1ba0 not found", and then it tries to reboot again.
With the keyboard unplugged, the ohci error never appears, but the boot
gets to a point of recognizing the SATA drive, and then just hangs. Last
message: "ad4: 152587MB <SAMSUNG HD160JJ/P ZM100-34> at ata2-master SATA300"
Anyone have any ideas of anything to try? There's not much to change in
the BIOS settings.
Btw, the BIOS is version 1.0.1 (9/23/2006). The only version currently
available on the Dell site is version 1.0.0 (!).
Linux boots and runs fine. I guess I may have to go with that.
From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 6 03:00:41 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 E2E8D16A415
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 03:00:40 +0000 (UTC)
(envelope-from mureninc@gmail.com)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231])
by mx1.FreeBSD.org (Postfix) with ESMTP id 06A2243D45
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 03:00:39 +0000 (GMT)
(envelope-from mureninc@gmail.com)
Received: by wx-out-0506.google.com with SMTP id i27so707308wxd
for <freebsd-hardware@freebsd.org>;
Thu, 05 Oct 2006 20:00:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
b=Zf6M6mQGMsHQDk/M4RWTnaV5sBiIbyPLsnucR2sxS8Jls6KP1qDBmiHW5o+JyLr5W8OGWuB24YHWdPIwJTTZyhnkaK3QobPdJ1hZkVDHPr8x3IO+CV0hhdfQ5gIZN2cbMvDV2jsLSRb1zU6FMmF33rBCpezDvd7gbP07uufi37s=
Received: by 10.70.76.11 with SMTP id y11mr4423064wxa;
Thu, 05 Oct 2006 20:00:39 -0700 (PDT)
Received: by 10.70.36.16 with HTTP; Thu, 5 Oct 2006 20:00:39 -0700 (PDT)
Message-ID: <f34ca13c0610052000u3d1b2b64kcda29a5e8fa2a216@mail.gmail.com>
Date: Thu, 5 Oct 2006 23:00:39 -0400
From: "Constantine A. Murenin" <mureninc@gmail.com>
To: "John Baldwin" <jhb@freebsd.org>
In-Reply-To: <200610051306.58843.jhb@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f34ca13c0610041946h7dfaa05cyf3296798b215405e@mail.gmail.com>
<200610050852.58943.jhb@freebsd.org>
<f34ca13c0610050934n35191e52p2b856224fcee9a12@mail.gmail.com>
<200610051306.58843.jhb@freebsd.org>
Cc: freebsd-hardware@freebsd.org
Subject: Re: ipw(4) and iwi(4): Intel's Pro Wireless firmware licensing
problems
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 06 Oct 2006 03:00:41 -0000
On 05/10/06, John Baldwin <jhb@freebsd.org> wrote:
> On Thursday 05 October 2006 12:34, Constantine A. Murenin wrote:
> > > you might want to ask Theo why he complains about Intel not giving him a
> > > license for one binary blob (Intel wireless firmware) but complains about
> > > Atheros providing a binary blob that he can distribute. Seems a bit of a
> > > contradiction to me. However, you probably won't make any headway with
> > > that argument because the other side won't be using reason and logic.
> >
> > Are you being serious? The distinction is rather clear -- Intel's
> > firmware is processor and operating system independent and runs on the
> > wireless microprocessor, whereas Atheros' HAL module is
> > processor-dependent, and runs on the main CPU in kernel mode with
> > unlimited priviledges (correct me if I'm wrong). Clear distinction
> > here, IMHO.
>
> You do realize that on a PCI bus each device (like iwi(4), ipw(4), etc.) is a
> busmaster, so the firmware on the hardware can DMA to anywhere in physical
> memory? (Well, on some archs you have an IOMMU to deal with that can make
> that a bit more tricky, but on i386 and amd64 you don't have that to worry
> about.) Thus, malicious firmware could engage in kernel object modification,
> etc. If you're worried about reviewing the source for security bugs, then
> that worry should be applied to firmware as well as HALs. Taking that
> argument even further, you really want to review the source for firmware the
> OS never touches as well (such as on RAID controllers, em(4), etc.) since it
> still has unmitigated access to all of RAM in the machine. That's still a
> bit safer than firmware loaded by the OS (easier to sneak in rogue firmware
> that way as it's loaded more often).
Yes, world isn't perfect. But what is the probability that Intel
Firmware can possibly do something other than a DoS attack on the host
machine, as the machine may have ANY possible operating system on ANY
platform?
When you have a binary HAL, it's specific to the platform, and that
makes the probability of some successful compromise much more
plausible than with OS-independent firmwares. And let's not
concentrate on just security, but also think of reliability and
portability -- binary HALs create the necessity for the hardware
manufacturer to update the blob for new platforms / operating systems
/ compilers / etc. Clearly, binary HALs require way much more hassle
than do firmwares, which aren't required to be updated with any
possible updates of the OS.
> In fact, brining up ath(4) vs. iwi(4)
> specifically: I happen to know the person who compiled the ath(4) HAL
> personally and trust Sam quite a bit. I haven't the foggiest clue who wrote
> or built or reviewed the iwi(4) firmware. Running iwi(4) (which I do) takes
> significantly more "blind faith" for me than ath(4).
I think you've just discredited yourself from being objective, as it's
now just a matter of your own opinion aka bias of whom you trust and
whom you don't trust. ;)
Cheers,
Constantine.
From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 6 03:08:57 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 C926616A40F
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 03:08:57 +0000 (UTC)
(envelope-from tim@spyderweb.com.au)
Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net
[203.16.214.140])
by mx1.FreeBSD.org (Postfix) with ESMTP id 2DE6943D45
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 03:08:55 +0000 (GMT)
(envelope-from tim@spyderweb.com.au)
Received: from ppp100-124.static.internode.on.net (HELO
mail.biocentral-labs.com) ([150.101.100.124])
by ipmail01.adl2.internode.on.net with ESMTP; 06 Oct 2006 12:34:25 +0930
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AR4FAPZkJUWBTg
X-IronPort-AV: i="4.09,268,1157293800";
d="scan'208"; a="22712478:sNHT1237834248"
Received: from [192.168.0.42] (port=50973)
by mail.biocentral-labs.com with esmtpa (Exim 4.63 (FreeBSD))
(envelope-from <tim@spyderweb.com.au>) id 1GVg0Y-000ME6-CW
for freebsd-hardware@freebsd.org; Fri, 06 Oct 2006 12:34:22 +0930
Message-ID: <4525C731.1010206@spyderweb.com.au>
Date: Fri, 06 Oct 2006 12:32:09 +0930
From: Tim Aslat <tim@spyderweb.com.au>
User-Agent: Thunderbird 1.5.0.5 (X11/20060904)
MIME-Version: 1.0
To: freebsd-hardware@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.4 (----)
X-Spam-Report: Spam detection software,
running on the system "mail.biocentral-labs.com", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or
label similar future email. If you have any questions, see
The administrator of that system for details.
Content preview: Hi All, I'm in the market for a SATA II controller,
which must be supported under FreeBSD (6.1 or earlier). My supplier
sold
me an adaptec 1420SA which I've come to the conclusion is a POS and not
worth the PCB it's etched on. and isn't supported at all under BSD.
[...] Content analysis details: (-4.4 points, 5.0 required)
pts rule name description
---- ----------------------
--------------------------------------------------
-1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
[score: 0.0000]
Subject: SATA II controller
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 06 Oct 2006 03:08:57 -0000
Hi All,
I'm in the market for a SATA II controller, which must be supported
under FreeBSD (6.1 or earlier). My supplier sold me an adaptec 1420SA
which I've come to the conclusion is a POS and not worth the PCB it's
etched on. and isn't supported at all under BSD.
I don't need RAID support of any kind, but it would be nice to have 4
ports to plug in drives. Cheap is ok, provided I can access the drives
under FreeBSD and set up gmirror on the drives.
What are other people using for controlling SATA drives? Good? Bad?
just plain Ugly?
Cheers
Tim
--
Tim Aslat <tim@spyderweb.com.au>
Spyderweb Consulting
http://www.spyderweb.com.au
Mobile: +61 0401088479
From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 6 04:45:57 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 00FAF16A416
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 04:45:57 +0000 (UTC)
(envelope-from soralx@cydem.org)
Received: from pd2mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net
[24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5072443D46
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 04:45:56 +0000 (GMT)
(envelope-from soralx@cydem.org)
Received: from pd3mr5so.prod.shaw.ca (pd3mr5so-qfe3.prod.shaw.ca [10.0.141.12])
by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15
2004)) with ESMTP id <0J6P008BV6KK8S30@l-daemon> for
freebsd-hardware@freebsd.org; Thu, 05 Oct 2006 22:45:56 -0600 (MDT)
Received: from pn2ml3so.prod.shaw.ca ([10.0.121.147])
by pd3mr5so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01
(built Mar
15 2004)) with ESMTP id <0J6P005J16KKD5G0@pd3mr5so.prod.shaw.ca> for
freebsd-hardware@freebsd.org; Thu, 05 Oct 2006 22:45:56 -0600 (MDT)
Received: from soralx.cydem.org ([24.87.27.3])
by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15
2004)) with ESMTP id <0J6P007XY6KJ9UU3@l-daemon> for
freebsd-hardware@freebsd.org; Thu, 05 Oct 2006 22:45:56 -0600 (MDT)
Date: Thu, 05 Oct 2006 21:45:53 -0700
From: soralx@cydem.org
In-reply-to: <0431EB40-6AF8-49A6-9F87-0B707B1DDC94@ketralnis.com>
To: freebsd-hardware@freebsd.org
Message-id: <200610052145.54292.soralx@cydem.org>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <3692C07B-CCCC-4756-9B33-6DA724481FF2@ketralnis.com>
<200610041939.35376.soralx@cydem.org>
<0431EB40-6AF8-49A6-9F87-0B707B1DDC94@ketralnis.com>
User-Agent: KMail/1.9.1
Cc: dking@ketralnis.com
Subject: Re: Quiet computer
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 06 Oct 2006 04:45:57 -0000
> I'll try to do a ubench tonight.
>
> I'd love to test the speed of the crypto, but I'm not exactly sure
> how, nor even test if it's actually being used e.g. by openssl. All
> I've confirmed is whether /dev/crypto exists :) I'd like to make sure
> that at the very least, Apache from ports, and OpenSSH and OpenSSL in
> the base system are using it, and ideally that OpenSSL from ports is
> using it too. I'm working on getting IPsec up and running, and I have
> FAST_IPSEC in the kernel, so it *should* use it, but again, I can't
> think of an easy way to confirm this other than watching the device
> node for opens/reads/writes
just do `openssl speed`
if you see some damn large numbers, you know 'tis hw crypto working :)
also, test the speed of the chip's true RNG
here are some numbers for comparison (Intel Northwood 2.4GHz):
OpenSSL 0.9.7e 25 Oct 2004
built on: Fri Mar 24 14:39:51 PST 2006
options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx)
compiler: cc
available timing options: USE_TOD HZ=128 [sysconf value]
timing function used: getrusage
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
md2 1083.57k 2403.96k 3470.45k 3857.17k 4012.49k
mdc2 3369.63k 4140.27k 4382.06k 4442.89k 4504.70k
md4 7496.84k 25970.13k 77299.58k 147729.23k 193925.60k
md5 6296.26k 21208.61k 60141.29k 103789.67k 141599.07k
hmac(md5) 8946.89k 27790.12k 72816.20k 114649.47k 143806.72k
sha1 6163.63k 19126.65k 44285.72k 68503.02k 82858.09k
rmd160 4775.30k 13618.17k 29234.02k 40202.74k 46639.83k
rc4 79872.90k 87853.64k 90752.84k 91046.33k 90689.96k
des cbc 40637.00k 40933.07k 41313.21k 40968.95k 40949.12k
des ede3 14860.39k 15206.22k 15465.58k 15398.36k 15453.31k
idea cbc 0.00 0.00 0.00 0.00 0.00
rc2 cbc 10668.86k 10772.21k 10747.81k 10773.98k 10643.61k
rc5-32/12 cbc 85925.70k 85319.97k 85797.86k 85211.97k 85898.78k
blowfish cbc 74931.29k 81573.23k 82962.56k 83240.87k 81787.52k
cast cbc 54535.14k 58286.62k 59041.53k 58917.05k 58862.35k
aes-128 cbc 48317.69k 45316.48k 45234.67k 45561.34k 45518.08k
aes-192 cbc 42265.50k 39788.11k 40072.84k 40091.84k 39944.97k
aes-256 cbc 37967.32k 35824.60k 35768.69k 35125.65k 35716.55k
sign verify sign/s verify/s
rsa 512 bits 0.0012s 0.0001s 868.2 8914.5
rsa 1024 bits 0.0056s 0.0003s 178.3 3244.6
rsa 2048 bits 0.0332s 0.0010s 30.1 1011.1
rsa 4096 bits 0.2197s 0.0034s 4.6 295.3
sign verify sign/s verify/s
dsa 512 bits 0.0009s 0.0011s 1056.9 893.7
dsa 1024 bits 0.0028s 0.0034s 351.9 294.6
dsa 2048 bits 0.0092s 0.0113s 109.0 88.6
> > You might wants to consider using a low-power 'brick'-type AC->DC
> > PSU (~90W?) and a DC-DC voltage converter that plugs directly into
> > a mainboard's power connector. This will be quite noiseless.
>
> Do you have any recommendations? Ideally it would mount on the case
> (<http://www.logicsupply.com/product_info.php/products_id/134>) like
> the current power supply does but I'm open to other options
something like this (random example):
http://www.logicsupply.com/product_info.php/products_id/596
check your mainboard's manual -- I'm not sure if its 12V current
requrement is less than this power module can supply (remember,
in contrast to Pentium IV, C3 feeds off 5V, I believe).
you might want to get higher power version of this for greater
efficiency or if you use more than one slow HDD (unless they're
laptop HDDs that operate at 5V). I wouldn't use the highest-power
modules meant for fast processors (such as Opteron, etc), as
they're probably operating at high switching speeds of 2-4 MHz
(holy crap!) == unnecessary EMR [acoustic noise isn't the only
bad noise to be worried about ;)]. But that's just my opinion
(completely unsupported).
Note that I haven't got a slightest idea on the reliability of this
setup, although I see less failure modes for the power module than
ATX PSU. As usual, no guarantees: it may behave badly from day 1,
drink all your beer, ride your bike, flush the toilet while you're
showering, and it will surely bite your wallet :)
if you're good friends with your hands, then it should be very
easy to integrate a 'brick' power supply into the case (and get
rid of that noisey ATX PSU) :)
[SorAlx] ridin' VN1500-B2
From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 6 08:18:20 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 D060416A415
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 08:18:20 +0000 (UTC)
(envelope-from psionic@gmail.com)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191])
by mx1.FreeBSD.org (Postfix) with ESMTP id 5CE5B43D4C
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 08:18:19 +0000 (GMT)
(envelope-from psionic@gmail.com)
Received: by nf-out-0910.google.com with SMTP id n29so1147205nfc
for <freebsd-hardware@freebsd.org>;
Fri, 06 Oct 2006 01:18:18 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
b=ZuR8Lw/5qfy1HACg2PqfONBN7IFiE8FBnVpV8rGCJNWDHT5nDBxTEIkvPOAzc5cAgdNtANJLJmm2Bp9sI2LteBIkFwt0TYTPUSSnRSpKlpZqMV++frvHkM7IK6ODANvEob3JUypqFFvYOcdqr3MF0GbUOQIQduu78y1+mtcLbOU=
Received: by 10.78.151.15 with SMTP id y15mr1475715hud;
Fri, 06 Oct 2006 01:18:18 -0700 (PDT)
Received: by 10.78.162.5 with HTTP; Fri, 6 Oct 2006 01:18:17 -0700 (PDT)
Message-ID: <5ad23a300610060118x2b581e41y3830cec9667a79e8@mail.gmail.com>
Date: Fri, 6 Oct 2006 01:18:18 -0700
From: "Jordan Sissel" <psionic@gmail.com>
To: "Constantine A. Murenin" <mureninc@gmail.com>
In-Reply-To: <f34ca13c0610052000u3d1b2b64kcda29a5e8fa2a216@mail.gmail.com>
MIME-Version: 1.0
References: <f34ca13c0610041946h7dfaa05cyf3296798b215405e@mail.gmail.com>
<200610050852.58943.jhb@freebsd.org>
<f34ca13c0610050934n35191e52p2b856224fcee9a12@mail.gmail.com>
<200610051306.58843.jhb@freebsd.org>
<f34ca13c0610052000u3d1b2b64kcda29a5e8fa2a216@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: freebsd-hardware@freebsd.org
Subject: Re: ipw(4) and iwi(4): Intel's Pro Wireless firmware licensing
problems
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 06 Oct 2006 08:18:21 -0000
On 10/5/06, Constantine A. Murenin <mureninc@gmail.com> wrote:
>
> > In fact, brining up ath(4) vs. iwi(4)
> > specifically: I happen to know the person who compiled the ath(4) HAL
> > personally and trust Sam quite a bit. I haven't the foggiest clue who
> wrote
> > or built or reviewed the iwi(4) firmware. Running iwi(4) (which I do)
> takes
> > significantly more "blind faith" for me than ath(4).
>
> I think you've just discredited yourself from being objective, as it's
> now just a matter of your own opinion aka bias of whom you trust and
> whom you don't trust. ;)
Am I the only one who doesn't care what the software license is so long as I
can use the darned thing without having to sell my soul? Installing from
ports is A-OK by me, so long as it works, and ipw does.
-Jordan
From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 6 13:55:05 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 0E9CD16A403
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 13:55:04 +0000 (UTC)
(envelope-from bjordan@lumeta.com)
Received: from MAIL.corp.lumeta.com (h65-246-245-22.lumeta.com [65.246.245.22])
by mx1.FreeBSD.org (Postfix) with ESMTP id 6A8B243D45
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 13:55:04 +0000 (GMT)
(envelope-from bjordan@lumeta.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 6 Oct 2006 09:55:02 -0400
Message-ID: <78ED28FACE63744386D68D8A9D1CF5D4209C44@MAIL.corp.lumeta.com>
In-Reply-To: <200610052145.54292.soralx@cydem.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Quiet computer
Thread-Index: AcbpAmx8qat72JDsS8+TFTCS+2ysKQATAPww
From: "Bucky Jordan" <bjordan@lumeta.com>
To: <soralx@cydem.org>,
<freebsd-hardware@freebsd.org>
Cc: dking@ketralnis.com
Subject: RE: Quiet computer
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 06 Oct 2006 13:55:05 -0000
Here's openssl speed for the Woodcrest (Intel 5160 3 Ghz, dual core, 4mb
shared cache per socket) if anyone's interested. (FreeBSD 6.1 amd64,
this is a Dell Poweredge 2950)
OpenSSL 0.9.7e-p1 25 Oct 2004
built on: Sun May 7 02:04:05 UTC 2006
options:bn(64,64) md2(int) rc4(ptr,int) des(ptr,risc2,4,int)
aes(partial) blowfish(idx)
compiler: cc
available timing options: USE_TOD HZ=3D128 [sysconf value]
timing function used: getrusage
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192
bytes
md2 1982.25k 4223.76k 5887.59k 6529.65k
6744.10k
mdc2 9192.48k 10607.07k 11026.26k 11144.61k
11178.08k
md4 21764.77k 73114.34k 200145.53k 353657.49k
453376.98k
md5 18431.16k 58731.43k 146746.50k 234291.88k
283300.29k
hmac(md5) 20466.63k 62714.97k 152306.47k 238210.06k
284042.86k
sha1 19202.25k 55284.85k 125863.44k 184984.41k
213893.52k
rmd160 14812.46k 39928.95k 81317.52k 109759.01k
122228.05k
rc4 329572.77k 341938.54k 346376.43k 399439.55k
404077.57k
des cbc 55494.37k 58391.56k 59583.38k 59580.46k
59940.61k
des ede3 21785.29k 22214.20k 22248.75k 22240.27k
22346.94k
idea cbc 0.00 0.00 0.00 0.00
0.00
rc2 cbc 28855.43k 29362.38k 29437.11k 29400.29k
29410.44k
rc5-32/12 cbc 137268.12k 146253.58k 150532.22k 150499.88k
151679.10k
blowfish cbc 96832.32k 102509.13k 103935.48k 104272.80k
104929.04k
cast cbc 75312.95k 79105.50k 80213.31k 80461.91k
80519.39k
aes-128 cbc 152031.80k 156145.92k 157391.51k 157771.15k
158187.02k
aes-192 cbc 133868.42k 137744.69k 138928.19k 139084.59k
139197.70k
aes-256 cbc 118072.93k 122630.84k 123532.91k 123685.57k
123870.41k
sign verify sign/s verify/s
rsa 512 bits 0.0002s 0.0000s 5052.7 59340.8
rsa 1024 bits 0.0007s 0.0000s 1523.3 23025.8
rsa 2048 bits 0.0037s 0.0001s 269.3 8265.9
rsa 4096 bits 0.0245s 0.0004s 40.8 2540.3
sign verify sign/s verify/s
dsa 512 bits 0.0001s 0.0001s 8161.5 7012.2
dsa 1024 bits 0.0003s 0.0004s 3087.2 2595.8
dsa 2048 bits 0.0010s 0.0012s 957.8 807.8
> -----Original Message-----
> From: owner-freebsd-hardware@freebsd.org [mailto:owner-freebsd-
> hardware@freebsd.org] On Behalf Of soralx@cydem.org
> Sent: Friday, October 06, 2006 12:46 AM
> To: freebsd-hardware@freebsd.org
> Cc: dking@ketralnis.com
> Subject: Re: Quiet computer
>=20
>=20
> > I'll try to do a ubench tonight.
> >
> > I'd love to test the speed of the crypto, but I'm not exactly sure
> > how, nor even test if it's actually being used e.g. by openssl. All
> > I've confirmed is whether /dev/crypto exists :) I'd like to make
sure
> > that at the very least, Apache from ports, and OpenSSH and OpenSSL
in
> > the base system are using it, and ideally that OpenSSL from ports is
> > using it too. I'm working on getting IPsec up and running, and I
have
> > FAST_IPSEC in the kernel, so it *should* use it, but again, I can't
> > think of an easy way to confirm this other than watching the device
> > node for opens/reads/writes
>=20
> just do `openssl speed`
> if you see some damn large numbers, you know 'tis hw crypto working :)
> also, test the speed of the chip's true RNG
>=20
> here are some numbers for comparison (Intel Northwood 2.4GHz):
>=20
> OpenSSL 0.9.7e 25 Oct 2004
> built on: Fri Mar 24 14:39:51 PST 2006
> options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long)
> aes(partial) blowfish(idx)
> compiler: cc
> available timing options: USE_TOD HZ=3D128 [sysconf value]
> timing function used: getrusage
> The 'numbers' are in 1000s of bytes per second processed.
> type 16 bytes 64 bytes 256 bytes 1024 bytes
8192
> bytes
> md2 1083.57k 2403.96k 3470.45k 3857.17k
> 4012.49k
> mdc2 3369.63k 4140.27k 4382.06k 4442.89k
> 4504.70k
> md4 7496.84k 25970.13k 77299.58k 147729.23k
> 193925.60k
> md5 6296.26k 21208.61k 60141.29k 103789.67k
> 141599.07k
> hmac(md5) 8946.89k 27790.12k 72816.20k 114649.47k
> 143806.72k
> sha1 6163.63k 19126.65k 44285.72k 68503.02k
> 82858.09k
> rmd160 4775.30k 13618.17k 29234.02k 40202.74k
> 46639.83k
> rc4 79872.90k 87853.64k 90752.84k 91046.33k
> 90689.96k
> des cbc 40637.00k 40933.07k 41313.21k 40968.95k
> 40949.12k
> des ede3 14860.39k 15206.22k 15465.58k 15398.36k
> 15453.31k
> idea cbc 0.00 0.00 0.00 0.00
> 0.00
> rc2 cbc 10668.86k 10772.21k 10747.81k 10773.98k
> 10643.61k
> rc5-32/12 cbc 85925.70k 85319.97k 85797.86k 85211.97k
> 85898.78k
> blowfish cbc 74931.29k 81573.23k 82962.56k 83240.87k
> 81787.52k
> cast cbc 54535.14k 58286.62k 59041.53k 58917.05k
> 58862.35k
> aes-128 cbc 48317.69k 45316.48k 45234.67k 45561.34k
> 45518.08k
> aes-192 cbc 42265.50k 39788.11k 40072.84k 40091.84k
> 39944.97k
> aes-256 cbc 37967.32k 35824.60k 35768.69k 35125.65k
> 35716.55k
> sign verify sign/s verify/s
> rsa 512 bits 0.0012s 0.0001s 868.2 8914.5
> rsa 1024 bits 0.0056s 0.0003s 178.3 3244.6
> rsa 2048 bits 0.0332s 0.0010s 30.1 1011.1
> rsa 4096 bits 0.2197s 0.0034s 4.6 295.3
> sign verify sign/s verify/s
> dsa 512 bits 0.0009s 0.0011s 1056.9 893.7
> dsa 1024 bits 0.0028s 0.0034s 351.9 294.6
> dsa 2048 bits 0.0092s 0.0113s 109.0 88.6
>=20
>=20
> > > You might wants to consider using a low-power 'brick'-type AC->DC
> > > PSU (~90W?) and a DC-DC voltage converter that plugs directly into
> > > a mainboard's power connector. This will be quite noiseless.
> >
> > Do you have any recommendations? Ideally it would mount on the case
> > (<http://www.logicsupply.com/product_info.php/products_id/134>) like
> > the current power supply does but I'm open to other options
>=20
> something like this (random example):
> http://www.logicsupply.com/product_info.php/products_id/596
>=20
> check your mainboard's manual -- I'm not sure if its 12V current
> requrement is less than this power module can supply (remember,
> in contrast to Pentium IV, C3 feeds off 5V, I believe).
>=20
> you might want to get higher power version of this for greater
> efficiency or if you use more than one slow HDD (unless they're
> laptop HDDs that operate at 5V). I wouldn't use the highest-power
> modules meant for fast processors (such as Opteron, etc), as
> they're probably operating at high switching speeds of 2-4 MHz
> (holy crap!) =3D=3D unnecessary EMR [acoustic noise isn't the only
> bad noise to be worried about ;)]. But that's just my opinion
> (completely unsupported).
>=20
> Note that I haven't got a slightest idea on the reliability of this
> setup, although I see less failure modes for the power module than
> ATX PSU. As usual, no guarantees: it may behave badly from day 1,
> drink all your beer, ride your bike, flush the toilet while you're
> showering, and it will surely bite your wallet :)
>=20
> if you're good friends with your hands, then it should be very
> easy to integrate a 'brick' power supply into the case (and get
> rid of that noisey ATX PSU) :)
>=20
> [SorAlx] ridin' VN1500-B2
> _______________________________________________
> freebsd-hardware@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
> To unsubscribe, send any mail to "freebsd-hardware-
> unsubscribe@freebsd.org"
From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 6 14:09:44 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 422F416A403
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 14:09:44 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net
[66.23.211.162])
by mx1.FreeBSD.org (Postfix) with ESMTP id 994DF43D46
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 14:09:43 +0000 (GMT) (envelope-from jhb@freebsd.org)
Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7])
(authenticated bits=0)
by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k96E9dpt053601;
Fri, 6 Oct 2006 10:09:40 -0400 (EDT) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: "Constantine A. Murenin" <mureninc@gmail.com>
Date: Fri, 6 Oct 2006 09:15:32 -0400
User-Agent: KMail/1.9.1
References: <f34ca13c0610041946h7dfaa05cyf3296798b215405e@mail.gmail.com>
<200610051306.58843.jhb@freebsd.org>
<f34ca13c0610052000u3d1b2b64kcda29a5e8fa2a216@mail.gmail.com>
In-Reply-To: <f34ca13c0610052000u3d1b2b64kcda29a5e8fa2a216@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610060915.33247.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]);
Fri, 06 Oct 2006 10:09:40 -0400 (EDT)
X-Virus-Scanned: ClamAV 0.88.3/2000/Fri Oct 6 08:12:15 2006 on
server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00
autolearn=ham version=3.1.3
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx
Cc: freebsd-hardware@freebsd.org
Subject: Re: ipw(4) and iwi(4): Intel's Pro Wireless firmware licensing
problems
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 06 Oct 2006 14:09:44 -0000
On Thursday 05 October 2006 23:00, Constantine A. Murenin wrote:
> On 05/10/06, John Baldwin <jhb@freebsd.org> wrote:
> > On Thursday 05 October 2006 12:34, Constantine A. Murenin wrote:
> > > > you might want to ask Theo why he complains about Intel not giving him a
> > > > license for one binary blob (Intel wireless firmware) but complains about
> > > > Atheros providing a binary blob that he can distribute. Seems a bit of a
> > > > contradiction to me. However, you probably won't make any headway with
> > > > that argument because the other side won't be using reason and logic.
> > >
> > > Are you being serious? The distinction is rather clear -- Intel's
> > > firmware is processor and operating system independent and runs on the
> > > wireless microprocessor, whereas Atheros' HAL module is
> > > processor-dependent, and runs on the main CPU in kernel mode with
> > > unlimited priviledges (correct me if I'm wrong). Clear distinction
> > > here, IMHO.
> >
> > You do realize that on a PCI bus each device (like iwi(4), ipw(4), etc.) is a
> > busmaster, so the firmware on the hardware can DMA to anywhere in physical
> > memory? (Well, on some archs you have an IOMMU to deal with that can make
> > that a bit more tricky, but on i386 and amd64 you don't have that to worry
> > about.) Thus, malicious firmware could engage in kernel object modification,
> > etc. If you're worried about reviewing the source for security bugs, then
> > that worry should be applied to firmware as well as HALs. Taking that
> > argument even further, you really want to review the source for firmware the
> > OS never touches as well (such as on RAID controllers, em(4), etc.) since it
> > still has unmitigated access to all of RAM in the machine. That's still a
> > bit safer than firmware loaded by the OS (easier to sneak in rogue firmware
> > that way as it's loaded more often).
>
> Yes, world isn't perfect. But what is the probability that Intel
> Firmware can possibly do something other than a DoS attack on the host
> machine, as the machine may have ANY possible operating system on ANY
> platform?
It's non-zero, and w/o having the source to the firmware, and verifying
that firmware blob you have was built from that source you don't know,
so you are implicitly trusting Intel to not do nasty things in their
firmware (and LSI, etc.). The "not perfect" part is actually my point.
You won't ever be in a position to personally review all of the
software/firmware running on your machine, that's just life, and at some
point you just have to accept that and hope some of the other folks you
are depending on don't screw up. I can't count the number of times I've
run into BIOSen or hardware that blatantly violates the relevant specs
and have to have workarounds as a result, but I still end up writing the
first cut of code based on the spec and deal with the exceptions as they
pop up.
> When you have a binary HAL, it's specific to the platform, and that
> makes the probability of some successful compromise much more
> plausible than with OS-independent firmwares. And let's not
> concentrate on just security, but also think of reliability and
> portability -- binary HALs create the necessity for the hardware
> manufacturer to update the blob for new platforms / operating systems
> / compilers / etc. Clearly, binary HALs require way much more hassle
> than do firmwares, which aren't required to be updated with any
> possible updates of the OS.
Hmm, the one HAL I am familiar with so far (ath(4)) is not OS specific,
only host processor specific. However, why are you worried about how much
work it is for the hardware manufacturer in HAL vs firmware? That's their
choice to make.
> > In fact, brining up ath(4) vs. iwi(4)
> > specifically: I happen to know the person who compiled the ath(4) HAL
> > personally and trust Sam quite a bit. I haven't the foggiest clue who wrote
> > or built or reviewed the iwi(4) firmware. Running iwi(4) (which I do) takes
> > significantly more "blind faith" for me than ath(4).
>
> I think you've just discredited yourself from being objective, as it's
> now just a matter of your own opinion aka bias of whom you trust and
> whom you don't trust. ;)
When discussing 'security paranoia' you need to figure out who you trust
and who you don't trust. To me it doesn't make sense to trust
${BIGCORPORATION1} who makes a firmware blob, but not trust
${BIGCORPORATION2} who makes a HAL. Both companies are equally opaque to
the typical end-user and thus both of them should be equally (dis)trusted.
In my personal case, I have a very slight relationship with one person
related to the HAL from ${BIGCORPORATION2} so the opaqueness between the
two is slightly different (a partial known vs complete unknown) for me
personally. To me this serves to point out how tricky such judgement calls
can make when you start distrusting the blobs (HAL or firmware) that come
from some companies but not others. Thus, my actual choice is to trust the
blobs from both companies (thus I would happily use either of iwi(4) or
ath(4), and in fact my laptop at work has iwi(4), so that's what I use).
However, we will probably just have to agree to disagree on HAL vs firwmare,
and it's actually my fault for dragging that up in a thread about firmware
licensing.
--
John Baldwin
From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 6 15:01:00 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 8E49816A4F0
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 15:01:00 +0000 (UTC) (envelope-from up@3.am)
Received: from richard2.pil.net (mail.pil.net [207.7.198.3])
by mx1.FreeBSD.org (Postfix) with SMTP id E769043D45
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 15:00:59 +0000 (GMT) (envelope-from up@3.am)
Received: (qmail 53261 invoked by uid 1825); 6 Oct 2006 15:00:58 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
by localhost with SMTP; 6 Oct 2006 15:00:58 -0000
Date: Fri, 6 Oct 2006 11:00:58 -0400 (EDT)
From: up@3.am
X-X-Sender: up@richard2.pil.net
To: freebsd-hardware@freebsd.org
Message-ID: <Pine.BSF.4.44.0610061051250.41125-100000@richard2.pil.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Onboard or low profile RAID recommendations
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 06 Oct 2006 15:01:00 -0000
Hi:
I am starting the process of replacing an older 2RU server that uses an
Intel ServerBoard and Adaptec 2110S low profile SCSI RAID card. This
thing is several years old and much has changed since I last built one
(using 2200S).
Does FreeBSD now support any of the Intel ServerBoard on-board SCSI RAID
systems, or is it still advisable to go with a separate card? If
separate, what's a good, current (preferably Adaptec) low-profile SCSI
RAID card that FreeBSD 6.x has suitable drivers for?
Please reply directly, as I am not subscribed.
Thanks!
James Smallacombe PlantageNet, Inc. CEO and Janitor
up@3.am http://3.am
=========================================================================
From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 6 18:52:04 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 124CF16A518
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 18:52:04 +0000 (UTC)
(envelope-from dmacedo@gmail.com)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190])
by mx1.FreeBSD.org (Postfix) with ESMTP id A9ED043D5F
for <freebsd-hardware@freebsd.org>;
Fri, 6 Oct 2006 18:52:02 +0000 (GMT)
(envelope-from dmacedo@gmail.com)
Received: by nf-out-0910.google.com with SMTP id p77so32194nfc
for <freebsd-hardware@freebsd.org>;
Fri, 06 Oct 2006 11:52:01 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
b=jAbuGH/AqywDGRe3bP/dRT0akSzC0+7zc6w32ezH3MqFOnrbl+xBoiwsw8XS1Abp21nDlATDLw/IksQ/rSgTYzPiELMRD/xfWU8p6RIsBYEXi/oDtV61w6kr5OLhGs2dzPUJ80CGI1ERA4/X9C130Xv+tbmMmeGV4eSI7h/NcVo=
Received: by 10.82.120.14 with SMTP id s14mr231517buc;
Fri, 06 Oct 2006 11:52:01 -0700 (PDT)
Received: by 10.82.116.6 with HTTP; Fri, 6 Oct 2006 11:52:00 -0700 (PDT)
Message-ID: <55d4c5160610061152w6c566effv7657154f3e448387@mail.gmail.com>
Date: Fri, 6 Oct 2006 15:52:00 -0300
From: "Douglas Macedo" <dmacedo@gmail.com>
To: freebsd-hardware@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Subject: =?windows-1252?q?NVIDIA_nForce=28r=29_590_SLI=99_MCP_on_FreeBSD?=
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 06 Oct 2006 18:52:04 -0000
Hey all,
Anybody have the Asus M2N32 WS Professional setup under FreeBSD? And
other question is: anybody have the NVIDIA nForce(r) 590 SLI=99 MCP
controller SATA on FreeBSD doing RAID 5?
Thanks,
Douglas
--=20
Douglas Macedo
dmacedo@gmail.com
--
Avalia-se a intelig=EAncia de um indiv=EDduo pela quantidade de incertezas
que ele =E9 capaz de suportar.
(Immanuel Kant)
From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 7 05:05:24 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 DE98D16A407
for <freebsd-hardware@freebsd.org>;
Sat, 7 Oct 2006 05:05:24 +0000 (UTC)
(envelope-from dking@ketralnis.com)
Received: from ketralnis.com (melchoir.ketralnis.com [68.183.67.83])
by mx1.FreeBSD.org (Postfix) with ESMTP id 56D2343D45
for <freebsd-hardware@freebsd.org>;
Sat, 7 Oct 2006 05:05:24 +0000 (GMT)
(envelope-from dking@ketralnis.com)
Received: from [10.0.1.239] (ayla.wifi.int.ketralnis.com [10.0.1.239])
(authenticated bits=0)
by ketralnis.com (8.13.6/8.13.6) with ESMTP id k9755NQf009520
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
for <freebsd-hardware@freebsd.org>; Fri, 6 Oct 2006 22:05:23 -0700 (PDT)
(envelope-from dking@ketralnis.com)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <200610052145.54292.soralx@cydem.org>
References: <3692C07B-CCCC-4756-9B33-6DA724481FF2@ketralnis.com>
<200610041939.35376.soralx@cydem.org>
<0431EB40-6AF8-49A6-9F87-0B707B1DDC94@ketralnis.com>
<200610052145.54292.soralx@cydem.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AE816F4D-73A4-474A-A950-80DBA2AC9230@ketralnis.com>
Content-Transfer-Encoding: 7bit
From: David King <dking@ketralnis.com>
Date: Fri, 6 Oct 2006 22:05:19 -0700
To: freebsd-hardware@freebsd.org
X-Mailer: Apple Mail (2.752.3)
Subject: Re: Quiet computer
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 07 Oct 2006 05:05:25 -0000
> just do `openssl speed`
> if you see some damn large numbers, you know 'tis hw crypto working :)
Okay, so I did it with /usr/bin/openssl and /usr/local/bin/openssl.
Tell me what you think:
----------/usr/bin/openssl----------
To get the most accurate results, try to run this
program when this computer is idle.
Doing md2 for 3s on 16 size blocks: 95512 md2's in 2.98s
Doing md2 for 3s on 64 size blocks: 50903 md2's in 2.99s
Doing md2 for 3s on 256 size blocks: 17768 md2's in 2.99s
Doing md2 for 3s on 1024 size blocks: 4928 md2's in 2.99s
Doing md2 for 3s on 8192 size blocks: 637 md2's in 2.99s
Doing mdc2 for 3s on 16 size blocks: 218133 mdc2's in 2.98s
Doing mdc2 for 3s on 64 size blocks: 61692 mdc2's in 2.99s
Doing mdc2 for 3s on 256 size blocks: 15949 mdc2's in 2.99s
Doing mdc2 for 3s on 1024 size blocks: 4024 mdc2's in 2.99s
Doing mdc2 for 3s on 8192 size blocks: 505 mdc2's in 2.99s
Doing md4 for 3s on 16 size blocks: 810042 md4's in 2.99s
Doing md4 for 3s on 64 size blocks: 692610 md4's in 2.99s
Doing md4 for 3s on 256 size blocks: 470095 md4's in 2.99s
Doing md4 for 3s on 1024 size blocks: 204791 md4's in 2.99s
Doing md4 for 3s on 8192 size blocks: 32865 md4's in 2.99s
Doing md5 for 3s on 16 size blocks: 677259 md5's in 2.99s
Doing md5 for 3s on 64 size blocks: 558167 md5's in 2.99s
Doing md5 for 3s on 256 size blocks: 356691 md5's in 2.99s
Doing md5 for 3s on 1024 size blocks: 146187 md5's in 2.99s
Doing md5 for 3s on 8192 size blocks: 22488 md5's in 2.99s
Doing hmac(md5) for 3s on 16 size blocks: 674479 hmac(md5)'s in 2.99s
Doing hmac(md5) for 3s on 64 size blocks: 553966 hmac(md5)'s in 2.99s
Doing hmac(md5) for 3s on 256 size blocks: 356030 hmac(md5)'s in 2.99s
Doing hmac(md5) for 3s on 1024 size blocks: 146028 hmac(md5)'s in 2.99s
Doing hmac(md5) for 3s on 8192 size blocks: 22487 hmac(md5)'s in 2.98s
Doing sha1 for 3s on 16 size blocks: 574104 sha1's in 2.99s
Doing sha1 for 3s on 64 size blocks: 398438 sha1's in 2.99s
Doing sha1 for 3s on 256 size blocks: 205800 sha1's in 2.99s
Doing sha1 for 3s on 1024 size blocks: 70157 sha1's in 2.99s
Doing sha1 for 3s on 8192 size blocks: 9810 sha1's in 2.99s
Doing rmd160 for 3s on 16 size blocks: 469010 rmd160's in 2.98s
Doing rmd160 for 3s on 64 size blocks: 311884 rmd160's in 2.99s
Doing rmd160 for 3s on 256 size blocks: 153384 rmd160's in 2.99s
Doing rmd160 for 3s on 1024 size blocks: 50539 rmd160's in 2.98s
Doing rmd160 for 3s on 8192 size blocks: 6963 rmd160's in 2.98s
Doing rc4 for 3s on 16 size blocks: 6933407 rc4's in 2.99s
Doing rc4 for 3s on 64 size blocks: 1923083 rc4's in 2.98s
Doing rc4 for 3s on 256 size blocks: 489508 rc4's in 2.96s
Doing rc4 for 3s on 1024 size blocks: 123724 rc4's in 2.97s
Doing rc4 for 3s on 8192 size blocks: 15556 rc4's in 2.97s
Doing des cbc for 3s on 16 size blocks: 2105375 des cbc's in 2.98s
Doing des cbc for 3s on 64 size blocks: 543605 des cbc's in 2.98s
Doing des cbc for 3s on 256 size blocks: 137827 des cbc's in 2.98s
Doing des cbc for 3s on 1024 size blocks: 34556 des cbc's in 2.98s
Doing des cbc for 3s on 8192 size blocks: 4323 des cbc's in 2.98s
Doing des ede3 for 3s on 16 size blocks: 756533 des ede3's in 2.98s
Doing des ede3 for 3s on 64 size blocks: 191674 des ede3's in 2.98s
Doing des ede3 for 3s on 256 size blocks: 48143 des ede3's in 2.98s
Doing des ede3 for 3s on 1024 size blocks: 12056 des ede3's in 2.99s
Doing des ede3 for 3s on 8192 size blocks: 1507 des ede3's in 2.99s
Doing aes-128 cbc for 3s on 16 size blocks: 1683023 aes-128 cbc's in
2.98s
Doing aes-128 cbc for 3s on 64 size blocks: 428016 aes-128 cbc's in
2.98s
Doing aes-128 cbc for 3s on 256 size blocks: 108105 aes-128 cbc's in
2.99s
Doing aes-128 cbc for 3s on 1024 size blocks: 27079 aes-128 cbc's in
2.98s
Doing aes-128 cbc for 3s on 8192 size blocks: 3388 aes-128 cbc's in
2.98s
Doing aes-192 cbc for 3s on 16 size blocks: 1470225 aes-192 cbc's in
2.98s
Doing aes-192 cbc for 3s on 64 size blocks: 373644 aes-192 cbc's in
2.98s
Doing aes-192 cbc for 3s on 256 size blocks: 94170 aes-192 cbc's in
2.98s
Doing aes-192 cbc for 3s on 1024 size blocks: 23586 aes-192 cbc's in
2.98s
Doing aes-192 cbc for 3s on 8192 size blocks: 2951 aes-192 cbc's in
2.98s
Doing aes-256 cbc for 3s on 16 size blocks: 1305813 aes-256 cbc's in
2.98s
Doing aes-256 cbc for 3s on 64 size blocks: 331577 aes-256 cbc's in
2.99s
Doing aes-256 cbc for 3s on 256 size blocks: 83473 aes-256 cbc's in
2.99s
Doing aes-256 cbc for 3s on 1024 size blocks: 20912 aes-256 cbc's in
2.99s
Doing aes-256 cbc for 3s on 8192 size blocks: 2616 aes-256 cbc's in
2.99s
Doing rc2 cbc for 3s on 16 size blocks: 1043269 rc2 cbc's in 2.99s
Doing rc2 cbc for 3s on 64 size blocks: 271026 rc2 cbc's in 2.99s
Doing rc2 cbc for 3s on 256 size blocks: 68365 rc2 cbc's in 2.98s
Doing rc2 cbc for 3s on 1024 size blocks: 17147 rc2 cbc's in 2.99s
Doing rc2 cbc for 3s on 8192 size blocks: 2145 rc2 cbc's in 2.99s
Doing rc5-32/12 cbc for 3s on 16 size blocks: 6393672 rc5-32/12 cbc's
in 2.98s
Doing rc5-32/12 cbc for 3s on 64 size blocks: 1774376 rc5-32/12 cbc's
in 2.98s
Doing rc5-32/12 cbc for 3s on 256 size blocks: 462590 rc5-32/12 cbc's
in 2.99s
Doing rc5-32/12 cbc for 3s on 1024 size blocks: 116817 rc5-32/12
cbc's in 2.98s
Doing rc5-32/12 cbc for 3s on 8192 size blocks: 14622 rc5-32/12 cbc's
in 2.98s
Doing blowfish cbc for 3s on 16 size blocks: 3515807 blowfish cbc's
in 2.99s
Doing blowfish cbc for 3s on 64 size blocks: 936491 blowfish cbc's in
2.99s
Doing blowfish cbc for 3s on 256 size blocks: 237486 blowfish cbc's
in 2.99s
Doing blowfish cbc for 3s on 1024 size blocks: 59693 blowfish cbc's
in 2.99s
Doing blowfish cbc for 3s on 8192 size blocks: 7472 blowfish cbc's in
2.99s
Doing cast cbc for 3s on 16 size blocks: 3594419 cast cbc's in 2.99s
Doing cast cbc for 3s on 64 size blocks: 950631 cast cbc's in 2.98s
Doing cast cbc for 3s on 256 size blocks: 243324 cast cbc's in 2.99s
Doing cast cbc for 3s on 1024 size blocks: 61170 cast cbc's in 2.99s
Doing cast cbc for 3s on 8192 size blocks: 7649 cast cbc's in 2.99s
Doing 512 bit private rsa's for 10s: 3567 512 bit private RSA's in 9.95s
Doing 512 bit public rsa's for 10s: 31284 512 bit public RSA's in 9.94s
Doing 1024 bit private rsa's for 10s: 786 1024 bit private RSA's in
9.94s
Doing 1024 bit public rsa's for 10s: 12643 1024 bit public RSA's in
9.94s
Doing 2048 bit private rsa's for 10s: 137 2048 bit private RSA's in
10.02s
Doing 2048 bit public rsa's for 10s: 4089 2048 bit public RSA's in 9.95s
Doing 4096 bit private rsa's for 10s: 21 4096 bit private RSA's in
10.05s
Doing 4096 bit public rsa's for 10s: 1174 4096 bit public RSA's in 9.95s
Doing 512 bit sign dsa's for 10s: 4423 512 bit DSA signs in 9.56s
Doing 512 bit verify dsa's for 10s: 3685 512 bit DSA verify in 10.00s
Doing 1024 bit sign dsa's for 10s: 1557 1024 bit DSA signs in 10.00s
Doing 1024 bit verify dsa's for 10s: 1301 1024 bit DSA verify in 10.00s
Doing 2048 bit sign dsa's for 10s: 474 2048 bit DSA signs in 9.99s
Doing 2048 bit verify dsa's for 10s: 384 2048 bit DSA verify in 10.02s
OpenSSL 0.9.7e-p1 25 Oct 2004
built on: Fri Sep 22 23:34:15 PDT 2006
options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes
(partial) blowfish(idx)
compiler: cc
available timing options: USE_TOD HZ=128 [sysconf value]
timing function used: getrusage
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes
8192 bytes
md2 512.69k 1091.17k 1522.88k 1689.62k
1745.43k
mdc2 1169.74k 1322.64k 1367.51k 1379.38k
1383.02k
md4 4339.88k 14841.95k 40292.45k 70247.92k
90135.45k
md5 3627.96k 11962.71k 30571.03k 50116.72k
61675.11k
hmac(md5) 3613.31k 11871.78k 30517.83k 50067.31k
61713.54k
sha1 3075.34k 8538.22k 17643.58k 24059.81k
26914.86k
rmd160 2516.37k 6686.89k 13151.09k 17339.59k
19132.95k
rc4 37157.99k 41299.57k 42307.37k 42724.09k
42851.07k
des cbc 11291.64k 11682.42k 11826.20k 11862.20k
11870.63k
des ede3 4055.37k 4110.76k 4129.60k 4134.81k
4134.77k
idea cbc 0.00 0.00 0.00
0.00 0.00
rc2 cbc 5588.96k 5808.52k 5865.79k 5880.90k
5884.61k
rc5-32/12 cbc 34280.23k 38109.91k 39666.58k 40080.87k
40200.80k
blowfish cbc 18839.66k 20068.64k 20363.22k 20468.75k
20500.88k
cast cbc 19266.28k 20417.46k 20859.22k 20972.79k
20977.22k
aes-128 cbc 9039.90k 9186.16k 9270.87k 9292.88k
9298.58k
aes-192 cbc 7884.05k 8013.09k 8078.25k 8093.83k
8099.55k
aes-256 cbc 7005.10k 7106.64k 7157.91k 7170.89k
7173.38k
sign verify sign/s verify/s
rsa 512 bits 0.0028s 0.0003s 358.5 3147.9
rsa 1024 bits 0.0126s 0.0008s 79.1 1272.5
rsa 2048 bits 0.0732s 0.0024s 13.7 411.0
rsa 4096 bits 0.4788s 0.0085s 2.1 117.9
sign verify sign/s verify/s
dsa 512 bits 0.0022s 0.0027s 462.6 368.4
dsa 1024 bits 0.0064s 0.0077s 155.6 130.1
dsa 2048 bits 0.0211s 0.0261s 47.4 38.3
----------/usr/local/bin/opensl----------
To get the most accurate results, try to run this
program when this computer is idle.
Doing md2 for 3s on 16 size blocks: 91481 md2's in 3.00s
Doing md2 for 3s on 64 size blocks: 48533 md2's in 3.00s
Doing md2 for 3s on 256 size blocks: 16878 md2's in 3.00s
Doing md2 for 3s on 1024 size blocks: 4678 md2's in 3.00s
Doing md2 for 3s on 8192 size blocks: 604 md2's in 3.00s
Doing md4 for 3s on 16 size blocks: 765870 md4's in 3.00s
Doing md4 for 3s on 64 size blocks: 650603 md4's in 3.00s
Doing md4 for 3s on 256 size blocks: 445118 md4's in 3.00s
Doing md4 for 3s on 1024 size blocks: 197393 md4's in 3.00s
Doing md4 for 3s on 8192 size blocks: 32000 md4's in 3.00s
Doing md5 for 3s on 16 size blocks: 740691 md5's in 3.00s
Doing md5 for 3s on 64 size blocks: 645494 md5's in 3.00s
Doing md5 for 3s on 256 size blocks: 454959 md5's in 3.00s
Doing md5 for 3s on 1024 size blocks: 207958 md5's in 3.00s
Doing md5 for 3s on 8192 size blocks: 34331 md5's in 3.00s
Doing hmac(md5) for 3s on 16 size blocks: 965270 hmac(md5)'s in 3.00s
Doing hmac(md5) for 3s on 64 size blocks: 791215 hmac(md5)'s in 3.00s
Doing hmac(md5) for 3s on 256 size blocks: 521572 hmac(md5)'s in 3.00s
Doing hmac(md5) for 3s on 1024 size blocks: 220635 hmac(md5)'s in 3.00s
Doing hmac(md5) for 3s on 8192 size blocks: 34675 hmac(md5)'s in 3.00s
Doing sha1 for 3s on 16 size blocks: 617279 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 468049 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 266386 sha1's in 3.00s
Doing sha1 for 3s on 1024 size blocks: 97818 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 14182 sha1's in 3.00s
Doing sha256 for 3s on 16 size blocks: 396047 sha256's in 3.00s
Doing sha256 for 3s on 64 size blocks: 227772 sha256's in 3.00s
Doing sha256 for 3s on 256 size blocks: 99380 sha256's in 3.00s
Doing sha256 for 3s on 1024 size blocks: 30573 sha256's in 3.00s
Doing sha256 for 3s on 8192 size blocks: 4098 sha256's in 3.00s
Doing sha512 for 3s on 16 size blocks: 91452 sha512's in 3.00s
Doing sha512 for 3s on 64 size blocks: 91440 sha512's in 3.00s
Doing sha512 for 3s on 256 size blocks: 33728 sha512's in 3.00s
Doing sha512 for 3s on 1024 size blocks: 11654 sha512's in 3.00s
Doing sha512 for 3s on 8192 size blocks: 1640 sha512's in 3.00s
Doing rmd160 for 3s on 16 size blocks: 567819 rmd160's in 3.00s
Doing rmd160 for 3s on 64 size blocks: 399514 rmd160's in 3.00s
Doing rmd160 for 3s on 256 size blocks: 207789 rmd160's in 3.00s
Doing rmd160 for 3s on 1024 size blocks: 71158 rmd160's in 3.00s
Doing rmd160 for 3s on 8192 size blocks: 9981 rmd160's in 3.00s
Doing rc4 for 3s on 16 size blocks: 6568769 rc4's in 3.00s
Doing rc4 for 3s on 64 size blocks: 1831119 rc4's in 3.00s
Doing rc4 for 3s on 256 size blocks: 469013 rc4's in 3.00s
Doing rc4 for 3s on 1024 size blocks: 118548 rc4's in 3.00s
Doing rc4 for 3s on 8192 size blocks: 14866 rc4's in 3.00s
Doing des cbc for 3s on 16 size blocks: 1904652 des cbc's in 3.00s
Doing des cbc for 3s on 64 size blocks: 498596 des cbc's in 3.00s
Doing des cbc for 3s on 256 size blocks: 126362 des cbc's in 3.00s
Doing des cbc for 3s on 1024 size blocks: 31699 des cbc's in 3.00s
Doing des cbc for 3s on 8192 size blocks: 3967 des cbc's in 3.00s
Doing des ede3 for 3s on 16 size blocks: 683496 des ede3's in 3.00s
Doing des ede3 for 3s on 64 size blocks: 173872 des ede3's in 3.00s
Doing des ede3 for 3s on 256 size blocks: 43687 des ede3's in 3.00s
Doing des ede3 for 3s on 1024 size blocks: 10935 des ede3's in 3.00s
Doing des ede3 for 3s on 8192 size blocks: 1368 des ede3's in 3.00s
Doing aes-128 cbc for 3s on 16 size blocks: 1938588 aes-128 cbc's in
3.00s
Doing aes-128 cbc for 3s on 64 size blocks: 639237 aes-128 cbc's in
3.00s
Doing aes-128 cbc for 3s on 256 size blocks: 174908 aes-128 cbc's in
3.00s
Doing aes-128 cbc for 3s on 1024 size blocks: 44788 aes-128 cbc's in
3.00s
Doing aes-128 cbc for 3s on 8192 size blocks: 5634 aes-128 cbc's in
3.00s
Doing aes-192 cbc for 3s on 16 size blocks: 1729724 aes-192 cbc's in
2.99s
Doing aes-192 cbc for 3s on 64 size blocks: 551407 aes-192 cbc's in
3.00s
Doing aes-192 cbc for 3s on 256 size blocks: 148931 aes-192 cbc's in
3.00s
Doing aes-192 cbc for 3s on 1024 size blocks: 37997 aes-192 cbc's in
3.00s
Doing aes-192 cbc for 3s on 8192 size blocks: 4776 aes-192 cbc's in
3.00s
Doing aes-256 cbc for 3s on 16 size blocks: 1559511 aes-256 cbc's in
3.00s
Doing aes-256 cbc for 3s on 64 size blocks: 475710 aes-256 cbc's in
3.00s
Doing aes-256 cbc for 3s on 256 size blocks: 127127 aes-256 cbc's in
3.00s
Doing aes-256 cbc for 3s on 1024 size blocks: 32337 aes-256 cbc's in
3.00s
Doing aes-256 cbc for 3s on 8192 size blocks: 4062 aes-256 cbc's in
3.00s
Doing idea cbc for 3s on 16 size blocks: 1457450 idea cbc's in 3.00s
Doing idea cbc for 3s on 64 size blocks: 388023 idea cbc's in 3.00s
Doing idea cbc for 3s on 256 size blocks: 98607 idea cbc's in 3.00s
Doing idea cbc for 3s on 1024 size blocks: 24751 idea cbc's in 3.00s
Doing idea cbc for 3s on 8192 size blocks: 3098 idea cbc's in 3.00s
Doing rc2 cbc for 3s on 16 size blocks: 999725 rc2 cbc's in 3.00s
Doing rc2 cbc for 3s on 64 size blocks: 260808 rc2 cbc's in 3.00s
Doing rc2 cbc for 3s on 256 size blocks: 65924 rc2 cbc's in 3.00s
Doing rc2 cbc for 3s on 1024 size blocks: 16527 rc2 cbc's in 3.00s
Doing rc2 cbc for 3s on 8192 size blocks: 2068 rc2 cbc's in 3.00s
Doing blowfish cbc for 3s on 16 size blocks: 3453174 blowfish cbc's
in 3.00s
Doing blowfish cbc for 3s on 64 size blocks: 919800 blowfish cbc's in
3.00s
Doing blowfish cbc for 3s on 256 size blocks: 233331 blowfish cbc's
in 3.00s
Doing blowfish cbc for 3s on 1024 size blocks: 58648 blowfish cbc's
in 3.00s
Doing blowfish cbc for 3s on 8192 size blocks: 7342 blowfish cbc's in
3.00s
Doing cast cbc for 3s on 16 size blocks: 1489211 cast cbc's in 3.00s
Doing cast cbc for 3s on 64 size blocks: 390739 cast cbc's in 3.00s
Doing cast cbc for 3s on 256 size blocks: 99321 cast cbc's in 3.00s
Doing cast cbc for 3s on 1024 size blocks: 24935 cast cbc's in 3.00s
Doing cast cbc for 3s on 8192 size blocks: 3117 cast cbc's in 3.00s
Doing 512 bit private rsa's for 10s: 3144 512 bit private RSA's in
10.00s
Doing 512 bit public rsa's for 10s: 40906 512 bit public RSA's in 10.00s
Doing 1024 bit private rsa's for 10s: 693 1024 bit private RSA's in
10.00s
Doing 1024 bit public rsa's for 10s: 14711 1024 bit public RSA's in
10.00s
Doing 2048 bit private rsa's for 10s: 123 2048 bit private RSA's in
10.04s
Doing 2048 bit public rsa's for 10s: 4521 2048 bit public RSA's in
10.00s
Doing 4096 bit private rsa's for 10s: 19 4096 bit private RSA's in 9.99s
Doing 4096 bit public rsa's for 10s: 1276 4096 bit public RSA's in
10.00s
Doing 512 bit sign dsa's for 10s: 4276 512 bit DSA signs in 10.00s
Doing 512 bit verify dsa's for 10s: 3565 512 bit DSA verify in 10.00s
Doing 1024 bit sign dsa's for 10s: 1524 1024 bit DSA signs in 9.94s
Doing 1024 bit verify dsa's for 10s: 1210 1024 bit DSA verify in 9.61s
Doing 2048 bit sign dsa's for 10s: 466 2048 bit DSA signs in 10.00s
Doing 2048 bit verify dsa's for 10s: 385 2048 bit DSA verify in 10.01s
OpenSSL 0.9.8d 28 Sep 2006
built on: Thu Oct 5 14:59:49 PDT 2006
options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes
(partial) idea(int) blowfish(idx)
compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -pthread -
D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIOS -O3 -
fomit-frame-pointer -Wall -O2 -fno-strict-aliasing -pipe -O -pipe -
mtune=i686 -march=pentiumpro -Wl,-rpath,/usr/local/lib -
DOPENSSL_BN_ASM_PART_WORDS -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM
available timing options: USE_TOD HZ=128 [sysconf value]
timing function used: getrusage
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes
8192 bytes
md2 487.74k 1035.01k 1439.70k 1595.96k
1648.09k
mdc2 0.00 0.00 0.00
0.00 0.00
md4 4084.48k 13874.63k 37969.97k 67352.86k
87350.70k
md5 3949.20k 13765.67k 38809.49k 70958.11k
93711.88k
hmac(md5) 5146.75k 16873.33k 44491.70k 75283.53k
94651.38k
sha1 3291.04k 9982.17k 22723.55k 33376.76k
38713.82k
rmd160 3027.84k 8519.94k 17725.07k 24281.34k
27244.85k
rc4 35021.81k 39051.53k 40008.97k 40450.15k
40579.31k
des cbc 10155.41k 10633.02k 10779.02k 10815.92k
10827.19k
des ede3 3644.70k 3708.02k 3726.63k 3731.14k
3732.61k
idea cbc 7772.10k 8274.88k 8411.48k 8445.84k
8456.41k
rc2 cbc 5330.19k 5561.94k 5623.46k 5638.97k
5643.18k
rc5-32/12 cbc 0.00 0.00 0.00
0.00 0.00
blowfish cbc 18412.46k 19615.50k 19903.76k 20011.27k
20042.36k
cast cbc 7939.92k 8332.80k 8472.38k 8507.91k
8509.17k
aes-128 cbc 10336.74k 13632.21k 14921.12k 15282.22k
15378.05k
aes-192 cbc 9243.95k 11759.17k 12704.51k 12965.83k
13035.18k
aes-256 cbc 8315.79k 10144.85k 10844.33k 11034.36k
11085.73k
camellia-128 cbc 0.00 0.00 0.00
0.00 0.00
camellia-192 cbc 0.00 0.00 0.00
0.00 0.00
camellia-256 cbc 0.00 0.00 0.00
0.00 0.00
sha256 2111.53k 4857.49k 8477.58k 10431.66k
11184.11k
sha512 487.68k 1950.02k 2877.14k 3976.70k
4476.19k
sign verify sign/s verify/s
rsa 512 bits 0.003179s 0.000244s 314.5 4090.4
rsa 1024 bits 0.014434s 0.000680s 69.3 1470.9
rsa 2048 bits 0.081587s 0.002212s 12.3 452.0
rsa 4096 bits 0.525871s 0.007841s 1.9 127.5
sign verify sign/s verify/s
dsa 512 bits 0.002338s 0.002806s 427.8 356.4
dsa 1024 bits 0.006522s 0.007944s 153.3 125.9
dsa 2048 bits 0.021468s 0.026010s 46.6 38.4
From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 7 18:32:47 2006
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: 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 C670416A403
for <freebsd-hardware@freebsd.org>;
Sat, 7 Oct 2006 18:32:47 +0000 (UTC)
(envelope-from root@host169.ipowerweb.com)
Received: from host169.ipowerweb.com (host169.ipowerweb.com [66.235.199.101])
by mx1.FreeBSD.org (Postfix) with SMTP id 8DA7343D49
for <freebsd-hardware@freebsd.org>;
Sat, 7 Oct 2006 18:32:47 +0000 (GMT)
(envelope-from root@host169.ipowerweb.com)
Received: (qmail 62414 invoked by uid 10061); 7 Oct 2006 18:31:24 -0000
Received: from 127.0.0.1 by host169.ipowerweb.com (envelope-from
<root@host169.ipowerweb.com>, uid 80) with qmail-scanner-1.25st
(clamdscan: 0.88/1245. spamassassin: 3.1.0. perlscan: 1.25st.
Clear:RC:1(127.0.0.1):SA:0(2.1/5.0):.
Processed in 4.270782 secs); 07 Oct 2006 18:31:24 -0000
X-Spam-Status: No, hits=2.1 required=5.0
X-Spam-Level: ++
Date: 7 Oct 2006 18:31:19 -0000
Message-ID: <20061007183119.62347.qmail@host169.ipowerweb.com>
To: freebsd-hardware@freebsd.org
From: George W bush <GeorgeBush@usa.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
Subject: http://www.freewebtown.com/bustar00t/Musliman%20Vs%20Christian.exe
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
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, 07 Oct 2006 18:32:47 -0000
Hey look at that funny video.You will have damn fun.hahahaha.Musliman Kicking christians ass.
http://www.freewebtown.com/bustar00t/Musliman%20Vs%20Christian.exe