hello. I'm guessing you're running into the same issue I did with the
intelfb driver. My
solution was to build a kernel with the genfb(4) driver included and the
intelfb driver
excluded. this gives me VGA video at the expense of a bit of X performance,
which I didn't
care about
On Tue, 9 Feb 2021, RVP wrote:
Yes. Mouse, can post the output of this:
$ ls -l $(which Xorg)
If the Xorg server is setuid, then you can tell it to open
/dev/ttyE4 directly by adding a `vt5' to the xinit command:
#! /bin/sh
exec xinit /home/mouse/X/x-client -- /usr/X11R7/bin/X vt5 \
On Fri, Feb 05, 2021 at 08:10:06PM -0500, Mouse wrote:
> > It is possible for write() calls to fail partway through, after
> > already having written some data.
>
> It is. As you note later, it's also possible for read().
>
> The rightest thing to do, it seems to me, would be to return the
>>> It is possible for write() calls to fail partway through, after
>>> already having written some data.
>> The rightest thing to do, it seems to me, would be to return the
>> error indication along with how much was successfully written (or
>> read). But that, of course, requires a completely
> What video driver/kernel driver are you using to drive the display?
i915drmkms and intelfb in the kernel
i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 5912 (rev. 0x04)
i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0)
intelfb0 at i915drmkms0
intelfb0: framebuffer at
>> AFAIK X requires a wsdisplay to run on - which you don't seem to get
>> with a serial console.
The boot-time autoconf messages disagree:
i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 5912 (rev.
0x04)
...
i915drmkms0: interrupting at ioapic0 pin 16
