From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 8806 invoked from network); 5 Sep 2021 23:05:28 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 5 Sep 2021 23:05:28 -0000 Received: from wopr.sciops.net ([216.126.196.60]) by 4ess; Sun Sep 5 18:52:49 -0400 2021 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sciops.net; s=20210706; t=1630882359; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=xX/DWoLhDBh6J5kYFm6nfeq84MUcwPmJcxOP0e+dat8=; b=RBU/b0RiZ3w3c0cavSDmQ0ht+LPZhHbgPM3wDM1shKYoBrBUDK13W7HEbWzEF0YiP8aoSh ngBiwFFkgXbplnKWmzEY386TbupQjtsKRaGPVviSQTLsFfyiyqMP4/f7oduCpbB+simH52 vFgZKorM6MAMyiDJhrMY8cKQpyoWwbY= Received: by wopr.sciops.net (OpenSMTPD) with ESMTPSA id 1175a0ac (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO) for <9front@9front.org>; Sun, 5 Sep 2021 15:52:39 -0700 (PDT) Message-ID: From: qwx Date: Mon, 06 Sep 2021 00:52:37 +0200 To: 9front@9front.org In-Reply-To: <1630860700604.2131728698.1474874245@vivaldi.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: grid-oriented app-oriented generator Subject: Re: [9front] trident cyber 9525 graphics glitches Reply-To: 9front@9front.org Precedence: bulk Hi lyndsay, > first of all, the vanilla /lib/vgadb does not have an entry with the right > BIOS identifier for this device, so it wasn't giving me any graphical > output regardless of the settings i chose at first. i was able to revise > the cyber938x entry in /lib/vgadb to add the appropriate line (diff) and > inject that into the install ISO, and it now does produce some output with > `aux/vga -m xga -l 1024x768x16`. (it does not work with -m vesa.) this gpu > technically supports 24-bit color modes, but vga dies telling me there's > not enough memory if i try to use one, which is also a known problem on > solaris that they say to fix by using a 16-bit mode. The device's pci did may be missing from /lib/vgadb simply because no one has tested that particular device, but since you can at least get a picture, it can be added, especially if modesetting with vesa doesn't work. > the issue now is that although i can get the display to load, the screen > output is garbled. it properly renders the cursor, including its movement, > and responds to my keyboard too, but everything else is totally broken. it > IS clear where the things displayed on the screen are coming from, so it's > not like it's just dumping nonsense from memory. i'll link two pictures > showing what this looks like - the first is the initial screen the > installer drops to where it asks for mouse type, the second is the default > rio layout after hitting enter on that screen: I think this is a bug either in vga(8) or elsewhere and it's not limited to this driver. My 380d with a neomagic gpu behaves similarly (sysinfo: [1]). 24bit modes cannot be enabled, though you could try the same command 2-3 times in a row, this sometimes works on these drivers despite the memory errors, though probably without useful results. I also had a garbled picture, but only on the bottom of the screen, again indicating similar memory issues. Using a *lower resolution* works. An even lower resolution with 24bit color may have worked too, I don't remember. The cursor is ok probably because it's the hardware cursor, which is handled elsewhere (someone please correct me if I'm wrong). Hardware issue or bugs, there are no two ways of fixing it. These drivers are very old and no one has touched them since forever, mostly because no one has really used 9front on hardware this old, and those who have haven't arsed to fix them (sorry). I could try to look at my 380d at some point if it still even boots and the stupid pcmcia dongle works, but these are empty promises. If you'd like to try debugging this, we'll help however we can. Hope this clears it up somewhat, qwx [1] http://plan9.stanleylieber.com/hardware/thinkpad/380d/2635-3au/sysinfo