On 4/11/24 15:08, Jeffrey Walton wrote:
On Thu, Apr 11, 2024 at 6:01 PM Sam Varshavchik wrote:
Tim via users writes:
"The service systemd-networkd-wait-online.service invokes systemd-
networkd-wait-online without any options. Thus, it waits for all
managed interfaces to be configured or
home user composed on 2024-04-11 19:49 (UTC-0600):
> What does the -100 vs. -200 signify?
From observation, not reading any doc:
A fresh Fedora release gets -300, moving the prior release to -200, and the
prior
to prior release to -100. After the prior-prior's support ends, there is only
On 4/11/24 18:49, home user wrote:
On 4/11/24 7:00 PM, Go Canes wrote:
On Thu, Apr 11, 2024 at 8:06 PM Tom Horsley
wrote:
On Thu, 11 Apr 2024 17:52:10 -0600
home user wrote:
kmod_build_6.8.4-100.fc38.x86_64
Possibly relevant, but I don't know what it means for sure:
My system gets
On 4/11/24 7:00 PM, Go Canes wrote:
On Thu, Apr 11, 2024 at 8:06 PM Tom Horsley wrote:
On Thu, 11 Apr 2024 17:52:10 -0600
home user wrote:
kmod_build_6.8.4-100.fc38.x86_64
Possibly relevant, but I don't know what it means for sure:
My system gets regular updates. I've never had a
On Thu, Apr 11, 2024 at 8:06 PM Tom Horsley wrote:
>
> On Thu, 11 Apr 2024 17:52:10 -0600
> home user wrote:
>
> > kmod_build_6.8.4-100.fc38.x86_64
>
> Possibly relevant, but I don't know what it means for sure:
>
> My system gets regular updates. I've never had a yadda-yadda-100 kernel,
> all
On Thu, 11 Apr 2024 17:52:10 -0600
home user wrote:
> kmod_build_6.8.4-100.fc38.x86_64
Possibly relevant, but I don't know what it means for sure:
My system gets regular updates. I've never had a yadda-yadda-100 kernel,
all mine are -200. Currently I'm running 6.8.4-200.fc39.x86_64, all the
On 4/11/24 5:39 PM, Samuel Sieb wrote:
On 4/11/24 16:36, home user wrote:
On 4/11/24 5:31 PM, Samuel Sieb wrote:
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error:
On 4/11/24 16:36, home user wrote:
On 4/11/24 5:31 PM, Samuel Sieb wrote:
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a
On 4/11/24 5:31 PM, Samuel Sieb wrote:
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
There has been a kernel change of some
On 4/11/24 4:45 PM, Samuel Sieb wrote:
On 4/11/24 15:40, home user wrote:
On 4/11/24 4:34 PM, Samuel Sieb wrote:
On 4/11/24 13:01, home user wrote:
I tried the command suggested in that log file.
--
bash.24[~]: /usr/sbin/akmods --force
Checking kmods exist for 6.8.4-100.fc38.x86_64
On 4/11/24 15:40, home user wrote:
On 4/11/24 4:34 PM, Samuel Sieb wrote:
On 4/11/24 13:01, home user wrote:
I tried the command suggested in that log file.
--
bash.24[~]: /usr/sbin/akmods --force
Checking kmods exist for 6.8.4-100.fc38.x86_64 [ OK ]
Building and installing
On 4/11/24 4:34 PM, Samuel Sieb wrote:
On 4/11/24 13:01, home user wrote:
I tried the command suggested in that log file.
--
bash.24[~]: /usr/sbin/akmods --force
Checking kmods exist for 6.8.4-100.fc38.x86_64 [ OK ]
Building and installing nvidia-470xx-kmod
On 4/11/24 13:01, home user wrote:
I tried the command suggested in that log file.
--
bash.24[~]: /usr/sbin/akmods --force
Checking kmods exist for 6.8.4-100.fc38.x86_64 [ OK ]
Building and installing nvidia-470xx-kmod [FAILED]
Building rpms failed; see
On 4/11/24 11:19 AM, home user wrote:
(f-38; stand-alone work station; nvidia graphics card; dual monitor; kmod 4xx
driver)
I just finished doing a "dnf upgrade" as a prerequisite step to upgrading from
f-38 to f-39.
There were no hints of any problems. The kernel and the graphics driver
On Thu, Apr 11, 2024 at 6:01 PM Sam Varshavchik wrote:
>
> Tim via users writes:
>
> > "The service systemd-networkd-wait-online.service invokes systemd-
> > networkd-wait-online without any options. Thus, it waits for all
> > managed interfaces to be configured or failed, and for at least one to
Tim via users writes:
"The service systemd-networkd-wait-online.service invokes systemd-
networkd-wait-online without any options. Thus, it waits for all
managed interfaces to be configured or failed, and for at least one to
be online."
Could it be that you have some additional interfaces
home user wrote:
> I tried the command suggested in that log file.
>
> --
> bash.24[~]: /usr/sbin/akmods --force
> Checking kmods exist for 6.8.4-100.fc38.x86_64 [ OK ]
> Building and installing nvidia-470xx-kmod [FAILED]
> Building rpms failed; see
>
On 4/11/24 12:34, Tom Horsley wrote:
On Thu, 11 Apr 2024 11:09:26 -0700
Doug Herr wrote:
I don't have Nvidia currently and can't remember where you find those logs.
/var/log/akmod/akmod.log
If it doesn't say something about "Success" near the end, then it didn't
build correctly.
I usually
On 4/11/24 12:09, Doug Herr wrote:
On Thu, Apr 11, 2024, at 10:19 AM, home user wrote:
(f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx driver)
I just finished doing a "dnf upgrade" as a prerequisite step to
upgrading from f-38 to f-39.
There were no hints of any
On Thu, 11 Apr 2024 15:12:08 -0400
Jeffrey Walton wrote:
> When something does not (can not?) build correctly, can you just boot
> to an earlier kernel until the problems with the current kernel
> modules are fixed? Or does rebuilding akmod break past kernels?
I've certainly just booted old
On Thu, Apr 11, 2024 at 2:35 PM Tom Horsley wrote:
>
> On Thu, 11 Apr 2024 11:09:26 -0700
> Doug Herr wrote:
>
> > I don't have Nvidia currently and can't remember where you find those logs.
>
> /var/log/akmod/akmod.log
>
> If it doesn't say something about "Success" near the end, then it didn't
On Thu, 11 Apr 2024 11:09:26 -0700
Doug Herr wrote:
> I don't have Nvidia currently and can't remember where you find those logs.
/var/log/akmod/akmod.log
If it doesn't say something about "Success" near the end, then it didn't
build correctly.
I usually do a tail -f on that file when running
On Thu, Apr 11, 2024, at 10:19 AM, home user wrote:
> (f-38; stand-alone work station; nvidia graphics card; dual monitor;
> kmod 4xx driver)
>
> I just finished doing a "dnf upgrade" as a prerequisite step to
> upgrading from f-38 to f-39.
> There were no hints of any problems. The kernel and
On 4/11/24 12:19, home user wrote:
(f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx driver)
I just finished doing a "dnf upgrade" as a prerequisite step to
upgrading from f-38 to f-39.
There were no hints of any problems. The kernel and the graphics driver
were
(f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx driver)
I just finished doing a "dnf upgrade" as a prerequisite step to
upgrading from f-38 to f-39.
There were no hints of any problems. The kernel and the graphics driver
were replaced during this "dnf upgrade".
On Thu, 2024-04-11 at 07:59 -0400, Sam Varshavchik wrote:
> What I do see, though, is that we have both NetworkManager-wait-
> online and systemd-networkd-wait-online. Why do we need both of them?
>
> I simply disabled systemd-networkd-wait-online, and that seems to
> solve the problem.
Roger Heflin writes:
Run this:
systemd-analyze critical-chain network-online.target
Can you explain why you think inspecting dependencies and starting times of
different systemd units would have any bearing on why a single unit, systemd-
network, is blowing chunks? Wasn't it clear from my
28 matches
Mail list logo
