On Fri, 2004-11-26 at 09:23 +0000, Michael A. Peters wrote:
> Later, when the computer starts, if ifup eth0 doesn't work,
can you
> bring the interface up manually using ifconfig ?
I tried (from within /etc/sysconfig/network-scripts) ./ifup eth0 and
that did not work.
Provide tcpdump output
tcpdump -i eth0
> > 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
No, it didn't. Not with the boot.iso for fc2 or fc3t2
The boot.iso would get stuck asking what network driver it should use,
it would never get beyond that. I've seen at least one other iMac
report that issue in the ppc archives.
Hmm, odd. I too have an iMac, and possibly Paul has tried it too
> What kernel is this?
It's the kernel that was in FC3T2
I'll have to set the iMac up again to get you more info - such as lspci
output.
Tree at duke?
> > 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
It's a tray loading iMac, Bondi Blue with Rev B. motherboard
Should be sungem
I'll set the iMac back up this weekend and get the lspci etc.
Good, without useful debugging information, we can't help you either
--
Colin Charles, byte(a)aeon.com.my
http://www.bytebot.net/
"First they ignore you, then they laugh at you, then they fight you,
then you win." -- Mohandas Gandhi