Yeah, in night I tried to play Diablo with wine under Knoppix 8.6 - kernel 5.2.26. It was disappointment comparing to my experience with Knoppix 8.2. Something is wrong - I dont know what. But maybe there is no need to be in hurry to switch to 5. brand kernel. Xorg terrible failed - blank screen with unresponsive keyboard - seems it was screen issue - possibly. Boot command knoppix 2 - which starts system without X server - just hangs. So let be careful instead of sorry.

In what you wrote nothing links to Slackware.

I rely on my intuition. If something worries me it means it is worrisome. It just should not happen. Problem is: look for reason. Who or what to blame? If who - then there is no problem. If what - there is a problem which can possibly influence all distributions including Slackware.

Anyway Slackware doesn't and certainly won't ever ship a 5.2 kernel as this branch is EOL, so if there is an issue with the kernel you mention it most probably won't influence Slackware.

PS I suggest that you report issues with Knoppix on a Knoppix support channel, as that could help solve them.

1 members found this post helpful.

Can you check Diablo with Wine in Slackware with Kernel 5.2.26 and see if this runs smoothly?

Relying on intuition does have it's advantages but it is also rife with disadvantages. One of the advantages is that intuition is fairly instantaneous. One of the disadvantages is also that it is instantaneous since intuition is reactive rather than responsive. One can react to even a single event which is rarely a large enough sample from which to draw larger conclusions. Responsiveness requires permutations in order to detect commonality of patterns. FWIW I have 14.2 and Current installed on three machines here, a four year old Intel box, a 7 year old Intel box, and a 12 year old AMD single core 64 bit box and each 14.2 install has been running "5 brand" kernels for months with very few issues. In fact the only issues have been with Current which is installed as designed for testing and those only with kernel 5.4.0-rc1 and rc2. The only issues for those was that a change in format of Modules.symvers caused failure in building nvidia kernel modules. The 5.0.20 and other kernels not of the 5.2.x branch work flawlessly for me on those machines for this length of time.

Also FWIW my above experiences also include considerable time in wine games in each although I don't specifically play Diablo. I have not experienced much difference let alone problems with these six installs, excepting as noted with the release candidates of 5.4 kernels. It is my understanding that AMD graphics users experience greater differences than I have so far due to substantial improvements in the open source drivers.

1 members found this post helpful.

I was not precise enough. Post is not about running Diablo. Actually it works. Windows games I play only on live system to not taint hard drive installation with exe files. Games are kept on separate partition never never being auto mounted by hard drive installed systems. It was accidentally that my first attempt to use Knoppix 8.6 was about to play game. But eg. hangs on after boot command knoppix 2 is pure clean unrelated to wine or Diablo.

PS. Best performance to play Diablo I got under Slackware 12.2

Unless you have copied Slackware's .config file from 4.19 in -current, have run 'make oldconfig' and have made necessary selections, built 5.2.x on Slackware (for whatever reason one might do so at this juncture) and are having problems, this post has nothing to do with anything and is utter nonsense.

1 members found this post helpful.

Poprocks I can't tell whom you are addressing. Are you simply saying that Knoppix has no bearing on Slackware? Not only would I agree with that but I'd go further and insist on apples-to-apples and slipstream a fully configured 5.2 kernel into LiveSlak for a direct comparison though I would still wonder how what happens in Knoppix has much if anything to do with Slack.

I'd ask if you meant building a 5.2 kernel in Slack and slipping it into Knoppix but that seems so unlikely I won't ask.

I think that future resolve this issue and will prove that I am right. I must say I have no idea where lies difference between Slackware and Knoppix. Processes Knoppix runs are the same as in Slackware. Run level 2 in Knoppix which corresponds to run level 3 in Slackware are the same except systemd-udevd daemon. I would say all it looks very Slackwarish. In terms of reliability: kernels 5. runs ok for some while not ok for others which obviously can not be accepted. The idea came to my mind that there may be a problem with passing boot time kernel parameters to init process.

Hmmm it is my understanding that Knoppix 8.6 dropped systemd but I don't know which init it does now use. However I doubt that it is the same as Slackware BSD style rc init. IMHO "looks very Slackwarish" is a non-specific term since wildly different systems can look identical. Passing boot time kernel parameters can be handled in a variety of ways - by the bootloader, by an initrd, or by option selection combined with rc.local, rc.modules.local and modprobe.d etc... at least in Slackware. That control and efficiency is substantially more difficult in a Live environment, even one with persistence.

I find myself wondering what ever possessed you to create this thread in Slackware? Did you write similar threads for each of the other distro sub-forums? What was your intent in creating this thread and especially off of such a singular event of considerably different code?

1 members found this post helpful.

Because I thought It could be of some benefit to post it here. Are you asking for reason? None. Let me explain. There are two kinds experts: the first relies on mostly knowledge and experience. And they are very good in circumstances where there is enough reliable information. The second kind of experts are people working int situations of lack of information or data are being unreliable. Because there is lack of information decision cannot be made on base of procedures, recipes, knowledge, experience. So expert of second kind is making decision because of its feelings, pain in his leg, fool taste of coffee. No matter. What really matter is they are correct statistically - say in 6 per 10 they are correct. I am quite sure that soon companies will start to look for such kind of persons - which can see things where others see nothing. World is becoming to complicated so knowledge, experience, science won't be sufficient as base for decision making. Today there is no relation between Alice's pain in her left knee and software project - tomorrow manager will order to run detailed tests because Alice feels pain. Because often when Alice feels pain bug was found - so company decided to promote Alice as expert software tester. And tool Alice is using is her knee - does it pain or not. The only reason: because it works. Question how would such connection be possible is senseless.

The thing is, nobody here cares what knoppix does. Slackware doesn't take cues from that distro and it doesn't use the same scripts to detect/initialize hardware in the same way. If Slackware installs a problematic kernel, or there's a problem with udev, Slackware will correct the situation.

Pain in my ass might be a symptom of software bugs, but so far my knee hasn't affected my Linux kernel :-)

(I get what you're saying though, and that insight is not lost on me. Human decisions are affected by personal issues and external factors. However, for Alice's knee pain to have any correlation with software bugs, Alice would have to be reacting to the knowledge of them in the first place. I don't believe in clairvoyance)

P.S. There was a time (before we had udev) when Knoppix hardware probing/detection was revolutionary, but that time has passed.

OP you have the cart before the horse...Knoppix' lack of stability has nothing to do with Slackware. Now, if you were asking does Slackware's legendary stability mean that Knoppix is screwing with something to make it unstable, then you may have a valid question.

If you are correct then I sincerely hope companies that own hospitals don't hire the "second kind of 'experts'" to do surgery or prescribe medicines. Generally and far more often than not, seeing things where others see nothing is called hallucination.

1 members found this post helpful.