OK, i think i didn't write it like it is supposed to be. My xen.cfg file was empty, so i just add nouveau.modset.... but without the "". And i add it just after the smt part in grub. I have miss something i guess.
Le jeudi 10 janvier 2019 23:55:23 UTC+1, Marek Marczykowski-Górecki a écrit : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Thu, Jan 10, 2019 at 02:01:39PM -0800, Mataku wrote: > > Le jeudi 10 janvier 2019 20:59:53 UTC+1, Marek Marczykowski-Górecki a écrit > > : > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA256 > > > > > > On Thu, Jan 10, 2019 at 09:55:54AM -0800, Mataku wrote: > > > > Hello Qubes users, > > > > I just starting my voyage in thr qubes world and i think it is going to > > > > be funny :D. Cannot wait to be become an expert. But for now i am a > > > > nooby. So please be kind :). > > > > I get my qubes os on this system : > > > > Motherboard : Asus Rog maximus ix > > > > Cpu : i7 7700k > > > > Ram : 32g > > > > Nvme pci : optane > > > > Gpu : nvidia pascal titan X > > > > Qubes : 4.0 (from yesterday) > > > > > > > > My goal is to get my nvidia card passing into my win7new i have create > > > > from the tutorial on the qubes website. > > > > When i'm adding the nvidia card on the VM and start it... > > > > Bang! Black screen and reboot. > > > > The devices in Qubes Manager is VGA > > > > compatible controller: NVIDIA Corporation GP102 [TITAN X] (rev a1) > > > > > > > > ps : i got the same issue if my main screen come from the gpu of the > > > > cpu or the gpu nvidia. > > > > > > > > Thank you in advance for your time. > > > > > > If you're going to assign nvidia GPU to some VM, you can't use it at the > > > same time in dom0 (to your main X server). The best way to ensure it, > > > is to unload "nouveau" kernel module in dom0, but if it's already > > > grabbed by the X server, you may need to add "nouveau.modeset=0" option > > > to the kernel command line (/boot/efi/EFI/qubes/xen.cfg on EFI system, > > > /etc/default/grub + grub2-mkconfig -o /boot/grub2/grub.cfg on legacy). > > > > > > If that doesn't help, you'll need to collect the crash message. It's > > > either dom0 panic, or Xen panic. For dom0 panic, it may be enough to > > > switch to text console and start VM from there (qvm-start ...), with a > > > camera handy. If you're not fast enough, add "noreboot" option to Xen > > > command line (just after "smt=off"). > > > If that's Xen panic, serial console may be necessary to extract it. > > > > Thank you!!!! > > Seams to be a kernel panic > > There is clearly nouveau module in this call trace. Please try the first > part of my response. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -----BEGIN PGP SIGNATURE----- > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlw3zVMACgkQ24/THMrX > 1yy9WQf9HK5W18EXFhatK2P5cxhs8sHEgV0bpWjXorkntSxHhIzjw7CnDlFtK18T > H057AQl6ibrwnjauFnE/Hu1hYGFS9zmplu2xTPHnznToy8bwk1KqgOom1JMcJcrx > ffE42ib1Z+HX5/nN1CU+vltZp9I2KCb5FBYBxPKQL3Q4mzglk1S34fSAo+Ej4Bwe > 6NMw5VQdVHpVPWvZi4X4bI9npMdZ9Tb+wANaElaCJJOz4MJmBaLeUKfPlrKXxmtN > crXJeOAtBYmgFqyR/COI6ZdaQqjMCliaOSJ7rMD5VsQhK5XB9CW+Ksyb2LQT939I > oa+tkOPpYDmlcPlas8431DQq9Nyw3A== > =WITW > -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/78f70ca4-94d4-4496-a269-8df06f5e2166%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
