Re: problem compiling wscons kernel on pmax

Izumi Tsutsui ([email protected]) wrote:

>Hmm, maybe you don't have dtkbd, then how about the attached diff?

Yes, it does the trick. I indeed do not have dtkbd. I think it should not
be necessary on a DecSystem 5000/150 (3MIN).


>--- files.pmax_wscons.orig      2005-02-19 11:34:57.000000000 +0900
>+++ files.pmax_wscons   2005-02-19 11:34:39.000000000 +0900
>@@ -8,7 +8,7 @@
> attach dz at ibus with dz_ibus
> file   arch/pmax/ibus/dz_ibus.c        dz_ibus
> 
>-device lkkbd: wskbddev
>+device lkkbd: wskbddev, lkkbdmap
> attach lkkbd at dz with dzkbd
> file   dev/dec/dzkbd.c                 dzkbd needs-flag


Now the next problem is that neither with my customized nor with the stock
NetBSD 2.0 WSCONS kernel do I get an X-server an the screen. XdecNetBSD
does run (I can see it with top), but all I see is five garbeled blocks of
random pixels in the upper ca. 3% of my screen. Could it be incompatible
with my setup?
xdm.log reads like this:

XdecNetBSD: screen 0: MX (MFB), 1280x1024
ioctl(WSDISPLAYIO_PUTCMAP) fails: Inappropriate ioctl for deviceCould not
init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!

The fonts problem do not serve as an explanation in my opinion.
Here's the output from dmesg:

NetBSD 2.0 (WSCONS) #0: Wed Dec  1 20:43:48 UTC 2004

builds@build:/big/builds/ab/netbsd-2-0-RELEASE/pmax/200411300000Z-obj/big/b
uilds/ab/netbsd-2-0-RELEASE/src/sys/arch/pmax/compile/WSCONS
DECstation 5000/150 (3MIN)
total memory = 32768 KB
avail memory = 28264 KB
mainbus0 (root)
cpu0 at mainbus0: MIPS R4000 CPU (0x430) Rev. 3.0 with MIPS R4010 FPC Rev.
0.0
cpu0: 8KB/16B direct-mapped L1 Instruction cache, 48 TLB entries
cpu0: 8KB/16B direct-mapped write-back L1 Data cache
cpu0: 1024KB/32B direct-mapped write-back L2 Unified cache
tc0 at mainbus0: 12.5 MHz clock
ioasic0 at tc0 slot 3 offset 0x0
le0 at ioasic0 offset 0xc0000: address 08:00:2b:27:7b:b6
le0: 32 receive buffers, 8 transmit buffers
zsc0 at ioasic0 offset 0x100000
vsms0 at zsc0 channel 0
wsmouse0 at vsms0 mux 0
zstty0 at zsc0 channel 1
zsc1 at ioasic0 offset 0x180000
lkkbd0 at zsc1 channel 0
wskbd0 at lkkbd0: console keyboard
zstty1 at zsc1 channel 1
mcclock0 at ioasic0 offset 0x200000: mc146818 or compatible
asc0 at ioasic0 offset 0x300000: NCR53C94, 25MHz, SCSI ID 7
scsibus0 at asc0: 8 targets, 8 luns per target
mfb0 at tc0 slot 0 offset 0x0: 1280x1024, 1bpp
wsdisplay0 at mfb0 kbdmux 1: console (std, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
Kernelized RAIDframe activated
scsibus0: waiting 2 seconds for devices to settle...
....

With both kernels I get the following error message on startup to the
console:

wsconscfg: WSDISPLAY0_ADDSCREEN: Cannot allocate memory
wsconscfg: WSDISPLAY0_ADDSCREEN: Cannot allocate memory
wsconscfg: WSDISPLAY0_ADDSCREEN: Cannot allocate memory
wsconscfg: WSDISPLAY0_ADDSCREEN: Cannot allocate memory
wsconsctl: WSCBDIO_SETENCODING: Invalid argument  

is some of my setup at fault?


-- 
Georg Schwarz    http://home.pages.de/~schwarz/
 [email protected]     +49 177 8811442