From owner-freebsd-hardware Sun Jan 30 8:29:36 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 4F2C414DC9; Sun, 30 Jan 2000 08:29:06 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id QAA05771; Sun, 30 Jan 2000 16:21:30 GMT (envelope-from n_hibma@webweaving.org) Date: Sun, 30 Jan 2000 16:21:29 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Donald Burr Cc: freebsd-net@FreeBSD.ORG, FreeBSD Hardware Subject: Re: Drivers for Davicom DM9102 10/100 NIC chip 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 If this is one of those USB only (USB keyboard, mouse, etc.) thingies you might want to be careful. I have not yet tried that and so far the only report I've had was that it did not work on an Acer. 1) there is a problem with ISA not being there I expect 2) Is the USB support amture enough to keep you going. Could you specify a location where one can find more information on this device? Cheers, Nick On Sat, 29 Jan 2000, Donald Burr wrote: > One of my suppliers has just started carrying a new item, called the > "BookPC", a really nice fully integrated PC (built in AGP video, USB, > 10/100 NIC, 56K modem, and AC97 audio) in an extremely small case > (even smaller than MicroATX). I'd like to buy a couple of these and turn > them into "tiny FreeBSD workstations". unfortunately, they use an > ethernet controller that is not supported. It is the Davicom DM9102 > (http://www.davicom8.com/lan/dm9102.htm). Fortunately it looks like this > company is pretty open-source friendly, there is a datasheet that you can > get right off the Web site, and there is even *source* for a Linux driver > (also available on the web site). > > It would be great if this chip were supported under > FreeBSD. Unfortunately, I lack the necessary mojo to pull this off. > > Any takers? Many thanks in advance! > -- > Donald Burr Resistance is Futile | FreeBSD: The > WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to > Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | Serve! http:// > Phone: (805) 957-9666 FAX: (800) 492-5954 | www.freebsd.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jan 30 14:28: 7 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from borg-cube.com (226-193.adsl2.avtel.net [207.71.226.193]) by hub.freebsd.org (Postfix) with ESMTP id 68EC214E0D; Sun, 30 Jan 2000 14:28:02 -0800 (PST) (envelope-from dburr@borg-cube.com) Received: from hugh.collective.borg-cube.com (IDENT:dburr@hugh.collective.borg-cube.com [192.168.0.6]) by borg-cube.com (8.9.3/8.9.3) with ESMTP id OAA09673; Sun, 30 Jan 2000 14:27:58 -0800 (PST) (envelope-from dburr@borg-cube.com) Date: Sun, 30 Jan 2000 06:28:38 -0800 (PST) From: Donald Burr To: Nick Hibma Cc: freebsd-net@FreeBSD.ORG, FreeBSD Hardware Subject: Re: Drivers for Davicom DM9102 10/100 NIC chip In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 30 Jan 2000, Nick Hibma wrote: NH>If this is one of those USB only (USB keyboard, mouse, etc.) thingies NH>you might want to be careful. I have not yet tried that and so far the NH>only report I've had was that it did not work on an Acer. No, it has a PS/2 mouse and keyboard port. NH>1) there is a problem with ISA not being there I expect NH>2) Is the USB support amture enough to keep you going. NH>Could you specify a location where one can find more information on this NH>device? It is an extremely small (12"x11"x3.5") completely self contained PC. intel 810 chipset motherboard, socket 370 (celeron CPU), 2 x DIMM slots, room for a CD-ROM, hard drive, and floppy drive. No slots (everything is built in). 56K modem, 10/100 ethernet, USB, PS/2 mouse and keyboard, printer port, built in video, built in PCI AC97 sound card. I figure a stack of these will make a nice little FreeBSD cluster. Here are a couple of websites where you can see pictures of them, get more information, etc.: http://www.eastoncomputerworks.com/ecw/bookpc.htm http://www.arnoldco.com/bookpc/bookpc.html and here are some pictures of me assembling mine (I bought a "bare bones" unit without memory, CPU, or hard drive, since I have some spare components lying around) http://www.borg-cube.com/pix/hugh/ -- Donald Burr Resistance is Futile | FreeBSD: The WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | Serve! http:// Phone: (805) 957-9666 FAX: (800) 492-5954 | 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 Sun Jan 30 15:33:19 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 3D4A714FFB; Sun, 30 Jan 2000 15:33:13 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id RAA22043; Sun, 30 Jan 2000 17:32:55 -0600 (CST) Date: Sun, 30 Jan 2000 17:32:54 -0600 From: Tim Tsai To: Donald Burr Cc: Nick Hibma , freebsd-net@FreeBSD.ORG, FreeBSD Hardware Subject: Re: Drivers for Davicom DM9102 10/100 NIC chip Message-ID: <20000130173254.A21957@futuresouth.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We've used one of these for awhile (I brought one back from Taiwan a few months ago). It makes a nice compact size workstation but the TV output is really pretty crappy. I wouldn't get it to connect to the TV. Tim On Sun, Jan 30, 2000 at 06:28:38AM -0800, Donald Burr wrote: > On Sun, 30 Jan 2000, Nick Hibma wrote: > > NH>If this is one of those USB only (USB keyboard, mouse, etc.) thingies > NH>you might want to be careful. I have not yet tried that and so far the > NH>only report I've had was that it did not work on an Acer. > > No, it has a PS/2 mouse and keyboard port. > > NH>1) there is a problem with ISA not being there I expect > NH>2) Is the USB support amture enough to keep you going. > NH>Could you specify a location where one can find more information on this > NH>device? > > It is an extremely small (12"x11"x3.5") completely self contained PC. > intel 810 chipset motherboard, socket 370 (celeron CPU), 2 x DIMM slots, > room for a CD-ROM, hard drive, and floppy drive. No slots (everything is > built in). 56K modem, 10/100 ethernet, USB, PS/2 mouse and keyboard, > printer port, built in video, built in PCI AC97 sound card. I figure a > stack of these will make a nice little FreeBSD cluster. > > Here are a couple of websites where you can see pictures of them, get more > information, etc.: > > http://www.eastoncomputerworks.com/ecw/bookpc.htm > http://www.arnoldco.com/bookpc/bookpc.html > > and here are some pictures of me assembling mine (I bought a "bare bones" > unit without memory, CPU, or hard drive, since I have some spare > components lying around) > > http://www.borg-cube.com/pix/hugh/ > -- > Donald Burr Resistance is Futile | FreeBSD: The > WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to > Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | Serve! http:// > Phone: (805) 957-9666 FAX: (800) 492-5954 | www.freebsd.org > > > > 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 Sun Jan 30 20:33:44 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (Postfix) with ESMTP id C254914E3D for ; Sun, 30 Jan 2000 20:33:34 -0800 (PST) (envelope-from jonny@coe.ufrj.br) Received: (from uucp@localhost) by roma.coe.ufrj.br (8.9.3/8.9.3) id CAA16029 for ; Mon, 31 Jan 2000 02:33:32 -0200 (EDT) (envelope-from jonny@coe.ufrj.br) Received: from localhost.coe.ufrj.br(127.0.0.1), claiming to be "coe.ufrj.br" via SMTP by localhost.coe.ufrj.br, id smtpdF16025; Mon Jan 31 02:33:24 2000 Message-ID: <3895108E.4355268B@coe.ufrj.br> Date: Mon, 31 Jan 2000 02:33:19 -0200 From: =?iso-8859-1?Q?Jo=E3o?= Carlos Mendes =?iso-8859-1?Q?Lu=EDs?= X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: hardware@freebsd.org Subject: Disable DMA in only one disk, with ata driver Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a setup with FreeBSD current and 3 IDE drives (Western Digital). One of them does not work well with DMA, and I'd like to disable DMA for it, but keep it enabled for the others. How can I do that, using the new ata driver? Would it be interesting to have flag options disk by disk specifying which PIO/DMA mode to run? Is it difficult to implement? Something like: 0x0007 - Mask for the higher mode 0x0008 - PIO/DMA 0x0010 - Limit mode Example: flags 0x0012 -> limit to PIO mode 2 flags 0x0019 -> limit to DMA mode 1 Thanks in advance, Jonny PS: Is this the best list for this discussion? -- João Carlos Mendes Luís jonny@jonny.eng.br Networking Engineer jcml@ieee.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jan 30 20:41: 0 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from biff.nerdpower.net (c13574-005.nerdpower.net [24.108.80.110]) by hub.freebsd.org (Postfix) with SMTP id 66BF314E93 for ; Sun, 30 Jan 2000 20:40:46 -0800 (PST) (envelope-from jeff@nerdpower.com) Received: (qmail 685 invoked by alias); 31 Jan 2000 04:42:08 -0000 Received: from flanders.nerdpower.net (HELO flanders) (24.108.80.209) by biff.nerdpower.net with SMTP; 31 Jan 2000 04:42:08 -0000 From: "Jeff Lush" To: Cc: Subject: FW: Help with a bad hard disk Date: Sun, 30 Jan 2000 21:42:43 -0700 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.2314.1300 Importance: Normal Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I'm hoping someone can offer some assistance with a bad IDE disk running FreeBSD 3.4. The disk is a Western Digital Caviar 1.6 GB and is the secondary drive on a PPro 200. The machine was accidently and suddenly powered off and now whenever the machine boots, the kernel stops and I need to run fsck manually, when I run fsck manually, it says: w1s1e: hard error reading fsbn3016199 of 3016176-3016287 (w1s1 bn 3016199; cn 748 to 4 sn 11) (status59(rdy,seekdone,drg,err) error 40) /dev/rwd1s1e: CANNOT READ: BLK 3016176 I have run the diagnostic software from Western Digital and it says to return the drive for warranty, but I was hoping someone might know of a trick or have some advice on how to make her work or at least pull the data off. If there is anymore info I can provide, please let me know. Thanks for the help, Jeff Lush To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Feb 1 0:55:32 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from pinky.us.net (pinky.us.net [198.240.73.64]) by builder.freebsd.org (Postfix) with ESMTP id B34A33D76; Tue, 1 Feb 2000 00:55:16 -0800 (PST) Received: (from sillybug@localhost) by pinky.us.net (8.9.3/8.9.3) id CAA02480; Tue, 1 Feb 2000 02:45:36 -0500 (EST) (envelope-from sillybug) From: Brian Skrab Message-Id: <200002010745.CAA02480@pinky.us.net> Subject: DVD Drive support on FreeBSD ? To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Date: Tue, 1 Feb 2000 02:45:35 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm looking into the possibility of purchasing a DVD drive for the home and am wondering if it'd be possible to place it on the FreeBSD server. Does anyone know of any DVD drive that is supported on FreeBSD 3.4+? Thanks, ~Brian Skrab sillybug@pinky.us.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Feb 1 1:10:47 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by builder.freebsd.org (Postfix) with ESMTP id 782EA3D53; Tue, 1 Feb 2000 01:10:36 -0800 (PST) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id LAA16504; Tue, 1 Feb 2000 11:08:59 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <200002010908.LAA16504@oskar.dev.nanoteq.co.za> Subject: Re: DVD Drive support on FreeBSD ? In-Reply-To: <200002010745.CAA02480@pinky.us.net> from Brian Skrab at "Feb 1, 2000 2:45:35 am" To: sillybug@pinky.us.net (Brian Skrab) Date: Tue, 1 Feb 2000 11:08:59 +0200 (SAT) Cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As far as I know ... most DVD drives are ATAPI standard .. so anyone should work ... although I think only -current has the DVD-ioctls implemented. I'm not sure if it is in -stable. I have a DVS 600 (6x DVD, 40X CD) DVD-ROM and it work perfectly under 4.0-current (Jan 10) Reinier > Hello, > > I'm looking into the possibility of purchasing a DVD drive for the > home and am wondering if it'd be possible to place it on the FreeBSD > server. Does anyone know of any DVD drive that is supported on > FreeBSD 3.4+? > > Thanks, > > ~Brian Skrab > sillybug@pinky.us.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 Feb 1 2: 4:42 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from www.quakeclan.net (www.quakeclan.net [24.237.0.24]) by builder.freebsd.org (Postfix) with SMTP id D1A033D8A; Tue, 1 Feb 2000 02:04:37 -0800 (PST) Received: from hades.ctnet.org.au (unverified [139.134.150.135]) by www.quakeclan.net (EMWAC SMTPRS 0.83) with SMTP id ; Tue, 01 Feb 2000 01:10:14 -0900 From: Shaun Dwyer Reply-To: zeus@quakeclan.net To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Aureal Vortex soundcard under FreeBSD Date: Tue, 1 Feb 2000 18:01:49 +0800 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00020118080600.99901@hades.ctnet.org.au> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I noticed that linux drivers are available for the vortex1/2/advantage chipsets are available at http://linux.aureal.com. They are (amazing but true) source!! I'm sure this will help who ever is writing the FreeBSD driver. I've seen Doug White's response to the availability of a vortex driver. However, it didn't give any details. My question is when will a driver be available. As I am not subscribed to the mailing lists, please e-mail me directly. Thanks, Shaun ---------------------- Shaun Dwyer Zeus@quakeclan.net ---------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Feb 1 2:28: 5 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by builder.freebsd.org (Postfix) with ESMTP id EB5483D9B for ; Tue, 1 Feb 2000 02:28:03 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #35196) with ESMTP id <01JLE3XLS5Q6000LNQ@research.kpn.com> for freebsd-hardware@freebsd.org; Tue, 1 Feb 2000 11:27:52 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Tue, 01 Feb 2000 11:27:51 +0100 Content-return: allowed Date: Tue, 01 Feb 2000 11:27:48 +0100 From: "Koster, K.J." Subject: To: 'FreeBSD Hardware mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522013137B9@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear FreeBSD-hardware, Does FreeBSD have support for the ServerSitter card? http://www.serversitter.com/ Kees Jan PS. Sorry, I could not resist. ============================================== You are only young once, but you can stay immature all your life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Feb 2 9:13:28 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from engine2.dhivehinet.net.mv (engine2.dhivehinet.net.mv [202.1.192.211]) by builder.freebsd.org (Postfix) with ESMTP id 301A140B4 for ; Wed, 2 Feb 2000 09:13:20 -0800 (PST) Received: from summoner ([202.1.193.113]) by engine2.dhivehinet.net.mv (Post.Office MTA v3.5.3 release 223 ID# 0-58493U3000L300S0V35) with SMTP id mv for ; Wed, 2 Feb 2000 22:09:10 +0500 Message-ID: <000201bf6d9f$efeede60$71c101ca@summoner> From: "Haikal Saadh" To: Subject: Choice of display cards under freebsd. Date: Wed, 2 Feb 2000 15:29: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.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm planning to upgrade my box within a few months, and I was just wondering: As far as running games (such as halflife) under freebsd are concerned, does it make sense to by a D3D-based card, such as nVidia's card, as D3D only works under windows, right? Or to rephrase the question, which one would provide the better 3D experience? The geForce or the Voodoo3? I know that the latest version of X supports both cards. I'm looking at getting the stuff in time for 4.0 to be released. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Feb 2 15:56:52 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by builder.freebsd.org (Postfix) with ESMTP id 7D91C41F8 for ; Wed, 2 Feb 2000 15:56:47 -0800 (PST) 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 RAA33755; Wed, 2 Feb 2000 17:56:46 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 2 Feb 2000 17:56:46 -0600 (CST) From: Chris Dillon To: Haikal Saadh Cc: hardware@FreeBSD.ORG Subject: Re: Choice of display cards under freebsd. In-Reply-To: <000201bf6d9f$efeede60$71c101ca@summoner> 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 Wed, 2 Feb 2000, Haikal Saadh wrote: > Hi, I'm planning to upgrade my box within a few months, and I was > just wondering: As far as running games (such as halflife) under > freebsd are concerned, does it make sense to by a D3D-based card, > such as nVidia's card, as D3D only works under windows, right? > > Or to rephrase the question, which one would provide the better 3D > experience? The geForce or the Voodoo3? I know that the latest > version of X supports both cards. > > I'm looking at getting the stuff in time for 4.0 to be released. I would avoid any of the 3DFX VooDoo cards. I've got an "old" VooDoo2 myself, and it works pretty well (in Windows), but it has some serious limitations. The VooDoo3 boards have some limitations as well, such as only a 16-bit Z-buffer and color depth in 3D mode as opposed to 32-bit which is available on just about any other modern card. Not even the new VooDoo4 or VooDoo5 boards are going to be able to compete with NVidia's next-generation chipset (which should be out about the same time as the VooDoo[4,5]) in terms of pure speed. They may not even be able to compete with the current GeForce 256! Long-gone are the days of 3DFX leading the speed arena like they did with the VooDoo2, and they aren't likely to ever do it again at this rate. If I were to buy a card right now, it would be either a NVidia GeForce 256 based card (probably the ASUS model), or a Matrox G400 MAX. The GeForce based cards will offer you pure, unparalleled 3D speed. The Matrox G400 MAX would offer you what Matrox has always offered -- excellent visual quality, great features, and solid drivers, but it isn't nearly as fast as the GeForce in the 3D arena (not that you couldn't play a mean game of Quake with it.. you can). Your biggest concern is which of these will be supported the best under XFree86, and as far as I can tell they've all got quite a bit of support under 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 Thu Feb 3 3:13:38 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by builder.freebsd.org (Postfix) with ESMTP id 4BCE04337 for ; Thu, 3 Feb 2000 03:13:31 -0800 (PST) Received: by ren.detir.qld.gov.au; id VAA23208; Thu, 3 Feb 2000 21:12:46 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpdb23202; Thu Feb 3 21:12:43 2000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id VAA09251; Thu, 3 Feb 2000 21:12:31 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id VAA14422; Thu, 3 Feb 2000 21:12:31 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id VAA91854; Thu, 3 Feb 2000 21:12:30 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <200002031112.VAA91854@nymph.detir.qld.gov.au> To: Chris Dillon Cc: freebsd-hardware@freebsd.org, Haikal Saadh , syssgm@detir.qld.gov.au Subject: Re: Choice of display cards under freebsd. References: <000201bf6d9f$efeede60$71c101ca@summoner> In-Reply-To: from Chris Dillon at "Wed, 02 Feb 2000 17:56:46 -0600" Date: Thu, 03 Feb 2000 21:12:29 +1000 From: Stephen McKay Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 2nd February 2000, Chris Dillon wrote: >On Wed, 2 Feb 2000, Haikal Saadh wrote: > >> Hi, I'm planning to upgrade my box within a few months, and I was >> just wondering: As far as running games (such as halflife) under >> freebsd are concerned, does it make sense to by a D3D-based card, >> such as nVidia's card, as D3D only works under windows, right? Direct3D is available only for Windoze, and not even all versions of Windoze. OpenGL is available on a number of platforms. nVidia's cards do not support only D3D. Their OpenGL support (for Windoze) works fine for games. Eventually, OpenGL support in XFree86 (and hence Linux and FreeBSD) will be good, and I expect that support for nVidia, 3dfx and Matrox cards will be good. But not yet... >> Or to rephrase the question, which one would provide the better 3D >> experience? The geForce or the Voodoo3? I know that the latest >> version of X supports both cards. >I would avoid any of the 3DFX VooDoo cards. I've got an "old" VooDoo2 >myself, and it works pretty well (in Windows), but it has some serious >limitations. The VooDoo3 boards have some limitations as well, such >as only a 16-bit Z-buffer and color depth in 3D mode as opposed to >32-bit which is available on just about any other modern card. For most purposes 32 bit colour is too slow, and almost impossible to pick visually. If you restrict yourself to 16 bit colour, then the Voodoo 3 is the current speed leader in recent games (Quake 3, Unreal Tournament) under most circumstances. For UT in particular, 3dfx cards work exceptionally well, due to Glide support, and are visually superior to other cards. For Q3A, you have to take a visual detail hit because of the limited maximum texture size. >If I were to buy a card right now, it would be either a NVidia GeForce >256 based card (probably the ASUS model), or a Matrox G400 MAX. The >GeForce based cards will offer you pure, unparalleled 3D speed. The >Matrox G400 MAX would offer you what Matrox has always offered -- >excellent visual quality, great features, and solid drivers, but it >isn't nearly as fast as the GeForce in the 3D arena (not that you >couldn't play a mean game of Quake with it.. you can). Your biggest >concern is which of these will be supported the best under XFree86, >and as far as I can tell they've all got quite a bit of support under >them. I recommend a cheap Voodoo2, to be honest. You don't need proper support in XFree86 to drive a Voodoo2, unlike any other card. When full OpenGL support arrives for XFree86, I'd recommend the Matrox G400 for the visual quality. Until then, the Voodoo2 is a reasonable workaround. I'd also disagree about "solid drivers" from Matrox. I've installed many of their unreliable OpenGL driver revisions. Then I bought a TNT2. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 3 5:22:13 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ockle.dev.nanoteq.co.za (ockle.dev.nanoteq.co.za [196.7.114.28]) by builder.freebsd.org (Postfix) with ESMTP id B58B343A7 for ; Thu, 3 Feb 2000 05:22:04 -0800 (PST) Received: by ockle.dev.nanoteq.co.za (8.9.3/8.9.3) id PAA13168 for freebsd-hardware@freebsd.org; Thu, 3 Feb 2000 15:21:15 +0200 (SAST) (envelope-from johan) From: Johan Kruger Reply-To: jkruger@oskar.nanoteq.co.za Organization: Nanoteq To: freebsd-hardware@freebsd.org Subject: PCMCIA card driver Date: Thu, 3 Feb 2000 15:20:48 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00020315195605.12823@ockle.dev.nanoteq.co.za> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hope this is the correct mailing list. I want to write a driver for a PCMCIA Cyptomodule card. Do someone know where i can find an example driver source code for a PCMCIA card It would be nice if the example was a KLD module as well. -- Johan Kruger ( B.Ing Electronic Engineering ) Developement Engineer Nanoteq PTA ( 012 6727000 ) e-mail : jkruger@oskar.nanoteq.co.za e-mail : jk@nanoteq.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 3 5:22:34 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ockle.dev.nanoteq.co.za (ockle.dev.nanoteq.co.za [196.7.114.28]) by builder.freebsd.org (Postfix) with ESMTP id 60E824333 for ; Thu, 3 Feb 2000 05:22:04 -0800 (PST) Received: by ockle.dev.nanoteq.co.za (8.9.3/8.9.3) id PAA13171 for freebsd-hardware@freebsd.org; Thu, 3 Feb 2000 15:21:16 +0200 (SAST) (envelope-from johan) From: Johan Kruger Reply-To: jkruger@oskar.nanoteq.co.za Organization: Nanoteq To: freebsd-hardware@freebsd.org Subject: PCMCIA card driver Date: Thu, 3 Feb 2000 15:21:12 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00020315195605.12823@ockle.dev.nanoteq.co.za> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hope this is the correct mailing list. I want to write a driver for a PCMCIA Cyptomodule card. Do someone know where i can find an example driver source code for a PCMCIA card It would be nice if the example was a KLD module as well. -- Johan Kruger ( B.Ing Electronic Engineering ) Developement Engineer Nanoteq PTA ( 012 6727000 ) e-mail : jkruger@oskar.nanoteq.co.za e-mail : jk@nanoteq.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 3 7:47:29 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by builder.freebsd.org (Postfix) with ESMTP id 62E5C3E82 for ; Thu, 3 Feb 2000 07:47:23 -0800 (PST) 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 JAA39023; Thu, 3 Feb 2000 09:47:24 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 3 Feb 2000 09:47:24 -0600 (CST) From: Chris Dillon To: Stephen McKay Cc: freebsd-hardware@freebsd.org, Haikal Saadh Subject: Re: Choice of display cards under freebsd. In-Reply-To: <200002031112.VAA91854@nymph.detir.qld.gov.au> 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 Thu, 3 Feb 2000, Stephen McKay wrote: > On Wednesday, 2nd February 2000, Chris Dillon wrote: [...snip...] > >I would avoid any of the 3DFX VooDoo cards. I've got an "old" VooDoo2 > >myself, and it works pretty well (in Windows), but it has some serious > >limitations. The VooDoo3 boards have some limitations as well, such > >as only a 16-bit Z-buffer and color depth in 3D mode as opposed to > >32-bit which is available on just about any other modern card. > > For most purposes 32 bit colour is too slow, and almost impossible to > pick visually. If you restrict yourself to 16 bit colour, then the > Voodoo 3 is the current speed leader in recent games (Quake 3, Unreal > Tournament) under most circumstances. For UT in particular, 3dfx cards > work exceptionally well, due to Glide support, and are visually superior > to other cards. For Q3A, you have to take a visual detail hit because > of the limited maximum texture size. My point was more that the 3DFX cards can't even do what their peers can, which is 32-bit color-depth and Z-buffering. It is true that those only help with visual quality and not speed, but if visual quality is your thing, you definately want it. The 32-bit Z-buffering matters more than the color-depth because it helps prevent odd clipping problems, which is far far worse visually than only seeing thousands of colors instead of millions. I see these kinds of things all the time using my VooDoo2. It can be very distracting and annoying, especially if you're playing a deathmatch with someone and all of a sudden you see some clipping "noise" out of the corner of your eye and think it is your enemy coming after you. :-) If you take the Matrox G400 MAX as an example, it performs nearly as well in 32-bit modes as it does in 16-bit, so 32-bit doesn't have to mean a significant performance hit when your hardware is designed correctly (plenty of memory bandwidth). > >If I were to buy a card right now, it would be either a NVidia GeForce > >256 based card (probably the ASUS model), or a Matrox G400 MAX. The > >GeForce based cards will offer you pure, unparalleled 3D speed. The > >Matrox G400 MAX would offer you what Matrox has always offered -- > >excellent visual quality, great features, and solid drivers, but it > >isn't nearly as fast as the GeForce in the 3D arena (not that you > >couldn't play a mean game of Quake with it.. you can). Your biggest > >concern is which of these will be supported the best under XFree86, > >and as far as I can tell they've all got quite a bit of support under > >them. > > I recommend a cheap Voodoo2, to be honest. You don't need proper support > in XFree86 to drive a Voodoo2, unlike any other card. When full OpenGL > support arrives for XFree86, I'd recommend the Matrox G400 for the visual > quality. Until then, the Voodoo2 is a reasonable workaround. Right, but I've also had limited luck getting my VooDoo2 to work under FreeBSD. It does work, but I just can't get the gamma correct (everything is too dark), and the mouse is totally erratic (a linuxulator config problem on my part, I know). I guess I also haven't cared enough to actually get it working correctly. :-) Also, the VooDoo2 is seriously lacking in visual quality. Just about any modern card, even the cheaper ones, can probably do better. > I'd also disagree about "solid drivers" from Matrox. I've installed > many of their unreliable OpenGL driver revisions. Then I bought a TNT2. Most of my experience with the Matrox drivers has been in the 2D arena, and I must say I've never had a problem with them. I can't comment as much on their 3D drivers, but ALL of the vendors have problems with that now and then, especially when the drivers are young. -- 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 Thu Feb 3 11:27:21 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from uswgco3.uswc.uswest.com (uswgco3.uswest.com [209.54.108.174]) by builder.freebsd.org (Postfix) with ESMTP id 302143E2D for ; Thu, 3 Feb 2000 11:27:17 -0800 (PST) Received: from egate-ut2.uswc.uswest.com (egate-ut2.uswc.uswest.com [148.157.122.199]) by uswgco3.uswc.uswest.com (8.8.5/8.8.5) with ESMTP id MAA26261 for ; Thu, 3 Feb 2000 12:22:17 -0700 (MST) Received: from medmail.mrg.uswest.com (localhost [127.0.0.1]) by egate-ut2.uswc.uswest.com (8.8.8/8.8.8) with ESMTP id MAA08186 for ; Thu, 3 Feb 2000 12:22:08 -0700 (MST) Received: from worldsecure.dex.uswest.com (worldsecure.dex.uswest.com [155.70.2.88]) by medmail.mrg.uswest.com (8.7.1/8.7.3) with SMTP id MAA22154 for ; Thu, 3 Feb 2000 12:16:04 -0700 (MST) Received: from 155.70.2.83 by worldsecure.dex.uswest.com with ESMTP ( WorldSecure Server SMTP Relay(WSS) v4.3); Thu, 03 Feb 00 12:22:06 -0700 X-Server-Uuid: aadd1a76-264d-11d1-91c7-080009d97107 Received: by DENIMS01.mrg.uswest.com with Internet Mail Service ( 5.5.2448.0) id <1F91TB3N>; Thu, 3 Feb 2000 12:22:06 -0700 Message-ID: From: "Sattler, Rick" To: "'freebsd-hardware@freebsd.org'" Subject: problem enabling new ethernet card... Date: Thu, 3 Feb 2000 12:22:05 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) X-WSS-ID: 14870AD4790343-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Howdy, I am attempting to create a dual-homed system and have run into a snag - I am having difficulty enabling the new ethernet adapter in the PC I am using. I have made sure the particular ethernet device is uncommented in the configuration file for my kernel, I have verified that the card is seen and enable in the system BIOS routine, yet the device is not probed for nor is it enabled upon boot of the system. I can enable/disable the current ethernet interface, so the configuration/make/install process is working. An assistance would be greatly appreciated. Here are the particulars: Running FreeBSD v3.1 (will upgrade AFTER I get this all working properly). The PC is a Compaq Deskpro 4000 with an embedded ThunderLan PCI ethernet chip. Plenty of RAM, plenty of disk. Everything working fine. Added a 3Com 10/100 PCI ethernet card on the PCI bus, slot 3. As far as I can tell, this device equates to "device xl0" in the configuration file for my PC. In any case, I do not have any ethernet device commented out in the configuration file... I have also added the following to the /etc/rc.conf file for the card: # added xl0 - new 3com ethernet card ifconfig_xl0="inet 144.163.49.97 media "100baseT/UTP" mediaopt "full-duplex" netmask 255.255.255.0" # original embedded interface config ifconfig_tl0="inet 144.163.49.36 media "10baseT/UTP" mediaopt "half-duplex" netmask 255.255.255.0" network_interfaces="tl0 lo0 xl0" For reference, I have edited the particular configuration file for my PC. Ran /usr/sbin/config against it. Changed directories to the appropriate compile directory to run "make depend", "make", and "make install". When I reboot the system to boot the new kernel, it does not probe for the new card, just enables the embedded (original) device and continues on it's merry way like it doesn't exist. It shouldn't be this difficult, should it? Thanks in advance, Rick Sattler rsattle@uswest.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 4 4:35: 4 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by builder.freebsd.org (Postfix) with ESMTP id 6E2704025 for ; Fri, 4 Feb 2000 04:34:59 -0800 (PST) Received: by ren.detir.qld.gov.au; id WAA12614; Fri, 4 Feb 2000 22:34:32 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd012609; Fri Feb 4 22:34:23 2000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA02733; Fri, 4 Feb 2000 22:34:05 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id WAA11899; Fri, 4 Feb 2000 22:34:05 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id WAA43156; Fri, 4 Feb 2000 22:34:04 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <200002041234.WAA43156@nymph.detir.qld.gov.au> To: Chris Dillon Cc: Stephen McKay , freebsd-hardware@freebsd.org, Haikal Saadh Subject: Re: Choice of display cards under freebsd. References: In-Reply-To: from Chris Dillon at "Thu, 03 Feb 2000 09:47:24 -0600" Date: Fri, 04 Feb 2000 22:34:04 +1000 From: Stephen McKay Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thursday, 3rd February 2000, Chris Dillon wrote: >My point was more that the 3DFX cards can't even do what their peers >can, which is 32-bit color-depth and Z-buffering. We're pretty close to agreement on most things. Even this. But my point is that these other features aren't always useful. To my mind, the only real failing of current 3dfx cards is the limited maximum texture size. AGP is a crock, hardware transform and lighting is ahead of its proper time (ie it's all hype without sufficient fill rate), and 32 bit colour ain't useful. Maybe 32 bit Z-buffering is useful, but I don't see the clipping problems you see *except* when a 32 bit card does pretty much the same thing (thinking Unreal and Half Life here). >If you take the Matrox G400 MAX as an example, it performs nearly as >well in 32-bit modes as it does in 16-bit, so 32-bit doesn't have to >mean a significant performance hit when your hardware is designed >correctly (plenty of memory bandwidth). When 32 bit is a zero cost option, I'll be converted. Check back in a year. >> I recommend a cheap Voodoo2... >Right, but I've also had limited luck getting my VooDoo2 to work under >FreeBSD. It does work, but I just can't get the gamma correct >(everything is too dark), and the mouse is totally erratic (a >linuxulator config problem on my part, I know). I guess I also >haven't cared enough to actually get it working correctly. :-) Well, OK, I admit I got a Weendoze box for gaming because so few games work with anything else. But soon, I'll have another go at gaming with FreeBSD. Last time I dabbled, it was with one of the early Quake3 tests and it worked fine on the Voodoo2 and the Linuxulator. Maybe my monitor is naturally brighter. Despite the limitations, a cheap Voodoo2 will be easier to get working for Linuxulator games than any other card, and will do OK until proper OpenGL support arrives for better cards. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 4 6: 7:38 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by builder.freebsd.org (Postfix) with ESMTP id DF3964048 for ; Fri, 4 Feb 2000 06:07:35 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #35196) with ESMTP id <01JLIIIC5PXW000O2U@research.kpn.com> for freebsd-hardware@freebsd.org; Fri, 4 Feb 2000 15:07:50 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Fri, 04 Feb 2000 15:07:49 +0100 Content-return: allowed Date: Fri, 04 Feb 2000 15:07:43 +0100 From: "Koster, K.J." Subject: Deskpro XL 466 works in 3.4-stable To: 'FreeBSD Hardware mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522013137E7@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear FreeBSD hardware list, No need to reply, this is only so that future owners of a Compaq Deskpro XL 466 will know that this machine works fine under FreeBSD version 3.4 stable. The on-board SCSI controller is supported by Teckram's amd driver. Kees Jan ============================================== You are only young once, but you can stay immature all your life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 5 10:16:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from hotmail.com (oe39.law4.hotmail.com [216.33.148.76]) by builder.freebsd.org (Postfix) with SMTP id 3CCA445FF for ; Sat, 5 Feb 2000 10:15:51 -0800 (PST) Received: (qmail 38988 invoked by uid 65534); 5 Feb 2000 18:16:18 -0000 Message-ID: <20000205181618.38987.qmail@hotmail.com> X-Originating-IP: [209.25.12.154] From: "Gregory Stark" To: , Subject: PnP PCI Modem Date: Sat, 5 Feb 2000 13:16:06 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" 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 apologize for the length of this e-mail, but I wanted to include all the information I had on my problem. I am unsuccessfully trying to talk to a PCI V.90 modem which I assume is a PnP modem. I am currently running a custom kernel 3.2-Release which has the isa0, pnp0, and pci0 controllers. I'll append the config file to this e-mail. The modem is an OEM 3com model 3CP2977 of which I can find absolutely no information. The motherboard is an ASUS P3B-F. The other peripherals in the system are: 1 IDE Hard Drive 1 IDE CD-ROM driver 1 Floppy drive 1 AGP Video card 1 ISA PnP Sound card I have tried using the PPP command in term mode to talk to the modem with absolutely no success. I have set the device to each of the cuaa values. In fact, the system seems to find almost no evidence of the modem's existence. Here is the output from running pnpinfo: ############### begin pnpinfo output ############### Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL00f0 (0xf0008c0e), Serial Number 0xffffffff PnP Version 1.0, Vendor Version 16 Device Description: Creative ViBRA16X PnP Logical Device ID: CTL0043 0x43008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x10, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x394, alignment 0x4, len 0x4 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG End DF Logical Device ID: CTL7005 0x05708c0e #1 Compatible Device ID: PNPb02f (2fb0d041) Device Description: Game TAG Start DF Good Configuration I/O Range 0x201 .. 0x201, alignment 0x1, len 0x1 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x200 .. 0x20f, alignment 0x1, len 0x1 [16-bit addr] TAG End DF End Tag Successfully got 48 resources, 2 logical fdevs -- card select # 0x0001 CSN CTL00f0 (0xf0008c0e), Serial Number 0xffffffff Logical device #0 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 Logical device #1 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 ############### end pnpinfo output ############### I assume all the pnpinfo output is referring to the sound card in the ISA slot. Now here is the some of the output from booting verbosely: ############### begin boot -v output ############### avail memory = 127836160 (124840K bytes) Found BIOS32 Service Directory header at 0xc00f92a0 Entry = 0xf06b0 (0xc00f06b0) Rev = 0 Len = 1 PCI BIOS entry at 0x8b0 SMIBIOS header at 0xc00f1f40 Version 2.3 Table at 0xf1f70, 44 entries, 1314 bytes, largest entry 93 bytes DMI header at 0xc00f1f50 Version 2.3 Table at 0xf1f70, 44 entries, 1314 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fc310 Preloaded elf kernel "kernel" at 0xc029d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc029d09c. pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7190, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base e4000000, size 26 chip0: rev 0x03 on pci0.0.0 found-> vendor=0x8086, dev=0x7191, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip1: rev 0x03 on pci0.1.0 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip2: rev 0x02 on pci0.4.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000d800, size 4 ide_pci0: rev 0x01 on pci0.4.1 intel_piix_status: primary master sample = 3, master recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary slave sample = 3, slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled ide_pci: busmaster 0 status: 64 from port: 0000d802 ide_pci: ide0:0 has been configured for DMA by BIOS ide_pci: ide0:1 has been configured for DMA by BIOS intel_piix_status: secondary master sample = 5, master recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary slave sample = 5, slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000d80a found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=9 map[0]: type 4, range 32, base 0000d400, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip3: rev 0x02 on pci0.4.3 found-> vendor=0x12b9, dev=0x1008, revid=0x01 class=07-00-02, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 map[0]: type 4, range 32, base 0000d000, size 3 Probing for devices on PCI bus 1: found-> vendor=0x102b, dev=0x0521, revid=0x03 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 3, range 32, base e3000000, size 24 map[1]: type 1, range 32, base e2000000, size 14 map[2]: type 1, range 32, base e1800000, size 23 vga0: rev 0x03 int a irq 11 on pci1.0.0 Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] Called nullpnp_probe with tag 0x00000001, type 0xf0008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 90 03 3c psm: status 90 03 3c psm: status 90 03 3c psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 12949MB (26520480 sectors), 26310 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 041f wdc0: unit 1 (atapi): , removable, accel, dma, iordis wdc0: ATAPI CD-ROMs not configured wdc1 not found at 0x170 ppc: parallel port found at 0x378 ppc: chipset forced to generic ppc0: ECP SPP ECP+EPP SPP ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached lpt0: on ppbus 0 lpt0: Interrupt-driven port vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface apm0: disabled, not probed. sb_reset_dsp failed sb0 not found at 0x220 imasks: bio c0084040, tty c003101a, net c0060080 BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert disabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry bpf: tun0 attached bpf: ppp0 attached bpf: ppp1 attached new masks: bio c0084040, tty c003101a, net c007109a bpf: lo0 attached Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to wd0s1a wd0s1: type 0xa5, start 63, end = 26520479, size 26520417 : OK ############### end boot -v output ############### I don't really know how to interpret all this but I don't see any evidence of the modem being recognized here. The final diagnostic I tried was running pnpscan at the boot prompt. This output is transcribed rather than verbatim. ############### begin pnpscan -v output ############### probing Pnp bios probing ISA bus probing PCI bios pnp0401 pnp0501 pnp0501 pnp0700 pnp0f13 pnp0c01 pnp0000 pnp0100 pnp0b00 pnp0303 pnp0c04 pnp0200 pnp0800 pnp0a03 pnp0c02 ctl00f0:creative Vibra16x pnp found 71118086: IDE controller 0521102b: VGA display 100812b9: 16550 serial controller 71128086: USB controller ############### end pnpscan -v output ############### I thought perhaps the "100812b9: 16550 serial controller" might have been the only hint that freebsd saw my modem. Can anybody confirm this? Any help out there? If I have to, I'll just buy an external modem, but I don't want to. Greg Stark securityguides llc greg@securityguides.com www.securityguides.com ##################begin kernel config file############# # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.143.2.12 1999/05/14 15:12:26 jkh Exp $ machine "i386" cpu "I686_CPU" ident MORGAN maxusers 32 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 controller isa0 controller pnp0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # # `flags' for serial drivers that support consoles (only for sio now): # 0x10 enable console support for this unit. The other console flags # are ignored unless this is set. Enabling console support does # not make the unit the preferred console - boot with -h or set # the 0x20 flag for that. Currently, at most one unit can have # console support; the first one (in config file order) with # this flag set is preferred. Setting this flag for sio0 gives # the old behaviour. # 0x20 force this unit to be the console (unless there is another # higher priority console). This replaces the COMCONSOLE option. # 0x40 reserve this unit for low level console operations. Do not # access the device in any normal way. # # PnP `flags' (set via userconfig using pnp x flags y) # 0x1 disable probing of this device. Used to prevent your modem # from being attached as a PnP modem. # device sio0 at isa? port "IO_COM1" tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 # Parallel port device ppc0 at isa? port? flags 0x40 net irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? drq 5 #device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 #device opl0 at isa? port 0x388 pseudo-device loop pseudo-device ether pseudo-device ppp 2 pseudo-device tun 1 pseudo-device pty 16 pseudo-device bpfilter 4 pseudo-device gzip # Exec gzipped a.out's options PPP_BSDCOMP options PPP_DEFLATE options PPP_FILTER # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options "ICMP_BANDLIM" ################## end kernel config file ############# To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 5 10:38:53 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from moffetimages.com (alar.scruz.predictive.com [207.251.1.130]) by builder.freebsd.org (Postfix) with ESMTP id A788245CB; Sat, 5 Feb 2000 10:38:46 -0800 (PST) Received: (from brianm@localhost) by moffetimages.com (8.9.3/8.9.3) id KAA34831; Sat, 5 Feb 2000 10:41:16 -0800 (PST) (envelope-from brianm) Date: Sat, 5 Feb 2000 10:41:16 -0800 (PST) From: "Brian D. Moffet" Message-Id: <200002051841.KAA34831@moffetimages.com> To: gregory_stark@hotmail.com Subject: Re: PnP PCI Modem Cc: hardware@freebsd.org, questions@freebsd.org In-Reply-To: <20000205181618.38987.qmail@hotmail.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > found-> vendor=0x12b9, dev=0x1008, revid=0x01 > class=07-00-02, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=255 > map[0]: type 4, range 32, base 0000d000, size 3 That is your modem, and according to the PNP stuff, it looks like a 16550, which is good. > device sio0 at isa? port "IO_COM1" tty irq 4 > device sio1 at isa? port "IO_COM2" tty irq 3 The way I did this is to modify the sio drivers to be: device sio1 at isa? port 0xe800 tty irq 3 which required me to hard code the irq to be 3 in the BIOS. In yourcase, the base address you would put in instead of 0xe800 would be 0xd000. My complete sio stuff is: # Serial (COM) ports device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port 0xe800 tty irq 3 device sio2 at isa? port "IO_COM3" tty irq 10 device sio3 at isa? disable port "IO_COM4" tty irq 9 I do not have the PNP stuff enabled. when mine boots, it states: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0xe800-0xe807 irq 3 on eisa slot 14 sio1: type 16550A sio2 at 0x3e8-0x3ef irq 10 on isa sio2: type 16550A I did choose to put my modem on SIO1, and my second serial port on SIO2, but that is up to you. Using hylafax, I can receive faxes on the modem, I have not set it up for dialup or anything, sometime in the near future. Good Luck Brian Moffet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Feb 7 6:52: 8 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from engine2.dhivehinet.net.mv (engine2.dhivehinet.net.mv [202.1.192.211]) by builder.freebsd.org (Postfix) with ESMTP id 6221E3F1E for ; Mon, 7 Feb 2000 06:52:01 -0800 (PST) Received: from summoner ([202.1.193.124]) by engine2.dhivehinet.net.mv (Post.Office MTA v3.5.3 release 223 ID# 0-58493U3000L300S0V35) with SMTP id mv for ; Mon, 7 Feb 2000 19:52:38 +0500 Message-ID: <000401bf717a$b785a0c0$7cc101ca@summoner> From: "Haikal Saadh" To: Subject: A suggestion, if I may... Date: Mon, 7 Feb 2000 10:44:47 +0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How about a website where people can go and rate certain pieces of hardware? And throw in instructions on how they it (the hardware) up, as well as performance notes, perhaps. Something along the lines of the software compatablility page at the Wine project's website? [www.winehq.org , I think.] I think that would help people make up their minds on what to buy, as well as making it easier to answer 'does this work with freebsd?' questions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Feb 7 7:37:17 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.rz.fh-wilhelmshaven.de (mail.rz.fh-wilhelmshaven.de [139.13.25.134]) by builder.freebsd.org (Postfix) with ESMTP id A92BB3FC5 for ; Mon, 7 Feb 2000 07:37:02 -0800 (PST) Received: from fettesau.stuwo.fh-wilhelmshaven.de (stuwopc5.stuwo.fh-wilhelmshaven.de [139.13.209.5]) by mail.rz.fh-wilhelmshaven.de (8.9.3/8.9.3) with SMTP id QAA02890; Mon, 7 Feb 2000 16:37:29 +0100 (MET) Message-Id: <4.1.20000207163012.0091f8b0@mail.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mail.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 07 Feb 2000 16:32:11 +0100 To: "Haikal Saadh" From: Olaf Hoyer Subject: Re: A suggestion, if I may... Cc: hardware@FreeBSD.ORG In-Reply-To: <000401bf717a$b785a0c0$7cc101ca@summoner> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 10:44 07.02.00 +0500, you wrote: >How about a website where people can go and rate certain pieces of hardware? >And throw in instructions on how they it (the hardware) up, as well as >performance notes, perhaps. >Something along the lines of the software compatablility page at the Wine >project's website? [www.winehq.org , I think.] > >I think that would help people make up their minds on what to buy, as well >as making it easier to answer 'does this work with freebsd?' questions. > Hi! Well, Ok, I also thought about that while in process of re-building my webpages.. If someone would assist a bit in gathering/maintaining, I'd be happy to contribute some webspace for that... Comments appreciated... Regards Olaf Hoyer -------- Olaf Hoyer www.nightfire.de mailto:Olaf.Hoyer@nightfire.de FreeBSD- Turning PC's into workstations ICQ:22838075 Liebe und Hass sind nicht blind, aber geblendet vom Feuer, dass sie selber mit sich tragen. (Nietzsche) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Feb 7 14:34:16 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.nostrum.com (mail.nostrum.com [206.28.8.254]) by builder.freebsd.org (Postfix) with ESMTP id D2BC73D70 for ; Mon, 7 Feb 2000 14:34:10 -0800 (PST) Received: (from pckizer@localhost) by mail.nostrum.com (8.9.0/8.9.0) id QAA04234; Mon, 7 Feb 2000 16:34:56 -0600 Message-Id: <200002072234.QAA04234@mail.nostrum.com> To: freebsd-hardware@freebsd.org Subject: Fwd: Problems with a new cyclades Ye-32, HW or driver? 8-bit characters where there shouldn't be From: Philip Kizer Date: Mon, 07 Feb 2000 16:34:56 -0600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I sent this to -questions a week ago with no response, so I though I'd try one last time on -hardware. More information from my end will probably be needed (perhaps the card revision numbers?); but, here's the situation: Existing system running 3.4-STABLE, happily using an existing Cyclades Ye-32 (not that it really matters, but for Sun/SGI/FreeBSD serial consoles, FYI). I purchased a new Ye-32 planning on going to a total of 64-ports split on 2 cards. To make sure all was working, I pulled the old card out, verified that the DIP switches on the new card matched the configuration of the old card, and put the new card in its place, no other changes, just a card- swap. Powered up... It didn't work: It "randomly" sets the high-bit of outgoing characters: (i.e. character sent = character typed | 0x80) [which wreaks havoc as a console interface] % kermit -l /dev/cuac00 C-Kermit 7.0.196, 1 Jan 2000, for FreeBSD 3.0 Copyright (C) 1985, 2000, Trustees of Columbia University in the City of New York. Type ? or HELP for help. (/home/pckizer/) C-Kermit>c Connecting to /dev/cuac00, speed 9600. The escape character is Ctrl-\ (ASCII 28, FS) Type the escape character followed by C to get back, or followed by ? to see other options. ---------------------------------------------------- root@ldap-test:/ # ls zsh: command not found: \M-ls zsh: exit 1 ls root@ldap-test:/ # id zsh: command not found: i\M-d zsh: exit 1 id root@ldap-test:/ # id zsh: command not found: i\M-d zsh: exit 1 id root@ldap-test:/ # sh # id uid=0(root) gid=0(root) # id uid=0(root) gid=0(root) # id i\344: not found # id i\344: not found # id i\344: not found # uptime \365p\364i\355\345: not found # uptime \365p\364i\355\345: not found # ---------------------------------------------------- Device: /dev/cuac00 Speed 9600 Terminal echo: remote Terminal bytesize: 7 Command bytesize: 7 Parity: none Autodownload: on Session log: (none) Carrier Detect (CD): On Dataset Ready (DSR): On Clear To Send (CTS): On Ring Indicator (RI): Off Data Terminal Ready (DTR): On Request To Send (RTS): On Elapsed time: 00:00:36 ---------------------------------------------------- So, the pattern is "mostly" repeatable; it certainly has not worked except for the odd command (if I continue typing 'id', I have yet to get a successful non-high-bit-set entire command in 30+ tries). I've tried the all combinations of: {7,8}{E,N}{1,2} with no success. Also, again, the exact same setup works using an existing card. Things I have tried (in order): o Booting from a DOS floppy and ran cyctest.exe (cyc400), all tests passed on both cards, o Call Cyclades tech-support, got blown off (must be software, we don't support that), o Download their (older) cyy30 FreeBSD driver from their ftp server and try to compile it. It doesn't even compile (minor change needed [adding an #include just like sio.c does], but when I do so, I get even worse behaviour, i.e. no connection at all, boot says: cy0 irq 10 maddr 0xd4000 msize 8192 on isa cy0: irq with no handler). o Compile in ddb so I might be able to print out the kernel structures to make absolutely sure no 8-bit data is being sent, but my level of kernel debugging is not up to it without some explicit instructions. Since I was trying their driver, I though I might call them back regarding their code, but given that this community tends to be more helpful and the included driver is newer than theirs, I thought I would try here before banging my head on their tech support's door again. I am also leaning heavily towards returning the card to the vendor and asking for a "new" one, even though the cyc400 tests all passed. Basically, I'm seeking some suggestions on where to turn (or, better yet, that someone might have seen this before). Thanks, philip -- AKA: Philip Kizer Texas A&M CIS Operating Systems Group, Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Feb 9 9:50:52 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from bartok.lanl.gov (bartok.lanl.gov [128.165.205.72]) by builder.freebsd.org (Postfix) with ESMTP id 496D140C6; Wed, 9 Feb 2000 09:50:39 -0800 (PST) Received: (from john@localhost) by bartok.lanl.gov (8.9.2/8.9.2) id JAA02994; Wed, 9 Feb 2000 09:51:15 -0700 (MST) (envelope-from john) Date: Wed, 9 Feb 2000 09:51:15 -0700 (MST) Message-Id: <200002091651.JAA02994@bartok.lanl.gov> From: John Galbraith To: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: National Instruments AT-GPIB/TNT driver Cc: john@bartok.lanl.gov Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have posted a new version of my GPIB (IEEE 488, or HPIB) driver to www.ece.arizona.edu/~john. This one is a total rewrite of my old one and should be faster on small transfers and a bit more reliable overall. It has also been ported to the FreeBSD-4.0 newbus architecture. I have been running real experiments on it, so the basic stuff is working well for me. There is some documentation and some examples there, and instructions on how to install it. Please let me know if you are interested in this and if it works for you. There aren't many people using GPIB with FreeBSD, so I would like to know about everybody and anybody who ends up using this for anything so we can get it well tested. Thanks, John Galbraith john@bartok.lanl.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Feb 9 11:13:39 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by builder.freebsd.org (Postfix) with ESMTP id B991741B7 for ; Wed, 9 Feb 2000 11:13:32 -0800 (PST) Received: from shell-3.enteract.com (jrs@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id NAA38960 for ; Wed, 9 Feb 2000 13:12:56 -0600 (CST) (envelope-from jrs@enteract.com) Date: Wed, 9 Feb 2000 13:12:55 -0600 (CST) From: John Sconiers To: freebsd-hardware@freebsd.org Subject: Exteranal SCSI storedge devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm look at purchasing an exteranal storedge device and place 4 9gb SCA drives into them to connect to a scsi card on my freebsd box. Can anybody recommend an enclosure?? Jrs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 10 13:30:28 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by builder.freebsd.org (Postfix) with ESMTP id 87B834737 for ; Thu, 10 Feb 2000 13:30:25 -0800 (PST) Received: from vpop.net (bilbo.vpop.net [216.160.82.65]) by boromir.vpop.net (8.9.1/8.9.1) with ESMTP id NAA01278; Thu, 10 Feb 2000 13:29:16 -0800 (PST) Message-ID: <38A32DBE.6B158100@vpop.net> Date: Thu, 10 Feb 2000 13:29:34 -0800 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Sconiers Cc: freebsd-hardware@freebsd.org Subject: Re: Exteranal SCSI storedge devices References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Sconiers wrote: > > I'm look at purchasing an exteranal storedge device and place 4 9gb SCA > drives into them to connect to a scsi card on my freebsd box. Can anybody > recommend an enclosure?? > > Jrs We've had good success with Kingston enclosures (two of the four-bay enclosures with four 4G disks). Before we got them, we were losing drives (probably to heat), but we haven't had a single problem with those disks in the two years since. Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 11 2:26: 4 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by builder.freebsd.org (Postfix) with ESMTP id 55E4646E0 for ; Fri, 11 Feb 2000 02:25:58 -0800 (PST) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id KAA10405; Fri, 11 Feb 2000 10:25:42 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id WAA02290; Thu, 10 Feb 2000 22:51:00 GMT (envelope-from n_hibma@calcaphon.com) Date: Thu, 10 Feb 2000 22:51:00 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Michael Robinson Cc: freebsd-hardware@freebsd.org Subject: Re: USB CD-RW drive In-Reply-To: <200001151746.BAA06653@netrinsics.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 SOrry for the slow response. If all goes well this device should eventually (in a month or two) be supported. Most ATAPI devices use the bridge from Shuttle or the one from another company, of which I cannot remember the name at the moment. The difficulty is twofold at the moment. First the wire protocol has to be implemented and second some form of atapi driver on top of this has to be created. If you want to be sure to stay on top of this subscribe yourself to the usb-bsd@egroups.com mailing list. I'll save a copy of your message locally in the appropriate folder to update you when it is ready, but I have the tendency to forget that or postpone it until it is already in 4.x included :-) Cheers, Nick On Sun, 16 Jan 2000, Michael Robinson wrote: > I just received a HP USB CD-RW drive. Is there any hope of making this work > under freebsd? Is there any hope of making it work after Warner finishes > his newbusification work? > > -Michael Robinson > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 11 3:17:16 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from lilzcvp.liwest.at (lilzcvp.liwest.at [212.33.32.230]) by builder.freebsd.org (Postfix) with SMTP id 3E1263D2C for ; Fri, 11 Feb 2000 03:17:09 -0800 (PST) Received: from [212.33.32.221] by lilzcvp.relay.liwest.at (NTMail 4.30.0012/AB8573.63.b914fe78) with ESMTP id zkgwaaaa for ; Fri, 11 Feb 2000 12:16:48 +0000 Received: by OFFICE1_LIWEST with Internet Mail Service (5.5.2232.9) id ; Fri, 11 Feb 2000 12:15:59 +0100 Message-ID: <1F879C64A1A7D211B0F10004AC4C07FC119CE9@OFFICE1_LIWEST> From: Haider Roland To: "'freebsd-hardware@freebsd.org'" Subject: Is the COMPAQ Smart Arry controller family now supported ? Date: Fri, 11 Feb 2000 12:15:54 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi and thank's for reading! I'm getting a bit worried about our investment. A few months ago I checked the handbook and release notes to see wether its worth upgrading our old compaq servers or not. There were a bunch of Compaq RAID controllers listed in the hardware controllers section, so I thougt adding disks and RAM would make them good FreeBSD machines. Now I finished the hardware upgrade and tried to install 3.4-RELEASE, but no controller is detected. A quick check in LINT also brought up nothing. So is this already alzheimer or has the documentation changed? Have those controllers never been supported? Do I realy have to stick with NT? What pizza should I order today? So many questions, so few answers..... Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 11 9: 2:47 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from svlcaexch2.ins.com (svlcaexch2.ins.com [199.0.193.121]) by builder.freebsd.org (Postfix) with ESMTP id C8A363D3F for ; Fri, 11 Feb 2000 09:01:34 -0800 (PST) Received: from kagan.quedawg.com (199.0.199.167 [199.0.199.167]) by svlcaexch2.ins.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 1WF98L6G; Fri, 11 Feb 2000 08:59:38 -0800 Received: (from psiphi@localhost) by kagan.quedawg.com (8.9.3/8.9.3) id MAA02741 for freebsd-hardware@freebsd.org; Fri, 11 Feb 2000 12:48:35 GMT Date: Fri, 11 Feb 2000 12:48:34 +0000 From: "Brian K . Walters" To: freebsd-hardware@freebsd.org Subject: SMP Machines Message-ID: <20000211124834.B2690@kagan.quedawg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: Linux Organization: Lucent Netcare Professional Services X-Disclaimer: Lucent NPS - The Knowledge Behind The Network Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm new to freebsd and I am looking to replace Linux with freebsd on my Dell workstation that I have at home. How is the performance of freebsd on SMP machines. I looked around but did not see any reference to freebsd on SMP machines like they have kernels specifically tailored for SMP in Linux. Does freebsd have that capability? thanks, -- Brian K. Walters -- Senior Network Systems Consultant ----------------------------------------------------- Lucent Technologies -- bkwalters@lucent.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 11 9: 7:48 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by builder.freebsd.org (Postfix) with SMTP id 160163D89 for ; Fri, 11 Feb 2000 09:07:45 -0800 (PST) Received: (qmail 29779 invoked by uid 1825); 11 Feb 2000 17:07:32 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 11 Feb 2000 17:07:32 -0000 Date: Fri, 11 Feb 2000 12:07:32 -0500 (EST) From: X-Sender: up@richard2.pil.net To: "Brian K . Walters" Cc: freebsd-hardware@freebsd.org Subject: Re: SMP Machines In-Reply-To: <20000211124834.B2690@kagan.quedawg.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 On Fri, 11 Feb 2000, Brian K . Walters wrote: > I'm new to freebsd and I am looking to replace Linux with freebsd > on my Dell workstation that I have at home. How is the performance > of freebsd on SMP machines. I looked around but did not see any > reference to freebsd on SMP machines like they have kernels > specifically tailored for SMP in Linux. > > Does freebsd have that capability? Sure, just uncomment the appropriate lines in your kernel config file, recompile and install the kernel: # To make an SMP kernel, the next two are needed # options SMP # Symmetric MultiProcessor Kernel # options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 11 9:52:20 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by builder.freebsd.org (Postfix) with ESMTP id 5839C3D76 for ; Fri, 11 Feb 2000 09:52:15 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id MAA71254; Fri, 11 Feb 2000 12:52:03 -0500 (EST) Date: Fri, 11 Feb 2000 12:52:03 -0500 (EST) From: "Matthew N. Dodd" To: Haider Roland Cc: "'freebsd-hardware@freebsd.org'" Subject: Re: Is the COMPAQ Smart Arry controller family now supported ? In-Reply-To: <1F879C64A1A7D211B0F10004AC4C07FC119CE9@OFFICE1_LIWEST> 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, 11 Feb 2000, Haider Roland wrote: > There were a bunch of Compaq RAID controllers listed in the > hardware controllers section, so I thougt adding disks and > RAM would make them good FreeBSD machines. What kind of Compaq RAID controllers do you have? Currently the driver in the tree supports the PCI Smart-2, Smart 31xx and Smart 221 series array controllers. I'm working on support for the 42xx series as well as the EISA Smart-2 controllers. I've got EISA IDA and IDA-2 controllers as well but until I'm able to write a FreeBSD based array config util I'm not sure I'll be able to get them running. If you've got an IDA or IDA-2 controller I'd love to talk to you. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 11 19:10:43 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from borg-cube.com (226-193.adsl2.avtel.net [207.71.226.193]) by builder.freebsd.org (Postfix) with ESMTP id 52FC93ED3; Fri, 11 Feb 2000 19:10:40 -0800 (PST) Received: from borg-cube.com (dburr@borg-cube.com [207.71.226.193]) by borg-cube.com (8.9.3/8.9.3) with ESMTP id TAA28526; Fri, 11 Feb 2000 19:06:50 -0800 (PST) (envelope-from dburr@borg-cube.com) Date: Fri, 11 Feb 2000 19:06:46 -0800 (PST) From: Donald Burr To: FreeBSD Hardware Cc: FreeBSD SCSI Subject: Tekram DC-315U: what kind of chipset, and is it FBSD compatible? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I found a nice SCSI card on ebay that I want to buy: http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=253753162 NEW! Tekram DC315U Ultra SCSI Controller Card This is an UltraSCSI (narrow 50pin, 20MB/sec) card, and the chipset is listed on the spec sheet as "Tekram S1040 Ultra SCSI processor" I thought the Tekram cards used the NCR/Symbios chips on them? Is this chip merely a re-labeled symbios part? And, most importantly, WILL IT WORK IN FREEBSD? Anyone who can provide assisntance, it would be greatly appreciated! Thanks! -- Donald Burr Resistance is Futile | FreeBSD: The WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | Serve! http:// Phone: (805) 957-9666 FAX: (800) 492-5954 | 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 Feb 11 19:52:54 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id AD6EE3EA7; Fri, 11 Feb 2000 19:52:43 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA60486; Fri, 11 Feb 2000 20:21:34 -0700 (MST) (envelope-from ken) Date: Fri, 11 Feb 2000 20:21:33 -0700 From: "Kenneth D. Merry" To: Donald Burr Cc: FreeBSD Hardware , FreeBSD SCSI Subject: Re: Tekram DC-315U: what kind of chipset, and is it FBSD compatible? Message-ID: <20000211202133.A60458@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dburr@borg-cube.com on Fri, Feb 11, 2000 at 07:06:46PM -0800 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Feb 11, 2000 at 19:06:46 -0800, Donald Burr wrote: > I found a nice SCSI card on ebay that I want to buy: > > http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=253753162 > NEW! Tekram DC315U Ultra SCSI Controller Card > > This is an UltraSCSI (narrow 50pin, 20MB/sec) card, and the chipset is > listed on the spec sheet as "Tekram S1040 Ultra SCSI processor" I thought > the Tekram cards used the NCR/Symbios chips on them? Is this chip merely > a re-labeled symbios part? And, most importantly, WILL IT WORK IN > FREEBSD? The S1040 is Tekram's own Ultra-Wide (i.e. 16 bit, 20Mhz) SCSI chip. The 315 just uses that chip in a narrow configuration, and I think the 395 is an Ultra-Wide board. You can use it for FreeBSD, since Tekram has written a FreeBSD/CAM driver for it. (Tekram is to be commended for supporting FreeBSD! They also wrote their own AMD driver, which is in our tree, and their own NCR driver for FreeBSD.) You'll have to download the driver from Tekram's web or ftp site (not sure where it is), and compile a new kernel. The catch is that at least from the way the driver is written, it doesn't look like the chip has a SCSI phase engine, so it probably won't perform very well. (i.e. several interrupts per transaction) If you want a Tekram board, I would suggest one of their NCR/Symbios/LSI based boards. You can use those with the sym driver, and they will perform pretty 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 Sat Feb 12 1:35:17 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1]) by builder.freebsd.org (Postfix) with ESMTP id 63EF43D55; Sat, 12 Feb 2000 01:35:11 -0800 (PST) Received: from pn.nettuno.it (ppp19-nas0.pn.nettuno.it [193.207.109.188]) by bologna.nettuno.it (8.9.3/8.9.3/NETTuno 4.1) with ESMTP id KAA10497; Sat, 12 Feb 2000 10:35:03 +0100 (MET) Message-ID: <38A52AFD.82226A9C@pn.nettuno.it> Date: Sat, 12 Feb 2000 10:42:21 +0100 From: "James A. Abercromby II" X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Schwenk , freebsd-hardware@FreeBSD.org, freebsd-questions@FreeBSD.org Subject: Re: Dual Boot Win98/FreeBSD 3.4 X-Priority: 1 (Highest) References: <38A49256.3731862F@pn.nettuno.it> <38A494A9.1284978C@math.udel.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter, Got a quick question for ya I wanna buy this ASUS ide/atapi 52X cd drive, but I am wondering this is an old (not really imo) FIC PA-2011 via chipset based ATX motherboard w/AMD 233 K6 (old school) hehe. If I hook up 52x cd drive will the bottlenecks/performance problems? Peter Schwenk wrote: > I'd buy a name-brand CDROM, even if it's slower. I'm glad to hear that you > are getting things going! It really is worth it. FreeBSD rox once you get > the hang of it. > > "James A. Abercromby II" wrote: > > > Peter, > > Just thought I would let you know. > > > > SUCCESS > > > > You won't believe this, but.... > > > > You know in the errata for 3.4 it talks about doing custom/expert > > installs being > > corrupt sig11ing etc. and to download the new MFSBoot.flp disk? > > Well it never said anything about doing installs NOVICE right? so you > > should > > be good except for custom/expert? > > > > Well, all this blood, sweat, and tears I was going through I was > > exclusively > > using the NOVICE option. > > > > Downloaded the new MFSBoot.flp disk made a new floppy. > > > > Boom. > > > > Good to go? > > > > No. > > > > The only way I got the Maxtor 17.2gig to take FreeBSD to dual boot > > was to create 1-479meg, 1-8000meg, 1-8000meg slices. > > > > pick boot option of none or standard (shit now I forget which one I > > used) > > > > boom. > > > > But... > > one little side note > > > > The first novice install right off the bat I chose everything. > > The stupid 40x atapi/ide cdrom would hang here and there. > > > > HI-VAL is crap I am coming to the conclusion. > > You think its worth it to buy an ASUS 52X for 75$???? IDE/ATAPI > > > > so, > > Last go round I only installed bin-distribution (required/minimal) > > finished the install > > and I was good to , logged in and everything (I figure tommorow I can go > > back > > and run sysinstall and pick the distributions and packages I want > > right?). > > > > At the moment I rebooted back into Win98 to email you. > > > > Man, I really do appreciate your help and patience. > > > > See ya > > in the list > > > > next is configuring my ppp dialup > > > > Sincerely > > James A. Abercromby II > > -- > PETER SCHWENK | UNIX System Administrator > Department of Mathematical Sciences | University of Delaware > schwenk@math.udel.edu | (302)831-0437 <-NEW!!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 12 2:13:30 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mt.ks.edu.tw (mt.ks.edu.tw [163.16.1.20]) by builder.freebsd.org (Postfix) with ESMTP id 958924276 for ; Sat, 12 Feb 2000 02:12:27 -0800 (PST) Received: from netscape.net (tnt2-80.ks.edu.tw [163.16.4.90]) by mt.ks.edu.tw (8.9.3/8.9.3) with ESMTP id SAA31410 for ; Sat, 12 Feb 2000 18:13:49 +0800 Message-ID: <38A531BD.5CA1BA40@netscape.net> Date: Sat, 12 Feb 2000 18:11:09 +0800 From: kemmy X-Mailer: Mozilla 4.5 [zh-TW] (Win98; I) X-Accept-Language: zh-TW MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: integrated AGP display card Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't know how to configure my AGP display card(SiS 85c503) to run under any Xserver. I don't know which is the most appropriate server for it either. My system is FreeBSD 3.0-980222-SNAP, XFree86 3.1.2D. I've done trial and error a lot these 3 days and quite frustrated. Here is the result of "SuperProbe" First video: Super-VGA Chipset: Tseng (chipset unknown) (Port Probed) Signature data: f (please report) Memory: 0 Kbytes RAMDAC: Generic 8-bit pseudo-color DAC (with 6-bit wide lookup tables (or in 6-bit mode)) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 12 2:28:40 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by builder.freebsd.org (Postfix) with ESMTP id 496C33E52 for ; Sat, 12 Feb 2000 02:28:37 -0800 (PST) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id DAA18562; Sat, 12 Feb 2000 03:28:22 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Sat, 12 Feb 2000 03:28:22 -0700 (MST) From: Doug Russell To: kemmy Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: integrated AGP display card In-Reply-To: <38A531BD.5CA1BA40@netscape.net> 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 Sat, 12 Feb 2000, kemmy wrote: > I don't know how to configure my AGP display card(SiS 85c503) to run > under any Xserver. > I don't know which is the most appropriate server for it either. > > My system is FreeBSD 3.0-980222-SNAP, > XFree86 3.1.2D. Hmm... I don't see your chipset listed anywhere here, but recent XFree86 releases have support for several SiS chipsets. I have a: (--) SVGA: chipset: sis6326 (--) SVGA: videoram: 4096k in this machine, and it just started being usable in 3.3.6. In 3.3.5, it only worked in 24 bpp, there was no text display in other modes. It's still a little buggy, but it works reasonably well. From README.SiS in 3.3.6: 2. Supported chips SiS 86c201 (External hardware clock) SiS 86c202, SiS 86c2x5, SiS 5597/5598, SiS 6326, SiS 530, SiS 620 (Internal clock synthesizer) The above are supported by the SVGA server, however, If your chip really is a 85c503, I'm not sure where you look next. Perhaps try a more recent XFree86 SVGA server. Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 12 6:15: 0 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by builder.freebsd.org (Postfix) with ESMTP id 81C3B3E85; Sat, 12 Feb 2000 06:14:54 -0800 (PST) Received: from we.lc.ehu.es (lxpxdo.lx.ehu.es [158.227.99.192]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id PAA06288; Sat, 12 Feb 2000 15:14:49 +0100 (MET) Message-ID: <38A56AD6.8C3E1A97@we.lc.ehu.es> Date: Sat, 12 Feb 2000 15:14:46 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.org Cc: freebsd-mobile@FreeBSD.org Subject: [fix and RFC] interrupt-level buffer overflows with Xircom PCMCIA modem Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have just purchased a Xircom RealPort Modem 56, which I easily got working as sio1 after adding an entry to pccard.conf (the laptop runs 3.4-RELEASE). However, I was getting many messages like these on the console: sio1: 31 more interrupt-level buffer overflows (total 31) sio1: 273 more interrupt-level buffer overflows (total 273) sio1: 437 more interrupt-level buffer overflows (total 710) ... and so on. I tested this problem simply using the user-ppp's terminal, and typing modem commands such as "AT&V" or "ATI11", which give several lines of output. I must clearly state that the modem has RTS/CTS flow control enabled (AT&K3). And the laptop is new: a Dell Inspiron 3700 with a Celeron-433 processor, so that the system speed or load are not the causes of this problem. The first "solution" I tried was to disable the 16550A's FIFO using the sio(4) flag "0x02". The messages went away, indeed, but I was seeing ~3000 interrupts/second for sio1, and this is very bad. Then, I thought that increasing the sio's receive and/or send buffer sizes could be a better solution, so that after reading sys/i386/isa/sio.c I found the RS_IBUFSIZE macro, #defined to 256, and I incremented its value to 1024. This means that the memory dedicated to sio buffers grow from 1 Kbyte to 4 Kbyte for each sio device. Anyway, I compiled a new kernel and the buffer overflows dissapeared (with the 16550A's FIFO re-enabled, of course). Now, the conclusions: perhaps RS_IBUFSIZE=256 is too low for some devices (notably internal modems); it's only a theory. Or perhaps some devices have problems with RTS/CTS flow control. In any case, I suggest the addition of a new kernel configuration option for permitting to change RS_IBUFSIZE to any desired value. Any comments or ideas? -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 12 9:13:59 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by builder.freebsd.org (Postfix) with ESMTP id 55E013F45; Sat, 12 Feb 2000 09:13:46 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id EAA09932; Sun, 13 Feb 2000 04:16:21 +1100 Date: Sun, 13 Feb 2000 04:13:19 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Jose M. Alcaide" Cc: freebsd-hardware@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: [fix and RFC] interrupt-level buffer overflows with Xircom PCMCIA modem In-Reply-To: <38A56AD6.8C3E1A97@we.lc.ehu.es> 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 Sat, 12 Feb 2000, Jose M. Alcaide wrote: > Now, the conclusions: perhaps RS_IBUFSIZE=256 is too low for some devices > (notably internal modems); it's only a theory. Or perhaps some devices Too large for devices with broken 16550 emulation. > have problems with RTS/CTS flow control. In any case, I suggest RTS emulation is probably also broken for there to be a problem. Ideally, the sender should check its version of RTS (i.e., CTS) before sending each character. For bug for bug compatibility with 16550 senders, the sender only needs to check it every 16th character. > the addition of a new kernel configuration option for permitting > to change RS_IBUFSIZE to any desired value. RS_IBUFSIZE doesn't exist in -current. Instead, the buffer is sized to hold 4 ticks (4.0 / hz seconds) worth of input at the current input speed (or 128 bytes if that is larger). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 12 15:14:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by builder.freebsd.org (Postfix) with ESMTP id 8CD494019 for ; Sat, 12 Feb 2000 15:14:31 -0800 (PST) Received: from we.lc.ehu.es (lxpxfs.lx.ehu.es [158.227.99.248]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id AAA07240; Sun, 13 Feb 2000 00:14:20 +0100 (MET) Message-ID: <38A5E94B.397E77BC@we.lc.ehu.es> Date: Sun, 13 Feb 2000 00:14:19 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Bruce Evans Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: [fix and RFC] interrupt-level buffer overflows with Xircom PCMCIAmodem References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bruce Evans wrote: > > On Sat, 12 Feb 2000, Jose M. Alcaide wrote: > > > Now, the conclusions: perhaps RS_IBUFSIZE=256 is too low for some devices > > (notably internal modems); it's only a theory. Or perhaps some devices > > Too large for devices with broken 16550 emulation. Uh? Are you saying that I should decrement RS_IBUFSIZE instead of incrementing it? I could test this, but I don't see how a shorter buffer could help to avoid buffer overruns... > RTS emulation is probably also broken for there to be a problem. Ideally, > the sender should check its version of RTS (i.e., CTS) before sending > each character. For bug for bug compatibility with 16550 senders, the > sender only needs to check it every 16th character. I could insert some "probes" in sio.c to see what happens with RTS/CTS, but I am not a 16550 expert, so I need some advice :-) > RS_IBUFSIZE doesn't exist in -current. Instead, the buffer is sized to > hold 4 ticks (4.0 / hz seconds) worth of input at the current input speed > (or 128 bytes if that is larger). Ah! Unfortunately I am not running -CURRENT on my laptop. I should have checked -CURRENT's sio.c before suggesting that kernel config option. Sorry. Thanks very much, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Feb 13 0:18:48 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from lily.ezo.net (lily.ezo.net [206.102.130.13]) by builder.freebsd.org (Postfix) with ESMTP id 664E13E2B; Sun, 13 Feb 2000 00:18:42 -0800 (PST) Received: from lily.ezo.net (jflowers@localhost.ezo.net [127.0.0.1]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id DAA18388; Sun, 13 Feb 2000 03:18:45 -0500 (EST) Date: Sun, 13 Feb 2000 03:18:45 -0500 (EST) From: Jim Flowers To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Synchronous FT1 with Built-in CSU/DSU ISA/PCI 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 There have been a lot of posts looking for synch T1/FT1 PCI cards. We use the Sangoma ISA card with built-in CSU/DSU and have been quite satisfied with its performance. The CSU/DSU appears to be a BAT module and the software control/monitoring panel looks just like a BAT hardware unit down to the flashing LEDs and testing functions - just as sparse but sufficient to our purpose. From their news brief, it looks like the PCI card is now available. We have paired these with Livingston, Cray, BAT, Eastern Research and each other with no more than the usual turnup problems, fewer than many. It's nice having the driver code available Also, the freebsd driver has been rewritten. It needed it as the existing driver was at the 97% completion level. I have not tried it yet but will do so on our next VPN Access Controller. The news briefs follow: news briefs--------------------------------------- PCI S514/FT1 with integral T1 DSU/CSU shipping ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ February 11, 2000 The S514/FT1 PCI card has a built in T1 and Fractional T1 DSU/CSU. The card is software configurable to run at speeds from 64kbps to 1.54Mbps in steps of 64kbps. It is similar in all details to the S508/FT1, except that it is PCI based and requires no jumper settings. The North American retail price is $869.00 US. WANPIPE Version: 1.1.0 for FreeBSD Versions 3.1+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ February 5, 2000 This is a complete rewrite of Sangoma WANPIPE for FreeBSD-3.x that supports both S508 and the new S514 PCI cards, including the integrated DSU/CSU /FT1 versions. It supports Cisco HDLC, Frame Relay and PPP. The major difference from previous driver versions is that you don't need re-compile kernel each time you change the protocol type. In the new version you only need to stop all routers, reboot your machine, run the configuration program to edit the corresponding router configuration file and start the routers again. The new version supports two different modes: WANPIPE for routing and a user API for transparent user data transfer. The API is very standard, using the Berkeley Packet Filter. The code includes an installation script (Setup) that copies the files to the kernel tree directory and creates sample configuration files. A full screen based configuration utility (wancfg) is included, that automatically creates all configuration files. This user friendly interface does parameter checking and has comprehensive context sensitive help. It is the same utility that runs on WANPIPE under Linux. A similar utility, cfgft1 configures the DSU/CSU interactively. ----------------------------- I have no connection with Sangamo but I do like to see good products succeed, particularly when they support FreeBSD specifically. The support has been very good, both from David Mandelstam and from the fairly active users group. It looks like they plan to continue that support. Jim Flowers #4 ISP on C|NET, #1 in Ohio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Feb 13 9:15:55 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by builder.freebsd.org (Postfix) with ESMTP id B8C954174 for ; Sun, 13 Feb 2000 09:15:51 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id EAA25661; Mon, 14 Feb 2000 04:18:50 +1100 Date: Mon, 14 Feb 2000 04:15:41 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Jose M. Alcaide" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: [fix and RFC] interrupt-level buffer overflows with Xircom PCMCIAmodem In-Reply-To: <38A5E94B.397E77BC@we.lc.ehu.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 13 Feb 2000, Jose M. Alcaide wrote: > Bruce Evans wrote: > > > > On Sat, 12 Feb 2000, Jose M. Alcaide wrote: > > > > > Now, the conclusions: perhaps RS_IBUFSIZE=256 is too low for some devices > > > (notably internal modems); it's only a theory. Or perhaps some devices > > > > Too large for devices with broken 16550 emulation. > > Uh? Are you saying that I should decrement RS_IBUFSIZE instead of > incrementing it? I could test this, but I don't see how a shorter buffer > could help to avoid buffer overruns... Oops, I meant "too low". > > RTS emulation is probably also broken for there to be a problem. Ideally, > > the sender should check its version of RTS (i.e., CTS) before sending > > each character. For bug for bug compatibility with 16550 senders, the > > sender only needs to check it every 16th character. > > I could insert some "probes" in sio.c to see what happens with RTS/CTS, > but I am not a 16550 expert, so I need some advice :-) Maybe you aren't actually using RTS/CTS. RTS is mostly for the termios line discipline. For slip and ppp, it is only deasserted when the interrupt-level buffer is more than 3/4 full, not when buffers in higher layers are almost full. However that should be enough to stop an emulator. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Feb 13 11:51:48 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by builder.freebsd.org (Postfix) with ESMTP id D93184137; Sun, 13 Feb 2000 11:51:31 -0800 (PST) Received: from cs.ucla.edu (rdwarrior.cs.ucla.edu [131.179.192.88]) by mailman.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id LAA08391; Sun, 13 Feb 2000 11:51:41 -0800 (PST) Message-ID: <38A70B73.8A5DAE1C@cs.ucla.edu> Date: Sun, 13 Feb 2000 11:52:19 -0800 From: "B. Scott Michel" Organization: UCLA Computer Chaos X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, freebsd-stable@freebsd.org Subject: Sondy SDT-5000 SCSI tape drive problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm currently running FreeBSD 3.4 and finally got around to installing a tape drive (hey, backups are good, so I'm told... :-) I opted for installing flexbackup since I don't need to swat gnats with sledgehammers (i.e. Amanda is too heavy weight.) The problem I'm running into with the 3.4 kernel is that it keeps complaining: (sa0:ncr0:0:3:0): tape is now frozen- use an OFFLINE... So I go off and 'mt offline', reinsert the tape, do a 'flexbackup -newtape', only to repeat the cycle. What have I overlooked? -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Feb 13 11:55:58 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by builder.freebsd.org (Postfix) with ESMTP id 7DAA83E33; Sun, 13 Feb 2000 11:55:38 -0800 (PST) Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.192.128]) by mailman.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id LAA08417; Sun, 13 Feb 2000 11:55:48 -0800 (PST) Received: (from root@localhost) by mordred.cs.ucla.edu (8.9.3/UCLACS-5.0) id LAA00455; Sun, 13 Feb 2000 11:55:47 -0800 (PST) Date: Sun, 13 Feb 2000 11:55:47 -0800 (PST) From: The Root of all Vile Message-Id: <200002131955.LAA00455@mordred.cs.ucla.edu> To: freebsd-hardware@freebsd.org, freebsd-stable@freebsd.org Subject: Sony SDT-5000 and my configuration Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here's my configuration, FWIW. -scooter --------------------------------------------------------------------- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-STABLE #13: Sat Feb 12 16:01:50 PST 2000 root@mordred.cs.ucla.edu:/usr/src/sys/compile/MORDRED Timecounter "i8254" frequency 1193242 Hz Timecounter "TSC" frequency 233875483 Hz CPU: AMD-K6tm w/ multimedia extensions (233.88-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping = 2 Features=0x8001bf AMD Features=0x400<> real memory = 67108864 (65536K bytes) avail memory = 62746624 (61276K bytes) Preloaded elf kernel "kernel" at 0xc02bd000. Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x00 on pci0.1.0 chip2: rev 0x41 on pci0.7.0 uhci0: rev 0x02 int d irq 11 on pci0.7.2 chip3: rev 0x10 on pci0.7.3 ncr0: rev 0x03 int a irq 9 on pci0.8.0 pn0: <82c169 PNIC 10/100BaseTX> rev 0x20 int a irq 11 on pci0.9.0 pn0: Ethernet address: 00:a0:cc:56:bc:7a pn0: autoneg complete, link status good (full-duplex, 100Mbps) Probing for devices on PCI bus 1: vga0: rev 0x04 int a irq 9 on pci1.5.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <6 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 flags 0x10 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface usb0: uhub0 at usb0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 100 packets/entry by default Waiting 8 seconds for SCSI devices to settle sa0 at ncr0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 8) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 16), Tagged Queueing Enabled da0: 4345MB (8899737 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Logical unit not ready, manual intervention required da1 at ncr0 bus 0 target 6 lun 0 da1: Removable Direct Access SCSI-2 device da1: 3.300MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present pn0: selecting MII, 100Mbps, half duplex pn0: selecting MII, 100Mbps, full duplex (sa0:ncr0:0:3:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. (sa0:ncr0:0:3:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. ---------------------------------------------------------------------- machine "i386" ident MORDRED maxusers 32 makeoptions DEBUG="-g" options PQ_HUGECACHE # color for 1024k/16k cache # # This directive defines a number of things: # - The compiled kernel is to be called `kernel' # - The root filesystem might be on partition wd0a # - Crash dumps will be written to wd0b, if possible. Specifying the # dump device here is not recommended. Use dumpon(8). # config kernel root on da0s2a cpu "I586_CPU" # aka Pentium(tm) options "CPU_WT_ALLOC" options "NO_F00F_HACK" options "COMPAT_43" options USER_LDT options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" options "VM86" options DDB options KTRACE options PERFMON options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG # This is good for 100Mb Ethernet, makes timing resolution decent: options HZ=1000 options INET options "TCP_COMPAT_42" #emulate 4.2BSD TCP bugs options IPFIREWALL options IPFIREWALL_VERBOSE options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options "ICMP_BANDLIM" pseudo-device ether pseudo-device loop pseudo-device bpfilter 4 pseudo-device disc options FFS #Fast filesystem options MFS #Memory File System options NFS #Network File System options NFS_NOSERVER options "CD9660" #ISO 9660 filesystem options MSDOSFS #MS DOS File System options FFS_ROOT #FFS usable as root device options SOFTUPDATES options NSWAPDEV=2 # NFS options: options "NFS_MINATTRTIMO=3" # VREG attrib cache timeout in sec options "NFS_MAXATTRTIMO=60" options "NFS_MINDIRATTRTIMO=30" # VDIR attrib cache timeout in sec options "NFS_MAXDIRATTRTIMO=60" options "NFS_GATHERDELAY=10" # Default write gather delay (msec) options "NFS_UIDHASHSIZ=29" # Tune the size of nfssvc_sock with this options "NFS_WDELAYHASHSIZ=16" # and with this options "NFS_MUIDHASHSIZ=63" # Tune the size of nfsmount with this options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" controller scbus0 #base SCSI code device da0 #SCSI direct access devices (aka disks) device sa0 #SCSI tapes device cd0 #SCSI CD-ROMs device pass0 #CAM passthrough driver # The previous devices (ch, da, st, cd) are recognized by config. # config doesn't (and shouldn't) know about these newer ones, # so we have to specify that they are on a SCSI bus with the "at scbus?" # clause. device pt0 at scbus? # SCSI processor type device sctarg0 at scbus? # SCSI target options SCSI_DELAY=8000 pseudo-device pty 16 pseudo-device speaker pseudo-device gzip options "MSGBUF_SIZE=40960" controller isa0 controller pnp0 #options "AUTO_EOI_1" #options "AUTO_EOI_2" #options "NTIMECOUNTER=20" controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts options VGA_ALT_SEQACCESS options VESA pseudo-device splash device sc0 at isa? tty options MAXCONS=6 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines device npx0 at isa? port IO_NPX iosiz 0x0 flags 0x0 irq 13 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 device sio1 at isa? port "IO_COM2" tty flags 0x10 irq 3 ## Sound: #device pcm0 at isa? port ? irq 5 drq 3 flags 0x0f #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 3 #device sbxvi0 at isa? drq 5 #device sbmidi0 at isa? port 0x330 #device opl0 at isa? port 0x388 controller pci0 controller ncr0 device de0 device pn0 controller ppbus0 device lpt0 at ppbus? device ppc0 at isa? disable port? tty irq 7 options CLK_CALIBRATION_LOOP options "CLK_USE_I8254_CALIBRATION" options CLK_USE_TSC_CALIBRATION options CLUSTERDEBUG options NBUF=512 options NMBCLUSTERS=1024 options PANIC_REBOOT_WAIT_TIME=16 options SHOW_BUSYBUFS # List buffers that prevent root unmount controller uhci0 controller usb0 device ugen0 device ukbd0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Feb 13 15:28:48 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id 194AD429D; Sun, 13 Feb 2000 15:28:35 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA05194; Mon, 14 Feb 2000 09:59:32 +1030 (CST) Date: Mon, 14 Feb 2000 09:59:32 +1030 From: Greg Lehey To: "B. Scott Michel" Cc: freebsd-hardware@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Sondy SDT-5000 SCSI tape drive problems Message-ID: <20000214095932.D2699@freebie.lemis.com> References: <38A70B73.8A5DAE1C@cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <38A70B73.8A5DAE1C@cs.ucla.edu> 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sunday, 13 February 2000 at 11:52:19 -0800, B. Scott Michel wrote: > I'm currently running FreeBSD 3.4 and finally got around to > installing a tape drive (hey, backups are good, so I'm > told... :-) I opted for installing flexbackup since I don't > need to swat gnats with sledgehammers (i.e. Amanda is too > heavy weight.) > > The problem I'm running into with the 3.4 kernel is that > it keeps complaining: > > (sa0:ncr0:0:3:0): tape is now frozen- use an OFFLINE... > > So I go off and 'mt offline', reinsert the tape, do a > 'flexbackup -newtape', only to repeat the cycle. > > What have I overlooked? The error message. What you quoted ("tape is now frozen") is a consequence of an earlier problem. FWIW, it pisses me off too. 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 Feb 15 1: 5:40 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from orbix.mobilix.dk (orbix.mobilix.dk [194.234.180.132]) by builder.freebsd.org (Postfix) with ESMTP id DCB404226 for ; Tue, 15 Feb 2000 01:05:36 -0800 (PST) Received: from ms04.mobilix.dk (ms04.mobilix.dk [172.16.1.24]) by orbix.mobilix.dk (8.9.3/8.9.3) with SMTP id KAA00729 for ; Tue, 15 Feb 2000 10:03:21 +0100 Received: FROM ms07.mobilix.dk BY ms04.mobilix.dk ; Tue Feb 15 10:05:57 2000 +0100 Received: by ms07.mobilix.dk with Internet Mail Service (5.5.2448.0) id <1FCYHNST>; Tue, 15 Feb 2000 10:05:58 +0100 Message-ID: <818F6C8F771DD211B5EA0008C7FABF4B019C0ECC@ms08.mobilix.dk> From: Nicolai Stok To: "'freebsd-hardware@freebsd.org'" Subject: Mylex Extremeraid 1100 Date: Tue, 15 Feb 2000 10:05:56 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I was told my one of our hardware suppliers that the Mylex Extremeraid 1100 (raid cointroller) was supported by FreeBSD, or atleast there should be drivers in development, is the true? Best regards Nicolai B. Stok Newsmaster Mobilix Internet phone +45 8233 7000 fax +45 8233 7009 http://www.mobilix.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Feb 15 9:56:18 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from thud.tbe.net (thud.tbe.net [209.123.109.174]) by builder.freebsd.org (Postfix) with ESMTP id 0ADA04D3F for ; Tue, 15 Feb 2000 09:51:37 -0800 (PST) Received: by thud.tbe.net (Postfix, from userid 1001) id AC1601C9516; Tue, 15 Feb 2000 12:51:41 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by thud.tbe.net (Postfix) with ESMTP id A6AADDCF4D; Tue, 15 Feb 2000 12:51:41 -0500 (EST) Date: Tue, 15 Feb 2000 12:51:41 -0500 (EST) From: "Gary D. Margiotta" To: freebsd-hardware@freebsd.org Cc: "Gary D. Margiotta" Subject: Diamond suprasonic II 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 Anyone here ever use this modem? I'm considering it, as I have gotten normal PPP multilink working, and I'd like to only take up 1 slot as opposed to 2... My router/dialup box is currently running 3.4-RELEASE, and I have a couple external USR's on it now. Any response would be useful... and please mail direct as I'm not on this particular list. Thanks! -Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Feb 15 18:25: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by builder.freebsd.org (Postfix) with ESMTP id 227BB423D for ; Tue, 15 Feb 2000 18:16:54 -0800 (PST) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id VAA54615; Tue, 15 Feb 2000 21:13:39 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp.simianscience.com (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id VAA23374; Tue, 15 Feb 2000 21:13:38 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: NST@Mobilix.dk (Nicolai Stok) Cc: freebsd-hardware@freebsd.org Subject: Re: Mylex Extremeraid 1100 Date: Wed, 16 Feb 2000 02:12:34 GMT Message-ID: <38aa0749.791808660@mail.sentex.net> References: In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15 Feb 2000 04:06:14 -0500, in sentex.lists.freebsd.hardware you wrote: >Hi > >I was told my one of our hardware suppliers that the Mylex Extremeraid 1100 >(raid cointroller) was supported by FreeBSD, or atleast there should be >drivers in development, is the true? Maybe... go to www.dejanews.com. Go to power search, for the forums, enter in mailing.freebsd.*,muc.lists.freebsd.*,comp.unix.bsd.freebsd.* keywords, raid, mylex. No doubt you will find reference to http://www.freebsd.org/~msmith/RAID for 3.x 4.x has it integrated into the source tree. ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Feb 15 23: 3: 0 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ma.ks.edu.tw (ma.ks.edu.tw [163.16.1.6]) by builder.freebsd.org (Postfix) with ESMTP id B50A0400E for ; Tue, 15 Feb 2000 23:02:56 -0800 (PST) Received: from ma.ks.edu.tw (tnt2-178.ks.edu.tw [163.16.4.188]) by ma.ks.edu.tw (8.9.1/8.9.1) with ESMTP id OAA02305 for ; Wed, 16 Feb 2000 14:49:43 +0800 Message-ID: <38AA4E0A.7EBBDC16@ma.ks.edu.tw> Date: Wed, 16 Feb 2000 15:13:14 +0800 From: kemmy X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Waiting 15s for SCSI devices to settle Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My computer hangs here waiting for SCSI devices to settle. It boots ok on FreeBSD 3.0 SNAPSHOT but fails to boot here on FreeBSD 3.4. I have a Tekram SCSI card(DC390F) and a SCSI disk and 2 SCSI cds. The two scsi cds show ready lights but the kernel don't go on. It shows messages like this: ncr0 :timed out .... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Feb 16 9:10: 6 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 5DBF937B50D for ; Wed, 16 Feb 2000 09:10:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (castles549.castles.com [208.214.165.113]) by builder.freebsd.org (Postfix) with ESMTP id E6D04132DE for ; Wed, 16 Feb 2000 09:09:24 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA03514; Tue, 15 Feb 2000 18:55:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002160255.SAA03514@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mike@sentex.net (Mike Tancsa) Cc: NST@Mobilix.dk (Nicolai Stok), freebsd-hardware@freebsd.org Subject: Re: Mylex Extremeraid 1100 In-reply-to: Your message of "Wed, 16 Feb 2000 02:12:34 GMT." <38aa0749.791808660@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Feb 2000 18:55:43 -0800 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Be aware that we have issues in the 4.0 pre-release phase with booting from this controller; I believe we've seen that fixed today and am just waiting for clearance to commit the relevant changes. > On 15 Feb 2000 04:06:14 -0500, in sentex.lists.freebsd.hardware you wrote: > > >Hi > > > >I was told my one of our hardware suppliers that the Mylex Extremeraid 1100 > >(raid cointroller) was supported by FreeBSD, or atleast there should be > >drivers in development, is the true? > > Maybe... go to > > www.dejanews.com. Go to power search, for the forums, enter in > > mailing.freebsd.*,muc.lists.freebsd.*,comp.unix.bsd.freebsd.* > > keywords, raid, mylex. No doubt you will find reference to > > http://www.freebsd.org/~msmith/RAID > > for 3.x > > 4.x has it integrated into the source tree. > > ---Mike > Mike Tancsa (mdtancsa@sentex.net) > Sentex Communications Corp, > Waterloo, Ontario, Canada > "Given enough time, 100 monkeys on 100 routers > could setup a national IP network." (KDW2) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Feb 16 11:55: 2 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 8FD5B37B55D for ; Wed, 16 Feb 2000 11:54:59 -0800 (PST) (envelope-from bob@luke.immure.com) Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by builder.freebsd.org (Postfix) with ESMTP id A4116132ED for ; Wed, 16 Feb 2000 11:54:20 -0800 (PST) Received: (from bob@localhost) by luke.immure.com (8.9.3/8.9.3) id NAA53246 for freebsd-hardware@freebsd.org; Wed, 16 Feb 2000 13:54:55 -0600 (CST) (envelope-from bob) Date: Wed, 16 Feb 2000 13:54:55 -0600 From: Bob Willcox To: freebsd-hardware@freebsd.org Subject: Supermicro PIIIDM3 MB won't boot 4.0-current kernel Message-ID: <20000216135455.A53006@luke.immure.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All, I just received a Supermicro PIIIDM3 motherboard (they just became available) that 4.0-current will not boot on. This is a brand new board using the Intel 840 chipset (also has two 3.3v, 64-bit PCI slots, which is why I needed it). Attempting to boot the 4.0-20000214-CURRENT snapshot floppies causes it to panic with the following screen output: -------------------------------------------------------------------------------- Booting [kernel] ... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supperfisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xc05f9ffc frame pointer = 0x10:0x0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = Idle interrupt mask = net tty bio cam trap number = 12 panic: page fault -------------------------------------------------------------------------------- Though this is a dual cpu MB I only have one processor plugged into it (533MHz PIII). I would greatly appreciate any suggestions and/or pointers on where to go next. I have also tried booting some older -current kernels, but they also fail (though the 4.0-20000210-CURRENT snapshot kernel quickly reboots rather than panicing). Thanks in advance, Bob -- Bob Willcox The infliction of cruelty with a good conscience bob@immure.com is a delight to moralists. That is why they Austin, TX invented hell. -- Bertrand Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 17 11: 6:18 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from menalto.com (m206-35.dsl.tsoft.com [198.144.206.35]) by hub.freebsd.org (Postfix) with ESMTP id 619AA37B7AF for ; Thu, 17 Feb 2000 11:06:15 -0800 (PST) (envelope-from bharat@menalto.com) Received: from firebrand (firebrand [10.0.0.7]) by menalto.com (8.9.3/8.9.3) with SMTP id LAA18278 for ; Thu, 17 Feb 2000 11:06:20 -0800 (PST) (envelope-from bharat@menalto.com) From: "Bharat Mediratta" To: Subject: OnStream 3Gb IDE tape drive Date: Thu, 17 Feb 2000 11:06:11 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Howdy. I hear that there has been little or no progress on the SCSI front for the OnStream drives. However, I see that OnStream has released beta drivers for the Linux platform. Is there any status on the IDE front for these drives? I just bought one and have 28 days left to return it if I can't use it on my FreeBSD box :-) -Bharat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 17 12: 6:28 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 9D6B337B7DC for ; Thu, 17 Feb 2000 12:06:24 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00690; Thu, 17 Feb 2000 12:17:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002172017.MAA00690@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nicolai Stok Cc: "'freebsd-hardware@freebsd.org'" Subject: Re: Mylex Extremeraid 1100 In-reply-to: Your message of "Tue, 15 Feb 2000 10:05:56 +0100." <818F6C8F771DD211B5EA0008C7FABF4B019C0ECC@ms08.mobilix.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Feb 2000 12:17:46 -0800 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi > > I was told my one of our hardware suppliers that the Mylex Extremeraid 1100 > (raid cointroller) was supported by FreeBSD, or atleast there should be > drivers in development, is the true? This is correct; it will be supported in FreeBSD 4.0 -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message