search

a-barinov / liteqube

Liteqube - put Qubes OS on a diet
54 stars 5 forks source link

cannot create regular file '/home/user/TEST_FILE': No such file or directory and other previous errors #4

Open sirakai-pc opened 2 years ago

sirakai-pc commented 2 years ago

liteqube_install.log

could not paste the log file anywhere bcs text is too long.

sirakai-pc commented 2 years ago

my uname -a: Linux dom0 5.10.90-1.fc32.qubes.x86_64 #1 SMP Thu Jan 13 20:46:58 CET 2022 x86_64 x86_64 x86_64 GNU/Linux

a-barinov commented 2 years ago

That's a pretty stupid bug: installer naively assumes your dom0 username is 'user' which is unlikely to be the case. Do you mind if I fix this in the next commit without doing a 0.92.1 release?

sirakai-pc commented 2 years ago

For me there's no problem, already done?

a-barinov commented 2 years ago

Yes, this commit fixes it.

sirakai-pc commented 2 years ago

Got other error in 3.USB:

VM core-usb ALREADY EXISTS
CONFIGURING core-usb
STARTING debian-core
CONFIGURING debian-core
Reading package lists.
Building dependency tree...
Reading state information...
Package qubes-usb-proxy is
not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Unable to locate package usbguard
E: Package
"qubes-usb-proxy
has no installation candidate
a-barinov commented 2 years ago

qubes-usb-proxy certainly exists in Qubes debian repo. What this might indicate is package lists were not properly updated over tor, which can easily happen if a bad exit node got picked up.

What I suggest you try doing is open terminal in debian-core (via '~/bin/lq-xtem debian-core') and then run one of 'apt-get update', 'aptitude update' or just aptitude and update package lists from it.

Once update completes properly, qubes-usb-proxy shall get picked up.

sirakai-pc commented 2 years ago

Managed to update and install those 2 packages Tried rerunning install.sh on 2.Network Got this: IMG_20220630_235339_341.jpg

I removed the PCI device from core-net(usb dongle, done using qubes GUI), now installation hangs infinitely when there needs to download updates for Dom0

I don't think I was supposed to remove the device from it but at least the script failed later

sirakai-pc commented 2 years ago

Installed drivers for the WiFi usb drive, still stuck at connecting to the internet IMG_20220701_011358_972.jpg

IMG_20220701_011923_292.jpg

a-barinov commented 2 years ago

First, you can automate driver installation by putting driver package name into the installer script, line 11.

Second, the installer definitely falls for you in a non-intuitive way as default permissions for liteqube.signalWiFi should be set by it. Unconditionally.

Any chance for you to run the install script with 'set -x' set? This would give me some clues on what's failing for you.

sirakai-pc commented 2 years ago

What do u mean "set -x set"? Entering the command and retrying the install? If so there's not much change in the stout

sirakai-pc commented 2 years ago

Ohh, and... Not all realtek firmwares are in apt repositories, better installing it manually

sirakai-pc commented 2 years ago

Question: can I use sys-usb to attach usb wifi device to net-core? It just seems the only thing that could work to get internet and continue the installation with net-core and other new qubes. The installer automatically add realtek usb drive to the selected PCI device for net-core, this causes a bunch of conflict errors from other new qubes.

sirakai-pc commented 2 years ago

On the default qubes os I had to uninstall wpa_supplicant and use iwd because otherwise it wouldn't work

a-barinov commented 2 years ago

What do u mean "set -x set"? Entering the command and retrying the install? If so there's not much change in the stout

Apologies, I mean adding 'set -x' line as second line of the install script. This will print every command executed which s the most verbose form of debug available.

a-barinov commented 2 years ago

Ohh, and... Not all realtek firmwares are in apt repositories, better installing it manually

The support I have for this is putting your firmware files (not sideloaded packages bu actual firmware files!) into 2.Network/files/Firmware, these will get installed automatically.

a-barinov commented 2 years ago

Question: can I use sys-usb to attach usb wifi device to net-core? It just seems the only thing that could work to get internet and continue the installation with net-core and other new qubes. The installer automatically add realtek usb drive to the selected PCI device for net-core, this causes a bunch of conflict errors from other new qubes.

Two thoughts on this:

  1. You can use core-usb to provide network (or core-net to provide usb) but liteqube does not currently support this. You will need to manually merge the relevant folders in /etc/protect and assign devices though.
  2. You can use qvm-usb to pass your network dongle to core-net once it boots. Some scripting in dom0 required, but this will work for sure.

BTW, the logic installer uses to assign PCI devided to core-net is super-simple: it copies attached devices list from sys-net. I can probably create a blacklist option if it helps you, but un-assigning the troubled device from sys-net before the install is probably best.