From owner-freebsd-hardware Mon Oct 5 01:18:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29891 for freebsd-hardware-outgoing; Mon, 5 Oct 1998 01:18:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29886 for ; Mon, 5 Oct 1998 01:18:30 -0700 (PDT) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id SAA24223; Mon, 5 Oct 1998 18:17:40 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma024215; Mon, 5 Oct 98 18:17:17 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id SAA01288; Mon, 5 Oct 1998 18:17:17 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id SAA11598; Mon, 5 Oct 1998 18:17:16 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id SAA21031; Mon, 5 Oct 1998 18:17:15 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199810050817.SAA21031@nymph.dtir.qld.gov.au> To: "Duncan Barclay" cc: freebsd-hardware@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: Exabyte 8200 References: <199810021421.HAA01170@mailgate.cadence.com> In-Reply-To: <199810021421.HAA01170@mailgate.cadence.com> from "Duncan Barclay" at "Fri, 02 Oct 1998 15:21:23 +0000" Date: Mon, 05 Oct 1998 18:17:14 +1000 From: Stephen McKay Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 2nd October 1998, "Duncan Barclay" wrote: >> As I recal, the only real problem with a Cybernetic tape drive is >> the compression is vendor unique. > >Doesn't matter as it's for home use. And I only need to back up a >gigabyte or so. I would dispute this. Your cheap custom tape drive is likely to expire before your disk, and then you are left with a pile of unreadable backups. Write uncompressed tapes, and use software compression if you want to save time/space. Then you at least have the option of recovering your files at work if, say, a burglar takes a liking to your backup device. Stephen. PS Every time I post about Exabytes I ask if anyone knows how to query one about its error rate (or other head cleaning related notifications). No, I can't find this on the Exabyte site, and yes, I've looked. I would be happy to be proven an idiot by being given an URL showing actual information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 5 01:32:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01774 for freebsd-hardware-outgoing; Mon, 5 Oct 1998 01:32:25 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01725 for ; Mon, 5 Oct 1998 01:32:17 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id BAA11803; Mon, 5 Oct 1998 01:31:42 -0700 (PDT) Message-Id: <199810050831.BAA11803@mailgate.cadence.com> Received: from symnt3.cadence.com(194.32.101.100) by mailgate.cadence.com via smap (mjr-v1.2) id xma907576301.011790; Mon, 5 Oct 98 01:31:41 -0700 Received: from pc287-cam.cadence.com (d194032096136.Cadence.COM [194.32.96.136]) by symnt3.Cadence.COM with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id Q4J1BZW6; Mon, 5 Oct 1998 09:32:01 +0100 Comments: Authenticated sender is From: "Duncan Barclay" To: Stephen McKay Date: Mon, 5 Oct 1998 09:31:21 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Exabyte 8200 Reply-to: dmlb@ragnet.demon.co.uk CC: freebsd-hardware@FreeBSD.ORG In-reply-to: <199810050817.SAA21031@nymph.dtir.qld.gov.au> References: <199810021421.HAA01170@mailgate.cadence.com> from "Duncan Barclay" at "Fri, 02 Oct 1998 15:21:23 +0000" X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Friday, 2nd October 1998, "Duncan Barclay" wrote: > > >> As I recal, the only real problem with a Cybernetic tape drive is > >> the compression is vendor unique. > > > >Doesn't matter as it's for home use. And I only need to back up a > >gigabyte or so. > > I would dispute this. Your cheap custom tape drive is likely to > expire before your disk, and then you are left with a pile of > unreadable backups. Write uncompressed tapes, and use software > compression if you want to save time/space. Then you at least have > the option of recovering your files at work if, say, a burglar takes > a liking to your backup device. Sorry, I think I meant to say: Doesn't matter as it's for home use. And I only need to back up a gigabyte or so, and I probably won't bother with compression. Compression on backup tapes always seems like a bad idea to me in case something goes wrong, i.e. corruption of the dictionary etc. > Stephen. > > PS Every time I post about Exabytes I ask if anyone knows how to > query one about its error rate (or other head cleaning related > notifications). No, I can't find this on the Exabyte site, and yes, > I've looked. I would be happy to be proven an idiot by being given > an URL showing actual information. I didn't see anything related to this either. I think I may have seen it on a DejaNews searches I did, and I may have saved it a home. I will dig it up tonight if I can. Duncan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 5 09:50:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08926 for freebsd-hardware-outgoing; Mon, 5 Oct 1998 09:50:59 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA07834 for ; Mon, 5 Oct 1998 09:47:27 -0700 (PDT) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id MAA21040; Mon, 5 Oct 1998 12:46:27 -0400 Date: Mon, 5 Oct 1998 12:46:27 -0400 (EDT) From: Jamie Bowden To: Duncan Barclay cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Exabyte 8200 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 Thu, 1 Oct 1998, Duncan Barclay wrote: > Hi > > I've have just picked up a Exabyte 8200 from a fire sale at work (almost free). > This appears to be fine for use at home and as something is better than nothing > when it comes to backups. > > I wonder if anyone can help me out on working out how > to use it/point me to manuals? It seems to be working, although I haven't got > any tapes in it yet, it probes fine etc. > > The model I have has an LCD panel over the drive door. When the drive powers up > it asks me to select a compression mode, there is a small round button on the > LCD which toggles a little "C" on the LCD, next to a "2". There is also an > extra card plugged into the SCSI connector which I think controls the LCD. > > This model doesn'y seem to be a standard Exabyte model and markings on the > chassis don't tell me much. > > I'm going to try and get manuals from work (but they may be in the bin...) > > Any suggestions as to which brands of tape are good/bad etc. I only need to > back up a few hundred meg. on it at home (everything else is on CDs or CVSup!) Got a model # on the chassis anywhere? I have an 8505 with similar features, which is actually a Contemporary Cybernetics chassis built around an exabyte mechanism. Jamie Bowden -- Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 5 14:05:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01671 for freebsd-hardware-outgoing; Mon, 5 Oct 1998 14:05:27 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bvainc.com (mail1.bvainc.com [208.145.185.197]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA01657 for ; Mon, 5 Oct 1998 14:05:23 -0700 (PDT) (envelope-from SWorthington@hsag.com) Received: from BVA-Message_Server by bvainc.com with Novell_GroupWise; Mon, 05 Oct 1998 13:43:10 -0700 Message-Id: X-Mailer: Novell GroupWise 5.2 Date: Mon, 05 Oct 1998 13:43:28 -0700 From: "Scott Worthington" To: hardware@FreeBSD.ORG Cc: SteveFriedrich@hot-shot.com Subject: Problem with Adaptec AHA-2940xx Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 04 Oct 1998, Steve Friedrich wrote: >>Okay the culprit was the AMI BIOS! > >How did you jump to this conclusion?? You're using a different motherboard too. It was not a jump, more like a skip. Both motherboards use the same chipset (VIA). The PA-2007 is a AT mainboard whilst the PA-2011 is an ATX mainboard. > >>I went to www.fic.com.tw and downloaded the latest >>_AWARD_ BIOS for the FIC PA-2011 motherboard... >>and PRESTO, she works! > >I've never heard of a moboard manufacturer offering multiple >BIOSes for their moboards. Did FIC switch to Award because of >problems with AMI?? Have you reported your findings to FIC and AMI?? Perhaps FIC did have a problem? I don't know. I only know that for this mainboard, both AMI and Award are available for flash. And I know that changing to Award solved the frustrating 'waiting for scsi to settle' crash. Does anyone know the direct e-mail to a developer at FIC or AMI? I'd be glad to share the information. Again, I hope this find helps others who run into the 'waiting for scsi to settle' problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 5 15:35:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18970 for freebsd-hardware-outgoing; Mon, 5 Oct 1998 15:35:46 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18923 for ; Mon, 5 Oct 1998 15:35:34 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id XAA00602; Mon, 5 Oct 1998 23:35:19 +0100 (BST) Date: Mon, 5 Oct 1998 23:35:19 +0100 (BST) From: Karl Pielorz To: Scott Worthington cc: hardware@FreeBSD.ORG, SteveFriedrich@hot-shot.com Subject: Re: Problem with Adaptec AHA-2940xx 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 Mon, 5 Oct 1998, Scott Worthington wrote: > Again, I hope this find helps others who run into the 'waiting for > scsi to settle' problem. Hi, Is this the problem whereby 'certain' machines with 'certain' aha2940's just sit there 'waiting for scsi to settle' (which if you leave them for like up to half an hour turns into errors like "board not responding" etc.?) I got caught with this one a while ago - and posted all my findings to the list (in a kind of summary)... If I dig them out - maybe we should pool them - do you have the board revisions / BIOS's on the Adaptec's etc. as well? Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 5 17:30:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15359 for freebsd-hardware-outgoing; Mon, 5 Oct 1998 17:30:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bvainc.com (mail1.bvainc.com [208.145.185.197]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA15179 for ; Mon, 5 Oct 1998 17:29:51 -0700 (PDT) (envelope-from SWorthington@hsag.com) Received: from BVA-Message_Server by bvainc.com with Novell_GroupWise; Mon, 05 Oct 1998 16:57:08 -0700 Message-Id: X-Mailer: Novell GroupWise 5.2 Date: Mon, 05 Oct 1998 16:52:36 -0700 From: "Scott Worthington" To: kpielorz@tdx.co.uk Cc: hardware@FreeBSD.ORG, SteveFriedrich@hot-shot.com Subject: Re: Problem with Adaptec AHA-2940xx -Reply Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA15190 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Pooling is an excellent idea. I have two AHA-2940UW boards, one "born-on" circa 1996 and the other "born-on" July 1998. The 1996 board shipped with 1.25, the 1998 with 1.34.3. So I have two test boards plus two 2940UA with a BIOS version (erg, I forgot it's version). Plus access to a FIC PA-2007 with Award BIOS, Two FIC PA-2011 with BIOS that I can switch from AMI to Award, and access to Dell (Pentium, Pentium Pro, Pentium II). I can bounce the card around to various machines, boot the FreeBSD / Linux Slackware boot-floppy and note the various problems. I noted my solution to my FIC PA-2011, and hopefully I have helped reduce some stress somewhere. Creating a Adaptec / Mainboard compatibility FAQ with all the details would be excellent--reducing the "waiting for scsi to settle" confusion. Interestingly, I found this problem to be the same with Linux, but I did not find any discussions of it through searching the www.dejanews.com archive. How many months are archived and searchable, I wonder? Great idea, what is your proposed next step? Tonight I will try upgrading my AHA-2940UW (that works as downgraded to 1.25) back to its 1.34.3 shipped version. (I just hate flashing, I hope it goes smoothly and the UPS holds on). I will note the problems and solutions with that flash. >>> Karl Pielorz October 5, 1998 3:35 pm >>> On Mon, 5 Oct 1998, Scott Worthington wrote: > Again, I hope this find helps others who run into the 'waiting for > scsi to settle' problem. Hi, Is this the problem whereby 'certain' machines with 'certain' aha2940's just sit there 'waiting for scsi to settle' (which if you leave them for like up to half an hour turns into errors like "board not responding" etc.?) I got caught with this one a while ago - and posted all my findings to the list (in a kind of summary)... If I dig them out - maybe we should pool them - do you have the board revisions / BIOS's on the Adaptec's etc. as well? Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 6 01:06:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27782 for freebsd-hardware-outgoing; Tue, 6 Oct 1998 01:06:24 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from www.in-design.com (www.in-design.com [206.210.93.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27762; Tue, 6 Oct 1998 01:06:20 -0700 (PDT) (envelope-from nero@in-design.com) Received: from www.in-design.com (nero@www.in-design.com [206.210.93.16]) by www.in-design.com (8.8.7/8.8.5) with SMTP id EAA06308; Tue, 6 Oct 1998 04:06:18 -0400 (EDT) Date: Tue, 6 Oct 1998 04:06:18 -0400 (EDT) From: God To: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Question about NCR driver / SCSI Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all; I have an NCR SDMS V3.0 PCI SCSI adaptor. This is a wide deffrential adaptor it is connected to a 9 gig Seagate Barracuda ST19171WD drive The SCSI card bois notices the drive, but then when fbsd loads up, the following error messages are generated: ncr0: script cmd = 72060000 ncr0: regdump: da 00 80 03 47 00 0d 07 31 08 0c 00 80 00 09 02. ncr0: have to clear fifos. (ncr0:13:0): 8 parity error(s), fallback. (ncr0:13:0): COMMAND FAILED (ff 62) @f2593c00. ncr0:0: ERROR (81:1) (8-0-8000) (0/3) @ (mem 340c28:00000000). ncr0: regdump: da 00 c0 03 47 00 0d 07 31 08 0c 00 80 00 09 02. This error message is repeated about 20 times. First I was wondering if there is a way I can fix this? And ofcourse how to fix it? Thanks alot in advance. Cheers Tamer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 6 11:19:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09413 for freebsd-hardware-outgoing; Tue, 6 Oct 1998 11:19:45 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA09407; Tue, 6 Oct 1998 11:19:41 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA06850; Tue, 6 Oct 1998 17:18:35 +0100 From: Luigi Rizzo Message-Id: <199810061618.RAA06850@labinfo.iet.unipi.it> Subject: Re: 2nd call for testers for RealTek 8139 driver To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Tue, 6 Oct 1998 17:18:35 +0100 (MET) Cc: hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG In-Reply-To: <199809292311.TAA12549@skynet.ctr.columbia.edu> from "Bill Paul" at Sep 29, 98 07:11:31 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This is another call for testers for the RealTek 8139 fast ethernet > driver. So far I have only gotten one (1) response to my first call ... ok, adapting the driver to do bridging was not that hard but now i seem unable to deal with pkts larger than a few bytes (an mbuf i think): ping -s 80 does not seem to go through, whereas regular pings work. I am not sure what is the problem and now it is too late to investigate more. In any case my diffs are as follows, in case they suggest something. cheers luigi --- if_rl.c.orig Tue Oct 6 17:29:40 1998 +++ if_rl.c Tue Oct 6 18:09:03 1998 @@ -121,6 +121,10 @@ #include #endif +#ifdef BRIDGE +#include +#endif + #include /* for vtophys */ #include /* for vtophys */ #include /* for DELAY */ @@ -1407,6 +1411,9 @@ eh = mtod(m, struct ether_header *); ifp->if_ipackets++; + m->m_pkthdr.len = m->m_len = total_len; + m->m_pkthdr.rcvif = ifp; /* XXX */ + #if NBPFILTER > 0 /* * Handle BPF listeners. Let the BPF user see the packet, but @@ -1414,18 +1421,36 @@ * a broadcast packet, multicast packet, matches our ethernet * address or the interface is in promiscuous mode. */ - if (ifp->if_bpf) { - m->m_pkthdr.len = m->m_len = total_len; + if (ifp->if_bpf) bpf_mtap(ifp, m); +#endif +#ifdef BRIDGE + if (do_bridge) { + struct ifnet *bdg_ifp ; + bdg_ifp = bridge_in(m); + if (bdg_ifp == BDG_DROP) + goto dropit; + else { + if (bdg_ifp != BDG_LOCAL) + bdg_forward(&m, bdg_ifp); + if (!m) + goto dropit ; + if (bdg_ifp == BDG_LOCAL || bdg_ifp == BDG_BCAST || + bdg_ifp == BDG_MCAST) + goto getit ; + else if (m) + goto dropit ; + } + } else +#endif if (ifp->if_flags & IFF_PROMISC && (bcmp(eh->ether_dhost, sc->arpcom.ac_enaddr, - ETHER_ADDR_LEN) && - (eh->ether_dhost[0] & 1) == 0)) { + ETHER_ADDR_LEN) && (eh->ether_dhost[0] & 1) == 0)) { +dropit: m_freem(m); continue; } - } -#endif +getit: /* Remove header from mbuf and pass it on. */ m_adj(m, sizeof(struct ether_header)); ether_input(ifp, eh, m); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 6 15:01:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07308 for freebsd-hardware-outgoing; Tue, 6 Oct 1998 15:01:21 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from vespucci.advicom.net (vespucci.advicom.net [199.170.120.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07086; Tue, 6 Oct 1998 15:00:28 -0700 (PDT) (envelope-from avalon@advicom.net) Received: from advicom.net (dyn-u1-8.advicom.net [165.113.131.8] (may be forged)) by vespucci.advicom.net (8.8.8/8.8.5) with ESMTP id RAA08025; Tue, 6 Oct 1998 17:00:20 -0500 (CDT) X-Envelope-Recipient: freebsd-hardware@freebsd.org Message-ID: <361A92E1.B77BBF4B@advicom.net> Date: Tue, 06 Oct 1998 17:00:01 -0500 From: Avalon Books Organization: Avalon Books X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: 16C650 UART Support Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does any have detailed information about enabling 16C650 UART support in 2.2.6R? I have a Boca IO650 with dual ST16C650 UART's, and I need to eliminate the I/O bottleneck out to my ISDN TA. Hitting 230.4 kbps would be nice... So... Which files I do alter, and what are the alterations? Or is there a separate driver for 16C650-based cards (and if so, where do I find it)? Is there already support for baud rates above 115.2 kbps? Or do I need to add support? And if so, how? You get the idea... --Rick Pelletier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 6 18:52:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28911 for freebsd-hardware-outgoing; Tue, 6 Oct 1998 18:52:11 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28875; Tue, 6 Oct 1998 18:51:43 -0700 (PDT) (envelope-from dmaddox@scsn.net) Received: from rhiannon.scsn.net ([209.12.57.57]) by mail.scsn.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-41950U6000L1100S0) with ESMTP id AAA142; Tue, 6 Oct 1998 21:42:20 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.9.1/8.9.1) id VAA00444; Tue, 6 Oct 1998 21:52:13 GMT (envelope-from root) Message-ID: <19981006215213.A318@scsn.net> Date: Tue, 6 Oct 1998 21:52:13 +0000 From: dmaddox@scsn.net (Donald J. Maddox) To: Avalon Books , freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: 16C650 UART Support Reply-To: dmaddox@scsn.net References: <361A92E1.B77BBF4B@advicom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <361A92E1.B77BBF4B@advicom.net>; from Avalon Books on Tue, Oct 06, 1998 at 05:00:01PM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 06, 1998 at 05:00:01PM -0500, Avalon Books wrote: > Does any have detailed information about enabling 16C650 UART support > in 2.2.6R? I have a Boca IO650 with dual ST16C650 UART's, and I need to > eliminate the I/O bottleneck out to my ISDN TA. Hitting 230.4 kbps would > be nice... > So... > Which files I do alter, and what are the alterations? Or is there a > separate driver for 16C650-based cards (and if so, where do I find it)? > Is there already support for baud rates above 115.2 kbps? Or do I need > to add support? And if so, how? > You get the idea... I believe the 16650-specific stuff just requires that you set the 0x20000 bit in the sio flags, like this: device sio2 at isa? port "IO_COM3" tty flags 0x20000 irq 12 vector siointr There are some other interesting bits in there, too... Just take a look at sio.c. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 00:20:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00454 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 00:20:16 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from redfish.go2net.com (redfish.go2net.com [207.178.55.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA00362 for ; Wed, 7 Oct 1998 00:20:06 -0700 (PDT) (envelope-from marcs@go2net.com) Received: from marcs by redfish.go2net.com with smtp (Exim 1.82 #2) id 0zQnsA-0001lR-00; Wed, 7 Oct 1998 00:18:58 -0700 Date: Wed, 7 Oct 1998 00:18:58 -0700 (PDT) From: Marc Slemko X-Sender: marcs@redfish To: hardware@FreeBSD.ORG Subject: Lite-On PNIC (fwd) 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 For anyone interested; from an OpenBSD mailing list. It would be happiness if such small changes were indeed all that is required. ---------- Forwarded message ---------- Date: Wed, 7 Oct 1998 01:59:49 -0400 (EDT) From: jason@thought.net To: tech@openbsd.org Subject: Lite-On PNIC What follows are the diffs for /sys/dev/pci/{if_de.c,if_devar.h} to support the Lite-On PNIC. I'm not sure about the marketing, but the box this card came in said "Netgear FA310TX rev D1", and I've been told that newer Kingston? boards use this same chip set. I need testers, and I'd like for someone more familiar with if_de to tell me if I'm doing things all wrong or not =) The card works, but it seems to have trouble with manually setting the media type. If you have a board that probes as "Lite-On PNIC", please give this patch a try and let me know your results as soon as possible. --Jason Wright Index: if_de.c =================================================================== RCS file: /cvs/src/sys/dev/pci/if_de.c,v retrieving revision 1.34 diff -u -r1.34 if_de.c --- if_de.c 1998/09/09 04:05:36 1.34 +++ if_de.c 1998/10/07 05:51:39 @@ -140,6 +140,7 @@ #endif #include #include +#include #include #define DEVAR_INCLUDE "dev/pci/if_devar.h" #endif /* __NetBSD__ */ @@ -193,6 +194,9 @@ static void tulip_ifmedia_status(struct ifnet * const ifp, struct ifmediareq *req); #endif /* static void tulip_21140_map_media(tulip_softc_t *sc); */ +static void tulip_pnic_media_probe(tulip_softc_t * const); +static void tulip_identify_pnic_nic(tulip_softc_t * const); +static void tulip_pnic_media_preset(tulip_softc_t * const); static void tulip_timeout_callback( @@ -720,7 +724,8 @@ * If we really transmitted a packet, then that's the media we'll use. */ if (event == TULIP_MEDIAPOLL_TXPROBE_OK || event == TULIP_MEDIAPOLL_LINKPASS) { - if (event == TULIP_MEDIAPOLL_LINKPASS) + if (event == TULIP_MEDIAPOLL_LINKPASS && + sc->tulip_chipid != TULIP_LC82C168) sc->tulip_probe_media = TULIP_MEDIA_10BASET; #if defined(TULIP_DEBUG) else @@ -1281,6 +1286,17 @@ "ICS 1890" #endif }, + { 0x78100000, 0, /* 00-A0-CC */ + { + { 0x14, 0x0800, 0x0000 }, /* 10TX */ + { 0x14, 0x0800, 0x0800 }, /* 100TX */ + { }, /* 100T4 */ + { 0x14, 0x1000, 0x1000 }, /* FULL_DUPLEX */ + }, +#if defined(TULIP_DEBUG) + "LEVEL1 LXT970" +#endif + }, { 0 } }; @@ -1871,6 +1887,31 @@ tulip_2114x_media_preset, }; +static void +tulip_pnic_media_probe(sc) + tulip_softc_t * const sc; +{ + /* Media probe is actually handled by tulip_identify_pnic_nic */ + sc->tulip_media = TULIP_MEDIA_UNKNOWN; +} + +static void +tulip_pnic_media_preset(sc) + tulip_softc_t * const sc; +{ + TULIP_CSR_WRITE(sc, csr_command, + sc->tulip_cmdmode | TULIP_CMD_PORTSELECT); + DELAY(10); +} + +static const tulip_boardsw_t tulip_pnic_boardsw = { + TULIP_21040, + tulip_pnic_media_probe, + tulip_media_select, + tulip_media_poll, + tulip_pnic_media_preset, +}; + /* * ******** END of chip-specific handlers. *********** */ @@ -2033,6 +2074,21 @@ unsigned csr = TULIP_CSR_READ(sc, csr_srom_mii) & (MII_RD|MII_DOUT|MII_CLK); unsigned data; + if (sc->tulip_chipid == TULIP_LC82C168) { + u_int32_t v; + int tmout = 1000; + + TULIP_CSR_WRITE(sc, csr_20, (MII_RDCMD << 28) | + (devaddr << 23) | + (regno << 18)); + do { + if (!((v = TULIP_CSR_READ(sc, csr_20)) & 0x80000000)) + return (v & 0xffff); + } while (--tmout); + printf("Timeout reading from PHY\n"); + return 0xffff; + } + csr &= ~(MII_RD|MII_CLK); MII_EMIT; tulip_mii_writebits(sc, MII_PREAMBLE, 32); tulip_mii_writebits(sc, MII_RDCMD, 8); @@ -2055,7 +2111,21 @@ unsigned regno, unsigned data) { - unsigned csr = TULIP_CSR_READ(sc, csr_srom_mii) & (MII_RD|MII_DOUT|MII_CLK); + unsigned csr; + + if (sc->tulip_chipid == TULIP_LC82C168) { + int tmout = 1000; + + TULIP_CSR_WRITE(sc, csr_20, (MII_WRCMD << 28) | + (devaddr << 23) | (regno << 18) | data); + do { + if (! (TULIP_CSR_READ(sc, csr_20) & 0x8000000)) + return; + } while (--tmout); + return; + } + + csr = TULIP_CSR_READ(sc, csr_srom_mii) & (MII_RD|MII_DOUT|MII_CLK); csr &= ~(MII_RD|MII_CLK); MII_EMIT; tulip_mii_writebits(sc, MII_PREAMBLE, 32); tulip_mii_writebits(sc, MII_WRCMD, 8); @@ -2311,6 +2381,49 @@ } static void +tulip_identify_pnic_nic( + tulip_softc_t * const sc) +{ + tulip_media_info_t *mi = sc->tulip_mediainfo; + int idx; + + strcpy(sc->tulip_boardid, "Lite-On "); + mi->mi_type = TULIP_MEDIAINFO_MII; + mi->mi_gpr_length = 0; + mi->mi_gpr_offset = 0; + mi->mi_reset_length = 0; + mi->mi_reset_offset = 0;; + mi->mi_phyaddr = TULIP_MII_NOPHY; + for (idx = 20; idx > 0 && mi->mi_phyaddr == TULIP_MII_NOPHY; idx--) { + DELAY(10000); + mi->mi_phyaddr = tulip_mii_get_phyaddr(sc, 0); + } + if (mi->mi_phyaddr == TULIP_MII_NOPHY) { + printf(TULIP_PRINTF_FMT ": can't find phy 0\n", TULIP_PRINTF_ARGS); + return; + } + + sc->tulip_features |= TULIP_HAVE_MII | TULIP_HAVE_POWERMGMT; + mi->mi_capabilities = PHYSTS_10BASET | PHYSTS_10BASET_FD | + PHYSTS_100BASETX | PHYSTS_100BASETX_FD; + mi->mi_advertisement = PHYSTS_10BASET | PHYSTS_10BASET_FD | + PHYSTS_100BASETX | PHYSTS_100BASETX_FD; + mi->mi_full_duplex = PHYSTS_10BASET_FD | PHYSTS_100BASETX_FD; + mi->mi_tx_threshold = PHYSTS_10BASET | PHYSTS_10BASET_FD; + TULIP_MEDIAINFO_ADD_CAPABILITY(sc, mi, 100BASETX_FD); + TULIP_MEDIAINFO_ADD_CAPABILITY(sc, mi, 100BASETX); + TULIP_MEDIAINFO_ADD_CAPABILITY(sc, mi, 10BASET_FD); + TULIP_MEDIAINFO_ADD_CAPABILITY(sc, mi, 10BASET); + mi->mi_phyid = (tulip_mii_readreg(sc, mi->mi_phyaddr, PHYREG_IDLOW) << 16) | + tulip_mii_readreg(sc, mi->mi_phyaddr, PHYREG_IDHIGH); + + TULIP_CSR_WRITE(sc, csr_15, 0x00000001); + TULIP_CSR_WRITE(sc, csr_12, 0x00000032); + TULIP_CSR_WRITE(sc, csr_23, 0x0201b07a); + sc->tulip_cmdmode = 0x812C0000; +} + +static void tulip_identify_asante_nic( tulip_softc_t * const sc) { @@ -2732,6 +2845,7 @@ { tulip_identify_cogent_nic, { 0x00, 0x00, 0x92 } }, { tulip_identify_asante_nic, { 0x00, 0x00, 0x94 } }, { tulip_identify_accton_nic, { 0x00, 0x00, 0xE8 } }, + { tulip_identify_pnic_nic, { 0x00, 0xA0, 0xCC } }, { NULL } }; @@ -2773,6 +2887,21 @@ sc->tulip_rombuf[idx] = TULIP_CSR_READBYTE(sc, csr_enetrom); sc->tulip_boardsw = &tulip_21040_boardsw; #endif /* TULIP_EISA */ + } else if (sc->tulip_chipid == TULIP_LC82C168) { + for (idx = 0; idx < 3; idx++) { + int tmout = 10000; + TULIP_CSR_WRITE(sc, csr_19, 0x600 | idx); + while ((csr = TULIP_CSR_READ(sc, csr_9)) & 0x80000000 && --tmout); + if (!tmout) + return -1; + sc->tulip_rombuf[idx * 2] = (csr >> 8) & 0xff; + sc->tulip_enaddr[idx * 2] = (csr >> 8) & 0xff; + sc->tulip_rombuf[(idx * 2) + 1] = csr & 0xff; + sc->tulip_enaddr[(idx * 2) + 1] = csr & 0xff; + } + sc->tulip_boardsw = &tulip_pnic_boardsw; + sc->tulip_features |= TULIP_HAVE_OKROM; + goto check_oui; } else { if (sc->tulip_chipid == TULIP_21041) { /* @@ -4825,6 +4954,9 @@ sc->tulip_csrs.csr_13 = csr_base + 13 * csr_size; sc->tulip_csrs.csr_14 = csr_base + 14 * csr_size; sc->tulip_csrs.csr_15 = csr_base + 15 * csr_size; + sc->tulip_csrs.csr_19 = csr_base + 19 * csr_size; /* PNIC */ + sc->tulip_csrs.csr_20 = csr_base + 20 * csr_size; /* PNIC */ + sc->tulip_csrs.csr_23 = csr_base + 23 * csr_size; /* PNIC */ #if defined(TULIP_EISA) sc->tulip_csrs.csr_enetrom = csr_base + DE425_ENETROM_OFFSET; #endif @@ -5124,6 +5256,12 @@ { struct pci_attach_args *pa = (struct pci_attach_args *) aux; + if (PCI_VENDORID(pa->pa_id) == PCI_VENDOR_LITEON) { + if (PCI_CHIPID(pa->pa_id) == PCI_PRODUCT_LITEON_PNIC) + return 1; + return 0; + } + if (PCI_VENDORID(pa->pa_id) != DEC_VENDORID) return 0; if (PCI_CHIPID(pa->pa_id) == CHIPID_21040 @@ -5250,6 +5388,9 @@ else if (PCI_CHIPID(id) == CHIPID_21041) chipid = TULIP_21041; else if (PCI_CHIPID(id) == CHIPID_21142) chipid = TULIP_21142; } + else if (PCI_VENDOR(id) == PCI_VENDOR_LITEON && + PCI_CHIPID(id) == PCI_PRODUCT_LITEON_PNIC) + chipid = TULIP_LC82C168; if (chipid == TULIP_CHIPID_UNKNOWN) return; @@ -5296,6 +5437,8 @@ if (chipid != TULIP_21041 && sc->tulip_revinfo >= 0x20) sc->tulip_features |= TULIP_HAVE_SIA100; } + if (chipid == TULIP_LC82C168) + sc->tulip_features |= TULIP_HAVE_POWERMGMT; if (sc->tulip_features & TULIP_HAVE_POWERMGMT && (cfdainfo & (TULIP_CFDA_SLEEP|TULIP_CFDA_SNOOZE))) { Index: if_devar.h =================================================================== RCS file: /cvs/src/sys/dev/pci/if_devar.h,v retrieving revision 1.7 diff -u -r1.7 if_devar.h --- if_devar.h 1998/08/28 06:31:25 1.7 +++ if_devar.h 1998/10/07 05:51:42 @@ -140,6 +140,9 @@ tulip_csrptr_t csr_13; /* CSR13 */ tulip_csrptr_t csr_14; /* CSR14 */ tulip_csrptr_t csr_15; /* CSR15 */ + tulip_csrptr_t csr_19; /* CSR19 - PNIC */ + tulip_csrptr_t csr_20; /* CSR20 - PNIC */ + tulip_csrptr_t csr_23; /* CSR23 - PNIC */ } tulip_regfile_t; #define csr_enetrom csr_9 /* 21040 */ @@ -223,6 +226,7 @@ TULIP_21041, TULIP_21140, TULIP_21140A, TULIP_21142, TULIP_21143, + TULIP_LC82C168, TULIP_CHIPID_UNKNOWN } tulip_chipid_t; @@ -731,6 +735,7 @@ "21140A [10-100Mb/s]", "21142 [10-100Mb/s]", "21143 [10-100Mb/s]", + "82C168 [10-100Mb/s]", }; static const char * const tulip_mediums[] = { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 00:37:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03669 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 00:37:17 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (castles29.castles.com [208.214.165.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03650 for ; Wed, 7 Oct 1998 00:37:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA01166; Wed, 7 Oct 1998 00:42:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810070742.AAA01166@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Marc Slemko cc: hardware@FreeBSD.ORG Subject: Re: Lite-On PNIC (fwd) In-reply-to: Your message of "Wed, 07 Oct 1998 00:18:58 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 00:42:19 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > For anyone interested; from an OpenBSD mailing list. > > It would be happiness if such small changes were indeed all that is > required. Bill Paul has more or less inadvertently rewritten the 'de' driver while writing support for the Winbond 100Mbps chips. We might want to go with something that's slightly less of an ifdef tangle (have you tried looking at the 'de' sources?), especially if the maintainer continues to be too busy to maintain it. It would be interesting to test these changes though. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Oct 7 09:39:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25720 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 09:39:25 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25704 for ; Wed, 7 Oct 1998 09:39:18 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id RAA05632; Wed, 7 Oct 1998 17:39:08 +0100 (BST) Date: Wed, 7 Oct 1998 17:39:08 +0100 (BST) From: Karl Pielorz To: Justin Clift cc: hardware@FreeBSD.ORG Subject: Re: NE-2100 and FreeBSD 2.3 In-Reply-To: <000301bdf20c$aa6c5e40$011d6ccb@knight> 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, 8 Oct 1998, Justin Clift wrote: > Hiya Karl, > > You seem to have some experience overcoming problems with NE-2100 cards? Hmmm... Yes, I guess so - I certainly used to use quite a few of them ;-) (I've cc'd this mail to the FreeBSD hardware list, in case someone else has heard of these cards)... > Any ideas for a first time BSD installer on how to get the machine to go > past the Visual setup when using one of these cards? > > I tried the settings I found in the mailing list archives where you > recommended to try: [snip] > I have no idea which settings the card is really ON though, as its totally > jumperless. > > The card is a HP PC/LAN card, supposed to be NE1500/2100 compatible. > > I'm attempting to get a 486/8mb/340MB HDD up and running on FreeBSD 2.3... Hmmm... FreeBSD 2.3? - FreeBSD normally has version such as 2.2.1, 2.2.7 etc. - I don't think there is a 2.3 :( Anyway, Your going to need to find out what that card's set to configuration wise before you will get it to work... 0x340, drq 7, irq 9 is what we run ours round here on - but we're lucky and have Jumpers to set on them... I just had a quick look round HP's website - I can't find that card, does it have an HP partnumber, something like J25537 or something? Most the 'jumperless' cards these days are Plug & Play, we need to find out if that card is - if it isn't there'll be usually a DOS based configuration program that will set the card up (e.g. for Intel ISA cards this used to be a utility called 'softset') Without knowing what the cards set to, and with having the IRQ, port and DMA to play with - the chances of 'guessing' it's settings are going to be quite slim... The only other thing I could think of would be to put it into a Win95 machine and see what that thinks about it - sometimes (if your lucky) it will manage to figure what the card is, and what's it on (it usually screws up the DMA channel - but that's not too hard to guess ;-) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 09:51:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26976 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 09:51:59 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from calvin.saturn-tech.com ([207.229.19.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26968 for ; Wed, 7 Oct 1998 09:51:56 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id KAA01665; Wed, 7 Oct 1998 10:51:13 -0600 (MDT) (envelope-from drussell@saturn-tech.com) Date: Wed, 7 Oct 1998 10:51:13 -0600 (MDT) From: Doug Russell To: "Kenneth D. Merry" cc: alk@pobox.com, hardware@FreeBSD.ORG Subject: Re: Sony CDU926S In-Reply-To: <199810020552.XAA11908@panzer.plutotech.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 Thu, 1 Oct 1998, Kenneth D. Merry wrote: > Tony Kimball wrote... > > Is anyone using this CD-R drive succesfully with CAM? > > Talk to Parag Patel . He submitted a quirk entry to disable > multi-LUN probing for that drive. Interesting counter-question.... Does anyone have one working properly (cdrecord) WITHOUT CAM? I think I MUST be doing something wrong here. I have everything (as far as I can tell) configured properly, cdrecord -checkdrive, etc... finds the drive and reports it as a 926, using the 924 driver, etc. I can get through dummy data and audio writes with no errors, and even burn the disks with no errors, however, they don't have any information on them! :) An audio CD comes out with all the tracks, but they all just sound like clicks. (The data reads a long string of NULLs, then a little data, if you read the file back in with tosha.) A 9660 FS supposedly burned onto a disc is not mountable. (It seems to be recorded just like the audio... no data.) What might I be doing wrong here? The drive is on an NCR-810 with a Sony CDU-411 or some such number 12x CD-ROM as the only other device. Works fine from WinNT. Anything wack-o that has to be done to make this work? Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 10:01:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28571 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 10:01:09 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28560 for ; Wed, 7 Oct 1998 10:01:00 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id LAA11287; Wed, 7 Oct 1998 11:00:09 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810071700.LAA11287@panzer.plutotech.com> Subject: Re: Sony CDU926S In-Reply-To: from Doug Russell at "Oct 7, 98 10:51:13 am" To: drussell@saturn-tech.com (Doug Russell) Date: Wed, 7 Oct 1998 11:00:09 -0600 (MDT) Cc: alk@pobox.com, hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Doug Russell wrote... > > On Thu, 1 Oct 1998, Kenneth D. Merry wrote: > > > Tony Kimball wrote... > > > Is anyone using this CD-R drive succesfully with CAM? > > > > Talk to Parag Patel . He submitted a quirk entry to disable > > multi-LUN probing for that drive. > > Interesting counter-question.... Does anyone have one working properly > (cdrecord) WITHOUT CAM? I think I MUST be doing something wrong here. > > I have everything (as far as I can tell) configured properly, cdrecord > -checkdrive, etc... finds the drive and reports it as a 926, using the 924 > driver, etc. I can get through dummy data and audio writes with no > errors, and even burn the disks with no errors, however, they don't have > any information on them! :) An audio CD comes out with all the tracks, > but they all just sound like clicks. (The data reads a long string of > NULLs, then a little data, if you read the file back in with tosha.) > > A 9660 FS supposedly burned onto a disc is not mountable. (It seems to be > recorded just like the audio... no data.) > > What might I be doing wrong here? The drive is on an NCR-810 with a Sony > CDU-411 or some such number 12x CD-ROM as the only other device. Works > fine from WinNT. > > Anything wack-o that has to be done to make this work? Well, one thing you didn't mention is the command line arguments you used with cdrecord to record the audio tracks. Keep in mind that you need the -swab flag to cdrecord, otherwise the audio tracks will come out sounding like garbage. You might also want to try the cdrecord port that Jean-Marc checked in last night. It could be that you're running into a bug that has been fixed. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 11:03:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11854 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 11:03:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11832 for ; Wed, 7 Oct 1998 11:03:10 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id OAA22328; Wed, 7 Oct 1998 14:02:22 -0400 (EDT) Date: Wed, 7 Oct 1998 14:02:22 -0400 (EDT) From: "Matthew N. Dodd" To: Mike Smith cc: Marc Slemko , hardware@FreeBSD.ORG, wpaul@ctr.columbia.edu Subject: Re: Lite-On PNIC (fwd) In-Reply-To: <199810070742.AAA01166@dingo.cdrom.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 [Added Bill Paul to the CC:] On Wed, 7 Oct 1998, Mike Smith wrote: > Bill Paul has more or less inadvertently rewritten the 'de' driver > while writing support for the Winbond 100Mbps chips. We might want to > go with something that's slightly less of an ifdef tangle (have you > tried looking at the 'de' sources?), especially if the maintainer > continues to be too busy to maintain it. > > It would be interesting to test these changes though. You're proposing to provide Bill with examples of -all- the different varients of the Tulip cards and enough hard drugs to keep in in the state of mind required to do the work? Impressive. The PNIC changes appear to be straight forward (though they could probably use some un-grunging) and in line with existing code to support other Tulip varients. Though I would speak to Bill about this first, I'm betting the best course would be to apply some flavor of this patch and move on to better things. I'm pretty sure that more duplicated code would be a step backwards. (Unless of ocurse, Bill accepts your crates of cards and your stash of smack.) (I would really fear a Bill-written Tulip driver; his other code is really clean and it would be interesting to see his solution to the Tulip mess.) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 11:20:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15489 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 11:20:11 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15441 for ; Wed, 7 Oct 1998 11:20:07 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA01419; Wed, 7 Oct 1998 11:21:35 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810071821.LAA01419@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Matthew N. Dodd" cc: Mike Smith , Marc Slemko , hardware@FreeBSD.ORG, wpaul@ctr.columbia.edu Subject: Re: Lite-On PNIC (fwd) In-reply-to: Your message of "Wed, 07 Oct 1998 14:02:22 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 11:21:35 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > [Added Bill Paul to the CC:] > > On Wed, 7 Oct 1998, Mike Smith wrote: > > Bill Paul has more or less inadvertently rewritten the 'de' driver > > while writing support for the Winbond 100Mbps chips. We might want to > > go with something that's slightly less of an ifdef tangle (have you > > tried looking at the 'de' sources?), especially if the maintainer > > continues to be too busy to maintain it. > > > > It would be interesting to test these changes though. > > You're proposing to provide Bill with examples of -all- the different > varients of the Tulip cards and enough hard drugs to keep in in the state > of mind required to do the work? I was actually planning on just feeding the non-Digital-based cards to Bill, as most of them are cut-downs. We're certainly more than happy to facilitate providing hardware to developers, especially ones with track records like Bill's. 8) > The PNIC changes appear to be straight forward (though they could probably > use some un-grunging) and in line with existing code to support other > Tulip varients. Though I would speak to Bill about this first, I'm > betting the best course would be to apply some flavor of this patch and > move on to better things. I'm pretty sure that more duplicated code would > be a step backwards. It almost certainly would be. The problem is that the 'de' driver is (meant to be) maintained by Matt Thomas, who has been extremely quiet of late (due to a move and other things). We've supplied Matt with hardware in the past (eg. a Macronix card a month or so back), but his responses have been kinda patchy, and as you've seen the net result is an almost unmaintainable mess. > (I would really fear a Bill-written Tulip driver; his other code is really > clean and it would be interesting to see his solution to the Tulip mess.) Having spent some time headfirst in the 'de' dungheap, I'd be inclined to say that it really needs to be a pile of well-specified function vectors with a large heap of access and personality macros. There's just far too much "if tulip_chipid == foo" logic in there, not to mention more #ifdefs than anyone wants to see. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Oct 7 11:31:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17750 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 11:31:18 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: (from wpaul@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17593; Wed, 7 Oct 1998 11:30:33 -0700 (PDT) (envelope-from wpaul) From: Bill Paul Message-Id: <199810071830.LAA17593@hub.freebsd.org> Subject: Re: Lite-On PNIC (fwd) In-Reply-To: from Marc Slemko at "Oct 7, 98 00:18:58 am" To: marcs@znep.com (Marc Slemko) Date: Wed, 7 Oct 1998 11:30:32 -0700 (PDT) Cc: jason@thought.net, tech@openbsd.org, hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 > Date: Wed, 7 Oct 1998 01:59:49 -0400 (EDT) > From: jason@thought.net > To: tech@openbsd.org > Subject: Lite-On PNIC > > What follows are the diffs for /sys/dev/pci/{if_de.c,if_devar.h} to > support the Lite-On PNIC. I'm not sure about the marketing, but the > box this card came in said "Netgear FA310TX rev D1", and I've been told > that newer Kingston? boards use this same chip set. > > I need testers, and I'd like for someone more familiar with if_de to > tell me if I'm doing things all wrong or not =) The card works, but > it seems to have trouble with manually setting the media type. > > If you have a board that probes as "Lite-On PNIC", please give this patch > a try and let me know your results as soon as possible. > > --Jason Wright FYI: I spotted a small bug just looking at this patch. The code that writes to the PHY registers has a typo in it: > - unsigned csr = TULIP_CSR_READ(sc, csr_srom_mii) & (MII_RD|MII_DOUT|MII_CLK); > + unsigned csr; > + > + if (sc->tulip_chipid == TULIP_LC82C168) { > + int tmout = 1000; > + > + TULIP_CSR_WRITE(sc, csr_20, (MII_WRCMD << 28) | > + (devaddr << 23) | (regno << 18) | data); > + do { > + if (! (TULIP_CSR_READ(sc, csr_20) & 0x8000000)) > + return; ^^^^^^^^^ > + } while (--tmout); > + return; > + } > + > + csr = TULIP_CSR_READ(sc, csr_srom_mii) & (MII_RD|MII_DOUT|MII_CLK); That 0x8000000 up there should be 0x80000000. The 'busy' bit is bit 31. Also, LinkSys sells a 10/100 card that uses the PNIC chip. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 11:39:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19962 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 11:39:30 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19925 for ; Wed, 7 Oct 1998 11:39:14 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id OAA22728; Wed, 7 Oct 1998 14:38:44 -0400 (EDT) Date: Wed, 7 Oct 1998 14:38:44 -0400 (EDT) From: "Matthew N. Dodd" To: Mike Smith cc: Marc Slemko , hardware@FreeBSD.ORG, wpaul@ctr.columbia.edu Subject: Re: Lite-On PNIC (fwd) In-Reply-To: <199810071821.LAA01419@dingo.cdrom.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 Wed, 7 Oct 1998, Mike Smith wrote: > > You're proposing to provide Bill with examples of -all- the different > > varients of the Tulip cards and enough hard drugs to keep in in the state > > of mind required to do the work? > > I was actually planning on just feeding the non-Digital-based cards to > Bill, as most of them are cut-downs. We're certainly more than happy > to facilitate providing hardware to developers, especially ones with > track records like Bill's. 8) You didn't say anything about the hard drugs. :) > It almost certainly would be. The problem is that the 'de' driver is > (meant to be) maintained by Matt Thomas, who has been extremely quiet > of late (due to a move and other things). We've supplied Matt with > hardware in the past (eg. a Macronix card a month or so back), but his > responses have been kinda patchy, and as you've seen the net result is > an almost unmaintainable mess. Humm... My experience with Matt has been rather good but the last time I talked to him re: the de driver was about 3 years ago when I was trying to get a Znyx 314 card to work. In all likelyhood the multi OS nature of the de driver is what is causing the most problem. > Having spent some time headfirst in the 'de' dungheap, I'd be inclined > to say that it really needs to be a pile of well-specified function > vectors with a large heap of access and personality macros. There's > just far too much "if tulip_chipid == foo" logic in there, not to > mention more #ifdefs than anyone wants to see. Cool. Coherent design. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 12:00:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23723 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 12:00:10 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from calvin.saturn-tech.com ([207.229.19.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23606 for ; Wed, 7 Oct 1998 11:59:57 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id MAA01865; Wed, 7 Oct 1998 12:59:31 -0600 (MDT) (envelope-from drussell@saturn-tech.com) Date: Wed, 7 Oct 1998 12:59:31 -0600 (MDT) From: Doug Russell Reply-To: Doug Russell To: "Kenneth D. Merry" cc: alk@pobox.com, hardware@FreeBSD.ORG Subject: Re: Sony CDU926S In-Reply-To: <199810071700.LAA11287@panzer.plutotech.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 > > I have everything (as far as I can tell) configured properly, cdrecord > > -checkdrive, etc... finds the drive and reports it as a 926, using the 924 > > driver, etc. I can get through dummy data and audio writes with no > > errors, and even burn the disks with no errors, however, they don't have > > any information on them! :) An audio CD comes out with all the tracks, > > but they all just sound like clicks. (The data reads a long string of ... > Well, one thing you didn't mention is the command line arguments you used > with cdrecord to record the audio tracks. With CDR_DEVICE=0,6,0 and CDR_SPEED=2 cdrecord -v -audio Trackx.wav > Keep in mind that you need the -swab flag to cdrecord, otherwise the audio > tracks will come out sounding like garbage. It already knows that it needs the -swab for the 926. I actually wanted to try turning it OFF to see if that was the problem, but I never got around to recompiling it so it didn't force the 926 to -swab. (There is no -noswab option for drives with it (quirk entried?) hard coded.) I then tried doing a data disc, and it didn't work either, so I am guessing the the -swab is NOT the problem. I also tried going from raw pcm out of TOSHA and from .wav, if I remember right. Same results. It also doesn't sound like wrong-endian data... it clicks at a constant rate, not static messy noise. To burn the data disk, I did a simple cdrecord -v test9660.img The image is fine, as I can use the vn driver to mount_cd9660 it. I can't mount it from the CD, however. The track is there, if I do a cdrecord -toc, or whathaveyou, but nothing can access it. In any case, it has been a couple weeks since I last recompiled cdrecord, so I'm off to do a cvsup ports-distfile && make. :) At least now I know that it SHOULD work if others can burn CDs. :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 12:04:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24313 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 12:04:03 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24285 for ; Wed, 7 Oct 1998 12:03:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA01756; Wed, 7 Oct 1998 12:07:25 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810071907.MAA01756@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Matthew N. Dodd" cc: Mike Smith , Marc Slemko , hardware@FreeBSD.ORG, wpaul@ctr.columbia.edu Subject: Re: Lite-On PNIC (fwd) In-reply-to: Your message of "Wed, 07 Oct 1998 14:38:44 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 12:07:25 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Wed, 7 Oct 1998, Mike Smith wrote: > > > You're proposing to provide Bill with examples of -all- the different > > > varients of the Tulip cards and enough hard drugs to keep in in the state > > > of mind required to do the work? > > > > I was actually planning on just feeding the non-Digital-based cards to > > Bill, as most of them are cut-downs. We're certainly more than happy > > to facilitate providing hardware to developers, especially ones with > > track records like Bill's. 8) > > You didn't say anything about the hard drugs. :) Send me your PGP key first. Remember I'm a furriner in this country; the're watching me. 8) > > It almost certainly would be. The problem is that the 'de' driver is > > (meant to be) maintained by Matt Thomas, who has been extremely quiet > > of late (due to a move and other things). We've supplied Matt with > > hardware in the past (eg. a Macronix card a month or so back), but his > > responses have been kinda patchy, and as you've seen the net result is > > an almost unmaintainable mess. > > Humm... My experience with Matt has been rather good but the last time I > talked to him re: the de driver was about 3 years ago when I was trying to > get a Znyx 314 card to work. Matt's very much dedicated to the 'de' driver; he's just very employable and thus very busy. > In all likelyhood the multi OS nature of the de driver is what is causing > the most problem. That and the fact that it's grown organically without having been designed for it. I remember way back when it was first imported, it was neat, clean and easy to follow. Kinda like the 'ed' driver, only worse. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Oct 7 14:36:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27914 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 14:36:36 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27907 for ; Wed, 7 Oct 1998 14:36:29 -0700 (PDT) (envelope-from son@cezanne.prism.uvsq.fr) Received: from cezanne.prism.uvsq.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA04958 for ; Wed, 7 Oct 1998 23:36:09 +0200 (MET DST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.9.1/8.8.5) id XAA00256; Wed, 7 Oct 1998 23:36:08 GMT Message-ID: <19981007233608.26066@breizh.prism.uvsq.fr> Date: Wed, 7 Oct 1998 23:36:08 +0000 From: Nicolas Souchu To: freebsd-hardware@FreeBSD.ORG Subject: Aladdin V AGPset chipset datasheet? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e X-Operating-System: FreeBSD breizh 3.0-BETA FreeBSD 3.0-BETA Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org G'day, Is there any chance to find/get the Aladdin V AGPset chipset datasheet? I've already tried on there web site, but with no success. Did I miss something? Thanks in advance, Regards, Nicolas. -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PCs into workstations - 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 Wed Oct 7 14:44:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29156 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 14:44:29 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA29146 for ; Wed, 7 Oct 1998 14:44:26 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 26683 invoked by uid 1001); 7 Oct 1998 21:44:20 +0000 (GMT) To: freebsd-hardware@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: What kind of SCSI controller is in a Compaq Proliant 3000? Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Date: Wed, 07 Oct 1998 23:44:20 +0200 Message-ID: <26681.907796660@verdi.nethelp.no> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just got my hands on a nice shiny new Compaq Proliant 3000 server (yes, I know Compaqs are weird in some ways, but this is beyond my control). I'd like to install FreeBSD on it, but the problem is that no SCSI disk controller is detected (and thus no SCSI disks) by the 3.0 boot disk. The standard Proliant 3000 config: http://www.compaq.com/products/servers/proliant3000/index.html mentions a dual channel wide-ultra SCSI-3 controller, and this is indeed what the BIOS claims it has. I thought it might be an Adaptec (with a different PCI Chip ID). Will try to have a look at the actual controller tomorrow. Meanwhile, does anybody know kind of beast this SCSI controller is? Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 14:56:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01467 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 14:56:01 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01410; Wed, 7 Oct 1998 14:55:51 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA02835; Wed, 7 Oct 1998 15:00:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810072200.PAA02835@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sthaug@nethelp.no cc: freebsd-hardware@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: What kind of SCSI controller is in a Compaq Proliant 3000? In-reply-to: Your message of "Wed, 07 Oct 1998 23:44:20 +0200." <26681.907796660@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 15:00:39 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Just got my hands on a nice shiny new Compaq Proliant 3000 server (yes, > I know Compaqs are weird in some ways, but this is beyond my control). > I'd like to install FreeBSD on it, but the problem is that no SCSI disk > controller is detected (and thus no SCSI disks) by the 3.0 boot disk. > The standard Proliant 3000 config: > > http://www.compaq.com/products/servers/proliant3000/index.html > > mentions a dual channel wide-ultra SCSI-3 controller, and this is indeed > what the BIOS claims it has. > > I thought it might be an Adaptec (with a different PCI Chip ID). Will try > to have a look at the actual controller tomorrow. Meanwhile, does anybody > know kind of beast this SCSI controller is? No, but the device ID's will be printed if you boot with '-v', and that will give us an excellent start on working out what it is. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Oct 7 15:04:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04157 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 15:04:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--189.sirius.net [205.134.241.189]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04083 for ; Wed, 7 Oct 1998 15:04:18 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id PAA08349; Wed, 7 Oct 1998 15:00:03 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199810072200.PAA08349@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Russell cc: "Kenneth D. Merry" , alk@pobox.com, hardware@FreeBSD.ORG Subject: Re: Sony CDU926S In-reply-to: Your message of "Wed, 07 Oct 1998 10:51:13 MDT." X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 15:00:03 -0700 From: Parag Patel Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Interesting counter-question.... Does anyone have one working properly >(cdrecord) WITHOUT CAM? I think I MUST be doing something wrong here. Worked fine for me before I switched to the CAM kernel, on both 2.2-STABLE and 3.0-CURRENT. I would guess that your drive may be bad. Can you try it on a Mac or even (I hate to suggest it) Windows system and see if it'll still burn readable CD-Rs? -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 15:21:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08720 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 15:21:11 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08704 for ; Wed, 7 Oct 1998 15:21:06 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA13181; Wed, 7 Oct 1998 16:20:19 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810072220.QAA13181@panzer.plutotech.com> Subject: Re: Sony CDU926S In-Reply-To: from Doug Russell at "Oct 7, 98 12:59:31 pm" To: drussell@saturn-tech.com Date: Wed, 7 Oct 1998 16:20:19 -0600 (MDT) Cc: alk@pobox.com, hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Doug Russell wrote... > > > > I have everything (as far as I can tell) configured properly, cdrecord > > > -checkdrive, etc... finds the drive and reports it as a 926, using the 924 > > > driver, etc. I can get through dummy data and audio writes with no > > > errors, and even burn the disks with no errors, however, they don't have > > > any information on them! :) An audio CD comes out with all the tracks, > > > but they all just sound like clicks. (The data reads a long string of > ... > > > Well, one thing you didn't mention is the command line arguments you used > > with cdrecord to record the audio tracks. > > With CDR_DEVICE=0,6,0 and CDR_SPEED=2 > > cdrecord -v -audio Trackx.wav > > > Keep in mind that you need the -swab flag to cdrecord, otherwise the audio > > tracks will come out sounding like garbage. > > It already knows that it needs the -swab for the 926. I actually wanted > to try turning it OFF to see if that was the problem, but I never got > around to recompiling it so it didn't force the 926 to -swab. (There is > no -noswab option for drives with it (quirk entried?) hard coded.) Well, as long as that's the case (that it defaults to -swab), you should be fine. The first time I burned an audio CD with cdrecord, I didn't set the -swab flag and I just got a CD full of noise. > > I then tried doing a data disc, and it didn't work either, so I am > guessing the the -swab is NOT the problem. I also tried going from raw > pcm out of TOSHA and from .wav, if I remember right. Same results. It > also doesn't sound like wrong-endian data... it clicks at a constant > rate, not static messy noise. > > To burn the data disk, I did a simple cdrecord -v test9660.img > > The image is fine, as I can use the vn driver to mount_cd9660 it. I can't > mount it from the CD, however. The track is there, if I do a cdrecord > -toc, or whathaveyou, but nothing can access it. > > In any case, it has been a couple weeks since I last recompiled cdrecord, > so I'm off to do a cvsup ports-distfile && make. :) > > At least now I know that it SHOULD work if others can burn CDs. :) Yeah, it should work okay. In fact, I just burned a data CD with cdrecord compiled from Jean-Marc's new port. I used the following arguments to mkisofs: # mkisofs -a -d -D -l -L -N -R -V 1 -o foo.img foo_dir And I ran cdrecord like this: # cdrecord dev=1,3,0 speed=4 -data foo.img The resulting CD reads just fine. In general, if cdrecord can talk to your drive at all, it isn't really a CAM problem. i.e. if you can do something like 'cdrecord dev=1,3,0 -inq' and 'cdrecord -scanbus', and get valid results, then the cdrecord<->CAM interface is working just fine. If the cdrecord<->CAM interface is working okay, then the other things to look at are the arguments to the mkisofs/tosha/cdrecord commands, the state of the drive (broken?), type of media, etc. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 16:24:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20923 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 16:24:10 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from calvin.saturn-tech.com ([207.229.19.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20886 for ; Wed, 7 Oct 1998 16:24:04 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id RAA05591; Wed, 7 Oct 1998 17:23:10 -0600 (MDT) (envelope-from drussell@saturn-tech.com) Date: Wed, 7 Oct 1998 17:23:10 -0600 (MDT) From: Doug Russell To: Parag Patel cc: hardware@FreeBSD.ORG Subject: Re: Sony CDU926S In-Reply-To: <199810072200.PAA08349@pinhead.parag.codegen.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 Wed, 7 Oct 1998, Parag Patel wrote: > Worked fine for me before I switched to the CAM kernel, on both > 2.2-STABLE and 3.0-CURRENT. I would guess that your drive may be bad. > Can you try it on a Mac or even (I hate to suggest it) Windows system > and see if it'll still burn readable CD-Rs? It is burning a CD as we speak from NT4. I updated cdrecord this afternoon, so I'll try to play with it this evening again. Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 16:50:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25519 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 16:50:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pegasus.com (pegasus.com [206.127.225.31]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA25490 for ; Wed, 7 Oct 1998 16:50:48 -0700 (PDT) (envelope-from richard@pegasus.com) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id NAA20011; Wed, 7 Oct 1998 13:50:18 -1000 Date: Wed, 7 Oct 1998 13:50:18 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199810072350.NAA20011@pegasus.com> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-hardware@FreeBSD.ORG Subject: Full duplex ethernet Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Which ether-card drivers currently support full duplex? Recently, someone here said that full duplex for 10Base-T was a waste of time. But after some research it's beginning to look like that's not true at all. 10BT switches are available, and cost way less than 100BT switches. I've gotten reports from several places saying that in practice, switched full-duplex 10BT is faster than half-duplex hub-based 100BT. Since 100BT switches aren't really affordable yet, full duplex 10BT sounds like a winner. Do any of the 10/100 cards support full duplex in their 10BT mode? Thanks Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 16:56:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26727 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 16:56:42 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26679; Wed, 7 Oct 1998 16:56:33 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id SAA03821; Wed, 7 Oct 1998 18:56:25 -0500 (CDT) Date: Wed, 7 Oct 1998 18:56:25 -0500 From: Dan Nelson To: sthaug@nethelp.no, freebsd-hardware@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: What kind of SCSI controller is in a Compaq Proliant 3000? Message-ID: <19981007185625.A3740@emsphone.com> References: <26681.907796660@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <26681.907796660@verdi.nethelp.no>; from "sthaug@nethelp.no" on Wed Oct 7 23:44:20 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In the last episode (Oct 07), sthaug@nethelp.no said: > Just got my hands on a nice shiny new Compaq Proliant 3000 server (yes, > I know Compaqs are weird in some ways, but this is beyond my control). > I'd like to install FreeBSD on it, but the problem is that no SCSI disk > controller is detected (and thus no SCSI disks) by the 3.0 boot disk. > The standard Proliant 3000 config: > > http://www.compaq.com/products/servers/proliant3000/index.html > > mentions a dual channel wide-ultra SCSI-3 controller, and this is indeed > what the BIOS claims it has. I believe all of the Compaq SCSI adaptors (except possible the RAID ones) are Symbios/NCR chipsets. At least out Proliant 2500 is, and there is just one Compaq SCSI HAM driver for Netware, so it must cover all the Compaq cards. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 19:36:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23658 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 19:36:03 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23616; Wed, 7 Oct 1998 19:35:52 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA26077; Wed, 7 Oct 1998 19:18:37 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd026010; Wed Oct 7 19:18:28 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id TAA01141; Wed, 7 Oct 1998 19:18:24 -0700 (MST) From: Terry Lambert Message-Id: <199810080218.TAA01141@usr08.primenet.com> Subject: Re: What kind of SCSI controller is in a Compaq Proliant 3000? To: dnelson@emsphone.com (Dan Nelson) Date: Thu, 8 Oct 1998 02:18:23 +0000 (GMT) Cc: sthaug@nethelp.no, freebsd-hardware@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <19981007185625.A3740@emsphone.com> from "Dan Nelson" at Oct 7, 98 06:56:25 pm X-Mailer: ELM [version 2.4 PL25] 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 > > Just got my hands on a nice shiny new Compaq Proliant 3000 server (yes, > > I know Compaqs are weird in some ways, but this is beyond my control). > > I'd like to install FreeBSD on it, but the problem is that no SCSI disk > > controller is detected (and thus no SCSI disks) by the 3.0 boot disk. > > The standard Proliant 3000 config: > > > > http://www.compaq.com/products/servers/proliant3000/index.html > > > > mentions a dual channel wide-ultra SCSI-3 controller, and this is indeed > > what the BIOS claims it has. > > I believe all of the Compaq SCSI adaptors (except possible the RAID > ones) are Symbios/NCR chipsets. At least out Proliant 2500 is, and > there is just one Compaq SCSI HAM driver for Netware, so it must cover > all the Compaq cards. If this is the RAID controller, a driver was written, but not integrated into -current. Check the list archives for "compaq RAID". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 20:27:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03875 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 20:27:28 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.84.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03846; Wed, 7 Oct 1998 20:27:20 -0700 (PDT) (envelope-from root@danberlin.resnet.rochester.edu) Received: from danberlin.resnet.rochester.edu (root@danberlin.resnet.rochester.edu [128.151.84.217]) by danberlin.resnet.rochester.edu (8.9.1a/8.9.1/Debian/GNU) with ESMTP id XAA13246; Wed, 7 Oct 1998 23:21:00 -0400 Date: Wed, 7 Oct 1998 23:21:00 -0400 (EDT) From: Daniel Berlin To: Dan Nelson cc: sthaug@nethelp.no, freebsd-hardware@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: What kind of SCSI controller is in a Compaq Proliant 3000? In-Reply-To: <19981007185625.A3740@emsphone.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 They prolly pulled a Diamond and changed the vendor ID on it. If it's symbios, it's a 876. If it's adaptec, it's a 7895. On Wed, 7 Oct 1998, Dan Nelson wrote: > In the last episode (Oct 07), sthaug@nethelp.no said: > > Just got my hands on a nice shiny new Compaq Proliant 3000 server (yes, > > I know Compaqs are weird in some ways, but this is beyond my control). > > I'd like to install FreeBSD on it, but the problem is that no SCSI disk > > controller is detected (and thus no SCSI disks) by the 3.0 boot disk. > > The standard Proliant 3000 config: > > > > http://www.compaq.com/products/servers/proliant3000/index.html > > > > mentions a dual channel wide-ultra SCSI-3 controller, and this is indeed > > what the BIOS claims it has. > > I believe all of the Compaq SCSI adaptors (except possible the RAID > ones) are Symbios/NCR chipsets. At least out Proliant 2500 is, and > there is just one Compaq SCSI HAM driver for Netware, so it must cover > all the Compaq cards. > > -Dan Nelson > dnelson@emsphone.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 21:49:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16923 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 21:49:07 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA16879; Wed, 7 Oct 1998 21:48:51 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zR80D-0004WB-00; Wed, 7 Oct 1998 22:48:37 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id WAA10928; Wed, 7 Oct 1998 22:48:15 -0600 (MDT) Message-Id: <199810080448.WAA10928@harmony.village.org> To: Daniel Berlin Subject: Re: What kind of SCSI controller is in a Compaq Proliant 3000? Cc: Dan Nelson , sthaug@nethelp.no, freebsd-hardware@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 07 Oct 1998 23:21:00 EDT." References: Date: Wed, 07 Oct 1998 22:48:15 -0600 From: Warner Losh Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Daniel Berlin writes: : If it's symbios, it's a 876. : If it's adaptec, it's a 7895. Then it is either a 876 or something else since CAM groks the aic-7895 chip. Or compaq somehow jimmied the vendor ID on it... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 7 22:38:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23258 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 22:38:25 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (castles134.castles.com [208.214.165.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23253 for ; Wed, 7 Oct 1998 22:38:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA01244; Wed, 7 Oct 1998 22:43:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810080543.WAA01244@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: richard@pegasus.com (Richard Foulk) cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Full duplex ethernet In-reply-to: Your message of "Wed, 07 Oct 1998 13:50:18 -1000." <199810072350.NAA20011@pegasus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 22:43:18 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Which ether-card drivers currently support full duplex? de, fxp, tl, xl, tx at least. Basically, the high-performance cards. > Recently, someone here said that full duplex for 10Base-T was a waste > of time. But after some research it's beginning to look like that's > not true at all. > > 10BT switches are available, and cost way less than 100BT switches. > > I've gotten reports from several places saying that in practice, switched > full-duplex 10BT is faster than half-duplex hub-based 100BT. I can produce staistics for just about anything, including a pathalogical case where you may get "better performance" from a 10bT switch than a 100bT hub, but unless you're taking your particular work profile into account, on average you will lose. > Since 100BT switches aren't really affordable yet, full duplex 10BT > sounds like a winner. Less than US$600 for an 8-port 100bT switch, less than US$300 for a 16-port 100bT hub. Be wary of hubs with single switched "server ports". > Do any of the 10/100 cards support full duplex in their 10BT mode? Most if not all, AFAIK. But the cost argument for 10bT just isn't there anymore. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Oct 7 22:58:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26335 for freebsd-hardware-outgoing; Wed, 7 Oct 1998 22:58:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26258 for ; Wed, 7 Oct 1998 22:57:59 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id BAA29927; Thu, 8 Oct 1998 01:57:39 -0400 (EDT) Date: Thu, 8 Oct 1998 01:57:39 -0400 (EDT) From: "Matthew N. Dodd" To: Richard Foulk cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Full duplex ethernet In-Reply-To: <199810072350.NAA20011@pegasus.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 Wed, 7 Oct 1998, Richard Foulk wrote: > I've gotten reports from several places saying that in practice, > switched full-duplex 10BT is faster than half-duplex hub-based 100BT. I think that it only be intuitive deduction that this would be the case. I think the original poster was trying to point out that the real world difference b/t 10meg half duplex switched and 10 meg full duplex switched was not as great as one might think and in a great number of cases a really trivial difference. Since most 'switches' will support half and full, and any of the good cards should support 10/100 half and full, turning on 'full-duplex' can at worst case, only give you warm fuzzies. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 8 02:50:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02891 for freebsd-hardware-outgoing; Thu, 8 Oct 1998 02:50:32 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from Tasha.STARDreams.org (maccess-01-070.magna.com.au [203.111.85.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02732 for ; Thu, 8 Oct 1998 02:50:06 -0700 (PDT) (envelope-from kevla@studentmail.dis.unimelb.edu.au) Received: from EventHorizon (EventHorizon.STARDreams.org [10.144.144.1]) by Tasha.STARDreams.org (8.9.1/8.8.8) with SMTP id FAA05379 for ; Thu, 8 Oct 1998 05:50:00 -0400 (EDT) (envelope-from kevla@studentmail.dis.unimelb.edu.au) Message-Id: <3.0.3.32.19981008194944.0097da90@studentmail.dis.unimelb.edu.au> X-Sender: kevla@studentmail.dis.unimelb.edu.au X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 08 Oct 1998 19:49:44 +1000 To: freebsd-hardware@FreeBSD.ORG From: Kevin Lam Subject: Re: Full duplex ethernet In-Reply-To: <199810072350.NAA20011@pegasus.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 13:50 10/7/98 -1000, you wrote: >Which ether-card drivers currently support full duplex? > >Recently, someone here said that full duplex for 10Base-T was a waste >of time. But after some research it's beginning to look like that's >not true at all. > >10BT switches are available, and cost way less than 100BT switches. > >I've gotten reports from several places saying that in practice, switched >full-duplex 10BT is faster than half-duplex hub-based 100BT. You might be confusing a few things here. Firstly, full-duplex does not equate to switching.. however it is usually implemented alongside switching. It is true that switched 10BT would be faster than hub-based 100BT, but it would hold true even if it was switched half-duplex 10BT. The vast improvement in performance comes from the switch, which effectively creates a dedicated point-to-point channel for communications on the network, being much more powerful than shared 100BaseTX. In a switched architecture, collisions, which greatly impact performance, are almost eliminated, however, the two stations exchanging data could also collide with each other, even in a switched architecture. Full duplex merely eliminates this from happening at all (as both may transmit simultaneously). Switching plays the greatest part in reducing collisions and segregating communications, then full-duplex forms the icing on the cake. Anyway, for what it's worth, the xl driver (3Com Fast EtherLink) has full-duplex functions at both 10 and 100Mbps listed as available media. -- K "Deliver yesterday, code today, think tomorrow." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 8 09:35:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28887 for freebsd-hardware-outgoing; Thu, 8 Oct 1998 09:35:59 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28869 for ; Thu, 8 Oct 1998 09:35:54 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id MAA05261; Thu, 8 Oct 1998 12:35:03 -0400 (EDT) Date: Thu, 8 Oct 1998 12:35:03 -0400 (EDT) From: "Matthew N. Dodd" To: Mike Smith cc: Richard Foulk , freebsd-hardware@FreeBSD.ORG Subject: Re: Full duplex ethernet In-Reply-To: <199810080543.WAA01244@dingo.cdrom.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 Wed, 7 Oct 1998, Mike Smith wrote: > > Which ether-card drivers currently support full duplex? > > de, fxp, tl, xl, tx at least. Basically, the high-performance cards. Bill Paull reports that the RealTek chip supports full duplex as well. how about the winbond and liteon? They will when I'm done with them. So, to completly qualify your answer, a number of high-performance cards and a number of really trashy evil ugly cards. I wouldn't be surprised if you could get any of the RealTek, Winbond, or Liteon cards for $10 or $15. Regarding Mike's bit about 100meg hubs vs. 10meg switches the only reason I can see for a switch over a hub is if you need SNMP (usually standard on switches) and you don't want to allow systems on the same network to snoop eachother. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 8 11:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21637 for freebsd-hardware-outgoing; Thu, 8 Oct 1998 11:45:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA21557 for ; Thu, 8 Oct 1998 11:45:38 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 5386 invoked by uid 1001); 8 Oct 1998 18:45:26 +0000 (GMT) To: mike@smith.net.au Cc: freebsd-hardware@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: What kind of SCSI controller is in a Compaq Proliant 3000? In-Reply-To: Your message of "Wed, 07 Oct 1998 15:00:39 -0700" References: <199810072200.PAA02835@dingo.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 08 Oct 1998 20:45:26 +0200 Message-ID: <5384.907872326@verdi.nethelp.no> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Just got my hands on a nice shiny new Compaq Proliant 3000 server (yes, > > I know Compaqs are weird in some ways, but this is beyond my control). > > I'd like to install FreeBSD on it, but the problem is that no SCSI disk > > controller is detected (and thus no SCSI disks) by the 3.0 boot disk. ... > > I thought it might be an Adaptec (with a different PCI Chip ID). Will try > > to have a look at the actual controller tomorrow. Meanwhile, does anybody > > know kind of beast this SCSI controller is? > > No, but the device ID's will be printed if you boot with '-v', and that > will give us an excellent start on working out what it is. Unfortunately, no. I have to wonder if the PCI probing is different in 3.0, because *no* PCI devices are detected, except the basic PCI bridges in the system. This is with 3.0-19981006-BETA. It writes "Probing for devices on PCI bus 1", and then no devices are found. I was able to install 2.2.7-19980914-SNAP with only minor problems (using a different Ethernet card for the install, since the Thunderland driver is not on the 2.2.7 boot disks). The disk controller is a Symbios 53c876 (checked by looking at the actual chip), which appears as two 53c875's. Below is the boot -v output from 2.2.7. Anybody have an idea of why PCI probing fails in 3.0-19981006-BETA on this Compaq system? Anything more I can do to debug it? (Might try to install 3.0 "by hand" tomorrow - this is feasible since I have a running 2.2.7 system now, and plenty of disk space). Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- Calibrating clock(s) ... i586 clock: 332826782 Hz, i8254 clock: 1193275 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_I586_CALIBRATION not specified - using old calibration method CPU: Pentium II (quarter-micron) (332.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183fbff,,MMX,> real memory = 603979776 (589824K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00221000 - 0x23ffdfff, 601739264 bytes (146909 pages) avail memory = 589602816 (575784K bytes) eisa0: Probing for devices on the EISA bus pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x00000000 pcibus_setup(1a): mode1res=0x80000000 (0x80000000) pcibus_check: device 0 is there (id=00051166) Probing for devices on PCI bus 0: configuration mode 1 allows 32 devices. chip0 rev 3 on pci0:0:0 vga0 rev 34 int a irq ?? on pci0:6:0 mapreg[10] type=0 addr=c5000000 size=1000000. chip1 rev 7 on pci0:15:0 chip2 rev 3 on pci0:17:0 pci0: uses 16777216 bytes of memory from c5000000 upto c5ffffff. Probing for devices on PCI bus 1: ncr0 rev 20 int a irq 9 on pci1:4:0 mapreg[10] type=1 addr=00005000 size=0100. mapreg[14] type=0 addr=c6ffdf00 size=0100. mapreg[18] type=0 addr=c6fff000 size=1000. reg20: virtual=0xf616ef00 physical=0xc6ffdf00 size=0x100 reg24: virtual=0xf616f000 physical=0xc6fff000 size=0x1000 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 and 8..15 (V2 pl24 96/12/14) ncr0 waiting for scsi devices to settle (ncr0:0:0): WIDE SCSI (16 bit) enabled(ncr0:0:0): 10.0 MB/s (200 ns, offset 15) (ncr0:0:0): "COMPAQ HD0093172C 3207" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 15) 8678MB (17773500 512 byte sectors) sd0(ncr0:0:0): with 6962 cyls, 12 heads, and an average 212 sectors/track (ncr0:1:0): WIDE SCSI (16 bit) enabled(ncr0:1:0): 10.0 MB/s (200 ns, offset 15) (ncr0:1:0): "COMPAQ HD0093172C 3207" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): WIDE SCSI (16 bit) enabled sd1(ncr0:1:0): 40.0 MB/s (50 ns, offset 15) 8678MB (17773500 512 byte sectors) sd1(ncr0:1:0): with 6962 cyls, 12 heads, and an average 212 sectors/track (ncr0:4:0): WIDE SCSI (16 bit) enabled(ncr0:4:0): 10.0 MB/s (200 ns, offset 15) (ncr0:4:0): "COMPAQ HD0093172C 3207" type 0 fixed SCSI 2 sd2(ncr0:4:0): Direct-Access sd2(ncr0:4:0): WIDE SCSI (16 bit) enabled sd2(ncr0:4:0): 40.0 MB/s (50 ns, offset 15) 8678MB (17773500 512 byte sectors) sd2(ncr0:4:0): with 6962 cyls, 12 heads, and an average 212 sectors/track (ncr0:5:0): WIDE SCSI (16 bit) enabled(ncr0:5:0): 10.0 MB/s (200 ns, offset 15) (ncr0:5:0): "COMPAQ HD0093172C 3207" type 0 fixed SCSI 2 sd3(ncr0:5:0): Direct-Access sd3(ncr0:5:0): WIDE SCSI (16 bit) enabled sd3(ncr0:5:0): 40.0 MB/s (50 ns, offset 15) 8678MB (17773500 512 byte sectors) sd3(ncr0:5:0): with 6962 cyls, 12 heads, and an average 212 sectors/track ncr1 rev 20 int b irq 10 on pci1:4:1 mapreg[10] type=1 addr=00005400 size=0100. mapreg[14] type=0 addr=c6ffde00 size=0100. mapreg[18] type=0 addr=c6ffe000 size=1000. reg20: virtual=0xf6170e00 physical=0xc6ffde00 size=0x100 reg24: virtual=0xf6171000 physical=0xc6ffe000 size=0x1000 ncr1: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr1: single-ended, open drain IRQ driver, using on-chip SRAM ncr1: restart (scsi reset). ncr1 scanning for targets 0..6 and 8..15 (V2 pl24 96/12/14) ncr1 waiting for scsi devices to settle tl0 rev 16 int a irq 5 on pci1:8:0 mapreg[10] type=1 addr=00005800 size=0010. mapreg[14] type=0 addr=c6ffddf0 size=0010. tl0: Ethernet address: 00:08:c7:1e:a7:35 tl0: looking for phy at addr 0 tl0: status: 0 tl0: looking for phy at addr 1 tl0: status: 7849 tl0: phy at mii address 1 tl0: 10/100Mbps full duplex autonegotiating tl0: autoneg complete, link status good (full-duplex, 100Mbps) bpf: tl0 attached pci1: uses 8720 bytes of memory from c6ffddf0 upto c6ffffff. pci1: uses 528 bytes of I/O space from 5000 upto 580f. Probing for devices on the ISA bus: sc0: the current keyboard controller command byte 0065 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0 at 0x60-0x6f irq 1 on motherboard sc0: BIOS video mode:3 sc0: VGA registers upon power-up 50 18 10 00 10 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 sc0: video mode:24 sc0: VGA registers 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 sc0: VGA registers 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 sc0: rows_offset:1 sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x9 0x19 0x9 0x9 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 lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached psm0: current command byte:0065 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: 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 0a psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 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 (atapi): , removable, accel, dma, iordis wcd0: 1378Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: door open, unlocked npx0 flags 0x1 on motherboard npx0: INT 16 interface imasks: bio c0084640, tty c003109a, net c0060020 BIOS Geometries: 0:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 2:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 3:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: tun0 attached bpf: ppp0 attached new masks: bio c0084640, tty c003109a, net c00710ba bpf: lo0 attached Considering FFS root f/s. sd0s1: type 0x12, start 63, end = 80324, size 80262 : OK sd0s2: type 0x6, start 80325, end = 674729, size 594405 : OK sd0s3: type 0xa5, start 674730, end = 17767889, size 17093160 : OK sd1s1: type 0xa5, start 16065, end = 17767889, size 17751825 : OK sd1s3: type 0x12, start 63, end = 16064, size 16002 : OK sd3s1: type 0xa5, start 16065, end = 17767889, size 17751825 : OK sd3s3: type 0x12, start 63, end = 16064, size 16002 : OK sd2s1: type 0xa5, start 16065, end = 17767889, size 17751825 : OK sd2s3: type 0x12, start 63, end = 16064, size 16002 : OK sd2s1: type 0xa5, start 16065, end = 17767889, size 17751825 : OK sd2s3: type 0x12, start 63, end = 16064, size 16002 : OK sd3s1: type 0xa5, start 16065, end = 17767889, size 17751825 : OK sd3s3: type 0x12, start 63, end = 16064, size 16002 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 8 14:47:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26844 for freebsd-hardware-outgoing; Thu, 8 Oct 1998 14:47:28 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from tasam.com (tasam.com [198.232.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26807 for ; Thu, 8 Oct 1998 14:47:01 -0700 (PDT) (envelope-from clash@tasam.com) Received: from bug (bug.tasam.com [198.232.144.254]) by tasam.com (8.9.1/8.9.1) with SMTP id RAA14978 for ; Thu, 8 Oct 1998 17:46:45 -0400 (EDT) Message-ID: <008f01bdf305$30575de0$f10408d1@bug.tasam.com> From: "Joe Gleason" To: Subject: AIC-7895 in Stable? Where did Cam go? Can I fit entire message in subject line? Date: Thu, 8 Oct 1998 17:46:55 -0400 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 4.72.2110.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to get my AIC-7895 onboard controler on my Iwill DBS100 board working without going to 3.0-beta. Does anyone know when the AIC-7895 chipset will be in stable? I think it is in current, but I really don't want to goto current on my primary server. I read back in the list archive and found the AIC-7895 is supported in CAM and I have found this to be true. I am now running 2.2CAM-19980716-SNAP with this board and it works great. What happened to CAM? It seems to have dissappeared from the ftp sites. I assume it was assimilated into current. What will happen if I cvsup 2.2CAM-19980716-SNAP? With support for my SCSI still work? (I will find the answer to this one in a few hours through experimentation) Any help that anyone can give will be greatly appreciated. Joe Gleason Tasam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 8 15:27:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05042 for freebsd-hardware-outgoing; Thu, 8 Oct 1998 15:27:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05023 for ; Thu, 8 Oct 1998 15:27:50 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA20256; Thu, 8 Oct 1998 16:27:33 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810082227.QAA20256@panzer.plutotech.com> Subject: Re: AIC-7895 in Stable? Where did Cam go? Can I fit entire message in subject line? In-Reply-To: <008f01bdf305$30575de0$f10408d1@bug.tasam.com> from Joe Gleason at "Oct 8, 98 05:46:55 pm" To: clash@tasam.com (Joe Gleason) Date: Thu, 8 Oct 1998 16:27:33 -0600 (MDT) Cc: freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Joe Gleason wrote... > I'm trying to get my AIC-7895 onboard controler on my Iwill DBS100 board > working without going to 3.0-beta. > > Does anyone know when the AIC-7895 chipset will be in stable? Chipsets don't come with the operating system. Support for various pieces of hardware does come with the OS. There will never be support for the aic-7895 in the 2.2-stable tree. > I think it is in current, but I really don't want to goto current on my > primary server. CAM was integrated into current several weeks ago, so yes, there is support for the 7895 in -current. > I read back in the list archive and found the AIC-7895 is supported in CAM > and I have found this to be true. I am now running 2.2CAM-19980716-SNAP > with this board and it works great. So what's the problem? It works great, and you aren't running -current... > What happened to CAM? It seems to have > dissappeared from the ftp sites. It was moved. The new URL is: ftp://ftp.FreeBSD.ORG/pub/FreeBSD/development/cam > I assume it was assimilated into current. Yes. > What will happen if I cvsup 2.2CAM-19980716-SNAP? With support for my SCSI > still work? (I will find the answer to this one in a few hours through > experimentation) You can't cvsup "2.2CAM-19980716-SNAP". You can cvsup -current, -stable, or the CVS tree, but you can't cvsup something that was never checked into cvs. If you cvsup the 2.2-stable tree and rebuild, you will lose support for your 7895. As far as a new 2.2-stable CAM snapshot, that won't happen until after 3.0 comes out. (i.e. after October 15th) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 8 16:37:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20616 for freebsd-hardware-outgoing; Thu, 8 Oct 1998 16:37:01 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from tor-dev1.nbc.netcom.ca (tor-dev1.nbc.netcom.ca [207.181.89.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20605 for ; Thu, 8 Oct 1998 16:36:58 -0700 (PDT) (envelope-from dacole@netcom.ca) Received: from localhost (dacole@localhost) by tor-dev1.nbc.netcom.ca (8.8.8/8.8.8) with SMTP id TAA18101 for ; Thu, 8 Oct 1998 19:36:37 -0400 (EDT) X-Authentication-Warning: tor-dev1.nbc.netcom.ca: dacole owned process doing -bs Date: Thu, 8 Oct 1998 19:36:37 -0400 (EDT) From: Dave Cole X-Sender: dacole@tor-dev1.nbc.netcom.ca To: freebsd-hardware@FreeBSD.ORG Subject: pcmcia 3com 3c562d support? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got this card sitting here and I'm praying there is some initiative to supporting it in freebsd. Any freebsd. Will my hopes and dreams be realized? Is there a particular reason it isn't supported yet or ever? ---------------------------------------------------------------- Dave Cole (DC1110) | dacole@netcom.ca Systems Administrator |* dacole@rik.net * | office/~dacole/ Netcom Canada |* www.rik.net/~dacole/ * 905 King Street West, Toronto, M6K 3G9 | phone - 416.341.5801 Toronto, Ontario, Canada, Earth, Sol | fax - 416.341.5725 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 9 01:08:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20116 for freebsd-hardware-outgoing; Fri, 9 Oct 1998 01:08:28 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from rnocserv.urc.ac.ru (rnocserv.urc.ac.ru [193.233.85.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20016 for ; Fri, 9 Oct 1998 01:07:21 -0700 (PDT) (envelope-from joy@urc.ac.ru) Received: from urc.ac.ru (y.urc.ac.ru [193.233.85.37]) by rnocserv.urc.ac.ru (8.8.8/8.8.8) with ESMTP id MAA23135; Fri, 9 Oct 1998 12:44:15 +0600 (ESS) (envelope-from joy@urc.ac.ru) Message-ID: <361DB0BF.4C46881B@urc.ac.ru> Date: Fri, 09 Oct 1998 12:44:15 +0600 From: Konstantin Chuguev Organization: Southern Ural Regional Center of FREEnet X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 3.0-BETA i386) X-Accept-Language: ru,en MIME-Version: 1.0 To: Dave Cole CC: freebsd-hardware@FreeBSD.ORG Subject: Re: pcmcia 3com 3c562d support? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dave Cole wrote: > > I've got this card sitting here and I'm praying there is some > initiative to supporting it in freebsd. Any freebsd. > > Will my hopes and dreams be realized? Is there a particular reason it > isn't supported yet or ever? > I asked this question several months ago. No progress since that time. :-( I am ready to try to write the driver myself. I think it should not differ much from the ep driver. Anybody has specs/docs on this card? I heard Linux supports it. -- Konstantin V. Chuguev. System administrator of Southern http://www.urc.ac.ru/~joy/ Ural Regional Center of FREEnet, mailto:joy@urc.ac.ru Chelyabinsk, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 9 06:53:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05547 for freebsd-hardware-outgoing; Fri, 9 Oct 1998 06:53:55 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA05507 for ; Fri, 9 Oct 1998 06:53:28 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id PAA00867; Fri, 9 Oct 1998 15:52:26 +0200 Message-ID: <361E1518.9BC322C@we.lc.ehu.es> Date: Fri, 09 Oct 1998 15:52:24 +0200 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: 3.0R on Iwill DBL100 or Asus P2B-DS ? 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 FreeBSDers! We are planning the purchase of five dual-processor PC-stations which will run, of course, under FreeBSD 3.0-RELEASE. Now we are looking for a good motherboard. We usually work with two computer suppliers: one uses Iwill motherboards, and the other uses Asus. Then, our main options are the Iwill DBL100 and the Asus P2B-DS (we want the SCSI bus). Both motherboards are evenly featured. Both use the BX chipset, admit up to 1GB of SDRAM, include an AIC7890 SCSI controller... We have PCs based on the Iwill PIILS (LX chipset, monoprocessor, AIC7880 SCSI controller), and they work fine with FreeBSD 2.2.7: zero problems. I would very grateful for advice or experiences with any of these motherboards under FreeBSD 3.0. I must say that we want to use the new PC-stations mainly for software development and for running our {CPU,memory,disk}-intensive programs. Cheers, -- JM ----------------------------------------------------------------------- José M. Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-944647700 x2624 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 9 17:12:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26996 for freebsd-hardware-outgoing; Fri, 9 Oct 1998 17:12:27 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bigwoop.vicor-nb.com ([208.206.78.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26986 for ; Fri, 9 Oct 1998 17:12:17 -0700 (PDT) (envelope-from daver@bigwoop.vicor-nb.com) Received: (from daver@localhost) by bigwoop.vicor-nb.com (8.8.5/8.7.3) id RAA16561; Fri, 9 Oct 1998 17:11:25 -0700 (PDT) Date: Fri, 9 Oct 1998 17:11:25 -0700 (PDT) From: Pomegranate Message-Id: <199810100011.RAA16561@bigwoop.vicor-nb.com> To: hardware@FreeBSD.ORG Subject: DPT Raid Controllers Cc: daver@bigwoop.vicor-nb.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello. I'm implementing Raid-1 on some of our servers and have been looking into different options for FreeBSD support. I have read good things about the DPT controllers, but fail to see any real recommendations for model numbers and so on. Does anyone out there have any suggestions/preferences for model numbers? I want a simple, hardware solution for Raid-1, simple mirroring. I have a DPT Sx4030 card to evaluate but it seems that the board may be DOA. Am I on the right track? I noticed that folks claim DPT has FreeBSD support, which is why I'm interested in their products. Any help would be much appreciated. dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 10 02:18:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11378 for freebsd-hardware-outgoing; Sat, 10 Oct 1998 02:18:12 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11368 for ; Sat, 10 Oct 1998 02:18:02 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA11140 for ; Sat, 10 Oct 1998 18:47:51 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA20920; Sat, 10 Oct 1998 18:47:49 +0930 (CST) Message-ID: <19981010184749.Y3369@freebie.lemis.com> Date: Sat, 10 Oct 1998 18:47:49 +0930 From: Greg Lehey To: FreeBSD-hardware@FreeBSD.ORG Subject: Which IBM IDE disk? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog 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 6 months ago I bought an IBM DHEA 36480 (6 GB Ultra DMA IDE drive, also nicknamed "Deskstar 5"), with which I have been well pleased. Now it looks as if another drive is dying, and I'm looking around for a second IBM IDE drive. Well, the Deskstar 5s are gone, and the Deskstar 8s which replaced them are on their way out, and now there's the Deskstar 16. I end up with the choice between a DHEA-38541 (DS 8) or a DTTA-350840 (DS 16), both 8.4 decimal GB. The DHEA costs SGP $338 in Singapore, the DTTA costs $369. I've looked at the IBM web site, and I can't find any significant difference between the three series. They all have a 9.5 ms average positioning time, the same average latency, the same rotational speed, a 512 kB buffer from which the firmware steals a chunk, the same interface, and documents which are laid out completely differently just to confuse me. Does anybody know a reason I should shell out $31 more for the DTTA? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 10 07:34:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11977 for freebsd-hardware-outgoing; Sat, 10 Oct 1998 07:34:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11963 for ; Sat, 10 Oct 1998 07:34:13 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id PAA06555; Sat, 10 Oct 1998 15:33:40 +0100 (BST) Message-ID: <361F7012.60C13628@tdx.co.uk> Date: Sat, 10 Oct 1998 15:32:50 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey CC: FreeBSD-hardware@FreeBSD.ORG Subject: Re: Which IBM IDE disk? References: <19981010184749.Y3369@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg Lehey wrote: > > I've looked at the IBM web site, and I can't find any significant > difference between the three series. They all have a 9.5 ms average > positioning time, the same average latency, the same rotational speed, > a 512 kB buffer from which the firmware steals a chunk, the same > interface, and documents which are laid out completely differently > just to confuse me. Does anybody know a reason I should shell out $31 > more for the DTTA? > > Greg Hi Greg, I think the DS16 has a much better media transfer rate compared to the DS8... The DS16 also has a faster sustained data rate (13 to 8Mb/sec for the DS16 vs. 10.2 to 5.8Mb/sec for the DS8)... I guess it depends on how much the $31 extra is worth to you... ;-) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 10 08:20:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16166 for freebsd-hardware-outgoing; Sat, 10 Oct 1998 08:20:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA16146; Sat, 10 Oct 1998 08:20:17 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA05659; Sat, 10 Oct 1998 11:25:26 -0400 From: Bill Paul Message-Id: <199810101525.LAA05659@skynet.ctr.columbia.edu> Subject: Call for testers for PNIC ethernet driver To: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Date: Sat, 10 Oct 1998 11:25:25 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I know I'm going to regret this, but: this is a call for testers for a preliminary driver for PNIC-based ethernet adapters. This includes the latest LinkSys LNE100TX 10/100 adapters, certain newer NetGear cards, and others. The LinkSys cards have the chip marked with the part number 82c168 or 82c169. I know I said I was going to do a driver for the Winbond fast ethernet chip next, but I haven't found a vendor for a board yet. Incidentally, if anyone knows where to order a board with a Winbond W89C840F chip, please let me know. (That's 840, not 940; the 940 is 10Mbps only and is an NE2000 clone.) Note: my two usual test machines were shipped to Berlin for a demo at a conference by some of the lab crew. This left me with just the one SMP box and no neigboring machine with which to do decent speed tests. (I usually hook the card up to another working system with a crossover cable and stuff it full of traffic to see what happens.) All I can say for now is that the driver is stable enough that I left it in the test box overnight as the primary interface and it hasn't fallen over. I have not been able to pound on it to really evaluate performance, nor have I tested it at all speeds and modes, however it should autonegotiate all modes correctly (right now it's linked to a switch at 100Mbps/full-duplex). Yes, this is a separate driver, not a patch to the de driver. The de driver scares me. Also, the de driver uses a fixed size ring buffer descriptor layout, whereas I'm partial to using linked lists. This actually proved to be a bit of a problem as I encountered some unusual behavior with the PNIC. With my linked list strategy, it's necessary to reload the chip's transmit list base pointer register (if the chip hits the end of a list, you want to give it a new one). However after several hours of hammering on it, I could not find a way to properly update the chip's pointer after it had been loaded the first time. Even after shutting the transmitter off, updating the register, and observing that its contents had changed, the chip would refuse to transmit from the newly loaded list. (Instead, it would yield 'no tx buffer available' errors). The only way to really clear the pointer is to do a soft reset of the chip, but that trashes the rest of the chip state. My solution to this was to allocate one extra descriptor (called the kludge descriptor) and tack it on the end of each list with the 'own' bit cleared. This would cause the chip to go idle when it hit the end of the current list with its pointer set to the address of the kludge descriptor, which I could then update to point to anther arbitrarily located list. It means loading an extra descriptor into the chip for each frame, which sucks, but which hopefully won't impact performace that much. Also, the PNIC chip apparently has an internal transceiver which can be used instead of an external PHY, however the LinkSys card that I have uses an external PHY chip so that's what the driver supports. I get the feeling that most of the PNIC-based cards use an external PHY anyway. The driver source code can be obtained from the following locations: http://www.freebsd.org/~wpaul/PNIC/3.0 source for FreeBSD 3.0 http://www.freebsd.org/~wpaul/PNIC/2.2 source for FreeBSD 2.2.x To add the driver to an existing system, do the following: - Download if_pn.c and if_pnreg.h for your system and copy them to /sys/pci. - Edit /sys/conf/files and add a line that says: pci/if_pn.c optional pn device-driver - Edit your kernel config file (e.g. /sys/i386/conf/GENERIC) and add a line that says: device pn0 - Config and compile a new kernel and boot it. Please report successes or failures to wpaul@skynet.ctr.columbia.edu. Bear in mind that I can't really do proper tests at 100Mbps until my two test machines get back from Berlin; if you do have problems, give detailed descriptions. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 10 10:26:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02761 for freebsd-hardware-outgoing; Sat, 10 Oct 1998 10:26:29 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02756; Sat, 10 Oct 1998 10:26:25 -0700 (PDT) (envelope-from rkw@Dataplex.NET) Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id MAA03922; Sat, 10 Oct 1998 12:47:12 -0500 (CDT) (envelope-from rkw@dataplex.net) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199810101525.LAA05659@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 10 Oct 1998 12:24:18 -0500 To: Bill Paul From: Richard Wackerbarth Subject: Re: Call for testers for PNIC ethernet driver Cc: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 10:25 AM -0500 10/10/98, Bill Paul wrote: >I know I'm going to regret this, but: this is a call for testers for a >preliminary driver for PNIC-based ethernet adapters. I'll give it a try. >However after several hours of hammering on it, I could not find a >way to properly update the chip's pointer after it had been loaded >the first time. Even after shutting the transmitter off, updating the >register, and observing that its contents had changed, the chip would >refuse to transmit from the newly loaded list. (Instead, it would yield >'no tx buffer available' errors). The only way to really clear the >pointer is to do a soft reset of the chip, but that trashes the rest of >the chip state. > >My solution to this was to allocate one extra descriptor (called >the kludge descriptor) and tack it on the end of each list with >the 'own' bit cleared. This would cause the chip to go idle when >it hit the end of the current list with its pointer set to the >address of the kludge descriptor, which I could then update to >point to anther arbitrarily located list. It means loading an >extra descriptor into the chip for each frame, which sucks, but >which hopefully won't impact performace that much. Sounds like the 1394 driver that I wrote last year. I was able to do a slight variation on your theme. I had a single kludge descriptor per DMA channel. When I was ready to queue a new batch of output, I set the last link of the batch chain to point to the kludge. I then went back and changed the link of the (remembered) previous chain to point to the head of my addition. There was the usual race condition. If the hardware "won", it jumped off to the kludge and gave its halt interrupt. If "I" won, the hardware saw the list as if it had always been a single chain and never knew that the kludge block had been at its earlier location. In my case, I was able to keep the channel busy most of the time and rarely took the extra hit. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message