Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!mel.dit.csiro.au!kimba.catt.citri.edu.au!tim From: tim@kimba.catt.citri.edu.au (Tim Liddelow) Subject: Re: /386bsd: reject 65340 Message-ID: <1992Sep19.084637.17954@mel.dit.csiro.au> Sender: tim@kimba (Tim Liddelow) Organization: CATT Centre at CITRI, Melbourne, Australia References: <3594@ra.nrl.navy.mil> <1992Sep18.085534@IASTATE.EDU> <rwa.716836288@aupair.cs.athabascau.ca> <19d7v2INN75q@frigate.doc.ic.ac.uk> Date: Sat, 19 Sep 92 08:46:37 GMT Lines: 39 In article <19d7v2INN75q@frigate.doc.ic.ac.uk>, kd@sophia.doc.ic.ac.uk (Kostis Dryllerakis) writes: |> |> In article <rwa.716836288@aupair.cs.athabascau.ca>, rwa@aupair.cs.athabascau.ca (Ross Alexander) writes: |> > jzelle@IASTATE.EDU (James A Zelle) writes: |> > >In article <3594@ra.nrl.navy.mil>, deal@hightop.nrl.navy.mil (Richard |> > >Deal) writes: |> > >>/386bsd: reject65340 messages. The number is mostly 65340 but is |> > >>some times 65342, 65344, 65366. if I type |> > >I'm having a similar problem with a Western Digital Ethernet card, |> > >except I think the error says "reject655341" in my case. The error |> > >goes away when the Ethernet cable is disconnected, so it appears that |> > >386BSD doesn't like what it sees on the network. Any ideas? |> > |> > This problem arises from having shadow memory enabled in the range of |> > addresses (0xD0000 - 0xD03FFF as I remember) that the dual-port ram in |> > the WD8013 card corresponds to. Turn off any shadowing or caching in |> > this region via your BIOS EAPROM setup firmware and the problem will |> > go away (your mileage may vary :). |> > |> It might not be that easy. We have a NEC 386PC of some age having |> the same problem. No CMOS setup is available in ROM (or that is what we |> think) and no shadow RAM should appear. |> What seems curious is the fact the the WE card is recoginsed at |> boot time as being in IRQ 9 instead of IRQ 2 mentioned in the documentation. |> The card WD8003E is set to IRQ2 and -the funny bit- it will not accept a |> jumper setting for IRQ 9. |> IRQ9 is really a redirected IRQ2. Reconfiguring the WE card on another IRQ (say 5) may help. Again, your mileage may vary. ________________________________________________________________________________ Tim Liddelow for(;;) fork(); Systems Programmer Centre of Advanced Technology in Telecommunications My brain on a bad day. CITRI, Melbourne, Australia internet : tim@kimba.catt.citri.edu.au Phone : +61 3 282 2455 Fax : +61 3 282 2444 ________________________________________________________________________________