From owner-freebsd-hackers Thu Feb 20 10:37:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA28431 for hackers-outgoing; Thu, 20 Feb 1997 10:37:56 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA28397; Thu, 20 Feb 1997 10:37:39 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-45.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA20592 (5.67b/IDA-1.5); Thu, 20 Feb 1997 19:37:25 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id TAA11622; Thu, 20 Feb 1997 19:37:21 +0100 (CET) Message-Id: <19970220193720.BV28868@x14.mi.uni-koeln.de> Date: Thu, 20 Feb 1997 19:37:20 +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. References: <19970218205749.IK34225@x14.mi.uni-koeln.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 In-Reply-To: ; from Maxim A. Bolotin on Feb 20, 1997 19:30:37 +0300 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Feb 20, max@rnd.runnet.ru (Maxim A. Bolotin) wrote: > OK, Here's what I have with controller pci0 > > Probing for devices on the EISA bus > ahc0: at 0x9c00-0x9cff irq 11 > ahc0: on eisa0 slot 9 > pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x81000800 > pcibus_setup(2): mode 2 enable port (0x0cf8) is 0x00 > pcibus_setup(2a): mode2res=0x0e (0x0e) > pcibus_setup(2a): now trying mechanism 2 > pcibus_check: device 0 1 2 3 is there (id=00000021) > Probing for devices on PCI bus 0: > configuration mode 2 allows 16 devices. > vga0 rev 0 int _ irq ?? on pci0:3 > vga1 rev 0 int _ irq ?? on pci0:7 > vga? mirrored on pci0:11 > vga? mirrored on pci0:15 > Probing for devices on the ISA bus: Ok, I see ... Thanks for sending this message log! The problem is, that EISA and PCI use overlapping port regions, and for the probe code, it appears as if there really was a PCI device in slot 3. The value read is valid, and while no device with that ID exists, the code can't possibly know. I've got an idea for another test, which would find that there isn't really a PCI bus in your system. But that test will need to write into EISA address space ports, and while I can restore the values previously read, I can't be sure that the device has not been confused by the test ... As soon as I have a patch ready, you'll receive it for testing. Regards, STefan