PDA

View Full Version : [xubuntu] display problems - WHAT? acpi=force?



dan1973
April 24th, 2009, 08:19 AM
I am setting up a number of old IBM Thinkpad laptops with Xubuntu for resale.

Mostly gone without problems - 12 A22m's already done!

I have come to a sticking point with the latest few machines, a A20m, and an A20p and one A22m.

PROBLEM: when installing xubuntu, selection of language screen OK,

option screen where select to install OK

straight after this the following message appears for a brief moment:


ACPI: BIOS age 1999 fails cutoff 2000 acpi=force is required to enable ACPI


The install continues until the beginning of the installation stages when the display 'fractures' into two kind of mirrored halves and remains like this.

How do I fix this?

Any ideas much appreciated,

inobe
April 24th, 2009, 08:29 AM
the bios date is from 99' there are acpi issues for that year and before.


can you find and upgrade your bios to a newer version ?

inobe
April 24th, 2009, 08:35 AM
did research on those models for you.

http://www-307.ibm.com/pc/support/site.wss/MIGR-4JSQHA.html

dan1973
April 24th, 2009, 09:02 AM
Thanks for the link, will be trying the update in a short while, fingers crossed.

inobe
April 24th, 2009, 09:06 AM
haven't flashed a bios manually in a long time, just thinking about those days makes the hair stand on the back of my neck !

goodluck dan

dan1973
April 24th, 2009, 09:38 AM
Unfortunately, message was that BIOS is not in need of updating.

I have subsequently had one installation on an A20m machine go through this same 'acpi' message and install xubuntu without screen fragmentation problems.

Must start a new thread as this 'acpi' issue is obviously not the real problem.

Any further insights?

many thanks.

inobe
April 24th, 2009, 09:47 AM
dan this would be a great place to start >>click<< (http://www.google.com/search?q=ACPI%3A+BIOS+age+1999+fails+cutoff+2000+a cpi%3Dforce+is+required+to+enable+ACPI+&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:en-US:unofficial&client=firefox-a)

dan1973
April 24th, 2009, 10:55 AM
Thanks for the pointer 'forcing' worked to get rid of the error message but not the problem yet.

Screen still fractured.

inobe
April 24th, 2009, 08:43 PM
i still think the initial problem is related.

maybe if i post someone will see this thread.