Re: Help please, setting up lm-sensors
On Fri, 2001-12-14 at 21:20, Stan Brown wrote: I;ve got a new machine with a custom 2.4.16 kernel. I have managed to get lm-sensors built, and the modules load. However sensor-detect does not give me enough info to get the rest set up. The machine is a Epox EP-8KTA3PRO with a VIA KT133A chipset. Here is a typescript of the sensors detect run: Script started on Fri Dec 14 21:35:36 2001 progeny:~# sensors-detect This program will help you to determine which I2C/SMBus modules you need to load to use lm_sensors most effectively. You need to have installed lm-sensors modules before you can use some functions of this utility. Also, you need to be root', or at least have access to the /dev/i2c* files for some things. If you have patched your kernel and have some drivers built-in you can safely answer NO if asked to load some modules. In this case, things may seem a bit confusing, but they will still work. We can start with probing for (PCI) I2C or SMBus adapters. You do not need any special privileges for this. Do you want to probe now? (YES/no): Probing for PCI bus adapters... Use driver `i2c-viapro' for device 00:07.4: VIA Technologies VT 82C686 Apollo ACPI Probe succesfully concluded. We will now try to load each adapter module in turn. Load `i2c-viapro' (say NO if built into your kernel)? (YES/no): Module loaded succesfully. Do you now want to be prompted for non-detectable adapters? (yes/NO): To continue, we need module `i2c-dev' to be loaded. If it is built-in into your kernel, you can safely skip this. i2c-dev is not loaded. Do you want to load it now? (YES/no): Module loaded succesfully. We are now going to do the adapter probings. Some adapters may hang halfway through; we can't really help that. Also, some chips will be double detected; we choose the one with the highest confidence value in that case. If you found that the adapter hung after probing a certain address, you can specify that address to remain unprobed. If you have a PIIX4, that often includes addresses 0x69 and/or 0x6a. Next adapter: SMBus vt82c596 adapter at 5000 (Non-I2C SMBus adapter) Do you want to scan it? (YES/no/selectively): Can't open /dev/i2c0 (No such file or directory) Do you have this file in your /dev directory? If not, MAKEDEV i2c will make the device nodes for you. If you are using devfs you're going to have some fun trying to debug why they don't show up. Once you get the dev files you should be able to get the right chips detected and proceed. --mike
Re: Help please, setting up lm-sensors
On Fri, Dec 14, 2001 at 10:20:14PM -0500, Stan Brown wrote: Can't open /dev/i2c0 (No such file or directory) The module loads successfully (so the hardware is there), but you can't talk to it, which seems to say to me that the entry in /dev is missing. Check that first. -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] pgpJmPfamBRl6.pgp Description: PGP signature
Re: Help please, setting up lm-sensors
Stan Brown [EMAIL PROTECTED] writes: SB I;ve got a new machine with a custom 2.4.16 kernel. I have managed to get SB lm-sensors built, and the modules load. However sensor-detect does not give SB me enough info to get the rest set up. SB Next adapter: SMBus vt82c596 adapter at 5000 (Non-I2C SMBus adapter) SB Do you want to scan it? (YES/no/selectively): SB Can't open /dev/i2c0 (No such file or directory) This looks wrong (either /dev/i2c/0 or /dev/i2c-0 would be plausible). Looking through the sensors-detect source, though (it's just a Perl script), it tries all three of i2c-0, i2c0, and i2c/0. What version of lm-sensors are you using? Of i2c? -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
Re: Help please, setting up lm-sensors
On Sat Dec 15 11:03:05 2001 David Z Maze wrote... Stan Brown [EMAIL PROTECTED] writes: SB I;ve got a new machine with a custom 2.4.16 kernel. I have managed to get SB lm-sensors built, and the modules load. However sensor-detect does not give SB me enough info to get the rest set up. SB Next adapter: SMBus vt82c596 adapter at 5000 (Non-I2C SMBus adapter) SB Do you want to scan it? (YES/no/selectively): SB Can't open /dev/i2c0 (No such file or directory) This looks wrong (either /dev/i2c/0 or /dev/i2c-0 would be plausible). Looking through the sensors-detect source, though (it's just a Perl script), it tries all three of i2c-0, i2c0, and i2c/0. What version of lm-sensors are you using? Of i2c? Im really not certain how to tell. Both are the version form the Debain -source package for testing. Looking in the CHANGES file, the latest version mentioned in both is 2.6.1 -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
Re: Help please, setting up lm-sensors
Stan Brown [EMAIL PROTECTED] writes: SB On Sat Dec 15 11:03:05 2001 David Z Maze wrote... DZM Stan Brown [EMAIL PROTECTED] writes: SB I;ve got a new machine with a custom 2.4.16 kernel. I have SB managed to get lm-sensors built, and the modules load. However SB sensor-detect does not give me enough info to get the rest set SB up. DZM SB Next adapter: SMBus vt82c596 adapter at 5000 (Non-I2C SMBus adapter) SB Do you want to scan it? (YES/no/selectively): SB Can't open /dev/i2c0 (No such file or directory) DZM DZM This looks wrong (either /dev/i2c/0 or /dev/i2c-0 would be DZM plausible). Looking through the sensors-detect source, though DZM (it's just a Perl script), it tries all three of i2c-0, i2c0, DZM and i2c/0. DZM DZM What version of lm-sensors are you using? Of i2c? SB SB Im really not certain how to tell. Both are the version form the SB Debain -source package for testing. Looking in the CHANGES file, SB the latest version mentioned in both is 2.6.1 The right way to check is to do 'dpkg -s lm-sensors-2.4.16' and 'dpkg -s i2c-2.4.16', and look for the Version there. The reported versions should be something like '2.6.1-1+2.4.16', depending on the version of the source you built and the --revision you built your kernel with. Other things that come to mind: 'modprobe i2c-dev' as root. Do you have a /dev/i2c directory then? Does your new kernel use devfs? Did your old one? (If you do, /dev will show up in /proc/mounts, and you'll probably have a /dev/.devfsd special device.) If you're not using devfs, you need to make sure that the i2c devices exist in /dev, doing (as someone else suggested) '/sbin/MAKEDEV i2c'. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
Re: Help please, setting up lm-sensors
On Sat Dec 15 11:58:04 2001 David Z Maze wrote... Stan Brown [EMAIL PROTECTED] writes: SB On Sat Dec 15 11:03:05 2001 David Z Maze wrote... DZM Stan Brown [EMAIL PROTECTED] writes: SB I;ve got a new machine with a custom 2.4.16 kernel. I have SB managed to get lm-sensors built, and the modules load. However SB sensor-detect does not give me enough info to get the rest set SB up. DZM SB Next adapter: SMBus vt82c596 adapter at 5000 (Non-I2C SMBus adapter) SB Do you want to scan it? (YES/no/selectively): SB Can't open /dev/i2c0 (No such file or directory) DZM DZM This looks wrong (either /dev/i2c/0 or /dev/i2c-0 would be DZM plausible). Looking through the sensors-detect source, though DZM (it's just a Perl script), it tries all three of i2c-0, i2c0, DZM and i2c/0. DZM DZM What version of lm-sensors are you using? Of i2c? SB SB Im really not certain how to tell. Both are the version form the SB Debain -source package for testing. Looking in the CHANGES file, SB the latest version mentioned in both is 2.6.1 The right way to check is to do 'dpkg -s lm-sensors-2.4.16' and 'dpkg -s i2c-2.4.16', and look for the Version there. The reported versions should be something like '2.6.1-1+2.4.16', depending on the version of the source you built and the --revision you built your kernel with. OK, Source: lm-sensors (2.6.1-3) Source: i2c (2.6.1-1) Other things that come to mind: 'modprobe i2c-dev' as root. Do you have a /dev/i2c directory then? Does your new kernel use devfs? Did your old one? (If you do, /dev will show up in /proc/mounts, and you'll probably have a /dev/.devfsd special device.) If you're not using devfs, you need to make sure that the i2c devices exist in /dev, doing (as someone else suggested) '/sbin/MAKEDEV i2c'. progeny:~# modprobe i2c-dev progeny:~# lsmod Module Size Used by i2c-dev 3968 0 (unused) i2c-core 13200 0 [i2c-dev] mousedev4432 1 input 3584 0 [mousedev] emu10k155696 0 (unused) sound 54992 0 [emu10k1] ide-scsi7616 0 progeny:~# ls /dev/i2* /dev/i2c-0 /dev/i2c-14 /dev/i2c-2 /dev/i2c-25 /dev/i2c-30 /dev/i2c-8 /dev/i2c-1 /dev/i2c-15 /dev/i2c-20 /dev/i2c-26 /dev/i2c-31 /dev/i2c-9 /dev/i2c-10 /dev/i2c-16 /dev/i2c-21 /dev/i2c-27 /dev/i2c-4 /dev/i2c-11 /dev/i2c-17 /dev/i2c-22 /dev/i2c-28 /dev/i2c-5 /dev/i2c-12 /dev/i2c-18 /dev/i2c-23 /dev/i2c-29 /dev/i2c-6 /dev/i2c-13 /dev/i2c-19 /dev/i2c-24 /dev/i2c-3 /dev/i2c-7 The machien has never had /dev/fsd on it. I ran /sbin/MAKEDEV 12c (when did it move there from /devg ?) with no complaints, but even after all of this, I wind up with this: #cut here # I2C adapter drivers # I2C chip drivers #cut here To make the sensors modules behave correctly, add these lines to /etc/modutils/local and run update-modules: #cut here # I2C module options alias char-major-89 i2c-dev #cut here When I run sensors-detect. What else can I try? Thanks for the help. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
