On Sunday, June 3, 2012 3:34:00 PM UTC-4, Bharath Ramesh wrote: > > On Sunday, June 3, 2012 8:58:32 AM UTC-4, davilla wrote: >> >> >I am attaching the config for your perusal. I would warn you that I >> >am yet to figure out the reason why I am able to get only 64MB of >> >the RAM when I use vesafb. If I enable nouveau from staging then I >> >get to see the entire 256MB of RAM, this is very much unlike the >> >hardy kernel that I am currently running. Enabling nouveau implies >> >the loss of using nvidia drivers. If you could help in getting over >> >this hurdle it would be really awesome. >> >> Is the nvidia driver stealing system ram ? You can turn that off. >> > > Its not the nvidia driver stealing system ram, that I can turn off from > xorg.conf. > This just minimal command line only installation which doesnt see the > entire > 256MB of ram. Dmesg output > > [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 > bytes) > [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) > [ 0.000000] Initializing CPU#0 > [ 0.000000] Initializing HighMem for node 0 (00000000:00000000) > [ 0.000000] Memory: 61412k/261120k available (2861k kernel code, > 9512k reserved, 1056k data, 372k init, 0k highmem) > I have been trying to debug this issue further. I am not sure if this has anything to do with the framebuffer driver. It seems mostly related to the size of the kernel. I am sure I am missing some option which is causing the kernel only to load the close to 64MB of the available memory once it falls below particular size. Any suggestions on how to further debug this issue is greatly appreciated.
-- Bharath -- To post to this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/atv-bootloader?hl=en
