Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!dfw.nkn.net!vortex.fastlane.net!rowdy.lonestar.org!nemesis!uhclem From: uhclem@nemesis.lonestar.org (Frank Durda IV) Subject: Re: Installing from CDROM - Simple question X-Newsreader: Tin 1.1 PL5 Organization: The Big Blue Box Message-ID: <DFLB9n.AE6@nemesis.lonestar.org> References: <447h35$hk7@homer.alpha.net> Date: Thu, 28 Sep 1995 00:41:46 GMT Lines: 100 [0]Thank you all who answered my question. Since i don't see it posted [0]here, and some might appreciate the reply I got, if you include a "-c" [0]during the boot (with fbsdboot before the -D kernel), the boot sequence [0]will let you configure the devices. [0] [0]I've gotten that far, and configure my device properly (matcd...only [0]needs the "matcd port 0x230", but tried pretty much everything) but it [0]still doesn't work. Is it possible that this kernel doesn't support the [0]new version. I know I had a problem with this with Linux and I had to [0]compile a newer kernel. To get going, walk through the following sanity test and checks: 1. Does the CD-ROM drive have a label with the model number CR-562 or CR-563? If not, matcd does not support that drive and a different driver must be used. (The TEAC CD55, Matsushita CR-522 and CR-523 drives are not compatible and WILL NOT WORK. Drives made by Sony, TEAC, and Mitsumi will not work either with this driver.) 2. Does the drive connect to the connector on the adapter or sound card that says "CREATIVE/PANASONIC"? If No, then the matcd drive is not the right driver to use or is connected incorrectly. (Can the drive be accessed under MS-DOS?) 3. When the system starts, does the matcd driver keep displaying the same message over and over until you reset the computer? If so, the host interface is not compatible with the genuine Creative Labs interface, and you need to get the latest driver. (See below for information on where to get the latest driver.) 4. When the system starts, does the matcd driver just simply say "not found"? If so, make sure MS-DOS commands can access the drive OR perform the following hardware checklist: A. Drive is connected to the host interface and cable is not off by one pin or connected upside down. B. Drive is connected to power and by pressing the drive button it will open and close the motorized tray. C. Drive is jumpered to be "Drive 0". This jumper is on the back of the drive. (If you have multiple drives, only one must be drive 0.) D. On the host interface card, make sure the CD interface is enabled. (Check by running DOS drivers OR verifying jumpers) E. If you have a "Multi-CD" sound card, make sure the CD type jumper is set to "PANASONIC" or "CREATIVE". It must not be set to "MITSUMI", "SONY", or "NONE". (The IRQ jumper for the CD-ROM should be set to "NONE".) F. Confirm by inspecting the jumpers and the host interface manual what the actual starting I/O port address is for the CD-ROM section of the card. Some Creative Labs DOS software (and manuals) list only the starting address of the audio section, and you are expected to know that the CD-ROM section is always 0x10 higher. So if the display says 0x220, try 0x230. Matcd must be told the starting address of the CD-ROM section of the card. G. With the knowledge gained in step F, set the matcd driver to look at the I/O port address by using the kernel -c command and port matcd 0xnnn , where nnn is the address. Then type quit and see if the drive is detected. If you find yourself in the condition where you need the newer driver, download the latest STABLE boot.flp file freebsd.cdrom.com. These can usually be found in directories with the name "SNAP" in them. (Avoid the "current" directories unless you are an experienced system debugger. "Current" is very experimental and may not work on a given day.) Once you have this new boot.flp file, place the image on a boot floppy and boot from that rather from the disk you were using. You may still have to set the appropriate I/O address, but the newer driver will handle a larger number of host interface cards from many additional vendors. Once the system is installed and running on the hard disk, you will be running the older kernel that came off the CD-ROM and it won't see the CD-ROM drive anymore. At this point you may have to disable the CD-ROM temporarily (use kernel -c for this too) until you can compile a kernel that contains the new driver. You could also obtain a newer kernel from freebsd.cdrom.com if you don't want to compile the kernel yourself. If none of that works, then send the exact model number of the drive you are trying to use, the exact brand and model of the host interface card you are trying to use, plus the labels and settings of all the jumpers on the host interface card. Please try all of the above checks in the order they are listed before giving up. Thanks. Frank Durda IV uhclem%nemesis@fw.ast.com