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=-3.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,NICE_REPLY_A autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 12059 invoked from network); 5 Sep 2021 23:34:44 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 5 Sep 2021 23:34:44 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Received: from smtp.vivaldi.net ([31.209.137.12]) by 4ess; Sun Sep 5 19:25:06 -0400 2021 Received: from localhost (localhost [127.0.0.1]) by smtp.vivaldi.net (Postfix) with ESMTP id 8E645BD06B for <9front@9front.org>; Sun, 5 Sep 2021 23:16:51 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.vivaldi.net 8E645BD06B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vivaldi.net; s=default; t=1630883811; bh=j3vNtNvIdu6gKw7vRXmCYX8C/i0Hp/xRxnk8rribypY=; h=Subject:To:References:From:Date:In-Reply-To:From; b=kOKucv7zOvL4wsHqvjGij2cfKJQ8E3R7NHM8auX2AerR1OeZCSorgPLH8Z2l2PDcJ 7SWBaipHlmOW0voByXgX414oC+D+XZLn1UJyOKJAdTgr6Imfidae83Mis2ic9Dt3WR kN4tIIBhLbQ0qLcvKGf/cO8OUTa1S5SsG6TGWvDvQnKu6ndGtcACruTs7G/Nrz7ha5 6x9TMt9W+OREXCg/bGQXTwBN5/cVbbton2oJB+kBkLCAsiwCiyQEYTHwEo6WodRSTe TH1N+TiV/wZzSHBo1sf6FA35h5U9YH/8M8jyzS9xq7GLAIxJ5l5y3rb3RTxgYyyaeG qZXVkEjYNWM1A== X-Virus-Scanned: Debian amavisd-new at smtp.vivaldi.net Received: from smtp.vivaldi.net ([127.0.0.1]) by localhost (mxo.viv.dc01 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JIbKg3aU27ai for <9front@9front.org>; Sun, 5 Sep 2021 23:16:47 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.vivaldi.net 9CE94BD054 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vivaldi.net; s=default; t=1630883805; bh=j3vNtNvIdu6gKw7vRXmCYX8C/i0Hp/xRxnk8rribypY=; h=Subject:To:References:From:Date:In-Reply-To:From; b=Z0vZpMFfm+dxNknAiya1G0Obbk0pRDaxtTS8bMByaMj/lEN6AdBuLcHGVMbpjVwHd M4IwLqYsYrKW3e8ySnYeWzGsj2bOYsO3FbrxkLRdxIoW5KmKFzWAFe+rm4W7GnOwrr tTJH7RLgakPeKHxctlbsfK6x4iVaMASSBrVYvRcK6CZ/Vb0kwGO9ntWcvqWdK2t89/ Xa/TZ+77iEnmxnGf00pPvVMF+2a1YfurRAd5piCmr9w2+NA4aoXdKN35djSAoPVoSf gbqKozdXH3UILV3b8iYQy0RUBlnVO7ggVyECGQPbnXkELyPUHvEF1VigI4w8EtZ0ZY IHrwyleNKR6zA== To: 9front@9front.org References: From: lyndsay Message-ID: Date: Sun, 5 Sep 2021 17:18:12 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: abstract self-signing frontend Subject: Re: [9front] trident cyber 9525 graphics glitches Reply-To: 9front@9front.org Precedence: bulk oh my god, i can't believe i didn't think of simply trying a lower resolution. i'm an idiot sometimes. the graphics DO in fact work fine, and it accepts 24-bit color, using a 640x480 resolution! i would definitely be interested in trying to debug and fix the issue at the source if you/others on the list are interested in helping with that, but i know that's a tall task and probably not a priority for most people, so just downscaling looks like it will work as a quick superficial fix. thank you!! On 9/5/21 4:52 PM, qwx wrote: > 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