🚀 go-pugleaf

In article <4g0gcs$emb@news.isc.rit.edu> drsics@osfmail.isc.rit.edu (SMITH) writes:
>In article <mdoerner.60.002B53B0@magnus.acs.ohio-state.edu>,
>Nuke'd <mdoerner@magnus.acs.ohio-state.edu> wrote:
>>In article <4f6k0k$n7u@st-james.comp.vuw.ac.nz> bthomas@promansys.co.nz (Ben Thomas) writes:
>>>From: bthomas@promansys.co.nz (Ben Thomas)
>>>Subject: Re: Help! Linux can not see SCSI cd drive.
>>>Date: Tue, 06 Feb 96 22:12:47 GMT
>>
>>[Text Deleted]
>>
>>>I have a virtually the same problem with a CHINON 525 SCSI drive and Adaptec 
>>>1522a controller.  The common elements to the above are that I am using EIDE 
>>>HDDs and SCSI CD-ROM.  Linux complains that it is not a block device or the 
>>>scsi bus times out.
>>
>>>I am using the Slackware 3.0 November 1995 edition.
>>
>[...]
>>>Linux works fine, I just can't mount the CD - which is a real pain.
>>
>[...]
>>I am having the EXACT same problem as you. I have a SIDE GOLD adapter (aha152x 
>>compatible, VL-BUS) and have the Chinon CDS-525 and a Fujitsu 540 meg hd, both 
>>SCSI-2. I have no problem with the hard drive, but the CD-ROM refuses to 
>>mount! The CD-ROM eventally times out (under both redhat and linux CD 
>>Distributions) eventually saying that the superblock is bad or that the wrong 
>>file system is being mounted. See my origonal post in the Linux.setup group 
>>for all the details. WHAT IS THE @#$%*&^ DEAL HERE? (The scsi FAQ on cd-rom is 
>>useless for troubleshooting.)
>>
>
>	Everyone seems to be using adaptec scsi and IDE at the same time. 
>If this is the configuration you have, then there are a couple of things 
>you should be prepared for:
>
>	1) If the scsi card has a scsi bios on board, then it will conflict
>with the manster IDE drive in your system.  This is because you cannot have
>two "intelligent" controllers in the system at the same time.

PLEASE, don't tell my computer this!  BTW this is a STUPID statement.  The 
ORIGINAL IBM spec allowed for a LOT of BIOS space, and larger BIOS are banked.
I have THREE "intelligent" controllers.

>
>	2) If you are lucky enough to have gotten past the above, the 
>autodetect code in the kernel will not be able to find the card(the kernel
>locates the scsi card by passively searching memory for a particular 
>identification string -- if there's no bios, there's no id string).


SIMPLE, just leave the bios there!  It works GREAT for me, and MANY others!

>
>	3) You can either get around this by adding a command line option
>to the LILO prompt at boot up, or you can use a special build of the 
>kernel with appropriate values compiled in.  The command line would look
>something like:
>
>	LILO: linux aha152x=0x340,11,7,1
>where
>	0x340 is the port addres in hex
>	11 is the IRQ 
>	7 is the scsi id of the interface(ideally this is always 7)
>	1 is enable/disable scsi reconnect(I use 1 all the time and it
>						seems to work fine).
>
>	On a final note, the example above works for the aha1520, aha1522 
>family of adapters(this is the adapter shipped on a SoundBlaster, too). If
>you have a different adapter, you'll need to modify the above accordingly.

The ONLY way ANY of your statements concerning BIOS could be true at ALL is
if you have an address conflict there.  THAT is why they are SETTABLE!