Debian in Buffalo LS-CHL-v2

[mailminhthang]

Hi I don't see LS-CHL-v2 firmware in your list of files. Is it possible to install Debian in it ? I see some guide lines in Google search but they are too old and seem to be not ok now Thanks so much

[polochon777]

Hello, does anyone try to install it recently?

I've followed all the instructions here https://github.com/1000001101000/Debian_on_Buffalo/wiki/Alternate-install-method-via-debootstrap-script for the linkstation. I have the debian_bullseye_armel.img at the end of the process, I write it on the hard disk but once installed I have a 6X red blinking led. Here is my setup:

##set some vars.
target="/mnt/target"
target_hostname="lschl"
machine="Buffalo Linkstation LS-CHL"
arch="armel"
#arch="armhf"
target_rootpw="mysecretpassword"
target_user="debian"
target_userpw="mysecretpassword"
#distro="stretch"
#distro="buster"
distro="bullseye"
boot_size="1024"
swap_size="1024"
root_size="2048"
use_raid="N"

I've changed target_hostname, machine, passwords and boot_size.

I think I have a LS-CHLV2 because of this message on buffalo site: http://buffalo.jp/support_ap/support/products/ls_chl.html

This is the firmware for V1 Series which has blue web-based interface. The firmware can't use for V2 Series which has red web-based interface.

My interface was red so I guess it is V2...

Any idea about how to debug this? Thanks a lot Polochon

[1000001101000]

Good to hear from you!

If yours is the V2 type you may just need to change your machine line to: machine="Buffalo Linkstation LS-CHLv2"

[polochon777]

Hello, thanks a lot, it works! But, I've read the script and I didn't found where this parameter have an impact. You check several machine name, but never Buffalo Linkstation LS-CHLv2 What's the magic here?

[1000001101000]

flash-kernel normally checks a few places under /proc and /sys for a string that identify s the device model when installing a kernel to determine settings like which device-tree to use. Since we're running in a simulated environment we override it with the desired value in that machine file.

The value needs to match an entry in one of flash-kernel's *.db files so that it can perform that lookup.

[polochon777]

OK, understood. So for my case, the string can be found here https://github.com/1000001101000/Debian_on_Buffalo/blob/master/Bullseye/device_trees/kirkwood-lschlv2.dts in the model parameter. Correct me if I'm wrong, but this (important!) information is not detailed in the wiki. I wonder if it could be added for futur users (or maybe I'm too idiot and the only one that didn't found this information by himself ...) I can do a PR if you want. Thanks again Polochon

[1000001101000]

What wiki page are you looking at?

[polochon777]

Forget what I say: this is clearly wrote here: https://github.com/1000001101000/Debian_on_Buffalo/wiki/Alternate-install-method-via-debootstrap-script#prepare-the-script With a wonderful array which says all the possibility for the machine's name... I probably need to open my eyes first! Thanks Polochon

[polochon777]

Hi, is this section https://github.com/1000001101000/Debian_on_Buffalo/wiki/Post-Installation-Options#fans relevant for the LS-CHL-v2 firmware (installed through debootstrap)? The fan noise is very high without fan control, If I can set it it will be great. I've installed lm-sensors, but a module is missing and no GPIO is detected:

root@lschl:~# sensors-detect
# sensors-detect version 3.6.0
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
# Kernel: 5.10.0-18-marvell armv5tel
# Processor: Feroceon 88FR131 rev 1 (v5l)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
modprobe: FATAL: Module cpuid not found in directory /lib/modules/5.10.0-18-marvell
Failed to load module cpuid.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Should I investigate further? Thanks a lot

[marklam]

In case it helps, from my notes when I set up a box like that (I can't remember any of it, so this is probably all the help I can offer).

FANS

apt-get install lm-sensors
apt-get install fancontrol
apt-get install hddtemp
apt-get install hdparm
apt-get install smartmontools
apt install python3-venv python3-pip
pip3 install hddfancontrol
wget https://github.com/desbma/hddfancontrol/raw/master/systemd/hddfancontrol.conf
wget https://github.com/desbma/hddfancontrol/raw/master/systemd/hddfancontrol.service
cp hddfancontrol.service /etc/systemd/system/
chmod ugo+x /etc/systemd/system/hddfancontrol.service
vi /etc/systemd/system/hddfancontrol.service

ExecStart=/usr/local/bin/hddfancontrol $HDDFANCONTROL_ARGS

mkdir -p /etc/conf.d
cp hddfancontrol.conf /etc/conf.d/hddfancontrol
vi /etc/conf.d/hddfancontrol

HDDFANCONTROL_ARGS="-d /dev/sda -p /sys/class/hwmon/hwmon0/pwm1 --pwm-start-value 2 --pwm-stop-value 0 --spin-down-time
3600"

systemctl enable hddfancontrol

[1000001101000]

Thanks @marklam

@polochon777 This model probably doesn't have a CPU temperature sensor which is what fancontrol typically uses. With newer kernels there is now a module that should allow you to make fancontrol use drive temperature instead of CPU temperature.

Try running modprobe drivetemp and then sensors to see the value.

If that doesn't work the solution @marklam posted looks like it's meant to accomplish the same thing without the new kernel module.

[polochon777]

Thanks a lot!!

Here are the steps:

• modprobe drivetemp
• sensors (should display the right GPIO)
• apt-get install fancontrol
• pwmconfig (follow the steps)

Now, launch fancontrol should be OK. If yes, you have to load the drivetemp module at startup to keep the control over reboot

• nano /etc/modules
• add this:

#controle du ventilo (or whatever you want)
drivetemp