RE: tulip (was RE: Kernel 2.4.3 fails to compile)
Jeff Garzik said: [snip conversation about NETDEV WATCHDOG errors on ADMTek Comet tulip clone card] > > Ok, this should be fixed in the latest patches sent to Alan and Linus. Testing with 2.4.3-ac3 and so far, so good. Thanks! -- Manuel A. McLure - Unify Corp. Technical Support <[EMAIL PROTECTED]> Space Ghost: "Hey, what happened to the-?" Moltar: "It's out." SG: "What about-?" M: "It's fixed." SG: "Eh, good. Good." - 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: tulip (was RE: Kernel 2.4.3 fails to compile)
Jeff Garzik said: [snip conversation about NETDEV WATCHDOG errors on ADMTek Comet tulip clone card] Ok, this should be fixed in the latest patches sent to Alan and Linus. Testing with 2.4.3-ac3 and so far, so good. Thanks! -- Manuel A. McLure - Unify Corp. Technical Support [EMAIL PROTECTED] Space Ghost: "Hey, what happened to the-?" Moltar: "It's out." SG: "What about-?" M: "It's fixed." SG: "Eh, good. Good." - 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: tulip (was RE: Kernel 2.4.3 fails to compile)
"Manuel A. McLure" wrote: > > Jeff Garzik wrote: > > On Fri, 30 Mar 2001, Manuel A. McLure wrote: > > > It looks like the tulip driver isn't as up-to-date as the one from > > > 2.4.2-ac20 - when is 2.4.3-ac1 due? :-) I got NETDEV > > WATCHDOG errors shortly > > > after rebooting with 2.4.3, although these were of the > > "slow/packet lossy" > > > type I got with 2.4.2-ac20 instead of the "network > > completely unusable" type > > > I got with 2.4.2-ac11 and earlier. > > > > I'm betting that the latest ac (ac28?) is broken for you, too. > > > > I had to revert the changes in 'ac' tulip -- they fixed Comet > > and 21041 > > cards, but broke some others. sigh. > > > > sigh. More testing and debugging for Jeffro... Comet (your chip, I > > am guessing?) should be fixed ASAP, it's pretty easy. 21041 is not as > > easy, but should be fixed quickly as well. > > Yes, mine is a Comet - here's the exact detection message: > > Mar 30 13:09:06 ulthar kernel: Linux Tulip driver version 0.9.14 (February > 20, 2 > 001) > Mar 30 13:09:06 ulthar kernel: PCI: Found IRQ 5 for device 00:0c.0 > Mar 30 13:09:06 ulthar kernel: eth0: ADMtek Comet rev 17 at 0xb000, > 00:20:78:0D: > D2:E1, IRQ 5. Ok, this should be fixed in the latest patches sent to Alan and Linus. -- Jeff Garzik | Sam: "Mind if I drive?" Building 1024 | Max: "Not if you don't mind me clawing at the dash MandrakeSoft | and shrieking like a cheerleader." - 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: tulip (was RE: Kernel 2.4.3 fails to compile)
"Manuel A. McLure" wrote: Jeff Garzik wrote: On Fri, 30 Mar 2001, Manuel A. McLure wrote: It looks like the tulip driver isn't as up-to-date as the one from 2.4.2-ac20 - when is 2.4.3-ac1 due? :-) I got NETDEV WATCHDOG errors shortly after rebooting with 2.4.3, although these were of the "slow/packet lossy" type I got with 2.4.2-ac20 instead of the "network completely unusable" type I got with 2.4.2-ac11 and earlier. I'm betting that the latest ac (ac28?) is broken for you, too. I had to revert the changes in 'ac' tulip -- they fixed Comet and 21041 cards, but broke some others. sigh. sigh. More testing and debugging for Jeffro... Comet (your chip, I am guessing?) should be fixed ASAP, it's pretty easy. 21041 is not as easy, but should be fixed quickly as well. Yes, mine is a Comet - here's the exact detection message: Mar 30 13:09:06 ulthar kernel: Linux Tulip driver version 0.9.14 (February 20, 2 001) Mar 30 13:09:06 ulthar kernel: PCI: Found IRQ 5 for device 00:0c.0 Mar 30 13:09:06 ulthar kernel: eth0: ADMtek Comet rev 17 at 0xb000, 00:20:78:0D: D2:E1, IRQ 5. Ok, this should be fixed in the latest patches sent to Alan and Linus. -- Jeff Garzik | Sam: "Mind if I drive?" Building 1024 | Max: "Not if you don't mind me clawing at the dash MandrakeSoft | and shrieking like a cheerleader." - 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: tulip (was RE: Kernel 2.4.3 fails to compile)
Jeff Garzik wrote: > On Fri, 30 Mar 2001, Manuel A. McLure wrote: > > It looks like the tulip driver isn't as up-to-date as the one from > > 2.4.2-ac20 - when is 2.4.3-ac1 due? :-) I got NETDEV > WATCHDOG errors shortly > > after rebooting with 2.4.3, although these were of the > "slow/packet lossy" > > type I got with 2.4.2-ac20 instead of the "network > completely unusable" type > > I got with 2.4.2-ac11 and earlier. > > I'm betting that the latest ac (ac28?) is broken for you, too. > > I had to revert the changes in 'ac' tulip -- they fixed Comet > and 21041 > cards, but broke some others. sigh. > > sigh. More testing and debugging for Jeffro... Comet (your chip, I > am guessing?) should be fixed ASAP, it's pretty easy. 21041 is not as > easy, but should be fixed quickly as well. Yes, mine is a Comet - here's the exact detection message: Mar 30 13:09:06 ulthar kernel: Linux Tulip driver version 0.9.14 (February 20, 2 001) Mar 30 13:09:06 ulthar kernel: PCI: Found IRQ 5 for device 00:0c.0 Mar 30 13:09:06 ulthar kernel: eth0: ADMtek Comet rev 17 at 0xb000, 00:20:78:0D: D2:E1, IRQ 5. I must say that I really appreciate the effort that all of the kernel developers put in... Thanks, -- Manuel A. McLure - Unify Corp. Technical Support <[EMAIL PROTECTED]> Space Ghost: "Hey, what happened to the-?" Moltar: "It's out." SG: "What about-?" M: "It's fixed." SG: "Eh, good. Good." - 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: tulip (was RE: Kernel 2.4.3 fails to compile)
Jeff Garzik wrote: On Fri, 30 Mar 2001, Manuel A. McLure wrote: It looks like the tulip driver isn't as up-to-date as the one from 2.4.2-ac20 - when is 2.4.3-ac1 due? :-) I got NETDEV WATCHDOG errors shortly after rebooting with 2.4.3, although these were of the "slow/packet lossy" type I got with 2.4.2-ac20 instead of the "network completely unusable" type I got with 2.4.2-ac11 and earlier. I'm betting that the latest ac (ac28?) is broken for you, too. I had to revert the changes in 'ac' tulip -- they fixed Comet and 21041 cards, but broke some others. sigh. sigh. More testing and debugging for Jeffro... Comet (your chip, I am guessing?) should be fixed ASAP, it's pretty easy. 21041 is not as easy, but should be fixed quickly as well. Yes, mine is a Comet - here's the exact detection message: Mar 30 13:09:06 ulthar kernel: Linux Tulip driver version 0.9.14 (February 20, 2 001) Mar 30 13:09:06 ulthar kernel: PCI: Found IRQ 5 for device 00:0c.0 Mar 30 13:09:06 ulthar kernel: eth0: ADMtek Comet rev 17 at 0xb000, 00:20:78:0D: D2:E1, IRQ 5. I must say that I really appreciate the effort that all of the kernel developers put in... Thanks, -- Manuel A. McLure - Unify Corp. Technical Support [EMAIL PROTECTED] Space Ghost: "Hey, what happened to the-?" Moltar: "It's out." SG: "What about-?" M: "It's fixed." SG: "Eh, good. Good." - 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/
