860 replies to this topic

[scorcho]

I'm curious about this too. If I don't need it then I'd rather not install it. I like to keep third-party kexts to a minimum.

just test it out yourself by booting with the kext and without it. the hwmonitor app will tell you whether you're seeing more sensors or not, and then you can decide.

[Riley Freeman]

I removed it last night and everything looked the same in HWMonitor and iStat Menus. So I guess I don't need it after all. My system log shows "SuperIODevice: found Nuvoton NCT6776F" so it must be supported by MotherboardSensors.kext

[Kucksy]

Intel DQ35JO motherboard - with the following output thanks to sudo dmesg -grep

F718x: Fintek: Found unsupported chip ID=0xf1 REVISION=0x91
IT87x: [Warning] found unsupported chip ID=0xf191
W836x: found unsupported chip ID=0xf1 REVISION=0x91

Cheers for all the great work so far

Troy

[kozlek]

Intel DQ35JO motherboard - with the following output thanks to sudo dmesg -grep

F718x: Fintek: Found unsupported chip ID=0xf1 REVISION=0x91
IT87x: [Warning] found unsupported chip ID=0xf191
W836x: found unsupported chip ID=0xf1 REVISION=0x91

Cheers for all the great work so far

Troy

Seems you hardware is unsupported.

Sorry, but I have no idea what's the chip is on you motherboard.

[Mohamed Khairy]

with latest changes

HWSensors Project Copyright 2012 netkas, slice, usr-sse2, kozlek, navi, THe KiNG. All rights reserved.
FakeSMCDevice: 22 preconfigured key(s) added
SMC: successfully initialized
INT340ESensors: [Warning] failed to evaluate TSDL table
INT340ESensors: [Warning] failed to evaluate OSDL table
INT340ESensors: started
CPUSensors: CPU family 0x6, model 0x2a, stepping 0x7, cores 2, threads 4, TJmax 100
console relocated to 0xf10000000
PCI configuration changed (bridge=18 device=2 cardbus=0)
[ PCI configuration end, bridges 7 devices 12 ]
INT340ESensors: started

@

kozlek

any idea about that ?

do you need any other info ?

[kozlek]

@

kozlek

any idea about that ?

do you need any other info ?

Sorry, you hardware is unsupported.

[TimeWalker75a]

It's easy - just remove INT3F0D from the project (I believe I've seen just one person having a SuperIO with such an ID and it gives absolutely nothing, just PCH and CPU Package temps with is practically useless) and you won't find people constantly reporting this. Because even if the machine has, say a Nuovoton chip user will still get some errors.
With the addition of INT3F0D into INT340ESensors it now tries to attach to a CWDT device found on most SNB/IVB motherboards/laptops since the device has the same EISA but has nothing to do with monitoring.

                Device (CWDT)
                {
                    Name (_HID, EisaId ("INT3F0D"))
                    Name (_CID, EisaId ("PNP0C02"))
                    Name (BUF0, ResourceTemplate ()
                    {
                        IO (Decode16,
                            0x0454,             // Range Minimum
                            0x0454,             // Range Maximum
                            0x04,               // Alignment
                            0x04,               // Length
                            )
                    })
                    Method (_STA, 0, Serialized)
                    {
                        If (LEqual (WDTE, One))
                        {
                            Return (0x0F)
                        }
                        Else
                        {
                            Return (Zero)
                        }
                    }
                    Method (_CRS, 0, Serialized)
                    {
                        Return (BUF0)
                    }
                }

[kozlek]

It's easy - just remove INT3F0D from the project (I believe I've seen just one person having a SuperIO with such an ID and it gives absolutely nothing, just PCH and CPU Package temps with is practically useless) and you won't find people constantly reporting this. Because even if the machine has, say a Nuovoton chip user will still get some errors.
With the addition of INT3F0D into INT340ESensors it now tries to attach to a CWDT device found on most SNB/IVB motherboards/laptops since the device has the same EISA but has nothing to do with monitoring.

I can solve this problem without restricting some people from monitoring their PCH and CPU temps. Maybe I'll update ACPISensors later.

[Mohamed Khairy]

Sorry, you hardware is unsupported.

so any upcoming thing give hope for my sensor ?

[kozlek]

so any upcoming thing give hope for my sensor ?

I am not develop plugins, only port some working code from windows and linux from other developers and maintain it.

[bcobco]

hi kozlek
i tried fakesmc versions 4.2 but they dont work. im stuck on 4.0. older versions 3 and even older version 2 works. but 4.2 doesnt. why? thanks in advance

[TimeWalker75a]

so any upcoming thing give hope for my sensor ?

decipher your registers/SMBUS output and make use of APCISensors. That is what I'm doing and it's pretty cool if you ask me.

[Mohamed Khairy]

decipher your registers/SMBUS output and make use of APCISensors. That is what I'm doing and it's pretty cool if you ask me.

my acpi tables does contain EC and no data for using acpisensors
you can see my tables on my topic

I am not develop plugins, only port some working code from windows and linux from other developers and maintain it.

so is the latest lunix kernel 3.6 rc6
or lm-sensors contain something useful for me ?

[kozlek]

my acpi tables does contain EC and no data for using acpisensors
you can see my tables on my topic



so is the latest lunix kernel 3.6 rc6
or lm-sensors contain something useful for me ?

Nothing useful for you.

[D-an-W]

Everything looking good with the latest version

Attached Files

•  Screen Shot 2012-09-23 at 14.19.12.png   336.64KB   168 downloads

[Peter_sm]

Hmmm, above post looks great, how can this be possible on a laptop, see more info on a earlier post from me....


http://www.insanelym...00#entry1850015

[myrorym]

When updating I always (feel the) need to go back to change this key in the info.plist

	 <key>REV </key>
	 <array>
	 <string>{rev</string>
	 <data>
	 ATkPAAAR
	 </data>
	 </array>

and also

<key>smc-compatible</key>
<string>smc-thurley</string>

I change to ATkPAAAR because it is closer match with a real MacPro5,1, not sure where I picked that up, but does it matter to the OS? or is it just cosmetic for System Profiler?

If it is a recommended change, it'd be helpful to have options in the installer based on the system users are emulating. Not sure how much research it would take, but I wonder how many people change this?

[wormyrocks]

After installing this I get a kernel panic immediately following boot, involving the kexts installed and their dependencies. What files must I remove in order to restore my install to operational status?

[D-an-W]

Are you running Kext Utility after installing and before rebooting (I install manually so always do this)?

[wormyrocks]

No, I didn't... my entire process of thought was a festering orgy of idiocy. Just installed, rebooted, and said, WELP, EVERYTHING HAD BETTER BE OKAY.
So yes, now I'm kicking myself. Ugh.