On 07/03/12 03:47, the mail apparently from David Cullen included:
Hello, Tom,
On 7/2/2012 2:29 PM, Tom Gall wrote:
That "should" work fine. What's important for cross assembling your own images is that qemu is reasonably up to date. Lucid is getting fairly old now. Speaking for myself I haven't built anything on lucid for some time.
You have a good point about qemu. One of the reasons I created the Ubuntu 12.04 Server VM was to get a newer version of qemu-user-static.
Ok. One thing to note. When using live build it doesn't actually build the packages, it just assembles images. It uses .debs which are found in all the various archives (including your own) to accomplish this.
Well, that's not what I need. I need to rebuild the kernel.
I'm just going to chroot into a copy of the root file system that I got from the image I downloaded from here:
http://www.omappedia.com/wiki/Ubuntu_Pre-Built_BinariesThat way, I can just install the linux-source package, build-essential, and whatever else I need in a self-contained environment.
I originally started looking at the Linaro stuff because the armhf+omap4 Ubuntu image runs very slowly, even after installing the PowerSVG binary driver.
However, when I loaded the 12.05 and 12.06 Linaro Ubuntu images, all I got was a black screen with a mouse pointer.
After running some experiments here, I discovered that the Linaro Ubuntu images only work with displays that have a native resolution of 1920x1080.
I tried to use kernel command line arguments to force the resolution to work with my 1680x1050 monitor, but my changes had no effect. I wanted to look at the kernel source for the Linaro Ubuntu image because I can probably figure out the correct kernel command line arguments from that. However, I could not figure out which git tree to use.
The whole thing reminds me of the line from Zork: "You are in a maze of twisty little passages, all alike."
Just to be clear, the kernel is recognizing your monitor and coming up with kms OK at your native resolution?
IIUI Xorg starts and you get a pointer you can move around but Xorg chokes somewhere.
Did you have a look at the Xorg logs then, or try to come up in runlevel three and do startx at the terminal?
If I did get the idea I am not sure recooking the kernel will change much, it's actually doing its side (as distinct from SGX module perhaps) okay from the sound of it.
-Andy