> On May 27, 2017, at 3:35 AM, Vít Šesták > <groups-no-private-mail--contact-me-at--contact.v6ak....@v6ak.com> wrote: > > Are you able to connect the laptop via ethernet? If so, you might try > something like? > > 1. Boot in rescue mode. > 2. chroot > 3. systemctl mask lightdm # this will prevent X from starting > 4. Boot in Qubes (without X11) > 5. Update kernel using qubes-dom0-update, ideally to the one from > current-testing (e.g., qubes-dom0-update > --enablerepo=qubes-dom0-current-testing kernel.
Thank you for this. Although it did not work as a solution “out of the box” it gave me some good clues on where to start. The below steps were worked out in fits and starts, trials and errors. 1. I booted, waited for it to hang, then hit Ctrl-Alt-F2 (or technically Ctlr-Alt-Fn-F2 on this machine) 2. Luckily was able to get text login from there. Logged in as root. 3. I found `systemctl mask lightdm` did not do the trick, nor did removing and masking display-manager. What seemed to work was `systemctl set-default multi-user.target`. Anyway, in the end I was trying all three and my recollection is that only when I tried all three did the boot proceed to the end without needing to be interrupted. NOTE, there was *always* an X server error — I think this is due to how the Qubes installer works, I am guessing it launches X independent of Fedora — but with these settings the rest of the boot proceeded. (In my mind, letting the boot go to the end maximized the chance of being able to update and salvage the system. In the end, I don’t know if any of this was necessary; it’s possible the below would have worked simply from hitting Ctrl-Alt-F2.) 4. su user qvm-create -t fedora-23 -n netvm --label purple qubes-prefs default-netvm netvm qubes-prefs updatevm netvm qvm-start netvm 5. At this point I plugged in a USB-Ethernet adapter. Netvm was showing no connection via curl. I found my Ethernet controller via lspci and assigned to the netvm via (sudo?) `qvm-pci -a netvm 00:1f.6`. This was sufficient; I did not need to assign USB for whatever reason. Only at this point was I able to successfully run a curl to remote server within the netvm. 6. I was getting just "failed to synchronize cache for repo” errors when trying to run the qubes-dom0-update commands. So on a lark I tried `qvm-run netvm 'yum upgrade' -p` and installed everything suggested. 7. sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing (Worked!) 8. Reboot 9. Qubes launched into X to finish setup. Yay. I got some kind of error twice but retrying eventually fixed. When I clicked Finished Configuration button in the lower right, I was booting into text again, so I reverted all my prior changes: rm /etc/systemd/system/lightdm.service rm /etc/systemd/system/display-manager.service ln -s /usr/lib/systemd/system/lightdm.service /etc/systemd/system/lightdm.service ln -s /usr/lib/systemd/system/lightdm.service /etc/systemd/system/display-manager.service systemctl set-default graphical.target reboot 10. Qubes launches! At this point I struggle mightily to get the USB-Ethernet working again, including by deleting my old netvm to make sure it wouldn’t interefere with sys-net, making sure sys-net has the same ethernet controller (yup), turning on sys-usb, resetting sys-net. I never did get it working but meanwhile I’m waiting for the weird Lenovo mini-ethernet adapter to come so I can just use the ethernet port. 11. However in the meantime it turns out I have wifi! Success. Eager for 4.0 but in the meantime I have a nice running Qubes. -- 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/12D1F4AD-AA38-4C73-B4BA-E36B306E9DA4%40ryantate.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
