You can use the powerfull install command in your modprobe.conf.<br>Putting forcedeth&nbsp; in /etc/modprobe.d/blacklist and forcing it install in modprobe.conf after e1000 via a install command could be a solution.<br>I never tested or tried this, I dont know if it will work.
<br>Try to setup HWADDR first.<br><br>Their is also a lot of module dependencies in /lib/modules/ maybe you could try to make forcedeth&nbsp;&nbsp; dependent of e1000 in these file.<br>But dependencies are compiled at every boot !<br>
<br><div>Regards<br>
<br>
<span class="gmail_quote">On 8/31/07, <b class="gmail_sendername">Jerry Geis</b> &lt;<a href="mailto:geisj@pagestation.com">geisj@pagestation.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is there a method to control module load order?<br><br>I want to ensure that the e1000 module loads before the forcedeth driver.<br><br>Jerry<br>_______________________________________________<br>CentOS mailing list<br><a href="mailto:CentOS@centos.org">
CentOS@centos.org</a><br><a href="http://lists.centos.org/mailman/listinfo/centos">http://lists.centos.org/mailman/listinfo/centos</a><br></blockquote></div><br><br clear="all"><br>-- <br>Alain Spineux<br>aspineux gmail com
<br>May the sources be with you