On Wed, 10 Feb 2021, Mouse wrote:
What would be involved in switching to genfb? Just disable i915drmkms,
or is there more to it?
Yes, disable i915drmkms, then set your screen resolution using
`gop' (UEFI/amd64) or `vesa' (BIOS/x86) in the bootloader.
https://www.unitedbsd.com/d/271-wfsb/6
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 anywa
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 \
> 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 0x83
>> 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 (i915drmk
On Tue, 9 Feb 2021, David Brownlee wrote:
AFAIK X requires a wsdisplay to run on - which you don't seem to get
with a serial console. I wonder if it might be possible to run it on
genfb?
Yes. Mouse, can post the output of this:
$ ls -l $(which Xorg)
-RVP
hello. What video driver/kernel driver are you using to drive the
display? I had a
similar problem using the intelfb(4) driver. I had to revert to the genfb(4)
driver to get the
VGA port to work properly. The Displayport /HDMI ports worked fine under the
intelfb(4)
driver, but the VG
>> Is there any way I can test for it?
> Connect something to the HDMI outputs?
I got out my HDMI-to-VGA converter, the same one I've used for HDMI
stuff on this before.
It doesn't work to just switch to HDMI. xrandr does recognize when
HDMI is connected (and which HDMI connector is connected),
On Tue, 9 Feb 2021 at 17:59, Mouse wrote:
>
> I don't know whether this is kernel or X11. There are things pointing
> each way.
>
> At work, I've got 9.1 on an amd64 machine. When I boot it normally -
> console on screen/keyboard - X works fine.
>
> But I'm having an issue. The machine is reboo
>> Is there any way I can test for it?
> Connect something to the HDMI outputs?
Worth trying. I should have thought of that myself.
However, neither of the (physical) HDMI outputs is paired with DP3, the
output RandR recognizes is connected when the VGA monitor is connected.
So I don't expect it
> Is there any way I can test for it?
Connect something to the HDMI outputs?
> Could it be the case that the X server expects some aspects of the video har$
That's certainly plausible. Is there any way I can test for it? Some
way to, for example, have the kernel do whatever it would do for video
console but still keep console I/O going to com2? (I would expect that
to b
Could it be the case that the X server expects some aspects of the video
hardware to be initialized by the video console driver that are uninitialized
in the serial console case? E.g., as you say outputs are shared between HDMI
and VGA, the X video simply goes to the HDMI output?
I don't know whether this is kernel or X11. There are things pointing
each way.
At work, I've got 9.1 on an amd64 machine. When I boot it normally -
console on screen/keyboard - X works fine.
But I'm having an issue. The machine is rebooting on me, sometimes,
and I don't know whether it's some
14 matches
Mail list logo
