Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
"nvidia" driver not working: No Devices Detected e
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3, 4  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Wed Aug 04, 2004 6:39 pm    Post subject: "nvidia" driver not working: No Devices Detected e Reply with quote

This is an ongoing problem.

Could someone give me some ideas or a checklist of sorts that I could use to FINALLY solve this?

I'm not sure where to even begin and I'm not certain what info is relevant at this point. Do I understand correctly that the "No Devices Detected" error means that X isn't finding a necessary videocard?
Back to top
View user's profile Send private message
gentoo_dude
l33t
l33t


Joined: 08 May 2004
Posts: 645
Location: Washington, DC

PostPosted: Wed Aug 04, 2004 6:54 pm    Post subject: Reply with quote

that means that the driver you want to use for X is not finding the card. Make sure that the driver you use is the proper one.
I would start with the generic ones first.
Run xorg.conf (x86free.conf -- depending which X server you have installed) and if you have Nvidia card, first use the nv driver (generic).
After you make sure that it works, if you want get the nvidia-kernel emerged and use the module (driver) which it installs (I believe is nvidia). If you have another card, make sure you know which one it is (check the card it should have some labels on it) and in the configuration scroll through the list of drivers.
Back to top
View user's profile Send private message
codergeek42
Bodhisattva
Bodhisattva


Joined: 05 Apr 2004
Posts: 5142
Location: Anaheim, CA (USA)

PostPosted: Wed Aug 04, 2004 6:56 pm    Post subject: Reply with quote

Did you try re-emerge-ing the latest (6106) nvidia-glx and nvidia-kernel (in ~arch)? Did you
Code:
# modprobe nvidia
? Do you have agpgart support in your kernel?
_________________
~~ Peter: Programmer, Mathematician, STEM & Free Software Advocate, Enlightened Agent, Transhumanist, Fedora contributor
Who am I? :: EFF & FSF
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Wed Aug 04, 2004 11:57 pm    Post subject: Reply with quote

codergeek42,

I run ~x86 by default, so yes, as usual I re-emerged the nvidia-kernel and glx after a new kernel build (which I did just to see if it was an issue with the current kernel I was running.

and yes, as always, I did #modprobe nividia

and also yes, agpgart is loaded as a kernel Module.

I'm using xorg and have in the past been running with the "nvidia" driver w/o issue. I'm currently having to use the "nv" driver. I'm not exactly sure what I changed along the line to cause the problem. At some point I had to restart X and it didn't come up. That's when the fun began.

Currently running love-sources 2.6.8-rc2-love3 and xorg.

#lsmod shows the nvidia module.
nvidia 4816564 0
agpgart 26408 1 via_agp

dmesg shows these lines:
vesafb: NVidia Corporation, NV20 Board, Chip Rev A3 (OEM: NVidia)
*and*
NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-6106 Wed Jun 23 08:14:01 PDT 2004
*and*
agpgart: Detected VIA KT266/KY266x/KT333 chipset
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: AGP aperture is 128M @ 0xf0000000

AND in my xorg.log.old: (From the failed "nvidia attempt")

(--) PCI:*(1:0:0) nVidia Corporation NV20 [GeForce3 Ti 200] rev 163, Mem @ 0xea000000/24, 0xec000000/26, 0xeb800000/19, BIOS @ 0xeb7f0000/16

The point in the log that the "nvidia" driver fails ends with:
(II) Primary Device is: PCI 01:00:0
(EE) No devices detected.

The next 2 lines that *SHOULD* follow according to the log using the "nv" driver are:

(--) Assigning device section with no busID to primary device
(--) Chipset GeForce3 Ti 200 found

Not sure if that helps or not.
Back to top
View user's profile Send private message
gentoo_dude
l33t
l33t


Joined: 08 May 2004
Posts: 645
Location: Washington, DC

PostPosted: Thu Aug 05, 2004 9:46 pm    Post subject: Reply with quote

Usually it worked for me after I updated my X server to reinstall the driver again
Code:
emerge nvidia-kernel
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Thu Aug 05, 2004 9:56 pm    Post subject: Reply with quote

Already done that.....several times.
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Thu Aug 05, 2004 9:58 pm    Post subject: Reply with quote

Already done that.....several times.
Back to top
View user's profile Send private message
formzero
n00b
n00b


Joined: 14 Dec 2002
Posts: 36
Location: Noisetown

PostPosted: Fri Aug 06, 2004 5:03 pm    Post subject: Reply with quote

yea, i've had the same problem. i don't know what is going on to be honest. i copied my XF86Config to xorg.conf and it will only load with the "nv" driver.

i've re-emerged the nvidia-kernel driver numerous times with no luck. using the 6106 version. i even attempted the nvidia-kernel that is currently marked stable. same result. anyone care to shed some light on this.
Back to top
View user's profile Send private message
codergeek42
Bodhisattva
Bodhisattva


Joined: 05 Apr 2004
Posts: 5142
Location: Anaheim, CA (USA)

PostPosted: Fri Aug 06, 2004 5:10 pm    Post subject: Reply with quote

Have you tried compiling agpgart statically rather than as a module?
_________________
~~ Peter: Programmer, Mathematician, STEM & Free Software Advocate, Enlightened Agent, Transhumanist, Fedora contributor
Who am I? :: EFF & FSF
Back to top
View user's profile Send private message
T-Bird
n00b
n00b


Joined: 28 Mar 2003
Posts: 71

PostPosted: Fri Aug 06, 2004 5:46 pm    Post subject: Reply with quote

I had this problem, but the newest nvidia-glx and -kernel fixed it.
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Fri Aug 06, 2004 6:33 pm    Post subject: Reply with quote

codergeek42,

Currently, I've REMOVED agpgart from the kernel. I can't recall if I've tried statically compiling agpgart or not...wouldn't suprise if I already had...I've done so much to try and resove this I've lost track of it.

I'll try it again shortly anyway and post back.
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Fri Aug 06, 2004 7:30 pm    Post subject: Reply with quote

No luck. Found out that the nvidia-kernel and glx have been update though....6111 is out now.

Even went back and installed agpgart as a module again since the new nvidia-kenel was out...just trying...anything.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 46279
Location: 56N 3W

PostPosted: Fri Aug 06, 2004 7:38 pm    Post subject: Reply with quote

ck42,

The nvida driver comes with its own agpgart driver. Do not use any of the kernel ones as built in, that blocks the nvdia one.

Can you post the /var/log/XFree86.0.log file after X has failed to come up with the nvidia driver. (Do make sure the kerenl module is loaded before you attempt to start X). you may as well post the XF86Config file too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Fri Aug 06, 2004 8:04 pm    Post subject: Reply with quote

I thought that the Nvagp setting in the xorg.conf file (1,2, or 3) specified the agpgart driver (or at least the order of which one to try).

Forgot to mention that I've also recently pulled the USB2.0 drivers from the kernel. There's been some rumours on the forum that these are causing some X conflicts. Didn't make any difference in my case though.

As for making sure the kernel module is loaded before attempting to start X, do you mean nvidia is listed in a #lsmod query?



Here's the log after trying with the nvidia driver AND nvagp in the kernel as a module:

cat Xorg.0.log.old

Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.6.7-love7 i686 [ELF]
Current Operating System: Linux Gentoobox 2.6.8-rc2-love3 #9 Fri Aug 6 15:07:31 EDT 2004 i686
Build Date: 17 July 2004
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 6 15:13:35 2004
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Simple Layout"
(**) |-->Screen "Screen 0" (0)
(**) | |-->Monitor "NEC FE750+"
(**) | |-->Device "Ti450"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(WW) The directory "/usr/share/fonts/TrueType/" does not exist.
Entry deleted from font path.
(**) FontPath set to "/usr/share/fonts/local/,/usr/share/fonts/misc/,/usr/share/fonts/75dpi/:unscaled,/usr/share/fonts/100dpi/:unscaled,/usr/share/fonts/Speedo/,/usr/share/fonts/Type1/,/usr/share/fonts/freefont/,/usr/share/fonts/75dpi/,/usr/share/fonts/100dpi/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(II) Open APM successful
Using vt 7
(--) using VT number 7

(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1106,3099 card 1043,807f rev 00 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1106,b099 card 0000,0000 rev 00 class 06,04,00 hdr 01
(II) PCI: 00:09:0: chip 14e4,4401 card 1043,80a8 rev 01 class 02,00,00 hdr 00
(II) PCI: 00:0b:0: chip 1013,6003 card 5053,3357 rev 01 class 04,01,00 hdr 00
(II) PCI: 00:10:0: chip 1106,3038 card 1043,808c rev 80 class 0c,03,00 hdr 80
(II) PCI: 00:10:1: chip 1106,3038 card 1043,808c rev 80 class 0c,03,00 hdr 80
(II) PCI: 00:10:2: chip 1106,3038 card 1043,808c rev 80 class 0c,03,00 hdr 80
(II) PCI: 00:10:3: chip 1106,3104 card 1043,808c rev 82 class 0c,03,20 hdr 00
(II) PCI: 00:11:0: chip 1106,3177 card 1043,808c rev 00 class 06,01,00 hdr 80
(II) PCI: 00:11:1: chip 1106,0571 card 1043,808c rev 06 class 01,01,8a hdr 00
(II) PCI: 01:00:0: chip 10de,0201 card 10b0,0c3c rev a3 class 03,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xea000000 - 0xeb5fffff (0x1600000) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xeb700000 - 0xefffffff (0x4900000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:0:0) nVidia Corporation NV20 [GeForce3 Ti 200] rev 163, Mem @ 0xea000000/24, 0xec000000/26, 0xeb800000/19, BIOS @ 0xeb7f0000/16
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xf0000000 from 0xf7ffffff to 0xefffffff
(II) Active PCI resource ranges:
[0] -1 0 0xe8000000 - 0xe80000ff (0x100) MX[B]
[1] -1 0 0xe8800000 - 0xe88fffff (0x100000) MX[B]
[2] -1 0 0xe9000000 - 0xe9000fff (0x1000) MX[B]
[3] -1 0 0xe9800000 - 0xe9801fff (0x2000) MX[B]
[4] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[5] -1 0 0xeb7f0000 - 0xeb7fffff (0x10000) MX[B](B)
[6] -1 0 0xeb800000 - 0xeb87ffff (0x80000) MX[B](B)
[7] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B](B)
[8] -1 0 0xea000000 - 0xeaffffff (0x1000000) MX[B](B)
[9] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
[10] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[11] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[12] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xe8000000 - 0xe80000ff (0x100) MX[B]
[1] -1 0 0xe8800000 - 0xe88fffff (0x100000) MX[B]
[2] -1 0 0xe9000000 - 0xe9000fff (0x1000) MX[B]
[3] -1 0 0xe9800000 - 0xe9801fff (0x2000) MX[B]
[4] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[5] -1 0 0xeb7f0000 - 0xeb7fffff (0x10000) MX[B](B)
[6] -1 0 0xeb800000 - 0xeb87ffff (0x80000) MX[B](B)
[7] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B](B)
[8] -1 0 0xea000000 - 0xeaffffff (0x1000000) MX[B](B)
[9] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
[10] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[11] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[12] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xe8000000 - 0xe80000ff (0x100) MX[B]
[6] -1 0 0xe8800000 - 0xe88fffff (0x100000) MX[B]
[7] -1 0 0xe9000000 - 0xe9000fff (0x1000) MX[B]
[8] -1 0 0xe9800000 - 0xe9801fff (0x2000) MX[B]
[9] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[10] -1 0 0xeb7f0000 - 0xeb7fffff (0x10000) MX[B](B)
[11] -1 0 0xeb800000 - 0xeb87ffff (0x80000) MX[B](B)
[12] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B](B)
[13] -1 0 0xea000000 - 0xeaffffff (0x1000000) MX[B](B)
[14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[15] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[16] -1 0 0x0000b800 - 0x0000b80f (0x10) IX[B]
[17] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[18] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[19] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
(II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI, mgag400,
mgag550
(II) GLINT: driver for 3Dlabs chipsets: gamma, gamma2, ti_pm2, ti_pm, r4,
pm4, pm3, pm2v, pm2, pm, 300sx, 500tx, mx, delta
(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
GeForce4 420 Go 32M, GeForce4 460 Go, GeForce4 440 Go 64M,
GeForce4 410 Go 16M, Quadro4 500 GoGL, Quadro4 550 XGL, Quadro4 NVS,
GeForce4 MX 440 with AGP8X, GeForce4 MX 440SE with AGP8X,
GeForce4 MX 420 with AGP8X, GeForce4 448 Go, GeForce4 488 Go,
Quadro4 580 XGL, Quadro4 280 NVS, Quadro4 380 XGL,
GeForce4 MX Integrated GPU, GeForce3, GeForce3 Ti 200,
GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600, GeForce4 Ti 4400,
0x0252, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
GeForce FX 5600 Ultra, GeForce FX 5600, 0x0313, GeForce FX 5600SE,
0x0316, 0x0317, GeForce FX Go5600, GeForce FX Go5650,
Quadro FX Go700, 0x031D, 0x031E, 0x031F, GeForce FX 5200,
GeForce FX 5200 Ultra, GeForce FX 5200, GeForce FX 5200SE,
GeForce FX Go5200, GeForce FX Go5250, GeForce FX Go5200 32M/64M,
0x0329, Quadro NVS 280 PCI, Quadro FX 500, GeForce FX Go5300,
GeForce FX Go5100, 0x032F, GeForce FX 5900 Ultra, GeForce FX 5900,
GeForce FX 5900XT, GeForce FX 5950 Ultra, 0x0334, Quadro FX 3000,
GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE,
GeForce FX 5700VE, 0x0345, GeForce FX Go5700, GeForce FX Go5700,
0x0349, 0x034B, Quadro FX Go1000, Quadro FX 1100, 0x034F
(II) TGA: driver for Digital chipsets: tga, tga2
(II) S3: driver (version 0.3.5 for S3 chipset: 964-0, 964-1, 968,
Trio32/64, Aurora64V+, Trio64UV+, Trio64V2/DX/GX
(II) S3VIRGE: driver (version 1.8.6) for S3 ViRGE chipsets: virge, 86C325,
virge vx, 86C988, virge dx, virge gx, 86C375, 86C385, virge gx2,
86C357, virge mx, 86C260, virge mx+, 86C280, trio 3d, 86C365,
trio 3d/2x, 86C362, 86C368
(II) SIS: driver for SiS chipsets: SIS5597/5598, SIS530/620,
SIS6326/AGP/DVD, SIS300/305, SIS630/730, SIS540, SIS315, SIS315H,
SIS315PRO, SIS550, SIS650/M650/651/740, SIS330(Xabre),
SIS660/661FX/M661FX/M661MX/741/741GX/M741/760/M760
(II) RENDITION: rendition driver (version 4.0) for chipsets: V1000, V2x00
(II) NEOMAGIC: Driver for Neomagic chipsets: neo2070, neo2090, neo2093,
neo2097, neo2160, neo2200, neo2230, neo2360, neo2380
(II) I740: Driver for Intel i740 chipset: i740 (agp), i740 (pci)
(II) TDFX: Driver for 3dfx Banshee/Voodoo3 chipsets: 3dfx Banshee,
3dfx Voodoo3, 3dfx Voodoo5
(II) SAVAGE: driver (version 1.1.27) for S3 Savage chipsets: Savage4,
Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX,
Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133,
ProSavage PN133, ProSavage KN133, SuperSavage/MX 128,
SuperSavage/MX 64, SuperSavage/MX 64C, SuperSavage/IX 128,
SuperSavage/IX 128, SuperSavage/IX 64, SuperSavage/IX 64,
SuperSavage/IXC 64, SuperSavage/IXC 64, ProSavage DDR,
ProSavage DDR-K
(II) CIRRUS: driver for Cirrus chipsets: CLGD5430, CLGD5434-4, CLGD5434-8,
CLGD5436, CLGD5446, CLGD5480, CL-GD5462, CL-GD5464, CL-GD5464BD,
CL-GD5465, CL-GD7548
(II) VMWARE: driver for VMware SVGA: vmware0405, vmware0710
(II) TSENG: driver for Tseng Labs chipsets: ET4000, ET4000W32, ET4000W32i,
ET4000W32p, ET6000, ET6100,
(II) TRIDENT: driver for Trident chipsets: tvga9000, tvga9000i, tvga8900c,
tvga8900d, tvga9200cxr, tgui9400cxi, cyber9320, cyber9388, cyber9397,
cyber9397dvd, cyber9520, cyber9525dvd, cyberblade/e4, tgui9420dgi,
tgui9440agi, tgui9660, tgui9680, providia9682, providia9685,
cyber9382, cyber9385, 3dimage975, 3dimage985, blade3d, cyberbladei7,
cyberbladei7d, cyberbladei1, cyberbladei1d, cyberbladeAi1,
cyberbladeAi1d, bladeXP, cyberbladeXPAi1, cyberbladeXP4
(II) CHIPS: Driver for Chips and Technologies chipsets: ct65520, ct65525,
ct65530, ct65535, ct65540, ct65545, ct65546, ct65548, ct65550,
ct65554, ct65555, ct68554, ct69000, ct69030, ct64200, ct64300
(II) APM: driver for the Alliance chipsets: AP6422, AT24, AT3D
(II) I128: driver for Number Nine I128 chipsets: i128, i128v2, i128t2r,
i128t2r4
(II) NSC: Nsc family driver (version 2.7.6) for chipsets: 5530, SC1200,
SC1400, REDCLOUD
(II) ATI: ATI driver (version 6.5.6) for chipsets: ati, ativga
(II) R128: Driver for ATI Rage 128 chipsets:
ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP),
ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP),
ATI Rage 128 Pro GL PA (AGP?), ATI Rage 128 Pro GL PB (AGP?),
ATI Rage 128 Pro GL PC (AGP?), ATI Rage 128 Pro GL PD (PCI),
ATI Rage 128 Pro GL PE (AGP?), ATI Rage 128 Pro GL PF (AGP),
ATI Rage 128 Pro VR PG (AGP?), ATI Rage 128 Pro VR PH (AGP?),
ATI Rage 128 Pro VR PI (AGP?), ATI Rage 128 Pro VR PJ (AGP?),
ATI Rage 128 Pro VR PK (AGP?), ATI Rage 128 Pro VR PL (AGP?),
ATI Rage 128 Pro VR PM (AGP?), ATI Rage 128 Pro VR PN (AGP?),
ATI Rage 128 Pro VR PO (AGP?), ATI Rage 128 Pro VR PP (PCI),
ATI Rage 128 Pro VR PQ (AGP?), ATI Rage 128 Pro VR PR (PCI),
ATI Rage 128 Pro VR PS (AGP?), ATI Rage 128 Pro VR PT (AGP?),
ATI Rage 128 Pro VR PU (AGP?), ATI Rage 128 Pro VR PV (AGP?),
ATI Rage 128 Pro VR PW (AGP?), ATI Rage 128 Pro VR PX (AGP?),
ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP),
ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI),
ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (AGP?),
ATI Rage 128 4X SF (AGP?), ATI Rage 128 4X SG (AGP?),
ATI Rage 128 4X SH (AGP?), ATI Rage 128 4X SK (AGP?),
ATI Rage 128 4X SL (AGP?), ATI Rage 128 4X SM (AGP),
ATI Rage 128 4X SN (AGP?), ATI Rage 128 Pro ULTRA TF (AGP),
ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP),
ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?),
ATI Rage 128 Pro ULTRA TU (AGP?)
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ (AGP/PCI),
ATI Radeon Mobility M7 LW (AGP),
ATI Mobility FireGL 7800 M7 LX (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP320M (U1) 4336,
ATI Radeon IGP330/340/350 (A4) 4137,
ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon Mobility 7000 IGP 4437,
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 8500 AIW BB (AGP),
ATI Radeon 8500 AIW BC (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP),
ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835,
ATI Radeon 9200PRO 5960 (AGP), ATI Radeon 9200 5961 (AGP),
ATI Radeon 9200 5962 (AGP), ATI Radeon 9200SE 5964 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP), ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9700 Pro ND (AGP),
ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9700 NF (AGP),
ATI FireGL X1 NG (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP),
ATI FireGL RV360 AV (AGP), ATI Radeon Mobility 9600 (M10) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M10) NT (AGP),
ATI FireGL Mobility T2 (M11) NV (AGP), ATI Radeon 9800SE AH (AGP),
ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
ATI FireGL X2 AK (AGP), ATI Radeon 9800PRO NH (AGP),
ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP),
ATI Radeon 9800XT NJ (AGP)
(II) I810: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100,
i810e, i815, i830M, 845G, 852GM/855GM, 865G
(II) ARK: driver (version 0.5.0 for ARK Logic chipset: ark1000pv,
ark2000pv, ark2000mt
(II) CYRIX: driver for Cyrix MediaGX Processors: mediagx
(II) Silicon Motion: driver (version 1.3.1) for Silicon Motion Lynx chipsets:
Lynx, LynxE, Lynx3D, LynxEM, LynxEM+, Lynx3DM, Cougar3DR
(II) via: driver for VIA chipsets: CLE266, KM400, K8M800
(II) VESA: driver for VESA chipsets: vesa
(II) VGA: Generic VGA driver (version 4.0) for chipsets: generic
(II) DUMMY: Driver for Dummy chipsets: dummy
(II) FBDEV: driver for framebuffer: fbdev, afb
(II) v4l driver for Video4Linux
(II) I810: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100,
i810e, i815, i830M, 845G, 852GM/855GM, 865G
(II) Primary Device is: PCI 01:00:0
(EE) No devices detected.

Fatal server error:
no screens found

Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.


_________________________________

And my xorg.conf file:

cat /etc/X11/xorg.conf
# File generated by xf86config.


Section "Module"

Load "dbe" # Double buffer extension
Load "extmod" # For VMware
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
Load "speedo"
# Load "freetype"
# Load "xtt"
Load "glx"
# Load "dri"
Load "GLcore"
EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)

FontPath "/usr/share/fonts/local/"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/TrueType/"
FontPath "/usr/share/fonts/freefont/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
EndSection

Section "ServerFlags"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection

Section "InputDevice"

Identifier "Keyboard1"
Driver "Keyboard"
Option "AutoRepeat" "500 30"
# Option "XkbOptions" "ctrl:swapcaps" #example: swaps key positions

Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "Buttons" "5"
Option "ZAxisMapping" " 4 5"
Option "Resolution" "1200" #mouse-speed setting for ps/2 mousr
EndSection

Section "Monitor"

Identifier "NEC FE750+"
HorizSync 31.5-96
VertRefresh 55-160
vendorname "[NEC]"
modelname "[FE750+]"
Option "DPMS"
ModeLine "1280x1024/75Hz" 65 1024 1032 1176 1344 768 771 777 806 -HSync -VSync
ModeLine "1280x1024/85Hz" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +HSync +VSync
ModeLine "1280x1024/76Hz" 135 1280 1312 1416 1664 1024 1027 1030 1064
ModeLine "1280x1024/70Hz" 126.5 1280 1312 1472 1696 1024 1032 1040 1068 -HSync -VSync
ModeLine "1280x1024/61Hz" 110 1280 1328 1512 1712 1024 1025 1028 1054
EndSection

Section "Device"
Identifier "Ti450"
Driver "nv" **Using "nv" while troubleshooting "nvidia"**
VideoRam 65536
Option "NoLogo" "1"
# BusID "PCI:01:00:0"
vendorname "Gainward"
boardname "Ti450"
Option "DPMS"
Option "NvAGP" "3" **changed to "1" when I removed nvagp from kernel**
EndSection

Section "Screen"
Identifier "Screen 0"
Device "Ti450"
Monitor "NEC FE750+"
DefaultDepth 24

# Subsection "Display"
# Depth 8
# Modes "1280x1024/85Hz"
# ViewPort 0 0
# Virtual 0 0
# EndSubsection
# Subsection "Display"
# Depth 16
# Modes "1280x1024/85Hz"
# ViewPort 0 0
# Virtual 0 0
# EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024/85Hz"
ViewPort 0 0
Virtual 0 0
EndSubsection
EndSection

Section "ServerLayout"

Identifier "Simple Layout"
Screen "Screen 0"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection


Not sure if this has anything to do with it but just recently I've been seeing this in my dmesg:

PCI: Found IRQ 3 for device 0000:00:10.0
IRQ routing conflict for 0000:00:10.0, have irq 7, want irq 3
IRQ routing conflict for 0000:00:10.1, have irq 7, want irq 3
IRQ routing conflict for 0000:00:10.2, have irq 7, want irq 3
IRQ routing conflict for 0000:00:10.3, have irq 7, want irq 3
uhci_hcd 0000:00:10.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
uhci_hcd 0000:00:10.0: irq 7, io base 0000d800
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Found IRQ 3 for device 0000:00:10.1
IRQ routing conflict for 0000:00:10.0, have irq 7, want irq 3
IRQ routing conflict for 0000:00:10.1, have irq 7, want irq 3
IRQ routing conflict for 0000:00:10.2, have irq 7, want irq 3
IRQ routing conflict for 0000:00:10.3, have irq 7, want irq 3
uhci_hcd 0000:00:10.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2)
uhci_hcd 0000:00:10.1: irq 7, io base 0000d400
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PCI: Found IRQ 3 for device 0000:00:10.2
IRQ routing conflict for 0000:00:10.0, have irq 7, want irq 3
IRQ routing conflict for 0000:00:10.1, have irq 7, want irq 3
IRQ routing conflict for 0000:00:10.2, have irq 7, want irq 3
IRQ routing conflict for 0000:00:10.3, have irq 7, want irq 3
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 46279
Location: 56N 3W

PostPosted: Fri Aug 06, 2004 8:44 pm    Post subject: Reply with quote

ck42,

I'm confused. The log lists every graphics driver known to man, then can't find your chipset.

The interrupt problem you report at the botom of your post is the USB being unhappy with irq 7. Thats not directly the problem but its interesting.

What does /proc/interrups show?
Has your graphics card got an interrup?
Is it allowed one in the BIOS settings?

If your kernel is not compiled to allow PCI interrupt sharing you may meed to fix that to get enough interrups to go round, or turn off the serial and/or parallel posts to free up some unsued ones (if they are unused).
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Fri Aug 06, 2004 8:52 pm    Post subject: Reply with quote

cat /proc/interrupts
CPU0
0: 5975437 XT-PIC timer
1: 3819 XT-PIC i8042
2: 0 XT-PIC cascade
3: 0 XT-PIC CS46XX
7: 60 XT-PIC uhci_hcd, uhci_hcd, uhci_hcd
8: 2 XT-PIC rtc
10: 7629 XT-PIC eth0
12: 48942 XT-PIC i8042
14: 20421 XT-PIC ide0
15: 25 XT-PIC ide1
NMI: 0
ERR: 0

Not sure which one of those, if there is one, is the videocard.
I've just gone through the BIOS again earlier. By default, I diable any uneeded hardware, ie, seral/parallel, IDE controllers, etc.

Happen to remember WHERE in the kernel setup the setting for PCI sharing is?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 46279
Location: 56N 3W

PostPosted: Fri Aug 06, 2004 9:00 pm    Post subject: Reply with quote

ck42,

IRQ sharing is on. Your IRQ 7 is shared by three USB controllers.
However your, video card is not listed.
you have interrupts 4,5,6,9 and 11 spare, so you are not short.

I suspect the Video Card Interrupt is turned off in the BIOS. the nVidia driver needs one, some other drivers don't.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Fri Aug 06, 2004 11:51 pm    Post subject: Reply with quote

Not sure how the video card doesn't have an IRQ. Even if the system is using the "nv" driver, the videocard needs an IRQ....regardless in order to even operate.

Just to be sure, I'll try and dig out the m/b manual to see if the only other card (PCI) is sitting in the AGP/PCI irq shared slot. If so, then maybe the PCI sound card is causing issues with the AGP videocard.
Back to top
View user's profile Send private message
mike4148
l33t
l33t


Joined: 09 Sep 2003
Posts: 641

PostPosted: Sat Aug 07, 2004 2:04 am    Post subject: Reply with quote

It looks like the nvidia kernel module itself isn't working with the card. My /proc/interrupts lists the nvidia driver as claiming an IRQ for itself. Plus, I've seen /sbin/lspci output from someone with this problem that showed the card claiming the IRQ, while the nvidia driver wasn't.

One thing I find strange is that the nvidia X driver isn't giving any output at all. If the kernel module weren't working (or if it couldn't find the card), I would expect it to load and complain. Is the driver module (/usr/X11R6/lib/modules/drivers/nvidia_drv.o) there? Does it appear (via mtimes) to be from your currently installed nvidia-glx?

I'd be interested to know whether other people with this problem are running ~x86 and/or using exotic kernel sources. Switching to a really stable config (minus the nvidia drivers, which work better ~x86 than x86) might make a difference, but it would be far, far too much effort for no guaranteed positive outcome.

Does /var/log/emerge.log show anything relevant at about the time the driver stopped working?
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Sat Aug 07, 2004 2:25 am    Post subject: Reply with quote

Here's some of the output:


/var/log
[22:07] [root] lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
0000:00:09.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
0000:00:0b.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
0000:00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80)
0000:00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80)
0000:00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80)
0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti 200] (rev a3)

/var/log
[22:07] [root] la /usr/X11R6/lib/modules/drivers/
total 645K
drwxr-xr-x 2 root root 80 Aug 6 15:12 .
drwxr-xr-x 5 root root 192 Jul 17 22:08 ..
-rwxr-xr-x 1 root root 644K Aug 6 15:12 nvidia_drv.o

So yes, it appears that the videocard is listed and the nvidia driver exist.

BUT,

/proc/driver/nvidia/agp
[22:16] [root] cat status
Status: Disabled

Yet.....

/proc/driver/nvidia/agp
[22:16] [root] cat card
Fast Writes: Not Supported
SBA: Supported
AGP Rates: 4x 2x 1x
Registers: 0x1f000207:0x00000000


..........and, for the IRQ question:

/proc/driver/nvidia/cards
[22:17] [root] cat 0
Model: GeForce3 Ti 200
IRQ: 11
Video BIOS: ??.??.??.??.??
Card Type: AGP


and if it matters,

/proc
[22:18] [root] cat devices
Character devices:
1 mem
2 pty
3 ttyp
4 /dev/vc/0
4 tty
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input
14 sound
21 sg
29 fb
67 coda_psdev
116 alsa
128 ptm
136 pts
180 usb
195 nvidia
254 devfs


So, I'm still looking at a system that apparently SEES the card but doesn't want to run the nvidia drivers with it.....like it had in the past.

and Mike4148, I am running ~x86 all the way. Have been almost from the start. As for the emerge.log, it's full of nvidia stuff. But, I can't even pin down WHEN this problem occured. When it happened, the system was rebooted after having been running for prolly a month....and having a month's full of changes mixed in with it. There's no way I could find the one thing that caused the problem....wish I could.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 46279
Location: 56N 3W

PostPosted: Sat Aug 07, 2004 10:54 am    Post subject: Reply with quote

ck42,

Heres a long shot for you but its easy to test.
In some kernels (2.6.7 for sure) ehci-hcd (the usb 2.0 driver) is broken. It shuts down the interrupt its allocated, which takes down anything else (like nvidia) that may be sharing the irq.

Look through dmesg to see if ehci is being allocated irq 11, which is where nvidia seems to be and read the surrounding context for a line that includes 'nobody cared'.

The fix is to remove ehci_hcd, or at least, stop it loading.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Sat Aug 07, 2004 2:29 pm    Post subject: Reply with quote

Quote:

Forgot to mention that I've also recently pulled the USB2.0 drivers from the kernel. There's been some rumours on the forum that these are causing some X conflicts. Didn't make any difference in my case though.


Also:

In /proc/interrupts:

7: 60 XT-PIC uhci_hcd, uhci_hcd, uhci_hcd

I'm guessing that the ehci_hcd device would've be listed on this line too, right?


Any possiblilty that framebuffer may be causing some issues?
Back to top
View user's profile Send private message
newboydan
n00b
n00b


Joined: 02 Jan 2003
Posts: 16

PostPosted: Sat Aug 07, 2004 5:00 pm    Post subject: Reply with quote

This is possibly unrelated, but wortha look.

I have the same problem upgrading from 2.4 (to 2.6.7). However, at the same time, I'd also changed my CFLAGS from default to -march=athlon-xp, which , among other things, let ncurses be compiled but broken. Changing back to defaults fixed that. Recompiling nvidia-kernel now actually creates nvidia.ko (which it didn't with the optimisation - despite it not giving any errors).

Now nvidia won't insert properly, but thats another matter.

Basically, I'd advise you to check your CFLAGS, and try recompiling nvidia-kernel with no optimisation. (I'm now going to try using a 386 processor setting in my kernel, rather than Duron. I've never had any luck with them in any kernel...)
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 46279
Location: 56N 3W

PostPosted: Sat Aug 07, 2004 5:27 pm    Post subject: Reply with quote

ck42,

Thats not how interrupt allocation works. First, there are two methods, one in the BIOS and one in the kernel. You can tell the kernel to use whatever the BIOS has done, or it can do it itself.

I'm willing to bet they come up with different allocations. The reasons for having two mothods are historical. Some BIOSes were (still are?) broken and linux was unable to pick up its settings.

The BIOS only does the allocation once. There is a one time setting, which you can set to enable, usually on the PCI page. At the next boot, the BIOS does the allocation and sets the option back to disable. If you are using the BIOS method, when you add or relocate hardare on the PCI or AGP you need to re-enable this BIOS setting for IRQs, I/O Ports etc to get reallocated.

I must have missed your taking USB 2.0 out.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ck42
l33t
l33t


Joined: 31 Jul 2003
Posts: 789

PostPosted: Sat Aug 07, 2004 5:49 pm    Post subject: Reply with quote

I think I know what you're referring to...forget what the BIOS calls it, but I've used it before. I'll give that a try.


EDIT:

No luck :(
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2, 3, 4  Next
Page 1 of 4

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum