Dennis writes:
> We have thousands of boards installedmaking them work back to back in a
> non-standard configuration does not make the product *better*, particularly
> when working with someone who cant provide useful info on *why* it doesnt
> work. I wish I could stop what I was doing every
> Of course now that you've publically badmouthed us Im sure your requests
> well get very high priority :-)
This is very unprofessional. I hope I shall never have to order from your
company, and will advice others of this as appropriate.
- Marius -
To Unsubscribe: send mail to majord...@freeb
> If it "had no backing" then how could it be a "fact"?
I assume that if you report that a card fails to work that that is true.
That makes it a fact, e.g. my seat is red, but I'm not going to send you
a picture to prove it.
> replacing the cards with intels and having the problem go away is
>The discussion started with a remark about the fact that 3Com cards have
>problems under load, without a backing of that statement. That is the
>thing that made people trip over. It is a statement that is not the
>least helpful for anyone on the hackers mailing list and will not
>trigger help fro
>> The discussion started with a remark about the fact that 3Com
>> cards have
>> problems under load, without a backing of that statement. That is the
>> thing that made people trip over. It is a statement that is not the
>> least helpful for anyone on the hackers mailing list and will not
>> tr
Dennis wrote:
>
> At 08:00 AM 6/1/99 -0700, you wrote:
> >On Tue, 1 Jun 1999 10:09:59 +0200
> > Alexander Maret wrote:
> >
> > > At first I tried my FreeBSD machine and I got about 800-900 collisions.
> > > Second I booted on the same machine linux and I only got 4 (!) collisions.
> >
> >It's als
On Tue, 1 Jun 1999, Dennis wrote:
> If your nic driver chains packets (such that there is no time in
> between) you will see good throughput from the box but your overall
> network performance will suffer. A PCI card with continueous traffic
> can completely hog your lan (particularly at 10Mb/s)...
At 11:03 AM 6/1/99 -0700, you wrote:
>
>>
>> If your nic driver chains packets (such that there is no time in between)
>> you will see good throughput from the box but your overall network
>> performance will suffer. A PCI card with continueous traffic can completely
>> hog your lan (particularly
>
> If your nic driver chains packets (such that there is no time in between)
> you will see good throughput from the box but your overall network
> performance will suffer. A PCI card with continueous traffic can completely
> hog your lan (particularly at 10Mb/s)...which can cause a lot more
> c
> Dennis wrote:
>
> > For "Fairness" gaps in between frames are better
> > as you approach capacity of your wire.
>
> Isn't there some ethernet requirement (implemented on the NIC) that a
> transmitter holds off the wire a little to give other NICs enough time
> to notice there's nothing being tr
At 02:50 PM 5/30/99 -0700, you wrote:
>> >> I have no stake in 3com cards (they are
>> >> problematic in LINUX as well)...maybe the cards are flawed? Its not my
>> >> problem.
>> >
>> >It *is* your problem. Supposing you can't get Intel cards anymore.
>> >Then what're you going to do.
>>
>> Use so
Dennis wrote:
> For "Fairness" gaps in between frames are better
> as you approach capacity of your wire.
Isn't there some ethernet requirement (implemented on the NIC) that a
transmitter holds off the wire a little to give other NICs enough time
to notice there's nothing being transmitted?
The
At 08:06 PM 5/30/99 -0700, you wrote:
>
>It is kind of interesting that now the shoe is on the other foot...
>
>A few months ago I purchased some sync cards from ET, and had some (and am
>still having) trouble getting them to work consistently.
>
>When I emailed their support dept for help, I got a
At 08:00 AM 6/1/99 -0700, you wrote:
>On Tue, 1 Jun 1999 10:09:59 +0200
> Alexander Maret wrote:
>
> > At first I tried my FreeBSD machine and I got about 800-900 collisions.
> > Second I booted on the same machine linux and I only got 4 (!) collisions.
>
>It's also possible that Linux isn't coun
Of all the gin joints in all the towns in all the world, Alexander Maret
had to walk into mine and say:
> Hi,
>
> > Well maybe FreeBSD is transmitting packets much faster than Linux. :)
> > You still haven't actually measured the transfer speed, so there's
> > no way for us to know.
>
> Well, I
On Tue, 1 Jun 1999 10:09:59 +0200
Alexander Maret wrote:
> At first I tried my FreeBSD machine and I got about 800-900 collisions.
> Second I booted on the same machine linux and I only got 4 (!) collisions.
It's also possible that Linux isn't counting the collisions properly.
> I have no
Alexander Maret writes:
> Hi,
>
> > -Original Message-
> > From: Sheldon Hearn [mailto:sheld...@uunet.co.za]
> > Sent: Dienstag, 1. Juni 1999 10:45
> > To: Alexander Maret
> > Cc: hack...@freebsd.org
> > Subject: Re: xl driver for 3Com
> Yes, I read this remark and then decided to write to the developer
> because I had such a problem. I tried to post as many information
> as I could. Well it was not enough for Bill, but instead everyone
> just saying: "Provide information" people should ask questions.
> You will only exactl
Hi,
> -Original Message-
> From: Nick Hibma [mailto:nick.hi...@jrc.it]
> Sent: Dienstag, 1. Juni 1999 11:58
> To: Alexander Maret
> Cc: 'hack...@freebsd.org'
> Subject: RE: xl driver for 3Com
>
>
>
> The discussion started with a remar
> > FreeBSD developers do things in their spare time and they want
> > people to respect that. They want to see some investment from
> > the other side as well to make it worthwhile.
> > And if that trade off is not what
> > you want, there are companies out there that solve problems for mone
Hi,
> -Original Message-
> From: Nick Hibma [mailto:nick.hi...@jrc.it]
> Sent: Dienstag, 1. Juni 1999 11:01
> To: Alexander Maret
> Cc: FreeBSD hackers mailing list
> Subject: RE: xl driver for 3Com
>
> This comparison with Linux is completely off. The n
This comparison with Linux is completely off. The number of knowledgable
people working on USB for example is equivalent to the ones in FreeBSD.
Most of the people talking on linux-usb are talkers not do-ers.
FreeBSD developers do things in their spare time and they want other
people to respect t
Hi,
> -Original Message-
> From: Sheldon Hearn [mailto:sheld...@uunet.co.za]
> Sent: Dienstag, 1. Juni 1999 10:45
> To: Alexander Maret
> Cc: hack...@freebsd.org
> Subject: Re: xl driver for 3Com
>
> FreeBSD _developers_ seem to be more concerned with producing
On Tue, 01 Jun 1999 10:31:21 +0200, Alexander Maret wrote:
> There are so many FreeBSD-Hackers who are whining that Linux has so
> many users and FreeBSD hasn't.
No there are not. There are many FreeBSD enthusiasts who are whining
that Linux has so many users and FreeBSD hasn't.
FreeBSD _devel
Hi,
> -Original Message-
> From: Greg Black [mailto:g...@acm.org]
> Sent: Dienstag, 1. Juni 1999 05:21
> To: Bill Paul
> Cc: hack...@freebsd.org
> Subject: Re: xl driver for 3Com
>
> This whole argument strikes me as a good wake up call for all of
> us. It
Bill Paul writes:
> If you have a real, detailed and accurate bug report to submit, then fine:
> let's hear it. But if you just want to make vague and unsubstantiated
> complaints, do me a favor and just keep it to yourself.
This whole argument strikes me as a good wake up call for all of
us. I
Hi,
> Collisions on half-duplex Ethernet are *normal*. Get used to it.
>
> Collisions is the standard flow control mechanism for
> half-duplex Ethernet.
> The amount of collisions you get depend on the cards used,
> the amount of
> traffic, and several other things. The amount of collisions
>
> I don't think that so many collisions are normal! I think there is a
> problem, because at work we nearly only use 3COM 100 Mbit cards and
> don't have much collisions. Even under high load!
Collisions on half-duplex Ethernet are *normal*. Get used to it.
Collisions is the standard flow control
Hi,
> Well maybe FreeBSD is transmitting packets much faster than Linux. :)
> You still haven't actually measured the transfer speed, so there's
> no way for us to know.
Well, I'll do and report the results to you.
> Grrr. I'm sorry, but I really don't think you're putting the pieces
> together
Of all the gin joints in all the towns in all the world, Alexander Maret
had to walk into mine and say:
> Hmm,
>
> I'm no expert and this all sounds reasonable to me, but there are
> things I haven't mentioned yet:
Grrr. What were you waiting for. You should have mentioned them to
start with.
> > I'm having serious problems with my 3COM Card too. The problem is
> > that there are many many collisions on the network. If i for
> > example transfer 30MB via samba from one computer to the other i get
> > about 900 collisions.
Leaving busy networks etc. aside, this is purely a characterist
Of all the gin joints in all the towns in all the world, Alexander Maret
had to walk into mine and say:
> Hi,
>
>
> > If you have a real, detailed and accurate bug report to
> > submit, then fine:
> > let's hear it. But if you just want to make vague and unsubstantiated
> > complaints, do me
It is kind of interesting that now the shoe is on the other foot...
A few months ago I purchased some sync cards from ET, and had some (and am
still having) trouble getting them to work consistently.
When I emailed their support dept for help, I got a few curt non-helpful
replies, then a message
> >> I have no stake in 3com cards (they are
> >> problematic in LINUX as well)...maybe the cards are flawed? Its not my
> >> problem.
> >
> >It *is* your problem. Supposing you can't get Intel cards anymore.
> >Then what're you going to do.
>
> Use something else that works. If none of them work
At 05:59 PM 5/29/99 -0400, you wrote:
>Of all the gin joints in all the towns in all the world, Dennis had to
>walk into mine and say:
>
>> >Then *FIND THEM OUT*! Replacing the cards does not fix the problem! How
>> >is anybody supposed to be able to help you if a) you never tell anybody
>> >abou
On Sat, 29 May 1999, Bill Paul wrote:
:So, tell me: just how many of you other people reading this have been
:having problems with 'drivers under load' and couldn't be bothered to
:actually report the problem? Hm? Well what're you waiting for?! Go on:
:speak up! Take two minutes of your precious t
Of all the gin joints in all the towns in all the world, Dennis had to
walk into mine and say:
> >Then *FIND THEM OUT*! Replacing the cards does not fix the problem! How
> >is anybody supposed to be able to help you if a) you never tell anybody
> >about the trouble, b) you destroy the test confi
At 01:40 AM 5/29/99 -0400, you wrote:
>Of all the gin joints in all the towns in all the world, Dennis had to
>walk into mine and say:
>
>> I dunno what it is, but we've had customers experiencing packet loss at
>> high usage on 100Mb's nets...and the problem goes away when replacing them
>> with
Bill Paul writes:
> [...] Yes! I like it! Instead of trying to help
> people, I'll be maddeningly vague! I'll pretend to be helpful but stop
> short of actually providing any useful information! Then everyone else
> will go insane instead of me, society will collapse, an
At 1:40 am -0400 29/5/99, Bill Paul wrote:
>[...] Yes! I like it! Instead of trying to help
>people, I'll be maddeningly vague! I'll pretend to be helpful but stop
>short of actually providing any useful information! Then everyone else
>will go insane instead of me, society will collapse, and I can
> wonderful! You know, I should use that myself! "Hey Bill: my network
> crashed." "Well, there's probably something you could do to fix that
> but I don't know the details." Yes! I like it! Instead of trying to help
> people, I'll be maddeningly vague! I'll pretend to be helpful but stop
You hav
+[ Bill Paul ]-
|
| but I don't know the details." Yes! I like it! Instead of trying to help
| people, I'll be maddeningly vague! I'll pretend to be helpful but stop
| short of actually providing any useful information! Then everyone else
Be carefu
Of all the gin joints in all the towns in all the world, Dennis had to
walk into mine and say:
> I dunno what it is, but we've had customers experiencing packet loss at
> high usage on 100Mb's nets...and the problem goes away when replacing them
> with intels. I dont know the details.
Then *FIN
Of all the gin joints in all the towns in all the world, Dennis had to
walk into mine and say:
> Note that this card/driver seems to have serious problems under heavy load.
> Just so you know.
This is statement is nothing more than baseless slander, just so *you* know.
I really hate it when:
At 03:12 AM 5/29/99 +0200, Dag-Erling Smorgrav wrote:
>Dennis writes:
>> At 02:58 PM 5/28/99 +0200, you wrote:
>> > I need to hack the driver file if_xl.c to do the following :
>> Note that this card/driver seems to have serious problems under heavy load.
>> Just so you know.
>
>What FreeBSD versi
Dennis writes:
> At 02:58 PM 5/28/99 +0200, you wrote:
> > I need to hack the driver file if_xl.c to do the following :
> Note that this card/driver seems to have serious problems under heavy load.
> Just so you know.
What FreeBSD version do you run? There were a few commits to the xl
driver shor
At 09:29 AM 5/28/99 -0700, you wrote:
>> At 02:58 PM 5/28/99 +0200, you wrote:
>> >Hi there hackers.
>> >I need to hack the driver file if_xl.c to do the following :
>> >-> Detect the first 3Com card normally.
>> >-> All cards hereafter must only be able to receive packets, not
>> >transmit them.
>
> At 02:58 PM 5/28/99 +0200, you wrote:
> >Hi there hackers.
> >I need to hack the driver file if_xl.c to do the following :
> >-> Detect the first 3Com card normally.
> >-> All cards hereafter must only be able to receive packets, not
> >transmit them.
> >Does anybody know how i can achieve this b
> At 02:58 PM 5/28/99 +0200, you wrote:
> >Hi there hackers.
> >I need to hack the driver file if_xl.c to do the following :
> >-> Detect the first 3Com card normally.
> >-> All cards hereafter must only be able to receive packets, not
> >transmit them.
looks like the typical ipfw thing, rather th
At 02:58 PM 5/28/99 +0200, you wrote:
>Hi there hackers.
>I need to hack the driver file if_xl.c to do the following :
>-> Detect the first 3Com card normally.
>-> All cards hereafter must only be able to receive packets, not
>transmit them.
>Does anybody know how i can achieve this by changes in t
Hi there hackers.
I need to hack the driver file if_xl.c to do the following :
-> Detect the first 3Com card normally.
-> All cards hereafter must only be able to receive packets, not
transmit them.
Does anybody know how i can achieve this by changes in the file if_xl.c
Even if you could point me
51 matches
Mail list logo
