Updating the BIOS has not helped. I am still having major issues with suspend / resume, spurring multiple apport reports.
In addition the Thunderbolt 3 / Ethernet link is also still faulty. I'll be working away, then all of a sudden the DHCP connection will pop up a message that the connection is lost; then the rest of the computer freezes!
I will return and post if I find anything that helps.
I am starting to find information that using nvidia-prime to switch between NVIDIA and Intel graphics may be a source of these suspend / wake up issues.
With all of these earlier issues I have been running on the Intel graphics in order to maintain better battery life. I'll try it out with the nvidia card to see what goes on with that. I am using nvidia-352 binaries from the ubuntu repositories.
@hammerstyle are you running the default linux install that came with the machine? I've stopped using the intel X driver (xf86-video-intel) and am using kernel mode setting (KMS) with the i915 kernel module suspend works great for me. The Arch Linux wiki page at wiki.archlinux.org/.../intel_graphics;has excellent information that may even be useful if you're using Ubuntu. It may required a bit of hackery in the terminal, but it may provide a solution for your wake from suspend issue.
I have had some progress with the suspend. After a reboot i can runt suspend from the power menu once, but not a second time.
And running:
# sudo pm-suspend
Works fine for me. The computer suspends just fine, it even does so much quicker than with the power button choice. It is not quite the same as with the suspend through the power menu though because it does not return me to the login screen when resuming.
When looking though the /var/log/pm-suspend.log the two ways of suspending seems very similar. What might the power menu suspend do that the pm-suspend does not?
I have found some more information, and resolved some things.
For the suspend issue, it turns out that the nvidia proprietary drivers (nvidia-352) do not handle suspend properly when the discrete graphics card is disabled. In other words, if you go to nvidia-settings and under "PRIME Profiles," if you enable "Intel (power saving mode)", suspend will have issues.
By leaving it on the PRIME profile for "NVIDIA (Performance Mode)" I have had no issues whatsoever with suspend. Unfortunately, this means I've taken a hit to battery life, but it's still very good battery - and way better than when the battery is burning itself up when the Intel mode isn't suspending properly. I think that this is a bug in the proprietary nvidia drivers, and I will look into raising a bug report.
For the thunderbolt 3 ethernet dongle, this is an issue with the linux kernel for which a bug report can be found here. The bug is open and for now we'll have to live with it. There is a patch in the comments for that bug report, but I am not entirely sure on how to manually patch my linux kernel. When I figure it out I'll report back.
@hammerstyle are you running the default linux install that came with the machine? I've stopped using the intel X driver (xf86-video-intel) and am using kernel mode setting (KMS) with the i915 kernel module suspend works great for me. The Arch Linux wiki page at wiki.archlinux.org/.../intel_graphics;has excellent information that may even be useful if you're using Ubuntu. It may required a bit of hackery in the terminal, but it may provide a solution for your wake from suspend issue.
Yes, I'm running the default linux install. Thanks for your suggestion and I'll look into it. It has the added benefit of being on the arch wiki. I learned linux on that distro before switching to ubuntu for this laptop (and because it just works(TM)). I'll see if I can get that to resolve my suspend issues while running the intel GPU.
I have had some progress with the suspend. After a reboot i can runt suspend from the power menu once, but not a second time.
And running:
# sudo pm-suspend
This is one of the things I tried, and it didn't work for me.
I am also using the original image that came with the computer. Upon first boot i created a image with the Dell Recovery utility.
To enable encrypted disk i reinstalled using the image. [The installer is buggy when using LVM, had to go through some hoops to make it work.] I did all this prior to connecting the machine to the network. I tried some different approaches before settling with my current setup.
When testing after the finished install with the factory image I tested the ethernet dongle, suspension, reboot, bluetooth and so on before connecting the machine to the net. And it was then i noticed the problems with the dongle and suspension.
I then connected the machine to the network and updated it all the way current using apt-get.I tested the suspension after updating hoping that it would work, but it seemed to be the same.
That was when I posted here.
It was after that I came over the pm-suspend test. And it worked. After spending lots of time trying to understand what the GUI suspend did different from pm-suspend, I tested to close the lid and suspend just started working. Maybe some reboots after updating did it, I am not sure. I did not do anything else that I can imagine affecting the suspend.
Before updating I could suspend once after updating. When trying to suspend the screen just flickered black and went right back to the login screen as if it suspend and woke up strait after. It even locked up before entering sleep and I had to force reboot the machine.
I have not tested to enter sleep with the Ethernet dongle inserted which I had some of the times I tried before updating.
HamsterStyle
6 Posts
0
May 7th, 2016 12:00
Updating the BIOS has not helped. I am still having major issues with suspend / resume, spurring multiple apport reports.
In addition the Thunderbolt 3 / Ethernet link is also still faulty. I'll be working away, then all of a sudden the DHCP connection will pop up a message that the connection is lost; then the rest of the computer freezes!
I will return and post if I find anything that helps.
HamsterStyle
6 Posts
0
May 8th, 2016 16:00
I am starting to find information that using nvidia-prime to switch between NVIDIA and Intel graphics may be a source of these suspend / wake up issues.
With all of these earlier issues I have been running on the Intel graphics in order to maintain better battery life. I'll try it out with the nvidia card to see what goes on with that. I am using nvidia-352 binaries from the ubuntu repositories.
Highplay
3 Posts
0
May 15th, 2016 13:00
I have, as you, a brand new 5510 and I am experiencing the exact same issues as you and I am very interested in any solutions that you might find.
aalotia
19 Posts
0
May 16th, 2016 16:00
@hammerstyle are you running the default linux install that came with the machine? I've stopped using the intel X driver (xf86-video-intel) and am using kernel mode setting (KMS) with the i915 kernel module suspend works great for me. The Arch Linux wiki page at wiki.archlinux.org/.../intel_graphics;has excellent information that may even be useful if you're using Ubuntu. It may required a bit of hackery in the terminal, but it may provide a solution for your wake from suspend issue.
Highplay
3 Posts
0
May 17th, 2016 14:00
I have had some progress with the suspend. After a reboot i can runt suspend from the power menu once, but not a second time.
And running:
# sudo pm-suspend
Works fine for me. The computer suspends just fine, it even does so much quicker than with the power button choice. It is not quite the same as with the suspend through the power menu though because it does not return me to the login screen when resuming.
When looking though the /var/log/pm-suspend.log the two ways of suspending seems very similar. What might the power menu suspend do that the pm-suspend does not?
HamsterStyle
6 Posts
0
May 19th, 2016 10:00
I have found some more information, and resolved some things.
For the suspend issue, it turns out that the nvidia proprietary drivers (nvidia-352) do not handle suspend properly when the discrete graphics card is disabled. In other words, if you go to nvidia-settings and under "PRIME Profiles," if you enable "Intel (power saving mode)", suspend will have issues.
By leaving it on the PRIME profile for "NVIDIA (Performance Mode)" I have had no issues whatsoever with suspend. Unfortunately, this means I've taken a hit to battery life, but it's still very good battery - and way better than when the battery is burning itself up when the Intel mode isn't suspending properly. I think that this is a bug in the proprietary nvidia drivers, and I will look into raising a bug report.
For the thunderbolt 3 ethernet dongle, this is an issue with the linux kernel for which a bug report can be found here. The bug is open and for now we'll have to live with it. There is a patch in the comments for that bug report, but I am not entirely sure on how to manually patch my linux kernel. When I figure it out I'll report back.
HamsterStyle
6 Posts
0
May 19th, 2016 10:00
Yes, I'm running the default linux install. Thanks for your suggestion and I'll look into it. It has the added benefit of being on the arch wiki. I learned linux on that distro before switching to ubuntu for this laptop (and because it just works(TM)). I'll see if I can get that to resolve my suspend issues while running the intel GPU.
This is one of the things I tried, and it didn't work for me.
Highplay
3 Posts
0
May 20th, 2016 05:00
I am also using the original image that came with the computer. Upon first boot i created a image with the Dell Recovery utility.
To enable encrypted disk i reinstalled using the image. [The installer is buggy when using LVM, had to go through some hoops to make it work.] I did all this prior to connecting the machine to the network. I tried some different approaches before settling with my current setup.
When testing after the finished install with the factory image I tested the ethernet dongle, suspension, reboot, bluetooth and so on before connecting the machine to the net. And it was then i noticed the problems with the dongle and suspension.
I then connected the machine to the network and updated it all the way current using apt-get.I tested the suspension after updating hoping that it would work, but it seemed to be the same.
That was when I posted here.
It was after that I came over the pm-suspend test. And it worked. After spending lots of time trying to understand what the GUI suspend did different from pm-suspend, I tested to close the lid and suspend just started working. Maybe some reboots after updating did it, I am not sure. I did not do anything else that I can imagine affecting the suspend.
Before updating I could suspend once after updating. When trying to suspend the screen just flickered black and went right back to the login screen as if it suspend and woke up strait after. It even locked up before entering sleep and I had to force reboot the machine.
I have not tested to enter sleep with the Ethernet dongle inserted which I had some of the times I tried before updating.