Bug#253999: discover1: bad module locks system: discover just tries again at reboot
Package: discover1
Version: 1.5-9
Severity: minor
Not sure if this has been fixed (apparently Im a version or 3 behind, but
I couldnt find the latest one at my local mirror yet).
The BTTV driver locks the system good and proper if loaded as the driver
for the BT878 based Twinhan Visionplus cards.
Unfortunately, discover doesn't notice the hard lock, and upon rebooting,
BTTV is loaded and locks the system again.
The problem is that the cards do have the same vendor and device numbers
as real BTTV cards, so the module "matches" but without options, dies.
I dont know what currently happens in this prog (Im not a big coder), but
I think what needs to be done, is have discover write to a file somewhere
*before* attempting to load any module, and then also record it's success
after. It either doesnt do this at the moment, or default conditions may
put it running on a read-only filesystem (I havent looked at this yet).
I have tried puting "skip bttv" in the discover.conf but it didnt seem to
work. Probably a case of me puting things in the wrong place (or a typo
caused by this dodgy old keyboard I've been forced back to using).
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.25-1-386
Locale: LANG=en_AU, LC_CTYPE=en_AU
Versions of packages discover1 depends on:
ii dash 0.4.26 The Debian Almquist Shell
ii debconf 1.4.25 Debian configuration management sy
ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries an
ii libdiscover1 1.5-9 hardware identification library
-- debconf information:
discover/manage_cdrom_devices: true
discover/cdrom_base_mountpoint: /
discover/cdrom_base_mountpoint_error:
Reply to: