sensor konfiguration für lm75A und sysinfo gesucht

  • Hallo,


    ich versuche gerade, einen an den i2c Bus gehangenen LM75 mit sensors auszulesen. Leider wird der LM75 nur mit sensors-detect erkannt, ist aber irgendwie nicht über sensors ansprechbar. Kann sich vielleicht ein Spezi meine output's ansehen und mir einen Tip geben ?
    Bei mir läuft im Moment noch MVDR1.3, aber auch unter suse9.2 bekomme ich es nicht hin...
    Vielen Dank im Voraus


    linux:~ # sensors-detect


    This program will help you determine which I2C/SMBus modules you need to
    load to use lm_sensors most effectively. You need to have i2c and
    lm_sensors installed before running this program.
    Also, you need to be `root', or at least have access to the /dev/i2c-*
    files, for most 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.


    It is generally safe and recommended to accept the default answers to all
    questions, unless you know what you're doing.


    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): y
    Probing for PCI bus adapters...
    Use driver `i2c-matroxfb' for device 01:00.0: MGA G200 AGP
    Use driver `i2c-piix4' for device 00:07.3: Intel 82371AB PIIX4 ACPI
    Probe succesfully concluded.


    We will now try to load each adapter module in turn.
    Load `i2c-matroxfb' (say NO if built into your kernel)? (YES/no): n
    Module `i2c-piix4' already loaded.
    If you have undetectable or unsupported adapters, you can have them
    scanned by manually loading the modules before running this script.


    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 already loaded.


    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. That often
    includes address 0x69 (clock chip).


    Next adapter: SMBus PIIX4 adapter at f0b0 (Algorithm unavailable)
    Do you want to scan it? (YES/no/selectively): y
    Client found at address 0x49
    Probing for `National Semiconductor LM75'... Success!
    (confidence 6, driver `lm75')
    Probing for `Dallas Semiconductor DS1621'... Failed!
    Probing for `National Semiconductor LM92'... Failed!
    Probing for `National Semiconductor LM76'... Failed!
    Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
    Client at address 0x50 can not be probed - unload all client drivers first!
    Client at address 0x54 can not be probed - unload all client drivers first!
    Client found at address 0x69
    Client found at address 0x73
    Probing for `FSC Poseidon'... Success!
    (confidence 8, driver `fscpos')
    Probing for `FSC Scylla'... Failed!
    Probing for `FSC Hermes'... Failed!


    Some chips are also accessible through the ISA bus. ISA probes are
    typically a bit more dangerous, as we have to write to I/O ports to do
    this. This is usually safe though.


    Do you want to scan the ISA bus? (YES/no): n


    Some Super I/O chips may also contain sensors. Super I/O probes are
    typically a bit more dangerous, as we have to write to I/O ports to do
    this. This is usually safe though.


    Do you want to scan for Super I/O sensors? (YES/no): n


    Now follows a summary of the probes I have just done.
    Just press ENTER to continue:


    Driver `lm75' (should be inserted):
    Detects correctly:
    * Bus `SMBus PIIX4 adapter at f0b0' (Algorithm unavailable)
    Busdriver `i2c-piix4', I2C address 0x49
    Chip `National Semiconductor LM75' (confidence: 6)


    Driver `fscpos' (should be inserted):
    Detects correctly:
    * Bus `SMBus PIIX4 adapter at f0b0' (Algorithm unavailable)
    Busdriver `i2c-piix4', I2C address 0x73
    Chip `FSC Poseidon' (confidence: 8)



    I will now generate the commands needed to load the I2C modules.
    Sometimes, a chip is available both through the ISA bus and an I2C bus.
    ISA bus access is faster, but you need to load an additional driver module
    for it. If you have the choice, do you want to use the ISA bus or the
    I2C/SMBus (ISA/smbus)? smbus


    To make the sensors modules behave correctly, add these lines to
    /etc/modprobe.conf:


    #----cut here----
    # I2C module options
    alias char-major-89 i2c-dev
    #----cut here----


    To load everything that is needed, add this to some /etc/rc* file:


    #----cut here----
    # I2C adapter drivers
    modprobe i2c-piix4
    # I2C chip drivers
    modprobe lm75
    modprobe fscpos
    # sleep 2 # optional
    /usr/bin/sensors -s # recommended
    #----cut here----


    WARNING! If you have some things built into your kernel, the list above
    will contain too many modules. Skip the appropriate ones! You really should
    try these commands right now to make sure everything is working properly.
    Monitoring programs won't work until it's done.


    Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): n


    ========================================================================================================================


    linux:~ # sensors lm75-i2c-0-49
    Specified sensor(s) not found!


    =========================================================================================================================


    linux:~ # lsmod
    Module Size Used by
    thinkpad 6020 0
    snd_pcm_oss 57896 0
    snd_pcm 96776 1 snd_pcm_oss
    snd_timer 24708 1 snd_pcm
    snd_page_alloc 10248 1 snd_pcm
    snd_mixer_oss 19200 1 snd_pcm_oss
    snd 60164 4 snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
    soundcore 9056 1 snd
    nvram 8328 0
    usbserial 26856 0
    parport_pc 37824 1
    lp 10536 0
    parport 37960 2 parport_pc,lp
    speedstep_lib 4228 0
    freq_table 4356 0
    thermal 17928 0
    processor 25640 1 thermal
    fan 5380 0
    button 8464 0
    battery 11396 0
    ac 6404 0
    ipt_TOS 2560 14
    ip6t_LOG 6656 17
    ip6t_limit 2432 17
    ipt_LOG 6912 30
    ipt_limit 2432 30
    ipt_pkttype 1792 2
    edd 10012 0
    ip6t_state 2048 22
    ip6_conntrack 38404 1 ip6t_state
    ipt_state 2176 28
    ip6t_REJECT 7552 3
    ipt_REJECT 6784 3
    iptable_mangle 2944 1
    iptable_filter 3072 1
    ip6table_mangle 2688 0
    ip_nat_ftp 5232 0
    iptable_nat 23980 1 ip_nat_ftp
    ip_conntrack_ftp 72624 1 ip_nat_ftp
    ip_conntrack 43512 4 ipt_state,ip_nat_ftp,iptable_nat,ip_conntrack_ftp
    ip_tables 17664 9 ipt_TOS,ipt_LOG,ipt_limit,ipt_pkttype,ipt_state,ipt_REJECT,iptable_mangle,iptable_filter,iptable_nat
    ip6table_filter 2816 1
    ip6_tables 18816 6 ip6t_LOG,ip6t_limit,ip6t_state,ip6t_REJECT,ip6table_mangle,ip6table_filter
    ipv6 237312 15 ip6_conntrack,ip6t_REJECT
    lm75 8732 0
    eeprom 8480 0
    i2c_sensor 3968 2 lm75,eeprom
    i2c_dev 9472 0
    i2c_piix4 8336 0
    i2c_core 23312 5 lm75,eeprom,i2c_sensor,i2c_dev,i2c_piix4
    joydev 9664 0
    sg 35872 0
    st 37404 0
    sr_mod 16292 0
    ide_cd 38176 0
    cdrom 36508 2 sr_mod,ide_cd
    intel_agp 21024 1
    agpgart 32168 1 intel_agp
    uhci_hcd 29712 0
    subfs 7552 3
    nls_utf8 2176 1
    nls_cp437 5888 1
    vfat 13056 1
    fat 43168 1 vfat
    evdev 8960 0
    dm_mod 54524 0
    usbcore 106724 4 usbserial,uhci_hcd
    reiserfs 242000 1
    aic7xxx 179768 3
    sd_mod 16912 4
    scsi_mod 111308 5 sg,st,sr_mod,aic7xxx,sd_mod
    linux:~ #



    Gruß marder

  • neuer Stand,


    habe leider herausgefunden, das der LM75A unter Windows mit MBM5 läuft, aber unter Linux der LM75 Treiber nicht ausreicht, um den Sensor auszulesen. Nun bräuchte ich ein für den Kernel 2.6.13.2 kompiliertes Treibermodul, um es selber laden zu können und ich bezweifle, daß mir hier jemand weiterhelfen kann, oder ?


    Gruß marder

  • Hi,


    hast Du es schonmal nur mit sensors versucht, also ohne Parameter? Ich hab bei mir den lm89 und ich starte es immer ohne irgendwelche Parameter. Vielleicht mal ein Versuch, es könnte ja sein, dass das, was Du als Parameter für lm75 eingibts einfach nicht existiert?
    Bei mir wird der Chip automatisch erkannt...:



    root@vdr-box:~# sensors
    lm85b-i2c-0-2e
    Adapter: SMBus I801 adapter at dc00


    V1.5: +1.50 V (min = +1.42 V, max = +1.58 V)
    VCore: +1.50 V (min = +1.45 V, max = +1.60 V)
    V3.3: +3.37 V (min = +3.13 V, max = +3.47 V)
    V5: +5.13 V (min = +4.74 V, max = +5.26 V)
    V12: +12.12 V (min = +11.38 V, max = +12.62 V)
    CpuFan: 2174 RPM (min = 1000 RPM)
    Fan2: 1361 RPM (min = 0 RPM)
    Fan3: 210 RPM (min = 0 RPM)
    Fan4: 1650 RPM (min = 0 RPM)
    CPU: +29 C (low = -128 C, high = +50 C)
    Board: +31 C (low = +10 C, high = +35 C)
    Remote: +26 C (low = +10 C, high = +35 C)
    CPU_PWM: 255
    Fan2_PWM: 255
    Fan3_PWM: 77
    vid: +1.525 V (VRM Version 9.0)


    Nur mal so als Idee...


    Gruß Doc

    Current:

    Hardware_: Gigabyte B360M D3H, Silverstone Milo ML03, DD Cine S2 V7A, 256GB Samsung EVO 970, 4GB RAM, ASUS GT1030 passive

    Software_: ArchLinux, VDR4Arch, VDR 2.4.0, softhdcuvid, nordlichtsepg, skinenigmang


Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!