SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You won't be able to get KMS working "straight from the lilo getgo." KMS is part of the linux kernel and lilo launches before the kernel. If you build KMS into the kernel, however, you can get it to load within the first few seconds of the kernel loading.
Adam
Ok, I see.
So you saying I'm forced to use vesa at 1024x768 from the lilo getgo? Or is there a way?
The way I figured it was that when lilo starts, and i hit enter to load the kernel, it loads said kernel, and in turn would load any drivers and framebuffers I have installed. I guess i am missing some thing fundamental here.
So you saying I'm forced to use vesa at 1024x768 from the lilo getgo? Or is there a way?
The way I figured it was that when lilo starts, and i hit enter to load the kernel, it loads said kernel, and in turn would load any drivers and framebuffers I have installed. I guess i am missing some thing fundamental here.
No, you pretty much understand it. But when you say "from the lilo getgo" I assume you mean you want lilo at that resolution. Since that's before the kernel loads, the kernel drivers have no control over the resolution when lilo is on the screen.
If you don't want the kernel to switch to the vesa framebuffer console before then switching to the inteldrmfb console, and you want the inteldrmfb console to start right away, you will either need to add the intel DRM driver to an initrd (as well as any firmware that the DRM code depends on) or you will need to compile the intel DRM driver into the kernel.
No, you pretty much understand it. But when you say "from the lilo getgo" I assume you mean you want lilo at that resolution. Since that's before the kernel loads, the kernel drivers have no control over the resolution when lilo is on the screen.
If you don't want the kernel to switch to the vesa framebuffer console before then switching to the inteldrmfb console, and you want the inteldrmfb console to start right away, you will either need to add the intel DRM driver to an initrd (as well as any firmware that the DRM code depends on) or you will need to compile the intel DRM driver into the kernel.
Adam
I don't want 1366x768 at the lilo prompt, but rather after the kernel has been loaded by lilo.
I have compiled DRM driver in to the kernel, when lilo has loaded the kernel, a few lines fly by (at 800x600) and then DRM driver kicks in (1366x768). This is what im trying to fix, the lilo resolution support, as it seems to be using vesa still, after the kernel has loaded.
Maybe there is some kind of kernel driver initialisation priority (even if there is no module, it's built in)?
This is a Intel i5 M2430 Sandy Bridge. I can't seem to wrap my head around this. All I want is the kernel to kick in DRM right after I have loaded it via lilo.
The intel DRM fb console should kick in within seconds of the kernel loading. On my laptop, with the intel DRM compiled in and KMS enabled, you can see that the kernel is switching to the intel DRM framebuffer console between 1 and 2 seconds after the kernel loads:
Code:
[ 1.354396] fbcon: inteldrmfb (fb0) is primary device
[ 1.355265] [drm] Changing LVDS panel from (+hsync, -vsync) to (-hsync, +vsync)
[ 1.957129] fb0: inteldrmfb frame buffer device
[ 1.957131] drm: registered panic notifier
[ 2.000370] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
I doubt very much you can get it to switch faster than that. What does your dmesg show?
The intel DRM fb console should kick in within seconds of the kernel loading. On my laptop, with the intel DRM compiled in and KMS enabled, you can see that the kernel is switching to the intel DRM framebuffer console between 1 and 2 seconds after the kernel loads:
Code:
[ 1.354396] fbcon: inteldrmfb (fb0) is primary device
[ 1.355265] [drm] Changing LVDS panel from (+hsync, -vsync) to (-hsync, +vsync)
[ 1.957129] fb0: inteldrmfb frame buffer device
[ 1.957131] drm: registered panic notifier
[ 2.000370] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
I doubt very much you can get it to switch faster than that. What does your dmesg show?
So as you can see, the intel DRM framebuffer console kicks in around second 2.44. Seems perfectly normal and reasonable to me. I doubt there's much you could do to improve it as I'm not familiar with any method to force the kernel to load specific drivers first.
So as you can see, the intel DRM framebuffer console kicks in around second 2.44. Seems perfectly normal and reasonable to me. I doubt there's much you could do to improve it as I'm not familiar with any method to force the kernel to load specific drivers first.
Adam
Ok, well that cleared up a few things then. Thank you very much for your time Have a good one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Have a good one.
