Date: Fri, 02 Feb 2001 17:17:48 -0500 From: Doug Ledford <dledford@redhat.com> To: Mike Panetta <mpanetta@applianceware.com> Cc: aic7xxx@FreeBSD.ORG Subject: Re: aic7xxx-2.1.0 kernel 2.2.18 and a serverworks based board. (BROKEN) Message-ID: <3A7B320C.38DC9E2F@redhat.com> References: <20010202105340.A12967@tetsuo.applianceware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Panetta wrote: > > The driver cannot detect the built in scsi controller > on this board. I think its due to the fact that the > controller is on the second PCI bus. I cannot get > the driver to work as a built in or as a module. > As a built in the driver message never shows up. > As a module the driver says device or resource > busy when I insmod it. This is usually a sign > that the device was not detected. > > Can anyone help? You'll have to update the PCI scan code to get that to work. It obviously has one of the new ServerWorks chipsets in it, since the older models are well supported in 2.2.18. In order to make yours work, there has to be a new entry added for your chipset in the arch/i386/bios32.c file. You can try just adding your new DEVICE_ID number for your chipset into the table dev_ex_table[] in that file by copying one of the existing server works entries and see if that solves your problem (it likely will, I don't think they changed the address of the bus number registers, they likely just added a new device ID that isn't in the table yet to support some more advanced features). -- Doug Ledford <dledford@redhat.com> http://people.redhat.com/dledford Please check my web site for aic7xxx updates/answers before e-mailing me about problems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A7B320C.38DC9E2F>