Hello, I'm using 2.6.0 and CVS sources too, they do work fine. I applied the (at the time) 16 patches and did ./makelinks /usr/src/linux I don't know I was simply repeating the same thing but did it anyways.
The firmware needs to be placed in /usr/lib/hotplug/firmware/dec2000t.bin Since your kernel compiled I guess you placed it there. Have you enabled hotpluging and installed the hotpluging service? If not this is probably your problem as everything started working once I did this too. Enable firmware hotplugging Device Drivers >> Generic Driver Options >> Hotplug firmware loading support (I built mine into the kernel rather than a module) And install the hotplugging from http://linux-hotplug.sourceforge.net/ or maybe there is a Fedora build? Adding hotplug as a boot service you should find that the dvb_core and ttusb_dec modules load automatically and the firmware is magically loaded too. Hope this helps. Regards Stefan On Mon, 05 Jan 2004 11:17:19 +0000 "Michael Jorgenson" <[EMAIL PROTECTED]> wrote: > Hi All, > > I have decided to bite the bullet and start using Fedora on my work laptop > instead of Windows 2000, and after getting most things working, I started trying > to get my DEC2000-T to talk. It worked fine under Win2K on my laptop, and has > pretty good reception here in Cardiff - approx. 40 TV and 30 radio channels > available. However, no luck so far... > > I've been reading through the mailing list archive, and believe that the problem > lies with inserting the boot code into the kernel module. I started by upgrading > the kernel to 2.6.0, compiling the source code from www.kernel.org rather than > relying on pre-packaged and patched RPMs. After searching through the mailing > list, I found some messages describing similar problems, and after installing > the ttusb-dec module in debug mode, noticed that the module appeared not to have > the firmware installed. Also, the module caused kernel panic messages when > loaded in debug mode. > > So, I have now tried with the very latest CVS kernel drivers, applied by using > the "make links" script as described in the CVS README file. The single module > version compiles properly. I have installed both the 2000-T and 3000-S firmware > as instructed: ls -l /usr/lib/hotplug/firmware/ > total 1368 > -rw-r--r-- 1 root video 462684 Jan 3 14:51 dec2000t.bin > -rw-rw-rw- 1 root video 462684 Apr 4 2003 > dvb-ttusb-dec-2000t-2.15a.fw > -rw-rw-rw- 1 root video 462684 Apr 4 2003 > dvb-ttusb-dec-3000s-2.15a.fw > ---- > > But, when installing the module, although the kernel no longer panics, dmesg > shows: > ---- > drivers/usb/core/usb.c: registered new driver TechnoTrend/Hauppauge DEC USB > hub 1-0:1.0: new USB device on port 2, assigned address 7 > ttusb_dec_probe > ttusb_dec_init_usb > ttusb_dec_alloc_iso_urbs > ttusb_dec_setup_urbs > ttusb_dec_init_stb > ttusb_dec_send_command > ttusb_dec_send_command: command: 0xAA 0x01 0x08 0x00 > ttusb_dec_send_command: result: 0x55 0x01 0x08 0x10 0x00 0x00 0x00 0x00 0x12 > 0x34 0x56 0x78 0xAB 0xCD 0xEF 0xAB 0x00 0x00 0x00 0x00 > ttusb_dec_boot_dsp > ttusb_dec_boot_dsp: Firmware (dvb-ttusb-dec-2000t-2.15a.fw) unavailable. > ttusb_dec_exit_usb > ttusb_dec_free_iso_urbs > --- > > For info, my digibox reports firmware version 0.78, dated 16th October 2002, and > I'm using the UHCI drivers. Laptop is by Samsung, containing mobile P4 chip. > > Please help! > > Thanks, > Michael > > (PS. Apologies if this message appears more than once - our mail systems seem to > have been a bit upset over the holidays about sending mail externally - so I'm > resending this email) > > > -- > Info: > To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as > subject. > -- Stefan Weidt 9905090 Chemical Physics 5MX Edinburgh University ICQ: 37376819 MSN: [EMAIL PROTECTED] -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
