From owner-freebsd-hardware Sun Oct 8 0:48:14 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail1.mia.bellsouth.net (mail1.mia.bellsouth.net [205.152.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 9CE0C37B503; Sun, 8 Oct 2000 00:48:11 -0700 (PDT) Received: from www.goldendeckcasino.com (adsl-61-143-206.mia.bellsouth.net [208.61.143.206]) by mail1.mia.bellsouth.net (3.3.5alt/0.75.2) with SMTP id DAA23363; Sun, 8 Oct 2000 03:44:20 -0400 (EDT) From: bubblehead32@hotmail.com Message-Id: <200010080744.DAA23363@mail1.mia.bellsouth.net> To: <> Subject: WOW!!! Highest Payouts Around!!!!!!!! Date: Sun, 08 Oct 2000 03:38:02 -0400 X-Sender: bubblehead32@hotmail.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 X-MSMail-Priority: Normal Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Its just like being there. Go to www.goldendeckcasino.com/goldendeckcasino/links/2769.html. If you would like to be removed from these mailings in the future please mailto:bubblehead32@hotmail.com?subject=remove To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Oct 8 10:42:36 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from gabriel.schoolpeople.net (gabriel.schoolpeople.net [216.34.170.167]) by hub.freebsd.org (Postfix) with ESMTP id 32E5837B66C for ; Sun, 8 Oct 2000 10:42:34 -0700 (PDT) Received: from dopey (cs2714-158.austin.rr.com [24.27.14.158]) by gabriel.schoolpeople.net (8.9.3/8.9.3) with SMTP id MAA00759; Sun, 8 Oct 2000 12:39:59 -0500 (CDT) (envelope-from brandon@schoolpeople.net) Message-ID: <003301c0314e$d375d9a0$0501a8c0@dopey> From: "Brandon DeYoung" To: "Francisco Reyes" , References: <200010072155.RAA28099@sanson.reyes.somos.net> Subject: Re: RELEASE 4.1.1 and 3Ware controllers Date: Sun, 8 Oct 2000 12:40:18 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yes, I burned the disk from ISO, it's a 3Ware 5200. See Mike Smith's response. ~B ----- Original Message ----- From: Francisco Reyes To: Brandon DeYoung ; Sent: Saturday, October 07, 2000 4:57 PM Subject: Re: RELEASE 4.1.1 and 3Ware controllers > On Wed, 4 Oct 2000 11:58:42 -0500, Brandon DeYoung wrote: > > >I'm booting to the 4.1.1 CD and geting "no disks found". When I'd expect to see the fdisk screen. > >Any work arounds? > >~Brandon > > For starters there was no 4.1.1 CD, unless you burnt it yourself > from ISO. > Which 3ware are you trying this on? > When the machine is booting does the 3ware card announces itself > and are you able to go into it's setup? > > > francisco > Moderator of the Corporate BSD list > http://www.egroups.com/group/BSD_Corporate > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Oct 8 18:21:46 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from home.ecn.ab.ca (fn2.freenet.edmonton.ab.ca [198.161.206.7]) by hub.freebsd.org (Postfix) with ESMTP id 9508237B502 for ; Sun, 8 Oct 2000 18:21:40 -0700 (PDT) Received: from fn2.freenet.edmonton.ab.ca (0@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by home.ecn.ab.ca (8.8.7/8.7.3) with ESMTP id TAA76012 for ; Sun, 8 Oct 2000 19:21:39 -0600 Received: from freenet.edmonton.ab.ca (835@freenet.edmonton.ab.ca [198.161.206.2]) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id TAA75484 for ; Sun, 8 Oct 2000 19:21:27 -0600 Received: from localhost (ron@localhost) by freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id TAA58274 for ; Sun, 8 Oct 2000 19:21:26 -0600 Date: Sun, 8 Oct 2000 19:21:26 -0600 (MDT) From: Ronald Grootkarzyn To: freebsd-hardware@FreeBSD.ORG Subject: Choosing CUSL2 or CUV4X ASUS M/B? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am considering an ASUS CUSL2 'Solano 2' M/B. I am concerned that the 815e graphics and AGP memory controller chipset may cause problems with both the custom kernel and XFree86? Or would a more conserative M/B, such as the CUV4X be an apppropriate choice? Other suggestions based on the 370 CPU config will also be welcome! I am looking forward to a system that will have several years of compatiblity with current hardware trends and prove to be agreeable to FreeBSD development trends as well. Ronald Grootkarzyn email: ron@freenet.edmonton.ab.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Oct 8 18:58: 2 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id A218337B502 for ; Sun, 8 Oct 2000 18:57:59 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e991xwh03214; Sun, 8 Oct 2000 18:59:58 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010090159.e991xwh03214@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Ronald Grootkarzyn Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Choosing CUSL2 or CUV4X ASUS M/B? In-reply-to: Your message of "Sun, 08 Oct 2000 19:21:26 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Oct 2000 18:59:58 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am considering an ASUS CUSL2 'Solano 2' M/B. I am concerned that the > 815e graphics and AGP memory controller chipset may cause problems with > both the custom kernel and XFree86? Or would a more conserative M/B, such > as the CUV4X be an apppropriate choice? Other suggestions based on the > 370 CPU config will also be welcome! The 810/815 chipsets are pretty bargain-basement; you should expect support, but I wouldn't be encouraging them for serious work. The 440BX-based board will perform better. > I am looking forward to a system that will have several years of > compatiblity with current hardware trends and prove to be agreeable to > FreeBSD development trends as well. If your budget can handle it, consider the CUR-DLS. Bear in mind that memory for it is a little more expensive. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Oct 8 19:59:15 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from home.ecn.ab.ca (fn2.freenet.edmonton.ab.ca [198.161.206.7]) by hub.freebsd.org (Postfix) with ESMTP id 06F2737B66D for ; Sun, 8 Oct 2000 19:59:13 -0700 (PDT) Received: from fn2.freenet.edmonton.ab.ca (0@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by home.ecn.ab.ca (8.8.7/8.7.3) with ESMTP id UAA62840 for ; Sun, 8 Oct 2000 20:59:11 -0600 Received: from freenet.edmonton.ab.ca (835@freenet.edmonton.ab.ca [198.161.206.2]) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id UAA35690 for ; Sun, 8 Oct 2000 20:59:07 -0600 Received: from localhost (ron@localhost) by freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id UAA53304 for ; Sun, 8 Oct 2000 20:59:05 -0600 Date: Sun, 8 Oct 2000 20:59:05 -0600 (MDT) From: Ronald Grootkarzyn To: freebsd-hardware@FreeBSD.ORG Subject: Re: Choosing CUSL2 or CUV4X ASUS M/B? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 8 Oct 2000, Ronald Grootkarzyn wrote: > I am considering an ASUS CUSL2 'Solano 2' M/B. I am concerned that the > 815e graphics and AGP memory controller chipset may cause problems with > both the custom kernel and XFree86? Or would a more conserative M/B, such > as the CUV4X be an apppropriate choice? Other suggestions based on the > 370 CPU config will also be welcome! > > I am looking forward to a system that will have several years of > compatiblity with current hardware trends and prove to be agreeable to > FreeBSD development trends as well. > > Ronald Grootkarzyn > email: ron@freenet.edmonton.ab.ca > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > Ronald Grootkarzyn email: ron@freenet.edmonton.ab.ca 4013 - 114 Avenue phone: (403) 479-2672 Edmonton, AB, T5W 0S9 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 3:14:45 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from psismtp1.psi.airtel.es (back.airtel.net [212.73.32.158]) by hub.freebsd.org (Postfix) with ESMTP id 39A4437B66C; Mon, 9 Oct 2000 03:14:41 -0700 (PDT) Received: from pccarlos ([212.166.134.124]) by psismtp1.psi.airtel.es (ESMTP service) with SMTP id G25R4702.TH3; Mon, 9 Oct 2000 12:14:31 +0200 From: "Carlos Asensio" To: Cc: Subject: Thosiba PORTEGE 7200 Date: Mon, 9 Oct 2000 12:13:36 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I am traying to configure my Xfree 4.0.1 in order to work with this computer. It is a Toshiba laptop. Its video card is a Trident Cyberblade e4-128 PCI/AGP. I haven't been able to set it up. Can anyone help me? Is this card supported by Xfree86? Thanks in advance Regards Carlos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 5:50:19 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail-sp.viplink.com.br (baco.viplink.com.br [200.211.188.87]) by hub.freebsd.org (Postfix) with ESMTP id 9CC1C37B66C; Mon, 9 Oct 2000 05:50:12 -0700 (PDT) Received: from ROMAMK (200.211.188.76 [200.211.188.76]) by mail-sp.viplink.com.br with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id T6Z5Z7Q0; Mon, 9 Oct 2000 09:51:01 -0300 Message-ID: <000901c031f7$f68d1c60$0a06030a@visionmis.com.br> Reply-To: "Samuka" From: "Samuka" To: , Subject: Two Wavelan in the same machine Date: Mon, 9 Oct 2000 10:50:58 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, everybody Could you help me ? I have tried put two wavelan card with two isa adapter in the same machine, but i not have had success on many release (3.0,3.4,4.0). Have someody some solution, scripts or another thing for do it ? Tks Samuka To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 7:33:51 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from white.dogwood.com (white.dogwood.com [63.96.228.130]) by hub.freebsd.org (Postfix) with ESMTP id 6E78C37B502; Mon, 9 Oct 2000 07:33:48 -0700 (PDT) Received: (from dave@localhost) by white.dogwood.com (8.11.1/8.9.3) id e99EXm097119; Mon, 9 Oct 2000 07:33:48 -0700 (PDT) (envelope-from dave) From: Dave Cornejo Message-Id: <200010091433.e99EXm097119@white.dogwood.com> Subject: WEP keys for an driver To: freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Date: Mon, 9 Oct 2000 07:33:47 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org my apologies if i am not following the correct procedures here... I have submitted a patch in PR kern/21843 which adds WEP key support to the an driver. This is my first attempt at messing with driver code so any constructive criticism is appreciated. I have tested the patch with the hardware available to me and it seems to work well (I've used Aironet firmware 3.98 & an as yet unreleased version). If there's any interest and I can get permission to, I'm working on a firmware upgrade program next... dave -- Dave Cornejo @ Dogwood Media, Fremont, California "There aren't any monkeys chasing us..." - Xochi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 8:55: 7 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id 6B81337B502; Mon, 9 Oct 2000 08:55:02 -0700 (PDT) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id IAA42985; Mon, 9 Oct 2000 08:51:46 -0700 (PDT) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id IAA30329; Mon, 9 Oct 2000 08:51:23 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200010091551.IAA30329@whistle.com> Subject: Re: WEP keys for an driver In-Reply-To: <200010091433.e99EXm097119@white.dogwood.com> from Dave Cornejo at "Oct 9, 2000 07:33:47 am" To: Dave Cornejo Date: Mon, 9 Oct 2000 08:51:23 -0700 (PDT) Cc: freebsd-hardware@FreeBSD.org, freebsd-hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dave Cornejo writes: | my apologies if i am not following the correct procedures here... | | I have submitted a patch in PR kern/21843 which adds WEP key support | to the an driver. This is my first attempt at messing with driver | code so any constructive criticism is appreciated. | | I have tested the patch with the hardware available to me and it seems | to work well (I've used Aironet firmware 3.98 & an as yet unreleased | version). Looking at the code I don't see this as a complete solution. Maybe that is what you mean by: The ioctl interface used to configure the card does not include a way to set WEP keys If you look at http://www.ambrisko.com/doug/an.patch.wep. It includes the changes to both sides to enable WEP in the various modes and the various keys. I've been to busy to submit this, but I finally did today. Some people have been using this code with success. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 11:42:39 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from white.dogwood.com (white.dogwood.com [63.96.228.130]) by hub.freebsd.org (Postfix) with ESMTP id 7541B37B502; Mon, 9 Oct 2000 11:42:33 -0700 (PDT) Received: (from dave@localhost) by white.dogwood.com (8.11.1/8.9.3) id e99IgWd05020; Mon, 9 Oct 2000 11:42:32 -0700 (PDT) (envelope-from dave) From: Dave Cornejo Message-Id: <200010091842.e99IgWd05020@white.dogwood.com> Subject: Re: WEP keys for an driver In-Reply-To: <200010091551.IAA30329@whistle.com> from Doug Ambrisko at "Oct 9, 2000 08:51:23 am" To: Doug Ambrisko Date: Mon, 9 Oct 2000 11:42:32 -0700 (PDT) Cc: Dave Cornejo , freebsd-hardware@FreeBSD.org, freebsd-hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It doesn't matter to me which version gets used - I just need the capability to set the WEP keys. Some comments on your code: - WEP keysare variable length from 5-13 bytes, you should just check for >=5 & <=13 (it seems odd, but I have seen networks that use the odd sizes). - In an_setkeys() you allow 28 characters, the error message says 18, but really only 13 are significant. - The AN_RXMODE_LAN_MONITOR_CURBSS was a good catch - I never tested that one. - The authentication handling in ancontrol is in error: there is no AN_AUTH_TYPE_EXCLUDE_UNENCRYPTED bit. I should have added constants for the correct values for the authentication type. 0x000x - no encryption 0x010x - full encryption 0x030x - mixed cell (allow unencrypted) despite what's in the driver, bit 2 (0x0004) is not used. The bits as defined by Aironet engineering: #define AN_AUTHTYPE_PRIVACY_IN_USE 0x0100 #define AN_AUTHTYPE_ALLOW_UNENCRYPTED 0x0200 I would like to see my structure changes checked in - there are an error or two and some interesting new elements in there. In some more recent radio firmware, they provide normalized RSSI, and the IP address of the base station. There are also a few other things hinted at in there that some may find interesting. I should however add in some more constants. I didn't provide patches to ancontrol as you did, but I find ancontrol is getting way too nasty with its switches. Your patches look fine to me except that I'd really like to see a better way to specify volatile vs. persistent keys. dave c Doug Ambrisko wrote: > Looking at the code I don't see this as a complete solution. Maybe that > is what you mean by: > The ioctl interface used to configure the card does not include > a way to set WEP keys > > If you look at http://www.ambrisko.com/doug/an.patch.wep. It includes > the changes to both sides to enable WEP in the various modes and the > various keys. > > I've been to busy to submit this, but I finally did today. Some people > have been using this code with success. -- Dave Cornejo @ Dogwood Media, Fremont, California "There aren't any monkeys chasing us..." - Xochi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 11:59:16 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 9D6F837B503; Mon, 9 Oct 2000 11:59:12 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e99Iwlk03981; Mon, 9 Oct 2000 11:58:47 -0700 Date: Mon, 9 Oct 2000 11:58:47 -0700 From: Brooks Davis To: Dave Cornejo Cc: Doug Ambrisko , freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: WEP keys for an driver Message-ID: <20001009115847.A2570@Odin.AC.HMC.Edu> References: <200010091551.IAA30329@whistle.com> <200010091842.e99IgWd05020@white.dogwood.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200010091842.e99IgWd05020@white.dogwood.com>; from dave@dogwood.com on Mon, Oct 09, 2000 at 11:42:32AM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Oct 09, 2000 at 11:42:32AM -0700, Dave Cornejo wrote: > Some comments on your code: > - WEP keysare variable length from 5-13 bytes, you should just check for > >=5 & <=13 (it seems odd, but I have seen networks that use the odd > sizes). Since all the windows drivers I've looked at only allow 0, 5, and 13 byte keys, I'd suggest only allowing those values. That's what wicontrol does. > I didn't provide patches to ancontrol as you did, but I find ancontrol > is getting way too nasty with its switches. Your patches look fine > to me except that I'd really like to see a better way to specify > volatile vs. persistent keys. You need to add ancontrol support or the patch is basicaly useless. I'm looking forward to some sort of working crypto support for the aironet cards. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 12:20:23 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id C8F3037B670; Mon, 9 Oct 2000 12:20:15 -0700 (PDT) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA53386; Mon, 9 Oct 2000 12:19:49 -0700 (PDT) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id MAA33332; Mon, 9 Oct 2000 12:19:46 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200010091919.MAA33332@whistle.com> Subject: Re: WEP keys for an driver In-Reply-To: <200010091842.e99IgWd05020@white.dogwood.com> from Dave Cornejo at "Oct 9, 2000 11:42:32 am" To: Dave Cornejo Date: Mon, 9 Oct 2000 12:19:46 -0700 (PDT) Cc: Doug Ambrisko , freebsd-hardware@FreeBSD.org, freebsd-hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dave Cornejo writes: | It doesn't matter to me which version gets used - I just need the | capability to set the WEP keys. | | Some comments on your code: | - WEP keysare variable length from 5-13 bytes, you should just check for | >=5 & <=13 (it seems odd, but I have seen networks that use the odd | sizes). Really ... I need to check the WEP configurator again on Windows. I thought when I tried it it only let me do 40 or 128 not in between. Also it also it only excepted a hex string (the base code from wicontrol accepted an ASCII string as well). | - In an_setkeys() you allow 28 characters, the error message says 18, | but really only 13 are significant. Right 28 = max of "0x" + 2 * byte (5 or 13). So 2 + 2 * 13 = 28. That 18 sounds like a bug (stale cut'n'paste). | - The AN_RXMODE_LAN_MONITOR_CURBSS was a good catch - I never tested | that one. Running tcpdump kept bitting me. Hey why did ping stop :-( | - The authentication handling in ancontrol is in error: there is no | AN_AUTH_TYPE_EXCLUDE_UNENCRYPTED bit. I should have added constants | for the correct values for the authentication type. | | 0x000x - no encryption | 0x010x - full encryption | 0x030x - mixed cell (allow unencrypted) In my manual on page 7-51 in the table for General Configuration Parameters: +0x003E AuthenticationType 0x01 Open 0x02 Shared-Key 0x04 Exclude Unencrypted So this is were I got it. I have DOC 710-004247, Rev B1. I'm not sure what you are reading or maybe talking about. It almost sounds that you are talking binary instead of hex. BTW I didn't ever get "Exclude Unencrypted" to do anything usefull if I recall. So maybe my documentation is wrong. If you have a newer one could you send it to me? I'm on my second version of the manual. | despite what's in the driver, bit 2 (0x0004) is not used. The bits as | defined by Aironet engineering: | | #define AN_AUTHTYPE_PRIVACY_IN_USE 0x0100 | #define AN_AUTHTYPE_ALLOW_UNENCRYPTED 0x0200 AN_AUTHTYPE_ALLOW_UNENCRYPTED seems to be a new one. Actually the are both not listed in my manual. I derived it from the posting by an Aironet engineer on the Linux driver mailing list. Where did you find out about 0x100 & 0x200? | I would like to see my structure changes checked in - there are an | error or two and some interesting new elements in there. In some more | recent radio firmware, they provide normalized RSSI, and the IP | address of the base station. There are also a few other things hinted | at in there that some may find interesting. I should however add in | some more constants. I don't have any problem with that. I was just worked on getting WEP going. | I didn't provide patches to ancontrol as you did, but I find ancontrol | is getting way too nasty with its switches. Your patches look fine | to me except that I'd really like to see a better way to specify | volatile vs. persistent keys. Agreed. It did not fit in with the "primative" model that the WaveLan cards use. I tried to make it as clean as possible with the 3 flags: - set any key - set mode - turn WEP on/off (looks like this needs to be expanded to allow unencrypted traffic) Unfortanetly I has to do some stuff in ancontrol to virtualize the different register for the last 2 since they are munge into on but should but are treated separetly in the Windows UI. Linux just sets them for and doesn't give you this flexibility so you may not be able to interoperate in a valid windows network. However, without the ancontrol changes it becomes difficult to set these things from a user perspective. Thanks for the review. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 12:32:33 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from white.dogwood.com (white.dogwood.com [63.96.228.130]) by hub.freebsd.org (Postfix) with ESMTP id B33C137B502 for ; Mon, 9 Oct 2000 12:32:29 -0700 (PDT) Received: (from dave@localhost) by white.dogwood.com (8.11.1/8.9.3) id e99JWMG06801; Mon, 9 Oct 2000 12:32:22 -0700 (PDT) (envelope-from dave) From: Dave Cornejo Message-Id: <200010091932.e99JWMG06801@white.dogwood.com> Subject: Re: WEP keys for an driver In-Reply-To: <20001009115847.A2570@Odin.AC.HMC.Edu> from Brooks Davis at "Oct 9, 2000 11:58:47 am" To: Brooks Davis Date: Mon, 9 Oct 2000 12:32:22 -0700 (PDT) Cc: Dave Cornejo , Doug Ambrisko , freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORGG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brooks Davis wrote: > Since all the windows drivers I've looked at only allow 0, 5, and 13 > byte keys, I'd suggest only allowing those values. That's what > wicontrol does. I guess my feeling is that it's an artificial restriction. I dunno if anyone really uses odd sized keys, but why limit them? > > I didn't provide patches to ancontrol as you did, but I find ancontrol > > is getting way too nasty with its switches. Your patches look fine > > to me except that I'd really like to see a better way to specify > > volatile vs. persistent keys. > > You need to add ancontrol support or the patch is basicaly useless. I'm > looking forward to some sort of working crypto support for the aironet > cards. Agreed, but I wanted to push getting those patches into the driver so something would get moving :-) It looks like I prodded someone else with a similar patch including ancontrol to get around to submitting his fix. Hopefully we can work together to solve the problems in both of our patches and get something useful out of it. I do have my own version of ancontrol that I am using, but it does things I've not gotten fully cleared to release yet. dave c -- Dave Cornejo @ Dogwood Media, Fremont, California "There aren't any monkeys chasing us..." - Xochi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 12:40: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id EF93C37B66D; Mon, 9 Oct 2000 12:40:04 -0700 (PDT) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA54330; Mon, 9 Oct 2000 12:30:49 -0700 (PDT) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id MAA33408; Mon, 9 Oct 2000 12:30:19 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200010091930.MAA33408@whistle.com> Subject: Re: WEP keys for an driver In-Reply-To: <20001009115847.A2570@Odin.AC.HMC.Edu> from Brooks Davis at "Oct 9, 2000 11:58:47 am" To: Brooks Davis Date: Mon, 9 Oct 2000 12:30:19 -0700 (PDT) Cc: Dave Cornejo , Doug Ambrisko , freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brooks Davis writes: | On Mon, Oct 09, 2000 at 11:42:32AM -0700, Dave Cornejo wrote: | > Some comments on your code: | > - WEP keysare variable length from 5-13 bytes, you should just check for | > >=5 & <=13 (it seems odd, but I have seen networks that use the odd | > sizes). | | Since all the windows drivers I've looked at only allow 0, 5, and 13 | byte keys, I'd suggest only allowing those values. That's what | wicontrol does. That's what I recall from Windows and I allow 0, 5 or 13 characters as 0 -> erase key 0xDDDDDDDDDD -> set 40 bit 0xDDDDDDDDDDDDDDDDDDDDDDDDDD -> set 128 bit I also verified it did the right thing by booting back into Windows and then running the WEP utility to see if it made the right change. Also did it as hex since that is what the WEP utility did. The code would probably work with ASCII strings but how do you encode 0-255 as a character in an ASCII string? BTW my test string was 0x001122334455 (for 40 bit). Originally I wasn't doing a 40 bit or 128 and things didn't work. Once I started doing 40 bit or 128 bit keys then things worked fine. Since the programming doc didn't say anything about that I burned a few days on that :-( | > I didn't provide patches to ancontrol as you did, but I find ancontrol | > is getting way too nasty with its switches. Your patches look fine | > to me except that I'd really like to see a better way to specify | > volatile vs. persistent keys. | | You need to add ancontrol support or the patch is basicaly useless. I'm | looking forward to some sort of working crypto support for the aironet | cards. Well if you just download mine for now again at www.ambrisko.com/doug/an.patch.wep That will get you going. Some people other then myself are using it with success. It looks like it will get some more features since it looks like he has gleaned some more knowledge then I was told. Give it a try and let me know if you run into a problem. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 14: 2:40 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from home.ecn.ab.ca (fn2.freenet.edmonton.ab.ca [198.161.206.7]) by hub.freebsd.org (Postfix) with ESMTP id 3398637B503 for ; Mon, 9 Oct 2000 14:02:37 -0700 (PDT) Received: from fn2.freenet.edmonton.ab.ca (0@fn2.freenet.edmonton.ab.ca [198.161.206.7]) by home.ecn.ab.ca (8.8.7/8.7.3) with ESMTP id PAA54902 for ; Mon, 9 Oct 2000 15:02:35 -0600 Received: from freenet.edmonton.ab.ca (835@freenet.edmonton.ab.ca [198.161.206.2]) by fn2.freenet.edmonton.ab.ca (8.8.7/8.7.3) with ESMTP id PAA54882 for ; Mon, 9 Oct 2000 15:02:26 -0600 Received: from localhost (ron@localhost) by freenet.edmonton.ab.ca (8.8.7/8.7.3) with SMTP id PAA26018 for ; Mon, 9 Oct 2000 15:02:25 -0600 Date: Mon, 9 Oct 2000 15:02:24 -0600 (MDT) From: Ronald Grootkarzyn To: freebsd-hardware@FreeBSD.ORG Subject: Summary: Choosing CUSL2 or CUV4X M/B Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks to all those whom responded; It is clear through reading the FAQ's, Handbook and the comments from this newsgroup, that a better choice would be a motherboard with a (440)BX chipset. I have found two supporting the socket 370, an ASUS CUBX and the ABIT BX133(?). sincerely ron Ronald Grootkarzyn email: ron@freenet.edmonton.ab.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 17:20:29 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from irv1-mail2.intelenet.net (irv1-mail2.intelenet.net [204.182.160.3]) by hub.freebsd.org (Postfix) with ESMTP id B579137B503 for ; Mon, 9 Oct 2000 17:20:27 -0700 (PDT) Received: from nimba.intelenet.net (nimba.intelenet.net [207.38.65.93]) by irv1-mail2.intelenet.net (8.9.3/8.9.3) with ESMTP id RAA17919 for ; Mon, 9 Oct 2000 17:20:27 -0700 (PDT) Received: by nimba.intelenet.net (Postfix, from userid 1294) id 5823E83C05; Mon, 9 Oct 2000 17:20:24 -0700 (PDT) Date: Mon, 9 Oct 2000 17:20:23 -0700 From: matthew zeier To: freebsd-hardware@freebsd.org Subject: panic: NMI indicates hardware failure Message-ID: <20001009172022.A12975@intelenet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm not sure how to understand this error: panic: NMI indicates hardware failure It causes the box to reboot. What is NMI? How can I tell what hardware has failed? How can I fix this? I'm running 4.1.1 with GENERIC + IPFilter on an Intel ISP 2150 with a Mylex 150 RAID controller. - mz -- matthew zeier - "There ain't no rules around here. We're trying to accomplish something." - Thomas Edison To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 9 22:33:16 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1617237B66D; Mon, 9 Oct 2000 22:33:11 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9A5X9Y11369; Mon, 9 Oct 2000 23:33:09 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA23139; Mon, 9 Oct 2000 23:33:08 -0600 (MDT) Message-Id: <200010100533.XAA23139@harmony.village.org> To: "Samuka" Subject: Re: Two Wavelan in the same machine Cc: freebsd-hardware@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Mon, 09 Oct 2000 10:50:58 -0300." <000901c031f7$f68d1c60$0a06030a@visionmis.com.br> References: <000901c031f7$f68d1c60$0a06030a@visionmis.com.br> Date: Mon, 09 Oct 2000 23:33:07 -0600 From: Warner Losh Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <000901c031f7$f68d1c60$0a06030a@visionmis.com.br> "Samuka" writes: : I have tried put two wavelan card with two isa adapter in the same machine, : but i not have had success on many release (3.0,3.4,4.0). : Have someody some solution, scripts or another thing for do it ? I think that pccardd needs to be hacked to support this. You might be able to do it with multiple config lines: # Lucent WaveLAN/IEEE card "Lucent Technologies" "WaveLAN/IEEE" config 0x1 "wi0" ? config 0x1 "wi1" ? insert /etc/pccard_ether $device remove /sbin/ifconfig $device delete but I don't know if that will work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 10 10:30:34 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from d902.iki.rssi.ru (d902.iki.rssi.ru [193.232.9.10]) by hub.freebsd.org (Postfix) with ESMTP id 2D52037B66C for ; Tue, 10 Oct 2000 10:30:31 -0700 (PDT) Received: from FISH ([193.232.9.87]) by d902.iki.rssi.ru (8.9.3/8.9.3) with SMTP id VAA06942 for ; Tue, 10 Oct 2000 21:30:25 +0400 (MSD) From: Alexander Degay To: freebsd-hardware@freebsd.org Subject: FreeBSD on HP NetServer LC 2000 - ????? Date: Tue, 10 Oct 2000 21:30:24 +0400 Organization: SMISLAB Reply-To: degay@d902.iki.rssi.ru Message-ID: <4hk6us0kpv3a8vqtnro36ihma0hpq1g6q0@4ax.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings ! Possible, we're forced to use HP NetServer LC2000 and want to know: is it possible to set up FreeBSD on such (non-standard we think) a platform? It seems, the RAID controller NetRAID-1Si now supported in version 4.1, but what about motherboard, etc? Maybe anyone already tries to set up? Be very grateful for any information. Alexander Degay. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 10 11:28:26 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from irv1-mail2.intelenet.net (irv1-mail2.intelenet.net [204.182.160.3]) by hub.freebsd.org (Postfix) with ESMTP id 94F3937B502; Tue, 10 Oct 2000 11:28:22 -0700 (PDT) Received: from nimba.intelenet.net (nimba.intelenet.net [207.38.65.93]) by irv1-mail2.intelenet.net (8.9.3/8.9.3) with ESMTP id LAA10240; Tue, 10 Oct 2000 11:28:22 -0700 (PDT) Received: by nimba.intelenet.net (Postfix, from userid 1294) id C97A283B56; Tue, 10 Oct 2000 11:28:21 -0700 (PDT) Date: Tue, 10 Oct 2000 11:28:21 -0700 From: matthew zeier To: freebsd-hardware@freebsd.org, freebsd-stable@freebsd.org Subject: fatal trap 19 ? Message-ID: <20001010112821.B23447@intelenet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="NMuMz9nt05w80d4+" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --NMuMz9nt05w80d4+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I got this on my box today: Fatal trap 19: non-maskable interrupt trap while in kernel mode instruction pointer =3D3D 0x8:0xc02158d6 stack pointer =3D3D 0x10:0xcd3cfe6c frame pointer =3D3D 0x10:0xcd3cfe84 code segment =3D3D base 0x0, limit 0xfffff, type 0x1b =3D3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D3D interrupt enabled, resume, IOPL =3D3D 0 current process =3D3D 71512 (perl) interrupt mask =3D3D none trap number =3D3D 19 panic: non-maskable interrupt trap syncing disks... 89 89 85 71 23=3D20 done Uptime: 18h7m34s --=20 matthew zeier - "There ain't no rules around here. We're trying to accomplish something." - Thomas Edison --NMuMz9nt05w80d4+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (SunOS) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjnjX8QACgkQ2vhH5UMgI9fC+QCdGuf/Hl3Iahb3qe0AQrUFxAiD hrAAnRKxdDZY8lup2BN/NHJ4RY53XzkJ =Tp+A -----END PGP SIGNATURE----- --NMuMz9nt05w80d4+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 10 11:38:59 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 50F6C37B66D; Tue, 10 Oct 2000 11:38:55 -0700 (PDT) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA00741; Tue, 10 Oct 2000 11:38:52 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200010101838.LAA00741@freeway.dcfinc.com> Subject: Re: fatal trap 19 ? In-Reply-To: <20001010112821.B23447@intelenet.net> from matthew zeier at "Oct 10, 0 11:28:21 am" To: matthew@intelenet.net (matthew zeier) Date: Tue, 10 Oct 2000 11:38:52 -0700 (MST) Cc: freebsd-hardware@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As I recall, matthew zeier wrote: > > > I got this on my box today: > > Fatal trap 19: non-maskable interrupt trap while in kernel mode > instruction pointer =3D 0x8:0xc02158d6 > stack pointer =3D 0x10:0xcd3cfe6c > frame pointer =3D 0x10:0xcd3cfe84 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 71512 (perl) > interrupt mask =3D none > trap number =3D 19 > panic: non-maskable interrupt trap > > syncing disks... 89 89 85 71 23=20 > done > Uptime: 18h7m34s On most PC hardware, a non-maskable interrupt is generated by the power supply. Some will generate an NMI if they have parity or ECC memory that detects an uncorrectable error. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 10 12:42:48 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from kheops.demo.telefonica.com.pe (kheops.demo.telefonica.com.pe [200.37.84.130]) by hub.freebsd.org (Postfix) with ESMTP id B522E37B66C; Tue, 10 Oct 2000 12:42:37 -0700 (PDT) Received: from elcsa20008 (khephren.demo.telefonica.com.pe [200.37.84.131]) by kheops.demo.telefonica.com.pe (8.11.0/8.11.0) with SMTP id e9AJjuj16510; Tue, 10 Oct 2000 14:45:56 -0500 (PET) Message-ID: <006201c032f2$0efd0030$4d01190a@tp.com.pe> From: "Richard Cotrina" To: Cc: Subject: Support for ESS Allegro-1 PCI Date: Tue, 10 Oct 2000 14:41:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, Does anyone know if FreeBSD have support for the sound card : ESS Allegro-1 PCI (ESS 1989) ? I have not seen anything related to this card in the Kernel LINT. (I am using FreeBSD 4.1-Release). I would preciate any help or information. Regards, Richard Cotrina To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 10 13:14:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from astra.domix.de (dial-213-168-73-38.netcologne.de [213.168.73.38]) by hub.freebsd.org (Postfix) with ESMTP id 94FEC37B502; Tue, 10 Oct 2000 13:14:28 -0700 (PDT) Received: (from dr@localhost) by astra.domix.de (8.11.0/8.11.0) id e9AKFtK02690; Tue, 10 Oct 2000 22:15:55 +0200 (CEST) (envelope-from dr) Date: Tue, 10 Oct 2000 22:15:55 +0200 From: Dominik Rothert To: Richard Cotrina Cc: freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Support for ESS Allegro-1 PCI Message-ID: <20001010221555.A2554@astra.local> Mail-Followup-To: Dominik Rothert , Richard Cotrina , freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG References: <006201c032f2$0efd0030$4d01190a@tp.com.pe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <006201c032f2$0efd0030$4d01190a@tp.com.pe>; from rcc@demo.telefonica.com.pe on Tue, Oct 10, 2000 at 02:41:16PM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Richard Cotrina wrote: > Does anyone know if FreeBSD have support for the sound card : > ESS Allegro-1 PCI (ESS 1989) ? pcm(4) supports ESS. -Dominik -- /* Dominik Rothert | dr@astorit.com * * A S T O R I T | http://www.astorit.com/ * * Hohenzollernring 52 | fon +49-221-251440 * * 50672 Cologne, Germany | fax +49-221-251443 */:wq! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 10 13:44: 3 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 060BA37B66C; Tue, 10 Oct 2000 13:43:59 -0700 (PDT) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA06985; Tue, 10 Oct 2000 16:43:31 -0400 (EDT) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id QAA07534; Tue, 10 Oct 2000 16:43:28 -0400 (EDT) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA07530; Tue, 10 Oct 2000 16:43:28 -0400 (EDT) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Tue, 10 Oct 2000 16:43:28 -0400 (EDT) From: Kenneth Wayne Culver To: Richard Cotrina Cc: freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Support for ESS Allegro-1 PCI In-Reply-To: <006201c032f2$0efd0030$4d01190a@tp.com.pe> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is not yet supported. I don't know if there are plans to support it or not. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 10 Oct 2000, Richard Cotrina wrote: > Greetings, > > Does anyone know if FreeBSD have support for the sound card : ESS Allegro-1 > PCI (ESS 1989) ? > I have not seen anything related to this card in the Kernel LINT. (I am > using FreeBSD 4.1-Release). > > I would preciate any help or information. > > > Regards, > > > Richard Cotrina > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 10 21:20:55 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 1C45C37B502 for ; Tue, 10 Oct 2000 21:20:53 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9B4Mmh04309; Tue, 10 Oct 2000 21:22:52 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010110422.e9B4Mmh04309@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: degay@d902.iki.rssi.ru Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD on HP NetServer LC 2000 - ????? In-reply-to: Your message of "Tue, 10 Oct 2000 21:30:24 +0400." <4hk6us0kpv3a8vqtnro36ihma0hpq1g6q0@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Oct 2000 21:22:48 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Greetings ! > > Possible, we're forced to use HP NetServer LC2000 > and want to know: is it possible to set up FreeBSD > on such (non-standard we think) a platform? Actually, these machines should be pretty stock. > It seems, the RAID controller NetRAID-1Si I would not expect any major problems with this system. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 10 21:34:34 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id E4F3E37B503 for ; Tue, 10 Oct 2000 21:34:31 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9B4abh04403; Tue, 10 Oct 2000 21:36:37 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010110436.e9B4abh04403@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: matthew zeier Cc: freebsd-hardware@freebsd.org Subject: Re: panic: NMI indicates hardware failure In-reply-to: Your message of "Mon, 09 Oct 2000 17:20:23 PDT." <20001009172022.A12975@intelenet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Oct 2000 21:36:36 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I'm not sure how to understand this error: > > panic: NMI indicates hardware failure > > > It causes the box to reboot. What is NMI? NMI stands for "non maskable interrupt", and it's a signal from the hardware indicating a critical failure. > How can I tell what hardware has failed? You can't, easily. 8( It's most likely a PCI SERR, probably caused by bad motherboard timing. > How can I fix this? Default your PCI configuration to begin with. Check that you're not overclocking anything. > I'm running 4.1.1 with GENERIC + IPFilter on an Intel ISP 2150 with a > Mylex 150 RAID controller. You might want to check that the Mylex controller is properly seated, and that it's using Mylex-certified RAM (if it's the memory it came with, it should be OK). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 11 6:18:40 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mtu.ru (ns.mtu.ru [195.34.32.10]) by hub.freebsd.org (Postfix) with ESMTP id DFAE737B503 for ; Wed, 11 Oct 2000 06:18:37 -0700 (PDT) X-Recipient: freebsd-hardware@freebsd.org Received: from design2.any (ppp103-38.dialup.mtu-net.ru [212.188.103.38]) by mtu.ru (Postfix) with ESMTP id AA048745C for ; Wed, 11 Oct 2000 17:18:04 +0400 (MSD) (envelope-from avn@any.ru) Date: Wed, 11 Oct 2000 17:13:06 +0400 From: "Alexey V.Neyman" X-Mailer: The Bat! (v1.39) Educational Reply-To: "Alexey V.Neyman" Organization: ANY X-Priority: 3 (Normal) Message-ID: <19717.001011@any.ru> To: freebsd-hardware@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Good day. I've encountered the following problem using Seagate STT20000A Hornet Travan 20Gb streamer (IDE, Travan 5, connected to primary IDE controller as slave), tape "Imation Travan5", under FreeBSD 3.3-RELEASE. Performing dump -0uc -d 67733 -f /dev/rwst0 / causes the following to be output by dump: [...first portion skipped, it looks like normal dump work...] DUMP: DUMP: 25933 tape blocks on 1 volume DUMP: finished in 68 seconds, throughput 381Kbytes/sec DUMP: level 0 dump on Wed Oct 11 16:51:37 2000 DUMP: closing /dev/rwst0 On this stage, IDE controller hangs. The following is displayed on the console: wst0: 26542080d total bytes transferred atapi0.1: controller not ready, status=c0 , error=c0 atapi0.1: controller not ready for cmd atapi0.1: controller not ready for cmd atapi0.1: controller not ready for cmd wst0: Sense media failed Has anybody encountered the same problem and found a solution? Best regards, Alexey. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 7:36:20 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id D51A937B502 for ; Fri, 13 Oct 2000 07:36:17 -0700 (PDT) Received: by moo.sysabend.org (Postfix, from userid 1004) id 5C87D755D; Fri, 13 Oct 2000 07:40:45 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 59C2B1D89 for ; Fri, 13 Oct 2000 07:40:45 -0700 (PDT) Date: Fri, 13 Oct 2000 07:40:45 -0700 (PDT) From: Jamie Bowden To: hardware@FreeBSD.org Subject: K7V problem? Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I recently upgraded my personal machine, and am having a problem attempting to install FreeBSD. It appears to be a hardware issue, which is why I'm sending this here. The machine in question is an Athlon/850 on an Asus K7V (BIOS 1007) with a 256M PC-133 DIMM. Motherboard devices are channel 1 of IDE controller, with LS-120 attached, serial 1 enabled, LPT enabled in ECP mode(DMA 3), two USB controllers, and floppy controller (no floppies drives, but no option to disable the onboard contoller). PCI devices are Creative 3D Blaster Annihilator2 (GeForce2 GTS 32MB AGP), Canopus Pure3D2 (Voodoo2 12MB), Intel EtherExpress Pro/100+, Adaptec 2940 UW SCSI, and SoundBlaster Live!. SCSI devices are IBM 4.3G UW, Seagate 4.0G UN, Plextor UltraPlex (32x), Plextor UltraPlex 40max, Plextor PlexWriter 8/20, and Archive Python 4mm DDS2 tape drive. The machine will not boot a FreeBSD cdrom, nor will it boot a FreeBSD floppy. Of interest is that it will boot a Windows NT cdrom, but not a Win98 floppy. It will boot Win9x(DOS) or NT install floppy just fine as well. When attempting to boot from the CD, the machine locks immediately after the adaptec card reports "SCSI BIOS installed successfully". Hard locks. requires hard reset. This is the same for a Win98 CD. Something in the way FBSD and Win98 load themselves into memory is obviously unhappy. If I attempt to boot from a floppy, the machine gets to the point where it reads from the floppy, and then stops. No output to screen of any sort. I can ctrl-alt-del at that point, so it's not as bad as the cd lockup. I'm considering maybe removing the LS-120 and trying a traditional floppy drive to see if that works, but I really like, and want to keep my LS-120 drive. The optimal solution is to figure out why it won't boot from the CD direct, but I'll take booting from floppy. As a side note, OS/2 warp boots most of it's second floppy, but dies as well. I'm certain OS/2's problem is complete lack of clue on how to deal with the LS-120 though. I'm sure others out there are using this motherboard, and I would really appreciate any input that can be offered. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 7:43:15 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from thor.theseus.com (south.theseus.com [63.74.60.130]) by hub.freebsd.org (Postfix) with ESMTP id D9A4137B502 for ; Fri, 13 Oct 2000 07:43:11 -0700 (PDT) Received: from spanky.theseus.com (spanky.theseus.com [192.168.0.51]) by thor.theseus.com (8.9.3/8.9.3) with SMTP id KAA13225; Fri, 13 Oct 2000 10:41:03 -0400 From: Bryan -TheBS- Smith Reply-To: thebs@smithconcepts.com, thebs@theseus.com Organization: (Personal Contact Info) To: Jamie Bowden Subject: Re: K7V problem? <- Make sure DIMM is in slot 1 Date: Fri, 13 Oct 2000 10:36:05 -0400 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain References: In-Reply-To: Cc: hardware@FreeBSD.ORG MIME-Version: 1.0 Message-Id: <0010131041030T.12156@spanky.theseus.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Re: K7V problem? <- Make sure DIMM is in slot 1 On Fri, 13 Oct 2000, Jamie Bowden wrote: > The machine in question is an Athlon/850 on an Asus K7V (BIOS 1007) with a > 256M PC-133 DIMM. > ... > When attempting to boot from the CD, the machine locks immediately after > the adaptec card reports "SCSI BIOS installed successfully". Hard locks. > requires hard reset. This is the same for a Win98 CD. Something in the > way FBSD and Win98 load themselves into memory is obviously unhappy. > ... 9 times out of 10, the problem I have with registered DIMMs (256MB+) as well as PC133 is the failure to put the DIMMs in slot order. That means first DIMM in slot 1, second in slot 2, etc... Every mainboard manual says this and you could get away with it in the pasta, but on these faster/registered DIMM modules, its now a requirement most of the time. BTW, DIMM 1 is NOT always the DIMM closest to the CPU. In fact, my Abit BP6 and KT7 mainboards have DIMM 1 farthest from the CPU. Many other boards are similar. I have been trying to get the word out to major resellers about this. I have had at least a half dozen tech support departments thank me about this over the last month or so. -- TheBS P.S. Another thing: Be more conservative with your settings in your BIOS/CMOS. Start extremely conservative, then tweak. I'll take several weeks to get them exact (meaning run for hours with each). -- Bryan "TheBS" Smith PERSONAL CONTACT INFO *********************************************************** Chat: thebs413 @ AOL/MSN/Yahoo (see http://Everybuddy.com) Email: mailto:thebs@smithconcepts.com,thebs@theseus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 7:54:58 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 2DC5B37B502 for ; Fri, 13 Oct 2000 07:54:56 -0700 (PDT) Received: by moo.sysabend.org (Postfix, from userid 1004) id BBA22755D; Fri, 13 Oct 2000 07:59:20 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id B8FCA1D89; Fri, 13 Oct 2000 07:59:20 -0700 (PDT) Date: Fri, 13 Oct 2000 07:59:20 -0700 (PDT) From: Jamie Bowden To: thebs@smithconcepts.com, thebs@theseus.com Cc: hardware@FreeBSD.ORG Subject: Re: K7V problem? <- Make sure DIMM is in slot 1 In-Reply-To: <0010131041030T.12156@spanky.theseus.com> Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 13 Oct 2000, Bryan -TheBS- Smith wrote: :Re: K7V problem? <- Make sure DIMM is in slot 1 DIMM1 is in slot1. I didn't think to mention this, but yes, I checked that. :P.S. Another thing: Be more conservative with your settings in :your BIOS/CMOS. Start extremely conservative, then tweak. I'll :take several weeks to get them exact (meaning run for hours with :each). My BIOS settings are pretty dull. I don't overclock, and I disable anything I don't need. I'd turn the floppy controller off if I had the option. Except for designating memory speed, and disabling unneccessary devices, the BIOS settings are factory default. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 8: 6:46 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mtu.ru (ns.mtu.ru [195.34.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 94B0137B502 for ; Fri, 13 Oct 2000 08:06:43 -0700 (PDT) X-Recipient: freebsd-hardware@freebsd.org Received: from design2.any (ppp106-149.dialup.mtu-net.ru [212.188.106.149]) by mtu.ru (Postfix) with ESMTP id 779C67499 for ; Fri, 13 Oct 2000 19:06:39 +0400 (MSD) (envelope-from avn@any.ru) Date: Fri, 13 Oct 2000 19:01:45 +0400 From: "Alexey V.Neyman" X-Mailer: The Bat! (v1.39) Educational Reply-To: "Alexey V.Neyman" Organization: ANY X-Priority: 3 (Normal) Message-ID: <13792.001013@any.ru> To: freebsd-hardware@freebsd.org Subject: Seagate Hornet/FreeBSD3.3-R problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Good day. I've encountered the following problem using Seagate STT20000A Hornet Travan 20Gb streamer (IDE, Travan 5, connected to primary IDE controller as slave), tape "Imation Travan5", under FreeBSD 3.3-RELEASE. Performing dump -0uc -d 67733 -f /dev/rwst0 / causes the following to be output by dump: [...first portion skipped, it looks like normal dump work...] DUMP: DUMP: 25933 tape blocks on 1 volume DUMP: finished in 68 seconds, throughput 381Kbytes/sec DUMP: level 0 dump on Wed Oct 11 16:51:37 2000 DUMP: closing /dev/rwst0 On this stage, IDE controller hangs. The following is displayed on the console: wst0: 26542080d total bytes transferred atapi0.1: controller not ready, status=c0 , error=c0 atapi0.1: controller not ready for cmd atapi0.1: controller not ready for cmd atapi0.1: controller not ready for cmd wst0: Sense media failed Has anybody encountered the same problem and found a solution? Best regards, Alexey. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 8:36:16 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id F349737B66E for ; Fri, 13 Oct 2000 08:36:14 -0700 (PDT) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id e9DFaAL13073; Fri, 13 Oct 2000 08:36:10 -0700 (PDT) Date: Fri, 13 Oct 2000 08:36:10 -0700 (PDT) From: Jin Guojun (DSD staff) Message-Id: <200010131536.e9DFaAL13073@portnoy.lbl.gov> To: ragnar@sysabend.org, thebs@smithconcepts.com, thebs@theseus.com Subject: Re: K7V problem? <- Make sure DIMM is in slot 1 Cc: hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bryan -TheBS- Smith wrote: > > The machine in question is an Athlon/850 on an Asus K7V (BIOS 1007) with a > > 256M PC-133 DIMM. > > ... > > When attempting to boot from the CD, the machine locks immediately after > > the adaptec card reports "SCSI BIOS installed successfully". Hard locks. > > requires hard reset. This is the same for a Win98 CD. Something in the > > way FBSD and Win98 load themselves into memory is obviously unhappy. > > ... > > 9 times out of 10, the problem I have with registered DIMMs > (256MB+) as well as PC133 is the failure to put the DIMMs in slot >... Hmmm, the manual says: "registered DIMMs are not supported." (P20, P22). It looks like not a slot problem, but the memory type. -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 8:42:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 61E7A37B502 for ; Fri, 13 Oct 2000 08:42:33 -0700 (PDT) Received: by moo.sysabend.org (Postfix, from userid 1004) id D9909755D; Fri, 13 Oct 2000 08:47:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id D4E8C1D89; Fri, 13 Oct 2000 08:47:00 -0700 (PDT) Date: Fri, 13 Oct 2000 08:47:00 -0700 (PDT) From: Jamie Bowden To: Jin Guojun Cc: thebs@smithconcepts.com, thebs@theseus.com, hardware@FreeBSD.ORG Subject: Re: K7V problem? <- Make sure DIMM is in slot 1 In-Reply-To: <200010131536.e9DFaAL13073@portnoy.lbl.gov> Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 13 Oct 2000, Jin Guojun wrote: :Bryan -TheBS- Smith wrote: :> > The machine in question is an Athlon/850 on an Asus K7V (BIOS 1007) with a :> > 256M PC-133 DIMM. :> > ... :> > When attempting to boot from the CD, the machine locks immediately after :> > the adaptec card reports "SCSI BIOS installed successfully". Hard locks. :> > requires hard reset. This is the same for a Win98 CD. Something in the :> > way FBSD and Win98 load themselves into memory is obviously unhappy. :> > ... :> :> 9 times out of 10, the problem I have with registered DIMMs :> (256MB+) as well as PC133 is the failure to put the DIMMs in slot :>... : :Hmmm, the manual says: "registered DIMMs are not supported." (P20, P22). :It looks like not a slot problem, but the memory type. That's odd, since the board will take 3 512M PC133 DIMMs. I'm not aware of what exactly is meant by 'registered DIMMs', could someone explain. The machine runs NT Server 4.0 and Win98 just fine, and I realize FBSD tends to use hardware more aggressively. If the memory were incompatible, I would think nothing would run. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 8:45:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from rhymer.cogsci.ed.ac.uk (rhymer.cogsci.ed.ac.uk [129.215.144.8]) by hub.freebsd.org (Postfix) with ESMTP id 90EE137B503 for ; Fri, 13 Oct 2000 08:45:32 -0700 (PDT) Received: (from richard@localhost) by rhymer.cogsci.ed.ac.uk (8.9.3+Sun/8.9.3) id QAA27626; Fri, 13 Oct 2000 16:44:44 +0100 (BST) Date: Fri, 13 Oct 2000 16:44:44 +0100 (BST) Message-Id: <200010131544.QAA27626@rhymer.cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: K7V problem? <- Make sure DIMM is in slot 1 To: Jamie Bowden , Jin Guojun In-Reply-To: Jamie Bowden's message of Fri, 13 Oct 2000 08:47:00 -0700 (PDT) Organization: just say no Cc: thebs@smithconcepts.com, thebs@theseus.com, hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm not aware > of what exactly is meant by 'registered DIMMs', could someone explain. I think it means "having registers" :-) According to http://www.memoryx.net/128rpc133ecc.html: Registered means the module has a type of buffering. This allows more modules to run stably in a system. To use registered dimm, your mainboard must support registration and you can not mix registered and non registered memory. -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 8:52:50 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id E273437B502 for ; Fri, 13 Oct 2000 08:52:48 -0700 (PDT) Received: by moo.sysabend.org (Postfix, from userid 1004) id 4BD3E7567; Fri, 13 Oct 2000 08:57:16 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 4900A1D8E; Fri, 13 Oct 2000 08:57:16 -0700 (PDT) Date: Fri, 13 Oct 2000 08:57:16 -0700 (PDT) From: Jamie Bowden To: Richard Tobin Cc: Jin Guojun , thebs@smithconcepts.com, thebs@theseus.com, hardware@FreeBSD.ORG Subject: Re: K7V problem? <- Make sure DIMM is in slot 1 In-Reply-To: <200010131544.QAA27626@rhymer.cogsci.ed.ac.uk> Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 13 Oct 2000, Richard Tobin wrote: :> I'm not aware :> of what exactly is meant by 'registered DIMMs', could someone explain. : :I think it means "having registers" :-) : :According to http://www.memoryx.net/128rpc133ecc.html: : : Registered means the module has a type of buffering. This allows more : modules to run stably in a system. To use registered dimm, your : mainboard must support registration and you can not mix registered : and non registered memory. I have no idea if the DIMM is registered or not. The memory supplier you point to above sells both reg'd and unreg'd 256M DIMMs, so size is not an indicator. Looking at the price difference, I doubt I have a reg'd DIMM. I'd also think if I did, nothing would work, not just FreeBSD. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 9:39: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 9F14537B678 for ; Fri, 13 Oct 2000 09:39:05 -0700 (PDT) Received: by moo.sysabend.org (Postfix, from userid 1004) id EC9AA756E; Fri, 13 Oct 2000 09:43:33 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id E906F1D8F; Fri, 13 Oct 2000 09:43:33 -0700 (PDT) Date: Fri, 13 Oct 2000 09:43:33 -0700 (PDT) From: Jamie Bowden To: Jeremy Vandenhouten Cc: hardware@FreeBSD.org Subject: Re: K7V problem? In-Reply-To: <24d9f1f066.1f06624d9f@marquette.edu> Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 13 Oct 2000, Jeremy Vandenhouten wrote: :I've also seen the lockup problem when you have boot-virus protection :enabled in the bios... Whenever you install a new OS make sure this is :disabled... It is disabled. I'm not a newbie here, I've been running FBSD since 1.1. This is the first time I've seen this behaviour though. I do think it's hardware since win98's bootable cd suffers from the exact same problem as FreeBSD. The problem is everything works in NT and 98 (installed 98 using floppy), so dealing with Asus is likely to get me an answer of 'We don't support FreeBSD.' I have no doubt others are using this board without problems in FreeBSD. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 10:33:53 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 9B11637B66E for ; Fri, 13 Oct 2000 10:33:50 -0700 (PDT) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id e9DHXo016751; Fri, 13 Oct 2000 10:33:50 -0700 (PDT) Date: Fri, 13 Oct 2000 10:33:50 -0700 (PDT) From: Jin Guojun (DSD staff) Message-Id: <200010131733.e9DHXo016751@portnoy.lbl.gov> To: jeremy.vandenhouten@marquette.edu, ragnar@sysabend.org Subject: Re: K7V problem? Cc: hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It is disabled. I'm not a newbie here, I've been running FBSD since 1.1. > This is the first time I've seen this behaviour though. I do think it's > hardware since win98's bootable cd suffers from the exact same problem as > FreeBSD. The problem is everything works in NT and 98 (installed 98 using > floppy), so dealing with Asus is likely to get me an answer of 'We don't > support FreeBSD.' I have no doubt others are using this board without > problems in FreeBSD. I have used K7V with FreeBSD 4.x and 5.x for a long time. The box has equipped with all of following peripherals together: SK dual-port GigE, SCSI, Intel EEPRO 100+, as well as other devices. It has run FreeBSD for at least four months, and not seen any problem. ASUS will probably not answer your inquire at all. I have tried to contact them for serveral times, and only get one reply with useless message:-( However, the ASUS motherboards are very good (or best) for FreeBSD in my experience; I have processed over 100s motherboards including almost every ASUS motherboard. So, most likely is the hardware configuration in your situation. If your memory has 18 chips, you may have registered DIMM. If you have 16 chips DIMM, you may try it before making a conclusion. Best wish, -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 10:46: 8 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ns.tcworks.net (ns.tcworks.net [216.61.218.2]) by hub.freebsd.org (Postfix) with ESMTP id DB2F437B66C for ; Fri, 13 Oct 2000 10:46:05 -0700 (PDT) Received: from tcworks.net (stuck.sticky.org [216.61.218.6]) by ns.tcworks.net (8.9.2/8.9.2) with ESMTP id MAA45550 for ; Fri, 13 Oct 2000 12:39:44 -0500 (CDT) (envelope-from ccook@tcworks.net) Message-ID: <39E74AA9.1DEF6C13@tcworks.net> Date: Fri, 13 Oct 2000 12:47:21 -0500 From: Chris Cook X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Adaptec ARO-1130U2 RAID Card Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can anyone please tell me if FreeBSD currently supports the above named RAID controller? Here is a link: http://www.adaptec.com/products/overview/aro1130u2.html Thanks, please cc me any messages because I am not subscribed to the list. -- Chris o----< ccook@tcworks.net >-------------------------------------o |Chris Cook - Admin | TCWORKS.NET - http://www.tcworks.net | |The Computer Works ISP | FreeBSD - http://www.freebsd.org | o--------------------------------------------------------------o To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 11:57:31 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 8492737B66C for ; Fri, 13 Oct 2000 11:57:29 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9DIxW701846; Fri, 13 Oct 2000 11:59:37 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010131859.e9DIxW701846@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chris Cook Cc: freebsd-hardware@freebsd.org Subject: Re: Adaptec ARO-1130U2 RAID Card In-reply-to: Your message of "Fri, 13 Oct 2000 12:47:21 CDT." <39E74AA9.1DEF6C13@tcworks.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Oct 2000 11:59:32 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can anyone please tell me if FreeBSD currently supports the above named > RAID controller? Here is a link: > > http://www.adaptec.com/products/overview/aro1130u2.html > > Thanks, please cc me any messages because I am not subscribed to the > list. This isn't a RAID controller. It's a checksum accelerator module for Windows-only RAID software. FreeBSD doesn't support it, and unless Adaptec release their RAIDport software in source form, probably never will. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 13:53:57 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id DDC1337B66D for ; Fri, 13 Oct 2000 13:53:53 -0700 (PDT) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id e9DKrqi24279; Fri, 13 Oct 2000 13:53:52 -0700 (PDT) Date: Fri, 13 Oct 2000 13:53:52 -0700 (PDT) From: Jin Guojun (DSD staff) Message-Id: <200010132053.e9DKrqi24279@portnoy.lbl.gov> To: ragnar@sysabend.org, richard@cogsci.ed.ac.uk Subject: Re: K7V problem? <- Make sure DIMM is in slot 1 Cc: hardware@FreeBSD.ORG, jin@george.lbl.gov, thebs@smithconcepts.com, thebs@theseus.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 13 Oct 2000 Jamie Bowden wrote: } :> I'm not aware } :> of what exactly is meant by 'registered DIMMs', could someone explain. } : } :I think it means "having registers" :-) } : } :According to http://www.memoryx.net/128rpc133ecc.html: } : } : Registered means the module has a type of buffering. This allows more } : modules to run stably in a system. To use registered dimm, your } : mainboard must support registration and you can not mix registered } : and non registered memory. } } I have no idea if the DIMM is registered or not. The memory supplier you } point to above sells both reg'd and unreg'd 256M DIMMs, so size is not an } indicator. Looking at the price difference, I doubt I have a reg'd DIMM. } I'd also think if I did, nothing would work, not just FreeBSD. Not for this case, but reverse one. 'registered DIMMs' means buffered DIMMs. buffered DIMM is for EDO type memory, and registered DIMM is for SDRAM. They are the same term in different technologies. Normally, unbeffered DIMM looks like -- | | | | | | | | non-parity | | | | | | | | | parity buffered/registered DIMM looks like -- | | | | -- | | | | non-parity | | | | -- | | | | | parity Each line represents a memory chip. Another way to look at this is the notch location. unbuffered DIMM module has this notch away from 20 pin (close to 60 pin) side. buffered DIMM module has this notch in the middle between 20 pin and 60 pin. Putting a unbuffered DIMM in buffered memory controller will not work at all. Putting a buffered/registered DIMM in an unbuffered memory controller may or may not work depending on the chip feature (double buffered signal). This is similar to putting some good 70ns memory to a 60ns system and the system will work no problem. By putting random 70ns memory chip into a 60ns system may have marginal work, or may not work at all. If you have registered DIMM, this probably is a case. The only controller known to work with registered and unbuffered 256MB DIMM is the intel BX-440 chip. All those 8## chip designed to work different memory modules between DIMM and RIMM do not seem work well at this point. I did not catch your original message. If your system works under other O.S., but FreeBSD, I would like to know how can we solve the problem. -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 13 21:24:53 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 3FABA37B66C for ; Fri, 13 Oct 2000 21:24:47 -0700 (PDT) Received: by moo.sysabend.org (Postfix, from userid 1004) id 74381755B; Fri, 13 Oct 2000 21:29:17 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 6353A1D89; Fri, 13 Oct 2000 21:29:17 -0700 (PDT) Date: Fri, 13 Oct 2000 21:29:17 -0700 (PDT) From: Jamie Bowden To: Jin Guojun Cc: richard@cogsci.ed.ac.uk, hardware@FreeBSD.ORG, thebs@smithconcepts.com, thebs@theseus.com Subject: Re: K7V problem? <- Make sure DIMM is in slot 1 In-Reply-To: <200010132053.e9DKrqi24279@portnoy.lbl.gov> Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 13 Oct 2000, Jin Guojun wrote: :On Fri, 13 Oct 2000 Jamie Bowden wrote: :} I have no idea if the DIMM is registered or not. The memory supplier you :} point to above sells both reg'd and unreg'd 256M DIMMs, so size is not an :} indicator. Looking at the price difference, I doubt I have a reg'd DIMM. :} I'd also think if I did, nothing would work, not just FreeBSD. : :Not for this case, but reverse one. : :'registered DIMMs' means buffered DIMMs. :buffered DIMM is for EDO type memory, and registered DIMM is for SDRAM. :They are the same term in different technologies. Actually, the DIMM slot is keyed to only allow 3.3v unbuffered DIMMs (pulled out the manual), so that's not an issue. I still expect full well that if I put a real floppy in the machine instead of the LS-120, it'll boot CDROM just fine in all likelihood. I don't think the K7V bios and Adaptec's means of making CDROMs boot by overriding the bios A: drive assignment are getting along with the LS-120. Why the FreeBSD boot floppy won't boot, I haven't a clue. That should work no matter whether I have 1.44M floppy or LS-120 I would think. Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message