booting fedora project image

I have tried to boot from Fedora's g'ziped tarball on GCP. I find it hard to understand how to do this. GCP's instructions seem vague Videos I find on youtube also seem to be old and out of date. I know you upload this to a bucket but how do you get it to a VM to install and boot? Is anyone

Re: booting with test_fs set

On Mon, 2022-10-17 at 16:04 -0400, Bill Cunningham wrote: > Ok I will do like I did with this post. I cut off all below the bottom > line and the line its' self this time. I hit enter for a new line and > posted this, so I wasn't top posting. Did this work? Yes, that worked brilliantly. --

Re: booting with test_fs set

On Mon, 2022-10-17 at 16:04 -0400, Bill Cunningham wrote: > > On 10/17/2022 6:09 AM, Patrick O'Callaghan wrote: > > On Mon, 2022-10-17 at 13:43 +1030, Tim via users wrote: > > > Leave a completely blank line between quotes and reply, do not > > > type > > > immediately below quotes (like I've

Re: booting with test_fs set

On 10/17/22 13:04, Bill Cunningham wrote: Ok I will do like I did with this post. I cut off all below the bottom line and the line its' self this time. I hit enter for a new line and posted this, so I wasn't top posting. Did this work? Yes, that was perfect!

Re: booting with test_fs set

On 10/17/2022 6:09 AM, Patrick O'Callaghan wrote: On Mon, 2022-10-17 at 13:43 +1030, Tim via users wrote: Leave a completely blank line between quotes and reply, do not type immediately below quotes (like I've done, above).  Various email clients re-wrapping functions make a mess of separating

Re: booting with test_fs set

On Mon, 2022-10-17 at 13:43 +1030, Tim via users wrote: > Leave a completely blank line between quotes and reply, do not type > immediately below quotes (like I've done, above).  Various email > clients re-wrapping functions make a mess of separating different > paragraphs if you don't do that. 

Re: booting with test_fs set

On Sun, 2022-10-16 at 13:35 -0700, Samuel Sieb wrote: > What is your email client doing to make your reply appear quoted? That > makes it difficult to find it. He's probably doing what a lot people do: Not leaving a blank line between quotes and his reply. Leave a completely blank line

Re: booting with test_fs set

thought it was to force a test of the filesystem before booting. I have ran e2fsck before and the mount was clean. Run it again and no it was dirty. That flag is definitely not for that purpose. "force_fsck" would do that. You don't want to be using "test_fs". What is you

Re: booting with test_fs set

of the filesystem before booting. I have ran e2fsck before and the mount was clean. Run it again and no it was dirty. B ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct

Re: booting with test_fs set

On 10/15/22 14:33, Bill Cunningham wrote: IDK why my system seems to hang when I set the test_fs option. tune2fs -E test_fs /dev/sda3 'exactly what I type' and reboot. Why are you setting that? That's a special development flag. ___ users mailing

booting with test_fs set

works. But same booting results when the test_fs flag is set. I am grasping at straws there in adding and removing the journal. No change there though, doesn't seem to hurt anything. Maybe there's an error that e2fsck isn't reporting and I should ask it to dig deeper? IDK Does anyone have

Re: Dual booting

I'm going to put off dealing with the "new" computer until I get another VGA cable. This computer also requires a VGA cable, which makes using the "new" one a bit of a bother. -- Michael henne...@web.cs.ndsu.nodak.edu "Sorry but your password must contain an uppercase letter, a number, a

Re: Dual booting

On 7/3/22 22:04, Michael Hennebry wrote: On Sat, 2 Jul 2022, George N. White III wrote: On Wed, Jun 29, 2022 at 6:23 PM Robert McBroom via users < users@lists.fedoraproject.org> wrote: Do you plan to have the user "home" directory in a separate partition? There have been glitches with

Re: Dual booting

On Wed, 2022-07-06 at 09:16 +1000, Stephen Morris wrote: > I'm tri-booting between Win11, Fedora and Ubuntu. I used to have the > bios time configured to local time and found that Linux assumed the > bios time was UTC, and didn't provide an easy way of changing that, > and hence w

Re: Dual booting

On 4/7/22 22:37, Tim via users wrote: Barry wrote: I ran duel boot win10+fedora like this, now I duel boot win11+fedora in this way. Patrick O'Callaghan: Duel? Are they fighting each other? Sorry :-) I think it's rather apt. Not sorry ;-) I'm tri-booting between Win11, Fedora and Ubuntu. I

Re: Dual booting

Barry wrote: >> I ran duel boot win10+fedora like this, >> now I duel boot win11+fedora in this way. Patrick O'Callaghan: > Duel? Are they fighting each other? > > Sorry :-) I think it's rather apt. Not sorry ;-) -- uname -rsvp Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28

Re: Dual booting

On Mon, 2022-07-04 at 08:13 +0100, Barry wrote: > I ran duel boot win10+fedora like this, > now I duel boot win11+fedora in this way. Duel? Are they fighting each other? Sorry :-) poc ___ users mailing list -- users@lists.fedoraproject.org To

Re: Dual booting

> On 4 Jul 2022, at 03:11, Michael Hennebry > wrote: > > On Sat, 2 Jul 2022, George N. White III wrote: > >>> On Wed, Jun 29, 2022 at 6:23 PM Robert McBroom via users < >>> users@lists.fedoraproject.org> wrote: >> >> Do you plan to have the user "home" directory in a separate partition? >>

Re: Dual booting

get Linux to run well using local time, that's second best. Though be prepared to have a fight around daylight savings time changes (Linux usually worked well enough by itself, in local time, but dual booting may require you to manually intervene on both sides, so both sides feel they've correctly

Re: Dual booting

On Sat, 2 Jul 2022, George N. White III wrote: On Wed, Jun 29, 2022 at 6:23 PM Robert McBroom via users < users@lists.fedoraproject.org> wrote: Do you plan to have the user "home" directory in a separate partition? There have been glitches with configuration details stored in the users home

Re: Dual booting

Fedora) > > in case I ever need Windows for something. > > > > I have set up dual booting before, > > but it has been a long time. > > Ideally it would be a triple boot: > > one for Windows, one that I just installed > > and one that I've been using latel

Re: Dual booting

Windows' tools to shrink NTFS and its partition. But more importantly make sure to disable Fast Still, why a two-step? Why not with Windows tools or with Linux tools? startup.https://dev.to/xeroxism/how-to-disable-fast-start-in-ubuntu-windows-dual-booting-setup-4akn Now that I had not known

Re: Dual booting

last. If firmware is UEFI, the order doesn't matter. I agree with the suggestions to use Windows' tools to shrink NTFS and its partition. But more importantly make sure to disable Fast startup.https://dev.to/xeroxism/how-to-disable-fast-start-in-ubuntu-windows-dual-booting-setup-4akn -- Chris

Re: Dual booting

On 6/30/22 16:17, Michael Hennebry wrote: Thanks. On Wed, 29 Jun 2022, Robert McBroom via users wrote: On 6/29/22 00:16, Michael Hennebry wrote: I think that I would want to dual-boot it (Windows/Fedora) in case I ever need Windows for something. Here is how I do the booting on a Dell

Re: Dual booting

Thanks. On Wed, 29 Jun 2022, Robert McBroom via users wrote: On 6/29/22 00:16, Michael Hennebry wrote: I think that I would want to dual-boot it (Windows/Fedora) in case I ever need Windows for something. Here is how I do the booting on a Dell Studio. The first step is to use the windows

Re: Dual booting

:   350 MB C:    930.44 GB recovery: 750 MB I think that I would want to dual-boot it (Windows/Fedora) in case I ever need Windows for something. I have set up dual booting before, but it has been a long time. Ideally it would be a triple boot: one for Windows, one that I just installed and one

Dual booting

I think that I would want to dual-boot it (Windows/Fedora) in case I ever need Windows for something. I have set up dual booting before, but it has been a long time. Ideally it would be a triple boot: one for Windows, one that I just installed and one that I've been using lately. Mostly what I

Re: PXE GRUB booting for BIOS and UEFI

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's pretty simple. I just

Problem with kernel 5.16.16 not auto booting on 1 machine??

Have 5 linux machines at home. 3 with Fedora 34 and 2 with Fedora 35. 4 did the dnf update that included 5.16.16 and rebooted fine. The one system didn't?? Have 3 machine I vnc into, and have one monitor that I connect when I need to look at them. When I couldn't get to the machine after

Re: Machine won't finish booting after update

On Tue, 18 Jan 2022 22:58:28 -0500 Fulko Hew wrote: > On a lark, today I saw that Discover was telling me there were > updates. I asked it to show me what. > After a number of minutes it told me... 7 packages. > OK, I did a 'dnf update' instead. > After 30 seconds it had fetched and installed

Re: Machine won't finish booting after update

On Mon, Jan 17, 2022 at 11:29 PM Joe Zeff wrote: >> On 1/17/22 6:31 PM, Fulko Hew wrote: >> What I don't remember is what this multi-stage install-reboot was trying >> to accomplish. >> Looking back in messages or journalctl, I don't see anything. >> But it was doing something explicitly. >> > If

Re: Machine won't finish booting after update

On Tue, 18 Jan 2022 at 12:31, stan via users wrote: > On Tue, 18 Jan 2022 09:22:55 -0700 > stan wrote: > > > In boot, there should be a config file for that latest kernel. Run > > the command > > grep -i vfat config[latest kernel text] > > If there is no vfat, this will show it, but I think

Re: Machine won't finish booting after update

On Tue, 18 Jan 2022 09:22:55 -0700 stan wrote: > In boot, there should be a config file for that latest kernel. Run > the command > grep -i vfat config[latest kernel text] > If there is no vfat, this will show it, but I think all fedora kernels > are built with drivers for vfat built in. >

Re: Machine won't finish booting after update

On Mon, 17 Jan 2022 17:20:17 -0500 Fulko Hew wrote: > After a lot of experimentation, I did get the previous kernel to boot > all the way to the GUI. (I don't know why that didn't work the first > time I tried it.) So I'm back to a working system. > My hardware is fine. > And that older

Re: Machine won't finish booting after update

On 1/17/22 6:31 PM, Fulko Hew wrote: What I don't remember is what this multi-stage install-reboot was trying to accomplish. Looking back in messages or journalctl, I don't see anything. But it was doing something explicitly. If you were installing something, try dnf history.

Re: Machine won't finish booting after update

c, it's what's called a mandelbug. > When booting the new kernel, it fails the same way every time. Very deterministic. mount: /boot/efi: unknown filesystem type 'vfat'. What I don't remember is what this multi-stage install-reboot was trying to accomplish. Looking back in messages or journalc

Re: Machine won't finish booting after update

On 1/17/22 11:59 AM, stan via users wrote: Suspicious that this is not deterministic. It should either fail identically every time or restart every time (in my opinion). If it's really nnondeterministic, it's what's called a mandelbug. ___ users

Re: Machine won't finish booting after update

On Mon, Jan 17, 2022 at 2:00 PM stan via users < users@lists.fedoraproject.org> wrote: > On Sun, 16 Jan 2022 21:07:29 -0500 > Fulko Hew wrote: > > > I decided to log out and log back in to my X11 based KDE session just > > now, and I saw that 'Discover' was telling me I had updates available. >

Re: Machine won't finish booting after update

On Sun, 16 Jan 2022 21:07:29 -0500 Fulko Hew wrote: > I decided to log out and log back in to my X11 based KDE session just > now, and I saw that 'Discover' was telling me I had updates available. > So I said 'go ahead'. > Eventually, it said I needed to reboot, so I did. > After 4 (or 5)

Machine won't finish booting after update

I decided to log out and log back in to my X11 based KDE session just now, and I saw that 'Discover' was telling me I had updates available. So I said 'go ahead'. Eventually, it said I needed to reboot, so I did. After 4 (or 5) reboots that the machine drove itself through, the last reboot failed

Re: Booting F35 install from USB on Thinkpad X1 6th gen

On 11/14/21 14:27, George N. White III wrote: On Sun, 14 Nov 2021 at 02:58, Frederic Muller wrote: Hi! Trying to perform a fresh install of F35 on my (wife's) X1 Carbon 6th gen and while it did work in the past with UEFI USB boot option enabled in Bios, it seems not to

Re: Booting F35 install from USB on Thinkpad X1 6th gen

On 11/13/21 22:57, Frederic Muller wrote: Trying to perform a fresh install of F35 on my (wife's) X1 Carbon 6th gen and while it did work in the past with UEFI USB boot option enabled in Bios, it seems not to with F35. I "burned" the usb as usual with livecd-iso-to-disk --format --reset-mbr

Re: Booting F35 install from USB on Thinkpad X1 6th gen

On Sun, 14 Nov 2021 at 02:58, Frederic Muller wrote: > Hi! > > Trying to perform a fresh install of F35 on my (wife's) X1 Carbon 6th > gen and while it did work in the past with UEFI USB boot option enabled > in Bios, it seems not to with F35. > > I "burned" the usb as usual with

Booting F35 install from USB on Thinkpad X1 6th gen

Hi! Trying to perform a fresh install of F35 on my (wife's) X1 Carbon 6th gen and while it did work in the past with UEFI USB boot option enabled in Bios, it seems not to with F35. I "burned" the usb as usual with livecd-iso-to-disk --format --reset-mbr

Re: F32 not booting

First problem is: [8.090730] shure kernel: EXT4-fs (dm-0): unable to read superblock [8.090784] shure mount[471]: mount: /sysroot: can't read superblock on /dev/mapper/fedora_shure-root. Therefore sysroot can't mount. The reason it can't read it is really bad luck: [ 10.481731] shure

Re: F32 not booting

On Thu, 28 Jan 2021 at 11:09, GianPiero Puccioni < gianpiero.pucci...@isc.cnr.it> wrote: > On 1/27/21 3:23 PM, George N. White III wrote: > > On Wed, 27 Jan 2021 at 05:17, GianPiero Puccioni < > gianpiero.pucci...@isc.cnr.it > > > wrote: > > > > Hi, > > >

Re: F32 not booting

On 1/27/21 3:23 PM, George N. White III wrote: On Wed, 27 Jan 2021 at 05:17, GianPiero Puccioni > wrote: Hi, yesterday my laptop with F32 didn't boot. It goes in emergency mode and creates a rdsosreport file I usually don't do this but

Re: F32 not booting

ing may not be available to users these days). Many users complain that their laptop has slowed down when a disk is doing a lot of "bad" block replacements. If I hear about the slowdown I try to get them a replacement disk. Soon after the slowdown starts the system will fail to boot but in

F32 not booting

Hi, yesterday my laptop with F32 didn't boot. It goes in emergency mode and creates a rdsosreport file I usually don't do this but this time when I installed F I let the system create the partitions and I think it's LVM with XFS but I'm not sure of the latter and I am not familiar with this

Re: booting problem

I booted from dvd. I used it becuase it had the uefi files on it. I used fdisk to check the install hd. It was still set to gpt but i set it again anyway. I could not find any way in the bios to switch between uefi and bios mode. After I rebooted the normal settings were there but they

Re: booting problem

on the motherboard. It also sounds like the Centos installer you are booting may be a legacy installer, in which case you might be better off obtaining a live cd/dvd of a Centos UEFI system. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org

Re: booting problem

On Wed, Jun 03, 2020 at 12:52:05AM -0400, doug.lindqu...@atlanticbb.net wrote: > I recently tried to install Centos 8 on my 3tb uefi hd that already had > Fedora 32 and Windows 10 on it. The Centos installation did not finish > because it could install the boot loader.  It ended up screwing up

booting problem

I recently tried to install Centos 8 on my 3tb uefi hd that already had Fedora 32 and Windows 10 on it. The Centos installation did not finish because it could install the boot loader.  It ended up screwing up the uefi boot because it will no longer boot to anything.  It looks like the bios

Re: Grub stops before booting F31

On 5/7/20 7:07 PM, and...@gn.apc.org wrote: At boot, Grub enters its rescue mode with the message error: unknown file system. Have you tried re generating the grub files for the bootloader ? You might have to do a chroot. -- Regards, Sreyan ___

Grub stops before booting F31

Hello! I seem to have inadvertently change partition 1 on my hard disk ... At boot, Grub enters its rescue mode with the message error: unknown file system. If I use my Fedora 32 live USB to boot then I can bring up the F32 desktop. If I run Disks utility then I have: Partition 1: size 1.1GB

Live cd's have problems booting with amd 3700x cpu and MSI x 570 a pro mother board

i had problems installing fedora on a new pc and wanted to share what happened. i filed a bugzilla report https://bugzilla.redhat.com/show_bug.cgi?id=1740334 using gtx 1660 ti video card fails on fedora 29 using gtx 1050 ti works on fedora 29 using fedora 30 fails with both gtx 1050 ti and gtx

Re: Booting impossible

I am curious. Checking in the info --boot-directory=DIR' Install GRUB images under the directory 'DIR/grub/' It means that in your example, it will be installed in /boot/efi/EFI/fedora/grub while the default is /boot On my machine there is not /boot/grub (inly a /boot/grub2) and no

Re: Booting impossible

On Wed, Jun 26, 2019 at 1:24 PM Patrick Dupre wrote: >> >> grub2-install --boot-directory=/boot /dev/sda > > This is what I do not understand: > --boot-directory=/boot is the default > then > grub2-install /dev/sda --boot-directory=/boot/efi/EFI/fedora

Re: Booting impossible

On Tue, Jun 25, 2019 at 9:10 PM stan via users wrote: > > re-install the shim and grub-efi. e.g. > dnf reinstall grub2-efi shim-ia32 shim-x64 dnf reinstall grub2-efi-x64 shim-x64 No need for shim-ia32 on x64. ___ users mailing list --

Re: Booting impossible

On Tue, Jun 25, 2019 at 8:11 PM Patrick Dupre wrote: > > The situation is becoming worst and worst. > I tried an grub2-install /dev/sda > Now, I cannot boot at all. > I just enter in to a grub menu from here I am stuck. "grub2-install /dev/sda" isn't good on EFI. On Fedora, you need:

Re: Booting impossible

On Thu, 27 Jun 2019 16:12:10 +0200 "Patrick Dupre" wrote: > Hello, > > The issue is fixed. But I cannot really gives a recipes. > The issue was in the generation of the grub.cfg > 1) It did let boot on system 1 when generated by system 2 (it looks > that a efilinux and efiinitrd were missing).

Re: Booting impossible

ence, I reinstalled the old > > /boot/efi. > > So, you updated a bios F28 to efi F30? I don't know how well that is > supported, but it sounds like a recipe for trouble. > > > Lucky, I was able to boot on my "old" system. > > I booted 2 times and then I run > &g

Re: Booting impossible

times and then I run > grub2-mkconfig /boot/efi/fedora/grub.cfg because I wanted to be able > to have the option of booting of 2 systems. But, then, no way to > reboot, any of the systems. I tried tons of times from the bios > configuration. No way. I tried to boot by using the "

Re: Booting impossible

Ok On Wed, 2019-06-26 at 11:45 -0700, Samuel Sieb wrote: > On 6/25/19 12:31 PM, Igor Bezrodnik wrote: > > Patrick if you use uefi system once you boot do this steps: > > ) sudo grub2-install /dev/sda/ > > Please do not suggest this any more. On an EFI system, it will not > help > and might

Re: Booting impossible

On 6/25/19 12:31 PM, Igor Bezrodnik wrote: Patrick if you use uefi system once you boot do this steps: ) sudo grub2-install /dev/sda/ Please do not suggest this any more. On an EFI system, it will not help and might harm things. ___ users mailing

Re: Booting impossible

> > == > > > > > > > Sent: Tuesday, June 25, 2019 at 9:09 PM > > > From: "Igor Bezrodnik" > > > To: users@lists.fedoraproject.org > > > Subject: Re: Booting impossible

Re: Booting impossible

0, 21078 DIJON Cedex FRANCE > Tel: +33 (0)380395988 > = > == > > > > Sent: Tuesday, June 25, 2019 at 9:09 PM > > From: "Igor Bezrodnik" > > To: users@lists.fedoraproject.org > > Subject: Re: Booting imposs

Re: Booting impossible

ent: Tuesday, June 25, 2019 at 9:09 PM > From: "Igor Bezrodnik" > To: users@lists.fedoraproject.org > Subject: Re: Booting impossible > > Patrick, you need this steps to boot your system : > > Using the GRUB2 boot prompt > > If improperly configured, GRUB

Re: Booting impossible

mbr saved for sda and I reinstalled the default mbr, and I also had a /boot/efi saved. Hence, I reinstalled the old /boot/efi. Lucky, I was able to boot on my "old" system. I booted 2 times and then I run grub2-mkconfig /boot/efi/fedora/grub.cfg because I wanted to be able to have the op

Re: Booting impossible

Patrick if you use uefi system once you boot do this steps: ) sudo grub2-install /dev/sda/ 2) sudo dnf reinstall grub2-efi-x64 shim-ia32 shim-x6 3) sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg On Tue, 2019-06-25 at 19:20 +0200, Patrick Dupre wrote: > Hello, > > The situation is becoming

Re: Booting impossible

Patrick, you need this steps to boot your system : Using the GRUB2 boot prompt If improperly configured, GRUB2 may fail to load and subsequently drop to a boot prompt. To address this issue, proceed as follows: 1) Load the XFS and LVM modules insmod xfs insmod lvm 2) List the

Re: Booting impossible

could have fedora, suse, ubuntu, debian, windows, etc. installed, and they could all be selected and boot from that same /boot/efi, but not a second version of any of them. Kind of clumsy, and makes it hard to run a backup version of Fedora other than by putting it on a different disk, and bootin

Re: Booting impossible

On Tue, 25 Jun 2019 11:23:49 -0700 stan wrote: > dnf reinstall grub2-efi shim-ia32 shim-x64 This should be dnf reinstall grub2-efi-x64 shim-ia32 shim-x64 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to

Re: Booting impossible

On Tue, 25 Jun 2019 19:20:32 +0200, Patrick Dupre wrote: > Hello, > > The situation is becoming worst and worst. > I tried an grub2-install /dev/sda When did you run that command? Within a running working installation? And why did you run it? > Now, I cannot boot at all. > I just enter in to a

Re: Booting impossible

like you are throwing mud at the wall, and hoping something will stick. That's a recipe for disaster when troubleshooting computer systems. Calm and methodical, that's the way. I know only a little about UEFI booting, though I recently got it working. My understanding is that there can be only one de

Booting impossible

Hello, The situation is becoming worst and worst. I tried an grub2-install /dev/sda Now, I cannot boot at all. I just enter in to a grub menu from here I am stuck. Can I collect a bit of help? Thank. === Patrick DUPRÉ

Re: booting and NVME on older motherboards

On 10/24/18 3:55 PM, Gordon Messmer wrote: On 10/24/18 2:11 PM, Wolfgang S. Rupprecht wrote: Is copying the /boot and /boot/efi partitions to the sata drive and editing /boot/efi/EFI/fedora/grub.cfg to point the /dev/sda instead of /dev/nvme0n1 all that needs doing?  No hidden firmare on the

Re: booting and NVME on older motherboards

On 10/24/18 2:11 PM, Wolfgang S. Rupprecht wrote: Is copying the /boot and /boot/efi partitions to the sata drive and editing /boot/efi/EFI/fedora/grub.cfg to point the /dev/sda instead of /dev/nvme0n1 all that needs doing? No hidden firmare on the bootable drive like in the bios days? Is

booting and NVME on older motherboards

Has anyone gone through the exercise of setting up the boot environment for booting fedora on a system with an NVME drive where the motherboard UEFI code doesn't understand NVME disks? I did a clean install of fedora to the nvme and let anacondia do its thing. The only non-default item

Re: Problem PXE booting Fedora 28

.1 >>    NBP filename is uefi/shim.efi >>    NBP filesize is 1210776 Bytes >>   Downloading NBP file... >> >>    NBP file downloaded successfully. >> Fetching Netboot Image >> >> >> And there it hangs. I'm not sure how to debug to see

Re: Problem PXE booting Fedora 28

.1 >>    NBP filename is uefi/shim.efi >>    NBP filesize is 1210776 Bytes >>   Downloading NBP file... >> >>    NBP file downloaded successfully. >> Fetching Netboot Image >> >> >> And there it hangs. I'm not sure how to debug to see

Re: Problem PXE booting Fedora 28

is trying to do. This UEFI PXE booting is totally new for me, so I may be missing something terribly obvious. If you could get a log of requests from the tftp server that would have helped you. However, I don't think it does that. Many times I used strace on the tftp server to find out wha

Re: Problem PXE booting Fedora 28

EFI guest, transcribed manually) >>Start PXE over IPv4 Station IP address is 10.1.14.186 Server IP address is 10.1.4.1 NBP filename is uefi/shim.efi NBP filesize is 1210776 Bytes Downloading NBP file... NBP file downloaded successfully. Fetching Netboot Image And there it hangs

Re: Problem PXE booting Fedora 28

On 2018-10-15 2:21 p.m., Samuel Sieb wrote: > On 10/15/18 10:55 AM, Digimer wrote: >> That worked!! Thank you so much! I bashed my head on this since >> Thursday... > > It took me a while to get this working initially when I started it > several years ago.  At some point, I want to see if I can

Re: Problem PXE booting Fedora 28

On 10/15/18 10:55 AM, Digimer wrote: That worked!! Thank you so much! I bashed my head on this since Thursday... It took me a while to get this working initially when I started it several years ago. At some point, I want to see if I can get grub loading instead of pxelinux, although I don't

Re: Problem PXE booting Fedora 28

On 2018-10-15 12:44 p.m., Samuel Sieb wrote: > On 10/15/18 8:53 AM, Digimer wrote: >> Here's the PXE menu (with kernel options) I am using; >> >> >> label linux >> menu label ^Install Fedora 28 64-bit >> menu default >> kernel fedora28/vmlinuz >> append initrd=fedora28/initrd.img >>

Re: Problem PXE booting Fedora 28

On 10/15/18 8:53 AM, Digimer wrote: Here's the PXE menu (with kernel options) I am using; label linux menu label ^Install Fedora 28 64-bit menu default kernel fedora28/vmlinuz append initrd=fedora28/initrd.img inst.stage2=http://10.1.4.1/fedora28/x86_64/os/ ip=dhcp ksdevice=eth0 rd.shell

Re: Problem PXE booting Fedora 28

On 2018-10-15 2:52 a.m., Samuel Sieb wrote: > On 10/14/18 8:17 PM, Digimer wrote: >> https://docs.fedoraproject.org/en-US/fedora/f28/install-guide/advanced/Network_based_Installations/ >> >> >> I've got to the point where I can PXE boot fine, the kernel and >> initrd.img are downloaded by the

Re: Problem PXE booting Fedora 28

On 2018-10-15 2:52 a.m., Samuel Sieb wrote: > On 10/14/18 8:17 PM, Digimer wrote: >> https://docs.fedoraproject.org/en-US/fedora/f28/install-guide/advanced/Network_based_Installations/ >> >> >> I've got to the point where I can PXE boot fine, the kernel and >> initrd.img are downloaded by the

Re: Problem PXE booting Fedora 28

On 10/14/18 8:17 PM, Digimer wrote: https://docs.fedoraproject.org/en-US/fedora/f28/install-guide/advanced/Network_based_Installations/ I've got to the point where I can PXE boot fine, the kernel and initrd.img are downloaded by the client, but then the install fails and drops to the dracut

Problem PXE booting Fedora 28

Hi all, I tried following this; https://docs.fedoraproject.org/en-US/fedora/f28/install-guide/advanced/Network_based_Installations/ I've got to the point where I can PXE boot fine, the kernel and initrd.img are downloaded by the client, but then the install fails and drops to the dracut

Re: Screen goes dark when booting latest kernel

On Sat, Jun 16, 2018 at 7:11 PM, Samuel Sieb wrote: > On 06/16/2018 09:05 AM, Alex wrote: >> >> Hi all, this appears to be a problem with the latest kernels and >> Radeon cards (at least). Adding 'nomodeset' to the kernel command-line >> fixes it. > > What video device do you have? Look in the

Re: Screen goes dark when booting latest kernel

On 06/16/2018 09:05 AM, Alex wrote: Hi all, this appears to be a problem with the latest kernels and Radeon cards (at least). Adding 'nomodeset' to the kernel command-line fixes it. What video device do you have? Look in the output of "lspci" for a line containing "VGA".

Re: Screen goes dark when booting latest kernel

Hi all, this appears to be a problem with the latest kernels and Radeon cards (at least). Adding 'nomodeset' to the kernel command-line fixes it. Has anyone else experienced this where the screen goes blank shortly after booting and is completely unresponsive? On Tue, Jun 12, 2018 at 11:10 PM

Re: Screen goes dark when booting latest kernel

On 06/13/18 10:47, Alex wrote: > Hi, > > On Tue, Jun 12, 2018 at 6:16 PM, Ed Greshko wrote: >> On 06/13/18 04:45, Alex wrote: >>> Hi, >>> I have a fedora27 system on an older x86_64 machine and when booting >>> the latest kernel (I believe it was just r

Re: Screen goes dark when booting latest kernel

Hi, On Tue, Jun 12, 2018 at 6:16 PM, Ed Greshko wrote: > On 06/13/18 04:45, Alex wrote: >> Hi, >> I have a fedora27 system on an older x86_64 machine and when booting >> the latest kernel (I believe it was just released today) as well as >> the previous two, the di

Re: Screen goes dark when booting latest kernel

No.  During boot, on the main session shows what is transpiring, but one of the other screens shows all the messages. On 06/12/2018 06:00 PM, Samuel Sieb wrote: On 06/12/2018 02:44 PM, Robert Moskowitz wrote: Is it to get the log session or is it F6? What log session?  Are you thinking of

Re: Screen goes dark when booting latest kernel

On 06/13/18 04:45, Alex wrote: > Hi, > I have a fedora27 system on an older x86_64 machine and when booting > the latest kernel (I believe it was just released today) as well as > the previous two, the display goes dark and becomes unresponsive. > > I've booted into the rescu

Re: Screen goes dark when booting latest kernel

On 06/12/2018 02:44 PM, Robert Moskowitz wrote: Is it to get the log session or is it F6? What log session? Are you thinking of the installer? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to

Re: Screen goes dark when booting latest kernel

Is it to get the log session or is it F6? On 06/12/2018 05:09 PM, Samuel Sieb wrote: On 06/12/2018 01:58 PM, Alex wrote: Hi, I should add that I tried to boot into runlevel 3 and it made no difference. How do I determine at what point it went to a black screen and just stopped booting? Can

  1   2   3   4   5   6   7   8   >