On Tue, 7 Apr 2009, Kaj Niemi wrote:
On Apr 7, 2009, at 14:52, Ben wrote:
That particular string is there in modules.alias on RHEL 5.3 and the
e1000e driver seems to have that as well inside itself...
So one wonders what the problem is... Do other operating systems work
with it? Have you tried an installation of Fedora 9 or 10? Or even
another distribution altogether, or Windows? Might be worth confirming
that it's the OS that's at fault...
I got the Fedora 11 beta installed with pxe without any troubles.
I meant without PXE, but in the normal manner, and then whether the NIC
worked as advertised during normal operation. But never mind.
Further troubleshooting with RHEL 5.3 seems to indicate that the
driver/chip behaves funnily if one has "spanning-tree porfast" enabled on
PXE ports. The other side is a Catalyst 2960G running 12.2(50)SE.
Disabling portfast makes things work during the RHEL 5.3 install while
Fedora 11 did get installed even with it enabled.
Probably something to do with needing the port to settle before it'll pass
data. It's something we used to encounter with certain models of Dell
PowerEdge; that the connection wouldn't come up until just _after_ the time
the kickstart wanted to use the port.
Ben
--
Unix Support, MISD, University of Cambridge, England
Plugger of wire, typer of keyboard, imparter of Clue
Life Is Short. It's All Good.
_______________________________________________
rhelv5-list mailing list
rhelv5-list@redhat.com
https://www.redhat.com/mailman/listinfo/rhelv5-list
