2012-02-02 23:40, Ulf Samuelsson skrev:
1. Took me 20 minutes to boot the stuff.
Most of the time waiting at "Recreate volatile


Comments:

Some uglyness in the printout, see below:
1. in the Welcome message:
2. udev printout.
(The [OK]'s are aligned on the terminal)

Unfortunately, the board seems to lock up when recreating
"Volatile Files and Directories"
Been at this point for 15 minutes.
Had this problem with latest oe-classic, when the kernel was too old.
2.6.30 took a long time to run udev, and 2.6.39 was much faster.
It was related to where temporary files was stored. In flash or in RAM.


OK, Boot completed after 20 minutes.
Second time I reboot, the boot completes without a long delay.

I added some stuff to /etc/xinetd.conf

+++++++++++++++

# Simple configuration file for xinetd
#
# Some defaults, and include /etc/xinetd.d/
defaults
{
        instances               = 60
        log_type                = SYSLOG authpriv
        log_on_success          = HOST PID
        log_on_failure          = HOST
        cps                     = 25 30
}
includedir /etc/xinetd.d

----------------------------------

Still no screen output...

The boot is disturbed by stuff printing out in the middle of other stuff...
Maybe with systemd parallel activities, some synchronization is needed
on the console.
No prompt, until everything else has been completed,
or maybe the output should go to a log file.

Starting Getty on tty1...
                                                                               
Started Getty on tty1                                                  [  OK  ]

.---O---.
|       |                  .-.           o o
|   |   |-----.-----.-----.| |   .----..-----.-----.
|       |     | __  |  ---'| '--.|  .-'|     |     |
|   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
'---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
                -'  |
                '---'

The Angstrom Distribution at91sam9g35ek ttyS0

Angstrom v2012.01-core - Kernel 2.6.39.4+

at91sam9g35ek login: xinetd[81]: Starting internet superserver: xinetd.
Started xinetd.service [ OK ]
                                                                                
                                                                      Starting 
ofono.service...



Running a 2.6.39 modified for an at91 at the moment.
Will try to analyze the other kernel recipes to see why I have a problem.

Another possible problem:
The Ethernet controller tends to die in U-Boot after some time,
losing connection to the server, but then I cannot ping the nfs server
from the board, and the nfs server cannot ping the board.
At this stage, the board can still be pinged by the server
so I doubt this is the case.

------------------------------------------------------------------------------------

Welcome to The �Ångstr�öm Distribution!

Starting udev Coldplug all Devices...
Starting Lock Directory...
Starting Remount API VFS...
Starting Media Directory...
Starting Runtime Directory...
Started Huge Pages File System [ OK ]
Starting File System Check on Root Device...
Starting udev Kernel Device Manager...
Starting Journal Service...
Started Journal Service [ OK ]
Started Set Up Additional Binary Formats udevd[45]: starting version 175
[ OK ]
Starting POSIX Message Queue File System...
Starting Debug File System...
Started Load Kernel Modules [ OK ]
Started Configuration File System [ OK ]
Started FUSE Control File System [ OK ]
Started Apply Kernel Variables [ OK ]
Started Security File System [ OK ]
Started udev Kernel Device Manager [ OK ]
Started Lock Directory [ OK ]
Started Remount API VFS [ OK ]
Started Media Directory [ OK ]
Started Runtime Directory [ OK ]
Started File System Check on Root Device [ OK ]
Started POSIX Message Queue File System [ OK ]
Started Debug File System [ OK ]
Starting Remount Root FS...
Started Remount Root FS [ OK ]
Starting Opkg first boot configure...
Starting /tmp...
Started Machine ID first boot configure [ OK ]
Started /tmp [ OK ]
Starting Recreate Volatile Files and Directories...
Starting Load Random Seed...
Started Load Random Seed [ OK ]
Started udev Coldplug all Devices [ OK ]
Started Recreate Volatile Files and Directories [ OK ]

<20 MINUTES WAIT>

Starting Connection service...

Started Login Service
at91sam9g35ek login:
Angstrom v2012.01-core - Kernel 2.6

<SEEMS TO FREEZE>
No screen output...

did rlogin over the net to root, which worked.
Could create a user...

checked running processes with ps.
killed "/sbin/getty 115200 ttyS0" and rerun


Here is the result of "ps" after that.

PID USER VSZ STAT COMMAND
1 root 4276 S {systemd} /sbin/init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [kworker/0:0]
5 root 0 SW [kworker/u:0]
6 root 0 SW [rcu_kthread]
7 root 0 SW< [khelper]
8 root 0 SW [sync_supers]
9 root 0 SW [bdi-default]
10 root 0 SW< [kblockd]
11 root 0 SW [khubd]
12 root 0 SW< [cfg80211]
13 root 0 SW [kworker/0:1]
14 root 0 SW< [rpciod]
15 root 0 SW [kswapd0]
16 root 0 SW [fsnotify_mark]
17 root 0 SW< [nfsiod]
18 root 0 SW< [crypto]
27 root 0 SW [mtdblock0]
28 root 0 SW [mtdblock1]
29 root 0 SW [kworker/u:1]
32 root 0 SW [irq/39-qt1070]
33 root 0 SW [mmcqd/0]
35 root 0 SW [flush-0:14]
45 root 2380 S /lib/udev/udevd
46 root 3764 S /lib/systemd/systemd-journald
1439 root 3972 S /usr/sbin/connmand -n
1442 root 2740 S /lib/systemd/systemd-logind
1448 root 1812 S /sbin/agetty tty1 38400
1456 messageb 2596 S /usr/bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation
1458 root 4224 S /usr/sbin/ofonod
1462 root 2376 S /lib/udev/udevd
1463 root 2376 S /lib/udev/udevd
1469 root 4644 S /usr/sbin/wpa_supplicant -u
1483 root 2552 S /usr/sbin/dropbear -i -r /etc/dropbear/dropbear_rsa_host_key -p 22
1484 ulf 2760 S -sh
1493 root 2552 S su
1494 root 2736 S sh
1498 root 1812 S /sbin/getty 115200 ttyS0
1500 root 2296 R ps

Kernel Command line =
Kernel command line: mem=128M console=ttyS0,115200 root=/dev/nfs rw nfsroot=10.175.196.237:/tftpboot/systemd-GNOME-image/at91sam9g35ek/ ip=10.175.196.225:10.175.196.237:10.175.196.1:255.255.255.0::eth0:off

Should not X Windows start ?

When I run /etc/init.d/xinetd start
root@at91sam9g35ek:/etc/init.d# ./xinetd start
Starting internet superserver: xinetd.

but ps reports nothing.
xinetd.conf is empty... xinetd.d as well.
No /etc/defaults/xinetd

start-stop-daemon --start --exec /usr/sbin/xinetd -- -pidfile /var/run/xinetd.pid
left no effect on "ps".

The "/etc/xinit.d/xinetd" script adds $XINETD_OPTS, but I didn't find a definition in the rootfs, so I guess it is empty.




_______________________________________________
Angstrom-distro-users mailing list
Angstrom-distro-users@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users


_______________________________________________
Angstrom-distro-users mailing list
Angstrom-distro-users@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users

Reply via email to