Envy bugfix release, new web page, updated FAQ

Here is the changelog of Envy’s new release:
* Changed: backported xparse and xorgconfig from Envy's unstable branch so as to
switch to the guidance backend
* Changed: backported improvements to Shutilities from Envy's unstable branch
* Changed: the latest release of the ATI driver is automatically installer for
ATI FireGL cards
* Added: objects.restorexorg()
* Fixed: Bug #179746 xorg.conf couldn't be modified because of a bug in xparse
* Fixed: nvidia-settings is no longer installed for the legacy driver because of
Ubuntu's Bug #156730

As you can see, this new release should solve a few problems and includes some backported parts of Envy’s next major release (0.9.10). Unfortunately the package “nvidia-settings” can no longer be installed because of Ubuntu’s Bug #156730. This problem affects only nvidia-glx-legacy (driver 7xxx) while the other two flavours of the driver are not affected since they already include “nvidia-settings” and therefore don’t need “nvidia-settings” to be installed. If you use the legacy driver, please use Ubuntu’s “Screens and Graphics” application (in the “System/Administration” menu) if you need to set up your screen resolution (or multiple screens).

As some of you might have noticed I have recently changed Envy’s web page since some users complained about its length and about its confusing structure. I’m not a web designer therefore don’t expect to see a masterpiece. If you have further suggestions regarding its usability, please let me know. I have also updated the FAQ for both Ubuntu and Debian.

NOTE: if Opera is your browser you will have to select the “Fixed Table Layout” option in the “View/Style” menu, otherwise the table on my web page will be as large as the entire page. I don’t know why this is happening since I can’t reproduce the problem using Firefox, Epiphany, Konqueror, Internet Explorer 6 (yes, even IE 6!!!)

34 thoughts on “Envy bugfix release, new web page, updated FAQ”

  1. The redesign looks good. One comment though, it would be nice to see the current version and change log history, maybe on another page.

    Also, a question. Is there any news on why the newest ATI Catalyst driver 7.12 causes everything to be choppy (scrolling web pages, compiz animations, horrible fullscreen playback, etc.)?

    Thanks

    Reply

  2. I am so desesperate to see AIGLX instead of FGLRX enabled for all the ATI users!

    Any comment on that sir Alberto?

    Cygoku

    Reply

  3. @Ross Peoples
    I’ll think about it.

    As regards the ATI Catalyst driver 7.12, I have the same problem which I have reported to ATI’s devs. Let’s cross our fingers…

    @Cygoku
    What do you mean?

    AIGLX is part of the Xserver and is also supported by the latest fglrx driver. What’s the problem?

    Reply

  4. Hello to everybody. And thank you Alberto for your work.
    This question is little OT, but for me it’s important.
    Does someone found this driver little slow with AIGLX and Compiz ?
    There is something I can do to improve performance?

    Bye

    Reply

  5. Ciao Alberto,

    Any news on when Envy will be available for Hardy? I’ve spent *days* trying to manually install 169.07 for my 8800GT and just can’t make it work.

    David.

    Reply

  6. I think Cygoku is thinking of XGL, not FGLRX. The newest ATI driver no longer requires XGL for Compiz to work (thank goodness). It uses AIGLX by default now. However, the driver itself is called FGLRX. The names can get confusing.

    Reply

  7. @albertomilone
    The problem with ATI and aiglx is to enable it, right now, by default, it’s always fglrx.

    Cygoku

    Reply
  8. Pingback: Alberto Milone rilascia il nuovo Envy e aggiorna il sito at pollycoke :)

  9. Hi!

    I’ve got a nvidia GeForce 256 NV10, some months ago I try to install nvidia legacy driver both manually both whith Envy, but result is the same: I don’t managed to set right resolution.

    Do you think that with this new Envy’s version I could set it?

    Thanks!

    Reply

  10. @macro182
    Envy doesn’t set the resolution for you.

    You should use Ubuntu’s “Screens and Graphics” application (in the “System/Administration” menu).

    Follow these steps:

    1) Get to the “System/Administration/Screens and Graphics” menu

    2) click on the monitor model and select a generic LCD panel “1024×768” (o or another generic LCD panel with the resolution you need) and press OK.

    3) log out and press CTRL+ALT+Backspace, then log in

    4) Get to the “System/Administration/Screens and Graphics” menu again

    5) Select the resolution you need and press OK.

    6) You might have to log out, press CTRL+ALT+Backspace and log in again

    and that’s all

    Reply

  11. Love the tool, only problem I have it that everytime I use Envy it blows away my /etc/default/linux-restricted-modules-common. I’m using the svn madwifi drivers and have to have ath_hal disabled. However Envy blows this away when adding fglrx to the DISABLED_MODULES line. Not a major problem but really frustrated when I forget about it and my wireless doesn’t work after I upgrade my video drivers.

    Reply

  13. Alberto, congrats on an awesome program which I’ve been using since the heady days of the Nvidia beta drivers.

    Also, the new page is certainly much better! However, if you don’t mind I’d like to suggest another change: using WordPress for the entire site (with its page support) rather than just one section. The main reason is that it makes it so much easier to navigate from one to the other. I routinely build these types of sites (take a look at my site) and this would be a walk in the park for me.

    However, I’m unsure if I would be prepared to do this for free… I’m quite busy with paying projects. Still, something to keep in mind.

    Reply

  14. Hi, envy didnt config my xorg properly this time. So I tried the method you had above and I can get back to my native resolution of 1280×800 (widescreen) but this keeps getting reset on reboot as well as the login screen having the wrong resolution as well.

    In Ubuntu’s “Screens and Graphics” I have:
    1280×800 now.

    In xorg.conf:

    # xorg.conf (xorg X Window System server configuration file)
    #
    # This file was generated by failsafeDexconf, using
    # values from the debconf database and some overrides to use vesa mode.
    #
    # You should use dexconf or another such tool for creating a “real” xorg.conf
    # For example:
    # sudo dpkg-reconfigure -phigh xserver-xorg
    Section “Files”
    EndSection

    Section “Module”
    Load “glx”
    Load “v4l”
    EndSection

    Section “InputDevice”
    Identifier “Generic Keyboard”
    Driver “kbd”
    Option “CoreKeyboard”
    Option “XkbRules” “xorg”
    Option “XkbModel” “pc105”
    Option “XkbLayout” “us”
    EndSection

    Section “InputDevice”
    Identifier “Configured Mouse”
    Driver “mouse”
    Option “CorePointer”
    Option “Device” “/dev/input/mice”
    Option “Protocol” “ImPS/2”
    Option “ZAxisMapping” “4 5”
    Option “Emulate3Buttons” “true”
    EndSection

    Section “InputDevice”
    Identifier “Synaptics Touchpad”
    Driver “synaptics”
    Option “SendCoreEvents” “true”
    Option “Device” “/dev/psaux”
    Option “Protocol” “auto-dev”
    Option “HorizScrollDelta” “0”
    EndSection

    Section “Device”
    Identifier “Failsafe Device”
    Boardname “vesa”
    Busid “PCI:1:0:0”
    Driver “nvidia”
    Screen 0
    EndSection

    Section “Monitor”
    Identifier “Failsafe Monitor”
    Vendorname “Generic LCD Display”
    Modelname “LCD Panel 1280×800”
    Horizsync 31.5-50.0
    Vertrefresh 56.0 – 65.0
    modeline “800×600@56” 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
    modeline “800×600@60” 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
    modeline “1280×768@60” 80.14 1280 1344 1480 1680 768 769 772 795 -hsync +vsync
    modeline “1280×720@60” 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync
    modeline “1280×800@60” 83.46 1280 1344 1480 1680 800 801 804 828 -hsync +vsync
    Gamma 1.0
    EndSection

    Section “Screen”
    Identifier “Default Screen”
    Device “Failsafe Device”
    Monitor “Failsafe Monitor”
    Defaultdepth 24
    Option “AddARGBGLXVisuals” “True”
    SubSection “Display”
    Depth 24
    Virtual 1280 800
    Modes “1280×800@60” “1280×720@60” “1280×768@60” “800×600@60” “800×600@56”
    EndSubSection
    EndSection

    Section “ServerLayout”
    Identifier “Default Layout”
    screen 0 “Default Screen” 0 0
    Inputdevice “Generic Keyboard”
    Inputdevice “Configured Mouse”
    Inputdevice “Synaptics Touchpad”
    EndSection
    Section “device” #
    Identifier “device1”
    Boardname “vesa”
    Busid “PCI:1:0:0”
    Driver “nvidia”
    Screen 1
    EndSection
    Section “screen” #
    Identifier “screen1”
    Device “device1”
    Defaultdepth 24
    Monitor “monitor1”
    Option “AddARGBGLXVisuals” “True”
    SubSection “Display”
    Depth 24
    Modes “640×480@60”
    EndSubSection
    EndSection
    Section “monitor” #
    Identifier “monitor1”
    Vendorname “Plug ‘n’ Play”
    Modelname “Plug ‘n’ Play”
    modeline “640×480@60” 25.2 640 656 752 800 480 490 492 525 -vsync -hsync
    Gamma 1.0
    EndSection
    Section “ServerFlags”
    EndSection
    Section “Extensions”
    Option “Composite” “Enable”
    EndSection

    Reply

  15. @STx
    The Nvidia driver failed therefore Ubuntu’s Bulletproof X was activated and it set the driver to “vesa”.

    type:
    sudo envy --uninstall-all

    then restart the Xserver and use “Screens and Graphics” to set up the resolution you need

    Reply

  17. hmm im tempted to go back to the previous version of envy. Im using the hardy kernel on gutsy btw, using a guide on ubuntu forums – im not sure if this might be causing it.

    Reply

  19. @alberto
    Ok, I did what you suggested but that command uninstalls the currently installed nvidia driver too right? so after I logged back in after restarting xserver from the login screen, i used envy to install the nvidia driver again and I told it yes to config my xorg but its done the same thing again I think:

    # xorg.conf (xorg X Window System server configuration file)
    #
    # This file was generated by failsafeDexconf, using
    # values from the debconf database and some overrides to use vesa mode.
    #
    # You should use dexconf or another such tool for creating a “real” xorg.conf
    # For example:
    # sudo dpkg-reconfigure -phigh xserver-xorg
    Section “Files”
    EndSection

    Section “Module”
    Load “glx”
    Load “v4l”
    EndSection

    Section “InputDevice”
    Identifier “Generic Keyboard”
    Driver “kbd”
    Option “CoreKeyboard”
    Option “XkbRules” “xorg”
    Option “XkbModel” “pc105”
    Option “XkbLayout” “us”
    EndSection

    Section “InputDevice”
    Identifier “Configured Mouse”
    Driver “mouse”
    Option “CorePointer”
    Option “Device” “/dev/input/mice”
    Option “Protocol” “ImPS/2”
    Option “ZAxisMapping” “4 5”
    Option “Emulate3Buttons” “true”
    EndSection

    Section “InputDevice”
    Identifier “Synaptics Touchpad”
    Driver “synaptics”
    Option “SendCoreEvents” “true”
    Option “Device” “/dev/psaux”
    Option “Protocol” “auto-dev”
    Option “HorizScrollDelta” “0”
    EndSection

    Section “Device”
    Identifier “Failsafe Device”
    Boardname “vesa”
    Busid “PCI:1:0:0”
    Driver “nvidia”
    Screen 0
    EndSection

    Section “Monitor”
    Identifier “Failsafe Monitor”
    Vendorname “Generic LCD Display”
    Modelname “LCD Panel 1280×800”
    Horizsync 31.5-50.0
    Vertrefresh 56.0 – 65.0
    modeline “800×600@56” 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
    modeline “800×600@60” 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
    modeline “1280×768@60” 80.14 1280 1344 1480 1680 768 769 772 795 -hsync +vsync
    modeline “1280×720@60” 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync
    modeline “1280×800@60” 83.46 1280 1344 1480 1680 800 801 804 828 -hsync +vsync
    Gamma 1.0
    EndSection

    Section “Screen”
    Identifier “Default Screen”
    Device “Failsafe Device”
    Monitor “Failsafe Monitor”
    Defaultdepth 24
    Option “AddARGBGLXVisuals” “True”
    SubSection “Display”
    Depth 24
    Virtual 1280 800
    Modes “1280×800@60” “1280×720@60” “1280×768@60” “800×600@60” “800×600@56”
    EndSubSection
    EndSection

    Section “ServerLayout”
    Identifier “Default Layout”
    screen 0 “Default Screen” 0 0
    Inputdevice “Generic Keyboard”
    Inputdevice “Configured Mouse”
    Inputdevice “Synaptics Touchpad”
    EndSection
    Section “device” #
    Identifier “device1”
    Boardname “vesa”
    Busid “PCI:1:0:0”
    Driver “nvidia”
    Screen 1
    EndSection
    Section “screen” #
    Identifier “screen1”
    Device “device1”
    Defaultdepth 24
    Monitor “monitor1”
    Option “AddARGBGLXVisuals” “True”
    SubSection “Display”
    Depth 24
    Modes “640×480@60”
    EndSubSection
    EndSection
    Section “monitor” #
    Identifier “monitor1”
    Vendorname “Plug ‘n’ Play”
    Modelname “Plug ‘n’ Play”
    modeline “640×480@60” 25.2 640 656 752 800 480 490 492 525 -vsync -hsync
    Gamma 1.0
    EndSection
    Section “ServerFlags”
    EndSection
    Section “Extensions”
    Option “Composite” “Enable”
    EndSection

    Reply

  21. I like the work you for those of us that can’t learn the ins and outs of linux. a request, please post on the new home page what the current release is. yes, I know that I can download again just to find out what the current envy is, however when just dropping in to see if you have an update, its would be nicer just to see what your current version is.

    and now a real question, why……drum roll….can’t I run the most up to date nvidia driver out…current 169.xx on my Geforce 2 Go ? it(envy as well as the restricted drivers from ubuntu) always installs some older version for my older cards and the newest version for my newer cards. Nvidia has alway been backwards compatible to even the oldest cards out, AND, I have never once had any problems running the very newest and latest drivers on my windows computers. So why is linux different ? I ask only because I know for a fact that with a notebook I have that has a Geforce 2 Go card, the earlier drivers had a bug that made GoogleEarth crash on it under Win2K, however when I installed a newer driver several months back, I think it was a beta 100.xx version, finally GoogleEarth ran without crashing for the first time in 3 years. My point being that the most current Nvidia driver finally solved a problem for me in windows, and I think I can safely assume that it will solve the very same problem now that I run Ubuntu on that very same computer. …any thoughts ?

    Reply

  22. I should have added that I would like to try the 169.xx nvidia drivers on that notebook with a Geforce 2 Go, but don’t know how to get them installed with out restricted manager or envy…and I’m not ready to become a linux expert.

    Reply

  23. Was I missed or was I ignored 🙁

    “Any news on when Envy will be available for Hardy? I’ve spent *days* trying to manually install 169.07 for my 8800GT and just can’t make it work.”

    Reply

  24. @gene
    your card is supported by the new legacy driver (96.43.01)

    @David
    No, sorry it won’t be released now since I’m working with Ubuntu’s devs in order to make Envy work smoothly on Hardy in case of system updates (without the “–uninstall-all” command). This will require changes in Hardy.

    In the meantime you can try this trick:
    http://albertomilone.com/wordpress/?p=107

    it will need you to change 2 things though:
    1) the file you have to modify is:
    /usr/lib/python2.5/site-packages/Envy/classes.py

    instead of:
    /usr/share/envy/instun/classes.py

    2) replace the name “gutsy” with “hardy” in the tutorial

    Reply

  26. Alberto,
    I already knew that my card runs 96.43.01, my question was why can’t I run the 169.xx drivers ? I can install 169.xx video drivers for windows and those drivers fix a GoogleEarth crash problem there, so why can’t I get the 169.xx drivers for Linux ?

    Reply

  28. I’m using opera v9.50 Beta 2 b1754 for linux and your site is perfect. I’ve found no bugs. tkz for new envy 😀
    (sorry, my english is bad :|)

    Reply

  29. I’m new to ubuntu, installed 7.10 using the alternative cd. I get a black screen after splash, so I’m trying to get envy to work. But I’m stuck in the command line. I tried this:
    wget http://albertomilone.com/ubuntu/nvidia/scripts/envy_0.9.9-0ubuntu6_all.deb and got back 404 not found.
    I did get the path to work for envy_0.9.7_0ubuntu2_all.deb after following your instructions on a previous blog post. I then installed, following your instructions, and updated dependencies. But after launch with envy -t command, I get a failure message “envy doesn’t work with your operative system” (not precise language; my apologies.
    My guess is that the newest release of envy will work better. Can you provide the correct wget path?

    Many thanks for all your good work.

    Reply

  31. Alberto,

    I tried the hack you referenced. The auto install did not work (did not detect supported graphics card) so I selected manual install. This appeared to work and requested a reboot. On reboot I was only offered ’emergency’ resolution (640×480) and mouse did not work.

    I rebooted again. This time the display was locked + distorted (not displaying Gnome) with mouse and keyboard locked out.

    Not sure how I recover from this, so I might go back to 7.10 and hope I can get my 8800GT working there. :/

    Reply

  33. Thanks, I tried that (small typo in your instructions – it should be ‘envy –uninstall-all’). It appeared to work but when I rebooted I had the same problem – Gnome desktop was painted but so distorted I could not read any of it. Also, mouse and keyboard seemed to be non-functioning.

    I then tried:
    sudo dpkg-reconfigure xserver-xorg

    This worked and I’m now back with functioning desktop.

    I’m now trying some tips from http://ubuntuforums.org/showthread.php?p=4125275 to get my 8800GT working.

    Reply

  34. That did not work. Also I read that the latest Nvidia driver for 8800GT makes fan run at 100% (which is *very* noisy), so I will sadly give up on Ubuntu and go back to XP for now.

    Hopefully this will all get fixed over the next few months as Hardy is developed. I can then try and move to Ubuntu again.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.