Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

OT: unreliable firmware load after cold boot

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


warpme at o2

Jul 17, 2012, 12:58 PM

Post #1 of 22 (3943 views)
Permalink
OT: unreliable firmware load after cold boot

Hi *

I just finish upgrade my system to 4xDVB-S2 + 1xDVB-T.
All runs over single cable (SCR) :-)

I'm looking for advice related to unreliable firmware loading.
My sys is ArchLinux, kernel3.3.8, Mystique SaTiX-S2 Sky Xpress Dual,
DVB-S2 a.k.a DvbSky S952.
Card is based on Montage Montage DS3103/TS2022 with cx23885 A/V decoder.
Both chips required firmware files.
My issue is that sometimes (especially after cold boot) one or both
tuners are non-functional due issue with loading firmware.
Warm reboot usually helps - but 1 for 10 times not.
I have impression this is kind of races or kernel bug.

Does anybody idea how to solve issue ?


Kernel log looks following:

[root [at] mytht var]# cat /var/log/kernel.log | grep
"DVB:\|firmware\|cx\|m88ds"
Jul 17 21:04:09 [ 5.457385] cx88/2: cx2388x MPEG-TS Driver Manager
version 0.0.9 loaded
Jul 17 21:04:09 [ 5.460816] cx88[0]: subsystem: b034:3034, board:
Prof 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
Jul 17 21:04:09 [ 5.460819] cx88[0]: TV tuner type -1, Radio tuner
type -1
Jul 17 21:04:09 [ 5.478014] cx88/0: cx2388x v4l2 driver version 0.0.9
loaded
Jul 17 21:04:09 [ 5.690521] cx23885 driver version 0.0.3 loaded
Jul 17 21:04:09 [ 5.691092] CORE cx23885[0]: subsystem: 4254:0952,
board: DVBSKY S952 [card=36,autodetected]
Jul 17 21:04:09 [ 5.996797] cx25840 3-0044: cx23885 A/V decoder found
@ 0x88 (cx23885[0])
Jul 17 21:04:09 [ 6.210084] input: cx88 IR (Prof 7301 DVB-S/S2) as
/devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0/input4
Jul 17 21:04:09 [ 6.210123] rc0: cx88 IR (Prof 7301 DVB-S/S2) as
/devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0
Jul 17 21:04:09 [ 6.213429] input: MCE IR Keyboard/Mouse (cx88xx) as
/devices/virtual/input/input5
Jul 17 21:04:09 [ 6.213500] rc rc0: lirc_dev: driver ir-lirc-codec
(cx88xx) registered at minor = 0
Jul 17 21:04:09 [ 6.213502] cx88[0]/2: cx2388x 8802 Driver Manager
Jul 17 21:04:09 [ 6.213531] cx88[0]/2: found at 0000:05:06.2, rev: 5,
irq: 20, latency: 32, mmio: 0xf5000000
Jul 17 21:04:09 [ 6.220418] cx88[1]: subsystem: 0070:9002, board:
Hauppauge Nova-T DVB-T [card=18,autodetected], frontend(s): 1
Jul 17 21:04:09 [ 6.220421] cx88[1]: TV tuner type 4, Radio tuner type -1
Jul 17 21:04:09 [ 6.384583] cx88[1]: hauppauge eeprom: model=90003
Jul 17 21:04:09 [ 6.443479] input: cx88 IR (Hauppauge Nova-T DVB-T as
/devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1/input6
Jul 17 21:04:09 [ 6.443525] rc1: cx88 IR (Hauppauge Nova-T DVB-T as
/devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1
Jul 17 21:04:09 [ 6.444724] input: MCE IR Keyboard/Mouse (cx88xx) as
/devices/virtual/input/input7
Jul 17 21:04:09 [ 6.444813] rc rc1: lirc_dev: driver ir-lirc-codec
(cx88xx) registered at minor = 1
Jul 17 21:04:09 [ 6.444817] cx88[1]/2: cx2388x 8802 Driver Manager
Jul 17 21:04:09 [ 6.444847] cx88[1]/2: found at 0000:05:07.2, rev: 5,
irq: 21, latency: 32, mmio: 0xfa000000
Jul 17 21:04:09 [ 6.448487] cx88[0]/0: found at 0000:05:06.0, rev: 5,
irq: 20, latency: 32, mmio: 0xf6000000
Jul 17 21:04:09 [ 6.448938] cx88[0]/0: registered device video0 [v4l2]
Jul 17 21:04:09 [ 6.449299] cx88[0]/0: registered device vbi0
Jul 17 21:04:09 [ 6.449418] cx88[1]/0: found at 0000:05:07.0, rev: 5,
irq: 21, latency: 32, mmio: 0xfb000000
Jul 17 21:04:09 [ 6.449586] cx88[1]/0: registered device video1 [v4l2]
Jul 17 21:04:09 [ 6.449735] cx88[1]/0: registered device vbi1
Jul 17 21:04:09 [ 6.454475] cx88[2]: subsystem: b034:3034, board:
Prof 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
Jul 17 21:04:09 [ 6.454478] cx88[2]: TV tuner type -1, Radio tuner
type -1
Jul 17 21:04:09 [ 6.697405] cx25840 3-0044: loaded
v4l-cx23885-avcore-01.fw firmware (16382 bytes)
Jul 17 21:04:09 [ 6.731510] cx23885_dvb_register() allocating 1
frontend(s)
Jul 17 21:04:09 [ 6.731515] cx23885[0]: cx23885 based dvb card
Jul 17 21:04:09 [ 6.833715] m88ds3103_load_firmware: Waiting for
firmware upload (dvb-fe-ds3103.fw)...
Jul 17 21:04:09 [ 6.846768] firmware 0000:02:00.0:
firmware_loading_store: unexpected value (0)
Jul 17 21:04:09 [ 6.847589] m88ds3103_load_firmware: Waiting for
firmware upload(2)...
Jul 17 21:04:09 [ 6.847591] m88ds3103_load_firmware: No firmware
uploaded (timeout or file not found?)
Jul 17 21:04:09 [ 6.848230] m88ds3103_initilaze: Unable initialize
firmware
Jul 17 21:04:09 [ 6.848874] DVB: registering new adapter (cx23885[0])
Jul 17 21:04:09 [ 6.848876] DVB: registering adapter 0 frontend 0
(Montage DS3103/TS2022)...
Jul 17 21:04:09 [ 6.849338] cx23885_dvb_register() allocating 1
frontend(s)
Jul 17 21:04:09 [ 6.849340] cx23885[0]: cx23885 based dvb card
Jul 17 21:04:09 [ 6.907675] m88ds3103_load_firmware: Waiting for
firmware upload (dvb-fe-ds3103.fw)...
Jul 17 21:04:09 [ 6.908077] firmware 0000:02:00.0:
firmware_loading_store: unexpected value (0)
Jul 17 21:04:09 [ 6.910099] m88ds3103_load_firmware: Waiting for
firmware upload(2)...
Jul 17 21:04:09 [ 6.910102] m88ds3103_load_firmware: No firmware
uploaded (timeout or file not found?)
Jul 17 21:04:09 [ 6.910822] m88ds3103_initilaze: Unable initialize
firmware
Jul 17 21:04:09 [ 6.911534] DVB: registering new adapter (cx23885[0])
Jul 17 21:04:09 [ 6.911537] DVB: registering adapter 1 frontend 0
(Montage DS3103/TS2022)...
Jul 17 21:04:09 [ 6.912099] cx23885_dev_checkrevision() Hardware
revision = 0xa5
Jul 17 21:04:09 [ 6.912105] cx23885[0]/0: found at 0000:02:00.0, rev:
4, irq: 16, latency: 0, mmio: 0xfd200000
Jul 17 21:04:09 [ 6.953136] input: cx88 IR (Prof 7301 DVB-S/S2) as
/devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2/input8
Jul 17 21:04:09 [ 6.953347] rc2: cx88 IR (Prof 7301 DVB-S/S2) as
/devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2
Jul 17 21:04:09 [ 6.953524] input: MCE IR Keyboard/Mouse (cx88xx) as
/devices/virtual/input/input9
Jul 17 21:04:09 [ 6.953864] rc rc2: lirc_dev: driver ir-lirc-codec
(cx88xx) registered at minor = 2
Jul 17 21:04:09 [ 6.953870] cx88[2]/0: found at 0000:05:08.0, rev: 5,
irq: 23, latency: 32, mmio: 0xf8000000
Jul 17 21:04:09 [ 6.954019] cx88[2]/0: registered device video2 [v4l2]
Jul 17 21:04:09 [ 6.954121] cx88[2]/0: registered device vbi2
Jul 17 21:04:09 [ 6.957672] cx88[2]/2: cx2388x 8802 Driver Manager
Jul 17 21:04:09 [ 6.957691] cx88[2]/2: found at 0000:05:08.2, rev: 5,
irq: 23, latency: 32, mmio: 0xf7000000
Jul 17 21:04:09 [ 6.958037] cx88/2: cx2388x dvb driver version 0.0.9
loaded
Jul 17 21:04:09 [ 6.958039] cx88/2: registering cx8802 driver, type:
dvb access: shared
Jul 17 21:04:09 [ 6.958041] cx88[0]/2: subsystem: b034:3034, board:
Prof 7301 DVB-S/S2 [card=83]
Jul 17 21:04:09 [ 6.958043] cx88[0]/2: cx2388x based DVB/ATSC card
Jul 17 21:04:09 [ 6.958045] cx8802_alloc_frontends() allocating 1
frontend(s)
Jul 17 21:04:09 [ 7.170175] input: cx23885 IR (DVBSKY S952) as
/devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3/input10
Jul 17 21:04:09 [ 7.173748] rc3: cx23885 IR (DVBSKY S952) as
/devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3
Jul 17 21:04:09 [ 7.173877] input: MCE IR Keyboard/Mouse (cx23885) as
/devices/virtual/input/input11
Jul 17 21:04:09 [ 7.174106] rc rc3: lirc_dev: driver ir-lirc-codec
(cx23885) registered at minor = 3
Jul 17 21:04:09 [ 7.386469] DVB: registering new adapter (cx88[0])
Jul 17 21:04:09 [ 7.386473] DVB: registering adapter 2 frontend 0
(STV090x Multistandard)...
Jul 17 21:04:09 [ 7.387604] cx88[1]/2: subsystem: 0070:9002, board:
Hauppauge Nova-T DVB-T [card=18]
Jul 17 21:04:09 [ 7.387608] cx88[1]/2: cx2388x based DVB/ATSC card
Jul 17 21:04:09 [ 7.387610] cx8802_alloc_frontends() allocating 1
frontend(s)
Jul 17 21:04:09 [ 7.762722] DVB: registering new adapter (cx88[1])
Jul 17 21:04:09 [ 7.762726] DVB: registering adapter 3 frontend 0
(Conexant CX22702 DVB-T)...
Jul 17 21:04:09 [ 7.766281] cx88[2]/2: subsystem: b034:3034, board:
Prof 7301 DVB-S/S2 [card=83]
Jul 17 21:04:09 [ 7.766285] cx88[2]/2: cx2388x based DVB/ATSC card
Jul 17 21:04:09 [ 7.766287] cx8802_alloc_frontends() allocating 1
frontend(s)
Jul 17 21:04:09 [ 7.893821] DVB: registering new adapter (cx88[2])
Jul 17 21:04:09 [ 7.893824] DVB: registering adapter 4 frontend 0
(STV090x Multistandard)...
Jul 17 21:05:45 [ 104.894844] DVB: registering new adapter (DVB-LOOPBACK)
Jul 17 21:05:45 [ 104.896424] DVB: registering new adapter (DVB-LOOPBACK)
Jul 17 21:05:45 [ 104.896832] DVB: registering new adapter (DVB-LOOPBACK)
Jul 17 21:05:45 [ 104.897199] DVB: registering new adapter (DVB-LOOPBACK)
Jul 17 21:14:07 [ 606.813334] cx8802_start_dma() Failed. Unsupported
value in .mpeg (0x00000001)
Attachments: warpme.vcf (83 B)


newbury at mandamus

Jul 17, 2012, 1:34 PM

Post #2 of 22 (3850 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 07/17/2012 03:58 PM, Warpme wrote:
> Hi *
>
> I just finish upgrade my system to 4xDVB-S2 + 1xDVB-T.
> All runs over single cable (SCR) :-)
>
> I'm looking for advice related to unreliable firmware loading.
> My sys is ArchLinux, kernel3.3.8, Mystique SaTiX-S2 Sky Xpress Dual,
> DVB-S2 a.k.a DvbSky S952.
> Card is based on Montage Montage DS3103/TS2022 with cx23885 A/V decoder.
> Both chips required firmware files.
> My issue is that sometimes (especially after cold boot) one or both
> tuners are non-functional due issue with loading firmware.
> Warm reboot usually helps - but 1 for 10 times not.
> I have impression this is kind of races or kernel bug.
>
> Does anybody idea how to solve issue ?
>
>
> Kernel log looks following:
>
> [root [at] mytht var]# cat /var/log/kernel.log | grep
> "DVB:\|firmware\|cx\|m88ds"
> Jul 17 21:04:09 [ 5.457385] cx88/2: cx2388x MPEG-TS Driver Manager
> version 0.0.9 loaded
> Jul 17 21:04:09 [ 5.460816] cx88[0]: subsystem: b034:3034, board: Prof
> 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
> Jul 17 21:04:09 [ 5.460819] cx88[0]: TV tuner type -1, Radio tuner type -1
> Jul 17 21:04:09 [ 5.478014] cx88/0: cx2388x v4l2 driver version 0.0.9
> loaded
> Jul 17 21:04:09 [ 5.690521] cx23885 driver version 0.0.3 loaded
> Jul 17 21:04:09 [ 5.691092] CORE cx23885[0]: subsystem: 4254:0952,
> board: DVBSKY S952 [card=36,autodetected]
> Jul 17 21:04:09 [ 5.996797] cx25840 3-0044: cx23885 A/V decoder found @
> 0x88 (cx23885[0])
> Jul 17 21:04:09 [ 6.210084] input: cx88 IR (Prof 7301 DVB-S/S2) as
> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0/input4
> Jul 17 21:04:09 [ 6.210123] rc0: cx88 IR (Prof 7301 DVB-S/S2) as
> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0
> Jul 17 21:04:09 [ 6.213429] input: MCE IR Keyboard/Mouse (cx88xx) as
> /devices/virtual/input/input5
> Jul 17 21:04:09 [ 6.213500] rc rc0: lirc_dev: driver ir-lirc-codec
> (cx88xx) registered at minor = 0
> Jul 17 21:04:09 [ 6.213502] cx88[0]/2: cx2388x 8802 Driver Manager
> Jul 17 21:04:09 [ 6.213531] cx88[0]/2: found at 0000:05:06.2, rev: 5,
> irq: 20, latency: 32, mmio: 0xf5000000
> Jul 17 21:04:09 [ 6.220418] cx88[1]: subsystem: 0070:9002, board:
> Hauppauge Nova-T DVB-T [card=18,autodetected], frontend(s): 1
> Jul 17 21:04:09 [ 6.220421] cx88[1]: TV tuner type 4, Radio tuner type -1
> Jul 17 21:04:09 [ 6.384583] cx88[1]: hauppauge eeprom: model=90003
> Jul 17 21:04:09 [ 6.443479] input: cx88 IR (Hauppauge Nova-T DVB-T as
> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1/input6
> Jul 17 21:04:09 [ 6.443525] rc1: cx88 IR (Hauppauge Nova-T DVB-T as
> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1
> Jul 17 21:04:09 [ 6.444724] input: MCE IR Keyboard/Mouse (cx88xx) as
> /devices/virtual/input/input7
> Jul 17 21:04:09 [ 6.444813] rc rc1: lirc_dev: driver ir-lirc-codec
> (cx88xx) registered at minor = 1
> Jul 17 21:04:09 [ 6.444817] cx88[1]/2: cx2388x 8802 Driver Manager
> Jul 17 21:04:09 [ 6.444847] cx88[1]/2: found at 0000:05:07.2, rev: 5,
> irq: 21, latency: 32, mmio: 0xfa000000
> Jul 17 21:04:09 [ 6.448487] cx88[0]/0: found at 0000:05:06.0, rev: 5,
> irq: 20, latency: 32, mmio: 0xf6000000
> Jul 17 21:04:09 [ 6.448938] cx88[0]/0: registered device video0 [v4l2]
> Jul 17 21:04:09 [ 6.449299] cx88[0]/0: registered device vbi0
> Jul 17 21:04:09 [ 6.449418] cx88[1]/0: found at 0000:05:07.0, rev: 5,
> irq: 21, latency: 32, mmio: 0xfb000000
> Jul 17 21:04:09 [ 6.449586] cx88[1]/0: registered device video1 [v4l2]
> Jul 17 21:04:09 [ 6.449735] cx88[1]/0: registered device vbi1
> Jul 17 21:04:09 [ 6.454475] cx88[2]: subsystem: b034:3034, board: Prof
> 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
> Jul 17 21:04:09 [ 6.454478] cx88[2]: TV tuner type -1, Radio tuner type -1
> Jul 17 21:04:09 [ 6.697405] cx25840 3-0044: loaded
> v4l-cx23885-avcore-01.fw firmware (16382 bytes)
> Jul 17 21:04:09 [ 6.731510] cx23885_dvb_register() allocating 1 frontend(s)
> Jul 17 21:04:09 [ 6.731515] cx23885[0]: cx23885 based dvb card
> Jul 17 21:04:09 [ 6.833715] m88ds3103_load_firmware: Waiting for
> firmware upload (dvb-fe-ds3103.fw)...
> Jul 17 21:04:09 [ 6.846768] firmware 0000:02:00.0:
> firmware_loading_store: unexpected value (0)
> Jul 17 21:04:09 [ 6.847589] m88ds3103_load_firmware: Waiting for
> firmware upload(2)...
> Jul 17 21:04:09 [ 6.847591] m88ds3103_load_firmware: No firmware
> uploaded (timeout or file not found?)
> Jul 17 21:04:09 [ 6.848230] m88ds3103_initilaze: Unable initialize firmware
> Jul 17 21:04:09 [ 6.848874] DVB: registering new adapter (cx23885[0])
> Jul 17 21:04:09 [ 6.848876] DVB: registering adapter 0 frontend 0
> (Montage DS3103/TS2022)...
> Jul 17 21:04:09 [ 6.849338] cx23885_dvb_register() allocating 1 frontend(s)
> Jul 17 21:04:09 [ 6.849340] cx23885[0]: cx23885 based dvb card
> Jul 17 21:04:09 [ 6.907675] m88ds3103_load_firmware: Waiting for
> firmware upload (dvb-fe-ds3103.fw)...
> Jul 17 21:04:09 [ 6.908077] firmware 0000:02:00.0:
> firmware_loading_store: unexpected value (0)
> Jul 17 21:04:09 [ 6.910099] m88ds3103_load_firmware: Waiting for
> firmware upload(2)...
> Jul 17 21:04:09 [ 6.910102] m88ds3103_load_firmware: No firmware
> uploaded (timeout or file not found?)
> Jul 17 21:04:09 [ 6.910822] m88ds3103_initilaze: Unable initialize firmware
> Jul 17 21:04:09 [ 6.911534] DVB: registering new adapter (cx23885[0])
> Jul 17 21:04:09 [ 6.911537] DVB: registering adapter 1 frontend 0
> (Montage DS3103/TS2022)...
> Jul 17 21:04:09 [ 6.912099] cx23885_dev_checkrevision() Hardware
> revision = 0xa5
> Jul 17 21:04:09 [ 6.912105] cx23885[0]/0: found at 0000:02:00.0, rev: 4,
> irq: 16, latency: 0, mmio: 0xfd200000
> Jul 17 21:04:09 [ 6.953136] input: cx88 IR (Prof 7301 DVB-S/S2) as
> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2/input8
> Jul 17 21:04:09 [ 6.953347] rc2: cx88 IR (Prof 7301 DVB-S/S2) as
> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2
> Jul 17 21:04:09 [ 6.953524] input: MCE IR Keyboard/Mouse (cx88xx) as
> /devices/virtual/input/input9
> Jul 17 21:04:09 [ 6.953864] rc rc2: lirc_dev: driver ir-lirc-codec
> (cx88xx) registered at minor = 2
> Jul 17 21:04:09 [ 6.953870] cx88[2]/0: found at 0000:05:08.0, rev: 5,
> irq: 23, latency: 32, mmio: 0xf8000000
> Jul 17 21:04:09 [ 6.954019] cx88[2]/0: registered device video2 [v4l2]
> Jul 17 21:04:09 [ 6.954121] cx88[2]/0: registered device vbi2
> Jul 17 21:04:09 [ 6.957672] cx88[2]/2: cx2388x 8802 Driver Manager
> Jul 17 21:04:09 [ 6.957691] cx88[2]/2: found at 0000:05:08.2, rev: 5,
> irq: 23, latency: 32, mmio: 0xf7000000
> Jul 17 21:04:09 [ 6.958037] cx88/2: cx2388x dvb driver version 0.0.9 loaded
> Jul 17 21:04:09 [ 6.958039] cx88/2: registering cx8802 driver, type: dvb
> access: shared
> Jul 17 21:04:09 [ 6.958041] cx88[0]/2: subsystem: b034:3034, board: Prof
> 7301 DVB-S/S2 [card=83]
> Jul 17 21:04:09 [ 6.958043] cx88[0]/2: cx2388x based DVB/ATSC card
> Jul 17 21:04:09 [ 6.958045] cx8802_alloc_frontends() allocating 1
> frontend(s)
> Jul 17 21:04:09 [ 7.170175] input: cx23885 IR (DVBSKY S952) as
> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3/input10
> Jul 17 21:04:09 [ 7.173748] rc3: cx23885 IR (DVBSKY S952) as
> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3
> Jul 17 21:04:09 [ 7.173877] input: MCE IR Keyboard/Mouse (cx23885) as
> /devices/virtual/input/input11
> Jul 17 21:04:09 [ 7.174106] rc rc3: lirc_dev: driver ir-lirc-codec
> (cx23885) registered at minor = 3
> Jul 17 21:04:09 [ 7.386469] DVB: registering new adapter (cx88[0])
> Jul 17 21:04:09 [ 7.386473] DVB: registering adapter 2 frontend 0
> (STV090x Multistandard)...
> Jul 17 21:04:09 [ 7.387604] cx88[1]/2: subsystem: 0070:9002, board:
> Hauppauge Nova-T DVB-T [card=18]
> Jul 17 21:04:09 [ 7.387608] cx88[1]/2: cx2388x based DVB/ATSC card
> Jul 17 21:04:09 [ 7.387610] cx8802_alloc_frontends() allocating 1
> frontend(s)
> Jul 17 21:04:09 [ 7.762722] DVB: registering new adapter (cx88[1])
> Jul 17 21:04:09 [ 7.762726] DVB: registering adapter 3 frontend 0
> (Conexant CX22702 DVB-T)...
> Jul 17 21:04:09 [ 7.766281] cx88[2]/2: subsystem: b034:3034, board: Prof
> 7301 DVB-S/S2 [card=83]
> Jul 17 21:04:09 [ 7.766285] cx88[2]/2: cx2388x based DVB/ATSC card
> Jul 17 21:04:09 [ 7.766287] cx8802_alloc_frontends() allocating 1
> frontend(s)
> Jul 17 21:04:09 [ 7.893821] DVB: registering new adapter (cx88[2])
> Jul 17 21:04:09 [ 7.893824] DVB: registering adapter 4 frontend 0
> (STV090x Multistandard)...
> Jul 17 21:05:45 [ 104.894844] DVB: registering new adapter (DVB-LOOPBACK)
> Jul 17 21:05:45 [ 104.896424] DVB: registering new adapter (DVB-LOOPBACK)
> Jul 17 21:05:45 [ 104.896832] DVB: registering new adapter (DVB-LOOPBACK)
> Jul 17 21:05:45 [ 104.897199] DVB: registering new adapter (DVB-LOOPBACK)
> Jul 17 21:14:07 [ 606.813334] cx8802_start_dma() Failed. Unsupported
> value in .mpeg (0x00000001)


I have had a similar problem with a Hauppauge 2250 card. The card
requires that the modules be loaded in a particular order, as the later
module relies upon the existence of the firmware of the earlier modules.
But the computer generally fails to use the correct order on boot.

I have added lines to rc.local to remove the modules and then reload in
the correct order. Because the modules 'above' rely on those below (when
correctly installed) you will get a error something like 'module in use:
cannot remove'.
It took a brute force ring-around to ensure that all three (in my case)
were removed: that is: I did modprobe -r #3, modprobe -r #2, modprobe -r
#1, modprobe -r #2, modprobe -r #3. modprobe -r #2. Then installed them
in proper order and get a 'registered' or 'initialized' report.

Geoff









_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mikep at randomtraveller

Jul 17, 2012, 1:49 PM

Post #3 of 22 (3857 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 17/07/12 21:34, R. G. Newbury wrote:
> On 07/17/2012 03:58 PM, Warpme wrote:
>> Hi *
>>
>> I just finish upgrade my system to 4xDVB-S2 + 1xDVB-T.
>> All runs over single cable (SCR) :-)
>>
>> I'm looking for advice related to unreliable firmware loading.
>> My sys is ArchLinux, kernel3.3.8, Mystique SaTiX-S2 Sky Xpress Dual,
>> DVB-S2 a.k.a DvbSky S952.
>> Card is based on Montage Montage DS3103/TS2022 with cx23885 A/V decoder.
>> Both chips required firmware files.
>> My issue is that sometimes (especially after cold boot) one or both
>> tuners are non-functional due issue with loading firmware.
>> Warm reboot usually helps - but 1 for 10 times not.
>> I have impression this is kind of races or kernel bug.
>>
>> Does anybody idea how to solve issue ?
>>
>>
>> Kernel log looks following:
>>
>> [root [at] mytht var]# cat /var/log/kernel.log | grep
>> "DVB:\|firmware\|cx\|m88ds"
>> Jul 17 21:04:09 [ 5.457385] cx88/2: cx2388x MPEG-TS Driver Manager
>> version 0.0.9 loaded
>> Jul 17 21:04:09 [ 5.460816] cx88[0]: subsystem: b034:3034, board: Prof
>> 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
>> Jul 17 21:04:09 [ 5.460819] cx88[0]: TV tuner type -1, Radio tuner type -1
>> Jul 17 21:04:09 [ 5.478014] cx88/0: cx2388x v4l2 driver version 0.0.9
>> loaded
>> Jul 17 21:04:09 [ 5.690521] cx23885 driver version 0.0.3 loaded
>> Jul 17 21:04:09 [ 5.691092] CORE cx23885[0]: subsystem: 4254:0952,
>> board: DVBSKY S952 [card=36,autodetected]
>> Jul 17 21:04:09 [ 5.996797] cx25840 3-0044: cx23885 A/V decoder found @
>> 0x88 (cx23885[0])
>> Jul 17 21:04:09 [ 6.210084] input: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0/input4
>> Jul 17 21:04:09 [ 6.210123] rc0: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0
>> Jul 17 21:04:09 [ 6.213429] input: MCE IR Keyboard/Mouse (cx88xx) as
>> /devices/virtual/input/input5
>> Jul 17 21:04:09 [ 6.213500] rc rc0: lirc_dev: driver ir-lirc-codec
>> (cx88xx) registered at minor = 0
>> Jul 17 21:04:09 [ 6.213502] cx88[0]/2: cx2388x 8802 Driver Manager
>> Jul 17 21:04:09 [ 6.213531] cx88[0]/2: found at 0000:05:06.2, rev: 5,
>> irq: 20, latency: 32, mmio: 0xf5000000
>> Jul 17 21:04:09 [ 6.220418] cx88[1]: subsystem: 0070:9002, board:
>> Hauppauge Nova-T DVB-T [card=18,autodetected], frontend(s): 1
>> Jul 17 21:04:09 [ 6.220421] cx88[1]: TV tuner type 4, Radio tuner type -1
>> Jul 17 21:04:09 [ 6.384583] cx88[1]: hauppauge eeprom: model=90003
>> Jul 17 21:04:09 [ 6.443479] input: cx88 IR (Hauppauge Nova-T DVB-T as
>> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1/input6
>> Jul 17 21:04:09 [ 6.443525] rc1: cx88 IR (Hauppauge Nova-T DVB-T as
>> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1
>> Jul 17 21:04:09 [ 6.444724] input: MCE IR Keyboard/Mouse (cx88xx) as
>> /devices/virtual/input/input7
>> Jul 17 21:04:09 [ 6.444813] rc rc1: lirc_dev: driver ir-lirc-codec
>> (cx88xx) registered at minor = 1
>> Jul 17 21:04:09 [ 6.444817] cx88[1]/2: cx2388x 8802 Driver Manager
>> Jul 17 21:04:09 [ 6.444847] cx88[1]/2: found at 0000:05:07.2, rev: 5,
>> irq: 21, latency: 32, mmio: 0xfa000000
>> Jul 17 21:04:09 [ 6.448487] cx88[0]/0: found at 0000:05:06.0, rev: 5,
>> irq: 20, latency: 32, mmio: 0xf6000000
>> Jul 17 21:04:09 [ 6.448938] cx88[0]/0: registered device video0 [v4l2]
>> Jul 17 21:04:09 [ 6.449299] cx88[0]/0: registered device vbi0
>> Jul 17 21:04:09 [ 6.449418] cx88[1]/0: found at 0000:05:07.0, rev: 5,
>> irq: 21, latency: 32, mmio: 0xfb000000
>> Jul 17 21:04:09 [ 6.449586] cx88[1]/0: registered device video1 [v4l2]
>> Jul 17 21:04:09 [ 6.449735] cx88[1]/0: registered device vbi1
>> Jul 17 21:04:09 [ 6.454475] cx88[2]: subsystem: b034:3034, board: Prof
>> 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
>> Jul 17 21:04:09 [ 6.454478] cx88[2]: TV tuner type -1, Radio tuner type -1
>> Jul 17 21:04:09 [ 6.697405] cx25840 3-0044: loaded
>> v4l-cx23885-avcore-01.fw firmware (16382 bytes)
>> Jul 17 21:04:09 [ 6.731510] cx23885_dvb_register() allocating 1 frontend(s)
>> Jul 17 21:04:09 [ 6.731515] cx23885[0]: cx23885 based dvb card
>> Jul 17 21:04:09 [ 6.833715] m88ds3103_load_firmware: Waiting for
>> firmware upload (dvb-fe-ds3103.fw)...
>> Jul 17 21:04:09 [ 6.846768] firmware 0000:02:00.0:
>> firmware_loading_store: unexpected value (0)
>> Jul 17 21:04:09 [ 6.847589] m88ds3103_load_firmware: Waiting for
>> firmware upload(2)...
>> Jul 17 21:04:09 [ 6.847591] m88ds3103_load_firmware: No firmware
>> uploaded (timeout or file not found?)
>> Jul 17 21:04:09 [ 6.848230] m88ds3103_initilaze: Unable initialize firmware
>> Jul 17 21:04:09 [ 6.848874] DVB: registering new adapter (cx23885[0])
>> Jul 17 21:04:09 [ 6.848876] DVB: registering adapter 0 frontend 0
>> (Montage DS3103/TS2022)...
>> Jul 17 21:04:09 [ 6.849338] cx23885_dvb_register() allocating 1 frontend(s)
>> Jul 17 21:04:09 [ 6.849340] cx23885[0]: cx23885 based dvb card
>> Jul 17 21:04:09 [ 6.907675] m88ds3103_load_firmware: Waiting for
>> firmware upload (dvb-fe-ds3103.fw)...
>> Jul 17 21:04:09 [ 6.908077] firmware 0000:02:00.0:
>> firmware_loading_store: unexpected value (0)
>> Jul 17 21:04:09 [ 6.910099] m88ds3103_load_firmware: Waiting for
>> firmware upload(2)...
>> Jul 17 21:04:09 [ 6.910102] m88ds3103_load_firmware: No firmware
>> uploaded (timeout or file not found?)
>> Jul 17 21:04:09 [ 6.910822] m88ds3103_initilaze: Unable initialize firmware
>> Jul 17 21:04:09 [ 6.911534] DVB: registering new adapter (cx23885[0])
>> Jul 17 21:04:09 [ 6.911537] DVB: registering adapter 1 frontend 0
>> (Montage DS3103/TS2022)...
>> Jul 17 21:04:09 [ 6.912099] cx23885_dev_checkrevision() Hardware
>> revision = 0xa5
>> Jul 17 21:04:09 [ 6.912105] cx23885[0]/0: found at 0000:02:00.0, rev: 4,
>> irq: 16, latency: 0, mmio: 0xfd200000
>> Jul 17 21:04:09 [ 6.953136] input: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2/input8
>> Jul 17 21:04:09 [ 6.953347] rc2: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2
>> Jul 17 21:04:09 [ 6.953524] input: MCE IR Keyboard/Mouse (cx88xx) as
>> /devices/virtual/input/input9
>> Jul 17 21:04:09 [ 6.953864] rc rc2: lirc_dev: driver ir-lirc-codec
>> (cx88xx) registered at minor = 2
>> Jul 17 21:04:09 [ 6.953870] cx88[2]/0: found at 0000:05:08.0, rev: 5,
>> irq: 23, latency: 32, mmio: 0xf8000000
>> Jul 17 21:04:09 [ 6.954019] cx88[2]/0: registered device video2 [v4l2]
>> Jul 17 21:04:09 [ 6.954121] cx88[2]/0: registered device vbi2
>> Jul 17 21:04:09 [ 6.957672] cx88[2]/2: cx2388x 8802 Driver Manager
>> Jul 17 21:04:09 [ 6.957691] cx88[2]/2: found at 0000:05:08.2, rev: 5,
>> irq: 23, latency: 32, mmio: 0xf7000000
>> Jul 17 21:04:09 [ 6.958037] cx88/2: cx2388x dvb driver version 0.0.9 loaded
>> Jul 17 21:04:09 [ 6.958039] cx88/2: registering cx8802 driver, type: dvb
>> access: shared
>> Jul 17 21:04:09 [ 6.958041] cx88[0]/2: subsystem: b034:3034, board: Prof
>> 7301 DVB-S/S2 [card=83]
>> Jul 17 21:04:09 [ 6.958043] cx88[0]/2: cx2388x based DVB/ATSC card
>> Jul 17 21:04:09 [ 6.958045] cx8802_alloc_frontends() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 7.170175] input: cx23885 IR (DVBSKY S952) as
>> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3/input10
>> Jul 17 21:04:09 [ 7.173748] rc3: cx23885 IR (DVBSKY S952) as
>> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3
>> Jul 17 21:04:09 [ 7.173877] input: MCE IR Keyboard/Mouse (cx23885) as
>> /devices/virtual/input/input11
>> Jul 17 21:04:09 [ 7.174106] rc rc3: lirc_dev: driver ir-lirc-codec
>> (cx23885) registered at minor = 3
>> Jul 17 21:04:09 [ 7.386469] DVB: registering new adapter (cx88[0])
>> Jul 17 21:04:09 [ 7.386473] DVB: registering adapter 2 frontend 0
>> (STV090x Multistandard)...
>> Jul 17 21:04:09 [ 7.387604] cx88[1]/2: subsystem: 0070:9002, board:
>> Hauppauge Nova-T DVB-T [card=18]
>> Jul 17 21:04:09 [ 7.387608] cx88[1]/2: cx2388x based DVB/ATSC card
>> Jul 17 21:04:09 [ 7.387610] cx8802_alloc_frontends() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 7.762722] DVB: registering new adapter (cx88[1])
>> Jul 17 21:04:09 [ 7.762726] DVB: registering adapter 3 frontend 0
>> (Conexant CX22702 DVB-T)...
>> Jul 17 21:04:09 [ 7.766281] cx88[2]/2: subsystem: b034:3034, board: Prof
>> 7301 DVB-S/S2 [card=83]
>> Jul 17 21:04:09 [ 7.766285] cx88[2]/2: cx2388x based DVB/ATSC card
>> Jul 17 21:04:09 [ 7.766287] cx8802_alloc_frontends() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 7.893821] DVB: registering new adapter (cx88[2])
>> Jul 17 21:04:09 [ 7.893824] DVB: registering adapter 4 frontend 0
>> (STV090x Multistandard)...
>> Jul 17 21:05:45 [ 104.894844] DVB: registering new adapter (DVB-LOOPBACK)
>> Jul 17 21:05:45 [ 104.896424] DVB: registering new adapter (DVB-LOOPBACK)
>> Jul 17 21:05:45 [ 104.896832] DVB: registering new adapter (DVB-LOOPBACK)
>> Jul 17 21:05:45 [ 104.897199] DVB: registering new adapter (DVB-LOOPBACK)
>> Jul 17 21:14:07 [ 606.813334] cx8802_start_dma() Failed. Unsupported
>> value in .mpeg (0x00000001)
>
>
> I have had a similar problem with a Hauppauge 2250 card. The card requires that
> the modules be loaded in a particular order, as the later module relies upon the
> existence of the firmware of the earlier modules. But the computer generally
> fails to use the correct order on boot.
>
> I have added lines to rc.local to remove the modules and then reload in the
> correct order. Because the modules 'above' rely on those below (when correctly
> installed) you will get a error something like 'module in use: cannot remove'.
> It took a brute force ring-around to ensure that all three (in my case) were
> removed: that is: I did modprobe -r #3, modprobe -r #2, modprobe -r #1, modprobe
> -r #2, modprobe -r #3. modprobe -r #2. Then installed them in proper order and
> get a 'registered' or 'initialized' report.
>
Is this the kind of situation that calls for udev rules?

--

Mike Perkins



_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gary.buhrmaster at gmail

Jul 17, 2012, 2:25 PM

Post #4 of 22 (3845 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On Tue, Jul 17, 2012 at 8:34 PM, R. G. Newbury <newbury [at] mandamus> wrote:
....
> I have had a similar problem with a Hauppauge 2250 card. The card requires
> that the modules be loaded in a particular order, as the later module relies
> upon the existence of the firmware of the earlier modules. But the computer
> generally fails to use the correct order on boot.

Depending on the details, it is sometimes possible to create
an /etc/modprobe.d/<something>.conf which uses install or
softdep to achieve ordering. That presumes, of course, your
drivers are otherwise well behaved (not all all).
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gary.buhrmaster at gmail

Jul 17, 2012, 2:30 PM

Post #5 of 22 (3840 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On Tue, Jul 17, 2012 at 8:49 PM, Mike Perkins
<mikep [at] randomtraveller> wrote:
...
> Is this the kind of situation that calls for udev rules?

Details vary, but udev rules are (usually) triggered when the device
is created. Depending on the driver, the device may not be created
until the firmware is loaded. In theory, sometimes, one might be
able to trigger a rule on an appropriate parent device creation.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


newbury at mandamus

Jul 17, 2012, 6:32 PM

Post #6 of 22 (3835 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 07/17/2012 04:49 PM, Mike Perkins wrote:
> On 17/07/12 21:34, R. G. Newbury wrote:
>> On 07/17/2012 03:58 PM, Warpme wrote:
>>> Hi *
>>>
>>> I just finish upgrade my system to 4xDVB-S2 + 1xDVB-T.
>>> All runs over single cable (SCR) :-)
>>>
>>> I'm looking for advice related to unreliable firmware loading.
>>> My sys is ArchLinux, kernel3.3.8, Mystique SaTiX-S2 Sky Xpress Dual,
>>> DVB-S2 a.k.a DvbSky S952.
>>> Card is based on Montage Montage DS3103/TS2022 with cx23885 A/V decoder.
>>> Both chips required firmware files.
>>> My issue is that sometimes (especially after cold boot) one or both
>>> tuners are non-functional due issue with loading firmware.
>>> Warm reboot usually helps - but 1 for 10 times not.
>>> I have impression this is kind of races or kernel bug.
>>>
>>> Does anybody idea how to solve issue ?
>>>
>>>
>>> Kernel log looks following:
>>>
>>> [root [at] mytht var]# cat /var/log/kernel.log | grep
>>> "DVB:\|firmware\|cx\|m88ds"
>>> Jul 17 21:04:09 [ 5.457385] cx88/2: cx2388x MPEG-TS Driver Manager
>>> version 0.0.9 loaded
>>> Jul 17 21:04:09 [ 5.460816] cx88[0]: subsystem: b034:3034, board: Prof
>>> 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
>>> Jul 17 21:04:09 [ 5.460819] cx88[0]: TV tuner type -1, Radio tuner
>>> type -1
>>> Jul 17 21:04:09 [ 5.478014] cx88/0: cx2388x v4l2 driver version 0.0.9
>>> loaded
>>> Jul 17 21:04:09 [ 5.690521] cx23885 driver version 0.0.3 loaded
>>> Jul 17 21:04:09 [ 5.691092] CORE cx23885[0]: subsystem: 4254:0952,
>>> board: DVBSKY S952 [card=36,autodetected]
>>> Jul 17 21:04:09 [ 5.996797] cx25840 3-0044: cx23885 A/V decoder found @
>>> 0x88 (cx23885[0])
>>> Jul 17 21:04:09 [ 6.210084] input: cx88 IR (Prof 7301 DVB-S/S2) as
>>> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0/input4
>>> Jul 17 21:04:09 [ 6.210123] rc0: cx88 IR (Prof 7301 DVB-S/S2) as
>>> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0
>>> Jul 17 21:04:09 [ 6.213429] input: MCE IR Keyboard/Mouse (cx88xx) as
>>> /devices/virtual/input/input5
>>> Jul 17 21:04:09 [ 6.213500] rc rc0: lirc_dev: driver ir-lirc-codec
>>> (cx88xx) registered at minor = 0
>>> Jul 17 21:04:09 [ 6.213502] cx88[0]/2: cx2388x 8802 Driver Manager
>>> Jul 17 21:04:09 [ 6.213531] cx88[0]/2: found at 0000:05:06.2, rev: 5,
>>> irq: 20, latency: 32, mmio: 0xf5000000
>>> Jul 17 21:04:09 [ 6.220418] cx88[1]: subsystem: 0070:9002, board:
>>> Hauppauge Nova-T DVB-T [card=18,autodetected], frontend(s): 1
>>> Jul 17 21:04:09 [ 6.220421] cx88[1]: TV tuner type 4, Radio tuner
>>> type -1
>>> Jul 17 21:04:09 [ 6.384583] cx88[1]: hauppauge eeprom: model=90003
>>> Jul 17 21:04:09 [ 6.443479] input: cx88 IR (Hauppauge Nova-T DVB-T as
>>> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1/input6
>>> Jul 17 21:04:09 [ 6.443525] rc1: cx88 IR (Hauppauge Nova-T DVB-T as
>>> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1
>>> Jul 17 21:04:09 [ 6.444724] input: MCE IR Keyboard/Mouse (cx88xx) as
>>> /devices/virtual/input/input7
>>> Jul 17 21:04:09 [ 6.444813] rc rc1: lirc_dev: driver ir-lirc-codec
>>> (cx88xx) registered at minor = 1
>>> Jul 17 21:04:09 [ 6.444817] cx88[1]/2: cx2388x 8802 Driver Manager
>>> Jul 17 21:04:09 [ 6.444847] cx88[1]/2: found at 0000:05:07.2, rev: 5,
>>> irq: 21, latency: 32, mmio: 0xfa000000
>>> Jul 17 21:04:09 [ 6.448487] cx88[0]/0: found at 0000:05:06.0, rev: 5,
>>> irq: 20, latency: 32, mmio: 0xf6000000
>>> Jul 17 21:04:09 [ 6.448938] cx88[0]/0: registered device video0 [v4l2]
>>> Jul 17 21:04:09 [ 6.449299] cx88[0]/0: registered device vbi0
>>> Jul 17 21:04:09 [ 6.449418] cx88[1]/0: found at 0000:05:07.0, rev: 5,
>>> irq: 21, latency: 32, mmio: 0xfb000000
>>> Jul 17 21:04:09 [ 6.449586] cx88[1]/0: registered device video1 [v4l2]
>>> Jul 17 21:04:09 [ 6.449735] cx88[1]/0: registered device vbi1
>>> Jul 17 21:04:09 [ 6.454475] cx88[2]: subsystem: b034:3034, board: Prof
>>> 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
>>> Jul 17 21:04:09 [ 6.454478] cx88[2]: TV tuner type -1, Radio tuner
>>> type -1
>>> Jul 17 21:04:09 [ 6.697405] cx25840 3-0044: loaded
>>> v4l-cx23885-avcore-01.fw firmware (16382 bytes)
>>> Jul 17 21:04:09 [ 6.731510] cx23885_dvb_register() allocating 1
>>> frontend(s)
>>> Jul 17 21:04:09 [ 6.731515] cx23885[0]: cx23885 based dvb card
>>> Jul 17 21:04:09 [ 6.833715] m88ds3103_load_firmware: Waiting for
>>> firmware upload (dvb-fe-ds3103.fw)...
>>> Jul 17 21:04:09 [ 6.846768] firmware 0000:02:00.0:
>>> firmware_loading_store: unexpected value (0)
>>> Jul 17 21:04:09 [ 6.847589] m88ds3103_load_firmware: Waiting for
>>> firmware upload(2)...
>>> Jul 17 21:04:09 [ 6.847591] m88ds3103_load_firmware: No firmware
>>> uploaded (timeout or file not found?)
>>> Jul 17 21:04:09 [ 6.848230] m88ds3103_initilaze: Unable initialize
>>> firmware
>>> Jul 17 21:04:09 [ 6.848874] DVB: registering new adapter (cx23885[0])
>>> Jul 17 21:04:09 [ 6.848876] DVB: registering adapter 0 frontend 0
>>> (Montage DS3103/TS2022)...
>>> Jul 17 21:04:09 [ 6.849338] cx23885_dvb_register() allocating 1
>>> frontend(s)
>>> Jul 17 21:04:09 [ 6.849340] cx23885[0]: cx23885 based dvb card
>>> Jul 17 21:04:09 [ 6.907675] m88ds3103_load_firmware: Waiting for
>>> firmware upload (dvb-fe-ds3103.fw)...
>>> Jul 17 21:04:09 [ 6.908077] firmware 0000:02:00.0:
>>> firmware_loading_store: unexpected value (0)
>>> Jul 17 21:04:09 [ 6.910099] m88ds3103_load_firmware: Waiting for
>>> firmware upload(2)...
>>> Jul 17 21:04:09 [ 6.910102] m88ds3103_load_firmware: No firmware
>>> uploaded (timeout or file not found?)
>>> Jul 17 21:04:09 [ 6.910822] m88ds3103_initilaze: Unable initialize
>>> firmware
>>> Jul 17 21:04:09 [ 6.911534] DVB: registering new adapter (cx23885[0])
>>> Jul 17 21:04:09 [ 6.911537] DVB: registering adapter 1 frontend 0
>>> (Montage DS3103/TS2022)...
>>> Jul 17 21:04:09 [ 6.912099] cx23885_dev_checkrevision() Hardware
>>> revision = 0xa5
>>> Jul 17 21:04:09 [ 6.912105] cx23885[0]/0: found at 0000:02:00.0, rev: 4,
>>> irq: 16, latency: 0, mmio: 0xfd200000
>>> Jul 17 21:04:09 [ 6.953136] input: cx88 IR (Prof 7301 DVB-S/S2) as
>>> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2/input8
>>> Jul 17 21:04:09 [ 6.953347] rc2: cx88 IR (Prof 7301 DVB-S/S2) as
>>> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2
>>> Jul 17 21:04:09 [ 6.953524] input: MCE IR Keyboard/Mouse (cx88xx) as
>>> /devices/virtual/input/input9
>>> Jul 17 21:04:09 [ 6.953864] rc rc2: lirc_dev: driver ir-lirc-codec
>>> (cx88xx) registered at minor = 2
>>> Jul 17 21:04:09 [ 6.953870] cx88[2]/0: found at 0000:05:08.0, rev: 5,
>>> irq: 23, latency: 32, mmio: 0xf8000000
>>> Jul 17 21:04:09 [ 6.954019] cx88[2]/0: registered device video2 [v4l2]
>>> Jul 17 21:04:09 [ 6.954121] cx88[2]/0: registered device vbi2
>>> Jul 17 21:04:09 [ 6.957672] cx88[2]/2: cx2388x 8802 Driver Manager
>>> Jul 17 21:04:09 [ 6.957691] cx88[2]/2: found at 0000:05:08.2, rev: 5,
>>> irq: 23, latency: 32, mmio: 0xf7000000
>>> Jul 17 21:04:09 [ 6.958037] cx88/2: cx2388x dvb driver version 0.0.9
>>> loaded
>>> Jul 17 21:04:09 [ 6.958039] cx88/2: registering cx8802 driver, type: dvb
>>> access: shared
>>> Jul 17 21:04:09 [ 6.958041] cx88[0]/2: subsystem: b034:3034, board: Prof
>>> 7301 DVB-S/S2 [card=83]
>>> Jul 17 21:04:09 [ 6.958043] cx88[0]/2: cx2388x based DVB/ATSC card
>>> Jul 17 21:04:09 [ 6.958045] cx8802_alloc_frontends() allocating 1
>>> frontend(s)
>>> Jul 17 21:04:09 [ 7.170175] input: cx23885 IR (DVBSKY S952) as
>>> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3/input10
>>> Jul 17 21:04:09 [ 7.173748] rc3: cx23885 IR (DVBSKY S952) as
>>> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3
>>> Jul 17 21:04:09 [ 7.173877] input: MCE IR Keyboard/Mouse (cx23885) as
>>> /devices/virtual/input/input11
>>> Jul 17 21:04:09 [ 7.174106] rc rc3: lirc_dev: driver ir-lirc-codec
>>> (cx23885) registered at minor = 3
>>> Jul 17 21:04:09 [ 7.386469] DVB: registering new adapter (cx88[0])
>>> Jul 17 21:04:09 [ 7.386473] DVB: registering adapter 2 frontend 0
>>> (STV090x Multistandard)...
>>> Jul 17 21:04:09 [ 7.387604] cx88[1]/2: subsystem: 0070:9002, board:
>>> Hauppauge Nova-T DVB-T [card=18]
>>> Jul 17 21:04:09 [ 7.387608] cx88[1]/2: cx2388x based DVB/ATSC card
>>> Jul 17 21:04:09 [ 7.387610] cx8802_alloc_frontends() allocating 1
>>> frontend(s)
>>> Jul 17 21:04:09 [ 7.762722] DVB: registering new adapter (cx88[1])
>>> Jul 17 21:04:09 [ 7.762726] DVB: registering adapter 3 frontend 0
>>> (Conexant CX22702 DVB-T)...
>>> Jul 17 21:04:09 [ 7.766281] cx88[2]/2: subsystem: b034:3034, board: Prof
>>> 7301 DVB-S/S2 [card=83]
>>> Jul 17 21:04:09 [ 7.766285] cx88[2]/2: cx2388x based DVB/ATSC card
>>> Jul 17 21:04:09 [ 7.766287] cx8802_alloc_frontends() allocating 1
>>> frontend(s)
>>> Jul 17 21:04:09 [ 7.893821] DVB: registering new adapter (cx88[2])
>>> Jul 17 21:04:09 [ 7.893824] DVB: registering adapter 4 frontend 0
>>> (STV090x Multistandard)...
>>> Jul 17 21:05:45 [ 104.894844] DVB: registering new adapter
>>> (DVB-LOOPBACK)
>>> Jul 17 21:05:45 [ 104.896424] DVB: registering new adapter
>>> (DVB-LOOPBACK)
>>> Jul 17 21:05:45 [ 104.896832] DVB: registering new adapter
>>> (DVB-LOOPBACK)
>>> Jul 17 21:05:45 [ 104.897199] DVB: registering new adapter
>>> (DVB-LOOPBACK)
>>> Jul 17 21:14:07 [ 606.813334] cx8802_start_dma() Failed. Unsupported
>>> value in .mpeg (0x00000001)
>>
>>
>> I have had a similar problem with a Hauppauge 2250 card. The card
>> requires that
>> the modules be loaded in a particular order, as the later module
>> relies upon the
>> existence of the firmware of the earlier modules. But the computer
>> generally
>> fails to use the correct order on boot.
>>
>> I have added lines to rc.local to remove the modules and then reload
>> in the
>> correct order. Because the modules 'above' rely on those below (when
>> correctly
>> installed) you will get a error something like 'module in use: cannot
>> remove'.
>> It took a brute force ring-around to ensure that all three (in my
>> case) were
>> removed: that is: I did modprobe -r #3, modprobe -r #2, modprobe -r
>> #1, modprobe
>> -r #2, modprobe -r #3. modprobe -r #2. Then installed them in proper
>> order and
>> get a 'registered' or 'initialized' report.
>>
> Is this the kind of situation that calls for udev rules?


Yes, but I was unable to find anything which dealt with the situation.

The three modules for the Hauppauge 2250 are (in order of required
install) tda18271, s5h1411 and finally saa7164.

I can provide a chunk of dmesg if anyone knows how to create a udev rule
which needs to go into the wiki. If we can collectively figure out the
right parts and correct order together with the right rules, maybe
Richard or Axel can package an install rpm for this unit.

Geoff






--
R. Geoffrey Newbury
Barrister and Solicitor
Suite 106, 150 Lakeshore Road West
Mississauga, Ontario, L5H 3R2

o905-271-9600 f905-271-1638
newbury [at] mandamus


_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


newbury at mandamus

Jul 17, 2012, 6:35 PM

Post #7 of 22 (3833 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 07/17/2012 05:25 PM, Gary Buhrmaster wrote:
> On Tue, Jul 17, 2012 at 8:34 PM, R. G. Newbury <newbury [at] mandamus> wrote:
> ....
>> I have had a similar problem with a Hauppauge 2250 card. The card requires
>> that the modules be loaded in a particular order, as the later module relies
>> upon the existence of the firmware of the earlier modules. But the computer
>> generally fails to use the correct order on boot.
>
> Depending on the details, it is sometimes possible to create
> an /etc/modprobe.d/<something>.conf which uses install or
> softdep to achieve ordering. That presumes, of course, your
> drivers are otherwise well behaved (not all all).

Once I got the order correct, which took a little combinatorial
experimentatoin, the modules are reasonably well behaved.
But getting it right requires removing them first as detailed in the
post. I don't know exactly *what* you can do in a conf file. My
impression is that it is very limited.

Geoff


_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


phipps-hutton at sky

Jul 17, 2012, 11:41 PM

Post #8 of 22 (3829 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

Quoting Mike Perkins <mikep [at] randomtraveller>:

> On 17/07/12 21:34, R. G. Newbury wrote:
>> It took a brute force ring-around to ensure that all three (in my case) were
>> removed: that is: I did modprobe -r #3, modprobe -r #2, modprobe -r
>> #1, modprobe
>> -r #2, modprobe -r #3. modprobe -r #2. Then installed them in
>> proper order and
>> get a 'registered' or 'initialized' report.
>>
> Is this the kind of situation that calls for udev rules?

No, the fix should be in the dependencies compiled into the modules so
that modprobe #3 just works.

Cheers,
Tim.


_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv-users at lists

Jul 18, 2012, 1:03 AM

Post #9 of 22 (3831 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

Gary Buhrmaster wrote:
> Depending on the details, it is sometimes possible to create
> an /etc/modprobe.d/<something>.conf which uses install or
> softdep to achieve ordering. That presumes, of course, your
> drivers are otherwise well behaved (not all all).

For me it works by adding "adapter_nr=..." in /etc/modprobe/options.conf
as described in the Wiki

options dvb_usb_dib0700 adapter_nr=0,1
options dvb_usb_af9015 adapter_nr=2,3

> http://www.mythtv.org/wiki/Device_Filenames_and_udev#Alternatives_to_udev_for_naming_for_DVB_cards_.28The_adapter_nr_module_option.29

To list the available option use "modinfo <module>".

HTH
Thomas

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


newbury at mandamus

Jul 18, 2012, 10:58 AM

Post #10 of 22 (3821 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 07/18/2012 02:41 AM, phipps-hutton [at] sky wrote:
>
> Quoting Mike Perkins <mikep [at] randomtraveller>:
>
>> On 17/07/12 21:34, R. G. Newbury wrote:
>>> It took a brute force ring-around to ensure that all three (in my
>>> case) were
>>> removed: that is: I did modprobe -r #3, modprobe -r #2, modprobe -r
>>> #1, modprobe
>>> -r #2, modprobe -r #3. modprobe -r #2. Then installed them in proper
>>> order and
>>> get a 'registered' or 'initialized' report.
>>>
>> Is this the kind of situation that calls for udev rules?
>
> No, the fix should be in the dependencies compiled into the modules so
> that modprobe #3 just works.

Ahh, dreaming in technicolor are we??

Would be nice but!

A quick modinfo shows that none of the three lists any of the others as
a dependency, but my experimentation showed that they are all needed and
in a set order.
They are described as a 'driver' 'demodulator driver' and 'tuner driver'
each matching the chipset on the card.

But I had completely forgotten about modinfo. I will have to turn on
some debugging. Mythtv's setup does not like this card and does not set
it up properly or does not 'see' it properly.
It tunes with azap and vlc handles it nicely, but myth does not....

Geoff



_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


newbury at mandamus

Jul 18, 2012, 11:03 AM

Post #11 of 22 (3822 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 07/18/2012 04:03 AM, Thomas Boehm wrote:
> Gary Buhrmaster wrote:
>> Depending on the details, it is sometimes possible to create
>> an /etc/modprobe.d/<something>.conf which uses install or
>> softdep to achieve ordering. That presumes, of course, your
>> drivers are otherwise well behaved (not all all).
>
> For me it works by adding "adapter_nr=..." in /etc/modprobe/options.conf
> as described in the Wiki
>
> options dvb_usb_dib0700 adapter_nr=0,1
> options dvb_usb_af9015 adapter_nr=2,3
>
>> http://www.mythtv.org/wiki/Device_Filenames_and_udev#Alternatives_to_udev_for_naming_for_DVB_cards_.28The_adapter_nr_module_option.29
>
> To list the available option use "modinfo<module>".


I was just reminded about modinfo. And the card has a parameter which
can be used: adapter_nr:DVB adapter numbers (array of short)


But the problem is with the required sub-modules which are not (visibly)
listed as dependencies.

Geoff

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


dheitmueller at kernellabs

Jul 18, 2012, 11:08 AM

Post #12 of 22 (3818 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On Wed, Jul 18, 2012 at 2:03 PM, R. G. Newbury <newbury [at] mandamus> wrote:
> But the problem is with the required sub-modules which are not (visibly)
> listed as dependencies.

This is actually the expected behavior. Unlike many drivers, tuner
and demodulator drivers which are subdevices of a bridge don't use the
standard module dependency mechanism. Otherwise it would result in
*every* tuner and demodulator driver for a given bridge to be
required, which for many PCI or USB bridge can be in the dozens.

For example, if you have an em28xx based product, there can be a
couple of dozen bridges or demodulators that can be invoked because
there are so many different em28xx based products that have different
tuners/demods. The dependencies are resolved automatically at runtime
by the tuner-core and dvb framework once the actual product model is
determined. This avoids having to load modules for every single tuner
and demodulator that could *possibly* be used by that driver.

Devin

--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


newbury at mandamus

Jul 18, 2012, 12:01 PM

Post #13 of 22 (3816 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 07/18/2012 02:08 PM, Devin Heitmueller wrote:
> On Wed, Jul 18, 2012 at 2:03 PM, R. G. Newbury<newbury [at] mandamus> wrote:
>> But the problem is with the required sub-modules which are not (visibly)
>> listed as dependencies.
>
> This is actually the expected behavior. Unlike many drivers, tuner
> and demodulator drivers which are subdevices of a bridge don't use the
> standard module dependency mechanism. Otherwise it would result in
> *every* tuner and demodulator driver for a given bridge to be
> required, which for many PCI or USB bridge can be in the dozens.
>
> For example, if you have an em28xx based product, there can be a
> couple of dozen bridges or demodulators that can be invoked because
> there are so many different em28xx based products that have different
> tuners/demods. The dependencies are resolved automatically at runtime
> by the tuner-core and dvb framework once the actual product model is
> determined. This avoids having to load modules for every single tuner
> and demodulator that could *possibly* be used by that driver.

Which of course makes perfect and reasonable sense. The problem is how
to work around a situation where the invocation is not happening
correctly. I presume that there are a series of pokes and peeks, but
they are internal to the module code and not exposed. We really need to
latch onto something exposed, and unique.

And it may not exist.

And as you say, there are lots of hardware items which use different
chipsets internally, while declaring that they are twins to a different
model. Or they just report themselves wrongly anyway!

Geoff

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


dheitmueller at kernellabs

Jul 18, 2012, 12:37 PM

Post #14 of 22 (3811 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On Wed, Jul 18, 2012 at 3:01 PM, R. G. Newbury <newbury [at] mandamus> wrote:
> Which of course makes perfect and reasonable sense. The problem is how to
> work around a situation where the invocation is not happening correctly. I
> presume that there are a series of pokes and peeks, but they are internal to
> the module code and not exposed. We really need to latch onto something
> exposed, and unique.
>
> And it may not exist.
>
> And as you say, there are lots of hardware items which use different
> chipsets internally, while declaring that they are twins to a different
> model. Or they just report themselves wrongly anyway!

Let me ask around and see if I can get my hands on a 2250. The
problem I ran into the last time somebody suggested that module
loading order fixed it was actually a race condition related to udev
calling v4l-id while the digital side of the board was still
initializing.

Can you send me the actual symptoms you encounter (including the dmesg
output showing any error messages during initialization)?

Devin

--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


warpme at o2

Jul 18, 2012, 12:46 PM

Post #15 of 22 (3809 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 7/18/12 7:58 PM, R. G. Newbury wrote:
> On 07/18/2012 02:41 AM, phipps-hutton [at] sky wrote:
>>
>> Quoting Mike Perkins <mikep [at] randomtraveller>:
>>
>>> On 17/07/12 21:34, R. G. Newbury wrote:
>>>> It took a brute force ring-around to ensure that all three (in my
>>>> case) were
>>>> removed: that is: I did modprobe -r #3, modprobe -r #2, modprobe -r
>>>> #1, modprobe
>>>> -r #2, modprobe -r #3. modprobe -r #2. Then installed them in proper
>>>> order and
>>>> get a 'registered' or 'initialized' report.
>>>>
>>> Is this the kind of situation that calls for udev rules?
>>
>> No, the fix should be in the dependencies compiled into the modules so
>> that modprobe #3 just works.
>
> Ahh, dreaming in technicolor are we??
>
> Would be nice but!
>
> A quick modinfo shows that none of the three lists any of the others
> as a dependency, but my experimentation showed that they are all
> needed and in a set order.
> They are described as a 'driver' 'demodulator driver' and 'tuner
> driver' each matching the chipset on the card.
>
> But I had completely forgotten about modinfo. I will have to turn on
> some debugging. Mythtv's setup does not like this card and does not
> set it up properly or does not 'see' it properly.
> It tunes with azap and vlc handles it nicely, but myth does not....
>
> Geoff
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
Indeed, mythtv-setup is another problem :-(
No mater what I was trying, tuners on this card wasn't recognized.
Infact other tuners also wasn't recognized. Problem seems to be somehow
dependent on number of tuners in system, as in my cloned test system
with only 2 tuners I was able to configure them).
After hours of tries I was forced to do all capturecard, cardinput,
diseqc_tree (including SCR trees) & inputgroups setup manually at sql
level.
Positive is that I have full view how my DVB subsystem is configured
(monotonic tuners numbers, clear diseqc tree, etc) - but, being under
time pressure (production system), I was little frustrated that
down-time took 3h instead of 15min :-(
Attachments: warpme.vcf (83 B)


warpme at o2

Jul 18, 2012, 12:54 PM

Post #16 of 22 (3816 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 7/17/12 10:34 PM, R. G. Newbury wrote:
> On 07/17/2012 03:58 PM, Warpme wrote:
>> Hi *
>>
>> I just finish upgrade my system to 4xDVB-S2 + 1xDVB-T.
>> All runs over single cable (SCR) :-)
>>
>> I'm looking for advice related to unreliable firmware loading.
>> My sys is ArchLinux, kernel3.3.8, Mystique SaTiX-S2 Sky Xpress Dual,
>> DVB-S2 a.k.a DvbSky S952.
>> Card is based on Montage Montage DS3103/TS2022 with cx23885 A/V decoder.
>> Both chips required firmware files.
>> My issue is that sometimes (especially after cold boot) one or both
>> tuners are non-functional due issue with loading firmware.
>> Warm reboot usually helps - but 1 for 10 times not.
>> I have impression this is kind of races or kernel bug.
>>
>> Does anybody idea how to solve issue ?
>>
>>
>> Kernel log looks following:
>>
>> [root [at] mytht var]# cat /var/log/kernel.log | grep
>> "DVB:\|firmware\|cx\|m88ds"
>> Jul 17 21:04:09 [ 5.457385] cx88/2: cx2388x MPEG-TS Driver Manager
>> version 0.0.9 loaded
>> Jul 17 21:04:09 [ 5.460816] cx88[0]: subsystem: b034:3034, board: Prof
>> 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
>> Jul 17 21:04:09 [ 5.460819] cx88[0]: TV tuner type -1, Radio tuner
>> type -1
>> Jul 17 21:04:09 [ 5.478014] cx88/0: cx2388x v4l2 driver version 0.0.9
>> loaded
>> Jul 17 21:04:09 [ 5.690521] cx23885 driver version 0.0.3 loaded
>> Jul 17 21:04:09 [ 5.691092] CORE cx23885[0]: subsystem: 4254:0952,
>> board: DVBSKY S952 [card=36,autodetected]
>> Jul 17 21:04:09 [ 5.996797] cx25840 3-0044: cx23885 A/V decoder found @
>> 0x88 (cx23885[0])
>> Jul 17 21:04:09 [ 6.210084] input: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0/input4
>> Jul 17 21:04:09 [ 6.210123] rc0: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0
>> Jul 17 21:04:09 [ 6.213429] input: MCE IR Keyboard/Mouse (cx88xx) as
>> /devices/virtual/input/input5
>> Jul 17 21:04:09 [ 6.213500] rc rc0: lirc_dev: driver ir-lirc-codec
>> (cx88xx) registered at minor = 0
>> Jul 17 21:04:09 [ 6.213502] cx88[0]/2: cx2388x 8802 Driver Manager
>> Jul 17 21:04:09 [ 6.213531] cx88[0]/2: found at 0000:05:06.2, rev: 5,
>> irq: 20, latency: 32, mmio: 0xf5000000
>> Jul 17 21:04:09 [ 6.220418] cx88[1]: subsystem: 0070:9002, board:
>> Hauppauge Nova-T DVB-T [card=18,autodetected], frontend(s): 1
>> Jul 17 21:04:09 [ 6.220421] cx88[1]: TV tuner type 4, Radio tuner
>> type -1
>> Jul 17 21:04:09 [ 6.384583] cx88[1]: hauppauge eeprom: model=90003
>> Jul 17 21:04:09 [ 6.443479] input: cx88 IR (Hauppauge Nova-T DVB-T as
>> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1/input6
>> Jul 17 21:04:09 [ 6.443525] rc1: cx88 IR (Hauppauge Nova-T DVB-T as
>> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1
>> Jul 17 21:04:09 [ 6.444724] input: MCE IR Keyboard/Mouse (cx88xx) as
>> /devices/virtual/input/input7
>> Jul 17 21:04:09 [ 6.444813] rc rc1: lirc_dev: driver ir-lirc-codec
>> (cx88xx) registered at minor = 1
>> Jul 17 21:04:09 [ 6.444817] cx88[1]/2: cx2388x 8802 Driver Manager
>> Jul 17 21:04:09 [ 6.444847] cx88[1]/2: found at 0000:05:07.2, rev: 5,
>> irq: 21, latency: 32, mmio: 0xfa000000
>> Jul 17 21:04:09 [ 6.448487] cx88[0]/0: found at 0000:05:06.0, rev: 5,
>> irq: 20, latency: 32, mmio: 0xf6000000
>> Jul 17 21:04:09 [ 6.448938] cx88[0]/0: registered device video0 [v4l2]
>> Jul 17 21:04:09 [ 6.449299] cx88[0]/0: registered device vbi0
>> Jul 17 21:04:09 [ 6.449418] cx88[1]/0: found at 0000:05:07.0, rev: 5,
>> irq: 21, latency: 32, mmio: 0xfb000000
>> Jul 17 21:04:09 [ 6.449586] cx88[1]/0: registered device video1 [v4l2]
>> Jul 17 21:04:09 [ 6.449735] cx88[1]/0: registered device vbi1
>> Jul 17 21:04:09 [ 6.454475] cx88[2]: subsystem: b034:3034, board: Prof
>> 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
>> Jul 17 21:04:09 [ 6.454478] cx88[2]: TV tuner type -1, Radio tuner
>> type -1
>> Jul 17 21:04:09 [ 6.697405] cx25840 3-0044: loaded
>> v4l-cx23885-avcore-01.fw firmware (16382 bytes)
>> Jul 17 21:04:09 [ 6.731510] cx23885_dvb_register() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 6.731515] cx23885[0]: cx23885 based dvb card
>> Jul 17 21:04:09 [ 6.833715] m88ds3103_load_firmware: Waiting for
>> firmware upload (dvb-fe-ds3103.fw)...
>> Jul 17 21:04:09 [ 6.846768] firmware 0000:02:00.0:
>> firmware_loading_store: unexpected value (0)
>> Jul 17 21:04:09 [ 6.847589] m88ds3103_load_firmware: Waiting for
>> firmware upload(2)...
>> Jul 17 21:04:09 [ 6.847591] m88ds3103_load_firmware: No firmware
>> uploaded (timeout or file not found?)
>> Jul 17 21:04:09 [ 6.848230] m88ds3103_initilaze: Unable initialize
>> firmware
>> Jul 17 21:04:09 [ 6.848874] DVB: registering new adapter (cx23885[0])
>> Jul 17 21:04:09 [ 6.848876] DVB: registering adapter 0 frontend 0
>> (Montage DS3103/TS2022)...
>> Jul 17 21:04:09 [ 6.849338] cx23885_dvb_register() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 6.849340] cx23885[0]: cx23885 based dvb card
>> Jul 17 21:04:09 [ 6.907675] m88ds3103_load_firmware: Waiting for
>> firmware upload (dvb-fe-ds3103.fw)...
>> Jul 17 21:04:09 [ 6.908077] firmware 0000:02:00.0:
>> firmware_loading_store: unexpected value (0)
>> Jul 17 21:04:09 [ 6.910099] m88ds3103_load_firmware: Waiting for
>> firmware upload(2)...
>> Jul 17 21:04:09 [ 6.910102] m88ds3103_load_firmware: No firmware
>> uploaded (timeout or file not found?)
>> Jul 17 21:04:09 [ 6.910822] m88ds3103_initilaze: Unable initialize
>> firmware
>> Jul 17 21:04:09 [ 6.911534] DVB: registering new adapter (cx23885[0])
>> Jul 17 21:04:09 [ 6.911537] DVB: registering adapter 1 frontend 0
>> (Montage DS3103/TS2022)...
>> Jul 17 21:04:09 [ 6.912099] cx23885_dev_checkrevision() Hardware
>> revision = 0xa5
>> Jul 17 21:04:09 [ 6.912105] cx23885[0]/0: found at 0000:02:00.0, rev: 4,
>> irq: 16, latency: 0, mmio: 0xfd200000
>> Jul 17 21:04:09 [ 6.953136] input: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2/input8
>> Jul 17 21:04:09 [ 6.953347] rc2: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2
>> Jul 17 21:04:09 [ 6.953524] input: MCE IR Keyboard/Mouse (cx88xx) as
>> /devices/virtual/input/input9
>> Jul 17 21:04:09 [ 6.953864] rc rc2: lirc_dev: driver ir-lirc-codec
>> (cx88xx) registered at minor = 2
>> Jul 17 21:04:09 [ 6.953870] cx88[2]/0: found at 0000:05:08.0, rev: 5,
>> irq: 23, latency: 32, mmio: 0xf8000000
>> Jul 17 21:04:09 [ 6.954019] cx88[2]/0: registered device video2 [v4l2]
>> Jul 17 21:04:09 [ 6.954121] cx88[2]/0: registered device vbi2
>> Jul 17 21:04:09 [ 6.957672] cx88[2]/2: cx2388x 8802 Driver Manager
>> Jul 17 21:04:09 [ 6.957691] cx88[2]/2: found at 0000:05:08.2, rev: 5,
>> irq: 23, latency: 32, mmio: 0xf7000000
>> Jul 17 21:04:09 [ 6.958037] cx88/2: cx2388x dvb driver version 0.0.9
>> loaded
>> Jul 17 21:04:09 [ 6.958039] cx88/2: registering cx8802 driver, type: dvb
>> access: shared
>> Jul 17 21:04:09 [ 6.958041] cx88[0]/2: subsystem: b034:3034, board: Prof
>> 7301 DVB-S/S2 [card=83]
>> Jul 17 21:04:09 [ 6.958043] cx88[0]/2: cx2388x based DVB/ATSC card
>> Jul 17 21:04:09 [ 6.958045] cx8802_alloc_frontends() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 7.170175] input: cx23885 IR (DVBSKY S952) as
>> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3/input10
>> Jul 17 21:04:09 [ 7.173748] rc3: cx23885 IR (DVBSKY S952) as
>> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3
>> Jul 17 21:04:09 [ 7.173877] input: MCE IR Keyboard/Mouse (cx23885) as
>> /devices/virtual/input/input11
>> Jul 17 21:04:09 [ 7.174106] rc rc3: lirc_dev: driver ir-lirc-codec
>> (cx23885) registered at minor = 3
>> Jul 17 21:04:09 [ 7.386469] DVB: registering new adapter (cx88[0])
>> Jul 17 21:04:09 [ 7.386473] DVB: registering adapter 2 frontend 0
>> (STV090x Multistandard)...
>> Jul 17 21:04:09 [ 7.387604] cx88[1]/2: subsystem: 0070:9002, board:
>> Hauppauge Nova-T DVB-T [card=18]
>> Jul 17 21:04:09 [ 7.387608] cx88[1]/2: cx2388x based DVB/ATSC card
>> Jul 17 21:04:09 [ 7.387610] cx8802_alloc_frontends() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 7.762722] DVB: registering new adapter (cx88[1])
>> Jul 17 21:04:09 [ 7.762726] DVB: registering adapter 3 frontend 0
>> (Conexant CX22702 DVB-T)...
>> Jul 17 21:04:09 [ 7.766281] cx88[2]/2: subsystem: b034:3034, board: Prof
>> 7301 DVB-S/S2 [card=83]
>> Jul 17 21:04:09 [ 7.766285] cx88[2]/2: cx2388x based DVB/ATSC card
>> Jul 17 21:04:09 [ 7.766287] cx8802_alloc_frontends() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 7.893821] DVB: registering new adapter (cx88[2])
>> Jul 17 21:04:09 [ 7.893824] DVB: registering adapter 4 frontend 0
>> (STV090x Multistandard)...
>> Jul 17 21:05:45 [ 104.894844] DVB: registering new adapter
>> (DVB-LOOPBACK)
>> Jul 17 21:05:45 [ 104.896424] DVB: registering new adapter
>> (DVB-LOOPBACK)
>> Jul 17 21:05:45 [ 104.896832] DVB: registering new adapter
>> (DVB-LOOPBACK)
>> Jul 17 21:05:45 [ 104.897199] DVB: registering new adapter
>> (DVB-LOOPBACK)
>> Jul 17 21:14:07 [ 606.813334] cx8802_start_dma() Failed. Unsupported
>> value in .mpeg (0x00000001)
>
>
> I have had a similar problem with a Hauppauge 2250 card. The card
> requires that the modules be loaded in a particular order, as the
> later module relies upon the existence of the firmware of the earlier
> modules. But the computer generally fails to use the correct order on
> boot.
>
> I have added lines to rc.local to remove the modules and then reload
> in the correct order. Because the modules 'above' rely on those below
> (when correctly installed) you will get a error something like 'module
> in use: cannot remove'.
> It took a brute force ring-around to ensure that all three (in my
> case) were removed: that is: I did modprobe -r #3, modprobe -r #2,
> modprobe -r #1, modprobe -r #2, modprobe -r #3. modprobe -r #2. Then
> installed them in proper order and get a 'registered' or 'initialized'
> report.
>
> Geoff
>
>
>
>
>
>
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
Oh well - this approach was my first try.
I was trying blacklist all relevant modules to have clear starting point
and next write small script allowing to load them "reliably".
Issue is that after blacklisting all modules for this card it still
loads. Probably there are some other modules - common with other cards -
which are triggering load of modules for this card. Now I potentially
have to cover not only this feral card but also modules for other - well
working - cards.
I decided stop this concept and listen what some more knowledgeable ppl
will say here...

-br
Attachments: warpme.vcf (83 B)


newbury at mandamus

Jul 18, 2012, 5:51 PM

Post #17 of 22 (3807 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 07/18/2012 03:37 PM, Devin Heitmueller wrote:
> On Wed, Jul 18, 2012 at 3:01 PM, R. G. Newbury<newbury [at] mandamus> wrote:
>> Which of course makes perfect and reasonable sense. The problem is how to
>> work around a situation where the invocation is not happening correctly. I
>> presume that there are a series of pokes and peeks, but they are internal to
>> the module code and not exposed. We really need to latch onto something
>> exposed, and unique.
>>
>> And it may not exist.
>>
>> And as you say, there are lots of hardware items which use different
>> chipsets internally, while declaring that they are twins to a different
>> model. Or they just report themselves wrongly anyway!
>
> Let me ask around and see if I can get my hands on a 2250. The
> problem I ran into the last time somebody suggested that module
> loading order fixed it was actually a race condition related to udev
> calling v4l-id while the digital side of the board was still
> initializing.
>
> Can you send me the actual symptoms you encounter (including the dmesg
> output showing any error messages during initialization)?
>
> Devin


But of course. Tomorrow, or even later tonight.


Geoff
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


newbury at mandamus

Jul 18, 2012, 5:54 PM

Post #18 of 22 (3810 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 07/18/2012 03:46 PM, Warpme wrote:
> On 7/18/12 7:58 PM, R. G. Newbury wrote:
>> On 07/18/2012 02:41 AM, phipps-hutton [at] sky wrote:
>>>
>>> Quoting Mike Perkins <mikep [at] randomtraveller>:
>>>
>>>> On 17/07/12 21:34, R. G. Newbury wrote:
>>>>> It took a brute force ring-around to ensure that all three (in my
>>>>> case) were
>>>>> removed: that is: I did modprobe -r #3, modprobe -r #2, modprobe -r
>>>>> #1, modprobe
>>>>> -r #2, modprobe -r #3. modprobe -r #2. Then installed them in proper
>>>>> order and
>>>>> get a 'registered' or 'initialized' report.
>>>>>
>>>> Is this the kind of situation that calls for udev rules?
>>>
>>> No, the fix should be in the dependencies compiled into the modules so
>>> that modprobe #3 just works.
>>
>> Ahh, dreaming in technicolor are we??
>>
>> Would be nice but!
>>
>> A quick modinfo shows that none of the three lists any of the others
>> as a dependency, but my experimentation showed that they are all
>> needed and in a set order.
>> They are described as a 'driver' 'demodulator driver' and 'tuner
>> driver' each matching the chipset on the card.
>>
>> But I had completely forgotten about modinfo. I will have to turn on
>> some debugging. Mythtv's setup does not like this card and does not
>> set it up properly or does not 'see' it properly.
>> It tunes with azap and vlc handles it nicely, but myth does not....
>>
>> Geoff
>>
>>
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users [at] mythtv
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>
> Indeed, mythtv-setup is another problem :-(
> No mater what I was trying, tuners on this card wasn't recognized.
> Infact other tuners also wasn't recognized. Problem seems to be somehow
> dependent on number of tuners in system, as in my cloned test system
> with only 2 tuners I was able to configure them).
> After hours of tries I was forced to do all capturecard, cardinput,
> diseqc_tree (including SCR trees) & inputgroups setup manually at sql
> level.
> Positive is that I have full view how my DVB subsystem is configured
> (monotonic tuners numbers, clear diseqc tree, etc) - but, being under
> time pressure (production system), I was little frustrated that
> down-time took 3h instead of 15min :-(


Could you be so kind as to email me the records in the various tables
which relate explicitly to this tuner? If it will work with some pokes
and prods, I'm up for some table bashing.

Geoff




_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


warpme at o2

Jul 19, 2012, 9:51 AM

Post #19 of 22 (3797 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 7/17/12 9:58 PM, Warpme wrote:
> Hi *
>
> I just finish upgrade my system to 4xDVB-S2 + 1xDVB-T.
> All runs over single cable (SCR) :-)
>
> I'm looking for advice related to unreliable firmware loading.
> My sys is ArchLinux, kernel3.3.8, Mystique SaTiX-S2 Sky Xpress Dual,
> DVB-S2 a.k.a DvbSky S952.
> Card is based on Montage Montage DS3103/TS2022 with cx23885 A/V decoder.
> Both chips required firmware files.
> My issue is that sometimes (especially after cold boot) one or both
> tuners are non-functional due issue with loading firmware.
> Warm reboot usually helps - but 1 for 10 times not.
> I have impression this is kind of races or kernel bug.
>
> Does anybody idea how to solve issue ?
>
>
> Kernel log looks following:
>
> [root [at] mytht var]# cat /var/log/kernel.log | grep
> "DVB:\|firmware\|cx\|m88ds"
> Jul 17 21:04:09 [ 5.457385] cx88/2: cx2388x MPEG-TS Driver Manager
> version 0.0.9 loaded
> Jul 17 21:04:09 [ 5.460816] cx88[0]: subsystem: b034:3034, board:
> Prof 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
> Jul 17 21:04:09 [ 5.460819] cx88[0]: TV tuner type -1, Radio tuner
> type -1
> Jul 17 21:04:09 [ 5.478014] cx88/0: cx2388x v4l2 driver version
> 0.0.9 loaded
> Jul 17 21:04:09 [ 5.690521] cx23885 driver version 0.0.3 loaded
> Jul 17 21:04:09 [ 5.691092] CORE cx23885[0]: subsystem: 4254:0952,
> board: DVBSKY S952 [card=36,autodetected]
> Jul 17 21:04:09 [ 5.996797] cx25840 3-0044: cx23885 A/V decoder
> found @ 0x88 (cx23885[0])
> Jul 17 21:04:09 [ 6.210084] input: cx88 IR (Prof 7301 DVB-S/S2) as
> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0/input4
> Jul 17 21:04:09 [ 6.210123] rc0: cx88 IR (Prof 7301 DVB-S/S2) as
> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0
> Jul 17 21:04:09 [ 6.213429] input: MCE IR Keyboard/Mouse (cx88xx)
> as /devices/virtual/input/input5
> Jul 17 21:04:09 [ 6.213500] rc rc0: lirc_dev: driver ir-lirc-codec
> (cx88xx) registered at minor = 0
> Jul 17 21:04:09 [ 6.213502] cx88[0]/2: cx2388x 8802 Driver Manager
> Jul 17 21:04:09 [ 6.213531] cx88[0]/2: found at 0000:05:06.2, rev:
> 5, irq: 20, latency: 32, mmio: 0xf5000000
> Jul 17 21:04:09 [ 6.220418] cx88[1]: subsystem: 0070:9002, board:
> Hauppauge Nova-T DVB-T [card=18,autodetected], frontend(s): 1
> Jul 17 21:04:09 [ 6.220421] cx88[1]: TV tuner type 4, Radio tuner
> type -1
> Jul 17 21:04:09 [ 6.384583] cx88[1]: hauppauge eeprom: model=90003
> Jul 17 21:04:09 [ 6.443479] input: cx88 IR (Hauppauge Nova-T DVB-T
> as /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1/input6
> Jul 17 21:04:09 [ 6.443525] rc1: cx88 IR (Hauppauge Nova-T DVB-T as
> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1
> Jul 17 21:04:09 [ 6.444724] input: MCE IR Keyboard/Mouse (cx88xx)
> as /devices/virtual/input/input7
> Jul 17 21:04:09 [ 6.444813] rc rc1: lirc_dev: driver ir-lirc-codec
> (cx88xx) registered at minor = 1
> Jul 17 21:04:09 [ 6.444817] cx88[1]/2: cx2388x 8802 Driver Manager
> Jul 17 21:04:09 [ 6.444847] cx88[1]/2: found at 0000:05:07.2, rev:
> 5, irq: 21, latency: 32, mmio: 0xfa000000
> Jul 17 21:04:09 [ 6.448487] cx88[0]/0: found at 0000:05:06.0, rev:
> 5, irq: 20, latency: 32, mmio: 0xf6000000
> Jul 17 21:04:09 [ 6.448938] cx88[0]/0: registered device video0 [v4l2]
> Jul 17 21:04:09 [ 6.449299] cx88[0]/0: registered device vbi0
> Jul 17 21:04:09 [ 6.449418] cx88[1]/0: found at 0000:05:07.0, rev:
> 5, irq: 21, latency: 32, mmio: 0xfb000000
> Jul 17 21:04:09 [ 6.449586] cx88[1]/0: registered device video1 [v4l2]
> Jul 17 21:04:09 [ 6.449735] cx88[1]/0: registered device vbi1
> Jul 17 21:04:09 [ 6.454475] cx88[2]: subsystem: b034:3034, board:
> Prof 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
> Jul 17 21:04:09 [ 6.454478] cx88[2]: TV tuner type -1, Radio tuner
> type -1
> Jul 17 21:04:09 [ 6.697405] cx25840 3-0044: loaded
> v4l-cx23885-avcore-01.fw firmware (16382 bytes)
> Jul 17 21:04:09 [ 6.731510] cx23885_dvb_register() allocating 1
> frontend(s)
> Jul 17 21:04:09 [ 6.731515] cx23885[0]: cx23885 based dvb card
> Jul 17 21:04:09 [ 6.833715] m88ds3103_load_firmware: Waiting for
> firmware upload (dvb-fe-ds3103.fw)...
> Jul 17 21:04:09 [ 6.846768] firmware 0000:02:00.0:
> firmware_loading_store: unexpected value (0)
> Jul 17 21:04:09 [ 6.847589] m88ds3103_load_firmware: Waiting for
> firmware upload(2)...
> Jul 17 21:04:09 [ 6.847591] m88ds3103_load_firmware: No firmware
> uploaded (timeout or file not found?)
> Jul 17 21:04:09 [ 6.848230] m88ds3103_initilaze: Unable initialize
> firmware
> Jul 17 21:04:09 [ 6.848874] DVB: registering new adapter (cx23885[0])
> Jul 17 21:04:09 [ 6.848876] DVB: registering adapter 0 frontend 0
> (Montage DS3103/TS2022)...
> Jul 17 21:04:09 [ 6.849338] cx23885_dvb_register() allocating 1
> frontend(s)
> Jul 17 21:04:09 [ 6.849340] cx23885[0]: cx23885 based dvb card
> Jul 17 21:04:09 [ 6.907675] m88ds3103_load_firmware: Waiting for
> firmware upload (dvb-fe-ds3103.fw)...
> Jul 17 21:04:09 [ 6.908077] firmware 0000:02:00.0:
> firmware_loading_store: unexpected value (0)
> Jul 17 21:04:09 [ 6.910099] m88ds3103_load_firmware: Waiting for
> firmware upload(2)...
> Jul 17 21:04:09 [ 6.910102] m88ds3103_load_firmware: No firmware
> uploaded (timeout or file not found?)
> Jul 17 21:04:09 [ 6.910822] m88ds3103_initilaze: Unable initialize
> firmware
> Jul 17 21:04:09 [ 6.911534] DVB: registering new adapter (cx23885[0])
> Jul 17 21:04:09 [ 6.911537] DVB: registering adapter 1 frontend 0
> (Montage DS3103/TS2022)...
> Jul 17 21:04:09 [ 6.912099] cx23885_dev_checkrevision() Hardware
> revision = 0xa5
> Jul 17 21:04:09 [ 6.912105] cx23885[0]/0: found at 0000:02:00.0,
> rev: 4, irq: 16, latency: 0, mmio: 0xfd200000
> Jul 17 21:04:09 [ 6.953136] input: cx88 IR (Prof 7301 DVB-S/S2) as
> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2/input8
> Jul 17 21:04:09 [ 6.953347] rc2: cx88 IR (Prof 7301 DVB-S/S2) as
> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2
> Jul 17 21:04:09 [ 6.953524] input: MCE IR Keyboard/Mouse (cx88xx)
> as /devices/virtual/input/input9
> Jul 17 21:04:09 [ 6.953864] rc rc2: lirc_dev: driver ir-lirc-codec
> (cx88xx) registered at minor = 2
> Jul 17 21:04:09 [ 6.953870] cx88[2]/0: found at 0000:05:08.0, rev:
> 5, irq: 23, latency: 32, mmio: 0xf8000000
> Jul 17 21:04:09 [ 6.954019] cx88[2]/0: registered device video2 [v4l2]
> Jul 17 21:04:09 [ 6.954121] cx88[2]/0: registered device vbi2
> Jul 17 21:04:09 [ 6.957672] cx88[2]/2: cx2388x 8802 Driver Manager
> Jul 17 21:04:09 [ 6.957691] cx88[2]/2: found at 0000:05:08.2, rev:
> 5, irq: 23, latency: 32, mmio: 0xf7000000
> Jul 17 21:04:09 [ 6.958037] cx88/2: cx2388x dvb driver version
> 0.0.9 loaded
> Jul 17 21:04:09 [ 6.958039] cx88/2: registering cx8802 driver,
> type: dvb access: shared
> Jul 17 21:04:09 [ 6.958041] cx88[0]/2: subsystem: b034:3034, board:
> Prof 7301 DVB-S/S2 [card=83]
> Jul 17 21:04:09 [ 6.958043] cx88[0]/2: cx2388x based DVB/ATSC card
> Jul 17 21:04:09 [ 6.958045] cx8802_alloc_frontends() allocating 1
> frontend(s)
> Jul 17 21:04:09 [ 7.170175] input: cx23885 IR (DVBSKY S952) as
> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3/input10
> Jul 17 21:04:09 [ 7.173748] rc3: cx23885 IR (DVBSKY S952) as
> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3
> Jul 17 21:04:09 [ 7.173877] input: MCE IR Keyboard/Mouse (cx23885)
> as /devices/virtual/input/input11
> Jul 17 21:04:09 [ 7.174106] rc rc3: lirc_dev: driver ir-lirc-codec
> (cx23885) registered at minor = 3
> Jul 17 21:04:09 [ 7.386469] DVB: registering new adapter (cx88[0])
> Jul 17 21:04:09 [ 7.386473] DVB: registering adapter 2 frontend 0
> (STV090x Multistandard)...
> Jul 17 21:04:09 [ 7.387604] cx88[1]/2: subsystem: 0070:9002, board:
> Hauppauge Nova-T DVB-T [card=18]
> Jul 17 21:04:09 [ 7.387608] cx88[1]/2: cx2388x based DVB/ATSC card
> Jul 17 21:04:09 [ 7.387610] cx8802_alloc_frontends() allocating 1
> frontend(s)
> Jul 17 21:04:09 [ 7.762722] DVB: registering new adapter (cx88[1])
> Jul 17 21:04:09 [ 7.762726] DVB: registering adapter 3 frontend 0
> (Conexant CX22702 DVB-T)...
> Jul 17 21:04:09 [ 7.766281] cx88[2]/2: subsystem: b034:3034, board:
> Prof 7301 DVB-S/S2 [card=83]
> Jul 17 21:04:09 [ 7.766285] cx88[2]/2: cx2388x based DVB/ATSC card
> Jul 17 21:04:09 [ 7.766287] cx8802_alloc_frontends() allocating 1
> frontend(s)
> Jul 17 21:04:09 [ 7.893821] DVB: registering new adapter (cx88[2])
> Jul 17 21:04:09 [ 7.893824] DVB: registering adapter 4 frontend 0
> (STV090x Multistandard)...
> Jul 17 21:05:45 [ 104.894844] DVB: registering new adapter
> (DVB-LOOPBACK)
> Jul 17 21:05:45 [ 104.896424] DVB: registering new adapter
> (DVB-LOOPBACK)
> Jul 17 21:05:45 [ 104.896832] DVB: registering new adapter
> (DVB-LOOPBACK)
> Jul 17 21:05:45 [ 104.897199] DVB: registering new adapter
> (DVB-LOOPBACK)
> Jul 17 21:14:07 [ 606.813334] cx8802_start_dma() Failed. Unsupported
> value in .mpeg (0x00000001)
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users
Hi,
FYI
My problem seems to be triggered in udev by:
http://marc.info/?l=linux-netdev&m=132655490826765&w=2
Some driver developers seems to be working on driver updates:
http://article.gmane.org/gmane.linux.kernel.wireless.general/85716
In the meantime, my distro (Archlinux) developer (Tom Gundersen)
developed patch which seems to be solving issue (at least with 10 tests
I hadn't any problem with firmware loading):
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/0001-Reinstate-TIMEOUT-handling.patch?h=packages/systemd

-br
Attachments: warpme.vcf (83 B)


newbury at mandamus

Jul 19, 2012, 2:27 PM

Post #20 of 22 (3787 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 07/18/2012 03:54 PM, Warpme wrote:

>>
> Oh well - this approach was my first try.
> I was trying blacklist all relevant modules to have clear starting point
> and next write small script allowing to load them "reliably".
> Issue is that after blacklisting all modules for this card it still
> loads. Probably there are some other modules - common with other cards -
> which are triggering load of modules for this card. Now I potentially
> have to cover not only this feral card but also modules for other - well
> working - cards.
> I decided stop this concept and listen what some more knowledgeable ppl
> will say here...

Most of the tuner modules rely on i2c-core and other stuff so you cannot
avoid that being called. I only removed the exact drivers which the
'top' module uses.

You could try using modinfo, but it will not necessarily disclose the
hardware modules upon which the top driver depends. At least that's the
situation with this card: the other two modules are not "dependencies"
listed by modinfo.

G.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


newbury at mandamus

Jul 19, 2012, 3:26 PM

Post #21 of 22 (3789 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On 07/19/2012 12:51 PM, Warpme wrote:
> On 7/17/12 9:58 PM, Warpme wrote:
>> Hi *
>>
>> I just finish upgrade my system to 4xDVB-S2 + 1xDVB-T.
>> All runs over single cable (SCR) :-)
>>
>> I'm looking for advice related to unreliable firmware loading.
>> My sys is ArchLinux, kernel3.3.8, Mystique SaTiX-S2 Sky Xpress Dual,
>> DVB-S2 a.k.a DvbSky S952.
>> Card is based on Montage Montage DS3103/TS2022 with cx23885 A/V decoder.
>> Both chips required firmware files.
>> My issue is that sometimes (especially after cold boot) one or both
>> tuners are non-functional due issue with loading firmware.
>> Warm reboot usually helps - but 1 for 10 times not.
>> I have impression this is kind of races or kernel bug.
>>
>> Does anybody idea how to solve issue ?
>>
>>
>> Kernel log looks following:
>>
>> [root [at] mytht var]# cat /var/log/kernel.log | grep
>> "DVB:\|firmware\|cx\|m88ds"
>> Jul 17 21:04:09 [ 5.457385] cx88/2: cx2388x MPEG-TS Driver Manager
>> version 0.0.9 loaded
>> Jul 17 21:04:09 [ 5.460816] cx88[0]: subsystem: b034:3034, board: Prof
>> 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
>> Jul 17 21:04:09 [ 5.460819] cx88[0]: TV tuner type -1, Radio tuner
>> type -1
>> Jul 17 21:04:09 [ 5.478014] cx88/0: cx2388x v4l2 driver version 0.0.9
>> loaded
>> Jul 17 21:04:09 [ 5.690521] cx23885 driver version 0.0.3 loaded
>> Jul 17 21:04:09 [ 5.691092] CORE cx23885[0]: subsystem: 4254:0952,
>> board: DVBSKY S952 [card=36,autodetected]
>> Jul 17 21:04:09 [ 5.996797] cx25840 3-0044: cx23885 A/V decoder found
>> @ 0x88 (cx23885[0])
>> Jul 17 21:04:09 [ 6.210084] input: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0/input4
>> Jul 17 21:04:09 [ 6.210123] rc0: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0
>> Jul 17 21:04:09 [ 6.213429] input: MCE IR Keyboard/Mouse (cx88xx) as
>> /devices/virtual/input/input5
>> Jul 17 21:04:09 [ 6.213500] rc rc0: lirc_dev: driver ir-lirc-codec
>> (cx88xx) registered at minor = 0
>> Jul 17 21:04:09 [ 6.213502] cx88[0]/2: cx2388x 8802 Driver Manager
>> Jul 17 21:04:09 [ 6.213531] cx88[0]/2: found at 0000:05:06.2, rev: 5,
>> irq: 20, latency: 32, mmio: 0xf5000000
>> Jul 17 21:04:09 [ 6.220418] cx88[1]: subsystem: 0070:9002, board:
>> Hauppauge Nova-T DVB-T [card=18,autodetected], frontend(s): 1
>> Jul 17 21:04:09 [ 6.220421] cx88[1]: TV tuner type 4, Radio tuner type -1
>> Jul 17 21:04:09 [ 6.384583] cx88[1]: hauppauge eeprom: model=90003
>> Jul 17 21:04:09 [ 6.443479] input: cx88 IR (Hauppauge Nova-T DVB-T as
>> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1/input6
>> Jul 17 21:04:09 [ 6.443525] rc1: cx88 IR (Hauppauge Nova-T DVB-T as
>> /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1
>> Jul 17 21:04:09 [ 6.444724] input: MCE IR Keyboard/Mouse (cx88xx) as
>> /devices/virtual/input/input7
>> Jul 17 21:04:09 [ 6.444813] rc rc1: lirc_dev: driver ir-lirc-codec
>> (cx88xx) registered at minor = 1
>> Jul 17 21:04:09 [ 6.444817] cx88[1]/2: cx2388x 8802 Driver Manager
>> Jul 17 21:04:09 [ 6.444847] cx88[1]/2: found at 0000:05:07.2, rev: 5,
>> irq: 21, latency: 32, mmio: 0xfa000000
>> Jul 17 21:04:09 [ 6.448487] cx88[0]/0: found at 0000:05:06.0, rev: 5,
>> irq: 20, latency: 32, mmio: 0xf6000000
>> Jul 17 21:04:09 [ 6.448938] cx88[0]/0: registered device video0 [v4l2]
>> Jul 17 21:04:09 [ 6.449299] cx88[0]/0: registered device vbi0
>> Jul 17 21:04:09 [ 6.449418] cx88[1]/0: found at 0000:05:07.0, rev: 5,
>> irq: 21, latency: 32, mmio: 0xfb000000
>> Jul 17 21:04:09 [ 6.449586] cx88[1]/0: registered device video1 [v4l2]
>> Jul 17 21:04:09 [ 6.449735] cx88[1]/0: registered device vbi1
>> Jul 17 21:04:09 [ 6.454475] cx88[2]: subsystem: b034:3034, board: Prof
>> 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
>> Jul 17 21:04:09 [ 6.454478] cx88[2]: TV tuner type -1, Radio tuner
>> type -1
>> Jul 17 21:04:09 [ 6.697405] cx25840 3-0044: loaded
>> v4l-cx23885-avcore-01.fw firmware (16382 bytes)
>> Jul 17 21:04:09 [ 6.731510] cx23885_dvb_register() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 6.731515] cx23885[0]: cx23885 based dvb card
>> Jul 17 21:04:09 [ 6.833715] m88ds3103_load_firmware: Waiting for
>> firmware upload (dvb-fe-ds3103.fw)...
>> Jul 17 21:04:09 [ 6.846768] firmware 0000:02:00.0:
>> firmware_loading_store: unexpected value (0)
>> Jul 17 21:04:09 [ 6.847589] m88ds3103_load_firmware: Waiting for
>> firmware upload(2)...
>> Jul 17 21:04:09 [ 6.847591] m88ds3103_load_firmware: No firmware
>> uploaded (timeout or file not found?)
>> Jul 17 21:04:09 [ 6.848230] m88ds3103_initilaze: Unable initialize
>> firmware
>> Jul 17 21:04:09 [ 6.848874] DVB: registering new adapter (cx23885[0])
>> Jul 17 21:04:09 [ 6.848876] DVB: registering adapter 0 frontend 0
>> (Montage DS3103/TS2022)...
>> Jul 17 21:04:09 [ 6.849338] cx23885_dvb_register() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 6.849340] cx23885[0]: cx23885 based dvb card
>> Jul 17 21:04:09 [ 6.907675] m88ds3103_load_firmware: Waiting for
>> firmware upload (dvb-fe-ds3103.fw)...
>> Jul 17 21:04:09 [ 6.908077] firmware 0000:02:00.0:
>> firmware_loading_store: unexpected value (0)
>> Jul 17 21:04:09 [ 6.910099] m88ds3103_load_firmware: Waiting for
>> firmware upload(2)...
>> Jul 17 21:04:09 [ 6.910102] m88ds3103_load_firmware: No firmware
>> uploaded (timeout or file not found?)
>> Jul 17 21:04:09 [ 6.910822] m88ds3103_initilaze: Unable initialize
>> firmware
>> Jul 17 21:04:09 [ 6.911534] DVB: registering new adapter (cx23885[0])
>> Jul 17 21:04:09 [ 6.911537] DVB: registering adapter 1 frontend 0
>> (Montage DS3103/TS2022)...
>> Jul 17 21:04:09 [ 6.912099] cx23885_dev_checkrevision() Hardware
>> revision = 0xa5
>> Jul 17 21:04:09 [ 6.912105] cx23885[0]/0: found at 0000:02:00.0, rev:
>> 4, irq: 16, latency: 0, mmio: 0xfd200000
>> Jul 17 21:04:09 [ 6.953136] input: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2/input8
>> Jul 17 21:04:09 [ 6.953347] rc2: cx88 IR (Prof 7301 DVB-S/S2) as
>> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2
>> Jul 17 21:04:09 [ 6.953524] input: MCE IR Keyboard/Mouse (cx88xx) as
>> /devices/virtual/input/input9
>> Jul 17 21:04:09 [ 6.953864] rc rc2: lirc_dev: driver ir-lirc-codec
>> (cx88xx) registered at minor = 2
>> Jul 17 21:04:09 [ 6.953870] cx88[2]/0: found at 0000:05:08.0, rev: 5,
>> irq: 23, latency: 32, mmio: 0xf8000000
>> Jul 17 21:04:09 [ 6.954019] cx88[2]/0: registered device video2 [v4l2]
>> Jul 17 21:04:09 [ 6.954121] cx88[2]/0: registered device vbi2
>> Jul 17 21:04:09 [ 6.957672] cx88[2]/2: cx2388x 8802 Driver Manager
>> Jul 17 21:04:09 [ 6.957691] cx88[2]/2: found at 0000:05:08.2, rev: 5,
>> irq: 23, latency: 32, mmio: 0xf7000000
>> Jul 17 21:04:09 [ 6.958037] cx88/2: cx2388x dvb driver version 0.0.9
>> loaded
>> Jul 17 21:04:09 [ 6.958039] cx88/2: registering cx8802 driver, type:
>> dvb access: shared
>> Jul 17 21:04:09 [ 6.958041] cx88[0]/2: subsystem: b034:3034, board:
>> Prof 7301 DVB-S/S2 [card=83]
>> Jul 17 21:04:09 [ 6.958043] cx88[0]/2: cx2388x based DVB/ATSC card
>> Jul 17 21:04:09 [ 6.958045] cx8802_alloc_frontends() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 7.170175] input: cx23885 IR (DVBSKY S952) as
>> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3/input10
>> Jul 17 21:04:09 [ 7.173748] rc3: cx23885 IR (DVBSKY S952) as
>> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3
>> Jul 17 21:04:09 [ 7.173877] input: MCE IR Keyboard/Mouse (cx23885) as
>> /devices/virtual/input/input11
>> Jul 17 21:04:09 [ 7.174106] rc rc3: lirc_dev: driver ir-lirc-codec
>> (cx23885) registered at minor = 3
>> Jul 17 21:04:09 [ 7.386469] DVB: registering new adapter (cx88[0])
>> Jul 17 21:04:09 [ 7.386473] DVB: registering adapter 2 frontend 0
>> (STV090x Multistandard)...
>> Jul 17 21:04:09 [ 7.387604] cx88[1]/2: subsystem: 0070:9002, board:
>> Hauppauge Nova-T DVB-T [card=18]
>> Jul 17 21:04:09 [ 7.387608] cx88[1]/2: cx2388x based DVB/ATSC card
>> Jul 17 21:04:09 [ 7.387610] cx8802_alloc_frontends() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 7.762722] DVB: registering new adapter (cx88[1])
>> Jul 17 21:04:09 [ 7.762726] DVB: registering adapter 3 frontend 0
>> (Conexant CX22702 DVB-T)...
>> Jul 17 21:04:09 [ 7.766281] cx88[2]/2: subsystem: b034:3034, board:
>> Prof 7301 DVB-S/S2 [card=83]
>> Jul 17 21:04:09 [ 7.766285] cx88[2]/2: cx2388x based DVB/ATSC card
>> Jul 17 21:04:09 [ 7.766287] cx8802_alloc_frontends() allocating 1
>> frontend(s)
>> Jul 17 21:04:09 [ 7.893821] DVB: registering new adapter (cx88[2])
>> Jul 17 21:04:09 [ 7.893824] DVB: registering adapter 4 frontend 0
>> (STV090x Multistandard)...
>> Jul 17 21:05:45 [ 104.894844] DVB: registering new adapter (DVB-LOOPBACK)
>> Jul 17 21:05:45 [ 104.896424] DVB: registering new adapter (DVB-LOOPBACK)
>> Jul 17 21:05:45 [ 104.896832] DVB: registering new adapter (DVB-LOOPBACK)
>> Jul 17 21:05:45 [ 104.897199] DVB: registering new adapter (DVB-LOOPBACK)
>> Jul 17 21:14:07 [ 606.813334] cx8802_start_dma() Failed. Unsupported
>> value in .mpeg (0x00000001)


The drivers need to load in a particular order. It may be (as it is with
my Hauppauge 2250 card) that the modules are being loaded in the wrong
order.

Try removing them and then reloading in the desired order. Looks like
you have 2 separate tuner sets, with the cx88 ( or cx2388) module as the
base. If you can get that repeatable, then stick it into rc.local and
call it on every boot.

This is a workaround and not a fix, but your mythbox will work and the
WAF will climb, not plunge.




G.







_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


jaglover at gmail

Jul 19, 2012, 5:38 PM

Post #22 of 22 (3779 views)
Permalink
Re: OT: unreliable firmware load after cold boot [In reply to]

On Thu, 19 Jul 2012 18:26:52 -0400
"R. G. Newbury" <newbury [at] mandamus> wrote:

> On 07/19/2012 12:51 PM, Warpme wrote:
> > On 7/17/12 9:58 PM, Warpme wrote:
> >> Hi *
> >>
> >> I just finish upgrade my system to 4xDVB-S2 + 1xDVB-T.
> >> All runs over single cable (SCR) :-)
> >>
> >> I'm looking for advice related to unreliable firmware loading.
> >> My sys is ArchLinux, kernel3.3.8, Mystique SaTiX-S2 Sky Xpress
> >> Dual, DVB-S2 a.k.a DvbSky S952.
> >> Card is based on Montage Montage DS3103/TS2022 with cx23885 A/V
> >> decoder. Both chips required firmware files.
> >> My issue is that sometimes (especially after cold boot) one or both
> >> tuners are non-functional due issue with loading firmware.
> >> Warm reboot usually helps - but 1 for 10 times not.
> >> I have impression this is kind of races or kernel bug.
> >>
> >> Does anybody idea how to solve issue ?
> >>
> >>
> >> Kernel log looks following:
> >>
> >> [root [at] mytht var]# cat /var/log/kernel.log | grep
> >> "DVB:\|firmware\|cx\|m88ds"
> >> Jul 17 21:04:09 [ 5.457385] cx88/2: cx2388x MPEG-TS Driver Manager
> >> version 0.0.9 loaded
> >> Jul 17 21:04:09 [ 5.460816] cx88[0]: subsystem: b034:3034, board:
> >> Prof 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
> >> Jul 17 21:04:09 [ 5.460819] cx88[0]: TV tuner type -1, Radio tuner
> >> type -1
> >> Jul 17 21:04:09 [ 5.478014] cx88/0: cx2388x v4l2 driver version
> >> 0.0.9 loaded
> >> Jul 17 21:04:09 [ 5.690521] cx23885 driver version 0.0.3 loaded
> >> Jul 17 21:04:09 [ 5.691092] CORE cx23885[0]: subsystem: 4254:0952,
> >> board: DVBSKY S952 [card=36,autodetected]
> >> Jul 17 21:04:09 [ 5.996797] cx25840 3-0044: cx23885 A/V decoder
> >> found @ 0x88 (cx23885[0])
> >> Jul 17 21:04:09 [ 6.210084] input: cx88 IR (Prof 7301 DVB-S/S2) as
> >> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0/input4
> >> Jul 17 21:04:09 [ 6.210123] rc0: cx88 IR (Prof 7301 DVB-S/S2) as
> >> /devices/pci0000:00/0000:00:14.4/0000:05:06.2/rc/rc0
> >> Jul 17 21:04:09 [ 6.213429] input: MCE IR Keyboard/Mouse (cx88xx)
> >> as /devices/virtual/input/input5
> >> Jul 17 21:04:09 [ 6.213500] rc rc0: lirc_dev: driver ir-lirc-codec
> >> (cx88xx) registered at minor = 0
> >> Jul 17 21:04:09 [ 6.213502] cx88[0]/2: cx2388x 8802 Driver Manager
> >> Jul 17 21:04:09 [ 6.213531] cx88[0]/2: found at 0000:05:06.2, rev:
> >> 5, irq: 20, latency: 32, mmio: 0xf5000000
> >> Jul 17 21:04:09 [ 6.220418] cx88[1]: subsystem: 0070:9002, board:
> >> Hauppauge Nova-T DVB-T [card=18,autodetected], frontend(s): 1
> >> Jul 17 21:04:09 [ 6.220421] cx88[1]: TV tuner type 4, Radio tuner
> >> type -1 Jul 17 21:04:09 [ 6.384583] cx88[1]: hauppauge eeprom:
> >> model=90003 Jul 17 21:04:09 [ 6.443479] input: cx88 IR (Hauppauge
> >> Nova-T DVB-T
> >> as /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1/input6 Jul
> >> 17 21:04:09 [ 6.443525] rc1: cx88 IR (Hauppauge Nova-T DVB-T
> >> as /devices/pci0000:00/0000:00:14.4/0000:05:07.2/rc/rc1 Jul 17
> >> 21:04:09 [ 6.444724] input: MCE IR Keyboard/Mouse (cx88xx)
> >> as /devices/virtual/input/input7 Jul 17 21:04:09 [ 6.444813] rc
> >> rc1: lirc_dev: driver ir-lirc-codec (cx88xx) registered at minor =
> >> 1 Jul 17 21:04:09 [ 6.444817] cx88[1]/2: cx2388x 8802 Driver
> >> Manager Jul 17 21:04:09 [ 6.444847] cx88[1]/2: found at
> >> 0000:05:07.2, rev: 5, irq: 21, latency: 32, mmio: 0xfa000000
> >> Jul 17 21:04:09 [ 6.448487] cx88[0]/0: found at 0000:05:06.0, rev:
> >> 5, irq: 20, latency: 32, mmio: 0xf6000000
> >> Jul 17 21:04:09 [ 6.448938] cx88[0]/0: registered device video0
> >> [v4l2] Jul 17 21:04:09 [ 6.449299] cx88[0]/0: registered device
> >> vbi0 Jul 17 21:04:09 [ 6.449418] cx88[1]/0: found at 0000:05:07.0,
> >> rev: 5, irq: 21, latency: 32, mmio: 0xfb000000
> >> Jul 17 21:04:09 [ 6.449586] cx88[1]/0: registered device video1
> >> [v4l2] Jul 17 21:04:09 [ 6.449735] cx88[1]/0: registered device
> >> vbi1 Jul 17 21:04:09 [ 6.454475] cx88[2]: subsystem: b034:3034,
> >> board: Prof 7301 DVB-S/S2 [card=83,autodetected], frontend(s): 1
> >> Jul 17 21:04:09 [ 6.454478] cx88[2]: TV tuner type -1, Radio tuner
> >> type -1
> >> Jul 17 21:04:09 [ 6.697405] cx25840 3-0044: loaded
> >> v4l-cx23885-avcore-01.fw firmware (16382 bytes)
> >> Jul 17 21:04:09 [ 6.731510] cx23885_dvb_register() allocating 1
> >> frontend(s)
> >> Jul 17 21:04:09 [ 6.731515] cx23885[0]: cx23885 based dvb card
> >> Jul 17 21:04:09 [ 6.833715] m88ds3103_load_firmware: Waiting for
> >> firmware upload (dvb-fe-ds3103.fw)...
> >> Jul 17 21:04:09 [ 6.846768] firmware 0000:02:00.0:
> >> firmware_loading_store: unexpected value (0)
> >> Jul 17 21:04:09 [ 6.847589] m88ds3103_load_firmware: Waiting for
> >> firmware upload(2)...
> >> Jul 17 21:04:09 [ 6.847591] m88ds3103_load_firmware: No firmware
> >> uploaded (timeout or file not found?)
> >> Jul 17 21:04:09 [ 6.848230] m88ds3103_initilaze: Unable initialize
> >> firmware
> >> Jul 17 21:04:09 [ 6.848874] DVB: registering new adapter
> >> (cx23885[0]) Jul 17 21:04:09 [ 6.848876] DVB: registering adapter
> >> 0 frontend 0 (Montage DS3103/TS2022)...
> >> Jul 17 21:04:09 [ 6.849338] cx23885_dvb_register() allocating 1
> >> frontend(s)
> >> Jul 17 21:04:09 [ 6.849340] cx23885[0]: cx23885 based dvb card
> >> Jul 17 21:04:09 [ 6.907675] m88ds3103_load_firmware: Waiting for
> >> firmware upload (dvb-fe-ds3103.fw)...
> >> Jul 17 21:04:09 [ 6.908077] firmware 0000:02:00.0:
> >> firmware_loading_store: unexpected value (0)
> >> Jul 17 21:04:09 [ 6.910099] m88ds3103_load_firmware: Waiting for
> >> firmware upload(2)...
> >> Jul 17 21:04:09 [ 6.910102] m88ds3103_load_firmware: No firmware
> >> uploaded (timeout or file not found?)
> >> Jul 17 21:04:09 [ 6.910822] m88ds3103_initilaze: Unable initialize
> >> firmware
> >> Jul 17 21:04:09 [ 6.911534] DVB: registering new adapter
> >> (cx23885[0]) Jul 17 21:04:09 [ 6.911537] DVB: registering adapter
> >> 1 frontend 0 (Montage DS3103/TS2022)...
> >> Jul 17 21:04:09 [ 6.912099] cx23885_dev_checkrevision() Hardware
> >> revision = 0xa5
> >> Jul 17 21:04:09 [ 6.912105] cx23885[0]/0: found at 0000:02:00.0,
> >> rev: 4, irq: 16, latency: 0, mmio: 0xfd200000
> >> Jul 17 21:04:09 [ 6.953136] input: cx88 IR (Prof 7301 DVB-S/S2) as
> >> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2/input8
> >> Jul 17 21:04:09 [ 6.953347] rc2: cx88 IR (Prof 7301 DVB-S/S2) as
> >> /devices/pci0000:00/0000:00:14.4/0000:05:08.0/rc/rc2
> >> Jul 17 21:04:09 [ 6.953524] input: MCE IR Keyboard/Mouse (cx88xx)
> >> as /devices/virtual/input/input9
> >> Jul 17 21:04:09 [ 6.953864] rc rc2: lirc_dev: driver ir-lirc-codec
> >> (cx88xx) registered at minor = 2
> >> Jul 17 21:04:09 [ 6.953870] cx88[2]/0: found at 0000:05:08.0, rev:
> >> 5, irq: 23, latency: 32, mmio: 0xf8000000
> >> Jul 17 21:04:09 [ 6.954019] cx88[2]/0: registered device video2
> >> [v4l2] Jul 17 21:04:09 [ 6.954121] cx88[2]/0: registered device
> >> vbi2 Jul 17 21:04:09 [ 6.957672] cx88[2]/2: cx2388x 8802 Driver
> >> Manager Jul 17 21:04:09 [ 6.957691] cx88[2]/2: found at
> >> 0000:05:08.2, rev: 5, irq: 23, latency: 32, mmio: 0xf7000000
> >> Jul 17 21:04:09 [ 6.958037] cx88/2: cx2388x dvb driver version
> >> 0.0.9 loaded
> >> Jul 17 21:04:09 [ 6.958039] cx88/2: registering cx8802 driver,
> >> type: dvb access: shared
> >> Jul 17 21:04:09 [ 6.958041] cx88[0]/2: subsystem: b034:3034, board:
> >> Prof 7301 DVB-S/S2 [card=83]
> >> Jul 17 21:04:09 [ 6.958043] cx88[0]/2: cx2388x based DVB/ATSC card
> >> Jul 17 21:04:09 [ 6.958045] cx8802_alloc_frontends() allocating 1
> >> frontend(s)
> >> Jul 17 21:04:09 [ 7.170175] input: cx23885 IR (DVBSKY S952) as
> >> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3/input10
> >> Jul 17 21:04:09 [ 7.173748] rc3: cx23885 IR (DVBSKY S952) as
> >> /devices/pci0000:00/0000:00:04.0/0000:02:00.0/rc/rc3
> >> Jul 17 21:04:09 [ 7.173877] input: MCE IR Keyboard/Mouse (cx23885)
> >> as /devices/virtual/input/input11
> >> Jul 17 21:04:09 [ 7.174106] rc rc3: lirc_dev: driver ir-lirc-codec
> >> (cx23885) registered at minor = 3
> >> Jul 17 21:04:09 [ 7.386469] DVB: registering new adapter (cx88[0])
> >> Jul 17 21:04:09 [ 7.386473] DVB: registering adapter 2 frontend 0
> >> (STV090x Multistandard)...
> >> Jul 17 21:04:09 [ 7.387604] cx88[1]/2: subsystem: 0070:9002, board:
> >> Hauppauge Nova-T DVB-T [card=18]
> >> Jul 17 21:04:09 [ 7.387608] cx88[1]/2: cx2388x based DVB/ATSC card
> >> Jul 17 21:04:09 [ 7.387610] cx8802_alloc_frontends() allocating 1
> >> frontend(s)
> >> Jul 17 21:04:09 [ 7.762722] DVB: registering new adapter (cx88[1])
> >> Jul 17 21:04:09 [ 7.762726] DVB: registering adapter 3 frontend 0
> >> (Conexant CX22702 DVB-T)...
> >> Jul 17 21:04:09 [ 7.766281] cx88[2]/2: subsystem: b034:3034, board:
> >> Prof 7301 DVB-S/S2 [card=83]
> >> Jul 17 21:04:09 [ 7.766285] cx88[2]/2: cx2388x based DVB/ATSC card
> >> Jul 17 21:04:09 [ 7.766287] cx8802_alloc_frontends() allocating 1
> >> frontend(s)
> >> Jul 17 21:04:09 [ 7.893821] DVB: registering new adapter (cx88[2])
> >> Jul 17 21:04:09 [ 7.893824] DVB: registering adapter 4 frontend 0
> >> (STV090x Multistandard)...
> >> Jul 17 21:05:45 [ 104.894844] DVB: registering new adapter
> >> (DVB-LOOPBACK) Jul 17 21:05:45 [ 104.896424] DVB: registering new
> >> adapter (DVB-LOOPBACK) Jul 17 21:05:45 [ 104.896832] DVB:
> >> registering new adapter (DVB-LOOPBACK) Jul 17 21:05:45
> >> [ 104.897199] DVB: registering new adapter (DVB-LOOPBACK) Jul 17
> >> 21:14:07 [ 606.813334] cx8802_start_dma() Failed. Unsupported
> >> value in .mpeg (0x00000001)
>
>
> The drivers need to load in a particular order. It may be (as it is
> with my Hauppauge 2250 card) that the modules are being loaded in the
> wrong order.
>
> Try removing them and then reloading in the desired order. Looks like
> you have 2 separate tuner sets, with the cx88 ( or cx2388) module as
> the base. If you can get that repeatable, then stick it into rc.local
> and call it on every boot.
>
> This is a workaround and not a fix, but your mythbox will work and
> the WAF will climb, not plunge.

I haven't following this thread from beginning. But if you have
firmware loading problems why don't you build it into kernel?
Works for me.

--
Cheers, Saul
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.