hello, i have the same problem here my configuration i use discover to load modules for pci devices (both on laptop and desktop) i have hotplug pci subsystem disabled on laptop, i use udev to rename eth0->lan, on desktop eth0 is eth0 ;) i have ifplugd configured to watch all hotplug interfaces and no static interface
i noticed it, when i switched from hotplug for pci to discover on my desktop (maybe it wasn't working before, but i don't restart my desktop offten so i didn't notice after boot, i have ifplugd running for lan interface, but it's not up, i was searching why, and it seems, that problem is, when you have /etc/networking/run/ifstate linked to /dev/shm ... appearently, it's not available, when hotplug launches ifplugd i created regular directory and file and lan is up after boot i fiddled a little with sequence of commands in rcS ... now it's S33mountall.sh S34mountvirtfs (we need /dev/shm mounted) S35ifupdown (we need /dev/shm/network/run/ifstate) S36discover (it loads e100, it seems to emit hotplug action -> launches ifplugd which ifups lan, so we need /dev/shm/network/run/ifstate) S40hotplug (is not important) (old sequence was S35mountall.sh S36discover S36mountvirtfs S39ifupdown S40hotplug ) and it also boots with lan ifuped what do you think? i think, it should work this way, maybe this bug should be assigned to another package (maybe it's complete gibberish, but it fixed my problem, it seems) well as i look on sequence of commands in rcS, it seem, that when e100 module was loaded by hotplug pci, ifupdown was already finished, so ifstate file existed cu libor
signature.asc
Description: OpenPGP digital signature
