From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from duke.felloff.net ([216.126.196.34]) by ur; Sun May 1 00:05:20 EDT 2016 Message-ID: <31b8e79ee083187b58bac044158ee402@felloff.net> Date: Sun, 1 May 2016 06:05:10 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org Subject: Re: [9front] installing 9front on Dell Optiplex 790 In-Reply-To: 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: transactional API wrapper storage database that message looks like its from trying to read edid info from displayport. if theres nothing connected to displayport, and you only use the vga connector, then it doesnt matter. its hard to tell from your description if its an issue with the fdi or the transcoder/port. you might check the monitors OSD and see if it got a stable signal. maybe the fdi is just misprogrammed sending garbage digital data to the transcoder explaining the snow. could you try a displayport->vga adapter? or a displayport monitor? that might help distinguishing between the two scenarios. some systematic debugging is needed to get that driver working. i wonder why vesa doesnt work at all... you said you get a black screen, so does that mean the monitor doesnt even turn on? (no signal) maybe we hit some issue with realemu when setting up graphics, but we dont see the error message? please run the commands with filedescriptors 1 and 2 redirected to a logfile. or you could connect to the machine with drawterm/cpu and then run aux/vga from that with #i #v #$ and #P bound before /dev. aux/vga has some experimental support for display selection, by appending #N to the mode where N is display number counting from 1, so you could also try aux/vga -m vesa -l '800x600x32#2' ect... if we could get vesa to setup the graphics, even if not with native resolution of your monitor, we can make a trace of all register reads and writes and get some initial to start from. you probably *just* want your graphics to work and not become a driver programmer... but its difficult to write drivers without access to the hardware and no way to test stuff... and without any debug output, i cannot help you at all. if this is a new machine, it might have support for UEFI, which might provide us with a framebuffer... as a last resort... if nothing works, try a diffrent computer or try a different discrete graphics card maybe... -- cinap