From owner-freebsd-mobile@FreeBSD.ORG Sun Feb 27 04:31:27 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A6C116A4CF for ; Sun, 27 Feb 2005 04:31:27 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 8CF2243D49 for ; Sun, 27 Feb 2005 04:31:26 +0000 (GMT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Feb 2005 04:31:25 +0000 (GMT) To: freebsd-mobile@freebsd.org Date: Sun, 27 Feb 2005 04:31:25 +0000 From: Ian Dowse Message-ID: <200502270431.aa10917@salmon.maths.tcd.ie> Subject: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 04:31:27 -0000 It's possible that the experimantal patch below may help on some notebooks where the display does not recover from a suspend-resume cycle. It makes use of the VESA BIOS to save the display settings before the system suspends and then restores them on resume. The patch is against -CURRENT, but might apply against RELENG_5 without too much trouble. I have a JVC laptop here where this is the only way I have found so far to bring the LCD back to life after resuming, so maybe it will help on other systems too. To test it, apply the patch and rebuild your kernel + modules. You need to either have 'options VESA' in the kernel config or else load the vesa module. It may also be worth trying with the hw.acpi.reset_video sysctl set to 0, since rerunning the VGA POST should be unnecessary. Ian Patch also at: http://people.freebsd.org/~iedowse/vesa_restore.diff Index: dev/fb/vgareg.h =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/dev/fb/vgareg.h,v retrieving revision 1.7 diff -u -r1.7 vgareg.h --- dev/fb/vgareg.h 16 Jun 2004 09:46:43 -0000 1.7 +++ dev/fb/vgareg.h 27 Feb 2005 02:37:20 -0000 @@ -69,6 +69,7 @@ struct video_adapter; typedef struct vga_softc { struct video_adapter *adp; + void *state_buf; #ifdef FB_INSTALL_CDEV genfb_softc_t gensc; #endif Index: isa/vga_isa.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/isa/vga_isa.c,v retrieving revision 1.31 diff -u -r1.31 vga_isa.c --- isa/vga_isa.c 3 Nov 2004 09:07:44 -0000 1.31 +++ isa/vga_isa.c 27 Feb 2005 03:12:08 -0000 @@ -34,6 +34,7 @@ #include #include #include +#include #include #include #include @@ -160,6 +161,55 @@ return 0; } +static int +isavga_suspend(device_t dev) +{ + vga_softc_t *sc; + int err, nbytes; + + sc = device_get_softc(dev); + err = bus_generic_suspend(dev); + if (err) + return (err); + + /* Save the video state across the suspend. */ + if (sc->state_buf != NULL) { + free(sc->state_buf, M_TEMP); + sc->state_buf = NULL; + } + nbytes = (*vidsw[sc->adp->va_index]->save_state)(sc->adp, NULL, 0); + if (nbytes <= 0) + return (0); + sc->state_buf = malloc(nbytes, M_TEMP, M_NOWAIT | M_ZERO); + if (sc->state_buf == NULL) + return (0); + if ((*vidsw[sc->adp->va_index]->save_state)(sc->adp, sc->state_buf, + nbytes) != 0) { + device_printf(dev, "failed to save state\n"); + free(sc->state_buf, M_TEMP); + sc->state_buf = NULL; + } else + device_printf(dev, "saved %d bytes of state\n", nbytes); + return (0); +} + +static int +isavga_resume(device_t dev) +{ + vga_softc_t *sc; + + sc = device_get_softc(dev); + if (sc->state_buf != NULL) { + device_printf(dev, "restoring state\n"); + (*vidsw[sc->adp->va_index]->load_state)(sc->adp, sc->state_buf); + free(sc->state_buf, M_TEMP); + sc->state_buf = NULL; + } + + bus_generic_resume(dev); + return 0; +} + #ifdef FB_INSTALL_CDEV static int @@ -204,6 +254,8 @@ DEVMETHOD(device_identify, isavga_identify), DEVMETHOD(device_probe, isavga_probe), DEVMETHOD(device_attach, isavga_attach), + DEVMETHOD(device_suspend, isavga_suspend), + DEVMETHOD(device_resume, isavga_resume), DEVMETHOD(bus_print_child, bus_generic_print_child), { 0, 0 } Index: i386/isa/vesa.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/i386/isa/vesa.c,v retrieving revision 1.47 diff -u -r1.47 vesa.c --- i386/isa/vesa.c 15 Jul 2004 08:26:05 -0000 1.47 +++ i386/isa/vesa.c 27 Feb 2005 03:54:02 -0000 @@ -423,7 +423,7 @@ bzero(&vmf, sizeof(vmf)); vmf.vmf_eax = 0x4f04; - vmf.vmf_ecx = STATE_MOST; + vmf.vmf_ecx = STATE_ALL; vmf.vmf_edx = STATE_SIZE; err = vm86_intcall(0x10, &vmf); if ((err != 0) || (vmf.vmf_ax != 0x4f)) @@ -440,13 +440,14 @@ bzero(&vmf, sizeof(vmf)); vmf.vmf_eax = 0x4f04; - vmf.vmf_ecx = STATE_MOST; + vmf.vmf_ecx = STATE_ALL; vmf.vmf_edx = code; /* STATE_SAVE/STATE_LOAD */ buf = (u_char *)vm86_getpage(&vesa_vmcontext, 1); vm86_getptr(&vesa_vmcontext, (vm_offset_t)buf, &vmf.vmf_es, &vmf.vmf_bx); bcopy(p, buf, size); err = vm86_datacall(0x10, &vmf, &vesa_vmcontext); + bcopy(buf, p, size); return ((err != 0) || (vmf.vmf_ax != 0x4f)); } From owner-freebsd-mobile@FreeBSD.ORG Sun Feb 27 20:06:53 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 389A916A4CE for ; Sun, 27 Feb 2005 20:06:53 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id CABB543D60 for ; Sun, 27 Feb 2005 20:06:52 +0000 (GMT) (envelope-from jamesd.earl@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so702856wri for ; Sun, 27 Feb 2005 12:06:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=serxlzS/4nwt/UZN7xaV5h/2xQFH8oGy9DopbmuM3nyzmMztAfS/xbn95AIjzs8p0TOO1Vjx7ABWjGfLkE9tJ1iNKo9LszMELRbmZ3ElQUm+RIfMgJGa16w3syuKZyY0ESa7j1XbXqtuRt8BR1R+/LakWo7uFHepDBcSrP6V+24= Received: by 10.54.49.9 with SMTP id w9mr2549wrw; Sun, 27 Feb 2005 12:06:51 -0800 (PST) Received: by 10.54.54.57 with HTTP; Sun, 27 Feb 2005 12:06:51 -0800 (PST) Message-ID: Date: Sun, 27 Feb 2005 13:06:51 -0700 From: James Earl To: freebsd-mobile@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Adding Sierra AirCard support from OpenBSD X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: James Earl List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 20:06:53 -0000 Hi, I'm trying to port OpenBSD's support for the Sierra AirCard's over to FreeBSD. I don't really know what I'm doing... but I just had to give it a shot. I have three AirCard 555's at the moment. I have confirmed that these cards do work with OpenBSD 3.6. I've basically focused on these files: /sys/dev/pccard/pccard_cis_quirks.c /sys/dev/pccard/pccarddevs /etc/pccard.conf I'm not sure if I'm missing some additional files that have required changes or not. From searching through previous posts on this topic, it sounds as though one subscriber nearly got it working (see Resources below). I imagine if he had his hands on the OpenBSD changes he would have gotten it to work. I'm guessing this is probably amazingly easy for somone who knows what they're doing. My diffs can be found here: http://urbanex.ca/download/pccard_cis_quirks.c.diff http://urbanex.ca/download/pccarddevs.diff I'm not exactly sure what to put in /etc/pccard.conf: card "SIERRA" "A555" config auto "sio" ? Upon booting I get: pccard1: using CIS quirks for Sierra Wireless, AirCard 555, A555, Rev 1 pccard1: CIS version PC Card Standard 7.0 pccard1: CIS info: Sierra Wireless, AirCard 555, A555, Rev 1 pccard1: Manufacturer code 0x192, product 0xa555 pccard1: function 1: serial port, ccr addr 700 mask 73 pccard1: function 1, config table entry 32: I/O Card; irq mask 3fbc; iomask 0, iospace 3f8-3ff; io8 irqlevel pccard1: Allocation failed for cfe 32 pccard1: No config entry could be allocated -- Resources: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pcmcia/ http://lists.freebsd.org/mailman/htdig/freebsd-mobile/2004-August/004657.html http://www.sierrawireless.com/SupportDownload/ac555_Linux.asp From owner-freebsd-mobile@FreeBSD.ORG Sun Feb 27 20:24:25 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0893A16A4CE for ; Sun, 27 Feb 2005 20:24:25 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id D55B843D41 for ; Sun, 27 Feb 2005 20:24:24 +0000 (GMT) (envelope-from vladimir@math.uic.edu) Received: from cat.math.uic.edu (c-24-12-126-199.client.comcast.net[24.12.126.199]) by comcast.net (rwcrmhc13) with SMTP id <2005022720242401500l16eje>; Sun, 27 Feb 2005 20:24:24 +0000 Received: (qmail 52980 invoked by uid 31415); 27 Feb 2005 20:24:23 -0000 Date: Sun, 27 Feb 2005 14:24:23 -0600 From: Vladimir Egorin To: freebsd-mobile@freebsd.org Message-ID: <20050227202423.GA52924@math.uic.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.8i Subject: video conferencing on a laptop X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 20:24:25 -0000 I have a Thinkpad T23 laptop with FreeBSD 5.3 installed, and I am trying to add video conferencing functionality to it. Does anyone have any suggestions on possible hardware configurations (additional cards, USB camera, etc)? This machine has USB1 ports and PCMCIA/Cardbus support. There is also S-video out, but that probably won't help? Thanks, Vladimir From owner-freebsd-mobile@FreeBSD.ORG Sun Feb 27 21:14:45 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5996B16A505 for ; Sun, 27 Feb 2005 21:14:45 +0000 (GMT) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1431743D41 for ; Sun, 27 Feb 2005 21:14:45 +0000 (GMT) (envelope-from joshe@mail.elsasser.org) Received: from mail.elsasser.org ([68.160.4.106])0.04 <0ICL000PJ9OGSL70@vms042.mailsrvcs.net> for freebsd-mobile@freebsd.org; Sun, 27 Feb 2005 15:14:40 -0600 (CST) Received: by mail.elsasser.org (Postfix, from userid 1000) id DDF82A4; Sun, 27 Feb 2005 16:16:30 -0500 (EST) Date: Sun, 27 Feb 2005 16:16:30 -0500 From: Josh Elsasser In-reply-to: <200502270431.aa10917@salmon.maths.tcd.ie> To: Ian Dowse Message-id: <20050227211630.GX2702@jade.elsasser.org> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=1Wg5Vd7si6EhrIHA Content-disposition: inline X-PGP-Key-URL: http://www.elsasser.org/pubkey.asc X-PGP-Key-Fingerprint: 8F39 9F2B 3738 54D9 3E40 4604 CFD5 EA3F B833 FD50 References: <200502270431.aa10917@salmon.maths.tcd.ie> User-Agent: Mutt/1.4.2.1i cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 21:14:45 -0000 --1Wg5Vd7si6EhrIHA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 27, 2005 at 04:31:25AM +0000, Ian Dowse wrote: >=20 > It's possible that the experimantal patch below may help on some > notebooks where the display does not recover from a suspend-resume > cycle. It makes use of the VESA BIOS to save the display settings > before the system suspends and then restores them on resume. The > patch is against -CURRENT, but might apply against RELENG_5 without > too much trouble. >=20 > I have a JVC laptop here where this is the only way I have found > so far to bring the LCD back to life after resuming, so maybe it > will help on other systems too. >=20 > To test it, apply the patch and rebuild your kernel + modules. You > need to either have 'options VESA' in the kernel config or else > load the vesa module. It may also be worth trying with the > hw.acpi.reset_video sysctl set to 0, since rerunning the VGA POST > should be unnecessary. >=20 > Ian >=20 > Patch also at: http://people.freebsd.org/~iedowse/vesa_restore.diff >=20 THANK YOU! I've had my laptop for 3 1/2 years, and I can finally suspend/resume and have a usable display afterwards! Cardbus doesn't appear to work after resume, but that's a whole different can of worms... The system I tested this on was RELENG_5 from yesterday, the patch applied cleanly. I already had the hw.acpi.reset_video set to 0, so I don't know if it would work with it set to 1. I would love to see this committed and MFC'd if it doesn't break things for anyone else. -jre --1Wg5Vd7si6EhrIHA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCIjiuz9XqP7gz/VARAisOAKDRmbF//P1Oifcz4xgSeUnLFBFQvACfRJ3A aQral45eK+bbEp+tUCbseyo= =z3hQ -----END PGP SIGNATURE----- --1Wg5Vd7si6EhrIHA-- From owner-freebsd-mobile@FreeBSD.ORG Sun Feb 27 22:55:05 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9F7D16A4CE for ; Sun, 27 Feb 2005 22:55:05 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D4D843D54 for ; Sun, 27 Feb 2005 22:55:05 +0000 (GMT) (envelope-from jamesd.earl@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so720528wri for ; Sun, 27 Feb 2005 14:55:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=smuE/x2gbBThCa6NZmfiHDmSTfz49saesGWkkEHCBEX78rS1D0tkXqcVp3JE/KL8h+ZccXdZYXnk7I1VBbiJvaLYCcI1rbjvqJkZxkCz1rN+xueNNTuw/fM93viOLx9E1cEGObMeXRaI2s6b/vwQmoBn77tEdbmViB/kzzBNH6k= Received: by 10.54.46.2 with SMTP id t2mr28998wrt; Sun, 27 Feb 2005 14:55:04 -0800 (PST) Received: by 10.54.54.57 with HTTP; Sun, 27 Feb 2005 14:55:04 -0800 (PST) Message-ID: Date: Sun, 27 Feb 2005 15:55:04 -0700 From: James Earl To: freebsd-mobile@freebsd.org In-Reply-To: <42222FB8.30808@nrw.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <42222FB8.30808@nrw.ca> Subject: Re: Adding Sierra AirCard support from OpenBSD X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: James Earl List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 22:55:05 -0000 On Sun, 27 Feb 2005 15:38:16 -0500, Mike Goumans wrote: > James Earl wrote: > > >Hi, > > > >I'm trying to port OpenBSD's support for the Sierra AirCard's over to > >FreeBSD. I don't really know what I'm doing... but I just had to give > >it a shot. I have three AirCard 555's at the moment. > > > > > I fought and fought and fought with this. > > I was about to give up, and suddenly someone suggested something that > worked. > > This are the pccard_cis_quirks entries I used > > static struct pccard_function pccard_a555_func0 = { > 0, /* function number */ > PCCARD_FUNCTION_SERIAL, > 0x23, /* last cfe number */ > 0x00, /* ccr_base */ > 0x73, /* ccr_mask */ > }; > > struct pccard_config_entry pccard_a555_func0_cfe0 = { > 0x20, > PCCARD_CFE_IO8 | PCCARD_CFE_IRQLEVEL, > PCCARD_IFTYPE_IO, > 1, /* num_iospace */ > 3, /* iomask */ > { { 0x07, 0x3e8 } }, /* iospace */ > 0x3fbc, /* irqmask */ > 0, /* num_memspace */ > { }, /* memspace */ > 0, /* maxtwins */ > }; > > and pccarddevs > > vendor SIERRAWIRELESS 0x0192 Sierra Wireless > > /* Sierra Wireless */ > product SIERRAWIRELESS A555 0xa555 Sierra Wireless AirCard 555 > > It gets detected as an 8250, but it works ok, I think it just that it > cant find the proper uart. > > It is SLOOOOOOW I get 3k/sec on a good day. Alot less on a bad day. > > I ended up junking it and replacing it with an external multi-tech > modem. Its much faster, its sturdier and it works with incoming as well > as outgoing calls. > > And it was cheaper than replacing the A555. > > Sierra wireless has no way of registering an incoming call via the > serial interface, only the network interface with cns. > The antenna and its jack also came off the card after spending a few > hours in my trunk. > > Sorry for the messy way the information is , I dont have that card > anymore so Im just going over it from the notes I had made. Hi Mike, Thank you! Changing the iomask and iospace did the trick. From owner-freebsd-mobile@FreeBSD.ORG Sun Feb 27 23:11:06 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4AED16A4CE for ; Sun, 27 Feb 2005 23:11:06 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76AE843D2F for ; Sun, 27 Feb 2005 23:11:06 +0000 (GMT) (envelope-from jamesd.earl@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so722115wri for ; Sun, 27 Feb 2005 15:11:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=PFNX7nhRefygXWOI9CXgx1y9qmKo9uza8XShjSzRtPsk05VJpl8/wYARHqG4q3YbjqKjy6evtyAml7X7BEy4fmZntyD62PEdPJFgkCChNWvfhcSfGuJstmq+wqdDmARp90abnOfXbA3YWVizzdKHt3dFC3F+Yq8XR50khpzxT0Q= Received: by 10.54.57.28 with SMTP id f28mr22650wra; Sun, 27 Feb 2005 15:11:05 -0800 (PST) Received: by 10.54.54.57 with HTTP; Sun, 27 Feb 2005 15:11:05 -0800 (PST) Message-ID: Date: Sun, 27 Feb 2005 16:11:05 -0700 From: James Earl To: freebsd-mobile@freebsd.org In-Reply-To: <20050227210541.GC36316@empiric.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050227210541.GC36316@empiric.icir.org> Subject: Re: Adding Sierra AirCard support from OpenBSD X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: James Earl List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 23:11:07 -0000 On Sun, 27 Feb 2005 21:05:42 +0000, Bruce M Simpson wrote: > On Sun, Feb 27, 2005 at 01:06:51PM -0700, James Earl wrote: > > I've basically focused on these files: > > > > /sys/dev/pccard/pccard_cis_quirks.c > > /sys/dev/pccard/pccarddevs > > /etc/pccard.conf > > ...they're all obsolete, as OLDCARD has now been removed. > > I'd suggest looking at the current wi(4) driver to see how to proceed > in the NEWCARD era. No idea what chipset these cards use, so you may > have to write a new driver. Thanks, I'll look into this. So what I've done will no longer work as of 5.4-RELEASE? From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 03:09:04 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 137D916A55E for ; Mon, 28 Feb 2005 03:09:04 +0000 (GMT) Received: from diamond.34sp.com (diamond.34sp.com [195.50.105.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22F8E43D2F for ; Mon, 28 Feb 2005 03:09:03 +0000 (GMT) (envelope-from list@understudy.net) Received: (qmail 4382 invoked from network); 28 Feb 2005 03:09:01 -0000 Received: from adsl-11-166-118.mia.bellsouth.net (HELO ?10.0.0.124?) (65.11.166.118) by mcp.34sp.com with SMTP; 28 Feb 2005 03:09:00 -0000 Message-ID: <42228B46.9050900@understudy.net> Date: Sun, 27 Feb 2005 22:08:54 -0500 From: Understudy User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-mobile@FreeBSD.ORG References: <20050219040357.47106754@spadger.best.vwh.net> <42197CA3.7050709@understudy.net> <421E331C.10804@siol.net> <20050224181142.B60128@sasami.jurai.net> <421E7780.6050800@understudy.net> <20050224202147.A60128@sasami.jurai.net> <421EAAA5.3090304@understudy.net> <20050225095658.D60128@sasami.jurai.net> In-Reply-To: <20050225095658.D60128@sasami.jurai.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Thinkpad 600e interrupt storm X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 03:09:04 -0000 Matthew N. Dodd wrote: > On Thu, 24 Feb 2005, Understudy wrote: > [how do I build a kernel module?] > > cd /sys/modules/bios/smapi > make all > make load > > Also, this will only work on 5.x or -CURRENT. > Slacker# cd /sys/module/bios/smapi /sys/module/bios/smapi: No such file or directory. Slacker# Hmmm, maybe not. Sincerely, Brendhan From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 04:07:31 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C88216A4CE for ; Mon, 28 Feb 2005 04:07:31 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7261243D55 for ; Mon, 28 Feb 2005 04:07:29 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j1S45uNu006389; Sun, 27 Feb 2005 21:05:56 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 27 Feb 2005 21:06:09 -0700 (MST) Message-Id: <20050227.210609.37239597.imp@bsdimp.com> To: jamesd.earl@gmail.com From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: Adding Sierra AirCard support from OpenBSD X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 04:07:31 -0000 In message: James Earl writes: : Hi, : : I'm trying to port OpenBSD's support for the Sierra AirCard's over to : FreeBSD. I don't really know what I'm doing... but I just had to give : it a shot. I have three AirCard 555's at the moment. : : I have confirmed that these cards do work with OpenBSD 3.6. : : I've basically focused on these files: : : /sys/dev/pccard/pccard_cis_quirks.c : /sys/dev/pccard/pccarddevs : /etc/pccard.conf : : I'm not sure if I'm missing some additional files that have required : changes or not. From searching through previous posts on this topic, : it sounds as though one subscriber nearly got it working (see : Resources below). I imagine if he had his hands on the OpenBSD : changes he would have gotten it to work. I'm guessing this is : probably amazingly easy for somone who knows what they're doing. : : My diffs can be found here: : : http://urbanex.ca/download/pccard_cis_quirks.c.diff : http://urbanex.ca/download/pccarddevs.diff : : I'm not exactly sure what to put in /etc/pccard.conf: : card "SIERRA" "A555" : config auto "sio" ? : : Upon booting I get: : : pccard1: using CIS quirks for Sierra Wireless, AirCard 555, A555, Rev 1 : pccard1: CIS version PC Card Standard 7.0 : pccard1: CIS info: Sierra Wireless, AirCard 555, A555, Rev 1 : pccard1: Manufacturer code 0x192, product 0xa555 : pccard1: function 1: serial port, ccr addr 700 mask 73 : pccard1: function 1, config table entry 32: I/O Card; irq mask 3fbc; : iomask 0, iospace 3f8-3ff; io8 irqlevel : pccard1: Allocation failed for cfe 32 : pccard1: No config entry could be allocated Looks like you have another serial port using 3f8-3ff (which is generally COM1). I've had communications with insiders that say other serial ports would also work... I've have no time to integrate things, however. Warner From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 04:13:42 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8405716A4CE for ; Mon, 28 Feb 2005 04:13:42 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CF5043D1F for ; Mon, 28 Feb 2005 04:13:42 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j1S4Arpr006502; Sun, 27 Feb 2005 21:10:54 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 27 Feb 2005 21:11:06 -0700 (MST) Message-Id: <20050227.211106.33317022.imp@bsdimp.com> To: jamesd.earl@gmail.com From: "M. Warner Losh" In-Reply-To: <20050227.210609.37239597.imp@bsdimp.com> References: <20050227.210609.37239597.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: Adding Sierra AirCard support from OpenBSD X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 04:13:42 -0000 In message: <20050227.210609.37239597.imp@bsdimp.com> "M. Warner Losh" writes: : Looks like you have another serial port using 3f8-3ff (which is : generally COM1). I've had communications with insiders that say other : serial ports would also work... I've have no time to integrate : things, however. Also looks like all 4 traditional COM ports are supported, given the highest config #.... Warner From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 04:23:54 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C921916A4CF for ; Mon, 28 Feb 2005 04:23:54 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57CF543D54 for ; Mon, 28 Feb 2005 04:23:54 +0000 (GMT) (envelope-from jamesd.earl@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so755044wri for ; Sun, 27 Feb 2005 20:23:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=iyAYMmSCwskKlG7louSWYOQxTgfL4VcEgCoS+CI91P+KvxVkknxpuG/8Dg0Tfrx/EK5Ywet4bVDX4YqNIt7QBfnX//BPlMfO/YUtyQGVTuiyfX37Srew1dkYCf/y0EVPR0fNmxLnAAB5rsNwI3JqkkhJxMVkvZZx2u4BLozgkMg= Received: by 10.54.14.31 with SMTP id 31mr3530wrn; Sun, 27 Feb 2005 20:23:53 -0800 (PST) Received: by 10.54.54.57 with HTTP; Sun, 27 Feb 2005 20:23:53 -0800 (PST) Message-ID: Date: Sun, 27 Feb 2005 21:23:53 -0700 From: James Earl To: freebsd-mobile@freebsd.org In-Reply-To: <20050227.211106.33317022.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050227.210609.37239597.imp@bsdimp.com> <20050227.211106.33317022.imp@bsdimp.com> Subject: Re: Adding Sierra AirCard support from OpenBSD X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: James Earl List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 04:23:54 -0000 On Sun, 27 Feb 2005 21:11:06 -0700 (MST), M. Warner Losh wrote: > In message: <20050227.210609.37239597.imp@bsdimp.com> > "M. Warner Losh" writes: > : Looks like you have another serial port using 3f8-3ff (which is > : generally COM1). I've had communications with insiders that say other > : serial ports would also work... I've have no time to integrate > : things, however. > > Also looks like all 4 traditional COM ports are supported, given the > highest config #.... Changing to a different COM port did allow the device to work. There must be something else wrong with my setup because I was getting really slow performance, and sio overflows... sio was also reporting something (upon bootup) about not being 8250 or something... sorry I don't have access to the machine right now. James From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 04:24:34 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23F7916A4CE for ; Mon, 28 Feb 2005 04:24:34 +0000 (GMT) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C677C43D53 for ; Mon, 28 Feb 2005 04:24:33 +0000 (GMT) (envelope-from joshe@mail.elsasser.org) Received: from mail.elsasser.org ([68.160.4.106])0.04 <0ICL005W9TKV9AD0@vms042.mailsrvcs.net> for freebsd-mobile@freebsd.org; Sun, 27 Feb 2005 22:24:32 -0600 (CST) Received: by mail.elsasser.org (Postfix, from userid 1000) id CC33F17E; Sun, 27 Feb 2005 23:26:23 -0500 (EST) Date: Sun, 27 Feb 2005 23:26:23 -0500 From: Josh Elsasser In-reply-to: <1109545918.1537.8.camel@localhost> To: Vladimir Grebenschikov Message-id: <20050228042623.GY2702@jade.elsasser.org> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=QQ0dNM4HnH4+xgqD Content-disposition: inline X-PGP-Key-URL: http://www.elsasser.org/pubkey.asc X-PGP-Key-Fingerprint: 8F39 9F2B 3738 54D9 3E40 4604 CFD5 EA3F B833 FD50 References: <200502270431.aa10917@salmon.maths.tcd.ie> <20050227211630.GX2702@jade.elsasser.org> <1109545918.1537.8.camel@localhost> User-Agent: Mutt/1.4.2.1i cc: Ian Dowse cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 04:24:34 -0000 --QQ0dNM4HnH4+xgqD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 28, 2005 at 02:11:58AM +0300, Vladimir Grebenschikov wrote: > ? ??, 27/02/2005 ? 16:16 -0500, Josh Elsasser ?????: > >On Sun, Feb 27, 2005 at 04:31:25AM +0000, Ian Dowse wrote: > >>=20 > >> It's possible that the experimantal patch below may help on some > >> notebooks where the display does not recover from a suspend-resume > >> cycle. It makes use of the VESA BIOS to save the display settings > >> before the system suspends and then restores them on resume. The > >> patch is against -CURRENT, but might apply against RELENG_5 without > >> too much trouble. > >>=20 > >> I have a JVC laptop here where this is the only way I have found > >> so far to bring the LCD back to life after resuming, so maybe it > >> will help on other systems too. > >>=20 > >> To test it, apply the patch and rebuild your kernel + modules. You > >> need to either have 'options VESA' in the kernel config or else > >> load the vesa module. It may also be worth trying with the > >> hw.acpi.reset_video sysctl set to 0, since rerunning the VGA POST > >> should be unnecessary. > >>=20 > >> Ian > >>=20 > >> Patch also at: http://people.freebsd.org/~iedowse/vesa_restore.diff > >>=20 > > > >THANK YOU! I've had my laptop for 3 1/2 years, and I can finally > >suspend/resume and have a usable display afterwards! Cardbus doesn't > >appear to work after resume, but that's a whole different can of > >worms... > > > >The system I tested this on was RELENG_5 from yesterday, the patch > >applied cleanly. I already had the hw.acpi.reset_video set to 0, so I > >don't know if it would work with it set to 1. >=20 > What notebook you have ? I was not such lucky. >=20 > I Has SONY VAIO PCG-Z1WA, by zzz it sleeps ok,=20 > With patch it even said about saving VESA data. > On any key after it is awakes, spin up drive and fan, but screen still > black (even no backlight), and it is very unlike that I get console back > (typing has no effect, even when I try to call kdb). >=20 > Also if I try this patch with vesa module loaded it just carsh in vm86 > mode on zzz (curproc acpiconf). >=20 > Any suggestions are very welcome. What is hw.acpi.reset_video set to on your system? At some point between 5.2 and 5.3, my machine would hang on resume instead of just resuming with no display. Setting hw.acpi.reset_video=3D0 in loader.conf fixed that. I have a Sony Vaio FX220, which has an i815 graphics chip. -jre --QQ0dNM4HnH4+xgqD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCIp1vz9XqP7gz/VARAks2AJ41fd++YdvNoEzJlXNhW7ITXQ1jkQCeK0SJ bmoRcTy204/1UoGbvVuA1Aw= =kbGz -----END PGP SIGNATURE----- --QQ0dNM4HnH4+xgqD-- From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 04:26:44 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F9D016A4CE for ; Mon, 28 Feb 2005 04:26:44 +0000 (GMT) Received: from sasami.jurai.net (sasami.jurai.net [69.17.104.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE23743D1D for ; Mon, 28 Feb 2005 04:26:42 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [69.17.104.113]) by sasami.jurai.net (8.13.1/8.13.1) with ESMTP id j1S4Qdjf004870; Sun, 27 Feb 2005 23:26:41 -0500 (EST) (envelope-from mdodd@FreeBSD.ORG) Date: Sun, 27 Feb 2005 23:26:39 -0500 (EST) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: Understudy In-Reply-To: <42228B46.9050900@understudy.net> Message-ID: <20050227232531.U60128@sasami.jurai.net> References: <20050219040357.47106754@spadger.best.vwh.net> <42197CA3.7050709@understudy.net> <421E331C.10804@siol.net> <20050224181142.B60128@sasami.jurai.net> <421E7780.6050800@understudy.net> <20050224202147.A60128@sasami.jurai.net> <421EAAA5.3090304@understudy.net> <20050225095658.D60128@sasami.jurai.net> <42228B46.9050900@understudy.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (sasami.jurai.net [69.17.104.113]); Sun, 27 Feb 2005 23:26:42 -0500 (EST) cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Thinkpad 600e interrupt storm X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 04:26:44 -0000 On Sun, 27 Feb 2005, Understudy wrote: > Matthew N. Dodd wrote: >> cd /sys/modules/bios/smapi > Slacker# cd /sys/module/bios/smapi > /sys/module/bios/smapi: No such file or directory. > Slacker# > Hmmm, maybe not. Try again. -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00 From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 07:38:36 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB10316A4CE for ; Mon, 28 Feb 2005 07:38:36 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id B652A43D53 for ; Mon, 28 Feb 2005 07:38:35 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.44 (FreeBSD)) id 1D5XZu-0001E0-Rt; Mon, 28 Feb 2005 02:11:58 +0300 From: Vladimir Grebenschikov To: Josh Elsasser In-Reply-To: <20050227211630.GX2702@jade.elsasser.org> References: <200502270431.aa10917@salmon.maths.tcd.ie> <20050227211630.GX2702@jade.elsasser.org> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Mon, 28 Feb 2005 02:11:58 +0300 Message-Id: <1109545918.1537.8.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.1.5 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: Ian Dowse cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 07:38:36 -0000 =F7 =D7=D3, 27/02/2005 =D7 16:16 -0500, Josh Elsasser =D0=C9=DB=C5=D4: >On Sun, Feb 27, 2005 at 04:31:25AM +0000, Ian Dowse wrote: >>=20 >> It's possible that the experimantal patch below may help on some >> notebooks where the display does not recover from a suspend-resume >> cycle. It makes use of the VESA BIOS to save the display settings >> before the system suspends and then restores them on resume. The >> patch is against -CURRENT, but might apply against RELENG_5 without >> too much trouble. >>=20 >> I have a JVC laptop here where this is the only way I have found >> so far to bring the LCD back to life after resuming, so maybe it >> will help on other systems too. >>=20 >> To test it, apply the patch and rebuild your kernel + modules. You >> need to either have 'options VESA' in the kernel config or else >> load the vesa module. It may also be worth trying with the >> hw.acpi.reset_video sysctl set to 0, since rerunning the VGA POST >> should be unnecessary. >>=20 >> Ian >>=20 >> Patch also at: http://people.freebsd.org/~iedowse/vesa_restore.diff >>=20 > >THANK YOU! I've had my laptop for 3 1/2 years, and I can finally >suspend/resume and have a usable display afterwards! Cardbus doesn't >appear to work after resume, but that's a whole different can of >worms... > >The system I tested this on was RELENG_5 from yesterday, the patch >applied cleanly. I already had the hw.acpi.reset_video set to 0, so I >don't know if it would work with it set to 1. What notebook you have ? I was not such lucky. I Has SONY VAIO PCG-Z1WA, by zzz it sleeps ok,=20 With patch it even said about saving VESA data. On any key after it is awakes, spin up drive and fan, but screen still black (even no backlight), and it is very unlike that I get console back (typing has no effect, even when I try to call kdb). Also if I try this patch with vesa module loaded it just carsh in vm86 mode on zzz (curproc acpiconf). Any suggestions are very welcome. >I would love to see this committed and MFC'd if it doesn't break >things for anyone else. > > -jre --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 07:48:40 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D438516A4CE for ; Mon, 28 Feb 2005 07:48:40 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55DE043D1F for ; Mon, 28 Feb 2005 07:48:40 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.44 (FreeBSD)) id 1D5fds-000B5M-LO; Mon, 28 Feb 2005 10:48:36 +0300 From: Vladimir Grebenschikov To: Josh Elsasser In-Reply-To: <20050228042623.GY2702@jade.elsasser.org> References: <200502270431.aa10917@salmon.maths.tcd.ie> <20050227211630.GX2702@jade.elsasser.org> <1109545918.1537.8.camel@localhost> <20050228042623.GY2702@jade.elsasser.org> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Mon, 28 Feb 2005 10:48:35 +0300 Message-Id: <1109576915.7823.7.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.1.5 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 07:48:41 -0000 =F7 =D7=D3, 27/02/2005 =D7 23:26 -0500, Josh Elsasser =D0=C9=DB=C5=D4: ...cut... >> >> Patch also at: http://people.freebsd.org/~iedowse/vesa_restore.diff >> >>=20 >> > >> >THANK YOU! I've had my laptop for 3 1/2 years, and I can finally >> >suspend/resume and have a usable display afterwards! Cardbus doesn't >> >appear to work after resume, but that's a whole different can of >> >worms... >> > >> >The system I tested this on was RELENG_5 from yesterday, the patch >> >applied cleanly. I already had the hw.acpi.reset_video set to 0, so I >> >don't know if it would work with it set to 1. >>=20 >> What notebook you have ? I was not such lucky. >>=20 >> I Has SONY VAIO PCG-Z1WA, by zzz it sleeps ok,=20 >> With patch it even said about saving VESA data. >> On any key after it is awakes, spin up drive and fan, but screen still >> black (even no backlight), and it is very unlike that I get console back >> (typing has no effect, even when I try to call kdb). >>=20 >> Also if I try this patch with vesa module loaded it just carsh in vm86 >> mode on zzz (curproc acpiconf). >>=20 >> Any suggestions are very welcome. > >What is hw.acpi.reset_video set to on your system? At some point >between 5.2 and 5.3, my machine would hang on resume instead of just >resuming with no display. Setting hw.acpi.reset_video=3D0 in >loader.conf fixed that. I have a Sony Vaio FX220, which has an i815 >graphics chip. > I've tried both 0 and 1 for reset_video (but set via sysctl). And I has 6-CURRENT now, but this notebook never returned from suspend=20 (with 5.3 too). It has ATI RADEON chip. Probably I should try firewire console to detect what happens on resume, but firewire bus itself should be resumed first.=20 Suspend/Resume gurus, is it possible to debug dead console resume with firewire ? > -jre --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 10:16:51 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F72416A4CE for ; Mon, 28 Feb 2005 10:16:51 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 6E2F243D46 for ; Mon, 28 Feb 2005 10:16:50 +0000 (GMT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 28 Feb 2005 10:16:49 +0000 (GMT) To: vova@fbsd.ru In-Reply-To: Your message of "Mon, 28 Feb 2005 02:11:58 +0300." <1109545918.1537.8.camel@localhost> Date: Mon, 28 Feb 2005 10:16:48 +0000 From: Ian Dowse Message-ID: <200502281016.aa49779@salmon.maths.tcd.ie> cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 10:16:51 -0000 In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschikov writes: >What notebook you have ? I was not such lucky. > >I Has SONY VAIO PCG-Z1WA, by zzz it sleeps ok,=20 >With patch it even said about saving VESA data. >On any key after it is awakes, spin up drive and fan, but screen still >black (even no backlight), and it is very unlike that I get console back >(typing has no effect, even when I try to call kdb). > >Also if I try this patch with vesa module loaded it just carsh in vm86 >mode on zzz (curproc acpiconf). > >Any suggestions are very welcome. It is probably necessary to get this working with VESA to have much of a chance of it helping, since otherwise only the basic VGA registers will be saved and restored. One possible reason for the vm86 crash is that it appears our VESA code cannot handle saving more than 4k of state data. Does it make any difference if you revert the part of the patch that changed STATE_MOST to STATE_ALL? i.e. change the two uses of STATE_ALL in vesa.c back to STATE_MOST. I found that with SAVE_MOST, I needed to switch to X and back before the console would display, but the backlight did come on immediately. Ian From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 15:28:15 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1B7616A4CE for ; Mon, 28 Feb 2005 15:28:15 +0000 (GMT) Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.com [194.25.134.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id A903543D39 for ; Mon, 28 Feb 2005 15:28:15 +0000 (GMT) (envelope-from ingoguse@t-online.de) Received: from fwd28.aul.t-online.de by mailout11.sul.t-online.com with smtp id 1D5mog-0000xA-00; Mon, 28 Feb 2005 16:28:14 +0100 Received: from [192.168.2.100] (Go1PFBZVQeo7DcNh-zvXocOiGokRNIBpNEyele2r7jesctocUqHMgZ@[62.226.32.61]) by fwd28.sul.t-online.de with esmtp id 1D5moK-2LDkNE0; Mon, 28 Feb 2005 16:27:52 +0100 Message-ID: <42233889.1040407@t-online.de> Date: Mon, 28 Feb 2005 16:28:09 +0100 From: Ingo Guse User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ID: Go1PFBZVQeo7DcNh-zvXocOiGokRNIBpNEyele2r7jesctocUqHMgZ X-TOI-MSGID: 1bc6d213-61cb-4899-a638-2223fee6a13a Subject: kernel search for ata-slave delays boot X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 15:28:16 -0000 I installed FBSD5.3 sucessfully on Toshiba-SatelliteM30 notebook. When the kernel boots, it searches for slave-drives on ata0 and 1. As there isn´t one, that causes delay during boot. How can I prevent the kernel to look for slave drives? I think something with loader.conf and hints, but I cannot find relevant items in the docs. Any suggestions? Thanks. From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 16:03:53 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4ED816A4CE for ; Mon, 28 Feb 2005 16:03:53 +0000 (GMT) Received: from azzurro.acantho.net (azzurro.acantho.net [213.174.160.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 083B943D48 for ; Mon, 28 Feb 2005 16:03:53 +0000 (GMT) (envelope-from admin@acantho.com) Received: from localhost.localdomain (unknown [10.174.190.103]) by azzurro.acantho.net (Postfix) with ESMTP id 717C239251C for ; Mon, 28 Feb 2005 17:03:49 +0100 (CET) Received: from admin by localhost.localdomain with local (Exim 4.44) id 1D5nNY-0002Ct-JQ for freebsd-mobile@freebsd.org; Mon, 28 Feb 2005 17:04:16 +0100 Date: Mon, 28 Feb 2005 17:04:16 +0100 From: dario-dot-ferroni-at-acantho-com@acantho.com To: freebsd-mobile@freebsd.org Message-ID: <20050228160416.GA8452@acantho.com> References: <20050228154804.GA8441@acantho.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050228154804.GA8441@acantho.com> User-Agent: Mutt/1.5.6+20040907i Subject: GPRS over bluetooth X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 16:03:53 -0000 Hi folks, Following the handbook, I tried to set up GPRS over bluetooth with a Nokia 6310i on my Dell Latitude D505 running FreeBSD 5.3. Everything seems working OK by bluetooth, until I try using rfcomm_pppd, where I keep getting this error: Feb 20 16:54:45 pc-bsd rfcomm_pppd[766]: Could not connect socket. Connection refused (61) I made several tries before posting but without results; attached you can find my configuration files. Any help, suggestion or link is greatly appreciated. Many thanks in advance Dan ---------------------------------------------------------------------- pc-bsd# dmesg | grep ubt0 ubt0: Dell BC02 Bluetooth USB Adapter, rev 2.00/12.66, addr 2 ubt0: Dell BC02 Bluetooth USB Adapter, rev 2.00/12.66, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 pc-bsd# /etc/rc.bluetooth start ubt0 BD_ADDR: Features: 0xff 0xff 0x8f 0x78 0x18 0x18 00 0x80 <3-Slot> <5-Slot> Max. ACL packet size: 192 bytes Number of ACL packets: 8 Max. SCO packet size: 64 bytes Number of SCO packets: 8 pc-bsd# hccontrol -n ubt0hci inquiry Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 00 Page Scan Mode: 00 Class: 50:02:04 Clock offset: 0x100b Inquiry complete. Status: No error [00] pc-bsd# l2ping -a 0 bytes from seq_no=0 time=133.043 ms result=0 0 bytes from seq_no=0 time=133.043 ms result=0 0 bytes from seq_no=0 time=133.043 ms result=0 0 bytes from seq_no=0 time=133.043 ms result=0 pc-bsd# rfcomm_pppd -a -c -C 1 -l rfcomm-dialup pc-bsd# pc-bsd# tail -f /var/log/messages Feb 20 16:54:45 pc-bsd rfcomm_pppd[766]: Could not connect socket. Connection refused (61) pc-bsd# tail -f /var/log/ppp.log pc-bsd# hcidump -x HCIDump - HCI packet analyzer ver 1.5 device: any snap_len: 65535 filter: 0xffffffff < HCI Command: Create Connection(0x01|0x0005) plen 13 07 05 3C 57 60 00 18 CC 00 00 00 00 00 > HCI Event: Command Status(0x0f) plen 4 00 01 05 04 > HCI Event: Connect Complete(0x03) plen 11 00 2E 00 07 05 3C 57 60 00 01 00 < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 2E 00 0E 00 < ACL data: handle 0x002e flags 0x02 dlen 12 L2CAP(s): Connect req: psm 3 scid 0x0059 > HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 > HCI Event: Max Slots Change(0x1b) plen 3 2E 00 05 > HCI Event: Command Complete(0x0e) plen 6 01 0D 08 00 2E 00 > ACL data: handle 0x002e flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0059 result 0 status 0 < ACL data: handle 0x002e flags 0x02 dlen 12 L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0 > HCI Event: QoS Setup Complete(0x0d) plen 21 00 2E 00 00 01 00 00 00 00 00 00 00 00 88 13 00 00 FF FF FF FF > HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 > ACL data: handle 0x002e flags 0x02 dlen 16 > ACL data: handle 0x002e flags 0x01 dlen 16 > ACL data: handle 0x002e flags 0x01 dlen 8 L2CAP(s): Config req: dcid 0x0059 flags 0x0000 clen 28 MTU 32772 Unknown (type 03, len 22) < ACL data: handle 0x002e flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0 > ACL data: handle 0x002e flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0059 flags 0x0000 result 0 clen 0 < ACL data: handle 0x002e flags 0x02 dlen 8 L2CAP(d): cid 0x40 len 4 [psm 3] RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c > HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 > ACL data: handle 0x002e flags 0x02 dlen 8 L2CAP(d): cid 0x59 len 4 [psm 3] RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 < ACL data: handle 0x002e flags 0x02 dlen 18 L2CAP(d): cid 0x40 len 14 [psm 3] RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 667 max_retrans 0 credits 7 > HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 > ACL data: handle 0x002e flags 0x02 dlen 16 > ACL data: handle 0x002e flags 0x01 dlen 2 L2CAP(d): cid 0x59 len 14 [psm 3] RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0 frame_size 324 max_retrans 0 credits 0 < ACL data: handle 0x002e flags 0x02 dlen 8 L2CAP(d): cid 0x40 len 4 [psm 3] RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59 > HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 > HCI Event: Link Key Request(0x17) plen 6 07 05 3C 57 60 00 > HCI Event: Disconn Complete(0x05) plen 4 00 2E 00 08 ----------- hcsecd.conf ----------- device { bdaddr c:e:l:l:p:h:o:n:e ; name "Nokia 6310i" ; key nokey ; pin "1234" ; } -------- ppp.conf -------- default: set log Phase Chat LCP IPCP CCP tun command ident user-ppp VERSION (built COMPILATIONDATE) rfcomm-dialup: enable force-scripts set debug all set speed 115200 set authname "test" set authkey "test" set phone "*99#" set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK \ AT+CGDCONT=1,IP,internet.wind \ \"\" AT OK-AT-OK ATE1Q0 OK \\dATD\\T TIMEOUT 40 CONNECT" set login set timeout 30 enable dns resolv rewrite set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 17:12:24 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E1A016A4CE for ; Mon, 28 Feb 2005 17:12:24 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id E41F443D1F for ; Mon, 28 Feb 2005 17:12:23 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 31E5B3BE95; Mon, 28 Feb 2005 11:12:23 -0600 (CST) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14659-01-32; Mon, 28 Feb 2005 11:12:23 -0600 (CST) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mailgate1b.savvis.net (Postfix) with ESMTP id ED04C3BE2E; Mon, 28 Feb 2005 11:12:22 -0600 (CST) Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 28 Feb 2005 11:11:53 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 28 Feb 2005 11:11:51 -0600 Message-ID: <422350D1.3080906@savvis.net> Date: Mon, 28 Feb 2005 09:11:45 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dario-dot-ferroni-at-acantho-com@acantho.com References: <20050228154804.GA8441@acantho.com> <20050228160416.GA8452@acantho.com> In-Reply-To: <20050228160416.GA8452@acantho.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Feb 2005 17:11:51.0694 (UTC) FILETIME=[9856CAE0:01C51DB8] X-Virus-Scanned: amavisd-new at savvis.net cc: freebsd-mobile@freebsd.org Subject: Re: GPRS over bluetooth X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 17:12:24 -0000 Hello Dan, it seems that you did not start hcsecd(8). according to the dump everything stops after "Link Key Request" event. that is your phone is trying to authenticate incoming connection. hcsecd(8) must be running as it responds to authentication requests. thanks, max p.s. next time please ask bluetooth related questions in freebsd-bluetooth mailing list. dario-dot-ferroni-at-acantho-com@acantho.com wrote: > Hi folks, > Following the handbook, I tried to set up GPRS over bluetooth with a Nokia 6310i > on my Dell Latitude D505 running FreeBSD 5.3. > Everything seems working OK by bluetooth, until I try using rfcomm_pppd, where I > keep getting this error: > > Feb 20 16:54:45 pc-bsd rfcomm_pppd[766]: Could not connect socket. > Connection refused (61) > > I made several tries before posting but without results; attached you can find my > configuration files. > > Any help, suggestion or link is greatly appreciated. > > Many thanks in advance > > Dan > > > > > ---------------------------------------------------------------------- > pc-bsd# dmesg | grep ubt0 > ubt0: Dell BC02 Bluetooth USB Adapter, rev 2.00/12.66, addr 2 > ubt0: Dell BC02 Bluetooth USB Adapter, rev 2.00/12.66, addr 2 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, > bulk-out=0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 > > pc-bsd# /etc/rc.bluetooth start ubt0 > BD_ADDR: > Features: 0xff 0xff 0x8f 0x78 0x18 0x18 00 0x80 > <3-Slot> <5-Slot> > > > > > > Max. ACL packet size: 192 bytes > Number of ACL packets: 8 > Max. SCO packet size: 64 bytes > Number of SCO packets: 8 > > pc-bsd# hccontrol -n ubt0hci inquiry > Inquiry result, num_responses=1 > Inquiry result #0 > BD_ADDR: > Page Scan Rep. Mode: 0x1 > Page Scan Period Mode: 00 > Page Scan Mode: 00 > Class: 50:02:04 > Clock offset: 0x100b > Inquiry complete. Status: No error [00] > > pc-bsd# l2ping -a > 0 bytes from seq_no=0 time=133.043 ms result=0 > 0 bytes from seq_no=0 time=133.043 ms result=0 > 0 bytes from seq_no=0 time=133.043 ms result=0 > 0 bytes from seq_no=0 time=133.043 ms result=0 > > pc-bsd# rfcomm_pppd -a -c -C 1 -l > rfcomm-dialup > pc-bsd# > > pc-bsd# tail -f /var/log/messages > Feb 20 16:54:45 pc-bsd rfcomm_pppd[766]: Could not connect socket. > Connection refused (61) > > pc-bsd# tail -f /var/log/ppp.log > > pc-bsd# hcidump -x > HCIDump - HCI packet analyzer ver 1.5 > device: any snap_len: 65535 filter: 0xffffffff > < HCI Command: Create Connection(0x01|0x0005) plen 13 > 07 05 3C 57 60 00 18 CC 00 00 00 00 00 > >>HCI Event: Command Status(0x0f) plen 4 00 01 05 04 >>HCI Event: Connect Complete(0x03) plen 11 > > 00 2E 00 07 05 3C 57 60 00 01 00 > < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 > 2E 00 0E 00 > < ACL data: handle 0x002e flags 0x02 dlen 12 > L2CAP(s): Connect req: psm 3 scid 0x0059 > >>HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 >>HCI Event: Max Slots Change(0x1b) plen 3 2E 00 05 >>HCI Event: Command Complete(0x0e) plen 6 01 0D 08 00 2E 00 >>ACL data: handle 0x002e flags 0x02 dlen 16 > > L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0059 result 0 status 0 > < ACL data: handle 0x002e flags 0x02 dlen 12 > L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0 > >>HCI Event: QoS Setup Complete(0x0d) plen 21 > > 00 2E 00 00 01 00 00 00 00 00 00 00 00 88 13 00 00 FF FF FF > FF > >>HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 >>ACL data: handle 0x002e flags 0x02 dlen 16 >>ACL data: handle 0x002e flags 0x01 dlen 16 >>ACL data: handle 0x002e flags 0x01 dlen 8 > > L2CAP(s): Config req: dcid 0x0059 flags 0x0000 clen 28 > MTU 32772 Unknown (type 03, len 22) > < ACL data: handle 0x002e flags 0x02 dlen 14 > L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0 > >>ACL data: handle 0x002e flags 0x02 dlen 14 > > L2CAP(s): Config rsp: scid 0x0059 flags 0x0000 result 0 clen 0 > < ACL data: handle 0x002e flags 0x02 dlen 8 > L2CAP(d): cid 0x40 len 4 [psm 3] > RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c > >>HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 >>HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 >>ACL data: handle 0x002e flags 0x02 dlen 8 > > L2CAP(d): cid 0x59 len 4 [psm 3] > RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 > < ACL data: handle 0x002e flags 0x02 dlen 18 > L2CAP(d): cid 0x40 len 14 [psm 3] > RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 > dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size > 667 max_retrans 0 credits 7 > >>HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 >>ACL data: handle 0x002e flags 0x02 dlen 16 >>ACL data: handle 0x002e flags 0x01 dlen 2 > > L2CAP(d): cid 0x59 len 14 [psm 3] > RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 > dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0 frame_size > 324 max_retrans 0 credits 0 > < ACL data: handle 0x002e flags 0x02 dlen 8 > L2CAP(d): cid 0x40 len 4 [psm 3] > RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59 > >>HCI Event: Number of Completed Packets(0x13) plen 5 01 2E 00 01 00 >>HCI Event: Link Key Request(0x17) plen 6 07 05 3C 57 60 00 >>HCI Event: Disconn Complete(0x05) plen 4 > > 00 2E 00 08 > > ----------- > hcsecd.conf > ----------- > device { > bdaddr c:e:l:l:p:h:o:n:e ; > name "Nokia 6310i" ; > key nokey ; > pin "1234" ; > } > > -------- > ppp.conf > -------- > > default: > set log Phase Chat LCP IPCP CCP tun command > ident user-ppp VERSION (built COMPILATIONDATE) > > rfcomm-dialup: > enable force-scripts > set debug all > set speed 115200 > set authname "test" > set authkey "test" > set phone "*99#" > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ > \"\" AT OK-AT-OK \ > AT+CGDCONT=1,IP,internet.wind \ > \"\" AT OK-AT-OK ATE1Q0 OK \\dATD\\T TIMEOUT 40 CONNECT" > set login > set timeout 30 > enable dns > > resolv rewrite > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > add default HISADDR > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 17:39:25 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 071F816A4D3 for ; Mon, 28 Feb 2005 17:39:25 +0000 (GMT) Received: from mailbox7.ucsd.edu (mailbox7.ucsd.edu [132.239.1.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D00443D64 for ; Mon, 28 Feb 2005 17:39:24 +0000 (GMT) (envelope-from david@aogsquid.ucsd.edu) Received: from smtp.ucsd.edu (smtp-a.ucsd.edu [132.239.1.49]) by mailbox7.ucsd.edu (8.13.1/8.13.1) with ESMTP id j1SHdKqJ066730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 28 Feb 2005 09:39:21 -0800 (PST) Received: from [192.168.231.16] (aogsquid.ucsd.edu [132.239.152.182]) by smtp.ucsd.edu (8.12.10/8.9.3) with ESMTP id j1SHdKTg005754 for ; Mon, 28 Feb 2005 09:39:20 -0800 (PST) Message-ID: <42235748.8050403@aogsquid.ucsd.edu> Date: Mon, 28 Feb 2005 09:39:20 -0800 From: David Horwitt User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041008 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org References: <200502270431.aa10917@salmon.maths.tcd.ie> In-Reply-To: <200502270431.aa10917@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Greylisting: NO DELAY (Trusted relay host); processed by UCSD_GL-v1.1 on mailbox7.ucsd.edu; Mon, 28 February 2005 17:39:21 +0000 (UTC) X-MailScanner: PASSED (v1.2.8 48414 j1SHdKqJ066730 mailbox7.ucsd.edu) Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 17:39:25 -0000 Ian Dowse wrote: > It's possible that the experimantal patch below may help on some > notebooks where the display does not recover from a suspend-resume > cycle. It makes use of the VESA BIOS to save the display settings > before the system suspends and then restores them on resume. The > patch is against -CURRENT, but might apply against RELENG_5 without > too much trouble. > > I have a JVC laptop here where this is the only way I have found > so far to bring the LCD back to life after resuming, so maybe it > will help on other systems too. > > To test it, apply the patch and rebuild your kernel + modules. You > need to either have 'options VESA' in the kernel config or else > load the vesa module. It may also be worth trying with the > hw.acpi.reset_video sysctl set to 0, since rerunning the VGA POST > should be unnecessary. > > Ian > > Patch also at: http://people.freebsd.org/~iedowse/vesa_restore.diff > > Thank you here as well. This patch allows my Vaio TR3 to now resume correctly, modulo some fxp and mouse issues. 5.3-STABLE, hw.acpi.reset_video=0 DH From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 20:26:19 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 109BF16A4DA for ; Mon, 28 Feb 2005 20:26:19 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 2039B43D2D for ; Mon, 28 Feb 2005 20:26:18 +0000 (GMT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 28 Feb 2005 20:26:17 +0000 (GMT) To: vova@fbsd.ru In-Reply-To: Your message of "Mon, 28 Feb 2005 10:16:48 GMT." <200502281016.aa49779@salmon.maths.tcd.ie> Date: Mon, 28 Feb 2005 20:26:16 +0000 From: Ian Dowse Message-ID: <200502282026.aa38504@salmon.maths.tcd.ie> cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 20:26:19 -0000 In message <200502281016.aa49779@salmon.maths.tcd.ie>, Ian Dowse writes: >In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschikov writes: >>Also if I try this patch with vesa module loaded it just carsh in vm86 >>mode on zzz (curproc acpiconf). > >It is probably necessary to get this working with VESA to have much >of a chance of it helping, since otherwise only the basic VGA >registers will be saved and restored. > >One possible reason for the vm86 crash is that it appears our VESA >code cannot handle saving more than 4k of state data. Does it make >any difference if you revert the part of the patch that changed >STATE_MOST to STATE_ALL? i.e. change the two uses of STATE_ALL in >vesa.c back to STATE_MOST. I found that with SAVE_MOST, I needed >to switch to X and back before the console would display, but the >backlight did come on immediately. I've updated the patch at http://people.freebsd.org/~iedowse/vesa_restore.diff so that the VESA code allows up to 8k of state storage and will fail if the BIOS claims to need more space. Could you try this with the vesa module loaded and with both 0 and 1 for hw.acpi.reset_video? Ian From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 21:17:08 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E95616A4CE; Mon, 28 Feb 2005 21:17:08 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 6AA6243D54; Mon, 28 Feb 2005 21:17:07 +0000 (GMT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 28 Feb 2005 21:17:06 +0000 (GMT) To: current@freebsd.org, freebsd-mobile@freebsd.org In-Reply-To: Your message of "Mon, 28 Feb 2005 21:06:14 GMT." <200502282106.j1SL6EjM066161@repoman.freebsd.org> Date: Mon, 28 Feb 2005 21:17:06 +0000 From: Ian Dowse Message-ID: <200502282117.aa52128@salmon.maths.tcd.ie> Subject: VESA display resume support (Re: cvs commit: src/sys/dev/fb vgareg.h src/sys/isa vga_isa.c) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 21:17:08 -0000 FYI, this and the previous commit to sys/i386/isa vesa.c may help notebooks displays that don't recover from a suspend/resume. You probably need to enable VESA support for it to make a difference, and may need to set hw.acpi.reset_video=0 also. Let me know if this causes any problems - due to the variety of VESA implementations out there, this may need a sysctl knob to disable it on problem hardware. Ian In message <200502282106.j1SL6EjM066161@repoman.freebsd.org>, Ian Dowse writes: >iedowse 2005-02-28 21:06:14 UTC > > FreeBSD src repository > > Modified files: > sys/dev/fb vgareg.h > sys/isa vga_isa.c > Log: > Save and restore the VGA state across a suspend-resume cycle. This > is particularly useful when VESA is available (either `options VESA' > or load the vesa module), as BIOSes in some notebooks may correctly > save and restore LCD panel settings using VESA in cases where calling > the video BIOS POST is not effective. On some systems it may also > be necessary to set the hw.acpi.reset_video sysctl to 0. > > Revision Changes Path > 1.8 +1 -0 src/sys/dev/fb/vgareg.h > 1.33 +55 -0 src/sys/isa/vga_isa.c From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 28 23:46:56 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 438F116A4CE for ; Mon, 28 Feb 2005 23:46:56 +0000 (GMT) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D415343D2F for ; Mon, 28 Feb 2005 23:46:55 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) j1SNknW8011012; Mon, 28 Feb 2005 18:46:49 -0500 (EST) Date: Mon, 28 Feb 2005 18:46:49 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "M. Warner Losh" In-Reply-To: <20050216.084004.117280004.imp@bsdimp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) cc: freebsd-mobile@freebsd.org Subject: Re: dc no worky with , also LOR X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Eischen List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 23:46:56 -0000 On Wed, 16 Feb 2005, M. Warner Losh wrote: > Dan, > > My Xircom cardbus cards work here for me, and I didn't see anything > odd enough to explain WHY things went south, only that they did. > Which one is the X3201? Maybe I don't see this because I'm trying the > wrong cards or don't yet own one (shocking, I know!). I'd like to copy Bill Paul on this, but am gun-shy ;-) I found an older Xircom CardBus Ethernet II adapter that worked. I know it's not a bad adapter because: 1) I've two of them (both shrink-wrapped and brand new) 2) They work under Windows on the same laptop(s). The older Xircom is identically marked - CBE2-100. I can see no physical differences between the older Xircom and the two newer Xircoms. To summarize, these are the cards I have tried: (A) - Xircom RealPort CardBus Ethernet II 10/100 + Modem 56 -- works (B) - Xircom CardBus Ethernet II 10/100, CBE2-100, old -- works (C) - Xircom CardBus Ethernet II 10/100, CBE2-100, new, qty 2 -- neither work When I boot verbose, the only difference I see between (B) and (C) is that (B) has a powerspec of 1, while (C) has a powerspec of 2: (B) powerspec 1 supports D0 D1 D2 D3 current D0 (C) powerspec 2 supports D0 D1 D2 D3 current D0 Full boot messages available on request. -- (B) Old Xircom, works pcib2: device cardbus0 requested decoded memory range 0xf4000000-0xfbffffff pcib2: device cardbus0 requested decoded memory range 0xf4000000-0xfbffffff pcib2: device cardbus0 requested decoded I/O range 0xe000-0xffff found-> vendor=0x115d, dev=0x0003, revid=0x03 bus=4, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0x14 (5000 ns), maxlat=0x28 (10000 ns) intpin=a, irq=222 powerspec 1 supports D0 D1 D2 D3 current D0 dc0: port 0xe000-0xe07f mem 0xf4002000-0xf40027ff, 0xf4002800-0xf4002fff irq 10 at device 0.0 on cardbus0 pcib2: device dc0 requested decoded I/O range 0xe000-0xe07f miibus0: on dc0 tdkphy0: on miibus0 tdkphy0: OUI 0x00c039, model 0x0014, rev. 11 tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: bpf attached dc0: Ethernet address: 00:10:a4:8a:17:17 dc0: if_start running deferred for Giant dc0: [GIANT-LOCKED] -- (C) Newer Xircoms, don't work pcib2: device cardbus0 requested decoded memory range 0xf4000000-0xfbffffff pcib2: device cardbus0 requested decoded memory range 0xf4000000-0xfbffffff pcib2: device cardbus0 requested decoded I/O range 0xe000-0xffff found-> vendor=0x115d, dev=0x0003, revid=0x03 bus=4, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0x14 (5000 ns), maxlat=0x28 (10000 ns) intpin=a, irq=222 powerspec 2 supports D0 D1 D2 D3 current D0 dc0: port 0xe000-0xe07f mem 0xf4002000-0xf40027ff, 0xf4002800-0xf4002fff irq 10 at device 0.0 on cardbus0 pcib2: device dc0 requested decoded I/O range 0xe000-0xe07f dc0: MII without any PHY! lock order reversal 1st 0xc1b67d40 dc0 (network driver) @ /opt/FreeBSD/src/sys/pci/if_dc.c:2358 2nd 0xc07c9800 ACPI root bus (ACPI root bus) @ /opt/FreeBSD/src/sys/dev/acpica/acpi.c:1050 KDB: stack backtrace: kdb_backtrace(0,ffffffff,c07dfb08,c07e0d50,c07a88ac) at kdb_backtrace+0x29 witness_checkorder(c07c9800,9,c0741eb5,41a) at witness_checkorder+0x54c _sx_xlock(c07c9800,c0741eb5,41a,d36cea04,c05af97c) at _sx_xlock+0x50 acpi_release_resource(c1979a00,c1bdf380,1,0,c1b81c80) at acpi_release_resource+0x26 bus_generic_release_resource(c1a46580,c1bdf380,1,0,c1b81c80) at bus_generic_release_resource+0x64 resource_list_release(c1c24504,c1a46980,c1bdf380,1,0) at resource_list_release+0x6e bus_generic_rl_release_resource(c1a46980,c1bdf380,1,0,c1b81c80) at bus_generic_rl_release_resource+0x5e bus_generic_release_resource(c1a4c180,c1bdf380,1,0,c1b81c80) at bus_generic_release_resource+0x64 resource_list_release(c1c24504,c1a4ca00,c1bdf380,1,0) at resource_list_release+0x6e bus_generic_rl_release_resource(c1a4ca00,c1bdf380,1,0,c1b81c80) at bus_generic_rl_release_resource+0x5e cbb_cardbus_release_resource(c1a4cc00,c1bdf380,1,0,c1b81c80) at cbb_cardbus_release_resource+0x98 cbb_release_resource(c1a4cc00,c1bdf380,1,0,c1b81c80) at cbb_release_resource+0x42 resource_list_release(c1c24504,c1a57400,c1bdf380,1,0) at resource_list_release+0xfb bus_generic_rl_release_resource(c1a57400,c1bdf380,1,0,c1b81c80) at bus_generic_rl_release_resource+0x5e bus_release_resource(c1bdf380,1,0,c1b81c80) at bus_release_resource+0x61 dc_detach(c1bdf380) at dc_detach+0xb2 dc_attach(c1bdf380) at dc_attach+0xe20 device_attach(c1bdf380,0,c1bdf380,c1c24500,0) at device_attach+0x58 device_probe_and_attach(c1bdf380,c1c24500,c1a57400,c1bdf380,c1a57400,c1bdf380) at device_probe_and_attach+0xe0 cardbus_attach_card(c1a57400) at cardbus_attach_card+0x1ae cbb_insert(c1a73800) at cbb_insert+0xd2 cbb_event_thread(c1a73800,d36ced48,c1a73800,c04fddb4,0) at cbb_event_thread+0x129 fork_exit(c04fddb4,c1a73800,d36ced48) at fork_exit+0xa4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd36ced7c, ebp = 0 --- device_attach: dc0 attach returned 6 From owner-freebsd-mobile@FreeBSD.ORG Tue Mar 1 03:12:25 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F9BD16A4D0 for ; Tue, 1 Mar 2005 03:12:25 +0000 (GMT) Received: from diamond.34sp.com (diamond.34sp.com [195.50.105.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAB9643D2F for ; Tue, 1 Mar 2005 03:12:23 +0000 (GMT) (envelope-from list@understudy.net) Received: (qmail 55199 invoked from network); 1 Mar 2005 03:12:22 -0000 Received: from adsl-11-166-118.mia.bellsouth.net (HELO ?10.0.0.124?) (65.11.166.118) by mcp.34sp.com with SMTP; 1 Mar 2005 03:12:20 -0000 Message-ID: <4223DD8E.2000501@understudy.net> Date: Mon, 28 Feb 2005 22:12:14 -0500 From: Understudy User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-mobile@FreeBSD.org References: <20050219040357.47106754@spadger.best.vwh.net> <42197CA3.7050709@understudy.net> <421E331C.10804@siol.net> <20050224181142.B60128@sasami.jurai.net> <421E7780.6050800@understudy.net> <20050224202147.A60128@sasami.jurai.net> <421EAAA5.3090304@understudy.net> <20050225095658.D60128@sasami.jurai.net> <42228B46.9050900@understudy.net> <20050227232531.U60128@sasami.jurai.net> In-Reply-To: <20050227232531.U60128@sasami.jurai.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Thinkpad 600e interrupt storm X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 03:12:25 -0000 Okay, it looks like the beginning of the end. After doing a bit more reading I found a few settings that might work to solve my interrupt storm problem. First and foremost I want to thank everyone who has been helping me on the list. You patience and understanding is gratefully appreciated. Unfortunately my ignorance is the biggest problem in all of this. Here is what happened. I could not get Matt's smapi program to work for me. Most likely because it has to be extracted and made in a specific way. I never had the /sys/module/bios/smapi that he mentioned. I tried extracting it again and ended up with the same result. Most likely there is some easy step I missed. Unfortunately I don't really know how to code or understand the structure behind FreeBSD or any other OS. I went back to google and found a few pages that had a tip here and a tip there. I also found a bit of information on getting the sound card to work. I also have the OLDCARD section commented out. I am using the NEWCARD stuff that comes with GENERIC. So here is the kernel: # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.413.2.6.2.2 2004/10/24 18:02:52 scottl Exp $ # Slacker.bjh.homenet custom settings # 1.leave only cpu I686_CPU uncommented # 2.ident SLACKER uncommented machine i386 #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident SLACKER # To statically compile in device wiring instead of /boot/device.hints # Slacker custom settings # leave hints commented #hints "GENERIC.hints" # Default places to look for devices. # Slacker custom settings # Unless otherwise noted all below are uncommented options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking # comment INET6 #options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device # Comment NFSCLIENT #options NFSCLIENT # Network Filesystem Client # Comment NFSSERVER #options NFSSERVER # Network Filesystem Server # Comment NFS_ROOT #options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 # Comment SCSI_DELAY #options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers # Slacker custom settings # All of SCSI Controllers are commented #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device ahd # AHA39320/29320 and onboard AIC79xx devices #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') #device trm # Tekram DC395U/UW/F DC315U adapters #device adv # Advansys SCSI adapters #device adw # Advansys wide SCSI adapters #device aha # Adaptec 154x SCSI adapters #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. #device bt # Buslogic/Mylex MultiMaster SCSI adapters #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals # Slacker custom settings # all commented except for scbus and da device scbus # SCSI bus (required for SCSI) #device ch # SCSI media changers device da # Direct Access (disks) #device sa # Sequential Access (tape etc) #device cd # CD #device pass # Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem # Slacker custom settings # All of this section is commented out #device amr # AMI MegaRAID #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device ciss # Compaq Smart RAID 5* #device dpt # DPT Smartcache III, IV - See NOTES for options #device hptmv # Highpoint RocketRAID 182x #device iir # Intel Integrated RAID #device ips # IBM (Adaptec) ServeRAID #device mly # Mylex AcceleRAID/eXtremeRAID #device twa # 3ware 9000 series PATA/SATA RAID # RAID controllers # Slacker custom settings # All of this section commented out #device aac # Adaptec FSA RAID #device aacp # SCSI passthrough for aac (requires CAM) #device ida # Compaq Smart RAID #device mlx # Mylex DAC960 family #device pst # Promise Supertrak SX6000 #device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) # Slacker custom settings # uncomment apm device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # PCCARD (PCMCIA) support # OLDCARD #nodevice cbb # cardbus (yenta) bridge #nodevice pcic # ExCA ISA and PCI bridges #device pccard # PC Card (16-bit) bus #device cardbus # CardBus (32-bit) bus #device card # pccard bus #device pcic # PCMCIA bridge # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to the sio and/or ppc drivers): #device puc # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device em # Intel PRO/1000 adapter Gigabit Ethernet Card device ixgb # Intel PRO/10GbE Ethernet Card device txp # 3Com 3cR990 (``Typhoon'') device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bfe # Broadcom BCM440x 10/100 Ethernet device bge # Broadcom BCM570xx Gigabit Ethernet device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device lge # Level 1 LXT1001 gigabit ethernet device nge # NatSemi DP83820 gigabit ethernet device pcn # AMD Am79C97x PCI 10/100 (precedence over 'lnc') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet device ste # Sundance ST201 (D-Link DFE-550TX) device ti # Alteon Networks Tigon I/II gigabit Ethernet device tl # Texas Instruments ThunderLAN device tx # SMC EtherPower II (83c170 ``EPIC'') device vge # VIA VT612x gigabit ethernet device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard NICs included. device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards device ex # Intel EtherExpress Pro/10 and Pro/10+ device ep # Etherlink III based cards device fe # Fujitsu MB8696x based cards device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. device lnc # NE2100, NE32-VL Lance Ethernet cards device sn # SMC's 9000 series of Ethernet chips device xe # Xircom pccard Ethernet # ISA devices that use the old ISA shims #device le # Wireless NIC cards device wlan # 802.11 support device an # Aironet 4500/4800 802.11 wireless NICs. device awi # BayStack 660 and others device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices. device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" #device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # USB Ethernet, requires mii device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet # FireWire support # Slacker custom settings # all of this section commented out #device firewire # FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) #Sound Support # Slacker custom settings # sound driver uncommented #device pcm device sound device snd_mss #end of kernel okay then I went for a modification on /boot/device.hints . This shut off acpi and turned on apmd. I am not sure what the big deal on this issue is but you can sure get mail going back and forth on acpi and apm issues. Here is /boot/device.hints : # $FreeBSD: src/sys/i386/conf/GENERIC.hints,v 1.13 2004/04/01 21:48:31 alfred Exp $ hint.fdc.0.at="isa" hint.fdc.0.port="0x3F0" hint.fdc.0.irq="6" hint.fdc.0.drq="2" hint.fd.0.at="fdc0" hint.fd.0.drive="0" hint.fd.1.at="fdc0" hint.fd.1.drive="1" hint.ata.0.at="isa" hint.ata.0.port="0x1F0" hint.ata.0.irq="14" hint.ata.1.at="isa" hint.ata.1.port="0x170" hint.ata.1.irq="15" hint.adv.0.at="isa" hint.adv.0.disabled="1" hint.bt.0.at="isa" hint.bt.0.disabled="1" hint.aha.0.at="isa" hint.aha.0.disabled="1" hint.aic.0.at="isa" hint.aic.0.disabled="1" hint.atkbdc.0.at="isa" hint.atkbdc.0.port="0x060" hint.atkbd.0.at="atkbdc" hint.atkbd.0.irq="1" hint.psm.0.at="atkbdc" hint.psm.0.irq="12" hint.vga.0.at="isa" hint.sc.0.at="isa" hint.sc.0.flags="0x100" hint.vt.0.at="isa" hint.vt.0.disabled="1" hint.apm.0.disabled="0" hint.apm.0.flags="0x20" hint.pcic.0.at="isa" # hint.pcic.0.irq="10" # Default to polling hint.pcic.0.port="0x3e0" hint.pcic.0.maddr="0xd0000" hint.pcic.1.at="isa" hint.pcic.1.irq="11" hint.pcic.1.port="0x3e2" hint.pcic.1.maddr="0xd4000" hint.pcic.1.disabled="1" hint.sio.0.at="isa" hint.sio.0.port="0x3F8" hint.sio.0.flags="0x10" hint.sio.0.irq="4" hint.sio.1.at="isa" hint.sio.1.port="0x2F8" hint.sio.1.irq="3" hint.sio.2.at="isa" hint.sio.2.disabled="1" hint.sio.2.port="0x3E8" hint.sio.2.irq="5" hint.sio.3.at="isa" hint.sio.3.disabled="1" hint.sio.3.port="0x2E8" hint.sio.3.irq="9" hint.ppc.0.at="isa" hint.ppc.0.irq="7" hint.ed.0.at="isa" hint.ed.0.disabled="1" hint.ed.0.port="0x280" hint.ed.0.irq="10" hint.ed.0.maddr="0xd8000" hint.cs.0.at="isa" hint.cs.0.disabled="1" hint.cs.0.port="0x300" hint.sn.0.at="isa" hint.sn.0.disabled="1" hint.sn.0.port="0x300" hint.sn.0.irq="10" hint.ie.0.at="isa" hint.ie.0.disabled="1" hint.ie.0.port="0x300" hint.ie.0.irq="10" hint.ie.0.maddr="0xd0000" hint.fe.0.at="isa" hint.fe.0.disabled="1" hint.fe.0.port="0x300" hint.lnc.0.at="isa" hint.lnc.0.disabled="1" hint.lnc.0.port="0x280" hint.lnc.0.irq="10" hint.lnc.0.drq="0" # added for cbb hw.cbb.start_memory="0x20000000" hint.acpi.0.disable="1" hw.pci.allow_unsupported_io_range="1" Then I found out about a having a /boot/loader.conf . This was not a file that I had originally so I created it. Here it is: hw.cbb.start_memory="0x20000000" hw.pci.allow_unsupported_io_range="1" hint.acpi.0.disabled="1" hint.pcm.0.flags="0x10" Okay the I went and did make buildkernel and make installkernel. I figured I had nothing to lose. I almost did a back flip when I saw it boot and no interrupt storms. Here is the dmesg: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #13: Mon Feb 28 02:38:59 EST 2005 root@Slacker.bjh.homenet:/usr/obj/usr/src/sys/SLACKER Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (363.96-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 134021120 (127 MB) avail memory = 121507840 (115 MB) npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0x40000000-0x43ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) cbb0: mem 0x50102000-0x50102fff irq 11 at device 2.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pci0: at device 6.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0x8400-0x841f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) cpu0 on motherboard orm0: at iomem 0xc0000-0xcbfff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse Explorer, device ID 4 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) pcm0: at port 0x220-0x233,0x388-0x38b,0x530-0x537 irq 5 drq 0,1 flags 0x10 on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounters tick every 10.000 msec ad0: 11513MB [23392/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master PIO4 ed1: at port 0x100-0x11f irq 11 function 0 config 32 on pccard1 ed1: Ethernet address: 00:50:ba:cb:54:f0 ed1: if_start running deferred for Giant ed1: type DL10022 (16 bit) miibus0: on ed1 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Mounting root from ufs:/dev/ad0s1a I don't know what the "unkown" stuff means but the the IRQ conflicts appear to be gone. Here is the result of dmesg | grep irq [bhorne@Slacker:bhorne, 09:46 PM, Mon Feb 28]>dmesg | grep irq cbb0: mem 0x50102000-0x50102fff irq 11 at device 2.0 on pci0 cbb1: mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0 uhci0: port 0x8400-0x841f irq 11 at device 7.2 on pci0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio1: configured irq 3 not in bitmap of probed irqs 0 unknown: can't assign resources (irq) pcm0: at port 0x220-0x233,0x388-0x38b,0x530-0x537 irq 5 drq 0,1 flags 0x10 on isa0 ed1: at port 0x100-0x11f irq 11 function 0 config 32 on pccard1 I am not sure if this is a final acceptable solution, so I submit this for approval. I know there is a ton of information here. However I don't want to leave something important out. Thanks again everyone. Let me know. Sincerely, Brendhan From owner-freebsd-mobile@FreeBSD.ORG Tue Mar 1 05:53:20 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C771C16A4CE for ; Tue, 1 Mar 2005 05:53:20 +0000 (GMT) Received: from sasami.jurai.net (sasami.jurai.net [69.17.104.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F9C443D3F for ; Tue, 1 Mar 2005 05:53:20 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [69.17.104.113]) by sasami.jurai.net (8.13.1/8.13.1) with ESMTP id j215rHm8018065; Tue, 1 Mar 2005 00:53:19 -0500 (EST) (envelope-from mdodd@FreeBSD.ORG) Date: Tue, 1 Mar 2005 00:53:17 -0500 (EST) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: Understudy In-Reply-To: <4223DD8E.2000501@understudy.net> Message-ID: <20050301005118.P16908@sasami.jurai.net> References: <20050219040357.47106754@spadger.best.vwh.net> <42197CA3.7050709@understudy.net> <421E331C.10804@siol.net> <20050224181142.B60128@sasami.jurai.net> <421E7780.6050800@understudy.net> <20050224202147.A60128@sasami.jurai.net> <421EAAA5.3090304@understudy.net> <20050225095658.D60128@sasami.jurai.net> <42228B46.9050900@understudy.net> <20050227232531.U60128@sasami.jurai.net> <4223DD8E.2000501@understudy.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (sasami.jurai.net [69.17.104.113]); Tue, 01 Mar 2005 00:53:19 -0500 (EST) cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Thinkpad 600e interrupt storm X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 05:53:20 -0000 On Mon, 28 Feb 2005, Understudy wrote: > Here is what happened. I could not get Matt's smapi program to work for > me. Most likely because it has to be extracted and made in a specific > way. I never had the /sys/module/bios/smapi that he mentioned. Its /sys/modules/bios/smapi/ ^ The 's' is important. -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00 From owner-freebsd-mobile@FreeBSD.ORG Tue Mar 1 05:59:02 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A723316A4CE for ; Tue, 1 Mar 2005 05:59:02 +0000 (GMT) Received: from diamond.34sp.com (diamond.34sp.com [195.50.105.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCDCD43D60 for ; Tue, 1 Mar 2005 05:59:01 +0000 (GMT) (envelope-from list@understudy.net) Received: (qmail 87057 invoked from network); 1 Mar 2005 05:59:00 -0000 Received: from adsl-11-166-118.mia.bellsouth.net (HELO ?10.0.0.124?) (65.11.166.118) by mcp.34sp.com with SMTP; 1 Mar 2005 05:59:00 -0000 Message-ID: <4224049E.3020201@understudy.net> Date: Tue, 01 Mar 2005 00:58:54 -0500 From: Understudy User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-mobile@FreeBSD.org References: <20050219040357.47106754@spadger.best.vwh.net> <42197CA3.7050709@understudy.net> <421E331C.10804@siol.net> <20050224181142.B60128@sasami.jurai.net> <421E7780.6050800@understudy.net> <20050224202147.A60128@sasami.jurai.net> <421EAAA5.3090304@understudy.net> <20050225095658.D60128@sasami.jurai.net> <42228B46.9050900@understudy.net> <20050227232531.U60128@sasami.jurai.net> <4223DD8E.2000501@understudy.net> <20050301005118.P16908@sasami.jurai.net> In-Reply-To: <20050301005118.P16908@sasami.jurai.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Thinkpad 600e interrupt storm X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 05:59:02 -0000 Matthew N. Dodd wrote: > On Mon, 28 Feb 2005, Understudy wrote: > >> Here is what happened. I could not get Matt's smapi program to work >> for me. Most likely because it has to be extracted and made in a >> specific way. I never had the /sys/module/bios/smapi that he mentioned. > > > Its /sys/modules/bios/smapi/ > ^ > The 's' is important. > Yes I guess it would be. I am on it . I feel like a heel. I knew it was something simple and stupid. Sincerely, Brendhan From owner-freebsd-mobile@FreeBSD.ORG Tue Mar 1 08:52:40 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B109A16A4CE for ; Tue, 1 Mar 2005 08:52:40 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6CBB43D1F for ; Tue, 1 Mar 2005 08:52:39 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.44 (FreeBSD)) id 1D637F-0000NG-Rj; Tue, 01 Mar 2005 11:52:29 +0300 From: Vladimir Grebenschikov To: Ian Dowse In-Reply-To: <200502282026.aa38504@salmon.maths.tcd.ie> References: <200502282026.aa38504@salmon.maths.tcd.ie> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Tue, 01 Mar 2005 11:52:29 +0300 Message-Id: <1109667149.1098.5.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.1.5 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 08:52:40 -0000 =F7 =D0=CE, 28/02/2005 =D7 20:26 +0000, Ian Dowse =D0=C9=DB=C5=D4: >In message <200502281016.aa49779@salmon.maths.tcd.ie>, Ian Dowse writes: >>In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschikov wr= ites: >>>Also if I try this patch with vesa module loaded it just carsh in vm86 >>>mode on zzz (curproc acpiconf). >> >>It is probably necessary to get this working with VESA to have much >>of a chance of it helping, since otherwise only the basic VGA >>registers will be saved and restored. >> >>One possible reason for the vm86 crash is that it appears our VESA >>code cannot handle saving more than 4k of state data. Does it make >>any difference if you revert the part of the patch that changed >>STATE_MOST to STATE_ALL? i.e. change the two uses of STATE_ALL in >>vesa.c back to STATE_MOST. I found that with SAVE_MOST, I needed >>to switch to X and back before the console would display, but the >>backlight did come on immediately. > >I've updated the patch at > > http://people.freebsd.org/~iedowse/vesa_restore.diff > >so that the VESA code allows up to 8k of state storage and will >fail if the BIOS claims to need more space. Could you try this with >the vesa module loaded and with both 0 and 1 for hw.acpi.reset_video? Unfortunately it panics on boot with this patch. (before mounting root). I have console just now to check what happens, will do this later and send you panic output.=20 >Ian --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 00:57:43 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43DC916A4CE for ; Wed, 2 Mar 2005 00:57:43 +0000 (GMT) Received: from ni-mail2.dna.utvinternet.net (mail2.u.tv [194.46.8.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF85443D49 for ; Wed, 2 Mar 2005 00:57:41 +0000 (GMT) (envelope-from aidanwhyte@eircom.net) Received: from moriarty (unverified [194.46.94.108]) by ni-mail2.dna.utvinternet.net for ; Wed, 2 Mar 2005 00:57:40 +0000 Message-ID: <00e001c51ec2$d6b17550$2201040a@moriarty> From: "Aidan Whyte" To: Date: Wed, 2 Mar 2005 00:57:42 -0000 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-RFC2646: Format=Flowed; Original Subject: 802.11a pcmcia cards X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 00:57:43 -0000 Anyone know of any 802.11a (/ab/abg/ag/whatever) pcmcia cards that have an external antenna connector? I've read that they're hard to find because most 802.11a cards use a mix of 2 frequency bands to give more non-overlapping channels, but the FCC doesn't allow one of those bands to be used for external use so no equipment transmitting over that spectrum can have external antenna connectors. I'm in Europe where this doesn't apply, but I still can't find any card with an external antenna connector :o/ If one was found that was known to work under freebsd that would be a big bonus :o) TIA, Aidan From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 01:00:43 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01F1416A4CE for ; Wed, 2 Mar 2005 01:00:43 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB96043D5D for ; Wed, 2 Mar 2005 01:00:42 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j2210dar029404; Tue, 1 Mar 2005 17:00:39 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j2210dsB029403; Tue, 1 Mar 2005 17:00:39 -0800 Date: Tue, 1 Mar 2005 17:00:39 -0800 From: Brooks Davis To: Aidan Whyte Message-ID: <20050302010039.GA28884@odin.ac.hmc.edu> References: <00e001c51ec2$d6b17550$2201040a@moriarty> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: <00e001c51ec2$d6b17550$2201040a@moriarty> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-mobile@freebsd.org Subject: Re: 802.11a pcmcia cards X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 01:00:43 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Mar 02, 2005 at 12:57:42AM -0000, Aidan Whyte wrote: > Anyone know of any 802.11a (/ab/abg/ag/whatever) pcmcia cards that > have an external antenna connector? > > I've read that they're hard to find because most 802.11a cards use a > mix of 2 frequency bands to give more non-overlapping channels, but > the FCC doesn't allow one of those bands to be used for external use > so no equipment transmitting over that spectrum can have external > antenna connectors. I'm in Europe where this doesn't apply, but I > still can't find any card with an external antenna connector :o/ If > one was found that was known to work under freebsd that would be a big > bonus :o) I can't help you with a PCCard, but I've got a DLink AG PCI card with an external antenna (how else :) so that's not likely the real issue. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCJRA2XY6L6fI4GtQRApWoAJwP4PU/CezFdpwhe3gVykMpSdlD0QCgjbEE AwcRd2tqwWFHehEd32jolkQ= =BA7O -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW-- From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 02:01:17 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CE5716A4CE for ; Wed, 2 Mar 2005 02:01:17 +0000 (GMT) Received: from mailgate.uni-paderborn.de (mailgate.uni-paderborn.de [131.234.22.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82B7343D1D for ; Wed, 2 Mar 2005 02:01:16 +0000 (GMT) (envelope-from arne@rfc2549.org) Received: from dsl-213-023-207-232.arcor-ip.net ([213.23.207.232] helo=[192.168.0.23]) by mailgate.uni-paderborn.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id 1D6JAf-0002Cq-EX; Wed, 02 Mar 2005 03:01:05 +0100 Message-ID: <42251E5F.90707@rfc2549.org> Date: Wed, 02 Mar 2005 03:01:03 +0100 From: Arne Schwabe User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Aidan Whyte References: <00e001c51ec2$d6b17550$2201040a@moriarty> In-Reply-To: <00e001c51ec2$d6b17550$2201040a@moriarty> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-UNI-PB_FAK-EIM-MailScanner-Information: Please see http://imap.uni-paderborn.de for details X-UNI-PB_FAK-EIM-MailScanner: Found to be clean X-UNI-PB_FAK-EIM-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.208, required 4, AUTH_EIM_USER -5.00, RCVD_IN_NJABL_DUL 1.66, RCVD_IN_SORBS_DUL 0.14) X-MailScanner-From: arne@rfc2549.org cc: freebsd-mobile@freebsd.org Subject: Re: 802.11a pcmcia cards X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 02:01:17 -0000 Aidan Whyte wrote: >Anyone know of any 802.11a (/ab/abg/ag/whatever) pcmcia cards that have an external antenna >connector? > >I've read that they're hard to find because most 802.11a cards use a mix of 2 frequency bands to >give more non-overlapping channels, but the FCC doesn't allow one of those bands to be used for >external use so no equipment transmitting over that spectrum can have external antenna connectors. >I'm in Europe where this doesn't apply, but I still can't find any card with an external antenna >connector :o/ If one was found that was known to work under freebsd that would be a big bonus :o) > > > I had no luck either finding one, even the 11a cards for the proxim ap 2000 we have at the university have no antenna connnector even though they have external antenna (Well I am not 100% sure, they may have under the plastic) http://www.proxim.com/products/wifi/ap/ap200011a/index.html If you find one I would be happy if you can tell me too. Arne From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 07:21:11 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCCA216A4CE for ; Wed, 2 Mar 2005 07:21:11 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B1B443D39 for ; Wed, 2 Mar 2005 07:21:11 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.44 (FreeBSD)) id 1D6E1U-0000oZ-4k; Tue, 01 Mar 2005 23:31:16 +0300 From: Vladimir Grebenschikov To: Ian Dowse In-Reply-To: <200502282026.aa38504@salmon.maths.tcd.ie> References: <200502282026.aa38504@salmon.maths.tcd.ie> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Tue, 01 Mar 2005 23:31:15 +0300 Message-Id: <1109709075.1329.3.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.1.5 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 07:21:12 -0000 =F7 =D0=CE, 28/02/2005 =D7 20:26 +0000, Ian Dowse =D0=C9=DB=C5=D4: >In message <200502281016.aa49779@salmon.maths.tcd.ie>, Ian Dowse writes: >>In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschikov wr= ites: >>>Also if I try this patch with vesa module loaded it just carsh in vm86 >>>mode on zzz (curproc acpiconf). >> >>It is probably necessary to get this working with VESA to have much >>of a chance of it helping, since otherwise only the basic VGA >>registers will be saved and restored. >> >>One possible reason for the vm86 crash is that it appears our VESA >>code cannot handle saving more than 4k of state data. Does it make >>any difference if you revert the part of the patch that changed >>STATE_MOST to STATE_ALL? i.e. change the two uses of STATE_ALL in >>vesa.c back to STATE_MOST. I found that with SAVE_MOST, I needed >>to switch to X and back before the console would display, but the >>backlight did come on immediately. > >I've updated the patch at > > http://people.freebsd.org/~iedowse/vesa_restore.diff > >so that the VESA code allows up to 8k of state storage and will >fail if the BIOS claims to need more space. Could you try this with >the vesa module loaded and with both 0 and 1 for hw.acpi.reset_video? I've rechecked patch with fresh kernel build and firewire console. It does not panics and does not awake :(=20 As in previous variant it sleeps ok, but on awake it only spin up HDD. No any other activity seen, it does not react on keys, firewire console is dead. It does not answer on network activity. Probably It hangs while try to restore console, and I should try to disable console at all ?=20 Any other ideas ? >Ian --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 11:54:51 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC45816A4CF for ; Wed, 2 Mar 2005 11:54:51 +0000 (GMT) Received: from omega.lacnic.net.uy (lacnic.net.uy [200.40.228.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC77B43D46 for ; Wed, 2 Mar 2005 11:54:50 +0000 (GMT) (envelope-from pablo@omega.lacnic.net.uy) Received: from omega.lacnic.net.uy (localhost.localdomain [127.0.0.1]) by omega.lacnic.net.uy (8.12.11/8.12.5) with ESMTP id j22CuFcv012407 for ; Wed, 2 Mar 2005 09:56:15 -0300 Received: (from pablo@localhost) by omega.lacnic.net.uy (8.12.11/8.12.5/Submit) id j22CuFTO012406 for freebsd-mobile@freebsd.org; Wed, 2 Mar 2005 09:56:15 -0300 Date: Wed, 2 Mar 2005 09:56:15 -0300 From: Pablo Allietti To: freebsd-mobile@freebsd.org Message-ID: <20050302125615.GD11238@omega.lacnic.net.uy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: Freebsd 5.3 X-Organization: LACNIC X-URL: http://lacnic.net/ X-Lacnic-MailScanner-Information: Please contact Lacnic for more information (lacnic at lacnic.net) X-Lacnic-MailScanner: Found to be clean X-MailScanner-From: pablo@omega.lacnic.net.uy Subject: wireless linksys X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 11:54:51 -0000 hi all, i recently buy a linksys USB wireless card is a WUSB54G. is possible to make work this card in freebsd 5.3 ? in dmesg say ugen0: Cisco-Linksys Wireless-G USB Network Adapter, rev 2.00/0.04, addr 2 but nothing else. and ifconfig dont show this card. any body can guide my to install this card? thanks -- Pablo Allietti LACNIC -------------- From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 12:57:46 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A42D16A4CE for ; Wed, 2 Mar 2005 12:57:46 +0000 (GMT) Received: from mail0.jaist.ac.jp (mail0.jaist.ac.jp [150.65.5.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id B764E43D3F for ; Wed, 2 Mar 2005 12:57:43 +0000 (GMT) (envelope-from zrelli@jaist.ac.jp) Received: from mail-vc.jaist.ac.jp (mail-vc.jaist.ac.jp [150.65.5.31]) by mail0.jaist.ac.jp (3.7W-jaist_mail) with ESMTP id j22Cvgl05552 for ; Wed, 2 Mar 2005 21:57:42 +0900 (JST) Received: from mail-vc.jaist.ac.jp (localhost [127.0.0.1]) by localhost.jaist.ac.jp (Postfix) with ESMTP id 46B9384B4 for ; Wed, 2 Mar 2005 21:57:42 +0900 (JST) Received: from smtp.jaist.ac.jp (smtp.jaist.ac.jp [150.65.38.97]) by mail-vc.jaist.ac.jp (Postfix) with ESMTP id 1C48B84B1 for ; Wed, 2 Mar 2005 21:57:42 +0900 (JST) Received: from [150.65.42.125] (dm6d25.jaist.ac.jp [150.65.42.125]) by smtp.jaist.ac.jp (3.7W-smtp) with ESMTP id j22Cvf810204 for ; Wed, 2 Mar 2005 21:57:41 +0900 (JST) Message-ID: <422636D3.6030403@jaist.ac.jp> Date: Wed, 02 Mar 2005 21:57:39 +0000 From: Saber Zrelli User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Content-Type: multipart/mixed; boundary="------------030702040700060105090902" Subject: system temperature too high, shutting down soon! X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 12:57:46 -0000 This is a multi-part message in MIME format. --------------030702040700060105090902 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all , I'm runnig FreeBSD 5.3-RELEASE #0 on an IBM Thinkpad R50p , when I run some make install in the ports distribution. I got the following message : tornado root: WARNING: system temperature too high, shutting down soon! After 2-3 secs the system shuts down. when I looked in /var/log/messages after booting , I found : Mar 2 21:24:18 tornado kernel: cpu0: Performance states changed Mar 2 21:24:39 tornado kernel: cpu0: Performance states changed Mar 2 21:24:39 tornado root: WARNING: system temperature too high, shutting down soon! I was using 5.3 CURRENT ( and previous releases ) a while before , and I did not have this problem. my first thoughts is that it is a ACIP problem. but I dont have knowledge about ACPI stuff. I think that some parameters in hw.acpi.thermal are not correct. hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.tz0.temperature: 3312 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3647 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3672 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 specially hw.acpi.thermal.tz0._ACx , there is no cooling level temperatures defined. Also , the hw.acpi.thermal.tz0._CRT: 3672 ,hw.acpi.thermal.tz0._PSV: 3647 are too close , the cpu don't have enough time to cool down before reaching the critical temp. I tried debugging the ACPI module , so I compiled it with debuggin options . but the kernel could not load it and I was running without acpi. I attached < sysctl -a > and < cat /lvar/og/messages > I want to keep using ACPI , and I really need to fix this. For any suggestions , Many thanks -- Saber. --------------030702040700060105090902 Content-Type: text/plain; name="messages" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="messages" Feb 28 21:00:00 tornado newsyslog[732]: logfile turned over due to size>100K Feb 28 21:21:08 tornado halt: halted by zrelli Feb 28 21:21:08 tornado syslogd: exiting on signal 15 Feb 28 21:33:41 tornado syslogd: kernel boot file is /boot/kernel/kernel Feb 28 21:33:41 tornado kernel: Copyright (c) 1992-2004 The FreeBSD Project. Feb 28 21:33:41 tornado kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Feb 28 21:33:41 tornado kernel: The Regents of the University of California. All rights reserved. Feb 28 21:33:41 tornado kernel: FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 Feb 28 21:33:41 tornado kernel: root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Feb 28 21:33:41 tornado kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Feb 28 21:33:41 tornado kernel: CPU: Intel(R) Pentium(R) M processor 1700MHz (1698.57-MHz 686-class CPU) Feb 28 21:33:41 tornado kernel: Origin = "GenuineIntel" Id = 0x695 Stepping = 5 Feb 28 21:33:41 tornado kernel: Features=0xa7e9f9bf Feb 28 21:33:41 tornado kernel: real memory = 1073086464 (1023 MB) Feb 28 21:33:41 tornado kernel: avail memory = 1040527360 (992 MB) Feb 28 21:33:41 tornado kernel: npx0: [FAST] Feb 28 21:33:41 tornado kernel: npx0: on motherboard Feb 28 21:33:41 tornado kernel: npx0: INT 16 interface Feb 28 21:33:41 tornado kernel: acpi0: on motherboard Feb 28 21:33:41 tornado kernel: acpi_ec0: port 0x66,0x62 on acpi0 Feb 28 21:33:41 tornado kernel: acpi0: Power Button (fixed) Feb 28 21:33:41 tornado kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Feb 28 21:33:41 tornado kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 Feb 28 21:33:41 tornado kernel: cpu0: on acpi0 Feb 28 21:33:41 tornado kernel: acpi_tz0: on acpi0 Feb 28 21:33:41 tornado kernel: acpi_lid0: on acpi0 Feb 28 21:33:41 tornado kernel: acpi_button0: on acpi0 Feb 28 21:33:41 tornado kernel: pcib0: port 0xcf8-0xcff on acpi0 Feb 28 21:33:41 tornado kernel: pci0: on pcib0 Feb 28 21:33:41 tornado kernel: agp0: mem 0xd0000000-0xdfffffff at device 0.0 on pci0 Feb 28 21:33:41 tornado kernel: pcib1: at device 1.0 on pci0 Feb 28 21:33:41 tornado kernel: pci1: on pcib1 Feb 28 21:33:41 tornado kernel: pci1: at device 0.0 (no driver attached) Feb 28 21:33:41 tornado kernel: uhci0: port 0x1800-0x181f irq 11 at device 29.0 on pci0 Feb 28 21:33:41 tornado kernel: uhci0: [GIANT-LOCKED] Feb 28 21:33:41 tornado kernel: usb0: on uhci0 Feb 28 21:33:41 tornado kernel: usb0: USB revision 1.0 Feb 28 21:33:41 tornado kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Feb 28 21:33:41 tornado kernel: uhub0: 2 ports with 2 removable, self powered Feb 28 21:33:41 tornado kernel: uhci1: port 0x1820-0x183f irq 11 at device 29.1 on pci0 Feb 28 21:33:41 tornado kernel: uhci1: [GIANT-LOCKED] Feb 28 21:33:41 tornado kernel: usb1: on uhci1 Feb 28 21:33:41 tornado kernel: usb1: USB revision 1.0 Feb 28 21:33:41 tornado kernel: uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Feb 28 21:33:41 tornado kernel: uhub1: 2 ports with 2 removable, self powered Feb 28 21:33:41 tornado kernel: uhci2: port 0x1840-0x185f irq 11 at device 29.2 on pci0 Feb 28 21:33:41 tornado kernel: uhci2: [GIANT-LOCKED] Feb 28 21:33:41 tornado kernel: usb2: on uhci2 Feb 28 21:33:41 tornado kernel: usb2: USB revision 1.0 Feb 28 21:33:41 tornado kernel: uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Feb 28 21:33:41 tornado kernel: uhub2: 2 ports with 2 removable, self powered Feb 28 21:33:41 tornado kernel: pci0: at device 29.7 (no driver attached) Feb 28 21:33:41 tornado kernel: pcib2: at device 30.0 on pci0 Feb 28 21:33:41 tornado kernel: pci2: on pcib2 Feb 28 21:33:41 tornado kernel: cbb0: mem 0xb0000000-0xb0000fff irq 11 at device 0.0 on pci2 Feb 28 21:33:41 tornado kernel: cardbus0: on cbb0 Feb 28 21:33:41 tornado kernel: pccard0: <16-bit PCCard bus> on cbb0 Feb 28 21:33:41 tornado kernel: cbb1: mem 0xb1000000-0xb1000fff irq 11 at device 0.1 on pci2 Feb 28 21:33:41 tornado kernel: cardbus1: on cbb1 Feb 28 21:33:41 tornado kernel: pccard1: <16-bit PCCard bus> on cbb1 Feb 28 21:33:41 tornado kernel: em0: port 0x8000-0x803f mem 0xc0200000-0xc020ffff,0xc0220000-0xc023ffff irq 11 at device 1.0 on pci2 Feb 28 21:33:41 tornado kernel: em0: Ethernet address: 00:0d:60:89:c2:67 Feb 28 21:33:41 tornado kernel: em0: Speed:N/A Duplex:N/A Feb 28 21:33:41 tornado kernel: pci2: at device 2.0 (no driver attached) Feb 28 21:33:41 tornado kernel: isab0: at device 31.0 on pci0 Feb 28 21:33:41 tornado kernel: isa0: on isab0 Feb 28 21:33:41 tornado kernel: atapci0: port 0x1860-0x186f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 Feb 28 21:33:41 tornado kernel: ata0: channel #0 on atapci0 Feb 28 21:33:41 tornado kernel: ata1: channel #1 on atapci0 Feb 28 21:33:41 tornado kernel: pci0: at device 31.3 (no driver attached) Feb 28 21:33:41 tornado kernel: pci0: at device 31.5 (no driver attached) Feb 28 21:33:41 tornado kernel: pci0: at device 31.6 (no driver attached) Feb 28 21:33:41 tornado kernel: atkbdc0: port 0x64,0x60 irq 1 on acpi0 Feb 28 21:33:41 tornado kernel: atkbd0: irq 1 on atkbdc0 Feb 28 21:33:41 tornado kernel: kbd0 at atkbd0 Feb 28 21:33:41 tornado kernel: atkbd0: [GIANT-LOCKED] Feb 28 21:33:41 tornado kernel: psm0: irq 12 on atkbdc0 Feb 28 21:33:41 tornado kernel: psm0: [GIANT-LOCKED] Feb 28 21:33:41 tornado kernel: psm0: model Generic PS/2 mouse, device ID 0 Feb 28 21:33:41 tornado kernel: fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 Feb 28 21:33:41 tornado kernel: fdc0: [FAST] Feb 28 21:33:41 tornado kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 Feb 28 21:33:41 tornado kernel: sio0: port may not be enabled Feb 28 21:33:41 tornado kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Feb 28 21:33:41 tornado kernel: sio0: type 8250 or not responding Feb 28 21:33:41 tornado kernel: ppc0: port 0x3bc-0x3be irq 7 on acpi0 Feb 28 21:33:41 tornado kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Feb 28 21:33:41 tornado kernel: ppbus0: on ppc0 Feb 28 21:33:41 tornado kernel: plip0: on ppbus0 Feb 28 21:33:41 tornado kernel: lpt0: on ppbus0 Feb 28 21:33:41 tornado kernel: lpt0: Interrupt-driven port Feb 28 21:33:41 tornado kernel: ppi0: on ppbus0 Feb 28 21:33:41 tornado kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Feb 28 21:33:41 tornado kernel: sio1: port may not be enabled Feb 28 21:33:41 tornado kernel: acpi_cmbat0: on acpi0 Feb 28 21:33:41 tornado kernel: acpi_acad0: on acpi0 Feb 28 21:33:41 tornado kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Feb 28 21:33:41 tornado kernel: sio1: port may not be enabled Feb 28 21:33:41 tornado kernel: orm0: at iomem 0xdc000-0xdffff,0xd1000-0xd1fff,0xd0000-0xd0fff on isa0 Feb 28 21:33:41 tornado kernel: pmtimer0 on isa0 Feb 28 21:33:41 tornado kernel: sc0: at flags 0x100 on isa0 Feb 28 21:33:41 tornado kernel: sc0: VGA <16 virtual consoles, flags=0x300> Feb 28 21:33:41 tornado kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Feb 28 21:33:41 tornado kernel: sio1: port may not be enabled Feb 28 21:33:41 tornado kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Feb 28 21:33:41 tornado kernel: Timecounter "TSC" frequency 1698565963 Hz quality 800 Feb 28 21:33:41 tornado kernel: Timecounters tick every 10.000 msec Feb 28 21:33:41 tornado kernel: acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% Feb 28 21:33:41 tornado kernel: ad0: 53564MB [108828/16/63] at ata0-master UDMA100 Feb 28 21:33:41 tornado kernel: ata1-slave: FAILURE - ATAPI_IDENTIFY timed out Feb 28 21:33:41 tornado last message repeated 2 times Feb 28 21:33:41 tornado kernel: acd0: DVDR at ata1-master UDMA33 Feb 28 21:33:41 tornado kernel: Mounting root from ufs:/dev/ad0s2a Feb 28 21:33:41 tornado kernel: em0: Link is up 10 Mbps Half Duplex Feb 28 21:34:00 tornado login: ROOT LOGIN (root) ON ttyv0 Feb 28 21:34:24 tornado reboot: rebooted by root Feb 28 21:34:24 tornado syslogd: exiting on signal 15 Mar 2 19:43:09 tornado syslogd: kernel boot file is /boot/kernel/kernel Mar 2 19:43:09 tornado kernel: Copyright (c) 1992-2004 The FreeBSD Project. Mar 2 19:43:09 tornado kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Mar 2 19:43:09 tornado kernel: The Regents of the University of California. All rights reserved. Mar 2 19:43:09 tornado kernel: FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 Mar 2 19:43:09 tornado kernel: root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Mar 2 19:43:09 tornado kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Mar 2 19:43:09 tornado kernel: CPU: Intel(R) Pentium(R) M processor 1700MHz (1698.56-MHz 686-class CPU) Mar 2 19:43:09 tornado kernel: Origin = "GenuineIntel" Id = 0x695 Stepping = 5 Mar 2 19:43:09 tornado kernel: Features=0xa7e9f9bf Mar 2 19:43:09 tornado kernel: real memory = 1073086464 (1023 MB) Mar 2 19:43:09 tornado kernel: avail memory = 1040527360 (992 MB) Mar 2 19:43:09 tornado kernel: npx0: [FAST] Mar 2 19:43:09 tornado kernel: npx0: on motherboard Mar 2 19:43:09 tornado kernel: npx0: INT 16 interface Mar 2 19:43:09 tornado kernel: acpi0: on motherboard Mar 2 19:43:09 tornado kernel: acpi_ec0: port 0x66,0x62 on acpi0 Mar 2 19:43:09 tornado kernel: acpi0: Power Button (fixed) Mar 2 19:43:09 tornado kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Mar 2 19:43:09 tornado kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 Mar 2 19:43:09 tornado kernel: cpu0: on acpi0 Mar 2 19:43:09 tornado kernel: acpi_tz0: on acpi0 Mar 2 19:43:09 tornado kernel: acpi_lid0: on acpi0 Mar 2 19:43:09 tornado kernel: acpi_button0: on acpi0 Mar 2 19:43:09 tornado kernel: pcib0: port 0xcf8-0xcff on acpi0 Mar 2 19:43:09 tornado kernel: pci0: on pcib0 Mar 2 19:43:09 tornado kernel: agp0: mem 0xd0000000-0xdfffffff at device 0.0 on pci0 Mar 2 19:43:09 tornado kernel: pcib1: at device 1.0 on pci0 Mar 2 19:43:09 tornado kernel: pci1: on pcib1 Mar 2 19:43:09 tornado kernel: pci1: at device 0.0 (no driver attached) Mar 2 19:43:09 tornado kernel: uhci0: port 0x1800-0x181f irq 11 at device 29.0 on pci0 Mar 2 19:43:09 tornado kernel: uhci0: [GIANT-LOCKED] Mar 2 19:43:09 tornado kernel: usb0: on uhci0 Mar 2 19:43:09 tornado kernel: usb0: USB revision 1.0 Mar 2 19:43:09 tornado kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 2 19:43:09 tornado kernel: uhub0: 2 ports with 2 removable, self powered Mar 2 19:43:09 tornado kernel: uhci1: port 0x1820-0x183f irq 11 at device 29.1 on pci0 Mar 2 19:43:09 tornado kernel: uhci1: [GIANT-LOCKED] Mar 2 19:43:09 tornado kernel: usb1: on uhci1 Mar 2 19:43:09 tornado kernel: usb1: USB revision 1.0 Mar 2 19:43:09 tornado kernel: uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 2 19:43:09 tornado kernel: uhub1: 2 ports with 2 removable, self powered Mar 2 19:43:09 tornado kernel: uhci2: port 0x1840-0x185f irq 11 at device 29.2 on pci0 Mar 2 19:43:09 tornado kernel: uhci2: [GIANT-LOCKED] Mar 2 19:43:09 tornado kernel: usb2: on uhci2 Mar 2 19:43:09 tornado kernel: usb2: USB revision 1.0 Mar 2 19:43:09 tornado kernel: uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 2 19:43:09 tornado kernel: uhub2: 2 ports with 2 removable, self powered Mar 2 19:43:09 tornado kernel: pci0: at device 29.7 (no driver attached) Mar 2 19:43:09 tornado kernel: pcib2: at device 30.0 on pci0 Mar 2 19:43:09 tornado kernel: pci2: on pcib2 Mar 2 19:43:09 tornado kernel: cbb0: mem 0xb0000000-0xb0000fff irq 11 at device 0.0 on pci2 Mar 2 19:43:09 tornado kernel: cardbus0: on cbb0 Mar 2 19:43:09 tornado kernel: pccard0: <16-bit PCCard bus> on cbb0 Mar 2 19:43:09 tornado kernel: cbb1: mem 0xb1000000-0xb1000fff irq 11 at device 0.1 on pci2 Mar 2 19:43:09 tornado kernel: cardbus1: on cbb1 Mar 2 19:43:09 tornado kernel: pccard1: <16-bit PCCard bus> on cbb1 Mar 2 19:43:09 tornado kernel: em0: port 0x8000-0x803f mem 0xc0200000-0xc020ffff,0xc0220000-0xc023ffff irq 11 at device 1.0 on pci2 Mar 2 19:43:09 tornado kernel: em0: Ethernet address: 00:0d:60:89:c2:67 Mar 2 19:43:09 tornado kernel: em0: Speed:N/A Duplex:N/A Mar 2 19:43:09 tornado kernel: pci2: at device 2.0 (no driver attached) Mar 2 19:43:09 tornado kernel: isab0: at device 31.0 on pci0 Mar 2 19:43:09 tornado kernel: isa0: on isab0 Mar 2 19:43:09 tornado kernel: atapci0: port 0x1860-0x186f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 Mar 2 19:43:09 tornado kernel: ata0: channel #0 on atapci0 Mar 2 19:43:09 tornado kernel: ata1: channel #1 on atapci0 Mar 2 19:43:09 tornado kernel: pci0: at device 31.3 (no driver attached) Mar 2 19:43:09 tornado kernel: pci0: at device 31.5 (no driver attached) Mar 2 19:43:09 tornado kernel: pci0: at device 31.6 (no driver attached) Mar 2 19:43:09 tornado kernel: atkbdc0: port 0x64,0x60 irq 1 on acpi0 Mar 2 19:43:09 tornado kernel: atkbd0: irq 1 on atkbdc0 Mar 2 19:43:09 tornado kernel: kbd0 at atkbd0 Mar 2 19:43:09 tornado kernel: atkbd0: [GIANT-LOCKED] Mar 2 19:43:09 tornado kernel: psm0: irq 12 on atkbdc0 Mar 2 19:43:09 tornado kernel: psm0: [GIANT-LOCKED] Mar 2 19:43:09 tornado kernel: psm0: model Generic PS/2 mouse, device ID 0 Mar 2 19:43:09 tornado kernel: fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 Mar 2 19:43:09 tornado kernel: fdc0: [FAST] Mar 2 19:43:09 tornado kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 Mar 2 19:43:09 tornado kernel: sio0: port may not be enabled Mar 2 19:43:09 tornado kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Mar 2 19:43:09 tornado kernel: sio0: type 8250 or not responding Mar 2 19:43:09 tornado kernel: ppc0: port 0x3bc-0x3be irq 7 on acpi0 Mar 2 19:43:09 tornado kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Mar 2 19:43:09 tornado kernel: ppbus0: on ppc0 Mar 2 19:43:09 tornado kernel: plip0: on ppbus0 Mar 2 19:43:09 tornado kernel: lpt0: on ppbus0 Mar 2 19:43:09 tornado kernel: lpt0: Interrupt-driven port Mar 2 19:43:09 tornado kernel: ppi0: on ppbus0 Mar 2 19:43:09 tornado kernel: sio1: port 0x2f8-0x2ff irq 3 drq 3 on acpi0 Mar 2 19:43:09 tornado kernel: sio1: type 16550A Mar 2 19:43:09 tornado kernel: acpi_cmbat0: on acpi0 Mar 2 19:43:09 tornado kernel: acpi_acad0: on acpi0 Mar 2 19:43:09 tornado kernel: orm0: at iomem 0xdc000-0xdffff,0xd1000-0xd1fff,0xd0000-0xd0fff on isa0 Mar 2 19:43:09 tornado kernel: pmtimer0 on isa0 Mar 2 19:43:09 tornado kernel: sc0: at flags 0x100 on isa0 Mar 2 19:43:09 tornado kernel: sc0: VGA <16 virtual consoles, flags=0x300> Mar 2 19:43:09 tornado kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Mar 2 19:43:09 tornado kernel: Timecounter "TSC" frequency 1698564535 Hz quality 800 Mar 2 19:43:09 tornado kernel: Timecounters tick every 10.000 msec Mar 2 19:43:09 tornado kernel: acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% Mar 2 19:43:09 tornado kernel: ad0: 53564MB [108828/16/63] at ata0-master UDMA100 Mar 2 19:43:09 tornado kernel: ata1-slave: FAILURE - ATAPI_IDENTIFY timed out Mar 2 19:43:09 tornado last message repeated 2 times Mar 2 19:43:09 tornado kernel: acd0: DVDR at ata1-master UDMA33 Mar 2 19:43:09 tornado kernel: Mounting root from ufs:/dev/ad0s2a Mar 2 19:43:09 tornado kernel: em0: Link is up 10 Mbps Half Duplex Mar 2 19:44:12 tornado login: ROOT LOGIN (root) ON ttyv0 Mar 2 19:45:40 tornado gconfd (zrelli-536): Owner of /var/tmp/orbit-zrelli-a8e8c858 is not the current user Mar 2 19:46:17 tornado su: zrelli to root on /dev/ttyp0 Mar 2 19:46:17 tornado kernel: cd9660: Joliet Extension (Level 3) Mar 2 19:46:35 tornado kernel: pcm0: port 0x18c0-0x18ff,0x1c00-0x1cff mem 0xc0000800-0xc00008ff,0xc0000c00-0xc0000dff irq 11 at device 31.5 on pci0 Mar 2 19:46:35 tornado kernel: pcm0: [GIANT-LOCKED] Mar 2 19:46:35 tornado kernel: pcm0: Mar 2 20:04:09 tornado kernel: cd9660: RockRidge Extension Mar 2 20:06:55 tornado kernel: cd9660: RockRidge Extension Mar 2 21:24:18 tornado kernel: cpu0: Performance states changed Mar 2 21:24:39 tornado kernel: cpu0: Performance states changed Mar 2 21:24:39 tornado root: WARNING: system temperature too high, shutting down soon! Mar 2 21:24:39 tornado syslogd: /dev/:0: No such file or directory Mar 2 21:24:45 tornado syslogd: exiting on signal 15 Mar 2 21:26:10 tornado syslogd: kernel boot file is /boot/kernel/kernel Mar 2 21:26:10 tornado kernel: Copyright (c) 1992-2004 The FreeBSD Project. Mar 2 21:26:10 tornado kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Mar 2 21:26:10 tornado kernel: The Regents of the University of California. All rights reserved. Mar 2 21:26:10 tornado kernel: FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 Mar 2 21:26:10 tornado kernel: root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Mar 2 21:26:10 tornado kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Mar 2 21:26:10 tornado kernel: CPU: Intel(R) Pentium(R) M processor 1700MHz (1698.56-MHz 686-class CPU) Mar 2 21:26:10 tornado kernel: Origin = "GenuineIntel" Id = 0x695 Stepping = 5 Mar 2 21:26:10 tornado kernel: Features=0xa7e9f9bf Mar 2 21:26:10 tornado kernel: real memory = 1073086464 (1023 MB) Mar 2 21:26:10 tornado kernel: avail memory = 1040527360 (992 MB) Mar 2 21:26:10 tornado kernel: npx0: [FAST] Mar 2 21:26:10 tornado kernel: npx0: on motherboard Mar 2 21:26:10 tornado kernel: npx0: INT 16 interface Mar 2 21:26:10 tornado kernel: acpi0: on motherboard Mar 2 21:26:10 tornado kernel: acpi_ec0: port 0x66,0x62 on acpi0 Mar 2 21:26:10 tornado kernel: acpi0: Power Button (fixed) Mar 2 21:26:10 tornado kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Mar 2 21:26:10 tornado kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 Mar 2 21:26:10 tornado kernel: cpu0: on acpi0 Mar 2 21:26:10 tornado kernel: acpi_tz0: on acpi0 Mar 2 21:26:10 tornado kernel: acpi_lid0: on acpi0 Mar 2 21:26:10 tornado kernel: acpi_button0: on acpi0 Mar 2 21:26:10 tornado kernel: pcib0: port 0xcf8-0xcff on acpi0 Mar 2 21:26:10 tornado kernel: pci0: on pcib0 Mar 2 21:26:10 tornado kernel: agp0: mem 0xd0000000-0xdfffffff at device 0.0 on pci0 Mar 2 21:26:10 tornado kernel: pcib1: at device 1.0 on pci0 Mar 2 21:26:10 tornado kernel: pci1: on pcib1 Mar 2 21:26:10 tornado kernel: pci1: at device 0.0 (no driver attached) Mar 2 21:26:10 tornado kernel: uhci0: port 0x1800-0x181f irq 11 at device 29.0 on pci0 Mar 2 21:26:10 tornado kernel: uhci0: [GIANT-LOCKED] Mar 2 21:26:10 tornado kernel: usb0: on uhci0 Mar 2 21:26:10 tornado kernel: usb0: USB revision 1.0 Mar 2 21:26:10 tornado kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 2 21:26:10 tornado kernel: uhub0: 2 ports with 2 removable, self powered Mar 2 21:26:10 tornado kernel: uhci1: port 0x1820-0x183f irq 11 at device 29.1 on pci0 Mar 2 21:26:10 tornado kernel: uhci1: [GIANT-LOCKED] Mar 2 21:26:10 tornado kernel: usb1: on uhci1 Mar 2 21:26:10 tornado kernel: usb1: USB revision 1.0 Mar 2 21:26:10 tornado kernel: uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 2 21:26:10 tornado kernel: uhub1: 2 ports with 2 removable, self powered Mar 2 21:26:10 tornado kernel: uhci2: port 0x1840-0x185f irq 11 at device 29.2 on pci0 Mar 2 21:26:10 tornado kernel: uhci2: [GIANT-LOCKED] Mar 2 21:26:10 tornado kernel: usb2: on uhci2 Mar 2 21:26:10 tornado kernel: usb2: USB revision 1.0 Mar 2 21:26:10 tornado kernel: uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 2 21:26:10 tornado kernel: uhub2: 2 ports with 2 removable, self powered Mar 2 21:26:10 tornado kernel: pci0: at device 29.7 (no driver attached) Mar 2 21:26:10 tornado kernel: pcib2: at device 30.0 on pci0 Mar 2 21:26:10 tornado kernel: pci2: on pcib2 Mar 2 21:26:10 tornado kernel: cbb0: mem 0xb0000000-0xb0000fff irq 11 at device 0.0 on pci2 Mar 2 21:26:10 tornado kernel: cardbus0: on cbb0 Mar 2 21:26:10 tornado kernel: pccard0: <16-bit PCCard bus> on cbb0 Mar 2 21:26:10 tornado kernel: cbb1: mem 0xb1000000-0xb1000fff irq 11 at device 0.1 on pci2 Mar 2 21:26:10 tornado kernel: cardbus1: on cbb1 Mar 2 21:26:10 tornado kernel: pccard1: <16-bit PCCard bus> on cbb1 Mar 2 21:26:10 tornado kernel: em0: port 0x8000-0x803f mem 0xc0200000-0xc020ffff,0xc0220000-0xc023ffff irq 11 at device 1.0 on pci2 Mar 2 21:26:10 tornado kernel: em0: Ethernet address: 00:0d:60:89:c2:67 Mar 2 21:26:10 tornado kernel: em0: Speed:N/A Duplex:N/A Mar 2 21:26:10 tornado kernel: pci2: at device 2.0 (no driver attached) Mar 2 21:26:10 tornado kernel: isab0: at device 31.0 on pci0 Mar 2 21:26:10 tornado kernel: isa0: on isab0 Mar 2 21:26:10 tornado kernel: atapci0: port 0x1860-0x186f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 Mar 2 21:26:10 tornado kernel: ata0: channel #0 on atapci0 Mar 2 21:26:10 tornado kernel: ata1: channel #1 on atapci0 Mar 2 21:26:10 tornado kernel: pci0: at device 31.3 (no driver attached) Mar 2 21:26:10 tornado kernel: pcm0: port 0x18c0-0x18ff,0x1c00-0x1cff mem 0xc0000800-0xc00008ff,0xc0000c00-0xc0000dff irq 11 at device 31.5 on pci0 Mar 2 21:26:10 tornado kernel: pcm0: [GIANT-LOCKED] Mar 2 21:26:10 tornado kernel: pcm0: Mar 2 21:26:10 tornado kernel: pci0: at device 31.6 (no driver attached) Mar 2 21:26:10 tornado kernel: atkbdc0: port 0x64,0x60 irq 1 on acpi0 Mar 2 21:26:10 tornado kernel: atkbd0: irq 1 on atkbdc0 Mar 2 21:26:10 tornado kernel: kbd0 at atkbd0 Mar 2 21:26:10 tornado kernel: atkbd0: [GIANT-LOCKED] Mar 2 21:26:10 tornado kernel: psm0: irq 12 on atkbdc0 Mar 2 21:26:10 tornado kernel: psm0: [GIANT-LOCKED] Mar 2 21:26:10 tornado kernel: psm0: model Generic PS/2 mouse, device ID 0 Mar 2 21:26:10 tornado kernel: fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 Mar 2 21:26:10 tornado kernel: fdc0: [FAST] Mar 2 21:26:10 tornado kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 Mar 2 21:26:10 tornado kernel: sio0: port may not be enabled Mar 2 21:26:10 tornado kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Mar 2 21:26:10 tornado kernel: sio0: type 8250 or not responding Mar 2 21:26:10 tornado kernel: ppc0: port 0x3bc-0x3be irq 7 on acpi0 Mar 2 21:26:10 tornado kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Mar 2 21:26:10 tornado kernel: ppbus0: on ppc0 Mar 2 21:26:10 tornado kernel: plip0: on ppbus0 Mar 2 21:26:10 tornado kernel: lpt0: on ppbus0 Mar 2 21:26:10 tornado kernel: lpt0: Interrupt-driven port Mar 2 21:26:10 tornado kernel: ppi0: on ppbus0 Mar 2 21:26:10 tornado kernel: sio1: port 0x2f8-0x2ff irq 3 drq 3 on acpi0 Mar 2 21:26:10 tornado kernel: sio1: type 16550A Mar 2 21:26:10 tornado kernel: acpi_cmbat0: on acpi0 Mar 2 21:26:10 tornado kernel: acpi_acad0: on acpi0 Mar 2 21:26:10 tornado kernel: orm0: at iomem 0xdc000-0xdffff,0xd1000-0xd1fff,0xd0000-0xd0fff on isa0 Mar 2 21:26:10 tornado kernel: pmtimer0 on isa0 Mar 2 21:26:10 tornado kernel: sc0: at flags 0x100 on isa0 Mar 2 21:26:10 tornado kernel: sc0: VGA <16 virtual consoles, flags=0x300> Mar 2 21:26:10 tornado kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Mar 2 21:26:10 tornado kernel: Timecounter "TSC" frequency 1698564926 Hz quality 800 Mar 2 21:26:10 tornado kernel: Timecounters tick every 10.000 msec Mar 2 21:26:10 tornado kernel: acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% Mar 2 21:26:10 tornado kernel: ad0: 53564MB [108828/16/63] at ata0-master UDMA100 Mar 2 21:26:10 tornado kernel: ata1-slave: FAILURE - ATAPI_IDENTIFY timed out Mar 2 21:26:10 tornado last message repeated 2 times Mar 2 21:26:10 tornado kernel: acd0: DVDR at ata1-master UDMA33 Mar 2 21:26:10 tornado kernel: Mounting root from ufs:/dev/ad0s2a Mar 2 21:26:10 tornado kernel: em0: Link is up 10 Mbps Half Duplex Mar 2 21:26:16 tornado login: ROOT LOGIN (root) ON ttyv0 Mar 2 21:26:32 tornado gconfd (zrelli-505): Owner of /var/tmp/orbit-zrelli-a8e8c858 is not the current user --------------030702040700060105090902 Content-Type: text/plain; name="sysctl-output.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="sysctl-output.txt" kern.ostype: FreeBSD kern.osrelease: 5.3-RELEASE kern.osrevision: 199506 kern.version: FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC kern.maxvnodes: 69950 kern.maxproc: 6164 kern.maxfiles: 12328 kern.argmax: 65536 kern.securelevel: -1 kern.hostname: tornado.jaist.ac.jp kern.hostid: 0 kern.clockrate: { hz = 100, tick = 10000, profhz = 1024, stathz = 128 } kern.posix1version: 200112 kern.ngroups: 16 kern.job_control: 1 kern.saved_ids: 0 kern.boottime: { sec = 1109798729, usec = 285588 } Wed Mar 2 21:25:29 2005 kern.domainname: kern.osreldate: 503001 kern.bootfile: /boot/kernel/kernel kern.maxfilesperproc: 11095 kern.maxprocperuid: 5547 kern.ipc.maxsockbuf: 262144 kern.ipc.sockbuf_waste_factor: 8 kern.ipc.somaxconn: 128 kern.ipc.max_linkhdr: 16 kern.ipc.max_protohdr: 60 kern.ipc.max_hdr: 76 kern.ipc.max_datalen: 132 kern.ipc.nmbclusters: 25600 kern.ipc.maxpipekva: 16777216 kern.ipc.pipes: 126 kern.ipc.pipekva: 1032192 kern.ipc.pipefragretry: 0 kern.ipc.pipeallocfail: 0 kern.ipc.piperesizefail: 0 kern.ipc.piperesizeallowed: 1 kern.ipc.msgmax: 16384 kern.ipc.msgmni: 40 kern.ipc.msgmnb: 2048 kern.ipc.msgtql: 40 kern.ipc.msgssz: 8 kern.ipc.msgseg: 2048 kern.ipc.semmap: 30 kern.ipc.semmni: 10 kern.ipc.semmns: 60 kern.ipc.semmnu: 30 kern.ipc.semmsl: 60 kern.ipc.semopm: 100 kern.ipc.semume: 10 kern.ipc.semusz: 92 kern.ipc.semvmx: 32767 kern.ipc.semaem: 16384 kern.ipc.shmmax: 33554432 kern.ipc.shmmin: 1 kern.ipc.shmmni: 192 kern.ipc.shmseg: 128 kern.ipc.shmall: 8192 kern.ipc.shm_use_phys: 0 kern.ipc.shm_allow_removed: 0 kern.ipc.numopensockets: 177 kern.ipc.maxsockets: 25600 kern.ipc.nsfbufs: 6656 kern.ipc.nsfbufspeak: 3 kern.ipc.nsfbufsused: 0 kern.dummy: 0 kern.ps_strings: 3217031152 kern.usrstack: 3217031168 kern.logsigexit: 1 kern.iov_max: 1024 kern.cam.scsi_delay: 15000 kern.cam.cd.changer.min_busy_seconds: 5 kern.cam.cd.changer.max_busy_seconds: 15 kern.cam.da.retry_count: 4 kern.cam.da.default_timeout: 60 kern.disks: ad0 kern.geom.debugflags: 0 kern.geom.collectstats: 1 kern.elf32.fallback_brand: -1 kern.init_path: /sbin/init:/sbin/oinit:/sbin/init.bak:/stand/sysinstall kern.acct_suspend: 2 kern.acct_resume: 4 kern.acct_chkfreq: 15 kern.cp_time: 15858 0 1483 286 220038 kern.openfiles: 401 kern.kq_calloutmax: 4096 kern.stackprot: 7 kern.ps_arg_cache_limit: 256 kern.lastpid: 712 kern.randompid: 0 kern.ktrace.genio_size: 4096 kern.ktrace.request_pool: 100 kern.module_path: /boot/kernel;/boot/modules kern.malloc: Type InUse MemUse HighUse Requests Size(s) linux 10 1K 1K 10 32 acpidev 75 3K 3K 75 32 acpisem 22 2K 2K 22 64 acpitask 0 0K 1K 474 16,32 acpica 3731 194K 194K 30224 16,32,64,128,256,512,1024,2048 feeder 50 1K 1K 50 16,64 acpibatt 1 1K 1K 1 16 ac97 2 1K 1K 2 16,256 mixer 1 1K 1K 1 1024 GEOM 67 9K 18K 334 16,32,64,128,256,512,1024,2048,4096 atkbddev 2 1K 1K 2 32 pfs_fileno 1 20K 20K 1 pfs_nodes 20 3K 3K 20 128 nexusdev 3 1K 1K 3 16 memdesc 1 4K 8K 11 32,4096 MSDOSFS mount 1 128K 128K 1 UMAHash 2 2K 2K 5 256,512,1024 VM pgdata 2 65K 65K 2 64 DEVFS 130 20K 20K 234 16,32,128,4096 USBdev 3 1K 5K 12 128,512 USB 46 5K 5K 46 16,32,64,128,256 UFS mount 3 7K 7K 3 256,2048,4096 UFS ihash 1 256K 256K 1 UFS dirhash 117 24K 24K 117 16,32,64,128,256,512 newblk 1 1K 1K 1 256 inodedep 1 256K 256K 1 pagedep 1 32K 32K 1 p1003.1b 1 1K 1K 1 16 agp 2 257K 257K 2 16 NFS daemon 1 1K 1K 1 256 NFS hash 1 256K 256K 1 in6_multi 7 1K 1K 7 64 syncache 1 8K 8K 1 hostcache 1 24K 24K 1 in_multi 2 1K 1K 2 32 routetbl 37 4K 4K 96 16,32,64,128,256 entropy 1024 64K 64K 1024 64 lo 1 1K 1K 1 1024 clone 4 16K 16K 4 4096 ether_multi 30 2K 2K 30 16,32,64 ifaddr 29 9K 9K 30 16,32,64,256,512,2048 BPF 7 9K 9K 7 64,128,256,4096 mount 9 3K 3K 14 16,32,128,1024 vnodes 29 7K 7K 160 16,32,64,128,256 cluster_save buffer 0 0K 1K 18 32,64 vfscache 1 512K 512K 1 BIO buffer 678 1356K 1356K 682 2048 pcb 15 5K 5K 121 16,32,64,2048 soname 90 11K 11K 1247 16,32,64,128 tag 0 0K 1K 7 32 ptys 1 1K 1K 1 128 ttys 1119 147K 147K 2484 128,512 shm 10 21K 22K 28 1024 sem 4 7K 7K 4 512,1024,4096 msg 4 25K 25K 4 512,4096 iov 0 0K 1K 82528 16,64,128,256 ioctlops 0 0K 4K 15 512,1024,4096 turnstiles 131 9K 9K 131 64 taskqueue 6 1K 1K 6 64 ppbusdev 3 1K 1K 3 128 sleep queues 131 5K 5K 131 32 sbuf 0 0K 21K 358 16,32,64,128,256,512,1024,2048,4096 rman 199 13K 13K 1018 16,64 ATA generic 4 2K 2K 5 16,512 kobj 234 468K 468K 282 2048 eventhandler 37 2K 2K 37 32,128 devstat 6 13K 13K 6 16,4096 bus-sc 53 32K 115K 2028 16,32,64,128,256,512,1024,2048,4096 bus 930 39K 140K 4619 16,32,64,128,1024 SWAP 2 33K 33K 2 64 sysctltmp 0 0K 1K 3727 16,32,64,128 sysctloid 2276 68K 68K 2276 16,32,64 sysctl 0 0K 1K 129 16,32,64 uidinfo 4 2K 2K 19 32,1024 plimit 16 4K 5K 251 256 cred 27 4K 4K 29320 128 subproc 143 402K 430K 1753 32,4096 proc 2 8K 8K 2 4096 session 25 4K 4K 40 128 pgrp 29 2K 2K 125 64 mtx_pool 1 8K 8K 1 module 346 22K 22K 346 64,128 ip6ndp 5 1K 1K 6 64,128 temp 91 237K 246K 8679 16,32,64,128,256,512,1024,2048,4096 devbuf 1495 3226K 3226K 3463 16,32,64,128,256,512,2048,4096 lockf 4 1K 1K 33 64 linker 65 119K 124K 119 16,32,64,256,1024,4096 KTRACE 100 13K 13K 100 128 ithread 54 5K 5K 55 64,128 zombie 0 0K 1K 613 128 proc-args 42 3K 4K 760 32,64,128,256 kqueue 0 0K 3K 100 128,1024 kenv 106 6K 6K 107 16,32,64,2048 sigio 1 1K 1K 1 32 file desc 135 39K 44K 874 16,32,256,512,2048 cdev 48 12K 12K 48 256 ACD driver 1 2K 2K 1 2048 AR driver 1 1K 3K 3 64,256,2048 AD driver 1 1K 1K 1 128 ISOFS mount 1 256K 256K 1 isadev 19 2K 2K 19 64 ATA DMA 2 1K 1K 2 128 kern.ident: GENERIC kern.maxusers: 384 kern.fallback_elf_brand: -1 kern.kstack_pages: 2 kern.uarea_pages: 1 kern.sync_on_panic: 0 kern.shutdown.poweroff_delay: 5000 kern.shutdown.kproc_shutdown_wait: 60 kern.sugid_coredump: 0 kern.coredump: 1 kern.nodump_coredump: 0 kern.corefile: %N.core kern.fscale: 2048 kern.timecounter.stepwarnings: 0 kern.timecounter.nbinuptime: 2072412 kern.timecounter.nnanouptime: 0 kern.timecounter.nmicrouptime: 758 kern.timecounter.nbintime: 1125934 kern.timecounter.nnanotime: 706947 kern.timecounter.nmicrotime: 418987 kern.timecounter.ngetbinuptime: 0 kern.timecounter.ngetnanouptime: 397 kern.timecounter.ngetmicrouptime: 372490 kern.timecounter.ngetbintime: 0 kern.timecounter.ngetnanotime: 66 kern.timecounter.ngetmicrotime: 381440 kern.timecounter.nsetclock: 2 kern.timecounter.hardware: ACPI-fast kern.timecounter.choice: TSC(800) ACPI-fast(1000) i8254(0) dummy(-1000000) kern.timecounter.tick: 1 kern.threads.thr_scope_sys: 0 kern.threads.thr_concurrency: 0 kern.threads.debug: 0 kern.threads.max_threads_per_proc: 1500 kern.threads.max_groups_per_proc: 1500 kern.threads.max_threads_hits: 0 kern.threads.virtual_cpu: 1 kern.sched.name: 4BSD kern.sched.quantum: 100000 kern.sched.followon: 0 kern.sched.pfollowons: 0 kern.sched.kgfollowons: 0 kern.ccpu: 1948 kern.devstat.numdevs: 1 kern.devstat.generation: 86 kern.devstat.version: 6 kern.kobj_methodcount: 110 kern.log_wakeups_per_second: 5 kern.log_console_output: 1 kern.always_console_output: 0 kern.msgbuf: kern.msgbuf_clear: 0 kern.smp.maxcpus: 1 kern.smp.active: 0 kern.smp.disabled: 0 kern.smp.cpus: 1 kern.nselcoll: 0 kern.drainwait: 300 kern.tty_nin: 9008 kern.tty_nout: 44400 kern.console: consolectl,/ttyd0,consolectl, kern.consmute: 0 kern.consmsgbuf_size: 8192 kern.constty_wakeups_per_second: 5 kern.rootdev: ad0s2a kern.filedelay: 30 kern.dirdelay: 29 kern.metadelay: 28 kern.minvnodes: 17487 kern.chroot_allow_open_directories: 1 kern.rpc.retries: 0 kern.rpc.request: 0 kern.rpc.timeouts: 0 kern.rpc.unexpected: 0 kern.rpc.invalid: 0 kern.random.yarrow.gengateinterval: 10 kern.random.yarrow.bins: 10 kern.random.yarrow.fastthresh: 192 kern.random.yarrow.slowthresh: 256 kern.random.yarrow.slowoverthresh: 2 kern.random.sys.seeded: 1 kern.random.sys.harvest.ethernet: 1 kern.random.sys.harvest.point_to_point: 1 kern.random.sys.harvest.interrupt: 1 kern.random.sys.harvest.swi: 0 vm.vmtotal: System wide totals computed every five seconds: (values in kilobytes) =============================================== Processes: (RUNQ: 1 Disk Wait: 1 Page Wait: 0 Sleep: 52) Virtual Memory: (Total: 2097752K, Active 203100K) Real Memory: (Total: 227404K Active 150712K) Shared Virtual Memory: (Total: 47524K Active: 45020K) Shared Real Memory: (Total: 41220K Active: 39064K) Free Memory Pages: 792156K vm.loadavg: { 0.04 0.09 0.08 } vm.v_free_min: 1688 vm.v_free_target: 7166 vm.v_free_reserved: 414 vm.v_inactive_target: 10749 vm.v_cache_min: 7166 vm.v_cache_max: 14332 vm.v_pageout_free_min: 34 vm.pageout_algorithm: 0 vm.swap_enabled: 1 vm.kmem_size: 335544320 vm.kmem_size_max: 335544320 vm.kmem_size_scale: 3 vm.swap_async_max: 4 vm.dmmax: 32 vm.nswapdev: 1 vm.swap_idle_threshold1: 2 vm.swap_idle_threshold2: 10 vm.v_free_severe: 1051 vm.stats.sys.v_swtch: 895046 vm.stats.sys.v_trap: 241992 vm.stats.sys.v_syscall: 1988563 vm.stats.sys.v_intr: 674974 vm.stats.sys.v_soft: 69644 vm.stats.vm.v_vm_faults: 126574 vm.stats.vm.v_cow_faults: 21759 vm.stats.vm.v_cow_optim: 101 vm.stats.vm.v_zfod: 74936 vm.stats.vm.v_ozfod: 74786 vm.stats.vm.v_swapin: 0 vm.stats.vm.v_swapout: 0 vm.stats.vm.v_swappgsin: 0 vm.stats.vm.v_swappgsout: 0 vm.stats.vm.v_vnodein: 1377 vm.stats.vm.v_vnodeout: 0 vm.stats.vm.v_vnodepgsin: 10661 vm.stats.vm.v_vnodepgsout: 0 vm.stats.vm.v_intrans: 55 vm.stats.vm.v_reactivated: 846 vm.stats.vm.v_pdwakeups: 0 vm.stats.vm.v_pdpages: 0 vm.stats.vm.v_dfree: 0 vm.stats.vm.v_pfree: 28948 vm.stats.vm.v_tfree: 87116 vm.stats.vm.v_page_size: 4096 vm.stats.vm.v_page_count: 255146 vm.stats.vm.v_free_reserved: 414 vm.stats.vm.v_free_target: 7166 vm.stats.vm.v_free_min: 1688 vm.stats.vm.v_free_count: 197841 vm.stats.vm.v_wire_count: 20104 vm.stats.vm.v_active_count: 28027 vm.stats.vm.v_inactive_target: 10749 vm.stats.vm.v_inactive_count: 8877 vm.stats.vm.v_cache_count: 198 vm.stats.vm.v_cache_min: 7166 vm.stats.vm.v_cache_max: 14332 vm.stats.vm.v_pageout_free_min: 34 vm.stats.vm.v_interrupt_free_min: 2 vm.stats.vm.v_forks: 634 vm.stats.vm.v_vforks: 21 vm.stats.vm.v_rforks: 0 vm.stats.vm.v_kthreads: 57 vm.stats.vm.v_forkpages: 65469 vm.stats.vm.v_vforkpages: 1135 vm.stats.vm.v_rforkpages: 0 vm.stats.vm.v_kthreadpages: 0 vm.stats.misc.zero_page_count: 145472 vm.stats.misc.cnt_prezero: 229363 vm.max_proc_mmap: 49344 vm.msync_flush_flags: 3 vm.old_msync: 0 vm.old_contigmalloc: 0 vm.idlezero_enable: 1 vm.idlezero_maxrun: 16 vm.max_launder: 32 vm.pageout_stats_max: 7166 vm.pageout_full_stats_interval: 20 vm.pageout_stats_interval: 5 vm.swap_idle_enabled: 0 vm.defer_swapspace_pageouts: 0 vm.disable_swapspace_pageouts: 0 vm.pageout_lock_miss: 0 vm.zone: ITEM SIZE LIMIT USED FREE REQUESTS FFS2 dinode: 256, 0, 3052, 38, 3161 FFS1 dinode: 128, 0, 0, 0, 0 FFS inode: 140, 0, 3052, 28, 3161 SWAPMETA: 276, 121576, 0, 0, 0 rtentry: 132, 0, 17, 41, 17 ripcb: 180, 25608, 0, 44, 2 sackhole: 16, 0, 0, 203, 2 tcpreass: 20, 1690, 0, 169, 63 hostcache: 88, 15400, 2, 86, 2 syncache: 108, 15372, 0, 0, 0 tcptw: 56, 5159, 0, 134, 1 tcpcb: 448, 25605, 7, 11, 65 inpcb: 180, 25608, 7, 37, 65 udpcb: 180, 25608, 3, 41, 447 unpcb: 140, 25620, 167, 29, 489 socket: 324, 25608, 177, 15, 1010 KNOTE: 68, 0, 0, 112, 100 PIPE: 384, 0, 63, 27, 330 DIRHASH: 1024, 0, 266, 6, 266 NFSNODE: 452, 0, 0, 0, 0 NFSMOUNT: 432, 0, 0, 0, 0 L VFS Cache: 291, 0, 22, 17, 25 S VFS Cache: 68, 0, 3186, 62, 8378 NAMEI: 1024, 0, 0, 20, 70748 VNODEPOLL: 64, 0, 0, 0, 0 VNODE: 264, 0, 3203, 22, 3203 ata_request: 200, 0, 0, 38, 6512 g_bio: 132, 0, 0, 870, 25195 MbufClust: 2048, 25600, 384, 6, 384 Mbuf: 256, 0, 386, 139, 109330 Packet: 256, 0, 384, 141, 18741 VMSPACE: 300, 0, 43, 22, 653 UPCALL: 44, 0, 8, 148, 8 KSEGRP: 104, 0, 112, 63, 112 TID: 140, 0, 1, 53, 1 THREAD: 388, 0, 124, 6, 58197 PROC: 452, 0, 99, 9, 709 Files: 68, 0, 401, 47, 10726 4096: 4096, 0, 155, 12, 7626 2048: 2048, 0, 932, 2, 1344 1024: 1024, 0, 29, 99, 1929 512: 512, 0, 102, 18, 638 256: 256, 0, 264, 21, 1602 128: 128, 0, 1743, 27, 36682 64: 64, 0, 5167, 84, 91568 32: 32, 0, 2931, 120, 6606 16: 16, 0, 2305, 131, 32241 DP fakepg: 72, 0, 4786, 37, 4787 PV ENTRY: 24, 1494805, 67577, 2603, 525812 MAP ENTRY: 68, 0, 3411, 173, 38226 KMAP ENTRY: 68, 56560, 43, 125, 6257 MAP: 192, 0, 7, 33, 5 VM OBJECT: 132, 0, 4285, 94, 17032 128 Bucket: 524, 0, 63, 0, 0 64 Bucket: 268, 0, 37, 5, 0 32 Bucket: 140, 0, 21, 7, 0 16 Bucket: 76, 0, 33, 17, 0 UMA Hash: 128, 0, 3, 27, 0 UMA RCntSlab: 104, 0, 195, 27, 0 UMA Slabs: 64, 0, 798, 28, 0 UMA Zones: 88, 0, 60, 20, 0 UMA Kegs: 136, 0, 60, 12, 0 vm.kvm_size: 1073737728 vm.kvm_free: 142602240 vfs.nfs4.access_cache_timeout: 60 vfs.nfs4.nfsv3_commit_on_close: 0 vfs.nfs.downdelayinitial: 12 vfs.nfs.downdelayinterval: 30 vfs.nfs.realign_test: 0 vfs.nfs.realign_count: 0 vfs.nfs.bufpackets: 4 vfs.nfs.reconnects: 0 vfs.nfs.iodmaxidle: 120 vfs.nfs.iodmin: 4 vfs.nfs.iodmax: 20 vfs.nfs.defect: 0 vfs.nfs.nfs_ip_paranoia: 1 vfs.nfs.diskless_valid: 0 vfs.nfs.diskless_rootpath: vfs.nfs.access_cache_timeout: 60 vfs.nfs.nfsv3_commit_on_close: 0 vfs.devfs.noverflow: 32768 vfs.devfs.generation: 98 vfs.devfs.inodes: 98 vfs.devfs.topinode: 101 vfs.ufs.dirhash_minsize: 2560 vfs.ufs.dirhash_maxmem: 2097152 vfs.ufs.dirhash_mem: 288995 vfs.ufs.dirhash_docheck: 0 vfs.pfs.vncache.entries: 0 vfs.pfs.vncache.maxentries: 0 vfs.pfs.vncache.hits: 0 vfs.pfs.vncache.misses: 0 vfs.vmiodirenable: 1 vfs.runningbufspace: 0 vfs.bufspace: 82051072 vfs.maxbufspace: 117293056 vfs.bufmallocspace: 1388544 vfs.maxmallocbufspace: 5831884 vfs.lobufspace: 116572160 vfs.hibufspace: 116637696 vfs.bufreusecnt: 5008 vfs.buffreekvacnt: 0 vfs.bufdefragcnt: 0 vfs.lorunningspace: 524288 vfs.hirunningspace: 1048576 vfs.dirtybufferflushes: 0 vfs.altbufferflushes: 0 vfs.recursiveflushes: 0 vfs.numdirtybuffers: 7 vfs.lodirtybuffers: 904 vfs.hidirtybuffers: 1809 vfs.dirtybufthresh: 1628 vfs.numfreebuffers: 7152 vfs.lofreebuffers: 402 vfs.hifreebuffers: 804 vfs.getnewbufcalls: 5120 vfs.getnewbufrestarts: 0 vfs.flushwithdeps: 0 vfs.cache.numneg: 199 vfs.cache.numcache: 3208 vfs.cache.numcalls: 287370 vfs.cache.dothits: 2817 vfs.cache.dotdothits: 164 vfs.cache.numchecks: 295318 vfs.cache.nummiss: 8485 vfs.cache.nummisszap: 88 vfs.cache.numposzaps: 150 vfs.cache.numposhits: 248322 vfs.cache.numnegzaps: 33 vfs.cache.numneghits: 27311 vfs.cache.nchstats: 248322 27311 183 0 8573 0 228 423 vfs.cache.numcwdcalls: 86 vfs.cache.numcwdfail1: 0 vfs.cache.numcwdfail2: 0 vfs.cache.numcwdfail3: 0 vfs.cache.numcwdfail4: 0 vfs.cache.numcwdfound: 86 vfs.cache.numfullpathcalls: 0 vfs.cache.numfullpathfail1: 0 vfs.cache.numfullpathfail2: 0 vfs.cache.numfullpathfail3: 0 vfs.cache.numfullpathfail4: 0 vfs.cache.numfullpathfound: 0 vfs.write_behind: 1 vfs.read_max: 8 vfs.opv_numops: 64 vfs.usermount: 0 vfs.numvnodes: 3203 vfs.wantfreevnodes: 25 vfs.freevnodes: 848 vfs.reassignbufcalls: 2696 vfs.nameileafonly: 0 vfs.timestamp_precision: 0 vfs.worklist_len: 2 vfs.nfsrv.nfs_privport: 0 vfs.nfsrv.async: 0 vfs.nfsrv.commit_blks: 0 vfs.nfsrv.commit_miss: 0 vfs.nfsrv.realign_test: 0 vfs.nfsrv.realign_count: 0 vfs.nfsrv.gatherdelay: 10000 vfs.nfsrv.gatherdelay_v3: 0 vfs.ffs.doasyncfree: 1 vfs.ffs.doreallocblks: 1 net.local.stream.sendspace: 8192 net.local.stream.recvspace: 8192 net.local.dgram.maxdgram: 2048 net.local.dgram.recvspace: 4096 net.local.inflight: 0 net.inet.ip.portrange.lowfirst: 1023 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.first: 49152 net.inet.ip.portrange.last: 65535 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.hilast: 65535 net.inet.ip.portrange.reservedhigh: 1023 net.inet.ip.portrange.reservedlow: 0 net.inet.ip.portrange.randomized: 1 net.inet.ip.forwarding: 0 net.inet.ip.redirect: 1 net.inet.ip.ttl: 64 net.inet.ip.rtexpire: 3600 net.inet.ip.rtminexpire: 10 net.inet.ip.rtmaxcache: 128 net.inet.ip.sourceroute: 0 net.inet.ip.intr_queue_maxlen: 50 net.inet.ip.intr_queue_drops: 0 net.inet.ip.accept_sourceroute: 0 net.inet.ip.keepfaith: 0 net.inet.ip.gifttl: 30 net.inet.ip.subnets_are_local: 0 net.inet.ip.fastforwarding: 0 net.inet.ip.process_options: 1 net.inet.ip.maxfragpackets: 800 net.inet.ip.maxfragsperpacket: 16 net.inet.ip.sendsourcequench: 0 net.inet.ip.random_id: 0 net.inet.ip.check_interface: 0 net.inet.icmp.maskrepl: 0 net.inet.icmp.icmplim: 200 net.inet.icmp.maskfake: 0 net.inet.icmp.drop_redirect: 0 net.inet.icmp.log_redirect: 0 net.inet.icmp.icmplim_output: 1 net.inet.icmp.reply_src: net.inet.icmp.bmcastecho: 0 net.inet.tcp.rfc1323: 1 net.inet.tcp.rfc1644: 0 net.inet.tcp.mssdflt: 512 net.inet.tcp.keepidle: 7200000 net.inet.tcp.keepintvl: 75000 net.inet.tcp.sendspace: 32768 net.inet.tcp.recvspace: 65536 net.inet.tcp.keepinit: 75000 net.inet.tcp.delacktime: 100 net.inet.tcp.v6mssdflt: 1024 net.inet.tcp.hostcache.cachelimit: 15360 net.inet.tcp.hostcache.hashsize: 512 net.inet.tcp.hostcache.bucketlimit: 30 net.inet.tcp.hostcache.count: 2 net.inet.tcp.hostcache.expire: 3600 net.inet.tcp.hostcache.purge: 0 net.inet.tcp.log_in_vain: 0 net.inet.tcp.blackhole: 0 net.inet.tcp.delayed_ack: 1 net.inet.tcp.rfc3042: 1 net.inet.tcp.rfc3390: 1 net.inet.tcp.reass.maxsegments: 1600 net.inet.tcp.reass.cursegments: 0 net.inet.tcp.reass.maxqlen: 48 net.inet.tcp.reass.overflows: 0 net.inet.tcp.path_mtu_discovery: 1 net.inet.tcp.slowstart_flightsize: 1 net.inet.tcp.local_slowstart_flightsize: 4 net.inet.tcp.newreno: 1 net.inet.tcp.minmss: 216 net.inet.tcp.minmssoverload: 0 net.inet.tcp.tcbhashsize: 512 net.inet.tcp.do_tcpdrain: 1 net.inet.tcp.pcbcount: 7 net.inet.tcp.icmp_may_rst: 1 net.inet.tcp.isn_reseed_interval: 0 net.inet.tcp.inflight.enable: 1 net.inet.tcp.inflight.debug: 0 net.inet.tcp.inflight.min: 6144 net.inet.tcp.inflight.max: 1073725440 net.inet.tcp.inflight.stab: 20 net.inet.tcp.sack.enable: 1 net.inet.tcp.syncookies: 1 net.inet.tcp.syncache.bucketlimit: 30 net.inet.tcp.syncache.cachelimit: 15359 net.inet.tcp.syncache.count: 0 net.inet.tcp.syncache.hashsize: 512 net.inet.tcp.syncache.rexmtlimit: 3 net.inet.tcp.msl: 30000 net.inet.tcp.rexmit_min: 30 net.inet.tcp.rexmit_slop: 200 net.inet.tcp.always_keepalive: 1 net.inet.udp.checksum: 1 net.inet.udp.maxdgram: 9216 net.inet.udp.recvspace: 42080 net.inet.udp.log_in_vain: 0 net.inet.udp.blackhole: 0 net.inet.udp.strict_mcast_mship: 0 net.inet.raw.maxdgram: 8192 net.inet.raw.recvspace: 8192 net.inet.accf.unloadable: 0 net.link.generic.system.ifcount: 3 net.link.ether.inet.prune_intvl: 300 net.link.ether.inet.max_age: 1200 net.link.ether.inet.host_down_time: 20 net.link.ether.inet.maxtries: 5 net.link.ether.inet.useloopback: 1 net.link.ether.inet.proxyall: 0 net.link.ether.inet.log_arp_wrong_iface: 1 net.link.ether.inet.log_arp_movements: 1 net.link.ether.ipfw: 0 net.link.gif.max_nesting: 1 net.link.gif.parallel_tunnels: 0 net.inet6.ip6.forwarding: 0 net.inet6.ip6.redirect: 1 net.inet6.ip6.hlim: 64 net.inet6.ip6.maxfragpackets: 6400 net.inet6.ip6.accept_rtadv: 1 net.inet6.ip6.keepfaith: 0 net.inet6.ip6.log_interval: 5 net.inet6.ip6.hdrnestlimit: 50 net.inet6.ip6.dad_count: 1 net.inet6.ip6.auto_flowlabel: 1 net.inet6.ip6.defmcasthlim: 1 net.inet6.ip6.gifhlim: 30 net.inet6.ip6.kame_version: 20010528/FreeBSD net.inet6.ip6.use_deprecated: 1 net.inet6.ip6.rr_prune: 5 net.inet6.ip6.v6only: 1 net.inet6.ip6.rtexpire: 3600 net.inet6.ip6.rtminexpire: 10 net.inet6.ip6.rtmaxcache: 128 net.inet6.ip6.use_tempaddr: 0 net.inet6.ip6.temppltime: 86400 net.inet6.ip6.tempvltime: 604800 net.inet6.ip6.auto_linklocal: 1 net.inet6.ip6.prefer_tempaddr: 0 net.inet6.ip6.maxfrags: 6400 net.inet6.icmp6.rediraccept: 1 net.inet6.icmp6.redirtimeout: 600 net.inet6.icmp6.nd6_prune: 1 net.inet6.icmp6.nd6_delay: 5 net.inet6.icmp6.nd6_umaxtries: 3 net.inet6.icmp6.nd6_mmaxtries: 3 net.inet6.icmp6.nd6_useloopback: 1 net.inet6.icmp6.nodeinfo: 3 net.inet6.icmp6.errppslimit: 100 net.inet6.icmp6.nd6_maxnudhint: 0 net.inet6.icmp6.nd6_debug: 0 net.isr.enable: 0 net.isr.count: 2436 net.isr.directed: 0 net.isr.deferred: 2436 net.isr.queued: 91 net.isr.drop: 0 net.isr.swi_count: 2463 net.route.netisr_maxqlen: 256 debug.firewire_debug: 0 debug.fwmem_debug: 0 debug.if_fwe_debug: 0 debug.sbp_debug: 0 debug.mddebug: 0 debug.doslowdown: 0 debug.elf32_trace: 0 debug.elf32_legacy_coredump: 0 debug.boothowto: -2147483648 debug.bootverbose: 0 debug.free_devt: 0 debug.sizeof.g_class: 68 debug.sizeof.g_geom: 68 debug.sizeof.g_provider: 88 debug.sizeof.g_consumer: 60 debug.sizeof.g_bioq: 48 debug.sizeof.vnode: 264 debug.sizeof.proc: 452 debug.sizeof.cdev: 232 debug.sizeof.bio: 132 debug.sizeof.buf: 436 debug.sizeof.kinfo_proc: 648 debug.sizeof.devstat: 240 debug.to_avg_depth: 3276 debug.to_avg_gcalls: 487 debug.to_avg_mpcalls: 2763 debug.kdb.available: _TMP debug.kdb.current: debug.kdb.enter: 0 debug.rman_debug: 0 debug.ttydebug: 0 debug.dobkgrdwrite: 1 debug.nchash: 131071 debug.ncnegfactor: 16 debug.numneg: 199 debug.numcache: 3208 debug.numcachehv: 733 debug.vfscache: 1 debug.vnsize: 264 debug.ncsize: 36 debug.hashstat.nchash: 131072 3170 2 241 debug.hashstat.nfsnode: 65536 0 0 0 debug.disablecwd: 0 debug.disablefullpath: 0 debug.rush_requests: 0 debug.vnlru_nowhere: 0 debug.bpf_bufsize: 4096 debug.bpf_maxbufsize: 524288 debug.if_tun_debug: 0 debug.mpsafenet: 1 debug.ieee80211: 0 debug.dopersistence: 0 debug.snapdebug: 0 debug.collectsnapstats: 0 debug.max_softdeps: 279800 debug.tickdelay: 2 debug.maxindirdeps: 50 debug.worklist_push: 0 debug.blk_limit_push: 0 debug.ino_limit_push: 0 debug.blk_limit_hit: 0 debug.ino_limit_hit: 0 debug.sync_limit_hit: 0 debug.indir_blk_ptrs: 0 debug.inode_bitmap: 0 debug.direct_blk_ptrs: 0 debug.dir_entry: 0 debug.bigcgs: 0 debug.dircheck: 0 debug.mpsafevm: 0 debug.nosleepwithlocks: 0 debug.fdc.fifo: 8 debug.fdc.debugflags: 0 debug.fdc.retries: 10 debug.fdc.spec1: 175 debug.fdc.spec2: 16 debug.fdc.settle: 12 debug.PMAP1changed: 2119 debug.PMAP1unchanged: 303230 debug.psmhz: 20 debug.psm_soft_timeout: 500000 debug.psmerrsecs: 2 debug.psmerrusecs: 0 debug.psmsecs: 0 debug.psmusecs: 500000 debug.psmpkterrthresh: 2 debug.psmloglevel: 0 debug.acpi.acpi_ca_version: 0x20040527 debug.acpi.semaphore_debug: 0 hw.machine: i386 hw.model: Intel(R) Pentium(R) M processor 1700MHz hw.ncpu: 1 hw.byteorder: 1234 hw.physmem: 1064140800 hw.usermem: 981778432 hw.pagesize: 4096 hw.floatingpoint: 1 hw.machine_arch: i386 hw.aac.iosize_max: 65536 hw.an.an_dump: off hw.an.an_cache_mode: dbm hw.an.an_cache_mcastonly: 0 hw.an.an_cache_iponly: 1 hw.ata.ata_dma: 1 hw.ata.wc: 1 hw.ata.atapi_dma: 1 hw.cardbus.debug: 0 hw.cardbus.cis_debug: 0 hw.cs.debug: 0 hw.cs.ignore_checksum_failure: 0 hw.cs.recv_delay: 570 hw.firewire.try_bmr: 1 hw.firewire.hold_count: 3 hw.firewire.fwmem.eui64_hi: 0 hw.firewire.fwmem.eui64_lo: 0 hw.firewire.fwmem.speed: 2 hw.firewire.fwe.stream_ch: 1 hw.firewire.fwe.tx_speed: 2 hw.firewire.fwe.rx_queue_len: 128 hw.firewire.sbp.auto_login: 1 hw.firewire.sbp.max_speed: -1 hw.firewire.sbp.exclusive_login: 1 hw.firewire.sbp.login_delay: 1000 hw.firewire.sbp.scan_delay: 500 hw.firewire.sbp.use_doorbell: 0 hw.firewire.sbp.tags: 0 hw.pccard.debug: 0 hw.pccard.cis_debug: 0 hw.cbb.start_memory: 2281701376 hw.cbb.start_16_io: 256 hw.cbb.start_32_io: 4096 hw.cbb.debug: 0 hw.pcic.intr_mask: 57016 hw.pci.enable_io_modes: 1 hw.pci.do_powerstate: 0 hw.pci.host_mem_start: -2147483648 hw.pci.irq_override_mask: 57080 hw.wi.txerate: 0 hw.wi.debug: 0 hw.xe.debug: 0 hw.intr_storm_threshold: 500 hw.availpages: 259800 hw.bus.devctl_disable: 0 hw.dc_quick: 1 hw.ste.rxsyncs: 0 hw.kbd.keymap_restrict_change: 0 hw.syscons.saver.keybonly: 1 hw.syscons.bell: 1 hw.syscons.sc_no_suspend_vtswitch: 0 hw.busdma.free_bpages: 512 hw.busdma.reserved_bpages: 0 hw.busdma.active_bpages: 0 hw.busdma.total_bpages: 512 hw.busdma.total_bounced: 0 hw.busdma.total_deferred: 0 hw.clockrate: 1698 hw.instruction_sse: 1 hw.snd.targetirqrate: 32 hw.snd.report_soft_formats: 1 hw.snd.verbose: 1 hw.snd.unit: 0 hw.snd.maxautovchans: 0 hw.snd.pcm0.buffersize: 16384 hw.snd.pcm0.vchans: 0 hw.snd.pcm0.ac97rate: 48000 hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S3 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 hw.acpi.reset_video: 1 hw.acpi.cpu.throttle_max: 8 hw.acpi.cpu.throttle_state: 8 hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/85 hw.acpi.cpu.cx_lowest: C3 hw.acpi.cpu.cx_usage: 0.00% 100.00% 0.00% hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.tz0.temperature: 3312 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3647 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3672 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 100 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 hw.em0.debug_info: -1 hw.em0.stats: -1 hw.em0.rx_int_delay: 0 hw.em0.tx_int_delay: 66 hw.em0.rx_abs_int_delay: 66 hw.em0.tx_abs_int_delay: 66 machdep.adjkerntz: 0 machdep.disable_rtc_set: 0 machdep.wall_cmos_clock: 0 machdep.conrclk: 1843200 machdep.gdbspeed: 9600 machdep.conspeed: 9600 machdep.enable_panic_key: 0 machdep.disable_mtrrs: 0 machdep.cpu_idle_hlt: 1 machdep.guessed_bootdev: 2687500288 machdep.panic_on_nmi: 1 machdep.tsc_freq: 1698564926 machdep.i8254_freq: 1193182 machdep.acpi_timer_freq: 3579545 machdep.acpi_root: 1011184 user.cs_path: /usr/bin:/bin:/usr/sbin:/sbin: user.bc_base_max: 99 user.bc_dim_max: 2048 user.bc_scale_max: 99 user.bc_string_max: 1000 user.coll_weights_max: 0 user.expr_nest_max: 32 user.line_max: 2048 user.re_dup_max: 255 user.posix2_version: 199212 user.posix2_c_bind: 0 user.posix2_c_dev: 0 user.posix2_char_term: 0 user.posix2_fort_dev: 0 user.posix2_fort_run: 0 user.posix2_localedef: 0 user.posix2_sw_dev: 0 user.posix2_upe: 0 user.stream_max: 20 user.tzname_max: 255 p1003_1b.asynchronous_io: 0 p1003_1b.mapped_files: 1 p1003_1b.memlock: 0 p1003_1b.memlock_range: 0 p1003_1b.memory_protection: 0 p1003_1b.message_passing: 0 p1003_1b.prioritized_io: 0 p1003_1b.priority_scheduling: 1 p1003_1b.realtime_signals: 0 p1003_1b.semaphores: 0 p1003_1b.fsync: 0 p1003_1b.shared_memory_objects: 1 p1003_1b.synchronized_io: 0 p1003_1b.timers: 0 p1003_1b.aio_listio_max: -1 p1003_1b.aio_max: -1 p1003_1b.aio_prio_delta_max: -1 p1003_1b.delaytimer_max: 0 p1003_1b.mq_open_max: 0 p1003_1b.pagesize: 4096 p1003_1b.rtsig_max: 0 p1003_1b.sem_nsems_max: 0 p1003_1b.sem_value_max: 0 p1003_1b.sigqueue_max: 0 p1003_1b.timer_max: 0 compat.linux.osname: Linux compat.linux.osrelease: 2.4.2 compat.linux.oss_version: 198144 security.jail.set_hostname_allowed: 1 security.jail.socket_unixiproute_only: 1 security.jail.sysvipc_allowed: 0 security.jail.getfsstatroot_only: 1 security.jail.allow_raw_sockets: 0 security.jail.jailed: 0 security.bsd.suser_enabled: 1 security.bsd.see_other_uids: 1 security.bsd.see_other_gids: 1 security.bsd.conservative_signals: 1 security.bsd.unprivileged_proc_debug: 1 security.bsd.unprivileged_read_msgbuf: 1 security.bsd.hardlink_check_uid: 0 security.bsd.hardlink_check_gid: 0 security.bsd.unprivileged_get_quota: 0 dev.nexus.0.%driver: nexus dev.nexus.0.%parent: root0 dev.npx.0.%desc: math processor dev.npx.0.%driver: npx dev.npx.0.%parent: nexus0 dev.acpi.0.%desc: IBM TP-1R dev.acpi.0.%driver: acpi dev.acpi.0.%parent: nexus0 dev.acpi_ec.0.%desc: Embedded Controller: GPE 0x1c, ECDT dev.acpi_ec.0.%driver: acpi_ec dev.acpi_ec.0.%location: handle=\_SB_.PCI0.LPC_.EC__ dev.acpi_ec.0.%pnpinfo: _HID=PNP0C09 _UID=0 dev.acpi_ec.0.%parent: acpi0 dev.acpi_sysresource.0.%desc: System Resource dev.acpi_sysresource.0.%driver: acpi_sysresource dev.acpi_sysresource.0.%location: handle=\_SB_.MEM_ dev.acpi_sysresource.0.%pnpinfo: _HID=PNP0C01 _UID=0 dev.acpi_sysresource.0.%parent: acpi0 dev.acpi_sysresource.1.%desc: System Resource dev.acpi_sysresource.1.%driver: acpi_sysresource dev.acpi_sysresource.1.%location: handle=\_SB_.PCI0.LPC_.SIO_ dev.acpi_sysresource.1.%pnpinfo: _HID=PNP0C02 _UID=0 dev.acpi_sysresource.1.%parent: acpi0 dev.acpi_timer.0.%desc: 24-bit timer at 3.579545MHz dev.acpi_timer.0.%driver: acpi_timer dev.acpi_timer.0.%location: unknown dev.acpi_timer.0.%pnpinfo: unknown dev.acpi_timer.0.%parent: acpi0 dev.cpu.0.%desc: ACPI CPU (3 Cx states) dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU_ dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.acpi_tz.0.%desc: Thermal Zone dev.acpi_tz.0.%driver: acpi_tz dev.acpi_tz.0.%location: handle=\_TZ_.THM0 dev.acpi_tz.0.%pnpinfo: _HID=none _UID=0 dev.acpi_tz.0.%parent: acpi0 dev.acpi_lid.0.%desc: Control Method Lid Switch dev.acpi_lid.0.%driver: acpi_lid dev.acpi_lid.0.%location: handle=\_SB_.LID_ dev.acpi_lid.0.%pnpinfo: _HID=PNP0C0D _UID=0 dev.acpi_lid.0.%parent: acpi0 dev.acpi_lid.0.wake: 1 dev.acpi_button.0.%desc: Sleep Button dev.acpi_button.0.%driver: acpi_button dev.acpi_button.0.%location: handle=\_SB_.SLPB dev.acpi_button.0.%pnpinfo: _HID=PNP0C0E _UID=0 dev.acpi_button.0.%parent: acpi0 dev.acpi_button.0.wake: 1 dev.pcib.0.%desc: ACPI Host-PCI bridge dev.pcib.0.%driver: pcib dev.pcib.0.%location: handle=\_SB_.PCI0 dev.pcib.0.%pnpinfo: _HID=PNP0A03 _UID=0 dev.pcib.0.%parent: acpi0 dev.pcib.0.wake: 0 dev.pcib.1.%desc: ACPI PCI-PCI bridge dev.pcib.1.%driver: pcib dev.pcib.1.%location: slot=1 function=0 handle=\_SB_.PCI0.AGP_ dev.pcib.1.%pnpinfo: vendor=0x8086 device=0x3341 subvendor=0x0000 subdevice=0x0000 class=0x060400 dev.pcib.1.%parent: pci0 dev.pcib.2.%desc: ACPI PCI-PCI bridge dev.pcib.2.%driver: pcib dev.pcib.2.%location: slot=30 function=0 handle=\_SB_.PCI0.PCI1 dev.pcib.2.%pnpinfo: vendor=0x8086 device=0x2448 subvendor=0x0000 subdevice=0x0000 class=0x060400 dev.pcib.2.%parent: pci0 dev.pcib.2.wake: 0 dev.pci.0.%desc: ACPI PCI bus dev.pci.0.%driver: pci dev.pci.0.%parent: pcib0 dev.pci.0.wake: 0 dev.pci.1.%desc: ACPI PCI bus dev.pci.1.%driver: pci dev.pci.1.%parent: pcib1 dev.pci.2.%desc: ACPI PCI bus dev.pci.2.%driver: pci dev.pci.2.%parent: pcib2 dev.pci.2.wake: 0 dev.agp.0.%desc: Intel 82855 host to AGP bridge dev.agp.0.%driver: agp dev.agp.0.%location: slot=0 function=0 dev.agp.0.%pnpinfo: vendor=0x8086 device=0x3340 subvendor=0x1014 subdevice=0x0529 class=0x060000 dev.agp.0.%parent: pci0 dev.uhci.0.%desc: Intel 82801DB (ICH4) USB controller USB-A dev.uhci.0.%driver: uhci dev.uhci.0.%location: slot=29 function=0 handle=\_SB_.PCI0.USB0 dev.uhci.0.%pnpinfo: vendor=0x8086 device=0x24c2 subvendor=0x1014 subdevice=0x052d class=0x0c0300 dev.uhci.0.%parent: pci0 dev.uhci.0.wake: 0 dev.uhci.1.%desc: Intel 82801DB (ICH4) USB controller USB-B dev.uhci.1.%driver: uhci dev.uhci.1.%location: slot=29 function=1 handle=\_SB_.PCI0.USB1 dev.uhci.1.%pnpinfo: vendor=0x8086 device=0x24c4 subvendor=0x1014 subdevice=0x052d class=0x0c0300 dev.uhci.1.%parent: pci0 dev.uhci.1.wake: 0 dev.uhci.2.%desc: Intel 82801DB (ICH4) USB controller USB-C dev.uhci.2.%driver: uhci dev.uhci.2.%location: slot=29 function=2 handle=\_SB_.PCI0.USB2 dev.uhci.2.%pnpinfo: vendor=0x8086 device=0x24c7 subvendor=0x1014 subdevice=0x052d class=0x0c0300 dev.uhci.2.%parent: pci0 dev.usb.0.%desc: Intel 82801DB (ICH4) USB controller USB-A dev.usb.0.%driver: usb dev.usb.0.%parent: uhci0 dev.usb.1.%desc: Intel 82801DB (ICH4) USB controller USB-B dev.usb.1.%driver: usb dev.usb.1.%parent: uhci1 dev.usb.2.%desc: Intel 82801DB (ICH4) USB controller USB-C dev.usb.2.%driver: usb dev.usb.2.%parent: uhci2 dev.uhub.0.%desc: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 dev.uhub.0.%driver: uhub dev.uhub.0.%parent: usb0 dev.uhub.1.%desc: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 dev.uhub.1.%driver: uhub dev.uhub.1.%parent: usb1 dev.uhub.2.%desc: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 dev.uhub.2.%driver: uhub dev.uhub.2.%parent: usb2 dev.cbb.0.%desc: PCI-CardBus Bridge dev.cbb.0.%driver: cbb dev.cbb.0.%location: slot=0 function=0 handle=\_SB_.PCI0.PCI1.CBS0 dev.cbb.0.%pnpinfo: vendor=0x104c device=0xac46 subvendor=0x1014 subdevice=0x0552 class=0x060700 dev.cbb.0.%parent: pci2 dev.cbb.1.%desc: PCI-CardBus Bridge dev.cbb.1.%driver: cbb dev.cbb.1.%location: slot=0 function=1 handle=\_SB_.PCI0.PCI1.CBS1 dev.cbb.1.%pnpinfo: vendor=0x104c device=0xac46 subvendor=0x1014 subdevice=0x0552 class=0x060700 dev.cbb.1.%parent: pci2 dev.cardbus.%parent: pci dev.cardbus.0.%desc: CardBus bus dev.cardbus.0.%driver: cardbus dev.cardbus.0.%parent: cbb0 dev.cardbus.1.%desc: CardBus bus dev.cardbus.1.%driver: cardbus dev.cardbus.1.%parent: cbb1 dev.pccard.0.%desc: 16-bit PCCard bus dev.pccard.0.%driver: pccard dev.pccard.0.%parent: cbb0 dev.pccard.1.%desc: 16-bit PCCard bus dev.pccard.1.%driver: pccard dev.pccard.1.%parent: cbb1 dev.em.0.%desc: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 dev.em.0.%driver: em dev.em.0.%location: slot=1 function=0 dev.em.0.%pnpinfo: vendor=0x8086 device=0x101e subvendor=0x1014 subdevice=0x0549 class=0x020000 dev.em.0.%parent: pci2 dev.isab.0.%desc: PCI-ISA bridge dev.isab.0.%driver: isab dev.isab.0.%location: slot=31 function=0 handle=\_SB_.PCI0.LPC_ dev.isab.0.%pnpinfo: vendor=0x8086 device=0x24cc subvendor=0x0000 subdevice=0x0000 class=0x060100 dev.isab.0.%parent: pci0 dev.isa.0.%desc: ISA bus dev.isa.0.%driver: isa dev.isa.0.%parent: isab0 dev.atapci.0.%desc: Intel ICH4 UDMA100 controller dev.atapci.0.%driver: atapci dev.atapci.0.%location: slot=31 function=1 handle=\_SB_.PCI0.IDE0 dev.atapci.0.%pnpinfo: vendor=0x8086 device=0x24ca subvendor=0x1014 subdevice=0x052d class=0x01018a dev.atapci.0.%parent: pci0 dev.ata.0.%driver: ata dev.ata.0.%parent: atapci0 dev.ata.1.%driver: ata dev.ata.1.%parent: atapci0 dev.pcm.0.%desc: Intel ICH4 (82801DB) dev.pcm.0.%driver: pcm dev.pcm.0.%location: slot=31 function=5 dev.pcm.0.%pnpinfo: vendor=0x8086 device=0x24c5 subvendor=0x1014 subdevice=0x0554 class=0x040100 dev.pcm.0.%parent: pci0 dev.atpic.0.%desc: AT interrupt controller dev.atpic.0.%driver: atpic dev.atpic.0.%location: handle=\_SB_.PCI0.LPC_.PIC_ dev.atpic.0.%pnpinfo: _HID=PNP0000 _UID=0 dev.atpic.0.%parent: acpi0 dev.attimer.0.%desc: AT timer dev.attimer.0.%driver: attimer dev.attimer.0.%location: handle=\_SB_.PCI0.LPC_.TIMR dev.attimer.0.%pnpinfo: _HID=PNP0100 _UID=0 dev.attimer.0.%parent: acpi0 dev.attimer.1.%desc: AT realtime clock dev.attimer.1.%driver: attimer dev.attimer.1.%location: handle=\_SB_.PCI0.LPC_.RTC_ dev.attimer.1.%pnpinfo: _HID=PNP0B00 _UID=0 dev.attimer.1.%parent: acpi0 dev.atdma.0.%desc: AT DMA controller dev.atdma.0.%driver: atdma dev.atdma.0.%location: handle=\_SB_.PCI0.LPC_.DMAC dev.atdma.0.%pnpinfo: _HID=PNP0200 _UID=0 dev.atdma.0.%parent: acpi0 dev.npxisa.0.%desc: Legacy ISA coprocessor support dev.npxisa.0.%driver: npxisa dev.npxisa.0.%location: handle=\_SB_.PCI0.LPC_.FPU_ dev.npxisa.0.%pnpinfo: _HID=PNP0C04 _UID=0 dev.npxisa.0.%parent: acpi0 dev.atkbdc.0.%desc: Keyboard controller (i8042) dev.atkbdc.0.%driver: atkbdc dev.atkbdc.0.%location: handle=\_SB_.PCI0.LPC_.KBD_ dev.atkbdc.0.%pnpinfo: _HID=PNP0303 _UID=0 dev.atkbdc.0.%parent: acpi0 dev.atkbd.0.%desc: AT Keyboard dev.atkbd.0.%driver: atkbd dev.atkbd.0.%parent: atkbdc0 dev.psmcpnp.0.%desc: PS/2 mouse port dev.psmcpnp.0.%driver: psmcpnp dev.psmcpnp.0.%location: handle=\_SB_.PCI0.LPC_.MOU_ dev.psmcpnp.0.%pnpinfo: _HID=IBM0057 _UID=0 dev.psmcpnp.0.%parent: acpi0 dev.psm.0.%desc: PS/2 Mouse dev.psm.0.%driver: psm dev.psm.0.%parent: atkbdc0 dev.fdc.0.%desc: Enhanced floppy controller dev.fdc.0.%driver: fdc dev.fdc.0.%location: handle=\_SB_.PCI0.LPC_.FDC_ dev.fdc.0.%pnpinfo: _HID=PNP0700 _UID=0 dev.fdc.0.%parent: acpi0 dev.sio.0.%desc: 16550A-compatible COM port dev.sio.0.%driver: sio dev.sio.0.%location: handle=\_SB_.PCI0.LPC_.UART dev.sio.0.%pnpinfo: _HID=PNP0501 _UID=0 dev.sio.0.%parent: acpi0 dev.sio.0.wake: 0 dev.sio.1.%desc: Generic IRDA-compatible device dev.sio.1.%driver: sio dev.sio.1.%location: handle=\_SB_.PCI0.LPC_.FIR_ dev.sio.1.%pnpinfo: _HID=IBM0071 _UID=0 dev.sio.1.%parent: acpi0 dev.ppc.0.%desc: Standard parallel printer port dev.ppc.0.%driver: ppc dev.ppc.0.%location: handle=\_SB_.PCI0.LPC_.LPT_ dev.ppc.0.%pnpinfo: _HID=PNP0400 _UID=0 dev.ppc.0.%parent: acpi0 dev.ppbus.0.%desc: Parallel port bus dev.ppbus.0.%driver: ppbus dev.ppbus.0.%parent: ppc0 dev.plip.0.%desc: PLIP network interface dev.plip.0.%driver: plip dev.plip.0.%parent: ppbus0 dev.lpt.0.%desc: Printer dev.lpt.0.%driver: lpt dev.lpt.0.%parent: ppbus0 dev.ppi.0.%desc: Parallel I/O dev.ppi.0.%driver: ppi dev.ppi.0.%parent: ppbus0 dev.acpi_cmbat.0.%desc: Control Method Battery dev.acpi_cmbat.0.%driver: acpi_cmbat dev.acpi_cmbat.0.%location: handle=\_SB_.PCI0.LPC_.EC__.BAT0 dev.acpi_cmbat.0.%pnpinfo: _HID=PNP0C0A _UID=0 dev.acpi_cmbat.0.%parent: acpi0 dev.acpi_acad.0.%desc: AC Adapter dev.acpi_acad.0.%driver: acpi_acad dev.acpi_acad.0.%location: handle=\_SB_.PCI0.LPC_.EC__.AC__ dev.acpi_acad.0.%pnpinfo: _HID=ACPI0003 _UID=0 dev.acpi_acad.0.%parent: acpi0 dev.orm.0.%desc: ISA Option ROMs dev.orm.0.%driver: orm dev.orm.0.%parent: isa0 dev.pmtimer.0.%driver: pmtimer dev.pmtimer.0.%parent: isa0 dev.sc.0.%desc: System console dev.sc.0.%driver: sc dev.sc.0.%parent: isa0 dev.vga.0.%desc: Generic ISA VGA dev.vga.0.%driver: vga dev.vga.0.%parent: isa0 hptmv.status: RocketRAID 182x SATA Controller driver Version 1.1 --------------030702040700060105090902-- From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 17:39:42 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3EFE16A4CE for ; Wed, 2 Mar 2005 17:39:42 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3920543D2D for ; Wed, 2 Mar 2005 17:39:42 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so232110wra for ; Wed, 02 Mar 2005 09:39:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=lWJ5reja0l0XoURsoc74IwEkuBVDFrIA8o/gkfqoFgUpZ87CJcyLzVjul2P2xpkToCkwmkWuW5pB6LbjngAThbvb1/GgpfggNRDBcpqGPG+quTqWS8mrTcv0yhFldLrkduGe21d3dIBeFg5ctP71Uf/R27QWOp1qEaop4Da992U= Received: by 10.54.37.52 with SMTP id k52mr21170wrk; Wed, 02 Mar 2005 09:39:11 -0800 (PST) Received: by 10.54.40.69 with HTTP; Wed, 2 Mar 2005 09:39:10 -0800 (PST) Message-ID: <2fd864e05030209393c89d94f@mail.gmail.com> Date: Wed, 2 Mar 2005 17:39:10 +0000 From: Astrodog To: Saber Zrelli In-Reply-To: <422636D3.6030403@jaist.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <422636D3.6030403@jaist.ac.jp> cc: freebsd-mobile@freebsd.org Subject: Re: system temperature too high, shutting down soon! X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 17:39:42 -0000 On Wed, 02 Mar 2005 21:57:39 +0000, Saber Zrelli wrote: > Hi all , > > I'm runnig FreeBSD 5.3-RELEASE #0 on an IBM Thinkpad R50p , > when I run some make install in the ports distribution. > > I got the following message : > tornado root: WARNING: system temperature too high, shutting down soon! > > After 2-3 secs the system shuts down. > > when I looked in /var/log/messages after booting , I found : > Mar 2 21:24:18 tornado kernel: cpu0: Performance states changed > Mar 2 21:24:39 tornado kernel: cpu0: Performance states changed > Mar 2 21:24:39 tornado root: WARNING: system temperature too high, > shutting down soon! > > I was using 5.3 CURRENT ( and previous releases ) a while before , and I > did not have this problem. > > my first thoughts is that it is a ACIP problem. but I dont have > knowledge about ACPI stuff. > > I think that some parameters in hw.acpi.thermal are not correct. > > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.tz0.temperature: 3312 > hw.acpi.thermal.tz0.active: -1 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: 3647 > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 3672 > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > > specially hw.acpi.thermal.tz0._ACx , there is no cooling level > temperatures defined. > Also , the hw.acpi.thermal.tz0._CRT: 3672 ,hw.acpi.thermal.tz0._PSV: > 3647 are too close , > the cpu don't have enough time to cool down before reaching the critical > temp. > > I tried debugging the ACPI module , so I compiled it with debuggin options . > but the kernel could not load it and I was running without acpi. > > I attached < sysctl -a > and < cat /lvar/og/messages > > > I want to keep using ACPI , and I really need to fix this. > > For any suggestions , > > Many thanks > > -- > Saber. Have you considered, that maybe its just running too hot? (Without ACPI, it has no way to make that determination) From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 19:18:12 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BEDA16A4CE for ; Wed, 2 Mar 2005 19:18:12 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id F131B43D39 for ; Wed, 2 Mar 2005 19:18:11 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Wed, 02 Mar 2005 11:18:11 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id B54675D07; Wed, 2 Mar 2005 11:18:09 -0800 (PST) To: vova@fbsd.ru In-reply-to: Your message of "Tue, 01 Mar 2005 23:31:15 +0300." <1109709075.1329.3.camel@localhost> Date: Wed, 02 Mar 2005 11:18:09 -0800 From: "Kevin Oberman" Message-Id: <20050302191809.B54675D07@ptavv.es.net> cc: Ian Dowse cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 19:18:12 -0000 > From: Vladimir Grebenschikov > Date: Tue, 01 Mar 2005 23:31:15 +0300 > Sender: owner-freebsd-mobile@freebsd.org > > ÷ ĐÎ, 28/02/2005 × 20:26 +0000, Ian Dowse ĐÉŰĹÔ: > >In message <200502281016.aa49779@salmon.maths.tcd.ie>, Ian Dowse writes: > >>In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschikov writes: > >>>Also if I try this patch with vesa module loaded it just carsh in vm86 > >>>mode on zzz (curproc acpiconf). > >> > >>It is probably necessary to get this working with VESA to have much > >>of a chance of it helping, since otherwise only the basic VGA > >>registers will be saved and restored. > >> > >>One possible reason for the vm86 crash is that it appears our VESA > >>code cannot handle saving more than 4k of state data. Does it make > >>any difference if you revert the part of the patch that changed > >>STATE_MOST to STATE_ALL? i.e. change the two uses of STATE_ALL in > >>vesa.c back to STATE_MOST. I found that with SAVE_MOST, I needed > >>to switch to X and back before the console would display, but the > >>backlight did come on immediately. > > > >I've updated the patch at > > > > http://people.freebsd.org/~iedowse/vesa_restore.diff > > > >so that the VESA code allows up to 8k of state storage and will > >fail if the BIOS claims to need more space. Could you try this with > >the vesa module loaded and with both 0 and 1 for hw.acpi.reset_video? > > I've rechecked patch with fresh kernel build and firewire console. > > It does not panics and does not awake :( > As in previous variant it sleeps ok, but on awake it only spin up HDD. > No any other activity seen, it does not react on keys, firewire console > is dead. > It does not answer on network activity. > > Probably It hangs while try to restore console, and I should try to > disable console at all ? Is the disk active LED on? Many systems have had trouble with this, although I thought Soren had fixed this. If the LED is on, you might want to try ATA MkIII. (That WILL break ATAPICAM!) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 19:32:51 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E72D916A4CE for ; Wed, 2 Mar 2005 19:32:51 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B32643D31 for ; Wed, 2 Mar 2005 19:32:51 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Wed, 02 Mar 2005 11:32:50 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id EFCA25D07; Wed, 2 Mar 2005 11:32:50 -0800 (PST) To: Saber Zrelli In-reply-to: Your message of "Wed, 02 Mar 2005 21:57:39 GMT." <422636D3.6030403@jaist.ac.jp> Date: Wed, 02 Mar 2005 11:32:50 -0800 From: "Kevin Oberman" Message-Id: <20050302193250.EFCA25D07@ptavv.es.net> cc: freebsd-mobile@freebsd.org Subject: Re: system temperature too high, shutting down soon! X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 19:32:52 -0000 > Date: Wed, 02 Mar 2005 21:57:39 +0000 > From: Saber Zrelli > Sender: owner-freebsd-mobile@freebsd.org > > This is a multi-part message in MIME format. > --------------030702040700060105090902 > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > Content-Transfer-Encoding: 7bit > > Hi all , > > I'm runnig FreeBSD 5.3-RELEASE #0 on an IBM Thinkpad R50p , > when I run some make install in the ports distribution. > > I got the following message : > tornado root: WARNING: system temperature too high, shutting down soon! > > After 2-3 secs the system shuts down. > > when I looked in /var/log/messages after booting , I found : > Mar 2 21:24:18 tornado kernel: cpu0: Performance states changed > Mar 2 21:24:39 tornado kernel: cpu0: Performance states changed > Mar 2 21:24:39 tornado root: WARNING: system temperature too high, > shutting down soon! > > I was using 5.3 CURRENT ( and previous releases ) a while before , and I > did not have this problem. > > my first thoughts is that it is a ACIP problem. but I dont have > knowledge about ACPI stuff. > > I think that some parameters in hw.acpi.thermal are not correct. > > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.tz0.temperature: 3312 > hw.acpi.thermal.tz0.active: -1 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: 3647 > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 3672 > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > > > specially hw.acpi.thermal.tz0._ACx , there is no cooling level > temperatures defined. > Also , the hw.acpi.thermal.tz0._CRT: 3672 ,hw.acpi.thermal.tz0._PSV: > 3647 are too close , > the cpu don't have enough time to cool down before reaching the critical > temp. > > I tried debugging the ACPI module , so I compiled it with debuggin options . > but the kernel could not load it and I was running without acpi. > > I attached < sysctl -a > and < cat /lvar/og/messages > > > I want to keep using ACPI , and I really need to fix this. > > For any suggestions , > You should really use 5-Stable. A huge number of ACPI fixes and extensions have gone in since 5.3 was released. That said, 5.4 is getting very close and will have these fixes if you want to wait. You are seeing the temperatures in raw form which is tenths of degrees Kelvin. In Current and 5-Stable these numbers are translated to degrees C. The temperatures you show are not near a shutdown, but the CPU temp can change VERY quickly. 3312 is really very cool. Is your system a P4-M? If so, are you using P4TCC? My experience with P4TCC was that it was not a good idea to play with it as it defaults to automatic. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 21:16:14 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2CD116A4CE for ; Wed, 2 Mar 2005 21:16:13 +0000 (GMT) Received: from omega.lacnic.net.uy (lacnic.net.uy [200.40.228.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1576C43D48 for ; Wed, 2 Mar 2005 21:16:13 +0000 (GMT) (envelope-from pablo@omega.lacnic.net.uy) Received: from omega.lacnic.net.uy (localhost.localdomain [127.0.0.1]) by omega.lacnic.net.uy (8.12.11/8.12.5) with ESMTP id j22MHbaQ005464 for ; Wed, 2 Mar 2005 19:17:37 -0300 Received: (from pablo@localhost) by omega.lacnic.net.uy (8.12.11/8.12.5/Submit) id j22MHaok005463 for freebsd-mobile@freebsd.org; Wed, 2 Mar 2005 19:17:36 -0300 Date: Wed, 2 Mar 2005 19:17:36 -0300 From: Pablo Allietti To: freebsd-mobile@freebsd.org Message-ID: <20050302221736.GA5378@omega.lacnic.net.uy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: Freebsd 5.3 X-Organization: LACNIC X-URL: http://lacnic.net/ X-Lacnic-MailScanner-Information: Please contact Lacnic for more information (lacnic at lacnic.net) X-Lacnic-MailScanner: Found to be clean X-MailScanner-From: pablo@omega.lacnic.net.uy Subject: ndiswrapper X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 21:16:14 -0000 hi all again. :) i have a problem to install ndiswrapper any body have a port for that? or any instruction to make this package? this is my error sony# make install "Makefile", line 1: Need an operator make: fatal errors encountered -- cannot continue sony# and the make file have this in the first line. i add to #!/usr/local/bin/bash but nothing happend. -include version ese es el error. alguna sugerencia? -- Pablo Allietti LACNIC -------------- From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 22:02:36 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABB4116A4CE for ; Wed, 2 Mar 2005 22:02:36 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DBB643D31 for ; Wed, 2 Mar 2005 22:02:36 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Wed, 02 Mar 2005 14:02:36 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id DB1E95D08; Wed, 2 Mar 2005 14:02:35 -0800 (PST) To: vova@fbsd.ru In-reply-to: Your message of "Thu, 03 Mar 2005 00:36:51 +0300." <1109799411.1629.4.camel@localhost> Date: Wed, 02 Mar 2005 14:02:35 -0800 From: "Kevin Oberman" Message-Id: <20050302220235.DB1E95D08@ptavv.es.net> cc: Ian Dowse cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 22:02:36 -0000 > From: Vladimir Grebenschikov > Date: Thu, 03 Mar 2005 00:36:51 +0300 > Sender: Vladimir Grebenschikov > > ÷ ÓŇ, 02/03/2005 × 11:18 -0800, Kevin Oberman ĐÉŰĹÔ: > >> From: Vladimir Grebenschikov > >> Date: Tue, 01 Mar 2005 23:31:15 +0300 > >> Sender: owner-freebsd-mobile@freebsd.org > >> > >> ÷ ĐÎ, 28/02/2005 × 20:26 +0000, Ian Dowse ĐÉŰĹÔ: > >> >In message <200502281016.aa49779@salmon.maths.tcd.ie>, Ian Dowse writes> : > >> >>In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschikov> writes: > >> >>>Also if I try this patch with vesa module loaded it just carsh in vm8> 6 > >> >>>mode on zzz (curproc acpiconf). > >> >> > >> >>It is probably necessary to get this working with VESA to have much > >> >>of a chance of it helping, since otherwise only the basic VGA > >> >>registers will be saved and restored. > >> >> > >> >>One possible reason for the vm86 crash is that it appears our VESA > >> >>code cannot handle saving more than 4k of state data. Does it make > >> >>any difference if you revert the part of the patch that changed > >> >>STATE_MOST to STATE_ALL? i.e. change the two uses of STATE_ALL in > >> >>vesa.c back to STATE_MOST. I found that with SAVE_MOST, I needed > >> >>to switch to X and back before the console would display, but the > >> >>backlight did come on immediately. > >> > > >> >I've updated the patch at > >> > > >> > http://people.freebsd.org/~iedowse/vesa_restore.diff > >> > > >> >so that the VESA code allows up to 8k of state storage and will > >> >fail if the BIOS claims to need more space. Could you try this with > >> >the vesa module loaded and with both 0 and 1 for hw.acpi.reset_video? > >> > >> I've rechecked patch with fresh kernel build and firewire console. > >> > >> It does not panics and does not awake :( > >> As in previous variant it sleeps ok, but on awake it only spin up HDD. > >> No any other activity seen, it does not react on keys, firewire console > >> is dead. > >> It does not answer on network activity. > >> > >> Probably It hangs while try to restore console, and I should try to > >> disable console at all ? > > > >Is the disk active LED on? Many systems have had trouble with this, > >although I thought Soren had fixed this. > > Both led and sound, it spin-up, shows some activity by both led and > sound, and then stop any activity. > > Probably I should try kernel without ata ? (only md for root) Only if the LED comes on and stays on is it an ATA issue. If it seems to come back but never finishes, it is something else. Can you connect to the system over the net after resume? If so, it's probably a display issue, as you seem to have suspected. I was just bringing up the ATA issue in case you really had two problems. Seems like you do not. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 23:27:29 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF85C16A4CE for ; Wed, 2 Mar 2005 23:27:29 +0000 (GMT) Received: from omega.lacnic.net.uy (lacnic.net.uy [200.40.228.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B230B43D5C for ; Wed, 2 Mar 2005 23:27:28 +0000 (GMT) (envelope-from pablo@omega.lacnic.net.uy) Received: from omega.lacnic.net.uy (localhost.localdomain [127.0.0.1]) by omega.lacnic.net.uy (8.12.11/8.12.5) with ESMTP id j230SrlG010039; Wed, 2 Mar 2005 21:28:53 -0300 Received: (from pablo@localhost) by omega.lacnic.net.uy (8.12.11/8.12.5/Submit) id j230SqMX010038; Wed, 2 Mar 2005 21:28:52 -0300 Date: Wed, 2 Mar 2005 21:28:52 -0300 From: Pablo Allietti To: Vince Vielhaber Message-ID: <20050303002852.GB9739@omega.lacnic.net.uy> References: <20050302221736.GA5378@omega.lacnic.net.uy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Operating-System: Freebsd 5.3 X-Organization: LACNIC X-URL: http://lacnic.net/ X-Lacnic-MailScanner-Information: Please contact Lacnic for more information (lacnic at lacnic.net) X-Lacnic-MailScanner: Found to be clean X-MailScanner-From: pablo@omega.lacnic.net.uy cc: freebsd-mobile@freebsd.org cc: Pablo Allietti Subject: Re: ndiswrapper X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 23:27:30 -0000 On Wed, Mar 02, 2005 at 04:27:37PM -0500, Vince Vielhaber wrote: > On Wed, 2 Mar 2005, Pablo Allietti wrote: > > > hi all again. :) > > > > i have a problem to install ndiswrapper any body have a port for that? > > or any instruction to make this package? > > > > this is my error > > > > sony# make install > > "Makefile", line 1: Need an operator > > make: fatal errors encountered -- cannot continue > > sony# > > > > and the make file have this in the first line. i add to > > #!/usr/local/bin/bash but nothing happend. > > That error usually indicates you need gmake, unless there's some > junk in that line. And you don't want #!/usr/local/bin/bash in > the makefile. no i try with gmake and not working too. :( > > Vince. > -- > Fast, inexpensive internet service 56k and beyond! http://www.pop4.net/ > http://www.meanstreamradio.com http://www.unknown-artists.com > Online radio: It's not file sharing, it's just radio. ---end quoted text--- -- Pablo Allietti LACNIC -------------- From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 00:45:16 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA8E716A4CE for ; Thu, 3 Mar 2005 00:45:16 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEA4F43D48 for ; Thu, 3 Mar 2005 00:45:14 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j230g6kq063009; Wed, 2 Mar 2005 17:42:07 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 02 Mar 2005 17:42:27 -0700 (MST) Message-Id: <20050302.174227.73381425.imp@bsdimp.com> To: aidanwhyte@eircom.net From: "M. Warner Losh" In-Reply-To: <00e001c51ec2$d6b17550$2201040a@moriarty> References: <00e001c51ec2$d6b17550$2201040a@moriarty> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: 802.11a pcmcia cards X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 00:45:17 -0000 I've found Atheros AR5210 cards that have an external connector if you drill out a hole for it through the plastic... Warner From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 03:45:25 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CF6316A4CE for ; Thu, 3 Mar 2005 03:45:25 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FB8443D48 for ; Thu, 3 Mar 2005 03:45:25 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so376180wra for ; Wed, 02 Mar 2005 19:45:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=BTtcdbDZ5/ip6Dr60bsvmsR/z0T82TU0Nhc6eO52OuGqx1loaH+j4pL5T6BqAdGglaDZ9HqiyqpgyQfcikev3ibroI7zOWf08M5S3NPzfJzM3Cs8DcqOggBy9oU4yI+MJSzIISmntWaTQG5IhalC0Uq6jWLGPR9oCLy0q6zSrvc= Received: by 10.54.31.11 with SMTP id e11mr49993wre; Wed, 02 Mar 2005 19:45:02 -0800 (PST) Received: by 10.54.7.56 with HTTP; Wed, 2 Mar 2005 19:44:59 -0800 (PST) Message-ID: <6eb82e05030219447bdda412@mail.gmail.com> Date: Thu, 3 Mar 2005 11:44:59 +0800 From: Rong-En Fan To: Ian Dowse In-Reply-To: <200502282026.aa38504@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200502281016.aa49779@salmon.maths.tcd.ie> <200502282026.aa38504@salmon.maths.tcd.ie> cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Rong-En Fan List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 03:45:25 -0000 On Mon, 28 Feb 2005 20:26:16 +0000, Ian Dowse wrote: > > I've updated the patch at > > http://people.freebsd.org/~iedowse/vesa_restore.diff > > so that the VESA code allows up to 8k of state storage and will > fail if the BIOS claims to need more space. Could you try this with > the vesa module loaded and with both 0 and 1 for hw.acpi.reset_video? I use 3/3's current with this patch on IBM TP X31. I can now successfully suspend/resume in X with dri enable on RADEON! (can't do that before, with dri, after resume screen mess up). reset_video 0 or 1 both works. It even works without vesa module loaded. The only problem is that my tracepoint (psm0) dead after resume. demsg (verbose) and suspend/resume dmesg are both at http://rafan.infor.org/tmp/vesa/ rafan. From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 04:58:28 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A242616A4CE for ; Thu, 3 Mar 2005 04:58:28 +0000 (GMT) Received: from diamond.34sp.com (diamond.34sp.com [195.50.105.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8763143D55 for ; Thu, 3 Mar 2005 04:58:27 +0000 (GMT) (envelope-from list@understudy.net) Received: (qmail 1068 invoked from network); 3 Mar 2005 04:58:26 -0000 Received: from adsl-11-166-118.mia.bellsouth.net (HELO ?10.0.0.114?) (65.11.166.118) by mcp.34sp.com with SMTP; 3 Mar 2005 04:58:25 -0000 Message-ID: <4226996D.3020402@understudy.net> Date: Wed, 02 Mar 2005 23:58:21 -0500 From: Understudy User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Matthew N. Dodd" References: <20050219040357.47106754@spadger.best.vwh.net> <42197CA3.7050709@understudy.net> <421E331C.10804@siol.net> <20050224181142.B60128@sasami.jurai.net> <421E7780.6050800@understudy.net> <20050224202147.A60128@sasami.jurai.net> <421EAAA5.3090304@understudy.net> <20050225095658.D60128@sasami.jurai.net> In-Reply-To: <20050225095658.D60128@sasami.jurai.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Thinkpad 600e interrupt storm X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 04:58:28 -0000 Matthew N. Dodd wrote: > On Thu, 24 Feb 2005, Understudy wrote: > [how do I build a kernel module?] > > cd /sys/modules/bios/smapi > make all > make load > > Also, this will only work on 5.x or -CURRENT. > Okay , I finally got that to work. After realizing this was a typo on my part. Slacker# cd /sys/modules/bios/smapi Slacker# make all Warning: Object directory not changed from original /usr/src/sys/modules/bios/smapi Slacker# make load /sbin/kldload -v /usr/src/sys/modules/bios/smapi/smapi.ko Loaded /usr/src/sys/modules/bios/smapi/smapi.ko, id=4 Slacker# I read through the man pages now that this is loaded how do I find this smapi config ? I have a smapi_config.c smapi_config.o. But I don't see in it what you are looking for. Sincerely, Brendhan From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 05:45:23 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEA1516A4CE for ; Thu, 3 Mar 2005 05:45:23 +0000 (GMT) Received: from mail.liquidation.com (mail.liquidation.com [65.196.108.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59B9243D3F for ; Thu, 3 Mar 2005 05:45:23 +0000 (GMT) (envelope-from pgollucci@p6m7g8.com) Received: from [10.0.0.82] (everything.liquidation.com [65.196.108.171]) by mail.liquidation.com (8.12.9/8.12.9) with ESMTP id j235m5ir026821 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 3 Mar 2005 00:48:05 -0500 Message-ID: <4226A470.6040504@p6m7g8.com> Date: Thu, 03 Mar 2005 00:45:20 -0500 From: "Philip M. Golllucci" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Content-Type: multipart/mixed; boundary="------------000807080404020600050508" X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-4.722, required 5, AWL 0.18, BAYES_00 -4.90) X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Dell 5160 / Wireless X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 05:45:23 -0000 This is a multi-part message in MIME format. --------------000807080404020600050508 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I've got a dell 5160 notebook with builtin wireless ethernet. The ethernet is none existant. Per a kind soul's suggest on -questions, I've relocated here after adding all the networking devices from NOTES to my kernel config with still no luck. Windows XP home detects it as Dell Wireless WLAN 1350 Mini-PCI Card Attached are: uname -a dmesg ifconfig -a kernel config file Thanks in advance. --------------000807080404020600050508-- From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 05:52:39 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E159816A4CE for ; Thu, 3 Mar 2005 05:52:39 +0000 (GMT) Received: from sasami.jurai.net (sasami.jurai.net [69.17.104.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 090B143D49 for ; Thu, 3 Mar 2005 05:52:39 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [69.17.104.113]) by sasami.jurai.net (8.13.1/8.13.1) with ESMTP id j235qate032850; Thu, 3 Mar 2005 00:52:38 -0500 (EST) (envelope-from mdodd@FreeBSD.ORG) Date: Thu, 3 Mar 2005 00:52:35 -0500 (EST) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: Understudy In-Reply-To: <4226996D.3020402@understudy.net> Message-ID: <20050303004752.V16908@sasami.jurai.net> References: <20050219040357.47106754@spadger.best.vwh.net> <42197CA3.7050709@understudy.net> <421E331C.10804@siol.net> <20050224181142.B60128@sasami.jurai.net> <421E7780.6050800@understudy.net> <20050224202147.A60128@sasami.jurai.net> <421EAAA5.3090304@understudy.net> <20050225095658.D60128@sasami.jurai.net> <4226996D.3020402@understudy.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (sasami.jurai.net [69.17.104.113]); Thu, 03 Mar 2005 00:52:38 -0500 (EST) cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Thinkpad 600e interrupt storm X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 05:52:40 -0000 On Wed, 2 Mar 2005, Understudy wrote: > I read through the man pages now that this is loaded how do I find this > smapi config ? I have a smapi_config.c smapi_config.o. But I don't see > in it what you are looking for. You untar ftp://ftp.jurai.net/users/winter/smapi.tar.gz This creates a hierarchy in your current directory so do this in /tmp. As root run the following commands: 'cd /tmp/usr.sbin/smapi' and then 'make all install'. The 'smapi' command will be installed in /usr/sbin which should be in root's path. Run it. Its got pretty reasonable usage instructions. -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00 From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 05:55:16 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F331A16A4CF for ; Thu, 3 Mar 2005 05:55:15 +0000 (GMT) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FD8843D3F for ; Thu, 3 Mar 2005 05:55:15 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.13.1/8.13.1) with ESMTP id j235tDir000207; Wed, 2 Mar 2005 21:55:15 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.13.1/8.12.9) with ESMTP id j235tDXF060641; Wed, 2 Mar 2005 21:55:13 -0800 (PST) (envelope-from frank@realtime.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.1/8.13.1/Submit) id j235tDc7060619; Wed, 2 Mar 2005 21:55:13 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200503030555.j235tDc7060619@realtime.exit.com> In-Reply-To: <4226A470.6040504@p6m7g8.com> To: "Philip M. Golllucci" Date: Wed, 2 Mar 2005 21:55:12 -0800 (PST) X-Copyright0: Copyright 2005 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL119 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: freebsd-mobile@freebsd.org Subject: Re: Dell 5160 / Wireless X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: frank@exit.com List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 05:55:16 -0000 Philip M. Golllucci wrote: > I've got a dell 5160 notebook with builtin wireless ethernet. > The ethernet is none existant. Inspiron 5160? It has an RJ45 for wired ethernet based on a Broadcom chip, use the bfe(4) driver. As for the wireless, you have two options. You can use the ndis(4) driver to run the Dell 1350 (really another Broadcom chipset), or you can replace that with an Atheros-based minipci card and use the ath(4) driver. I chose the latter course and am using it right now. I am running -current, however, since the wireless support there is _much_ better than that in 5.x. Running -current is not for the faint of heart. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 05:56:19 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE66B16A4CF for ; Thu, 3 Mar 2005 05:56:19 +0000 (GMT) Received: from mail.liquidation.com (mail.liquidation.com [65.196.108.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93E1343D1F for ; Thu, 3 Mar 2005 05:56:18 +0000 (GMT) (envelope-from pgollucci@p6m7g8.com) Received: from [10.0.0.82] (everything.liquidation.com [65.196.108.171]) by mail.liquidation.com (8.12.9/8.12.9) with ESMTP id j235wwir027102 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 3 Mar 2005 00:58:58 -0500 Message-ID: <4226A6FD.1020106@p6m7g8.com> Date: Thu, 03 Mar 2005 00:56:13 -0500 From: "Philip M. Golllucci" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Philip M. Golllucci" References: <4226A470.6040504@p6m7g8.com> In-Reply-To: <4226A470.6040504@p6m7g8.com> Content-Type: multipart/mixed; boundary="------------080509000104020809050401" X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-4.723, required 5, AWL 0.18, BAYES_00 -4.90) cc: freebsd-mobile@freebsd.org Subject: Re: Dell 5160 / Wireless [with attachments not stripped] X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 05:56:19 -0000 This is a multi-part message in MIME format. --------------080509000104020809050401 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Appologies... .tar.gz's are stripped .. I thought I checked it on the mailing list page. Philip M. Golllucci wrote: > Hi, > > I've got a dell 5160 notebook with builtin wireless ethernet. > The ethernet is none existant. > > Per a kind soul's suggest on -questions, I've relocated here > after adding all the networking devices from NOTES to my kernel config > with still no luck. > > Windows XP home detects it as Dell Wireless WLAN 1350 Mini-PCI Card > > Attached are: > uname -a > dmesg > ifconfig -a > kernel config file > > Thanks in advance. > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" --------------080509000104020809050401 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.txt" Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-CURRENT #5: Wed Mar 2 23:40:08 EST 2005 root@laptop1.p6m7g8.net:/usr/obj/usr/src/sys/LAPTOP WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Mobile Intel(R) Pentium(R) 4 CPU 3.06GHz (3056.82-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 536662016 (511 MB) avail memory = 515883008 (491 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard WORNING! Network stack is not MPSAFE. Turning off debug.cp.mpsafenet. WORNING! Network stack is not MPSAFE. Turning off debug.ct.mpsafenet. WORNING! Network stack is not MPSAFE. Turning off debug.cx.mpsafenet. npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 0.3 (no driver attached) pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.2 (no driver attached) pci0: at device 29.7 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 pci2: at device 1.0 (no driver attached) pci2: at device 2.0 (no driver attached) cbb0: at device 4.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pci2: at device 4.1 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xbfa0-0xbfaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.5 (no driver attached) pci0: at device 31.6 (no driver attached) acpi_tz0: on acpi0 pci_link0: irq 11 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 11 on acpi0 pci_link3: irq 11 on acpi0 pci_link4: irq 11 on acpi0 pci_link5: irq 11 on acpi0 atkbdc0: port 0x66,0x62,0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd0: [GIANT-LOCKED] psm0: flags 0x1000 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 speaker0: port 0x67,0x65,0x63,0x61 on acpi0 orm0: at iomem 0xcf800-0xcffff,0xc0000-0xcf7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. IP Filter: v3.4.35 initialized. Default = pass all, Logging = enabled ipfw2 initialized, divert loadable, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default acd0: CDRW at ata0-master UDMA33 ad2: 38154MB [77520/16/63] at ata1-master UDMA100 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad2s1a --------------080509000104020809050401 Content-Type: text/plain; name="ifconfig.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ifconfig.txt" lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 --------------080509000104020809050401 Content-Type: text/plain; name="LAPTOP" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="LAPTOP" ############################################################################### ################################## Architecture ############################### ############################################################################### machine i386 maxusers 256 cpu I686_CPU # aka Pentium Pro(tm) ident LAPTOP device npx ## Multi-Processor options SMP device apic ## Scheduler options SCHED_4BSD ############################################################################### ################################# Compatibility ############################### ############################################################################### options COMPAT_43 options COMPAT_FREEBSD4 ############################################################################### ################################# Networking ################################## ############################################################################### options INET #Internet communications protocols options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IP device ether #Generic Ethernet device loop #Network loopback device device miibus device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus ############################################################################### ########################## Firewalls ########################################## ############################################################################### options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT #divert sockets options IPFILTER #ipfilter support options IPFILTER_LOG #ipfilter logging options IPSTEALTH #support for stealth forwarding options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN ############################################################################### ################################# FileSystems ################################# ############################################################################### options FFS #Memory File System options CD9660 #ISO 9660 filesystem options MSDOSFS options NFSCLIENT options PROCFS #Process filesystem options PSEUDOFS options SOFTUPDATES options UFS_DIRHASH options QUOTA #enable disk quotas ############################################################################### ############################## ATA Devices #################################### ############################################################################### device isa device pci device ata device atadisk device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID ############################################################################### ############################### Misc Devices ################################## ############################################################################### device pty #Pseudo ttys device speaker #Play IBM BASIC-style noises out your speaker device md #Memory/malloc disk device snp #Snoop device - to look at pty/vty/etc.. device atkbdc device atkbd device psm device vga device agp device random device io device mem device pty device tun # Packet tunnel. device bpf ############################################################################### ################################## Terminal Options ########################### ############################################################################### device sc options MAXCONS=16 # number of virtual consoles options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores device arl device ed options ED_3C503 options ED_HPP options ED_SIC device el device ie # Hints only required for Starlan device lnc device sbni ## require device sppp device sppp device sr device ar device cp device cx device ctau ## require device token and sppp device token device oltr # Wireless NIC cards device wlan # 802.11 support device an # Aironet 4500/4800 802.11 wireless NICs. device awi # BayStack 660 and others device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. device wl # Older non 802.11 Wavelan wireless NIC. --------------080509000104020809050401 Content-Type: text/plain; name="uname.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="uname.txt" FreeBSD laptop1.p6m7g8.net 6.0-CURRENT FreeBSD 6.0-CURRENT #5: Wed Mar 2 23:40:08 EST 2005 root@laptop1.p6m7g8.net:/usr/obj/usr/src/sys/LAPTOP i386 --------------080509000104020809050401-- From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 07:40:12 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFEC916A4CE for ; Thu, 3 Mar 2005 07:40:12 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA51943D55 for ; Thu, 3 Mar 2005 07:40:11 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.44 (FreeBSD)) id 1D6bWW-0000mB-9s; Thu, 03 Mar 2005 00:36:52 +0300 From: Vladimir Grebenschikov To: Kevin Oberman In-Reply-To: <20050302191809.B54675D07@ptavv.es.net> References: <20050302191809.B54675D07@ptavv.es.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Thu, 03 Mar 2005 00:36:51 +0300 Message-Id: <1109799411.1629.4.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.1.5 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: Ian Dowse cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 07:40:12 -0000 =F7 =D3=D2, 02/03/2005 =D7 11:18 -0800, Kevin Oberman =D0=C9=DB=C5=D4: >> From: Vladimir Grebenschikov >> Date: Tue, 01 Mar 2005 23:31:15 +0300 >> Sender: owner-freebsd-mobile@freebsd.org >>=20 >> =F7 =D0=CE, 28/02/2005 =D7 20:26 +0000, Ian Dowse =D0=C9=DB=C5=D4: >> >In message <200502281016.aa49779@salmon.maths.tcd.ie>, Ian Dowse writes= : >> >>In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschikov= writes: >> >>>Also if I try this patch with vesa module loaded it just carsh in vm8= 6 >> >>>mode on zzz (curproc acpiconf). >> >> >> >>It is probably necessary to get this working with VESA to have much >> >>of a chance of it helping, since otherwise only the basic VGA >> >>registers will be saved and restored. >> >> >> >>One possible reason for the vm86 crash is that it appears our VESA >> >>code cannot handle saving more than 4k of state data. Does it make >> >>any difference if you revert the part of the patch that changed >> >>STATE_MOST to STATE_ALL? i.e. change the two uses of STATE_ALL in >> >>vesa.c back to STATE_MOST. I found that with SAVE_MOST, I needed >> >>to switch to X and back before the console would display, but the >> >>backlight did come on immediately. >> > >> >I've updated the patch at >> > >> > http://people.freebsd.org/~iedowse/vesa_restore.diff >> > >> >so that the VESA code allows up to 8k of state storage and will >> >fail if the BIOS claims to need more space. Could you try this with >> >the vesa module loaded and with both 0 and 1 for hw.acpi.reset_video? >>=20 >> I've rechecked patch with fresh kernel build and firewire console. >>=20 >> It does not panics and does not awake :(=20 >> As in previous variant it sleeps ok, but on awake it only spin up HDD. >> No any other activity seen, it does not react on keys, firewire console >> is dead. >> It does not answer on network activity. >>=20 >> Probably It hangs while try to restore console, and I should try to >> disable console at all ?=20 > >Is the disk active LED on? Many systems have had trouble with this, >although I thought Soren had fixed this. Both led and sound, it spin-up, shows some activity by both led and sound, and then stop any activity. Probably I should try kernel without ata ? (only md for root)=20 >If the LED is on, you might want to try ATA MkIII. (That WILL break >ATAPICAM!)=20 --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 07:40:14 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C96EA16A4CE for ; Thu, 3 Mar 2005 07:40:14 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E6B643D58 for ; Thu, 3 Mar 2005 07:40:14 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.44 (FreeBSD)) id 1D6jYw-00076q-5s; Thu, 03 Mar 2005 09:11:54 +0300 From: Vladimir Grebenschikov To: Kevin Oberman In-Reply-To: <20050302220235.DB1E95D08@ptavv.es.net> References: <20050302220235.DB1E95D08@ptavv.es.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Thu, 03 Mar 2005 09:11:53 +0300 Message-Id: <1109830313.1629.8.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.1.5 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: Ian Dowse cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 07:40:15 -0000 =F7 =D3=D2, 02/03/2005 =D7 14:02 -0800, Kevin Oberman =D0=C9=DB=C5=D4: >> From: Vladimir Grebenschikov >> Date: Thu, 03 Mar 2005 00:36:51 +0300 >> Sender: Vladimir Grebenschikov >>=20 >> =F7 =D3=D2, 02/03/2005 =D7 11:18 -0800, Kevin Oberman =D0=C9=DB=C5=D4: >> >> From: Vladimir Grebenschikov >> >> Date: Tue, 01 Mar 2005 23:31:15 +0300 >> >> Sender: owner-freebsd-mobile@freebsd.org >> >>=20 >> >> =F7 =D0=CE, 28/02/2005 =D7 20:26 +0000, Ian Dowse =D0=C9=DB=C5=D4: >> >> >In message <200502281016.aa49779@salmon.maths.tcd.ie>, Ian Dowse wri= tes> : >> >> >>In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschi= kov> writes: >> >> >>>Also if I try this patch with vesa module loaded it just carsh in = vm8> 6 >> >> >>>mode on zzz (curproc acpiconf). >> >> >> >> >> >>It is probably necessary to get this working with VESA to have much >> >> >>of a chance of it helping, since otherwise only the basic VGA >> >> >>registers will be saved and restored. >> >> >> >> >> >>One possible reason for the vm86 crash is that it appears our VESA >> >> >>code cannot handle saving more than 4k of state data. Does it make >> >> >>any difference if you revert the part of the patch that changed >> >> >>STATE_MOST to STATE_ALL? i.e. change the two uses of STATE_ALL in >> >> >>vesa.c back to STATE_MOST. I found that with SAVE_MOST, I needed >> >> >>to switch to X and back before the console would display, but the >> >> >>backlight did come on immediately. >> >> > >> >> >I've updated the patch at >> >> > >> >> > http://people.freebsd.org/~iedowse/vesa_restore.diff >> >> > >> >> >so that the VESA code allows up to 8k of state storage and will >> >> >fail if the BIOS claims to need more space. Could you try this with >> >> >the vesa module loaded and with both 0 and 1 for hw.acpi.reset_video= ? >> >>=20 >> >> I've rechecked patch with fresh kernel build and firewire console. >> >>=20 >> >> It does not panics and does not awake :(=20 >> >> As in previous variant it sleeps ok, but on awake it only spin up HDD= . >> >> No any other activity seen, it does not react on keys, firewire conso= le >> >> is dead. >> >> It does not answer on network activity. >> >>=20 >> >> Probably It hangs while try to restore console, and I should try to >> >> disable console at all ?=20 >> > >> >Is the disk active LED on? Many systems have had trouble with this, >> >although I thought Soren had fixed this. >>=20 >> Both led and sound, it spin-up, shows some activity by both led and >> sound, and then stop any activity. >>=20 >> Probably I should try kernel without ata ? (only md for root)=20 > >Only if the LED comes on and stays on is it an ATA issue. If it seems to >come back but never finishes, it is something else. > >Can you connect to the system over the net after resume?=20 No, I can't ping machine, and firewire console is dead. >If so, it's probably a display issue, as you seem to have suspected. I was= just >bringing up the ATA issue in case you really had two problems. Seems >like you do not. Anyway, I'll try kernel without ATA to be sure. --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 08:44:39 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19C7616A4DE for ; Thu, 3 Mar 2005 08:44:39 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id B044443D4C for ; Thu, 3 Mar 2005 08:44:38 +0000 (GMT) (envelope-from rob.pollock@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so315163rnf for ; Thu, 03 Mar 2005 00:44:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=G8T2ir7qxe920uZ1eqgKUnEQJAc7PxzdTMBQ8CTGf2mqiB2HhAXcVeiIQSzqkdOuYCPZLi27CqGYUUpVHuwajk/o9p0d6xslDO3H9I4tixQVwT+V514sjP5IiK/wi8YNfQgAux/v5d9YcdWWaYqYNWWqOHGZFAMtyitUxGSvzxs= Received: by 10.38.181.10 with SMTP id d10mr105576rnf; Thu, 03 Mar 2005 00:43:48 -0800 (PST) Received: by 10.38.101.43 with HTTP; Thu, 3 Mar 2005 00:43:48 -0800 (PST) Message-ID: Date: Thu, 3 Mar 2005 21:43:48 +1300 From: Rob Pollock To: freebsd-mobile@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: FreeBSD 5.x on IBM 760EL X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Rob Pollock List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 08:44:39 -0000 Hi all, I noticed a number of posts with people not being able to get CardBus support with FreeBSD 5.x on laptops with the TI-1130 chipset (at least not during the boot process). My laptop doesn't support ACPI, and when you try to boot the installer program, there is no PCMCIA or CardBus support. Thus, networking (and subsequently installing, for a CD-ROM-less machine) is disabled. I am currently using FreeBSD 4.11-RELEASE. I have tried to install 5.x a number of times, and run into the same problem. Perusing the freebsd-mobile archive, I found a recent reference, so it looks like it's still an issue. Thread [Re: PCCard bus don't work] http://www.freebsd.org/cgi/getmsg.cgi?fetch=41766+44775+/usr/local/www/db/text/2005/freebsd-mobile/20050116.freebsd-mobile I would very much like this resolved so that I am not "locked out" of future upgrade paths on my very old machine. (yes, i know, I'm cheap...) Thanks, Rob Pollock. From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 10:29:16 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0952116A4CE for ; Thu, 3 Mar 2005 10:29:16 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62BE843D5A for ; Thu, 3 Mar 2005 10:29:15 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (adsl-68-252-59-28.dsl.wotnoh.ameritech.net [68.252.59.28]) (authenticated bits=0)j23A13mQ082529 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 3 Mar 2005 05:01:04 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: Rong-En Fan Date: Thu, 3 Mar 2005 05:33:12 -0500 User-Agent: KMail/1.7 References: <200502281016.aa49779@salmon.maths.tcd.ie> <200502282026.aa38504@salmon.maths.tcd.ie> <6eb82e05030219447bdda412@mail.gmail.com> In-Reply-To: <6eb82e05030219447bdda412@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3522222.cV02p8EnUv"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200503030533.21126.mistry.7@osu.edu> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 10:29:16 -0000 --nextPart3522222.cV02p8EnUv Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 02 March 2005 10:44 pm, Rong-En Fan wrote: > On Mon, 28 Feb 2005 20:26:16 +0000, Ian Dowse =20 wrote: > > I've updated the patch at > > > > http://people.freebsd.org/~iedowse/vesa_restore.diff > > > > so that the VESA code allows up to 8k of state storage and will > > fail if the BIOS claims to need more space. Could you try this > > with the vesa module loaded and with both 0 and 1 for > > hw.acpi.reset_video? > > I use 3/3's current with this patch on IBM TP X31. I can now > successfully suspend/resume in X with dri enable on RADEON! (can't > do that before, with dri, after resume screen mess up). reset_video > 0 or 1 both works. It even works without vesa module loaded. The > only problem is that my tracepoint (psm0) dead after resume. > Does adding the following to your /boot/device.hints to fix the mouse=20 resume issue: hint.psm.0.flags=3D"0x3000" =2D-=20 Anish Mistry --nextPart3522222.cV02p8EnUv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCJufxxqA5ziudZT0RAkicAJ94Npip/5KH0fbK+lfxdPodC+ZAQwCgrBPw 3A+dUImqzi5vCIYmYUYpVF8= =Ms92 -----END PGP SIGNATURE----- --nextPart3522222.cV02p8EnUv-- From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 10:34:19 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3AA216A4CE for ; Thu, 3 Mar 2005 10:34:19 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id BBC6C43D39 for ; Thu, 3 Mar 2005 10:34:18 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail invoked by alias); 03 Mar 2005 10:34:17 -0000 Received: from pD9E6E9AF.dip.t-dialin.net (EHLO ms.homeip.net) (217.230.233.175) by mail.gmx.net (mp007) with SMTP; 03 Mar 2005 11:34:17 +0100 X-Authenticated: #15946415 Received: from [10.0.0.1] (helo=[10.0.0.13]) by ms.homeip.net with esmtpsa (TLSv1:AES256-SHA:256) id 1D6nhi-000BRs-7i; Thu, 03 Mar 2005 11:37:14 +0100 Message-ID: <4226E824.3080403@gmx.de> Date: Thu, 03 Mar 2005 11:34:12 +0100 From: Jochen Gensch User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Rong-En Fan References: <200502281016.aa49779@salmon.maths.tcd.ie> <200502282026.aa38504@salmon.maths.tcd.ie> <6eb82e05030219447bdda412@mail.gmail.com> In-Reply-To: <6eb82e05030219447bdda412@mail.gmail.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 10:34:19 -0000 Rong-En Fan schrieb: > I use 3/3's current with this patch on IBM TP X31. I can now successfully > suspend/resume in X with dri enable on RADEON! (can't do that before, with > dri, after resume screen mess up). reset_video 0 or 1 both works. It even > works without vesa module loaded. The only problem is that my tracepoint > (psm0) dead after resume. On my Thinkpad A30p I was able to reactivate my trackpoint after resume by setting hint.psm.0.flags="0x6000" in /boot/device.hints. Could you tell me more about you resume issues? I have a Radeon Mobility as well an my backlight does not turn off, when going to suspend nuder a normal CURRENT. Did you also use that DPMS patch posted here a while ago, or did you only use that vesa patch? No other modifications, any sysctls...? Thanks, Jochen From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 12:14:25 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 230E616A4CE for ; Thu, 3 Mar 2005 12:14:25 +0000 (GMT) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48B3B43D48 for ; Thu, 3 Mar 2005 12:14:24 +0000 (GMT) (envelope-from pdquilty@adelphia.net) Received: from pdq-9100 ([67.22.208.158]) by mta11.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with ESMTP id <20050303121423.ODPJ5402.mta11.adelphia.net@pdq-9100> for ; Thu, 3 Mar 2005 07:14:23 -0500 From: "Peter D. Quilty" To: "Philip M. Golllucci" In-Reply-To: <200503030555.j235tDc7060619@realtime.exit.com> References: <200503030555.j235tDc7060619@realtime.exit.com> Message-Id: <1109851966.76608.16.camel@pdq-9100> Mime-Version: 1.0 Resent-From: "Peter D. Quilty" Resent-To: freebsd-mobile@freebsd.org Date: Thu, 03 Mar 2005 07:14:22 -0500 X-Mailer: Evolution 2.0.4 FreeBSD GNOME Team Port Resent-Message-Id: <20050303121424.48B3B43D48@mx1.FreeBSD.org> Resent-Date: Thu, 3 Mar 2005 12:14:24 +0000 (GMT) Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-mobile@freebsd.org Subject: Re: Dell 5160 / Wireless X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Peter D. Quilty" List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 12:14:25 -0000 I have an Inspiron 9100 with a Dell 1350 card running 5.3-RELEASE-p5. I've been using the ndis driver for about a month now with only the occasional minor problem. ndis0: mem 0xfaff6000-0xfaff7fff irq 17 at device 3.0 on pci2 ndis0: NDIS API version: 5.1 ndis0: Ethernet address: 00:90:96:a3:80:81 ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps ndis0: flags=8843 mtu 1500 inet 192.168.1.57 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:90:96:a3:80:81 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated ssid MY_SSID_HERE 1:MY_SSID_HERE channel 1 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode OFF wepmode MIXED weptxkey 1 wepkey 1:104-bit It works great 99% of the time, but occasionally under certain heavy load conditions I get the following: kernel: ndis0: watchdog timeout kernel: ndis0: link down When I do "ifconfig ndis0 up", I then get: kernel: NDIS: buggy driver deleting active packet pool! kernel: NDIS: buggy driver deleting active buffer pool! kernel: ndis0: link up And it starts working again. I haven't been able to figure out why, but it hardly happens, so I haven't spent any time on it. PDQ On Wed, 2005-03-02 at 21:55 -0800, Frank Mayhar wrote: > Philip M. Golllucci wrote: > > I've got a dell 5160 notebook with builtin wireless ethernet. > > The ethernet is none existant. > > Inspiron 5160? It has an RJ45 for wired ethernet based on a Broadcom > chip, use the bfe(4) driver. As for the wireless, you have two options. > You can use the ndis(4) driver to run the Dell 1350 (really another Broadcom > chipset), or you can replace that with an Atheros-based minipci card and > use the ath(4) driver. > > I chose the latter course and am using it right now. I am running -current, > however, since the wireless support there is _much_ better than that in > 5.x. Running -current is not for the faint of heart. From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 12:41:20 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCFFD16A4CE for ; Thu, 3 Mar 2005 12:41:20 +0000 (GMT) Received: from diamond.34sp.com (diamond.34sp.com [195.50.105.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id E752843D1F for ; Thu, 3 Mar 2005 12:41:17 +0000 (GMT) (envelope-from list@understudy.net) Received: (qmail 24044 invoked from network); 3 Mar 2005 12:41:15 -0000 Received: from adsl-11-166-118.mia.bellsouth.net (HELO ?10.0.0.114?) (65.11.166.118) by mcp.34sp.com with SMTP; 3 Mar 2005 12:41:15 -0000 Message-ID: <422705E7.5090000@understudy.net> Date: Thu, 03 Mar 2005 07:41:11 -0500 From: Understudy User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Matthew N. Dodd" References: <20050219040357.47106754@spadger.best.vwh.net> <42197CA3.7050709@understudy.net> <421E331C.10804@siol.net> <20050224181142.B60128@sasami.jurai.net> <421E7780.6050800@understudy.net> <20050224202147.A60128@sasami.jurai.net> <421EAAA5.3090304@understudy.net> <20050225095658.D60128@sasami.jurai.net> <4226996D.3020402@understudy.net> <20050303004752.V16908@sasami.jurai.net> In-Reply-To: <20050303004752.V16908@sasami.jurai.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Thinkpad 600e interrupt storm X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 12:41:21 -0000 Matthew N. Dodd wrote: > On Wed, 2 Mar 2005, Understudy wrote: > >> I read through the man pages now that this is loaded how do I find >> this smapi config ? I have a smapi_config.c smapi_config.o. But I >> don't see in it what you are looking for. > > > You untar ftp://ftp.jurai.net/users/winter/smapi.tar.gz > > This creates a hierarchy in your current directory so do this in > /tmp. As root run the following commands: 'cd /tmp/usr.sbin/smapi' > and then 'make all install'. > > The 'smapi' command will be installed in /usr/sbin which should be in > root's path. Run it. Its got pretty reasonable usage instructions. > ahhh, When I downloaded I just put it in a downloads folder I in my user account. I did a make from there. I will move it to /tmp and try again. Sincerely, Brendhan From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 13:52:49 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A08A316A4CE for ; Thu, 3 Mar 2005 13:52:49 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3865F43D48 for ; Thu, 3 Mar 2005 13:52:49 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so505490wra for ; Thu, 03 Mar 2005 05:52:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=kvdBaRWoc5/SYjIDrmXUq4i4cFm77Qjt95nMcF5pPEQzSoO0zLi558TRoOSNVeHS01k34k4lVPUaFwmIP2U9JlAPtIZt7ADuuFwEyDnueLUUsqPNp4Lv6WdoBQVjnmnlGXZjXSBCw9nh1rw0ndF/pW5B0yaDZuG8U8f+Pux5w98= Received: by 10.54.66.3 with SMTP id o3mr21587wra; Thu, 03 Mar 2005 05:52:48 -0800 (PST) Received: by 10.54.7.56 with HTTP; Thu, 3 Mar 2005 05:52:48 -0800 (PST) Message-ID: <6eb82e0503030552c9506e6@mail.gmail.com> Date: Thu, 3 Mar 2005 21:52:48 +0800 From: Rong-En Fan To: Anish Mistry In-Reply-To: <200503030533.21126.mistry.7@osu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200502281016.aa49779@salmon.maths.tcd.ie> <200502282026.aa38504@salmon.maths.tcd.ie> <6eb82e05030219447bdda412@mail.gmail.com> <200503030533.21126.mistry.7@osu.edu> cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Rong-En Fan List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 13:52:49 -0000 On Thu, 3 Mar 2005 05:33:12 -0500, Anish Mistry wrote: > On Wednesday 02 March 2005 10:44 pm, Rong-En Fan wrote: > > I use 3/3's current with this patch on IBM TP X31. I can now > > successfully suspend/resume in X with dri enable on RADEON! (can't > > do that before, with dri, after resume screen mess up). reset_video > > 0 or 1 both works. It even works without vesa module loaded. The > > only problem is that my tracepoint (psm0) dead after resume. > > > Does adding the following to your /boot/device.hints to fix the mouse > resume issue: > hint.psm.0.flags="0x3000" Yes, thanks. And in fact, 0x2000 works :) BTW, 0x2000 is PSM_HOOKRESUME in kernel conf. Regards, rafan From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 13:55:07 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A578C16A4CE for ; Thu, 3 Mar 2005 13:55:07 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35FDB43D41 for ; Thu, 3 Mar 2005 13:55:07 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so506184wra for ; Thu, 03 Mar 2005 05:55:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=dQMkgpXwIW8wWzc7QcnCOyiSdIOVZx6NC11wkTZGntAWAm+8P/BRzAE1o9DvHYt8Tgd1TPf6uGHPXHyaTTUzHrEYrLF9jeRCFSK3tPCGCAWrDZb2j/YDC9cV+jUkAlcACTOUUw1wfD9mXFsYuNGEBqCCznb8HBvQbiOaTPscwjI= Received: by 10.54.70.7 with SMTP id s7mr47696wra; Thu, 03 Mar 2005 05:55:06 -0800 (PST) Received: by 10.54.7.56 with HTTP; Thu, 3 Mar 2005 05:55:06 -0800 (PST) Message-ID: <6eb82e05030305552d4481fb@mail.gmail.com> Date: Thu, 3 Mar 2005 21:55:06 +0800 From: Rong-En Fan To: Jochen Gensch In-Reply-To: <4226E824.3080403@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200502281016.aa49779@salmon.maths.tcd.ie> <200502282026.aa38504@salmon.maths.tcd.ie> <6eb82e05030219447bdda412@mail.gmail.com> <4226E824.3080403@gmx.de> cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Rong-En Fan List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 13:55:07 -0000 On Thu, 03 Mar 2005 11:34:12 +0100, Jochen Gensch wrote: > Rong-En Fan schrieb: > > > I use 3/3's current with this patch on IBM TP X31. I can now successfully > > suspend/resume in X with dri enable on RADEON! (can't do that before, with > > dri, after resume screen mess up). reset_video 0 or 1 both works. It even > > works without vesa module loaded. The only problem is that my tracepoint > > (psm0) dead after resume. > > On my Thinkpad A30p I was able to reactivate my trackpoint after resume > by setting hint.psm.0.flags="0x6000" in /boot/device.hints. > > Could you tell me more about you resume issues? I have a Radeon Mobility > as well an my backlight does not turn off, when going to suspend nuder a > normal CURRENT. Did you also use that DPMS patch posted here a while > ago, or did you only use that vesa patch? > > No other modifications, any sysctls...? I have vesa patch and no dpms patch. backlight is not off in suspend. The DPMS patch works ago, but it does not work for a few months. It is said that you can use xset dpms force off to turn off backlight, but i never tried that. no other modifications, hw.acpi.reset_video is 0, but 1 also works for me. Regards, rafan. From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 20:56:05 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AFD716A4CE for ; Thu, 3 Mar 2005 20:56:05 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 718E343D5D for ; Thu, 3 Mar 2005 20:56:05 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Thu, 03 Mar 2005 12:56:05 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id A87D25D07; Thu, 3 Mar 2005 12:56:04 -0800 (PST) To: Jochen Gensch In-reply-to: Your message of "Thu, 03 Mar 2005 11:34:12 +0100." <4226E824.3080403@gmx.de> Date: Thu, 03 Mar 2005 12:56:04 -0800 From: "Kevin Oberman" Message-Id: <20050303205604.A87D25D07@ptavv.es.net> cc: Rong-En Fan cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 20:56:05 -0000 > Date: Thu, 03 Mar 2005 11:34:12 +0100 > From: Jochen Gensch > Sender: owner-freebsd-mobile@freebsd.org > > Rong-En Fan schrieb: > > > I use 3/3's current with this patch on IBM TP X31. I can now successfully > > suspend/resume in X with dri enable on RADEON! (can't do that before, with > > dri, after resume screen mess up). reset_video 0 or 1 both works. It even > > works without vesa module loaded. The only problem is that my tracepoint > > (psm0) dead after resume. > > On my Thinkpad A30p I was able to reactivate my trackpoint after resume > by setting hint.psm.0.flags="0x6000" in /boot/device.hints. > > Could you tell me more about you resume issues? I have a Radeon Mobility > as well an my backlight does not turn off, when going to suspend nuder a > normal CURRENT. Did you also use that DPMS patch posted here a while > ago, or did you only use that vesa patch? hint.psm.0.flags="0x6000" is probably a bit excessive. Mine does fine with hint.psm.0.flags="0x2000". The man page suggests trying 2000 first and 6000 only if 2000 fails. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 20:57:58 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3404616A4CF for ; Thu, 3 Mar 2005 20:57:58 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7FE743D46 for ; Thu, 3 Mar 2005 20:57:57 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Thu, 03 Mar 2005 12:57:57 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 4B8935D07; Thu, 3 Mar 2005 12:57:57 -0800 (PST) To: Rong-En Fan In-reply-to: Your message of "Thu, 03 Mar 2005 21:55:06 +0800." <6eb82e05030305552d4481fb@mail.gmail.com> Date: Thu, 03 Mar 2005 12:57:57 -0800 From: "Kevin Oberman" Message-Id: <20050303205757.4B8935D07@ptavv.es.net> cc: Jochen Gensch cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 20:57:58 -0000 > Date: Thu, 3 Mar 2005 21:55:06 +0800 > From: Rong-En Fan > Sender: owner-freebsd-mobile@freebsd.org > > On Thu, 03 Mar 2005 11:34:12 +0100, Jochen Gensch wrote: > > Rong-En Fan schrieb: > > > > > I use 3/3's current with this patch on IBM TP X31. I can now successfully > > > suspend/resume in X with dri enable on RADEON! (can't do that before, with > > > dri, after resume screen mess up). reset_video 0 or 1 both works. It even > > > works without vesa module loaded. The only problem is that my tracepoint > > > (psm0) dead after resume. > > > > On my Thinkpad A30p I was able to reactivate my trackpoint after resume > > by setting hint.psm.0.flags="0x6000" in /boot/device.hints. > > > > Could you tell me more about you resume issues? I have a Radeon Mobility > > as well an my backlight does not turn off, when going to suspend nuder a > > normal CURRENT. Did you also use that DPMS patch posted here a while > > ago, or did you only use that vesa patch? > > > > No other modifications, any sysctls...? > > I have vesa patch and no dpms patch. backlight is not off in suspend. > The DPMS patch works ago, but it does not work for a few months. > It is said that you can use xset dpms force off to turn off backlight, > but i never tried that. > > no other modifications, hw.acpi.reset_video is 0, but 1 also works > for me. The DPMS patch is still working for me (although I had to update it for changes to acpi_video.c). -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 06:00:46 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A56F16A4CE for ; Fri, 4 Mar 2005 06:00:46 +0000 (GMT) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E61543D2F for ; Fri, 4 Mar 2005 06:00:45 +0000 (GMT) (envelope-from freebsd-mobile@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1D75mg-0008Iy-Ka for freebsd-mobile@freebsd.org; Fri, 04 Mar 2005 06:55:34 +0100 Received: from jesse.guardiani.us ([216.64.98.233]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 04 Mar 2005 06:55:34 +0100 Received: from jesse by jesse.guardiani.us with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 04 Mar 2005 06:55:34 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-mobile@freebsd.org From: Jesse Guardiani Date: Fri, 04 Mar 2005 13:01:21 -0500 Organization: WingNET Lines: 27 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: jesse.guardiani.us User-Agent: KNode/0.8.2 X-Mail-Copies-To: never Sender: news X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner: Found to be clean X-MailScanner-From: freebsd-mobile@m.gmane.org X-MailScanner-To: freebsd-mobile@freebsd.org Subject: Thinkpad Thermals X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 06:00:46 -0000 Howdy! My IBM Thinkpad A30p's ATI video chip got cooked last year, leaving me with an unreadable screen full of artifacts. I finally bought a replacement mobo a few days ago and installed it this evening. It's now running artifact free! Yay! Anyway, I'm no longer running FreeBSD on this laptop. I'm currently running Gentoo Linux. But it would be trivial to switch back if needed. I'm using gkrellm under linux to monitor my CPU temp, and I'm noticing that it runs quite hot. The fan doesn't kick in until the CPU hits 80C! That's a little too close for comfort, IMO. I think I remember seeing other posts from Thinkpad users mentioning high temps under ACPI. Has anyone found a way to cool these things down? -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 07:16:32 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBDC316A4CE for ; Fri, 4 Mar 2005 07:16:32 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6087E43D46 for ; Fri, 4 Mar 2005 07:16:32 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so753261wra for ; Thu, 03 Mar 2005 23:16:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=mmfX8lYxeF/mqe7m0XsAq9LTnZsdYr1KM3U63Pdws2QU13F5NNkfNUlV1t3pAjgrt0JS3FCDIGgh2OW208KlZ2p71qYVN89GkgE7Jbau5DfurOVGH+7oEihZU2I4pvsUHNQ+MfHJ5ZBjL5SKwwjEvmTCynP+RtZbCFEdsl36Wnw= Received: by 10.54.66.14 with SMTP id o14mr145204wra; Thu, 03 Mar 2005 23:16:29 -0800 (PST) Received: by 10.54.7.56 with HTTP; Thu, 3 Mar 2005 23:16:29 -0800 (PST) Message-ID: <6eb82e05030323162deb6113@mail.gmail.com> Date: Fri, 4 Mar 2005 15:16:29 +0800 From: Rong-En Fan To: Kevin Oberman In-Reply-To: <20050303205757.4B8935D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <6eb82e05030305552d4481fb@mail.gmail.com> <20050303205757.4B8935D07@ptavv.es.net> cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Rong-En Fan List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 07:16:32 -0000 On Thu, 03 Mar 2005 12:57:57 -0800, Kevin Oberman wrote: > The DPMS patch is still working for me (although I had to update it for > changes to acpi_video.c). Hmm, I just tried it again. It did turn off backlight but my lcd does not come back after resuming, hw.acpi_reset_video does not help. BTW, I want dri in my X, so I can't load acpi_video :-) rafan. From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 08:40:32 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 983F316A4CE for ; Fri, 4 Mar 2005 08:40:32 +0000 (GMT) Received: from mailgw.dgrp.sk (mailgw.dgrp.sk [195.28.127.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6703343D53 for ; Fri, 4 Mar 2005 08:40:31 +0000 (GMT) (envelope-from lk@tempest.sk) Received: by mailgw.dgrp.sk (Postfix, from userid 1003) id EE25E34A5A8; Fri, 4 Mar 2005 09:40:29 +0100 (CET) Received: from webmail.tempest.sk (unknown [195.28.100.38]) by mailgw.dgrp.sk (Postfix) with ESMTP id 0CA0134A5A7 for ; Fri, 4 Mar 2005 09:40:27 +0100 (CET) Received: from lk.tempest.sk ([195.28.109.47]) by webmail.tempest.sk (Lotus Domino Release 6.5.2) with ESMTP id 2005030409402685-162 ; Fri, 4 Mar 2005 09:40:26 +0100 Received: from lk.tempest.sk (localhost [127.0.0.1]) by lk.tempest.sk (8.13.1/8.12.9) with ESMTP id j248eHgu052642; Fri, 4 Mar 2005 09:40:17 +0100 (CET) (envelope-from koren@lk.tempest.sk) Received: (from koren@localhost) by lk.tempest.sk (8.13.1/8.13.1/Submit) id j248eH1l052639; Fri, 4 Mar 2005 09:40:17 +0100 (CET) (envelope-from koren) Date: Fri, 4 Mar 2005 09:40:17 +0100 (CET) Message-Id: <200503040840.j248eH1l052639@lk.tempest.sk> From: Ludo Koren To: freebsd-mobile@freebsd.org X-MIMETrack: Itemize by SMTP Server on Domino1/DGRP(Release 6.5.2|June 01, 2004) at 04.03.2005 09:40:26, Serialize by Router on Domino1/DGRP(Release 6.5.2|June 01, 2004) at 04.03.2005 09:40:27, Serialize complete at 04.03.2005 09:40:27 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mailgw X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.2 Subject: Dell Latitude D600 (again) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 08:40:32 -0000 Hi, I've finally got Dell Latitude D600 and installed FreeBSD 5.4-PRERELEASE. I am not able to make working of internal modem and wireless network card. pciconf -lv shows: .... none0@pci0:31:6: class=0x070300 card=0x542214f1 chip=0x24c68086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller' class = simple comms ..... none2@pci2:3:0: class=0x028000 card=0x27228086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class = network I've seen in the freebsd-current mailing list, the PRO/Wireless 2200BG Network Connection was recognized as ndis. So when I make # cd /usr/src/sys/modules/if_ndis/ # ndiscvt -s w22n51.sys -o ndis_driver_data.h # make Warning: Object directory not changed from original /usr/src/sys/modules/if_ndis @ -> /usr/src/sys machine -> /usr/src/sys/i386/include touch opt_bdg.h awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h awk -f @/tools/makeobjops.awk @/dev/pccard/card_if.m -h awk -f @/tools/pccarddevs2h.awk @/dev/pccard/pccarddevs cc -O -pipe -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/contrib/altq -I@/../include -I/usr/include -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c cc -O -pipe -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/contrib/altq -I@/../include -I/usr/include -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis_pci.c In file included from /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis_pci.c:65: ./ndis_driver_data.h:13: error: syntax error before '}' token *** Error code 1 Stop in /usr/src/sys/modules/if_ndis. # I suppose, there is a problem in correct generation of header file, so I changed the following lines: *** wnc.h Thu Mar 3 21:47:41 2005 --- ndis_driver_data.h Fri Mar 4 09:22:27 2005 *************** *** 9,16 **** #ifdef NDIS_REGVALS ndis_cfg ndis_regvals[] = { { NULL, NULL, { 0 }, 0 } - }; #endif /* NDIS_REGVALS */ #ifdef NDIS_IMAGE --- 9,16 ---- #ifdef NDIS_REGVALS ndis_cfg ndis_regvals[] = { { NULL, NULL, { 0 }, 0 } #endif /* NDIS_REGVALS */ + }; #ifdef NDIS_IMAGE After successful compiling and installing of if_ndis module and doing: # kldload ndis # kldload if_ndis kldload: can't load if_ndis: No such file or directory # and in the /var/log/messages: .... Mar 4 09:29:38 lk107 kernel: link_elf: symbol windrv_load undefined .... The internal modem is not recognized after doing: # /usr/local/etc/rc.d/ltmdm.sh start Enabling ltmdm. eval: cannot create /dev/cual0: Operation not supported # If I try to build ndis module for the internal modem, I have the same result as with wireless card. Could anybody help solve the problems with both the internal modem and wireless card? Any hints appreciated. Thank you very much in advance. Regards, lk From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 11:01:03 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B513C16A4CE for ; Fri, 4 Mar 2005 11:01:03 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id AB12243D3F for ; Fri, 4 Mar 2005 11:01:02 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail invoked by alias); 04 Mar 2005 11:01:01 -0000 Received: from pD9E6FF8D.dip.t-dialin.net (EHLO ms.homeip.net) (217.230.255.141) by mail.gmx.net (mp007) with SMTP; 04 Mar 2005 12:01:01 +0100 X-Authenticated: #15946415 Received: from [10.0.0.1] (helo=[10.0.0.13]) by ms.homeip.net with esmtpsa (TLSv1:AES256-SHA:256) id 1D7AbK-000NiP-G2; Fri, 04 Mar 2005 12:04:10 +0100 Message-ID: <42283FEA.9090201@gmx.de> Date: Fri, 04 Mar 2005 12:00:58 +0100 From: Jochen Gensch User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20050303205757.4B8935D07@ptavv.es.net> In-Reply-To: <20050303205757.4B8935D07@ptavv.es.net> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 11:01:03 -0000 Kevin Oberman schrieb: > The DPMS patch is still working for me (although I had to update it for > changes to acpi_video.c). Didn't work for me at any time. Display is screwed when I resume, even without radeon module... damn I'd love to have a working S3 state. Jochen From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 13:59:19 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFF5B16A542 for ; Fri, 4 Mar 2005 13:59:18 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id BC36143D5C for ; Fri, 4 Mar 2005 13:59:17 +0000 (GMT) (envelope-from ph.schulz@gmx.de) Received: (qmail invoked by alias); 04 Mar 2005 13:59:16 -0000 Received: from dsl-084-056-231-166.arcor-ip.net (EHLO [192.168.1.4]) (84.56.231.166) by mail.gmx.net (mp025) with SMTP; 04 Mar 2005 14:59:16 +0100 X-Authenticated: #1954550 Message-ID: <42286A05.8050800@gmx.de> Date: Fri, 04 Mar 2005 15:00:37 +0100 From: Phil Schulz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041217 X-Accept-Language: de, en-us, en MIME-Version: 1.0 To: Pablo Allietti References: <20050302221736.GA5378@omega.lacnic.net.uy> In-Reply-To: <20050302221736.GA5378@omega.lacnic.net.uy> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 cc: freebsd-mobile@freebsd.org Subject: Re: ndiswrapper X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 13:59:19 -0000 On 03/02/05 23:17, Pablo Allietti wrote: > hi all again. :) > > i have a problem to install ndiswrapper any body have a port for that? > or any instruction to make this package? > There is no port since it is included in the base system since FreeBSD 5.3 For details see ndis(4) and ndiscvt(8). Regards, Phil. From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 15:37:34 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B593016A4CE for ; Fri, 4 Mar 2005 15:37:34 +0000 (GMT) Received: from mbc.edu (mail.mbc.edu [216.57.240.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 131C543D1F for ; Fri, 4 Mar 2005 15:37:32 +0000 (GMT) (envelope-from ckleski@mbc.edu) Received: from [10.0.1.129] by mbc.edu (Cipher TLSv1:RC4-MD5:128) (MDaemon.PRO.v8.0.0f.R) with ESMTP id md50000007090.msg for ; Fri, 04 Mar 2005 10:36:36 -0500 From: ckleski@mbc.edu To: freebsd-mobile@freebsd.org Date: Fri, 4 Mar 2005 10:37:34 +0000 User-Agent: KMail/1.7.2 References: <200503040840.j248eH1l052639@lk.tempest.sk> In-Reply-To: <200503040840.j248eH1l052639@lk.tempest.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503041037.35168.ckleski@mbc.edu> X-SortMonster-MessageSniffer-Message: md50000007090.msg X-SortMonster-MessageSniffer-Rules: tgibseut-MDPv0.53b (SNFv2-3.1i2) No patterns matched. X-SortMonster-MessageSniffer-Result: 0 X-Authenticated-Sender: ckleski@mbc.edu X-Spam-Processed: mail.mbc.edu, Fri, 04 Mar 2005 10:36:36 -0500 (not processed: message from trusted or authenticated source) X-Lookup-Warning: HELO/EHLO lookup on 10.0.1.129 does not match 216.12.19.185 X-MDRemoteIP: 216.12.19.185 X-Return-Path: ckleski@mbc.edu X-MDaemon-Deliver-To: freebsd-mobile@freebsd.org X-MDAV-Processed: mail.mbc.edu, Fri, 04 Mar 2005 10:36:37 -0500 Subject: Re: Dell Latitude D600 (again) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 15:37:34 -0000 Drivers for the 2200 for FreeBSD are available at http://damien.bergamini.free.fr/ipw/index.html I am using the 2100 driver, and it works perfectly. Regards, Craig On Friday 04 March 2005 08:40 am, Ludo Koren wrote: > Hi, > > I've finally got Dell Latitude D600 and installed FreeBSD > 5.4-PRERELEASE. I am not able to make working of internal modem and > wireless network card. > > pciconf -lv shows: > > .... > none0@pci0:31:6: class=0x070300 card=0x542214f1 chip=0x24c68086 > rev=0x01 hdr=0x00 vendor = 'Intel Corporation' > device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem > Controller' class = simple comms > ..... > none2@pci2:3:0: class=0x028000 card=0x27228086 chip=0x42208086 rev=0x05 > hdr=0x00 vendor = 'Intel Corporation' > device = 'PRO/Wireless 2200BG Network Connection' > class = network > > > I've seen in the freebsd-current mailing list, the PRO/Wireless 2200BG > Network Connection was recognized as ndis. > > So when I make > # cd /usr/src/sys/modules/if_ndis/ > # ndiscvt -s w22n51.sys -o ndis_driver_data.h > # make > Warning: Object directory not changed from original > /usr/src/sys/modules/if_ndis @ -> /usr/src/sys > machine -> /usr/src/sys/i386/include > touch opt_bdg.h > awk -f @/tools/makeobjops.awk @/kern/device_if.m -h > awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h > awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h > awk -f @/tools/makeobjops.awk @/dev/pccard/card_if.m -h > awk -f @/tools/pccarddevs2h.awk @/dev/pccard/pccarddevs > cc -O -pipe -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I@ > -I@/contrib/altq -I@/../include -I/usr/include -finline-limit=8000 > -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 > -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -std=c99 -c > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c cc -O -pipe > -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/contrib/altq > -I@/../include -I/usr/include -finline-limit=8000 -fno-common > -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -std=c99 -c > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis_pci.c In file > included from > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis_pci.c:65: > ./ndis_driver_data.h:13: error: syntax error before '}' token > *** Error code 1 > > Stop in /usr/src/sys/modules/if_ndis. > # > > I suppose, there is a problem in correct generation of header file, so > I changed the following lines: > > > *** wnc.h Thu Mar 3 21:47:41 2005 > --- ndis_driver_data.h Fri Mar 4 09:22:27 2005 > *************** > *** 9,16 **** > #ifdef NDIS_REGVALS > ndis_cfg ndis_regvals[] = { > { NULL, NULL, { 0 }, 0 } > - }; > #endif /* NDIS_REGVALS */ > > > #ifdef NDIS_IMAGE > --- 9,16 ---- > #ifdef NDIS_REGVALS > ndis_cfg ndis_regvals[] = { > { NULL, NULL, { 0 }, 0 } > #endif /* NDIS_REGVALS */ > + }; > > > #ifdef NDIS_IMAGE > > > After successful compiling and installing of if_ndis module and doing: > > # kldload ndis > # kldload if_ndis > kldload: can't load if_ndis: No such file or directory > # > > and in the /var/log/messages: > .... > Mar 4 09:29:38 lk107 kernel: link_elf: symbol windrv_load undefined > .... > > The internal modem is not recognized after doing: > # /usr/local/etc/rc.d/ltmdm.sh start > Enabling ltmdm. > eval: cannot create /dev/cual0: Operation not supported > # > > If I try to build ndis module for the internal modem, I have the same > result as with wireless card. > > Could anybody help solve the problems with both the internal modem and > wireless card? Any hints appreciated. > > Thank you very much in advance. > > Regards, > lk > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 16:36:25 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF7C816A5B1 for ; Fri, 4 Mar 2005 16:36:25 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A55343D31 for ; Fri, 4 Mar 2005 16:36:25 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Fri, 04 Mar 2005 08:36:25 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 04DAC5D07; Fri, 4 Mar 2005 08:36:24 -0800 (PST) To: Jochen Gensch In-reply-to: Your message of "Fri, 04 Mar 2005 12:00:58 +0100." <42283FEA.9090201@gmx.de> Date: Fri, 04 Mar 2005 08:36:24 -0800 From: "Kevin Oberman" Message-Id: <20050304163624.04DAC5D07@ptavv.es.net> cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 16:36:25 -0000 > Date: Fri, 04 Mar 2005 12:00:58 +0100 > From: Jochen Gensch > > Kevin Oberman schrieb: > > > The DPMS patch is still working for me (although I had to update it for > > changes to acpi_video.c). > > Didn't work for me at any time. Display is screwed when I resume, even > without radeon module... damn I'd love to have a working S3 state. What version of X and what version of FreeBSD are you running? Which Radeon are you using? Are you running DRI? If you are running DRI, I have no suggestions. I have seen one report claiming to have DRI and S3 working, but I have never had any luck. I am running current and X.org 6.8.1. on yesterday's current with a Radeon M7. I need to put both: hw.acpi.reset_video=0 hw.syscons.sc_no_suspend_vtswitch=1 into /etc/sysctl.conf to make this work. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 18:22:15 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84A1516A4CE for ; Fri, 4 Mar 2005 18:22:15 +0000 (GMT) Received: from mailhost.m5p.com (209-162-215-52.dq1sn.easystreet.com [209.162.215.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA7C443D31 for ; Fri, 4 Mar 2005 18:22:14 +0000 (GMT) (envelope-from george@m5p.com) Received: from m5p.com (ssh.m5p.com [IPv6:2001:418:3fd::fb]) by mailhost.m5p.com (8.13.2/8.13.2) with ESMTP id j24IMEEe097837 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=OK) for ; Fri, 4 Mar 2005 10:22:14 -0800 (PST) Received: (from george@localhost) by m5p.com (8.13.2/8.13.2/Submit) id j24IKjoq048977; Fri, 4 Mar 2005 10:20:45 -0800 (PST) Date: Fri, 4 Mar 2005 10:20:45 -0800 (PST) Message-Id: <200503041820.j24IKjoq048977@m5p.com> From: george+freebsd@m5p.com To: freebsd-mobile@freebsd.org X-Scanned-By: MIMEDefang 2.49 on IPv6:2001:418:3fd::f7 Subject: Any experience with Via Gigapro? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 18:22:15 -0000 Does anyone have any experience to report with laptops with a VIA Gigapro CPU? Fry's has one on sale at $400 under their "Great Quality" house brand, which doesn't show up on the FreeBSD Laptop Compatability list. -- George Mitchell From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 18:42:05 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C20F816A4CE for ; Fri, 4 Mar 2005 18:42:05 +0000 (GMT) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEE8E43D4C for ; Fri, 4 Mar 2005 18:42:04 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j24Ig3Pu077838; Fri, 4 Mar 2005 12:42:03 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4228ABFC.3000405@centtech.com> Date: Fri, 04 Mar 2005 12:42:04 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: george+freebsd@m5p.com References: <200503041820.j24IKjoq048977@m5p.com> In-Reply-To: <200503041820.j24IKjoq048977@m5p.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/746/Fri Mar 4 06:04:27 2005 on mh1.centtech.com X-Virus-Status: Clean cc: freebsd-mobile@freebsd.org Subject: Re: Any experience with Via Gigapro? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 18:42:05 -0000 george+freebsd@m5p.com wrote: > Does anyone have any experience to report with laptops with a VIA Gigapro > CPU? Fry's has one on sale at $400 under their "Great Quality" house > brand, which doesn't show up on the FreeBSD Laptop Compatability list. The Gigapro processors are VIA CPU's - work fine.. As far as extra abilities of the laptop itself, I can't recall. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology I have seen the future and it is just like the present, only longer. ------------------------------------------------------------------------ From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 18:43:56 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3416A16A4CE for ; Fri, 4 Mar 2005 18:43:56 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BD5243D1D for ; Fri, 4 Mar 2005 18:43:55 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Fri, 04 Mar 2005 10:43:54 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 9A3B65D07; Fri, 4 Mar 2005 10:43:53 -0800 (PST) To: jesse@wingnet.net In-reply-to: Your message of "Fri, 04 Mar 2005 13:01:21 EST." Date: Fri, 04 Mar 2005 10:43:53 -0800 From: "Kevin Oberman" Message-Id: <20050304184353.9A3B65D07@ptavv.es.net> cc: freebsd-mobile@freebsd.org Subject: Re: Thinkpad Thermals X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 18:43:56 -0000 > From: Jesse Guardiani > Date: Fri, 04 Mar 2005 13:01:21 -0500 > Sender: owner-freebsd-mobile@freebsd.org > > Howdy! > > My IBM Thinkpad A30p's ATI video chip got cooked last year, > leaving me with an unreadable screen full of artifacts. I > finally bought a replacement mobo a few days ago and installed > it this evening. It's now running artifact free! Yay! > > Anyway, I'm no longer running FreeBSD on this laptop. I'm > currently running Gentoo Linux. But it would be trivial > to switch back if needed. > > I'm using gkrellm under linux to monitor my CPU temp, and > I'm noticing that it runs quite hot. The fan doesn't kick > in until the CPU hits 80C! That's a little too close for > comfort, IMO. > > I think I remember seeing other posts from Thinkpad users > mentioning high temps under ACPI. Has anyone found a way > to cool these things down? Jesse, Is it running at or near 80C when idle, when in typical use, or when building something BIG (CPU running at >95% for minutes). I believe that the A30p is a P4-M CPU. It will turn itself off (hard, like a power cut-off) before the CPU dies, but that is NOT a good thing. That does not happen until the CPU reaches a frightening 135C. If you are running 5-Stable or 6-Current you should load cpufreq and acpi_perf. These will give you a large number of CPU "frequencies" visible in dev.cpu.0 and settable in dev.cpu.0.freq. This provides fine-grained control. Yo can also look at hw.acpi.0.thermal for _PSV and _CRT. _PSV is the temperature at which the CPU should start to slow down to moderate the temperature. _CRT is the point at which alarms are sounded and the OS should start a clean shutdown. If there is no cooling problem _PSV should keep the temperature from ever reaching _CRT. You will note that these temperatures are WAY under 135C, but the 135C cutoff is intended for catastrophic failures (like a broken/improperly installed heat sink) and assumes that the temperature rose very quickly. It is not intended that the CPU should run at that sort of temperature normally. FreeBSD is still working on support for all of this, but it's getting much closer. The addition of powerd to Current is a big step, but it is probably not quite ready for prime time and is disabled by default. Nate just committed it to current a few days ago and I just installed it yesterday, so I have no experience with it. Bottom line is that as long as the temperature stays below _PSV under heavy load, you should not be concerned. If it exceeds _PSV for very long, you might want to reduce dev.cpu.0.freq a bit. If you ever hit _CRT, dow something quickly. FWIW, my system has _PSV at 86.5C and _CRT at 94.0C, so 80C is really not that hot, though my thigh does not agree when my laptop is literally on my lap. As always, I am not really an expert on all of this and I can hope that Nate or someone else will correct any errors in this. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 22:18:37 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 779D616A4CE for ; Fri, 4 Mar 2005 22:18:37 +0000 (GMT) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 409F943D53 for ; Fri, 4 Mar 2005 22:18:36 +0000 (GMT) (envelope-from freebsd-mobile@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1D7Ky0-00082f-T5 for freebsd-mobile@freebsd.org; Fri, 04 Mar 2005 23:08:18 +0100 Received: from office.wingnet.net ([216.64.98.250]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 04 Mar 2005 23:08:16 +0100 Received: from jesse by office.wingnet.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 04 Mar 2005 23:08:16 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-mobile@freebsd.org From: Jesse Guardiani Date: Fri, 04 Mar 2005 05:09:46 -0500 Organization: WingNET Lines: 111 Message-ID: References: <20050304184353.9A3B65D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: office.wingnet.net User-Agent: KNode/0.8.2 X-Mail-Copies-To: never Sender: news X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner: Found to be clean X-MailScanner-From: freebsd-mobile@m.gmane.org X-MailScanner-To: freebsd-mobile@freebsd.org Subject: Re: Thinkpad Thermals X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 22:18:37 -0000 Kevin Oberman wrote: >> From: Jesse Guardiani >> Date: Fri, 04 Mar 2005 13:01:21 -0500 >> Sender: owner-freebsd-mobile@freebsd.org >> >> Howdy! >> >> My IBM Thinkpad A30p's ATI video chip got cooked last year, >> leaving me with an unreadable screen full of artifacts. I >> finally bought a replacement mobo a few days ago and installed >> it this evening. It's now running artifact free! Yay! >> >> Anyway, I'm no longer running FreeBSD on this laptop. I'm >> currently running Gentoo Linux. But it would be trivial >> to switch back if needed. >> >> I'm using gkrellm under linux to monitor my CPU temp, and >> I'm noticing that it runs quite hot. The fan doesn't kick >> in until the CPU hits 80C! That's a little too close for >> comfort, IMO. >> >> I think I remember seeing other posts from Thinkpad users >> mentioning high temps under ACPI. Has anyone found a way >> to cool these things down? > > Jesse, > > Is it running at or near 80C when idle, when in typical use, or when > building something BIG (CPU running at >95% for minutes). More or less idle. It fluctuates between 70C and 80C. Just playing an MP3 I'm at 77C right now. Is this normal acceptable temp for a thinkpad? Or should I be targeting the 40C range like I do with my desktop machines? > I believe that the A30p is a P4-M CPU. It will turn itself off (hard, > like a power cut-off) before the CPU dies, but that is NOT a good > thing. That does not happen until the CPU reaches a frightening 135C. Actually, I think mine is a P3-M at 1.2ghz. It uses PC133 SODIMMs, and /proc/cpuinfo reveals this: Intel(R) Pentium(R) III Mobile CPU 1200MHz I think it's the A31p that uses a P4-M. > If you are running 5-Stable or 6-Current you should load cpufreq and > acpi_perf. These will give you a large number of CPU "frequencies" > visible in dev.cpu.0 and settable in dev.cpu.0.freq. This provides > fine-grained control. I asked this question here mostly because I know a lot of people on this list run Thinkpads, and I remember more than one complaining about cooling issues. Again, I no longer run FreeBSD on this laptop. I run Gentoo. Linux has various different daemons capable of throttling the CPU though, and I currently have an "on-battery" runlevel setup that runs the speedfreq daemon with a preference for "powersave". I could install something in my default "on-AC" runlevel that regulates CPU based on load even when on AC... But... is 80C normal under load? Running a frequency daemon won't change the under-load temp unless I cap the horsepower or introduce some sort of temp related frequency feedback control as you describe below. Hmmm... well that's interesting: Just to test it out, I unplugged the AC and ran it for a while, still playing the same MP3. It leveled out at 66C in the "powersave" profile, which means that the CPU is running at just 799.457mhz instead of 1199.185mhz (performance). Is 66C acceptable temp for a laptop? It's definitely a better temp, but It would really stink if my 1.2ghz had to be run at just 800mhz all the time to avoid cooking things. > Yo can also look at hw.acpi.0.thermal for _PSV and _CRT. _PSV is the > temperature at which the CPU should start to slow down to moderate the > temperature. _CRT is the point at which alarms are sounded and the OS > should start a clean shutdown. If there is no cooling problem _PSV > should keep the temperature from ever reaching _CRT. You will note that > these temperatures are WAY under 135C, but the 135C cutoff is intended > for catastrophic failures (like a broken/improperly installed heat sink) > and assumes that the temperature rose very quickly. It is not intended > that the CPU should run at that sort of temperature normally. > > FreeBSD is still working on support for all of this, but it's getting > much closer. The addition of powerd to Current is a big step, but it is > probably not quite ready for prime time and is disabled by default. Nate > just committed it to current a few days ago and I just installed it > yesterday, so I have no experience with it. > > Bottom line is that as long as the temperature stays below _PSV under > heavy load, you should not be concerned. If it exceeds _PSV for very > long, you might want to reduce dev.cpu.0.freq a bit. If you ever hit > _CRT, dow something quickly. FWIW, my system has _PSV at 86.5C and _CRT > at 94.0C, so 80C is really not that hot, though my thigh does not agree > when my laptop is literally on my lap. > > As always, I am not really an expert on all of this and I can hope that > Nate or someone else will correct any errors in this. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 22:36:31 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7B4816A4CE for ; Fri, 4 Mar 2005 22:36:31 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E22343D2F for ; Fri, 4 Mar 2005 22:36:31 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Fri, 04 Mar 2005 14:36:30 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 1CCD15D07; Fri, 4 Mar 2005 14:36:30 -0800 (PST) To: jesse@wingnet.net In-reply-to: Your message of "Fri, 04 Mar 2005 05:09:46 EST." Date: Fri, 04 Mar 2005 14:36:30 -0800 From: "Kevin Oberman" Message-Id: <20050304223630.1CCD15D07@ptavv.es.net> cc: freebsd-mobile@freebsd.org Subject: Re: Thinkpad Thermals X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 22:36:31 -0000 > From: Jesse Guardiani > Date: Fri, 04 Mar 2005 05:09:46 -0500 > Sender: owner-freebsd-mobile@freebsd.org > > Kevin Oberman wrote: > > >> From: Jesse Guardiani > >> Date: Fri, 04 Mar 2005 13:01:21 -0500 > >> Sender: owner-freebsd-mobile@freebsd.org > >> > >> Howdy! > >> > >> My IBM Thinkpad A30p's ATI video chip got cooked last year, > >> leaving me with an unreadable screen full of artifacts. I > >> finally bought a replacement mobo a few days ago and installed > >> it this evening. It's now running artifact free! Yay! > >> > >> Anyway, I'm no longer running FreeBSD on this laptop. I'm > >> currently running Gentoo Linux. But it would be trivial > >> to switch back if needed. > >> > >> I'm using gkrellm under linux to monitor my CPU temp, and > >> I'm noticing that it runs quite hot. The fan doesn't kick > >> in until the CPU hits 80C! That's a little too close for > >> comfort, IMO. > >> > >> I think I remember seeing other posts from Thinkpad users > >> mentioning high temps under ACPI. Has anyone found a way > >> to cool these things down? > > > > Jesse, > > > > Is it running at or near 80C when idle, when in typical use, or when > > building something BIG (CPU running at >95% for minutes). > > More or less idle. It fluctuates between 70C and 80C. Just playing an > MP3 I'm at 77C right now. Is this normal acceptable temp for a thinkpad? > Or should I be targeting the 40C range like I do with my desktop machines? > Acceptable? I suspect it is, although it seems a bit warm to me, too. My T30 idles at about 48C and playing MP3s pushes it up about 5 degrees, so your's is running a bit hotter than mine. Laptop CPUs almost always run hotter than desktop systems. Just think about the fans and the big heat sink on the CPU. Your laptop has no space for things like that. P4s are especially bad and P4-Ms are just a bit better. The newer P-Ms (often call Centrino) do MUCH better, but their internals are very different from the P4..probably more like a P3. Getting heat out of a laptop is a real problem. > > > I believe that the A30p is a P4-M CPU. It will turn itself off (hard, > > like a power cut-off) before the CPU dies, but that is NOT a good > > thing. That does not happen until the CPU reaches a frightening 135C. > > Actually, I think mine is a P3-M at 1.2ghz. It uses PC133 SODIMMs, and > /proc/cpuinfo reveals this: > > Intel(R) Pentium(R) III Mobile CPU 1200MHz > > I think it's the A31p that uses a P4-M. Sorry. The P3s generally run much cooler than the P4s. Is your fan running? It should be at those temperatures. It's under BIOS control in my T30, but you would have to dump your ACPI tables to see if there is any fan control available. > > If you are running 5-Stable or 6-Current you should load cpufreq and > > acpi_perf. These will give you a large number of CPU "frequencies" > > visible in dev.cpu.0 and settable in dev.cpu.0.freq. This provides > > fine-grained control. > > I asked this question here mostly because I know a lot of people on this > list run Thinkpads, and I remember more than one complaining about cooling > issues. > > Again, I no longer run FreeBSD on this laptop. I run Gentoo. Linux has > various different daemons capable of throttling the CPU though, and I > currently have an "on-battery" runlevel setup that runs the speedfreq > daemon with a preference for "powersave". I could install something in > my default "on-AC" runlevel that regulates CPU based on load even when > on AC... > > But... is 80C normal under load? Running a frequency daemon won't change > the under-load temp unless I cap the horsepower or introduce some sort > of temp related frequency feedback control as you describe below. > > Hmmm... well that's interesting: Just to test it out, I unplugged the > AC and ran it for a while, still playing the same MP3. It leveled out > at 66C in the "powersave" profile, which means that the CPU is running > at just 799.457mhz instead of 1199.185mhz (performance). > > Is 66C acceptable temp for a laptop? It's definitely a better temp, but > It would really stink if my 1.2ghz had to be run at just 800mhz all the > time to avoid cooking things. Once again, I can't define "acceptable". It is not so hot as to be frightening, but it does sound like it's running warmer than I would expect. Dust? Blocked air intake/outlet? Those can real impact thermals. And, of course, fan problems can be a big issue. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 4 23:08:14 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2068216A4CE for ; Fri, 4 Mar 2005 23:08:14 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id B587143D48 for ; Fri, 4 Mar 2005 23:08:12 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j24N89U9050396; Sat, 5 Mar 2005 00:08:10 +0100 (CET) (envelope-from mime@traveller.cz) From: Michal Mertl To: jesse@wingnet.net In-Reply-To: References: <20050304184353.9A3B65D07@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-2 Date: Sat, 05 Mar 2005 00:08:08 +0100 Message-Id: <1109977688.1073.38.camel@genius2.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit cc: freebsd-mobile@freebsd.org Subject: Re: Thinkpad Thermals X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 23:08:14 -0000 Before finishing my email a new one from Mr. Oberman came and said most of what I'm about to post, but here it is, anyway... Jesse Guardiani píše v pá 04. 03. 2005 v 05:09 -0500: > Kevin Oberman wrote: > > >> From: Jesse Guardiani > >> Date: Fri, 04 Mar 2005 13:01:21 -0500 > >> Sender: owner-freebsd-mobile@freebsd.org > >> > >> Howdy! > >> > >> My IBM Thinkpad A30p's ATI video chip got cooked last year, > >> leaving me with an unreadable screen full of artifacts. I > >> finally bought a replacement mobo a few days ago and installed > >> it this evening. It's now running artifact free! Yay! > >> > >> Anyway, I'm no longer running FreeBSD on this laptop. I'm > >> currently running Gentoo Linux. But it would be trivial > >> to switch back if needed. > >> > >> I'm using gkrellm under linux to monitor my CPU temp, and > >> I'm noticing that it runs quite hot. The fan doesn't kick > >> in until the CPU hits 80C! That's a little too close for > >> comfort, IMO. > >> > >> I think I remember seeing other posts from Thinkpad users > >> mentioning high temps under ACPI. Has anyone found a way > >> to cool these things down? > > > > Jesse, > > > > Is it running at or near 80C when idle, when in typical use, or when > > building something BIG (CPU running at >95% for minutes). > > More or less idle. It fluctuates between 70C and 80C. Just playing an > MP3 I'm at 77C right now. Is this normal acceptable temp for a thinkpad? > Or should I be targeting the 40C range like I do with my desktop machines? > > > > I believe that the A30p is a P4-M CPU. It will turn itself off (hard, > > like a power cut-off) before the CPU dies, but that is NOT a good > > thing. That does not happen until the CPU reaches a frightening 135C. > > Actually, I think mine is a P3-M at 1.2ghz. It uses PC133 SODIMMs, and > /proc/cpuinfo reveals this: > > Intel(R) Pentium(R) III Mobile CPU 1200MHz > > I think it's the A31p that uses a P4-M. I think P4-M is something pretty different than P-M (sometimes called also P3-M). P-M is based on PentiumPro core (the basic design is the same from PP to P3) and has lots of enhancements over P3. It has rather low nominal speed (maximum is I think 2GHz) but is much faster per MHz than P4-whatever. It has two more important revisions AFAIK - the older is codenamed Banias (1MB L2 cache and 130nm manufacturing process) and the newer Dothan (2MB L2 cache at 90nm). It has been developped by rather small Intel team located in Israel. It has lots of nifty features to conserve power. P4 (NetBurst architecture) has been developped independently as the Intel future 32bit architecture (the first really new architecture after PentiumPro) and trades efficiency for MHz. It seems it's almost dead in my opinion. P-M notebooks have <=2GHz speed, weigh usually less than 3 kg (sometimes just little over 1 kg) and last at least 3 hours on battery when idle. P4-M notebooks have >2GHz, weigh more than 3 kg and last much less (1.5hrs?). My Dothan P-M (maximum 1500MHz) runs at 23MHz(!) at the moment at 40C on FreeBSD-current. It will run at little over 30C if I don't have usb and sound loaded (they prevent acpi from going to C3 or C4 (does probably something to the chipset to conserver power in addition to slowing down the CPU). > > If you are running 5-Stable or 6-Current you should load cpufreq and > > acpi_perf. These will give you a large number of CPU "frequencies" > > visible in dev.cpu.0 and settable in dev.cpu.0.freq. This provides > > fine-grained control. > > I asked this question here mostly because I know a lot of people on this > list run Thinkpads, and I remember more than one complaining about cooling > issues > > Again, I no longer run FreeBSD on this laptop. I run Gentoo. Linux has > various different daemons capable of throttling the CPU though, and I > currently have an "on-battery" runlevel setup that runs the speedfreq > daemon with a preference for "powersave". I could install something in > my default "on-AC" runlevel that regulates CPU based on load even when > on AC... > > But... is 80C normal under load? Running a frequency daemon won't change > the under-load temp unless I cap the horsepower or introduce some sort > of temp related frequency feedback control as you describe below. > > Hmmm... well that's interesting: Just to test it out, I unplugged the > AC and ran it for a while, still playing the same MP3. It leveled out > at 66C in the "powersave" profile, which means that the CPU is running > at just 799.457mhz instead of 1199.185mhz (performance). > > Is 66C acceptable temp for a laptop? It's definitely a better temp, but > It would really stink if my 1.2ghz had to be run at just 800mhz all the > time to avoid cooking things. In FreeBSD you have probably as much control over the throttling as on Gentoo, at least on current. The temperature gets rather high when doing CPU bound tasks - I've seen close to 80C on my notebook but I believe it's to be expected and it's nothing to be afraid of. There are now 5 power saving subsystems supported on my notebook - ichss, p4tcc, acpi_throttle, acpi_perf and est. Look at cpufreq(4) on current but be prepared it won't answer all your questions. > > Yo can also look at hw.acpi.0.thermal for _PSV and _CRT. _PSV is the > > temperature at which the CPU should start to slow down to moderate the > > temperature. _CRT is the point at which alarms are sounded and the OS > > should start a clean shutdown. If there is no cooling problem _PSV > > should keep the temperature from ever reaching _CRT. You will note that > > these temperatures are WAY under 135C, but the 135C cutoff is intended > > for catastrophic failures (like a broken/improperly installed heat sink) > > and assumes that the temperature rose very quickly. It is not intended > > that the CPU should run at that sort of temperature normally. > > > > FreeBSD is still working on support for all of this, but it's getting > > much closer. The addition of powerd to Current is a big step, but it is > > probably not quite ready for prime time and is disabled by default. Nate > > just committed it to current a few days ago and I just installed it > > yesterday, so I have no experience with it. > > > > Bottom line is that as long as the temperature stays below _PSV under > > heavy load, you should not be concerned. If it exceeds _PSV for very > > long, you might want to reduce dev.cpu.0.freq a bit. If you ever hit > > _CRT, dow something quickly. FWIW, my system has _PSV at 86.5C and _CRT > > at 94.0C, so 80C is really not that hot, though my thigh does not agree > > when my laptop is literally on my lap. > > > > As always, I am not really an expert on all of this and I can hope that > > Nate or someone else will correct any errors in this. Michal Mertl From owner-freebsd-mobile@FreeBSD.ORG Sat Mar 5 13:02:52 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 821F216A4CE for ; Sat, 5 Mar 2005 13:02:52 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9832843D46 for ; Sat, 5 Mar 2005 13:02:51 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so1060998wra for ; Sat, 05 Mar 2005 05:02:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=KxPfDzJEk+HFOqBFiI9BstH9Q89QsJKoNSgCEU5UX+CYx2v+K2wQjxtlhp6wLJ78DD8Gh1bJb9WF5bCMw21GjWd+F9+k1NIgitytpZztwcN7+Enc63Iny7IAeryh4s+8smp4JechPsLFz1Av7bxewPMGAweFBZpN8a37awYnIwA= Received: by 10.54.81.18 with SMTP id e18mr111850wrb; Sat, 05 Mar 2005 05:02:51 -0800 (PST) Received: by 10.54.7.56 with HTTP; Sat, 5 Mar 2005 05:02:50 -0800 (PST) Message-ID: <6eb82e050305050284084ca@mail.gmail.com> Date: Sat, 5 Mar 2005 21:02:50 +0800 From: Rong-En Fan To: Ian Dowse In-Reply-To: <6eb82e05030219447bdda412@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200502281016.aa49779@salmon.maths.tcd.ie> <200502282026.aa38504@salmon.maths.tcd.ie> <6eb82e05030219447bdda412@mail.gmail.com> cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Rong-En Fan List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2005 13:02:52 -0000 On Thu, 3 Mar 2005 11:44:59 +0800, Rong-En Fan wrote: > > so that the VESA code allows up to 8k of state storage and will > > fail if the BIOS claims to need more space. Could you try this with > > the vesa module loaded and with both 0 and 1 for hw.acpi.reset_video? > > I use 3/3's current with this patch on IBM TP X31. I can now successfully > suspend/resume in X with dri enable on RADEON! (can't do that before, with > dri, after resume screen mess up). reset_video 0 or 1 both works. It even I was wrong. drm was broken that time, after apply patch on cvs-all with dri, after resume, my screen mess up as before. rafan. > works without vesa module loaded. The only problem is that my tracepoint > (psm0) dead after resume. From owner-freebsd-mobile@FreeBSD.ORG Sat Mar 5 19:22:05 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1339C16A4CE for ; Sat, 5 Mar 2005 19:22:05 +0000 (GMT) Received: from mailhost.tao.org.uk (transwarp.tao.org.uk [212.135.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 388D143D1F for ; Sat, 5 Mar 2005 19:22:04 +0000 (GMT) (envelope-from joe@tao.org.uk) Received: from genius.tao.org.uk (genius.tao.org.uk [212.135.162.51]) by mailhost.tao.org.uk (Postfix) with ESMTP id 2ABDD76F3 for ; Sat, 5 Mar 2005 19:21:58 +0000 (GMT) Received: by genius.tao.org.uk (Postfix, from userid 100) id 4F02840B7; Sat, 5 Mar 2005 19:21:53 +0000 (GMT) Date: Sat, 5 Mar 2005 19:21:53 +0000 From: Josef Karthauser To: mobile@freebsd.org Message-ID: <20050305192153.GA20692@genius.tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline User-Agent: Mutt/1.5.8i Subject: Out of battery indicator. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2005 19:22:05 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Does anyone have a solution to running out of battery using ACPI (5.3?). I keep forgetting to plug in my power supply and the machine dies rather suddenly without beeping or giving me any warning that it was out of battery. Any ideas? I would have thought that this was an O/S task rather than a third party app task. Joe --=20 Josef Karthauser (joe@tao.org.uk) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D An eclectic mix of fact an= d theory. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkIqBtAACgkQXVIcjOaxUBbzCQCg1TKIYMDDeL7dMHhME//M4tvS cdgAoKknqme/klhMMfIE2Nfv6q5feO1r =Jsgu -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- From owner-freebsd-mobile@FreeBSD.ORG Sat Mar 5 20:59:01 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9C9B16A4CE for ; Sat, 5 Mar 2005 20:59:01 +0000 (GMT) Received: from marketvisionresearch.com (mail.marketvisionresearch.com [66.42.197.227]) by mx1.FreeBSD.org (Postfix) with SMTP id 2AF2543D5A for ; Sat, 5 Mar 2005 20:59:01 +0000 (GMT) (envelope-from mmetzger@marketvisionresearch.com) Received: from borderdo-Message_Server by marketvisionresearch.com with Novell_GroupWise; Sat, 05 Mar 2005 16:05:40 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.7.1 Beta Date: Sat, 05 Mar 2005 16:05:04 -0500 From: "Michael Metzger" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: AC'97 Modem Controller X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2005 20:59:01 -0000 I have the following modem controller in my dell laptop and was wondering = if there is any driver support for it. pciconf brings back the following: none3@pci0:31:6 class=3D0x070300 card=3D0x4d6414e4=20 chip=3D0x24c68086 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device=3D'82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller class =3D simple comms I know there is one that exists for linux, but I am not that good with = linux binary compatibility to know how to use it. It is available for my device at the following web site:=20 http://www.linuxant.com/drivers/hsf/full/downloads.php