| LinHES Forums http://forums.linhes.org/ |
|
| udev and dvb-t usb tuners http://forums.linhes.org/viewtopic.php?f=2&t=17094 |
Page 1 of 1 |
| Author: | gazza [ Thu Oct 25, 2007 10:27 am ] |
| Post subject: | udev and dvb-t usb tuners |
Hi I've been struggling with udev and my 3 usb dvb-t tuners since the upgrade to r5f27 from r5e50. The tuner device assignments bounce around a lot more now, whereas they were a lot more stable under r5e50. Occasionally they seem to overlap, and different tuners in myth will access the same physical tuner I have created udev rules to create symlinks called usbdvb*, (from 0 to 2), and that works and creates the symlinks. However, for these cards, which is card type "dvb dtv capture card" in myth-setup, it will only let me choose card number, not actual device assignments such as /dev/dvb0 etc. the udev rule seems to be a complete pta to decypher. Any ideas, other than manually connecting each tuner after powerup, bearing in mind I'd like to get acpi wakeup working again. thanks Gary |
|
| Author: | turpie [ Thu Oct 25, 2007 6:20 pm ] |
| Post subject: | |
What type of tuners are you using? In an earlier version of KM I had to unload and reload the module after bootup to get the firmware to load properly. If your tuners are using different drivers it might work to use a script to manually load the driver modules in an order that works. |
|
| Author: | soundoff [ Thu Oct 25, 2007 7:48 pm ] |
| Post subject: | |
search for a post entitled "edev sucks" it gives suggestions on how to fix your device allocations. i fixed mine by swapping cards round in the PCI ports. |
|
| Author: | gazza [ Fri Oct 26, 2007 1:26 am ] |
| Post subject: | |
to answer the 2 replies so far. I'm using freecom dvb-t usb tuners. the evidence from dmesg is that the three tuners are being picked up correctly and the firmware is being loaded correctly onto each tuner. I have created a local udev rule to map symlinks to each tuner, and that rule is being executed correctly. In myth-setup though I cannot identify this type of tuner by /dev/video0 ( for example). I have to select each tuner just by number 0,1,2, which means that the symlink trick is useless for me. I need to be able to create 3 rules based probably on the dev id (14aa:0221 for example) to map a specific device for each tuner which would need to be /dev/dvb/adaptorX. thanks gaz |
|
| Author: | turpie [ Sun Oct 28, 2007 5:12 pm ] |
| Post subject: | |
What does dmesg say for these devices? |
|
| Author: | gazza [ Mon Oct 29, 2007 3:07 pm ] |
| Post subject: | |
Extracted section from dmesg Code: dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. NET: Registered protocol family 23 usb 4-1: new high speed USB device using ehci_hcd and address 6 fuse init (API version 7.7) usb 4-1: configuration #1 chosen from 1 choice dvb-usb: found a 'WideView WT-220U PenType Receiver (based on ZL353)' in warm state. dvb-usb: will use the device's hardware PID filter (table count: 15). DVB: registering new adapter (WideView WT-220U PenType Receiver (based on ZL353)) DVB: registering frontend 0 (WideView USB DVB-T)... input: IR-receiver inside an USB DVB receiver as /class/input/input0 dvb-usb: schedule remote query interval to 300 msecs. dvb-usb: WideView WT-220U PenType Receiver (based on ZL353) successfully initialized and connected. NET: Registered protocol family 17 NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver usb 4-4: new high speed USB device using ehci_hcd and address 7 usb 4-4: configuration #1 chosen from 1 choice dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' in warm state. dvb-usb: will use the device's hardware PID filter (table count: 15). DVB: registering new adapter (WideView WT-220U PenType Receiver (Typhoon/Freecom)) DVB: registering frontend 1 (WideView USB DVB-T)... input: IR-receiver inside an USB DVB receiver as /class/input/input1 dvb-usb: schedule remote query interval to 300 msecs. dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) successfully initialized and connected. usb 4-3: new high speed USB device using ehci_hcd and address 8 usb 4-3: configuration #1 chosen from 1 choice dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' in warm state. dvb-usb: will use the device's hardware PID filter (table count: 15). DVB: registering new adapter (WideView WT-220U PenType Receiver (Typhoon/Freecom)) DVB: registering frontend 2 (WideView USB DVB-T)... input: IR-receiver inside an USB DVB receiver as /class/input/input2 dvb-usb: schedule remote query interval to 300 msecs. dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) successfully initialized and connected. The three tuners are picked up in dmesg as shown above and appear to be OK. The main problem is that myth sometimes uses the hardware tuner 0 as tuner 0 and 2. I have tested this by using live tv and switching tuners and watching both the messages in log files, and the activity lights on the tuners themselves. This often leads myth to miss some recordings. A cold reboot will ususally fix this. It has to be a cold boot to reset the tuner firmware. This behavior only started when I upgraded to r5e50, when udev started, and has become worse with the upgrade to r5f27. The other wierd thing is if I remove one tuner the box only picks one tuner, and often none. A single tuner is picked up fine all the time. It is very weird, and I'd be tempted to dump the tuners, but am struggling to find a low-profile pci alternative which is not going to give me headaches, nova-t 500 would be a great card but seems to have different hardware revisions which don't all seem to be supported.[/code] |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|