night light mode
by Patrick Dupre
Hello,
Since I set the night light mode in manual, I cannot return to
automatic mode.
How can I change this set up to default?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
5 years, 6 months
Trying to get gpt + software raid + LVM in kickstart
by Digimer
Hi all,
I've for a Fedora 28 kickstart file booting from a PXE server. I can't
seem to work out the magic incantation to format it though.
Here's the PXE invocation (note 'inst.gpt');
====
kernel fedora28/vmlinuz
append initrd=fedora28/initrd.img
root=live:http://10.1.4.1/fedora28/x86_64/os/images/install.img
inst.stage2=http://10.1.4.1/fedora28/x86_64/os/ ip=dhcp
inst.ks=http://10.1.4.1/fedora28/x86_64/kickstart/striker.ks inst.gpt
inst.sshd
====
The partition section in the kickstart is;
====
zerombr
clearpart --all --drives=/dev/vda,/dev/vdb
ignoredisk --only-use=/dev/vda,/dev/vdb
bootloader --location=mbr --driveorder=/dev/vda,/dev/vdb
--boot-drive=/dev/vda
# biosboot
part biosboot --fstype=biosboot --size=2 --ondisk=/dev/vda
part biosboot --fstype=biosboot --size=2 --ondisk=/dev/vdb
part raid.11 --size 1024 --ondisk=/dev/vda
part raid.12 --size 1024 --ondisk=/dev/vdb
raid /boot --fstype=ext4 --device=md0 --level=RAID1 raid.11 raid.12
# LVM PV
part raid.21 --size 100 --grow --ondisk=/dev/vda
part raid.22 --size 100 --grow --ondisk=/dev/vdb
raid pv.1 --fstype=lvmpv --device=md1 --level=RAID1 raid.21 raid.22
# LVM Volume groups
volgroup striker_69E6A4A0 pv.1
# LVM logical volumes
logvol swap --fstype=swap --size=4096 --name=lv_swap
--vgname=striker_69E6A4A0
logvol / --fstype=xfs --size=16382 --name=lv_root
--vgname=striker_69E6A4A0
====
I zero out the two disks in the client machine;
====
[anaconda root@localhost ~]# parted /dev/vda print free
Error: /dev/vda: unrecognised disk label
Model: Virtio Block Device (virtblk)
Disk /dev/vda: 21.5GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
[anaconda root@localhost ~]# parted /dev/vdb print free
Error: /dev/vdb: unrecognised disk label
Model: Virtio Block Device (virtblk)
Disk /dev/vdb: 21.5GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
====
When I run the install, it fails with:
====
('new lv is too large to fit in free space', 'striker_69E6A4A0')
====
When I log into the server, it shows that nothing was done on the disks;
====
[anaconda root@localhost ~]# parted /dev/vda print free
Error: /dev/vda: unrecognised disk label
Model: Virtio Block Device (virtblk)
Disk /dev/vda: 21.5GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
[anaconda root@localhost ~]# parted /dev/vdb print free
Error: /dev/vdb: unrecognised disk label
Model: Virtio Block Device (virtblk)
Disk /dev/vdb: 21.5GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
====
Here's the anaconda log:
====
[anaconda root@localhost ~]# cat /tmp/anaconda.log
09:00:17,113 INF main: /sbin/anaconda 28.22.10-1.fc28
09:00:17,450 INF isys: 2171368 kB (2120 MB) are available
09:00:17,466 INF startup_utils: check_memory(): total:2120, needed:320,
graphical:410
09:00:17,480 INF main: anaconda called with cmdline = ['/sbin/anaconda']
09:00:17,480 INF main: Default encoding = utf-8
09:00:17,546 INF dbus.connection: Connecting to a default bus at
unix:abstract=/tmp/dbus-Rktjjl7n4T,guid=efed0a38c7f04387181cd3025bffaaa1.
09:00:18,331 INF startup_utils: Waiting 60 sec for modules to be started.
09:00:19,334 INF startup_utils: Waiting 59 sec for modules to be started.
09:00:20,337 INF startup_utils: Waiting 58 sec for modules to be started.
09:00:21,341 INF startup_utils: Waiting 57 sec for modules to be started.
09:00:22,504 INF startup_utils: Parsing kickstart: /run/install/ks.cfg
09:00:22,584 ERR core.util: Failed to import module docker from path
/usr/share/anaconda/addons/com_redhat_docker/ks/docker.py in collect: No
module named 'pyanaconda.iutil'
09:00:24,134 WRN kickstart: Command firstboot will be parsed in DBus module.
09:00:24,136 WRN kickstart: Command keyboard will be parsed in DBus module.
09:00:24,136 WRN kickstart: Command timezone will be parsed in DBus module.
09:00:24,137 WRN kickstart: Command lang will be parsed in DBus module.
09:00:24,137 WRN kickstart: Command rootpw will be parsed in DBus module.
09:00:24,139 WRN kickstart: Command zerombr will be parsed in DBus module.
09:00:24,139 WRN kickstart: Command clearpart will be parsed in DBus module.
09:00:24,139 WRN kickstart: Command ignoredisk will be parsed in DBus
module.
09:00:24,142 WRN misc:
/usr/lib/python3.6/site-packages/pykickstart/commands/partition.py:416:
UserWarning: A partition with the mountpoint biosboot has already been
defined.
warnings.warn(_("A partition with the mountpoint %s has already been
defined.") % pd.mountpoint)
09:00:24,492 DBG localization: setting locale to: en_CA.UTF-8
09:00:24,546 DBG network: devices found ['ens12', 'ens3']
09:00:24,587 DBG network: ensure single initramfs connections
09:00:24,805 DBG network: apply kickstart
09:00:24,855 WRN network: apply kickstart: --device does not exist
09:00:24,858 DBG network: create missing ifcfg files
09:00:25,305 DBG network: set real ONBOOT value
09:00:25,332 WRN network: set ONBOOT: --device does not exist
09:00:25,339 INF threading: Running Thread: AnaWaitForConnectingNMThread
(140225530734336)
09:00:25,342 DBG anaconda: setting display mode to TUI
09:00:25,356 WRN stdout: Not asking for VNC because of an automated install
09:00:25,357 WRN stdout: Not asking for VNC because text mode was
explicitly asked for in kickstart
09:00:25,360 INF anaconda: Display mode is set to 'interactive text mode'.
09:00:25,362 INF isys: 2171368 kB (2120 MB) are available
09:00:25,383 INF startup_utils: check_memory(): total:2120, needed:320,
graphical:410
09:00:25,493 INF network: got 0 NTP servers from DHCP
09:00:25,500 INF threading: Thread Done: AnaWaitForConnectingNMThread
(140225530734336)
09:00:25,517 DBG installclass: Searching
/usr/lib64/python3.6/site-packages/pyanaconda/installclasses.
09:00:25,536 DBG installclass: Found Fedora (FedoraBaseInstallClass).
09:00:25,536 DBG installclass: Found Atomic Host (AtomicHostInstallClass).
09:00:25,537 DBG installclass: Found Red Hat Enterprise Linux
(RHELBaseInstallClass).
09:00:25,537 DBG installclass: Found Fedora (DefaultInstallClass).
09:00:25,537 DBG installclass: Found Fedora Server
(FedoraServerInstallClass).
09:00:25,538 DBG installclass: Found Scientific Linux
(ScientificBaseInstallClass).
09:00:25,538 DBG installclass: Found Fedora Workstation
(FedoraWorkstationInstallClass).
09:00:25,539 DBG installclass: Found CentOS Linux (CentOSBaseInstallClass).
09:00:25,539 INF installclass: Using a visible install class Fedora
Server (FedoraServerInstallClass).
09:00:26,444 DBG payload: getting release version from tree at None (28)
09:00:26,445 DBG payload: using default release version of 28
09:00:26,449 INF bootloader: bootloader GRUB2 on X86 platform
09:00:26,452 INF autopart: Detected 2.07 GiB of memory
09:00:26,453 INF autopart: Suggested swap size (2.07 GiB) exceeds 10 %
of disk space, using 10 % of disk space (0.0) instead.
09:00:26,454 INF autopart: Swap attempt of 0.0
09:00:26,456 INF bootloader: bootloader GRUB2 on X86 platform
09:00:26,630 DBG storage_utils: LABEL=OEMDRV matches [] for
devicetree=None and disks_only=True
09:00:26,637 INF threading: Running Thread: AnaStorageThread
(140225530734336)
09:00:26,644 INF threading: Running Thread: AnaTimeInitThread
(140225428047616)
09:00:26,708 DBG payload: Restarting payload thread
09:00:26,710 INF threading: Running Thread: AnaPayloadRestartThread
(140225419654912)
09:00:26,711 INF geoloc: Geolocation is disabled due to automated
kickstart based installation.
09:00:26,713 INF threading: Running Thread: AnaPayloadThread
(140225411262208)
09:00:26,714 INF threading: Thread Done: AnaPayloadRestartThread
(140225419654912)
09:00:26,715 DBG payload: Updating payload thread state: 0
09:00:26,721 DBG payload: Updating payload thread state: 1
09:00:26,873 DBG simpleline: GLib event loop is used!
09:00:27,004 INF threading: Thread Done: AnaTimeInitThread (140225428047616)
09:00:27,020 INF lifecycle: Adding controller: SummaryHub
09:00:27,031 INF lifecycle: Module initialized: TimeSpoke
09:00:27,439 INF lifecycle: Module initialized: LangSpoke
09:00:27,445 INF threading: Running Thread: AnaSoftwareWatcher
(140225428047616)
09:00:27,447 INF threading: Running Thread: AnaSourceWatcher
(140225419654912)
09:00:27,455 INF threading: Running Thread: AnaStorageWatcher
(140225402869504)
09:00:28,399 INF lifecycle: Module initialized: NetworkSpoke
09:00:28,423 INF lifecycle: Module initialized: PasswordSpoke
09:00:28,502 WRN ui.tui.hubs: Spoke PasswordSpoke initialization failure!
09:00:28,506 INF lifecycle: Module initialized: UserSpoke
09:00:28,508 WRN ui.tui.hubs: Spoke UserSpoke initialization failure!
09:00:28,509 INF lifecycle: Initialization of all modules (8) has been
started.
09:00:29,749 INF threading: Thread Done: AnaStorageThread (140225530734336)
09:00:29,750 DBG payload: Updating payload thread state: 2
09:00:29,751 DBG payload: Updating payload thread state: 4
09:00:29,754 INF lifecycle: Module initialized: StorageSpoke
09:00:29,755 INF threading: Thread Done: AnaStorageWatcher (140225402869504)
09:00:29,798 DBG payload: getting release version from tree at
http://10.1.4.1/fedora28/x86_64/os/ (28)
09:00:29,798 DBG payload: retrieving treeinfo from
http://10.1.4.1/fedora28/x86_64/os/ (proxy: ; sslverify: True)
09:00:29,798 INF payload: Trying to download '.treeinfo'
09:00:29,805 DBG payload: Retrieved '.treeinfo' from
http://10.1.4.1/fedora28/x86_64/os/
09:00:29,807 DBG payload: using treeinfo release version of 28
09:00:29,846 DBG payload: Updating payload thread state: 5
09:00:30,555 INF payload: Refreshing environmentAddons
09:00:30,562 DBG payload: Updating payload thread state: 6
09:00:30,563 DBG ui.tui.spokes.software_selection: Payload restarted,
set new info and clear the old one.
09:00:30,564 INF threading: Thread Done: AnaPayloadThread (140225411262208)
09:00:30,564 DBG ui.tui.spokes.software_selection: Apply called old env
None, new env None and addons set()
09:00:30,564 INF lifecycle: Module initialized: SoftwareSpoke
09:00:30,565 INF threading: Thread Done: AnaSoftwareWatcher
(140225428047616)
09:00:30,566 INF lifecycle: Module initialized: SourceSpoke
09:00:30,566 INF lifecycle: All modules have been initialized.
09:00:30,567 INF threading: Thread Done: AnaSourceWatcher (140225419654912)
09:00:31,610 DBG storage: clearpart: initializing vda
09:00:31,735 DBG storage: clearpart: initializing vdb
09:00:32,023 DBG storage_utils: /dev/vda matches ['vda'] for
devicetree=existing 20 GiB disk vda (3) with non-existent gpt disklabel
existing 1024 MiB cdrom sr0 (8)
existing 20 GiB disk vdb (13) with non-existent gpt disklabel
existing 0 B file /tmp/curl_fetch_url0/install.img (deleted) (18)
existing 0 B loop loop0 (22)
existing 0 B file /LiveOS/rootfs.img (32)
existing 0 B loop loop1 (36) with existing ext4 filesystem
existing 2 GiB dm live-rw (60) with existing ext4 filesystem
existing 2 GiB dm live-base (70) with existing ext4 filesystem
existing 0 B file /overlay (deleted) (46)
existing 0 B loop loop2 (50)
and disks_only=True
09:00:32,132 DBG storage_utils: /dev/vdb matches ['vdb'] for
devicetree=existing 20 GiB disk vda (3) with non-existent gpt disklabel
existing 1024 MiB cdrom sr0 (8)
existing 20 GiB disk vdb (13) with non-existent gpt disklabel
existing 0 B file /tmp/curl_fetch_url0/install.img (deleted) (18)
existing 0 B loop loop0 (22)
existing 0 B file /LiveOS/rootfs.img (32)
existing 0 B loop loop1 (36) with existing ext4 filesystem
existing 2 GiB dm live-rw (60) with existing ext4 filesystem
existing 2 GiB dm live-base (70) with existing ext4 filesystem
existing 0 B file /overlay (deleted) (46)
existing 0 B loop loop2 (50)
and disks_only=True
09:00:32,137 DBG bootloader: new disk order: ['vda', 'vdb']
09:00:32,244 DBG storage_utils: /dev/vda matches ['vda'] for
devicetree=existing 20 GiB disk vda (3) with non-existent gpt disklabel
existing 1024 MiB cdrom sr0 (8)
existing 20 GiB disk vdb (13) with non-existent gpt disklabel
existing 0 B file /tmp/curl_fetch_url0/install.img (deleted) (18)
existing 0 B loop loop0 (22)
existing 0 B file /LiveOS/rootfs.img (32)
existing 0 B loop loop1 (36) with existing ext4 filesystem
existing 2 GiB dm live-rw (60) with existing ext4 filesystem
existing 2 GiB dm live-base (70) with existing ext4 filesystem
existing 0 B file /overlay (deleted) (46)
existing 0 B loop loop2 (50)
and disks_only=True
09:00:33,221 ERR ui.tui.spokes.storage: storage configuration failed:
The following problem occurred on line 68 of the kickstart file:
('new lv is too large to fit in free space', 'striker_69E6A4A0')
09:00:35,323 ERR bootloader: bios order specified unknown disk vdb
09:00:35,324 ERR bootloader: bios order specified unknown disk vda
09:00:35,622 DBG simpleline: Scheduling screen SummaryHub
09:00:35,624 DBG simpleline: New signal RenderScreenSignal enqueued with
source ScreenScheduler
09:00:35,625 DBG simpleline: Scheduling screen ProgressSpoke
09:00:35,626 DBG simpleline: Starting main loop
09:00:35,626 DBG simpleline: Processing screen
ScreenData(SummaryHub,None,False)
09:00:35,648 DBG payload: Source http://10.1.4.1/fedora28/x86_64/os/
needs network for installation
09:00:35,874 DBG simpleline: Input is required by
ScreenData(SummaryHub,None,False) screen
09:00:35,879 DBG payload: Source http://10.1.4.1/fedora28/x86_64/os/
needs network for installation
====
In the past, I would just do a manual install and then examine
'anaconda-ks.cfg' to see what it generated for the partitioning, but
that no longer seems to be recorded.
Any help in figurin out what I'm doing wrong would be my appreciated.
--
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
5 years, 6 months
hibernate stops working after upgrade to F29 from F28
by Ranjan Maitra
Hi,
I tried the following:
systemctl hibernate
and I get:
Failed to hibernate system via logind: Resume not configured, can't hibernate
I have never previously had to configure anything on an upgraded system already capable of hibernating (once hibernated). Has something changed? What do I do to fix this issue?
Many thanks and best wishes,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
5 years, 6 months
dnf update fails
by Willis Yonker
Hi,
I did a fresh install of Fedora 29 a few weeks ago. It seems to work fine
except now dnf seems to not want to use the fedora repo. If I remove the
fedora.repo file, or even disable the fedora repo in the file, it works.
Any help would be appreciated!
Thank you!
If I run dnf -v update, here is the last part of the output:
Fedora 29 - x86_64
13 kB/s | 18 kB 00:01
reviving: 'fedora' can be revived - metalink checksums match.
not found other for: Fedora 29 - x86_64
not found modules for: Fedora 29 - x86_64
not found deltainfo for: Fedora 29 - x86_64
not found updateinfo for: Fedora 29 - x86_64
loading repo 'fedora' failure: repo_add_solv() has failed.
Error: Loading repository 'fedora' has failed
Here is the last part of the dnf.log file:
2018-11-30T14:56:58Z DEBUG loading repo 'fedora' failure: repo_add_solv()
has failed.
2018-11-30T14:56:58Z DDEBUG Cleaning up.
2018-11-30T14:56:58Z SUBDEBUG
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/base.py", line 144, in
_add_repo_to_sack
self._sack.load_repo(hrepo, build_cache=True, **mdload_flags)
_hawkey.Exception: repo_add_solv() has failed.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 64, in main
return _main(base, args, cli_class, option_parser_class)
File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 99, in _main
return cli_run(cli, base)
File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 115, in
cli_run
cli.run()
File "/usr/lib/python3.7/site-packages/dnf/cli/cli.py", line 1054, in run
self._process_demands()
File "/usr/lib/python3.7/site-packages/dnf/cli/cli.py", line 785, in
_process_demands
load_available_repos=self.demands.available_repos)
File "/usr/lib/python3.7/site-packages/dnf/base.py", line 400, in
fill_sack
self._add_repo_to_sack(r)
File "/usr/lib/python3.7/site-packages/dnf/base.py", line 148, in
_add_repo_to_sack
_("Loading repository '{}' has failed").format(repo.id))
dnf.exceptions.RepoError: Loading repository 'fedora' has failed
2018-11-30T14:56:58Z CRITICAL Error: Loading repository 'fedora' has failed
5 years, 6 months
Kernel 4.19 does not make an ethernet connection
by Lester M Petrie
Hi,
I am currently running Fedora 28. I did a dnf upgrade this morning, and
it upgraded the kernel to 4.19.
Linux morgoth.localdomain 4.19.4-200.fc28.x86_64
After rebooting to the new kernel, I found I could not connect to
anything over ethernet. I rebooted to the previous kernel, which was 4.18.
Linux morgoth.localdomain 4.18.18-200.fc28.x86_64
My connection worked again. I went looking in the journal for entries
related to the ifname. Under the 4.19 kernel, I found the following
entries(sorry for the wrapping, I can't seem to turn it off).
-- Logs begin at Thu 2018-05-10 18:16:12 EDT, end at Thu 2018-11-29
14:05:16 EST. --
Nov 29 13:58:38 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
renamed from eth0
Nov 29 13:59:29 morgoth.localdomain NetworkManager[920]: <info>
[1543517969.1764] ifcfg-rh: new connection
/etc/sysconfig/network-scripts/ifcfg-enp6s0
(8719d767-2f8e-3fc1-a9e2-522bde03a5a7,"enp6s0")
Nov 29 13:59:30 morgoth.localdomain NetworkManager[920]: <info>
[1543517970.4361] manager: (enp6s0): new Ethernet device
(/org/freedesktop/NetworkManager/Devices/2)
Nov 29 13:59:30 morgoth.localdomain NetworkManager[920]: <info>
[1543517970.4371] device (enp6s0): state change: unmanaged ->
unavailable (reason 'managed', sys-iface-state: 'external')
Nov 29 13:59:30 morgoth.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP):
enp6s0: link is not ready
Nov 29 13:59:30 morgoth.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP):
enp6s0: link is not ready
For the 4.18 kernel, I get the following, plus many more lines after it
is connected.
-- Logs begin at Thu 2018-05-10 18:16:12 EDT, end at Thu 2018-11-29
14:10:03 EST. --
Nov 29 14:08:04 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
renamed from eth0
Nov 29 14:08:59 morgoth.localdomain NetworkManager[930]: <info>
[1543518539.5379] ifcfg-rh: new connection
/etc/sysconfig/network-scripts/ifcfg-enp6s0
(8719d767-2f8e-3fc1-a9e2-522bde03a5a7,"enp6s0")
Nov 29 14:09:00 morgoth.localdomain NetworkManager[930]: <info>
[1543518540.6720] manager: (enp6s0): new Ethernet device
(/org/freedesktop/NetworkManager/Devices/2)
Nov 29 14:09:00 morgoth.localdomain NetworkManager[930]: <info>
[1543518540.6731] device (enp6s0): state change: unmanaged ->
unavailable (reason 'managed', sys-iface-state: 'external')
Nov 29 14:09:00 morgoth.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP):
enp6s0: link is not ready
Nov 29 14:09:00 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
link down
Nov 29 14:09:00 morgoth.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP):
enp6s0: link is not ready
Nov 29 14:09:02 morgoth.localdomain NetworkManager[930]: <info>
[1543518542.3332] device (enp6s0): carrier: link connected
Nov 29 14:09:02 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
link up
Nov 29 14:09:02 morgoth.localdomain kernel: IPv6:
ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Looking at these, I did a search for r8169. The 4.19 kernel gives the
following.
-- Logs begin at Thu 2018-05-10 18:16:12 EDT, end at Thu 2018-11-29
14:46:52 EST. --
Nov 29 13:58:37 morgoth.localdomain kernel: libphy: r8169: probed
Nov 29 13:58:37 morgoth.localdomain kernel: r8169 0000:06:00.0 eth0:
RTL8168c/8111c, a4:ba:db:f9:fa:9d, XID 3c4000c0, IRQ 33
Nov 29 13:58:37 morgoth.localdomain kernel: r8169 0000:06:00.0 eth0:
jumbo features [frames: 6128 bytes, tx checksumming: ko]
Nov 29 13:58:38 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
renamed from eth0
Nov 29 13:59:30 morgoth.localdomain kernel: Generic PHY r8169-600:00:
attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-600:00,
irq=IGNORE)
The 4.18 kernel shows the following.
-- Logs begin at Thu 2018-05-10 18:16:12 EDT, end at Thu 2018-11-29
14:46:52 EST. --
Nov 29 14:08:03 morgoth.localdomain kernel: r8169 Gigabit Ethernet
driver 2.3LK-NAPI loaded
Nov 29 14:08:03 morgoth.localdomain kernel: r8169 0000:06:00.0: can't
disable ASPM; OS doesn't have ASPM control
Nov 29 14:08:03 morgoth.localdomain kernel: r8169 0000:06:00.0 eth0:
RTL8168c/8111c, a4:ba:db:f9:fa:9d, XID 3c4000c0, IRQ 33
Nov 29 14:08:03 morgoth.localdomain kernel: r8169 0000:06:00.0 eth0:
jumbo features [frames: 6128 bytes, tx checksumming: ko]
Nov 29 14:08:04 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
renamed from eth0
Nov 29 14:09:00 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
link down
Nov 29 14:09:02 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
link up
Is there something obvious to do that will get the 4.19 kernel
connecting? Is there someother information that would help find the
problem? Thanks for any help.
--
Lester M Petrie
5 years, 6 months
Fedora29 + 802.1x
by Todor Petkov
Hello,
in the office we are using 802.1x authentication on the switches with
username/password. It was working just fine for me, but after upgrade to
Fedora29, it stopped authenticating. On the switch I don't see anything
about user/pass being wrong. In NetworkManager I am using PEAP +
user/password authentication, as before, but it just stopped working.
Anyone with similar issue?
Thanks in advance
5 years, 6 months
Rubygem
by Emmett Culley
When I upgrades to Fedora 29 I had to remove a package to get through it. Namely rubygem-compass-immport-once had a conflict. now when I attempt to install it I get:
['\n Problem 1: conflicting requests\n - nothing provides rubygem(sass) = 3.2) needed by rubygem-compass-import-once-1.0.5-10.fc29.noarch\n Problem 3: package rubygem-compass-import-once-doc-1.0.5-10.fc29.noarch requires rubygem-compass-import-once = 1.0.5-10.fc29, but none of the providers can be installed\n - conflicting requests\n - nothing provides (rubygem(sass) = 3.2) needed by rubygem-compass-import-once-1.0.5-10.fc29.noarch\n Problem 4: package rubygem-compass-rails-2.0.4-6.fc29.noarch requires (rubygem(compass) >= 1.0.0 with rubygem(compass) = 0.12.2, but none of the providers can be installed\n - conflicting requests\n - nothing provides rubygem(sass)
Does anyone have any ideas how to fix the. Kind of a pain not having compass to compile CSS.
Emmett
5 years, 6 months
Download Archive for F28 iso
by Joerg Lechner
Hi,
had a crash and lost the F28 iso. Found only F24/F25 in Fedora Archives. Does anyone know a Fedora Archive containing F28 iso?
Thanks in advance!
Kind regards
5 years, 6 months
Fedora 29 root -
by Bob Goodwin
.
I just did a new install of Fedora 29 and find the installation provides
no root password. I have a lot of configuration to do and sudo is
inconvenient.
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-27/64bit LINUX XFCE Fastmail POP3
5 years, 6 months