[mythtvnz] Issues with Nova-500-td
Pshem Kowalczyk
pshem.k at gmail.com
Mon Oct 4 07:18:56 BST 2010
Hi,
I had to reload my main backend, that has a nova-500-td. After the
reload the nova card stopped working - the firmware can't be
downloaded any more onto the card. Udev times out on the operation:
Oct 4 19:04:20 mamaku kernel: [44343.028605] dvb-usb: found a
'Hauppauge Nova-TD-500 (84xxx)' in cold state, will try to load a
firmware
Oct 4 19:04:20 mamaku kernel: [44343.028609] usb 3-1: firmware:
requesting dvb-usb-dib0700-1.20.fw
Oct 4 19:05:20 mamaku kernel: [44403.029380] dvb-usb: did not find
the firmware file. (dvb-usb-dib0700-1.20.fw) Please see
linux/Documentation/dvb/ for more details on firmware-problems. (-2)
(firmware happily sits in /lib/firmware)
if I try to do it manually I get the following:
mamaku ~ # /lib64/udev/firmware --firmware=dvb-usb-dib0700-1.20.fw
--devpath=/devices/pci0000:00/0000:00:08.0/0000:01:06.2/usb3/3-1/firmware/3-1
libudev: set_loading: error: can not open
'/sys/devices/pci0000:00/0000:00:08.0/0000:01:06.2/usb3/3-1/firmware/3-1/loading'
Segmentation fault
I have an hvr2200 in the same box, but that firmware loads fine (using
saa7164 and tda18271 modules).
I tried 3 different kernels (2.6.33, .34 and .35) with the same
results. I also tried the hg version of v4l. I powered down the box
and let it rest for a few minutes to clear all 'old' state in the
card. I move the card to different slots all to no avail.
The one thing that I'm not sure about is the path for loading of the
firmware detected by the kernel. If you have a nova-500-td can you
please have a look in your /sys/devices to tell me if the 'loading'
entry exists in your setup? If you have any further ideas please let
me know too. I'm planing to return the card (it's only about 6 months
old) and get it replaced, but before I go there I would like to try
all other options.
thx for your help.
kind regards
Pshem
More information about the mythtvnz
mailing list