From owner-freebsd-mobile Sun Mar 11 2:37:44 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 06A6D37B718; Sun, 11 Mar 2001 02:37:37 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA95252; Sun, 11 Mar 2001 11:37:32 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103111037.LAA95252@freebsd.dk> Subject: Re: iomega clik! In-Reply-To: <200103102051.f2AKpXI20839@harmony.village.org> from Warner Losh at "Mar 10, 2001 01:51:33 pm" To: imp@harmony.village.org (Warner Losh) Date: Sun, 11 Mar 2001 11:37:31 +0100 (CET) Cc: sos@freebsd.org, mobile@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Warner Losh wrote: I'll look at this asap, some of it should be dealt with a bit differently, I'll be back with a new patch... > I just got one of those cool pccard clik! drives. The ones with the > drive integrated into the card. > > Turns out they don't grok the mode sense for page > ATAPI_REWRITEABLE_CAP_PAGE, nor the ejection prevention commands > (ATAPI_PREVENT_ALLOW). So we fake it. > > These patches are loosely based on patches that Tetsuo Sakaguchi-san > posted in [bsd-nomads:14262] against 2.2.8 + PAO > wfd.c. I didn't see anything in the message to indicate if > Sakagushi-san is the athor of these patches, or if he was just passing > them along. If you commit this, please give credit something like: > > Submitted by: imp based on earlier patches by Tetsuo Sakaguchi-san > > > In addition, they fix a kernel panic when an atapi driver fails to > attach and is later detached. We do this by adding a check to see if > adp is non-NULL before using it in atapi_detach(). Maybe a better way > would be to clear the present bit in the parent bus, but I'm not sure > what the implications of doing that would be. > > I don't have any atapi fd devices to test these patches with. I'm > fairly certain I didn't break anything, but am posting these here in > case I did. > > Warner > > Index: atapi-all.c > =================================================================== > RCS file: /cache/ncvs/src/sys/dev/ata/atapi-all.c,v > retrieving revision 1.63 > diff -u -r1.63 atapi-all.c > --- atapi-all.c 2001/02/12 08:34:07 1.63 > +++ atapi-all.c 2001/03/10 18:43:13 > @@ -121,6 +121,12 @@ > void > atapi_detach(struct atapi_softc *atp) > { > + /* > + * atp will be NULL when the child failed to attach. > + */ > + if (atp == NULL) > + return; > + > switch (ATP_PARAM->device_type) { > #ifdef DEV_ATAPICD > case ATAPI_TYPE_CDROM: > Index: atapi-fd.c > =================================================================== > RCS file: /cache/ncvs/src/sys/dev/ata/atapi-fd.c,v > retrieving revision 1.58 > diff -u -r1.58 atapi-fd.c > --- atapi-fd.c 2001/03/06 09:42:46 1.58 > +++ atapi-fd.c 2001/03/10 20:32:53 > @@ -67,6 +67,7 @@ > > /* prototypes */ > static int afd_sense(struct afd_softc *); > +static int afd_clik_sense(struct afd_softc *); > static void afd_describe(struct afd_softc *); > static int afd_partial_done(struct atapi_request *); > static int afd_done(struct atapi_request *); > @@ -93,13 +94,19 @@ > fdp->atp = atp; > fdp->lun = ata_get_lun(&afd_lun_map); > > + if (!strncmp(ATA_PARAM(atp->controller, atp->unit)->model, > + "IOMEGA Clik!", 12)) > + fdp->iomega_clik = 1; > + else > + fdp->iomega_clik = 0; > + > if (afd_sense(fdp)) { > free(fdp, M_AFD); > return -1; > } > > - if (!strncmp(ATA_PARAM(fdp->atp->controller, fdp->atp->unit)->model, > - "IOMEGA ZIP", 10)) > + if (!strncmp(ATA_PARAM(atp->controller, atp->unit)->model, > + "IOMEGA ZIP", 10)) > fdp->transfersize = 64; > > devstat_add_entry(&fdp->stats, "afd", fdp->lun, DEV_BSIZE, > @@ -131,7 +138,35 @@ > free(fdp, M_AFD); > } > > +/* > + * The iomega clik, like other iomega, it a pain in the backside. > + * It doesn't support the ATAPI_REWRITABLE_CAP_PAGE, so we have > + * to fake it up. In addition, we have to kick the drive to make > + * sure that it is something approaching sane. But test_ready > + * appears to fail when a disk isn't inserted. > + */ > static int > +afd_clik_sense(struct afd_softc *fdp) > +{ > + atapi_test_ready(fdp->atp); > + > + fdp->transfersize = 64; > + fdp->header.wp = 0; > + fdp->header.medium_type = MFD_CLIK; > + fdp->cap.page_code = ATAPI_REWRITEABLE_CAP_PAGE; > + fdp->cap.ps = 0; > + fdp->cap.page_length = 0; > + fdp->cap.transfer_rate = 500; > + fdp->cap.heads = CLIK_HEADS; > + fdp->cap.sectors = CLIK_SECTORS; > + fdp->cap.sector_size = CLIK_SECTOR_SIZE; > + fdp->cap.cylinders = CLIK_CYLS; > + fdp->cap.motor_delay = 1; > + fdp->cap.rpm = 3600; > + return 0; > +} > + > +static int > afd_sense(struct afd_softc *fdp) > { > int8_t buffer[256]; > @@ -140,6 +175,8 @@ > 0, 0, 0, 0, 0, 0, 0 }; > int count, error = 0; > > + if (fdp->iomega_clik) > + return (afd_clik_sense(fdp)); > bzero(buffer, sizeof(buffer)); > /* get drive capabilities, some drives needs this repeated */ > for (count = 0 ; count < 5 ; count++) { > @@ -423,5 +460,8 @@ > int8_t ccb[16] = { ATAPI_PREVENT_ALLOW, 0, 0, 0, lock, > 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }; > > + if (fdp->iomega_clik) > + return 0; > + > return atapi_queue_cmd(fdp->atp, ccb, NULL, 0, 0,30, NULL, NULL); > } > Index: atapi-fd.h > =================================================================== > RCS file: /cache/ncvs/src/sys/dev/ata/atapi-fd.h,v > retrieving revision 1.13 > diff -u -r1.13 atapi-fd.h > --- atapi-fd.h 2001/01/10 19:19:47 1.13 > +++ atapi-fd.h 2001/03/10 19:39:34 > @@ -39,6 +39,7 @@ > #define MFD_HD_12 0x23 > #define MFD_HD_144 0x24 > #define MFD_UHD 0x31 > +#define MFD_CLIK 0xfe /* Fake clik type */ > > #define MFD_UNKNOWN 0x00 > #define MFD_NO_DISC 0x70 > @@ -70,6 +71,12 @@ > u_int8_t reserved30[2]; > }; > > +/* IOMEGA Clik parameters */ > +#define CLIK_SECTOR_SIZE 512 > +#define CLIK_CYLS 39441 > +#define CLIK_SECTORS 2 > +#define CLIK_HEADS 1 > + > struct afd_softc { > struct atapi_softc *atp; /* controller structure */ > int lun; /* logical device unit */ > @@ -80,5 +87,5 @@ > struct disk disk; /* virtual drives */ > struct devstat stats; > dev_t dev; /* device place holder */ > + int iomega_clik; > }; > - > -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 8:11:21 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 068C837B718 for ; Sun, 11 Mar 2001 08:11:18 -0800 (PST) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f2BGBGn61059; Sun, 11 Mar 2001 08:11:16 -0800 (PST) Date: Sun, 11 Mar 2001 08:11:16 -0800 (PST) From: David Wolfskill Message-Id: <200103111611.f2BGBGn61059@bunrab.catwhisker.org> To: david@catwhisker.org, mobile@FreeBSD.ORG Subject: Re: -CURRENT OK; -STBALE (4.3-BETA) not for D-Link DFE-650? In-Reply-To: <200103110244.f2B2ilH59627@bunrab.catwhisker.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Date: Sat, 10 Mar 2001 18:44:47 -0800 (PST) >From: David Wolfskill In my haste yesterday, I made a couple of mistakes, with the result that nothing I was writing about was worth posting to this (or any other) list; sorry. >Sorry; I can't get to the FreeBSD Web site to check the archives; >I'm able to ping freefall & traceroute to it, but the Web server >doesn't appear to be responding. That was a result of a loss of a default route. >.... >while in today's -CURRENT, it works fine: >The kernel configs are as similar as I can make them; here's a diff of a >normal (non-verbose) dmesg output: Except that the -CURRENT kernel had the "ed" device defined, while neither -STABLE kernel did. Amazing what defining the device can do for the ability to use it. My apologies to anyone affected, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 12:22:47 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from burdell.cc.gatech.edu (burdell.cc.gatech.edu [130.207.3.207]) by hub.freebsd.org (Postfix) with ESMTP id 3476D37B719 for ; Sun, 11 Mar 2001 12:22:46 -0800 (PST) (envelope-from dibble@cc.gatech.edu) Received: from felix.cc.gatech.edu (felix.cc.gatech.edu [130.207.107.11]) by burdell.cc.gatech.edu (8.9.1/8.9.3) with ESMTP id PAA01604 for ; Sun, 11 Mar 2001 15:22:45 -0500 (EST) Received: from jefflee.cnd.gatech.edu (r55h47.res.gatech.edu [128.61.55.47]) by felix.cc.gatech.edu (8.9.3+Sun/8.9.1) with SMTP id PAA05773 for ; Sun, 11 Mar 2001 15:22:44 -0500 (EST) Content-Type: text/plain; charset="iso-8859-1" From: "Jeffrey J. Lee" Reply-To: dibble@cc.gatech.edu Organization: Georgia Tech To: freebsd-mobile@freebsd.org Subject: apm: time remaining Date: Sun, 11 Mar 2001 15:20:10 -0500 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01031115201001.57156@jefflee.cnd.gatech.edu> Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org whenever I run apm -t to find out how long i have left on my battery, I = get=20 the -1 return value. Is there some way to fix this, or is it something t= o do=20 with the hardware not supporting this feature? --=20 #################### Jeff Lee Dibble@cc.gatech.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 12:28:43 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from linux.the-dixons.net (ip209-183-109-168.as.indy.net [209.183.109.168]) by hub.freebsd.org (Postfix) with ESMTP id B031037B719 for ; Sun, 11 Mar 2001 12:28:39 -0800 (PST) (envelope-from tdixon@the-dixons.net) Received: by linux.the-dixons.net (Postfix, from userid 501) id 1AF8729ABB; Sun, 11 Mar 2001 15:26:15 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by linux.the-dixons.net (Postfix) with ESMTP id 13439253EF; Sun, 11 Mar 2001 15:26:15 +0000 (GMT) Date: Sun, 11 Mar 2001 15:26:15 +0000 (GMT) From: Tim Dixon To: "Jeffrey J. Lee" Cc: Subject: Re: apm: time remaining In-Reply-To: <01031115201001.57156@jefflee.cnd.gatech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to the APM man page, it returns -1 if your hardware doesn't provide a time estimate. On Sun, 11 Mar 2001, Jeffrey J. Lee wrote: > whenever I run apm -t to find out how long i have left on my battery, I get > the -1 return value. Is there some way to fix this, or is it something to do > with the hardware not supporting this feature? > > -- Tim Dixon tdixon@the-dixons.net http://www.the-dixons.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 19:24:49 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id 0D89337B719 for ; Sun, 11 Mar 2001 19:24:44 -0800 (PST) (envelope-from stannous@stannous-ultra.cisco.com) Received: from stannous-ultra.cisco.com (stannous-ultra.cisco.com [161.44.54.62]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id TAA08832 for ; Sun, 11 Mar 2001 19:24:46 -0800 (PST) Received: (from stannous@localhost) by stannous-ultra.cisco.com (8.8.8+Sun/8.8.8) id WAA19368 for freebsd-mobile@freebsd.org; Sun, 11 Mar 2001 22:24:48 -0500 (EST) Date: Sun, 11 Mar 2001 22:24:48 -0500 From: Sam Tannous To: freebsd-mobile@freebsd.org Subject: serial port on thinkpad t20? Message-ID: <20010311222447.A19362@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone been able to get the serial port on the t20 working? If so, I'd appreciate any tips on the kernel config needed. dmesg shows this on my T20: sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 Thanks, Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 19:28:43 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 1CD4237B718 for ; Sun, 11 Mar 2001 19:28:39 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA02276; Mon, 12 Mar 2001 13:58:22 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010311222447.A19362@cisco.com> Date: Mon, 12 Mar 2001 13:58:22 +1030 (CST) From: "Daniel O'Connor" To: Sam Tannous Subject: RE: serial port on thinkpad t20? Cc: freebsd-mobile@freebsd.org Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 12-Mar-01 Sam Tannous wrote: > Has anyone been able to get the serial port > on the t20 working? If so, I'd > appreciate any tips on the kernel > config needed. > > > dmesg shows this on my T20: > > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 > sio1: configured irq 3 not in bitmap of probed irqs 0 I don't have a T20 (sigh :) but I have seen this when the BIOS serial settings say 'auto' rather than forcing the comport address. Don't know if that's any help. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 20:10:12 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail5.nc.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id 497B137B71A for ; Sun, 11 Mar 2001 20:10:10 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail5.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 11 Mar 2001 23:10:03 -0500 Message-ID: <3AAC4C03.13000DE@babbleon.org> Date: Sun, 11 Mar 2001 23:09:39 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Subject: Bridging with 3C589D-COMBO on 4.2-RELEASE? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am trying to get vmware going and having all sorts of trouble with networking. It has finally occured to me that the problem *may* be with my ethernet interface, which is a 3com PCMCIA ethernet card, the 3c589d combo card, device ed0. The freebsd handbook says to see the man page for devices that arene't supported for bridge; the man page says that Interfaces that cannot be put into promiscuous mode or that don't support sending packets with arbitrary Ethernet source addresses are not compati- ble with bridging. I don't have any idea if this is true of the 3c589d, or even how to find out. -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 20:19:52 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 6D6D637B718 for ; Sun, 11 Mar 2001 20:19:50 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2C4JbI31972; Sun, 11 Mar 2001 21:19:37 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103120419.f2C4JbI31972@harmony.village.org> To: The Babbler Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 11 Mar 2001 23:09:39 EST." <3AAC4C03.13000DE@babbleon.org> References: <3AAC4C03.13000DE@babbleon.org> Date: Sun, 11 Mar 2001 21:19:36 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <3AAC4C03.13000DE@babbleon.org> The Babbler writes: : It has finally occured to me that the problem *may* be with my ethernet : interface, which is a 3com PCMCIA ethernet card, the 3c589d combo card, : device ed0. 3c589d card uses the ep driver. : The freebsd handbook says to see the man page for devices that arene't : supported for bridge; the man page says that : Interfaces that cannot be put into promiscuous mode or that don't : support sending packets with arbitrary Ethernet source addresses : are not compatible with bridging. : : I don't have any idea if this is true of the 3c589d, or even how to find : out. I know that the ep driver supports promiscuous mode. I don't know if it can send packets with arbitrary ethrnet source addresses. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 20:20:48 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail5.nc.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id 7E40137B718 for ; Sun, 11 Mar 2001 20:20:45 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail5.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 11 Mar 2001 23:20:44 -0500 Message-ID: <3AAC4E83.2C281B90@babbleon.org> Date: Sun, 11 Mar 2001 23:20:20 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <3AAC4C03.13000DE@babbleon.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oh, I hate it when I do that. It's known as ep0, of course. Anybody else got a promiscuous 3c589d? When I try to enable bridging, it shuts down my ep0 networking entirely, so I lose all my networking; if I unplug & plug the card it gets address 0.0.0.0, presumably because DHCP fails; and if I try to turn off bridging after the fact, the machine hangs hard & I have to power off. PS: In my experience, though FreeBSD has lots of advantages, it is *much* less stable than Linux. It's crashed -way- more than Linux ever did; more even than Windows does at work (of course I push Windows a lot less). And I've had it lose files a couple of times when it came back up after a hard crash like that. Is this at all normal? Is it at all normal for folks with laptops? The Babbler wrote: > > I am trying to get vmware going and having all sorts of trouble with > networking. > > It has finally occured to me that the problem *may* be with my ethernet > interface, which is a 3com PCMCIA ethernet card, the 3c589d combo card, > device ed0. ep0 > > The freebsd handbook says to see the man page for devices that arene't > supported for bridge; the man page says that > > Interfaces that cannot be put into promiscuous mode or that don't > support sending packets with arbitrary Ethernet source addresses are > not compatible with bridging. > > I don't have any idea if this is true of the 3c589d, or even how to find > out. > > -- > "Brian, the man from babble-on" bts@babbleon.org > Brian T. Schellenberger http://www.babbleon.org > Support http://www.eff.org. Support decss defendents. > Support http://www.programming-freedom.org. Boycott amazon.com. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 20:45: 9 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from assaris.sics.se (dhcp119.iss.kth.se [130.237.7.119]) by hub.freebsd.org (Postfix) with ESMTP id 6C47E37B719 for ; Sun, 11 Mar 2001 20:45:06 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id FAA95295; Mon, 12 Mar 2001 05:45:07 +0100 (CET) (envelope-from assar) To: Subject: changing to bss mode for an and ray From: Assar Westerlund Date: 12 Mar 2001 05:45:07 +0100 Message-ID: <5lpufna94c.fsf@assaris.sics.se> Lines: 55 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I would like to change the default mode to be BSS, so if anybody using the ray and an drivers could test these changes, I would be grateful. /assar Index: dev/an/if_an.c =================================================================== RCS file: /home/ncvs/src/sys/dev/an/if_an.c,v retrieving revision 1.14 diff -u -w -r1.14 if_an.c --- dev/an/if_an.c 2001/01/19 01:58:28 1.14 +++ dev/an/if_an.c 2001/03/12 04:36:06 @@ -375,7 +375,7 @@ sc->an_ssidlist.an_ssid1_len = strlen(AN_DEFAULT_NETNAME); sc->an_config.an_opmode = - AN_OPMODE_IBSS_ADHOC; + AN_OPMODE_INFRASTRUCTURE_STATION; sc->an_tx_rate = 0; bzero((char *)&sc->an_stats, sizeof(sc->an_stats)); Index: dev/an/if_anreg.h =================================================================== RCS file: /home/ncvs/src/sys/dev/an/if_anreg.h,v retrieving revision 1.5 diff -u -w -r1.5 if_anreg.h --- dev/an/if_anreg.h 2001/02/09 06:08:38 1.5 +++ dev/an/if_anreg.h 2001/03/12 04:36:06 @@ -34,8 +34,8 @@ #define AN_TIMEOUT 65536 -/* Default network name: ANY */ -#define AN_DEFAULT_NETNAME "ANY" +/* Default network name: empty string implies any */ +#define AN_DEFAULT_NETNAME "" /* The nodename must be less than 16 bytes */ #define AN_DEFAULT_NODENAME "FreeBSD" Index: dev/ray/if_raymib.h =================================================================== RCS file: /home/ncvs/src/sys/dev/ray/if_raymib.h,v retrieving revision 1.10 diff -u -w -r1.10 if_raymib.h --- dev/ray/if_raymib.h 2000/11/14 05:32:01 1.10 +++ dev/ray/if_raymib.h 2001/03/12 04:36:11 @@ -537,7 +537,7 @@ */ #define RAY_MIB_NET_TYPE_ADHOC 0x00 #define RAY_MIB_NET_TYPE_INFRA 0x01 -#define RAY_MIB_NET_TYPE_DEFAULT RAY_MIB_NET_TYPE_ADHOC +#define RAY_MIB_NET_TYPE_DEFAULT RAY_MIB_NET_TYPE_INFRA /* * mib_ap_status To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 21:56:25 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 04F6737B718; Sun, 11 Mar 2001 21:56:22 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f2C5uLP04471; Sun, 11 Mar 2001 21:56:21 -0800 Date: Sun, 11 Mar 2001 21:56:21 -0800 From: Brooks Davis To: Assar Westerlund Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: changing to bss mode for an and ray Message-ID: <20010311215621.A3739@Odin.AC.HMC.Edu> References: <5lpufna94c.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <5lpufna94c.fsf@assaris.sics.se>; from assar@FreeBSD.ORG on Mon, Mar 12, 2001 at 05:45:07AM +0100 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Mar 12, 2001 at 05:45:07AM +0100, Assar Westerlund wrote: > I would like to change the default mode to be BSS, so if anybody using > the ray and an drivers could test these changes, I would be grateful. The default mode change on the an driver should work. I've tested it in another form (see PR: conf/25577). I don't know about the SSID change since my networks don't allow that to work. I believe the author of the ray driver objected to this change in principle. -- 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 --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6rGUEXY6L6fI4GtQRAlelAKCExwdL+LbmoENb2xEtthVINqvC6gCeNVPM dL88jth3aUM2igwDjDKMfmE= =YAPN -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Mar 11 22:14:52 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from assaris.sics.se (dhcp119.iss.kth.se [130.237.7.119]) by hub.freebsd.org (Postfix) with ESMTP id 8539C37B718 for ; Sun, 11 Mar 2001 22:14:48 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id HAA06457; Mon, 12 Mar 2001 07:14:45 +0100 (CET) (envelope-from assar) To: Brooks Davis Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: changing to bss mode for an and ray References: <5lpufna94c.fsf@assaris.sics.se> <20010311215621.A3739@Odin.AC.HMC.Edu> From: Assar Westerlund Date: 12 Mar 2001 07:14:45 +0100 In-Reply-To: Brooks Davis's message of "Sun, 11 Mar 2001 21:56:21 -0800" Message-ID: <5lwv9vy0mi.fsf@assaris.sics.se> Lines: 18 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brooks Davis writes: > The default mode change on the an driver should work. I've tested it in > another form (see PR: conf/25577). Thanks for testing it. I've comitted it. > I don't know about the SSID change since my networks don't allow > that to work. Could somebody else test that? The empty string is the right thing for wi and makes sense to me but I don't know anything about an. > I believe the author of the ray driver objected to this change in > principle. Could you give me a pointer to this discussion? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 0: 3:53 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from vaio.avias.com (dialup2.avias.com [195.14.38.69]) by hub.freebsd.org (Postfix) with ESMTP id 74B2D37B718 for ; Mon, 12 Mar 2001 00:03:47 -0800 (PST) (envelope-from juriy@vaio.avias.com) Received: (from juriy@localhost) by vaio.avias.com (8.11.3/8.11.3) id f2C86fc01545 for freebsd-mobile@FreeBSD.ORG; Mon, 12 Mar 2001 11:06:41 +0300 (MSK) (envelope-from juriy) Date: Mon, 12 Mar 2001 11:05:26 +0300 From: Juriy Goloveshkin To: freebsd-mobile@FreeBSD.ORG Subject: Vaio's GlidePoint & wheel mode Message-ID: <20010312110525.A1431@avias.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, it migth be usefull for somebody... moused_flags="-3 -w3 -m2=4" -m2=4 means "Tap" is equal middle button(I migth be not very good...) Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5" Option "Buttons" "5" EndSection It seems like wheel rolling when right button is pressed. -- Bye Juriy Goloveshkin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 0:13:40 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 6C25E37B718; Mon, 12 Mar 2001 00:13:37 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 646D66AC94; Mon, 12 Mar 2001 18:43:35 +1030 (CST) Date: Mon, 12 Mar 2001 18:43:35 +1030 From: Greg Lehey To: Assar Westerlund Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: changing to bss mode for an and ray Message-ID: <20010312184335.D11986@wantadilla.lemis.com> References: <5lpufna94c.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5lpufna94c.fsf@assaris.sics.se>; from assar@FreeBSD.ORG on Mon, Mar 12, 2001 at 05:45:07AM +0100 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Monday, 12 March 2001 at 5:45:07 +0100, Assar Westerlund wrote: > I would like to change the default mode to be BSS, so if anybody using > the ray and an drivers could test these changes, I would be grateful. AFAIK there are no base stations for ray. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 0:21:58 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from assaris.sics.se (dhcp119.iss.kth.se [130.237.7.119]) by hub.freebsd.org (Postfix) with ESMTP id 4F76037B719 for ; Mon, 12 Mar 2001 00:21:55 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id JAA17076; Mon, 12 Mar 2001 09:21:34 +0100 (CET) (envelope-from assar) To: Greg Lehey Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: changing to bss mode for an and ray References: <5lpufna94c.fsf@assaris.sics.se> <20010312184335.D11986@wantadilla.lemis.com> From: Assar Westerlund Date: 12 Mar 2001 09:21:33 +0100 In-Reply-To: Greg Lehey's message of "Mon, 12 Mar 2001 18:43:35 +1030" Message-ID: <5l66hfxur6.fsf@assaris.sics.se> Lines: 9 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg Lehey writes: > AFAIK there are no base stations for ray. I've no clue, but in the source, they are hinted at: * I have received an AP from Raylink and will be working on * infrastructure mode. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 0:26:10 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 305C937B719; Mon, 12 Mar 2001 00:26:07 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 3940A6A90D; Mon, 12 Mar 2001 18:56:05 +1030 (CST) Date: Mon, 12 Mar 2001 18:56:05 +1030 From: Greg Lehey To: Assar Westerlund Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: changing to bss mode for an and ray Message-ID: <20010312185605.E11986@wantadilla.lemis.com> References: <5lpufna94c.fsf@assaris.sics.se> <20010312184335.D11986@wantadilla.lemis.com> <5l66hfxur6.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5l66hfxur6.fsf@assaris.sics.se>; from assar@FreeBSD.ORG on Mon, Mar 12, 2001 at 09:21:33AM +0100 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Monday, 12 March 2001 at 9:21:33 +0100, Assar Westerlund wrote: > Greg Lehey writes: >> AFAIK there are no base stations for ray. > > I've no clue, but in the source, they are hinted at: > > * I have received an AP from Raylink and will be working on > * infrastructure mode. Correct, there was talk about it. But they've gone broke now, I think. I'm pretty sure that just about everybody who has the cards uses them in ad-hoc mode. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 1:38:38 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (Postfix) with ESMTP id D700037B718; Mon, 12 Mar 2001 01:38:35 -0800 (PST) (envelope-from dmlb@dmlb.org) Received: from symnt3.Cadence.COM (symnt3.Cadence.COM [194.32.101.100]) by mailgate.Cadence.COM (8.9.3/8.9.3) with ESMTP id BAA06685; Mon, 12 Mar 2001 01:36:52 -0800 (PST) Received: from pc610cam (pc610-cam.cadence.com [194.32.96.210]) by symnt3.Cadence.COM with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id GM9QP4G5; Mon, 12 Mar 2001 09:36:12 -0000 Message-ID: <004301c0aad7$f45b7960$d26020c2@Cadence.COM> From: "Duncan Barclay" To: "Greg Lehey" , "Assar Westerlund" Cc: References: <5lpufna94c.fsf@assaris.sics.se> <20010312184335.D11986@wantadilla.lemis.com> <5l66hfxur6.fsf@assaris.sics.se> <20010312185605.E11986@wantadilla.lemis.com> Subject: Re: changing to bss mode for an and ray Date: Mon, 12 Mar 2001 09:36:45 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Received: By mailgate.Cadence.COM as BAA06685 at Mon Mar 12 01:36:52 2001 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi [outcast mail Greg - sorry] There are basestations for the ray cards and there is still a company selling them. They've sent me a basestation. As the manual states, the driver supports ad-hoc only cards. Duncan -- _____________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@dmlb.org | the alcoholics, and the permanently stoned. dmlb@freebsd.org| Steven King ----- Original Message ----- From: "Greg Lehey" To: "Assar Westerlund" Cc: Sent: Monday, March 12, 2001 8:26 AM Subject: Re: changing to bss mode for an and ray > On Monday, 12 March 2001 at 9:21:33 +0100, Assar Westerlund wrote: > > Greg Lehey writes: > >> AFAIK there are no base stations for ray. > > > > I've no clue, but in the source, they are hinted at: > > > > * I have received an AP from Raylink and will be working on > > * infrastructure mode. > > Correct, there was talk about it. But they've gone broke now, I > think. I'm pretty sure that just about everybody who has the cards > uses them in ad-hoc mode. > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 2:17:12 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E38D137B718; Mon, 12 Mar 2001 02:17:06 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA45917; Mon, 12 Mar 2001 11:17:02 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103121017.LAA45917@freebsd.dk> Subject: Re: iomega clik! In-Reply-To: <200103111037.LAA95252@freebsd.dk> from Soren Schmidt at "Mar 11, 2001 11:37:31 am" To: sos@freebsd.dk (Soren Schmidt) Date: Mon, 12 Mar 2001 11:17:02 +0100 (CET) Cc: imp@harmony.village.org (Warner Losh), sos@FreeBSD.ORG, mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Soren Schmidt wrote: > It seems Warner Losh wrote: > > I'll look at this asap, some of it should be dealt with a bit > differently, I'll be back with a new patch... OK, here is the "official" patch for the clik, the detach part is handled by another patch set I have in the wings, that deals with prober detach/attach of devices, but thats for another time.. Anyhow I cannot test this, so please let me know if this makes the clik work... Index: atapi-fd.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/atapi-fd.c,v retrieving revision 1.58 diff -u -r1.58 atapi-fd.c --- atapi-fd.c 2001/03/06 09:42:46 1.58 +++ atapi-fd.c 2001/03/12 07:48:11 @@ -140,6 +146,19 @@ 0, 0, 0, 0, 0, 0, 0 }; int count, error = 0; + /* The IOMEGA Clik! doesn't support reading the cap page, fake it */ + if (!strncmp(ATA_PARAM(fdp->atp->controller, fdp->atp->unit)->model, + "IOMEGA Clik!", 12)) { + fdp->transfersize = 64; + fdp->cap.transfer_rate = 500; + fdp->cap.heads = 1; + fdp->cap.sectors = 2; + fdp->cap.cylinders = 39441; + fdp->cap.sector_size = 512; + atapi_test_ready(fdp->atp); + return 0; + } + bzero(buffer, sizeof(buffer)); /* get drive capabilities, some drives needs this repeated */ for (count = 0 ; count < 5 ; count++) { -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 3:12: 6 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from neptune.he.net (neptune.he.net [216.218.166.2]) by hub.freebsd.org (Postfix) with ESMTP id B094C37B718 for ; Mon, 12 Mar 2001 03:12:02 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com ([211.101.228.66] (may be forged)) by neptune.he.net (8.8.6/8.8.2) with ESMTP id DAA04610 for ; Mon, 12 Mar 2001 03:12:02 -0800 Received: (from robinson@localhost) by netrinsics.com (8.11.2/8.11.1) id f2CBBxT17315 for freebsd-mobile@outbound.freebsd.org.; Mon, 12 Mar 2001 19:11:59 +0800 (+0800) (envelope-from robinson) Date: Mon, 12 Mar 2001 19:11:59 +0800 (+0800) From: Michael Robinson Message-Id: <200103121111.f2CBBxT17315@netrinsics.com> To: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brian T. Schellenberger writes: >PS: In my experience, though FreeBSD has lots of advantages, it is >*much* less stable than Linux. It's crashed -way- more than Linux ever >did; more even than Windows does at work (of course I push Windows a lot >less). And I've had it lose files a couple of times when it came back >up after a hard crash like that. > >Is this at all normal? >Is it at all normal for folks with laptops? I've been using FreeBSD on all my various laptops since 2.0.5, back in '95. I'm running 5.0-CURRENT now. In all these years, versions, and machines, FreeBSD has only ever crashed on me either as the result of reproducible, known deficiencies in the support of laptop-hardware esoterica (e.g., bad handling of PCMCIA card ejection, etc.), or reproducible, known deficiencies in the handling of resource starvation (e.g. an inadvertant infinitely recursive Makefile sucks up all available file descriptor slots). In every configuration, it has only been a question of knowing the few things not to do, and not doing them. Generally speaking, the rule of thumb is that if FreeBSD crashes for no apparent reason, your hardware is bad. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 4: 8:16 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.sanda.gr.jp (ns.sanda.gr.jp [210.232.122.18]) by hub.freebsd.org (Postfix) with ESMTP id D592C37B718; Mon, 12 Mar 2001 04:08:06 -0800 (PST) (envelope-from non@ever.sanda.gr.jp) Received: from ever.sanda.gr.jp (epoch [10.93.63.51]) by ns.sanda.gr.jp (8.9.3/3.7W) with ESMTP id VAA19309; Mon, 12 Mar 2001 21:08:04 +0900 (JST) From: non@ever.sanda.gr.jp Received: from localhost (localhost [127.0.0.1]) by ever.sanda.gr.jp (8.8.8/3.3W9) with ESMTP id VAA17649; Mon, 12 Mar 2001 21:08:04 +0900 (JST) To: mobile@FreeBSD.ORG Cc: sos@FreeBSD.ORG Subject: Re: iomega clik! In-Reply-To: <200103121017.LAA45917@freebsd.dk> References: <200103111037.LAA95252@freebsd.dk> <200103121017.LAA45917@freebsd.dk> X-Mailer: Mew version 1.94 on Emacs 19.28 / Mule 2.3 =?iso-2022-jp?B?KBskQkt2RSYyVhsoQik=?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010312210804X.non@ever.sanda.gr.jp> Date: Mon, 12 Mar 2001 21:08:04 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 11 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Soren Schmidt Date: Mon, 12 Mar 2001 11:17:02 +0100 (CET) > OK, here is the "official" patch for the clik, the detach part > is handled by another patch set I have in the wings, that deals > with prober detach/attach of devices, but thats for another time.. > Anyhow I cannot test this, so please let me know if this makes > the clik work... It worked for original Iomega Clik (40MB). // Noriaki Mitsunaga // non@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 12:17: 3 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 10CC837B718 for ; Mon, 12 Mar 2001 12:16:54 -0800 (PST) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 22318 invoked by uid 0); 12 Mar 2001 20:16:52 -0000 Received: from p3ee21613.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.19) by mail.gmx.net (mail08) with SMTP; 12 Mar 2001 20:16:52 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id RAA15783 for freebsd-mobile@freebsd.org; Mon, 12 Mar 2001 17:48:52 +0100 Date: Mon, 12 Mar 2001 17:48:52 +0100 From: Gerhard Sittig To: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Message-ID: <20010312174852.T20830@speedy.gsinet> Mail-Followup-To: freebsd-mobile@freebsd.org References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3AAC4E83.2C281B90@babbleon.org>; from bts@babbleon.org on Sun, Mar 11, 2001 at 11:20:20PM -0500 Organization: System Defenestrators Inc. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Mar 11, 2001 at 23:20 -0500, The Babbler wrote: > > Anybody else got a promiscuous 3c589d? I had quite a few tcpdump(1) sessions with a 3c589D and FreeBSD 3.3 and 4.[012], so I assume promiscous mode works fine. The only problem I had with this card is that it defaults to the wrong media type and doesn't recognize TP wiring, instead it always falls back to BNC. So I have to force 10baseT selection. > When I try to enable bridging, it shuts down my ep0 networking > entirely, so I lose all my networking; if I unplug & plug the > card it gets address 0.0.0.0, presumably because DHCP fails; > and if I try to turn off bridging after the fact, the machine > hangs hard & I have to power off. Do you 'ifconfig down' the card *prior* to removal? For my own sake I would get used to some sort of this behaviour ... :> Just make sure nothing's using the card when you unplug it instead of dazzling all the drivers / apps with events there's no card for. > PS: In my experience, though FreeBSD has lots of advantages, it > is *much* less stable than Linux. It's crashed -way- more than > Linux ever did; more even than Windows does at work (of course > I push Windows a lot less). And I've had it lose files a > couple of times when it came back up after a hard crash like > that. > > Is this at all normal? > Is it at all normal for folks with laptops? No. And no. You state the reason for your "stable Windows" yourself. And in comparison to Linux it must be some configuration issue. Setup correctly (and given decent hardware) both FreeBSD and Linux run fine. While FreeBSD is said to cope better (smooth) with heavy load. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 12:31:34 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id AC39D37B718; Mon, 12 Mar 2001 12:31:29 -0800 (PST) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f2CKVRs19327; Mon, 12 Mar 2001 12:31:27 -0800 (PST) Message-Id: <200103122031.f2CKVRs19327@ptavv.es.net> To: mobile@freebsd.org Cc: stable@freebsd.org Subject: Disk I/O problem in 4.3-BETA Date: Mon, 12 Mar 2001 12:31:27 -0800 From: "Kevin Oberman" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm not too sure if this belongs in mobile or stable. I reported the problem last week, but have seen no comments. Either it's something unique to my system (or my hardware) or people have not been doing large disk copy operations. My disk I/O performance has tanked after a cvsup on March 1. Subsequent updates have not made a difference. Specifics: System ran normally until the March 1 cvsup. The prior cvsup was February 24. Prior to March 1 I could dd a 4 GB slice in 580 seconds (or a bit under 10 minutes). After March 1 the same exact command took just under 40 minutes to complete. The same was seen copying a 2 GB slice. It increased from 5 minutes to 20 minutes. No kernel configuration changes were made. The system is an IBM ThinkPad 600E with 192 MB RAM and 12 GB and 6 GB disks. Both disks are UDMA33. All operations were performed after a stand-alone boot with only root mounted and that mounted RO. FreeBSD is on the 2 GB slice with W98 on the 4 GB one. The commands used: dd bs=32k if=/dev/ad0s1 of=/dev/ad2s1 dd bs=32k if=/dev/ad0s2 of=/dev/ad2s2 The FWIW, I subjectively feel that the time to buildworld has also increased, but I really don't recall how long it was taking in the past, so I really don't have a basis for comparison. Is anybody else aware of anything that might be causing this? IS anyone else seeing it at all? 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 12:36:38 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3674E37B719; Mon, 12 Mar 2001 12:36:32 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA99695; Mon, 12 Mar 2001 21:36:27 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103122036.VAA99695@freebsd.dk> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <200103122031.f2CKVRs19327@ptavv.es.net> from Kevin Oberman at "Mar 12, 2001 12:31:27 pm" To: oberman@es.net (Kevin Oberman) Date: Mon, 12 Mar 2001 21:36:27 +0100 (CET) Cc: mobile@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Kevin Oberman wrote: > I'm not too sure if this belongs in mobile or stable. I reported the > problem last week, but have seen no comments. Either it's something > unique to my system (or my hardware) or people have not been doing > large disk copy operations. > > My disk I/O performance has tanked after a cvsup on March 1. > Subsequent updates have not made a difference. Some of this might be due to write caching being turned off as default now, this was done due to "popular demand" because write caching can hose your filesystem on a power outage. > Specifics: System ran normally until the March 1 cvsup. The prior > cvsup was February 24. > > Prior to March 1 I could dd a 4 GB slice in 580 seconds (or a bit > under 10 minutes). After March 1 the same exact command took just > under 40 minutes to complete. The same was seen copying a 2 GB > slice. It increased from 5 minutes to 20 minutes. No kernel > configuration changes were made. This is worse than expected, try to use option ATA_ENABLE_WC and see what gives, if its not back to normal we have to look elsewhere. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 12:38:44 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from sodium.cips.nokia.com (Sodium.cips.nokia.com [199.46.17.134]) by hub.freebsd.org (Postfix) with ESMTP id 9224F37B71A for ; Mon, 12 Mar 2001 12:38:42 -0800 (PST) (envelope-from key@network-alchemy.com) Received: from sodium.cips.nokia.com (localhost.network-alchemy.com [127.0.0.1]) by sodium.cips.nokia.com (8.9.3/8.8.8) with ESMTP id MAA74319; Mon, 12 Mar 2001 12:38:34 -0800 (PST) (envelope-from key@sodium.cips.nokia.com) Message-Id: <200103122038.MAA74319@sodium.cips.nokia.com> To: Sam Tannous Cc: freebsd-mobile@FreeBSD.ORG From: Ken Key Subject: Re: serial port on thinkpad t20? In-reply-to: Your message of Sun, 11 Mar 2001 22:24:48 -0500. <20010311222447.A19362@cisco.com> Date: Mon, 12 Mar 2001 12:38:34 -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My T21 does exactly that when the serial is not enable via the BIOS. In this mode the serial port will work under Win2K but not FreeBSD, which made it very confusing to trouble shoot. Power cycle, enter BIOS by hitting F1 when prompted. With "Config" high-lighted, hit Enter. Arrow key down to "Serial port", hit Enter. Hit F5 to toggle from Disabled to Enabled. F10 to Save and Exit. Hope this helps, K^2 > Has anyone been able to get the serial port > on the t20 working? If so, I'd > appreciate any tips on the kernel > config needed. > > > dmesg shows this on my T20: > > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 > sio1: configured irq 3 not in bitmap of probed irqs 0 > > Thanks, > Sam > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- Ken Key (key@cips.nokia.com, key@Network-Alchemy.com) Nokia, Clustered IP Solutions, Santa Cruz, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 12:58:13 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id CF84A37B718 for ; Mon, 12 Mar 2001 12:58:11 -0800 (PST) (envelope-from stannous@stannous-ultra.cisco.com) Received: from stannous-ultra.cisco.com (stannous-ultra.cisco.com [161.44.54.62]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id MAA18485; Mon, 12 Mar 2001 12:58:14 -0800 (PST) Received: (from stannous@localhost) by stannous-ultra.cisco.com (8.8.8+Sun/8.8.8) id PAA20444; Mon, 12 Mar 2001 15:58:16 -0500 (EST) Date: Mon, 12 Mar 2001 15:58:16 -0500 From: Sam Tannous To: Ken Key Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: serial port on thinkpad t20? Message-ID: <20010312155816.I20183@cisco.com> References: <20010311222447.A19362@cisco.com> <200103122038.MAA74319@sodium.cips.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103122038.MAA74319@sodium.cips.nokia.com>; from key@network-alchemy.com on Mon, Mar 12, 2001 at 12:38:34PM -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 12, 2001 at 12:38:34PM -0800, Ken Key wrote: > Power cycle, enter BIOS by hitting F1 when prompted. > With "Config" high-lighted, hit Enter. > Arrow key down to "Serial port", hit Enter. > Hit F5 to toggle from Disabled to Enabled. > F10 to Save and Exit. > > Hope this helps, It does help. Thanks very much! (You didn't happen to get sound working on your T21, did you? I get the dreaded "channel dead" when I play any pcm sound (CD's play fine and the mixer works after adding options PNPBIOS and device pcm and device csa and a kernel recompile)). Regards, Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 13: 0:28 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 89FA037B71A; Mon, 12 Mar 2001 13:00:23 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2CKx5Z20448; Mon, 12 Mar 2001 12:59:05 -0800 (PST) Date: Mon, 12 Mar 2001 12:59:05 -0800 From: Alfred Perlstein To: Soren Schmidt Cc: Kevin Oberman , mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312125905.X18351@fw.wintelcom.net> References: <200103122031.f2CKVRs19327@ptavv.es.net> <200103122036.VAA99695@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103122036.VAA99695@freebsd.dk>; from sos@freebsd.dk on Mon, Mar 12, 2001 at 09:36:27PM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Soren Schmidt [010312 12:37] wrote: > It seems Kevin Oberman wrote: > > I'm not too sure if this belongs in mobile or stable. I reported the > > problem last week, but have seen no comments. Either it's something > > unique to my system (or my hardware) or people have not been doing > > large disk copy operations. > > > > My disk I/O performance has tanked after a cvsup on March 1. > > Subsequent updates have not made a difference. > > Some of this might be due to write caching being turned off as > default now, this was done due to "popular demand" because > write caching can hose your filesystem on a power outage. > > > Specifics: System ran normally until the March 1 cvsup. The prior > > cvsup was February 24. > > > > Prior to March 1 I could dd a 4 GB slice in 580 seconds (or a bit > > under 10 minutes). After March 1 the same exact command took just > > under 40 minutes to complete. The same was seen copying a 2 GB > > slice. It increased from 5 minutes to 20 minutes. No kernel > > configuration changes were made. > > This is worse than expected, try to use option ATA_ENABLE_WC > and see what gives, if its not back to normal we have to look elsewhere. Mr ATA, is there no ATA command to "syncronize cache" like in SCSI? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 13:20:43 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id F0F1837B718; Mon, 12 Mar 2001 13:20:38 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA10675; Mon, 12 Mar 2001 22:20:32 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103122120.WAA10675@freebsd.dk> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010312125905.X18351@fw.wintelcom.net> from Alfred Perlstein at "Mar 12, 2001 12:59:05 pm" To: bright@wintelcom.net (Alfred Perlstein) Date: Mon, 12 Mar 2001 22:20:32 +0100 (CET) Cc: oberman@es.net (Kevin Oberman), mobile@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Alfred Perlstein wrote: > > > Prior to March 1 I could dd a 4 GB slice in 580 seconds (or a bit > > > under 10 minutes). After March 1 the same exact command took just > > > under 40 minutes to complete. The same was seen copying a 2 GB > > > slice. It increased from 5 minutes to 20 minutes. No kernel > > > configuration changes were made. > > > > This is worse than expected, try to use option ATA_ENABLE_WC > > and see what gives, if its not back to normal we have to look elsewhere. > > Mr ATA, is there no ATA command to "syncronize cache" like in SCSI? Yes, there is, and the ATA driver even uses it, the problem is WHEN to use it. I originally made it flush the cache if a write contained the BIO_ORDERED bit, but that doesn't work with softupdates.. If somebody can come up with a way to tell me when I need to flush the write cache, then I'll happily add that.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 13:46:29 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 6A6CC37B719; Mon, 12 Mar 2001 13:46:25 -0800 (PST) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f2CLkLs08952; Mon, 12 Mar 2001 13:46:21 -0800 (PST) Message-Id: <200103122146.f2CLkLs08952@ptavv.es.net> To: Soren Schmidt Cc: mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-reply-to: Your message of "Mon, 12 Mar 2001 21:36:27 +0100." <200103122036.VAA99695@freebsd.dk> Date: Mon, 12 Mar 2001 13:46:21 -0800 From: "Kevin Oberman" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Soren, Thanks for the quick reply! And right on the button, too. I have turned the write cache back on (any relevance to "write cache" being abbreviated to "WC"? :-) and the time to dd the slices went back to 10 and 5 minutes (actually 489 and 287 seconds). How serious is the possible corruption issue, anyway. The loss in performance is pretty drastic although it may be that dd is an especially bad case, but I really don't like to corrupt my disks, either. Is there hope for a sysctl interface to ATA that would make it possible to switch this sort of thing without rebuilding the kernel? 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 13:47:16 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from sodium.cips.nokia.com (Sodium.cips.nokia.com [199.46.17.134]) by hub.freebsd.org (Postfix) with ESMTP id 075F437B71E for ; Mon, 12 Mar 2001 13:47:12 -0800 (PST) (envelope-from key@network-alchemy.com) Received: from sodium.cips.nokia.com (localhost.network-alchemy.com [127.0.0.1]) by sodium.cips.nokia.com (8.9.3/8.8.8) with ESMTP id NAA76483; Mon, 12 Mar 2001 13:47:03 -0800 (PST) (envelope-from key@sodium.cips.nokia.com) Message-Id: <200103122147.NAA76483@sodium.cips.nokia.com> To: Sam Tannous Cc: Ken Key , freebsd-mobile@FreeBSD.ORG From: Ken Key Subject: Re: serial port on thinkpad t20? In-reply-to: Your message of Mon, 12 Mar 2001 15:58:16 -0500. <20010312155816.I20183@cisco.com> Date: Mon, 12 Mar 2001 13:47:03 -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It does help. Thanks very much! > > (You didn't happen to get sound > working on your T21, did you? Nope. > I get the dreaded "channel dead" > when I play any pcm sound (CD's play > fine and the mixer works after > adding options PNPBIOS and device > pcm and device csa and a kernel > recompile)). I've done the same and get the "channel dead", too. I haven't had time to pursue sound as it's not a high priority for my daily work, but it would be nice. Cheers, K^2 -- Ken Key (key@cips.nokia.com, key@Network-Alchemy.com) Nokia, Clustered IP Solutions, Santa Cruz, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 13:54:28 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ohm.physics.purdue.edu (ohm.physics.purdue.edu [128.210.146.32]) by hub.freebsd.org (Postfix) with ESMTP id 45B4637B71A; Mon, 12 Mar 2001 13:54:21 -0800 (PST) (envelope-from will@physics.purdue.edu) Received: (from will@localhost) by ohm.physics.purdue.edu (8.11.2/8.9.3) id f2CLsHk65621; Mon, 12 Mar 2001 16:54:17 -0500 (EST) (envelope-from will@physics.purdue.edu) X-Authentication-Warning: ohm.physics.purdue.edu: will set sender to will@physics.purdue.edu using -f Date: Mon, 12 Mar 2001 16:54:17 -0500 From: Will Andrews To: Kevin Oberman Cc: Soren Schmidt , mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312165417.S61859@ohm.physics.purdue.edu> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Kevin Oberman , Soren Schmidt , mobile@FreeBSD.ORG, stable@FreeBSD.ORG References: <200103122036.VAA99695@freebsd.dk> <200103122146.f2CLkLs08952@ptavv.es.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ivHc2SZskddb40s2" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103122146.f2CLkLs08952@ptavv.es.net>; from oberman@es.net on Mon, Mar 12, 2001 at 01:46:21PM -0800 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ivHc2SZskddb40s2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 12, 2001 at 01:46:21PM -0800, Kevin Oberman wrote: > How serious is the possible corruption issue, anyway. The loss in > performance is pretty drastic although it may be that dd is an > especially bad case, but I really don't like to corrupt my disks, > either. If you have any serious or important data on your drives, you'd be crazy not to invest in a backup system anyways. --=20 wca --ivHc2SZskddb40s2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6rUWJF47idPgWcsURAvDLAJ0XiwzNdDXG85wk8vs5U/CrvKiwCwCfYwp5 RWpN0Du092amWhgB8BoOfFQ= =O4Wb -----END PGP SIGNATURE----- --ivHc2SZskddb40s2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 13:57:22 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 3E4B637B728; Mon, 12 Mar 2001 13:57:11 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.16 #1) id 14caJL-000I7H-00; Mon, 12 Mar 2001 13:57:03 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Will Andrews Cc: Kevin Oberman , Soren Schmidt , mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA References: <200103122036.VAA99695@freebsd.dk> <200103122146.f2CLkLs08952@ptavv.es.net> <20010312165417.S61859@ohm.physics.purdue.edu> Message-Id: Date: Mon, 12 Mar 2001 13:57:03 -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > If you have any serious or important data on your drives, you'd be crazy > not to invest in a backup system anyways. a fool and his data are soon parted -- monty williams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 14: 7:57 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3966637B719; Mon, 12 Mar 2001 14:07:54 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2CM6at22778; Mon, 12 Mar 2001 14:06:36 -0800 (PST) Date: Mon, 12 Mar 2001 14:06:36 -0800 From: Alfred Perlstein To: Kevin Oberman Cc: Soren Schmidt , mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312140636.A18351@fw.wintelcom.net> References: <200103122036.VAA99695@freebsd.dk> <200103122146.f2CLkLs08952@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103122146.f2CLkLs08952@ptavv.es.net>; from oberman@es.net on Mon, Mar 12, 2001 at 01:46:21PM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Kevin Oberman [010312 13:46] wrote: > Soren, > > Thanks for the quick reply! And right on the button, too. > > I have turned the write cache back on (any relevance to "write cache" > being abbreviated to "WC"? :-) and the time to dd the slices went back > to 10 and 5 minutes (actually 489 and 287 seconds). > > How serious is the possible corruption issue, anyway. The loss in > performance is pretty drastic although it may be that dd is an > especially bad case, but I really don't like to corrupt my disks, > either. If basically running with blind write caching turned on is akin to running your filesystem in async mode. This is because write caching gives the drive license to lie about completing a write, the various ordering of writes are effectively bypassed. If you crash without these dependancies actually written to the disk, when you come back up you have a good chance of losing large portions of your filesystem. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 14:22:26 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 86B9337B718 for ; Mon, 12 Mar 2001 14:22:24 -0800 (PST) (envelope-from ncbp@bank-pedersen.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1002) id 8A6B35D39; Mon, 12 Mar 2001 23:22:23 +0100 (CET) Date: Mon, 12 Mar 2001 23:22:23 +0100 From: "Niels Chr. Bank-Pedersen" To: freebsd-mobile@FreeBSD.ORG Subject: XFree86 + IBM t21 with S3 Savage IX8+ (Was: Re: serial port on thinkpad t20?) Message-ID: <20010312232223.A1082@bank-pedersen.dk> Mail-Followup-To: "Niels Chr. Bank-Pedersen" , freebsd-mobile@FreeBSD.ORG References: <20010312155816.I20183@cisco.com> <200103122147.NAA76483@sodium.cips.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103122147.NAA76483@sodium.cips.nokia.com>; from key@network-alchemy.com on Mon, Mar 12, 2001 at 01:47:03PM -0800 X-PGP-Fingerprint: 18D0 73F3 767F 3A40 CEBA C595 4783 D7F5 5DD1 FB8C X-PGP-Public-Key: http://freesbee.wheel.dk/~ncbp/gpgkey.pub Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (Sorry about hijacking the thread, but it sortof started wandering anyway :) Does anybody have XFree86 running on the S3 Savage IX8+ chip (1400x1050) installed on some of the T21's? /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 15: 3:33 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from sodium.cips.nokia.com (Sodium.cips.nokia.com [199.46.17.134]) by hub.freebsd.org (Postfix) with ESMTP id 5B47C37B718 for ; Mon, 12 Mar 2001 15:03:30 -0800 (PST) (envelope-from key@network-alchemy.com) Received: from sodium.cips.nokia.com (localhost.network-alchemy.com [127.0.0.1]) by sodium.cips.nokia.com (8.9.3/8.8.8) with ESMTP id PAA78151; Mon, 12 Mar 2001 15:03:26 -0800 (PST) (envelope-from key@sodium.cips.nokia.com) Message-Id: <200103122303.PAA78151@sodium.cips.nokia.com> To: "Niels Chr. Bank-Pedersen" Cc: freebsd-mobile@FreeBSD.ORG From: Ken Key Subject: Re: XFree86 + IBM t21 with S3 Savage IX8+ (Was: Re: serial port on thinkpad t20?) In-reply-to: Your message of Mon, 12 Mar 2001 23:22:23 +0100. <20010312232223.A1082@bank-pedersen.dk> Date: Mon, 12 Mar 2001 15:03:26 -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yes, using the XFree86 v4.0.2 FreeBSD binary distribution on top of FreeBSD v4.2-RELEASE. I'm running 1400x1050 with a depth of 16. I'll mail you my XF86Config directly under separate cover. Regards, K^2 > (Sorry about hijacking the thread, but it sortof started wandering > anyway :) > > Does anybody have XFree86 running on the S3 Savage IX8+ chip > (1400x1050) installed on some of the T21's? > > > /Niels Chr. > > -- > Niels Christian Bank-Pedersen, NCB1-RIPE. > Network Manager, Tele Danmark NET, IP-section. > > "Hey, are any of you guys out there actually *using* RFC 2549?" > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- Ken Key (key@cips.nokia.com, key@Network-Alchemy.com) Nokia, Clustered IP Solutions, Santa Cruz, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 15:10:34 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id E14C237B719; Mon, 12 Mar 2001 15:10:29 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2CNANH77246; Mon, 12 Mar 2001 15:10:23 -0800 (PST) (envelope-from dillon) Date: Mon, 12 Mar 2001 15:10:23 -0800 (PST) From: Matt Dillon Message-Id: <200103122310.f2CNANH77246@earth.backplane.com> To: Alfred Perlstein Cc: Kevin Oberman , Soren Schmidt , mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA References: <200103122036.VAA99695@freebsd.dk> <200103122146.f2CLkLs08952@ptavv.es.net> <20010312140636.A18351@fw.wintelcom.net> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :If basically running with blind write caching turned on is akin to :running your filesystem in async mode. This is because write :caching gives the drive license to lie about completing a write, :the various ordering of writes are effectively bypassed. If you :crash without these dependancies actually written to the disk, when :you come back up you have a good chance of losing large portions :of your filesystem. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] :Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ It's actually worse. Someone, I forget who, ran some tests with write-caching turned on and found that the IDE drive could hold a pending write in its cache 'forever', even in the face of other writes, as long as there was other disk activity going on. So we aren't just talking about issuing I/O's out of order, we are talking about issuing a sequence of writes and having some of them simply not ever commiting to disk (not for a long, long time) in a heavily loaded environment. That's bad news. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 15:14:44 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3C39F37B71B; Mon, 12 Mar 2001 15:14:38 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2CNDGY25125; Mon, 12 Mar 2001 15:13:16 -0800 (PST) Date: Mon, 12 Mar 2001 15:13:15 -0800 From: Alfred Perlstein To: Matt Dillon Cc: Kevin Oberman , Soren Schmidt , mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312151315.F18351@fw.wintelcom.net> References: <200103122036.VAA99695@freebsd.dk> <200103122146.f2CLkLs08952@ptavv.es.net> <20010312140636.A18351@fw.wintelcom.net> <200103122310.f2CNANH77246@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103122310.f2CNANH77246@earth.backplane.com>; from dillon@earth.backplane.com on Mon, Mar 12, 2001 at 03:10:23PM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Matt Dillon [010312 15:11] wrote: > :If basically running with blind write caching turned on is akin to > :running your filesystem in async mode. This is because write > :caching gives the drive license to lie about completing a write, > :the various ordering of writes are effectively bypassed. If you > :crash without these dependancies actually written to the disk, when > :you come back up you have a good chance of losing large portions > :of your filesystem. > : > :-- > :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > :Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ > > It's actually worse. Someone, I forget who, ran some tests with > write-caching turned on and found that the IDE drive could hold a > pending write in its cache 'forever', even in the face of other writes, > as long as there was other disk activity going on. So we aren't just > talking about issuing I/O's out of order, we are talking about issuing > a sequence of writes and having some of them simply not ever commiting > to disk (not for a long, long time) in a heavily loaded environment. > That's bad news. Someone leaked the Linux austrailian elevator algorithm to the disk manufacturers? I was wondering why I got a Turbo Linux CDrom with my last disk purchase. Of course I'm only kidding... -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 16:50:31 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from grumpy.dyndns.org (user-24-214-76-236.knology.net [24.214.76.236]) by hub.freebsd.org (Postfix) with ESMTP id C725C37B71A; Mon, 12 Mar 2001 16:50:23 -0800 (PST) (envelope-from dkelly@grumpy.dyndns.org) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.2/8.11.2) with ESMTP id f2D0lte06674; Mon, 12 Mar 2001 18:47:55 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200103130047.f2D0lte06674@grumpy.dyndns.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Alfred Perlstein Cc: Kevin Oberman , Soren Schmidt , mobile@FreeBSD.ORG, stable@FreeBSD.ORG From: David Kelly Subject: Re: Disk I/O problem in 4.3-BETA In-reply-to: Message from Alfred Perlstein of "Mon, 12 Mar 2001 14:06:36 PST." <20010312140636.A18351@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Mar 2001 18:47:55 -0600 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alfred Perlstein writes: > * Kevin Oberman [010312 13:46] wrote: > > > > How serious is the possible corruption issue, anyway. The loss in > > performance is pretty drastic although it may be that dd is an > > especially bad case, but I really don't like to corrupt my disks, > > either. > > If basically running with blind write caching turned on is akin to > running your filesystem in async mode. This is because write > caching gives the drive license to lie about completing a write, > the various ordering of writes are effectively bypassed. If you > crash without these dependancies actually written to the disk, when > you come back up you have a good chance of losing large portions > of your filesystem. If I'm not mistaken when write caching is disabled the ATA drive does not return from the write command until the data is on disc? And that ATA drives can not overlap or queue pending commands so the pending read/writes have to queue in the kernel? Is tagged queuing the solution or is that something else? The FreeBSD kernel has a built in daemon called syncer. It sounds like a natural place to periodically issue a sync command to such storage devices. Assuming such a command exists. My "purchased because they threw in a USB Zip-100 and ATA-100 PCI card" 45G Maxtor is awfully impressive. 32000 blocks of 128k staring 8G from the begining of the disk resulted in over 30MB/sec according to dd. I'm stunned. Kernel from mid-Feb. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 17:16:27 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 544A437B71E; Mon, 12 Mar 2001 17:16:19 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2D1F0K29172; Mon, 12 Mar 2001 17:15:00 -0800 (PST) Date: Mon, 12 Mar 2001 17:14:59 -0800 From: Alfred Perlstein To: David Kelly Cc: Kevin Oberman , Soren Schmidt , mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010312171459.P18351@fw.wintelcom.net> References: <200103130047.f2D0lte06674@grumpy.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103130047.f2D0lte06674@grumpy.dyndns.org>; from dkelly@hiwaay.net on Mon, Mar 12, 2001 at 06:47:55PM -0600 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * David Kelly [010312 16:48] wrote: > Alfred Perlstein writes: > > * Kevin Oberman [010312 13:46] wrote: > > > > > > How serious is the possible corruption issue, anyway. The loss in > > > performance is pretty drastic although it may be that dd is an > > > especially bad case, but I really don't like to corrupt my disks, > > > either. > > > > If basically running with blind write caching turned on is akin to > > running your filesystem in async mode. This is because write > > caching gives the drive license to lie about completing a write, > > the various ordering of writes are effectively bypassed. If you > > crash without these dependancies actually written to the disk, when > > you come back up you have a good chance of losing large portions > > of your filesystem. > > If I'm not mistaken when write caching is disabled the ATA drive does > not return from the write command until the data is on disc? And that > ATA drives can not overlap or queue pending commands so the pending > read/writes have to queue in the kernel? Is tagged queuing the solution > or is that something else? That would make the writes a bunch quicker... > The FreeBSD kernel has a built in daemon called syncer. It sounds like > a natural place to periodically issue a sync command to such storage > devices. Assuming such a command exists. This won't work. The syncer exists to: a) make sure data _eventually_ gets to disk. Basically without syncer, if your entire working set sat in cache and there was a crash, you might find yourself with data that's several days/weeks/months/whatever old! b) provide pressure on the filesystem to sync out data to free buffer space, although honestly this is mostly done by the buf_daemon now. You can't rely on the syncer to send out data ordered. (*) (*) well actually you can, but only as a side effect of the softupdates callback mechanism, when a buffer write happens and there's softdeps hung off it, a callback is made to back-out changes until the buffer is safe to write out. The problem is that you still have the writecaching going on so the ordering can get messed up. > My "purchased because they threw in a USB Zip-100 and ATA-100 PCI card" > 45G Maxtor is awfully impressive. 32000 blocks of 128k staring 8G from > the begining of the disk resulted in over 30MB/sec according to dd. I'm > stunned. Kernel from mid-Feb. > :P showoff... :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 19:16:10 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from grumpy.dyndns.org (user-24-214-76-236.knology.net [24.214.76.236]) by hub.freebsd.org (Postfix) with ESMTP id 9BE5337B718; Mon, 12 Mar 2001 19:16:00 -0800 (PST) (envelope-from dkelly@grumpy.dyndns.org) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.2/8.11.2) with ESMTP id f2D3DTe08249; Mon, 12 Mar 2001 21:13:29 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200103130313.f2D3DTe08249@grumpy.dyndns.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Alfred Perlstein Cc: Kevin Oberman , Soren Schmidt , mobile@FreeBSD.ORG, stable@FreeBSD.ORG From: David Kelly Subject: Re: Disk I/O problem in 4.3-BETA In-reply-to: Message from Alfred Perlstein of "Mon, 12 Mar 2001 17:14:59 PST." <20010312171459.P18351@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Mar 2001 21:13:29 -0600 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alfred Perlstein writes: > * David Kelly [010312 16:48] wrote: > > > The FreeBSD kernel has a built in daemon called syncer. It sounds like > > a natural place to periodically issue a sync command to such storage > > devices. Assuming such a command exists. > > This won't work. The syncer exists to: [...] > The problem is that you still have the writecaching going on > so the ordering can get messed up. Thanks for the excellent reply. Sitting here thinking, "Duh. I knew that. Why didn't I remember that before sending?" Maybe I can blame it on the low level sinus headache which has made me grumpy all day. > > My "purchased because they threw in a USB Zip-100 and ATA-100 PCI card" > > 45G Maxtor is awfully impressive. 32000 blocks of 128k staring 8G from > > the begining of the disk resulted in over 30MB/sec according to dd. I'm > > stunned. Kernel from mid-Feb. > > > > :P showoff... :) Altho the thread is on writing the above was the read speed. Well, yes and no. Partialy its an atta-boy for Soren. After all, "everybody knows SCSI is the only serious storage media" yet Soren made the ATA stuff scream. I still boot SCSI on this machine because I always have. But no longer fret when budget doesn't allow for SCSI on something at work. Now if I really wanted to brag I'd tell you I got the HD and zip drive from Staples in December for a total of $180 (plus tax). Had to pay $53.90 for the ATA-100 card but my $50 rebate arrived today. :-) -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 19:32:23 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4924737B718; Mon, 12 Mar 2001 19:32:21 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2D3VPI42148; Mon, 12 Mar 2001 20:31:27 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103130331.f2D3VPI42148@harmony.village.org> To: Soren Schmidt Subject: Re: iomega clik! Cc: sos@FreeBSD.org, mobile@FreeBSD.org In-reply-to: Your message of "Mon, 12 Mar 2001 11:17:02 +0100." <200103121017.LAA45917@freebsd.dk> References: <200103121017.LAA45917@freebsd.dk> Date: Mon, 12 Mar 2001 20:31:25 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200103121017.LAA45917@freebsd.dk> Soren Schmidt writes: : OK, here is the "official" patch for the clik, the detach part : is handled by another patch set I have in the wings, that deals : with prober detach/attach of devices, but thats for another time.. : Anyhow I cannot test this, so please let me know if this makes : the clik work... This won't work. The clik! cannot execute afd_prevent_allow(). That's why I added the iomega_clik to the softc. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 21:49:35 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 8520237B719 for ; Mon, 12 Mar 2001 21:49:31 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id WAA08836; Mon, 12 Mar 2001 22:49:30 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id WAA10736; Mon, 12 Mar 2001 22:49:29 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15021.46309.150521.925816@nomad.yogotech.com> Date: Mon, 12 Mar 2001 22:49:25 -0700 (MST) To: The Babbler Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? In-Reply-To: <3AAC4E83.2C281B90@babbleon.org> References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > PS: In my experience, though FreeBSD has lots of advantages, it is > *much* less stable than Linux. It's crashed -way- more than Linux ever > did; more even than Windows does at work (of course I push Windows a lot > less). And I've had it lose files a couple of times when it came back > up after a hard crash like that. > > Is this at all normal? > Is it at all normal for folks with laptops? In the last 4 years on my laptop, I've had 3 crashes, and two of them were related to running the machine completely out of memory. Newer versions of FreeBSD have patches that Matt Dillon wrote to fix these kind of crashes, but I wasn't then (nor am now) running a version with this fix. FreeBSD *rarely* if ever crashes on properly configured, correctly functioning hardware. If you mis-configure things such as VMWARE which get very cozy with the kernel and hardware, you will see crashes. My very strong suspicion is that you're boxed is misconfigured. Unfortunately, Linux may make it easier for you to configure your hardware correctly, so in some respects that it's difficult to configure your hardware correctly could be considered a 'bug' in FreeBSD. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 22:14:54 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from Mail6.nc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 2D0EB37B718 for ; Mon, 12 Mar 2001 22:14:48 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by Mail6.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Tue, 13 Mar 2001 01:14:42 -0500 Message-ID: <3AADBAB8.36039542@babbleon.org> Date: Tue, 13 Mar 2001 01:14:16 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nate Williams Cc: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In fairness to FreeBSD, I've been spending a lot of time getitng things configured and most of my really annoying crashes have been while I was in the midst of configuring or testing my ethernet setup (interface, bridging, networking). But I could do that *without* crashing Linux all the time--essentially the only time it crashes is when you use experimental drivers, in my experience. Perhaps all PCMCIA support under FreeBSD should be considered quasi-experimental or something, but I'm deliberately avoiding using anything but stock 4.2-RELEASSE in order to (hopefully) get maximum stability. For example, it froze both last night and tonight while I was trying to get vmware networking set up properly. But it's not just that; my gateway/firewall just locks up with the PCMCIA light stuck on about every couple of weeks. And making it all especially bad is that I've FreeBSD lose file contents (revert to zero length) after rebooting, even on files that hadn't actually been updated any time close to when the lockup occured. So . . . Perhaps my machine is mis-configured, but how would I go about figuring out what's wrong and configuring it properly? Lord knows I've bugged this list plenty over the past few months trying to get it all right . . . (In fairness, I should note that Linux PCMCIA support appears to be superior to everybody else's. It's certainly superior to Windows as well as FreeBSD.) PS: There are *other* things I like about FreeBSD: The scripts are easier to work with by far. The first real O/S I ever used was BSD circa 1981. I was able to get printing working, including working under Samba, which I could never, ever do with Linux despite untold hours of beating my head against that particular wall. Overall it's worth it anyway, but I was expecting the same or more stability, not a Windows-like tradeoff . . . Sorry, I'm babbling. Anyway, any suggestions for determining the source of such crashes. For the fully-configured system, since the lockups happen only every couple of weeks, it's not really feasible to leave kernel tracing permanently on or anything like that. And these "crashes" of which I speak are system lockups, not kernel panics--there's no recovery possible becuase it locks up tight as a drum and I have to power off. Nor is this just an X display problem, for it also happens to my gateway/firewall, which doesn't even have X installed. How would you deal with such problems? Nate Williams wrote: > > > PS: In my experience, though FreeBSD has lots of advantages, it is > > *much* less stable than Linux. It's crashed -way- more than Linux ever > > did; more even than Windows does at work (of course I push Windows a lot > > less). And I've had it lose files a couple of times when it came back > > up after a hard crash like that. > > > > Is this at all normal? > > Is it at all normal for folks with laptops? > > In the last 4 years on my laptop, I've had 3 crashes, and two of them > were related to running the machine completely out of memory. Newer > versions of FreeBSD have patches that Matt Dillon wrote to fix these > kind of crashes, but I wasn't then (nor am now) running a version with > this fix. > > FreeBSD *rarely* if ever crashes on properly configured, correctly > functioning hardware. If you mis-configure things such as VMWARE which > get very cozy with the kernel and hardware, you will see crashes. > > My very strong suspicion is that you're boxed is misconfigured. > Unfortunately, Linux may make it easier for you to configure your > hardware correctly, so in some respects that it's difficult to configure > your hardware correctly could be considered a 'bug' in FreeBSD. > > Nate > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Mar 12 23:42:20 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 158F737B719; Mon, 12 Mar 2001 23:42:17 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA63705; Tue, 13 Mar 2001 08:40:58 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103130740.IAA63705@freebsd.dk> Subject: Re: iomega clik! In-Reply-To: <200103130331.f2D3VPI42148@harmony.village.org> from Warner Losh at "Mar 12, 2001 08:31:25 pm" To: imp@harmony.village.org (Warner Losh) Date: Tue, 13 Mar 2001 08:40:58 +0100 (CET) Cc: sos@FreeBSD.ORG, mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Warner Losh wrote: > In message <200103121017.LAA45917@freebsd.dk> Soren Schmidt writes: > : OK, here is the "official" patch for the clik, the detach part > : is handled by another patch set I have in the wings, that deals > : with prober detach/attach of devices, but thats for another time.. > : Anyhow I cannot test this, so please let me know if this makes > : the clik work... > > This won't work. The clik! cannot execute afd_prevent_allow(). > That's why I added the iomega_clik to the softc. Thats why I have this in the patch: @@ -423,5 +452,8 @@ int8_t ccb[16] = { ATAPI_PREVENT_ALLOW, 0, 0, 0, lock, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }; - return atapi_queue_cmd(fdp->atp, ccb, NULL, 0, 0,30, NULL, NULL); + if (!strncmp(ATA_PARAM(fdp->atp->controller, fdp->atp->unit)->model, + "IOMEGA Clik!", 12)) + return 0; + return atapi_queue_cmd(fdp->atp, ccb, NULL, 0, 0, 30, NULL, NULL); } -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 0:15:27 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5141E37B719; Tue, 13 Mar 2001 00:15:24 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2D8E2900479; Tue, 13 Mar 2001 01:14:02 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103130814.f2D8E2900479@harmony.village.org> To: Soren Schmidt Subject: Re: iomega clik! Cc: sos@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Tue, 13 Mar 2001 08:40:58 +0100." <200103130740.IAA63705@freebsd.dk> References: <200103130740.IAA63705@freebsd.dk> Date: Tue, 13 Mar 2001 01:14:02 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200103130740.IAA63705@freebsd.dk> Soren Schmidt writes: : Thats why I have this in the patch: : : @@ -423,5 +452,8 @@ : int8_t ccb[16] = { ATAPI_PREVENT_ALLOW, 0, 0, 0, lock, : 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }; : : - return atapi_queue_cmd(fdp->atp, ccb, NULL, 0, 0,30, NULL, NULL); : + if (!strncmp(ATA_PARAM(fdp->atp->controller, fdp->atp->unit)->model, : + "IOMEGA Clik!", 12)) : + return 0; : + return atapi_queue_cmd(fdp->atp, ccb, NULL, 0, 0, 30, NULL, NULL); : } That part of the patch didn't make it to me here. Do you really want to do a string compare for every prevent_allow command? I'd half way expected you to have some kind of quirk table incase iomega comes out with other, newer weirder drives :-). But if that's how you want to do it, then that should work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 0:44:28 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2643E37B718; Tue, 13 Mar 2001 00:44:25 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA80078; Tue, 13 Mar 2001 09:43:06 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103130843.JAA80078@freebsd.dk> Subject: Re: iomega clik! In-Reply-To: <200103130814.f2D8E2900479@harmony.village.org> from Warner Losh at "Mar 13, 2001 01:14:02 am" To: imp@harmony.village.org (Warner Losh) Date: Tue, 13 Mar 2001 09:43:05 +0100 (CET) Cc: sos@FreeBSD.ORG, mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Warner Losh wrote: > In message <200103130740.IAA63705@freebsd.dk> Soren Schmidt writes: > : Thats why I have this in the patch: > : > : @@ -423,5 +452,8 @@ > : int8_t ccb[16] = { ATAPI_PREVENT_ALLOW, 0, 0, 0, lock, > : 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }; > : > : - return atapi_queue_cmd(fdp->atp, ccb, NULL, 0, 0,30, NULL, NULL); > : + if (!strncmp(ATA_PARAM(fdp->atp->controller, fdp->atp->unit)->model, > : + "IOMEGA Clik!", 12)) > : + return 0; > : + return atapi_queue_cmd(fdp->atp, ccb, NULL, 0, 0, 30, NULL, NULL); > : } > > That part of the patch didn't make it to me here. Do you really want > to do a string compare for every prevent_allow command? I'd half way > expected you to have some kind of quirk table incase iomega comes out > with other, newer weirder drives :-). But if that's how you want to > do it, then that should work. Since IOMEGA has decided to make crappy firmware, I guess they deserve this :) BTW does the clik really have the transfer size limit as well ? At any rate I dont think the strcmp matters, all the atapi-fd type devices are painfully slow anyhow ... Somebody should put IOMEGA out of their misery.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 0:48:42 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from gw-nl1.origin-it.com (gw-nl1.origin-it.com [193.79.128.34]) by hub.freebsd.org (Postfix) with ESMTP id EE95E37B718; Tue, 13 Mar 2001 00:48:33 -0800 (PST) (envelope-from Helge.Oldach@de.origin-it.com) Received: from mail.de.origin-it.com (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id JAA15378; Tue, 13 Mar 2001 09:48:31 +0100 (MET) (envelope-from Helge.Oldach@de.origin-it.com) Received: from smtprelay-de1.origin-it.com(172.16.188.53) by gw-nl1.origin-it.com via mwrap (4.0a) id xma015371; Tue, 13 Mar 01 09:48:31 +0100 Received: from mailhub.de.origin-it.com (mailhub.de.origin-it.com [172.16.189.20]) by mail.de.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id JAA29883; Tue, 13 Mar 2001 09:48:30 +0100 (MET) Received: from galaxy.de.cp.philips.com (galaxy.de.cp.philips.com [130.143.166.29]) by mailhub.de.origin-it.com (8.11.2/8.11.2/hmo23oct00) with ESMTP id f2D8mRG94319; Tue, 13 Mar 2001 09:48:28 +0100 (CET) (envelope-from Helge.Oldach@de.origin-it.com) Received: (from hmo@localhost) by galaxy.de.cp.philips.com (8.9.3/8.9.3/hmo14aug98) id JAA08707; Tue, 13 Mar 2001 09:48:27 +0100 (MET) Message-Id: <200103130848.JAA08707@galaxy.de.cp.philips.com> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010312140636.A18351@fw.wintelcom.net> from Alfred Perlstein at "Mar 12, 2001 2: 6:36 pm" To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 13 Mar 2001 09:48:26 +0100 (MET) Cc: oberman@es.net, sos@freebsd.dk, mobile@FreeBSD.ORG, stable@FreeBSD.ORG From: Helge Oldach X-Address: Atos Origin GmbH, Billstrasse 80, D-20539 Hamburg, Germany X-Phone: +49 40 7886 464, Fax: +49 40 7886 235, Mobile: +49 160 4782517 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alfred Perlstein: >* Kevin Oberman [010312 13:46] wrote: >> How serious is the possible corruption issue, anyway. The loss in >> performance is pretty drastic although it may be that dd is an >> especially bad case, but I really don't like to corrupt my disks, >> either. > >If basically running with blind write caching turned on is akin to >running your filesystem in async mode. This is because write >caching gives the drive license to lie about completing a write, >the various ordering of writes are effectively bypassed. If you >crash without these dependancies actually written to the disk, when >you come back up you have a good chance of losing large portions >of your filesystem. I'd say this is a bit too pessimistic. There is a fundamental difference between softupdates and ATA write-cacheing: Softupdates holds the async data in main RAM while ATA write-cacheing already has it in the (cache memory of the) disk device. Obviously a power outage would affect both situations in a similar way. But during just an operating system crash (assuming power stays up), one should be better off with ATA write-cacheing, as the disk should be able to dump the data from the cache chips to the physical medium. With softupdates async data is just lost. Generally I'd say it's not a bad idea to have write caching on the disk enabled - assuming that it is decently implemented. BTW, don't SCSI disks use write cacheing as well? :-) Just my 2¢, Helge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 0:59:37 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0868C37B718; Tue, 13 Mar 2001 00:59:32 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2D8wBX10760; Tue, 13 Mar 2001 00:58:11 -0800 (PST) Date: Tue, 13 Mar 2001 00:58:11 -0800 From: Alfred Perlstein To: Helge Oldach Cc: oberman@es.net, sos@freebsd.dk, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010313005811.J29888@fw.wintelcom.net> References: <20010312140636.A18351@fw.wintelcom.net> <200103130848.JAA08707@galaxy.de.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103130848.JAA08707@galaxy.de.cp.philips.com>; from Helge.Oldach@de.origin-it.com on Tue, Mar 13, 2001 at 09:48:26AM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Helge Oldach [010313 00:48] wrote: > Alfred Perlstein: > >* Kevin Oberman [010312 13:46] wrote: > >> How serious is the possible corruption issue, anyway. The loss in > >> performance is pretty drastic although it may be that dd is an > >> especially bad case, but I really don't like to corrupt my disks, > >> either. > > > >If basically running with blind write caching turned on is akin to > >running your filesystem in async mode. This is because write > >caching gives the drive license to lie about completing a write, > >the various ordering of writes are effectively bypassed. If you > >crash without these dependancies actually written to the disk, when > >you come back up you have a good chance of losing large portions > >of your filesystem. > > I'd say this is a bit too pessimistic. There is a fundamental difference > between softupdates and ATA write-cacheing: Softupdates holds the async > data in main RAM while ATA write-cacheing already has it in the (cache > memory of the) disk device. > > Obviously a power outage would affect both situations in a similar way. > But during just an operating system crash (assuming power stays up), > one should be better off with ATA write-cacheing, as the disk should be > able to dump the data from the cache chips to the physical medium. With > softupdates async data is just lost. > > Generally I'd say it's not a bad idea to have write caching on the disk > enabled - assuming that it is decently implemented. BTW, don't SCSI > disks use write cacheing as well? :-) I'm pretty sure you're wrong. I'm not 100% certain, but many people working with embedded systems have explained to me that it's no longer safe to assume that write cached data will be sync'd to the disk's media at crash time. First off, some disk caches are getting > 10megs, that's a lot of potnetial seeking after loosing power depending on the cache contents... (Also, Matt Dillon wrote how some disks can hold data in the write cache for indefinite amounts of time) Basically, from what's been explained to me, modern disks only retain enough charge/momentum to park (retract) the disk heads when a power outtage occurs, not to write out the cache contents. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 1: 7:34 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from gw-nl1.origin-it.com (gw-nl1.origin-it.com [193.79.128.34]) by hub.freebsd.org (Postfix) with ESMTP id F195037B718; Tue, 13 Mar 2001 01:07:27 -0800 (PST) (envelope-from Helge.Oldach@de.origin-it.com) Received: from mail.de.origin-it.com (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id KAA26098; Tue, 13 Mar 2001 10:07:15 +0100 (MET) (envelope-from Helge.Oldach@de.origin-it.com) Received: from smtprelay-de1.origin-it.com(172.16.188.53) by gw-nl1.origin-it.com via mwrap (4.0a) id xma026082; Tue, 13 Mar 01 10:07:19 +0100 Received: from mailhub.de.origin-it.com (mailhub.de.origin-it.com [172.16.189.20]) by mail.de.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id KAA01308; Tue, 13 Mar 2001 10:07:12 +0100 (MET) Received: from galaxy.de.cp.philips.com (galaxy.de.cp.philips.com [130.143.166.29]) by mailhub.de.origin-it.com (8.11.2/8.11.2/hmo23oct00) with ESMTP id f2D975G94966; Tue, 13 Mar 2001 10:07:06 +0100 (CET) (envelope-from Helge.Oldach@de.origin-it.com) Received: (from hmo@localhost) by galaxy.de.cp.philips.com (8.9.3/8.9.3/hmo14aug98) id KAA08943; Tue, 13 Mar 2001 10:07:04 +0100 (MET) Message-Id: <200103130907.KAA08943@galaxy.de.cp.philips.com> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010313005811.J29888@fw.wintelcom.net> from Alfred Perlstein at "Mar 13, 2001 0:58:11 am" To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 13 Mar 2001 10:07:03 +0100 (MET) Cc: oberman@es.net, sos@freebsd.dk, mobile@FreeBSD.ORG, stable@FreeBSD.ORG From: Helge Oldach X-Address: Atos Origin GmbH, Billstrasse 80, D-20539 Hamburg, Germany X-Phone: +49 40 7886 464, Fax: +49 40 7886 235, Mobile: +49 160 4782517 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alfred Perlstein: >* Helge Oldach [010313 00:48] wrote: >> Alfred Perlstein: >> >If basically running with blind write caching turned on is akin to >> >running your filesystem in async mode. This is because write >> >caching gives the drive license to lie about completing a write, >> >the various ordering of writes are effectively bypassed. If you >> >crash without these dependancies actually written to the disk, when >> >you come back up you have a good chance of losing large portions >> >of your filesystem. >> >> I'd say this is a bit too pessimistic. There is a fundamental difference >> between softupdates and ATA write-cacheing: Softupdates holds the async >> data in main RAM while ATA write-cacheing already has it in the (cache >> memory of the) disk device. >> >> Obviously a power outage would affect both situations in a similar way. >> But during just an operating system crash (assuming power stays up), >> one should be better off with ATA write-cacheing, as the disk should be >> able to dump the data from the cache chips to the physical medium. With >> softupdates async data is just lost. >> >> Generally I'd say it's not a bad idea to have write caching on the disk >> enabled - assuming that it is decently implemented. BTW, don't SCSI >> disks use write cacheing as well? :-) > >I'm pretty sure you're wrong. I think you misunderstood my argument. Agreed, there is practically no difference in the damage done to softupdates versus write-cacheing during a power outage. But there should be a difference when the OS dies away while power stays up. The OS dying away means that the disk has lots of time to spill out the cached data to the physical medium as it's no longer banged at high data rates by the host. So at least in theory we should be better off in this situation. >I'm not 100% certain, but many people working with embedded systems >have explained to me that it's no longer safe to assume that write >cached data will be sync'd to the disk's media at crash time. That may be correct. But then this breaks my naive understanding of "write caching"... And again: Isn't write-cacheing turned on on SCSI disks? :-) Helge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 1:10:46 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 2F90837B719 for ; Tue, 13 Mar 2001 01:10:43 -0800 (PST) (envelope-from mwm@mired.org) Received: (qmail 69166 invoked by uid 100); 13 Mar 2001 09:10:42 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15021.58386.377695.943846@guru.mired.org> Date: Tue, 13 Mar 2001 03:10:42 -0600 To: Helge Oldach Cc: bright@wintelcom.net (Alfred Perlstein), oberman@es.net, sos@freebsd.dk, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <200103130848.JAA08707@galaxy.de.cp.philips.com> References: <20010312140636.A18351@fw.wintelcom.net> <200103130848.JAA08707@galaxy.de.cp.philips.com> X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Helge Oldach types: > Generally I'd say it's not a bad idea to have write caching on the disk > enabled - assuming that it is decently implemented. BTW, don't SCSI > disks use write cacheing as well? :-) Yes, they do. And it's recommended that you turn it off if you turn on softupdates. The driver doesn't do it for you, though. I'd be interested to know details about why softupdates makes it more critical to have write caching off. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 1:19:13 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id A749437B71A; Tue, 13 Mar 2001 01:19:10 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2D9Hq901233; Tue, 13 Mar 2001 02:17:52 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103130917.f2D9Hq901233@harmony.village.org> To: Soren Schmidt Subject: Re: iomega clik! Cc: sos@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Tue, 13 Mar 2001 09:43:05 +0100." <200103130843.JAA80078@freebsd.dk> References: <200103130843.JAA80078@freebsd.dk> Date: Tue, 13 Mar 2001 02:17:51 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200103130843.JAA80078@freebsd.dk> Soren Schmidt writes: : Since IOMEGA has decided to make crappy firmware, I guess they deserve : this :) BTW does the clik really have the transfer size limit as well ? Yes. It won't work without it. : Somebody should put IOMEGA out of their misery.... Agreed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 1:30:46 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1296937B725; Tue, 13 Mar 2001 01:30:40 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2D9TJt11526; Tue, 13 Mar 2001 01:29:19 -0800 (PST) Date: Tue, 13 Mar 2001 01:29:19 -0800 From: Alfred Perlstein To: Helge Oldach Cc: oberman@es.net, sos@freebsd.dk, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010313012919.K29888@fw.wintelcom.net> References: <20010313005811.J29888@fw.wintelcom.net> <200103130907.KAA08943@galaxy.de.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103130907.KAA08943@galaxy.de.cp.philips.com>; from Helge.Oldach@de.origin-it.com on Tue, Mar 13, 2001 at 10:07:03AM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Helge Oldach [010313 01:07] wrote: > Alfred Perlstein: > >* Helge Oldach [010313 00:48] wrote: > >> Alfred Perlstein: > >> >If basically running with blind write caching turned on is akin to > >> >running your filesystem in async mode. This is because write > >> >caching gives the drive license to lie about completing a write, > >> >the various ordering of writes are effectively bypassed. If you > >> >crash without these dependancies actually written to the disk, when > >> >you come back up you have a good chance of losing large portions > >> >of your filesystem. > >> > >> I'd say this is a bit too pessimistic. There is a fundamental difference > >> between softupdates and ATA write-cacheing: Softupdates holds the async > >> data in main RAM while ATA write-cacheing already has it in the (cache > >> memory of the) disk device. > >> > >> Obviously a power outage would affect both situations in a similar way. > >> But during just an operating system crash (assuming power stays up), > >> one should be better off with ATA write-cacheing, as the disk should be > >> able to dump the data from the cache chips to the physical medium. With > >> softupdates async data is just lost. > >> > >> Generally I'd say it's not a bad idea to have write caching on the disk > >> enabled - assuming that it is decently implemented. BTW, don't SCSI > >> disks use write cacheing as well? :-) > > > >I'm pretty sure you're wrong. > > I think you misunderstood my argument. Agreed, there is practically > no difference in the damage done to softupdates versus write-cacheing > during a power outage. huh? I'm confused about "softupdates versus write-cacheing". > But there should be a difference when the OS dies away while power stays > up. The OS dying away means that the disk has lots of time to spill out > the cached data to the physical medium as it's no longer banged at high > data rates by the host. So at least in theory we should be better off in > this situation. No we shouldn't! Either way we should have a consistant filesystem. > >I'm not 100% certain, but many people working with embedded systems > >have explained to me that it's no longer safe to assume that write > >cached data will be sync'd to the disk's media at crash time. > > That may be correct. But then this breaks my naive understanding of > "write caching"... > > And again: Isn't write-cacheing turned on on SCSI disks? :-) It's suggested that it be turned off, see Justin's answers to my previous questions. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 1:34:25 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C6A5E37B71E; Tue, 13 Mar 2001 01:34:21 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2D9X1N11667; Tue, 13 Mar 2001 01:33:01 -0800 (PST) Date: Tue, 13 Mar 2001 01:33:01 -0800 From: Alfred Perlstein To: Mike Meyer Cc: Helge Oldach , oberman@es.net, sos@freebsd.dk, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010313013301.L29888@fw.wintelcom.net> References: <20010312140636.A18351@fw.wintelcom.net> <200103130848.JAA08707@galaxy.de.cp.philips.com> <15021.58386.377695.943846@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15021.58386.377695.943846@guru.mired.org>; from mwm@mired.org on Tue, Mar 13, 2001 at 03:10:42AM -0600 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Mike Meyer [010313 01:10] wrote: > Helge Oldach types: > > Generally I'd say it's not a bad idea to have write caching on the disk > > enabled - assuming that it is decently implemented. BTW, don't SCSI > > disks use write cacheing as well? :-) > > Yes, they do. And it's recommended that you turn it off if you turn on > softupdates. The driver doesn't do it for you, though. Oh great... Perhaps the disk guru's can add some notes to the sfotupdates docco about this? Or did I just miss this? > I'd be interested to know details about why softupdates makes it more > critical to have write caching off. It's always critical to have write caching turned off to ensure filesystem consistancy during an outtage. Having write caching on is like having the disk ignore _any_ filesystem's attempt to do softupdates/logging/delayed-order-writes because the disk _lies_ to the OS about when a write is safely on the disk. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 1:38:44 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3BE1237B718; Tue, 13 Mar 2001 01:38:40 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA95619; Tue, 13 Mar 2001 10:38:30 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103130938.KAA95619@freebsd.dk> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010313013301.L29888@fw.wintelcom.net> from Alfred Perlstein at "Mar 13, 2001 01:33:01 am" To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 13 Mar 2001 10:38:30 +0100 (CET) Cc: mwm@mired.org (Mike Meyer), Helge.Oldach@de.origin-it.com (Helge Oldach), oberman@es.net, mobile@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Alfred Perlstein wrote: > > Having write caching on is like having the disk ignore _any_ > filesystem's attempt to do softupdates/logging/delayed-order-writes > because the disk _lies_ to the OS about when a write is safely on > the disk. Hmm, I think the problem here is that the OS doesn't tell the drivers WHEN it expects to have data written to disk, I can't see why it should not be possible to have even softupdates say "now before I write this I expect everything so far to be on disk". -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 1:43: 8 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.136]) by hub.freebsd.org (Postfix) with ESMTP id 6241237B71A; Tue, 13 Mar 2001 01:43:04 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by phk.freebsd.dk (8.9.3/8.9.3) with ESMTP id KAA39262; Tue, 13 Mar 2001 10:43:02 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f2D9hMp05056; Tue, 13 Mar 2001 10:43:22 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Soren Schmidt Cc: bright@wintelcom.net (Alfred Perlstein), mwm@mired.org (Mike Meyer), Helge.Oldach@de.origin-it.com (Helge Oldach), oberman@es.net, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: Your message of "Tue, 13 Mar 2001 10:38:30 +0100." <200103130938.KAA95619@freebsd.dk> Date: Tue, 13 Mar 2001 10:43:22 +0100 Message-ID: <5054.984476602@critter> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200103130938.KAA95619@freebsd.dk>, Soren Schmidt writes: >It seems Alfred Perlstein wrote: >> >> Having write caching on is like having the disk ignore _any_ >> filesystem's attempt to do softupdates/logging/delayed-order-writes >> because the disk _lies_ to the OS about when a write is safely on >> the disk. > >Hmm, I think the problem here is that the OS doesn't tell the >drivers WHEN it expects to have data written to disk, I can't >see why it should not be possible to have even softupdates >say "now before I write this I expect everything so far to >be on disk". I think it can be done really easy: Whenever a sync(1) is executed and every 30 seconds a flush should be sent. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 1:52: 9 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7F8F237B718; Tue, 13 Mar 2001 01:52:01 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2D9odl12219; Tue, 13 Mar 2001 01:50:39 -0800 (PST) Date: Tue, 13 Mar 2001 01:50:39 -0800 From: Alfred Perlstein To: Soren Schmidt Cc: Mike Meyer , Helge Oldach , oberman@es.net, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010313015039.P29888@fw.wintelcom.net> References: <20010313013301.L29888@fw.wintelcom.net> <200103130938.KAA95619@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103130938.KAA95619@freebsd.dk>; from sos@freebsd.dk on Tue, Mar 13, 2001 at 10:38:30AM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Soren Schmidt [010313 01:38] wrote: > It seems Alfred Perlstein wrote: > > > > Having write caching on is like having the disk ignore _any_ > > filesystem's attempt to do softupdates/logging/delayed-order-writes > > because the disk _lies_ to the OS about when a write is safely on > > the disk. > > Hmm, I think the problem here is that the OS doesn't tell the > drivers WHEN it expects to have data written to disk, I can't > see why it should not be possible to have even softupdates > say "now before I write this I expect everything so far to > be on disk". It doesn't expect that, it just expects you to block until that specific write is on disk. And you're probably right that there's no propogation of this request down to the disk driver level, and yes that's a bug. I said a while back that the most simple "fix" for this was to add another variant of bwrite() that asked for write-through behavior. The reason why simply changing bwrite() to do this is a bad idea is because afaik when there's a lack of buffer space and the kernel is desperately trying to flush buffers it calls bwrite(). In that case, since most likely normal data is being written you _want_ write caching for performance. The reason bwrite() is used instead of bawrite() when we're low on memory is because writes may need additional bufferspace to pull in the indirect blocks, and if you bawrite the data you may wind up deadlocking. Or something like that. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 2: 7:14 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 3FED537B718; Tue, 13 Mar 2001 02:07:10 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from mobile.wemm.org (mobile.wemm.org [10.0.0.5]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f2DA79p39547; Tue, 13 Mar 2001 02:07:09 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f2DA73h54023; Tue, 13 Mar 2001 02:07:07 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200103131007.f2DA73h54023@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Soren Schmidt Cc: bright@wintelcom.net (Alfred Perlstein), mwm@mired.org (Mike Meyer), Helge.Oldach@de.origin-it.com (Helge Oldach), oberman@es.net, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <200103130938.KAA95619@freebsd.dk> Content-Transfer-Encoding: 8bit Date: Tue, 13 Mar 2001 02:07:03 -0800 From: Peter Wemm Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Soren Schmidt wrote: > It seems Alfred Perlstein wrote: > > > > Having write caching on is like having the disk ignore _any_ > > filesystem's attempt to do softupdates/logging/delayed-order-writes > > because the disk _lies_ to the OS about when a write is safely on > > the disk. > > Hmm, I think the problem here is that the OS doesn't tell the > drivers WHEN it expects to have data written to disk, I can't > see why it should not be possible to have even softupdates > say "now before I write this I expect everything so far to > be on disk". Exactly. softupdates depends on the "block done, is on disk now!" notification in order to queue up the next set of dependencies. There is no B_ORDERED or anything. It just snoops the iodone calls. The disk driver has no way of knowing if the fs has something waiting on that given block or not. The alternative is to put B_ORDERED on *every* write from ffs/softdep, which would mean a cache flush after every operation on the ata driver. We cant even look to see if there are dependencies or not on a given block when it is initiated.. because while it is being sent to the drive, another operation can appear that depends on it. It was too late to set the ORDERED bit, so it may not get written to actual disk, and the disk will *LIE* about the completion of the write, and softupdates will queue up the next dependenent transfter, which might make it to disk before the first one that the drive *LIED* about. If your power goes out or the drive gets a hard reset in that window... boom! corrupt fs! hello backups! Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 2:31:59 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from swan.au.en-bio.com (swan.en-bio.COM.AU [203.35.254.3]) by hub.freebsd.org (Postfix) with ESMTP id A685537B71D for ; Tue, 13 Mar 2001 02:31:55 -0800 (PST) (envelope-from TMaher@entigen.com) Received: from shad.au.int.en-bio.com (www-cache.au.en-bio.com [203.35.254.2]) by swan.au.en-bio.com (8.9.1a/8.9.1) with ESMTP id VAA05825 for ; Tue, 13 Mar 2001 21:31:47 +1100 Received: (from tonym@localhost) by shad.au.int.en-bio.com (8.9.1b+Sun/8.9.1) id VAA16508 for mobile@freebsd.org; Tue, 13 Mar 2001 21:32:47 +1100 (EST) Date: Tue, 13 Mar 2001 21:32:47 +1100 (EST) From: Tony Maher Message-Id: <200103131032.VAA16508@shad.au.int.en-bio.com> To: mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nate Williams wrote: > > Is this at all normal? > > Is it at all normal for folks with laptops? > > In the last 4 years on my laptop, I've had 3 crashes, and two of them > were related to running the machine completely out of memory. Newer > versions of FreeBSD have patches that Matt Dillon wrote to fix these > kind of crashes, but I wasn't then (nor am now) running a version with > this fix. > > FreeBSD *rarely* if ever crashes on properly configured, correctly > functioning hardware. If you mis-configure things such as VMWARE which > get very cozy with the kernel and hardware, you will see crashes. > > My very strong suspicion is that you're boxed is misconfigured. I am not sure I would necessarily come to that conclusion. My own experience has been that desktop/server boxes are extremely stable (its hard to remember when one crashed) but my laptop crashes more often. Suspending while ppp is running is sure to do it (so I dont do that!). But sometimes after disconnecting from network and moving to another desk and forgetting to plug back in and just leaving it sit, it just reboots after a while (sometimes). (actually have crashdump of this last one - but I could not get anything out of it that made sense - but that could just be my inexperience) Maybe its just the particular laptop that gives trouble (mine is Dell inspiron 3500). In doing a little testing for Boris Popov smbfs work he discovered a certain problem only existed with Dell notebooks, his comment "Wow, in all cases this is a Dell notebooks..." The only common thing appears to be changes in network but nothing reproducable (except for the smbfs early versions and suspending while using ppp). But its less than 1 crash a month and the laptops in use home/work 7 days a week. It could be random hardware failure but the correlation with network changes tends to rule it out. just my 2c tonym ps. also more rarely I get an X problem that screws the machine too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 3:28:33 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id EA3AC37B745; Tue, 13 Mar 2001 03:28:24 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2DBQZD14553; Tue, 13 Mar 2001 03:26:35 -0800 (PST) Date: Tue, 13 Mar 2001 03:26:35 -0800 From: Alfred Perlstein To: Mars Attack Cc: Soren Schmidt , Peter Wemm , Mike Meyer , Helge Oldach , oberman@es.net, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010313032635.Q29888@fw.wintelcom.net> References: <200103131007.f2DA73h54023@mobile.wemm.org> <01f001c0abaa$133e1680$4500a8c0@nomad> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01f001c0abaa$133e1680$4500a8c0@nomad>; from marsattack@cannoncreek.com on Tue, Mar 13, 2001 at 06:40:46PM +0800 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Mars Attack [010313 02:18] wrote: > Geez, this thread is getting longer and all the more confusing, can some > guru possibly attempt to outline the good and bad points of Softupdates or > WC ? 1) softupdates good 2) WC bad (even when not using softupdates) Basically, softupdates doesn't really matter, as long as you have write caching turned on, you're defeating the safeness of FFS (noasync) and FFS (softdep) by allowing the disk to reorder what should be ordered writes. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 3:51:22 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id 646A537B71D; Tue, 13 Mar 2001 03:51:19 -0800 (PST) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.22 #1) id 14cnKZ-0005ZI-00; Tue, 13 Mar 2001 11:51:11 +0000 To: bright@wintelcom.net, Helge.Oldach@de.origin-it.com Subject: Re: Disk I/O problem in 4.3-BETA Cc: mobile@FreeBSD.ORG, oberman@es.net, sos@freebsd.dk, stable@FreeBSD.ORG In-Reply-To: <20010313005811.J29888@fw.wintelcom.net> Message-Id: From: Pete French Date: Tue, 13 Mar 2001 11:51:11 +0000 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org All very interesting, but a small point has been forgotten hasnt it ? The way I read this thread is that until recentlly write-caching was enabled by default and has now been disabled (hence the original obseravtion of disc performance dropping). I havent noticed that FreeBSD has a bad reputation for loss of data in the event of am power outage, and my own experience backs this up. As so many people appear to have been running it this way by default until now you might have though that if it were a serious problem in reality then people would have noticed by now ? -pete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 3:54:19 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from oz.core.gelsen-net.de (oz.core.gelsen-net.de [195.145.169.11]) by hub.freebsd.org (Postfix) with ESMTP id C898637B721 for ; Tue, 13 Mar 2001 03:54:16 -0800 (PST) (envelope-from jojo@Leidinger.net) Received: from BigBrother.leidinger.net (pm3227.dial.gelsen-net.de [212.6.182.91]) by oz.core.gelsen-net.de (8.8.8/8.8.8) with ESMTP id MAA29523 for ; Tue, 13 Mar 2001 12:52:09 +0100 (MET) Received: (from jojo@localhost) by BigBrother.leidinger.net (8.11.3/8.11.3) id f2DBoH901143 for mobile@freebsd.org; Tue, 13 Mar 2001 12:50:17 +0100 (CET) (envelope-from jojo) Message-Id: <200103131150.f2DBoH901143@BigBrother.leidinger.net> Date: Tue, 13 Mar 2001 12:50:16 +0100 (CET) From: jojo@blackpoint.de Subject: Fujitsu-Siemens Lifebook E-Serie? To: mobile@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear reader, I've read the README.TXT (FreeBSD 4.2) and Cards (X11). It seems to me, I can buy the E-Serie (E-6180/6540/6550/6560) with internal modem (for WIN only) and buy an extra PCMCIA-Card 3COM 3CCFE574BT. Has someone a good experience with Fujitsu-Siemens Liefbook E-Serie? Are there any problems with that hardware on FreeBSD? Any comments, hints and tips are very welcome. Sorry for my bad english! Thanks! Joachim -- --------------------------------------------------------------- Hans-Joachim Leidinger black point arts Internet Solutions GmbH email: jojo@blackpoint.de FAX : +49 0209-398265 http://www.bpaserver.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 3:58: 6 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3F19037B71D; Tue, 13 Mar 2001 03:58:03 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2DBvtD15382; Tue, 13 Mar 2001 03:57:55 -0800 (PST) Date: Tue, 13 Mar 2001 03:57:55 -0800 From: Alfred Perlstein To: Pete French Cc: Helge.Oldach@de.origin-it.com, mobile@FreeBSD.ORG, oberman@es.net, sos@freebsd.dk, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA Message-ID: <20010313035755.S29888@fw.wintelcom.net> References: <20010313005811.J29888@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from pfrench@firstcallgroup.co.uk on Tue, Mar 13, 2001 at 11:51:11AM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Pete French [010313 03:51] wrote: > All very interesting, but a small point has been forgotten > hasnt it ? The way I read this thread is that until recentlly > write-caching was enabled by default and has now been disabled (hence > the original obseravtion of disc performance dropping). > > I havent noticed that FreeBSD has a bad reputation for loss of data > in the event of am power outage, and my own experience backs this up. > As so many people appear to have been running it this way by default until > now you might have though that if it were a serious problem in reality then > people would have noticed by now ? Your optimism is appreciated, however just because you can't see the approaching hordes doesn't mean they're not at the gates. To be true to our users, we need to either: 1) turn off write caching. 2) propogate bwrite() intention down to the device layer. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 4: 1:53 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from amleth.demon.co.uk (amleth.demon.co.uk [158.152.198.225]) by hub.freebsd.org (Postfix) with SMTP id 19FE537B725 for ; Tue, 13 Mar 2001 04:01:39 -0800 (PST) (envelope-from PEB@amleth.demon.co.uk) Date: Tue, 13 Mar 2001 09:53:19 GMT From: PEB@amleth.demon.co.uk (Paul E. Bennett) Reply-To: peb@amleth.demon.co.uk Message-Id: <6530@amleth.demon.co.uk> To: nate@yogotech.com, (Nate Williams) Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? X-Mailer: PCElm 1.10 Lines: 57 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <15021.46309.150521.925816@nomad.yogotech.com> Nate Williams writes: > > PS: In my experience, though FreeBSD has lots of advantages, it is > > *much* less stable than Linux. It's crashed -way- more than Linux ever > > did; more even than Windows does at work (of course I push Windows a lot > > less). And I've had it lose files a couple of times when it came back > > up after a hard crash like that. > > > > Is this at all normal? > > Is it at all normal for folks with laptops? [%X] > My very strong suspicion is that you're boxed is misconfigured. > Unfortunately, Linux may make it easier for you to configure your > hardware correctly, so in some respects that it's difficult to configure > your hardware correctly could be considered a 'bug' in FreeBSD. Perhaps we might consider the lack of a probe utility that reports back to the configuration engineer as a bug too. To someone who is, admittedly, new to FreeBSD but who likes what he has seen of it so far, I find that lack of a single utility that you can be told to run which will properly discover what hardware you have attached makes resolving proper configuartion more difficult. Being told, as we have been, to use the Windows 9x/2k facilities to do such probing would seem to be a bit of an admission that the FreeBSD people have missed something important from the system. It would seem to be more important to have such utilities these days as many hardware manufactures are being really mean in the povision of information about their products. They just provide a disk that will configure the system for Win9x/2k and dis-regard any other OS possibility. OK, probe detection requires that the facilities for it are built in to the probeable hardware. That was what the PnP issue was all about. I get better results from my control systems (which are all probable over the networks - but then I build them that way). Incidently, I too have PCMCIA issues, raised through here, the misc newsgroup and in email to those on the PAO project but have yet to get resolved on my problems. I am a bit limited in time I can spend plodding through all the masses of documentation as I need to do other things with my days beside get my Dell laptop properly sorted (starting to wish for 80 hour days here) but I would like to soon be able to transfer my email, web-acces and other work related stuff to that. I am, however, beginning to know the way in which I want it all to operate. Now, is 4.3R going to have PCMCIA Ether/Modem combo-card support? -- ******************************************************************** Paul E. Bennett .................... Forth based HIDECS Consultancy ..... Mob: +44 (0)7811-639972 .........NOW AVAILABLE:- HIDECS COURSE...... Tel: +44 (0)1235-814586 .... see http://www.feabhas.com for details. Going Forth Safely ..... EBA. www.electric-boat-association.org.uk.. ******************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 4: 1:59 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from hugo10.ka.punkt.de (kagate.punkt.de [194.77.232.254]) by hub.freebsd.org (Postfix) with ESMTP id 3537337B737; Tue, 13 Mar 2001 04:01:53 -0800 (PST) (envelope-from hausen@punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.9.3/8.9.3) id NAA88345; Tue, 13 Mar 2001 13:01:45 +0100 (CET) (envelope-from ry93) From: "Patrick M. Hausen" Message-Id: <200103131201.NAA88345@hugo10.ka.punkt.de> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: from Pete French at "Mar 13, 2001 11:51:11 am" To: pfrench@firstcallgroup.co.uk (Pete French) Date: Tue, 13 Mar 2001 13:01:45 +0100 (CET) Cc: bright@wintelcom.net, Helge.Oldach@de.origin-it.com, mobile@FreeBSD.ORG, oberman@es.net, sos@freebsd.dk, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all! Pete wrote: > All very interesting, but a small point has been forgotten > hasnt it ? The way I read this thread is that until recentlly > write-caching was enabled by default and has now been disabled (hence > the original obseravtion of disc performance dropping). > > I havent noticed that FreeBSD has a bad reputation for loss of data > in the event of am power outage, and my own experience backs this up. > As so many people appear to have been running it this way by default until > now you might have though that if it were a serious problem in reality then > people would have noticed by now ? Well, there are a great number of people running Linux with async mounts, who haven't experienced loss of data either. And they will happily tell you that living fast and loose was the way it's meant to be and, BTW, it gives much better performance ... The point in Kirk's work on softupdates was to provide a way to live "almost asynchronously" while _guaranteeing_ filesystem meta data consistency. This guarantee is lost with WC enabled, so you might as well mount async and join the "fast and loose" crowd. Only recently was softupdates included in the GENERIC kernel, so my impression is that because softupdates is now kind of default, the problem with WC popped up and was solved in the "do the right thing [tm]" manner. You are free to reenable WC any time you like. HTH, Patrick -- --- WEB ISS GmbH - Scheffelstr. 17a - 76135 Karlsruhe - 0721/9109-0 --- ------ Patrick M. Hausen - Technical Director - hausen@punkt.de ------- "Two men say, they're Jesus - one of 'em must be wrong." (Dire Straits) > > -pete. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 4:48:16 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id A919F37B720; Tue, 13 Mar 2001 04:48:10 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f2DCjuB22590; Tue, 13 Mar 2001 07:45:56 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200103131245.f2DCjuB22590@hda.hda.com> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010313035755.S29888@fw.wintelcom.net> from Alfred Perlstein at "Mar 13, 2001 03:57:55 am" To: Alfred Perlstein Date: Tue, 13 Mar 2001 07:45:55 -0500 (EST) Cc: mobile@freebsd.org, stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > * Pete French [010313 03:51] wrote: > > All very interesting, but a small point has been forgotten > > hasnt it ? The way I read this thread is that until recentlly > > write-caching was enabled by default and has now been disabled (hence > > the original obseravtion of disc performance dropping). > > > > I havent noticed that FreeBSD has a bad reputation for loss of data > > in the event of am power outage, and my own experience backs this up. > > As so many people appear to have been running it this way by default until > > now you might have though that if it were a serious problem in reality then > > people would have noticed by now ? > > Your optimism is appreciated, however just because you can't see > the approaching hordes doesn't mean they're not at the gates. > > To be true to our users, we need to either: > > 1) turn off write caching. > 2) propogate bwrite() intention down to the device layer. I haven't been following this too closely, but if "2)" means use ordering commands to the drive firmware to ensure block ordering you need a warning about using an UPS and being nervous about disk firmware revs. I think write cache enable with an UPS and SCSI drives that grew up in a workstation environment is safe, now with either mass-market drives or counting on block ordering firmware working properly I get nervous too, and with soft updates reducing the disk overhead maybe it just isn't worth it. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 5:16:34 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail7.nc.rr.com (fe7.southeast.rr.com [24.93.67.54]) by hub.freebsd.org (Postfix) with ESMTP id 2DDBB37B722 for ; Tue, 13 Mar 2001 05:16:31 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail7.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Tue, 13 Mar 2001 08:16:25 -0500 Message-ID: <3AAE1D92.37D743FC@babbleon.org> Date: Tue, 13 Mar 2001 08:16:02 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Tony Maher Cc: mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <200103131032.VAA16508@shad.au.int.en-bio.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tony Maher wrote: > > Nate Williams wrote: > > > > Is this at all normal? > > > Is it at all normal for folks with laptops? > > > > My very strong suspicion is that you're boxed is misconfigured. > > Maybe its just the particular laptop that gives trouble (mine is Dell inspiron > 3500). In doing a little testing for Boris Popov smbfs work he discovered > a certain problem only existed with Dell notebooks, his comment > "Wow, in all cases this is a Dell notebooks..." My primary machine is a Dell Inspiron, too. > > The only common thing appears to be changes in network but nothing > reproducable (except for the smbfs early versions and suspending while using > ppp). But its less than 1 crash a month and the laptops in use home/work > 7 days a week. Most of my crashes (probably all of them, but it's hard to tell) have involved messing around with network paraeters and/or inserting/removing a network card. So there might be a pattern here . . . > tonym > ps. also more rarely I get an X problem that screws the machine too. This could happen in Linux as well, so I don't think is O/S dependent. I've never had it happen on FreeBSd, but that's probably because I've only been running a few months. KDE does lockup at the KDE level on logoff sometimes, but CTL-ALT-BS and CTL-ALT-F? will get control back. The troublesome lockups are at a lower level. And it's *not* a memory starvation problem; I had *that* issue with Linux owing to a Netscape bug that sometimes would make it start wildly consuming memory, so I keep xosview up all the time to monitor memory usage. PS: A weird thing--I run the Linux version of Netscape, because the BSD version crashes before it even brings up a window. It doesn't have the memory consumption bug! (I mean it uses a lot memory, but under Linux, Netscape would fairly frequently [like every few days] go on a memory rampage where the memory meter would just start climbing towards infinity, and I'd have to kill the Netscape process to prevent an eventual memory-starvation crash. That has *never* happened under FreeBSD. So my experience is: kudos to FreeBSD for better memory management, but there seems to be some weakness in (of all things) the networking code. (I say "of all things" because FreeBSD advocates are frequently most proud of the networking code . . . indeed it's a reason I switched to FreeBSD, but it's given me plenty of trouble.) -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 5:45:28 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mobile.hub.org (mobile.acadiau.ca [131.162.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 352F037B731 for ; Tue, 13 Mar 2001 05:45:26 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f2DDiJD67539; Tue, 13 Mar 2001 09:44:29 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Tue, 13 Mar 2001 09:44:19 -0400 (AST) From: The Hermit Hacker To: Juriy Goloveshkin Cc: Subject: Re: Sony VAIO: hibernation to disk vs ram? In-Reply-To: <20010310120317.A663@avias.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 10 Mar 2001, Juriy Goloveshkin wrote: > On Fri, Mar 09, 2001 at 07:38:51PM -0400, The Hermit Hacker wrote: > > can someone tell me how to *properly* suspend FreeBSD on a VAIO? I > > have a 207Meg (192Meg of RAM) 'file system' at the end of the disk for the > > dump to disk ... hitting fn-f12 appears to do a 'to RAM' suspend, which,of > > course, is draining my battery somewhat, reducing the battery lifetime ... > How did you create this 'file system'? fdisk on the boot disk with my FreeBSD boot ... subtype of 160 ... size is 423360 (~207Meg) according to the 'FDISK Partition Editor' ... > The right way is to use utility from vaio compact disk(in disk boot image). > You can also do this without utility by creating partition with sysid > 160(the place on disk is where you want, but the number of partition > migth be important - 4th). Okay, I just made it last partition on the drive, but you don't think that will work? basically, WinDoze, FreeBSD then subtype 160 ... > don't forget about cold reboot... > don't use acpica, only apm. acpica vs apm? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 7:35:23 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by hub.freebsd.org (Postfix) with ESMTP id 6B61F37B727 for ; Tue, 13 Mar 2001 07:35:17 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 14cqpL-0001vV-00 for freebsd-mobile@FreeBSD.ORG; Tue, 13 Mar 2001 10:35:11 -0500 Date: Tue, 13 Mar 2001 10:35:10 -0500 From: Peter Radcliffe To: freebsd-mobile@FreeBSD.ORG Subject: Re: Sony VAIO: hibernation to disk vs ram? Message-ID: <20010313103510.A6592@pir.net> Reply-To: mobile@freebsd.org Mail-Followup-To: freebsd-mobile@FreeBSD.ORG References: <20010310120317.A663@avias.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scrappy@hub.org on Tue, Mar 13, 2001 at 09:44:19AM -0400 X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The Hermit Hacker probably said: > On Sat, 10 Mar 2001, Juriy Goloveshkin wrote: > fdisk on the boot disk with my FreeBSD boot ... subtype of 160 ... size is > 423360 (~207Meg) according to the 'FDISK Partition Editor' ... > > > The right way is to use utility from vaio compact disk(in disk boot image). > > > You can also do this without utility by creating partition with sysid > > 160(the place on disk is where you want, but the number of partition > > migth be important - 4th). The partition number does seem to be significant. The exact correct soze and position on the disk also seem to be significant. It also has to be under 8Gb for the bios to use it. > Okay, I just made it last partition on the drive, but you don't think that > will work? basically, WinDoze, FreeBSD then subtype 160 ... A suspend to disk partition created with anything but the phdisk.exe utility will not work, in my experience. If you have identical disks and identical laptop models you can take the details created by phdisk.exe one one machine and use them on another, but I've tried several times to create partitions for suspend to disk on new machines/disks and other than phdisk.exe none of them worked for whatever reason. Forget creating it manually and use phdisk.exe. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 7:43:15 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 5E81A37B722; Tue, 13 Mar 2001 07:43:08 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA13599; Tue, 13 Mar 2001 07:42:52 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda13595; Tue Mar 13 07:42:46 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f2DFgeT04673; Tue, 13 Mar 2001 07:42:40 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdUp4670; Tue Mar 13 07:41:56 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.3/8.9.1) id f2DFfte07457; Tue, 13 Mar 2001 07:41:55 -0800 (PST) Message-Id: <200103131541.f2DFfte07457@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdBS7450; Tue Mar 13 07:41:14 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Pete French Cc: bright@wintelcom.net, Helge.Oldach@de.origin-it.com, mobile@FreeBSD.ORG, oberman@es.net, sos@freebsd.dk, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-reply-to: Your message of "Tue, 13 Mar 2001 11:51:11 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Mar 2001 07:41:14 -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Pete French writes: > All very interesting, but a small point has been forgotten > hasnt it ? The way I read this thread is that until recentlly > write-caching was enabled by default and has now been disabled (hence > the original obseravtion of disc performance dropping). > > I havent noticed that FreeBSD has a bad reputation for loss of data > in the event of am power outage, and my own experience backs this up. > As so many people appear to have been running it this way by default until > now you might have though that if it were a serious problem in reality then > people would have noticed by now ? Operating systems which write their metadata asynchronously are worse for data loss during power failure than FreeBSD. My experiences with FreeBSD in this area have been excellent: Much better data integrity during power failure than Linux and the commercial UNIX systems. Any loss of data that I've experienced on a FreeBSD system has either been a hardware problem or I have been the cause of the data loss. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 7:47:17 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by hub.freebsd.org (Postfix) with ESMTP id C1D3E37B719 for ; Tue, 13 Mar 2001 07:47:13 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 14cr0y-0001zy-00 for freebsd-mobile@freebsd.org; Tue, 13 Mar 2001 10:47:12 -0500 Date: Tue, 13 Mar 2001 10:47:11 -0500 From: Peter Radcliffe To: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Message-ID: <20010313104711.B6592@pir.net> Reply-To: mobile@freebsd.org Mail-Followup-To: freebsd-mobile@freebsd.org References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AADBAB8.36039542@babbleon.org>; from bts@babbleon.org on Tue, Mar 13, 2001 at 01:14:16AM -0500 X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The Babbler probably said: > Perhaps all PCMCIA support under FreeBSD should be considered > quasi-experimental or something, but I'm deliberately avoiding using > anything but stock 4.2-RELEASSE in order to (hopefully) get maximum > stability. PCMCIA under freebsd seems far more stable than Linux PCMCIA support when _correctly_ _configured_. I've helped dozens of people get wavelan support working at conferences and getting it as stable with Linux requires the exact correct versions (and the only way to find them is to test) of half a dozen things ... > For example, it froze both last night and tonight while I was trying to > get vmware networking set up properly. vmware messes with things at a pretty low level and isn't designed for FreeBSD. It's going to cause problems. Having said that, once I got it set up properly (you did read the FreeBSD readme, didn't you ?) it hasn't crashed the host OS on my machine in a long time. > But it's not just that; my gateway/firewall just locks up with the > PCMCIA light stuck on about every couple of weeks. I would assume you have a misconfiguration or a hardware problem. I've had freebsd boxes doing routing/filtering/pcmcia up for _months_ with no problems. > And making it all especially bad is that I've FreeBSD lose file contents > (revert to zero length) after rebooting, even on files that hadn't > actually been updated any time close to when the lockup occured. Never seen that in my last few years of freebsd use. > (In fairness, I should note that Linux PCMCIA support appears to be > superior to everybody else's. It's certainly superior to Windows as > well as FreeBSD.) Can't disagree strongly enough. > Anyway, any suggestions for determining the source of such crashes. For > the fully-configured system, since the lockups happen only every couple > of weeks, it's not really feasible to leave kernel tracing permanently > on or anything like that. And these "crashes" of which I speak are > system lockups, not kernel panics--there's no recovery possible becuase > it locks up tight as a drum and I have to power off. Nor is this just > an X display problem, for it also happens to my gateway/firewall, which > doesn't even have X installed. > > How would you deal with such problems? Double and triple check for any irq/memory problems and then start using DDB and DIAGNOSTIC. It's the only sane way to debug hard hangs. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 8:12:39 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 87DD337B723 for ; Tue, 13 Mar 2001 08:12:37 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id 5ED6E5E3B; Tue, 13 Mar 2001 17:12:39 +0100 (CET) Date: Tue, 13 Mar 2001 17:12:39 +0100 From: Dave Boers To: freebsd-mobile@freebsd.org Subject: Anyone experience with Asus L8400C or L8400K? Message-ID: <20010313171239.A33050@relativity.student.utwente.nl> Reply-To: djb@quantum-physics.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-key: ftp://relativity.student.utwente.nl/pub/pgpkeys/djb.asc Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, Does anybody here have experience with FreeBSD on an Asus L8400C or L8400K? I'm thinking seriously about getting one (or rather: my employer) and of course I want a sane OS on it. Thanks, Dave Boers. -- GOD is real, unless declared integer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 10:41: 7 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 48CC537B71A for ; Tue, 13 Mar 2001 10:41:03 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f2DIeka17000; Tue, 13 Mar 2001 10:40:46 -0800 Date: Tue, 13 Mar 2001 10:40:46 -0800 From: Brooks Davis To: The Babbler Cc: Tony Maher , mobile@FreeBSD.ORG Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Message-ID: <20010313104046.A13119@Odin.AC.HMC.Edu> References: <200103131032.VAA16508@shad.au.int.en-bio.com> <3AAE1D92.37D743FC@babbleon.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3AAE1D92.37D743FC@babbleon.org>; from bts@babbleon.org on Tue, Mar 13, 2001 at 08:16:02AM -0500 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 13, 2001 at 08:16:02AM -0500, The Babbler wrote: > So my experience is: kudos to FreeBSD for better memory management, but > there seems to be some weakness in (of all things) the networking code.= =20 > (I say "of all things" because FreeBSD advocates are frequently most > proud of the networking code . . . indeed it's a reason I switched to > FreeBSD, but it's given me plenty of trouble.) The part of the networking code people are usually talking about is the TCP/IP stack. From what I've read of your comments that's no the part you are messing with. Rather you're messing with driver settings and bridging. Bridging has a MUCH smaller audience then TCP/IP so obviously it's less tested. Add the fact that you're using it with Linux emulation and an application that get very intimate with the OS internals stability problems aren't exactly suprising. -- Brooks P.S. IMNSHO running 4.2-RELEASE instead of 4-STABLE for stability is a very odd idea. It's quite likely a bug that effects you there has been fixed in a later version. Of course you run the risk of finding new bugs, but that's always the case. --=20 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 --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6rmmtXY6L6fI4GtQRAlkqAJ4qHyRxcXxW5BQcPuc1nwalrRKsFQCghKkW hkJolOMvCa8m5uRxbWymKEM= =j4ht -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 10:57:59 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from macnews.de (webmail.macnews.de [195.8.237.93]) by hub.freebsd.org (Postfix) with ESMTP id E3AC237B719 for ; Tue, 13 Mar 2001 10:57:55 -0800 (PST) (envelope-from eric@macnews.de) Received: from [217.81.130.233] (account ) by macnews.de (CommuniGate Pro WebUser 3.4.1) with HTTP id 1117865 for ; Tue, 13 Mar 2001 19:57:54 +0100 From: Eric Knauel Subject: pccardc: device not configured To: freebsd-mobile@FreeBSD.ORG X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Tue, 13 Mar 2001 19:57:54 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm quite new to FreeBSD and I hope my question is not to dumb. ;-) Yesterday, I installed FreeBSD 4.2 on my notebook and everything -- expect sound -- worked perfectly. That's why I build a custom kernel which only differs from GENERIC in support for "device pcm". Okay, the build-process worked fine, the sound support also worked perfectly. However, now PCMCIA-support is broken! In dmesg's output I can find : pcic-pci0: at device 10.0 on pci0 pcic-pci1: at device 10.1 on pci0 That's okay. /etc/rc.conf has a line pccard_enable="YES", I guess that's why pccardc is called during the boot process: pcacardc: /dev/card0: device not configured Hmm... What does that mean? I already tried to re-make /dev/card* entries with MAKEDEV, didn't help. pccardd doesn't work of course: "fatal error: no PC-CARD slots" and pccardc dumpcis doesn't work either. What can I do? Ciao, Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 14:48:41 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from web3102.mail.yahoo.com (web3102.mail.yahoo.com [204.71.202.187]) by hub.freebsd.org (Postfix) with SMTP id B103437B718 for ; Tue, 13 Mar 2001 14:48:37 -0800 (PST) (envelope-from guangruifu@yahoo.com) Message-ID: <20010313224837.21080.qmail@web3102.mail.yahoo.com> Received: from [216.98.102.225] by web3102.mail.yahoo.com; Tue, 13 Mar 2001 14:48:37 PST Date: Tue, 13 Mar 2001 14:48:37 -0800 (PST) From: Guangrui Fu Subject: Mobile IP implementation for FreeBSD To: mobile-ip , freebsd-net , freebsd-mobile MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm looking for open-sourced Mobile IP implementation on FreeBSD. Could anyone please give me some information? Many thanks, Guangrui __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 20: 4:33 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from grumpy.dyndns.org (user-24-214-76-236.knology.net [24.214.76.236]) by hub.freebsd.org (Postfix) with ESMTP id E013737B718; Tue, 13 Mar 2001 20:04:27 -0800 (PST) (envelope-from dkelly@grumpy.dyndns.org) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.2/8.11.2) with ESMTP id f2E44Ne16415; Tue, 13 Mar 2001 22:04:24 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200103140404.f2E44Ne16415@grumpy.dyndns.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Pete French Cc: mobile@FreeBSD.ORG, sos@freebsd.dk, stable@FreeBSD.ORG From: David Kelly Subject: Re: Disk I/O problem in 4.3-BETA In-reply-to: Message from Pete French of "Tue, 13 Mar 2001 11:51:11 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Mar 2001 22:04:23 -0600 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Pete French writes: > All very interesting, but a small point has been forgotten > hasnt it ? The way I read this thread is that until recentlly > write-caching was enabled by default and has now been disabled (hence > the original obseravtion of disc performance dropping). > > I havent noticed that FreeBSD has a bad reputation for loss of data > in the event of am power outage, and my own experience backs this up. > As so many people appear to have been running it this way by default until > now you might have though that if it were a serious problem in reality then > people would have noticed by now ? Well, I am an ex-Linux user who got fed up with Linux trashing my disk 3 times one week. Each time (kernel panics) the damage was bad enough fsck (e2fsck?) deleted a lot of critical files making a wipe/reinstall the fastest way back to a running system. This was shortly after the release of FreeBSD 2.0.0. Remember it well because that is when I became a FreeBSD user. Hmm, probably 6 years ago this month. Have watched Linux from "outside" since then. Noticed I was not the only one losing data. From what I've seen the Linux solution was not to to fix a faulty design but to hack it until it doesn't lose as much. Linux was/is very proud of their ext2fs speed. Clearly at the expense of reliability. Oddly enough that machine got 600k Bytes/sec thruput on Linux, but 900k Bytes/sec on FreeBSD 2.0.0-RELEASE. 240 MB Western Digital IDE drive. IMO the most reliable settings are the correct thing to do in spite of simpleminded magazine authors who will "do a shootout" of Linux vs. FreeBSD using only the stock settings. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 21:41:55 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail5.nc.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E51337B718; Tue, 13 Mar 2001 21:41:45 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail5.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 14 Mar 2001 00:41:44 -0500 Message-ID: <3AAF047F.341981B2@babbleon.org> Date: Wed, 14 Mar 2001 00:41:20 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: mobile@freebsd.org Cc: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Radcliffe wrote: > > The Babbler probably said: > > Perhaps all PCMCIA support under FreeBSD should be considered > > quasi-experimental or something, but I'm deliberately avoiding using > > anything but stock 4.2-RELEASSE in order to (hopefully) get maximum > > stability. > > PCMCIA under freebsd seems far more stable than Linux PCMCIA support > when _correctly_ _configured_. I've helped dozens of people get > wavelan support working at conferences and getting it as stable with > Linux requires the exact correct versions (and the only way to find > them is to test) of half a dozen things ... I haven't used WaveLANS, but every PCMCIA I ever stuck in my Linux box just worked. I've had to buy cards to get them to work with FreeBSD. My Linksys EtherFast Modem/Ethernet card is sitting a drawer in my desk because I finally gave up on it and bought a new (and more physically awkward) card for FreeBSD. You can search for old postings of my back in January or so for the saga on *that*. Similarly, I could *never* get two identical cards to work on my gateway machine; I finally bought a card to make FreeBSD happy. With Linux it just worked. Easy. To say the least, then, my experience does not concord with yours in this regard. > > For example, it froze both last night and tonight while I was trying to > > get vmware networking set up properly. > > vmware messes with things at a pretty low level and isn't designed for > FreeBSD. It's going to cause problems. Having said that, once I got it > set up properly (you did read the FreeBSD readme, didn't you ?) it > hasn't crashed the host OS on my machine in a long time. I read the FreeBSD readme. And I've had a nubmer of posting in the emultors group as I got things working there, too. The bridging would never work for me, but my final conclusion is that my card doesn't work with bridging, I guess. Only some cards do. (It says *that* in the handbook and the bridge man page.) > > But it's not just that; my gateway/firewall just locks up with the > > PCMCIA light stuck on about every couple of weeks. > > I would assume you have a misconfiguration or a hardware problem. > I've had freebsd boxes doing routing/filtering/pcmcia up for > _months_ with no problems. PCMCIA-based laptops or desktops? > > And making it all especially bad is that I've FreeBSD lose file contents > > (revert to zero length) after rebooting, even on files that hadn't > > actually been updated any time close to when the lockup occured. > > Never seen that in my last few years of freebsd use. Happened to me twice within days of my install. Both times it was "cal.vcs," for what it's worth. That's the calendar database for korganize, which *is* loaded, but would have had no reason to be writing to disk when I crashed. I never lost any files under Linux except once when I had a physical disk failure. > > (In fairness, I should note that Linux PCMCIA support appears to be > > superior to everybody else's. It's certainly superior to Windows as > > well as FreeBSD.) > > Can't disagree strongly enough. Well, as I said before, that's my experience. Probably depends on the network cards one uses and such. > > Anyway, any suggestions for determining the source of such crashes. For > > the fully-configured system, since the lockups happen only every couple > > of weeks, it's not really feasible to leave kernel tracing permanently > > on or anything like that. And these "crashes" of which I speak are > > system lockups, not kernel panics--there's no recovery possible becuase > > it locks up tight as a drum and I have to power off. Nor is this just > > an X display problem, for it also happens to my gateway/firewall, which > > doesn't even have X installed. > > > > How would you deal with such problems? > > Double and triple check for any irq/memory problems and then start > using DDB and DIAGNOSTIC. It's the only sane way to debug hard hangs. I did *lots* of checking for irq/memory problems on the gateway, believe you me. As for the "man" laptop computer, so far all crashes have involved configuration, though frequently at the bridge/ethernet layer rather than the hardware layer. Frequently they've involved poppping out or in a PCMCIA card while there's a daemon running that expects to talk to it. This is unfriendly to the O/S, but Linux seemed to handle such situations with more alactrity. > using DDB and DIAGNOSTIC. It's the only sane way to debug hard hangs. No manual entry for diagnostic. Also, I did a "make search" on ports. No "diagnostic" there, either. As for ddb, what you do, leave it up for two weeks waiting for the elusive crash? Wouldn't that have a severe impact on performance at least? Besides, when it hangs, it *hangs*. It won't even respond to keyboard input, not even CTL-ALT-DEL or ALT-F2. How would I use an interactive debugger in this context? Use the remote debugging? To do that, do I need a null modem cable? Not to mention that I don't *have* a desktop Linux/FreeBSD machine (though perhaps there's a gdb for Windows . . .) that could keep the gdb session up for that long. I'm not trying to difficult; I'm really ignorant, never having had much cause to do kernel debugging before. (I was once upon a time working on a Linux device driver for . . . heck, I forget what . . . but it was a while ago and I did it the old-fashioned way, with kernel logging calls.) > > P. > > -- > pir pir@pir.net pir@net.tufts.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 21:41:55 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail5.nc.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E51337B718; Tue, 13 Mar 2001 21:41:45 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail5.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 14 Mar 2001 00:41:44 -0500 Message-ID: <3AAF047F.341981B2@babbleon.org> Date: Wed, 14 Mar 2001 00:41:20 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: mobile@freebsd.org Cc: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Radcliffe wrote: > > The Babbler probably said: > > Perhaps all PCMCIA support under FreeBSD should be considered > > quasi-experimental or something, but I'm deliberately avoiding using > > anything but stock 4.2-RELEASSE in order to (hopefully) get maximum > > stability. > > PCMCIA under freebsd seems far more stable than Linux PCMCIA support > when _correctly_ _configured_. I've helped dozens of people get > wavelan support working at conferences and getting it as stable with > Linux requires the exact correct versions (and the only way to find > them is to test) of half a dozen things ... I haven't used WaveLANS, but every PCMCIA I ever stuck in my Linux box just worked. I've had to buy cards to get them to work with FreeBSD. My Linksys EtherFast Modem/Ethernet card is sitting a drawer in my desk because I finally gave up on it and bought a new (and more physically awkward) card for FreeBSD. You can search for old postings of my back in January or so for the saga on *that*. Similarly, I could *never* get two identical cards to work on my gateway machine; I finally bought a card to make FreeBSD happy. With Linux it just worked. Easy. To say the least, then, my experience does not concord with yours in this regard. > > For example, it froze both last night and tonight while I was trying to > > get vmware networking set up properly. > > vmware messes with things at a pretty low level and isn't designed for > FreeBSD. It's going to cause problems. Having said that, once I got it > set up properly (you did read the FreeBSD readme, didn't you ?) it > hasn't crashed the host OS on my machine in a long time. I read the FreeBSD readme. And I've had a nubmer of posting in the emultors group as I got things working there, too. The bridging would never work for me, but my final conclusion is that my card doesn't work with bridging, I guess. Only some cards do. (It says *that* in the handbook and the bridge man page.) > > But it's not just that; my gateway/firewall just locks up with the > > PCMCIA light stuck on about every couple of weeks. > > I would assume you have a misconfiguration or a hardware problem. > I've had freebsd boxes doing routing/filtering/pcmcia up for > _months_ with no problems. PCMCIA-based laptops or desktops? > > And making it all especially bad is that I've FreeBSD lose file contents > > (revert to zero length) after rebooting, even on files that hadn't > > actually been updated any time close to when the lockup occured. > > Never seen that in my last few years of freebsd use. Happened to me twice within days of my install. Both times it was "cal.vcs," for what it's worth. That's the calendar database for korganize, which *is* loaded, but would have had no reason to be writing to disk when I crashed. I never lost any files under Linux except once when I had a physical disk failure. > > (In fairness, I should note that Linux PCMCIA support appears to be > > superior to everybody else's. It's certainly superior to Windows as > > well as FreeBSD.) > > Can't disagree strongly enough. Well, as I said before, that's my experience. Probably depends on the network cards one uses and such. > > Anyway, any suggestions for determining the source of such crashes. For > > the fully-configured system, since the lockups happen only every couple > > of weeks, it's not really feasible to leave kernel tracing permanently > > on or anything like that. And these "crashes" of which I speak are > > system lockups, not kernel panics--there's no recovery possible becuase > > it locks up tight as a drum and I have to power off. Nor is this just > > an X display problem, for it also happens to my gateway/firewall, which > > doesn't even have X installed. > > > > How would you deal with such problems? > > Double and triple check for any irq/memory problems and then start > using DDB and DIAGNOSTIC. It's the only sane way to debug hard hangs. I did *lots* of checking for irq/memory problems on the gateway, believe you me. As for the "man" laptop computer, so far all crashes have involved configuration, though frequently at the bridge/ethernet layer rather than the hardware layer. Frequently they've involved poppping out or in a PCMCIA card while there's a daemon running that expects to talk to it. This is unfriendly to the O/S, but Linux seemed to handle such situations with more alactrity. > using DDB and DIAGNOSTIC. It's the only sane way to debug hard hangs. No manual entry for diagnostic. Also, I did a "make search" on ports. No "diagnostic" there, either. As for ddb, what you do, leave it up for two weeks waiting for the elusive crash? Wouldn't that have a severe impact on performance at least? Besides, when it hangs, it *hangs*. It won't even respond to keyboard input, not even CTL-ALT-DEL or ALT-F2. How would I use an interactive debugger in this context? Use the remote debugging? To do that, do I need a null modem cable? Not to mention that I don't *have* a desktop Linux/FreeBSD machine (though perhaps there's a gdb for Windows . . .) that could keep the gdb session up for that long. I'm not trying to difficult; I'm really ignorant, never having had much cause to do kernel debugging before. (I was once upon a time working on a Linux device driver for . . . heck, I forget what . . . but it was a while ago and I did it the old-fashioned way, with kernel logging calls.) > > P. > > -- > pir pir@pir.net pir@net.tufts.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 21:52:10 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail5.nc.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id 5509137B71A for ; Tue, 13 Mar 2001 21:52:02 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail5.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 14 Mar 2001 00:52:00 -0500 Message-ID: <3AAF06E8.103042C6@babbleon.org> Date: Wed, 14 Mar 2001 00:51:36 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Gerhard Sittig Cc: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <20010312174852.T20830@speedy.gsinet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gerhard Sittig wrote: > > On Sun, Mar 11, 2001 at 23:20 -0500, The Babbler wrote: > > > > Anybody else got a promiscuous 3c589d? > > I had quite a few tcpdump(1) sessions with a 3c589D and FreeBSD > 3.3 and 4.[012], so I assume promiscous mode works fine. > > The only problem I had with this card is that it defaults to the > wrong media type and doesn't recognize TP wiring, instead it > always falls back to BNC. So I have to force 10baseT selection. I haven't noticed a problem with that . . . > > When I try to enable bridging, it shuts down my ep0 networking > > entirely, so I lose all my networking; if I unplug & plug the > > card it gets address 0.0.0.0, presumably because DHCP fails; > > and if I try to turn off bridging after the fact, the machine > > hangs hard & I have to power off. > > Do you 'ifconfig down' the card *prior* to removal? For my own > sake I would get used to some sort of this behaviour ... :> Just > make sure nothing's using the card when you unplug it instead of > dazzling all the drivers / apps with events there's no card for. Heck, no. I just pop the card out. Windows gets upset if you do this, but Linux is quite happy if I insert it and remove it willy-nilly and never type in any commands at all. It is all just handled automatically. This might be the secret that I'm missing. It never once crossed my mind to type in a command before removing the PCMCIA network card . . . I never ifconfig down it *after* I remove it, either. I just wait 'til I'm back at the base station and plug it in again. So this could very well be the major issue. > > PS: In my experience, though FreeBSD has lots of advantages, it > > is *much* less stable than Linux. It's crashed -way- more than > > Linux ever did; more even than Windows does at work (of course > > I push Windows a lot less). And I've had it lose files a > > couple of times when it came back up after a hard crash like > > that. > > > > Is this at all normal? > > Is it at all normal for folks with laptops? > > No. And no. You state the reason for your "stable Windows" > yourself. And in comparison to Linux it must be some > configuration issue. Setup correctly (and given decent hardware) > both FreeBSD and Linux run fine. While FreeBSD is said to cope > better (smooth) with heavy load. FreeBSD's memory handling is noticaably superior, even when it's running a program under Linux emulation. And both startup/shutdown and printing I found much easier to configure the way I wanted. Plus I like the way the kernel config works--I can use my editor to just search. Lots of pluses. Hopefully the ifconfig thing is the clue I need to make the stability comparable. Thanks. > > virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 > Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Mar 13 23:41:34 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from vortex.greycat.com (vortex.greycat.com [207.173.133.4]) by hub.freebsd.org (Postfix) with SMTP id 6AB9137B718 for ; Tue, 13 Mar 2001 23:41:31 -0800 (PST) (envelope-from dann@bigphred.greycat.com) Received: (qmail 7763 invoked from network); 14 Mar 2001 07:41:29 -0000 Received: from bigphred.greycat.com (207.173.133.2) by vortex.greycat.com with SMTP; 14 Mar 2001 07:41:29 -0000 Received: (from dann@localhost) by bigphred.greycat.com (8.11.1/8.11.1) id f2E7fSi70867 for mobile@freebsd.org; Tue, 13 Mar 2001 23:41:28 -0800 (PST) (envelope-from dann) Date: Tue, 13 Mar 2001 23:41:28 -0800 From: Dann Lunsford To: mobile@freebsd.org Subject: Tosh 2595XDVD -- fan control? Message-ID: <20010313234128.A70849@greycat.com> Reply-To: Dann Lunsford Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Have a ${SUBJECT}, running 4.2-STABLE as of Jan 5. Looking for data on turning on the cooling fan (as it gets a bit warm in there). Natch, Toshiba's reaction on hearing "FreeBSD" or "UNIX" is "Huh?", Anyone got a clue? Ideally, I'd just like to type "fan on" or "fan off", but I'll take whatever I can get. I've seen some references to Linux based utils of this type, but my experience has been that porting Linux hardware utils is pure torture. Thanks! -- Dann Lunsford The only thing necessary for the triumph of evil dann@greycat.com is that men of good will do nothing. -- Cicero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 0: 8:52 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id A7F5737B71B for ; Wed, 14 Mar 2001 00:08:47 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 4575 invoked from network); 14 Mar 2001 08:02:41 -0000 Received: from acs-24-154-53-165.zoominternet.net (24.154.53.165) by scully.zoominternet.net with SMTP; 14 Mar 2001 08:02:41 -0000 Date: Wed, 14 Mar 2001 03:08:47 -0500 (EST) From: Donn Miller X-X-Sender: To: David Kelly Cc: Pete French , , , Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <200103140404.f2E44Ne16415@grumpy.dyndns.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 13 Mar 2001, David Kelly wrote: > Well, I am an ex-Linux user who got fed up with Linux trashing my disk 3 > times one week. Each time (kernel panics) the damage was bad enough fsck > (e2fsck?) deleted a lot of critical files making a wipe/reinstall the > fastest way back to a running system. This was shortly after the release > of FreeBSD 2.0.0. Remember it well because that is when I became a > FreeBSD user. Hmm, probably 6 years ago this month. > > Have watched Linux from "outside" since then. Noticed I was not the > only one losing data. From what I've seen the Linux solution was not to > to fix a faulty design but to hack it until it doesn't lose as much. I agree -- EXT2 is kinda crappy. But to be fair, Linux has Reiserfs, and I've heard of EXT3 on the way. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 0:15:12 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.dev.itouchnet.net (mx1.dev.itouchnet.net [196.14.181.66]) by hub.freebsd.org (Postfix) with ESMTP id 599F737B718 for ; Wed, 14 Mar 2001 00:15:06 -0800 (PST) (envelope-from bvi@devco.net) Received: from nobody by mx1.dev.itouchnet.net with scanned_ok (Exim 3.16 #1) id 14d6VB-000BQx-00 for freebsd-mobile@freebsd.org; Wed, 14 Mar 2001 10:19:25 +0200 Received: from [196.14.181.39] (helo=e0-ter-fw1.dev.itouchnet.net) by mx1.dev.itouchnet.net with esmtp (Exim 3.16 #1) id 14d6VA-000BQi-00 for freebsd-mobile@freebsd.org; Wed, 14 Mar 2001 10:19:24 +0200 Received: from daemon.prv.dev.itouchnet.net ([192.168.8.10]) by e0-ter-fw1.dev.itouchnet.net with esmtp (Exim 3.15 #1) id 14d6Qw-000HYu-00 for freebsd-mobile@freebsd.org; Wed, 14 Mar 2001 10:15:02 +0200 Received: from bvi by daemon.prv.dev.itouchnet.net with local (Exim 3.16 #1) id 14d6UO-00072Y-00; Wed, 14 Mar 2001 10:18:36 +0200 Date: Wed, 14 Mar 2001 10:18:36 +0200 From: Barry Irwin To: Dann Lunsford Cc: freebsd-mobile@freebsd.org Subject: Re: Tosh 2595XDVD -- fan control? Message-ID: <20010314101836.H22889@devco.net> References: <20010313234128.A70849@greycat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010313234128.A70849@greycat.com>; from dann@greycat.com on Tue, Mar 13, 2001 at 11:41:28PM -0800 X-Checked: This message has been scanned for any virusses and unauthorized attachments. X-iScan: Version $Id: iScan,v 1.26 2000/10/08 14:12:55 rip Exp $ Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue 2001-03-13 (23:41), Dann Lunsford wrote: > Have a ${SUBJECT}, running 4.2-STABLE as of Jan 5. Looking for data > on turning on the cooling fan (as it gets a bit warm in there). Natch, > Toshiba's reaction on hearing "FreeBSD" or "UNIX" is "Huh?", Anyone got > a clue? Ideally, I'd just like to type "fan on" or "fan off", but I'll > take whatever I can get. I've seen some references to Linux based > utils of this type, but my experience has been that porting Linux > hardware utils is pure torture. Interesting, I havent seen any mention of this , or experienced a fan running under windows. I have toshiba DVD in my HP omnibook xe3 acd0: DVD-ROM at ata1-master using UDMA33 Although I've noticed disks seem to come out cooler when I'm running BSD than windows. Barry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 2:56:30 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from deborah.paradise.net.nz (deborah.paradise.net.nz [203.96.152.32]) by hub.freebsd.org (Postfix) with ESMTP id 9850F37B718; Wed, 14 Mar 2001 02:56:24 -0800 (PST) (envelope-from marki@paradise.net.nz) Received: from paradise.net.nz (203-79-69-96.apx0.paradise.net.nz [203.79.69.96]) by deborah.paradise.net.nz (8.11.3/8.11.3) with ESMTP id f2EArTU06551; Wed, 14 Mar 2001 23:53:29 +1300 (NZDT) Message-ID: <3AAF4DA0.C8DA9485@paradise.net.nz> Date: Wed, 14 Mar 2001 23:53:20 +1300 From: Mark Ibell X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Mars Attack , Soren Schmidt , Peter Wemm , Mike Meyer , Helge Oldach , oberman@es.net, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA References: <200103131007.f2DA73h54023@mobile.wemm.org> <01f001c0abaa$133e1680$4500a8c0@nomad> <20010313032635.Q29888@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What doesn't appear to have been mentioned is how exactly do we turn off write caching on SCSI drives. From poking around the best I could work out was to run 'camcontrol modepage da0 -m 0x08 -e -P 3' and set WCE to 0 where 0x08 comes from /usr/share/misc/scsi_modes. Is this the correct way to do it? Also, is it okay to leave tagged queuing enabled? (I'm really starting to get paranoid after all this discussion!) Cheers, Mark Alfred Perlstein wrote: > > * Mars Attack [010313 02:18] wrote: > > Geez, this thread is getting longer and all the more confusing, can some > > guru possibly attempt to outline the good and bad points of Softupdates or > > WC ? > > 1) softupdates good > 2) WC bad (even when not using softupdates) > > Basically, softupdates doesn't really matter, as long as you have > write caching turned on, you're defeating the safeness of FFS > (noasync) and FFS (softdep) by allowing the disk to reorder what > should be ordered writes. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 3:14: 9 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from vortex.greycat.com (vortex.greycat.com [207.173.133.4]) by hub.freebsd.org (Postfix) with SMTP id 94AD137B718 for ; Wed, 14 Mar 2001 03:14:03 -0800 (PST) (envelope-from dann@bigphred.greycat.com) Received: (qmail 8681 invoked from network); 14 Mar 2001 11:14:01 -0000 Received: from bigphred.greycat.com (207.173.133.2) by vortex.greycat.com with SMTP; 14 Mar 2001 11:14:01 -0000 Received: (from dann@localhost) by bigphred.greycat.com (8.11.1/8.11.1) id f2EBE0H43915; Wed, 14 Mar 2001 03:14:00 -0800 (PST) (envelope-from dann) Date: Wed, 14 Mar 2001 03:14:00 -0800 From: Dann Lunsford To: Barry Irwin Cc: mobile@freebsd.org Subject: Re: Tosh 2595XDVD -- fan control? Message-ID: <20010314031400.A43363@greycat.com> Reply-To: Dann Lunsford References: <20010313234128.A70849@greycat.com> <20010314101836.H22889@devco.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010314101836.H22889@devco.net>; from bvi@devco.net on Wed, Mar 14, 2001 at 10:18:36AM +0200 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 14, 2001 at 10:18:36AM +0200, Barry Irwin wrote: > On Tue 2001-03-13 (23:41), Dann Lunsford wrote: > > Have a ${SUBJECT}, running 4.2-STABLE as of Jan 5. Looking for data > > on turning on the cooling fan (as it gets a bit warm in there). Natch, > > Toshiba's reaction on hearing "FreeBSD" or "UNIX" is "Huh?", Anyone got > > a clue? Ideally, I'd just like to type "fan on" or "fan off", but I'll > > take whatever I can get. I've seen some references to Linux based > > utils of this type, but my experience has been that porting Linux > > hardware utils is pure torture. > > Interesting, I havent seen any mention of this , or experienced a fan > running under windows. I have toshiba DVD in my HP omnibook xe3 > > acd0: DVD-ROM at ata1-master using UDMA33 > Heh. You're not looking at it from the right corner of the Toshiba Universe. The 2595XDVD is a laptop, not a DVDROM drive, although it has one in it. The fan I want to turn on is the case exhaust fan, a little muffin about an inch square. Apparently, under MICROS~1, this thing comes on automagically, when temps get too high. Possibly an APM controlable doo-hickey, but I can't find anything about it. Major PITA. Thanks for the reply! Much appreciated -- Dann Lunsford The only thing necessary for the triumph of evil dann@greycat.com is that men of good will do nothing. -- Cicero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 3:22:29 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-59.dsl.lsan03.pacbell.net [63.207.60.59]) by hub.freebsd.org (Postfix) with ESMTP id F129037B71C; Wed, 14 Mar 2001 03:22:23 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C9A7D66B6C; Wed, 14 Mar 2001 03:22:19 -0800 (PST) Date: Wed, 14 Mar 2001 03:22:19 -0800 From: Kris Kennaway To: Guangrui Fu Cc: mobile-ip , freebsd-net , freebsd-mobile Subject: Re: Mobile IP implementation for FreeBSD Message-ID: <20010314032219.A30923@mollari.cthul.hu> References: <20010313224837.21080.qmail@web3102.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010313224837.21080.qmail@web3102.mail.yahoo.com>; from guangruifu@yahoo.com on Tue, Mar 13, 2001 at 02:48:37PM -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 13, 2001 at 02:48:37PM -0800, Guangrui Fu wrote: > Hi, >=20 > I'm looking for open-sourced Mobile IP implementation > on FreeBSD. Could anyone please give me some > information? KAME (www.kame.net) has an experimental implementation which will be integrated into FreeBSD at some point in the future once it's considered ready enough. Kris --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6r1RrWry0BWjoQKURAq+5AKDQhahBiMpxloTDQgsLF5jphJh34ACdEJIf 0nbm260/T/ZLfyu+IYWN4/4= =D/Zh -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 4:50:49 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 7314537B719; Wed, 14 Mar 2001 04:50:45 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.06) with ESMTP id VAA23800; Wed, 14 Mar 2001 21:50:32 +0900 (JST) To: Kris Kennaway Cc: Guangrui Fu , mobile-ip , freebsd-net , freebsd-mobile In-reply-to: kris's message of Wed, 14 Mar 2001 03:22:19 PST. <20010314032219.A30923@mollari.cthul.hu> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Mobile IP implementation for FreeBSD From: itojun@iijlab.net Date: Wed, 14 Mar 2001 21:50:32 +0900 Message-ID: <23798.984574232@coconut.itojun.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> I'm looking for open-sourced Mobile IP implementation >> on FreeBSD. Could anyone please give me some >> information? > >KAME (www.kame.net) has an experimental implementation which will be >integrated into FreeBSD at some point in the future once it's >considered ready enough. KAME does mobile-ip6 only. we don't do mobile-ip4. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 4:51:43 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by hub.freebsd.org (Postfix) with ESMTP id 8555337B71B for ; Wed, 14 Mar 2001 04:51:34 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 14dAkX-0002Uh-00 for mobile@freebsd.org; Wed, 14 Mar 2001 07:51:33 -0500 Date: Wed, 14 Mar 2001 07:51:32 -0500 From: Peter Radcliffe To: mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Message-ID: <20010314075132.A8440@pir.net> Reply-To: mobile@freebsd.org Mail-Followup-To: mobile@freebsd.org References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> <3AAF047F.341981B2@babbleon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AAF047F.341981B2@babbleon.org>; from bts@babbleon.org on Wed, Mar 14, 2001 at 12:41:20AM -0500 X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The Babbler probably said: > Peter Radcliffe wrote: > > PCMCIA under freebsd seems far more stable than Linux PCMCIA support > > when _correctly_ _configured_. I've helped dozens of people get > > wavelan support working at conferences and getting it as stable with > > Linux requires the exact correct versions (and the only way to find > > them is to test) of half a dozen things ... > I haven't used WaveLANS, but every PCMCIA I ever stuck in my Linux box > just worked. It sometimes took a couple of _days_ of hackery to get wavelan cards working with some linux boxes, the only fast way at the first conference was to find the person who already had it working and ask them what they did. Certainly not "just working". > in January or so for the saga on *that*. Similarly, I could *never* get > two identical cards to work on my gateway machine; I finally bought a > card to make FreeBSD happy. With Linux it just worked. Easy. I've had identical cards working perfectly in the same machine. > To say the least, then, my experience does not concord with yours in > this regard. Mine nor dozens of other people. > I read the FreeBSD readme. And I've had a nubmer of posting in the > emultors group as I got things working there, too. The bridging would > never work for me, but my final conclusion is that my card doesn't work > with bridging, I guess. Only some cards do. (It says *that* in the /usr/ports/emulators/vmware2/files/README.FreeBSD - Support only for Host networking. Doesn't have a bridgink networking But really this mean, that you are need to enable gateway on our FreeBSD box. And after that virtual machine can communicate with a rest of the world. > > I would assume you have a misconfiguration or a hardware problem. > > I've had freebsd boxes doing routing/filtering/pcmcia up for > > _months_ with no problems. > PCMCIA-based laptops or desktops? Both. Two examples are an old 486 laptop as a wavelan <-> ether gateway and a desktop box that wasn't rebooted with an ISA pcmcia controller which I used CF cards in. My current laptop only gets rebooted for upgrades, basicly, has been suspended/resumed thousands of times and it's primary net access is pcmcia wavelan. I'm typing on it right now. > Happened to me twice within days of my install. Both times it was > "cal.vcs," for what it's worth. That's the calendar database for > korganize, which *is* loaded, but would have had no reason to be writing > to disk when I crashed. Sounds like bad hardware to me, then. Have you been reading the write cache thread ? I currently run soemthing like 10 heavily used desktops/laptops for my group at work. I hammer my machines. I've _never_ seen this happen. > I never lost any files under Linux except once when I had a physical > disk failure. I've never lost any files under FreeBSD except for physical disk failure. Your point ? > No manual entry for diagnostic. Also, I did a "make search" on ports. > No "diagnostic" there, either. It's a kernel entry; # The DIAGNOSTIC option is used to enable extra debugging information options DIAGNOSTIC > As for ddb, what you do, leave it up for two weeks waiting for the > elusive crash? Wouldn't that have a severe impact on performance at > least? No. My laptop runs with DDB in the kernel dating from when there was a problem with removing/reinserting ATA cards a few times in 4.* and I was trying to assist in debugging the issue. Never saw any reason to turn it off after the issue was fixed properly and have noticed no performance issues. > Besides, when it hangs, it *hangs*. It won't even respond to keyboard > input, not even CTL-ALT-DEL or ALT-F2. How would I use an interactive > debugger in this context? Use the remote debugging? To do that, do I Thats the point of DDB. You drop to the debugger, which is below everything else. You don't seem to be able to drop to DDB while running X, which is unfortunate, but crash dumps can still help assuming one happens or can be provoked and you have collection turned on. http://www.freebsd.org/docs/en/books/handbook/kerneldebug.html P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 5:14:25 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by hub.freebsd.org (Postfix) with ESMTP id 23CE637B718 for ; Wed, 14 Mar 2001 05:14:22 -0800 (PST) (envelope-from martijn.pronk@xs4all.nl) Received: from boekje (lap-34.nikhef.nl [192.16.192.34]) by smtp8.xs4all.nl (8.9.3/8.9.3) with SMTP id OAA17514; Wed, 14 Mar 2001 14:14:17 +0100 (CET) Message-ID: <007901c0ac88$a0bc2b30$22c010c0@boekje> From: "Martijn Pronk" To: , References: <200103131150.f2DBoH901143@BigBrother.leidinger.net> Subject: Re: Fujitsu-Siemens Lifebook E-Serie? Date: Wed, 14 Mar 2001 14:13:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > I've read the README.TXT (FreeBSD 4.2) and Cards (X11). > It seems to me, I can buy the E-Serie (E-6180/6540/6550/6560) with > internal modem (for WIN only) and buy an extra PCMCIA-Card 3COM > 3CCFE574BT. > > Has someone a good experience with Fujitsu-Siemens Liefbook E-Serie? > Are there any problems with that hardware on FreeBSD? Well, I use a Fujitsu Lifebook C-6310, FreeBSD works as a charm and X aswell, but I don't know about the E series... I can say that my Lifebook a bit on the weak side is (Mechanical, that is...) since the bottom part can be bend a bit (with all the scary noises) Yust my $ .02 ... -- Martijn There is nothing magic about SCSI cabling. There are sound technical reasons why they occasionally require the sacrifice of a young goat. - Somebody in FreeBSD-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 6: 5:47 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 2BC8437B719; Wed, 14 Mar 2001 06:05:43 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f2EE5Ks71827; Wed, 14 Mar 2001 07:05:21 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200103141405.f2EE5Ks71827@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Alfred Perlstein Cc: Helge Oldach , oberman@es.net, sos@freebsd.dk, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: Your message of "Tue, 13 Mar 2001 00:58:11 PST." <20010313005811.J29888@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Mar 2001 07:05:20 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >First off, some disk caches are getting > 10megs, that's a lot >of potnetial seeking after loosing power depending on the cache >contents... I've heard that most modern drives reserve a contiguous area of the disk the size of the cache near where the heads park to dump any cache contents on power outage. This avoids most if not all seeking. When the disk powers up again, the reserve track is read and the transactions are written to the correct locations. Any disk that does this should be safe to use with write caching enabled. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 6:10:34 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D839637B71A; Wed, 14 Mar 2001 06:10:25 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA29652; Wed, 14 Mar 2001 15:10:10 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103141410.PAA29652@freebsd.dk> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <200103141405.f2EE5Ks71827@aslan.scsiguy.com> from "Justin T. Gibbs" at "Mar 14, 2001 07:05:20 am" To: gibbs@scsiguy.com (Justin T. Gibbs) Date: Wed, 14 Mar 2001 15:10:10 +0100 (CET) Cc: bright@wintelcom.net (Alfred Perlstein), Helge.Oldach@de.origin-it.com (Helge Oldach), oberman@es.net, mobile@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Justin T. Gibbs wrote: > >First off, some disk caches are getting > 10megs, that's a lot > >of potnetial seeking after loosing power depending on the cache > >contents... > > I've heard that most modern drives reserve a contiguous area of the > disk the size of the cache near where the heads park to dump any > cache contents on power outage. This avoids most if not all seeking. > When the disk powers up again, the reserve track is read and the > transactions are written to the correct locations. Any disk that does > this should be safe to use with write caching enabled. I belived that as well, but after consulting with some of the disk vendors, I found out this was just wishfull thinking, almost noone does this anymore infact only one remembered a single drive that did this... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 6:30: 1 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id B1DF937B719 for ; Wed, 14 Mar 2001 06:29:56 -0800 (PST) (envelope-from mwm@mired.org) Received: (qmail 13706 invoked by uid 100); 14 Mar 2001 14:29:56 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15023.32868.9995.327616@guru.mired.org> Date: Wed, 14 Mar 2001 08:29:56 -0600 To: Mark Ibell Cc: Alfred Perlstein , Mars Attack , Soren Schmidt , Peter Wemm , Helge Oldach , oberman@es.net, mobile@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <3AAF4DA0.C8DA9485@paradise.net.nz> References: <200103131007.f2DA73h54023@mobile.wemm.org> <01f001c0abaa$133e1680$4500a8c0@nomad> <20010313032635.Q29888@fw.wintelcom.net> <3AAF4DA0.C8DA9485@paradise.net.nz> X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mark Ibell types: > What doesn't appear to have been mentioned is how exactly do we turn off > write caching on SCSI drives. From poking around the best I could work > out was to run 'camcontrol modepage da0 -m 0x08 -e -P 3' and set WCE to > 0 where 0x08 comes from /usr/share/misc/scsi_modes. > > Is this the correct way to do it? Assuming you've got the right numbers for WCE, yes. Camcontrol is the right tool. > Also, is it okay to leave tagged queuing enabled? (I'm really starting > to get paranoid after all this discussion!) I'd say yes, as at least some of the drivers expect it to be there. I think the critical thing is that the driver know when the data is actually on the disk, so if tagged queueing doesn't interfere with that, it's ok. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 6:46:32 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by hub.freebsd.org (Postfix) with ESMTP id 780F437B719 for ; Wed, 14 Mar 2001 06:46:18 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 14 Mar 2001 08:51:03 -0500 Message-ID: <3AAF77CD.5B204389@babbleon.org> Date: Wed, 14 Mar 2001 08:53:17 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> <3AAF047F.341981B2@babbleon.org> <20010314075132.A8440@pir.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [I was going to take this off-line since I'm not sure that everybody really wants to read this, but I noticed that you have your reply-to set to the list for some reason, so I'm going to respect that request and keep it public. If you want to reply personally to me that's fine, and we can post a summary at the end of the discussion.] Peter Radcliffe wrote: > > The Babbler probably said: > > Peter Radcliffe wrote: > > > PCMCIA under freebsd seems far more stable than Linux PCMCIA support > > > when _correctly_ _configured_. I've helped dozens of people get > > > wavelan support working at conferences and getting it as stable with > > > Linux requires the exact correct versions (and the only way to find > > > them is to test) of half a dozen things ... > > I haven't used WaveLANS, but every PCMCIA I ever stuck in my Linux box > > just worked. > > It sometimes took a couple of _days_ of hackery to get wavelan cards > working with some linux boxes, the only fast way at the first > conference was to find the person who already had it working and ask > them what they did. Certainly not "just working". Ok, I believe you. FreeBSD handles WaveLAN cards. It handles them much better Linux. I'd just like you to admit that FreeBSD has inferior PCMCIA support in other ways. > > in January or so for the saga on *that*. Similarly, I could *never* get > > two identical cards to work on my gateway machine; I finally bought a > > card to make FreeBSD happy. With Linux it just worked. Easy. > > I've had identical cards working perfectly in the same machine. I wish you'd been around on the list in January and able to help me then. > > To say the least, then, my experience does not concord with yours in > > this regard. > > Mine nor dozens of other people. Well, there are dozens of people with my same experience, I'm sure; I get personal mail from a number of them (one of them just yesterday) hoping to hear what success I had in solving some of my problems. I've been able to help some people get their cards working, in fact, by helping them with their pccard.conf files. All of the cards I'm talking about, under Linux, don't require changing any configuratin files anyplace. And that's not to even mention the fact that my computer locks up hard if I do a soft boot with my 3com card in the bay--FreeBSD fails to shut something down properly on the card, the result of which is that it locks up the machine on reboot. I can softboot Windows and Linux without any trouble. I'd actually forgotten about this problem when I was writing before, because I've worked around it--by aliasing both "halt" and "reboot" to "shutdown -p now." But again, that's pretty lame. Linux and Windows both manage to do better. > > > I read the FreeBSD readme. And I've had a nubmer of posting in the > > emultors group as I got things working there, too. The bridging would > > never work for me, but my final conclusion is that my card doesn't work > > with bridging, I guess. Only some cards do. (It says *that* in the > > /usr/ports/emulators/vmware2/files/README.FreeBSD > > - Support only for Host networking. Doesn't have a bridgink networking > But really this mean, that you are need to enable gateway on > our FreeBSD box. And after that virtual machine can communicate > with a rest of the world. Damnit, you are really starting to get annoying. You are as bad as the blind "everything Windows does must be best" advocates. I said I READ THE README. I meant that I READ THE README. You can check the freebsd-emulators list archive. I've *DONE* that. I *KNOW* that. I used host-only networking under Linux anyway, because that way I could use my host machine to do the address translation, and then the guest O/Ss didn't have to know when I moved from one network to another, only the host did. But if I enabled bridging in my kernel (which is where this thread started--did you ever read my *original* post?), then the card totally fails to initilize and FreeBSD itself (the host) loses all networking since the network card stops functioning. (Did I mention that I never had any trouble with a kernel option disabling a hardware driver under Linux?) If I used the very latest vwmware2 port I couldn't communicate even from vmnet1 to the guest. I still haven't been able to get a gateway configuation going to make vmware work. Would be you willing to "put your money where you mouth is" and help me through it? I'll readily admit that I'm no expert in the area of gateways, although was able to get this working under Linux with relative ease. > > > I would assume you have a misconfiguration or a hardware problem. > > > I've had freebsd boxes doing routing/filtering/pcmcia up for > > > _months_ with no problems. > > PCMCIA-based laptops or desktops? > > Both. Two examples are an old 486 laptop as a wavelan <-> ether > gateway and a desktop box that wasn't rebooted with an ISA pcmcia > controller which I used CF cards in. My current laptop only gets > rebooted for upgrades, basicly, has been suspended/resumed thousands > of times and it's primary net access is pcmcia wavelan. I'm typing on > it right now. Perhaps I'd be better off with wavelans. Clearly they are the card of choice for you. Is it not at least conceivable that FreeBSD has superior support for wavelans and inferior suport for Linksys and 3com cards? > > Happened to me twice within days of my install. Both times it was > > "cal.vcs," for what it's worth. That's the calendar database for > > korganize, which *is* loaded, but would have had no reason to be writing > > to disk when I crashed. > > Sounds like bad hardware to me, then. Have you been reading the write > cache thread ? Yes, I've been finding that one quite interesting. That said, I was running Linux for over a year on this exact same machine. It never crashed anywhere near as much as FreeBSD, but it did crash a few times (or at least get X lockups), though, and I never lost any data. > I currently run soemthing like 10 heavily used desktops/laptops for > my group at work. I hammer my machines. I've _never_ seen this happen. > > > I never lost any files under Linux except once when I had a physical > > disk failure. > > I've never lost any files under FreeBSD except for physical disk > failure. Your point ? My point is that any claims about the *superior* ability of FreeBSD to avoid losses in the filesystem are at odds with my experience. This could, of course, just be fantastically bad luck on my part. It only happened twice, and that's not a statistically significant sample size. (Unlike my PCMCIA troubles, which have covered two machines and numerous different problems.) > > No manual entry for diagnostic. Also, I did a "make search" on ports. > > No "diagnostic" there, either. > > It's a kernel entry; > > # The DIAGNOSTIC option is used to enable extra debugging information > options DIAGNOSTIC > > > As for ddb, what you do, leave it up for two weeks waiting for the > > elusive crash? Wouldn't that have a severe impact on performance at > > least? > > No. My laptop runs with DDB in the kernel dating from when there was a > problem with removing/reinserting ATA cards a few times in 4.* and I > was trying to assist in debugging the issue. Never saw any reason to > turn it off after the issue was fixed properly and have noticed no > performance issues. > > > Besides, when it hangs, it *hangs*. It won't even respond to keyboard > > input, not even CTL-ALT-DEL or ALT-F2. How would I use an interactive > > debugger in this context? Use the remote debugging? To do that, do I > > Thats the point of DDB. You drop to the debugger, which is below > everything else. > > You don't seem to be able to drop to DDB while running X, which is > unfortunate, but crash dumps can still help assuming one happens > or can be provoked and you have collection turned on. > > http://www.freebsd.org/docs/en/books/handbook/kerneldebug.html Ok, thanks. I'll try enabling those and see what happens. For the gateway machine, I don't have X installed anyway, and so far on the main laptop machine the crashes have all involved "configuration" sorts of things. I don't think this excuses FreeBSD morally, as it were, but it makes it less of a long-term issue since I'm anticipating that once I get the configuration completed it won't be such a problem. (And, again, Linux doesn't crash while I configure it--granted that most of it worked automatically enough that no configuration was necessary--if it has an equivalent of /etc/pccard.conf I don't even know about it 'cause I never needed it.) > > P. > > -- > pir pir@pir.net pir@net.tufts.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 7: 0:49 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from clientmail.realtime.co.uk (simian.realtime.co.uk [194.205.134.131]) by hub.freebsd.org (Postfix) with ESMTP id 1A04437B71A for ; Wed, 14 Mar 2001 07:00:46 -0800 (PST) (envelope-from waynep@zaphod.realtime.co.uk) Received: from zaphod.realtime.co.uk ([194.205.134.208]) by clientmail.realtime.co.uk with esmtp (Exim 3.20 #1) id 14dClV-0004UV-01 for mobile@freebsd.org; Wed, 14 Mar 2001 15:00:41 +0000 Received: from waynep by zaphod.realtime.co.uk with local (Exim 3.20 #1) id 14dClP-0006qT-00 for mobile@freebsd.org; Wed, 14 Mar 2001 15:00:35 +0000 From: Wayne Pascoe To: mobile@freebsd.org Subject: Cardbus support Reply-To: wayne.pascoe@realtime.co.uk Date: 14 Mar 2001 15:00:35 +0000 Message-ID: Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a quick question... Which release is cardbus support slated to be in? I have all of my desktops and all of my servers moved from Linux to FreeBSD. I just have 2 laptops still to move. As I already own 3com cardbus cards, I don't really want to buy new hardware. Thanks, -- - Wayne Pascoe E-mail: wayne.pascoe@realtime.co.uk Phone : +44 (0) 20 7544 4668 Mobile: +44 (0) 788 431 1675 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 7:21:31 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id C52CF37B719 for ; Wed, 14 Mar 2001 07:21:26 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.1/8.11.1) id f2EGXAf28286 for mobile@freebsd.org; Wed, 14 Mar 2001 16:33:10 GMT (envelope-from nik) Date: Wed, 14 Mar 2001 16:33:10 +0000 From: Nik Clayton To: mobile@freebsd.org Subject: lcron Message-ID: <20010314163309.A28199@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: FreeBSD Project Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Has anyone experimented with lcron? It's a "location aware" cron, built on top of xcron, with support for triggering and/or running events based on what it thinks your 'location' is. More details at http://www.isi.edu/~johnh/SOFTWARE/XCRON/ N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqvnUUACgkQk6gHZCw343UgpQCeM5zOlkpufc7He5niBa96Aerr i2YAn1ZU8UcpD4uxUcGDrEE4WfunznTu =3VFL -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 7:22:24 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from isris.pair.com (isris.pair.com [209.68.2.39]) by hub.freebsd.org (Postfix) with SMTP id 5CF3F37B718 for ; Wed, 14 Mar 2001 07:22:21 -0800 (PST) (envelope-from rooneg@isris.pair.com) Received: (qmail 36239 invoked by uid 3130); 14 Mar 2001 15:22:20 -0000 Date: Wed, 14 Mar 2001 10:22:20 -0500 From: Garrett Rooney To: Wayne Pascoe Cc: mobile@freebsd.org Subject: Re: Cardbus support Message-ID: <20010314102220.A34993@electricjellyfish.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from wayne.pascoe@realtime.co.uk on Wed, Mar 14, 2001 at 03:00:35PM +0000 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 14, 2001 at 03:00:35PM +0000, Wayne Pascoe wrote: > Just a quick question... Which release is cardbus support slated to be > in? I have all of my desktops and all of my servers moved from Linux > to FreeBSD. I just have 2 laptops still to move. As I already own 3com > cardbus cards, I don't really want to buy new hardware. there is some cardbus support in -CURRENT, and supposably it works well. from what i've heard it probably won't be MFC'd any time soon though, and since -CURRENT is very much a developers only place these days, you're kind of stuck. -- garrett rooney Unix was not designed to stop you from rooneg@electricjellyfish.net doing stupid things, because that would http://electricjellyfish.net/ stop you from doing clever things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 7:30:11 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from the.oneinsane.net (the.oneinsane.net [66.42.61.25]) by hub.freebsd.org (Postfix) with ESMTP id 5179C37B71A for ; Wed, 14 Mar 2001 07:29:40 -0800 (PST) (envelope-from blovett@venus.bsdguru.com) Received: from darkstar.bsdguru.com (unknown [165.24.155.244]) by the.oneinsane.net (Postfix) with ESMTP id D1C169B9F for ; Wed, 14 Mar 2001 07:29:33 -0800 (PST) Received: from venus.bsdguru.com (venus.n2.net [207.113.133.11]) by darkstar.bsdguru.com (Postfix) with ESMTP id 00C881E3F; Wed, 14 Mar 2001 06:32:49 -0800 (PST) Received: by venus.bsdguru.com (Postfix, from userid 1000) id 400A260; Wed, 14 Mar 2001 06:32:47 -0800 (PST) Date: Wed, 14 Mar 2001 06:32:46 -0800 From: Ben Lovett To: Dann Lunsford Cc: mobile@FreeBSD.ORG Subject: Re: Tosh 2595XDVD -- fan control? Message-ID: <20010314063246.A12367@bsdguru.com> References: <20010313234128.A70849@greycat.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010313234128.A70849@greycat.com>; from dann@greycat.com on Tue, Mar 13, 2001 at 11:41:28PM -0800 X-Organization: San Diego BSD Users Group [http://www.sdbug.org] X-Disclaimer: All messages are the opinion of my employer.. They just don't know it yet. X-Operating-System: FreeBSD venus 4.2-STABLE X-Moon: The Moon is Waning Gibbous (73% of Full) X-GPG-Key: http://www.oneinsane.net/~blovett/blovett.pgp X-GPG-Fingerprint: C75F A722 1518 03B8 26C3 77A1 7C76 8AFA EBAB 2004 X-Uptime: 6:30AM up 4:46, 3 users, load averages: 0.12, 0.20, 0.19 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I believe I saw Dann Lunsford (dann@greycat.com) write this: > Have a ${SUBJECT}, running 4.2-STABLE as of Jan 5. Looking for data > on turning on the cooling fan (as it gets a bit warm in there). Natch, > Toshiba's reaction on hearing "FreeBSD" or "UNIX" is "Huh?", Anyone got > a clue? Ideally, I'd just like to type "fan on" or "fan off", but I'll > take whatever I can get. I've seen some references to Linux based > utils of this type, but my experience has been that porting Linux > hardware utils is pure torture. > > Thanks! > > > -- > Dann Lunsford The only thing necessary for the triumph of evil > dann@greycat.com is that men of good will do nothing. -- Cicero > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > Hello Dann, I had this very same problem on my Satellite 2505CDS and 2515CDS and someone was kind enough to port the Linux fan util to FreeBSD so it works great ;) I have attached the fan util and here are some instructions on how to use it. It *may* need to be modified slightly for a new laptop but I'm not sure (not being a coder myself). To start run: fan -n to stop: fan -f (both must be done as root) HTH -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Ben Lovett printf("Hello world!); blovett@bsdguru.com return 0; -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- The dark ages were caused by the Y1K problem. --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="fan.c" /* fan.c -- turn the internal fan on/off in a Toshiba Pentium(tm) laptop. * * Copyright (c) 1996/98 Jonathan A. Buzzard (jonathan@buzzard.org.uk) * * $Log: fan.c,v $ * Revision 3.1 1999/07/24 13:52:37 jab * updates for glibc * * Revision 3.0 1998/07/11 14:01:38 jab * New selective switching method based on the return from GetMachineID, * should work on all known models * * Revision 2.2 1998/05/30 22:50:03 jab * hopefully fixed problems with reporting of fan status * * Revision 2.1 1998/05/08 22:52:17 jab * now drop root priveleges as soon as permision on the ports granted * * Revision 2.0 1998/01/31 16:00:23 jab * Changed to new method of turning the fan on/off, which should * work on a wider range of Toshiba laptops * * Revision 1.5 1997/05/23 13:17:25 jab * change the command line option processing to only deal with the first * * Revision 1.4 1997/04/29 21:26:11 jab * changed the name of the port variables to reflect their real status * * Revision 1.3 1996/08/01 14:25:36 jab * Added logging of changes in fan status via syslogd(8) * * Revision 1.2 1996/07/30 18:11:16 jab * fixed reporting of unknown command line options * * Revision 1.1 1996/06/25 21:47:42 jab * Initial revision * * * This program is free software; you can redistribute it and/or modify it * under the terms of the GNU General Public License as published by the * Free Software Foundation; either version 2, or (at your option) any * later version. * * This program is distributed in the hope that it will be useful, but * WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * General Public License for more details. * * You should have received a copy of the GNU General Public License along * with this program; if not, write to the Free Software Foundation, Inc., * 675 Mass Ave, Cambridge, MA 02139, USA. * */ static const char rcsid[]="$Id: fan.c,v 3.1 1999/07/24 13:52:37 jab Exp jab $"; #include #include #include /* #include */ #ifdef __GLIBC__ #include #endif #include #include #include #define DEFAULT 0 #define PORTAGE 1 #define TECRA 2 int GetMachineID(int *id) { unsigned short lsb,msb; unsigned char fl1,fl2; return 0; asm ("movw $0xfe00,%%ax\n\t" \ "movw $0x0070,%%bx\n\t" \ "movl $0x000ffffa,%%edx\n\t" \ "inb $0xb2,%%al\n\t" \ "movw %%cx,%0\n\t" \ "lahf\n\t" \ "movb %%ah,%1\n\t" \ "movw $0xfe00,%%ax\n\t" \ "movw $0x0070,%%bx\n\t" \ "movl $0x000ffffe,%%edx\n\t" \ "inb $0xb2,%%al\n\t" \ "movw %%cx,%2\n\t" \ "lahf\n\t" \ "movb %%ah,%3\n" :"=m" (lsb), "=m" (fl1), "=m" (msb), "=m" (fl2) \ : \ : "memory" ); *id = (lsb & 0xff) + 0x100*(msb & 0xff); return ((fl1 & 0x01)==1) || ((fl2 & 0x01)==1); } void FanOn(int method) { switch (method) { case PORTAGE: asm("cli\n\t" \ "movb $0xbe,%al\n\t" \ "outb %al,$0xe4\n\t" \ "inb $0xe5,%al\n\t" \ "andb $0xfe,%al\n\t" \ "movb %al,%ah\n\t" \ "movb $0xbe,%al\n\t" \ "outb %al,$0xe4\n\t" \ "movb %ah,%al\n\t" \ "outb %al,$0xe5\n\t" \ "sti"); break; case TECRA: asm("cli\n\t" \ "movw $0x00e4,%dx\n\t" \ "movb $0xe0,%al\n\t" \ "outb %al,%dx\n\t" \ "incw %dx\n\t" \ "inb %dx,%al\n\t" \ "orw $0x0001,%ax\n\t" \ "decw %dx\n\t" \ "movb %al,%ah\n\t" \ "movb $0xe0,%al\n\t" \ "outw %ax,%dx\n\t" \ "sti"); break; default: asm ("movw $0xffff,%ax\n\t" \ "movw $0x0004,%bx\n\t" \ "movw $0x0001,%cx\n\t" \ "inb $0xb2,%al"); break; } return; } void FanOff(int method) { switch (method) { case PORTAGE: asm("cli\n\t" \ "movb $0xbe,%al\n\t" \ "outb %al,$0xe4\n\t" \ "inb $0xe5,%al\n\t" \ "orb $0x01,%al\n\t" \ "movb %al,%ah\n\t" \ "movb $0xbe,%al\n\t" \ "outb %al,$0xe4\n\t" \ "movb %ah,%al\n\t" \ "outb %al,$0xe5\n\t" \ "sti"); break; case TECRA: asm("cli\n\t" \ "movw $0x00e4,%dx\n\t" \ "movb $0xe0,%al\n\t" \ "outb %al,%dx\n\t" \ "incw %dx\n\t" \ "inb %dx,%al\n\t" \ "andw $0xfffe,%ax\n\t" \ "decw %dx\n\t" \ "movb %al,%ah\n\t" \ "movb $0xe0,%al\n\t" \ "outw %ax,%dx\n\t" \ "sti"); break; default: asm ("movw $0xffff,%ax\n\t" \ "movw $0x0004,%bx\n\t" \ "movw $0x0000,%cx\n\t" \ "inb $0xb2,%al"); break; } return; } int FanStatus(int method) { unsigned short status; switch(method) { case PORTAGE: asm("cli\n\t" \ "movb $0xbe,%%al\n\t" \ "outb %%al,$0xe4\n\t" \ "inb $0xe5,%%al\n\t" \ "andw $0x0001,%%ax\n\t" \ "movw %%ax,%0\n\t" \ "sti\n" :"=m" (status) : : "memory" ); status = (status==0x00) ? 0x01:0x00; break; case TECRA: asm("cli\n\t" \ "movw $0x00e4,%%dx\n\t" \ "movb $0xe0,%%al\n\t" \ "outb %%al,%%dx\n\t" \ "incw %%dx\n\t" \ "inb %%dx,%%al\n\t" \ "andw $0x0001,%%ax\n\t" "movw %%ax,%0\n\t" \ "sti\n" :"=m" (status) : : "memory" ); break; default: asm ("pushl %%eax\n\t" \ "pushl %%ebx\n\t" \ "pushl %%ecx\n\t" \ "movw $0xfefe,%%ax\n\t" \ "movw $0x0004,%%bx\n\t" \ "movw $0x0000,%%cx\n\t" \ "inb $0xb2,%%al\n\t" \ "andw $0x0001,%%cx\n\t" \ "movw %%cx,%0\n\t" \ "popl %%ecx\n\t" \ "popl %%ebx\n\t" \ "popl %%eax\n" :"=m" (status) : : "memory" ); break; } return (int) status; } int main(int argc, char *argv[]) { int method,id; struct passwd *pw; char *name; /* get the necessary I/O permissions */ #ifdef NONONO if (iopl(3)) { printf("fan: can't get I/O permissions.\n"); exit (1); } #endif /* NONONO */ if ( i386_set_ioperm( 0xb2, 4, 1) ) perror("ioperm()"); /* drop root priveleges to minimize security risk of running suid root */ /* seteuid(getuid()); setegid(getgid()); */ /* open connection to system logger */ openlog("fan", LOG_PID | LOG_CONS, LOG_USER); /* get user name */ pw = getpwuid(getuid()); name = pw ? pw->pw_name : getenv("LOGNAME"); /* select a method based on the model we are running on */ method = DEFAULT; if (GetMachineID(&id)==0x00) { if (id==0xfccb) method = PORTAGE; else if (id==0xfccc) method = TECRA; } /* process command line arguments */ if ((--argc>0) && ((*++argv)[0]=='-')) switch (*++argv[0]) { case 'n': /* turn the fan on */ FanOn(method); syslog(LOG_INFO, "cooling fan turned on by %s", name); break; case 'f': /* turn the fan off */ FanOff(method); syslog(LOG_INFO, "cooling fan turned off by %s", name); break; default: printf("fan: illegal option %s\nUsage: fan [-n|f]\n", argv[0]); exit(1); } /* Toshiba's fan.exe waits here for 0.1 seconds, so we do the same */ usleep(100000); /* print the current status of the fan */ if (FanStatus(method)==0x00) printf("Fan is off.\n"); else printf("Fan is on.\n"); return 0; } --xHFwDpU9dbj6ez1V-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 8:20: 9 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from rigel.cs.pdx.edu (rigel.cs.pdx.edu [131.252.208.59]) by hub.freebsd.org (Postfix) with ESMTP id 2574C37B718 for ; Wed, 14 Mar 2001 08:19:57 -0800 (PST) (envelope-from jrb@cs.pdx.edu) Received: from sirius.cs.pdx.edu (root@sirius.cs.pdx.edu [131.252.208.57]) by rigel.cs.pdx.edu (8.9.1/8.9.1) with ESMTP id IAA05740; Wed, 14 Mar 2001 08:19:56 -0800 (PST) Received: from sirius.cs.pdx.edu (jrb@localhost [127.0.0.1]) by sirius.cs.pdx.edu (8.8.6/8.8.5) with ESMTP id IAA17160; Wed, 14 Mar 2001 08:19:54 -0800 (PST) Message-Id: <200103141619.IAA17160@sirius.cs.pdx.edu> To: Kris Kennaway Cc: freebsd-mobile@freebsd.org Subject: Re: Mobile IP implementation for FreeBSD In-Reply-To: Your message of "Wed, 14 Mar 2001 03:22:19 PST." <20010314032219.A30923@mollari.cthul.hu> Date: Wed, 14 Mar 2001 08:19:54 -0800 From: Jim Binkley Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org please see http://www.cs.pdx.edu/research/SMN for a FreeBSD version. I last ported it to 3.2, and am in the process of porting it to 4.2. for ipv4 only. Jim Binkley jrb@cs.pdx.edu Your message <20010314032219.A30923@mollari.cthul.hu>: > >--BOKacYhQ+x31HxR3 >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Tue, Mar 13, 2001 at 02:48:37PM -0800, Guangrui Fu wrote: >> Hi, >>=20 >> I'm looking for open-sourced Mobile IP implementation >> on FreeBSD. Could anyone please give me some >> information? > >KAME (www.kame.net) has an experimental implementation which will be >integrated into FreeBSD at some point in the future once it's >considered ready enough. > >Kris > >--BOKacYhQ+x31HxR3 >Content-Type: application/pgp-signature >Content-Disposition: inline > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.0.4 (FreeBSD) >Comment: For info see http://www.gnupg.org > >iD8DBQE6r1RrWry0BWjoQKURAq+5AKDQhahBiMpxloTDQgsLF5jphJh34ACdEJIf >0nbm260/T/ZLfyu+IYWN4/4= >=D/Zh >-----END PGP SIGNATURE----- > >--BOKacYhQ+x31HxR3-- > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-mobile" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 8:38:37 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id A659937B718; Wed, 14 Mar 2001 08:38:31 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id IAA47422; Wed, 14 Mar 2001 08:36:47 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200103141636.IAA47422@gndrsh.dnsmgr.net> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <200103141405.f2EE5Ks71827@aslan.scsiguy.com> from "Justin T. Gibbs" at "Mar 14, 2001 07:05:20 am" To: gibbs@scsiguy.com (Justin T. Gibbs) Date: Wed, 14 Mar 2001 08:36:47 -0800 (PST) Cc: bright@wintelcom.net (Alfred Perlstein), Helge.Oldach@de.origin-it.com (Helge Oldach), oberman@es.net, sos@freebsd.dk, mobile@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >First off, some disk caches are getting > 10megs, that's a lot > >of potnetial seeking after loosing power depending on the cache > >contents... > > I've heard that most modern drives reserve a contiguous area of the > disk the size of the cache near where the heads park to dump any > cache contents on power outage. This avoids most if not all seeking. > When the disk powers up again, the reserve track is read and the > transactions are written to the correct locations. Any disk that does > this should be safe to use with write caching enabled. As some one who has spent some time working with disk drive manufactures in the far past all sorts of work is done to make sure that the write cache is not a failure mechanism for lost data. Some of the designs include things like using the spindle motor as a generator and the inertia of the platters to drive it to insure the drive has adaquate power for a long enough period to flush any cached data. Other things done are in non-segmented write caches is to only cache write data for the current track (this is actually where the write cache does most of its good) and always flush it before doing any seek. Only broken WC designs loose data in a power out sitation. There are many broken designs out there. There are also many that work perfectly. The general tell tell on this is what state the WCE bit is in when the drive comes from the factory. Those manufactures who have good designs tend to ship with WCE on, those that tend to loose data always ship with WCE off. With the wonderful breakthroughs in supercapacitors it should now be possible to have some very large caches. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 9:44:58 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id C634837B718 for ; Wed, 14 Mar 2001 09:44:50 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA15151; Wed, 14 Mar 2001 10:44:33 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id KAA25145; Wed, 14 Mar 2001 10:44:31 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15023.44543.137285.702518@nomad.yogotech.com> Date: Wed, 14 Mar 2001 10:44:31 -0700 (MST) To: The Babbler Cc: Gerhard Sittig , freebsd-mobile@FreeBSD.ORG Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? In-Reply-To: <3AAF06E8.103042C6@babbleon.org> References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <20010312174852.T20830@speedy.gsinet> <3AAF06E8.103042C6@babbleon.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Do you 'ifconfig down' the card *prior* to removal? For my own > > sake I would get used to some sort of this behaviour ... :> Just > > make sure nothing's using the card when you unplug it instead of > > dazzling all the drivers / apps with events there's no card for. > > Heck, no. I just pop the card out. Windows gets upset if you do this, > but Linux is quite happy if I insert it and remove it willy-nilly and > never type in any commands at all. It is all just handled > automatically. Note, it's *impossible* due to the design constraints of PCMCIA hardware to do this right everytime. Because it works in Linux doesn't mean it's not doing bad things. It's just that you're really lucky. (Seriously). Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 10:21:17 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mymlan.lifix.fi (mymlan.lifix.fi [195.197.211.98]) by hub.freebsd.org (Postfix) with ESMTP id 9764937B71C; Wed, 14 Mar 2001 10:21:07 -0800 (PST) (envelope-from ban@lifix.fi) Received: from ban by mymlan.lifix.fi with local id 14dF1v-0004t1-00; Wed, 14 Mar 2001 19:25:47 +0200 Date: Wed, 14 Mar 2001 19:25:47 +0200 From: Bjorn Andersson To: Guangrui Fu Cc: mobile-ip , freebsd-net , freebsd-mobile Subject: Re: Mobile IP implementation for FreeBSD Message-ID: <20010314192547.B18619@mymlan.lifix.fi> Mail-Followup-To: Bjorn Andersson , Guangrui Fu , mobile-ip , freebsd-net , freebsd-mobile References: <20010313224837.21080.qmail@web3102.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010313224837.21080.qmail@web3102.mail.yahoo.com>; from guangruifu@yahoo.com on Tue, Mar 13, 2001 at 02:48:37PM -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 13 2001, at 14:48:37 -0800, Guangrui Fu wrote: > I'm looking for open-sourced Mobile IP implementation > on FreeBSD. Could anyone please give me some > information? Check out the Monarch Project: http://www.monarch.cs.cmu.edu/ Björn -- Björn Andersson +358 50 341 2556 Lifix Systems Oy PGP id 5AFC144B Yliopistonkatu 5, 3rd floor; FIN-00100 Helsinki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 11: 4:28 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from gollum.esys.ca (dhcp198-52.esys.ca [198.161.92.52]) by hub.freebsd.org (Postfix) with ESMTP id 08D5737B71C; Wed, 14 Mar 2001 11:04:23 -0800 (PST) (envelope-from lyndon@gollum.esys.ca) Received: from localhost (localhost [127.0.0.1]) by gollum.esys.ca (8.11.3/8.11.3) with ESMTP id f2EJ48c09287; Wed, 14 Mar 2001 12:04:08 -0700 (MST) (envelope-from lyndon@gollum.esys.ca) Message-Id: <200103141904.f2EJ48c09287@gollum.esys.ca> From: Lyndon Nerenberg Organization: ACI / Messagingdirect X-URL: http://www.messagingdirect.com/ To: Bjorn Andersson Cc: mobile-ip , freebsd-net , freebsd-mobile Subject: Re: Mobile IP implementation for FreeBSD In-Reply-To: Message from Bjorn Andersson of "Wed, 14 Mar 2001 19:25:47 +0200." <20010314192547.B18619@mymlan.lifix.fi> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9284.984596647.1@localhost> Date: Wed, 14 Mar 2001 12:04:08 -0700 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I'm looking for open-sourced Mobile IP implementation > > on FreeBSD. > Check out the Monarch Project: > http://www.monarch.cs.cmu.edu/ This supports FreeBSD 2.2.x, which is long dead. (And this was the case for the other mobile ip implementations I tracked down.) Is anyone working on this for a current version of FreeBSD (4.x) ? --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 11:17: 2 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 8D15637B719; Wed, 14 Mar 2001 11:16:54 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id MAA16832; Wed, 14 Mar 2001 12:16:34 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id MAA25818; Wed, 14 Mar 2001 12:16:34 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15023.50066.334891.956685@nomad.yogotech.com> Date: Wed, 14 Mar 2001 12:16:34 -0700 (MST) To: Lyndon Nerenberg Cc: Bjorn Andersson , mobile-ip , freebsd-net , freebsd-mobile Subject: Re: Mobile IP implementation for FreeBSD In-Reply-To: <200103141904.f2EJ48c09287@gollum.esys.ca> References: <20010314192547.B18619@mymlan.lifix.fi> <200103141904.f2EJ48c09287@gollum.esys.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I'm looking for open-sourced Mobile IP implementation > > > on FreeBSD. > > > Check out the Monarch Project: > > http://www.monarch.cs.cmu.edu/ > > This supports FreeBSD 2.2.x, which is long dead. FreeBSD's networking stack isn't that much different from FreeBSD 2.X (or for that matter FreeBSD 1.X) to what it is now. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 11:50:19 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by hub.freebsd.org (Postfix) with ESMTP id B25B337B72E for ; Wed, 14 Mar 2001 11:50:12 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 14dHHf-0005CL-00 for mobile@freebsd.org; Wed, 14 Mar 2001 14:50:11 -0500 Date: Wed, 14 Mar 2001 14:50:10 -0500 From: Peter Radcliffe To: mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Message-ID: <20010314145010.A19141@pir.net> Reply-To: mobile@freebsd.org Mail-Followup-To: mobile@freebsd.org References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> <3AAF047F.341981B2@babbleon.org> <20010314075132.A8440@pir.net> <3AAF77CD.5B204389@babbleon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AAF77CD.5B204389@babbleon.org>; from bts@babbleon.org on Wed, Mar 14, 2001 at 08:53:17AM -0500 X-fish: < Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The Babbler probably said: > Damnit, you are really starting to get annoying. You are as bad as the > blind "everything Windows does must be best" advocates. > > I said I This conversation is no longer useful. > the area of gateways, although was able to get this working under Linux > with relative ease. Then go use Linux is you think it's so much better. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 12:16:48 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id A22DB37B71C for ; Wed, 14 Mar 2001 12:16:40 -0800 (PST) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 5849 invoked by uid 0); 14 Mar 2001 20:16:39 -0000 Received: from p3ee20a8c.dip.t-dialin.net (HELO speedy.gsinet) (62.226.10.140) by mail.gmx.net (mp022-rz3) with SMTP; 14 Mar 2001 20:16:39 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id TAA22484 for freebsd-mobile@freebsd.org; Wed, 14 Mar 2001 19:43:26 +0100 Date: Wed, 14 Mar 2001 19:43:26 +0100 From: Gerhard Sittig To: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Message-ID: <20010314194326.X20830@speedy.gsinet> Mail-Followup-To: freebsd-mobile@freebsd.org References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> <3AAF047F.341981B2@babbleon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3AAF047F.341981B2@babbleon.org>; from bts@babbleon.org on Wed, Mar 14, 2001 at 12:41:20AM -0500 Organization: System Defenestrators Inc. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 14, 2001 at 00:41 -0500, The Babbler wrote: > > I read the FreeBSD readme. And I've had a nubmer of posting in > the emultors group as I got things working there, too. The > bridging would never work for me, but my final conclusion is > that my card doesn't work with bridging, I guess. Only some > cards do. (It says *that* in the handbook and the bridge man > page.) It has been stated in the thread before, but let me repeat it: You have this experience of "bridging doesn't work" with a -RELEASE. Did you ever consider using -STABLE? You might want to visit the cvs-all archive and look out for luigi@FreeBSD.org's commit messages to RELENG_4. There's been a lot of them related to bridging lately (late January, I guess). I don't know if simple boot / fixit floppies will enable you to check this setup. But you might want to update your system after reading the commit messages. And then there have been recent threads about plugging some netgraph nodes together to form a router / bridge / packet filter. NG has been around for quite a while (4.0?), but I understand recent development made it even more suitable for this kind of job. It will be worth a look, too. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 12:17:40 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from larry.compuage.com (larry.compuage.com [208.233.246.4]) by hub.freebsd.org (Postfix) with ESMTP id 3C79C37B71D for ; Wed, 14 Mar 2001 12:17:34 -0800 (PST) (envelope-from kelly@compuage.com) Received: from hnet04.kellyhendrix.com (unverified [208.233.247.37]) by larry.compuage.com (Vircom SMTPRS 4.0.179) with ESMTP id for ; Wed, 14 Mar 2001 15:13:54 -0500 Received: by hnet04.kellyhendrix.com (Postfix, from userid 1001) id B634A18CB0; Wed, 14 Mar 2001 15:19:19 -0500 (EST) Date: Wed, 14 Mar 2001 15:19:19 -0500 From: Kelly Hendrix To: freebsd-mobile@freebsd.org Subject: DVD drive not detected at startup Message-ID: <20010314151919.A3595@hnet04.kellyhendrix.com> Reply-To: Kelly Hendrix Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Freebsd-Version: FreeBSD 4.3-BETA i386 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings At startup, my dvd drive is not recognized and I get the error ata0-slave: identify retries exceeded. This is on a Dell Inspiron 8000. The result of uname -a is : FreeBSD mobile.kellyhendrix.com 4.3-BETA FreeBSD 4.3-BETA#2: Wed Mar 14 14:25:46 EST 2001 root@mobile.kellyhendrix.com:/usr/src/sys/compile/mobile i386 I did manage to boot and install 4.2-RELEASE from that drive, but I can't remember whether or not after the install if it was detected. (Guess I was in too much of a hurry to get X and sound up and working) According to windows the drive is a LG DVD-ROM DRN8080B. Just wondering if anyone could give me any insight into this problem. In my kernel config, I've tried both the ata and ata0 and ata1 entries with the same results. I've also commented and uncommented both ATA_STATIC_ID and ATA_ENABLE_ATAPI_DMA options and rebuilt the kernel. There is also an atapicd device entry. Just wondering if anyone could give me any insight on how to fix this problem. TIA Kelly -- ______________________________________________________________________ | There are two ways to live your life. One is as though nothing is a | | miracle. The other is as though everything is a miracle. | | | | Albert Einstein (1879-1955) | |______________________________________________________________________| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 12:26:14 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 2184537B718; Wed, 14 Mar 2001 12:26:08 -0800 (PST) (envelope-from krepel@fokus.gmd.de) Received: from fokus.gmd.de (dial-05 [193.174.152.250]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id VAA08733; Wed, 14 Mar 2001 21:25:58 +0100 (MET) Message-ID: <3AAFD3DB.6381F3C9@fokus.gmd.de> Date: Wed, 14 Mar 2001 21:26:08 +0100 From: Falco Reply-To: krepel@fokus.gmd.de X-Mailer: Mozilla 4.76 (Macintosh; U; PPC) X-Accept-Language: en,de MIME-Version: 1.0 To: itojun@iijlab.net Cc: mobile-ip , freebsd-net , freebsd-mobile Subject: Re: Mobile IP implementation for FreeBSD References: <23798.984574232@coconut.itojun.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Perhaps you have allready find this: http://www.mobile-ip.de Some Links, but no for FreeBSD 4.x. But if you find an implementation there you could test it. Falco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 13: 5:32 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from vortex.greycat.com (vortex.greycat.com [207.173.133.4]) by hub.freebsd.org (Postfix) with SMTP id 3DFD737B718 for ; Wed, 14 Mar 2001 13:05:28 -0800 (PST) (envelope-from dann@bigphred.greycat.com) Received: (qmail 12286 invoked from network); 14 Mar 2001 21:05:25 -0000 Received: from bigphred.greycat.com (207.173.133.2) by vortex.greycat.com with SMTP; 14 Mar 2001 21:05:25 -0000 Received: (from dann@localhost) by bigphred.greycat.com (8.11.1/8.11.1) id f2EL5Lq45680; Wed, 14 Mar 2001 13:05:21 -0800 (PST) (envelope-from dann) Date: Wed, 14 Mar 2001 13:05:21 -0800 From: Dann Lunsford To: Ben Lovett Cc: mobile@freebsd.org Subject: Re: Tosh 2595XDVD -- fan control? Message-ID: <20010314130521.A45519@greycat.com> Reply-To: Dann Lunsford References: <20010313234128.A70849@greycat.com> <20010314063246.A12367@bsdguru.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010314063246.A12367@bsdguru.com>; from blovett@bsdguru.com on Wed, Mar 14, 2001 at 06:32:46AM -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org WOW! This is *very* cool; thanks a LOT! Will go over this carefully later on. Where there other Tosh hardware utils at the same place? And where did you find this (yeah, I'm enthused about this :-)). I wish Toshiba and other HUBGA companies would release more detailed hardware programming material; I still remember building S-100 boards with a great deal of pleasure. *sigh* Thanks again! -- Dann Lunsford The only thing necessary for the triumph of evil dann@greycat.com is that men of good will do nothing. -- Cicero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 14:24:38 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from melete.ch.intel.com (chfdns02.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id 33A1D37B719 for ; Wed, 14 Mar 2001 14:24:36 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.35 2001/02/12 09:03:45 smothers Exp $) with ESMTP id WAA02146 for ; Wed, 14 Mar 2001 22:24:30 GMT Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.14 2001/01/02 18:39:59 steved Exp $) with ESMTP id PAA19469 for ; Wed, 14 Mar 2001 15:24:30 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id RAA13810; Wed, 14 Mar 2001 17:24:30 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15023.61342.400884.548056@hip186.ch.intel.com> Date: Wed, 14 Mar 2001 15:24:30 -0700 To: mobile@freebsd.org Subject: Dell Latitude CPx J - good match for 4-STABLE? X-Mailer: VM 6.91 under Emacs 20.7.2 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've searched the archives for -questions, -mobile, and -stable and it appears that most people are having reasonable success using FreeBSD with a Dell Latitude CPx J laptop. Can anybody confirm that for me? Seems that people have had problems here and there with suspending properly and APM, etc. I'm wondering if that's now fixed and working (most of the things I found were dated towards the late summer/fall of 2000)? I'm looking at buying a used one primarily to run windoze, but I would also like to dual boot into FreeBSD so I'm trying not to buy a laptop that's on the "black list." Please cc: replies, thank you for your time! -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds New WCCG battle cry: "We do it in 1/2 the time, | | 480-554-9092 CH6-210 with 1/2 the people for 1/2 our raises." | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 14:30:18 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from the.oneinsane.net (the.oneinsane.net [66.42.61.25]) by hub.freebsd.org (Postfix) with ESMTP id 5B6DC37B719 for ; Wed, 14 Mar 2001 14:30:15 -0800 (PST) (envelope-from blovett@venus.bsdguru.com) Received: from darkstar.bsdguru.com (unknown [165.24.155.244]) by the.oneinsane.net (Postfix) with ESMTP id 53AF29B9F; Wed, 14 Mar 2001 14:30:13 -0800 (PST) Received: from venus.bsdguru.com (venus.n2.net [207.113.133.11]) by darkstar.bsdguru.com (Postfix) with ESMTP id 0DF721E3F; Wed, 14 Mar 2001 14:30:09 -0800 (PST) Received: by venus.bsdguru.com (Postfix, from userid 1000) id 87C3266; Wed, 14 Mar 2001 14:30:05 -0800 (PST) Date: Wed, 14 Mar 2001 14:30:04 -0800 From: Ben Lovett To: Dann Lunsford Cc: mobile@freebsd.org Subject: Re: Tosh 2595XDVD -- fan control? Message-ID: <20010314143004.A42213@bsdguru.com> References: <20010313234128.A70849@greycat.com> <20010314063246.A12367@bsdguru.com> <20010314130521.A45519@greycat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010314130521.A45519@greycat.com>; from dann@greycat.com on Wed, Mar 14, 2001 at 01:05:21PM -0800 X-Organization: San Diego BSD Users Group [http://www.sdbug.org] X-Disclaimer: All messages are the opinion of my employer.. They just don't know it yet. X-Operating-System: FreeBSD venus 4.2-STABLE X-Moon: The Moon is Waning Gibbous (70% of Full) X-GPG-Key: http://www.oneinsane.net/~blovett/blovett.pgp X-GPG-Fingerprint: C75F A722 1518 03B8 26C3 77A1 7C76 8AFA EBAB 2004 X-Uptime: 1:23PM up 8:41, 3 users, load averages: 0.05, 0.17, 0.17 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I believe I saw Dann Lunsford (dann@greycat.com) write this: > WOW! This is *very* cool; thanks a LOT! Will go over this carefully > later on. Where there other Tosh hardware utils at the same place? > And where did you find this (yeah, I'm enthused about this :-)). > I wish Toshiba and other HUBGA companies would release more detailed > hardware programming material; I still remember building S-100 boards > with a great deal of pleasure. *sigh* > > Thanks again! > > -- > Dann Lunsford The only thing necessary for the triumph of evil > dann@greycat.com is that men of good will do nothing. -- Cicero > I actually sent an email to this list (-mobile) back in June or July of last year requesting that somebody see about hacking that together for me out of the Toshiba linux utils package .. This little hack has saved my lap from being burned many a times ;) TTYL -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Ben Lovett printf("Hello world!); blovett@bsdguru.com return 0; -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- The best things in life are free, but the expensive ones are still worth a look. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 15:17:11 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from web3102.mail.yahoo.com (web3102.mail.yahoo.com [204.71.202.187]) by hub.freebsd.org (Postfix) with SMTP id AAAE537B718 for ; Wed, 14 Mar 2001 15:17:07 -0800 (PST) (envelope-from guangruifu@yahoo.com) Message-ID: <20010314231707.7672.qmail@web3102.mail.yahoo.com> Received: from [216.98.102.225] by web3102.mail.yahoo.com; Wed, 14 Mar 2001 15:17:07 PST Date: Wed, 14 Mar 2001 15:17:07 -0800 (PST) From: Guangrui Fu Subject: Re: Dell Latitude CPx J - good match for 4-STABLE? To: John Reynolds~ , mobile@freebsd.org In-Reply-To: <15023.61342.400884.548056@hip186.ch.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi, a similar question, does anyone tried FreeeBSD 4.2 with Sony VAIO notebooks and if so, which series? Thanks a lot. G. --- John Reynolds~ wrote: > > I've searched the archives for -questions, -mobile, > and -stable and it appears > that most people are having reasonable success using > FreeBSD with a Dell > Latitude CPx J laptop. Can anybody confirm that for > me? Seems that people have > had problems here and there with suspending properly > and APM, etc. I'm > wondering if that's now fixed and working (most of > the things I found were > dated towards the late summer/fall of 2000)? > > I'm looking at buying a used one primarily to run > windoze, but I would also > like to dual boot into FreeBSD so I'm trying not to > buy a laptop that's on the > "black list." > > Please cc: replies, thank you for your time! > > -Jr > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > | John Reynolds New WCCG battle cry: "We > do it in 1/2 the time, | > | 480-554-9092 CH6-210 with 1/2 the > people for 1/2 our raises." | > | jreynold@sedona.ch.intel.com > http://www-aec.ch.intel.com/~jreynold/ | > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 15:40:49 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by hub.freebsd.org (Postfix) with ESMTP id 78F5F37B71E for ; Wed, 14 Mar 2001 15:40:44 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 14dKsl-0006mP-00 for mobile@freebsd.org; Wed, 14 Mar 2001 18:40:43 -0500 Date: Wed, 14 Mar 2001 18:40:42 -0500 From: Peter Radcliffe To: mobile@freebsd.org Subject: Re: Dell Latitude CPx J - good match for 4-STABLE? Message-ID: <20010314184042.A25999@pir.net> Reply-To: mobile@freebsd.org Mail-Followup-To: mobile@freebsd.org References: <15023.61342.400884.548056@hip186.ch.intel.com> <20010314231707.7672.qmail@web3102.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010314231707.7672.qmail@web3102.mail.yahoo.com>; from guangruifu@yahoo.com on Wed, Mar 14, 2001 at 03:17:07PM -0800 X-fish: < Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Guangrui Fu probably said: > a similar question, does anyone tried FreeeBSD 4.2 with Sony VAIO > notebooks and if so, which series? Thanks a lot. I've run FreeBSD on the 505TR, Z505HS and F430. Other people I know have run it on the Z505R and many others. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 15:54:19 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 01F8437B718 for ; Wed, 14 Mar 2001 15:54:17 -0800 (PST) (envelope-from dom@happygiraffe.net) Received: from myrddin.demon.co.uk ([158.152.54.180] helo=ppe.happygiraffe.net) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 14dL5r-000DJN-0B; Wed, 14 Mar 2001 23:54:16 +0000 Received: by ppe.happygiraffe.net (Postfix, from userid 1000) id 9A96F4CA; Wed, 14 Mar 2001 23:54:12 +0000 (GMT) Date: Wed, 14 Mar 2001 23:54:12 +0000 To: Guangrui Fu Cc: John Reynolds~ , mobile@freebsd.org Subject: Re: Dell Latitude CPx J - good match for 4-STABLE? Message-ID: <20010314235412.A53709@ppe.happygiraffe.net> References: <15023.61342.400884.548056@hip186.ch.intel.com> <20010314231707.7672.qmail@web3102.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010314231707.7672.qmail@web3102.mail.yahoo.com>; from guangruifu@yahoo.com on Wed, Mar 14, 2001 at 03:17:07PM -0800 X-Warning: Incoming message from The Big Giant Head! X-OS: FreeBSD 4.3-BETA i386 X-Uptime: 11:52PM up 2:57, 6 users, load averages: 1.39, 1.37, 1.34 From: dom@happygiraffe.net (Dominic Mitchell) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 14, 2001 at 03:17:07PM -0800, Guangrui Fu wrote: > a similar question, does anyone tried FreeeBSD 4.2 > with > Sony VAIO notebooks and if so, which series? Thanks a > lot. I've got FreeBSD 4.2 (4.3-BETA now) working great on my Z600TEK. I think that's a euro model, though. It's model number is PCG-5316, if that's any use. Very nice laptop, very compact, everything works well (but I had to fiddle a little with pccardd). -- M-x smite-the-infidel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 16:12:44 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id 4598237B71A for ; Wed, 14 Mar 2001 16:12:40 -0800 (PST) (envelope-from eculp@EnContacto.Net) Received: (from root@localhost) by dsl.MexComUSA.net (8.11.3/8.11.3) id f2F074Y69172 for freebsd-mobile@FreeBSD.ORG; Wed, 14 Mar 2001 16:07:04 -0800 (PST) (envelope-from eculp@EnContacto.Net) Received: from 63.205.16.202 ( [63.205.16.202]) as user eculp@EnContacto.Net by Mail.MexComUSA.net with HTTP; Wed, 14 Mar 2001 16:07:04 -0800 Message-ID: <984614824.3ab007a89da52@Mail.MexComUSA.net> Date: Wed, 14 Mar 2001 16:07:04 -0800 From: Edwin Culp To: freebsd-mobile@FreeBSD.ORG Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> <3AAF047F.341981B2@babbleon.org> <20010314194326.X20830@speedy.gsinet> In-Reply-To: <20010314194326.X20830@speedy.gsinet> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs X-Originating-IP: 63.205.16.202 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoting Gerhard Sittig : > On Wed, Mar 14, 2001 at 00:41 -0500, The Babbler wrote: > > > > I read the FreeBSD readme. And I've had a nubmer of posting in > > the emultors group as I got things working there, too. The > > bridging would never work for me, but my final conclusion is > > that my card doesn't work with bridging, I guess. Only some > > cards do. (It says *that* in the handbook and the bridge man > > page.) > > It has been stated in the thread before, but let me repeat it: > You have this experience of "bridging doesn't work" with a > -RELEASE. Did you ever consider using -STABLE? You might want > to visit the cvs-all archive and look out for luigi@FreeBSD.org's > commit messages to RELENG_4. There's been a lot of them related > to bridging lately (late January, I guess). > > I don't know if simple boot / fixit floppies will enable you to > check this setup. But you might want to update your system after > reading the commit messages. I really haven't been following this thread but the reference to the fixit floppies reminded me of the link that Luigi has on his dummy net site to a picobsd floppy that is a self contained router/bridge with extras such as bandwidth control. This way you don't have to change O.S.'s or even compile anything just download 1.4M and give it a try. http://www.iet.unipi.it/~luigi/ip_dummynet/ Plus the page, while focused on dummynet, is jam-packed with valuable general information for filtering, firewalls, bridging, etc. If you have already done this and I'm repeating or am answering a question that wasn't asked, please accept my apologies. I should pay more attention to the threads. ed ------------------------------------------------- EnContacto.Net - CafeMania.Net - InternetSalon.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 17:16:56 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from yez.hyperreal.org (gate.sp.collab.net [64.211.228.36]) by hub.freebsd.org (Postfix) with SMTP id 393A837B71E for ; Wed, 14 Mar 2001 17:16:52 -0800 (PST) (envelope-from brian@collab.net) Received: (qmail 15273 invoked by uid 1000); 15 Mar 2001 01:17:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Mar 2001 01:17:43 -0000 Date: Wed, 14 Mar 2001 17:17:43 -0800 (PST) From: Brian Behlendorf X-X-Sender: To: Guangrui Fu Cc: Subject: Re: Dell Latitude CPx J - good match for 4-STABLE? In-Reply-To: <20010314231707.7672.qmail@web3102.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 14 Mar 2001, Guangrui Fu wrote: > a similar question, does anyone tried FreeeBSD 4.2 with Sony VAIO > notebooks and if so, which series? Thanks a lot. Works well on the C1XS, though no support for the winmodem nor camera, nor have I gotten the IR working. Everything else is well-supported. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 18: 0: 4 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from laptop.os2warp.org (asrue1-1-61.cswnet.com [216.84.112.61]) by hub.freebsd.org (Postfix) with ESMTP id 40E9A37B718 for ; Wed, 14 Mar 2001 18:00:00 -0800 (PST) (envelope-from lambert@laptop.os2warp.org) Received: by laptop.os2warp.org (Postfix, from userid 1000) id E4C559C3A; Wed, 14 Mar 2001 17:19:47 -0600 (CST) Date: Wed, 14 Mar 2001 17:19:47 -0600 From: Scott Lambert To: freebsd-mobile@freebsd.org Subject: Re: Tosh 2595XDVD -- fan control? Message-ID: <20010314171947.A905@laptop.os2warp.org> Reply-To: Scott Lambert Mail-Followup-To: Scott Lambert , freebsd-mobile@freebsd.org References: <20010313234128.A70849@greycat.com> <20010314063246.A12367@bsdguru.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010314063246.A12367@bsdguru.com>; from blovett@bsdguru.com on Wed, Mar 14, 2001 at 06:32:46AM -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 14, 2001 at 06:32:46AM -0800, Ben Lovett wrote: > I believe I saw Dann Lunsford (dann@greycat.com) write this: > > Toshiba's reaction on hearing "FreeBSD" or "UNIX" is "Huh?", Anyone got > > a clue? Ideally, I'd just like to type "fan on" or "fan off", but I'll > > I had this very same problem on my Satellite 2505CDS and 2515CDS and > someone was kind enough to port the Linux fan util to FreeBSD so it > works great ;) For what it's worth, this program works on my Satellite 2805-S201. It always says "Fan is off." but it works. Maybe my legs won't catch fire anymore while working with my laptop on my lap. :-) -- Scott Lambert lambert@cswnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 18:19: 7 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from vortex.greycat.com (vortex.greycat.com [207.173.133.4]) by hub.freebsd.org (Postfix) with SMTP id 6F7F137B71A for ; Wed, 14 Mar 2001 18:18:55 -0800 (PST) (envelope-from dann@bigphred.greycat.com) Received: (qmail 14159 invoked from network); 15 Mar 2001 02:18:43 -0000 Received: from bigphred.greycat.com (207.173.133.2) by vortex.greycat.com with SMTP; 15 Mar 2001 02:18:43 -0000 Received: (from dann@localhost) by bigphred.greycat.com (8.11.1/8.11.1) id f2F2IfT46936; Wed, 14 Mar 2001 18:18:41 -0800 (PST) (envelope-from dann) Date: Wed, 14 Mar 2001 18:18:41 -0800 From: Dann Lunsford To: Ben Lovett Cc: mobile@freebsd.org Subject: Re: Tosh 2595XDVD -- fan control? Message-ID: <20010314181841.A46913@greycat.com> Reply-To: Dann Lunsford References: <20010313234128.A70849@greycat.com> <20010314063246.A12367@bsdguru.com> <20010314130521.A45519@greycat.com> <20010314143004.A42213@bsdguru.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010314143004.A42213@bsdguru.com>; from blovett@bsdguru.com on Wed, Mar 14, 2001 at 02:30:04PM -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a followup: The fan control program works like a charm! No problems, temp in case is much better. Nice quiet fan, ejecting all the heat out the rear. This is great! Guess I'll have to take a look for the other utilities for Toshibas out there, see if I can do something similar. Thanks again! -- Dann Lunsford The only thing necessary for the triumph of evil dann@greycat.com is that men of good will do nothing. -- Cicero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 18:30:28 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from bear.mshindo.net (bear.mshindo.net [202.229.42.121]) by hub.freebsd.org (Postfix) with ESMTP id B4D1937B719; Wed, 14 Mar 2001 18:30:21 -0800 (PST) (envelope-from mshindo@mshindo.net) Received: from localhost (IDENT:mshindo@dhcp15.cosinecom.co.jp [202.229.42.15]) by bear.mshindo.net (8.11.1/8.11.1) with ESMTP id f2F2Mfn32999; Thu, 15 Mar 2001 11:22:41 +0900 (JST) (envelope-from mshindo@mshindo.net) Date: Thu, 15 Mar 2001 11:31:01 +0900 (JST) Message-Id: <20010315.113101.74755852.mshindo@mshindo.net> To: itojun@iijlab.net Cc: kris@obsecurity.org, guangruifu@yahoo.com, mobile-ip@sunroof.eng.sun.com, freebsd-net@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Mobile IP implementation for FreeBSD From: Motonori Shindo In-Reply-To: <23798.984574232@coconut.itojun.org> References: <20010314032219.A30923@mollari.cthul.hu> <23798.984574232@coconut.itojun.org> X-Mailer: Mew version 1.95b76 on Emacs 20.7 / Mule 4.0 (HANANOEN) X-PGP-fingerprint: 06 B0 B1 A4 06 C1 6A 14 63 C0 D7 18 01 CD D9 83 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris, From: itojun@iijlab.net Subject: Re: Mobile IP implementation for FreeBSD Date: Wed, 14 Mar 2001 21:50:32 +0900 Message-ID: <23798.984574232@coconut.itojun.org> > >> I'm looking for open-sourced Mobile IP implementation > >> on FreeBSD. Could anyone please give me some > >> information? > > > >KAME (www.kame.net) has an experimental implementation which will be > >integrated into FreeBSD at some point in the future once it's > >considered ready enough. > > KAME does mobile-ip6 only. we don't do mobile-ip4. CMU Monarch Project has a Mobile-IPv4 support for FreeBSD, but it only supports FreeBSD 2.2.2. For more detail, pls refer to: http://www.monarch.cs.cmu.edu/ =--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--= +----+----+ |.. .| | Motonori Shindo |_~__| | | .. |~~_~| Sr. Systems Engineer | . | | CoSine Communications Inc. +----+----+ C o S i n e e-mail: mshindo@cosinecom.com Communications =--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 19:16:38 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from Mail6.nc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 773EC37B71A; Wed, 14 Mar 2001 19:16:27 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by Mail6.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 14 Mar 2001 22:16:22 -0500 Message-ID: <3AB033EC.191F47A0@babbleon.org> Date: Wed, 14 Mar 2001 22:15:56 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Xeon2578@netscape.net, freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: BSD with two NIC's References: <21662211.7E01A45E.00877270@netscape.net> <3AAEF70C.DFFCFCCC@babbleon.org> <0A3465D9.5B1A3086.00877270@netscape.net> <3AAF6F9D.5A3810D8@babbleon.org> <46CED77F.23FFB834.00877270@netscape.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Immediate device timeouts are usually indicative of IRQ conflicts. But there is another problem (and it might even be the same problem, or the original problem); namely, FreeBSD ships with an (IMHO) broken kernel config; at any rate, one that doesn't work with PCMCIA cards. Find the line that looks like this: device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 and change it to just this: device ed and rebuild your kernel. If that doesn't do it, then you probably have an IRQ conflict; you did the "dmesg | grep irq" thing already, right? Xeon2578@netscape.net wrote: > > Thank you very much. Like you said After twicking with the pccard.conf file, i got pccardd > enable the cards: > > irq 3 13 > > config 0x2 "ed0" 3 > config 0x3 "ed1" 13 > > I configured each interface with a different IP Address(different subnets) > but immediately after the ifconfig command I get a message > /kernel: ed0: device timeout for ed0 > and /kernel: ed1: device timeout for ed1 > Besides each interface can ping itself on the respective IP. > But I can't ping other hosts on respective subnets... > > Any Idea...DriverS?? > > The Babbler wrote: > > > > > > Sorry, I was confused anyway. That question is irrelavent. > > > > What you need to try is to edit your /etc/pccard.conf file. > > Copy the entries for those two cards from the /etc/defaults/pccard.conf > > file, > > and change one of the entries to use a different interrupt and entry > > number; eg, > > if the first card is in the defaults file with > > > > config 0x1 "ed" ? > > > > then try making it look like > > > > config 0x2 "ed" 9 > > > > instead. > > > > (Actually, what you need to do is to do > > > > dmesg | grep irq > > > > and see what irqs are free so you can assign one of those. Nine happens > > to be what worked for me.) > > > > Then you just have to play around with it until it works. Of course, > > you have to restart the pccardd every time you change these. > > > > You might be able to get this all easier by using "pccardc enabler" > > until you find workable parameters rather than messing with pccard.conf > > right off the bat, but I didn't personally stumble across pccardc > > enabler 'til after I had might working. > > > > PS: Mine only had an IRQ conflict. It's possible that yours will solve > > the memory conflict itself if you fix the IRQ conflict. After all was > > said & done, mine actually was fixed by putting just this in the > > pccard.conf: > > > > irq 3 9 > > > > > > It's possible that this is all you need--to explicitly list the > > non-conflicting IRQs in your system. > > > > > > > > > > Xeon2578@netscape.net wrote: > > > > > > The Babbler wrote: > > > > > > > > Xeon2578@netscape.net wrote: > > > > > > > > > > Hi - > > > > > > > > > > I was so relievd when I saw your posting on: > > > > > "PCMCIA Questions: 2 NICs & new pccard.conf entry" > > > > > Unfortunately, there were no followups...I am hoping you > > > > > got a solution for your problem, cause I have the same too. > > > > > > > > > > I have two different PCMCIA network cards installed on a SONY(fx101) Laptop > > > > > 1. Netgear FA410TX > > > > > 2. D-Link 650 > > > > > These cards appear to use the exact same resources, > > > > > IRQ 3 and I/O 0x240-0x25F > > > > > The cards are seen by PCCARDD, but either will load but not both. > > > > > If one load, the other produces an error message: > > > > > No free configuration for card "card_name" > > > > > > > > > > > > Are both cards using the same driver (eg, both "ed" or "ep" or > > > > whatever)? > > > > > > > > > > Well yes, they use ed. > > > > > > MAT > > > > > > __________________________________________________________________ > > > Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ > > > > -- > > "Brian, the man from babble-on" bts@babbleon.org > > Brian T. Schellenberger http://www.babbleon.org > > Support http://www.eff.org. Support decss defendents. > > Support http://www.programming-freedom.org. Boycott amazon.com. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > __________________________________________________________________ > Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 19:32:42 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail7.nc.rr.com (mail7.southeast.rr.com [24.93.67.54]) by hub.freebsd.org (Postfix) with ESMTP id BEC8F37B71A for ; Wed, 14 Mar 2001 19:32:37 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail7.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 14 Mar 2001 22:32:35 -0500 Message-ID: <3AB037BB.EADF0432@babbleon.org> Date: Wed, 14 Mar 2001 22:32:11 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Gerhard Sittig Cc: freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> <3AAF047F.341981B2@babbleon.org> <20010314194326.X20830@speedy.gsinet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think I'm having a cultural/linguistic problem. In Linux, there is is a "stable" version and a "development" version, but even the "stable" version is less stable than the released version if you catch it between releases. I'm starting to "get it" that this is not the case with FreeBSD, so I'll check the FreeBSD handbook and find out how to upgrade in the middle of a release cycle and and see if that clears up some of the trouble . . . I'll post the results here once that's done; it'll probably be a couple of days. Gerhard Sittig wrote: > > On Wed, Mar 14, 2001 at 00:41 -0500, The Babbler wrote: > > > > I read the FreeBSD readme. And I've had a nubmer of posting in > > the emultors group as I got things working there, too. The > > bridging would never work for me, but my final conclusion is > > that my card doesn't work with bridging, I guess. Only some > > cards do. (It says *that* in the handbook and the bridge man > > page.) > > It has been stated in the thread before, but let me repeat it: > You have this experience of "bridging doesn't work" with a > -RELEASE. Did you ever consider using -STABLE? You might want > to visit the cvs-all archive and look out for luigi@FreeBSD.org's > commit messages to RELENG_4. There's been a lot of them related > to bridging lately (late January, I guess). > > I don't know if simple boot / fixit floppies will enable you to > check this setup. But you might want to update your system after > reading the commit messages. > > And then there have been recent threads about plugging some > netgraph nodes together to form a router / bridge / packet > filter. NG has been around for quite a while (4.0?), but I > understand recent development made it even more suitable for this > kind of job. It will be worth a look, too. > > virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 > Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Mar 14 19:35:41 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail7.nc.rr.com (mail7.southeast.rr.com [24.93.67.54]) by hub.freebsd.org (Postfix) with ESMTP id DE5C137B719 for ; Wed, 14 Mar 2001 19:35:38 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail7.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 14 Mar 2001 22:35:37 -0500 Message-ID: <3AB03870.AF02329B@babbleon.org> Date: Wed, 14 Mar 2001 22:35:12 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> <3AAF047F.341981B2@babbleon.org> <20010314075132.A8440@pir.net> <3AAF77CD.5B204389@babbleon.org> <20010314145010.A19141@pir.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Radcliffe wrote: > > The Babbler probably said: > > Damnit, you are really starting to get annoying. You are as bad as the > > blind "everything Windows does must be best" advocates. > > > > I said I > > This conversation is no longer useful. > > > the area of gateways, although was able to get this working under Linux > > with relative ease. > > Then go use Linux is you think it's so much better. To tell you the truth, if I had to start over I would never have switched. My primary motivation for switching (better integration with FreeBSD systems at work) turns out not to work out very well anyway, and these problems are frustrating. But at lot of *other* stuff is better about FreeBSD, and switching back is another massive undertaking. I'd prefer to move forward rather than back if I could . . . > > P. > > -- > pir pir@pir.net pir@net.tufts.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 1:57:32 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3F91237B71D for ; Thu, 15 Mar 2001 01:57:29 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2F9vO921416; Thu, 15 Mar 2001 02:57:25 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103150957.f2F9vO921416@harmony.village.org> To: wayne.pascoe@realtime.co.uk Subject: Re: Cardbus support Cc: mobile@FreeBSD.ORG In-reply-to: Your message of "14 Mar 2001 15:00:35 GMT." References: Date: Thu, 15 Mar 2001 02:57:24 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Wayne Pascoe writes: : Just a quick question... Which release is cardbus support slated to be : in? I have all of my desktops and all of my servers moved from Linux : to FreeBSD. I just have 2 laptops still to move. As I already own 3com : cardbus cards, I don't really want to buy new hardware. FreeBSD 5.0. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 1:59: 1 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id F30C437B718 for ; Thu, 15 Mar 2001 01:58:59 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2F9wo921440; Thu, 15 Mar 2001 02:58:50 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103150958.f2F9wo921440@harmony.village.org> To: Garrett Rooney Subject: Re: Cardbus support Cc: Wayne Pascoe , mobile@FreeBSD.ORG In-reply-to: Your message of "Wed, 14 Mar 2001 10:22:20 EST." <20010314102220.A34993@electricjellyfish.net> References: <20010314102220.A34993@electricjellyfish.net> Date: Thu, 15 Mar 2001 02:58:50 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20010314102220.A34993@electricjellyfish.net> Garrett Rooney writes: : there is some cardbus support in -CURRENT, and supposably it works well. : : from what i've heard it probably won't be MFC'd any time soon though, and : since -CURRENT is very much a developers only place these days, you're kind : of stuck. My hope is to not MFC cardbus to 4.x. However, if 5.0 isn't ready by the 4.5 time frame (8mo from now), then there will be much pressure to MFC it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 2: 0:29 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id CBF1F37B718 for ; Thu, 15 Mar 2001 02:00:27 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2FA0H921465; Thu, 15 Mar 2001 03:00:17 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103151000.f2FA0H921465@harmony.village.org> To: nate@yogotech.com (Nate Williams) Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Cc: The Babbler , Gerhard Sittig , freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Wed, 14 Mar 2001 10:44:31 MST." <15023.44543.137285.702518@nomad.yogotech.com> References: <15023.44543.137285.702518@nomad.yogotech.com> <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <20010312174852.T20830@speedy.gsinet> <3AAF06E8.103042C6@babbleon.org> Date: Thu, 15 Mar 2001 03:00:17 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <15023.44543.137285.702518@nomad.yogotech.com> Nate Williams writes: : Note, it's *impossible* due to the design constraints of PCMCIA hardware : to do this right everytime. : : Because it works in Linux doesn't mean it's not doing bad things. It's : just that you're really lucky. (Seriously). This is also true if it just works in FreeBSD too. We can make the windows of death as small as possible, but you can only make them so small. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 4:53:26 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail7.nc.rr.com (mail7.southeast.rr.com [24.93.67.54]) by hub.freebsd.org (Postfix) with ESMTP id 4A60437B718 for ; Thu, 15 Mar 2001 04:53:13 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by mail7.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Thu, 15 Mar 2001 07:53:07 -0500 Message-ID: <3AB0BB19.504935BE@babbleon.org> Date: Thu, 15 Mar 2001 07:52:42 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Nate Williams , Gerhard Sittig , freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? References: <15023.44543.137285.702518@nomad.yogotech.com> <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <20010312174852.T20830@speedy.gsinet> <3AAF06E8.103042C6@babbleon.org> <200103151000.f2FA0H921465@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I find it a bit implausible that the fact that I've had apparent PCMCIA-related crashes at least a half-dozen times in two months with FreeBSD and at most twice over a span of four years with Linux does not in some way reflect a difference between the operating systems, rather than random luck. A 70x incidence rate strongly suggests causality to *me*. Of course, I *am* running the straight-up 4.2 support, not the new PCCARD support. But I'd expect that to *help* with stability for the cards where it works at all. Warner Losh wrote: > > In message <15023.44543.137285.702518@nomad.yogotech.com> Nate Williams writes: > : Note, it's *impossible* due to the design constraints of PCMCIA hardware > : to do this right everytime. > : > : Because it works in Linux doesn't mean it's not doing bad things. It's > : just that you're really lucky. (Seriously). > > This is also true if it just works in FreeBSD too. We can make the > windows of death as small as possible, but you can only make them so > small. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 9:15:40 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 8A6F437B718 for ; Thu, 15 Mar 2001 09:15:38 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2FHFC923360; Thu, 15 Mar 2001 10:15:12 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103151715.f2FHFC923360@harmony.village.org> To: The Babbler Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Cc: Nate Williams , Gerhard Sittig , freebsd-mobile@freebsd.org In-reply-to: Your message of "Thu, 15 Mar 2001 07:52:42 EST." <3AB0BB19.504935BE@babbleon.org> References: <3AB0BB19.504935BE@babbleon.org> <15023.44543.137285.702518@nomad.yogotech.com> <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <20010312174852.T20830@speedy.gsinet> <3AAF06E8.103042C6@babbleon.org> <200103151000.f2FA0H921465@harmony.village.org> Date: Thu, 15 Mar 2001 10:15:12 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <3AB0BB19.504935BE@babbleon.org> The Babbler writes: : I find it a bit implausible that the fact that I've had apparent : PCMCIA-related crashes at least a half-dozen times in two months with : FreeBSD and at most twice over a span of four years with Linux does not : in some way reflect a difference between the operating systems, rather : than random luck. A 70x incidence rate strongly suggests causality to : *me*. Interesting. My brother reports pcmcia related crashes with linux on the order of once or twice a year. He also reports to me that he's never had FreeBSD crash on him once I helped get the pccard issue resolved. He's the only person I know personally that runs both on a regular basis. :-) I guess it is highly variable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 10: 5:58 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 9CCB737B719 for ; Thu, 15 Mar 2001 10:05:54 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA09206; Thu, 15 Mar 2001 11:05:42 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id LAA05256; Thu, 15 Mar 2001 11:05:41 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15025.1141.330249.751565@nomad.yogotech.com> Date: Thu, 15 Mar 2001 11:05:41 -0700 (MST) To: The Babbler Cc: Warner Losh , Nate Williams , Gerhard Sittig , freebsd-mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? In-Reply-To: <3AB0BB19.504935BE@babbleon.org> References: <15023.44543.137285.702518@nomad.yogotech.com> <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <20010312174852.T20830@speedy.gsinet> <3AAF06E8.103042C6@babbleon.org> <200103151000.f2FA0H921465@harmony.village.org> <3AB0BB19.504935BE@babbleon.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I find it a bit implausible that the fact that I've had apparent > PCMCIA-related crashes at least a half-dozen times in two months with > FreeBSD and at most twice over a span of four years with Linux does not > in some way reflect a difference between the operating systems, rather > than random luck. As I've stated in the past, I think either you have mis-configured and/or bad hardware. This is allow very apparent when you state you lose parts of your FS when it crashes, which implies (to me anyway) that you're getting bogus IRQ's that are probably causing FS corruption. If you're hardware is misconfigured, no OS can protect you from data loss. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 10:48:17 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 5A9FF37B718; Thu, 15 Mar 2001 10:48:12 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA09952; Thu, 15 Mar 2001 11:48:09 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id LAA05513; Thu, 15 Mar 2001 11:48:08 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15025.3687.986222.637039@nomad.yogotech.com> Date: Thu, 15 Mar 2001 11:48:07 -0700 (MST) To: The Babbler Cc: Xeon2578@netscape.net, freebsd-questions@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: BSD with two NIC's In-Reply-To: <3AB033EC.191F47A0@babbleon.org> References: <21662211.7E01A45E.00877270@netscape.net> <3AAEF70C.DFFCFCCC@babbleon.org> <0A3465D9.5B1A3086.00877270@netscape.net> <3AAF6F9D.5A3810D8@babbleon.org> <46CED77F.23FFB834.00877270@netscape.net> <3AB033EC.191F47A0@babbleon.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Immediate device timeouts are usually indicative of IRQ conflicts. > > But there is another problem (and it might even be the same problem, or > the original problem); namely, FreeBSD ships with an (IMHO) broken > kernel config; at any rate, one that doesn't work with PCMCIA cards. > > Find the line that looks like this: > > device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 > > and change it to just this: > > device ed > > and rebuild your kernel. The above should not effect PCMCIA cards at all, since the PCMCIA/PCCARD infrastructure completely ignores the settings above. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 11:51:15 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 104AA37B71D; Thu, 15 Mar 2001 11:51:02 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id LAA23598; Thu, 15 Mar 2001 11:50:54 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda23596; Thu Mar 15 11:50:34 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f2FJoOg37579; Thu, 15 Mar 2001 11:50:24 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdq37567; Thu Mar 15 11:49:33 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.3/8.9.1) id f2FJnVF13620; Thu, 15 Mar 2001 11:49:31 -0800 (PST) Message-Id: <200103151949.f2FJnVF13620@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdk13545; Thu Mar 15 11:49:29 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: David Kelly Cc: Pete French , mobile@FreeBSD.ORG, sos@freebsd.dk, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-reply-to: Your message of "Tue, 13 Mar 2001 22:04:23 CST." <200103140404.f2E44Ne16415@grumpy.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Mar 2001 11:49:29 -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200103140404.f2E44Ne16415@grumpy.dyndns.org>, David Kelly writes: > Pete French writes: > > All very interesting, but a small point has been forgotten > > hasnt it ? The way I read this thread is that until recentlly > > write-caching was enabled by default and has now been disabled (hence > > the original obseravtion of disc performance dropping). > > > > I havent noticed that FreeBSD has a bad reputation for loss of data > > in the event of am power outage, and my own experience backs this up. > > As so many people appear to have been running it this way by default until > > now you might have though that if it were a serious problem in reality then > > people would have noticed by now ? > > Well, I am an ex-Linux user who got fed up with Linux trashing my disk 3 > times one week. Each time (kernel panics) the damage was bad enough fsck > (e2fsck?) deleted a lot of critical files making a wipe/reinstall the > fastest way back to a running system. This was shortly after the release > of FreeBSD 2.0.0. Remember it well because that is when I became a > FreeBSD user. Hmm, probably 6 years ago this month. That's the same reason I switched from Linux to FreeBSD 2.0.5 5 or 6 years ago. > Have watched Linux from "outside" since then. Noticed I was not the > only one losing data. From what I've seen the Linux solution was not to > to fix a faulty design but to hack it until it doesn't lose as much. > > Linux was/is very proud of their ext2fs speed. Clearly at the expense of > reliability. Oddly enough that machine got 600k Bytes/sec thruput on > Linux, but 900k Bytes/sec on FreeBSD 2.0.0-RELEASE. 240 MB Western > Digital IDE drive. > > IMO the most reliable settings are the correct thing to do in spite of > simpleminded magazine authors who will "do a shootout" of Linux vs. > FreeBSD using only the stock settings. This is one of the three big reasons we (at our shop) are migrating our infrastructure servers (kerberos, console, file, web, firewall/proxy, etc.) from Linux to FreeBSD. As Linux (specifically RedHat) comes with more toys, bells and whistles, Linux will remain our desktop standard, not to mention the sure-to-be-lost political battle. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 12: 2:32 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from Mail6.nc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 9994037B718; Thu, 15 Mar 2001 12:02:26 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by Mail6.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Thu, 15 Mar 2001 15:02:21 -0500 Message-ID: <3AB11FB3.9F2AB272@babbleon.org> Date: Thu, 15 Mar 2001 15:01:55 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nate Williams Cc: Xeon2578@netscape.net, freebsd-questions@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: BSD with two NIC's References: <21662211.7E01A45E.00877270@netscape.net> <3AAEF70C.DFFCFCCC@babbleon.org> <0A3465D9.5B1A3086.00877270@netscape.net> <3AAF6F9D.5A3810D8@babbleon.org> <46CED77F.23FFB834.00877270@netscape.net> <3AB033EC.191F47A0@babbleon.org> <15025.3687.986222.637039@nomad.yogotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If you say so, but I have two laptops, and neither of them would work my linksys cards before I made this change, and both of them worked after I made it. Maybe it's just voodoo, but it works for me. And I've had mail with people for whom it also seemed to make a difference. So, Xeon, I'd try it anyway. One thing for sure: it won't hurt. Nate Williams wrote: > > > Immediate device timeouts are usually indicative of IRQ conflicts. > > > > But there is another problem (and it might even be the same problem, or > > the original problem); namely, FreeBSD ships with an (IMHO) broken > > kernel config; at any rate, one that doesn't work with PCMCIA cards. > > > > Find the line that looks like this: > > > > device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 > > > > and change it to just this: > > > > device ed > > > > and rebuild your kernel. > > The above should not effect PCMCIA cards at all, since the PCMCIA/PCCARD > infrastructure completely ignores the settings above. > > Nate -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 12: 7:34 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from Mail6.nc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 634B837B718; Thu, 15 Mar 2001 12:07:28 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by Mail6.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Thu, 15 Mar 2001 15:06:21 -0500 Message-ID: <3AB120A3.C9A50843@babbleon.org> Date: Thu, 15 Mar 2001 15:05:55 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Cy Schubert - ITSD Open Systems Group Cc: David Kelly , Pete French , mobile@freebsd.org, sos@freebsd.dk, stable@freebsd.org Subject: Re: Disk I/O problem in 4.3-BETA References: <200103151949.f2FJnVF13620@cwsys.cwsent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Personally, I've had more data loss with FreeBSD. My experience does seem to be unusual, but FreeBSD is no panacea, and no substitute for backups. On the other hand, Linux emulation mode works amazingly well; you don't actually have to give up user programs. I do miss "supermount", but I use vmware and the Linux version of Netscape--which works better under FreeBSD than under Linux. You really don't have to give up much even for a desktop. Cy Schubert - ITSD Open Systems Group wrote: > > In message <200103140404.f2E44Ne16415@grumpy.dyndns.org>, David Kelly > writes: > > Pete French writes: > > > All very interesting, but a small point has been forgotten > > > hasnt it ? The way I read this thread is that until recentlly > > > write-caching was enabled by default and has now been disabled (hence > > > the original obseravtion of disc performance dropping). > > > > > > I havent noticed that FreeBSD has a bad reputation for loss of data > > > in the event of am power outage, and my own experience backs this up. > > > As so many people appear to have been running it this way by default until > > > now you might have though that if it were a serious problem in reality then > > > people would have noticed by now ? > > > > Well, I am an ex-Linux user who got fed up with Linux trashing my disk 3 > > times one week. Each time (kernel panics) the damage was bad enough fsck > > (e2fsck?) deleted a lot of critical files making a wipe/reinstall the > > fastest way back to a running system. This was shortly after the release > > of FreeBSD 2.0.0. Remember it well because that is when I became a > > FreeBSD user. Hmm, probably 6 years ago this month. > > That's the same reason I switched from Linux to FreeBSD 2.0.5 5 or 6 > years ago. > > > > Have watched Linux from "outside" since then. Noticed I was not the > > only one losing data. From what I've seen the Linux solution was not to > > to fix a faulty design but to hack it until it doesn't lose as much. > > > > Linux was/is very proud of their ext2fs speed. Clearly at the expense of > > reliability. Oddly enough that machine got 600k Bytes/sec thruput on > > Linux, but 900k Bytes/sec on FreeBSD 2.0.0-RELEASE. 240 MB Western > > Digital IDE drive. > > > > IMO the most reliable settings are the correct thing to do in spite of > > simpleminded magazine authors who will "do a shootout" of Linux vs. > > FreeBSD using only the stock settings. > > This is one of the three big reasons we (at our shop) are migrating our > infrastructure servers (kerberos, console, file, web, firewall/proxy, > etc.) from Linux to FreeBSD. As Linux (specifically RedHat) comes with > more toys, bells and whistles, Linux will remain our desktop standard, > not to mention the sure-to-be-lost political battle. > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca > Open Systems Group, ITSD, ISTA > Province of BC > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 12:17:23 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 3F56837B718 for ; Thu, 15 Mar 2001 12:17:17 -0800 (PST) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 379 invoked by uid 0); 15 Mar 2001 20:17:15 -0000 Received: from pd9508688.dip.t-dialin.net (HELO speedy.gsinet) (217.80.134.136) by mail.gmx.net (mp021-rz3) with SMTP; 15 Mar 2001 20:17:15 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id SAA25100 for freebsd-mobile@freebsd.org; Thu, 15 Mar 2001 18:13:18 +0100 Date: Thu, 15 Mar 2001 18:13:18 +0100 From: Gerhard Sittig To: freebsd-mobile@freebsd.org Subject: Re: Updating FreeBSD (was: Bridging with 3C589D-COMBO on 4.2-RELEASE?) Message-ID: <20010315181318.Z20830@speedy.gsinet> Mail-Followup-To: freebsd-mobile@freebsd.org References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> <3AAF047F.341981B2@babbleon.org> <20010314194326.X20830@speedy.gsinet> <3AB037BB.EADF0432@babbleon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3AB037BB.EADF0432@babbleon.org>; from bts@babbleon.org on Wed, Mar 14, 2001 at 10:32:11PM -0500 Organization: System Defenestrators Inc. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 14, 2001 at 22:32 -0500, The Babbler wrote: > > I think I'm having a cultural/linguistic problem. > > In Linux, there is is a "stable" version and a "development" > version, but even the "stable" version is less stable than the > released version if you catch it between releases. That's not the whole truth (as I understand it, but yes I've been running Linux since '92). What you call the "stable" and "devel" version above seems to be the kernel only! Looking at the Documentation/ directory and especially the Changes file there's a whole lot of userland tools the *user/admin* has to keep in sync when upgrading. And it's quite easy to get the dependencies wrong and render your system unusable by doing things in the wrong order. That's when distributions come into play doing all of this for the user. But the next problem is that there's so many of them and graticious(id?) differences make work a hell unnecessarily. > I'm starting to "get it" that this is not the case with > FreeBSD, so I'll check the FreeBSD handbook and find out how to > upgrade in the middle of a release cycle and and see if that > clears up some of the trouble . . . The difference between Linux and FreeBSD in this respect is that tracking -STABLE provides you with much an easier way of getting a complete suite of software fitting perfectly together. Under the assumption that you read and follow UPDATING and scan the -stable mailing list for "HEADS UP" notices. The base system is one fine tuned collection of the kernel and essential tools plus basic services, while the ports system mostly brings independent apps for your comfort and pleasure. IMO it's less troublesome to upgrade in FreeBSD land. How to do it is described in the online doc on your disk and on the project servers as well as discussed on an almost regular basis in the list (about once a month) ... I recommend you read the Handbook chapters on how to track -STABLE and use the release of 4.3 to get up to date. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 12:35:45 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from imo-m06.mx.aol.com (imo-m06.mx.aol.com [64.12.136.161]) by hub.freebsd.org (Postfix) with ESMTP id D21CE37B719; Thu, 15 Mar 2001 12:35:28 -0800 (PST) (envelope-from Xeon2578@netscape.net) Received: from Xeon2578@netscape.net by imo-m06.mx.aol.com (mail_out_v29.5.) id e.2.10f01e7 (16226); Thu, 15 Mar 2001 15:35:17 -0500 (EST) Received: from netscape.com (aimmail02.aim.aol.com [205.188.144.194]) by air-in02.mx.aol.com (v77_r1.21) with ESMTP; Thu, 15 Mar 2001 15:35:17 -0500 Date: Thu, 15 Mar 2001 15:34:28 -0500 From: Xeon2578@netscape.net To: bts@babbleon.org Cc: Xeon2578@netscape.net, freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: BSD with two NIC's Mime-Version: 1.0 Message-ID: <35F74CD0.46D5FE7A.00877270@netscape.net> References: <21662211.7E01A45E.00877270@netscape.net> <3AAEF70C.DFFCFCCC@babbleon.org> <0A3465D9.5B1A3086.00877270@netscape.net> <3AAF6F9D.5A3810D8@babbleon.org> <46CED77F.23FFB834.00877270@netscape.net> <3AB033EC.191F47A0@babbleon.org> X-Mailer: Franklin Webmailer 1.0 Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi - I rebuilt the Kernel accordingly....but my situation has not changed. I keep getting the device time when I issue the "ifconfig .." I tried a Linksys PCMPC200 V2, but it seems its not supported... although I nooticed the PCMPC100 is!!! Any more Ideas..I wouldn't want to give up so soon!! ????? The Babbler wrote: > > > Immediate device timeouts are usually indicative of IRQ conflicts. > > But there is another problem (and it might even be the same problem, or > the original problem); namely, FreeBSD ships with an (IMHO) broken > kernel config; at any rate, one that doesn't work with PCMCIA cards. > > Find the line that looks like this: > > device      ed0 at isa? port 0x280 irq 10 iomem 0xd8000 > > and change it to just this: > > device      ed > > and rebuild your kernel. > > If that doesn't do it, then you probably have an IRQ conflict; you did > the "dmesg | grep irq" thing already, right? > > > Xeon2578@netscape.net wrote: > > > > Thank you very much. Like you said After twicking with the pccard.conf file, i got pccardd > > enable the cards: > > > > irq 3 13 > > > > config 0x2 "ed0" 3 > > config 0x3 "ed1" 13 > > > > I configured each interface with a different IP Address(different subnets) > > but immediately after the ifconfig command I get a message > > /kernel: ed0: device timeout for  ed0 > > and /kernel: ed1: device timeout for ed1 > > Besides each interface can ping itself on the respective IP. > > But I can't ping other hosts on respective subnets... > > > > Any Idea...DriverS?? > > > > The Babbler wrote: > > > > > > > > > Sorry, I was confused anyway.  That question is irrelavent. > > > > > > What you need to try is to edit your /etc/pccard.conf file. > > > Copy the entries for those two cards from the /etc/defaults/pccard.conf > > > file, > > > and change one of the entries to use a different interrupt and entry > > > number; eg, > > > if the first card is in the defaults file with > > > > > >   config 0x1 "ed" ? > > > > > > then try making it look like > > > > > >    config 0x2 "ed" 9 > > > > > > instead. > > > > > > (Actually, what you need to do is to do > > > > > >     dmesg | grep irq > > > > > > and see what irqs are free so you can assign one of those.  Nine happens > > > to be what worked for me.) > > > > > > Then you just have to play around with it until it works.  Of course, > > > you have to restart the pccardd every time you change these. > > > > > > You might be able to get this all easier by using "pccardc enabler" > > > until you find workable parameters rather than messing with pccard.conf > > > right off the bat, but I didn't personally stumble across pccardc > > > enabler 'til after I had might working. > > > > > > PS:  Mine only had an IRQ conflict.  It's possible that yours will solve > > > the memory conflict itself if you fix the IRQ conflict.  After all was > > > said & done, mine actually was fixed by putting just this in the > > > pccard.conf: > > > > > > irq 3 9 > > > > > > > > > It's possible that this is all you need--to explicitly list the > > > non-conflicting IRQs in your system. > > > > > > > > > > > > > > > Xeon2578@netscape.net wrote: > > > > > > > > The Babbler wrote: > > > > > > > > > > Xeon2578@netscape.net wrote: > > > > > > > > > > > > Hi - > > > > > > > > > > > > I was so relievd when I saw your posting on: > > > > > > "PCMCIA Questions: 2 NICs & new pccard.conf entry" > > > > > > Unfortunately, there were no followups...I am hoping you > > > > > > got a solution for your problem, cause I have the same too. > > > > > > > > > > > > I have two different PCMCIA network cards installed on a SONY(fx101) Laptop > > > > > > 1. Netgear FA410TX > > > > > > 2. D-Link 650 > > > > > > These cards appear to use the exact same resources, > > > > > > IRQ 3 and I/O 0x240-0x25F > > > > > > The cards are seen by PCCARDD, but either will load but not both. > > > > > > If one load, the other produces an error message: > > > > > > No free configuration for card "card_name" > > > > > > > > > > > > > > > Are both cards using the same driver (eg, both "ed" or "ep" or > > > > > whatever)? > > > > > > > > > > > > > Well yes, they use ed. > > > > > > > > MAT > > > > > > > > __________________________________________________________________ > > > > Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ > > > > > > -- > > > "Brian, the man from babble-on"              bts@babbleon.org > > > Brian T. Schellenberger                      http://www.babbleon.org > > > Support http://www.eff.org.                  Support decss defendents. > > > Support http://www.programming-freedom.org.  Boycott amazon.com. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > __________________________________________________________________ > > Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ > > -- > "Brian, the man from babble-on"              bts@babbleon.org > Brian T. Schellenberger                      http://www.babbleon.org > Support http://www.eff.org.                  Support decss defendents. > Support http://www.programming-freedom.org.  Boycott amazon.com. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > __________________________________________________________________ Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 13:46:37 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 0B0E637B719; Thu, 15 Mar 2001 13:46:28 -0800 (PST) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f2FLkE516737; Thu, 15 Mar 2001 13:46:14 -0800 (PST) Message-ID: <3AB13826.4D85FC40@isi.edu> Date: Thu, 15 Mar 2001 13:46:14 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Xeon2578@netscape.net Cc: bts@babbleon.org, freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: BSD with two NIC's References: <21662211.7E01A45E.00877270@netscape.net> <3AAEF70C.DFFCFCCC@babbleon.org> <0A3465D9.5B1A3086.00877270@netscape.net> <3AAF6F9D.5A3810D8@babbleon.org> <46CED77F.23FFB834.00877270@netscape.net> <3AB033EC.191F47A0@babbleon.org> <35F74CD0.46D5FE7A.00877270@netscape.net> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms7EF46D6E0818B0D90E6397BB" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a cryptographically signed message in MIME format. --------------ms7EF46D6E0818B0D90E6397BB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Xeon2578@netscape.net wrote: > I tried a Linksys PCMPC200 V2, but it seems its not supported... That's a Cardbus card. > although I nooticed the PCMPC100 is!!! This isn't. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms7EF46D6E0818B0D90E6397BB Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDMxNTIxNDYxNFowIwYJKoZIhvcNAQkEMRYE FC8uYXyUCcQMuPLvycdIejU/S8I2MFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAqetsycKPy04UkG2koVdESY7U5VTBGGpSqTrQb0Pk9JXd3U/jo4fX U+OG33Ou42ccsI6Nc4lg8+os6IZFmh2WXTwWFuOUzwrcGPhgsFAm673lhMSJCDpyY4W3h++9 uTEMgTmwMTRQOyX21rM0TVa4pwZJsDeHoxreigFNiS+Pxmc= --------------ms7EF46D6E0818B0D90E6397BB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 13:53:20 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 4461C37B719; Thu, 15 Mar 2001 13:53:13 -0800 (PST) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f2FLrA518099; Thu, 15 Mar 2001 13:53:10 -0800 (PST) Message-ID: <3AB139C6.36D8B4F0@isi.edu> Date: Thu, 15 Mar 2001 13:53:10 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Xeon2578@netscape.net Cc: bts@babbleon.org, freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: BSD with two NIC's References: <21662211.7E01A45E.00877270@netscape.net> <3AAEF70C.DFFCFCCC@babbleon.org> <0A3465D9.5B1A3086.00877270@netscape.net> <3AAF6F9D.5A3810D8@babbleon.org> <46CED77F.23FFB834.00877270@netscape.net> <3AB033EC.191F47A0@babbleon.org> <35F74CD0.46D5FE7A.00877270@netscape.net> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msD5220D44203DC837B6C30179" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a cryptographically signed message in MIME format. --------------msD5220D44203DC837B6C30179 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Xeon2578@netscape.net wrote: > irq 3 13 > config 0x2 "ed0" 3 > config 0x3 "ed1" 13 Are these IRQs really free? What do "vmstat -i" and "dmesg | grep irq" say? Does either card work on its own (i.e. with the other removed)? Do other cards work - i.e. are the pcic setting correct? > I configured each interface with a different IP Address(different subnets) > but immediately after the ifconfig command I get a message > /kernel: ed0: device timeout for ed0 > and /kernel: ed1: device timeout for ed1 > Besides each interface can ping itself on the respective IP. That's because pings for local addresses go over loopback (see "netstat -r"). Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------msD5220D44203DC837B6C30179 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDMxNTIxNTMxMFowIwYJKoZIhvcNAQkEMRYE FLIdLirVx6Iu++OlhI9eIZ5b4O0UMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAKIaOXcJqiNN3y8zokW77Bf5V+CeCmHBMWkAULyG8kJ/F3ywfJg1b xk+rGK7tkObnvZxaxLna6ECrVOjcdNfWw+XfChLgnYjquUjJzIuI+FMx5h13zIGiOkOWRMMF 4QmarMGfTJT9u2ROprTfALxrB2xSYprxla8PI8U9hMplt18= --------------msD5220D44203DC837B6C30179-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 14:16:13 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 6566637B719; Thu, 15 Mar 2001 14:16:08 -0800 (PST) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f2FMFFs03674; Thu, 15 Mar 2001 14:15:15 -0800 (PST) Message-Id: <200103152215.f2FMFFs03674@ptavv.es.net> To: Cy Schubert - ITSD Open Systems Group Cc: David Kelly , Pete French , mobile@FreeBSD.ORG, sos@freebsd.dk, stable@FreeBSD.ORG Subject: Re: Disk I/O problem in 4.3-BETA In-reply-to: Your message of "Thu, 15 Mar 2001 11:49:29 PST." <200103151949.f2FJnVF13620@cwsys.cwsent.com> Date: Thu, 15 Mar 2001 14:15:15 -0800 From: "Kevin Oberman" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Cy Schubert - ITSD Open Systems Group > Date: Thu, 15 Mar 2001 11:49:29 -0800 > Sender: owner-freebsd-mobile@FreeBSD.ORG > > This is one of the three big reasons we (at our shop) are migrating our > infrastructure servers (kerberos, console, file, web, firewall/proxy, > etc.) from Linux to FreeBSD. As Linux (specifically RedHat) comes with > more toys, bells and whistles, Linux will remain our desktop standard, > not to mention the sure-to-be-lost political battle. With the arrival of Darwin, I would not be quite sure about the political battle. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 14:17: 8 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 90D3137B718 for ; Thu, 15 Mar 2001 14:17:05 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f2FMH5303658 for freebsd-mobile@freebsd.org; Thu, 15 Mar 2001 14:17:05 -0800 Date: Thu, 15 Mar 2001 14:17:05 -0800 From: Brooks Davis To: freebsd-mobile@freebsd.org Subject: ifconfig your wireless card Message-ID: <20010315141705.A2184@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'd like to draw your attention to some patches I've created which provide a consistent interface to configuring 802.11 wireless cards via ifconfig. Currently, wi and an cards are supported, but the interface is designed to be general is with some minor work support for awi and ray cards could be added. Patches for current are available at: http://www.one-eyed-alien.net/~brooks/FreeBSD/ifconfig.diff Patches against stable are at: http://www.one-eyed-alien.net/~brooks/FreeBSD/ifconfig.diff-stable The userland interfaces are based on those in BSD/OS (5.0 I think), but are slightly different. Compatibility with both BSD/OS and NetBSD is provided in ifconfig. The new kernel interfaces are inspired by Bill Paul's interfaces to the wi and an drivers. Media support is almost entirely taken from NetBSD. Comments and suggestions appreciated. -- Brooks P.S. I can't get my Cisco card to work with crypto under STABLE with or without my patches, so while they should work, I can't say for sure. It works perfectly under CURRENT. --=20 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 --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6sT9gXY6L6fI4GtQRAgkAAKCNv4FVtwXlDgcbaOQyeyDk/rjXYQCfQBnl 0lkz3WjQgzNZxJ0i1B9QE40= =tsT/ -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 15: 4:59 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from amleth.demon.co.uk (amleth.demon.co.uk [158.152.198.225]) by hub.freebsd.org (Postfix) with SMTP id 9681C37B71C for ; Thu, 15 Mar 2001 15:04:49 -0800 (PST) (envelope-from PEB@amleth.demon.co.uk) Date: Thu, 15 Mar 2001 09:10:24 GMT From: PEB@amleth.demon.co.uk (Paul E. Bennett) Reply-To: peb@amleth.demon.co.uk Message-Id: <6679@amleth.demon.co.uk> To: freebsd-mobile@FreeBSD.org Subject: Re: Tosh 2595XDVD -- fan control? X-Mailer: PCElm 1.10 Lines: 33 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20010314130521.A45519@greycat.com> Dann Lunsford writes: > WOW! This is *very* cool; thanks a LOT! Will go over this carefully > later on. Where there other Tosh hardware utils at the same place? > And where did you find this (yeah, I'm enthused about this :-)). > I wish Toshiba and other HUBGA companies would release more detailed > hardware programming material; I still remember building S-100 boards > with a great deal of pleasure. *sigh* Sadly, many hardware manufacturers these days are limiting the amount of information they publish. I have spent ages scouring web-sites, chasing links that don't work and trying to email companies that seem to not have a "postmaster@xxx.yyy", "webmaster@xxx.yyy" or similar general address where mail to the correct domain will automatically be routed (my own "*any*@amleth.demon.co.uk" addresses will come to me if it isn't taken by other valid email addresses). The reasons that the information is so lacking these days is the view, by manufacturers, that everybody will run M$ Windows and they provide the drivers accordingly. As these are never open source other OS proponents are left in the cold. I am continuing to press my suppliers and manufacturers for better information whenever I can get it. -- ******************************************************************** Paul E. Bennett .................... Forth based HIDECS Consultancy ..... Mob: +44 (0)7811-639972 .........NOW AVAILABLE:- HIDECS COURSE...... Tel: +44 (0)1235-814586 .... see http://www.feabhas.com for details. Going Forth Safely ..... EBA. www.electric-boat-association.org.uk.. ******************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 16:15: 4 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from Mail6.nc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id BF5D537B719 for ; Thu, 15 Mar 2001 16:14:57 -0800 (PST) (envelope-from bts@babbleon.org) Received: from babbleon.org ([66.26.250.181]) by Mail6.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Thu, 15 Mar 2001 19:14:51 -0500 Message-ID: <3AB15AE1.5F37390C@babbleon.org> Date: Thu, 15 Mar 2001 19:14:26 -0500 From: The Babbler Organization: None to speak of X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nate Williams , mobile@freebsd.org Subject: Babbleon the idiot / status (was: Bridging with 3C589D-COMBO on 4.2-RELEASE?) References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <20010312174852.T20830@speedy.gsinet> <3AAF06E8.103042C6@babbleon.org> <15023.44543.137285.702518@nomad.yogotech.com> <3AB036DB.3CE7E3C3@babbleon.org> <15025.897.571649.16251@nomad.yogotech.com> <3AB11C3B.7578E134@babbleon.org> <15025.7561.937102.558775@nomad.yogotech.com> <3AB12177.6DA79EF1@babbleon.org> <15025.8842.184792.656585@nomad.yogotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org NON-TECHNICAL STUFF: Ok, first, let me say that most of y'all have the patience of saints. I was getting out of line with the tone of my posts, and WAY out of line with the volume. I posted a straightforward "is this normal" question; the answer was no. That should have been that. One poster took a tone that I found condesending and I started lashing out at everybody. I'm not sure if my interpretation of his posts as condesending was fair to him in the first place, though I find few things quite as annoying as telling somebody that something's wrong and hearing "no, it's fine." But it was CERTAINLY unfair to everybody else. I came across as an idiot who was unwilling to learn anything new, and a pro-Linux advocate. I like to think that I'm neither; indeed, I like almost everything else about FreeBSD better, but the area of PCMCIA/network support has given me trouble. I actually ran FreeBSD back in 1996ish but switched to Linux because of the (at the time unquestionably) superior (as in, extant) PCMCIA support. I expected to have some trouble with this area and that probably colored the way I've seen it. This also makes me an A-1 hypocrite since a major reason I wanted to switch was that I was finding modern Linux distributions (like Mandrake) too automatic. Indeed, with FreeBSD I was able to fairly easily get Windows machines to print via Samba to my printer, a task which had eluded me for months under Linux. The reason I could do that under FreeBSD is because I controlled all the scripts & parameters so I could figure out where the process was breaking down and fix it. Yet here I am complaining over much the same thing w/r/t PCMCIA. Sheesh. Finally, another confession: I didn't actually use *this* network card under Linux. Thus, my comments about relative stability are bogus anyway; maybe the card is problematic for any operating system, for all the more I know. I got this card (3com 3c589D) specifically for FreeBSD after giving up on getting my Linux card working under FreeBSD at all (see J. Rodrigo Refandez M.'s post of 22 January 2001 in this list if you are interested in the details of *that*). I'm using the same card in my other machine, for much the same reason--I was never able to get things properly configured with the exact same cards I used under Linux and this card "seemed" to work better under FreeBSD (and was recommended to me by Brian Dean, my local FreeBSD guru). My guess is that the double-file-loss on crash was coincidence and/or a korganizer bug (it perhaps re-writes the config file every time it starts up, though why it should do such a thing eludes me). I'm not really interested in investigating that one unless it happens again. Three times starts to stetch my ability to explain away things as coincidence. Anyway, I apologize and I hope I can sort of "start over" on the right foot. TECHNICAL STUFF: I'm in the process of upgrading my kernel to -STABLE from -RELEASE, building in debugging, diagnostic, and ddb code, and double-checking my IRQs. I'm having trouble getting the STABLE kernel built, which certainly argues in favor of the thesis that I no longer have any functioning brain cells. However, I'm bugging the poor folks on the freebsd-stable list about that so most of you can take a break in that regard. If I get any information from the kernel debugging I've enabled, I'll post the information back here. IRQ: Guess what! Sure enough, it looks like I have two IRQ conflicts after all. I really *thought* I'd checked this long ago, but I guess I checked these on my other computer and not on this one . . . and one of the conflicts is with the PCMCIA card, sho' nuff. I could swear that I'd checked this long ago, but I now suspect that I'd checked it only on my *other* computer. In practice, I hadn't had any trouble with the 3com card on this computer. The crashes I've had on this computer have involved changes to the bridges and firewall code. Changes which I never even thought to connect with the PCMCIA itself until this thread started. They are with devices I never use, but perhaps they generate interrupts sometimes anyway. IRQ 3: Used by sio1 and the ep0 PCMCIA card. This one might explain a lot. IRQ 5: Used by the USB controller and the sound card. I don't ever use USB devices, and I don't even have usb support built into the kernel. Is this a potential problem anyway, or is it harmless? As for IRQ 3, I've now set up pccard.conf to use IRQ 9 (which is unused) and we'll see what that does for the state of my system. BUT: Still, when all is said & done I find it odd that changing bridge/firewall settting might possibly crash the computer, even if the hardware ethernet settings are silly, when this never happens without bridging or firewalling set. I mean, I'll change it in the hopes that things will be better, but does it make sense as a possible explanation? Nate Williams wrote: > > > > > Do you mean that popping them out might cost reliability, or that the > > > > Linux code that tolerates them better itself makes Linux less reliable? > > > > > > Ahh, the light-bulb is starting to come on now. :) > > > > > > As an example of this kind of behavior, what happens when you pop out a > > > CF memory card or an ATA hard-disk in the middle of writing data to it? > > > > > > Something very bad has happened, because the data has not been > > > completely written to the disk. > > > > Well, yes, of course. And if an ethernet card is in the middle of > > writing packets back things could happen there, too. But if it's > > quiesent and there aren't NFS mounts going across it or anything I > > wouldn't expect to have to run explicit commands. > > You got it. That's why I said it's impossible to do 100% reliability. > However, you can get pretty darn close, and I do hot-swap with my cards > running FreeBSD. (I'm the author of the hot-swap code in FreeBSD, which > was written over 2 years ago, ). > > Minimizing the window of vulnerability is *hard*, but possible. With > all the changes that came about in recent FreeBSD kernels, the window is > bigger. Probably no bigger than in Linux, but certainly bigger than I > was comfortable with. > > In any case, even if the kernel crashes, it should rarely (if ever) > corrupt your hard-disk, unless there is a misconfiguration. > > Nate -- "Brian, the man from babble-on" bts@babbleon.org Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 16:32:43 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 783CB37B719 for ; Thu, 15 Mar 2001 16:32:42 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2G0WYk23510; Thu, 15 Mar 2001 16:32:34 -0800 (PST) Date: Thu, 15 Mar 2001 16:32:34 -0800 From: Alfred Perlstein To: The Babbler Cc: Nate Williams , mobile@FreeBSD.ORG Subject: Re: Babbleon the idiot / status (was: Bridging with 3C589D-COMBO on 4.2-RELEASE?) Message-ID: <20010315163234.I29888@fw.wintelcom.net> References: <20010312174852.T20830@speedy.gsinet> <3AAF06E8.103042C6@babbleon.org> <15023.44543.137285.702518@nomad.yogotech.com> <3AB036DB.3CE7E3C3@babbleon.org> <15025.897.571649.16251@nomad.yogotech.com> <3AB11C3B.7578E134@babbleon.org> <15025.7561.937102.558775@nomad.yogotech.com> <3AB12177.6DA79EF1@babbleon.org> <15025.8842.184792.656585@nomad.yogotech.com> <3AB15AE1.5F37390C@babbleon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AB15AE1.5F37390C@babbleon.org>; from bts@babbleon.org on Thu, Mar 15, 2001 at 07:14:26PM -0500 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * The Babbler [010315 16:15] wrote: > dude, get a USB ethernet, the suck for performance but are quite usable. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 16:38:51 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 7190237B719 for ; Thu, 15 Mar 2001 16:38:47 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f2G0cjD20563; Thu, 15 Mar 2001 16:38:45 -0800 Date: Thu, 15 Mar 2001 16:38:45 -0800 From: Brooks Davis To: The Babbler Cc: mobile@FreeBSD.ORG Subject: Re: Babbleon the idiot / status (was: Bridging with 3C589D-COMBO on 4.2-RELEASE?) Message-ID: <20010315163845.A15949@Odin.AC.HMC.Edu> References: <20010312174852.T20830@speedy.gsinet> <3AAF06E8.103042C6@babbleon.org> <15023.44543.137285.702518@nomad.yogotech.com> <3AB036DB.3CE7E3C3@babbleon.org> <15025.897.571649.16251@nomad.yogotech.com> <3AB11C3B.7578E134@babbleon.org> <15025.7561.937102.558775@nomad.yogotech.com> <3AB12177.6DA79EF1@babbleon.org> <15025.8842.184792.656585@nomad.yogotech.com> <3AB15AE1.5F37390C@babbleon.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3AB15AE1.5F37390C@babbleon.org>; from bts@babbleon.org on Thu, Mar 15, 2001 at 07:14:26PM -0500 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 15, 2001 at 07:14:26PM -0500, The Babbler wrote: > TECHNICAL STUFF: > I'm in the process of upgrading my kernel to -STABLE from -RELEASE, > building in debugging, diagnostic, and ddb code, and double-checking my > IRQs. I'm having trouble getting the STABLE kernel built, which > certainly argues in favor of the thesis that I no longer have any > functioning brain cells. However, I'm bugging the poor folks on the > freebsd-stable list about that so most of you can take a break in that > regard. If I get any information from the kernel debugging I've > enabled, I'll post the information back here. Just a recommendation, since you've obviously never done the whole upgrade before, I recommend using a GENERIC kernel to start with unless there are serious problems with that (you're system crashes on probe of some device, etc.) The reason for this is that there are a number of simple little gotchas in kernel configuration the get even experienced people if they aren't paying quite enough attention and so it's much easier to just use GENERIC at first. Later you can move on to a custom kernel. > They are with devices I never use, but perhaps they generate interrupts > sometimes anyway.=20 >=20 > IRQ 3: Used by sio1 and the ep0 PCMCIA card. This one might explain a > lot. This is bad. Both of those are more or less ISA devices and ISA can't share interupts (with minor, irrelavent exceptions). > IRQ 5: Used by the USB controller and the sound card. This is likely harmless since pretty much all USB and sound devices are PCI these days. > I don't ever use USB devices, and I don't even have usb support built > into the kernel. Is this a potential problem anyway, or is it harmless? Not having the device in the kernel is probably harmless. Personaly once everything else works, I'd take a shot at getting USB working just for kicks. You can test it with a cheap ass mouse or something. > As for IRQ 3, I've now set up pccard.conf to use IRQ 9 (which is unused) > and we'll see what that does for the state of my system. That's likely to fix the problem or at least help a lot. > Still, when all is said & done I find it odd that changing > bridge/firewall settting might possibly crash the computer, even if the > hardware ethernet settings are silly, when this never happens without > bridging or firewalling set. I mean, I'll change it in the hopes that > things will be better, but does it make sense as a possible explanation? I suspect the IRQ problem wasn't the cause here, but you really never know. Enabling bridging does poke the ethernet hardware slightly (when enabling promiscuous mode) so that could actually be the problem. There definatly have been problems with bridging that have been fixed between now and the 4.2 release so there's a good chance that an upgrade will make them go away. As I think I mentioned before, bridging just isn't used by most people. VMWare is making is much more popular and it should become much more solid then before. -- Brooks --=20 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 --3MwIy2ne0vdjdPXF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6sWCUXY6L6fI4GtQRAoB8AJwN1Ij76Z4ySn9yghA+51ezmdaktwCdHt6+ zPM6M50PSHKzriwvkkwEAzA= =60fz -----END PGP SIGNATURE----- --3MwIy2ne0vdjdPXF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 19:16: 7 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 7B12437B719 for ; Thu, 15 Mar 2001 19:16:05 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f2G3ETH85377; Thu, 15 Mar 2001 19:14:29 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: bts@babbleon.org Cc: nate@yogotech.com, mobile@FreeBSD.ORG Subject: Re: Babbleon the idiot / status (was: Bridging with 3C589D-COMBO on 4.2-RELEASE?) In-Reply-To: <3AB15AE1.5F37390C@babbleon.org> References: <3AB12177.6DA79EF1@babbleon.org> <15025.8842.184792.656585@nomad.yogotech.com> <3AB15AE1.5F37390C@babbleon.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010315191428I.jkh@osd.bsdi.com> Date: Thu, 15 Mar 2001 19:14:28 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 6 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As someone who was also offended by the tone of your posts but chose not to say anything, let me just applaud your willingness to "come clean" here and try for a fresh start. If only more people did that when necessary. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Mar 15 23:58:25 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7F73437B719; Thu, 15 Mar 2001 23:58:21 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2G7w8928955; Fri, 16 Mar 2001 00:58:08 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103160758.f2G7w8928955@harmony.village.org> To: Lars Eggert Subject: Re: BSD with two NIC's Cc: Xeon2578@netscape.net, bts@babbleon.org, freebsd-questions@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 15 Mar 2001 13:53:10 PST." <3AB139C6.36D8B4F0@isi.edu> References: <3AB139C6.36D8B4F0@isi.edu> <21662211.7E01A45E.00877270@netscape.net> <3AAEF70C.DFFCFCCC@babbleon.org> <0A3465D9.5B1A3086.00877270@netscape.net> <3AAF6F9D.5A3810D8@babbleon.org> <46CED77F.23FFB834.00877270@netscape.net> <3AB033EC.191F47A0@babbleon.org> <35F74CD0.46D5FE7A.00877270@netscape.net> Date: Fri, 16 Mar 2001 00:58:08 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <3AB139C6.36D8B4F0@isi.edu> Lars Eggert writes: : This is a cryptographically signed message in MIME format. : : --------------msD5220D44203DC837B6C30179 : Content-Type: text/plain; charset=us-ascii : Content-Transfer-Encoding: 7bit : : Xeon2578@netscape.net wrote: : > irq 3 13 : > config 0x2 "ed0" 3 : > config 0x3 "ed1" 13 : : Are these IRQs really free? What do "vmstat -i" and "dmesg | grep irq" say? irq 13 is not an available interrupt. I really should put enforcement of that into pccard/pcic. After reading enough data sheets, I can tell you that irq 1, 2, 8, 13 and usually 6 are listed as reserved in the datasheets. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 0: 0:46 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7555D37B719 for ; Fri, 16 Mar 2001 00:00:43 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2G80e929001; Fri, 16 Mar 2001 01:00:40 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103160800.f2G80e929001@harmony.village.org> To: Brooks Davis Subject: Re: ifconfig your wireless card Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 15 Mar 2001 14:17:05 PST." <20010315141705.A2184@Odin.AC.HMC.Edu> References: <20010315141705.A2184@Odin.AC.HMC.Edu> Date: Fri, 16 Mar 2001 01:00:40 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20010315141705.A2184@Odin.AC.HMC.Edu> Brooks Davis writes: : Currently, wi and an cards are supported, but the interface is designed : to be general is with some minor work support for awi and ray cards : could be added. I have my awi card back in action. What changes would be needed for it? Also, I have cnwctl in the wings right now that I'd like to not commit if ifconfig could be made to work :-). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 2:16:19 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from bumper.jellybaby.net (bumper.jellybaby.net [194.159.247.1]) by hub.freebsd.org (Postfix) with ESMTP id 4BA4437B718 for ; Fri, 16 Mar 2001 02:16:17 -0800 (PST) (envelope-from simond@bumper.jellybaby.net) Received: (from simond@localhost) by bumper.jellybaby.net (8.9.2/8.9.2) id KAA37288; Fri, 16 Mar 2001 10:16:05 GMT (envelope-from simond) Date: Fri, 16 Mar 2001 10:16:05 +0000 From: simond@irrelevant.org To: Alfred Perlstein Cc: The Babbler , Nate Williams , mobile@FreeBSD.ORG Subject: Re: Babbleon the idiot / status (was: Bridging with 3C589D-COMBO on 4.2-RELEASE?) Message-ID: <20010316101605.B36288@irrelevant.org> References: <3AAF06E8.103042C6@babbleon.org> <15023.44543.137285.702518@nomad.yogotech.com> <3AB036DB.3CE7E3C3@babbleon.org> <15025.897.571649.16251@nomad.yogotech.com> <3AB11C3B.7578E134@babbleon.org> <15025.7561.937102.558775@nomad.yogotech.com> <3AB12177.6DA79EF1@babbleon.org> <15025.8842.184792.656585@nomad.yogotech.com> <3AB15AE1.5F37390C@babbleon.org> <20010315163234.I29888@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010315163234.I29888@fw.wintelcom.net>; from bright@wintelcom.net on Thu, Mar 15, 2001 at 04:32:34PM -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 15, 2001 at 04:32:34PM -0800, Alfred Perlstein wrote: > * The Babbler [010315 16:15] wrote: > > > > dude, get a USB ethernet, the suck for performance but are > quite usable. :) Assuming you get one that works :) -- Simon Dick simond@irrelevant.org "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 2:26: 3 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ix.rain.fr (ix.rain.fr [194.51.3.175]) by hub.freebsd.org (Postfix) with ESMTP id 8DF5037B719 for ; Fri, 16 Mar 2001 02:25:59 -0800 (PST) (envelope-from tfischer@rain.fr) Received: from rain.fr (localhost [127.0.0.1]) by ix.rain.fr (8.11.1/8.11.1) with ESMTP id f2GAPNb74075 for ; Fri, 16 Mar 2001 11:25:23 +0100 (CET) (envelope-from tfischer@rain.fr) Message-ID: <3AB1EA12.1CA95936@rain.fr> Date: Fri, 16 Mar 2001 11:25:22 +0100 From: Tom Fischer Organization: France Telecom Transpac X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@FreeBSD.ORG Subject: Re: Tosh 2595XDVD -- fan control? References: <6679@amleth.demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Sorry to take up space on everyone's disk, but can someone send me this fan control program? I'd like to try it out on my Toshiba Tecra 8100, and I stupidly deleted the original mail with the program from my mailbox. Thanks in advance! tom tfischer@rain.fr "Paul E. Bennett" wrote: > > In message <20010314130521.A45519@greycat.com> Dann Lunsford writes: > > > WOW! This is *very* cool; thanks a LOT! Will go over this carefully > > later on. Where there other Tosh hardware utils at the same place? > > And where did you find this (yeah, I'm enthused about this :-)). > > I wish Toshiba and other HUBGA companies would release more detailed > > hardware programming material; I still remember building S-100 boards > > with a great deal of pleasure. *sigh* > > Sadly, many hardware manufacturers these days are limiting the amount > of information they publish. I have spent ages scouring web-sites, > chasing links that don't work and trying to email companies that seem > to not have a "postmaster@xxx.yyy", "webmaster@xxx.yyy" or similar > general address where mail to the correct domain will automatically > be routed (my own "*any*@amleth.demon.co.uk" addresses will come to > me if it isn't taken by other valid email addresses). > > The reasons that the information is so lacking these days is the view, > by manufacturers, that everybody will run M$ Windows and they provide > the drivers accordingly. As these are never open source other OS > proponents are left in the cold. > > I am continuing to press my suppliers and manufacturers for better > information whenever I can get it. > > -- > ******************************************************************** > Paul E. Bennett .................... > Forth based HIDECS Consultancy ..... > Mob: +44 (0)7811-639972 .........NOW AVAILABLE:- HIDECS COURSE...... > Tel: +44 (0)1235-814586 .... see http://www.feabhas.com for details. > Going Forth Safely ..... EBA. www.electric-boat-association.org.uk.. > ******************************************************************** > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 7:15: 5 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from imo-m03.mx.aol.com (imo-m03.mx.aol.com [64.12.136.6]) by hub.freebsd.org (Postfix) with ESMTP id D58CC37B71A for ; Fri, 16 Mar 2001 07:15:00 -0800 (PST) (envelope-from Xeon2578@netscape.net) Received: from Xeon2578@netscape.net by imo-m03.mx.aol.com (mail_out_v29.5.) id n.ec.1153993 (16231); Fri, 16 Mar 2001 10:14:01 -0500 (EST) Received: from netscape.com (aimmail01.aim.aol.com [205.188.144.193]) by air-in02.mx.aol.com (v77_r1.21) with ESMTP; Fri, 16 Mar 2001 10:14:01 1900 Date: Fri, 16 Mar 2001 10:13:13 -0500 From: Xeon2578@netscape.net To: Xeon2578@netscape.net Cc: freebsd-mobile@freebsd.org Subject: 2 NIC's on LAPTOP Mime-Version: 1.0 Message-ID: <0366EE18.181ACD59.00877270@netscape.net> References: <7F3371DC.0DCA8C96.00877270@netscape.net> <3AB22DD5.96960888@pacbell.net> <67381BD4.38922E65.00877270@netscape.net> X-Mailer: Franklin Webmailer 1.0 Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I got the cards seen by pccardd..but whenevr I issue the ifconfig command on  either, i get Device edx: device time out.... > > richard childers wrote: > > > > Solutions that come to mind: > > > > (1)    Get a new PCMCIA card made by another vendor. > > > > (2)    Edit /etc/defaults/pccard.conf and give one of the cards a new set of properties. > > > > See the man page for pccardc(8) and pccardd(8) for additional inbformation on how PCMCIA cards work. > > > > > > Hope this helps !! > > > > > > -- richard > > > > > > > > Xeon2578@netscape.net wrote: > > > > > Greetings, > > > > > >  I searched the FreeBSD list archives, etc for this issue and turned up with a few hits, but no solid answers, so I thought that I would pose the > > > question here - > > > > > > I have two different PCMCIA network cards installed on a > > > SONY(PCG-fx101) Laptop > > > 1. Netgear FA410TX > > > 2. D-Link 650 > > > These cards appear to use the exact same resources, > > > IRQ 3 and I/O 0x240-0x25F > > > The cards are seen by PCCARDD; either card will load but not both. > > > If one card is configured by pccardd, the other produces an error message: > > > No free configuration for card "its card_name" > > > > > > Please help, any references Please. > > > > > > Thank you. > > > Xeon2 > > > > > > __________________________________________________________________ > > > Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > > > -- > > Richard A. Childers > > Senor UNIX Administrator > > fscked@pacbell.net (email) > > 415.664.6291 (voice/msgs) > > > > # Providing administrative expertise (not 'damage control') since 1986. > > # PGP fingerprint: 7EFF 164A E878 7B04 8E9F  32B6 72C2 D8A2 582C 4AFA > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > __________________________________________________________________ > Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > __________________________________________________________________ Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 7:41: 4 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from hand.dotat.at (inch.demon.co.uk [194.222.223.128]) by hub.freebsd.org (Postfix) with ESMTP id 5B80337B719 for ; Fri, 16 Mar 2001 07:41:02 -0800 (PST) (envelope-from fanf@dotat.at) Received: from fanf by hand.dotat.at with local (Exim 3.20 #3) id 14dnWj-0000CS-00; Fri, 16 Mar 2001 06:15:53 +0000 Date: Fri, 16 Mar 2001 06:15:53 +0000 From: Tony Finch To: John Reynolds~ Cc: mobile@freebsd.org Subject: Re: Dell Latitude CPx J - good match for 4-STABLE? Message-ID: <20010316061553.G385@hand.dotat.at> References: <15023.61342.400884.548056@hip186.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15023.61342.400884.548056@hip186.ch.intel.com> Organization: Covalent Technologies, Inc Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Reynolds~ wrote: > >I've searched the archives for -questions, -mobile, and -stable and it appears >that most people are having reasonable success using FreeBSD with a Dell >Latitude CPx J laptop. Can anybody confirm that for me? On the whole it worjed fine for me, except for a BIOS bug that broke suspending within X. I put a wrapper around zzz to switch VCs away from X when the machine was suspended which solved the problem. It should have used `vidcontrol -s` but I wrote it in C due to ignorance. You might also be able to solve the problem by upgrading the BIOS. Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 8:10:20 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from imo-m10.mx.aol.com (imo-m10.mx.aol.com [64.12.136.165]) by hub.freebsd.org (Postfix) with ESMTP id BDEB437B718 for ; Fri, 16 Mar 2001 08:10:17 -0800 (PST) (envelope-from Xeon2578@netscape.net) Received: from Xeon2578@netscape.net by imo-m10.mx.aol.com (mail_out_v29.5.) id n.1b.11668c0 (16219) for ; Fri, 16 Mar 2001 11:09:44 -0500 (EST) Received: from netscape.com (aimmail01.aim.aol.com [205.188.144.193]) by air-in01.mx.aol.com (v77_r1.21) with ESMTP; Fri, 16 Mar 2001 11:09:44 -0500 Date: Fri, 16 Mar 2001 11:08:56 -0500 From: Xeon2578@netscape.net To: freebsd-mobile@freebsd.org Subject: USB IOMEGA ZIP 100 ON SONY LAPTOP!!! Mime-Version: 1.0 Message-ID: <0F3172CA.512EC5EC.00877270@netscape.net> X-Mailer: Franklin Webmailer 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings... I have a strange problem with my Iomega Zip 100 USB,I have installed it on a sony laptop PCG-FX101, which has two usb ports. I am running FreeBSD 4.0 I rebuilt my Kernel with USB Support: see below device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device umass # Disks/Mass storage - Requires scbus and da The LINT File specifically Identifies "device umass" as the one for IOMEGA ZIP 100 USB. with all this done, Every thing seems O.K. I then configured usbd according, started it and tested it by removing and inserting the USB Zip drive, the Kernel notices the Insertion and I dentfies the device as umass0: IOMEGA ZIP 100, when I remove it again it is noticed but with a message that says: "Woops! this will panic your system." "Detachment of drive is no supported currently." On rebootingwith Zip connected and Powered, every things works out fine, it is identified again as umass0: IOMEGA ZIP ........ but just before it starts mounting filesystems, It stops for a while and then returns a some output messages: Fault trap 12: Page fault while in kernel mode ----------- ---------- ----------- Panic: Page fault Rebooting in 15 seconds This goes on and on until I disconnect the ZIP drive, and then it boots normally. ANy Ideas? could it be some conflict with the IDE hard drive.??? __________________________________________________________________ Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 8:15:25 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from henny.webweaving.org (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id E7D2737B718 for ; Fri, 16 Mar 2001 08:15:20 -0800 (PST) (envelope-from n_hibma@FreeBSD.ORG) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id QAA61552; Fri, 16 Mar 2001 16:13:05 GMT (envelope-from n_hibma@FreeBSD.ORG) Date: Fri, 16 Mar 2001 16:13:05 +0000 (GMT) From: X-X-Sender: Reply-To: Nick Hibma To: Cc: Subject: Re: USB IOMEGA ZIP 100 ON SONY LAPTOP!!! In-Reply-To: <0F3172CA.512EC5EC.00877270@netscape.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Update to 4.x-STABLE. You have an out of date version of the driver. Nick > Greetings... > > > I have a strange problem with my Iomega Zip 100 USB,I have installed it on a sony laptop PCG-FX101, which has two usb ports. I am running FreeBSD 4.0 > > > I rebuilt my Kernel with USB Support: see below > > > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device usb # USB Bus (required) > device ugen # Generic > device uhid # "Human Interface Devices" > device umass # Disks/Mass storage - Requires scbus and da > > > The LINT File specifically Identifies "device umass" as the one for IOMEGA ZIP 100 USB. > with all this done, Every thing seems O.K. > I then configured usbd according, started it and tested it by removing and inserting the USB Zip drive, the Kernel notices the Insertion and I dentfies the device as umass0: IOMEGA ZIP 100, when I remove it again it is > noticed but with a message that says: > "Woops! this will panic your system." > "Detachment of drive is no supported currently." > On rebootingwith Zip connected and Powered, every things works out fine, it is identified again as > umass0: IOMEGA ZIP ........ > but just before it starts mounting filesystems, It stops for a while and then returns a some output messages: > > > Fault trap 12: Page fault while in kernel mode > ----------- > ---------- > ----------- > Panic: Page fault > Rebooting in 15 seconds > > > > This goes on and on until I disconnect the ZIP drive, and then it boots normally. > > > ANy Ideas? could it be some conflict with the IDE hard drive.??? > > __________________________________________________________________ > Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > -- The USB for FreeBSD project. n_hibma@FreeBSD.ORG http://www.etla.net/~n_hibma/usb/usb.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 8:56: 6 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 2F38637B71C for ; Fri, 16 Mar 2001 08:56:02 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f2GGtnb14872; Fri, 16 Mar 2001 08:55:49 -0800 Date: Fri, 16 Mar 2001 08:55:49 -0800 From: Brooks Davis To: Warner Losh Cc: Brooks Davis , freebsd-mobile@FreeBSD.ORG Subject: Re: ifconfig your wireless card Message-ID: <20010316085549.A12128@Odin.AC.HMC.Edu> References: <20010315141705.A2184@Odin.AC.HMC.Edu> <200103160800.f2G80e929001@harmony.village.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200103160800.f2G80e929001@harmony.village.org>; from imp@harmony.village.org on Fri, Mar 16, 2001 at 01:00:40AM -0700 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 16, 2001 at 01:00:40AM -0700, Warner Losh wrote: > In message <20010315141705.A2184@Odin.AC.HMC.Edu> Brooks Davis writes: > : Currently, wi and an cards are supported, but the interface is designed > : to be general is with some minor work support for awi and ray cards > : could be added. >=20 > I have my awi card back in action. What changes would be needed for > it? If you take a look at the current patch there is some totally untested and partialy incomplete code to implement the ioctl part of the interface. Basicaly what you do is implement the interface documented in ieee80211.4 (included in the patch). You then implement an if_media interface for speed selection and ad-hoc vs infrastructure. The one gotcha with implementing the awi stuff is that my API doesn't currently understand hopsets on FH cards. You could probably overload channel, but I'm not sure that going to be the right thing to do. If I actually knew what you'd like to set in general with regard to hopsets I could add appropriate support to ifconfig and the API easily. > Also, I have cnwctl in the wings right now that I'd like to not commit=20 > if ifconfig could be made to work :-). cnwctl? I don't see a cnw driver... If this is for an as yet uncomitted 802.11 driver it should be pretty straight forward. -- Brooks --=20 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 --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6skWUXY6L6fI4GtQRAsupAKDQxfbjk78Bw7MuBLfMDMt8hLyskQCg0Lrv DOzPZt+jBnCH8XD334a5xtY= =1uZe -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 9: 3: 7 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id BFA8D37B71A for ; Fri, 16 Mar 2001 09:02:52 -0800 (PST) (envelope-from oppermann@monzoon.net) Received: (qmail 96606 invoked from network); 16 Mar 2001 16:59:20 -0000 Received: from unknown (HELO monzoon.net) ([62.48.21.98]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 16 Mar 2001 16:59:20 -0000 Message-ID: <3AB246C8.9031B21@monzoon.net> Date: Fri, 16 Mar 2001 18:00:56 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Subject: Helping with progress of PCMCIA/PCCARD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there, I'm willing to support the progress of the PCMCIA/PCCARD code with some serious money. Target is to make it really working well, the stuff we have now is somewhat a mess. I'm spending now over two days (w/o success so far) on getting an Lucent Orinoco and an Cisco Aironet card working in my Vaio (600Z) and my embedded system (FreeBSD-Stable and -current). If one or more of you pccard hackers want to spend a couple of month' on it to get it really forward I'm willing to fully fund that. Please reply privatly if you are interested. Cheers -- Andre Oppermann Monzoon Networks AG Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 35 Fax +41 1 277 75 36 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 9: 7: 9 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id A998D37B718 for ; Fri, 16 Mar 2001 09:07:06 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2GH73935160; Fri, 16 Mar 2001 10:07:03 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103161707.f2GH73935160@harmony.village.org> To: Brooks Davis Subject: Re: ifconfig your wireless card Cc: freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 16 Mar 2001 08:55:49 PST." <20010316085549.A12128@Odin.AC.HMC.Edu> References: <20010316085549.A12128@Odin.AC.HMC.Edu> <20010315141705.A2184@Odin.AC.HMC.Edu> <200103160800.f2G80e929001@harmony.village.org> Date: Fri, 16 Mar 2001 10:07:03 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20010316085549.A12128@Odin.AC.HMC.Edu> Brooks Davis writes: : The one gotcha with implementing the awi stuff is that my API doesn't : currently understand hopsets on FH cards. OK. The awi card is ds, so that shouldn't be a big deal. : > Also, I have cnwctl in the wings right now that I'd like to not commit=20 : > if ifconfig could be made to work :-). : : cnwctl? I don't see a cnw driver... If this is for an as yet uncomitted : 802.11 driver it should be pretty straight forward. Your tree must be more than a few hours old :-) cnw isn't 802.11, so maybe it doesn't apply. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 9:49: 1 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from sundance.cse.ucsc.edu (sundance.cse.ucsc.edu [128.114.48.62]) by hub.freebsd.org (Postfix) with SMTP id 7161E37B719 for ; Fri, 16 Mar 2001 09:48:59 -0800 (PST) (envelope-from dkulp@cse.ucsc.edu) Received: (from dkulp@localhost) by sundance.cse.ucsc.edu (8.6.10/8.6.12) id JAA06905; Fri, 16 Mar 2001 09:48:59 -0800 Date: Fri, 16 Mar 2001 09:48:59 -0800 Message-Id: <200103161748.JAA06905@sundance.cse.ucsc.edu> From: "David C. Kulp" To: freebsd-mobile@freebsd.org Subject: Laptop Compatibility for FreeBSD Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just wanted to mention that the list of FreeBSD ported laptops has topped 100 at http://www.cse.ucsc.edu/~dkulp/fbsd/laptop.html This is similar to the PAO survey. It's not pretty, but I think the nicest thing is that it provides an opportunity for people with similar models to find a sympathetic ear. That's all. Have a good day. -d To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 9:55:14 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id F18CC37B718 for ; Fri, 16 Mar 2001 09:55:10 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f2GHt8d20495; Fri, 16 Mar 2001 09:55:08 -0800 Date: Fri, 16 Mar 2001 09:55:08 -0800 From: Brooks Davis To: Warner Losh Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: ifconfig your wireless card Message-ID: <20010316095508.B12128@Odin.AC.HMC.Edu> References: <20010316085549.A12128@Odin.AC.HMC.Edu> <20010315141705.A2184@Odin.AC.HMC.Edu> <200103160800.f2G80e929001@harmony.village.org> <20010316085549.A12128@Odin.AC.HMC.Edu> <200103161707.f2GH73935160@harmony.village.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="WYTEVAkct0FjGQmd" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200103161707.f2GH73935160@harmony.village.org>; from imp@harmony.village.org on Fri, Mar 16, 2001 at 10:07:03AM -0700 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --WYTEVAkct0FjGQmd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 16, 2001 at 10:07:03AM -0700, Warner Losh wrote: > OK. The awi card is ds, so that shouldn't be a big deal. Hmm, the README claims to support "BayStack 650" and "Netwave AirSurfer Plus" cards which are both FH cards. Is it wrong? > : > Also, I have cnwctl in the wings right now that I'd like to not commi= t=3D20 > : > if ifconfig could be made to work :-). > :=20 > : cnwctl? I don't see a cnw driver... If this is for an as yet uncomitt= ed > : 802.11 driver it should be pretty straight forward. >=20 > Your tree must be more than a few hours old :-) I saw it in my cvsup about a minute after I sent that. :-) > cnw isn't 802.11, so maybe it doesn't apply. It depends. We could probably fake up an interface using the SSID (possiably parsed) for the domain and then wepkey for the scramble key. I don't know if it's really worth the effort though, I presume since the files have a NetBSD copyright cnwctl is already mostly written? -- Brooks --=20 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 --WYTEVAkct0FjGQmd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6slN6XY6L6fI4GtQRAu8SAKDcFYGxlqgPSOuk6jeoh2/KYo6SqACg4fAC qR5O3hph+/tJ4KMBn2tHSA8= =YDG/ -----END PGP SIGNATURE----- --WYTEVAkct0FjGQmd-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 11:30:10 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from burdell.cc.gatech.edu (burdell.cc.gatech.edu [130.207.3.207]) by hub.freebsd.org (Postfix) with ESMTP id 29FD637B718 for ; Fri, 16 Mar 2001 11:30:06 -0800 (PST) (envelope-from dibble@cc.gatech.edu) Received: from felix.cc.gatech.edu (felix.cc.gatech.edu [130.207.107.11]) by burdell.cc.gatech.edu (8.9.1/8.9.3) with ESMTP id OAA26392; Fri, 16 Mar 2001 14:30:05 -0500 (EST) Received: from thor (thor.cnd.gatech.edu [199.77.147.56]) by felix.cc.gatech.edu (8.9.3+Sun/8.9.1) with SMTP id OAA00973; Fri, 16 Mar 2001 14:30:04 -0500 (EST) Message-ID: <004601c0ae4f$b5e7f160$38934dc7@cnd.gatech.edu> From: "Jeff Lee" To: "David C. Kulp" , References: <200103161748.JAA06905@sundance.cse.ucsc.edu> Subject: Re: Laptop Compatibility for FreeBSD Date: Fri, 16 Mar 2001 14:31:34 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just looking at it the PAO patches seem to be for only freeBSD 3.5.1 and under. I am running 4.3-beta on my compaq laptop. Which would be better from a hardware support standpoint? ################# Jeff Lee dibble@cc.gatech.edu PGP ID: 0xDDB291A5 ----- Original Message ----- From: "David C. Kulp" To: Sent: Friday, March 16, 2001 12:48 PM Subject: Laptop Compatibility for FreeBSD > I just wanted to mention that the list of FreeBSD ported laptops has > topped 100 at http://www.cse.ucsc.edu/~dkulp/fbsd/laptop.html > This is similar to the PAO survey. > > It's not pretty, but I think the nicest thing is that it provides > an opportunity for people with similar models to find a sympathetic > ear. > > That's all. Have a good day. > > -d > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 11:44:38 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [63.86.88.201]) by hub.freebsd.org (Postfix) with ESMTP id 3048537B718 for ; Fri, 16 Mar 2001 11:44:35 -0800 (PST) (envelope-from desmo@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1000) id AF2C07589; Fri, 16 Mar 2001 11:45:22 -0800 (PST) Date: Fri, 16 Mar 2001 11:45:22 -0800 From: Ken Monville To: Freebsd-mobile@freebsd.org Subject: ed driver Message-ID: <20010316114522.A30722@moo.sysabend.org> Reply-To: kjm@bandwidth.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Hardly any X-Operating-System: FreeBSD 3.3-RELEASE Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi everybody, I've been fighting for nearly a week with trying to get my Dell CPx online with 4.2-R. I did a cd install but could not get either of the pcmcia cards I have to work. I was using both a Linksys PCMPC100 (V3) and a D-Link DFE-650DX. I got both to allocate resources properly, but both would spew "ed0: device timeout" when trying to receive traffic. (It appeared they could send fine as I saw DHCP requests when sniffing the network with tcpdump.) Finally I stumbled accross a mail which referenced a program called fa_select.c. This allowed me to configure the card to negotiate the link speed/type properly. Happily, I am now working and on the network. If the fa_select.c functionality going to be incorporated into the driver in future releases? Perhaps fa_select just just be part of the base system? Url to fa_select.c http://webperso.easynet.fr/fonvi/fa_select.c Well, thanks for listening to my rant. Ken -- Ken Monville GCS d- s++: a-- C+++ UHB++++$ P+++ L- E--- W+ N o? K? w--- O M+ !V PS PE++ Y+ PGP+ t 5 X+ !R tv+ b DI+++ D++ G e>++ h r% y+(*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 12:15:43 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 9E1F137B71A for ; Fri, 16 Mar 2001 12:15:41 -0800 (PST) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f2GKFZs19932; Fri, 16 Mar 2001 12:15:35 -0800 (PST) Message-Id: <200103162015.f2GKFZs19932@ptavv.es.net> To: "Jeff Lee" Cc: "David C. Kulp" , freebsd-mobile@FreeBSD.ORG Subject: Re: Laptop Compatibility for FreeBSD In-reply-to: Your message of "Fri, 16 Mar 2001 14:31:34 EST." <004601c0ae4f$b5e7f160$38934dc7@cnd.gatech.edu> Date: Fri, 16 Mar 2001 12:15:34 -0800 From: "Kevin Oberman" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: "Jeff Lee" > Date: Fri, 16 Mar 2001 14:31:34 -0500 > Sender: owner-freebsd-mobile@FreeBSD.ORG > > Just looking at it the PAO patches seem to be for only freeBSD 3.5.1 and > under. I am running 4.3-beta on my compaq laptop. Which would be better > from a hardware support standpoint? In almost all cases, 4-Stable is the best place to be. Almost everything in PAO has been merged into -stable. There are some very uncommon cards that don't have drivers in Stable, but they are few and far between and, unless you need one of these, -stable is a far better choice. The other exception is for CardBus cards. These are rapidly becoming more popular and are only supported in -current. There is no support in either -stable or PAO. I'd suggest trying to avoid CardBus cards for now and -current has been even more of a mine field than usual of late and is not for the weak at heart (or those who don't want to rebuild daily and reboot, on some occasions, far more often. The last I heard, the developers were not planning on CardBus support in a release before 5.0, but I did see a message that it might happen before then if 5.0 gets pushed out too far. But, it will be a while, at best. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 13:52:38 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2F31937B71A for ; Fri, 16 Mar 2001 13:52:35 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2GLqX937500 for ; Fri, 16 Mar 2001 14:52:34 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103162152.f2GLqX937500@harmony.village.org> To: mobile@freebsd.org Subject: Simple patches for IRQ enforcement Date: Fri, 16 Mar 2001 14:52:33 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please look at http://people.freebsd.org/~imp/Ppccard-irq for a patch that might help things. It requires that the irq for management be in the list of allowed ones (3, 4, 5, 7, 9, 10, 11, 12, 14, 15). In addition, it cleans up a few manifest constants that are in the driver now that I have the PD6710/'22 datasheet. It is amazing the number of things that you learn about hardware when you have a good datasheet for it. It also explicitly turns on the the "report management interrupts" flag in the PCIC_INT_GEN register. This is programmed on by most bioses, but some seem to not do it so we don't get management interrupts on those machines. This is especially true of a suspend/resume sequence. It also adds the 82365 to the list of chips we do special things for for power. While the original 82365 didn't support 3.3V operations, many clones do. And they do it in the PD67xx way, it would appear. Since these registers are not used on the 82365, this should be OK as the 3.3V stuff will fail later anyway. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 14:12:55 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id C979637B718 for ; Fri, 16 Mar 2001 14:12:53 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2GMCj937676; Fri, 16 Mar 2001 15:12:45 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103162212.f2GMCj937676@harmony.village.org> To: kjm@bandwidth.org Subject: Re: ed driver Cc: Freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 16 Mar 2001 11:45:22 PST." <20010316114522.A30722@moo.sysabend.org> References: <20010316114522.A30722@moo.sysabend.org> Date: Fri, 16 Mar 2001 15:12:45 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20010316114522.A30722@moo.sysabend.org> Ken Monville writes: : Well, thanks for listening to my rant. fa-select will never be part of the base system directly. However, in -current we've subsumed the need for fa-select by putting the functionality into the driver. There are some problems with the current driver, but it works well on 10/100 switches. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 14:14:11 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4289837B71A for ; Fri, 16 Mar 2001 14:14:09 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2GMDv937695; Fri, 16 Mar 2001 15:13:57 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103162213.f2GMDv937695@harmony.village.org> To: "Kevin Oberman" Subject: Re: Laptop Compatibility for FreeBSD Cc: "Jeff Lee" , "David C. Kulp" , freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 16 Mar 2001 12:15:34 PST." <200103162015.f2GKFZs19932@ptavv.es.net> References: <200103162015.f2GKFZs19932@ptavv.es.net> Date: Fri, 16 Mar 2001 15:13:57 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200103162015.f2GKFZs19932@ptavv.es.net> "Kevin Oberman" writes: : The last I heard, the developers were not planning on CardBus support : in a release before 5.0, but I did see a message that it might happen : before then if 5.0 gets pushed out too far. But, it will be a while, : at best. -stable won't see cardbus ebfore 6 months from now unless something seriously strange happens :-). But there were folks that wanted to fund things, so maybe it might happen. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Mar 16 18: 3:13 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from femail12.sdc1.sfba.home.com (femail12.sdc1.sfba.home.com [24.0.95.108]) by hub.freebsd.org (Postfix) with ESMTP id 5F43E37B718 for ; Fri, 16 Mar 2001 18:03:11 -0800 (PST) (envelope-from europax@home.com) Received: from home.com ([24.12.186.185]) by femail12.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010317020303.GIWY7377.femail12.sdc1.sfba.home.com@home.com>; Fri, 16 Mar 2001 18:03:03 -0800 Message-ID: <3AB2C5DF.BC351396@home.com> Date: Fri, 16 Mar 2001 18:03:11 -0800 From: Rob X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "David C. Kulp" Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Laptop Compatibility for FreeBSD References: <200103161748.JAA06905@sundance.cse.ucsc.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "David C. Kulp" wrote: > > I just wanted to mention that the list of FreeBSD ported laptops has > topped 100 at http://www.cse.ucsc.edu/~dkulp/fbsd/laptop.html > This is similar to the PAO survey. > > It's not pretty, but I think the nicest thing is that it provides > an opportunity for people with similar models to find a sympathetic > ear. > > That's all. Have a good day. > > -d > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message Whats the best way to update an entry? Mine on the Acer 602TER should add that burncd works well on its CDRW and audio is fine with new pcm driver. Rob. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Mar 17 4:53:19 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 1027137B718 for ; Sat, 17 Mar 2001 04:53:07 -0800 (PST) (envelope-from alex@cichlids.cichlids.com) Received: from fwd01.sul.t-online.com by mailout02.sul.t-online.com with smtp id 14eGCJ-0001cP-01; Sat, 17 Mar 2001 13:52:43 +0100 Received: from neutron.cichlids.com (520050424122-0001@[62.225.195.199]) by fmrl01.sul.t-online.com with esmtp id 14eGC5-0tyHD6C; Sat, 17 Mar 2001 13:52:29 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 983D1AB44; Sat, 17 Mar 2001 13:53:40 +0100 (CET) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id D356614A5A; Fri, 16 Mar 2001 21:22:48 +0100 (CET) Date: Fri, 16 Mar 2001 21:22:48 +0100 To: Ken Monville Cc: Freebsd-mobile@freebsd.org Subject: Re: ed driver Message-ID: <20010316212248.A7992@cichlids.cichlids.com> References: <20010316114522.A30722@moo.sysabend.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010316114522.A30722@moo.sysabend.org>; from kjm@bandwidth.org on Fri, Mar 16, 2001 at 11:45:22AM -0800 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@cichlids.cichlids.com (Alexander Langer) X-Sender: 520050424122-0001@t-dialin.net Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Ken Monville (kjm@bandwidth.org): > speed/type properly. Happily, I am now working and on the network. If > the fa_select.c functionality going to be incorporated into the driver in > future releases? Perhaps fa_select just just be part of the base system? Similar code (at least with the same effect) has been committed to -CURRENT about two (?) weeks ago. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Mar 17 9:12:37 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from unbeat.com (24-168-37-22.nyc.rr.com [24.168.37.22]) by hub.freebsd.org (Postfix) with ESMTP id 80FC337B719 for ; Sat, 17 Mar 2001 09:12:28 -0800 (PST) (envelope-from moxie@unbeat.com) Received: (from moxie@localhost) by unbeat.com (8.11.2/8.11.2) id f2GIQD100717; Fri, 16 Mar 2001 13:26:13 -0500 (EST) (envelope-from moxie) Date: Fri, 16 Mar 2001 13:26:13 -0500 From: JT To: Dominic Mitchell Cc: Guangrui Fu , John Reynolds~ , mobile@FreeBSD.ORG Subject: Re: Dell Latitude CPx J - good match for 4-STABLE? Message-ID: <20010316132613.B284@zed.unbeat.com> References: <15023.61342.400884.548056@hip186.ch.intel.com> <20010314231707.7672.qmail@web3102.mail.yahoo.com> <20010314235412.A53709@ppe.happygiraffe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010314235412.A53709@ppe.happygiraffe.net>; from dom@happygiraffe.net on Wed, Mar 14, 2001 at 11:54:12PM +0000 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I can confirm that the Vaio Z505LS superslim works really well, though PCCard needs some fiddling (don't use polling, change memory location as noted in archives). Some of the special function buttons for suspending, volume control, lcd brightness don't work (apparently they are software-based). XFree86 doesn't respond to ctrl-alt-backspace for some reason, but that's about it. Upgrading to 4 might help, or maybe I stomped it with keymappings (alt->meta) or something really stupid. Battery usage is sub-optimal, but there were some recent discussions about additional sysctls to aid laptop users in spinning down hard drives and such - I'd love to see them make it into -stable. On Wed, Mar 14, 2001 at 11:54:12PM +0000, Dominic Mitchell wrote: > On Wed, Mar 14, 2001 at 03:17:07PM -0800, Guangrui Fu wrote: > > a similar question, does anyone tried FreeeBSD 4.2 > > with > > Sony VAIO notebooks and if so, which series? Thanks a > > lot. > > I've got FreeBSD 4.2 (4.3-BETA now) working great on my Z600TEK. I > think that's a euro model, though. It's model number is PCG-5316, if > that's any use. Very nice laptop, very compact, everything works well > (but I had to fiddle a little with pccardd). > -- > M-x smite-the-infidel > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Mar 17 13:28:21 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail.arsconcero.com (elvis2.intrepid.net [209.190.164.164]) by hub.freebsd.org (Postfix) with SMTP id 0F3C837B718 for ; Sat, 17 Mar 2001 13:28:19 -0800 (PST) (envelope-from mark@mail.arsconcero.com) Received: (qmail 16376 invoked by uid 500); 17 Mar 2001 21:28:12 -0000 Date: Sat, 17 Mar 2001 16:28:12 -0500 From: Mark Conway Wirt To: freebsd-mobile@freebsd.org Subject: Zoom 56K Model 3000 Message-ID: <20010317162812.A16363@ArsConcero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to get a Zoom model 3000 working in a 4.2 stable box, and I've run into a difficulty that I've seen others have had, but I'm not sure if there has ever been a resolution. Upon inserting the modem, it's identified as a generic modem, and assigned sio4: Mar 17 13:14:20 elvis /kernel: sio4 at port 0x2e8-0x2ef irq 11 slot 1 on pccard1 Mar 17 13:14:20 elvis /kernel: sio4: type 16450 Mar 17 13:14:20 elvis pccardd[55]: sio4: GENERIC PCMCIA modem inserted. The UART is identified (misidentified?) as a 16450, and when I try to use the modem, the system freezes hard. I see in the archives that there was some discussion of this about six months ago. Was a work-around ever posted? Could a modification of pccard.conf help? Thanks in advance. --Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message