> System:
> AlphaStation 200 4/166, running OSf1/v3.0.
> Software package,
> Multimedia Services for DEC OSF1 (runtime) v1.5. from the April layered products CD.
> subset names is mme150.
>
> Hello all,
> I'm having a problem getting the MMS package to work with my alpha
> station. After installing MMS and doing the kernel rebuild the msb0
> device doesn't show up in the list of system devices during boot.
> I installed a new operatiing system from the December OSF1/v3.0 CD.
> before adding the MMS package the sounds board would appear in the list
> of devices as:
> msb0 at isa0
>
> I then installed the MMS v1.5 package from tha april layered
> products CD and rebuilt the kernel. Now I see the following during boot
> msb0 Warning Sound board 0 in system configuration, but not present.
> msb0 not probed.
> When I try to run it IVP for MMS I get the following error:
> Error: Exiting did not find any devices.
>
> I shutdown the system vis shutdown -h and did an isacfg -all and a
> show config. It showed the following values for the sound board.
> etyp 1
> slot 2
> dev 0
> name PCXBJ
> iobase0 530
> isbase1 388
> irq 9
>
> These are the values that were installed by DEC. Anyone have any
> idea why the msb0 device show up before I install the MMS software and
> not after? Anyhelp with htis would be great.
> Thanks,
Strictly speaking, the April 1995 LP library CD is in support of DEC OSF/1
V3.2, not V3.0, but I don't think that's the problem.
I don't personally have a system with the sound board, so it's impossible
for me to attempt to replicate your problem.
However, I don't think that's important, and I'll try to advise you on how
to get it working again.
I think what went wrong was when you installed the kernel. It sounds like
the msb0 option didn't get configured into your new kernel.
You already used the "show config" command; make sure there aren't any ISA
device conflicts (same IRQ or IO base address assigned). ISA devices can be
mis-configured to cause conflicts, just as SCSI devices can be assigned to
the same bus address, and the result is that the device isn't seen by higher
software layers. Of course, you need to shut down your system to do this.
Reboot using the "genvmunix" kernel -- at the >>> console prompt enter the
command
boot -fi "genvmunix" dka0
or whatever device contains your root file system. This device is usually
recorded in the console environment variable bootdef_dev so you can use the
console's "show" command and look for that variable.
Once your system is up and running, log in as root. Look at the file
/var/adm/messages for references to the msb0 device. If they are there,
then your device is OK, because the GENERIC kernel sees it. I believe it
was seen before by the GENERIC kernel.
Now run the doconfig script to create a new kernel configuration file. You
already did this, but do it again. You can pick a different system name if
you want to make sure you can make comparisons and you have enough free disk
space to build two different kernel configuration. (If you think you'll run
out of disk space, remove the directory /sys/SYSTEMNAME and move the current
/sys/conf/SYSTEMNAME file to /sys/conf/SYSTEMNAME.old before you start the
donconfig step). Then (as root) just enter "doconfig" and when prompted put
your original SYSTEMNAME and a new /sys/conf/SYSTEMNAME file is created and
a new kernel is built in /sys/SYSTEMNAME.
After the kernel is built, check the /sys/conf/SYSTEMNAME file against the
old one you saved from before. If there are NO DIFFERENCES then you have a
problem, maybe. Check for msb0 ; if it's in there, then your new kernel is
probably OK, but if it's not, you may have a problem.
You should see a line in the configuration file for "controller msb0" but if
it's not there, edit the file and add a line like this:
controller msb0 at * vector msbintr
Then rebuild the kernel with "doconfig -c SYSTEMNAME". The new kernel
should recognize your sound card when you reboot.
You can check your existing /sys/conf/SYSTEMNAME file for the "controller
msb0" line; if it's not there, that's why the MME stuff isn't working with
your kernel. As to WHY it's not there, I don't know.
Good luck!
Tom
Dr. Thomas P. Blinn, UNIX Software Group, Digital Equipment Corporation
110 Spit Brook Road, MS ZKO3-2/U20 Nashua, New Hampshire 03062-2698
Technology Partnership Engineering Phone: (603) 881-0646
Internet: tpb_at_zk3.dec.com Digital's Easynet: alpha::tpb
Worry kills more people than work because more people worry than work.
My favorite palindrome is: Satan, oscillate my metallic sonatas.
-- Phil Agre, pagre_at_ucsd.edu
Opinions expressed herein are my own, and do not necessarily represent
those of my employer or anyone else, living or dead, real or imagined.
Received on Fri May 26 1995 - 12:01:20 NZST