CB cant boot with or from SD, and Power problem

[cooco...@gmail.com]

I have three problems.

Board model dated: 2012-09-09, 1GB

Memory card: 16GB MicroSDHC from Sandisk (Ultra series)

The following problems (1 and 2) occurred with factory pre-installed Android and blank SD card:

1. Power --- 

    Both the OTG (mini USB) and the DC (5V usb power supply provided) turn the board on (red light is on). However, only the OTG power allow the board to boot to Android.

    Scenario 1: If I use only the OTG, then Android boots fine.

    Scenario 2: If I use only the 5V DC power cable provided, the red light go on, but screen doesn't show anything. Doesn't boot, not even flash screen.

    Scenario 3: If I use BOTH the OTG and and the DC cable, CB boot up fine. 

                     In Scenario 3, if I remove the DC during android operation, it works fine. However; if I remove the OTG, then display disappears and  bunch of color lines show up, the board still have power.

2. SD card prevent CB from Booting

     A. When the SD card is in the slot, CB doesn't boot up at all in any of the scenarios mention in keynote 1 above.

     B. After booting into Android, I insert the SD card and Android immediately recognize it and I can use it.

3. Ubuntu/Dabian distro will not boot from SD card

     A. After I boot into Android, I load my SD card

     B. I retrieve the BerryBoot per this instruction: http://www.cnx-software.com/2012/12/09/cubieboard-unboxing-and-quick-start-guide/

     C. Using the "Within Android" method, I installed Debian and Ubuntu. Both worked flawlessly. I can switch between distros fine if I don't power down the CB.

     D. If I power down the CB, then I can't boot from the SD card anymore. This is due to the problem mention above in key note 2.

Hypothesis:

1. Board error, when SD card is in, CB won't boot

2. Graphic switch to resolution TV can't understand

3. This is not my day...CB is just f**king with me

Doctor(s), those are my symptoms, please diagnose. 3AM now, got to go to sleep.

[Simos Xenitellis]

On Sat, Jan 26, 2013 at 11:58 AM, <cooco...@gmail.com> wrote:
> Scenario 2: If I use only the 5V DC power cable provided, the red light
> go on, but screen doesn't show anything. Doesn't boot, not even flash
> screen.

From which batch did your Cubieboard come from?
Is it Indiegogo?
According to http://www.indiegogo.com/cubieboard?c=activity
(check the item about the faulty DC to USB cable),
you may have just a cable issue.

Simos

[Bill Coron]

On Saturday, January 26, 2013 3:58:32 AM UTC-6, cooco...@gmail.com wrote:

2. SD card prevent CB from Booting

     A. When the SD card is in the slot, CB doesn't boot up at all in any of the scenarios mention in keynote 1 above.

     B. After booting into Android, I insert the SD card and Android immediately recognize it and I can use it.

3. Ubuntu/Dabian distro will not boot from SD card

     A. After I boot into Android, I load my SD card

     B. I retrieve the BerryBoot per this instruction: http://www.cnx-software.com/2012/12/09/cubieboard-unboxing-and-quick-start-guide/

     C. Using the "Within Android" method, I installed Debian and Ubuntu. Both worked flawlessly. I can switch between distros fine if I don't power down the CB.

     D. If I power down the CB, then I can't boot from the SD card anymore. This is due to the problem mention above in key note 2.

I am having similar issues here.

 No video with the SD card inserted. I assume it isn't booting. I'm also not getting the green LED near the CPU that lights when Android boots.

 I followed and tried both methods (from linux and within android) verifying the files both times. 

I am powering from the OTG port. Even tried using a USB cable with 2 USB-A for extra power.

My Berryboot.apk imaged my SD, but when it offered to reboot, I get no video, so I never got to choose a distro and get to step 3.C. above.

Not sure how the other user over came that part.

My board is an Indigogo board 2012-09-09

Any insight appreciated and I will update my progress here.

Thank You,

Bill

 

[Floris Bos]

On 01/26/2013 05:58 PM, Bill Coron wrote:

On Saturday, January 26, 2013 3:58:32 AM UTC-6, cooco...@gmail.com wrote:

3. Ubuntu/Dabian distro will not boot from SD card

     A. After I boot into Android, I load my SD card

     B. I retrieve the BerryBoot per this instruction: http://www.cnx-software.com/2012/12/09/cubieboard-unboxing-and-quick-start-guide/

     C. Using the "Within Android" method, I installed Debian and Ubuntu. Both worked flawlessly. I can switch between distros fine if I don't power down the CB.

     D. If I power down the CB, then I can't boot from the SD card anymore. This is due to the problem mention above in key note 2.

If you:

- start Android without SD card inserted.
- insert SD card
- tell Android to reboot.

Does it boot the SD card then?


==

I am having similar issues here.

 No video with the SD card inserted. I assume it isn't booting. I'm also not getting the green LED near the CPU that lights when Android boots.

 I followed and tried both methods (from linux and within android) verifying the files both times. 

I am powering from the OTG port. Even tried using a USB cable with 2 USB-A for extra power.

My Berryboot.apk imaged my SD, but when it offered to reboot, I get no video, so I never got to choose a distro and get to step 3.C. above.

Not sure how the other user over came that part.

What resolutions does your monitor support?
There is a known issue with displays that only support 1080i instead of 1080p.

Can you try opening uEnv.txt on the FAT partition of the SD card, and changing "disp.screen0_output_mode=EDID:1280x720p60" to "disp.screen0_output_mode=1280x720p60" ?


Yours sincerely,

Floris Bos

[cooco...@gmail.com]

This is a possibility, but I seem to be getting power from the DC connector. However Android refuses to boot up with DC power. The initial Android's flash screen show up, but hung up afterward.

[cooco...@gmail.com]

Floris, I don't know how to restart Android using soft restart. I can restart using the hard restart by holding down the power button for a few second. Once shutdown, I have to hold the power power button to turn it back on again.

Regarding modifying the uEnv.txt file. I've tried that, but no luck. My monitor can do both 720p/1080p.

Thanks.

[Floris Bos]

On 01/27/2013 12:45 AM, cooco...@gmail.com wrote:

Floris, I don't know how to restart Android using soft restart.

Try the old fashioned three finger salute on your keyboard: ctrl + alt + del



Also uploaded a berryboot-cubieboard-beta4 image to http://www.berryterminal.com/doku.php/berryboot_a10
But that only has a fix for dealing with interlaced displays (1080i).
Only available as dd image right now, still have to update the Android installer.


Yours sincerely,

Floris Bos

[cooco...@gmail.com]

After spending 15 minutes writing a response, the reply windows crashed on me. Google forum is starting to get annoying and it's really difficult to read and follow up. I'm seriously considering going to www.reddit.com/r/cubieboard.

Anyhow...Yours tried and true magical method worked!!! I booted into android without the SD card; then once in, insert the card. Soft restart using Ctrl+Alt+Del and I get into the distros selection box. Then I can load the other distros without any problem.

For some reason, Android made me completely forget about the keyboard.

I had to change the uEvn.txt back to original with "disp.screen0_output_mode=EDID:1280x720p60" or else the display get cutoff a little.

Thank you very much for this. I thought I was hopeless and my CB was going to retire.

Now, onto experiment number 2: DC Power

After booting with both DC and OTG power, I disconnected the OTG to see if it still remain on. Surprise!!! It does stay on....but only for 5 seconds, then the screen went blank. The board still have power though.

My suspicion is that the DC power is misswired somewhere on the board. Any guesses?

Side Note:

Ubuntu's Chromium doesn't play youtube videos directly youtube, but it plays the youtube's videos on other website like reddit with jittering. No sound!!

[George Ioakimedes]

I posted a question about the input power which was never answered. I know Tom is software but who is the hardware guy on this board? I'm also curious why we all have 2012-09 boards but the schematic posted is the older version.

In case you didn't see that post my question was how does the board work with just OTG power when according to the schematic that should not allow the 1.5V for DDR3 or the 3.3V for IO rails to come up. D2 should block voltage from getting to what's called DC-5V and that's what is the input to U5 and U7 which create these 2 power rails.

[John]

Does anyone else experienced this same situation with their DC power? Any electrical engineer out there with circuitry experience?

--

You received this message because you are subscribed to the Google Groups "Cubieboard" group.
To unsubscribe from this group, send email to cubieboard+...@googlegroups.com.
Visit this group at http://groups.google.com/group/cubieboard?hl=en.
 
 

[George Ioakimedes]

I don't believe the schematics accurately reflect the actual board. I haven't had time to probe out the board to see what is up. I don't understand why this question has not been answered either.

[autod...@gmail.com]

My CB is in Same situation. I received 2 hours ago.

My CB boot good and display all the menu and setting even internet site in OTG USB cable is connected in lab-top computer.

But Disconnected OTG Usb cable and when DC cable connected, all led operation same to OTG Usb cable connected but

Display is in Blank !!!  I seems that boot is not complete....

2013년 1월 28일 월요일 오후 3시 48분 36초 UTC+9, John 님의 말:

[autod...@gmail.com]

2013년 1월 28일 월요일 오후 5시 13분 33초 UTC+9, autod...@gmail.com 님의 말:

[cooco...@gmail.com]

Okay. I really want this board to succeed. Maybe we can fix the DC power problem in the future revision of the board. I can forgo powering the board by DC power and using OTG. There are plenty of mini USB cable I can use to power this board.

What I really want to focus on now is the software problem: I can not boot up the CubieBoard with SD card inserted. This is a serious flaw and I'm hoping that maybe something similar to a "bios update" can fix the problem. Maybe it has something to how the board sequence its boot up?

Right now, I don't have a 32bit system that I can flash Linux images easily. I'm afraid that if I wipe the original Android system, I don't have anything to work with. I really don't want a dead board on my hand. 

Has anyone have success/failure with installing different Linux distros to the system 4GB onboard memory using the mini usb cable? I'm willing to experiment to get Debian/Ubuntu onto the onboard memory using the mini USB cable, but I'm relatively new to the Linux environment and don't want to screw up. If you have success with this, can you share the direction or post a link to the directions. Maybe provide some tips along the way. Or if you are a Youtube guru, provide an instructional video. I've seen plenty of videos on putting the distros onto SD card, but that's not an option for me right now with the board being uncooperative.

Thanks.

[George Ioakimedes]

That is my goal too but I have been working on the SD Card first. There is a post by Pat Wood which details how to get Linux onto the NAND but I haven't had time to try it yet. You can check that out at https://www.miniand.com/forums/forums/development/topics/boot-ubuntu-lubuntu-from-internal-4g-flash

In order to get a quick SD Card up and running first try Berryboot or follow this thread:

http://www.cnx-software.com/2012/06/13/hardware-packs-for-allwinner-a10-devices-and-easier-method-to-create-a-bootable-ubuntu-12-04-sd-card/

I have used the a1x-media-create.sh script successfully many times.

[kingn...@gmail.com]

> Right now, I don't have a 32bit system that I can flash Linux images easily.

--If you grab a microSD card reader (~$10 or under from Target/Walmart), you can still use ' dd ' from Linux 64-bit (or even MacOS) to get the image onto the card...

[Patrick Wood]

You can also try this: http://guillaumeplayground.net/mele-a2000-ubuntu-12-10-armhf-base-with-nand-install-v1/

The PIMP_MY_MELE perl script should work on most linux distros.

[cooco...@gmail.com]

Update: Feb 16, 2013

Okay, I received the replacement 5V DC cable today. It look at little thicker and bigger than the original, so maybe they use a thicker copper cable. The original cable also power up the CB, but Android did not load.

The cable I received today surprisingly load up Android fine, which is great. The problem still remain, I can't boot up the CB with an SD card on board. There must be something wrong with the wiring on the board I received. 

Any update from anyone else having this SD card problem?

[bossesand]

As long as you can boot up the built in android, I do not belive there is any wiring problem.

There might be several problems:

- The image on the SD card is not bootable.

- The booting procedure recognizes the SD card, but does not understand that it is not to be used as boot media and does not go to the internal nand for boot.

I got hangings with a SD card when i had used the wrong program to write the image to the SD Card.

copying  info I wrote in another subject:

I wanted to upgrade my recently received cubieboard to a software that was of more use, i decided on  Android and went for:

http://dl.cubieboard.org/software/android/cubiebox_tvbox_rel2.img  

That when my trouble started. Information on what types if images that are available is not good for new users. 

I tried to write using the  https://launchpad.net/win32-image-writer/ recommended in http://www.cnx-software.com/2012/12/09/cubieboard-unboxing-and-quick-start-guide/  or so I belived :-)

That was before I understood that images can be either an image suitable for direct write to a sd card with dd or win32-image-writer, how are i to see the difference? 

The tvbox image is in the http://linux-sunxi.org/LiveSuit_images format! How was I to know?

Well any way I guesses that might be the case after a number of hours of googling.

So I decided to use the livesuit program, after spending 3+ hours in trying to get livesuit to recognize the Cubieboard in FEL mode i gave up and found a reference to PhoenixCard program.

I did not find out how to get correct drivers for the USB (android) device.

After finding PhoenixCardV306_2012_03_02 ( search in google to find download site ) I was able to create a sd-card that flashed the NAND.

I have not verified if PhoenixCard can create a runable sdcard.

Regards

Bosse

[Thiago]

I'm having this SD card isse as well....only the stock android works.

It doesnt matter if I flash the SD card with Berryboot or any linux distro, the boot sequence freezes (on berryboot it freezes while loading mali module), and even the "within android" method describe above does not work...

My board is from Indiegogo campaign...

[Thiago]

I've just made a trace from the terminal......maybe it can help.

(The boot sequence froze on berryboot, while loading the MALI module. This berryboot was installed from within android)

====================

U-Boot SPL 2013.01-rc1-ga07a224-dirty (Dec 06 2012 - 20:55:56)

Board: Cubieboard

DRAM: 1024MB

SUNXI SD/MMC: 0

U-Boot 2013.01-rc1-g4295940 (Dec 28 2012 - 01:50:29) Allwinner Technology

CPU:   SUNXI Family

Board: Cubieboard

I2C:   ready

DRAM:  1 GiB

MMC:   SUNXI SD/MMC: 0

*** Warning - bad CRC, using default environment

In:    serial

Out:   serial

Err:   serial

Net:   wemac

Hit any key to stop autoboot:  0 

reading uEnv.txt

424 bytes read in 14 ms (29.3 KiB/s)

Loaded environment from uEnv.txt

Running uenvcmd ...

reading script.bin

44592 bytes read in 6 ms (7.1 MiB/s)

reading kernel_a10_aufs.img

3598016 bytes read in 167 ms (20.5 MiB/s)

reading berryboot.img

8277009 bytes read in 376 ms (21 MiB/s)

## Booting kernel from Legacy Image at 48000000 ...

   Image Name:   Linux-3.4.24-a10-aufs+

   Created:      2013-01-26  23:28:24 UTC

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    3597952 Bytes = 3.4 MiB

   Load Address: 40008000

   Entry Point:  40008000

   Verifying Checksum ... OK

## Loading init Ramdisk from Legacy Image at 43100000 ...

   Image Name:   uInitrd

   Created:      2013-01-26  23:41:57 UTC

   Image Type:   ARM Linux RAMDisk Image (uncompressed)

   Data Size:    8276945 Bytes = 7.9 MiB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0

[    0.000000] Initializing cgroup subsys cpuset

[    0.000000] Linux version 3.4.24-a10-aufs+ (max@lynx) (gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1) ) #1 PREEMPT Sun Jan 27 00:28:21 CET 2013

[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d

[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

[    0.000000] Machine: sun4i

[    0.000000] Memory cut off:

[    0.000000] MALI : 0x5c000000 - 0x5fffffff  (  64 MB)

[    0.000000] Ignoring unrecognised tag 0x00000000

[    0.000000] Memory Reserved:

[    0.000000] SYS  : 0x43000000 - 0x4300ffff  (  64 kB)

[    0.000000] VE   : 0x44000000 - 0x48ffffff  (  80 MB)

[    0.000000] G2D  : 0x58000000 - 0x58ffffff  (  16 MB)

[    0.000000] LCD  : 0x5a000000 - 0x5bffffff  (  32 MB)

[    0.000000] Memory policy: ECC disabled, Data cache writeback

[    0.000000] chip-id: A10 (AW1623 revision C)

[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 243712

[    0.000000] Kernel command line: console=ttyS0,115200 console=tty0 disp.screen0_output_mode=EDID:1280x720p60 hdmi.audio=EDID:0 mmc0_led=1 bootmenutimeout=10

[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)

[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)

[    0.000000] Memory: 448MB 512MB = 960MB total

[    0.000000] Memory: 826620k/826620k available, 156420k reserved, 270336K highmem

[    0.000000] Virtual kernel memory layout:

[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)

[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)

[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)

[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)

[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)

[    0.000000]       .text : 0xc0008000 - 0xc0658000   (6464 kB)

[    0.000000]       .init : 0xc0658000 - 0xc0684000   ( 176 kB)

[    0.000000]       .data : 0xc0684000 - 0xc06cd600   ( 294 kB)

[    0.000000]        .bss : 0xc06cd624 - 0xc0877b58   (1706 kB)

[    0.000000] SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

[    0.000000] NR_IRQS:96

[    0.000000] timer0: Periodic Mode

[    0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms

[    0.000000] Console: colour dummy device 80x30

[    0.000000] console [tty0] enabled

[    0.000000] Calibrating delay loop... 1001.88 BogoMIPS (lpj=5009408)

[    0.040000] pid_max: default: 32768 minimum: 301

[    0.040000] Mount-cache hash table entries: 512

[    0.040000] Initializing cgroup subsys cpuacct

[    0.040000] Initializing cgroup subsys devices

[    0.040000] Initializing cgroup subsys freezer

[    0.040000] Initializing cgroup subsys blkio

[    0.040000] CPU: Testing write buffer coherency: ok

[    0.040000] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available

[    0.040000] Setting up static identity map for 0x40498d10 - 0x40498d68

[    0.040000] devtmpfs: initialized

[    0.040000] dummy: 

[    0.040000] NET: Registered protocol family 16

[    0.040000] hw-breakpoint: debug architecture 0x4 unsupported.

[    0.040000] SOFTWINNER DMA Driver, (c) 2003-2004,2006 Simtec Electronics

[    0.040000] Initialize DMAC OK

[    0.040000] bio: create slab <bio-0> at 0

[    0.040000] SCSI subsystem initialized

[    0.040000] usbcore: registered new interface driver usbfs

[    0.040000] usbcore: registered new interface driver hub

[    0.040000] usbcore: registered new device driver usb

[    0.040000] Linux video capture interface: v2.00

[    0.040000] Advanced Linux Sound Architecture Driver Version 1.0.25.

[    0.040000] Bluetooth: Core ver 2.16

[    0.040000] NET: Registered protocol family 31

[    0.040000] Bluetooth: HCI device and connection manager initialized

[    0.040000] Bluetooth: HCI socket layer initialized

[    0.040000] Bluetooth: L2CAP socket layer initialized

[    0.040000] Bluetooth: SCO socket layer initialized

[    0.040000] cfg80211: Calling CRDA to update world regulatory domain

[    0.040000] Init eGon pin module V2.0

[    0.040000] Switching to clocksource aw 64bits couter

[    0.040000] FS-Cache: Loaded

[    0.040000] CacheFiles: Loaded

[    0.050000] [usb_manager]: CONFIG_USB_SW_SUN4I_USB0_HOST_ONLY

[    0.050000] [sw_hcd0]: usb host driver initialize........

[    0.050000] NET: Registered protocol family 2

[    0.050000] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)

[    0.050000] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)

[    0.050000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)

[    0.050000] TCP: Hash tables configured (established 131072 bind 65536)

[    0.050000] TCP: reno registered

[    0.050000] UDP hash table entries: 512 (order: 1, 8192 bytes)

[    0.050000] UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)

[    0.050000] NET: Registered protocol family 1

[    0.050000] Trying to unpack rootfs image as initramfs...

[    0.560000] Freeing initrd memory: 8080K

[    0.560000] [pm]aw_pm_init!

[    0.560000] audit: initializing netlink socket (disabled)

[    0.560000] type=2000 audit(0.559:1): initialized

[    0.560000] highmem bounce pool size: 64 pages

[    0.560000] VFS: Disk quotas dquot_6.5.2

[    0.560000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

[    0.570000] squashfs: version 4.0 (2009/01/31) Phillip Lougher

[    0.570000] fuse init (API version 7.18)

[    0.570000] aufs 3.4-20121210

[    0.570000] msgmni has been set to 1102

[    0.570000] alg: No test for stdrng (krng)

[    0.570000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)

[    0.570000] io scheduler noop registered

[    0.570000] io scheduler deadline registered

[    0.570000] io scheduler cfq registered (default)

[    0.570000] sunxi disp driver loaded (/dev/disp api 1.0)

[    0.570000] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled

[    0.570000] [uart]: used uart info.: 0x05

[    0.570000] [uart]: serial probe 0 irq 1 mapbase 0x01c28000

[    0.590000] sunxi-uart.0: ttyS0 at MMIO 0x1c28000 (irq = 1) is a U6_16550A

[    1.150000] console [ttyS0] enabled

[    1.160000] [uart]: serial probe 2 irq 3 mapbase 0x01c28800

[    1.180000] sunxi-uart.2: ttyS1 at MMIO 0x1c28800 (irq = 3) is a U6_16550A

[    1.190000] G2D: g2dmem: g2d_start=58000000, g2d_size=1000000

[    1.200000] G2D: head:d8000000,tail:d9000000

[    1.200000] G2D: Module initialized.major:251

[    1.200000] brd: module loaded

[    1.210000] loop: module loaded

[    1.210000] [NAND]nand driver, init.

[    1.220000] cmu_clk is 480 

[    1.220000] nand clk init end 

[    1.220000] offset 0xc:  0x26140 

[    1.230000] offset 0x14:  0x8200000b 

[    1.230000] [NAND] nand gpio_request

[    1.230000] [NAND] nand driver version: 0x2 0x9 

[    1.240000] nand interrupte register ok

[    1.240000] ret of NFC_ChangMode is 0 

[    1.240000] dma_hdle  is 0 

[    1.250000] dma_hdle  is 10000008 

[    1.250000] cmu_clk is 480 

[    1.250000] nand clk init end 

[    1.260000] offset 0xc:  0x26140 

[    1.260000] offset 0x14:  0x82000007 

[    1.320000] The 0 disk name = DEVICE, class name = NAND, disk start = 0, disk size = 7979008

[    1.330000] The 1 disk name = bootloader, class name = DISK, disk size = 32768

[    1.330000] The 2 disk name = env, class name = DISK, disk size = 32768

[    1.340000] The 3 disk name = boot, class name = DISK, disk size = 65536

[    1.350000] The 4 disk name = misc, class name = DISK, disk size = 32768

[    1.350000] The 5 disk name = recovery, class name = DISK, disk size = 65536

[    1.360000] The 6 disk name = private, class name = DISK, disk size = 32768

[    1.370000] The 7 disk name = sysrecovery, class name = DISK, disk size = 655360

[    1.380000] The 8 disk name = UDISK, class name = DISK, disk size = 4816896

[    1.380000] The 8 disk size = 5062656

[    1.390000] part total count = 9

[    1.390000]  nand: unknown partition table

[    1.400000]  nanda:

[    1.400000]  nandb: unknown partition table

[    1.410000]  nandc: unknown partition table

[    1.410000]  nandd: unknown partition table

[    1.420000]  nande: unknown partition table

[    1.420000]  nandf:

[    1.430000]  nandg: unknown partition table

[    1.430000]  nandh:

[    1.440000] benn: nand probe enter

[    1.440000] [NAND]nand driver, ok.

[    1.440000] sw_ahci sw_ahci.0: controller can't do PMP, turning off CAP_PMP

[    1.450000] sw_ahci sw_ahci.0: forcing PORTS_IMPL to 0x1

[    1.460000] sw_ahci sw_ahci.0: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode

[    1.460000] sw_ahci sw_ahci.0: flags: ncq sntf pm led clo only pio slum part ccc 

[    1.470000] scsi0 : sw_ahci_platform

[    1.480000] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 56

[    1.480000] wemac Ethernet Driver, V1.01 in file:drivers/net/ethernet/sun4i/sun4i_wemac.c

[    1.490000] [EMAC] ahb clk enable

[    1.500000] [EMAC] ahb gate clk: 0x2026140

[    1.530000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

[    1.530000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver

[    1.540000] [sw-ehci1]: open clock

[    1.560000] [sw-ehci1]: Set USB Power ON

[    1.570000] sw-ehci sw-ehci.1: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver

[    1.570000] sw-ehci sw-ehci.1: new USB bus registered, assigned bus number 1

[    1.580000] sw-ehci sw-ehci.1: irq 39, io mem 0xf1c14000

[    1.610000] sw-ehci sw-ehci.1: USB 0.0 started, EHCI 1.00

[    1.610000] hub 1-0:1.0: USB hub found

[    1.610000] hub 1-0:1.0: 1 port detected

[    1.620000] [sw-ohci1]: open clock

[    1.640000] sw-ohci sw-ohci.1: SW USB2.0 'Open' Host Controller (OHCI) Driver

[    1.650000] sw-ohci sw-ohci.1: new USB bus registered, assigned bus number 2

[    1.660000] sw-ohci sw-ohci.1: irq 64, io mem 0xf1c14400

[    1.660000] ehci_irq: port change detect

[    1.730000] hub 2-0:1.0: USB hub found

[    1.730000] hub 2-0:1.0: 1 port detected

[    1.740000] [sw-ehci2]: open clock

[    1.760000] [sw-ehci2]: Set USB Power ON

[    1.760000] sw-ehci sw-ehci.2: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver

[    1.770000] sw-ehci sw-ehci.2: new USB bus registered, assigned bus number 3

[    1.780000] sw-ehci sw-ehci.2: irq 40, io mem 0xf1c1c000

[    1.800000] sw-ehci sw-ehci.2: USB 0.0 started, EHCI 1.00

[    1.800000] ehci_irq: port change detect

[    1.800000] hub 3-0:1.0: USB hub found

[    1.810000] hub 3-0:1.0: 1 port detected

[    1.810000] [sw-ohci2]: open clock

[    1.820000] ehci_irq: port change detect

[    1.830000] ata1: SATA link down (SStatus 0 SControl 300)

[    1.850000] sw-ohci sw-ohci.2: SW USB2.0 'Open' Host Controller (OHCI) Driver

[    1.850000] sw-ohci sw-ohci.2: new USB bus registered, assigned bus number 4

[    1.860000] sw-ohci sw-ohci.2: irq 65, io mem 0xf1c1c400

[    1.880000] The port change to OHCI now!

[    1.930000] hub 4-0:1.0: USB hub found

[    1.930000] hub 4-0:1.0: 1 port detected

[    1.940000] usbcore: registered new interface driver cdc_acm

[    1.940000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

[    1.950000] usbcore: registered new interface driver usblp

[    1.960000] Initializing USB Mass Storage driver...

[    1.960000] usbcore: registered new interface driver usb-storage

[    1.970000] USB Mass Storage support registered.

[    1.970000] usbcore: registered new interface driver ums-alauda

[    1.980000] usbcore: registered new interface driver ums-cypress

[    1.980000] usbcore: registered new interface driver ums-datafab

[    1.990000] usbcore: registered new interface driver ums_eneub6250

[    2.000000] usbcore: registered new interface driver ums-freecom

[    2.000000] usbcore: registered new interface driver ums-isd200

[    2.010000] usbcore: registered new interface driver ums-jumpshot

[    2.010000] usbcore: registered new interface driver ums-karma

[    2.020000] usbcore: registered new interface driver ums-onetouch

[    2.030000] usbcore: registered new interface driver ums-realtek

[    2.030000] usbcore: registered new interface driver ums-sddr09

[    2.040000] usbcore: registered new interface driver ums-sddr55

[    2.040000] usbcore: registered new interface driver ums-usbat

[    2.050000] mousedev: PS/2 mouse device common for all mice

[    2.060000] sunxi RTC version 0.1 

[    2.060000] sunxi-rtc sunxi-rtc: sunxi_rtc_probe tmp_data = 380248073

[    2.070000] [RTC] ERR: Set LOSC to external failed!!!

[    2.070000] [RTC] WARNING: Rtc time will be wrong!!

[    2.080000] usb 2-1: new low-speed USB device number 2 using sw-ohci

[    2.080000] sunxi-rtc sunxi-rtc: rtc core: registered rtc as rtc0

[    2.090000] i2c /dev entries driver

[    2.090000] !!! base_Addr = 0xf1c2ac00 

[    2.100000] config i2c gpio with gpio_config api 

[    2.100000] twi0, apb clock = 24000000 

[    2.110000] axp_mfd 0-0034: AXP (CHIP ID: 0x21) detected

[    2.110000] I2C: i2c-0: AW16XX I2C adapter

[    2.120000] **********start************

[    2.120000] 0x40 

[    2.120000] 0xf8 

[    2.120000] 0x28 

[    2.130000] 0x0 

[    2.130000] 0x0 

[    2.130000] **********end************

[    2.130000] !!! base_Addr = 0xf1c2b000 

[    2.140000] twi1, apb clock = 24000000 

[    2.140000] I2C: i2c-1: AW16XX I2C adapter

[    2.150000] **********start************

[    2.150000] 0x40 

[    2.150000] 0xf8 

[    2.150000] 0x58 

[    2.160000] 0x0 

[    2.160000] 0x0 

[    2.160000] **********end************

[    2.160000] !!! base_Addr = 0xf1c2b400 

[    2.170000] twi2, apb clock = 24000000 

[    2.170000] I2C: i2c-2: AW16XX I2C adapter

[    2.170000] **********start************

[    2.180000] 0x40 

[    2.180000] 0xf8 

[    2.180000] 0x58 

[    2.180000] 0x0 

[    2.190000] 0x0 

[    2.190000] **********end************

[    2.190000] lirc_dev: IR Remote Control driver registered, major 250 

[    2.200000] IR NEC protocol handler initialized

[    2.200000] IR RC5(x) protocol handler initialized

[    2.210000] IR RC6 protocol handler initialized

[    2.210000] IR JVC protocol handler initialized

[    2.220000] IR Sony protocol handler initialized

[    2.220000] IR RC5 (streamzap) protocol handler initialized

[    2.230000] IR SANYO protocol handler initialized

[    2.230000] IR MCE Keyboard/mouse protocol handler initialized

[    2.240000] IR LIRC bridge handler initialized

[    2.240000] [cedar dev]: install start!!!

[    2.250000] [cedar dev]: install end!!!

[    2.250000] [ace_drv] start!!!

[    2.250000] [ace_drv] init end!!!

[    2.260000] [pa_drv] start!!!

[    2.260000] [pa_drv] init end!!!

[    2.260000] axp20_ldo1: 1300 mV 

[    2.270000] axp20_ldo2: 1800 <--> 3300 mV at 3000 mV 

[    2.270000] axp20_ldo3: 700 <--> 3500 mV at 2800 mV 

[    2.280000] axp20_ldo4: 1250 <--> 3300 mV at 2800 mV 

[    2.290000] axp20_buck2: 700 <--> 2275 mV at 1400 mV 

[    2.290000] axp20_buck3: 700 <--> 3500 mV at 1250 mV 

[    2.300000] axp20_ldoio0: 1800 <--> 3300 mV at 2800 mV 

[    2.300000] ehci_irq: port change detect

[    2.310000] input: axp20-supplyer as /devices/platform/sun4i-i2c.0/i2c-0/0-0034/axp20-supplyer.28/input/input0

[    2.330000] Bluetooth: HCI UART driver ver 2.2

[    2.340000] Bluetooth: HCI H4 protocol initialized

[    2.340000] Bluetooth: HCI BCSP protocol initialized

[    2.350000] Bluetooth: HCILL protocol initialized

[    2.350000] cpuidle: using governor ladder

[    2.360000] cpuidle: using governor menu

[    2.360000] [mmc_pm]: no sdio card used in configuration

[    2.370000] The port change to OHCI now!

[    2.370000] [mmc]: sunximmc_init

[    2.370000] [mmc]: sunxi mmc controller using config : 0x9

[    2.380000] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0

[    2.380000] [mmc]: mmc 0 power off !!

[    2.390000] [mmc]: mmc0 Probe: base:0xf1c0f000 irq:32 dma:0 pdes:0xef3f8000, ret 0.

[    2.400000] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3

[    2.400000] [mmc]: mmc 3 power off !!

[    2.410000] [mmc]: mmc3 Probe: base:0xf1c12000 irq:35 dma:0 pdes:0xef3fc000, ret 0.

[    2.420000] sunxi_leds driver init

[    2.420000] sunxi leds can't find script data '[leds_para]' 'leds_used'

[    2.430000] input: GASIA USB KB V11 as /devices/platform/sw-ohci.1/usb2/2-1/2-1:1.0/input/input1

[    2.440000] generic-usb 0003:0E8F:0022.0001: input: USB HID v1.10 Keyboard [GASIA USB KB V11] on usb-sw-ohci-1/input0

[    2.460000] input: GASIA USB KB V11 as /devices/platform/sw-ohci.1/usb2/2-1/2-1:1.1/input/input2

[    2.470000] generic-usb 0003:0E8F:0022.0002: input: USB HID v1.10 Device [GASIA USB KB V11] on usb-sw-ohci-1/input1

[    2.480000] usbcore: registered new interface driver usbhid

[    2.490000] usbhid: USB HID core driver

[    2.490000] logger: created 256K log 'log_main'

[    2.490000] logger: created 256K log 'log_events'

[    2.500000] logger: created 256K log 'log_radio'

[    2.500000] logger: created 256K log 'log_system'

[    2.510000] enter sun4i Audio codec!!!

[    2.510000] sun4i audio support initialized

[    2.520000] sun4i Audio codec successfully loaded..

[    2.520000] soc-audio soc-audio.0: ASoC machine sun4i-sndhdmi should use snd_soc_register_card()

[    2.530000] asoc: sndhdmi <-> sun4i-hdmiaudio.0 mapping ok

[    2.540000] IPv4 over IPv4 tunneling driver

[    2.540000] TCP: cubic registered

[    2.550000] Initializing XFRM netlink socket

[    2.550000] NET: Registered protocol family 17

[    2.560000] NET: Registered protocol family 15

[    2.560000] Bluetooth: RFCOMM TTY layer initialized

[    2.560000] Bluetooth: RFCOMM socket layer initialized

[    2.570000] Bluetooth: RFCOMM ver 1.11

[    2.570000] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

[    2.580000] Bluetooth: BNEP filters: protocol multicast

[    2.580000] 8021q: 802.1Q VLAN Support v1.8

[    2.590000] [mmc_pm]: No sdio card, please check your config !!

[    2.590000] Registering the dns_resolver key type

[    2.600000] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3

[    2.610000] Registering SWP/SWPB emulation handler

[    2.610000] registered taskstats version 1

[    2.670000] usb 4-1: new low-speed USB device number 2 using sw-ohci

[    2.710000] ParseEDID

[    2.710000] DDC_Init

[    2.720000] EDID ready

[    2.720000] DDC_Read

[    2.820000] Sink : EDID bank 0:

[    2.820000]  0   1   2   3   4   5   6   [    3.040000] Sink : EDID bank 1:

[    3.040000]  0   1   2   3   4   5   6   7   8   9   A   B   C   D   E   F

[    3.050000]  ===============================================================================================

[    3.060000]  02  03  21  f1  4e  90  04  03  01  14  12  05  1f  10  13  00

[    3.070000]  00  00  00  23  09  07  07  83  01  00  00  65  03  0c  00  10

[    3.080000]  00  02  3a  80  18  71  38  2d  40  58  2c  45  00  fe  22  11

[    3.080000]  00  00  1e  01  1d  80  18  71  1c  16  20  58  2c  25  00  fe

[    3.090000]  22  11  00  00  9e  01  1d  00  72  51  d0  1e  20  6e  28  55

[    3.100000]  00  fe  22  11  00  00  1e  8c  0a  d0  8a  20  e0  2d  10  10

[    3.100000]  3e  96  00  fe  22  11  00  00  18  00  00  00  00  00  00  00

[    3.110000]  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  de

[    3.120000]  ===============================================================================================

[    3.130000] Unimplemented SVD code 31

[    3.130000] Unimplemented SVD code 16

[    3.130000] Reserved SVD code 0

[    3.140000] Reserved SVD code 0

[    3.140000] Reserved SVD code 0

[    3.140000] Reserved SVD code 0

[    3.150000] Parse_VideoData_Block: VIC 16 (native) support

[    3.150000] Parse_VideoData_Block: VIC 4 support

[    3.160000] Parse_VideoData_Block: VIC 3 support

[    3.160000] Parse_VideoData_Block: VIC 1 support

[    3.170000] Parse_VideoData_Block: VIC 20 support

[    3.170000] Parse_VideoData_Block: VIC 18 support

[    3.180000] Parse_VideoData_Block: VIC 5 support

[    3.180000] Parse_VideoData_Block: VIC 31 support

[    3.190000] Parse_VideoData_Block: VIC 16 support

[    3.190000] Parse_VideoData_Block: VIC 19 support

[    3.190000] Parse_VideoData_Block: VIC 0 support

[    3.200000] Parse_VideoData_Block: VIC 0 support

[    3.200000] Parse_VideoData_Block: VIC 0 support

[    3.210000] Parse_VideoData_Block: VIC 0 support

[    3.210000] Parse_AudioData_Block: max channel=2

[    3.220000] Parse_AudioData_Block: SampleRate code=7

[    3.220000] Parse_AudioData_Block: WordLen code=7

[    3.230000] Find HDMI Vendor Specific DataBlock

[    3.230000] PCLK=148500000 X 1920 2008 2052 2200 Y 1080 1084 1089 1125 fr 60 PP

[    3.240000] PCLK=74250000 X 1920 2008 2052 2200 Y 540 542 547 562 fr 60 PP

[    3.250000] PCLK=74250000 X 1280 1390 1430 1650 Y 720 725 730 750 fr 60 PP

[    3.250000] PCLK=27000000 X 720 736 798 858 Y 480 489 495 525 fr 59 NN

[    3.260000] waited 0 ms for EDID info

[    3.260000] disp clks: lcd 148500000 pre_scale 1 hdmi 148500000 pll 297000000 2x 0

[    3.390000] [mmc]: mmc 0 detect change, present 1

[    3.690000] [mmc]: mmc 0 power on !!

[    3.730000] [mmc]: sdxc_request_done(L1113): smc 0 err, cmd 52,  RTO !!

[    3.730000] [mmc]: sdxc_request_done(L1113): smc 0 err, cmd 52,  RTO !!

[    3.740000] [mmc]: sdxc_request_done(L1113): smc 0 err, cmd 5,  RTO !!

[    3.750000] [mmc]: sdxc_request_done(L1113): smc 0 err, cmd 5,  RTO !!

[    3.760000] [mmc]: sdxc_request_done(L1113): smc 0 err, cmd 5,  RTO !!

[    3.770000] [mmc]: sdxc_request_done(L1113): smc 0 err, cmd 5,  RTO !!

[    3.820000] mmc0: new high speed SDHC card at address aaaa

[    3.840000] mmcblk0: mmc0:aaaa SU08G 7.40 GiB 

[    3.840000]  mmcblk0: p1

[    4.730000] Console: switching to colour frame buffer device 240x67

[    4.760000] axp20_buck3: incomplete constraints, leaving on

[    4.770000] axp20_buck2: incomplete constraints, leaving on

[    4.770000] axp20_ldo4: incomplete constraints, leaving on

[    4.780000] axp20_ldo3: incomplete constraints, leaving on

[    4.780000] axp20_ldo2: incomplete constraints, leaving on

[    4.790000] axp20_ldo1: incomplete constraints, leaving on

[    4.790000] sunxi-rtc sunxi-rtc: hctosys: unable to read the hardware clock

[    4.800000] ALSA device list:

[    4.810000]   #0: sun4i-sndhdmi

[    4.810000]   #1: sun4i-CODEC  Audio Codec

[    4.810000] Freeing init memory: 176K

====================================

[vince bardsley]

I have a similar problem.  My CB boots to Android OK, but will not boot when a SD is inserted. Red light comes on, green light blinks very briefly, then nothing.  QC seems to a problem!

--

You received this message because you are subscribed to the Google Groups "Cubieboard" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cubieboard+...@googlegroups.com.

Visit this group at http://groups.google.com/group/cubieboard?hl=en.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[George Ioakimedes]

I had/have similar problems with the SD slot on my board. Try pushing down on the metal SD card cage a little and see if the boot process changes at all. I noticed that once I could get the board to boot from the SD card it would work again even after a reboot as long as I didn't take the SD card out of the lot.

Can you boot to Android and then put the SD Card in and see if it can be read?

[Thiago Palmieri]

Well, in my case, the SD card is recognized by the stock android, in fact, as I've said, it even installs berryboot from within android.

It does not seem to be a "bad connection" problem.

I don't know much about SD cards, but maybe CB is not compatible with some SD brands?? I'm using SanDisk Cards....

2013/2/18 George Ioakimedes <georg...@gmail.com>

--
'A imaginação é muito mais importante que o conhecimento.' (Albert Einstein)

When it comes to encryption, there are two important security rules:
1. Don't tell everything you know.

[George Ioakimedes]

It is one of the new Ultra type cards? I had one that wasn't recognized. These embedded boards seem to work better with "older" cards. Even the Raspberry Pi forums recommend using Class 4/6 cards instead of Class 10. I did a project using the Raspberry Pi and purchased 20 Patriot Class 10 8GB cards. 11/20 did NOT boot but they were perfectly fine on any other hardware I put them in or formatted them on. I wish I would have kept one for reference so I could have debugged what was going on but I didn't.

If Android sees the card then I would definitely try a different card and see what happens. I've got so many cards laying around now I can't keep them straight!

[Thiago Palmieri]

The Sandiscs I'm using are Class 4, labeled as Micro SDHC.

2013/2/18 George Ioakimedes <georg...@gmail.com>

[plh]

It looks the same problem addressed at https://github.com/linux-sunxi/linux-sunxi/issues/113.

You can try not load mali, mali_drm module at boot time.  

Hope it would be fixed soon.

My CB works all right at first, someday it somehow cannot boot with the same OS image. But with mali mali_drm removed, it can enter X sesiion all right.

在 2013年2月18日星期一UTC+8上午8时03分54秒，Thiago写道：

[cooco...@gmail.com]

EUREEEKAAAA!!! HOOORAYY for George Loakimedes!!!  

You have hit the nail right on the head. After reading your post, I remember I have another SD card in the car DVR. It is NOT a sand disk brand. It's 16gb, class 10 that I bought over the internet over a year ago. I put it in and Android booted up and recognizes it. NO MORE freezing.

I have not loaded another Linux distros onto it yet to test to see if it will boot up to it. I will update later/tomorrow.

Bottom line: SanDisk Ultra does not work with Cubieboard (At least mine does not.) Can someone else verify??

[Alessandro Recchi]

My sd card works (SanDisk Ultra 16GB)

[Patrick Wood]

*** Warning - bad CRC, using default environment

This is a red herring.  The message is coming from u-boot when it fails to load the environment from a fixed position in the boot block.  The mmc is obviously working, as the kernel is loaded from the first partition:

reading kernel_a10_aufs.img
3598016 bytes read in 167 ms (20.5 MiB/s)
reading berryboot.img
8277009 bytes read in 376 ms (21 MiB/s)

Also, the MMC is initialized by the kernel here:

[    3.820000] mmc0: new high speed SDHC card at address aaaa
[    3.840000] mmcblk0: mmc0:aaaa SU08G 7.40 GiB
[    3.840000]  mmcblk0: p1

However, only one partition is found.  Since I don't have any experience with berryboot, is this correct?

I get a message that my root file system on the MMC was mounted right before 

<6>Freeing init memory: 184K

and you don't. I can't say if this is correct behavior for berryboot or not, but unless you're missing a partition on your SD card, it's probably not your problem.

[Thiago Palmieri]

Hello,

When I use a SD card with a Headless kernel, everything goes well (MALI module is not loaded). Every kernel I use that is not headless (including berryboot) the system halts when handling MALI module.

Does that mean that I have a faulty board, since MALI handles GPU ? Android on the other hand boots well.....

I'm using HDMI connection to a 24'' LG monitor (which is capable of handling 1920x1080) and I have my desktop connected via DVI to the same monitor.

2013/2/21 Patrick Wood <patric...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "Cubieboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cubieboard+...@googlegroups.com.
Visit this group at http://groups.google.com/group/cubieboard?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Roman Mamedov]

On Thu, 21 Feb 2013 09:25:31 -0300
Thiago Palmieri <thiago....@gmail.com> wrote:

> Hello,
>
> When I use a SD card with a Headless kernel, everything goes well (MALI
> module is not loaded). Every kernel I use that is not headless (including
> berryboot) the system halts when handling MALI module.
>
> Does that mean that I have a faulty board, since MALI handles GPU ? Android
> on the other hand boots well.....

modprobe lcd
modprobe hdmi
modprobe disp
modprobe mali
modprobe fb
modprobe ump
modprobe mali_drm

^ afaik you need to load ALL of these and in THIS exact order.

Do not rely on /etc/modules or the like. Try from a shell script. Start with
Xorg and desktop manager disabled, then load the modules with commands as
above, if it didn't lock-up, then start Xorg.

--
With respect,
Roman

[Floris Bos]

On 02/21/2013 04:07 AM, Patrick Wood wrote:

[    3.820000] mmc0: new high speed SDHC card at address aaaa

[    3.840000] mmcblk0: mmc0:aaaa SU08G 7.40 GiB
[    3.840000]  mmcblk0: p1

However, only one partition is found.  Since I don't have any experience with berryboot, is this correct?

That is correct.
The Berryboot program is very small, lives on a FAT partition, and gets loaded into memory by u-boot as initramfs image.
On first use, it will guide the user through an installation procedure that will repartition the drive and creates a second partition for the files of the operating system.

But it will never get there if it already hangs while loading the modules shortly after boot.
Not sure why that happens for the topic starter, it is not something I have been able to reproduce.

That said you only need the mali module if you want 3D graphics, it is not necessary for unaccelerated framebuffer stuff.
I might change it so that it simply will not load the module by default in a future version.


Yours sincerely,

Floris Bos

[cooco...@gmail.com]

UPDATE: 

After successfully booting up with a blank SD card in the slot. I've installed Ubuntu Desktop onto the SD card. However, after successfully installing the distros. I can not boot up from the SD card. It just doesn't load.

I can can boot up into android and then Ctr+Alt+Delete and go to Ubuntu, but I can not boot straight into Ubuntu from cold power on.

I will now abandon the SD card card route, but before wiping out Android, I will experiment with booting up from the sata drive instead. Being new to linux, can someone tell me how to change the boot sequence from SD>NAND to HDD>NAND?

Thanks.

[George Ioakimedes]

have you tried connecting the serial console to check for messages? this is the best way to see the boot process and determine what the problem is.

--
You received this message because you are subscribed to a topic in the Google Groups "Cubieboard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cubieboard/RbwiUQEv8kI/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to cubieboard+...@googlegroups.com.

[Mike Glyer]

Hi All,

I'm having the same issues as above.  I have Cubiuntu loaded on my SD card, but it won't boot.  I am using an 8GB Transcend Class 10 SD Card. I can start up from the NAND card with a linux image I flashed on it.  When I insert the SD card in after booting up, I can mount both partitions of the SD card.  

So Issues:

1.  I don't know where the serial port is on the cubietruck, so I have no idea where my SD card freezes, since I get nothing plugged into my monitor from HDMI.

2. I don't know how I might start the image on the SD card, once I have it plugged in after booting to NAND.

3. It seems like the SD card issue is not reliably a problem for class 10 cards, based on the above dialog.

4.  Does anyone have a tutorial on removing the MALI drivers, since I don't even plan to run X on this Cubie.

Thanks,

Mike

[Chen GUO]

all linux users should suffering, if you just updated your system to latest. i guess it light be the u-boot problem, 201307-4

You received this message because you are subscribed to the Google Groups "Cubieboard" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cubieboard+...@googlegroups.com.
Visit this group at http://groups.google.com/group/cubieboard.
For more options, visit https://groups.google.com/d/optout.