depmod not run correctly for vmware modules
Bug #79655 reported by
Matt Zimmerman
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-restricted-modules-2.6.20 (Ubuntu) |
Fix Released
|
High
|
Kyle McMartin |
Bug Description
<mdz> kyle: hmm, looks like vmware-
mizar:[~] sudo modprobe vmmon
Password:
FATAL: Module vmmon not found.
mizar:[~] sudo depmod -a
mizar:[~] sudo modprobe vmmon
mizar:[~]
<kyle> hmm, odd.
<mdz> it's in postinst though
<mdz> kyle: it's not specifying a version; I bet it was run for the wrong kernel version
<kyle> that's entirely possible, especially if it got upgraded as well
The depmod command in postinst must specify the version of the kernel corresponding to the modules in the package.
Changed in linux-restricted-modules-2.6.20: | |
assignee: | nobody → kyle |
status: | Unconfirmed → Confirmed |
Changed in linux-restricted-modules-2.6.20: | |
status: | In Progress → Needs Info |
Changed in linux-restricted-modules-2.6.20: | |
status: | Needs Info → Fix Released |
To post a comment you must log in.
Fixed in a forthcoming upload.