From owner-freebsd-acpi@FreeBSD.ORG Fri Feb 3 16:18:59 2012 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28F36106564A for ; Fri, 3 Feb 2012 16:18:59 +0000 (UTC) (envelope-from jakobp78@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 873388FC0A for ; Fri, 3 Feb 2012 16:18:58 +0000 (UTC) Received: by werm13 with SMTP id m13so4471607wer.13 for ; Fri, 03 Feb 2012 08:18:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:subject:to:reply-to:mime-version:x-priority :content-type:content-transfer-encoding; bh=fWo5vpC08L0Of/q0PLq1keD3dYe/9OxukSJhIIRPKPM=; b=Zqbw0ctJQzA/S/s9oxwxpR+J5eFtk0qcpCeej7qPnWSHBBRAt29P1nmLA0+nt/MlV2 yTxm4Jg5FwpfuKgMgDtcjzoKa+4Hbo1to5Rq/y+RyUy1JJAwBoNO74fcg7NUJXsRyp6k nf5fUelztRRXFRpXVGALAWZU6ge3zQYmaTuPQ= Received: by 10.180.81.66 with SMTP id y2mr12449706wix.20.1328285937472; Fri, 03 Feb 2012 08:18:57 -0800 (PST) Received: from lhrnms-0125-fe.pr.nmsg.s.nokia.com (em1x-90.lhr.messaging.nokia.com. [131.228.18.90]) by mx.google.com with ESMTPS id n5sm18793403wiw.7.2012.02.03.08.18.55 (version=SSLv3 cipher=OTHER); Fri, 03 Feb 2012 08:18:56 -0800 (PST) Message-ID: <4f2c08f0.e54cb40a.5700.ffff860c@mx.google.com> Date: Fri, 03 Feb 2012 16:18:22 +0000 From: "jakobp78@gmail.com" To: "freebsd-acpi@freebsd.org" , "John Baldwin" MIME-Version: 1.0 X-Priority: 3 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Cc: Subject: RE: ACPI error caused by broken asl, how to fix? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jakobp78@gmail.com List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2012 16:18:59 -0000 Hi John, Thank you for your reply. The more I look the less confident I am that = this will in fact fix my wifi, but if it does it is just an added bonus= . I will submit a separate report to mobile@freebsd and focus on suspen= d/resume issues in this thread or at least a cleaner dmesg. The laptop suspends, but screen remains black and I need to hold down t= he power button to cut power. When restarting it just does a normal boo= t, suggesting unclean shutdown.=20 -----Original Message----- From: John Baldwin Sent: 03/02/2012 2:42:58 pm To: freebsd-acpi@freebsd.org Cc: Jakob Pedersen Subject: Re: ACPI error caused by broken asl, how to fix? On Thursday, February 02, 2012 5:23:25 am Jakob Pedersen wrote: > Hello there, >=20 > I am running PCBSD 9.0 on a Packard Bell R1926 and having the followi= ng > problems: >=20 > - Suspend resume does put the machine asleep, but it doesn't resume. > - I am having strange issues with my wifi card, which disconnects if = more > than 2 metres away from the router. Several linux distros seem to sug= gest a > general problem with wifi is caused by acpi problems (under linux eit= her > WiFi works OR USB). My wifi card is RALINK rc61/R2561s using the ral0 > driver. Full specs of the laptop can be found here: > http://dl.dropbox.com/u/7820484/PackardBell-R1926-bios-info.txt >=20 > For trouble shooting I extracted the ASL of the bios and recompiled i= t > using iasl. This gave the following error: >=20 > -------- > Intel ACPI Component Architecture > ASL Optimizing Compiler version 20110527-32 > Copyright (c) 2000 - 2011 Intel Corporation >=20 > packardbell-r1926.asl 3565: Return (0x00) > Error 4080 - Invalid object type for reserved name ^ (foun= d > INTEGER, requires Buffer) >=20 > ASL Input: packardbell-r1936.asl - 3577 lines, 109288 bytes, 1236 ke= ywords > Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 572 Optimizati= ons > -------- > The ASL can be found here: > http://dl.dropbox.com/u/7820484/packardbell-r1926.asl >=20 > I had a look at the ASL code and it appears to cause problems in ALKD= as > mentioned in the dmesg: It's not trivial to fix this warning, but I also strongly doubt it will do anything to help your wifi card. If your wifi card works at all (ge= ts interrupts, etc.), then worrying about ALKD is just a red herring. You might ask on mobile@FreeBSD.org about debugging your wifi issues. As far as suspend and resume, resume is not very easy to debug when it doesn't work. Does your screen come back at all if you resume or does = it just stay black? --=20 John Baldwin