Bug 213045 - kldload vesa gives "error 19"
Summary: kldload vesa gives "error 19"
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 11.0-STABLE
Hardware: amd64 Any
: --- Affects Many People
Assignee: freebsd-bugs mailing list
URL:
Keywords: needs-patch
Depends on:
Blocks:
 
Reported: 2016-09-28 14:11 UTC by Harri
Modified: 2019-08-25 23:18 UTC (History)
12 users (show)

See Also:


Attachments
dmesg output (9.93 KB, text/plain)
2016-09-28 14:11 UTC, Harri
no flags Details
HP t610 TC boot (8.46 KB, text/plain)
2017-06-11 18:18 UTC, Valery
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harri 2016-09-28 14:11:37 UTC
Created attachment 175228 [details]
dmesg output

"kldload vesa" fails with

module_register_init: MOD_LOAD (vesa, 0xffffffff83477000, 0) error 19
sysctl_unregister_oid: failed to unregister sysctl

"vidcontrol -i mode" doesn't list any videomodes, either.
Comment 1 Harri 2016-11-05 08:44:33 UTC
Is there anything I could try? It would be a shame to use this laptop for anything else but FreeBSD.
Comment 2 Jason W. Bacon freebsd_committer 2017-03-15 23:25:16 UTC
I'm getting the same error on my Thinkpad T61, and yet vesa mode works fine.  I'm using it due to an apparent regression in the intel driver (bug #217689).

Sleep/resume is not working properly with vesa, though, and I found a suggestion that kldload vesa might fix this.

So what is error 19 for kldload?

From dmesg:

module_register_init: MOD_LOAD (vesa, 0xffffffff81cae000, 0) error 19
Comment 3 Valery 2017-06-11 18:18:07 UTC
Created attachment 183409 [details]
HP t610 TC boot
Comment 4 Valery 2017-06-11 18:24:13 UTC
I have the same problem, running FreeBSD r10.3,r11,12-CURRENT on my HP t610 Thin Client. See attached dmesg output in attachment "HP t610 TC boot".

I can boot only in Safe mode (both from USB flash or from HDD).
But not sure that it's because of vesa error...
Comment 5 Patrick McMunn 2017-08-19 17:48:38 UTC
This issue affects me on 11.1-RELEASE, as well on a Dell Dimension 2400. At the very least, this bug should be upgraded from "Affects Only Me" to "Affects multiple users".
Comment 6 Mateusz Piotrowski freebsd_committer 2018-06-23 11:15:05 UTC
I'm experiencing it on Dell XPS L702X[1]. 

 * I can log in.
 * I've got "module_register_init: MOD_LOAD (vesa, 0xffffffff810ed680, 0) error 19" in dmesg.
 * I cannot kldload vesa as I get the same errors as Harri [2].

The machine is running 12.0-CURRENT r335317 amd64.

[1]: https://wiki.freebsd.org/Laptops/Dell_XPS_L702X
[2]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213045#c0
Comment 7 patpro 2018-07-08 14:01:58 UTC
Same here on 11.1-RELEASE-p11 running on INTEL DQ77KB motherboard with Intel Core i3-3220T CPU.
Comment 8 Michael Siegel 2018-07-17 10:40:01 UTC
I'm having the same problem on 11.2-STABLE (i386).

This is what pciconf -lv says about my graphics card:
RS200M [Radeon IGP 330M/340M/345M/350M]
Comment 9 Max Kostikov 2018-12-14 19:57:06 UTC
Have the same error with Matrox MGA G200e [Pilot] ServerEngines (SEP1) on 12.0-RELEASE

module_register_init: MOD_LOAD (vesa, 0xffffffff810f9770, 0) error 19
Comment 10 Ftn 2019-03-01 07:50:57 UTC
Have the same error with NVIDIA Corporation GT218 [ION] on 11.2-RELEASE-p9 (amd64) (GENERIC)

kernel: module_register_init: MOD_LOAD (vesa, 0xffffffff80ff4580, 0) error 19
Comment 11 Jason Mours 2019-06-06 13:04:31 UTC
Seeing kldload vesa error 19 with FREEBSD 12.0-RELEASE r341666 GENERIC

module_register_init: MOD_LOAD (vesa, 0xffffffff8059000, 0) error 19
sysctl_unregistered_oid: failed to unregister sysctl

efifb loads

vidcontrol shows no alternative video modes.
Comment 12 Hilko Meyer 2019-08-25 23:18:40 UTC
Have the same problem and found the reason. The new console driver vt(4) is default since 11.0 and the old syscons(4) is retiered. But it lacks VESA support. See https://wiki.freebsd.org/Newcons The last edit of that wiki page was almost a year ago. No idea about the current state.