Lubuntu possible on S905?

[Koxx]

Yes!!!!
alsa now has soundcards
I had to compile those drivers, not as modules, but in the kernel.

odroid@odroid64:~$ cat /proc/asound/cards
0 [AMLM8AUDIO ]: AML-M8AUDIO - AML-M8AUDIO
AML-M8AUDIO

[Koxx]

here is the error when I compile the kernel

CC [M] sound/soc/aml/m8/odroid_hdmi.o
In file included from sound/soc/aml/m8/odroid_hdmi.c:18:0:
include/linux/module.h:87:32: error: '__mod_of_device_table' aliased to undefined symbol 'odroid_hdmi_dt_match'
extern const struct gtype##_id __mod_##gtype##_table \
^
include/linux/module.h:145:3: note: in expansion of macro 'MODULE_GENERIC_TABLE'
MODULE_GENERIC_TABLE(type##_device, name)
^
sound/soc/aml/m8/odroid_hdmi.c:246:1: note: in expansion of macro 'MODULE_DEVICE_TABLE'
MODULE_DEVICE_TABLE(of, odroid_hdmi_dt_match);
^
scripts/Makefile.build:308: recipe for target 'sound/soc/aml/m8/odroid_hdmi.o' failed
make[4]: *** [sound/soc/aml/m8/odroid_hdmi.o] Error 1
scripts/Makefile.build:455: recipe for target 'sound/soc/aml/m8' failed
make[3]: *** [sound/soc/aml/m8] Error 2
scripts/Makefile.build:455: recipe for target 'sound/soc/aml' failed
make[2]: *** [sound/soc/aml] Error 2
scripts/Makefile.build:455: recipe for target 'sound/soc' failed
make[1]: *** [sound/soc] Error 2
Makefile:843: recipe for target 'sound' failed
make: *** [sound] Error 2
make: *** Waiting for unfinished jobs....

[Koxx]

that's the problem ... I am not sure about the sound device I should pick for my Minix 1G/8G. For me, it's the "aml_m8" (for hdmi audio)... like on my odroid c1.
But the compilation fails with this driver. I'll try cross-compile.

same for wifi.
It seems to be a AP6212 (broadcom).

http://www.cnx-software.com/2015/10/28/47-beelink-mini-mx-android-5-1-tv-box-features-amlogic-s905-processor/

[balbes150]

You need to rebuild your kernel with the sound devices used in these TV-tuners. Odroid in another system. And perform settings.

[Koxx]

There is a good manual here

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905/tronsmart-ac/firmware-roms-tools-at/565449-running-linux-from-sd-card-or-usb-flash-drive-using-balbes150-method-and-files

yes, it was my starting point.

now, kodi is running with accelerated hardware... but still no sound.

[balbes150]

There is a good manual here

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905/tronsmart-ac/firmware-roms-tools-at/565449-running-linux-from-sd-card-or-usb-flash-drive-using-balbes150-method-and-files

[Koxx]

hdmi in 1080p !
recompiled the s905_autoscript
http://www.cnx-software.com/2015/12/...mx-or-k1-plus/

usb bluetotth dongle (csr8510) working

[Koxx]

yes it does !

current status:
- hdmi 720p only (boot.ini seems to be ignored)
- MAC address is changing after each reboot (I forced it in networking config)
- ethernet is working.
- no wifi, bt or sound.
- kodi is installing but no video or sound.

I am currently rebuild the kernel to see if I can improve the situation.

[balbes150]

forget it !
I missed the aml_autoscript part. It's working now.

It work ?

[Koxx]

forget it !
I missed the aml_autoscript part. It's working now.

[Koxx]

Hi,
I am using a MiniMx, and it's working great !
thanks for all those awesome informations.
The only problem is : I still have to use the toothpick method to boot on Ubuntu sdcard.
On the MMC memory, I am still with Android 105 release.
What should I do to change the uboot ?
Is it safe for this box ?

[balbes150]

See this message, maybe You got wrong version of the script in the archive telos_uboot_update.zip

http://forum.tronsmart.com/forum/vega-s95-custom-roms-kernels-discussion/2138-openelec-for-vega-s95?start=24#11706

[freezer2k]

What firmware version You currently have in your device ? Maybe she changed ENV u-boot settings , so the script aml_autoscript from Telos doesn't work.

The one from here http://amlinuxmedia.com/forum/index.php?topic=33.0 (RC1 without the update ; this is OpenELEC installed on the eMMC and Android wiped)

[balbes150]

What firmware version You currently have in your device ? Maybe she changed ENV u-boot settings , so the script aml_autoscript from Telos doesn't work.

[freezer2k]

Compared the env settings for u-boot S95 and M18, they are very similar. You can try to use the script aml_autoscript from S95 Telos to make the necessary changes in u-boot. Make sure You can connect UART-console, if something goes wrong. We must be prepared that will need repair via UART-console !!!

I already tried to run the Telos aml_autoscript (without UART), not sure what it actually did, but still can only boot using the toothpick method and microSD. Before this I flashed the OpenELEC version from amlinux.ru, this might have also altered the stock u-boot settings/version.


Will look into getting UART attached and working.


// Edit

The unpopulated 3.3V Serial headers can be seen on those pictures: https://yadi.sk/i/pi83XCO-qPBRW

Will populate them and wire them to a Raspberry for Console access.