Ben,
So when you got the configuration right the driver still failed, because
the IRQ was already allocated.
the funny thing is: the lirc_serial driver *does* work when share_irq=1
is added to the parameters specified in
/etc/modprobe.d/lirc_serial.conf. At least, I can now happily use my
r
Hi,
ok, 'twas my fault -- loading lirc_serial with share_irq=1 did the
trick. Hence I ask you to close this bug report.
Thanx, and sorry for bothering you --
Torsten
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Package: linux-2.6
Version: 3.0.0-5
Severity: normal
Dear Maintainer,
althoug I disabled serial port /dev/ttyS1 via setserial, lirc_serial
claims the specified IO port (0x02f8) and IRQ (3) to be in use. However,
"cat /proc/ioports" and "cat /proc/interrupts" tell otherwise.
Please find the ou
Hi there,
I just wanted to let you know that the kernel oops as well as the
complete freeze on cat /proc/interrupts was gone after a recent system
upgrade. (lirc_serial is still complaining about port 0x02f8 and IRQ 3
being in use, though...) So I guess this bug report can be closed?
Regards
Hi,
since my previous attempt to submit further information apparently
failed, I hereby re-submit my message from yestarday night:
8<
Ben, Jarod,
in order to confirm that lirc_serial is the bad guy, I tried to prevent
the lirc modules from loading -- without success though.
Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Dear Maintainer,
when trying to figure out which kernel module might be using IRQ 3 in my
Intel D525MW-based system by calling "cat /proc/interrupts", I get the
reply "Killed" on the console, and the messages from [ 916.033769]
onwards sho
6 matches
Mail list logo
