Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
Running Linux From SD Card or USB Flash Drive - Using Balbes150 Method And Files.
Collapse
This is a sticky topic.
X
X
-
Originally posted by maco222 View Post
Yesterday I have successfully compiled the kernel with that config option changed from 'm' to 'y'. But I don't understand what type of image is linux.img in the /boot partition of your system images. After kernel compilation I have standard uncompressed image in arch/arm64/boot. I guess I have to convert it using mkimage from u-boot-tools, but every try ends with sth like 'Invalid ARM64 image magic' error message.
Comment
-
Hello, I would like to run Armbian_5.27_S9xxx_Debian_jessie_3.14.29_server_20 170319.img.xz from my Nexbox A95X from sd card. I don't need graphical interface, my goal is to use the device as a server in the house, I would like to use it just running OScam and TVheadend. I would also like to prevent bricking my device running the command "apt-get remove linux-u-boot-odroidc2" after the installation, can I run than apt-get distupgrade without getting in troubles? Please annyone who could give me some advice before bricking my device?
Is the login and password: root and 1234? And wich dtb file should I use?
regards, Jefken3
Comment
-
Originally posted by Jefken3 View PostHello, I would like to run Armbian_5.27_S9xxx_Debian_jessie_3.14.29_server_20 170319.img.xz from my Nexbox A95X from sd card. I don't need graphical interface, my goal is to use the device as a server in the house, I would like to use it just running OScam and TVheadend. I would also like to prevent bricking my device running the command "apt-get remove linux-u-boot-odroidc2" after the installation, can I run than apt-get distupgrade without getting in troubles? Please annyone who could give me some advice before bricking my device?
Is the login and password: root and 1234? And wich dtb file should I use?
i can't tell is dist-upgrade would break things, i don't know if a different version of debian will run on those images, it should but balbes150 will have to confirm this.
For more recent software i would advise you to use the ubuntu 16.04 server image instead.
Test various dtb to find one that works on your device, on my nexbox a95x s905 (not s905x) i'm using the gxbb_p201.dtb version.
If your box has a s905x soc (recent a95x boxes are s905x) you'll have to use another dtb, they are classified by their prefix gxbb is for s905, GXL is for s905x then 1g or 2g for your ram version.
if you've copied the wrong dtb.img on your BOOT partition then the system will fail to boot, usually resulting in a black screen, you may or may not get to the Nexbox logo and get stuck there.
Don't forget you have to install the update script "aml_autoscript.zip" (included in the image) from your android update tool (in the app menu).
oscam and tvheadend should run without problems but you may have some troubles running your dvb hardware on those images, i don't know exactly which dvb drivers are included.
if you're interested, know that you should also be able to install the linux system on your internal emmc (after you've made sure everything works fine from sdcard).
Yes initial password is 1234, it'll ask to change it and create a new user, you can also do that through ssh.
if i'm correct the server image doesn't require a firstrun reboot, but to be safe, reboot it if it does not after a minute.
Comment
-
Originally posted by eldonT View Post
i can't tell is dist-upgrade would break things, i don't know if a different version of debian will run on those images, it should but balbes150 will have to confirm this.
For more recent software i would advise you to use the ubuntu 16.04 server image instead.
Test various dtb to find one that works on your device, on my nexbox a95x s905 (not s905x) i'm using the gxbb_p201.dtb version.
If your box has a s905x soc (recent a95x boxes are s905x) you'll have to use another dtb, they are classified by their prefix gxbb is for s905, GXL is for s905x then 1g or 2g for your ram version.
if you've copied the wrong dtb.img on your BOOT partition then the system will fail to boot, usually resulting in a black screen, you may or may not get to the Nexbox logo and get stuck there.
Don't forget you have to install the update script "aml_autoscript.zip" (included in the image) from your android update tool (in the app menu).
oscam and tvheadend should run without problems but you may have some troubles running your dvb hardware on those images, i don't know exactly which dvb drivers are included.
if you're interested, know that you should also be able to install the linux system on your internal emmc (after you've made sure everything works fine from sdcard).
Yes initial password is 1234, it'll ask to change it and create a new user, you can also do that through ssh.
if i'm correct the server image doesn't require a firstrun reboot, but to be safe, reboot it if it does not after a minute.
regards.
Comment
-
Originally posted by Jefken3 View PostThank You for Your advice, I didn't know there was a new soc on these boxes, this info will certainly help me further and prevent a lot of frustration. Kszaq cleand up his device tree-archive, only the most recents are available, will these last ones suit for running balbes150's linux images? Can You point me to the download link for ubuntu 16.04?regards.
anyways you'll find current balbes150's linux images here : https://yadi.sk/d/5_32km_EsCV2A/
i believe "20170316" were already fixed for emmc install (there was a problem last week), but you can stay on sdcard until it's been validated.
Anyways once you've installed the boot script you can always boot from sd card even if you've installed a faulty armbian image (balbes150 ones) to your emmc.
And If you plan to do so, always make a backup of your emmc before, all the backup / install script are in the /root/ directory.
i don't know about Kszaq "linux" images, so far i only tested libreelec builds from him, if his has other images i'd be interested to know where ?
Comment
-
Originally posted by Jefken3 View PostI think I'm wrong I thougt that I had to copy Kszaq's dtb.img to root, now that I have prepared my sd-card I do see a folder with dtb's, Do I copy one of these and rename to dtb.img and place it in root of partition with BOOT label?
yes there are multiple folders with dtbs in the BOOT partition, copy your box dtb (or the one compatible with it) from the directory "dtb" to a file name "dtb.img" in the root of BOOT..
Also the kernel has changed so old dtb won't work anymore with balbes150 images, only use the dtbs from the BOOT/dtb/ dir
And as i said before don't worry about choosing the wrong dtb, it won't break anything, the sd card boot modifies nothing on your box internal flash, the only thing that will happen is that it won't boot, then chose another dtb until you get it to boot.
Comment
-
Originally posted by eldonT View Post
Also the kernel has changed so old dtb won't work anymore with balbes150 images, only use the dtbs from the BOOT/dtb/ dir
Comment
-
Hi guys,
I am trying to follow the guide to get this going, but I am failing to update the u-boot.
"1b.) With no SD card inserted in the S95, power on the S95. When Android boots, insert the SD Card to the S95. Open the Backup&Update app. Under the "Local Update" section, click "Select". It will examine the SD Card and you should see the file, "'aml_autoscript.zip", select it. This will return you to the Update&Backup app's home screen. In the "Local Update" section, click "Update", to run the update."
my box is coming with android 6.0.1 and the update app will give me error when I try to load that zip.
Any other way to do that.
I was able to write OpenELEC 7 on SD and boot from it using the reset button hold while powering on. This method also allows me to boot TWRP.
Any ideas how to proceed?
Comment
-
Now all images Armbian and LE has all the files for activate the multi-boot. Anything in addition to download and copy to media is not required.
1. Download the desired image
2. Unpack
3. Record an image on the medium
4. to run Android
5. open the app "Update&Backup"
6. Select local update and an archive on removable media (aml_update.zip)
7. Run update
8. System twice to reboot and start running the system from external media.
9. If after 7-10 minutes on the monitor not to receive any messages on system startup. Turn off TV box and add in manual in the first partition (FAT) the file "dtb.img". On the media there is a directory dtb from where you can take the files and copy them to the root of the renaming of "dtb.img".
Need to pick up the option for the file system will run. Pay attention, after you add\change the dtb file, you need to try to run the system and waiting to run 7-10 minutes. If not happened, repeat with a different dtb file.
Comment
What's Going On
Collapse
There are currently 2254 users online. 1 members and 2253 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Comment