On Sunday, January 8, 2017 at 12:14:17 PM UTC-5, Grzesiek Chodzicki wrote: > W dniu niedziela, 8 stycznia 2017 18:03:47 UTC+1 użytkownik Andrew David Wong > napisał: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > On 2017-01-08 08:30, Grzesiek Chodzicki wrote: > > > I know that this sounds rather bizarre, but my Qubes instance > > > consistently gets stuck after GRUB menu if a USB Audio device is > > > connected to the computer. So far I have a 3/3 repro rate on that. > > > What type of logs/information should I gather from my machine in > > > order to troubleshoot that? XL dmesg does print a RMRR warning > > > about USB controllers > > > > > > Qubes 3.2 Kernel 4.8.12-12 I use a sys-usb AppVM with all > > > controllers hidden from Dom0. > > > > > > > Is your sys-usb set to autostart? If so, try disabling that to see > > whether the system can boot. > > > > - -- > > Andrew David Wong (Axon) > > Community Manager, Qubes OS > > https://www.qubes-os.org > > -----BEGIN PGP SIGNATURE----- > > > > iQIcBAEBCgAGBQJYcnDpAAoJENtN07w5UDAw8NcP/iQTveiRfsgdJbeweJC84k6V > > d3UdLc8i7OrFuh4Cya0opcH341OKvCid4Rv3jIVAhRhE+TSVgobKQkXXEEE9UO8u > > 8l2ugFuUg3gYUv//WIJUmCNZXRXTTT7Tk7JFjXXhyKUjrkD1B9oAhlVPcK3UaUiQ > > 2lkAgMWVPDpo9mJMoc4GaQlWZX9sDwJ14M75lMa0lPtbN93nmFOOiye6FNIQ20bH > > pmbuu6bfyI1w53bVMA84HZIXs1msvXfLLO2CaVksntEk8TaiO/MBM8wmXYA9IQrF > > I3yxsAVm6pjqlkAIABTkGzM6wOrUeHQjgqTewvmQYO+ch5K00r/Jy2/zZwmNYOOx > > p/qHn0q82GcITe73xDTD2vp6QILkqV3VCeFBPc9JzqrFYYRONtPr3vDyD48EJ2Nb > > ButtRJXAxqe6QIkfWs614tfZYWzHMgOVSHokiGnoHMIG5OfU8jDD+ywwzLGyt+2Y > > QZsAL7dKVxxfEybAFIacumC0HyAIJWtbZDcfl6mnP3qmrGbIo8PebzwpOGCkDMFu > > NS4aC+dmqJQSqfl2yufNYbr+2eZGoPmhE206qfIL0KBM3Cch8M2RytEXHjyBCH4s > > u5SGaOALrvlM5zWADoTWyhd6PEg9EWEHkl9vo2MkFYq90o7/VIzWQBX15H5uCsYJ > > wIyI9Itq6I/JD32gR2i0 > > =lqgz > > -----END PGP SIGNATURE----- > > Hello Andrew, > > The issue still occurs after disabling autostart of the sys-usb AppVM.
Did you make sure you followed these directions? https://www.qubes-os.org/doc/external-audio/ what type of bios boot are you using? Try legacy boot. How much ram does your system have? What if you just remove the sys-usb and try booting qubes without it while device is attached? Did you create it manually? After removing the sys-usb vm then rebooting and seeing if qubes boots with the usb attached. Then recreate sys-usb using qubes commands qubesctl top.enable qvm.sys-usb qubesctl state.highstate and repeat audio device instructions. Try disabling vt-d to identify the bios iommu as possibly the problem. Doublecheck bios options. -- 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/f8d244fe-8900-4b55-a379-b5e083dd043b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
