Jump to content

Recommended Posts

Posted (edited)

The memory type it is easy to determine with the command "fdisk-l". If this team will see internal storage as a regular disk (mmcblkXpX), then it's eMMC. And for such memory the desired option gxbb_p200.

 

By the way, you can accurately determine, through run your script ddbr, if he can start back up - then it's eMMC. :)

Edited by balbes150
Posted

@balbes150

Then it's eMMC as the carton box says:
 

Model: Mini M8S TV BOX

CPU: Amlogic S905 Quad-core 64-bit

ARM Cortex-A53 up to 2GHz

GPU: Penta-core ARM Mali-450

Ethernet: 100Mbps/LAN

RAM: DDR3 2GB

ROM: eMMC 8GB

WIFI: IEEE 802.11b/g/n,2.4G

BT: 4.0

Adapter: 5VDC 2A

Operation System: Android 5.1

 

Posted

@balbes150

The files in /boot/dtb and /boot/dtb-4.12.0-next-20170516+ are identical (checked with md5sum)

There is no gxbb_p200 : all dtb's are prefixed with "meson-"

So meson-gxbb-p200.dtb is the file i am looking for, of is there some other file i have to find?

If yes, i will use this in the next boot.

And a recommendation:

For a pleasant Desktop experience, this image Armbian_5.27_S905_Ubuntu_xenial_4.12.0-next-20170516+_mate.img.xz

needs some packages:

ubuntu-mate-themes ( for correctly picking GTK theme that is in memory but not exists )

adwaita-icon-theme-full ( for correctly picking the mouse pointer that again is in memory but not exists )

Also there are some useless packages that left there from xfce ( thunar* for example  as there exists caja already ).

Spoiler

Capture-2.jpg.1f6baa8602475f7eef441449d9859708.jpgCapture-1.jpg.b4b576ebe12dbeb87a368b2660e379b3.jpgCapture-3.jpg.7802cb666c08aebc3171acfc3bcba5fb.jpg

 

 

Posted

1. Directories with the same dtb. Multiple directories with the same files - the result of the installation kernel, the installation script makes an advance copy with the version name in case of error.

2. You need the files where the name has the specified value, prefixed with "meson" all the same. You can check all files to find the one with which the system will work better.

3. In the last images have already appeared of the topic.

4. A list of extra files I will check, but it can be tied to the build scripts and dependencies.

 

Thank you for the test and information, it helps to improve the system.

Posted

Started fresh with a usb stick 3.0 32GB with the latest testing image as i mentioned in previous posts.

  • USB not always picking up the boot process and some times system starts to LibreELEC that i have in eMMC.
  • WiFi was not working ( it was able to see networks but was not connecting ) but after 3 reboot it picked up my nwtwork.

Since then it is always working as expected. ( i run "rfkill unblock wifi" between those reboots, as my wifi was Soft Blocked, but i dont know if that helped any ).

  • Bluetooth is not working ( no adapter at all ).
  • Video playback with mpv still segfaults.
  • Video playback with vlc segfaults too
  • Audio is not working.
  • Youtube in windows looks ok, in fullscreen looks acceptable but i have no audio to compare if video/audio was in sync.

The first dtb tried was meson-gxbb-p200.dtd as /boot/dtb.img

That's all the info i have for now.

Tomorrow i will try another dtb ( if God wants so ).

 

Posted
I can not understand ??

 

Please help me to determine the type of wifi hardware of my x96. thank you

Screenshot at 2017-06-06 19:35:29.png

Posted

@Stress

Try the command lsmod

if wifi is working ( as i can see in your picture ), it should tell you the names of the active modules in your system.

Posted
10 hours ago, Stress said:

I can not understand ??

1. After the first command, you need to wait 1-2 minutes and check the network connections Manager the advent of Wi-Fi. If your desired network appears, you need to open the file /etc/modules and add on a new line the name of the module wifi_dummy. After that, reboot the system, if you did everything correctly, you should automatically see the wifi network at startup.

2. If the first module (wifi_dummy) network did not work. You need to run the second command "sudo modprobe dhd" . Notice all the letters exactly as written. Capitalization is important in LINUX. dhd is not equal DHD. Other actions with the dhd module are the same as in the first point.

Posted

Hi Balbes150,

 

I've been following this topic, and others related to your Linux development efforts on Amlogic platforms for a few weeks now.

 

I'm curious about the function of the Fn button inside the headphone jack. When that button is held, does the device change its boot order, and use the u-boot installed on the SD card, or does it simply change the stock u-boot's environment?

 

Is it possible to create an SD card with a custom u-boot that's bootable in an unmodified (no multiboot) TV box like the Mini M8S II simply by holding the recovery/Fn button?

Posted
10 hours ago, jakogut said:

I've been following this topic, and others related to your Linux development efforts on Amlogic platforms for a few weeks now.

 

I'm curious about the function of the Fn button inside the headphone jack. When that button is held, does the device change its boot order, and use the u-boot installed on the SD card, or does it simply change the stock u-boot's environment?

 

Is it possible to create an SD card with a custom u-boot that's bootable in an unmodified (no multiboot) TV box like the Mini M8S II simply by holding the recovery/Fn button?

1. Button makes the built-in bootloader (u-boot) in the first place to look for on an external storage medium a file (aml_autoscript). If it is, go to it aml_autoscript. If there is no such file, the loader starts the built-in recovery mode. In theory, you could write your own version aml_autoscript that will load from external media new u-boot and will give him control. But it requires a good knowledge of the structure of u-boot (source code for your specific model) and the availability of special commands for the complete transfer of control the new u-boot on an external drive.

2. If you need to boot from external media (without making any changes multi-boot) you can rename the script s905_autoscript in aml_autoscript and pressing the button will immediately run the script to start the system from external media. In this embodiment, for system start up from external media will need to click when you enable this button.

Posted (edited)
On 6/5/2017 at 1:23 PM, balbes150 said:

To ALL

 

In the last images I removed from startup all the modules of Wi-Fi. They prevent launch on some models of TV boxes (which require other modules for WiFi). So you need to manually (via terminal) to verify which model is suitable for your TV model and enter it in the file /etc/modules (for later auto run at startup).

First of all thank you very much for your hard work. You have made my nexbox usable and fun. The only part i dont undesrtand is wifi. After running the wifi dummy command it finds my network and I succesfuly connect but I dont understand how to add it to modules . I am not an experienced linux user and I dont know what line do I write (i open the file with sudo nano command). My wifi driver is rtl8723bs . How do I add it to modules config file? Thank you in advance for your answer

Edited by Joseph22
Posted
16 hours ago, Joseph22 said:

First of all thank you very much for your hard work. You have made my nexbox usable and fun. The only part i dont undesrtand is wifi. After running the wifi dummy command it finds my network and I succesfuly connect but I dont understand how to add it to modules . I am not an experienced linux user and I dont know what line do I write (i open the file with sudo nano command). My wifi driver is rtl8723bs . How do I add it to modules config file? Thank you in advance for your answer

What command do you give to load the WiFi module ?

Posted

Balbes150, I've got Linux 4.12.0-rc5 running on an Amlogic S905X based P212 device with your Arch image.

 

Next is the Mali kernel driver.

Posted

I've got 3.14.29 kernel with xorg installed manually but cannot launch kodi (twm/xterm is working fine), looks like xrandr is not detecting refresh rate and kodi denies to launch. Anyone got it working?

localhost kodi # DISPLAY=:0 startx

...

12:35:48.630 T:547496951824   DEBUG: Selected UDev as storage provider
12:35:48.655 T:547496951824    INFO: Available videomodes (xrandr):
12:35:48.655 T:547496951824    INFO: Output 'default' has 1 modes
12:35:48.656 T:547496951824    INFO: ID:0x53 Name:1920x1080 Refresh:0.000000 Width:1920 Height:1080
12:35:48.656 T:547496951824    INFO: Pixel Ratio: 1.000000
12:35:48.656 T:547496951824  NOTICE: Checking resolution 16
12:35:48.657 T:547496951824   ERROR: Failed to find matching visual
12:35:48.658 T:547496951824    INFO: GL: Maximum texture width: 32768
localhost kodi # DISPLAY=:0 xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
   1920x1080      0.00*

 

PS.  is there any way to get rid of bootimage (android on internal) and see whole kernel logs on tv without soldering uart?

Posted

Hello, I recently bought Odroid C2. Legacy Ubuntu Server image works great, but Ubuntu Server Next (mainline kernel) doesn't boot. SSH shows network error: connection timed out, screen is black. Is it something wrong with current image or my hardware? (Other OSes are working fine like legacy dekstop, DietPi). Power supply is official barrel DC jack 5V/2A

Posted

Continuing from my last post:

This is Armbian_5.27_S905_Ubuntu_xenial_4.12.0-next-20170516+_mate.img

  • Tried meson-gxbb-p200.dtb ( see previous post )
  • meson-gxbb-nexbox-a95x.dtb ( boot to cli, no keyboard, power led blinking )
  • meson-gxbb-p201.dtb ( same as p200 if not worse )
  • meson-gxbb-vega-s95-meta.dtb ( no boot at all )
  • meson-gxbb-vega-s95-pro.dtb ( no boot at all )
  • meson-gxbb-odroidc2.dtb ( no boot + power led blinking )
  • meson-gxbb-vega-s95-telos.dtb ( next to try when i have the time... )
Posted

Hi everyone,

 

It seems Mali EGL X11 support is broken, here are the steps to reproduce the defect:

 

sudo apt-get install mesa-utils cmake xorg-dev
git clone --depth 1 https://github.com/ptitseb/gl4es
cd gl4es
cmake . -DODROID=1; make GL -j4
export LD_LIBRARY_PATH=./lib
glxgears

 

Exporting `LIBGL_FB=1` (2, 3) doesn't help either.  The same allegedly works on Odroid C2 so there's no reason it shouldn't be made to work on S905 boxes as well. Any suggestions where the `eglInitialize` failure is coming from?

Posted
On 13.06.2017 at 9:00 AM, jakogut said:

I've got Linux 4.12.0-rc5 running on an Amlogic S905X based P212 device with your Arch image.

I updated the image with ArchLinux. Also added to the website test versions of packages with kernel 3.14 and 4.12 (for installation via pacman).

 

On 14.06.2017 at 1:42 PM, oczkers said:

I've got 3.14.29 kernel with xorg installed manually but cannot launch kodi (twm/xterm is working fine), looks like xrandr is not detecting refresh rate and kodi denies to launch. Anyone got it working?

What version of KODI are you trying to run ?

 

On 14.06.2017 at 1:42 PM, oczkers said:

PS.  is there any way to get rid of bootimage (android on internal) and see whole kernel logs on tv without soldering uart?

You want to install Armbian (Linux) on the internal memory ?

 

On 14.06.2017 at 6:38 PM, Joseph22 said:

sudo modprobe wifi_dummy

Add the file /etc/modules a new line with the name of the module (wifi_dummy).

 

21 hours ago, xXx said:

Continuing from my last post:

Soon to be updated to the image-4.12\13 

 

 

Posted
4 hours ago, magan said:

It seems Mali EGL X11 support is broken, here are the steps to reproduce the defect:

 

 

image Armbian Ubuntu Mate 20170601

 

root@amlogic:/home/user/gl4es# export LD_LIBRARY_PATH=./lib
root@amlogic:/home/user/gl4es# glxgears
LIBGL: Initialising gl4es
LIBGL: v0.9.7 built on Jun 15 2017 19:13:38
LIBGL:loaded: libGLESv1_CM.so
LIBGL:loaded: libEGL.so
LIBGL: Extension glBlendColor found and used
LIBGL: Extension GL_OES_point_sprite detected and used
LIBGL: Extension GL_OES_point_size_array detected
LIBGL: Extension GL_OES_framebuffer_object detected and used
LIBGL: Extension GL_OES_packed_depth_stencil detected and used
LIBGL: Extension GL_OES_depth24 detected and used
LIBGL: Extension GL_OES_rgb8_rgba8 detected and used
LIBGL: Extension GL_EXT_texture_format_BGRA8888 detected and used
LIBGL: Extension GL_OES_depth_texture detected and used
LIBGL: Extension GL_OES_texture_cube_map detected and used
LIBGL: Extension GL_OES_draw_texture detected and used
LIBGL: Max texture size: 4096
LIBGL: Texture Units: 8, Max lights: 8, Max planes: 1
LIBGL: Implementation Read is GL_RGB/GL_UNSIGNED_SHORT_5_6_5
LIBGL: Current folder is:/home/user/gl4es
Error: couldn't open display (null)

 

Posted
Quote

What version of KODI are you trying to run ?

17.3 kodi-standalone and kodi on top of twm using fbdev but no luck so i'll wait for 4.12+ and full gles support via xf86-video-armsoc

 

Quote

You want to install Armbian (Linux) on the internal memory ?

It would be perfect to just remove splashscreen and show full boot process without installing to internal - i'm just not familiar with android boot process.

Posted
1 hour ago, balbes150 said:

root@amlogic

Ha, ha, I generally don't do that or the original report would have included this recommendation to actually see gl4es in action:

 

LIBGL_FB=3 glxgears

 

Still, apart from the wrong permissions, Mali X11/EGL doesn't work as reported, but at least now I understand the setup - only the framebuffer driver is available. I'll report the broken FB display to the author, maybe it can be fixed. 

Posted

Balbes150, how to use latest debian/ubuntu image on sd card, i have khadas vim board with Android nougat, it was different procedure with marshmallow, update app is different?

 

Tapatalk

 

 

 

 

Posted
1 hour ago, Tommy21 said:

how to use latest debian/ubuntu image on sd card, i have khadas vim board with Android nougat, it was different procedure with marshmallow, update app is different?

I have not tested the multi-boot into Android 7.

 

 

To All

By the way, there's good news, with the help of user SFS (from Russian forum puppyrus) I've worc with KODI to play videos in standard Linux. Only on the basis of ArchLinux, but I hope it can be transferred to the Armbian. Now need time to go to collect and debug and assembe a complete system. If you would be willing to help testing KODI on the basis of ArchLinux - write. Also welcome assistance in building packages for Debian\Ubuntu (I have little experience in this).

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines