home user composed on 2022-11-03 21:42 (UTC-0600):
> What I have is
> -rw---. 1 root root 33824169 Oct 20 09:47
> initramfs-5.19.16-100.fc35.x86_64.img
> -rw---. 1 root root 35051075 Oct 20 11:19
> initramfs-5.19.16-200.fc36.x86_64.img
> -rw---. 1 root root 35452743 Nov 3 13:02
>
On 11/3/22 8:48 PM, Felix Miata wrote:
home user composed on 2022-11-03 20:29 (UTC-0600):
Felix Miata wrote:
home user composed on 2022-11-03 19:02 (UTC-0600):
...
1-Backup the initrd for 5.19.
According to the man page for initrd, it should be in "/dev" and/or "/".
But using "ls -a"
home user composed on 2022-11-03 20:29 (UTC-0600):
> Felix Miata wrote:
>> home user composed on 2022-11-03 19:02 (UTC-0600):
> ...
>> 1-Backup the initrd for 5.19.
> According to the man page for initrd, it should be in "/dev" and/or "/".
> But using "ls -a", I don't see initrd in either pla
On 11/03/2022 04:59 PM, home user wrote:
How do I determine which kernel I'm using now?
uname -r
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
On 11/3/22 7:20 PM, Felix Miata wrote:
home user composed on 2022-11-03 19:02 (UTC-0600):
...
1-Backup the initrd for 5.19.
According to the man page for initrd, it should be in "/dev" and/or "/".
But using "ls -a", I don't see initrd in either place. The "whereis"
command only find a co
home user composed on 2022-11-03 19:02 (UTC-0600):
> What specifically do I need to install?
> "dnf install [what?]" and re-boot.
> Is there anything else I need to do?
It still boots the 5.19 kernel OK, right?
1-Backup the initrd for 5.19.
2-Boot only the 5.19 kernel until such time as updated
On 11/3/22 3:51 PM, home user wrote:
(f36)
...
A few have asked about kernel and driver versions. I've been trying to
grope through logs to get answers. The logs are being split in strange
ways, ways not matching the dates on which the dnf commands were run,
making this both difficult and
On 11/3/22 4:58 PM, Jerry James wrote:
On Thu, Nov 3, 2022 at 4:45 PM home user wrote:
I do not see any such logs in the gnome "logview" tool (which is where I
see the boot and dnf logs). Where are the akmod logs?
/var/cache/akmods/nvidia
Nothing there...
-
bash.3[nvidia]: ls -a
. ..
On 11/3/22 15:59, home user wrote:
On 11/3/22 4:25 PM, Felix Miata wrote:
home user composed on 2022-11-03 15:51 (UTC-0600):
...
Were you previously using a 5.19 kernel and the new kernel is a 6.0?
The problem
is NVidia's proprietary driver isn't working, and the fallback driver
is too crude
On 03/11/2022 21:51, home user wrote:
(f36)
Good afternoon,
A short while ago, I did my weekly patches (dnf upgrade), and then
re-booted. Just before that, the workstation display (dual monitor) was
fine. After the reboot, only one display works. If I switch the monitor
cables, I still get
On 11/3/22 4:25 PM, Felix Miata wrote:
home user composed on 2022-11-03 15:51 (UTC-0600):
...
Were you previously using a 5.19 kernel and the new kernel is a 6.0? The problem
is NVidia's proprietary driver isn't working, and the fallback driver is too
crude
to support more than one display or m
On Thu, Nov 3, 2022 at 4:45 PM home user wrote:
> I do not see any such logs in the gnome "logview" tool (which is where I
> see the boot and dnf logs). Where are the akmod logs?
/var/cache/akmods/nvidia
--
Jerry James
http://www.jamezone.org/
___
use
On 11/3/22 3:59 PM, Barry wrote:
On 3 Nov 2022, at 21:53, home user wrote:
[... snip ...]
[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start
running (1min 18s / no limit)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start
running (1m
home user composed on 2022-11-03 15:51 (UTC-0600):
...
> This leads me to think that the problem is not with the monitors. The
> display in the one monitor looks a little fuzzy and stretched out
> horizontally. I also notice at the end of the boot log the following lines:
...
> What is the prob
Barry composed on 2022-11-03 21:59 (UTC):
> Seems that you want to use the nvidia driver but it is not compiled and so
> the fallback nouveau is used.
> Guess nouveau does not support 2 monitors.
Nouveau supports 2 monitors, but not when NVidia drivers interfere by
blacklisting
nouveau, which
> On 3 Nov 2022, at 21:53, home user wrote:
>
> (f36)
>
> Good afternoon,
>
> A short while ago, I did my weekly patches (dnf upgrade), and then re-booted.
> Just before that, the workstation display (dual monitor) was fine. After
> the reboot, only one display works. If I switch the mon
(f36)
Good afternoon,
A short while ago, I did my weekly patches (dnf upgrade), and then
re-booted. Just before that, the workstation display (dual monitor) was
fine. After the reboot, only one display works. If I switch the monitor
cables, I still get a one-monitor display, but on the othe
17 matches
Mail list logo
