cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
FlyingKiwi311
Paper Tape
Posts: 2
Registered: ‎10-13-2018
Location: AT
Views: 2,003
Message 31 of 178

Re: ThinkPad E485/E585 - Firmware bug ACPI IVRS table

Against the sporadic freezes the kernel parameter "idle=nomwait" seems to help (see https://bugs.freedesktop.org/show_bug.cgi?id=106658).

arcooke
Punch Card
Posts: 16
Registered: ‎08-31-2018
Location: US
Views: 1,925
Message 32 of 178

Re: ThinkPad E485/E585 - Firmware bug ACPI IVRS table

UPDATE:

 

It seems this may be a more widespread problem than just our Thinkpads.  See this thread, it's happening with other Raven Ridge laptops as well. Lots of discussion here:

 

https://bugzilla.kernel.org/show_bug.cgi?id=200087

 

Looks like this might be a multi-part problem that requires fixes on both the kernel and bios

Boppoo
Paper Tape
Posts: 2
Registered: ‎11-18-2018
Location: CN
Views: 1,710
Message 33 of 178

Re: ThinkPad E485/E585 - Firmware bug ACPI IVRS table

lenovo,amd,linux?
dcbbleo
Punch Card
Posts: 41
Registered: ‎10-20-2018
Location: CA
Views: 1,677
Message 34 of 178

Re: ThinkPad E485/E585 - Firmware bug ACPI IVRS table

Indeed. However,  I would order them as AMD > Linux > Lenovo because amd should definitely be first to provide integrators with proper specs and tools to implement their CPU features.

 

Linux should be able to fall back to normal enumeration just like Windows is doing at the moment and finally Lenovo should at least provide an option to disable the iommu or just disable it altogether until amd gets it working.

 

 

Ziniral
Fanfold Paper
Posts: 14
Registered: ‎09-14-2018
Location: DE
Views: 1,426
Message 35 of 178

Re: ThinkPad E485/E585 - Firmware bug ACPI IVRS table

There are notebooks with the same Ryzen CPU (Ryzen 3/5/7) and the same chipset that are working completly perfectly fine with Linux. So the problem here lies clearly at Lenovo, which has to fix the BIOS bug. And even if the bug is not in the BIOS, they have to report it to AMD and the Linux Kernel Team. Since there is still not any mention of the E585 or E485 in the kernel bug report, it seems Lenovo employees still did not have taken any action in the case. No Lenovo employee has made inquiries to the Linux Kernel Team, because the not-working Lenovo notebooks are not even mentioned there.  So I only make Lenovo responsible for there faineance and the guilt lies by them.

Ziniral
Fanfold Paper
Posts: 14
Registered: ‎09-14-2018
Location: DE
Views: 1,415
Message 36 of 178

Re: ThinkPad E485/E585 - Firmware bug ACPI IVRS table

Now I wrote a comment in the Linux bug report, so that the Linux Kernel Team is at least aware of that critical bug.

 

Only if we make pressure on all sides something will change.

arcooke
Punch Card
Posts: 16
Registered: ‎08-31-2018
Location: US
Views: 1,409
Message 37 of 178

Re: ThinkPad E485/E585 - Firmware bug ACPI IVRS table

I'm honestly doubting we're going to get any help with this.  I contacted Lenovo support on Twitter about bluetooth not working in Linux, and they promptly directed me to a page stating that linux is not supported on this laptop.  The same issue was already fixed in a bios update on the A485, but they didn't apply the fix to the E-series.  I asked them to please forward my email on to the bios developers anyway, because they might be able to essentially just copy/paste the fix.. he said he would, but who knows.

 

LLYZyJu

 

The short url links to here:

https://support.lenovo.com/us/en/solutions/pd031426?Source=social_eservices&Medium=TWITTER&Term=eSer...

 

Fixed in bios 1.06 on A485:

<1.06>   
- [Important] Fixed an issue that the BT status can't be got in Linux.

https://download.lenovo.com/pccbbs/mobiles/r0wuj43w.txt

 

 

It's frustrating.  The reason I chose the E-series over the A-series is that having a number pad is important to me, if I wanted a Ryzen thinkpad, it was my only option.

Highlighted
Ziniral
Fanfold Paper
Posts: 14
Registered: ‎09-14-2018
Location: DE
Views: 1,401
Message 38 of 178

Re: ThinkPad E485/E585 - Firmware bug ACPI IVRS table

This seems for me just a lame excuse. I mean we still speak about a ThinkPad. The ThinkPad is Lenovos high-quality product class with a high reputation in businesses. Even if it's just a E585 or E485, its still part of Lenovos highest-quality notebook product class. If this goes to the press that Linux is still not working after a half a year and Lenovo does not care any about it, that would not make a good impression to Lenovo's standing in the public.

 

I now also wrote a support ticket to Lenovo, maybe it helps a little. Everyone who has this problem, should also write a support ticket to Lenovo.

Xepter
Fanfold Paper
Posts: 9
Registered: ‎08-28-2018
Location: AU
Views: 1,378
Message 39 of 178

Re: ThinkPad E485/E585 - Firmware bug ACPI IVRS table

Honestly very disappointed with Lenovo after all the good things I've heard about them. This behaviour from them is quite disgusting in response to valid issues with their products. Similar thing happened to us a few months ago with the laggy keyboard issue. Took them AGES to finally release a patch after substantial pressure from the community and even worse was that they didn't even address the issue in the BIOS changelog... Which is why I went Googling before applying the latest BIOS update. For those having suspend issues, there's another forum post here outlining a fix. Still haven't updated BIOS because of it. Paid for a professional laptop to do work on, not to beta test for Lenovo.

Hans0815
Ctrl-Alt-Del
Posts: 7
Registered: ‎11-19-2018
Location: DE
Views: 1,320
Message 40 of 178

Re: ThinkPad E485/E585 - Firmware bug ACPI IVRS table

It is now two months since this thread started in the forum with not a single official statement or fix from Lenovo. Also the suspend-bug was not fixed for almost 5 months. We have just userspace-workarounds for both of them. Does Lenovo still plan to react on their broken BIOS-IVRS-Table and the broken suspend which seems to be introduced with their recent bios? "No support for Linux" is in my eyes not equal with "we build bugs inside our products and let consumers fix them with individual workarounds". Wouldn't it be far easier to publish a fixed UEFI and have those bugs fixed for all consumers at once? Also in terms of publicity?

There is no need to re-invent the wheel. I assume a high probability that some (slightly adapted) patch for A485 can be applied here.

Check out current deals!


Shop current deals

Top Kudoed Authors