I see what you're saying, but there's no module to load once the
virtualbox-ose-source is upgraded and neither is there anything found to
unpack. Yet aptitude will swear that it is installed.
The only thing I have gotten to work is the original module installed by
aptitude and then auto installed by module assistant. If I just try to
load the module after aptitude upgrades it, there is nothing there to
load. I have it in /etc/modules.conf, but it doesn't get started. Only
the one which module assistant will install turns up and allows
virtualbox to start the virtual machine.
Must be some other way besides module assistant that I haven't a clue
about. I suppose the same situation exists for NVidia. No way to load
that kernel either for me unless module assistant can build it. So for
that, since there isn't an older version for module assistant to use
like there is for virtualbox-ose, I had to install the downloaded binary
from NVidia, which is something I had been attempting to avoid doing.
Someone has to write new guides as I see nothing around besides either
module assistant or building the source manually in that debian wiki
NVidia guide. Is that what we're supposed to do from now on? Unpack
and build these sources ourselves manually?
And that's supposed to be the better, new and improved thing? No
thanks. Go back to the old way where this stuff was semi-automatic.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
