Re: [qubes-users] Qubes OS 3.2 Installation Issues: anaconda 'text mode' Installation Destination autopart failed LUKS

2017-04-21 Thread pixelite25
On Saturday, April 8, 2017 at 4:00:49 PM UTC-7, radekz...@gmail.com wrote: > Can you share the exact solution for that? What boot kernel parameters have > been used? Cheers. I'm not exactly sure what 'boot kernel parameters' are, I only had to set the BIOS setting to 256MB as described and

Re: [qubes-users] Qubes OS 3.2 Installation Issues: anaconda 'text mode' Installation Destination autopart failed LUKS

2017-04-08 Thread radekzdonczyk
Can you share the exact solution for that? What boot kernel parameters have been used? Cheers. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [qubes-users] Qubes OS 3.2 Installation Issues: anaconda 'text mode' Installation Destination autopart failed LUKS

2017-01-04 Thread pixelite25
Thanks for the replies everyone. I wanted to provide an update on the original problem in which the GUI would freeze and thus force me to attempt to use Anaconda's text interface. I actually (accidentally) stumbled upon the solution. Apparently, changing the Total Graphics Memory setting

[qubes-users] Qubes OS 3.2 Installation Issues: anaconda 'text mode' Installation Destination autopart failed LUKS

2016-11-22 Thread pixelite25
Device: Lenovo ThinkPad L450 modified with OCZ Trion 150 (480GB) SSD Installation Setup: USB Drive with prepared ISO, using Basic Graphics mode under Troubleshooting due to system lockup in GUI mode. Primary Problem: When trying to setup partitioning, and selecting either Standard or LVM, this