Sorry!
]]>New topic for new iso at https://bbs.archlinux.org/viewtopic.php?id=130747. This topic needs to be closed.
I think bernarcher just closed the wrong topic.
]]>Also the guide on how to create own image files seems outdated? There is no core-xxx folder on the iso.
]]>Ok then can you send me the values of /sys/block/yourusbdevice
"$(cat ${block}/${dev}/device/type)" == "0" && "$(cat ${block}/${dev}/removable)" == "1" && ! "$(cat ${block}/${dev}/size)" == "0"
I need the values of type removable and size
Thanks for your help to debug this.
in my case it looks like this:
"$(cat ${block}/${dev}/device/type)"
0"$(cat ${block}/${dev}/removable)"
1"$(cat ${block}/${dev}/size)"
3913664
Edit:
after i made changes suggested by spoked i was able to install packages. but another problem is with efivars. i already tried a solution from KairiTech but without a result
there is also a lot of lines about some relocation made written to the output
The umount is already removed from the next setup script.
What does /dev/*usb* show? I have no usbstick that makes such symlinks or nodes.
I'm sorry /dev/*usb* was just an abstraction of what your usb stick dev is such as /dev/sdb1 /dev/sdc1. A sort of "fill in the blank". It's my fault for using a non standard way of writing it. Could have been /dev/{PATH_TO_USB_STICK}
]]>spoked wrote:@pejotr
open /arch/setup in editor.At line 282, comment out the umount command.
mount /dev/*usb* to /src
!Could you give me a list of /dev/*usb* ?
And also a list of the /sys/block/*usb*Thanks i'll add it on next version to fix this issue.
Well, it depends on the user. For me, it was /dev/sdb1 as /dev/sda in my main hdd. I guess it is better to check if something is already mounted to /src and leave it that way if it is the case. I don't get the point of the umount procedure in the script, if a user has mounted an additional drive before loading up /arch/setup, surely they have an idea of what's going on.
]]>@pejotr
open /arch/setup in editor.At line 282, comment out the umount command.
mount /dev/*usb* to /src
!
Could you give me a list of /dev/*usb* ?
And also a list of the /sys/block/*usb*
Thanks i'll add it on next version to fix this issue.
]]>I have run into a similar problem this week while trying to install from the USB stick repo and not network while booting from UEFI. I found a solution that works, though I cannot guarantee it is bulletproof.
At boot, exit setup.
open /arch/setup in editor.
At line 282, comment out the umount command.
mount /dev/*usb* to /src
Run /arch/setup
It works for me, basically the script is unmounting any leftovers before trying to get its media, but fails to do so properly. The umount command in the script makes any manual attempt to work around the issue useless. Hope this helps!
]]>i'm having a problem installing archboot in uefi mode on my t420 notebook. What I did so far:
* create USB drive with fat32 filesystem and unpack there archboot iso. The system boot from USB - "UEFI only" mode, so far so good. But when it comes to Package Source a choose "CDROM, USBSTICK or OTHER SOURCE" and get first error:
No source media was autodetected, please switch to another VC and manually mount media under /src(...)
no problem, i thought i mounted the usb stick in /src everythink is in place. But then when i go to next step "Select Packages" i get and the bottom of the screen:
grep: /packages/core-x86_64/pkg/packages.txt No such file or directory
of course installation fails...
* i tried to follow a wiki tutor on creating usb stick https://wiki.archlinux.org/index.php/Ar … _ISO_Howto but there is no such folder "/core-x86_64/pkg" on archboot image i downloaded. The md5sum is edf1dafc993e7200f34b178b51f26f89 so image seems to be allright.
what is going on?
EDIT 1:
Installer is looking for archboot_packages_x86_64.tar, i created it from content of archboot_packages_x86_64.squashfs, but apperently it could find archboot_packages_x86_64.squashfs either. In dmesg I found:
FAT-fs (sdb): invalid media value (0xf3)
FAT-fs (sdb): Can't find a valid FAT filesystem
So how can I create valid filesystem??? I tried with diskpart on win7, and cfdisk on linux with partition type 0x0c
EDIT2:
I donloaded iso image again and recreated ubs stick, but i have stll the same problem
I did folowing:
# mount /dev/sdb1 /home
# mount -o loop /home/packages/archboot_packages_x86_64.squashfs /src
# /arch/quickinst media /mnt /src/pkg
but there is 7 error "failed retrieving file" for
linux-firmware-20110822-1-any
iana-etc=2.30-2-any
filesystem-2011.08-1-any
mkinitcpio-0.7.2-1-any
licenses-2.8-1-any
man-pages-3.32-1-any
pacman-mirrorlist-20110816-any
"Launch EFI shell from filesystem device" is likely an ASUS specific way to boot into a pure UEFI install. Seems like my ASUS looks or "Shellx64.efi" in the top level of all FAT partitions. That's why I can dump it onto a flash USB and boot from that into the install drive. It most likely will not work exactly the same with any other brand of motherboard/laptop.
You may have a similar boot option in your laptop's BIOS setup screen but there's no guarantee that the file should be named "Shellx64.efi" or that it should be in the same location as for my ASUS motherboard.
Look here for the "final" solution that worked for me...
]]>On HP Laptops the default paths to the efi file are
EFI/BOOT/BOOTX64.EFI
EFI/Microsoft/BOOT/bootmgfw.efi
but I don't get it to start automatically..
tried that :
cp /boot/efi/efi/grub/grub.efi /boot/efi/efi/Microsoft/BOOT/bootmgfw.efi
(Don't know if the firmware is case sensitivity..) Any information ?
My EFI partion ( GPT, EF00) is on a USB Stick (mounted on /boot/efi), Harddisk has its own /boot partion also GPT
only select efi file with F9 works..
shell also works with F9
Changing the efibootmgr boot order don't work, the Laptop forget it.
efibootmgr --create --gpt --disk /dev/sdb --part 1 --write-signature --label "GRUB2" --loader "\\EFI\\grub\\grub.efi"
efibootmgr --bootorder XXXX,YYYY,ZZZZ
Amusingly bootnext is working. Could wirte a script for every shutdown to set bootnext at grub.
efibootmgr --bootnext XXXX
Maybe I can try to change the Bootorder with the efi shell ?
Don't know if the bios is buggy or efibootmgr..
Tested with BIOS revision: 68SCF Ver. F08. I will update to F.20 soon.
Keep Calm and Hack On
]]>