Re: BIOS update, grub boots, Fedora doesn't - SOLVED

On Thu, Apr 10, 2025 at 8:52 PM Go Canes wrote: > > I recently updated the BIOS on a new Dell XPS 16 running Fedora 40. > Prior to the update everything was working fine. After the update, > grub displays the boot menu and indicates it is booting the default > entry, then...not

Re: BIOS update, grub boots, Fedora doesn't

On Sat, 2025-04-12 at 15:32 -0700, Samuel Sieb wrote: > You mentioned that you installed the non-graphical system, then added > the desktop later. That's why I thought the server one didn't let you > add desktops during install. I mentioned that. I don't recall if it were a case of blind insta

Re: BIOS update, grub boots, Fedora doesn't

On Sat, Apr 12, 2025 at 6:32 PM Samuel Sieb wrote: > You mentioned that you installed the non-graphical system, then added > the desktop later. That's why I thought the server one didn't let you > add desktops during install. I installed the desktop as part of the Fedora install. Sorry if I led

Re: BIOS update, grub boots, Fedora doesn't

On 4/12/25 3:27 PM, Go Canes wrote: On Sat, Apr 12, 2025 at 6:16 PM Samuel Sieb wrote: I missed that you were using the netinstall version of the server install. I didn't realize there was one. The everything install lets you install the graphical desktop as well. Also, at least the filesyst

Re: BIOS update, grub boots, Fedora doesn't

On Sat, Apr 12, 2025 at 6:16 PM Samuel Sieb wrote: > I missed that you were using the netinstall version of the server > install. I didn't realize there was one. The everything install lets > you install the graphical desktop as well. Also, at least the > filesystem defaults are different with

Re: BIOS update, grub boots, Fedora doesn't

On 4/12/25 4:46 AM, Go Canes wrote: On Fri, Apr 11, 2025 at 11:16 PM Samuel Sieb wrote: On 4/11/25 6:45 PM, Go Canes wrote: On Fri, Apr 11, 2025 at 9:42 AM Tim via users wrote: When I installed Fedora 40 (I think, it's 40), I couldn't get the usual installation ISOs to work. I had to use t

Re: BIOS update, grub boots, Fedora doesn't

On Sat, Apr 12, 2025 at 8:45 AM George N. White III wrote: > My Dell systems did something similar. On this one, the EFI Fedora entry > (Boot0001) had > been replaced with what is now (after renaming) Boot0003 below. A recent > BIOS update > made Boot0003 the default, but I go

Re: BIOS update, grub boots, Fedora doesn't

On Thu, Apr 10, 2025 at 9:52 PM Go Canes wrote: > I recently updated the BIOS on a new Dell XPS 16 running Fedora 40. > Prior to the update everything was working fine. After the update, > grub displays the boot menu and indicates it is booting the default > entry, then...nothing

Re: BIOS update, grub boots, Fedora doesn't

On Fri, Apr 11, 2025 at 11:16 PM Samuel Sieb wrote: > > On 4/11/25 6:45 PM, Go Canes wrote: > > On Fri, Apr 11, 2025 at 9:42 AM Tim via users > > wrote: > >> When I installed Fedora 40 (I think, it's 40), I couldn't get the usual > >> installation ISOs to work. I had to use the server spin, I be

Re: BIOS update, grub boots, Fedora doesn't

> On 11 Apr 2025, at 14:41, Tim via users wrote: > > I had to use the server spin, I believe it > used a different bootloading method. All my server installs use the exact same boot mechanism as my desktops. e.g. UEFI shim -> grub -> kernel -> happy user Barry -- ___

Re: BIOS update, grub boots, Fedora doesn't

On 4/11/25 6:45 PM, Go Canes wrote: On Fri, Apr 11, 2025 at 9:42 AM Tim via users wrote: When I installed Fedora 40 (I think, it's 40), I couldn't get the usual installation ISOs to work. I had to use the server spin, I believe it used a different bootloading method. I installed a non-graphic

Re: BIOS update, grub boots, Fedora doesn't

A thought that occurs to me The various Fedora boot failures are occurring after grub, but before any kernel output. Failure loading initrd image? So maybe something to do with RAM that the BIOS testing isn't detecting, or something to do with decompressing the image? Either way, why

Re: BIOS update, grub boots, Fedora doesn't

gt; system, afterwards installing a graphical desktop. I normally use the server netinstall ISO, as it avoids installing all the packages only to replace them immediately with the first "dnf update". F40 was originally installed and I used the laptop for a month or two. No major issues until doin

Re: BIOS update, grub boots, Fedora doesn't

On Fri, Apr 11, 2025 at 1:51 AM Marco Moock wrote: > I assume it is an UEFI (some vendors still call that BIOS). Yes, UEFI which Dell still calls BIOS > Can you reset it to the default settings? While I didn't list it, this has been tried. More than once. > Does it support CSM?

Re: BIOS update, grub boots, Fedora doesn't

On Thu, 2025-04-10 at 20:52 -0400, Go Canes wrote: > - booting a f40 netinstall ISO(via Ventoy) (the same one used to > instal Fedora 40 on this laptop initially) gets as far as the > "install/test/rescue" menu, but otherwise has the same boot failure When I installed Fedora 40 (I think, it's 40),

Re: BIOS update, grub boots, Fedora doesn't

On Thu, 10 Apr 2025 20:52 Go Canes wrote: > I have performed the following tests and/or remedial actions: > - attempted to downgrade the BIOS - the updated version does not allow > downgrading > - no change if secure boot is enabled or disabled > - confirmed the boot disk (NVMe)

BIOS update, grub boots, Fedora doesn't

I recently updated the BIOS on a new Dell XPS 16 running Fedora 40. Prior to the update everything was working fine. After the update, grub displays the boot menu and indicates it is booting the default entry, then...nothing. I have performed the following tests and/or remedial actions

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

h. I have twice had a failure to resume after suspend, and attributed it to having done a dnf update and gotten a new kernel. If we have a firmware problem in F41 that is fixed in F42, how do we get it back-ported? On 3/16/25 9:26 PM, Andre Robatino wrote: Since 42 Beta went Gold, I de

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

Since 42 Beta went Gold, I decided to install the UEFI firmware and then F42. Afterwards, it works perfectly. I had 2 issues before: 1) suspend didn't work, and 2) the GRUB menu wasn't responsive on a cold boot (I could see it but not interact), unless I plugged in an external USB keyboard. Both

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

Well that is good to hear. I really like these Lenovos. But I wonder if they support Win11; going to have to check out my one 140e that is running Win10 and figure out what to do come 10's EOL.  Unfortunately I do need one Win box... On 3/12/25 1:32 PM, Andre Robatino wrote: I tried running

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

I tried running the firmware-util.sh utility at Mrchromebox.tech, and it looks like it will work (I'm not going to burn the UEFI firmware right now as my existing Fedora install isn't expected to work after that so I'll have to reinstall, which I'll do when F42 goes Gold). The first time I ran i

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

I have rarely made bootable thumb drives.  I always burn such ISO images to CD using K3B then use a USB CD/DVD player/burner (the one I used to make the CD). But the messages say booting from Hard Disk, not your USB disk. That is suspect. On 2/28/25 11:02 AM, Andre Robatino wrote: I burned

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

Should also mention that I clean install each new version of Fedora (GNOME Workstation Live) on the laptop using the same thumb drive and also burning the image to it using mediawriter. That always works fine. -- ___ users mailing list -- users@lists.f

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

The thumb drive was easily recognizable in the boot options, and confirmed in some of the messages that appeared after. Plus, my only other drive on the laptop is the SSD with Fedora (which boots fine), there is no actual HDD. So I think that's just a generic message. -- ___

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

On Fri, Feb 28, 2025 at 7:52 AM Andre Robatino wrote: > > I have a Lenovo X131e which is currently running an old BIOS from > johnlewis.ie (4.0-6588-g4acd8ea-dirty, 09/04/2014). It was originally a > Chromebook and I replaced the BIOS so there would be no danger of it >

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

The current BIOS is SeaBIOS. AFAIK all I can do is hit ESC after booting to select the boot device (it boots from the regular SSD by default and then shows Fedora's grub menu if I don't do that). There doesn't seem to be anything like a conventional BIOS menu. And before install

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

Is secure boot turned on? That could cause it not to boot. Regards Andrew On 28 February 2025 16:03:36 "Andre Robatino" wrote: I burned g8uj35us.iso to a thumb drive using mediawriter and tried booting from it by selecting the thumb drive after "Press ESC for boot menu". It failed with th

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

I burned g8uj35us.iso to a thumb drive using mediawriter and tried booting from it by selecting the thumb drive after "Press ESC for boot menu". It failed with the messages Booting from Hard Disk... Boot failed: not a bootable disk Booting from CBFS... Then spewed some messages to the screen an

Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

I have a Lenovo X131e which is currently running an old BIOS from johnlewis.ie (4.0-6588-g4acd8ea-dirty, 09/04/2014). It was originally a Chromebook and I replaced the BIOS so there would be no danger of it automatically reinstalling Chrome. I see there is a Lenovo page at https

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

It SHOULD work.  It is just that for these bios updates Lenovo only lists WIn versions. Just make sure you have not locked the bios firmware before you boot up with the CD you made from the ISO image. I have been using Lenovo x1--e notebooks for 10 years, all used from ebay, and applying

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

BTW, it has an Intel Celeron 1007U CPU and my machine type according to the label is 628323U (6283 for short). That type is not listed as one the BIOS is intended for, however I'm guessing that's only because this was originally a

Re: [F40] Cannot boot live version from USB drive with UEFI BIOS

> Are you using windows to create the usb stick? No, I created them from F38 with either dd or mediawriter. > Was the f36 image a lot smaller then all the newer versions? I do not remember but I think they were all more than 2Mb. I've now solved the issue by installing F36, then upgrading to F40

Re: [F40] Cannot boot live version from USB drive with UEFI BIOS

On 6/29/24 10:01 AM, Frédéric wrote: I created a USB stick with a live version of Fedora 40. I tried both the default version and the KDE Spin. I tried using dd and using mediawriter. Same result: I cannot boot on the USB drive if my BIOS is configured in UEFI as it is to boot from my hard disk

Re: [F40] Cannot boot live version from USB drive with UEFI BIOS

On Sun, Jun 30, 2024 at 12:49 PM Frédéric wrote: > [...] > So I'm still not able to boot F40 on a USB stick. > > Maybe, I should try F39 or F38. If it works, I will be able to upgrade > later. Some people have been able to boot either the network installer or the server installer. For the latt

Re: [F40] Cannot boot live version from USB drive with UEFI BIOS

> On 30 Jun 2024, at 16:30, Frédéric wrote: > > However, I was > able to download and install F36 on a USB stick and boot from it > without any issue. Are you using windows to create the usb stick? Was the f36 image a lot smaller then all the newer versions? Barry -- _

Re: [F40] Cannot boot live version from USB drive with UEFI BIOS

> I created a USB stick with a live version of Fedora 40. I tried both > the default version and the KDE Spin. I tried using dd and using > mediawriter. Same result: I cannot boot on the USB drive if my BIOS is > configured in UEFI as it is to boot from my hard disk on Fedora 38. It

Re: [F40] Cannot boot live version from USB drive with UEFI BIOS

> Here is what the 'GPT:Primary header thinks Alt. header is not at the > end of the disk' message means: > . Thank you: I was able to fix the error using fdisk with just the command "w". However, this does not make my USB

Re: [F40] Cannot boot live version from USB drive with UEFI BIOS

On Sat, Jun 29, 2024 at 1:02 PM Frédéric wrote: > > Hi, > > I created a USB stick with a live version of Fedora 40. I tried both > the default version and the KDE Spin. I tried using dd and using > mediawriter. Same result: I cannot boot on the USB drive if my BIOS is > con

[F40] Cannot boot live version from USB drive with UEFI BIOS

Hi, I created a USB stick with a live version of Fedora 40. I tried both the default version and the KDE Spin. I tried using dd and using mediawriter. Same result: I cannot boot on the USB drive if my BIOS is configured in UEFI as it is to boot from my hard disk on Fedora 38. It says that there

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

> On 15 Jul 2023, at 22:51, Michael Hennebry > wrote: > > I was expecting that there would be some time between > the first corrupt block and an irreparable filing system. > From subsequent reading, there is, > but the SSD does a good job of hiding corrupt blocks. > A better tactic would be to

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On Thu, 13 Jul 2023, Samuel Sieb wrote: On 7/13/23 21:08, Michael Hennebry wrote: If you really want a warning and all else fails, use your own checksums. Have a process walk the filesystem. If a file is open for writing, skip it. If a file is older than the recorded checksum, test the checksum

Re: WD BLUE SSD died. Not even seen in BIOS or via USB? Bad Response from WD Support.

On 7/14/23 03:29, Michael D. Setzer II via users wrote: Not very happy with WD support, was actually looking for info to figure out what happened with drive versus trying to get a replacement, but that seems all they are concerned about NOT DOING. There's no way they could tell how or why it fa

Re: WD BLUE SSD died. Not even seen in BIOS or via USB? Bad Response from WD Support.

On 14 Jul 2023 at 15:08, Barry wrote: From: Barry Subject:Re: WD BLUE SSD died. Not even seen in BIOS or via USB? Bad Response from WD Support. Date sent: Fri, 14 Jul 2023 15:08:56 +0100 To: mi...@guam.net, Community

Re: WD BLUE SSD died. Not even seen in BIOS or via USB? Bad Response from WD Support.

> On 14 Jul 2023, at 11:29, Michael D. Setzer II via users > wrote: > > The two WD Black drives I just ordered and > seller sent serial numbers without being asked. WD Support comes > back that those serial numbers were meant for drives installed in > systems, so WD provides no warranty. T

Re: WD BLUE SSD died. Not even seen in BIOS or via USB? Bad Response from WD Support.

On Fri, Jul 14, 2023 at 7:29 AM Michael D. Setzer II via users < users@lists.fedoraproject.org> wrote: > Not very happy with WD support, was actually looking for info to > figure out what happened with drive versus trying to get a > replacement, but that seems all they are concerned about NOT > DO

Re: WD BLUE SSD died. Not even seen in BIOS or via USB? Bad Response from WD Support.

On 13 Jul 2023 at 21:43, Samuel Sieb wrote: Date sent: Thu, 13 Jul 2023 21:43:34 -0700 Subject:Re: WD BLUE SSD died. Not even seen in BIOS or via USB? To: users@lists.fedoraproject.org From: Samuel Sieb Send reply to

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On 7/13/23 21:08, Michael Hennebry wrote: If you really want a warning and all else fails, use your own checksums. Have a process walk the filesystem. If a file is open for writing, skip it. If a file is older than the recorded checksum, test the checksum. Write a new checksum. Where to put the

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

If you really want a warning and all else fails, use your own checksums. Have a process walk the filesystem. If a file is open for writing, skip it. If a file is older than the recorded checksum, test the checksum. Write a new checksum. Where to put the checksums is left as an exercise for the re

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On 7/13/23 07:40, Michael D. Setzer II via users wrote: Drives where purchase via ebay. Found I had 18 messages in my ebay folder that had WD BLUE in them. Seems there are usually 3 messages for each order, once for order, shipping, an then when received. some orders were single drives, while oth

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On Wed, Jul 12, 2023 at 6:53 PM Michael D. Setzer II via users < users@lists.fedoraproject.org> wrote: > Had the WD SSD just die in one of my 5 Home Fedora 37 > machines. Reply from WD is just it is out of warranty. > > Wondering if others are seeing this or it is just one bad drive. > According

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On 13 Jul 2023 at 17:38, Barry Scott wrote: From: Barry Scott Subject:Re: WD BLUE SSD died. Not even seen in BIOS or via USB? Date sent: Thu, 13 Jul 2023 17:38:28 +0100 Copies to: "George N. White III" To: "Michael D. Setzer" , Community supp

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

> On 13 Jul 2023, at 15:40, Michael D. Setzer II via users > wrote: > > Drives where purchase via ebay. I personally would be concerned to by critical components from ebay. Its bad enough trusting the disk makers... What I have been doing for years is buying so-called enterprise HDD that ha

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On 13 Jul 2023 at 10:09, George N. White III wrote: From: "George N. White III" Date sent: Thu, 13 Jul 2023 10:09:08 -0300 Subject:Re: WD BLUE SSD died. Not even seen in BIOS or via USB? To: mi...@guam.net, Community support for Fedora users Send reply to:

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On 13 Jul 2023 at 9:50, George N. White III wrote: From: "George N. White III" Date sent: Thu, 13 Jul 2023 09:50:57 -0300 Subject:Re: WD BLUE SSD died. Not even seen in BIOS or via USB? To: mi...@guam.net, Community support for Fedora users Send reply to:

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On Thu, Jul 13, 2023 at 3:19 AM Michael D. Setzer II via users < users@lists.fedoraproject.org> wrote: > Hopefully, this is just a random failure and others will be running > for years. Had some maxtor drives that were still running after 10 > years. Drive was made in 09Sep2022 so isn't even a yea

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On Wed, Jul 12, 2023 at 7:53 PM Michael D. Setzer II via users < users@lists.fedoraproject.org> wrote: > Had the WD SSD just die in one of my 5 Home Fedora 37 > machines. Reply from WD is just it is out of warranty. > I've had the same reply many times -- I always hope for a secret extension for

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On Thu, 2023-07-13 at 16:18 +1000, Michael D. Setzer II wrote: > Never opened an ssd drive, or even it it is possible. I have, it just looks like a circuit board with RAM chips on it, like a squarer version of the motherboard RAM cards. I reckon you'd need a special rig for each board and have to

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On 7/12/23 23:18, Michael D. Setzer II via users wrote: On 12 Jul 2023 at 21:49, ToddAndMargo via users wrote: Date sent: Wed, 12 Jul 2023 21:49:34 -0700 Subject:Re: WD BLUE SSD died. Not even seen in BIOS or via USB? To: users

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

On 12 Jul 2023 at 21:49, ToddAndMargo via users wrote: Date sent: Wed, 12 Jul 2023 21:49:34 -0700 Subject:Re: WD BLUE SSD died. Not even seen in BIOS or via USB? To: users@lists.fedoraproject.org Send reply to: Community support for

Re: WD BLUE SSD died. Not even seen in BIOS or via USB?

reported machine was down. Check machine, and it was showing errors. So went to reboot it to run fsck, but on reboot, it doesn't even see the disk in bios. Tried different cables, and different ports, and even hooked it to other computers, but no response at all. dmesg doesn't even show any

WD BLUE SSD died. Not even seen in BIOS or via USB?

showing errors. So went to reboot it to run fsck, but on reboot, it doesn't even see the disk in bios. Tried different cables, and different ports, and even hooked it to other computers, but no response at all. dmesg doesn't even show anything when hooked with a USB adapter.. Hook

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

Roger Heflin: >> And the bios will have no way to know what is hot-swappable as that is >> an external case feature/add-on enclosure. Philip Rhoades: > Not sure what you mean - I can set "Hot Swappable" in the BIOS. For something to be hotswappable, everything has to

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

On 8/21/22 23:23, Philip Rhoades via users wrote: I think he is stuck with booting into BIOS It does look like it . . a bit sad . . Just out of curiosity, is there some reason why you can't reboot? User have hot tar and feathers waiting fo

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

It generally is worse than that. It should be almost trivial to code, if you have the internal document for each bios version laying out the structure that is stored in the nvram. The other issue is even though it is trivial, the structure could be different between bios versions in the same MB

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

drives are hot-swappable but dmidecode does not supply that information - is there some way of getting the info without rebooting into the BIOS setup screen? I am running F36. Tangential approach - download the manual for the board. That won't help. They could be set either way. Correct.

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

Roger, On 2022-08-22 06:40, Roger Heflin wrote: Generally there is no standard for how anything is encoded/decoded in the bios. Ah . . Each vendor does it a slightly different way even on different bios versions. You would need a vendor tool that works for the specific motherboard

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

- is there some way of getting the info without rebooting into the BIOS setup screen? I am running F36. Tangential approach - download the manual for the board. That won't help. They could be set either way. I think he is stuck with booting into

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

> getting the info without rebooting into the BIOS setup screen? I am > running F36. Tangential approach - download the manual for the board. -- uname -rsvp Linux 3.10.0-1160.76.1.el7.x86_64 #1 SMP Wed Aug 10 16:21:17 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox i

Re: Interrogating BIOS from CLI? - dmidecode doesn't have the info

Generally there is no standard for how anything is encoded/decoded in the bios. Each vendor does it a slightly different way even on different bios versions. You would need a vendor tool that works for the specific motherboard. And the bios will have no way to know what is hot-swappable as that

Interrogating BIOS from CLI? - dmidecode doesn't have the info

People, I have a fairly recent ASUS ROG motherboard that I want to interrogate from the CLI - specifically to see which SATA drives are hot-swappable but dmidecode does not supply that information - is there some way of getting the info without rebooting into the BIOS setup screen? I am

Re: PXE GRUB booting for BIOS and UEFI

stallation media. It's commonly used for BIOS PXE booting as well. *shudders at the memories of dealing with pxelinux* GRUB is way better for that. Yes, you can use GRUB for PXE and UEFI netboot too. That's what I use for both. Would you care to document your set-ups? It'

Re: How to set the (virtual) BIOS time before a VM boots

On Tue, May 25, 2021 at 9:43 PM Samuel Sieb wrote: > On 2021-05-25 6:10 p.m., Fulko Hew wrote: > > I'm trying to do some Y2038 testing, using VMs. > > So what I'd like to do is have the time pre-set to after the Y2038 time > > and then boot an OS/VM (to have the &#

Re: How to set the (virtual) BIOS time before a VM boots

On 2021-05-25 6:10 p.m., Fulko Hew wrote: I'm trying to do some Y2038 testing, using VMs. So what I'd like to do is have the time pre-set to after the Y2038 time and then boot an OS/VM (to have the 'BIOS' provide the post 2038 time). (In this case I'm trying to test an

How to set the (virtual) BIOS time before a VM boots

I'm trying to do some Y2038 testing, using VMs. So what I'd like to do is have the time pre-set to after the Y2038 time and then boot an OS/VM (to have the 'BIOS' provide the post 2038 time). (In this case I'm trying to test an application under Win XP.) [Please, no emai

Re: bios configuration to install fedora-33

so, you probably need to disable "fastboot" in Windows (to install Fedora and again when Windows is updated). > > At boot time, I can see the menu: > Install Fedora 33 > Test this media... > troubleshooting > > But that's all... nothing happens if I choose any o

Re: bios configuration to install fedora-33

Le 22/12/2020 à 15:41, Jorge Fábregas a écrit : On 12/22/20 5:23 AM, François Patte wrote: What is the right config in the bios to perform a linux install with these "new" motherboard. Hi, There's nothing special really. Either you boot in UEFI mode or Legacy mode (appe

Re: bios configuration to install fedora-33

On 12/22/20 5:23 AM, François Patte wrote: > What is the right config in the bios to perform a linux install with > these "new" motherboard. Hi, There's nothing special really. Either you boot in UEFI mode or Legacy mode (appears as "CSM" in firmware options). I

bios configuration to install fedora-33

at is the right config in the bios to perform a linux install with these "new" motherboard. Thank you for any help. -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33

Re: Lost the UEFI boot info that my BIOS shows

t used to involve a 2nd disk drive, but now, these new laptops no longer have easily accessible drives, and that just makes it all the more difficult and tedious. P.S. Now that I have the new install, I'm seeing that my CPU fan is no longer spinning. The Dell/BIOS test program can control the

Re: Lost the UEFI boot info that my BIOS shows

you don't have a backup for it to restore then ... 2) try to enable CSM in your UEFI setup so that your system can boot in BIOS mode hoping you still have a working MBR and GRUB is installed there (see if it boots). If that doesn work... 3) grab what you need from booting off the USB stick a

Re: Lost the UEFI boot info that my BIOS shows

On Sun, Nov 29, 2020 at 8:23 AM Jorge Fábregas wrote: > On 11/28/20 11:48 PM, Fulko Hew wrote: > > > > 'DEVNAME': '/dev/sda1', > > 'DEVPATH': > > > '/devices/pci:00/:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1', > > 'ID_FS_TYPE': 'vfat', > > 'ID_PART_ENTRY_NAME': 'EFI\\x20System

Re: Lost the UEFI boot info that my BIOS shows

On 11/28/20 11:48 PM, Fulko Hew wrote: > > 'DEVNAME': '/dev/sda1', > 'DEVPATH': > '/devices/pci:00/:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1', > 'ID_FS_TYPE': 'vfat', > 'ID_PART_ENTRY_NAME': 'EFI\\x20System\\x20Partition', > 'ID_PART_ENTRY_NUMBER': '1', > 'ID_PART_ENTRY_OFFSET

Re: Lost the UEFI boot info that my BIOS shows

On Sat, 2020-11-28 at 22:48 -0500, Fulko Hew wrote: > What I forgot to say, was that this is a F26 system, > so I can't find an efibootmgr string. That's a pretty important detail. F26 was EOLed at the end of May 2018. You really need to update to at least F32. poc ___

Re: Lost the UEFI boot info that my BIOS shows

On Sat, Nov 28, 2020 at 9:17 PM Jorge Fábregas wrote: > On 11/28/20 9:27 PM, Fulko Hew wrote: > > Any idea what happened to my HD boot info in my BIOS, or how to restore > it? > > PS. It is a Dell laptop. > > Hi, > > I'm assuming you're booting off a U

Re: Lost the UEFI boot info that my BIOS shows

On 11/28/20 9:27 PM, Fulko Hew wrote: > Any idea what happened to my HD boot info in my BIOS, or how to restore it? > PS. It is a Dell laptop. Hi, I'm assuming you're booting off a UEFI-based system and that you lost the menu entry stored in NVRAM corresponding to "Fedora&qu

Lost the UEFI boot info that my BIOS shows

and performed my backup. Now I wanted to go back and try to diagnose/fix my root filesystem issue. Sadly, my BIOS no longer knows about the bootable entity on the HD, and only shows me the Flash drive (even if it's not plugged in). Any idea what happened to my HD boot info in my BIOS, or h

Re: Boot & Bios Issues

On 5/7/19 7:43 PM, S. Bob wrote: Oddly enough the slow boot / shutdowns have dissappeared, the only remaining issue is the bios setting weirdness, including the fact that Linux will not boot without legacy OS Boot = on That's not weird. You don't have an EFI boot partition, so yo

Re: Boot & Bios Issues

On Tue, May 7, 2019 at 8:44 PM S. Bob wrote: > > Oddly enough the slow boot / shutdowns have dissappeared, the only > remaining issue is the bios setting weirdness, including the fact that > Linux will not boot without legacy OS Boot = on > > > Thoughts? From my first

Re: Boot & Bios Issues

Oddly enough the slow boot / shutdowns have dissappeared, the only remaining issue is the bios setting weirdness, including the fact that Linux will not boot without legacy OS Boot = on Thoughts? On 5/7/19 8:08 PM, Chris Murphy wrote: On Tue, May 7, 2019 at 3:54 PM S. Bob wrote: root

Re: Boot & Bios Issues

On 05/07/2019 08:08 PM, Chris Murphy wrote: You can add '> journal.log' to output to a file and post it somewhere Or, you can use | tee journal.log so you can keep a copy and see the results yourself if you prefer. ___ users mailing list -- users@li

Re: Boot & Bios Issues

On Tue, May 7, 2019 at 3:54 PM S. Bob wrote: > > root@F30-host # cat /etc/fstab > > # > # /etc/fstab > # Created by anaconda on Wed Dec 31 19:25:43 1997 > # > # Accessible filesystems, by reference, are maintained under '/dev/disk/'. > # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8)

Re: Boot & Bios Issues

a windows boot manager, showing several options, like this: 1. ATA HDD1: HFS512G39TNF-N3A0A 2. ATA HDD2: CT1000MX500SSD4 3. Windows Boot Manager Then I need to power off again and change the following bios settings, they always get changed when I hard power off: Legacy OS Boot - (Gets set to Disable

Re: Boot & Bios Issues

rd power off then it boots to what seems to be a > windows boot manager, showing several options, like this: > > 1. ATA HDD1: HFS512G39TNF-N3A0A > > 2. ATA HDD2: CT1000MX500SSD4 > > 3. Windows Boot Manager > > > Then I need to power off again and change the following bios

Boot & Bios Issues

urnal to persistent storage 3) If I ever do a hard power off then it boots to what seems to be a windows boot manager, showing several options, like this: 1. ATA HDD1: HFS512G39TNF-N3A0A 2. ATA HDD2: CT1000MX500SSD4 3. Windows Boot Manager Then I need to power off again and change the following b

Re: UEFI boot with BIOS password, am I screwed?

wants, whatever that is. > >> e.g. if something with the Fedora bootloader gets nerfed then it'd > >> boot Windows. > > > > > > I'm pressing F12 and manually selecting Fedora, but I did later try to > change the boot order, both with efibootmgr and in th

Re: UEFI boot with BIOS password, am I screwed?

sary to list everything in bootorder, you can just >> have one. The idea of populating it fully is to have exactly the >> predictable fallback boot behavior the user wants, whatever that is. >> e.g. if something with the Fedora bootloader gets nerfed then it'd >> b

Re: UEFI boot with BIOS password, am I screwed?

edictable fallback boot behavior the user wants, whatever that is. > e.g. if something with the Fedora bootloader gets nerfed then it'd > boot Windows. > I'm pressing F12 and manually selecting Fedora, but I did later try to change the boot order, both with efibootmgr and in the BIOS to

Re: UEFI boot with BIOS password, am I screwed?

On Wed, Apr 24, 2019 at 8:02 AM Richard Shaw wrote: > > While I had to run it through the shredder I finally sat down and went > through all the passwords I've ever used and figured it out :) > > I turned off Secure Boot but it still won't boot Fedora. > > I finally figured out I had to use -v to

Re: UEFI boot with BIOS password, am I screwed?

While I had to run it through the shredder I finally sat down and went through all the passwords I've ever used and figured it out :) I turned off Secure Boot but it still won't boot Fedora. I finally figured out I had to use -v to get what I wanted from efibootmgr: BootCurrent: 0001 Timeout: 0

Re: UEFI boot with BIOS password, am I screwed?

. > > I assume one is for the old system and one for the new. > > When I try to go into advanced settings in Win10 to change UEFI settings > it reboots me but there is a password on the BIOS. I can't remember if I > set a password of maybe the kids did somehow but I have

  1   2   3   >