Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
On 9/26/19 11:59 AM, donoban wrote: >> On 1/29/19 10:33 AM, Patrik Hagara wrote: >>> Managed to get rid of the error (and more importantly, the >>> annoying artifacts) by forcing Xorg to use the generic >>> modesetting driver instead of i915/i965. ... ... >>> >> After this procedure, do you get hardware acceleration? In my case, >> I do get `name:modesetting`, but I also get these in Xorg.0.log >> (and no hardware acceleration, obviously): > (...) > I did same steps and I have acceleration working fine. Right. Just tried on a T470 (i5-7200U) and it worked! Many thanks. So it's the T490 Intel chipset that refuses to cooperate. R4.1 will have Fedora 29 in dom0, so I guess that should fix it too. -- Best, r -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/77c11851-3a94-0105-c590-8e410160daa0%40hackerspace.pl. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2019-09-26 13:50, Michał "rysiek" Woźniak wrote: > Hey, > > On 1/29/19 10:33 AM, Patrik Hagara wrote: >> Managed to get rid of the error (and more importantly, the >> annoying artifacts) by forcing Xorg to use the generic >> modesetting driver instead of i915/i965. ... ... > After this procedure, do you get hardware acceleration? In my case, > I do get `name:modesetting`, but I also get these in Xorg.0.log > (and no hardware acceleration, obviously): > > [29.654] EGL_MESA_drm_image required. [29.654] (EE) > modeset(G0): glamor initialization failed (...) [29.728] (EE) > AIGLX: reverting to software rendering > I did same steps and I have acceleration working fine. > Did you install/remove any packages? Can you share the output you > get from `dnf list mesa* libdrm* xorg*`? > >> My hardware (sorry for not mentioning this earlier): Lenovo T480s >> with i7-8650U, no discrete GPU. > > I'm on a T490. Will also test on a T470 later. > I think that I did not install nothing additional but I attached my dnf output. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAl2MqBMACgkQFBMQ2OPt CKWG+Q/+Iu4u8f5FHZ7+grxRpxlZ3d8M4TUpVaBRVnhJwHVgpr6x99NGsXR7c7fK LdhHv4oES1uYwvksATXlYcKwpQs7bLZo8+UOXAWhgrMrzy+YZTdbmvOWCrSo/Cys idoNM6P8N8ByzXZ/TwLx5Zoco2dE5vwHorSpvkDBASG4OL4CgpQcdUOQcJApS4+v fAV6nn5rukkb7svrvF7UJVJNrMPikWQbeJRtkwIHKcyX7qNc2oOCs+3yBn9vIOEA AZux704wCdzJnMnKG16raA2HhMZCikijefUMzDc4ihdMKAcpaBebuUU1wc7zIHKS hF73jnUzEX5QmOwC6UEoHAYsgETpbSnAwxBToZRVjlqdZ4jy825XcWwZQ6qwKkSF lFTvB4p296xoAsTbZB+867YsS/GVCG+/eBIew/9lPYLTTTh14zWqPujuUs9cD6U+ JlrAnFEqBCQ+Ky2520Q++yb8UsrlxqQ/uTWAtAlOToP30EXHkmG7T0QEevGISU+0 FTK87h8lFEkjOjQ7/906/YhL2lTLO7oWwgrgA6JIGgTj5yiuOwW0SPDkVg/0BvXp cTbMrtbhI3R8KWtKV0avet4Ckv4xmwKO4Nxci6bn0az4e/u3+Mylmc1jSjavZ7cc RhHdDcGd0Oh0nj1YXUn1XB6ZzV1jtTxEGhyUTPDjtrOqK1MuZp0= =nr5J -END PGP SIGNATURE- -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/df5dfe37-5296-ac06-7989-ed811820b998%40riseup.net. Last metadata expiration check: 23 days, 22:32:35 ago on Mon Sep 2 15:25:23 2019. Installed Packages libdrm.x86_64 2.4.85-1.fc25 @anaconda mesa-dri-drivers.x86_64 17.0.5-3.fc25 @anaconda mesa-filesystem.x86_64 17.0.5-3.fc25 @anaconda mesa-libEGL.x86_64 17.0.5-3.fc25 @anaconda mesa-libGL.x86_64 17.0.5-3.fc25 @anaconda mesa-libGLU.x86_64 9.0.0-10.fc24 @qubes-dom0-cached mesa-libgbm.x86_64 17.0.5-3.fc25 @anaconda mesa-libglapi.x86_6417.0.5-3.fc25 @anaconda mesa-libwayland-egl.x86_64 17.0.5-3.fc25 @anaconda mesa-libxatracker.x86_6417.0.5-3.fc25 @anaconda xorg-x11-apps.x86_647.7-15.fc24 @qubes-dom0-cached xorg-x11-drivers.x86_64 7.7-18.fc25 @anaconda xorg-x11-drv-ati.x86_64 18.0.1-1.fc25 @anaconda xorg-x11-drv-dummy.x86_64 0.3.7-1.fc25 @anaconda xorg-x11-drv-evdev.x86_64 2.10.5-1.fc25 @anaconda xorg-x11-drv-fbdev.x86_64 0.4.3-25.fc25 @anaconda xorg-x11-drv-intel.x86_64 2.99.917-32.20171025.fc25 @anaconda xorg-x11-drv-libinput.x86_640.23.0-4.fc25 @anaconda xorg-x11-drv-nouveau.x86_64 1:1.0.15-4.fc25 @anaconda xorg-x11-drv-openchrome.x86_64 0.5.0-2.fc25 @anaconda xorg-x11-drv-qxl.x86_64 0.1.5-2.fc25 @anaconda xorg-x11-drv-v4l.x86_64 0.2.0-47.fc25 @anaconda xorg-x11-drv-vesa.x86_642.3.2-25.fc25 @anaconda xorg-x11-drv-vmware.x86_64 13.2.1-1.fc25 @anaconda xorg-x11-drv-wacom.x86_64 0.34.2-1.fc25 @anaconda xorg-x11-font-utils.x86_64 1:7.5-32.fc25 @anaconda xorg-x11-fonts-ISO8859-1-100dpi.noarch 7.5-16.fc24 @anaconda xorg-x11-fonts-misc.noarch 7.5-16.fc24 @qubes-dom0-cached xorg-x11-server-Xorg.x86_64 1.19.3-1.fc25 @anaconda xorg-x11-server-common.x86_64 1.19.3-1.fc25 @anaconda xorg-x11-server-utils.x86_647.7-20.fc25 @anaconda xorg-x11-utils.x86_64 7.5-21.fc24
Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
Hey, On 1/29/19 10:33 AM, Patrik Hagara wrote: > Managed to get rid of the error (and more importantly, the annoying > artifacts) by forcing Xorg to use the generic modesetting driver instead > of i915/i965. > > Steps (all commands in dom0): > > 1) check the driver currently in use (`xrandr --listproviders`), it's > the last string (should be "name:Intel" now) > > 2) create file /etc/X11/xorg.conf.d/20-intel.conf (as root) with the > following contents (also make sure there are no other files in that > directory with "Device" "Driver" set to "intel"): > >> Section "Device" >> Identifier "Intel Graphics" >> Driver "modesetting" >> Option "AccelMethod" "glamor" >> Option "DRI" "3" >> EndSection > > 3) restart the X server (eg. using `sudo systemctl restart lightdm`) > > 4) use the same xrandr command as in step 1, the driver should now be > "modesetting" and you should see no errors in /var/log/Xorg.0.log, nor > any graphical artifacts After this procedure, do you get hardware acceleration? In my case, I do get `name:modesetting`, but I also get these in Xorg.0.log (and no hardware acceleration, obviously): [29.654] EGL_MESA_drm_image required. [29.654] (EE) modeset(G0): glamor initialization failed (...) [29.728] (EE) AIGLX: reverting to software rendering Did you install/remove any packages? Can you share the output you get from `dnf list mesa* libdrm* xorg*`? > My hardware (sorry for not mentioning this earlier): Lenovo T480s with > i7-8650U, no discrete GPU. I'm on a T490. Will also test on a T470 later. -- Best r -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4818b401-2add-13c8-4d8e-0a4bf71a323e%40hackerspace.pl. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/29/19 11:33 AM, Patrik Hagara wrote: > > Update! > > Managed to get rid of the error (and more importantly, the > annoying artifacts) by forcing Xorg to use the generic modesetting > driver instead of i915/i965. > > Pages that have been helpful: * > https://wiki.gentoo.org/wiki/Intel#Modesetting_DDX * > https://ask.fedoraproject.org/en/question/130414/enabling-glamordri3-f edora-29-gnome-xorg/ > > * > https://www.reddit.com/r/Fedora/comments/5uo6ta/modesetting_driver_fed ora_25/ > > * > https://www.phoronix.com/scan.php?page=news_item&px=Fedora-Xorg-Intel- DDX-Switch > > Great! Very nice :) -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlxQdd8ACgkQFBMQ2OPt CKU3dxAAuf/KxeuXzvscYiAIbehsJ3Z2h+t4DofMtwDCGECetUx0h3LSnrqaLxVL 1hC8q8psqGZfEhnnQ8XymLQMIUbBF0dIl7GGOEm7a/YBrr3e6/sewbPUy4OYZeZf 4dFv/vxTLbOhv/k2RnkW/BefF37O5Y779+uheafbhgAYjXCSQSZYiEYLaiiyzTc+ qEBC8teu0Eg9ljnXEfW+Ukm2UilEaP/uGIqM3Gv8Z5mu6/tsAczHFxwmQKc4jnCV 3bFOFw+ck8mLGIb85IdgErwi8chRMprtJQi20TfxQMokkmob+7qlspCg0LOr7+qi R7FyuPeADDuoTWrotebtiyt8+KVBK6TASllSa2ipuYWFKHII5VS8JIK3vVgcYyTb X0KwMz8c4cFHqPHZHu/90njVEr9FHLoVXdyXDXoTg19fS/CNZKrkGOqFwLxIx68T /LSlvOgB+xBzlEmntG4feJxXOTQIVydzXTU/8o5J/xsOWBGZfNR4ToHDokMLB9cI j/ij6mUv6/LOO20g1u2BHfUyNEj11QV2rYuDf4/Osqf+vjPhU6g+tN0OjkQtSYIO REK7Mdpc1icPzG5KE1pXw0reMFbOdNzQY/JgjU/Cx75c2OFBU5jDE9QuRyyeo+4R kEJEvPbyQdgFXiGQNflb51Ynqq5AWJaMlA/AtszC3lYRAdUWUrA= =q2fJ -END PGP SIGNATURE- -- 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/bdfdec5d-7f26-6200-1367-0a90e7c74206%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
On 1/25/19 3:16 PM, Marek Marczykowski-Górecki wrote: > On Fri, Jan 25, 2019 at 01:58:59PM +0100, Patrik Hagara wrote: >> On 1/24/19 5:18 PM, Patrik Hagara wrote: >>> On 1/20/19 1:57 AM, Marek Marczykowski-Górecki wrote: Hi all, There is updated "kernel" package available in current-testing repository - it's a Linux long term support 4.19.x series, as an update over 4.14.x before. Since the upgrade switches to the next major LTS branch, I'll keep it in current-testing repository longer than usual 1-2 weeks. This also applies to kernel package for VMs: kernel-qubes-vm. Please report new issues the usual way, at qubes-issues[1], or simply by replying here. In either case, please mark it clearly it happens after updating to 4.19, preferably including a link to the update: https://github.com/QubesOS/updates-status/issues/850 4.19.x kernel was already available as kernel-latest package for some time. Users of kernel-latest will see the update to 4.19.15 too, but kernel-latest soon will carry 4.20.x kernel version. [1] https://github.com/QubesOS/qubes-issues/issues >>> >>> I get weird graphical artifacts with the new kernel after ~an hour of >>> usage. Windows from AppVMs turn all white sometimes when switching >>> workspaces in i3wm. Events like mousing over an interactive table rows >>> in a browser (when the current row gets highlighted) return that >>> particular section of the window back to normal (but not the whole >>> window, for that I need to trigger a repaint of the whole window by eg. >>> making it full-screen and immediately switching back to non-full-screen). > >> The only error message I've been able to find so far is in dom0 Xorg log: > >>> (EE) intel(0): Failed to submit rendering commands (Bad address), >> disabling acceleration. > > This is very likely related. Normally I'd say "Bad address" indicate > user-space issue, but the only thing changed is the kernel version... It > may be also that some kernel API have changed and the driver is using > parts that weren't there before. > > Anyway, I've looked into 'intel' X driver sources and the version we > currently have (2.99.917) is the latest one. On the other hand, there > was over 800 commits since that release and some of them may be related. > For example maybe this: https://bugs.freedesktop.org/show_bug.cgi?id=105886 > > This suggests you may want to try enabling or disabling composition, if > i3wm supports it. > >> Duckduckgo-ing the error message yielded a few [1][2] Arch Linux bug >> reports describing the same symptoms. The first bug report also has a >> kernel patch [3] linked, which supposedly fixes the issue (haven't tried >> it). > > That patch is from 2014, already included in 3.19+ > >> [1] https://bugs.archlinux.org/task/43143 >> [2] https://bugs.archlinux.org/task/55732 >> [3] >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d472fcc8379c062bd56a3876fc6ef22258f14a91 Update! Managed to get rid of the error (and more importantly, the annoying artifacts) by forcing Xorg to use the generic modesetting driver instead of i915/i965. Steps (all commands in dom0): 1) check the driver currently in use (`xrandr --listproviders`), it's the last string (should be "name:Intel" now) 2) create file /etc/X11/xorg.conf.d/20-intel.conf (as root) with the following contents (also make sure there are no other files in that directory with "Device" "Driver" set to "intel"): > Section "Device" > Identifier "Intel Graphics" > Driver "modesetting" > Option "AccelMethod" "glamor" > Option "DRI" "3" > EndSection 3) restart the X server (eg. using `sudo systemctl restart lightdm`) 4) use the same xrandr command as in step 1, the driver should now be "modesetting" and you should see no errors in /var/log/Xorg.0.log, nor any graphical artifacts As a side note, I discovered a reliable reproducer for the issue: run `glxgears` in dom0 and then start thunderbird in some appvm. For me, this always triggered the i915 bug (logged in /var/log/Xorg.0.log) and the gears stopped turning (due to the acceleration being disabled, I guess). My hardware (sorry for not mentioning this earlier): Lenovo T480s with i7-8650U, no discrete GPU. Pages that have been helpful: * https://wiki.gentoo.org/wiki/Intel#Modesetting_DDX * https://ask.fedoraproject.org/en/question/130414/enabling-glamordri3-fedora-29-gnome-xorg/ * https://www.reddit.com/r/Fedora/comments/5uo6ta/modesetting_driver_fedora_25/ * https://www.phoronix.com/scan.php?page=news_item&px=Fedora-Xorg-Intel-DDX-Switch Cheers, Patrik -- 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 h
Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/24/19 5:18 PM, Patrik Hagara wrote: > I get weird graphical artifacts with the new kernel after ~an hour > of usage. Windows from AppVMs turn all white sometimes when > switching workspaces in i3wm. Events like mousing over an > interactive table rows in a browser (when the current row gets > highlighted) return that particular section of the window back to > normal (but not the whole window, for that I need to trigger a > repaint of the whole window by eg. making it full-screen and > immediately switching back to non-full-screen). > > Haven't had to time to debug this issue yet, will look closer over > the next weekend or two. For now I've reverted to using the old > kernel from stable repo and the issue went away. > I am also getting graphical artifacts with KDE. Although I think that I also had some in the past now they appear very soon. Sometimes I have to close and reopen a window because it stops redrawing except I move or resize it. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEznLCgPSfWTT+LPrmFBMQ2OPtCKUFAlxMRz8ACgkQFBMQ2OPt CKWgIA/+ISduFIH5euTsqOzUGnoaxC0xK4PG/tdkMoIHEnIwOt6Zd0hTkNhDSXwv YelHOiL3WVlNvVxG4ZAahJsDrUdA7MR98nHd4rDlc53htmH+7ZhD6rVEJMRzEbIU zbT0Ipwv0I5lsd/cXKY0bZq4Dp8scdpm4qF9hVBRayDynU4w6KrqbMzvhSMbV84d Wz/34eGUAO0EHaYC8RFAqF84bpsdEALnJFQppIaPuj1wmFyiB4vURvNor5hYxmwi OYKiQrRr+QVN/eUJghXmbnruV9X1YtbZmTHD7+hQkWWRZ02nIsnQHJoHhGyDhGJd BNhnbpjAmZWMKe9UUiuVllWHgPre4s4e9T5EQBvf3dSmuVWKNASJkNDOe3sLLbKh zchsS+opGsKIo/wIojJQ0JsyRbwxgBlMmYbeiNHDyQVKb5/O1T4/8Q3iYO0sMD9D XuJUtD9Ip4/xH/H9QSL9kyiYEuoK2Pl8GWyeoCK6171IPJlwgvm7oxbIqYS5ckH2 /0NDnFJfhOG0PylCsIbLYBsPeYJ+yy8m7D22v8WkNSPfGtlqSwTUS7U8cOe8pX1r xZrs7rqJ/c+8wmy6ZIRZk8lYLMGXSf1LyCpJQJC9mDHDp1CoP/WV3HVDXBuovYye wWZdoxvh2jtdAkZOFAC9iw0EiUeDc9O3uccW/z+N8h+utC4XYx0= =f+V0 -END PGP SIGNATURE- -- 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/5992b29e-2f25-d4ae-1b22-2289464fad46%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Jan 25, 2019 at 01:58:59PM +0100, Patrik Hagara wrote: > On 1/24/19 5:18 PM, Patrik Hagara wrote: > > On 1/20/19 1:57 AM, Marek Marczykowski-Górecki wrote: > >> Hi all, > >> > >> There is updated "kernel" package available in current-testing > >> repository - it's a Linux long term support 4.19.x series, as an update > >> over 4.14.x before. Since the upgrade switches to the next major LTS > >> branch, I'll keep it in current-testing repository longer than usual 1-2 > >> weeks. This also applies to kernel package for VMs: kernel-qubes-vm. > >> Please report new issues the usual way, at qubes-issues[1], or > >> simply by replying here. In either case, please mark it clearly it > >> happens after updating to 4.19, preferably including a link to the > >> update: > >> https://github.com/QubesOS/updates-status/issues/850 > >> > >> 4.19.x kernel was already available as kernel-latest package for some > >> time. Users of kernel-latest will see the update to 4.19.15 too, but > >> kernel-latest soon will carry 4.20.x kernel version. > >> > >> [1] https://github.com/QubesOS/qubes-issues/issues > >> > >> > > > > I get weird graphical artifacts with the new kernel after ~an hour of > > usage. Windows from AppVMs turn all white sometimes when switching > > workspaces in i3wm. Events like mousing over an interactive table rows > > in a browser (when the current row gets highlighted) return that > > particular section of the window back to normal (but not the whole > > window, for that I need to trigger a repaint of the whole window by eg. > > making it full-screen and immediately switching back to non-full-screen). > > The only error message I've been able to find so far is in dom0 Xorg log: > > > (EE) intel(0): Failed to submit rendering commands (Bad address), > disabling acceleration. This is very likely related. Normally I'd say "Bad address" indicate user-space issue, but the only thing changed is the kernel version... It may be also that some kernel API have changed and the driver is using parts that weren't there before. Anyway, I've looked into 'intel' X driver sources and the version we currently have (2.99.917) is the latest one. On the other hand, there was over 800 commits since that release and some of them may be related. For example maybe this: https://bugs.freedesktop.org/show_bug.cgi?id=105886 This suggests you may want to try enabling or disabling composition, if i3wm supports it. > Duckduckgo-ing the error message yielded a few [1][2] Arch Linux bug > reports describing the same symptoms. The first bug report also has a > kernel patch [3] linked, which supposedly fixes the issue (haven't tried > it). That patch is from 2014, already included in 3.19+ > [1] https://bugs.archlinux.org/task/43143 > [2] https://bugs.archlinux.org/task/55732 > [3] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d472fcc8379c062bd56a3876fc6ef22258f14a91 > > Cheers, > Patrik - -- 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/THMrX1ywFAlxLGisACgkQ24/THMrX 1yyRKwf9G9TX89Bh2aePabdq7k40zDEHK68sKmsbL7xcm0JpfsdXHK/MuM+B4AyJ BT7PrEIr8n1wXc++EArbtwapIPldICAhnBRK4fFdazHmtgAeW5S1GztAFisa4EaD w0AWDoLLVg4DR7AcwFi1EXse4jgT0/CSYkHIENM0QRl4uevEV6lKlpN4lS8Rgjm8 cUCXajC5RCLT3RVDUTzufUOxLLt/syRzGVtBsgJqCwvVdnOxArZqlEJgSI7wq9lN HR6OSv1ETGdlubxegn2LsAtqLvHXD+vnV11hgT4EvSZhHTfcbOI8FJdsnU8YxNY1 vsHV3L772QpTm3+jZ05X8AxJLEYrHA== =XaRm -END PGP SIGNATURE- -- 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/20190125141611.GH1429%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
On 1/24/19 5:18 PM, Patrik Hagara wrote: > On 1/20/19 1:57 AM, Marek Marczykowski-Górecki wrote: >> Hi all, >> >> There is updated "kernel" package available in current-testing >> repository - it's a Linux long term support 4.19.x series, as an update >> over 4.14.x before. Since the upgrade switches to the next major LTS >> branch, I'll keep it in current-testing repository longer than usual 1-2 >> weeks. This also applies to kernel package for VMs: kernel-qubes-vm. >> Please report new issues the usual way, at qubes-issues[1], or >> simply by replying here. In either case, please mark it clearly it >> happens after updating to 4.19, preferably including a link to the >> update: >> https://github.com/QubesOS/updates-status/issues/850 >> >> 4.19.x kernel was already available as kernel-latest package for some >> time. Users of kernel-latest will see the update to 4.19.15 too, but >> kernel-latest soon will carry 4.20.x kernel version. >> >> [1] https://github.com/QubesOS/qubes-issues/issues >> >> > > I get weird graphical artifacts with the new kernel after ~an hour of > usage. Windows from AppVMs turn all white sometimes when switching > workspaces in i3wm. Events like mousing over an interactive table rows > in a browser (when the current row gets highlighted) return that > particular section of the window back to normal (but not the whole > window, for that I need to trigger a repaint of the whole window by eg. > making it full-screen and immediately switching back to non-full-screen). The only error message I've been able to find so far is in dom0 Xorg log: > (EE) intel(0): Failed to submit rendering commands (Bad address), disabling acceleration. Duckduckgo-ing the error message yielded a few [1][2] Arch Linux bug reports describing the same symptoms. The first bug report also has a kernel patch [3] linked, which supposedly fixes the issue (haven't tried it). [1] https://bugs.archlinux.org/task/43143 [2] https://bugs.archlinux.org/task/55732 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d472fcc8379c062bd56a3876fc6ef22258f14a91 Cheers, Patrik -- 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/aa46442c-52b2-0ee2-1b1b-fb9138114ad1%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
On 1/20/19 1:57 AM, Marek Marczykowski-Górecki wrote: > Hi all, > > There is updated "kernel" package available in current-testing > repository - it's a Linux long term support 4.19.x series, as an update > over 4.14.x before. Since the upgrade switches to the next major LTS > branch, I'll keep it in current-testing repository longer than usual 1-2 > weeks. This also applies to kernel package for VMs: kernel-qubes-vm. > Please report new issues the usual way, at qubes-issues[1], or > simply by replying here. In either case, please mark it clearly it > happens after updating to 4.19, preferably including a link to the > update: > https://github.com/QubesOS/updates-status/issues/850 > > 4.19.x kernel was already available as kernel-latest package for some > time. Users of kernel-latest will see the update to 4.19.15 too, but > kernel-latest soon will carry 4.20.x kernel version. > > [1] https://github.com/QubesOS/qubes-issues/issues > > I get weird graphical artifacts with the new kernel after ~an hour of usage. Windows from AppVMs turn all white sometimes when switching workspaces in i3wm. Events like mousing over an interactive table rows in a browser (when the current row gets highlighted) return that particular section of the window back to normal (but not the whole window, for that I need to trigger a repaint of the whole window by eg. making it full-screen and immediately switching back to non-full-screen). Haven't had to time to debug this issue yet, will look closer over the next weekend or two. For now I've reverted to using the old kernel from stable repo and the issue went away. Cheers, Patrik -- 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/8f187918-75d0-abd0-d068-e8336511c374%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
On 2019-01-20 00:57, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi all, > > There is updated "kernel" package available in current-testing > repository - it's a Linux long term support 4.19.x series, as an update > over 4.14.x before. Since the upgrade switches to the next major LTS > branch, I'll keep it in current-testing repository longer than usual 1-2 > weeks. This also applies to kernel package for VMs: kernel-qubes-vm. > Please report new issues the usual way, at qubes-issues[1], or > simply by replying here. In either case, please mark it clearly it > happens after updating to 4.19, preferably including a link to the > update: > https://github.com/QubesOS/updates-status/issues/850 > > 4.19.x kernel was already available as kernel-latest package for some > time. Users of kernel-latest will see the update to 4.19.15 too, but > kernel-latest soon will carry 4.20.x kernel version. > > [1] https://github.com/QubesOS/qubes-issues/issues > > - -- > 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/THMrX1ywFAlxDx4YACgkQ24/THMrX > 1ywtlgf9HE/mQmGQIZtymeLHdeAP6FnpBhGrbaJESWM2AhFxRFIQpGLEBIIrpKvH > K6aFYqbFPNHYPE2DnboHmHebP1But8krrSbi4Ig5Z6E1pTFIk9XTrPQSbyY8jei9 > hGY6Y8NRdTB3ljAbQpdLmfvmq9LksBQox9V5v+7lbNd6IhFOuqYnfcjz/P6PWO/F > Np/orRT2QEB5Hzuqgm8dnfKUY1NBiwE1Nbxe2vl9OqrEkpceo4sKpBhEpF3LX7Z4 > aTjroOnfk4Hrb2souyTKuVhRaBdHP3wxxof+xNcsakFQNp96Jeh/2b/+im6CSaEa > 9BUaPC82RwFT//o8TvYwyybX8wuLpg== > =nKaU > -END PGP SIGNATURE- Feedback The only minor bug I've noticed is: the encrypted disk password gui screen is missing at login. However, login remain available via terminal -- 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/e34715ac1a25c72b44182215d6ae57b3%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
Well... Keep it. All CPUs are coming up and for the first time since the 4.0 release touchpad and track point are working on Lenovo P52. And all of the things that got successively worse to 4.19.12 are gone. Achim -- 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/c020b30dfe9782f63370ab6cbc68ba55b5fccb71.camel%40noses.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, There is updated "kernel" package available in current-testing repository - it's a Linux long term support 4.19.x series, as an update over 4.14.x before. Since the upgrade switches to the next major LTS branch, I'll keep it in current-testing repository longer than usual 1-2 weeks. This also applies to kernel package for VMs: kernel-qubes-vm. Please report new issues the usual way, at qubes-issues[1], or simply by replying here. In either case, please mark it clearly it happens after updating to 4.19, preferably including a link to the update: https://github.com/QubesOS/updates-status/issues/850 4.19.x kernel was already available as kernel-latest package for some time. Users of kernel-latest will see the update to 4.19.15 too, but kernel-latest soon will carry 4.20.x kernel version. [1] https://github.com/QubesOS/qubes-issues/issues - -- 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/THMrX1ywFAlxDx4YACgkQ24/THMrX 1ywtlgf9HE/mQmGQIZtymeLHdeAP6FnpBhGrbaJESWM2AhFxRFIQpGLEBIIrpKvH K6aFYqbFPNHYPE2DnboHmHebP1But8krrSbi4Ig5Z6E1pTFIk9XTrPQSbyY8jei9 hGY6Y8NRdTB3ljAbQpdLmfvmq9LksBQox9V5v+7lbNd6IhFOuqYnfcjz/P6PWO/F Np/orRT2QEB5Hzuqgm8dnfKUY1NBiwE1Nbxe2vl9OqrEkpceo4sKpBhEpF3LX7Z4 aTjroOnfk4Hrb2souyTKuVhRaBdHP3wxxof+xNcsakFQNp96Jeh/2b/+im6CSaEa 9BUaPC82RwFT//o8TvYwyybX8wuLpg== =nKaU -END PGP SIGNATURE- -- 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/20190120005742.GS1205%40mail-itl. For more options, visit https://groups.google.com/d/optout.
