display is showing in excess of 50 entries for
Thunderbird where all of them have a unique TID value, is
Thunderbird really starting that many threads?
https://serverfault.com/questions/312815/iotop-fields-what-does-tid-mean-in-iotop
Thanks Will, that is what I thought it
On Fri, 2024-11-29 at 09:31 +1100, Stephen Morris wrote:
> When I run IOTOP, the first column is TID, what is TID? This display
> is showing in excess of 50 entries for Thunderbird where all of them
> have a unique TID value, is Thunderbird really starting that many
> threads?
On Thu, 28 Nov 2024 at 22:50, Stephen Morris
wrote:
> On 29/11/24 09:45, Will McDonald wrote:
>
> On Thu, 28 Nov 2024 at 22:31, Stephen Morris
> wrote:
>
>> HI,
>> When I run IOTOP, the first column is TID, what is TID? This display
>> is showing in exc
On 29/11/24 09:45, Will McDonald wrote:
On Thu, 28 Nov 2024 at 22:31, Stephen Morris
wrote:
HI,
When I run IOTOP, the first column is TID, what is TID? This
display is showing in excess of 50 entries for Thunderbird where
all of them have a unique TID value, is Thunderbird
On Thu, 28 Nov 2024 at 22:31, Stephen Morris
wrote:
> HI,
> When I run IOTOP, the first column is TID, what is TID? This display
> is showing in excess of 50 entries for Thunderbird where all of them have a
> unique TID value, is Thunderbird really starting that many threa
HI,
When I run IOTOP, the first column is TID, what is TID? This
display is showing in excess of 50 entries for Thunderbird where all of
them have a unique TID value, is Thunderbird really starting that many
threads?
Also when I run IOTOP I get a display in the middle of the screen
On Sat, Nov 16, 2024 at 09:59:28AM +1100, Stephen Morris wrote:
> ��� While on the subject of HTOP internals, at the bottom of its screen
> it
> shows a list of keyboard shortcuts, one of which is F10 for Exit. The issue
> I have with that is Konsole has taken over that shortcut for its men
On Sat, Nov 16, 2024 at 1:01 PM Robert McBroom via users <
users@lists.fedoraproject.org> wrote:
> In XFCE found a setting I didn't see in LXDE that set suspend to never.
> Working at this point
>
Today, running Gnome Software Update on 2 Fedora Workstation desktop
systems got some message
that
not working in that I occasionally see an entry at
the top where one or more of the 3 % columns is non 0 for a very
short period, but as I have indicated in another thread, it seems to
me that its monitoring may not be up to scratch when the hard disk
light on my machine is hard on, the disk I/O
an entry at the top where
one or more of the 3 % columns is non 0 for a very short period, but as
I have indicated in another thread, it seems to me that its monitoring
may not be up to scratch when the hard disk light on my machine is hard
on, the disk I/O summary display I added in its setting
3 % columns is non 0 for a very short period, but as
I have indicated in another thread, it seems to me that its monitoring
may not be up to scratch when the hard disk light on my machine is hard
on, the disk I/O summary display I added in its settings says the disk
I/O is 100% but its detail
issues: https://www.baeldung.com/linux/monitor-disk-io
Thanks Barry, I'll have a look at that. I have added disk I/O to the
HTOP summary display at the top of its screen which has highlighted, in
my view, that HTOP is doing things wrong, as the summary display says
the disk I/O is 100% bu
access the system from firefox on another
machine
and open a terminal. Is there a command that will restart the
graphical
display?
With the terminal you should be able to find details using
`journalctl`. It would
be very useful to know if the issue is caused by something crashing or
access the system from firefox on another
machine
and open a terminal. Is there a command that will restart the
graphical
display?
With the terminal you should be able to find details using
`journalctl`. It would
be very useful to know if the issue is caused by something crashing or
On 2024-11-15 14:59, Stephen Morris wrote:
Hi,
With the IO tab in HTOP, how do I determine which devices it is
monitoring and how do I change it to look at multiple volumes?
While KDE is still thrashing my hard disks after the desktop
displays (the hard disk light is permanently on, n
em from firefox on another machine
> and open a terminal. Is there a command that will restart the graphical
> display?
>
With the terminal you should be able to find details using `journalctl`.
It would
be very useful to know if the issue is caused by something crashing or by
some
un
> On 15 Nov 2024, at 22:59, Stephen Morris wrote:
>
> (the hard disk light is permanently on, not flickering)
There are better tools for investigating this type of I/O issue.
You could have a read of this article that explains how to track down disk I/O
issues: https://www.baeldung.com/linux
I can
find to never. I can access the system from firefox on another machine
and open a terminal. Is there a command that will restart the graphical
display?
AFAIK, not without restarting the desktop or display manager.
I've used pkill -u "user" to drop back to the display-manage
never. I
can access the system from firefox on another machine and open a terminal. Is
there a command that will restart the graphical display?
I've used pkill -u "user" to drop back to the display-manager but really want
to get to the session as operable or to have it never
On 16/11/24 10:48, Will McDonald wrote:
On Fri, 15 Nov 2024 at 22:59, Stephen Morris
wrote:
While on the subject of HTOP internals, at the bottom of its
screen it shows a list of keyboard shortcuts, one of which is F10
for Exit. The issue I have with that is Konsole has taken over
ystem from firefox on another machine
and open a terminal. Is there a command that will restart the graphical
display?
AFAIK, not without restarting the desktop or display manager.
I've used pkill -u "user" to drop back to the display-manager but really
want to get to the session as
On Fri, 15 Nov 2024 at 22:59, Stephen Morris
wrote:
> While on the subject of HTOP internals, at the bottom of its screen it
> shows a list of keyboard shortcuts, one of which is F10 for Exit. The issue
> I have with that is Konsole has taken over that shortcut for its menus,
> hence it doesn't w
Hi,
With the IO tab in HTOP, how do I determine which devices it is
monitoring and how do I change it to look at multiple volumes?
While KDE is still thrashing my hard disks after the desktop
displays (the hard disk light is permanently on, not flickering) HTOP is
telling me the R/W%, R
gt; and open a terminal. Is there a command that will restart the graphical
> display?
>
>
AFAIK, not without restarting the desktop or display manager.
> I've used pkill -u "user" to drop back to the display-manager but really
> want to get to the session as o
similar to earlier thread. System goes blank and does not resume from
wherever. Using LXDE and have set all the suspend, etc. options I can
find to never. I can access the system from firefox on another machine
and open a terminal. Is there a command that will restart the graphical
display
On 11/3/24 00:03, francis.montag...@inria.fr wrote:
you should look at your ~/.xsession-errors file for errors.
I did. What do you think I was doing all those hours?
I must have gone through 20 articles on how to fix this.
That was indeed mentioned
--
__
Hi.
On Sat, 02 Nov 2024 16:58:25 -0700 ToddAndMargo via users wrote:
> During the troubleshooting I had a fc39 mate live usb fired
> up in a virtual machine. I used the following to hunt down
> all the xsessions, .ICE*, etc.. I could find no difference.
> # find / -iname \*xsess\*
As I said, i
On 11/2/24 06:50, Patrick O'Callaghan wrote:
On Sat, 2024-11-02 at 05:12 -0700, ToddAndMargo via users wrote:
On 11/2/24 04:45, Patrick O'Callaghan wrote:
On Sat, 2024-11-02 at 11:24 +, Patrick O'Callaghan wrote:
On Fri, 2024-11-01 at 17:23 -0700, ToddAndMargo via users wrote:
On 11/1/24
On Sat, 2024-11-02 at 05:12 -0700, ToddAndMargo via users wrote:
> On 11/2/24 04:45, Patrick O'Callaghan wrote:
> > On Sat, 2024-11-02 at 11:24 +, Patrick O'Callaghan wrote:
> > > On Fri, 2024-11-01 at 17:23 -0700, ToddAndMargo via users wrote:
> > > > On 11/1/24 06:02, francis.montag...@inria.
On 11/2/24 04:45, Patrick O'Callaghan wrote:
On Sat, 2024-11-02 at 11:24 +, Patrick O'Callaghan wrote:
On Fri, 2024-11-01 at 17:23 -0700, ToddAndMargo via users wrote:
On 11/1/24 06:02, francis.montag...@inria.fr wrote:
Look in your ~/.xsession-errors or test with a brand new test user.
On Sat, 2024-11-02 at 11:24 +, Patrick O'Callaghan wrote:
> On Fri, 2024-11-01 at 17:23 -0700, ToddAndMargo via users wrote:
> > On 11/1/24 06:02, francis.montag...@inria.fr wrote:
> > > Look in your ~/.xsession-errors or test with a brand new test user.
> >
> > Neither of my own profile or th
On Fri, 2024-11-01 at 17:23 -0700, ToddAndMargo via users wrote:
> On 11/1/24 06:02, francis.montag...@inria.fr wrote:
> > Look in your ~/.xsession-errors or test with a brand new test user.
>
> Neither of my own profile or the two new profiles
> had an xsession-errors file
Just in case: it's .xe
On 11/1/24 06:02, francis.montag...@inria.fr wrote:
At this point you should try to run a "dnf distro-sync" in a protected
way.
Example with systemd-run:
sudo systemd-run -u distro-sync --no-block --service-type=oneshot \
dnf -y distro-sync
Wait for this transient distro-sync unit to
On 11/1/24 06:02, francis.montag...@inria.fr wrote:
Look in your ~/.xsession-errors or test with a brand new test user.
Neither of my own profile or the two new profiles
had an xsession-errors file
--
___
users mailing list -- users@lists.fedoraprojec
On 11/1/24 12:39, Robert McBroom via users wrote:
lightdm works on rawhide f42
From my research, it work in the vast majority
of cases. But if you are one of the "unlucky" ones,
yo will learn a few new swear words. (Not an
admission that I cuss.)
--
_
Screen lock and power management aren't working either
On Fri, Nov 1, 2024 at 8:11 PM Max Pyziur wrote:
>
> > On 11/01/2024 2:27 PM EDT Max Pyziur wrote:
> >
> >
> > Greetings,
> >
> > While trying a two-screen setup with my Dell XPS 13 (9380), I&#x
> On 11/01/2024 2:27 PM EDT Max Pyziur wrote:
>
>
> Greetings,
>
> While trying a two-screen setup with my Dell XPS 13 (9380), I've lost my
> display settings and I can't seem to be able to restore them.
>
> The laptop's display specs
On 11/1/24 9:02 AM, francis.montag...@inria.fr wrote:
lightdm nor slick-greeter (since January, for F39 and F40).
I suspect a change in your account profiles (shell for example).
Look in your ~/.xsession-errors or test with a brand new test user.
Funny. I liked the version of Thunderbird on
Greetings,
While trying a two-screen setup with my Dell XPS 13 (9380), I've lost my
display settings and I can't seem to be able to restore them.
The laptop's display specs are 1920 x 1080. But even though I get an
approximation, when I reboot, the configuration isn't sa
On Fri, 01 Nov 2024 04:57:23 -0700 ToddAndMargo via users wrote:
> On 11/1/24 02:16, francis.montag...@inria.fr wrote:
>> Is it the machine where you did a system-upgrade to F40 ? (with
>> duplicates systemd RPMs ... at least).
> This is that same system. I cloned it back to
> fc39. After a dnf
On 11/1/24 02:16, francis.montag...@inria.fr wrote:
Is it the machine where you did a system-upgrade to F40 ? (with
duplicates systemd RPMs ... at least).
Tihs is that same system. I cloned it back to
fc39. After a dnf update, lightdm stopped working.
Funny. I liked the version of Thunderbi
On Fri, 01 Nov 2024 01:26:09 -0700 ToddAndMargo via users wrote:
> On 11/1/24 01:15, francis.montag...@inria.fr wrote:
>> Elaborate please: we are using lightdm on hundreds of machines
>> without issues, except on a few of them using nvidia-340xx ...
> I am not using an nvidia graphics card.
> I
On 11/1/24 01:14, Stephen Morris wrote:
No problems, glad it's working now.
regards,
Steve
I must have spent 16 hours trying to fix this.
About killed me.
I am tickled with lxdm.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscr
On 1/11/24 19:04, ToddAndMargo via users wrote:
On 11/1/24 00:58, Stephen Morris wrote:
On 1/11/24 14:20, ToddAndMargo via users wrote:
# systemctl status display-manager.service
Unit display-manager.service could not be found.
What display-manager are you actually using, is it sddm, gdm or
Hi.
On Fri, 01 Nov 2024 01:04:01 -0700 ToddAndMargo via users wrote:
> Turns out I have no issues with x running. The problem
> is lightdm;
> I am stuck in the "endless loop" problem that is plaguing
> lightdm users.
Elaborate please: we are using lightdm on undreds of machines without
issues,
On 11/1/24 01:15, francis.montag...@inria.fr wrote:
Hi.
On Fri, 01 Nov 2024 01:04:01 -0700 ToddAndMargo via users wrote:
Turns out I have no issues with x running. The problem
is lightdm;
I am stuck in the "endless loop" problem that is plaguing
lightdm users.
Elaborate please: we are usi
On 11/1/24 00:58, Stephen Morris wrote:
On 1/11/24 14:20, ToddAndMargo via users wrote:
# systemctl status display-manager.service
Unit display-manager.service could not be found.
What display-manager are you actually using, is it sddm, gdm or
something different.
Lets say you are using gdm
On 1/11/24 14:20, ToddAndMargo via users wrote:
# systemctl status display-manager.service
Unit display-manager.service could not be found.
What display-manager are you actually using, is it sddm, gdm or
something different.
Lets say you are using gdm with Gnome, what does systemctl display
Fedora 39
How do I check to see if my xorg display manager is running?
# systemctl status display-manager.service
Unit display-manager.service could not be found.
# dnf provides display-manager
...
Error: No matches found.
Many thanks,
-T
On 7/29/24 9:42 AM, bruce wrote:
I'm looking to update the permissions of a bunch of folders within a
dir (not recursively), but I'd like to display the dirs prior to
making changes -- measure twice, then cut.
find /etc/*/ -maxdepth 0 -type d -exec ls -dal {} \;
--seems to display t
g to update the permissions of a bunch of folders within a
> dir (not recursively), but I'd like to display the dirs prior to
> making changes -- measure twice, then cut.
>
> find /etc/*/ -maxdepth 0 -type d -exec ls -dal {} \;
> --seems to display the list of dirs for the test
Hi
I'm looking to update the permissions of a bunch of folders within a
dir (not recursively), but I'd like to display the dirs prior to
making changes -- measure twice, then cut.
find /etc/*/ -maxdepth 0 -type d -exec ls -dal {} \;
--seems to display the list of dirs for the test fo
On 4/30/24 2:23 AM, Javier Perez wrote:
What kernel are you using?
The bad patching ("dnf upgrade" early this month) was from
6.7.11-100.fc38x86_64 to 6.8.4-100.fc38x86_64.
The good patching Saturday was from 6.7.11-100.fc38x86_64 to
6.8.7-100.fc38x86_64.
The full upgrade ("dnf system-upgra
(a second time?!).
> > During the boot-up, there was a message that it was failing back to
> nouveau.
> > The display is not working properly; only one monitor is being used and
> everything is oversized in the display.
> > I am not comfortable proceeding with the f-38 to f-
ics driver were replaced
during this "dnf upgrade".
The akmods did finish before I rebooted.
The shutdown took 5 minutes because it ran akmods (a second time?!).
During the boot-up, there was a message that it was failing back to nouveau.
The display is not working properly; only one monit
5 minutes because it ran akmods (a second time?!).
During the boot-up, there was a message that it was failing back to
nouveau.
The display is not working properly; only one monitor is being used
and everything is oversized in the display.
I am not comfortable proceeding with the f-38 to f-39 up
On 4/15/24 14:02, home user wrote:
On 4/11/24 11:19 AM, home user wrote:
There's
1.
(Thomas)
I finally just nuked all the RPMFusion packages and downloaded the
drivers directly from https://www.nvidia.com/download/index.aspx and
ran the installer from there. It works fine again.
(To
time?!).
During the boot-up, there was a message that it was failing back to nouveau.
The display is not working properly; only one monitor is being used and
everything is oversized in the display.
I am not comfortable proceeding with the f-38 to f-39 upgrade with the work
station in this condition
On 4/14/24 17:21, Michael D. Setzer II via users wrote:
So, not sure why it works with 6.7.x but not with 6.8.x.
Something changed in the kernel and the NVidia driver needs to be
changed to work with it. The driver is out of tree so it doesn't get
fixed by the people making the change like t
On 14 Apr 2024 at 18:50, John Pilkington wrote:
Date sent: Sun, 14 Apr 2024 18:50:40 +0100
Subject:Re: crippling nvidia display issue.
To: users@lists.fedoraproject.org
From: John Pilkington
Send reply to: Community
On 14/04/2024 16:22, Michael D. Setzer II via users wrote:
On 15 Apr 2024 at 0:29, Michael D. Setzer II via user wrote:
Just as an additional note. I have an older Acer notebook that has
an NVIDIA GT 650M that had been working fine with the
rpmfusion driver. Have BOINC using its GPU for a pro
On 15 Apr 2024 at 0:29, Michael D. Setzer II via user wrote:
To: Community support for Fedora users
Date sent: Mon, 15 Apr 2024 00:29:38 +1000
Subject:Re: crippling nvidia display issue.
Priority: normal
Send reply to: mi
On 14 Apr 2024 at 12:47, John Pilkington wrote:
Date sent: Sun, 14 Apr 2024 12:47:57 +0100
Subject:Re: crippling nvidia display issue.
From: John Pilkington
To: users@lists.fedoraproject.org
Send reply to: Community
On 12/04/2024 12:58, John Pilkington wrote:
On 12/04/2024 00:52, home user wrote:
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/_
> On 12 Apr 2024, at 01:06, Tom Horsley wrote:
>
> 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
> kernels in my old fedora 38 partition are also -200, not -100.
The -NNN is the version that is
On 12/04/2024 00:52, home user wrote:
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/n
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
curren
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 regula
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 yadda-ya
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 min
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
kern
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: 'DRM_UN
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 functi
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'?
Th
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 sor
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 n
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 [F
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
/var/c
ics driver were replaced
during this "dnf upgrade".
The akmods did finish before I rebooted.
The shutdown took 5 minutes because it ran akmods (a second time?!).
During the boot-up, there was a message that it was failing back to nouveau.
The display is not working properly; only one monit
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
> /var/cache
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 d
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 pr
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 kerne
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 d
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 t
iver
were replaced during this "dnf upgrade".
The akmods did finish before I rebooted.
The shutdown took 5 minutes because it ran akmods (a second time?!).
During the boot-up, there was a message that it was failing back to
nouveau.
The display is not working properly; only one monit
uot;dnf upgrade".
The akmods did finish before I rebooted.
The shutdown took 5 minutes because it ran akmods (a second time?!).
During the boot-up, there was a message that it was failing back to nouveau.
The display is not working properly; only one monitor is being used and
everything is over
Hi guys.
Would you know how to disable/tweak bits in kernel/module so
display(& audio) is completely disabled?
I have AMD RX 6600 which I hope I could give completely to
ROCm for computing.
many thanks, L.--
___
users mailing list -- u
On 11/23/23 8:00 PM, home user wrote:
I would like to run a memory test. Does what Fedora offers now work? I recall
from a previous thread that it does not. If it does, please remind me how to
install it.
It's memtest86+.
It's on my work station, accessed during boot-up via the grub menu.
used "less -r /var/log/boot.log" you'd see them displayed using
the colour codes to colour the display. And if you really wanted to,
you could pipe them through something to strip them out, or use them
without showing them, then copy and paste.
less -r /var/log/boot.log|gre
On 11/23/23 8:52 PM, Samuel Sieb wrote:
On 11/23/23 19:00, home user wrote:
I'm as much at a loss as you as to what really happened in the mid-day dnf
commands. I'm also at a loss as to why the clean-up this evening had so many
failures.
It kind of sounds like the earlier upgrade failed som
On 11/23/23 19:00, home user wrote:
I'm as much at a loss as you as to what really happened in the mid-day
dnf commands. I'm also at a loss as to why the clean-up this evening
had so many failures.
It kind of sounds like the earlier upgrade failed somehow. You could
check the logs from that
;less -r /var/log/boot.log" you'd see them displayed using
the colour codes to colour the display. And if you really wanted to,
you could pipe them through something to strip them out, or use them
without showing them, then copy and paste.
less -r /var/log/boot.log|grep ounted
[ OK
On 11/23/23 5:53 PM, Samuel Sieb wrote:
On 11/23/23 16:07, home user wrote:
On 11/23/23 5:04 PM, Samuel Sieb wrote:
On 11/23/23 16:00, home user wrote:
On 11/23/23 4:56 PM, Samuel Sieb wrote:
On 11/23/23 15:39, home user wrote:
Where is the "6.5.12" kernel coming from, since you don't act
On 11/23/23 16:07, home user wrote:
On 11/23/23 5:04 PM, Samuel Sieb wrote:
On 11/23/23 16:00, home user wrote:
On 11/23/23 4:56 PM, Samuel Sieb wrote:
On 11/23/23 15:39, home user wrote:
Where is the "6.5.12" kernel coming from, since you don't actually
have it installed? Try dnf upgrad
On 11/23/23 5:04 PM, Samuel Sieb wrote:
On 11/23/23 16:00, home user wrote:
On 11/23/23 4:56 PM, Samuel Sieb wrote:
On 11/23/23 15:39, home user wrote:
Where is the "6.5.12" kernel coming from, since you don't actually have it
installed? Try dnf upgrading your kernel.
--
--
-bash.12[
On 11/23/23 16:00, home user wrote:
On 11/23/23 4:56 PM, Samuel Sieb wrote:
On 11/23/23 15:39, home user wrote:
Where is the "6.5.12" kernel coming from, since you don't actually
have it installed? Try dnf upgrading your kernel.
--
--
-bash.12[~]: uname -a
Linux coyote 6.5.12-200.fc3
On 11/23/23 4:56 PM, Samuel Sieb wrote:
On 11/23/23 15:39, home user wrote:
Where is the "6.5.12" kernel coming from, since you don't actually have it
installed? Try dnf upgrading your kernel.
--
--
-bash.12[~]: uname -a
Linux coyote 6.5.12-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Mon No
1 - 100 of 1069 matches
Mail list logo
