Your message dated Mon, 16 Jun 2008 00:49:55 +0200
with message-id <[EMAIL PROTECTED]>
and subject line re: linux-image-2.6.24-1-amd64: DVB driver budget-ci fails to
load frontend driver, missing symbol tda10045_attach
has caused the Debian Bug report #464223,
regarding linux-image-2.6.24-1-amd64: DVB driver budget-ci fails to load
frontend driver, missing symbol tda10045_attach
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
464223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464223
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: linux-image-2.6.24-1-amd64
Version: 2.6.24-2
Severity: normal
In 2.6.24, the budget-ci module can't load the driver for my TDA10045H
front-end, saying that tda10045_attach is missing.
During loading of my DVB card driver, budget-ci, I get:
Feb 3 01:25:08 noddy kernel: DVB: Unable to find symbol tda10045_attach()
Feb 3 01:25:08 noddy kernel: budget-ci: A frontend driver was not found for
device 1131/7146 subsystem 13c2/1011
This also happened in 2.6.22-3, although 2.6.22-2 was fine.
Hamish
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.24-1-amd64 depends on:
ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy
ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo
ii yaird [linux-initramfs-tool] 0.0.12-25 Yet Another mkInitRD
linux-image-2.6.24-1-amd64 recommends no packages.
-- debconf information:
linux-image-2.6.24-1-amd64/preinst/abort-overwrite-2.6.24-1-amd64:
linux-image-2.6.24-1-amd64/postinst/old-dir-initrd-link-2.6.24-1-amd64: true
linux-image-2.6.24-1-amd64/preinst/failed-to-move-modules-2.6.24-1-amd64:
linux-image-2.6.24-1-amd64/postinst/bootloader-test-error-2.6.24-1-amd64:
linux-image-2.6.24-1-amd64/postinst/create-kimage-link-2.6.24-1-amd64: true
linux-image-2.6.24-1-amd64/postinst/depmod-error-initrd-2.6.24-1-amd64: false
linux-image-2.6.24-1-amd64/preinst/overwriting-modules-2.6.24-1-amd64: true
linux-image-2.6.24-1-amd64/postinst/bootloader-error-2.6.24-1-amd64:
linux-image-2.6.24-1-amd64/postinst/old-initrd-link-2.6.24-1-amd64: true
linux-image-2.6.24-1-amd64/postinst/kimage-is-a-directory:
linux-image-2.6.24-1-amd64/preinst/bootloader-initrd-2.6.24-1-amd64: true
linux-image-2.6.24-1-amd64/preinst/initrd-2.6.24-1-amd64:
linux-image-2.6.24-1-amd64/prerm/removing-running-kernel-2.6.24-1-amd64: true
linux-image-2.6.24-1-amd64/postinst/depmod-error-2.6.24-1-amd64: false
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.24-1-amd64/preinst/lilo-initrd-2.6.24-1-amd64: true
linux-image-2.6.24-1-amd64/postinst/old-system-map-link-2.6.24-1-amd64: true
linux-image-2.6.24-1-amd64/preinst/lilo-has-ramdisk:
linux-image-2.6.24-1-amd64/preinst/abort-install-2.6.24-1-amd64:
linux-image-2.6.24-1-amd64/prerm/would-invalidate-boot-loader-2.6.24-1-amd64:
true
linux-image-2.6.24-1-amd64/preinst/elilo-initrd-2.6.24-1-amd64: true
--- End Message ---
--- Begin Message ---
hmm old abi breakage, solved since. thus clsoing
--
maks
--- End Message ---
