tandalone, so user direct modification is not proscribed like it is
for grub.cfg.
So if you want to modify one menu entry, you can modify the BLS snippet. If
you want to modify all, and newly added menu entries, /etc/default/grub is
what you should update.
--
Chr
roups? They can have different block sizes and
redundancy profiles, e.g. by default 16KiB block size for metadata,
4KiB for data. And by default hard drives have dup metadata, single
data; and 2+ device file systems will get raid1 for metadata and
single for data. Bu
i.e. no checksumming for data, and no compression.
Also, btrfs metadata (the file system itself) is always cow. It can't
be disabled.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists
On Tue, Dec 8, 2020 at 5:53 AM Sreyan Chakravarty wrote:
>
> On Mon, Dec 7, 2020 at 3:43 PM Chris Murphy wrote:
>>
>>
>> This isn't a great location for a swapfile on btrfs because you can't ever
>> snapshot /.
>
>
> You never said why it was not possi
our
expectations (b) how to maintain and manage it, in particular disaster
recovery. Because that too is different.
[1]
https://github.com/kdave/btrfs-progs/issues/277
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
d off a mandb process. Problem fixed. On the second machine I found a
mandb rebuild service unit (I can't remember the exact name and I'm mobile
at the moment) and just did 'sudo systemctl start mandbwhatever.service'
and that also fixed it.
What I don't know is why it broke in the first pla
https://bugs.kde.org/show_bug.cgi?id=427092
--- Comment #9 from Chris Murphy ---
Created attachment 133926
--> https://bugs.kde.org/attachment.cgi?id=133926=edit
udisksctl dump
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427092
--- Comment #8 from Chris Murphy ---
Created attachment 133925
--> https://bugs.kde.org/attachment.cgi?id=133925=edit
solid-hardware5 list
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427092
--- Comment #7 from Chris Murphy ---
(The originally reported test setup is gone (it's a VM), so I have another
setup based on Fedora-KDE-Live-x86_64-Rawhide-20201206.n.1.iso and a 2x btrfs
raid1.)
$ ls -l /dev/disk/by-label/
total 0
lrwxrwxrwx. 1
e show?
This isn't a great location for a swapfile on btrfs because you can't ever
snapshot /. And it takes extra steps to make hibernation possible.
The more predictable arrangement is a swap partition.
--
Chris Murphy
___
users mailing list -- u
of use cases run at
1:1 zram to RAM, and upstream considers 2:1 reasonable due to the
compression ratio. I think in Fedora land that's too aggressive for
making it the default behavior, but on a case by case basis it's
reasonable not least of which is that it's easy for users to fiddle
with it, if they w
s the user, it's not confusing Btrfs or data on the file
system.
https://gitlab.gnome.org/GNOME/gvfs/-/issues/519
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
l
mounted file system path. A user can of course always mount the
top-level of the file system and see all such subvolumes.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...
g-mergerfs-to-increase-your-virtual-storage/
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-
with while in
transit.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
L
above fails with :
> -bash: echo: write error: No such device
>
What do you get for 'swapon' ?
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fed
On Sat, Dec 5, 2020 at 10:03 PM Tim via users
wrote:
>
> On Sat, 2020-12-05 at 17:45 -0700, Chris Murphy wrote:
> > There definitely is no free lunch with swap-on-zram, but it helps
> > quite a lot for most workloads.
>
> I'm curious how dedicating some of your RAM fo
ra-workstation/blob/master/f/hibernationstatus.md
That doc goes into the details of why hibernation is difficult to
support, and won't limit future decisions for Fedora.
--
Chris Murphy
___
users mailing list -- users@lists.fedorapro
that? There isn't even a mention of
b43-fwcutter on this page.
Thanks,
--
Chris Murphy
___
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev
On Wed, Dec 2, 2020 at 1:51 PM Fulko Hew wrote:
>
>
>
> On Wed, Dec 2, 2020, 12:57 Chris Murphy, wrote:
>>
>> On Wed, Dec 2, 2020 at 9:39 AM Fulko Hew wrote:
>> >
>> > It's been a bad week for me.
>> > First my disk drive died, and now I
t test is to disable
thermald and see if the same behavior still happens. If that fixes the
problem, I suggest a thermald bug report. If it doesn't fix the
problem, then we need to look at a possible kernel regression.
There are some user space tools that can directly manipulate fans i
On Tue, Dec 1, 2020 at 1:38 PM Tom Horsley wrote:
>
> On Tue, 1 Dec 2020 13:33:22 -0700
> Chris Murphy wrote:
>
> > Yep. For sure the kernel is what's responsible for reading the
> > partition table. And that alone would cause a spin up. e.g.
>
> But why would it ne
old and brave, you can
even build bees and dedup. I expect a significant ability to dedup the
same version OS because the binaries will be identical. That is,
Workstation 33 and KDE 33 will share a lot of the same binaries. Same
for Workstation 33 and Silverblue 33. You could have a very lo
On Tue, Dec 1, 2020 at 1:07 PM Samuel Sieb wrote:
>
> On 12/1/20 8:42 AM, Patrick O'Callaghan wrote:
> > On Tue, 2020-12-01 at 09:01 -0700, Chris Murphy wrote:
> >> On Tue, Dec 1, 2020 at 6:59 AM Tom Horsley wrote:
> >>>
> >>> On Tue, 1 Dec 2
On Tue, Dec 1, 2020 at 9:42 AM Patrick O'Callaghan
wrote:
>
> On Tue, 2020-12-01 at 09:01 -0700, Chris Murphy wrote:
> > On Tue, Dec 1, 2020 at 6:59 AM Tom Horsley wrote:
> > >
> > > On Tue, 1 Dec 2020 14:52:21 +0100
> > > Roberto Ragusa wrote:
&
udev/rules.d/69-hdparm.rules
ACTION=="add", SUBSYSTEM=="block", \
KERNEL=="sd*[!0-9]", \
ENV{ID_SERIAL_SHORT}=="WDZ47F0A", \
RUN+="/usr/sbin/hdparm -B 100 -S 252 /dev/disk/by-id/wwn-0x5000c500a93cae8a"
$
--
Chris Murphy
_
o know what everything is.
The only way it can know what it is, it needs to be spun up to read
the partition map and all the signatures on each partition.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email
On Tue, Dec 1, 2020 at 2:06 AM Sreyan Chakravarty wrote:
>
>
>
> On Mon, Nov 30, 2020 at 10:12 PM Chris Murphy wrote:
>>
>>
>> I don't understand why you're going to another forum to ask the same
>> question, and posting different information. It's just ma
ong?
Fedora users BootLoaderSpec snippets found in /boot/loader/entries -
if the associated snippet for the deleted kernel isn't being deleted
then there's a bug somewhere. It's not one I've come across though.
--
Chris Murphy
___
users mailing list -- u
g convention would be more flexible and self-describing. But
either of these requires a design, and (ideally) expand the spec to
cover this case.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
On Mon, Nov 30, 2020 at 2:19 AM Sreyan Chakravarty wrote:
>
>
>
> On Mon, Nov 30, 2020 at 2:38 AM Chris Murphy wrote:
>>
>>
>> It does. You can check with any or all of these commands:
>>
>> mount | grep btrfs
>> sudo btrfs subvolume list
On Sun, Nov 29, 2020 at 10:37 PM Sreyan Chakravarty wrote:
>
>
>
> On Mon, Nov 30, 2020 at 2:38 AM Chris Murphy wrote:
>>
>>
>> There's a lot more than one way to do this. As one possible example:
>>
>> $ sudo mount /dev/nvme0n1p7 /mnt
>> $ cd
On Sat, Nov 28, 2020 at 11:57 PM Sreyan Chakravarty wrote:
>
>
>
> On Sun, Nov 29, 2020 at 5:43 AM Chris Murphy wrote:
>>
>>
>> It's possibly stale information, back from when the installer first
>> added support for LVM thinp. I forget if it was someone on
On Sat, Nov 28, 2020 at 10:25 PM Samuel Sieb wrote:
>
> On 11/28/20 4:13 PM, Chris Murphy wrote:
> > On Fri, Nov 27, 2020 at 10:54 PM Sreyan Chakravarty
> > wrote:
> >
> >> Where exactly are you getting this from ?
> >>
> >> I have been using s
provisioning"
But I don't see that thread at:
https://www.redhat.com/archives/lvm-devel/2020-November/thread.html
Also, I have a reply on that thread from Danti Gionatan. That too is
not listed at redhat.com but is on lore. And it also came to me by
email directly from him, not from the list ser
ng about the "default subvolume". And to give a complete answer
is a bit of a story. But you can get the gist from 'man btrfs
subvolume' and read the set-default and get-default sections in
particular.
[1] Nested versus flat layouts. The above example is a flat layou
the LE to PE mapping, and it
should work. But does it work for both paging and hibernation files?
And what's the implication if the thin volume were to be snapshot?
Thanks,
--
Chris Murphy
___
linux-lvm mailing list
linux-lvm@redhat.com
https
port for LVM thinp. I forget if it was someone on the
installer or LVM team, but I can't find any reference. The installer,
to this day, creates swap on a conventional "thick" provisioned LV,
even when choosing the LVM thinp layout.
--
Chris Murphy
___
please install recommended
> missing binary /usr/sbin/thin_check!
>
>
> In short my system has gone to hell.
>
> This all started when I did a fstrim like this:
>
> sudo fstrim -v /
Without complete start to finish logs, showing the first instance of
problems, it's not much t
system-upgrade fails when openssh-ldap is installed
https://bugzilla.redhat.com/show_bug.cgi?id=1902084
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
ed. So you can just remove it.
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/XHPP2WBHZCOUO2LQ5D3MH76JQCGG562G/
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-
in volumes, it will return no longer used blocks back to the
thin pool.
Once per week is enough for most workloads.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
F
doesn't look like it does that. So I'm not sure.
And of course file copy tools are OK as well, though they sometimes
come with the burden/risk of many extra options.
---
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe
My experience is LVM thick (traditional) snapshots are slow. Where LVM thin
provisioning snapshots address quite allot faster.
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le
On Mon, Nov 16, 2020 at 12:30 PM Kamil Paral wrote:
> On Thu, Nov 12, 2020 at 9:25 PM Chris Murphy wrote:
>>
>> I often had to click the 'how to vote' link in a separate tab to copy/paste
>> the proper tag. It'd be nice if the list of possible voting tags is si
On Mon, Nov 16, 2020 at 1:39 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Sun, Nov 15, 2020 at 04:28:36PM -0700, Chris Murphy wrote:
> > On Sun, Nov 15, 2020 at 4:12 AM Zbigniew Jędrzejewski-Szmek
> > wrote:
> > >
> > > On Wed, Nov 04, 2020 at 01:12:44PM -05
are some
opportunities for it to fail.
There's a bunch of tests to do to help narrow down the problem.
https://www.kernel.org/doc/html/latest/power/basic-pm-debugging.html
Note that swapfiles on Btrfs additionally need an offset boot parameter added.
https://bugzilla.kernel.org/show_bug.cgi?id=20
layer and for me
> that command did nothing, whereas it worked fine in F32.
What do you get for
grub2-editenv list
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedora
om write the ESP after
> installation except for /boot/efi/EFI/fedora/grubenv after updates (or
> perhaps shim updates) but I'm wondering...
Yeah I don't think you need to consider it too much.
--
Chris Murphy
___
users mailing list -- users@
an fstab entry
using a path from /stratis, and also doesn't include the nofail or
noauto mount options, boot can fail waiting indefinitely on a file
system that won't ever appear
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscr
;
> Here is the message:
>
> SELinux is preventing systemd-logind from read access on the file
> /fedora.swap.
mkswap sets the label. So this is a secondary effect of what Sam Sieb
already discovered from the lack of a blkid swap signature. You forgot
ready in libblockdev.
But it's missing a minimum size check. That issue is referenced in the
fedora-btrfs#35 issue. I'm not sure where it belongs, but there
probably needs to be a check for number of devices and only support
shrink on single device Btrfs.
--
Chris Murphy
___
in
> their integration with Blockerbugs and Bugzilla websites?
>
+1 to what Adam already mentioned.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of C
do a partial recovery
of the files on the surviving drive. Most likely this is a big mess
but some folks might find it useful.
Another way to do this is just select the two drives, and do an
automatic installation. And then convert to raid0 after installation
and reboot.
btrfs
with a custom zram-generator.conf and xhange
the limit to 16G. You'll get an 8G zram device in this case, if you make no
other changes to the configuration.
I'm curious at what minimum zram allocation this problem doesn't happen.
6G, 8G, 10G?
--
Chris Murphy
___
m to 75% ram.
While 100% is normally OK, it might be a use case better off with disk
based swap. It just depends on the workload.
Most users should be ok with the defaults. It's what I'm using most of the
time for over one year now. But I'm always on the l
self), i.e.
mkfs.btrfs -mraid1 -draid5
Or
mkfs.btrfs -mraid1c3 -draid6
But yeah, raid is not a backup
---
Chris Murphy
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora C
I thought it was just something wrong with my
> browser.
Is it broken for 32 and 31? Our just 33?
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora C
e of BPF perf tools
http://www.brendangregg.com/blog/2020-11-04/bpf-co-re-btf-libbpf.html
Fedora does have CONFIG_DEBUG_INFO_BTF=y
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.or
EFI "enabled" and somehow Fedora got installed with a "Legacy BIOS"
mode enabled. In which case it's easier to just reinstall - don't
forget to backup /home though first.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproj
the data
itself is located. To say "metadata profile is raid1" means two copies
of the file system, meaning one device can file and the file system
itself is OK. Since there's only one copy of data, anything on a
failed drive is lost, so this is not likely a bootable system. But
f
ackups. So no matter how
badly I mess it up I know I'm not losing things I care about.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
h
chemes, same as in the GUI: Btrfs, LVM, LVM
Thin, Standard. But there's no other choices to customize these. You
pick the scheme and get that scheme's "automatic" partitioning. You do
get a choice whether to use only free space on the disk (default) or
erase it.
--
Chris Murphy
_
On Mon, Nov 2, 2020 at 2:14 PM Jorge Fábregas wrote:
>
> On 11/2/20 3:48 PM, Chris Murphy wrote:
> > Short version: If you want unattended degraded RAID boot, use mdadm
> > and put Btrfs on top of it.
>
> Hi Chris,
>
> I get it now. Thanks. I see it's not that
y device during boot means
an immediate degraded mount. And without a scrub to catch up the late
device, the mirrors can end up in kind of "split brain" situation, and
that's not recoverable or repairable.
--
Chris Murphy
___
users mailing list -- users@
On Mon, Nov 2, 2020 at 3:50 AM Patrick O'Callaghan
wrote:
>
> On Sun, 2020-11-01 at 19:00 -0700, Chris Murphy wrote:
> > On Sun, Nov 1, 2020 at 6:51 AM John Mellor wrote:
> > > On 2020-10-31 10:46 p.m., Tim via users wrote:
> > > > On Sat, 2020-10-31 at 16:1
On Sun, Nov 1, 2020 at 7:00 PM Chris Murphy wrote:
> ddrescue by default reads the whole file (via the mounted file system,
> not pointing it to raw sectors), but with truncated bad 4KiB blocks.
> The bad blocks are simply missing, there is no gap filled with zeros
> or some other pa
this most recent bad RAM one is
quite straightforward.
https://bugzilla.redhat.com/show_bug.cgi?id=1882875
What's noteworthy is Btrfs doesn't assign blame. It just states the
facts. It's up to us to figure out the puzzle, and it is a learnable
skill.
--
Chris Murphy
__
ttps://getfedora.org/en/security/
> >
>
> I'm guessing that those extra lines are data needed by a process that
> sha256sum calls (perhaps gpg), but sha256sum doesn't use them directly.
> Otherwise I have no idea what their purpose is.
Step 2 at the above URL: Now, verify that the CHECK
ferent kernel versions for different archs?
What about different media? Or do they all get the same kernel
version? Pretty sure it's the latter which makes this harder.
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send
On Mon, Oct 26, 2020 at 5:26 PM Chris Murphy wrote:
> If you want more granular settings, see 'btrfs property', which can be
> applied per subvolume, directory or per file. It is possible to
> specify an algorithm. But is not yet possible to specify level, set it
> recursively or u
it
recursively or unset it once set.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-o
arning experience for me. Fedora is my passion,
> From my studies, I may discover that you are absolutely right to state that I
> do not need to make the extra subvolumes.
> The advantage I have over you is my career. It is called "retirement".
> Ret
On Fri, Oct 23, 2020 at 8:33 AM Neal Gompa wrote:
>
> On Fri, Oct 23, 2020 at 1:39 AM Chris Murphy wrote:
> > I'm not sure it's possible (still) for UEFI and BIOS GRUB to co-exist
> > on one media, hence using isolinux to boot BIOS.
> Could we just drop syslinux/
On Fri, Oct 23, 2020 at 8:18 AM Chris Adams wrote:
>
> Once upon a time, Chris Murphy said:
> Although: now that I look at the ISO structure with isoinfo, it does
> appear that the files are not actually duplicated - they are pointing to
> the same sectors. Reading the genis
verything could be on the squashfs file and deduped.
I'm not sure it's possible (still) for UEFI and BIOS GRUB to co-exist
on one media, hence using isolinux to boot BIOS.
ISO 9660 doesn't support hardlinks or symlinks. UDF supports both. But
I think xorriso doesn't support UDF and also I
ng what problem you think you
might have, that you're trying to avoid.
> I tried to create the two subvars, without success. I even went so far as to
> examine the grub menu entries.
What did you try? How did it fail?
> Is this not possible with Fed33 beta?
Fedora
On Tue, Oct 13, 2020 at 7:38 PM Chris Murphy wrote:
>
> Hi,
>
> I'm looking for testers:
> - Fedora 33
> - User home is on Btrfs (clean installed or converted, in a subvolume
> or not, these details won't matter)
> - using any spin other than Workstation (kde, lxqt, xfce,
On Tue, Oct 13, 2020 at 7:38 PM Chris Murphy wrote:
>
> Note 2: It's decently likely you will get the expected results if
> /home is on XFS. Arguably if we get a result on Btrfs indicating
I got distracted, and didn't finish the thought before clicking send!
If the result on Btrf
Fedora 33 upgraded from F32, and clean install Fedora 33 (Workstation)
$ cat /proc/sys/kernel/printk
3417
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le
is on XFS. Arguably if we get a result on Btrfs indicating
--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US
On Mon, Oct 12, 2020 at 1:33 AM Lennart Poettering
wrote:
>
> On So, 11.10.20 14:57, Chris Murphy (li...@colorremedies.com) wrote:
>
> > Hi,
> >
> > A Fedora 32 (systemd-245.8-2.fc32) user has a 10-drive Btrfs raid1 set
> > to mount in /etc/fstab:
> >
>
On Sun, Oct 11, 2020 at 11:56 PM Andrei Borzenkov wrote:
>
> 11.10.2020 23:57, Chris Murphy пишет:
> > Hi,
> >
> > A Fedora 32 (systemd-245.8-2.fc32) user has a 10-drive Btrfs raid1 set
> > to mount in /etc/fstab:
> >
> > UUID=f89f0a16- /srv btrfs de
m) per the BootLoaderSpec's intention of sharing
/boot/loader/entries among the installed systems.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
to mount this file system at /srv
Anyway I'm mainly confused why the btrfs udev rule is seemingly not
applied in this case.
--
Chris Murphy
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo
ecified when creating a new partition, preventing specific use cases
(edit)
https://bugzilla.redhat.com/show_bug.cgi?id=1878620
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fe
in related bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1883609#c30
In this case you can replace it by just copying a substitute
grubx64.efi to the proper location on the USB stick... which might be
EFI/BOOT, I'd have to poke it with a stick to find out.
--
Chris Murphy
__
On Sun, Oct 4, 2020 at 10:50 AM Marius Schwarz wrote:
>
> Am 03.10.20 um 22:07 schrieb Chris Murphy:
> >
> > No the correct invocation is "dnf reinstall grub2-efi-x64 shim-x64"
> >
> > Suggesting UEFI users install GRUB with grub2-install is asking for
urn hasn't
changed in 12 months, so yeah that leaves grub.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject
rubx64.efi expects to find the grub.cfg in
/boot/grub2/grub.cfg. This OSLoader is not signed.
The grub2-efi-x64-2.04-31.fc33.x86_64 based grubx64.efi expects to
find the grub.cfg on the EFI system partition inside EFI/fedora/ and
this OSLoader is signed.
Basically you've stepped thro
t work with
UEFI Secure Boot enabled unless manually signed by the user, and it
has different behavior from the Fedora created one: where it expects
to find modules and the grub.cfg.
> But the correct invocation for EFI systems is different. You just use
> "grub2-install" without the disk d
t it to compare.
Further, Server installations benefit from RPM's using zstd
compression, whereas Workstation installs use xz compression with a
correspondingly higher CPU hit.
--
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsu
https://bugs.kde.org/show_bug.cgi?id=425040
Chris Murphy changed:
What|Removed |Added
CC||bugzi...@colorremedies.com
--- Comment #7 from
On Wed, Sep 30, 2020 at 4:22 PM Marius Schwarz wrote:
>
> Am 01.10.20 um 00:02 schrieb Chris Murphy:
>
> I made some more tests. It's a race, 1 out of 10 tries succeeds and the
> chance that it does is improoved by inserting the usb drive while being
> in the bios.
>
&
On Wed, Sep 30, 2020 at 3:42 PM Marius Schwarz wrote:
>
> Am 30.09.20 um 23:00 schrieb Chris Murphy:
> >
> >
> > And then these are current
> > grub2-efi-x64-2.04-31.fc33.x86_64
> > grub2-efi-x64-2.04-23.fc32.x86_64
> > grub2-efi-x64-2.02-110.fc31.x86_64
On Wed, Sep 30, 2020 at 10:46 AM Stephen John Smoogen
wrote:
>
> The Fedora secure boot signing keys were updated after F32 was initially
released to deal with the grub2 problems found during the summer. I believe
some systems have needed firmware updates from the manufacturer to work
with the
o idea what the LiveCD component is, but the bug report
contains so little information I also don't know what I'd reassign it
to. Asking about it on devel is probably the right thing to do for
now.
--
Chris Murphy
___
devel mailing list -- devel@lists.
https://bugs.kde.org/show_bug.cgi?id=427092
Chris Murphy changed:
What|Removed |Added
Summary|dolphin mishandles a btrfs |btrfs multiple device
|file
https://bugs.kde.org/show_bug.cgi?id=427092
--- Comment #5 from Chris Murphy ---
udisks2-2.9.1-1.fc33.x86_64
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427092
--- Comment #4 from Chris Murphy ---
kernel 5.8.11-300.fc33.x86_64
--
You are receiving this mail because:
You are watching all bug changes.
801 - 900 of 8361 matches
Mail list logo
