Em agosto 22, 2019 17:15 Damjan Georgievski via arch-general escreveu:
Just in case, I'll mention kernel-install [1] once again, it's a nice
central hub where initramfs creators, bootloaders (and optionally signing
of uefi images) can hook into, and then any kernel install can call all the
users
On 8/22/19 3:36 PM, Giancarlo Razzolini via arch-general wrote:
> Em agosto 22, 2019 16:29 Damjan Georgievski via arch-general escreveu:
...
>
> On the other hand, I have been using dracut for months now without any
> issues.
>
> Regards,
> Giancarlo Razzolini
I too have been using it for months
On Thu, 22 Aug 2019 at 21:36, Giancarlo Razzolini
wrote:
> Em agosto 22, 2019 16:29 Damjan Georgievski via arch-general escreveu:
> > Are there any news/updates on this front?
> >
> > I have dracut installed in one test VM, but I have to run it manually
> after
> > each kernel update. The wiki pa
Em agosto 22, 2019 16:29 Damjan Georgievski via arch-general escreveu:
Are there any news/updates on this front?
I have dracut installed in one test VM, but I have to run it manually after
each kernel update. The wiki page [1] is still empty, so
how do I configure proper hooks to build the initr
I have been looking into dracut for some time now, I copied some stuff from
> them on a few of my own
> scripts and they also have an actual test suite, that we currently can't
> use on Arch, but I plan to
> change that.
>
>
Are there any news/updates on this front?
I have dracut installed in one
On 6/15/19 5:12 PM, Genes Lists via arch-general wrote:
...
>
> I need to do more work ... perhaps test with the --madadmconf flag when
> building the initrd is next step.
>
I confirm that building the initrd with --mdadmconf fixes the problem
assembling the raid disks using dracut - this happen
I now understand why this works with mkinitrd - it's because this
approach does not assemble the array until -after- the pivot root - and
the hostname is now the real hostname and this matches what's in the
raid superblock.
dracut attempts to assemble the array(s) before - in this case the
hostnam
On 2019-06-11 18:02, Damjan Georgievski via arch-general wrote:
> Is there any support for post hooks in Dracut?
>
> ie. I want to sign the uefi image with sbsign, after it's built with
> `dracut --uefi …`
>
That would be cool, but dracut doesn't have this capability built in,
see the last few
>
> I have been looking into dracut for some time now, I copied some stuff
> from them on a few of my own
> scripts and they also have an actual test suite, that we currently can't
> use on Arch, but I plan to
> change that.
>
Is there any support for post hooks in Dracut?
ie. I want to sign the
> Giancarlo Razzolini
Found this (very) old thread [1] - and tried the suggesion - removed
name= from mdadm.conf, rebuilt the initrd and rebooted but had same
problem. Booted from mkinitrd and still works. May be i need to learn
more about raid
Will need to get back to this.
[1] https://ubunt
Em junho 4, 2019 18:08 Genes Lists via arch-general escreveu:
On 6/4/19 4:53 PM, Genes Lists via arch-general wrote:
Forgot to post the boot the boot log which shows the problem occurs
after switching the pivot root:
...
saplinux kernel: md/raid:md127: raid level 6 active with 6 out of 6
devic
>
Speculation - this may be related to the kernel config which has
CONFIG_DEFAULT_HOSTNAME="archlinux"
for arch kernels and i use a different name (saplinux)
In either case, in the boot logs the hostame shown before the pivot root
is that default as compiled into thekernel - but after the switc
On 6/4/19 4:53 PM, Genes Lists via arch-general wrote:
Forgot to post the boot the boot log which shows the problem occurs
after switching the pivot root:
...
saplinux kernel: md/raid:md127: raid level 6 active with 6 out of 6
devices, algorithm 2
saplinux kernel: md127: detected capacity change
On 6/4/19 12:07 PM, Genes Lists via arch-general wrote:
> FYI - I have switched my custom kernel builds to use dracut by default
Ug take it back - i have one problem - a big problem.
On a computer using md RAID-6 the raid disks are not assembled at boot -
and the boot fails. Works fine switching
FYI - I have switched my custom kernel builds to use dracut by default
now - tested on 8 machines with no issues. Very supportive of switching
to dracut.
thank you.
gene
Em maio 29, 2019 18:49 Michael Lojkovic via arch-general escreveu:
Should this work with a minimal initramfs, without udev? I don't know
how to transfer the mkinitcpio config to dracut to test this properly.
It would help if you upload your current config/preset somewhere. I'm not
sure anyth
Should this work with a minimal initramfs, without udev? I don't know
how to transfer the mkinitcpio config to dracut to test this properly.
On 5/27/19 2:07 PM, Genes Lists via arch-general wrote:
Likely the same issue
https://lkml.org/lkml/2019/5/28/812
Thanks,
gene
On 5/27/19 2:07 PM, Genes Lists via arch-general wrote:
> Hi
>
> I've come across a possible issue which related to usb keyboard/mouse
> device.
>
>
Quick follow up. I have this issue on 2 machines I've tested.
(i) vendor_id : GenuineIntel
cpu family : 6
model : 78
model na
On 5/27/19 6:10 AM, Joerg Schilling wrote:
> Eli Schwartz via arch-general wrote:
>
>> I think Chet Ramey did a pretty good explanation in the linked mailing
>> list about why this is a fundamental misunderstanding of what "POSIX"
>> means, but just to be extra sure... you are aware that POSIX de
Hi
I've come across a possible issue which related to usb keyboard/mouse
device.
I notice that booting using dracut initramfs with kernel 5.2-rc2 that as
soon as it boots it shows on the console: stopping job udev Kernel
Device Manager with red spinner.
This times out and boot continues fine - o
Em maio 27, 2019 13:45 Damjan Georgievski escreveu:
Thanks,
I've also noticed another issue about the uefi stub and sent a PR:
https://github.com/dracutdevs/dracut/pull/575
Thank you all for testing and also submitting patches to make it work better
not just on Arch, but any other distro too.
> > dracut 049-3 on an Arch [testing] VM
> >
>
> There are a few more instances where arch must be replaced with uname -m.
>
> I'll deploy a version of dracut with that patch later:
>
> https://github.com/dracutdevs/dracut/pull/573
>
Thanks,
I've also noticed another issue about the uefi stub and
Em maio 27, 2019 11:18 Damjan Georgievski via arch-general escreveu:
dracut --uefi
This seems to fail for me:
$ sudo dracut --no-early-microcode --uefi /boot/EFI/Linux/arch-linux.efi
dracut: Executing: /usr/bin/dracut --no-early-microcode --uefi
/boot/EFI/Linux/arch-linux.efi
/usr/bin/dracu
On 2019-05-27 16:18, Damjan Georgievski via arch-general wrote:> This
seems to fail for me:
> $ sudo dracut --no-early-microcode --uefi /boot/EFI/Linux/arch-linux.efi
> dracut: Executing: /usr/bin/dracut --no-early-microcode --uefi
> /boot/EFI/Linux/arch-linux.efi
> /usr/bin/dracut: line 1063: arch
>
>
> dracut --uefi
>
This seems to fail for me:
$ sudo dracut --no-early-microcode --uefi /boot/EFI/Linux/arch-linux.efi
dracut: Executing: /usr/bin/dracut --no-early-microcode --uefi
/boot/EFI/Linux/arch-linux.efi
/usr/bin/dracut: line 1063: arch: command not found
/usr/bin/dracut: line 1069: a
Eli Schwartz via arch-general wrote:
> I think Chet Ramey did a pretty good explanation in the linked mailing
> list about why this is a fundamental misunderstanding of what "POSIX"
> means, but just to be extra sure... you are aware that POSIX defines
> `command ^` as the only true, correct POSI
Neven Sajko via arch-general wrote:
> Regarding using bash as sh:
>
> > Bash runs POSIX scripts just fine.
>
> Bash does not run some POSIX scripts fine. See
> https://lists.gnu.org/archive/html/bug-bash/2017-08/msg00087.html ,
> for example. In that case an executable named ^ can not be called.
Em maio 26, 2019 0:08 Eli Schwartz via arch-general escreveu:
Anyway I suspect this thread is not the best place to begin a
fundamental discussion about whether GNU bash is allowed to claim it
implements POSIX. Also I doubt dracut does insane things like attempt to
invoke a utility named "^", wi
On 5/25/19 1:54 AM, Neven Sajko via arch-general wrote:
> Regarding using bash as sh:
>
>> Bash runs POSIX scripts just fine.
>
> Bash does not run some POSIX scripts fine. See
> https://lists.gnu.org/archive/html/bug-bash/2017-08/msg00087.html ,
> for example. In that case an executable named ^
On Sat, 25 May 2019 05:54:23 +, Neven Sajko via arch-general wrote:
>Regarding using bash as sh:
>
>> Bash runs POSIX scripts just fine.
>
>Bash does not run some POSIX scripts fine. See
>https://lists.gnu.org/archive/html/bug-bash/2017-08/msg00087.html ,
>for example. In that case an executa
On 05/22/2019 11:41 AM, Eli Schwartz via arch-general wrote:
> I would rather avoid such bundles at all costs, it sounds like someone
> saw a problem named bootctl and decided to create even more problems in
> the name of a solution.
I've always respected the Arch KISS approach. The further we sta
Regarding using bash as sh:
> Bash runs POSIX scripts just fine.
Bash does not run some POSIX scripts fine. See
https://lists.gnu.org/archive/html/bug-bash/2017-08/msg00087.html ,
for example. In that case an executable named ^ can not be called.
On 5/21/19 12:24 PM, Genes Lists via arch-general wrote:
> 1) Feedback:
> Tested one computer and it worked fine.
Working fine on a couple more I tested.
Also for my custome kernel builds, I added a libalpm hook to create the
dracut initrd - makes it easier for me to test.
Thank you for doing th
On 2019-05-22 18:41, Eli Schwartz via arch-general wrote:
> True, but on the other hand bootctl sucks and you can implement a 2MB
> efi partition that works everywhere and supports a single unified
> kernel/microcode/initramfs setup stored on an ext4/btrfs/whatever /boot
> subdirectory inside your
On 5/22/19 12:22 PM, Jonas Witschel wrote:
> On 2019-05-22 17:25, Giancarlo Razzolini via arch-general wrote:
>>> Unfortunately this process currently only works for AMD, but not for
>>> Intel, since Arch Linux doesn't package the necessary files standalone:
>>> they are downloaded by intel-ucode a
On 2019-05-22 17:25, Giancarlo Razzolini via arch-general wrote:
>> Unfortunately this process currently only works for AMD, but not for
>> Intel, since Arch Linux doesn't package the necessary files standalone:
>> they are downloaded by intel-ucode and used to produce a CPIO image, but
>> not adde
Em maio 22, 2019 9:25 Jonas Witschel escreveu:
On 2019-05-22 14:00, Giovanni Harting via arch-general wrote:
Unfortunately this process currently only works for AMD, but not for
Intel, since Arch Linux doesn't package the necessary files standalone:
they are downloaded by intel-ucode and used to
On 2019-05-22 14:00, Giovanni Harting via arch-general wrote:
> AMD's microcode is in linux-firmware: /usr/lib/firmware/amd-ucode/
Dracut indeed looks in /usr/lib/firmware/{amd,intel}-ucode/ for
microcode updates to include in the initramfs. When using a host-only
initramfs, only the relevant file
On 21/05/2019 20:55, Genes Lists via arch-general wrote:
Funnily enough, while I do have intel-ucode package installed I don't
have amd-ucode. The dracut script seems to have found it somewhere I
suppose - not sure where yet.
AMD's microcode is in linux-firmware: /usr/lib/firmware/amd-ucode/
Hi,
> This output is a json file, so I'm not sure what you're outputting there.
>
Something was wrong with the pastebin-service, I pasted it again:
http://sprunge.us/3rXzR4
root is an XFS on an encrypted luks device.
BR
Bjoern
signature.asc
Description: OpenPGP digital signature
Em maio 21, 2019 17:29 Bjoern Franke via arch-general escreveu:
Just dracut -f /boot/initramfs-linux.img. It is that simple.
Tried it, the output looked fine:
https://p.rrbone.net/paste/FV7HMpE7#
But while booting dracut hang on "initqueue hooks"
This output is a json file, so I'm not su
> Just dracut -f /boot/initramfs-linux.img. It is that simple.
Tried it, the output looked fine:
https://p.rrbone.net/paste/FV7HMpE7#
But while booting dracut hang on "initqueue hooks"
Thanks for your efforts,
Bjoern
signature.asc
Description: OpenPGP digital signature
On 5/21/19 1:21 PM, Giancarlo Razzolini wrote:
>> Got text prompt for passphrase not graphical - think there is a way to
>> get graphical as well but need to read further how to do that. I prefer
>> text as I also can see the boot progress details which is helpful.
>> Still, be good to know how to
On 5/21/19 2:48 PM, Giancarlo Razzolini wrote:
> Em maio 21, 2019 15:42 Genes Lists via arch-general escreveu:
...
>
> Loading the microcode before will probably always work and should
> continue to be the desirable solution.
..
Funnily enough, while I do have intel-ucode package installed I don'
W dniu 21.05.2019 o 20:48, Giancarlo Razzolini via arch-general pisze:
> Em maio 21, 2019 15:42 Genes Lists via arch-general escreveu:
>> Early Microcode and initrd.
>>
>> I notice that the AMD microcode is [1] in the initrd while the intel
>> microcode is not.
>>
>> Booting with option:
>> initr
Em maio 21, 2019 15:42 Genes Lists via arch-general escreveu:
Early Microcode and initrd.
I notice that the AMD microcode is [1] in the initrd while the intel
microcode is not.
Booting with option:
initrd=/boot/intel-ucode.img
to get the microcode installed early works fine with dracut as it al
Early Microcode and initrd.
I notice that the AMD microcode is [1] in the initrd while the intel
microcode is not.
Booting with option:
initrd=/boot/intel-ucode.img
to get the microcode installed early works fine with dracut as it always
has.
Is this something that will remain the same as now or
Em maio 21, 2019 15:15 Andy Pieters escreveu:
What's the rationale for going dracut? I'm quite happy with mkinitcpio
I think I've addressed this in the first email. I'm also quite happy with
mkinitcpio,
and I myself maintain several mkinitcpio hooks that would need to be re-written
for dracu
On 05/21/2019 12:06 PM, Giancarlo Razzolini via arch-general wrote:
> I'll stress this, dracut and mkinitcpio will co-exist for a *long* time. So,
> each will have their own hooks for updating the images.
>
Thank you. mkinitcpio isn't broken and using both SuSE with dracut and Arch
with mkinitcpi
What's the rationale for going dracut? I'm quite happy with mkinitcpio
Em maio 21, 2019 13:24 Genes Lists via arch-general escreveu:
1) Feedback:
Tested one computer and it worked fine.
Used refind to boot - it has encrytped /home but not root.
Got text prompt for passphrase not graphical - think there is a way to
get graphical as well but need to read further how t
Em maio 21, 2019 12:21 Lone_Wolf escreveu:
from https://dracut.wiki.kernel.org/index.php/Main_Page :
* Scripts that end up on the initrd should be POSIX compliant. dracut
will try to use /bin/dash as /bin/sh for the initrd if it is
available, so you should install it on your system
Em maio 21, 2019 11:26 Genes Lists via arch-general escreveu:
...
I'm an arch tester and I'd be happy to test dracut.
It would be helpful if you could create a little write-up on 'how to
switch' from mkinitcpio to dracut.
Just run dracut =D. But seriously, I'll work on a wiki page about this.
On 5/21/19 12:41 PM, Doug Newgard via arch-general wrote:
>
>
> Since ln won't work on vfat, that's not really an option for a lot of people.
>
Ah thanks and good point.
While it would actualy work with refind ( as the images are on ext4
/boot partition and only the refind efi images sit in the
On Tue, 21 May 2019 18:28:50 +0200
Damjan Georgievski via arch-general wrote:
> > 2) Question:
> >Arch typically has used unversioned initrd images which has the
> >convenience that the boot standzas don't need updating on new kernel.
> >
>
> This can (also) be fixed if Arch implements
On Tue, 21 May 2019 12:24:09 -0400
Genes Lists via arch-general wrote:
> 1) Feedback:
> Tested one computer and it worked fine.
> Used refind to boot - it has encrytped /home but not root.
> Got text prompt for passphrase not graphical - think there is a way to
> get graphical as well but need to
> 2) Question:
>Arch typically has used unversioned initrd images which has the
>convenience that the boot standzas don't need updating on new kernel.
>
This can (also) be fixed if Arch implements the `kerne-install` [1]
mechanism to update the boot-loader stanzas.
[1]
https://www.freede
1) Feedback:
Tested one computer and it worked fine.
Used refind to boot - it has encrytped /home but not root.
Got text prompt for passphrase not graphical - think there is a way to
get graphical as well but need to read further how to do that. I prefer
text as I also can see the boot progress det
On 5/21/19 11:21 AM, Lone_Wolf wrote:
>
> On 21-05-2019 16:26, Genes Lists via arch-general wrote:
>> On 5/20/19 10:41 PM, Giancarlo Razzolini via arch-dev-public wrote:
>>> Hi All,
>>>
>> ...
>>> In this initial phase I want to ask as many of you to test this as a
>>> replacement to mkinitcpio in
On Tue, 21 May 2019 17:21:31 +0200
Lone_Wolf wrote:
> Seems like having dracut depending on bash may not be a good idea.
>
> Or is there a way to make sure dracut scripts & hooks will use bash in
> POSIX-compliant mode ?
>
> LW
Bash runs POSIX scripts just fine. No need to do anything.
On 21-05-2019 16:26, Genes Lists via arch-general wrote:
On 5/20/19 10:41 PM, Giancarlo Razzolini via arch-dev-public wrote:
Hi All,
...
In this initial phase I want to ask as many of you to test this as a
replacement to mkinitcpio in your setups,
as many as possible, and in as many scenari
On 5/20/19 10:41 PM, Giancarlo Razzolini via arch-dev-public wrote:
> Hi All,
>
...
>
> In this initial phase I want to ask as many of you to test this as a
> replacement to mkinitcpio in your setups,
> as many as possible, and in as many scenarios as possible. We will
...
I'm an arch tester an
63 matches
Mail list logo
