From owner-freebsd-mobile Sun Nov 23 04:20:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA05959 for mobile-outgoing; Sun, 23 Nov 1997 04:20:37 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from oxmail4.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA05947 for ; Sun, 23 Nov 1997 04:20:33 -0800 (PST) (envelope-from neil.long@materials.oxford.ac.uk) Received: from njl2.materials.ox.ac.uk by oxmail4 with SMTP (PP); Sun, 23 Nov 1997 12:20:28 +0000 Received: by njl2.materials.ox.ac.uk (950413.SGI.8.6.12/940406.SGI) for freebsd-mobile@FreeBSD.ORG id MAA24788; Sun, 23 Nov 1997 12:20:28 GMT From: neil.long@materials.oxford.ac.uk (Neil J Long) Message-Id: <199711231220.MAA24788@njl2.materials.ox.ac.uk> Subject: TDK DF2814 on 2.2.5_RELENG anyone? X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: freebsd-mobile@freebsd.org Date: Sun, 23 Nov 1997 12:20:28 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] Content-Type: text Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Just a quick post, the TDK DF2814 v.34 worked under the 2.2-PAO mods but I am getting no luck with 2.2.5-STABLE. Anyone else have this card and had any success? I have an Acer 370C, the 3Com PC ethernet card works fine. Anyone know of a modem card which does work with an Acer of this ilk? Thanks Neil From owner-freebsd-mobile Sun Nov 23 07:26:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14351 for mobile-outgoing; Sun, 23 Nov 1997 07:26:17 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from capricorn.loopback.com (loopback.com [205.243.146.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA14341 for ; Sun, 23 Nov 1997 07:26:12 -0800 (PST) (envelope-from elazich@capricorn.loopback.com) Received: from localhost (elazich@localhost) by capricorn.loopback.com (8.8.5/8.7.3) with SMTP id JAA27342; Sun, 23 Nov 1997 09:22:03 -0600 (CST) Date: Sun, 23 Nov 1997 09:22:03 -0600 (CST) From: Eli Lazich To: Nate Williams cc: freebsd-mobile@FreeBSD.ORG Subject: Re: PAO 2.2.5 In-Reply-To: <199711230605.XAA19910@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 22 Nov 1997, Nate Williams wrote: > > I have a 3com 3c589b ethernet card that appears to be recognized as zp0 > > but is not configurable if I run ifconfig -a. > > How do you know it's recognized? It's possible that the configuration > values stored in the card's EEPROM are different than what the FreeBSD > driver expects. The zp0 driver is not a 'PCMCIA/generic' driver, so it > uses the card's own built-in configuratio (port, IRQ, IOMEM) values to > configure the card, similar to a 'point driver' in DOS. > > > Under PAO-2.2.2 it was configured as ep0. > > The default FreeBSD boot floppy doesn't have generic PCCARD support in > it. You need to build a special kernel with PCCARD support (which will > cause your ethernet driver to be ep0, like in PAO.) > > > I also have a Motorola Montana Modem that does not get > > recognized at all. > > See above. The boot floppy laptop drivers are zp0/ze0, and work with > the 3Com 589 and IBM Info-mover cards respectively. No other > laptop/PCMCIA cards are supported on the boot floppy. > > > Nate > OK, I understand all of this, now that prompts the question of how in 2.2.5 you build the kernel to support PCMCIA. I found the GENERIC kernel with the PCMCIA lines commented out, tried to build and got an error because the generic (ze0/zp0) devices were still left in. I then tried to rebuild with those devices commented out to no avail. I got an error toward the end of the make on the new kernel referring to scsi drivers not being configured (I'll have to try again to get the exact error messages). OOnce I get the new kernel built, where do valid pccard.conf and pccard_ether etc... files get created. Eli From owner-freebsd-mobile Sun Nov 23 07:41:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA15031 for mobile-outgoing; Sun, 23 Nov 1997 07:41:54 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA15024 for ; Sun, 23 Nov 1997 07:41:51 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA14794; Sun, 23 Nov 1997 08:41:50 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA20712; Sun, 23 Nov 1997 08:41:46 -0700 Date: Sun, 23 Nov 1997 08:41:46 -0700 Message-Id: <199711231541.IAA20712@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eli Lazich Cc: Nate Williams , freebsd-mobile@FreeBSD.ORG Subject: Re: PAO 2.2.5 In-Reply-To: References: <199711230605.XAA19910@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > OK, I understand all of this, now that prompts the question of how in > 2.2.5 you build the kernel to support PCMCIA. As I stated in earlier email, the FreeBSD boot floppy doesn't have generic PCMCIA support, but has support for 2 specific ethernet cards, which are serviced by zp/ze. > I found the GENERIC kernel > with the PCMCIA lines commented out, tried to build and got an error > because the generic (ze0/zp0) devices were still left in. Right, you can't mix the 'specific card' driver and 'generic PCMCIA' support. > I then tried to rebuild with those devices commented out to no avail. > I got an error toward the end of the make on the new kernel referring > to scsi drivers not being configured (I'll have to try again to get > the exact error messages). Because of this confusion, in the next releases of FreeBSD there are now 'PCCARD' config files that contain laptop support kernels. If you upgrade to 2.2.5-STABLE (post 2.2.5), that config file will exist which should give you a better idea what is supported in FreeBSD, as well as much better laptop support. > OOnce I get the new kernel built, where do valid pccard.conf and > pccard_ether etc... files get created. They are in /usr/src/etc, and must be edited/installed in /etc. (Some are already, but I believe pccard.conf is installed as pccard.conf.sample). Nate From owner-freebsd-mobile Sun Nov 23 13:13:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA01956 for mobile-outgoing; Sun, 23 Nov 1997 13:13:51 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from inertia.dfacades.com (inertia.dfacades.com [207.155.93.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA01949 for ; Sun, 23 Nov 1997 13:13:49 -0800 (PST) (envelope-from dleeds@dfacades.com) Received: (from dleeds@localhost) by inertia.dfacades.com (8.8.7/8.8.7) id NAA20976; Sun, 23 Nov 1997 13:17:07 -0800 (PST) From: Daniel Leeds Message-Id: <199711232117.NAA20976@inertia.dfacades.com> Subject: Re: Info on a card... In-Reply-To: <199711221635.JAA03355@harmony.village.org> from Warner Losh at "Nov 22, 97 09:35:21 am" To: imp@village.org (Warner Losh) Date: Sun, 23 Nov 1997 13:17:06 -0800 (PST) Cc: mobile@freebsd.org X-Mailer: ELM [version 2.4ME+ PL35 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In message Donald Burr writes: > > But the aic driver is known to be a total flake right now. At least > for my 1522 and 1522A cards it won't work with just one item on the > bus, properly terminated (my scsi cd changer). Does PAO have a > better aic driver? I'll have to try it if that is the case on my > desktop. > > If I do get the card (and it is really cheap), I think that it will > give me incentive to get things working if there is some kind of > problem... > > Warner i have an adaptec 1460 pcmcia using the aic driver and it is working fine, with an external 3gig drive, cdrom, cdrom burner, and DLT. From owner-freebsd-mobile Sun Nov 23 13:15:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA02083 for mobile-outgoing; Sun, 23 Nov 1997 13:15:30 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA02075 for ; Sun, 23 Nov 1997 13:15:26 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xZjNE-0005YG-00; Sun, 23 Nov 1997 14:15:24 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id OAA01594; Sun, 23 Nov 1997 14:14:16 -0700 (MST) Message-Id: <199711232114.OAA01594@harmony.village.org> To: Daniel Leeds Subject: Re: Info on a card... Cc: mobile@freebsd.org In-reply-to: Your message of "Sun, 23 Nov 1997 13:17:06 PST." <199711232117.NAA20976@inertia.dfacades.com> References: <199711232117.NAA20976@inertia.dfacades.com> Date: Sun, 23 Nov 1997 14:14:16 -0700 From: Warner Losh Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199711232117.NAA20976@inertia.dfacades.com> Daniel Leeds writes: : i have an adaptec 1460 pcmcia using the aic driver and it is working : fine, with an external 3gig drive, cdrom, cdrom burner, and DLT. Dang. Wish my 1522A worked as well. I'll have to get the Toaster card, since it is so cheap as to be worth the risk... Warner From owner-freebsd-mobile Sun Nov 23 18:57:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25793 for mobile-outgoing; Sun, 23 Nov 1997 18:57:38 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from u3.farm.idt.net (root@u3.farm.idt.net [169.132.8.12]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25788 for ; Sun, 23 Nov 1997 18:57:33 -0800 (PST) (envelope-from garycorc@idt.net) Received: from idt.net (ppp-17.ts-1.mlb.idt.net [169.132.71.17]) by u3.farm.idt.net (8.8.8/8.8.5) with ESMTP id VAA06812; Sun, 23 Nov 1997 21:57:27 -0500 (EST) Message-ID: <3478ED06.56F54BC2@idt.net> Date: Sun, 23 Nov 1997 21:57:10 -0500 From: "Gary T. Corcoran" X-Mailer: Mozilla 4.03 [en] (Win95; U) MIME-Version: 1.0 To: Nate Williams CC: freebsd-mobile@FreeBSD.ORG Subject: Re: PC-Card modem problem References: <19971120212503.32639@quiddity.org> <199711211706.KAA14332@mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nate, Regarding: > Seriously, even if all of the above work out, Bruce pointed out a big > bug in the modem/serial probing code that exists in the PCCARD code that > negatively affects certain hardware. It's a fairly 'simple' fix, but > requires *LOTS* of changes to the entire system. Rather than attack it, > I want to finish up the 'suspend/resume' stuff and then see how things > fare. I'm curious: might this 'big bug' have anything to do with the built-in serial port in my Tecra 750 not being detected? I haven't had any time to look into it (and probably won't till next year) since I don't yet use it. But if there is a 'known' problem, I won't worry about it - until I need to use the port, of course... ;-) Gary From owner-freebsd-mobile Sun Nov 23 19:04:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA26338 for mobile-outgoing; Sun, 23 Nov 1997 19:04:33 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26331 for ; Sun, 23 Nov 1997 19:04:30 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id UAA18439; Sun, 23 Nov 1997 20:04:28 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA21779; Sun, 23 Nov 1997 20:04:27 -0700 Date: Sun, 23 Nov 1997 20:04:27 -0700 Message-Id: <199711240304.UAA21779@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Gary T. Corcoran" Cc: Nate Williams , freebsd-mobile@FreeBSD.ORG Subject: Re: PC-Card modem problem In-Reply-To: <3478ED06.56F54BC2@idt.net> References: <19971120212503.32639@quiddity.org> <199711211706.KAA14332@mt.sri.com> <3478ED06.56F54BC2@idt.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Seriously, even if all of the above work out, Bruce pointed out a big > > bug in the modem/serial probing code that exists in the PCCARD code that > > negatively affects certain hardware. It's a fairly 'simple' fix, but > > requires *LOTS* of changes to the entire system. Rather than attack it, > > I want to finish up the 'suspend/resume' stuff and then see how things > > fare. > > I'm curious: might this 'big bug' have anything to do with the built-in > serial port in my Tecra 750 not being detected? Nope, it's completely un-related, since the built-in serial ports aren't probed by the PCCARD code. Nate From owner-freebsd-mobile Mon Nov 24 03:28:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA26244 for mobile-outgoing; Mon, 24 Nov 1997 03:28:22 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (ppp13.portal.net.au [202.12.71.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA26237 for ; Mon, 24 Nov 1997 03:28:10 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA00245; Mon, 24 Nov 1997 11:21:16 +1030 (CST) Message-Id: <199711240051.LAA00245@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nate Williams cc: Ken Key , mobile@freebsd.org Subject: Re: Sony PRD650-WM and 2.2.5-STABLE? In-reply-to: Your message of "Sat, 22 Nov 1997 14:50:11 PDT." <199711222150.OAA19106@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Nov 1997 11:21:15 +1030 From: Mike Smith Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I'm about ready to wipe and load Win95 (but it won't stay long! :-) > > just so I can test the darn player to make sure the drive isn't toast. > > Ahh, you haven't initialized it under Win95? Unfortunately, I couldn't > get it to work at all until *after* I used under Win95. Then, it seemed > to work fine from that point on, even after power-cycling and has worked > since. Maybe the Win95 driver did something to the card/CD player to > make it work fine, but it was required for my So y CD650. Perhaps it has a soft-settable CIS, and has to be initialised first? Many of the "generic" PCCARD interface chipsets have their CIS in an external EEPROM, allowing them to be personalised for a given vendor. Some vendors may decide to wait until the user gets the card before actually writing this information. Just a guess... mike From owner-freebsd-mobile Mon Nov 24 21:11:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA11023 for mobile-outgoing; Mon, 24 Nov 1997 21:11:24 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from duncan.cs.utk.edu (DUNCAN.CS.UTK.EDU [128.169.94.83]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA11015 for ; Mon, 24 Nov 1997 21:11:18 -0800 (PST) (envelope-from key@cs.utk.edu) Received: from LOCALHOST.cs.utk.edu by duncan.cs.utk.edu with SMTP (cf v2.11c-UTK) id AAA01645; Tue, 25 Nov 1997 00:10:52 -0500 Message-Id: <199711250510.AAA01645@duncan.cs.utk.edu> To: Mike Smith cc: Nate Williams , Ken Key , mobile@freebsd.org Subject: Re: Sony PRD650-WM and 2.2.5-STABLE? From: Ken Key In-reply-to: Your message of Mon, 24 Nov 1997 11:21:15 +1030. <199711240051.LAA00245@word.smith.net.au> Date: Tue, 25 Nov 1997 00:10:49 -0500 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Perhaps it has a soft-settable CIS, and has to be initialised first? I'm not too sure about that. The aic0 shows up OK, it's getting the CDROM on the bus to respond. Right now the behavior appears to be that as long as I keep power to the CDROM (it can stand at least 5 minutes but not more than 2 hours) I can pwoer cycle the laptop (and thus 1460A), etc once I've fired up the CDROM under WIn95. If I leave the CDROM unplug from the power supply for something less than 2 hours, it doesn't show up the next time I plug the 1460A in. Note that I don't have the LIP-12 battery, just AC power. Anyways, I installed 2.2-971122-SNAP by booting up on the PAO boot floppy and changing options. I've got it using the ISC DHCP client setting my ed0 and am a happy camper again (modulo the having to boot Win95 occasionally weirdness). Thanks for all the help, K^2 -- Ken Key (key@cs.utk.edu) Univ. of Tennessee, Knoxville From owner-freebsd-mobile Tue Nov 25 11:00:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA09229 for mobile-outgoing; Tue, 25 Nov 1997 11:00:54 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA09221 for ; Tue, 25 Nov 1997 11:00:50 -0800 (PST) (envelope-from jose@dial.pipex.com) Received: (qmail 16655 invoked from network); 25 Nov 1997 19:00:32 -0000 Received: from ao095.du.pipex.com (HELO ?193.130.254.95?) (193.130.254.95) by smtp.dial.pipex.com with SMTP; 25 Nov 1997 19:00:32 -0000 X-Sender: ae220@pop.dial.pipex.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 25 Nov 1997 19:00:40 +0000 To: freebsd-mobile@FreeBSD.ORG From: jose@dial.pipex.com (Jose Marques) Subject: What does "unsupported" really mean? Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm thinking of buying a laptop to run FreeBSD (yet another disillusioned Mac user abandoning ship). The models I've looked at all have some form of "unsupported (at the current time) by FreeBSD" hardware, i.e. CardBUS, XV ports, USB ports etc. Does this mean that I can't use FreeBSD on these machines? Or (hopefully) can I still use FreeBSD but not use the hardware in question? Ta. From owner-freebsd-mobile Tue Nov 25 12:23:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA21632 for mobile-outgoing; Tue, 25 Nov 1997 12:23:51 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA21614 for ; Tue, 25 Nov 1997 12:23:45 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xaRWA-0006r6-00; Tue, 25 Nov 1997 13:23:34 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA14770; Tue, 25 Nov 1997 13:22:44 -0700 (MST) Message-Id: <199711252022.NAA14770@harmony.village.org> To: jose@dial.pipex.com (Jose Marques) Subject: Re: What does "unsupported" really mean? Cc: freebsd-mobile@freebsd.org In-reply-to: Your message of "Tue, 25 Nov 1997 19:00:40 GMT." References: Date: Tue, 25 Nov 1997 13:22:43 -0700 From: Warner Losh Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Jose Marques writes: : I'm thinking of buying a laptop to run FreeBSD (yet another disillusioned : Mac user abandoning ship). The models I've looked at all have some form of : "unsupported (at the current time) by FreeBSD" hardware, i.e. CardBUS, XV : ports, USB ports etc. Does this mean that I can't use FreeBSD on these : machines? Or (hopefully) can I still use FreeBSD but not use the hardware : in question? Generally speaking, unsupported means that you can't use the hardware in question. For some things this isn't a big deal (eg USB ports), while for other things it can be a big deal (CardBus would make it hard to expand a machine). PAO does do CardBus better than stock FreeBSD does at this time. Your best bet would be to take some kind of FreeBSD boot disk with you when purchasing a system and see if you can boot it before purchase. Laptops generally have large restocking fees, so the buy one and return it until it works strategy wouldn't work too well. Warner From owner-freebsd-mobile Tue Nov 25 12:52:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA27092 for mobile-outgoing; Tue, 25 Nov 1997 12:52:35 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA27082 for ; Tue, 25 Nov 1997 12:52:28 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id VAA00374; Tue, 25 Nov 1997 21:50:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: jose@dial.pipex.com (Jose Marques) cc: freebsd-mobile@FreeBSD.ORG Subject: Re: What does "unsupported" really mean? In-reply-to: Your message of "Tue, 25 Nov 1997 19:00:40 GMT." Date: Tue, 25 Nov 1997 21:50:43 +0100 Message-ID: <372.880491043@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message , Jose Marques writes: >I'm thinking of buying a laptop to run FreeBSD (yet another disillusioned >Mac user abandoning ship). The models I've looked at all have some form of >"unsupported (at the current time) by FreeBSD" hardware, i.e. CardBUS, XV >ports, USB ports etc. Does this mean that I can't use FreeBSD on these >machines? Or (hopefully) can I still use FreeBSD but not use the hardware >in question? That has worked for me on all my machines so far :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-mobile Tue Nov 25 14:53:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA13470 for mobile-outgoing; Tue, 25 Nov 1997 14:53:36 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA13451 for ; Tue, 25 Nov 1997 14:53:28 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id JAA00367; Wed, 26 Nov 1997 09:18:51 +1030 (CST) Message-Id: <199711252248.JAA00367@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: jose@dial.pipex.com (Jose Marques) cc: freebsd-mobile@FreeBSD.ORG Subject: Re: What does "unsupported" really mean? In-reply-to: Your message of "Tue, 25 Nov 1997 19:00:40 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Nov 1997 09:18:51 +1030 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm thinking of buying a laptop to run FreeBSD (yet another disillusioned > Mac user abandoning ship). The models I've looked at all have some form of > "unsupported (at the current time) by FreeBSD" hardware, i.e. CardBUS, XV > ports, USB ports etc. Does this mean that I can't use FreeBSD on these > machines? Or (hopefully) can I still use FreeBSD but not use the hardware > in question? You need to consider whether the hardware is critical to the system's operation or not. For example, this Toshiba 220CDS has a USB port (unsupported) and software-selectable PCMCIA/CardBus ports. USB isn't critical, and I can disable the CardBus stuff, so it works really well. When you're buying a laptop, there are two *critical* things to look at: - The pcic type (PCMCIA interface chip). Toshiba, Dell, NEC, Sharp, and IBM all use parts that are compatible with FreeBSD. Acer (at least) does not. YMMV; if at all possible, boot a FreeBSD kernel built with pcic support in order to find out what you're looking at. - Video chipset. The undisputed 'best supported' chipset at the moment is the C&T 655xx family. If you are willing to buy the Accelerated X server then you can look at units using the Cirrus 754x and NeoMagic chipsets. Avoid the rest, as X will not work. mike > Ta. > > > From owner-freebsd-mobile Wed Nov 26 13:08:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA19544 for mobile-outgoing; Wed, 26 Nov 1997 13:08:41 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from gvr.gvr.org (root@gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA19536 for ; Wed, 26 Nov 1997 13:08:36 -0800 (PST) (envelope-from guido@gvr.org) Received: (from guido@localhost) by gvr.gvr.org (8.8.6/8.8.5) id WAA15575; Wed, 26 Nov 1997 22:06:36 +0100 (MET) From: Guido van Rooij Message-Id: <199711262106.WAA15575@gvr.gvr.org> Subject: Re: What does "unsupported" really mean? In-Reply-To: <199711252248.JAA00367@word.smith.net.au> from Mike Smith at "Nov 26, 97 09:18:51 am" To: mike@smith.net.au (Mike Smith) Date: Wed, 26 Nov 1997 22:06:36 +0100 (MET) Cc: jose@dial.pipex.com, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Smith wrote: > When you're buying a laptop, there are two *critical* things to look at: > > - The pcic type (PCMCIA interface chip). Toshiba, Dell, NEC, Sharp, > and IBM all use parts that are compatible with FreeBSD. Acer (at > least) does not. YMMV; if at all possible, boot a FreeBSD kernel > built with pcic support in order to find out what you're looking at. > > - Video chipset. The undisputed 'best supported' chipset at the > moment is the C&T 655xx family. If you are willing to buy the > Accelerated X server then you can look at units using the Cirrus 754x > and NeoMagic chipsets. Avoid the rest, as X will not work. > I am using XFree 3.2 on a: Cirrus CL-GD7548 (on a Compaq Armada 1130) Works just fine. It seems that 3.3 works even better. -Guido From owner-freebsd-mobile Wed Nov 26 14:46:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA26128 for mobile-outgoing; Wed, 26 Nov 1997 14:46:27 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from gvr.gvr.org (root@gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA26111 for ; Wed, 26 Nov 1997 14:46:21 -0800 (PST) (envelope-from guido@gvr.org) Received: (from guido@localhost) by gvr.gvr.org (8.8.6/8.8.5) id XAA16278 for freebsd-mobile@freebsd.org; Wed, 26 Nov 1997 23:46:19 +0100 (MET) From: Guido van Rooij Message-Id: <199711262246.XAA16278@gvr.gvr.org> Subject: armada 1130 with 16bpp To: freebsd-mobile@freebsd.org Date: Wed, 26 Nov 1997 23:46:19 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone succeeded in running XFree86 3.1.1 in 16bpp on an Armada 1130? -Guido From owner-freebsd-mobile Wed Nov 26 15:57:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA01341 for mobile-outgoing; Wed, 26 Nov 1997 15:57:31 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from rigel.cs.pdx.edu (root@rigel.cs.pdx.edu [131.252.220.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA01335 for ; Wed, 26 Nov 1997 15:57:28 -0800 (PST) (envelope-from zchen@cs.pdx.edu) Received: from alcor.cs.pdx.edu (zchen@alcor.cs.pdx.edu [204.203.70.68]) by rigel.cs.pdx.edu (8.8.6/8.8.6) with ESMTP id PAA14973 for ; Wed, 26 Nov 1997 15:57:21 -0800 (PST) Received: from localhost (zchen@localhost) by alcor.cs.pdx.edu (8.8.6/8.8.6) with SMTP id PAA26384 for ; Wed, 26 Nov 1997 15:57:20 -0800 (PST) X-Authentication-Warning: alcor.cs.pdx.edu: zchen owned process doing -bs Date: Wed, 26 Nov 1997 15:57:19 -0800 (PST) From: zhong chen To: freebsd-mobile@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am a member of Portland State University's Secure Mobile Network project. We use FreeBSD as the platform of developing various Mobile IP daemons and applications. Curretly, we are talking about supoorting multicast in Mobile IP. The problem is that, all our routers speak PIM (Protocol Independent Multicasting), but the FreeBSD mrouted speaks DVMRP (Distance Vector Multicast Routing Protocol), so they can not interoperate and our mobile hosts can not connect to mbone when their traffic are indirectly routed through mobility agents which are powered by FreeBSD. Any idea about this problem is appreciated. (Is there a PIM implementation for FreeBSD? Or PIM and DVMRP can actually interoperate?) Thanks a lot! *********************************************** Zhong CHEN Dept. of Computer Science Portland State University P.O.Box 751 Portland, OR 97207 Tel: (503)725,4138(O) http://www.cs.pdx.edu/~zchen/ *********************************************** From owner-freebsd-mobile Fri Nov 28 05:08:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA12029 for mobile-outgoing; Fri, 28 Nov 1997 05:08:54 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from gate2.consol.de (gate2.consol.de [194.162.127.131]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA12011 for ; Fri, 28 Nov 1997 05:08:40 -0800 (PST) (envelope-from mwe@consol.de) Received: (from root@localhost) by gate2.consol.de (8.8.7/8.8.7) id OAA29802 for ; Fri, 28 Nov 1997 14:08:35 +0100 (CET) (envelope-from mwe@consol.de) Received: from gauss.int.consol.de(10.0.1.2) by gate2.consol.de via smap (V2.0) id xma029651; Fri, 28 Nov 97 13:50:24 +0100 Received: from fourier.int.consol.de (mwe@fourier.int.consol.de [10.0.1.17]) by gauss.int.consol.de (8.8.6/8.8.6) with ESMTP id HAA07252 for ; Fri, 28 Nov 1997 07:50:26 -0500 (EST) Received: (from mwe@localhost) by fourier.int.consol.de (8.8.7/8.8.7) id NAA17015; Fri, 28 Nov 1997 13:50:23 +0100 (CET) (envelope-from mwe) Message-ID: <19971128135023.30234@consol.de> Date: Fri, 28 Nov 1997 13:50:23 +0100 From: Michael Elbel To: mobile@freebsd.org Subject: Any experiences with Kapok Notebooks? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Like the subject says - does anybody have experience with Kapok notebooks (http://www.kapok.com.tw)? I'm looking for a notebook and they appear to have an incredible price/performance ratio (14" Display for prices I haven't seen yet in Germany - they're resold by SEH here (http://www.seh-gmbh.de). Unfortunately, it's pretty difficult to get technical specifications (video controller, chipset etc.) So, anybody out there who has had one under his/her fingers and tried to run FreeBSD? Experiences? Michael -- Michael Elbel, ConSol*, Muenchen, Germany - mwe@consol.de Fermentation fault (coors dumped) From owner-freebsd-mobile Sat Nov 29 11:57:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA17310 for mobile-outgoing; Sat, 29 Nov 1997 11:57:34 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from lsmarso.dialup.access.net (lsmarso@lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA17305 for ; Sat, 29 Nov 1997 11:57:27 -0800 (PST) (envelope-from lsmarso@lsmarso.dialup.access.net) Received: (from lsmarso@localhost) by lsmarso.dialup.access.net (8.8.5/8.8.5) id OAA01297 for freebsd-mobile@freebsd.org; Sat, 29 Nov 1997 14:56:40 -0500 (EST) Message-ID: <19971129145636.34723@panix.com> Date: Sat, 29 Nov 1997 14:56:36 -0500 From: "Larry S. Marso" To: freebsd-mobile@freebsd.org Subject: apm -- possible to disable auto-suspend? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently learned in a desperate, bleed the batteries dry session that my dual lithium ion battery configuration lasts *substantially* longer (1/2 +) than the point that the apm system starts auto-suspending my system. At the same time, I need my apm's features that ramp down the cpu and cutoff my floppy drive when they are unused. Is there any way to turn off the system's propensity to suspend my system, but retain other apm features? -- Larry S. Marso lsmarso@panix.com From owner-freebsd-mobile Sat Nov 29 19:06:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10054 for mobile-outgoing; Sat, 29 Nov 1997 19:06:50 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (ppp4.portal.net.au [202.12.71.104]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10046 for ; Sat, 29 Nov 1997 19:06:43 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA00378; Sun, 30 Nov 1997 13:31:47 +1030 (CST) Message-Id: <199711300301.NAA00378@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Larry S. Marso" cc: freebsd-mobile@freebsd.org Subject: Re: apm -- possible to disable auto-suspend? In-reply-to: Your message of "Sat, 29 Nov 1997 14:56:36 CDT." <19971129145636.34723@panix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 30 Nov 1997 13:31:46 +1030 From: Mike Smith Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I recently learned in a desperate, bleed the batteries dry session that my > dual lithium ion battery configuration lasts *substantially* longer (1/2 +) > than the point that the apm system starts auto-suspending my system. > > At the same time, I need my apm's features that ramp down the cpu and > cutoff my floppy drive when they are unused. > > Is there any way to turn off the system's propensity to suspend my system, > but retain other apm features? This is a feature of your BIOS. It may be that your "smart" battery hasn't been calibrated correctly. If you read the manual that came with your system, it probably said that the first time you used it you should take it from full charge to flat in a single session so that it could work out what was what. You can check this using the 'apm' command, which will tell you what the BIOS thinks of the current battery state. mike