Jump to content

Armbian for Amlogic S9xxx kernel 5.x

balbes150

By balbes150
in General Chat

 Share

Recommended Posts

Donate your old hardware to community. Start a giveaway Raffle!

balbes150

balbes150

Posted
  • Author
Posted
On 9/16/2019 at 3:45 PM, Z11ntal33r said:

This is the patch I need which Amlogic worked out for g12 devices: dwc3/core: xHCI host not responding to stop endpoint command
I can't seem to find the patch in Kernel 5.3 patch notes... So I suppose it isn't merged yet. Could you please add the patch to your next build, @balbes150?

This patch is for an old kernel, I don't work with this old kernel.

 

17 hours ago, KrishIsola said:

Could you please help to resolve or provide leads to the solution?

WiFi is evil, I don't work with it.

Link to comment
Share on other sites
Z11ntal33r

Z11ntal33r

Posted
Posted
19 minutes ago, balbes150 said:

This patch is for an old kernel, I don't work with this old kernel.

 

I understand. It's an unfortunate situation as the USB3.0 interface for meson-g12b devices is broken and neither Amlogic or Hardkernel devs want to send the patch upstream to mainline and follow it up (https://forum.odroid.com/viewtopic.php?f=176&t=33993&p=268688#p268598)...  One should absolutely avoid using meson-g12b devices if you want to use USB3 then. At the current state, my VIM3 is pointless as I can't move files between my micro SD and USB Harddrives. So I guess I've to build my own kernel and include this patch

Link to comment
Share on other sites
Z11ntal33r

Z11ntal33r

Posted
Posted
6 hours ago, balbes150 said:

Try this version, it has a kernel with all the latest changes.

https://yadi.sk/d/ixLCvgeXlW4-1w

Unfortunately, with the build above I'm in a boot loop. I tried both booting from mSD slot and booting from a USB 3.0 mSD card reader. The latest line I can see on my TV is "OK Mounted /tmp." before it boots again. So I guess that the next line where it fails is "Found device /dev/...." etc. 

This is what I did:

  1. Installed the build to a brand new mSD card and changed both /extlinux/extlinux.conf and uEnv.ini to meson-g12b-a311d-khadas-vim3.dtb.
  2. Activated multi-boot and booted to mSD card. No other devices were connected expect from a keyboard.

PS: Which means that both Android VIM3_Pie_V190907 and my current Armbian_5.95_Aml-g12_Debian_buster_default_5.3.0-rc6_20190904 build is installed to eMMC.

I think it's easier to just upgrade kernel with my current system, so I will build the latest kernel files tomorrow both with and without the patch. I'll let you know when I've tested this, balbes150:)

Link to comment
Share on other sites
KrishIsola

KrishIsola

Posted
Posted
22 hours ago, KrishIsola said:

Hello @balbes150 and Others,

 

I'm able to boot my X96 (S905x) device from a SD card with linux builds  (tried Armbian 5.91 and 5.96). However, when I tried to configure the device as Wifi Hotspot / Access Point (AP), facing issues with connecting or pairing to the AP. The device appears to be configured with SSID and a static IP. But, when I tried to pair another device to this SSID + Passcode, it fails - something like invalid passcode.

 

Could you please help to resolve or provide leads to the solution?

 

- Krish

 

For my wifi hotspot authentication problem, I found the below log messages. Does this log help to identify the problem?

I'm not an expert in kernel / os level. Hence, seeking for help (DESPERATE !!!).

Sep 17 17:36:08 nsiod68 kernel: [  492.907311] Modules linked in: fuse ipt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter bnep 8021q garp mrp stp llc zstd zram r8723bs(C) cfg80211 snd_soc_meson_aiu_i2s snd_soc_meson_aiu_spdif hci_uart btqca btbcm btintel meson_vdec bluetooth crct10dif_ce videobuf2_dma_contig v4l2_mem2mem dw_hdmi_cec videobuf2_memops videobuf2_v4l2 videobuf2_common ir_nec_decoder ecdh_generic videodev rfkill meson_ir snd_soc_meson_audio_core pwm_meson ao_cec media adc_keys input_polldev sch_fq_codel ip_tables x_tables ipv6 crc_ccitt
Sep 17 17:36:08 nsiod68 kernel: [  492.957945] Process RTW_CMD_THREAD (pid: 782, stack limit = 0x000000006754f26e)
Sep 17 17:36:08 nsiod68 kernel: [  492.965188] CPU: 3 PID: 782 Comm: RTW_CMD_THREAD Tainted: G         C        5.1.15-aml-s905 #5.91
Sep 17 17:36:08 nsiod68 kernel: [  492.974067] Hardware name: Khadas VIM (DT)
Sep 17 17:36:08 nsiod68 kernel: [  492.978123] pstate: 80000005 (Nzcv daif -PAN -UAO)
Sep 17 17:36:08 nsiod68 kernel: [  492.982921] pc : nl80211_send_station.isra.62+0x2d0/0xbb0 [cfg80211]
Sep 17 17:36:08 nsiod68 kernel: [  492.989198] lr : nl80211_send_station.isra.62+0xa98/0xbb0 [cfg80211]
Sep 17 17:36:08 nsiod68 kernel: [  492.995456] sp : ffff000010bdbbb0
Sep 17 17:36:08 nsiod68 kernel: [  492.998734] x29: ffff000010bdbbb0 x28: ffff000010bdc008
Sep 17 17:36:08 nsiod68 kernel: [  493.003995] x27: ffff000010bdbc50 x26: ffff80000dc15030
Sep 17 17:36:08 nsiod68 kernel: [  493.009257] x25: ffff80000dc15000 x24: 0000000000000030
Sep 17 17:36:08 nsiod68 kernel: [  493.014518] x23: ffff000010bdbcd8 x22: 0000000000000000
Sep 17 17:36:08 nsiod68 kernel: [  493.019779] x21: ffff800074961e00 x20: ffff000012315000
Sep 17 17:36:08 nsiod68 kernel: [  493.025040] x19: ffff80000dc15014 x18: 0000000000000000
Sep 17 17:36:08 nsiod68 kernel: [  493.030301] x17: 0000000000000000 x16: 0000000000000000
Sep 17 17:36:08 nsiod68 kernel: [  493.035563] x15: 0000000000000000 x14: 000af217000bdd00
Sep 17 17:36:08 nsiod68 kernel: [  493.040827] x13: 0000000000000000 x12: 0000000000000000
Sep 17 17:36:08 nsiod68 kernel: [  493.046088] x11: 0000000000ff1740 x10: 2d1a2d000c02ac0f
Sep 17 17:36:08 nsiod68 kernel: [  493.051350] x9 : 00000104ac0f0000 x8 : ffff80000dc15064
Sep 17 17:36:08 nsiod68 kernel: [  493.056611] x7 : 0000000000000000 x6 : ffff80000dc15064
Sep 17 17:36:08 nsiod68 kernel: [  493.061872] x5 : ffff80000dc15064 x4 : ffff000010bdbda0
Sep 17 17:36:08 nsiod68 kernel: [  493.067133] x3 : 0000000000000268 x2 : 0000000000000064
Sep 17 17:36:08 nsiod68 kernel: [  493.072394] x1 : 0000000000000008 x0 : ffff80000dc15000
Sep 17 17:36:08 nsiod68 kernel: [  493.077657] Call trace:
Sep 17 17:36:08 nsiod68 kernel: [  493.080173]  nl80211_send_station.isra.62+0x2d0/0xbb0 [cfg80211]
Sep 17 17:36:08 nsiod68 kernel: [  493.086112]  cfg80211_new_sta+0x78/0xe8 [cfg80211]
Sep 17 17:36:08 nsiod68 kernel: [  493.090895]  rtw_cfg80211_indicate_sta_assoc+0x6c/0x90 [r8723bs]
Sep 17 17:36:08 nsiod68 kernel: [  493.096826]  rtw_stassoc_event_callback+0x194/0x1e0 [r8723bs]
Sep 17 17:36:08 nsiod68 kernel: [  493.102507]  mlme_evt_hdl+0x74/0xa0 [r8723bs]
Sep 17 17:36:08 nsiod68 kernel: [  493.106817]  rtw_cmd_thread+0x16c/0x360 [r8723bs]
Sep 17 17:36:08 nsiod68 kernel: [  493.111392]  kthread+0x124/0x128
Sep 17 17:36:08 nsiod68 kernel: [  493.114578]  ret_from_fork+0x10/0x1c
Sep 17 17:36:08 nsiod68 kernel: [  493.118117] Code: 9b037c23 11000421 a9090fa4 8b03009c (b8636883)
Sep 17 17:36:08 nsiod68 kernel: [  493.124153] ---[ end trace c1575f5c5fb8f5a3 ]---
Sep 17 17:36:11 nsiod68 systemd[1]: serial-getty@ttyS0.service: Succeeded.
Sep 17 17:36:11 nsiod68 systemd[1]: serial-getty@ttyS0.service: Service RestartSec=100ms expired, scheduling restart.
Sep 17 17:36:11 nsiod68 systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 46.
Sep 17 17:36:11 nsiod68 systemd[1]: Stopped Serial Getty on ttyS0.
Sep 17 17:36:11 nsiod68 systemd[1]: Started Serial Getty on ttyS0.
Sep 17 17:36:14 nsiod68 kernel: [  498.890843] RTL8723BS: ap recv disassoc reason code(8) sta:6c:8d:c1:db:7b:0c
Sep 17 17:36:14 nsiod68 hostapd: wlan0: STA 6c:8d:c1:db:7b:0c IEEE 802.11: disassociated
 

Link to comment
Share on other sites
dbsharpe

dbsharpe

Posted
Posted
32 minutes ago, KrishIsola said:

 

For my wifi hotspot authentication problem, I found the below log messages. Does this log help to identify the problem?

I'm not an expert in kernel / os level. Hence, seeking for help (DESPERATE !!!).

 

 

I had issues with hostapd but I don't recall the exact problem. I got it down to the armbian kernel being a bit too new and perhaps a bug had crept in. The .config feature that wasnt working might have been multiple ssid's or higher speed wireless 802.11n.
Work around was to get hostapd sources a couple of years old and compile it.

I use rt2xxx based hardware and don't recommend  the internal wifi devices.

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
14 hours ago, Z11ntal33r said:

Unfortunately, with the build above I'm in a boot loop. I tried both booting from mSD slot and booting from a USB 3.0 mSD card reader. The latest line I can see on my TV is "OK Mounted /tmp." before it boots again. So I guess that the next line where it fails is "Found device /dev/...." etc. 

Use the DTB from the previous image. There is an error in the current DTB for VIM3.

 

 

Link to comment
Share on other sites
KrishIsola

KrishIsola

Posted
Posted
22 hours ago, dbsharpe said:

 

I had issues with hostapd but I don't recall the exact problem. I got it down to the armbian kernel being a bit too new and perhaps a bug had crept in. The .config feature that wasnt working might have been multiple ssid's or higher speed wireless 802.11n.
Work around was to get hostapd sources a couple of years old and compile it.

I use rt2xxx based hardware and don't recommend  the internal wifi devices.

Thanks for the response. I'm not sure of what to do next.

Link to comment
Share on other sites
Z11ntal33r

Z11ntal33r

Posted
Posted
13 hours ago, balbes150 said:

Use the DTB from the previous image. There is an error in the current DTB for VIM3.

 

Yeah, that did the trick! With the build Armbian_5.96_Aml-g12_Ubuntu_bionic_dev_5.3.0_20190917 you uploaded, I'm finally able to copy/move files over the USB3.0 interface without any IO errors. Did you actually include the patch i referred to into this build or is it pure kernel 5.3.0?

One more thing. I tried to build the kernel files by following your guide at https://github.com/150balbes/Build-Armbian, but when I was building, I faced an error as seen from the picture attached. I've only followed your guide and selected "U-boot and kernel packages" -> "Do not change the kernel configuration" -> "aml-g12" -> "next". I want to upgrade my current installed build to the latest kernel with the patch. Any ideas why it fails? Let me know if you want the whole output or any logs.

Spoiler

 

Screenshot 2019-09-18 at 20.41.18.png

 

Thanks for the great help BTW! It's awesome when someone from the community aid much more support than the actually support team who released the SBC...

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
12 hours ago, Z11ntal33r said:

-> "next".

Build version NEXT is very naughty and is intended for experienced users who know the process of kernel build and the build Armbian (used source code directly from GIT Linux), also requires additional manual operations to configure a shared build (disable wireguard, etc.).  You'd better use the "default" option.

 

13 hours ago, KrishIsola said:

Just curious, what "wifi" issues are fixed in this build?

Current fixes address only a few model specific errors.

Link to comment
Share on other sites
Z11ntal33r

Z11ntal33r

Posted
Posted
14 hours ago, balbes150 said:

Build version NEXT is very naughty and is intended for experienced users who know the process of kernel build and the build Armbian (used source code directly from GIT Linux), also requires additional manual operations to configure a shared build (disable wireguard, etc.).  You'd better use the "default" option.

 

Current fixes address only a few model specific errors.

The reason for why I did not choose "default" was that it states: "Vendor provided / legacy". I do not want a vendor kernel, I want to update my 5.3RC6 kernel to 5.3.0.

I ask again: Your build Armbian_5.96_Aml-g12_Ubuntu_bionic_dev_5.3.0_20190917 you uploaded fixed the IO errors over USB3.0 interface for g12 devices. Did you actually include the patch i referred to into this build or is it pure kernel 5.3.0?

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
5 minutes ago, Z11ntal33r said:

The reason for why I did not choose "default" was that it states: "Vendor provided / legacy".

This text is outdated and it is not necessary to pay attention to it.

 

7 minutes ago, Z11ntal33r said:

I ask again: Your build Armbian_5.96_Aml-g12_Ubuntu_bionic_dev_5.3.0_20190917 you uploaded fixed the IO errors over USB3.0 interface for g12 devices. Did you actually include the patch i referred to into this build or is it pure kernel 5.3.0?

Many additional patches are included in this kernel.

Link to comment
Share on other sites
Z11ntal33r

Z11ntal33r

Posted
Posted
On 9/19/2019 at 10:22 AM, balbes150 said:

This text is outdated and it is not necessary to pay attention to it.

Good to know! Choosing "default" worked perfectly and I built kernel 5.3.0 with the latest commit v20190918. I can see from GH source that you did include the patch dwc3/core: xHCI host not responding to stop endpoint command into commit v20190918. Thanks! :)

For meson-g12 users: If you want to upgrade kernel to 5.3.0 with balbes150 v20190918 patches, the .deb files can be downloaded at: Armbian 5.96 and kernel 5.3.0 for meson-g12 devices (v.20190918)

Link to comment
Share on other sites
KrishIsola

KrishIsola

Posted
Posted

Hello @balbes150,

 

I have the following observations to share.

Observation with X96Max (S905x2 2gb ram 16gb eMMC). Request for your help to resolve.

  1. Flashed 5.96 (& also latest dated 20-Sep) image on SD card.
  2. Edited uEvn.ini and set the dtb_name=/dtb/meson-g12a-x96-max-rmii.dtb
    • Also tried with dtb_name=/dtb/meson-g12a-x96-max.dtb
  3. Successfully booted with Armbian Linux
  4. However, only ethernet is shown. Wireless lan (wlan0) is not detected at all. Not detecting usb wifi adapter too

Few other observations from 5.96 Armbian_Buster_desktop:

  1. dhcpcd, dnsmasq are not available by default
    • Specific to Ubuntu_Bionic image: When tried to install with "apt-get install", gets an error like "ports.ubuntu.com" is not available
    • Tried this for few days assuming the portal is down. But unable to install packages on ubuntu builds
  2. Chrome: I'm trying a webrtc solution and browser show errors like video codecs are not available
    • I remember the same webrtc solution worked with 5.91 build
    • The codecs are VP8, H.264. Not sure of why the webrtc library complains that codecs are missing

Regards,

Krishna

 

Link to comment
Share on other sites
maachifx

maachifx

Posted
Posted

hello! 

first thank you for your hard work...

now i installed arndian ubuntu version desktop bionic 5.89 ,5.90 and 5.96 i had no problem with boot or installation ...

however when i try to install programs like vlc , kodi , google chrome , ext.... i cant get it to work 

my question is : is it possible to install programs in this ubuntu or not ?

ps  i am using USB drive of 16g and my tv box is almogic tanix tx3 max s905w

thanks again and plz help

Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted
9 hours ago, maachifx said:

my question is : is it possible to install programs in this ubuntu or not ?

It should work fine. Do you have an internet connection? How are you trying to install them? Best way is to use the terminal.

sudo apt install vlc kodi chromium

You give very little useful info. Please show what's the result of your installation efforts.

Link to comment
Share on other sites
qstaq

qstaq

Posted
Posted
7 hours ago, balbes150 said:

New image 5.97

 

Hi @balbes150

 

Just tried your new 5.97 image on an Odroid N2. All the basic hardware seems to work but Im getting a display saturated in green colour.  It looks like the blue colour is missing from the RGB signal, the same as when you have a faulty display cable. Its not an X11 problem, the display is green coloured in the framebuffer too, infact its green right from the point the kernel initialises. Any ideas as to what might be causing this?

 

I have not tried any previous versions of your G12 images yet or the official Armbian K4.9 build. The devices previously ran a buildroot based firmware of my own making with HK's 4.9 and there were no colour problems under framebuffer or wayland (no x11). Ive also just tried the Manjaro N2 release and that seems to work fine.

 

armbianmonitor -u:  http://ix.io/1WzE

 

 Thanks

 

 

Update:

Just tried the normal Armbian N2 build from the main download page and the colour problem is not there, the problem is only in your Yandisk images

 

Normal Armbian:  http://ix.io/1WAf

 

Update 2:

Just tried the 5.96 image and its fine. The colour problem is only with the 5.97 image

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
14 hours ago, qstaq said:

Any ideas as to what might be causing this?

 

u-boot-2019 has a bug when working with the new kernel. For the new image to work properly on the N2, you must use either u-boot-2015 (which is in SPI) or replace the u-boot on the SD card. I have launched a new version of SPIboot. Which includes support for direct system startup from USB (and easy setup of any order of startup from all media) and use for tests and work only USB 3.0, which works much faster than all SD cards and eMMC.

 

 

 

 

Link to comment
Share on other sites
KrishIsola

KrishIsola

Posted
Posted
On 9/22/2019 at 12:28 AM, KrishIsola said:

Hello @balbes150,

 

I have the following observations to share.

Observation with X96Max (S905x2 2gb ram 16gb eMMC). Request for your help to resolve.

  1. Flashed 5.96 (& also latest dated 20-Sep) image on SD card.
  2. Edited uEvn.ini and set the dtb_name=/dtb/meson-g12a-x96-max-rmii.dtb
    • Also tried with dtb_name=/dtb/meson-g12a-x96-max.dtb
  3. Successfully booted with Armbian Linux
  4. However, only ethernet is shown. Wireless lan (wlan0) is not detected at all. Not detecting usb wifi adapter too

Few other observations from 5.96 Armbian_Buster_desktop:

  1. dhcpcd, dnsmasq are not available by default
    • Specific to Ubuntu_Bionic image: When tried to install with "apt-get install", gets an error like "ports.ubuntu.com" is not available
    • Tried this for few days assuming the portal is down. But unable to install packages on ubuntu builds
  2. Chrome: I'm trying a webrtc solution and browser show errors like video codecs are not available
    • I remember the same webrtc solution worked with 5.91 build
    • The codecs are VP8, H.264. Not sure of why the webrtc library complains that codecs are missing

Regards,

Krishna

 

 

Hello!
I appreciate of any help with X96Max (S905x2) issue mentioned above.

Link to comment
Share on other sites
KrishIsola

KrishIsola

Posted
Posted

Hello!

May I know of the Android TV box device models of Amlogic S905/S905x/S912, Armbian is supported without any issues?
The n/w functionality required is: LAN, Wifi (Hotspot), WebRTC (Codecs: VP8, H.264) If possible (VP9, H.265 too).

After going through various posts in this forum, came to an opinion that X96 (S905x) and X96Max (S905x2) works good. But, facing different issues with wifi and configuring as AP. On S905x2, wlan itself is not detected with 5.96 Debian buster image

Link to comment
Share on other sites
funben

funben

Posted
Posted

Hello to all

 

Thanks to @balbes150 for creating armbian.

Here is my problem, I can't figure how to start it.

  1. I have a Beelink Mini MXIII v20_20160408
  2. I downloaded   Armbian_5.97_Aml-g12_Debian_buster_default_5.3.0_20190923.img (also tried with Armbian_5.90_Aml-s905_Debian_buster_default_5.1.0_20190701.img )
  3. I change dtb in uenv.ini to dtb_name=/dtb/meson-gxbb-p200.dtb (and also tried with dtb_name=/dtb-5.1.0-aml-s905/meson-gxbb-p200.dtb)
    I used this DTB because @Janaboy Janaboy say it works fine for mxIII
  4. I burned it on SD card using rufus & Booted with recovery mode
  5. I Have now have message "Gave up waiting for root file sytem device"

For more details, here is the console capture

https://pasteboard.co/IyXxDCZ.jpg

https://pasteboard.co/IyXyjaP.jpg

 

What should I do from here ?

Link to comment
Share on other sites
funben

funben

Posted
Posted

Thanks for your answer.

 

I started armbian succesfully with  "meson-gxbb-nexbox-a95x.dtbjeedom" however how can I check that erverything is fine / that it is the right DTB.

It seem that I have a network issue, the box is plugged with ethernet cable and I have "Network is unreachable" error

I had to start manually the network service

 

With the meson-gxbb-vega-s95-meta.dtb and meson-gxbb-vega-s95-pro.dtb the network started succesfully

How do I know which DTB is the best ?

 

 

 

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept