[opensuse] Original INITRD_MODULES....
Stupid me, I forgot to comment out and to copy the original INITRD_MODULES line the /etc/sysconfig/kernel and just changed it. Now I have the problem that a module is not loaded which causes the display to stay in a relative low resolution during and after boot. It is also the reason that when switching from console to X-window, the X-window freezes for some seconds. Is there a way to rebuild the contents using the initrd file? I am using the opensuse 12.3-i586 version. Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 29/10/13 18:04, Frans de Boer escribió:
Stupid me, I forgot to comment out and to copy the original INITRD_MODULES line the /etc/sysconfig/kernel and just changed it. Now I have the problem that a module is not loaded which causes the display to stay in a relative low resolution during and after boot. It is also the reason that when switching from console to X-window, the X-window freezes for some seconds.
Is there a way to rebuild the contents using the initrd file? I am using the opensuse 12.3-i586 version.
Do you know which module ? it looks like a bug that needs to be corrected .. INITRD_MODULES is, most of the time a hack around to cover $someothercomponent 's ass. -- "Any real systematist (or scientist in general) has to be ready to heave all that he or she has believed in, consider it crap, and move on, in the face of new evidence. That is how we differ from clerics." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/29/2013 11:09 PM, Cristian Rodríguez wrote:
El 29/10/13 18:04, Frans de Boer escribió:
Stupid me, I forgot to comment out and to copy the original INITRD_MODULES line the /etc/sysconfig/kernel and just changed it. Now I have the problem that a module is not loaded which causes the display to stay in a relative low resolution during and after boot. It is also the reason that when switching from console to X-window, the X-window freezes for some seconds.
Is there a way to rebuild the contents using the initrd file? I am using the opensuse 12.3-i586 version.
Do you know which module ? it looks like a bug that needs to be corrected .. INITRD_MODULES is, most of the time a hack around to cover $someothercomponent 's ass.
No, I do not know which module, hence the question how to rebuild. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/30/2013 07:56 AM, Frans de Boer wrote:
On 10/29/2013 11:09 PM, Cristian Rodríguez wrote:
El 29/10/13 18:04, Frans de Boer escribió:
Stupid me, I forgot to comment out and to copy the original INITRD_MODULES line the /etc/sysconfig/kernel and just changed it. Now I have the problem that a module is not loaded which causes the display to stay in a relative low resolution during and after boot. It is also the reason that when switching from console to X-window, the X-window freezes for some seconds.
Is there a way to rebuild the contents using the initrd file? I am using the opensuse 12.3-i586 version.
Do you know which module ? it looks like a bug that needs to be corrected .. INITRD_MODULES is, most of the time a hack around to cover $someothercomponent 's ass.
No, I do not know which module, hence the question how to rebuild.
Well, I found that the buildin vesafb driver was not activated during boot. The original kernel somehow magical used that driver whiteout the vga=... switch on the kernel boot line!!? Even a recompile of the original sources did not work, I therefore assumed correctly that it must be an external parameter of some sort. Knowing that the vga=... switch is deprecated, how to make sure that the vesafb driver is used during IPL? Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-10-30 16:32, Frans de Boer wrote:
Knowing that the vga=... switch is deprecated, how to make sure that the vesafb driver is used during IPL?
I have a laptop on 12.3 that doesn't work correctly without "vga=791". Different parameters (display, video) fail to work. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
On 2013-10-30 16:36 (GMT+0100) Carlos E. R. composed:
Frans de Boer wrote:
Knowing that the vga=... switch is deprecated, how to make sure that the vesafb driver is used during IPL?
I have a laptop on 12.3 that doesn't work correctly without "vga=791". Different parameters (display, video) fail to work.
Video= only works when the gfxchip has KMS support. Vga= is used only for a few seconds of init, until KMS is triggered. Cmdline options other than video= (KMS) and vga= (non-KMS) are parameters used by boot loaders and/or installers. Your laptop likely has a rather old ATI (Rage 128 or older), Intel (810 or older) or MGA (any age) gfxchip, any of which simply do not have KMS support. Even with KMS support, using vga=ask still does what it always did, provide a list of modes supported by the video BIOS, from which a mode can be selected via keyboard for only that boot. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R. -
Cristian Rodríguez -
Felix Miata -
Frans de Boer