F16,F15 & F14 Nvidia driver guides - Page 38

Cygn · #**556** 27th October 2009, 05:50 PM

had tried that to no effect before posting. Should said that in the first post...

leigh123linux · #**557** 27th October 2009, 05:52 PM

OK, post

Code:

lsmod

Cygn · #**558** 27th October 2009, 05:54 PM

Friend google found something:

http://www.nvnews.net/vbulletin/show....php?p=2107352

last post say resolved in 190.42

Cygn · #**559** 27th October 2009, 05:54 PM

Code:

[haliyo@cygn ~]$ lsmod                 
Module                  Size  Used by  
fuse                   49320  2        
rfcomm                 57988  4        
bridge                 43864  0        
stp                     1972  1 bridge 
llc                     4944  2 bridge,stp
bnep                   14916  2           
sco                    16168  2           
l2cap                  32428  16 rfcomm,bnep
sunrpc                155680  1             
ipv6                  235672  40            
nf_conntrack_netbios_ns     2112  0         
p4_clockmod             4352  0             
btusb                  13560  2             
bluetooth              77104  9 rfcomm,bnep,sco,l2cap,btusb
nls_utf8                1524  1
vfat                    8608  1
fat                    40636  1 vfat
dm_multipath           14044  0
uinput                  6684  0
snd_intel8x0           28088  3
snd_ac97_codec         91768  1 snd_intel8x0
ac97_bus                1416  1 snd_ac97_codec
snd_pcm                63236  2 snd_intel8x0,snd_ac97_codec
dcdbas                  8516  0
nvidia               8858284  46
snd_timer              17760  1 snd_pcm
snd                    50292  10 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
pcspkr                  2176  0
i2c_i801               10212  0
iTCO_wdt               10368  0
soundcore               5484  1 snd
firewire_ohci          19712  0
firewire_core          37588  1 firewire_ohci
gspca_stv06xx          18084  0
iTCO_vendor_support     2760  1 iTCO_wdt
snd_page_alloc          7784  2 snd_intel8x0,snd_pcm
e1000                 103528  0
crc_itu_t               1604  1 firewire_core
gspca_main             19172  1 gspca_stv06xx
i2c_core               25032  2 nvidia,i2c_i801
videodev               29620  1 gspca_main
floppy                 47220  0
v4l1_compat            12056  1 videodev
ata_generic             4296  0
pata_acpi               3652  0
[haliyo@cygn ~]$

***Hlingler*** · #**560** 27th October 2009, 06:01 PM

Quote:

kernel-devel-2.6.30.8-64.fc11.i586
kernel-devel-2.6.30.9-90.fc11.i586

Why are these installed?

V

Cygn · #**561** 27th October 2009, 06:10 PM

why not ? :-)
was probably needed when building some gspca module from mercurial, not sure now.

leigh123linux · #**562** 27th October 2009, 06:32 PM

Quote:

Originally Posted by Cygn

Friend google found something:

http://www.nvnews.net/vbulletin/show....php?p=2107352

last post say resolved in 190.42

Try this post in a hour or two (repo is being updated).

http://forums.fedoraforum.org/showpo...91&postcount=4

***Hlingler*** · #**563** 27th October 2009, 06:50 PM

I would suggest that the installation of extraneous kernel-devel packages (i586 when you already have i686.PAE to match kernels) is potentially problematic: compilers (like those used by the nvidia drivers to build kmods) looking for kernel sources could become "confused" and use the wrong sources. It is possible that in some cases, you might need both, but unless specially/specifically required, I'd avoid such "mixing" of kernel-devel packages. I consider the compilers to be "stupid" enough to make such mistakes.

Perhaps now would be a good time to get a definitive answer on the above from someone more knowledgeable (Leigh ?).

V

stevea · #**564** 29th October 2009, 07:21 AM

Quote:

Originally Posted by Hlingler

I would suggest that the installation of extraneous kernel-devel packages (i586 when you already have i686.PAE to match kernels) is potentially problematic: compilers (like those used by the nvidia drivers to build kmods) looking for kernel sources could become "confused" and use the wrong sources. It is possible that in some cases, you might need both, but unless specially/specifically required, I'd avoid such "mixing" of kernel-devel packages. I consider the compilers to be "stupid" enough to make such mistakes.

Perhaps now would be a good time to get a definitive answer on the above from someone more knowledgeable (Leigh ?).

V

It is certainly *potentially* problematic, but to place blame properly it's usually the driver makefile at fault, not the compiler.

The primary reason to have the kernel-devel package around is so that one can compile modules, typically drivers, for a pre-built kernel. These files go into distinct directories based the kernel release name extension (the "uname -r" string) so there is little chance for confusion. OTOH I've never seen a driver build that requires anything other than one kernel's development files (mostly makefiles and include files), so there isn''t much justification for keeping around extraneous kernel-devel packages except for the few kernels in use.

For a long time most driver modules would use /usr/src/kernels/$(uname -r), or
/lib/modules/$(uname -r)/build linked to the same. The driver makefile invoke the kernel release makefile and ... the rest is quite complex. So the include files for the kernel you have currently booted, are typically used. Unfortunately we sometimes want to build a driver for a kernel that we haven't or can't boot or one with a variant extension name..

Another recent issue is that some kernel varients use the same kernel-devel package or perhaps have none of their own. In these cases you must also somehow make the build proceed without the default directory.
--

For the current case ...
If you run the NVIDIA driver package installer with the -A (advanced options) you will see this description.

Code:

./NVIDIA-Linux-x86-185.18.36-pkg1.run -A
...
  -k, --kernel-name=KERNEL-NAME
      Build and install the NVIDIA kernel module for the
      non-running kernel specified by KERNEL-NAME (KERNEL-NAME
      should be the output of `uname -r` when the target kernel
      is actually running).  This option implies
      '--no-precompiled-interface'.  If the options
      '--kernel-install-path' and '--kernel-source-path' are not
      given, then they will be inferred from KERNEL-NAME; eg:
      '/lib/modules/KERNEL-NAME/kernel/drivers/video/' and
      '/lib/modules/KERNEL-NAME/build/', respectively.
...

So Nvidia does give you a nice clean option (-kernel_name=2.6.30.....PAE) to select the kernel-devel you are building against. A lot of drivers aren't so clever and then you have to find ways to trick the makefiles or re-link the directories or whatever. Relinking the directories ((using "mv" and "ln -s", not code linking)) is a great opportunity to make a mess of things.

Only install the kernel sources or kernel-devels for the kernels you intend to boot.

I recommend searching out the makefile or installer options whenever available, as in the NVidia case.
My second choice would be to manually edit the driver makefile.
Try to avoid the confusion of switching around the kernel-devel or source directories.

Cygn · #**565** 29th October 2009, 03:47 PM

Quote:

Originally Posted by leigh123linux

Try this post in a hour or two (repo is being updated).

http://forums.fedoraforum.org/showpo...91&postcount=4

Code:

[haliyo@cygn ~]$ wget http://www.dfm.uninsubria.it/compiz/fusion-testing/nvidia/i386/nvidia-x11-drv-190.42-1.fc11.i586.rpm
....
2009-10-29 15:37:07 ERREUR 404: Not Found.

Cygn · #**566** 30th October 2009, 07:18 PM

190.42 works as expected.

Thx!

chegivara · #**567** 31st October 2009, 04:17 PM

Hi all

Code:

# uname -r
2.6.30.9-90.fc11.i586

Code:

# lspci |grep VGA
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1)

Installed drivers:

Code:

# yum install akmod-nvidia-96xx xorg-x11-drv-nvidia-96xx-libs

Code:

# rpm -qa |grep nvidia
akmod-nvidia-96xx-96.43.13-1.fc11.i686
kmod-nvidia-96xx-2.6.30.9-90.fc11.i586-96.43.13-1.fc11.i686
xorg-x11-drv-nvidia-96xx-96.43.13-2.fc11.i586
xorg-x11-drv-nvidia-96xx-libs-96.43.13-2.fc11.i586

Blacklisted:

Code:

# tail -n 1 /etc/modprobe.d/blacklist.conf 
blacklist nouveau

and remake initrd

Code:

mkinitrd -v /boot/initrd-`uname -r`.img  `uname -r`

Xorg:

Code:

 cat /etc/X11/xorg.conf
# Xorg configuration created by livna-config-display

Section "Files"
  	ModulePath   "/usr/lib/xorg/modules/extensions/nvidia"
    	ModulePath   "/usr/lib/xorg/modules/drivers"
    	ModulePath   "/usr/lib/xorg/modules"
EndSection

Section "ServerFlags"
	Option	    "AIGLX" "on"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "vesa"
EndSection

Section "Extensions"
	Option	    "Composite" "Enable"
EndSection

Also i'm trying add in menu.list vmalloc=256MB

But X not started:

Code:

(==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0):     enabled.
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the
(EE) NVIDIA(0):     system's kernel log for additional error messages and
(EE) NVIDIA(0):     consult the NVIDIA README for details.
(EE) NVIDIA(0):  *** Aborting ***
(II) UnloadModule: "nvidia"
(II) UnloadModule: "wfb"
(II) UnloadModule: "fb"
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Debroyston · #**568** 31st October 2009, 05:38 PM

Installing Nvidia drivers appears to be OK but I have a problemm getting the details of the monitor entered into /etc/X11/xorg-conf. This is either using system-confi-display or editing the file with mousepad.
It keeps putting the "default" settings into Monitor0.
Can any one suggest how I can solve this?

nightflare · #**569** 1st November 2009, 02:01 PM

hi.. everyone..

i'm a newbie to linux. Recently installed Fedora 11 on my system. i hav this configuration :

Mother Board: M2N68-AM PLUS
Processor: AMD Sempron 2.7 GHz 1MB Total Cache (Fedora recognize this as AMD Processor Model Unknown)
Memory: 1Gb
Graphics Card : nVIDIA GeForce 7025
Partition: 2GB Swap; 10 GB /; 8gb Windows; 30gb Data; 70 gb Funclub

Fedora Release 11 (Leonidas)
Kernel Linux 2.6.29.4-167.fc11.i686.PAE

from fedora unofficial guide site, i got a code to install driver for my graphics card. code is this:

su -c 'yum install akmod-nvidia-173xx xorg-x11-drv-nvidia-173xx-libs.i586 xorg-x11-drv-nvidia-173xx-libs.x86_64'

after installation i restarted the system. when os loads it supposed to go to a graphical Log in screen, but it blanks and drops to a text mode log in screen. it also says that some nvidia driver not found and it wil be disabled till a new one is found.
am i did something wrong..? is there any way to revert all back to original one..? like Windows Restore..

Any way i reinstalled ma fedora. But i would really i like to knw if this happens what must do to get back GUI. And i really like hav 3D desktop shown in those screenshots.

sorry for lengthy post.. Please reply. 1000 thanks in advance..

leigh123linux · #**570** 2nd November 2009, 10:11 AM

Quote:

Originally Posted by nightflare

hi.. everyone..

i'm a newbie to linux. Recently installed Fedora 11 on my system. i hav this configuration :

Mother Board: M2N68-AM PLUS
Processor: AMD Sempron 2.7 GHz 1MB Total Cache (Fedora recognize this as AMD Processor Model Unknown)
Memory: 1Gb
Graphics Card : nVIDIA GeForce 7025
Partition: 2GB Swap; 10 GB /; 8gb Windows; 30gb Data; 70 gb Funclub

Fedora Release 11 (Leonidas)
Kernel Linux 2.6.29.4-167.fc11.i686.PAE

from fedora unofficial guide site, i got a code to install driver for my graphics card. code is this:

su -c 'yum install akmod-nvidia-173xx xorg-x11-drv-nvidia-173xx-libs.i586 xorg-x11-drv-nvidia-173xx-libs.x86_64'

after installation i restarted the system. when os loads it supposed to go to a graphical Log in screen, but it blanks and drops to a text mode log in screen. it also says that some nvidia driver not found and it wil be disabled till a new one is found.
am i did something wrong..? is there any way to revert all back to original one..? like Windows Restore..

Any way i reinstalled ma fedora. But i would really i like to knw if this happens what must do to get back GUI. And i really like hav 3D desktop shown in those screenshots.

sorry for lengthy post.. Please reply. 1000 thanks in advance..

Thread moved.