Power management
by Celso Viana
Hi all,
I set Fedora 38 Workstation's power mode to performance, but if any
user doesn't login the computer hibernates. How do I change this
behavior so that the computer does not go to sleep if there is no user
logged in?
Thanks
--
Celso Vianna
BSD User: 51318
http://www.bsdcounter.org
Palmas/TO
6 months, 3 weeks
Re: Power management
by Iosif Fettich
Hi,
merely out of curiosity, I asked your question on ChatGPT. Here's the answer:
---
To prevent Fedora from going to sleep when no user is logged in, you can modify
the power settings and systemd configurations. Here are the steps to change
this behavior:
1. Open Terminal: Open a terminal on your Fedora system.
2. Check the Current Power Settings:
To see the current power settings, you can use the following command:
bash
gsettings list-recursively org.gnome.settings-daemon.plugins.power
This will show you the current values and settings for power management.
3. Modify Power Settings:
To change the behavior when no user is logged in, you can set the
sleep-inactive-ac-timeout and sleep-inactive-battery-timeout values to -1,
which effectively disables sleep. Run the following commands:
bash
gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout
-1
gsettings set org.gnome.settings-daemon.plugins.power
sleep-inactive-battery-timeout -1
4. Check Systemd Configuration:
You should also check your systemd configuration to ensure that it's not
overriding your power settings. Run the following command to display the
current settings:
bash
sudo systemctl show sleep.target
Look for a line that starts with InactiveExitTimestamp. If it's set to yes, it
means the system will go to sleep when no user is logged in. To disable this,
run the following command:
bash
sudo systemctl mask sleep.target suspend.target hibernate.target
hybrid-sleep.target
5. Reboot: After making these changes, it's a good idea to reboot your
system to ensure that the new settings take effect.
After following these steps, your Fedora system should no longer go to sleep
when no user is logged in, even when the power mode is set to "performance."
---
Seems quite ok to me...
Best regards,
Iosif Fettich
6 months, 3 weeks
what's the trick to get hardlink to use sha256 in docker?
by Curtis Doty
$ docker run --rm --interactive --tty fedora:39 hardlink -nv /dev/null
cannot initialize sha256 method, use 'memcmp' fallback
Mode: dry-run
Method: memcmp
Files: 0
Linked: 0 files
Compared: 0 xattrs
Compared: 0 files
Saved: 0 B
Duration: 0.001141 seconds
6 months, 3 weeks
fc38 in fc39?
by ToddAndMargo
One of my Fedora machines I just upgraded from fc38
to fc39 still have a ton of fc38 stuff in it. Is
that normal?
`uname -a` and `cat /etc/redhat-release` all say I
am on fc39.
But when I go to do a `dnf upgrade` I get tons of
fc38 stuff to upgrade to a newer fc38 version.
Am I missing something?
Perplexed,
-T
6 months, 3 weeks
f38 live workstation and network manager wait online
by Tom Horsley
Just noticed this while testing my multi-boot USB stick with scads
of ISO images:
In Fedora 39, the boot spends an annoying amount of time imagining
that it can wait for a network to be up, but the physical ethernet
port is connected (via crossover cable) to a device which will definitely
not be providing any DHCP. I suspect if I unplugged the cable, it would
boot faster since nothing would look like a live signal.
I tried booting the Fedora 38 workstation live ISO, and it didn't
spend a lot of time waiting for the network, so something is different
from f38 to f39 (maybe the "no limit" timeout?).
They both eventually booted up, so it obviously isn't a major issue.
6 months, 3 weeks
[Testdays] Call for Fedora Linux 40 testing events
by Sumantro Mukherjee
Hi Fedora users, developers, and friends!
It's time to start thinking about Test Days for Fedora 40.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/624 . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development
schedule, though, in deciding when you want to run your Test Day - for
some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific time frame due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or time frame you'd
like, and we'll figure it out from there.
If you don't want to run your own Test Day, but you are willing to
help with another, feel free to join one or more of already accepted
Test Days:
GNOME Test Day*
i18n Test Day*
Kernel Test Week(s)*
Upgrade Test Day*
IoT Test Week*
Cloud Test Day*
Fedora CoreOS Test Week*
And don't be afraid, there are a lot of more slots available for your
own Test Day!
[*] These are the test days we run generally to make sure everything
is working fine, the dates get announced as we move into the release
cycle.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on IRC. Thanks!
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
6 months, 3 weeks
freaking TFTP
by lejeczek
Hi guys.
cannot get a client to get anything from 'in.tftp' server?
Connection seems to get established, _tcpdump_ shows:
...
13:13:08.331277 IP 10.3.1.100.35176 > whale.mine.priv.tftp:
TFTP, length 19, RRQ "zabbix.zip" octet
13:13:13.331324 IP 10.3.1.100.35176 > whale.mine.priv.tftp:
TFTP, length 19, RRQ "zabbix.zip" octet
...
journal log for tftp.service, so on the servers, shows:
...
tftpd: read(ack): No route to host
...
any & all thoughts on how troubleshoot & fix this are much
appreciated.
many thanks, L.
6 months, 3 weeks
NVidia Tesla trouble in both F38 & F39
by Felix Miata
3 different Tesla cards involved so far: GT210 (not mine) plus G98 and GT218 mine.
Without the workaround, screen locks in black except for a few random portions of
80x25 mode characters in upper left.
Bad kernels include 6.4.16, 6.5.9 & 6.5.10. OK without workaround: 6.3.12. Which
kernels work OK without workaround seem to vary with which NVidia/PC combination.
These are slow booting oldsters with no more than 2 CPU threads (here at least).
Worse, the G98 is a PCI card, not PCIe. :(
<https://www.linuxquestions.org/questions/linux-desktop-74/kernel-6-5-9-gt...>
has the original details.
Known workaround so far here is to include vga=791 on kernel cmdline.
Not yet tried on Fermis, and not yet tried forced inclusion of nouveau.ko in initrd.
From one of 3 PCs involved:
# inxi -GSaz --vs --zl --hostname
inxi 3.3.31-00 (2023-11-02)
System:
Host: g5eas Kernel: 6.5.10-300.fc39.x86_64 arch: x86_64 bits: 64
compiler: gcc v: 2.40-13.fc39 clocksource: tsc available: hpet,acpi_pm
parameters: ro root=LABEL=<filter> noresume selinux=0 audit=0
ipv6.disable=1 net.ifnames=0 plymouth.enable=0 consoleblank=0
mitigations=off vga=791
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 7 dm:
1: KDM 2: XDM Distro: Fedora release 39 (Thirty Nine)
Graphics:
Device-1: NVIDIA G98 [GeForce 8400 GS Rev. 2] vendor: PNY driver: nouveau
v: kernel non-free: series: 340.xx status: legacy (EOL~2019-12-xx) last:
release: 340.108 kernel: 5.4 xorg: 1.20 arch: Tesla process: 40-80nm
built: 2006-2013 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 link-max: lanes: 16
ports: active: DVI-I-1,VGA-1 empty: none bus-ID: 0b:00.0
chip-ID: 10de:06e4 class-ID: 0300
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: nouveau gpu: nouveau display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00")
s-diag: 803mm (31.62")
Monitor-1: DVI-I-1 pos: primary,left model: NEC EA243WM serial: <filter>
built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
Monitor-2: VGA-1 pos: right model: Dell P2213 serial: <filter> built: 2012
res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65")
diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 egl: 1.4
drv: nouveau device: 1 drv: swrast surfaceless: egl: 1.4 drv: nouveau x11:
egl: 1.4 drv: nouveau inactive: gbm,wayland
API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 23.2.1 glx-v: 1.4
direct-render: yes renderer: NV98 device-ID: 10de:06e4 memory: 483.4 MiB
unified: no
#
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
6 months, 3 weeks
Cups shared print now showing in Windows
by ToddAndMargo
Hi All,
Fedora 38
cups-2.4.7-1.fc38.x86_64
cups-lpd-2.4.7-1.fc38.x86_64
My old printer broke, so I had to replace it.
I removed the old printer from cups and added the
new printer. I set the new printer to network
share (and it does over LPD).
/etc/printcap:
# This file was automatically generated by cupsd(8) from the
# /etc/cups/printers.conf file. All changes to this file
# will be lost.
HLL2300D|HLL2300D:rm=server.acme.local:rp=HLL2300D:
Cups-PDF|Cups-PDF:rm=server.acme.local:rp=Cups-PDF:
"Cups-PDF" shows in the Windows 10 "add printer" dialog,
but my new HLL2300D does not.
I have cups-lpd installed, so I just did a manual create
port lpd and my new printer works fine from Windows 10.
But, why can Windows 10's "Add Printer" dialog find it?
Perplexed,
-T
6 months, 3 weeks
