[lug] Re: SB AWE32 Errors

[D. Stimits]

SoloCDM wrote:
> 
> "D. Stimits" stated the following:
> >
> > SoloCDM wrote:
> > >
> > > "D. Stimits" stated the following:
> > > >
> > > > SoloCDM wrote:
> > > > >
> > > > > I found the following modules for a Creative SB AWE32, with kernel
> > > > > 2.2.14-15:
> > > > >
> > > > > /sbin/modprobe sound; /sbin/modprobe isapnp; /sbin/modprobe
> > > > > joy-creative; /sbin/modprobe joystick; /sbin/modprobe snd-card-sbawe;
> > > > > /sbin/modprobe snd-midi; /sbin/modprobe snd-mpu401-uart;
> > > > > /sbin/modprobe snd-hwdep; /sbin/modprobe snd; /sbin/modprobe snd-pcm;
> > > > > /sbin/modprobe soundcore; /sbin/modprobe snd-sb16-csp; /sbin/modprobe
> > > > > snd-sb16-dsp; /sbin/modprobe snd-mixer; /sbin/modprobe snd-opl3;
> > > > > /sbin/modprobe snd-wavefront-synth; /sbin/modprobe awe_wave;
> > > > > /sbin/modprobe snd-hwdep; /sbin/modprobe snd-card-sbawe; /sbin/insmod
> > > > > opl3; /sbin/insmod sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330;
> > > > > /sbin/insmod uart401
> > > > >
> > > > > My sound worked perfectly with kernel 2.0.36.  I have my CDROM
> > > > > connected to the IDE controller card.  Every time I run sndconfig
> > > > > with(out) global $DISPLAY environment variable, as per instructions,
> > > > > I get the following errors:
> > > > >
> > > > > Don't know what to do with CONFIGURE CTL0044/941569 (LD 2 on or
> > > > > around line 353 /etc/isapnp.conf:353 -- Fatal - Error occurred
> > > > > parsing config file --- no action taken
> > > >
> > > > FYI, this is not a module error. This is for setting up plug-n-play ISA
> > > > cards so that their hardware settings can match what either the kernel
> > > > or the modules are set to use. I don't know if maybe the version of
> > > > isapnptools also required a change/upgrade when going from the old 2.0.x
> > > > to 2.2.x. You might want to post about a half dozen lines before and
> > > > after line 353 (and mark 353) for /etc/isapnp.conf. Plus back it up so
> > > > you can experiment, e.g., rerun isapnpdump and edit again.
> > >
> > > I didn't upgrade from 2.0.x to 2.2.x.  I overhauled the entire disk --
> > > formatted the disk, installed new OS, which included kernel 2.2.x.  I
> > > incorporated configurations from the old OS by modifying them to fit
> > > the present platform.  I used sndconfig to create /etc/isapnp.conf.
> > >
> > > > > What must be done to fix this problem?
> >
> > It sounds like sndconfig is broken. Is the sound card in fact an ISA
> > slot, plug-n-play card? What are the lines surrounding the error line of
> > /etc/isapnp.conf? I would still guess that sndconfig is reading this
> > file but it is generated by isapnptools (I assume since the file is
> > there and not copied from the old install that isapnptools was
> > installed).
> 
> Here's the lines gathered around line 353:
> 
> # Edit the entries below to uncomment out the configuration required.
> # Note that only the first value of any range is given, this may be
> changed if required
> # Don't forget to uncomment the activate (ACT Y) when happy
> #
> (CONFIGURE CTL0044/941569 (LD 2
> #     ANSI string -->WaveTable<--
> 
> # Multiple choice time, choose one only !
> 
> #     Start dependent functions: priority preferred
> #       Logical device decodes 16 bit IO address lines
> #             Minimum IO base address 0x0620
> #             Maximum IO base address 0x0620
> #             IO base alignment 1 bytes
> #             Number of IO addresses required: 4
> # (IO 0 (SIZE 4) (BASE 0x0620))
> 
> #       Start dependent functions: priority acceptable
> #       Logical device decodes 16 bit IO address lines
> #             Minimum IO base address 0x0620
> #             Maximum IO base address 0x0680
> #             IO base alignment 32 bytes
> #             Number of IO addresses required: 4
> # (IO 0 (SIZE 4) (BASE 0x0620))
> 
> #     End dependent functions
>  (NAME "CTL0044/941569[2]{WaveTable           }")
> # (ACT Y)
> ))
> 
> Note: When you reply to this message, please include the mailing
>       list/newsgroup address in Cc: and my email address in To:.
> 
> *********************************************************************
> Signed,
> SoloCDM

This is where I hate line wrapping in email. There are places that I
assume line wrapping has occurred, but am not positive. The other thing
is that it would be nice to know exactly which line is line 353; even
with that, it looks like it will be necessary to see the whole file to
figure it out. The reason I say this is because of the common failure to
have mismatched pairs of parenthesis "()", quotes, square braces "[]",
or curly-braces "{}". If the line directly at 353 doesn't have an
obvious error, then it is the matching of the items similar to
parenthesis that should be checked. Since this file is created entirely
commented out, and then uncommented to reveal the parts that have been
chosen to be activated, it isn't unusual to make an error when done by
hand. If this is the case, the actual error probably occurred before
line 353, and 353 is just the first point that the error could be
spotted at (a symptom rather than a cause, the point of error might not
even be part of the soundblaster area if more than one ISA plug-n-play
card is present). From the modprobe data though, you can see which
subsections should be uncommented: io=0x220 irq=5 dma=1 dma16=5
mpu_io=0x330.

BTW, is this the exact copy of the same file you had in the prior
install? You could use "diff" to compare them ("diff fileA fileB" has no
output if they are exact copies). And no hardware changes were made, not
even the moving of a card from one slot to another?

D. Stimits, stimits at idcomm.com