W dniu niedziela, 13 sierpnia 2017 14:17:33 UTC+2 użytkownik Epitre napisał: > Le dimanche 13 août 2017 09:41:53 UTC+2, Foppe de Haan a écrit : > > On Sunday, August 13, 2017 at 9:38:06 AM UTC+2, Epitre wrote: > > > Le dimanche 13 août 2017 09:19:25 UTC+2, Epitre a écrit : > > > > Le dimanche 13 août 2017 07:24:29 UTC+2, Foppe de Haan a écrit : > > > > > For any newcomers: can you tell me if this covers all the bases? > > > > > https://github.com/0spinboson/qubes-doc/blob/patch-1/managing-os/compiling-your-own-kernel.md > > > > > (or if not, what's missing?) > > > > > > > > Hi, > > > > > > > > It seems right for me. Just a a comment for the version in devel-4.11, > > > > the last working version (at least for me, and need to be confirmed) is > > > > 4.11.8: > > > > > > > > The 4.11.12 has a Xen bug which has to be fixed and prevent Xen to work. > > > > The 4.12.5 has also the same bug but need to have also 3 patches > > > > updated. > > > > > > > > In both cases, qubes-core status: > > > > > > > > août 11 21:37:07 dom0 startup-misc.sh: xenstore-write: xs_open: > > > > No such file or directory > > > > août 11 21:37:07 dom0 startup-misc.sh: xenstore-write: xs_open: > > > > No such file or directory > > > > août 11 21:37:07 dom0 startup-misc.sh: xc: error: Could not > > > > obtain handle on privileged command interface (2 = No such file or > > > > directory): Internal error > > > > août 11 21:37:07 dom0 startup-misc.sh: libxl: error: > > > > libxl.c:116:libxl_ctx_alloc: cannot open libxc handle: No such file or > > > > directory > > > > août 11 21:37:07 dom0 startup-misc.sh: cannot init xl context > > > > > > > > I will dig more into the problem in the next week but if someone would > > > > like to test to confirm or not, it would help. > > > > > > > > Moreover, for those who have problem with NOUVEAU driver (see my first > > > > post asking help: > > > > https://groups.google.com/d/msg/qubes-devel/koDHzHJICEs/M5B19MBgCgAJ) > > > > and their GTX970 with 4G of VRAM, I patched the qubes kernel > > > > (https://github.com/fepitre/qubes-linux-kernel) for version 4.9 and > > > > 4.11. The major problem is in the computation of VRAM which has been > > > > completely remade and solved in kernel 4.12. > > > > > > Sorry for the quick updates but writing the message it came to mind that > > > it would maybe something related to Grub...and yes...I boot the my dev > > > machine and I don't know why but the grub conf was badly updated... > > > > > > I can confirm that the lastest working version is 4.11.12. I will also > > > update properly my repo for the patches in devel-4.12. > > > > np. I had a look, but didn't see any error messages akin to yours (running > > 4.11.12). 4.12.6 indeed only built for me if I disabled 3 kernel patches, 1 > > related to xsa155. > > Now building and running properly kernel-4.12 is ok. I pushed on my > devel-4.12 branch the updated 3 kernel patches who failed at first instance > (rewrite in the kernel sources to obtain properly updated lines). > > We can now go on the next releases (especially if someone like has Ryzen or > Kaby Lake CPU or latest NVIDIA cards).
Interestingly enough, your 4.12 branch compiles fine in the AppVM previously used to (unsuccessfully) compile Reg's 4.11 kernel. -- 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 firstname.lastname@example.org. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0051f14b-8829-4004-b8bc-87faa15b4dab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.