ASRock ION330HT setup from XBMC Live (XBMC Freak version 9.11.14). In the meantime upgraded to Dharma.
Live TV support via ppa:lars-opdenkamp/xbmc-pvr with TVheadend and USB-DVBS2 device Tevii S660
Folks,
I have Live TV in the above combination working however I have to boot twice.
When I power up all devices the first time XBMC (tvheadend) tells me "no device present".
When I power cycle XBMC (leaving the Tevii with power!) it comes up properly.
I captured an "uname -a", "lsusb", "dmesg | grep usb" output into two files to compare the differences. Here it is:
Code:
xbox@XIon:~$ diff Tev1.txt Tev2.txt
2c2
< Bus 001 Device 006: ID 9022:d660
---
> Bus 001 Device 005: ID 9022:d660
13a14
> usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
35d35
< usb 1-6: USB disconnect, address 5
38,39c38
< dvb-usb: MAC address reading failed.
< dvb-usb: no frontend was attached by 'TEVII S660 DVBS2 USB2.0'
---
> dvb-usb: MAC address: 00:18:bd:5c:4a:f0
44,57d42
< dvb-usb: TEVII S660 DVBS2 USB2.0 successfully deinitialized and disconnected.
< usb 1-6: new high speed USB device using ehci_hcd and address 6
< usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
< usb 1-6: configuration #1 chosen from 1 choice
< dvb-usb: found a 'TEVII S660 DVBS2 USB2.0' in cold state, will try to load a firmware
< usb 1-6: firmware: requesting dvb-usb-teviis660.fw
< dvb-usb: downloading firmware from file 'dvb-usb-teviis660.fw'
< usb 1-6: firmware: requesting dvb-usb-teviis660.fw
< dvb-usb: found a 'TEVII S660 DVBS2 USB2.0' in warm state.
< dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
< dvb-usb: MAC address: 00:18:bd:5c:4a:f0
< input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:04.1/usb1/1-6/input/input9
< dvb-usb: schedule remote query interval to 150 msecs.
< dvb-usb: TEVII S660 DVBS2 USB2.0 successfully initialized and connected.
I spot the message "MAC address reading failed" during the first boot sequence, but have neither an idea why this happens nor how to overcome this.
While working on my Sheevaplug Debian system I ran across the following
blog entry, but I don't think my device is as spoiled as this?!