Date: Tue, 18 Feb 1997 20:57:49 +0100 From: se@freebsd.org (Stefan Esser) To: max@rnd.runnet.ru (Maxim A. Bolotin) Cc: se@freebsd.org (Stefan Esser), hackers@freebsd.org Subject: Re: Acer ALTOS 7000 instalation problem. Message-ID: <19970218205749.IK34225@x14.mi.uni-koeln.de> In-Reply-To: <Pine.BSF.3.95q.970218131354.29469B-100000@altos.rnd.runnet.ru>; from Maxim A. Bolotin on Feb 18, 1997 13:21:11 %2B0300 References: <19970217201949.SG24812@x14.mi.uni-koeln.de> <Pine.BSF.3.95q.970218131354.29469B-100000@altos.rnd.runnet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 18, max@rnd.runnet.ru (Maxim A. Bolotin) wrote:
> On Mon, 17 Feb 1997, Stefan Esser wrote:
> > 1) Chip set (vendor and type)
> Acer ALTOS 7000, Acer BIOS V1.2R1.0, 1993,
> 7 EISA slots, AIC 7770, twin channel.
Hmmm, I still have no idea what the chip-set might be ...
> > 2) Version of FreeBSD (2.1.x or 2.2.x)
> It was with 2.1.0, 2.1.5, 2.1.6, and NOW with 2.2-GAMMA:
Ok. I should look into this :)
> FreeBSD 2.2-970205-GAMMA #0: Mon Feb 10 19:03:30 MSK 1997
> It's my kernel, without contorller pci0.
Ok. Obviously it works without pci0 defined. Now we need
to find out, what goes wrong if it is enabled ...
> ahc0: <Adaptec aic7770 SCSI host adapter> at 0x9c00-0x9cff irq 11
> ahc0: on eisa0 slot 9
This appears to be your only EISA card ...
> > You can build a kernel without PCI support
> > (remove the line "controller pci0" and all
> > the PCI specific drivers), and install it
> > under a non-default name, eg. /kernel.altos.
> I know about it, I have worked my computer, but I can't do normal
> upgrade procedure 'cause I can't boot from standart boot floppy.
> Can I turn off controller pci0 in visual config or something ?
No, sorry, the PCI can't be deactivated from
the user config screen.
> I think it's a common problem, or maybe not. Maybe only Acer hang out
> after pci probing :-(.
No, this is not a common problem ...
There have been a few PCI chip-sets, that failed
to follow the PCI specs. To compensate for that,
I had to implement certain heuristics, in order to
identify those broken chips. But these heuristics
may cause problems on some systems with EISA bus.
Could you please apply the following patch, build
a kernel with pci0, boot with "-v", and send me
the boot messages ?
I would also like to know the numbers from all
messages that contain "pcibus_setup" or other PCI
bus specific messages from the 2.2 boot floppy
kernel. You may have to write down those numbers,
since the system will not work with that kernel.
(I don't need the text of the messages, but the
(1), (1a), ... that identify those PCI lines.)
Thanks in advance, STefan
Index: /sys/i386/isa/pcibus.c
===================================================================
RCS file: /usr/cvs/src/sys/i386/isa/pcibus.c,v
retrieving revision 1.27
diff -C2 -r1.27 pcibus.c
*** pcibus.c 1996/10/30 22:38:55 1.27
--- pcibus.c 1997/02/18 19:49:52
***************
*** 200,203 ****
--- 200,204 ----
*/
+ #ifdef undef
if ((oldval1 & CONF1_ENABLE_MSK) == 0) {
***************
*** 232,235 ****
--- 233,237 ----
};
}
+ #endif
/*---------------------------------------
***************
*** 244,247 ****
--- 246,250 ----
}
+ #idef undef
if ((oldval2 & 0xf0) == 0) {
***************
*** 265,268 ****
--- 268,272 ----
}
}
+ #endif
/*---------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970218205749.IK34225>