Skip to main content

Gnome 3 shell screen "lock" (workaround)

Solution:  I tried to use the Discrete video adapter (non-Optimus) and load the akmod-nvidia driver.  This, however, does not fix the problem :-(  Install the Compiz goodness and run that as your Display Manager.  I actually don't mind Gnome3 now.... bordering on almost liking it.  I certainly hope they get their stuff together soon.

# Install Compiz

yum -y install compiz.x86_64 compiz-bcop.noarch compiz-devel.x86_64 compiz-gconf.x86_64 compiz-gnome.x86_64 compiz-gtk.x86_64 compiz-manager.noarch compiz-plugins-main.x86_64 compiz-plugins-main-devel.x86_64 compiz-plugins-main-gconf.x86_64 compizconfig-backend-gconf.x86_64 compizconfig-python.x86_64 libcompizconfig.x86_64 libcompizconfig-devel.x86_64



UPDATE:  The problems continues using the Nvidia driver and discrete display adapter.  Unfortunately I can not handle this type of issue on my primary workstation and therefore I am migrating to RHEL 6.2 workstation.

Issue:  My system would somewhat frequently have a "hung display".  So - what do I mean by that?  The display would freeze at a certain point.  However, I could still move the mouse around.  Yet, I could not click on anything.  The corner activation would fail also.  The only resolution at that point would be to hit the definitive CTRL-ALT-Backspace.. and reboot.  Interestingly enough, this would only occur when I was using VMware Workstation 8.0.1

For giggles, I installed the akmod-nvidia package (and dependencies) and I then went into the BIOS and configured the machine to only use the Discrete (Nvidia) display adapter.  My machine is basically always plugged in, so this does not concern me much.  I am very much looking forward to a Linux-capable Optimus setup to be released.  Reverting back will not be simple.  It would be nice to have an option of going back and forth.  The Intel display adapter was fine for my needs, aside from it apparently locking up my display.

NOTE:  The dual-display configuration with Nvidia pretty much sucks in Gnome 3.  It resorts back to the failsafe config on my machine.  This might be my first "bugfix" submission.  Wish us luck!

Lenovo T520, Fedora 16 x86_64, Gnome 3, dual-display, nvidia, optimus
Labels:

Comments

  1. UnknownSeptember 17, 2013 at 1:02 PM

    Yeah, I have an integrated intel GPU as well, and it freezes with VMWare player. Seems to happen when the lockscreen tries to turn on on the host machine if I have VMWare active. Not fun, but same exact symptoms.

    ReplyDelete

Post a Comment

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...
2 comments
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more