Re: NetBSD installation woes on Sun Blade 100

On Thu, Jun 25, 2020 at 3:05 PM Connor McLaughlan <[email protected]> wrote:
>
> On Thu, Jun 25, 2020 at 2:33 PM Martin Husemann <[email protected]> wrote:
> >
> > On Thu, Jun 25, 2020 at 12:15:22PM +0200, Connor McLaughlan wrote:
> > > So i guess i am good to install it and use it from here?
> >
> > Yes, and also Michael now knows what he needs to request a pullup for ;-)
> >
> > Martin
>
> A follow up:
>
> The kernel now detects and initializes the mach64 and reports it at bus id 19
>
> dmesg output:
> [     1.000000] ppb0 at pci0 dev 5 function 0: Digital Equipment DC21152 PCI-PCI
>  Bridge (rev. 0x03)
> [     1.000000] pci1 at ppb0 bus 1
> [     1.000000] pci1: i/o space, memory space enabled
> [     1.000000] machfb0 at pci0 dev 19 function 0: ATI Technologies Rage XL (rev
> . 0x27)
> [     1.000000] machfb0: using MMIO aperture
> [     1.000000] machfb0: 16 MB aperture at 0x03000000, 4 KB registers at 0x00426
> 000
> [     1.000000] machfb0: 128 KB ROM at 0x00440000
> [     1.000000] machfb0: ref_freq=29.498MHz
> [     1.000000] machfb0: 8192 KB SDRAM 114.992 MHz, maximum RAMDAC clock 230 MHz
> [     1.000000] machfb0: initial resolution 1280x1024 at 8 bpp
> [     1.000000] wsdisplay0 at machfb0 kbdmux 1: console (default, vt100 emulatio
> n)
>
>
> But afterwards the Xserver can not initialize it's own mach64 driver
> on id 00:19:00:
>
> Xorg.0.log:
> [  4189.080] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
> [  4189.080] (II) MACH64(0): Creating default Display subsection in
> Screen section
>     "Builtin Default ati Screen 0" for depth/fbbpp 24/32
> [  4189.081] (==) MACH64(0): Depth 24, (--) framebuffer bpp 32
> [  4189.081] (==) MACH64(0): Using EXA acceleration architecture
> [  4189.083] (EE) Unable to map mmio aperture. Invalid argument (22)
> [  4189.084] (WW) MACH64: Mach64 in slot 0:19:0 could not be detected!
> [  4189.084] (II) UnloadModule: "mach64"
> [  4189.084] (EE) Screen(s) found, but none have a usable configuration.
> [  4189.084] (EE)
> Fatal server error:
> [  4189.085] (EE) no screens found(EE)
>
> So far i can only use the "wsfb" driver.
>
> How can i fix the ati-driver init?

I found a thread with a possible solution here:

https://mail-index.netbsd.org/port-sparc64/2016/08/23/msg002564.html

I either need to run the kernel at a lower security level or use
sysutils/aperture to do it.

It seems sysutils/aperture no longer exists, so my only option is to
lower the kernel securitylevel to get X started.
Is that about correct?