deskpi-team / deskpi Goto Github PK

I tried to install the DeskPI Pro driver under Volumio 2.861, which is technically a Raspbian based music player (Raspbian GNU/Linux 8 (jessie)

During installation I've got the following output:

[info] DeskPi Fan control script installation Start..
[info] Enable dwc2 on Host Mode.
[info] dwc2 has been setting up successfully.
[info] DeskPi main control service loaded..
[info] DeskPi Service configuration finished..
[info] DeskPi Service Load module..
Failed to start deskpi.service: Unit deskpi.service failed to load: Invalid argument. See system logs and 'systemctl status deskpi.service' for details.
[ ok ] DeskPi PWM Fan Control and Safeshut Service installed successfully..
[info] System will reboot in 5 seconds to take effect..

Using systemctl, the following error message displayed:

Jan 04 12:39:40 volumio systemd[1]: [/lib/systemd/system/deskpi.service:7] Executable path is not absolute, ignoring: sudo /usr/bin/pwmFanControl &
Jan 04 12:39:40 volumio systemd[1]: deskpi.service lacks both ExecStart= and ExecStop= setting. Refusing.

How could I circumvent this issue?

@yoyojacky In many of the issues we have been told - "please contact [email protected] to change the daughterboard."

Can you explain how customers who bought their DeskPi cases from SeeedStudio can obtain a new replacement daughterboard?

I have verified that when activating TRIM, the value 2147450880 assigned to 'discard_max_bytes', according to the manual, does not remain after reboot:
root@raspberrypi:/home/pi# cat /sys/block/sda/queue/discard_max_bytes
4294966784
It can also be seen in the output of the lsblk --discard command, where 4G appears instead of 2G

In my case I have created a new udev rule (99-maxdiscard.rules) to keep this value:
ACTION=="add|change", KERNEL=="sda", SUBSYSTEM=="block", ATTR{queue/discard_max_bytes}="2147450880"

In the manual it does not say anything about it. If I'm not mistaken, I think that to avoid problems this attribute should be kept at its correct value.
I don't know if anyone else has been able to verify this problem.

Sometimes Deskpi is hanging on reboot.

Steps taken:

Power status jumper is in default setting.

Disabled all installed services such as databases and webgui.

Set /etc/systemd/journald.conf to persistent logging.

Using:

sudo systemctl reboot

System hangs, deskpi has blue power light, intermittent white flashing behind case ?HD activity light?

Hold power button 3s and system turns off, fan turns off.

Tap power button, system boots.

# journalctl -r -b-1

May 25 09:25:51 smarthome-hub systemd-journald[109]: Journal stopped
May 25 09:25:51 smarthome-hub systemd-shutdown[1]: Sending SIGTERM to remaining processes...
May 25 09:25:51 smarthome-hub systemd-shutdown[1]: Syncing filesystems and block devices.
May 25 09:25:51 smarthome-hub kernel: printk: systemd-shutdow: 38 output lines suppressed due to ratelimiting
May 25 09:25:51 smarthome-hub systemd[1]: Failed to set timeout to 600s: Invalid argument
May 25 09:25:51 smarthome-hub systemd[1]: Hardware watchdog 'Broadcom BCM2835 Watchdog timer', version 0
May 25 09:25:51 smarthome-hub systemd[1]: Shutting down.
May 25 09:25:51 smarthome-hub systemd[1]: Reached target Reboot.

But deskpi stays in stalled state. Needs to be manually power cycled.

shutdown -h now results in Deskpi powered down with red light on power button.

If I can't reboot system for unattended upgrades, I'll have to toss the Deskpi pro.

Most frustrating is that sometimes reboot works.

Hi! Is there a way to tell the OS to shutdown by pressing the power button with a short press? I tried installing acpid tools but it did not work. Any tool that can help getting a safe shutdown? Thanks.

Hello,

I'm running the latest raspberry pi OS and downloaded the latest deskpi package, which installed correctly.
However, I'm no longer able to control the fan speed of my fan, which was working on the previous PCB (in fact, if I plug in the previous PCB again I regain control of the fan speed).

The fan is always running at 100% regardless of the speed setting.

The required service and USB device appears to be available.

raspi4-8:~ $ systemctl status deskpi.service
● deskpi.service - DeskPi PWM Control Fan Service
Loaded: loaded (/lib/systemd/system/deskpi.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-05-30 17:58:45 CEST; 3s ago
Main PID: 1369 (sudo)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/deskpi.service
├─1369 /usr/bin/sudo /usr/bin/pwmFanControl
└─1370 /usr/bin/pwmFanControl

May 30 17:58:45 raspi4-8 systemd[1]: Started DeskPi PWM Control Fan Service.
May 30 17:58:45 raspi4-8 sudo[1369]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/pwmFanControl
May 30 17:58:45 raspi4-8 sudo[1369]: pam_unix(sudo:session): session opened for user root by (uid=0)
raspi4-8:~ $ ls /dev/ttyUSB0
/dev/ttyUSB0
raspi4-8:~ $ dmesg | grep -i ttyusb
[ 9.738267] usb 3-1.1: ch341-uart converter now attached to ttyUSB0

Any pointers to troubleshoot this behaviour further ?

The automatic fan controller really could use some hysteresis built in so it doesn't cycle on and off unnecessarily when it is hovering around one of the temperature thresholds. For example if the 25% fan speed threshold is 45 degrees, the fan should turn on at 45c but should stay on until the temp drops to below a value of, say 43 or 42 degrees. Just pick a hysteresis value of 2 or 3 degrees and apply that to all the threshold values.

64bit os for rpi4 64bit

Hi,

Can you setup auto boot when power is connected?

There is a problem with SSD boot as the bridge chip from JMicron that is used in DeskPi is not UAS compatible. As a workaround, the section below can be added to the instruction "How to boot from USB SSD/HDD?". Further details and explanations can be found at https://www.raspberrypi.org/forums/viewtopic.php?t=245931

Disable UAS protocol for the JMicron chip
sudo nano /boot/cmdline.txt
Insert usb-storage.quirks=152d:0562:u first on the first line. Please note the trailing space.
Save and exit with ctrl+s ctrl+x

Hello,

If I press the power button for 3 seconds, the system is power off imediately instead of a soft shutdown.
Is there any way to control the power button from a script or from a C program ?

Regards,

Hi all
I have installed the new board and updated the FW to V3. Everything seems to work, my 1TB Crucial MX500 SSD is detected as UASP and works ok.
However two things don't work:

• the two USB2 ports on the front seem to be non functional
• when I power down the RP4 via software, the power button on the enclosure stays blue. Am I right in assuming it should turn red once the RP4 has actually powered down?
  Do these two issues point to a HW defect on the board?

Hi,

I installed my Raspberry pi 4 in the DeskPi Pro enclosure, not using SSD/M.2 HDD yet.
But my USB port where not working properlly, sometime front ones where working, soetime back one where working, sometime USB2 but not USB3 or other way around.

So I remove my PI from the enclosure, and now none of the USB ports are working any more ?

Please advise,

Constant

I have No Problems with Built in Wifi or Wireless Keyboard/Mouse Plugged into Pi4 but when I Plugin USB extension for the Front USB and SSD that's when I Loose Wifi and K/M Signals. All this Happens when I use Twister OS. With 32GB card that was included with my DeskPi Pro it works Perfectly.

As I mentioned in the other thread, my fan is rather noisy. It makes scratching noises on low levels (unexpected) and wind noises on high levels (expected). I try to concentrate on the low level noise in this issue, as the wind noise is natural for fans of this size.

To find out what's going on, I tried different situations, and want to share my findings here:

• The fan PWM is probably controlled by U8, that controls a MOSFET (Q5). Unfortunately, U8 is not labeled, so I can't find out what it is and how it works
• My fan makes a high-pitched, scratchy noise at PWM levels 25%, 50% and 75%. I can't tell if this noise is still there at 100%, as the fan is quite loud then, but I think I can't hear the scratchy noise then anymore. A quick and dirty measurement with a spectrometer on my smartphone shows a peak at 4800 Hz, which strangely correlates with the 9600 baud rate used in the program to control the PWM.

ASSUMPTION: The high pitched noise is caused by PWM. By adjusting the PWM frequency, the noise could be pushed into an inaudible range. As I can't tell what the PWM controller IC is, I can't tell if the IC is able to provide sufficiently high PWM frequencies (>20kHz). Also the fan might not support such high frequencies.
(The correlation between the fan noise frequency and the UART baud rate lets me assume that the PWM signal is directly connected to the UART signal, so maybe changing the UART baud rate might improve the noise)

• The fan is less loud when the module is placed outside of the metal case; the scratchy noise is less audible, but still there
• After pushing the module back into the case, the fan was much louder, the noise was amplified by the case
• In the third try, I tried to adjust the cooler as good as possible so that it does not touch the case, which is not entirely possible, but it still helped a bit

Now I tried to attach the 40x40x10mm Noctua fan, only to find out that it does not fit. The original fan is even thinner than 10mm, and I am too lazy to get a ruler right now...

Next, I added a small rubber band between fan and cooler, so that the fan does not directly touch the cooler. This also helped a lot, but the fan is still audible on low levels.

FINDINGS: The PWM sound is amplified by the case. This might be, because the case's shape and material causes a resonant frequency that is in the audible range and is excited by the fan/cooler combo. This could be reduced by gluing damping material to the case (which I don't have) or by reducing the contact between case and cooler, for example by adding two rubber rings like in this image (when you put them in the right position, they are almost invisible from the outside):

At last, I will try to mount the Noctua fan directly onto the case with two screws, and add some small passive heatsinks directly on the ICs on the Raspberry Pi. After that, I will compare the two solutions (ICE cooler with rubber bands and Noctua fan with passive heatsinks) regarding temps and volume/noise. By holding the Noctua fan onto the case, I already found out that the slots in the case also amplify fan wind noise, but this fortunately only happens at 100% PWM.

CONCLUSION: Damping the contact between fan and cooler and cooler and case reduces fan noises by a lot and is a quick and easy fix for those complaining about fan noise.
Manufacturing-wise, chamfering the slots on the top of the case might help with wind noises at high PWM levels, but also adds manufacturing costs to the case. Also adding mounting holes for a 40mm fan directly to the case would be a cool thing in case the other cooling solution works well.

TODO: Edit the baud rate in the code and see if and how it affects the PWM rate. Unfortunately, I am not code savvy enough, and the function of U8 is still unclear. I assume the worst case with adjusted baud rates would be U8 not working properly anymore, but I can't tell...

The service doesn't get executed due to the next problem:

sudo: unable to execute /usr/bin/pwmFanControl: No such file or directory

I tried using the script for Ubuntu Mate but it doesn't work well. I had to execute the commands by hand. Therefore, I imagine the scripts should be prepare for Ubuntu 20.04.

Linux raspberrypi 5.10.1-v7l+ #1383 SMP Fri Dec 18 19:05:58 GMT 2020 armv7l GNU/Linux

I have to run deskpi-config to get it to start each time I boot.

Because you chose to use the JMicron chipset that has issues running in UAS mode (the default) users need to add usb-storage.quirks=152d:0562:u to cmdline.txt in order for it to work properly. Without it the SATA drive will not boot.

Please update the readme.md with this step so that others can be spared wasting a ton of time troubleshooting a known issue. In my case it cost me an entire Sunday.

The fan doesn't work. I'm using Raspberry Pi 4 8GB, booting from SSD with Ubuntu 21.04 64-bit. I'm using the newest PCB board you've sent me.
The error is:

root@ubuntu:/var/log# systemctl status deskpi.service
● deskpi.service - DeskPi PWM Control Fan Service
     Loaded: loaded (/lib/systemd/system/deskpi.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2021-05-28 13:37:19 UTC; 27min ago
   Main PID: 6474 (code=exited, status=1/FAILURE)

May 28 13:37:19 ubuntu systemd[1]: Started DeskPi PWM Control Fan Service.
May 28 13:37:19 ubuntu sudo[6474]:     root : PWD=/ ; USER=root ; COMMAND=/usr/bin/pwmFanControl
May 28 13:37:19 ubuntu sudo[6474]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 28 13:37:19 ubuntu sudo[6474]: pam_unix(sudo:session): session closed for user root
May 28 13:37:19 ubuntu sudo[6474]: sudo: unable to execute /usr/bin/pwmFanControl: No such file or directory
May 28 13:37:19 ubuntu systemd[1]: deskpi.service: Main process exited, code=exited, status=1/FAILURE
May 28 13:37:19 ubuntu systemd[1]: deskpi.service: Failed with result 'exit-code'.

It seems the fan controller is broken:

root@ubuntu:/var/log# ls -la /usr/bin/pwmFanControl
-rwxr-xr-x 1 root root 8880 May 28 13:35 /usr/bin/pwmFanControl
root@ubuntu:/var/log# /usr/bin/pwmFanControl
-bash: /usr/bin/pwmFanControl: No such file or directory

Hi, in ubuntu server I am having problems getting the install.sh to work without problems.

This is the output of the install.sh:

ubuntu@ubuntu    ~/deskpi     master  sudo ./install.sh                                                                                                                                                                                                                                          1 ↵   16:23:42 
fatal: destination path 'deskpi' already exists and is not an empty directory.
 * DeskPi Fan control script installation Start.
 * Enable dwc2 on Host Mode
sed: can't read /boot/config.txt: No such file or directory
sed: can't read /boot/config.txt: No such file or directory
 * DeskPi main control service loaded.
 * DeskPi Service configuration finished.
 * DeskPi Service Load module.
 * DeskPi PWM Fan Control and Safeshut Service installed successfully.
 * System will reboot in 5 seconds to take effect.
Job for deskpi.service failed because the control process exited with error code.
See "systemctl status deskpi.service" and "journalctl -xe" for details.

It would seem to me that the install.sh was meant to work with the Raspbian, and not with say ubuntu server. This is a problem, as I cannot use raspbian with my raspberry pi - so I wonder how am I going to control the cpu fan now? I can see that it without load is running already at 49 degrees celcius.

I have received my upgrade board, thanks.
In the package this item was included:

However it is unclear to me where this fits. One possibility would be like this:

Where is the correct location to fit this?
Thanks

Does the installation work for Ubuntu 20.10 64Bit and not mate?
I'm not experienced in working with Linux. Only Deskpi-config seems not to work with 64Bit, right?

Hi! I have downloaded the new firmware and successfully installed it.
I have tried then activating Trim following the steps provided, and after changing provisioning_mode to unmap successfully, and adding the discard_max_bytes setting to /sys/block/sda/queque/discard_max_bytes, TRIM fails with

fstrim -v /
fstrim: /: the discard operation is not supported

@bpicon, I noticed that you succedeed on this operation in another post. Can you help me? Did you experience similar result?

Hello,

It seem than Safe-Shutdown doesn't work. When the pi is UP and I press on shutdown button, nothing doing.

When I make a long press, the power is shutdown but it's not safe for the pi.

Hello,

I'm trying to install the ubuntu script on my Pi4-8GB, however the script fails if I follow the instruction

sudo ./install-ubuntu-mate.sh

This is because it seems to look for the drivers where they aren't, in they assume the drivers are located in user root and not the current $USER

jason@jason-desktop:~/deskpi$ sudo ./install-ubuntu-mate.sh

• DeskPi Fan control script installation Start.
• DeskPi main control service loaded.
  ./install-ubuntu-mate.sh: line 25: cd: /home/root/deskpi/drivers/c/: No such file or directory
  cp: cannot stat '/home/root/deskpi/drivers/c/pwmFanControl': No such file or directory
  cp: cannot stat '/home/root/deskpi/drivers/c/fanStop': No such file or directory
  cp: cannot stat '/home/root/deskpi/deskpi-config': No such file or directory
  cp: cannot stat '/home/root/deskpi/Deskpi-uninstall': No such file or directory
• DeskPi Service configuration finished.
• DeskPi Service Load module.
  Created symlink /etc/systemd/system/multi-user.target.wants/deskpi.service → /lib/systemd/system/deskpi.service.
  Created symlink /etc/systemd/system/halt.target.wants/deskpi-safeshut.service → /lib/systemd/system/deskpi-safeshut.service.
  Created symlink /etc/systemd/system/shutdown.target.wants/deskpi-safeshut.service → /lib/systemd/system/deskpi-safeshut.service.
  Created symlink /etc/systemd/system/poweroff.target.wants/deskpi-safeshut.service → /lib/systemd/system/deskpi-safeshut.service.
• DeskPi PWM Fan Control and Safeshut Service installed successfully.
• System will reboot in 5 seconds to take effect.
  Job for deskpi.service failed because the control process exited with error code.
  See "systemctl status deskpi.service" and "journalctl -xe" for details.
  Reboot system for changes to take effect

If I try running the script without SUDO that's going to fail on permissions issues.

Kind Regards
Jason

Is there a way to enable an automatic power on after power loss. I realize it's not an advertised feature, but there must be some way to connect some test points, or replace a capacitor, and cause the device to power on automatically when power is applied?

This case is a great form factor for a RPI Server because it is stackable and has cooling. This is a necessary feature for a server.

Hi all, love the deskpi but have an issue when trying to boot from SSD
On boot, SSD is not recognised until I remove the USB dongle and plug it in again (then boots)
Unsure if this is related to #1
Any idea?

deskpi.service script blocks completion of Bootup:

iainf@hopper:$ uptime
17:34:06 up 6 min, 1 user, load average: 0.21, 0.21, 0.10
iainf@hopper:$ systemd-analyze
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
iainf@hopper:~$ systemctl list-jobs
JOB UNIT TYPE STATE
136 deskpi.service start running

1 jobs listed.
iainf@hopper:~$

I am unable to get any video via the full size HDMI ports. I have verified that the onboard Micro HDMI port is working and I see activity via the green LED so the unit is reading the provided MicroSD card. I have booted and updated the unit via the provided MicroSD card so it is not a card issue. I am using the same monitor that I used when I connected to the onboard Micro HDMI port so there is no change in monitors.

Hello, I would like to request that an installer script for the LibreELEC OS be written, so that people can use the deskpi as a media center case.

Linux raspberrypi4 5.10.43-1-MANJARO-ARM #1 SMP PREEMPT Mon Jun 14 14:31:41 UTC 2021 aarch64 GNU/Linux

cd ~
git clone https://github.com/DeskPi-Team/deskpi.git
cd ~/deskpi/
chmod +x install-manjaro.sh
sudo ./install-manjaro.sh
./install-manjaro.sh: line 3: /lib/lsb/init-functions: No such file or directory
./install-manjaro.sh: line 12: log_action_msg: command not found
./install-manjaro.sh: line 25: log_action_msg: command not found
./install-manjaro.sh: line 26: cd: /home/root/deskpi/drivers/c/: No such file or directory
cp: cannot stat '/home/root/deskpi/drivers/c/pwmFanControl': No such file or directory
cp: cannot stat '/home/root/deskpi/drivers/c/fanStop': No such file or directory
chmod: cannot access '/usr/bin/pwmFanControl': No such file or directory
chmod: cannot access '/usr/bin/fanStop': No such file or directory
cp: cannot stat '/home/root/deskpi/deskpi-config': No such file or directory
chmod: cannot access '/usr/bin/deskpi-config': No such file or directory
cp: cannot stat '/home/root/deskpi/Deskpi-uninstall': No such file or directory
chmod: cannot access '/usr/bin/Deskpi-uninstall': No such file or directory
./install-manjaro.sh: line 60: log_action_msg: command not found
./install-manjaro.sh: line 67: log_action_msg: command not found
Created symlink /etc/systemd/system/multi-user.target.wants/deskpi.service → /usr/lib/systemd/system/deskpi.service.
Created symlink /etc/systemd/system/halt.target.wants/deskpi-safeshut.service → /usr/lib/systemd/system/deskpi-safeshut.service.
Created symlink /etc/systemd/system/shutdown.target.wants/deskpi-safeshut.service → /usr/lib/systemd/system/deskpi-safeshut.service.
Created symlink /etc/systemd/system/poweroff.target.wants/deskpi-safeshut.service → /usr/lib/systemd/system/deskpi-safeshut.service.
Job for deskpi.service failed because the control process exited with error code.
See "systemctl status deskpi.service" and "journalctl -xeu deskpi.service" for details.
./install-manjaro.sh: line 74: log_success_msg: command not found
./install-manjaro.sh: line 76: log_action_msg: command not found

deskpi.service - DeskPi PWM Control Fan Service
     Loaded: loaded (/usr/lib/systemd/system/deskpi.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Mon 2021-06-21 22:50:48 CEST; 6min ago
    Process: 404 ExecStart=sudo /usr/bin/pwmFanControl & (code=exited, status=1/FAILURE)
   Main PID: 404 (code=exited, status=1/FAILURE)
        CPU: 45ms

Jun 21 22:50:48 raspberrypi4 systemd[1]: Starting DeskPi PWM Control Fan Service...
Jun 21 22:50:48 raspberrypi4 sudo[404]: sudo: /usr/bin/pwmFanControl: command not found
Jun 21 22:50:48 raspberrypi4 systemd[1]: deskpi.service: Main process exited, code=exited, status=1/FAILURE
Jun 21 22:50:48 raspberrypi4 systemd[1]: deskpi.service: Failed with result 'exit-code'.
Jun 21 22:50:48 raspberrypi4 systemd[1]: Failed to start DeskPi PWM Control Fan Service.

ls -la /usr/bin/pwmFanControl
ls: cannot access '/usr/bin/pwmFanControl': No such file or directory

After replacing lsb functions by normal echos, changed

× deskpi.service - DeskPi PWM Control Fan Service
     Loaded: loaded (/usr/lib/systemd/system/deskpi.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Tue 2021-06-22 00:02:12 CEST; 1min 23s ago
    Process: 18800 ExecStart=sudo /usr/bin/pwmFanControl & (code=exited, status=1/FAILURE)
   Main PID: 18800 (code=exited, status=1/FAILURE)
        CPU: 28ms

Jun 22 00:02:12 raspberrypi4 systemd[1]: Starting DeskPi PWM Control Fan Service...
Jun 22 00:02:12 raspberrypi4 sudo[18800]:     root : PWD=/ ; USER=root ; COMMAND=/usr/bin/pwmFanControl &
Jun 22 00:02:12 raspberrypi4 sudo[18800]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jun 22 00:02:12 raspberrypi4 sudo[18800]: pam_unix(sudo:session): session closed for user root
Jun 22 00:02:12 raspberrypi4 sudo[18800]: sudo: unable to execute /usr/bin/pwmFanControl: No such file or directory
Jun 22 00:02:12 raspberrypi4 systemd[1]: deskpi.service: Main process exited, code=exited, status=1/FAILURE
Jun 22 00:02:12 raspberrypi4 systemd[1]: deskpi.service: Failed with result 'exit-code'.
Jun 22 00:02:12 raspberrypi4 systemd[1]: Failed to start DeskPi PWM Control Fan Service.

ls -la /usr/bin/pwmFanControl
-rwxr-xr-x 1 root root 8880 Jun 21 23:58 /usr/bin/pwmFanControl

sudo /usr/bin/pwmFanControl
sudo: unable to execute /usr/bin/pwmFanControl: No such file or directory

Running deskip-config has same problems with lsb functions:

[marbi@raspberrypi4 deskpi]$ deskpi-config
/usr/bin/deskpi-config: line 11: /lib/lsb/init-functions: No such file or directory
/usr/bin/deskpi-config: line 44: log_action_msg: command not found
/usr/bin/deskpi-config: line 45: log_action_msg: command not found
/usr/bin/deskpi-config: line 46: log_action_msg: command not found
/usr/bin/deskpi-config: line 47: log_action_msg: command not found
/usr/bin/deskpi-config: line 48: log_action_msg: command not found
/usr/bin/deskpi-config: line 49: log_action_msg: command not found
/usr/bin/deskpi-config: line 50: log_action_msg: command not found
/usr/bin/deskpi-config: line 51: log_action_msg: command not found
/usr/bin/deskpi-config: line 52: log_action_msg: command not found
/usr/bin/deskpi-config: line 53: log_action_msg: command not found
/usr/bin/deskpi-config: line 54: log_action_msg: command not found
/usr/bin/deskpi-config: line 55: log_action_msg: command not found
/usr/bin/deskpi-config: line 56: log_action_msg: command not found
Your choice:

I'm able to select from 1-4 and I could see how the fan speed level works, option 7 hangs since deskip.service is failing.

I managed to get everything working including booting from a 2.5" SSD (which required the USB "quirks command" mentioned in other threads).

My only issue now is that the fan makes a buzzing rattling noise on any speed other than 100%. Fortunately, the software provides significant control, so I just don't run the fan until things get hot. Then I run it at 100%.

Neither of the USB 2.0 ports on the back of the DeskPi Pro work with my mouse / keyboard doggle. I had to move the doggle to the front of the panel. The USB 3.0 and 2.0 ports on the back work just fine for USB sticks and a USB SSD drive I had, but if I put the doggle for my mouse / keyboard in it doesn't work.

Given that the Raspberry Pi OS, Ubuntu 20.10 Desktop, and LibreElec
are all Officially supported by The Raspberry Pi Foundation, it would seem that these should be supported at minimal, rather then other unsupported distros.

I want to use Ubuntu 20.10 Desktop as my default internal SSD OS but if I can't use all the features there is no point.

This is reported in the /var/log/syslog when the USB SSD board is plugged in

Dec 8 15:49:59 raspberrypi dhcpcd[441]: wlan0: carrier lost
Dec 8 15:49:59 raspberrypi dhcpcd[441]: wlan0: deleting address fe80::f92e:f60f:536:85e0
Dec 8 15:49:59 raspberrypi avahi-daemon[410]: Withdrawing address record for fe80::f92e:f60f:536:85e0 on wlan0.
Dec 8 15:49:59 raspberrypi avahi-daemon[410]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::f92e:f60f:536:85e0.
Dec 8 15:49:59 raspberrypi avahi-daemon[410]: Interface wlan0.IPv6 no longer relevant for mDNS.
Dec 8 15:50:00 raspberrypi kernel: [ 235.016190] v3d fec00000.v3d: MMU error from client L2T (0) at 0x2401000, pte invalid
Dec 8 15:50:00 raspberrypi avahi-daemon[410]: Withdrawing address record for 192.168.1.17 on wlan0.
Dec 8 15:50:00 raspberrypi avahi-daemon[410]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.17.
Dec 8 15:50:00 raspberrypi avahi-daemon[410]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dec 8 15:50:00 raspberrypi dhcpcd[441]: wlan0: deleting route to 192.168.1.0/24
Dec 8 15:50:00 raspberrypi dhcpcd[441]: wlan0: deleting default route via 192.168.1.1
Dec 8 15:50:21 raspberrypi kernel: [ 256.256862] usb 2-1: USB disconnect, device number 5
Dec 8 15:50:21 raspberrypi kernel: [ 256.257715] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.

Then when it is removed

Dec 8 15:50:27 raspberrypi dhcpcd[441]: wlan0: carrier acquired
Dec 8 15:50:27 raspberrypi dhcpcd[441]: wlan0: IAID 32:25:08:91
Dec 8 15:50:27 raspberrypi dhcpcd[441]: wlan0: adding address fe80::f92e:f60f:536:85e0
Dec 8 15:50:27 raspberrypi avahi-daemon[410]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::f92e:f60f:536:85e0.
Dec 8 15:50:27 raspberrypi avahi-daemon[410]: New relevant interface wlan0.IPv6 for mDNS.
Dec 8 15:50:27 raspberrypi avahi-daemon[410]: Registering new address record for fe80::f92e:f60f:536:85e0 on wlan0.*.
Dec 8 15:50:27 raspberrypi dhcpcd[441]: wlan0: soliciting an IPv6 router
Dec 8 15:50:27 raspberrypi dhcpcd[441]: wlan0: rebinding lease of 192.168.1.17
Dec 8 15:50:27 raspberrypi dhcpcd[441]: wlan0: probing address 192.168.1.17/24
Dec 8 15:50:33 raspberrypi dhcpcd[441]: wlan0: leased 192.168.1.17 for 86400 seconds
Dec 8 15:50:33 raspberrypi avahi-daemon[410]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.17.
Dec 8 15:50:33 raspberrypi avahi-daemon[410]: New relevant interface wlan0.IPv4 for mDNS.
Dec 8 15:50:33 raspberrypi avahi-daemon[410]: Registering new address record for 192.168.1.17 on wlan0.IPv4.
Dec 8 15:50:33 raspberrypi dhcpcd[441]: wlan0: adding route to 192.168.1.0/24
Dec 8 15:50:33 raspberrypi dhcpcd[441]: wlan0: adding default route via 192.168.1.1
Dec 8 15:50:36 raspberrypi systemd[1]: Started Session 4 of user pi.
Dec 8 15:50:40 raspberrypi dhcpcd[441]: wlan0: no IPv6 Routers available

It also has trouble booting from SSD. I will try the quirk fix mentioned in another post.

EDIT: The quirk fix resolved my slow SSD boot. Now I am just left with Wifi issues.

DeskPi Pro with update boards. Main issue: SSD not working.
(with the OLD boards, I never got the SSD to work, either)

BUT, I could remove the SSD from DeskPi and using a USB3 to SATA cable, it would boot.
I used both a SSD and the M.2 SSD. (SSD = WD BLUE 250GB 3D NAND) and
(M.2 card has a Kingston SA400M8/240G) and both work outside the Pi with the USB3 cable.

Secondary NEW issue (SD card was not working) fixed by replacing the small/short cable. It was cut and the fan connector was broken too, the fan cable is OK and does work in the broken connector.

After reading wiki and a total reload.
I ran the Windows “FW Flash tool” OK.

$ lsblk still only shows SD card. “mmcblk0”
$ lsusb now shows ASMedia Tech ASM items both 3G/sec and 6G/sec.
“/dev/disk/by-id” NOW shows usb DeskPi_Pro 00202011… – Good?

BUT, using SD Copier, when run, I get “could not write to destination” {the usb_DeskPi_Pro DISK}
AND still no SSD boot.

YES, latest boot version in USB mode and all updates.

steve

Do you have any plans to switch to the ASMedia USB hub instead of the JMicron one? The JMicron has serious UASP issues on the Raspberry PI requiring changes to the cmdline.txt file to make it work. The ASMedia chicpset supports UASP.

On RPiOS 64bit lite, git is not installed by default. The installer fails but reboots so the output indicating why the install fails may be lost. Please add a warning and abort the install if git is not found.

Hi.

Having just run through this (successfully, as i know just enough to spot the errors) i can see many getting seriously stuck/confused due to some spelling errors, missing commands etc. Some files simply cannot be edited as stated due to permissions (I used >sudo thunar and found/edited them manually) So it does work, just needs some proof checking/clean-up and will save you a heap of email I'm sure. Thanks, Drew

Just received my DeskPi Pro today. Put everything together along with a WD Blue M.2 SSD. Installing went ok, but there's a learning curve.

My issue was when it came to prepare the SSD for USB Boot. I followed the directions on the GitHub Readme file. My issue came when I perfomed the changes under raspi-config. Everything seemed to go as expected, but when I did the "sudo -E rpi-eeprom-config --edit command things didn't go as expected. The boot config file pulled up, but it only had a couple of lines. It only had the BOOT_UART=0, WAKE_ON-GPIO=1, and POWER_OFF_ON_HALT=0 lines. I tried several times, but nothing "pulled" into the bootloader file about BOOT_ORDER=0fx41. When I performed all the rest of the steps and rebooted without the MicroSD card, I got the Raspberry Pi splash screen and then a blank screen with the white light in the DeskPi Pro box flashing constantly. After some digging, I watched the video called "How to USB boot you Raspberry Pi via DeskPi Pro with M 2 SATA SSD 1080p" made by Kevin Deng. At around 37:20 he used vcgencmd bootloader_config to check the BOOT_ORDER and that's where I figured out the steps in the Readme didn't work. I manually entered the information in my bootloader file and it worked ONCE, although it's VERY SLOW on boot-up.

I did a speed test of my SSD and got the following numbers:

Raspberry Pi Diagnostics - version 0.6
Wed Dec 23 14:21:05 2020

Test : SD Card Speed Test
Run 1
prepare-file;0;0;280068;547
seq-write;0;0;259035;505
rand-4k-write;0;0;74642;18660
rand-4k-read;73061;18265;0;0
Sequential write speed 259035 KB/sec (target 10000) - PASS
Random write speed 18660 IOPS (target 500) - PASS
Random read speed 18265 IOPS (target 1500) - PASS
Test PASS

It takes almost 3 minutes from first power applied to get to the home screen (no icons) and another 1-2 minutes for the menu icons to show up. Trying to launch Chromium took another 1-2 minutes.

There needs to be a fix for this.

I’ve followed all set up steps per deskpi pro instructions. However when I try to boot from SSD it is unusably slow. Way way slower than SD card.
thx

systemd[1]: Configuration file /lib/systemd/system/deskpi.service is marked executable. Please remove executable permission bits. Proceeding anyway.

Warning after running deskpi install.sh script

I'm not sure if it is like this for the other scripts, but the script "install-ubuntu-mate.sh" installs a 32bit version of pwmFanControl which fails to run on 64bit Ubuntu.

I received the updated boards yesterday. I just changed out the old with the new boards and booted up. No issues there, but after performing a diagnostic test on the SSD, I found the speeds the same as when we had to run Quirks to get them to function. I removed the Quirks command from my config.txt file and rebooted. No change in speed. When I first got this DeskPi Pro I was able to boot up once with the SSD's in "normal" mode and my speeds were comprable to what you'd expect for a SSD.

Raspberry Pi Diagnostics - version 0.6
Wed Dec 23 14:21:05 2020

Test : SD Card Speed Test
Run 1
prepare-file;0;0;280068;547
seq-write;0;0;259035;505
rand-4k-write;0;0;74642;18660
rand-4k-read;73061;18265;0;0
Sequential write speed 259035 KB/sec (target 10000) - PASS
Random write speed 18660 IOPS (target 500) - PASS
Random read speed 18265 IOPS (target 1500) - PASS
Test PASS

After I ran Quirks I was getting these speeds:

Raspberry Pi Diagnostics - version 0.6
Wed Dec 23 15:23:14 2020

Test : SD Card Speed Test
Run 1
prepare-file;0;0;184089;359
seq-write;0;0;179550;350
rand-4k-write;0;0;22505;5626
rand-4k-read;18729;4682;0;0
Sequential write speed 179550 KB/sec (target 10000) - PASS
Random write speed 5626 IOPS (target 500) - PASS
Random read speed 4682 IOPS (target 1500) - PASS
Test PASS

At this time, with the new board installed and with or without Quirks set, I'm still getting speeds that are 25-30% lower than when I was able to utilize the full potential of the SSD.

So is there some other driver I need to install to utilize the controller on this new board??? I really don't want to do a full reinstall of the system on my DeskPi as I've gotten it set up just the way I want it while waiting for the fixed boards to arrive.

Help.

Installing the ice tower provided with the desk pi pro requires signficant in order to mount the two back brackets, such that they bend a lot and add stress to the PCB.
I've already seen reports from other people about damaging their raspberry pi due to sloppy manufacturing tolerances in the desk pi pro & the low profile ice tower cooler that they sell separately, which is what the desk pi ice cooler is based on, uses significantly thicker brackets and longer mounting pillars so that it doesn't have this issue. For example, it uses 6mm pillars instead of 5mm, etc.

Hi,

We dont have any news about new pcb board. Deskpi team doesnt answer to mail too.

i need also another USB3 rear adaptater

Can you make an answer for that

thx

I have tried to use berry boot to install an OS to a 2.5" SSD and nothing ever boots up properly.

I modified the config and the cmdline files with the quirk modification and the front usb lines.

Tried to install rasbian os 64 full, manjaro, and ubuntu. Rasbian doesnt load up at all. Manjaro and Ubuntu load up but network and other functions do not work. I can start a browser but nothing connects to the internet otherwise. Applications crash constantly

First, let's start with the things that are good:

I like the overall design and concept of the case. It has some neat extra functions like the additional USB ports and the IR receiver. Also, the illuminated power button (two colors!) was a great surprise, as it wasn't visible on the render images on your website. I also like the interior design, how everything comes together in the small case.

But there are some serious problems with the case, as well:

Obviously, USB booting is bugged, and you will probably need a new controller. Jeff Geerling has tested a lot of controllers and USB storage solutions in his blog, so maybe you can use his knowledge to your advantage when selecting the next controller IC.
When googling for a solution for the problem, I also found that sometimes the Raspberry Pi won't boot from USB when there is a powered USB hub connected to it, as cheap USB hubs will feed back 5V to the USB output of the Raspberry Pi, and this stops the Raspi from booting. Maybe the problem with the USB boot is actually related to the USB hub IC you are using, and not to the USB-to-SATA bridge. If this is the case, you could maybe find a solution with the parts you already have in stock, by adding a single MOSFET and a resistor to keep the hub from backfeeding.

If you could post the schematics for the Deskpi Pro on Github, it would be far easier for people to find bugs like these, and to find solutions.

Furthermore, the HDMI output is problematic, sometimes I do not get any video output at all, and when I have video and lift the case, the video disappears.
Also, 4K video shows a faulty image. Both problems could also be caused by the HDMI cable that was delivered with the Deskpi Pro, as I did not test any other cable, but I assume it is more of a problem of the board routing or the microHDMI connectors.

I could not test the IR receiver, yet, but it is pretty far in the back of the case, so I assume reception will not be that good. Maybe you can also find a different position for this part when you redesign the PCBs.

There are also some mechanical problems I'd like to address:

The GPIO board that gives external access to the pins has a slight bend that will probably not affect the function of the case, but is still looking not that good.
Placing the mounting holes just a tiny bit closer to each other will probably remove that bend. Also, it seems like the 5V on the pins is only supplied by the thin FFC cable, which might cause problems with devices that draw (or deliver, like an UPS) a lot more power. Maybe the power pins of the GPIO board could also be powered from the main power source, and you can select with two jumpers where the 5V and 3V3 for the GPIO pins are coming from.

Also, the cutouts in the front and back panel are very tight. Adding 0,25mm on each side would still look good, but it would make assembly a bit easier.

Finally, the fan that was delivered with the cooler is crap. Below 100% it makes some high pitched scratching noise. I already tried to mount the fan with only one bracket in the hopes that it would stop scratching then, but even when the fan and the cooler have very little contact, the noise remains. I will replace the fan with one from Noctua.

Some people call for support for NVMe for the next board version, but I think this is counterproductive, as it would mean to drop support for SATA and 2.5 inch drives. So please stick to SATA, as this is the special thing about your case.

Hello, I have purchased the DeskPi Pro and assembled it without any problems. Unfortunately, the add-on board (PCB) for the SATA SSDs does not recognize the SSDs. Therefore, I can not boot from SSD or USB. Raspberry Pi OS does not display the SSD so I assume a hardware defect.

How to solve the issue?

Greetings

deskpi.service service file never releases - this mean the multi-user.target startup is never completed.

Patch below:

--- /lib/systemd/system/deskpi.service~ 2021-02-15 12:21:13.841558454 +0000
+++ /lib/systemd/system/deskpi.service 2021-02-15 12:47:53.408371617 +0000
@@ -2,8 +2,8 @@
Description=DeskPi PWM Control Fan Service
After=multi-user.target
[Service]
-Type=oneshot
-RemainAfterExit=true
-ExecStart=sudo /usr/bin/pwmFanControl &
+Type=simple
+RemainAfterExit=no
+ExecStart=sudo /usr/bin/pwmFanControl
[Install]
WantedBy=multi-user.target