LinHES Forums http://forum.linhes.org/ |
|
Firewire newbie - Black Picture Can't detect 6200 http://forum.linhes.org/viewtopic.php?f=6&t=16470 |
Page 1 of 1 |
Author: | yong_sa [ Wed Sep 12, 2007 5:21 pm ] |
Post subject: | Firewire newbie - Black Picture Can't detect 6200 |
Hello: I installed a DCT 6200 on a fresh Knoppmyth install from September 9th. I can't get any picture to come on the screen. I ran the following commands: Quote: root@mythtv:/home/mythtv# plugreport Host Adapter 0 ============== Node 0 GUID 0x200000000300138d ------------------------------ libiec61883 error: error reading oMPR libiec61883 error: error reading iMPR Node 1 GUID 0x0019a6fffef37a39 ------------------------------ oMPR n_plugs=1, data_rate=2, bcast_channel=63 oPCR[0] online=1, bcast_connection=0, n_p2p_connections=0 channel=0, data_rate=2, overhead_id=0, payload=376 iMPR n_plugs=0, data_rate=2 I then ran this command: Quote: plugctl -n 1 opcr[0].bcast_connection=1 plugctl -n 1 opcr[0]plugctl -n 1 opcr[0].bcast_connection=1 .channel=63 I don't get errors. I select "Watch TV". The box says, 0 then 3, and I get a black screen for about 10 seconds. It then goes back to the menu. So there is some sort of communication via firewire, it's just that no pictures are going through. I went to the mythbackend log and got the following: Quote: 2007-09-12 16:22:06.922 adding: mythtv as a client (events: 0)
2007-09-12 16:22:06.924 TVRec(1): Changing from None to WatchingLiveTV 2007-09-12 16:22:06.928 TVRec(1): HW Tuner: 1->1 libiec61883 warning: Established connection on channel 0. You may need to manually set the channel on the receiving node. 2007-09-12 16:22:08.624 FireRec: Buffered packets 2000 (8000 KB) 2007-09-12 16:22:14.084 Expiring TV Guide from Wed Sep 12 15:00:00 2007, 0 MBytes, forced expire (LiveTV recording) 2007-09-12 16:22:15.148 TVRec(1): Changing from WatchingLiveTV to None 2007-09-12 16:22:23.643 FireRec: No Input in 15 seconds [P:0 N:1] (select) 2007-09-12 16:22:23.661 Finished recording TV Guide: channel 1002 Any advice would be greatly appreciated from you firewire gurus! Thanks so much. yong_sa |
Author: | yong_sa [ Thu Sep 13, 2007 9:15 am ] |
Post subject: | |
If there's any more information that you need, please let me know. I've searched throughout the forums without success. Thank you so much. |
Author: | mooseboots [ Thu Sep 13, 2007 9:09 pm ] |
Post subject: | I have the same issue |
I have the same issue. I can change the channel, and see that the command is going over FireWire to the cable box, but no picture. I had this working at one point in time. Don't know what I did to screw it up. Please re-post here if you work out a solution, and I will do likewise. |
Author: | yong_sa [ Fri Sep 14, 2007 12:13 pm ] |
Post subject: | |
Here's some more information just in case it will help. It looks like there's some communication because I get a 0 whenever I try to start live tv. But I still get a black screen. Here's the parse from the dmesg command pertaining to the 1394 firewire: Quote: dmesg ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[11] MMIO=[e2010000-e20107ff] Max Packet=[2048] IR/IT contexts=[4/8] ieee1394: Host added: ID:BUS[0-00:1023] GUID[200000000300138d] ieee1394: Node added: ID:BUS[0-01:1023] GUID[0019a6fffef37a39] ieee1394: raw1394: /dev/raw1394 device initialized eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1) ieee1394: sbp2: Try serialize_io=0 for better performance ieee1394: Node suspended: ID:BUS[0-01:1023] GUID[0019a6fffef37a39] ieee1394: Node resumed: ID:BUS[0-01:1023] GUID[0019a6fffef37a39] Here's the result that I get when I try to run 6200ch: Quote: root@mythtv:/home/hrcruz# 6200ch -v 3 starting with node: 1 node 1: vendor_id = 0x000019a6 model_id = 0x0000620a Could not find Motorola DCT-6200 on the 1394 bus. here's what I get when I try to run the firewire tester as stated in other posts: Quote: root@mythtv:/home/hrcruz# firewire_tester -B -n 1 -v
raw1394: Allocating handle, port 0. Action: Attempt to fix broadcast connection 1 times, node 1 Broadcast: Creating, node 1, channel 62 Broadcast: Testing...Failed Broadcast: Disconnecting. P2P: Creating, node 1, channel 1 P2P: Testing...Failed P2P: Disconnecting. P2P: Creating, node 1, channel 1 P2P: Testing...Failed P2P: Disconnecting. P2P: Creating, node 1, channel 1 P2P: Testing...Failed P2P: Disconnecting. P2P: Creating, node 1, channel 1 P2P: Testing...Failed P2P: Disconnecting. P2P: Creating, node 1, channel 1 P2P: Testing...Failed P2P: Disconnecting. P2P: Creating, node 1, channel 1 P2P: Testing...Failed P2P: Disconnecting. P2P: Creating, node 1, channel 1 P2P: Testing...Failed P2P: Disconnecting. P2P: Creating, node 1, channel 1 P2P: Testing...Failed P2P: Disconnecting. P2P: Creating, node 1, channel 1 P2P: Testing...Failed P2P: Disconnecting. P2P: Creating, node 1, channel 1 P2P: Testing...Failed P2P: Disconnecting. Broadcast Fix: Failed raw1394: Releasing handle. Hopefully this info will help everyone out for a solution. I have confirmed that my Cable provider has activated the 1394 port on the 6200. Thanks so much for your help! yong_sa |
Author: | yong_sa [ Fri Sep 14, 2007 12:24 pm ] |
Post subject: | |
I found an article on google regarding patching the 6200ch software: http://www.mythtv.org/pipermail/mythtv- ... 28907.html Could it be a problem with the vendor ID on my 6200 not being recognized by the 6200ch software? It is a brand new box. Unfortunately, I have no idea what the person is talking about regarding patching the 6200ch.c software, being a linux user, not a linux guru. Looking for your input - Thanks! |
Author: | RichP [ Mon Sep 17, 2007 10:55 am ] |
Post subject: | |
I have found that my Myth firewire connection fails if the cable box is on an encrypted channel (for example HBO, I'm running Comcast btw) I do NOT use the 6200ch in the mythtv-setup for firewire. Manually change the channel on your cable box to say channel 5 and try running the firewire_tester again. I think I am going to run a script that changes the channel to 005 and then runs firewire_tester before a recording. Sometimes I need to pull the power plug on the cable box for a few minutes to get everything fresh again. If you do this check if your node # has changes and be sure to change it in mythtv-setup. |
Author: | mooseboots [ Mon Sep 17, 2007 4:46 pm ] |
Post subject: | Power reset on cable box |
I have noticed increased reliability also if I kill the power on my Cable box periodically and reinit the firewire connection. If I stay on the same channel, I can run overnight watching one channel. After a few channel changes, the firewire connection eventually becomes unstable. I'm running with a 6412. |
Author: | RichP [ Tue Sep 18, 2007 5:50 am ] |
Post subject: | Re: Power reset on cable box |
I'm not sure if it would kill your connection while watching a show, but maybe you can schedule firewire_tester to run every hour or so. I'm thinking it will just glitch up 5 seconds of the video. mooseboots wrote: I have noticed increased reliability also if I kill the power on my Cable box periodically and reinit the firewire connection. If I stay on the same channel, I can run overnight watching one channel.
After a few channel changes, the firewire connection eventually becomes unstable. I'm running with a 6412. |
Author: | mooseboots [ Tue Sep 18, 2007 7:07 am ] |
Post subject: | firewire_tester |
I think someone else on this forum jigged up a plan to run firewire_tester on every channel change. However, running firewire tester periodically is not enough for my setup. I have to power cycle the cable box. I'm thinking about doing the following... 1) Call my cable company for an extra cable box. 2) Hook up the cable box directly to my MythTV; and have it be a dedicated signal source for the Myth box. 3) Write a quick script that power cycles the box, parses the output of plugreport for the node number, runs firewire_tester, etc. 4) Call such script before/during every channel change. 5) I'll watch "Live TV" through my current cable box - unconnected to Myth. |
Author: | RichP [ Wed Sep 19, 2007 5:10 am ] |
Post subject: | |
There was another program called gscanbus that I think allows you to do bus resets without powering down the cablebox. Gscanbus was gui only but it looks like someone wrote it for command line: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=200093 |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |