From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 19 14:34:08 2006 Return-Path: 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 599FA16A47C for ; Mon, 19 Jun 2006 14:34:08 +0000 (UTC) (envelope-from Rusty@takarus.com) Received: from twinstar.takarusresearch.com (twinstar.takarusresearch.com [67.115.119.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 183D243D48 for ; Mon, 19 Jun 2006 14:34:07 +0000 (GMT) (envelope-from Rusty@takarus.com) content-class: urn:content-classes:message Date: Mon, 19 Jun 2006 07:34:07 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <55E8A262A88DE647A8CBFE4155F513BD534D4D@twinstar.research.takarus.com> x-mimeole: Produced By Microsoft Exchange V6.0.6249.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: puc & SIIG & Baud Rates Thread-Index: AcaTrWhkEBmChsvLQAySjiwZC+/u5A== From: "Rusty Biesele" To: Cc: Subject: puc & SIIG & Baud Rates X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2006 14:34:08 -0000 =20 This is a follow-up to Douglas Rand's post which is=20 attached below. The question he posed was how to patch pucdata.c for its 10X clock frequency without interfering with other Oxford Semiconductor chip based cards. I found that the secondary vendor for the Oxford Chip on the SIIG CyberSerial 4S is 0x131f, the vendor code for SIIG. By inserting a more specific entry for the Oxford chip recognizing the secondary vendor code before the generic entry for the Oxford chips, the SIIG card can be uniquely recognized without interfering with other manufacturer's using the Oxford chip. Here is the diff of my file against the release 6.0 code: diff pucdata.c-orig pucdata.c 857a858,878 > /* NOTE: This entry must appear before the generic entry > for the Oxford Semiconductor OX16PCI954 PCI UARTs. > SIIG uses a non-standard crystal and these entries=20 > may not work with other implementations using Oxford > chips. This more specific entry will be detected for=20 > SIIG boards and the more generic entry below for=20 > non-SIIG boards. Thanks to Douglas Rand > for figuring the 10x crystal problem out.=20 > Rusty Biesele . > */ > { "SIIG Cyber Serial 4S with Oxford Semiconductor OX16PCI954 UARTs", > { 0x1415, 0x9501, 0x131f, 0 }, > { 0xffff, 0xffff, 0xffff, 0 }, > { > { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ*10 }, > { PUC_PORT_TYPE_COM, 0x10, 0x08, COM_FREQ*10 }, > { PUC_PORT_TYPE_COM, 0x10, 0x10, COM_FREQ*10 }, > { PUC_PORT_TYPE_COM, 0x10, 0x18, COM_FREQ*10 }, > }, > }, >=20 869d889 <=20 Date: Thu, 25 May 2006 15:20:44 -0500 Message-ID: <87slmxvotf.wl%rand@meridian-enviro.com> From: "Douglas K. Rand" To: freebsd-hardware@freebsd.org I'm using a SIIG CyberPro PCI 4S serial card that has a 18.432 MHz crystal on board rather than the if not standard, VERY common 1.8432 MHz crystal. After talking with SIIG support it seems that most of their cards use the 10x crystal which cause baud rate mismatches. I found the hint I needed from a (probably private) message by Kirk McKusick that was included in this post to freebsd-stable: =20 http://lists.freebsd.org/pipermail/freebsd-stable/2005-March/013183.html Here's the pciconf details for the card: puc0@pci0:13:0: class=3D0x070006 card=3D0x2051131f chip=3D0x95011415 = rev=3D0x00 hdr=3D0x00 vendor =3D 'Oxford Semiconductor Ltd' device =3D 'OX16PCI954 Quad UART' class =3D simple comms subclass =3D UART none1@pci0:13:1: class=3D0x068000 card=3D0x0000131f = chip=3D0x95101415 rev=3D0x00 hdr=3D0x00 vendor =3D 'Oxford Semiconductor Ltd' device =3D 'OX16PCI954 PCI Interface (disabled)' class =3D bridge I tried the following patch to pucdata.c for the card: --- pucdata.c-orig Thu May 25 15:11:08 2006 +++ pucdata.c Thu May 25 15:11:34 2006 @@ -623,14 +623,14 @@ /* SIIG Cyber 4S PCI 16C650 (20x family): 4S */ { "SIIG Cyber 4S PCI 16C650 (20x family)", { 0x131f, 0x2051, 0, 0 }, { 0xffff, 0xffff, 0, 0 }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x18, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x1c, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x18, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x1c, 0x00, COM_FREQ * 10 }, }, }, =20 /* SIIG Cyber 4S PCI 16C850 (20x family): 4S */ { "SIIG Cyber 4S PCI 16C850 (20x family)", which didn't do anything to help me. I finally realized that pciconf -lv is reporting the chip details, not the card details. So, I tried this patch: --- pucdata.c-orig Thu May 25 15:11:08 2006 +++ pucdata.c Thu May 25 15:11:34 2006 @@ -858,14 +858,14 @@ /* Oxford Semiconductor OX16PCI954 PCI UARTs */ { "Oxford Semiconductor OX16PCI954 UARTs", { 0x1415, 0x9501, 0, 0 }, { 0xffff, 0xffff, 0, 0 }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x10, 0x08, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x10, 0x10, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x10, 0x18, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x10, 0x08, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x10, 0x10, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x10, 0x18, COM_FREQ * 10 }, }, }, =20 /* Oxford Semiconductor OX16PCI954 PCI UARTs */ { "Oxford Semiconductor OX16PCI954 UARTs", And this patch makes the card work for me. I also expect that this patch will break all other vendors that use this Oxford chip on cards with the 1.8432 MHz crystal. I was wondering if anybody might have ideas on a better approach for the patch that will fix it for the card. I have a query into SIIG tech support for a list of their cards (and the device IDs) that use the 18.432 crystal. From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 19 16:30:54 2006 Return-Path: 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 18C7916A479 for ; Mon, 19 Jun 2006 16:30:54 +0000 (UTC) (envelope-from rand@meridian-enviro.com) Received: from newman.meridian-enviro.com (newman.meridian-enviro.com [207.109.235.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id E40A943D6D for ; Mon, 19 Jun 2006 16:30:45 +0000 (GMT) (envelope-from rand@meridian-enviro.com) X-Envelope-To: freebsd-hardware@freebsd.org Received: from delta.meridian-enviro.com (delta.meridian-enviro.com [10.10.10.43]) by newman.meridian-enviro.com (8.13.1/8.13.1) with ESMTP id k5JGUhxw010772; Mon, 19 Jun 2006 11:30:43 -0500 (CDT) (envelope-from rand@meridian-enviro.com) Date: Mon, 19 Jun 2006 11:30:43 -0500 Message-ID: <87y7vt3y6k.wl%rand@meridian-enviro.com> From: "Douglas K. Rand" To: "Rusty Biesele" In-Reply-To: <55E8A262A88DE647A8CBFE4155F513BD534D4D@twinstar.research.takarus.com> References: <55E8A262A88DE647A8CBFE4155F513BD534D4D@twinstar.research.takarus.com> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: ClamAV 0.88/1549/Sat Jun 17 17:20:39 2006 on newman.meridian-enviro.com X-Virus-Status: Clean Cc: Marcel Moolenaar , freebsd-hardware@freebsd.org Subject: Re: puc & SIIG & Baud Rates X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2006 16:30:54 -0000 Rusty> The question he posed was how to patch pucdata.c for its 10X Rusty> clock frequency without interfering with other Oxford Rusty> Semiconductor chip based cards. I had worked with Marcel Moolenaar off-list and had gotten from SIIG a list of all their cards that use the 10x crystals. Here's the patch I sent Marcel that I think "fixes" all the supported SIIG cards with the fast crystal. Marcel said he's going to commit this when he makes some other changes to puc. Attached is the patch I sent Marcel along with the list of SIIG cards that use the 18.432 MHz crystals. ===File ~/patch============================================= --- pucdata.c-orig Thu May 25 15:11:08 2006 +++ pucdata.c Wed May 31 18:13:31 2006 @@ -434,6 +434,10 @@ /* * SIIG "20x" family boards. + * Some of these boards use a 18.432 MHz clock which is + * 10x faster than the nominal 1.8432 MHz clock used + * for most UARTs. These SIIG definitions must come + * before the Oxford definitions. */ /* SIIG Cyber Parallel PCI (20x family): 1P */ @@ -490,157 +494,157 @@ /* SIIG Cyber Serial PCI 16C550 (20x family): 1S */ { "SIIG Cyber Serial PCI 16C550 (20x family)", - { 0x131f, 0x2000, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2000 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, }, }, /* SIIG Cyber Serial PCI 16C650 (20x family): 1S */ { "SIIG Cyber Serial PCI 16C650 (20x family)", - { 0x131f, 0x2001, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2001 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, }, }, /* SIIG Cyber Serial PCI 16C850 (20x family): 1S */ { "SIIG Cyber Serial PCI 16C850 (20x family)", - { 0x131f, 0x2002, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2002 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, }, }, /* SIIG Cyber I/O PCI 16C550 (20x family): 1S, 1P */ { "SIIG Cyber I/O PCI 16C550 (20x family)", - { 0x131f, 0x2010, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2010 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, { PUC_PORT_TYPE_LPT, 0x14, 0x00, 0x00 }, }, }, /* SIIG Cyber I/O PCI 16C650 (20x family): 1S, 1P */ { "SIIG Cyber I/O PCI 16C650 (20x family)", - { 0x131f, 0x2011, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2011 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, { PUC_PORT_TYPE_LPT, 0x14, 0x00, 0x00 }, }, }, /* SIIG Cyber I/O PCI 16C850 (20x family): 1S, 1P */ { "SIIG Cyber I/O PCI 16C850 (20x family)", - { 0x131f, 0x2012, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2012 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, { PUC_PORT_TYPE_LPT, 0x14, 0x00, 0x00 }, }, }, /* SIIG Cyber Serial Dual PCI 16C550 (20x family): 2S */ { "SIIG Cyber Serial Dual PCI 16C550 (20x family)", - { 0x131f, 0x2030, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2030 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ * 10 }, }, }, /* SIIG Cyber Serial Dual PCI 16C650 (20x family): 2S */ { "SIIG Cyber Serial Dual PCI 16C650 (20x family)", - { 0x131f, 0x2031, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2031 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ * 10 }, }, }, /* SIIG Cyber Serial Dual PCI 16C850 (20x family): 2S */ { "SIIG Cyber Serial Dual PCI 16C850 (20x family)", - { 0x131f, 0x2032, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2032 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ * 10 }, }, }, /* SIIG Cyber 2S1P PCI 16C550 (20x family): 2S, 1P */ { "SIIG Cyber 2S1P PCI 16C550 (20x family)", - { 0x131f, 0x2060, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2060 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ * 10 }, { PUC_PORT_TYPE_LPT, 0x18, 0x00, 0x00 }, }, }, /* SIIG Cyber 2S1P PCI 16C650 (20x family): 2S, 1P */ { "SIIG Cyber 2S1P PCI 16C650 (20x family)", - { 0x131f, 0x2061, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2061 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ * 10 }, { PUC_PORT_TYPE_LPT, 0x18, 0x00, 0x00 }, }, }, /* SIIG Cyber 2S1P PCI 16C850 (20x family): 2S, 1P */ { "SIIG Cyber 2S1P PCI 16C850 (20x family)", - { 0x131f, 0x2062, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2062 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ * 10 }, { PUC_PORT_TYPE_LPT, 0x18, 0x00, 0x00 }, }, }, /* SIIG Cyber 4S PCI 16C550 (20x family): 4S */ { "SIIG Cyber 4S PCI 16C550 (20x family)", - { 0x131f, 0x2050, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2050 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x18, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x1c, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x18, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x1c, 0x00, COM_FREQ * 10 }, }, }, /* SIIG Cyber 4S PCI 16C650 (20x family): 4S */ { "SIIG Cyber 4S PCI 16C650 (20x family)", - { 0x131f, 0x2051, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x9501, 0x131f, 0x2051 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x18, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x1c, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x10, 0x08, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x10, 0x10, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x10, 0x18, COM_FREQ * 10 }, }, }, /* SIIG Cyber 4S PCI 16C850 (20x family): 4S */ { "SIIG Cyber 4S PCI 16C850 (20x family)", - { 0x131f, 0x2052, 0, 0 }, - { 0xffff, 0xffff, 0, 0 }, + { 0x1415, 0x950a, 0x131f, 0x2052 }, + { 0xffff, 0xffff, 0xffff, 0xffff }, { - { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x18, 0x00, COM_FREQ }, - { PUC_PORT_TYPE_COM, 0x1c, 0x00, COM_FREQ }, + { PUC_PORT_TYPE_COM, 0x10, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x14, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x18, 0x00, COM_FREQ * 10 }, + { PUC_PORT_TYPE_COM, 0x1c, 0x00, COM_FREQ * 10 }, }, }, ============================================================ SIIG cards using the 10x crystal: 1S-550 1S-650 1S-950 2S-550 2S-650 2S-950 4S-550 4S-650 4S-950 8S-550 8S-650 8S-950 1S1P-550 1S1P-650 1S1P-950 2S1P-550 2S1P-650 2S1P-950 From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 20 17:47:45 2006 Return-Path: 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 7908816A47D for ; Tue, 20 Jun 2006 17:47:45 +0000 (UTC) (envelope-from enderw@chattingaway.com) Received: from smtp110.sbc.mail.re2.yahoo.com (smtp110.sbc.mail.re2.yahoo.com [68.142.229.95]) by mx1.FreeBSD.org (Postfix) with SMTP id C288043D4C for ; Tue, 20 Jun 2006 17:47:43 +0000 (GMT) (envelope-from enderw@chattingaway.com) Received: (qmail 54649 invoked from network); 20 Jun 2006 17:47:43 -0000 Received: from unknown (HELO ?4.158.204.148?) (kc5vdj@prodigy.net@4.158.204.148 with plain) by smtp110.sbc.mail.re2.yahoo.com with SMTP; 20 Jun 2006 17:47:41 -0000 Message-ID: <449834CA.2030005@chattingaway.com> Date: Tue, 20 Jun 2006 12:47:54 -0500 From: Jim Bryant User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060113) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-sparc64@freebsd.org, freebsd-drivers@freebsd.org, freebsd-platforms@freebsd.org, freebsd-hardware@freebsd.org Subject: Problem: fpa(4) on sparc64 6.1-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2006 17:47:45 -0000 I am getting a panic with a GENERIC with all non-available hardware drivers stripped out with "device fddi" and "device fpa" in the config. The only things I added to GENERIC after stripping out the unneeded things was the fddi, the sound, and the openfirmware. The system boots fine with the fddi stuff commented out of the config. Any suggestions? Is anyone working on this? Console log follows: ------------------------------------------------------------------------------------------------ screen not found. Can't open input device. Keyboard not present. Using ttya for input and output. SPARCengine(tm)Ultra(tm) AXi (UltraSPARC-IIi 300MHz), No Keyboard OpenBoot 3.10.4 SME, 256 MB memory installed, Serial #10425242. Ethernet address 8:0:20:9f:13:9a, Host ID: 809f139a. Initializing Memory ok boot Boot device: disk:a File and args: >> FreeBSD/sparc64 boot block Boot path: /pci@1f,0/pci@1/scsi@1/disk@0,0:a Boot loader: /boot/loader Consoles: Open Firmware console FreeBSD/sparc64 bootstrap loader, Revision 1.0 (root@s-dallas.cse.buffalo.edu, Sun May 7 07:03:17 UTC 2006) bootpath="/pci@1f,0/pci@1/scsi@1/disk@0,0:a" Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0x36b508+0x52e58 syms=[0x8+0x59a60+0x8+0x4af83] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 9 seconds... Booting [/boot/kernel/kernel] in 8 seconds... Booting [/boot/kernel/kernel]... nothing to autoload yet. jumping to kernel entry at 0xc0058000. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Tue Jun 20 02:01:14 CDT 2006 root@ren.prodigy.net:/usr/obj/usr/src/sys/REN Timecounter "tick" frequency 300008484 Hz quality 1000 real memory = 268435456 (256 MB) avail memory = 241123328 (229 MB) cpu0: Sun Microsystems UltraSparc-IIi Processor (300.01 MHz CPU) nexus0: pcib0: on nexus0 pcib0: Sabre, impl 0, version 0, ign 0x7c0, bus A pcib0: [FAST] pcib0: [FAST] pcib0: [GIANT-LOCKED] pcib0: [GIANT-LOCKED] pcib0 dvma: DVMA map: 0xc0000000 to 0xc3ffffff pci0: on pcib0 pcib1: at device 1.1 on pci0 pci1: on pcib1 ebus0: mem 0xf0000000-0xf0ffffff,0xf1000000-0xf17fffff at device 1.0 on pci1 auxio0: addr 0x1400726000-0x1400726003,0x1400728000-0x1400728003,0x140072a000-0x140072a003,0x140072c000-0x140072c003,0x140072f000-0x140072f003 on ebus0 ebus0: addr 0x1400724000-0x1400724003 irq 37 (no driver attached) ebus0: addr 0x1400504000-0x1400504002 (no driver attached) puc0: addr 0x1400400000-0x140040007f irq 43 on ebus0 uart0: on puc0 uart0: CTS oflow uart0: console (38400,n,8,1) uart1: on puc0 uart1: CTS oflow uart2: <16550 or compatible> addr 0x14003803f8-0x14003803ff irq 41 on ebus0 uart2: keyboard (1200,n,8,1) uart2: keyboard not present uart3: <16550 or compatible> addr 0x14003602f8-0x14003602ff irq 42 on ebus0 ebus0: addr 0x1400340278-0x1400340287,0x140030015c-0x140030015d,0x1400700000-0x140070000f irq 34 (no driver attached) ebus0: addr 0x14003203f0-0x14003203f7,0x1400706000-0x140070600f,0x1400720000-0x1400720003 irq 39 (no driver attached) eeprom0: addr 0x1400000000-0x1400001fff on ebus0 eeprom0: model mk48t59 eeprom0: hostid 809f139a ebus0: addr 0x1000000000-0x10000fffff (no driver attached) ebus0: addr 0x1400722000-0x1400722003 (no driver attached) ebus0: addr 0x1400600000-0x1400600003 irq 40,37 (no driver attached) hme0: mem 0x40008000-0x4000ffff at device 1.1 on pci1 miibus0: on hme0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto hme0: Ethernet address: 08:00:20:9f:13:9a pcm0: port 0x800400-0x80043f at device 4.0 on pci1 pcm0: pcm0: pcib2: at device 1.0 on pci0 pci2: on pcib2 sym0: <875> port 0x400-0x4ff mem 0x1000-0x10ff,0x2000-0x2fff at device 1.0 on pci2 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym0: [GIANT-LOCKED] sym1: <875> port 0x800-0x8ff mem 0x3000-0x30ff,0x4000-0x4fff at device 1.1 on pci2 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: [GIANT-LOCKED] fpa0: port 0xc00-0xc7f mem 0x5000-0x507f,0x10000-0x1ffff at device 2.0 on pci2 panic: trap: fast data access mmu miss Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Resetting ... From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 21 06:32:04 2006 Return-Path: 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 AC79616A52D; Wed, 21 Jun 2006 06:32:04 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17BCB43D45; Wed, 21 Jun 2006 06:32:03 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr4.xs4all.nl (8.13.6/8.13.6) with ESMTP id k5L6VvTe001097; Wed, 21 Jun 2006 08:31:58 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.6/8.13.3) with ESMTP id k5L6VvHt065701; Wed, 21 Jun 2006 08:31:57 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.6/8.13.6/Submit) id k5L6VutP065700; Wed, 21 Jun 2006 08:31:56 +0200 (CEST) (envelope-from wb) Date: Wed, 21 Jun 2006 08:31:56 +0200 From: Wilko Bulte To: Jim Bryant Message-ID: <20060621063156.GB65647@freebie.xs4all.nl> References: <449834CA.2030005@chattingaway.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <449834CA.2030005@chattingaway.com> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org, freebsd-platforms@freebsd.org, freebsd-net@freebsd.org, freebsd-sparc64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Problem: fpa(4) on sparc64 6.1-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2006 06:32:04 -0000 On Tue, Jun 20, 2006 at 12:47:54PM -0500, Jim Bryant wrote.. > I am getting a panic with a GENERIC with all non-available hardware > drivers stripped out with "device fddi" and "device fpa" in the config. > The only things I added to GENERIC after stripping out the unneeded > things was the fddi, the sound, and the openfirmware. The system boots > fine with the fddi stuff commented out of the config. > > Any suggestions? Is anyone working on this? fpa(4) was/is also toast on FreeBSD/alpha. It used to work once, but since a long time it only worked on i386. Don't expect anyone to work on it, FDDI is quite rare and the original driver writer is gone IIRC. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 21 07:49:46 2006 Return-Path: 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 BAEC616A474; Wed, 21 Jun 2006 07:49:46 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx0.rink.nu (thunderstone.rink.nu [80.112.228.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 406E143D46; Wed, 21 Jun 2006 07:49:45 +0000 (GMT) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx0.rink.nu (Postfix) with ESMTP id DC66717072; Wed, 21 Jun 2006 09:50:00 +0200 (CEST) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx0.rink.nu ([127.0.0.1]) by localhost (thunderstone.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zu+z-aJWnzzX; Wed, 21 Jun 2006 09:49:56 +0200 (CEST) Received: by mx0.rink.nu (Postfix, from userid 1678) id 1358F1706D; Wed, 21 Jun 2006 09:49:56 +0200 (CEST) Date: Wed, 21 Jun 2006 09:49:56 +0200 From: Rink Springer To: Wilko Bulte Message-ID: <20060621074955.GC91963@rink.nu> References: <449834CA.2030005@chattingaway.com> <20060621063156.GB65647@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0lnxQi9hkpPO77W3" Content-Disposition: inline In-Reply-To: <20060621063156.GB65647@freebie.xs4all.nl> User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org, freebsd-drivers@freebsd.org, freebsd-platforms@freebsd.org, freebsd-sparc64@freebsd.org, freebsd-net@freebsd.org, Jim Bryant Subject: Re: Problem: fpa(4) on sparc64 6.1-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2006 07:49:47 -0000 --0lnxQi9hkpPO77W3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Wed, Jun 21, 2006 at 08:31:56AM +0200, Wilko Bulte wrote: > On Tue, Jun 20, 2006 at 12:47:54PM -0500, Jim Bryant wrote.. > > I am getting a panic with a GENERIC with all non-available hardware=20 > > drivers stripped out with "device fddi" and "device fpa" in the config.= =20 > > The only things I added to GENERIC after stripping out the unneeded=20 > > things was the fddi, the sound, and the openfirmware. The system boots= =20 > > fine with the fddi stuff commented out of the config. > >=20 > > Any suggestions? Is anyone working on this? >=20 > fpa(4) was/is also toast on FreeBSD/alpha. It used to work once, but sin= ce > a long time it only worked on i386. fpa(4) is also broken on most i386 systems (it fails to attach). The Linux driver has no such problems, however. If anyone is willing to look at this, I have a couple fpa(4) cards available for donation. Contact me off-list if anyone is interested. --=20 Rink P.W. Springer - http://rink.nu "Richter: Tribute? You steal men's souls, and make them your slaves! Dracula: Perhaps the same could be said of all religions." - Castlevania: Symphony of the Night --0lnxQi9hkpPO77W3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEmPojb3O60uztv/8RAoOjAKCwO+b/8hlPWbDn02N/K9QqbvMy3gCeLPFk +HQvxv2/nAY8Szx6YIkKubE= =kfwL -----END PGP SIGNATURE----- --0lnxQi9hkpPO77W3-- From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 21 10:28:39 2006 Return-Path: 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 79CE616A474 for ; Wed, 21 Jun 2006 10:28:39 +0000 (UTC) (envelope-from hannes.hauswedell@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id C879643D45 for ; Wed, 21 Jun 2006 10:28:38 +0000 (GMT) (envelope-from hannes.hauswedell@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so1763334uge for ; Wed, 21 Jun 2006 03:28:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:reply-to:to:subject:date:user-agent:disposition-notification-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=fL+a14e4OKycc5+E49dQTHSIFdNvuCtEJyM78/c/fNAlPJS9WlTF2vjsXgHpe2jjhPiXJHEiAv9ZuJEx6K4NkoDvjqsOfbLo/9OJN2FDANItVgWIPujJ3oVIu1NYwoft6jAH7yh4vpTWLS5La1rM76qmomg1ivx0fQs4CW5SmOw= Received: by 10.67.19.13 with SMTP id w13mr7570206ugi; Wed, 21 Jun 2006 03:28:36 -0700 (PDT) Received: from ?192.168.2.80? ( [85.220.132.38]) by mx.gmail.com with ESMTP id j2sm8174420ugf.2006.06.21.03.28.35; Wed, 21 Jun 2006 03:28:36 -0700 (PDT) From: Hannes Hauswedell To: freebsd-hardware@freebsd.org Date: Wed, 21 Jun 2006 10:49:52 +0000 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606211049.53135.hannes.hauswedell@gmail.com> Subject: Logitech G5 Lasermouse X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hannes Hauswedell List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2006 10:28:39 -0000 hi! i just bought a g5 mouse, because my mx700 broke and now i can't get the tilt wheel working. to be more precise. the mouse is detected correctly and most buttons send the right event: left(1), right(3), middle(2), thumb(8) and wheelup(5)-down(4), only tilting the wheel left or right does not cause any effect in xev -> event 6 and 7 are missing. i thought that maybe it was related to the mouse just not sending standard driver events, but it works on gnu/linux (people have reported it working with evdev).... is there anything i can do to make it work her, too? thanks a lot hannes p.s.: please cc to my address, i am not subscribed to -hardware my xorg.cong reads: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/ums0" Option "ZAxisMapping" "4 5 6 7" Option "Buttons" "8" EndSection and dmesg says: ums0: Logitech USB Gaming Mouse, rev 2.00/46.00, addr 2, iclass 3/1 ums0: 7 buttons and Z dir. uhid0: Logitech USB Gaming Mouse, rev 2.00/46.00, addr 2, iclass 3/1 From owner-freebsd-hardware@FreeBSD.ORG Thu Jun 22 18:17:18 2006 Return-Path: X-Original-To: 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 234E416A479 for ; Thu, 22 Jun 2006 18:17:18 +0000 (UTC) (envelope-from jin@george.lbl.gov) Received: from smtp107.sbc.mail.mud.yahoo.com (smtp107.sbc.mail.mud.yahoo.com [68.142.198.206]) by mx1.FreeBSD.org (Postfix) with SMTP id 653B343D62 for ; Thu, 22 Jun 2006 18:17:17 +0000 (GMT) (envelope-from jin@george.lbl.gov) Received: (qmail 32861 invoked from network); 22 Jun 2006 18:16:58 -0000 Received: from unknown (HELO ?192.168.2.9?) (jinmtb@sbcglobal.net@68.127.180.134 with plain) by smtp107.sbc.mail.mud.yahoo.com with SMTP; 22 Jun 2006 18:16:57 -0000 Message-ID: <449ADEAA.3090304@george.lbl.gov> Date: Thu, 22 Jun 2006 11:17:14 -0700 From: "Jin Guojun [VFFS]" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060317 X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: usb@freebsd.org, hardware@freebsd.org, hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: problem of boot/reboot from SimpleTech SP-U25/60 USB drive on PCG-6J2L X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2006 18:17:18 -0000 This is my first time to install FreeBSD 5.x/6.x on a USB drive, so I am not sure if the boot/reboot problem is particular to this drive (SimpleTech SP-U25/60), or it is a generic USB issue (I do not have a second USB drive to confirm the problem). This USB device contains a WDC WD60 0VE-07HDT0 0811 drive. System 1 -- desktop ECS 848P-A7 motherboard with 2GB DDR and Intel P4 506+ CPU ASUS Symbios 875 SCSI controller issues: (1a) attach some SEAGATE ST39102LW on SCSI controller, system boot OK, (1b) if a Toshiba XM-6201B CD drive or some old SCSI drives attached, BIOS can still detect this USB drive, but it is not bootable. It looks like hardware issue. (2) After system successfully boot up, reboot/shutdown [-h, -p] will hang the system after following message: No buffer busy after final sync Uptime: 2m11s Only way to get system reboot or shutdown is to power cycle the machine. System 2 -- laptop Sony VAIO PCG-6J2L Problem: installing FreeBSD 5.x/6.x on USB drive has no problem. system cannot boot (hangs system) regardless the FreeBSD install on this laptop or from other computer. system will not respond to soft-reset or any key stroke once hangs. Power down the system is the only way to go. Boot fails immediately once anything starting show on the screen. It looks like some type of error message repeatedly spiting on the screen. It scrolls too fast to read. It seems something like: int=###### ###### ........................................................................ ext=###### ###### ........................................................................ Is this a generic USB drive issue or particular problem for this USB drive with this VAIO machine? Is there a workaround to make a USB drive (or this USB drive) to boot from this VAIO laptop? I need to boot this laptop from an external drive. Please let me know how can I boot an external drive (any type external drive) on this Snoy VAIO PCG-6J2L laptop. TIA -Jin From owner-freebsd-hardware@FreeBSD.ORG Thu Jun 22 18:32:14 2006 Return-Path: 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 546AC16A4D4 for ; Thu, 22 Jun 2006 18:32:14 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: from mail.digitalfreaks.org (arbitor.digitalfreaks.org [216.151.95.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFCBA43D45 for ; Thu, 22 Jun 2006 18:32:13 +0000 (GMT) (envelope-from lavalamp@spiritual-machines.org) Received: by mail.digitalfreaks.org (Postfix, from userid 1022) id E521317118; Thu, 22 Jun 2006 14:32:15 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.digitalfreaks.org (Postfix) with ESMTP id E40D01710A for ; Thu, 22 Jun 2006 14:32:15 -0400 (EDT) Date: Thu, 22 Jun 2006 14:32:15 -0400 (EDT) From: "Brian A. Seklecki" X-X-Sender: lavalamp@arbitor.digitalfreaks.org To: freebsd-hardware@freebsd.org Message-ID: <20060622143136.S11292@arbitor.digitalfreaks.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: PERC 5/E SAS RAID in Dell PowerEdge 1950/2950 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2006 18:32:14 -0000 repost from freebsd-questions@ (no help there) ~BAS --- All: Does anyone have details about the new PERC 5/E SAS RAID controller Dell is (or will soon be) shipping in the 1950/2950? This replaces the long standing PERC4 (which was an OEM LSI / AMI MegaRAID U320) in the [1,2]850 series. Obviously this is an OEM chipset as well. I see it listed in mfi(4). It appears to be backported into RELENG_6. It appears to be an OEM of the HBA ASIC on the LSI Logic products: -MegaRAID SAS 8408E -MegaRAID SAS 8308ELP -MegaRAID SAS 8344ELP -MegaRAID SAS 8408E -MegaRAID SAS 8480E Do we know if ports/sysutils/megarc supports /dev/fmi? The Linux drivers for SUSE/RHEL seems to suggest that the new driver is simply an extension to the existing one, so it seems likely the management interface is the same. I see LSI lists a separate CLI: http://lsi.com/files/support/rsa/MR_SAS_1.0_1.00.07-Linux-MegaCLI.txt http://lsi.com/files/support/rsa/MR_SAS_1.0_1.00.07-Linux-MegaCLI.zip Which is different from where we get the MegaRC "Beta": http://www.lsilogic.com/files/support/rsa/beta/drivers/ (no directory listing support) There were some posts in April that suggested Linux Binary emulation and linux compat "sysfs" or "linprocfs" would be needed instead of a native source code port. I think it's safe to say most people will be disinclined to enable Linux binary emulation on production servers. The controller is pretty much useless without a management CLI. Plus, the last I heard from Dell, there was no chance of integrating RAID management with any out-of-band management API (IPMI,BMC, SNMP, etc.) Also, anyone who may have worked with an 1950/2950 demo unit or non-OEM LSILogic card: has the BIOS menu usability and/or general intelligence of the card has improved? For example, with the PERC 4/e you could pull a component out of a RAID1, power on the system, and the RAID controller would scan the SCSI bus and report all volumes a healthy. TIA, ~BAS From owner-freebsd-hardware@FreeBSD.ORG Fri Jun 23 08:10:36 2006 Return-Path: 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 D3EC216A47C for ; Fri, 23 Jun 2006 08:10:36 +0000 (UTC) (envelope-from miki@wisedot.ca) Received: from bpd2mo2no.prod.shawcable.com (shawmail.shawcable.com [64.59.128.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C6BE43D49 for ; Fri, 23 Jun 2006 08:10:34 +0000 (GMT) (envelope-from miki@wisedot.ca) Received: from bpd2mi6no.prod.shawcable.com (bpd2mi6no-qfe3.prod.shawcable.com [10.0.184.161]) by bpd2mo2no.prod.shawcable.com (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J1B00LAY00RMW60@bpd2mo2no.prod.shawcable.com> for freebsd-hardware@freebsd.org; Fri, 23 Jun 2006 02:10:03 -0600 (MDT) Received: from wisedota6635sx (S0106001217f998fd.vf.shawcable.net [70.69.34.22]) by bpd2mi6no.prod.shawcable.com (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J1B00AHY00RPLP0@bpd2mi6no.prod.shawcable.com> for freebsd-hardware@freebsd.org; Fri, 23 Jun 2006 02:10:03 -0600 (MDT) Date: Fri, 23 Jun 2006 01:10:07 -0700 From: "Miki Klein - Wisedot Technologies Inc." To: freebsd-hardware@freebsd.org Message-id: <000501c6969c$70933d00$7101a8c0@wisedota6635sx> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: IBM 440 8cpu +_ Raid 4LX X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2006 08:10:36 -0000 Hi, I am trying to install freebsd on IBM server. But the system hung up after the boot. (There is an error saying that there are more then 32 cpu id). I can turn ACPI off in this case the server will boot but without the raid. I tried FreeBSD live cd and it is running well but in single CPU. Need Help in this Issue Miki From owner-freebsd-hardware@FreeBSD.ORG Sat Jun 24 04:12:49 2006 Return-Path: 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 DDB6216A47E for ; Sat, 24 Jun 2006 04:12:49 +0000 (UTC) (envelope-from hcpo@ig.com.br) Received: from smtp-32.ig.com.br (smtp-32.ig.com.br [200.226.132.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98A8943D45 for ; Sat, 24 Jun 2006 04:12:48 +0000 (GMT) (envelope-from hcpo@ig.com.br) Received: (qmail 4217 invoked from network); 23 Jun 2006 13:51:40 -0000 Received: from wm114.ig.com.br (HELO localhost.localdomain) ([200.226.130.114]) (envelope-sender ) by email-32.ig.com.br (qmail-ldap-1.03) with SMTP for ; 23 Jun 2006 13:51:40 -0000 To: freebsd-hardware@freebsd.org From: hcpo Date: Fri, 23 Jun 2006 10:51:39 -0300 X-Priority: 3 (Normal) Message-ID: <20060623_135139_076089.hcpo@ig.com.br> X-Originating-IP: [200.226.130.114]192.168.100.74, 200.255.206.1 X-Mailer: iGMail [www.ig.com.br] X-user: hcpo@ig.com.br Teste: asaes MIME-Version: 1.0 Content-type: multipart/mixed; boundary="Message-Boundary-by-Mail-Sender-1151070699" Subject: freebsd x serveredge 1400sc X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2006 04:12:49 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --Message-Boundary-by-Mail-Sender-1151070699 Content-type: text/plain; charset=ISO-8859-1 Content-description: Mail message body Content-transfer-encoding: 8bit Content-disposition: inline HI, I installed Freebsd 6.0 p1 in a Dell ServerEdge 1400SC for a proxy/firewall server. System reboots once at each two or three days. Is there any incompatibility between Frebsd and Dell ServerEdge 1400SC. Configuration Server: Pentium III 850, 1Gb RAM, 2x 18Gb HD, raid 0 using motherboard scsi controllers. Tks, Herminio --Message-Boundary-by-Mail-Sender-1151070699--