Alexelec установка на флешку

Alexelec установка на флешку

Выбор версии.

Образ OS Alex@ELEC поставляется в упакованном виде (архив «*.tar»).

Расшифровка названия файла, например:

AlexELECv4-Generic.20140129-r0001.tar

  • AlexELECv4 – название (AlexELEC) и версия (v4) OS
  • Generic – тип сборки. Обозначает, для какого оборудования подходит эта версия (пояснения ниже)
  • 20140129 – год, месяц и число сборки
  • r0001 – порядковый номер релиза ( r0001) версии (v4)

Типы сборок:

  • ION – для систем на чипсетах ION/ION2. Процессор Intel Atom; графика ION (GeForce 9400M) или ION2 (NVIDIA GT218).
  • Intel – для систем с процессорами Intel второго (Sandy Bridge) и третьего (Ivy Bridge) поколения со встроенной графикой.
  • Fusion — для систем с процессорами AMD Brazos и встроенным графическим ядром.
  • Generic – подходит для всего выше перечисленного оборудования (в сборке нет оптимизации под конкретный CPU и содержит драйвера для графики Nv > ​

Создание загрузочного USB-Flash носителя.

Распакуйте скачанный образ системы (архив «*.tar»). В Windows Вы можете воспользоваться WinRAR, 7-Zip …

Для проверки загруженного и распакованного образа системы Вы можете сверить MD5-суммы файлов «KERNEL» и «SYSTEM» которые находятся в каталоге «target». Суммы находятся в файлах «KERNEL.md5» и «SYSTEM.md5», соответственно.

Для создания установочного носителя Вам понадобиться USB-flash диск размером не менее 1-го Гигабайта. Запустите BAT-файл «create_livestick.bat» для создания под Windows или «create_livestick» в Linux. Пример для Windows:

Будет открыто окно в котором Вас попросят ввести букву USB-flash диска.

*После буквы диска обязательно должно стоять двоеточие « : ». Например – « g: ».

После нажатия клавиши «Enter» начнется создание.

В конце Вас попросят нажать «любую клавишу», после чего — окно будет закрыто.

Можно отсоединять «флешку» и приступать к установке системы.

Если у Вас возникли проблемы при установке системы с «флешки», пред созданием установочного USB-диска – рекомендуется отформатировать «флешку» (FAT32) программой «HPUSBFW».

Установка системы.

OS (операционная система Alex@ELEC) может быть установлена на:

  • жесткий диск (HDD)
  • твердотельный накопитель (SDD)
  • USB Flash диск
  • карту памяти (MS, MMC, SD… ext)

размером не менее 1Гб (рекомендуется 2Гб и более).

В «BIOS» Вашей материнской платы должен быть выставлен приоритет загрузки с USB-Flash диска.

В этом примере установка производиться с USB диска (флешки) – «silicon-power» на жесткий диск «TOSHIBA MK3276».

Или выбран приоритет в «BOOT Menu».

После появления следующего меню

у Вас есть 5 сек. для выбора «Live» режима загрузки системы. В этом режиме большинство функций OS будут не доступны, но таким образом можно проверить совместимость оборудования (графического адаптера, например) перед установкой системы.

Если Вы выбрали «Run AlexELEC Installer» — появиться меню установки, выберите «Quick Install of AlexELEC» и нажмите «OK» (Enter).

Далее Вам нужно выбрать диск, на который будет установлена система.

Все данные на выбраном для установки диске будут уничтожены!

На следующем экране инсталлятор спросит Вас: хотите ли Вы использовать «GPT» разделы?

Если диск на который Вы устанавливаете систему меньше 2Тб, отвечайте — «No».

Сама инсталяция занимает не более 2-х минут.

Осталось извлечь установочный носитель (флешку) и …

Установка ОС AlexELEC на карту памяти для Андроид ТВ приставки — это небольшой дистрибутив построен на базе OS Linux и OpenELEC (Open Embedded Linux Entertainment Center) с адаптацией под нужды русскоязычного пользователя. Позволяет превратить ваш ТВ бокс в полноценный медиацентр. ОС разработана, чтобы сделать загрузку Вашей системы как можно быстрее и установка настолько проста, что любой человек может превратить свою ТВ приставку в медиацентр менее чем за пятнадцать минут.

Читайте также:  Core voltage offset что это

Условия конкурса: https://youtu.be/-LckU48RrdU

by chewitt · Published August 20, 2016 · Updated September 18, 2016

An easy to use application to create bootable USB and SD card installation media has been on the staff wish-list for a long long time, so we are delighted to reveal the official “LibreELEC USB-SD Creator” app for Linux, macOS and Windows.

The app has four clearly marked steps to guide you through downloading the latest official LibreELEC image for your hardware and writing it to removable media, and checking “show all” enables selection of previous releases and current Alpha/Beta preview builds. You can also load a local image file, allowing the app to be used with previously downloaded images, or development and community created images that are not hosted on our official download servers.

The Windows version is compiled 32-bit and should run on Windows XP and newer. The macOS app is 64-bit and should run on 10.9 (Mavericks) and newer. The Linux app is available in 32-bit and 64-bit versions and should run on Ubuntu 14.04 and newer, and other Debian derivatives. The app checks for updates when started and displays a pop-up message if a newer version is available.

Please use the links below to download and test the app!

LibreELEC would like to credit our neighbours and distro collaborators at RasPlex as the original source of the app’s code, and our own @vpeter for his efforts evolving it into the work of art that you can download from today.

  • Next story LibreELEC (Krypton) v7.90.005 ALPHA
  • Previous story LibreELEC (Krypton) v7.90.004 ALPHA

53 Responses

  • Comments 51
  • Pingbacks 2

Just like UNetbootin.

does not start on Windows 10

run us administrator

run as administrator but not working

RT (which is now discontinued by MS so not on our support list) is 32-bit arm. Unless it can emulate a 64-bit x86 CPU (unlikely) the app code won’t execute on it. You can try but we’d be very surprised if it ran.

Windows 10 Version 1607 (Build 14393.51)

No problem with my W10x64pro1607

I’ve just used this and it worked perfectly 🙂
I was getting a size check error when trying to update by dropping the .tar into the update folder –
I’m on MAC OS

Symantec EndPoint Alert WS.Reputation.1

It’s a brand new file so it has no past history ‘reputation’ with Symantec; which just proves that traditional AV products are a bit dumb these days.

Great works fine here on windows 10 although Smartscreen decided it wasn’t an official app for some reason.

I’d recommend putting the Generic image at the top of the “select version” pulldown as that will be used by most people. I’d also recommend making the naming easier. Something like “Generic 32/64bit”.

Thanks again, this is a huge improvement for new users and old alike

Читайте также:  Flying перевод с английского на русский

If we sort by popularity Pi builds are on-top by a mile not Generic 🙂 but feedback on the long names is welcomed. We particularly want to see how non-English users get on as we’d like to add localisations to the app in the future. Generic is 64-bit only btw, 32-bit support was dropped about 3 years ago in OE days. App signing is also something we’d like to figure out to help with security warnings.

Wait… Does this tool allow Rpi 1 to overcome limitations mentioned here https://www.raspberrypi.org/blog/pi-3-booting-part-i-usb-mass-storage-boot/ ?? Have you found a way to boot from USB withour SD?

Honestly speaking I am really happy that LibreELEC evolves, but the manual in the Wiki could be more specific, what Creator allows for (and what is does not) 🙂

The creator app is simply a tool for creating bootable SD cards, nothing more. RPi1 and RPi2 hardware *must* boot from an SD card; they don’t support the new boot modes that article is talking about (the article does state that – just above comments). NB: Even with the new features RPi3 still needs bootcode.bin on SD for initial boot, but can then read the kernel.img and SYSTEM files etc. from attached USB media.

This is a good question. So what would be the recommended way to set up RPi3 now? Use these new bootable partitions on usb, and then separately create SD with bootcode.bin?

LE will support users running with a USB configuration (it needs no changes) but it won’t be something we encourage as it’s not really required. The speed benefit is negligible and stability issues with SD cards were resolved aeons ago.

Worked flawlessly on Windows 10 x64 latest build.

Not sure if I would have needed to, but I did right click ‘Run as Administrator’.

Used it to test the latest Alpha on my Pi1

Is there any way you can add a dropdown to add drivers for usb wifi dongles? I noticed that after installing the attatched usb wifi adapter was not discovered and I have to settle for 2.4ghz connection vise the preferred 5ghz that the usb wifi gives me. If there is a way to add it after install please let me know.

LE is an “embedded” distribution so all drivers need to be pre-compiled into the KERNEL image file and they cannot be added afterwards. It would help to know the wireless chipset details (not product brand/model) and there’s little we can do about the low quality of Realtek drivers (most popular for wireless issues) .. but you never know 🙂

Does this mean I can now use a usb stick instead of a micro sd card? I think they may be cheaper as well. I can use 2.0 and/or 3.0 although I beleive 3.0 won’t matter in terms of speed?

Yes/No. As above; Pi3 (only) still requires an SD card with bootcode.bin but all other files can be moved to USB media. Some people have a reliability preference for USB over SD, but whether that opinion is justified I couldn’t comment on. With modern SD cards the performance is likely to be much the same.

Читайте также:  Asus radeon hd 7800 series

Hi mate, no offense but you did not read the article tiroy posted properly. there is no ‘NB: Even with the new features RPi3 still needs bootcode.bin on SD for initial boot, but can then read the kernel.img and SYSTEM files etc. from attached USB media.’ present in the article, he writes he coded a single bootcode.bin for RP1&2 so the sd card never needs to be mounted that’s it. and of cause you need the next branch bootfiles to set the OTP bit on RPi3, but only ONCE.

the RPi3 can boot fine without a sdcard present at all:
https://github.com/raspberrypi/documentation/blob/master/hardware/raspberrypi/bootmodes/msd.md
https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/bootflow.md
check the bootflow, no bootcode.bin is necessary on the sdcard, it moves on to usb looking for it, and then pxe once the OTP bit has been set with ‘program_usb_boot_mode=1’ in config.txt on next branch firmware (this is done one time only).
I’ve done the tutorial, only I did not move the filesystem instead I just wrote the raspbian image file again to a usbstick (this was much faster) and made the changes to cmdline.txt and fstab. so in theory you should be able to boot LE from USB-stick/drive by installing raspbian upgrade to next branch firmware, set the OTP bit as described above. burn LE to a usb stick/removable HD using your tool, and finally edit cmdline.txt so boot and storage, points to sda or better uuid/label of the hardrive partitions instead of mmcblk0.

I am fully aware your tool is not meant for this, but an aid to write current image files in a very easy way. but there is food for thought for what you could make it do once the firmware goes stable and boards likely will come shipped with the OTP bit already set.

btw. I also agree that sdcards have reached a speed and prices where it does not matter much. I also have sdcards from when the RPi1 came out and they still work fine albeit very slow compared with nowadays standards (I recently switched to a cheap samsung evo+ on the RPi1, and what a difference when up/downgrading millhouse builds lol). I have managed to corrupt a particular sensitive one in the past though with overclocking but the card took no harm. where it really could help/speed up/make things easier, is if you run a server and boot from ssd or hdd. for embedded stuff it’s really not worth it imho.

You can still move the /storage partition to a USB device, but personally I’d use an external HDD/SSD for it. Using a USB stick will not give you extra safety, as many USB sticks (or SD cards) still have no proper TRIM support like SSDs do, so sooner or later their chips will fade into oblivion. I recently had to throw away 2 usb sticks and a SD card myself because they suddenly stopped working. HDD and SSD devices have a better track record, but yes, they are also more expensive.

Ссылка на основную публикацию
Adblock detector