Toralf Förster | 1 Mar 09:40 2011
Picon
Picon

Re: ThinkPad T400 : should kernel option "reboot=pci" be hard coded ?


Pedro Ribeiro wrote at 07:01:28
> > Matthew Garrett wrote at 16:11:03
> > 
> >> No, the best thing to do would be to figure out what changed to require
> >> the extra 9 seconds. Are you able to work out which the last kernel
> >> release without this timeout was?
> > 

> I also have a T400, and reboot=pci solves the problem for me.
> 
> Just tested with kernel 2.6.20 and the 9 second boot delay is still
> there. Maybe this should be hardcoded...

I'd like to point to this after a half year of lthe last email. Shouldn't it 
be hard coded ?

--

-- 
MfG/Kind regards
Toralf Förster

pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

Matthew Garrett | 1 Mar 13:35 2011

Re: ThinkPad T400 : should kernel option "reboot=pci" be hard coded ?

On Tue, Mar 01, 2011 at 09:40:13AM +0100, Toralf Förster wrote:
> I'd like to point to this after a half year of lthe last email. Shouldn't it 
> be hard coded ?

Windows appears to have exactly the same behaviour, so it seems that 
this is working like designed.

--

-- 
Matthew Garrett | mjg59 <at> srcf.ucam.org
Picon

Re: [ibm-acpi-devel] ThinkPad T400 : should kernel option "reboot=pci" be hard coded ?

On Tue, 01 Mar 2011, Matthew Garrett wrote:
> On Tue, Mar 01, 2011 at 09:40:13AM +0100, Toralf Förster wrote:
> > I'd like to point to this after a half year of lthe last email. Shouldn't it 
> > be hard coded ?
> 
> Windows appears to have exactly the same behaviour, so it seems that 
> this is working like designed.

Which makes this "something we could ask Lenovo" about.  The standard rules
apply.  Assuming you do not have direct contacts in the Lenovo BIOS team
yourself, send me or to Thomas Renninger a full description of the observed
problem, and of our workaround, and what you'd like to know (e.g: what is
causing the delay?).

--

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
Vincent Batts | 2 Mar 05:18 2011

hello world, brightness fix?

this is a simple introduction, like a first meeting at a support group.
my name is Vincent, and i'm a thinkpad user...

But serious, i've been attempting to investigate the brightness issues
on the W510, when using the nvidia proprietary driver.
There had been a patch around 2.6.35.7, that did work successfully,
but no longer worked of 2.6.35.10 and subsequent kernels. I have
attached a copy of that patch.

I am happy provide information, or go on a rabbit hunt if someone can
point me in a direction of where to gather debugging information.

Take care,
vb
Attachment (kernel-thinkpad_acpi-brightness.patch): application/octet-stream, 3659 bytes
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
ibm-acpi-devel mailing list
ibm-acpi-devel@...
https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
Picon

Re: hello world, brightness fix?

On Tue, 01 Mar 2011, Vincent Batts wrote:
> But serious, i've been attempting to investigate the brightness issues
> on the W510, when using the nvidia proprietary driver.
> There had been a patch around 2.6.35.7, that did work successfully,
> but no longer worked of 2.6.35.10 and subsequent kernels. I have
> attached a copy of that patch.
> 
> I am happy provide information, or go on a rabbit hunt if someone can
> point me in a direction of where to gather debugging information.

We can't really help you in this forum, since that thinkpad does not use
thinkpad-acpi to handle brightness changes.

Still, post the *list of files* modified by the patch that used to work.
"lsdiff" will give you that.  That way we can at least tell you what was
being patched, and therefore we might be able to tell you where to look for
help.

--

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
(Continue reading)

Keith Packard | 14 Mar 07:52 2011

[PATCH] thinkpad-acpi: Some BIOS versions don't end in WW, remove check

My X201s BIOS version string is 6QET46V1 (1.16 ). The
EC version string is 6QHT28WW-1.09. The driver was requiring that both
of these have 'WW' in positions 6 and 7. I don't know what the
significance of having 'V1' there instead is, but removing the test
makes the driver load on my machine.

Signed-off-by: Keith Packard <keithp <at> keithp.com>
---
 drivers/platform/x86/thinkpad_acpi.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/drivers/platform/x86/thinkpad_acpi.c b/drivers/platform/x86/thinkpad_acpi.c
index eb99223..32f602e 100644
--- a/drivers/platform/x86/thinkpad_acpi.c
+++ b/drivers/platform/x86/thinkpad_acpi.c
 <at>  <at>  -8617,8 +8617,7  <at>  <at>  static bool __pure __init tpacpi_is_valid_fw_id(const char* const s,
 		tpacpi_is_fw_digit(s[1]) &&
 		s[2] == t && s[3] == 'T' &&
 		tpacpi_is_fw_digit(s[4]) &&
-		tpacpi_is_fw_digit(s[5]) &&
-		s[6] == 'W' && s[7] == 'W';
+		tpacpi_is_fw_digit(s[5]);
 }

 /* returns 0 - probe ok, or < 0 - probe error.
--

-- 
1.7.4.1

Henrique de Moraes Holschuh | 14 Mar 16:46 2011
Picon

Re: [PATCH] thinkpad-acpi: Some BIOS versions don't end in WW, remove check

On Sun, 13 Mar 2011, Keith Packard wrote:
> My X201s BIOS version string is 6QET46V1 (1.16 ). The

This is not marked as a production release.

> EC version string is 6QHT28WW-1.09. The driver was requiring that both
> of these have 'WW' in positions 6 and 7. I don't know what the
> significance of having 'V1' there instead is, but removing the test
> makes the driver load on my machine.

I also don't know what V1 is, but Lenovo has shipped ThinkPads with firmware
that was not supposed to get shipped to the production lines at least
once...

On this case, it looks like someone forgot to give the 6QET46 the "WW" stamp
of aproval, or they shipped the image to the factory from the wrong point in
the QA pipeline.

Here:
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-74983

You will find the "summarized" changelogs of the firmware for the X201 (and
it looks like it is a good idea to upgrade based on those alone).  Near the
end of the page, there is a complete list of released firmware:

release  BIOS (BIOS ID) ECP (ECP ID)
	
1.32 	1.32 (6QET62WW)	1.12/1.12 (6QHT31WW / 6SHT31WW)
1.31 	1.31 (6QET61WW)	1.12/1.12 (6QHT31WW / 6SHT31WW)
1.22 	1.22 (6QET52WW)	1.11/1.11 (6QHT30WW / 6SHT30WW)
(Continue reading)

Keng-Yu Lin | 15 Mar 10:25 2011

[PATCH] thinkpad-acpi: disable alsa volume mixer for SL410/SL510

The mute key on SL410/SL510 only works when the alsa volume mixer
is not enabled. This patch makes the alsa volume mixer disabled
on the matched SL410/SL510 EC versions.

Signed-off-by: Keng-Yu Lin <keng-yu.lin <at> canonical.com>
---
 drivers/platform/x86/thinkpad_acpi.c |   12 ++++++++----
 1 files changed, 8 insertions(+), 4 deletions(-)

BugLink: https://launchpad.net/bugs/595896

diff --git a/drivers/platform/x86/thinkpad_acpi.c b/drivers/platform/x86/thinkpad_acpi.c
index eb99223..d4ee8f2 100644
--- a/drivers/platform/x86/thinkpad_acpi.c
+++ b/drivers/platform/x86/thinkpad_acpi.c
 <at>  <at>  -6870,6 +6870,7  <at>  <at>  err_exit:

 #define TPACPI_VOL_Q_MUTEONLY	0x0001	/* Mute-only control available */
 #define TPACPI_VOL_Q_LEVEL	0x0002  /* Volume control available */
+#define TPACPI_VOL_Q_IGNORE	0x0003  /* No Volume control available */

 static const struct tpacpi_quirk volume_quirk_table[] __initconst = {
 	/* Whitelist volume level on all IBM by default */
 <at>  <at>  -6886,6 +6887,8  <at>  <at>  static const struct tpacpi_quirk volume_quirk_table[] __initconst = {
 	TPACPI_QEC_LNV('7', 'J', TPACPI_VOL_Q_LEVEL), /* X60t */
 	TPACPI_QEC_LNV('7', '7', TPACPI_VOL_Q_LEVEL), /* Z60 */
 	TPACPI_QEC_LNV('7', 'F', TPACPI_VOL_Q_LEVEL), /* Z61 */
+	TPACPI_QEC_LNV('6', 'J', TPACPI_VOL_Q_IGNORE), /* SL410/SL510 */
+	TPACPI_QEC_LNV('7', 'X', TPACPI_VOL_Q_IGNORE), /* SL410/SL510 */

(Continue reading)

Jake Drexel | 15 Mar 15:14 2011

x100e brightness level count wrong

Hi,

I'm very happy with my x100e though there is a bug with the number of
brightness levels detected.
8 levels are reported but it should be 16.
I'm able to use either 0-7 or 8-15 depending on the last setting in win 7.

Part of the dmesg output:
thinkpad_acpi: ThinkPad ACPI Extras v0.24
thinkpad_acpi: http://ibm-acpi.sf.net/
thinkpad_acpi: ThinkPad BIOS 6XET47WW (1.30 ), EC 6XHT43WW-1.183000
thinkpad_acpi: Lenovo ThinkPad X100e, model 35085GG
thinkpad_acpi: tpacpi_acpi_handle_locate: Found ACPI handle for video
thinkpad_acpi: detected a 8-level brightness capable ThinkPad

Would someone be so kind and look into this? I'd be happy to provide
more debug output.

Jake

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
Vesa Vilhonen | 15 Mar 08:58 2011

THERMAL ALERT: unknown thermal alarm received

Hi,

I got on of these in my dmesg output. It instructed me to notify you by 
email. Here's some additional information:

[14652.682701] thinkpad_acpi: THERMAL ALERT: unknown thermal alarm received
[14652.684561] thinkpad_acpi: temperatures (Celsius): 44 0 0 0 0 0 0 0
[14652.684573] thinkpad_acpi: unhandled HKEY event 0x6000
[14652.684576] thinkpad_acpi: please report the conditions when this 
event happened to ibm-acpi-devel@...

lshw output is attached.

- Vesa Vilhonen
hiski
    description: Notebook
    product: 25412TG
    vendor: LENOVO
    version: ThinkPad W701
    serial: R98XK23
    width: 64 bits
    capabilities: smbios-2.6 dmi-2.6 vsyscall64 vsyscall32
    configuration: administrator_password=disabled boot=normal chassis=notebook
frontpanel_password=unknown keyboard_password=disabled power-on_password=disabled uuid=0DD0DCE0-EE62-11DF-A589-C8F5098136A4
  *-core
       description: Motherboard
       product: 25412TG
       vendor: LENOVO
(Continue reading)


Gmane