You are not logged in.
Hi
I tried to initial RAM disk with and got error message
[root@archiso /]# mkinitcpio -p linux
==> ERROR; Preset not found: '/etc/mkinitcpio.d/linux.preset'
And I found some answers but one said
ALARM doesn't use an uInitrd.
and another said I have to be install kernel26.
How I can solve this?
Last edited by rob111 (2013-08-31 17:41:46)
Offline
Are you using the default kernel? If not, the preset is probably named something else.
Offline
ALARM = Arch Linux ARM.
Are you using ARM hardware? If so, please ask on their forum http://archlinuxarm.org/forum/
Are you using the default kernel? If not, the preset is probably named something else.
He's using archiso, so I'm not sure if this is the problem.
Last edited by karol (2013-08-25 21:30:24)
Offline
How I can know what kind of kernel I use?
And also I don't know I am using ARM or not. How I can check this?
Thanks
Offline
Have you run 'arch-chroot /mnt'?
https://wiki.archlinux.org/index.php/In … the_system
Offline
Scimmia wrote:Are you using the default kernel? If not, the preset is probably named something else.
He's using archiso, so I'm not sure if this is the problem.
Good catch, I missed that.
rob111, tell us what you're trying to do. Are you trying to update the initrd of the live system or of an installed system?
Offline
rob111, this sounds just like your other thread which you marked as solved ... though I don't know why you think it is solved. It sounds like the base and base-devel installation didn't complete properly and you should not try to work your way around that, you should go back and fix it. You only have a partially installed system.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Are you trying to update the initrd of the live system or of an installed system?
Good question: https://bbs.archlinux.org/viewtopic.php … 4#p1316854
Offline
rob111, this sounds just like your other thread which you marked as solved ... though I don't know why you think it is solved. It sounds like the base and base-devel installation didn't complete properly and you should not try to work your way around that, you should go back and fix it. You only have a partially installed system.
Trilby
How I can go back and fix that?
I can switch between [root@archiso /] and root@archiso ~ #.
I am doing now this step https://wiki.archlinux.org/index.php/Installation_Guide#Configure_the_system
Which step did I skip?
Thanks
Offline
Scimmia wrote:Are you trying to update the initrd of the live system or of an installed system?
Good question: https://bbs.archlinux.org/viewtopic.php … 4#p1316854
I am installing system on my laptop.
Offline
Run the commands outlined in https://wiki.archlinux.org/index.php/In … the_system
When you run 'arch-chroot /mnt' the prompt should change a bit and you should be able to run all subsequent commands, including 'mkinitcpio -p linux'.
Offline
How I can go back and fix that?
I can switch between [root@archiso /] and root@archiso ~ #.
I don't know which one of those is which. I don't suspect you skipped a step, but I do suspect that the `pacstrap /mnt/ base base-devel` command did not complerte successfully.
If you are in the live system (what the live usb first boots into), then you can just rerun that command and make sure there are no error messages.
If you are chrooted into your new system, you *should* be able to just do `pacman -Syu base base-devel`, but depending on what went wrong the first time, this may or may not work.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I can switch between [root@archiso /] and root@archiso ~ #.
This is confusing given this report. Could you confirm exactly the prompt you have when you try to run the configuration commands such as mkinitcpio -p linux.
Because, as Trilby says, if you really have successfully installed base and base-devel and chrooted into the system, you should not be seeing these errors. Also, I am pretty sure that you should not have needed to verify the master key manually. When Arch first introduced signing, manual verification of keys was required but I am almost certain that is no longer the case. So something is almost certainly wrong at an earlier stage and you need to fix that, as Trilby says, before moving onto the next stage.
EDIT: "As Trilby says" should now read "as Trilby says again" - I'm too slow.
Last edited by cfr (2013-08-25 22:57:40)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
"As Trilby says" ... "as Trilby says again"
The first two installments of the made-for-tv drama of one linux user out to save the world one installation at a time.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline