Page 19 of 22

Porteus 5.0 RC2 bug reports

Posted: 03 Jan 2021, 01:10
by cad
beny wrote:
02 Jan 2021, 21:49
hi,maybe not work but append this line to porteus.config: i8042.nopnp initcall_blacklist=dw_i2c_init_driver to try touchpad working
LABEL arch-5.10.2
MENU LABEL slack-5.10.2
LINUX ../vmlinuz-5.10.2-zen1
APPEND root=UUID=xxxxxxxxxx rw i8042.nopnp initcall_blacklist=dw_i2c_init_driver
INITRD ../initrd.xz
I tried appending, as per your suggestion:

Code: Select all

i8042.nopnp initcall_blacklist=dw_i2c_init_driver
but touchpad still did not work, just as before.
Then I also tried appending:

Code: Select all

i8042.nopnp=1 initcall_blacklist=dw_i2c_init_driver
and, later:

Code: Select all

i8042.nopnp=1 pci=nocrs
but none of the above could get my Lenovo IdeaPad's touchpad to work. This with Blaze's newest 5.10.4 (Jan 1st) kernel.

Then I tried all of the above with the original Porteus 5.0rc2 5.4.57 kernel. Still, no joy.

Porteus 5.0 RC2 bug reports

Posted: 03 Jan 2021, 10:14
by beny
Michael Reutman (mreutman) wrote on 2020-08-25: #53

Hello,

I was able to get the touchpad working on my Lenovo Ideapad 3 15iil05 to function by adding the following arguments to GRUB_CMDLINE_LINUX_DEFAULT.

"i8042.nopnp=1 pci=nocrs"

I'm curious as to what this does that makes it work, but I can report that my touchpad works and I have full control of my mouse (one and two finger gestures work just fine).

Hopefully this helps.
the link to this tread:https://bugs.launchpad.net/ubuntu/+sour ... ug/1880172, maybe can help you.

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 00:08
by cad
beny wrote:
03 Jan 2021, 10:14
Michael Reutman (mreutman) wrote on 2020-08-25: #53

Hello,

I was able to get the touchpad working on my Lenovo Ideapad 3 15iil05 to function by adding the following arguments to GRUB_CMDLINE_LINUX_DEFAULT.

"i8042.nopnp=1 pci=nocrs"

I'm curious as to what this does that makes it work, but I can report that my touchpad works and I have full control of my mouse (one and two finger gestures work just fine).

Hopefully this helps.
the link to this tread:https://bugs.launchpad.net/ubuntu/+sour ... ug/1880172, maybe can help you.
Well, that's exactly one of the arguments I tried appending yesterday (as described in my previous post), but it did not work in my case. Thank you for posting that link, I'll check it out.

Initially, I thought it might have been caused by the Porteus kernel not supporting it. But today I looked into the latest kernel (ver. 5.10.4) and it looks like all that is necessary for the Lenovo IdeaPad touchpad (Elan and Elantech support) is already there. However, "Elan touchpad" (or something similar) does not show up in neither /var/log/messages or /var/log/dmesg, so apparently it is not being properly recognized. All I get in reference to a mouse device in both of those files is:

Code: Select all

mousedev: PS/2 mouse device common for all mice
and

Code: Select all

input: IdeaPad extra buttons as /device/pci000[SNIP...]

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 03:33
by Rava
System 5.0rc2 with 003-xfce-4.12-20201108.xzm

/opt/porteus-scripts/xpsinfo aka 'Porteus System Info' ends with this:

Code: Select all

/bin/sh: -c: line 1: syntax error: unexpected end of file
Traceback (most recent call last):
  File "/opt/porteus-scripts/xpsinfo", line 360, in <module>
    class XPSInfo(Gtk.Window):
  File "/opt/porteus-scripts/xpsinfo", line 361, in XPSInfo
    system_info = PSInfo()
  File "/opt/porteus-scripts/xpsinfo", line 20, in __init__
    self.init_infos()
  File "/opt/porteus-scripts/xpsinfo", line 255, in init_infos
    fd.write( f.read() )
  File "/usr/lib64/python3.8/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 6429: invalid start byte

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 05:56
by roadie
cad wrote:
04 Jan 2021, 00:08
beny wrote:
03 Jan 2021, 10:14
Michael Reutman (mreutman) wrote on 2020-08-25: #53

Hello,

I was able to get the touchpad working on my Lenovo Ideapad 3 15iil05 to function by adding the following arguments to GRUB_CMDLINE_LINUX_DEFAULT.

"i8042.nopnp=1 pci=nocrs"

I'm curious as to what this does that makes it work, but I can report that my touchpad works and I have full control of my mouse (one and two finger gestures work just fine).

Hopefully this helps.
the link to this tread:https://bugs.launchpad.net/ubuntu/+sour ... ug/1880172, maybe can help you.
Well, that's exactly one of the arguments I tried appending yesterday (as described in my previous post), but it did not work in my case. Thank you for posting that link, I'll check it out.
cad,
I'm a bit surprised that the touchpad isn't working with Blaze's kernel as it does with mine. I'm assuming though that yours needs the same kernel options due to being AMD and that may not be the case. There's obviously something missing. My touchpad was a learning exercise, for sure. It was what got me started in compiling my own kernels.

Does anything show up in:

Code: Select all

dmesg | grep ELAN
or:

Code: Select all

lspci -k
The sites I saw are reporting an Elan touchpad in the newer Lenova machines, but if the kernel driver isn't there, it's doubtful that dmesg will show anything, it didn't for me without the module.

I found an option for Lenova touchpads to be used on the command line, but I think your answer will be in the kernel.

Code: Select all

ivrs_ioapic[32]=00:14.0

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 06:38
by cad
Hi roadie,

I just gave additional information about this issue by editing my previous post #273 in this thread, before seeing your post. To make a long story short, Blaze's 5.10.4 kernel did not get my laptop's touchpad to work. I looked today into his 64bit.config file and it seems that all required support for ELAN is already in there, either compiled directly into the kernel or as a module.
As to your suggestions:

Code: Select all

dmesg | grep ELAN
gives nothing ("ELAN" is not found in /var/log/dmesg)

Code: Select all

lspci -k
does not show any touchpad/mouse as being recognized. Also, I tried appending:

Code: Select all

ivrs_ioapic[32]=00:14.0
but that argument does not change a thing.

What did you change in your kernel in order to get your ELAN touchpad to work? Did you modify kernel 5.10.4 or an earlier one?

I asked peebee in this thread viewtopic.php?p=80820#p80820 whether he could gracefully provide a download link for his new aufs5 patch set for kernel 5.10.4. I can't wait to start tinkering with it...
But, again, everything seems to be already in there to support the ELAN touchpad. The only thing I noticed missing is "IdeaPad Laptop Slidebar support" (CONFIG_INPUT_IDEAPAD_SLIDEBAR) in Device Drivers/Input device support/Miscellaneous devices, but I am pretty much sure this is not related to supporting my laptop's ELAN touchpad at all.

Thanks again for the

Code: Select all

amdgpu.dc=0
argument for the AMD graphics card. Even though, as you say, you did not generate it, you were the one to so gracefully provide it. It helped immensely! :)

EDIT: I read your post again, and you made it clear Blaze's kernel did the trick for you. So, please disregard my question above.

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 10:53
by beny
hi cad from the arch forum if you have an amd cpu on:
I have a Lenovo Ideapad 320-15ABR with an Elantech touchpad. I tried enable the Elantech and I2C options in my kernel to no avail. I then tried setting CONFIG_PINCTRL_AMD=y in my configuration and the touchpad worked in my new kernel.
this is a blaze task.....

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 11:50
by babam

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 16:14
by cad
beny wrote:
04 Jan 2021, 10:53
hi cad from the arch forum if you have an amd cpu on:
I have a Lenovo Ideapad 320-15ABR with an Elantech touchpad. I tried enable the Elantech and I2C options in my kernel to no avail. I then tried setting CONFIG_PINCTRL_AMD=y in my configuration and the touchpad worked in my new kernel.
this is a blaze task.....
Thank you beny for your kernel related suggestion. I would do it myself and then post results here. Now that a suitable aufs5 patch set for kernel 5.10.4 is available, all I need is a compiler (05-devel.xzm module?) to start making changes to the kernel. Where to find said compiler for 5.10.4?

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 16:18
by cad
Now that kernel 5.10.4 has been "adopted" by the Porteus team, I'd like to start working and experimenting with that...
Thanks for your suggestion, though. :)

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 16:48
by babam
cad wrote:
04 Jan 2021, 16:18
Now that kernel 5.10.4 has been "adopted" by the Porteus team, I'd like to start working and experimenting with that...
I suggest you try this kernel first because it already has CONFIG_PINCTRL_AMD=y

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 17:10
by cad
babam wrote:
04 Jan 2021, 16:48
I suggest you try this kernel first because it already has CONFIG_PINCTRL_AMD=y
OK, it makes sense. So I'll give it a try and report here afterwards. The latest Blaze 5.10.4 kernel has it compiled as a module (CONFIG_PINCTRL_AMD=m), I just checked. I will give 5.4.67 a try and report results here. Thanks!

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 18:19
by cad
babam wrote:
04 Jan 2021, 16:48
I suggest you try this kernel first because it already has CONFIG_PINCTRL_AMD=y
Gave it a try... We are heading in the right direction, but still not quite there:
With the 5.4.67 kernel you suggested, the touchpad still does not work and does not show up with

Code: Select all

lspci -k
However, now a

Code: Select all

dmesg | grep ELAN
command produces:

Code: Select all

[   27.174917] i2c_hid i2c-ELAN0666:00: i2c-ELAN0666:00 supply vdd not found, using dummy regulator
[   27.174940] i2c_hid i2c-ELAN0666:00: i2c-ELAN0666:00 supply vddl not found, using dummy regulator
whereas before the same command produced nothing at all, both with Blaze's latest kernel and the original 5.0rc2 kernel.
I also later tried appending the argument, at boot up:

Code: Select all

ivrs_ioapic[32]=00:14.0
but it did not change anything.
If this new result is due to CONFIG_PINCTRL_AMD=y in your suggested kernel 5.4.67 or to something else, I do not know.

Need to take off now. Will be back tonight (in about 10 hours) to check posts.

Porteus 5.0 RC2 bug reports

Posted: 04 Jan 2021, 18:38
by joejac
Hello and I wish you all a Happy and Successful 2021.
Are there any news on the final release of Porteus 5?
Best regards
joejac

Porteus 5.0 RC2 bug reports

Posted: 07 Jan 2021, 14:26
by babam
cad wrote:
29 Dec 2020, 05:18
Lenovo IdeaPad Slim's touchpad is not supported in latest 5.0 RC2

This is the latest generation of the Lenovo IdeaPad Slim laptops, featuring a Buttonless Mylar® surface multi-touch touchpad.
cad, try this kernel Porteus Kernel Builder (Пост Blaze #80931)