* [lm-sensors] i2c_nforce2 on ASUS K8N-DRE
@ 2006-09-06 18:19 Brady Chang
2006-09-06 19:14 ` Jean Delvare
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: Brady Chang @ 2006-09-06 18:19 UTC (permalink / raw)
To: lm-sensors
Hi all,
I have the K8N-DRE running redhat 4 update 3
Kernel 2.6.9-34.0.2ELsmp , sensors version 2.8.7
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 8162
Flags: 66Mhz, fast devsel, IRQ 177
I/O ports at fc00 [size2]
I/O ports at 4c00 [sized]
I/O ports at 4c40 [sized]
Capabilities: [44] Power Management version 2
Appreciated if anyone knows what PCI ID's I should add to the nForce2_smbus
In the past, I used
echo "10de 0052" > /sys/bus/pci/drivers/nForce2_smbus/new_id on the Tyans, and it seems to work.
thanks in advance for your assistance.
-Brady
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060906/bb87b898/attachment.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lm-sensors] i2c_nforce2 on ASUS K8N-DRE
2006-09-06 18:19 [lm-sensors] i2c_nforce2 on ASUS K8N-DRE Brady Chang
@ 2006-09-06 19:14 ` Jean Delvare
2006-09-06 19:17 ` Brady Chang
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Jean Delvare @ 2006-09-06 19:14 UTC (permalink / raw)
To: lm-sensors
Hi Brady,
> I have the K8N-DRE running redhat 4 update 3
> Kernel 2.6.9-34.0.2ELsmp , sensors version 2.8.7
>
> 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
> Subsystem: ASUSTeK Computer Inc.: Unknown device 8162
> Flags: 66Mhz, fast devsel, IRQ 177
> I/O ports at fc00 [size2]
> I/O ports at 4c00 [sized]
> I/O ports at 4c40 [sized]
> Capabilities: [44] Power Management version 2
>
>
> Appreciated if anyone knows what PCI ID's I should add to the nForce2_smbus
>
> In the past, I used
> echo "10de 0052" > /sys/bus/pci/drivers/nForce2_smbus/new_id on the Tyans, and it seems to work.
I don't understand what you want. The PCI ID is 10de 0052, you wrote it
yourself above. What's your problem exactly?
--
Jean Delvare
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lm-sensors] i2c_nforce2 on ASUS K8N-DRE
2006-09-06 18:19 [lm-sensors] i2c_nforce2 on ASUS K8N-DRE Brady Chang
2006-09-06 19:14 ` Jean Delvare
@ 2006-09-06 19:17 ` Brady Chang
2006-09-06 19:43 ` Jean Delvare
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Brady Chang @ 2006-09-06 19:17 UTC (permalink / raw)
To: lm-sensors
Hi Jean,
I forgot to mention that the PCI ID worked on Tyan 2891 did not work for the ASUS k8n-dre.
thanks
-Brady
________________________________
From: Jean Delvare [mailto:khali at linux-fr.org]
Sent: Wed 9/6/2006 2:14 PM
To: Brady Chang
Cc: lm-sensors at lm-sensors.org
Subject: Re: [lm-sensors] i2c_nforce2 on ASUS K8N-DRE
Hi Brady,
> I have the K8N-DRE running redhat 4 update 3
> Kernel 2.6.9-34.0.2ELsmp , sensors version 2.8.7
>
> 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
> Subsystem: ASUSTeK Computer Inc.: Unknown device 8162
> Flags: 66Mhz, fast devsel, IRQ 177
> I/O ports at fc00 [size2]
> I/O ports at 4c00 [sized]
> I/O ports at 4c40 [sized]
> Capabilities: [44] Power Management version 2
>
>
> Appreciated if anyone knows what PCI ID's I should add to the nForce2_smbus
>
> In the past, I used
> echo "10de 0052" > /sys/bus/pci/drivers/nForce2_smbus/new_id on the Tyans, and it seems to work.
I don't understand what you want. The PCI ID is 10de 0052, you wrote it
yourself above. What's your problem exactly?
--
Jean Delvare
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060906/85fd3d4a/attachment.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lm-sensors] i2c_nforce2 on ASUS K8N-DRE
2006-09-06 18:19 [lm-sensors] i2c_nforce2 on ASUS K8N-DRE Brady Chang
2006-09-06 19:14 ` Jean Delvare
2006-09-06 19:17 ` Brady Chang
@ 2006-09-06 19:43 ` Jean Delvare
2006-09-06 19:58 ` Brady Chang
2006-09-06 21:19 ` Jean Delvare
4 siblings, 0 replies; 6+ messages in thread
From: Jean Delvare @ 2006-09-06 19:43 UTC (permalink / raw)
To: lm-sensors
Brady,
> I forgot to mention that the PCI ID worked on Tyan 2891 did
> not work for the ASUS k8n-dre.
If that's the same device, that's the same ID, so if you use the same
kernel on both and it works for one board it must work for the other.
You can check the exact ID with "lspci -n".
--
Jean Delvare
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lm-sensors] i2c_nforce2 on ASUS K8N-DRE
2006-09-06 18:19 [lm-sensors] i2c_nforce2 on ASUS K8N-DRE Brady Chang
` (2 preceding siblings ...)
2006-09-06 19:43 ` Jean Delvare
@ 2006-09-06 19:58 ` Brady Chang
2006-09-06 21:19 ` Jean Delvare
4 siblings, 0 replies; 6+ messages in thread
From: Brady Chang @ 2006-09-06 19:58 UTC (permalink / raw)
To: lm-sensors
I imagine that should be the case.
I have another computer with supermicro board. That seems to work once I added the newIDs.
on k8n-dre:
lspci -n
00:01.1 Class 0c05: 10de:0052 (rev a2)
on H8DCE-HTE
lspci -n
00:01.1 Class 0c05: 10de:0052 (rev a2)
Check with ASUS for now.
thanks
-Brady
________________________________
From: Jean Delvare [mailto:khali at linux-fr.org]
Sent: Wed 9/6/2006 2:43 PM
To: Brady Chang
Cc: lm-sensors at lm-sensors.org
Subject: Re: [lm-sensors] i2c_nforce2 on ASUS K8N-DRE
Brady,
> I forgot to mention that the PCI ID worked on Tyan 2891 did
> not work for the ASUS k8n-dre.
If that's the same device, that's the same ID, so if you use the same
kernel on both and it works for one board it must work for the other.
You can check the exact ID with "lspci -n".
--
Jean Delvare
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060906/9c3ce58b/attachment.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lm-sensors] i2c_nforce2 on ASUS K8N-DRE
2006-09-06 18:19 [lm-sensors] i2c_nforce2 on ASUS K8N-DRE Brady Chang
` (3 preceding siblings ...)
2006-09-06 19:58 ` Brady Chang
@ 2006-09-06 21:19 ` Jean Delvare
4 siblings, 0 replies; 6+ messages in thread
From: Jean Delvare @ 2006-09-06 21:19 UTC (permalink / raw)
To: lm-sensors
> I imagine that should be the case.
> I have another computer with supermicro board. That seems to work once I added the newIDs.
>
> on k8n-dre:
> lspci -n
> 00:01.1 Class 0c05: 10de:0052 (rev a2)
>
> on H8DCE-HTE
> lspci -n
> 00:01.1 Class 0c05: 10de:0052 (rev a2)
>
> Check with ASUS for now.
Is it the same kernel? You need hotplug support, else adding the new id
on the fly doesn't work.
Please provide the output of "lspci -xxx -s 00:01.1" on the failing
machine.
Nothing in the logs when you add the new id? The driver should complain
if something goes wrong.
--
Jean Delvare
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-09-06 21:19 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-06 18:19 [lm-sensors] i2c_nforce2 on ASUS K8N-DRE Brady Chang
2006-09-06 19:14 ` Jean Delvare
2006-09-06 19:17 ` Brady Chang
2006-09-06 19:43 ` Jean Delvare
2006-09-06 19:58 ` Brady Chang
2006-09-06 21:19 ` Jean Delvare
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.