Geode lxfb framebuffer not working
Kushal Koolwal
kushalkoolwal at hotmail.com
Thu Jun 12 17:46:36 EDT 2008
> Step 1 is to try a kernel from GIT HEAD.
I followed the instructions at http://linux.yyz.us/git-howto.html and downloaded the GIT repository.
The kernel version that I got was 2.6.26-rc5
The problem with this was that lxfb did not find /dev/fb0 device and hence I was not sure if you still want the outputs that you had asked for.
Here is what the dmesg said:
[ 0.000000] Kernel command line: root=/dev/hda1 ro video=lxfb:1024x768-32 at 60
[ 0.173548] lxfb 0000:00:01.1: 16 KB of video memory at 0xe0000000
[ 0.173679] lxfb 0000:00:01.1: could not find valid video mode
[ 0.173780] lxfb: probe of 0000:00:01.1 failed with error -22
and fbset:
debian:~# fbset
open /dev/fb0: No such file or directory
debian:~#
If would still like the full outputs of dmesg, fbset, msr-tool, sys/device/*, etc for this kernel I will attach it. If I did not used the kernel that you were expected then please let me know which kernel I should try.
Thanks.
Kushal Koolwal
I do blog at http://blogs.koolwal.net/
______________________
EMAILING FOR THE GREATER GOOD
> Date: Thu, 12 Jun 2008 12:52:58 -0600
> From: jordan.crouse at amd.com
> To: kushalkoolwal at hotmail.com
> CC: mart.raudsepp at artecdesign.ee; linux-geode at bombadil.infradead.org
> Subject: Re: Geode lxfb framebuffer not working
>
> On 12/06/08 10:34 -0700, Kushal Koolwal wrote:
> > Glad to know that someone else has the same issue. Always good to have inputs from more people to help us all resolve the issue.
> >
> > > I want to help, but I need your help to get me started.
> > Jordan, I am there to help to resolve this issue. Just let me know all the information that you need (outputs, register info, config files, etc). I am not an expert in debugging kernel level stuff therefore I need to know what I should be sending you guys.
>
> Step 1 is to try a kernel from GIT HEAD.
>
> Step 2 is to send us the complete dmesg output. What BIOS are you using?
>
> Step 3 is to send us the fbset information from a broken system
>
> step 4 is to tell us what your monitor thinks it is driving (there is usually
> a information button that says what the current xres yres and refresh is).
>
> Step 5 is to compile up the the MSR tools from hpa
> http://www.kernel.org/pub/linux/utils/cpu/msr-tools/
> And connect via serial or net to the system when it is broken and
> send the value of MSR 0x4C000015.
>
> Step 6 is to send the complete output of
> /sys/devices/pci0000:00/0000:00:01.1/resource
>
> Jordan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://bombadil.infradead.org/pipermail/linux-geode/attachments/20080612/32a91764/attachment.html
More information about the Linux-geode
mailing list