a-barinov / liteqube

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

error: Cannot dynamically attach #5

Open moiselazarus opened 2 years ago

moiselazarus commented 2 years ago

I got this error during installation. I had also to install e2fsprogs by hand. Screenshot_2022-06-30_11-30-22

a-barinov commented 2 years ago

I was never able to fully get rid on this type of errors in the network qubes installer. It happens because sometimes qubes are extremely slow to start in the first few runs. Suggest you re-run the installer, usually it helps. On slower machines (I'm talking m3-Y70) I have to re-run the installer 3-4 times to succeed.

As for e2fsprogs, this was wrong for me to assume everyone has it installed. This commit fixes it.

moiselazarus commented 2 years ago

if I run the installer the 2. or 3. time, I got this error. I uninstalled.sh and tried again, same error. The mcedit command is also not found/installed. Screenshot_2022-07-01_08-47-00 For the base install.sh you can use the sgdisk command, then you don't need to type Yes.

moiselazarus commented 2 years ago

I found the reason. I have no wireless, only ethernet. And Sys-net is running with the pci attached. It needs to be stopped befor core-net starts. I added this lines to 2.Network/install.sh after line 456 message "SETTING DEFAULT NETVM, CLOCKVM AND UPDATEVM" qvm-shutdown --quiet --wait --force "${SYS_NET}" qvm-start --quiet --skip-if-running "${VM_NET}" I can't run the install.sh more than one time, before I have to run the uninstall.sh. This is because the netvm is not set.

a-barinov commented 2 years ago

Thanks, the proposed fix looks helpful. I pushed a commit with these extra 2 lines.

Can you elaborate on why you need to run uninstall.sh? Because you'r left with a system without properly set default netvm?

BTW, I changed default uninstall editor to nano as well.

moiselazarus commented 2 years ago

With this extra 2 lines, it works. But before, it stops with the message error: no such property netvm. Next problem: core-net trys to connect to wireless, but no wifi is there. How can I default to ethernet. How can I get a terminal in core-net? The systray Networkmanager is not shown?

moiselazarus commented 2 years ago

I prefere vi over nano. Have you checked the sgdisk man. Maybe set vi or nano global.

a-barinov commented 2 years ago

I prefere vi over nano. Have you checked the sgdisk man. Maybe set vi or nano global.

Can you check if you have $EDITOR or $VISUAL set? Unset for me :( I can easily use $EDITOR or $VISUAL if set and default to vim otherwise.

Switching to sgdisk requires a proper testing, that's a longish excersise.

a-barinov commented 2 years ago

With this extra 2 lines, it works. But before, it stops with the message error: no such property netvm.

This is something I can't quite get to the bottom of, as I'm getting the same issue sometimes. Every vm has netvm property, I can't quite understand how it can not exist. Will investigate...

Next problem: core-net trys to connect to wireless, but no wifi is there. How can I default to ethernet.

I'll make a setting for this :)

How can I get a terminal in core-net?

Try '$HOME/bin/lq-xterm core-net' or '~/bin/lq-connect' from dom0, both should work.

The systray Networkmanager is not shown?

That's the downside of not having xorg running in every qube, you lose standard applets. I'll make an alternative applet (network, tor, sound, vpn printing) fol liteqube, but not a priority ATM. And if you are wondering how I live without these applets currently, I have a nice awesome vm setup that works around this by creating alternative applets. But I can't recommend all liteqube users to install awesome vm :(

moiselazarus commented 2 years ago

Can you share your awesome config. I just changed to awesome and have just the defaults.

a-barinov commented 2 years ago

Next problem: core-net trys to connect to wireless, but no wifi is there. How can I default to ethernet.

Seems like liteqube does nothing to enforce NetworkManager to activate a wifi connection. This means we just need to issue a proper instruction to NetworkManager at core-net start and we're good. Two ways you can achieve this:

  1. Boot debian-core and open terminal there (~/bin/lq-xterm debian-core). Edit /etc/protect/template.core-net/config/rc.local and put whichever nmcli commands you need to bring network up at the end of this script
  2. Tweak the installer to have custom rc.cocal installed by using 2.Network/custom folder.
a-barinov commented 2 years ago

Can you share your awesome config. I just changed to awesome and have just the defaults.

I sure can, but not keen to setup a repo for this as the code isn't really ready for public consumption. Is there a way on github to share something with you privately? Otherwise I'll set up a repo an will kill it once you clone.

moiselazarus commented 2 years ago

Thanks for the network hints. If you set up the repo, I'll fast clone it. Thank you very much!

a-barinov commented 2 years ago

I created qubes-awesome repo with my full config. Note that you need material design icons webfont from here: https://materialdesignicons.com/

moiselazarus commented 2 years ago

Thank you very much!