panic(cpu 1 caller 0xfffffff008b68f78): SEP/OS failed to boot at stage 1 #242
Replies: 1 comment 18 replies
-
|
Well, the first step would be to post the used command to run the emulator, and also a hash of the used sepfw. not the file itself, just a hash. no keys, just the hash. |
Beta Was this translation helpful? Give feedback.
-
|
No need, just knowing where the issue is, logs, etc. is enough for us to take a look and fix it. Thanks for letting me know that the TCP USB code is working improperly on Windows. I already had suspicions that the code is a source of errors, considering its lack of quality, and its use of a thread instead of QEMU's AIO concepts. |
Beta Was this translation helpful? Give feedback.
-
|
The QEMU codebase is a piece of shit as well, but unfortunately would've taken a long time to reinvent the wheel and roll my own code. I do plan on making a fresh, fast, maintainable and stable QEMU alternative, if this project succeeds, though, as an "Inferno 2" so to speak. |
Beta Was this translation helpful? Give feedback.
-
|
After testing on different conditions, I found that if you start the emulated device before the Companion VM, the lag will not appear, but if you start the Companion VM before the emulated device, you will see the lag. I made a patch to workaround the issue (see kasumikira@a361ca8), but to be honest, I do not know why it works. |
Beta Was this translation helpful? Give feedback.
-
|
I guess that it doesn't like the additional load needed for the USB workaround. As in, afaik the iOS instance won't connect to the companion VM (properly) if it's started later. So in one case you have a functional USB connection, and in the other case you most likely have none. |
Beta Was this translation helpful? Give feedback.
-
|
Understood. Just to clarify, my patch only modifies the win32 keyboard hook logic to prevent the input lag on Windows, without touching any other core logic, and it's not a clean fix. Since it seems to be a specific windows backend issue, I'll just keep the fix in my fork for now. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I really don't know if I'm making a mistake. After checking all the commands carefully, I still don't know why the emulator is crashing every time I try to run the idevicerestore.
Here is the log:
Beta Was this translation helpful? Give feedback.
All reactions