Uncompressing Linux... done, booting the kernel.

Below is the text from console. I used this image for a file system.

Angstrom-TI-GNOME-image-eglibc-ipk-v2012.01-core-beagleboard-2012.01.11

This image boots and I have network. I then built 3.0.14 I downloaded from https://www.kernel.org/pub/linux/kernel/. I used beagleboard_defconfig. I made no changes. I copied uImage to the second partition under /boot (where the working kernel is). So I now have in the directory uImage-3.0.14+ (Angstrom’s uImage) and my uImage-3.0.14.

I ran the same commands on both uImages. The 3.0.14+ boots, the 3.0.14 does not. Here is the results of ‘file’ command.

uImage-3.0.14: u-boot legacy uImage, Linux-3.0.14, Linux/ARM, OS Kernel Image (Not compressed), 3325268 bytes, Wed Aug 19 12:53:49 2015, Load Address: 0x80008000, Entry Point: 0x80008000, Header CRC: 0x638C9B4E, Data CRC: 0x91C3AA1C
uImage-3.0.14+: u-boot legacy uImage, Angstrom/3.0.14/beagleboard, Linux/ARM, OS Kernel Image (Not compressed), 3372252 bytes, Thu Dec 22 01:53:44 2011, Load Address: 0x80008000, Entry Point: 0x80008000, Header CRC: 0xDBAB6EA9, Data CRC: 0x950C1585

As you can see from the bootargs I do have console set to ttyO2 and the other tty0 was suppose to tell kernel to print. Just in case it was booting and I just could not see output, I checked server for DHCP messages. There were none.

Any help is appreciated.

Thank you.

Durwin

=== console===
OMAP3 beagleboard.org # setenv bootargs “earlyprintk console=ttyO2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait ro”
OMAP3 beagleboard.org # mmcinfo
Device: OMAP SD/MMC
Manufacturer ID: 3
OEM: 5344
Name: SE32G
Tran Speed: 25000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 29.7 GiB
Bus Width: 4-bit
OMAP3 beagleboard.org # ext2load mmc 0:2 80007fc0 /boot/uImage-3.0.14
Loading file “/boot/uImage-3.0.14” from mmc device 0:2 (xxa2)
3325332 bytes read
OMAP3 beagleboard.org # bootm 0x80007fc0

Booting kernel from Legacy Image at 80007fc0 …

Image Name: Linux-3.0.14
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3325268 Bytes = 3.2 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK
XIP Kernel Image … OK
OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.

As you seem to ignore the replies to this exact same question you asked before…

As you seem to ignore the replies to this exact same question you asked
before..

Below is the text from console. I used this image for a file system.

Angstrom-TI-GNOME-image-eglibc-ipk-v2012.01-core-beagleboard-2012.01.11

This image boots and I have network. I then built 3.0.14 I downloaded

from https://www.kernel.org/pub/linux/kernel/. I used
beagleboard_defconfig. I made no changes. I copied uImage to the second
partition under /boot (where the working kernel is). So I now have in the
directory uImage-3.0.14+ (Angstrom's uImage) and my uImage-3.0.14.

3.0.14+ is NOT the same as 3.0.14, you need to add 'ALL' patches that made
it a '+'

I tried to get the source for 3.0.14+. The image that was create does not
have any source that I can find (or patches). Which is why I went to kernel.org
Does anyone know where I can find source/patches for 3.0.14+?

Thank you.

This post references a link which I did check out. But it does not have TIDSPBRIDGE. That is why I am trying to use 3.0.14+ image with 3.0.14 source (which does have TIDSPBRIDGE). Now if the source or patches for 3.0.14+ exist, I have not been able to find it.

https://github.com/Angstrom-distribution/meta-ti/blob/master/recipes-kernel/linux/linux_3.0.bb

&

https://github.com/Angstrom-distribution/meta-ti/tree/master/recipes-kernel/linux/linux-3.0

Regards,

TIDSPBRIDGE is dead...

for "3.0.14+ patchset" look at the patches at:

https://github.com/Angstrom-distribution/meta-ti/blob/master/recipes-kernel/linux/linux_3.0.bb

&

https://github.com/Angstrom-distribution/meta-ti/tree/master/recipes-kernel/linux/linux-3.0

Regards,

Thank you.

I used this command to get the repository.

git clone https://github.com/Angstrom-distribution/meta-ti.git

I see

meta-ti/tree/master/recipes-kernel/linux/linux-3.0
meta-ti/tree/master/recipes-kernel/linux/linux-3.0.bb

I do not see

meta-ti/blob/master/recipes-kernel/linux/linux_3.0.bb

1) Is linux-3.0.bb a script used with 'patch'?
2) Do I cd to top level of kernel tree and run patch with this script?
3) How is this script executed?

Thank you,

Durwin

Thank you.

I used this command to get the repository.

git clone https://github.com/Angstrom-distribution/meta-ti.git

I see

meta-ti/tree/master/recipes-kernel/linux/linux-3.0
meta-ti/tree/master/recipes-kernel/linux/linux-3.0.bb

I do not see

meta-ti/blob/master/recipes-kernel/linux/linux_3.0.bb

Well, yeah "blob" is just part of the github "web" interface...

1) Is linux-3.0.bb a script used with 'patch'?
2) Do I cd to top level of kernel tree and run patch with this script?
3) How is this script executed?

It's a *.bb script... so either use "bitbake", or write a script to
manually "patch -p1 < <file>" in the order shown in the *.bb file.

I'd personally write a script.. Using "bitbake" requires more other
un-related work..

Regards,

Ok, patches went in successfully, and uImage was built successfully.
I am still stuck at booting the kernel. I need an idea to debug this.
Any ideas?

Thank you,

Durwin

Well, assuming you followed the *.bb exactly for the patches and
kernel defconfig...

It's probably a gcc bug.. Make sure you use a version of gcc from
that same era. As that "repo" worked in that era.

Good Luck!

Regards,