Re: [qubes-users] Installation help please

2018-08-17 Thread 'awokd' via qubes-users
On Fri, August 17, 2018 12:41 pm, Bengt Thuree wrote:

> GPU   : GigaByte GeForce GT 1030

Try adding nouveau.modeset=0. See
https://www.qubes-os.org/doc/nvidia-troubleshooting/#disabling-nouveau.

> ==> Q2 How do I input the encryption key when I use the text based
> installer?
> ==> Q3 How do I create and use a kickstart file?

These are good questions, but I don't know the answers!

> ==> Q4 I presume Qubes should work fine with my configuration?

There are a handful of people who got it running on Ryzen so it's probably
a question of if the motherboard/BIOS can handle it. Check
https://www.qubes-os.org/hcl/.


-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/caca4e35a5119395a012f39e30b3c3a8.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Installation help please

2018-08-17 Thread Bengt Thuree
Hi All

I have just assembled my new Desktop consisting of the following main 
components.

Motherboard : Asus Prime A320M-E
CPU : AMD Ryze 7 2700 (No internal video handling)
GPU : GigaByte GeForce GT 1030
SSD : Samsung 970 Pro NVMe M.2
RAM : 16GB DDR4

First, this is my first attempt in installing Qubes, so I probably have made 
some stupid misstakes...

I downloaded the latest Qubes 4.0, and dd'it to my USB stick.
Confirmed the check sum was ok.

Booted up the qubes installer, and tried both options on first page (Install, 
Verify and Install).
None worked due to X-Issues.

Loads of Firmware Bug popped up.
X statup failed, aborting installation
(WARN anaconda: X startup failed, Xorg existed with status 1)
(DEBUG blivet: IGNORED: blivet.safe_dbus.DBusCalError: Failed to call 
Introspect method on /org/freedesktop/UDisks2/Manager with None arguments:
GDBus.Error.=:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.UDisks2 was not provided by any .service files)

The /tmp/X.log has the following info at the end.
Screen(s) found, but none have a usable configuration.

Basic Graphics mode did not work either.

So this did not work, so I found some information on how to do it in the old 
fashion way, just text terminal.

I added inst.text to the boot prompt.
And I got further

But now it stops on Partitioner don't have LUKS password!
1) Selected the SSD
2) Use all Space
3) LVM Thin Provisioning
---> And the following output appears
Generating updated storage configuration
storage configuration failed: autopart failed:
Encryption requested for LUKS device nvme0n1p2 but no encryption key specified 
for this device

I thought I could perhaps use a kickstart file (found reference to it via 
Google), but could not find the kickstart file on the SSD disk. I presume it is
created when installation starts, which it will not do since there is an Error 
checking storage configuration.
Some questions...

==> Q1 How do I get the graphical installer to work for me?
==> Q2 How do I input the encryption key when I use the text based installer?
==> Q3 How do I create and use a kickstart file?
==> Q4 I presume Qubes should work fine with my configuration?

Looking forward to any hints or tips or suggestions

Cheers

Bengt

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0f0586bc79f094b62a3d6552d1ad7bbf026f4dcb.camel%40thuree.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: This is a digitally signed message part