Hi David, On 6/9/07, David Engel <[EMAIL PROTECTED]> wrote: > Hi, > > I just got a Kworld ATSC 115 to play around with and maybe eventually > use with MythTV. The analog support appears to work just fine, but > I'm having a problem loading the nxt2004 firmware for the digital > support. > > I downloaded the dvb-fe-nxt2004.fw firmware fileusing the > get_dvb_firmware script and put it in /lib/firmware, so I don't think > missing firmware is the cause. > > [EMAIL PROTECTED] ll /lib/firmware > ~ > total 12 > -rw-r--r-- 1 root root 9584 Jun 9 11:26 dvb-fe-nxt2004.fw > > Is the 9584 size correct? It seems rather small. > > Here is a snippet from my kernel log when loading the saa7134-dvb > module and trying to do an atscscan. The kobject_add failure looks > awfully suspicious to me and is probably the major problem. > > Jun 9 13:42:08 opus kernel: nxt200x: NXT2004 Detected > Jun 9 13:42:08 opus kernel: DVB: registering new adapter (saa7133[0]). > Jun 9 13:42:08 opus kernel: DVB: registering frontend 0 (Nextwave NXT200X > VSB/QAM frontend)... > Jun 9 13:42:33 opus kernel: nxt2004: Waiting for firmware upload > (dvb-fe-nxt2004.fw)... > Jun 9 13:42:33 opus kernel: kobject_add failed for i2c-2 with -EEXIST, don't > try to register things with the same name in the same directory. > Jun 9 13:42:33 opus kernel: [<c01fc204>] kobject_shadow_add+0x114/0x190 > Jun 9 13:42:33 opus kernel: [<c024d88f>] device_add+0xbf/0x670 > Jun 9 13:42:33 opus kernel: [<c01fc2ef>] kobject_init+0x2f/0x50 > Jun 9 13:42:33 opus kernel: [<f88771cb>] _request_firmware+0x11b/0x360 > [firmware_class] > Jun 9 13:42:33 opus kernel: [<f88774af>] request_firmware+0xf/0x20 > [firmware_class] > Jun 9 13:42:33 opus kernel: [<f8a1ab23>] nxt200x_init+0xa3/0xc70 [nxt200x] > Jun 9 13:42:33 opus kernel: [<c0383091>] __sched_text_start+0x301/0x960 > Jun 9 13:42:33 opus kernel: [<c03830bd>] __sched_text_start+0x32d/0x960 > Jun 9 13:42:33 opus kernel: [<f8a0d51d>] dvb_frontend_init+0x1d/0x60 > [dvb_core] > Jun 9 13:42:33 opus kernel: [<c0114cf9>] __wake_up_common+0x39/0x60 > Jun 9 13:42:33 opus kernel: [<f8a0e825>] dvb_frontend_thread+0x65/0x2f0 > [dvb_core] > Jun 9 13:42:33 opus kernel: [<c0115acf>] complete+0x3f/0x60 > Jun 9 13:42:33 opus kernel: [<f8a0e7c0>] dvb_frontend_thread+0x0/0x2f0 > [dvb_core] > Jun 9 13:42:33 opus kernel: [<c012ec4a>] kthread+0xba/0xf0 > Jun 9 13:42:33 opus kernel: [<c012eb90>] kthread+0x0/0xf0 > Jun 9 13:42:33 opus kernel: [<c0103773>] kernel_thread_helper+0x7/0x14 > Jun 9 13:42:33 opus kernel: ======================= > Jun 9 13:42:33 opus kernel: fw_register_device: device_register failed > Jun 9 13:42:33 opus kernel: nxt2004: Waiting for firmware upload(2)... > Jun 9 13:42:33 opus kernel: nxt2004: No firmware uploaded (timeout or file > not found?) > Jun 9 13:42:33 opus kernel: nxt200x: Timeout waiting for nxt2004 to init. >
compile the i2c framework as modules, then the error will go away. I already discussed this bug with other developers, and I'll submit a bugfix soon (it's a bug in the firmware class code which tries to create duplicate sysfs entries which already got created by the i2c-dev code) cheers, Markus > I tried googling for similar problem reports, but couldn't find any. > Does anyone know what might be wrong? This was all done with the > v2.6.21.4 Linux kernel. I can easily try other kernel versions or DVB > drivers to test. > > David > -- > David Engel > [EMAIL PROTECTED] > > _______________________________________________ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > -- Markus Rechberger _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
