[mythtv-users] Another PVR-250 IR failure

[Max]

I knew this was my own stupidity, just did not know what that stupidity was. Now I know. 

Here is a tip for successfull use of LIRC with PVR250 - make sure your /dev/lirc is the right device. I discovered mine was a symlink to serial port instead of a character device 61,0 (which is what lirc module expects) Also, for whatever reason starting lirc via the init script  that came with it does not seem to work(lircd starts, yet dies shortly after), however starting it manually works just fine. Will need to investigate that.

Now anyone know of a decent RC5 device code I can use instead of the silly useless hauppage remote?  I got the black one, and it IS pretty useless.

-M

  ----- Original Message ----- 
  From: Max 
  To: Discussion about mythtv 
  Sent: Sunday, June 15, 2003 11:44 PM
  Subject: [mythtv-users] Another PVR-250 IR failure


  Ok, I am not sure what I am doing wrong, but I followed the instructions for installing myth on RH9 posted here, and everything so far seems to work, but I cannot for my life get a peep out of my remote (the old black one)

  I got the latest CVS version of everything, including lirc. I used lircd.conf file from ivtv, I even tested my remote with a camcorder to make sure it is actually sending ir codes.

  modules load and lirc starts no problems (it IS trying to load bttv.o for whatever reason and failing)
  but when I run irw, i get nothing (no errors, no messages)

  here is what is in the /var/log/messages:
  -----------------------------------
  Jun 15 22:11:31 watcher kernel: lirc_dev: IR Remote Control driver registered, at major 61
  Jun 15 22:11:35 watcher kernel: bttv: driver version 0.7.104 loaded
  Jun 15 22:11:35 watcher kernel: bttv: using 4 buffers with 2080k (8320k total) for capture
  Jun 15 22:11:35 watcher kernel: bttv: Host bridge is Intel Corp. 82845G/GL [Brookdale-G] Chipset Host Bridge
  Jun 15 22:11:35 watcher insmod: /lib/modules/2.4.20-18.9.2atrpms/kernel/drivers/media/video/bttv.o: init_module: No such device
  Jun 15 22:11:35 watcher insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
  Jun 15 22:11:35 watcher insmod: /lib/modules/2.4.20-18.9.2atrpms/kernel/drivers/media/video/bttv.o: insmod bttv failed
  Jun 15 22:11:35 watcher modprobe: modprobe: Can't locate module rivatv
  Jun 15 22:11:35 watcher kernel: lirc_i2c: chip found @ 0x18 (Hauppauge IR)
  Jun 15 22:11:35 watcher kernel: lirc_dev: lirc_register_plugin:sample_rate: 10
  -----------------------------------

  Someone suggested using irrecord, but if I run it I get:

  ------------------------------------
  [root at watcher daemons]# ./irrecord -v
  irrecord 0.5
  [root at watcher daemons]# ./irrecord pvr.conf

  irrecord -  application for recording IR-codes for usage with lirc

  Copyright (C) 1998,1999 Christoph Bartelmus(lirc at bartelmus.de)

  ./irrecord: could not get hardware features
  ./irrecord: this device driver does not support the new LIRC interface
  ./irrecord: make sure you use a current version of the driver
  ./irrecord: could not init hardware (lircd running ? --> close it, check permissions)
  [root at watcher daemons]# 
  ------------------------------------

  Any ideas?

  Thanks.

  -M


------------------------------------------------------------------------------


  _______________________________________________
  mythtv-users mailing list
  mythtv-users at snowman.net
  http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.snowman.net/pipermail/mythtv-users/attachments/20030621/be7ca1e0/attachment.htm