Bug 84565

Summary:	IrDA doesn't work out of box
Product:	[Retired] Red Hat Public Beta	Reporter:	Peter Bowen <pzbowen+rhbeta>
Component:	irda-utils	Assignee:	wdovlrrw <brosenkr>
Status:	CLOSED NOTABUG	QA Contact:	Jay Turner <jturner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	phoebe	CC:	srevivo
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-02-19 01:11:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Bowen 2003-02-18 23:59:01 UTC

In order to get IrDA working I had to do two things:

1) change DEVICE to /dev/ttyS1 in /etc/sysconfig/irda.  The default of
/dev/ttyS2 didn't work.  irattach didn't do any when it was set to this.

2) Add the modules to modules.conf.  Some program should add the alias to
modules.conf:

alias char-major-161 ircomm-tty

Comment 1 Peter Bowen 2003-02-19 00:02:03 UTC

OK, I take back point 2.  It looks like modprobe has the necessary aliases built in.

Comment 2 Bill Nottingham 2003-02-19 00:43:48 UTC

DEVICE= sounds very much specific to your particular hardware. Not sure if
there's really anything we can do about that.

Comment 3 Peter Bowen 2003-02-19 01:11:40 UTC

Ok, you are right.  I just misread the docs, or general lack there of.  I was
under the impression it emulated a serial port on the specified device, but it
is the other way around.  It looks at that device and uses it as an irport, as
the BIOS emulates a serial port with a IR device attached, similar to a modem.

I'm going to open this so that others can find the answer on their hardware.