Bug 237849 - lenovo X60 needs quirk in fdi file.
Summary: lenovo X60 needs quirk in fdi file.
Alias: None
Product: Fedora
Classification: Fedora
Component: hal-info   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: David Zeuthen
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-25 17:52 UTC by Dave Jones
Modified: 2015-01-04 22:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-07 01:33:57 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Dave Jones 2007-04-25 17:52:18 UTC
This needs to be added to
for suspend to ram to come back with video..

      <match key="system.hardware.product" prefix="63664DU">
        <merge key="power_management.quirk.vbe_post" type="bool">true</merge>

Comment 1 David Zeuthen 2007-04-25 20:33:47 UTC
Committed upstream


Will build a new hal-info release shortly.

Comment 2 David Zeuthen 2007-04-25 20:34:29 UTC
(reassigning to hal-info)

Comment 3 Matthias Clasen 2007-04-25 23:49:39 UTC
Whee, splitting off hal-info pays off already

Comment 4 Bryan O'Sullivan 2007-06-21 06:03:29 UTC
Here's another:

      <match key="system.hardware.product" prefix="1709">
        <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
        <merge key="power_management.quirk.s3_mode" type="bool">true</merge>

Comment 5 Dave Jones 2007-07-12 20:56:19 UTC
The original quirk I filed above is in the latest update, Bryan's doesn't seem
to be.  Bryan, what model laptop is that for ?   I'm guessing something like a T60 ?

Comment 6 Bryan O'Sullivan 2007-07-12 21:12:58 UTC
Dave, mine's an X60 as well, model 1709CTO.

Comment 7 Bryan O'Sullivan 2007-07-12 21:15:10 UTC
Jeremy Fitzhardinge mentioned something about his X60 still not resuming from
hibernate properly, even with my quirk present.  Maybe he can elaborate?

Comment 8 Jeremy Fitzhardinge 2007-07-12 21:21:06 UTC
Current FC7 kernel kernel-2.6.21-1.3228.fc7 does not resume for me.  On resume,
it sits there in text mode with "inux" in yellow in the upper-left of the screen
(first line, ~5-6 characters in from the edge).  The capslock light responds,
but attempting to switch to the X VT locks up the machine fully.

Current top-of-tree linux kernels built from git suspend and resume without

In addition to the quirk entry, I also boot with acpi_sleep=s3_bios, which is
what I needed to make FC6 suspend/resume properly.  It doesn't seem to make any
difference in this case, and I think its redundant anyway.

Comment 9 Bryan Che 2007-07-14 05:15:22 UTC
I have the same issues as Jeremy (comment #8) on my Thinkpad T60 with

Comment 10 Jeremy Fitzhardinge 2007-07-14 15:22:23 UTC
BTW, my machine is an X60, model 170997U.

Comment 11 Bug Zapper 2008-04-04 00:16:24 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 12 Bug Zapper 2008-05-07 01:33:56 UTC
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

Note You need to log in before you can comment on or make changes to this bug.