On Sun, 2004-06-06 at 14:22, dircha wrote: > > Bingo! Running "lsmod" in the working vs non-working config shows > > that a whole bunch of drivers are no longer being loaded after the > > dist-upgrade. Running modprobe to force the network drivers to be > > loaded restores network connectivity. > > > > So the question now is: why did dist-upgrade from testing to unstable > > mess around with the list of modules that are loaded at boot time? > > That's sort of a rhetorical question; I don't hugely care as I now > > have a working system [at least I can manually force the necessary > > drivers to be loaded on boot]. But presumably other people will be > > bitten by this too...
Just for the record: I did a dist-upgrade today and rebooted, and all the appropriate modules are now loading automatically. Whatever the problem was, it seems to have been fixed in the latest unstable. Dircha: thanks for the additional info on modutils. Regards, Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
