The Latest Kernel Release.

marav · 01-12-2023, 09:07 AM

Quote:

Originally Posted by LuckyCyborg

Secure Display is an improved HDCP technology brought to us by the Hollywood Godfathers.

Apparently, your laptop does not qualify for it, so ... probably soon this will mean: no legal movies for you!

According to the description:

Code:

This option enables the calculation of crc of specific region via debugfs. Cooperate with specific DMCU FW

Anyway, I heavily doubt HDCP technology or similar will land in the kernel one day or another

EDIT:
revert to previous kernel-firmware and everything is clear in dmesg again
or maybe I could just disable secure display in the kernel

jkh2cpu · 01-12-2023, 09:32 AM

I'm gonna whine here again about Nvidia and linux-6.1.5 one more time, and then I'll shut-up.

I can startx and get the KDE session, which seems to work OK. If I log out back to run level 3, KDE stops, but I never get back to the command line with a usable terminal.

SSH'ing into the stalled box, I see this snip from /var/log/messages:

Jan 12 09:24:42 jkh-box dbus-daemon[11677]: [session uid=1000 pid=11675] Activating service name='org.kde.LogoutPrompt' requested by ':1.25' (uid=1000 pid=11888 comm="/usr/bin/plasmashell")
Jan 12 09:24:43 jkh-box dbus-daemon[11677]: [session uid=1000 pid=11675] Successfully activated service 'org.kde.LogoutPrompt'
Jan 12 09:24:46 jkh-box dbus-daemon[11677]: [session uid=1000 pid=11675] Activating service name='org.kde.Shutdown' requested by ':1.71' (uid=1000 pid=12355 comm="/usr/lib64/libexec/ksmserver-logout-greeter")
Jan 12 09:24:46 jkh-box dbus-daemon[11677]: [session uid=1000 pid=11675] Successfully activated service 'org.kde.Shutdown'
Jan 12 09:25:06 jkh-box kernel: PGD 1c8201067 P4D 1c8201067 PUD 0
Jan 12 09:25:42 jkh-box sshd[12390]: Accepted keyboard-interactive/pam for jkh from 192.168.12.195 port 33454 ssh2
Jan 12 09:25:42 jkh-box elogind-daemon[1391]: New session 3 of user jkh.

When I reboot the stalled machine via SSH, I see the following lines.

root@jkh-box:/var/log# reboot

Broadcast message from root@jkh-box (pts/0) (Thu Jan 12 09:26:43 2023):

The system is going down for reboot NOW!
root@jkh-box:/var/log# Connection to jkh-box closed by remote host.
Connection to jkh-box closed

Something is not cleaning up properly and/or not restoring a terminal window.

Thoughts?

Aeterna · 01-12-2023, 10:42 AM

Quote:

Originally Posted by kjhambrick

Thanks cwizardone.

I had already built the modules for 6.1.5 before I built 5.15.87 so I assumed they would be in /lib/modules/`uname -r`/

Let that be a lesson to me

-- kjh

Each installation of nvidia will remove previous installation. In past you could keep previously installed nvidia drivers for different kernels. If this switch is still available (-K), you could keep two kernels with installed nvidia drivers.

garpu · 01-12-2023, 10:59 AM

Quote:

Originally Posted by Aeterna

Each installation of nvidia will remove previous installation. In past you could keep previously installed nvidia drivers for different kernels. If this switch is still available (-K), you could keep two kernels with installed nvidia drivers.

It is.

burdi01 · 01-12-2023, 11:59 AM

My post #5127 of Dec 28:

Quote:

Originally Posted by burdi01

Since kernel 6.1.X the wifi rtw88_8723de driver causes a kernel crash on my HP 17-by1905nd i5 8256SU laptop. With kernel 6.0.X things were ok. On my desktops the crash does not occur.
Luckily I can blacklist the rtw88_8723de driver and use a USB dongle for net access.
Is there someone else having this problem?

Kernels 6.1.5 as well as 6.2.0-rc3 still show the problem ...

marav · 01-12-2023, 01:38 PM

Quote:

Originally Posted by marav

According to the description:

Code:

This option enables the calculation of crc of specific region via debugfs. Cooperate with specific DMCU FW

Anyway, I heavily doubt HDCP technology or similar will land in the kernel one day or another

EDIT:
revert to previous kernel-firmware and everything is clear in dmesg again
or maybe I could just disable secure display in the kernel

Code:

CONFIG_DRM_AMD_DC_HDCP:
Choose this option if you want to support HDCP authentication

ok, i'd better shut my ... up (it's not like this is the first time

)

garpu · 01-12-2023, 08:27 PM

6.1.5 on slackware-64/current/multilib is about like 6.1.4. I'm still having the xid 31 errors switching to console exiting X and while X is running. (525.78.01, geforce 1050ti.) Other than that, if I don't try to bounce between console and X, it's fine. (Or as fine as things can be with that, but I think it's an nvidia problem, not a Slackware problem.)

Here's the error, if anyone's interested.

Code:

Jan 12 18:27:03 zdeno kernel: NVRM: Xid (PCI:0000:07:00): 31, pid=11131, name=Xorg, Ch 00000008, intr 10000000. MMU Fault: ENGINE GRAPHICS HUBCLIENT_FE faulted @ 0x1_00184000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
Jan 12 18:27:06 
zdeno kernel: NVRM: Xid (PCI:0000:07:00): 31, pid=11131, name=Xorg, Ch 00000008, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST faulted @ 0x1_00090000. Fault is of type FAULT_PDE ACCESS_TYPE_READ

cwizardone · 01-13-2023, 06:37 AM

A series of messages related to the selection of the next LTS kernel,
https://lkml.iu.edu/hypermail/linux/...1.1/07357.html
https://lkml.iu.edu/hypermail/linux/...1.1/07361.html
https://lkml.iu.edu/hypermail/linux/...1.1/04157.html

garpu · 01-13-2023, 08:03 AM

https://bugzilla.kernel.org/show_bug.cgi?id=216303 Here's the nvidia console bug people are having. Lots of finger pointing, snark, and I'm not sure who should get the bug report now. :/ There's a kernel patch that allegedly fixes it, but I'm not sure when we're getting it. (If we're getting it...)

ttk · 01-13-2023, 11:34 PM

Just wanted to pop in to say that y'all rock.

I've been contemplating the best way forward with my small fleet of Xeon Phi coprocessor cards, for which kernel support (MIC) was dropped after 5.9.x.

So far I've been using Slackware 14.2 and CentOS 6 to host them, and backporting a handful of packages, but would much rather upgrade all of these systems to Slackware 15.

My first thought was to port the MIC drivers forward to 5.15.x, but that was not feasible. The MIC drivers were dropped so that work could proceed on supporting imx8qm, and subsequent kernel development has rendered the old MIC code nonviable.

My next thought was to try running Slackware 15 with the latest 5.9.x kernel, but was the 5.9.x kernel problematic?

To answer that I rooted around in this thread and found everyone who reported running 5.9.x under Slackware (pages 53 through 57). None of the problems you reported were relevant to my use-case (I run the Xeon Phi hosts headless) which is perfect. It gives me the confidence to try Slackware 15 / linux-5.9.16 this weekend.

So this is a shout-out to all of you wonderful people who test-drive each and every minor kernel release on your Slackware systems. You are seen, you are studied, and you are appreciated :-) Thank you!

Didier Spaier · 01-14-2023, 02:45 AM

@ttk: However the 5.9 branch is EOL and no more mentioned in https://kernel.org/. Maybe you'd be better off using a 5.10 kernel, which has a projected EOL of December, 2026 according to https://kernel.org/category/releases.html or if that is still too new for your hardware (I didn't check) 5.4, with a projected EOL of December, 2025.

kjhambrick · 01-14-2023, 04:26 AM

Quote:

Originally Posted by Aeterna

Each installation of nvidia will remove previous installation. In past you could keep previously installed nvidia drivers for different kernels. If this switch is still available (-K), you could keep two kernels with installed nvidia drivers.

Quote:

Originally Posted by garpu

It is.

Thanks Aeterna and garpu.

I'll give the -K Option a shot this morning.

-- kjh

Code:

$ sh NVIDIA-Linux-x86_64-525.78.01.run -A

<<snip>>

  -K, --kernel-modules-only
      Install the kernel modules only, and do not uninstall the existing driver.  
      This is intended to be used to install kernel modules for additional kernels 
      (in cases where you might boot between several different kernels).  To use 
      this option, you must already have a driver installed, and the version of 
      the installed driver must match the version of these kernel modules.

<<snip>>

cwizardone · 01-14-2023, 05:05 AM

Kernel updates 6.1.6, 5.15.88 and 5.10.163, are now available at, https://www.kernel.org
The change logs,
https://cdn.kernel.org/pub/linux/ker...hangeLog-6.1.6

https://cdn.kernel.org/pub/linux/ker...ngeLog-5.15.88

https://cdn.kernel.org/pub/linux/ker...geLog-5.10.163

ttk · 01-14-2023, 05:51 AM

Quote:

Originally Posted by Didier Spaier

@ttk: However the 5.9 branch is EOL and no more mentioned in https://kernel.org/. Maybe you'd be better off using a 5.10 kernel, which has a projected EOL of December, 2026

Alas the entire point of the exercise is to host my Xeon Phi coprocessors, for which support was dropped after 5.9.x.

3rensho · 01-14-2023, 06:05 AM

6.1.6 built and running fine. Nvidia playing nicely as well