Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!serv.hinet.net!news.uoregon.edu!tezcat!news.bbnplanet.com!cam-news-hub1.bbnplanet.com!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Problems: EISA+1542; NE2000(PCI); onboard MACH-64 Date: 5 Jan 1997 17:15:05 GMT Organization: Private BSD site, Dresden Lines: 50 Message-ID: <5aonip$8lr@uriah.heep.sax.de> References: <32CE572F.2781@datatone.co.uk> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33600 Dave Humphreys <dave@datatone.co.uk> wrote: > (list of other DEBUG: messages) > > sd0(aha0:0:0): timed out > sd0(aha0:0:0): timed out > adaptor not taking commands.. frozen?! This is normally a typical symptom for SCSI cabling or termination problems. > My hunch is that the early disk access is done via the BIOS, which > works, and the later disk access is done via the aha0 driver, which > doesn't. Quite possible that the aha driver knocks much harder on the SCSI bus, e.g. the system BIOS might not use sync transfers, or uses it at a lower data rate. I think if you boot with -v (to the least then), the aha driver will tell you what it negotiated with the drive. Running the bus at lower speed makes it less likely to trigger cabling or termination problems. > Is it possible to configure the NE2000 driver to operate at other IO > port addresses? Will the driver work when it is addressing a PCI card > rather than an ISA card (even though it is a compatible type)? It is possible, and meanwhile (FreeBSD 2.2), there's also a PCI version of the `ed' driver. This will probably solve your hassles once and forever. > 2) I have not managed to get the X-server to operate as a MACH-64. > Windows 95 seems to work with an "ATI Graphics Pro Turbo PCI" driver on > this machine, so I had much hope. Which version? XFree86 3.1.2, or 3.2? > the xf86config program did not result in success. I have fiddled about > with many options, but I have virtually no information about the > hardware. Every time I try to start the server when configured for > Mach-64, the screen goes blank and the machine hangs. This is a typical symptom when using the 3.1.2 server: the chip is too new for that one. Upgrading is your only (and best) option. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)