Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!swrinde!gatech!news.mathworks.com!news-res.gsl.net!news.gsl.net!ix.netcom.com!netcom.net.uk!dispatch.news.demon.net!demon!usenet2.news.uk.psi.net!uknet!usenet1.news.uk.psi.net!uknet!uknet!newsfeed.ed.ac.uk!nerc-keyworth!usenet From: jre@mail.nmh.ac.uk (Russ Evans) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: Help! SCSI error on Mac IIvi Date: 27 Jun 1996 14:08:49 GMT Organization: The Natural Environment Research Council Lines: 33 Message-ID: <4qu4lh$jvk@kwuz.nerc-keyworth.ac.uk> References: <31CE4C0D.6D35@mail.hh.provi.de> NNTP-Posting-Host: mhsg.nerc-murchison.ac.uk X-Newsreader: NN version 6.5.0 CURRENT #3 Thorsten Wollweber <thorsten@mail.hh.provi.de> writes: >I am trying to get NetBSD 1.1 installed on a Mac IIvi. It has Sys 7.5.1 running, a >Apple 24.8 graphics adapter, a FPU, and 12 MB of RAM. I don't have a graphics adapter, but otherwise run the same system. >When I partition a new Seagate ST51080N and install the essential binaries, >everything goes fine until I actually boot the system. Then it confronts me with a >message saying that NetBSD was not testet on this machine, even though it is a Mac >IIvi which is listet in the README as being testet. I'm not working on my Mac at present, so can't check the exact wording, but I always get a similar message -- machine boots fine, anyway. FWIW, both my disks are Quantums, rather than Seagates. >Then at some point (it happens quite often) I get a SCSI error, saying something >like invalid data. I will post more precise error messages if anyone thinks he can >help me. I get a single SCSI error (#5, I think) every time I start up my system. From discussion on the mac68k mailing list, I seem to recall that it simply means that some page or other wasn't downloaded from the device on request, and that the information on that page isn't needed i.e. it's safe to ignore the message. As a general rule, you would be better off giving precise details of the messages which are associated with your problem, as these can be unambiguously traced back, if necessary into the source code. You may also find that you'll get more help on the mac68k mailing list -- few MacBSD users (and even fewer gurus!) seem to read newsgroups. Russ