I'm sorry to post twice.... But one strange thing. After about 5 minutes
of sitting at the main mythtv screen, I see this come up on the mythbackend
logs...
2007-02-02 23:32:42.327 New DB connection, total: 4
2007-02-02 23:32:42.327 Connected to database 'mythconverg' at host:
localhost
2007-02-02 23:32:48.907 TVRec(1): Changing from WatchingLiveTV to None
2007-02-02 23:34:22.950 Expiring 8 MBytes for 11286 @ Fri Feb 2 23:31:29
2007 => Unknown
2007-02-02 23:34:22.950 Expiring 0 MBytes for 11282 @ Fri Feb 2 23:31:40
2007 => Unknown
2007-02-02 23:34:22.950 Expiring 6 MBytes for 11282 @ Fri Feb 2 23:31:43
2007 => Unknown
2007-02-02 23:34:22.951 Expiring 0 MBytes for 11281 @ Fri Feb 2 23:31:48
2007 => Unknown
2007-02-02 23:34:22.951 Expiring 27 MBytes for 11281 @ Fri Feb 2 23:31:50
2007 => Unknown
2007-02-02 23:34:22.951 Expiring 0 MBytes for 1005 @ Fri Feb 2 23:32:10 2007
=> Unknown
2007-02-02 23:35:44.047 Finished recording Unknown: channel 1005
2007-02-02 23:35:44.055 MythSocket(b518e0:-1): writeStringList: Error,
socket went unconnected.
2007-02-02 23:38:21.543 MainServer::HandleAnnounce Playback
When the "MythSocket(b518e0)....." line pops up, I'm able to go back in and
watch live tv again on that tuner and not get the firmware unresponsive
messages. Just thought that might be a clue.
Thanks,
Mike
On 2/2/07, Michael Wisniewski <[EMAIL PROTECTED]> wrote:
Hi!
I posted a message the other day with some problems with ivtv and
firmware unresponsive. Well, I wiped my system and decided to put Ubuntu
Feisty Fawn on. Yeah, I know it's beta, but I was having a hell of a time
trying to get Dapper and Edgy to work with my cards.
So now, I'm running 2.6.20-6-generic kernel and everything seems to be
recognized, but I still get the errors. As far as I know, the kernel is
built with ivtv, so I didn't have to install it. But why is it that I have
so many headaches trying to get this firmware unresponsive message to go
away!?! Argh. Oh well, there are many smart people out there and I'm sure
one of them will be nice enough to help. :)
Here is the dmesg
root@:/usr/src/homemade/mythtv# dmesg | grep -i ivtv
[ 27.015057] ivtv: ==================== START INIT IVTV
====================
[ 27.015062] ivtv: version 0.9.1 (tagged release) loading
[ 27.015064] ivtv: Linux version: 2.6.20-6-generic SMP mod_unload
[ 27.015066] ivtv: In case of problems please include the debug info
between
[ 27.015067] ivtv: the START INIT IVTV and END INIT IVTV lines, along
with
[ 27.015069] ivtv: any module options, when mailing the ivtv-users
mailinglist.
[ 27.145104] ivtv0: Autodetected Hauppauge card (cx23416 based)
[ 27.797100] ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
[ 28.000455] **WARNING** I2C adapter driver [ivtv i2c driver #0] forgot
to specify physical device; fix it!
[ 28.015449] tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[ 28.095421] ivtv0: Autodetected Hauppauge WinTV PVR-150
[ 28.095423] ivtv0: reopen i2c bus for IR-blaster support
[ 28.095486] **WARNING** I2C adapter driver [ivtv i2c driver #0] forgot
to specify physical device; fix it!
[ 28.186014] tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[ 28.331398] cx25840 3-0044: cx25841-23 found @ 0x88 (ivtv i2c driver
#0)
[ 31.224167] wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #0)
[ 31.280262] ivtv0: Encoder revision: 0x02050032
[ 31.280318 ] ivtv0: Registered device video1 for encoder MPEG
[ 31.280542] ivtv0: Registered device video32 for encoder YUV
[ 31.280795] ivtv0: Registered device vbi1 for encoder VBI
[ 31.280970] ivtv0: Registered device video24 for encoder PCM audio
[ 31.585700] ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
[ 31.585723] ivtv: ==================== END INIT IVTV
====================
And here is the errors in dmesg when it happens...
[ 4935.783563] ivtv0 warning: 1000 ms time out waiting for firmware
[ 4935.783569] ivtv0 warning: Failed api call 0x00000082 with result
0xfffffff0
[ 4935.783578] ivtv0 warning: ENC: Failed stopping capture -16
[ 4956.836605] ivtv0 warning: No Free Mailbox for cmd 0x000000c9 after 100
tries!
[ 4956.836612] ivtv0 warning: Mailbox[0] 0x000000dc flags 0x00000003
[ 4956.836618] ivtv0 warning: Mailbox[1] 0x000000cd flags 0x00000003
[ 4956.836624] ivtv0 warning: Mailbox[2] 0x000000d9 flags 0x00000003
[ 4956.836628] ivtv0 warning: Firmware UNRESPONSIVE when trying cmd
0x000000c9!!!
[ 4960.064157] ivtv0 warning: No Free Mailbox for cmd 0x000000dc after 100
tries!
[ 4960.064164] ivtv0 warning: Mailbox[0] 0x000000db flags 0x00000003
[ 4960.064170] ivtv0 warning: Mailbox[1] 0x000000dc flags 0x00000003
[ 4960.064175] ivtv0 warning: Mailbox[2] 0x000000dc flags 0x00000003
[ 4960.064179] ivtv0 warning: Firmware UNRESPONSIVE when trying cmd
0x000000dc!!!
[ 4968.091088] ivtv0 warning: 1000 ms time out waiting for firmware
[ 4968.091094] ivtv0 warning: Failed api call 0x000000b7 with result
0xfffffff0
As usual, if anybody has any ideas, I would be greatful because this is
driving me nuts.
Thanks!
Mike
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
