Re: Still no go on

[<ssc...@wo...>]

The command

setserial /dev/ttySx uart none

is a standard thing, I think to clear the serial buffer, if your 
serial device is on COM3 the command should look something like

setserial /dev/ttyS2 uart none

but your /var/log/dmesg /var/log/syslog /var/log/messages files could 
tell you where it mapped the serial port, to what device file
I still think it is unlikely you will get the IrDA working under LIRC.
Are you doing this on a laptop with the IrDA header builtin?  or is 
the header an external device? (not that you are, but I'll assume you 
nothing on the subject) I'm thinking possibly, you have the BIOS set 
for IrDA support on the serial port, but you don't have any hardware 
attached for LIRC to find... which if you don't have the hardware, I'd 
suggest NOT buying any, and turn your attention to buying a serial IR 
device that LIRC explicitly supports.

Hope this helps.


----- Original Message -----
From: "John D. Mann" <joh...@gm...>
Date: Thursday, January 26, 2006 0:31 am
Subject: Still no go on

> music:/dev# irrecord test.lirc
> 
> irrecord -  application for recording IR-codes for usage with lirc
> 
> Copyright (C) 1998,1999 Christoph Bartelmus(li...@ba...)
> 
> irrecord: could not open /dev/lirc
> irrecord: default_init(): No such device
> irrecord: could not init hardware (lircd running ? --> close it, 
check
> permissions)
> music:/dev#
> 
> 
> I've tried everything I can think of.  The IrDA port is set in the 
> BIOS to
> COM 3, and the ./setup.sh is being set to COM 3 as well.
> 
> I did, however, make some progress.  During the make output, there 
> was a
> small section that said warning: use the following:
> 
> setserial /dev/ttySx uart none
> 
> due to something about serial in my kernel.  I'm not sure, it 
> scrolls past
> my buffer too fast for me to read it word for word, but after 
> watching it go
> by several times, I made out the command it wanted me to do.  No 
other
> warnings or errors, though.
> 
> I've done the setserial on all my ttyS's, but still no go.  The 
> warningdoesn't come back now, though.
> 
> Any suggestions? I'm stumped :(
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through 
> log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD 
> SPLUNK!http://sel.as-
> us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642