What do you mean by....
>
> Boot installation media and hit tab, adding (after "quiet")
> ks=hd:sdb1:/ks.cfg
> Installation should run with no further interaction.
I am trying to get around the LUKS encryption section in the text based installation of Qubes 3.2.
When you say "tab" I am guessing you are exiting to a shell, so for v3.2 it is "Ctrl-Tab-F2"
When you say "after quiet", I am guessing you are editing the following line in the xen.cfg file...
kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R3.2-x86_64 i915.preliminary_hw_support=1 quiet rhgb
to become:
kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R3.2-x86_64 i915.preliminary_hw_support=1 quiet ks=hd:sdb1:/ks.cfg rhgb
however the whole filesystem is read-only and I cannot save the edit.
Please could someone assist?
Thanks,
Rob.
What file are you referring to when you say "fedora kernel"?
Not sure if you made a typo there but when I try to run that line with cp it say that this file can't be found :/
My computer is an H-P compact desktop. The Qubes install (4.0-rc3 for
x86_64) doesn't like something about either the Intel ethernet or the
Intel i915, so it doesn't automatically try vnc and Xorg fails.
And with text, the disk autopart fails for lack of an encryption
password for the LVM partition.
I let the default (not text) install fail, unable to start Xorg.
I press Alt-Tab until I get the shell window. I find the network
interface name by running networkctl. I run dhclient with the
interface name as the sole argument. I use ifconfig to find the
IP address that DHCP assigned. I remove /var/run/anaconda.pid.
I run
anaconda --vnc
On a remote computer behind the same router I start a vnc client and
connect to the Qubes target IP::5901. I think the client (tightvnc
on Windows 8.1) defaults to port 5900, and the anaconda sets up 5901.
Just do the graphical install on the vnc client and all goes well right
up to the reboot failing to boot from the hard drive, which I consider
to be a separate problem.