From: Ash C. <as...@gu...> - 2011-01-22 17:07:32
|
Hi, On Sat, Jan 22, 2011 at 8:21 AM, wilhemina <fmp...@gm...> wrote: > fter disabling the wireless option using menuconfig, I didn't get the > libertas messages anymore however, the boot process stopped at this point: Okay---this is good to know a workaround for this libertas problem. Thanks :). > > Waiting for root device /dev/sdd2... > mmc0: host does not support reading read-only switch. assuming write-enable. > mmc0: new high speed SDHC card at address aaaa > mmcblk0: mmc0:aaaa SU08G 7.40 GiB > mmcblk0: p1 p2 > mmc1: new SDIO card at address 0001 How long did you wait? I've had the boot appear to stall if the EXT3 filesystem got corrupted on a previous boot and the whole thing needs to be rescanned. I don't think I've ever actually had it stop complete here (max. 5 mins stall). Also, are you using an SD card >=2GB? Informally, I've had issues with SDHC cards on the 2.6.32 android kernel. > > and then nothing happens. No more modules no more messages. No android > either. I've followed all the instructions in the guide to the letter and > I'm really puzzled as to why everyone out there seems to have gotten the > overo working using the guide and yet mine is giving so many issues. Most > people who had it working seem to be using the palo43 board. I'm using the > summit-board with overo fire. Are there configurations steps I might have > left out that are not mentioned in your guide? For summit, make sure you are specifying the right display (i.e. HDMI not LCD). This line, # setenv anddisplay 'vram=8M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=lcd43' should be something like # setenv anddisplay 'vram=8M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi' instead. > I might eventually have to apply the patches as well but that is somewhat > unfamiliar territory for me. Is there a walk-through I can follow? I found > the ones relating to IGepv2 that Hedwin posted. Did you tweak them > specifically for overo? How do you apply them? Adding the files directly > didn't work either. Have you tried building directly with the kernel? I > guess since you had to go with the patches that didn't work. I hope I'm not > asking for too much but I'm really hoping to get this working so I really > appreciate the help. There are many tutorials about using diff and patch and for git, I find I can usually get by with git man pages and information from this site:http://progit.org/. I did make some Overo specific changes but these were mostly for the kernel. I've taken patches directly from Hedwin and others commits and applied them to my repository. This includes the kernel directly. Perhaps I'm missing your question here? > > PS: Is it possible to update the guide about all the modules that are not > expected to work as well as workarounds? This might make it less of a hassle > trying to solve any issues that might arise. Please update the guide with your workarounds :). The motivation behind having a wiki is that everyone can help others by improving the collective documentation. -Ash |