That stinks. Yeah, this thing is a dinosaur. I will try that. Thanks for
your help!

On Thu, Apr 15, 2021, 2:27 PM Matthieu Herrb <[email protected]> wrote:

> On Thu, Apr 15, 2021 at 09:05:51AM -0400, Thomas Vetere wrote:
> > Hello everyone,
> >
> > I am currently running OpenBSD 6.8 on an IBM ThinkPad 600e. I am using
> > the GENERIC kernel and the only modifications that I have to the system
> > is to disable
> >
> > ACPI in rc.shutdown in order to circumvent KARL (this machine fails to
> > boot in ACPI mode so I have to use APM).
> >
> > The other day I setup X11 with xenodm and when I tried to launch cwm I
> > kept getting the error message “Unable to open display 0.0”.
> >
> > I read the manual pages for X11 and found where the logs were. After
> > reading through the logs, I can see that I have the message “Screens
> > found but none have a usable configuration”. Also within the logs, I
> > can see that it is not loading the proper module for my Graphics
> > processor. I made sure that my graphics processor is supported by OpenBSD
> > and you can see that it is here:
> >
> > https://man.openbsd.org/neo.4
>
> This driver is for neomagic *audio* chipsets not graphics.
> >
> > In the log it says this module “neomagic” does not exist and it falls
> > back on the vesa module it seems. If this module is loaded into the
> > kernel at the installation time of OpenBSD, could this be a hardware
> > detection issue? If so, is there a way that I can enable this module in
> > order to see if that will fix the issue in configuring the screen?
> >
> > Here is the output of various log files:
>
> Hi,
>
> The neomagic(4) X.Org driver was removed during the OpenBSD 6.6
> release cycle because it's not supported by X.Org upstreams
> anymore. In particular the driver only supported XAA 2D acceleration,
> and recent X servers have dropped support for that acceleration code
> (only EXA and glamor are supported nowadays).
>
> You may be able to get X working using the (unaccelerated)
> xf86-video-vesa driver (see vesa(4)). Create an /etc/X11/xorg.conf
> file containing just
>
> Section "Device"
>         Identifier "mycard"
>         Driver "vesa"
> EndSection
>
> The drawback with this approach is that if the Video BIOS of your
> machine doesn't include support for the pannel of your laptop, the
> vesa driver may not be able to drive it at its native resolution.
>
> --
> Matthieu Herrb
>

Reply via email to