Device is issued different device# at boot

hpladd · 10-25-2007, 09:13 AM

Sometimes my tuner card works; other times it does not work at all. It appears that how the hardware is recognized at boot time determines whether the card will operate or not.

The dmesg snipets below are from the same machine. The first was obtained when the system was NOT working. The second was obtained when it was working.

Not operational:

Quote:

$ cat dmesg_not_operational | grep tuner
cx88[0]: TV tuner type 60, Radio tuner type -1
tuner 0-0043: chip found @ 0x86 (cx88[0])
tda9887 0-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 0-0043: type set to tda9887
tuner 0-0061: chip found @ 0xc2 (cx88[0])
tuner-simple 0-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
tuner 0-0061: type set to Thomson DTT 761X (ATSC/NTSC)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tuner-simple 1-0061: type set to 50 (TCL 2002N)
tuner 1-0061: type set to TCL 2002N

Operational:

Quote:

$ cat dmesg_operational | grep tuner
cx88[0]: TV tuner type 60, Radio tuner type -1
tuner 2-0043: chip found @ 0x86 (cx88[0])
tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 2-0043: type set to tda9887
tuner 2-0061: chip found @ 0xc2 (cx88[0])
tuner-simple 2-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
tuner 2-0061: type set to Thomson DTT 761X (ATSC/NTSC)
tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tveeprom 3-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tuner-simple 3-0061: type set to 50 (TCL 2002N)
tuner 3-0061: type set to TCL 2002N

The error message from dmesg_not_operational:

Quote:

$ tail dmesg_not_operational
or51132: Waiting for firmware upload(dvb-fe-or51132-vsb.fw)...
or51132: I2C write (addr 0x15 len 1771) error: -121
or51132: load_firmware error 1
or51132: Writing firmware to device failed!

Note: I am sure that the firmware which fails to load (dvb-fe-or51132-vsb.fw) is used by the misbehaving tuner card. It makes sense that the card would fail without its firmware.

My theory: The system is trying to load the firmware to the wrong location or perhaps to the wrong card.

The temporary cure: Unplug the machine for 10 minutes and reboot. Then the firmware loads, and the machine works for the next 3 to 5 boots.

Machine description:
AMD Athlon 64
1 gig ram
Knoppmyth
2.6.18-chw-13
pcHDTV -- HD3000 (failing capture card)
Hauppauge PVR-150 (capture that works like a charm)

lspci (from the machine when operating correctly):

Quote:

00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation C51G [GeForce 6100] (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a2)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a2)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.2 Multimedia audio controller: nVidia Corporation MCP51 AC97 Audio Controller (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
04:08.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
04:08.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
04:09.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)

aus9 · 10-26-2007, 02:09 AM

while you wait for a better reply,

q have you tried F7 or is there some reason why you stay with F6?

q have you tried a compiled kernel?

q have you tried (if F has such a thing) to include the i2c module in /etc/modprobe.preload or words to that effect

q if no such F preload is available have you tried a extra line in your rc.local to retry your hw detection module in case, its merely a time issue.

BTW I do not have your hw I am only replying as its in the zero posts.

seeing that your reset works for a few boots causes me just as much puzzlement as I am sure it does for you.

hpladd · 10-26-2007, 05:29 AM

Quote:

Originally Posted by aus9

while you wait for a better reply,

Thanks I'm desperate.

Quote:

q have you tried F7 or is there some reason why you stay with F6?

I'm assuming F7 is Fedora Core 7 -- not the F7 key. This project was done with Knoppmyth R5F27 -- a distribution dedicated to creating MythTV boxes.

Quote:

q have you tried a compiled kernel?

Nope -- the MythTV compile is too complex for me brain.

Quote:

q have you tried (if F has such a thing) to include the i2c module in /etc/modprobe.preload or words to that effect

q if no such F preload is available have you tried a extra line in your rc.local to retry your hw detection module in case, its merely a time issue.

Thinking along those lines. I started to look at how to write udev rules.

Quote:

seeing that your reset works for a few boots causes me just as much puzzlement as I am sure it does for you.

What particularly puzzles me is this: when the machine operates correctly the tuners are numbered 3 and 4 (without any reference to 1 or 2 in dmesg). When it is not operational, the tuners are number 1 and 2.

What causes the numbering to skip 1 and 2 is a mystery, and why it is important to skip 1 and 2 for the machine to operate properly I don't know.

aus9 · 10-26-2007, 10:42 AM

hava agander at this post
http://www.linuxquestions.org/questi...tv-pro-573379/

politely ask HappyTux if he can look at your post and post a link to it.

its not quite a hijack but I spot your tuner in his list for v4l