GPIO driver installation broken ?

This topic has 9 replies, 3 voices, and was last updated 11 years ago by Anonymous.

Viewing 10 posts - 1 through 10 (of 10 total)

Author

Posts
11/10/2013 at 13:40 #3144

Anonymous
Inactive

Hi everybody,

First of all, thanks for all your hard work on this project.
It’s amazing.

I post this message because I have issues to install the GPIO driver since the last RetroPie project. I managed to install it successfully in my previous installation.

A few days ago, I reinstalled everything from the last release. I did the binaries compilation and everything is fine. Then, I tried to install the GPIO driver to use my psx pad. Unfortunately, the installation fails (option 11 of the SETUP menu).
I see that the script tries to download some deb package from an URL containg “niksula” followed by a 404 error. It’s difficult to see this lines as the treatment is fast and the script go back immediately to the menu…

I think that may be a broken link… any idea ?
thank yo ufor your help.

11/10/2013 at 23:31 #3147

Anonymous
Inactive

I managed to get a picture from the super fast console output.
Apparently the script fails to find the linux-headers-3.6.11-rpi-aufs package.

the command uname -r gives me : 3.6.11-rpi-aufs
so its seems my current installation was the good version.

then, i did a rpi-update, it seems the downloaded kernel is 3.10.10+.
however, after firmware update and reboot, uname -r still gives me 3.6.11-rpi-aufs

there is a linux-headers-3.6.11+ file in /usr/src/ .

i read that the gamecon drivers needs to be reinstalled after a kernel update. SO, that’s what I tried in with RetroPie script… it seems something is missing somewhere to make the link between the RetroPie script and the linux headers.

I continue my investigations…

11/13/2013 at 21:35 #3152

petrockblog
Keymaster

Marqs has pushed an update to the RetroPie Setup Script (see https://github.com/retropie/RetroPie-Setup/pull/243).

Does this solve your issue?

11/14/2013 at 00:57 #3153

Anonymous
Inactive

It didn’t. Here’s what I did.

1. installation of the RetroPie 1.9 image.
2. sudo apt-get update
3. update of the firmware through retropie setup script
4. install/update of the gamcon drivers via retropie instal lscript

At this step, I obtain this output. It seems gcc4.7 is installed but I still got the 404 error.

Hit http://raspberrypi.collabora.com wheezy Release.gpg
Hit http://archive.raspberrypi.org wheezy Release.gpg
Hit http://mirrordirector.raspbian.org wheezy Release.gpg
Hit http://raspberrypi.collabora.com wheezy Release
Hit http://archive.raspberrypi.org wheezy Release
Hit http://mirrordirector.raspbian.org wheezy Release
Hit http://raspberrypi.collabora.com wheezy/rpi armhf Packages
Hit http://archive.raspberrypi.org wheezy/main armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/main armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/contrib armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/non-free armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/rpi armhf Packages
Ign http://archive.raspberrypi.org wheezy/main Translation-en_GB
Ign http://raspberrypi.collabora.com wheezy/rpi Translation-en_GB
Ign http://archive.raspberrypi.org wheezy/main Translation-en
Ign http://raspberrypi.collabora.com wheezy/rpi Translation-en
Ign http://mirrordirector.raspbian.org wheezy/contrib Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/contrib Translation-en
Ign http://mirrordirector.raspbian.org wheezy/main Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/main Translation-en
Ign http://mirrordirector.raspbian.org wheezy/non-free Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/non-free Translation-en
Ign http://mirrordirector.raspbian.org wheezy/rpi Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/rpi Translation-en
Reading package lists…
Reading package lists…
Building dependency tree…
Reading state information…
dkms is already the newest version.
gcc-4.7 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
dpkg-query: no packages found matching linux-headers-3.6.11-rpi-aufs
–2013-11-13 23:54:02– http://www.niksula.hut.fi/~mhiienka/Rpi/linux-headers-rpi/linux-headers-3.6.11-rpi-aufs_3.6.11-rpi-aufs-2_armhf.deb
Resolving http://www.niksula.hut.fi (www.niksula.hut.fi)… 130.233.43.7
Connecting to http://www.niksula.hut.fi (www.niksula.hut.fi)|130.233.43.7|:80… connected.
HTTP request sent, awaiting response… 404 Not Found
2013-11-13 23:54:04 ERROR 404: Not Found.

dpkg: error processing linux-headers-3.6.11-rpi-aufs_3.6.11-rpi-aufs-2_armhf.deb (–install):
cannot access archive: No such file or directory
Errors were encountered while processing:
linux-headers-3.6.11-rpi-aufs_3.6.11-rpi-aufs-2_armhf.deb
rm: cannot remove `linux-headers-3.6.11-rpi-aufs_3.6.11-rpi-aufs-2_armhf.deb’: No such file or directory
gamecon is the newest version
db9 is the newest version
ERROR: Module gamecon_gpio_rpi not found.

11/14/2013 at 22:03 #3158

petrockblog
Keymaster

Does it help, when you update the RetroPie Setup Script first (“git pull” from within the RetroPie-Setup folder)?

11/18/2013 at 00:58 #3175

Anonymous
Inactive

I tried with the “git pull” command from the Retropie-setup and it gives me:
Already up-to-date.

Just in case, I tried again after this command and I obtain the same output as above. As it’s a 404 error, is it related to the script ?

Starting installation.
Hit http://raspberrypi.collabora.com wheezy Release.gpg
Hit http://archive.raspberrypi.org wheezy Release.gpg
Hit http://mirrordirector.raspbian.org wheezy Release.gpg
Hit http://raspberrypi.collabora.com wheezy Release
Hit http://archive.raspberrypi.org wheezy Release
Hit http://mirrordirector.raspbian.org wheezy Release
Hit http://raspberrypi.collabora.com wheezy/rpi armhf Packages
Hit http://archive.raspberrypi.org wheezy/main armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/main armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/contrib armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/non-free armhf Packages
Hit http://mirrordirector.raspbian.org wheezy/rpi armhf Packages
Ign http://archive.raspberrypi.org wheezy/main Translation-en_GB
Ign http://raspberrypi.collabora.com wheezy/rpi Translation-en_GB
Ign http://archive.raspberrypi.org wheezy/main Translation-en
Ign http://raspberrypi.collabora.com wheezy/rpi Translation-en
Ign http://mirrordirector.raspbian.org wheezy/contrib Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/contrib Translation-en
Ign http://mirrordirector.raspbian.org wheezy/main Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/main Translation-en
Ign http://mirrordirector.raspbian.org wheezy/non-free Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/non-free Translation-en
Ign http://mirrordirector.raspbian.org wheezy/rpi Translation-en_GB
Ign http://mirrordirector.raspbian.org wheezy/rpi Translation-en
Reading package lists…
Reading package lists…
Building dependency tree…
Reading state information…
dkms is already the newest version.
gcc-4.7 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
dpkg-query: no packages found matching linux-headers-3.6.11-rpi-aufs
–2013-11-13 23:54:02– http://www.niksula.hut.fi/~mhiienka/Rpi/linux-headers-rpi/linux-headers-3.6.11-rpi-aufs_3.6.11-rpi-aufs-2_armhf.deb
Resolving http://www.niksula.hut.fi (www.niksula.hut.fi)… 130.233.43.7
Connecting to http://www.niksula.hut.fi (www.niksula.hut.fi)|130.233.43.7|:80… connected.
HTTP request sent, awaiting response… 404 Not Found
2013-11-13 23:54:04 ERROR 404: Not Found.

dpkg: error processing linux-headers-3.6.11-rpi-aufs_3.6.11-rpi-aufs-2_armhf.deb (–install):
cannot access archive: No such file or directory
Errors were encountered while processing:
linux-headers-3.6.11-rpi-aufs_3.6.11-rpi-aufs-2_armhf.deb
rm: cannot remove `linux-headers-3.6.11-rpi-aufs_3.6.11-rpi-aufs-2_armhf.deb’: No such file or directory
gamecon is the newest version
db9 is the newest version
ERROR: Module gamecon_gpio_rpi not found.

11/19/2013 at 07:07 #3184

petrockblog
Keymaster

The game con driver is developed and maintained by a guy called “Marqs”. His original post about the driver can be found at http://www.raspberrypi.org/phpBB3/viewtopic.php?f=78&t=15787&p=453958&hilit=gamecon#p453958.

Until now, Marqs has always given an update when Raspbian was updated. Unfortunately, I cannot give any detailed support on the driver or even the needed files for that.

Maybe you can post this issue on the forum thread that I gave above.

11/21/2013 at 19:28 #3201

smartroad
Participant

Did you ever find a solution to this as I think this is the same error I am hitting now.

11/21/2013 at 21:01 #3204

smartroad
Participant

I think I have figured out part of the problem for me. When the RetroPie Setup script looks for the linux-headers file it is looking for (with mine) linux-headers-3.10.19+_3.10.19+-2_armhf.deb which isn’t on the website. I tried to manually do 3.10.18 but it errors, not surprising as it is the wrong version but worth a shot.

11/22/2013 at 00:51 #3205

Anonymous
Inactive

Hello!

So finally after many investigation and thanks to some ideas coming from your link, petrockblog I may have understood the error.

In fact, I think it came from… my berryboot installation !
I checked the code of the RetroPie script for the driver installation and saw that everything is based on the command ‘uname’ to determine the current linux kernel version.
That’s fine, excepted that the uname command was ALWAYS giving me 3.6.11-rpi-aufs, whatever the firmware that I compiled in raspbian! After some search on internet, I discovered that berryboot seems to manage alone the /boot directory and mount it when launching an image.
In my case, berryboot was launching the retropie image, mounted its own partition (and its firmware) into /boot and strangely, no firmware update was throwing an error… it’s like if the firware update worked, but the active firmware was still version 3.6 (from /boot, i.e. berryboot installation).

I starting everything again from a SD formating, using NOOBS to do a dual boot with OpenElec and Raspbian (where I installed RetroPie). The firware updates worked fine, the unmae command gave me the good versions and the driver update was successfull.

Conclusion, a BerryBoot boot of the RetroPie image may be incompatible with the current script to install the GPIO driver. Does anyone boot successfully RetroPie after a BerryBoot startup ?

@smartroad: hope this helps?
Author

Posts

Viewing 10 posts - 1 through 10 (of 10 total)

The forum ‘Everything else related to the RetroPie Project’ is closed to new topics and replies.

Login