Ticket #1618 (closed task)
Opened 7 years ago
problem with output from nivdia card (Examined/Solved - lm_sensors 2.8.4 linux 2.6.3-gentoo-r1)
| Reported by: | contact | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | kernel | Version: | |
| Keywords: | Cc: |
Description
I know, that rivatv is not your buisness, but maybe you know the solution.
I have Asus P4B533 board and GF 256DDR (hw Quadro mod). On kernel 2.4 everything
was all right. But when I installed 2.6 i get no output from GF card. Rivatv
version is 0.8.3. Here is lsmod:
bash-2.05b# lsmod
Module Size Used by
rivatv 70296 0
rtc 10680 0
saa7108e 11776 0
videodev 7936 1 rivatv
eeprom 6408 0
w83781d 31232 0
i2c_sensor 2560 2 eeprom,w83781d
i2c_dev 8576 0
i2c_algo_bit 9096 1 rivatv
i2c_i801 7056 0
i2c_core 18948 8 rivatv,saa7108e,eeprom,w83781d,i2c_sensor,
i2c_dev,i2c_algo_bit,i2c_i801
snd_cmipci 31764 0
snd_opl3_lib 9600 1 snd_cmipci
snd_hwdep 7712 1 snd_opl3_lib
snd_mpu401_uart 6272 1 snd_cmipci
snd_rawmidi 20640 1 snd_mpu401_uart
8139too 19712 0
I don't know if smbus is detected correctly.
bash-2.05b# /var/tools/lm_sensors-2.8.4/prog/detect/i2cdetect
Error: No i2c-bus specified!
Syntax: i2cdetect I2CBUS
I2CBUS is an integer
i2cdetect -l lists installed busses only
Installed I2C busses:
i2c-2 unknown NVIDIA display adapter bus 0
Algorithm unavailable
i2c-1 unknown NVIDIA display adapter bus 1
Algorithm unavailable
i2c-0 unknown SMBus I801 adapter at e800
Algorithm unavailable
What does it mean that I have "No i2c-bus specified!"?? Sensor-detect works
great and it finds my GF board just like on 2.4 kernel. But the sensor output
is:
bash-2.05b# sensors
eeprom-i2c-6-57
Adapter: NVIDIA display adapter bus 0
eeprom-i2c-6-56
Adapter: NVIDIA display adapter bus 0
eeprom-i2c-6-55
Adapter: NVIDIA display adapter bus 0
eeprom-i2c-6-54
Adapter: NVIDIA display adapter bus 0
eeprom-i2c-6-53
Adapter: NVIDIA display adapter bus 0
eeprom-i2c-6-52
Adapter: NVIDIA display adapter bus 0
eeprom-i2c-6-51
Adapter: NVIDIA display adapter bus 0
eeprom-i2c-6-50
Adapter: NVIDIA display adapter bus 0
Either use the ddcmon driver instead of the eeprom driver,
or run the decode-edid.pl script.
eeprom-i2c-0-50
Adapter: SMBus I801 adapter at e800
Memory type: DDR SDRAM DIMM
Memory size (MB): 256
as99127f-i2c-0-2d
Adapter: SMBus I801 adapter at e800
VCore 1: +1.71 V (min = +1.66 V, max = +1.82 V)
VCore 2: +1.76 V (min = +1.66 V, max = +1.82 V)
+3.3V: +3.17 V (min = +3.14 V, max = +3.46 V) ALARM
+5V: +5.05 V (min = +4.73 V, max = +5.24 V)
+12V: +11.19 V (min = +10.82 V, max = +13.19 V)
-12V: -11.70 V (min = -0.00 V, max = -0.00 V)
-5V: -4.43 V (min = -0.00 V, max = -0.00 V)
fan1: 0 RPM (min = 3994 RPM, div = 2)
fan2: 0 RPM (min = 998 RPM, div = 8)
fan3: 0 RPM (min = 998 RPM, div = 8)
M/B Temp: +24C (high = +80C, hyst = +75C)
CPU Temp: +27.0C (high = +100C, hyst = +90C)
temp3: -0.5C (high = +80C, hyst = +75C)
vid: +1.750 V
alarms:
beep_enable:
Sound alarm enabled
Only mainboard sensor readings are displayed. Why there is so many buses?? When
I was using kernel 2.4 the output was:
w83781d-i2c-2-2d
Adapter: NVIDIA display adapter bus 1
Algorithm: Bit-shift algorithm
VCore 1: +2.84 V (min = +0.00 V, max = +0.00 V) ALARM
VCore 2: +1.40 V (min = +0.00 V, max = +0.00 V) ALARM
+3.3V: +2.97 V (min = +2.97 V, max = +3.63 V) ALARM
...etc. It was bus 1, not 0. Also I didn't have to load eeprom module to make
card visible to sensors.
I tried patching rivatv with patch called "rivatv-0.8.3-i2c-2.8.0.patch" but it
didn't help. I also couldn't find module ddcmon. Decode-edid.pl says: "EDID
EEPROM not found. Please make sure that the eeprom module is loaded.".
I'm out of ideas.
--- The new sensors output looks better to me.
Don't load the eeprom module and you won't get all the extra stuff.
What exactly is the problem? Looks good to me!
If you have further questions follow up by email, ref. your ticket #.
The rivatv i2c driver was missing the correct classes. Once added, the hardware
monitoring chip is back. Patch has been sent to the rivatv team.
Khali 2004-03-06
