I'm trying to bring back a 2018 Mac Mini (Intel) to life, after a long period of not being used it's no longer booting: LED active, black screen, no connection to USB keyboard. Apple tried swapping the PSU, now wants to replace the logic board.
I read about reported issues with the T2 chip for this model and how to fix it here.
Using Apple Configurator I can run Restore to the point where I actually see the Apple Logo and a progress bar on the monitor connected to the Mini.
Surely this means it's salvageable!?
However, once finished it still can't boot. LED active, no video signal, no connection to keyboard over USB. (I've tried holding down different keys to go into recovery OS, resetting PRAM etc, but the keyboard doesn't seem to be connected anyway)
Restoring using libimobiledevice - idevicerestore gives the same results: Suddenly I get picture while it installs, restore successful - Still can't boot. I have the vain hope that someone knowledgeable can read through the "logs" in the link below and analyze the situation:
Logs from running idevicerestore -l -e- d
Related
I was following the nvprosamples creating the direct display to prevent the OS to affect the usage of it as described in this nvidia sample:
[ddisplay sample][1] [1]: https://github.com/nvpro-samples/gl_render_vk_ddisplay
This was approx one year ago, using Vulkan 1.1, everything was working fine.
After upgrade to 1.3 creation of the swapchain was not possible as it seemed that display was not made available for vulkan api anymore, _device->createSwapchainKHRUnique resulting to eErrorInitializationFailed.
This init error was possible to fix by adding the vkAcquireWinrtDisplayNV call which seems that in new version is somehow making the display available for swapchain (surface), same stuff was added to the new version of the nvidia sample.
The problem is that it seems that after the application finishes the monitor is still hanging in some vacuum, invisible for the OS anymore, the process of the application becomes hanging in the taskmanager, without posibility to kill it anyhow (niether admin forced task kill will work as it will state that no instance of the process is running). Even the computer is not possible to be restarted (as the restart screen hangs indefinitely). The Nvidia's sample is causing the same behaviour as mine app.
Is there any way to return the display back to the OS when application ends withou powering off and on the workstation?
I tried to use vkReleaseDisplayEXT on destruction, but without any success (it is also not used anywhere in the sample code if I am not blind).
I trained the whole network and got the parameters. When I use one pth to infer the result on a test dataset, just testing, by debugging, each time when it goes to "torch.save(predictions, predictions_path, pickle_module=dill) ", the whole system gets dead. The clock stops and the mouse cannot move. Push contl+alt+F1 to tty but no response. Nothing can do. Everything is dead. If I restart the machine by the "start" button, the system then says "lost inducing document" and the whole system dumped and I have to re-install the whole Linux. If I wait for the dead system to be back, it costs one day or so, and finally, it gets back to response and just shows "system error".
I searched for all possible solutions and tried but not work. I bought new memory banks, updated and upgraded all software, checked error logs, and optimized many system services. But all is useless. Each time it got dead for one day. The system is centos for ubuntu. Anyone can help?
I'm working on a labview program that will talk to box via VISA commands. When I use the instrument assistant in the labview Instrument I/O palette as an open window, it will send and receive information perfectly. When I close the window and try to run it within the context of the larger program (containing only that) it says that the VISA resource is busy.
I have also tried using the Open/write/close option from the Instrument I/O palette, and that also will not allow me to access the resource. I've tried all three directly after restarting the instrument in question, so I'm pretty sure it's not actually busy.
Does anyone have experience with a similar problem, and if so how did you fix it?
This is a really odd one: Could I ask any experienced Windows developers to please look at these screencaps, and advise if they've ever seen anything like this before: corrupted background whitespace, in Windows 2012: see these mages - these are seen within Win2012 VMs running on HyperV on Win2012 host:
screencap 1 - showing whitepace corruption
screencap 2 - another view of whitespace corruption
I should say - the machine works perfectly still: this is purely a visual effect, and appears to be a corruption of some sort of background (font??) - every new application pane opened, shows it - Windows Explorer does - but as soon as appn writes to the whitespace, it clears the corruption away.
This is an RDP view to the server but that seems unrelated: the actual RDP desktop background is not affected, just the whitespace in each Windows application pane. That's why I wonder if it's something to do with a font corruption or related.
Hoping to resolve it without a complete rebuild: is part of an industrial server application on a client site.
All wisdom will be gratefully received.
Thanks very much
Mike, London
I'm trying to upload new images to iTunes Connect. However, they continue to fail. I've checked many many times now and no dice. The screenshot sizes match Apple's requirements. Saving it as a .jpg continues to fail. Saving it as a .png with no Alpha continues to fail. Spent most of my work day on here finding other solutions that I've tried and still fails.
Other things I tried was using different browsers, saving the image file as generic as possible (ex. 1.png, and I've tried using screenshots pulled from an actual device as well as the Xcode simulator.
I am trying to do this via a windows machine. Has anybody been able to successfully upload screenshots through iTunes Connect using a Windows machine? At this point that is the only thing I can think of as to why it continues to fail.
Try waiting... in my experience, iTunes connect is not all that reliable, and waiting a day solved the screenshot upload issue for me.
Also, if you have not already, open the screenshots in an image editor, and insure they are exactly the right size... I have found that my screenshots always end up a pixel to skinny for some reason.
Lastly, keep in mind new rules for the iPhone 6 and 6 Plus.