Installation of Debian 9 Minimal Server 1. After downloading the Debian 9 minimal CD image from the above links. Once you have created the installer bootable media, place your CD/USB into your system appropriate. The system will start loading media installer and a page to select the. The program we downloaded allows you to create bootable Live USB drives. Its extremely simple to use. (Numbered steps match arrows on images) 1.Insert your USB and check the corresponding drive letter. Open the program. 3.Click the Diskimage radiobutton. 4.Select your diskimage. 5.Select the correct drive letter for your usb. Install Using Debian-Installer. Supported Platforms. Starting at 2014-10-04, the daily installer builds offer the option to install the system from a USB stick, provided you are running mainline u-boot and have a device for which u-boot provides EHCI support. Install Debian to USB Drive. These instructions are not for a live install, but rather an installation of Debian to USB flash media. An added bonus here is that we’re going to first prepare our Debian chroot inside an img file that we mount as a loopback device. We can then use that img file as a generic base image. How to Install Debian 9 Stretch – Step by Step Tutorial with Screenshots Debian Install Uchiwa – Dashboard for Sensu Core Mo Debian Install Sensu on Ubuntu 16.04 / Debian 9 / Debian.
.
Contents
Support for boards using the Allwinner 'sunxi' (sun4i, sun5i, sun6i, sun7i, sun8i) family of processors, e.g. A10, A13, A31/A31s, A20, A23/A33, etc.
Supported Platforms
Debian-installer should work out of the box on all the following sunxi-based systems, but as the developers do not have access to all of them, the installer has only been tested on particular systems. If you have used the installer on one of the untested systems, please submit an installation-report to the Debian project (cf. the Submitting Installation Reports chapter in the Debian installation-guide).
Systems tested and confirmed working in Jessie
Systems for which the Jessie installer has support code, but on which installation has not been tested yet
Systems supported only in Sid/Stretch (tested and confirmed working)
Systems for which the Sid installer has support code, but on which installation has not been tested yet
The installer can also be used on other sunxi-based systems as long as device-tree support for them is available, but on those systems manual intervention during the installation is required (see below).
Storage options
From Jessie Beta 2 onwards, Debian-Installer allows installing to either a SATA disk or to an MMC/SD card. Installation to the on-board NAND flash available on some sunxi-based systems is not supported.
Booting the installed system directly from a SATA disk requires a u-boot with AHCI support (see the corresponding uboot information below).
Pre-installation preparations
On sunxi-based systems, u-boot is the system firmware that initializes the hardware and then allows to boot an operating system. It is the sunxi-equivalent of the BIOS on a PC. In contrast to PCs, where the BIOS is stored in an on-board flash memory chip, on sunxi-based devices u-boot is usually stored on an SD card. Some sunxi-based devices have on-board flash memory and even contain a stripped-down u-boot version in it, but this version is usually unsuitable for Debian. Therefore you usually have to setup an SD card with the appropriate u-boot version for your particular device (see below) as a prerequisite for installing Debian. If you use the pre-made SD card images with the installer, this step is not necessary, as these images already contain u-boot.
Installing over the network by TFTP
Debian provides a ready-made netboot tarball (jessie version, stretch version, daily sid build) that can simply be unpacked in the root directory of a TFTP server. It contains the installer as well as a network boot script which can automatically be executed by mainline u-boot as part of the default boot order (MMC/SD -> SATA -> USB mass storage -> TFTP). Manually executing the boot script is possible by entering 'run bootcmd_dhcp' at the u-boot prompt.
Manually setting up TFTP booting
If you do not want to use the netboot tarball, you can of course also manually set up TFTP booting:
Download the kernel vmlinuz, installer initrd.gz and the appropriate Flattended Device Tree (FDT) Blob (or DTB) for the board and copy them to a path on your TFTP server. e.g.
Create a script to boot the installer. e.g. /srv/tftp/didaily/cubietruck:
then to make a script which u-boot can run:
At the u-boot prompt, boot the images which were just downloaded via the script:
Install in the usual way. Use setenv diargs foo=bar to pass arguments to the installer (e.g. for preseeding)
Installing from a USB stickInstall Debian With Usb Adapter
Starting at 2014-10-04, the daily installer builds offer the option to install the system from a USB stick, provided you are running mainline u-boot and have a device for which u-boot provides EHCI support.
Unpack the daily hd-media tarballor stable hd-media tarballonto a USB stick with a filesystem that is supported by u-boot (FAT16 / FAT32 / ext2 / ext3 / ext4) and copy the ISO image of either the weekly testing Debian/testing CD #1 or the weekly testing Debian/testing DVD #1or for stable Debian/9.3 CD #1onto the stick.
Insert the USB stick into the target system and issue the command
at the u-boot command prompt to start the installer.
Notice: The combination of the daily-built hd-media tarball and the weekly-built CD/DVD image might not work correctly in periods of kernel transitions in Debian. The installer assumes that the kernel in the hd-media tarball and the kernel modules in the ISO image have the same version, which of course might not be the case directly after a kernel version bump.
Installing from an SD card image
Since 2015-04-02, Debian offers SD card images with u-boot and the netinstall version of the Debian-Installer for various sunxi-based systems at https://get.debian.org/debian/dists/stable/main/installer-armhf/current/images/netboot/SD-card-images/. The images are provided in the form of a device-specific part (containing the partition table and the device-specific u-boot) and a device-independent part (containing the actual installer), which can be unpacked and concatenated together to build a complete installer image.
The device-specific part is named firmware.<board_name>.img.gz and the device-independent part is named partition.img.gz. To write a full image to an SD card, simply unpack, concatenate and write the parts to an SD card in a single step with
These images are meant for the SD card slot on the device and will not work when SD card is inserted into USB based SD card readers. Once the installer is started, it runs completely in the system's RAM and does not need to load anything from the SD card anymore, so you can delete all existing partitions and use the full card for installing Debian. It is recommended to use the 'guided partitioning' option in the installer to create a proper partition layout on the SD card.
With jessie, the above installation methods require a serial cable to interact with the installer. An alternative is to use the HDMI output with simplefb, which is supposed to be supported in the jessie kernel (but I couldn't get it to work), but not in jessie's u-boot. However, it works fine with the stretch installer snapshots available from https://get.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/ combined with a u-boot snapshot (see below). At the u-boot prompt, use tty1 as console and disable framebuffer in the installer:
You can install jessie using the stretch installer by changing the debconf priority to low when choosing the mirror.
IMPORTANT NOTICE: The stretch builds from 2015-10-23 contain a bug which causes them to hang during the hardware detection. This bug is fixed in the daily builds available at http://d-i.debian.org/daily-images/armhf/daily/.
If your USB-Keyboard does not work in u-boot, you can mount the partition.img, copy the configuration directives from boot.scr to boot.cmd (i.e. strip initial 'noise') and insert the setenv commands above manually. Then run the following command
taken from here https://linux-sunxi.org/Mainline_U-bootand the installer will boot in non-framebuffer mode without any further input needed.
Booting the installed systemBooting the Installed System from MMC/SD Card
If you are running a current mainline u-boot or a recent u-boot-sunxi (cf. the u-boot overview below), have installed the system to an MMC/SD card and have used the guided partitioning option in the installer, auto booting the installed system works without requiring any user interaction. Note that guided partitioning must be selected to use the *whole* card and not only available space. Otherwise Debian installer will not be removed from the card. To fix this then please use the instruction for Creating a bootable SD Card with u-boot from above to install a recent U-Boot version.
Some background information:
![]()
By default, u-boot-sunxi expects the first partition on the MMC/SD card to be the boot partition and to contain either a FAT or an ext2 filesystem. The guided partitioning option in the installer takes care of this and sets up an ext2-formatted /boot partition as the first partition. If you have chosen a different layout, you have to manually set the u-boot environment variable ${partition} to the number of the partition containing /boot.
Mainline u-boot does not impose restrictions on the filesystem type of the boot partition, as long as u-boot generally supports the particular filesystem (which by default includes ext2/ext3/ext4). Mainline u-boot also does not use the ${device}/${partition} scheme used by u-boot-sunxi, but instead automatically checks all available devices for a boot script.
Booting the Installed System from a SATA Disk on Mainline U-Boot
If booting from MMC fails and a SATA disk is available, mainline u-boot automatically tries to boot from it. If you want to manually boot from a SATA disk at the u-boot prompt, just enter the command 'run bootcmd_scsi0'.
Notice: the mechanism to automatically boot from SATA disk had a bug in mainline u-boot v2014.10rc2, but this issue has been fixed in the release version of u-boot v2014.10.
Booting the Installed System from a SATA Disk on U-Boot-Sunxi
Note: u-boot-sunxi does by default not support booting from SATA. This paragraph applies only if you use a u-boot-sunxi version on which additional AHCI patches have been applied.
U-boot-sunxi does not have an autoboot mechanism for SATA disks. To manually boot from a SATA disk on u-boot-sunxi, run the following at the u-boot prompt:
This can be made the default with:
Installing on systems that are not supported out of the box
First find a suitable device tree blob (DTB) for your board. You might find one in the daily builds, or in the device-tree git repo. The latter is a repository containing all of the device tree files shipped with the upstream Linux kernel but in a separate git tree (which is much quicker to clone and build than the full kernel) which tracks mainline Linux development. You can build all of the ARM (and therefore Allwinner/sunxi) device tree blobs in that tree in only a few seconds devices with:
The device tree blobs will be found in src/arm/*.dtb. You can build a single device tree by passing it to make instead of all_arm. e.g.
Otherwise you might need to write a device tree file yourself (or find someone who is willing to do it for you). If you only have the device tree source (DTS) you can convert it to DTB using these commands:
Once you have a suitable DTB you can populate the TFTP server with the vmlinuz, initrd.gz and the DTB and create a suitable installer boot script by modifying the one above.
Boot the installer and proceed as usual. Towards the end you will encounter:
This is expected. Make a note of the partitions and continue. Once the installer has completed the installation you need to boot the resulting system, but using the DTB from TFTP in order to fix things up. This can be done like in the following example (which assumes an installation to a SATA disk):
This should now boot you to a login prompt.
Login and install flash-kernel and the u-boot-tools:
Now you need to create a flash-kernel database entry. Start by copying the entries for Cubietech Cubietruck from /usr/share/flash-kernel/db/all.db to /etc/flash-kernel/db. Now you need to modify the Machine and DTB-Id fields.
For the Machine use the output of:
For DTB-Id if you used a DTB from the daily builds then use that name for DTB-Id. If you got the DTB from somewhere else then install it as /boot/dtb-$(uname -r) and omit the DTB-Id Download adobe ultra cs3 v3 0. field. In this case you will need to take care around kernel upgrades.
Now run flash-kernel and reboot. At this point you should be able to boot using the process from Booting the Installed System above. If this fails the boot again using the manual method described above and try again e.g. fix your /etc/flash-kernel/db.
Once you have it working run reportbug flash-kernel and report a wishlist bug to support your platform. Be sure to include the contents of /etc/flash-kernel/db and say where the DTB came from.
There are two different Linux kernel series for sunxi-based systems:
Development for sunxi-based systems had originally begun based on an Allwinner android kernel. The linux-sunxi.org 3.4 kernel series is based on this android kernel and is maintained by a group of volunteers at linux-sunxi.org.
The mainline kernel is the 'official' Linux kernel series released by Linus Torvalds. Beginning with kernel 3.8, several developers have been working on integrating sunxi support into the mainline kernel. An overview of the progress can be found in the linux-sunxi.org wiki.
Debian uses the same kernel on all supported architectures and therefore supports only the mainline kernel. The disadvantage of the mainline kernel compared to the linux-sunxi.org kernel is that not all sunxi-specific drivers have yet been ported. The mainline kernel contains support for serial console, USB, SATA, Ethernet and MMC/SD, but the version in Jessie has no native display and audio drivers for sunxi hardware. When using mainline u-boot v2015.01 or newer and a suitable kernel version, it is possible to run Linux with graphics support by using the simplefb driver. Simplefb works similar to vesafb on PC hardware - u-boot initializes the display hardware with a fixed mode and the Linux kernel just uses the pre-initialized framebuffer. Support for this kind of operation is available in the mainline kernel from version 3.19 onwards and has been backported to the Debian kernel version 3.16.7-ckt7-1. The major disadvantage of simplefb in comparison to a 'proper' display driver is that the kernel has no way to reconfigure the display controller, which means that it is e.g. impossible to change the resolution and there is no display power management available. Jessie has been released with u-boot v2014.10 which does not have simplefb-support, but u-boot v2016.01 is available in Sid and Stretch, so if you would like to try simplefb, you can use this version.
First patches to implement a native kernel driver for the display engine used in the A10/A10s/A13/A20 have been posted to the Linux kernel mailing list, but those are still preliminary and probably won't enter the mainline kernel before version 4.6. An audio driver that supports the headphone jacks on some sunxi-based systems has recently been written; support for the first boards has been included in kernel 4.4 (available in Sid), support for further boards is planned for kernel 4.5.
Install Debian Usb Flash Drive
While the installer always uses the mainline kernel, it is possible to manually install a linux-sunxi.org kernel on a Debian system later on, but in that case you are on your own with regard to kernel updates and bootloader setup. Several of the automatic mechanisms in Debian to smoothly handle kernel updates and bootloader configuration will not work properly with the linux-sunxi.org 3.4 series.
Overview
There are several u-boot versions for sunxi-based systems:
Allwinner u-boot
You can mostly ignore the original Allwinner u-boot for Debian purposes. Compared to u-boot-sunxi and in particular to mainline u-boot its codebase is rather old, and it relies on proprietary bootloader components ('boot0'/'boot1') to perform basic hardware initialization. About the only use case for it is booting from the NAND flash available on some sunxi-based boards in conjunction with using an android or android-derived kernel version that contains the original Allwinner NAND flash driver for Android.
U-boot-sunxi
U-boot-sunxi is derived from the original Allwinner u-boot and is maintained by a group of volunteers at linux-sunxi.org. It contains an SPL component that takes care of the basic hardware initialization and therefore does not need the proprietary boot0/boot1 loaders from Allwinner. It can boot locally from MMC/SD card and over the network by TFTP, but it cannot access the NAND flash. The current version (as of 08/2014) has been updated to the featureset of mainline u-boot v2014.04; it does not have PSCI-, AHCI- and EHCI-support. Development of u-boot-sunxi has mostly stopped; active development happens in mainline u-boot nowadays. Therefore u-boot-sunxi is only interesting for a few systems which are not yet supported by mainline u-boot.
Mainline u-boot
Mainline u-boot is the official upstream u-boot version. It contains PSCI-, AHCI- and EHCI-support. The first mainline u-boot version with sunxi support was v2014.10, the current mainline u-boot (v2016.01) has added support for many more sunxi-based systems. If a system is supported by mainline u-boot, you should use it instead of u-boot-sunxi. Mainline u-boot has - besides the master git tree at http://git.denx.de/u-boot.git/ - so-called 'custodian trees' for each supported platform, in which platform-specific changes get integrated first before being merged into the central u-boot git repository for the next release. The sunxi custodian tree is available at http://git.denx.de/u-boot-sunxi.git/ and provides 'bleeding-edge' development versions. Those are primarily interesting for developers, normal users should use the master git tree instead.
During the v2014.10 development cycle for mainline u-boot, some rather invasive changes have been introduced. This includes restructuring the build system and introducing a new default environment and a new generic bootcmd handling. The new default environment is not fully compatible with some older bootscripts written for u-boot-sunxi, but flash-kernel >= 3.24 creates bootscripts that work with both the old and the new default environment. If you are using a flash-kernel version older than 3.24 and intend to change from u-boot-sunxi to mainline u-boot, you should update flash-kernel first.
Creating a bootable SD Card with u-boot
Since 2015-02-04, Debian provides mainline u-boot images for a variety of supported systems in the daily installer builds at http://d-i.debian.org/daily-images/armhf/daily/u-boot/. The daily builds contain both a ready-made gzipped SD card image (<boardname>.sdcard.img.gz) as well as a gzipped 'bare' u-boot image (u-boot-sunxi-with-spl.bin.gz).
The easiest way to create a bootable SD card with u-boot is to copy the ready-made card image to the card, e.g. with
Please note that writing the SD card image overwrites an already existing partition table on the card and thereby causes loss of any data that was on the card previously!
U-Boot images can also be taken from the u-boot-sunxi:armhf package. To create a bootable SD card with help of the u-boot-sunxi package, copy the appropriate u-boot image to offset 8kb on the SD card, e.g. with
https://skyeyexecutive251.weebly.com/download-miscellaneous-devices-intlib.html. for the Cubietruck. This method keeps an existing partition table on the SD card untouched.
Please note that the u-boot-sunxi package contains both normal as well as FEL images for various systems. FEL mode is a special boot mode that allows sunxi-based systems to be booted via a USB cable from another system instead of from a mass storage device. FEL mode requires specifically adapted u-boot builds which are unsuitable for booting from SD card, so use the normal non-FEL images for building bootable SD cards.
To install the u-boot-sunxi:armhf package on a non-armhf system (e.g. on an amd64-based PC), you can use Debian's multiarch functionality:
SMP/PSCI support
For SMP support on Allwinner SOCs, i.e. for using more than one CPU core, the mainline Linux kernel requires support for PSCI (Power State Coordination Interface) in u-boot, which is only available in mainline u-boot.
AHCI support
AHCI support allows u-boot to boot the kernel, initrd and dtb from a SATA harddisk. U-boot itself has still to be installed on an SD card, but the rest of the system can be put onto a (much faster) harddisk. This feature is available in mainline u-boot for most mainline-supported systems with a SATA socket.
EHCI support
EHCI support allows u-boot to boot the kernel, initrd and dtb from a USB mass storage device such as a USB memory stick or a USB harddisk. U-boot itself has still to be installed on an SD card, but the rest of the system can be put onto a USB device. This feature is available in mainline u-boot for most mainline-supported systems with a USB host (type 'A') socket.
Cubietech Cubietruck
Wifi requires non-free firmware firmware-brcm80211 at least version 0.42 plus an additional firmware file which is not yet packaged but can be installed with:
Install Debian Usb Windows
Message such as brcmfmac: brcmf_fil_cmd_data: Failed err=-23 are expected and do not represent a actual problem.
Olimex A20-OLinuXino-MICRO/A20-OLinuXino-LIME2 + 7' or 10'LCD
If you have one of those boards+lcd display and want to use the mainline kernel with simplefb http://karme.de/prisirah/ might be interesting for you.
Create Debian Install UsbBanana PI M2 Berry
(Those are just notes at this point, added by LucasNussbaum)
Installing DebianInstall Debian With Usb
Post-installation stuff
Debian Iso Usb
http://linux-sunxi.org/
Hi
Yes, you can delete all the partitions during setup using the install media when you boot from it. Review the following guide for instructions and details about configuring your BIOS or UEFI boot settings for DVD, CD, USB or SD Card. a BIOS/UEFI Setup Guide: Boot from a CD, DVD, USB Drive or SD Card https://www.groovypost.com/howto/bios-uefi-setu.. Once your computer is set to boot from the DVD, you should see this option. If you are installing from a retail Windows 10 USB thumb drive, you will be asked to select either 32 or 64 bit Windows 10. Learn more here https://www.groovypost.com/howto/choose-windows.. The Windows logo will appear on screen, this might be here for a while, as long as you see the animating dots, everything should be ok. Select your Language, Time and Keyboard method then click Next. Click Install now Windows 10 setup will prompt you for a product key during installation a couple times. If you originally upgraded from Windows 7 or Windows 8/8.1 click the option 'I don't have a key' and 'Do this later' . If you have a Windows 10 product key, you can proceed to enter it. Setup will also prompt you to select the edition you have a license for - Home or Pro. Please make sure you choose the right edition. If you choose the wrong edition, your only option will be to perform a clean install again. The copy of Windows 10 you download and upgrade from will correspond with the edition of Windows you have installed, if it does not, this is why you might be experiencing problems activating: Windows 7 Starter, Home Basic, Home Premium, Windows 8.0 Core, Windows 8.1 Core should install Windows 10 Home Windows 7 Professional, Windows 7 Ultimate, Windows 8.0 Pro, Windows 8.1 Pro should install Windows 10 Pro IF YOU ARE NOT SURE WHICH EDITION YOUR SYSTEM CAME WITH, CHOOSE WINDOWS 10 HOME. Wait while setup prepares to copy files Accept the license terms then click Next Click Custom: Install Windows only (advanced) NOTE: Sometimes Windows 10 setup can become confused if it see's a thumb drive. You might get a driver missing error or something to that effect. If you do, restart setup, but this time, when you arrive at the following screen, disconnect your thumb drive then go through Custom options. When setup is ready copy files, it will prompt you to reconnect the installation source (your USB). Select the drive then click New NOTE: If you have multiple partitions listed, select each one (starting at the bottom), then click delete until there is only a single (one) unallocated drive displayed in the window. Select the unallocated drive listed, click New, click Apply then OK This will split the drive into multiple partitions, select the Primary partition then click Next. NOTE: The System Reserved partition is where recovery files are kept for diagnostics and repairing damaged Windows 10 files; or even reinstall Windows 10. Wait while Windows installs When this phase of setup is complete, Windows will automatically restart then reboot into setup again. Windows is detecting and installing your hardware. After this is complete, Windows will restart one last time. Out of Box Experience The Out of Box Experience page is where you get to configure detailed settings in Windows, which includes creating a user account, configure privacy, sync PC settings and install modern applications. Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it. Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |