[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Install on Orange Pi Plus eMMC work but no reboot

Le 07. 10. 16 à 17:09, Lennart Sorensen a écrit :
On Fri, Oct 07, 2016 at 02:48:30PM +0200, Jean-Christian de Rivaz wrote:
On some system, maybe. Not on the Orange Pi Plus
Well I guess it is one of the exceptions.

As I user I experience the H3 ROM like a PC BIOS, and the H3 U-Boot like GRUB. Like a PC BIOS can always boot a CDROM/USB (or SD card on some laptop) regardless the garbage that might affect the HDD/SSD (or eMMC on cheap laptop), the H3 ROM on the Orange Pi Plus can alway boot a SD card regardless the garbage that might affect the eMMC. Like GRUB on a PC, the H3 U-Boot is needed to boot Linux, and both are usually written into the media where Debian is installed. I know UEFI is now on the mainboard EEPROM, but it's still part of the board and don't require the installation media (CDROM/USB or SD card) to normally boot the system.

So if you account all the PC that follow that same schema, I don't think that the Orange Pi Plus is an exception. On the contrary, this is a board that perfectly fit the way the Debian installer act on any PC.

Well, I understand the technical part. But from a user point, when he see
the Orange Pi Plus in the board list of the Debian installer, I think it's
normal that he expect to be able to install a working system like the Debian
installer do for a PC.
The problem with arm systems with u-boot is that you are dealing with
embedded systems, not standard machines.  They have options for how to
boot (on some systems u-boot needs a recompile depending on if you boot
from eMMC or SD, so that's a pain).

Given debian for armhf can run on just about any modern arm system,
the only bit it doesn't cover is installing the boot loader since
that is board specific (and sometimes board configuration specific).
Having a wiki or other document listing what else needs to be done for
a given system would be handy (and probably exists for at least some of
the systems).

You mean the flash-kernel package and not by the flash-kernel-installer ?
flash-kernel takes care of the kernel and the boot script.  It doesn't
install u-boot.  At least not at this time.

Ok. Where the U-Boot install task will be appropriate to add on the installation process ?

Yes, but only at the installer time on that board. As soon as you reboot it
without the SD card or without FEL OTG injection of u-boot, you are left
with a useless board.
Well it is still fixable with a tiny bit of one time work.

I must admit that for various arm boards I have played with I have never
used the installer.  I have used debootstrap to create a rootfs and then
put it and the required bits on uSD or eMMC or wherever I wanted it.
Some of the boards have needed a custom kernel build of course, although
some didn't.

I also played with debootstrap and the like and frankly from a user point of view there are painful. The Debian installer is a wonderful simple way to install Debian in comparison.

Agree, but again take the point of view of a user that simply want to
install Debian on the Orange Pi Plus. By fare, the simplest way is to write
a SD card image of the Debian installer into a SD card and insert it into
the board slot. It could be netboot, or hd.media with an additional
partition for the ISO image. Both will work to install Debian on the eMMC.
Any others way require more work. Anyway, actually either methods will let
the user with a useless board.
Well the simplest would be to just dump a premade image on uSD and leave
it there and forget eMMC.  Of course eMMC often has better performance
than uSD and it is nice to have a method for file transfers (although
USB keys and ethernet are often more convinient).

It sound like if you say to a PC user that it just have to install Debian on a USB memory because of some GURB issues and that it can forget his HDD/SSD.


Reply to: