From owner-freebsd-hardware Sun Jul 9 13:57:19 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from web125.yahoomail.com (web125.yahoomail.com [205.180.60.193]) by hub.freebsd.org (Postfix) with SMTP id 3F58A37BF55 for ; Sun, 9 Jul 2000 13:57:02 -0700 (PDT) (envelope-from eaglez69@yahoo.com) Received: (qmail 1836 invoked by uid 60001); 9 Jul 2000 20:56:55 -0000 Message-ID: <20000709205655.1835.qmail@web125.yahoomail.com> Received: from [136.152.193.189] by web125.yahoomail.com; Sun, 09 Jul 2000 13:56:55 PDT Date: Sun, 9 Jul 2000 13:56:55 -0700 (PDT) From: Eaglez Subject: Re: keyboards w/no windows keys To: freebsd-hardware@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I saw these keyboards at linux-con (yes, i know, evil evil...) and they were very sweet. The only problem is that even the el-cheepo LITE version is $69! and it's for something that has so many less keys than the standard 102 key keyboard, which you could get for like $12. I mean, i DO still want one if i ever get a high-paying job. But for right now, is there a place to get old 102 key keyboards, or anything really, for $12 or so? i have a few computers to furnish right now, and i don't feel like forking out hundreds of dollars. oh yea, the way the cursor keys are on these keyboards, it's almost impossible to scroll through past commands (tcsh, bash) casually... i think it'd have been infinatly better if they'd just done cursors like on the old macs, in one row or column. -Jesse (sorry for ranting) --- Parag Patel wrote: > On Fri, 07 Jul 2000 14:44:52 CDT, Craig Johnston > wrote: > > > >Although this is somewhat offtopic, I figured some > of you could point > >me towards a quality keyboard with no stupid > windows keys on it. I > >resent giving up useful spacebar real-estate to > advertise for MS on my > >keyboard. > > Try for the Hackers > Keyboards. These don't have > those keys and also have escape and control in their > correct places. I > haven't tried these yet and so can't give a review, > but I really like > the Sun keyboard layout that these are based on. > Your mileage may vary. > > > -- Parag Patel > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of > the message __________________________________________________ Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 9 14:19: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id C87F137B51E for ; Sun, 9 Jul 2000 14:19:04 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id OAA17561; Sun, 9 Jul 2000 14:19:02 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: Eaglez Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: keyboards w/no windows keys In-Reply-To: Message from Eaglez of "Sun, 09 Jul 2000 13:56:55 PDT." <20000709205655.1835.qmail@web125.yahoomail.com> Organization: CodeGen, Inc. X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Sun, 09 Jul 2000 14:19:02 -0700 Message-ID: <17557.963177542@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 09 Jul 2000 13:56:55 PDT, Eaglez wrote: > >But for right now, is there a place >to get old 102 key keyboards, or anything really, for >$12 or so? Your best-bet may be to find a local computer junk shop and browse through their used keyboard collection. They may not all work so buy extras. Given how cheap new keyboards are, this probably isn't a good use of time or money. www.centralcomputers.com has some cheap new keyboards for ~$11-15 - other vendors may even have them cheaper. Just pop out the dreaded Windows key, or glue a custom label on top, say a drawing of a middle-finger, raised, in front of the logo. :) I currently use cheap PC keyboards and use X's xmodmap command to turn the caps-lock into a control key, and map the tilde/grave ~` key to escape if it is in the upper-left corner. I've also built a similar keyboard mapping for the console. That makes PC keyboards close enough to the Sun/Unix keyboards for me. >i think it'd >have been infinatly better if they'd just done cursors >like on the old macs, in one row or column. Personally, I prefer an inverted-"T" layout for cursor keys. I've kinda gotten used to using PageUp/PageDown as well. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 9 19:55: 3 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from isass0.solar.isas.ac.jp (isass0.solar.isas.ac.jp [133.74.8.100]) by hub.freebsd.org (Postfix) with ESMTP id 7634B37B952 for ; Sun, 9 Jul 2000 19:54:55 -0700 (PDT) (envelope-from handy@isass0.solar.isas.ac.jp) Received: from localhost by isass0.solar.isas.ac.jp (8.8.7/1.1.20.3/28Jan00-0547AM) id LAA0000031369; Mon, 10 Jul 2000 11:54:31 +0900 (JST) Date: Mon, 10 Jul 2000 11:54:31 +0900 (JST) From: Brian Handy To: freebsd-hardware@freebsd.org Subject: Serial I/O thruput 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 Hi folks, I asked some questions a while back about 'Space Hardware', and got a pile of really useful advice in short order. Heady with success, I thought I'd try this process again. This time it's more dumb questions though. I want to talk to three CCD cameras, and I'd like to download data from these cameras just about as fast as I can. The communications bus is TBD; it could be serial connections, parallel ports, heck, could even be USB maybe. (Or some other method I haven't been made aware of yet.) I had originally thought rather simplistically about using RS-232, since the board I'm looking at has (I think) 4 serial ports. However...I'm not sure how fast I can push data into the motherboard over these ports. I don't have any hardware yet (that's what the proposal is for), so I can't really benchmark anything. Is multiple serial ports (or a multi-port serial card) a silly idea for this? Any suggestions, and what sort of transfer rates I can expect? The only complicating factor is I have to talk to three cameras, each of which is [baseline] capable of generating 4MB of data every 10 seconds. I should probably know this stuff. Thanks, Brian -- Brian Handy Mail: handy@physics.montana.edu Department of Physics Phone: (406) 994-6317 Montana State University Fax: (406) 994-4452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 6:29: 1 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 3427737B58A for ; Mon, 10 Jul 2000 06:28:59 -0700 (PDT) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id 38B9775DD; Mon, 10 Jul 2000 06:32:46 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 340931D89; Mon, 10 Jul 2000 06:32:46 -0700 (PDT) Date: Mon, 10 Jul 2000 06:32:46 -0700 (PDT) From: Jamie Bowden To: Craig Johnston Cc: freebsd-hardware@freebsd.org Subject: Re: keyboards w/no windows keys In-Reply-To: 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, 7 Jul 2000, Craig Johnston wrote: :Although this is somewhat offtopic, I figured some of you could point :me towards a quality keyboard with no stupid windows keys on it. I :resent giving up useful spacebar real-estate to advertise for MS on my :keyboard. I believe IBM is still selling it's original OS/2 keyboard under the IBM Options product line (they were last time I checked, but that has been quite a long while now). Jamie Bowden -- "Of course, that's sort of like asking how other than Marketing, Microsoft is different from any other software company..." Kenneth G. Cavness To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 6:43:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ns1.hit.net (ns1.hit.net [206.252.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 0874C37B58A for ; Mon, 10 Jul 2000 06:43:06 -0700 (PDT) (envelope-from hsmock@hit.net) Received: from abit (oxnt.hit.net [206.252.168.132]) by ns1.hit.net (8.8.8/8.8.5) with SMTP id IAA28959 for ; Mon, 10 Jul 2000 08:43:05 -0500 (CDT) Message-ID: <009101bfea76$e9deda80$0501a8c0@hit.net> From: "Howard Smock" To: Subject: New machines and Raid compatabilty Date: Mon, 10 Jul 2000 08:58:23 -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.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am looking to purchase 3 systems to run FreeBSD in a raid 5 configuration. I read the hardware compatibility list and do not find the AMD 1500 Raid controllers listed. But on the FreeBSD Kernel information page I do find a listing for the MegaRaid. # RAID controllers device ida # Compaq Smart RAID device amr # AMI MegaRAID ****Here is a paste from the kernal section of the web guide****** device mlx # Mylex DAC960 family So is this Raid compatable? Has anyone used this configuration? Here is a quote on the hardware I have at this time. Any input would be welcome Processor 1 Pentium III 650Mhz/100 w/256K Cache Intel BoardSpecs 1 Dual RDY Pentium II/III, GX, L440GX Lancewood BoardSpecs 1 (4) 32bit PCI, (2)32/66mhz bit PCI, (1) ISA (2) USB 2MB Video BoardSpecs 1 4 Dimms, 2GB Max, Onboard Management Software BoardSpecs 1 Integrated LVD, 10/100 Ethernet Memory 1 128 MB SDRAM, DIMM, 133Mhz Disk 5 18GB, 10,000 RPM, LVD 160MB/Sec 4MB Cache Seagate SLEDS 6 DataPort Shuttle for SCA Drive Backplane 2 3 Bay 1 Channel SCA LVD Hot Swap Backplane (1x3) Backplane 2 LVD Cable to Backplane Backplane 2 Backplane Terminator Floppy 1 3.5" Floppy and System Cabling MPF-920-1-131 CD ROM 1 48X Sony IDE CD-ROM Host RAID Ctl 1 AMI Mega 4 Channel RAID Ctrlr, LVD MegaRAID 1500 Host RAID Ctl 1 64MB SDRAM Cache for 1500 MegaRAID 1500 Cabling 2 LVD Internal Cabling CPU ATX Rack 1 4U BLACK Rackmount, (8)5.25 Bays, Dual 300W Red power Rack Rails 1 Sliding Rails (one per rack shelf) RACK-6CA300 1 * Please notice rack case color is black unless specified Warranty 1 3 Year Warranty SERVICE 1 1 Year NBD on-site, Banctec Server Thank you for your assistance. Howard Smock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 8:54:21 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 8F04C37B9F6 for ; Mon, 10 Jul 2000 08:54:17 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id JAA05309; Mon, 10 Jul 2000 09:02:22 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007101602.JAA05309@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Howard Smock" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: New machines and Raid compatabilty In-reply-to: Your message of "Mon, 10 Jul 2000 08:58:23 CDT." <009101bfea76$e9deda80$0501a8c0@hit.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Jul 2000 09:02:22 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am looking to purchase 3 systems to run FreeBSD in a raid 5 > configuration. I read the hardware compatibility list and do not find the > AMD 1500 Raid controllers listed. Quoting from the HARDWARE.TXT file: AMI MegaRAID Express and Enterprise family RAID controllers: MegaRAID 418 MegaRAID Enterprise 1200 (428) MegaRAID Enterprise 1300 MegaRAID Enterprise 1400 MegaRAID Enterprise 1500 MegaRAID Elite 1500 MegaRAID Express 200 MegaRAID Express 300 Dell PERC Dell PERC 2/SC Dell PERC 2/DC Some HP NetRAID controllers are OEM versions of AMI designs, and these are also supported. -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 9:27:29 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 8DBC637B5BC for ; Mon, 10 Jul 2000 09:27:26 -0700 (PDT) (envelope-from jfb@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id C35D436E6 for ; Mon, 10 Jul 2000 11:27:25 -0500 (CDT) Received: (from jfb@localhost) by isis.visi.com (8.8.8/8.8.8) id LAA16839 for freebsd-hardware@freebsd.org; Mon, 10 Jul 2000 11:27:25 -0500 (CDT) From: Date: Mon, 10 Jul 2000 11:27:25 -0500 To: freebsd-hardware@freebsd.org Subject: Re: keyboards w/no windows keys Message-ID: <20000710112725.G12465@visi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i In-Reply-To: ; from Craig Johnston on Fri, Jul 07, 2000 at 02:44:52PM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Although this is somewhat offtopic, I figured some of you could point > me towards a quality keyboard with no stupid windows keys on it. Well, I've found that the Happy Hacker (1) model works well for what it is, although I do find myself missing the cursor and function keys. It's got a decent feel, and all the keys are in the proper positions. Another option would be the "classic" IBM keyboards, if you could find them. While they still have the detested capslock key in place of ctrl, at least they have a totally superior feel. I ordered a pair from some cheesy Yahoo store (2) this morning. Just my .02$, (jfb) (1) http://www.pfuca.com (2) http://store.yahoo.com/pckeyboards/ibmkeyboards.html -- What a puny plan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 12:26:19 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp-ham-1.netsurf.de (smtp-ham-1.netsurf.de [194.195.64.97]) by hub.freebsd.org (Postfix) with ESMTP id 98D2137B5B0 for ; Mon, 10 Jul 2000 12:26:15 -0700 (PDT) (envelope-from inferno@nightfire.de) Received: from mail-ham-1.netsurf.de ([192.168.10.65]) by smtp-ham-1.netsurf.de (Netscape Messaging Server 4.1) with ESMTP id FXHX7R01.BC1 for ; Mon, 10 Jul 2000 21:09:27 +0200 Received: from nightfire.de ([195.179.179.207]) by mail-ham-1.netsurf.de (Netscape Messaging Server 4.1) with ESMTP id FXHXZA00.1WU; Mon, 10 Jul 2000 21:25:58 +0200 Message-ID: <396A21AC.A43F233E@nightfire.de> Date: Mon, 10 Jul 2000 21:19:08 +0200 From: Olaf Hoyer Reply-To: ohoyer@fbwi.fh-wilhelmshaven.de X-Mailer: Mozilla 4.7 [de]C-CCK-MCD QXW0322q (Win95; I) X-Accept-Language: de,en MIME-Version: 1.0 To: Brian Handy Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Serial I/O thruput References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This time it's more dumb questions though. I want to talk to three CCD > cameras, and I'd like to download data from these cameras just about as > fast as I can. The communications bus is TBD; it could be serial > connections, parallel ports, heck, could even be USB maybe. (Or some > other method I haven't been made aware of yet.) I had originally thought > rather simplistically about using RS-232, since the board I'm looking at > has (I think) 4 serial ports. > > However...I'm not sure how fast I can push data into the motherboard over > these ports. I don't have any hardware yet (that's what the proposal is > for), so I can't really benchmark anything. Is multiple serial ports (or > a multi-port serial card) a silly idea for this? Any suggestions, and > what sort of transfer rates I can expect? The only complicating factor is > I have to talk to three cameras, each of which is [baseline] capable of > generating 4MB of data every 10 seconds. Hi! Well, the standard 16550 FIFO is capable of shovelling about 115200 bps. There are better chips available, that shall be able to do more than (IIRC, 8 times) that value. YOu need some special drivers for that. RS 422 or so come to mind, but you will need special gear for that. I'd check that out if ya need to. Cyclades comes to mind... They are working hard on native FreeBSD drivers, and introduced some new cards yet, as I heard on Linuxtag 2000 in Stuttgart. And they want to cooperate with the FreeBSD driver coders for those cards. Regards Olaf Hoyer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 12:36: 4 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ssabsd.csw.net (ssabsd.csw.net [209.136.201.12]) by hub.freebsd.org (Postfix) with ESMTP id BB42937B7E3 for ; Mon, 10 Jul 2000 12:35:57 -0700 (PDT) (envelope-from lambert@ssabsd.csw.net) Received: by ssabsd.csw.net (Postfix, from userid 1000) id 665622E; Mon, 10 Jul 2000 14:36:17 -0500 (CDT) To: freebsd-hardware@freebsd.org Subject: Re: keyboards w/no windows keys In-Reply-To: References: Reply-To: lambert@cswnet.com Message-Id: <20000710193617.665622E@ssabsd.csw.net> Date: Mon, 10 Jul 2000 14:36:17 -0500 (CDT) From: lambert@ssabsd.csw.net (Scott Lambert) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In muc.lists.freebsd.hardware, you wrote: >On Fri, 7 Jul 2000, Craig Johnston wrote: > >:Although this is somewhat offtopic, I figured some of you could point >:me towards a quality keyboard with no stupid windows keys on it. I >:resent giving up useful spacebar real-estate to advertise for MS on my >:keyboard. > >I believe IBM is still selling it's original OS/2 keyboard under the IBM >Options product line (they were last time I checked, but that has been >quite a long while now). I think you mean the PS/2 keyboard. OS/2 is the Operating System with the useful GUI. The PS/2 had the good but proprietary hardware. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 14:18: 1 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.hcvlny.cv.net (mx1.hcvlny.cv.net [167.206.112.76]) by hub.freebsd.org (Postfix) with ESMTP id 7E11637BA6A for ; Mon, 10 Jul 2000 14:16:41 -0700 (PDT) (envelope-from steinyv@skyweb.net) Received: from s1.optonline.net (s1.optonline.net [167.206.112.6]) by mx1.hcvlny.cv.net (8.9.3/8.9.3) with ESMTP id RAA04847 for ; Mon, 10 Jul 2000 17:16:10 -0400 (EDT) Received: from downstairs (d133-103.jcsnnj.optonline.net [24.189.133.103]) by s1.optonline.net (8.9.1/8.9.3) with ESMTP id RAA09266 for ; Mon, 10 Jul 2000 17:16:09 -0400 (EDT) Message-Id: <4.2.0.58.20000710165909.00a06aa0@> X-Sender: steinyv@pluto.skyweb.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 10 Jul 2000 16:59:13 -0400 To: freebsd-hardware@freebsd.org From: steinyv Subject: requirements Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org what kind of requirements does a dns server require??? thanks _________________________________________ Steiny's Studio Pachyderm Productions http://steiny.hypermart.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 15:41:41 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.hcvlny.cv.net (mx1.hcvlny.cv.net [167.206.112.76]) by hub.freebsd.org (Postfix) with ESMTP id 36B0A37B6B6 for ; Mon, 10 Jul 2000 15:38:16 -0700 (PDT) (envelope-from steinyv@skyweb.net) Received: from s1.optonline.net (s1.optonline.net [167.206.112.6]) by mx1.hcvlny.cv.net (8.9.3/8.9.3) with ESMTP id SAA21948 for ; Mon, 10 Jul 2000 18:36:09 -0400 (EDT) Received: from downstairs (d133-103.jcsnnj.optonline.net [24.189.133.103]) by s1.optonline.net (8.9.1/8.9.3) with ESMTP id SAA08537 for ; Mon, 10 Jul 2000 18:36:09 -0400 (EDT) Message-Id: <4.2.0.58.20000710181742.009c4b30@> X-Sender: steinyv@pluto.skyweb.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 10 Jul 2000 18:18:39 -0400 To: freebsd-hardware@freebsd.org From: steinyv Subject: RE: requirements In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How about disk space. I was just wondering, is seems that it will need a lot of space??? At 05:39 PM 7/10/00 , you wrote: >minimum - 486/25 with 8 to 12 meg > >-----Original Message----- >From: steinyv [mailto:steinyv@skyweb.net] >Sent: Monday, July 10, 2000 3:59 PM >To: freebsd-hardware@freebsd.org >Subject: requirements > > >what kind of requirements does a dns server require??? >thanks > >_________________________________________ >Steiny's Studio >Pachyderm Productions >http://steiny.hypermart.net > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message _________________________________________ Steiny's Studio Pachyderm Productions http://steiny.hypermart.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 16:27:36 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from kenny.netrail.net (kenny.netrail.net [205.215.10.5]) by hub.freebsd.org (Postfix) with ESMTP id D9D3E37B8D5 for ; Mon, 10 Jul 2000 16:27:28 -0700 (PDT) (envelope-from jhartley@netrail.net) Received: from jhartley (kenny.netrail.net [205.215.10.5]) by kenny.netrail.net (8.9.3/8.9.3) with SMTP id TAA02054 for ; Mon, 10 Jul 2000 19:29:43 -0400 (EDT) From: "Jeff Hartley" To: Subject: SysKonnect and Intel gig boards Date: Mon, 10 Jul 2000 19:26:36 -0400 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) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Anyone have any experience (good/bad/indifferent) with the Intel GigSX boards, or the SysKonnect dual-port GigSX boards, under 4.0-RELEASE? I'm in need of quad-gig boxes, and I'm reluctant to stick with 3COM, based on an unsatisfactory failure rate in the past. Horror stories or blessings, anyone? I did notice that SysKonnect seems to be friendlier with the developer community than Intel (go figure). Thanks, -Jeff Hartley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 16:32:56 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CF3DF37BC4C for ; Mon, 10 Jul 2000 16:32:51 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA30177; Mon, 10 Jul 2000 16:31:08 -0700 Date: Mon, 10 Jul 2000 16:29:12 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jeff Hartley Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: SysKonnect and Intel gig boards 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 Don't use the wx driven EEPRO-1000 from 4.0 (wait for the 4.1 release which will have some bug fixes). I can't speak about SysKonnect. The Tigon-II based NetGear cards have been peachy. On Mon, 10 Jul 2000, Jeff Hartley wrote: > Anyone have any experience (good/bad/indifferent) with the Intel GigSX > boards, or the SysKonnect dual-port GigSX boards, under 4.0-RELEASE? I'm in > need of quad-gig boxes, and I'm reluctant to stick with 3COM, based on an > unsatisfactory failure rate in the past. Horror stories or blessings, > anyone? I did notice that SysKonnect seems to be friendlier with the > developer community than Intel (go figure). > > Thanks, > -Jeff Hartley > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 16:52:21 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id BE15837B5C1 for ; Mon, 10 Jul 2000 16:52:17 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA28995; Mon, 10 Jul 2000 17:51:59 -0600 (MDT) (envelope-from ken) Date: Mon, 10 Jul 2000 17:51:59 -0600 From: "Kenneth D. Merry" To: Jeff Hartley Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: SysKonnect and Intel gig boards Message-ID: <20000710175159.A28975@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from jhartley@netrail.net on Mon, Jul 10, 2000 at 07:26:36PM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jul 10, 2000 at 19:26:36 -0400, Jeff Hartley wrote: > Anyone have any experience (good/bad/indifferent) with the Intel GigSX > boards, or the SysKonnect dual-port GigSX boards, under 4.0-RELEASE? I'm in > need of quad-gig boxes, and I'm reluctant to stick with 3COM, based on an > unsatisfactory failure rate in the past. Horror stories or blessings, > anyone? I did notice that SysKonnect seems to be friendlier with the > developer community than Intel (go figure). 3Com's 3c985b is really just a rebadged Alteon Tigon II board with 1MB SRAM. The Netgear GA620 is a rebadged Tigon II board with 512K SRAM. FWIW, the Tigon boards work quite well. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 16:56:20 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 CF5E537B865 for ; Mon, 10 Jul 2000 16:56:17 -0700 (PDT) (envelope-from jin@portnoy.lbl.gov) Received: (from jin@localhost) by portnoy.lbl.gov (8.10.0/8.10.0) id e6ANuGk18566; Mon, 10 Jul 2000 16:56:16 -0700 (PDT) Date: Mon, 10 Jul 2000 16:56:16 -0700 (PDT) From: Jin Guojun (DSD staff) Message-Id: <200007102356.e6ANuGk18566@portnoy.lbl.gov> To: jhartley@netrail.net, mjacob@feral.com Subject: Re: SysKonnect and Intel gig boards Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob Wrote: > Don't use the wx driven EEPRO-1000 from 4.0 (wait for the 4.1 release which > will have some bug fixes). > > I can't speak about SysKonnect. The Tigon-II based NetGear cards have been > peachy. Just more info.: SysKonnect and Intel EEPRO-1000 have the similar pricey, but they work well. The Tigon-II based NetGear card is cheaper, but has a couple of drawback: (1) the driver under FreeBSD up/down a couple of times at boottime, this causes NFS mount failure during boot. It is not a big deal. I fixed it in rc.local with a line: df | grep $mymount_point || mount -a (2) chewing significant CPU: (tested on completely idle machines) 500 MHz P-III + single NetGear A620 I/O takes 47% CPU time 750 MHz AMD K7 + single NetGear A620 I/O takes less 10% CPU 500 MHz P-III + single SysKonnect I/O takes less 5% CPU If you have a high end machine, it is probably not a big issue. The driver chews CPU on both FreeBSD and Linux; so it is driver issue, but O.S. Hopefully, the newer driver will fix the problem. -Jin > On Mon, 10 Jul 2000, Jeff Hartley wrote: > > > Anyone have any experience (good/bad/indifferent) with the Intel GigSX > > boards, or the SysKonnect dual-port GigSX boards, under 4.0-RELEASE? I'm in > > need of quad-gig boxes, and I'm reluctant to stick with 3COM, based on an > > unsatisfactory failure rate in the past. Horror stories or blessings, > > anyone? I did notice that SysKonnect seems to be friendlier with the > > developer community than Intel (go figure). > > > > Thanks, > > -Jeff Hartley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 17: 0:16 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 4B07537B8AE for ; Mon, 10 Jul 2000 17:00:13 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA07792; Mon, 10 Jul 2000 17:08:09 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007110008.RAA07792@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jeff Hartley" Cc: freebsd-hardware@freebsd.org Subject: Re: SysKonnect and Intel gig boards In-reply-to: Your message of "Mon, 10 Jul 2000 19:26:36 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Jul 2000 17:08:09 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Anyone have any experience (good/bad/indifferent) with the Intel GigSX > boards, or the SysKonnect dual-port GigSX boards, under 4.0-RELEASE? I'm in > need of quad-gig boxes, and I'm reluctant to stick with 3COM, based on an > unsatisfactory failure rate in the past. Horror stories or blessings, > anyone? I did notice that SysKonnect seems to be friendlier with the > developer community than Intel (go figure). I can't comment on the performance or reliability of the SysKonnect boards (other than that Bill Paul wrote/maintains the driver, which is a Good Thing). However I note that the cards I've seen appear to be designed for failover rather than dual-port operation, and one of the two interface parts is fan-cooled (for the primary port) while the other just has a passive heatsink (presumably because it's not meant to be running all the time). Just a point to consider. -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 17: 7:51 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 328DD37B975 for ; Mon, 10 Jul 2000 17:07:48 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA30394; Mon, 10 Jul 2000 17:07:41 -0700 Date: Mon, 10 Jul 2000 17:05:45 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jin Guojun Cc: jhartley@netrail.net, freebsd-hardware@FreeBSD.ORG Subject: Re: SysKonnect and Intel gig boards In-Reply-To: <200007102356.e6ANuGk18566@portnoy.lbl.gov> 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 > > SysKonnect and Intel EEPRO-1000 have the similar pricey, but they work well. > The Tigon-II based NetGear card is cheaper, but has a couple of drawback: > (1) the driver under FreeBSD up/down a couple of times at boottime, > this causes NFS mount failure during boot. It is not a big > deal. I fixed it in rc.local with a line: > > df | grep $mymount_point || mount -a Which driver are you referring to? The Intel card's wx driver had some definite problems here that were/are fixed recently for -current and -stable. The Tigon-II driver doesn't have this problem insofar as I know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 10 17:30:32 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id E786137B614 for ; Mon, 10 Jul 2000 17:30:19 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA29204; Mon, 10 Jul 2000 18:30:11 -0600 (MDT) (envelope-from ken) Date: Mon, 10 Jul 2000 18:30:11 -0600 From: "Kenneth D. Merry" To: Jin Guojun Cc: jhartley@netrail.net, mjacob@feral.com, freebsd-hardware@FreeBSD.ORG Subject: Re: SysKonnect and Intel gig boards Message-ID: <20000710183011.A29172@panzer.kdm.org> References: <200007102356.e6ANuGk18566@portnoy.lbl.gov> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="9amGYk9869ThD9tj" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007102356.e6ANuGk18566@portnoy.lbl.gov>; from jin@george.lbl.gov on Mon, Jul 10, 2000 at 04:56:16PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 10, 2000 at 16:56:16 -0700, Jin Guojun wrote: > Matthew Jacob Wrote: > > > Don't use the wx driven EEPRO-1000 from 4.0 (wait for the 4.1 release which > > will have some bug fixes). > > > > I can't speak about SysKonnect. The Tigon-II based NetGear cards have been > > peachy. > > Just more info.: > > SysKonnect and Intel EEPRO-1000 have the similar pricey, but they work well. > The Tigon-II based NetGear card is cheaper, but has a couple of drawback: > (1) the driver under FreeBSD up/down a couple of times at boottime, > this causes NFS mount failure during boot. It is not a big > deal. I fixed it in rc.local with a line: > > df | grep $mymount_point || mount -a You can fix that by sleeping for 5 seconds or so after the ifconfig. I've got some patches that fix that behavior by waiting for the 5 seconds or the link to come up before returning from the ifconfig. The patches are against the zero copy version of the Tigon driver, and based on a quick test, they won't apply cleanly to the -current version of the driver. You can probably figure out what's going on, though. Anyway, the patches are attached. If you want to try the zero copy code as well, it is located here: http://people.FreeBSD.ORG/~ken/zero_copy/ > (2) chewing significant CPU: (tested on completely idle machines) > 500 MHz P-III + single NetGear A620 I/O > takes 47% CPU time > > 750 MHz AMD K7 + single NetGear A620 I/O > takes less 10% CPU > > 500 MHz P-III + single SysKonnect I/O > takes less 5% CPU What benchmark are you running and what size packets are you using? I think I mentioned to you before that the driver is probably tuned for 9000 byte packets, and you might need to tweak things somewhat to get better performance with 1500 byte packets. > If you have a high end machine, it is probably not a big issue. The driver > chews CPU on both FreeBSD and Linux; so it is driver issue, but O.S. Hopefully, > the newer driver will fix the problem. Ken -- Kenneth Merry ken@kdm.org --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_ti.wait_for_link.20000710" ==== //depot/cam/sys/pci/if_ti.c#32 - /a/ken/perforce2/cam/sys/pci/if_ti.c ==== *** /tmp/tmp.66522.0 Mon Jul 10 18:27:04 2000 --- /a/ken/perforce2/cam/sys/pci/if_ti.c Mon Jul 10 14:46:23 2000 *************** *** 229,234 **** --- 229,235 ---- static void ti_stop __P((struct ti_softc *)); static void ti_watchdog __P((struct ifnet *)); static void ti_shutdown __P((device_t)); + static void ti_link_timeout __P((void *)); static int ti_ifmedia_upd __P((struct ifnet *)); static void ti_ifmedia_sts __P((struct ifnet *, struct ifmediareq *)); *************** *** 966,971 **** --- 967,975 ---- e = &sc->ti_rdata->ti_event_ring[sc->ti_ev_saved_considx]; switch(e->ti_event) { case TI_EV_LINKSTAT_CHANGED: + { + int s; + sc->ti_linkstat = e->ti_code; if (e->ti_code == TI_EV_CODE_LINK_UP) printf("ti%d: 10/100 link up\n", sc->ti_unit); *************** *** 973,979 **** --- 977,996 ---- printf("ti%d: gigabit link up\n", sc->ti_unit); else if (e->ti_code == TI_EV_CODE_LINK_DOWN) printf("ti%d: link down\n", sc->ti_unit); + /* + * If we're waiting for a link event to return from + * an ifconfig type ioctl, wakeup the sleeping + * process. + */ + s = splimp(); + if (sc->ti_flags & TI_FLAG_WAIT_FOR_LINK) { + untimeout(ti_link_timeout, sc, sc->link_handle); + sc->ti_flags &= ~TI_FLAG_WAIT_FOR_LINK; + wakeup(&sc->ti_flags); + } + splx(s); break; + } case TI_EV_ERROR: if (e->ti_code == TI_EV_CODE_ERR_INVAL_CMD) printf("ti%d: invalid command\n", sc->ti_unit); *************** *** 2961,2966 **** --- 2978,2992 ---- struct ti_softc *sc = xsc; int s; + /* + * We only want to initialize once, unless the watchdog timer + * fires or we're resetting the MTU. + */ + #if 0 + if (++sc->num_inits > 1) + return; + #endif + s = splimp(); /* Cancel pending I/O and flush buffers. */ *************** *** 3176,3188 **** --- 3202,3241 ---- case SIOCSIFADDR: case SIOCGIFADDR: error = ether_ioctl(ifp, command, data); + + /* + * If this is somehow our first initialization of the chip + * (the SIOCSIFADDR ioctl called ti_init() already.), we + * need to wait for it to complete. If this isn't the + * first initialization, ti_init() returned without doing + * anything so we don't need to wait. + */ + #if 0 + if ((command == SIOCSIFADDR) + && (sc->num_inits == 1)) { + #endif + if (command == SIOCSIFADDR) { + sc->link_handle = timeout(ti_link_timeout, sc, + TI_LINK_TIMEOUT * hz); + sc->ti_flags |= TI_FLAG_WAIT_FOR_LINK; + do { + tsleep(&sc->ti_flags, PSOCK, "tilksa", 0); + } while (sc->ti_flags & TI_FLAG_WAIT_FOR_LINK); + } break; case SIOCSIFMTU: if (ifr->ifr_mtu > TI_JUMBO_MTU) error = EINVAL; else { ifp->if_mtu = ifr->ifr_mtu; + sc->num_inits = 0; ti_init(sc); + sc->link_handle = timeout(ti_link_timeout, sc, + TI_LINK_TIMEOUT * hz); + sc->ti_flags |= TI_FLAG_WAIT_FOR_LINK; + do { + tsleep(&sc->ti_flags, PSOCK, "tilkmt", 0); + } while (sc->ti_flags & TI_FLAG_WAIT_FOR_LINK); } break; case SIOCSIFFLAGS: *************** *** 3205,3215 **** sc->ti_if_flags & IFF_PROMISC) { TI_DO_CMD(TI_CMD_SET_PROMISC_MODE, TI_CMD_CODE_PROMISC_DIS, 0); ! } else ti_init(sc); } else { if (ifp->if_flags & IFF_RUNNING) { ti_stop(sc); } } sc->ti_if_flags = ifp->if_flags; --- 3258,3297 ---- sc->ti_if_flags & IFF_PROMISC) { TI_DO_CMD(TI_CMD_SET_PROMISC_MODE, TI_CMD_CODE_PROMISC_DIS, 0); ! } else { ti_init(sc); + sc->link_handle = timeout(ti_link_timeout, sc, + TI_LINK_TIMEOUT * hz); + sc->ti_flags |= TI_FLAG_WAIT_FOR_LINK; + do { + tsleep(&sc->ti_flags, PSOCK, + "tilkup", 0); + } while (sc->ti_flags & TI_FLAG_WAIT_FOR_LINK); + } } else { if (ifp->if_flags & IFF_RUNNING) { + /* + * XXX KDM for some reason when you take + * the link down, it doesn't always give + * you a link down event. Because of that, + * you'll never wake up from the sleep if + * you tsleep waiting for the link to come + * up. + */ + #if 0 + printf("ti%d: taking interface down\n", + sc->ti_unit); + #endif ti_stop(sc); + #if 0 + sc->ti_flags |= TI_FLAG_WAIT_FOR_LINK; + do { + tsleep(&sc->ti_flags, PSOCK, + "tilkdn", 0); + } while (sc->ti_flags & TI_FLAG_WAIT_FOR_LINK); + printf("ti%d: interface is down\n", + sc->ti_unit); + #endif } } sc->ti_if_flags = ifp->if_flags; *************** *** 3256,3261 **** --- 3338,3365 ---- return(0); } + static void + ti_link_timeout(arg) + void *arg; + { + struct ti_softc *sc; + int s; + + sc = (struct ti_softc *)arg; + + if (sc == NULL) + return; + + s = splimp(); + if (sc->ti_flags & TI_FLAG_WAIT_FOR_LINK) { + sc->ti_flags &= ~TI_FLAG_WAIT_FOR_LINK; + wakeup(&sc->ti_flags); + } + splx(s); + printf("ti%d: timeout waiting for link (waited %d seconds)\n", + sc->ti_unit, TI_LINK_TIMEOUT); + } + static int ti_close(dev_t dev, int flag, int fmt, struct proc *p) { *************** *** 3564,3569 **** --- 3668,3674 ---- splx(s); printf("ti%d: watchdog timeout -- resetting\n", sc->ti_unit); + sc->num_inits = 0; ti_stop(sc); ti_init(sc); ==== //depot/cam/sys/pci/if_tireg.h#16 - /a/ken/perforce2/cam/sys/pci/if_tireg.h ==== *** /tmp/tmp.66522.1 Mon Jul 10 18:27:04 2000 --- /a/ken/perforce2/cam/sys/pci/if_tireg.h Tue Jun 27 17:13:23 2000 *************** *** 983,991 **** --- 983,997 ---- TI_FLAG_WAIT_FOR_LINK = 0x02 } ti_flag_vals; + /* + * Wait 5 seconds for link, then give up. + */ + #define TI_LINK_TIMEOUT 5 + struct ti_softc { STAILQ_ENTRY(ti_softc) ti_links; struct arpcom arpcom; /* interface info */ + int num_inits; bus_space_handle_t ti_bhandle; vm_offset_t ti_vhandle; bus_space_tag_t ti_btag; *************** *** 1021,1026 **** --- 1027,1033 ---- int ti_txcnt; ti_flag_vals ti_flags; dev_t dev; + struct callout_handle link_handle; }; /* --9amGYk9869ThD9tj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 2:17:42 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from paperboy.sixforty.co.uk (paperboy.sixforty.co.uk [195.10.242.11]) by hub.freebsd.org (Postfix) with ESMTP id C031737B5CC for ; Tue, 11 Jul 2000 02:17:38 -0700 (PDT) (envelope-from lawrence@epcdirect.co.uk) Received: from mail.shorewood-epc.co.uk (mail.shorewood-epc.co.uk [195.10.240.17]) by paperboy.sixforty.co.uk (8.9.3/8.9.3) with ESMTP id KAA92106 for ; Tue, 11 Jul 2000 10:17:36 +0100 (BST) (envelope-from lawrence@epcdirect.co.uk) Received: from lfarr (bka.shorewood-epc.co.uk [192.168.15.200]) by mail.shorewood-epc.co.uk (8.9.3/8.9.3) with SMTP id KAA03057 for ; Tue, 11 Jul 2000 10:17:34 +0100 (BST) (envelope-from lawrence@epcdirect.co.uk) Reply-To: From: "Lawrence Farr" To: Subject: Tigon-II boards (Was sysconnect and intel gig boards) Date: Tue, 11 Jul 2000 10:17:38 +0100 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) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal In-Reply-To: <200007102356.e6ANuGk18566@portnoy.lbl.gov> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am seeing the same problem with the card going up and down at boot time, which stops netatalk from running. Unfortunately, every time you start netatalk it brings the card down then up again. Are there any patches for this as yet? Lawrence Farr EPC Direct Limited mailto:lawrence@epcdirect.co.uk T:01179666123 F:01179666111 M:07970780901 > -----Original Message----- > From: owner-freebsd-hardware@FreeBSD.ORG > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf Of Jin Guojun (DSD > staff) > Sent: 11 July 2000 00:56 > To: jhartley@netrail.net; mjacob@feral.com > Cc: freebsd-hardware@FreeBSD.ORG > Subject: Re: SysKonnect and Intel gig boards > > > Matthew Jacob Wrote: > > > Don't use the wx driven EEPRO-1000 from 4.0 (wait for the 4.1 > release which > > will have some bug fixes). > > > > I can't speak about SysKonnect. The Tigon-II based NetGear > cards have been > > peachy. > > Just more info.: > > SysKonnect and Intel EEPRO-1000 have the similar pricey, but they > work well. > The Tigon-II based NetGear card is cheaper, but has a couple of drawback: > (1) the driver under FreeBSD up/down a couple of times at boottime, > this causes NFS mount failure during boot. It is not a big > deal. I fixed it in rc.local with a line: > > df | grep $mymount_point || mount -a > > (2) chewing significant CPU: (tested on completely idle machines) > 500 MHz P-III + single NetGear A620 I/O > takes 47% CPU time > > 750 MHz AMD K7 + single NetGear A620 I/O > takes less 10% CPU > > 500 MHz P-III + single SysKonnect I/O > takes less 5% CPU > > If you have a high end machine, it is probably not a big issue. The driver > chews CPU on both FreeBSD and Linux; so it is driver issue, but > O.S. Hopefully, > the newer driver will fix the problem. > > -Jin > > > On Mon, 10 Jul 2000, Jeff Hartley wrote: > > > > > Anyone have any experience (good/bad/indifferent) with the Intel GigSX > > > boards, or the SysKonnect dual-port GigSX boards, under > 4.0-RELEASE? I'm in > > > need of quad-gig boxes, and I'm reluctant to stick with 3COM, > based on an > > > unsatisfactory failure rate in the past. Horror stories or blessings, > > > anyone? I did notice that SysKonnect seems to be friendlier with the > > > developer community than Intel (go figure). > > > > > > Thanks, > > > -Jeff Hartley > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 2:53: 3 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id B3D1F37B5F3 for ; Tue, 11 Jul 2000 02:52:50 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 21291 invoked from network); 11 Jul 2000 09:52:45 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 11 Jul 2000 09:52:45 -0000 Date: Tue, 11 Jul 2000 19:52:40 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: ohoyer@fbwi.fh-wilhelmshaven.de Cc: Brian Handy , freebsd-hardware@FreeBSD.ORG Subject: Re: Serial I/O thruput In-Reply-To: <396A21AC.A43F233E@nightfire.de> 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 Mon, 10 Jul 2000, Olaf Hoyer wrote: > > However...I'm not sure how fast I can push data into the motherboard over > > these ports. I don't have any hardware yet (that's what the proposal is Not very fast. Maybe 90K/sec using 8 standard ports or 1 nonstandard one. > Well, the standard 16550 FIFO is capable of shovelling about 115200 bps. More like 1.5 Mbps, actually. Even 8250's can handle low speeds like 115200 bps. Standard hardware is bug for bug compatible with original pre-ISA hardware, so it uses a 1.8432 MHz crystal and can't go faster than 1.8432 * 10^5 / 16 = 115200 bps. > There are better chips available, that shall be able to do more than > (IIRC, 8 times) that value. YOu need some special drivers for that. Boards with higher frequency crystals are usually shipped with newer UARTS with larger FIFOs since feeble drivers/OSes can't drain the 16550 FIFO fast enough. This makes little difference under FreeBSD since the bottleneck is the ISA bus (or the slow interface to the PCI bus in the case of the pci cyclades-Y (non-16550) hardware), provided the CPU is not too slow (P5 or better). Some simple modifications are required to support speeds above 115200 bps under FreeBSD. The pc98 version of sio already has them. The cyclades driver is arbitrarily limited to 150000 bps (some versions of the hardware work at 300000 bps). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 7: 7:21 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 6BB6537C46D for ; Tue, 11 Jul 2000 07:07:16 -0700 (PDT) (envelope-from brandon@schoolpeople.net) Received: from bach ([24.27.10.76]) by gabriel.schoolpeople.net (8.9.3/8.9.3) with SMTP id JAA65824; Tue, 11 Jul 2000 09:07:07 -0500 (CDT) (envelope-from brandon@schoolpeople.net) Message-ID: <002301bfeb41$82091c60$1301a8c0@bach> From: "Brandon DeYoung" To: , "steinyv" References: <4.2.0.58.20000710181742.009c4b30@> Subject: Re: requirements Date: Tue, 11 Jul 2000 09:07:57 -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.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >what kind of requirements does a dns server require??? > >thanks A 4 GB hard drive is more than you'd ever need for a DNS box. As far as other requirements; 64MB RAM should be more than enough. The one I built is currently running on a 466 Celeron which it hardly uses. If your site is getting very high traffic volume you may want to increase processor and RAM. ~Brandon ----- Original Message ----- From: "steinyv" To: Sent: Monday, July 10, 2000 5:18 PM Subject: RE: requirements > How about disk space. I was just wondering, is seems that it will need a > lot of space??? > > At 05:39 PM 7/10/00 , you wrote: > >minimum - 486/25 with 8 to 12 meg > > > >-----Original Message----- > >From: steinyv [mailto:steinyv@skyweb.net] > >Sent: Monday, July 10, 2000 3:59 PM > >To: freebsd-hardware@freebsd.org > >Subject: requirements > > > > > >what kind of requirements does a dns server require??? > >thanks > > > >_________________________________________ > >Steiny's Studio > >Pachyderm Productions > >http://steiny.hypermart.net > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-hardware" in the body of the message > > > _________________________________________ > Steiny's Studio > Pachyderm Productions > http://steiny.hypermart.net > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 13:18:14 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by hub.freebsd.org (Postfix) with ESMTP id 2E1E337B7E8; Tue, 11 Jul 2000 13:18:04 -0700 (PDT) (envelope-from john@essenz.com) Received: from localhost (john@localhost) by athena.lightningone.net (8.9.3/8.9.3) with ESMTP id QAA04948; Tue, 11 Jul 2000 16:39:15 -0400 (EDT) (envelope-from john@essenz.com) X-Authentication-Warning: athena.lightningone.net: john owned process doing -bs Date: Tue, 11 Jul 2000 16:39:15 -0400 (EDT) From: Essenz Consulting X-Sender: john@athena.lightningone.net To: hackers@freebsd.org, hardware@freebsd.org Subject: 160/m support... 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 Just curious, This has probably been asked before, but.. Is Adaptec aic-7892 and 7899 160/m SCSI support in the pipeline to be worked on? aka, has adaptec released any info to those FreeBSD team members who work on the SCSI drivers? Is it possible that maybe within the next 4 months 160/m support will exist in FreeBSD 4/5? -john v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 14: 2: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 4218237B662; Tue, 11 Jul 2000 14:01:59 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA38548; Tue, 11 Jul 2000 15:01:53 -0600 (MDT) (envelope-from ken) Date: Tue, 11 Jul 2000 15:01:53 -0600 From: "Kenneth D. Merry" To: Essenz Consulting Cc: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: 160/m support... Message-ID: <20000711150153.A38521@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from john@essenz.com on Tue, Jul 11, 2000 at 04:39:15PM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 11, 2000 at 16:39:15 -0400, Essenz Consulting wrote: > Just curious, > > This has probably been asked before, but.. > > Is Adaptec aic-7892 and 7899 160/m SCSI support in the pipeline to be > worked on? aka, has adaptec released any info to those FreeBSD team > members who work on the SCSI drivers? Is it possible that maybe within the > next 4 months 160/m support will exist in FreeBSD 4/5? It's working, but isn't in the tree yet. You'll need to ask Justin Gibbs if you want any more information... Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 16:46:53 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from smyk.apk.net (smyk.apk.net [207.54.158.17]) by hub.freebsd.org (Postfix) with ESMTP id 21E8B37B8D1 for ; Tue, 11 Jul 2000 16:46:48 -0700 (PDT) (envelope-from ipswitch@junior.apk.net) Received: from junior.apk.net (ipswitch@junior.apk.net [207.54.158.20]) by smyk.apk.net (8.9.3/8.9.3/apk.990812+rchk1.22+bspm1.13.1.5) with ESMTP id TAA27723 for ; Tue, 11 Jul 2000 19:37:12 -0400 (EDT) Received: (from ipswitch@localhost) by junior.apk.net (8.9.3/8.9.3) id TAA27215 for freebsd-hardware@freebsd.org; Tue, 11 Jul 2000 19:37:12 -0400 (EDT) X-Real-To: freebsd-hardware@freebsd.org Date: Tue, 11 Jul 2000 19:37:12 -0400 From: Ipswitch To: freebsd-hardware@freebsd.org Subject: Re: requirements Message-ID: <20000711193712.A21444@junior.apk.net> References: <4.2.0.58.20000710181742.009c4b30@> <002301bfeb41$82091c60$1301a8c0@bach> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <002301bfeb41$82091c60$1301a8c0@bach>; from Brandon DeYoung on Tue, Jul 11, 2000 at 09:07:57AM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 11, 2000 at 09:07:57AM -0500, Brandon DeYoung wrote: > > >what kind of requirements does a dns server require??? > > >thanks > > A 4 GB hard drive is more than you'd ever need for a DNS box. As far as > other requirements; 64MB RAM should be more than enough. The one I built is > currently running on a 466 Celeron which it hardly uses. If your site is > getting very high traffic volume you may want to increase processor and RAM. If the machine is only running bind, then the HD space requirements for that are low. Logging may take up a fair bit of room. I'd agree that a 4 GB HD is fine. The main thing that a DNS server needs is RAM. Lots of it! last pid: 7830; load averages: 0.42, 0.41, 0.38 19:27:45 40 processes: 39 sleeping, 1 on cpu CPU states: 79.7% idle, 9.5% user, 10.8% kernel, 0.0% iowait, 0.0% swap Memory: 256M real, 7652K free, 7676K swap in use, 505M swap free PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND 13381 root 1 33 0 67M 65M sleep 32.5H 13.50% named That's about normal, although I've seen it as high as 100 MB. Zone transfers actually take more CPU and I/O than named itself. I'd recommend something with high quality, like maybe an IBM PC Server or Netfinity. You want something that will be extremely reliable. (A Sun SparcStation 20 in good shape is also ideal, but you probably want to stick with the x86 platform.) Don't bother with a fast hard drive. Go for a cool-running 5400 RPM model that will last longer. A Celeron 466 is probably overkill, although I think I'd prefer a P-II 400 since it has the 100 MHz bus. Perhaps an AMD K6-2 on a Super 7 board? Even a Pentium 200 will probably be enough horsepower for most nameservers. Did I mention that you want lots of RAM? :-) Running RCS on the zone files and named.conf is also a good idea, as are frequent backups. Stuart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 17:39:14 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from uhura.concentric.net (uhura.concentric.net [206.173.118.93]) by hub.freebsd.org (Postfix) with ESMTP id 605E037B903 for ; Tue, 11 Jul 2000 17:38:42 -0700 (PDT) (envelope-from arubin@concentric.net) Received: from marconi.concentric.net (marconi.concentric.net [206.173.118.71]) by uhura.concentric.net (8.9.1a/(98/12/15 5.12)) id UAA23122; Tue, 11 Jul 2000 20:38:41 -0400 (EDT) [1-800-745-2747 The Concentric Network] Received: from r2d2 (w184.z064001133.chi-il.dsl.cnc.net [64.1.133.184]) by marconi.concentric.net (8.9.1a) id UAA22042; Tue, 11 Jul 2000 20:38:40 -0400 (EDT) Message-ID: <002501bfeb9a$36bbc6f0$b8850140@r2d2> From: "Anthony Rubin" To: Subject: Asus K7V with Crucial PC133 ECC RAM Date: Tue, 11 Jul 2000 19:43:36 -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.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I recently put together a system that uses the Asus K7V motherboard with Crucial PC133 ECC RAM. I bought 2 128MB DIMMs. The BIOS is seeing the RAM correctly as 264144K, but FreeBSD has 262064K listed under real memory. I thought this was odd and wanted to make sure one of the DIMMs wasn't bad so I removed both and then tried one at a time. No matter which DIMM I use and which slot I put it in the BIOS sees 131072K and FreeBSD sees 130992K. The only other thing that is strange about this setup is that the K7V BIOS currently has a known problem when you enable ECC so ECC is currently disabled on my board. Below is the portion of dmesg I am referring to. > dmesg | grep memory real memory = 268353536 (262064K bytes) avail memory = 256950272 (250928K bytes) Perhaps I am being a bit paranoid but I'd rather exchange parts now if I have to. I ran a cvsup and make world without any problems. I also ran the dnetc client for a day without problems. While this probably proves nothing, the system does seem to be running great. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 17:52:42 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id E34FA37B763 for ; Tue, 11 Jul 2000 17:52:39 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA00561; Tue, 11 Jul 2000 18:00:55 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007120100.SAA00561@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Anthony Rubin" Cc: freebsd-hardware@freebsd.org Subject: Re: Asus K7V with Crucial PC133 ECC RAM In-reply-to: Your message of "Tue, 11 Jul 2000 19:43:36 CDT." <002501bfeb9a$36bbc6f0$b8850140@r2d2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jul 2000 18:00:55 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I recently put together a system that uses the Asus K7V motherboard with > Crucial PC133 ECC RAM. I bought 2 128MB DIMMs. The BIOS is seeing the RAM > correctly as 264144K, but FreeBSD has 262064K listed under real memory. I > thought this was odd and wanted to make sure one of the DIMMs wasn't bad so > I removed both and then tried one at a time. No matter which DIMM I use and > which slot I put it in the BIOS sees 131072K and FreeBSD sees 130992K. The > only other thing that is strange about this setup is that the K7V BIOS > currently has a known problem when you enable ECC so ECC is currently > disabled on my board. Below is the portion of dmesg I am referring to. > > > dmesg | grep memory > real memory = 268353536 (262064K bytes) > avail memory = 256950272 (250928K bytes) There's nothing wrong with your RAM - some of it is being used by the kernel. > Perhaps I am being a bit paranoid but I'd rather exchange parts now if I > have to. I ran a cvsup and make world without any problems. I also ran the > dnetc client for a day without problems. While this probably proves > nothing, the system does seem to be running great. Memory doesn't just sort of dribble away when it's faulty. 8) -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 19:24:27 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from devils.maquina.com (devils.maquina.com [62.229.71.43]) by hub.freebsd.org (Postfix) with ESMTP id C820537BA6C; Tue, 11 Jul 2000 19:24:23 -0700 (PDT) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.maquina.com (8.9.3/8.9.3) with ESMTP id DAA24495; Wed, 12 Jul 2000 03:24:21 +0100 (WEST) (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.maquina.com: gabriel owned process doing -bs Date: Wed, 12 Jul 2000 03:24:21 +0100 (WEST) From: Jose Gabriel Marcelino To: Mike Smith Cc: Anthony Rubin , freebsd-hardware@FreeBSD.ORG Subject: Re: Asus K7V with Crucial PC133 ECC RAM In-Reply-To: <200007120100.SAA00561@mass.osd.bsdi.com> 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 > > Perhaps I am being a bit paranoid but I'd rather exchange parts now if I > > have to. I ran a cvsup and make world without any problems. I also ran the > > dnetc client for a day without problems. While this probably proves > > nothing, the system does seem to be running great. > > Memory doesn't just sort of dribble away when it's faulty. 8) > Strange as it may seem (it totally freaked me out) I saw this happening on a Asus K7M motherboard. These boards where very picky with RAM, I had them running with no-name 128Mb DIMM and altough the BIOS and Windows both said I had 128MB, Linux (I didn't get to install FreeBSD at the time) alternated in values around 64-72Mb of available memory. The system was very slow (it only really had those 64Mb working in Linux) and crashed *A LOT*. Once replaced with 128Mb CAS2 DIMMS from Crucial, Linux always detected the 128Mb just fine and run without more trouble (apart from the usual Linux ones, that is :) I'll send a gift to the first one who explains why did the system behave that way. I've never bought no-name since then and I'm always more than happy to spend more but get much more quality from Crucial. Regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 20: 7:14 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id D7C6437B7EF; Tue, 11 Jul 2000 20:07:08 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id MAA30489; Wed, 12 Jul 2000 12:37:04 +0930 (CST) (envelope-from grog) Date: Wed, 12 Jul 2000 12:37:04 +0930 From: Greg Lehey To: Mike Smith Cc: Anthony Rubin , freebsd-hardware@FreeBSD.ORG Subject: Re: Asus K7V with Crucial PC133 ECC RAM Message-ID: <20000712123704.E30262@wantadilla.lemis.com> References: <002501bfeb9a$36bbc6f0$b8850140@r2d2> <200007120100.SAA00561@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200007120100.SAA00561@mass.osd.bsdi.com> Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 11 July 2000 at 18:00:55 -0700, Mike Smith wrote: >> I recently put together a system that uses the Asus K7V motherboard with >> Crucial PC133 ECC RAM. I bought 2 128MB DIMMs. The BIOS is seeing the RAM >> correctly as 264144K, but FreeBSD has 262064K listed under real memory. I >> thought this was odd and wanted to make sure one of the DIMMs wasn't bad so >> I removed both and then tried one at a time. No matter which DIMM I use and >> which slot I put it in the BIOS sees 131072K and FreeBSD sees 130992K. The >> only other thing that is strange about this setup is that the K7V BIOS >> currently has a known problem when you enable ECC so ECC is currently >> disabled on my board. Below is the portion of dmesg I am referring to. >> >>> dmesg | grep memory >> real memory = 268353536 (262064K bytes) >> avail memory = 256950272 (250928K bytes) > > There's nothing wrong with your RAM - some of it is being used by the > kernel. I think he's referring to the 80 kB that don't show up in real memory. I'd assume that's the BIOS. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 20:23:40 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from uhura.concentric.net (uhura.concentric.net [206.173.118.93]) by hub.freebsd.org (Postfix) with ESMTP id 756CE37BB6D; Tue, 11 Jul 2000 20:23:35 -0700 (PDT) (envelope-from arubin@concentric.net) Received: from marconi.concentric.net (marconi.concentric.net [206.173.118.71]) by uhura.concentric.net (8.9.1a/(98/12/15 5.12)) id XAA29586; Tue, 11 Jul 2000 23:23:33 -0400 (EDT) [1-800-745-2747 The Concentric Network] Received: from r2d2 (w184.z064001133.chi-il.dsl.cnc.net [64.1.133.184]) by marconi.concentric.net (8.9.1a) id XAA12522; Tue, 11 Jul 2000 23:23:32 -0400 (EDT) Message-ID: <006501bfebb1$3ea5df60$b8850140@r2d2> From: "Anthony Rubin" To: "Greg Lehey" , "Mike Smith" Cc: References: <002501bfeb9a$36bbc6f0$b8850140@r2d2> <200007120100.SAA00561@mass.osd.bsdi.com> <20000712123704.E30262@wantadilla.lemis.com> Subject: Re: Asus K7V with Crucial PC133 ECC RAM Date: Tue, 11 Jul 2000 22:28:27 -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.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just realized there is an error in my original post. The system reports 262144K with 256MB installed. This means FreeBSD always reports 80K less. ----- Original Message ----- From: "Greg Lehey" To: "Mike Smith" Cc: "Anthony Rubin" ; Sent: Tuesday, July 11, 2000 10:07 PM Subject: Re: Asus K7V with Crucial PC133 ECC RAM > On Tuesday, 11 July 2000 at 18:00:55 -0700, Mike Smith wrote: > >> I recently put together a system that uses the Asus K7V motherboard with > >> Crucial PC133 ECC RAM. I bought 2 128MB DIMMs. The BIOS is seeing the RAM > >> correctly as 264144K, but FreeBSD has 262064K listed under real memory. I > >> thought this was odd and wanted to make sure one of the DIMMs wasn't bad so > >> I removed both and then tried one at a time. No matter which DIMM I use and > >> which slot I put it in the BIOS sees 131072K and FreeBSD sees 130992K. The > >> only other thing that is strange about this setup is that the K7V BIOS > >> currently has a known problem when you enable ECC so ECC is currently > >> disabled on my board. Below is the portion of dmesg I am referring to. > >> > >>> dmesg | grep memory > >> real memory = 268353536 (262064K bytes) > >> avail memory = 256950272 (250928K bytes) > > > > There's nothing wrong with your RAM - some of it is being used by the > > kernel. > > I think he's referring to the 80 kB that don't show up in real > memory. I'd assume that's the BIOS. > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 11 23:21:40 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-193-112-57.dsl.snfc21.pacbell.net [63.193.112.57]) by hub.freebsd.org (Postfix) with ESMTP id 5F1D037BC37 for ; Tue, 11 Jul 2000 23:21:31 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA00772; Tue, 11 Jul 2000 23:29:49 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007120629.XAA00772@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Anthony Rubin" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Asus K7V with Crucial PC133 ECC RAM In-reply-to: Your message of "Tue, 11 Jul 2000 22:28:27 CDT." <006501bfebb1$3ea5df60$b8850140@r2d2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Jul 2000 23:29:49 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ahh, yes. Well, in this case the amount of memory 'lost' is indeed inversely proportional to the quality of your RAM. The better your RAM, the less capacity that's lost through various coupling issues. You can also improve things by rotating your RAM regularly, and cleaning the contacts with fine wet-and-dry sandpaper every couple of months to reduce oxidation. Also you may find that as your RAM is "broken in" it will regain a little capacity - using a "RAM exerciser" program here can help. Of course, the law of diminishing returns applies as well; spending twice as much on RAM isn't going to result in RAM that only "loses" half as much - there's some "RAM loss" that's just inevitable. Orientation of the system is also important - and if you're really unlucky you can end up with RAM that's designed for use in the southern hemisphere. Due to the manufacturing processes there's always more of it than the northern hemisphere type so the chip makers tend to try to dump it into the channel. Typically the sort of "loss" you're seeing (0.03%) is considered quite acceptable - I'd expect that you can probably soak up at least 10x this with an Enlightenment theme or a neat desktop sound scheme. > I just realized there is an error in my original post. The system reports > 262144K with 256MB installed. This means FreeBSD always reports 80K less. > > ----- Original Message ----- > From: "Greg Lehey" > To: "Mike Smith" > Cc: "Anthony Rubin" ; > Sent: Tuesday, July 11, 2000 10:07 PM > Subject: Re: Asus K7V with Crucial PC133 ECC RAM > > > > On Tuesday, 11 July 2000 at 18:00:55 -0700, Mike Smith wrote: > > >> I recently put together a system that uses the Asus K7V motherboard > with > > >> Crucial PC133 ECC RAM. I bought 2 128MB DIMMs. The BIOS is seeing the > RAM > > >> correctly as 264144K, but FreeBSD has 262064K listed under real memory. > I > > >> thought this was odd and wanted to make sure one of the DIMMs wasn't > bad so > > >> I removed both and then tried one at a time. No matter which DIMM I > use and > > >> which slot I put it in the BIOS sees 131072K and FreeBSD sees 130992K. > The > > >> only other thing that is strange about this setup is that the K7V BIOS > > >> currently has a known problem when you enable ECC so ECC is currently > > >> disabled on my board. Below is the portion of dmesg I am referring to. > > >> > > >>> dmesg | grep memory > > >> real memory = 268353536 (262064K bytes) > > >> avail memory = 256950272 (250928K bytes) > > > > > > There's nothing wrong with your RAM - some of it is being used by the > > > kernel. > > > > I think he's referring to the 80 kB that don't show up in real > > memory. I'd assume that's the BIOS. > > > > Greg > > -- > > Finger grog@lemis.com for PGP public key > > See complete headers for address and phone numbers > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > For those of you with no bloody sense of humour, the real reason is that the BIOS has reserved some memory for its own use, as Greg correctly pointed out. If you've studied this entire message for signs I'm on illegal drugs - sorry. 8) -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 12 8:22: 6 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 02B5437C08B; Wed, 12 Jul 2000 08:22:02 -0700 (PDT) (envelope-from jin@portnoy.lbl.gov) Received: (from jin@localhost) by portnoy.lbl.gov (8.10.0/8.10.0) id e6CFLjQ22630; Wed, 12 Jul 2000 08:21:45 -0700 (PDT) Date: Wed, 12 Jul 2000 08:21:45 -0700 (PDT) From: Jin Guojun (DSD staff) Message-Id: <200007121521.e6CFLjQ22630@portnoy.lbl.gov> To: arubin@concentric.net, msmith@FreeBSD.ORG Subject: Re: Asus K7V with Crucial PC133 ECC RAM Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I do not think there is any thing to do with memory chips, but the O.S. By carefully tested on many systems with different CPU, M/B and memory, I found that this happenes on all systems we have here with running 4.x or CURRENT. The real memory is 12kB to 16kB less the BIOS says. Attach another disk with 2.2.8 and 3.5 does not have such phenomena. A wild guessing is that either 4.x or later reports real-real availiable amount to the system, or the new bus system intends to do so. Maybe someone from the coreteam can tell what is the true story. -Jin > Ahh, yes. Well, in this case the amount of memory 'lost' is indeed > inversely proportional to the quality of your RAM. The better your RAM, > the less capacity that's lost through various coupling issues. You can > also improve things by rotating your RAM regularly, and cleaning the > contacts with fine wet-and-dry sandpaper every couple of months to reduce > oxidation. Also you may find that as your RAM is "broken in" it will > regain a little capacity - using a "RAM exerciser" program here can help. > > Of course, the law of diminishing returns applies as well; spending > twice as much on RAM isn't going to result in RAM that only "loses" half > as much - there's some "RAM loss" that's just inevitable. Orientation of > the system is also important - and if you're really unlucky you can end > up with RAM that's designed for use in the southern hemisphere. Due to > the manufacturing processes there's always more of it than the northern > hemisphere type so the chip makers tend to try to dump it into the channel. > > Typically the sort of "loss" you're seeing (0.03%) is considered quite > acceptable - I'd expect that you can probably soak up at least 10x this > with an Enlightenment theme or a neat desktop sound scheme. > > > I just realized there is an error in my original post. The system reports > > 262144K with 256MB installed. This means FreeBSD always reports 80K less. > > > > ----- Original Message ----- > > From: "Greg Lehey" > > To: "Mike Smith" > > Cc: "Anthony Rubin" ; > > Sent: Tuesday, July 11, 2000 10:07 PM > > Subject: Re: Asus K7V with Crucial PC133 ECC RAM > > > > > > > On Tuesday, 11 July 2000 at 18:00:55 -0700, Mike Smith wrote: > > > >> I recently put together a system that uses the Asus K7V motherboard > > with > > > >> Crucial PC133 ECC RAM. I bought 2 128MB DIMMs. The BIOS is seeing the > > RAM > > > >> correctly as 264144K, but FreeBSD has 262064K listed under real memory. > > I > > > >> thought this was odd and wanted to make sure one of the DIMMs wasn't > > bad so > > > >> I removed both and then tried one at a time. No matter which DIMM I > > use and > > > >> which slot I put it in the BIOS sees 131072K and FreeBSD sees 130992K. > > The > > > >> only other thing that is strange about this setup is that the K7V BIOS > > > >> currently has a known problem when you enable ECC so ECC is currently > > > >> disabled on my board. Below is the portion of dmesg I am referring to. > > > >> > > > >>> dmesg | grep memory > > > >> real memory = 268353536 (262064K bytes) > > > >> avail memory = 256950272 (250928K bytes) > > > > > > > > There's nothing wrong with your RAM - some of it is being used by the > > > > kernel. > > > > > > I think he's referring to the 80 kB that don't show up in real > > > memory. I'd assume that's the BIOS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 12 8:45: 2 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.hcvlny.cv.net (mx1.hcvlny.cv.net [167.206.112.76]) by hub.freebsd.org (Postfix) with ESMTP id 9CDE337B809 for ; Wed, 12 Jul 2000 08:44:58 -0700 (PDT) (envelope-from steinyv@skyweb.net) Received: from s1.optonline.net (s1.optonline.net [167.206.112.6]) by mx1.hcvlny.cv.net (8.9.3/8.9.3) with ESMTP id LAA11121 for ; Wed, 12 Jul 2000 11:44:57 -0400 (EDT) Received: from downstairs (d133-103.jcsnnj.optonline.net [24.189.133.103]) by s1.optonline.net (8.9.1/8.9.3) with ESMTP id LAA10056 for ; Wed, 12 Jul 2000 11:44:57 -0400 (EDT) Message-Id: <4.2.0.58.20000712112207.009fd740@> X-Sender: steinyv@pluto.skyweb.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 12 Jul 2000 11:23:18 -0400 To: freebsd-hardware@freebsd.org From: steinyv Subject: boot glitch Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey all, I purchased a symbios 8751sp scsi card to go with a Micronics M55Hi rev B motherboard with a P200 & 64M and 2M s3 video. Every time I try to boot (I had a previous install on disk) or when I try to install via floppy or cd, when the time came for scsi devices to settle, the screen keeps scrolling an error to the point where whatever it is being displayed, cant be read. From what I can decipher, SCSI BUS RESET DETECTED PCI STATUS : 0X8100 (0/5) @ (SCRIPT 48:F33100004) SYM0 REGDUMP : CA 00 00 05 47 00 00 0E 00 08 00 00 08 00 08 02 00 70 E3 03 I have 2 of these cards and both get this error on this board, I used to have an Adaptec 2940uw that worked with the board, and from the dmesg output there were no problems. Ill try some other stuff in the meantime, what do you think?? Thanks PS Sorry for the cross post, I didnt seem to be getting any suggestions from questions so Ill post to a more appropriate group.......... _________________________________________ Steiny's Studio Pachyderm Productions http://steiny.hypermart.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 12 10:12:37 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 9EAE937BF87 for ; Wed, 12 Jul 2000 10:12:28 -0700 (PDT) (envelope-from brandon@schoolpeople.net) Received: from triangulata (cs2887-130.austin.rr.com [24.28.87.130]) by gabriel.schoolpeople.net (8.9.3/8.9.3) with SMTP id MAA69508 for ; Wed, 12 Jul 2000 12:12:27 -0500 (CDT) (envelope-from brandon@schoolpeople.net) Message-ID: <005701bfec24$e9b9a9e0$82571c18@austin.rr.com> From: "Brandon S. DeYoung" To: References: <200007120629.XAA00772@mass.osd.bsdi.com> Subject: Re: Asus K7V with Crucial PC133 ECC RAM Date: Wed, 12 Jul 2000 12:16:22 -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.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > ......using a "RAM exerciser" program here can help.... I hear they got a good "RAM exerciser" program here: http://microsoft.com/presspass/features/2000/jul00/07-12ie5.5.asp ----- Original Message ----- From: "Mike Smith" To: "Anthony Rubin" Cc: Sent: Wednesday, July 12, 2000 1:29 AM Subject: Re: Asus K7V with Crucial PC133 ECC RAM > > Ahh, yes. Well, in this case the amount of memory 'lost' is indeed > inversely proportional to the quality of your RAM. The better your RAM, > the less capacity that's lost through various coupling issues. You can > also improve things by rotating your RAM regularly, and cleaning the > contacts with fine wet-and-dry sandpaper every couple of months to reduce > oxidation. Also you may find that as your RAM is "broken in" it will > regain a little capacity - using a "RAM exerciser" program here can help. > > Of course, the law of diminishing returns applies as well; spending > twice as much on RAM isn't going to result in RAM that only "loses" half > as much - there's some "RAM loss" that's just inevitable. Orientation of > the system is also important - and if you're really unlucky you can end > up with RAM that's designed for use in the southern hemisphere. Due to > the manufacturing processes there's always more of it than the northern > hemisphere type so the chip makers tend to try to dump it into the channel. > > Typically the sort of "loss" you're seeing (0.03%) is considered quite > acceptable - I'd expect that you can probably soak up at least 10x this > with an Enlightenment theme or a neat desktop sound scheme. > > > I just realized there is an error in my original post. The system reports > > 262144K with 256MB installed. This means FreeBSD always reports 80K less. > > > > ----- Original Message ----- > > From: "Greg Lehey" > > To: "Mike Smith" > > Cc: "Anthony Rubin" ; > > Sent: Tuesday, July 11, 2000 10:07 PM > > Subject: Re: Asus K7V with Crucial PC133 ECC RAM > > > > > > > On Tuesday, 11 July 2000 at 18:00:55 -0700, Mike Smith wrote: > > > >> I recently put together a system that uses the Asus K7V motherboard > > with > > > >> Crucial PC133 ECC RAM. I bought 2 128MB DIMMs. The BIOS is seeing the > > RAM > > > >> correctly as 264144K, but FreeBSD has 262064K listed under real memory. > > I > > > >> thought this was odd and wanted to make sure one of the DIMMs wasn't > > bad so > > > >> I removed both and then tried one at a time. No matter which DIMM I > > use and > > > >> which slot I put it in the BIOS sees 131072K and FreeBSD sees 130992K. > > The > > > >> only other thing that is strange about this setup is that the K7V BIOS > > > >> currently has a known problem when you enable ECC so ECC is currently > > > >> disabled on my board. Below is the portion of dmesg I am referring to. > > > >> > > > >>> dmesg | grep memory > > > >> real memory = 268353536 (262064K bytes) > > > >> avail memory = 256950272 (250928K bytes) > > > > > > > > There's nothing wrong with your RAM - some of it is being used by the > > > > kernel. > > > > > > I think he's referring to the 80 kB that don't show up in real > > > memory. I'd assume that's the BIOS. > > > > > > Greg > > > -- > > > Finger grog@lemis.com for PGP public key > > > See complete headers for address and phone numbers > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hardware" in the body of the message > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message > > > > For those of you with no bloody sense of humour, the real reason is that > the BIOS has reserved some memory for its own use, as Greg correctly > pointed out. If you've studied this entire message for signs I'm on > illegal drugs - sorry. 8) > > -- > ... 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] > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 12 10:24:37 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by hub.freebsd.org (Postfix) with ESMTP id 9BCC437BF62; Wed, 12 Jul 2000 10:24:33 -0700 (PDT) (envelope-from john@essenz.com) Received: from localhost (john@localhost) by athena.lightningone.net (8.9.3/8.9.3) with ESMTP id NAA13323; Wed, 12 Jul 2000 13:45:56 -0400 (EDT) (envelope-from john@essenz.com) X-Authentication-Warning: athena.lightningone.net: john owned process doing -bs Date: Wed, 12 Jul 2000 13:45:56 -0400 (EDT) From: Essenz Consulting X-Sender: john@athena.lightningone.net To: hardware@freebsd.org, hackers@freebsd.org Subject: System Crash 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 Question. I have a machine that is crashing. Basically, random processes will die off and give SEGMENTATION FAULTS, then followed by a core dump, and the machine halts. Has to be manual rebooted after that. I tryed another hard drive in the machine, and same problems come up. So I am not sure if it is bad memory or a bad processor, or a bad motherboard. Is there anyway to find out? -john v. e. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 12 10:30:11 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from envy.vuurwerk.nl (envy.vuurwerk.nl [194.178.232.112]) by hub.freebsd.org (Postfix) with SMTP id 146F837BE5D for ; Wed, 12 Jul 2000 10:29:44 -0700 (PDT) (envelope-from petervd@daemon.vuurwerk.nl) Received: (qmail 68391 invoked from network); 12 Jul 2000 17:29:35 -0000 Received: from kesteren.vuurwerk.nl (HELO daemon.vuurwerk.nl) (194.178.232.59) by envy.vuurwerk.nl with SMTP; 12 Jul 2000 17:29:35 -0000 Received: (nullmailer pid 96704 invoked by uid 11109); Wed, 12 Jul 2000 17:29:35 -0000 Date: Wed, 12 Jul 2000 19:29:35 +0200 From: Peter van Dijk To: hackers@FreeBSD.ORG, hardware@freebsd.org Subject: Re: System Crash Message-ID: <20000712192935.G95013@vuurwerk.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from john@essenz.com on Wed, Jul 12, 2000 at 01:45:56PM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jul 12, 2000 at 01:45:56PM -0400, Essenz Consulting wrote: > Question. > > I have a machine that is crashing. Basically, random processes will die > off and give SEGMENTATION FAULTS, then followed by a core dump, and the > machine halts. Has to be manual rebooted after that. I tryed another hard > drive in the machine, and same problems come up. So I am not sure if it is > bad memory or a bad processor, or a bad motherboard. Is there anyway to > find out? Replace one part at a time until the problems go away. Usually bad memory. Adjusting memory timings in your BIOS setup might help too. Greetz, Peter. -- petervd@vuurwerk.nl - Peter van Dijk [student:developer:ircoper] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 12 11: 5:17 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id E202B37BCD4; Wed, 12 Jul 2000 11:05:07 -0700 (PDT) (envelope-from simon@optinet.com) Received: from station1 (adsl-151-202-97-90.bellatlantic.net [151.202.97.90]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id LAA03843; Wed, 12 Jul 2000 11:59:23 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200007121759.LAA03843@mail.fpsn.net> From: "Simon" To: "Essenz Consulting" , "hackers@FreeBSD.ORG" , "hardware@FreeBSD.ORG" Date: Wed, 12 Jul 2000 14:08:06 -0500 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: System Crash Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I say it's a bad memory. I had the same problem. -Simon On Wed, 12 Jul 2000 13:45:56 -0400 (EDT), Essenz Consulting wrote: >Question. > >I have a machine that is crashing. Basically, random processes will die >off and give SEGMENTATION FAULTS, then followed by a core dump, and the >machine halts. Has to be manual rebooted after that. I tryed another hard >drive in the machine, and same problems come up. So I am not sure if it is >bad memory or a bad processor, or a bad motherboard. Is there anyway to >find out? > >-john v. e. > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 13 8:37:47 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from barney.ife.no (barney.ife.no [128.39.229.49]) by hub.freebsd.org (Postfix) with ESMTP id 7130737C1A3 for ; Thu, 13 Jul 2000 08:37:41 -0700 (PDT) (envelope-from stein@ife.no) Received: from ife.no (virginis.ife.no [128.39.229.176]) by barney.ife.no (8.9.3/8.9.3) with ESMTP id RAA14054; Thu, 13 Jul 2000 17:37:38 +0200 (MET DST) Message-ID: <396DE242.879DFCA6@ife.no> Date: Thu, 13 Jul 2000 17:37:38 +0200 From: "Stein M. Sandbech" Reply-To: stein@ife.no Organization: IFE X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: Intel D815EEA. Testing FreeBSD 4.0 on, Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FYI I`ve finished a custom install of FreeBSD 4.0 Release on a brand new Intel motherboard last night, the D815EEA, with integrated LAN, Audio and Graphics. The initial results are summarized below: Configuration: - D815EEA with; * Intel 82562ET 10/100Mbit/sec (nic) component. * Audio (Intel 82801BA+AD1885 analog codec, and Creative Labs ES1373 digital controller and the CS4297 Analog codec). * Intel 82815E Graphics and Memory Controller Hub, the Graphics controller. - Pentium III 733/133MHz CPU. - 128MB PC133 SDRAM, non ECC. - IBM Deskstar 18GB IDE disk. - CDROM/floppy/....... etc The initial install went OK, and after the first reboot I noticed that it did not recognice a valid ethernet controller. I really expected it to see a "fxp" device, but no. I have not tested the audio or graphics parts yet. I expect that I won`t be able to use the older 810 chipset support in XFree86. This board has an AGP4x port, however. I will disable onboard LAN for the time being, and install another nic for further testing of the board. The board are really fast and seems very stable. All i all a nice board. Are there anybody working on support for these new Intel LAN components? I will also install an AGP Graphics card for further testing, I do not expect that the new Intel graphics chip will be supported soon. --Stein Morten -- /* Stein M Sandbech Email: stein@ife.no ** ** Senior Systems Engineer, EDP dept Email: stein@www.ife.no ** ** Institute for Energy Technology Tel: +47 63 80 60 00 ** ** Box 40, N-2007 Kjeller, NORWAY Fax: +47 63 81 11 68 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 13 16:28:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from devils.maquina.com (devils.maquina.com [62.229.71.43]) by hub.freebsd.org (Postfix) with ESMTP id D1B1137B63D for ; Thu, 13 Jul 2000 16:28:27 -0700 (PDT) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.maquina.com (8.9.3/8.9.3) with ESMTP id AAA32857 for ; Fri, 14 Jul 2000 00:28:25 +0100 (WEST) (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.maquina.com: gabriel owned process doing -bs Date: Fri, 14 Jul 2000 00:28:25 +0100 (WEST) From: Jose Gabriel Marcelino To: freebsd-hardware@freebsd.org Subject: Gigabit recommendations 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 Hi, I'm preparing for a Gigabit setup here for a couple of FreeBSD and some Linux boxes. This will actaully be a Gigabit backbone to connect 4 switches over fiber, 1000Base-SX (Yes I know about the 220m limitation over my multimode fiber) I wonder if anyone could give me some recommendations. : I've already read enough about the network cards from the previous posts and it seems SysKonnect are the best, but I may have to go to the 3Com 3c985b Tigon II based cards due to local availability. My main doubt in on the switch side, I'm tempted to go for the 3Com SuperStack II 3900 which I can get for around US$2.400 here for the 24 port version. The 3800 is also tempting with it's layer 3 switching but at US$6.330 a piece it's a bit of overkill and overbudget for my company. Note I only mentioned 3Com here, these are the only ones I could get some info on. I'd be very happy to know other good, trustworthy brands you are using (I think Cisco may be very expensive but I haven't found the correct model yet...) Thanks for all the help. Regards Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 13 20:34:27 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 72AF537B8B4 for ; Thu, 13 Jul 2000 20:34:24 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id WAA16888; Thu, 13 Jul 2000 22:34:08 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 13 Jul 2000 22:34:08 -0500 (CDT) From: Chris Dillon To: Jose Gabriel Marcelino Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Gigabit recommendations 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 Fri, 14 Jul 2000, Jose Gabriel Marcelino wrote: > My main doubt in on the switch side, I'm tempted to go for the 3Com > SuperStack II 3900 which I can get for around US$2.400 here for the 24 > port version. > > The 3800 is also tempting with it's layer 3 switching but at US$6.330 a > piece it's a bit of overkill and overbudget for my company. > > Note I only mentioned 3Com here, these are the only ones I could get some > info on. I'd be very happy to know other good, trustworthy brands you are > using (I think Cisco may be very expensive but I haven't found the correct > model yet...) The 3COM switches are all over-priced CRAP. Go with Cisco or HP ProCurve, which should cost the same or less, respectively, and offer better performance and features. I'm speaking entirely from experience. :-) I've also heard very good things about Extreme Networks and Foundry Networks switches, but I have no personal experience with them. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 14 4:32:28 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from devils.maquina.com (devils.maquina.com [62.229.71.43]) by hub.freebsd.org (Postfix) with ESMTP id EB66437C155 for ; Fri, 14 Jul 2000 04:32:23 -0700 (PDT) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.maquina.com (8.9.3/8.9.3) with ESMTP id MAA35146; Fri, 14 Jul 2000 12:31:59 +0100 (WEST) (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.maquina.com: gabriel owned process doing -bs Date: Fri, 14 Jul 2000 12:31:59 +0100 (WEST) From: Jose Gabriel Marcelino To: Chris Dillon Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Gigabit recommendations 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 Hi! > > Note I only mentioned 3Com here, these are the only ones I could get some > > info on. I'd be very happy to know other good, trustworthy brands you are > > using (I think Cisco may be very expensive but I haven't found the correct > > model yet...) > > The 3COM switches are all over-priced CRAP. Go with Cisco or HP > ProCurve, which should cost the same or less, respectively, and offer > better performance and features. I'm speaking entirely from > experience. :-) I was somewhat expecting that response on 3Com products :) I looked really well into HP and Cisco and I was very surprised to find that the Cisco really is less expensive than 3Com here. The HP one looks nice too, I'm amazed to find a HP product that looks good (and is recommended) after all the mess I've seen with all the brain-damaged Jetdirect printer modules (the printers themselves aren't too good either) and the brain-damaGING HP-UX boxes I've unfortunately had to support :) Thanks a lot for your advice! Regards Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 14 8:12:26 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from barney.ife.no (barney.ife.no [128.39.229.49]) by hub.freebsd.org (Postfix) with ESMTP id 085A737C5DF; Fri, 14 Jul 2000 08:11:57 -0700 (PDT) (envelope-from stein@ife.no) Received: from ife.no (virginis.ife.no [128.39.229.176]) by barney.ife.no (8.9.3/8.9.3) with ESMTP id RAA12793; Fri, 14 Jul 2000 17:11:29 +0200 (MET DST) Message-ID: <396F2DA1.83BC5793@ife.no> Date: Fri, 14 Jul 2000 17:11:29 +0200 From: "Stein M. Sandbech" Reply-To: stein@ife.no Organization: IFE X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Stefan Esser , freebsd-hardware@FreeBSD.org Subject: Re: Intel D815EEA. Testing FreeBSD 4.0 on, References: <396DE242.879DFCA6@ife.no> <20000714093901.A1355@StefanEsser.FreeBSD.org> Content-Type: multipart/mixed; boundary="------------0B020E5659E904BD04F6346D" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------0B020E5659E904BD04F6346D Content-Type: multipart/alternative; boundary="------------8996D72DBAED94EF0F06B7EC" --------------8996D72DBAED94EF0F06B7EC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Stefan Esser wrote: > On 2000-07-13 17:37 +0200, "Stein M. Sandbech" wrote: > > Configuration: > > - D815EEA with; > > * Intel 82562ET 10/100Mbit/sec (nic) component. > > * Audio (Intel 82801BA+AD1885 analog codec, and Creative Labs > > ES1373 digital controller > > and the CS4297 Analog codec). > > * Intel 82815E Graphics and Memory Controller Hub, the Graphics > > controller. > > > The initial install went OK, and after the first reboot I noticed that > > it did not recognice a > > valid ethernet controller. I really expected it to see a "fxp" device, > > but no. snip ... > Can you check the output of "pciconf -l" for the Ethernet function ? > Perhaps it is sufficient to just enter the PCI ID into the list of > known IDs in the fxp driver ... OK, see attached files. I tested a small change to the if_fxp.c just adding a new if block: > static int > fxp_probe(device_t dev) > { > if ((pci_get_vendor(dev) == FXP_VENDORID_INTEL) && > (pci_get_device(dev) == FXP_DEVICEID_i82562)) { > device_set_desc(dev, "Intel 82562ET 10/100B Ethernet chip"); > return 0; > } snip ... > if ((pci_get_vendor(dev) == FXP_VENDORID_INTEL) && > (pci_get_device(dev) == FXP_DEVICEID_i82559)) { > device_set_desc(dev, "Intel InBusiness 10/100 Ethernet"); > return 0; > } and the following change in if_fxpreg.h : > #define FXP_DEVICEID_i82562 0x1132 /* New 82562ET device id.. */ Built a new kernel, installed and rebooted. fxp0 was detected, however when I did a "ifconfig fxp0 netmask " the system froze. I must admit that I`m not overly surprised that it did ... So, I hope this can be of help. I may have a look at the if_fxp code later this weekend, but I`m not very familiar with writing driver code so do not expect too much :-) --Stein Morten -- /* Stein M Sandbech Email: stein@ife.no ** ** Senior Systems Engineer, EDP dept Email: stein@www.ife.no ** ** Institute for Energy Technology Tel: +47 63 80 60 00 ** ** Box 40, N-2007 Kjeller, NORWAY Fax: +47 63 81 11 68 */ --------------8996D72DBAED94EF0F06B7EC Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Stefan Esser wrote:
On 2000-07-13 17:37 +0200, "Stein M. Sandbech" <stein@ife.no> wrote:
> Configuration:
> - D815EEA with;
>         * Intel 82562ET 10/100Mbit/sec (nic) component.
>         * Audio (Intel 82801BA+AD1885 analog codec, and Creative Labs
> ES1373 digital controller
>                            and the CS4297 Analog codec).
>         * Intel 82815E Graphics and Memory Controller Hub, the Graphics
> controller.

> The initial install went OK, and after the first reboot I noticed that
> it did not recognice a
> valid ethernet controller. I really expected it to see a  "fxp"  device,
> but no.

      snip ...
Can you check the output of "pciconf -l" for the Ethernet function ?
Perhaps it is sufficient to just enter the PCI ID into the list of
known IDs in the fxp driver ...
OK, see attached files.

I tested a small change to the  if_fxp.c  just adding a new  if block:

> static int
> fxp_probe(device_t dev)
> {
>       if ((pci_get_vendor(dev) == FXP_VENDORID_INTEL) &&
>           (pci_get_device(dev) == FXP_DEVICEID_i82562)) {
>               device_set_desc(dev, "Intel 82562ET 10/100B Ethernet chip");
>               return 0;
>       }

   snip ...

>       if ((pci_get_vendor(dev) == FXP_VENDORID_INTEL) &&
>           (pci_get_device(dev) == FXP_DEVICEID_i82559)) {
>               device_set_desc(dev, "Intel InBusiness 10/100 Ethernet");
>               return 0;
>       }

and the following change in  if_fxpreg.h :

> #define FXP_DEVICEID_i82562   0x1132  /* New 82562ET device id.. */

Built a new kernel, installed and rebooted. fxp0 was detected, however when
I did a "ifconfig fxp0 <ipaddr> netmask <netmask>" the system froze.

I must admit that I`m not overly surprised that it did ...

So, I hope this can be of help. I may have a look at the if_fxp code later this weekend,
but I`m not very familiar with writing driver code so do not expect too much :-)

--Stein Morten 

-- 
/*  Stein M Sandbech                   Email: stein@ife.no     **
**  Senior Systems Engineer, EDP dept  Email: stein@www.ife.no **
**  Institute for Energy Technology    Tel: +47 63 80 60 00    **
**  Box 40, N-2007 Kjeller, NORWAY     Fax: +47 63 81 11 68    */
  --------------8996D72DBAED94EF0F06B7EC-- --------------0B020E5659E904BD04F6346D Content-Type: text/plain; charset=us-ascii; name="pciconf-with-LAN-only.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pciconf-with-LAN-only.txt" chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x11308086 rev=0x02 hdr=0x00 none0@pci0:2:0: class=0x030000 card=0x45418086 chip=0x11328086 rev=0x02 hdr=0x00 pcib1@pci0:30:0: class=0x060400 card=0x00000000 chip=0x244e8086 rev=0x01 hdr=0x01 isab0@pci0:31:0: class=0x060100 card=0x00000000 chip=0x24408086 rev=0x01 hdr=0x00 atapci0@pci0:31:1: class=0x010180 card=0x45418086 chip=0x244b8086 rev=0x01 hdr=0x00 none1@pci0:31:2: class=0x0c0300 card=0x45418086 chip=0x24428086 rev=0x01 hdr=0x00 none2@pci0:31:3: class=0x0c0500 card=0x45418086 chip=0x24438086 rev=0x01 hdr=0x00 none3@pci0:31:4: class=0x0c0300 card=0x45418086 chip=0x24448086 rev=0x01 hdr=0x00 none4@pci1:8:0: class=0x020000 card=0x30138086 chip=0x24498086 rev=0x01 hdr=0x00 --------------0B020E5659E904BD04F6346D Content-Type: text/plain; charset=us-ascii; name="pciconf-with-all-idev.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pciconf-with-all-idev.txt" chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x11308086 rev=0x02 hdr=0x00 none0@pci0:2:0: class=0x030000 card=0x45418086 chip=0x11328086 rev=0x02 hdr=0x00 pcib1@pci0:30:0: class=0x060400 card=0x00000000 chip=0x244e8086 rev=0x01 hdr=0x01 isab0@pci0:31:0: class=0x060100 card=0x00000000 chip=0x24408086 rev=0x01 hdr=0x00 atapci0@pci0:31:1: class=0x010180 card=0x45418086 chip=0x244b8086 rev=0x01 hdr=0x00 none1@pci0:31:2: class=0x0c0300 card=0x45418086 chip=0x24428086 rev=0x01 hdr=0x00 none2@pci0:31:3: class=0x0c0500 card=0x45418086 chip=0x24438086 rev=0x01 hdr=0x00 none3@pci0:31:4: class=0x0c0300 card=0x45418086 chip=0x24448086 rev=0x01 hdr=0x00 none4@pci0:31:5: class=0x040100 card=0x45418086 chip=0x24458086 rev=0x01 hdr=0x00 none5@pci1:8:0: class=0x020000 card=0x30138086 chip=0x24498086 rev=0x01 hdr=0x00 --------------0B020E5659E904BD04F6346D Content-Type: text/plain; charset=us-ascii; name="messages" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="messages" This is the /var/log/messages when booting with all the integrated functions enabled in BIOS (on GENERIC kernel). Jul 14 16:28:02 /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Jul 14 16:28:02 /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 14 16:28:02 /kernel: The Regents of the University of California. All rights reserved. Jul 14 16:28:02 /kernel: FreeBSD 4.0-RELEASE #0: Mon Mar 20 22:50:22 GMT 2000 Jul 14 16:28:02 /kernel: root@monster.cdrom.com:/usr/src/sys/compile/GENERIC Jul 14 16:28:02 /kernel: Timecounter "i8254" frequency 1193182 Hz Jul 14 16:28:02 /kernel: CPU: Pentium III/Pentium III Xeon (730.97-MHz 686-class CPU) Jul 14 16:28:02 /kernel: Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Jul 14 16:28:02 /kernel: Features=0x383f9ff Jul 14 16:28:02 /kernel: real memory = 132907008 (129792K bytes) Jul 14 16:28:02 /kernel: avail memory = 124968960 (122040K bytes) Jul 14 16:28:02 /kernel: Preloaded elf kernel "kernel" at 0xc03c0000. Jul 14 16:28:02 /kernel: Pentium Pro MTRR support enabled Jul 14 16:28:02 /kernel: md0: Malloc disk Jul 14 16:28:02 /kernel: npx0: on motherboard Jul 14 16:28:02 /kernel: npx0: INT 16 interface Jul 14 16:28:02 /kernel: pcib0: on motherboard Jul 14 16:28:02 /kernel: pci0: on pcib0 Jul 14 16:28:02 /kernel: pci0: at 2.0 irq 11 Jul 14 16:28:02 /kernel: pcib1: at device 30.0 on pci0 Jul 14 16:28:02 /kernel: pci1: on pcib1 Jul 14 16:28:02 /kernel: pci1: (vendor=0x8086, dev=0x2449) at 8.0 irq 11 Jul 14 16:28:02 /kernel: isab0: at device 31.0 on pci0 Jul 14 16:28:02 /kernel: isa0: on isab0 Jul 14 16:28:02 /kernel: atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 Jul 14 16:28:02 /kernel: ata0: at 0x1f0 irq 14 on atapci0 Jul 14 16:28:02 /kernel: ata1: at 0x170 irq 15 on atapci0 Jul 14 16:28:02 /kernel: pci0: at 31.2 irq 11 Jul 14 16:28:02 /kernel: pci0: (vendor=0x8086, dev=0x2443) at 31.3 irq 9 Jul 14 16:28:02 /kernel: pci0: at 31.4 irq 10 Jul 14 16:28:02 /kernel: pci0: (vendor=0x8086, dev=0x2445) at 31.5 irq 9 Jul 14 16:28:02 /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Jul 14 16:28:02 /kernel: fdc0: FIFO enabled, 8 bytes threshold Jul 14 16:28:02 /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Jul 14 16:28:02 /kernel: atkbdc0: at port 0x60-0x6f on isa0 Jul 14 16:28:02 /kernel: atkbd0: irq 1 on atkbdc0 Jul 14 16:28:02 /kernel: psm0: irq 12 on atkbdc0 Jul 14 16:28:02 /kernel: psm0: model IntelliMouse, device ID 3 Jul 14 16:28:02 /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jul 14 16:28:02 /kernel: sc0: on isa0 Jul 14 16:28:02 /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Jul 14 16:28:02 /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Jul 14 16:28:02 /kernel: sio0: type 16550A Jul 14 16:28:02 /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Jul 14 16:28:02 /kernel: sio1: type 16550A Jul 14 16:28:02 /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Jul 14 16:28:02 /kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode Jul 14 16:28:02 /kernel: ppi0: on ppbus0 Jul 14 16:28:02 /kernel: lpt0: on ppbus0 Jul 14 16:28:02 /kernel: lpt0: Interrupt-driven port Jul 14 16:28:02 /kernel: plip0: on ppbus0 Jul 14 16:28:02 /kernel: ad0: 17206MB [34960/16/63] at ata0-master using BIOSDMA Jul 14 16:28:02 /kernel: acd0: CDROM at ata1-master using PIO4 Jul 14 16:28:02 /kernel: Mounting root from ufs:/dev/ad0s1a Jul 14 16:28:11 login: ROOT LOGIN (root) ON ttyv0 --------------0B020E5659E904BD04F6346D-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 14 9:15:24 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 4FD8A37C938 for ; Fri, 14 Jul 2000 09:15:17 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id JAA04151; Fri, 14 Jul 2000 09:23:40 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007141623.JAA04151@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: stein@ife.no Cc: freebsd-hardware@FreeBSD.org Subject: Re: Intel D815EEA. Testing FreeBSD 4.0 on, In-reply-to: Your message of "Fri, 14 Jul 2000 17:11:29 +0200." <396F2DA1.83BC5793@ife.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jul 2000 09:23:40 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > - D815EEA with; > > > * Intel 82562ET 10/100Mbit/sec (nic) component. > > > > > The initial install went OK, and after the first reboot I noticed that > > > it did not recognice a > > > valid ethernet controller. I really expected it to see a "fxp" device, > > > but no. > > snip ... > > > Can you check the output of "pciconf -l" for the Ethernet function ? > > Perhaps it is sufficient to just enter the PCI ID into the list of > > known IDs in the fxp driver ... > > OK, see attached files. > > I tested a small change to the if_fxp.c just adding a new if block: ... > > #define FXP_DEVICEID_i82562 0x1132 /* New 82562ET device id.. */ > > Built a new kernel, installed and rebooted. fxp0 was detected, however when > I did a "ifconfig fxp0 netmask " the system froze. Bill Paul and I went over the ICH2 datasheet yesterday, and it looks like the integrated network component is not an 8255x derivative. In fact, it looks a lot like the old 82586 architecture, even down to the 16-bit address registers. 8( Until we can extract some more data from Intel, this device is going to remain unsupported, I think. -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 14 10:47:38 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 6EC4437B95E for ; Fri, 14 Jul 2000 10:47:33 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id MAA04319; Fri, 14 Jul 2000 12:47:26 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 14 Jul 2000 12:47:25 -0500 (CDT) From: Chris Dillon To: Jose Gabriel Marcelino Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Gigabit recommendations 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 Fri, 14 Jul 2000, Jose Gabriel Marcelino wrote: > > Hi! > > > > Note I only mentioned 3Com here, these are the only ones I could get some > > > info on. I'd be very happy to know other good, trustworthy brands you are > > > using (I think Cisco may be very expensive but I haven't found the correct > > > model yet...) > > > > The 3COM switches are all over-priced CRAP. Go with Cisco or HP > > ProCurve, which should cost the same or less, respectively, and offer > > better performance and features. I'm speaking entirely from > > experience. :-) > > I was somewhat expecting that response on 3Com products :) > > I looked really well into HP and Cisco and I was very surprised to > find that the Cisco really is less expensive than 3Com here. I was very surprised that Cisco was the same or cheaper, too. That certainly wasn't the case in the past, but I guess Cisco has been enlightened by other, cheaper products that can do as well as they do. > The HP one looks nice too, I'm amazed to find a HP product that > looks good (and is recommended) after all the mess I've seen with > all the brain-damaged Jetdirect printer modules (the printers > themselves aren't too good either) and the brain-damaGING HP-UX > boxes I've unfortunately had to support :) Yes, we've got three HP ProCurve 4000M's, using only the 10/100 modules so far (no Gigabit yet), and I am very impressed with them. We have six 3COM SSII-3300 24-port switches and twelve SSII-1100 24+2 port switches. We also have two Cisco 2924-XL switches. I am most impressed by the management software on the Cisco switches. It is top-notch. The management software on the HP switches is second to the Cisco switches, but where the HP stuff excels the most is its reliability and expandability compared to the others (I know 3COM and Cisco have chassis-based switches too, but NOT in this price range). The HP 4000M is a 10-slot chassis with all modules hot-swappable and comes with five 8-port 10/100 modules (40 ports) for barely more or the same price as a 24-port 3COM SSII-3300. It also has the ability for two internal hot-swap power supplies (it comes with one). The 3COM are not (nearly as) expandable, the internal management console is slow, and the management features are sorely lacking. Probably the big reason for the console slowness is that the 3COM switches use a Motorola 68EC020 at 16MHz for a management processor, about equal to a Macintosh Classic. In contrast, the HP switches use a 66MHz Intel 960 and the Cisco switches use a PowerPC 403GA of at least 33MHz, but probably 50MHz or more (I haven't opened one up to look, yet). The 3COM console is so slow it is unbearable to use for extended configuration sessions, and there is no way to use a text configuration file and stick it on a server somewhere or replicate it to other switches like you can with the HP or Cisco switches. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 14 12:10:25 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 32CED37B6B1 for ; Fri, 14 Jul 2000 12:10:21 -0700 (PDT) (envelope-from brandon@schoolpeople.net) Received: from triangulata (cs2887-130.austin.rr.com [24.28.87.130]) by gabriel.schoolpeople.net (8.9.3/8.9.3) with SMTP id OAA75331; Fri, 14 Jul 2000 14:10:06 -0500 (CDT) (envelope-from brandon@schoolpeople.net) Message-ID: <001601bfedc7$ba2c3f40$82571c18@austin.rr.com> From: "Brandon S. DeYoung" To: "Jose Gabriel Marcelino" Cc: References: Subject: Re: Gigabit recommendations Date: Fri, 14 Jul 2000 14:14:24 -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.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Something worth taking a look at for a switch is the Dlink 5600: http://www.dlink.com/products/switches/des5600/ I've got one of these, it works like a charm and is a whole lot cheaper than anything even remotely comparable from Cisco or 3Com. ~Brandon ----- Original Message ----- From: "Jose Gabriel Marcelino" To: "Chris Dillon" Cc: Sent: Friday, July 14, 2000 6:31 AM Subject: Re: Gigabit recommendations > > Hi! > > > > Note I only mentioned 3Com here, these are the only ones I could get some > > > info on. I'd be very happy to know other good, trustworthy brands you are > > > using (I think Cisco may be very expensive but I haven't found the correct > > > model yet...) > > > > The 3COM switches are all over-priced CRAP. Go with Cisco or HP > > ProCurve, which should cost the same or less, respectively, and offer > > better performance and features. I'm speaking entirely from > > experience. :-) > > I was somewhat expecting that response on 3Com products :) > > I looked really well into HP and Cisco and I was very surprised to find > that the Cisco really is less expensive than 3Com here. > > The HP one looks nice too, I'm amazed to find a HP product that looks good > (and is recommended) after all the mess I've seen with all the > brain-damaged Jetdirect printer modules (the printers themselves aren't > too good either) and the brain-damaGING HP-UX boxes I've unfortunately had > to support :) > > Thanks a lot for your advice! > > Regards > > Gabriel > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 14 12:27:38 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from sn1oexchr01.nextvenue.com (sn1oexchr01.nextvenue.com [63.209.169.9]) by hub.freebsd.org (Postfix) with SMTP id 9403737C6CE for ; Fri, 14 Jul 2000 12:27:31 -0700 (PDT) (envelope-from nevans@nextvenue.com) Received: FROM sn1exchmbx.nextvenue.com BY sn1oexchr01.nextvenue.com ; Fri Jul 14 15:25:45 2000 -0400 Received: by sn1exchmbx.nextvenue.com with Internet Mail Service (5.5.2650.21) id <34BTY6G3>; Fri, 14 Jul 2000 15:23:10 -0400 Message-ID: <712384017032D411AD7B0001023D799B07C9D1@sn1exchmbx.nextvenue.com> From: Nick Evans To: 'Jose Gabriel Marcelino' , freebsd-hardware@freebsd.org Subject: RE: Gigabit recommendations Date: Fri, 14 Jul 2000 15:23:02 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFEDC8.EDCF2140" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. ------_=_NextPart_001_01BFEDC8.EDCF2140 Content-Type: text/plain; charset="iso-8859-1" Extreme Networks www.extremenetworks.com. They make some pretty damn quick switches, and their prices are not bad. They also have a simple interface, much easier to use than IOS, and more flexible. nick -----Original Message----- From: Jose Gabriel Marcelino [mailto:gabriel@maquina.com] Sent: Thursday, July 13, 2000 7:28 PM To: freebsd-hardware@freebsd.org Subject: Gigabit recommendations Hi, I'm preparing for a Gigabit setup here for a couple of FreeBSD and some Linux boxes. This will actaully be a Gigabit backbone to connect 4 switches over fiber, 1000Base-SX (Yes I know about the 220m limitation over my multimode fiber) I wonder if anyone could give me some recommendations. : I've already read enough about the network cards from the previous posts and it seems SysKonnect are the best, but I may have to go to the 3Com 3c985b Tigon II based cards due to local availability. My main doubt in on the switch side, I'm tempted to go for the 3Com SuperStack II 3900 which I can get for around US$2.400 here for the 24 port version. The 3800 is also tempting with it's layer 3 switching but at US$6.330 a piece it's a bit of overkill and overbudget for my company. Note I only mentioned 3Com here, these are the only ones I could get some info on. I'd be very happy to know other good, trustworthy brands you are using (I think Cisco may be very expensive but I haven't found the correct model yet...) Thanks for all the help. Regards Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message ------_=_NextPart_001_01BFEDC8.EDCF2140 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Gigabit recommendations

Extreme Networks www.extremenetworks.com. They make = some pretty damn quick switches, and their prices are not bad. They = also have a simple interface, much easier to use than IOS, and more = flexible.

nick

-----Original Message-----
From: Jose Gabriel Marcelino [mailto:gabriel@maquina.com]
Sent: Thursday, July 13, 2000 7:28 PM
To: freebsd-hardware@freebsd.org
Subject: Gigabit recommendations



Hi,

I'm preparing for a Gigabit setup here for a couple = of FreeBSD and some
Linux boxes.  This will actaully be a Gigabit = backbone to connect 4
switches over fiber, 1000Base-SX (Yes I know about = the 220m limitation
over my multimode fiber)

I wonder if anyone could give me some = recommendations.  :

I've already read enough about the network cards from = the previous posts
and it seems SysKonnect are the best, but I may have = to go to the 3Com
3c985b Tigon II based cards due to local = availability.

My main doubt in on the switch side, I'm tempted to = go for the 3Com
SuperStack II 3900 which I can get for around = US$2.400 here for the 24
port version.

The 3800 is also tempting with it's layer 3 switching = but at US$6.330 a
piece it's a bit of overkill and overbudget for my = company.

Note I only mentioned 3Com here, these are the only = ones I could get some
info on. I'd be very happy to know other good, = trustworthy brands you are
using (I think Cisco may be very expensive but I = haven't found the correct
model yet...)

Thanks for all the help.

Regards

Gabriel




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

------_=_NextPart_001_01BFEDC8.EDCF2140-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 14 23:15:41 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.prod.itd.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 8230A37B5CF; Fri, 14 Jul 2000 23:15:37 -0700 (PDT) (envelope-from dmehler22@earthlink.net) Received: from hellraiser (ip103.dayton5.oh.pub-ip.psi.net [38.27.181.103]) by gull.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with SMTP id XAA11098; Fri, 14 Jul 2000 23:15:35 -0700 (PDT) Message-ID: <000d01bfeeee$4e830620$0200a8c0@hellraiser> Reply-To: "dave" From: "dave" To: Cc: Subject: usr3030 modem? Date: Sun, 16 Jul 2000 02:23:05 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BFEECC.C6094AA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BFEECC.C6094AA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, Does anyone have a usr 3030 modem, it's an isa modem, 56k data/fax = modem? It has the identifier usr30307256 and it is listed in the sio.c = file of fbsd 4.0. I'm trying to get mine working and em encountering no = success. If anyone has this particular modem please e-mail me. Thank you. Dave. ------=_NextPart_000_0005_01BFEECC.C6094AA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
    Does anyone have a = usr 3030=20 modem, it's an isa modem, 56k data/fax modem? It has the identifier = usr30307256=20 and it is listed in the sio.c file of fbsd 4.0. I'm trying to get mine = working=20 and em encountering no success. If anyone has this particular modem = please=20 e-mail me.
Thank you.
Dave.
 
------=_NextPart_000_0005_01BFEECC.C6094AA0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jul 15 3:30:27 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from elit.ci.net.ua (elit.ci.net.ua [212.86.96.11]) by hub.freebsd.org (Postfix) with ESMTP id 4E93A37BD0F; Sat, 15 Jul 2000 03:30:18 -0700 (PDT) (envelope-from acid@ci.net.ua) Received: from localhost (acid@localhost) by elit.ci.net.ua (8.9.3/Who was second?) with ESMTP id NAA34020; Sat, 15 Jul 2000 13:30:14 +0300 (EEST) Date: Sat, 15 Jul 2000 13:30:14 +0300 (EEST) From: "Michael I. Vasilenko" To: freesbd-questions@freebsd.org Subject: Is it possible to port DVB drivers from Linux? 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 Hello ! I'm HIGHLY interested in developing driver for DVB card, such as SkyStar1. There are free drivers for linux, which is available on http://www.linuxtv.org/dvb Is it possible to port it to FreeBSD ? Or they are highly integrated into Linux kernel (things, like i2c and video, for example) In other words, from what should I start ? ANY feedback would be fine please, CC: me, I'm off the list -- Michael Vasilenko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jul 15 23:19:25 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from hawk.prod.itd.earthlink.net (hawk.prod.itd.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 6775937B5A7; Sat, 15 Jul 2000 23:19:03 -0700 (PDT) (envelope-from dmehler22@earthlink.net) Received: from hellraiser (ip25.dayton5.oh.pub-ip.psi.net [38.27.181.25]) by hawk.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with SMTP id XAA06621; Sat, 15 Jul 2000 23:19:01 -0700 (PDT) Message-ID: <000801bfefb7$f1eda440$0200a8c0@hellraiser> Reply-To: "dave" From: "dave" To: Cc: Subject: generalized instructions for pnp modem configuration. Date: Mon, 17 Jul 2000 02:26:28 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BFEF96.696AC100" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BFEF96.696AC100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, If anyone is using a pnp modem of any type under fbsd 4.0-release = could you let me know step by step what you had to do to get it working, = with ppp, what you had to change in your kernel or add to = kernel.conf/sio.c anything? I'm still having difficulties getting mine = to work. Help appreciated. Thanks. Dave. ------=_NextPart_000_0005_01BFEF96.696AC100 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
    If anyone is using a = pnp modem=20 of any type under fbsd 4.0-release could you let me know step by step = what you=20 had to do to get it working, with ppp, what you had to change in your = kernel or=20 add to kernel.conf/sio.c anything? I'm still having difficulties getting = mine to=20 work.
    Help = appreciated.
Thanks.
Dave.
 
------=_NextPart_000_0005_01BFEF96.696AC100-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message