From df027fb0d5ea630e09e50ba766f955637e6ae8fc Mon Sep 17 00:00:00 2001 From: Jean Delvare Date: Sun, 23 Sep 2007 16:37:51 +0000 Subject: [PATCH] Drop all references to the MBM website, it's gone now. git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4857 7894878c-1315-0410-8ee3-d5d059ff63e0 --- doc/FAQ | 23 +++++++++-------------- doc/lm_sensors-FAQ.html | 8 +++----- doc/lm_sensors-FAQ.texi | 6 ++---- doc/useful_addresses.html | 5 ----- 4 files changed, 14 insertions(+), 28 deletions(-) diff --git a/doc/FAQ b/doc/FAQ index cc4b2c56..18be897b 100644 --- a/doc/FAQ +++ b/doc/FAQ @@ -355,10 +355,9 @@ for candidates, then *note Help::) 3. Check the manufacturer's website or ask their support - 4. Check the Motherboard Monitor (http://mbm.livewiredev.com/) - website and the "links" - (http://www.lm-sensors.org/wiki/UsefulLinks) page on our website - (http://www.lm-sensors.org) some good cross-references. + 4. Check the "links" (http://www.lm-sensors.org/wiki/UsefulLinks) + page on our website (http://www.lm-sensors.org) some good + cross-references. 3.2.2 Do you support motherboard XYZ? ------------------------------------- @@ -861,13 +860,12 @@ it was misidentified. We are working on improving that too. -------------------------------------- Do you own an ASUS motherboard? Perhaps your chip is being -misidentified. Look on the motherboard (or at -`http://mbm.livewiredev.com') for a 'Winbond' or Asus chip. Often the -real device is an Asus as99127f. If so, the driver can be forced to -recognize the as99127f with `force_as99127f=BUS,0x2d' where `BUS' is -your i2c bus number. Cat /proc/bus/i2c to see a list of bus numbers. -Read the w83781d module documentation (`doc/chips/w83781d') for more -details. +misidentified. Look on the motherboard for a 'Winbond' or Asus chip. +Often the real device is an Asus as99127f. If so, the driver can be +forced to recognize the as99127f with `force_as99127f=BUS,0x2d' where +`BUS' is your i2c bus number. Cat /proc/bus/i2c to see a list of bus +numbers. Read the w83781d module documentation (`doc/chips/w83781d') +for more details. 4.17.6 Bus hangs on Ali 1543 on Asus P5A boards! ------------------------------------------------ @@ -1085,9 +1083,6 @@ Either 2. Check the manufacturer's website. - 3. Check the Motherboard Monitor (http://mbm.livewiredev.com/) - website. - When you know what chips you have, check the Driver Status (http://www.lm-sensors.org/wiki/Devices) web page to see if support has been added for your chip in a later release or in SVN. diff --git a/doc/lm_sensors-FAQ.html b/doc/lm_sensors-FAQ.html index d004d244..fc77a032 100644 --- a/doc/lm_sensors-FAQ.html +++ b/doc/lm_sensors-FAQ.html @@ -588,7 +588,7 @@ for candidates, then see Help)
  1. Look at your motherboard.
  2. Check the manufacturer's website or ask their support -
  3. Check the Motherboard Monitor website and the +
  4. Check the "links" page on our website some good cross-references.
@@ -1371,8 +1371,7 @@ misidentified. We are working on improving that too.

4.17.5 Bad readings from a w8378[12]d!

Do you own an ASUS motherboard? Perhaps your chip is being -misidentified. Look on the motherboard (or at -http://mbm.livewiredev.com) for a 'Winbond' or Asus chip. +misidentified. Look on the motherboard for a 'Winbond' or Asus chip. Often the real device is an Asus as99127f. If so, the driver can be forced to recognize the as99127f with force_as99127f=BUS,0x2d where BUS is your i2c bus number. @@ -1643,8 +1642,7 @@ Run devfs in the kernel to get the But in any case you should figure out what is on the board:

  1. Look at your motherboard. -
  2. Check the manufacturer's website. -
  3. Check the Motherboard Monitor website. +
  4. Check the manufacturer's website.

When you know what chips you have, check the diff --git a/doc/lm_sensors-FAQ.texi b/doc/lm_sensors-FAQ.texi index de5a6f26..2a9b79ea 100644 --- a/doc/lm_sensors-FAQ.texi +++ b/doc/lm_sensors-FAQ.texi @@ -317,7 +317,7 @@ If that doesn't work: @enumerate 2 @item Look at your motherboard. @item Check the manufacturer's website or ask their support -@item Check the @uref{http://mbm.livewiredev.com/, Motherboard Monitor} website and the +@item Check the @uref{http://www.lm-sensors.org/wiki/UsefulLinks, "links"} page on @uref{http://www.lm-sensors.org, our website} some good cross-references. @end enumerate @@ -902,8 +902,7 @@ misidentified. We are working on improving that too. @subsection Bad readings from a w8378[12]d! Do you own an ASUS motherboard? Perhaps your chip is being -misidentified. Look on the motherboard (or at -@uref{http://mbm.livewiredev.com}) for a 'Winbond' or Asus chip. +misidentified. Look on the motherboard for a 'Winbond' or Asus chip. Often the real device is an Asus as99127f. If so, the driver can be forced to recognize the as99127f with @command{force_as99127f=BUS,0x2d} where @code{BUS} is your i2c bus number. @@ -1123,7 +1122,6 @@ But in any case you should figure out what is on the board: @enumerate @item Look at your motherboard. @item Check the manufacturer's website. -@item Check the @uref{http://mbm.livewiredev.com/, Motherboard Monitor} website. @end enumerate When you know what chips you have, check the diff --git a/doc/useful_addresses.html b/doc/useful_addresses.html index 108fe5e1..5b8e41f2 100644 --- a/doc/useful_addresses.html +++ b/doc/useful_addresses.html @@ -253,11 +253,6 @@ implementations. Please report any other references you have found!

  • Other hardware monitoring implementations (not using LM Sensors)