Angstrom on Pandaboard ES with latest TI OMAP Linux Kernel OR ?

[mammar]

Hi,

I am a newbie to embedded/kernel side but i have a good experience with C, Python and  Linux  application development.

Now a days i have free time and i want to contribute/work on linux embedded/kernel side.

I am already experimenting with Pandaboard ES and compiled the Ubuntu 11.10 kernel on it for the purpose of debugging a kernel module.

I have also installed the Angstrom on Pandaboard ES by getting and compiling the latest u-boot from Linaro and Angstrom linux from Angstrom site.

As i saw during installation of Angstrom on Pandaboard ES, Angstrom is currently not available for OMAP4460 and the current kernel version used by Angstrom is 2.6.35.

So, I want to build/compile Angstrom with latest TI OMAP Linux Kernel for Pandaboard ES with POWERVR SGX540 drivers.

So, kindly tell me is it worth it to do the above? If yes, then can anyone here guide me in the right direction to achieve the above? And, If not can you guys suggest me the area in Linux embedded/kernel side where i should spend me time and energies?

As i mentioned earlier, now a days i have a good amount of time so i really want to do something related to Linux embedded/kernel on Pandaboard.

Kindly tell me what should i read(Book, tutorial etc..) as a prerequisite.

Please Help me and share you suggestions.

Any help will be greatly appreciated.

 

Thanks

[JB]

I would also be interested in any Angstrom recommendations.  I've had no luck with Angstrom on Pandaboard or Pandaboard ES.  I've tried the Angstrom builder at http://www.angstrom-distribution.org/builder/, but the kernel (uImage-2.6.35.3+) that comes in the .tar.gz simply doesn't work.  It consistently gives

INIT: "1" respawning too fast: disabled for 5 minutes
INIT: "S" respawning too fast: disabled for 5 minutes

over and over...

[Philip Balister]

On 09/13/2012 11:12 AM, JB wrote:
> I would also be interested in any Angstrom recommendations. I've had no
> luck with Angstrom on Pandaboard or Pandaboard ES. I've tried the Angstrom
> builder at http://www.angstrom-distribution.org/builder/, but the kernel
> (uImage-2.6.35.3+) that comes in the .tar.gz simply doesn't work. It
> consistently gives
>
> INIT: "1" respawning too fast: disabled for 5 minutes
> INIT: "S" respawning too fast: disabled for 5 minutes

That sounds like you are passing the kernel a bad console= line.

Philip

>
> over and over...
>
>
>
>
> On Thursday, May 31, 2012 4:07:00 AM UTC-7, ma1 wrote:

>>u-bbot udelay

[Tom Mitchell]

On Thu, Sep 13, 2012 at 11:12 AM, JB <jared.b...@gmail.com> wrote:

I would also be interested in any Angstrom recommendations.  I've had no luck with Angstrom on Pandaboard or Pandaboard ES.  I've tried the Angstrom builder at http://www.angstrom-distribution.org/builder/, but the kernel (uImage-2.6.35.3+) that comes in the .tar.gz simply doesn't work.  It consistently gives

INIT: "1" respawning too fast: disabled for 5 minutes
INIT: "S" respawning too fast: disabled for 5 minutes

over and over...

That may be good news because this is init telling you that

something in user space is borked.  The kernel may be fine

and init itself may be fine.

Verify the ABI of your objects, verify the shared library  that starts

them.    

Edit many startup scripts that init runs so they contain

something like:

   echo "Hello this is _________.sh"; sleep 1

so you can discover which is ill.  With luck it

is not shell or something too fundamental.

Note that init and friends often redirect stdout, stderr

to /dev/null  so a log file or a tty as the target may

help.

 

--
  T o m   M i t c h e l l

[Tom Mitchell]

Do not neglect an inspection of the log files.   Just

mount the boot media on another machine and inspect.

I have a USB SD card reader from a camera shop  and

have looked at pandaboard SD cards on a running pandaboard.

Sometimes all I need to do is run fsck on the card....

 

--
  T o m   M i t c h e l l

[Pavol Cupka]

check out your /etc/inittab to contain something like this

# TERMINALS
c1:12345:respawn:/sbin/agetty 38400 tty1 linux
c2:2345:respawn:/sbin/agetty 38400 tty2 linux
c3:2345:respawn:/sbin/agetty 38400 tty3 linux
c4:2345:respawn:/sbin/agetty 38400 tty4 linux
c5:2345:respawn:/sbin/agetty 38400 tty5 linux
c6:2345:respawn:/sbin/agetty 38400 tty6 linux

# SERIAL CONSOLES
s0:12345:respawn:/sbin/agetty 115200 ttyO2 vt100

and check your bootargs in boot.scr to contain something like this
console=ttyO2,115200n8

also make sure you have agetty or something similar and adjust as needed

pavol

[Sukumar Ghorai]

I am getting the similar problem..
1. the file system working fine on 5days back.. today the same FS from
MMC/SD card giving the following error.
2. Where as if I unzip the same old
random-63481ab3-image-pandaboard.tar.gz and working fine.
---
INIT: version 2.86 booting
mount: mount point /proc does not exist
Please wait: booting...
mount: mount point /proc does not exist
grep: /proc/mounts: No such file or directory
grep: /proc/mounts: No such file or directory
Remounting root file system...
[ 6.027984] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
Caching udev devnodes
Populating dev cachemv: cannot rename '/tmp/uname': No such file or directory
error: "net.ipv4.conf.default.rp_filter" is an unknown key
error: "net.ipv4.conf.all.rp_filter" is an unknown key
logger: warning: can't open /etc/mtab: No such file or directory
logger: mount: mount point /proc does not exist
logger: mount: mount point /dev/pts does not exist
logger: mount: mount point /proc/bus/usb does not exist
logger: mount: mount point /dev/shm does not exist
[ 6.513458] omap_device: omap_hsmmc.0: new worst case deactivate
latency 0: 61035
grep: /proc/filesystems: No such file or directory
ALSA: Restoring mixer settings...
sed: /proc/mounts: No such file or directory
sed: /proc/mounts: No such file or directory
sed: /proc/mounts: No such file or directory
Configuring network interfaces... /usr/sbin/alsactl: load_state:1625:
No soundcards found...
ifconfig: SIOCGIFFLAGS: No such device
done.
Starting portmap daemon: portmapstart-stop-daemon: can't open '/proc':
No such file or directory
.
grep: /proc/mounts: No such file or directory
error: "net.ipv4.conf.default.rp_filter" is an unknown key
error: "net.ipv4.conf.all.rp_filter" is an unknown key
hwclock: can't open '/dev/misc/rtc': No such file or directory
Tue Sep 18 09:19:00 UTC 2012
hwclock: can't open '/dev/misc/rtc': No such file or directory
INIT: Entering runlevel: 5
Starting system message bus: dbus.
/etc/rc5.d/S10dropbear: line 31: can't open /proc/mounts: no such file
Starting Dropbear SSH server: dropbear.
Starting advanced power management daemon: start-stop-daemon: can't
open '/proc': No such file or directory
(failed.)
Starting syslogd/klogd: start-stop-daemon: can't open '/proc': No such
file or directory
* Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon


Timeout reached while wating for return value
Could not receive return value from daemon process.
...fail!



INIT: Id "S" respawning too fast: disabled for 5 minutes

[dmitry pervushin]

Hello,

> I am getting the similar problem..
> 1. the file system working fine on 5days back.. today the same FS from
> MMC/SD card giving the following error.
> 2. Where as if I unzip the same old
> random-63481ab3-image-pandaboard.tar.gz and working fine.
> ---
> INIT: version 2.86 booting
> mount: mount point /proc does not exist

It makes sense to create the /proc on your SD card

[log skipped]

--
Sincerely yours,
dmitry pervushin

[Sukumar Ghorai]

On Thu, Sep 27, 2012 at 8:49 PM, dmitry pervushin <d-per...@ti.com> wrote:
> Hello,
>
>
>> I am getting the similar problem..
>> 1. the file system working fine on 5days back.. today the same FS from
>> MMC/SD card giving the following error.
>> 2. Where as if I unzip the same old
>> random-63481ab3-image-pandaboard.tar.gz and working fine.
>> ---
>> INIT: version 2.86 booting
>> mount: mount point /proc does not exist
>
> It makes sense to create the /proc on your SD card

1. Any guess how the /proc folder removed?
2. Also creating the /proc folder did not help.. stop at the same place
[19:34:43.1] [ 2.794921] omap_device: omap_hsmmc.4: new worst case
deactivate latency 0: 30517
[19:34:44.5] [ 4.167755] EXT4-fs (mmcblk0p3): warning: maximal
mount count reached, running e2fsck is recommended
--> Any Guess what going on here.. this is not in working case.
[19:34:44.7] [ 4.384246] EXT4-fs (mmcblk0p3): recovery complete
[19:34:44.9] [ 4.595916] EXT4-fs (mmcblk0p3): mounted filesystem
with ordered data mode. Opts: (null)
[19:34:44.9] [ 4.604766] VFS: Mounted root (ext4 filesystem) on device 179:3.
[19:34:44.9] [ 4.611419] Freeing init memory: 296K

[19:34:45.1] INIT: version 2.86 booting

[19:34:45.2] mount: mount point /proc does not exist

[dmitry pervushin]

On 09/28/2012 08:33 AM, Sukumar Ghorai wrote:
> On Thu, Sep 27, 2012 at 8:49 PM, dmitry pervushin <d-per...@ti.com> wrote:
>> Hello,
>>
>>
>>> I am getting the similar problem..
>>> 1. the file system working fine on 5days back.. today the same FS from
>>> MMC/SD card giving the following error.
>>> 2. Where as if I unzip the same old
>>> random-63481ab3-image-pandaboard.tar.gz and working fine.
>>> ---
>>> INIT: version 2.86 booting
>>> mount: mount point /proc does not exist
>>
>> It makes sense to create the /proc on your SD card
> 1. Any guess how the /proc folder removed?
> 2. Also creating the /proc folder did not help.. stop at the same place
> [19:34:43.1] [ 2.794921] omap_device: omap_hsmmc.4: new worst case
> deactivate latency 0: 30517
> [19:34:44.5] [ 4.167755] EXT4-fs (mmcblk0p3): warning: maximal
> mount count reached, running e2fsck is recommended
> --> Any Guess what going on here.. this is not in working case.

mount decided that the filesystem on the 3rd partition of your SD card
needs to be checked using fsck. By the way, is it expected, to have the
mmcblk0p3 as the root filesystem?

> [19:34:44.7] [ 4.384246] EXT4-fs (mmcblk0p3): recovery complete
> [19:34:44.9] [ 4.595916] EXT4-fs (mmcblk0p3): mounted filesystem
> with ordered data mode. Opts: (null)
> [19:34:44.9] [ 4.604766] VFS: Mounted root (ext4 filesystem) on device 179:3.

and it has been mounted now. Have you created the /proc directcory on
the _3rd partition_ of SD, which becomes root?