| View previous topic :: View next topic |
| Author |
Message |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54309
Location: 56N 3W
|
 Posted: Sun Aug 29, 2004 4:22 pm Post subject: |
 |
|
waldosr,
Not every BIOS has the option.
It will likely be on the PCI page where you can choose which card to use at boot and its called something like Assign VGA IRQ
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
 |
waldosr
n00b
Joined: 24 Sep 2003
Posts: 65
|
| Posted: Sun Aug 29, 2004 4:35 pm Post subject: |
|
|
| while booting i noticed that the display controller is on irq 11. does that help me at all? |
|
| Back to top |
|
|
waldosr
n00b
Joined: 24 Sep 2003
Posts: 65
|
| Posted: Sun Aug 29, 2004 4:36 pm Post subject: |
|
|
| there is nothing to assign an irq |
|
| Back to top |
|
|
pem
Guru
Joined: 29 Aug 2004
Posts: 390
Location: France
|
| Posted: Sun Aug 29, 2004 4:49 pm Post subject: |
|
|
At boot, the video bios display some info (quite fast) and the come your BIOS. The IRQ resolution should be performed here.
As your 'cat /proc/interrupts' displays it, there is no assigned IRQ for your card, neither by the BIOS nor by Linux. That's odd! 
Try to check wether your mobo has a plugnplay activation/deactivation switch. Set it on, if not. |
|
| Back to top |
|
|
pem
Guru
Joined: 29 Aug 2004
Posts: 390
Location: France
|
| Posted: Sun Aug 29, 2004 4:58 pm Post subject: |
|
|
 By the way, nVidia provides a real good /proc interface gathering all info we need.
Normally, when the driver is loaded, you be granted with that kind of results:
| Code: |
cat /proc/driver/nvidia/cards/0
Model: GeForce4 Ti 4200
IRQ: 16
Video BIOS: 04.25.00.30.00
Card Type: AGP
|
I guess that if your driver is loaded (we've seen it after your lsmod) and you still don't have any IRQs assigned to your GPU, we are into a dead point. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54309
Location: 56N 3W
|
| Posted: Sun Aug 29, 2004 5:26 pm Post subject: |
|
|
waldosr,
Are you using one of the 2.6.7 kernels with the broken USB 2.0 driver?
do If you get nobody cared we are on to something.
What happens is the nvidia card and broken USB 2.0 share an interrupt. The USB bug disables the interrupt, so that nothing on that IRQ works.
The short term fix is to disable USB 2.0 by deleting the kernel module. The long term fix is to move to 2.6.8
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
synapscape
Apprentice
Joined: 07 Apr 2003
Posts: 234
Location: Germany
|
| Posted: Tue Aug 31, 2004 9:24 am Post subject: |
|
|
Hi waldosr!
Somewhere above you did a
and it showed that your kernel is compiled with SMP support. Unless you do have 2 cpu's in your system this option is not needed. I am guessing here, but maybe something concerning SMP (used for dual-cpu systems) is screwing up your systems IRQs. The solution would be to recompile your kernel without SMP support.
Good Luck
EDIT: Ah, and please check your /dev directory if it contains /dev/nvidia0 and /dev/nvidiactl . There were posts in these forums indicating that these nodes weren't created quickly enough so X bails out. See here:
https://forums.gentoo.org/viewtopic.php?p=1482652#1482652
_________________
mad season forever |
|
| Back to top |
|
|
waldosr
n00b
Joined: 24 Sep 2003
Posts: 65
|
| Posted: Tue Aug 31, 2004 9:00 pm Post subject: |
|
|
I just put on the gentoo-dev-sources
Here is something funny!
| Code: |
bash-2.05b# cat /proc/driver/nvidia/cards/0
Model: GeForce FX 5200
IRQ: 16
Video BIOS: ??.??.??.??.??
Card Type: AGP
bash-2.05b#
|
dmesg | grep obody comes up empty |
|
| Back to top |
|
|
pem
Guru
Joined: 29 Aug 2004
Posts: 390
Location: France
|
| Posted: Tue Aug 31, 2004 9:03 pm Post subject: |
|
|
| I guess synapscape was right. It was the SMP stuff which trick the interrupts. |
|
| Back to top |
|
|
waldosr
n00b
Joined: 24 Sep 2003
Posts: 65
|
| Posted: Tue Aug 31, 2004 9:08 pm Post subject: |
|
|
| I just looked and I still had the SMP in the new kernel. I am going to recompile the kernel without it. |
|
| Back to top |
|
|
waldosr
n00b
Joined: 24 Sep 2003
Posts: 65
|
| Posted: Tue Aug 31, 2004 9:45 pm Post subject: |
|
|
Ok, this is weird. 'cat /proc/driver/nvidia/cards/0' shows that the card has a IRQ of 16 while 'cat /proc/interrupts' shows nothing on 16. And why is it saying video bios is questionmarks? Any new ideas?
| Code: |
bash-2.05b# cat /proc/driver/nvidia/cards/0
Model: GeForce FX 5200
IRQ: 16
Video BIOS: ??.??.??.??.??
Card Type: AGP
bash-2.05b# dmesg | grep obody
bash-2.05b# cat /proc/interrupts
CPU0
0: 3332480 IO-APIC-edge timer
1: 2891 IO-APIC-edge i8042
2: 0 XT-PIC cascade
12: 199099 IO-APIC-edge i8042
14: 78658 IO-APIC-edge ide0
15: 28 IO-APIC-edge ide1
22: 0 IO-APIC-level VIA8233
23: 36483 IO-APIC-level eth0
NMI: 0
LOC: 3337831
ERR: 0
MIS: 0
bash-2.05b#
|
|
|
| Back to top |
|
|
waldosr
n00b
Joined: 24 Sep 2003
Posts: 65
|
| Posted: Tue Aug 31, 2004 11:01 pm Post subject: |
|
|
| synapscape wrote: |
EDIT: Ah, and please check your /dev directory if it contains /dev/nvidia0 and /dev/nvidiactl . There were posts in these forums indicating that these nodes weren't created quickly enough so X bails out. See here:
https://forums.gentoo.org/viewtopic.php?p=1482652#1482652 |
I did the mknod commands that were listed at that url and now i get this:
| Code: |
tux root # cat /proc/driver/nvidia/cards/0
cat: /proc/driver/nvidia/cards/0: No such file or directory
tux root # dmesg | grep obody
tux root # modprobe nvidia
FATAL: Error inserting nvidia (/lib/modules/2.6.8-gentoo-r3/video/nvidia.ko): Invalid module format
tux root #
|
Help me please. This seems to really screwed things up. And I do have those two devices listed under my /dev directory. |
|
| Back to top |
|
|
bennettp
Guru
Joined: 22 Feb 2004
Posts: 335
Location: on my back and tumbling
|
| Posted: Wed Sep 01, 2004 2:08 am Post subject: |
|
|
waldosr: it sounds to me like you are using version 4996 (or 4966, I can never remember) of the nvidia drivers. This still uses the 2.4 kernel module format, which no longer works since the 2.6.5 kernel.
The solution is to upgrade either to version 5336 of the nvidia drivers (which never worked for me), or to the 6111 drivers (which I've never had a problem with).
The quick answer:
| Code: | | ACCEPT_KEYWORDS=~x86 emerge nvidia-glx nvidia-kernel |
Then make sure the old nvidia driver isn't loaded (with lsmod). If it is, try "modprobe -r nvidia".
Then load the new nvidia module with "modprobe nvidia", fire up X, and with a little luck, all will be fine!
Don't forget: you MUST be running the same version of nvidia-kernel as nvidia-glx!
Edit: If this all works fine, you can always use the latest versions of nvidia drivers by modifying /etc/portage/package.keywords (create it if it doesn't exist), and adding the following lines:
| Code: | media-video/nvidia-kernel ~x86
media-video/nvidia-glx ~x86 |
This will force portage to use the most recent versions of the nvidia drivers.
_________________
Registered Linux User #363420 |
|
| Back to top |
|
|
waldosr
n00b
Joined: 24 Sep 2003
Posts: 65
|
| Posted: Wed Sep 01, 2004 9:51 pm Post subject: |
|
|
| Thank you SOOOOOOOOOO VERY much. It is finally working after four days of work. |
|
| Back to top |
|
|
mlmartin
n00b
Joined: 29 Aug 2004
Posts: 31
|
| Posted: Wed Sep 01, 2004 10:14 pm Post subject: |
|
|
| bennettp wrote: | waldosr: it sounds to me like you are using version 4996 (or 4966, I can never remember) of the nvidia drivers. This still uses the 2.4 kernel module format, which no longer works since the 2.6.5 kernel.
The solution is to upgrade either to version 5336 of the nvidia drivers (which never worked for me), or to the 6111 drivers (which I've never had a problem with).
The quick answer:
| Code: | | ACCEPT_KEYWORDS=~x86 emerge nvidia-glx nvidia-kernel |
Then make sure the old nvidia driver isn't loaded (with lsmod). If it is, try "modprobe -r nvidia".
Then load the new nvidia module with "modprobe nvidia", fire up X, and with a little luck, all will be fine!
Don't forget: you MUST be running the same version of nvidia-kernel as nvidia-glx!
Edit: If this all works fine, you can always use the latest versions of nvidia drivers by modifying /etc/portage/package.keywords (create it if it doesn't exist), and adding the following lines:
| Code: | media-video/nvidia-kernel ~x86
media-video/nvidia-glx ~x86 |
This will force portage to use the most recent versions of the nvidia drivers. |
I got the same problem but none of this is working for me. |
|
| Back to top |
|
|
cybermatthieu
Tux's lil' helper
Joined: 07 Jul 2004
Posts: 77
|
| Posted: Sun Sep 12, 2004 7:08 am Post subject: |
|
|
Same here...
This driver is driving me crazy! 
I still get "Failed to initialize the NVIDIA graphics device!" when I startx |
|
| Back to top |
|
|
Raistlin
l33t
Joined: 17 May 2004
Posts: 691
Location: Boston, MA
|
| Posted: Sun Sep 12, 2004 8:18 am Post subject: |
|
|
i had the same error... the fix was to add manually (!!) the devices /dev/nvidia* and /dev/nvidiactl...
cheers, raist.
_________________
Zwei Was Eins Initially
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." |
|
| Back to top |
|
|
cybermatthieu
Tux's lil' helper
Joined: 07 Jul 2004
Posts: 77
|
| Posted: Sun Sep 12, 2004 7:24 pm Post subject: |
|
|
But the devices /dev/nvidia* and /dev/nvidiactl are there when I start the module (modprobe nvidia)
??? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54309
Location: 56N 3W
|
| Posted: Sun Sep 12, 2004 8:09 pm Post subject: |
|
|
cybermatthieu,
Which kerenl are you using (uname -a) will check?
Does /usr/src/linux point to it (ls -l /usr/src/linux
Which version of nvdia-kernel are you trying to use?
emerge nvdia-kernel -p
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
cybermatthieu
Tux's lil' helper
Joined: 07 Jul 2004
Posts: 77
|
| Posted: Sun Sep 12, 2004 9:35 pm Post subject: |
|
|
Here's my uname -a output:
Linux WarFreak 2.6.8-gentoo-r3 #11 Sun Sep 12 03:54:39 EDT 2004 i686 AMD Athlon(tm) Processor AuthenticAMD GNU/Linux
the command ls -l /usr/src/linux output is:
lrwxr-xr-x 1 root root 21 Sep 4 04:09 /usr/src/linux -> linux-2.6.8-gentoo-r3
I tried:
nvidia-kernel-1.0.6111 and nvidia-glx-1.0.6111 (gave me the "Failed to initialize the NVIDIA graphics device!")
nvidia-kernel-1.0.6106-r1 and nvidia-glx-1.0.6106-r3 (gave me a black screen, crashing my computer)
nvidia-kernel-1.0.5336-r4 and nvidia-glx-1.0.5336-r2 (gave me a black screen, crashing my computer)
nvidia-kernel-1.0.5328-r1 and nvidia-glx-1.0.5328-r2 (gave me a black screen, crashing my computer)
But right now I'm tring to get the 6111 version to work since it's not crashing my computer...
Thanks for your help...
I posted my problem to an other post :
https://forums.gentoo.org/viewtopic.php?p=1532261
Last edited by cybermatthieu on Sun Sep 12, 2004 9:57 pm; edited 2 times in total |
|
| Back to top |
|
|
malloc
l33t
Joined: 19 Sep 2003
Posts: 762
|
| Posted: Sun Sep 12, 2004 9:44 pm Post subject: |
|
|
| cybermatthieu wrote: | Same here...
This driver is driving me crazy!
I still get "Failed to initialize the NVIDIA graphics device!" when I startx |
Check the permissions on /dev to see if you have permission to access the devices. If you're using udev that's probably the problem.
_________________
--> Linux ### 2.6.11-ck2 #1 Sat Mar 12 20:21:30 WET 2005 i686 GNU/Linux <-- |
|
| Back to top |
|
|
cybermatthieu
Tux's lil' helper
Joined: 07 Jul 2004
Posts: 77
|
| Posted: Sun Sep 12, 2004 9:49 pm Post subject: |
|
|
here what ls -l | grep nvidia gave me:
crw-r--r-- 1 root root 195, 0 Dec 31 1969 nvidia0
crw-r--r-- 1 root root 195, 255 Dec 31 1969 nvidiactl |
|
| Back to top |
|
|
malloc
l33t
Joined: 19 Sep 2003
Posts: 762
|
| Posted: Sun Sep 12, 2004 9:52 pm Post subject: |
|
|
| cybermatthieu wrote: | here what ls -l | grep nvidia gave me:
crw-r--r-- 1 root root 195, 0 Dec 31 1969 nvidia0
crw-r--r-- 1 root root 195, 255 Dec 31 1969 nvidiactl |
Ah there might reside the problem...here's what mine gives...
| Code: |
~@ ls /dev/nvidia*
crw-rw---- 1 root video 195, 0 Set 12 16:47 /dev/nvidia0
crw-rw---- 1 root video 195, 255 Set 12 16:47 /dev/nvidiactl
|
Of course your user must belong to the video group
_________________
--> Linux ### 2.6.11-ck2 #1 Sat Mar 12 20:21:30 WET 2005 i686 GNU/Linux <-- |
|
| Back to top |
|
|
cybermatthieu
Tux's lil' helper
Joined: 07 Jul 2004
Posts: 77
|
| Posted: Sun Sep 12, 2004 9:59 pm Post subject: |
|
|
| Quote: | | Ok so how could I make those to be writable for the users? |
Dumb question... 
I changed the rights to the /dev/nvidia0... To be able to read from a user...
It didn't do a thing... |
|
| Back to top |
|
|
malloc
l33t
Joined: 19 Sep 2003
Posts: 762
|
| Posted: Wed Sep 15, 2004 12:03 pm Post subject: |
|
|
| cybermatthieu wrote: | | Quote: | | Ok so how could I make those to be writable for the users? |
Dumb question...
I changed the rights to the /dev/nvidia0... To be able to read from a user...
It didn't do a thing... |
You must make it available for reading and writing to the group video (or whatever name you want to name group)
_________________
--> Linux ### 2.6.11-ck2 #1 Sat Mar 12 20:21:30 WET 2005 i686 GNU/Linux <-- |
|
| Back to top |
|
|
|
Desktop Environments
