From owner-freebsd-doc Tue Feb 13 00:25:36 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA21255 for doc-outgoing; Tue, 13 Feb 1996 00:25:36 -0800 (PST) Received: from test.yamagiwa.co.jp (test.yamagiwa.co.jp [202.248.143.138]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA21247 for ; Tue, 13 Feb 1996 00:25:27 -0800 (PST) Received: (from root@localhost) by test.yamagiwa.co.jp (8.6.12/8.6.12) id CAA00231; Wed, 14 Feb 1996 02:26:28 +0900 Date: Wed, 14 Feb 1996 02:26:28 +0900 Message-Id: <199602131726.CAA00231@test.yamagiwa.co.jp> To: doc@freebsd.org X-URL: mailto:doc@freebsd.org X-Mailer: Lynx, Version 2-4-2 X-Personal_name: matt From: matt@yamagiwa.co.jp Subject: mailto:doc@freebsd.org Sender: owner-doc@freebsd.org Precedence: bulk Hi! From owner-freebsd-doc Tue Feb 13 06:23:07 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA13471 for doc-outgoing; Tue, 13 Feb 1996 06:23:07 -0800 (PST) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA13453 for ; Tue, 13 Feb 1996 06:23:01 -0800 (PST) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id PAA01136 for freebsd-doc@FreeBSD.org; Tue, 13 Feb 1996 15:22:46 +0100 Message-Id: <199602131422.PAA01136@nixpbe.pdb.sni.de> Subject: I had mail configuration problems... To: hackers@FreeBSD.org (Hackers; FreeBSD), freebsd-doc@FreeBSD.org (FreeBSD Documenters) Date: Tue, 13 Feb 96 15:23:08 MET From: Greg Lehey X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-doc@FreeBSD.org Precedence: bulk I've just recovered from a system configuration error here at SNI. If you sent me mail during the last 24 hours, it probably bounced. If you send it again, I hope it won't. Greg From owner-freebsd-doc Tue Feb 13 07:34:18 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA17669 for doc-outgoing; Tue, 13 Feb 1996 07:34:18 -0800 (PST) Received: from fslg8.fsl.noaa.gov (fslg8.fsl.noaa.gov [137.75.131.171]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA17662 for ; Tue, 13 Feb 1996 07:34:13 -0800 (PST) Received: by fslg8.fsl.noaa.gov (5.57/Ultrix3.0-C) id AA13782; Tue, 13 Feb 96 09:34:11 -0600 Received: by emu.fsl.noaa.gov (1.38.193.4/SMI-4.1 (1.38.193.4)) id AA03486; Tue, 13 Feb 1996 08:34:10 -0700 Date: Tue, 13 Feb 1996 08:34:10 -0700 From: kelly@fsl.noaa.gov (Sean Kelly) Message-Id: <9602131534.AA03486@emu.fsl.noaa.gov> To: matt@yamagiwa.co.jp Cc: doc@freebsd.org In-Reply-To: <199602131726.CAA00231@test.yamagiwa.co.jp> (matt@yamagiwa.co.jp) Subject: Re: mailto:doc@freebsd.org Sender: owner-doc@freebsd.org Precedence: bulk >>>>> "matt" == matt writes: matt> Hi! Hello. -- Sean Kelly NOAA Forecast Systems Laboratory, Boulder Colorado USA My roommate got a pet elephant. Then it got lost. It's in the apartment somewhere. -- Steven Wright From owner-freebsd-doc Tue Feb 13 19:16:18 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA00606 for doc-outgoing; Tue, 13 Feb 1996 19:16:18 -0800 (PST) Received: from ecc-mail.hongo.ecc.u-tokyo.ac.jp (ecc-as06.hongo.ecc.u-tokyo.ac.jp [130.69.248.26]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA00599 for ; Tue, 13 Feb 1996 19:16:15 -0800 (PST) Received: from [130.69.160.17] (t50516@[130.69.160.17]) by ecc-mail.hongo.ecc.u-tokyo.ac.jp (8.6.9+2.4W/3.3W95032410) with SMTP id MAA17108 for ; Wed, 14 Feb 1996 12:16:05 +0900 Message-Id: <199602140316.MAA17108@ecc-mail.hongo.ecc.u-tokyo.ac.jp> X-Authentication-Warning: ecc-as06.hongo.ecc.u-tokyo.ac.jp: Host [130.69.160.17] didn't use HELO protocol To: doc@freebsd.org Subject: Let me Nice jobs... Date: Wed, 14 Feb 1996 12:16:04 +0900 From: Yukihiro Nakai Sender: owner-doc@freebsd.org Precedence: bulk Hello. I am a FreeBSD user at japan. I am very interested in release free unix. Is there anything I can help that? I would like to maintain documents (HTML or so), especially those transration into Japanese. Yukihiro Nakai Univercity Of Tokyo, Department of EEICE t50516@hongo.ecc.u-tokyo.ac.jp From owner-freebsd-doc Wed Feb 14 07:32:18 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA17741 for doc-outgoing; Wed, 14 Feb 1996 07:32:18 -0800 (PST) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA17725 for ; Wed, 14 Feb 1996 07:32:07 -0800 (PST) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id QAA17350 for freebsd-doc@FreeBSD.org; Wed, 14 Feb 1996 16:31:56 +0100 Message-Id: <199602141531.QAA17350@nixpbe.pdb.sni.de> Subject: Confused!!!! (fwd) To: hackers@FreeBSD.org (Hackers; FreeBSD) Date: Wed, 14 Feb 96 16:27:35 MET From: Greg Lehey Cc: freebsd-doc@FreeBSD.org (FreeBSD Documenters), mollers.pad@sni.de X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-doc@FreeBSD.org Precedence: bulk Forwarded message: > From: Frank J Estremera > > I am so confused as to how to boot FreeBSD from a boot manager, while on a > second drive. I have an internal IDE drive running Windows95. I also have a > secondary SCSI drive (device 0), totally devoted to FreeBSD. I do have > FreeBSD loaded on it, but when I installed FreeBSD, and selected BootEasy > as the boot manager, The operating system could not be found when booting to > Windows95 (primary drive). I deinstalled BootEasy and installed System > Commander as my boot manager. It recognized the SCSI drive as having FreeBSD > loaded on it, but when selected, System Commander tells me that the boot block > is missing on this device. The only way that I can boot FreeBSD is to insert > the install diskette in the A drive, boot from it, and when the BOOT prompt > appears, pointing it to hd(1,a)/kernel (I think). Just for laughs I did a > disklabel -B sd0 to maybe try to force a boot block on the SCSI device, but > to no avail (unless I am totally out in left field, which is likely). What > am I missing??? Why is my operating system under Windows95 being clobbered?? > (I then have to do an fdisk from diskette to activate my C: partition again). > Please shine a flashlight on my face and enlighten me! Could it be that the lack of replies to this message is the result of everybody else being confused as well? I currently can't get near a running FreeBSD system, and I honestly don't know a good answer, but I get the feeling that we have a bug which manifests itself when using booteasy when FreeBSD is not on the first drive. I've had another report of this kind of problem here at SNI, and in this case I'm pretty sure it wasn't user error. Any comments from others? Greg From owner-freebsd-doc Wed Feb 14 09:04:25 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA00276 for doc-outgoing; Wed, 14 Feb 1996 09:04:25 -0800 (PST) Received: from lightning.Stanford.EDU (tip-mp7-ncs-4.Stanford.EDU [36.173.0.131]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA00257 Wed, 14 Feb 1996 09:04:15 -0800 (PST) Received: (from bora@localhost) by lightning.Stanford.EDU (8.6.12/8.6.12) id JAA00215; Wed, 14 Feb 1996 09:00:49 -0800 Date: Wed, 14 Feb 1996 09:00:49 -0800 (PST) From: Bora Akyol X-Sender: bora@lightning.Stanford.EDU To: Greg Lehey cc: hackers@freebsd.org, FreeBSD Documenters , mollers.pad@sni.de Subject: Re: Confused!!!! (fwd) In-Reply-To: <199602141531.QAA17350@nixpbe.pdb.sni.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk Here is what I did when I had the same setup. I used os-bs beta version that is on the Walnut Creek CDROM. I made sure that the SCSI drive is seen by dos (does not need to be formatted). Then, I used os-bs beta version to create a boot menu. When it was done , everything worked. ONe thing that needs to be done is to hard wire the device id for the scsi drive for the kernel. Otherwise, it automatically assigns an ID at boot time to the scsi drive and it can't find the root partition when it comes to fsck at boot. After you do hard wire the drive in the kernel config DO not forget the change the fstab file. Hope this helps, if anyone has specific questions email me at akyol@leland.stanford.edu Bora On Wed, 14 Feb 1996, Greg Lehey wrote: > Forwarded message: > > > From: Frank J Estremera > > > > I am so confused as to how to boot FreeBSD from a boot manager, while on a > > second drive. I have an internal IDE drive running Windows95. I also have a > > secondary SCSI drive (device 0), totally devoted to FreeBSD. I do have > > FreeBSD loaded on it, but when I installed FreeBSD, and selected BootEasy > > as the boot manager, The operating system could not be found when booting to > > Windows95 (primary drive). I deinstalled BootEasy and installed System > > Commander as my boot manager. It recognized the SCSI drive as having FreeBSD > > loaded on it, but when selected, System Commander tells me that the boot block > > is missing on this device. The only way that I can boot FreeBSD is to insert > > the install diskette in the A drive, boot from it, and when the BOOT prompt > > appears, pointing it to hd(1,a)/kernel (I think). Just for laughs I did a > > disklabel -B sd0 to maybe try to force a boot block on the SCSI device, but > > to no avail (unless I am totally out in left field, which is likely). What > > am I missing??? Why is my operating system under Windows95 being clobbered?? > > (I then have to do an fdisk from diskette to activate my C: partition again). > > Please shine a flashlight on my face and enlighten me! > > Could it be that the lack of replies to this message is the result of > everybody else being confused as well? I currently can't get near a > running FreeBSD system, and I honestly don't know a good answer, but I > get the feeling that we have a bug which manifests itself when using > booteasy when FreeBSD is not on the first drive. I've had another > report of this kind of problem here at SNI, and in this case I'm > pretty sure it wasn't user error. Any comments from others? > > Greg > > > From owner-freebsd-doc Wed Feb 14 09:56:58 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA03474 for doc-outgoing; Wed, 14 Feb 1996 09:56:58 -0800 (PST) Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA03453 Wed, 14 Feb 1996 09:56:52 -0800 (PST) Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id MAA14830; Wed, 14 Feb 1996 12:56:20 -0500 Date: Wed, 14 Feb 1996 12:56:20 -0500 (EST) From: John Fieber X-Sender: jfieber@fieber-john.campusview.indiana.edu To: Greg Lehey cc: hackers@freebsd.org, FreeBSD Documenters , mollers.pad@sni.de, festremera@shell.monmouth.com Subject: Re: Confused!!!! (fwd) In-Reply-To: <199602141531.QAA17350@nixpbe.pdb.sni.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Wed, 14 Feb 1996, Greg Lehey wrote: > Forwarded message: > > > From: Frank J Estremera > > > > I am so confused as to how to boot FreeBSD from a boot manager, while on a > > second drive. I have an internal IDE drive running Windows95. I also have a > > secondary SCSI drive (device 0), totally devoted to FreeBSD. I do have Sounds like my setup, minus the Windows95. > Could it be that the lack of replies to this message is the result of > everybody else being confused as well? I currently can't get near a > running FreeBSD system, and I honestly don't know a good answer, but I > get the feeling that we have a bug which manifests itself when using > booteasy when FreeBSD is not on the first drive. I've had another > report of this kind of problem here at SNI, and in this case I'm > pretty sure it wasn't user error. Any comments from others? My first drive is an IDE and is dedicated to the various lesser operating systems (currently DOS, Windoze, and OS/2). The second drive (SCSI ID 0) is FreeBSD. The only problem I had booting of the second drive was figuring out that I had to type hd0 at the boot prompt or FreeBSD would get confused about where its root partition was. (I've since made new bootblocks with this as the default. I've also since given up booteasy for the OS/2 bootmanager.) My understanding is that failing to find bootblocks is frequently evidence of geometry translation problems. Also, I have an Adaptec 1542C and to boot from the second drive, I had to enable the BIOS on the controller, otherwize booteasy wouldn't detect the existance of the SCSI drive. That is about as much light as I can shed on the issue. -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-doc Wed Feb 14 14:49:46 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA19965 for doc-outgoing; Wed, 14 Feb 1996 14:49:46 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA19960 Wed, 14 Feb 1996 14:49:40 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA00886; Wed, 14 Feb 1996 15:48:36 -0700 From: Terry Lambert Message-Id: <199602142248.PAA00886@phaeton.artisoft.com> Subject: Re: Confused!!!! (fwd) To: lehey.pad@sni.de (Greg Lehey) Date: Wed, 14 Feb 1996 15:48:36 -0700 (MST) Cc: hackers@freebsd.org, freebsd-doc@freebsd.org, mollers.pad@sni.de In-Reply-To: <199602141531.QAA17344@nixpbe.pdb.sni.de> from "Greg Lehey" at Feb 14, 96 04:27:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org Precedence: bulk > Forwarded message: > > > From: Frank J Estremera > > > > I am so confused as to how to boot FreeBSD from a boot manager, while on a > > second drive. I have an internal IDE drive running Windows95. I also have a > > secondary SCSI drive (device 0), totally devoted to FreeBSD. I do have > > FreeBSD loaded on it, but when I installed FreeBSD, and selected BootEasy > > as the boot manager, The operating system could not be found when booting to > > Windows95 (primary drive). I deinstalled BootEasy and installed System > > Commander as my boot manager. It recognized the SCSI drive as having FreeBSD > > loaded on it, but when selected, System Commander tells me that the boot block > > is missing on this device. The only way that I can boot FreeBSD is to insert > > the install diskette in the A drive, boot from it, and when the BOOT prompt > > appears, pointing it to hd(1,a)/kernel (I think). Just for laughs I did a > > disklabel -B sd0 to maybe try to force a boot block on the SCSI device, but > > to no avail (unless I am totally out in left field, which is likely). What > > am I missing??? Why is my operating system under Windows95 being clobbered?? > > (I then have to do an fdisk from diskette to activate my C: partition again). > > Please shine a flashlight on my face and enlighten me! > > Could it be that the lack of replies to this message is the result of > everybody else being confused as well? I currently can't get near a > running FreeBSD system, and I honestly don't know a good answer, but I > get the feeling that we have a bug which manifests itself when using > booteasy when FreeBSD is not on the first drive. I've had another > report of this kind of problem here at SNI, and in this case I'm > pretty sure it wasn't user error. Any comments from others? I haven't answered because of the formatting. It's impossible to quickly scan through the provided information and see the problem (but then I'm dyslexic and use eidetic memory coexamination as a crosscheck for what I read, so I may be the only one bothered by the way the question was organized). Comment if this is incorrect: 1) One IDE drive. Drive is primary boot device (DOS drive "C:"). 2) One SCSI drive. Drive is seen by DOS FDISK as drive "D:". 3) Loading FreeBSD on SCSI drive. 4) Want boot manager to boot DOS on IDE or BSD on SCSI. If this is correct, then: o When you install BSD on the second drive, you *don't* want to use BSD to install the boot manager. It doesn't do this very well because of OnTrack and similar translation strangeness not being equally applicable to both drives. o FDISK up the SCSI drive as a bootable drive. You may have to disable the IDE and boot from floppy to do this. If you disabled the IDE, reenable it afterwards. This will put the standard DOS MBR on the SCSI disk. o Install BSD. If you disabled the IDE in the previous step, it's easiest to do this with the IDE disabled (the SCSI drive will be drive "C:" if the IDE is disabled). o Make sure you can boot the floppy and give the device name at the floppy boot prompt and boot BSD from the SCSI. This means that BSD is properly installed on the SCSI. o With the IDE enabled, use the DOS install for the OS-BS/Booteasy boot selector *after* booting from the IDE drive. If you are running Windows95, you need to pick "Restart the computer in MS-DOS Mode" from the shutdown dialog". You have to do this because: o If you boot from a floppy instead of the IDE drive, you may not have the translation software correctly loaded. o When you are installing OS-BS/Booteasy during the BSD install, it doesn't look for the translation software except on the install drive, and even then, it only looks for the translation software it knows about. o Windows95 "MD-DOS Prompt" windows go through Windows95 I/O by default (you *can* make one that doesn't, but it involves making a shortcut to the DOS prompt and changing the properties by clicking the "Advanved..." button on the "Program" tab and checking "MS-DOS mode" in the "Advanced Program Settings" dialog). Now the boot manager will offer you to boot "DOS" (Windows95) or to boot from the second drive (which has no boot selector, only a DOS MBR with the BSD partition marked "active"). This presumes the SCSI drive looks like drive "D:" to fdisk and the SCSI BIOS correctly implements interrupt chaining for INT 13. Adapetc does, not everyone else does. Note that some BIOS incorrectly fill out the register that is supposed to contain the device actually booted from. If this happens, you will need to replace the MBR on the second drive with the boot selector as well. Do that with the IDE drive disabled, or after booting from a floppy instead of the IDE drive. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-doc Wed Feb 14 17:56:37 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA01797 for doc-outgoing; Wed, 14 Feb 1996 17:56:37 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA01789 Wed, 14 Feb 1996 17:56:29 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA19883; Thu, 15 Feb 1996 12:28:59 +1030 From: Michael Smith Message-Id: <199602150158.MAA19883@genesis.atrad.adelaide.edu.au> Subject: Re: Confused!!!! (fwd) To: lehey.pad@sni.de (Greg Lehey) Date: Thu, 15 Feb 1996 12:28:58 +1030 (CST) Cc: hackers@freebsd.org, freebsd-doc@freebsd.org, mollers.pad@sni.de In-Reply-To: <199602141531.QAA17350@nixpbe.pdb.sni.de> from "Greg Lehey" at Feb 14, 96 04:27:35 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org Precedence: bulk Greg Lehey stands accused of saying: > > Could it be that the lack of replies to this message is the result of > everybody else being confused as well? I currently can't get near a More likely that the message is close to unreadable, and thus easily ignored by all but the most patient. > running FreeBSD system, and I honestly don't know a good answer, but I > get the feeling that we have a bug which manifests itself when using > booteasy when FreeBSD is not on the first drive. I've had another > report of this kind of problem here at SNI, and in this case I'm > pretty sure it wasn't user error. Any comments from others? There are a number of problems with the 2.1 installer's handling of MBRs. In the specific case outlined in the original message, the installer has not written a bootable MBR to the second disk and thus when Booteasy tries to run it it fails. The solution here is to use 'bootinst' off the 2.1 CD or FTP site to install booteasy onto the second disk as well. > Greg -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "I seek PEZ!" - The Tick [[ From owner-freebsd-doc Thu Feb 15 07:58:36 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA05743 for doc-outgoing; Thu, 15 Feb 1996 07:58:36 -0800 (PST) Received: from montana.com (paw.montana.com [199.2.139.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA05738 Thu, 15 Feb 1996 07:58:28 -0800 (PST) From: garya@dreamchaser.org Received: from 199.2.139.40 ([199.2.139.40]) by montana.com (5.x/SMI-SVR4) id AA07644; Thu, 15 Feb 1996 08:59:22 -0700 Date: Thu, 15 Feb 1996 08:59:22 -0700 Message-Id: <9602151559.AA07644@montana.com > Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Subject: Supra Express 288i PnP modem To: hardware@freebsd.org, doc@freebsd.org X-Mailer: SPRY Mail Version: 04.00.06.17 Sender: owner-doc@freebsd.org Precedence: bulk You might want to mention that until FreeBSD supports Plug and Play, the following modem *will not work* in this environment; it apparently has no default port addr and irq: Supra Express 288i PnP Gary Aitken garya@ics.com (business) garya@dreamchaser.org (personal) From owner-freebsd-doc Thu Feb 15 08:13:06 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA06378 for doc-outgoing; Thu, 15 Feb 1996 08:13:06 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA06359 Thu, 15 Feb 1996 08:12:58 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id JAA29524; Thu, 15 Feb 1996 09:15:38 -0700 Date: Thu, 15 Feb 1996 09:15:38 -0700 From: Nate Williams Message-Id: <199602151615.JAA29524@rocky.sri.MT.net> To: garya@dreamchaser.org Cc: hardware@freebsd.org, doc@freebsd.org Subject: Re: Supra Express 288i PnP modem In-Reply-To: <9602151559.AA07644@montana.com > References: <9602151559.AA07644@montana.com > Sender: owner-doc@freebsd.org Precedence: bulk > You might want to mention that until FreeBSD supports Plug and Play, > the following modem *will not work* in this environment; it apparently > has no default port addr and irq: > > Supra Express 288i PnP Is there any way of setting the port and IRQ via a DOS program? Most of the 'software selectable' hardware I've gotten has some program to setup the software under DOS. Nate From owner-freebsd-doc Thu Feb 15 10:08:56 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA12828 for doc-outgoing; Thu, 15 Feb 1996 10:08:56 -0800 (PST) Received: from montana.com (paw.montana.com [199.2.139.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA12808 Thu, 15 Feb 1996 10:08:50 -0800 (PST) From: garya@dreamchaser.org Received: from 199.2.139.37 ([199.2.139.37]) by montana.com (5.x/SMI-SVR4) id AA13228; Thu, 15 Feb 1996 11:09:39 -0700 Date: Thu, 15 Feb 1996 11:09:39 -0700 Message-Id: <9602151809.AA13228@montana.com > Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Subject: Re: Supra Express 288i PnP modem To: Nate Williams Cc: hardware@freebsd.org, doc@freebsd.org X-Mailer: SPRY Mail Version: 04.00.06.17 Sender: owner-doc@freebsd.org Precedence: bulk On Thu, 15 Feb 1996, Nate Williams wrote: >> You might want to mention that until FreeBSD supports Plug and Play, >> the following modem *will not work* in this environment; it apparently >> has no default port addr and irq: >> >> Supra Express 288i PnP > >Is there any way of setting the port and IRQ via a DOS program? Most of >the 'software selectable' hardware I've gotten has some program to setup >the software under DOS. Yes, but I don't think its sufficient. Here's what I tried: I had it properly configured and it worked under win95 at a more or less standard place; I can't remember if it was 0x3f8 @ irq4 or 0x2f8 @ irq3. >From there I shutdown win95 and soft booted freebsd. So the system was never powered off, but did go through a normal boot sequence. The modem was never recognised. I also tried configuring kernels to look at all 8 combinations of the standard port addrs and irq 3 & 4, and the thing never showed up at any of them. Then I got pissed and sent some mail to supra support. My question and their reply: >>I just purchased a Micron system with a SupraExpress 288i PnP modem in it, >>and am trying to configure the system to run FreeBSD, a UNIX system. >>Micron cannot answer my questions, and suggested I contact you. >>I need to know what the default hardware configuration for this modem is, >>since the system does not support PnP. I tried all the standard io addresses >>and irq's and the modem didn't respond. (0x3f8 @ irq3 & irq4, >>0x2f8 @ irq3 & irq4, 0x3e8 @irq3 & irq4, 0x2e8 @ irq3 & irq4) >>Does this device have a default address and irq, or does it only work in a >>PnP environment? >It only works in a PnP environment or with the PnP Utility Install in a Win >3.1, 3.11, Win95 or DOS environment. I did not go to the trouble of trying to run the utility. I assumed that since I had it properly configured under win95, then did a soft shutdown and boot to freebsd, and I would need to do the soft shutdown and boot regardless, that the utility wouldn't make it behave any differently. I gave up, decided never to buy another supra modem, and switched it with a US Robotics running in another system. Gary Aitken garya@ics.com (business) garya@dreamchaser.org (personal) From owner-freebsd-doc Thu Feb 15 12:36:19 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA20880 for doc-outgoing; Thu, 15 Feb 1996 12:36:19 -0800 (PST) Received: from srv1.thuntek.net (root@[206.206.98.20]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA20874 Thu, 15 Feb 1996 12:36:11 -0800 (PST) Received: from scott.cr.usgs.gov (aslpca.cr.usgs.gov [136.177.121.30]) by srv1.thuntek.net (8.6.12/8.6.12) with SMTP id NAA20750; Thu, 15 Feb 1996 13:36:59 -0700 Message-Id: <2.2.32.19960215205056.00ad1d10@thuntek.net> X-Sender: thor@thuntek.net X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 15 Feb 1996 13:50:56 -0700 To: garya@dreamchaser.org, Nate Williams From: Scott Halbert Subject: Re: Supra Express 288i PnP modem Cc: hardware@FreeBSD.ORG, doc@FreeBSD.ORG Sender: owner-doc@FreeBSD.ORG Precedence: bulk At 11:09 AM 2/15/96 -0700, garya@dreamchaser.org wrote: > > >On Thu, 15 Feb 1996, Nate Williams wrote: >>> You might want to mention that until FreeBSD supports Plug and Play, >>> the following modem *will not work* in this environment; it apparently >>> has no default port addr and irq: >>> >>> Supra Express 288i PnP >> >>Is there any way of setting the port and IRQ via a DOS program? Most of >>the 'software selectable' hardware I've gotten has some program to setup >>the software under DOS. > >Yes, but I don't think its sufficient. >Here's what I tried: > Don't forget that there is another problem going on here. Not only do you have the PnP problem to deal with, but FreeBSD has some problems seeing some internal modems even if they are there and properly set up (there are some delay problems in the driver). > >Gary Aitken garya@ics.com (business) > garya@dreamchaser.org (personal) ---Scott Halbert (thor@thuntek.net) Thunder Network Technologies From owner-freebsd-doc Thu Feb 15 13:23:56 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA24197 for doc-outgoing; Thu, 15 Feb 1996 13:23:56 -0800 (PST) Received: from montana.com (paw.montana.com [199.2.139.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA24188 Thu, 15 Feb 1996 13:23:52 -0800 (PST) From: garya@dreamchaser.org Received: from 199.2.139.31 ([199.2.139.31]) by montana.com (5.x/SMI-SVR4) id AA23722; Thu, 15 Feb 1996 14:24:10 -0700 Date: Thu, 15 Feb 1996 14:24:09 -0700 Message-Id: <9602152124.AA23722@montana.com > Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Subject: Re: Supra Express 288i PnP modem To: Scott Halbert , Nate Williams Cc: hardware@FreeBSD.ORG, doc@FreeBSD.ORG X-Mailer: SPRY Mail Version: 04.00.06.17 Sender: owner-doc@FreeBSD.ORG Precedence: bulk >Don't forget that there is another problem going on here. Not only do >you have the PnP problem to deal with, but FreeBSD has some problems >seeing some internal modems even if they are there and properly >set up (there are some delay problems in the driver). That's good to know, if I ever get that far. Thanks. I just tried the configuration program supplied with the modem and it won't even load properly under win95; or dos 7.0, or dos 6.22; nor will it run from the distribution disk. Just hangs and you have to reboot. Shoot the modem, and the mfg... Gary Aitken garya@ics.com (business) garya@dreamchaser.org (personal) From owner-freebsd-doc Thu Feb 15 15:44:50 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA02762 for doc-outgoing; Thu, 15 Feb 1996 15:44:50 -0800 (PST) Received: from srv1.thuntek.net (root@[206.206.98.20]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA02754 Thu, 15 Feb 1996 15:44:47 -0800 (PST) Received: from scott.cr.usgs.gov (aslpca.cr.usgs.gov [136.177.121.30]) by srv1.thuntek.net (8.6.12/8.6.12) with SMTP id QAA22132; Thu, 15 Feb 1996 16:45:55 -0700 Message-Id: <2.2.32.19960215235954.00e7af4c@thuntek.net> X-Sender: thor@thuntek.net X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 15 Feb 1996 16:59:54 -0700 To: garya@dreamchaser.org, Nate Williams From: Scott Halbert Subject: Re: Supra Express 288i PnP modem Cc: hardware@FreeBSD.ORG, doc@FreeBSD.ORG Sender: owner-doc@FreeBSD.ORG Precedence: bulk At 02:24 PM 2/15/96 -0700, garya@dreamchaser.org wrote: > >>Don't forget that there is another problem going on here. Not only do >>you have the PnP problem to deal with, but FreeBSD has some problems >>seeing some internal modems even if they are there and properly >>set up (there are some delay problems in the driver). > >That's good to know, if I ever get that far. Thanks. >I just tried the configuration program supplied with the modem and it >won't even load properly under win95; or dos 7.0, or dos 6.22; >nor will it run from the distribution disk. Just hangs and you have to >reboot. We're running with some supras without Pnp, but I had to patch sio.c to get them to work. Basically I think that no PnP device will work with FreeBSD until a PnP manager is added to the kernel and device drivers are updated to support it. The PnP BIOS negotiates IRQs and addresses with the cards and FreeBSD must get that info from the PnP BIOS tables in order for any of the drivers to know about the cards. I don't even know what happens to PnP cards when you have no PnP BIOS in your machine. ---Scott Halbert >Shoot the modem, and the mfg... > >Gary Aitken garya@ics.com (business) > garya@dreamchaser.org (personal) > > From owner-freebsd-doc Sat Feb 17 18:44:41 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA18823 for doc-outgoing; Sat, 17 Feb 1996 18:44:41 -0800 (PST) Received: from ionline.com (infinity.i2k.net [199.176.249.62]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA18809 for ; Sat, 17 Feb 1996 18:44:18 -0800 (PST) X-ROUTED: Sat, 17 Feb 1996 21:43:46 -0500 Received: from by ionline.com with smtp id BFCLANFK ; Sat, 17 Feb 1996 21:43:12 -0500 Message-ID: <3126BBE1.38A7@ionline.com> Date: Sat, 17 Feb 1996 21:40:49 -0800 From: Paul X-Mailer: Mozilla 2.0 (Win16; I) MIME-Version: 1.0 To: doc@freebsd.org Subject: manual X-URL: http://www.freebsd.org/handbook/ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org Precedence: bulk I wish I could help with the project, but I'm just starting to install FreeBSD for the first time. What I'm writing about is that I'd like to obtain the manual in it's entirety to print out and use. Is it available in either printed form aor as a downloadable file? I'm willing to pay for it. Paul From owner-freebsd-doc Sat Feb 17 22:17:59 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA27546 for doc-outgoing; Sat, 17 Feb 1996 22:17:59 -0800 (PST) Received: from xi.dorm.umd.edu (xi.dorm.umd.edu [129.2.152.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA27535 Sat, 17 Feb 1996 22:17:48 -0800 (PST) Received: from xi.dorm.umd.edu (localhost [127.0.0.1]) by xi.dorm.umd.edu (8.7.3/8.6.12) with SMTP id BAA03208; Sun, 18 Feb 1996 01:17:22 -0500 (EST) Date: Sun, 18 Feb 1996 01:17:20 -0500 (EST) From: Sujal Patel X-Sender: smpatel@xi.dorm.umd.edu To: garya@dreamchaser.org cc: hardware@freebsd.org, doc@freebsd.org Subject: Re: Supra Express 288i PnP modem In-Reply-To: <9602151559.AA07644@montana.com > Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Thu, 15 Feb 1996 garya@dreamchaser.org wrote: > You might want to mention that until FreeBSD supports Plug and Play, > the following modem *will not work* in this environment; it apparently > has no default port addr and irq: > > Supra Express 288i PnP I have working ISA PnP support for FreeBSD-- But I'm still working on various parts of the code (I guess I really should get someone to commit the code as it is, since it mostly works). The code works properly with all the PnP cards I've found so far (all 3 of them :) Your Supra modem is the exact same one I have, so you should have no problems. Here is a quick summary of what you need to do.. Sorry for the uglyness, but I'm working on complete auto-configuration of PnP devices (until then you'll need to do manual configuration, but it will work): Here is a manifest of what you'll find on ftp://xi.dorm.umd.edu/pub/pnp: autoconf.c.patch PATCH to src/sys/i386/i386/autoconf.c files.i386.patch PATCH to src/sys/i386/conf/files.i386 pnp.c place in src/sys/i386/isa pnp.h place in src/sys/i386/isa pnpinfo.tar.gz untar somewhere. You'll need to put "controller pnp" in your kernel config (but do not change any of the device entries to reference the controller pnp). You'll also need to edit pnp.c's configuration information (since it only supports manual configuration right now). The structure looks like: { 0x00008803, /* Serial Number */ -1, /* Logical Device Number */ { 15, -1 }, /* IRQ Number */ { -1, -1 }, /* DRQ Number */ { 0x3e8, /* Ports 1 */ -1, /* Ports 2 */ -1, /* Ports 3 */ -1, /* Ports 4 */ -1, /* Ports 5 */ -1, /* Ports 6 */ -1, /* Ports 7 */ } }, Just change the Serial Number, and other parameters to match what "pnpinfo" says about your device. If all goes well, it should say that it configured your device on boot up. You may need to fiddle with this a bit, since I those patches are against -current (and were created manually, not from my running kernel w/pnp). Lemme know how it goes or if you have any problems. Sujal