http://paste.fedoraproject.org/151650/87454141 Valient that is my single drive dual crypt setup MADE BY installer no issues
Corey W Sheldon Freelance IT Consultant, Multi-Discipline Tutor 310.909.7672 www.facebook.com/1stclassmobileshine On Mon, Nov 17, 2014 at 5:20 PM, Andrew Lutomirski <l...@mit.edu> wrote: > On Mon, Nov 17, 2014 at 2:09 PM, valent.turko...@gmail.com > <valent.turko...@gmail.com> wrote: > > On Mon, Nov 17, 2014 at 1:04 AM, Andrew Lutomirski <l...@mit.edu> wrote: > >> On Sun, Nov 16, 2014 at 4:01 PM, valent.turko...@gmail.com > >> <valent.turko...@gmail.com> wrote: > >>> Just a quick update - i got suspend/resume to once randomly work in > >>> LXDE environment, but after that again everytime it failed. > >>> > >>> Then I tried using "debugging" kernel on GRUB menu, and now each time > >>> I tried suspend/resume in all environments (GNOME 3, LXDE, Cinnamon, > >>> XFCE) it worked every time as expected. > >> > >> This smells like a no_console_suspend and/or whatever the new drm or > >> i915 fast suspend/resume thing is. Are there interesting boot > >> parameters that differ between working and non-working configurations? > >> > >> --Andy > > > > Andy do you have any ideas how to disable "i915 fast suspend/resume" ? > > Try i915.fastboot=0, I think. Although that seems to be the default, > so I may be off-base here. > > You could also try intel_iommu=on and/or intel_iommu=off -- there are > historical issues there. > > TBH, though, given the luks involvement, this could be some nasty > plymouth interaction. Fiddling with quiet and rhgb could help. > > Also, booting with no_console_suspend might give a better error message. > > --Andy > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct