Hi all,
I would like to extend ng_one2many module to include
automatic link failure datection, failover and FEC functionality.
My question is:
Are interface nodes able to send upstream notification
that their state has changed or do I have to poll their status periodically
as it is done in ng_fe
Hi all,
I finally got some time to do the simple MFC for ida driver. It enables
the automatic drive rebuild on Integrated SmartArray controllers.
I tested enclosed patch on DL380 (controller firmware 1.42) and it works
fine.
Could someone please have a look and commit this simple MFC into -stabl
> > > If you are using a switch you should use FEC or VLANs.
> > > Yes I know there switches out there without that features
> but if you
> > > want more performance then use hardware that can do the
> job you need.
> >
> > Could you please point me to some howto for FEC on FreeBSD ?
>
> See t
> -Original Message-
> From: Bernd Walter [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 26, 2001 19:12
> To: Leo Bicknell
> Cc: [EMAIL PROTECTED]
> Subject: Re: ARP cache problems
>
>
> On Thu, Jul 26, 2001 at 11:35:59AM -0400, Leo Bicknell wrote:
> > On Thu, Jul 26, 2001 at 10:0
Hi all,
I finally got some time to do the simple MFC for ida driver. It enables
the automatic drive rebuild on Integrated SmartArray controllers.
I tested enclosed patch on DL380 (controller firmware 1.42) and it works
fine.
Could someone please have a look and commit this simple MFC into -stabl
Hi all,
I need to MFC changes in ida driver, which start backround
firmware processing on Integrated SmartArray controllers
(this allows automatic on-line rebuild of failed drives).
I am going to do it in next few days. I understood that I shall
avoid all changes for interrupt-entropy harvesting
Hi all,
I asked following question on 'hardware' last week,
but got no answer so far.
Could you please help to clarify the situation?
Thanks in advance,
Milon
--
[EMAIL PROTECTED]
> Perhaps it is a stupid question, but I would like to ask
> what bits are missing in card bus supp
Hi,
Yesterday, I installed on the 4.0R server the apache13-php3 port with mod_ssl (using
4.0R ports skeleton) and it seems that I run into similar problem.
When I try to connect with Netscape 4.x or Exploder 5 to Apache over SSL I get the
following errors in apache_ssl_engine.log:
[18/May/2
David Greenman wrote:
>
> >At the moment I have a spare machine
> >and the NIC available for testing.
> >
> >Please let me know if you are interested
> >in my offer to test your patches to 4.0 driver?
>
>Thanks, Milon. I've attached patches which I believe will fix the problem
> as seen with
David Greenman wrote:
>
> ...
Hi David,
you wrote that you have trouble finding a person
with Intel 82559 based NIC (regular or onboard),
I am willing to assist you as much as I can
to solve this problem.
I alredy looked at the code in FBSD v3.4R and tried
to create workaround a patch for my c
) L933SB2.
The PCI chip ID was set to 82558, but I was able to distinguish
between 8255[89] by reading PHY revision code directly from
PHY's registers and the PHY revision code was the same as
in Intel's docs for 82559.
I can test the patch.
Hope this helps.
Milon Papezik
--
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Hi all,
I have a problem with 3.4-RELEASE on Compaq Deskpro machines
with new Fast Ethernet cards with i82559 chip.
I installed them from 3.4-R ISO image without problems noticed
(ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.4-install.iso).
I can use networking with Cisco router
12 matches
Mail list logo
