Support > Remote Buddy Forum > Problem with driver // IOSPIRIT [EN]

Support

All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.

Forum closed

This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview

Author

Thread

User

18.01.2010 18:06:04

Problem with driver

View

This posting is older than 6 months and can contain outdated information.

I was giving the remote buddy trial a spin on my iMac G5 with an eHome 2005 receiver connected and the driver does not appear to work.

Testrun has the following error:
Set 1 .. 0
Set 2 .. 0
Executing '/bin/rm -drf "/private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/TemporaryItems/RBIOKitHelper.kext"' ..
Exited with code 0
Executing '/bin/cp -pr "/Volumes/Remote Buddy 1/Remote Buddy.app/Contents/Resources/RBIOKitHelper.kext" "/private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/TemporaryItems"' ..
Exited with code 0
Executing '/usr/sbin/chown -R root:wheel "/private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/TemporaryItems/RBIOKitHelper.kext"' ..
Exited with code 0
Executing '/bin/chmod -R 755 "/private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/TemporaryItems/RBIOKitHelper.kext"' ..
Exited with code 0
Executing '/sbin/kextload -t "/private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/TemporaryItems/RBIOKitHelper.kext"' ..
Exited with code 256
kextload failed
Operation failed

Loading the kernel extension in terminal gives the following error:
kextload: kext /private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/TemporaryItems/RBIOKitHelper.kext is not valid
can't add kernel extension /private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/TemporaryItems/RBIOKitHelper.kext (validation error) (run kextload on this kext with -t for diagnostic output)
kextload: resolving dependencies for kernel extensions with validation and authentication failures
kernel extension /private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/TemporaryItems/RBIOKitHelper.kext has problems:
Validation failures:
{
"Executable file doesn't contain kernel extension code" = true
}
Warnings:
{
"A personality matches on IOResources but IOMatchCategory is missing or not equal to its IOClass (driver may fail to win matching)" = true
}

Installing the driver completely crashes my mac as soon as an ir command gets received.

Thanks in advance for any help!

These entries from the FAQ may be relevant to this topic:

Driver

What is the task of the driver and what do I need it for? (FAQ015E0177)
The Setup Wizard already contains a summary on how the driver does help Remote Buddy to provide additional features and hardware support. If that summary was too short, here's some more info on each of the points:
- fix for Apple® Remote driver problems in OS X
  Since OS X 10.4.9 (that includes 10.4.10/10.4.11/10.5.x/..) many users have been experiencing that one button press on their remote does now trigger two reactions - once from any currently running application that supports the Apple® Remote, once the default system action. So, this problem is not specific to Remote Buddy. The driver provides a clean, system conform fix to this problem using only documented APIs.
- enabling of all features of built-in IR receivers
  Only with the Remote Buddy driver do you gain support for arbitrary length button presses for the Play and Menu buttons as well as minimized reaction times for all buttons. While this may sound like unimportant technical details, they actually do have a strong practical impact. If, for example, you want to map a function to the Play or Menu button, that you want to see executed for as long as you press that button, this was previously simply impossible to achieve. This limitation still applies to all other applications. It does not for Remote Buddy with the driver loaded.
- the emulation of a virtual Apple® Remote
  Control applications that have support for and listen to an Apple® Remote - with any remote control of your choice supported by Remote Buddy. And on any Mac®. This allows you to f.ex. use iAlertU side by side with Remote Buddy or accessing special functions and modes inside applications that would otherwise require these apps to have full control over the built-in IR receiver of your Mac® - and that your Mac® actually came with one.
- support for Bluetooth® remotes and external receivers
  It's not possible to reliably operate many Bluetooth® based remotes, like for example the Wii® Remote with a Mac® purely from userspace due to limitations in the operating system. The situation for many external receivers is similiar: some of their features - or the entire device - can only be supported with the help of a driver.

Hardware - Apple® Remote

After uninstalling/quitting Remote Buddy, my Mac® no longer reacts to the Apple® Remote. (FAQ015E0241)
To enable you to use all capabilities of the IR Receiver of your Mac®, Remote Buddy is using its own driver. In contrast, all other applications with integrated Apple® Remote support usually use the OS X Apple® Remote subsystem.

As long as you're running Remote Buddy, Remote Buddy and its driver are responsible for turning the received button presses into actions. As soon as you quit Remote Buddy, this task is again handled by the OS X Apple® Remote subsystem.

If other applications don't use the interface to the OS X Apple® Remote subsystem correctly, this can lead to the effect that nothing happens when you press a button on your Apple® Remote. For as long as you're running Remote Buddy, issues like this are covered by Remote Buddy and it's driver and are therefore not visible to you. However, as soon as you quit Remote Buddy, the OS X Apple® Remote subsystem is back in control and any issues caused in it by other applications become visible.

Therefore Remote Buddy is neither the cause of the issue nor is it responsible for it. Instead, the cause of the issue exists independently of Remote Buddy. It's located elsewhere and can also only be solved there.

Although our products can't cause any such issues, we're regularly contacted about such issues and asked for help. In order to make locating and fixing the cause of such issues as easy and efficient as possible, we've developed a free diagnostics tool: Remote Control Diagnostics. It can locate issues with a single click and will provide you with information about the issue as well as with instructions on how you can fix it.

Hardware - eHome 2005

My MCE/eHome receiver is not recognized - is it supported? (FAQ015E0192)
Remote Buddy currently only supports the models as listed under "Supported Hardware".
If you own a receiver that is being advertised for with a Windows®-Logo on the packaging or that comes bundled with a remote that has a Windows®-Logo printed on it:
Please file a support inquiry with the exact name of your receiver, as well as with the USB vendor and product ID as displayed in "System Profiler" for this device. We can then check whether we may be able to add support for your receiver in a future version.
Do you currently support the MCE remote bundled with many eHome 2005 receivers? (FAQ015E0179)
This remote control is currently not supported. Support for it may be available in the future, though.

User

18.01.2010 22:40:11

Re: Problem with driver

View

This posting is older than 6 months and can contain outdated information.

Thanks for asking.

Which version of Remote Buddy are you using?

kextload does always report an "error" under OS X 10.5 because OS X 10.5 didn't have support for Intel 64 Bit drivers. It nonetheless does load the i386/ppc part of the driver just fine. The latest versions of Remote Buddy know about this odd behaviour of kextload on OS X 10.5 systems and only will report an error when there really is one - and not in the case where kextload returns an error although there isn't any.

If your Mac crashes, please send in the panic log and a System Profile (in XML/SPX format) to the email address as found in the Imprint ( http://www.iospirit.com/imprint/ ).

Best regards,
Felix Schwarz

Remote Buddy
Support
1. Overview
2. Manuals
3. FAQs
4. Forums
1. Lost license code
2. Support inquiry
IOSPIRIT
1. About us
2. Blog
3. Labs
4. Developers
1. Contact
2. Press releases
3. Imprint
4. Jobs