From owner-freebsd-mobile Sun Dec 21 06:18:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA03948 for mobile-outgoing; Sun, 21 Dec 1997 06:18:30 -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 GAA03940 for ; Sun, 21 Dec 1997 06:18:23 -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 JAA00560 for freebsd-mobile@freebsd.org; Sun, 21 Dec 1997 09:16:54 -0500 (EST) Message-ID: <19971221091647.59950@panix.com> Date: Sun, 21 Dec 1997 09:16:47 -0500 From: "Larry S. Marso" To: freebsd-mobile@freebsd.org Subject: hot swapping floppy disk 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 If my floppy drive is not attached when FreeBSD boots up, I cannot just swap my battery or cdrom drive for the floppy later and have it recognized by the system. Any solutions? -- Larry S. Marso lsmarso@panix.com From owner-freebsd-mobile Sun Dec 21 06:36:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA04645 for mobile-outgoing; Sun, 21 Dec 1997 06:36:54 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from colossus.dyn.ml.org (root@199-170-160-225.la.inreach.net [199.107.160.225]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA04633 for ; Sun, 21 Dec 1997 06:36:50 -0800 (PST) (envelope-from dburr@POBoxes.com) Received: from control.colossus.dyn.ml.org (dburr@control.colossus.dyn.ml.org [192.160.60.1]) by colossus.dyn.ml.org (8.8.7/8.8.7) with SMTP id GAA12870; Sun, 21 Dec 1997 06:40:03 -0800 (PST) (envelope-from dburr@POBoxes.com) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 21 Dec 1997 06:38:50 -0800 (PST) Organization: Starfleet Command From: Donald Burr To: Brian Handy Subject: RE: Mail Question Cc: mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 20-Dec-97, Brian Handy wrote: >This seems like an appropriate group for this sort of mail question, but >I >could be wrong. OH WELL -- tough! :-) This very question was discussed at great length recently. Look through the mailing list archives. Unfortunately, I have forgotten which list it was discussed in (I think it was -mobile, but it oculd've been - -questions), nor do I remember the participants in the discussion. - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNJ0qQfjpixuAwagxAQFboAQAmF5YE8owCxCzVYyHd1UGVCZ5Li/X6U78 9exOi6+dlGLwOhe69o//FlLhQJMdFsYccOKKocWPg7PWiXjaqjoaTWyUDWnOzwJ5 WvKHwwD/8mvJ+CZO5aaqAt/gUHBWw+BRoU3s16xWK36IfK0LhkqRYJgVbrl2upUE XGTQQQ54WHw= =6dl9 -----END PGP SIGNATURE----- From owner-freebsd-mobile Sun Dec 21 14:42:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA03523 for mobile-outgoing; Sun, 21 Dec 1997 14:42:09 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from noether.blah.org (slmel13p17.ozemail.com.au [203.108.202.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA03516 for ; Sun, 21 Dec 1997 14:41:58 -0800 (PST) (envelope-from ada@not-enough.bandwidth.org) Received: (from ada@localhost) by noether.blah.org (8.8.7/8.8.8) id JAA23961 for mobile@freebsd.org; Mon, 22 Dec 1997 09:41:19 +1100 (EST) From: Ada Message-Id: <199712212241.JAA23961@noether.blah.org> Subject: scsi cards To: mobile@freebsd.org Date: Mon, 22 Dec 1997 09:41:18 +1100 (EST) Reply-To: ada@bsd.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 The only SCSI PCCards I can find here are all APA-1460 or clones. From what I've heard, the aic driver which is used for these has serious problems, especially driving hard disks. Is there anything which is recommended? I'm looking to house a CD-R and a HD for images in an external case. Ada -- Don't ever speak more clearly than you think... -- Niels Bohr From owner-freebsd-mobile Sun Dec 21 18:26:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA17607 for mobile-outgoing; Sun, 21 Dec 1997 18:26:42 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from colossus.dyn.ml.org (root@206-18-115-37.la.inreach.net [206.18.115.37]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA17594 for ; Sun, 21 Dec 1997 18:26:32 -0800 (PST) (envelope-from dburr@POBoxes.com) Received: from control.colossus.dyn.ml.org (dburr@control.colossus.dyn.ml.org [192.160.60.1]) by colossus.dyn.ml.org (8.8.7/8.8.7) with SMTP id SAA04664; Sun, 21 Dec 1997 18:30:29 -0800 (PST) (envelope-from dburr@POBoxes.com) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199712212241.JAA23961@noether.blah.org> Date: Sun, 21 Dec 1997 18:29:16 -0800 (PST) Organization: Starfleet Command From: Donald Burr To: ada@bsd.org Subject: RE: scsi cards Cc: mobile@freebsd.org Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 21-Dec-97, Ada wrote: >The only SCSI PCCards I can find here are all APA-1460 or clones. From >what I've heard, the aic driver which is used for these has serious >problems, especially driving hard disks. Is there anything which is >recommended? I'm looking to house a CD-R and a HD for images in an >external case. FWIW, I've used FreeBSD with both an genuine Adaptec card as well as a New Media Toast'n'Jam Sound+SCSI (which uses the same chipset) to drive a NEC 8x CD-ROM and a Iomega Jaz 1 GB removable cartridge drive, with absolutely no problems. - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNJ3QwPjpixuAwagxAQErsQQAhfgt7Zg61VLGKNsriKLs5ItiTBEVH8Lp BxywpbvvbGyaqXhIEQTzJ9FdUwu/BMI461iu3DvZijunt03xEuIUwOn8yIV3P01C jBegJSFQJBH3O99GzeK7gsEZfhfEBPDO7NCj0jjC9ktfCGBD+GacfWzJzUVML6U/ oo5nObA40CY= =PGjw -----END PGP SIGNATURE----- From owner-freebsd-mobile Sun Dec 21 20:20:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA24577 for mobile-outgoing; Sun, 21 Dec 1997 20:20:26 -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 UAA24560 for ; Sun, 21 Dec 1997 20:20:20 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id OAA00508; Mon, 22 Dec 1997 14:44:13 +1030 (CST) Message-Id: <199712220414.OAA00508@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: ada@bsd.org cc: mobile@freebsd.org Subject: Re: scsi cards In-reply-to: Your message of "Mon, 22 Dec 1997 09:41:18 +1100." <199712212241.JAA23961@noether.blah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Dec 1997 14:44:13 +1030 From: Mike Smith Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The only SCSI PCCards I can find here are all APA-1460 or clones. From > what I've heard, the aic driver which is used for these has serious > problems, especially driving hard disks. Is there anything which is > recommended? I'm looking to house a CD-R and a HD for images in an > external case. There's nothing available at the moment that will do a CD-R justice, so you are probably wasting your time. General experience suggests that feeding a CD-R requires a PCI adapter and plenty of free bandwidth, unless you fork out for one with *lots* of buffer memory. mike From owner-freebsd-mobile Sun Dec 21 20:30:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA25140 for mobile-outgoing; Sun, 21 Dec 1997 20:30:32 -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 UAA25135 for ; Sun, 21 Dec 1997 20:30:26 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id OAA00556; Mon, 22 Dec 1997 14:54:40 +1030 (CST) Message-Id: <199712220424.OAA00556@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Donald Burr cc: ada@bsd.org, mobile@freebsd.org Subject: Re: scsi cards In-reply-to: Your message of "Sun, 21 Dec 1997 18:29:16 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Dec 1997 14:54:40 +1030 From: Mike Smith Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > FWIW, I've used FreeBSD with both an genuine Adaptec card as well as a New > Media Toast'n'Jam Sound+SCSI (which uses the same chipset) to drive a NEC > 8x CD-ROM and a Iomega Jaz 1 GB removable cartridge drive, with absolutely > no problems. You should also be able to use the Iomega Jaz Traveller with the vpo driver. This is a parallel port interface, and if price is more important than speed it's a real candidate. mike From owner-freebsd-mobile Sun Dec 21 20:43:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA25738 for mobile-outgoing; Sun, 21 Dec 1997 20:43:02 -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 UAA25728 for ; Sun, 21 Dec 1997 20:42:52 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id PAA00626; Mon, 22 Dec 1997 15:05:11 +1030 (CST) Message-Id: <199712220435.PAA00626@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Larry S. Marso" cc: freebsd-mobile@freebsd.org Subject: Re: hot swapping floppy disk In-reply-to: Your message of "Sun, 21 Dec 1997 09:16:47 CDT." <19971221091647.59950@panix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Dec 1997 15:05:10 +1030 From: Mike Smith Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > If my floppy drive is not attached when FreeBSD boots up, I cannot just > swap my battery or cdrom drive for the floppy later and have it recognized > by the system. > > Any solutions? Set the flags value for fdc0 to 0x1. This is documented in the fdc(4) manpage, which I suggest you read. 8) mike From owner-freebsd-mobile Mon Dec 22 05:11:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA22175 for mobile-outgoing; Mon, 22 Dec 1997 05:11:58 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from noether.blah.org (slmel11p47.ozemail.com.au [203.108.200.63]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA22169 for ; Mon, 22 Dec 1997 05:11:51 -0800 (PST) (envelope-from ada@not-enough.bandwidth.org) Received: (from ada@localhost) by noether.blah.org (8.8.7/8.8.8) id AAA01125; Tue, 23 Dec 1997 00:09:53 +1100 (EST) From: Ada Message-Id: <199712221309.AAA01125@noether.blah.org> Subject: Re: scsi cards In-Reply-To: <199712220414.OAA00508@word.smith.net.au> from Mike Smith at "Dec 22, 97 02:44:13 pm" To: mike@smith.net.au (Mike Smith) Date: Tue, 23 Dec 1997 00:09:53 +1100 (EST) Cc: mobile@freebsd.org Reply-To: ada@bsd.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 > > The only SCSI PCCards I can find here are all APA-1460 or clones. From > > what I've heard, the aic driver which is used for these has serious > > problems, especially driving hard disks. Is there anything which is > > recommended? I'm looking to house a CD-R and a HD for images in an > > external case. > > There's nothing available at the moment that will do a CD-R justice, so > you are probably wasting your time. General experience suggests that > feeding a CD-R requires a PCI adapter and plenty of free bandwidth, > unless you fork out for one with *lots* of buffer memory. In my experience, with a slow CD-R such as mine, even the 1510 worked fine. I'm just worried about the disk aspect, though - I've heard that the aic driver can cause panics in such an instance? Ada. -- Do not condemn the judgement of another because it differs from your own. You may both be wrong. -- Dandemis From owner-freebsd-mobile Mon Dec 22 10:31:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13963 for mobile-outgoing; Mon, 22 Dec 1997 10:31:02 -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 KAA13958 for ; Mon, 22 Dec 1997 10:30:57 -0800 (PST) (envelope-from dleeds@dfacades.com) Received: (from dleeds@localhost) by inertia.dfacades.com (8.8.7/8.8.7) id KAA21889; Mon, 22 Dec 1997 10:30:52 -0800 (PST) From: Daniel Leeds Message-Id: <199712221830.KAA21889@inertia.dfacades.com> Subject: Re: scsi cards In-Reply-To: <199712212241.JAA23961@noether.blah.org> from Ada at "Dec 22, 97 09:41:18 am" To: ada@bsd.org Date: Mon, 22 Dec 1997 10:30:51 -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 > The only SCSI PCCards I can find here are all APA-1460 or clones. From > what I've heard, the aic driver which is used for these has serious > problems, especially driving hard disks. Is there anything which is > recommended? I'm looking to house a CD-R and a HD for images in an > external case. > i have an adaptec 1460 pcmcia scsi card which works just fine with freebsd 2.2.5-stable on my thinkpad. I drive 3 4 gig hard drives, a cdrom, and a DLT tape device all at the same time with not one problem. --daniel From owner-freebsd-mobile Mon Dec 22 18:39:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA21806 for mobile-outgoing; Mon, 22 Dec 1997 18:39:14 -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 SAA21801 for ; Mon, 22 Dec 1997 18:39:09 -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 VAA02986; Mon, 22 Dec 1997 21:39:02 -0500 Message-Id: <199712230239.VAA02986@duncan.cs.utk.edu> To: freebsd-mobile@freebsd.org cc: key@cs.utk.edu Subject: patch for APM suspend/resume and the "calltodo" timer list. Date: Mon, 22 Dec 1997 21:39:00 -0500 From: Ken Key Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Folks, I was holding off sending this patch until I could prove a problem I saw with select() under XF86 v331 was not related to this mod. I just had the failure occur on the unmodified kernel, so I can feel OK about posting this patch. This patch causes the "calltodo" timer list to be decremented by the amount of time that the laptop was suspending. Thus, select() calls that might have had an hour timeout will fire upon resume if it expired while the machine was suspended rather than firing at 1hr + "time suspended" since the timer was posted. My motivation for doing this was the ISC DHCP client, which uses the select() timeout for calculating T1 and T2 for lease renewal. I still have some other issues with the client, but this addresses the timeout problem. (Actually, using Paul Traina's /etc/pccard_ether that kills and restarts the DHCP client on insert - and thus resume - bypasses this issue). Adding: options APM_FIXUP_CALLTODO to the kernel config enables the patch. regards, Ken Key =====================>8 cut here 8<============================== *** sys/i386/apm/apm.c-orig Mon Dec 22 18:22:25 1997 --- sys/i386/apm/apm.c Mon Dec 22 14:55:34 1997 *************** *** 344,351 **** tmp_time = time; /* because 'time' is volatile */ timevaladd(&tmp_time, &diff_time); time = tmp_time; splx(pl); ! second = resume_time.tv_sec - suspend_time.tv_sec; hour = second / 3600; second %= 3600; minute = second / 60; --- 344,365 ---- tmp_time = time; /* because 'time' is volatile */ timevaladd(&tmp_time, &diff_time); time = tmp_time; + #ifdef APM_FIXUP_CALLTODO + /* Calculate the delta time suspended */ + timevalsub(&resume_time, &suspend_time); + /* Fixup the calltodo list with the delta time. */ + adjust_timeout_calltodo(&resume_time); + #endif /* APM_FIXUP_CALLTODOK */ splx(pl); ! #ifndef APM_FIXUP_CALLTODO ! second = resume_time.tv_sec - suspend_time.tv_sec; ! #else /* APM_FIXUP_CALLTODO */ ! /* ! * We've already calculated resume_time to be the delta between ! * the suspend and the resume. ! */ ! second = resume_time.tv_sec; ! #endif /* APM_FIXUP_CALLTODO */ hour = second / 3600; second %= 3600; minute = second / 60; *** sys/kern/kern_clock.c-orig Mon Dec 22 18:22:47 1997 --- sys/kern/kern_clock.c Mon Dec 22 15:08:24 1997 *************** *** 1290,1292 **** --- 1290,1360 ---- pps_intcnt++; } #endif /* PPS_SYNC */ + + #ifdef APM_FIXUP_CALLTODO + /* + * Adjust the kernel calltodo timeout list. This routine is used after + * an APM resume to recalculate the calltodo timer list values with the + * number of hz's we have been sleeping. The next hardclock() will detect + * that there are fired timers and run softclock() to execute them. + * + * Please note, I have not done an exhaustive analysis of what code this + * might break. I am motivated to have my select()'s and alarm()'s that + * have expired during suspend firing upon resume so that the applications + * which set the timer can do the maintanence the timer was for as close + * as possible to the originally intended time. Testing this code for a + * week showed that resuming from a suspend resulted in 22 to 25 timers + * firing, which seemed independant on whether the suspend was 2 hours or + * 2 days. Your milage may vary. - Ken Key + */ + void + adjust_timeout_calltodo(time_change) + struct timeval *time_change; + { + register struct callout *p, *t; + unsigned long delta_ticks; + int s; + int num_fired; + + /* + * How many ticks were we asleep? + * (stolen from hzto()). + */ + if (time_change->tv_sec < 0) { + /* Don't do anything */ + return; + } + else if (time_change->tv_sec <= LONG_MAX / 1000000) { + delta_ticks = (time_change->tv_sec * 1000000 + time_change->tv_usec + (tick - 1)) / tick + 1; + } + else if (time_change->tv_sec <= LONG_MAX / hz) { + delta_ticks = time_change->tv_sec * hz + + (time_change->tv_usec + (tick - 1)) / tick + 1; + } + else { + delta_ticks = LONG_MAX; + } + if (delta_ticks > INT_MAX) + delta_ticks = INT_MAX; + + /* + * Now rip through the timer calltodo list looking for timers to expire. + */ + + /* don't collide with softclock() */ + s = splhigh(); + for (p = calltodo.c_next; p != NULL; p = p->c_next) { + p->c_time -= delta_ticks; + + /* Break if the timer had more time on it than delta_ticks */ + if (p->c_time > 0) + break; + + /* take back the ticks the timer didn't use (p->c_time <= 0). */ + delta_ticks = -p->c_time; + } + splx(s); + + return; + } + #endif /* APM_FIXUP_CALLTODO */ From owner-freebsd-mobile Mon Dec 22 19:05:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA23155 for mobile-outgoing; Mon, 22 Dec 1997 19:05:15 -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 TAA23144 for ; Mon, 22 Dec 1997 19:05:06 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id NAA00266; Tue, 23 Dec 1997 13:29:13 +1030 (CST) Message-Id: <199712230259.NAA00266@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: ada@bsd.org cc: mike@smith.net.au (Mike Smith), mobile@freebsd.org Subject: Re: scsi cards In-reply-to: Your message of "Tue, 23 Dec 1997 00:09:53 +1100." <199712221309.AAA01125@noether.blah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Dec 1997 13:29:11 +1030 From: Mike Smith Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > There's nothing available at the moment that will do a CD-R justice, so > > you are probably wasting your time. General experience suggests that > > feeding a CD-R requires a PCI adapter and plenty of free bandwidth, > > unless you fork out for one with *lots* of buffer memory. > In my experience, with a slow CD-R such as mine, even the 1510 worked > fine. Ah, OK. I was presuming you were talking about buying one. > I'm just worried about the disk aspect, though - I've heard that > the aic driver can cause panics in such an instance? The aic driver doesn't handle error conditions very well, no. mike From owner-freebsd-mobile Tue Dec 23 07:26:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA13454 for mobile-outgoing; Tue, 23 Dec 1997 07:26:02 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from chuck.schiele-ct.de (chuck.schiele-ct.de [193.141.27.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA13445 for ; Tue, 23 Dec 1997 07:25:59 -0800 (PST) (envelope-from br@schiele-ct.de) Received: from schiele-ct.de (localhost.schiele-ct.de [127.0.0.1]) by chuck.schiele-ct.de (8.8.7/8.8.7) with ESMTP id QAA27835 for ; Tue, 23 Dec 1997 16:29:59 +0100 (CET) (envelope-from br@schiele-ct.de) Message-Id: <199712231529.QAA27835@chuck.schiele-ct.de> To: freebsd-mobile@freebsd.org Subject: Re: scsi cards In-reply-to: Your message of "Mon, 22 Dec 1997 20:34:43 +0100." <199712221830.KAA21889@inertia.dfacades.com> Date: Tue, 23 Dec 1997 16:29:59 +0100 From: Bernd Rosauer Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Daniel Leeds: > i have an adaptec 1460 pcmcia scsi card which works just fine with > freebsd 2.2.5-stable on my thinkpad. > > I drive 3 4 gig hard drives, a cdrom, and a DLT tape device all at the > same time with not one problem. Last week I read the online description of this card at www.adaptec.com. They wrote that this card only drives up to _three_ SCSI devices. This fact was the reason why I did not purchase this card. I need to drive a SCSI system case housing six SCSI devices. From what you claim I would conclude now that my needs would be fulfilled by this card. Right? Is there anyone else driving more than three devices with one Adaptec SlimSCSI card? -Bernd From owner-freebsd-mobile Tue Dec 23 16:36:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA24740 for mobile-outgoing; Tue, 23 Dec 1997 16:36:11 -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 QAA24732 for ; Tue, 23 Dec 1997 16:36:05 -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 SAA00549; Tue, 23 Dec 1997 18:20:47 -0500 Message-Id: <199712232320.SAA00549@duncan.cs.utk.edu> To: Ken Key cc: freebsd-mobile@freebsd.org Subject: Forgot patch of function declaration for my APM suspend patch. From: Ken Key In-reply-to: Your message of Mon, 22 Dec 1997 21:39:00 -0500. <199712230239.VAA02986@duncan.cs.utk.edu> Date: Tue, 23 Dec 1997 18:20:47 -0500 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I realized late last night that I forgot to include the patched sys/sys/systm.h that adds the function declaration for adjust_timeout_calltodo() in my message yesterday. After sitting on the deltas for a few weeks, that one had slipped my mind. Fortunately, the kernel compiled OK without it. I've included it below for completeness. K^2 -- Ken Key (key@cs.utk.edu) Univ. of Tennessee, Knoxville =====================>8 cut here 8<============================== *** sys/sys/systm.h-orig Tue Dec 23 09:42:04 1997 --- sys/sys/systm.h Tue Dec 23 09:36:33 1997 *************** *** 137,142 **** --- 137,146 ---- void hardupdate __P((long)); void hardpps __P((struct timeval *tvp, long usec)); + #ifdef APM_FIXUP_CALLTODO + void adjust_timeout_calltodo __P((struct timeval *time_change)); + #endif /* APM_FIXUP_CALLTODO */ + #include /* Initialize the world */ From owner-freebsd-mobile Tue Dec 23 17:37:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA29018 for mobile-outgoing; Tue, 23 Dec 1997 17:37:46 -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 RAA29011 for ; Tue, 23 Dec 1997 17:37:42 -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 SAA02329; Tue, 23 Dec 1997 18:37:41 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA05218; Tue, 23 Dec 1997 18:37:40 -0700 Date: Tue, 23 Dec 1997 18:37:40 -0700 Message-Id: <199712240137.SAA05218@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ken Key Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Forgot patch of function declaration for my APM suspend patch. In-Reply-To: <199712232320.SAA00549@duncan.cs.utk.edu> References: <199712230239.VAA02986@duncan.cs.utk.edu> <199712232320.SAA00549@duncan.cs.utk.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I realized late last night that I forgot to include the patched > sys/sys/systm.h that adds the function declaration for > adjust_timeout_calltodo() in my message yesterday. After sitting on the > deltas for a few weeks, that one had slipped my mind. Fortunately, the > kernel compiled OK without it. I've included it below for completeness. I just committed it, thanks! Nate From owner-freebsd-mobile Wed Dec 24 09:13:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA18599 for mobile-outgoing; Wed, 24 Dec 1997 09:13:34 -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 JAA18594 for ; Wed, 24 Dec 1997 09:13:30 -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 MAA00786; Wed, 24 Dec 1997 12:13:20 -0500 Message-Id: <199712241713.MAA00786@duncan.cs.utk.edu> To: freebsd-mobile@freebsd.org cc: key@cs.utk.edu Subject: More on APM suspened/calltodo patch. Date: Wed, 24 Dec 1997 12:13:19 -0500 From: Ken Key Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Folks, I failed to point out in my patch that it is for 2.2-STABLE (circa 2.2.5-RELEASE). In -CURRENT, the timer setup has completely changed and the patch is not appropriate. Sorry if there was any confusion. regards, K^2 University of Tennessee, Knoxville From owner-freebsd-mobile Fri Dec 26 14:09:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08626 for mobile-outgoing; Fri, 26 Dec 1997 14:09:14 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from grizzly.fas.com (chs0295.awod.com [208.140.97.55]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA08620 for ; Fri, 26 Dec 1997 14:09:06 -0800 (PST) (envelope-from stanb@awod.com) Message-Id: <199712262209.OAA08620@hub.freebsd.org> Received: by grizzly.fas.com ($Revision: 1.37.109.23 $/16.2) id AA255944137; Fri, 26 Dec 1997 17:08:57 -0500 Subject: Help with alternate network and ppp setup To: freebsd-mobile@freebsd.org (FreeBSD Mobile List) Date: Fri, 26 Dec 1997 17:08:56 -0500 (EST) From: "Stan Brown" X-Mailer: ELM [version 2.4 PL24] 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 I am having a problem getting my FreeBSD laptop to work exactly the way I want it to. Here is the situation. The machine has a PCMCIA etherent card in it and might find it self connected to any one of 3 different networks. In addation I want to be able to dial into my home network and connect to it using PPP. Some kind soul sent me a small perl script that I have made a few minor changes to for the multi netwrk setup here it is. #!/usr/local/bin/perl %gateway = ('205.159.77.233' => { gw => '205.159.77.234', dns => ['205.159.77.240', '208.140.99.9', '198.81.225.1'], dom => 'fas.com' }, '222.198.37.141' => { gw => '222.198.37.254', dns => ['192.1.37.20'], dom => 'westvaco.com' }, '192.168.0.3 -link0' => { gw => '192.168.0.1', dns => ['192.168.0.1'], dom => 'westvaco.com' }, ); `route delete default 2>&1 > /dev/null`; foreach $key (keys(%gateway)) { $thiskey = $key; $up=1; `ifconfig ep0 inet $key netmask 0xffffff00 link1`; unless (system("ping -c 1 $gateway{$key}{gw} > /dev/null")) { last; } print "Cannot ping $gateway{$key}{gw}\n"; $up=0; } if($up) { `route add default $gateway{$thiskey}{gw}`; open RESOLVFILE, "> /etc/resolv.conf"; print RESOLVFILE "domain $gateway{$thiskey}{dom}\n"; foreach $ipnum (@{$gateway{$thiskey}{dns}}) { print RESOLVFILE "nameserver $ipnum\n"; } close RESOLVFILE; if($gateway{$thiskey}{dom} eq 'fas.com') { `ypbind beach`; } print "Configured for network $gateway{$thiskey}{dom}\n"; } else { print "Cannot find a known network\n"; } This script is invoked from thee pccard script. Y have put NO in the sysconfig file for the functions handled by this script. This seems to work OK. Primarly I have tested it on my home network. Now I am trying to get the machine to dial up and do aPPP link to one of the computers on my home network. I have the chat script and all that working and can get a PPP prompt. I can then telnet to the machine that I have conected to. At this point, I can't get to anu other machines on my network, much less the outsde world. Also somehow in hacking on this I have reached the point where when brought up on my local network rwho and ruptime don't work on this machine. As a matter of fact, It sees thother machines, but not itslef! Here is the output of netstat -r and ifconfig -a after booting on my local network. Script started on Fri Dec 26 17:05:39 1997 ]0;stan@polar.fas.com;/home/stanstan@polar.fas.com:/home/stan $ netstat -r Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default koala UGSc 5 33 ep0 localhost localhost UH 2 134 lo0 205.159.77 link#5 UC 0 0 polar 0:20:af:c7:2d:af UHLW 0 9 lo0 koala link#5 UHLW 6 1 kodiak 8:0:9:78:ea:56 UHLW 2 13977 ep0 857 grizzly 8:0:9:11:e5:a UHLW 4 34881 ep0 857 205.159.77.255 ff:ff:ff:ff:ff:ff UHLWb 0 2 ep0 ]0;stan@polar.fas.com;/home/stanstan@polar.fas.com:/home/stan $ ifconfig -a lp0: flags=8810 mtu 1500 tun0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 ep0: flags=a843 mtu 1500 inet 205.159.77.233 netmask 0xffffff00 broadcast 205.159.77.255 ether 00:20:af:c7:2d:af ]0;stan@polar.fas.com;/home/stanstan@polar.fas.com:/home/stan $ WhatI think* is going on here, is that there are still some remnants of the attempts to talk to the non-exustent betworsk. Does this make sense? Has anyone else worked through this? Script done on Fri Dec 26 17:05:50 1997 -- Stan Brown stanb@netcom.com 770-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1997 Stan Brown. Redistribution via the Microsoft Network is prohibited. From owner-freebsd-mobile Fri Dec 26 15:11:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA11857 for mobile-outgoing; Fri, 26 Dec 1997 15:11:49 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from mail.nomadix.com (mail.nomadix.com [205.147.49.199]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA11843 for ; Fri, 26 Dec 1997 15:11:27 -0800 (PST) (envelope-from gdicus@nomadix.com) Received: from gdicus.nomadix.com (nomad7.nomadix.com [205.147.49.207]) by mail.nomadix.com (8.8.3/8.7.2) with ESMTP id PAA09619 for ; Fri, 26 Dec 1997 15:09:43 -0800 (PST) Message-Id: <199712262309.PAA09619@mail.nomadix.com> From: "Glenn Lee Dicus" To: "Mobile FreeBSD" Subject: PC Card Driver "fe0" Date: Fri, 26 Dec 1997 15:12:49 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1162 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to attach a driver to slot A of a pc compatible evaluation board. However, I recieve a "Nomad_One cardd[35]: driver allocation failed for EAGLE Technology" error on boot up. The dump that I get is the following: *Dec 26 12:24:10 Nomad_One /kernel: fe0: probing 0 at 0x120 *Dec 26 12:24:11 Nomad_One /kernel: fe0: probing 1 at 0x120 *Dec 26 12:24:11 Nomad_One /kernel: fe0: probe (0x120) for ATI *Dec 26 12:24:11 Nomad_One /kernel: fe0: registers, * DLCR = 46 9f 46 9f 46 9f 46 9f, * BMPR = xx xx 46 9f 46 9f 46 9f, * asic = 46 9f 46 9f 46 9f 46 9f + 46 9f 46 9f 46 9f 46 9f *Dec 26 12:24:11 Nomad_One /kernel: fe0: probing 2 at 0x120 *Dec 26 12:24:11 Nomad_One /kernel: fe0: probe (0x120) for MBH *Dec 26 12:24:11 Nomad_One /kernel: fe0: registers, * DLCR = 46 9f 46 9f 46 9f 46 9f, * BMPR = xx xx 46 9f 46 9f 46 9f, * asic = 46 9f 46 9f 46 9f 46 9f + 46 9f 46 9f 46 9f 46 9f *Dec 26 12:24:11 Nomad_One /kernel: Probe Port:0,Value:ff,Mask:9.Bits:0 *Dec 26 12:24:11 Nomad_One /kernel: fe0: probing 3 at 0x120 *Dec 26 12:24:11 Nomad_One /kernel: Probe Port:2,Value:ff,Mask:70.Bits:0 *Dec 26 12:24:11 Nomad_One /kernel: fe0 not found at 0x120 And towards the end of boot-up, the code apparently tries to initialize the pccard again using the same code with different results according to the dump: *Dec 26 12:24:25 Nomad_One /ernel: Start Probe *Dec 26 12:24:25 Nomad_One /kernel: fe0: probing 0 at 0x120 *Dec 26 12:24:25 Nomad_One /kernel: fe0: probing 1 at 0x120 *Dec 26 12:24:25 Nomad_One /kernel: fe0: probe (0x120) for ATI *Dec 26 12:24:25 Nomad_One /kernel: fe0: registers, * DLCR = ff ff ff ff ff ff ff ff, * BMPR = xx xx ff ff ff ff ff ff, * asic = ff ff ff ff ff ff ff ff + ff ff ff ff ff ff ff ff *Dec 26 12:24:25 Nomad_One /kernel: fe0: probing 2 at 0x120 *Dec 26 12:24:25 Nomad_One /kernel: fe0: probe (0x120) for MBH *Dec 26 12:24:25 Nomad_One /kernel: fe0: registers, * DLCR = ff ff ff ff ff ff ff ff, * BMPR = xx xx ff ff ff ff ff ff, * asic = ff ff ff ff ff ff ff ff + ff ff ff ff ff ff ff ff *Dec 26 12:24:25 Nomad_One /kernel: Probe Port:0,Value:ff,Mask:9.Bits:0 *Dec 26 12:24:25 Nomad_One /kernel: fe0: probing 3 at 0x120 *Dec 26 12:24:25 Nomad_One /kernel: Probe Port:2,Value:ff,Mask:70.Bits:0 Are these valid values? If so, what does this mean? thanks in advance glenn From owner-freebsd-mobile Sat Dec 27 09:19:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA06204 for mobile-outgoing; Sat, 27 Dec 1997 09:19:04 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA06198 for ; Sat, 27 Dec 1997 09:18:58 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.4) with UUCP id RAA07183; Sat, 27 Dec 1997 17:17:11 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 27 Dec 1997 17:06:06 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199712150557.OAA02926@afs.ntc.mita.keio.ac.jp> References: Your message of "Sun, 14 Dec 1997 21:17:57 -0700". <199712150417.VAA03645@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 27 Dec 1997 17:04:49 +0000 To: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) From: Bob Bishop Subject: Re: Multifunction PC-card support Cc: mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, This information may help a bit. I have a Grey Cell GCS3000 modem/ethernet card here, which I think is a well-behaved multifunction card. I have ethernet working on ed1 (it's a NE2000 clone) using the following pccard.conf entry: -------------------------------------------------------------------------- card "Grey Cell" "GCS3000" config 0x28 "ed1" 10 insert echo Grey Cell Ethernet inserted insert /etc/pccard_ether ed1 remove echo Grey Cell Ethernet removed remove /sbin/ifconfig ed1 delete -------------------------------------------------------------------------- ...but I haven't managed to get the modem working. Here is the output of pccardc dumpcis; note that the first address in each config entry looks like an ed ethernet port and the second looks like a serial port. Also that tuple 20 (code 0x21) shows "Multifunction card": -------------------------------------------------------------------------- Configuration data for card in slot 1 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: dc 00 ff Common memory device information: Device number 1, type Function specific, WPS = ON Speed = 100nS, Memory block size = 512b, 1 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 3 000: 49 00 ff Attribute memory device information: Device number 1, type EEPROM, WPS = ON Speed = 250nS, Memory block size = 512b, 1 units Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 43 01 41 33 PCMCIA ID = 0x143, OEM ID = 0x3341 Tuple #4, code = 0x15 (Version 1 info), length = 30 000: 04 01 47 72 65 79 20 43 65 6c 6c 00 47 43 53 33 010: 30 30 30 00 47 6f 6c 64 20 33 00 31 00 ff Version = 4.1, Manuf = [Grey Cell],card vers = [GCS3000] Addit. info = [Gold 3],[1] Tuple #5, code = 0x1a (Configuration map), length = 5 000: 01 2f f8 03 03 Reg len = 2, config register addr = 0x3f8, last config = 0x2f Registers: XX------ Tuple #6, code = 0x1b (Configuration entry), length = 26 000: e4 81 9d 3f 55 4d 5d 86 76 36 e6 46 fc 24 ca 61 010: 00 03 1f f8 02 07 30 38 9e 08 Config index = 0x24(default) Interface byte = 0x81 (I/O) wait signal supported Vcc pwr: Nominal operating supply voltage: 5 x 1V Minimum operating supply voltage: 4.5 x 1V Maximum operating supply voltage: 5.5 x 1V Continuous supply current: 1 x 100mA, ext = 0x76 Max current average over 1 second: 3 x 100mA Max current average over 10 ms: 6 x 100mA, ext = 0x46 Wait scale Speed = 1.5 x 10 us Card decodes 4 address lines, 8 Bit I/O only IRQ modes: Level IRQ level = 4 Max twin cards = 2 Misc attr: (Audio-BVD2) (Ext byte = 0x61) Tuple #7, code = 0x1b (Configuration entry), length = 10 000: 25 08 ca 61 20 03 1f f8 02 07 Config index = 0x25 Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x320 block length = 0x20 I/O address # 2: block start = 0x2f8 block length = 0x8 Tuple #8, code = 0x1b (Configuration entry), length = 10 000: 26 08 ca 61 40 03 1f f8 02 07 Config index = 0x26 Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x340 block length = 0x20 I/O address # 2: block start = 0x2f8 block length = 0x8 Tuple #9, code = 0x1b (Configuration entry), length = 10 000: 27 08 ca 61 60 03 1f f8 02 07 Config index = 0x27 Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x360 block length = 0x20 I/O address # 2: block start = 0x2f8 block length = 0x8 Tuple #10, code = 0x1b (Configuration entry), length = 10 000: 28 08 ca 61 00 03 1f e8 03 07 Config index = 0x28 Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x300 block length = 0x20 I/O address # 2: block start = 0x3e8 block length = 0x8 Tuple #11, code = 0x1b (Configuration entry), length = 10 000: 29 08 ca 61 20 03 1f e8 03 07 Config index = 0x29 Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x320 block length = 0x20 I/O address # 2: block start = 0x3e8 block length = 0x8 Tuple #12, code = 0x1b (Configuration entry), length = 10 000: 2a 08 ca 61 40 03 1f e8 03 07 Config index = 0x2a Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x340 block length = 0x20 I/O address # 2: block start = 0x3e8 block length = 0x8 Tuple #13, code = 0x1b (Configuration entry), length = 10 000: 2b 08 ca 61 60 03 1f e8 03 07 Config index = 0x2b Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x360 block length = 0x20 I/O address # 2: block start = 0x3e8 block length = 0x8 Tuple #14, code = 0x1b (Configuration entry), length = 10 000: 2c 08 ca 61 00 03 1f e8 02 07 Config index = 0x2c Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x300 block length = 0x20 I/O address # 2: block start = 0x2e8 block length = 0x8 Tuple #15, code = 0x1b (Configuration entry), length = 10 000: 2d 08 ca 61 20 03 1f e8 02 07 Config index = 0x2d Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x320 block length = 0x20 I/O address # 2: block start = 0x2e8 block length = 0x8 Tuple #16, code = 0x1b (Configuration entry), length = 10 000: 2e 08 ca 61 40 03 1f e8 02 07 Config index = 0x2e Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x340 block length = 0x20 I/O address # 2: block start = 0x2e8 block length = 0x8 Tuple #17, code = 0x1b (Configuration entry), length = 10 000: 2f 08 ca 61 60 03 1f e8 02 07 Config index = 0x2f Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x360 block length = 0x20 I/O address # 2: block start = 0x2e8 block length = 0x8 Tuple #18, code = 0x14 (No link), length = 0 Tuple #19, code = 0x40 (Version 2 Info), length = 38 000: 00 00 00 00 00 00 00 00 01 47 72 65 79 20 43 65 010: 6c 6c 20 53 79 73 74 65 6d 73 20 4c 74 64 00 47 020: 6f 6c 64 20 33 00 Tuple #20, code = 0x21 (Functional ID), length = 2 000: 00 00 Multifunction card Tuple #21, code = 0xff (Terminator), length = 0 -------------------------------------------------------------------------- Note that no serial interface or modem capabilities are visible. I can dump off parts of the attribute memory if that will help you, but it looks rather different from your Mariner card. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-mobile Sat Dec 27 12:35:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA16617 for mobile-outgoing; Sat, 27 Dec 1997 12:35:06 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from hermes (hermes.uninet.net.mx [200.33.146.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA16599 for ; Sat, 27 Dec 1997 12:35:00 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from mc.mexcom.net by hermes (SMI-8.6/SMI-SVR4) id OAA09478; Sat, 27 Dec 1997 14:37:45 -0600 Message-ID: <34A5677A.41C67EA6@ver1.telmex.net.mx> Date: Sat, 27 Dec 1997 14:39:22 -0600 From: eculp Organization: MexCom X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-971226-SNAP i386) MIME-Version: 1.0 To: mobile@FreeBSD.ORG Subject: Pccard configuration Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have just installed 3.0-971226-SNAP on my TI laptop with ppp. I tried to install my 3C589B ethernet adapter. I am confused with rc.pccard, pccard.conf and the kernel configuration. Should the card driver be compiled in the kernel? Should I use the zp0 or ep0? I currently use only the following lines in the kernel configuration. What am I missing? controller card0 controller pcic0 at card? controller pcic1 at card? Where can I get more information? I have done searches in freebsd.org, but haven't found the answers. Thank you, ed