speed improvement with kernel 4.2.5 / 4.3.3 / 4.6.6

[fvdw]

@uelpenich

PS: Power LED brightness is not set at boot time. But it is possible to set brightness by the GUI.

does that mean the leds are out after boot or at full brightness

[uelpenich]

The front leds are at full brightness after boot.

[fvdw]

that is the expected behavior, seems the latets settings set in the gui are not applied (issue for Jocko)

[fvdw]

on the internet I read some info on gpio-fan were they are able to set more options like fand speed , but then we need entries like this

Code: Select all

/sys/devices/platform/gpio-fan/fan1_target (and fan1_input)


But to be able to use these I need to know which gpio pins have to be linked to these entries
+ why did it work on 3.14.2 ? why do we need a different setup now, there must be a more simple solution :scratch

[fvdw]

can you determine what type of fan is in the 2big2 ?

For a nwsp2 max it seems they use also a gpio-fan with similar setup
seems that there it is a fan with following spec: (dimension) 40x40x16: ADDA AD0412LB-D50 6000rpm@12v

If that is the case we can try to use the code they use for nwsp2max, there fan cotrol and speed are defined in the platform data without a need to know gpio pins other then the alarm gpio which is the same as on 2big2 (25)
but it still bugs me why it worked ok in 3.1.4.2 with the simple code

for info the code for nwsp2max (that of 2big2 I posted already earlier

Code: Select all

/*****************************************************************************
 * GPIO fan
 ****************************************************************************/

/* Designed for fan 40x40x16: ADDA AD0412LB-D50 6000rpm@12v */
static struct gpio_fan_speed netspace_max_v2_fan_speed[] = {
   {    0,  0 },
   { 1500,   15 },
   { 1700,   14 },
   { 1800,   13 },
   { 2100,   12 },
   { 3100,   11 },
   { 3300,   10 },
   { 4300,    9 },
   { 5500,    8 },
};

static unsigned netspace_max_v2_fan_ctrl[] = { 22, 7, 33, 23 };

static struct gpio_fan_alarm netspace_max_v2_fan_alarm = {
   .gpio      = 25,
   .active_low   = 1,
};

static struct gpio_fan_platform_data netspace_max_v2_fan_data = {
   .num_ctrl   = ARRAY_SIZE(netspace_max_v2_fan_ctrl),
   .ctrl      = netspace_max_v2_fan_ctrl,
   .alarm      = &netspace_max_v2_fan_alarm,
   .num_speed   = ARRAY_SIZE(netspace_max_v2_fan_speed),
   .speed      = netspace_max_v2_fan_speed,
};

static struct platform_device netspace_max_v2_gpio_fan = {
   .name   = "gpio-fan",
   .id   = -1,
   .dev   = {
      .platform_data   = &netspace_max_v2_fan_data,
   },
};

but if we go this route then I guess we must also make a daemon that controls the fan speed based on a measurement of disk temperature like we have for 5big2

BUT it still bugs me why it worked ok in 3.1.4.2 with the simple code

therefor another hypothesis, is the fan really working on 3.1.4.2 and linked to a temperature
you mentioned this

With the 3.14.2 kernel the fan starts running at power-on. It stops (or runs very slowly) when the kernel is booted and rcS starts its actions.

But are you sure that the fan starts to run faster if the box heats up ?
It could be that it it just runs at low constant speed and never reacts on temperature. In that case the situation becomes different

[fvdw]

attached trial kernel 6,

revert back to gpio-fan.c code of 4.3.3 kernel and I enable some generic thermal diver that might be required to use on board temp sensors.

--edit there is new kernel with a patch for bug in mv643xx driver

viewtopic.php?f=4&t=2345&p=22201#p22201

[andjohn]

Hey FVDW,
I'm still getting failure to liniarize, but i think its just over gigabit.

I don't understand what you actually mean with only over gigabit.
I use at home a gigabit lan and see no problems (cable ?)

Hey FVDW,
I meant that if I was using Wifi I wouldn't get the problem, perhaps the difference between 300Mbps and the physical gigabit is where the problem manifests. I was trying to move over 300GB and perhaps it only manifests after like 50GB or something? Perhaps it slowly stops keeping up?

[uelpenich]

But are you sure that the fan starts to run faster if the box heats up ?
It could be that it it just runs at low constant speed and never reacts on temperature.

I opened the box to see what really happens. After boot the fan stops and never runs again. Even the hairdryer trick didn't start it.

In that case the situation becomes different

yes.

[Jocko]

Good idea to use an hairdryer :thumbup

But with what kernel version did you made the test ?

What fvdw would like to know is if the fan speed increases with 3.14.2 or its speed stays slow in any case.

If yes that would mean the fan driver does not also work on this version and so it is not really a kernel issue but a driver issue.

[uelpenich]

Good idea to use an hairdryer :thumbup

But with what kernel version did you made the test ?

What fvdw would like to know is if the fan speed increases with 3.14.2 or its speed stays slow in any case.

If yes that would mean the fan driver does not also work on this version and so it is not really a kernel issue but a driver issue.

Sorry for the shorthand description. I did this test with kernel 3.14.2. The fan doesn't run at all.