| Author | Thread |
User 26.10.2009 20:27:00 | Testdrive driver fails, and the remote doesn't work anymore | |
This posting is older than 6 months and can contain outdated information. Hi, Since the recent upgrades of Snow Leopard and RemoteBuddy, my remote doesn't work anymore. I did checked its battery (it is fine), and I don't think it is broken. Also, I don't know if it is related, when I run the testdrive driver, I got the following message :
___
Detected 32 Bit version of the driver and Snow Leopard - skipping unload
Executing '/bin/rm -drf "/private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/TemporaryItems/RBIOKitHelper.kext"' ..
Exited with code 0
Executing '/bin/cp -pr "/Applications/Support/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 0
Operation failed
___ My system is the following :
$ uname -a
Darwin arda.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386 Informations matériel : Nom du modèle : iMac
Identifiant du modèle : iMac6,1
Nom du processeur : Intel Core 2 Duo
Vitesse du processeur : 2,33 GHz
Nombre de processeurs : 1
Nombre total de cœurs : 2
Cache de niveau 2 : 4 Mo
Mémoire : 3 Go
Vitesse du bus : 667 MHz
Version de la ROM de démarrage : IM61.0093.B07
Version SMC (système) : 1.10f3 What can I do to have my remote working again ?
| These entries from the FAQ may be relevant to this topic: Driver 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
- Please make sure you have the latest version of Remote Buddy installed. If in doubt, download the latest version, quit Remote Buddy, delete it, empty your trash, then copy the downloaded version of Remote Buddy to your harddrive and start it from there.
- Please make sure, that you have installed the latest version of the Remote Buddy drivers. You can install the drivers using the Setup Wizard (=> access it via the Remote Buddy pulldown menu).
- Check your Remote Buddy settings in the Hardware category. Your remote control should be listed there and the lamp next to it should be green. If you don't find your remote control there, either the Remote Buddy drivers were not installed or installed in an outdated version - or - there is a general problem with the device. For USB devices, plugging the device to another port or resetting the PMU and/or SMC-unit of your Mac® (=> find guides on how to do this for your Mac® in the support area of apple.com) may help. If you can't find it under "USB" in the System Profiler (=> /Applications/Utilities) either, a hardware defect is as well possible.
- Check the batteries of your remote control.
- If your remote control has an on/off switch: make sure that your remote control is switched on.
- If your remote control requires additional receiver hardware: make sure that it is correctly attached to your computer and that it turns up in System Profiler.
- If you use an Apple® Remote, you should also check your system settings. Quit Remote Buddy, then open System Preferences.app > Security. Please make sure that the option to disable the infrared receiver is NOT active and click on "Unpair" should you have paired your Apple® Remote with your Mac®. After that, start Remote Buddy. If your Apple® Remote still doesn't work with Remote Buddy, please also check its preferences for the Apple® Remote. They can be found at Preferences > Hardware > Built-in IR receiver. If support for multiple remote controls is enabled there, ensure that your remote control is checked in the right table (=> you can find the correct entry for your remote control by pressing a button on it).
- If you are using a Keyspan™ RF Remote for Front Row, re-pair its remote control and receiver by simultaneously pressing the small knob on the back of the remote control and the knob on the receiver stick (the knob looks like the blinking LED, except it does not blink).
Hardware - Apple® Remote
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.
| User 26.10.2009 21:10:22 | Re: Testdrive driver fails, and the remote doesn't work anymore | |
This posting is older than 6 months and can contain outdated information. Thanks for asking. Remote Buddy requires its driver to be loaded for any access to real
hardware (including the Apple Remote IR Receiver). If you have an old
version of the Remote Buddy driver installed, newer versions will not
use it, but instead prompt you to update the driver. Once you have
updated the driver, Remote Buddy uses it and can access the hardware
again. Regarding the "Testdrive" option in the driver Setup Wizard: it is
currently only available under Snow Leopard when no previous/old
version of the driver is installed. Here are the two options available under Snow Leopard: 1) Use the "Uninstall" option to uninstall the old driver version
already installed on your Mac. Reboot , so that changes can take
effect. Then choose "Testdrive". It should work fine. 2) Use the "Install" option to upgrade the old version of the driver
to the latest version. Reboot, so that changes can take effect. Best regards,
Felix Schwarz
| User 26.10.2009 21:45:37 | Re: Testdrive driver fails, and the remote doesn't work anymore | |
This posting is older than 6 months and can contain outdated information. 2) Use the "Install" option to upgrade the old version of the driver to the latest version. Reboot, so that changes can take effect. I did uninstall the driver, rebooted, installed the driver, and rebooted again.
The "install driver" wizard says that the current installed and loaded version is 1.7.0. Nothing new, the remote is still inactive. Also, in "Preferences… > Hardware > Built-in receiver", in the left frame an Apple Remote is displayed with a green light, and there is nothing on the right panel (screenshot : http://www.zimagez.com/zimage/capturedacran2009-10-26214307.php) The following files are present on the system :
___
$ find /System/Library/Extensions/RBIOKitHelper.kext/ -type f -exec file {} \;
/System/Library/Extensions/RBIOKitHelper.kext/Contents/CodeDirectory: Mac OS X Code Directory version 20100 - 162 bytes
/System/Library/Extensions/RBIOKitHelper.kext/Contents/CodeRequirements: Mac OS X Code Requirement Set - 12 bytes
/System/Library/Extensions/RBIOKitHelper.kext/Contents/CodeResources: XML document text
/System/Library/Extensions/RBIOKitHelper.kext/Contents/CodeSignature: data
/System/Library/Extensions/RBIOKitHelper.kext/Contents/Info.plist: XML document text
/System/Library/Extensions/RBIOKitHelper.kext/Contents/MacOS/RBIOKitHelper: Mach-O universal binary with 2 architectures
/System/Library/Extensions/RBIOKitHelper.kext/Contents/MacOS/RBIOKitHelper (for architecture ppc): Mach-O object ppc
/System/Library/Extensions/RBIOKitHelper.kext/Contents/MacOS/RBIOKitHelper (for architecture i386): Mach-O object i386
/System/Library/Extensions/RBIOKitHelper.kext/Contents/PlugIns/RBIOKitHelper64.kext/Contents/CodeDirectory: Mac OS X Code Directory version 20100 - 164 bytes
/System/Library/Extensions/RBIOKitHelper.kext/Contents/PlugIns/RBIOKitHelper64.kext/Contents/CodeRequirements: Mac OS X Code Requirement Set - 12 bytes
/System/Library/Extensions/RBIOKitHelper.kext/Contents/PlugIns/RBIOKitHelper64.kext/Contents/CodeResources: XML document text
/System/Library/Extensions/RBIOKitHelper.kext/Contents/PlugIns/RBIOKitHelper64.kext/Contents/CodeSignature: data
/System/Library/Extensions/RBIOKitHelper.kext/Contents/PlugIns/RBIOKitHelper64.kext/Contents/Info.plist: XML document text
/System/Library/Extensions/RBIOKitHelper.kext/Contents/PlugIns/RBIOKitHelper64.kext/Contents/MacOS/RBIOKitHelper64: Mach-O 64-bit kext bundle x86_64
/System/Library/Extensions/RBIOKitHelper.kext/Contents/PlugIns/RBIOKitHelper64.kext/Contents/_CodeSignature/CodeDirectory: Mac OS X Code Directory version 20100 - 164 bytes
/System/Library/Extensions/RBIOKitHelper.kext/Contents/PlugIns/RBIOKitHelper64.kext/Contents/_CodeSignature/CodeRequirements: Mac OS X Code Requirement Set - 12 bytes
/System/Library/Extensions/RBIOKitHelper.kext/Contents/PlugIns/RBIOKitHelper64.kext/Contents/_CodeSignature/CodeResources: XML document text
/System/Library/Extensions/RBIOKitHelper.kext/Contents/PlugIns/RBIOKitHelper64.kext/Contents/_CodeSignature/CodeSignature: data
/System/Library/Extensions/RBIOKitHelper.kext/Contents/_CodeSignature/CodeDirectory: Mac OS X Code Directory version 20100 - 162 bytes
/System/Library/Extensions/RBIOKitHelper.kext/Contents/_CodeSignature/CodeRequirements: Mac OS X Code Requirement Set - 12 bytes
/System/Library/Extensions/RBIOKitHelper.kext/Contents/_CodeSignature/CodeResources: XML document text
/System/Library/Extensions/RBIOKitHelper.kext/Contents/_CodeSignature/CodeSignature: data
___ Thanks for your time :) Last edited: 26.10.2009 21:48:21
| User 27.10.2009 21:47:36 | Re: Testdrive driver fails, and the remote doesn't work anymore | |
This posting is older than 6 months and can contain outdated information. I did upgrade to driver 1.7.1 (RemoteBuddy v1.15.1), but no change : still no remote.
| User 28.10.2009 09:28:47 | Re: Re: Testdrive driver fails, and the remote doesn't work anymore | |
This posting is older than 6 months and can contain outdated information. Thanks for the update. Also, in "Preferences… > Hardware > Built-in receiver", in the left frame an Apple Remote is displayed with a green light, and there is nothing on the right panel (screenshot : http://www.zimagez.com/zimage/capturedacran2009-10-26214307.php ) No options are available for the Apple Remote itself, just for the
Built-In IR Receiver. The options set for the IR Receiver would be
interesting for this support case, though. Could you post a screenshot
of it? If possible, please also post a screenshot of System
Preferences > Security to see, what options are set for the IR
Receiver, there. Thanks in advance. Best regards,
Felix Schwarz
| User 28.10.2009 18:31:37 | Re: Testdrive driver fails, and the remote doesn't work anymore | |
This posting is older than 6 months and can contain outdated information. No options are available for the Apple Remote itself, just for the Built-In IR Receiver. The options set for the IR Receiver would be interesting for this support case, though. Could you post a screenshot of it? If possible, please also post a screenshot of System Preferences > Security to see, what options are set for the IR Receiver, there. Here they are :
http://www.zimagez.com/zimage/capturedacran2009-10-28182329.php http://www.zimagez.com/zimage/capturedacran2009-10-28182356.php I discovered those log as well, I guess you want them? If yes, tell me where to mail them:
~/Library/Logs/DiagnosticReports/Remote Buddy_2009-10-23-213711_arda.crash
~/Library/Logs/DiagnosticReports/Remote Buddy_2009-10-23-213936_arda.crash
~/Library/Logs/DiagnosticReports/Remote Buddy_2009-10-27-213245_arda.crash Thanks
| User 04.11.2009 19:19:46 | Re: Re: Testdrive driver fails, and the remote doesn't work anymore | |
This posting is older than 6 months and can contain outdated information. Thanks for the info. What happens, if you, at "RB Prefs > Hardware > Built-In IR Receiver",
you remove the entry with ID 141 and then press a button on your
remote. Is it re-added? Best regards,
Felix Schwarz
|
|
