> In message <199903152134.naa02...@apollo.backplane.com>, Matthew Dillon
> writes:
>
> Shouldn't this be detected by PCI-id rather than by brute force probing ?
Since these are ISA chipsets, no.
They're not (all) PnP devices either, unfortunately.
>
> >:> I had a very weird problem with
In message <199903152134.naa02...@apollo.backplane.com>, Matthew Dillon writes:
Shouldn't this be detected by PCI-id rather than by brute force probing ?
>:> I had a very weird problem with the new parallel port device that caused
>
>Try this patch. This is what I had to do to make my m
:Thanks for the pointer. This seems to have been the problem and I have it
:booting now. As a followup, is it possible to specify boot parameters
:(i.e. splash screen, pnp config, etc) on a machine that is net booting?
:
:Thanks for the help.
:
:Nick
:
:On Sun, 14 Mar 1999, Matthew Dillon wrote:
Thanks for the pointer. This seems to have been the problem and I have it
booting now. As a followup, is it possible to specify boot parameters
(i.e. splash screen, pnp config, etc) on a machine that is net booting?
Thanks for the help.
Nick
On Sun, 14 Mar 1999, Matthew Dillon wrote:
> I
I had a very weird problem with the new parallel port device that caused
this to occur. It turned out to be speculative probing by the parallel
device causing the system to go unstable.
Try disabling the new parallel port device(s)/controllers and see if you
can boot again.
This is a problem I have had on two seperate systems, running
3.0-RELEASE and now 3.1-STABLE built about a week ago. The systems were
brought up seperately.
Unfortunately since this machine never comes up to any usable state, I
don't have detailed logs of its boot output. I'll try to summarize:
