Incmplete Sdl
- Thread starter jjoe
- Start date
Hobo
Member
same here
Digitalrat
Well-Known Member
- Joined
- Jan 8, 2005
- Messages
- 1,639
same problem here
Soyburg
Still Fresh
It's just a thought, but maybe worth a try. In the file install_libs.gpu the tar command is this:
tar -zxvf /mnt/sd/install_libs.tar.gz -C /
Maybe you can't add the files, because some of the files it extracts are already there and that causes the extraction to be aborted. So maybe if you append -k (keep existing files; don’t overwrite them from archive) to that, it will leave those. Something like
tar -zxvf /mnt/sd/install_libs.tar.gz -k -C /
might work. If it does: Good. Task completed. If it does not, then your best bet is on creating a little file (deinstall_libs.gpu for example) make it executable and have it remove the libraries you installed. Somthing like
#/bin/sh
rm your_path_and_library_here
rm your_next_path_and_library_here
rm your_next_path_and_library_here
cd /usr/gp2x
./gp2xmenu
should remove the libs you installed. Then a fresh run of the install script should work. Or so I am guessing. I am unsure however, whether the /lib/gconv directory was already there and had libraries in it, or whether it was added by the install script. If it was added, you might want to remove that too. But you should check first, whether there are files in it.
A small script along the lines of
#/bin/sh
ls -l /lib/gconv/* > /mnt/sd/whotsinthere.txt
cd /usr/gp2x
./gp2xmenu
should show you the content of that directory and then you could compare it with what you installed and what's in the install_libs.tar.gz archive. The output on my gp2x is
-rwxr-xr-x 1 root root 10908 Oct 17 2005 /lib/gconv/EUC-KR.so
-rwxr-xr-x 1 root root 15401 Oct 17 2005 /lib/gconv/ISO8859-1.so
-rwxr-xr-x 1 root root 91700 Oct 17 2005 /lib/gconv/SJIS.so
-rwxr-xr-x 1 root root 13268 Oct 17 2005 /lib/gconv/UTF-16.so
-rwxr-xr-x 1 root root 43131 Oct 17 2005 /lib/gconv/gconv-modules
-rwxr-xr-x 1 root root 48269 Oct 17 2005 /lib/gconv/libKSC.so
which is the same as in the archive and would suggest that it's safe to add a line to your removal script to remove that directory
rm -rf /lib/gconv
(which would delete the whole directory, so you wouldn't have to delete each single file in it).
Of course that's just guesswork and if you bork your gp2x in the process of doing any of this, you are completely on your own. Hope it helps anyway.
Last edited by a moderator:
Soyburg
Still Fresh
...would suggest that it's safe to add a line to your removal script to remove that directory
rm -rf /lib/gconv
that line should of course be among the other lines beginning with "rm", and not at the end of the skript.
rm -rf /lib/gconv
that line should of course be among the other lines beginning with "rm", and not at the end of the skript.
Vimacs
Don't be evil!
if you do that you get a nice brick!
PSyMastR
\m/O__O\m/
Last edited by a moderator:
daclassicgamingmaster
It Is Your Birthday.
someone already posted that image psy. get with the times
Last edited by a moderator:
PSyMastR
\m/O__O\m/
I know, I just like that image.
NeoStuey
Active Member
h34r: OUCH! h34r: I don't want to see anyone bricking their machine, so you guys be sure about what you're doing.
Last edited by a moderator:
Soyburg
Still Fresh
I am curious as what part of my post would do the brickifying. Could you please shed some light on this?
All I suggested was removing the partly installed libraries before reinstalling them again.
Thanks in advance, Guru.
Last edited by a moderator:
Soyburg
Still Fresh
Could you please explain how you went about installing only some of the libraries? Did you remove the ones you did not want to install from the tar.gz file? Or did you run the install script and then had the impression that not all were installed through that script?
Last edited by a moderator:
FFNoir
I
is there any way to unbrick a GP2X? Like loading an SD card with a flasher... cause I hear the GP2X can boot from SD...
Digitalrat
Well-Known Member
- Joined
- Jan 8, 2005
- Messages
- 1,639
Yes, there is a way. (trough the EXT-Port) ED flashes the units for free if you ordered from him.
The problem with the SDL-libs is just that you put them in a folder. They need to go directly on the card. (and don't uncompress the tar inside the tar
)I am also having a similar problem. I have installed the SDL-libs from a formatted card and SnesGP2x and NesGP2x both load and work OK, but NeocdGP2x, Quake, Unhexen all do not load.
When selected the screen goes black and then go back to main menu.
I tried adding -K to the line as suggested above by Soyburg, but this just goes to black screen and never goes back to main menu. The rest of that post unfortunatly goes right over my head and the mentions of bricking only cause me more concern.
Does anyone have any ideas on possible cause and solution?
Edit; Also would I be right in assuming that when the releases are HH, this will no longer be a problem?
When selected the screen goes black and then go back to main menu.
I tried adding -K to the line as suggested above by Soyburg, but this just goes to black screen and never goes back to main menu. The rest of that post unfortunatly goes right over my head and the mentions of bricking only cause me more concern.
Does anyone have any ideas on possible cause and solution?
Edit; Also would I be right in assuming that when the releases are HH, this will no longer be a problem?
Soyburg
Still Fresh
You are able to start the snes and nes emus. So the sdl libraries are properly installed. No need to fix that. Your problem must lie elsewhere. I haven't tried quake, but I got hexen working by copying the files uhexen.gpe and hexen.wad onto the card and then executing uhexen.gpe in the games menu. Two questions: You have got the hexen.wad, don't you? It's in the hexen shareware, which you can easily find on the web by googling for "hexndemo.zip". And did you put the two files into a folder? Try putting it onto the card directly, not into a folder. Hope that works for you.
As to why the screen went black and stayed there, when you put a "-K" into the tar line: (Assuming you really put a capital K in there) The script is case sensitive and it should have been a small k. A capital K in tar means "begin at file F in the archive) to which there was no argument, so tar would exit with an error and the script would end there. The order to bring up the menu again was in the last two lines of the script, but unfortunately, it exited before it could do that. In any case... No harm done.
Last edited by a moderator:
