Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. ivtv>
  3. users
Intermittent: why can't I see two /dev/lirc devices instead of just one?
rbonafied at gmail
Dec 19, 2009, 11:34 AM
Post #1 of 2 (1788 views)
Permalink
Hi,

With Jarod's help, I'm using the lirc_zilog module to enable my pvr 150
IR blaster. The box is fitted with two pvr 150's. Before rebooting, I
had both a /dev/lirc0 and a /dev/lirc1. I had to open the box up to
connect another fan and after booting, I only have one /dev/lirc0
showing up. I think opening the box has nothing to do with it, but I
thought I'd mention it. Both IVTV cards are registered. What can I do
to debug this or better yet to activate the second blaster/remote
consistently?

Here are my box details:
Linux notivo 2.6.31.5-desktop-1mnb #1 SMP Fri Oct 23 01:46:54 EDT 2009
i686 AMD Athlon(tm) II X2 250 Processor GNU/Linux

/etc/modprobe.conf:
# I2C module options
alias char-major-89 i2c-dev
alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-81-1 ivtv

Message log info:

Dec 14 16:45:06 notivo ivtv: Start initialization, version 1.4.1
Dec 14 16:45:06 notivo ivtv0: Initializing card 0
Dec 14 16:45:06 notivo ivtv0: Autodetected Hauppauge card (cx23416 based)
Dec 14 16:45:06 notivo ivtv 0000:03:06.0: PCI INT A -> GSI 20 (level,
low) -> IRQ 20
Dec 14 16:45:06 notivo ivtv0: Unreasonably low latency timer, setting to
64 (was 32)
Dec 14 16:45:06 notivo ivtv0: Autodetected Hauppauge WinTV PVR-150
Dec 14 16:45:06 notivo ivtv0: Reopen i2c bus for IR-blaster support
Dec 14 16:45:06 notivo cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c
driver #0)
Dec 14 16:45:06 notivo tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
Dec 14 16:45:06 notivo wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
Dec 14 16:45:06 notivo IRQ 20/ivtv0: IRQF_DISABLED is not guaranteed on
shared IRQs
Dec 14 16:45:06 notivo ivtv0: Registered device video0 for encoder MPG
(4096 kB)
Dec 14 16:45:06 notivo ivtv0: Registered device video32 for encoder YUV
(2048 kB)
Dec 14 16:45:06 notivo ivtv0: Registered device vbi0 for encoder VBI
(1024 kB)
Dec 14 16:45:06 notivo ivtv0: Registered device video24 for encoder PCM
(320 kB)
Dec 14 16:45:06 notivo ivtv0: Initialized card: Hauppauge WinTV PVR-150
Dec 14 16:45:06 notivo ivtv1: Initializing card 1
Dec 14 16:45:06 notivo ivtv1: Autodetected Hauppauge card (cx23416 based)
Dec 14 16:45:06 notivo ivtv 0000:03:07.0: PCI INT A -> GSI 21 (level,
low) -> IRQ 21
Dec 14 16:45:06 notivo ivtv1: Unreasonably low latency timer, setting to
64 (was 32)
Dec 14 16:45:06 notivo ivtv1: Autodetected Hauppauge WinTV PVR-150
Dec 14 16:45:06 notivo ivtv1: Reopen i2c bus for IR-blaster support
Dec 14 16:45:06 notivo cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c
driver #1)
Dec 14 16:45:06 notivo tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
Dec 14 16:45:06 notivo wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
Dec 14 16:45:06 notivo IRQ 21/ivtv1: IRQF_DISABLED is not guaranteed on
shared IRQs
Dec 14 16:45:06 notivo ivtv1: Registered device video1 for encoder MPG
(4096 kB)
Dec 14 16:45:06 notivo ivtv1: Registered device video33 for encoder YUV
(2048 kB)
Dec 14 16:45:06 notivo ivtv1: Registered device vbi1 for encoder VBI
(1024 kB)
Dec 14 16:45:06 notivo ivtv1: Registered device video25 for encoder PCM
(320 kB)
Dec 14 16:45:06 notivo ivtv1: Initialized card: Hauppauge WinTV PVR-150
Dec 14 16:45:06 notivo ivtv: End initialization
Dec 14 16:45:06 notivo ivtv 0000:03:06.0: firmware: requesting
v4l-cx2341x-enc.fw
Dec 14 16:45:06 notivo ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836
bytes)
Dec 14 16:45:06 notivo ivtv 0000:03:07.0: firmware: requesting
v4l-cx2341x-enc.fw
Dec 14 16:45:06 notivo ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836
bytes)
Dec 14 16:45:06 notivo ivtv0: Encoder revision: 0x02060039
Dec 14 16:45:06 notivo ivtv1: Encoder revision: 0x02060039
Dec 14 16:45:06 notivo lirc_dev: IR Remote Control driver registered,
major 251
Dec 14 16:45:06 notivo lirc_zilog: Zilog/Hauppauge IR driver initializing
Dec 14 16:45:06 notivo lirc_zilog: chip found with RX and TX
Dec 14 16:45:06 notivo i2c-adapter i2c-1: lirc_dev: driver lirc_zilog
registered at minor = 0
Dec 14 16:45:06 notivo lirc_zilog: Zilog/Hauppauge IR blaster firmware
version 1.3.0 loaded
Dec 14 16:45:06 notivo lirc_zilog: initialization complete


Thank you,
Rick

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: Intermittent: why can't I see two /dev/lirc devices instead of just one? [ In reply to ]
awalls at radix
Dec 20, 2009, 11:03 AM
Post #2 of 2 (1667 views)
Permalink
On Sat, 2009-12-19 at 14:34 -0500, Rick wrote:
> Hi,
>
> With Jarod's help, I'm using the lirc_zilog module to enable my pvr 150
> IR blaster. The box is fitted with two pvr 150's. Before rebooting, I
> had both a /dev/lirc0 and a /dev/lirc1. I had to open the box up to
> connect another fan and after booting, I only have one /dev/lirc0
> showing up. I think opening the box has nothing to do with it, but I
> thought I'd mention it. Both IVTV cards are registered. What can I do
> to debug this or better yet to activate the second blaster/remote
> consistently?

1. Inhibit i2c_dev and ir-kbd-i2c from loading automatically by
blacklisting them in your modules configuration.

2. Before loading lirc modules use ivtv-ctl to reset the Zilog IR chip

# ivtv-ctl -d /dev/video0 --reset 1
# ivtv-ctl -d /dev/video1 --reset 1

3. And maybe you'll feel like twiddling the ivtv module parameters
"new_i2c" and "i2c_clock_period". Results may vary and may make things
worse. If you set the i2c_clock_period too long, you'll certainly
notice.


> Here are my box details:
> Linux notivo 2.6.31.5-desktop-1mnb #1 SMP Fri Oct 23 01:46:54 EDT 2009
> i686 AMD Athlon(tm) II X2 250 Processor GNU/Linux
>
> /etc/modprobe.conf:
> # I2C module options
> alias char-major-89 i2c-dev
> alias char-major-81 videodev
> alias char-major-81-0 ivtv
> alias char-major-81-1 ivtv
>
> Message log info:
>
> Dec 14 16:45:06 notivo ivtv: Start initialization, version 1.4.1
> Dec 14 16:45:06 notivo ivtv0: Initializing card 0
> Dec 14 16:45:06 notivo ivtv0: Autodetected Hauppauge card (cx23416 based)
> Dec 14 16:45:06 notivo ivtv 0000:03:06.0: PCI INT A -> GSI 20 (level,
> low) -> IRQ 20
> Dec 14 16:45:06 notivo ivtv0: Unreasonably low latency timer, setting to
> 64 (was 32)
> Dec 14 16:45:06 notivo ivtv0: Autodetected Hauppauge WinTV PVR-150
> Dec 14 16:45:06 notivo ivtv0: Reopen i2c bus for IR-blaster support
> Dec 14 16:45:06 notivo cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c
> driver #0)

Out of curiosity, do these PVR-150's really have CX25841 chips (as
opposed to CX25843 chips)?

Regards,
Andy

> Dec 14 16:45:06 notivo tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> Dec 14 16:45:06 notivo wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
> Dec 14 16:45:06 notivo IRQ 20/ivtv0: IRQF_DISABLED is not guaranteed on
> shared IRQs
> Dec 14 16:45:06 notivo ivtv0: Registered device video0 for encoder MPG
> (4096 kB)
> Dec 14 16:45:06 notivo ivtv0: Registered device video32 for encoder YUV
> (2048 kB)
> Dec 14 16:45:06 notivo ivtv0: Registered device vbi0 for encoder VBI
> (1024 kB)
> Dec 14 16:45:06 notivo ivtv0: Registered device video24 for encoder PCM
> (320 kB)
> Dec 14 16:45:06 notivo ivtv0: Initialized card: Hauppauge WinTV PVR-150
> Dec 14 16:45:06 notivo ivtv1: Initializing card 1
> Dec 14 16:45:06 notivo ivtv1: Autodetected Hauppauge card (cx23416 based)
> Dec 14 16:45:06 notivo ivtv 0000:03:07.0: PCI INT A -> GSI 21 (level,
> low) -> IRQ 21
> Dec 14 16:45:06 notivo ivtv1: Unreasonably low latency timer, setting to
> 64 (was 32)
> Dec 14 16:45:06 notivo ivtv1: Autodetected Hauppauge WinTV PVR-150
> Dec 14 16:45:06 notivo ivtv1: Reopen i2c bus for IR-blaster support
> Dec 14 16:45:06 notivo cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c
> driver #1)
> Dec 14 16:45:06 notivo tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> Dec 14 16:45:06 notivo wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
> Dec 14 16:45:06 notivo IRQ 21/ivtv1: IRQF_DISABLED is not guaranteed on
> shared IRQs
> Dec 14 16:45:06 notivo ivtv1: Registered device video1 for encoder MPG
> (4096 kB)
> Dec 14 16:45:06 notivo ivtv1: Registered device video33 for encoder YUV
> (2048 kB)
> Dec 14 16:45:06 notivo ivtv1: Registered device vbi1 for encoder VBI
> (1024 kB)
> Dec 14 16:45:06 notivo ivtv1: Registered device video25 for encoder PCM
> (320 kB)
> Dec 14 16:45:06 notivo ivtv1: Initialized card: Hauppauge WinTV PVR-150
> Dec 14 16:45:06 notivo ivtv: End initialization
> Dec 14 16:45:06 notivo ivtv 0000:03:06.0: firmware: requesting
> v4l-cx2341x-enc.fw
> Dec 14 16:45:06 notivo ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836
> bytes)
> Dec 14 16:45:06 notivo ivtv 0000:03:07.0: firmware: requesting
> v4l-cx2341x-enc.fw
> Dec 14 16:45:06 notivo ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836
> bytes)
> Dec 14 16:45:06 notivo ivtv0: Encoder revision: 0x02060039
> Dec 14 16:45:06 notivo ivtv1: Encoder revision: 0x02060039
> Dec 14 16:45:06 notivo lirc_dev: IR Remote Control driver registered,
> major 251
> Dec 14 16:45:06 notivo lirc_zilog: Zilog/Hauppauge IR driver initializing
> Dec 14 16:45:06 notivo lirc_zilog: chip found with RX and TX
> Dec 14 16:45:06 notivo i2c-adapter i2c-1: lirc_dev: driver lirc_zilog
> registered at minor = 0
> Dec 14 16:45:06 notivo lirc_zilog: Zilog/Hauppauge IR blaster firmware
> version 1.3.0 loaded
> Dec 14 16:45:06 notivo lirc_zilog: initialization complete
>
>
> Thank you,
> Rick


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal