Out of curiosity, do only 3c509's exibit this behavior, or is this
the core problem with 3c59x's as well? My experiences have not
been consistent with these cards, and I had assumed it was due
to buggy code in the 3-Com chipset. I've noticed flaky behavior from the
"Vortex" [3c59x] card as well
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
This sounds like a necessary consequence of the "PCI crapshoot."
On Tue, 23 Jan 2001, Mike Meyer wrote:
> Mike Smith <[EMAIL PROTECTED]> types:
> > > After installing a fresh cvsup last Sunday, I find that my usb printer
> > > quit working. Some investigation shows that this is because the uh
Just out of curiousity, has anyone documented how much of a performance
hit there is with the i386 code enabled in the kernel?
Regards,
Glen Gross
On Thu, 18 Jan 2001, Mike Smith wrote:
> > > That's one of the big reasons that we're 4.x based right now rather
> > > than 3.x based, despite 4
OK, but it makes sense to me that for certain applications, it makes sense
to utilize the old hardware since it is still readily available and cheap.
In particular, why not install FreeBSD on i386 for use in routers? In
many cases there is a negligible performance advantage from using faster
CPU
Since my last cvsup, my Soundblaster AWE-64 card is no longer
detected.
unknown: can't assign resources
unknown: can't assign resources
unknown0: at port 0x620-0x623 on isa0
Has anyone else seen this problem? Below is the full dmesg output.
Copyright (c) 1992-2000 The FreeBSD Project.
Is it possible to use an old Intel EtherExpress-16 card with FreeBSD?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Is it possible to use the old Intel EtherExpress-16 cards with FreeBSD?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
