[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

- X3lectric - 2010-02-01 11:11

I would if I had them perhaps a quick email to Asrock? The ones I have on system are the 9.10 version with lirc 0.8.6 sry Sad

- andyblac - 2010-02-01 17:37

i could not get Karmic sersors to work with your instructons, i have modifies it so it does heres mine

Code:

apt-get install lm-sensors linux-source build-essential -y --force-yescd /usr/src

wget [url]http://mabene.icomedias.com/coretemp.patch[/url]

tar jxvf linux-source-$(uname -r | awk -F'-' '{print $1}').tar.bz2 

cd linux-source-$(uname -r | awk -F'-' '{print $1}') 

patch -p1 < ../coretemp.patch | tee -a ~/setup/xbmc-live-configure.log

make -j 4 -C /lib/modules/[color=red]2.6.31-17-generic[/color]/build M=/usr/src/linux-source-$(uname -r | awk -F'-' '{print $1}')/drivers/hwmon/ modules

cp /usr/src/linux-source-$(uname -r | awk -F'-' '{print $1}')/drivers/hwmon/coretemp.ko /lib/modules/[color=red]2.6.31-17-generic[/color]/kernel/drivers/hwmon/coretemp.ko

cd /usr/sbin/

rm /usr/sbin/sensors-detect

wget [url]http://bit.ly/5ta8Z6[/url] 

chmod 755 /usr/sbin/sensors-detect

Please answer YES (Y/y) to ALL!!

PHP Code:

sensors-detect
echo coretemp >> /etc/modules
modprobe coretemp
service lm-sensors start
sensors -s 

- X3lectric - 2010-02-01 18:00

_ml_ Wrote:X3lectric: Im running a x64 kernel, could this be the problem?

Runing sudo dpkg -i lirc-nct677x-x64-1.0.1-ubuntu9.10.deb

give this output:

Code:

(Reading database ... 51926 files and directories currently installed.) Preparing to replace lirc-nct677x-x64 1.0.1-ubuntu9.10 (using lirc-nct677x-x64-1 .0.1-ubuntu9.10.deb) ... * Stopping execution daemon: irexec [fail] ERROR: Module lirc_wb677 does not exist in /proc/modules patching file /usr/share/lirc/lirc.hwdb Reconfigure lirc * Stopping execution daemon: irexec [fail] * Reloading kernel event manager... [ OK ] * Starting execution daemon: irexec [fail] Unpacking replacement lirc-nct677x-x64 ... Setting up lirc-nct677x-x64 (1.0.1-ubuntu9.10) ... Copy patch file... * Stopping execution daemon: irexec [fail] `/usr/share/lirc_wb677/lirc_wb677.ko' -> `/lib/modules/2.6.28-17-generic/kernel/ ubuntu/lirc/lirc_wb677/lirc_wb677.ko' /etc/lirc/lircrc existed. append it. patching file /usr/share/lirc/lirc.hwdb * Stopping execution daemon: irexec [fail] * Reloading kernel event manager... [ OK ] * Starting execution daemon: irexec [fail]
Only thing I found out from this output is that the lirc_wb677 module is not loaded correct.

Maybe I need to compile the module from src. Just have to figure out how dkms works first.

This is what happens on my system and it installs perfectly.

Code:

* Stopping execution daemon: irexec                                     [fail]

 * Stopping remote control daemon(s): LIRC                               [ OK ]

patching file /usr/share/lirc/lirc.hwdb

Reconfigure lirc

 * Stopping execution daemon: irexec                                     [fail]

 * Stopping remote control daemon(s): LIRC                               [fail]

 * Starting execution daemon: irexec                                     [fail]

Unpacking replacement lirc-nct677x ...

Setting up lirc-nct677x (1.0.4-ubuntu9.10) ...

Copy patch file...

 * Stopping execution daemon: irexec                                     [fail]

`/usr/share/lirc_wb677/lirc_wb677.ko' -> `/lib/modules/2.6.31-17-generic/kernel/ubuntu/lirc/lirc_wb677/lirc_wb677.ko'

/etc/lirc/lircrc existed. append it.

patching file /usr/share/lirc/lirc.hwdb

 * Stopping execution daemon: irexec                                     [fail]

 * Loading LIRC modules                                                  [ OK ]

 * Starting remote control daemon(s) : LIRC                              [ OK ]

 * Starting execution daemon: irexec                                     [ OK ]

On the first run its a lirc reconfigure it doesn't matter cause we are choosing none second run when you get prompted again and pick relevant driver Nuvoton Remotes and transceivers the driver is loaded and irexec doesn't really need to stop to load a driver just restarted; lirc on the other hand does and that gets stopped and restarted ok as you can see the whole process including the irexec is restarted ok it just reports you didn't stop it... even 64bit the output has to be like what I posted everything being right and all

Im sure you can if you or anybody else really want to kill the irexec Im sure it is possible if your having problems with driver install... old post but only noticed it now Sad

- speed32219 - 2010-02-02 00:07

X3lectric,

"patch -p1 < ../coretemp.patch
make -j 4 -C /lib/modules/2.6.31-17-generic/build M=/usr/src/linux-source-$(uname -r | awk -F'-' '{print $1}')/drivers/hwmon/ modules
echo coretemp.ko >> /etc/modules" "

What is that last line in the setting up lm-sensors?

Also, I'm getting some warnings during the make process.

Quote: make: Entering directory `/usr/src/linux-headers-2.6.31-15-generic'
CC [M] /usr/src/linux-source-2.6.31/drivers/hwmon/coretemp.o
Building modules, stage 2.
MODPOST 80 modules
WARNING: modpost: Found 10 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
LD [M] /usr/src/linux-source-2.6.31/drivers/hwmon/coretemp.ko
make: Leaving directory `/usr/src/linux-headers-2.6.31-15-generic'

- andyblac - 2010-02-02 01:10

speed32219 Wrote:X3lectric,

"patch -p1 < ../coretemp.patch
make -j 4 -C /lib/modules/2.6.31-17-generic/build M=/usr/src/linux-source-$(uname -r | awk -F'-' '{print $1}')/drivers/hwmon/ modules
echo coretemp.ko >> /etc/modules" "

What is that last line in the setting up lm-sensors?

Also, I'm getting some warnings during the make process.

Quote: make: Entering directory `/usr/src/linux-headers-2.6.31-15-generic'
CC [M] /usr/src/linux-source-2.6.31/drivers/hwmon/coretemp.o
Building modules, stage 2.
MODPOST 80 modules
WARNING: modpost: Found 10 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
LD [M] /usr/src/linux-source-2.6.31/drivers/hwmon/coretemp.ko
make: Leaving directory `/usr/src/linux-headers-2.6.31-15-generic'

please READ his post,

you HAVE NOT made the required change your trying to build against kernel 2.6.31.17 but you have 2.6.31.15 installed.

you did

"make -j 4 -C /lib/modules/2.6.31-17-generic......"

you need to either update your kernel or change it in the make line.

try this :

make -j 4 -C /lib/modules/2.6.31-15-generic/build M=/usr/src/linux-source-$(uname -r | awk -F'-' '{print $1}')/drivers/hwmon/ modules

- speed32219 - 2010-02-02 03:03

Andyblac, I went back and redid everything. Except I followed your procedure below and I now have sensors working. Smile

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +9.0°C (crit = +95.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +21.0°C (crit = +95.0°C)

coretemp-isa-0002
Adapter: ISA adapter
Core 2: +9.0°C (crit = +95.0°C)

coretemp-isa-0003
Adapter: ISA adapter
Core 3: +21.0°C (crit = +95.0°C)

I am running a Zotac ION 330.

Thank you to all the posters. I am a Happy camper.

- andyblac - 2010-02-02 03:45

speed32219 Wrote:Andyblac, I went back and redid everything. Except I followed your procedure below and I now have sensors working.

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +9.0°C (crit = +95.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +21.0°C (crit = +95.0°C)

coretemp-isa-0002
Adapter: ISA adapter
Core 2: +9.0°C (crit = +95.0°C)

coretemp-isa-0003
Adapter: ISA adapter
Core 3: +21.0°C (crit = +95.0°C)

I am running a Zotac ION 330.

Thank you to all the posters. I am a Happy camper.

glad you got it working, dont forget to add the required info to your advancedsettings.xml file Smile

, so they show in XBMC

- andyblac - 2010-02-02 06:02

BTW got hddtemp working as none root Smile

Code:

sudo chmod u+s /usr/sbin/hddtemp

test by typing this in terminal:

Code:

hddtemp -n /dev/sda

and this should work in XBMC advanceedsettings.xml (when they add support)

Code:

<hddtempcommand>echo "$(hddtemp -n /dev/sda) C"</hddtempcommand>

- monty0815 - 2010-02-02 11:14

speed32219 Wrote:coretemp-isa-0000
Adapter: ISA adapter
Core 0: +9.0°C (crit = +95.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +21.0°C (crit = +95.0°C)

coretemp-isa-0002
Adapter: ISA adapter
Core 2: +9.0°C (crit = +95.0°C)

coretemp-isa-0003
Adapter: ISA adapter
Core 3: +21.0°C (crit = +95.0°C)

I'm running an asrock 330HT and get similar readings. However these temperatures seem very wrong, far too low. After heavy load I get about 30°C with lm_sensors, but after a reboot the bios values differ greatly.
Any ideas?

regards,
monty

- X3lectric - 2010-02-02 12:03

andyblac Wrote:BTW got hddtemp working as none root

Code:

sudo chmod u+s /usr/sbin/hddtemp
test by typing this in terminal:

Code:

hddtemp -n /dev/sda
and this should work in XBMC advanceedsettings.xml (when they add support)

Code:

<hddtempcommand>echo "$(hddtemp -n /dev/sda) C"</hddtempcommand>

nice nice nice, that's my thoughts exactly when support is added now I cant remember at all if I made a request or no...

@ monty0815

such massive discrepancy between bios temps and what is show is not a good sign. I blame it on both lack of proper compiled kernels with the drivers each system needs and shite HW revisions mainly the automatic voltage regulator and total lack of all ION-HT hardware (and other ION platforms) in Linux mainly cause manufacturers are prolly being paid off to support windows preferentially over Linux (so you end up buying a MS OS). Just as a Curiosity Asrock, Zotac and anyone else providing ION platforms are NOT the ones who are licensed to manufacture them, to best my knowledge the company who is sole licensee to build whatever ION platforms is Pegatron Corp. this can be easily seen on the similar components being used (exact versions same chips) & the ION 330 actually advertises it in retail box.

Now imagine this; middle man (manufacturer or system assembler only in this case Pegatron), middle man (Company who name is silkscreened on mobo or company offering product), middle man (Nuvoton and others (e.g. AMI for Bios) who are driver providers for their chips) middle man (retailer) finally ---- you.

your temps along with everyone who has a ION based system will only display correct temperatures when various issues with IO port probing gets resolved at kernel level. ATM what happens is that for some components the IO ports being called by acpi and hwmon at same time this not only accounts for some of the discrepancy it also can cause hw malfunctions. however sensor readings can be improved slightly by using a better sensors-detect file. (you can get the svn lm-sensors nightly build and get the file) Only needs renaming existing and chmod +755 filename on new one before it can be used and of course run the sensors-detect again.

maybe be worth mentioning that the IO ports issue while reported fixed in 2.6.30 only kernels and the issue is still present in current kernels. and worst many drivers have not been ported to the new kernels hence why we having to compile coretemp.ko and others which is a pita. this info is all available on lm-sensors page if it loads at all..... I have downloaded the latest sensors-detect and host it here http://www.mediafire.com/X301 in case lm-sensors webpage does not load for you.

BTW Pegatron Corp assemble all their shit in china. We all know what the track record for products made in china is...