norgo wrote:I patched slacko-700-RC3_k4.4.70-PAE_2018-04-05.iso by the changes of commit d553a8c for test.
wdlkmpx you are awesome !
I 've replaced with this and now Puppy knows about the pkeys from the kernel options. So that works well.
I am also running the slacko64 from Sailor on this dualcore PC. I've lost the keyboard and the mouse twice now. First time I reinstalled, but I did not keep the pupsave. Second time I have kept the pupsave; I can drag out some logs if someone wants them to look at it.
Beginning of april I've also reported trouble with be-latin1 on this PC and UpupBionic. In the end I reinstalled and further ignored it.
Maybe all this has to do with this commit d553a8c?
I've made a 64bit Slacko compatible 4.14.35 kernel via Puppy kernel-kit, with the no firmware option. Will need an fdrv for firmware. Is Spectre/Meltdown mitigated. Have swapped it into Slacko64 6.9.9.9 and LxpupSc64 18.03. Works ok in both.
See: http://murga-linux.com/puppy/viewtopic. ... 461#990461
I will have a go at my interpretation based on my experience with each. They are versions of Slacko64 6.9.9.9 using different kernels and with different browsers and features.
PM = Pale Moon, FF = Firefox, LO = Libre Office
The kernel versions are significant if you intend to compile additional software specific for that distribution beyond what was already provided.
Typically if you intend to simply use it as is then you are good to go. Otherwise if you intend further customization then you will need to know the specific kernel used to assemble the appropriate elements to compile software for additional utility.
Now as to the highly anticipated release of Slacko 7, well that is better answered by those diligently contributing their efforts to produce Slack 7.
I will have a go at my interpretation based on my experience with each. They are versions of Slacko64 6.9.9.9 using different kernels and with different browsers and features.
PM = Pale Moon, FF = Firefox, LO = Libre Office
The kernel versions are significant if you intend to compile additional software specific for that distribution beyond what was already provided.
Typically if you intend to simply use it as is then you are good to go. Otherwise if you intend further customization then you will need to know the specific kernel used to assemble the appropriate elements to compile software for additional utility.
Now as to the highly anticipated release of Slacko 7, well that is better answered by those diligently contributing their efforts to produce Slack 7.
Cheers to ya! Hope this helps a bit.
It did! and thanks! it makes sence
Kindly Gnimmelf
Anyone know if Micko is going to release a 2018 Slacko update to 700rc3 and/or Slacko64-700?
I know we've got Peebee's great Slacko LxPup versions, but I was just wondering if Micko's branch here has been officially declared dead??
A lot of stuff in Micko's 2017 Slacko 32/64 releases need updating, and not everyone is going to follow/download/install all the different posters' works/fixes who are valiantly trying to keep everything updated in these outdated 2017 releases.
I am also looking out with anticipation for a new slacko.
There are surely others:
In the 'woof-ce needs you' thread newer builds of slacko are offered. By Sailor, and one by norgo as well.
Testing one of these may help getting to a final version?
01micko seems to be doing very little in Puppy anymore, if anything.
I would say Slacko 7.0 is not going to happen, by him doing it.
Someone else needs to take over.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected YaPI(any iso installer)
Folks, the demands of producing a major puplet are immense. I've been on the forum (under current & previous nics) for 13 years & we see an oft repeated pattern - enthusiastic start, lots of output, lots of demands, lots of attempts to satisfy those, increasing bughunts/fixes, increasing pressure, then burnout & withdrawal, often after high personal cost. Mick has done what he could - and may get to again. Just hope he's OK.
Sailor Enceladus has produced some Slacko-current updates to 700rc3 if you want up-to-date stuff.
I use Peebee's LXPup18.03 (also based on 700rc3 & using Slacko-current). It's fantastic & more good stuff has followed, but I'm concerned he may be feeling the strain of his fruitful output.
watchdog wrote:Randomly the shutdown of slacko 700 RC3 fails. Did someone find an easy fix?
What do you mean? What build are you using exactly? What is your install?
I don't have any problem closing down with a frugal install of several Slacko's on hd and kernel option pmedia=usbflash.
Is the ext4 on the usb created by gparted in Puppy?
It's an external usb hd with many puppies in frugal installations. All puppies generally work on that hd. I do not remember when I setup it. I usually use gparted in a puppy to format hd's. It has grub4dos on its MBR. I can boot a puppy on it using plop boot manager and then grub4dos or grub4dos-grub2 from the main sda1 hd. Could it be a jwm bug related malfunction? I'm now experimenting a jwm upgrade.
watchdog wrote:Could it be a jwm bug related malfunction? I'm now experimenting a jwm upgrade.
Why do you think that?
Or Xorg? Do you have a graphic card? There is something with intel gc: http://www.murga-linux.com/puppy/viewto ... &start=390
Have you seen others report this problem? I haven't found any so far.
There was a bug in jwm when these builds were published. I'm using jwm 2.3.5 from xenialpup64 and until now the shutdown is ok.
That's the same reference as mine! I thought freezes occurred anytime in this case.
I haven't used the slackos of micko much. I found them not very solid (I expect stability from slacko! )
I use the more recent builds from Sailor (64bits) and norgo (32bits) from april. They should have a lot more fixes from woof CE.
Last edited by foxpup on Fri 31 Aug 2018, 17:18, edited 1 time in total.