Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.Before you post please read how to get help

I new to the Linux world, just switched from Vista, and i can proudly say that, "i will never go back to windows again".

But on to the problem im having. When i close the lid on my laptop it suspends just fine but, whenever i come back to it and open the lid for it to load, it freezes, with lines on the screen and i have to hold the power button and restart it.

as soon as i type in these commands just like how u see it, with the arrows and everything, save it, then reboot, it messes up everything. heres what it looks like.Section "Device" Identifier "Configured Video Device" Driver "nvidia" Option "NvAGP" "1" <= Option "nologo" "1" <= Option "NoLogo" "True"EndSection

where the 2 arrows are is what i inserted cause thats what it says. am i suppose to remove the arrows?also it says if i have that problem with the graphics getting bigger, to add it to the blacklist file, but when i try to do that, it says permission denied.

my other file as of right now, looks exactly like this. i copied straight from the file.

# Should we save and restore state using the VESA BIOS Extensions?#SAVE_VBE_STATE=trueSAVE_VBE_STATE=false <=

# The file that we use to save the vbestateVBESTATE=/var/lib/acpi-support/vbestate

# Should we attempt to warm-boot the video hardware on resume?#POST_VIDEO=truePOST_VIDEO=false <=

also, i really dont care about the hibernating part. all i really want is for my laptop to go into standby/suspend when i close the lid.

You should not have included the arrows -- they are simply pointers. So what you should do now are:1. Remove all arrows from each file that you edited.2. Remove the line that reads Option "NoLogo" "True" from your xorg.conf file.3. Reboot your computer afterwards then check to see if your computer can suspend and resume correctly.

If then you think you still have to blacklist AGPGART, do these steps:1. Open the blacklist file for editing, with this command:

ok iv done everything like you said so far. my graphics no long mess up but its still not working. its freezes on a black screen now. i added it to the blacklist. it looked like this when i added in the command you said to put:

# replaced by asus-laptop (Ubuntu: #184721)blacklist asus_acpi

# low-quality, just noise when being used for sound playback, causes# hangs at desktop session start (Ubuntu: #246969)blacklist snd_pcsp

# blacklist ipv6blacklist ipv6blacklist agpgart

that correct? its still freezing on a black screen when resuming from suspend.

Yes, that is correct. Unfortunately I have no idea what to do next for I do not have an AMD laptop, as stated in my previous post. So the best thing I can recommend now is to undo all the changes since they do not seem to do any good for you.

whats funny is that it use to work when i first installed mint, switching from ubuntu. it never had a problem with ubuntu. i was actually gonna see how fedora was, but idk. i already started putting a bunch of stuff on mint... i need some fast, and mint seems a bit slow. idk.

i wonder what happened along the way of having mint, that now it will not resume from suspend?

ok i think i may have found the problem. it seems that my swap partition may not be setup right. when i try to hibernate, this is what it says:matt@DV2610us ~ $ s2disks2disk: Could not lock myself. Reason: Cannot allocate memorymatt@DV2610us ~ $ sudo s2disk[sudo] password for matt: s2disk: Could not stat the snapshot device file. Reason: No such file or directory

I have managed to convince a generous friend to lend me his Turion laptop so that I can play around with ACPI tidbits more accurately. All I can tell for now is that the kernel ring message [ 0.612202] ACPI: EC: GPE = 0x2a, I/O: command/status = 0x66, data = 0x62 has nothing, or at least very little, to do with uswsusp.

And I am going out of town this morning, so this might take longer than I initially estimated.

I have managed to convince a generous friend to lend me his Turion laptop so that I can play around with ACPI tidbits more accurately. All I can tell for now is that the kernel ring message [ 0.612202] ACPI: EC: GPE = 0x2a, I/O: command/status = 0x66, data = 0x62 has nothing, or at least very little, to do with uswsusp.

And I am going out of town this morning, so this might take longer than I initially estimated.

Ok heres all the info you requested. From top to bottome just like you have listed.