My issue now is waking up from sleep/suspend/hibernate mode. I have an Asus K53Z Laptop and most forums I see people are also having trouble with this. From what I can tell the laptop is running fine in the background as I can SSH into the laptop even though screen won't power back on.
Is there a script I can write to have the laptop screen reinitialize?
I used to have a dbus config that listened for open/close laptop lit and run suspend unsuspend on a pm program that I forget the name of. But that was a while ago now I think systems just does it. For Ubuntu maybe there is something similar.
Sorry not a solution but maybe the info is useful for direction.
Not saying it would just checking as I am still new to the Linux stuff and diving in head first. Fun and challenging.
Okay so here is an interesting find I have. I tried the link @Raate provided and I can't seem to install any fglrx. Maybe my laptop is just too outside the range for support. Here is my graphics info.
+1 /ram but... It sounds to me like a composting issue or crossed architecture without supporting dependencies (32on64)... and without having you list logs/print-outs it could be a list of different issues. Solutions: save your bash history, wipe&reload the OS & config, examine what youi might have done wrong and learn from the experience. I bet you may have not given sufficient privi's to a post install config. (you installed something under your user profile and it requires su priviledges) Im not at all versed in the Ubuntu universe, so Im not sure how y'all handle autostart direction but look in ~/.config for autostarts and make sure each uncommented line is trailing with a & or &&. Itll prolly be isted as compton or compiz, etc... You could also restore system defaults from /etc/xdg untill you figure out your /user issue. (do this from the terminal) Have you tried booting your system from Live. Grab a debian or /deb/sid live distro and burn it to usb. You can use chroot to correct a lot of your issues as long as you (or they) havent locked down the /root and /etc on your native /system. Make sure you match architecture: 32on32, 64on64, arm on arm, etc. Repost back if you need a chroot cheat sheet / Im sure we can all come up with a list for you.
A couple-o-things though to either consider or completely disregard. 1.Its rarely a hardware issue 2.its rarely a distro issue (that someone hasnt already reported) 3.You are going to bork system configs and installs ...a lot! if you dont enjoy fixing, rewriting, reinstalling, searching for fixes, the only thing you should expect from *nix is a moderate level of frustration for the better part of the next year. 4.How can you be new to *nix and already be on the Debian Haterwagon? 5. As it says in the bible - the only way to heaven is through ARch Linux. So yes, it should be a goal of yours, so throw on some training wheels for the now so you can learn how the machine works first. We all had to do it at some point. (I would insert here that a good vanilla debian distro would be good for you - but I dont want to sway you against another of the amazing intro environments) IMO - Elementary & Ubuntu are not necessarily good for beginners - too many crutches around system commands and terminal operations that you will most certainly need to know venturing up to Arch and even most Debian systems. Cheers mate - youre here atleast, and therefore already ahead of the curve.
So I just tried a live version of Arch and put the laptop into sleep mode and was STILL not able to recover to a normal screen. I am starting to believe it is an issue with the model of laptop no matter what distro I use.
from my experience - speedstep /enabled has always had a hand in something gone/going wrong. If not concerning something immediate, future updates trigger problems. Sucks you have to deal with this right out of the gate.