You are not logged in.
Hi, after many hours, I've finally managed to get my Nvidia card running on Kernel 2.6.28 (i686)
This is done by downgrading to nvidia-177.82.
I cannot promise that this will work, but it worked for me,
and I can only hope it will work for you.
1. Get the installer for nvidia-177.82 (http://us.download.nvidia.com/XFree86/L … 2-pkg1.run)
2. In http://www.nvnews.net/vbulletin/showthr … 790&page=3, Under post #44, you will find a patch. Download it.
3. Patch the installer by running: sudo sh /where/your/NVIDIA-Linux-x86-177.82-pkg1.run/file/is/NVIDIA-Linux-x86-177.82-pkg1.run --apply-patch NVIDIA_kernel-177.82.diff.txt
This will produce a patched version called NVIDIA-Linux-x86-177.82-pkg1-custom.run.
4. Shutdown X, and run the patched version, it will say something about not being able to find the kernel interface, and will try to find it on Nvidia servers,
let it. It will fail and tell you that the kernel module needs to be built, just go along... Eventually, run nvidia-xconfig, and try 'startx'
Hope this helps anyone,
A.J.
Offline
hmm I am running here kernel 2.6.28 and nvidia 180.22 since weeks w/o any issues
Offline
hmm I am running here kernel 2.6.28 and nvidia 180.22 since weeks w/o any issues
+1. What was the problem ajschwartz?
Offline
Well, I ran a system upgrade yesterday, and after trying to reboot into the new Kernel, I got a Kernel panic message (The post is here somewhere).
Tried chrooting from both Arch Live-USB / Ubuntu64 Live-CD, and tried to reinstall/recompile the kernel/rerun mkinitcpio...nothing helped.
This morning, after some more attempts, I decided to re-install Arch.
Finished installing, Installed Xorg, Installed Nvidia-180.22, tried to "startx", and nothing - black screen, nonresponsive mouse an keyboards, and the CPU sounds like it's going up the roof...
Eventually I got a very basic xorg.config to work, which gave me a cave-man screen resolution...
Thats about it, drove me half insane
After several hours of going through forums and trying to get Nvidia-177 to run on the new Kernel, well - I found the solution
A.J.
Offline
hmm I am running here kernel 2.6.28 and nvidia 180.22 since weeks w/o any issues
My only issue that I had was that the first 2.6.28 testing kernel that I built needed a new "external modules" section in the PKGBUILD.
I hadn't noticed that the 2.6.28 ABS PKGBUILD added that new part for "external modules" that hadn't been in the kernel PKGBUILD before 2.6.28..... and it's needed for NVIDIA to build against. That confused me for about a day until someone told me to compare the PKGBUILD that I had been using with the new ABS testing PKGBUILD (which is now the core PKGBUILD)
So other than my own mistake, I have had no problems building either NVIDIA 180.18 or NVIDIA 180.22 on the 2.6.28 kernel.
Last edited by methuselah (2009-01-18 18:53:38)
Offline
This is the issue, that appeared in my case after upgrading to nvidia-180.22:
After short time of working it started to throw garbage all over the screen, like on the image above.
I have just installed back the nvidia-177.82-2, and this issue disappeared, though still I cannot log out of the Xorg (system hangs up), but it seems, that it is another issue, which I hope to resolve on my own .
Some applications are WYSIWYG, and some are WYSIWTF.
Offline
Glad to have helped!
Offline
This is the issue, that appeared in my case after upgrading to nvidia-180.22:
http://img403.imageshack.us/img403/5236 … ht2.th.jpg
After short time of working it started to throw garbage all over the screen, like on the image above.
I have just installed back the nvidia-177.82-2, and this issue disappeared, though still I cannot log out of the Xorg (system hangs up), but it seems, that it is another issue, which I hope to resolve on my own .
Damn. My screen doesn't look like that at all. I have noticed some slight bugginess when scrolling.
Offline
@ajshwartz:
here's your original post: http://bbs.archlinux.org/viewtopic.php?id=63224
i'm starting to see this a lot around here, but you posted an error log containing an error:
(II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(0): may not be running or the "AcpidSocketPath" X ....
but didn't say whether you tried to follow up on that error, or what you did, or if it helped at all.
it might not be relevant at all, but then again, it might lead you to a solution instead of a workaroud.
but congrats on getting your arch install up on its legs!
[23:00:16] dr_kludge | i want to invent an olfactory human-computer interface, integrate it into the web standards, then produce my own forked browser.
[23:00:32] dr_kludge | can you guess what i'd call it?
[23:01:16] dr_kludge | nosilla.
[23:01:32] dr_kludge | i really should be going to bed. i'm giggling madly about that.
Offline
kludge,
Well, I forgot to install acpid, hence the error Installing acpid did not help.
The resolution i posted is not relevant to the ACPI daemon error.
A.J.
p.s. Thanks for pointing that out.
Offline
ah, see, now that's all i wanted to know! here i was googling acpid and nvidia to try and find somethin' for ya.
i'm glad you found a work around, and i'm glad i don't have to deal with nvidia drivers.
[23:00:16] dr_kludge | i want to invent an olfactory human-computer interface, integrate it into the web standards, then produce my own forked browser.
[23:00:32] dr_kludge | can you guess what i'd call it?
[23:01:16] dr_kludge | nosilla.
[23:01:32] dr_kludge | i really should be going to bed. i'm giggling madly about that.
Offline
Very nice of you
Thanks!
And yes, lucky you...
Offline
This is the issue, that appeared in my case after upgrading to nvidia-180.22:
http://img403.imageshack.us/img403/5236 … ht2.th.jpg
After short time of working it started to throw garbage all over the screen, like on the image above.
I have just installed back the nvidia-177.82-2, and this issue disappeared, though still I cannot log out of the Xorg (system hangs up), but it seems, that it is another issue, which I hope to resolve on my own .
I had the same thing going on with 180.22 and my GeForce 8600M GS, so I also went back to 177.82 in the end (which by the way is working really nice with KDE 4.2 RC). I think I will just wait for nvidia to release another version of their driver. I already saw so many posts in their forum about this problem, so I'm pretty sure it will not take so long
Offline
Does anyone have a patch for 177.13 x86_64 to work on 2.6.28? The patch for x86 (per ajswchartz's post above) doesn't work and I'm having troubles with random freezes again with the 180.22 drivers. There doesn't seem to be any x86_64 patch in that nvnews post. I posted there as well to see if anyone else had one already.
Thanks,
Scott
Offline
That patch is for 177.82 and I know that it works on x86_64 because I'm using it here. There's also a patch for 177.80 that should work on either x86 or x86_64. Dunno about the 177.13 beta driver.
Offline
Thanks azleifel! I would have thought that 177.82 would have been on the "Linux AMD64 Display Driver Archive" page! Oh well. Works fine now.
Thanks,
Scott
Offline
Hi,
That's pretty weird, I have the same laptop (Asus G1S) and I don't have any problem with kernel 2.6.28 and latest nvidia driver.
I noticed some glitches when I am in emacs in console and I need to click in the terminal window to refresh the emacs view.
Offline
Hi,
That's pretty weird, I have the same laptop (Asus G1S) and I don't have any problem with kernel 2.6.28 and latest nvidia driver.
I noticed some glitches when I am in emacs in console and I need to click in the terminal window to refresh the emacs view.
Hi,
perhaps you have different version of BIOS? As you can see on the nvidia forums many people have similiar problem, but it seems that it is something more complex than just simply broken graphics driver. Otherwise we'd have some clearly defined groups, which have the same issue (i.eg. the GeForce 8600M GT users), but it's not as simple as that - if even you with the same hardware as I have, didn't encoutered that bug...
Just for curiosity - what options do you have set in xorg.conf?
Some applications are WYSIWYG, and some are WYSIWTF.
Offline
Hey, I've seen that before. It's all over the nvnews forums.
I think the fix is "Change High Performance images to Performance mode in nvidia-settings"
Cthulhu For President!
Offline
Currently I had it set on "Quality" rather than on "High performance", but I'll give it a try ('coz 180.22 is soooo sexy )
Ok, back on 180.22. I have played around with different settings, but I still have some unpleasant glitches from time to time, though it hasn't crashed yet... we'll see...
Last edited by Devastator (2009-01-20 14:52:59)
Some applications are WYSIWYG, and some are WYSIWTF.
Offline
Okay, I fixed it in a "Windowsy way" - rainstalled the drivers a few times, removed several files, mess around with config (randomly turning off some options), and haven't experienced any troubles since then... But I don't like the way I resolved it
Thanks for everyone's help .
Some applications are WYSIWYG, and some are WYSIWTF.
Offline
How does your xorg.conf look like now? And what else did you do exactly?
Offline
(...)
Section "Device"
# Insert Clocks lines here if appropriate
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600M GT"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "RegistryDwords" "PerfLevelSrc=0x3333"
# Option "NoLogo" "True"
Option "RenderAccel" "True"
Option "NoRenderExtension" "False"
Option "TripleBuffer" "True"
Option "OnDemandVBlankInterrupts" "True"
Option "AllowGLXWithComposite" "True"
Option "NvAGP" "3" # I suppose 0 would be ok too
# Option "AddARGBGLXVisuals" "True"
# Option "AllowSHMPixmaps" "1"
Option "ConnectedMonitor" "DFP" # use CRT, or DFP for LCD monitors
Option "TwinView" "0"
Option "metamodes" "1680x1050_60 +0+0; 1680x1050 +0+0"
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1680x1050"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1680x1050"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1680x1050"
EndSubSection
EndSection
And I have changed a few settings via nvidia-settings:
refresh frequency: 60Hz instead of auto (60Hz too, so it should not make any diffference)
Sync to vblank: on
allow flipping: true
image settings: performance
on-demand v-blank interrupts: on
flat panel scaling/Force Full GPU scaling: off
But I am rather inexperienced user, and I really don't know which setting makes it work well.
It might be also caused by cleaning-up the GL libraries (I removed nvidia and nvidia-utils by pacman, then removed manually all GL libraries, and installed nvidia, nvidia utils again. Also reinstalling mesa was needed, as GLU libraries were provided by this package)
Last edited by Devastator (2009-01-21 15:41:15)
Some applications are WYSIWYG, and some are WYSIWTF.
Offline
Okay, the issue appeared again. Really - this is frustrating...
The only strange thing I can find in logs is this, found in errors.log:
Jan 22 15:02:03 bananana NVRM: Xid (0001:00): 6, PE0001
Jan 22 15:02:04 bananana NVRM: Xid (0001:00): 13, 0001 00000000 00005097 00000538 3f78f8f9 00000040
Jan 22 15:02:04 bananana NVRM: Xid (0001:00): 13, 0001 00000000 00005097 00000538 3f78f8f9 00000040
Jan 22 15:02:05 bananana NVRM: Xid (0001:00): 13, 0001 00000000 00005097 00000538 3f78f8f9 00000040
Jan 22 15:02:07 bananana NVRM: Xid (0001:00): 13, 0001 00000000 00005097 00000538 3f78f8f9 00000040
Jan 22 15:17:08 bananana NVRM: Xid (0001:00): 6, PE0001
Jan 22 15:19:01 bananana NVRM: Xid (0001:00): 6, PE0001
Jan 22 15:20:04 bananana NVRM: Xid (0001:00): 13, 0001 00000000 0000502d 000008dc 00000000 00000100
and this in Xorg.0.log:
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Setting mode "1680x1050_60+0+0"
(II) NVIDIA(0): Initialized GPU GART.
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00003960, 0x00004f2c)
(WW) NVIDIA(0): WAIT (0, 6, 0x8000, 0x00004f2c, 0x00004f2c)
Strange, but changing anything by nvidia-settings (which requires reloading the drivers I suppose) fixes the thing for some time.
P.S. Screw it. Back on 177.82.
Last edited by Devastator (2009-01-22 16:17:23)
Some applications are WYSIWYG, and some are WYSIWTF.
Offline
Hope this helps anyone,
A.J.
It did, very much so. Thanks!
...
Offline