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

Bouvrie

Re: Dingoo just arrived! So, What now?
« Reply #15 on: October 26, 2009, 11:42:51 am »
Well, at least you've determined how to format the card now. :D

Just to recap, if I understand correctly, you tried to format 3 ways now:

1) Macbook, native formatting FAT32 failed.
2) Windows PC (assumed to be XP x86?), native formatting FAT32 failed.
3) Windows PC (assumed to be XP x86?), Panasonic SD formatting. 1st time failed, 2nd time worked.

Why did the 2nd Panasonic-based format work? Did you change its settings in any way?

As for the dev/mmcb1k0 panic: I think it's due to Dingux not being able to mount the SDcard correctly. Now that you managed to format the card with the right filesystem, you could try putting alternative (older?) rootfs and zImage files in your card's root to see if they work?
Write/save problems? Segmentation faults? Black screens? Read the Troubleshooting and FAQ guide first to fix your issues! :)
SD Card readonly/corruption issues? Chkdisk /F and steer clear from DMenu: use GMenu instead!

codiak

  • Guest
Re: Dingoo just arrived! So, What now?
« Reply #16 on: October 26, 2009, 12:39:43 pm »
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.

Absent (OP)

Re: Dingoo just arrived! So, What now?
« Reply #17 on: October 27, 2009, 11:55:32 pm »
Okay... Don't have midterm assignments while doing this. A lesson is learned.

So. To business.

Codiak, while fighting with this thing I've found one of your posts that says exactly that. Thus, that's all I've done.

Bouvrie, lets go through your list, shall we?
Macbook, native formatting FAT32 (which seems dubious to begin with) failed to boot.
Windows XP (I'm unsure what x86 means) native formatting FAT32 failed.
Windows XP Panasonic SD formatting.

Now, the first time I did this, I screwed it up. I set it to flash memory, which the card did not support, and afterwards it asked me to disconnect the device, which I didn't do. So the first time failed, and it was entirely my fault.

Second time, full format, flash erase off, format size adjustment on, success.

I think I already tried that, but what the hell, Ill give it another shot. I've got nothing else to do but keep re-formatting and trying different things until something works, someone solves this endless headache, or I get so frusturated that the next post I make is just one big red four-letter word.

Moral support, Goon. Don't underestimate it. I'm here battling for your future as much as my present, y'know.

Oh the drama
« Last Edit: October 28, 2009, 12:12:51 am by Absent »

Absent (OP)

Re: Dingoo just arrived! So, What now?
« Reply #18 on: October 28, 2009, 01:38:47 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.
« Last Edit: October 28, 2009, 03:01:09 am by Absent »

Bouvrie

Re: Dingoo just arrived! So, What now?
« Reply #19 on: October 28, 2009, 07:13:34 am »
Windows XP (I'm unsure what x86 means) native formatting FAT32 failed.
With the x86 part, I meant to ask whether it's a 32-bit Windows XP, or whether it's 64-bit. I'm assuming you're running a 32-bit WinXP?

All these fat32/sdcard issues are intruiging. I'll see if I can do some more testing with a spare minisd, to make some kind of detailed reports on what works and what doesn't.

Alternatively, perhaps there's a chance that a 1:1 raw clone of a working SDcard might help bypass any fat32-formatting related issues, I'll check into that too.

Basically I only have 1 (Kingston) miniSD adapter, so I can't rule out any adapter incompatibility...
« Last Edit: October 28, 2009, 10:56:43 am by Bouvrie »
Write/save problems? Segmentation faults? Black screens? Read the Troubleshooting and FAQ guide first to fix your issues! :)
SD Card readonly/corruption issues? Chkdisk /F and steer clear from DMenu: use GMenu instead!

Absent (OP)

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)

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)

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
  • e
  • 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