Armbian, small notes

[Im4Tinker]

Hello forum

I installed Armbian_5.59_Tinkerboard_Debian_stretch_next_4.14.67.7z. With some correction to see u-boot and kernel on the same UART.

• I found this message
  Code:

  Loading Environment from EXT4... ** File not found /boot/boot.env **
  Do you think I can simlink it to ArmbianEnv.txt ?
  

• Also I feel that the booting and UMS function are slightly delayed. Perhaps the u-boot delay is set to 5 seconds, I think.
  
• I have modified to add a second partition to allocate /home on that. It's my opinion that I may change the installation every hour, but would be nicer to have the personal setting and data saved away from the system partition.
  
• There might be problem if the partition UUID will change, therefore should convene to determine the UUID by the mmc selected by u-boot and allow to modify the kernel parameters to write also a partition label.
  

I've arranged to remove packages which I presumed not necessary, but I probably messed up with NetworkManager. Then the wlan0 is no more seen by NM and the connection is missing. I've tried also with wpa_supplicant, but there's an error.
A little frustrating to redo the installation again and modify what I preferred to use. As long as I don't imaging how to fix the NM case.

[igorpec]

• I found this message
  Code:

  Loading Environment from EXT4... ** File not found /boot/boot.env **
  Do you think I can simlink it to ArmbianEnv.txt ?
  

• Also I feel that the booting and UMS function are slightly delayed. Perhaps the u-boot delay is set to 5 seconds, I think.
  
• I have modified to add a second partition to allocate /home on that. It's my opinion that I may change the installation every hour, but would be nicer to have the personal setting and data saved away from the system partition.
  
• There might be problem if the partition UUID will change, therefore should convene to determine the UUID by the mmc selected by u-boot and allow to modify the kernel parameters to write also a partition label.
  

I've arranged to remove packages which I presumed not necessary, but I probably messed up with NetworkManager. Then the wlan0 is no more seen by NM and the connection is missing. I've tried also with wpa_supplicant, but there's an error.
A little frustrating to redo the installation again and modify what I preferred to use. As long as I don't imaging how to fix the NM case.

1. Most recent u-boot supports saving u-boot environment to ext4/fat filesystem. Since u-boot environment was never set, a file does not exist. Run saveenv in u-boot prompt and this error will go away. It should be possible also from Linux but it was not tried yet since its a fairly new function and there was no time to deal with in detail.
2. Possible. It is also possible that we have fs checking due to the wrong time (rtc problem)
3. One partition is fine for newbies. For experienced users, this is not a problem. In any case, we don't have resources for any major changes.
4. UUID does not change unless you change it, move to a different device. This is expected behavior. RootFS UUID is set in armbianEnv.txt and in /etc/fstab if this fs is mounted. Usually is. 

A network manager is essential for connectivity while it's 1st fallback, ifupdown should work (at least on Debian Stretch, not completely sure for Ubuntu Bionic version), but probably you removed a bit 2mouch.

[Im4Tinker]

1. I'll try it out. Anyway is a little thing which just disturbs when plugging to the UART.
   
2. Ah, your right. Mostly when switching of the time is lost. Only after connecting to ntp server can recover the time difference.
   
3. For newbye is indifferent if there's or not the second partition. But even Windows has gone to such way, after a decade or more. The advantage is just as I mentioned.
   
4. Relying on partition UUID it last as long as that partition remain untouched. But for my taste I prefer to put labels, easier to remember. So it's not a problem. I managed for my own scope.
   

Thank you for your support. The installation works finer than other. Just to mention that I could use a wifi dongle with easy.

[Im4Tinker]

I'm back for some additional input.
Today I tried to boot ALarm, by using armbian u-boot with rk3288-miniarm.dtb . It is going rather good. Some trial I even got to the login. The switch for a new kernel is pretty the same.
Anyway there's a problem which I need some information. The HDMI rc-cec gives a problem like this

Code:

[   24.936998] Registered IR keymap rc-cec
[   24.941362] rc rc0: RC for dw_hdmi as /devices/platform/ff980000.hdmi/rc/rc0
[   24.949366] input: RC for dw_hdmi as /devices/platform/ff980000.hdmi/rc/rc0/input78
[   24.958168] rockchip-drm display-subsystem: bound ff980000.hdmi (ops dw_hdmi_rockchip_ops [rockchipdrm])
[   24.969102] rockchip-drm display-subsystem: failed to bind ff960000.mipi (ops dw_mipi_dsi_ops [rockchipdrm]): -517
[   25.082924] rockchip-drm display-subsystem: master bind failed: -517
[   25.092053] rockchip-drm display-subsystem: bound ff930000.vop (ops vop_component_ops [rockchipdrm])
[   25.102485] rockchip-drm display-subsystem: bound ff940000.vop (ops vop_component_ops [rockchipdrm])
[   25.112789] dwhdmi-rockchip ff980000.hdmi: Detected HDMI TX controller v2.00a with HDCP (DWC MHL PHY)

That is replied endlessly.
I'm convinced that it will be possible to achieve a mainlined kernel, so any distro would be installable. An then all developers may converge to an unified target. The only condition will be to have the device-tree correct and consistent.

[igorpec]

Kernel 4.19.y for Tinkerboard. Need help on debugging.

https://twitter.com/TonyMac_32/status/10...5859016704

[Im4Tinker]

I haven't check about Arch, but I think it might be a bit ahead of 4.19
I'd like to find how to get my RTC running with that kernel
I forgotten where to get the nightly download. It will be worth to give a try.

[igorpec]

I haven't check about Arch, but I think it might be a bit ahead of 4.19
I'd like to find how to get my RTC running with that kernel
I forgotten where to get the nightly download. It will be worth to give a try.

Not enabled for download yet - you need to build on your own at this moment or switch to nightly repository, DEV branch ... from tomorrow.

[Im4Tinker]

Thanks Igor

you need to build on your own at this moment or switch to nightly repository

I have a limited subscription quota for my internet I'd prefer to keep downloads at the minimum. So, even tomorrow it won't harm

EDIT
Anyway, I remembered to check for Archlinuxarm, which comes up nicely

Code:

$ uname -a
Linux alarm 4.19.4-1-ARCH #1 SMP PREEMPT Sun Nov 25 17:14:23 UTC 2018 armv7l GNU/Linux

Just the bluetooth seems not available. But I think there could be something to add on the module setup

Code:

$ modinfo r8723bs
filename:       /lib/modules/4.19.4-1-ARCH/kernel/drivers/staging/rtl8723bs/r8723bs.ko.gz
version:        v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
author:         Realtek Semiconductor Corp.
description:    Realtek Wireless Lan Driver
license:        GPL
srcversion:     9E0F986EC07CFC648ED2D5D
alias:          sdio:c*v024CdB723*
alias:          sdio:c*v024Cd0626*
alias:          sdio:c*v024Cd0623*
alias:          sdio:c*v024Cd0523*
alias:          acpi*:OBDA8723:*
depends:        cfg80211
staging:        Y
intree:         Y
name:           r8723bs
vermagic:       4.19.4-1-ARCH SMP preempt mod_unload modversions ARMv7 p2v8
parm:           rtw_ips_mode:The default IPS mode (int)
parm:           rtw_usb_rxagg_mode:int
parm:           rtw_btcoex_enable:Enable BT co-existence mechanism (int)
parm:           rtw_ant_num:Antenna number setting (int)
parm:           rtw_qos_opt_enable:int
parm:           ifname:The default name to allocate for first interface (charp)
parm:           rtw_initmac:charp
parm:           rtw_channel_plan:int
parm:           rtw_chip_version:int
parm:           rtw_rfintfs:int
parm:           rtw_lbkmode:int
parm:           rtw_network_mode:int
parm:           rtw_channel:int
parm:           rtw_wmm_enable:int
parm:           rtw_vrtl_carrier_sense:int
parm:           rtw_vcs_type:int
parm:           rtw_busy_thresh:int
parm:           rtw_ht_enable:int
parm:           rtw_bw_mode:int
parm:           rtw_ampdu_enable:int
parm:           rtw_rx_stbc:int
parm:           rtw_ampdu_amsdu:int
parm:           rtw_lowrate_two_xmit:int
parm:           rtw_rf_config:int
parm:           rtw_power_mgnt:int
parm:           rtw_smart_ps:int
parm:           rtw_low_power:int
parm:           rtw_wifi_spec:int
parm:           rtw_antdiv_cfg:int
parm:           rtw_antdiv_type:int
parm:           rtw_enusbss:int
parm:           rtw_hwpdn_mode:int
parm:           rtw_hwpwrp_detect:int
parm:           rtw_hw_wps_pbc:int
parm:           rtw_max_roaming_times:The max roaming times to try (uint)
parm:           rtw_mc2u_disable:int
parm:           rtw_80211d:Enable 802.11d mechanism (int)
parm:           rtw_notch_filter:0:Disable, 1:Enable, 2:Enable only for P2P (uint)
parm:           rtw_hiq_filter:0:allow all, 1:allow special, 2:deny all (uint)
parm:           rtw_tx_pwr_lmt_enable:0:Disable, 1:Enable, 2: Depend on efuse (int)
parm:           rtw_tx_pwr_by_rate:0:Disable, 1:Enable, 2: Depend on efuse (int)
parm:           rtw_phy_file_path:The path of phy parameter (charp)
parm:           rtw_load_phy_file:PHY File Bit Map (int)
parm:           rtw_decrypt_phy_file:Enable Decrypt PHY File (int)

Maybe it needs to rtw_btcoex_enable=1 to set bt available.

[Im4Tinker]

I haven't find anything in https://dl.armbian.com/tinkerboard/nightly/

[igorpec]

It was disabled, enabled now https://github.com/armbian/build/commit/...5a271710fe ... will be during a day.

But you can upgrade any Armbian image to this kernel. armbian-config -> system -> switch to beta repository -> alternative kernels -> DEV