LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Mandriva
User Name
Password
Mandriva This Forum is for the discussion of Mandriva (Mandrake) Linux.

Notices


Reply
  Search this Thread
Old 10-10-2004, 09:57 PM   #16
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46

Nah he has an 801 see prior post.
 
Old 10-10-2004, 10:05 PM   #17
estatik
Member
 
Registered: Oct 2003
Location: CA / NY
Distribution: Mandrake 9.1, 9.2, 10.1, Cooker
Posts: 145

Rep: Reputation: 15
Quote:
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.

Last edited by estatik; 10-10-2004 at 10:07 PM.
 
Old 10-10-2004, 10:33 PM   #18
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46
"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.

Last edited by opjose; 10-10-2004 at 10:35 PM.
 
Old 10-11-2004, 12:10 AM   #19
estatik
Member
 
Registered: Oct 2003
Location: CA / NY
Distribution: Mandrake 9.1, 9.2, 10.1, Cooker
Posts: 145

Rep: Reputation: 15
Obviously, your reply speaks for itself.

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.
 
Old 10-11-2004, 02:05 AM   #20
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46
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.
 
Old 10-11-2004, 04:08 AM   #21
mdg
Member
 
Registered: Sep 2003
Distribution: Slackware
Posts: 626

Rep: Reputation: 38
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
 
Old 10-11-2004, 04:17 PM   #22
RavenLX
Member
 
Registered: Oct 2004
Posts: 98

Original Poster
Rep: Reputation: 15
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.
 
Old 10-11-2004, 04:28 PM   #23
RavenLX
Member
 
Registered: Oct 2004
Posts: 98

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by mdg
Also, post the results of lsmod so we can see what's running and what's not [/B]
Here is is:
Code:
Module                  Size  Used by
binfmt_misc             9960  1
md5                     3872  1
ipv6                  232352  10
sg                     38044  0
sr_mod                 17028  0
autofs4                14656  2
parport_pc             32832  1
lp                     12200  0
parport                38952  2 parport_pc,lp
snd-seq-oss            31232  0
snd-seq-midi-event      7552  1 snd-seq-oss
snd-seq                51024  4 snd-seq-oss,snd-seq-midi-event
snd-pcm-oss            51812  0
snd-mixer-oss          17952  1 snd-pcm-oss
snd-intel8x0           32776  1
snd-ac97-codec         58148  1 snd-intel8x0
snd-pcm                93156  2 snd-pcm-oss,snd-intel8x0
snd-timer              24484  2 snd-seq,snd-pcm
gameport                4480  1 snd-intel8x0
snd-page-alloc         11972  2 snd-intel8x0,snd-pcm
snd-mpu401-uart         7072  1 snd-intel8x0
snd-rawmidi            23616  1 snd-mpu401-uart
snd-seq-device          8008  3 snd-seq-oss,snd-seq,snd-rawmidi
snd                    52484  14 snd-seq-oss,snd-seq-midi-event,snd-seq,snd-pcm-oss,snd-mixer-oss,
                                 snd-intel8x0, snd-ac97-codec,snd-pcm,snd-timer,snd-mpu401-uart,
                                 snd-rawmidi,snd-seq-device
soundcore               9248  1 snd
af_packet              20520  2
raw                     7616  1
ide-floppy             18752  0
ide-tape               34864  0
ide-cd                 40548  0
cdrom                  37184  2 sr_mod,ide-cd
floppy                 59444  0
b44                    21284  0
nls_iso8859-1           3904  2
nls_cp850               4736  2
vfat                   13760  2
fat                    45120  1 vfat
supermount             37876  1
eeprom                  7336  0
i2c-sensor              2944  1 eeprom
i2c-isa                 1824  0
i2c-i801                7856  0
i2c-core               23044  4 eeprom,i2c-sensor,i2c-isa,i2c-i801
intel-agp              17372  1
agpgart                31016  1 intel-agp
usblp                  12288  0
acecad                  4640  0
usbmouse                5216  0
ehci-hcd               24196  0
hid                    53312  0
uhci-hcd               29104  0
usbcore                99132  8 usblp,acecad,usbmouse,ehci-hcd,hid,uhci-hcd
rtc                    11576  0
ext3                  110408  3
jbd                    54328  1 ext3
sd_mod                 16608  0
ata_piix                7844  0
libata                 38912  1 ata_piix,[permanent]
scsi_mod              114008  4 sg,sr_mod,sd_mod,libata
 
Old 10-11-2004, 04:32 PM   #24
RavenLX
Member
 
Registered: Oct 2004
Posts: 98

Original Poster
Rep: Reputation: 15
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:

#I2C adapter drivers
modprobe i2c-i801
modprobe i2c-isa
#I2C chip drivers
modprobe eeprom
modprobe w83731d
#sleep 2 #optional
#/usr/bin/sensors -s # recommended

Last edited by RavenLX; 10-11-2004 at 04:35 PM.
 
Old 10-11-2004, 04:40 PM   #25
RavenLX
Member
 
Registered: Oct 2004
Posts: 98

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by opjose
Eh, you should have no trouble with the 801 chipset.

It's working fine on one of my boxes.

modprobe i2c-i801

and make sure that the i2c drivers are detected and loaded.

Rerun sensors, etc.

You may want to also re-run sensors-detect and choose the i2c bus.

I've done this and still doesn't work. In fact, that was in one of the sets of instructions I tried.
 
Old 10-11-2004, 05:10 PM   #26
RavenLX
Member
 
Registered: Oct 2004
Posts: 98

Original Poster
Rep: Reputation: 15
Ok, last one...

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:

eeprom-i2c-0-51
Adapter: SMBus I801 adapter at 0500
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 0500
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

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?
 
Old 10-12-2004, 01:33 AM   #27
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46
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.

You may have to wait on this unfortunately.
 
Old 10-12-2004, 08:07 AM   #28
mdg
Member
 
Registered: Sep 2003
Distribution: Slackware
Posts: 626

Rep: Reputation: 38
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.
 
Old 10-12-2004, 12:40 PM   #29
estatik
Member
 
Registered: Oct 2003
Location: CA / NY
Distribution: Mandrake 9.1, 9.2, 10.1, Cooker
Posts: 145

Rep: Reputation: 15
@ 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.
Code:
[root@dragon root]# lsmod
Module                  Size  Used by
i2c-dev                 7616  0
ipx                    23788  0
n_hdlc                  7972  1
ppp_synctty             7744  1
md5                     3584  1
ipv6                  230916  1389
snd-pcm-oss            49480  0
snd-mixer-oss          17376  3 snd-pcm-oss
snd-cmipci             28228  2
snd-pcm                81800  2 snd-pcm-oss,snd-cmipci
snd-page-alloc          7400  1 snd-pcm
snd-opl3-lib            8448  1 snd-cmipci
snd-timer              20356  2 snd-pcm,snd-opl3-lib
snd-hwdep               6916  1 snd-opl3-lib
gameport                3328  1 snd-cmipci
snd-mpu401-uart         5856  1 snd-cmipci
snd-rawmidi            19300  1 snd-mpu401-uart
snd-seq-device          6344  2 snd-opl3-lib,snd-rawmidi
snd                    45988  10 snd-pcm-oss,snd-mixer-oss,snd-cmipci,snd-pcm,snd-opl3-lib,snd-timer,snd-hwdep,snd-mpu401-uart,snd-rawmidi,snd-seq-device
soundcore               7008  3 snd
ppp_async               8896  0
ppp_generic            24468  6 ppp_synctty,ppp_async
slhc                    6112  1 ppp_generic
crc-ccitt               1664  1 ppp_async
ipt_state               1408  34
ipt_REJECT              5536  4
ipt_limit               1760  6
ipt_LOG                 5568  6
ip_conntrack_ftp       71120  0
ip_conntrack           28616  2 ipt_state,ip_conntrack_ftp
iptable_filter          2080  1
ip_tables              14624  5 ipt_state,ipt_REJECT,ipt_limit,ipt_LOG,iptable_filter
af_packet              16072  4
floppy                 55088  0
8139too                20928  0
mii                     4224  1 8139too
ide-cd                 37280  0
cdrom                  37724  1 ide-cd
loop                   12520  0
supermount             34804  2
w83627hf               27908  0
eeprom                  6248  0
i2c-sensor              2240  2 w83627hf,eeprom
i2c-isa                 1600  0
i2c-viapro              5900  0
i2c-core               19060  6 i2c-dev,w83627hf,eeprom,i2c-sensor,i2c-isa,i2c-viapro
via-agp                 7360  1
agpgart                27752  2 via-agp
nvidia               4814228  12
ehci-hcd               26244  0
uhci-hcd               28752  0
usbcore               103172  4 ehci-hcd,uhci-hcd
reiserfs              258324  10
@ 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.
 
Old 10-12-2004, 01:40 PM   #30
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46
Let's see:

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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
lm_sensors not working Ephracis Linux - Hardware 0 10-22-2004 12:16 PM
lm_sensors not working. No sensors found! Kramer Linux - Hardware 36 10-15-2004 01:51 PM
Does ANYONE have lm_sensors working with an A7N8X? CanadianPenguin Linux - Software 2 05-11-2004 06:26 PM
lm_sensors not working?? nuzzy Slackware 1 09-15-2003 06:09 PM
lm_sensors...anyone got it working with Mandrake 9.0? discipledoc Linux - Software 3 01-20-2003 12:49 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Mandriva

All times are GMT -5. The time now is 03:18 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration