On Thu, Dec 16, 1999 at 02:03:10 +, W.H.Scholten wrote:
> Kenneth D. Merry wrote:
>
> > In general, the stock NCR driver isn't being actively maintained, and your
> > problem could be the result of a bug in the driver, or some problem with
> > your MO drive. It's hard to say for sure. Gerar
Kenneth D. Merry wrote:
> In general, the stock NCR driver isn't being actively maintained, and your
> problem could be the result of a bug in the driver, or some problem with
> your MO drive. It's hard to say for sure. Gerard's driver is actively
> maintained, though, so if you still have prob
On Thu, Dec 16, 1999 at 00:49:47 +, WHS wrote:
> Thomas David Rivers wrote:
> >
> > >
> > > The kernel hangs (rather an endless loop) with messages like:
> > >
> > > ncr0: timeout nccb=0xc0c38000
> > >
> > > if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the
> >
Thomas David Rivers wrote:
>
> >
> > The kernel hangs (rather an endless loop) with messages like:
> >
> > ncr0: timeout nccb=0xc0c38000
> >
> > if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the
> > ncr source it seems there's a problem with the script stuff in case
>
> The kernel hangs (rather an endless loop) with messages like:
>
> ncr0: timeout nccb=0xc0c38000
>
> if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the
> ncr source it seems there's a problem with the script stuff in case of a
> timeout. Anyway, this doesn't hap
L.S.
The kernel hangs (rather an endless loop) with messages like:
ncr0: timeout nccb=0xc0c38000
if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the
ncr source it seems there's a problem with the script stuff in case of a
timeout. Anyway, this doesn't happen with ei
6 matches
Mail list logo
