Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Hauppauge bt878 & LIRC & kernel 2.6 = not working!!
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Multimedia
View previous topic :: View next topic  
Author Message
Lorijho
n00b
n00b


Joined: 22 Jul 2003
Posts: 38
Location: Luxembourg

PostPosted: Wed Jun 02, 2004 9:44 am    Post subject: Hauppauge bt878 & LIRC & kernel 2.6 = not working!! Reply with quote

Hello everybody, getting lirc to work on 2.6 kernel is really a huge pain in the ass! I'm been trying for weeks and I really need some tips or help at this point...

Specifications:
- Hauppauge TV Card with bt878 chip
- gentoo-dev-sources 2.6.5-r1 with UDEV !!
- lirc 0.7.0_pre3

1) Kernel Config

Code:


Device Drivers  --->
|   Character devices  --->
|    |  Linux InfraRed Controller  --->
|    |  |   <M> Linux InfraRed Controller                                                           
|    |  |    (2)   Maximum LIRC devices                                                             
|    |  |   <M>   I2C Driver
|    |  |_
|    |_
|   I2C support  --->
|   |   <M> I2C support                                                                               
|   |   <M> I2C device interface
|   |   I2C Algorithms  --->
|   |   |   <M> I2C PCF 8584 interfaces
|   |   |_
|   | _ 
|   Multimedia devices  --->
|   |   <M> Video For Linux
|   |   Video For Linux  --->
|   |   |   <M> BT848 Video For Linux
|   |   |_
|   |_
|_



2) Load module

Code:

modprobe lirc_i2c


3) dmesg

Code:


lirc_dev: IR Remote Control driver registered, at major 61
Linux video capture interface: v1.00
bttv: driver version 0.9.12 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
PCI: Found IRQ 10 for device 0000:00:10.0
PCI: Sharing IRQ 10 with 0000:00:07.5
PCI: Sharing IRQ 10 with 0000:00:10.1
bttv0: Bt878 (rev 2) at 0000:00:10.0, irq: 10, latency: 64, mmio: 0xdddfe000
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00fffffb [init]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
bttv0: Hauppauge eeprom: model=61294, tuner=Philips FI1216 MK2 (5), radio=no
bttv0: using tuner=5
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
tvaudio: TV audio decoder + audio/video mux driver
tvaudio: known chips: tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54 (PV951),ta8874z
tuner: chip found at addr 0xc2 i2c-bus bt878 #0 [sw]
tuner: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) by bt878 #0 [sw]
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 . ok
lirc_dev: lirc_register_plugin:sample_rate: 6
lirc_dev: lirc_register_plugin:sample_rate: 6



4) lsmod
Code:


Module                  Size  Used by
tuner                  17324  0
tvaudio                20620  0
bttv                  144524  0
video_buf              17028  1 bttv
i2c_algo_bit            8936  1 bttv
v4l2_common             4832  1 bttv
btcx_risc               3848  1 bttv
videodev                7616  1 bttv
lirc_i2c                6788  0
i2c_core               19140  5 tuner,tvaudio,bttv,i2c_algo_bit,lirc_i2c
lirc_dev               11112  3 lirc_i2c
snd_seq_midi            6496  0
snd_via82xx            22240  0
snd_ac97_codec         62500  1 snd_via82xx
snd_mpu401_uart         6144  1 snd_via82xx
snd_rawmidi            20832  2 snd_seq_midi,snd_mpu401_uart
snd_seq_oss            33088  0
snd_seq_midi_event      6080  2 snd_seq_midi,snd_seq_oss
snd_seq                54032  5 snd_seq_midi,snd_seq_oss,snd_seq_midi_event
snd_seq_device          6728  4 snd_seq_midi,snd_rawmidi,snd_seq_oss,snd_seq
nvidia               2071656  0
nls_iso8859_15          4224  0



IMHO this is all like it should be!!

But the lirc modules don't create the /dev nodes /dev/lirc/lirc0 or /dev/lirc0, so upon a "/etc/init.d/lircd start" lircd can't find these entries...

Why does it not create the /dev entries ??

rmmod lirc_i2c gets me this

Code:


Unable to handle kernel paging request at virtual address 0a080101
 printing eip:
c018c296
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU:    0
EIP:    0060:[<c018c296>]    Tainted: PF
EFLAGS: 00010296   (2.6.5-gentoo-r1)
EIP is at sysfs_get_dentry+0x16/0x70
eax: 00000000   ebx: d4d90668   ecx: ffffffff   edx: 0a080101
esi: d4d90600   edi: 0a080101   ebp: d993a780   esp: d3f1be9c
ds: 007b   es: 007b   ss: 0068
Process rmmod (pid: 16554, threadinfo=d3f1a000 task=d4045360)
Stack: 00000001 00000246 0a080101 c0415368 d9a084d0 c0276eeb d4d90668 d711e7c0
       c018c335 d711e7c0 0a080101 d606a070 d99156dc d99156dc c0278308 d711e7c0
       0a080101 2c841600 d9915728 c027837b d606a070 d993a90c d993a8c0 c0278642
Call Trace:
 [<c0276eeb>] device_release+0x5b/0x60
 [<c018c335>] sysfs_hash_and_remove+0x45/0x9c
 [<c0278308>] device_release_driver+0x28/0x70
 [<c027837b>] driver_detach+0x2b/0x40
 [<c0278642>] bus_remove_driver+0x62/0xa0
 [<c0278a4a>] driver_unregister+0x1a/0x47
 [<d9936619>] i2c_del_driver+0xd9/0x1a0 [i2c_core]
 [<d9914ad8>] lirc_i2c_exit+0x18/0x2e [lirc_i2c]
 [<c0135515>] sys_delete_module+0x145/0x1a0
 [<c014b3f9>] sys_munmap+0x59/0x80
 [<c01094ab>] syscall_call+0x7/0xb

Code: f2 ae f7 d1 49 89 4c 24 0c 31 db 89 d7 49 83 f9 ff 74 24 8d



I would really appreciate any tips, hints and general help!
Back to top
View user's profile Send private message
Purrkur
Apprentice
Apprentice


Joined: 16 Jun 2003
Posts: 202
Location: Stockholm

PostPosted: Wed Jun 02, 2004 1:24 pm    Post subject: Reply with quote

You didn't mention what kernel you are running :(

I got myself a remote control for my tv card but I don't use it because I am always sitting right there in front of the controls. Feels sort of useless :)

If you are using a 2.6 kernel then "rmmod" module might not work as expected.

Here are a few things I would check:

1. Have you set the "lirc" USE flag? Might be helpful when compiling stuff...

2. You didn't mention how you are connecting the IR sensor to your computer. Is it a serial connection? I guess you should have "lirc_serial" module as well?

3. Are you sure that udev works with lirc?

Just my .02c worth. Good luck...
_________________
Punk is an attitude
not a fashion style
Back to top
View user's profile Send private message
Lorijho
n00b
n00b


Joined: 22 Jul 2003
Posts: 38
Location: Luxembourg

PostPosted: Wed Jun 02, 2004 10:14 pm    Post subject: Reply with quote

First of all... Thanks for your reply, I appreciate!

The remote control has it's meaning, we are talking about a DVDIVX PC at my place,
I don't work surf play or do anything else on it.

So is there a better (correct) way to unload 2.6 modules, rather then using rmmod?

The lirc USE flag is set, but wheather it is set or not does not affect kernel/module compilation!

The remote is connected to the Hauppauge Wintv (bt878) and the whole config worked just fine under 2.4 kernel with the lirc_i2c module, lirc_serial is of no use for this remote.

AFAIK udev does not support lirc devices yet but i am not sure, i have emerged the latest version avaible in portage -> 025-r1.
Back to top
View user's profile Send private message
lbrtuk
l33t
l33t


Joined: 08 May 2003
Posts: 910

PostPosted: Wed Jun 02, 2004 11:09 pm    Post subject: Reply with quote

Take a look at /usr/src/linux/Documentation/video4linux/README.ir

It seems to imply that in kernel 2.6, bttv IR interfaces are managed by the bttv module itself and work as keyboards.
Back to top
View user's profile Send private message
Purrkur
Apprentice
Apprentice


Joined: 16 Jun 2003
Posts: 202
Location: Stockholm

PostPosted: Thu Jun 03, 2004 7:02 am    Post subject: Reply with quote

Hello Lorijho!

Quote:
So is there a better (correct) way to unload 2.6 modules, rather then using rmmod?


Well, this has changed since 2.4. If you read the information on "module unloading" in the kernel you will find the following:

Quote:
Without this option you will not be able to unload any
modules (note that some modules may not be unloadable
anyway)


Now there is another option called "Forced module unloading" where you will find the following information:

Quote:
This option allows you to force a module to unload, even if the kernel believes it is unsafe.....This is mainly for kernel developers and desperate users.


In other words, it is not a sure thing that you can remove a module that you have loaded.

Quote:
The lirc USE flag is set, but wheather it is set or not does not affect kernel/module compilation!


So true, but it might affect compilation of programs that will use the remote!

I think that the best idea for you would be to read the document suggested by lbrtuk. You could also search through the forums. I checked what searching for "lirc mythtv" would turn up and I got 47 hits. I think many that want to run mythtv are lirc users as well so you might find something to help you there.

Sorry for not being able to help you any better....
_________________
Punk is an attitude
not a fashion style
Back to top
View user's profile Send private message
Maedhros
Bodhisattva
Bodhisattva


Joined: 14 Apr 2004
Posts: 5511
Location: Durham, UK

PostPosted: Thu Jun 03, 2004 10:27 am    Post subject: Re: Hauppauge bt878 & LIRC & kernel 2.6 = not workin Reply with quote

Lorijho wrote:
Specifications:
- Hauppauge TV Card with bt878 chip
- gentoo-dev-sources 2.6.5-r1 with UDEV !!
- lirc 0.7.0_pre3

I think the with UDEV !! line may be the key! :D

While udev is good at the moment, and can only get better, it isn't able to create some entries yet, like my nVidia entries (I'm using AMD64... the drivers are quite ancient, but they're the only ones that compile). I think it may be this is the problem.

Have a look at the gentoo-udev guide: http://www.gentoo.org/doc/en/udev-guide.xml

Hope this helps!
_________________
No-one's more important than the earthworm.
Back to top
View user's profile Send private message
peterton
Tux's lil' helper
Tux's lil' helper


Joined: 20 Aug 2003
Posts: 110

PostPosted: Sat Jun 05, 2004 8:36 pm    Post subject: Reply with quote

Of course you can create the device node by hand:
Code:
mkdir /dev/lirc
mknod --mode=666 /dev/lirc/lirc0 c 61 0
Back to top
View user's profile Send private message
Lorijho
n00b
n00b


Joined: 22 Jul 2003
Posts: 38
Location: Luxembourg

PostPosted: Tue Jun 08, 2004 1:42 pm    Post subject: Reply with quote

UDEV is the key!

I've configured the gentoo-dev-sources-2.6.5-r1 kernel back to the obsolete DEVFS and on modprobing lirc_i2c the devices are created: /dev/lirc/lirc0 /dev/lirc/lirc1.

lircd -n --device=/dev/lirc/lirc0 doesn't work when irw is used to test the remote
lircd -n --device=/dev/lirc/lirc1 does work with irw but only one time, on relaunching irw it doesn't work anymore until the system is rebooted.

So after switching back to UDEV and the devices are created manually

Code:
mkdir /dev/lirc
mknod --mode=666 /dev/lirc/lirc0 c 61 0
mknod --mode=666 /dev/lirc/lirc1 c 61 1

I execute
lircd -n --device=/dev/lirc/lirc1

when I start irw I immediately get this

Code:

Unable to handle kernel paging request at virtual address 63616c6e
 printing eip:
d99a7ef1
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU:    0
EIP:    0060:[<d99a7ef1>]    Tainted: PF
EFLAGS: 00010296   (2.6.5-gentoo-r1)
EIP is at i2c_master_recv+0x11/0xc0 [i2c_core]
eax: d5e52e58   ebx: d5e52e00   ecx: d9922180   edx: d5e52e58
esi: 63616c62   edi: 00000003   ebp: d7309c80   esp: d5cfff6c
ds: 007b   es: 007b   ss: 0068
Process lirc_dev (pid: 6723, threadinfo=d5cfe000 task=d5d117c0)
Stack: 00000000 d5cfffa4 000000c3 cb52a32b 00000035 d5d11980 fffe6a5d d5e52e00
       00000000 00000003 d99221ab d5e52e58 d5cfffac 00000003 00100100 00200200
       fffe6a5d 4b87ad6e c0128b90 d5d117c0 d99afaf4 00000000 ffffffc3 00000000
Call Trace:
 [<d99221ab>] add_to_buf_haup+0x2b/0x170 [lirc_i2c]
 [<c0128b90>] process_timeout+0x0/0x10
 [<d99ad15c>] lirc_thread+0x15c/0x200 [lirc_dev]
 [<d99ad000>] lirc_thread+0x0/0x200 [lirc_dev]
 [<c01072ad>] kernel_thread_helper+0x5/0x18

Code: 8b 46 0c 8b 48 24 85 c9 74 7a 0f b7 42 08 8d 5e 1c 66 89 44


This is really strange.
Even if I use the obsolete devfs, LIRC doesn't work like it should....
IMHO the lirc source in 2.6.5 is buggy!
UDEV (0.26-r1) has no LIRC support!
Back to top
View user's profile Send private message
Sipi
Guru
Guru


Joined: 03 Apr 2003
Posts: 406
Location: Hungary

PostPosted: Tue Jun 08, 2004 1:54 pm    Post subject: Reply with quote

Yes, I found it, too. 2.6.5 sources has some problem with lirc (and with bttv module, too).
I use gentoo-dev-sources-2.6.4-r1 without any problem with devfs. Didn't try udev yet (but I don't want to try it, anyway :) ).

Sipi
Back to top
View user's profile Send private message
Lorijho
n00b
n00b


Joined: 22 Jul 2003
Posts: 38
Location: Luxembourg

PostPosted: Tue Jun 08, 2004 2:15 pm    Post subject: Reply with quote

Sipi wrote
Quote:

Yes, I found it, too. 2.6.5 sources has some problem with lirc (and with bttv module, too).
I use gentoo-dev-sources-2.6.4-r1 without any problem with devfs. Didn't try udev yet (but I don't want to try it, anyway ).


I will try gentoo-dev-sources-2.6.4-r1 and hope that this will be fixed in future kernel releases!
What is the place to report this bug anyway ?
Back to top
View user's profile Send private message
Sipi
Guru
Guru


Joined: 03 Apr 2003
Posts: 406
Location: Hungary

PostPosted: Tue Jun 08, 2004 2:18 pm    Post subject: Reply with quote

bugs.gentoo.org

Sipi
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2767
Location: Pittsburgh, PA, USA

PostPosted: Tue Jun 08, 2004 4:48 pm    Post subject: Reply with quote

I have been in the same mess as you with lirc. I have been trying to get it working on my hauppage card and many 2.4 and 2.6 kernels and it has been one problem or another. Here is a link to my thread http://forums.gentoo.org/viewtopic.php?t=182772.


I have never gotten irw to work even once. However in several different configurations I was able to cat /dev/lirc/0 and get data, well at least on the first try... I have some questions. When you had irw working the first time did it say connection refused on the second go? Did you check the process list to see if lircd was still running the second time. During my testing the problem I was having was that irw crashed lirc. There were two ways that I could bring lircd up again after a crash was to run it from the console
Code:
/usr/sbin/lircd --device /dev/lirc/0


The other was to
Code:
modprobe -r lirc_i2c
modprobe lirc_i2c

_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
Lorijho
n00b
n00b


Joined: 22 Jul 2003
Posts: 38
Location: Luxembourg

PostPosted: Wed Jun 09, 2004 1:41 am    Post subject: Reply with quote

Solved!!

First...

UDEV (<= 0.26-r1) & LIRC do not work together, that's why i won't use it until lirc has found its into udev. If someone has a found a hack, PLEASE let us know!!

Until then...

After browsing bugs.gentoo.org I found the right hack to get LIRC (lirc_i2c) to work, all the time, using gentoo-dev-sources-2.6.5-r1and DEVFS!

1) Have a look at the bug report.

http://bugs.gentoo.org/show_bug.cgi?id=47404

2) You'll have to replace the lirc patch in gentoo-dev-sources-2.6.5-r1, which is obviously buggy, with the gentoo-dev-sources-2.6.4-r1 lirc patch which was modified to work with 2.6.5 .

Patch:
http://bugs.gentoo.org/attachment.cgi?id=29379&action=view

Save the patch as 4105_lirc_infrared-2.6.2_rc1-01242004.patch.

3) Delete 4105_lirc_infrared-2.6.5-rc2.patch from genpatches-2.6-5.29-extras.tar.bz2 after extracting it. Then tar cjvf genpatches-2.6-5.29 genpatches-2.6-5.29-extras.tar.bz2 after putting 4105_lirc_infrared-2.6.2_rc1-01242004.patch in it.

4) Re-digest the ebuild to re-emerge it.
ebuild /usr/portage/sys-kernel/gentoo-dev-sources/gentoo-dev-sources-2.6.5-r1.ebuild digest . Now emerge gentoo-dev-sources.

5) Recompile kernel & modules, reboot and you have working LIRC modules. At least I have them now! Lirc clients (e.g. irw) now work more the one single time.

We learned that the gentoo-dev-source-2.6.4-r1 patch-set isn't buggy, so people who are feeling uncomfortable at modifying 2.6.5-r1 have to downgrade to, or keep, 2.6.4.

It would be great to see future releases without this bug...
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2767
Location: Pittsburgh, PA, USA

PostPosted: Wed Jun 09, 2004 2:33 am    Post subject: Reply with quote

Thank You. I will try that when I get a chance.
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
sklettke
Guru
Guru


Joined: 05 Nov 2002
Posts: 352
Location: Madison, WI

PostPosted: Wed Jun 09, 2004 10:14 pm    Post subject: Reply with quote

I really hope to get reiser4 working so I'm trying to get lirc to work in 2.6.5-lokean2.

I have the ivtv modules loaded correctly as well as lirc_dev and lirc_i2c.

My dmesg output:
Code:
lirc_dev: IR Remote Control driver registered, at major 61


If I run /etc/init.d/lircd start, it starts correctly, but when I try irw, it gives this message:
Code:
lircd 0.7.0pre4[31620]: lircd(hauppauge) ready
lircd 0.7.0pre4[31620]: accepted new client on /dev/lircd
lircd 0.7.0pre4[31620]: could not open /dev/lirc/lirc0
lircd 0.7.0pre4[31620]: default_init(): No such device
lircd 0.7.0pre4[31620]: caught signal
Terminated


I've checked and there is no /dev/lirc/lirc0. However, if I start lircd manually with /usr/sbin/lircd -n -d /dev/lircd, I get this message after connecting with irw:
Code:
lircd 0.7.0pre4[31634]: lircd(hauppauge) ready
lircd 0.7.0pre4[31634]: accepted new client on /dev/lircd
lircd 0.7.0pre4[31634]: accepted new client on /dev/lircd

and then when I stop irw I get this message:
Code:
lircd 0.7.0pre4[31634]: removed client


I have copied the lircd-g.conf from the ivtv/utils directory into /etc/lircd.conf, however, this is the output I get from pushing the buttons 1 2 2 2:
Code:
^[[F^[[B^[[B^[[B


Only the numbered buttons give these control codes; none of the other buttons do anything.

I'm running the 2.6.5-lokean2 kernel with the 2.6.5-rc2 lirc patch. Any suggestions on why the lirc0 isn't being created?

Thanks.
Scott
_________________
Jab.ID: scottk@jabber.org

Kernel: 2.6.11-rc3-nitro0
KDE 3.3.2 with Xorg
MythBox: 2.6.5-gentoo-dev-r2 (LVMed 360GB in XFS; Athlon 2500+)
Back to top
View user's profile Send private message
Lorijho
n00b
n00b


Joined: 22 Jul 2003
Posts: 38
Location: Luxembourg

PostPosted: Thu Jun 10, 2004 12:05 am    Post subject: Reply with quote

The LIRC kernel modules gave me headaches!!

So thanks to lbrtuk for the advice! :idea:

I've tried the v4l2 drivers which include remote control modules, ir-kbd-i2c works great and everything was setup in about an hour.

v4l2 drivers FAQ


Last edited by Lorijho on Thu Jun 10, 2004 12:28 am; edited 1 time in total
Back to top
View user's profile Send private message
Lorijho
n00b
n00b


Joined: 22 Jul 2003
Posts: 38
Location: Luxembourg

PostPosted: Thu Jun 10, 2004 12:14 am    Post subject: Reply with quote

@ sklettke

Check /etc/conf.d/lircd, you'll find the variable LIRC_OPTS, set it to "-H hauppauge --device=/dev/lirc/lirc0" or lirc1.

Code:
 /usr/sbin/lircd -n -d /dev/lircd
cannot work, in fact /dev/lircd will be created by when lircd is fired up for the first time! You must point lircd to a device created by the Kernel. 2.6 lirc modules use /dev/lirc/lircX as devices.


UDEV doesn't create lirc devices yet, so that might be the reason if you're using udev.
Back to top
View user's profile Send private message
sklettke
Guru
Guru


Joined: 05 Nov 2002
Posts: 352
Location: Madison, WI

PostPosted: Thu Jun 10, 2004 2:06 am    Post subject: Reply with quote

Thanks, but the /etc/conf.d/lircd is set up correctly. The problem is that the kernel does not create any devices. I'm compiling 2.6.5-lokean2 with the older 2.6.2 lirc patch and seeing if that will work.

To get the kernel to create the devices you just have to load the modules, correct?
Code:
modprobe lirc_dev
modprobe lirc_i2c


If these don't work I'm going to try compiling the lirc stuff into the kernel.

Scott
_________________
Jab.ID: scottk@jabber.org

Kernel: 2.6.11-rc3-nitro0
KDE 3.3.2 with Xorg
MythBox: 2.6.5-gentoo-dev-r2 (LVMed 360GB in XFS; Athlon 2500+)
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2767
Location: Pittsburgh, PA, USA

PostPosted: Thu Jun 10, 2004 9:16 am    Post subject: Reply with quote

Thank You! It worked... I finally got lirc working with 2.6.4-gentoo. MythTV would not use the remote but I was able to get irxevent do to the job for me by editing the .lircrc file... Now I can try to see if I can get my XTASY Veverything card working so I can record and watch at the same time...
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
sklettke
Guru
Guru


Joined: 05 Nov 2002
Posts: 352
Location: Madison, WI

PostPosted: Fri Jun 11, 2004 5:10 pm    Post subject: Reply with quote

Still doesn't work for me yet. The only time that I got lirc working was using gentoo-dev-sources-2.6.5-r1 (the original, without the old lirc patched in). I was unable to get ivtv to work but at least lirc was working. I've gone back to that source but have not gotten lirc working since. Besides the lirc modules and the i2c modules, are there any other modules that need to be compiled for it to work? Besides when I was first installing the kernel (and following the MythTV how to directions), I have not been able to get any /dev/lirc/0, etc, etc, formed.

Thanks.
Scott
_________________
Jab.ID: scottk@jabber.org

Kernel: 2.6.11-rc3-nitro0
KDE 3.3.2 with Xorg
MythBox: 2.6.5-gentoo-dev-r2 (LVMed 360GB in XFS; Athlon 2500+)
Back to top
View user's profile Send private message
Lorijho
n00b
n00b


Joined: 22 Jul 2003
Posts: 38
Location: Luxembourg

PostPosted: Sun Jun 13, 2004 12:10 pm    Post subject: Reply with quote

@ sklettke

If you are using the following Hauppauge remote...
http://www.hauppauge.de/images/remote.jpg
I would suggest you to try the v4l2 remote drivers which are part of 2.6 kernel.

Read my mini howto on this...
http://forums.gentoo.org/viewtopic.php?t=185124
Back to top
View user's profile Send private message
sklettke
Guru
Guru


Joined: 05 Nov 2002
Posts: 352
Location: Madison, WI

PostPosted: Mon Jun 14, 2004 2:05 am    Post subject: Reply with quote

Thanks for your help. I'm now trying to get the Sony IR Receiver to work instead, but have ran into a little trouble there as well: http://forums.gentoo.org/viewtopic.php?p=1238937#1238937

Scott
_________________
Jab.ID: scottk@jabber.org

Kernel: 2.6.11-rc3-nitro0
KDE 3.3.2 with Xorg
MythBox: 2.6.5-gentoo-dev-r2 (LVMed 360GB in XFS; Athlon 2500+)
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2767
Location: Pittsburgh, PA, USA

PostPosted: Mon Jun 14, 2004 3:34 am    Post subject: Reply with quote

In 2.6.4-gentoo sources I have compiled it with lirc support and the bttv driver and all the i2c drivers and emerged ivtv with ~x86 keword and lirc version app-misc/lirc-0.7.0_pre3. I just used the ebuilds for both lirc and ivtv and did not compile them myself.
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
sklettke
Guru
Guru


Joined: 05 Nov 2002
Posts: 352
Location: Madison, WI

PostPosted: Mon Jun 14, 2004 9:23 pm    Post subject: Reply with quote

WOOHOO!!! Finally got the grey pvr-250 remote working; and it even works in MythTV!!!

This is what I did:

1) Follow Lorijho's excellent instructions (below) and the drunkentiger's MythTV guide
2) Download the 0.1.9 release of IVTV (or copy from /usr/portage/distfiles) and patch with https://www.lison.com/ivtv.patches/ivtv-0.1.9-2.6-3-20040206.diff from (from https://www.lison.com/ivtv.patches/
*** There is an error in the 2.6.5 lircd patch (irw only works once and then not until rebooting) and for me only the 0.1.9 patched IVTV works (note: haven't tried the 2.6.4 patch, but 2.6.3 patches successfully to gentoo-dev-sources 2.6.5-r1) ***
3) Compile the neccessary i2c modules, etc into the kernel and then reboot into it
4) as root, patch ivtv (from the parent directory of the ivtv directory)
Code:
patch < ivtv-0.1.9-2.6-3-20040206.diff -p0 --dry-run (then remove --dry-run when ready)

5) as root, extract the pvr-250 firmware in the utils directory and then compile ivtv
6) modprobe ivtv (this will load ivtv and the lirc-dev and lirc-i2c modules necessary for remote operation)
7) type cat /dev/video0 to see if it is created (upon loading of ivtv); if so, you're good for video
8- run dmesg and look for remarks regarding the remote control
9) make sure your /etc/conf.d/lircd contains "LIRCD_OPTS="-d /dev/lirc/lirc0"
10) copy lircd-g.conf (for grey remote) to /etc/lircd.conf
11) run /etc/init.d/lircd stop and then /etc/init.d/lircd start (to make sure it uses new config)
12) run irw and push some buttons on the remote

I am SO glad that I finally got this working! Thanks for the help everyone!

I am now going to try this same patched ivtv with a kernel that is patched with reiser4, but if that doesn't work I can always resort to XFS or ReiserFS for the file system.

Scott
_________________
Jab.ID: scottk@jabber.org

Kernel: 2.6.11-rc3-nitro0
KDE 3.3.2 with Xorg
MythBox: 2.6.5-gentoo-dev-r2 (LVMed 360GB in XFS; Athlon 2500+)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Multimedia All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum