'ckb-next' From Updated PPM Not Running

[wiak]

There may be no easy 'resolution' for running this from FossaPup, whose PPM uses official Ubuntu repos but is not 100% compatible with what these repos provide. In particular, if this Ubuntu package is written to use systemd, then you indeed have a problem since FossaPup does not support systemd as an init system. Whilst it would of course be possible to get the package working with other init system that would require a dev to specifically work on that and have any hardware involved so no easy solution I think.

Well... there is probably an 'easy' forum-oriented solution - use a forum-available distro that is 100% compatible with the Ubuntu repos the package comes from. On this forum, that would be FossaDog64 (which I presume does support using systemd).

Alternatively, if same package is available from Void repos then use a distro that is pretty much 100% compatible with Void repos, which is KLV-Airedale64; Void's version probably expects runit (rather than systemd) and KLV-Airedale uses runit.

In other words if you need a way to get this programmed then use a Dog and not a Pup (even VoidPup probably won't help since that doesn't use runit - or does it(?), I can't remember, and temporarily don't have VoidPup installed because I ran out of space on my old machine). Otherwise, you will indeed need to hope someone works out how to get the package running without systemd on a Pup (may be possible without having the hardware to test), which seems to be a struggle. Is it possible to 'program' the keyboard on one distro (e.g. a Dog) such that it can then be used on another (a Puppy)?

[mikewalsh]

</snip>....Is it possible to 'program' the keyboard on one distro (e.g. a Dog) such that it can then be used on another (a Puppy)?

That's entirely possible.....IF manufacturers all use roughly the same methods for this kind of thing, i.e, an on-board ROM chip that can be 'modified' by remote software. It worked that way for me with a Logitech ZoneTouch T400 Mouse back during my first year with Puppy.

At the time, fortunately, I still had an XP install on the old Dell lappie. I needed to make some setting changes for the mouse to be 'usable' (it had a mini-touchpad, or 'stroke-strip', where other mice would normally have their scroll-wheel.....capable of all kinds of fancy tricks, but something of a bear if not set the way the user preferred). I downloaded the Logitech software for the mouse, installed it to the Dell, and set the mouse up to personal preferences. Ever afterwards, even with the Dell powered-off & packed away in a cupboard, the mouse continued to run, as previously set up, with every Puppy I tried it in.....indicating that something on-board WAS retaining settings - in all likelihood, a 'flashable' EEPROM of some kind, similar to your BIOS/UEFI chip.

--------------------------------------------

My betting is that the Corsair keyboard can be 'amenable' in much the same way. Install the 'icue' software in Windows & set it up the way you want it. With any luck, those settings will hold afterwards, regardless of what you use the keyboard with. But this IS one of the reasons I tend to research my hardware before purchase nowadays.....I've finally got out of the Windows mind-set that says 'Buy what you like.....it'll work!'

There's not much hardware that isn't supported by the kernel these days. The problem comes with manufacturer-supported 'specialist' software for specific items.....that's where you're likely to run into issues, as the OP has here. The basic hardware functionality WILL be present; fancy software 'modifications', not so much. And WINE won't necessarily be a solution, here; as I stated earlier in the thread, even as good as WINE has become, it still struggles with translating M$ hardware stack 'calls' to their Unix/Posix/Linux equivalents....

(I'll be interested to see how good the brand-new WINE 7.0 is in this respect. After over a year in the making, and nearly 11,000 code commit changes, it ought to offer SOME improvements. Maybe hardware stack "translation" will be one of those areas..? We shall see.)

Mike.

[Grey]

WINE 7.0

Yesterday I talked to Kron4ek about a bug in Conty. But most importantly, he posted his portable Wine 7.1. So you can try it.
I have been using these builds for several years. So far, they have never failed.
Many builds of Windows games for Linux have been made on their basis. The meaning there is that the game starts with a single click, and Wine is built in.

[Grey]

On the topic. The rockedge's method works. But somehow not every time...

Here is a more recent version 0.4.4 for Fossa (.deb). I tried to do .pet and even did. But I won't post it, because I didn't understand all the points.

Besides, I got sick today, maybe a known virus, or maybe the flu

[bigpuppyfan]

The main reason why the version found on the PPM is failing is because it was compiled on ubuntu, which has systemd. Puppy uses its own different manager.

Since I use puppy in RAM mode only, I don't mind installing and trying several things, for learning purposes. I've tried installing the ubuntu ckb-next package to look into it.
You can try the following workaround, designed to fool several programs into thinking systemd is present. (btw, the "real" systemd you have installed is probably not functional on puppy). Not sure if not working with me just because I don't have the hardware:

Code: Select all

wget https://raw.githubusercontent.com/gdraheim/docker-systemctl-replacement/master/files/docker/systemctl3.py -O /usr/local/bin/systemctl

Then make this file executable (right click the file on ROX, found at /usr/local/bin/systemctl - permissions - yes
And then

Code: Select all

systemctl start ckb-next-daemon
run-as-spot ckb-next

If that doesn't work, you can try compiling it for puppy. It seems the developers have had the consideration for several init daemons, including sysvinit:
Uninstall the previous version first. You'll then need to install the devx.sfs for your puppy version
Download https://github.com/ckb-next/ckb-next/ar ... 4.4.tar.gz and unzip it to some folder. On terminal, cd to that folder and:

Code: Select all

pkg get libxcb-ewmh-dev
pkg get libdbusmenu-qt5-2
pkg get libdbusmenu-qt5-dev
sh ./quickinstall

When it's done, confirm the new daemon is installed and start it:

Code: Select all

service --status-all
service ckb-next-daemon.sh start

And finally

Code: Select all

run-as-spot ckb-next

Should also be easy to find out and remove somewhere in the code, before compiling, the root check lines, so it can be run without root.

[MrDuckGuy]

The main reason why the version found on the PPM is failing is because it was compiled on ubuntu, which has systemd. Puppy uses its own different manager. ... Should also be easy to find out and remove somewhere in the code, before compiling, the root check lines, so it can be run without root.

Thank you.

I will try this. I've already returned that keyboard, but I still will try it. If I can get it working, I will post the result on this topic.