I just upgraded a running FC2 system to FC3, and everything seemed to go smoothly except that I lost network connectivity via a slightly aged but still functional 3C509B NIC. I've tried reactivating it via the Network config program, but while its existence is acknowledged, it doesn't respond to my requests to start interfacing. Since the only access to the world beyond my home office is via that network card, it reduces the value of that system substantially. Has anyone else run into (and gone beyond) this problem?
Cheers, Gordon Keehn
On Mon, Nov 29, 2004 at 11:55:43AM -0500, Gordon R. Keehn wrote:
I just upgraded a running FC2 system to FC3, and everything seemed to go smoothly except that I lost network connectivity via a slightly aged but still functional 3C509B NIC. I've tried reactivating it via the Network config program, but while its existence is acknowledged, it doesn't respond to my requests to start interfacing. Since the only access to the world beyond my home office is via that network card, it reduces the value of that system substantially. Has anyone else run into (and gone beyond) this problem?
RH doesn't seem to distribute the binary driver for those old ISA network cards anymore. much to my chagrin. I've got a half-dozen or so 3c509b-tpo cards around here. Last time I looked they did distribute the source, still, so you could build the module yourself if you wanted to.
On Mon, Nov 29, 2004 at 12:16:59PM -0500, fredex wrote:
On Mon, Nov 29, 2004 at 11:55:43AM -0500, Gordon R. Keehn wrote:
I just upgraded a running FC2 system to FC3, and everything seemed to go smoothly except that I lost network connectivity via a slightly aged but still functional 3C509B NIC. I've tried reactivating it via the Network config program, but while its existence is acknowledged, it doesn't respond to my requests to start interfacing. Since the only access to the world beyond my home office is via that network card, it reduces the value of that system substantially. Has anyone else run into (and gone beyond) this problem?
RH doesn't seem to distribute the binary driver for those old ISA network cards anymore. much to my chagrin. I've got a half-dozen or so 3c509b-tpo cards around here. Last time I looked they did distribute the source, still, so you could build the module yourself if you wanted to.
I'm not having any problem with my 3c509 card. It is not detected by Kudzu or Anaconda, but system-config-network configures it correctly and it works just fine under FC3.
Just another data point.
On Tue, Nov 30, 2004 at 07:12:38AM +0800, John Summerfield wrote:
On Tuesday 30 November 2004 01:16, fredex wrote:
RH doesn't seem to distribute the binary driver
RH doesn't distribute binary-only drivers.
I didn't say binary ONLY. the installable CD images are full of binary modules/programs for which source is available.
The binaries for those old ISA cards, as opposed to newer chipsets (PCI or integrated) are not in the later RH distributions I've looked at (FC1, WS 3, etc.)
On Mon, 29 Nov 2004 19:07:44 -0500, fredex fredex@fcshome.stoneham.ma.us wrote:
On Tue, Nov 30, 2004 at 07:12:38AM +0800, John Summerfield wrote:
On Tuesday 30 November 2004 01:16, fredex wrote:
RH doesn't seem to distribute the binary driver
RH doesn't distribute binary-only drivers.
I didn't say binary ONLY. the installable CD images are full of binary modules/programs for which source is available.
The binaries for those old ISA cards, as opposed to newer chipsets (PCI or integrated) are not in the later RH distributions I've looked at (FC1, WS 3, etc.)
At past I need to turn the kudzu off the avoid the 3c905 problem in FC2 and now is ok in FC3. I can turned it on an running without problem....
Ringo
Wong Kwok-hon wrote:
On Mon, 29 Nov 2004 19:07:44 -0500, fredex fredex@fcshome.stoneham.ma.us wrote:
On Tue, Nov 30, 2004 at 07:12:38AM +0800, John Summerfield wrote:
On Tuesday 30 November 2004 01:16, fredex wrote:
RH doesn't seem to distribute the binary driver
RH doesn't distribute binary-only drivers.
I didn't say binary ONLY. the installable CD images are full of binary modules/programs for which source is available.
The binaries for those old ISA cards, as opposed to newer chipsets (PCI or integrated) are not in the later RH distributions I've looked at (FC1, WS 3, etc.)
At past I need to turn the kudzu off the avoid the 3c905 problem in FC2 and now is ok in FC3. I can turned it on an running without problem....
Ringo
Thanks fr passing on this information. I had a 3COM that I gave away because of the long term breakage. Cheers to those that got this card type rolling again.
Jim
Gordon R. Keehn wrote:
I just upgraded a running FC2 system to FC3, and everything seemed to go smoothly except that I lost network connectivity via a slightly aged but still functional 3C509B NIC. I've tried reactivating it via the Network config program, but while its existence is acknowledged, it doesn't respond to my requests to start interfacing. Since the only access to the world beyond my home office is via that network card, it reduces the value of that system substantially. Has anyone else run into (and gone beyond) this problem?
Cheers, Gordon Keehn
I spent this last Saturday tweaking parameters and rebooting without success. The only common factor was a series of nastygrammes containing the string SIOCSIFFLAG. A Google search suggested that this was probably related to parameter misdefinition, but there was no evidence of a bad IRQ. I also considered the possibility that the card (which is bordering on antique status) finally decided its time was up. I booted from the install and diagnostics diskette to verify the settings (which looked fine). As a last resort before opening the box and yanking the card, I reactivated Plug-and-Play (deactivated when I originally installed Linux on that box back around Redhat 7.2) and rebooted. The card was recognised, activated, and now appears to be working fine. Go figure! Cheers, Gordon
-
Fred Smith -
G.Wolfe Woodbury -
Gordon Keehn -
Jim Cornette -
John Summerfield -
Wong Kwok-hon