See my post #204 in this MX18 beta1 thread.
I am still fighting the Ryzen crash/reboot at idle problem.
From caprea's comments, and Pauls trials, I am trying to install the 4.19-antix.1 kernel with the MX Package installer.
But I get the errors in the #204 post, so I cannot try that kernel.
1. Any ideas why the MXPI did not install the kernel? I updated both MX 17.1 and 18 grubs.
Are my repositories messed up? I do have the dev repo enables (to get the nvidia driver-which worked).
2. Or can I some how install another parameter at grub time to make the rcu-nocbs=0-11 fix work in the MX kernel?
That may be this line...
CONFIG_RCU_NOCB_CPU=y
MX-18 beta 1 feedback
- entropyfoe
- Posts: 615
- Joined: Thu Apr 19, 2007 11:42 am
Re: MX-18 beta 1 feedback-MXPI not installing kernel
MX 23.5 on Asus PRIME X470-PRO
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound
Re: MX-18 beta 1 feedback-MXPI not installing kernel
I might have missed something. If you are referring to the timeout "Could not connect to iso.mxrepo.com",entropyfoe wrote: Fri Dec 07, 2018 10:02 am See my post #204 in this MX18 beta1 thread.
But I get the errors in the #204 post, so I cannot try that kernel.
1. Any ideas why the MXPI did not install the kernel? I updated both MX 17.1 and 18 grubs.
Are my repositories messed up? I do have the dev repo enables (to get the nvidia driver-which worked).
then the answer is simple: In such cases just select another repo-mirror with MX Repo Manager.
You might either select manually or try to select fastest. Note the later selection will only check the server is up,
but will not check the functionality to work properly as repo-server.
Having a pool of repo-mirrors is not only in respect of download bandwidth but also to cater for the case
if one repo is temporarily not available, which can happen.
BTW, meanwhile iso.mxrepo.com should be back again.

Re: MX-18 beta 1 feedback
OK, I can see having to have MXUM running in parallel with other apps, so I think it's a good suggestion to make it run with disown, for the rest of the apps I think I prefer the way it works now, meaning there's a clear workflow, you press on Teaks you do your teaks, finish with that and close it, Welcome screen comes back on.skidoo wrote: Fri Dec 07, 2018 2:10 am Quick access to MX User Manual is a standout feature. IIRC, what tripped me up while wearing my "noob user" tester hat:
When MXUM is launched from the welcome dialog, the welcome dialog autohides (and no taskbar item for it).
Please consider using nohup or disown in the Welcome--}MXUM launchstring, as well as for a select few other launchers presented within the Welcome dialog.
Re: MX-18 beta 1 feedback
I support skiddo's proposal.Adrian wrote: Fri Dec 07, 2018 10:55 amOK, I can see having to have MXUM running in parallel with other apps, so I think it's a good suggestion to make it run with disown, for the rest of the apps I think I prefer the way it works now, meaning there's a clear workflow, you press on Teaks you do your teaks, finish with that and close it, Welcome screen comes back on.skidoo wrote: Fri Dec 07, 2018 2:10 am Quick access to MX User Manual is a standout feature. IIRC, what tripped me up while wearing my "noob user" tester hat:
When MXUM is launched from the welcome dialog, the welcome dialog autohides (and no taskbar item for it).
Please consider using nohup or disown in the Welcome--}MXUM launchstring, as well as for a select few other launchers presented within the Welcome dialog.


Re: MX-18 beta 1 feedback
OK, fine, I wanted to avoid something like this:fehlix wrote: Fri Dec 07, 2018 11:05 amI support skiddo's proposal.Adrian wrote: Fri Dec 07, 2018 10:55 amOK, I can see having to have MXUM running in parallel with other apps, so I think it's a good suggestion to make it run with disown, for the rest of the apps I think I prefer the way it works now, meaning there's a clear workflow, you press on Teaks you do your teaks, finish with that and close it, Welcome screen comes back on.skidoo wrote: Fri Dec 07, 2018 2:10 am Quick access to MX User Manual is a standout feature. IIRC, what tripped me up while wearing my "noob user" tester hat:
When MXUM is launched from the welcome dialog, the welcome dialog autohides (and no taskbar item for it).
Please consider using nohup or disown in the Welcome--}MXUM launchstring, as well as for a select few other launchers presented within the Welcome dialog.Remember, newbies don't have a workflow, they want to look around first. A disappearance of the Welcome screen is rather irritating, not only for newbies for me too.
![]()

Re: MX-18 beta 1 feedback
Understand. It might be less irritating keeping the Welcom screen up, then this disappearing and suddenly appearing again.Adrian wrote: Fri Dec 07, 2018 11:13 amOK, fine, I wanted to avoid something like this:fehlix wrote: Fri Dec 07, 2018 11:05 amI support skiddo's proposal.Adrian wrote: Fri Dec 07, 2018 10:55 am
OK, I can see having to have MXUM running in parallel with other apps, so I think it's a good suggestion to make it run with disown, for the rest of the apps I think I prefer the way it works now, meaning there's a clear workflow, you press on Teaks you do your teaks, finish with that and close it, Welcome screen comes back on.Remember, newbies don't have a workflow, they want to look around first. A disappearance of the Welcome screen is rather irritating, not only for newbies for me too.
![]()
[/url]
It's now kind of/like Whisker-menu disappears when clicking an app, but suddenly from nowhere it appears again.
Re: MX-18 beta 1 feedback
I would find leaving the Welcome screen up annoying.
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: MX-18 beta 1 feedback
You are not newbie

Re: MX-18 beta 1 feedback
I think after a week of use a newbie would find it annoying. Just an opinion and not verifiable. I see nothing wrong with the current setup. For quick access put MX Welcome in Favorites.
EDIT: By the way MX Tools works the same way.
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: MX-18 beta 1 feedback
... probably rarely open the Welcome screen anyway, if at all. :lipsrsealed: