[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-08-15 Thread the2nd
Am Samstag, 20. Mai 2017 21:42:50 UTC+2 schrieb Reg Tiangha: > People may not have noticed, but there is now a 4.9 kernel in > current-testing (4.9.28 to be specific). > > If the release schedule holds, then that should be migrated to stable > soon, however, before that happens, some feedback on t

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-08-11 Thread lokedhs
The machine I'm testing on is a Dell Latitude E7470. > 1) Hardware that used to work with 4.4 or 4.8 no longer works with 4.9. The computer now greets me with a black screen (hung? I don't know) when coming out of sleep. Thankfully I don't usually put the machine to sleep, so I can live with it

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-08-11 Thread lokedhs
On Monday, 31 July 2017 11:11:58 UTC+8, lok...@gmail.com wrote: > > 2) Hardware that didn't work with 4.4 or 4.8 still doesn't work. > > I can now disable tap-to-click. Finally! Note that I quoted the wrong question here. It didn't work in the old version, but works with 4.9. -- You received

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-07-24 Thread Epitre
Hello, just a small ping to know if it is the good place to ask this question. Thank you. Le mardi 11 juillet 2017 09:11:54 UTC+2, Epitre a écrit : > > Dear all, > > I'm experiencing the same problem as described here > https://bugs.freedesktop.org/show_bug.cgi?id=94990 since kernel 4.9 (even

Re: [qubes-users] [qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-07-06 Thread 0spinboson
fyi: Ryzen pinctrl/gpio issue should be fixed in 4.11.9; not yet backported to 4.9: commit 0ec03ce7d79dc9a5c47d26bab38c78075d42de9c Author: Thomas Gleixner Date: Tue May 23 23:23:32 2017 +0200 pinctrl/amd: Use regular interrupt instead of chained commit ba714a9c1dea85e0bf2899d02d

Re: [qubes-users] [qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-07-05 Thread Ryan Tate
> On Jun 21, 2017, at 3:01 PM, Ryan Tate wrote: > > On Thursday, June 1, 2017 at 10:00:09 AM UTC-4, Pablo Di Noto wrote: > 4) General feedback on the 4.9 kernel. Oh, yeah... I have started experiencing quite annoying internet connectivity issues, very, very difficulty to tro

Re: [qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-06-01 Thread Patrik Hagara
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, Jun 1, 2017 at 4:00 PM, Pablo Di Noto wrote: >> >> 4) General feedback on the 4.9 kernel. >> > >> > Oh, yeah... I have started experiencing quite annoying internet >> > connectivity issues, very, very difficulty to troubleshot. Symptoms are

Re: [qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-06-01 Thread Pablo Di Noto
> > Experiencing consistently the "no wifi after resume" which was working fine > > with 4.4.x > > This can be avoided by adding "iwldvm iwlwifi" line to > the following file in your WiFi NetVM: > /rw/config/suspend-module-blacklist Thanks! Found the specific thread (https://groups.google.co

Re: [qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-06-01 Thread Patrik Hagara
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, Jun 1, 2017 at 2:55 PM, Pablo Di Noto wrote: > Hello, > >> 1) Hardware that used to work with 4.4 or 4.8 no longer works with 4.9. > > Using it on a Lenovo X250 (i3-5010U), and other desktops. > > Experiencing consistently the "no wifi after

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-06-01 Thread Pablo Di Noto
Hello, > 1) Hardware that used to work with 4.4 or 4.8 no longer works with 4.9. Using it on a Lenovo X250 (i3-5010U), and other desktops. Experiencing consistently the "no wifi after resume" which was working fine with 4.4.x > 4) General feedback on the 4.9 kernel. Oh, yeah... I have started

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-05-24 Thread Foppe de Haan
On Tuesday, May 23, 2017 at 6:40:47 PM UTC+2, Reg Tiangha wrote: > On 05/23/2017 10:37 AM, Foppe de Haan wrote: > > It failed to load that module on my PC. (That is, modprobe gave a 'not > > found' error, and keyboard didn't work.) > > Would you be willing to compile the version found here and he

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-05-24 Thread Foppe de Haan
On Tuesday, May 23, 2017 at 5:08:50 PM UTC+2, Reg Tiangha wrote: > On 05/23/2017 04:41 AM, Foppe de Haan wrote: > > Done and did run into something somewhat important (usb keyboard/mouse > > pass-through no longer functioning properly). I have the same issue with my > > own kernel/vm-kernel build

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-05-24 Thread Foppe de Haan
On Tuesday, May 23, 2017 at 6:11:07 PM UTC+2, Reg Tiangha wrote: > On 05/23/2017 09:59 AM, Foppe de Haan wrote: > > mouse+kb connected through sys-usb, yes. I have a ps/2 keyboard for > > 'emergencies', but since it's shit, I prefer not to use it. :) > > Anyway, have rebuilt my own kernel with the

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-05-24 Thread cyrinux
Thanks I have done this, i will try next 4.9.29 ;) Le mercredi 24 mai 2017 20:43:11 UTC+2, Reg Tiangha a écrit : > On 05/24/2017 12:37 PM, cyrinux wrote: > > Hi, > > > > I have a T450s, and it works well, just this: > > > > Seems to have a problem for me, i often miss wireless after suspend. > > I

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-05-24 Thread Cyril
Problem disappears following https://www.qubes-os.org/doc/wireless-troubleshooting/ Le mercredi 24 mai 2017 20:37:05 UTC+2, Cyril a écrit : > > Hi, > > I have a T450s, and it works well, just this: > > Seems to have a problem for me, i often miss wireless after suspend. > I need to stop fire

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-05-24 Thread cyrinux
Hi, I have a T450s, and it works well, just this: Seems to have a problem for me, i often miss wireless after suspend. I need to stop firewall and wlan vm to reload iwlwifi driver. No easy to unload iwlwifi, faster to stop and start. I don't remember i have this problem before. No other problems

[qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-05-23 Thread Foppe de Haan
Done and did run into something somewhat important (usb keyboard/mouse pass-through no longer functioning properly). I have the same issue with my own kernel/vm-kernel builds, not yet figured out what's causing this. -- You received this message because you are subscribed to the Google Groups