FS#18040 - [kernel26] incorrect display of boot messages, framebuffer problem?
Attached to Project:
Arch Linux
Opened by Leonid Isaev (lisaev) - Wednesday, 27 January 2010, 16:47 GMT
Last edited by Vesa Kaihlavirta (vegai) - Monday, 01 February 2010, 06:26 GMT
Opened by Leonid Isaev (lisaev) - Wednesday, 27 January 2010, 16:47 GMT
Last edited by Vesa Kaihlavirta (vegai) - Monday, 01 February 2010, 06:26 GMT
|
Details
Description:
When the boot process is just started, ("::booting 'Arch Linux'") and it comes to starting services, instead of continuing further, the new messages appear on top of those, which have already been written to the screen. If I use framebuffer instead, then everything is fine. It seems that even if there is no vga= option in menu.lst, the kernel still "thinks" it is using the framebuffer, only the output is the standard console. This happens with kernels 2.6.31 and .32, but not with .30. I have manually compiled several .31 and .32 vanilla kernels, but the problem still exists. So it has to be related to mkinitcpio or some other misconfigured thing (it looks too simple to be a kernel bug)... I am not sure that the graphics card is particularly important at this early stage, but all my machines have nVidia Geforce cards: 6100, 6150Go and GeForce4 MX 440. Additional info: * package version(s) kernel26 2.6.31/32 mkinitcpio 0.5.26 * config and/or log files etc. menu.lst mkinitcpio.conf Steps to reproduce: Just boot without the framebuffer |
This task depends upon
I guess that this is related to "fastboot" (asynchronous initialization) improvements in latest kernels. Now kernel log is "no-lineal", for example (You can see that messages are interlaced mutually):
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdd:
scsi 4:0:0:0: CD-ROM HL-DT-ST DVDRAM GH20NS15 IL00 PQ: 0 ANSI: 5
sdd1 sdd2 <sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:0:0: Attached scsi CD-ROM sr0
sdd5 sdd6 > sdd3 sdd4
sd 3:0:0:0: [sdd] Attached SCSI disk
There is nothing to do here, is a upstream issue, and probably will noy be fixed in favor of speed. (I guess)
http://bugzilla.kernel.org/show_bug.cgi?id=15152.