closing
** Changed in: lirc (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/204960
Title:
[Hardy] Lirc devinput (linux-input-layer) broken
To manage not
Basically, this but is about configurinng hald, a daemon gone since
long. Unless there is more input:_ can we close this bug?
** Changed in: lirc (Ubuntu)
Status: In Progress => Opinion
** Changed in: lirc (Ubuntu)
Status: Opinion => Incomplete
--
You received this bug notificatio
Digital Everywhere's FireDTV has another such receiver, which should be
included in that file.
true
I'm running Karmic. Relevant section in my HAL device list:
udi = '/org/freedesktop/Hal/devices/pci_11c1_5811_logicaldev_input'
info.addons.singleton = {'hald-addon-input'} (string list)
** Branch linked: lp:ubuntu/karmic/lirc
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
hy,
first of all, sorry about my english.
i've follow the steps to make my IR work . I have an saa7134 based tv
card. now it worcks perfectly but if i want to use the IR i have to do
* sudo /etc/init.d/inputlirc restart
Is there any way to do this automaticaly?
--
[Hardy] Lirc devinput (linu
ok mario if you think it's preferable, I don't saw your last answer
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
This bug shouldn't be closed, I believe more interfaces can have this
problem, since mine is a Techno Trend C1500 that I got from second hand
already 3 years ago.
** Changed in: lirc (Ubuntu)
Status: Incomplete => In Progress
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bu
This bug shouldn't be closed, I believe more interfaces can have this
problem, since mine is a Techno Trend C1500 that I got from second hand
already 3 years ago.
** Changed in: lirc (Ubuntu)
Status: Fix Released => Incomplete
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://b
Mirak:
Please open another bug to add that information ok?
Thanks
On Sun, Feb 15, 2009 at 12:12, mirak wrote:
> I have this issue with a TechnoTrend C1500 DVB-C card
> adding this to /usr/share/hal/fdi/preprobe/20thirdparty/lirc.vdi fixes it
> :
>
>
> true
>
>
> --
> [Hardy]
This bug shouldn't be closed, I believe more interfaces can have this
problem.
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I have this issue with a TechnoTrend C1500 DVB-C card
adding this to /usr/share/hal/fdi/preprobe/20thirdparty/lirc.vdi fixes it :
true
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you ar
Michael:
Please add that information to another bug. It will be lost on this bug as
this bug has already been marked "closed"
On Sun, Jan 25, 2009 at 04:11, Michael Rimbert
wrote:
> I experienced very nearly the same thing as above with my DViCO
> FusionHDTV5 RT Gold tuner card. This card has
I experienced very nearly the same thing as above with my DViCO
FusionHDTV5 RT Gold tuner card. This card has the product info string
'i2c IR (FusionHDTV)', as reported by hal-device. The patch provided
below prevents hal from grabbing /dev/input/event6, and treating is an
linux-input-layer devi
Per Heldal wrote:
> The fix in 0.8.4a-0ubuntu1 is not complete. Exceptions are made for HAL
> to ignore a list of known receivers, but there are surely more to come.
> A permanent fix can only be made upstream by making HAL able to identify
> dev/input IR-receivers in general, or integrate lircd to
The fix in 0.8.4a-0ubuntu1 is not complete. Exceptions are made for HAL
to ignore a list of known receivers, but there are surely more to come.
A permanent fix can only be made upstream by making HAL able to identify
dev/input IR-receivers in general, or integrate lircd to take events
from dev/inpu
This bug was fixed in the package lirc - 0.8.4a-0ubuntu1
---
lirc (0.8.4a-0ubuntu1) jaunty; urgency=low
* New upstream version.
* Drop no longer necessary patches:
- 03_extra_files
- 25_upstream_2.6.27
- 27_multiple_include
* Update patches for new version:
- 12_
bzr revno 45
** Changed in: lirc (Ubuntu)
Status: Confirmed => Fix Committed
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Hi Ari,
Thanks for your response. This M115 is in fact a card based on SAA7134
with an additional cx2028 tuner chip, but it doesn't register it's IR
as described in the workaround. It's running with the latest kernel
(2.6.27) and as card number 138 for the saa7134 module.
But I'll try as you sug
Hi Fastguy, this bug & workaround is specifically for SAA7134-based
cards, and it is only about LIRC being unable to grab the device,
because HAL did it earlier.
In any case, whatever the chipset you have, you may be having a driver
problem, or a lirc misconfig (since you seem to have the basics
w
I don't know if we need another bug report for the problem...
** Changed in: lirc (Ubuntu)
Status: Fix Released => Confirmed
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you are a member of Ubuntu
Bu
Hi,
I have an Avermedia M115 mini-pci-e TV card on an Acer Aspire 5652. The
card has an infrared device which is exactly working as described in the
original bug report. I can get some of the keys like 1-2-3-OK etc. on
the login screen, terminal window etc.
System is a Mythbuntu 8.10 beta 1 updat
This bug was fixed in the package lirc - 0.8.3-0ubuntu2
---
lirc (0.8.3-0ubuntu2) intrepid; urgency=low
* debian/patches/25_upstream_2.6.26.patch:
- Fix lirc-modules-source compilation on 2.6.26 by pulling some
patches from CVS (LP: #247233)
* debian/rules:
- Install
Thanks for all the triaging and development of this FDI file.
Fixed in bzr #26.
** Changed in: lirc (Ubuntu)
Assignee: (unassigned) => Mario Limonciello (superm1)
Status: Confirmed => Fix Committed
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/2
Removing incomplete so bug doesn't expire
** Changed in: lirc (Ubuntu)
Status: Incomplete => Confirmed
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ari
Spectacular explanation. Exactly what I was looking to hear before making
changes to this. In a future lirc upload i'll install your FDI file by
default then.
Regards
On Thu, Aug 14, 2008 at 13:59, Ari <[EMAIL PROTECTED]> wrote:
> Mario: without LIRC, the remote acts as normal keypresses
Mario: without LIRC, the remote acts as normal keypresses (like if it
were the PC's keyboard), i.e. if you open a terminal and press the "1"
key, you see a "1" char entered in the terminal, which is essentially
useless.
I've run mythTV in the past and I now run Elisa and both work fine (and
requir
Ari:
OK last question for sanities sake. Is there a usecase for this IR device
outside of LIRC? Does it act like normal key presses otherwise? Reason I
ask is because lirc gets installed by default on all mythbuntu installs and
can't be removed without breaking a lot of other stuff. Do you see
Hi Mario, I don't think there are negative side effects to this; I am
matching specifically this:
contains_ncase="saa7134 ir"
which is the infrared function of the chipset, which is bound to make
LIRC fail if we don't do this.
If people install lirc, I would have this added automatically to the
Ari:
So are there negative side effects to dropping that file in place with all
LIRC installs, or should it only be enabled on a case by case basis?
On Wed, Aug 13, 2008 at 23:52, Ari <[EMAIL PROTECTED]> wrote:
> Mario, the fix for this is having HAL bypass the saa7134 infrared port.
> The most f
Mario, the fix for this is having HAL bypass the saa7134 infrared port.
The most flexible way to do this is the adding and .fdi file
("remote.fdi" file in /usr/share/hal/fdi/preprobe/20thirdparty/)
This is the content:
true
... otherwise, remote controls for this popular cards will
Ari:
This bug is about to expire. Any updates on what should be done?
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
With the .fdi file removed, inputlirc no longer works, here's the
output:
Starting inputlirc
Failed to grab /dev/input/event6: Device or resource busy
Unable to open any event device!
[EMAIL PROTECTED]:~$ irw
connect: Connection refused
[EMAIL PROTECTED]:~$
Also, I've changed my .fdi rule for
Ari schrieb:
> it works. but this is with the remote.fdi blacklist installed. Not sure
> if you mean I have to remove it first?
>
Yeah, please remove it. A reboot might be good afterwards to get the
system back into a known state.
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bug
@Mario: yes, for saa7134 -based cards, the .fdi file is needed.
The problem in the file is that I match the whole info.product string,
so it works only for my particular card brand.
It would somewhat more generic to just match the "saa7134 IR" substring,
like this:
@laga: following your instr
I wonder if inputlirc will be able to gain exclusive access to your
device. If it does, then maybe lirc is broken.
* sudo aptitude install inputlirc
* Then modify /etc/default/inputlirc to look like this:
# Options to be passed to inputlirc.
EVENTS="/dev/input/event6"
OPTIONS="-g -m 0"
It's pos
So when this remote is selected, what should the option be then? Drop
that file in there and modify the FDI? yuck...
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Yes, I know I am way too lazy.
So after a little research I came up with a workaround and now my remote
is back alive.
Following laga's suggestion, you need to put the attached "remote.fdi"
file in /usr/share/hal/fdi/preprobe/20thirdparty/
Also you need to modify the file to match your remote.
Any chance to post at least some guidelines on how to implement this? I can try
them out.
It would be a pitty to have 8.04 ship with lirc broken for many tv card tuner
users.
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notifi
Attached the output of lshal, I guess it may help build the filter. The
device in question is the infrared part of the saa7134, it shows up in
the attachment.
Thanks!
** Attachment added: "lshal.txt"
http://launchpadlibrarian.net/12850129/lshal.txt
--
[Hardy] Lirc devinput (linux-input-lay
Michael,
Can you put together a patch to tell hald-addon-input service to ignore this
for Ari to try?
Thanks
On Mon, Mar 24, 2008 at 9:34 AM, laga <[EMAIL PROTECTED]> wrote:
> Mario Limonciello schrieb:
> > Hi Ari:
> > Given that it can't grab a lock on the device, this probably is because
> th
Mario Limonciello schrieb:
> Hi Ari:
> Given that it can't grab a lock on the device, this probably is because the
> hald-addon-input service has the tight grip on it.
>
> Perusing the man page for hal, I don't see an easy way to turn this off.
> If you find a scriptable way to do so, we'd be gl
I'm surprised. Are you aware of what could have changed with respect to
Gutsy / 2.6.22 and previous kernels/hald's?
This remote has been working perfectly on linux for a couple of years...
SAA7134-based boards are very popular out there.
A few questions, Is there a reason why LIRC's has to lock
Hi Ari:
Given that it can't grab a lock on the device, this probably is because the
hald-addon-input service has the tight grip on it.
Perusing the man page for hal, I don't see an easy way to turn this off.
If you find a scriptable way to do so, we'd be glad to adapt.
** Changed in: lirc (Ubu
Attaching lircd.conf
** Attachment added: "lircd.conf"
http://launchpadlibrarian.net/12804294/lircd.conf
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "hardware.conf"
http://launchpadlibrarian.net/12804291/hardware.conf
--
[Hardy] Lirc devinput (linux-input-layer) broken
https://bugs.launchpad.net/bugs/204960
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
45 matches
Mail list logo
