[mythtv-users] Lirc Problems and one other question

[Aleaxander]

Jarod C. Wilson wrote:

> On Nov 21, 2003, at 21:16, Aleaxander wrote:
> 
>> Jarod C. Wilson wrote:
>>
>>> On Nov 18, 2003, at 19:32, Aleaxander wrote:
>>>
>>>> Running irw again, gives me the "connect: Connection refused" error 
>>>> again.  Drat!  I tried looking in /var/log/lircd but there is no 
>>>> folder called lircd there.  So, I think I'm stuck.  Anyone have any 
>>>> idea what is wrong?  Live TV works, from within Myth frontend, so I 
>>>> think it is probably installed correctly, just no remote.
>>>
>>> Are you positive you have the right lircd.conf in place? Look at the 
>>> contents of /etc/lircd.conf. The top of the file should contain a 
>>> description for which remote it is for...
> 
> 
>> Yep, looks like it is the right lircd.conf.  I compared it to the 
>> lircd.conf in /usr/share/doc/ivtv-0.12/lircd.conf, and they are the 
>> same (I have the black remote).  Any suggestions?
> 
> 
> Damn. Huh. What output do you get from "/sbin/service lircd status" 
> after you've started it up?

Results:
$ /sbin/service lircd status
lircd (pid 7609) is running...

> There ought to be some useful information in 
> /var/log/messages also...
> 

Note, I don't seem to have a /var/log/lircd file.  Any reason for this?

This from /var/log/messages from startup:

Nov 22 10:55:22 mythtv insmod: 
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/parport/parport_pc.o: 
init_module: Device or resource busy
Nov 22 10:55:22 mythtv 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
Nov 22 10:55:22 mythtv insmod: 
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/parport/parport_pc.o: 
insmod parport_lowlevel failed
Nov 22 10:55:22 mythtv kernel: lp: driver loaded but no devices found
Nov 22 10:55:22 mythtv modprobe: modprobe: Can't locate module 
char-major-188
Nov 22 10:55:22 mythtv last message repeated 15 times
Nov 22 10:55:22 mythtv cups: cupsd startup succeeded
Nov 22 10:55:23 mythtv lircd 0.7.0pre2[7609]: lircd(hauppauge) ready
Nov 22 10:55:23 mythtv lircd: lircd startup succeeded
Nov 22 10:55:23 mythtv xfs: xfs startup succeeded
Nov 22 10:55:23 mythtv anacron: anacron startup succeeded
Nov 22 10:55:24 mythtv atd: atd startup succeeded
Nov 22 10:55:24 mythtv xfs: ignoring font path element 
/usr/X11R6/lib/X11/fonts/cyrillic (unreadable)
Nov 22 10:55:26 mythtv kernel: 0: nvidia: loading NVIDIA Linux x86 
nvidia.o Kernel Module  1.0-4363  Sat Apr 19 17:46:46 PDT 2003
Nov 22 10:55:26 mythtv insmod: Warning: loading 
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/video/nvidia.o will 
taint the kernel: non-GPL license - NVIDIA
Nov 22 10:55:26 mythtv insmod:   See 
http://www.tux.org/lkml/#export-tainted for information about tainted 
modules
Nov 22 10:55:26 mythtv insmod: Module nvidia loaded, with warnings
Nov 22 10:55:41 mythtv gdm(pam_unix)[7726]: session opened for user 
mythtv by (uid=0)
Nov 22 10:55:41 mythtv gdm[7726]: gdm_auth_user_add: /home/mythtv is 
writable by group.
Nov 22 10:55:52 mythtv modprobe: modprobe: Can't locate module sound-slot-0
Nov 22 10:55:53 mythtv modprobe: modprobe: Can't locate module sound-slot-0
Nov 22 10:55:53 mythtv modprobe: modprobe: Can't locate module sound-slot-1
Nov 22 10:55:53 mythtv modprobe: modprobe: Can't locate module 
sound-service-1-0
Nov 22 10:55:53 mythtv modprobe: modprobe: Can't locate module sound-slot-1
Nov 22 10:55:53 mythtv modprobe: modprobe: Can't locate module 
sound-service-1-0
Nov 22 10:56:01 mythtv automount[7882]: >> /usr/sbin/showmount: can't 
get address for .directory
Nov 22 10:56:01 mythtv automount[7882]: lookup(program): lookup for 
.directory failed
Nov 22 10:56:01 mythtv automount[7882]: failed to mount /net/.directory
Nov 22 10:56:01 mythtv automount[7887]: failed to mount /misc/.directory
Nov 22 10:56:23 mythtv su(pam_unix)[7921]: session opened for user root 
by mythtv(uid=500)
Nov 22 11:01:05 mythtv gconfd (root-7990): starting (version 2.2.0), pid 
7990 user 'root'
Nov 22 11:01:05 mythtv gconfd (root-7990): Resolved address 
"xml:readonly:/etc/gconf/gconf.xml.mandatory"
  to a read-only config source at position 0
Nov 22 11:01:05 mythtv gconfd (root-7990): Resolved address 
"xml:readwrite:/root/.gconf" to a writable co
nfig source at position 1
Nov 22 11:01:05 mythtv gconfd (root-7990): Resolved address 
"xml:readonly:/etc/gconf/gconf.xml.defaults"
to a read-only config source at position 2
Nov 22 11:03:05 mythtv gconfd (root-7990): GConf server is not in use, 
shutting down.
Nov 22 11:03:05 mythtv gconfd (root-7990): Exiting


Finally, this is the output to /var/log/messages when I run /usr/bin/irw:

ov 22 13:27:56 mythtv lircd 0.7.0pre2[7609]: accepted new client on 
/dev/lircd
Nov 22 13:27:56 mythtv kernel: lirc_dev: IR Remote Control driver 
registered, at major 61
Nov 22 13:27:56 mythtv kernel: i2c-core.o: i2c core module version 2.8.0 
(20030714)
Nov 22 13:27:56 mythtv kernel: Linux video capture interface: v1.00
Nov 22 13:27:57 mythtv kernel: bttv: driver version 0.7.104 loaded
Nov 22 13:27:57 mythtv kernel: bttv: using 4 buffers with 2080k (8320k 
total) for capture
Nov 22 13:27:57 mythtv kernel: bttv: Host bridge is VIA Technologies, 
Inc. VT8367 [KT266]
Nov 22 13:27:57 mythtv insmod: 
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/bttv.o: 
init_module: No such device
Nov 22 13:27:57 mythtv 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
Nov 22 13:27:57 mythtv insmod: 
/lib/modules/2.4.20-20_29.rh9.at/kernel/drivers/media/video/bttv.o: 
insmod bttv failed
Nov 22 13:27:57 mythtv modprobe: modprobe: Can't locate module rivatv
Nov 22 13:27:57 mythtv lircd 0.7.0pre2[7609]: could not open /dev/lirc
Nov 22 13:27:57 mythtv lircd 0.7.0pre2[7609]: default_init(): No such device
Nov 22 13:27:57 mythtv lircd 0.7.0pre2[7609]: caught signal

Anything wrong that you can see?

Thanks,

-Aleaxander