Re: fan control on thecus n2100
Frank A. Kingswood wrote: Martin Michlmayr wrote: * Gaudenz Steinlin [EMAIL PROTECTED] [2008-01-09 11:27]: How can I set the fan speed manually now and how do I enable automatic fan control (if possible)? I don't know which tools to use to control it automatically, but here are instructions for manual use: By default, the fan should run at full speed. If you need to regulate the speed, you need to locate the pwm files in /sys: find /sys/ | grep pwm /sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e/pwm2 /sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e/pwm1 If you want to stop the fan, you have to write the value zero to these files: echo 0 /sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e/pwm2 echo 0 /sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e/pwm1 You can activate full speed using the following commands: echo 255 /sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e/pwm1 echo 255 /sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e/pwm2 See http://www.debonaras.org/wiki/Info/N2100FanControl for a shell script that regulates the fan by reading system and disk temperatures. Fan control has only a very small control range, and the script needs to be tuned for that, but when that is done it works just fine. I've had a play with the script and found: a) In the example /etc/init.d/temper stopping the daemon only does: echo 255 /sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e/pwm2 which doesn't return the fan to full speed! You need to do echo 255 /sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e/pwm2 as well I think, can somebody confirm this? b) In /usr/local/sbin/temper the calculation R=$((150/$(cat $SPEED))) for fan RPM seems to be rubbish, as $SPEED rises the reported RPM falls! regards, Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Ethernet n.: something used to catch the etherbunny. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
octave3.0 crashes on startup
Hi,
we need some help. octave3.0 crashes on startup on ARM (#458852).
I attach a backtrace, provided by Soeren Sonnenburg (it's also in the
BTS).
=
OK, I've recompiled octave w/ -O2 -g and it dies on loading
dispatch.oct. This could be enough info for upstream to fix it.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x40022490 (LWP 11491)]
0x40db4890 in octave_shlib::make_shlib ()
from /usr/lib/octave-3.0.0/liboctave.so
(gdb) bt
#0 0x40db4890 in octave_shlib::make_shlib ()
from /usr/lib/octave-3.0.0/liboctave.so
#1 0x401f7584 in octave_dynamic_loader::do_load_oct (
this=value optimized out, [EMAIL PROTECTED], [EMAIL PROTECTED],
relative=false) at ../liboctave/oct-shlib.h:52
#2 0x401f7f54 in octave_dynamic_loader::load_oct ([EMAIL PROTECTED],
[EMAIL PROTECTED], relative=false) at dynamic-ld.cc:508
#3 0x40469150 in load_fcn_from_file ([EMAIL PROTECTED], exec_script=true)
at parse.y:3440
#4 0x40469878 in load_fcn_from_file (sym_rec=0xf71658, exec_script=true)
at parse.y:3480
#5 0x40519554 in lookup (sym_rec=0xf71658, exec_script=true)
at variables.cc:
#6 0x408021e4 in tree_identifier::do_lookup (this=0xf6fe38,
[EMAIL PROTECTED], exec_script=true) at pt-id.cc:110
#7 0x408038e0 in tree_identifier::rvalue (this=0xf6fe38, nargout=1)
at pt-id.cc:161
#8 0x408024c4 in tree_identifier::rvalue (this=0xbedd5450) at pt-id.cc:204
#9 0x4080b72c in tree_index_expression::rvalue (this=0xf71958, nargout=0)
at pt-idx.cc:279
#10 0x4083db18 in tree_statement::eval (this=0xf6f080, silent=false,
nargout=0, in_function_body=false) at pt-stmt.cc:133
#11 0x4083e50c in tree_statement_list::eval (this=0xf66428, silent=false,
---Type return to continue, or q return to quit---
nargout=0) at pt-stmt.cc:190
#12 0x404672e8 in parse_and_execute (f=0xf60620) at parse.y:2864
#13 0x40467c68 in parse_fcn_file ([EMAIL PROTECTED], exec_script=true,
force_script=true) at parse.y:3336
#14 0x40468308 in source_file ([EMAIL PROTECTED], [EMAIL PROTECTED])
at parse.y:3613
#15 0x402eeac4 in execute_pkg_add_or_del ([EMAIL PROTECTED],
[EMAIL PROTECTED]) at load-path.cc:1232
#16 0x402eedd8 in execute_pkg_add ([EMAIL PROTECTED]) at load-path.cc:1240
#17 0x402f3960 in load_path::do_set (this=0xf38c80, [EMAIL PROTECTED],
warn=false)
at load-path.cc:454
#18 0x402f3c1c in load_path::do_initialize (this=0xf38c80,
set_initial_path=true) at load-path.cc:382
#19 0x404427b8 in octave_main (argc=1, argv=0xbedd6b14, embedded=0)
at load-path.h:51
#20 0x424de040 in __libc_start_main () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
(gdb) up 2
#2 0x401f7f54 in octave_dynamic_loader::load_oct ([EMAIL PROTECTED],
[EMAIL PROTECTED], relative=false) at dynamic-ld.cc:508
508 ? instance-do_load_oct (fcn_name, file_name, relative) : false;
Current language: auto; currently c++
(gdb) p fcn_name
$1 = (const string ) @0xbedd5664: {static npos = 4294967295,
_M_dataplus = {std::allocatorchar = {__gnu_cxx::new_allocatorchar =
{No data fields}, No data fields}, _M_p = 0xf662ec dispatch}}
(gdb) p file_name
$2 = (const string ) @0xbedd5660: {static npos = 4294967295,
_M_dataplus = {std::allocatorchar = {__gnu_cxx::new_allocatorchar =
{No data fields}, No data fields},
_M_p = 0xf7247c
/usr/lib/octave/3.0.0/oct/arm-unknown-linux-gnu/dispatch.oct}}
(gdb)
=
The main question is: is it a problem in Octave or something else?
Thanks
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fan control on thecus n2100
Colin Tuckley wrote: [snip] I've had a play with the script and found: a) In the example /etc/init.d/temper stopping the daemon only does: echo 255 /sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e/pwm2 which doesn't return the fan to full speed! You need to do echo 255 /sys/devices/platform/IOP3xx-I2C.0/i2c-0/0-002e/pwm2 as well I think, can somebody confirm this? Sorry - I can't see the difference between those two. Incidentally, I too have looked at that script. There are references to needing to work out a couple of values to suit your machine but no indication of what the values represent or how you would work them out. Can anyone provide more information? TIA, John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fan control on thecus n2100
John Winters wrote: Sorry - I can't see the difference between those two. Oops! Typo. You need to set both pwm1 and pwm2 to 255 to make the fan run at full speed I think - anyone confirm? The existing script only does one of them. Also, I've just noticed that it sets the fan to full speed *before* it kills the daemon, which is unsafe since the daemon might run again before it gets killed and leave you with a slow or stopped fan! Incidentally, I too have looked at that script. There are references to needing to work out a couple of values to suit your machine but no indication of what the values represent or how you would work them out. Can anyone provide more information? The values are the temp difference for fan control FAN_RNG - which I've left as 10 Degrees C and FAN_MIN which is the lowest fan speed control value to output when not either stopping the fan (0) or running it at full speed (255). I've currently got mine set to 60 rather than the provided 70. I suspect it depends on how many hard drives you have fitted (one in my case) and how good the airflow is in the box, with some of the ventilation mods from the Debonaires page you can probably use a lower value. The idea being that in the ideal case the fan would come on at it's slowest speed as the box initially warms up and stay there all the time rather than coming on too fast and then being cycled off and on again. regards, Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Ethernet n.: something used to catch the etherbunny. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrading kernel on a NSLU2
On Wed, Jan 09, 2008 at 07:32:33PM -0800, [EMAIL PROTECTED] wrote: HI Martin, Thanks for the confirmation, the upgrade did work but with some tiny effort... see the log below I had to install the specific version by using linux-image =version_number... == myslug:~/kernel# apt-get clean myslug:~/kernel# apt-get clean all myslug:~/kernel# apt-get update Get:1 http://natasha.stmarytx.edu etch Release.gpg [378B] Hit http://natasha.stmarytx.edu etch Release Get:2 http://security.debian.org etch/updates Release.gpg [189B] Get:3 http://www.backports.org etch-backports Release.gpg [189B] Get:4 http://security.debian.org etch/updates Release [22.5kB] Get:5 http://www.backports.org etch-backports Release [43.7kB] Ign http://natasha.stmarytx.edu etch/main Packages/DiffIndex Ign http://natasha.stmarytx.edu etch/main Sources/DiffIndex Hit http://natasha.stmarytx.edu etch/main Packages Hit http://natasha.stmarytx.edu etch/main Sources Ign http://security.debian.org etch/updates/main Packages/DiffIndex Ign http://security.debian.org etch/updates/main Sources/DiffIndex Get:6 http://security.debian.org etch/updates/main Packages [191kB] Hit http://www.backports.org etch-backports/main Packages/DiffIndex Hit http://www.backports.org etch-backports/contrib Packages/DiffIndex Hit http://www.backports.org etch-backports/non-free Packages/DiffIndex Get:7 http://www.backports.org etch-backports/contrib 2007-06-10-0940.10.pdiff [596B] Get:8 http://www.backports.org etch-backports/contrib 2007-06-10-0940.10.pdiff [596B] Get:9 http://www.backports.org etch-backports/contrib 2007-06-10-0940.10.pdiff [596B] Ign http://www.backports.org etch-backports/contrib 2007-06-10-0940.10.pdiff Get:10 http://security.debian.org etch/updates/main Sources [28.9kB] Hit http://www.backports.org etch-backports/contrib Fetched 287kB in 6s (45.6kB/s) Reading package lists... Done myslug:~/kernel# apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Calculating upgrade... Done The following packages will be upgraded: linux-image-2.6.18-4-ixp4xx 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 8851kB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? n Abort. myslug:~/kernel# man apt-get Reformatting apt-get(8), please wait... myslug:~/kernel# apt-get -f apt 0.6.46.4-0.1 for linux arm compiled on Feb 26 2007 22:44:23 Usage: apt-get [options] command apt-get [options] install|remove pkg1 [pkg2 ...] apt-get [options] source pkg1 [pkg2 ...] apt-get is a simple command line interface for downloading and installing packages. The most frequently used commands are update and install. Commands: update - Retrieve new lists of packages upgrade - Perform an upgrade install - Install new packages (pkg is libc6 not libc6.deb) remove - Remove packages source - Download source archives build-dep - Configure build-dependencies for source packages dist-upgrade - Distribution upgrade, see apt-get(8) dselect-upgrade - Follow dselect selections clean - Erase downloaded archive files autoclean - Erase old downloaded archive files check - Verify that there are no broken dependencies Options: -h This help text. -q Loggable output - no progress indicator -qq No output except for errors -d Download only - do NOT install or unpack archives -s No-act. Perform ordering simulation -y Assume Yes to all queries and do not prompt -f Attempt to continue if the integrity check fails -m Attempt to continue if archives are unlocatable -u Show a list of upgraded packages as well -b Build the source package after fetching it -V Show verbose version numbers -c=? Read this configuration file -o=? Set an arbitrary configuration option, eg -o dir::cache=/tmp See the apt-get(8), sources.list(5) and apt.conf(5) manual pages for more information and options. This APT has Super Cow Powers. myslug:~/kernel# apt-get -d dist-upgrade Reading package lists... Done Building dependency tree... Done Calculating upgrade... Done The following packages will be upgraded: linux-image-2.6.18-4-ixp4xx 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 8851kB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://security.debian.org etch/updates/main linux-image-2.6.18-4-ixp4xx 2.6.18.dfsg.1-12etch2 [8851kB] Fetched 8851kB in 24s (364kB/s) Download complete and in download only mode myslug:~/kernel# dpkg -l | grep linux ii foomatic-db 20061031-1 linuxprinting.org printer support - database ii foomatic-db-engine 3.0.2-20061031-1 linuxprinting.org
Re: fan control on thecus n2100
Colin Tuckley wrote: John Winters wrote: Incidentally, I too have looked at that script. There are references to needing to work out a couple of values to suit your machine but no indication of what the values represent or how you would work them out. Can anyone provide more information? The values are the temp difference for fan control FAN_RNG - which I've left as 10 Degrees C and FAN_MIN which is the lowest fan speed control value to output when not either stopping the fan (0) or running it at full speed (255). I've currently got mine set to 60 rather than the provided 70. I suspect it depends on how many hard drives you have fitted (one in my case) and how good the airflow is in the box, with some of the ventilation mods from the Debonaires page you can probably use a lower value. The idea being that in the ideal case the fan would come on at it's slowest speed as the box initially warms up and stay there all the time rather than coming on too fast and then being cycled off and on again. Actually, it depends on the precise nature of your fan and it's control system. The "minimum PWM setting for which the fan reliably runs" varies considerably from one unit to the next, as does "the maximum PWM number beyond which the fan speed ceases to increase". For me, anything less than 62 and the fan is too easily stopped and does not restart, anything greater than 90 is equivalent to 255. So, although the PWM has a setting range of 256, my fan is only controlled over a range of about 30! regards, Colin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: building ipcld on debian/NSLU
On Wed, Jan 09, 2008 at 07:57:20PM -0800, [EMAIL PROTECTED] wrote: I am trying to build the iplcd driver for the NSLU2 http://www.linuxha.com/athome/common/iplcd/iplc-driver.tgz This is for the USB Insteon PowerLinc V2 I am looking for the kernel build library which is not installed with the linux-image package... myslug:~/smarthome/iplc/driver/linux-2.6# make make -C /lib/modules/2.6.18-5-ixp4xx/build/ SUBDIRS=/home/super1/smarthome/iplc/driver/linux-2.6 modules make: *** /lib/modules/2.6.18-5-ixp4xx/build/: No such file or directory. Stop. make: *** [default] Error 2 What package do I need to install to get the build directory for the kernel ? Usually linux-headers-`uname -r` (that being linux-headers-whatever_version_you_are_running) It will provide /lib/modules/version/build as a symlink which is what all proper build files look for these days. If the build system is broken, just point it at that or /usr/src/linux-headers-version -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fan control on thecus n2100
Steve Gane wrote: Actually, it depends on the precise nature of your fan and it's control system. The minimum PWM setting for which the fan reliably runs varies considerably from one unit to the next, as does the maximum PWM number beyond which the fan speed ceases to increase. For me, anything less than 62 and the fan is too easily stopped and does not restart, anything greater than 90 is equivalent to 255. So, although the PWM has a setting range of 256, my fan is only controlled over a range of about 30! Yes, I've discovered that too. My fan won't start with a value less than 60 but will keep going once running down to about 56. Also the N2100 seems to have problems reading the actual fan tacho values, I get a sudden drop in reported speed once the pwm value gets to about 80 despite being able to hear the fan actually running faster! Also note that Riku's driver reports actual fan speed rather than tacho value and so the calc at the end of the script isn't required. There is also a bug in your /etc/init.d/temper script. You set the pwm value to 255 for full speed before you stop the daemon. There is a chance that the daemon might change the value again before the init.d script gets to killing it, resulting in a possibly stopped or slow running fan. I've just updated the Wiki. regards, Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE Banging your head against the wall uses 120 calories an hour. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fan control on thecus n2100
Steve Gane wrote: Hey, it's not *my* script. But I think it does the job quite well. Oh, your name is in the comment at the top of the page, so I assumed it was yours. Colin -- Colin Tuckley | +44(0)1903 236872 | PGP/GnuPG Key Id Debian Developer | +44(0)7799 143369 | 0x1B3045CE APATHY ERROR: Don't bother striking any key. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fan control on thecus n2100
Colin Tuckley wrote: There is also a bug in your /etc/init.d/temper script. You set the pwm value to 255 for full speed before you stop the daemon. There is a chance that the daemon might change the value again before the init.d script gets to killing it, resulting in a possibly stopped or slow running fan. I've just updated the Wiki. Hey, it's not *my* script. But I think it does the job quite well. regards, Colin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: MySQL problems since update
David Fokkema wrote: Hi group, Since the MySQL update to 5.0.32-7etch3 my wordpress installation is broken. It appears that certain queries kill the server (signal 11, SEGV). Downgrading to 5.0.32-7etch1 fixes everything. I manually confirmed that the failing wordpress queries kill the server (using mysql-client). I don't really know how to debug this. Any ideas? Should I just file a bug report and wait it out? I'm seeing the same thing here. After upgrading MySQL, I'm getting lost connection during query errors all over the place. What the heck is going on? -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with the 2.6.22-3-arm lenny kernel?
Hi Christian On Jan 8, 2008 1:55 PM, Christian Weeks [EMAIL PROTECTED] wrote: the newer bacula there. Unfortunately the lenny kernel, 2.6.22-3-arm, doesn't seem to want to boot. The etch kernel is just fine, so I'm running an etch kernel with a lenny userspace, but I'd like to check out the latest kernel stuff too. Last time I tested the 2.6.22 kernel, it booted fine on the NSLU2. Without a serial port to view the boot log messages, it is hard to diagnose the problem. Have you tried 2.6.23 from unstable? Gordon -- Gordon Farquharson GnuPG Key ID: 32D6D676 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
