Fast Boot Firmware - 15 Second Boots

[theoddbot]

telinit 2

At the terminal will kill the menu.

 

[CyberAxe]

since cramfs makes the nand read only would that effect flashing of the gp2xfile.img during unbricking?

 

[FluffyPanda]

Nope, it's not a hardware read protection. It's a read only file system but the chip can still be flashed just fine.

 

[critical]

telinit 2

At the terminal will kill the menu.

​

Thanks for that - works a treat (although my app still feels more sluggish than when launched from the menu). It used to work at normal speed when launched from the bash prompt on firmware 1.2.1, but now it behaves differently, I think.

 

[theoddbot]

critical: the menu probably set the clock speed back to 100mhz, you'll have to use a tweaker to change it back

 

[Hanz™]

Im getting 12 second boots now, so wtf is everyone still crying about to get a 9 second boot? geez, it aint even worth the extra work in my book <_<

​

Well the improvements are not just boot time, the new uboot is not self-bricking among many other improvements.

 

[critical]

critical: the menu probably set the clock speed back to 100mhz, you'll have to use a tweaker to change it back

​

Right - didn't realise it did that. Thanks for the tip.

 

[woogal]

critical: the menu probably set the clock speed back to 100mhz, you'll have to use a tweaker to change it back

​

Right - didn't realise it did that. Thanks for the tip.

​

I've just come across the same problem. I do almost all my testing from a shell rather than the menu, and the new 100mhz menu is really starting to get on my tits. Instead of using the clockspeed app I've just created a bash script that calls telinit 2 (as the menu automatically sets the speed back to 200mhz when it runs an app).

Why GPH decided to go to the effort of running the main menu at 100mhz is beyond me. Dropping the speed for around 10 seconds isn't going to make the slightest bit of difference to the battery life.

 

[critical]

I've just come across the same problem. I do almost all my testing from a shell rather than the menu, and the new 100mhz menu is really starting to get on my tits. Instead of using the clockspeed app I've just created a bash script that calls telinit 2 (as the menu automatically sets the speed back to 200mhz when it runs an app).

Sounds like the best way to deal with it, yes.

Why GPH decided to go to the effort of running the main menu at 100mhz is beyond me. Dropping the speed for around 10 seconds isn't going to make the slightest bit of difference to the battery life.

​

They do seem to have a talent for making the wrong technical decisions at every turn. If they ever decide to jack in the whole GPH thing, they'd have no trouble at all getting managerial positions at several places I've worked at.

 

[daclassicgamingmaster]

Im getting 12 second boots now, so wtf is everyone still crying about to get a 9 second boot? geez, it aint even worth the extra work in my book <_<

​

Well the improvements are not just boot time, the new uboot is not self-bricking among many other improvements.

​

Oh, so no one's mentioned that. There is a possibility that my gp2x can just randomly brick??

 

[nickspoon]

Im getting 12 second boots now, so wtf is everyone still crying about to get a 9 second boot? geez, it aint even worth the extra work in my book <_<

​

Well the improvements are not just boot time, the new uboot is not self-bricking among many other improvements.

​

Oh, so no one's mentioned that. There is a possibility that my gp2x can just randomly brick??

​

It's happened before, so yes. It's possible. However it's very very very unlikely, so don't worry about it.

 

[primeris]

Ok,
I have a flash-impaired system. As in, it won't flash ever at boot.
I depend on Robsters flash loading utilities to upgrade my firmware.
Anyway, I can't do step five of the cramfs instalation: "flash as normal".

And NO! My problem is not with my slew of SD cards. Robsters flash tester always gives me a nand write error 16 or something.

Help!

 

[sand_man]

You got a dodgy NAND?

 

[nickspoon]

He's got a bad NAND, theoddbot mentioned it.

 

[pcklee123]

I hope the development version comes out soon. I am in a dilemma now. Cramfs with fast boot or network with Qtopia telnet & samba but slow boot. Which should I use?

 

[BBTroll]

Build your own kernel with cramfs and network support.

 

[pcklee123]

Build your own kernel with cramfs and network support.

​

I was hoping someone cleverer than myself would do it first and share with us.

 

[aapje89]

Hmm...I had to use robsters firmware flasher to get to 1.4 because the "normal" way didnt work, but I still cant flash the "gp2xkernel.img", and yes I did run the .gpu first.

Is it possible to replace the 1.4 firmware that comes with the flasher with the cramfs firmware or would that brick my gp2x?

Edit: WOOOOOOOOT!!!, the damn thing flased
I did just the same routine as i had did hundred times before, but I used the cramfs firmware with the poison skin, and suddenly it flashed .

firmware I used:
http://archive.gp2x.de/cgi-bin/cfiles.cgi?0,0,0,0,42,1291

 

[triton]

nifty! im gonna give that a shot! mine would flash to the new firmware but it never got past the green screen so i flashed back to 1.2.1 meb this will work. i have a toshiba card

 

[mooseknuckle2000]

I just took the plunge....and this is AWESOME! Thanks theoddbot, this makes adding things and checking them much easier. Rock on