LordFerret

I'm not an expert on it, but I will say that I can imagine there is a lot more at play than just swapping a memory image to/from disk during hibernation. If you'll think about it: all of the system services, all those open files/devices and the handles assigned, what memory allocated to who, etc ... when you return from hibernation, all of that must somehow be restored/reinstated into a system coming out of a cold boot - after all, your system was saved in a state with having all such allocations and references. Unlike Windows, I'd bet you could find more comprehensive documentation as to what actually goes on with Linux hibernation. - - - Updated - - - This is a bit dated, but you might want to check it out anyway... https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt - - - Updated - - - This is a bit more in-depth; It covers device power managment, suspend, and hibernation. I'm about to read through it myself. Enjoy. http://lxr.free-electrons.com/source/Documentation/power/devices.txt

I have one named "Jeep". lol

The US wasn't alone in 'extreme experimentation' ... a certain nation on 'the other side' did more than its fair share as well. As a matter of fact, many aspects of current medical science are what they are because of it. We didn't get to where we are via fluffy bunnies alone.

Mentioned many times in these forums... AV Linux.

When you hibernate in Linux, the entire contents of memory are swapped out as an image and then the machine and all its services are shut down; On restart, the system boots, sees the image in swap and loads it and executes from there. When you suspend, everything is left in memory and the machine (cpu and memory) goes into a low power state, with the hard drives, display, and other peripherals being powered off; On restore, the power state is brought back up (cpu and memory) and hard drives and display and such are re-enabled. According to the Debian Wiki, there is an alternative for the slow recovery from hibernation; And that is to suspend first, then hibernate. You can read more about it here.

Shhhh... you'll ruin the day of those who think climate change is caused by man. I remember reading about this, but not from that NASA article. My opinion?... I think we're headed toward another Maunder Minimum. I'll take cold over hot.

I kept monitoring this late into the night here, and saw several more after the last one I posted... as of this morning, the count is 42. There is a tsunami watch in effect. TSUNAMI THREAT FORECAST ----------------------- * TSUNAMI WAVES REACHING MORE THAN 3 METERS ABOVE THE TIDE LEVEL ARE POSSIBLE ALONG SOME COASTS OF CHILE. * TSUNAMI WAVES REACHING 1 TO 3 METERS ABOVE THE TIDE LEVEL ARE POSSIBLE ALONG SOME COASTS OF FRENCH POLYNESIA. * TSUNAMI WAVES REACHING 0.3 TO 1 METERS ABOVE THE TIDE LEVEL ARE POSSIBLE FOR SOME COASTS OF MEXICO... ECUADOR... PERU... ANTARCTICA... JAPAN... NEW CALEDONIA... NEW ZEALAND... MARSHALL ISLANDS... FIJI... SAMOA... AMERICAN SAMOA... COOK ISLANDS... TOKELAU... VANUATU... KIRIBATI... JOHNSTON ISLAND... PALMYRA ISLAND... HOWLAND AND BAKER... TONGA... WALLIS AND FUTUNA... PITCAIRN ISLANDS... NIUE... SOLOMON ISLANDS... RUSSIA... HAWAII... AND NW HAWAIIAN ISLANDS. * TSUNAMI WAVES ARE FORECAST TO BE LESS THAN 0.3 METERS ABOVE THE TIDE LEVEL FOR THE COASTS OF EL SALVADOR... GUATEMALA... HONDURAS... COSTA RICA... NICARAGUA... PANAMA... COLOMBIA... AUSTRALIA... PHILIPPINES... TAIWAN... CHINA... NORTHERN MARIANAS... GUAM... PALAU... YAP... POHNPEI... CHUUK... KOSRAE... NAURU... WAKE ISLAND... MIDWAY ISLAND... JARVIS ISLAND... TUVALU... PAPUA NEW GUINEA... INDONESIA... VIETNAM... MALAYSIA... AND BRUNEI. * ACTUAL AMPLITUDES AT THE COAST MAY VARY FROM FORECAST AMPLITUDES DUE TO UNCERTAINTIES IN THE FORECAST AND LOCAL FEATURES. IN PARTICULAR MAXIMUM TSUNAMI AMPLITUDES ON ATOLLS WILL LIKELY BE MUCH SMALLER THAN THE FORECAST INDICATES. * FOR OTHER AREAS COVERED BY THIS PRODUCT A FORECAST HAS NOT YET BEEN COMPUTED. THE FORECAST WILL BE EXPANDED AS NECESSARY IN SUBSEQUENT PRODUCTS.

Add another to the list, lesser, to the north... 5.3 57km SW of Ovalle, Chile 2015-09-17 00:06:16 UTC 10.0 km

Round about mid-1990's, long before Win8... pre-XP. https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface

That's what I was saying, like a TOW missile.

There was a blurb of concern about tsunamis for the coast of Chile and for Hawaii; I wonder if there's any concern for those that live on Robinson Crusoe Island?

More like getting hammered with earthquakes ... and so far, not really any mention what-so-ever on the news. 5.7 76km WSW of Illapel, Chile 2015-09-16 23:38:05 UTC 35.0 km 6.4 25km W of Illapel, Chile 2015-09-16 23:18:42 UTC 31.1 km 6.2 70km W of Illapel, Chile 2015-09-16 23:16:05 UTC 10.0 km 6.1 44km WSW of Illapel, Chile 2015-09-16 23:03:56 UTC 10.0 km 6.3 71km W of Illapel, Chile 2015-09-16 22:59:17 UTC 47.8 km 8.3 54km W of Illapel, Chile 2015-09-16 22:54:32 UTC 25.0 km

Well, a smart autonomous sub could melt its way down, enter the ocean, swim around and collect data, and then melt its way back up and deliver that data. Yes? No?

Do you mean to imply it would close up immediately, or rather very quickly? I would imagine 'very quickly' being the case if the melt from the probe-sub wasn't evacuated somehow, that as it bore down there would be re-freezing taking place behind it. That being the case, maybe leaving a trailing wire during descent would be the more viable option?... the quick re-freezing encasing the wire, safely locking it in? The only issue then would be any shifting of the crust, I'd suppose.

Another thing to consider with this hole-boring submarine idea, is that once you drill though the crust you may very well encounter pressures the second your break though which would turn that hole into a geyser, turning that 'submarine' into a bullet shot from a cannon. Maybe the thing to do would be to sit poised next to an existing geyser, and the moment it subsides drop the probe-sub in.

I see a number of potential problems, but where to start? It's not like I have the thing here in front of me - that would be a different story. I've seen system funkiness from a bad CD/DVD drive, where just removing the drive solved all the problems. Then there's also the problem with the USB3 ports, which, actually, that D5 error code relates to ... one of the things I read about that last night had to do with where (which USB ports) the mouse and keyboard were plugged into. As WedgeAntilles points out, it very well could be a drive issue; Although for testing such things, I have a universal adapter where swapping the drive out isn't required (just unplug the drive cables and power and plug in the appropriate adapter connects, then plug it into a USB port on another machine).

I've commented on this previously, in another thread somewhere here having to do with Europa; To use a probe as such with a wire, like a TOW missile, the wire going all the way back to the surface to a base station and data transmitted from there. Pretty much, just as pictured in the diagram. - - - Updated - - - Thinking about it, looking at the image of the tube/tunnel created by that test probe... I wonder if they've ever looked into using the ice tunnel created by the probe as a microwave waveguide? Maybe data communication could be accomplished using microwave, beaming data back up through the tunnel. The walls of the tunnel appear smooth enough, and ice has very low bulk resistivity.

It's worth the effort. I'd put a new one in... if you've gone that far to take it out, might as well slap a new one in!

Not to derail, just a small side-step: Gads I hate layers... backdoors. http://www.computerworld.com/article/2476651/malware-vulnerabilities/your-pc-or-laptop-may-have-a-backdoor-enabled-by-default-millions-do.html https://mjg59.dreamwidth.org/35110.html https://www.reddit.com/r/linux/comments/37c38l/uefi_backdoor_allows_root_exploit_in_linux/ I'll imagine Macs are susceptible as well.

Ok, well, looking at the manual for your motherboard; The LED codes you listed, "0S" is undefined "D5" is defined as "No Space for Legacy Option ROM initialization" "DS" is undefined "05" is undefined So, "No Space for Legacy Option ROM initialization" it is. A few Google searches on the subject suggest your BIOS is corrupted. That would make a lot of sense considering your description of failed boots. Go check that motherboard battery. It's located pretty much dead-center of the motherboard, right behind the PCIEX1 slot ... as defined in the manual for your motherboard, page 7. Note that removing this battery will effectively clear the CMOS values; If you can, get into your BIOS setup screen before doing this, make some notes and record all of the settings. How long since you last changed that battery (if ever) ?

Humm... maybe take a look here, the OEM's page. http://www.gigabyte.com/products/product-page.aspx?pid=4481#driver

65,535... we start the initial offset at 0. (unsigned)

Bah... error... the Driver Update utility is run from the Start Menu (once installed). - - - Updated - - - Wha?!? I'm looking at the Driver Update Utility page right now, and it says ... Operating System Install Requirements: Microsoft Vista*, Microsoft Windows 7*, Microsoft Windows 8*, Microsoft Windows 8.1*, Windows® 10

The Driver Updater is a program located in the Control Panel (should be, if you have it installed). The link(s) for the Driver Updater software and chipset drivers for the hardware you specified are in the previous post I made (shown below). So the next question would be, what are the minimum requirements - and does your system meet them. Doesn't sound like it.