Why did my Linux Mint system crash?

[Michael Butash]

Yours sounds a bit similar to a situation I had.

I had happened to on a m1330 dell laptop with an defective batch of 
nvidia 9000-series gpus that were popping off the bga on the mobo.  
Linux would do that to me, basically hit gdm, login, and when compiz 
kicked in and composited the desktop against the gpu, it would lock or 
just throw crazy colors on the lcd.  I could run it in "classic" at the 
time without compiz, which would work, which didn't call the gpu.  Had 
to rma the mobo under an extended warranty because of the gpu after some 
research.

Why I'd mentioned the gpu.  If integrated, you're screwed, if not, try a 
different card.  I find gpu's die in ugly ways, not always apparent, and 
I've seen linux get wonky with a few on my desktop before I get annoyed 
to attempt to rule it out.

-mb



On 01/14/2014 04:30 PM, joe at actionline.com wrote:
> Brian Cluff last wrote (in part):
>> If boot disks or other hard drives are working, you could try booting
>> into one of those and then mounting your root file system ...
> Each time I have tried starting the system, it would get as far as the
> Mint GUI login screen, but then when I logged in, it all crashed.
>
> So, this last time, instead of logging in, I did CTL+ALT+F2 to switch to
> a non-GUI screen and from there I am able to get to the command line; and
> as far as I can tell all of my home directories and files are still
> intact.  So, I tried to rsync those files to my two laptops, but it seems
> I do not have an Internet connection from this computer. This at risk
> computer is ethernet-wire connected to my router.
>
> How can I establish an Internet connection from the command line?
>
> If I could do that, then I could rsync/copy my most recent work onto my
> two laptops and avoid losing any data.
>
>
>
>
> ------------------
>> ... chrooting to
>> the mount and then reloading everything that is complaining on boot.
>> I usually find I have to do the following mounts to get packages to
>> install correctly in a chroot environment.
>>
>> mount /dev/sda1 /mnt
>> mount --bind /proc /mnt/proc
>> mount --bind /dev /mnt/dev
>> mount --bind /sys /mnt/sys
>>
>> cd /mnt
>> chroot .
>>
>> Of course you will need to mount any extra partitions you might have
>> your drive sliced into. The above assumes everything is on one big
>> partition.
>>
>> If your hard drive is dying, this won't do you any good, or at best,
>> will just buy you a little time before a catastrophic failure takes
>> everything with it.
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss