Re: Bug(?) in cardbus code MFC'd to RELENG_6 on 30 January
- From: Claude Buisson <cbuisson@xxxxxxxxx>
- Date: Tue, 28 Feb 2006 00:32:52 +0100
M. Warner Losh wrote:
I was unaware of this problem. It may be related to other problemsPerharps, it is the same problem I got with a dc card one week ago, and
that have surfaced in some code I recently MFC'd.
Warner
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
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@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
- References:
- Bug(?) in cardbus code MFC'd to RELENG_6 on 30 January
- From: László Károly
- Re: Bug(?) in cardbus code MFC'd to RELENG_6 on 30 January
- From: M. Warner Losh
- Bug(?) in cardbus code MFC'd to RELENG_6 on 30 January
- Prev by Date: Re: Bug(?) in cardbus code MFC'd to RELENG_6 on 30 January
- Next by Date: Re: nfs woes in FreeBSD 6.0
- Previous by thread: Re: Bug(?) in cardbus code MFC'd to RELENG_6 on 30 January
- Index(es):
Relevant Pages
|
|