Mailing List Archive

PVR-150 -- Remote not showing up
since no one answered this on the dev list i'm going to try putting it here

i'm trying to follow the guide to getting my remote working from http://ivtv.writeme.ch/tiki-print.php?page=remotes but after i modprobe ir-kbd-i2c it does not show up as a event device, i tried a mknod to add /dev/input/event4 (as 0-3 all exist and none are related to the card) and it still cant find the remote

lsmod is (evdev is compiled in the kernel so it doesn't show, but i do have it)

root[at]mr-slack:/home/edman007# lsmod
Module Size Used by
ir_kbd_i2c 8844 0
ir_common 8580 1 ir_kbd_i2c
w83627hf 30504 0
eeprom 7696 0
i2c_sensor 3840 2 w83627hf,eeprom
i2c_isa 2432 0
usb_storage 116496 0
intel_agp 23836 1
i2c_i801 9228 0
tda9887 13840 0
wm8775 6620 0
cx25840 43796 0
firmware_class 10880 1 cx25840
tuner 25376 0
tveeprom 14508 0
ivtv 215956 2
i2c_algo_bit 10248 1 ivtv
i2c_core 22272 12 ir_kbd_i2c,w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801,tda9887,wm8775,cx25840,tuner,tveeprom,i2c_algo_bit
videodev 9984 3 ivtv
ath_pci 82076 0
ath_rate_sample 16904 1 ath_pci
wlan 148124 3 ath_pci,ath_rate_sample
ath_hal 148944 3 ath_pci,ath_rate_sample
nvidia 3714216 12
nvidia_agp 8348 0
agpgart 36944 3 intel_agp,nvidia,nvidia_agp
analog 12448 0

and as mentioned in my pervious thread both tveeprom and tuner are the ivtv ones

when modprobing ir-kbd-i2c i see nothing in any logs or dmesg, maybe i'm not looking in the right one but i checked syslog and messages and there is nothing about it

and my lsinput

root[at]mr-slack:/home/edman007# lsinput
/dev/input/event0
bustype : BUS_USB
vendor : 0x46d
product : 0xc30a
version : 5376
name : "Logitech Logitech USB Keyboard"
phys : "usb-0000:00:1d.3-1/input0"
uniq : ""
bits ev : EV_SYN EV_KEY EV_LED EV_REP

/dev/input/event1
bustype : BUS_USB
vendor : 0x46d
product : 0xc30a
version : 5376
name : "Logitech Logitech USB Keyboard"
phys : "usb-0000:00:1d.3-1/input1"
uniq : ""
bits ev : EV_SYN EV_KEY EV_REL EV_ABS

/dev/input/event2
bustype : BUS_USB
vendor : 0x45e
product : 0x40
version : 768
name : "Microsoft Microsoft 3-Button Mou"
phys : "usb-0000:00:1d.3-2/input0"
uniq : ""
bits ev : EV_SYN EV_KEY EV_REL

/dev/input/event3
bustype : BUS_ISA
vendor : 0x1f
product : 0x1
version : 256
name : "PC Speaker"
phys : "isa0061/input0"
bits ev : EV_SYN EV_SND

open /dev/input/event4: No such device
root[at]mr-slack:/home/edman007# ls /dev/input/event4
/dev/input/event4

if i rm the event4 device that i created lsinput still tries to open it, also i'm running the 2.6.13.3 kernel

and on another note, does anyone know how to make mythtv use better quality data from the card, all fast motion spots with high contrast (like some one waving their arm) produces very jagged edges and i think its from the mpeg encoding as everything else looks excellent
PVR-150 -- Remote not showing up [ In reply to ]
What's your dmesg output between the "start init ivtv" and "end init
ivtv" lines? What about if you do dmesg|grep ir?

On 10/8/05, Edward Martin <edman007x@mac.com> wrote:
> since no one answered this on the dev list i'm going to try putting it here
>
> i'm trying to follow the guide to getting my remote working from http://ivtv.writeme.ch/tiki-print.php?page=remotes but after i modprobe ir-kbd-i2c it does not show up as a event device, i tried a mknod to add /dev/input/event4 (as 0-3 all exist and none are related to the card) and it still cant find the remote
>
> lsmod is (evdev is compiled in the kernel so it doesn't show, but i do have it)
>
> root[at]mr-slack:/home/edman007# lsmod
> Module Size Used by
> ir_kbd_i2c 8844 0
> ir_common 8580 1 ir_kbd_i2c
> w83627hf 30504 0
> eeprom 7696 0
> i2c_sensor 3840 2 w83627hf,eeprom
> i2c_isa 2432 0
> usb_storage 116496 0
> intel_agp 23836 1
> i2c_i801 9228 0
> tda9887 13840 0
> wm8775 6620 0
> cx25840 43796 0
> firmware_class 10880 1 cx25840
> tuner 25376 0
> tveeprom 14508 0
> ivtv 215956 2
> i2c_algo_bit 10248 1 ivtv
> i2c_core 22272 12 ir_kbd_i2c,w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801,tda9887,wm8775,cx25840,tuner,tveeprom,i2c_algo_bit
> videodev 9984 3 ivtv
> ath_pci 82076 0
> ath_rate_sample 16904 1 ath_pci
> wlan 148124 3 ath_pci,ath_rate_sample
> ath_hal 148944 3 ath_pci,ath_rate_sample
> nvidia 3714216 12
> nvidia_agp 8348 0
> agpgart 36944 3 intel_agp,nvidia,nvidia_agp
> analog 12448 0
>
> and as mentioned in my pervious thread both tveeprom and tuner are the ivtv ones
>
> when modprobing ir-kbd-i2c i see nothing in any logs or dmesg, maybe i'm not looking in the right one but i checked syslog and messages and there is nothing about it
>
> and my lsinput
>
> root[at]mr-slack:/home/edman007# lsinput
> /dev/input/event0
> bustype : BUS_USB
> vendor : 0x46d
> product : 0xc30a
> version : 5376
> name : "Logitech Logitech USB Keyboard"
> phys : "usb-0000:00:1d.3-1/input0"
> uniq : ""
> bits ev : EV_SYN EV_KEY EV_LED EV_REP
>
> /dev/input/event1
> bustype : BUS_USB
> vendor : 0x46d
> product : 0xc30a
> version : 5376
> name : "Logitech Logitech USB Keyboard"
> phys : "usb-0000:00:1d.3-1/input1"
> uniq : ""
> bits ev : EV_SYN EV_KEY EV_REL EV_ABS
>
> /dev/input/event2
> bustype : BUS_USB
> vendor : 0x45e
> product : 0x40
> version : 768
> name : "Microsoft Microsoft 3-Button Mou"
> phys : "usb-0000:00:1d.3-2/input0"
> uniq : ""
> bits ev : EV_SYN EV_KEY EV_REL
>
> /dev/input/event3
> bustype : BUS_ISA
> vendor : 0x1f
> product : 0x1
> version : 256
> name : "PC Speaker"
> phys : "isa0061/input0"
> bits ev : EV_SYN EV_SND
>
> open /dev/input/event4: No such device
> root[at]mr-slack:/home/edman007# ls /dev/input/event4
> /dev/input/event4
>
> if i rm the event4 device that i created lsinput still tries to open it, also i'm running the 2.6.13.3 kernel
>
> and on another note, does anyone know how to make mythtv use better quality data from the card, all fast motion spots with high contrast (like some one waving their arm) produces very jagged edges and i think its from the mpeg encoding as everything else looks excellent
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
PVR-150 -- Remote not showing up [ In reply to ]
On Saturday, October 08, 2005, at 05:45PM, Adam Forsyth <agforsyth@gmail.com> wrote:

>What's your dmesg output between the "start init ivtv" and "end init
>ivtv" lines? What about if you do dmesg|grep ir?
>
one thing i should mention is that ir_kdb_i2c does not modprobe itself like all the other modules

dmesg|grep ir shows nothing at all related to ir, its mostly SCSI and and IRQ's but anyways

Oct 8 05:09:35 localhost kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 8 05:09:35 localhost kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 8 05:09:35 localhost kernel: PCI: Using ACPI for IRQ routing
Oct 8 05:09:35 localhost kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
Oct 8 05:09:35 localhost kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Oct 8 05:09:35 localhost kernel: PNP: No PS/2 controller found. Probing ports directly.
Oct 8 05:09:35 localhost kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Oct 8 05:09:35 localhost kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Oct 8 05:09:35 localhost kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 18 (level, low) -> IRQ 16
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 16
Oct 8 05:09:35 localhost kernel: ICH5: not 100%% native mode: will probe irqs later
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
Oct 8 05:09:35 localhost kernel: ata1: SATA max UDMA/133 cmd 0xEFE0 ctl 0xEFAE bmdma 0xEF90 irq 16
Oct 8 05:09:35 localhost kernel: ata2: SATA max UDMA/133 cmd 0xEFA0 ctl 0xEFAA bmdma 0xEF98 irq 16
Oct 8 05:09:35 localhost kernel: Type: Direct-Access ANSI SCSI revision: 05
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 20 (level, low) -> IRQ 17
Oct 8 05:09:35 localhost kernel: PCI: Via IRQ fixup for 0000:03:03.0, from 5 to 1
Oct 8 05:09:35 localhost kernel: ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[17] MMIO=[f7eff800-f7efffff] Max Packet=[2048]
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 18
Oct 8 05:09:35 localhost kernel: ehci_hcd 0000:00:1d.7: irq 18, io mem 0xf7fffc00
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 19
Oct 8 05:09:35 localhost kernel: uhci_hcd 0000:00:1d.0: irq 19, io base 0x0000eec0
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 20
Oct 8 05:09:35 localhost kernel: uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000ef00
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 16
Oct 8 05:09:35 localhost kernel: uhci_hcd 0000:00:1d.2: irq 16, io base 0x0000ef20
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:00:1d.3[A] -> GSI 16 (level, low) -> IRQ 19
Oct 8 05:09:35 localhost kernel: uhci_hcd 0000:00:1d.3: irq 19, io base 0x0000ef40
Oct 8 05:09:35 localhost kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0028
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 21
Oct 8 05:09:35 localhost kernel: #0: Intel ICH5 with AD1985 at 0xf7fff800, irq 21
Oct 8 05:09:35 localhost kernel: Starting balanced_irq
Oct 8 05:09:35 localhost kernel: ReiserFS: hda1: journal params: device hda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Oct 8 05:09:35 localhost kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 19
Oct 8 05:09:35 localhost kernel: ReiserFS: sda2: journal params: device sda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Oct 8 05:09:35 localhost kernel: ReiserFS: sda3: journal params: device sda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Oct 8 05:09:35 localhost kernel: ReiserFS: sda4: journal params: device sda4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Oct 8 05:09:36 localhost kernel: ACPI: PCI Interrupt 0000:03:0d.0[A] -> GSI 21 (level, low) -> IRQ 22
Oct 8 05:09:36 localhost kernel: ath0: Atheros 5212: mem=0xf7ee0000, irq=22
Oct 8 05:09:37 localhost kernel: ACPI: PCI Interrupt 0000:03:0c.0[A] -> GSI 20 (level, low) -> IRQ 17
Oct 8 05:09:49 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02
Oct 8 05:09:49 localhost kernel: Type: Direct-Access ANSI SCSI revision: 00
Oct 8 17:35:21 localhost kernel: Type: Direct-Access ANSI SCSI revision: 00
Oct 8 17:37:44 localhost kernel: Type: Direct-Access ANSI SCSI revision: 00
Oct 8 17:38:37 localhost kernel: Type: Direct-Access ANSI SCSI revision: 00
Oct 8 17:41:04 localhost kernel: Type: Direct-Access ANSI SCSI revision: 00

and the ivtv stuff

Oct 8 05:09:37 localhost kernel: Linux video capture interface: v1.00
Oct 8 05:09:37 localhost kernel: ivtv: ==================== START INIT IVTV ====================
Oct 8 05:09:37 localhost kernel: ivtv: version 0.3.9 (development snapshot compiled on Thu 06 Oct 2005 06:18:49 PM EDT) loading
Oct 8 05:09:37 localhost kernel: ivtv: Linux version: 2.6.13.3 SMP preempt PENTIUM4 gcc-3.3
Oct 8 05:09:37 localhost kernel: ivtv: In case of problems please include the debug info
Oct 8 05:09:37 localhost kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when
Oct 8 05:09:37 localhost kernel: ivtv: mailing the ivtv-devel mailinglist.
Oct 8 05:09:37 localhost kernel: ivtv: Autodetected WinTV PVR 150 card (iTVC16 based)
Oct 8 05:09:37 localhost kernel: ACPI: PCI Interrupt 0000:03:0c.0[A] -> GSI 20 (level, low) -> IRQ 17
Oct 8 05:09:37 localhost kernel: tveeprom: ivtv version
Oct 8 05:09:37 localhost kernel: tveeprom: Hauppauge: model = 26032, rev = C199, serial# = 8239113
Oct 8 05:09:37 localhost kernel: tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50)
Oct 8 05:09:37 localhost kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
Oct 8 05:09:37 localhost kernel: tveeprom: audio processor = CX25841 (type = 23)
Oct 8 05:09:37 localhost kernel: tveeprom: decoder processor = CX25841 (type = 1c)
Oct 8 05:09:37 localhost kernel: ivtv: i2c attach to card #0 ok [client=tveeprom[50], addr=50]
Oct 8 05:09:37 localhost kernel: ivtv: i2c attach to card #0 ok [client=(tuner unset), addr=61]
Oct 8 05:09:37 localhost kernel: cx25840: loading /lib/modules/HcwMakoA.ROM
Oct 8 05:09:38 localhost kernel: ivtv: i2c attach to card #0 ok [client=cx25840, addr=44]
Oct 8 05:09:38 localhost kernel: ivtv: i2c attach to card #0 ok [client=wm8775, addr=1b]
Oct 8 05:09:39 localhost kernel: ivtv: loading /lib/modules/ivtv-fw-enc.bin
Oct 8 05:09:39 localhost kernel: ivtv: Encoder revision: 0x02040011
Oct 8 05:09:39 localhost kernel: ivtv: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
Oct 8 05:09:39 localhost kernel: ivtv: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
Oct 8 05:09:39 localhost kernel: ivtv: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
Oct 8 05:09:39 localhost kernel: ivtv: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
Oct 8 05:09:40 localhost kernel: ivtv: Initialized WinTV PVR 150, card #0
Oct 8 05:09:40 localhost kernel: ivtv: ==================== END INIT IVTV ====================



>On 10/8/05, Edward Martin <edman007x@mac.com> wrote:
>> since no one answered this on the dev list i'm going to try putting it here
>>
>> i'm trying to follow the guide to getting my remote working from http://ivtv.writeme.ch/tiki-print.php?page=remotes but after i modprobe ir-kbd-i2c it does not show up as a event device, i tried a mknod to add /dev/input/event4 (as 0-3 all exist and none are related to the card) and it still cant find the remote
>>
>> lsmod is (evdev is compiled in the kernel so it doesn't show, but i do have it)
>>
>> root[at]mr-slack:/home/edman007# lsmod
>> Module Size Used by
>> ir_kbd_i2c 8844 0
>> ir_common 8580 1 ir_kbd_i2c
>> w83627hf 30504 0
>> eeprom 7696 0
>> i2c_sensor 3840 2 w83627hf,eeprom
>> i2c_isa 2432 0
>> usb_storage 116496 0
>> intel_agp 23836 1
>> i2c_i801 9228 0
>> tda9887 13840 0
>> wm8775 6620 0
>> cx25840 43796 0
>> firmware_class 10880 1 cx25840
>> tuner 25376 0
>> tveeprom 14508 0
>> ivtv 215956 2
>> i2c_algo_bit 10248 1 ivtv
>> i2c_core 22272 12 ir_kbd_i2c,w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801,tda9887,wm8775,cx25840,tuner,tveeprom,i2c_algo_bit
>> videodev 9984 3 ivtv
>> ath_pci 82076 0
>> ath_rate_sample 16904 1 ath_pci
>> wlan 148124 3 ath_pci,ath_rate_sample
>> ath_hal 148944 3 ath_pci,ath_rate_sample
>> nvidia 3714216 12
>> nvidia_agp 8348 0
>> agpgart 36944 3 intel_agp,nvidia,nvidia_agp
>> analog 12448 0
>>
>> and as mentioned in my pervious thread both tveeprom and tuner are the ivtv ones
>>
>> when modprobing ir-kbd-i2c i see nothing in any logs or dmesg, maybe i'm not looking in the right one but i checked syslog and messages and there is nothing about it
>>
>> and my lsinput
>>
>> root[at]mr-slack:/home/edman007# lsinput
>> /dev/input/event0
>> bustype : BUS_USB
>> vendor : 0x46d
>> product : 0xc30a
>> version : 5376
>> name : "Logitech Logitech USB Keyboard"
>> phys : "usb-0000:00:1d.3-1/input0"
>> uniq : ""
>> bits ev : EV_SYN EV_KEY EV_LED EV_REP
>>
>> /dev/input/event1
>> bustype : BUS_USB
>> vendor : 0x46d
>> product : 0xc30a
>> version : 5376
>> name : "Logitech Logitech USB Keyboard"
>> phys : "usb-0000:00:1d.3-1/input1"
>> uniq : ""
>> bits ev : EV_SYN EV_KEY EV_REL EV_ABS
>>
>> /dev/input/event2
>> bustype : BUS_USB
>> vendor : 0x45e
>> product : 0x40
>> version : 768
>> name : "Microsoft Microsoft 3-Button Mou"
>> phys : "usb-0000:00:1d.3-2/input0"
>> uniq : ""
>> bits ev : EV_SYN EV_KEY EV_REL
>>
>> /dev/input/event3
>> bustype : BUS_ISA
>> vendor : 0x1f
>> product : 0x1
>> version : 256
>> name : "PC Speaker"
>> phys : "isa0061/input0"
>> bits ev : EV_SYN EV_SND
>>
>> open /dev/input/event4: No such device
>> root[at]mr-slack:/home/edman007# ls /dev/input/event4
>> /dev/input/event4
>>
>> if i rm the event4 device that i created lsinput still tries to open it, also i'm running the 2.6.13.3 kernel
>>
>> and on another note, does anyone know how to make mythtv use better quality data from the card, all fast motion spots with high contrast (like some one waving their arm) produces very jagged edges and i think its from the mpeg encoding as everything else looks excellent
>>
>> _______________________________________________
>> ivtv-users mailing list
>> ivtv-users@ivtvdriver.org
>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>>
>
>_______________________________________________
>ivtv-users mailing list
>ivtv-users@ivtvdriver.org
>http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
PVR-150 -- Remote not showing up [ In reply to ]
I don't think that's relevent, I meant the rest. You should be loading
lirc_dev / lirc_i2c, not i2c_kbd_whatever.

On 10/8/05, Edward Martin <edman007x@mac.com> wrote:
> well i cant use the kernel tveeprom as i had that before and i couldn't change channels, i don't want that happing again (look at the dev list)
>
> as for reading the docs i'll try compiling evdev as a module because that doc says "...as a module.." so that might be the cause and they give a few other things, i'll do everything that says and report back oin how it goes
>
> *off to recompile kernel* :(
>
> On Saturday, October 08, 2005, at 07:28PM, Adam Forsyth <agforsyth@gmail.com> wrote:
>
> >> one thing i should mention is that ir_kdb_i2c does not modprobe itself like all the other modules
> >>
> >> dmesg|grep ir shows nothing at all related to ir, its mostly SCSI and and IRQ's but anyways
> >
> >Your ivtv dmesg looks fine as far as it goes. I'd reccomend using the
> >kernel tveeprom.ko instead.
> >
> >> >> root[at]mr-slack:/home/edman007# lsmod
> >> >> Module Size Used by
> >> >> ir_kbd_i2c 8844 0
> >> >> ir_common 8580 1 ir_kbd_i2c
> >> >> w83627hf 30504 0
> >> >> eeprom 7696 0
> >> >> i2c_sensor 3840 2 w83627hf,eeprom
> >> >> i2c_isa 2432 0
> >> >> usb_storage 116496 0
> >> >> intel_agp 23836 1
> >> >> i2c_i801 9228 0
> >> >> tda9887 13840 0
> >> >> wm8775 6620 0
> >> >> cx25840 43796 0
> >> >> firmware_class 10880 1 cx25840
> >> >> tuner 25376 0
> >> >> tveeprom 14508 0
> >> >> ivtv 215956 2
> >> >> i2c_algo_bit 10248 1 ivtv
> >> >> i2c_core 22272 12 ir_kbd_i2c,w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801,tda9887,wm8775,cx25840,tuner,tveeprom,i2c_algo_bit
> >> >> videodev 9984 3 ivtv
> >> >> ath_pci 82076 0
> >> >> ath_rate_sample 16904 1 ath_pci
> >> >> wlan 148124 3 ath_pci,ath_rate_sample
> >> >> ath_hal 148944 3 ath_pci,ath_rate_sample
> >> >> nvidia 3714216 12
> >> >> nvidia_agp 8348 0
> >> >> agpgart 36944 3 intel_agp,nvidia,nvidia_agp
> >> >> analog 12448 0
> >> >>
> >> >> and as mentioned in my pervious thread both tveeprom and tuner are the ivtv ones
> >> >>
> >> >> when modprobing ir-kbd-i2c i see nothing in any logs or dmesg, maybe i'm not looking in the right one but i checked syslog and messages and there is nothing about it
> >
> >Nothing in dmesg or messages? When lirc_i2c attaches to my pvr-350 I
> >get this message:
> >
> >ivtv: i2c attach to card #0 ok [client=Hauppauge IR, addr=18]
> >
> >So if you're not seeing anything like that I don't think it's
> >connecting to the card correctly.
> >
> >I think that the info on that wiki page is very old. I'd follow the
> >instructions in the source at doc/README.lirc as it is more up to
> >date.
> >
> >
>
PVR-150 -- Remote not showing up [ In reply to ]
Looking better. Now:
1. Use the kernel version of tveeprom.ko
2. hide the bttv.ko
3. run depmod
4. cold boot.

Then, once lirc_i2c is loaded, start lircd, and do "ls -l /dev/lirc*"
and make sure there is a /dev/lircd, /dev/lirc0, and a /dev/lirc. If
there is no /dev/lirc, then you need to either create a symlink from
/dev/lirc0 to /dev/lirc immediately after loading the driver, or make
a udev rules file so it happens on it's own. If you do one of the 2nd
two make sure to restart lircd after the /dev/lirc is there.

Then, run irw and click away with that remote to see if you get
anything. The IR port on the back of the 350 is finniky so the 150 may
be too, make sure it's plugged in well.

On 10/8/05, Edward Martin <edman007x@mac.com> wrote:
>
> On Saturday, October 08, 2005, at 08:15PM, Adam Forsyth <agforsyth@gmail.com> wrote:
>
> >I don't think that's relevent, I meant the rest. You should be loading
> >lirc_dev / lirc_i2c, not i2c_kbd_whatever.
> >
> ok, well i did everything that thing said and it still dosent work, i just get a few bttv errors and it says it attached it, but i can't get anything out of it, and its not the remote cause i tested that with my digital camera
>
> and here is the dmesg stuff showing the errors
>
> lirc_dev: IR Remote Control driver registered, at major 61
> lirc_i2c: no version for "lirc_unregister_plugin" found: kernel tainted.
> Linux video capture interface: v1.00
> bttv: disagrees about version of symbol tveeprom_hauppauge_analog
> bttv: Unknown symbol tveeprom_hauppauge_analog
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.3.9 (development snapshot compiled on Sat 08 Oct 2005 08:48:59 PM EDT) loading
> ivtv: Linux version: 2.6.13.3 SMP preempt PENTIUM4 gcc-3.3
> ivtv: In case of problems please include the debug info
> ivtv: between the START INIT IVTV and END INIT IVTV lines when
> ivtv: mailing the ivtv-devel mailinglist.
> ivtv: Autodetected WinTV PVR 150 card (iTVC16 based)
> ACPI: PCI Interrupt 0000:03:0c.0[A] -> GSI 20 (level, low) -> IRQ 17
> tveeprom: ivtv version
> tveeprom: Hauppauge: model = 26032, rev = C199, serial# = 8239113
> tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50)
> tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
> tveeprom: audio processor = CX25841 (type = 23)
> tveeprom: decoder processor = CX25841 (type = 1c)
> ivtv: i2c attach to card #0 ok [client=tveeprom[50], addr=50]
> tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
> ivtv: i2c attach to card #0 ok [client=(tuner unset), addr=61]
> cx25840: loading /lib/modules/HcwMakoA.ROM
> ivtv: i2c attach to card #0 ok [client=cx25840, addr=44]
> ivtv: i2c attach to card #0 ok [client=wm8775, addr=1b]
> ivtv: loading /lib/modules/ivtv-fw-enc.bin
> ivtv: Encoder revision: 0x02040011
> ivtv: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
> ivtv: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
> ivtv: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
> ivtv: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
> tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0
> ivtv: Initialized WinTV PVR 150, card #0
> ivtv: ==================== END INIT IVTV ====================
> lirc_i2c: chip found @ 0x71 (Hauppauge IR (PVR150))
> ivtv: i2c attach to card #0 ok [client=Hauppauge IR (PVR150), addr=71]
> lirc_dev: lirc_register_plugin: sample_rate: 10
>
>
> >On 10/8/05, Edward Martin <edman007x@mac.com> wrote:
> >> well i cant use the kernel tveeprom as i had that before and i couldn't change channels, i don't want that happing again (look at the dev list)
> >>
> >> as for reading the docs i'll try compiling evdev as a module because that doc says "...as a module.." so that might be the cause and they give a few other things, i'll do everything that says and report back oin how it goes
> >>
> >> *off to recompile kernel* :(
> >>
> >> On Saturday, October 08, 2005, at 07:28PM, Adam Forsyth <agforsyth@gmail.com> wrote:
> >>t the rest. You should be loading
> lirc_dev / lirc_i2c, not i2c_kbd_whatever.
> >> >> one thing i should mention is that ir_kdb_i2c does not modprobe itself like all the other modules
> >> >>
> >> >> dmesg|grep ir shows nothing at all related to ir, its mostly SCSI and and IRQ's but anyways
> >> >
> >> >Your ivtv dmesg looks fine as far as it goes. I'd reccomend using the
> >> >kernel tveeprom.ko instead.
> >> >
> >> >> >> root[at]mr-slack:/home/edman007# lsmod
> >> >> >> Module Size Used by
> >> >> >> ir_kbd_i2c 8844 0
> >> >> >> ir_common 8580 1 ir_kbd_i2c
> >> >> >> w83627hf 30504 0
> >> >> >> eeprom 7696 0
> >> >> >> i2c_sensor 3840 2 w83627hf,eeprom
> >> >> >> i2c_isa 2432 0
> >> >> >> usb_storage 116496 0
> >> >> >> intel_agp 23836 1
> >> >> >> i2c_i801 9228 0
> >> >> >> tda9887 13840 0
> >> >> >> wm8775 6620 0
> >> >> >> cx25840 43796 0
> >> >> >> firmware_class 10880 1 cx25840
> >> >> >> tuner 25376 0
> >> >> >> tveeprom 14508 0
> >> >> >> ivtv 215956 2
> >> >> >> i2c_algo_bit 10248 1 ivtv
> >> >> >> i2c_core 22272 12 ir_kbd_i2c,w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801,tda9887,wm8775,cx25840,tuner,tveeprom,i2c_algo_bit
> >> >> >> videodev 9984 3 ivtv
> >> >> >> ath_pci 82076 0
> >> >> >> ath_rate_sample 16904 1 ath_pci
> >> >> >> wlan 148124 3 ath_pci,ath_rate_sample
> >> >> >> ath_hal 148944 3 ath_pci,ath_rate_sample
> >> >> >> nvidia 3714216 12
> >> >> >> nvidia_agp 8348 0
> >> >> >> agpgart 36944 3 intel_agp,nvidia,nvidia_agp
> >> >> >> analog 12448 0
> >> >> >>
> >> >> >> and as mentioned in my pervious thread both tveeprom and tuner are the ivtv ones
> >> >> >>
> >> >> >> when modprobing ir-kbd-i2c i see nothing in any logs or dmesg, maybe i'm not looking in the right one but i checked syslog and messages and there is nothing about it
> >> >
> >> >Nothing in dmesg or messages? When lirc_i2c attaches to my pvr-350 I
> >> >get this message:
> >> >
> >> >ivtv: i2c attach to card #0 ok [client=Hauppauge IR, addr=18]
> >> >
> >> >So if you're not seeing anything like that I don't think it's
> >> >connecting to the card correctly.
> >> >
> >> >I think that the info on that wiki page is very old. I'd follow the
> >> >instructions in the source at doc/README.lirc as it is more up to
> >> >date.
> >> >
> >> >
> >>
> >
> >
>