Date: Wed, 4 Dec 1996 12:11:03 -0700 (MST) From: Nate Williams <nate@mt.sri.com> To: Greg Lehey <grog@lemis.de> Cc: nate@mt.sri.com (Nate Williams), FreeBSD-current@freebsd.org (FreeBSD current users) Subject: Re: Installation: still not perfect Message-ID: <199612041911.MAA11167@rocky.mt.sri.com> In-Reply-To: <199612041850.TAA19392@freebie.lemis.de> References: <199612041819.LAA10954@rocky.mt.sri.com> <199612041850.TAA19392@freebie.lemis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> 2. This machine doesn't have a CD-ROM, so I had intended to install > >> via the Ethernet board. The boot kernel recognizes the Ethernet > >> board, thinks it initializes it, but nothing comes out. > > > > It may be using the wrong network connector. You may have to tell it to > > use a different connector using the '-link0 link1' OR 'link0 -link1' > > flags. > > That's a point. In the meantime, unfortunately, the diagnostics no > longer run, and I can't get the board recognized. They seem to expect > a Microsoft hard disk already installed, and after overwriting the > hard disk, they die with a spurious error message: > > Can't Run Install, files missing. Make sure you have INSTALL.EXE, > INST1.SAC and STRINGS.BIN in your directory (-1, 2) Hmm, you *should* be able to boot off an empty DOS disk and then run the program 3X589CFG.EXE and check everything out. > > The boot disk you have supports the 3Com PCMCIA cards fine, *as long* as > > the driver is configured to use the IRQ/port/IOMEM values stored in the > > card's ROM *AND* the correct network adaptor is selected using the link > > flags. > > The values were correct. They don't seem to be any more; now the > probes don't find the board any more, and I can no longer change them, > since the diagnostic is broke. See above. > >> 3. It may be that the Ethernet board is defective. It's difficult to > >> be sure: 3Com have designed what must be a superlative in their > >> line of decreasingly useful diagnostic software. I returned one > >> Ethernet board after the diagnostics said it was bad, but the > >> other one behaves just the same: if I write the config info first, > >> the diag software passes, but if I then stop the program and > >> re-enter, it fails again (can't find the registers). Has anybody > >> else seen this? > > > > Hmm, I haven't seen this. Are you using card-services before you run > > the configuration file. > > No. Why should I? I thought that was only for Microsoft users. I > don't have any Microsoft stuff on this machine any more. I meant *when* you were running the Diagnostics. > >> 5. OK, let's do a floppy install of the minimum necessary. That > >> doesn't work either, although I stuck to the letter of what the > >> installation scripts say. Looking at the debug output under F2, > >> it shows that it succeeded in mounting the disks (I tried both > >> MS-DOG and ufs formats) on /dist, and then went looking for > >> /dist/bin/bin.tgz and /dist/bin/bin.inf, which it didn't find. > >> There's nothing in any documentation I know about which even > >> mentions these files. > > > > Hmm, unless the documentation has changed, it *specifically* says to > > create the dists directories on the floppies. > > Yes, it does, and that's what I did. The first floppy contained > \BIN\BIN.AA through \BIN\BIN.AE. Hmm... *JORDAN*???? k > 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? You can try the PAO boot floppy. See: http://www.mt.cs.keio.ac.jp/person/hosokawa/PAO/ Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612041911.MAA11167>