[talk] Log kernel info for vesa driver

fire crow fire at firecrow.com
Sat Oct 21 14:57:20 EDT 2017

On Oct 21, 2017 1:43 PM, "fire crow" <fire at firecrow.com> wrote:

Hi all,
Off hand does anyone know how to log information from inside a kernel
module, debugging vesa.ko.


Nvm, found it, uprintf,


On Oct 21, 2017 1:14 PM, "fire crow" <fire at firecrow.com> wrote:

On Oct 21, 2017 1:03 PM, "Pete Wright" <pete at nomadlogic.org> wrote:

On 10/20/2017 21:21, fire crow wrote:

> Hi thanks for the tips, 12.0 current from the svn head and drm-next-kmod
> from ports didnt load up when vt initialized on boot. Im currently looking
> at the vesa kmod, getting this error that im trying to work out.
> $ kldload vesa
> module_register_init: MOD_LOAD (vesa, 0x< f and numbers>, 0) error 19
> sysctl_unregister_oid: failed to unregister sysctl

does your console load w/o attempting to load the vesa driver?  if it does
you might want to take a stab at using the SCFB xorg driver:

xf86-video-scfb-0.0.4_5        X.Org syscons display driver

It's a software driver, which while it may be slow - but it certainly is
usable for browsing, hacking and email.  it is what i was using on my
systems until we could get the drm-next code in a semi-usable state.

i'm not %100 sure why vesa would refuse to load the as a kmod - might be
worth pinging freebsd-x11@ if you get frustrated with it :)


Pete Wright
pete at nomadlogic.org

Thanks, I was able to get scfb working a couple months ago if i remember
right. It was slow but usable.

Thing is im not in X anymore, im just rocking on the inital vt console to
develop, using links for a browser etc. Im only after smaller text and
nicer fonts, but trying to pull it off in a world without X.

Readig vesa kmod code now, im hoping i can just update what devices the
driver identifies and use existing code for it. Fingera crossed.


talk mailing list
talk at lists.nycbug.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nycbug.org/pipermail/talk/attachments/20171021/0f19d783/attachment.html>

More information about the talk mailing list