I had the opposite impression - I thought you were abandoning Linux in favour of Windows 10, hence my confusion.
This will probably confuse you even more. I just reverted my Linux box with AMD 20.50 back to windows. I did this because the PC with the same bios settings for Windows and Ubuntu/AMD drivers would enter "suspend". The only way to recover was to power off the PC with its main power button then back on. I checked the BIOS for settings that could cause this scenario but could not find any. With the BIOS settings being the same way I do not have this problem with Windows. I am sure that this is a BIOS issue but am unable to "find that magic setting". Of course it could be a bad power supply, but that would also be a problem for windows. If anyone has any suggestions please offer them. Oh, I have an ASUS Bios. Sorry for deviating from thread topic.
I had the opposite impression - I thought you were abandoning Linux in favour of Windows 10, hence my confusion.
This will probably confuse you even more. I just reverted my Linux box with AMD 20.50 back to windows. I did this because the PC with the same bios settings for Windows and Ubuntu/AMD drivers would enter "suspend". The only way to recover was to power off the PC with its main power button then back on. I checked the BIOS for settings that could cause this scenario but could not find any. With the BIOS settings being the same way I do not have this problem with Windows. I am sure that this is a BIOS issue but am unable to "find that magic setting". Of course it could be a bad power supply, but that would also be a problem for windows. If anyone has any suggestions please offer them. Oh, I have an ASUS Bios. Sorry for deviating from thread topic.
When you say "suspend", do you mean BOINC suspends computation? or the computer itself enters a suspended state (looks like it's powered off)?
if the former, this is likely a BOINC setting, maybe you have "suspend GPU while computer in use" set?
if the latter, this is likely an OS power setting. Under Ubuntu Settings, under Power, make sure "Automatic Suspend" is ticked to "off". good idea to review your screen lock settings as well.
I had the opposite impression - I thought you were abandoning Linux in favour of Windows 10, hence my confusion.
This will probably confuse you even more. I just reverted my Linux box with AMD 20.50 back to windows. I did this because the PC with the same bios settings for Windows and Ubuntu/AMD drivers would enter "suspend". The only way to recover was to power off the PC with its main power button then back on. I checked the BIOS for settings that could cause this scenario but could not find any. With the BIOS settings being the same way I do not have this problem with Windows. I am sure that this is a BIOS issue but am unable to "find that magic setting". Of course it could be a bad power supply, but that would also be a problem for windows. If anyone has any suggestions please offer them. Oh, I have an ASUS Bios. Sorry for deviating from thread topic.
When you say "suspend", do you mean BOINC suspends computation? or the computer itself enters a suspended state (looks like it's powered off)?
if the former, this is likely a BOINC setting, maybe you have "suspend GPU while computer in use" set?
if the latter, this is likely an OS power setting. Under Ubuntu Settings, under Power, make sure "Automatic Suspend" is ticked to "off". good idea to review your screen lock settings as well.
robl wrote:
I checked the power settings and all seemed correct and "Automatic Suspend" was "off". "Suspend GPU" was not set. This is why I thought it might be a bios issue. I have noticed that after an upgrade/update to windows where a reboot is required it also requires a recycle of the "off/on" of the power button. Again it seems more like a bios issue. But....?????
if it was the BIOS, it should affect both OS's in the same manner. since it doesnt, it's likely some setting in the OS, either in BOINC, or the OS power save options.
again, what exactly are you seeing when you say "suspend". do you mean the computer is hibernating? or BOINC is saying the tasks are suspended? please clarify this.
did you also check the screen lock settings? turn of the automatic screen lock, under the Privacy settings.
if it was the BIOS, it should affect both OS's in the same manner. since it doesnt, it's likely some setting in the OS, either in BOINC, or the OS power save options.
again, what exactly are you seeing when you say "suspend". do you mean the computer is hibernating? or BOINC is saying the tasks are suspended? please clarify this.
did you also check the screen lock settings? turn of the automatic screen lock, under the Privacy settings.
by suspend I mean the pc is hibernating.
When you install Ubuntu or Windows updates and they require a reboot both require a toggle of the Power Button. There is no disk activity prior to toggling the power button.
When you install Ubuntu or Windows updates and they require a reboot both require a toggle of the Power Button. There is no disk activity prior to toggling the power button.
From your initial description of the problem, it did not sound like system updates were the cause of this issue. are you now saying they are? You can more or less stop all system updates in Ubuntu if you want to. but a reboot shouldn't result in "suspend" either, so I'm not sure how system updates are related to this problem.
did you check the screen lock settings? then try to reproduce.
I have a similar problem with my Ubuntu system that's running my Plex server (not a BOINC system). I had to disable the automatic screen lock to prevent it from hibernating.
This will probably confuse you even more. I just reverted my Linux box with AMD 20.50 back to windows. I did this because the PC with the same bios settings for Windows and Ubuntu/AMD drivers would enter "suspend". The only way to recover was to power off the PC with its main power button then back on.
After reading through all the useful information in the 'everything RX-500 series' thread I finally got my amd RX 570 running on Debian - on a new install of Bullseye (testing) with kernel 5.10.xxx usingamdgpu-20.40. xxxxx. with the usual opencl=rocr,legacy --no-dkms --headless.
Version .50 never completed, got the two lines of errors listed previously re: dkms and the other one - never tried the .45 amdgpu version either. 40 seems to work so far fine for me. BUT - to get to your issue on suspend - afaik, it's a debian - ubuntu deal that started at least with debian when I upgraded to 'Buster' Debian 10. More power saving 'features' to get us all compliant in time for the fine new green deal. Here's what I've been doing with fresh installs since and it's worked for me.
Put them to sleep with the systemctl, permanently. I run my boxes 24/7 normally they never rest.
BTW - you can revert back anytime by using 'unmask' in place of mask.
Bet this fixes it. I forget where I ran across this information now, on another forum somewhere I'm sure.I don't mind saving energy but having it forced upon you by these various back door gimmicks is not my idea of good PR on the subject. Bad enough that most linux users have to disable most or all APCI settings in BIOS to keep things stable - now you need to tweak basic system config defaults on some of these OS's. Hope this helps, I've gained a TON of great info off this forum and from the guys like Gary and other regular contributors. Thank you all - you know who you are!
Wedge009 wrote: I thought
)
I did say ta ta. I have no dislike of windows but I prefer Linux. There is a place for all OSes.
I had the opposite impression
)
I had the opposite impression - I thought you were abandoning Linux in favour of Windows 10, hence my confusion.
Soli Deo Gloria
Wedge009 wrote:I had the
)
This will probably confuse you even more. I just reverted my Linux box with AMD 20.50 back to windows. I did this because the PC with the same bios settings for Windows and Ubuntu/AMD drivers would enter "suspend". The only way to recover was to power off the PC with its main power button then back on. I checked the BIOS for settings that could cause this scenario but could not find any. With the BIOS settings being the same way I do not have this problem with Windows. I am sure that this is a BIOS issue but am unable to "find that magic setting". Of course it could be a bad power supply, but that would also be a problem for windows. If anyone has any suggestions please offer them. Oh, I have an ASUS Bios. Sorry for deviating from thread topic.
robl wrote: Wedge009
)
When you say "suspend", do you mean BOINC suspends computation? or the computer itself enters a suspended state (looks like it's powered off)?
if the former, this is likely a BOINC setting, maybe you have "suspend GPU while computer in use" set?
if the latter, this is likely an OS power setting. Under Ubuntu Settings, under Power, make sure "Automatic Suspend" is ticked to "off". good idea to review your screen lock settings as well.
_________________________________________________________________________
Ian&Steve C. wrote: robl
)
if it was the BIOS, it should
)
if it was the BIOS, it should affect both OS's in the same manner. since it doesnt, it's likely some setting in the OS, either in BOINC, or the OS power save options.
again, what exactly are you seeing when you say "suspend". do you mean the computer is hibernating? or BOINC is saying the tasks are suspended? please clarify this.
did you also check the screen lock settings? turn of the automatic screen lock, under the Privacy settings.
_________________________________________________________________________
Ian&Steve C. wrote: if it
)
by suspend I mean the pc is hibernating.
When you install Ubuntu or Windows updates and they require a reboot both require a toggle of the Power Button. There is no disk activity prior to toggling the power button.
robl wrote:by suspend I
)
From your initial description of the problem, it did not sound like system updates were the cause of this issue. are you now saying they are? You can more or less stop all system updates in Ubuntu if you want to. but a reboot shouldn't result in "suspend" either, so I'm not sure how system updates are related to this problem.
did you check the screen lock settings? then try to reproduce.
I have a similar problem with my Ubuntu system that's running my Plex server (not a BOINC system). I had to disable the automatic screen lock to prevent it from hibernating.
_________________________________________________________________________
Might also revisit the BIOS
)
Might also revisit the BIOS and disable both C-states and S3 Suspend state.
On Ubuntu going into
)
On Ubuntu going into 'suspend':
Quote from user Robl -
This will probably confuse you even more. I just reverted my Linux box with AMD 20.50 back to windows. I did this because the PC with the same bios settings for Windows and Ubuntu/AMD drivers would enter "suspend". The only way to recover was to power off the PC with its main power button then back on.
After reading through all the useful information in the 'everything RX-500 series' thread I finally got my amd RX 570 running on Debian - on a new install of Bullseye (testing) with kernel 5.10.xxx usingamdgpu-20.40. xxxxx. with the usual opencl=rocr,legacy --no-dkms --headless.
Version .50 never completed, got the two lines of errors listed previously re: dkms and the other one - never tried the .45 amdgpu version either. 40 seems to work so far fine for me. BUT - to get to your issue on suspend - afaik, it's a debian - ubuntu deal that started at least with debian when I upgraded to 'Buster' Debian 10. More power saving 'features' to get us all compliant in time for the fine new green deal. Here's what I've been doing with fresh installs since and it's worked for me.
Put them to sleep with the systemctl, permanently. I run my boxes 24/7 normally they never rest.
This works :
sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
-------------------------
BTW - you can revert back anytime by using 'unmask' in place of mask.
Bet this fixes it. I forget where I ran across this information now, on another forum somewhere I'm sure.I don't mind saving energy but having it forced upon you by these various back door gimmicks is not my idea of good PR on the subject. Bad enough that most linux users have to disable most or all APCI settings in BIOS to keep things stable - now you need to tweak basic system config defaults on some of these OS's. Hope this helps, I've gained a TON of great info off this forum and from the guys like Gary and other regular contributors. Thank you all - you know who you are!