SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,126
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
07-June-2022.
FWIW: Tried to build the new 5.19-rc1 kernel with gcc-12.1.0, but it was spitting errors left and right, so I finally stopped the process.
Removed gcc-12.1.0, installed gcc-11.3.0 and rebooted.
This time the build was successfully. Not a single error.
I didn't expect the NVIDIA-Linux-x86_64-470.129.06.run driver to build and it did not.
OTOH, I was pleasantly surprised to see VirtualBox-6.1.35-151573-Linux_amd64 build and run as it should.
Using the nouveau driver for now and so far, so good.
BTW. it took about 10 minutes longer to build this kernel than any other kernel I've built on the same box.
Just built the 5.19-rc4 kernel with gcc-12.1.0 and there were no errors.
As mentioned above, I didn't expect the NVIDIA-470.129.06.run driver to build and it did not.
However, VirtualBox-6.1.35-151866 built and is performing as it should.
Using the nouveau driver for now and so far, so good.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,126
Original Poster
Rep:
Year 2022, Round 39.
Another batch of updates has been scheduled for release on Wednesday, 29 June 2022, at approximately 11:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Note that there is a new Kernel Config in 5.15.51 that I compiled as a module:
Code:
*
* USB Type-C Support
*
USB Type-C Support (TYPEC) [M/n/y/?] m
USB Type-C Port Controller Manager (TYPEC_TCPM) [M/n/?] m
Type-C Port Controller Interface driver (TYPEC_TCPCI) [M/n/?] m
Richtek RT1711H Type-C chip driver (TYPEC_RT1711H) [M/n/?] m
Maxim TCPCI based Type-C chip driver (TYPEC_TCPCI_MAXIM) [M/n/?] m
Fairchild FUSB302 Type-C chip driver (TYPEC_FUSB302) [M/n/?] m
Intel WhiskeyCove PMIC USB Type-C PHY driver (TYPEC_WCOVE) [N/m/?] (NEW) m
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,126
Original Poster
Rep:
Year 2022, Round 40.
Another batch of updates has been scheduled for release on Saturday, 2 July 2022, at approximately 13:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Friday (depending on your time zone).
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,126
Original Poster
Rep:
Year 2022, Round 41.
Another batch of updates has been scheduled for release on Thursday, 7 July 2022, at approximately 12:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Wednesday (depending on your time zone).
p.s. Since I've got a new kernel-firmware package too, I'll also Enable my Clevo Discrete ThunderBolt Interface in my UEFI BIOS to see if it still causes a series 20 sec time-out delays when booting ...
This is what I see when my Discrete ThunderBolt is Enabled ( it was just a tad scary when I first booted my LapTop )
Code:
[ 9.359600] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input15
[ 27.953327] DMAR: DRHD: handling fault status reg 2
[ 27.959653] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr 0x69935000 [fault reas
on 0x05] PTE Write access is not set
[ 48.433330] DMAR: DRHD: handling fault status reg 2
[ 48.438777] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr 0x69935000 [fault reas
on 0x05] PTE Write access is not set
[ 68.913306] DMAR: DRHD: handling fault status reg 2
[ 68.919850] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr 0x69935000 [fault reas
on 0x05] PTE Write access is not set
[ 89.387726] thunderbolt 0000:07:00.0: failed to send driver ready to ICM
[ 89.394835] thunderbolt: probe of 0000:07:00.0 failed with error -110
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
