Inconsistent BB Startup Behavior from Session to Session

I have gotten Angstrom running on my new BB.

About half the time, the GUI appears on the DVI monitor. About Half
the time, the monitor stays black.

Sometimes, the USB-hubbed keyboard and mouse work. Other times, they
do not -- though the Angstrom boot window, visible over the UART, does
indicate (correctly) the plugging/unplugging of those devices and
their correct types.

Is my BB bogus? I'm not deliberately changing ANYTHING software-wise
from session to session...

thx
kb

Kb, what kernel version are you running? I've seen this before, it
seemed 50/50 with my Acer using 2.6.28, it's been better with
2.6.29...

Regards,

I used the current Angstrom demo image from
http://www.angstrom-distribution.org/demo/beagleboard/
which is dated 20090326 but doesn't say explicitly which version it is
(2.6.28 I'm guessing)

kb

I've verified it's 2.6.28

I just hit reset again, but theSB devices are still "locked" even
though it claims to see them.

There are some errors in the boot log -- could it be the SD card? Or
is that onboard memory?

Unplugging and replugging the USB hub causes messages about the
devices, but the still remain inert.

--------- Snippet from Boot Log with Errors ----

Remounting root file system...
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector
0
Buffer I/O error on device mtdblock0, logical block 0
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector
8
Buffer I/O error on device mtdblock0, logical block 1
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector
16
Buffer I/O error on device mtdblock0, logical block 2
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector
24
Buffer I/O error on device mtdblock0, logical block 3
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector
0
Buffer I/O error on device mtdblock0, logical block 0
NET: Registered protocol family 10
Unknown HZ value! (67) Assume 100.
ALSA: Restoring mixer settings...
Configuring network interfaces... ifup: interface lo already
configured
ifup: interface eth0 already configured
done.
Starting portmap daemon: portmapNo state is present for card
omap3beagle
/usr/sbin/alsactl: parse:1620: Unable to open file '/usr/share/alsa/
init/00main': No such file or directory
No state is present for card omap3beagle
.
Unknown HZ value! (68) Assume 100.
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
INIT: Entering runlevel: 5
Configuring leds:
  beagleboard::usr0: heartbeat
  beagleboard::usr1: mmc0
Starting Dropbear SSH server: dropbear.
Starting advanced power management daemon: No APM support in kernel
(failed.)
Starting system message bus: start-stop-daemon: open pidfile /var/run/
dbus/pid: Stale NFS file handle
Starting syslogd/klogd: done
* Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
Failed to open PID file: Stale NFS file handle
Failed to open PID file: Stale NFS file handle
*[fail]

--------------------------------- FULL BOOT LOG

I've verified it's 2.6.28

I just hit reset again, but theSB devices are still "locked" even
though it claims to see them.

There are some errors in the boot log -- could it be the SD card? Or
is that onboard memory?

Unplugging and replugging the USB hub causes messages about the
devices, but the still remain inert.

For some reason, the angstrom demo page isn't loading for me at the
moment. (although i've been fighting internal network problems all
day. :wink: rack shuffle) But there should be a 2.6.29-r31 there at some
point on there..

You can use the uImage i've built and tested for the debian variants
(100% source same), just to verify/test your lcd.
located here: http://www.rcn-ee.com/deb/kernel/CC-beagle-v2.6.29-58cf2f1-oer31.1

Just run these in terminal from your sd card:

wget http://www.rcn-ee.com/deb/kernel/CC-beagle-v2.6.29-58cf2f1-oer31.1
mv CC-beagle-v2.6.29-58cf2f1-oer31.1 uImage

note, the lcd string changes with 2.6.29

Thanks Robert, I really appreciate your effort! I might have screwed
up on this though.

I ran those commands on my (networked) ubuntu machine, it all seemed
fine, put the SD into the BB and fired it up but I get a FAT failure
right away (see below), so now I don't have any Angstrom at all.

Putting the SD card back into the ubuntu box, it claims that the boot
partition is read-only and won't re-execute the same 'wget' (or
obviously, 'mv') commands (and yes, the little lock slide on the SD is
in the right position)

When I run 'ls -l' on the uImage that *is* on the SD, it still shows
the old date, but now won't launch.

hrrm....

------ very short boot log ---

Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2009.01-00013-g52eddcd (Feb 03 2009 - 22:22:56)

OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM: 256 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Board revision C
Serial #699a00030000000004013f7903022014
Hit any key to stop autoboot: 0
reading uImage
Invalid FAT entry

512 bytes read
## Booting kernel from Legacy Image at 80300000 ...
   Image Name: Angstrom/2.6.28/beagleboard
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 2706168 Bytes = 2.6 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
OMAP3 beagleboard.org #

I always forget about ubuntu's auto-mount do this..

sudo fdisk -l (find your mmc card, probally /dev/sdb)

next type:
mount

should look something like this, probally vfat: (nosuid and nodev is
what makes this difficult)
/dev/sdb1 on /media/disk type ext3 (rw,nosuid,nodev,uhelper=hal)

lets umount it

sudo umount /media/disk

mkdir temp-mnt

sudo mount /dev/sdb1 ./temp-mnt
cd ./temp-mnt

sudo wget http://www.rcn-ee.com/deb/kernel/CC-beagle-v2.6.29-58cf2f1-oer31.1
sudo mv CC-beagle-v2.6.29-58cf2f1-oer31.1 uImage
sync

cd ..
sudo umount ./temp-mnt

Regards,

ahh... (light turns on) -- is there a different distro for my PC that
would be better for BB development? I only installed ubuntu recently
on that machine, specifically to make BB dev simpler. I'm happy to
switch if that would simplify the process.

So it booted right up! Though the boot log contained some errors, and
it still doesn't recognize keystrokes or mouse movement, though the
log does say it has identified the usb hub and its 4 ports....

The errors I got give me the feeling I'm missing part of the 2.6.29
data? (sadly, angstrom-dsitribution.org seems to be down atm...)

thanks again so much,
kb

--- errors only ---

...
modprobe: FATAL: Could not load /lib/modules/2.6.29/modules.dep: No
such file or directory

WARNING: Couldn't open directory /lib/modules/2.6.29: No such file or
directory
FATAL: Could not open /lib/modules/2.6.29/modules.dep.temp for
writing: No such file or directory

...

Starting Dropbear SSH server: modprobe: FATAL: Could not load /lib/
modules/2.6.29/modules.dep: No such file or directory

modprobe: FATAL: Could not load /lib/modules/2.6.29/modules.dep: No
such file or directory

dropbear.
Starting advanced power management daemon: No APM support in kernel
(failed.)

ahh... (light turns on) -- is there a different distro for my PC that
would be better for BB development? I only installed ubuntu recently
on that machine, specifically to make BB dev simpler. I'm happy to
switch if that would simplify the process.

It's fine. I usually have auto-mount in ubuntu disabled, so i assumed
to much when i sent the first message this morning. :wink:

So it booted right up! Though the boot log contained some errors, and
it still doesn't recognize keystrokes or mouse movement, though the
log does say it has identified the usb hub and its 4 ports....

Does your LCD work? 2.6.29's pretty picky about usb hubs..

The errors I got give me the feeling I'm missing part of the 2.6.29
data? (sadly, angstrom-dsitribution.org seems to be down atm...)

correct. :wink:

Starting Dropbear SSH server: modprobe: FATAL: Could not load /lib/
modules/2.6.29/modules.dep: No such file or directory

modprobe: FATAL: Could not load /lib/modules/2.6.29/modules.dep: No
such file or directory

These are fine, they were built as external modules, so the uImage
doesn't have them, but for basic networking and first boot up it's
fine.

Regards,

great!

Yes, the LCD does show me the login screen, and it seems to get there
EVERY time I power-on or reset (a few times now), which is a definite
improvement!

But no USB. Which is a mystery, since it HAD previously worked... I'm
connecting via a little D-Link "h4" hub, both the BB and the hub have
their own wall-socket power bricks. The system does know about the
hub... for example if I unplug the mouse, I see:

[ 248.538238] usb 1-2.2: USB disconnect, address 4

and restoring the connection:

[ 282.314971] usb 1-2.2: new low speed USB device using ehci-omap and
address 5
[ 282.445129] usb 1-2.2: configuration #1 chosen from 1 choice
[ 282.463775] input: Microsoft Microsoft 5-Button Mouse with
IntelliEye(TM) as /class/input/input5
[ 282.473327] generic-usb 0003:045E:0047.0004: input: USB HID v1.10
Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-
ehci-omap.0-2.2/input0

Similar behavior for the keyboard, disconnecting as 3 and reconnecting
as 6...

Powering down the entire hub:

[ 765.178039] usb 1-2: USB disconnect, address 2
[ 765.183197] usb 1-2.1: USB disconnect, address 6
[ 765.191223] usb 1-2.2: USB disconnect, address 5
[ 765.529388] usb 1-2: new high speed USB device using ehci-omap and
address 7
[ 765.691650] usb 1-2: configuration #1 chosen from 1 choice
[ 765.698059] hub 1-2:1.0: USB hub found
[ 765.704101] hub 1-2:1.0: 4 ports detected
[ 766.002227] usb 1-2.1: new low speed USB device using ehci-omap and
address 8
[ 766.135101] usb 1-2.1: configuration #1 chosen from 1 choice
[ 766.152221] input: ORTEK ORTEK Combo Keyboard V1.5 as /class/input/
input8
[ 766.159545] generic-usb 0003:05A4:9760.0007: input: USB HID v1.00
Keyboard [ORTEK ORTEK Combo Keyboard V1.5] on usb-ehci-omap.0-2.1/
input0
[ 766.202972] input: ORTEK ORTEK Combo Keyboard V1.5 as /class/input/
input9
[ 766.210601] generic-usb 0003:05A4:9760.0008: input: USB HID v1.00
Device [ORTEK ORTEK Combo Keyboard V1.5] on usb-ehci-omap.0-2.1/input1
[ 766.332275] usb 1-2.2: new low speed USB device using ehci-omap and
address 9
[ 766.461029] usb 1-2.2: configuration #1 chosen from 1 choice
[ 766.479614] input: Microsoft Microsoft 5-Button Mouse with
IntelliEye(TM) as /class/input/input10
[ 766.489196] generic-usb 0003:045E:0047.0009: input: USB HID v1.10
Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-
ehci-omap.0-2.2/input0

and repowering it:

[ 814.909240] usb 1-2: USB disconnect, address 7
[ 814.913726] usb 1-2.1: USB disconnect, address 8
[ 814.922302] usb 1-2.2: USB disconnect, address 9
[ 815.243896] usb 1-2: new high speed USB device using ehci-omap and
address 10
[ 815.402465] usb 1-2: configuration #1 chosen from 1 choice
[ 815.408843] hub 1-2:1.0: USB hub found
[ 815.414886] hub 1-2:1.0: 4 ports detected
[ 815.713165] usb 1-2.1: new low speed USB device using ehci-omap and
address 11
[ 815.846527] usb 1-2.1: configuration #1 chosen from 1 choice
[ 815.867279] input: ORTEK ORTEK Combo Keyboard V1.5 as /class/input/
input11
[ 815.874725] generic-usb 0003:05A4:9760.000A: input: USB HID v1.00
Keyboard [ORTEK ORTEK Combo Keyboard V1.5] on usb-ehci-omap.0-2.1/
input0
[ 815.906860] input: ORTEK ORTEK Combo Keyboard V1.5 as /class/input/
input12
[ 815.914489] generic-usb 0003:05A4:9760.000B: input: USB HID v1.00
Device [ORTEK ORTEK Combo Keyboard V1.5] on usb-ehci-omap.0-2.1/input1
[ 816.026092] usb 1-2.2: new low speed USB device using ehci-omap and
address 12
[ 816.156219] usb 1-2.2: configuration #1 chosen from 1 choice
[ 816.174926] input: Microsoft Microsoft 5-Button Mouse with
IntelliEye(TM) as /class/input/input13
[ 816.184539] generic-usb 0003:045E:0047.000C: input: USB HID v1.10
Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-
ehci-omap.0-2.2/input0

which to ME looks like it's behaving properly...

does this mean anything?

root@beagleboard:~# ls -l /dev/usb*
crw-rw---- 1 root root 252, 5 May 7 02:54 /dev/usbdev1.10_ep00
crw-rw---- 1 root root 252, 4 May 7 02:54 /dev/usbdev1.10_ep81
crw-rw---- 1 root root 252, 8 May 7 02:54 /dev/usbdev1.11_ep00
crw-rw---- 1 root root 252, 6 May 7 02:54 /dev/usbdev1.11_ep81
crw-rw---- 1 root root 252, 7 May 7 02:54 /dev/usbdev1.11_ep82
crw-rw---- 1 root root 252, 10 May 7 02:54 /dev/usbdev1.12_ep00
crw-rw---- 1 root root 252, 9 May 7 02:54 /dev/usbdev1.12_ep81
crw-rw---- 1 root root 252, 1 Jan 1 2000 /dev/usbdev1.1_ep00
crw-rw---- 1 root root 252, 0 Jan 1 2000 /dev/usbdev1.1_ep81
crw-rw---- 1 root root 252, 3 Jan 1 2000 /dev/usbdev2.1_ep00
crw-rw---- 1 root root 252, 2 Jan 1 2000 /dev/usbdev2.1_ep81
crw-rw---- 1 root root 253, 0 Jan 1 2000 /dev/usbmon0
crw-rw---- 1 root root 253, 1 Jan 1 2000 /dev/usbmon1
crw-rw---- 1 root root 253, 2 Jan 1 2000 /dev/usbmon2

the low-numbered devices have very old dates....

thx,
kb
(Applications guy with a lot of old unix experience but limited linux)

The devices appear in "lsusb" too btw

fixed! See http://groups.google.com/group/beagleboard/browse_thread/thread/3bc373c0d4ef9206?hl=en

thx again Robert
(and Koen for Narcissus)

kb
(who is slowly remembering what df dd and ps mean...)

Cool, just missing modules. That explains a couple other weird
reported bugs with usb/keyboards not being found with the network
install routines for debian. Time to enable more modules as
built-in..

Thanks,

I got this when I installed the wrong image, check that you selected
beagleboard as the machine (http://amethyst.openembedded.net/~koen/
narcissus/)