no HDMI output after upgrade to ADM2.7

[Tarl Cabot]

Hi,

is the problem only when Xorg beta was installed with new ADM2.7? So with the Xorg r22 no HDMI problem?

Yes, at least that's how it went down on my AS5102T... HDMI worked fine with ADM 2.7 and the old Xorg R22, but failed only after updating Xorg to the R29 beta.

Since I no longer run media apps on my Asustor pos, I decided to take one for the team and test HDMI incrementally between ADM and Xorg update combos to provide some insight on exactly when it would fail.

1) ADM 2.7.0BDB3 (beta) with old Xorg 10.14.7.R22 (stable) = HDMI OK
2) ADM 2.7.0.RF72 (stable) with old Xorg 10.14.7.R22 (stable) = HDMI OK
3) ADM 2.7.0.RF72 (stable) with new Xorg to 10.14.7.R29 (beta) = HDMI failed

I rebooted, tried adjusting Asustor Portal properties too, but with same outcome as described by the OP. The Initial boot processes display normally via the HDMI interface, so HDMI is working as it should at first, but then the display goes black at the point where the Asustor Portal screen should appear. Further, after about 30 seconds, my TV goes into stand-by mode, indicating a total loss of HDMI signalling; and as illustrated below, the Portal no longer recognizes the HDMI interface after updating Xorg to R29 beta.

Bottom line: If you need HDMI output , DO NOT UPDATE Xorg until this bug is fixed, and confirmed working by actual users.

LOL, wow, this is fubar even for an Asustor beta. Rather than these "world-class media servers," maybe Asustor should start selling whatever their QC engineers are smoking instead. Way more effective, and likely much happier customers too!

Cheers,

Portal error.jpg (27.65 KiB) Viewed 12231 times

[dkobelak]

thanks for the update! this is exactly what I had as well after testing.. ADM2.7 is ok but only with x.org r22 not the r29 beta..

[father.mande]

Hi,

Hi Philippe, would you explain a little bit more this procedure?
I tried updating control.json files without any success...
Thanks

First some remember :
NEVER use it if you don't understand exactly what you do
IF you use it ... be sure to have backup of your settings, config files and data ... or to be able to restart from a clean install ... if you fall in problems
This is first for beta tester and tester when developing application ... so always risky
This can be change (cancelled) by Asustor when they want

Last when you are sure ... verify one time more ...
in AppCentral disable applications linked to the APKG you want to change ... not mandatory ... but a good idea
... in all case this application will be disabled by the install procedure
be root (not admin)
cd /usr/builtin/etc/appcentral/
edit file installed.json (do a copy before in a safe place)
search for occurrence of the version (and package) you want to change
ex. xorg / 10.14.7.R29 (for beta Xorg)
change it (all occurrence be attention to perquisite even with beta or your own APKG it's less needed (you must know if you have added new APKG using the new version)
ex. if stable is 10.14.7.R22 ... use 10.14.7.R21 or R20
save file
open AppCentral ... normally your new "fake version" is displayed and due to the existence of a stable version R22 ... the update is proposed ... do the update (this disable APKG dependent of the uninstalled software, accept to disable it)
after update enable your application, starting in this case by Asportal, etc. etc.

I can't in ANY case recommend this ... it's your choice ... so be sure of what you do ...

the current method, uninstall (so all dependent applications are also uninstalled) ... then reinstall all ... and reconfigure work as well and are recommended for in-experimented users ... but normally this users don't tests beta version and wait up to stable ...

Philippe.
NB certainly an error to write previous post about this point ... apologize ... I really discuss as if I am in a beta forum dedicated to beta tests ...

[Maerlin]

Hi Philippe,

Don't be afraid, I won't consider you guilty of my mistakes
I suspected an external config / register file, it just that I could find it.
Anyway it seems to work, keep you posted.

Edit: confirmed. it worked. asportal back and running. thx for the trick.

[James.S@AST]

Dear All,

We just published the ASUSTOR Portal 2.0.3.R1227 for AS31/32/50/51/61/62/70 series to solve this issue.
Please update it via App Central--> Beta Apps section.
if the issue persists, please let me know.

Thank you,
JAMES

[methos]

I've tried it and it works well for me.

-Can anyone confirm if the portal update does the trick?

[dkobelak]

I've tried it and it works well for me.

-Can anyone confirm if the portal update does the trick?

yes, so far the new portal with new x.org has been working ok for me since the latest update..

[RMerlin]

Works for me as well, been using Kodi 17.0 with it.

[nymeron]

Hi!

Anyone still having this issue?

Because I have same problems even tough i have latest versions.

I have AS3102T with latest ADM 3.1.3 RHU2.
X.Org version is 10.14.7.R35
ASUSTOR Portal version is 2.2.4.r1213

Is there any solution for this?

AS3102T_issue.PNG (74.47 KiB) Viewed 10384 times

[orion]

Hi!

Anyone still having this issue?

Because I have same problems even tough i have latest versions.

I have AS3102T with latest ADM 3.1.3 RHU2.
X.Org version is 10.14.7.R35
ASUSTOR Portal version is 2.2.4.r1213

Is there any solution for this?

I think you'd better to send a support request to asustor to check it. https://support.asustor.com/