I have a newly acquired Asus TUF Gaming FA707NU laptop that I installed Slackware 15.0 on, and that boots up just fine using its default version (5.15.19) kernel.
However, trying to use any of the 6.1.x kernels that are part of Slackware-Current results in the keyboard failing to take input and the system locking up to the point that I am forced to use the power button to reset.
I even tried getting the Slack-Current iso file to boot from a USB drive, and that also makes the keyboard inaccessible, again forcing a hard reset via power switch.
I have no idea how to get around this, and I can confirm that the kernel parameters are identical for both kernel revisions, so it's highly doubtful that those could be the source of this issue.
Below is what I was able to extract from /var/log/syslog, but if required, I can provide the much larger file (128KB) /var/log/messages data for the same bootup attempt:

Jul 7 17:43:38 ummagumma kernel: #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15
Jul 7 17:43:38 ummagumma kernel: ACPI BIOS Error (bug): Could not resolve symbol [\x5c_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20220331/dswload2-162)
Jul 7 17:43:38 ummagumma kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
Jul 7 17:43:38 ummagumma kernel: ACPI BIOS Error (bug): Could not resolve symbol [\x5c_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20220331/dswload2-162)
Jul 7 17:43:38 ummagumma kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
Jul 7 17:43:38 ummagumma kernel: ACPI BIOS Error (bug): Could not resolve symbol [\x5c_SB.PCI0.GPP5.RTL8], AE_NOT_FOUND (20220331/dswload2-162)
Jul 7 17:43:38 ummagumma kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
Jul 7 17:43:38 ummagumma kernel: ACPI BIOS Error (bug): Failure creating named object [\x5c_SB.PCI0.GPP6.WLAN._S0W], AE_ALREADY_EXISTS (20220331/dswload2-326)
Jul 7 17:43:38 ummagumma kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
Jul 7 17:43:38 ummagumma kernel: ACPI BIOS Error (bug): Could not resolve symbol [\x5c_SB.PCI0.GPP7.DEV0], AE_NOT_FOUND (20220331/dswload2-162)
Jul 7 17:43:38 ummagumma kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
Jul 7 17:43:38 ummagumma kernel: ACPI: \x5c_SB_.PCI0.GP11: Overriding _PRW sleep state (S4) by S0 from power resources
Jul 7 17:43:38 ummagumma kernel: ACPI: \x5c_SB_.PCI0.GP12: Overriding _PRW sleep state (S4) by S0 from power resources
Jul 7 17:43:38 ummagumma kernel: ACPI: \x5c_SB_.PCI0.GP19.NHI0: Overriding _PRW sleep state (S3) by S0 from power resources
Jul 7 17:43:38 ummagumma kernel: ACPI: \x5c_SB_.PCI0.GP19.NHI1: Overriding _PRW sleep state (S4) by S0 from power resources
Jul 7 17:43:38 ummagumma kernel: Expanded resource Reserved due to conflict with PCI Bus 0000:00
Jul 7 17:43:38 ummagumma kernel: pci 0000:00:08.1: can't derive routing for PCI INT A
Jul 7 17:43:38 ummagumma kernel: pci 0000:00:08.1: PCI INT A: not connected
Jul 7 17:43:38 ummagumma kernel: pci 0000:00:08.3: can't derive routing for PCI INT A
Jul 7 17:43:38 ummagumma kernel: pci 0000:00:08.3: PCI INT A: not connected
Jul 7 17:43:38 ummagumma kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Jul 7 17:43:38 ummagumma kernel: pci 0000:00:00.2: PCI INT A: not connected
Jul 7 17:43:38 ummagumma kernel: OCFS2 User DLM kernel interface loaded
Jul 7 17:43:38 ummagumma kernel: hpet_acpi_add: no address or irqs in _CRS
Jul 7 17:43:38 ummagumma kernel: 3ware Storage Controller device driver for Linux v1.26.02.003.
Jul 7 17:43:38 ummagumma kernel: 3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
Jul 7 17:43:41 ummagumma kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Jul 7 17:43:41 ummagumma kernel: efifb: cannot reserve video memory at 0x40000000
Jul 7 17:43:41 ummagumma kernel: ------------[ cut here ]------------
Jul 7 17:43:41 ummagumma kernel: ioremap on RAM at 0x0000000040000000 - 0x00000000407e8fff
Jul 7 17:43:41 ummagumma kernel: WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:211 __ioremap_caller+0x337/0x350
Jul 7 17:43:41 ummagumma kernel: Modules linked in:
Jul 7 17:43:41 ummagumma kernel: CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.1.38 #1
Jul 7 17:43:41 ummagumma kernel: Hardware name: ASUSTeK COMPUTER INC. ASUS TUF Gaming A17 FA707NU_FA707NU/FA707NU, BIOS FA707NU.310 06/19/2023
Jul 7 17:43:41 ummagumma kernel: RIP: 0010:__ioremap_caller+0x337/0x350
Jul 7 17:43:41 ummagumma kernel: Code: e8 1e de ff ff 49 09 c7 e9 37 fe ff ff 48 8d 54 24 28 48 8d 74 24 18 48 c7 c7 d5 52 c0 8c c6 05 1d c2 2a 02 01 e8 a9 80 07 00 <0f> 0b 31 ed e9 99 fe ff ff e8 cb dc 1b 01 66 66 2e 0f 1f 84 00 00
Jul 7 17:43:41 ummagumma kernel: RSP: 0018:ffffb4848009fbd0 EFLAGS: 00010282
Jul 7 17:43:41 ummagumma kernel: RAX: 0000000000000000 RBX: 0000000040000000 RCX: 0000000000000000
Jul 7 17:43:41 ummagumma kernel: RDX: 0000000000000002 RSI: 00000000ffffdfff RDI: 00000000ffffffff
Jul 7 17:43:41 ummagumma kernel: RBP: ffff8ea047791800 R08: 0000000000000000 R09: ffffb4848009fa50
Jul 7 17:43:41 ummagumma kernel: R10: 0000000000000003 R11: ffffffff8d13dd28 R12: 0000000000000001
Jul 7 17:43:41 ummagumma kernel: R13: 00000000007e9000 R14: 00000000007e9000 R15: 0000000000000000
Jul 7 17:43:41 ummagumma kernel: FS: 0000000000000000(0000) GS:ffff8ea77e880000(0000) knlGS:0000000000000000
Jul 7 17:43:41 ummagumma kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 7 17:43:41 ummagumma kernel: CR2: 0000000000000000 CR3: 00000002ee010000 CR4: 0000000000750ee0
Jul 7 17:43:41 ummagumma kernel: PKRU: 55555554
Jul 7 17:43:41 ummagumma kernel: Call Trace:
Jul 7 17:43:41 ummagumma kernel: <TASK>
Jul 7 17:43:41 ummagumma kernel: ? __ioremap_caller+0x337/0x350
Jul 7 17:43:41 ummagumma kernel: ? __warn+0x79/0xc0
Jul 7 17:43:41 ummagumma kernel: ? __ioremap_caller+0x337/0x350
Jul 7 17:43:41 ummagumma kernel: ? report_bug+0xe6/0x170
Jul 7 17:43:41 ummagumma kernel: ? handle_bug+0x3a/0x70
Jul 7 17:43:41 ummagumma kernel: ? exc_invalid_op+0x13/0x60
Jul 7 17:43:41 ummagumma kernel: ? asm_exc_invalid_op+0x16/0x20
Jul 7 17:43:41 ummagumma kernel: ? __ioremap_caller+0x337/0x350
Jul 7 17:43:41 ummagumma kernel: ? efifb_probe.cold+0x1fd/0x722
Jul 7 17:43:41 ummagumma kernel: efifb_probe.cold+0x1fd/0x722
Jul 7 17:43:41 ummagumma kernel: platform_probe+0x44/0x90
Jul 7 17:43:41 ummagumma kernel: really_probe+0xd9/0x290
Jul 7 17:43:41 ummagumma kernel: ? pm_runtime_barrier+0x50/0x90
Jul 7 17:43:41 ummagumma kernel: __driver_probe_device+0x73/0xf0
Jul 7 17:43:41 ummagumma kernel: driver_probe_device+0x1f/0xe0
Jul 7 17:43:41 ummagumma kernel: __device_attach_driver+0x7f/0x110
Jul 7 17:43:41 ummagumma kernel: ? driver_allows_async_probing+0x70/0x70
Jul 7 17:43:41 ummagumma kernel: bus_for_each_drv+0x8b/0xd0
Jul 7 17:43:41 ummagumma kernel: __device_attach+0xaf/0x1b0
Jul 7 17:43:41 ummagumma kernel: bus_probe_device+0x8e/0xb0
Jul 7 17:43:41 ummagumma kernel: device_add+0x3df/0x850
Jul 7 17:43:41 ummagumma kernel: platform_device_add+0xfc/0x210
Jul 7 17:43:41 ummagumma kernel: sysfb_init+0xb9/0xe3
Jul 7 17:43:41 ummagumma kernel: ? firmware_map_add_early+0x53/0x53
Jul 7 17:43:41 ummagumma kernel: do_one_initcall+0x59/0x220
Jul 7 17:43:41 ummagumma kernel: kernel_init_freeable+0x1da/0x21d
Jul 7 17:43:41 ummagumma kernel: ? rest_init+0xd0/0xd0
Jul 7 17:43:41 ummagumma kernel: kernel_init+0x16/0x130
Jul 7 17:43:41 ummagumma kernel: ret_from_fork+0x22/0x30
Jul 7 17:43:41 ummagumma kernel: </TASK>
Jul 7 17:43:41 ummagumma kernel: ---[ end trace 0000000000000000 ]---
Jul 7 17:43:41 ummagumma kernel: efifb: abort, cannot remap video memory 0x7e9000 @ 0x40000000
Jul 7 17:43:41 ummagumma kernel: efi-framebuffer: probe of efi-framebuffer.0 failed with error -5
Jul 7 17:43:43 ummagumma udevd[776]: IMPORT{builtin}: 'usb-db' unknown /lib/udev/rules.d/75-tty-description.rules:7
Jul 7 17:43:43 ummagumma udevd[776]: IMPORT{builtin}: 'pci-db' unknown /lib/udev/rules.d/75-tty-description.rules:11
Jul 7 17:43:43 ummagumma kernel: wmi_bus wmi_bus-PNP0C14:00: WQ00 data block query control method not found
Jul 7 17:43:43 ummagumma kernel: ACPI BIOS Error (bug): Could not resolve symbol [\x5c_TZ.THRM._SCP.CTYP], AE_NOT_FOUND (20220331/psargs-330)
Jul 7 17:43:43 ummagumma kernel: ACPI Error: Aborting method \x5c_TZ.THRM._SCP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Jul 7 17:43:43 ummagumma kernel: hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
Jul 7 17:43:43 ummagumma kernel: nvidia: loading out-of-tree module taints kernel.
Jul 7 17:43:43 ummagumma kernel: nvidia: module license 'NVIDIA' taints kernel.
Jul 7 17:43:43 ummagumma kernel: Disabling lock debugging due to kernel taint
Jul 7 17:43:43 ummagumma kernel:
Jul 7 17:43:43 ummagumma kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 535.54.03 Tue Jun 6 22:20:39 UTC 2023
Jul 7 17:43:44 ummagumma kernel: ATPX version 1, functions 0x00000801
Jul 7 17:43:44 ummagumma kernel: ATPX Hybrid Graphics
Jul 7 17:43:44 ummagumma kernel: amdgpu 0000:36:00.0: amdgpu: PSP runtime database doesn't exist
Jul 7 17:43:44 ummagumma last message buffered 1 times
Jul 7 17:43:44 ummagumma kernel: Bluetooth: hci0: Failed to read codec capabilities (-22)
Jul 7 17:43:44 ummagumma kernel: amdgpu: SRAT table not found
Jul 7 17:43:47 ummagumma udevd[777]: IMPORT{builtin}: 'usb-db' unknown /lib/udev/rules.d/75-tty-description.rules:7
Jul 7 17:43:47 ummagumma udevd[777]: IMPORT{builtin}: 'pci-db' unknown /lib/udev/rules.d/75-tty-description.rules:11
Jul 7 17:43:49 ummagumma kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Jul 7 17:43:55 ummagumma named[5433]: config.c: option 'trust-anchor-telemetry' is experimental and subject to change in the future
Jul 7 17:43:55 ummagumma named[5433]: managed-keys-zone: Unable to fetch DNSKEY set '.': failure
Jul 7 17:43:57 ummagumma kernel: VBoxNetFlt: Successfully started.
Jul 7 17:43:57 ummagumma kernel: VBoxNetAdp: Successfully started.
Jul 7 17:43:58 ummagumma bumblebeed[8906]: No integrated video card found, quitting.

Just to clarify, did you use the 6.1 kernels on your 15.0 install? If so that is not going to work since you are using 6.1 kernels compiled for -current and not 15.0.. You would need to compile the 6.1 kernel using 15.0 libraries, but even them I am not sure that is advisable. Also you mentioned you tried Slackware-current on a usb, do you mean you tried installing Slackware-current from a usb? the -current iso will not work as a live distribution, you would have to use Alien Bob's Slack Live ISO's

https://docs.slackware.com/slackware:liveslak

Did you make the initrd file for the 6.1.x kernel?

Then perhaps you should use Slackware 15, however

The current kernel is 5.15.117, so you should consider updating the kernel. And make an initrd file to suit the 5.15.117 kernel BEFORE rebooting.

I should have clarified, but I found myself unable to even get the Slackware-Current installer to boot when put onto an empty USB drive, but Slackware-15.0 on the same drive comes up just fine, so there definitely appears to be something about the 6.1.x kernels that my machine objects to, even from a USB drive.

What is in /lib/udev/rules.d/75-tty-description.rules and which package installed it?

You use a proprietary nvidia module. If you use kernel built on -current, I hope you built the nvidia .ko modules also on -current (the gcc versions differ).

This is not quite true. The kernel does not use libraries, the libraries are a user space concept. I only use 6.1 kernels compiled on -current to run both 15.0 and 14.2. (If nvidia or any other out-of-tree modules are used, they need to be built on -current, too, because the differing gcc version could cause problems between the kernel and modules.)

2 members found this post helpful.

I had to look a bit, but the 75-tty-descriptoin.rules came with the udev-182-x86_64-7.txz package clear back with Slackware-14.1.
Would it be best for me to delete that, or is something else needed?

How is is possible that you have Slackware-14.1 udev files installed on a new laptop with Slackware-15.0? The switch from udev to eudev happened in 2015. Maybe you have other out-of-date files in your system?

It's possible that this is just a red herring and that your laptop has something else against newer kernels. But I would try it on a clean 15.0 (and then a 6.1 kernel).

Have you tried to connect an external keyboard? I have earlier seen laptops having non-working internal keyboard when using the setup disk. After installation it has worked ok.

I did not know that. Learn something new everyday, Thanks .

Update: I followed your suggestion by plugging in a USB keyboard and I had no problems that way.
However, I was forced to use the USB keyboard exclusively, and evtest indicated that the integral keyboard wasn't detected at.
Conversely, when booting into kernel 5.15.19 from Slackware-15.0, evtest shows that both the USB keyboard and the laptop's own keyboard are fully detected.
It's strange that a newer kernel lacks functionality that an older kernel had.
Maybe there's a boot-time kernel parameter, *.conf file to put into /etc/modprobe.d, or some kind of patch for this, but it's rather perplexing.
Thanks for the suggestions thus far, and I'm open to trying other options, if any.

Look at this:

https://bugzilla.kernel.org/show_bug.cgi?id=217336#c147

Thanks for locating what appears to be a conclusive explanation.
It looks as if I'll have to wait for some time for a workable version 6.4.x kernel for Slackware to emerge.
I could take a shot at trying to build it myself, but it's often tough getting one to boot up.

For what purpose must you use 6.1 if the install 5.15 works?

Newer does not always mean better. I'm running 4.14 on Slack15 and seemed more stable than 5.15. Works fine. And lol - you should see some of the 'new' people they let work on the kernel now. Because diversity. Meritocracy now dead.

Mainly, for better hardware support.
I hadn't heard about lower caliber help for Patrick V's distribution, but it wouldn't surprise me, sadly.

I'm pretty sure he is slammin' Linus Torvald's developers. I wasn't under the impression there were enough people lined up and interested making contributions to Slackware that dilution of talent by diversity initiatives could be a thing.