Date: Fri, 7 Apr 2006 10:46:48 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-acpi@freebsd.org Subject: Re: se7520af2 intel motherboard acpi problem Message-ID: <200604071046.50669.jhb@freebsd.org> In-Reply-To: <20060407125705.T67462@netserv1.chg.ru> References: <20060406113433.O6088@netserv1.chg.ru> <200604061103.16570.jhb@freebsd.org> <20060407125705.T67462@netserv1.chg.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 07 April 2006 05:02, Anton Menshutin wrote: > > On Thu, 6 Apr 2006, John Baldwin wrote: > > > Can you give more detail about how the pci-e busses do not work? > > > In dmesg output you can see kernel says nothing about areca raid > controller, which is on pci-e bus. And > pcib5: <ACPI PCI-PCI bridge> at device 0.0 on pci6 > pcib5: secondary bus 8 > pcib5: subordinate bus 8 > pcib5: I/O decode 0xf000-0xfff > pcib5: memory decode 0xfe900000-0xfe9fffff > pcib5: prefetched decode 0xfbc00000-0xfbffffff > device_attach: pcib5 attach returned 6 > what i think means there is a problem during init of pci-e bus. Ah, ok. It would be most helpful if you could add a bunch of printf's to the attach routine in sys/dev/acpica/acpi_pcib_pci.c to see where the error comes from. Oh, I think I've seen this before. This is due to incompetent BIOS writers. Edit sys/dev/acpica/acpi_pcib.c and in the acpi_pcib_attach() function comment out the acpi_DeviceIsPresent() check. The BIOS is claiming that the specific PCI bus doesn't exist. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604071046.50669.jhb>