Gp2x - Black Vs White, Good Vs Bad, F100 Vs F200


simonb

Member
Joined
Nov 6, 2007
Messages
141
Hey all,

So I bought an F200 a while back, when they first came out, and I was surprised (shocked?) to see all the people here debating which model was best.

I wanted to geek around on my GP2X - the user guides said you could usbnet the thing and ssh/telnet into it for doing dev work! Being a linux geek whose played around with Linux on arms before (handhelds.org stuff, for ipaq) I was desperate to see if I could tweak the system like I used to previously, bitterly recompiling stuff and replacing the default system binaries with esoteric replacements such as the code from Dan Bernstein, Felix Von Leitner, Uwe Ohse and others.

The shock and dissapointment when I realised that things were not so simple on the F200! The shock of discovering that GPH had removed the onboard netchip and simply replaced it with an SDHC card reader chip! The terrible realisation I may actually simply have to use this thing to play games! However, viewing this as a challenge I persevered and snarfed the kernel source, recompiled myself a pegasus.o module, plugged my F200 into the cable and with a bit of a painful hack about with sterm (touchscreen support on this would be awesome!) managed to modprobe, ifconfig, and get a remote terminal connection from another box to my F200. The rest is my history, and doesn't need repeating here.

Roll on a few months.

I decide I really need to see what the big fuss is about the F100, so I buy one from here, with the aim I can boot it up with a DC adaptor, leave it on all day and connect to it remotely so I can do some more dev experiments. Hell, it doesn't even matter /too/ much if I semi-brick it - long as I don't trash the boot loader, I can just whack the firmware back on...

... I've had nothing but pain from this unit. I've not got the networking connection to work as intended, and I've tried on windows, OSX, netbsd and linux host machines. I'm used to weird esoteric networking methods, and I've done usbnet before, but for love nor money I cannot get this thing to get on my LAN. Perhaps I'm doing something fundamentally wrong (though two days in I'd have assumed anything I was doing wrong would have been corrected by trial and error), so I guess a general point is perhaps the thing is broken. Or, perhaps I've hit that age whereby computers now really do hate me. But, I digress...

... Coming at this from the opposite way to most of the people on the forum here, owning both consoles in reverse order, I'd like to think I can put a unique perspective on the units. For me, the F200 wins hands down. But not on every point.

1) I've heard about longer boot times on the F200. The F100 I have is running firmware 3.0.0 (and yes, I know the 2.x.x firmware boots faster) and both devices near as dammit boot in the same time. Call that a draw.

2) Touchscreen support on the F200. No contest

3) SDHC support on the F200. No contest, though if someone can point me at a 3.0.0 bzImage with SDHC support I'll reconsider this point... slightly... I'll negate it if GPH produce an upgraded firmware for the F100.

4) I really dislike the joystick on the F100. I know this is a personal choice, indeed maybe I'm not used to it. Perhaps it is better if I change the cap. But, as it comes, it just ain't working for me. I concede the F200 buttons are a little fiddly, but I'm used to the them now. They do hurt a little, perhaps I need to develop my thumbskin. I really do just prefer the F200 and how it operates

5) The screen seems somewhat better on the F200.

6) The "Start" button. The F100 wins on this, as for some unknown reason GPH renamed it to the "home" button on the F200. This confuses people who I give the console too, as games say "press start". I have no idea why this was changed, it's just nonsensical.

7) Open2X. I guess the F100 wins on this score, as it's not being developed for the F200. However, I've not got a copy of Open2x to evaluate so this point doesn't carry any weight. (Apologies to KevCal, I'm wrong on this point, it is being developed for the F200)

8) Colour. I much prefer the black of the F100, and also the battery warning light. I wish GPH had included this on the F200

9) Power on LED. F100 wins no contest, the uber bright LED on the F200 reminds me of the time I had laser eye surgery.

10) Sound/Volume. I much prefer the F100's sound setup. The F200 "volume boost" for me simply equates to GPH turning the output up to 11, there's no need, it's too noisy and distorts. Even the short time it takes to turn the volume down in a game is a nightmare on the tube.


I'm happy to argue^Wdiscuss any of the points I've raised, but only with people who can articulate a decent argument. lolz.
 
The mini-USB port on F100's are very very picky about what kind of USB port they'll work on. The only port I've ever had any success with is a USB 1.0 port on my ancient Toshiba laptop.

You might try using an old USB1.0 hub on your USB2.0 ports, and try plugging the GP2X into the slower hub. Once you DO get it working, however, and have tasted the sweetness of running test builds on a mounted SMB share, and doing remote GDB debugging over the USBnet, you will curse GPH.

Anyways, yeah I'd have to agree with you on a lot of things. The F200's boot time, for example: I am even using FW4.0 and the difference in boot time just isn't that big. It's perfectly acceptable.

That comment about eye surgery regarding the F200 power LED is pretty spot-on, however. And my screen has interlacing problems. Normally this is very easily fixed because you'd go into the setup screen and use the adjustment utility on the F100, very simple. However, this utility is missing on the F200 FW 4.0! WHy!?!??!?
 
That's something I've noticed - have had major problems trying to get F100 connected via usbnet to my linux box - can ping, but no luck at all with telnet :( Have tried insmodding the g_ether.o(whatever) but still the same problem.
A linux 2.4 vs 2.6 problem I seem to hazily recollect...?
On Windows I have one usb that always works and others that work 'sometimes' - sometimes not at all - very strange.
 
The linux 2.4 v 2.6 problem is what g_ether.o is for, you need to replace the standard version.

I have no problems with it on my linux box.
 
Usually it's the usb cable rather than a usb port that's the problem. The cable that comes with the gp2x doesn't always work well for networking, and using a different cable will often solve the problem.

And there were a couple of unofficial SDHC firmwares for the F100 released ages ago. From what I've heard they don't work quite as reliably as fw4 though.
 
Hopefully there will be a new (last?) fw release for the F100 in the near future - there are quite a few changes in fw 4.0 ie.. not just f200 specific ones.
Of course, I'll be happy going to open2x when it comes out.....
I will look at g_ether.o again - I had the script that I thought had overwritten the driver file in the nand.. at least I thought that's what it did ;)
I will have another play connecting to my (linux) laptop soon as it would make developing even easier than it is now.
It was weird that I could ping, but not telnet or ftp (even though these were enabled on the gp2x) except from a windows box (ie to telnet I use my work windows pc).
 
Parkydr said:
The linux 2.4 v 2.6 problem is what g_ether.o is for, you need to replace the standard version.
If both hosts are running 2.4, you need replace g_ether? Or if the desktop linux box is on 2.6?
 
Last edited by a moderator:
Parkydr said:
What happened when I didn't have the right g_ether.o module was that the GP2X locked up on the first ping.
Ah... I'll have another look see.. :) cheers.

Does this look correct in /lib/modules/2.4.25/kernel/drivers/usb/gadget :
-rw-r--r-- 1 root root 36417 Jan 1 1970 g_ether.o
-rw-r--r-- 1 root root 34543 Sep 19 2006 g_file_storage.o
-rw-r--r-- 1 root root 34136 Sep 19 2006 net2272.o

Off topic: Did you get the speed increases you needed under Allegro inthe end?

jbrodack said:
open2x isn't being developed for the f200? I'd assumed it was being made for all models. and with the sucky firmware 4.0 we really need open2x for the f200
Who said it's not for the F200?
I said "Of course, I'll be happy going to open2x when it comes out....."
 
Last edited by a moderator:
Back
Top