lirc update from 4/5/11 may break your configuration. Here's the fix.

cyberpatrol · 2011-05-01 01:23:17

lastdeadmouse wrote:

I had the same problem with any protocol activated (of the ones that actually worked). My assumption is that 2.6.38 broke the cx88xx kernel module at least for some chipsets. At least everyone I've seen with my problem has a cx88. I gave up on the problem for the time being (had worked on it for days) and just went back to 2.6.37.4-1 and lirc-0.9.whatever a few minutes ago. Restored my lircd.conf backups (and nvidia-beta lol) and all is working again for now. I'll just hold off on a kernel upgrade until I have a good reason, as this is my myth box and kind of important (with a wife and kids )

As far as I understood, they have changed something in kernel 2.6.38.x, which seems to have some issues. I guess the chances for a fix are better if you'd also post on the both upstream mailing lists.

lastdeadmouse · 2011-05-01 01:27:02

I did add my input to the open kernel bug report, but i'll post to the kernel ml if I get a chance.

cyberpatrol · 2011-05-01 23:05:55

lastdeadmouse wrote:

I did add my input to the open kernel bug report, but i'll post to the kernel ml if I get a chance.

Would you post the link to your bug report?

lastdeadmouse · 2011-05-01 23:07:23

I did a few posts back

akb825 · 2011-05-01 23:54:01

For those of you using mceusb remotes, I noticed that the 2.6.38.4 kernel upgrade will break your remote if it is plugged into a USB 3.0 port. Everything else seems to work fine in a USB 3.0 port, but the remote fails. When I plugged my remote into a USB 2.0 port it worked again. I posted a bug report for the kernel here. (https://bugzilla.kernel.org/show_bug.cgi?id=34202)

subatomic · 2011-05-17 06:36:31

akb825 wrote:

Make sure that your remote receiver is plugged in and the mceusb (or whatever module corresponds to your remote) is loaded before that command gets executed. If you're putting that command in rc.local to happen at boot time, the simplest way is to make sure that your remote receiver is always plugged in. If your remote receiver is plugged in, and for some reason it doesn't automatically load the module, you may have to put it in your MODULES array.

How do I find the correct module for my Streamzap? Everyone here is talking mceusb and this is obviously not working for me.

OK just tried streamzap and appears to receive, however no action.

lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 041e:4080 Creative Technology, Ltd 
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 152d:2339 JMicron Technology Corp. / JMicron USA Technology Corp. 
Bus 003 Device 003: ID 0603:00f2 Novatek Microelectronics Corp. 
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 009: ID 0e9c:0000 Streamzap, Inc. Streamzap Remote Control

ls -l /dev/input/by-id
total 0
lrwxrwxrwx 1 root root 9 May 17 09:06 usb-0a12_0001-event-mouse -> ../event8
lrwxrwxrwx 1 root root 9 May 17 09:06 usb-0a12_0001-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 May 17 09:04 usb-Creative_Technology_Ltd._VF0610_Live__Cam_Socialize_HD_100507_a_01543-event-if00 -> ../event4                                                                                                           
lrwxrwxrwx 1 root root 9 May 17 09:04 usb-NOVATEK_USB_Keyboard-event-if01 -> ../event6
lrwxrwxrwx 1 root root 9 May 17 09:04 usb-NOVATEK_USB_Keyboard-event-kbd -> ../event5

/proc/bus/input/devices

I: Bus=0003 Vendor=0e9c Product=0000 Version=0100
N: Name="Streamzap PC Remote Infrared Receiver (0e9c:0000)"
P: Phys=usb-0000:00:02.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb3/3-1/3-1:1.0/rc/rc1070/input1078
U: Uniq=
H: Handlers=kbd event7
B: PROP=0
B: EV=100013
B: KEY=3ff 0 fc000 100000000 0 18000 4180c0000801 9e168000000000 0
B: MSC=10

I also have no rc0, just /sys/class/rc/
/dev/lirc0
/dev/lircd

Last edited by subatomic (2011-05-17 07:41:54)

colbert · 2011-05-17 16:15:14

edit: Nevermind, had to reboot, plug in IR receiver again, and now it's back to /sys/class/rc/rc0. Strange.

Last edited by colbert (2011-05-17 16:16:53)

akb825 · 2011-05-18 03:44:34

subatomic wrote:

akb825 wrote:
Make sure that your remote receiver is plugged in and the mceusb (or whatever module corresponds to your remote) is loaded before that command gets executed. If you're putting that command in rc.local to happen at boot time, the simplest way is to make sure that your remote receiver is always plugged in. If your remote receiver is plugged in, and for some reason it doesn't automatically load the module, you may have to put it in your MODULES array.
How do I find the correct module for my Streamzap? Everyone here is talking mceusb and this is obviously not working for me.
OK just tried streamzap and appears to receive, however no action.
lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 041e:4080 Creative Technology, Ltd 
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 152d:2339 JMicron Technology Corp. / JMicron USA Technology Corp. 
Bus 003 Device 003: ID 0603:00f2 Novatek Microelectronics Corp. 
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 009: ID 0e9c:0000 Streamzap, Inc. Streamzap Remote Control

ls -l /dev/input/by-id
total 0
lrwxrwxrwx 1 root root 9 May 17 09:06 usb-0a12_0001-event-mouse -> ../event8
lrwxrwxrwx 1 root root 9 May 17 09:06 usb-0a12_0001-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 May 17 09:04 usb-Creative_Technology_Ltd._VF0610_Live__Cam_Socialize_HD_100507_a_01543-event-if00 -> ../event4                                                                                                           
lrwxrwxrwx 1 root root 9 May 17 09:04 usb-NOVATEK_USB_Keyboard-event-if01 -> ../event6
lrwxrwxrwx 1 root root 9 May 17 09:04 usb-NOVATEK_USB_Keyboard-event-kbd -> ../event5

/proc/bus/input/devices

I: Bus=0003 Vendor=0e9c Product=0000 Version=0100
N: Name="Streamzap PC Remote Infrared Receiver (0e9c:0000)"
P: Phys=usb-0000:00:02.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb3/3-1/3-1:1.0/rc/rc1070/input1078
U: Uniq=
H: Handlers=kbd event7
B: PROP=0
B: EV=100013
B: KEY=3ff 0 fc000 100000000 0 18000 4180c0000801 9e168000000000 0
B: MSC=10
I also have no rc0, just /sys/class/rc/
/dev/lirc0
/dev/lircd

From what I can tell online, you should be using the streamzap module in place of mceusb. The setup should be the same apart from that, but others who have posted here have had issues that seemed to be a problem with the driver.

If it doesn't work after loading the streamzap module, you might want to see if it's plugged into a USB 3.0 port. My remote was plugged in a USB 3.0 port, and it failed in a similar way after a kernel update: lsusb listed it, but it didn't load the module automatically, and even when I loaded the module manually it didn't create a /sys/class/rc/rc0 directory. When I plugged it into a USB 2.0 port, it worked again. I posted a bug report, and it looks like a patch that was committed recently will most likely fix it. (https://bugzilla.kernel.org/show_bug.cgi?id=34202)

edit: Nevermind, had to reboot, plug in IR receiver again, and now it's back to /sys/class/rc/rc0. Strange.

From what I can tell, if you unplug the receiver and plug it back in, it will be assigned a different number. (ie: the first time you unplug it and plug it back in it will be /sys/class/rc/rc1) The protocol will also be reset to the default, so you will need to execute the echo command on the new rc path to change the protocol back to lirc. (or you can always reboot, as you did)

subatomic · 2011-05-18 07:08:56

I don't even have a USB 3.0 port, but I did try to move the receiver to another low speed port which changed nothing. I noticed it was constantly disconnecting, sometimes showing up in lsusb and sometimes not.
Here is the latest output

May 18 08:54:42 localhost kernel: [  507.003329] usb 3-4: new low speed USB device using ohci_hcd and address 50
May 18 08:54:42 localhost kernel: [  507.210398] Registered IR keymap rc-streamzap
May 18 08:54:42 localhost kernel: [  507.210524] input: Streamzap PC Remote Infrared Receiver (0e9c:0000) as /devices/pci0000:00/0000:00:02.0/usb3/3-4/3-4:1.0/rc/rc618/input626
May 18 08:54:42 localhost kernel: [  507.210623] rc618: Streamzap PC Remote Infrared Receiver (0e9c:0000) as /devices/pci0000:00/0000:00:02.0/usb3/3-4/3-4:1.0/rc/rc618
May 18 08:54:42 localhost kernel: [  507.210755] rc rc618: lirc_dev: driver ir-lirc-codec (streamzap) registered at minor = 0
May 18 08:54:42 localhost kernel: [  507.210765] streamzap 3-4:1.0: Registered Streamzap, Inc. Streamzap Remote Control on usb3:50
May 18 08:54:42 localhost mtp-probe: checking bus 3, device 50: "/sys/devices/pci0000:00/0000:00:02.0/usb3/3-4"
May 18 08:54:42 localhost mtp-probe: bus: 3, device: 50 was not an MTP device
May 18 08:54:42 localhost mtp-probe: checking bus 3, device 50: "/sys/devices/pci0000:00/0000:00:02.0/usb3/3-4"
May 18 08:54:42 localhost mtp-probe: bus: 3, device: 50 was not an MTP device
May 18 08:54:43 localhost kernel: [  507.416683] usb 3-4: USB disconnect, address 50
May 18 08:54:43 localhost kernel: [  507.417484] streamzap 3-4:1.0: urb terminated, status: -108

akb825 · 2011-05-19 06:48:29

It looks like it might be a driver issue. You can try posting in the kernel mailing list or posting a bug on the kernel's bugzilla page.

bmentink · 2011-06-21 08:30:38

I have a similar issue with my streamzap usb remote after upgrading to the 2.6.39 kernel, it looks like the driver is dying ...

---------------------------------------------------------- dmesg output ---------------------------------------------------
[ 431.362516] streamzap 6-1:1.0: Registered Streamzap, Inc. Streamzap Remote Control on usb6:102
[ 431.573352] usb 6-1: USB disconnect, device number 102
[ 431.575233] streamzap 6-1:1.0: urb terminated, status: -108
[ 431.829981] usb 6-1: new low speed USB device number 103 using uhci_hcd
[ 432.031358] Registered IR keymap rc-streamzap
[ 432.031489] input: Streamzap PC Remote Infrared Receiver (0e9c:0000) as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/rc/rc606/input615
[ 432.031581] rc606: Streamzap PC Remote Infrared Receiver (0e9c:0000) as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/rc/rc606
[ 432.031673] rc rc606: lirc_dev: driver ir-lirc-codec (streamzap) registered at minor = 0
[ 432.031681] streamzap 6-1:1.0: Registered Streamzap, Inc. Streamzap Remote Control on usb6:103
[ 432.250182] usb 6-1: USB disconnect, device number 103
[ 432.250395] streamzap 6-1:1.0: urb terminated, status: -108
[ 432.253471] BUG: unable to handle kernel NULL pointer dereference at 00000034
[ 432.253476] IP: [<f8c4460e>] show_protocols+0xfe/0x150 [rc_core]
[ 432.253483] *pde = 00000000
[ 432.253485] Oops: 0000 [#1] PREEMPT SMP
[ 432.253488] last sysfs file: /sys/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/rc/rc606/protocols
[ 432.253491] Modules linked in: cpufreq_ondemand ipv6 nilfs2 ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev usbhid hid rt2870sta(C) rc_imon_pad usb_storage uas imon crc_ccitt ir_rc5_sz_decoder rc_streamzap cx24116 nvidia(P) cx23885 altera_stapl(C) cx2341x videobuf_dma_sg videobuf_dvb videobuf_core v4l2_common sg snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer ir_lirc_codec lirc_dev i2c_i801 videodev media altera_ci snd dvb_core btcx_risc tveeprom ir_sony_decoder evdev ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder uhci_hcd ir_nec_decoder streamzap rc_core soundcore ehci_hcd firewire_ohci snd_page_alloc usbcore pcspkr r8169 iTCO_wdt mii iTCO_vendor_support button firewire_core crc_itu_t asus_atk0110 acpi_cpufreq freq_table processor mperf fuse ext4 mbcache jbd2 crc16 sr_mod sd_mod cdrom pata_acpi ata_piix pata_marvell libata scsi_mod radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core intel_agp intel_gtt agpgart
[ 432.253539]
[ 432.253541] Pid: 8613, comm: ir-keytable Tainted: P C 2.6.39-ARCH #1 System manufacturer P5Q-EM/P5Q-EM
[ 432.253545] EIP: 0060:[<f8c4460e>] EFLAGS: 00010202 CPU: 0
[ 432.253548] EIP is at show_protocols+0xfe/0x150 [rc_core]
[ 432.253550] EAX: 00000000 EBX: f8c46b8c ECX: ef6c7000 EDX: 00000001
[ 432.253551] ESI: f8c44510 EDI: c137d7ac EBP: ef6cff20 ESP: ef6cfee8
[ 432.253553] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 432.253555] Process ir-keytable (pid: 8613, ti=ef6ce000 task=ef5a41a0 task.ti=ef6ce000)
[ 432.253557] Stack:
[ 432.253558] 000080d0 00000000 c14a4780 f6b938e0 ef5a41a0 c14a3d00 ef6c7000 ef5a41a0
[ 432.253563] 22222222 22222222 ef63c540 f8c46b8c f8c44510 c137d7ac ef6cff30 c126238f
[ 432.253567] ef63c540 ef617840 ef6cff64 c116dc5b ef6cff64 c111467c b776f000 00000000
[ 432.253572] Call Trace:
[ 432.253576] [<f8c44510>] ? rc_g_keycode_from_table+0xd0/0xd0 [rc_core]
[ 432.253581] [<c126238f>] dev_attr_show+0x1f/0x50
[ 432.253585] [<c116dc5b>] sysfs_read_file+0x7b/0x120
[ 432.253588] [<c111467c>] ? rw_verify_area+0x6c/0x120
[ 432.253591] [<c1114b38>] vfs_read+0x88/0x160
[ 432.253593] [<c116dbe0>] ? sysfs_open_file+0x280/0x280
[ 432.253596] [<c1114c4d>] sys_read+0x3d/0x70
[ 432.253599] [<c134c11f>] sysenter_do_call+0x12/0x28
[ 432.253600] Code: 5e 5f 5d c3 90 8b 43 08 89 34 24 c7 44 24 04 23 63 c4 f8 89 44 24 08 e8 d1 c9 57 c8 01 c6 eb 87 90 8d 74 26 00 8b 80 98 01 00 00 <8b> 58 34 8b 70 38 e8 37 18 00 00 89 45 e8 89 55 e4 e9 31 ff ff
[ 432.253624] EIP: [<f8c4460e>] show_protocols+0xfe/0x150 [rc_core] SS:ESP 0068:ef6cfee8
[ 432.253629] CR2: 0000000000000034
[ 432.253631] ---[ end trace 0804d1cffb2784a2 ]---
[ 475.007085] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 595.003033] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 715.002184] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 835.003336] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 955.006680] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 1075.001790] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 1195.006645] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 1315.002254] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 1435.002881] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 1555.003764] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 1675.006874] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 1795.003722] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 1915.006570] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 2035.007481] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 2155.006562] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 2275.003172] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 2395.002621] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 2515.006518] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
[ 2635.006499] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 109
----------------------------------------------------------------------------------------------------------

I don't know what the fix is for that one ... I don't get any /devlirc0 style devices at all ..

Arch Linux

#51 2011-05-01 01:23:17

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

#52 2011-05-01 01:27:02

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

#53 2011-05-01 23:05:55

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

#54 2011-05-01 23:07:23

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

#55 2011-05-01 23:54:01

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

#56 2011-05-17 06:36:31

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

#57 2011-05-17 16:15:14

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

#58 2011-05-18 03:44:34

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

#59 2011-05-18 07:08:56

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

#60 2011-05-19 06:48:29

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

#61 2011-06-21 08:30:38

Re: lirc update from 4/5/11 may break your configuration. Here's the fix.

Board footer