Bug 114268 – Irda doesn't start on kernel 2.6 because of /etc/modprobe.conf.dist

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 114268 - Irda doesn't start on kernel 2.6 because of /etc/modprobe.conf.dist

Summary:	Irda doesn't start on kernel 2.6 because of /etc/modprobe.conf.dist

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	modutils (Show other bugs)
Sub Component:
Version:	1
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-01-25 15:28 EST by Péter, Soós
Modified:	2014-03-16 22:41 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:	2.4.26-3
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-01-29 02:47:19 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Péter, Soós 2004-01-25 15:28:36 EST

Description of problem:
If you configure irda stack via /etc/sysconfig/irda by giving the
proper serial port, irattach does not start on kernel 2.6 besause of
it unable to load tty-ldisc-11. The problem caused by a mistyped line
in /etc/modprobe.conf.dist:
alias tty-ldisc-11 irtty

Version-Release number of selected component (if applicable):
modutils-2.4.25-13

How reproducible:
always

Steps to Reproduce:
1. Configure irda
2. Try to start it
3.
  
Actual results:
Irda does not start:

Expected results:
Irda starts.

Additional info:
You should to change the line in /etc/modprobe.conf.dist
alias tty-ldisc-11 irtty
to
alias tty-ldisc-11 irtty-sir
because of the name of the driver was changed.

Comment 1 Bill Nottingham 2004-01-29 02:47:19 EST

Fixed in 2.4.26-3.

Note You need to log in before you can comment on or make changes to this bug.