Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Fri Jul 20, 2018 2:17 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 57 posts ]  Go to page Previous 1 2 3 4
Author Message
PostPosted: Thu Sep 16, 2010 11:47 am 
Offline
Newbie

Joined: Mon Aug 25, 2008 6:50 am
Posts: 42
It is done!

Here you can find a well working kernel and mini-daemon (for the featured kernel): http://linkstation.agrimm.de/

you NEED TO REGISTER to get to the DOWNLOAD-area , I got no upload-right here (sorry!) !

Balou

Edit: Uploaded the files to a free hosting service - please feel free to download and test !

http://uploading.com/files/mcb94c6b/2.6.36-rc3-git2.tar.gz/
http://uploading.com/files/c83c8a1c/lschld.tar.gz/

New Kernel (Power-Management disabled, maybe this caused some problems with samba, this is generally not enabled on 99% of orion5x-based devices):

http://www.file-upload.net/download-282 ... ar.gz.html


Top
   
PostPosted: Thu Nov 04, 2010 8:43 pm 
Offline
Newbie

Joined: Thu Nov 04, 2010 12:24 pm
Posts: 24
maybe there is a new kernel for ls chl v2 with CONFIG_SCSI_MULTI_LUN enabled?


Top
   
PostPosted: Fri Nov 05, 2010 7:17 am 
Offline
Moderator

Joined: Fri Jun 29, 2007 10:39 am
Posts: 2604
Why not build one yourself?
There are some hints how to do that in this Wiki article:
http://buffalo.nas-central.org/wiki/Building_a_kernel_from_Buffalos_source

_________________
Please do not use private mail (PN/M) to ask questions. Use the proper forum instead. (me)

If there is no verified backup of a dataset, the dataset, by definition, is unimportant. (c't 2012)

RAID (no matter which level) never ever substitutes a backup. (me)


Top
   
PostPosted: Sat Nov 06, 2010 8:21 pm 
Offline
Newbie

Joined: Thu Nov 04, 2010 12:24 pm
Posts: 24
I never build a kernel myself and there are so many things to know. I dont think im good enough.

//Edit: Okay, I tried, but the LS does not boot with the new one :/


Top
   
PostPosted: Sun Nov 07, 2010 8:16 am 
Offline
Moderator

Joined: Fri Jun 29, 2007 10:39 am
Posts: 2604
Which .config did you used?
Have you used "make menuconfig" to add your kernel switch?
Did you build the kernel on the box itself or have you cross compiled
it on a different machine?
Did you paid attention to warnings?
How did you exchange your box kernel with you selfbuild kernel?
Did you copied the new build modules (all of them and not just the
ones not already on the box) as well?

_________________
Please do not use private mail (PN/M) to ask questions. Use the proper forum instead. (me)

If there is no verified backup of a dataset, the dataset, by definition, is unimportant. (c't 2012)

RAID (no matter which level) never ever substitutes a backup. (me)


Top
   
PostPosted: Sun Nov 07, 2010 3:14 pm 
Offline
Newbie

Joined: Thu Nov 04, 2010 12:24 pm
Posts: 24
Hi,

i used http://www.onderka.com/wp-content/ls-ch ... 6.29.1.txt . I cross compiled with Debian Lenny x86-64 using the howtos in the wiki. I paid attention to warnings but I haven't seen something important. I compiled the modules also and I copied both of them via SCP to the LS. I dont have a serial link to the box so I cannot debug. Im just happy with a 2.6.22.18 kernel but this one has no CONFIG_SCSI_MULTI_LUN=y. I dont think I have enough knowhow :/


Top
   
PostPosted: Sun Nov 07, 2010 4:10 pm 
Offline
Moderator

Joined: Fri Jun 29, 2007 10:39 am
Posts: 2604
You should use the Buffalo sources to build the kernel.
And it is no problem to enable the kernel switch for this kernel.
Why do you think I posted the link to the wiki for building an own
kernel?

_________________
Please do not use private mail (PN/M) to ask questions. Use the proper forum instead. (me)

If there is no verified backup of a dataset, the dataset, by definition, is unimportant. (c't 2012)

RAID (no matter which level) never ever substitutes a backup. (me)


Top
   
PostPosted: Sun Nov 07, 2010 5:17 pm 
Offline
Newbie

Joined: Thu Nov 04, 2010 12:24 pm
Posts: 24
Quote:
what do you think why I used another "guide"?

I have absolutely no idea. That's the reason why I asked.
But if you like to decline my help, that is ok for me. You don't
have to worry.


Top
   
PostPosted: Sat Dec 04, 2010 2:56 pm 
Offline
Newbie

Joined: Sun Mar 28, 2010 6:09 pm
Posts: 17
Hi guys,

The ls-chl patch doesn't work with the most recent kernel.org git so I've uploaded a new one here. This version has been submitted to the arm kernel maintainers so it should be appearing in the mainline kernel at some point. The devio stuff is, again, as follows:

Code:
devio > foo 'wl 0xe3a01c0B,4' 'wl 0xe3811061,4'
cat foo arch/arm/boot/zImage > zImage.new
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n 'linux' -d zImage.new uImage.new


This patch changes the fan interface, an updated fan script is:

Code:
#! /bin/sh
#
#  fan-temperature control daemon - fannydee
#
#  this script checks the hdd temp on any LS-PPC that is running avr_evtd
#  and has hddtemp installed.  If the temperature is greater than the
#  defined limit, it kicks the fan up to high speed.
#
#  After the checkperiod elapses, it checks again.  If the temperature is
#  below that limit, then it drops it back to low speed.
#
#
#  In /etc/fannyd.conf, mak sure you define your devices that you want to check the temperature on
#  e.g.  /dev/hda  or /dev/sda , the temperature limit, time check, etc.
#  You can declare more than one hard drive, but that is not a likely situation.

source /etc/fannyd.conf
HDDT=/bin/hddtemp
        while : ; do

                for  A in $DEVICES ; do
                        TEMPERATURE=$($HDDT -n $A)
                        if [ $TEMPERATURE -gt $TEMPLIMITONE ]; then
                                if [ $TEMPERATURE -gt $TEMPLIMITTWO ]; then
                                        if [ $TEMPERATURE -gt $TEMPLIMITTHREE ]; then
                                                echo 5000 > /sys/class/hwmon/hwmon0/device/fan1_target
                                                sleep 40
                                        else
                                                echo 3250 > /sys/class/hwmon/hwmon0/device/fan1_target
                                                sleep 40
                                        fi
                                else
                                        echo 1500 > /sys/class/hwmon/hwmon0/device/fan1_target
                                        sleep 40
                                fi
                        else
                                sleep 60     # overcompensate w/ 1 min of extra fan time
                                echo 0 > /sys/class/hwmon/hwmon0/device/fan1_target
                        fi
                done

        done

exit  0


The fan lock alarm is available in the /sys/class/hwmon/hwmon0/device/ folder, you can monitor it for fan failures. Remember that it interrupts when the fan is turned off, so you should ignore it then. Perhaps disabling the interrupt in certain fan states is a patch for the new gpio-fans driver?

A config file is here.

I have gotten SMB file transfers back up to 10-15MB/s - the problem was the jumbo frames configuration not applying properly at startup.

Soon I will release some of the tools I've written for the box:
  • switch monitor - not quite finished yet
  • acp server daemon - listens for Nas Navigator packets and allows your debian box to show up there
  • keep-alive server - listens for WoL packets and reboots into ram (to turn off disks) when none are received after a few minutes. Used with the acp tool, this enables the 'auto power' feature on our boxes :D
  • nas_pwm - linux daemon to wake up network nas drives, same as Windows does.


Ash


Top
   
PostPosted: Fri Jan 21, 2011 3:25 pm 
Offline
Newbie

Joined: Sun Mar 28, 2010 6:09 pm
Posts: 17
This is now available in the mainline kernel. Remember to enable the gpio_fans module.

[edit] Updated the wiki: http://buffalo.nas-central.org/wiki/Category:LS-CHL


Top
   
PostPosted: Fri Jan 28, 2011 6:13 pm 
Offline
Site Admin
User avatar

Joined: Mon Jul 11, 2005 7:19 am
Posts: 7703
Location: Austria, Vienna
nice work ash87 :)

_________________
LS1 (2.6 kernel, foonas svn1062, 750 GB, UBoot 1.2) & LS Pro (FreeLink/jtymod/GenLink, changes all the time)
Thx to all donators!


Top
   
PostPosted: Sat Feb 12, 2011 2:16 pm 
Offline
Newbie

Joined: Sun Mar 28, 2010 6:09 pm
Posts: 17
Thanks :)

With the new Debian Squeeze out, the kernel needs to have:

CONFIG_SYSFS_DEPRECATED_V2
CONFIG_SYSFS_DEPRECATED

set to n, otherwise /dev/sd* won't show up. You'll need to correct this before you upgrade to squeeze otherwise you might need to take out the disk and mount it externally in order to get at the boot partition to replace the kernel.

*Replace the kernel before you upgrade to Squeeze.*

Also, if the fan then appears to not be working, it's probably because the default shell has changed. You can change:
Code:
#! /bin/sh
#


Code:
#! /bin/bash
#


in the fannyd script, or (perhaps) change the default shell back to bash.

Ash


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 57 posts ]  Go to page Previous 1 2 3 4

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 3 guests


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 post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Limited