This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
misc:hacks:rasberrypi [2013-06-10 00:52] absoloodle37 Multiple additions (did not delete/change any existing content) |
misc:hacks:rasberrypi [2013-06-11 03:32] absoloodle37 included URL for software to move files from Win PC to RPi |
||
---|---|---|---|
Line 83: | Line 83: | ||
</ | </ | ||
- | **Note**: If you used a Windows 7 PC and the cfclient GUI to create | + | **Note**: If you created |
-save the new .json file as something different than the default, so you can recognize it easily. | -save the new .json file as something different than the default, so you can recognize it easily. | ||
Line 89: | Line 89: | ||
-the new .json file is not located in the Program Files(x64)/ | -the new .json file is not located in the Program Files(x64)/ | ||
- | -copy your new .json file into the correct RPi folder: / | + | -copy your new .json file into the correct RPi folder: / |
+ | |||
+ | < | ||
+ | |||
+ | Verify netatalk was installed successfully on your RPi by checking the Finder window on your Mac for a " | ||
-the cfheadless client on RPi may not recognize the same controller channel " | -the cfheadless client on RPi may not recognize the same controller channel " | ||
Line 157: | Line 161: | ||
</ | </ | ||
- | You can only create the cfheadless file above in the /root/bin/ folder by being root--not pi or any other user name. Switch to root: '' | + | You can only create the cfheadless file above in the /root/bin/ folder by being root--not pi or any other user name. Switch to root: '' |
+ | |||
+ | <code bash> | ||
+ | </ | ||
+ | |||
+ | The -h halts all processes, the -r is the command to reboot after shutdown. | ||
+ | |||
+ | This should now take care to startup the headless client when you plug in the dongle and (hopefully ;-)) kill it again when you unplug. If you need any additional setup to get your controller working, you can add a similar udev-rule for that to take care of everything upon plugging in the controller as well. An example for the Microsoft Wireless XBox360 controller for PC can be found [[http:// | ||
And for the XBox360 Controller (after an " | And for the XBox360 Controller (after an " | ||
Line 180: | Line 191: | ||
* / | * / | ||
- | Also, if xboxdrv can't be run without the sudo command, or there are other permissions issues with the xbox wireless usb controller, try adding the the xbox360 wireless receiver to a group that has root privileges. | + | Also, if xboxdrv can't be run without the sudo command, or there are other permissions issues with the xbox wireless usb controller, try adding the the xbox360 wireless receiver to a group you created |
+ | |||
+ | <code bash> | ||
+ | |||
+ | Also, if running the xboxdrv command from a terminal window gives you the following error: | ||
+ | |||
+ | <code bash> | ||
- | Also, if running the xboxdrv command from a terminal window gives you the following error: 'Error couldn' | + | ...your controller may very well have already started automatically per the udev rule you created above and could be working correctly and currently is in use. Make sure your wireless |
===== Make your base station portable ===== | ===== Make your base station portable ===== |