something (somewhat unrelated) that catches my eye there, the pvr = 0x00087200 ...
I've noticed that the code on the fail0verflow blog checks for a pvr that ENDS in 0101 and the 1-512 title checks for a pvr that STARTS with 7001, neither of which happen to match what's shown here.
I would have assumed that all Wii U's should have the same pvr value but just out of curiosity, I was wondering if I could get the results of a few more people running that "cat /proc/cpuinfo" command to check it out (this would include both on a Wii U AND a normal Wii to compare) ?
On the virtual wii or in general?
Doing this now. Give me a few...
EDIT:
Doesn't recognize my keyboard anymore. Using the same one since your very first test.
Gets to the trinux login but will not load my keyboard.
i have nothing else inserted except for a 2gb sd card.
EDIT:
It used to recognize ANY device upon plugging into the USB receptacle, now, nothing.
Tried and failed 4 different times now... Will not load any of my USB devices now while in your application.
Testing now, Ninja and yes, with a little help, I can test anything you want me to test, whether it be in vWii or a pc.
I have been using the same GM321AA corded HP keyboard for every test he has asked to be performed.
I will let you know.
EDIT:
Don't know what to say... None of my keyboards or any USB device for that matter is even recognized anymore with the last two kernels that you have asked me to test.
I went back and tested a previous version and it seems to to recognize all of my stuff. If only you could re-implement whatever is now broken... If something, in fact, is broken...
Tried every character on the keyboard with shift and without shift and cannot get the ">" symbol to come up. Any certain key combination? I notice that the only keys that work correctly in this application are the number and letter keys. For example, I have to press shift + 7 to get the "/" symbol. Clicking on the actual symbol on the keyboard gets me a colon sign or a period, depending on if I am pressing the shift button. Sorry for even asking. I have no idea why it is doing this... Has since day one of testing...
I CAN get it to mount though, if that means anything...
I chose pc / qwerty / US american / Standard / Standard and everything works fine now. Thanks for clearing that up for me!
HERE is the file that you requested.