ODROID-XU3 installation

[sandorb]

Hi,

There's something wrong with the ODROID-XU3 installation guide here: http://archlinuxarm.org/platforms/armv7/samsung/odroid-xu3

It does not request an IP on the network, and there's nothing visible on the HDMI screen. All I can achieve with this is that the fun spins up and the red and green led lights up. No leds light up below the network interface.

I've tried different types of uSD cards, none of them worked. But it's almost there, because a with a totally wrong SD only the red led lights up, and the fun does NOT spin up. So, the process somehow fails in the middle of the boot, I guess.

The board boots with the official ubuntu image.

Can somebody please tell me what's wrong here?

[kmihelich]

The instructions work just fine, especially when they are followed.

[sandorb]

Thanks kmihalic, this was a very useful answer

I've followed the instructions properly, and all I can do with the uSD card created that way is to spin up the fan on the board and light up the red and green leds. But no network traffic, and nothing appears on the screen after that. The fan goes on a very high speed, it's very noisy compared to the normal operation with the ubuntu image, but nothing else happens.

Is that okay, that nothing appears on the screen?

I don't have a null-modem cable to check if there's something on the serial console. Is that the way to debug this kind of problems?

Can it be the size of the SD card that causes problem for the XU3 board?

[bocskay]

I've just tried to install on the eMMC card (64gb) following the instructions and I have encountered the same result twice in a row. Mine also spins up very fast and does not appear on the modems route table.

I have tried with it connected to an ODROID-VU with the boot.ini edited to include the ODROID-VU code and also with just the ethernet connected. Neither yielded any result other that high fan speed.

Any help with this would be much appreciated.

[WarheadsSE]

Do you have a serial cable?

[kmihelich]

There is no other answer other than the instructions do work. We are not in the habit of wasting our time to test and write instructions that do not work. History has also proven that the instructions only fail to work when they are not followed, or the user decides to substitute their own methods in place of our explicit instructions.

[sandorb]

The thing is, that the

$this->bbcode_second_pass_code('', ' sh sd_fusing.sh /dev/sdX ')

step causes the problem. On my notebook if the target uSD card is 2GB or 32GB, then the ext4 fs gets corrupted. (That means I cannot mount it after umounting it with the 32 GB card, and it just becomes empty (the untarred files disappear) with the 2 GB card.) I believe this isn't the expected behaviour. Maybe the dd command is a bit different on mzu machine, or what?

[sandorb]

Just for others with the same problem: it was the fdisk command I used to prepare the SD card that placed the partition's first sector to the 63rd sector. (That is the default for that old fdisk.) A more recent fdisk on another machine placed it to the 2048th sector by default and that way the sd_fuding.sh script worked properly.

[WarheadsSE]

This is actually a result of the dos compatability flag

[Goerlitzer]

I had the same issue. The problem was the eMMC card with lubuntu. After I removed the eMMC card all worked fine and I could boot the arch linux from the SD card an ssh in it from another machine. The eMMC- and the SD-card-slots have the same uuid so it seems that stops the boot process. I'm not sure but I think that is a problem for all odroids (my xu and x2 had the same issue). Maybe a sentence like "Be aware that another linux system on eMMC/SD card can disturb the boot process." in the instructions for odroid would be helpfull.