Slartibartfast

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 15 total)
  • Posted in:
  • 9. April 2020 at 17:44 #48437

    You can see the various stages of temperature improvement here

    Thermal testing Raspberry Pi 4

    9. April 2020 at 15:52 #48434

    The kernel updates work for Raspbian Buster when using the latest published download as a starting point so I am not sure why you think issues are normal. More than one kernel update has been related to power saving and temperature.

    8. April 2020 at 20:55 #48425

    As far as I can tell the problem arose when Raspbian Buster became stable. Anyone who updated the kernel before that point doesn’t have an issue. Anyone who tries to update the kernel using apt-get dist upgrade since then ends up with a device that will not boot. I can’t understand the reluctance to release a new image based on the latest stable Raspbian Buster.

    17. März 2020 at 19:06 #48169

    I don’t think you can install the new kernel on Max2Play but for some reason they will not offer a new image based on the new kernel for download. Maybe if enough people complain they might finally update it.
    I was able to install the new kernel because I didn’t use Max2Play. I installed Raspbian Buster instead. If I were you I would try PiCorePlayer until Max2Play sort themselves out. They know about this problem but will not address it.

    17. März 2020 at 18:11 #48167

    You will need to install the new kernel to reduce the temperature of your Pi4. It looks like yours is still using the old kernel even after the update. If you are only using it as a player the best way is probably PiCorePlayer but it seems a waste to use a Pi4 purely as a player. I ended up going back to Raspbian Buster and installing LMS but I don’t use mine as a player. Works perfectly and sits at around 42 degrees in a FLIRC case.

    17. März 2020 at 15:22 #48158

    I think it is probably because you updated your kernel many months ago. Anyone starting from a fresh image now finds the issue that the Pi won’t boot afterwards. When I mentioned this in the Squeezebox forum a member there tried updating a new image and found exactly the same thing. Of course the original poster is welcome to try it and report back.😀

    17. März 2020 at 14:58 #48156

    Updating Max2Play using „apt-get upgrade“ just leaves you with a Pi that doesn’t boot.

    17. März 2020 at 14:00 #48154

    It is getting too hot because the downloaded image comes with an old kernel and it is impossible to update it . If you try updating via the command line then the Pi will no longer boot.

    18. Februar 2020 at 16:49 #48039

    If you do this then don’t try to update using
    Apt-get dist-upgrade
    If you do your Pi will no longer boot. So you are likely to be stuck with the old kernel with the associated temperature issues.
    This would not be an issue if a Max2Play version based on the latest Raspbian Buster with updated kernel was available for download.

    27. Dezember 2019 at 15:19 #47836

    I have installed the Buster image on a Pi4. After updating Max2Play to the latest versions I tried updating Raspbian with
    sudo apt-get update
    sudo apt-get dist-upgrade
    After the upgrade the Pi no longer boots. I have tried this a few times and another user on the slimdevices forum has confirmed that he also found the same issue after performing the upgrade.
    Any ideas?

    12. September 2017 at 10:27 #31287

    In my experience

    Sudo apt-get update
    Sudo apt-get upgrade

    does not update the kernel.

    Sudo apt-get dist-upgrade

    does update the kernel.

    Why do you think your kernel is updated? You can check the kernel version with

    uname -a

    The latest stable version is 4.9.41 I think.

    7. Januar 2017 at 1:01 #25651

    On a whim I thought I would try turning off „Autostart Desktop“. My HDD has been in Standby for almost an hour so far. So far so good. Maybe you can think of a reason this would help.

    6. Januar 2017 at 23:45 #25649

    I have monitored reads and writes to the HDD using iostat. After a reboot the hard drive does go to sleep after 10 minutes. After about 10 minutes the hard drive spins up again and iostat shows there has been no read or write activity during this time period. Once the hard drive has spun up it never spins down again as if hd-idle does not realise that it has woken up which is understandable as there has been no disk activity.
    If I then cause some read activity by clicking on My Music in LMS then 10 minutes later the drive enters standby state again. About 10 minutes later the drive wakes up again with no read/write activity. It then stays awake until the idle timer is triggered again by using LMS. My squeezeplug with the same drive didn’t behave like this.

    6. Januar 2017 at 20:14 #25643

    I have reinstalled the image and hd-idle is still not working. I have not made any changes to the file „/etc/default/hd-idle“ so after 180 seconds the drive should sleep but it never spins down. The drive is a WD Elements drive which aspins down correctly with my Squeezeplug on a Goflex Net.

    5. Januar 2017 at 0:58 #25544

    If I run
    sudo hd-idle -t sda
    the HDD enters sleep mode. If I run
    sudo hd-idle -i 0 sda -i 300 -d
    I can see reads and writes to the HDD. These numbers do not change for 30 minutes but the HDD does not enter sleep mode. So I guess hd-idle is not working.

Viewing 15 posts - 1 through 15 (of 15 total)