Hacking neek2o

  • Thread starter Thread starter obcd
  • Start date Start date
  • Views Views 329,503
  • Replies Replies 1,533
  • Likes Likes 5
...after postloader. :P


But it seems I've missed a few updates since testing postloader plugins and devolution...from what I can tell, between r83 and r88 (as of writing the latest) my issue seems to be gone. I'll have to test some more to know for sure, but it's certainly looking good. :)


EDIT: damn...for some reason, my wii fails to start now (flashing blue console slot). At first, I thought it had to do that the procedure for modifying the config.bin files was a bit different than creating them (removing those files made it work...once). But now it seems it won't boot at all anymore. Or create a diconfig.bin file (it only creates a nandconfig.bin). :unsure:

I'll see if rev87 is any better.
EDIT2: apparently not...damn. :unsure:
 
Phew...this issue is starting to get on my nerves...

Checkdisk on both the SD card and USB drive came up with nothing. Clearing cache files and the sneekcache files in the nand did nothing. Neither does using a fresh modmii-generated nand.
On IRC I've tested out r89beta1, but even that doesn't make a difference.

All it does is just sit thee and blink the USB drive evenly about every 0.75 second. There's no USB acitivity.

Whatever error it is, it must have been introduced somewhere in r85 or 86, as r84 still works.

Too bad I don't have a USB gecko. :(


EDIT: after trying another SD drive and getting nowhere, I thought of another thing. This time one that actually worked (okay, once. Still gotta test things, but it's enough to throw a theory).

When I hacked my girlfriend's wii, neek2o wouldn't boot. This was pretty weird, as everything was done correctly. As it turned out, the USB spin of that hard drive up was a bit too slow. bootmii had already checked for a hard drive, concluded it wasn't there and had moved on by the time the thing became available.
Obviously, my own hard drive is fast enough. Or rather...it used to be fast enough. My theory is that the changes in r87 either improved the startup time to such a degree that my hard drive can't start fast enough anymore, or that extra initialisations of some kind were added to the hard drive so it can't return a "present" when bootmii asks for it.
Of course, this is just theory. All I can say in practice is that if I boot my wii directly, it won't work. If I start it in real nand mode and THEN switch to neek2o, things work fine.


EDIT 2: okay...this is the main reason why I tend to write things down on fora: you'll never know who can learn from it. Heck...it could even be yourself! In this case: I looked up my own post on the matter. And simply applied it.
It's kind of a pity that I'm not using bootmii @boot2 to boot into neek2o directly (have to take a detour), but at least my neek2o installation starts now. :)
 
EDIT 2: okay...this is the main reason why I tend to write things down on fora: you'll never know who can learn from it. Heck...it could even be yourself! In this case: I looked up my own post on the matter. And simply applied it.
It's kind of a pity that I'm not using bootmii @boot2 to boot into neek2o directly (have to take a detour), but at least my neek2o installation starts now. :)

i shouldve read your post to realize you had the same problem, it was just too long for me..
well i had the same problem, so it was really introduced in the newer revisions.
your workaround works for me too, so it has to be something with the boot2 booting. thanks for posting wever!
i was about to reformat my drive.. :D
 
Need help trying to get neek2o to start. Hangs on black screen. waited 20 minutes. HDD light flashes but nothing seems to happen. The only thing I noticed is nandcfg.bin is made but not the dicfg.bin.

I have a 4gb usb flash drive that works great but there's obviously no room for anything but my emu-nand. I tried neek2o last year (r64 or r68) and managed to get it to work by starting postloader and having it autoboot the neek2o channel and then emu nand priiloader would run postloader. but that doesn't seem to work anymore.

I was thinking - can i just do neek2o without the +DI and launch wiiflow from the neek2o emu-nand whenever I want to run a wii or GC game? Any help getting neek2o to work would be great. I'm pretty sure I have one of those slow spin up drives.
 
fledge, a few things pop up in my mind...

neek2o is very picky, it needs a FT32 partiton as first partition with a 32KB clustersize.
The hdd itself can also be a problem, if nswitch or the neek2o channel are not working, try the workaround wever mentioned in a few posts back.

Ofcourse you can also come to the IRC #cdi channel on abjects...
 
When I have had difficulty on first run of neek2o, I was able to solve the issue making an original sneek nand on sd, start and configure it, than use that nand for neek2o.
 
fledge, a few things pop up in my mind...

neek2o is very picky, it needs a FT32 partiton as first partition with a 32KB clustersize.
The hdd itself can also be a problem, if nswitch or the neek2o channel are not working, try the workaround wever mentioned in a few posts back.

Ofcourse you can also come to the IRC #cdi channel on abjects...
I just checked my hdd and it seems to be 64k cluster size. so that means I'm screwed right? because I have to format my drive to change it to 32k right?

Why won't neek2o work with a nand on sd card? I have a 16gb sd card for dml which i don't need anymore and could easily use that for my emu nand.
 
I just checked my hdd and it seems to be 64k cluster size. so that means I'm screwed right? because I have to format my drive to change it to 32k right?

Why won't neek2o work with a nand on sd card? I have a 16gb sd card for dml which i don't need anymore and could easily use that for my emu nand.
Yes, 64 KB clustersize is not going to work...

Neek2o still seems to have a bug, it should work on SD though...i hope OverjoY can look at it very soon..
But if you are going to try keep in mind that neek2o from sd is a different build, you can't just copy the neek files to SD...
(but i bet this is something you already knew ;) )
 
Because some people have issues booting into neek with the newer revs, I will create a kernel with verbose output for the FS USB module to the USB device tonight.

The people that have issues booting into neek can pm me or visit me on IRC if they wanna have a link for this
 
I was just going to post an update on my situation.

As stated in my previous posts, since r87* I can't boot directly into neek2o anymore (see above for my personal workaround).

However...today, I started wondering...

Since neek2o requires the following files...

SD:\sneek\kernel.bin
USB:\sneek\kernel.bin (the same file as on SD)
USB:\sneek\di.bin

...what would happen if I downgraded just the SD file to r84?

The result: neek2o boots again. But honestly, I have no idea WHY. And neither if it's stable.

So some extra output would be nice. Especially now it turns out I'm not the only one with this.
(in fact, aside from my girlfriend and Pizzapino, I also tested it with a completely different hard disk yesterday. That one also doesn't like to boot from bootmii@[member='boot2490']).




*it worked in r84
 
...what would happen if I downgraded just the SD file to r84?

Are you booting directly from bootmii ? If yes I guess you are simply running r84 the first boot, then on return to menu (for example exiting from a game) it may load r87 from isfs (usb).... but it is just a speculation...
 
Is Dios mios compatible with neek2o ?

Yes, DM and DML are compatible with neek2o - you just need to place the 00000008.app in the correct place on your emu nands (title\00000001\00000101\content).

However, there is a bug that affects some users that prevents DM usage on neek2o. Sadly, I'm one of those people - when I try loading GC games with neek2o, the wii shuts down.
 
Is Dios mios compatible with neek2o ?

Yes, DM and DML are compatible with neek2o - you just need to place the 00000008.app in the correct place on your emu nands (title\00000001\00000101\content).

However, there is a bug that affects some users that prevents DM usage on neek2o. Sadly, I'm one of those people - when I try loading GC games with neek2o, the wii shuts down.
The bug is that it doesn't use the emulated MIOS (assuming it works for some to begin with...I can't remember reading from someone with neek2o who got it working that way)

Just install the DM wad on your real nand. That'll get it working.
(there's no need for that .app in the correct place either)
 
The bug is that it doesn't use the emulated MIOS (assuming it works for some to begin with...I can't remember reading from someone with neek2o who got it working that way)

Just install the DM wad on your real nand. That'll get it working.
(there's no need for that .app in the correct place either)

Thanks wever, I've already installed dm on the real nand, so I will try using the original 00000008.app on my emunand and then test out a GC game.

EDIT: Yep - this information worked for me! I use neek2o for everything now, so I'm happy that I don't have to switch to the real nand for playing GC games.
 
The bug is that it doesn't use the emulated MIOS (assuming it works for some to begin with...I can't remember reading from someone with neek2o who got it working that way)

Just install the DM wad on your real nand. That'll get it working.
(there's no need for that .app in the correct place either)
It seems the xNEEK download for DIOS MIOS has been deprecated: http://code.google.c.../downloads/list . I wonder what this means…
 
Is Dios mios compatible with neek2o ?

Yes, DM and DML are compatible with neek2o - you just need to place the 00000008.app in the correct place on your emu nands (title\00000001\00000101\content).

However, there is a bug that affects some users that prevents DM usage on neek2o. Sadly, I'm one of those people - when I try loading GC games with neek2o, the wii shuts down.
The bug is that it doesn't use the emulated MIOS (assuming it works for some to begin with...I can't remember reading from someone with neek2o who got it working that way)

Just install the DM wad on your real nand. That'll get it working.
(there's no need for that .app in the correct place either)

Thank You!
 

Site & Scene News

Popular threads in this forum