[LINUX] My Asrock 330 ION Tweaks, Tips, Tricks, and Fixes!

[LINUX] My Asrock 330 ION Tweaks, Tips, Tricks, and Fixes! - Printable Version

+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Announcements, Info, and General Discussion (/forumdisplay.php?fid=85)
+--- Forum: Tips, tricks, and step by step guides (/forumdisplay.php?fid=110)
+--- Thread: [LINUX] My Asrock 330 ION Tweaks, Tips, Tricks, and Fixes! (/showthread.php?tid=61697)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

- monty0815 - 2010-02-05 00:59

@BoyBastos
Try this

Code:

sudo modprobe w83627ehf force_id=0xa510

and then have a look what

Code:

sensors

has to say about it.

thanks monty - BoyBastos - 2010-02-05 01:02

monty0815 Wrote:@BoyBastos
I meant after installing it like this:

Code:

sudo apt-get install lm-sensors
then run:

Code:

sudo sensors-detect
Say "yes" to everything, and see if the program finds anything.

regards,
monty

monty0815 Wrote:@BoyBastos
Try this

Code:

sudo modprobe w83627ehf force_id=0xa510
and then have a look what

Code:

sensors
has to say about it.

jeff@xbmc:~$ sudo modprobe w83627ehf force_id=0xa510
jeff@xbmc:~$ sensors
w83667hg-isa-fff8
Adapter: ISA adapter
in0: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
in1: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
in2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
in3: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
in4: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
in5: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
in6: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
in7: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
in8: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 128) ALARM
fan2: 0 RPM (min = 0 RPM, div = 128) ALARM
fan3: 0 RPM (min = 0 RPM, div = 128) ALARM
fan4: 0 RPM (min = 0 RPM, div = 128) ALARM
temp1: -1.0°C (high = -1.0°C, hyst = -1.0°C) ALARM sensor = diode
temp2: +0.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = diode
cpu0_vid: +0.000 V

hehe thanks mate but i think its off hehe Smile

PS i followed everything on the first 2 posts but unfortunately am stuck after running sensors-detect as there was no sensors detected Sad

any suggestions?

Am using foxconn nt330i netbook with full ubuntu karmic 9.10 install and xbmc full. running Linux xbmc 2.6.31-17-generic

- monty0815 - 2010-02-05 01:07

I now have serious doubts, that you have the same sensors as the ASRock 330....

- BoyBastos - 2010-02-05 01:10

well thanks alot monty i have been trying this lm-sensors thing wouldnt seem to work. on the lm-sensors page if i use the pyton sensors-detect i get a chip but it doesnt output any file tho Sad

- monty0815 - 2010-02-05 01:17

You mentioned a screenlet, that was capable of displaying the temperatures, did that run under linux? if yes, could you post a link, i'd like to have a look at it.

regards,
monty

- BoyBastos - 2010-02-05 01:23

monty: if i use the pyton sesors-detect on lm-sensors page i get this after running sensors-detect:

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

Driver `coretemp':
* Chip `Intel Atom thermal sensor' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

As for the screenleet i use it is this:

http://www.screenlets.org/index.php/WaterMark or try this http://www.gnome-look.org/content/show.php?content=71960&forumpage=0

when i config it from the drop down i use GPU core temp that is the only thing it detects automatically.

hope this helps

- monty0815 - 2010-02-05 01:49

BoyBastos Wrote:You should now start the lm_sensors service to load the required
kernel modules.

That would probably be "sudo /etc/init.d/lm-sensors start". Did you do that?

Thanks for the links.

- BoyBastos - 2010-02-05 01:55

monty0815 Wrote:That would probably be "sudo /etc/init.d/lm-sensors start". Did you do that?

Thanks for the links.

yea i did but its way off hehe same as the one u told me :

w83667hg-isa-fff8
Adapter: ISA adapter
in0: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
in1: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
in2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
in3: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
in4: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
in5: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
in6: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
in7: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
in8: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 128) ALARM
fan2: 0 RPM (min = 0 RPM, div = 128) ALARM
fan3: 0 RPM (min = 0 RPM, div = 128) ALARM
fan4: 0 RPM (min = 0 RPM, div = 128) ALARM
temp1: -1.0°C (high = -1.0°C, hyst = -1.0°C) ALARM sensor = diode
temp2: +0.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = diode
cpu0_vid: +0.000 V

- X3lectric - 2010-02-05 02:29

His chip results on sensors as w83667hg-isa-fff8
Mine isw83667hg-isa-0290

Because the mobos are laid out different it could be his chip ID to His an Foxconn Ion is at a different address to which is being forced....

Would have to have a look at his

Code:

sensors-detect

output and also the result of

Code:

cat /proc/ioports

to see if this is correct though to get the correct id to be forced can only be extracted from what file is found here

on another note I have notice my system reported a fan working at 8823rpm

Today it reports nothing.... Sad

Im wondering how much of this other driver is actually correct for a completely different however similar in what they do chip.

Also if it was as simple as this I have to ask why is it that lm-sensors project hasn't already modified the driver and has it released and working Confused

I mean they know this backwards...

http://lists.lm-sensors.org/pipermail/lm-sensors/2009-November/027193.html

That link is tied to the request for the diver and lm-sensors as on compat list near bottom on the post below....

http://www.lm-sensors.org/wiki/Devices

This is all a biiiig maybe maybe either way atm

Code:

sensors-detect

output and also the result of

Code:

cat /proc/ioports