Thanks to mmokrejs_at_prfdec.natur.cuni.cz,sto_at_stat.Duke.EDU,tpb_at_zk3.dec.com,
alan_at_nabeth.cxo.dec.com for a quick education in configuring the kernel
to accept third-party controllers with no instructions!! And, apologies
for not including info on my version - DU 4.0B - I work on Solaris, SunOS,
BSDI, and DU every day, sometimes it's a wonder I know my name!!
Here's how I got a Trident ISA VGA card to work in our DU 4.0B AlphaServer
400 4/233. I'll append at the end the informative responses I got.
The technique I used borrows a bit from several places, I didn't try all
the techniques people sent. I should also note we just wanted to attach
to a VGA console on a Raritan MasterConsole set into a DEC rack holding
some 4100s and StorageWorks disks - I haven't gotten graphics up on this
node, it is not very important to us, the procedure and card I used may
not be sufficient to do that. I did learn from Dec Tech Support that
the "PB2GA-FB ATI Mach64" is a supported ISA VGA card for the 400s.
>>> iconfig
[add "ISA--VGA" in Name column, tab to Enabled column, add "Y", enter-enter
to exit]
>>> boot -fi genvmunix dka0
# cp /vmunix /vmunix.yymmdd
# cd /usr/sys/conf
# cp MYSYS MYSYS.yymmdd
# doconfig (tell it to write config file to MYSYS.test)
[do a diff on MYSYS, MYSYS.test, consolidate as necessary into MYSYS]
# mv /usr/sys/MYSYS/vmunix /
[reboot to use the new kernel]
Thanks again to all!!!!
Judith Reed
jreed_at_appliedtheory.com
(315) 453-2912 x335
========================================================================
We have it in our AS 400/233 also.
What was critical to do was:
1. >>>isacfg -o -- shows devices
generally:
>>>isacfg -mod -slot<slot#> -handle <handle> -etyp 1 -enadev 1
2. in our case:
>>>isacfg -mod -slot<0> -handle <MACH64> -etyp 1 -enadev 1
for generic VGA:
>>>isacfg -mod -slot<0> -handle <ISA_VGA> -etyp 1 -enadev 1
3. >>>isacfg -mk dev 6 MACH64
4. >>>init
BTW(don't do this):
>>>isacfg -init -- clears all VGA cards
5. then boot with generic vmunix, run doconfig with no parameters, -don't
edit anything, and try to reboot. after you are successfull you can
rebuild it again with some customizations.
========================================================================
Those undefined objects are all in /sys/BINARY/vga.o You might
want to verify that you ahave installed all of the following
sets (note, this is from a 3.2c machine, but similar would apply
for other flavors of DU):
OSFBINCOM350
OSFHWBIN350
OSFSERQV350
The osfbincom350 contains the /usr/sys/include/io/dec/ws/vga.h,
/usr/sys/include/io/dec/ws/vgareg.h, /usr/sys/data/vga_data.c,
and /usr/sys/include/sys/vgainfo.h. OSFWBIN350 contains teh
vga.o file which I am guessing you have but not one or some
of the headers.
The other thing to try would be to boot genvuminx and
try a doconfig to create a new kernel configuration based
on detected hardware.
=========================================================================
The "right" "ISA handle" for a generic VGA option changed between V3.2x and
V4.0x. The way the kernel gets built changed between V3.2x and V4.0x. So
it matters VERY MUCH which version you're trying to do this on.
I'd strongly recommend that if the /genvmunix kernel recognizes the card and
seems to work (that is, the X server starts if you boot to multiuser), then
do what you're supposed to do: boot genvmunix, run doconfig without the -c
option, then merge in your customizations into the kernel configuration file
it spits out, instead of trying to hack the file manually.
By the way, there should be a release note in the V4.0 timeframe about the
change in the name for the ISA ATI Mach 64 card. I'm not sure what you'd
need in your ISA data for a generic card in V4.0 and later -- it might not
be what you've got.
==========================================================================
If it is going to work, you might be best off letting
doconfig build you a new configuration file based on
genvmunix. If you have any customizations to your
actual configuration you need to save, let doconfig
build the new one under a different name and then
see what the differences are. My guess is that you're
probably missing options or pseudo-devices that are
needed to resolve all the parts of the VGA driver.
===========================================================================
Received on Wed Aug 06 1997 - 23:09:57 NZST