On 07.06.2013 07:02, Adam Williamson wrote:
On Thu, 2013-06-06 at 23:25 +0200, Dennis Jacobfeuerborn wrote:
On 28.05.2013 02:23, Adam Williamson wrote:
On Tue, 2013-05-28 at 02:21 +0200, Dennis Jacobfeuerborn wrote:
Hi,
I just installed Fedora 19 beta rc4 using the netinstall iso in my new
Dell XPS 13 ultrabook and while it seems to work fine out of the box
this morning I found that it apparently had woken up again during the
night for no apparent reason.
Does anyone have an idea what could be the reason for a behaviour like this?
No, but I'm running F19 on the developer edition of the XPS 13 and
haven't seen that. Though I haven't woken it up for a day or two.
Since you have the developer edition I'm wondering about two things:
1) Do you have Intel Smart Connect and/or Intel Rapid Start enabled in
the BIOS?
2) Do you have a GPT partition with GUID D3BFE2DE-3DAF-11DF-BA40-
E3A556D89593 (if you installed in UEFI mode) or DOS partition with id 84
that has the same size as the amount of RAM in your system?
Since I have the Windows 8 edition and only shrunk the Windows partition
to make room for fedora but didn't touch the special partition for Rapid
Start for me these features are basically still intact and are probably
triggering this issue.
On the developer edition these features might not be enabled in the
BIOS/Firmware or if you wiped the complete disk the special partition is
missing and thus Rapid Start is effectively disabled and that may be why
you don't see this issue.
I don't know offhand what I have set in the BIOS, but I nuked the
pre-loaded Ubuntu install and did a fresh F19 install. A BIOS install,
because there was some kind of annoying roadblock when I tried to do a
UEFI install, I forget what, and I didn't want to bother fiddling with
it.
Maybe you tried installing it from USB? I fought with that for a while
until I found that you have to add the UEFI boot entry for the USB
device in a very peculiar way to get that going. After that I could
install in UEFI mode (see the last comment at
https://bugs.launchpad.net/dell-sputnik/+bug/1167617 ).
With the suspend Problem my money is actually on the Smart Connect BIOS
option since this technology specifically "wakes the system periodically
and re-establishes network connectivity. This enables your applications
that receive data from the Internet—such as your e-mail and social
network sites—to quickly sync with the cloud service and update your
system. After the content is updated, the system automatically
transitions back to sleep mode."
My theory is that this needs cooperation from the OS especially for the
"go back to sleep" part and this may be missing on Linux. This would
explain why the system comes back to life by itself.
Another interesting question is how exactly the suspend is triggered in
Fedora. I know that closing/opening the lid triggers it but what happens
when the system is woken up with the lid still closed? Does it notice
that it should go back to sleep since the lid is still closed or does it
sit there and wait for another "lid closed" event...which will never
come since it's already closed?
Regards,
Dennis
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
