Bug: 3.1.9: dahdi/kernel mismatch breaks OS upgrade
Posted: Thu Apr 14, 2011 4:23 pm
Vicibox 3.1.9 installs a 2.6.34.7 kernel, but a dahdi-kmp-pae-2.40 module built and tagged for kernel 2.6.34.0.
This means that *anything* you do with YoU after install, either via the vicibox-install script or manually, breaks dahdi ('s dependencies), forcing YoU to uninstall it.
When there's no dahdi package installed, (and assuming you require dahdi-dummy for lack of hardware drivers), Asterisk 1.4 won't start.
Doing no OS upgrade will, for some reason, allow dahdi to load, even though it *is* built for a different kernel.
Finding this out takes about 4 or 5 complete reinstalls, since it's not documented, and the documentation there *is* recommends doing the OS upgrade.
The probable cause is that the Studio build gets its kernel for the install from the repo -- which is a moving target while the dahdi modules, being from a different repo, don't move as fast -- but not being familiar with the internals of the installer appliance, I of course can't be sure.
This means that *anything* you do with YoU after install, either via the vicibox-install script or manually, breaks dahdi ('s dependencies), forcing YoU to uninstall it.
When there's no dahdi package installed, (and assuming you require dahdi-dummy for lack of hardware drivers), Asterisk 1.4 won't start.
Doing no OS upgrade will, for some reason, allow dahdi to load, even though it *is* built for a different kernel.
Finding this out takes about 4 or 5 complete reinstalls, since it's not documented, and the documentation there *is* recommends doing the OS upgrade.
The probable cause is that the Studio build gets its kernel for the install from the repo -- which is a moving target while the dahdi modules, being from a different repo, don't move as fast -- but not being familiar with the internals of the installer appliance, I of course can't be sure.