Re: Soundblaster 16 and kernel 2.6

From: Jim Bowering (iambat_at_otvcablelandot.net)
Date: 09/13/04 

Date: Mon, 13 Sep 2004 11:58:20 -0700

Andreas Janssen wrote:

> Hello
>
> Jim Bowering (<iambat@otvcablelandot.net>) wrote:
>
> (Please don't top-post, and please configure your new reader to display
> an attribution line that tells everyone who wrote the post that you
> reply to, like you can see above)
>
>> [Loading drivers for SB 16]
>> FATAL: Error inserting snd_sb1
>> (/lib/modules/2.6.7/kernel/sound/isa/sb/snd-sb16.ko): No such device
>>
>> I'm sure this is going to work. I have that feeling that I'm on the
>> right path. However, when I modprobe snd-sb16, I get this error
>> message
>> The driver is present in the indicated directory. All the other
>> modules insert quietly (-pcm-oss and so on). Is this a case where I
>> have to go to /dev and MAKEDEV? (Another mystery to me.)
>
> The device files should already be there, or will automatically be
> created when the drivers are loaded (e.g. if you use devfs or udev). If
> the driver is the correct one for your card, and doesn't find your
> card, /and/ if your card is an ISA card /without/ Plug and Play
> support, then my guess that you need to tell the driver some hardware
> info about your card, most of all the IO, IRQ and DMA values, e.g.
>
> modprobe snd-sb16 irq16=7 dma=1 io=220
>
> I don't know the configuration of your card. Maybe you can set the
> config using jumpers on the card itself, probably you can use some DOS
> configuration program to reconfigure it. Maybe it works from within
> Windows as well. Simply trying out some values can also work, if the
> configuration is not too exotic. You can find the options for the
> driver at the home page of the ALSA project (you got the link in my
> last post).
>
> best regards
> Andreas Janssen

I will "man" devfs and udev. I will try modprobe using the card's IRQ, DMA
and I/O port. I know my card's settings. It's been with me since OS/2,
through many other installs. I have fooled around with the DOS app that
changes its settings, but it's all default now. This should be a
straightforward test.

As for the reminder about top-posting: I understand the need to do that.
As you can see, my message started with a quotation, followed by my post at
the bottom. Here's how that happened so you can isolate the deficiency in
your automated script: I started a fresh message with the same subject
line as the original thread, pasted in material that I thought would
provide an adequate backdrop, and added my report on what happened when I
tried to modprobe snd-sb16.

I should have included attribution, now that you point it out. Attribution
is just useful for so many reasons that I should do it automatically. That
would be the fault of starting a fresh message, again.

Anyway, I'll boot MEPIS and try the extra parameters with modprobe. 

-- 
Lapdance - the laptop distribution.

Relevant Pages

  • Carte Blanche - the wait is almost over.
    ... The hardware works quite well but the driver has a lot ... What's needed to load a new configuration into the FPGA is a $12 ... JTAG adapter by Digilent and a PC with a real parallel port - not ... this code from a file on the SD card if needed. ...
    (comp.sys.apple2)
  • [PATCH 1/3] to Documentation/digiboard.txt
    ... Remove obsolete Documentation/digiboard.txt file - driver was obsoleted ... -The Linux Digiboard Driver ... -memory base address of the Nth card, ... -Boot-time configuration when linked into the kernel ...
    (Linux-Kernel)
  • Re: more install problems
    ... > mandrake install worked without needing to compile a separate ... I notice the card doesn't light up ... boot, and if I try to make a new configuration, the list is simply ... driver, just IPs and so forth, so redoing that is pointless. ...
    (Debian-User)
  • Re: Soundblaster 16 and kernel 2.6
    ... an attribution line that tells everyone who wrote the post that you ... > The driver is present in the indicated directory. ... card, /and/ if your card is an ISA card /without/ Plug and Play ... I don't know the configuration of your card. ...
    (comp.os.linux.setup)
  • RE: [UPDATED PATCH] EFI support for ia32 kernels
    ... >> reuse a single driver image for multiple architectures assuming there ... As one of the people responsible for the EFI Specification and our ... Perhaps the UNDI network card interface that Intel developed ... BIOS can't shadow that much ROM code. ...
    (Linux-Kernel)