linux-kernel - Re: lxfb is not changing modes, no errors/information printing out

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20080127203826.GA9612@cosmic.amd.com>
Date:	Sun, 27 Jan 2008 13:38:26 -0700
From:	"Jordan Crouse" <jordan.crouse@....com>
To:	"Andrew Paprocki" <andrew@...iboo.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: lxfb is not changing modes, no errors/information printing
 out

On 27/01/08 14:55 -0500, Andrew Paprocki wrote:
> On Jan 27, 2008 2:28 PM, Jordan Crouse <jordan.crouse@....com> wrote:
> > On 27/01/08 13:45 -0500, Andrew Paprocki wrote:
> > > Using 2.6.24, I can't get my Geode LX (LX800 CPU) to boot in anything
> > > other than the default 80x25 console even though lxfb appears to be
> > > loading normally. This device doesn't work with the VESA fb either
> > > when I request "vga=0x31a". All the other boards I have display a
> > > 1280x1024 console on my monitor. Are my kernel parameters wrong in
> > > some way? I tried "video=lxfb:<mode>" with and without "vga=0x31a".
> > > The driver is compiled into the kernel -- I am not using modules.
> >
> > Can you change the mode after you have booted with 'fbset'?
> 
> Two answers to this I just found out..
> 
> This is a system I installed BusyBox 1.8.0 on, and running 'fbset
> 1280x1024-75' does nothing. I copied over the real fbset binary from
> my Debian install and when I ran it the same way, it worked perfectly.
> So, yes, it appears that it is possible to change it after the fact,
> but for some reason BusyBox can't do it. The only problem then appears
> to be setting the fb mode from the boot line.

The busybox binary does have differences - I think that the -n parameter
is required to set the mode 'right now'.  But I'm glad that the
mode change works (thats the tough part).  Probably something changed
in the way we handle the setup and/or the mode database, thats easy enough
to instrument and fix.  I'll check this out tomorrow, and do a patch for
the blanking bug too.

Jordan

-- 
Jordan Crouse
Systems Software Development Engineer 
Advanced Micro Devices, Inc.


--
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/