Hello,
Sorry to revive an old mail chain, but I did more digging on this subject
and I tested out OpenBSD 6.5 to see how neomagic would perform and it
definitely is better than using vesa.
Interestingly, it works perfectly fine without XAA from Xorg server, it
just falls back on shadowfp and uses a depth of 16 without acceleration.
After searching the changelogs for both OpenBSD and X, I have gathered
the following information:
OpenBSD 6.5 is the latest release with neomagic included and it ships
with Xorg server (1.19.x) – this version of Xorg server does not have
XAA support, it was dropped in 1.13.x.
The last version of Xorg server that supported XAA is 1.12.x (Open BSD
5.3 is the latest that ships with this).
My two questions are:
1. Can neomagic be loaded into a release >=6.6 even though it’s not
there to start with (this is probably more trouble than it’s worth)
2. Can x server be downgraded to a specific version in an OpenBSD
release (I’ve searched mailing lists, etc. and have found nothing
on this topic)
Out of these two, I’d be fine with running a 6.5 OpenBSD with a
downgraded version of X if possible.
Thank you for your help!
From: Thomas Vetere
Sent: Tuesday, May 4, 2021 2:27 PM
To: Matthieu Herrb
Cc: [email protected]
Subject: Re: ThinkPad 600e (NeoMagic MagicMedia 256AV (NM2200)) X11 - neo
module not found
Il Gio 15 Apr 2021, 7:11 PM Thomas Vetere <[email protected]> ha
scritto:
Success! I noticed the error with fbbpp value of 24 so I played
around with this in the config. Turns out a value of 16 works fine.
Logging my xorg.conf file here in case anyone else has a NeoMagic
chip and wants to try and get vesa to work with OpenBSD >= 6.6.
=====================================================================================
Section "Device"
Identifier "mycard"
Driver "vesa"
EndSection
Section "Screen"
Identifier "myscreen"
Device "mycard"
DefaultFbBpp 16
EndSection
On Thu, Apr 15, 2021 at 3:15 PM Thomas Vetere <[email protected]>
wrote:
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
