Re: [qubes-users] X.org failure preventing boot, Intel graphics

[Ryan Tate]

> On Jun 10, 2017, at 2:39 AM, Vít Šesták 
>  wrote:
> 
> Good to hear it helps. Fronm “without being able to actually boot into 
> Qubes?”, I wrongly assumed you are unable to switch to a different tty. 

This was actually a correct assumption, due to my ignorance :-) I did not know 
the "trick" of stopping boot and getting a login prompt with Ctrl-Alt-Whatever 
until after I was researching your response on the web and I stumbled on 
something on StackOverflow. So all the confusion is my fault. Thanks again.


-- 
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/868E584B-8831-46BD-B5F1-B16FD3A4AD78%40ryantate.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] X.org failure preventing boot, Intel graphics

[Vít Šesták]

Good to hear it helps. Fronm “without being able to actually boot into Qubes?”, 
I wrongly assumed you are unable to switch to a different tty. And the level of 
details you had provided suggested you would write it differently if this 
works. This is the reason why I suggested booting installer etc.

Regards,
Vít Šesták 'v6ak'

-- 
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/281be6b6-f31c-43b7-b5cc-5ad98040d253%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] X.org failure preventing boot, Intel graphics

[Ryan Tate]

> On May 27, 2017, at 3:35 AM, Vít Šesták 
>  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

Re: [qubes-users] X.org failure preventing boot, Intel graphics

[cooloutac]

On Friday, May 26, 2017 at 12:25:13 AM UTC-4, Ryan Tate wrote:
> On May 25, 2017, at 11:19 PM, Ryan Tate  wrote:
> > 
> > Ah, it turns out I was able to boot when using same fedora but different 
> > (older) kernel (4.2.3).
> 
> To be clear, I still can't boot qubes, I'm just saying it seems to have more 
> to do with the kernel than distro.  Just booting direct to a fedora usb 
> stick., 4.2.3 works as does 4.5.5 -- so I'm guessing it is something to do 
> with the qubes 4.4.14 kernel. Grateful for any tips on how to swap in another 
> kernel without being able to boot dom0.

you might have to build your own iso after all man.

-- 
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/d5d1dec1-06b2-43a3-9e67-f0d07b2c0412%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] X.org failure preventing boot, Intel graphics

[Ryan Tate]

On May 25, 2017, at 11:19 PM, Ryan Tate  wrote:
> 
> Ah, it turns out I was able to boot when using same fedora but different 
> (older) kernel (4.2.3).

To be clear, I still can't boot qubes, I'm just saying it seems to have more to 
do with the kernel than distro.  Just booting direct to a fedora usb stick., 
4.2.3 works as does 4.5.5 -- so I'm guessing it is something to do with the 
qubes 4.4.14 kernel. Grateful for any tips on how to swap in another kernel 
without being able to boot dom0. 

-- 
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/9397C8FC-00D0-4BBC-999F-4D8E226BC4D3%40ryantate.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] X.org failure preventing boot, Intel graphics

[Ryan Tate]

> On May 25, 2017, at 10:25 PM, Ryan Tate  wrote:
> 
> So I made a fedora 23 live usb and was able to boot into fine on the same 
> system. No X issues, full GUI.
> 

Ah, it turns out I was able to boot when using same fedora but different 
(older) kernel (4.2.3).

Newer kernels also seem to work. My testing:

qubes3.2 kernel 4.4.14-11 graphics-no wifi-untested (fedora23)
fedora23 kernel 4.2.3-300 graphics-yes wifi-no
fedora24 kernel 4.5.5-300 graphics-yes wifi-no
fedora25 kernel 4.8.6-300 graphics-yes wifi-yes

Any clue how to get Qubes dom0 booting into a different kernel, without being 
able to actually boot into dom0 (just the boot welcome screen)?

I don’t think I’ll be able to get the NIC working given the above results but I 
could copy a different kernel onto /boot from removable media (certainly from 
rescue mode in CD). Then I imagine I’d need to change not just grub settings 
but also Xen settings somewhere? Bit out of my depth.

Thanks for any pointers.

-- 
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/D3E2C8BA-1516-4EB2-BB1F-1DAE747A74F1%40ryantate.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [qubes-users] X.org failure preventing boot, Intel graphics

[Ryan Tate]

> On May 25, 2017, at 12:48 AM, ryant...@ryantate.com wrote:
> 
> Maybe my Intel graphics are too new for this X?

So I made a fedora 23 live usb and was able to boot into fine on the same 
system. No X issues, full GUI.

So I am wondering if this is really about Xorg, since presumably this has the 
same X server as Qubes 3.2 dom0, which is also fedora 23.

Could this somehow be specific to Xen or Qubes?

I plan to continue to invest time in this, so if anyone has an idea what my 
next investigative step should be, do let me know. Thanks for reading….

-- 
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/98620976-6604-4C4C-BB99-3EE271CF7E26%40ryantate.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail