You are not logged in.
@sector11 there's a tidal wave of documentation on the smxi site which I never managed to make sense of. Can you point us to a tutorial for beginners? How did you get started?
Hi John ... This is not a cop out. This is what I did:
went to the site, selected:
2) install-scripts
and then I selected:
1) Installing smxi / sgfxi / svmi with zip installer
and checked that unzip was installed as per instructions.
Then I did what they said:
# as root, run the following command
cd /usr/local/bin && wget -Nc smxi.org/smxi.zip && unzip smxi.zip && smxisudo cd /usr/local/bin && wget -Nc smxi.org/smxi.zip && unzip smxi.zip && smxithat grabbed the zip file, unzipped it and ran it.
When it runs have it stop the desktop and just fallow instructions.
I use it to add the Liquorix repos to my sources list, and update the kernel, then I continue to graphics and install the latest nvidia driver.
It's menu drives and always has a way to go back one level in the menu.
- also you can use [shift]+[up] to see stuff that scrolled past your screen.
Once it's installed drop to a tty [Ctrl]+[Aly]+[F1]
sign in as your user... then:
su
password:
smxiruns it again.
That and I bent VastOne PM box all to heck to make sure I did it right, it must be pretty mangled by now. 
One thing to note: Do not use smxi with Ubuntu. They (the smxi devs) say Ubuntu has gone far enough away from Debian that it will not work.
I have never run anything other than "smxi" as it runs the other scripts via menu options.
#! Etiquette | Conky PitStop | VSIDO | Interactive LUA
Weather v9000 | Teo x4 Sites | Arclance | Finnish
Offline
@Erinsfan thank you - I might take you up on that offer when Waldorf goes stable and the desktop has to cross the great divide with its ancient hardware.
@sector11 thank you too - that's just the sort of getting started info I was looking for.
John
--------------------
( a boring Japan blog , and idle twitterings )
Offline
I just updated my Waldof 64b to linux 3,2,0-4 and it will not boot to gui just a terminal. I loaded nivida driver with this #! forum instructions. http://crunchbang.org/forums/viewtopic.php?id=19332 and was reassured the driver would update with kernel. I can choose the old kernel (3.2.0-3) from grub and everything is fine. is there a way to fix this.
Offline
You must re-install the nvidia kernel module for the new kernel.
The easiest way is probably to set aside the xorg.conf file, boot into the new kernel and go through that install procedure again:
(1) boot into the old kernel
(2) in a terminal window
sudo mv -v /etc/X11/xorg.conf /etc/X11/xorg.conf.nvidia(3) boot into the new kernel (using the nouveau driver)
(4) go through the nvidia install procedure again
(5) reboot into the new kernel
All should be well now.
Last edited by xaos52 (2012-11-03 19:08:37)
bootinfoscript - emacs primer - I ♥ #!
Offline
Offline
Those were replaced by version 3.2.0-4 by now.
Run
sudo apt-get update && sudo apt-get dist-upgradeThen try the m-a command again.
bootinfoscript - emacs primer - I ♥ #!
Offline
Thank you!! 
It's working now! 
Offline
this worked for me in 64 bit, but I added one step: I got rid of the xserver-xorg-video-nouveau driver, because I got a message about it conflicting with nvidia. And I had to reboot; I couldn't restart SLiM.
Nouveau has been absolute crap with my EVGA GeForce GT 630. Every few seconds, my screen flickers in X. And in tty consoles, I get this:
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 48
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 48
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 49
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 49
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 54
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 48
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 48
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 49
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 49
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 54
[uptime] [drm] nouveau 0000:01:00.0: No native mode, forcing panel scaling
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 48
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 48
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 49
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 49
[uptime] [drm] nouveau 0000:01:00.0: unknown i2c port 54I really need to learn something about bug reporting, cos this happened in madbox 12.04 as well. I'm going to pop in some other live distros and see where else I find the issue. It did not pop up in Stella 6.3, but IIRC, that uses nv, not nouveau.
Offline
This method should work with most stock or custom kernels. For a custom kernel, you need to have its Linux headers installed.
sudo apt-get install module-assistant nvidia-kernel-commonThen to build module
sudo m-a auto-install nvidia-kernel-source
I have it working know, but was just wondering... I have the default waldorf-installation considering kernels. Reading this, i don't have to install module-assistent and nvidia-kernel-common. But is it necessary to build the module in a stock kernel?
Offline
This worked for me man, thank you very very very much.
"Then what do we do now?"
"Cultivate patience and smoke cigarettes."
Offline
To the original poster; thanks, worked fine here as well (I did everything via ssh, as the machine was blank). And i got my vdpau/mplayer working as well.
inxi -G
Graphics: Card: NVIDIA G96 [GeForce 9400 GT] X.Org: 1.12.4 driver: nvidia Resolution: 1280x1024@60.0hz
GLX Renderer: GeForce 9400 GT/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 304.64Last edited by brontosaurusrex (2013-03-24 16:23:40)
Offline
I am glad this post and follow ups have helped people.
I have always used Nvidia with Linux because I believe they have the best drivers.
Geek by nature
Linux by choice.
Crunchbang by default
Offline
Thank you bartos! I finally found one that didn't crash my system I already had Xorg.conf set up from previous try's so I was able to follow these steps exactly. The debian version was playing hell with chrome-beta. Now life is good again. 
Inside of a ring or out, ain't nothing wrong with going down. It's staying down that's wrong.
Muhammad Ali 
Offline
The solution in this thread worked for me. Thank you Bartos!!
Ref #17 pvsage
Aside from games, what applications use these more advanced GPU capabilities? If, for example, the most graphics-intensive use one has for a PC is viewing HD video, do the proprietary drivers really improve performance?
As for other applications which use the GPU, I run VMware Workstation 9.02 on Waldorf host (2013 build), kernel 3.2.0-4-amd64, with Nvidia GeForce GTX570. VMware complained a lot at startup about not having the proper graphics drivers while using Nouveau. I ran Waldorf thru this thread and voila, no more VMware nags and I now have full hardware support on my VMware guests. I don't run VirtualBox so I can't speak to that.
I also tried Hardran's route
http://crunchbang.org/forums/viewtopic.php?id=11900&p=1
on both Statler and Waldorf 2012 builds with no success and no time to troubleshoot, so I just set it aside until now.
Edit:
Forgot to mention two minor speedbumps I saw in the sequence: (1) I had to use sudo to stop my desktop in the first instruction - this did not seem to affect the installation; (2) it warned me of the competing Nouveau driver, and suggested that a reboot could cure it. Said "OK", rebooted, and it did cure the conflict.
Last edited by skibum (2013-05-02 21:34:19)
Offline
Works on Nvidia GF 9600 GT
root@debian:/# glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: GeForce 9600 GT/PCIe/SSE2
GL_NV_conditional_render, GL_NV_copy_depth_to_color, GL_NV_copy_image,
GL_NV_parameter_buffer_object2, GL_NV_path_rendering,
GL_NVX_conditional_render, GL_NVX_gpu_memory_info,
GL_OES_depth_texture, GL_OES_element_index_uint, GL_OES_fbo_render_mipmap,
Offline
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.