tcp retransmit timeout?
How can I set the timeout for retransmitting non-acknowledged packets? I'd like to set linux up to more aggressive about assuming a packet didn't make it. Thanks! Mordy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
tcp retransmit timeout?
How can I set the timeout for retransmitting non-acknowledged packets? I'd like to set linux up to more aggressive about assuming a packet didn't make it. Thanks! Mordy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 5Mb missing...
On Wed, Mar 14, 2001 at 03:06:09PM +0100, Alex Baretta wrote: > Mike Galbraith wrote: > > > > If crashes are routine on this machine, I'd recommend that you take > > a serious look at your ram. (or if you're overclocking, don't) > > Crashes were routine, and I was not overclocking, so I took Mike's > advice and bought a new 256MB DIMM. The computer hasn't crashed > once since I installed it. Now, though, I have a curious though > fairly irrelevant problem. My kernel apparently sees less RAM than > I have. > > > [alex@localhost /home]$ free -m > total used free sharedbuffers > cached > Mem: 251209 42 60 > 61 92 > -/+ buffers/cache: 55196 > > > I strongly doubt this can be a bug in the kernel. Could anyone > explain to me why this might happen? when you boot, your bios decides how much ram is "really" available, usually for good reasons. If the bios knows that its power management routines need a few meg off the top it'll report a few less meg to the OS that is to be booted. You can tell linux to ignore the bios with the kernel parameter mem=256, but I highly recommend *against* it in this case. Look into it. Mordy > Alex > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 5Mb missing...
On Wed, Mar 14, 2001 at 03:06:09PM +0100, Alex Baretta wrote: Mike Galbraith wrote: If crashes are routine on this machine, I'd recommend that you take a serious look at your ram. (or if you're overclocking, don't) Crashes were routine, and I was not overclocking, so I took Mike's advice and bought a new 256MB DIMM. The computer hasn't crashed once since I installed it. Now, though, I have a curious though fairly irrelevant problem. My kernel apparently sees less RAM than I have. [alex@localhost /home]$ free -m total used free sharedbuffers cached Mem: 251209 42 60 61 92 -/+ buffers/cache: 55196 I strongly doubt this can be a bug in the kernel. Could anyone explain to me why this might happen? when you boot, your bios decides how much ram is "really" available, usually for good reasons. If the bios knows that its power management routines need a few meg off the top it'll report a few less meg to the OS that is to be booted. You can tell linux to ignore the bios with the kernel parameter mem=256, but I highly recommend *against* it in this case. Look into it. Mordy Alex - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: TCP vegas implementation
linux-vegas: http://pictures.care2.com/view/2/459681070 Really. Mordy On Tue, Mar 06, 2001 at 12:03:02PM -0500, Hao Sun wrote: > > > From Neal Cardwell ([EMAIL PROTECTED]) > > Tue, 20 Jul 1999 03:08:21 -0700 (PDT) > > > > Hi all, > > > > A new TCP Vegas patch for 2.2.10/2.3.10 is available at: > > http://www.cs.washington.edu/homes/cardwell/linux-vegas/ > > Does anyone know where to get the above TCP vegas implementation code > or a more recent one? The link above is broken and Neal Cardwell is > not there. > > TIA. Please CC to me. > > -- Hao > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: TCP vegas implementation
linux-vegas: http://pictures.care2.com/view/2/459681070 Really. Mordy On Tue, Mar 06, 2001 at 12:03:02PM -0500, Hao Sun wrote: From Neal Cardwell ([EMAIL PROTECTED]) Tue, 20 Jul 1999 03:08:21 -0700 (PDT) Hi all, A new TCP Vegas patch for 2.2.10/2.3.10 is available at: http://www.cs.washington.edu/homes/cardwell/linux-vegas/ Does anyone know where to get the above TCP vegas implementation code or a more recent one? The link above is broken and Neal Cardwell is not there. TIA. Please CC to me. -- Hao - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
CPRM is dead; Thanks Andre!
See: http://www.theregister.co.uk/content/2/17107.html IBM withdrew the proposal. mordy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
CPRM is dead; Thanks Andre!
See: http://www.theregister.co.uk/content/2/17107.html IBM withdrew the proposal. mordy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.1 crashing every other day
On Sun, Feb 18, 2001 at 02:46:30AM +0100, Andre Tomt wrote: > Very recently I installed a new mailserver for my company, based around > qmail, linux 2.4.1, and software raid 1. > It works very nicely untill it spews out oops's after a few days, leaving > hundreds of qmail-popup processes hanging, unkillable. THe server is very > lightly loaded for now, doing only a few hundreds smtp + pop's a day. > > It's a Pentium III 733 based system, with 256MB RAM (one stick, we have > already tried another stick), and every partition except swap on software > RAID 1. Both IDE disks (IBM-DTLA-307030, 30GB each) are connected to a HPT > ATA100 IDE controller (see the lscpi-output). I've attached some info, and > one decoded oops. Longer down you'll find info from lspci and the like. > > As a side note, we have one other _identical_ hardware setup, running the > same kernel, same base software, same partitioning, same RAID setup, just as > a webserver. And it works geat, no hickups whatsoever. Also, the oops's > seems to happen only with qmail-popup, at least thats how the few crashes I > had the chance to investigate did. > Looks like you were bitten by either the RAID 1 bugs or the elevator bugs. Try a 2.4.2-pre4 or an 2.4.1-ac18 kernel. Should solve it. Mordy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.1 crashing every other day
On Sun, Feb 18, 2001 at 02:46:30AM +0100, Andre Tomt wrote: Very recently I installed a new mailserver for my company, based around qmail, linux 2.4.1, and software raid 1. It works very nicely untill it spews out oops's after a few days, leaving hundreds of qmail-popup processes hanging, unkillable. THe server is very lightly loaded for now, doing only a few hundreds smtp + pop's a day. It's a Pentium III 733 based system, with 256MB RAM (one stick, we have already tried another stick), and every partition except swap on software RAID 1. Both IDE disks (IBM-DTLA-307030, 30GB each) are connected to a HPT ATA100 IDE controller (see the lscpi-output). I've attached some info, and one decoded oops. Longer down you'll find info from lspci and the like. As a side note, we have one other _identical_ hardware setup, running the same kernel, same base software, same partitioning, same RAID setup, just as a webserver. And it works geat, no hickups whatsoever. Also, the oops's seems to happen only with qmail-popup, at least thats how the few crashes I had the chance to investigate did. Looks like you were bitten by either the RAID 1 bugs or the elevator bugs. Try a 2.4.2-pre4 or an 2.4.1-ac18 kernel. Should solve it. Mordy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Reason (was: Re: dropcopyright script)
On Wed, Feb 14, 2001 at 12:52:36PM -0500, Gregory Maxwell wrote: > On Wed, Feb 14, 2001 at 10:00:25AM -0500, Mohammad A. Haque wrote: > > How big do you have your icons set that you can actually read stuff in > > it? > > On Wed, 14 Feb 2001, Mordechai Ovits wrote: > > > > > In newer file managers, the icon of a C file is a tiny image of the first > > > few lines of text. If all files startt with a copyright, it's not much > > > good. So running this on a local, personal, tree can be a good thing. > > It would probably be more useful to make a little picture of a tree of the Huh? Mordy > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Reason (was: Re: dropcopyright script)
On Wed, Feb 14, 2001 at 10:00:25AM -0500, Mohammad A. Haque wrote: > Heh > > How big do you have your icons set that you can actually read stuff in > it? They're quite large, and it is surprisingly effective. KDE2 and nautilus both do this. Mordy > On Wed, 14 Feb 2001, Mordechai Ovits wrote: > > > In newer file managers, the icon of a C file is a tiny image of the first > > few lines of text. If all files startt with a copyright, it's not much > > good. So running this on a local, personal, tree can be a good thing. > > > > Mordy > > > > -- > > = > Mohammad A. Haque http://www.haque.net/ >[EMAIL PROTECTED] > > "Alcohol and calculus don't mix. Project Lead >Don't drink and derive." --Unknown http://wm.themes.org/ >[EMAIL PROTECTED] > = > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Reason (was: Re: dropcopyright script)
On Wed, Feb 14, 2001 at 03:34:56PM +0100, Yoann Vandoorselaere wrote: > Mordechai Ovits <[EMAIL PROTECTED]> writes: > > > In newer file managers, the icon of a C file is a tiny image of the first > > few lines of text. If all files startt with a copyright, it's not much > > good. So running this on a local, personal, tree can be a good thing. > > Modifying the file manager to take care of that would > be a proper solution I think... hard to imagine that working for any general solution. Better to let people mess with their own files using a script like the one posted. Mordy > -- > > -- Yoann http://www.mandrakesoft.com/~yoann/ > C makes it easy to shoot yourself in the foot. C++ makes it harder, > but when you do, it blows away your whole leg. - Bjarne Stroustrup > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Reason (was: Re: dropcopyright script)
In newer file managers, the icon of a C file is a tiny image of the first few lines of text. If all files startt with a copyright, it's not much good. So running this on a local, personal, tree can be a good thing. Mordy On Wed, Feb 14, 2001 at 08:23:57AM -0500, Mohammad A. Haque wrote: > What prompted this? People are going to want copyright notices in a > prominent place. Namely at the beginning of the code along with whatever > instructions and cruft. > > Rick Hohensee wrote: > > > > ... > > ## drop copyright notices to the bottoms of C files in current dir and > > # subs. > > # /* > > # CopYriGHt Guess Who 2001All reserves righted. > > # */ > > > > grep -ilr "copyright" . > tempdropcopyrights > > > > for f in `cat tempdropcopyrights` > > do > > ed $f < > /[Cc][oO][pP][yY][rR][iI]/ > > ?\/\*? > > .,/\*\//m$ > > wq > > HEREDOC > > done > > > > > > -- > > = > Mohammad A. Haque http://www.haque.net/ >[EMAIL PROTECTED] > > "Alcohol and calculus don't mix. Project Lead >Don't drink and derive." --Unknown http://wm.themes.org/ >[EMAIL PROTECTED] > = > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Reason (was: Re: dropcopyright script)
In newer file managers, the icon of a C file is a tiny image of the first few lines of text. If all files startt with a copyright, it's not much good. So running this on a local, personal, tree can be a good thing. Mordy On Wed, Feb 14, 2001 at 08:23:57AM -0500, Mohammad A. Haque wrote: What prompted this? People are going to want copyright notices in a prominent place. Namely at the beginning of the code along with whatever instructions and cruft. Rick Hohensee wrote: ... ## drop copyright notices to the bottoms of C files in current dir and # subs. # /* # CopYriGHt Guess Who 2001All reserves righted. # */ grep -ilr "copyright" . tempdropcopyrights for f in `cat tempdropcopyrights` do ed $f HEREDOC /[Cc][oO][pP][yY][rR][iI]/ ?\/\*? .,/\*\//m$ wq HEREDOC done -- = Mohammad A. Haque http://www.haque.net/ [EMAIL PROTECTED] "Alcohol and calculus don't mix. Project Lead Don't drink and derive." --Unknown http://wm.themes.org/ [EMAIL PROTECTED] = - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Reason (was: Re: dropcopyright script)
On Wed, Feb 14, 2001 at 03:34:56PM +0100, Yoann Vandoorselaere wrote: Mordechai Ovits [EMAIL PROTECTED] writes: In newer file managers, the icon of a C file is a tiny image of the first few lines of text. If all files startt with a copyright, it's not much good. So running this on a local, personal, tree can be a good thing. Modifying the file manager to take care of that would be a proper solution I think... hard to imagine that working for any general solution. Better to let people mess with their own files using a script like the one posted. Mordy -- -- Yoann http://www.mandrakesoft.com/~yoann/ C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, it blows away your whole leg. - Bjarne Stroustrup - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Reason (was: Re: dropcopyright script)
On Wed, Feb 14, 2001 at 12:52:36PM -0500, Gregory Maxwell wrote: On Wed, Feb 14, 2001 at 10:00:25AM -0500, Mohammad A. Haque wrote: How big do you have your icons set that you can actually read stuff in it? On Wed, 14 Feb 2001, Mordechai Ovits wrote: In newer file managers, the icon of a C file is a tiny image of the first few lines of text. If all files startt with a copyright, it's not much good. So running this on a local, personal, tree can be a good thing. It would probably be more useful to make a little picture of a tree of the Huh? Mordy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: "Tux" is the wrong logo for Linux
'Yer funny! If only trolling paid, eh? Mordy On Thu, Oct 19, 2000 at 08:20:37AM -0700, KMF AV wrote: > First, the 2.4 kernel is years late and doesn't work > right, and keeps getting rewritten because it's a > festering hunk of fetid spaghetti inside. > > Then, Alan Cox suggests tossing the versioning scheme > to the wind even more that it already has been: > > > Alan Cox did post an interesting suggestion. In his > > scheme, there would essentially be two stable kernel > > > release tracks. Once 2.4 comes out, the 2.5 > > development series would go off as usual. At some > > point, however, the developers would stop and decide > > > which of the new features could be backported to the > > 2.4 kernel in a stable manner. That port would be > > done, with the result being 2.6. The 2.5 series > would > > then be renamed 2.7, and the whole thing would > > eventually be stabilized as 2.8. > > And then this delightful news story about Linux Kernel > Programmers -- who don't need debuggers, because > they're so rad -- don't actually know how to program: > > > The hunt for undefined code. Here's one kind of > > problem that a new compiler can turn up. Most C > > programmers learn early on to avoid code like: > > a[i] = i++; The results of this kind of code are > > undefined; the array assignment could happen either > > before or after the value of it is incremented. > Bernd > > Schmidt looked through the kernel source for this > > sort of code, and found quite a bit of it. He has > > submitted a patch to fix up the things he > > encountered; as he puts it, "in some cases, it > wasn't > > entirely clear what the code intended, so I had to > > guess." This patch went into 2.4.0-test10-pre4, so > we > > may well find a spot or two where he guessed wrong. > > The effort is a good one, though. This kind of code > > is a time bomb waiting to go off; it needs to be > > cleaned up sooner rather than later. > > ... obviously the Linux logo should be the > international symbol for the fucking retard. > > http://www.geocities.com/kmfav/ > > > > > __ > Do You Yahoo!? > Yahoo! Messenger - Talk while you surf! It's FREE. > http://im.yahoo.com/ > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Tux is the wrong logo for Linux
'Yer funny! If only trolling paid, eh? Mordy On Thu, Oct 19, 2000 at 08:20:37AM -0700, KMF AV wrote: First, the 2.4 kernel is years late and doesn't work right, and keeps getting rewritten because it's a festering hunk of fetid spaghetti inside. Then, Alan Cox suggests tossing the versioning scheme to the wind even more that it already has been: Alan Cox did post an interesting suggestion. In his scheme, there would essentially be two stable kernel release tracks. Once 2.4 comes out, the 2.5 development series would go off as usual. At some point, however, the developers would stop and decide which of the new features could be backported to the 2.4 kernel in a stable manner. That port would be done, with the result being 2.6. The 2.5 series would then be renamed 2.7, and the whole thing would eventually be stabilized as 2.8. And then this delightful news story about Linux Kernel Programmers -- who don't need debuggers, because they're so rad -- don't actually know how to program: The hunt for undefined code. Here's one kind of problem that a new compiler can turn up. Most C programmers learn early on to avoid code like: a[i] = i++; The results of this kind of code are undefined; the array assignment could happen either before or after the value of it is incremented. Bernd Schmidt looked through the kernel source for this sort of code, and found quite a bit of it. He has submitted a patch to fix up the things he encountered; as he puts it, "in some cases, it wasn't entirely clear what the code intended, so I had to guess." This patch went into 2.4.0-test10-pre4, so we may well find a spot or two where he guessed wrong. The effort is a good one, though. This kind of code is a time bomb waiting to go off; it needs to be cleaned up sooner rather than later. ... obviously the Linux logo should be the international symbol for the fucking retard. http://www.geocities.com/kmfav/ __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: use of add_interrupt_randomness in drivers missing in many drivers
On Wed, Oct 18, 2000 at 05:20:43PM +0100, Alan Cox wrote: > > The only thing needed is to add the SA_SAMPLE_RANDOM flag to request_irq > > in the drivers. > > > > If nobody objects, I'll submit a patch that adds this to network drivers. > > Network timing is controllable remotely Read Bruce Schneier's paper on the design of the Yarrow PRNG. You *can* use network timings as an entropy source if your PRNG is designed to prevent a source from being able to effect a compromise. Mordy > > Alan > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: use of add_interrupt_randomness in drivers missing in many drivers
On Wed, Oct 18, 2000 at 05:20:43PM +0100, Alan Cox wrote: The only thing needed is to add the SA_SAMPLE_RANDOM flag to request_irq in the drivers. If nobody objects, I'll submit a patch that adds this to network drivers. Network timing is controllable remotely Read Bruce Schneier's paper on the design of the Yarrow PRNG. You *can* use network timings as an entropy source if your PRNG is designed to prevent a source from being able to effect a compromise. Mordy Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 3c59x problems solved -- mostly
On Wed, Sep 27, 2000 at 11:26:09PM +1100, Andrew Morton wrote: > The sensible alternative, of course, is to use a multicast filter. The > 3c905B/C does have a 256 slot hash filter. Unfortunately (and > uncharacteristically), 3com forgot to document it. However it _is_ > implemented in 3com's own GPL'ed driver. This driver is bundled in > RedHat 6.x and is available at > http://support.3com.com/infodeli/tools/nic/linux.htm . It's worth > visiting that site just for the amusement factor of having to click on > "I agree" for the license. It's the GPL! > > Even better, port 3com's code to 3c59x.c and send me a patch :) > I admit, I got a major kick out of the GPL being a click-through licence :-). Anyway, given that 3com's driver has this extra hardware support, what advantage does that give? is there anything that their driver does better? Curious cuz I have a 905B, Mordy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 3c59x problems solved -- mostly
On Wed, Sep 27, 2000 at 11:26:09PM +1100, Andrew Morton wrote: The sensible alternative, of course, is to use a multicast filter. The 3c905B/C does have a 256 slot hash filter. Unfortunately (and uncharacteristically), 3com forgot to document it. However it _is_ implemented in 3com's own GPL'ed driver. This driver is bundled in RedHat 6.x and is available at http://support.3com.com/infodeli/tools/nic/linux.htm . It's worth visiting that site just for the amusement factor of having to click on "I agree" for the license. It's the GPL! Even better, port 3com's code to 3c59x.c and send me a patch :) I admit, I got a major kick out of the GPL being a click-through licence :-). Anyway, given that 3com's driver has this extra hardware support, what advantage does that give? is there anything that their driver does better? Curious cuz I have a 905B, Mordy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: No sound (es1371) after test7
On Fri, Sep 22, 2000 at 09:14:23AM -0400, Kernel Related Emails wrote: > List, > > Well everythings working fine in test9-pre5 except for the fact that sound > has stopped functioning on my es1371 card. I had no problems with it at > all in test7 but since then it doesn't work. On boot it detects normally, > pops and crackles for a second, and then just doesn't work. Any > ideas? I'm getting no kernel messages or any output that would indicate > the problem. Just as a datapoint, my es1371 is pumping out music under test8 as I type this. I did have some mixer wierdness tha twere probably unrelated, but check your volumes. Mordy > Thanks, > Kris > [EMAIL PROTECTED] > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: No sound (es1371) after test7
On Fri, Sep 22, 2000 at 09:14:23AM -0400, Kernel Related Emails wrote: List, Well everythings working fine in test9-pre5 except for the fact that sound has stopped functioning on my es1371 card. I had no problems with it at all in test7 but since then it doesn't work. On boot it detects normally, pops and crackles for a second, and then just doesn't work. Any ideas? I'm getting no kernel messages or any output that would indicate the problem. Just as a datapoint, my es1371 is pumping out music under test8 as I type this. I did have some mixer wierdness tha twere probably unrelated, but check your volumes. Mordy Thanks, Kris [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
