So, looking at the AML errors, I see:
line 2758: Name (_FDE, Package (0x05) // _FDE: Floppy Disk Enumerate
_FDE not used in the kernel, so this error can be ignored.
line 2897: This is a bug in the firmware, but I believe it won't do any
harm.
line 4413: Method OCOP: Method does not return a pac
Conclusion: Nothing we can fix and there is little to worry about. I
will mark it as "Won't Fix" if that's OK.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Thanks Colin,
that mobo is quite old, and there is no more firmware upgrade since a
while. The most trouble with that mobo is the boot process: need 2 cold
boot before the 3rd succeed (but that issue, existing since karmic, cant
be due to something else indeed, and had never been marrowed down)
I've added some more intelligence to fwts to give some better feedback
for some of the errors you see in the bug report. These will land in
fwts V0.26.05 or V0.26.06 depending on when the patches get pulled into
the release.
--
You received this bug notification because you are a member of Ubuntu
Most of the AML errors are due to sloppy coding by the firmware vendor,
for example, there are several mutex Acquires with timeouts that never
check if the timeout occurred and just carry on as if the mutex was
Acquired correctly. Also there are some methods that return values on
some paths of exe
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
