Why is Plasmac and QTplasmac pausing at the end of a cut for no reason?

rodw wrote:

Ok, had to use a wired keyboard to access the grub menu. Never been a problem before

I use a wireless one without issues.

around 20000 latency 
If only I still had a wifi card that worked.... would isolcpus break that?
Not sure how to debug that. Its always just worked before.

I don't know, I have two PC'c using WiFi but I don't have isolcpus.

I got it! Had to unblock a wifi driver and saw it start to auto connect
So how to make the RT the default boot and I'll be good!
I think It would have been quicker to compile the kernel! thanks for your help!

Well, I installed the Rt image with synaptic, rebooted, selected Advanced from the Grub menu then the correct image. The same way as most Debian based distros. Definitely quicker than compiling the kernel.

I broke the wifi somehow so I might end up reinstalling it now I have refreshed my memory. I uninstalled a driver because it was breaking apt-get which I think might have done that.

I also need to get the grub menu defaulting to preempt_rt. I was able to install grub_customiser that tommy used in his Mint install but the tool he used to do the grub menu. But it was a manual install as the progrm he used does not exisr.

I did get QTplasmac opening from  my earlier config and Gmocappy is operational. I still have a fair bit to do to get an operational qtplasmac config.

I have installed it on two PC's and several virtual machines on two iMacs and never had an issue with the rt kernel image. I just install the image with synaptic then reboot. When the Gub menu appears select Advanced Options then select the rt kernel image. It then uses that as the default kernel.

I think I have some to, I was going to tidy them up and post them but ...

I wouldn't say its hard, but not knowing what the name of the RT patch was in Synaptic extended the journey, Most of the rest comes down to your hardware. A wireless keyboard not working on the grub boot menu and a problematic wifi driver didn't help. I'm still not sure the touch screen came up. Normally, I install the hardware connected to a wired network, but this wasn't possible here.

My Asus VT168 works out of the box.

I am sure the RT kernels in all Debian based distros have similar name formats.