| View previous topic :: View next topic |
| Author |
Message |
Awox
n00b
Joined: 19 Nov 2003
Posts: 32
Location: North coast of NSW, Australia
|
 Posted: Tue May 18, 2004 2:34 pm Post subject: lm-sensors detect but do not work! |
 |
|
Hello, I run sensors-detect and it finds a suitable configuration. I tried both ISA and smbus modes and made sure to overwrite my /etc/conf.d/lm_sensors!
sensors-detect:
| Quote: |
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83781d' (should be inserted):
Detects correctly:
* Bus `SMBus AMD756 adapter at 5500' (Algorithm unavailable)
Busdriver `i2c-amd756', I2C address 0x2d (and 0x48 0x49)
Chip `Asus AS99127F (rev.1)' (confidence: 
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)?
|
I choose both ISA and smbus and overwrite.. I still get the following when I run sensors:
| Quote: |
as99127f-i2c-2-2d
Adapter: SMBus AMD756 adapter at 5500
Algorithm: Unavailable from sysfs
ERROR: Can't get IN0 data!
ERROR: Can't get IN1 data!
ERROR: Can't get IN2 data!
ERROR: Can't get IN3 data!
ERROR: Can't get IN4 data!
ERROR: Can't get IN5 data!
ERROR: Can't get IN6 data!
ERROR: Can't get FAN1 data!
ERROR: Can't get FAN2 data!
ERROR: Can't get FAN3 data!
ERROR: Can't get TEMP1 data!
ERROR: Can't get TEMP2 data!
ERROR: Can't get TEMP3 data!
ERROR: Can't get VID data!
alarms:
beep_enable:
Sound alarm enabled
|
| Quote: |
Module Size Used by
w83781d 33088 0
i2c_amd756 4804 0
i2c_algo_pcf 5764 0
i2c_sensor 2368 1 w83781d
i2c_dev 8576 0
i2c_core 18948 5 w83781d,i2c_amd756,i2c_algo_pcf,i2c_sensor,i2c_dev
snd_seq_midi 6496 0
snd_emu10k1_synth 6784 0
snd_emux_synth 33216 1 snd_emu10k1_synth
snd_seq_virmidi 5824 1 snd_emux_synth
snd_seq_midi_event 6272 2 snd_seq_midi,snd_seq_virmidi
snd_seq_midi_emul 6848 1 snd_emux_synth
snd_seq 53200 5 snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_event,snd_seq_midi_emul
snd_emu10k1 92612 2 snd_emu10k1_synth
snd_rawmidi 20896 3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1
snd_seq_device 6792 5 snd_seq_midi,snd_emu10k1_synth,snd_seq,snd_emu10k1,snd_rawmidi
snd_ac97_codec 60932 1 snd_emu10k1
snd_util_mem 3392 2 snd_emux_synth,snd_emu10k1
snd_hwdep 7556 2 snd_emux_synth,snd_emu10k1
snd_pcm_oss 49828 0
snd_pcm 86536 2 snd_emu10k1,snd_pcm_oss
snd_page_alloc 8964 2 snd_emu10k1,snd_pcm
snd_timer 22340 2 snd_seq,snd_pcm
snd_mixer_oss 17920 2 snd_pcm_oss
snd 48100 15 snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_event,snd_seq,snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_util_mem,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 7328 2 snd
vfat 12480 0
fat 40960 1 vfat
fglrx 207012 7
e100 28928 0
|
This is really annoying, any help would be much apreciated! At one stage (before udev) I could get some temps! Thanks for any assistance. |
|
| Back to top |
|
 |
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4983
Location: Gothenburg, Sweden
|
|
| Back to top |
|
|
Awox
n00b
Joined: 19 Nov 2003
Posts: 32
Location: North coast of NSW, Australia
|
| Posted: Tue May 18, 2004 2:57 pm Post subject: |
|
|
How silly of me to forget!
Kernel: 2.6.5-gentoo-r1
lm-sensors: 2.8.2 |
|
| Back to top |
|
|
appetitus
Apprentice
Joined: 28 Sep 2003
Posts: 210
|
| Posted: Thu May 20, 2004 1:51 am Post subject: |
|
|
Don't hold your breath.
At least you get some response from "sensors", I get 'no sensors found'. Kernel 2.6.6-mm4 and latest lm-sensors (I read their website, ebuild seems totally out of it).
Once again, gentoo cannot pass 4th grade.
No wonder the founder left abruptly.
_________________
Being a Gentoo user means living in a house inhabited by a family of crazed carpenters. When you wake up, the house is different. Maybe there is a new turret, or some walls have moved, or perhaps someone has removed the floor under your bed. |
|
| Back to top |
|
|
Admiral LSD
Guru
Joined: 27 Jun 2003
Posts: 522
Location: Northam, W.A., Australia
|
| Posted: Thu May 20, 2004 7:22 am Post subject: |
|
|
I don't think it's entirely fair to pin this all on Gentoo. Part of of the problem is over-zealous kernel developers making major changes to things and then leaving both users and developers of other projects to clean up the mess afterwards.
Try upgrading to a later version of the lm-sensors userspace package. You have to do a bit of unusual hacking in order to do this though as some issues on amd64 have forced them to mask the packages in a fairly boneheaded way. Essentially you want to put this:
| Code: | | sys-apps/lm-sensors -x86 |
into your /etc/portage/package.keywords file. That'll net you access to the latest versions of lm-sensors which may contain a fix for your problem.
Apparently they're moving to a standardised sensor API which should help alleviate this somewhat but I'd take that with a grain of salt as "standardise" in Linux terms usually means "works until the next kernel release".
_________________
Wasurenaide...
...watashi ga iru koto o.
Itsudatte soba ni iru yo.
Registered Linux user #319839 |
|
| Back to top |
|
|
Majeeks
n00b
Joined: 22 Feb 2003
Posts: 5
|
| Posted: Tue Jun 29, 2004 10:17 am Post subject: |
|
|
Had same problem, with lm-sensors 2.8.6 it disapeared. Thank you.
Linux 2.6.7-rc3-love2 |
|
| Back to top |
|
|
-Craig-
Guru
Joined: 03 Jun 2004
Posts: 333
|
| Posted: Tue Jun 29, 2004 10:59 am Post subject: |
|
|
I also had trouble with an older version (lm-sensors-2.8.1), with 2.8.6 they vanished!
The strange thing is that I just emerged lm-sensors, and lm-sensors-2.8.1 was installed, though an ebuild for 2.8.6 is in the correct directory!
Does anyone know why? |
|
| Back to top |
|
|
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4983
Location: Gothenburg, Sweden
|
| Posted: Tue Jun 29, 2004 8:10 pm Post subject: |
|
|
That's how portage works. It chooses version based on the KEYWORDS in the ebuild and your ACCEPT_KEYWORDS as well as any corresponding entry in /etc/portage/package.keywords. Any of the two latter must match the keyword defined in the ebuild for portage to choose that version.
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat |
|
| Back to top |
|
|
-Craig-
Guru
Joined: 03 Jun 2004
Posts: 333
|
| Posted: Wed Jun 30, 2004 1:10 pm Post subject: |
|
|
I am in the unstable tree and thought, that always the newest packages are use...well ok, thanks for the info!  |
|
| Back to top |
|
|
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4983
Location: Gothenburg, Sweden
|
| Posted: Wed Jun 30, 2004 1:26 pm Post subject: |
|
|
Yes, but in this case the keyword is actually 'minus x86' which normally means broken for x86 and not 'tilde x86', that is, unstable or testing, rather.
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
