YaRness
08-27-2001, 10:06 PM
i don't think the problem is directly related to freesco, but of course any familiarity might help.
what i've got in this box is two pci nics, different brands (both ne2000 compatible, i think one is a at2000t pnp and the other is a trend (tci-p/w or tpci/w or something like that). i'm fairly sure i've got the software disk for at least one of them.
linux finds both nics fine, puts them on eth0 and eth1. they are both on irq 9 though, which i'm not very clear about though i think that's supposed to be OK for PCI periphs. they are also set to I/O addresses that are VERY close together (0xfce0 and 0xfcc0), which i don't know if that is OK for PCI periphs again.
i think it hangs a bit after the DHCP daemon successfully initializes attached to eth0, and then whatever daemon listens to the internal network on eth1 starts.
when i was testing it off the network, it would hang trying to initialize DHCP through the first nic ("Waiting for DHCPOFFER on eth0" cuz it wasn't attached to the cable modem), but i could switch to another console (alt-f2) and log in, mess with stuff, yada yada yada.
when i finally hooked it up to the cable modem, it would finish the DHCP daemon, finish starting services, and present a login prompt on the first console. but either immediately or very shortly afterward, the keyboard would quit responding; not even settting scroll or numlock would work, no three-finger salute, nada. if i left it sitting there for a few minutes the box would just shut itself off, and not even the power button would get it back on until i completely unplugged it and let it sit for a moment.
i'm fairly sure this indicates the interrupt handler going boink. i'm not sure if i should set something in the bios (didn't see a lot of options there) or try and see if i have a disk with the diagnostic software for one of the nics so i can maybe force it to take a certain set of resources. or maybe there's something in linux (freesco flavored) that i need to change.
any fingers in the right direction would be greatly appreciated. i'll try the freesco board if i get no hits here, but i get the feeling it's a distro-independent problem.
what i've got in this box is two pci nics, different brands (both ne2000 compatible, i think one is a at2000t pnp and the other is a trend (tci-p/w or tpci/w or something like that). i'm fairly sure i've got the software disk for at least one of them.
linux finds both nics fine, puts them on eth0 and eth1. they are both on irq 9 though, which i'm not very clear about though i think that's supposed to be OK for PCI periphs. they are also set to I/O addresses that are VERY close together (0xfce0 and 0xfcc0), which i don't know if that is OK for PCI periphs again.
i think it hangs a bit after the DHCP daemon successfully initializes attached to eth0, and then whatever daemon listens to the internal network on eth1 starts.
when i was testing it off the network, it would hang trying to initialize DHCP through the first nic ("Waiting for DHCPOFFER on eth0" cuz it wasn't attached to the cable modem), but i could switch to another console (alt-f2) and log in, mess with stuff, yada yada yada.
when i finally hooked it up to the cable modem, it would finish the DHCP daemon, finish starting services, and present a login prompt on the first console. but either immediately or very shortly afterward, the keyboard would quit responding; not even settting scroll or numlock would work, no three-finger salute, nada. if i left it sitting there for a few minutes the box would just shut itself off, and not even the power button would get it back on until i completely unplugged it and let it sit for a moment.
i'm fairly sure this indicates the interrupt handler going boink. i'm not sure if i should set something in the bios (didn't see a lot of options there) or try and see if i have a disk with the diagnostic software for one of the nics so i can maybe force it to take a certain set of resources. or maybe there's something in linux (freesco flavored) that i need to change.
any fingers in the right direction would be greatly appreciated. i'll try the freesco board if i get no hits here, but i get the feeling it's a distro-independent problem.