[mythtv-users] IR hardware recognition / rtc

Dan Wilga dwilga at mtholyoke.edu
Thu Aug 11 13:32:23 UTC 2005


At 2:06 PM +0000 8/10/05, Marius Schrecker wrote:
>Notably I need to find out what ir hardware I have and make sure I have
>a module for it. This is tricky as I can't see anything in dmesg or lspci
>to help me identify it. It's a built in ir receiver on the front of my biostar
>ideq 330p (nforce4)...any ideas as to what it might be/how to identify it??

According to Biostar's web site, this is an IrDA receiver. IrDA 
devices do not use the same type of LED as most IR remote controls. 
Due to its fundamental frequency, IrDA is useless at anything over 
about 3 feet distance. Its primary use is for syncing portable 
devices (PDAs, laptops, etc.) with the main computer. For this 
particular purpose, the 3-foot restriction isn't a bad one.

Basically, you'll need to get some sort of additional hardware to 
support "regular" IR reception. At least you can probably take out 
the Biostar's IrDA receiver and put the other receiver in its place, 
inside the case.

>vo: X11 running at 1024x768 with depth 24 and 32 bpp (":0.0" => local display)
>Linux RTC init error in ioctl (rtc_irqp_set 1024): Inappropriate ioctl for
>device

Make sure your kernel is compiled with the rtc module, and that it is loaded:

# modinfo rtc
filename:       /lib/modules/2.6.11.10/kernel/drivers/char/rtc.ko
author:         Paul Gortmaker
license:        GPL
alias:          char-major-10-135
vermagic:       2.6.11.10 SMP PENTIUM4 gcc-3.4
depends:       

# lsmod | grep rtc
rtc                    14280  0

If the first works but the second produces nothing, try using:  modprobe rtc
-- 
Dan Wilga                                         dwilga at mtholyoke.edu
Web Administrator                             http://www.mtholyoke.edu
Mount Holyoke College                                Tel: 413-538-3027
South Hadley, MA  01075            "Who left the cake out in the rain?"


More information about the mythtv-users mailing list