Inconsistent BB Startup Behavior from Session to Session
21 views
Skip to first unread message
KB
May 8, 2009, 6:53:09 PM5/8/09
to Beagle Board
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
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
Robert Nelson
May 8, 2009, 7:22:26 PM5/8/09
to beagl...@googlegroups.com
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,
--
Robert Nelson
http://www.rcn-ee.com/
Joker B
May 8, 2009, 9:22:44 PM5/8/09
to Beagle Board
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
On May 8, 4:22 pm, Robert Nelson <robertcnel...@gmail.com> wrote:
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
On May 8, 4:22 pm, Robert Nelson <robertcnel...@gmail.com> wrote:
Joker B
May 9, 2009, 1:43:59 AM5/9/09
to Beagle Board
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
-------------------------------------------------------------------------
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
2706232 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 ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing
Linux..............................................................................................................................................................................
done, booting the kernel.
Linux version 2.6.28-omap1 (koen@dominion) (gcc version 4.3.1 (GCC) )
#1 Tue Mar 24 18:57:27 CET 2009
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 ES3.0
SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
Reserving 15728640 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages:
65024
Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw
rootwait
Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz
GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP34xx GPIO hardware version 2.5
PID hash table entries: 1024 (order: 10, 4096 bytes)
OMAP clockevent source: GPTIMER12 at 32768 Hz
Console: colour dummy device 80x30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 238592KB available (5008K code, 437K data, 196K init)
Calibrating delay loop... 502.07 BogoMIPS (lpj=1961984)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 532 bytes
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
USB: No board-specific platform config found
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
OMAP DSI rev 1.0
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
SCSI subsystem initialized
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
Bluetooth: Core ver 2.13
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain,
max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 466
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbcore: registered new interface driver catc
catc: v2.8:CATC EL1210A NetMate USB Ethernet driver
usbcore: registered new interface driver kaweth
pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet driver
usbcore: registered new interface driver rtl8150
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver smsc95xx
usbcore: registered new interface driver gl620a
usbcore: registered new interface driver net1080
usbcore: registered new interface driver plusb
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver cdc_subset
Broadcom 43xx driver loaded [ Features: L, Firmware-ID: FW13 ]
usbcore: registered new interface driver zd1211rw
usbcore: registered new interface driver rndis_wlan
usbcore: registered new interface driver zd1201
usbcore: registered new interface driver usb8xxx
usbcore: registered new interface driver rtl8187
usbcore: registered new interface driver rt2500usb
usbcore: registered new interface driver rt73usb
usbcore: registered new interface driver p54usb
i2c /dev entries driver
input: triton2-pwrbutton as /class/input/input0
triton2 power button driver initialized
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB
1,8V 16-bit)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand":
0x00000000-0x00080000 : "X-Loader"
0x00080000-0x00260000 : "U-Boot"
0x00260000-0x00280000 : "U-Boot Env"
0x00280000-0x00680000 : "Kernel"
0x00680000-0x10000000 : "File System"
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_cdc gadget: using random self ethernet address
g_cdc gadget: using random host ethernet address
usb0: MAC 32:e0:2a:f0:31:f5
usb0: HOST MAC e2:6c:12:91:8a:3a
g_cdc gadget: CDC Composite Gadget, version: King Kamehameha Day 2008
g_cdc gadget: g_cdc ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mice: PS/2 mouse device common for all mice
input: gpio-keys as /class/input/input1
twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Bluetooth: HCI USB driver ver 2.10
usbcore: registered new interface driver hci_usb
Bluetooth: Broadcom Blutonium firmware driver ver 1.2
usbcore: registered new interface driver bcm203x
Bluetooth: Digianswer Bluetooth USB driver ver 0.10
usbcore: registered new interface driver bpa10x
Bluetooth: Generic Bluetooth SDIO driver ver 0.1
mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
Registered led device: beagleboard::usr0
Registered led device: beagleboard::usr1
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
usbcore: registered new interface driver snd-usb-audio
ASoC version 0.13.2
OMAP3 Beagle SoC init
TWL4030 Audio Codec init
asoc: twl4030 <-> omap-mcbsp-dai-(link_id) mapping ok
usb 1-2: new high speed USB device using ehci-omap and address 2
ALSA device list:
#0: omap3beagle (twl4030)
oprofile: using arm/armv7
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: L2CAP ver 2.11
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.10
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jket...@linux.intel.com>
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
SmartReflex driver initialized
Disabling unused clock "sr2_fck"
Disabling unused clock "sr1_fck"
Disabling unused clock "mcbsp_fck"
Disabling unused clock "mcbsp_fck"
Disabling unused clock "mcbsp_fck"
Disabling unused clock "mcbsp_ick"
Disabling unused clock "mcbsp_ick"
Disabling unused clock "mcbsp_ick"
Disabling unused clock "gpt2_ick"
Disabling unused clock "gpt3_ick"
Disabling unused clock "gpt4_ick"
Disabling unused clock "gpt5_ick"
Disabling unused clock "gpt6_ick"
Disabling unused clock "gpt7_ick"
Disabling unused clock "gpt8_ick"
Disabling unused clock "gpt9_ick"
Disabling unused clock "wdt3_ick"
Disabling unused clock "wdt3_fck"
Disabling unused clock "gpio2_dbck"
Disabling unused clock "gpio3_dbck"
Disabling unused clock "gpio4_dbck"
Disabling unused clock "gpio5_dbck"
Disabling unused clock "gpio6_dbck"
Disabling unused clock "gpt9_fck"
Disabling unused clock "gpt8_fck"
Disabling unused clock "gpt7_fck"
Disabling unused clock "gpt6_fck"
Disabling unused clock "gpt5_fck"
Disabling unused clock "gpt4_fck"
Disabling unused clock "gpt3_fck"
Disabling unused clock "gpt2_fck"
Disabling unused clock "gpt1_ick"
Disabling unused clock "wdt1_ick"
Disabling unused clock "wdt2_ick"
Disabling unused clock "wdt2_fck"
Disabling unused clock "gpio1_dbck"
Disabling unused clock "gpt1_fck"
Disabling unused clock "cam_ick"
Disabling unused clock "cam_mclk"
Disabling unused clock "des1_ick"
Disabling unused clock "sha11_ick"
Disabling unused clock "rng_ick"
Disabling unused clock "aes1_ick"
Disabling unused clock "ssi_ick"
Disabling unused clock "mailboxes_ick"
Disabling unused clock "mcbsp_ick"
Disabling unused clock "mcbsp_ick"
Disabling unused clock "gpt10_ick"
Disabling unused clock "gpt11_ick"
Disabling unused clock "i2c_ick"
Disabling unused clock "mcspi_ick"
Disabling unused clock "mcspi_ick"
Disabling unused clock "mcspi_ick"
Disabling unused clock "mcspi_ick"
Disabling unused clock "hdq_ick"
Disabling unused clock "mspro_ick"
Disabling unused clock "des2_ick"
Disabling unused clock "sha12_ick"
Disabling unused clock "aes2_ick"
Disabling unused clock "icr_ick"
Disabling unused clock "pka_ick"
Disabling unused clock "ssi_ssr_fck"
Disabling unused clock "hdq_fck"
Disabling unused clock "mcspi_fck"
Disabling unused clock "mcspi_fck"
Disabling unused clock "mcspi_fck"
Disabling unused clock "mcspi_fck"
Disabling unused clock "mcbsp_fck"
Disabling unused clock "mcbsp_fck"
Disabling unused clock "i2c_fck"
Disabling unused clock "mspro_fck"
Disabling unused clock "gpt11_fck"
Disabling unused clock "gpt10_fck"
Disabling unused clock "dpll4_m6x2_ck"
Disabling unused clock "dpll3_m3x2_ck"
Disabling unused clock "sys_clkout1"
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev
1
registered taskstats version 1
Console: switching to colour frame buffer device 80x30
clock: clksel_round_rate_div: dpll4_m4_ck target_rate 48000000
clock: new_div = 9, new_rate = 48000000
twl4030_rtc twl4030_rtc: setting system clock to 2009-05-07 14:46:59
UTC (1241707619)
Waiting for root device /dev/mmcblk0p2...
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
mmc0: new high speed SD card at address b9da
mmcblk0: mmc0:b9da SD02G 1.83 GiB
mmcblk0: p1 p2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 196K
INIT: version 2.86 booting
usb 1-2.1: new low speed USB device using ehci-omap and address 3
usb 1-2.1: configuration #1 chosen from 1 choice
input: B16_b_02 USB-PS/2 Optical Mouse as /class/input/input2
generic-usb 0003:046D:C024.0001: input: USB HID v1.10 Mouse [B16_b_02
USB-PS/2 Optical Mouse] on usb-ehci-omap.0-2.1/input0
usb 1-2.2: new low speed USB device using ehci-omap and address 4
Please wait: booting...
Starting udevusb 1-2.2: configuration #1 chosen from 1 choice
input: LITEON Technology USB Multimedia Keyboard as /class/input/
input3
generic-usb 0003:046D:C313.0002: input: USB HID v1.10 Keyboard [LITEON
Technology USB Multimedia Keyboard] on usb-ehci-omap.0-2.2/input0
input: LITEON Technology USB Multimedia Keyboard as /class/input/
input4
generic-usb 0003:046D:C313.0003: input: USB HID v1.10 Device [LITEON
Technology USB Multimedia Keyboard] on usb-ehci-omap.0-2.2/input1
udevd version 124 started
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]
Starting Connection Manager
Starting Bluetooth subsystem: hcid hid2hci.
Running ntpdate to synchronize clockError : Temporary failure in name
resolution
.
Starting GPE display manager: gpe-dm
.-------.
| | .-.
| | |-----.-----.-----.| | .----..-----.-----.
| | | __ | ---'| '--.| .-'| | |
| | | | | |--- || --'| | | ' | | | |
'---'---'--'--'--. |-----''----''--' '-----'-'-'-'
-' |
'---'
The Angstrom Distribution beagleboard ttyS2
Angstrom 2009.X-test-20090305 beagleboard ttyS2
beagleboard login: root
root@beagleboard:~# ls
cmdline~ cmdlinz~
root@beagleboard:~#
--------------------------------------------------
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
-------------------------------------------------------------------------
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
2706232 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 ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing
Linux..............................................................................................................................................................................
done, booting the kernel.
Linux version 2.6.28-omap1 (koen@dominion) (gcc version 4.3.1 (GCC) )
#1 Tue Mar 24 18:57:27 CET 2009
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 ES3.0
SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
Reserving 15728640 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages:
65024
Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw
rootwait
Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz
GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP34xx GPIO hardware version 2.5
PID hash table entries: 1024 (order: 10, 4096 bytes)
OMAP clockevent source: GPTIMER12 at 32768 Hz
Console: colour dummy device 80x30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 238592KB available (5008K code, 437K data, 196K init)
Calibrating delay loop... 502.07 BogoMIPS (lpj=1961984)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 532 bytes
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
USB: No board-specific platform config found
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
OMAP DSI rev 1.0
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
SCSI subsystem initialized
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
Bluetooth: Core ver 2.13
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain,
max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 466
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbcore: registered new interface driver catc
catc: v2.8:CATC EL1210A NetMate USB Ethernet driver
usbcore: registered new interface driver kaweth
pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet driver
usbcore: registered new interface driver rtl8150
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver smsc95xx
usbcore: registered new interface driver gl620a
usbcore: registered new interface driver net1080
usbcore: registered new interface driver plusb
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver cdc_subset
Broadcom 43xx driver loaded [ Features: L, Firmware-ID: FW13 ]
usbcore: registered new interface driver zd1211rw
usbcore: registered new interface driver rndis_wlan
usbcore: registered new interface driver zd1201
usbcore: registered new interface driver usb8xxx
usbcore: registered new interface driver rtl8187
usbcore: registered new interface driver rt2500usb
usbcore: registered new interface driver rt73usb
usbcore: registered new interface driver p54usb
i2c /dev entries driver
input: triton2-pwrbutton as /class/input/input0
triton2 power button driver initialized
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB
1,8V 16-bit)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand":
0x00000000-0x00080000 : "X-Loader"
0x00080000-0x00260000 : "U-Boot"
0x00260000-0x00280000 : "U-Boot Env"
0x00280000-0x00680000 : "Kernel"
0x00680000-0x10000000 : "File System"
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_cdc gadget: using random self ethernet address
g_cdc gadget: using random host ethernet address
usb0: MAC 32:e0:2a:f0:31:f5
usb0: HOST MAC e2:6c:12:91:8a:3a
g_cdc gadget: CDC Composite Gadget, version: King Kamehameha Day 2008
g_cdc gadget: g_cdc ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mice: PS/2 mouse device common for all mice
input: gpio-keys as /class/input/input1
twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Bluetooth: HCI USB driver ver 2.10
usbcore: registered new interface driver hci_usb
Bluetooth: Broadcom Blutonium firmware driver ver 1.2
usbcore: registered new interface driver bcm203x
Bluetooth: Digianswer Bluetooth USB driver ver 0.10
usbcore: registered new interface driver bpa10x
Bluetooth: Generic Bluetooth SDIO driver ver 0.1
mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
Registered led device: beagleboard::usr0
Registered led device: beagleboard::usr1
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
usbcore: registered new interface driver snd-usb-audio
ASoC version 0.13.2
OMAP3 Beagle SoC init
TWL4030 Audio Codec init
asoc: twl4030 <-> omap-mcbsp-dai-(link_id) mapping ok
usb 1-2: new high speed USB device using ehci-omap and address 2
ALSA device list:
#0: omap3beagle (twl4030)
oprofile: using arm/armv7
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: L2CAP ver 2.11
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.10
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jket...@linux.intel.com>
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
SmartReflex driver initialized
Disabling unused clock "sr2_fck"
Disabling unused clock "sr1_fck"
Disabling unused clock "mcbsp_fck"
Disabling unused clock "mcbsp_fck"
Disabling unused clock "mcbsp_fck"
Disabling unused clock "mcbsp_ick"
Disabling unused clock "mcbsp_ick"
Disabling unused clock "mcbsp_ick"
Disabling unused clock "gpt2_ick"
Disabling unused clock "gpt3_ick"
Disabling unused clock "gpt4_ick"
Disabling unused clock "gpt5_ick"
Disabling unused clock "gpt6_ick"
Disabling unused clock "gpt7_ick"
Disabling unused clock "gpt8_ick"
Disabling unused clock "gpt9_ick"
Disabling unused clock "wdt3_ick"
Disabling unused clock "wdt3_fck"
Disabling unused clock "gpio2_dbck"
Disabling unused clock "gpio3_dbck"
Disabling unused clock "gpio4_dbck"
Disabling unused clock "gpio5_dbck"
Disabling unused clock "gpio6_dbck"
Disabling unused clock "gpt9_fck"
Disabling unused clock "gpt8_fck"
Disabling unused clock "gpt7_fck"
Disabling unused clock "gpt6_fck"
Disabling unused clock "gpt5_fck"
Disabling unused clock "gpt4_fck"
Disabling unused clock "gpt3_fck"
Disabling unused clock "gpt2_fck"
Disabling unused clock "gpt1_ick"
Disabling unused clock "wdt1_ick"
Disabling unused clock "wdt2_ick"
Disabling unused clock "wdt2_fck"
Disabling unused clock "gpio1_dbck"
Disabling unused clock "gpt1_fck"
Disabling unused clock "cam_ick"
Disabling unused clock "cam_mclk"
Disabling unused clock "des1_ick"
Disabling unused clock "sha11_ick"
Disabling unused clock "rng_ick"
Disabling unused clock "aes1_ick"
Disabling unused clock "ssi_ick"
Disabling unused clock "mailboxes_ick"
Disabling unused clock "mcbsp_ick"
Disabling unused clock "mcbsp_ick"
Disabling unused clock "gpt10_ick"
Disabling unused clock "gpt11_ick"
Disabling unused clock "i2c_ick"
Disabling unused clock "mcspi_ick"
Disabling unused clock "mcspi_ick"
Disabling unused clock "mcspi_ick"
Disabling unused clock "mcspi_ick"
Disabling unused clock "hdq_ick"
Disabling unused clock "mspro_ick"
Disabling unused clock "des2_ick"
Disabling unused clock "sha12_ick"
Disabling unused clock "aes2_ick"
Disabling unused clock "icr_ick"
Disabling unused clock "pka_ick"
Disabling unused clock "ssi_ssr_fck"
Disabling unused clock "hdq_fck"
Disabling unused clock "mcspi_fck"
Disabling unused clock "mcspi_fck"
Disabling unused clock "mcspi_fck"
Disabling unused clock "mcspi_fck"
Disabling unused clock "mcbsp_fck"
Disabling unused clock "mcbsp_fck"
Disabling unused clock "i2c_fck"
Disabling unused clock "mspro_fck"
Disabling unused clock "gpt11_fck"
Disabling unused clock "gpt10_fck"
Disabling unused clock "dpll4_m6x2_ck"
Disabling unused clock "dpll3_m3x2_ck"
Disabling unused clock "sys_clkout1"
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev
1
registered taskstats version 1
Console: switching to colour frame buffer device 80x30
clock: clksel_round_rate_div: dpll4_m4_ck target_rate 48000000
clock: new_div = 9, new_rate = 48000000
twl4030_rtc twl4030_rtc: setting system clock to 2009-05-07 14:46:59
UTC (1241707619)
Waiting for root device /dev/mmcblk0p2...
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
mmc0: new high speed SD card at address b9da
mmcblk0: mmc0:b9da SD02G 1.83 GiB
mmcblk0: p1 p2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 196K
INIT: version 2.86 booting
usb 1-2.1: new low speed USB device using ehci-omap and address 3
usb 1-2.1: configuration #1 chosen from 1 choice
input: B16_b_02 USB-PS/2 Optical Mouse as /class/input/input2
generic-usb 0003:046D:C024.0001: input: USB HID v1.10 Mouse [B16_b_02
USB-PS/2 Optical Mouse] on usb-ehci-omap.0-2.1/input0
usb 1-2.2: new low speed USB device using ehci-omap and address 4
Please wait: booting...
Starting udevusb 1-2.2: configuration #1 chosen from 1 choice
input: LITEON Technology USB Multimedia Keyboard as /class/input/
input3
generic-usb 0003:046D:C313.0002: input: USB HID v1.10 Keyboard [LITEON
Technology USB Multimedia Keyboard] on usb-ehci-omap.0-2.2/input0
input: LITEON Technology USB Multimedia Keyboard as /class/input/
input4
generic-usb 0003:046D:C313.0003: input: USB HID v1.10 Device [LITEON
Technology USB Multimedia Keyboard] on usb-ehci-omap.0-2.2/input1
udevd version 124 started
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]
Starting Connection Manager
Starting Bluetooth subsystem: hcid hid2hci.
Running ntpdate to synchronize clockError : Temporary failure in name
resolution
.
Starting GPE display manager: gpe-dm
.-------.
| | .-.
| | |-----.-----.-----.| | .----..-----.-----.
| | | __ | ---'| '--.| .-'| | |
| | | | | |--- || --'| | | ' | | | |
'---'---'--'--'--. |-----''----''--' '-----'-'-'-'
-' |
'---'
The Angstrom Distribution beagleboard ttyS2
Angstrom 2009.X-test-20090305 beagleboard ttyS2
beagleboard login: root
root@beagleboard:~# ls
cmdline~ cmdlinz~
root@beagleboard:~#
--------------------------------------------------
Robert Nelson
May 9, 2009, 11:09:23 AM5/9/09
to beagl...@googlegroups.com
On Sat, May 9, 2009 at 12:43 AM, Joker B <kevin....@gmail.com> wrote:
>
> 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.
>
> 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. ;) 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
from: omap-dss.def_disp=lcd omapfb.video_mode=1280x720MR-16@60
to: omapfb.mode=dvi:1280x720MR-16@60
> --------- 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
These are fine, the kernel just doesn't know what to do with the nand...
Joker B
May 9, 2009, 12:10:44 PM5/9/09
to Beagle Board
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
ERROR: can't get kernel image!
OMAP3 beagleboard.org #
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
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
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
ERROR: can't get kernel image!
OMAP3 beagleboard.org #
Robert Nelson
May 9, 2009, 12:22:02 PM5/9/09
to beagl...@googlegroups.com
On Sat, May 9, 2009 at 11:10 AM, Joker B <kevin....@gmail.com> wrote:
>
> 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....
>
> 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....
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
Joker B
May 9, 2009, 1:01:28 PM5/9/09
to Beagle Board
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.)
On May 9, 9:22 am, Robert Nelson <robertcnel...@gmail.com> wrote:
> sudo wgethttp://www.rcn-ee.com/deb/kernel/CC-beagle-v2.6.29-58cf2f1-oer31.1
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.)
Robert Nelson
May 9, 2009, 1:12:27 PM5/9/09
to beagl...@googlegroups.com
On Sat, May 9, 2009 at 12:01 PM, Joker B <kevin....@gmail.com> wrote:
>
> 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.
>
> 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. ;)
> 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. ;)
> 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.
Joker B
May 9, 2009, 1:44:27 PM5/9/09
to Beagle Board
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)
On May 9, 10:12 am, Robert Nelson <robertcnel...@gmail.com> wrote:
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)
On May 9, 10:12 am, Robert Nelson <robertcnel...@gmail.com> wrote:
Joker B
May 9, 2009, 2:43:45 PM5/9/09
to Beagle Board
The devices appear in "lsusb" too btw
Joker B
May 13, 2009, 3:52:55 AM5/13/09
to Beagle Board
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...)
thx again Robert
(and Koen for Narcissus)
kb
(who is slowly remembering what df dd and ps mean...)
Robert Nelson
May 13, 2009, 9:22:12 AM5/13/09
to beagl...@googlegroups.com
On Wed, May 13, 2009 at 2:52 AM, Joker B <kevin....@gmail.com> wrote:
>
> 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...)
>
>
> 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,
Yoan Blanc
May 25, 2009, 8:31:16 AM5/25/09
to Beagle Board
I got this when I installed the wrong image, check that you selected
beagleboard as the machine (http://amethyst.openembedded.net/~koen/
narcissus/)
--
Yoan
beagleboard as the machine (http://amethyst.openembedded.net/~koen/
narcissus/)
--
Yoan
Reply all
Reply to author
Forward
0 new messages