On Sat, May 26, 2007 at 09:26:25PM +0100, Ted Harding wrote:
I'd be a lot more willing to do that, if it wasn't in the same league as replacing the soil in which a garden of irreplaceable plants was growing ... Ted.
I'd look at getting a new machine and putting something recent on it and then looking at getting the old system copied across into some kind of virtual machine so that you have access to the old and can migrate it over to the new a little bit at a time.
adam
Yes, that would be the long-term solution. But, meanwhile, I need to be using that machine constantly (over nmy LAN), so am looking for an immediate fix to the NIC problem.
I'm getting sort of somewhere with the idea of probing for IRQs. The 'ne' driver finds the card at 0x300, but can;t find an IRQ. So I can set options to give it a trial IRQ (3,4 and 7 seem to be taken by Serial0, Serial1 and Parallel0), so I've tried the others in the low range. For most, the driver finds the card at ox300 and is "using IRQ 5" (e.g.); and Linux then sets up the eth0 interface as verified by ifconfig, and also the routing tables (including the correct default route). But nothing gets out of the card (e.g. I ping another og my machines, all packets are lost, and no lights blink).
But "sort of somwhere" isn't *there*!
Thanks for the continued suggestions. Ted.
PS Of course the ideal would be to replace the PSU on the old machine -- but they don't make then like that any more ...