On Fri, 2004-11-26 at 07:00 +0000, Michael A. Peters wrote: Please follow-up to fedora-ppc@xxxxxxxxxxxxxxxxxxx > Not using dhcp - using a static IP on my lan. > Network init script says it was starting, but eth0 was never brought > up. Later, when the computer starts, if ifup eth0 doesn't work, can you bring the interface up manually using ifconfig ? > It's possible that the network (ifcfg-eth0) setting set up by YDL were > not sufficient for FC - I tried manually adjusting ifcfg-eth0 to look > similar to the ifcfg-eth0 on an x86 FC3 box, but that didn't work - > even when I tried modprobing various modules I thought might be Why did you install YDL to bootstrap fedora? Fedora itself installs fine > responsible. I also tried running the network config tool - it didn't > recognize eth0. I suspect it may be fixed by a newer kernel, but there > were deps not installed when I tried to install it - I really need to > get one of those USB keychain thingies, but I don't have one. What kernel is this? > I tried modprobing mace, sungem, a few others that looked reasonable (I > believe mace is the correct one) - but the installed kernel is kind of sungem is the correct one. What iMac exactly do you have? We would appreciate lspci output > old (from C3T2). I want to try with a newer kernel before I file any > bug reports. I also want to pick up a USB key before I file a bug > report, to make it easier to try different kernels. Ok > While I highly doubt this has anything to do with it, this is a first > gen iMac but it has a Newer 433 G4 cpu daughtercard installed (opposed > to the 233 G3 it came with) - It's the second rev of the mobo (the one > used for Rev B/C/D iMacs) Hmm, post lscpi in your next post (only to fedora-ppc list). What does /proc/cpuinfo report ? (this is just for my curiosity) -- Colin Charles, byte@xxxxxxxxxxx http://www.bytebot.net/ "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi