[PLUG] Two Questions (for the price of one!)

[Jeff DeFouw]

On Sun, 22 Oct 2000, Paul Kuliniewicz wrote:

> After the installation, he then connected a drive with Windows 
> Millennium (I'm *not* calling it "Me") as the second IDE drive.  Sure 
> enough, the Windows partition was on /dev/hdb1 (I was able to mount it 
> easily), so I tried adding an option to boot off of /dev/hdb1 into LILO.
> 
> Well, it didn't work.

LILO uses the system BIOS to boot partitions.  This is usually a BIOS
limitation.  It's simply not designed to boot off anything other than the
first drive.  The most common solution is to make the Windows drive the
first drive and create a small Linux boot partition on it to boot into
Linux.  I have Linux boot on /dev/hda2 and Windows boot on /dev/hda4 (C:).  
This isn't just a boot partition in my case though, I gave my Linux root
15GB to play with and Windows only got 1GB on the first drive. :)
(However, Windows didn't like booting at the 18GB mark.  That was probably
an older LILO or BIOS problem.  I had to do some tricks to get that to
work and I haven't tried anything new with a newer LILO.)

> 2. SoundBlaster Live!, the problem that will not die. :(  I tried 
> installing the ALSA sound drivers (http://www.alsa-project.org), but I get 
> this error when I try loading the driver (as per the instructions):
> 
> [root@holly /sbin]# ./modprobe snd-card-sb16
> /lib/modules/2.2.16-22/misc/snd-card-sb16.o: init_module: Device or
> resource busy
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters
> /lib/modules/2.2.16-22/misc/snd-card-sb16.o: insmod
> /lib/modules/2.2.16-22/misc/snd-card-sb16.o failed
> /lib/modules/2.2.16-22/misc/snd-card-sb16.o: insmod snd-card-sb16 failed

Someone on the Emu10k1 (the OSS driver at opensource.creative.com -- it's
not in the greatest state right now, just merged the new mixer code, but
you might want to try it anyway) list had this problem and solved it by
turning off the "Plug and Play OS" option in the BIOS config.  So try
changing "Plug and Play OS" to "No" in your BIOS.  Something to do with
Linux being unable to initialize the IRQ/DMA values after the BIOS plays
with it.

--
Jeff DeFouw <defouwj@purdue.edu>