Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758894AbcCDKXo (ORCPT ); Fri, 4 Mar 2016 05:23:44 -0500 Received: from mail9.pr.hu ([87.242.0.9]:42032 "EHLO mail9.pr.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756532AbcCDKXk (ORCPT ); Fri, 4 Mar 2016 05:23:40 -0500 X-Greylist: delayed 821 seconds by postgrey-1.27 at vger.kernel.org; Fri, 04 Mar 2016 05:23:40 EST To: lkml From: Boszormenyi Zoltan Subject: Graphics console with VESAFB doesn't kick in in kernel 4.4.x Message-ID: <56D95EEE.2060503@pr.hu> Date: Fri, 4 Mar 2016 11:09:50 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Score: 1.7 (+) X-Spam-Report: Spam detection software, running on the system "prspamd4.pr.hu", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi, I have tried kernel 4.4.0, 4.4.3 and 4.4.4 on an old Geode LX based POS computer where the usual way to use graphics is VESAFB and optionally Xorg with the VESA driver. With vga=0x314 with or without video=vesafb:mtrr:3 the graphics mode is set but VESAFB doesn't start. There is no /dev/fb0 device after boot, although everything else works. [...] Content analysis details: (1.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.2 ALL_TRUSTED Passed through trusted hosts only via SMTP 3.0 BAYES_95 BODY: Bayes spam probability is 95 to 99% [score: 0.9604] -1.1 AWL AWL: Adjusted score from AWL reputation of From: address X-Scan-Signature: 7a6493e989a703e6709937009417634f X-Spam-Tracer: backend.mail.pr.hu 1.7 20160304100954Z Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1384 Lines: 38 Hi, I have tried kernel 4.4.0, 4.4.3 and 4.4.4 on an old Geode LX based POS computer where the usual way to use graphics is VESAFB and optionally Xorg with the VESA driver. With vga=0x314 with or without video=vesafb:mtrr:3 the graphics mode is set but VESAFB doesn't start. There is no /dev/fb0 device after boot, although everything else works. # dmesg | egrep -i '(vesa|onsol)' [ 0.000000] Kernel command line: BOOT_IMAGE=/bzImage root=UUID=b2cccbac-2717-4fcb-ae65-15189e087778 ro LANG=en.US.UTF-8 vga=0x314 video=vesafb:mtrr:3 [ 0.000000] Console: colour dummy device 80x25 [ 0.000000] console [tty0] enabled [ 1.847411] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch. [ 1.847838] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 2.416981] systemd[1]: Starting Setup Virtual Console... [ 2.698214] systemd[1]: Started Setup Virtual Console. The relevant configuration pieces are set, VESAFB is built into the kernel: CONFIG_FB_BOOT_VESA_SUPPORT=y CONFIG_FB_VESA=y CONFIG_HW_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_VT_CONSOLE_SLEEP=y CONFIG_VT_HW_CONSOLE_BINDING=y Help, please and cc: me in the answer, I am not subscribed to the list. Thanks in advance, Zolt?n B?sz?rm?nyi