users September 2018

users@lists.fedoraproject.org

104 participants
108 discussions

Failed to start Load Kernel Modules.
by Sudhir Khanger 17 Jan '19

17 Jan '19

Hello, I get *Failed to start Load Kernel Modules* during the boot. Everytime Kernel is updated VirtualBox modules fail I have to reboot into the new Kernel, run the following commands and then it starts working. $ sudo akmods --force $ sudo dracut -v -f $ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg Then everything starts working again and the boot error goes away. You can found the background of the issue in the link below. https://bugzilla.redhat.com/show_bug.cgi?id=1254340 My question is how can I automate this task.

5 20

ACPI errors (was: f24 boot fails; need help).
by William 19 Dec '18

19 Dec '18

Good evening, One of the problems reported in the log file "rdsosreport.txt" generated by the failed boots discussed in the "f24 boot fails; need help" topic was a set of "ACPI" errors. Here are the relevant lines (with added line numbers) from that log file (the first and last lines are just for context): ---------- 862 [ 1.218683] coyote kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 863 [ 1.218927] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 864 [ 1.219196] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543) 865 [ 1.219856] coyote kernel: ata2.00: ATA-8: ST2000DM001-1CH164, CC24, max UDMA/133 866 [ 1.220017] coyote kernel: ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA 867 [ 1.220812] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 868 [ 1.221100] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543) 869 [ 1.221620] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 870 [ 1.221909] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543) 871 [ 1.222200] coyote kernel: ata6.00: ATAPI: HL-DT-ST BD-RE BH14NS40, 1.00, max UDMA/100 872 [ 1.222374] coyote kernel: ata2.00: configured for UDMA/133 873 [ 1.222582] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 874 [ 1.222908] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543) 875 [ 1.222919] coyote kernel: scsi 1:0:0:0: Direct-Access ATA ST2000DM001-1CH1 CC24 PQ: 0 ANSI: 5 876 [ 1.223466] coyote kernel: ata4.00: ATAPI: PIONEER BD-RW BDR-208M, 1.10, max UDMA/100 877 [ 1.226360] coyote kernel: ata7: SATA link down (SStatus 0 SControl 300) 878 [ 1.226407] coyote kernel: ata9: SATA link down (SStatus 0 SControl 300) 879 [ 1.226501] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 880 [ 1.226507] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543) 881 [ 1.226519] coyote kernel: ata6.00: configured for UDMA/100 882 [ 1.227197] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 883 [ 1.227204] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543) 884 [ 1.227217] coyote kernel: ata4.00: configured for UDMA/100 ---------- What is this all about? Is this a real problem or a false alarm? How do I fix it? thanks, Bill.

5 10

Install on Zotac Zbox CI327?
by wwp 11 Dec '18

11 Dec '18

Hello there, (after a looong time not using Fedora, just back to it!) I've tried installing Fedora on a Zotac Zbox CI327 (Intel Celeron N3450 inside) but this happens to fail. I've tried F25 but it has not the right kernel to make it (I've read about 4.10 minimum), then tried F26-Alpha-1.7 Live and Rawhide-20170518 Live but none could reach the graphical login. They both boot, some steps take a lot of time and I end up in a state I don't understand but which is not friendly ;-). Here's a link to a rdsosreport.txt file generated using Rawhide, I must admit that I don't know what to do now.. https://paste.fedoraproject.org/paste/iRx8d~7Luk2TC3bsaDuuT15M1UNdIGYhyRLiv… BTW, I could install and run a Ubuntu 17.10 daily (artful-desktop-amd64-20170519.iso) - wow it starts up pretty quickly - and that gave me hope! Any hint or experience w/ such hardware? Regards, -- wwp

2 3

Network Manager not Retaining Wifi Password
by Stephen Morris 20 Nov '18

20 Nov '18

Hi, After the last system update in F28 Network Manager is not retaining the wifi password entered into its security tab. When I enter the password and select apply then 'OK' to exit network manager, when I get back in the password is gone. Is anyone else seeing this issue or have any tips on how to rectify this issue? regards, Steve

3 15

How to turn on networking from rescue boot
by vendor＠billoblog.com 29 Oct '18

29 Oct '18

So... I did a "sudo dnf upgrade" and things seemed to do well. However, when I rebooted, it hangs on bootup with the statment "Holding until bootup processes complete" or something like that -- I'm doing this from memory. I tried with a couple of older kernels, but they also hung. I assume that this is some transient thing associated with the upgrade. Over the years, I've had glitches appear on an upgrade and disappear on the next upgrade. Accordingly, I'd like to boot into rescue mode and see if I can upgrade again. However, I've forgotten how to turn on wifi networking from rescue mode. Can anybody point me to a tutorial? Thanks, billo

6 5

4.17.x kernels cause "nvme0: controller is down" on MacBook Air
by Lonni J Friedman 17 Oct '18

17 Oct '18

Ever since Fedora(27) released a 4.17.x kernel, my MacBook Air (7,1) is no longer able to boot at all. It hangs when trying to use the NVMe disk controller: nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x810 and the entire boot process eventually times out completely. If I return to using the last 4.16.x kernel (4.16.14-200.fc27.x86_64), then the problem does *not* reproduce, and everything boots normally. i opened a bug for this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1601196 however, I'm surprised that no one else has run into this issue. Any ideas or suggestions? thanks!

2 3

OT: fastest way to copy one drive to another
by Ranjan Maitra 06 Oct '18

06 Oct '18

Hi, I have two drives mounted on a F28 system. Both are identical 4TB drives. The second one is empty. I am concerned about the first one failing so would like to copy the contents (which are around 3.7 TB) to the second. What is the fastest way to copy the contents of the first drive to the second? I was using rsync, but is there a better way? Many thanks in advance for any advice, 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.

20 62

VNC alternatives
by Robert Moskowitz 05 Oct '18

05 Oct '18

It seems Tiger-vncserver is broken WRT polkit for any spin other than gnome. Definitely not Xfce that I use. The work around is nasty: Connect via SSH and run vncserver from the command line. But probably can do it better via SCREEN and just forget about that screen session... So it is time to look at the alternatives. I know they are out there and have been talked about on this list, but my search foo is weak (as always). So can I have a bit of help in figuring out what to replace my decades-old connection to VNC? thanks

9 21

fc29 beta
by ToddAndMargo 02 Oct '18

02 Oct '18

Hi All, I just upgraded one of my machines to FC29 Beta. Looks pretty. Haven't had a chance to play with it yet. -T Here are my upgrade notes; FC 28 -->> FC 29: # rpm --rebuilddb # rpm -Va --nofiles --nodigest if anything is too new, do a # dnf downgrade offender(s) # dnf --enablerepo=* update --refresh # dnf install python3-dnf-plugin-system-upgrade # dnf system-upgrade download --refresh --releasever=29 --allowerasing --best # dnf clean packages <-- optional # dnf system-upgrade reboot

6 18

fedora cloud AWS randomly shutdown
by Neal Becker 01 Oct '18

01 Oct '18

I'm using f28 cloud on AWS as a compute farm. It seems that instances randomly shutdown within hours of starting. An example log: ... Fedora 28 (Cloud Edition) Kernel 4.16.3-301.fc28.x86_64 on an x86_64 (ttyS0) Stopping Restore /run/initramfs on shutdown... [[0;32m OK [0m] Removed slice system-sshd\x2dkeygen.slice. Stopping User Manager for UID 1000... ... In this case after about 4 hours it seems to have spontaneously shutdown. This happens with high probability - maybe 2/10 instances I start spontaneously shutdown. Any ideas what's going on? I'm just wondering if this is something specific to fedora cloud edition, because it doesn't seem to be a common complaint on AWS (most of which is ubuntu).

3 6