Page 1 of 1

Xorg 10.14.7.R29 a.k.a., Asustor's Busted Beta

PostPosted: Mon Mar 13, 2017 2:30 pm
by Tarl Cabot
"Hory buggered betas, Batman!" I realize it's just a beta, but seriously Asustor? Your "engineers" published R29 without even checking if HDMI was still functional?

LOL! Nice job folks, keep up the great work!

As for any fellow users that got burned: If you lost HDMI after installing R29 and can't wait around for Asustor to fix their buggy code, you may want to try father.mande's roll-back instructions. But do so only if you are comfortable modifying critical root files. I tested the procedure on an AS5102T and it worked perfectly.

His instructions are here: viewtopic.php?f=72&t=8701&start=10#p27590

Cheers!

Re: Xorg 10.14.7.R29 a.k.a., Asustor's Busted Beta

PostPosted: Wed Mar 15, 2017 2:40 pm
by James.S@AST
Dear Tarl,

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

Re: Xorg 10.14.7.R29 a.k.a., Asustor's Busted Beta

PostPosted: Wed Mar 15, 2017 4:26 pm
by father.mande
Hi,
DELETED erroneous ...

Philippe.

Re: Xorg 10.14.7.R29 a.k.a., Asustor's Busted Beta

PostPosted: Wed Mar 15, 2017 4:44 pm
by orion
I think they solved this issue in Asustor Portal App, rather than xorg. (I cannot try it because my NAS is AS-304T whose xorg does not update.)

Re: Xorg 10.14.7.R29 a.k.a., Asustor's Busted Beta

PostPosted: Wed Mar 15, 2017 7:17 pm
by father.mande
Hi,

After updating Asportal to R1227 ... that also update Xorg (even without warning) to R29
... icon stay visible EVEN applications are disabled
ex. Vbox, VM_vbox, Plexmediaplayer

... changing Application status to Enable ... some applications don't start ... black screen ???

Reboot :

... status stay incoherent
applications are enable in AppCentral but not visible in Asportal
... disable / enable ... display it in Asportal (but each time asportal restart xorg reset it ??? fortunatly only one time (each) so not as previous

some applications (but not from Asustor) refuse to start ... don't use PlexMediaPlayer for ex. (even working before)
some other "virtualbox" freeze just after displaying their interface on screen ???
... only solution stop Virtualbox (or restart) (because no action possible (but I don't test all keys))
... BUT even now Enable ... and after a manual restart of asportal (to see) ... the virtualbox icon is NOT displayed ????

?????

I will try to continue some test ... but I work using a VPN at 1000 Kms of my NAS ... so a little difficult ...

Philippe.

Re: Xorg 10.14.7.R29 a.k.a., Asustor's Busted Beta

PostPosted: Wed Mar 15, 2017 7:56 pm
by father.mande
Hi,
Xorg R29 :
Just a (big) thanks to developer that move libraries or link from one place (in Xorg) to another one without assuming compatibility

Is it possible to do this by inadvertence ? ... except if it's a new policy to restrict other Asportal application to exist ... I don't think so :roll:

New version of PlexMediaPlayer is needed to workaround this change ... so not usable with new beta Asportal / Xorg for the moment ...
Philippe.

Re: Xorg 10.14.7.R29 a.k.a., Asustor's Busted Beta

PostPosted: Thu Mar 16, 2017 2:54 pm
by James.S@AST
Hi Philippe,
Sorry for not letting you know in advance about our changes on xorg R29 beta.
The new Xorg R29 upgraded the ffmpeg library version from 2.8.7 to 3.1.7 for KODI 17.0 and also change some library path.

After change the PlexMediaPlayer app, the libselinux.so.1, libpcre.so.3 arenot able to link after our changes.
You may add /usr/local/AppCentral/xorg/lib path in run_pmp.sh and it should work.

Thank you once again for providing the great apps for ASUSTOR NAS user.

Cheers,
JAMES

Re: Xorg 10.14.7.R29 a.k.a., Asustor's Busted Beta

PostPosted: Thu Mar 16, 2017 4:10 pm
by father.mande
Hi James,

I know the problem and the solution (please don't lost time to solve my APKG, I don't require this :lol: , normally I know how debugging my own project ) ... but building new version only to a change due to position of lib ... I always try without adding personal libraries to don't add more library path to avoid race condition ... due to delay added ...

BUT you are master in your castle ...

Also if you add and update ffmpeg to 3.1.7 ... I can suppress my APKG requested for serviio, (armhf and x86_64) ... but remember (sorry it's not my problem but) I will do port of kodi17 on other NAS (on Asustor only a stop gap game) ... using external ffmpeg is not the best way (my opinion) ... having the ffmpeg integrated lost a small space in memory but are sure to be coherent for each new version without changing ffmpeg each time (same for my own with plexmediaplayer where I don't use external ffmpeg but integrated (in pmp) version)

Philippe.

Re: Xorg 10.14.7.R29 a.k.a., Asustor's Busted Beta

PostPosted: Fri Mar 31, 2017 4:46 pm
by TheDoogy
Hi,

I can't save the screen resolution on my AS6204T with AS Portal 2.0.3.r1227 and X.Org 10.14.7.R29.
At each startup, the following screen resolution "std_1920x1080@60.00" is selected by default whereas I selected and saved ASUSTOR 4k during the previous session.

One more thing. It seems that this configuration is done for TVs that could have some problem of compatibility with asustor 4K resolution...
So, why no other regular 4K configuration is available ?

Thank you for your help.
Best regards,

Nicolas

Re: Xorg 10.14.7.R29 a.k.a., Asustor's Busted Beta

PostPosted: Fri Mar 31, 2017 5:21 pm
by orion
TheDoogy wrote:Hi,

I can't save the screen resolution on my AS6204T with AS Portal 2.0.3.r1227 and X.Org 10.14.7.R29.
At each startup, the following screen resolution "std_1920x1080@60.00" is selected by default whereas I selected and saved ASUSTOR 4k during the previous session.

One more thing. It seems that this configuration is done for TVs that could have some problem of compatibility with asustor 4K resolution...
So, why no other regular 4K configuration is available ?

Thank you for your help.
Best regards,

Nicolas

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