On Wed, Jan 06, 2010 at 03:27:23PM -0700, Brandan Rowley wrote:
You're welcome.
This is the one I heard about. Supposedly good stuff, but were
announced a month after I got my san cards so I didn't get to try to buy
any.
Haven't heard anything memorable about or tried.
This (A102u) I have working on 4.6
$ dmesg | grep -e OpenBSD -e san
OpenBSD 4.6-stable (GENERIC.MP) #7: Tue Nov 24 10:26:10 MST 2009
san0 at pci0 dev 4 function 0 "Sangoma A10x" rev 0x01 apic 3 int 1 (irq 11)
san1 at pci0 dev 8 function 0 "Sangoma A10x" rev 0x01 apic 3 int 6 (irq 10)
$ ifconfig | grep ^san
san0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
san1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
san2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
san3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
<SNIP>
I have several of the A102u, but if I remove the daughter board it is
magically an A101u, tho I have not tried that on 4.6, but did
(successfully) in earlier versions.
I have several messages in the archives and on gnats from when I was
getting them going, but when I upgraded to 4.6 they just "worked" same
as they have since I installed them.
They actually seem to DDB less and less as I upgrade to newer versions
of OpenBSD. Not that they would ever DDB often, generally only if I
reboot instead of halt and powercycle or if something goes on with an
AT&T line and they run their automated tests. One of their tests used
to cause it, and may still, but I haven't had reason to find out.
l8rZ,
--
andrew - ICQ# 253198 - Jabber: andrew@rraz.net
BOFH excuse of the day: Incorrectly configured static routes on the
corerouters.