Hi Andy, On Thu, 20 Oct 2005, Andy Clark wrote: > I'm experiencing a problem with a newly-bought Nebula uDigiTV USB2 box. > > It's brand new, so I'm assuming it'll have an mt351 frontend rather than an > nxt6000 one. I've compiled a vanilla 2.6.13 kernel on my system (CentOS 4.1), > but I've used the "makelinks" script from the dvb-kernel CVS (as of > 2005-10-19) to make use of the latest dvb-kernel code. The kernel compiles > and boots without a hitch, but the problem occurs when the modules are > loaded. > Oct 19 23:48:52 vim kernel: >>> 02 7f 01 00 00 00 00 > Oct 19 23:48:52 vim kernel: <<< 02 7f 01 8a 00 00 00 > Oct 19 23:48:52 vim kernel: >>> 02 73 01 00 00 00 00 > Oct 19 23:48:52 vim kernel: <<< 02 73 01 8a 00 00 00 Here we have it: When trying to identify the mt352 (0x7f) it gets 0x8a (whereas 0x13 is expected). Same for nxt6000: 0x0b expected, 0x8a delivered. So either you have a new very new device with an unkown demod inside, or your box is broken :). Does it work in windows? > These last few lines repeat indefinitely - I imagine because, while I'm > specifying the "disable_rc_polling=1" option to dvb_usb in my modprobe.conf > file, the insmod.sh script isn't using the option. You are right. insmod.sh does not care about any options in /etc/. Where is the "Unable to handle kernel paging request" from your subject? regards, Patrick. -- Mail: patrick.boettcher@xxxxxxx WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/
