linux-kernel - Re: Framebuffer issues in 2.6.26 with uvesafb and vesafb. Linux is about choice!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Oct 2008 08:26:55 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alistair John Strachan <alistair@...zero.co.uk>
CC:	Robert Moss <robert.von.moss@...il.com>,
	Samuel Thibault <samuel.thibault@...-lyon.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Framebuffer issues in 2.6.26 with uvesafb and vesafb. Linux is
 about choice!

Alistair John Strachan wrote:
> On Thursday 23 October 2008 12:21:09 Robert Moss wrote:
>> I also want to note, that I downloaded 2.6.27.3 and compiled, with
>> CONFIG_FB_VESA=Y, and still get excactly the same response as from
>> 2.6.26
> 
> Useful info, and I checked your configs and they enable the right options. 
> Looks like you've found a real bug.
> 
> IIRC, a lot of real mode assembler (including the x86 vga/vesa stuff, iirc) 
> was rewritten a year or so ago, in C. This might have been the time that this 
> bug was introduced. I've added hpa to CC since I believe he was the author of 
> these changes.
> 
> (Summary of the original report is that vga= vesa mode selection seems to have 
> broken for Robert since at least 2.6.26, and after 2.6.24. From what I can see 
> he has the right vesafb options enabled.)
> 

That happend in 2.6.23 I believe, so that would be unrelated.

The best would be to bisect the regression.  The second best would be if 
he could run the "vesainfo" program from the Syslinux distribution (it's 
a pre-boot program that dumps information on the VESA stack).  The third 
best would be to set up Xorg to run the "vesa" driver, and send 
/var/log/Xorg.0.log.

	-hpa

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/