Lirc does not respond after upgrading from 8.04 to 8.10 Beta
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lirc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
lirc does not respond after i had upgraded from 8.04 to 8.10 Beta.
I reconfigured lirc with my custom configuration and the remote does not respond.
This is a summary of my bttv Hardware
[ 29.475799] bttv: driver version 0.9.17 loaded
[ 29.475805] bttv: using 8 buffers with 2080k (520 pages) each for capture
[ 29.475916] bttv: Bt8xx card found (0).
[ 29.475940] bttv 0000:02:01.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 29.475953] bttv0: Bt878 (rev 17) at 0000:02:01.0, irq: 22, latency: 32, mmio: 0xeeafe000
[ 29.475975] bttv0: detected: Prolink Pixelview PV-BT [card=72], PCI subsystem ID is 1554:4011
[ 29.475981] bttv0: using: Prolink PixelView PlayTV MPEG2 PV-M4900 [card=139,insmod option]
[ 29.476048] bttv0: gpio: en=00000000, out=00000000 in=006fc0ff [init]
[ 29.476155] bttv0: tuner type=69
[ 29.476164] bttv0: i2c: checking for TDA9875 @ 0xb0... not found
[ 29.476773] bttv0: i2c: checking for TDA7432 @ 0x8a... not found
[ 29.871407] bttv0: registered device video0
[ 29.871554] bttv0: registered device vbi0
[ 29.871703] bttv0: registered device radio0
[ 29.871740] bttv0: PLL: 28636363 => 35468950 .. ok
[ 29.900825] input: bttv IR (card=139) as /class/input/input7
My TV tuner works perfectly with this configuration, as did my remote control in 7.10 and 8.04.
Ubuntu does recognise that there is an input device attached to the remote control due to the fact when i press buttons on the remote, I can change volume, or press some numbers. Needless to say this is due to keyboard mapping, which should be handled by lirc.
I have attached a copy of Dmesg
<code>
uname -a
Linux Spooky 2.6.27-5-generic #1 SMP Fri Oct 3 00:38:23 UTC 2008 i686 GNU/Linux
</code>
Related branches
Panayiotis Savva (psavva) wrote : | #1 |
Panayiotis Savva (psavva) wrote : | #2 |
Panayiotis Savva (psavva) wrote : | #3 |
Mario Limonciello (superm1) wrote : | #4 |
Can you post the output of lshal? An FDI quirk will be necessary.
edmon (bozhan-abv) wrote : | #5 |
after upgrade form from 8.04 to 8.10 Beta.
my remote accept only numbers...no more volume control or changing channel up and down.
my TV card is Asus My-Cinema and all configurations are default for the remote control PC-39
Mario Limonciello (superm1) wrote : Re: [Bug 279472] Re: Lirc does not respond after upgrading from 8.04 to 8.10 Beta | #6 |
Anyone running into this problem (including you edmon), please post your
lshal
output. It's how we'll be able to add quirks for your remote.
On Thu, Oct 9, 2008 at 07:12, edmon <email address hidden> wrote:
> after upgrade form from 8.04 to 8.10 Beta.
> my remote accept only numbers...no more volume control or changing channel
> up and down.
> my TV card is Asus My-Cinema and all configurations are default for the
> remote control PC-39
>
> --
> Lirc does not respond after upgrading from 8.04 to 8.10 Beta
> https:/
> You received this bug notification because you are a member of
> Mythbuntu, which is subscribed to lirc in ubuntu.
>
--
Mario Limonciello
<email address hidden>
Panayiotis Savva (psavva) wrote : | #7 |
Please find attached a copy of lshal log
On Thu, Oct 9, 2008 at 5:56 PM, Mario Limonciello <email address hidden> wrote:
> Anyone running into this problem (including you edmon), please post your
>
> lshal
>
> output. It's how we'll be able to add quirks for your remote.
>
> On Thu, Oct 9, 2008 at 07:12, edmon <email address hidden> wrote:
>
>> after upgrade form from 8.04 to 8.10 Beta.
>> my remote accept only numbers...no more volume control or changing channel
>> up and down.
>> my TV card is Asus My-Cinema and all configurations are default for the
>> remote control PC-39
>>
>> --
>> Lirc does not respond after upgrading from 8.04 to 8.10 Beta
>> https:/
>> You received this bug notification because you are a member of
>> Mythbuntu, which is subscribed to lirc in ubuntu.
>>
>
>
> --
> Mario Limonciello
> <email address hidden>
>
> --
> Lirc does not respond after upgrading from 8.04 to 8.10 Beta
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
edmon (bozhan-abv) wrote : | #8 |
edmon (bozhan-abv) wrote : | #9 |
after last update my remote stop working at all
Panayiotis Savva (psavva) wrote : | #10 |
I have new info about this problem
It seems that there may either be a permission problem of some sort.
Please review the output below
psavva@Spooky:~$ sudo lircd -n -d /dev/input/event8 -H dev/input
lircd-0.8.3[17094]: lircd(userspace) ready
lircd-0.8.3[17094]: accepted new client on /dev/lircd
lircd-0.8.3[17094]: initializing '/dev/input/event8'
lircd-0.8.3[17094]: can't get exclusive access to events comming from
`/dev/input/event8' interface
On Sat, Oct 11, 2008 at 11:50 AM, edmon <email address hidden> wrote:
> after last update my remote stop working at all
>
> --
> Lirc does not respond after upgrading from 8.04 to 8.10 Beta
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Panayiotis Savva (psavva) wrote : | #11 |
More info:
psavva@Spooky:~$ cat /proc/bus/
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/
U: Uniq=
H: Handlers=mouse0 event0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
I: Bus=0003 Vendor=046d Product=c00e Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-
S: Sysfs=/
U: Uniq=
H: Handlers=mouse1 event1
B: EV=17
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103
B: MSC=10
I: Bus=0003 Vendor=1241 Product=1603 Version=0110
N: Name=" USB Keyboard"
P: Phys=usb-
S: Sysfs=/
U: Uniq=
H: Handlers=kbd event2
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=1241 Product=1603 Version=0110
N: Name=" USB Keyboard"
P: Phys=usb-
S: Sysfs=/
U: Uniq=
H: Handlers=kbd event3
B: EV=13
B: KEY=2000000 39fa d941d001 1e0000 0 0 0
B: MSC=10
I: Bus=0003 Vendor=0d8c Product=000c Version=0100
N: Name="C-Media USB Headphone Set "
P: Phys=usb-
S: Sysfs=/
U: Uniq=
H: Handlers=kbd event4
B: EV=13
B: KEY=e0000 0 0 0
B: MSC=10
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/
U: Uniq=
H: Handlers=kbd event5
B: EV=40001
B: SND=6
I: Bus=0019 Vendor=0000 Product=0002 Version=0000
N: Name="Power Button (FF)"
P: Phys=LNXPWRBN/
S: Sysfs=/
U: Uniq=
H: Handlers=kbd event6
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button (CM)"
P: Phys=PNP0C0E/
S: Sysfs=/
U: Uniq=
H: Handlers=kbd event7
B: EV=3
B: KEY=4000 0 0 0 0
I: Bus=0001 Vendor=1554 Product=4011 Version=0001
N: Name="bttv IR (card=139)"
P: Phys=pci-
S: Sysfs=/
U: Uniq=
H: Handlers=kbd event8
B: EV=100003
B: KEY=2c0814 100004 0 0 0 4 2008000 2090 2001 1e0000 4400 0 ffc
On Tue, Oct 14, 2008 at 8:43 PM, Panayiotis Savva <email address hidden> wrote:
> I have new info about this problem
> It seems that there may either be a permission problem of some sort.
> Please review the output below
>
> psavva@Spooky:~$ sudo lircd -n -d /dev/input/event8 -H dev/input
> lircd-0.8.3[17094]: lircd(userspace) ready
> lircd-0.8.3[17094]: accepted new client on /dev/lircd
> lircd-0.8.3[17094]: initializing '/dev/input/event8'
> lircd-0.8.3[17094]: can't get exclusive access to events comming from
> `/dev/input/event8' interface
>
>
> On Sat, Oct 11, 2008 at 11:50 AM, edmon <email address hidden> wrote:
>> after last update my remote stop working at all
>>
>> --
>> Lirc does not respond after upgrading from 8.04 to 8.10 Beta
>> https:/
>> You received this bug...
Panayiotis Savva (psavva) wrote : | #12 |
I have managed to solve the problem
I needed to edit the FDI for Lirc:
/usr/share/
[code]
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="info.product" contains_
<merge key="info.ignore" type="bool"
</match>
<match key="info.product" contains_
<merge key="info.ignore" type="bool"
</match>
</device>
</deviceinfo>
[/code]
Please note that the in order to find which IR device you should use, you must type
[code]
[code]
lshal | grep IR
[/code]
input.product = 'bttv IR (card=139)' (string)
Note --> <match key="info.product" contains_
I think that this should be further reviewed and a patch should be supplied for this problem.
I used a second IR device which is the streamzap, which worked out of the box. :)
I hope we can do the same for the BTTV Device
I will include some info for your information about the exact card i have:
[code]
udi = '/org/freedeskt
info.linux.driver = 'bttv' (string)
info.parent = '/org/freedeskt
info.product = 'Bt878 Video Capture' (string)
info.subsystem = 'pci' (string)
info.udi = '/org/freedeskt
info.vendor = 'Brooktree Corporation' (string)
linux.
linux.subsystem = 'pci' (string)
linux.sysfs_path = '/sys/devices/
pci.device_class = 4 (0x4) (int)
pci.device_
pci.device_
pci.linux.
pci.product = 'Bt878 Video Capture' (string)
pci.product_id = 878 (0x36e) (int)
pci.subsys_
pci.subsys_vendor = 'PROLINK Microsystems Corp' (string)
pci.subsys_
pci.vendor = 'Brooktree Corporation' (string)
pci.vendor_id = 4254 (0x109e) (int)
udi = '/org/freedeskt
info.ignore = true (bool)
info.parent = '/org/freedeskt
info.product = 'Ignored Device' (string)
info.subsystem = 'input' (string)
info.udi = '/org/freedeskt
input.device = '/dev/input/event8' (string)
input.
input.product = 'bttv IR (card=139)' (string)
linux.device_file = '/dev/input/event8' (string)
linux.
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/devices/
udi = '/org/freedeskt
access_
access_
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
info.
info.capabilities = {'video4linux', 'video4linux.
edmon (bozhan-abv) wrote : | #13 |
may be i have to file new bug but whatever.
My remote behaves strange. When i press 1 several times in console i see severeal 1 but from time to time it writes 3, i see such messages in dmesg
[11978.269020] saa7134 IR (ASUSTeK P7131 Dual): unknown key: key=0x28 raw=0x28 down=1
[11978.496018] saa7134 IR (ASUSTeK P7131 Dual): unknown key: key=0x28 raw=0x28 down=0
[11978.672018] saa7134 IR (ASUSTeK P7131 Dual): unknown key: key=0x28 raw=0x28 down=1
[11978.784018] saa7134 IR (ASUSTeK P7131 Dual): unknown key: key=0x28 raw=0x28 down=0
[11981.500026] saa7134 IR (ASUSTeK P7131 Dual): unknown key: key=0x28 raw=0x28 down=1
[11981.616018] saa7134 IR (ASUSTeK P7131 Dual): unknown key: key=0x28 raw=0x28 down=0
[11981.732019] saa7134 IR (ASUSTeK P7131 Dual): unknown key: key=0x28 raw=0x28 down=1
[11981.849013] saa7134 IR (ASUSTeK P7131 Dual): unknown key: key=0x28 raw=0x28 down=0
[11982.104019] saa7134 IR (ASUSTeK P7131 Dual): unknown key: key=0x28 raw=0x28 down=1
[11982.332024] saa7134 IR (ASUSTeK P7131 Dual): unknown key: key=0x28 raw=0x28 down=0
most of the time i have to point remote in opposite direction to make it write 1 if i press 1
BUT for my surprise when i run inputlirc
edmon@bozhan:~$ irw
2 0 KEY_1 event5
3 0 KEY_2 event5
4 0 KEY_3 event5
5 0 KEY_4 event5
6 0 KEY_5 event5
7 0 KEY_6 event5
8 0 KEY_7 event5
9 0 KEY_8 event5
a 0 KEY_9 event5
174 0 KEY_ZOOM event5
b 0 KEY_0 event5
70 0 KEY_MACRO event5
179 0 KEY_TV event5
189 0 KEY_VIDEO event5
66 0 KEY_HOME event5
185 0 KEY_DVD event5
16e 0 KEY_PVR event5
8b 0 KEY_MENU event5
2 0 KEY_1 event5
3 0 KEY_2 event5
4 0 KEY_3 event5
5 0 KEY_4 event5
6 0 KEY_5 event5
7 0 KEY_6 event5
inputlirc reads and recognize all codes even if i point remote in any direction...
then i stoped inputlirc and restarted lirc...
and now it reads all remote codes:
edmon@bozhan:~$ sudo /etc/init.d/lirc start
* Loading LIRC modules [ OK ]
* Starting remote control daemon(s) : LIRC [ OK ]
edmon@bozhan:~$ irw
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010003 00 2 lirc.conf
0000000080010003 00 2 lirc.conf
0000000080010004 00 3 lirc.conf
0000000080010004 00 3 lirc.conf
0000000080010007 00 6 lirc.conf
0000000080010007 00 6 lirc.conf
0000000080010008 00 7 lirc.conf
0000000080010008 00 7 lirc.conf
0000000080010005 00 4 lirc.conf
0000000080010005 00 4 lirc.conf
0000000080010005 00 4 lirc.conf
0000000080010005 00 4 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
0000000080010002 00 1 lirc.conf
^C
edmon@bozhan:~$ 11111111...
laga (laga) wrote : | #14 |
Yes, please file a new bug report.
Sebastian Kempinski (sebic-k) wrote : | #15 |
I confirm. Had the same problem on different card ((Leadtek Winfast 2000XP - cx88 chip)
@Panayiotis Savva thanks for the solution.
Here is my /usr/share/
before:
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="info.product" contains_
<merge key="info.ignore" type="bool"
</match>
</device>
</deviceinfo>
...and after
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="info.product" contains_
<merge key="info.ignore" type="bool"
</match>
<match key="info.product" contains_
<merge key="info.ignore" type="bool"
</match>
</device>
</deviceinfo>
and suitable part of the lshal output:
udi = '/org/freedeskt
info.
info.callouts.add = {'debian-
info.capabilities = {'input', 'input.keys', 'button'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedeskt
info.product = 'cx88 IR (Leadtek Winfast 2000XP' (string)
info.subsystem = 'input' (string)
info.udi = '/org/freedeskt
input.device = '/dev/input/event4' (string)
input.
input.product = 'cx88 IR (Leadtek Winfast 2000XP' (string)
input.x11_driver = 'evdev' (string)
input.xkb.layout = 'pl' (string)
input.xkb.model = 'pc105' (string)
input.xkb.rules = 'evdev' (string)
linux.device_file = '/dev/input/event4' (string)
linux.
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/devices/
udi = '/org/freedeskt
access_
access_
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
info.
info.capabilities = {'video4linux', 'video4linux.
info.category = 'video4linux' (string)
info.parent = '/org/freedeskt
info.product = 'Leadtek Winfast 2000XP Expert' (string)
info.subsystem = 'video4linux' (string)
info.udi = '/org/freedeskt
linux.device_file = '/dev/radio0' (string)
linux.
linux.subsystem = 'video4linux' (string)
linux.sysfs_path = '/sys/devices/
video4linux.
video4linux.
udi = '/org/freedeskt
access_
access_
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
info.cal...
Thomas M. (thomas-moellenhoff) wrote : | #16 |
Having the same trouble with my Hauppauge Nova-S Plus Remote ... the lirc.fdi fix didn't work for me. Still getting the same error when I start irw / irrecord:
$ cat /var/log/daemon.log
...
lircd-0.8.3[5864]: accepted new client on /dev/lircd
lircd-0.8.3[5864]: initializing '/dev/input/event6'
lircd-0.8.3[5864]: can't get exclusive access to events comming from `/dev/input/event6' interface
lircd-0.8.3[5864]: removed client
lircd-0.8.3[5864]: closing '/dev/input/event6'
$ lshal | grep cx88
info.linux.driver = 'cx88-mpeg driver manager' (string)
info.linux.driver = 'cx88_audio' (string)
info.linux.driver = 'cx8800' (string)
input.product = 'cx88 IR (Hauppauge Nova-S-Plus' (string)
lshal in the attachment.
Mario Limonciello (superm1) wrote : | #17 |
This bug is fixed in bzr revno 45
Changed in lirc: | |
status: | New → Fix Committed |
Launchpad Janitor (janitor) wrote : | #18 |
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_pvr150_
- 16_lirc_gpio
- 26_transmitter_
- 28_irrecord_
* New patches:
- 38_encore_
* debian/lirc.fdi:
- Update FDI file to match a few more remotes reported
on bugs that work when keyed. (LP: #164627, #204960, #279472)
* debian/control:
- Update Recommends for lirc-modules-source
* debian/
- Remove old calls that will no longer be encountered in package
upgrades.
* Merge some packaging changes from Debian. They hadn't done a
release in a long time, so this will at least get us closer to their
packaging for an overarching goal of being in sync.
- Sync'ed changes:
+ debian/compat
+ README.Debian
+ debian/copyright
+ debian/
+ debian/
+ debian/
+ debian/lirc.postrm
+ debian/po
+ debian/
+ debian/
+ drop debian/
+ drop debian/
+ drop debian/lirc.modules
- Merge debian/control, remaining changes:
+ We don't share same VCS
+ We recommend udev
+ Our lirc-modules-source uses DKMS
- Merge debian/rules, remaining changes:
+ DKMS support
- Merge debian/
+ Version number we have is higher
- Merge debian/
+ We install udev rules
+ We install an FDI file
- Merge debian/
+ Some of our keys are named differently because we differentiate
between a remote and a transmitter device.
+ We've got some extra keys for details of devices.
- Merge debian/lirc.init.d, remaining changes:
+ We've pretty much entirely revamped the file. Our deltas will
need to be submitted incrementally to Debian.
- Merge debian/
+ We've pretty much entirely revamped the file. Our deltas will
need to be submitted incrementally to Debian.
- Merge debian/rules, remaining changes:
+ We install a udev rule
+ We install an FDI file
+ We install DKMS support
+ We install transmitter lircd.conf's
+ We Install the remote and transmitter hwdb explicitly
- Merge patches that we took from debian for 0.8.4 support:
+ debian/
+ debian/
lirc (0.8.3-3) unstable; urgency=low
* update swedish translation, thanks to Martin Bagge <email address hidden>
(Closes: #491772).
* add italian debconf translation, thanks to Vincenzo Campanella
<email address hidden>.
* silence LIRC_MODE_LIRCCODE log message, as it is not rate limited and
tends to overflow syslog in case IR receivers get removed without
stopping lirc or remo...
Changed in lirc: | |
status: | Fix Committed → Fix Released |
idokibovito (idokibovito) wrote : | #19 |
Mario, it may be a little late but I just found this bugreport and I seem to have pretty much the same problem:
1. Intrepid with now updated lirc 0.8.4a (had the same problem in 0.8.3 about a week ago)
2. Card is a Winfast TV 2000 XP with the CoolCommand Remote
3. The remote worked with lirc about 3 Ubuntu releases ago but since then the lirc modules could not be compiled.
Now in Intrepid the Volume buttons act as hotkeys on the keyboard, numbers work, and sleep/power does turn off the PC which is waaay uncool. Other buttons don't seem to work.
Oh, and that all without lirc aswell! So I have no idea what happened, the kernel suddenly sees the remote as a normal input device.
Any info on how to get all the buttons working again and how to remap them, would be very much appreciated.
Thanks in advance!
Peter
Mario Limonciello (superm1) wrote : | #20 |
Peter:
Can you start a new bug report so this one doesn't get too cluttered as it's
already marked "solved" and has tons of other things going on in it? Please
attach lshal output to that bug report.
On Thu, Nov 27, 2008 at 06:38, amnesia <email address hidden> wrote:
> Mario, it may be a little late but I just found this bugreport and I
> seem to have pretty much the same problem:
>
> 1. Intrepid with now updated lirc 0.8.4a (had the same problem in 0.8.3
> about a week ago)
> 2. Card is a Winfast TV 2000 XP with the CoolCommand Remote
> 3. The remote worked with lirc about 3 Ubuntu releases ago but since then
> the lirc modules could not be compiled.
>
> Now in Intrepid the Volume buttons act as hotkeys on the keyboard, numbers
> work, and sleep/power does turn off the PC which is waaay uncool. Other
> buttons don't seem to work.
> Oh, and that all without lirc aswell! So I have no idea what happened, the
> kernel suddenly sees the remote as a normal input device.
>
> Any info on how to get all the buttons working again and how to remap them,
> would be very much appreciated.
> Thanks in advance!
>
> Peter
>
> --
> Lirc does not respond after upgrading from 8.04 to 8.10 Beta
> https:/
> You received this bug notification because you are a member of
> Mythbuntu, which is subscribed to lirc in ubuntu.
>
--
Mario Limonciello
<email address hidden>
Attached is a copy of hardware.conf