Thanks for you response Kyle.  I made a typo there, I meant to say that /dev/lirc was there and I had permission to it.  At that point I had three files: lircd, lirc and lircm.  Now after peforming a modprobe -r lirc_i2c; modprobe lirc_i2c I only have lircd and lircm (/dev/lirc is gone).  Not sure why.  Anyway, I have a hauppauge 150 with the gray remote and I used the setup.sh script to select Driver Configuration, TV Card, Hauppauge TV Card before building.  The 150 itself seems to work.  What should I be trying next?  It appears that /dev/lirc has disappeared and not come back but I'm not sure why.
Thanks again,
Ben.

 
On 7/28/06, Kyle Kienapfel <doctor.whom@gmail.com> wrote:
The problem isn't /dev/lircd, your log bit says it connects to lircd.
The "lircd" part works, it's the "lirc" part that doesn't. Maybe
google for a howto for your IR reciever, i2c sounds like its attached
to your motherboard or a PCI card, but I know nothing beyond that its
driver issues.

On 7/27/06, ben usenetalias < ben.usenet.alias@gmail.com> wrote:
>
> Hello,
> I've just built and installed lirc and now I am having problems running it.
> I attempted...
>
> #modprobe lirc_i2c
> #lircd
> #irw
>
> attempting to run irw just bumps me right back to the command prompt and
> viewing the log I see...
>
> lircd: lircd(hauppauge) ready
> lircd: accepted new client on /dev/lircd
> lircd: could not open /dev/lirc
> lircd: default_init(): no such device
> lircd: caught signal
>
> the file /dev/lircd exists and I have permission to it.  I'm not sure why
> this is bombing out and I'm hoping you folks may be able to help.
> Thanks
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
>