Forum Replies Created

Viewing 35 posts - 1 through 35 (of 54 total)
  • Author
    Posts
  • smartroad
    Participant
    Post count: 76

    [quote=121381]I did see that link before but it not clear on how I update it :-(

    [/quote]

    Here is what I done:

    cd ~/RetroPie-Setup/scriptmodules/ports
    
    mv kodi.sh kodi.sh_15.2
    nano kodi.sh

    copy the code from the github wiki page and then press [crtl] + 'x‘ and then 'y' to save the new file.

    Load up the RetroPie script and find Kodi in the experimental menu and install as normal

    smartroad
    Participant
    Post count: 76

    I’d like to know how well the n64 and PSP emulators work :D Oh and maybe the Saturn one to Hehe

    smartroad
    Participant
    Post count: 76

    [quote=116763]White screens can happen for multiple reasons.

    – need to refresh ES for new theme
    – gpu split needs to be higher due to too many emulators
    – gpu split needs to be higher theme is heavy in graphics

    i think there might be another but those 3 are pretty common.

    [/quote]

    The key thing for me is that before updating to 3.5 (from a 3.4 install) I had no problems loading this with the number of emulators I have. simple-dark would load from boot with no issues. And I can get simple-dark to load after I have manually changed things.

    If the issue was the GPU memory not being enough I should never have been able to get it to work. Me confused! lol

    smartroad
    Participant
    Post count: 76

    [quote=116762]Not sure if this is helpful at all, but I’ve noticed that sometimes I will get “white screens” when choosing a new theme from inside ES, but then it will boot/load fine after quitting out of ES.

    [/quote]

    This happens after I have manually editied ES settings to carbon and then in ES switch to simple-dark, I have to restart ES. That is the weird part, it is fine doing that, just not when I do a total reboot.

    Even when previously (different install to this one) I switched to a theme that was nothing but white, the ES menus still popped up and worked. When I boot it is just a white screen and totally unresponsive to any input via gamepad or keyboard. The only way to get it doing anything is the SSH in and there I can edit, reboot etc.

    smartroad
    Participant
    Post count: 76

    [quote=116761]please post the output of ~/.emulationstation/es_log.txt after you have a whitescreen

    please post the contents of /boot/config.txt

    can use pastebin.com for the logs.

    [/quote]

    es_log: http://pastebin.com/dwixWSyj

    config.txt: http://pastebin.com/RZUz6Tbn

    smartroad
    Participant
    Post count: 76

    i have always used pi as the user and raspberry as the password.

    smartroad
    Participant
    Post count: 76

    So I deleted the powerblock directory totally and went back through the instructions. Still had the same issue :( Noticed it mentioned an error log file so have attached that. Seems like it is missing something, but I have done “sudo apt-get install -y cmake g++-4.9” which is what it asked for and it installed g++, said that cmake was already the up to date version.

    /PowerBlock$ make
    cd src/powerblock && make all
    make[1]: Entering directory '/home/osmc/PowerBlock/src/powerblock'
    cd ../lib/jsoncpp/ && mkdir -p build/release
    cd ../lib/jsoncpp/build/release && cmake -DCMAKE_BUILD_TYPE=release -DJSONCPP_LIB_BUILD_SHARED=OFF -G "Unix Makefiles" ../..
    -- The C compiler identification is unknown
    -- The CXX compiler identification is unknown
    CMake Error at CMakeLists.txt:2 (PROJECT):
      No CMAKE_C_COMPILER could be found.
    
      Tell CMake where to find the compiler by setting either the environment
      variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
      the compiler, or to the compiler name if it is in the PATH.
    
    CMake Error at CMakeLists.txt:2 (PROJECT):
      No CMAKE_CXX_COMPILER could be found.
    
      Tell CMake where to find the compiler by setting either the environment
      variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
      to the compiler, or to the compiler name if it is in the PATH.
    
    -- Configuring incomplete, errors occurred!
    See also "/home/osmc/PowerBlock/src/lib/jsoncpp/build/release/CMakeFiles/CMakeOutput.log".
    See also "/home/osmc/PowerBlock/src/lib/jsoncpp/build/release/CMakeFiles/CMakeError.log".
    Makefile:27: recipe for target '../lib/jsoncpp/build/release/lib/libjsoncpp.a' failed
    make[1]: *** [../lib/jsoncpp/build/release/lib/libjsoncpp.a] Error 1
    make[1]: Leaving directory '/home/osmc/PowerBlock/src/powerblock'
    Makefile:16: recipe for target 'all' failed
    make: *** [all] Error 2
    
    Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
    Compiler: CMAKE_C_COMPILER-NOTFOUND
    Build flags:
    Id flags:
    
    The output was:
    No such file or directory
    
    Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
    Compiler: CMAKE_C_COMPILER-NOTFOUND
    Build flags:
    Id flags: -c
    
    The output was:
    No such file or directory
    
    Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
    Compiler: CMAKE_C_COMPILER-NOTFOUND
    Build flags:
    Id flags: -Aa
    
    The output was:
    No such file or directory
    
    Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
    Compiler: CMAKE_CXX_COMPILER-NOTFOUND
    Build flags:
    Id flags:
    
    The output was:
    No such file or directory
    
    Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
    Compiler: CMAKE_CXX_COMPILER-NOTFOUND
    Build flags:
    Id flags: -c
    
    The output was:
    No such file or directory
    
    Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
    Compiler: CMAKE_C_COMPILER-NOTFOUND
    Build flags:
    Id flags:
    
    The output was:
    No such file or directory
    
    Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
    Compiler: CMAKE_C_COMPILER-NOTFOUND
    Build flags:
    Id flags: -c
    
    The output was:
    No such file or directory
    
    Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
    Compiler: CMAKE_C_COMPILER-NOTFOUND
    Build flags:
    Id flags: -Aa
    
    The output was:
    No such file or directory
    
    Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
    Compiler: CMAKE_CXX_COMPILER-NOTFOUND
    Build flags:
    Id flags:
    
    The output was:
    No such file or directory
    
    Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
    Compiler: CMAKE_CXX_COMPILER-NOTFOUND
    Build flags:
    Id flags: -c
    
    The output was:
    No such file or directory
    
    smartroad
    Participant
    Post count: 76

    Are you after the shaders? They are under the quickmenu when you are in an emulator

    smartroad
    Participant
    Post count: 76

    Still can’t get it to make :( followed instructions to the letter but just fails each time :(

    smartroad
    Participant
    Post count: 76

    [quote=115539]Update the RetroPie-Setup script then do a source install of the lr-gambatte. Reboot and by default it should launch in the pea soup green.

    [/quote]

    Didn’t change anything for me :( Best I have been able to get is a yellow/green. Ah well tis enough :)

    smartroad
    Participant
    Post count: 76

    [quote=115530]Marked as resolved. Thanks again herb, gizmo and floob. Working as intended.

    [/quote]

    What settings did you use? :)

    smartroad
    Participant
    Post count: 76

    I was just about to post up about this. I have tweeted on thegamesdb’s twitter account, but no communications either from Twitter or Facebook page :(

    smartroad
    Participant
    Post count: 76

    I mounted my USB stick as ~/RetroPie/roms/

    I formatted the disk to ext4 as it provided a good read/write speed compared to FAT (and I don’t plan on removing the drive anyway as I backup ROMs over the network).

    Then I found the drives unique ID (UUID) with this command

    ls /dev/disk/by-uuid

    once before I plugged in the drive and once after to see which uuid appeared. Once I knew the uuid I opened the fstab file:

    sudo nano /etc/fstab

    which opened as

    proc            /proc           proc    defaults          0       0
    /dev/mmcblk0p1  /boot           vfat    defaults          0       2
    /dev/mmcblk0p2  /               ext4    defaults,noatime  0       1
    # a swapfile is not a swap partition, no line here
    #   use  dphys-swapfile swap[on|off]  for that

    after /dev/mmcblk0p2 I added the line

    UUID=44916713-0138-40f9-a7de-68266894bd20 /home/pi/RetroPie/roms auto defaults 0 2

    this line is the UUID found in above, then the directory I want it to mount at, auto means automatically decide the filesystem, defaults is the default rw access (and some other stuff), 0 means don’t backup and 2 is the order for error checking. (See https://help.ubuntu.com/community/Fstab for more details).

    Next you need to delete the current contents on the /rom/ directory (make sure you have backups!!) so that it is empty – mounting devices needs to have empty mount points. I used WinSCP as it was easier than using the command line.

    Once the /rom/ directory is empty you just need to tell the system to remount the drives with

    sudo mount -a

    if you then type df -h you should see something like

    Filesystem      Size  Used Avail Use% Mounted on
    /dev/root        15G  2.7G   12G  20% /
    devtmpfs        364M     0  364M   0% /dev
    tmpfs           368M     0  368M   0% /dev/shm
    tmpfs           368M  5.3M  363M   2% /run
    tmpfs           5.0M  4.0K  5.0M   1% /run/lock
    tmpfs           368M     0  368M   0% /sys/fs/cgroup
    /dev/mmcblk0p1   57M   20M   38M  35% /boot
    /dev/sda1        59G  3.8G   52G   7% /home/pi/RetroPie/roms

    Maybe not the best way but works for me. One word of warning you have to unmount the drive manually if you want to take it out! Without doing it you will most likely end up with errors or data corruption. If the Pi is off then there is no issue taking it out.

    Although I formatted the drive to ext4 there is no reason why you couldn’t format it as FAT and then you could still access it with a Windows PC to.

    Not sure if this helps but was my solution :D

    smartroad
    Participant
    Post count: 76

    Awesome design!

    smartroad
    Participant
    Post count: 76

    Further refinements to the design. Ports line up much better and have more robust stand-offs. Also there is now a non-SNES version that can house PetRockBlog’s Power Block :D

    smartroad
    Participant
    Post count: 76
    in reply to: ROM folders #115278

    [quote=115218]I wouldn’t delete the folders, but deleting the contents of those folders should keep the emulators from showing up.

    [/quote]

    Thing is there is nothing in the folder and yet the option appears in ES :(

    smartroad
    Participant
    Post count: 76
    in reply to: ROM folders #115216

    Did you solve this? I am running 3.4 and would like to remove the x86 from emulation station. However when I go into the X86 room folder there isn’t anything in there but still the two x86 options show up in ES.

    smartroad
    Participant
    Post count: 76

    [quote=113803]If someone was to print this at home what is the cost roughly to print it as far as materials go?

    [/quote]

    The base uses about 20M of filament (50g)
    The upper case uses 24M (58g)
    The cover uses 18M (44g)

    Total of 62 meters or 152g of filament.

    Depending on who you buy filament from anything from about £5 up to £10 :) Hope this helps :D

    smartroad
    Participant
    Post count: 76

    I have updated the design, there is also now an option for the petRockBlock PowerBlock. An opening is on the side of the case for the microUSB connector, a 5mm hole on the front for an LED and an opening on the side for a rocker switch (opening 19.5 x 13mm).

    smartroad
    Participant
    Post count: 76

    [quote=109570]is retropie upgrading to jessie any time soon?

    [/quote]

    I think there is a start made to it. I believe you have to run the compile option though rather than being able to download the binaries.

    smartroad
    Participant
    Post count: 76

    Thanks guys. I was able to get it to work with WAV and ISO. The WAVs have to be uncompressed and named the same as the ISO with the track number after the name (starting at 2).

    Sonic CD.ISO
    Sonic CD 02.wav
    Sonic CD 03.wav

    Just converted the mp3s over.

    smartroad
    Participant
    Post count: 76

    Tried this but the system load times are awful. About 42 seconds to load on SD, well over a minute and a half on my USB stick. And the sticks read speed is twice that of the SD on my PC :(

    smartroad
    Participant
    Post count: 76

    Doh LOL

    Honestly thought about that, but was worried it would reset the controller not add an additional controller to it.

    Cheers!

    smartroad
    Participant
    Post count: 76

    I don’t think it should be a problem. The post I linked to just says Wheezy, nothing specific to the PI2 :)

    smartroad
    Participant
    Post count: 76

    Added a guide on how to install (partly for my reference and for anyone else who may want to try and see if it works for them!)

    smartroad
    Participant
    Post count: 76

    Print has been finished and is working well :D In total it was about 14 hours worth of printing in there. Really happy with the final look – can you guess which system I took inspiration from for the colour scheme? ;)

    smartroad
    Participant
    Post count: 76

    Does anyone have the files in the link for the video? It has died and I would like to get a main link rather than a link in the ports hub :)

    smartroad
    Participant
    Post count: 76

    Had an issue with old install so had to try again from scratch. However this time had a report of an error and have added to the issues in the scripts git entry.

    smartroad
    Participant
    Post count: 76

    Updated first post with picture of the base finishing printing :-)

    On our way :-D

    smartroad
    Participant
    Post count: 76

    [quote=107938]I like it. Looks like you’re throwing some SNES ports in the front?

    [/quote]

    Glad you like, just about to start the print :) I am going to put some SNES ports on front. Originally I was planning on just having it like a console with only those ports, but I really wanted to be able to use the new Amiga emulator for the PI 2. So thought about ways t get the USB ports out. Initially I was stuck thinking about getting small extension and panel mounted options. Then I had a flash of inspiration to just have a gap where the USB ports are in the case, mainly as I had visited a computer history museum that morning and I remembered the BBC Micro and the way its parallel and floppy ports were on the underside LOL.

    smartroad
    Participant
    Post count: 76

    I have the same issue, it is like EmuStat isn’t honouring the overscan settings?

    smartroad
    Participant
    Post count: 76

    Solved it by installing manually. Not sure why the script didn’t work tho?

    smartroad
    Participant
    Post count: 76

    Solved it. For some reason the WiFi kept dropping so when I was trying to update it wasn’t actually connected tot he network lol

    smartroad
    Participant
    Post count: 76

    I think all you should need to do is run the retropie_setup.sh script and tell it to update either the binaries or use the sources. If memory serves there is also an option to update the script as well, which probably should be done first!

    smartroad
    Participant
    Post count: 76

    I would suggest dumping the bios into the GBA rom directory via FTP/SAMBA, then SSH into the machine (or connect a keyboard and quit out of EmulationStation), and move from the GBA rom directory to the one you mentioned.

    Of the top of my head this should do it I think:

    cd into the GBA ROM directory
    mv gba_bios.bin /home/pi/RetroPie/emulators/gpsp/raspberrypi/ 

    you shouldn’t need root to use the command but just in case just add ‘sudo’ in front of the mv command.

    You won’t be able to find the correct directory on another machine (via FTP or SAMBA) as it isn’t shared, the only way is to manually copy it via the RaspberryPi.

    Hope this helps!!

Viewing 35 posts - 1 through 35 (of 54 total)