r164 165 wont build diconfig.bin

[GoogleCodeExporter]

What steps will reproduce the problem?
1.build sneek files with r22 ppc r32 arm 
2.use sneek installer .6c to install w/verbose output
3.load up uneek +di

What is the expected output? What do you see instead?
want to see system menu   black screen

What revision are you using? With what configuration
(SNEEK/UNEEK/SNEEK+DI)?
Uneek+di r164 0r r165 4.2u nand from original dump

Please provide any additional information below.
i have attached some debug logs for you

Original issue reported on code.google.com by Looking.4.nowok.76@gmail.com on 24 Jul 2011 at 5:15

Attachments:

• log164.txt
• log165.txt

[GoogleCodeExporter]

try r166

Original comment by cred...@rypp.net on 24 Jul 2011 at 8:34

• Changed state: Accepted

[GoogleCodeExporter]

Still getting a similar issue with r166.
Hopefully the additions in the dip.c (related to the DML feature) could work 
when creating or updating diconfig.bin, thanks.

Original comment by cona...@yahoo.com on 24 Jul 2011 at 10:54

Attachments:

• r166dml.txt

[GoogleCodeExporter]

How do you get those debug logs?

Original comment by andi.ire...@gmail.com on 25 Jul 2011 at 2:05

[GoogleCodeExporter]

Use verbose output option (-v) when patching the IOS files manually (or check 
the box of verbose output in SNEEK installer application). And with USBGecko 
(on memory slot of the Wii) connected to the computer running GeckoReader (or 
some other terminal application).

Original comment by cona...@yahoo.com on 25 Jul 2011 at 2:15

[GoogleCodeExporter]

Ahh, sorry, I made issue 130, and I think the patch I made there fixes this 
issue.

Original comment by logan.gba on 25 Jul 2011 at 2:49

[GoogleCodeExporter]

have you had any issues using r34 arm ive tried both r32 and r34 and get no 
difference for the output files yet i notice your using a lower revision of arm 
can i ask why

Original comment by andi.ire...@gmail.com on 25 Jul 2011 at 3:11

[GoogleCodeExporter]

have you had any issues using r34 arm ive tried both r32 and r34 and get no 
difference for the output files yet i notice your using a lower revision of arm 
can i ask why

Original comment by andi.ire...@gmail.com on 25 Jul 2011 at 3:11

[GoogleCodeExporter]

@logan: will try your patch attached in issue 130, thanks.

@andi: somehow, when I used devkitARM r34, the resulting elf files' sizes 
became quite large (more than 200 MB). Since I am not all familiar with the gcc 
linker options, perhaps it is better for me to wait until people who are more 
knowledgeable on this could provide more direction.

Original comment by cona...@yahoo.com on 25 Jul 2011 at 3:28

[GoogleCodeExporter]

i had that happen too, but only if it was not a clean all build and only rarely 
not sure what actually caused it clean all seems to result in normal size files 
though :)

Original comment by andi.ire...@gmail.com on 25 Jul 2011 at 3:41

[GoogleCodeExporter]

i can confirm r166 working fine for me i can choose options again and diconfig 
is wrote again Awesome work mr crediar

Original comment by Looking.4.nowok.76@gmail.com on 25 Jul 2011 at 3:47

[GoogleCodeExporter]

fixed in r167

Original comment by cred...@rypp.net on 25 Jul 2011 at 7:31

• Changed state: Fixed
• Added labels: Type-Defect, Priority-Critical, Usability

[GoogleCodeExporter]

Issue 130 has been merged into this issue.

Original comment by cred...@rypp.net on 25 Jul 2011 at 7:32