Reason I ask is because it has RAID6 algo fixed to AVX2(*) which (I think) the Celeron doesn't support.
(*) Normally the algo is tested at boot and it chooses the best one, but it costs a tiny amount of time. This has been patched so that you can choose the algo in kernel config without testing it at boot.
[ +0,009562] raid6: Forced to use recovery algorithm avx2x2
[ +0,000001] raid6: Forced gen() algo avx2x4
Here's the inxi of said machine:
CPU: Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP L2 cache: 6144 KiB
Speed: 700 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 700 2: 700 3: 700 4: 700 5: 700 6: 700 7: 700 8: 700
While getting the data I noticed that there are quite a few of these...
ACPI Error: Aborting method \_TZ.FNCL due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
…
[Di Sep 10 08:33:03 2019] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[Di Sep 10 08:33:03 2019] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0
[Di Sep 10 08:33:03 2019] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
...in dmesg, they may mess up the messages we want to see from the new kernel?
Think I need to do a BIOS upgrade first, which requires Windows 
, and I can't just boot from my dirty Windows USB drive, tried that before...need to swap the internal drive
One of these cases where something small leads to a cascade of other actions...
Thanks for reporting, unfortunately I have no clue where the error comes from.
AER is advanced error recovery for PCIe, which can be disabled with boot parameter pci=noaer. Doesn't solve the problem but should get rid of the messages.
Wait... is this on my kernel or Manjaro's, or both?
Don't worry, not your kernel yet 
This is the default Manjaro Stable one (5.2.11-1-MANJARO), but I was wondering if it doesn't make more sense to sort out these errors first before we switch the kernel, otherwise we won't know where potential new errors come from.
And getting rid of the existing errors will include the BIOS upgrade which in turn requires.....and on and on it goess
Well it would make sense, but if your computer runs well even with these errors (it says "corrected" after all) then I don't think we should worry.
However it would be interesting to know where the errors come from.
What device is 0000:00:1c.0?
See lspci.
FOLLOW >>
Ignore.
Thanks!
The machine seems to be fine re. the Atheros driver.
sudo dmesg|grep firmware|grep ath10k_pci
Gives me a similar, error free result.
The PCI are gone thanks to this:
And I understand I can ignore ACPI errors. And while I was on the case I also fixed the quiet boot so my wife doesn't get to see the error messages during boot
Everythings fixed now...
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
Handle 0x0019, DMI type 9, 17 bytes
System Slot Information
Designation: J6C1
Type: x1 PCI Express x1
Current Usage: In Use
Length: Other
ID: 1
Characteristics:
PME signal is supported
Hot-plug devices are supported
Bus Address: 0000:00:1c.0
And now over to the actual topic of this thread
I can give it a try if it works and report back, what info do I need to provide about it? I am little new to Manjaro so I am not up to date on all, but I got experience running Linux.
Do you want the test done on a newer PC or older.
I can do it on a VirtualMachine Now, for a PC I can do it end of the week when I get my system76.
Ari.
Think I got the kernel running.
It's the 5.2.13-3-vd one is it?
So far no new error messages in dmesg, journalctl is clean but my touchpad isn't working any longer
Anything specific I should test?
It would already be enough if you checked journalctl/dmesg for errors like TomZ did, and just report on the "feeling" (faster, slower? more, less responsive?).
Thanks.
Also thanks to TomZ.
@TomZ, which touchpad is it? I don't think I have touched the touchpad drivers but mistakes happen...
Here's what's in dmesg with the regular kernel:
[Di Sep 10 08:33:02 2019] input: ELAN469D:00 04F3:304B Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN469D:00/0018:04F3:304B.0001/input/input9
[Di Sep 10 08:33:02 2019] hid-multitouch 0018:04F3:304B.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN469D:00 04F3:304B] on i2c-ELAN469D:00
With your modified kernel I can't find any entry with…
sudo dmesg -T | grep hid-multitouch
Do you know which module(s) it uses and try to load them manually?
Both HID_ELAN and HID_MULTITOUCH are enabled in the kernel, but maybe they have a dependency on a module which is not included.
Nevermind. Found the problem, i2c-designware is disabled for some reason. I'll reenable it.
Again, thanks for reporting.
I don't I am afraid, how can I find out?
And once I know, how do I load a module post boot?
Ok, I guess this means you will update github and then I will download and compile again?
Exactly I will update in the next few minutes. EDIT: done!
But you don't have to waste your time.
EDIT: @AstraAdria4Ari, I forgot to say that I didn't include VBox guest modules in case you want to run it in VBox. It should still work but without filesharing support.
thanks torvic,
I will give it I try when I get some more dedicated time to test it, with my new pc arrival in few days old will be great for beta testing. It is great that users can test out new kernels.
This is probably a Manjaro newbie question, but I use GNOME does that make a diference for the testing since I know KDE, XFCE and GNOME are official version, but XFCE is first version of all 3?
Ari.
No, it shouldn't make a difference.
I assumed just wanted to be sure, sorry for the newbie question and thanks on the input.
Ari.
5.2.14 is out now.
Maybe I'll upload a precompiled package of .14 later today (but not built in a clean chroot as I haven't yet found out how to pass GPG sig verification to buildpkg, if someone knows, please tell me).
No worries, I went ahead anyway
New kernel compiled and booted -> touchpad works!
And dmesg is still quiet...
Forum kindly sponsored by
