From owner-freebsd-mobile Mon Nov 11 08:53:33 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA25359 for mobile-outgoing; Mon, 11 Nov 1996 08:53:33 -0800 (PST) Received: from tellab5.tellabs.com (tellab5.lisle.tellabs.com [138.111.243.28]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA25354 for ; Mon, 11 Nov 1996 08:53:31 -0800 (PST) From: mikebo@tellabs.com Received: from sunc210.tellabs.com by tellab5.tellabs.com with smtp (Smail3.1.29.1 #4) id m0vMzbX-0004fGC; Mon, 11 Nov 96 10:52 CST Received: by sunc210.tellabs.com (SMI-8.6/1.9) id KAA14528; Mon, 11 Nov 1996 10:52:43 -0600 Message-Id: <199611111652.KAA14528@sunc210.tellabs.com> Subject: Re: PAO-961020 for 2.2-961014-SNAP To: mobile@freebsd.org Date: Mon, 11 Nov 1996 10:52:42 -0600 (CST) Cc: mikebo (Mike Borowiec) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Previously, HOSOKAWA Tatsumi (hosokawa@mt.cs.keio.ac.jp) wrote: > PAO-961020 for 2.2-961014-SNAP is now available. > > ftp://ryukyu.mt.cs.keio.ac.jp/pub/FreeBSD/PAO/PAO-961020.tar.gz > > o relative to 2.2-961014-SNAP > o 'shutdown -x' is re-implemented by using at_shutdown() interface > o removed all kern_devconf > o fixed some minor bugs > > We want CardBus testbed, but none of us have CardBus machine... I only just discovered this list, so please bear with me... I have a Toshiba Tecra 720CDT w/48MB and a 3Com 3C589C. I recently posted to questions and hackers regarding a problem I'm having with this set up and the 'zp' driver: server /kernel: nfsd send error 55 and ping: sendto: No buffer space available. I rebuilt the server's kernel with more mbuf's, thinking this might solve it: options "NMBCLUSTERS=2048" but get the same problem... and the client must be rebooted each time. The server can be restored to "sanity" by killing all nfsd's and down-ing, then up-ing the interface (zp0). But to play it safe, both client and server were rebooted - same problem. Yesterday, Mike Smith (msmith@gsoft.com.au) wrote to me: > I think that you're discovering that the PCCARD support > in 2.1.5 sucks pretty badly. > That's an understatement... ;v) > Now, AFAIK the Tecras are cardbus machines, which means that the PCIC > in them is probably not supported by the PAO code yet. You could ask > on the freebsd-mobile mailing list (check the archives first) about > that. If you still need guinea pig for testing cardbus support, and the Tecra is indeed a cardbus machine, I'm your guy. I understand there is a new PAO support package for 2.2-961014-SNAP. I will load the 2.2-961014-SNAP today, and download the PAO package from: ftp://ryukyu.mt.cs.keio.ac.jp/pub/FreeBSD/PAO/PAO-961020.tar.gz Is there a better place to get this stuff? Anything more recent, or patched I should be sure to get? Is this on the ftp.freebsd.org site? Regards, - Mike -- -------------------------------------------------------------------------- Michael Borowiec - mikebo@tellabs.com - Tellabs Operations, Inc. Senior Member of Technical Staff 4951 Indiana Avenue, MS 63 630-512-8211 FAX: 630-512-7099 Lisle, IL 60532 USA -------------------------------------------------------------------------- From owner-freebsd-mobile Mon Nov 11 09:12:42 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA26468 for mobile-outgoing; Mon, 11 Nov 1996 09:12:42 -0800 (PST) Received: from rmsq.com (rmsq.com [204.133.95.70]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA26434; Mon, 11 Nov 1996 09:12:28 -0800 (PST) Received: (from baldrick@localhost) by rmsq.com (8.7.5/8.6.12) id KAA01102; Mon, 11 Nov 1996 10:16:58 -0700 (MST) Date: Mon, 11 Nov 1996 10:16:58 -0700 (MST) From: Just Baldrick Message-Id: <199611111716.KAA01102@rmsq.com> To: freebsd-questions@freebsd.org Subject: Problem with 2.1.5 and XFree86 3.2 on laptop Cc: freebsd-mobile@freebsd.org Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I am having trouble with the screen display on a laptop. XFree86 3.2 correctly detects the chipset, Chips & Technologies 65545, and everything works OK except that the display is 712x600 instead of 800x600. Using the option "fix_panel_size" (which does just that) the display is 800x600. However, after 4 hours or so the display goes crazy, either becoming a mess of horizontal lines or just turning black. Does anyone know why "fix_panel_size" should work perfectly at first and then crash later on? Thanks, Geoff Martindale From owner-freebsd-mobile Mon Nov 11 09:41:10 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28325 for mobile-outgoing; Mon, 11 Nov 1996 09:41:10 -0800 (PST) Received: from tahoma.cwu.edu (skynyrd@tahoma.cwu.edu [198.104.65.220]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA28320 for ; Mon, 11 Nov 1996 09:41:06 -0800 (PST) Received: by tahoma.cwu.edu; id AA08693; Mon, 11 Nov 1996 09:40:49 -0800 Date: Mon, 11 Nov 1996 09:40:49 -0800 (PST) From: Chris Timmons To: mikebo@tellabs.com Cc: mobile@freebsd.org Subject: Re: PAO-961020 for 2.2-961014-SNAP In-Reply-To: <199611111652.KAA14528@sunc210.tellabs.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The 3c589C does about the same thing in my versa 6030x p133 machine with the ep driver (via the PA0 2.2 boot floppy from early october.) Runs for a while with very slow throughput before petering out altogether. Since the same code apparently runs very well with the same 3c589C hw on slower CPUs, maybe it is one of those problems where a delay loop all of a sudden got a lot shorter :) I have the 3com docs coming and have been reading the source a bit but this may require a better hacker than I to fix. Nevertheless I'm going to give it a whack when my laptop comes back from a trip that it is on (without me :( Anybody else working on this? -Chris On Mon, 11 Nov 1996 mikebo@tellabs.com wrote: > Previously, HOSOKAWA Tatsumi (hosokawa@mt.cs.keio.ac.jp) wrote: > > PAO-961020 for 2.2-961014-SNAP is now available. > > > > ftp://ryukyu.mt.cs.keio.ac.jp/pub/FreeBSD/PAO/PAO-961020.tar.gz > > > > o relative to 2.2-961014-SNAP > > o 'shutdown -x' is re-implemented by using at_shutdown() interface > > o removed all kern_devconf > > o fixed some minor bugs > > > > We want CardBus testbed, but none of us have CardBus machine... > > I only just discovered this list, so please bear with me... > > I have a Toshiba Tecra 720CDT w/48MB and a 3Com 3C589C. I recently posted > to questions and hackers regarding a problem I'm having with this set up > and the 'zp' driver: server /kernel: nfsd send error 55 and > ping: sendto: No buffer space available. > > I rebuilt the server's kernel with more mbuf's, thinking this might > solve it: > options "NMBCLUSTERS=2048" > but get the same problem... and the client must be rebooted each time. > The server can be restored to "sanity" by killing all nfsd's and > down-ing, then up-ing the interface (zp0). But to play it safe, both > client and server were rebooted - same problem. > > Yesterday, Mike Smith (msmith@gsoft.com.au) wrote to me: > > I think that you're discovering that the PCCARD support > > in 2.1.5 sucks pretty badly. > > > That's an understatement... ;v) > > > Now, AFAIK the Tecras are cardbus machines, which means that the PCIC > > in them is probably not supported by the PAO code yet. You could ask > > on the freebsd-mobile mailing list (check the archives first) about > > that. > > If you still need guinea pig for testing cardbus support, and the Tecra > is indeed a cardbus machine, I'm your guy. I understand there is a new > PAO support package for 2.2-961014-SNAP. I will load the 2.2-961014-SNAP > today, and download the PAO package from: > ftp://ryukyu.mt.cs.keio.ac.jp/pub/FreeBSD/PAO/PAO-961020.tar.gz > > Is there a better place to get this stuff? Anything more recent, or > patched I should be sure to get? Is this on the ftp.freebsd.org site? > Regards, > - Mike > -- > -------------------------------------------------------------------------- > Michael Borowiec - mikebo@tellabs.com - Tellabs Operations, Inc. > Senior Member of Technical Staff 4951 Indiana Avenue, MS 63 > 630-512-8211 FAX: 630-512-7099 Lisle, IL 60532 USA > -------------------------------------------------------------------------- > From owner-freebsd-mobile Mon Nov 11 09:53:56 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29150 for mobile-outgoing; Mon, 11 Nov 1996 09:53:56 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29133; Mon, 11 Nov 1996 09:53:52 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA20329; Mon, 11 Nov 1996 10:53:48 -0700 (MST) Date: Mon, 11 Nov 1996 10:53:48 -0700 (MST) Message-Id: <199611111753.KAA20329@rocky.mt.sri.com> From: Nate Williams To: Just Baldrick Cc: freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: Problem with 2.1.5 and XFree86 3.2 on laptop In-Reply-To: <199611111716.KAA01102@rmsq.com> References: <199611111716.KAA01102@rmsq.com> Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am having trouble with the screen display on a > laptop. And this laptop would be....???? > XFree86 3.2 correctly detects the chipset, > Chips & Technologies 65545, and everything works > OK except that the display is 712x600 instead of > 800x600. If it's on a NEC or the HP (from the XFree86 notes) this is normal. > Using the option "fix_panel_size" (which does just that) > the display is 800x600. However, after 4 hours or so the > display goes crazy, either becoming a mess of horizontal > lines or just turning black. Hmm, this hasn't happened with my box (NEC Versa/P), but it might be an issue with the HP. > Does anyone know why "fix_panel_size" should work perfectly > at first and then crash later on? Check out this: http://www.xfree86.org/3.2/chips-4.html Nate From owner-freebsd-mobile Mon Nov 11 09:55:47 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29198 for mobile-outgoing; Mon, 11 Nov 1996 09:55:47 -0800 (PST) Received: from scruz.net (nic.scruz.net [165.227.1.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA29192 for ; Mon, 11 Nov 1996 09:55:45 -0800 (PST) Received: from osprey.grizzly.com by scruz.net (8.7.3/1.34) id JAA27846; Mon, 11 Nov 1996 09:55:41 -0800 (PST) Received: (from markd@localhost) by osprey.grizzly.com (8.7.6/8.7.3) id JAA14415; Mon, 11 Nov 1996 09:55:32 -0800 (PST) Date: Mon, 11 Nov 1996 09:55:32 -0800 (PST) Message-Id: <199611111755.JAA14415@osprey.grizzly.com> From: Mark Diekhans To: mobile@FreeBSD.org Subject: Recomendations wanted for a 28.8 modem that works well with PAO Sender: owner-mobile@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Can anyone recommend a good 28.8 modem that works well with PAO? I have given up on trying to make the cardinal I have work in anything but polled I/O mode. TIA From owner-freebsd-mobile Mon Nov 11 19:14:58 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA10651 for mobile-outgoing; Mon, 11 Nov 1996 19:14:58 -0800 (PST) Received: from rmsq.com (rmsq.com [204.133.95.70]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA10626; Mon, 11 Nov 1996 19:14:39 -0800 (PST) Received: (from baldrick@localhost) by rmsq.com (8.7.5/8.6.12) id UAA10681; Mon, 11 Nov 1996 20:19:09 -0700 (MST) Date: Mon, 11 Nov 1996 20:19:09 -0700 (MST) From: Just Baldrick Message-Id: <199611120319.UAA10681@rmsq.com> To: baldrick@rmsq.com, nate@mt.sri.com Subject: Re: Problem with 2.1.5 and XFree86 3.2 on laptop Cc: freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From nate@rocky.mt.sri.com Mon Nov 11 20:04:25 1996 To: Just Baldrick Cc: freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: Problem with 2.1.5 and XFree86 3.2 on laptop >> I am having trouble with the screen display on a >> laptop. > >And this laptop would be....???? It's a 120MHz Pentium by Bit Computers, ie a no-name machine. > >> XFree86 3.2 correctly detects the chipset, >> Chips & Technologies 65545, and everything works >> OK except that the display is 712x600 instead of >> 800x600. > >If it's on a NEC or the HP (from the XFree86 notes) this is normal. > >> Using the option "fix_panel_size" (which does just that) >> the display is 800x600. However, after 4 hours or so the >> display goes crazy, either becoming a mess of horizontal >> lines or just turning black. > I've read all the READMEs and notes on the XFree86 web site and couldn't find any answers. Looks like I'll just have to use X for only a few hours at a time. Geoff Martindale From owner-freebsd-mobile Fri Nov 15 08:36:53 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA27299 for mobile-outgoing; Fri, 15 Nov 1996 08:36:53 -0800 (PST) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA27263 for ; Fri, 15 Nov 1996 08:36:43 -0800 (PST) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id BAA21656; Sat, 16 Nov 1996 01:36:36 +0900 Date: Sat, 16 Nov 1996 01:36:36 +0900 Message-Id: <199611151636.BAA21656@frig.mt.cs.keio.ac.jp> To: mobile@freebsd.org Subject: PAO-961115 for 2.2-ALPHA is now available From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk PAO-961115 for 2.2-ALPHA is now available. ftp://ryukyu.mt.cs.keio.ac.jp/pub/FreeBSD/PAO/PAO-961115.tar.gz Changes: Target is changed from 2.2-SNAP to 2.2-ALPHA fe driver CRC length fix ed driver probe routine fix added xgps global positioning system client -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan