Any plan for basic mainline linux support?

User avatar
tobetter
Posts: 4123
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 48 times
Been thanked: 213 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by tobetter » Tue Oct 01, 2019 11:25 pm

elatllat wrote:
Tue Oct 01, 2019 11:07 pm
5.3.3 build (and script).
It would be 5.3.2, I also put them into my build queue. :)

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Tue Oct 01, 2019 11:34 pm

tobetter wrote:
Tue Oct 01, 2019 11:25 pm
elatllat wrote:
Tue Oct 01, 2019 11:07 pm
5.3.3 build (and script).
It would be 5.3.2, I also put them into my build queue. :)
Greg is using scripts without safety checks to prevent his typo so 5.3.2 was released as 5.3.3, and there is no point for him to revert it.
https://lkml.org/lkml/2019/10/1/58

User avatar
tobetter
Posts: 4123
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 48 times
Been thanked: 213 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by tobetter » Tue Oct 01, 2019 11:52 pm

elatllat wrote:
tobetter wrote:
Tue Oct 01, 2019 11:25 pm
elatllat wrote:
Tue Oct 01, 2019 11:07 pm
5.3.3 build (and script).
It would be 5.3.2, I also put them into my build queue. :)
Greg is using scripts without safety checks to prevent his typo so 5.3.2 was released as 5.3.3, and there is no point for him to revert it.
https://lkml.org/lkml/2019/10/1/58
good to know, thanks.

"Tapatalk wishes you to have fun with ODROID"


juanjo1024
Posts: 15
Joined: Sat Sep 02, 2017 10:07 pm
languages_spoken: english, spanish
ODROIDs: C2 N2
Has thanked: 0
Been thanked: 0
Contact:

Re: Any plan for basic mainline linux support?

Unread post by juanjo1024 » Wed Oct 02, 2019 7:51 am

@tobetter, can your 4.9 image be used safely ? i saw it is A LOT smaller than the official HK image.. can I assume it is a real minimal instalation ?
thanks a lot
Juanjo

User avatar
tobetter
Posts: 4123
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 48 times
Been thanked: 213 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by tobetter » Wed Oct 02, 2019 8:13 am

juanjo1024 wrote:
Wed Oct 02, 2019 7:51 am
@tobetter, can your 4.9 image be used safely ? i saw it is A LOT smaller than the official HK image.. can I assume it is a real minimal instalation ?
thanks a lot
Juanjo
"Safely" is very broadcast word...for me. :) What I can say is that I cannot guarantee that it is safe to use, but the image that I made contains the limited packages or tweaks except the packages and that's pretty much similar, I think, when you finished up the installation on PC.

juanjo1024
Posts: 15
Joined: Sat Sep 02, 2017 10:07 pm
languages_spoken: english, spanish
ODROIDs: C2 N2
Has thanked: 0
Been thanked: 0
Contact:

Re: Any plan for basic mainline linux support?

Unread post by juanjo1024 » Wed Oct 02, 2019 8:22 am

tobetter wrote:
Wed Oct 02, 2019 8:13 am
juanjo1024 wrote:
Wed Oct 02, 2019 7:51 am
@tobetter, can your 4.9 image be used safely ? i saw it is A LOT smaller than the official HK image.. can I assume it is a real minimal instalation ?
thanks a lot
Juanjo
"Safely" is very broadcast word...for me. :) What I can say is that I cannot guarantee that it is safe to use, but the image that I made contains the limited packages or tweaks except the packages and that's pretty much similar, I think, when you finished up the installation on PC.
you are right, it would be better to ask if its as safe/stable as the hardkernel image ?

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Wed Oct 02, 2019 8:25 am

juanjo1024 wrote:
Wed Oct 02, 2019 7:51 am
@tobetter, can your 4.9 image be used safely ?...
The closer to upstream a kernel is, the more testing it gets, and therefore the more stable and safe it is likely to be.

User avatar
tobetter
Posts: 4123
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 48 times
Been thanked: 213 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by tobetter » Wed Oct 02, 2019 9:06 am

juanjo1024 wrote:
Wed Oct 02, 2019 8:22 am
tobetter wrote:
Wed Oct 02, 2019 8:13 am
juanjo1024 wrote:
Wed Oct 02, 2019 7:51 am
@tobetter, can your 4.9 image be used safely ? i saw it is A LOT smaller than the official HK image.. can I assume it is a real minimal instalation ?
thanks a lot
Juanjo
"Safely" is very broadcast word...for me. :) What I can say is that I cannot guarantee that it is safe to use, but the image that I made contains the limited packages or tweaks except the packages and that's pretty much similar, I think, when you finished up the installation on PC.
you are right, it would be better to ask if its as safe/stable as the hardkernel image ?
Basically the kernel on my image is being built from the HK kernel source tree, so kernel features would be same. My image would not be mature like Meveric's or Armbian, you will see unsupported features. FYI, my build firm is also running with my images and te packages I built, it works quite well unless Docker crashes.

yrzr
Posts: 4
Joined: Fri Sep 27, 2019 9:20 pm
languages_spoken: english
ODROIDs: odroid-n2, odroid-xu4
Has thanked: 0
Been thanked: 0
Contact:

Re: Any plan for basic mainline linux support?

Unread post by yrzr » Wed Oct 02, 2019 7:48 pm

Help, any idea how to fix this issue?

Code: Select all

[    6.172117] mali_kbase: loading out-of-tree module taints kernel.
[    6.179846] mali ffe40000.gpu: Continuing without Mali regulator control
[    6.179939] ------------[ cut here ]------------
[    6.179942] reset reset-controller@1004 (ID: 20) is not acquired
[    6.179974] WARNING: CPU: 4 PID: 944 at drivers/reset/core.c:380 reset_control_assert+0x140/0x1c8
[    6.179976] Modules linked in: mali_kbase(O+) dw_hdmi_cec soundcore crct10dif_ce(+)
[    6.179989] CPU: 4 PID: 944 Comm: udevd Tainted: G           O      5.3.2-gentoo-yrzr #4
[    6.179991] Hardware name: Hardkernel ODROID-N2 (DT)
[    6.179995] pstate: 60000005 (nZCv daif -PAN -UAO)
[    6.179999] pc : reset_control_assert+0x140/0x1c8
[    6.180002] lr : reset_control_assert+0x140/0x1c8
[    6.180003] sp : ffff00001226b860
[    6.180005] x29: ffff00001226b860 x28: ffff000012355000 
[    6.180009] x27: 0000000000000100 x26: ffff7dfffe9fbbb8 
[    6.180013] x25: ffff000009a3d648 x24: ffff8000d7532180 
[    6.180016] x23: ffff8000d7e93810 x22: ffff8000d7e93800 
[    6.180019] x21: 0000000000000000 x20: 0000000000000000 
[    6.180022] x19: ffff8000d7532380 x18: ffff000011cdf000 
[    6.180025] x17: 0000000000000000 x16: 0000000000000000 
[    6.180028] x15: 00000000fffffff0 x14: ffff000011da0d98 
[    6.180031] x13: 0000000000000000 x12: ffff000011da0000 
[    6.180034] x11: ffff000011cdf000 x10: ffff000011da03e0 
[    6.180037] x9 : 0000000000000000 x8 : 0000000000000001 
[    6.180039] x7 : 0000000000000107 x6 : ffff000011da0000 
[    6.180042] x5 : 0000000000000001 x4 : 0000000000000000 
[    6.180045] x3 : 0000000000000000 x2 : 00000000ffffffff 
[    6.180048] x1 : e0417a8019dd1e00 x0 : 0000000000000000 
[    6.180051] Call trace:
[    6.180055]  reset_control_assert+0x140/0x1c8
[    6.180058]  reset_control_assert+0xec/0x1c8
[    6.180117]  pm_soft_reset+0x38/0x90 [mali_kbase]
[    6.180165]  pm_callback_power_on+0x80/0x168 [mali_kbase]
[    6.180216]  kbase_pm_register_access_enable+0x24/0x38 [mali_kbase]
[    6.180265]  kbase_backend_early_init+0x44/0xa0 [mali_kbase]
[    6.180314]  kbase_platform_device_probe+0x1f4/0xbc8 [mali_kbase]
[    6.180321]  platform_drv_probe+0x50/0xa0
[    6.180324]  really_probe+0xec/0x3d0
[    6.180326]  driver_probe_device+0xdc/0x130
[    6.180330]  device_driver_attach+0x6c/0x78
[    6.180332]  __driver_attach+0x9c/0x168
[    6.180337]  bus_for_each_dev+0x70/0xc0
[    6.180340]  driver_attach+0x20/0x28
[    6.180343]  bus_add_driver+0x190/0x220
[    6.180345]  driver_register+0x60/0x110
[    6.180349]  __platform_driver_register+0x44/0x50
[    6.180395]  kbase_platform_driver_init+0x20/0x1000 [mali_kbase]
[    6.180401]  do_one_initcall+0x74/0x1b0
[    6.180407]  do_init_module+0x50/0x208
[    6.180410]  load_module+0x1dd4/0x2368
[    6.180414]  __se_sys_finit_module+0x9c/0xf8
[    6.180418]  __arm64_sys_finit_module+0x18/0x20
[    6.180424]  el0_svc_common.constprop.0+0x88/0x150
[    6.180427]  el0_svc_handler+0x20/0x78
[    6.180430]  el0_svc+0x8/0xc
[    6.180433] ---[ end trace 908af3635a9bad7c ]---
[    6.180446] ------------[ cut here ]------------
[    6.180449] reset reset-controller@1004 (ID: 20) is not acquired
[    6.180474] WARNING: CPU: 4 PID: 944 at drivers/reset/core.c:421 reset_control_deassert+0x134/0x190
[    6.180476] Modules linked in: mali_kbase(O+) dw_hdmi_cec soundcore crct10dif_ce(+)
[    6.180486] CPU: 4 PID: 944 Comm: udevd Tainted: G        W  O      5.3.2-gentoo-yrzr #4
[    6.180488] Hardware name: Hardkernel ODROID-N2 (DT)
[    6.180491] pstate: 60000005 (nZCv daif -PAN -UAO)
[    6.180494] pc : reset_control_deassert+0x134/0x190
[    6.180497] lr : reset_control_deassert+0x134/0x190
[    6.180498] sp : ffff00001226b860
[    6.180500] x29: ffff00001226b860 x28: ffff000012355000 
[    6.180504] x27: 0000000000000100 x26: ffff7dfffe9fbbb8 
[    6.180507] x25: ffff000009a3d648 x24: ffff8000d7532180 
[    6.180510] x23: ffff8000d7e93810 x22: ffff8000d7e93800 
[    6.180513] x21: 0000000000000000 x20: 0000000000000000 
[    6.180516] x19: ffff8000d7532380 x18: ffff000011cdf000 
[    6.180519] x17: 0000000000000000 x16: 0000000000000000 
[    6.180522] x15: 00000000fffffff0 x14: ffff000011da0d98 
[    6.180524] x13: 0000000000000000 x12: ffff000011da0000 
[    6.180527] x11: ffff000011cdf000 x10: ffff000011da03e0 
[    6.180530] x9 : 0000000000000000 x8 : 0000000000000001 
[    6.180533] x7 : 000000000000013c x6 : ffff000011da0000 
[    6.180536] x5 : 0000000000000001 x4 : 0000000000000000 
[    6.180538] x3 : 0000000000000000 x2 : 00000000ffffffff 
[    6.180541] x1 : e0417a8019dd1e00 x0 : 0000000000000000 
[    6.180544] Call trace:
[    6.180547]  reset_control_deassert+0x134/0x190
[    6.180549]  reset_control_deassert+0xe0/0x190
[    6.180598]  pm_soft_reset+0x48/0x90 [mali_kbase]
[    6.180647]  pm_callback_power_on+0x80/0x168 [mali_kbase]
[    6.180694]  kbase_pm_register_access_enable+0x24/0x38 [mali_kbase]
[    6.180741]  kbase_backend_early_init+0x44/0xa0 [mali_kbase]
[    6.180788]  kbase_platform_device_probe+0x1f4/0xbc8 [mali_kbase]
[    6.180794]  platform_drv_probe+0x50/0xa0
[    6.180796]  really_probe+0xec/0x3d0
[    6.180799]  driver_probe_device+0xdc/0x130
[    6.180802]  device_driver_attach+0x6c/0x78
[    6.180805]  __driver_attach+0x9c/0x168
[    6.180810]  bus_for_each_dev+0x70/0xc0
[    6.180812]  driver_attach+0x20/0x28
[    6.180815]  bus_add_driver+0x190/0x220
[    6.180817]  driver_register+0x60/0x110
[    6.180820]  __platform_driver_register+0x44/0x50
[    6.180866]  kbase_platform_driver_init+0x20/0x1000 [mali_kbase]
[    6.180871]  do_one_initcall+0x74/0x1b0
[    6.180876]  do_init_module+0x50/0x208
[    6.180879]  load_module+0x1dd4/0x2368
[    6.180883]  __se_sys_finit_module+0x9c/0xf8
[    6.180887]  __arm64_sys_finit_module+0x18/0x20
[    6.180891]  el0_svc_common.constprop.0+0x88/0x150
[    6.180895]  el0_svc_handler+0x20/0x78
[    6.180897]  el0_svc+0x8/0xc
[    6.180899] ---[ end trace 908af3635a9bad7d ]---
[    6.181147] mali ffe40000.gpu: GPU identified as 0x2 arch 7.2.1 r0p0 status 0
[    6.181331] ------------[ cut here ]------------
[    6.181334] reset reset-controller@1004 (ID: 20) is not acquired
[    6.181364] WARNING: CPU: 4 PID: 944 at drivers/reset/core.c:380 reset_control_assert+0x140/0x1c8
[    6.181365] Modules linked in: mali_kbase(O+) dw_hdmi_cec soundcore crct10dif_ce(+)
[    6.181377] CPU: 4 PID: 944 Comm: udevd Tainted: G        W  O      5.3.2-gentoo-yrzr #4
[    6.181379] Hardware name: Hardkernel ODROID-N2 (DT)
[    6.181383] pstate: 60000005 (nZCv daif -PAN -UAO)
[    6.181386] pc : reset_control_assert+0x140/0x1c8
[    6.181389] lr : reset_control_assert+0x140/0x1c8
[    6.181391] sp : ffff00001226b750
[    6.181393] x29: ffff00001226b750 x28: ffff000012355000 
[    6.181396] x27: 0000000000000100 x26: ffff7dfffe9fbbb8 
[    6.181399] x25: ffff8000d59a5b58 x24: 0000000000000000 
[    6.181402] x23: 0000000000000002 x22: ffff000011cc9688 
[    6.181405] x21: ffff8000d59a5000 x20: 0000000000000000 
[    6.181408] x19: ffff8000d7532d80 x18: ffff000011cdf000 
[    6.181411] x17: ffff8000d6991c28 x16: 0000000000000001 
[    6.181414] x15: 00000000fffffff0 x14: ffff000011da0d98 
[    6.181417] x13: 0000000000000000 x12: ffff000011da0000 
[    6.181420] x11: ffff000011cdf000 x10: ffff000011da03e0 
[    6.181423] x9 : 0000000000000000 x8 : 0000000000000001 
[    6.181426] x7 : 0000000000000172 x6 : ffff000011da0000 
[    6.181429] x5 : 0000000000000001 x4 : 0000000000000000 
[    6.181431] x3 : 0000000000000000 x2 : 00000000ffffffff 
[    6.181434] x1 : e0417a8019dd1e00 x0 : 0000000000000000 
[    6.181437] Call trace:
[    6.181441]  reset_control_assert+0x140/0x1c8
[    6.181444]  reset_control_assert+0xec/0x1c8
[    6.181495]  pm_soft_reset+0x38/0x90 [mali_kbase]
[    6.181543]  kbase_pm_do_reset+0x44/0x190 [mali_kbase]
[    6.181589]  kbasep_protected_mode_disable+0x10/0x18 [mali_kbase]
[    6.181636]  kbase_pm_init_hw+0x128/0x698 [mali_kbase]
[    6.181681]  kbase_hwaccess_pm_powerup+0x3c/0x128 [mali_kbase]
[    6.181728]  kbase_backend_late_init+0x38/0xb0 [mali_kbase]
[    6.181774]  kbase_platform_device_probe+0x4a4/0xbc8 [mali_kbase]
[    6.181780]  platform_drv_probe+0x50/0xa0
[    6.181783]  really_probe+0xec/0x3d0
[    6.181787]  driver_probe_device+0xdc/0x130
[    6.181790]  device_driver_attach+0x6c/0x78
[    6.181792]  __driver_attach+0x9c/0x168
[    6.181797]  bus_for_each_dev+0x70/0xc0
[    6.181800]  driver_attach+0x20/0x28
[    6.181802]  bus_add_driver+0x190/0x220
[    6.181805]  driver_register+0x60/0x110
[    6.181808]  __platform_driver_register+0x44/0x50
[    6.181854]  kbase_platform_driver_init+0x20/0x1000 [mali_kbase]
[    6.181859]  do_one_initcall+0x74/0x1b0
[    6.181864]  do_init_module+0x50/0x208
[    6.181868]  load_module+0x1dd4/0x2368
[    6.181872]  __se_sys_finit_module+0x9c/0xf8
[    6.181875]  __arm64_sys_finit_module+0x18/0x20
[    6.181880]  el0_svc_common.constprop.0+0x88/0x150
[    6.181884]  el0_svc_handler+0x20/0x78
[    6.181887]  el0_svc+0x8/0xc
[    6.181889] ---[ end trace 908af3635a9bad7e ]---
[    6.181919] ------------[ cut here ]------------
[    6.181922] reset reset-controller@1004 (ID: 20) is not acquired
[    6.181947] WARNING: CPU: 4 PID: 944 at drivers/reset/core.c:421 reset_control_deassert+0x134/0x190
[    6.181949] Modules linked in: mali_kbase(O+) dw_hdmi_cec soundcore crct10dif_ce(+)
[    6.181958] CPU: 4 PID: 944 Comm: udevd Tainted: G        W  O      5.3.2-gentoo-yrzr #4
[    6.181960] Hardware name: Hardkernel ODROID-N2 (DT)
[    6.181964] pstate: 60000005 (nZCv daif -PAN -UAO)
[    6.181967] pc : reset_control_deassert+0x134/0x190
[    6.181969] lr : reset_control_deassert+0x134/0x190
[    6.181971] sp : ffff00001226b750
[    6.181973] x29: ffff00001226b750 x28: ffff000012355000 
[    6.181976] x27: 0000000000000100 x26: ffff7dfffe9fbbb8 
[    6.181979] x25: ffff8000d59a5b58 x24: 0000000000000000 
[    6.181982] x23: 0000000000000002 x22: ffff000011cc9688 
[    6.181985] x21: ffff8000d59a5000 x20: 0000000000000000 
[    6.181988] x19: ffff8000d7532d80 x18: ffff000011cdf000 
[    6.181991] x17: ffff8000d6991c28 x16: 0000000000000001 
[    6.181994] x15: 00000000fffffff0 x14: ffff000011da0d98 
[    6.181996] x13: 0000000000000000 x12: ffff000011da0000 
[    6.181999] x11: ffff000011cdf000 x10: ffff000011da03e0 
[    6.182002] x9 : 0000000000000000 x8 : 0000000000000001 
[    6.182005] x7 : 00000000000001a9 x6 : ffff000011da0000 
[    6.182008] x5 : 0000000000000001 x4 : 0000000000000000 
[    6.182010] x3 : 0000000000000000 x2 : 00000000ffffffff 
[    6.182013] x1 : e0417a8019dd1e00 x0 : 0000000000000000 
[    6.182016] Call trace:
[    6.182019]  reset_control_deassert+0x134/0x190
[    6.182021]  reset_control_deassert+0xe0/0x190
[    6.182069]  pm_soft_reset+0x48/0x90 [mali_kbase]
[    6.182117]  kbase_pm_do_reset+0x44/0x190 [mali_kbase]
[    6.182164]  kbasep_protected_mode_disable+0x10/0x18 [mali_kbase]
[    6.182211]  kbase_pm_init_hw+0x128/0x698 [mali_kbase]
[    6.182260]  kbase_hwaccess_pm_powerup+0x3c/0x128 [mali_kbase]
[    6.182308]  kbase_backend_late_init+0x38/0xb0 [mali_kbase]
[    6.182355]  kbase_platform_device_probe+0x4a4/0xbc8 [mali_kbase]
[    6.182360]  platform_drv_probe+0x50/0xa0
[    6.182362]  really_probe+0xec/0x3d0
[    6.182365]  driver_probe_device+0xdc/0x130
[    6.182368]  device_driver_attach+0x6c/0x78
[    6.182371]  __driver_attach+0x9c/0x168
[    6.182375]  bus_for_each_dev+0x70/0xc0
[    6.182377]  driver_attach+0x20/0x28
[    6.182379]  bus_add_driver+0x190/0x220
[    6.182382]  driver_register+0x60/0x110
[    6.182385]  __platform_driver_register+0x44/0x50
[    6.182432]  kbase_platform_driver_init+0x20/0x1000 [mali_kbase]
[    6.182436]  do_one_initcall+0x74/0x1b0
[    6.182442]  do_init_module+0x50/0x208
[    6.182445]  load_module+0x1dd4/0x2368
[    6.182449]  __se_sys_finit_module+0x9c/0xf8
[    6.182452]  __arm64_sys_finit_module+0x18/0x20
[    6.182457]  el0_svc_common.constprop.0+0x88/0x150
[    6.182461]  el0_svc_handler+0x20/0x78
[    6.182464]  el0_svc+0x8/0xc
[    6.182466] ---[ end trace 908af3635a9bad7f ]---
[    6.193999] debugfs: Directory 'ff800280.cec' with parent 'regmap' already present!
[    6.198369] Registered IR keymap rc-empty
[    6.198428] rc rc0: meson-ir as /devices/platform/soc/ff800000.bus/ff808000.ir/rc/rc0
[    6.198518] input: meson-ir as /devices/platform/soc/ff800000.bus/ff808000.ir/rc/rc0/input0
[    6.198665] rc rc0: lirc_dev: driver meson-ir registered at minor = 0, raw IR receiver, no transmitter
[    6.199139] meson-ir ff808000.ir: receiver initialized
[    6.244149] axg-sound-card sound: snd-soc-dummy-dai <-> ff6421c0.audio-controller mapping ok
[    6.248029] axg-sound-card sound: snd-soc-dummy-dai <-> ff642200.audio-controller mapping ok
[    6.249188] axg-sound-card sound: snd-soc-dummy-dai <-> ff642240.audio-controller mapping ok
[    6.250192] axg-sound-card sound: I2S IN B <-> TDM Pad mapping ok
[    6.250223] axg-sound-card sound: snd-soc-dummy-dai <-> TDM Loopback mapping ok
[    6.682509] mali ffe40000.gpu: Failed to soft-reset GPU (timed out after 500 ms), now attempting a hard reset
[    6.682871] mali ffe40000.gpu: Probed as mali0

mxmilkb
Posts: 12
Joined: Fri Apr 26, 2019 9:28 am
languages_spoken: English
ODROIDs: N2
Has thanked: 8 times
Been thanked: 4 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by mxmilkb » Sat Oct 05, 2019 2:30 am

Manjaro ARM has a test of using linux-aarch64 before mainline will be looked at again. Currently it doesn't boot after swapping out.

The linux-aarch64 is the Arch Linux ARM package (defined by its PKGBUILD).

How long before the stock mainline might support this? For server or starting to work on a GUI solution.

tobetter - Could the PKGBUILD be adapted to use your build script?

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Sat Oct 05, 2019 2:38 am

mxmilkb wrote:
Sat Oct 05, 2019 2:30 am
..How long before the stock mainline might support [Manjaro ARM ]?...
Looks like something is broken the Arch script, 5.3 works fine if you build it yourself (or use my or tobetter's build).

raidenii
Posts: 11
Joined: Tue Sep 17, 2019 9:04 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Any plan for basic mainline linux support?

Unread post by raidenii » Sun Oct 06, 2019 11:06 am

Quick question - does mainline kernel have KMS driver?

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Sun Oct 06, 2019 12:46 pm

Last edited by elatllat on Fri Oct 18, 2019 9:44 pm, edited 1 time in total.

erm67
Posts: 21
Joined: Sat Jun 22, 2019 10:53 pm
languages_spoken: english,german,italian
ODROIDs: N2
Has thanked: 1 time
Been thanked: 1 time
Contact:

Re: Any plan for basic mainline linux support?

Unread post by erm67 » Sun Oct 06, 2019 6:53 pm

At least mainline kernel mis coming .....
I tried your image and boots, unfortunately I have a uas-only usb3 enclosure and my root partition ison a ssd in such enclosure ... the uas module is not built by your script so when I booted it I only got a lot of errors from the disk in the enclosure, that also left the controller inside it very confused and it refused to boot also with the old kernel until I reset the enclosure. I also rebuilt the mainline kernel with the uas module but I still got a lot of strange errors, like:

Code: Select all

[    7.064750] sd 0:0:0:0: [sda] Unaligned partial completion (resid=78, sector_sz=512)
[    7.064772] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[    7.064781] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current] 
[    7.064788] sd 0:0:0:0: [sda] tag#0 ASC=0x21 ASCQ=0x0 
[    7.064798] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 e6 e6 e6 e6 e6 00 00 00 00 08 00 00
[    7.064807] blk_update_request: critical target error, dev sda, sector 253879390758400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    7.065369] sd 0:0:0:0: [sda] Unaligned partial completion (resid=78, sector_sz=512)
[    7.065385] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[    7.065395] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current] 
[    7.065402] sd 0:0:0:0: [sda] tag#0 ASC=0x21 ASCQ=0x0 
[    7.065411] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 e6 e6 e6 e6 e6 00 00 00 00 02 00 00
[    7.065419] blk_update_request: critical target error, dev sda, sector 253879390758400 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[    7.065428] Buffer I/O error on dev sda, logical block 126939695379200, async page read
[    7.065929] sd 0:0:0:0: [sda] Unaligned partial completion (resid=78, sector_sz=512)
[    7.065944] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[    7.065952] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current] 
[    7.065959] sd 0:0:0:0: [sda] tag#0 ASC=0x21 ASCQ=0x0 
[    7.065968] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 e6 e6 e6 e6 e6 02 00 00 00 06 00 00
[    7.065975] blk_update_request: critical target error, dev sda, sector 253879390758402 op 0x0:(READ) flags 0x0 phys_seg 3 prio class 0
[    7.065982] Buffer I/O error on dev sda, logical block 126939695379201, async page read
[    7.065989] Buffer I/O error on dev sda, logical block 126939695379202, async page read
[    7.065993] Buffer I/O error on dev sda, logical block 126939695379203, async page read
It also reported the drives inside as being enormous:

Code: Select all

[    5.294582] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[    5.305052] sd 0:0:0:0: [sda] 253879390758630 512-byte logical blocks: (130 PB/115 PiB)
[    5.312059] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    5.318009] sd 0:0:0:0: [sda] Write Protect is off
[    5.321975] sd 0:0:0:0: [sda] Mode Sense: 2b 00 00 00
[    5.322514] sd 0:0:0:0: [sda] No Caching mode page found
[    5.327813] sd 0:0:0:0: [sda] Assuming drive cache: write through
sda is a 120gb ssd and not 130 PetaBytes :-) and works fine with kernel 4.9.
I suspect there are still problems with uas and usb3, all problems disappeared when I hard reset the enclosure and reboot the 4.9 kernel, maybe the problems were caused by the first boot without uas drivers that confused the controller, since also the 4.9 was reporting thr wrong disk size when I rebooted without hard resetting the enclosure. I will test again maybe next week.
Please can you include the uas module? Multi disk uas enclosure are quite cheap and becoming common.

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Sun Oct 06, 2019 7:43 pm

erm67 wrote:
Sun Oct 06, 2019 6:53 pm
...include the uas module?...
If you can get it working (otherwise report the bug to Neil or the maintainer)
personally I don't use UAS to keep smartctl working.

erm67
Posts: 21
Joined: Sat Jun 22, 2019 10:53 pm
languages_spoken: english,german,italian
ODROIDs: N2
Has thanked: 1 time
Been thanked: 1 time
Contact:

Re: Any plan for basic mainline linux support?

Unread post by erm67 » Sun Oct 06, 2019 11:58 pm

That is funny since most uas controllers support SAT ATA PASS-THROUGH, mine does, you probably need just a better uas bridge since uas is definitely faster and more responsive tha the old n Bulk Object Transfer. My enclosure has 4 disks and no raid capability, without uas only the first drive is accessible.

Code: Select all

smartctl -q noserial -r ioctl,2 -d sat -i /dev/sdb
smartctl 7.0 2018-12-30 r4883 [aarch64-linux-4.9.190+] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org


REPORT-IOCTL: Device=/dev/sdb Command=IDENTIFY DEVICE
 Input:   FR=...., SC=0x01, LL=...., LM=...., LH=...., DEV=...., CMD=0xec IN
>>>> do_scsi_cmnd_io: sg_io_ver=3
 [ata pass-through(16): 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 ]
  scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0
  sg_info=0x0  sg_duration=0 milliseconds  resid=0
  Incoming data, len=512 [only first 256 bytes shown]:

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Mon Oct 07, 2019 2:08 am

erm67 wrote:
Sun Oct 06, 2019 11:58 pm
...SAT ATA PASS-THROUGH...
Seagate (possibly the largest hard drive manufacturer on the planet) unfortunately had issues with that last time I checked.
Maybe time I re-checked.

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Tue Oct 08, 2019 9:56 pm

Last edited by elatllat on Fri Oct 18, 2019 9:43 pm, edited 1 time in total.

User avatar
tobetter
Posts: 4123
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 48 times
Been thanked: 213 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by tobetter » Wed Oct 09, 2019 5:52 am

I've updated my repository for mainline 5.4.0-rc2 as well as 5.3.5 and had a quick test if they can boot up, not done a reliable test.

You can use one of these commands in order to install the kernel on my Debian/Ubuntu image.

Code: Select all

$ sudo apt installl linux-image-5.3.5-odroid-upstream-arm64

Code: Select all

$ sudo apt install linux-image-5.4.0-rc2-odroid-upstream-arm64
@elatllat, do you also have this error message with 5.4.0-rc2 kernel?

Code: Select all

[    0.632930] dwc3 ff500000.usb: Failed to get clk 'ref': -2
[    0.633007] dwc3 ff500000.usb: IRQ host not found
[    0.637637] dwc3 ff500000.usb: IRQ dwc_usb3 not found
[    1.253830] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Wed Oct 09, 2019 6:13 am

clk is an old issue, irq/pwm is new to 5.4 which I have not tested yet.

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Wed Oct 09, 2019 3:44 pm


yrzr
Posts: 4
Joined: Fri Sep 27, 2019 9:20 pm
languages_spoken: english
ODROIDs: odroid-n2, odroid-xu4
Has thanked: 0
Been thanked: 0
Contact:

Re: Any plan for basic mainline linux support?

Unread post by yrzr » Thu Oct 10, 2019 2:00 pm

tobetter wrote:
Wed Oct 09, 2019 5:52 am
I've updated my repository for mainline 5.4.0-rc2 as well as 5.3.5 and had a quick test if they can boot up, not done a reliable test.

You can use one of these commands in order to install the kernel on my Debian/Ubuntu image.

Code: Select all

$ sudo apt installl linux-image-5.3.5-odroid-upstream-arm64

Code: Select all

$ sudo apt install linux-image-5.4.0-rc2-odroid-upstream-arm64
@elatllat, do you also have this error message with 5.4.0-rc2 kernel?

Code: Select all

[    0.632930] dwc3 ff500000.usb: Failed to get clk 'ref': -2
[    0.633007] dwc3 ff500000.usb: IRQ host not found
[    0.637637] dwc3 ff500000.usb: IRQ dwc_usb3 not found
[    1.253830] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517
I get this error with 5.4.0-rc1 built by myself

Code: Select all

[    2.115717] dwc3-meson-g12a ffe09000.usb: USB2 ports: 2
[    2.120552] dwc3-meson-g12a ffe09000.usb: USB3 ports: 1
[    2.128410] dwc2 ff400000.usb: ff400000.usb supply vusb_d not found, using dummy regulator
[    2.133948] dwc2 ff400000.usb: ff400000.usb supply vusb_a not found, using dummy regulator
[    2.142210] dwc2 ff400000.usb: Controller does not support host mode.
[    2.148569] dwc2: probe of ff400000.usb failed with error -22
[    2.154385] dwc3 ff500000.usb: Failed to get clk 'ref': -2
[    2.159680] dwc3 ff500000.usb: IRQ host not found
[    2.164277] dwc3 ff500000.usb: IRQ dwc_usb3 not found
However, no error with pwm-regulator

Code: Select all

~ dmesg | grep "pwm-regulator" 
[    0.479103] pwm-regulator: supplied by regulator-dummy
[    0.479407] pwm-regulator: supplied by regulator-dummy

surfbluecrab
Posts: 9
Joined: Thu Oct 03, 2019 4:32 pm
languages_spoken: english, french
ODROIDs: ODROID-N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Any plan for basic mainline linux support?

Unread post by surfbluecrab » Thu Oct 10, 2019 3:48 pm

Is this your private repository?

If so what is the address?
tobetter wrote:
Wed Oct 09, 2019 5:52 am
I've updated my repository for mainline 5.4.0-rc2 as well as 5.3.5 and had a quick test if they can boot up, not done a reliable test.

You can use one of these commands in order to install the kernel on my Debian/Ubuntu image.

Code: Select all

$ sudo apt installl linux-image-5.3.5-odroid-upstream-arm64

Code: Select all

$ sudo apt install linux-image-5.4.0-rc2-odroid-upstream-arm64
@elatllat, do you also have this error message with 5.4.0-rc2 kernel?

Code: Select all

[    0.632930] dwc3 ff500000.usb: Failed to get clk 'ref': -2
[    0.633007] dwc3 ff500000.usb: IRQ host not found
[    0.637637] dwc3 ff500000.usb: IRQ dwc_usb3 not found
[    1.253830] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517

User avatar
rooted
Posts: 6773
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 219 times
Been thanked: 41 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by rooted » Thu Oct 10, 2019 4:23 pm

surfbluecrab wrote:Is this your private repository?

If so what is the address?
tobetter wrote:
Wed Oct 09, 2019 5:52 am
I've updated my repository for mainline 5.4.0-rc2 as well as 5.3.5 and had a quick test if they can boot up, not done a reliable test.

You can use one of these commands in order to install the kernel on my Debian/Ubuntu image.

Code: Select all

$ sudo apt installl linux-image-5.3.5-odroid-upstream-arm64

Code: Select all

$ sudo apt install linux-image-5.4.0-rc2-odroid-upstream-arm64
@elatllat, do you also have this error message with 5.4.0-rc2 kernel?

Code: Select all

[    0.632930] dwc3 ff500000.usb: Failed to get clk 'ref': -2
[    0.633007] dwc3 ff500000.usb: IRQ host not found
[    0.637637] dwc3 ff500000.usb: IRQ dwc_usb3 not found
[    1.253830] pwm-regulator regulator-vddcpu-a: Failed to get PWM: -517
Pretty sure it's here:

https://github.com/tobetter/linux/tree/stable-v5.3
These users thanked the author rooted for the post:
surfbluecrab (Fri Oct 11, 2019 2:41 pm)

mxmilkb
Posts: 12
Joined: Fri Apr 26, 2019 9:28 am
languages_spoken: English
ODROIDs: N2
Has thanked: 8 times
Been thanked: 4 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by mxmilkb » Fri Oct 11, 2019 2:06 am

I tried the Arch ARM linux-aarch64 5.3.5 and linux-aarch64-rc 5.4-rc2 but no change. Someone in the Arch IRC suggested it could be a kernel/memory overlap issue and to check UART output but I don't have a UART USB adapter (yet). I don't think the Arch ARM maintainer is in the IRC though they are regularly committing. The Arch ARM forum registration is appears broken. Strit of Manjaro ARM said they hadn't had any UART from the N2 yet, though had tried the linux-vim3 and gotten UART output of "Image is not a FDT...".. There's also uboot-odroid-n2 and uboot-odroid-n2-mainline packages, from Manjaro not Arch, the latter from more recent testing. I hadn't tried these before yesterday but no change. There's no git web interface for Manjaro PKGBUILDs, and they've a forum for an issue tracker, both of which make things slightly confusing.

I'm going to put this on the shelf in my mind again for a while, but if anyone might wish to recruit way more testers, as well as bag/unblock one (and, in turn, two) official rolling release distros with monthly image releases from third parties, then discerning and resolving the gap in the Arch ARM mainline kernel PKGBUILD between mainline-mainline and N2-mainline would be my recommendation.
These users thanked the author mxmilkb for the post:
surfbluecrab (Fri Oct 11, 2019 2:42 pm)

Toggleton
Posts: 4
Joined: Mon May 27, 2019 5:39 pm
languages_spoken: english
ODROIDs: c2, N2
Has thanked: 0
Been thanked: 3 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by Toggleton » Sun Oct 13, 2019 12:42 am

mxmilkb wrote:
Fri Oct 11, 2019 2:06 am
There's no git web interface for Manjaro PKGBUILDs, and they've a forum for an issue tracker, both of which make things slightly confusing.
https://gitlab.manjaro.org/manjaro-arm/packages there is not every package but it is a start. Yes the way of manjaro is confusing

I do myself try to get mainline running on Archlinuxarm but i have the same Problem no UART yet and the 5.4.rc2-1 in a Bootloop. But will try with if the next RCs will fix that.
These users thanked the author Toggleton for the post:
mxmilkb (Mon Oct 14, 2019 3:51 am)

bas25
Posts: 6
Joined: Sun Sep 24, 2017 2:25 am
languages_spoken: english
ODROIDs: odroid c2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Any plan for basic mainline linux support?

Unread post by bas25 » Sun Oct 13, 2019 8:31 pm

Hi all,

i try reading the state of gpioX.2 (#478) on pin 22.
i've export this pin on sysfs (echo 478 > /sys/class/gpio/export) but the value stay at 0, although the voltage is near 3.3V.

is the pin mapping different on mainline kernel as what is indicated on the hardkernel wiki page ?

brad
Posts: 978
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 16 times
Been thanked: 37 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by brad » Sun Oct 13, 2019 10:24 pm

bas25 wrote:
Sun Oct 13, 2019 8:31 pm
Hi all,

i try reading the state of gpioX.2 (#478) on pin 22.
i've export this pin on sysfs (echo 478 > /sys/class/gpio/export) but the value stay at 0, although the voltage is near 3.3V.

is the pin mapping different on mainline kernel as what is indicated on the hardkernel wiki page ?
yes believe mainline is different to amlogic based kernel. Try 67.

See here for reference https://git.kernel.org/pub/scm/linux/ke ... 12a-gpio.h

bas25
Posts: 6
Joined: Sun Sep 24, 2017 2:25 am
languages_spoken: english
ODROIDs: odroid c2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Any plan for basic mainline linux support?

Unread post by bas25 » Sun Oct 13, 2019 11:58 pm

brad wrote:
Sun Oct 13, 2019 10:24 pm
bas25 wrote:
Sun Oct 13, 2019 8:31 pm
Hi all,

i try reading the state of gpioX.2 (#478) on pin 22.
i've export this pin on sysfs (echo 478 > /sys/class/gpio/export) but the value stay at 0, although the voltage is near 3.3V.

is the pin mapping different on mainline kernel as what is indicated on the hardkernel wiki page ?
yes believe mainline is different to amlogic based kernel. Try 67.

See here for reference https://git.kernel.org/pub/scm/linux/ke ... 12a-gpio.h
thanks for your answer,
"echo 67 > /sys/class/gpio/export" didn't work : "write error: Invalid argument"

"gpioget gpiochip0 67" did the trick.
it's time switching to libgpiod !
These users thanked the author bas25 for the post:
odroid (Mon Oct 14, 2019 9:41 am)

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Tue Oct 15, 2019 10:20 am

Last edited by elatllat on Fri Oct 18, 2019 9:42 pm, edited 1 time in total.

bas25
Posts: 6
Joined: Sun Sep 24, 2017 2:25 am
languages_spoken: english
ODROIDs: odroid c2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Any plan for basic mainline linux support?

Unread post by bas25 » Wed Oct 16, 2019 6:08 pm

Hi,
my gpio status update.

thanks to brad, i can read or write value on different gpio using libgpiod.
For exemple "gpioset gpiochip0 66=0 ", "gpioget 0 61" works normaly.
the problem comes with gpiomon wich return an error :
> gpiomon gpiochip0 61
> gpiomon: error waiting for events: No such device

in sysfs gpio interface, i can export some pin, but :
-> there is no edge file
-> the value file don't do anything

i think it's a common problem with sysfs gpio interface not working.
any idea ?

SirZevo
Posts: 3
Joined: Tue Sep 17, 2019 4:17 pm
languages_spoken: English and Spanish
ODROIDs: ODROID-N2
Has thanked: 2 times
Been thanked: 1 time

Re: Any plan for basic mainline linux support?

Unread post by SirZevo » Thu Oct 17, 2019 3:49 am

SirZevo wrote:
Tue Sep 17, 2019 4:26 pm
elatllat wrote:
Tue Sep 17, 2019 7:42 am
"meson-g12b-odroid-n2 USB fix" should be fine.
This fix should not be called any odroid-n2 related as it most likely affect other g12b devices as well.
meson-g12b USB fix
disable park mode for meson-g12b - USB fix
meson-g12b xHCI - disable park mode
meson-g12b xHCI - disable park mode to prevent halt
I mean, the possibilities are endless and the fix might apply for other Amlogic g12b devices
The USB3.0 interface issue for Amlogic G12A/G12B/SM1 SoCs has finally been sent to mainline by Neil Armstrong after elatllat reported it :)

Patchwork - Linux Amlogic - arm64: g12-common: parkmode_disable_ss_quirk on DWC3 controller
These users thanked the author SirZevo for the post:
xabolcs (Mon Oct 21, 2019 11:47 pm)

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Fri Oct 18, 2019 10:38 pm

These users thanked the author elatllat for the post (total 2):
rooted (Sat Oct 19, 2019 10:56 am) • xabolcs (Mon Oct 21, 2019 11:47 pm)

woodyl
Posts: 16
Joined: Mon Aug 05, 2019 2:04 am
languages_spoken: english
ODROIDs: Odroid N2
Has thanked: 3 times
Been thanked: 0
Contact:

Re: Any plan for basic mainline linux support?

Unread post by woodyl » Fri Oct 25, 2019 10:37 pm

I'm running Arch Linux Arm using the 4.9 kernel and Petitboot. I saw that the new kernel installation includes a new u-boot. If I upgrade to the latest mainline kernel, will I need to replace Petitboot? Do I need to change some boot parameters in firmware after I update?

User avatar
tobetter
Posts: 4123
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 48 times
Been thanked: 213 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by tobetter » Sat Oct 26, 2019 12:00 am

woodyl wrote:
Fri Oct 25, 2019 10:37 pm
I'm running Arch Linux Arm using the 4.9 kernel and Petitboot. I saw that the new kernel installation includes a new u-boot. If I upgrade to the latest mainline kernel, will I need to replace Petitboot? Do I need to change some boot parameters in firmware after I update?
Petitboot itself include HK stock U-boot (v2015.01), the U-boot updated in the eMMC or uSD with new kernel won't be affected at all. Petitboot will only take care of new kernel.
These users thanked the author tobetter for the post:
woodyl (Sat Oct 26, 2019 1:27 am)

ASword
Posts: 194
Joined: Fri Aug 04, 2017 12:48 pm
languages_spoken: english
ODROIDs: XU4, HC1, 2x N2
Has thanked: 5 times
Been thanked: 3 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by ASword » Sat Oct 26, 2019 12:25 am

There doesn't happen to be a "N-2 mainline kernel status" tracking page or document somewhere, does there? Trolling through this thread is interesting, but it is very hard to get a good picture of what the current reality of mainine on N-2 is... and it seems to change daily. I'm sure a lot of people would like to be able to track how things are going so they can get a sense of when using it for their device might start to make sense.
These users thanked the author ASword for the post (total 2):
woodyl (Sat Oct 26, 2019 1:26 am) • mxmilkb (Sat Oct 26, 2019 1:38 am)

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Sat Oct 26, 2019 1:22 am

ASword wrote:
Sat Oct 26, 2019 12:25 am
... "N-2 mainline kernel status"...
OK let's make one;

- 5.5
- + temperature sensors
- + crypto driver
- + more
- 5.4
- - some irq/pwm warnings in dmesg
- + DVFS
- + audio support
- 5.3
- - patch to fix USB+NIC crashing
- - crypto speed is 1/2 of 4.9
- - no 4K H.265 decoder
- 5.2
- - no support

We can move it to the OP or a wiki so it's findable.
Last edited by elatllat on Mon Oct 28, 2019 9:17 pm, edited 1 time in total.
These users thanked the author elatllat for the post (total 2):
woodyl (Sat Oct 26, 2019 1:27 am) • mxmilkb (Sat Oct 26, 2019 1:36 am)

chewitt
Posts: 15
Joined: Mon Aug 12, 2019 12:27 pm
languages_spoken: english
Has thanked: 0
Been thanked: 8 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by chewitt » Sat Oct 26, 2019 1:27 am

http://linux-meson.com/doku.php <= is maintained by the kernel maintainers. It's not specific to N2, but then the N2 is "just another G12B device" from a kernel perspective.

The major WIP is on video. Now that the kernel V4L2 stateful API is documented the vdec drivers are being adjusted for compliance and some firmware corrections will be published too, and this will necessitate ffmpeg and other things being adjusted. HDR is almost working (although 8-bit for now) .. still some way to go though :)
These users thanked the author chewitt for the post (total 2):
elatllat (Sat Oct 26, 2019 1:34 am) • rooted (Sat Oct 26, 2019 6:05 am)

ASword
Posts: 194
Joined: Fri Aug 04, 2017 12:48 pm
languages_spoken: english
ODROIDs: XU4, HC1, 2x N2
Has thanked: 5 times
Been thanked: 3 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by ASword » Sun Oct 27, 2019 1:52 am

That's a helpful link, thanks. It would very helpful to understand what the delta between the hardkernel 4.x latest and the mainline is. What is missing is often just as important.

User avatar
memeka
Posts: 4369
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 1 time
Been thanked: 39 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by memeka » Sun Oct 27, 2019 9:32 am

ASword wrote:
Sun Oct 27, 2019 1:52 am
That's a helpful link, thanks. It would very helpful to understand what the delta between the hardkernel 4.x latest and the mainline is. What is missing is often just as important.
Take hk 4.9 and compare with mainline 4.9. You’ll get only few thousand commits :)

ASword
Posts: 194
Joined: Fri Aug 04, 2017 12:48 pm
languages_spoken: english
ODROIDs: XU4, HC1, 2x N2
Has thanked: 5 times
Been thanked: 3 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by ASword » Sun Oct 27, 2019 10:31 am

memeka wrote:
Sun Oct 27, 2019 9:32 am
ASword wrote:
Sun Oct 27, 2019 1:52 am
That's a helpful link, thanks. It would very helpful to understand what the delta between the hardkernel 4.x latest and the mainline is. What is missing is often just as important.
Take hk 4.9 and compare with mainline 4.9. You’ll get only few thousand commits :)
Heh, yeah... my point exactly. :roll:

brad
Posts: 978
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 16 times
Been thanked: 37 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by brad » Mon Oct 28, 2019 8:58 pm

memeka wrote:
Sun Oct 27, 2019 9:32 am
Take hk 4.9 and compare with mainline 4.9. You’ll get only few thousand commits :)
Hi memeka, havent seen you for a while hope you been having fun, how is the bubs?

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Tue Oct 29, 2019 10:14 pm

These users thanked the author elatllat for the post (total 2):
rooted (Wed Oct 30, 2019 7:57 am) • emk2203 (Wed Oct 30, 2019 11:35 pm)

User avatar
emk2203
Posts: 41
Joined: Fri Oct 16, 2015 12:29 am
languages_spoken: english, german
ODROIDs: C1+, C2, XU4, HC1, HC2, N2
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Any plan for basic mainline linux support?

Unread post by emk2203 » Wed Oct 30, 2019 11:35 pm

Thanks! As expected, worked also on Armbian 5.38 without issues.

One thing I noted: There's an error message fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0 coming up in the syslog 360 times, I guess before it get's suppressed. At the start, there's also axg-sound-card sound: ASoC: no DMI vendor name!. Are both issues because of the lack of proper audio support scheduled for 5.4? The known issue with dwc3 ff500000.usb: Failed to get clk 'ref': -2 was audio as well if I read this right.

Looking forward to 5.4 now!

congo
Posts: 6
Joined: Fri Oct 11, 2019 5:04 pm
languages_spoken: english
ODROIDs: N2
Has thanked: 1 time
Been thanked: 0
Contact:

Re: Any plan for basic mainline linux support?

Unread post by congo » Wed Oct 30, 2019 11:52 pm

emk2203 wrote:
Wed Oct 30, 2019 11:35 pm
Thanks! As expected, worked also on Armbian 5.38 without issues.

One thing I noted: There's an error message fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0 coming up in the syslog 360 times, I guess before it get's suppressed. At the start, there's also axg-sound-card sound: ASoC: no DMI vendor name!. Are both issues because of the lack of proper audio support scheduled for 5.4? The known issue with dwc3 ff500000.usb: Failed to get clk 'ref': -2 was audio as well if I read this right.

Looking forward to 5.4 now!
This is in 5.4.rc5 as well . This happens when alsa/pulseaudio tries to access the "sound device"

User avatar
memeka
Posts: 4369
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 1 time
Been thanked: 39 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by memeka » Thu Oct 31, 2019 4:02 am

brad wrote:
Mon Oct 28, 2019 8:58 pm
memeka wrote:
Sun Oct 27, 2019 9:32 am
Take hk 4.9 and compare with mainline 4.9. You’ll get only few thousand commits :)
Hi memeka, havent seen you for a while hope you been having fun, how is the bubs?
Just been lurking mostly, waiting for more patches to hit mainline and a LTS to come along :)
All is good with the little ones :)

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Thu Nov 07, 2019 12:36 am

.


5.3.9 (lkml)
5.4-rc6 (lkml)
builds (and script).




erm67 wrote:
Sun Oct 06, 2019 6:53 pm
...include the uas module?...
I enabled UAS which works for regular file system use but is still not compatible with smartctl on seagate enclosures;

Code: Select all

smartctl -q noserial -r ioctl,2 -d sat -i /dev/sdb
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-5.3.9-dirty] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org


REPORT-IOCTL: Device=/dev/sdb Command=IDENTIFY DEVICE
 Input:   FR=...., SC=0x01, LL=...., LM=...., LH=...., DEV=...., CMD=0xec IN
 [ata pass-through(16): 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 ]
  scsi_status=0x2, host_status=0x0, driver_status=0x8
  info=0x1  duration=0 milliseconds  resid=0
  Incoming data, len=512 [only first 256 bytes shown]:
 00     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 10     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 20     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 30     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 40     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 50     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 60     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 70     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 80     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 90     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 a0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 b0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 c0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 d0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 e0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 f0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
  >>> Sense buffer, len=18:
 00     70 00 05 00 00 00 00 0a  00 00 00 00 24 00 00 00
 10     00 00
  status=2: sense_key=5 asc=24 ascq=0
sat_device::ata_pass_through: scsi error: unsupported field in scsi command
REPORT-IOCTL: Device=/dev/sdb Command=IDENTIFY DEVICE returned -1 errno=5 [scsi error unsupported field in scsi command]

===== [IDENTIFY DEVICE] DATA START (BASE-16) =====
000-015: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
016-031: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
032-047: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
048-063: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
064-079: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
080-095: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
096-111: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
112-127: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
128-143: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
144-159: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
160-175: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
176-191: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
192-207: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
208-223: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
224-239: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
240-255: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
256-271: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
272-287: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
288-303: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
304-319: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
320-335: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
336-351: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
352-367: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
368-383: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
384-399: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
400-415: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
416-431: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
432-447: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
448-463: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
464-479: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
480-495: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
496-511: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
===== [IDENTIFY DEVICE] DATA END (512 Bytes) =====


REPORT-IOCTL: Device=/dev/sdb Command=IDENTIFY PACKET DEVICE
 Input:   FR=...., SC=0x01, LL=...., LM=...., LH=...., DEV=...., CMD=0xa1 IN
 [ata pass-through(16): 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 a1 00 ]
  scsi_status=0x2, host_status=0x0, driver_status=0x8
  info=0x1  duration=0 milliseconds  resid=0
  Incoming data, len=512 [only first 256 bytes shown]:
 00     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 10     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 20     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 30     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 40     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 50     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 60     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 70     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 80     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 90     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 a0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 b0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 c0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 d0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 e0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 f0     00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
  >>> Sense buffer, len=18:
 00     70 00 05 00 00 00 00 0a  00 00 00 00 24 00 00 00
 10     00 00
  status=2: sense_key=5 asc=24 ascq=0
sat_device::ata_pass_through: scsi error: unsupported field in scsi command
REPORT-IOCTL: Device=/dev/sdb Command=IDENTIFY PACKET DEVICE returned -1 errno=5 [scsi error unsupported field in scsi command]

===== [IDENTIFY PACKET DEVICE] DATA START (BASE-16) =====
000-015: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
016-031: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
032-047: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
048-063: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
064-079: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
080-095: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
096-111: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
112-127: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
128-143: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
144-159: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
160-175: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
176-191: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
192-207: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
208-223: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
224-239: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
240-255: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
256-271: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
272-287: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
288-303: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
304-319: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
320-335: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
336-351: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
352-367: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
368-383: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
384-399: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
400-415: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
416-431: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
432-447: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
448-463: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
464-479: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
480-495: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
496-511: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
===== [IDENTIFY PACKET DEVICE] DATA END (512 Bytes) =====

Read Device Identity failed: scsi error unsupported field in scsi command

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Looks like there might be a workaround;
https://www.smartmontools.org/ticket/971#comment:12
These users thanked the author elatllat for the post:
erm67 (Sat Nov 09, 2019 8:02 am)

nom_nom
Posts: 3
Joined: Thu Nov 07, 2019 10:41 pm
languages_spoken: english
ODROIDs: n2
Has thanked: 0
Been thanked: 0
Contact:

Re: Any plan for basic mainline linux support?

Unread post by nom_nom » Thu Nov 07, 2019 11:03 pm

Is it possible to use mainline u-boot on eMMC?

I can compile both http://denx.de/u-boot/u-boot and https://github.com/150balbes/Amlogic_S9 ... ee/2019-n2 and sure enough they work on an SD card. They will even boot up a USB.

But I have no such luck with an eMMC, it fails as follows:

Code: Select all

** No partition table - mmc 1 **
When I should see something like this, when booting from the SD

Code: Select all

Switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
883 bytes read in 3 ms (287.1 KiB/s)
1:      NixOS - Default
My objective is to use extlinux/extlinux.conf for use with nixos.

Below I've tried to summarise what I am doing in as few steps as possible.

Code: Select all

# 1. Create the partition table for the emmc and add u-boot, inspired by `packages/bsp/aml-g12/install.sh`

```
DEV_EMMC="/dev/mmcblk0"
dd if=/dev/zero of="${DEV_EMMC}" bs=1M count=4
sync
parted -s "${DEV_EMMC}" mklabel msdos
parted -s "${DEV_EMMC}" mkpart primary fat32 700M 828M
parted -s "${DEV_EMMC}" mkpart primary ext4 829M 100%
```

# 2a. Add u-boot

```
dd if=nixpkgs_extra/u-boot-armbian-2019_10.bin of="${DEV_EMMC}" conv=fsync bs=1 count=442
dd if=nixpkgs_extra/u-boot-armbian-2019_10.bin of="${DEV_EMMC}" conv=fsync bs=512 skip=1 seek=1
sync
```

> u-boot does not start

# 2b. Add u-boot

```
dd if=nixpkgs_extra/u-boot-armbian-2019_10.bin of="${DEV_EMMC}" conv=fsync bs=512 seek=1
sync
```

# 3. Reboot without SD

If step 2a. is performed u-boot does not start

if step 2b. is performed u-boot will start but reports `>> ** No partition table - mmc 1 **`


# 4. Mount and identify the partition to `dd` to the mmc

```
fdisk -l odroid-n2-20.03pre196811.7818f30cc4b-aarch64-linux.img
mkdir nixos
mount -o loop,offset=$((512*77824)) odroid-n2-20.03pre196811.7818f30cc4b-aarch64-linux.img nixos
```

# 5. Copy the root partition to the emmc
```
dd if=/dev/loop0 of=/dev/mmcblk0p1 bs=1M
sync
```

elatllat
Posts: 1573
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 24 times
Been thanked: 64 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by elatllat » Thu Nov 07, 2019 11:40 pm

> dd if=nixpkgs_extra/u-boot-armbian-2019_10.bin of="${DEV_EMMC}" conv=fsync bs=1 count=442

would have undone

> parted -s "${DEV_EMMC}" mklabel msdos

I think there is an example sh in https://github.com/hardkernel/u-boot/releases that should help you.

using only "bs=512 seek=1" looks more likely to be correct.

chewitt
Posts: 15
Joined: Mon Aug 12, 2019 12:27 pm
languages_spoken: english
Has thanked: 0
Been thanked: 8 times
Contact:

Re: Any plan for basic mainline linux support?

Unread post by chewitt » Fri Nov 08, 2019 12:14 am

I've run mainline u-boot on an N2 for some time and it works fine with the simple extlinux.conf packaging that LE uses. Some bits that might be useful:

https://github.com/BayLibre/u-boot/releases/ <= fip binaries for N2 can be had from here
https://github.com/chewitt/LibreELEC.tv ... er/install <= u-boot fip recipe
https://github.com/chewitt/LibreELEC.tv ... er/mkimage <= content for boot partition (prob. a bit LE specific)
https://github.com/chewitt/LibreELEC.tv ... package.mk <= u-boot package build

Post Reply

Return to “General Topics”

Who is online

Users browsing this forum: No registered users and 12 guests