Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!in1.uu.net!van-bc!news.mindlink.net!news From: mike_imai@mindlink.bc.ca Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: ncr 53c810 Date: 3 Oct 1995 02:32:12 GMT Organization: MIND LINK! - British Columbia, Canada Lines: 49 Message-ID: <44q7bc$jlu@fountain.mindlink.net> References: <44k1as$lm1@fountain.mindlink.net> <44n92v$kfv@uriah.heep.sax.de> <44pgiu$r0p@news.rrz.uni-koeln.de> Reply-To: mike_imai@mindlink.bc.ca NNTP-Posting-Host: line099.nwm.mindlink.net X-Newsreader: IBM NewsReader/2 v1.2 In <44pgiu$r0p@news.rrz.uni-koeln.de>, se@MI.Uni-Koeln.DE (Stefan Esser) writes: >In article <44n92v$kfv@uriah.heep.sax.de>, j@uriah.heep.sax.de (J Wunsch) writes: >|> <mike_imai@mindlink.bc.ca> wrote: >|> >|> >ncr0 < ncr53x810> inta, irq10 on pci0:9 >|> >reg20: virtual 0xf3166000 >|> >physical 0xc0000000 >|> >Core test failed: host wrote 1, ncr read 1 >|> >Core test failed: ncr wrote 2, host read 1 >|> >Core test failed: ncr wrote 2, host read -1 >|> >Cache incorrectly configured. >|> >|> >What does the error mean & how can i work around it? >|> >|> Looks like your chipset is broken. Try turning off write-back >|> caching. > >While Jvrg is right in general, I have to correct >him in this particular case ... > >(I've got to know, since it's at least partially >my fault, that the code breaks on your system :) > >Anyway, the PCI code in 2.0R didn't know how to >deal with systems, that could only map PCI chips >into a small range of addresses (i.e. combined >PCI+VLB motherboards). > >The code has been fixed, and I might be able to >send you a patch that makes your system work >(which obviously only will help you, if you got >access to some other system to build a modified >kernel on ...) > >Let me know whether you want to give it a try ... > >Regards, STefan >-- > Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 > Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 > ============================================================================== > http://www.zpr.uni-koeln.de/staff/esser/esser.html <se@ZPR.Uni-Koeln.DE> if the problem has been fixed and is in the soon to be released 2.1, I will wait until 2.1 is released. Thanks for the responses mike i.