[LINUX]XBMC on 2.6.35 (Lucid with Maverick kernel backport) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228) +---- Thread: [LINUX]XBMC on 2.6.35 (Lucid with Maverick kernel backport) (/showthread.php?tid=78571) |
[LINUX]XBMC on 2.6.35 (Lucid with Maverick kernel backport) - crazytony - 2010-08-07 Hey, Just upgraded from the stock Lucid kernel to the 2.6.35 kernel (2.6.35-14). I will post any gotchas I find against the latest svn and this kernel. First gotcha: LIRC v the kernel In 2.6.34, the LIRC guys started putting the IR stuff into the core kernel (IR core project). Took me a while to reconfigure my iMON remote that came with my Antec Fusion case: Code: Bus 004 Device 002: ID 15c2:0038 SoundGraph Inc. While the latest SVN does pick the remote up without LIRC running, you can't access the OSD or menus with the default binding. To get the remote working again you have to configure LIRC from lirc_imon to devinput (linux-input-layer) - lludger - 2010-08-07 Hi crazytony, that sounds really cool. I have the same setup and I'm still fighting with the details. Can you share your config files? Thank you very much, ludger - crazytony - 2010-08-08 I'm running the latest SVN version of LIRC -- I don't know if the Ubuntu dist includes the linux-input-layer (worth a try) Step 1: Configure LIRC /etc/lircd/lircd.conf: http://pastebin.com/PfGGBgWr hardware.conf: this is tricky. You have to get the device path right. First, run Code: cat /proc/bus/input/devices Code: I: Bus=0003 Vendor=15c2 Product=0038 Version=0002 Replace the phys line in the hardware.conf http://pastebin.com/cFn6Lbq5 with the value from the phys= line above. In my hardware.conf that looks like Code: ... Step 2: Restart lircd: Code: /etc/init.d/lirc stop Test lirc: Code: xbmc@frontmedia:~$ irw Gotcha 2: if you don't see anything, press the keyboard/mouse button on the remote. You may have to do this after every reboot. If you still don't see anything, then something in the config is wrong. Step 3: Configure XBMC Gotcha 3: latest SVN has linux-input-layer in the Lircmap.xml but it has the wrong key names. Here's my version: /usr/share/xbmc/system/Lircmap.xml: http://pastebin.com/VYRUL5f7 Restart xbmc and test in xbmc. - m3g4tr0n - 2010-08-10 where did you get the kernel from? do you have the .deb files you could share also for lirc. - crazytony - 2010-08-11 I compiled lirc directly from SVN -- no debs available I'm afraid. I would test the 0.86 version that ships with Lucid before doing something drastic like compiling. I didn't get a chance to do this because I was trying to debug the issue. The kernel came from the Ubuntu Kernel Team's PPA: Code: sudo add-apt-repository ppa:kernel-ppa/ppa You may have to make changes to your grub config (/etc/default/grub) to pick up the new kernel and you will have to reboot after installing and configuring to run the new kernel. This will tell you if you have the kernel Code: $ uname -a In order to use XBMC with the new kernel you will also have to uninstall the graphics drivers and reinstall the latest drivers from NVIDIA or ATI. I have an ION mobo so I installed the latest nvidia drivers (256.44) and it was fairly easy -- download, execute, follow the prompts. https://help.ubuntu.com/community/NvidiaManual - crazytony - 2010-08-15 I have just done a complete reinstall and I can confirm that the lirc 0.86 shipped with Lucid works. Code: cat /proc/bus/input/devices Code: sudo dpkg-reconfigure lirc Code: âââââââââââââââââââââââââââââ⤠Configuring lirc ââââââââââââââââââââââââââââââ Select the input device seen in the Handlers variable in the cat command (event4 on my machine) Code: ââââââââââââââââââââââââââââ⤠Configuring lirc âââââââââââââââââââââââââââââ when the menu pops up select linux input layer as the remote control configuration Restart lircd run irw and adjust the Lircmap.xml accordingly. - Forsaken - 2010-08-30 Tried your little guide but no luck for me, irw didn't get anything. I do have a 15c2:0036, which is quirky, requires me to patch the kernel module for 2.6.32. - proctor - 2010-09-21 Thanks crazytony, I was able to get my imon remote working properly in maverick beta with your guide. - bsphere - 2011-01-29 crazytony Wrote:This will tell you if you have the kernel I don't think it's necessary to go to nvidia binary route. I just installed 2.6.35-23 so I could use ath3k. I grabbed the headers and then: Code: sudo apt-get install --reinstall nvidia-current nvidia-current-modaliases nvidia-settings I'm enjoying XBMC once more. Now, to find some user reports of people using the PS3 remote, my mobo has no IR. HTH In my admittedly limited experience, it's better to use the input by-id. - toddwv - 2011-01-29 If you use the input-layer event, then you risk having to reconfigure after every boot since the events are not statically assigned. If you plug-in a new device, say a usb pendrive, then your remote could end up on a different event. devinput method works but.. - elscotty - 2011-02-01 Hey guys i just created a new post about a similar issue, here then saw this, maybe you can help. I have a Fusion Black w the LCD, and have it working fine using the Linux Input Layer for now. However one thing I had configured on my Karmic box was to remove the front knob volume control functions from the XBMC config so it would control my alsa/pulseaudio mixer volume instead (ie: master gain for the whole system). Did this by creating a new remote file (pulseaudio) in my ~/.lirc/ and creating an include to it in my ~/.lircrc file. I have recreated this same scenario, naming the remote as 'devinput' but no alsa control. Any ideas. |