Subject: port-acorn32/17258: vidcvideo initialisation corrupts display
To: None <gnats-bugs@gnats.netbsd.org>
From: Ben Harris <bjh21@netbsd.org>
List: netbsd-bugs
Date: 06/14/2002 23:24:42
>Number:         17258
>Category:       port-acorn32
>Synopsis:       vidcvideo initialisation corrupts display
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-acorn32-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 14 15:25:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Ben Harris
>Release:        2002-06-06
>Organization:
>Environment:
NetBSD 1.6A (RPC_WSCONS) #0: Thu Jun  6 23:42:21 UTC 2002
    bjh21@southeast-iceland:/usr/src/sys/arch/acorn32/compile/RPC_WSCONS

>Description:
In /var/log/dmesg.out, I have (excerpted):

cd0 at atapibus0 drive 1: <PHILIPS CDRW2412A, 5VO1214DS22435, 0.01000> type 5 cdrom removable
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
wd0 at wdc0 channel 0 drive 0: <FUJITSU MPA3017ATU>
wd0: drive supports 32-sector PIO transfers, LBA addressing
wd0: 1668 MB, 3390 cyl, 16 head, 63 sec, 512 bytes/sect x 3417976 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
fdc0 at pioc0 offset 0x3f0-0x3f7 irq 12 drq 0x00002000
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
com0 at pioc0 offset 0x3f8-0x3ff irq 10: ns16550a, working fifo
lpt0 at pioc0 offset 0x278-0x27b irq 0
iomd0 at mainbus0: IOMD20 version 2
iomd0: DRAM refresh=16us
clock0 at iomd0
rpckbd0 at iomd0
wskbd0 at rpckbd0: console keyboard
iic0 at iomd0
rtc0 at iic0 addr 0xa0: PCF8583 clock base 32.768KHz
todclock0 at rtc0
wsqms0 at iomd0
wsmouse0 at wsqms0 mux 0
vidc0 at mainbus0: VIDC20
vidcvideo0 at vidc0: refclk=24MHz 2048KB VRAM : using 640 x 480, 16bpp
wsdisplay0 at vidcvideo0 kbdmux 1: console (std, vt100 emulation), using wskbd0

On the console, however, the text between the "cd0" and "wsdisplay0" lines
was missing.  It looked to me as if the screen jumped when vidcvideo0
initialised, so my guess is that it reset the hardware scrolling or
somesuch.

>How-To-Repeat:
Boot a Risc PC in a 640x480 screen mode and watch the console carefully.
Having unclean filesystems or booting single-user probably helps.

>Fix:



>Release-Note:
>Audit-Trail:
>Unformatted: