FS#6224 - serial built in to kernel breaks lirc

Attached to Project: Arch Linux
Opened by Christ Schlacta (aarcane) - Tuesday, 16 January 2007, 12:26 GMT
Last edited by Greg (dolby) - Tuesday, 08 July 2008, 21:46 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

certain configurations of lirc are broken by SERIAL being built in to the kernel. a workaround is available, but it's a hackish solution. serial should be removed from the kernel and moved to a module.

a mkinitcpio hook serial or serial_console should be added for the individuals who use a serial console.
This task depends upon

Closed by  Greg (dolby)
Tuesday, 08 July 2008, 21:46 GMT
Reason for closing:  Won't fix
Comment by Dale Blount (dale) - Thursday, 03 May 2007, 20:34 GMT
do you have supporting references on this?
Comment by Christ Schlacta (aarcane) - Thursday, 03 May 2007, 22:54 GMT
I can't find the resources right now, but the following commands must be run PRIOR to starting lirc from init:

setserial /dev/ttyS0 uart none
modprobe lirc_serial

which means you can't run lircd from init, you have to run it from rc.local after entering those commands. the only OTHER option would be to re-build the kernel without serial support, and that should be managed by the distro since serial as a module is sufficient for most people and uses.
Comment by Roman Kyrylych (Romashka) - Saturday, 09 February 2008, 15:38 GMT
Is this still an issue?
And about what SERIAL option(s) are you talking? There is no CONFIG_SERIAL but a lot of CONFIG[_*]_SERIAL[_*].
Comment by Tobias Powalowski (tpowa) - Sunday, 10 February 2008, 09:36 GMT
some lirc modules just don't like it included in the kernel and so don't build
Comment by Gavin Bisesi (Daenyth) - Tuesday, 08 July 2008, 02:33 GMT
Should this be closed?
Comment by Christ Schlacta (aarcane) - Tuesday, 08 July 2008, 21:23 GMT
as I can't currently provide any further feedback or testing, and noone else seems to have a setup that's affected by this issue, I would suggest closing this bug.

Loading...