Nvidia 195.36.15

I know, that there where problems with a previous 195-starting version (I think 195.36.08), but after that, nvidia removed that from their website, and for a while, again the 190.53 was the stable version (as here), but now, another nvidia driver released, which is told to be the okay driver (195.36.15), and it seems, that for kde users, this is a solution for a slowness in 190.53:
https://bugs.kde.org/show_bug.cgi?id=226182 (comment #8)
What is the current state of nvidia drivers, as the newest is not even in testing.
And yes, this was the older buggy one (195.36.08) nvidia removed it from their site, since that there are a whole new okay driver: http://bbs.archlinux.org/viewtopic.php?id=92203

cleanrock wrote:195.36.15 should have entered testing when it was available, lazy maintainer i guess
They are not obliged to update it so fast, you should know
They will update it as soon as they can.
Last edited by flamelab (2010-03-31 08:57:56)

Similar Messages

Nvidia 195.36.31-1 doesn't detect horizontal refresh rate correctly

With both the nvidia driver 195.36.15 that was in the main repositories before the last update, and the nvidia-beta driver 256.35-1from aur my monitor's horizontal refresh rate is detected correctly(129.5khz with a 120hz vertical refresh rate). However, the nvidia driver currently in the repositories 195.36.31-1 doesn't detect it correctly and forces a horizontal refresh rate of about 185khz. This causes horizontal white lines to be seen all along the screen.
I'm now happily using the beta driver from aur, but I can try to pinpoint the problem if someone can point me in the right direction.
thanks.

this is not a bug. this is a nvidia workaround so that xrandr is able to handle correctly multihead refresh rates. see the nvidia readme for details, and don't worry, the refresh rate is correct, else you would see garbage.
Last edited by lloeki (2007-04-28 20:50:16)

Unable to load the kernel module 'nvidia.ko' [SOLVED]

After my most recent kernel upgrade, I can't get my GUI to run. I've tried reinstalling the nvidia driver to no avail.
Any insight would be greatly appreciated. I'm using a GeForce 8400 GS
cat /var/log/nvidia-installer.log
ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most
frequently when this kernel module was built against the wrong or
improperly configured kernel sources, with a version of gcc that differs
from the one used to build the target kernel, or if a driver such as
rivafb/nvidiafb is present and prevents the NVIDIA kernel module from
obtaining ownership of the NVIDIA graphics device(s), or NVIDIA GPU
installed in this system is not supported by this NVIDIA Linux graphics
driver release.
Please see the log entries 'Kernel module load error' and 'Kernel
messages' at the end of the file '/var/log/nvidia-installer.log' for
more information.
-> Kernel module load error: insmod: error inserting './usr/src/nv/nvidia.ko':
-1 No such device
-> Kernel messages:
NVRM: This can occur when a driver such as nouveau, rivafb,
NVRM: nvidiafb, or rivatv was loaded and obtained ownership of
NVRM: the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA graphics adapter probed!
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as nouveau, rivafb,
NVRM: nvidiafb, or rivatv was loaded and obtained ownership of
NVRM: the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA graphics adapter probed!
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as rivafb, nvidiafb or
NVRM: rivatv was loaded and obtained ownership of the NVIDIA
NVRM: device(s).
NVRM: Try unloading the rivafb, nvidiafb or rivatv kernel module
NVRM: (and/or reconfigure your kernel without rivafb/nvidiafb
NVRM: support), then try loading the NVIDIA kernel module again.
NVRM: No NVIDIA graphics adapter probed!
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at www.nvidia.com.
Last edited by wsims (2010-06-22 15:06:04)

if you used the packages from repos, the blacklist is done automatically in nvidia,
$ pacman -Qo /etc/modprobe.d/nouveau_blacklist.conf
/etc/modprobe.d/nouveau_blacklist.conf is owned by nvidia 195.36.31-1
$ cat /etc/modprobe.d/nouveau_blacklist.conf
blacklist nouveau
but i guess you just want to mess your system by using unsupported and very bad ways and you are way smarter than the devs if you used that installer
Last edited by wonder (2010-06-22 14:10:01)

Xorg 1.8 + nvidia drivers

Hey guys!
Yesterday, I upgraded to the new xorg 1.8.0.901-1 with nvidia 195.36.24-1 and nvidia-utils 195.36.24-2, but in some sites the scrolling is veeeeery slow (using the scroll bar, with the mouse wheel it's better, but not 100%), example page: https://bugs.launchpad.net/firefox/+bug/38131 . In this page, when I try to scroll down using the scroll bar, my X process consumes between 40 and 55% of CPU o.O, and Firefox is very choppy (ps. Pango is disabled in Firefox).
My video card: 01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8400 GS] (rev a1)
Am I missing some important/magic option in the device section?
Here's my xorg.conf (generated by X -configure)
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "glx"
Load "dri"
Load "record"
Load "dri2"
Load "dbe"
Load "extmod"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "G86 [GeForce 8400 GS]"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Someone else with slow scrolling in that page?
Thanks in advance!
Last edited by estevao (2010-05-02 22:01:43)

I only have these (no xorg.conf):
~ $ cat /etc/X11/xorg.conf.d/20-nvidia.conf
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "RandRRotation" "true"
Option "NoLogo" "true"
Option "Coolbits" "1"
Option "TripleBuffer" "True"
# Option "DamageEvents" "True"
# Option "UseEvents" "True"
# Option "BackingStore" "True"
Option "DPMS" "True"
Option "RegistryDwords" "PerfLevelSrc=0x3333"
EndSection

NVIDIA driver doesn't dynamically change power source

I'm using the NVIDIA driver on an MSI laptop, and I've noticed that it doesn't dynamically detect my power source. The result of this is that if I boot the computer on battery power, then plug it in, the video card will continue to perform at less-than-maximum performance until I reload the driver with modprobe (of course, this is annoying because I have to exit from X11 first, then restart X11 after). This goes the other way, as well; that is, I can boot the machine on AC power, then unplug it and the video card will continue to run as if it were still on AC power. I have the "PowerMizer" configured to "Adaptive" in the settings.
Has anyone else experienced this issue? Any ideas on how to solve it?
Thanks.
Arch x86_64
NVIDIA 195.36.15
MSI MS-1651 laptop
NVIDIA GeForce 9600M GT

Took me a bit to work out why my nvidia card wouldn't behave the way I wanted it to on battery / AC.
I've just achieved the behaviour you're describing working on my Dell laptop (I wanted adaptive on battery, full performance on AC in X).
What works for me is:
Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x3322; PowerMizerDefaultAC=0x1"
... in xorg.conf and making sure you have installed acpid and starting it at boot.
It seems the nvidia driver uses acpid to detect if the cable has been pulled or not -- if you don't have acpid running it will always stay at max performance with my xorg.conf device settings listed above.
All I did was install acpid, started it at boot in rc.conf, no acpid configuration at all (i.e. I didn't touch a file except for rc.conf after I installed it), then I found the nvidia driver was able to detect the AC state.
If you want to tweak the settings for an on boot scenario (e.g. runlevel 3, no X), I'm pretty sure you can pass module parameters to get what you want -- however I haven't bothered with that as I'm always in X anyway.
Hope this helps, cheers.
References:
http://tutanhamon.com.ua/technovodstvo/ … IX-driver/
http://wiki.archlinux.org/index.php/Acpid
Last edited by pezz (2010-06-02 16:35:28)

Nvidia g210m driver?

I have a new Asus UL80VT with an NVidia G210M graphics card. I gather this card is not supported by the nvidia 195.36.15 driver. Is there an alternative?
thanks,
Thea

I have the ul50vt model which is similar...as of right now there is only experimental support.
Here http://www.linlap.com/wiki/asus+ul80vt is a link with a breakdown of basic linux compatibility right now.
Check out these links for the various community support of hybrid-graphics currently in the works. It seems like the project in the first link is working itself into the next major kernel release so we may get lucky!
http://asusm51ta-with-linux.blogspot.com/
http://linux-hybrid-graphics.blogspot.c … re-is.html
http://www.phoronix.com/forums/showthread.php?t=21979

Nvidia driver fails to load with NV GT-220 graphics card

I am using 2.6.33-ARCH of May 13th, I installed a Nvidia GT-220 graphics card over my onboard 6100,
it was using nouveau, i tried to upgrade to using the nvidia driver but find now that i am not able to
modprobe -i nvidia i get Fatal: Error inserting nvidia (/lib/modules/2.6.33-ARCH/kernel/drivers/video/nvideo.ko
modinfo nvidia shows it in the above location.
startx gives me: cannot execute binary file.
even after !nouveau in MODULES /etc/rc.conf it shows up with lsmod |grep nouveau

I installed the nvidia drivers with: sudo pacman -S nvidia nvidia-utils
I seem to of gotten more than one problem with my attemps at resolving this. The issue with nvidia module has been resolved by reinstalling the previous kernel26 2.6.31.3-1 it apparently doesnt have nouveau. and lsmod |grep nouveau gives null reply so its gone...
I used sudo nvidia-xconfig and it completed as expected and wrote a new xorg.conf but i am still getting
cannot execute binary file when i try using startx.
startx gives me: cannot execute binary file. additionally using: sudo X -configure gives the same error.
the versions of nvidia are under question: I have nvidia 195.36.15-2 and nvidia-utils 195.36.15-1
I am not sure if different minors are a problem, just noting the difference.

NVIDIA OpenGL version not recognised properly

I recently found a problem with my system and OpenGL. I know for a fact that my GTS 250 graphics card supports at least OpenGL 2.1, but glxinfo reports the OpenGL version being used is 1.4 and newer OpenGL features cause programs to crash.
I've been searching for the past day and a half now and haven't found an answer. Does anyone know what could cause this? Here's my xorg.conf if that helps:
Section "ServerLayout"
Identifier "nVidia TwinView"
Screen 0 "TwinView Screen" 0 0
InputDevice "Logitech Cordless Mouse" "CorePointer"
InputDevice "Logitech Cordless Keyboard" "CoreKeyboard"
EndSection
Section "ServerLayout"
Identifier "TVOnly"
Screen 0 "LCD TV and nVidia"
InputDevice "Logitech Cordless Mouse" "CorePointer"
InputDevice "Logitech Cordless Keyboard" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/OTF"
EndSection
Section "Module"
Load "glx"
Load "dri"
Load "record"
Load "extmod"
Load "dbe"
EndSection
Section "ServerFlags"
Option "DefaultServerLayout" "nVidia TwinView"
Option "Xinerama" "0"
Option "AutoAddDevices" "false"
Option "AllowEmptyInput" "false
EndSection
Section "InputDevice"
Identifier "Logitech Cordless Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Logitech Cordless Mouse"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/input/by-id/usb-Logitech_USB_Receiver-mouse"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Samsung SyncMaster 223BW"
VendorName "Samsung"
ModelName "223Bw"
Gamma 0.8
EndSection
Section "Monitor"
Identifier "Samsung SyncMaster 931B"
VendorName "Samsung"
ModelName "931B"
Gamma 0.8
EndSection
Section "Monitor"
Identifier "LCD TV"
VendorName "Philips"
Gamma 0.8
EndSection
Section "Device"
Identifier "nVidia GeForce GTS 250"
Driver "nvidia"
VendorName "nVidia Corporation"
Option "RenderAccel" "true"
Option "AllowGLXWithComposite" "true"
EndSection
Section "Screen"
Identifier "SyncMaster 223BW and nVidia"
Device "nVidia GeForce GTS 250"
Monitor "Samsung SyncMaster 223BW"
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1690x1050"
EndSubSection
EndSection
Section "Screen"
Identifier "SyncMaster 931B and nVidia"
Device "nVidia GeForce GTS 250"
Monitor "Samsung SyncMaster 931B"
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768"
EndSubSection
EndSection
Section "Screen"
Identifier "LCD TV and nVidia"
Device "nVidia GeForce GTS 250"
Monitor "LCD TV"
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1920x1080"
EndSubSection
EndSection
Section "Screen"
Identifier "TwinView Screen"
Device "nVidia GeForce GTS 250"
Monitor "Samsung SyncMaster 223BW"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "MetaModes" "DFP-0: 1680x1050_60 +0+0, DFP-1: 1280x1024_60 +1680+0;DFP-0: 1680x1050_60 +0+0, DFP-1: NULL"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "true"
Option "Render" "true"
EndSection

it should report
OpenGL version string: 3.2.0 NVIDIA 195.36.24
unless you messed around with the nvidia installer and didn't used the nvidia packages from our repos. i guess the soname that provides libgl is linking to mesa

MSI VN220GT MD1G|GeForce 220 GT - causing lock ups/screen freezes

Hi, I've been searching everywhere for my problem, and the things I find usually are left unanswered :(
I recently upgraded my old graphics card (GeForce 7300 GT) to the GeForce 220 GT, at that time I was using Windows XP SP3. Everything went fine then, I downloaded the newest driver from nVidia (195.62) and restarted, everything went smoothly.
It was then my computer started to freeze, to the point where I can't do anything (mouse/keyboard unresponsive). I am forced to force reboot. This freezing usually happens randomly when there's nothing to provoke the problem.
So I decided to upgrade to the new Windows 7. I did everything it told me to and everything went very well. But the problem still occurs, but more often, and around 30 minutes after logging in. I got the Windows 7 32 bit version of the new nVidia driver (195.62) and installed it. Did nothing. I have also tried to update windows which also did nothing.
These forum threads ask the same question I am now asking:
http://forums.nvidia.com/index.php?showtopic=109833
http://vip.asus.com/forum/view.aspx?SLanguage=en-us&id=20091113065624625&board_id=14&model=CG5270&page=2&count=17
I am currently posting this in safe mode, very frustrated too. Help would be greatly appreciated, I have no where else to find answers :S

Quote from: ZSDE on 14-January-10, 23:31:55
I did some more research on the net and it seems this PSU is labelled under many different names. I found a Portuguese site that did the test for this unit and then used the google translator tool.
refer to http://www.clubedohardware.com.br/artigos/1818/1
Some translated extracts:
The Coletek is a national brand aimed at the OEM market, or its source is aimed at companies that assemble PCs They have a separate brand for products geared to the retail market, the C3Tech. Today we test the model LC-8460BTX S (which, despite its name, is an ATX and not a BTX) that is sold as a source of 450 W. Really?.....
....Speaking of curiosity, in Figure 7 you can see the marking of the type of fuse in the circuit board of the source. All sources bring this information. But the curious thing here is that the marking indicates that for a source from 150 to 200 W a 5 A fuse should be used and to a source from 230 to 300 W from a 6.3 A fuse should be used. As this power supply uses a fuse of 6.3 A, we have a source between 230 and 300 W, according to their own existing markup on the printed circuit board thereof. As the manufacturer can turn that into 450 W on the label of the source is a magic that Mr. M can not explain.....
....The Coletek LC-S 8460BTX burned when trying to draw about 225 W (which would be our test number seven). So the most you can pull it was about 190 W (which would be our test of 200 W). More information and video on the next page.
So I recommend that you perhaps translate the whole article to get the full results. In your case, I believe the PSU should be the first place where you should try something a bit more realistic before you do anything else.
Quote from: Henry on 15-January-10, 08:09:28
For a system with a 220 installed PSU with +12V~30A minimum is recommended. My recommendation is to get nothing less than a quality PSU such as a Corsair VX450W +12V~33A. That junk PSU is typical of the worthless ones that are often provided by case manufacturers and examples of similar units that can be purchased for as little as $10 (USD) on eBay.
Thank-you so much guys, you've most likely have just diagnosed and gave me a solution for my problem
At first I never knew all PSU's were different, and that my new graphics card could handle whatever I had in my system at the moment.
I don't think I will bother checking my PSU if my current PSU is a Okia or a Xion, I may as well upgrade the thing anyway
Just some things I need cleared up though:
Firstly, is it the Corsair VX450W that I would want to buy and install to run my card? Is it affordable?
And secondly, are PSU's hard to install/upgrade? Where can I find a guide/tutorial for this kind of thing?

Weird mouse problem (clicks not being performed, -)

Recently I am suffering from a really weird problem.
The middle mouse button shows a really strange behaviour:
I'm using KDE from [extra], and middle clicking e.g. a link in a webbrowser (no matter which toolkit it uses) instead of opening one tab, opens the link in several tabs.
Also middle clicking on a tab, normally should close *one* tab, while here it often closes more than one tab. Since this happens in every application I use, no matter which toolkit is used, this cannot be a KDE/Qt problem, since e.g. Firefox is affected by it too. I also doubt that GTK is the cause of this problem…
[The middle clicking problem has been solved, by cleaning the mouse wheel]
[The problem below, still persists]
Furthermore, sometimes my laptop looks like it enters a "state", where my clicks are not "performed" the normal way:
E.g. I had a media player running, when my laptop got into this "state". No matter where I clicked on this app, the clicking action was performed on the Play button. Using Alt+Tab to focus another window/bring it to the front, and clicking in this window anywhere again resulted in the Play button getting clicked.
After quitting the media player app (through a keyboard shortcut) my clicks still did not work normal. They still simply were not performed. In order to "re-gain" the ability to click, I had to log out first.
Since I've setup my Arch Linux not to automatically start X/KDM after logging out, I found myself in the terminal, where I ran startx, in order to run KDE.
The terminal still had some output of my X session, but it wasn't displayed with normal characters, but rather with some weird characters, looking all scrambled and stuff, as you can see on the screenshot. http://imagebin.org/100067
I currently use the packages from the testing repo, but IIRC this behaviour was there even before installing the testing repo packages.
Extra information:
kernel26 2.6.34-1
xorg-server 1.8.1-1
nvidia 195.36.24-2
xf86-input-evdev 2.4.0-1
I run Arch Linux x86_64 on an Acer 5741G Laptop, with a NVidia Geforce GT 320M.
Interestingly, another user who suffers from the same bug is running a computer with intel graphics, so it probably is not the nvidia driver causing the problem either.
Originally the bug was reported as a rekonq bug: https://bugs.kde.org/show_bug.cgi?id=238987
Thank you
Last edited by pano (2010-06-09 11:43:21)

Hello,
I seem to suffer from the same problem. Sometimes (perhaps triggered by amarok, but I have to investigate this further before blaming this app) the left mouse button stops working. I can not perform left-klicks anymore. Everything is fine with the right button. If I log out and in again the mouse if fully back. In this loop X has not been restarted.
My setup:
KDE 4.4.5 (official packages)
X: X.Org X Server 1.8.1.902 (1.8.2 RC 2)
kernel: 2.6.34-ARCH #1 SMP PREEMPT
architecture: x86_64
mouse: Logitech MX1000 Laser (Logitech, Inc. MX-1000 Cordless Mouse Receiver)
If s.o. will ever work in this I will be happy to provide any information I can come up with.
Cheers and good night.

Full Screen Preview is Soft in Bridge CS4

I'm experiencing some notable softening of images when previewing them with full screen toggled on or when viewing images as a slide show. Type of file seems irrelevant (CR2, TIFF, JPEG, etc.) nor does image size make a difference. The strange thing is that when I mouse click on an image after toggling to full screen (which brings it to 100%) the image then appears sharp. Stranger yet, when I open a jpeg previously sized to fit my monitor at 100% I must still click on it to achieve a sharp image. Images otherwise appear fine in all workspaces and no hassles with nVidia 195 drivers. I've tried all options for thumbnail previews, reset preferences, purged cache all to no avail. Is this a bug or does a solution exist? Win XP sp3.

Curt's statement about known problems with Photoshop and Bridge is the understatement of the decade. At least as it pertains to my Nvidia GeForce 9800GT running a Gateway FHD2400 and HP w2408 monitor.
Upgrading from a stable install of CS2 to CS4 was a nightmare that cost me hundreds of hours with Adobe, and alone, with no solution. Even their "clean" utilities failed to remove the software (CS2 & CS4) from my computer for a clean install of CS4. I was forced to do a total format and reinstall of everything on my system. That was a two week nightmare.
After all that a clean install of CS4 still presented the same problems with PS. The final solution was to reinstall PS7 and use it in lieu of CS4. For my digital workflow it works just fine. Photoshop CS2 and CS4 do not like co-existing on the same system with some unknown software driver from the one interfering with the other.
The problems with CS4 were two-fold. The first was an extremely slow scroll rate no matter the video display settings or PS4 settings utilized. By slow I mean the zoom (Ctrl + 0) and then scroll around the screen using a square marquee would take up to 5 minutes on a, roughly, twenty megabyte file with no layers. The same process in PS7 took approximately two seconds per image side. The same image was uploaded to Adobe with similar results. No resolution to the problem came to light after two weeks of back and forth.
The other problem is that PS CS4 constantly comes with up the "...includes graphic card acceleration..." popup window. This, even though it has been disabled and enabled in PS. Neither option prevents the popup from appearing. The problem lies somewhere with Adobe's handling of the pasteboard (that area beyond the actual image) and its interaction with the video driver.
From both of these problems as explained it would seem that Adobe has known of the problem for some time. This iteration of the software works beautifully on a non-Nvidia system and various different Nvidia drivers have been tried. Since Bridge CS4, which is used continuously throughout a fifteen hour workday, works, I suppose I should count my blessings.
The most stable Nvidia GeForce 9800GT driver I have found to be is version 181.20 with video bios version 62.92.52.00.07
I will seriously consider whether or not to purchase the next version of Creative Suite when it appears. My experience has been that Adobe's corporate policy is to charge customers via new versions with fixes for problems that existed in earlier software builds. And then to create new dilemmas!
And thank you for all that you Curt.

T61 Problem: Getting external monitor to display 1920x1080 through VGA

I've got the Nvidia 195.62 drivers, but windows still shows a max resolution of 1600x1200 for a 1920x1080 lcd screen. I'm using the VGA out.
This is frustrating.

Which windows version do you use?
I think if windows recognizes your monitor, it would be okey.

I Deleted My Kernel.... Why, How, And How I Restored It [SOLVED]

This has to be my all time biggest screw up to date since using Linux!
WHY:
I've had one of my Ubuntu installs hacked and patched to support Nvidia GT220 HDMI audio out months ago, but thought I'd just wait for nvidia, alsa and/or the Linux kernel for support in the future for my Arch install. Well today, I read that the new 2.6.34 kernel has built in support for it....WooHoo!!
I thought I just had to enable the testing repo and upgrade the kernel. etc...
HOW:
So I temporarily enabled testing, and using my handy GTKPacman, upgraded to 2.6.34, or so I thought.
Upon rebooting, I discovered that I was still running 2.6.32, so next I install all the 2.6.34 stuff and delete all the 2.6.33 stuff.
Reboot error to kernel is now MISSING! Oh S%$T, now what!
HOW I Restored It:
After a quick attempt to use a Ubuntu kernel copied to Arch on the same computer and failure.....
I googled arch kernel restore. with my other computer, which leads me to http://wiki.archlinux.org/index.php/Ker … all_kernel
As always when I screw something up, Arch WIKI to the rescue!!! Boot into my Arch live CD.
Next problem, I don't remember what partition numbers are boot and root, so boot back to Ubuntu, get partition info, back to live CD.
Now I get chrooted into my Arch install, but don't know the exact kernel file details....back to ........
So I finally get all the info to restore Arch via the chroot live CD method.
I'm thinking that I should have known, and should have just navigated the file system for the info I needed via chroot live CD, but it didn't sink in till it was all over. Chroot/live CD = installed Arch file system.
I also know that Arch is directed more towards "experienced" Linux users, and they know all this, but....
Would it benefit anyone other than me, for the above mentioned WIKI, to remind or hint, along with instructions, at getting the required info via as part of the live CD kernel restore process??
Just a thought....
Last edited by jeff story (2010-05-31 21:10:03)

Figured out the kernel upgrade issue I had.
GTK pacman did not indicate any problems but the command line did.
[root@Arch2009p2 jeff]# pacman -S testing/kernel26
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia: requires kernel26<2.6.34
So I
[root@Arch2009p2 jeff]# pacman -S testing/nvidia
resolving dependencies...
looking for inter-conflicts...
Targets (4): kernel26-firmware-2.6.34-1 kernel26-2.6.34-1 nvidia-utils-195.36.24-2 nvidia-195.36.24-2
Total Download Size: 35.52 MB
Total Installed Size: 172.96 MB
Proceed with installation? [Y/n] y
:: Retrieving packages from testing...
kernel26-firmware-2... 804.9K 151.2K/s 00:00:05 [################################################################] 100%
kernel26-2.6.34-1-x... 22.8M 139.4K/s 00:02:47 [################################################################] 100%
nvidia-utils-195.36... 9.8M 130.0K/s 00:01:17 [################################################################] 100%
nvidia-195.36.24-2-... 2.1M 106.4K/s 00:00:21 [################################################################] 100%
checking package integrity...
(4/4) checking for file conflicts [################################################################] 100%
(1/4) upgrading kernel26-firmware [################################################################] 100%
(2/4) upgrading kernel26 [################################################################] 100%
>>> Updating module dependencies. Please wait ...
>>> MKINITCPIO SETUP
>>> ----------------
>>> If you use LVM2, Encrypted root or software RAID,
>>> Ensure you enable support in /etc/mkinitcpio.conf .
>>> More information about mkinitcpio setup can be found here:
>>> http://wiki.archlinux.org/index.php/Mkinitcpio
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.34-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
WARNING: All config files need .conf: /etc/modprobe.d/framebuffer_blacklist.pacsave, it will be ignored in a future release.
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.34-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26-fallback.img'...SUCCESS
==> SUCCESS
(3/4) upgrading nvidia-utils [################################################################] 100%
(4/4) upgrading nvidia [################################################################] 100%
ERROR: Module nvidia is in use
In order to use the new nvidia module, exit Xserver and unload it manually.
Upon reboot I get
[jeff@Arch2009p2 ~]$ uname -a
Linux Arch2009p2 2.6.34-ARCH #1 SMP PREEMPT Mon May 17 09:29:00 CEST 2010 x86_64 AMD Phenom(tm) 9850 Quad-Core Processor AuthenticAMD GNU/Linux
Now going to test HDMI audio output.
And it works great!!!
Last edited by jeff story (2010-06-01 02:08:37)

Cs3 bridge preview ghost windows

I am running CS3 on a Gateway P7805-u w/ Intel Core Duo 2 CPU 2.26/2.27 ghz processor, 4.0 ram and 64 bit os machine using Windows Vista. I am unable to use Bridge because the preview windows seem to duplicate themselves and I end up with what looks like multiple window (do they call them ghost windows?) of a preview open at once. I've tried uninstalling and reinstalling, updating my NVidia9800 1GB graphics card and updating CS3. The program ran fine when I first started using it on this machine. It works fine on my desktop computer running XP.
I really like Bridge and would like to upgrade to CS4, but not if I can't run it on this machine. Any feedback would be appreciated.

Simple workarounds. This is a problem with the graphics card not being up to the task. You will also have problems with the slide mode.
A simple way to get aroiund this is to click on restore down in upper right corner. You can expand window to max with arrows. If you run in max mode you will get problem you describe.
Go to advanced preferences in Bridge and click on "use software rendering". Seems to work OK in this mode, so not necessary to replace video card for this this problem.
Hope this solves your problem.
p.s. There are a lot of problems with Nvidia 195 series drivers with Bridge and PS.

Xorg memory leak [Solved]

Lately i've been noticing that whenever i run any app in fullscreen, X will eat ram like crazy. I've just been reading a PDF in Okular for 5 mins and X shot up from 50MB to 645MB.
This is a fresh install, and i was having this problem before i reinstalled Arch. It happens when i run any app from what i can tell. Definitely chromium and okular, i'll have to test others.
I'm currently running twinview with Nvidia 195.36.08-1 and Xorg 1.7.5-1
Last edited by Mountainjew (2010-03-03 14:27:40)

It's an 85 page Linux Journal magazine. Though, shouldn't that just put high memory usage on okular, not X?
It's the same when running Chromium fullscreen though, so i don't think it's just an issue with Okular.
Ah nevermind, i had it set to aggressive ram usage, put it back to normal and it seems ok.
Last edited by Mountainjew (2010-03-03 14:27:26)

Nvidia 195.36.15

Similar Messages

Maybe you are looking for