[lug] Fedora 8 on new hardware network booting problem

[Swavek Skret]

I have an additional info on the possible error cause. I plugged a USB to
Ethernet adaptor and was able to boot successfully from the network. After
that, I added to my kickstart file post section a few commands to build and
install the e1000e driver. Well, it failed again but provided some more
readable error:

FATAL: error inserting e1000e: invalid module format
<3>e1000e: version magic '2.6.23.1-42.fc8 SMP mod_unload 686 4KSTACKS'
should be '2.6.23.1-42.fc8 SMP mod_unload 586 4KSTACKS'

which I think suggests the 32 vs 64 bit architecture mismatch. At that point
however, I can use the modprobe -f to force an installation and it works OK.
I would like to be able to tell kernel to do the same thing during the
pre-loading stage but do not know how to do that.

Thanks,
Swavek

On Sat, Aug 14, 2010 at 12:32 AM, Lee Woodworth <blug-mail at duboulder.com>wrote:

> On 08/13/10 20:20, Swavek Skret wrote:
> > Dave,
> >
> > No, I do not get a shell prompt. Instead, when the pxe fails to load the
> > kickstart file, I get switched to the manual installation during which I
> can
> > press cntr-alt-F3 which gives me some debug output. In the output, I see
> > other modules being loaded from the /tmp directory like libdata and
> others
> > before it breaks with the e1000e.
>
> Have you checked the release notes for the e1000e driver? You may also
> want to check dependencies for the module. I have had dependent modules not
> get autoloaded in an initramfs that I built from scratch.
>
> Is the install DVD kernel the same version and config as the one that gets
> loaded via PXE?
>
> >
> > Thanks,
> > Swavek
> >
> > On Fri, Aug 13, 2010 at 5:27 PM, David L. Anselmi <anselmi at anselmi.us
> >wrote:
> >
> >> Swavek Skret wrote:
> >>> When I boot up from the network, the board successfully sends dhcp
> >> request, retrieves the PXE
> >>> files, loads the initrd.img file and breaks when inserting the e1000e
> >> module with the following
> >>> message:
> >>> ...
> >>> Warning: failed to insert module (8)
> >>> Error: failed to insert /tmp/e1000e.ko
> >>
> >> Do you get a shell in the initrd?  Perhaps the module isn't in /tmp and
> you
> >> need to put it there or
> >> tell the code the right place to look.
> >>
> >> Dave
> >> _______________________________________________
> >> Web Page:  http://lug.boulder.co.us
> >> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >> Join us on IRC: irc.hackingsociety.org port=6667
> channel=#hackingsociety
> >>
> >
> >
> >
> > _______________________________________________
> > Web Page:  http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20100818/c26ded6f/attachment.html>