lirc_imon upgrade?
weirdfish
Status: New User - Welcome
Joined: 27 Feb 2010
Posts: 3
Reply Quote
Liquorix has been shipping for some time with lirc_imon v0.7. This driver however is under active development and had already reached v1.15 last time I checked.

I've built the module myself from the lirc CVS repo, but I can't get it to work with Liquorix. It seems the problem lies with lirc_dev, which should be upgraded as well: however, that module is nowhere to be found and when I try to insmod mine, I get an error about it being already loaded.

Is it possible to have lirc_imon updated to the current version, or alternatively can you help me find a way to upgrade the module without having to recompile the whole kernel?
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 914
Reply Quote
The next version of my kernel should the new lirc code, thanks for noticing.
Back to top
weirdfish
Status: New User - Welcome
Joined: 27 Feb 2010
Posts: 3
Reply Quote
Thanks to you for the swell work.

I had written a reply some time ago but it seems my browser ate it. Nevermind, I'm back with some real world feedback.

The new version, after some adjustments to my configuration, seems to be working. It does default to mouse mode rather than keyboard as the old driver did, which is weird for an HTPC remote. Any chance this can be fixed?
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 914
Reply Quote
That would need to be fixed upstream, sorry :\
Back to top
weirdfish
Status: New User - Welcome
Joined: 27 Feb 2010
Posts: 3
Reply Quote
Sorry to bump an old thread. I'm in the process of upgrading from 2.6.33-4.dmz.3 to the current 2.6.34-0.dmz.10. It appears the imon driver is no longer bundled with the kernel. Is this intended?
Back to top
DeepDayze
Status: Contributor
Joined: 21 May 2009
Posts: 116
Reply Quote
:: weirdfish wrote ::
Sorry to bump an old thread. I'm in the process of upgrading from 2.6.33-4.dmz.3 to the current 2.6.34-0.dmz.10. It appears the imon driver is no longer bundled with the kernel. Is this intended?


Have you tried to build this driver manually to ensure it works with this kernel? If it works, perhaps damentz will include it again in a future build
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 914
Reply Quote
Ah, sorry.

With 2.6.34, I'm no longer using Zen Sources as a base due to the developer's lack of interest. Plus, without cheater-conrad active, the quality of all the updates have been abysmal at best.

Since I'm starting from vanilla 2.6.34 sources, I have to choose which patches are included and which patches are not. This is one of the git branches I missed when looking for all the essential patches to my kernel, thanks for bringing this up.

The next kernel I upload should have the LIRC modules.
Back to top
dali
Status: New User - Welcome
Joined: 23 Oct 2010
Posts: 1
Reply Quote
I've had some problems with lirc_imon in 2.6.35-7.dmz.1-liquorix-amd64.

One problem was that the kernel oopsed with this logged to kern.log:

:: Code ::

Oct 24 07:50:02 zalmix kernel: lirc_dev: IR Remote Control driver registered, major 251
Oct 24 07:50:02 zalmix kernel: lirc_imon: Driver for SoundGraph iMON MultiMedia IR/Display, v0.7
Oct 24 07:50:02 zalmix kernel: BUG: unable to handle kernel NULL pointer dereference at 000000000000000e
Oct 24 07:50:02 zalmix kernel: IP: [<ffffffff8105ec27>] kfifo_alloc+0x27/0xa0
Oct 24 07:50:02 zalmix kernel: PGD 11e2d1067 PUD 11db33067 PMD 0
Oct 24 07:50:02 zalmix kernel: Oops: 0002 [#1] PREEMPT SMP
Oct 24 07:50:02 zalmix kernel: last sysfs file: /sys/bus/usb/drivers/option/uevent
Oct 24 07:50:02 zalmix kernel: CPU 0
Oct 24 07:50:02 zalmix kernel: Modules linked in: lirc_imon(+) lirc_dev option usb_wwan usbhid snd_hda_codec_nvhdmi nouveau ttm drm_kms_helper drm i2c_algo_bit nvidia(P) snd_hda_codec_realtek usb_storage snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm psmouse led_class snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi sg snd_seq_midi_event usbserial sr_mod serio_raw ohci_hcd ehci_hcd snd_seq pata_jmicron i2c_nforce2 r8169 mii wmi rtc_cmos rtc_core rtc_lib tpm_tis tpm tpm_bios video output cdrom shpchp pci_hotplug snd_timer snd_seq_device pcspkr evdev snd soundcore snd_page_alloc i2c_core button processor ext4 mbcache jbd2 crc16 sd_mod ahci libahci pata_acpi ata_generic libata scsi_mod thermal
Oct 24 07:50:02 zalmix kernel:
Oct 24 07:50:02 zalmix kernel: Pid: 1279, comm: modprobe Tainted: P            2.6.35-7.dmz.1-liquorix-amd64 #1 MI-9300-7AS9/MI-9300-7AS9
Oct 24 07:50:02 zalmix kernel: RIP: 0010:[<ffffffff8105ec27>]  [<ffffffff8105ec27>] kfifo_alloc+0x27/0xa0
Oct 24 07:50:02 zalmix kernel: RSP: 0018:ffff88011e00bcf8  EFLAGS: 00010286
Oct 24 07:50:02 zalmix kernel: RAX: ffff880119747a00 RBX: 000000000000000e RCX: ffffffff8105ec22
Oct 24 07:50:02 zalmix kernel: RDX: ffff880119747c00 RSI: 00000000000000d0 RDI: 0000000000000009
Oct 24 07:50:02 zalmix kernel: RBP: 0000000000000200 R08: 0000000000000000 R09: ffff8801185b5480
Oct 24 07:50:02 zalmix kernel: R10: 0000000000000001 R11: 0000000000000000 R12: ffff8801186d5400
Oct 24 07:50:02 zalmix kernel: R13: ffff88011b2047c0 R14: 0000000000000000 R15: 0000000000000004
Oct 24 07:50:02 zalmix kernel: FS:  00007f8169639700(0000) GS:ffff880001800000(0000) knlGS:0000000000000000
Oct 24 07:50:02 zalmix kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 24 07:50:02 zalmix kernel: CR2: 000000000000000e CR3: 000000011a1bb000 CR4: 00000000000406f0
Oct 24 07:50:02 zalmix kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 24 07:50:02 zalmix kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Oct 24 07:50:02 zalmix kernel: Process modprobe (pid: 1279, threadinfo ffff88011e00a000, task ffff88011e0577f0)
Oct 24 07:50:02 zalmix kernel: Stack:
Oct 24 07:50:02 zalmix kernel: ffff88011b145000 ffff8801186d7000 ffff88011b145000 ffffffffa02ea1ab
Oct 24 07:50:02 zalmix kernel: <0> 00ffffff8135442d ffff88011e0577f0 ffff8801196810f0 ffff880100000001
Oct 24 07:50:02 zalmix kernel: <0> ffffffff81354402 ffffffff00000004 ffff8801185b5480 000000001e00bda8
Oct 24 07:50:02 zalmix kernel: Call Trace:
Oct 24 07:50:02 zalmix kernel: [<ffffffffa02ea1ab>] ? imon_probe+0x5fb/0xee8 [lirc_imon]
Oct 24 07:50:02 zalmix kernel: [<ffffffff81354402>] ? mutex_unlock+0x12/0x20
Oct 24 07:50:02 zalmix kernel: [<ffffffff8125d554>] ? pm_runtime_resume+0x34/0x50
Oct 24 07:50:02 zalmix kernel: [<ffffffff8127367e>] ? usb_probe_interface+0x11e/0x220
Oct 24 07:50:02 zalmix kernel: [<ffffffff81256986>] ? driver_probe_device+0x96/0x1c0
Oct 24 07:50:02 zalmix kernel: [<ffffffff81256b43>] ? __driver_attach+0x93/0xa0
Oct 24 07:50:02 zalmix kernel: [<ffffffff81256ab0>] ? __driver_attach+0x0/0xa0
Oct 24 07:50:02 zalmix kernel: [<ffffffff81255e38>] ? bus_for_each_dev+0x58/0x80
Oct 24 07:50:02 zalmix kernel: [<ffffffff812560e0>] ? bus_add_driver+0xb0/0x250
Oct 24 07:50:02 zalmix kernel: [<ffffffff81256e4a>] ? driver_register+0x6a/0x130
Oct 24 07:50:02 zalmix kernel: [<ffffffff812732ea>] ? usb_register_driver+0xaa/0x170
Oct 24 07:50:02 zalmix kernel: [<ffffffffa01f2000>] ? imon_init+0x0/0x4f [lirc_imon]
Oct 24 07:50:02 zalmix kernel: [<ffffffffa01f202c>] ? imon_init+0x2c/0x4f [lirc_imon]
Oct 24 07:50:02 zalmix kernel: [<ffffffff810001d4>] ? do_one_initcall+0x34/0x1a0
Oct 24 07:50:02 zalmix kernel: [<ffffffff81076cda>] ? sys_init_module+0xba/0x200
Oct 24 07:50:02 zalmix kernel: [<ffffffff81002eeb>] ? system_call_fastpath+0x16/0x1b
Oct 24 07:50:02 zalmix kernel: Code: 00 00 00 00 55 89 f5 53 48 89 fb 89 f7 48 8d 47 ff 48 83 ec 08 48 85 ff 74 32 48 85 f8 75 2d 89 d6 e8 7e 11 08 00 48 85 c0 74 4e <48> 89 03 89 6b 08 31 c0 c7 43 10 00 00 00 00 c7 43 0c 00 00 00
Oct 24 07:50:02 zalmix kernel: RIP  [<ffffffff8105ec27>] kfifo_alloc+0x27/0xa0
Oct 24 07:50:02 zalmix kernel: RSP <ffff88011e00bcf8>
Oct 24 07:50:02 zalmix kernel: CR2: 000000000000000e
Oct 24 07:50:02 zalmix kernel: ---[ end trace 787133f218f700b6 ]---


Another problem was suspend to RAM. The suspend halted at "Suspending console(s) (use no_console_suspend to debug)".

Tried blacklisting lirc_imon in /etc/modprobe.d/blacklist.conf but ended up having to rename the kernel module in /lib/modules/2.6.35-7.dmz.1-liquorix-amd64/kernel/drivers/input/lirc/. That "solved" both oopses and suspend to RAM.

Not sure why the blacklisting didn't work, this way I have to rename the kernel module every time the kernel is updated. With Debian standard kernels blacklisting works, I've used it to disable nouveau and lirc_imon for years.

UPDATE:

Blacklisting doesn't work, but adding this to /etc/modprobe.d/00local.conf does:
:: Code ::

install lirc_imon /bin/true

Back to top
Display posts from previous:   

All times are GMT - 8 Hours