M. Warner Losh wrote:
I was unaware of this problem. It may be related to other problems
that have surfaced in some code I recently MFC'd.
Warner
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Perharps, it is the same problem I got with a dc card one week ago, and
which seemingly did not interested anyone.
Using black magic, I solved it by putting:
hw.cbb.start_32_io="0x4000"
in my loader.conf...
I found it by googling, and trying a trick used for a different card, in
a different computer, with a different version of FreeBSD !
I do not know why it works, but it works...
Is there somewhere a tool or a set of procedures to diagnostic/solve
this kind of port allocation problems, which manifest itself with
different kind of messages (as I found when trying the same card on
another computer) ??
Claude Buisson
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
