Very Computer

Has anyone been able to install Linux successfully using a
Soundblaster (not Soundblast pro) CD?  The boot driver
for soundblaster only supports SoundBlaster pro?

Thanks,

Did it a few times on machines equipped with a Soundblaster 16;
The new version is IDE - but maybe that's not what you mean?

--
 -----------------------------------------------------------------------------

 -----------------------------------------------------------------------------

I have an SB16 compatible doubling as interface to
a Sony33A CD. In my case the setup program mounts it as
a plain cdu31a (NOT sb-whatever) from /dev/sonycd
ie. the fact that it's connected via an SB doesn't
seem to matter.  /Henrik

=====================================================================

Did it a few times on machines equipped with a Soundblaster 16;
The new version is IDE - but maybe that's not what you mean?

--

-------------------------------------------------------------------------
----

   #

-------------------------------------------------------------------------
----

I got Ygrassi plug'n play (fall 95: from Borders.)to recognize
my NEC 3x  SCSI cd on a Soundblaster 16 ( creative labs)
by following the directions in the scsi HOWTO. ( Last night!)
( I'm assuming your soundblaster cd is connected to a sndblast
16/scsi?)  

At  the boot: prompt I used:

linux aha152x=0x340  sbpcd=0

to force recognition of my soundblaster and cd.
sbpcd= 0 avoids the long process of looking for the soundblaster pro.

It figured out the other numbers for itself with no problems and
came up in Linux with the cd mounted as  root.
( I may just have been lucky. I've got OS/2 which is as picky as linux!)

The X-windows demo worked the first time ( cool!).

I was impressed  by  'plug 'n play'   from the CD but
haven't  installed to  HD yet. Have to partition first.

As I mentioned I did this for the first time last night, so  don't
take anything I say to literally.

--------------------------------------------------
Bob Fletcher
Johns Hopkins Univ. Dept of Physics.
N. Charles st. Baltimore MD  

----------
From the SCSI  HOWTO.

   Section 4.3 : Adaptec 152x, 151x, Sound Blaster 16 SCSI, SCSI Pro,
        Gigabyte, and other AIC 6260/6360 based products (Standard)
Supported Configurations :
BIOS addresses : 0xd8000, 0xdc000, 0xd0000, 0xd4000, 0xc8000, 0xcc000,  
0xe0000,
        0xe4000.
Ports : 0x140, 0x340
IRQs : 9, 10, 11, 12
DMA is not used
IO : port mapped

Autoprobe :

    Works with many boards with an installed BIOS.  All
    other boards, including the Adaptec 1510, and Sound Blaster16 SCSI
    must use a kernel command line or compile time override.

Autoprobe Override :
Compile time :
Define PORTBASE, IRQ, SCSI_ID, RECONNECT, PARITY as appropriate, see  
Defines

kernel command line :  
aha152x=<PORTBASE>[,<IRQ>[,<SCSI-ID>[,<RECONNECT>[,<PARITY>]]]]

SCSI-ID is the SCSI ID of the HOST adapter, not of any devices you have  
installed
on it.  Usually, this should be 7.

To force detection at 0x340, IRQ 11, at SCSI-ID 7, allowing
disconnect/reconnect, you would use the following command line
option :

aha152x=0x340,11,7,1

Antiquity Problems, fix by upgrading :
1.  The driver fails with VLB boards.  There was a timing problem
        in kernels older than revision 1.0.5.

Defines :
AUTOCONF      : use configuration the controller reports (only 152x)
IRQ           : override interrupt channel (9,10,11 or 12) (default 11)
SCSI_ID       : override SCSI ID of AIC-6260 (0-7) (default 7)
RECONNECT     : override target disconnect/reselect (set to non-zero to
                allow, zero to disable)
DONT_SNARF     : Don't register ports (pl12 and below)
SKIP_BIOSTEST  : Don't test for BIOS signature (AHA-1510 or disabled BIOS)
PORTBASE       : Force port base. Don't try to probe

: > =====================================================================

: > >Has anyone been able to install Linux successfully using a
: > >Soundblaster (not Soundblast pro) CD?  The boot driver
: > >for soundblaster only supports SoundBlaster pro?
: >
: I got Ygrassi plug'n play (fall 95: from Borders.)to recognize
: my NEC 3x  SCSI cd on a Soundblaster 16 ( creative labs)
: by following the directions in the scsi HOWTO. ( Last night!)
: ( I'm assuming your soundblaster cd is connected to a sndblast
: 16/scsi?)  
 [snipped: the rest of Robert's SCSI-specific post]

 I am using a supposedly soundblaster-compatible card (SC400, apparently
made by Reveal, subtype unknown), connected to a Panasonic/Matsushita
CD 563.  The RedHat 2.0 install auto-detected it first as a Soundblaster-type
card at 0x630, but could not mount it.  Several iterations later, it
identified it as a "Lasermate" type.  Now, at the startup prompt, I use
boot:   linux sbpcd=0x630,Lasermate  
and it all works fine.  Go figure.
  -Richard "I dunno, last night is the first time it worked for me" Ebling

Quote:> I am using a supposedly soundblaster-compatible card (SC400, apparently
>made by Reveal, subtype unknown), connected to a Panasonic/Matsushita
>CD 563.  The RedHat 2.0 install auto-detected it first as a Soundblaster-type
>card at 0x630, but could not mount it.  Several iterations later, it
>identified it as a "Lasermate" type.  Now, at the startup prompt, I use
>boot:   linux sbpcd=0x630,Lasermate  
>and it all works fine.  Go figure.

Ah!  You have the exact same card as I do, except for your port number.

It is actually a soundblaster pro card-- the LaserMate is the cdrom
interface.  In my experience, Linux doesn't recognise my sound card at all
unless I run the soundinit program under DOS first.  Thus I have to start up
dos fully before I can look at linux.  I have to rerun the initiation after
every hard boot or I can't see the cdrom.

I'm just about to give up on RedHat 1.0 (I got it soon after it was
released) because it seems to require X, which I just can't seem to get
enough space for.  Does RH 2.0 have less of a requirement for disk space?

Oh, also, I tried installing without X, but I can't recompile the kernel.  I
followed the instructions in the readme to the letter, but it still says
that it can't find version.h and a few other include files.  The latest
DOSEMU also gives a similar error.

Quote:>  -Richard "I dunno, last night is the first time it worked for me" Ebling

-Billy