<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
> Can you run fbset without trying to change the mode? I'm interested in<br>> finding out what your system thinks you are currently running.<br>Here is the output without passing any parameters to my 2.6.25-4-custom kernel in which lxfb is compiled into the kernel:<br><br>debian:~# fbset<br>mode "640x480-63"<br> # D: 25.200 MHz, H: 32.143 kHz, V: 63.150 Hz<br> geometry 640 480 640 480 16<br> timings 39682 48 8 25 2 88 2<br> hsync high<br> vsync high<br> rgba 5/11,6/5,5/0,0/0<br>endmode<br>debian:~# <br><br>> I'm sorry - the kernel only has one mode (screen, whatever). If you are<br>> telling us that you have a problem with a splashscreen app (usplash), then<br>> yes, that is a known problem. Please boot to your "UGLY" mode, and run<br>> fbset and give us the results. Also, make sure<br>> that vesafb or any other frambuffer modules are not being loaded, there<br>> seems to be some confusion here betweeen vesa, lxfb and X which are all<br>> completely different entities.<br>I will try to make it clear this time. Once again I am sorry for the confusion. It's my mistake.<br><br>A) Using 2.6.25-4-custom kernel in which I compiled the lxfb driver *into the kernel* I get the blank screen every time I try to boot with or without passing the video= parameter. It seems that lxfb module tries to takeover the /dev/fb0 device and hence the result.<br><br>B) Using 2.6.25-4-486 default Debian kernel in which the lxfb is compiled as a *module* I can get the UGLY screen if I pass no parameter. If I pass vga=791 (1024x768 16-bit) the vesafb driver (which is compiled into the kernel) kicks in I get the framebuffer console at 1024x768.<br><br>If you are telling us that you have a problem with a splashscreen app (usplash), then <br>>yes, that is a known problem.<br>No, I am not using any kind of bootsplash program. <br><br>> One last thing - are you using a VGA device or a TFT panel? <br>I am using a VGA device - ViewSonic VE510b Monitor.<br><br>>Also, make sure that vesafb or any other frambuffer modules are not being loaded<br>Should I try not compiling the vesafb driver at all? Because right now in my 2.6.25-4-custom kernel I have the lxfb and vesafb both compiled into the kernel.<br>CONFIG_FB_VESA=y<br>CONFIG_FB_GEODE_LX=y<br># CONFIG_FB_GEODE_GX is not set<br># CONFIG_FB_GEODE_GX1 is not set<br><br><br>As I mentioned in my first post reverting back to my old 2.6.22 kernel with the development patch version of lxfb I can get the framebuffer console on the exact same hardware.<br><br>Thank you once again for your prompt response. Much appreciated!<br><br>Kushal Koolwal<br><br>I do blog at http://blogs.koolwal.net/<br><br><br><br>______________________<br><table style="height: 24px; font-family: 'Segoe UI',Tahoma,san-serif; font-size: 9pt; color: rgb(0, 153, 204);"><tbody><tr><td><a href="http://im.live.com/Messenger/IM/Home/?source=EML_WLHM_GreaterGood" target="_blank" style="color: rgb(51, 153, 102); text-decoration: none; font-weight: bold;"><img style="border-style: none;" src="http://gfx1.hotmail.com/mail/w2/ltr/i_charity.gif" alt="i'm"></a> EMAILING FOR THE GREATER GOOD</td></tr></tbody></table><br><br>> Date: Wed, 11 Jun 2008 14:14:04 -0600<br>> From: jordan.crouse@amd.com<br>> To: kushalkoolwal@hotmail.com<br>> CC: linux-geode@bombadil.infradead.org<br>> Subject: Re: Geode lxfb framebuffer not working<br>> <br>> On 11/06/08 13:04 -0700, Kushal Koolwal wrote:<br>> > <br>> > >Can you switch the mode manually from the command line with fbset?<br>> > <br>> > Using fbset did not help:<br>> > <br>> > debian:~# fbset -v 1024x768-60<br>> > Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)<br>> > (C) Copyright 1995-1999 by Geert Uytterhoeven<br>> > Opening frame buffer device `/dev/fb0'<br>> > Reading mode database from file `/etc/fb.modes'<br>> > Using video mode `1024x768-60'<br>> > Setting video mode to `/dev/fb0'<br>> > debian:~# <br>> <br>> Can you run fbset without trying to change the mode? I'm interested in<br>> finding out what your system thinks you are currently running.<br>> <br>> > After giving the above command when I git Ctrl-Alt-F1 I see some garbage (random graphic color) and it seems as if the console freaked out. Pressing Ctrl-Alt-F7 (returning to GDM) gets back everything to normal. I tried 800x600 also but same results.<br>> > <br>> > > So you are saying that the lxfb boots fine at 800x600@60? Have you tried<br>> > > any other modes? <br>> > What I meant was I can only see the UGLY (normal) screen during the boot process if I don't pass any parameters. <br>> <br>> I'm sorry - the kernel only has one mode (screen, whatever). If you are<br>> telling us that you have a problem with a splashscreen app (usplash), then<br>> yes, that is a known problem. Please boot to your "UGLY" mode, and run<br>> fbset and give us the results. Also, make sure<br>> that vesafb or any other frambuffer modules are not being loaded, there<br>> seems to be some confusion here betweeen vesa, lxfb and X which are all<br>> completely different entities.<br>> <br>> One last thing - are you using a VGA device or a TFT panel? <br>> <br>> Jordan<br>> <br>> -- <br>> Jordan Crouse<br>> Systems Software Development Engineer <br>> Advanced Micro Devices, Inc.<br>> <br></body>
</html>