ple who are more familiar with the hardware and the code.
I've updated PR 103435 with this info.
Rich Wales
Palo Alto, CA, USA
[EMAIL PROTECTED]
http://www.richw.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
's causing it.
Needless to say, I'd love to see a fix. Any ideas?
Rich Wales
Palo Alto, CA, USA
[EMAIL PROTECTED]
http://www.richw.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
23:71:66
miibus0: on sk0
e1000phy0: on miibus0
e1000phy0: 1000baseTX-FDX, 100baseTX-FDX, 100baseTX, 10baseTX-FDX, 10baseTX,
auto
Rich Wales[EMAIL PROTECTED]http://www.richw.org
___
freebsd-stable@freebsd.org mailing list
http:/
it appears that the current EG1032's use a Marvell 88E8003
chip, which (AFAICT) isn't supported by any driver in 4.11.
Rich Wales[EMAIL PROTECTED]http://www.richw.org
___
freebsd-stable@freebsd.org mailing list
http
full backup of the old drive in preparation for
copying the data onto the new drive.
Rich Wales[EMAIL PROTECTED]http://www.richw.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
h are MDNS (multicast DNS).
So, I was mistaken; my NIC doesn't have a "promiscuity" problem after
all. Sorry for raising a needless alarm.
Rich Wales[EMAIL PROTECTED]http://www.richw.org
___
freebsd-stable@free
imply impossible (and if so, why)? Thanks for any help.
Rich Wales[EMAIL PROTECTED]http://www.richw.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
What does this mean? Is it a reason for me to worry? Any ideas on
what might have caused it or what I should do about it?
Rich Wales[EMAIL PROTECTED]http://www.richw.org
___
freebsd-stable@freebsd.org mailing list
ide down, with more space around it, and
added another fan, and (touch wood!) I haven't had any more errors from
this drive for about three months now.
Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsub
)? If so,
this seems buggy to me; my desktop really only wants to know about
=one= hardware address for the bridge (not two).
Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
perfectly for me in all respects other
than ARP.
The "rl0" card in my bridge is identified as an "Accton MPX 5030/5038",
and I'm running it in 100baseTX full-duplex mode (connected to another
machine via a crossover cable).
Rich Wales [EMAIL PROTECTED] http://www.w
ands on the other
machines to tell them the bridge's hardware address -- but I really
shouldn't have to do this.
Any ideas?
Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
oblem to the XFree86 people. I also submitted
a FreeBSD PR (misc/23168), though this report got shot down on the
grounds that X isn't part of the FreeBSD base system. (I did post
a followup to my PR, with the above workaround, just in case anyone
else with the problem goes looking for help i
e kernel. For the moment, I think I'll have to stick with -RELEASE
and wait to track -STABLE until I have time to deal with a more involved
upgrade (including being able to back it out in case something doesn't
work -- the machine in question is a semi-production system and I can't
afford t
cable in
cases like this? For example, if an ATA controller has two devices,
and one is ATA-5 (or better?) but the other is not, then ata-dma.c
could say something like "can't do UDMA66 with fast/slow device mix".
Rich Wales [EMAIL PROTECTED] http://www.webcom.co
non-RSAREF code on September 20? Or do we need to wait one more day?
Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
16 matches
Mail list logo