On Sun, Oct 22, 2006 at 01:11:34PM +0200, Mau wrote:
> Package: irda-utils
> Version: 0.9.18-3
> Severity: important
>
>
> As you can see in the following 'Debconf information' for my smsc-ircc2
> the ali-ircc module is chosen: this results in a
> /etc/modprobe.d/irda-utils like this:
[snip]
>
> options ali-ircc smsc-ircc2
> alias irda0 ali-ircc
>
> ===== END ====
>
> It's obvious that the ali-ircc module can't be loaded with the
> 'smsc-ircc2' parameter... this prevents module loading and results in an
> irda port not working.
The problem is that 'smsc-ircc2' is set as a module option in your
debconf information. From your bug report:
> -- debconf information:
> * irda-utils/firopt: smsc-ircc2
^^^^^^^^^^
This could have been filled out by you, or by a wrong configuration and
an upgrade from a previous version older than 0.9.16-5. Did you upgrade
from such an older version? Was your old /etc/modprobe.d/irda or
/etc/modutils/irda correct? From the preinst file:
if [ -f "$modules" ]; then
if egrep "^alias irda0" $modules > /dev/null 2>&1 ; then
set `egrep "^alias irda0" $modules`
db_set $PACKAGE/firdev "$3"
if dpkg --compare-versions "$PREV" gt 0.9.14-17; then
set `egrep "^options $3" $modules`;
shift; shift
else
shift; shift; shift;
fi
db_set $PACKAGE/firopt "$*"
fi
fi
Only that code (or your answer to the debconf question) could have set that
debconf question to an invalid value such as 'smc-ircc2'.
Regards,
Alberto
--
Alberto Gonzalez Iniesta | Formación, consultoría y soporte técnico
agi@(inittab.org|debian.org)| en GNU/Linux y software libre
Encrypted mail preferred | http://inittab.com
Key fingerprint = 9782 04E7 2B75 405C F5E9 0C81 C514 AF8E 4BA4 01C3
