Alfred Perlstein wrote:
> * Terry Lambert <[EMAIL PROTECTED]> [020224 13:12] wrote:
> > Try the following patch; the failure message will be
> > somewhat less cryptic, since it will tell you the
> > proximal reason for failure out of the 5 possibles
> > for the message you are seeing. 8-).
>
> C
* Terry Lambert <[EMAIL PROTECTED]> [020224 13:12] wrote:
>
> Try the following patch; the failure message will be
> somewhat less cryptic, since it will tell you the
> proximal reason for failure out of the 5 possibles
> for the message you are seeing. 8-).
Cool explanation, the attached patch
In the last episode (Feb 24), Terry Lambert said:
> zhuravlev alexander wrote:
> > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> > unknown: can't assign resources
> > unknown: can't assign resources
> > unknown: can't assign resources
> > unknown: can't assign resources
> > unknow
Michael Smith wrote:
> > It is if you have your BIOS configured incorrectly with
> > regard to whether you are running a "PNP OS".
>
> It's also normal if you have hints loaded for things that could have been
> autoconfigured, which is what the above seems to suggest.
OK. 8-). I've always seen
> This is a multi-part message in MIME format.
> --741846253D1D9002AE8EAD96
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> zhuravlev alexander wrote:
> > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> > unknown: can't assign resources
>
zhuravlev alexander wrote:
> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> unknown: can't assign resources
> unknown: can't assign resources
> unknown: can't assign resources
> unknown: can't assign resources
> unknown: can't assign resources
> unknown: can't assign resources
>
