slow startup (~2 hours) on demo image

[VICKY]

I built the demo image for Beagleboard xM using the instructions on
webpage "http://code.google.com/p/beagleboard/wiki/
BeagleBoardDiagnosticsNext" and it shows very slow start up (~2 hours)
when I plug in the SD card very first time and after that is comes
fine every time. Although I don’t have this issue with the demo image
I downloaded from the web and put on the SD card.

I am very new to this platform, have any body face the same issue? Any
solution?

Regards,
Amit

[Maxim Podbereznyy]

YOU ARE VERY PATIENT! I would not wait 20 minutes, you could stand 2 hours! :))))

2010/10/20 VICKY <vicky...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To post to this group, send email to beagl...@googlegroups.com.
To unsubscribe from this group, send email to beagleboard...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.

[Paul Menzel]

Am Mittwoch, den 20.10.2010, 08:01 -0700 schrieb VICKY:
> I built the demo image for Beagleboard xM using the instructions on
> webpage "http://code.google.com/p/beagleboard/wiki/
> BeagleBoardDiagnosticsNext" and it shows very slow start up (~2 hours)
> when I plug in the SD card very first time and after that is comes
> fine every time.

Ȧngström has to configure the system on the very first installation.
Depending on how much software you have selected, I am guessing it takes
some time. Two hours are very long though.

Is there a certain task taking that much time?

I have never used the BeagleBoardDiagnosticsNext image. Maybe there is
an error or the diagnosis takes so long?

> Although I don’t have this issue with the demo image
> I downloaded from the web and put on the SD card.

I guess the configuration has already been done for these images.

[…]

Thanks,

Paul

[Mittal, Amit]

Thanks Paul,

During below messages it takes longest time (~2 hours)


Configuring hicolor-icon-theme.
Configuring dbus.
System startup links for /etc/init.d/dbus-1 already exist.
Configuring pango-module-basic-x.
Configuring pango-module-basic-fc.
Configuring ttf-dejavu-common.
Configuring ttf-dejavu-sans.
Configuring gdk-pixbuf-loader-png.
Configuring gdk-pixbuf-loader-jpeg.
Configuring gdk-pixbuf-loader-gif.
Configuring gdk-pixbuf-loader-xpm.
Configuring policykit.
Configuring gnome-vfs.
Configuring locale-base-de-de.
Configuring update-modules.
Configuring locale-base-ta-in.
Configuring gnome-keyring.
Configuring epiphany.
Configuring locale-base-en-gb.
Configuring hal.
Undefined users:
> pulse
Skipping /etc/default/volatiles/04_pulse
Configuring gimp.
Configuring locale-base-pt-br.
Configuring gnome-session.
Configuring nautilus.
Updating MIME database... this may take a while.
Configuring gnome-mount.
Configuring gedit.
Configuring libgnomekbd.
WARNING: Failed to parse default value `' for schema (/schemas/desktop/gnome/peripherals/keyboard/indicator/fontSize)
Configuring locale-base-ml-in.
Configuring locale-base-es-es.
Configuring omap3-sgx-modules.
Configuring libgsf.
Configuring libpurple.
Configuring file-roller.
Configuring libgnome-2-0.
Configuring at-spi.
Configuring gnome-terminal.
Configuring nautilus-cd-burner.
Configuring libgweather1.
Configuring gnome-applets.
Configuring locale-base-kn-in.
Configuring gst-plugin-gconfelements.
Configuring networkmanager.
System startup links for /etc/init.d/NetworkManager already exist.
Undefined users:
> pulse
Skipping /etc/default/volatiles/04_pulse
Configuring librsvg-2-gtk.
Configuring gnome-icon-theme.
Configuring gnome-themes.
Configuring locale-base-fr-fr.
Configuring ti-dsplink-module.
Configuring ti-lpm-module.
Configuring gnome-screensaver.
Configuring gnome-media.
Configuring ti-cmem-module.
Configuring evince.
Configuring metacity.
update-alternatives: Linking //usr/bin/x-window-manager to /usr/bin/metacity
Configuring gnome-system-tools.
Configuring shadow.
update-alternatives: Linking //usr/bin/passwd to passwd.shadow
update-alternatives: Linking //usr/sbin/chpasswd to chpasswd.shadow
update-alternatives: Linking //usr/bin/chfn to chfn.shadow
update-alternatives: Linking //usr/bin/chsh to chsh.shadow
update-alternatives: Linking //bin/login to login.shadow
update-alternatives: Error: not linking //sbin/vipw to vipw.shadow since //sbin/vipw exists and is not a link
update-alternatives: Linking //sbin/vigr to vigr.shadow
Configuring gdm.
System startup links for /etc/init.d/gdm already exist.
adduser: /var/lib/gdm: File exists
Configuring ppp.
Configuring ppp-dialin.
Configuring gnome-bluetooth.
Configuring network-manager-applet.
Configuring gnome-control-center.
Updating MIME database... this may take a while.
Configuring gnome-settings-daemon.
Configuring gnome-games-common.
Configuring gnome-games-gnomine.
Configuring pulseaudio-server.
Configuring gnumeric.
Configuring ttf-dejavu-sans-mono.
Configuring gnome-utils.
Configuring ttf-liberation-sans.
Configuring pulseaudio-alsa-wrapper.
Configuring pulseaudio-esd-wrapper.
Configuring ti-sdma-module.
Configuring gnome-games-iagno.
Configuring gnome-mplayer.
Configuring gconf-editor.
Configuring gnome-games-gnotski.
Configuring ttf-arphic-uming.
Configuring ttf-dejavu-serif.
Configuring ttf-liberation-serif.
Configuring ttf-liberation-mono.
Configuring gnome-panel.
Configuring gnome-power-manager.
Configuring gnome-system-monitor.
Configuring totem.
Configuring gnome-games-gtali.
Configuring angstrom-libc-fixup-hack.
Configuring libnss-mdns.
Configuring avahi-daemon.
System startup links for /etc/init.d/avahi-daemon already exist.
Configuring avahi-autoipd.
Configuring gnome-games-gnotravex.
Configuring gnome-games-gnobots2.
Configuring gnome-games-aisleriot.
Configuring gnome-games-glchess.
Configuring gnome-games-glines.
Configuring gnome-games-gnect.
Configuring gnome-games-mahjongg.
Configuring ntpdate.
adding crontab
Configuring midori.
Configuring locale-base-en-us.

Regards,

[Koen Kooi]

Op 20 okt 2010, om 23:12 heeft Paul Menzel het volgende geschreven:

> Am Mittwoch, den 20.10.2010, 08:01 -0700 schrieb VICKY:
>> I built the demo image for Beagleboard xM using the instructions on
>> webpage "http://code.google.com/p/beagleboard/wiki/
>> BeagleBoardDiagnosticsNext" and it shows very slow start up (~2 hours)
>> when I plug in the SD card very first time and after that is comes
>> fine every time.
>
> Ȧngström has to configure the system on the very first installation.
> Depending on how much software you have selected, I am guessing it takes
> some time. Two hours are very long though.
>
> Is there a certain task taking that much time?

It depends on the speed of the SD card used. With all sandisk cards on my desk it takes 10-15 minutes, with kingston cards (the ones that amazon sells for next to nothing) it takes close to two hours.
The card that comes with the xM isn't a speed daemon either since it needed to be cheap enough to get included. The plan is to make "preconfigured" images available in the future.

regards,

Koen

[Mittal, Amit]

Koen,

Thanks for sharing this info, and data is also matching as I am also using Kingston SD card. I will try with higher speed SD card. But still 10-15 minutes are too high.

Can you please guide how to make "preconfigured" image.

Regards,
Amit

-----Original Message-----
From: beagl...@googlegroups.com [mailto:beagl...@googlegroups.com] On Behalf Of Koen Kooi
Sent: Wednesday, October 20, 2010 4:55 PM
To: beagl...@googlegroups.com
Subject: Re: [beagleboard] slow startup (~2 hours) on demo image

[Maxim Podbereznyy]

What do you expect from ARM system? Want to get the speed - use x86 with huge heatsink :)

2010/10/21 Mittal, Amit <amit....@ti.com>

[Paul Menzel]

Dear Amit,

please do not top post.

Am Donnerstag, den 21.10.2010, 04:06 +0530 schrieb Mittal, Amit:

> Thanks for sharing this info, and data is also matching as I am also using Kingston SD card. I will try with higher speed SD card. But still 10-15 minutes are too high.
>
> Can you please guide how to make "preconfigured" image.

Did not you write, that it worked fine for you after the first boot. So
create your image, boot it once and take that once booted image as the
base.

Thanks,

Paul

[Mark Lazarewicz]

I unplugged my C4 from USB Hub and waited 10 minutes and got a real nice GUI olnn DVI   Plugging in hub it kernel panicks I am NOT using external power  supply   Any help appreciated       -------. |       |                  .-. |   |   |-----.-----.-----.| |   .----..-----.-----. |       |     | __  |  ---'| '--.|  .-'|     |     | |   |   |  |  |     |---  ||  --'|  |  |  '  | | | | '---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'                 -'  |                 '---' The Angstrom Distribution beagleboard ttyS2 Angstrom 2010.7-test-20100820 beagleboard ttyS2 beagleboard login: [  306.734588] usb 2-2: new high speed USB device using ehci- omap and address 2 [  306.892547] usb 2-2: New USB device found, idVendor=05e3, idProduct=0608 [  306.899658] usb 2-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [  306.907104] usb 2-2: Product: USB2.0 Hub [  306.916900] hub 2-2:1.0: USB hub found [  306.920715] Unable to handle kernel NULL pointer dereference at virtual addre ss 00000014 [  306.928863] pgd = c0004000 [  306.931579] [00000014] *pgd=00000000 [  306.935180] Internal error: Oops: 17 [#2] PREEMPT [  306.939910] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_set speed [  306.947509] Modules linked in: bufferclass_ti omaplfb pvrsrvkm sdmak lpm_omap 3530 dsplinkk cmemk rfcomm ircomm_tty ircomm irda ipv6 hidp l2cap bluetooth rfki ll rtc_twl rtc_core mt9t112(+) mailbox_mach mailbox [  306.966308] CPU: 0    Tainted: G      D W   (2.6.32 #3) [  306.971588] PC is at musb_interrupt+0x9f8/0xbb8 [  306.976135] LR is at musb_interrupt+0x9e4/0xbb8 [  306.980682] pc : [<c033df94>]    lr : [<c033df80>]    psr: 60000193 [  306.980682] sp : cf887b78  ip : cf887bb0  fp : 000000e0 [  306.992218] r10: 00000000  r9 : 00000099  r8 : 00000001 [  306.997467] r7 : 00000000  r6 : cf82b108  r5 : 00000001  r4 : 00000000 [  307.004028] r3 : 00000000  r2 : 00000000  r1 : fa0ab000  r0 : cf82b108 [  307.010620] Flags: nZCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment ker nel [  307.018035] Control: 10c5387d  Table: 8fbcc019  DAC: 00000017 [  307.023803] Process khubd (pid: 14, stack limit = 0xcf8862f0) [  307.029602] Stack: (0xcf887b78 to 0xcf888000) [  307.033966] 7b60:                                                       0003b 9ad 00000000 [  307.042205] 7b80: 00000010 00000001 00000000 cf82b108 60000113 cf8a0900 cf886 000 0000005c [  307.050415] 7ba0: 00000000 00000000 c0667ac0 c033e1b8 c005e3bc cf8a0900 c0635 148 c00a33a0 [  307.058654] 7bc0: c06bbad0 cf8a0900 c0635148 0000005c 00000002 00000001 cf886 000 cf887c75 [  307.066864] 7be0: cf887c66 c00a5498 0000005c 00000000 cf887c75 c003b074 00005 fac ffffffff [  307.075103] 7c00: fa200000 c003bb44 00000001 20000013 00000001 c063100c 00000 001 00000047 [  307.083312] 7c20: cf887c75 c067da23 0000001b 00000030 cf887c75 cf887c66 cf887 c28 cf887c50 [  307.091552] 7c40: c006d23c c006d904 20000013 ffffffff cfbc5270 00000036 00000 000 20000013 [  307.099761] 7c60: cf887cec 205b7ca4 36303320 3631392e 5d303039 cf800020 00000 001 00000000 [  307.108001] 7c80: 00000000 c06b46fc 00000000 cf886000 00000000 c0255bd0 c0483 f30 cebc3020 [  307.116210] 7ca0: cebc3000 00000000 cebc3020 c0653328 cebc3000 cf2b6000 00000 000 c04838b0 [  307.124450] 7cc0: 00000000 c031e128 c05b1c6b c05b1f9c ca341a40 c0653328 22222 222 22222222 [  307.132659] 7ce0: 00000000 cf2b6318 cebc3000 00000001 cf2b6068 ce8c27c0 cf2b6 000 c0484bb8 [  307.140899] 7d00: cf2b6000 cebc3020 cebc3000 00000000 cf2b6000 c0653328 c0653 3dc c06532f8 [  307.149108] 7d20: 00000000 c03264a0 00000000 c02babd8 cebc3020 c0653328 00000 000 c0653468 [  307.157348] 7d40: cebc3028 c02baa78 cebc3020 00000000 c02babd8 cebc3020 cf887 d60 c02b9eb0 [  307.165557] 7d60: cf87a808 cf87a574 c008c924 cebc3020 cebc3020 cebc3054 00000 000 c02bacbc [  307.173797] 7d80: cebc3000 cebc3020 cf2b6000 c02b9ce4 00000000 c02b861c cf2b6 000 cf2b6068 [  307.182006] 7da0: cebc3028 00000000 00000021 c0256d04 ce8c2388 cebc3000 cebc3 000 cf2b6000 [  307.190246] 7dc0: 00000000 cf039400 cf039400 00000001 ce8c2380 c0324cbc 00000 001 00000000 [  307.198455] 7de0: 00000000 00000000 00001388 c0062044 00000000 00000001 cfa2c c00 cf2b6004 [  307.206695] 7e00: 00000000 ca341a80 00000001 cf2b6068 cf039400 cf039404 00000 000 cf2b6000 [  307.214904] 7e20: 00000001 cf2b6068 c0653b2c 00000000 c0653294 cf2b6070 00000 000 c032ce3c [  307.223144] 7e40: cf2b6070 c0653b2c 00000000 c02babd8 cf2b6068 c032501c cf2b6 068 c02baa78 [  307.231353] 7e60: cf2b6068 00000000 c02babd8 cf2b6068 cf887e78 c02b9eb0 cf87a 808 cf87a4f4 [  307.239593] 7e80: c008c924 cf2b6068 cf2b6068 cf2b609c cfa2cc00 c02bacbc cf887 eb9 cf2b6068 [  307.247802] 7ea0: cf81bcc0 c02b9ce4 00000000 c02b861c 00000501 cfa2c868 39383 100 3932313a [  307.256042] 7ec0: cfa2cc00 c031ae40 c05b15a1 00000000 cf2b6000 cf2b6068 cfa2c c00 cfa4ce00 [  307.264251] 7ee0: 00000501 00000002 cfa2c800 c031dc70 00000001 00000000 00000 000 cfa2cc18 [  307.272491] 7f00: cf2b6000 c031f4b8 00000010 00000002 00000000 00000000 00000 3e8 c06309c8 [  307.280700] 7f20: 00000000 cf887f94 00000002 cfa2ca40 00000000 cf886000 00000 002 cfa3f020 [  307.288940] 7f40: cfa3f000 cfa2c800 cfa4ce40 cfa4ce44 cfa4ce48 cfa2c89c cfa4c e08 00000000 [  307.297149] 7f60: cfa3f020 cfa4ce9c cfa4ce4c 00000001 00000001 00000009 cfa2c c00 c0062044 [  307.305389] 7f80: cfa4ce01 cfa2c804 00000000 cf84a040 c0087c10 cf887f94 cf887 f94 00000501 [  307.313598] 7fa0: 05010001 cf887fd4 cf81ff64 cf887fd4 cf81ff64 00000000 c031e 924 00000000 [  307.321838] 7fc0: 00000000 00000000 00000000 c00877f0 00000000 00000000 cf887 fd8 cf887fd8 [  307.330047] 7fe0: 00000000 00000000 00000000 00000000 00000000 c003c9dc 02f7f f00 00fffe00 [  307.338287] [<c033df94>] (musb_interrupt+0x9f8/0xbb8) from [<c033e1b8>] (gene ric_interrupt+0x64/0x98) [  307.347595] [<c033e1b8>] (generic_interrupt+0x64/0x98) from [<c00a33a0>] (han dle_IRQ_event+0xac/0x1ec) [  307.356964] [<c00a33a0>] (handle_IRQ_event+0xac/0x1ec) from [<c00a5498>] (han dle_level_irq+0xbc/0x148) [  307.366333] [<c00a5498>] (handle_level_irq+0xbc/0x148) from [<c003b074>] (asm _do_IRQ+0x74/0x98) [  307.375091] [<c003b074>] (asm_do_IRQ+0x74/0x98) from [<c003bb44>] (__irq_svc+ 0x44/0xa8) [  307.383117] Exception stack(0xcf887c08 to 0xcf887c50) [  307.388214] 7c00:                   00000001 20000013 00000001 c063100c 00000 001 00000047 [  307.396423] 7c20: cf887c75 c067da23 0000001b 00000030 cf887c75 cf887c66 cf887 c28 cf887c50 [  307.404663] 7c40: c006d23c c006d904 20000013 ffffffff [  307.409759] [<c003bb44>] (__irq_svc+0x44/0xa8) from [<c006d904>] (vprintk+0x3 94/0x428) [  307.417724] [<c006d904>] (vprintk+0x394/0x428) from [<c04838b0>] (printk+0x18 /0x28) [  307.425445] [<c04838b0>] (printk+0x18/0x28) from [<c031e128>] (hub_probe+0xc0 /0x8bc) [  307.433227] [<c031e128>] (hub_probe+0xc0/0x8bc) from [<c03264a0>] (usb_probe_ interface+0x104/0x164) [  307.442352] [<c03264a0>] (usb_probe_interface+0x104/0x164) from [<c02baa78>] (driver_probe_device+0xc4/0x1a0) [  307.452331] [<c02baa78>] (driver_probe_device+0xc4/0x1a0) from [<c02b9eb0>] ( bus_for_each_drv+0x4c/0x8c) [  307.461853] [<c02b9eb0>] (bus_for_each_drv+0x4c/0x8c) from [<c02bacbc>] (devi ce_attach+0x68/0x8c) [  307.470794] [<c02bacbc>] (device_attach+0x68/0x8c) from [<c02b9ce4>] (bus_pro be_device+0x28/0x50) [  307.479705] [<c02b9ce4>] (bus_probe_device+0x28/0x50) from [<c02b861c>] (devi ce_add+0x368/0x508) [  307.488555] [<c02b861c>] (device_add+0x368/0x508) from [<c0324cbc>] (usb_set_ configuration+0x5e0/0x684) [  307.498016] [<c0324cbc>] (usb_set_configuration+0x5e0/0x684) from [<c032ce3c> ] (generic_probe+0x5c/0xa0) [  307.507537] [<c032ce3c>] (generic_probe+0x5c/0xa0) from [<c032501c>] (usb_pro be_device+0x2c/0x34) [  307.516479] [<c032501c>] (usb_probe_device+0x2c/0x34) from [<c02baa78>] (driv er_probe_device+0xc4/0x1a0) [  307.526000] [<c02baa78>] (driver_probe_device+0xc4/0x1a0) from [<c02b9eb0>] ( bus_for_each_drv+0x4c/0x8c) [  307.535552] [<c02b9eb0>] (bus_for_each_drv+0x4c/0x8c) from [<c02bacbc>] (devi ce_attach+0x68/0x8c) [  307.544464] [<c02bacbc>] (device_attach+0x68/0x8c) from [<c02b9ce4>] (bus_pro be_device+0x28/0x50) [  307.553405] [<c02b9ce4>] (bus_probe_device+0x28/0x50) from [<c02b861c>] (devi ce_add+0x368/0x508) [  307.562225] [<c02b861c>] (device_add+0x368/0x508) from [<c031dc70>] (usb_new_ device+0xe8/0x15c) [  307.570983] [<c031dc70>] (usb_new_device+0xe8/0x15c) from [<c031f4b8>] (hub_t hread+0xb94/0x10d4) [  307.579833] [<c031f4b8>] (hub_thread+0xb94/0x10d4) from [<c00877f0>] (kthread +0x78/0x80) [  307.587982] [<c00877f0>] (kthread+0x78/0x80) from [<c003c9dc>] (kernel_thread _exit+0x0/0x8) [  307.596374] Code: e3530003 13a02000 05963078 05933018 (05d33014) [  307.602661] ---[ end trace d3ff83a197f64efe ]---

[Gerald Coley]

Which USB port are you using?

 

Gerald

[jkri...@beagleboard.org]

This is a FAQ that we really should address better. There were changes in the Linux kernel that resulted in the musb interrupt not being plugged if you didn't load a gadget driver. Use a kernel with a gadget driver compiled in or load a gadget driver kernel module before connecting the usb port in device mode.


Short answer, pull down the kernel with 'gether' in the name from www.angstrom-distribution.org/demo/beagleboard

Apologies for the top post. My BlackBerry won't do it any other way.

Sent via BlackBerry from T-Mobile

---

From: Mark Lazarewicz <laza...@yahoo.com>

Sender: beagl...@googlegroups.com

Date: Fri, 22 Oct 2010 12:02:25 -0700 (PDT)

To: <beagl...@googlegroups.com>

ReplyTo: beagl...@googlegroups.com

Subject: [beagleboard] startup on demo image

[Mark Lazarewicz]

I plug the POWERED hub into the USB host on BB the HUB has keyboard,mouse and usb->ethernet plugged in I power the board with the mini USB OTG port if I power up with hub plugged into HOST port I kernel panick before the Matrix Application launcher appears on my DVI monitor --- On Fri, 10/22/10, Gerald Coley <ger...@beagleboard.org> wrote:

[Robert Nelson]

On Fri, Oct 22, 2010 at 3:32 PM, Mark Lazarewicz <laza...@yahoo.com> wrote:
>
> I plug the POWERED hub into the USB host on BB
> the HUB has keyboard,mouse and usb->ethernet plugged in
> I power the board with the mini USB OTG port

That's a known issue ^^^ use the 5volt dc connector for power on the beagle...

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

[Gerald Coley]

The current demo images gags an barfs on OTG being connected. Do as Robert suggests and use DC power.

 

Gerald

 

[Koen Kooi]

Quoting from http://www.angstrom-distribution.org/demo/beagleboard/:

"NOTE: Use external 5V supply and remove all USB connections from the Beagleboard when booting for the first time. Try USB later once you know it works."

and

"What If...

Some common problems and their fixes

• The kernel panics at random points during start-up.
Either use the 5V external power supply or use one of the multi-config-cpudile kernels. Sometimes the current via USB is not enough, but the cpuidle kernel should help with that. That comes at the cost of garbled characters on the serial console when it goes into a lower power mode.
• Even with the 5V supply the kernel panics during start-up.
Ensure that you copied the uImage file from the Angstrom filesystem into the boot partition. Compare md5 checksums to be sure.
• USB Ethernet doesn't work at startup.
The culprit is the composite USB gadget driver. In etc/default/usb-gadget set USB_MODE='networking' and run the module reconfiguration script (name?)."

Op 22 okt 2010, om 21:59 heeft jkri...@beagleboard.org het volgende geschreven:

> This is a FAQ that we really should address better. There were changes in the Linux kernel that resulted in the musb interrupt not being plugged if you didn't load a gadget driver. Use a kernel with a gadget driver compiled in or load a gadget driver kernel module before connecting the usb port in device mode.
>
>
> Short answer, pull down the kernel with 'gether' in the name from www.angstrom-distribution.org/demo/beagleboard
>
> Apologies for the top post. My BlackBerry won't do it any other way.
> Sent via BlackBerry from T-Mobile
>

[Jason Kridner]

On Fri, Oct 22, 2010 at 5:26 PM, Koen Kooi <ko...@beagleboard.org> wrote:
> Quoting from http://www.angstrom-distribution.org/demo/beagleboard/:
>
> "NOTE: Use external 5V supply and remove all USB connections from the Beagleboard when booting for the first time. Try USB later once you know it works."
>
> and
>
> "What If...
>
> Some common problems and their fixes
>
>        • The kernel panics at random points during start-up.
> Either use the 5V external power supply or use one of the multi-config-cpudile kernels. Sometimes the current via USB is not enough, but the cpuidle kernel should help with that. That comes at the cost of garbled characters on the serial console when it goes into a lower power mode.
>        • Even with the 5V supply the kernel panics during start-up.
> Ensure that you copied the uImage file from the Angstrom filesystem into the boot partition. Compare md5 checksums to be sure.
>        • USB Ethernet doesn't work at startup.
> The culprit is the composite USB gadget driver. In etc/default/usb-gadget set USB_MODE='networking' and run the module reconfiguration script (name?)."
>
>
> Op 22 okt 2010, om 21:59 heeft jkri...@beagleboard.org het volgende geschreven:
>
>> This is a FAQ that we really should address better. There were changes in the Linux kernel that resulted in the musb interrupt not being plugged if you didn't load a gadget driver. Use a kernel with a gadget driver compiled in or load a gadget driver kernel module before connecting the usb port in device mode.
>>
>>
>> Short answer, pull down the kernel with 'gether' in the name from www.angstrom-distribution.org/demo/beagleboard

I'm getting bugged about this enough that it is embarrassing. I'm
trying to get some folks to try out the instructions on
http://code.google.com/p/beagleboard/wiki/BeagleBoardDiagnosticsNext
with a C4 board to tell me how it works (where I expect it to fail
with the ramdisk). Once it is debugged, relative to u-boot at least,
on the C4 board, then I'll release a new diagnostics image with the
gether driver built-in. I want to minimize the churn.

[Jason Kridner]

There is a listing of images built on that day at:
http://beagleboard-validation.s3.amazonaws.com/deploy/201008201549/sd/list.html

This version of the image before it was configured is at:
http://beagleboard-validation.s3.amazonaws.com/deploy/201008201549/sd/beagleboard-demo-201008201549.img.gz

The image after it was configured is at:
http://beagleboard-validation.s3.amazonaws.com/deploy/201008201549/sd/beagleboard-demo-201008201549-configured.img.gz

>
> […]
>
>
> Thanks,
>
> Paul
>

[Jason Kridner]

On Wed, Oct 20, 2010 at 6:36 PM, Mittal, Amit <amit....@ti.com> wrote:
> Koen,
>
> Thanks for sharing this info, and data is also matching as I am also using Kingston SD card. I will try with higher speed SD card. But still 10-15 minutes are too high.
>
> Can you please guide how to make "preconfigured" image.

I simply performed a 'dd' after booting the image for the first time.