Having solved my problems with the suspend/resume on Intrepid whilst keeping Compiz and spinny things going, I had one final thing to crack.
When I used the ATI Catalyst Control Centre ( amdcccle ) to set my display resolution, I noticed that the changes were not being saved through a reboot. As an example, I could set the resolution to 1600x1200 to get the best out of my Thinkpad's HUUUUUGE screen, when I rebooted, the resolution would be back at 1024x768, which is a bit annoying.
As usual, Google had the answer, Google is my friend. I searched for "amdcccle saving" and found this article - the answer is to run gnome-display-properties and click Apply to save the current configuration ( this applet can be as a command ( ALT + F2 ) or via System -> Preferences -> Screen Resolution.
Strange but true
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV https://infosec.exchange/@davehay
Subscribe to:
Post Comments (Atom)
Note to self - use kubectl to query images in a pod or deployment
In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...
-
Why oh why do I forget this ? Running this command : - ldapsearch -h ad2012.uk.ibm.com -p 389 -D CN=bpmbind,CN=Users,DC=uk,DC=ibm,DC=com -w...
-
Error "ldap_sasl_interactive_bind_s: Unknown authentication method (-6)" on a LDAPSearch command ...Whilst building my mega Connections / Domino / Portal / Quickr / Sametime / WCM environment recently, I was using the LDAPSearch command tha...
-
Whilst building a new "vanilla" Kubernetes 1.25.4 cluster, I'd started the kubelet service via: - systemctl start kubelet.se...
2 comments:
I find my T60p is constantly losing its memory of which screens to start X on. When docked, I want it on my two external monitors, but after some mishaps or use it always ends up on one external monitor plus the laptop screen. I wonder if gnome-display-preferences offers an easy workaround? Gonna try.
Thx for this tip this did it also for me
Post a Comment