Solved vesa won't load

I tried to load vesa kldload vesa and i get an error message kldload: an error occurred while loading the module. Please check dmesg(8) for more details.

The dmesg that corresponds to this this error is
Code:
module_register_init: MOD_LOAD (vesa, 0xffffffff8251100, 0) error 19
sysctl_unregister_oid: failed to unregister sysctl

This happens both on virtualbox and livecd.
 
You don't need to load it, it's already part of the GENERIC kernel.
 
You don't need to load it, it's already part of the GENERIC kernel.
I read that somewhere but I'm sure there's an explicit message stating that such module have been loaded. Apparently, mine doesn't. I'm new to this, so I just followed what mentioned explicitly in the text but get such error instead. I tried to list the video mode using vidcontrol -i mode as in the handbook, but nothing listed save for the header. Did I miss something?
 
There's a difference between vt(4) and sc(4), recent FreeBSD versions have switched to vt(4). It's not as feature complete as sc(4) yet though. The reason for the switch is largely due to KMS. The older console driver didn't support it and this caused problems with the latest graphics drivers (which are mostly KMS based these days).

https://wiki.freebsd.org/Newcons
 
There's a difference between vt(4) and sc(4), recent FreeBSD versions have switched to vt(4). It's not as feature complete as sc(4) yet though. The reason for the switch is largely due to KMS. The older console driver didn't support it and this caused problems with the latest graphics drivers (which are mostly KMS based these days).

https://wiki.freebsd.org/Newcons
Well that should explain it. I'm still getting conditioned to new concept and oblivious to such change. The handbook could use some mention on this one. Luckily there's this forum.
 
Don't worry, sometimes things move so fast even I lose track of all the changes ;)
 
I knew that someone will mention such thing is mentioned here and here. It's just so happen that a beginner would likely to read these handbook as it is suggested for the first section(like a textbook,no skipping around). I'm talking about 3.2.3 just after the introduction to virtual console where it mentions to load vesa. A beginner like me would highly appreciate a mention on how it may not work for the newer console driver:).

I should have make the context clearer next time. Cheers mate.
 
It's just so happen that a beginner would likely to read these handbook as it is suggested for the first section(like a textbook,no skipping around).
This still happens to me on different topics as well. Once one is familar with something it is difficult to remember how it was at the beginning.
I should have make the context clearer next time. Cheers mate.
I think the misunderstanding was my fault. Basically the handbook is excellent. I think it is difficult to find the balance to give the right amount of information. To little is not good and too much or too detailed is not good either.
 
There's a difference between vt(4) and sc(4), recent FreeBSD versions have switched to vt(4). It's not as feature complete as sc(4) yet though. The reason for the switch is largely due to KMS. The older console driver didn't support it and this caused problems with the latest graphics drivers (which are mostly KMS based these days).

https://wiki.freebsd.org/Newcons

Hello SirDice,

forgive me stupid question. I’ve checked the https://wiki.freebsd.org/Newcons about vt(4) and it works actually when I use kldload i915kms it takes me out from ugly 80x25 console size and allows me to use native screen resolution with 160x50 stty size, that’s great!

But can you advice how can I make this change permanent? So it will stay like that also after reboot?

Thank you and have great day, bye.
 
Back
Top