1. For several weeks, I've been seeing text fly by early during the boot process, before the blue and white line grows left to right at the bottom of the screen. But the text scrolls by too fast and disappears too fast for me to catch more than an isolated word or two. I also had no idea how to access appropriate logs. Then came the boot failure. I did what the dracut shell said, and I recognized that the first set of lines that I posted in one of the boot failure postings quite possibly was the text I had been seeing during boots for the past several weeks. 2. Since the boot problem was fixed, I continue to see what I believe is the same text, the same way as before the boot failure problem. As you advised, I did the journalctl command. I routed the output to a text file, and then did a "cat -n" to another file so we would have line numbers. Here's the result, with line numbers and an extra couple lines at the beginning and end for context:
--------------- 698 May 21 11:22:13 coyote kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 699 May 21 11:22:13 coyote kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 700 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 701 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8db5ce0db2a8), AE_NOT_FOUND (20160930/psparse-543) 702 May 21 11:22:13 coyote kernel: ata2.00: ATA-8: ST2000DM001-1CH164, CC24, max UDMA/133 703 May 21 11:22:13 coyote kernel: ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA 704 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 705 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8db5ce0db2a8), AE_NOT_FOUND (20160930/psparse-543) 706 May 21 11:22:13 coyote kernel: ata2.00: configured for UDMA/133 707 May 21 11:22:13 coyote kernel: scsi 1:0:0:0: Direct-Access ATA ST2000DM001-1CH1 CC24 PQ: 0 ANSI: 5 708 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 709 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff8db5ce0db2f8), AE_NOT_FOUND (20160930/psparse-543) 710 May 21 11:22:13 coyote kernel: ata6.00: ATAPI: HL-DT-ST BD-RE BH14NS40, 1.00, max UDMA/100 711 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 712 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff8db5ce0db528), AE_NOT_FOUND (20160930/psparse-543) 713 May 21 11:22:13 coyote kernel: ata4.00: ATAPI: PIONEER BD-RW BDR-208M, 1.10, max UDMA/100 714 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 715 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff8db5ce0db528), AE_NOT_FOUND (20160930/psparse-543) 716 May 21 11:22:13 coyote kernel: ata4.00: configured for UDMA/100 717 May 21 11:22:13 coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 718 May 21 11:22:13 coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff8db5ce0db2f8), AE_NOT_FOUND (20160930/psparse-543) 719 May 21 11:22:13 coyote kernel: ata6.00: configured for UDMA/100 720 May 21 11:22:13 coyote kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 --------------- So yes, the problem is still there. (And now I know a way of getting to boot logs!) Thank-you for you help so far. Bill. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
