|
|
#49 | |
|
Registered User
Join Date: Mar 2007
Posts: 19
|
Quote:
Were you able to remote login? Can you post the bug report? Thanks |
|
|
|
|
|
#50 | |
|
Registered User
Join Date: Mar 2006
Posts: 26
|
Quote:
I found this info in yor kernel log:- i2c /dev entries driver via686a 0000:00:04.4: base address not set - upgrade BIOS or use force_addr=0xaddr Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC). Now I picked that, becuase I was finding this error log with my system using Linux-2.6.20.1:- dragon23dragon kernel: i2c /dev entries driver dragon23dragon kernel: gameport: EMU10K1 is pci0000:02:07.1/gameport0, io 0xde00, speed 1193kHz dragon23dragon kernel: Advanced Linux Sound Architecture Driver Version 1.0.14rc1 (Tue Jan 09 09:56:17 2007 UTC). ----/cut edit /---- dragon23dragon kernel: **WARNING** I2C adapter driver [NVIDIA i2c adapter 0 at 1:00.0] forgot to specify physical device; fix it! dragon23dragon kernel: **WARNING** I2C adapter driver [NVIDIA i2c adapter 1 at 1:00.0] forgot to specify physical device; fix it! dragon23dragon kernel: **WARNING** I2C adapter driver [NVIDIA i2c adapter 2 at 1:00.0] forgot to specify physical device; fix it! dragon23dragon kernel: **WARNING** I2C adapter driver [NVIDIA i2c adapter 3 at 1:00.0] forgot to specify physical device; fix it! And for the first time was having Xid problems. Using Linux-2.6.21-rc2, I now have this:- dragon23dragon kernel: I2O subsystem v1.325 dragon23dragon kernel: i2o: max drivers = 8 dragon23dragon kernel: i2c_adapter i2c-0: nForce2 SMBus adapter at 0x1c00 dragon23dragon kernel: i2c_adapter i2c-1: nForce2 SMBus adapter at 0x1c80 dragon23dragon kernel: gameport: EMU10K1 is pci0000:04:07.1/gameport0, io 0xde00, speed 573kHz dragon23dragon kernel: Advanced Linux Sound Architecture Driver Version 1.0.14rc2 (Wed Feb 14 07:42:13 2007 UTC). Nice and clean looking eh? And I don't have any Xid issues any more. My system hardware: CPU: Intel Core2 Duo E6600 Motherboard: Asus P5N32-E SLI Plus Video Card: GeForce-8800-GTX (Inno3D) EDIT: PS: Please don't jump the gun by installing Linux-2.6.21-rc3. I found to have a kernel Oops: 0002 [#1] when pluging in a USB device: pl2303 2-2:1.0: pl2303 converter (USB to serial converter) BUG: unable to handle kernel paging request at virtual address 575f3051 I have found (with my setup) Linux-2.6.21-rc2 to be stable for me. |
|
|
|
|
|
#51 |
|
Registered User
Join Date: Mar 2007
Posts: 19
|
Well that is an interesting finding.
Apart form the other issues with the ALSA (bad sound quality from my 1024live ) it apparently may have some other issues over there.I'm not saying that the locks are related with i2c access. But they might. Actually I just had another lock a few minutes ago. I was just going to post it when I saw that post. This time it wasn't a lock. It was an automatic reboot. Right before the reboot I was just going to slip my mouse pointer on to of a flash thingy on some web page (may have no relation whatsoever )After the reboot when it was suppose to show the nvidia logo I just got a flashing screen. (not the first time this happens) I pressed the reset, and again at the supposed nvida logo screen I just got a black screen... I turned off and on this time. Got a normal reboot and nvidia logo (which I like to see) and when I checked the logs I found that I got a Xid 3 right after the first (and automatic) reboot. What does that mean... That I would like to know... Anyway I'll try to look into that I2C bust thing. Thank for pointing that out. Apparently there are a few of us in the same boat. And were just trying to plug the holes so that this thing wont sink... |
|
|
|
|
#52 | |
|
NVIDIA Corporation
Join Date: Dec 2004
Posts: 8,763
|
The i2c warnings are a (harmless) bug that should be fixed in the 1.0-9755 driver.
|
|
|
|
|
|
#53 | |
|
Registered User
Join Date: Mar 2006
Posts: 26
|
Quote:
EDIT: Please note:- I had solved the Xid and (may be in relation to) the Motherboard I2C error issues by upgrading the Linux kernel, not the Nvidia video kernel driver. But I must say, the temperature information (or any reading?) of the video card must of been incorrect if the I2C was not working in the video Driver itself. Yes? |
|
|
|
|
|
#54 | |
|
Registered User
Join Date: Jan 2007
Posts: 18
|
Sorry the delay , i was traveling.
Attached is a bug report from the system locked , got using ssh... I hope this help all of us. |
|
|
|
|
|
#55 |
|
Registered User
Join Date: Dec 2002
Location: Clausthal/Germany
Posts: 1,104
|
does the Xids happen after a clean boot too?
|
|
|
|
|
#56 |
|
Registered User
Join Date: Jan 2007
Posts: 18
|
yes.
|
|
|
|
|
#57 |
|
Registered User
Join Date: Mar 2007
Posts: 19
|
Hello guys,
I just had another lock (sniff) Up to now I was unable to get any other pc or device to retrieve a debug report remotely. Until then I'll be trying some other stuff. As for now I'm trying to figure out if my card is overheating. My card is a Asus GeForce v6800 deluxe Does anyone knows the normal operating temperature and fan speed? Normal as in withing safe or stable limits. The linux util nvclock reports: " -- General info -- Card: nVidia Geforce 256 DDR Architecture: NV10 A3 PCI id: 0x101 GPU clock: 120.050 MHz Bustype: AGP -- Memory info -- Amount: 32 MB Type: 128 bit DDR Clock: 300.678 MHz -- AGP info -- Status: Enabled Rate: 4X AGP rates: 1X 2X 4X Fast Writes: Disabled SBA: Disabled -- Sensor info -- Sensor: Winbond W83781D Board temperature: 59C GPU temperature: 59C Fanspeed: 8544 RPM PWM duty cycle: nan% -- VideoBios information -- Version: 02.10.02.10 Signon message: ASUS AGP-V6800 DDR SGRAM BIOS Version 2.10.02.10.01 sba " Isn't 59C a bit high? Thats the temperature measured while idle. After a few minutes processing a small opengl application I got: -- Sensor info -- Sensor: Winbond W83781D Board temperature: 64C GPU temperature: 64C Fanspeed: 8544 RPM PWM duty cycle: nan% Don't know if it could get any higher. Any help (Nvidia guys?) Should I decrease my GPU/RAM speed (120/300MHz) Thanks |
|
|
|
|
#58 |
|
Registered User
Join Date: Jan 2007
Posts: 18
|
running 2.6.21-rc3 for one day and no problems at all
![]() |
|
|
|
|
#59 |
|
Registered User
Join Date: Jan 2007
Posts: 18
|
Well , it was too good to be true. XID problems are back in 2.6.21-rc3
![]() |
|
|
|
|
#60 |
|
Registered User
Join Date: Mar 2005
Posts: 6
|
they are never going to provide an answer, forget it
it''s been YEARS since this problem exists , and they havent fixed it yet, nor given back any info when you do what they ask you o do (update X,Y , provide proper bug report, try with latest kernel, blablabla) , it seems they answer only when you do something not correct/without enough info, in other cases (ie providing what they asked) they ignore you pathetic behaviour |
|
|
![]() |
| Thread Tools | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| NVRM: Xid while using chromium browser | blekot | NVIDIA Linux | 2 | 06-26-12 01:29 PM |
| xorg locks-up with newest nvidia drivers w/ vdpau. | theroot | NVIDIA Linux | 1 | 06-24-12 11:04 AM |
| Screen freeze NVRM: Xid error | ciancaroll | NVIDIA Linux | 0 | 06-05-12 01:05 PM |
| Xorg hang with 100% cpu, any driver version, GTX275 | bones_was_here | NVIDIA Linux | 20 | 05-23-12 09:49 AM |
| GTX 460M, Xorg 1.12, nvidia driver 295.49, linux 3.3.5-1-ARCH and NVRM Xid 44 | elsifaka | NVIDIA Linux | 0 | 05-14-12 08:48 AM |