From owner-freebsd-current Thu Dec 5 08:00:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA16233 for current-outgoing; Thu, 5 Dec 1996 08:00:09 -0800 (PST) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA16222 for ; Thu, 5 Dec 1996 08:00:05 -0800 (PST) From: Greg Lehey Received: from freebie.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vVgAH-000QrsC; Thu, 5 Dec 96 16:56 MET Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) id QAA18105; Thu, 5 Dec 1996 16:55:52 +0100 (MET) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199612051555.QAA18105@freebie.lemis.de> Subject: Re: Installation: still not perfect In-Reply-To: <199612050059.LAA18644@genesis.atrad.adelaide.edu.au> from Michael Smith at "Dec 5, 96 11:29:55 am" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Thu, 5 Dec 1996 16:30:23 +0100 (MET) Cc: FreeBSD-current@FreeBSD.ORG (FreeBSD current users) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > Greg Lehey stands accused of saying: >> >> Another question: I also have another PCMCIA board here, which appears >> to be an NE2000 clone. Without PCMCIA, it wasn't recognized. Is >> there any chance of getting it to run with the PCMCIA stuff >> configured? > > It's perhaps worth making a distinction between the two different sorts > of PCCARD support in the kernel : > > - there are some drivers (zp etc.) that recognise PCCARD devices. > - there are some drivers (ed, sio, etc.) that can be told to look at > a PCCARD. > > The latter class require the FreeBSD equivalent of "Card Services", ie. > the 'pcic' and 'crd' drivers in the kernel, 'pccardd' and the card > database in /etc. Thanks, I think I understand this now. > These aren't available on the normal boot floppy for space reasons. Then there should be another boot floppy. I know, there are good reasons to oppose this, but it shouldn't be at the expense of not being able to install on certain configurations. I think that an ethernet-based install on a laptop should be relatively common. > I fixed the 'ed' driver to support NE2000-style pccards a while back, > but I don't know if this change has been reflected in the latest PAO > boot floppy. At any rate, you're still stuck unless the particular > card you have is registered in the database. What card do you have? I have two cards: one is the 3C589C, which I can't configure because the diagnostic doesn't work. It seems that there might have been card services installed on the machine before I wiped out the Windoze 95% partition, but they didn't give me a diskette, and it seems that card services relate to the machine and not the board, so I don't have any card services at all any more. Without card services, the diagnostic just doesn't run. If somebody out there can send me a copy of CardWizard or whatever for the AcerNote Light, I'd be grateful. The other board is a masterpiece in understatement: the sum total of the description on the card is: PCMCIA TYPE II Ethernet Adapter Well, that's the front side. The back side contains the obligatory FCC notice, advice on how to damage it, and the stick-on label: P/N: 18-0A-40BC S/N: QK007360 There's also a very minimal "manual" (a folded sheet of paper) which tells me that it has drivers for every machine under the Sun, is Ethernet compliant, has a 16 kB data buffer. I've tried booting with the PAO boot floppy, and it recognizes the card, but claims it can't find card type (from memory) " ()" in the card database. This also happens, including the same name, with the 3C589, so I assume this doesn't relate to the board. About the only thing of any interest is the diagnostic diskette, which contains files with names like E2000.EXE, which suggests to me that it is NE2000 compatible. I think I've seen that kind of name before. It fires up the diagnostic reasonably well, and is able to output to the wire (though the stuff it sends out doesn't look correct; the Ethernet address is wrong. I suspect this is yet another Broken Diagnostic). The only problem is that the boot doesn't recognize anything. If your fixes will work on -current, tell me about them. I'm currently interfacing via PLIP (which, to my surprise, gets FTP transfers at about 58 kB/s, but seems to have trouble with NFS), so I can try it out easily enough. Greg