Date: Sun, 18 Feb 1996 16:05:19 -0500 (EST) From: Adam Prato <adamp@ovid.com> To: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> Cc: jkh@cdrom.com, hackers@freebsd.org, nirva@zynet.com Subject: Re: BT946C problems. Can you help? Message-ID: <Pine.A32.3.91.960218154248.94315B-100000@psyche.ovid.com> In-Reply-To: <199602182048.MAA02944@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 Feb 1996, Justin T. Gibbs wrote: > And you ensured that the kernel config for the bt driver matched these > settings every time? In 2.1R, the bt driver used an ISA probe to > find the BT cards, so it cannot change its irq or dma channel on the fly > like new pci probe can even if the driver does properly report what the > card is set too. If you were here, I'd show ya that I'm not seeing things. I didn't understand why when I changed pci slots, the IRQ changed. But when it was in the first slot it came up as irq 10, the second it was irq 11, and third it was irq 12. However now, I changed the cmos settings and set all ports except 11 to ISA, now whatever slot its in, it reports as irq 11. Also the DMA on the card is still off. > > I'm sure that it is mismatched configuration settings. Boot with -c and > set them up correctly to match your hardware and I bet the card will work. > Its most likely the irq since the driver polls during the initial probe > and doesn't require the irq to be set correctly to work during that > phase of the boot process. Doing that now. (was about to send this and then send another with an update but I'm sure you would all rather that I didnt). Here is what happens now: Same thing. Here is what I did - Disabled all IRQ's for PCI in the CMOS setup, thus forcing it to use irq 11. If I let it probe, it returns the correct values of drq 5 and irq 11 - it then proceeds to give me a parity error. If I try and boot the kernel -c, then set 'irq bt0 11' 'drq bt0 5', it boots, gets to the bt0 driver, and gives the same error. If I were to use a boot floppy with a different kernel, would this help my problem at all? Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.A32.3.91.960218154248.94315B-100000>