Re[2]: Cannot boot F40 from flash drive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



F40 just 'boots' to a black screen, the same for the KDE iso for F40. Since I added nomodeset parameter via grub to the linux cmd line for Knoppix, I also tried that for both F40 and the F40 KDE, but got no different results.  It appears that nothing is running behind that black screen, the PC just appears to hang. I did see a few errors related to my Corsair keyboard, which uses 2 USB connections, but an old Microsoft KB did not produce better results. The Knoppix could not see the Corsair KB after booting, but once the M$ KB was used, the Knoppix had no problems. Kubuntu has no issues using the Corsair KB.

As I mentioned, the PC was shut down gracefully with a shutdown command. The PC was not affected by the power outage since I have an UPS that provides 30 minutes  of power to my 2 PC's (Win10 & Linux).  UEFI BIOS was unaffected.

I explained my use of an outdated F25 in another post. I understood the 'risk' and managed to run it for 8 years without being compromised. I began using Unix Version 7 on a PDP-11 in 1980, and have used various Unix versions and then Linux at home since, so explaining to me why I'm perhaps naive strikes me as a little late. ^_^

I'm old, and I have forgotten much, but I am still relatively functional.

Regards,
Doug Wyatt


On Tue, Sep 17, 2024 at 04:33 PM, Çınar Civan <cinar@xxxxxxxxxxx> wrote:
On Tue, Sep 17, 2024 at 1:41 PM dwyatt--- via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
I've been running Fedora 25 on a homebuilt PC since 2016. It was becoming
unstable so I planned to install F40 on an alternate partition, but before
I was ready we had a power outage. Since my 2 PC's are on an UPS, I was
able to gracefully shut them down. After power returned, 11 hours later,
the Win10 box rebooted, no problem. But the F25 box couldn't reboot.
So, I put the KDE version of F40 on a multiboot flash drive... and couldn't
get that to boot.
I tried Knoppix 9.1, and using grub edit, added 'nomodeset' to the boot
cmdline to get that to boot.
Then I tried the non-KDE F40 ISO. but even adding 'nomodeset' did not
produce a successfull boot.

However, I just tried booting Kubuntu 24.04 LTS from a flash drive and had
no problem getting that to boot.

Does anyone have any insight into why F40 won't boot on this i7-6800k CPU
system with 32 GB of RAM?

--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


Hello,

First, I need to better understand the issue, as I don't have a clear
picture in my mind yet. Could we clarify the following points?

1) At what stage does the F40 fail to boot? Are there any error
messages, and if so, could you share them?
2) It's possible that GRUB or UEFI settings were affected by the power
outage. Have you checked your BIOS settings?

I’d like to clear up these details without diving too deep into
technicalities. Once I have a better grasp of the situation, I’ll do
my best.

I also have an important suggestion: Avoid using older Fedora versions
unless absolutely necessary, and try not to lag behind by more than
two versions. For example, using F38 right now is fine, but once F41
is released, support for upgrading from F38 will be discontinued.
Additionally, older versions are more susceptible to security
vulnerabilities, so it's best to stay up to date.

Best regards,
Çınar Civan
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux