So instead of trying to use a vm with fc25 and doing make, I'd advise you to actually use the qubes-builder. If however you prefer not to bother with that, you could technically build in dom0, though I see that as a security risk too. Instead I advise you to try the standard way:. So implying you use a vm based on fc30 template: Pull qubes-builder, then you need to setup the GPG keys and install dev dependecies. It's a bit tricky, because some of the qubes-builder docs are obsolete.
I will give you a quick idea of how I do it: Pre-reqs: VM must have at least 50 GB of space and passwordless sudo it's the default behaviour , 8 GB ram is preferable for good speed, 2 CPUs is fine, more is better So in the fc30 vm:. Repo verify with GPG keys: cd qubes-builder git tag -v git describe 6.
Building is simpler though because you do not need to configure anything. Just do make gcc-dom0. This will build gcc.
Afterwards do make linux-dom0-updates. It will may ask you to build other things beforehand, if so just do make thing until it works. Now that we have built the old linux-dom0-updates, apply the patch I gave here. And do not forget to reread my notes regarding the need to add the. I am trying to help people build Qubes as to make it more popular took me a lot of time to learn to build it , so feel free to ask me or some of the qubes devs.
I got as far as running make linux-dom0-updates which fails after about 30 seconds, and this is the end of the log below. I don't see anything in the log where it's asking me to build other packages first. Any idea what's wrong? Edit: i don't think this matters, but I'm running the builder on my fedora30 server, not a qubes vm. I think the issue is there's no fedora28 gpg keys in the chroot. I'm trying to figure out how to get them in there. Edit: hm, maybe the issue is the file that gets downloaded is fc xorg-xdrv-intel OK i was able to build the packages now.
I ended up blundering around until I ran "make get-sources" in the linux-dom0-updates dir and then i could run make linux-dom0-updates at the top level. So then I tarred up the rpms, copied them to dom0 and installed them with dnf. Unfortunately it did not fix the issue. Exact same problems as before, although now I get this warning that I didn't used to:. I am not sure if others needed to be installed, but I also added device-mapper-persistent-data I followed this path but with the same PCI id as weissjeffm.
Thanks to iprid23 I was able to build xorg-intel driver from the FC30 source repos he suggested. I then went down the rabbit hole of trying to get Mesa Meson was easy to solve but llvm I am experiencing the same issue on a T and have been since I got it, for about a year and a half.
Is there any chance we get an updated Mesa in Qubes 4. Clearly there is quite a few people having that problem. Intel U HD line is used in a lot of supported laptops, and there are not many of those in general: twice I was choosing a laptop, and twice I chose hardware specifically so that it can run Qubes; and one of these times the exact same graphics chipset just doesn't get full support.
The host is Ubuntu I want to use this machine for web development and I need the UI to be as responsive as possible. Using all three installations I did not experience good performance. It had always been slow. I must doing something wrong. Kernel version is 4. VirtualBox version is 5. The latest installation is based on KDE. I deleted the rest. Using a default monitor configuration.
If no devices become available, reconfigure udev or disable AutoAddDevices. Org Video Driver: Org XInput driver : Org Server Extension : Org Foundation" [ Org Server Extension, version Org Video Driver [ Org Video Driver, version Org XInput Driver [ Org XInput driver, version OpenGL renderer string: Gallium 0. All times are GMT. Then what should I do to get 3d acceleration working? It wouldn't work with KDE's Kwin manager yet if you have same problem as it was stated in ticket description.
Obviously, if the xorg log shows that no hardware acceleration is available, then neither kwin compositing, nor compiz nor glxgears will be accelerated? Which still leaves me wondering if this ever works for anybody with an nvidia host and what settings xorg.
It seems no log file is generated when I put this in front of the glxgears command. Try some fresh guest ubuntu install to see if it's related to your host or not.
Many thanks. I found it very counter-intuitive that with the errors in the log file and the explicit mention that a software rasteriser is loaded, that there would still be accelerated 3D.
My main install is actually debian unstable, but since it has seen many config changes I also tested with ubuntu and fedora in the past. This never gave me working 3d acceleration, but I now did a fresh ubuntu It seems recent since the last time I used ubuntu to test changes have improved the situation for my system. I'm attaching the xorg. I will now try to figure out how to fix my debian setup.
I'm also using it in a dual-boot configuration with the nvidia drivers to access the hardware directly. The confusing error messages in the log kept me looking in the wrong direction when the real remaining problem was apparently caused by glxgears loading the wrong libGL.
0コメント