Hi everyone,
i compiled the last versions of kamikaze successfully, but as soon as i install
various packages e.g. one of these:
kmod-usb-core - 2.6.17-brcm-1 - Kernel Support for USB
kmod-usb-ohci - 2.6.17-brcm-1 - Kernel driver for OHCI USB controllers
kmod-usb-printer - 2.6.17-brcm-1 - Kernel modules for USB Printer support
kmod-usb-serial - 2.6.17-brcm-1 - Kernel Support for USB-to-Serial converters
kmod-usb-serial-belkin - 2.6.17-brcm-1 - Kernel Support for Belkin USB-to-Serial converters
kmod-usb-serial-ftdi - 2.6.17-brcm-1 - Kernel Support for FTDI USB-to-Serial converters
kmod-usb-serial-pl2303 - 2.6.17-brcm-1 - Kernel Support for Prolific PL2303 USB-to-Serial converters
kmod-usb-serial-visor - 2.6.17-brcm-1 - Kernel Support for Handspring Visor / Palm m50x / Sony Clie Driver
kmod-usb-storage - 2.6.17-brcm-1 - Kernel modules for USB storage support
kmod-usb-uhci - 2.6.17-brcm-1 - Kernel driver for UHCI USB controllers
kmod-usb2 - 2.6.17-brcm-1 - Kernel driver for USB2 controllers
i get the following dependancy error.
Cannot satisfy the following dependencies for kmod-madwifi:
'kernel (=2.6.17-brcm-1)'
here is my kernel-version
uname -a
Linux OpenWrt 2.6.17 #1 Thu Oct 12 04:58:18 CEST 2006 mips unknown
i tried,
ipkg install kernel
Package kernel (2.6.17-brcm-1) installed in root is up to date.
Nothing to be done
Done.
but the dependency error still remains.
even none of the "force-options" resolve the dependancy prob.
Force Options (use when ipkg is too smart for its own good):
-force-depends Make dependency checks warnings instead of errors
Install/remove package in spite of failed dependences
-force-defaults Use default options for questions asked by ipkg.
(no prompts). Note that this will not prevent
package installation scripts from prompting.
-force-reinstall Allow ipkg to reinstall a package.
-force-overwrite Allow ipkg to overwrite files from another package during an install.
-force-downgrade Allow ipkg to downgrade packages.
-force_space Install even if there does not seem to be enough space.
is this a general bug, a "developing issue" or am i just "dumb" :-))
best regards martin....