AMD Ryzen laptop does not resume from sleep at random
by lejeczek
Hi guys.
I have a Lenovo E14 Gen2 which sports AMD Ryzen 4500U which
has recently became very annoying.
I do not shut the system off but, like many other I presume,
put it to sleep, or system does it automatically.
Resuming is the problem, sometimes. It's third sometimes Nth
time, previous times it would wake up, where system instead
of to wake up, freezes.
When it freezes, screens stay blank/black, I have an
external Dell monitor connected all the time as well as
external USB ThinkPad keyboard (in case somebody sees the
same problem in their config). Only power LED changes to
state saying it's back on, not sleeping.
I wonder if somebody might have any suggestions. My first
thought was tweaking, adding some kernel parameters but will
have to research that.
many thanks, L
3 years
- 3
- 2
Fedora 34 Works on a T500
by John Mellor
Kudos to the Fedora 34 and Gnome teams!!!
My Lenovo Thinkpad T500 runs Linux very well. Its a beat-up,
12-year-old, well-equipped dual-core laptop with 8GB ram, a Core2 Duo
cpu with an AMD Rv635 gpu. Its a good machine for meetings, as it is
quite rugged and mostly survives being dropped, coffee spills, etc.
Best of all, its highly secure with hardware that is not subject to the
problems related to later-generation Intel processor design faults, etc.
Fedora 24 through 32 just worked on this laptop. Updates were almost
seamless, and all was good.
Early Fedora 33 was a big disappointment, as it had serious font issues
in the message dropdowns and other places that made it semi-unusable,
and with later updates it would not even show a Gnome screen. I
reinstalled it several times to confirm that the hardware was ok. I
could never find any logs detailing why it didn't work, so I switched to
installing Ubuntu 20.10 as working much more correctly on this hardware
with the same version of Gnome.
Last week I did a fresh install of Fedora 34 pre-beta, and it just
worked. It continues to work with the hundreds of updates that are
being pushed. Fedora is back. Thanks!
3 years
- 3
- 2
RE: Fedora 34 Works on a T500
by J.Witvliet＠mindef.nl
See below
-----Original Message-----
From: John Mellor <john.mellor(a)gmail.com>
Sent: Thursday, April 1, 2021 2:50 PM
To: users(a)lists.fedoraproject.org
Subject: Fedora 34 Works on a T500
Kudos to the Fedora 34 and Gnome teams!!!
My Lenovo Thinkpad T500 runs Linux very well. Its a beat-up, 12-year-old, well-equipped dual-core laptop with 8GB ram, a Core2 Duo cpu with an AMD Rv635 gpu. Its a good machine for meetings, as it is quite rugged and mostly survives being dropped, coffee spills, etc. Best of all, its highly secure with hardware that is not subject to the problems related to later-generation Intel processor design faults, etc.
Fedora 24 through 32 just worked on this laptop. Updates were almost seamless, and all was good.
Early Fedora 33 was a big disappointment, as it had serious font issues in the message dropdowns and other places that made it semi-unusable, and with later updates it would not even show a Gnome screen. I reinstalled it several times to confirm that the hardware was ok. I could never find any logs detailing why it didn't work, so I switched to installing Ubuntu 20.10 as working much more correctly on this hardware with the same version of Gnome.
Last week I did a fresh install of Fedora 34 pre-beta, and it just worked. It continues to work with the hundreds of updates that are being pushed. Fedora is back. Thanks!
-----Original Message-----
Hi,
The ${SUBJECT} Surprised me.
Long, long time ago, i was part of the team that did the porting of Linux onto the T500.
However, that was abt 20 years ago, and the target was the HP T500 with a couple of PARISC CPU's.
I hope your machine consumes less electricity :-)
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
3 years
- 1
- 0
Desktop crash during a `dnf upgrade`, will this be a problem now?
by Qiyu Yan
Hi! folks,
Just now during a routine update using `dnf update` my desktop process
gnome-shell crashed.
Afterwards, I checked dnf history and /var/log/dnf.log to see if any
inconsistency is present. dnf.log didn't report the last transaction
as completed, but `dnf history info last` report the action was
successful. luckily, I didn't see any inconsistency in my system. I
just have to manually clean rpm files left in cache.
Seems that dnf is killed just when transaction done, before it can
write to dnf.log? While is it possible that dnf gets killed during
transaction and breaks the system when desktop session dies? Do we
have a approach to avoid this? Like telling dnf to ignore signals when
doing important things (does dnf have this already?)
--
Best regards,
Qiyu Yan
3 years
- 2
- 1
Suggestion to improve documentation of
Changes/BtrfsTransparentCompression
by misterx42＠protonmail.com
Just a small thing, but as someone who never actually played around with filesystems so far, I was looking to try out the changes outlined in Changes/BtrfsTransparentCompression, but the command on the page:
btrfs filesystem defrag -czstd -r
doesnt work without an additional argument. This is pretty obvious for people who already worked with filesystems before, but I think it would be a good idea to add a small, one sentence explanation of how to add the required path to the end of the command (ie / in my case). It would help people like me from getting confused and hopefully bring in more casual tinkerers trying the new change out.
Thanks.
3 years
- 4
- 6