LinHES Forums
http://forum.linhes.org/

2 Problems.. hauppauge 500
http://forum.linhes.org/viewtopic.php?f=2&t=7194		 Page 1 of 2
Author:  madsholme [ Sat Dec 03, 2005 2:20 pm ]
Post subject:  2 Problems.. hauppauge 500
Hi

Bought a hauppauge 500 to fit in my Via C3 board.

I did the install, and under the setup i give it /dev/video0 and /dev/video3 as the devices it should use, and under card type i select -250-350 mpeg card...

when i am about to search for channels i get a error that says:

Code:
cant open video0 to probe its inputs


1:
How do i see if it has found my hauppauge 500, and see what devices it should use?

2:
In order to get a remote, i bought a usb irda device, how can i see if its working or found ?

3:
i Bought a logitech harmony 525 remote, is it possible to get that to work with myth ?
Author:  ryanpatterson [ Sat Dec 03, 2005 4:41 pm ]
Post subject: 
use:
Code:
dmesg |grep ivtv

That should tell you if the ivtv driver was able to find the tuners on your card.

Is the pvr-500 the only tuner in your system? If so the tuners should be video0 and video1. Why are you tring video3?

There are some commandline utilities to tune the card to a channel and capture a .mpeg file to test the driver and which device you should use. I don't know them off the top of my head. Check the wiki or maybe somebody will post the commands.

Can't help with your other questions.
Author:  acosgrove [ Sat Dec 03, 2005 4:48 pm ]
Post subject:  Hauppauge pvr-500
The pvr-500 will use /dev/video0 and /dev/video1 unless you've got other video devices in there (other tv cards, usb video cameras, etc.)

What version of knoppmyth are you using? I'm on R5A22 and the 500 worked right out of a fresh install.

1. Ryan beat me to it - after typing that in you should get something to the effect of

Code:
ivtv:  ==================== START INIT IVTV ====================
.
.
.
ivtv:  ====================  END INIT IVTV  ====================


2. I'm not too good at the remotes part but you will need to make sure that linux detected your device on the usb port

Again another dmesg will let you know

Code:
dmesg | grep usb


You should see the device identification if everything goes good. If you get unknown device then you may have to go searching long and hard for drivers that may not exist.

3. My weak point - I'm useless as tits on a bull here... someone else might have an answer for you. Try the search function
Author:  tjc [ Sat Dec 03, 2005 4:48 pm ]
Post subject: 
I finally broke down and gathered a bunch of the information on using the log files to diagnose these problems in a single place on the wiki.
http://www.knoppmythwiki.org/index.php?page=CheckingLogFiles
Author:  madsholme [ Sat Dec 03, 2005 4:49 pm ]
Post subject: 
ryanpatterson wrote:
use:
Code:
dmesg |grep ivtv

That should tell you if the ivtv driver was able to find the tuners on your card.

Is the pvr-500 the only tuner in your system? If so the tuners should be video0 and video1. Why are you tring video3?

There are some commandline utilities to tune the card to a channel and capture a .mpeg file to test the driver and which device you should use. I don't know them off the top of my head. Check the wiki or maybe somebody will post the commands.

Can't help with your other questions.


Alright it used lspci and i can see it has found my card..

Now when i set it up under i select:

/dev/video0 and /dev/video2 (the 3 was a typo)
and tunero and tuner1

i then go down to:

input connections, and it just says NONE whit em all? i have put my cable to the tv card, and the same cable is working just fine in my tv.

and yes the 500 card is the only card in my system.. the via c3 board i am using only got one slot :)



Code:
root@mythtv:~# dmesg | grep ivtv
ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.4.0 (tagged release) loading
ivtv:  Linux version: 2.6.13.2-chw-3 SMP preempt 586 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.
ivtv0: Autodetected WinTV PVR 150 card (iTVC16 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom: ivtv version
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc0 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=60]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
ivtv0: This is the first unit of a PVR500
cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
tda9885/6/7: (ivtv) chip found @ 0x86
ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43]
ivtv0: Detected a TEA5767 radio tuner. Enabling radio support.
ivtv0: loading /lib/modules/ivtv-fw-enc.bin
ivtv0: Encoder revision: 0x02040011
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
ivtv0: Create encoder radio stream
tuner: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4)) by ivtv i2c driver #0
ivtv0: Initialized WinTV PVR 500 (unit #1), card #0
ivtv:  ======================  NEXT CARD  ======================
ivtv1: Autodetected WinTV PVR 150 card (iTVC16 based)
ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom: ivtv version
ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #1
ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61]
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
ivtv1: i2c attach to card #1 ok [client=cx25840, addr=44]
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
ivtv1: i2c attach to card #1 ok [client=wm8775, addr=1b]
tda9885/6/7: (ivtv) chip found @ 0x86
ivtv1: i2c attach to card #1 ok [client=tda9887, addr=43]
ivtv1: This is the second unit of a PVR500
ivtv1: Correcting tveeprom data: no radio present on second unit
ivtv1: loading /lib/modules/ivtv-fw-enc.bin
ivtv1: Encoder revision: 0x02040011
ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv1: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
ivtv1: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4)) by ivtv i2c driver #1
ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
ivtv:  ====================  END INIT IVTV  ====================
Author:  madsholme [ Sat Dec 03, 2005 4:54 pm ]
Post subject:  Re: Hauppauge pvr-500
acosgrove wrote:
The pvr-500 will use /dev/video0 and /dev/video1 unless you've got other video devices in there (other tv cards, usb video cameras, etc.)

What version of knoppmyth are you using? I'm on R5A22 and the 500 worked right out of a fresh install.




Using: R5a26



Code:
root@mythtv:~# dmesg | grep usb
usbcore: registered new driver usbfs
usbcore: registered new driver hub
usb 1-2: new full speed USB device using uhci_hcd and address 2
usb 2-1: new low speed USB device using uhci_hcd and address 2
usbcore: registered new driver usb-storage
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
drivers/usb/serial/usb-serial.c: USB Serial support registered for PL-2303
usb 1-2: PL-2303 converter now attached to ttyUSB0
usbcore: registered new driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.12
usbcore: registered new driver hiddev
input: USB HID v1.10 Mouse [Razer Razer Diamondback Optical Mouse] on usb-0000:00:10.1-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
usbcore: registered new driver ttusb
usbcore: registered new driver ttusb-dec
usb 1-2: USB disconnect, address 2
usb 2-1: USB disconnect, address 2
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: PL-2303 converter now attached to ttyUSB0
usb 2-1: new low speed USB device using uhci_hcd and address 3
input: USB HID v1.10 Mouse [Razer Razer Diamondback Optical Mouse] on usb-0000:00:10.1-1
root@mythtv:~#


Cant see anything in there with Irda.. does any know where you can get a irda device that works whit Linux? Either USB or the ones to fit on your mother boards (that i can never find)
Author:  acosgrove [ Sat Dec 03, 2005 5:08 pm ]
Post subject:  Irda
Ok pull your ir device out and note which address shows a disconnect... I'm suspecting it may be that prolific PL203.... (I'm guessing here so I may be wrong)

If it is then it may be a matter of telling lirc to use ttyusb0 as its input. You'll need to play with the lirc daemons to test. I was fiddling around with lirc a few weeks back but I can't recall the name of the binary that will spit out what your remote is sending.

Back to the 500: did you get your devices straight? The input connections should have a nice healthy listing.
Author:  mcdrama [ Sat Dec 03, 2005 5:16 pm ]
Post subject:  Re: 2 Problems.. hauppauge 500
madsholme wrote:
Hi

Bought a hauppauge 500 to fit in my Via C3 board.

I did the install, and under the setup i give it /dev/video0 and /dev/video3 as the devices it should use, and under card type i select -250-350 mpeg card...

when i am about to search for channels i get a error that says:

Code:
cant open video0 to probe its inputs


1:
How do i see if it has found my hauppauge 500, and see what devices it should use?

2:
In order to get a remote, i bought a usb irda device, how can i see if its working or found ?

3:
i Bought a logitech harmony 525 remote, is it possible to get that to work with myth ?


1:
from a command prompt run dmesg and look for this line:
ivtv: ==================== START INIT IVTV ====================

This will tell you if the card was detected when loadind the driver.


2:
dmesg | grep USB
dmesg | more
just look for the device name.


3:
possible? Most likely.
It will require some tinkering with your lircd.conf though.


I would google search the USB irda device and remote though, you will most likely get better results via google then here since those are both more linux related questions.
Author:  madsholme [ Sat Dec 03, 2005 5:20 pm ]
Post subject:  Re: Irda
acosgrove wrote:
Ok pull your ir device out and note which address shows a disconnect... I'm suspecting it may be that prolific PL203.... (I'm guessing here so I may be wrong)

If it is then it may be a matter of telling lirc to use ttyusb0 as its input. You'll need to play with the lirc daemons to test. I was fiddling around with lirc a few weeks back but I can't recall the name of the binary that will spit out what your remote is sending.

Back to the 500: did you get your devices straight? The input connections should have a nice healthy listing.


Alright this is how i did the setup:

Code:
Card Type - Meg2 encoder card (PVR-250, Pvr350)
Video device: /dev/video0
Default Input: Tuner 0

Card Type - Meg2 encoder card (PVR-250, Pvr350)
Video device: /dev/video1
Default Input: Tuner 1


also here is the dmesg with out the usb irda device in.


Code:
root@mythtv:~# dmesg | grep usb
usbcore: registered new driver usbfs
usbcore: registered new driver hub
usb 1-2: new full speed USB device using uhci_hcd and address 2
usb 2-1: new low speed USB device using uhci_hcd and address 2
usbcore: registered new driver usb-storage
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
drivers/usb/serial/usb-serial.c: USB Serial support registered for PL-2303
usb 1-2: PL-2303 converter now attached to ttyUSB0
usbcore: registered new driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.12
usbcore: registered new driver hiddev
input: USB HID v1.10 Mouse [Razer Razer Diamondback Optical Mouse] on usb-0000:00:10.1-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
usbcore: registered new driver ttusb
usbcore: registered new driver ttusb-dec
usb 1-2: USB disconnect, address 2
usb 2-1: USB disconnect, address 2
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: PL-2303 converter now attached to ttyUSB0
usb 2-1: new low speed USB device using uhci_hcd and address 3
input: USB HID v1.10 Mouse [Razer Razer Diamondback Optical Mouse] on usb-0000:00:10.1-1
usb 1-2: USB disconnect, address 3
usb 1-1: new full speed USB device using uhci_hcd and address 4
usb 1-1: PL-2303 converter now attached to ttyUSB0
usb 1-1: USB disconnect, address 4
root@mythtv:~#
Author:  mcdrama [ Sat Dec 03, 2005 5:26 pm ]
Post subject: 
what is the output of dmesg | grep ivtv ?
Author:  madsholme [ Sat Dec 03, 2005 5:29 pm ]
Post subject: 
mcdrama wrote:
what is the output of dmesg | grep ivtv ?


it is:


Code:
root@mythtv:~# dmesg | grep usb
usbcore: registered new driver usbfs
usbcore: registered new driver hub
usb 1-2: new full speed USB device using uhci_hcd and address 2
usb 2-1: new low speed USB device using uhci_hcd and address 2
usbcore: registered new driver usb-storage
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
drivers/usb/serial/usb-serial.c: USB Serial support registered for PL-2303
usb 1-2: PL-2303 converter now attached to ttyUSB0
usbcore: registered new driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.12
usbcore: registered new driver hiddev
input: USB HID v1.10 Mouse [Razer Razer Diamondback Optical Mouse] on usb-0000:00:10.1-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
usbcore: registered new driver ttusb
usbcore: registered new driver ttusb-dec
usb 1-2: USB disconnect, address 2
usb 2-1: USB disconnect, address 2
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: PL-2303 converter now attached to ttyUSB0
usb 2-1: new low speed USB device using uhci_hcd and address 3
input: USB HID v1.10 Mouse [Razer Razer Diamondback Optical Mouse] on usb-0000:00:10.1-1
usb 1-2: USB disconnect, address 3
usb 1-1: new full speed USB device using uhci_hcd and address 4
usb 1-1: PL-2303 converter now attached to ttyUSB0
usb 1-1: USB disconnect, address 4
root@mythtv:~#
root@mythtv:~# dmesg | grep usb
usbcore: registered new driver usbfs
usbcore: registered new driver hub
usb 1-2: new full speed USB device using uhci_hcd and address 2
usb 2-1: new low speed USB device using uhci_hcd and address 2
usbcore: registered new driver usb-storage
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
drivers/usb/serial/usb-serial.c: USB Serial support registered for PL-2303
usb 1-2: PL-2303 converter now attached to ttyUSB0
usbcore: registered new driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.12
usbcore: registered new driver hiddev
input: USB HID v1.10 Mouse [Razer Razer Diamondback Optical Mouse] on usb-0000:00:10.1-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
usbcore: registered new driver ttusb
usbcore: registered new driver ttusb-dec
usb 1-2: USB disconnect, address 2
usb 2-1: USB disconnect, address 2
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: PL-2303 converter now attached to ttyUSB0
usb 2-1: new low speed USB device using uhci_hcd and address 3
input: USB HID v1.10 Mouse [Razer Razer Diamondback Optical Mouse] on usb-0000:00:10.1-1
usb 1-2: USB disconnect, address 3
usb 1-1: new full speed USB device using uhci_hcd and address 4
usb 1-1: PL-2303 converter now attached to ttyUSB0
usb 1-1: USB disconnect, address 4
usb 1-1: new full speed USB device using uhci_hcd and address 5
usb 1-1: PL-2303 converter now attached to ttyUSB0
root@mythtv:~# dmesg | grep ivtv
ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.4.0 (tagged release) loading
ivtv:  Linux version: 2.6.13.2-chw-3 SMP preempt 586 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.
ivtv0: Autodetected WinTV PVR 150 card (iTVC16 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom: ivtv version
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc0 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=60]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
ivtv0: This is the first unit of a PVR500
cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
tda9885/6/7: (ivtv) chip found @ 0x86
ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43]
ivtv0: Detected a TEA5767 radio tuner. Enabling radio support.
ivtv0: loading /lib/modules/ivtv-fw-enc.bin
ivtv0: Encoder revision: 0x02040011
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
ivtv0: Create encoder radio stream
tuner: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4)) by ivtv i2c driver #0
ivtv0: Initialized WinTV PVR 500 (unit #1), card #0
ivtv:  ======================  NEXT CARD  ======================
ivtv1: Autodetected WinTV PVR 150 card (iTVC16 based)
ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom: ivtv version
ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #1
ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61]
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
ivtv1: i2c attach to card #1 ok [client=cx25840, addr=44]
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
ivtv1: i2c attach to card #1 ok [client=wm8775, addr=1b]
tda9885/6/7: (ivtv) chip found @ 0x86
ivtv1: i2c attach to card #1 ok [client=tda9887, addr=43]
ivtv1: This is the second unit of a PVR500
ivtv1: Correcting tveeprom data: no radio present on second unit
ivtv1: loading /lib/modules/ivtv-fw-enc.bin
ivtv1: Encoder revision: 0x02040011
ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv1: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
ivtv1: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4)) by ivtv i2c driver #1
ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
ivtv:  ====================  END INIT IVTV  ====================
root@mythtv:~#


so it seems the card is found
Author:  tjc [ Sat Dec 03, 2005 5:33 pm ]
Post subject: 
mcdrama wrote:
what is the output of dmesg | grep ivtv ?

Please use the sed command from the wiki page instead, the results are more complete. For example here is the information that would be missing from mine:
Code:
root@black2:~# sed -n '/= START INIT IVTV/,/=  END INIT IVTV/p' </var/log/dmesg | sed /ivtv/d
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 21
msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Oct  9 2005 22:52:16
tveeprom: Hauppauge: model = 32032, rev = B310, serial# = 6984053
tveeprom: tuner = Philips FI1236 MK2 (idx = 10, type = 2)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = MSP4448 (type = 1b)
tveeprom: decoder processor = SAA7115 (type = 13)
ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 18
tveeprom: Hauppauge: model = 26032, rev = C199, serial# = 8163083
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)
cx25840 3-0044: loaded /lib/modules/HcwMakoA.ROM firmware (14264 bytes)

NOTE!!! The example above is NOT the command to use unless you strip off the second chunk of sed that deletes all the ivtv stuff!!!
Author:  mcdrama [ Sat Dec 03, 2005 5:35 pm ]
Post subject: 
sorry, got a little confused, didn't see all the posts up above from tjc, and acosgrove.
I wrote my response and forgot to click submit. :x
Author:  madsholme [ Sat Dec 03, 2005 5:43 pm ]
Post subject: 
tjc wrote:
mcdrama wrote:
what is the output of dmesg | grep ivtv ?

Please use the sed command from the wiki page instead, the results are more complete. For example here is the information that would be missing from mine:
Code:
root@black2:~# sed -n '/= START INIT IVTV/,/=  END INIT IVTV/p' </var/log/dmesg | sed /ivtv/d
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 21
msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Oct  9 2005 22:52:16
tveeprom: Hauppauge: model = 32032, rev = B310, serial# = 6984053
tveeprom: tuner = Philips FI1236 MK2 (idx = 10, type = 2)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = MSP4448 (type = 1b)
tveeprom: decoder processor = SAA7115 (type = 13)
ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 18
tveeprom: Hauppauge: model = 26032, rev = C199, serial# = 8163083
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)
cx25840 3-0044: loaded /lib/modules/HcwMakoA.ROM firmware (14264 bytes)

NOTE!!! The example above is NOT the command to use unless you strip off the second chunk of sed that deletes all the ivtv stuff!!!


Isent this the correct command to use?

Code:
sed -n '/= START INIT IVTV/,/=  END INIT IVTV/p' </var/log/dmesg | more


if so i get no output from it
Author:  acosgrove [ Sat Dec 03, 2005 5:51 pm ]
Post subject:  USB info
Code:
<snip>
usb 1-2: PL-2303 converter now attached to ttyUSB0
usbcore: registered new driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.12
usbcore: registered new driver hiddev
input: USB HID v1.10 Mouse [Razer Razer Diamondback Optical Mouse] on usb-0000:00:10.1-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
usbcore: registered new driver ttusb
usbcore: registered new driver ttusb-dec
usb 1-2: USB disconnect, address 2
usb 2-1: USB disconnect, address 2
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: PL-2303 converter now attached to ttyUSB0
usb 2-1: new low speed USB device using uhci_hcd and address 3
input: USB HID v1.10 Mouse [Razer Razer Diamondback Optical Mouse] on usb-0000:00:10.1-1
usb 1-2: USB disconnect, address 3
usb 1-1: new full speed USB device using uhci_hcd and address 4
usb 1-1: PL-2303 converter now attached to ttyUSB0
usb 1-1: USB disconnect, address 4
usb 1-1: new full speed USB device using uhci_hcd and address 5
usb 1-1: PL-2303 converter now attached to ttyUSB0
</snip>


Ok so your device is just a usb -> serial and linux recognizes it as a serial device. This should make life a little easier for you. Now just tweak lirc to use ttyUSB0 for input instead of ttyS0 or ttyS1.

Next best stop for you would be the knoppmythwiki. Take a look at this article -> LIRCHowTo

You shouldn't have to recompile lirc but only tweak the configs to look at the right device and then a little session with irrecord so you can bind the right keys to that logitech remote of yours.

Hit me up on yahoo - If you wanna do a remote session I'll see if I can get that 500 going for you - yahoo IM = ancosgrove
Page 1 of 2 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/