| Blockland Forums > Help |
| Blockland caused a kernel panic on my Mac |
| << < (11/13) > >> |
| segfault314:
I like how this thread instantly devolved into four pages of idiots on both sides talking about macs instead of trying to figure out why this guy's machine kernel panicked while running Blockland. Anyone claiming that his machine can't run Blockland is wrong, Blockland will run on just about anything. An Intel GMA 950 is pretty weak for a GPU but it shouldn't cause kernel panicking, just like running Blockland on Windows with a crappy GPU wouldn't necessarily mean a bluescreen. A dual-core Intel with 2GB of DDR2 667 RAM is more than enough for Blockland. Do you remember exactly what you were doing before you kernel panicked? If not, can you try to recreate the issue for us? |
| SWAT One:
--- Quote from: segfault314 on June 25, 2012, 10:53:08 PM ----snip- --- End quote --- Good input, but uh. Who are you? You just popped up today with a 1k ID and several posts... |
| Sheath:
--- Quote from: segfault314 on June 25, 2012, 10:53:08 PM ---An Intel GMA 950 is pretty weak for a GPU but it shouldn't cause kernel panicking, just like running Blockland on Windows with a crappy GPU wouldn't necessarily mean a bluescreen. A dual-core Intel with 2GB of DDR2 667 RAM is more than enough for Blockland. --- End quote --- Yeah I agree, Blockland runs on an Intel Atom D525 and Intel GMA 950 graphics okay on my mini-itx. High brick count makes it slow, but it doesn't cause those kind of problems. Though I personally can't recommend people playing on those machines. |
| Steemer:
It wouldn't be blockland, it would be some background process you can't see that encountered an error. Or a hardware malfunction. It might not have been bad enough to stop all processes, and tell you to shut down, but it would have anyway, just to be safe. http://en.wikipedia.org/wiki/Kernel_panic --- Quote from: ScratchTehEPICSpaceDude on June 25, 2012, 08:28:13 PM ---I do? What are they and how do I disable them? --- End quote --- Probably not the best idea to disable background process that you don't know the function of. |
| segfault314:
--- Quote from: Steemer on June 26, 2012, 02:11:27 AM ---It wouldn't be blockland, it would be some background process you can't see that encountered an error. Or a hardware malfunction. It might not have been bad enough to stop all processes, and tell you to shut down, but it would have anyway, just to be safe. --- End quote --- If it was a background process or hardware failure he'd see a lot more kernel panics. |
| Navigation |
| Message Index |
| Next page |
| Previous page |