Nvidia AMD64 1.0-5332 trouble
Has anyone got X running using the Nvidia AMD64 1.0-5332 drivers? I compiled and installed the drivers according the instructions as supplied by nvidia. On my system (suse 9.0, k_deflt 2.4.21.201.x86_64, msi k8t neo fisr, athlon 64 3000, msi geforce fx5200) sax2 shows only a blank screen. Thanks Jeroen Amsterdam
Hello Jeroen, On Monday 01 March 2004 23:48, Jeroen Leijen wrote:
Has anyone got X running using the Nvidia AMD64 1.0-5332 drivers? I compiled and installed the drivers according the instructions as supplied by nvidia.
I installed this driver on system below succesfully, according the Nvidia instructions only. I did not need extra changes. Emile van Mierlo System: Tyan Tiger K8W (s2875), Dual Opteron 244, 2 x 1GB Kinston PC2700 registered RAM Adaptec 29160 SCSI, 2 x Maxtor Atlas 10k4 SCSI Nvidia FX5900 Graphics (Asus V9950SE), Plextor PX-708A CD/DVD Suse 9.0 kernel 2.4.21-201-smp, Nvidia 1.0-5336 driver
I am sure this is a SuSE yast2 newbie problem. But I have read and re-read the SLES 8 for AMD64 installation manual, The SuSE 9.0 installation manual and I have Googled for hours already. Help is appreciated. The specific problem is with Apache2, but I believe I should be using yast2 for all of my RPM installs, if I understand correctly. I downloaded the Apache2 rpms for SuSE 9.0 AMD64 from SuSE'S ftp site, expecting/hoping to be able to install them on my SLES 8 for AMD64 server. Here they are: apache2-2.0.48-24.x86_64.rpm apache2-devel-2.0.48-24.x86_64.rpm apache2-doc-2.0.48-24.x86_64.rpm apache2-example-pages-2.0.48-24.x86_64.rpm apache2-jakarta-tomcat-connectors-4.1.27-132.x86_64.rpm apache2-metuxmpm-2.0.48-24.x86_64.rpm apache2-mod_auth_mysql-20030510-99.x86_64.rpm apache2-mod_fastcgi-2.4.0-132.x86_64.rpm apache2-mod_macro-1.1.4-95.x86_64.rpm apache2-mod_perl-1.99_09_20030807-89.x86_64.rpm apache2-mod_php4-4.3.3-101.x86_64.rpm apache2-mod_python-3.0.3-131.x86_64.rpm apache2-mod_ruby-1.1.1-92.x86_64.rpm apache2-prefork-2.0.48-24.x86_64.rpm apache2-worker-2.0.48-24.x86_64.rpm Well of course I'm running into dependency problems. So I figure I would use yast2's "Install or Remove Software" option. So the first task was setting to use the "Change Source of Installation" to point at the the right directory - in my case /opt/software/apache2. Well when I try and add a "local directory" installation source it tells me: Error - Unable to create installation source from URL 'dir:///opt/software/apache2/'. Details: ERROR(InstSrc: E_non_instsrc_on_media) Is there some reasonably straightforward organization that the source directory needs to be in? I've tried using "yast2 -i apache2-2.0.48-24.x86_64.rpm". It installs the package with no complaints. I run an 'rpm -qa | egrep "apache2"' and it appears installed fine. But when I start up yast2 Install GUI for something else, it shows me all kinds of dependency problems. I was trying to stay with the RPM's rather than just untarring a distribution from Apache.org, but I'm starting to wonder. Thank you very much - Richard
On Mon, 1 Mar 2004 16:52:52 -0700
"Richard Mixon (qwest)"
I am sure this is a SuSE yast2 newbie problem. But I have read and re-read the SLES 8 for AMD64 installation manual, The SuSE 9.0 installation manual and I have Googled for hours already. Help is appreciated.
The specific problem is with Apache2, but I believe I should be using yast2 for all of my RPM installs, if I understand correctly.
I downloaded the Apache2 rpms for SuSE 9.0 AMD64 from SuSE'S ftp site, expecting/hoping to be able to install them on my SLES 8 for
You cannot directly install 9.0 RPMS on SLES8. The 9.0 RPMS require a newer glibc. Updating glibc is not trivial and has some traps. In addition apache has lots of references to other packages, so if you fulfilled all dependencies you would end up with half of the 9.0 in your SLES8 and likely quite some breakage. The better way probably would be to recompile the source rpm on SLES8. Even with that you will likely need to fix quite a few things by hand. -Andi
Andi,
Thank you for the advice. This is the start of a new web set of web servers we are rolling out over the next six months. I was
hoping to start clean with Apache 2, but maybe not.
So, I suppose this applies also to binary file from Apache Foundation
httpd-2.0.48-x86_64-unknown-linux-gnu.tar.gz
found at:
http://www.apache.org/dist/httpd/binaries/linux/
??
Also, what type of things might need to be fixed if I compiled from source?
Thank you again - Richard
-----Original Message-----
From: Andi Kleen [mailto:ak@suse.de]
Sent: Monday, March 01, 2004 5:39 PM
To: Richard Mixon (qwest)
Cc: suse-amd64@suse.com
Subject: Re: [suse-amd64] Help Installing SuSE 9 AMD64 Apache2 rpms with
yast2 on SLES 8 AMD64
On Mon, 1 Mar 2004 16:52:52 -0700
"Richard Mixon (qwest)"
I am sure this is a SuSE yast2 newbie problem. But I have read and re-read the SLES 8 for AMD64 installation manual, The SuSE 9.0 installation manual and I have Googled for hours already. Help is appreciated.
The specific problem is with Apache2, but I believe I should be using yast2 for all of my RPM installs, if I understand correctly.
I downloaded the Apache2 rpms for SuSE 9.0 AMD64 from SuSE'S ftp site, expecting/hoping to be able to install them on my SLES 8
for You cannot directly install 9.0 RPMS on SLES8. The 9.0 RPMS require a newer glibc. Updating glibc is not trivial and has some traps. In addition apache has lots of references to other packages, so if you fulfilled all dependencies you would end up with half of the 9.0 in your SLES8 and likely quite some breakage. The better way probably would be to recompile the source rpm on SLES8. Even with that you will likely need to fix quite a few things by hand. -Andi -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
Hello, Emile van Mierlo wrote:
Hello Jeroen,
On Monday 01 March 2004 23:48, Jeroen Leijen wrote:
Has anyone got X running using the Nvidia AMD64 1.0-5332 drivers? I compiled and installed the drivers according the instructions as supplied by nvidia.
I installed this driver on system below succesfully, according the Nvidia instructions only. I did not need extra changes.
Emile van Mierlo
System: Tyan Tiger K8W (s2875), Dual Opteron 244, 2 x 1GB Kinston PC2700 registered RAM Adaptec 29160 SCSI, 2 x Maxtor Atlas 10k4 SCSI Nvidia FX5900 Graphics (Asus V9950SE), Plextor PX-708A CD/DVD Suse 9.0 kernel 2.4.21-201-smp, Nvidia 1.0-5336 driver
so do I no problems System; Epox 8HDA (VIA K8T800), Nvidia fx5200 (Gainward Pro 660) kernel: Suse9 2.4.21-201-default nvidia installer: NVIDIA-Linux-x86_64-1.0-5332-pkg0.run mmhh.... works the open source driver (switch2nv) ? did the card work before with a other 64-Bit driver release ? detlef oertel
Jeroen,
My display is running fine with the NVIDIA1.0-5332 driver. It took a little
tweaking of size, resolution, depth, sync and refresh to get it to remain
stable with the XFree86 nv driver. I also turned off DPMS. Once the XFree86
config was stable, when I installed the NVIDIA driver, all I needed to do to
enable it was to change the driver name from "nv" to "nvidia".
Best regards
Hardware:
Gigabyte GA-K8NNXP, Athlon 64 3200+, MSI FX5700 TD 128, Mitsubishi DV172.
uname -a:
Linux linfinit 2.4.21-193-default x86_64 x86_64 x86_64 GNU/Linux
glxinfo:
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce FX 5700/AGP/SSE2
OpenGL version string: 1.4.1 NVIDIA 53.32
linfinit:/etc/X11 # diff -ub XF86Config.saxsave XF86Config
--- XF86Config.saxsave 2004-02-13 00:47:46.000000000 +1100
+++ XF86Config 2004-03-02 00:35:38.000000000 +1100
@@ -1,6 +1,6 @@
# /.../
# SaX generated XFree86 config file
-# Created on: 2004-02-13T00:43:27+1100.
+# Created on: 2004-02-13T00:47:46+1100.
#
# Version: 4.7
# Contact: Marcus Schaefer
Has anyone got X running using the Nvidia AMD64 1.0-5332 drivers?
I compiled and installed the drivers according the instructions as supplied by nvidia. On my system (suse 9.0, k_deflt 2.4.21.201.x86_64, msi k8t neo fisr, athlon 64 3000, msi geforce fx5200) sax2 shows only a blank screen.
Thanks Jeroen Amsterdam
Thanks everyone for your help. After all I managed to get X working. Hurray! Allthough I am not sure if it's running properly. See 2 questions below. At first X didn't run neither with the XFree open source driver nor with the drivers supplied by Nvidia. I think I finally got it running after I ajusted the AGP settings in XF86Config: Section "Device" BoardName "0x0322" BusID "1:0:0" Driver "nvidia" Identifier "Device[0]" VendorName "nvidia" Option "NvAgp" "1" EndSection "NvAgp" "1" did the trick. So my system is using the Nvidia AGP module. I don't understand why X doesn't run when using the regular kernel module AGPGART (i.e. Option "NvAgp" "3", the default setting). Running linux:/home/jeroen # dmesg | grep agp gives: Linux agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 690M agpgart: Detected AMD On-CPU GART chipset agpgart: AGP aperture is 128M @ 0xd0000000 Running linux:/home/jeroen # lsmod | grep agp gives nothing. 1. Has anyone X running with agpgart using the system setup described below? 2. Benchmark exchange: jeroen@linux:~> glxgears 7695 frames in 5.0 seconds = 1539.000 FPS 8951 frames in 5.0 seconds = 1790.200 FPS Thanks Jeroen from Amsterdam On Monday 01 March 2004 23:48, Jeroen Leijen wrote:
Has anyone got X running using the Nvidia AMD64 1.0-5332 drivers?
I compiled and installed the drivers according the instructions as supplied by nvidia. On my system (suse 9.0, k_deflt 2.4.21.201.x86_64, msi k8t neo fisr, athlon 64 3000, msi geforce fx5200) sax2 shows only a blank screen.
Thanks Jeroen Amsterdam
I have several workstations running with the Nvidia driver. There were
several problems early on....
Check /var/log/boot.msg to make sure that the kernel sees the AGP device...
<6>Linux agpgart interface v0.99 (c) Jeff Hartmann
<6>agpgart: Maximum main memory to use for agp memory: 5944M
<6>agpgart: Detected AMD 8151 chipset
<6>agpgart: AGP aperture is 128M @ 0xf0000000
<6>PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
Check /var/log/XFree86.0.log for the following line...
(WW) NVIDIA(0): Failed to verify AGP usage
This line indicates that the Nvidia driver could not recognize the AGP
tunnel, so it runs via the PCI interface (SLOW :)
The line should look like this...
(II) NVIDIA(0): AGP 8X successfully initialized
(II) NVIDIA(0): Setting mode "1600x1200,1600x1200"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
Make sure that you are running a current kernel. There were issues with
AGP in the 2.4.21.102 kernel that you get if you run right out ot the box.
I am running the 2.4.21-193 kernel, and am testing the current 2.4.21-201
kernel on a machine now. It seems to be working fine.
Check for an updated BIOS for your motherboard. I have systems running the
TYAN S2885 dual cpu motherboard with the v102 BIOS that work. On the
single processor S2875 motherboard, the BIOS that was on the web site did
not work with AGP on AMD64 Linux. I have a beta BIOS that seems to fix the
problem. I don't have any experience with the MSI board, so not sure if
that is your problem or not....
Kevin Gassiot
Advanced Systems Group
Visualization Systems Support
Veritas DGC
10300 Town Park Dr.
Houston, Texas 77072
832-351-8978
kevin_gassiot@veritasdgc.com
Jeroen Leijen
Has anyone got X running using the Nvidia AMD64 1.0-5332 drivers?
I compiled and installed the drivers according the instructions as supplied by nvidia. On my system (suse 9.0, k_deflt 2.4.21.201.x86_64, msi k8t neo fisr, athlon 64 3000, msi geforce fx5200) sax2 shows only a blank screen.
Thanks Jeroen Amsterdam
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
participants (7)
-
Andi Kleen
-
detlef oertel
-
Emile van Mierlo
-
Jeroen Leijen
-
Kevin_Gassiot@veritasdgc.com
-
Paul C. Leopardi
-
Richard Mixon (qwest)