Date: Tue, 29 Nov 2005 13:25:16 +0100 From: Olaf Greve <ogreve@millennics.com> To: Olaf Greve <o.greve@axis.nl> Cc: amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... Message-ID: <438C48AC.30803@millennics.com> In-Reply-To: <438C2322.8020801@axis.nl> References: <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, A little bit of further information (which I just checked on the machine when I went home for lunch): I identified the Texas Instruments device. It's not the memory (which of course makes sense), but rather, it seems to be a FireWire controller. (TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI]) ). When considering the following FreeBSD output: twa0: <3ware 9000 series storage controller> port 0xa000-0xa0ff mem 0xd8005000-0xd80050ff, 0xd2000000-0xd27fffff irq 16 at device 6.0 on pci5 And: fwohci0: <Texas Instruments TSB43AB22/A> irq 16 at device 11.0 on pci5 Could this perhaps be the culprit??? I don't recall having seen any way to disable FireWire on the MoBo, but perhaps there is... Also, I checked the chipset: it's nForce 4. Hopefully this additional information contributes to identifying the clashing devices... Cheers, Olafo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?438C48AC.30803>