> Sounds like the module isn't loaded early enough at boot time.
Fedora will load the module the first time the interface is referenced as it has a entry in /etc/modprobe.conf for each interface, for example: alias eth0 3c59x alias eth1 3c59x alias eth2 8139too > I couldn't find such a file on our CentOS 5 systems and couldn't > find an equivalent "insmod" anywhere in the init scripts. Using /etc/modprobe.conf and a suitable alias statement is the usual technique for loading modules in Fedora and RHEL when they aren't loaded by udev. Something like the Debian approach can be done by creating an executable /etc/rc.modules containing #!/bin/sh /sbin/modprobe 3c59x /sbin/modprobe 8139too but I wouldn't recommend that. The modules then always get loaded (including in single user mode) so there's no easy way to recover from a module which panics during boot. Better to let the modules be loaded via modprobe.conf as the device is used, that is, later in initialisation. This makes reaching single user mode depend on less software working correctly. That in turn means that more problems can be fixed remotely, not by asking someone to insert a Recovery CD. > I couldn't find such a file on our CentOS 5 systems and couldn't find an > equivalent "insmod" anywhere in the init scripts. > Maybe you can just force an insmod in the pppd configs or init script as a > work around until you find the right way. Ugly. Probably sinful too. -- Glen Turner <http://www.gdt.id.au/~gdt/> 0416 295 857 or +61 416 295 857 -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
