What exactly do you think I've been doing for the past few days?

Oh, I didn't know you built your own kernel and tried with different configurations. Well, too bad then. At this point I'd say go Mint.

Extra Strong or After Eight?

Stronger the better. Look, it has been two days now. Time to do something different, no? I'd start with make allnoconfig and build a lean kernel, stock kernels may have conflicting drivers. While at it I'd use the latest kernel considered stable at kernel.org.

Configuration file for 4.13.4, that's a starting point for you. it should boot with AHCI hard drive controller, GPT or MBR, Ext4 root filesystem. No initramfs needed. Add your sound and network devices as needed. You may need to set correct CPU, too.

You think that would be better than Mint's .config?

Just to clarify, can you post a few of the kernel boot parameters you tried *with the 'stock' 14.2dvd*
(like noapic nomodeset &esp 'my' retain_initrd). Thanks. (just stick all on one more quick boot)

OK...
Well, it certainly changed things...a lot worse now. Much longer Call Trace.

You cant compare. Mint kernel is built to work with every piece of hardware out there, all the support is built as modules, you need initramfs to get it boot. Custom kernel is strictly the other way around. No cruft, no modules.

Mint kernel works. Mint kernel has Ubuntu patches. Dell and Ubuntu have cooperated. If I can get Slackware running, then I can play around with custom kernels - if I have nowt better to do.

1 members found this post helpful.

Yeah right.

And I was thinking you want to get a stable system, even crafted a kernel seed for you.

>"a lot worse now. Much longer Call Trace."
Oh dear Too many cooksparams making a mess!!!
How does 'my one single retain_initrd ingredient stew' taste?

I thot of kdb/kgdb stuff, but Idk it, nor IF it's in them strange'better' slack.s kernels
I guess there's no way to catch the preceding err msg ("LPsysDinterrupt42missing")
plus all them kfoofcns, to | ddg.com

p.s. IF you hadn't erased Win10 (before trying a boot of the dvd),
could you have tried thisT3600 in a VBox.exe?
(is vbox how they captured all of the panic msgs scroll?)

In Mint, can you: inxi -Fzxx | nc termbin.com 9999 (T3600 has strange devices!!!)

Try blacklisting the nouveau driver when you boot Slackware, by editing the bootloader commandline (lilo, elilo, grub, whatever) and adding the string If that worked, you can permanently blacklist nouveau by installing the Slackware package "xf86-video-nouveau-blacklist" from the extra/ section of the repository and then it would be sensible to try and install the proprietary Nvidia drivers.

Edit - the kernel documentation states that the syntax should be:

Yeah, it looks like it will have to remain Slackless for a while. When I'm in the mood, I'll have another go at it.
Edit
Just read Alien's post
Don't think it's nouveau that's causing the problem. Mint was running nouveau when I installed it. NVidia driver now. I still think it's some Dell/Ubuntu patches in the kernel.

Just for science's sake can you try booting with nouveau blacklisted? So that we can strike one possibility off the list.