MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by opjose Nah he has an 801 see prior post.
If you will follow your own advice, I did state that I DID re-read his post and admitted to my mistake. Instead of regurgitating what has already been posted, why not give useful, and more important, constuctive solutions to get the OP closer to fixing his problem.
"If you will follow your own advice, I did state that I DID re-read his post and admitted to my mistake. Instead of regurgitating what has already been posted, why not give useful, and more important, constuctive solutions to get the OP closer to fixing his problem."
Wow, what a remarkably adolescent response!
You're also trying to get him to modprobe for chipsets which he has already determined (as per his prior post) do not exist in his system.
If you have been actually following this thread instead of standing on your pedestal, then you will find that he has not answered the questions that need to be answered to continue his progress in getting lm_sensors to work. And for the record, which chipsets have I been getting him to modprobe that he has found non-exist in his system? Please explain, or better yet, quote what has been posted.
Actually, (excuse my repetitiveness), I, for one, don't see anything that you have posted that has been helpful in this thread. So be it.
And I apologize if I touched your sensitivity. Like I said, follow your own advice and don't let the hippo out the crate.
You asked him to modprobe the w83627hf for which there is no kernel module for.
The i2c-801 should have suffied to report back fan and temp values.
As such either his i2c bus is not being recognized (unlikely as the RAM eeproms are being read) or his system board has the i2c mapped i/o locations at another address causing the system not to read.
Compiling a kernel is not a helpful step, usually a typical newbie response to a Linux problem due to other people erroneously recomending this. Not that you specifically told him to do so...
However when any such thing arises it's always best to first ask WHY should the kernel be recompiled and discourage the neophyte from attempting this course of action, which ends up causing them more problems than it's worth.
I've asked him in all cases to keep within the Mandrake framework so as not to break things.
It seems that for some reason you do not find this helpful so instead accuse me of placing myself on some pedastel.
Very strange. Someone does indeed seem to have some issues, and it is not I.
Please go ahead and dazzle us with your brilliance. Maybe you can show me something new.
Just to clear some thing up to avoid further confusion: the Abit IS-10 uses the Intel 865G chipset. SMBus i801 is a bus driver, a module in the kernel - two different things.
FuzzieDice: the last step in the sensors-detect program states:
Code:
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
This is the script that starts lm_sensors at boot time, you should follow that step unless you want to start lm_sensors manually each time you reboot.
Also, post the results of lsmod so we can see what's running and what's not
I'm in Windows at the minute as I just got done at work and am checking in here before I go boot to Mandrake Linux.
Firstly, to clarify a few things:
1. In Windows, I seem to have a "Intel 82801EB" SMBus controller with the hex value of "24D3" after the description. The "Intel 82865GE" appears to be in reference to the AGP and I/O controllers, as in:
Intel 82865G/PE/P/GV/82848P Processor to AGP Controller - 2571
Intel 82865G/PE/P/GV/82848P Processor to I/O Controller - 2570
Both of these have nothing to do with the SMBus. The SMBus is an "82801" so I'm guessing from this, in Linux I'd need an 801 driver. I think by 'chipset' they usually mean controllers and not sensors (my guess based on the above info).
2. I do remember giving my 'sensors' output in one of my previous posts.
3. While I have recompiled custom kernels before, I avoid having to do that like the plague. I've used Slackware (back when it first was released, even) and have ZipSlack 10 (though not installed right now), I've used Red Hat (last was v. 9) and am now using Mandrake 10 since I was not crazy about the move to Fedora Core and heard good things about Mandrake. However, I do pop terms and work a lot at the command line anyway, despite the fact I love KDE. But I still kinda consider myself a relative 'noobie' since I haven't used Linux for a few months and forgot a few things. So I might need to be reminded of the obvious now and then.
4. I read all posts and try things suggested, and I'll report back on some of these things. So please, do keep the ideas coming. Something might 'click' and actually work at some point. But I do hope I didn't start an arguement here. All responses are appreciated.
Oh yeah, and lastly, I'm a 'she' not really a 'he' but I don't mind. I've been thought of as a guy in FidoNet programming Echos as well.
Ok, I will get back into Linux and start trying to find the information some of you requested and post it soon.
If anyone needs more info on anything that seemed to get partly cut off in my above post, just ask and I'll repost those parts. But the red part is what I think we'd be concentrating on.
Right now, /etc/modules.conf has this added to it:
#I2C module options
alias char-major-89-i2c-dev
and /etc/rc.d/rc.modules has this added to the end of it:
I did the sensors-detect again, and I went for ISA instead of smbus, and then adjusted the rc.modules as recommended by the output. Reboot and still no sensors detected by gkrellm. Here's another output to consider as it stands now:
In every time I run sensors-detect, I do get this:
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83781d' (may not be inserted):
Misdetects:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627HF' (confidence: 8)
Driver `w83627hf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627HF Super IO Sensors' (confidence: 9)
Note the item in red says "misdetects" and the second one is ok. But the second one is a Super IO Sensor? What would be the difference and would that require some extra tweaks to get it working?
The problem is is that you need a kernel driver which hasn't been written yet.
The LM_SENSORS authors do this quite a bit, as they place the creation of the low level i2c & smbus drivers outside their "duties", leaving them instead to the kernel developers.
Check the lm_sensors home page for more info on what is being worked on, and what has outright no support nor intent of development.
I've run accross the same problem with a similiar motherboard for which even the latest kernels did not supply drivers.
The 2.6.3-13 and 2.6.6 Mdk kernels do have driver support for the W83627HF and W83781D chips. I'm pretty sure every version after that would also support them, or at least the W83627HF. According to lm_sensors, the W83627HF is an improvement on the older W83781D.
I looked through my old 2.6.3-7mdk kernel and, as some of the previous posts are pointing to, W83781D is there but W83627HF isn't. So it looks like your chances of getting lm_sensors working with your present setup are pretty slim, unless to move to a newer kernel.
@ mgd: Thanks for the clarification of the chipset/driver. I realized that when I re-read the OP's original post, that she had mentioned what her chipset was. So, I posted my mistake, but minutes later, I guess I needed to be corrected again to show my inferiority.
@ opjose: Well, again, you seem to be set on knowing only what you know and not believing in what is true. And again, if you had been following this thread, and actually reading all the info that been posted, then you won't need to make false accusations. Yes, I did post for the OP to modprobe w83627hf, for that's is what "sensors-detect" spit out, but that was BEFORE, she realized it wasn't complied in her running kernel version. So how am I having her do something she has already found futile? Now, to clear the air between you and I, what bothered me (only slightly though) was you to re-correct my mistake like you were of some authority, for I was only referring to your post " Nah he has an 801 see prior post." Then you had to take it further than needed by showing your immaturity. Again, I apologize if I offended you in any way, for that was not my intention. My focus was in helping the OP.
Now to shed some light on another example why I believe you're not being too helpful...
It very strange that you post
"The problem is is that you need a kernel driver which hasn't been written yet."
Yet, it seems that is has been "written" for I have that driver (w83627hf). I know I didn't compile it into my kernel.
@ FuzzieDice: And as mgd posted, moving up to a recent kernel version will work, for I know that since I had lm_sensors running on this mobo from kernel 2.6.7-x through 2.6.8.1-12. I haven't tried lm_sensors with your kernel version, and my ignorance in seeing that had me believing for sure it should work in your case.
Hmm...I guess there is something new to be learned everyday for everyone.
I used the word "nah" which caused you to accuse me of regurgitating useless information?
Hmm. I'd call this rather a rather overly sensitive and immature response.
Yet in the next breath I get elevated to placing myself on a pedestle and being immature?
I find that a bit funny. At my age being called immature tends to be a compliment.
Now if you looked at her original post you may have noticed that she was running Mandrake 10 official.
None of the current Mandrake 10 kernel releases have support for the W83627HF though I haven't looked at 10.1 CE.
mdg: stated that 2.6.3-13 has support for it, but even through 2.6.3-19mdk it is not present for 10.0.
Yet somehow you adjudged this as being not helpful.
Hmmm... Did someone make you chief post reviewer and value assessor?
If so you better get cracking as there are plenty of "more useless" posts around here that merit a rant or two.
You finish by stating that you are "only interested in helping OP". Hmmm. quite a bit of time spent with the above leads one to a quite different view.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
But I still kinda consider myself a relative 'noobie' since I haven't used Linux for a few months and forgot a few things. So I might need to be reminded of the obvious now and then. 
