(11-30-2019, 08:46 AM)sjk Wrote: Hi Just received my PineBookPro yesterday, and initial impressions are good. Updated using the supplied script to 1.5 without any issues.
My first hiccup is that suspend does not seem to be working. Hitting the power button and clicking suspend, cause it to sleep for a second, and then immediately wake up. Also closing the lid, does not seem to do anything, as I can still see the screen lit between the halves of the clamshell.
Thanks,
Scott.
I am experiencing this too and fiddled around with it a bit but I could only get suspend to work once per boot. I don't have the logs handy right now, but there were some problems with systemd-suspend trying to put the eMMC back so sleep because they get a wakeup call from somewhere.
This seems to be an issue with newest update. I was trying to debug it, but it only happens occasionally for me. Try to reboot and suspend - it will likely suspend just fine.
If someone could catch a dmesg or better yet UART, then this would be very useful.
(11-30-2019, 08:46 AM)sjk Wrote: Hi Just received my PineBookPro yesterday, and initial impressions are good. Updated using the supplied script to 1.5 without any issues.
My first hiccup is that suspend does not seem to be working. Hitting the power button and clicking suspend, cause it to sleep for a second, and then immediately wake up. Also closing the lid, does not seem to do anything, as I can still see the screen lit between the halves of the clamshell.
Thanks,
Scott.
I am experiencing this too and fiddled around with it a bit but I could only get suspend to work once per boot. I don't have the logs handy right now, but there were some problems with systemd-suspend trying to put the eMMC back so sleep because they get a wakeup call from somewhere.
This seems to be an issue with newest update. I was trying to debug it, but it only happens occasionally for me. Try to reboot and suspend - it will likely suspend just fine.
If someone could catch a dmesg or better yet UART, then this would be very useful.
It is consistent for me. \i reboot all the time, as that is the only way to stop since suspend does not work.
(11-30-2019, 08:46 AM)sjk Wrote: Hi Just received my PineBookPro yesterday, and initial impressions are good. Updated using the supplied script to 1.5 without any issues.
My first hiccup is that suspend does not seem to be working. Hitting the power button and clicking suspend, cause it to sleep for a second, and then immediately wake up. Also closing the lid, does not seem to do anything, as I can still see the screen lit between the halves of the clamshell.
Thanks,
Scott.
I am experiencing this too and fiddled around with it a bit but I could only get suspend to work once per boot. I don't have the logs handy right now, but there were some problems with systemd-suspend trying to put the eMMC back so sleep because they get a wakeup call from somewhere.
This seems to be an issue with newest update. I was trying to debug it, but it only happens occasionally for me. Try to reboot and suspend - it will likely suspend just fine.
If someone could catch a dmesg or better yet UART, then this would be very useful.
It is consistent for me. \i reboot all the time, as that is the only way to stop since suspend does not work.
attached is a sample dmesg log.
I'll point out this issue to @Mrfixit2001 Monday. Thank you for the dmesg dump.
If you wish to use FireFox instead of Chromium, then you can improve its performance by editing one variable.
Open Firefox and in the searchfield type the following; press accept for the displayed warning:
Quote:about:config
From here search for the following and set to 'true'
Code:
gfx.xrender.enabled
[/quote]
[/quote]
Hello,
After making this change, when I closed firefox I was never able to open it again. Every time I try, a small black window opens for a short time and closes. Firefox breaks instantly.
How could I solve it? Because I can't open firefox and change about:config... etc.
Thank you for what you're doing.
I am an end user from the other side of the world (Argentina) without much experience.
If you wish to use FireFox instead of Chromium, then you can improve its performance by editing one variable.
Open Firefox and in the searchfield type the following; press accept for the displayed warning:
Quote:about:config
From here search for the following and set to 'true'
Code:
gfx.xrender.enabled
[/quote]
[/quote]
Hello,
After making this change, when I closed firefox I was never able to open it again. Every time I try, a small black window opens for a short time and closes. Firefox breaks instantly.
How could I solve it? Because I can't open firefox and change about:config... etc.
Thank you for what you're doing.
I am an end user from the other side of the world (Argentina) without much experience.
Greetings!
[/quote]
In your Home folder, goto the .mozilla folder, then "firefox", then the folder that ends in "release". There is a javascript preferences file that contains the config for firefox. It is called "prefs.js". Open this and find the same tag, change is back to "false", save it and try to open firefox again.
(12-01-2019, 07:27 AM)Jeffersoniantoo Wrote: In your Home folder, goto the .mozilla folder, then "firefox", then the folder that ends in "release". There is a javascript preferences file that contains the config for firefox. It is called "prefs.js". Open this and find the same tag, change is back to "false", save it and try to open firefox again
Good luck!
Thank you, Jeffersoniantoo.
I found and made the switch, but Firefox still doesn't work. I guess the problem was somewhere else, maybe with the change of user name and home? I did just before the change in Firefox.
I imagine that uninstalling firefox and all its config files and reinstalling it might work.
How can I do that? There are 2 doubts:
1. How can I uninstall it with all the settings?
2. How to install it? because it was installed with the update 1.5 and not the repos of debian
(12-01-2019, 07:27 AM)Jeffersoniantoo Wrote: In your Home folder, goto the .mozilla folder, then "firefox", then the folder that ends in "release". There is a javascript preferences file that contains the config for firefox. It is called "prefs.js". Open this and find the same tag, change is back to "false", save it and try to open firefox again
Good luck!
Thank you, Jeffersoniantoo.
I found and made the switch, but Firefox still doesn't work. I guess the problem was somewhere else, maybe with the change of user name and home? I did just before the change in Firefox.
I imagine that uninstalling firefox and all its config files and reinstalling it might work.
How can I do that? There are 2 doubts:
1. How can I uninstall it with all the settings?
2. How to install it? because it was installed with the update 1.5 and not the repos of debian
You can use synaptic package manager or "apt-get remove firefox" to completely remove the firefox package. I would also go into the .mozilla folder and delete the firefox folder if it still exists. Then use synaptic to reinstall or install from command line (apt-get).
12-02-2019, 12:52 PM (This post was last modified: 12-02-2019, 12:54 PM by tuxor.)
(11-30-2019, 11:55 AM)Luke Wrote:
(11-30-2019, 10:02 AM)tuxor Wrote:
(11-30-2019, 08:46 AM)sjk Wrote: Hi Just received my PineBookPro yesterday, and initial impressions are good. Updated using the supplied script to 1.5 without any issues.
My first hiccup is that suspend does not seem to be working. Hitting the power button and clicking suspend, cause it to sleep for a second, and then immediately wake up. Also closing the lid, does not seem to do anything, as I can still see the screen lit between the halves of the clamshell.
Thanks,
Scott.
I am experiencing this too and fiddled around with it a bit but I could only get suspend to work once per boot. I don't have the logs handy right now, but there were some problems with systemd-suspend trying to put the eMMC back so sleep because they get a wakeup call from somewhere.
This seems to be an issue with newest update. I was trying to debug it, but it only happens occasionally for me. Try to reboot and suspend - it will likely suspend just fine.
If someone could catch a dmesg or better yet UART, then this would be very useful.
I attached my full dmesg with one suspend working and the second one not. When the suspend is not working I get the error marked below:
Code:
...
[ 152.419256] PM: Preparing system for sleep (freeze)
[ 152.422854] Freezing user space processes ... (elapsed 0.005 seconds) done.
[ 152.428746] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 152.430454] PM: Suspending system (freeze)
[ 152.430462] Suspending console(s) (use no_console_suspend to debug)
[ 152.430683] [BT_RFKILL]: Enter rfkill_rk_pm_prepare
[ 152.430685] [BT_RFKILL]: Disable UART_RTS
[ 152.430731] [BT_RFKILL]: enable irq for bt wakeup host
[ 152.432881] bcmsdh_sdmmc_suspend Enter func->num=2
[ 152.432886] dhdsdio_suspend Enter
[ 152.482286] bcmsdh_sdmmc_suspend bcmsdh_suspend err=-16
[ 152.482311] dpm_run_callback(): pm_generic_suspend+0x0/0x4c returns -16
>>>>> [ 152.482323] PM: Device mmc2:0001:2 failed to suspend: error -16
>>>>> [ 152.482331] PM: Some devices failed to suspend, or early wake event detected
>>>>> [ 152.581766] PM: resume of devices complete after 99.410 msecs
[ 152.588643] [BT_RFKILL]: Enter rfkill_rk_pm_complete
[ 152.588648] [BT_RFKILL]: ** disable irq
[ 152.588658] [BT_RFKILL]: Enable UART_RTS
[ 152.589250] PM: Finishing wakeup.
[ 152.589258] Restarting tasks ... done.
...
After a reboot suspend works as expected again (only once though until next reboot).
Don't have access to UART tools right now, otherwise I'd be glad to do some more testing.
(11-30-2019, 08:46 AM)sjk Wrote: Hi Just received my PineBookPro yesterday, and initial impressions are good. Updated using the supplied script to 1.5 without any issues.
My first hiccup is that suspend does not seem to be working. Hitting the power button and clicking suspend, cause it to sleep for a second, and then immediately wake up. Also closing the lid, does not seem to do anything, as I can still see the screen lit between the halves of the clamshell.
Thanks,
Scott.
I am experiencing this too and fiddled around with it a bit but I could only get suspend to work once per boot. I don't have the logs handy right now, but there were some problems with systemd-suspend trying to put the eMMC back so sleep because they get a wakeup call from somewhere.
This seems to be an issue with newest update. I was trying to debug it, but it only happens occasionally for me. Try to reboot and suspend - it will likely suspend just fine.
If someone could catch a dmesg or better yet UART, then this would be very useful.
I attached my full dmesg with one suspend working and the second one not. When the suspend is not working I get the error marked below:
Code:
...
[ 152.419256] PM: Preparing system for sleep (freeze)
[ 152.422854] Freezing user space processes ... (elapsed 0.005 seconds) done.
[ 152.428746] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 152.430454] PM: Suspending system (freeze)
[ 152.430462] Suspending console(s) (use no_console_suspend to debug)
[ 152.430683] [BT_RFKILL]: Enter rfkill_rk_pm_prepare
[ 152.430685] [BT_RFKILL]: Disable UART_RTS
[ 152.430731] [BT_RFKILL]: enable irq for bt wakeup host
[ 152.432881] bcmsdh_sdmmc_suspend Enter func->num=2
[ 152.432886] dhdsdio_suspend Enter
[ 152.482286] bcmsdh_sdmmc_suspend bcmsdh_suspend err=-16
[ 152.482311] dpm_run_callback(): pm_generic_suspend+0x0/0x4c returns -16
>>>>> [ 152.482323] PM: Device mmc2:0001:2 failed to suspend: error -16
>>>>> [ 152.482331] PM: Some devices failed to suspend, or early wake event detected
>>>>> [ 152.581766] PM: resume of devices complete after 99.410 msecs
[ 152.588643] [BT_RFKILL]: Enter rfkill_rk_pm_complete
[ 152.588648] [BT_RFKILL]: ** disable irq
[ 152.588658] [BT_RFKILL]: Enable UART_RTS
[ 152.589250] PM: Finishing wakeup.
[ 152.589258] Restarting tasks ... done.
...
After a reboot suspend works as expected again (only once though until next reboot).
Don't have access to UART tools right now, otherwise I'd be glad to do some more testing.
Can you please let us know if the latest release resolves the suspend/resume issue that you're seeing? v1.6 was pushed yesterday
(11-30-2019, 08:46 AM)sjk Wrote: Hi Just received my PineBookPro yesterday, and initial impressions are good. Updated using the supplied script to 1.5 without any issues.
My first hiccup is that suspend does not seem to be working. Hitting the power button and clicking suspend, cause it to sleep for a second, and then immediately wake up. Also closing the lid, does not seem to do anything, as I can still see the screen lit between the halves of the clamshell.
Thanks,
Scott.
I am experiencing this too and fiddled around with it a bit but I could only get suspend to work once per boot. I don't have the logs handy right now, but there were some problems with systemd-suspend trying to put the eMMC back so sleep because they get a wakeup call from somewhere.
This seems to be an issue with newest update. I was trying to debug it, but it only happens occasionally for me. Try to reboot and suspend - it will likely suspend just fine.
If someone could catch a dmesg or better yet UART, then this would be very useful.
I attached my full dmesg with one suspend working and the second one not. When the suspend is not working I get the error marked below:
Code:
...
[ 152.419256] PM: Preparing system for sleep (freeze)
[ 152.422854] Freezing user space processes ... (elapsed 0.005 seconds) done.
[ 152.428746] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 152.430454] PM: Suspending system (freeze)
[ 152.430462] Suspending console(s) (use no_console_suspend to debug)
[ 152.430683] [BT_RFKILL]: Enter rfkill_rk_pm_prepare
[ 152.430685] [BT_RFKILL]: Disable UART_RTS
[ 152.430731] [BT_RFKILL]: enable irq for bt wakeup host
[ 152.432881] bcmsdh_sdmmc_suspend Enter func->num=2
[ 152.432886] dhdsdio_suspend Enter
[ 152.482286] bcmsdh_sdmmc_suspend bcmsdh_suspend err=-16
[ 152.482311] dpm_run_callback(): pm_generic_suspend+0x0/0x4c returns -16
>>>>> [ 152.482323] PM: Device mmc2:0001:2 failed to suspend: error -16
>>>>> [ 152.482331] PM: Some devices failed to suspend, or early wake event detected
>>>>> [ 152.581766] PM: resume of devices complete after 99.410 msecs
[ 152.588643] [BT_RFKILL]: Enter rfkill_rk_pm_complete
[ 152.588648] [BT_RFKILL]: ** disable irq
[ 152.588658] [BT_RFKILL]: Enable UART_RTS
[ 152.589250] PM: Finishing wakeup.
[ 152.589258] Restarting tasks ... done.
...
After a reboot suspend works as expected again (only once though until next reboot).
Don't have access to UART tools right now, otherwise I'd be glad to do some more testing.
Can you please let us know if the latest release resolves the suspend/resume issue that you're seeing? v1.6 was pushed yesterday
I will let you know tomorrow. I left my PBP on my office desk, and will update as soon as I get to work in the morning. (Eastern Time)
