Thanks Colin,

To be honest, i’ve been doing it in my spare time over the the past few months and haven’t really kept a tally of everything. I would struggle a bit to make a guide now.

The tricky part was getting the pad to work. Eventually I realised non-genuine snes pads (even if they’re not USB) dont all work. Had to use proper original ones. Theres a member on here called FLOOB who has some great youtube tutorials that got me through a lot of the tweaks.

@bobchiba good to hear!
did you get both the controllers to work at the same time? i cannot have both the red lights at the same time :(
can you share this config you are talking about?

manually edit the TwinUSBJoystic.cfg file with the same button assignment as a PS3 controller

i’d love to have a look at it since i have only one controller working maybe it’s the config .. or maybe i should update to 3.0 as well :D

**WiFi Issues Update**

OK then I bought a cheap wifi dongle from Amazon – link below:

http://www.amazon.co.uk/dp/B00MXD2T5G

Inside it is a generic Ralink 148f:7601. Now Raspbian should supposedly natively support this, as I have the most up-to-date ‘Ralink’ firmware installed (according to apt-get install firmware-ralink), however it did not work at all. Neither my build nor the standard Raspbian install (direct from raspberrypi.org) could detect or set up this WiFi dongle.

I tried to install ‘WICD’ which is an alternative WiFi manager (with GUI) – no dice, it still could not find my dongle. I tried ‘WICD-CURSES’ which is the command line version of the same program – still no good, nothing found.

I done a Google search of ‘148f:7601’ and found others having the same problem with the Pi (and other Linux distros), and eventually found an updated firmware file on a Github page. I copied the file into the /lib/firmware/ directory inside Raspbian, rebooted then tried again. The standard Raspbian WiFi manager STILL couldnt see my WiFi adapter (on both my build and the standard build, using the ‘WPA_GUI’ utility), but when I tried WICD / WICD-CURSES – it works. It scanned and found a some SSIDS, I chose mine, entered the properties to update the password, tried to connect but it wouldn’t work. Found out I needed to change the DHCP Client to ‘dhclient’, tried it again and it worked, i.e. it has connected to my router and I am now able to browse the internet via WiFi. It also re-connects automatically on reboot.

So in conclusion – there is no problem with my build in regards to WiFi. It would instead seem as though Raspbian is in need of an update to include more / newer WiFi dongle firmwares. I can’t help you in the search of your own WiFi dongle drivers, however I can try and help with WICD:

You will need an ethernet cable plugged in before you continue!

To install WICD, open up a terminal (or SSH into the Pi), and type the following:

sudo apt-get install wicd

When it is finished installing, click on the start menu and go into the ‘Internet’ sub-menu. You should see ‘Wicd Network Manager’ – click on it and the network manager will appear. If your WiFi dongle is up and running already then it will scan and find any nearby SSID’s – click on your own, go to Properties and near the bottom of the page enter your WiFi password then go back and choose ‘Connect’. If it doesn’t connect first time then you may have to change your DHCP client from ‘Auto’ to a static value. To do this, click the drop-down menu button to the right of ‘Refresh’ at the top of the screen and then choose ‘Preferences’. Go into the ‘External Programs’ screen and choose a DHCP client from the list (there were only 2 options for me – I chose dhclient and it worked for me). Go back and try and connect again. It should hopefully work!

If you installed WICD and still couldn’t see any WiFi SSID’s then the chances are your driver / firmware is not installed for your dongle. To find out what driver you need, type in lsusb at the terminal. Here is my output:

pi@raspberrypi ~ $ lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 148f:7601 Ralink Technology, Corp.
Bus 001 Device 005: ID 046d:c077 Logitech, Inc.
Bus 001 Device 006: ID 0c40:8000

I can see an entry for Ralink Technology Corp. which I know is a manufacturer of WiFi chips, so that is my WiFi dongle. If you have a number of different USB devices plugged in then you may want to unplug them temporarily so you can identify your WiFi dongle easier. So I noted down the number next to my WiFi dongle entry – 148f:7601 – and searched for it in Google (search term 148f:7601 Raspberry Pi) to see if a driver exists. I soon found one, installed it, and it worked. You should hopefully be able to do the same thing.

Well, I hope this helps – its all I can really offer on this problem I’m afraid as it is a problem that is inherited from stock Raspbian. If you have difficulties in locating an updated driver for your WiFi dongle then I would suggest making a post at raspberrypi.org – thats where I found a thread on my own dongle.

Good luck!
Steve

It had been a project I’d wanted to do for a while, and it ended up taking forever to make by the time I’d gone through and fixed every little hitch I hit. As for selling it (there’s always one) I’d be unwilling to let it go for anything under a massive price due to the horrible development time and issues I had to overcome technically. Flicking through the build photos I’ve narrowed it down to two really good ones, and there’s a block of text to follow explaining everything least someone wishes to do the same, and yes, I very much feel there’s not nearly enough Tron in our lives! ;)

To start with I wanted it to be a N64 and had a broken one (so this isn’t a Ben Heckable mod because it was DOA, but you could swap the board out…), I also wanted to operate things using the original switch, which is a dual position four pole switch (very unusual) and use existing openings for ports etc. I cut the PCB and stripped it by desoldering all components, then decided on that gap there keeping the mounts for the front ports and the switch itself. The power input for the Pi is on the upper left through a modified USB 1 port (the power supply also had to be butchered to fit the new port, and I did this so that it would be impossible to put the light supply into the Pi supply), the one beside it powers the lighting so they don’t need to go all the time (12V 0.8A standard socket). I actually ended up removing the LED at the front because it used just enough current to drop the supply to the Pi below 5.28V which I wasn’t happy with. I did also go through and replace the wires with some higher voltage high copper ones just to ensure the unit always got a good supply. On the upper right you can see a simple HD corner connector which acts as video out and the four pole 3.5mm extension for audio/RCA. Cigarette lighter for scale, and up beside that is the scavenged computer plug for connecting the lighting which was done using a LED strip that was threaded throughout the shell. I wanted the Pi to be removable so glued some velcro to the case and the shell to shoulder it from jolts. The USB and audio cables had to be shortened to get them to fit and they range from about 60mm through to 120mm. The front ports were drilled out and shaped with a rotary tool and the female end was whittled into shape to fit. The top cover was cut with the rotary, given a few layers of undercoat, and that fancy white translucent plastic is simply ice-cream container. Finally I spent weeks trying to get some sort of a cool design for the logo before finally giving up because all attempts looked “fuzzy” in comparison with the rest of the design. Total cost: about $140 with excessive shelf usage, total dev time: about three months.

[quote=106959]Nevermind, I believe I may have found the answer to all my woes in the following links. Gonna stay up all night and skip church to see how this goes down. Fingers crossed!!!

http://bobbyromeo.com/technology/triple-boot-raspberry-pi-on-usb-raspbianretropieopenelec-part-1/

http://bobbyromeo.com/technology/triple-boot-raspberry-pi-on-usb-raspbianretropieopenelec-part-2/

http://bobbyromeo.com/technology/triple-boot-raspberry-pi-on-usb-raspbianretropieopenelec-part-3/

[/quote]

Hmmm… Im a little confused with this guide you have linked. It seems that he has made the process harder than it should be, although maybe that is due to the fact its designed to run off a USB stick instead of SD card. I really don’t understand how the OS switching occurs though? I have only skimmed through to be fair, but from what I gather the script to switch OS is triggered via SSH? That, to me, seems a little… odd, and un-intuitive. Maybe I have read it wrong, however I think that having a script to select in each OS that can be run natively on the Pi is a much more user friendly approach.

I intend to document my build process, in fact I have already started, but it will take a while til its finished. :/ To be fair its not a hard process that I follow, just very time consuming due to the fact I need to leave things in their ‘standard’ form all the time, so if I need to test then I need to go through the whole process every time from scratch – create the tarballs for each OS, copy to SD / USB, install, configure, test… takes a great deal of time! Especially when an error is found, small as it may be. Means that the process needs to be started over from scratch again. :/

P.s. its worth noting that when a card / USB stick gets to a certain size – 64gb and above – Windows will not allow formatting to fat32 so you have to revert to to a different program to force it to fat32 format. Even the ‘SD Formatting Tool’ will format to exfat on cards 64gb and above. There are plenty of free programs out there that will force format to fat32 so a quick Google search should get you what you need.

If using Linux then gparted works perfect for formatting to Fat32 on any size card you have.

Hi all.

There should be no problems with the install process for this build. Others have commented that it is working fine so the problem must be something at your end I’m afraid? Just to confirm – everything needs to be formatted strictly using Fat32, not exfat etc. I have tested this with a 16gb USB stick and 16gb and 32gb SD card and it works perfect for me. Maybe NOOBS doesn’t like large capacity USB sticks, but that is a total guess, and probably unlikely. All I can recommend is using a different method to format your USB stick as it is the stick that seems to be at fault if the OS choices are not showing. That or use a different USB stick altogether. I always use the same ‘USB’ build I compiled for NOOBS which works for my other dual boot builds so there is no reason why it won’t work for this too.

As for the WiFi issue – I have bought a WiFi dongle to test it myself. I’ll post if I find the problem but no timescales yet, just when I get the time to tinker with it.

And “sudo fdisk -l” reveals that my tiny little Sandisk USB stick is in fact showing up as /dev/sdb1

Probably because sda1 is in use by my 4Tb drive. I formatted it in NTFS format and it is not auto mounting under USB, why not?

I am trying to follow this guide:

http://linuxconfig.org/automatically-mount-usb-external-drive-with-autofs

replacing “udevinfo -a -p /sys/block/sdc/ | grep model” with “udevadm info -a -n /dev/sda1”

I get down to:

# /etc/init.d/udev restart
Stopping the hotplug events dispatcher: udevd.
Starting the hotplug events dispatcher: udevd.

Plug in external USB and your new base name is:

ls -l /dev/Iomega*
lrwxrwxrwx 1 root root 3 2011-02-23 12:36 /dev/Iomega -> sdc
lrwxrwxrwx 1 root root 12 2011-02-23 12:36 /dev/Iomega0 -> bsg/14:0:0:0
lrwxrwxrwx 1 root root 4 2011-02-23 12:36 /dev/Iomega1 -> sdc1
lrwxrwxrwx 1 root root 3 2011-02-23 12:36 /dev/Iomega3 -> sg3

Please note that /dev/Iomega1 points to a /dev/sdc1, which is exactly the partition we are interested in and we use it next to configure autofs.

——–

And I do not have the custom directory in /dev/

As a work around I updated to xbmc.sh script to read:

#!/bin/bash
sudo mount /dev/sda1 /mnt && kodi

Though I’d prefer if ALL of my drives auto mounted.