Author Topic: Dingoo just arrived! So, What now?  (Read 7069 times)

Absent (OP)

  • Posts: 43
Re: Dingoo just arrived! So, What now?
« Reply #20 on: October 29, 2009, 07:02:47 am »
Bouvrie, you rock SO HARD, word cannot express. I'm buying you a mafia of your choice.

I don't have access to the XP machine right now since the owners in bed, but since it just the piece-of-shit laptop the commerce students get at the beginning of the year, 32-bit is a safe bet. I'll let you know for sure though, edit this post or something.

Would partitioning the card help? How would I go about that?

I have another adapter on the way. Happy accident, helps rule out the stupid stuff.

My insufficient thanks.

Absent (OP)

  • Posts: 43
Re: Dingoo just arrived! So, What now?
« Reply #21 on: November 02, 2009, 07:07:26 am »
SUCCESS!
Fixed through formatting via a command prompt method mentioned in the FAQ thread.
Many, Many Thanks to everybody who posted advice in this thread. You all got/will randomly continue to get Karma.
Goon, if you read this, PM me and let me know when you get yours up and running. I'm pretty excited for you now.

So that's that, then. Thanks again!


Kalisiin

  • Guest
Re: Dingoo just arrived! So, What now?
« Reply #22 on: November 02, 2009, 08:24:43 am »
okay, I've tried reformatting this thing several times, each time with a different zImage and rootfs file on there, Ranging from oldest to newest.

They all give the same error message.

It doesn't seem to matter which toddlers pack they're paired with, or which SD card I use.

The Dingoo itself was flashed on the Mac first and then the Windows machine. I don't think that would be affecting this, but who knows.

Thanks to all. This is getting stupid.

I'm completely out of ideas.

If anybody has any ideas whatsoever


HELP!!!

The Big Fat Edit: This one COULD be important. My LCD type is ILI9331_3, NOT 9331 like I thought. The first time I loaded that screen, a whole bunch of digits got cut off for some reason, including the 1_3 of 9331_3.

Don't know if that one's significant, but it could be.

Did you re-name your zImage file?
There's TWO zImage files when you first put the local from Toddler on the system...neither is named correctly...you have to rename the one you need....and delete the other.

If you have the 331 screen use the zImage file the corresponds, rename it to just plain "zImage" and delete the 925 zImage file.

Are you taking that step?
« Last Edit: November 02, 2009, 08:26:17 am by Kalisiin »

Absent (OP)

  • Posts: 43
Re: Dingoo just arrived! So, What now?
« Reply #23 on: November 02, 2009, 02:09:48 pm »
...yeah, I took that step. It didn't want to mount the SD card. Kept giving an error code I hadn't seen anywhere else. Turned out I just needed to format the damned repulsive thing in a way I'd never heard of.

Thanks though!

Rebelphoenix

  • Posts: 161
    • Critical Indie Gamer
Re: Dingoo just arrived! So, What now?
« Reply #24 on: November 05, 2009, 11:50:15 am »
As I assumed in another post... the copy order seems to be important. (Format -> zImage -> rootfs -> local-dir)
I reformated my SD a few times with windows XP and never run into problems.

I ended up trying this and it works. I don't know why but that's what it does.

eule

  • * Former Staff
  • Posts: 889
Re: Dingoo just arrived! So, What now?
« Reply #25 on: November 05, 2009, 02:38:34 pm »
Okay...tried it on a different microSD card, same result, kernal panic error. message reads:
Reading kernal command line
FATAL: cannot mount dev/mmcb1k0,/dev/mmcb1k0p1 on boot
(17)
kernal panic - not syncing: Attempted to kill init!
Hmm, i had this error in the beginnings of Dingux, when the SD needed two partitions, one fat32, one ext3 (i think, it?s a long time ago  ;D). It happened, when the SD wasn?t partitioned in a right way, so the partitions couldn?t be mounted.
But as of now only one fat32 partition is necessary, so sorry, i don?t know what?s wrong. :-)

 

Post a new topic