From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 25 19:21:26 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E737E16A41F for ; Sun, 25 Dec 2005 19:21:26 +0000 (GMT) (envelope-from vaida.bogdan@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40AA843D53 for ; Sun, 25 Dec 2005 19:21:26 +0000 (GMT) (envelope-from vaida.bogdan@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1006150nzo for ; Sun, 25 Dec 2005 11:21:25 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VihCt6Tss+zPn7ax0/CC1Y3D6IKc+9DQxbR/poGjF1793xjUgMBsJpug01X2I9n93gQ87Ow6Q0RGWxR564e069cSTxKu86A1aw+G/0y4/y7aope1SW+o+tplPiABND1Y5W4JrMZa9gwBsAlPO0e1ZL4D+GkXrCA3SGOxi7+fai0= Received: by 10.36.9.20 with SMTP id 20mr2470572nzi; Sun, 25 Dec 2005 11:21:25 -0800 (PST) Received: by 10.36.251.28 with HTTP; Sun, 25 Dec 2005 11:21:25 -0800 (PST) Message-ID: <12848a3b0512251121j2b8e87caid3bf74ec8b275da0@mail.gmail.com> Date: Sun, 25 Dec 2005 21:21:25 +0200 From: Vaida Bogdan To: freebsd-acpi@freebsd.org In-Reply-To: <12848a3b0512230717uf7d9513rfcdf8904aab498ba@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <12848a3b0512230717uf7d9513rfcdf8904aab498ba@mail.gmail.com> Subject: Re: fujitsu notebook and acpi resume from sleep X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2005 19:21:27 -0000 I run 6.0-RELEASE It seems the hdd doesn't "wake up" after a resume with apic disabled: fwohci0:fwohci_pci_suspend fwohci0: device physically ejected? fw0hci0: suspend request ignored (not ready yet) fwohci0: Phy 1394a available S400, 2 ports fwohci0: Link S400, max_rec 2048 bytes fwohci0: Initiate bus reset fwohci0: Bus reset fwohci0: node_id=3D0xc800ffc0 gen=3D0 CYCLEMASTER MODE firewire0: 1 nodes maxhop <=3D0, cable IRM=3D0 (me) firewire0: bus manager 0 (me) fwohci0: phy int ad4 detached g_vfs_done() ad4s1a [READ(offset=3D53...,length=3D2048)] error=3D6 g_vfs_done()... vnode_pager_getpages: I/O read error g_vfs_done... [ seems I can run bash builtin commands =3D> memory was restored ok ] [ it also seems ad4 remains detached ] cd /bin ./ls g_vfs_done() ... vnode_pager_getpages: I/O read error ./ls: Input/Output error On 12/23/05, Vaida Bogdan wrote: > I have a Fujitsu Siemens AMILO Pro V2040 notebook and when I try to > resume an acpi sleep command it freezes: > > If I power on after a sleep (acpiconf -s 3): > > ioapic_suspend: not_implemented! > ioapic_suspend: not_implemented! > [...] > fwohci0: Phy 1394a available S400, 2 ports > fwohci0: Link S400, max_rec 2048 bytes > fwohci0: Initiate bus reset > [ Freezes ] > > acpiconf -s 5 - poweroff > acpiconf -s 4 - poweroff > acpiconf -s 2 - sleep state S2 not supported by bios > acpiconf -s 1 - sleep state S1 not supported by bios > > Attached: dmesg_acpi.txt (dmesg|grep acpi) and fujitsu_siemens.asl > (acpidump -t -d) > > Any ideeas on how to solve this? > > > From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 25 21:00:52 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFDBB16A41F for ; Sun, 25 Dec 2005 21:00:51 +0000 (GMT) (envelope-from vaida.bogdan@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A2D343D45 for ; Sun, 25 Dec 2005 21:00:46 +0000 (GMT) (envelope-from vaida.bogdan@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1015963nzo for ; Sun, 25 Dec 2005 13:00:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NosMc7J7DQBDnVXnwr8BPTiF/JvlA49KOPZ6h9Kck+pEJhf5KPVAF9VsrnBrD6VSO0uaWj3z/5kEUx8pOsWRuGkktFv1i2NDGDEd4Lzl65QGnA8tOd/cYkBmu/Ju6rtmN7LPGcYSOzSrXGdGOBugMhaVz8cVNtDs3HWC+RpJiMc= Received: by 10.36.65.10 with SMTP id n10mr2545234nza; Sun, 25 Dec 2005 13:00:45 -0800 (PST) Received: by 10.36.251.28 with HTTP; Sun, 25 Dec 2005 13:00:45 -0800 (PST) Message-ID: <12848a3b0512251300y4e932bafofdcd9896abe73990@mail.gmail.com> Date: Sun, 25 Dec 2005 23:00:45 +0200 From: Vaida Bogdan To: freebsd-acpi@freebsd.org In-Reply-To: <12848a3b0512251121j2b8e87caid3bf74ec8b275da0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <12848a3b0512230717uf7d9513rfcdf8904aab498ba@mail.gmail.com> <12848a3b0512251121j2b8e87caid3bf74ec8b275da0@mail.gmail.com> Subject: Re: fujitsu notebook and acpi resume from sleep X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2005 21:00:52 -0000 Note that I also tried using apm (http://www.freebsdforums.org/forums/showthread.php?s=3D&threadid=3D18153): 1) Kernel config has: "device apm" 2) Load kernel module at boot: apm_load=3D"YES" to /boot/loader.conf 3) Hint.apm.0.disabled=3D"0" in /boot/device.hints 4) Start apm automatically at boot: apm_enable=3D"YES" in /etc/rc.conf 5) Enable APM daemon: apmd_enable=3D"YES" to /etc/rc.conf and I get the followin error when starting apm: apm: can't open /dev/apm: no such file or directory /etc/rc: WARNING: /dev/apmctl not found; kernel is missing apm (4) (kldstat shows no acpi loaded, I also tried using apm and pmtimer in my kernel config file) On 12/25/05, Vaida Bogdan wrote: > I run 6.0-RELEASE > > It seems the hdd doesn't "wake up" after a resume with apic disabled: > > fwohci0:fwohci_pci_suspend > fwohci0: device physically ejected? > fw0hci0: suspend request ignored (not ready yet) > fwohci0: Phy 1394a available S400, 2 ports > fwohci0: Link S400, max_rec 2048 bytes > fwohci0: Initiate bus reset > fwohci0: Bus reset > fwohci0: node_id=3D0xc800ffc0 gen=3D0 CYCLEMASTER MODE > firewire0: 1 nodes maxhop <=3D0, cable IRM=3D0 (me) > firewire0: bus manager 0 (me) > fwohci0: phy int > ad4 detached > g_vfs_done() ad4s1a [READ(offset=3D53...,length=3D2048)] error=3D6 > g_vfs_done()... > vnode_pager_getpages: I/O read error > g_vfs_done... > [ seems I can run bash builtin commands =3D> memory was restored ok ] > [ it also seems ad4 remains detached ] > cd /bin > ./ls > g_vfs_done() ... > vnode_pager_getpages: I/O read error > ./ls: Input/Output error > > On 12/23/05, Vaida Bogdan wrote: > > I have a Fujitsu Siemens AMILO Pro V2040 notebook and when I try to > > resume an acpi sleep command it freezes: > > > > If I power on after a sleep (acpiconf -s 3): > > > > ioapic_suspend: not_implemented! > > ioapic_suspend: not_implemented! > > [...] > > fwohci0: Phy 1394a available S400, 2 ports > > fwohci0: Link S400, max_rec 2048 bytes > > fwohci0: Initiate bus reset > > [ Freezes ] > > > > acpiconf -s 5 - poweroff > > acpiconf -s 4 - poweroff > > acpiconf -s 2 - sleep state S2 not supported by bios > > acpiconf -s 1 - sleep state S1 not supported by bios > > > > Attached: dmesg_acpi.txt (dmesg|grep acpi) and fujitsu_siemens.asl > > (acpidump -t -d) > > > > Any ideeas on how to solve this? > > > > > > > From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 26 01:35:05 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 773B516A420; Mon, 26 Dec 2005 01:35:05 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A715443D5C; Mon, 26 Dec 2005 01:35:04 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.13.5/5.7) with ESMTP id jBQ1Z1Eu016932; Mon, 26 Dec 2005 02:35:01 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Mon, 26 Dec 2005 02:35:01 +0100 User-Agent: KMail/1.9 References: <200512221155.04352.groot@kde.org> <200512232244.37363.groot@kde.org> In-Reply-To: <200512232244.37363.groot@kde.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1903168.3AckSPnWF1"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512260235.01584.groot@kde.org> X-Spam-Score: 1.833 (*) BAYES_50,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Cc: freebsd-acpi@freebsd.org Subject: Re: Bad characters in Asus A8N-VM CSM X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2005 01:35:05 -0000 --nextPart1903168.3AckSPnWF1 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 23 December 2005 22:44, Adriaan de Groot wrote: > On Thursday 22 December 2005 11:55, Adriaan de Groot wrote: > > I just picked up an Asus A8N-VM CSM motherboard. It's a nForce 430 + > > GForge 6150 integrated mini-ATX job, amd64, very 1337 and new. That mea= ns > > trouble > > [Following up on myself, for documentation purposes, and CCing -amd64 to > warn off potential users there as well.] Same warning. Experiments with 6.0-STABLE x86 (so, really, amd64 readers ca= n=20 switch off) show the following: 1) 6.0-R x86 can be installed if ACPI is switched off. 2) With ACPI off, an interrupt storm will use 97% of CPU or so, so the=20 installation takes a long time. It may be worth digging out a 2x CDROM driv= e,=20 since I couldn't get a 52x to stay stable long enough to install from. 3) The DSDT is just so totally fscked on this system you need to hex-edit i= t=20 to fix it. I'll post a partly-fixed DSDT on a website if anyone needs it.=20 This causes checksum errors, but that doesn't seem to bother the system. 4) With the fixed DSDT and TFH "11.16.5.3 Overriding the Default AML" you c= an=20 boot with ACPI enabled and the interrupt storms will be over. 4a) Fixing the rest of the AML is beyond my ken, since it's got methods use= d=20 before definition (can I just move them up in the source file?). 4b) If that's fixed, then there's a bunch of If(SS1) statements outside of= =20 method bodies; SS1 is defined as constant 1 elsewhere, so this looks like=20 it's intended to be conditional compilation, which the current iasl doesn't= =20 support. 4c) If anyone else feels like looking at the ASL, I'll post it somewhere. 5) I just panic'ed the system while downloading portupgrade and accessing t= he=20 CDROM drive concurrently, so stability is an issue. =2D-=20 These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot --nextPart1903168.3AckSPnWF1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDr0jFdqzuAf6io/4RAqsDAJ9YIIJWmC1SGeq40uMF1XLq7IFQmgCdHzaT uwVQFysF2VdZAbMCQiWwILM= =a3D4 -----END PGP SIGNATURE----- --nextPart1903168.3AckSPnWF1-- From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 26 11:02:06 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 305BE16A420 for ; Mon, 26 Dec 2005 11:02:06 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5B7543D49 for ; Mon, 26 Dec 2005 11:02:05 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBQB25ja017971 for ; Mon, 26 Dec 2005 11:02:05 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBQB24p1017965 for freebsd-acpi@freebsd.org; Mon, 26 Dec 2005 11:02:04 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 26 Dec 2005 11:02:04 GMT Message-Id: <200512261102.jBQB24p1017965@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2005 11:02:06 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/22] i386/54756 acpi ACPI suspend/resume problem on CF-W2 lapt o [2003/08/17] i386/55661 acpi ACPI suspend/resume problem on ARMADA M70 o [2003/08/20] kern/55822 acpi No ACPI power off with SMP kernel o [2003/08/27] kern/56024 acpi ACPI suspend drains battery while in S3 o [2003/09/03] i386/56372 acpi acpi don't work on TYAN tiger100 M/B o [2004/03/09] i386/64002 acpi acpi problem o [2004/05/27] i386/67273 acpi [hang] system hangs with acpi and Xfree o [2004/10/12] i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Arma o [2005/03/21] i386/79080 acpi acpi thermal changes freezes HP nx6110 o [2005/03/21] i386/79081 acpi ACPI suspend/resume not working on HP nx6 o [2005/11/11] kern/88859 acpi ACPI broken on Compaq DL360 o [2005/11/25] i386/89545 acpi Compaq DL 360 ACPI will not boot with ACP 12 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/03/17] kern/64365 acpi ACPI problems o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) o [2004/07/29] i386/69750 acpi Boot without ACPI failed on ASUS L5 o [2004/11/11] i386/73822 acpi [request] add thermal support to ACPI o [2004/11/11] kern/73823 acpi [feature request] acpi / power-on by time f [2004/11/17] kern/74030 acpi Unplugging AC causes battery % to stay lo o [2005/05/09] kern/80815 acpi ACPI(pci_link) problem in 5.4-STABLE: TIM o [2005/12/03] kern/89879 acpi [acpi] ACPI-0438: *** Error: Looking up [ o [2005/12/18] kern/90607 acpi [acpi] [patch] Support for ASUS A4D lapto 9 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 26 15:25:55 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E13D16A420; Mon, 26 Dec 2005 15:25:55 +0000 (GMT) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B2FB43D58; Mon, 26 Dec 2005 15:25:55 +0000 (GMT) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBQFPt7v036316; Mon, 26 Dec 2005 15:25:55 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBQFPtvJ036312; Mon, 26 Dec 2005 15:25:55 GMT (envelope-from remko) Date: Mon, 26 Dec 2005 15:25:55 GMT From: Remko Lodder Message-Id: <200512261525.jBQFPtvJ036312@freefall.freebsd.org> To: g_jin@lbl.gov, remko@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: i386/80426: [APIC] [panic] 5.4-RC3 still panic when boot on ASUS P2B-DS M/B X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2005 15:25:55 -0000 Old Synopsis: [panic] 5.4-RC3 still panic when boot on ASUS P2B-DS M/B New Synopsis: [APIC] [panic] 5.4-RC3 still panic when boot on ASUS P2B-DS M/B State-Changed-From-To: feedback->open State-Changed-By: remko State-Changed-When: Mon Dec 26 15:22:49 UTC 2005 State-Changed-Why: The PRoblem is still open on 5.4 and 6.0 Responsible-Changed-From-To: freebsd-i386->freebsd-acpi Responsible-Changed-By: remko Responsible-Changed-When: Mon Dec 26 15:22:49 UTC 2005 Responsible-Changed-Why: Set it to the ACPI team to look into the issue. Along the lines it is mentioned that disabling ACPI made the machine work. So it might be related to something ACPI. http://www.freebsd.org/cgi/query-pr.cgi?pr=80426 From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 26 16:12:05 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 640D616A41F; Mon, 26 Dec 2005 16:12:05 +0000 (GMT) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A12043D49; Mon, 26 Dec 2005 16:12:05 +0000 (GMT) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBQGC4Cj039193; Mon, 26 Dec 2005 16:12:04 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBQGC415039189; Mon, 26 Dec 2005 16:12:04 GMT (envelope-from remko) Date: Mon, 26 Dec 2005 16:12:04 GMT From: Remko Lodder Message-Id: <200512261612.jBQGC415039189@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: i386/87568: [ACPI] [REGRESSION] 6.0-STABLE needs ACPI disabled but 5.4-RELEASE didn't X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2005 16:12:05 -0000 Old Synopsis: [acpi] 6.0-STABLE needs ACPI disabled but 5.4-RELEASE didn't (regression) New Synopsis: [ACPI] [REGRESSION] 6.0-STABLE needs ACPI disabled but 5.4-RELEASE didn't Responsible-Changed-From-To: freebsd-i386->freebsd-acpi Responsible-Changed-By: remko Responsible-Changed-When: Mon Dec 26 16:10:52 UTC 2005 Responsible-Changed-Why: The PR mentions acpi and also a workaround that disables acpi. Set the PR to the acpi guys to they can look into this. I also modified the Synopsis a bit to directly note that is going on. http://www.freebsd.org/cgi/query-pr.cgi?pr=87568 From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 26 16:43:19 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B534716A41F; Mon, 26 Dec 2005 16:43:19 +0000 (GMT) (envelope-from kono@kth.se) Received: from omega.nanophys.kth.se (omega.nanophys.kth.se [130.237.35.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2DAA43D5F; Mon, 26 Dec 2005 16:43:18 +0000 (GMT) (envelope-from kono@kth.se) Received: from omega.nanophys.kth.se (localhost [127.0.0.1]) by omega.nanophys.kth.se (8.13.4/8.13.1) with ESMTP id jBQGiYPL029227; Mon, 26 Dec 2005 17:44:34 +0100 (CET) (envelope-from kono@kth.se) Received: from localhost (kono@localhost) by omega.nanophys.kth.se (8.13.4/8.13.1/Submit) with ESMTP id jBQGiXBA029224; Mon, 26 Dec 2005 17:44:33 +0100 (CET) (envelope-from kono@kth.se) X-Authentication-Warning: omega.nanophys.kth.se: kono owned process doing -bs Date: Mon, 26 Dec 2005 17:44:33 +0100 (CET) From: Alexander Konovalenko X-X-Sender: kono@omega.nanophys.kth.se To: freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org Message-ID: <20051226172520.V29157@omega.nanophys.kth.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: "no carrier" on vr0 caused by suspend (FreeBSD 6.0) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2005 16:43:19 -0000 Hello, recently I have upgraded my AMD Athlono-XP laptop to 6.0 STABLE, everything works fine, even suspending with zzz works except network interface vr0 which is in state "no carrier" right after wake up. The only thing which helps is reboot. Is there any work around? RIGHT AFTER WAKE UP: # ifconfig vr0: flags=8843 mtu 1500 ether 00:40:d0:2d:b2:3f media: Ethernet autoselect status: no carrier lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 # # # sysctl -a | grep vr dev.vr.0.%desc: VIA VT6102 Rhine II 10/100BaseTX dev.vr.0.%driver: vr dev.vr.0.%location: slot=18 function=0 handle=\_SB_.PCI0.LAN0 dev.vr.0.%pnpinfo: vendor=0x1106 device=0x3065 subvendor=0x1631 subdevice=0x7002 class=0x020000 dev.vr.0.%parent: pci0 dev.vr.0.wake: 0 dev.miibus.0.%parent: vr0 NORMAL STATE: # ifconfig vr0: flags=8843 mtu 1500 inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:40:d0:2d:b2:3f media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 # # sysctl -a|grep vr dev.vr.0.%desc: VIA VT6102 Rhine II 10/100BaseTX dev.vr.0.%driver: vr dev.vr.0.%location: slot=18 function=0 handle=\_SB_.PCI0.LAN0 dev.vr.0.%pnpinfo: vendor=0x1106 device=0x3065 subvendor=0x1631 subdevice=0x7002 class=0x020000 dev.vr.0.%parent: pci0 dev.vr.0.wake: 0 dev.miibus.0.%parent: vr0 /Alexander Konovalenko From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 26 16:56:40 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43F0616A41F for ; Mon, 26 Dec 2005 16:56:40 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E38A43D49 for ; Mon, 26 Dec 2005 16:56:39 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id jBQGudZY071839 for ; Mon, 26 Dec 2005 14:56:40 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-acpi@freebsd.org Date: Mon, 26 Dec 2005 14:56:33 -0200 User-Agent: KMail/1.8.3 References: <20051226172520.V29157@omega.nanophys.kth.se> In-Reply-To: <20051226172520.V29157@omega.nanophys.kth.se> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512261456.33158.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: "no carrier" on vr0 caused by suspend (FreeBSD 6.0) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2005 16:56:40 -0000 On Monday 26 December 2005 14:44, Alexander Konovalenko wrote: > recently I have upgraded my AMD Athlono-XP laptop to 6.0 STABLE, > everything works fine, even suspending with zzz works except > network interface vr0 which is in state "no carrier" right after wake up. > The only thing which helps is reboot. > which NB is it? do you use acpi or apm? Do you mind posting the config? > Is there any work around? > perhaps you get it back by "ifconfig vr0 media 100baseTX up" or similar Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 26 18:50:06 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6928216A41F for ; Mon, 26 Dec 2005 18:50:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC9D143D46 for ; Mon, 26 Dec 2005 18:50:05 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBQIo5Bo049809 for ; Mon, 26 Dec 2005 18:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBQIo53j049808; Mon, 26 Dec 2005 18:50:05 GMT (envelope-from gnats) Date: Mon, 26 Dec 2005 18:50:05 GMT Message-Id: <200512261850.jBQIo53j049808@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: ravi pina Cc: Subject: Re: kern/88859: ACPI broken on Compaq DL360 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ravi pina List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2005 18:50:06 -0000 The following reply was made to PR kern/88859; it has been noted by GNATS. From: ravi pina To: bug-followup@FreeBSD.org, tedm@ipinc.net Cc: Subject: Re: kern/88859: ACPI broken on Compaq DL360 Date: Mon, 26 Dec 2005 13:40:30 -0500 are there any logs i can provide to assist in getting a fix? i also have a dl360 (with dual proc, however) and have the same issue. while disabling acpi works it was siggested that smp would not work. it would be a shame to have to downgrade to 5.x. thanks, -r -- +++ATH 7MN; {{{ From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 26 21:37:14 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E99C416A41F; Mon, 26 Dec 2005 21:37:14 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E453F43D80; Mon, 26 Dec 2005 21:37:05 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.13.5/5.7) with ESMTP id jBQLb262012580; Mon, 26 Dec 2005 22:37:02 +0100 (MET) From: Adriaan de Groot To: freebsd-acpi@freebsd.org Date: Mon, 26 Dec 2005 22:36:56 +0100 User-Agent: KMail/1.9 References: <20051226172520.V29157@omega.nanophys.kth.se> In-Reply-To: <20051226172520.V29157@omega.nanophys.kth.se> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1591578.ScZFQImDFy"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512262237.02342.groot@kde.org> X-Spam-Score: -0.01 () BAYES_40,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Cc: Alexander Konovalenko , freebsd-hardware@freebsd.org Subject: Re: "no carrier" on vr0 caused by suspend (FreeBSD 6.0) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2005 21:37:15 -0000 --nextPart1591578.ScZFQImDFy Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 26 December 2005 17:44, Alexander Konovalenko wrote: > recently I have upgraded my AMD Athlono-XP laptop to 6.0 STABLE, > everything works fine, even suspending with zzz works except > network interface vr0 which is in state "no carrier" right after wake up. > The only thing which helps is reboot. I just finished working on a Via C3-mini ITX box, also with a vr0 interface= ;=20 it's not a laptop, but I felt it needed to suspend anyway. Suspend into S3= =20 causes the vr0 to hang on resume, in my case with regular vr0: watchdog=20 timeout messages. Solution: reset the driver. Implementation: build a custom kernel with _no_ vr interface built in. Make= =20 sure vr is built as a module. In the suspend script, unload the module. In= =20 resume, reload it, then run rc.d/netif and rc.d/routing. For simple machine= s=20 with uncomplicated interfaces and routing, that ought to do the trick. =2D-=20 These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot --nextPart1591578.ScZFQImDFy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDsGJ+dqzuAf6io/4RAtjjAJ9kFr2KydYZeb8mF625Zk0Ab9kCjQCfaZOr uhKegr8HdPq/q4UHwQo4aI4= =/ijv -----END PGP SIGNATURE----- --nextPart1591578.ScZFQImDFy-- From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 27 00:17:49 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 242DC16A41F for ; Tue, 27 Dec 2005 00:17:49 +0000 (GMT) (envelope-from j_guojun@lbl.gov) Received: from smtp104.sbc.mail.mud.yahoo.com (smtp104.sbc.mail.mud.yahoo.com [68.142.198.203]) by mx1.FreeBSD.org (Postfix) with SMTP id 3B64843D64 for ; Tue, 27 Dec 2005 00:17:47 +0000 (GMT) (envelope-from j_guojun@lbl.gov) Received: (qmail 83070 invoked from network); 27 Dec 2005 00:17:47 -0000 Received: from unknown (HELO ?192.168.2.8?) (jinmtb@sbcglobal.net@68.127.171.235 with plain) by smtp104.sbc.mail.mud.yahoo.com with SMTP; 27 Dec 2005 00:17:47 -0000 Message-ID: <43B08825.1050906@lbl.gov> Date: Mon, 26 Dec 2005 16:17:41 -0800 From: "Jin Guojun [VFFS]" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051013 X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: Adriaan de Groot References: <20051226172520.V29157@omega.nanophys.kth.se> <200512262237.02342.groot@kde.org> In-Reply-To: <200512262237.02342.groot@kde.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Konovalenko , freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: "no carrier" on vr0 caused by suspend (FreeBSD 6.0) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2005 00:17:49 -0000 Adriaan de Groot wrote: >On Monday 26 December 2005 17:44, Alexander Konovalenko wrote: > > >>recently I have upgraded my AMD Athlono-XP laptop to 6.0 STABLE, >>everything works fine, even suspending with zzz works except >>network interface vr0 which is in state "no carrier" right after wake up. >>The only thing which helps is reboot. >> >> > >I just finished working on a Via C3-mini ITX box, also with a vr0 interface; >it's not a laptop, but I felt it needed to suspend anyway. Suspend into S3 >causes the vr0 to hang on resume, in my case with regular vr0: watchdog >timeout messages. > >Solution: reset the driver. > >Implementation: build a custom kernel with _no_ vr interface built in. Make >sure vr is built as a module. In the suspend script, unload the module. In >resume, reload it, then run rc.d/netif and rc.d/routing. For simple machines >with uncomplicated interfaces and routing, that ought to do the trick. > Just bought a ECS P4M800-M7 (V3.1), and had some problems on vr0 with FreeBSD 6.0. Without carrier, system hangs. With cable plugged in, vr0 doesn't work properly. Dhclient fails. Even manually ifconfig vr0 to a IP, machine cannot ping the gateway. Plugged in a fxp0 NIC and dhclient works on fxp0. So, I wonder if this vr driver issue or is it a bad NIC? (vr0 is on board NIC). -- ------------ Jin Guojun ----------- v --- jin@george.lbl.gov --- Distributed Systems Department http://www.dsd.lbl.gov/~jin Lawrence Berkeley National Laboratory, Berkeley, CA 94720 From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 27 05:21:48 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99F3516A41F for ; Tue, 27 Dec 2005 05:21:48 +0000 (GMT) (envelope-from j_guojun@lbl.gov) Received: from smtp104.sbc.mail.mud.yahoo.com (smtp104.sbc.mail.mud.yahoo.com [68.142.198.203]) by mx1.FreeBSD.org (Postfix) with SMTP id 9EC7A43D6A for ; Tue, 27 Dec 2005 05:21:43 +0000 (GMT) (envelope-from j_guojun@lbl.gov) Received: (qmail 49478 invoked from network); 27 Dec 2005 05:21:39 -0000 Received: from unknown (HELO ?192.168.2.10?) (jinmtb@sbcglobal.net@68.127.171.235 with plain) by smtp104.sbc.mail.mud.yahoo.com with SMTP; 27 Dec 2005 05:21:39 -0000 Message-ID: <43B0CFF6.2050005@lbl.gov> Date: Mon, 26 Dec 2005 21:24:06 -0800 From: "Jin Guojun [VFFS]" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050108 X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <20051226172520.V29157@omega.nanophys.kth.se> <200512262237.02342.groot@kde.org> <43B08825.1050906@lbl.gov> In-Reply-To: <43B08825.1050906@lbl.gov> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: "no carrier" on vr0 caused by suspend (FreeBSD 6.0) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2005 05:21:48 -0000 Jin Guojun [VFFS] wrote: > Just bought a ECS P4M800-M7 (V3.1), and had some problems on vr0 with > FreeBSD 6.0. > Without carrier, system hangs. With cable plugged in, vr0 doesn't work > properly. > Dhclient fails. Even manually ifconfig vr0 to a IP, machine cannot > ping the gateway. > Plugged in a fxp0 NIC and dhclient works on fxp0. > So, I wonder if this vr driver issue or is it a bad NIC? (vr0 is on > board NIC). It seems to be hardware problem because Windows 2000 even will not boot from this motherboard. -Jin From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 27 16:16:59 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32B2016A41F; Tue, 27 Dec 2005 16:16:59 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34C0E43D5F; Tue, 27 Dec 2005 16:16:58 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 4660867 for multiple; Tue, 27 Dec 2005 11:18:47 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id jBRGGthN019190; Tue, 27 Dec 2005 11:16:56 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Tue, 27 Dec 2005 11:17:13 -0500 User-Agent: KMail/1.8.2 References: <20051226172520.V29157@omega.nanophys.kth.se> <200512262237.02342.groot@kde.org> In-Reply-To: <200512262237.02342.groot@kde.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512271117.15361.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1218/Mon Dec 26 08:46:59 2005 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Alexander Konovalenko , freebsd-acpi@freebsd.org Subject: Re: "no carrier" on vr0 caused by suspend (FreeBSD 6.0) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2005 16:16:59 -0000 On Monday 26 December 2005 04:36 pm, Adriaan de Groot wrote: > On Monday 26 December 2005 17:44, Alexander Konovalenko wrote: > > recently I have upgraded my AMD Athlono-XP laptop to 6.0 STABLE, > > everything works fine, even suspending with zzz works except > > network interface vr0 which is in state "no carrier" right after wake up. > > The only thing which helps is reboot. > > I just finished working on a Via C3-mini ITX box, also with a vr0 > interface; it's not a laptop, but I felt it needed to suspend anyway. > Suspend into S3 causes the vr0 to hang on resume, in my case with regular > vr0: watchdog timeout messages. > > Solution: reset the driver. > > Implementation: build a custom kernel with _no_ vr interface built in. Make > sure vr is built as a module. In the suspend script, unload the module. In > resume, reload it, then run rc.d/netif and rc.d/routing. For simple > machines with uncomplicated interfaces and routing, that ought to do the > trick. You can try stopping the chip during suspend and init on resume. Something like this: Index: if_vr.c =================================================================== RCS file: /usr/cvs/src/sys/pci/if_vr.c,v retrieving revision 1.114 diff -u -r1.114 if_vr.c --- if_vr.c 11 Nov 2005 16:04:58 -0000 1.114 +++ if_vr.c 27 Dec 2005 16:16:55 -0000 @@ -132,6 +132,8 @@ static int vr_probe(device_t); static int vr_attach(device_t); static int vr_detach(device_t); +static int vr_suspend(device_t); +static int vr_resume(device_t); static int vr_newbuf(struct vr_softc *, struct vr_chain_onefrag *, struct mbuf *); @@ -182,6 +184,8 @@ DEVMETHOD(device_probe, vr_probe), DEVMETHOD(device_attach, vr_attach), DEVMETHOD(device_detach, vr_detach), + DEVMETHOD(device_suspend, vr_suspend), + DEVMETHOD(device_resume, vr_resume), DEVMETHOD(device_shutdown, vr_shutdown), /* bus interface */ @@ -830,6 +834,30 @@ return (0); } +static int +vr_suspend(device_t dev) +{ + struct vr_softc *sc = device_get_softc(dev); + + VR_LOCK(sc); + sc->suspended = 1; + vr_stop(sc); + VR_UNLOCK(sc); + return (0); +} + +static int +vr_resume(device_t dev) +{ + struct vr_softc *sc = device_get_softc(dev); + + VR_LOCK(sc); + sc->suspended = 0; + vr_init_locked(sc); + VR_UNLOCK(sc); + return (0); +} + /* * Initialize the transmit descriptors. */ -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 27 19:00:40 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C36A16A437 for ; Tue, 27 Dec 2005 19:00:40 +0000 (GMT) (envelope-from takawata@init-main.com) Received: from ns.init-main.com (104.194.138.210.bn.2iij.net [210.138.194.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DE2543D53 for ; Tue, 27 Dec 2005 19:00:39 +0000 (GMT) (envelope-from takawata@init-main.com) Received: from init-main.com (localhost [127.0.0.1]) by ns.init-main.com (8.13.3/8.13.3) with ESMTP id jBRItxAY026715 for ; Wed, 28 Dec 2005 03:55:59 +0900 (JST) (envelope-from takawata@init-main.com) Message-Id: <200512271855.jBRItxAY026715@ns.init-main.com> To: freebsd-acpi@freebsd.org From: takawata@freebsd.org Date: Wed, 28 Dec 2005 03:55:59 +0900 Sender: takawata@init-main.com Subject: AOpen A2000 Bare Born Laptop PC. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2005 19:00:40 -0000 Hi, I bought a new Laptop PC as an Christmas present for me. http://aopen.jp/products/baresystem/2000.html I bought an Turion64 processor and 512MB DDR SDRAM. I put some informations at http://www.init-main.com/a2000/ Main issues I have is as follows. 1. AMD64 S3 support. 2. ACPI Windows Management Instrument driver support. Hot keys are impremented on it in this machine. 3. When it goes C2,C3 idle state, some interrupt response may gets wrong, so it does not work properly. 4. It freqently fails EC transaction. From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 27 23:29:47 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14C9816A41F; Tue, 27 Dec 2005 23:29:47 +0000 (GMT) (envelope-from philip@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BECF243D4C; Tue, 27 Dec 2005 23:29:46 +0000 (GMT) (envelope-from philip@FreeBSD.org) Received: from freefall.freebsd.org (philip@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBRNTkO2068612; Tue, 27 Dec 2005 23:29:46 GMT (envelope-from philip@freefall.freebsd.org) Received: (from philip@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBRNTkxj068608; Tue, 27 Dec 2005 23:29:46 GMT (envelope-from philip) Date: Tue, 27 Dec 2005 23:29:46 GMT From: Philip Paeps Message-Id: <200512272329.jBRNTkxj068608@freefall.freebsd.org> To: philip@FreeBSD.org, freebsd-acpi@FreeBSD.org, philip@FreeBSD.org Cc: Subject: Re: kern/90607: [acpi] [patch] Support for ASUS A4D laptop X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2005 23:29:47 -0000 Synopsis: [acpi] [patch] Support for ASUS A4D laptop Responsible-Changed-From-To: freebsd-acpi->philip Responsible-Changed-By: philip Responsible-Changed-When: Tue Dec 27 23:29:46 UTC 2005 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=90607 From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 28 04:40:24 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AB3F16A41F for ; Wed, 28 Dec 2005 04:40:24 +0000 (GMT) (envelope-from takash-i@sophia.ac.jp) Received: from rockliff.cc.sophia.ac.jp (rockliff.cc.sophia.ac.jp [133.12.140.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81DC743D5E for ; Wed, 28 Dec 2005 04:40:23 +0000 (GMT) (envelope-from takash-i@sophia.ac.jp) Received: from heuvers.cc.sophia.ac.jp (heuvers [133.12.138.37]) by rockliff.cc.sophia.ac.jp (Postfix) with ESMTP id 710F810F02 for ; Wed, 28 Dec 2005 13:40:22 +0900 (JST) Received: from [133.12.65.10] (koetoi [133.12.138.217]) by heuvers.cc.sophia.ac.jp (Postfix) with ESMTP id 60ED518AE6 for ; Wed, 28 Dec 2005 13:40:22 +0900 (JST) Message-ID: <43B21780.8030100@sophia.ac.jp> Date: Wed, 28 Dec 2005 13:41:36 +0900 From: Takashi Inoue User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051013 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: fujitsu notebook and acpi resume from sleep X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2005 04:40:24 -0000 Hi, >I run 6.0-RELEASE > Sounds strange. I had >ioapic_suspend: not_implemented! >ioapic_suspend: not_implemented! > on 5.4R but I do not now on 6.0R. I thought the message is removed on 6.0R. >It seems the hdd doesn't "wake up" after a resume with apic disabled: > That is oppsit to my case on Tp X40. At here , with apic, hdd doesn't wake up. No message. But, without apic, whole pc wake up. I dropped "device apic" from kernel configurateion. So, although it looks similar, it mighth be distinct problem. Cheeres, T.I. Takashi From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 28 04:58:47 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14B8316A41F for ; Wed, 28 Dec 2005 04:58:47 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9934343D49 for ; Wed, 28 Dec 2005 04:58:46 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id jBS4wjiE061809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 27 Dec 2005 20:58:46 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43B21BD2.60406@errno.com> Date: Tue, 27 Dec 2005 21:00:02 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: hp nx6125 again X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2005 04:58:47 -0000 I posted a while back about getting a thermal trip whenever I take the machine off ac. Zone 3 jumps from ~30C to 150C in 5-10 seconds. I received no responses except me-too-style ones. I just started looking again and noticed that this only happens when the machine boots with ac plugged in, _then_ you move to battery. If you boot on battery there is no trip. Also, Linux (Suse 10.0) works fine. No thermal trip. In fact on suse I see other thermal zones with signicantly lower temps (e.g. tz0 is typically <40C while freebsd amd64 current as of today is >50C). And this is with freebsd running on the console (i.e. no X server) while suse is running X. The only significant difference I can think of is that freebsd is running the ndis emulator for the broadcom wireless part which appears to have some overhead--but removing it from the system doesn't seem to change the temp. The last issue is that like some other folks the system will lockup if I let powerd bring the clock down when idle. Lockups are easily reproducable but don't appear to be related to any particular state (e.g. I saw a lockup in the lowest frequency and also at one above lowest--though perhaps it was really switching to the lowest frequency and locked up before the printf made it to the console). Any suggestions on how to diagnose any of these problems would be appreciated. I'm most concerned about running too hot and locking up the system. Without resolving these things it's kinda hard to run freebsd. Sam From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 28 06:08:20 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 265DA16A41F for ; Wed, 28 Dec 2005 06:08:20 +0000 (GMT) (envelope-from unkn@unkn.homeunix.org) Received: from unkn.homeunix.org (Home05228.cluj.astral.ro [82.208.134.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83FA743D46 for ; Wed, 28 Dec 2005 06:08:17 +0000 (GMT) (envelope-from unkn@unkn.homeunix.org) Received: from localhost.unkn.homeunix.org (unknown [192.168.0.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by unkn.homeunix.org (Postfix) with ESMTP id 4E9E219512 for ; Wed, 28 Dec 2005 08:08:35 +0200 (EET) Received: from localhost.unkn.homeunix.org (localhost.unkn.homeunix.org [127.0.0.1]) by localhost.unkn.homeunix.org (8.13.5/8.13.4) with ESMTP id jBS680u5029886 for ; Wed, 28 Dec 2005 08:08:00 +0200 (EET) (envelope-from unkn@unkn.homeunix.org) From: unkn To: freebsd-acpi@freebsd.org Date: Wed, 28 Dec 2005 08:07:59 +0200 User-Agent: KMail/1.8.3 References: <43B21BD2.60406@errno.com> In-Reply-To: <43B21BD2.60406@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512280807.59635.unkn@unkn.homeunix.org> Subject: Re: hp nx6125 again X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2005 06:08:20 -0000 I have the same notebook, I have the same problems,here's what I found, it may help you > I posted a while back about getting a thermal trip whenever I take the > machine off ac. Zone 3 jumps from ~30C to 150C in 5-10 seconds. I > received no responses except me-too-style ones. I just started looking > again and noticed that this only happens when the machine boots with ac > plugged in, _then_ you move to battery. If you boot on battery there is > no trip. Also, Linux (Suse 10.0) works fine. No thermal trip. I do a sysctl hw.acpi.cpu.cx_lowest=C2 before I put the machine off ac, it _seems_ to help > > In fact on suse I see other thermal zones with signicantly lower temps > (e.g. tz0 is typically <40C while freebsd amd64 current as of today is > > >50C). And this is with freebsd running on the console (i.e. no X > > server) while suse is running X. The only significant difference I can > think of is that freebsd is running the ndis emulator for the broadcom > wireless part which appears to have some overhead--but removing it from > the system doesn't seem to change the temp. I don't have ndis loaded, but I have the same temperatures. > > The last issue is that like some other folks the system will lockup if I > let powerd bring the clock down when idle. Lockups are easily > reproducable but don't appear to be related to any particular state > (e.g. I saw a lockup in the lowest frequency and also at one above > lowest--though perhaps it was really switching to the lowest frequency > and locked up before the printf made it to the console). Add hint.acpi_throttle.0.disabled="1" to /boot/loader.conf, it worked for me. On FreeBSD current, there's no need to, as far as I can tell. > > Any suggestions on how to diagnose any of these problems would be > appreciated. I'm most concerned about running too hot and locking up > the system. Without resolving these things it's kinda hard to run freebsd. > > Sam I hope this helps you. From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 28 06:10:54 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3914116A41F for ; Wed, 28 Dec 2005 06:10:54 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD7F543D46 for ; Wed, 28 Dec 2005 06:10:53 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.240] (ppp-71-139-31-194.dsl.snfc21.pacbell.net [71.139.31.194]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jBS6B49e029639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 27 Dec 2005 22:11:05 -0800 Message-ID: <43B22AF0.9000901@root.org> Date: Tue, 27 Dec 2005 22:04:32 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler References: <43B21BD2.60406@errno.com> In-Reply-To: <43B21BD2.60406@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: hp nx6125 again X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2005 06:10:54 -0000 Sam Leffler wrote: > I posted a while back about getting a thermal trip whenever I take the > machine off ac. Zone 3 jumps from ~30C to 150C in 5-10 seconds. I > received no responses except me-too-style ones. I just started looking > again and noticed that this only happens when the machine boots with ac > plugged in, _then_ you move to battery. If you boot on battery there is > no trip. Also, Linux (Suse 10.0) works fine. No thermal trip. Something's not working right with acpi_thermal then. Perhaps it's not re-evaluating zones and disabling one that is now inactive once the machine is unplugged. The number of zones (acX) can change when power state changes. Then it gets an invalid reading and thermal trip occurs. Put debugging prints in the acpi_thermal re-evaluation code. > The last issue is that like some other folks the system will lockup if I > let powerd bring the clock down when idle. Lockups are easily > reproducable but don't appear to be related to any particular state > (e.g. I saw a lockup in the lowest frequency and also at one above > lowest--though perhaps it was really switching to the lowest frequency > and locked up before the printf made it to the console). It depends what drivers your system is using, dmesg | grep cpu. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 28 06:15:40 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0814416A41F for ; Wed, 28 Dec 2005 06:15:40 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1BFB43D5A for ; Wed, 28 Dec 2005 06:15:39 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id jBS6FciE062082 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Dec 2005 22:15:39 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43B22DD8.5030406@errno.com> Date: Tue, 27 Dec 2005 22:16:56 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <43B21BD2.60406@errno.com> <43B22AF0.9000901@root.org> In-Reply-To: <43B22AF0.9000901@root.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: hp nx6125 again X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2005 06:15:40 -0000 Nate Lawson wrote: > Sam Leffler wrote: > >> I posted a while back about getting a thermal trip whenever I take the >> machine off ac. Zone 3 jumps from ~30C to 150C in 5-10 seconds. I >> received no responses except me-too-style ones. I just started >> looking again and noticed that this only happens when the machine >> boots with ac plugged in, _then_ you move to battery. If you boot on >> battery there is no trip. Also, Linux (Suse 10.0) works fine. No >> thermal trip. > > > Something's not working right with acpi_thermal then. Perhaps it's not > re-evaluating zones and disabling one that is now inactive once the > machine is unplugged. The number of zones (acX) can change when power > state changes. Then it gets an invalid reading and thermal trip occurs. > Put debugging prints in the acpi_thermal re-evaluation code. Been there, done that. See my previous posting a month or so back. No invalid readings. No zone changes. The high temps really seem to be read. > >> The last issue is that like some other folks the system will lockup if >> I let powerd bring the clock down when idle. Lockups are easily >> reproducable but don't appear to be related to any particular state >> (e.g. I saw a lockup in the lowest frequency and also at one above >> lowest--though perhaps it was really switching to the lowest frequency >> and locked up before the printf made it to the console). > > > It depends what drivers your system is using, dmesg | grep cpu. > cpu0: on acpi0 acpi_throttle0: on cpu0 powernow0: on cpu0 The processor is a turion64 Mobile M-37. Sam From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 28 09:06:18 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42B7E16A41F for ; Wed, 28 Dec 2005 09:06:18 +0000 (GMT) (envelope-from paketix@bluewin.ch) Received: from mail29.bluewin.ch (mail29.bluewin.ch [195.186.18.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4CE343D53 for ; Wed, 28 Dec 2005 09:06:17 +0000 (GMT) (envelope-from paketix@bluewin.ch) Received: from mssazhb-int.msg.bluewin.ch (172.21.1.181) by mail29.bluewin.ch (Bluewin 7.2.069.1) id 43A928930014C078 for freebsd-acpi@freebsd.org; Wed, 28 Dec 2005 09:06:16 +0000 Received: from [195.186.18.74] by mssazhb-int.msg.bluewin.ch with HTTP; Wed, 28 Dec 2005 09:06:14 +0000 Date: Wed, 28 Dec 2005 10:06:14 +0100 Message-ID: <4392C11D000BE59C@mssazhb-int.msg.bluewin.ch> From: paketix@bluewin.ch To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Mailer: Bluewin WebMail / BlueMail Subject: dl580g3/amd64: [ACPI] 6.0-RELEASE will not boot with ACPI enabled X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2005 09:06:18 -0000 if booted with 6.0-RELEASE (amd64) the system hangs if booted with 5.4-RELEASE (amd64) the system boots just fine disabling acpi on 6.0-RELEASE helps but it seems that using SMP will not be possible after that it seems to be an issue related to the pci cards - if if remove all cards the system boots well using 6.0-RELEASE please find all the logs (boot -v; sysctl; acpidump) at http://mypage.bluewin.ch/poe/ system description: hp dl580g3 dual proc xeon 3ghz 4gb ram smart array 6i 5 fiber optic dual port pci-x cards (intel) 1 rj45 quad port pci-x card (intel) please let me know if further information/patch-testing is needed local access to the machines is possible until mid of january - one machine runs 5.4-RELEASE the other one 6.0-RELEASE hope somebody has the time to have a look at it regards, pat From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 29 16:30:08 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BC5B16A420 for ; Thu, 29 Dec 2005 16:30:08 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1253C43DAC for ; Thu, 29 Dec 2005 16:29:41 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 4808246 for multiple; Thu, 29 Dec 2005 11:27:38 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id jBTGTWok041363; Thu, 29 Dec 2005 11:29:36 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Thu, 29 Dec 2005 11:30:13 -0500 User-Agent: KMail/1.8.2 References: <4392C11D000BE59C@mssazhb-int.msg.bluewin.ch> In-Reply-To: <4392C11D000BE59C@mssazhb-int.msg.bluewin.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512291130.14606.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1219/Wed Dec 28 17:57:59 2005 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: dl580g3/amd64: [ACPI] 6.0-RELEASE will not boot with ACPI enabled X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2005 16:30:08 -0000 On Wednesday 28 December 2005 04:06 am, paketix@bluewin.ch wrote: > if booted with 6.0-RELEASE (amd64) the system hangs > if booted with 5.4-RELEASE (amd64) the system boots just fine > disabling acpi on 6.0-RELEASE helps but it seems that using SMP will not > be possible after that > it seems to be an issue related to the pci cards - if if remove all cards > the system boots well using 6.0-RELEASE > > please find all the logs (boot -v; sysctl; acpidump) at > http://mypage.bluewin.ch/poe/ > > system description: > hp dl580g3 > dual proc xeon 3ghz > 4gb ram > smart array 6i > 5 fiber optic dual port pci-x cards (intel) > 1 rj45 quad port pci-x card (intel) > > please let me know if further information/patch-testing is needed > local access to the machines is possible until mid of january - one machine > runs 5.4-RELEASE the other one 6.0-RELEASE > hope somebody has the time to have a look at it > > regards, pat Try enabling SMP by building an SMP kernel. I think I know what this issue is and might have a possible fix that's not in HEAD yet. On some Intel motherboards, when an OS uses a certain delivery mode for interrupts (LOWPRIO, which FreeBSD currently uses), the chipset sends all interrupts to cpu3 (htt cpu on 2nd processor), but with a UP kernel that CPU isn't started up and listening for interrupts. It seems that when you use LOWPRIO Intel's chipset _ignores_ the programmed destination and sends interrupts to CPU 3. Even if you program the Irq to go to CPU 2, it still sends it to CPU 3. I'm not sure why 5.4 is not seeing the same issue. However, several people have reported that on 6.0 they have to enable SMP if they use the apic to boot. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 29 21:40:09 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25FD116A420 for ; Thu, 29 Dec 2005 21:40:09 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 947FA43D48 for ; Thu, 29 Dec 2005 21:40:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBTLe8Ln033916 for ; Thu, 29 Dec 2005 21:40:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBTLe8EG033915; Thu, 29 Dec 2005 21:40:08 GMT (envelope-from gnats) Date: Thu, 29 Dec 2005 21:40:08 GMT Message-Id: <200512292140.jBTLe8EG033915@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Anders Nordby Cc: Subject: Re: i386/89545: Compaq DL 360 ACPI boot problem X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Anders Nordby List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2005 21:40:09 -0000 The following reply was made to PR i386/89545; it has been noted by GNATS. From: Anders Nordby To: John Baldwin Cc: bug-followup@freebsd.org, uralmetal@gmail.com Subject: Re: i386/89545: Compaq DL 360 ACPI boot problem Date: Thu, 29 Dec 2005 22:34:15 +0100 On Fri, Dec 16, 2005 at 03:34:38PM -0500, John Baldwin wrote: > Actually, what I need is someone to add some printf's to the acpi_pci_link > code and figure out where it is hanging if at all possible. There also > aren't any substantive changes (only a printf tweak) in between the start of > RELENG_6 and 6.0 in the pci_link code. I'm curious if the problem persists > on today's RELENG_6 since I've MFC'd various fixes since the release. Using a slightly modified version of John's pci_link_printf.patch (see http://people.freebsd.org/~anders/patches/pci_link_printf.patch-anders, I had to add dev argument to device_printf and a %d was missing) I get: acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported pci_link0: on acpi0 attach started pci_link0: calling _CRS pci_link0: _CRS returned AE_OK pci_link0: num_links = 0 pci_link1: on acpi0 attach started And there it hangs. I am using 6.0-RELEASE here. Haven't tested RELENG_6 yet. Cheers, -- Anders. From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 30 04:19:44 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9628E16A41F for ; Fri, 30 Dec 2005 04:19:44 +0000 (GMT) (envelope-from mls@quaggaspace.org) Received: from mail2.neureal.com (mail2.neureal.com [66.98.218.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 287D343D4C for ; Fri, 30 Dec 2005 04:19:43 +0000 (GMT) (envelope-from mls@quaggaspace.org) Received: (qmail 1724 invoked by uid 399); 30 Dec 2005 04:19:38 -0000 Received: from unknown (HELO ?192.168.0.2?) (mls@quaggaspace.org@69.143.62.94) by mail2.neureal.com with SMTP; 30 Dec 2005 04:19:38 -0000 Message-ID: <43B4B57C.2050007@quaggaspace.org> Date: Thu, 29 Dec 2005 23:20:12 -0500 From: Justin Settle User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ASUS A8N-VM unbootable (panics) with ACPI in 6.0-RELEASE X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 04:19:44 -0000 Hello, So my nice shiny new ASUS A8N-VM came in the mail today, and well, the system kernel panics if I try to boot it with ACPI. This happens in both the i386 and AMD64 6.0-RELEASE installs. The issue is the same one in this pr: http://www.freebsd.org/cgi/query-pr.cgi?pr=standards/90871 The error message I recieve is exactly identical to the one in that pr. Posted here for convenience: Dec 25 14:09:26 amd-64 kernel: ACPI-0397: *** Error: NsSearchAndEnter: Bad character in ACPI Name: 43005350 Dec 25 14:09:26 amd-64 kernel: ACPI-0381: *** Error: Looking up [0x43005350] (NON-ASCII) Dec 25 14:09:26 amd-64 kernel: in namespace, AE_BAD_CHARACTER Dec 25 14:09:26 amd-64 kernel: ACPI-0204: *** Error: AcpiLoadTables: Could not load namespace: AE_BAD_CHARACTER Dec 25 14:09:26 amd-64 kernel: ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_CHARACTER Dec 25 14:09:26 amd-64 kernel: ACPI: table load failed: AE_BAD_CHARACTER The system then panics, waits 15 seconds and reboots. If I boot the system without ACPI, it boots up, however my ata controller drops to ata-33. My system is near what is listed in that pr, with a slightly different motherboard. MB: ASUS A8N-VM (not the CSM model as in the pr - same bios though) CPU: Athlon64 3000+ 1 gig of RAM. 2 ATA-100 120 Gig Seagate drives. If there is any additional information that might help with this issue please let me know. I'm sure if this is fixable on the driver end or if I need to bug ASUS to fix it in the bios but this seemed like a good place to start. Thank you for your time, -Justin Settle From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 30 07:38:43 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C004716A434; Fri, 30 Dec 2005 07:38:43 +0000 (GMT) (envelope-from paketix@bluewin.ch) Received: from mail29.bluewin.ch (mail29.bluewin.ch [195.186.18.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44FF143D49; Fri, 30 Dec 2005 07:38:43 +0000 (GMT) (envelope-from paketix@bluewin.ch) Received: from mssazhb-int.msg.bluewin.ch (172.21.1.181) by mail29.bluewin.ch (Bluewin 7.2.069.1) id 43A92893001A16CF; Fri, 30 Dec 2005 07:38:42 +0000 Received: from [195.186.18.72] by mssazhb-int.msg.bluewin.ch with HTTP; Fri, 30 Dec 2005 07:38:38 +0000 Date: Fri, 30 Dec 2005 08:38:38 +0100 Message-ID: <4392C11D000CA114@mssazhb-int.msg.bluewin.ch> In-Reply-To: <200512291130.14606.jhb@freebsd.org> From: paketix@bluewin.ch To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Mailer: Bluewin WebMail / BlueMail Cc: Subject: Re: dl580g3/amd64: [ACPI] 6.0-RELEASE will not boot with ACPI enabled X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 07:38:45 -0000 >-- Original-Nachricht -- >From: John Baldwin >To: freebsd-acpi@freebsd.org >Subject: Re: dl580g3/amd64: [ACPI] 6.0-RELEASE will not boot with ACPI enabled >Date: Thu, 29 Dec 2005 11:30:13 -0500 >Cc: paketix@bluewin.ch > > >On Wednesday 28 December 2005 04:06 am, paketix@bluewin.ch wrote: >> if booted with 6.0-RELEASE (amd64) the system hangs >> if booted with 5.4-RELEASE (amd64) the system boots just fine >> disabling acpi on 6.0-RELEASE helps but it seems that using SMP will not >> be possible after that >> it seems to be an issue related to the pci cards - if if remove all cards >> the system boots well using 6.0-RELEASE >> >> please find all the logs (boot -v; sysctl; acpidump) at >> http://mypage.bluewin.ch/poe/ >> >> system description: >> hp dl580g3 >> dual proc xeon 3ghz >> 4gb ram >> smart array 6i >> 5 fiber optic dual port pci-x cards (intel) >> 1 rj45 quad port pci-x card (intel) >> >> please let me know if further information/patch-testing is needed >> local access to the machines is possible until mid of january - one machine >> runs 5.4-RELEASE the other one 6.0-RELEASE >> hope somebody has the time to have a look at it >> >> regards, pat > >Try enabling SMP by building an SMP kernel. I think I know what this issue >is >and might have a possible fix that's not in HEAD yet. On some Intel >motherboards, when an OS uses a certain delivery mode for interrupts >(LOWPRIO, which FreeBSD currently uses), the chipset sends all interrupts >to >cpu3 (htt cpu on 2nd processor), but with a UP kernel that CPU isn't started > >up and listening for interrupts. It seems that when you use LOWPRIO Intel's > >chipset _ignores_ the programmed destination and sends interrupts to CPU >3. >Even if you program the Irq to go to CPU 2, it still sends it to CPU 3. >I'm >not sure why 5.4 is not seeing the same issue. However, several people have > >reported that on 6.0 they have to enable SMP if they use the apic to boot. > >-- >John Baldwin <>< http://www.FreeBSD.org/~jhb/ >"Power Users Use the Power to Serve" = http://www.FreeBSD.org hi john thanks for your feedback! i created a smp kernel from RELENG_6_0 this morning and tested it on the dl580g3 with acpi enabled - but still the same behaviour... ...the system boots and hangs somewhere after initializing the nics please find the new logs (smp kernel config and boot -v) at http://mypage.bluewin.ch/poe/ From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 30 10:53:18 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 083A116A41F for ; Fri, 30 Dec 2005 10:53:18 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 681C743D48 for ; Fri, 30 Dec 2005 10:53:17 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.13.5/5.7) with ESMTP id jBUArDTl026624; Fri, 30 Dec 2005 11:53:13 +0100 (MET) From: Adriaan de Groot To: freebsd-acpi@freebsd.org Date: Fri, 30 Dec 2005 11:53:07 +0100 User-Agent: KMail/1.9.1 References: <43B4B57C.2050007@quaggaspace.org> In-Reply-To: <43B4B57C.2050007@quaggaspace.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1405281.GVCx7sIyGv"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512301153.12653.groot@kde.org> X-Spam-Score: 1.833 (*) BAYES_50,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Cc: Subject: Re: ASUS A8N-VM unbootable (panics) with ACPI in 6.0-RELEASE X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 10:53:18 -0000 --nextPart1405281.GVCx7sIyGv Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 30 December 2005 05:20, Justin Settle wrote: > So my nice shiny new ASUS A8N-VM came in the mail today, and well, the > system kernel panics if I try to boot it with ACPI. This happens in > both the i386 and AMD64 6.0-RELEASE installs. The issue is the same one > in this pr: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dstandards/90871 See my recent posts re: A8N-VM CSM with the same issue. The DSDT table is s= o=20 fundamentally broken (but has a correct checksum, so it's not an issue of o= ne=20 nibble falling over during manufacturing) that you can't use it on anything= =20 except Windows (which ignores the AML spec saying that names consist of=20 characters A-Z and _). In any case, what I did to fix this was: 1) Boot 6.0-R x86 in ACPI disabled mode 2) Use acpidump to get the DSDT 3) Hex edit the DSDT (you can't disassemlble it because it's so broken) 4) Set that modified DSDT for use as per Handbook section 11.rumtiddlypo 5) Reboot into 6.0-R x86 with ACPI 6) Profit! It seems to be a speedy and stable machine from there on in, at least when= =20 doing only one thing (portinstall kde) at a time. If you like, I can post the modified DSDT on a website somewhere. > The system then panics, waits 15 seconds and reboots. If I boot the > system without ACPI, it boots up, however my ata controller drops to > ata-33. Also with the fixed DSDT, ata-33. nForce430 is still too leading-edge. Do y= ou=20 get the nForce430 NIC listed at all? Mine doesn't even show up in pciconf=20 =2Dlv. > please let me know. I'm sure if this is fixable on the driver end or if > I need to bug ASUS to fix it in the bios but this seemed like a good > place to start. I figured that the first BIOS update (to 0506) would fix the problem, but n= o.=20 What's worse, it also made the machine lock up in x86 no-ACPI mode. =2D-=20 These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot --nextPart1405281.GVCx7sIyGv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDtRGYdqzuAf6io/4RAngJAJ9ocRCqKUD00/wR3Fo3sUKU+R4ZXgCggM62 5yWfbJWK/Ln43libx3pbUwM= =HCPX -----END PGP SIGNATURE----- --nextPart1405281.GVCx7sIyGv-- From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 30 12:25:55 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B62216A420; Fri, 30 Dec 2005 12:25:55 +0000 (GMT) (envelope-from bln@deprese.net) Received: from smtp-out3.iol.cz (smtp-out3.iol.cz [194.228.2.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id C916743D4C; Fri, 30 Dec 2005 12:25:52 +0000 (GMT) (envelope-from bln@deprese.net) Received: from antivir3.iol.cz (unknown [192.168.30.206]) by smtp-out3.iol.cz (Internet on Line ESMTP server) with ESMTP id 67B31318152; Fri, 30 Dec 2005 13:25:51 +0100 (CET) Received: from localhost (antivir3.iol.cz [127.0.0.1]) by antivir3.iol.cz (Postfix) with ESMTP id 5AD38420016; Fri, 30 Dec 2005 13:25:51 +0100 (CET) Received: from smtp-out3.iol.cz (unknown [192.168.30.28]) by antivir3.iol.cz (Postfix) with ESMTP id 481EA420015; Fri, 30 Dec 2005 13:25:51 +0100 (CET) Received: from 27.240.broadband2.iol.cz (27.240.broadband2.iol.cz [83.208.240.27]) by smtp-out3.iol.cz (Internet on Line ESMTP server) with ESMTP id 090DA3BE4E; Fri, 30 Dec 2005 13:25:50 +0100 (CET) Received: from [172.16.3.35] (unknown [172.16.3.35]) by 27.240.broadband2.iol.cz (Postfix) with ESMTP id 48A24C454A; Fri, 30 Dec 2005 13:25:50 +0100 (CET) Message-ID: <43B5274C.5010206@deprese.net> Date: Fri, 30 Dec 2005 13:25:48 +0100 From: Ondra Holecek User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051222) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at iol.cz Cc: Subject: problems with wifi X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 12:25:55 -0000 hello, i have bought new notebook - Fujitsu-Siemens Amilo A1650G it has problems with acpi (eg. acpiconf -s3 does not work, etc.), and it has also integrated 802.11b/g card - recognized as ath0. I can set it up, but it has no signal - i gues it is because it should be somehow turned on - there is the button on keyboard for this purpose, but of course it does not work in fbsd. I think, if i solve the problems with acpi, wifi will work. I have dmesg full of this messages: Dec 30 12:41:33 vergilius kernel: ACPI-0501: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE Dec 30 12:41:33 vergilius kernel: ACPI-1304: *** Error: Method execution failed [\_TZ_.TZS0._TMP] (Node 0xc29f9c00), AE_NO_HARDWARE_RESPONSE Of course, i would do any necessary tests if somebody tells me how. RELENG_6 oh From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 30 12:53:19 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA74716A420 for ; Fri, 30 Dec 2005 12:53:19 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8919543D49 for ; Fri, 30 Dec 2005 12:53:18 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: (qmail 5914 invoked by uid 89); 30 Dec 2005 12:53:17 -0000 Received: by simscan 1.1.0 ppid: 5898, pid: 5900, t: 2.4063s scanners: attach: 1.1.0 clamav: 0.86.2/m:33/d:1045 spam: 3.0.4 Received: from unknown (HELO ?192.168.100.179?) (rainer@ultra-secure.de@213.196.191.65) by bsd.ultra-secure.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 30 Dec 2005 12:53:14 -0000 Message-ID: <43B52DBA.9090107@ultra-secure.de> Date: Fri, 30 Dec 2005 13:53:14 +0100 From: Rainer Duffner User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ondra Holecek References: <43B5274C.5010206@deprese.net> In-Reply-To: <43B5274C.5010206@deprese.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bsd.ultra-secure.de X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: problems with wifi X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 12:53:19 -0000 Ondra Holecek wrote: > hello, > > i have bought new notebook - Fujitsu-Siemens Amilo A1650G > > it has problems with acpi (eg. acpiconf -s3 does not work, etc.), and > it has also integrated 802.11b/g card - recognized as ath0. > > I can set it up, but it has no signal - i gues it is because it should > be somehow turned on - there is the button on keyboard for this > purpose, but of course it does not work in fbsd. > You did turn it on in the BIOS, too, didn't you? Also, there's acpi_fujitsu.ko - though I don't know if it actually works on the low-end models. cheers, Rainer From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 30 13:18:24 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E20DE16A41F; Fri, 30 Dec 2005 13:18:24 +0000 (GMT) (envelope-from bln@deprese.net) Received: from smtp-out4.iol.cz (smtp-out4.iol.cz [194.228.2.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CBC643D4C; Fri, 30 Dec 2005 13:18:24 +0000 (GMT) (envelope-from bln@deprese.net) Received: from antivir4.iol.cz (unknown [192.168.30.209]) by smtp-out4.iol.cz (Internet on Line ESMTP server) with ESMTP id 4A5B633C258; Fri, 30 Dec 2005 14:18:18 +0100 (CET) Received: from localhost (antivir4.iol.cz [127.0.0.1]) by antivir4.iol.cz (Postfix) with ESMTP id 3EAFA650004; Fri, 30 Dec 2005 14:18:18 +0100 (CET) Received: from smtp-out4.iol.cz (mta-out4 [192.168.30.31]) by antivir4.iol.cz (Postfix) with ESMTP id 2C69B650002; Fri, 30 Dec 2005 14:18:18 +0100 (CET) Received: from 27.240.broadband2.iol.cz (27.240.broadband2.iol.cz [83.208.240.27]) by smtp-out4.iol.cz (Internet on Line ESMTP server) with ESMTP id 002C722AF76; Fri, 30 Dec 2005 14:18:17 +0100 (CET) Received: from [172.16.3.36] (unknown [172.16.3.36]) by 27.240.broadband2.iol.cz (Postfix) with ESMTP id E2F8DC454A; Fri, 30 Dec 2005 14:18:16 +0100 (CET) Message-ID: <43B53395.1030701@deprese.net> Date: Fri, 30 Dec 2005 14:18:13 +0100 From: Ondra Holecek User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051222) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rainer Duffner References: <43B5274C.5010206@deprese.net> <43B52DBA.9090107@ultra-secure.de> In-Reply-To: <43B52DBA.9090107@ultra-secure.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at iol.cz Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: problems with wifi X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 13:18:25 -0000 in BIOS there is the only option "Wireless default setting" = ENABLED (but the LED showing the state of wifi is still off) if i use acpi_fujitsu, nothing changes. oh > > You did turn it on in the BIOS, too, didn't you? > > > Also, there's acpi_fujitsu.ko - though I don't know if it actually works > on the low-end models. > > > > cheers, > Rainer From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 30 14:25:33 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CED8416A41F for ; Fri, 30 Dec 2005 14:25:33 +0000 (GMT) (envelope-from mls@quaggaspace.org) Received: from mail2.neureal.com (mail2.neureal.com [66.98.218.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 26C8B43D5C for ; Fri, 30 Dec 2005 14:25:30 +0000 (GMT) (envelope-from mls@quaggaspace.org) Received: (qmail 7874 invoked by uid 398); 30 Dec 2005 14:25:23 -0000 Received: from 161.80.245.235 (161.80.245.235 [161.80.245.235]) by 66.98.218.21 (Horde MIME library) with HTTP for ; Fri, 30 Dec 2005 08:25:23 -0600 Message-ID: <20051230082523.ni91bjf6ogwkcs8o@66.98.218.21> Date: Fri, 30 Dec 2005 08:25:23 -0600 From: mls@quaggaspace.org To: Adriaan de Groot References: <43B51B0F.7000804@quaggaspace.org> <3328e1b80512300531k46e77fedld98a4fddbe8ce576@mail.gmail.com> <3328e1b80512300537if3c172p57f504c8c88c63d0@mail.gmail.com> In-Reply-To: <3328e1b80512300537if3c172p57f504c8c88c63d0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) Cc: freebsd-acpi@freebsd.org Subject: Re: ASUS A8N-VM unbootable (panics) with ACPI in 6.0-RELEASE] X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 14:25:34 -0000 > From: Adriaan de Groot > To: freebsd-acpi@freebsd.org > Date: Fri, 30 Dec 2005 11:53:07 +0100 > Subject: Re: ASUS A8N-VM unbootable (panics) with ACPI in 6.0-RELEASE > On Friday 30 December 2005 05:20, Justin Settle wrote: >> So my nice shiny new ASUS A8N-VM came in the mail today, and well, the >> system kernel panics if I try to boot it with ACPI. This happens in >> both the i386 and AMD64 6.0-RELEASE installs. The issue is the same one >> in this pr: http://www.freebsd.org/cgi/query-pr.cgi?pr=standards/90871 > > See my recent posts re: A8N-VM CSM with the same issue. The DSDT table is so > fundamentally broken (but has a correct checksum, so it's not an issue of one > nibble falling over during manufacturing) that you can't use it on anything > except Windows (which ignores the AML spec saying that names consist of > characters A-Z and _). In any case, what I did to fix this was: Actually I had seen some of your posts prior to me buying the board. I didn't see the one that said to stay away from it (doh!). So now I'm at work reading up on the CSM board since more people seem to have that one and the problems are the same. Lovely fun with brand new hardware. Anyway I read in a few places that ASUS has been working off-and-on on a new bios. Thats my hope anyway. > 1) Boot 6.0-R x86 in ACPI disabled mode > 2) Use acpidump to get the DSDT > 3) Hex edit the DSDT (you can't disassemlble it because it's so broken) > 4) Set that modified DSDT for use as per Handbook section 11.rumtiddlypo > 5) Reboot into 6.0-R x86 with ACPI > 6) Profit! > > It seems to be a speedy and stable machine from there on in, at least when > doing only one thing (portinstall kde) at a time. > > If you like, I can post the modified DSDT on a website somewhere. Would it be possible for you to post it somewhere just to see what you did? Hexediting dstl tables would be a new thing for me :). >> The system then panics, waits 15 seconds and reboots. If I boot the >> system without ACPI, it boots up, however my ata controller drops to >> ata-33. > > Also with the fixed DSDT, ata-33. nForce430 is still too leading-edge. Do you > get the nForce430 NIC listed at all? Mine doesn't even show up in pciconf > -lv. I actually didn't try the nve at all. Having read previous messages I knew that would be an uphill battle. The machine is working nicely with an xl plugged into its PCI slot. The ATA is a bummer. I may try and got with a gentoo install and see if it'll work there. My understanding there is that nvidia's nforce drivers will allow the ata to work at full speed. However, the linux folks also have to hack up the kernel to get around the buggy asus acpi character. >> please let me know. I'm sure if this is fixable on the driver end or if >> I need to bug ASUS to fix it in the bios but this seemed like a good >> place to start. > > I figured that the first BIOS update (to 0506) would fix the problem, but no. > What's worse, it also made the machine lock up in x86 no-ACPI mode. Lovely. I think when I get home this evening I'm going to tinker with the machine some more and while I'm at it write an email to asus support. Rumors of a new bios have been around for a bit but I want add my voice to the number of people who have asked to get this resolved. Thanks for your help on this, -Justin From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 30 16:03:40 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DC8F16A41F for ; Fri, 30 Dec 2005 16:03:40 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 671FF43D5A for ; Fri, 30 Dec 2005 16:03:39 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.13.5/5.7) with ESMTP id jBUG3aGE025395; Fri, 30 Dec 2005 17:03:36 +0100 (MET) From: Adriaan de Groot To: mls@quaggaspace.org Date: Fri, 30 Dec 2005 17:03:35 +0100 User-Agent: KMail/1.9.1 References: <43B51B0F.7000804@quaggaspace.org> <3328e1b80512300537if3c172p57f504c8c88c63d0@mail.gmail.com> <20051230082523.ni91bjf6ogwkcs8o@66.98.218.21> In-Reply-To: <20051230082523.ni91bjf6ogwkcs8o@66.98.218.21> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1511736.edG5iXS7eZ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512301703.35991.groot@kde.org> X-Spam-Score: 1.833 (*) BAYES_50,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Cc: freebsd-acpi@freebsd.org Subject: Re: ASUS A8N-VM unbootable (panics) with ACPI in 6.0-RELEASE] X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 16:03:40 -0000 --nextPart1511736.edG5iXS7eZ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 30 December 2005 15:25, mls@quaggaspace.org wrote: > > On Friday 30 December 2005 05:20, Justin Settle wrote: > >> So my nice shiny new ASUS A8N-VM came in the mail today, and well, the > >> system kernel panics if I try to boot it with ACPI. This happens in > > > > See my recent posts re: A8N-VM CSM with the same issue. The DSDT table = is > > so fundamentally broken (but has a correct checksum, so it's not an iss= ue =2E.. > > If you like, I can post the modified DSDT on a website somewhere. > > Would it be possible for you to post it somewhere just to see what you > did? Hexediting dstl tables would be a new thing for me :). http://people.fruitsalad.org/adridg/development.freebsd.html#a8nvm I'm still working on a longer explanation of what goes wrong and what the=20 state of the system is. > > Also with the fixed DSDT, ata-33. nForce430 is still too leading-edge. = Do > > you get the nForce430 NIC listed at all? Mine doesn't even show up in > > pciconf -lv. > > I actually didn't try the nve at all. Having read previous messages I > knew that > would be an uphill battle. The machine is working nicely with an xl > plugged into its PCI slot. =20 Ditto. I found a 3c095 in a shoebox, which does just fine. > The ATA is a bummer. I may try and got with a=20 > gentoo install and see if it'll work there. My understanding there is th= at > nvidia's nforce drivers will allow the ata to work at full speed. Howeve= r, > the linux folks also have to hack up the kernel to get around the buggy > asus acpi character. Yes; note that the nVidia Linux boards are quite useful, and you can get FC= 4,=20 OpenSuse or Gentoo working on these systems. Here's a good start: http://www.nvnews.net/vbulletin/showthread.php?t=3D60596 > > I figured that the first BIOS update (to 0506) would fix the problem, b= ut > > no. What's worse, it also made the machine lock up in x86 no-ACPI mode. YMMV, it might have been arguing with ACPI more and I forget whether I was= =20 booting amd64 or x86 at the time. Perhaps 6-R x86 will work with the newer= =20 BIOS (I don't fancy looking for the floppies right now). In any case, with 6-STABLE x86 X w/ nvidia drivers works and runs KDE 3.5=20 quite nicely. =2D-=20 These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot --nextPart1511736.edG5iXS7eZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDtVpXdqzuAf6io/4RAoNZAJ0WtoP4tf0bjtE1tIpV9NZ+9LZK5wCdHrsK XgLr56PkM0q/5mrlrqjTofA= =se9z -----END PGP SIGNATURE----- --nextPart1511736.edG5iXS7eZ-- From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 30 21:10:26 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 041D616A420; Fri, 30 Dec 2005 21:10:26 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7C7543D45; Fri, 30 Dec 2005 21:10:24 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id jBULAG26022031; Fri, 30 Dec 2005 19:10:16 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-stable@freebsd.org Date: Fri, 30 Dec 2005 19:10:07 -0200 User-Agent: KMail/1.8.3 References: <43B5274C.5010206@deprese.net> <43B52DBA.9090107@ultra-secure.de> <43B53395.1030701@deprese.net> In-Reply-To: <43B53395.1030701@deprese.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512301910.08235.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-acpi@freebsd.org, Rainer Duffner Subject: Re: problems with wifi X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 21:10:26 -0000 On Friday 30 December 2005 11:18, Ondra Holecek wrote: > in BIOS there is the only option "Wireless default setting" =3D ENABLED > (but the LED showing the state of wifi is still off) > Hi in order to get the onboard wireless device to work you need to use the ndi= s=20 driver. Anyway, even so, since 6.0-RC1 if I remember well the LED do not work anymo= re=20 even if the device is working fine. This is unfortunatly not very handy sin= ce=20 you never know the reason of connection problems. Still worse is that when= =20 you switch off with the button pressed "off" the device do stay off on next= =20 boot until you press the button again. You could check with xev the button number and write a small script to catc= h=20 it that you are getting an advice/popup when you accidently press the butto= n. On my NB it is 214 WLbutton off 213 WLbutton on Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-acpi@FreeBSD.ORG Sat Dec 31 00:56:00 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFE8516A41F; Sat, 31 Dec 2005 00:56:00 +0000 (GMT) (envelope-from bln@deprese.net) Received: from smtp-out3.iol.cz (smtp-out3.iol.cz [194.228.2.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC1E943D62; Sat, 31 Dec 2005 00:55:59 +0000 (GMT) (envelope-from bln@deprese.net) Received: from antivir3.iol.cz (unknown [192.168.30.206]) by smtp-out3.iol.cz (Internet on Line ESMTP server) with ESMTP id A1DAD3180D0; Sat, 31 Dec 2005 01:55:56 +0100 (CET) Received: from localhost (antivir3.iol.cz [127.0.0.1]) by antivir3.iol.cz (Postfix) with ESMTP id 93B48420015; Sat, 31 Dec 2005 01:55:56 +0100 (CET) Received: from smtp-out3.iol.cz (unknown [192.168.30.28]) by antivir3.iol.cz (Postfix) with ESMTP id 7FCAB420014; Sat, 31 Dec 2005 01:55:56 +0100 (CET) Received: from 27.240.broadband2.iol.cz (27.240.broadband2.iol.cz [83.208.240.27]) by smtp-out3.iol.cz (Internet on Line ESMTP server) with ESMTP id 32AB13BE2B; Sat, 31 Dec 2005 01:55:53 +0100 (CET) Received: from [172.16.1.2] (pretender [172.16.1.2]) by 27.240.broadband2.iol.cz (Postfix) with ESMTP id 4831AC454A; Sat, 31 Dec 2005 01:55:53 +0100 (CET) Message-ID: <43B5D717.2020200@deprese.net> Date: Sat, 31 Dec 2005 01:55:51 +0100 From: Ondra Holecek User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051222) X-Accept-Language: en-us, en MIME-Version: 1.0 To: JoaoBR References: <43B5274C.5010206@deprese.net> <43B52DBA.9090107@ultra-secure.de> <43B53395.1030701@deprese.net> <200512301910.08235.joao@matik.com.br> In-Reply-To: <200512301910.08235.joao@matik.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at iol.cz Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: problems with wifi X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2005 00:56:01 -0000 hello, if i use ndis (driver for AR 5212), i can't see any ndis0 interface driver is net5211.inf, ar5211.sys => ar5211_sys.ko, which should work with this chipset. i have compiled kernel with options NDISAPI device ndis and with or without device ath but still no success the "wireless key" does not show anything in xev, maybe it is the reason? what to do with it? thank you oh JoaoBR wrote: > On Friday 30 December 2005 11:18, Ondra Holecek wrote: > >>in BIOS there is the only option "Wireless default setting" = ENABLED >>(but the LED showing the state of wifi is still off) >> > > > > Hi > in order to get the onboard wireless device to work you need to use the ndis > driver. > > Anyway, even so, since 6.0-RC1 if I remember well the LED do not work anymore > even if the device is working fine. This is unfortunatly not very handy since > you never know the reason of connection problems. Still worse is that when > you switch off with the button pressed "off" the device do stay off on next > boot until you press the button again. > You could check with xev the button number and write a small script to catch > it that you are getting an advice/popup when you accidently press the button. > On my NB it is > 214 WLbutton off > 213 WLbutton on > > Joćo > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. > Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br > From owner-freebsd-acpi@FreeBSD.ORG Sat Dec 31 03:52:57 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45B1516A41F; Sat, 31 Dec 2005 03:52:57 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C12743D4C; Sat, 31 Dec 2005 03:52:53 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp232-237.lns2.adl4.internode.on.net [203.122.232.237]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id jBV3qTUb019758 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 31 Dec 2005 14:22:34 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Sat, 31 Dec 2005 14:21:16 +1030 User-Agent: KMail/1.8.3 References: <43B5274C.5010206@deprese.net> <200512301910.08235.joao@matik.com.br> <43B5D717.2020200@deprese.net> In-Reply-To: <43B5D717.2020200@deprese.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1382258.mrk5OD77A9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512311422.13184.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: problems with wifi X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2005 03:52:57 -0000 --nextPart1382258.mrk5OD77A9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 31 Dec 2005 11:25, Ondra Holecek wrote: > and with or without device ath > > but still no success > > the "wireless key" does not show anything in xev, maybe it is the reason? > > what to do with it? Why don't you just load if_ath.ko? It should support that chipset. If you really want to use ndis for it you need to run ndisgen to create a=20 module for the driver in question. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1382258.mrk5OD77A9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD4DBQBDtgBs5ZPcIHs/zowRAtBHAJjea/McM0tsgRHl3qF9KZwzkuDqAKCY74gw I+i8i1Y2xHMPRMUMtDrF1g== =O6e0 -----END PGP SIGNATURE----- --nextPart1382258.mrk5OD77A9-- From owner-freebsd-acpi@FreeBSD.ORG Sat Dec 31 09:41:47 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE0A016A41F; Sat, 31 Dec 2005 09:41:47 +0000 (GMT) (envelope-from bln@deprese.net) Received: from smtp-out4.iol.cz (smtp-out4.iol.cz [194.228.2.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA29743D62; Sat, 31 Dec 2005 09:41:37 +0000 (GMT) (envelope-from bln@deprese.net) Received: from antivir4.iol.cz (unknown [192.168.30.209]) by smtp-out4.iol.cz (Internet on Line ESMTP server) with ESMTP id 8611C33C08D; Sat, 31 Dec 2005 10:41:36 +0100 (CET) Received: from localhost (antivir4.iol.cz [127.0.0.1]) by antivir4.iol.cz (Postfix) with ESMTP id 7B57C650003; Sat, 31 Dec 2005 10:41:36 +0100 (CET) Received: from smtp-out4.iol.cz (mta-out4 [192.168.30.31]) by antivir4.iol.cz (Postfix) with ESMTP id 685D2650002; Sat, 31 Dec 2005 10:41:36 +0100 (CET) Received: from 27.240.broadband2.iol.cz (27.240.broadband2.iol.cz [83.208.240.27]) by smtp-out4.iol.cz (Internet on Line ESMTP server) with ESMTP id 30D0222AEDB; Sat, 31 Dec 2005 10:41:31 +0100 (CET) Received: from [172.16.1.2] (pretender [172.16.1.2]) by 27.240.broadband2.iol.cz (Postfix) with ESMTP id 22DBEC454A; Sat, 31 Dec 2005 10:41:31 +0100 (CET) Message-ID: <43B65249.1030104@deprese.net> Date: Sat, 31 Dec 2005 10:41:29 +0100 From: Ondra Holecek User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051222) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel O'Connor References: <43B5274C.5010206@deprese.net> <200512301910.08235.joao@matik.com.br> <43B5D717.2020200@deprese.net> <200512311422.13184.doconnor@gsoft.com.au> In-Reply-To: <200512311422.13184.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at iol.cz Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: problems with wifi X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2005 09:41:48 -0000 yes, i can load if_ath, wireless card is found and i can set it up as ath0, but i still have no signal (and there are many ap's - i can see with different pcmcia card) therefore, i think i have to somehow turn it on (the special "wireless" key on keyboard of course doesn't work) > > Why don't you just load if_ath.ko? It should support that chipset. > i know, i did it. loaded generated kernel module, but no ndis0 > If you really want to use ndis for it you need to run ndisgen to create a > module for the driver in question. > From owner-freebsd-acpi@FreeBSD.ORG Sat Dec 31 12:30:12 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E14B16A41F for ; Sat, 31 Dec 2005 12:30:12 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA2A543D5A for ; Sat, 31 Dec 2005 12:30:11 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBVCUBiF075729 for ; Sat, 31 Dec 2005 12:30:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBVCUBfP075728; Sat, 31 Dec 2005 12:30:11 GMT (envelope-from gnats) Date: Sat, 31 Dec 2005 12:30:11 GMT Message-Id: <200512311230.jBVCUBfP075728@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Anders Nordby Cc: Subject: Re: i386/89545: Compaq DL 360 ACPI boot problem X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Anders Nordby List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2005 12:30:12 -0000 The following reply was made to PR i386/89545; it has been noted by GNATS. From: Anders Nordby To: John Baldwin Cc: bug-followup@freebsd.org, uralmetal@gmail.com Subject: Re: i386/89545: Compaq DL 360 ACPI boot problem Date: Sat, 31 Dec 2005 13:27:28 +0100 Hi, On Thu, Dec 29, 2005 at 10:34:15PM +0100, Anders Nordby wrote: > (..) For the record. I just tried using 6.0-STABLE as of december 30. It still hangs: acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported But now it stops earlier, or at least it doesn't print the pci_link: lines. Applying the printf patch then, I get: acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported attach started pci_link0: calling _CRS pci_link0: _CRS returned AE_OK pci_link0: num_links = 0 attach started Phew, luckily acpi is a module, so I only need to recompile it instead of the whole kernel. I had ACPI problems with FreeBSD 6 on other Compaq servers as well, one DL 580. Once we get this solved for DL 360 I can try with the 580 (it is in production, so I can not easily take it down when I want -- but it would be nice to use both CPUs on it ;-)). Cheers, -- Anders. From owner-freebsd-acpi@FreeBSD.ORG Sat Dec 31 21:28:58 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 9F9D116A420; Sat, 31 Dec 2005 21:28:58 +0000 (GMT) In-Reply-To: <43B65249.1030104@deprese.net> from Ondra Holecek at "Dec 31, 2005 10:41:29 am" To: bln@deprese.net (Ondra Holecek) Date: Sat, 31 Dec 2005 21:28:58 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051231212858.9F9D116A420@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: problems with wifi X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2005 21:28:58 -0000 > yes, i can load if_ath, wireless card is found and i can set it up as > ath0, but i still have no signal (and there are many ap's - i can see > with different pcmcia card) Note that if this in fact a problem with ACPI not supporting the wireless enable switch on your laptop correctly, it won't work with the NDISulator any better than it will with the ath(4) driver. I think the wireless enable switch controls the connection to the antenna(s), and is a separate device from the NIC itself that varies in implementation depending on the laptop. The NDIS driver only knows how to manipulate the NIC hardware: the NIC manufacturer can't really customize the driver for each laptop out there (and the laptop manufacturers usually don't customize the drivers either, beyond sticking their logo on them). > therefore, i think i have to somehow turn it on (the special "wireless" > key on keyboard of course doesn't work) > > > > > Why don't you just load if_ath.ko? It should support that chipset. > > > > i know, i did it. loaded generated kernel module, but no ndis0 > > > If you really want to use ndis for it you need to run ndisgen to create a > > module for the driver in question. > > > Let's look at what you did: > if i use ndis (driver for AR 5212), i can't see any ndis0 interface > driver is net5211.inf, ar5211.sys => ar5211_sys.ko, which should work > with this chipset. > i have compiled kernel with > options NDISAPI > device ndis First of all: GET YOUR FILTHY HANDS OFF THE KERNEL BUILD. I very carefully designed things so you don't have to rebuild the kernel, but everyone just charges ahead and does it anyway. Leave the kernel alone. Just kldload ndis.ko and if_ndis.ko. After that, you can kldload ar5211_sys.ko. Second, you said "driver is net5211.inf, ar5211.sys => ar5211_sys.ko, which should work with this chipset." It "should" work? Where did you get this driver from? Is it the one that actually came with your laptop, or did you go rummaging around until you found one that kinda sorta looked right? If no ndis0 device appears when you kldload ar5211_sys.ko, then the driver you have is _NOT_ the right one for your chipset. Look in the net5211.inf file. (Yes, you can look in it: it's just text.) Check the PCI ID list at the top and see if it has an entry that matches your device (shown with pciconf -lv). Check the vendor ID, device ID, _AND_ subsystem code. There must be an entry where all three match your device, otherwise ndis_probe_pci() won't consider the driver to be a match for your hardware. (You can force a match by carefully deleting the &SUBSYS_XXXXXXXX portion of one of the lines and then using ndisgen(8) to rebuild your driver module; a line with no SUBSYS section matches all devices with the specified vendor and device ID.) I couldn't find the first e-mail in this thread, so I don't know which laptop you have. Check to see if it's one of the ones mentioned here: http://rfswitch.sourceforge.net/?page=laptop_matrix If so, you may need some special software to make the switch work. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose =============================================================================