Envy 0.9.2-0ubuntu3 UNSTABLE – another update for Nvidia and ATI users

I have worked hard yesterday night to squash a few bugs which caused problems both to the owners of Nvidia cards such as 8800 and the owners of ATI legacy cards.

Here is the changelog:

envy (0.9.2-0ubuntu3) unstable; urgency=low
.
* Fixed: Envy deb compilation scripts did not create a link to libnvidia-wfb.so.1.0.9755 thus
causing problems to more recent cards
* Fixed: libnvidia-wfb.so.1.0.9755 was not included in the packages because of a typo
* Added: support for Nvidia 7300 GT
* Changed: the ATI legacy driver is packaged as if it were the latest version so that it will
not be automatically upgraded to ubuntu default version.
* Changed: the source code of Envy is now much smaller

Please, let me know if this release solves your problem.

You can download it from this page as usual

25 thoughts on “Envy 0.9.2-0ubuntu3 UNSTABLE – another update for Nvidia and ATI users

  1. Thanks for update Alberto! I will try last version now.
    But in the scripts page, the version number is wrong.
    it is UNSTABLE VERSION (0.9.2-0ubuntu2, released on April 23 2007)
    0.9.2-0ubuntu2

  2. Hi, thanks for the update!

    I tried the new version, but I still get the error “Build of the package fglrx-kernel-src failed” in the module assistant interactive mode, after the script extracts de package tarball “fglrx-kernel-source”.
    I’m trying to install a ati radeon 9000 using the manual instalation->old drivers.

    many thanks!

  3. Hi Alberto,

    Ignore my last post, I think I screwed up installing the new envy, and I was trying the old version instead, sorry.

    I tried the new version and I don’t get that error anymore. However, when the script finishes installing, it tells me that some error ocurred during the installation.

    I uploaded the log here:
    http://www.salle.url.edu/~tm09601/envy-installer.log

    many thanks!

  4. Alberto,

    I am sorry for your loss. We must always keep in mind that our friends are now in a better place and are never truly gone as long as we remember them.

    On to earthly matters; my two nvidia cards are having trouble. The 4400 tops out at 800×600 and the 5900 at 640×480 after running ENVY. The 4400 originally shows 1024×768 at install and then drops to 800×600. The 5900 is always at 640×480. Very odd to me.

    Phil

  5. Phil:
    1) do you use 2 cards in the same computer?
    2) If so, which version of the driver did you install?

  6. Alberto,

    I have been switching between the two cards in an attempt to reach the natural resolution of the monitor (1280×1024). After installing Feisty Fawn the 4400 will have a max resolution of 1024×768 and the 5900 of 800×600. After running Envy the resolutions go to 800×600 and 640×480 respectively. Feisty Fawn is reinstalled between each of the card swaps. The driver is whichever one Envy chooses.

    Phil

  7. Phil:
    use the 5900, install the latest driver and then restart the Xserver.

    To set the correct resolution, type:
    sudo nvidia-settings

    and set the resolution from there (save your settings)

  8. Alberto,

    This gets more interesting all the time. The 4400 was in the machine and the resolution was 1024×768. Neither the restricted driver manager nor envy had been run. Turned off the machine and swapped cards. On reboot the resolution was still 1024×768. That is the first time I have seen that resolution with the 5900. BTW, I also tried a 6800GT a few days ago, it behaved as badly as the 5900.

    Anyway, installed and ran envy. Nvidia Settings is suddenly now part of the Applications/System Tools Menu. The highest resolution is 1280×800, still short of the natural resolution of 1280×1024, but a great improvement over the previous results. Didn’t need to use Sudo nvidia-settings since it appeared as part of the menu.

    I am open to any other instructions or suggestions. I would still like to reach the 1280×1024 resolution.

    BTW, if I ever get back to the home country or you get to the states, we need to get together with all the folks you have helped and open a bottle of vino (or a few hundred, depending on how many show up) to celebrate.

    Phil

  9. Phil, what you’re describing sounds like what I get with Feisty, with a slight variation, since I have one card.

    After installing Feisty, if I take a look in my xorg.conf file, it has the same 3 default resolutions (“1024×768” “800×600” “640×480”) for all bit depths — but my native is 1680×1050. (It sounds like your 2 cards round-robin between those same values…?)

    My xorg.conf is still off, even after I’ve run Envy and the nVidia driver settings shows up in my Applications > System Tools. But when I load the nVidia tool, it says that it’s using the proper 1680×1050 resolution anyways. Perhaps the proper native resolution was probed, not from xorg.conf…?

    That’s not the only weird thing about the xorg.conf I got with Feisty, though. The X log file had a few warnings related to the font path and Wacom stuff, too. X seems to start up faster when I manually fix the xorg.conf file to address those warnings and fix the resolutions.

    I don’t know if that file is part of Envy’s scope or not. But maybe give the X config file a look. It worked for me.

  10. Oops. Forgot to mention… the Wacom error (‘wfb’ stuff) appears when I restart X. I guess quite a few people are getting that with Feisty.

    Is that’s what is fixed by the libnvidia-wfb.so.1.0.9755 change to Envy? If so, I’ll try it again from scratch…

  11. Phil:
    Create a modeline by typing:
    gtf x y refresh

    x stands for the horizontal resolution (e.g. 1024), y stands for the vertical resolution (es. 768) and refresh is (obviously) the refresh rate (e.g. 60)

    if (for example) you want to use 1024×768 at 60Hz you will have to type:
    gtf 1024 768 60

    the output will be similar to the following (i.e. a modeline):
    # 1024×768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 64.11 MHz
    Modeline “1024x768_60.00” 64.11 1024 1080 1184 1344 768 769 772 795 -HSync +Vsync

    Insert the modeline in the Screen Section of your /etc/X11/xorg.conf , save it and restart the Xserver.

    NOTE: launching nvidia-settings from the menu won’t let you save your settings for the resolution, refresh and tv-out (this is why you should launch it with sudo)

    kannon:
    Wacom error is not a real error and doesn’t affect the functioning of the Xserver. Ubuntu sets the xorg.conf so that if you plug in a Wacom tablet it will work out-of-box. If the tablet is not there you will only get that warning.

    “wfb” is a module of the Nvidia driver which is needed by geforce series 88xx.

  12. Ah, thanks! I understood that the Wacom entries were for out-of-the-box, but I thought that entry would have been removed since I didn’t haven’t connected mine yet.

    Sorry for confusing that with the (WW) and (EE) wfb errors, I really should read more slowly…

    Thanks again.

  13. Alberto,

    Created the modeline entry and modified the xorg.conf file. It bombed with an error that “modeline is not a valid entry in this section” or words to that effect.

    Phil

  14. Alberto,

    Made the changes with no effect. Nvidia settings don’t show 1280×1024. It does show other resolutions that are not shown in xorg.conf. (1280×800 and a few others)

    I reinstalled Feisty, max resolution of 800×600 from the preferences menu. Opened xorg.conf, the video card is correctly ID’ed, the monitor is correct and all the resolutions (in the screen section) are listed.

    I’m lost.

    Phil

  15. Hmm, I’m now having the same problem. I did the modeline thing and it worked… until I restarted xserver the second time, then it reverted back to saying it was 1680×1050, even though it wasn’t. So, I reverted back to my backup xorg.conf and repasted the modeline code into it, and it worked again until the second restart. My xorg.conf isn’t changing. Any ideas?

  16. Hey, no need I guess. After doing the modeline like you had suggested, I went to check in my nvidia-settings gui, and one of the monitors was set at a lower resolution for some reason, even though both got the same modeline. So, I changed them to match, and voila! Problem solved. Thanks for your help.

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.