Archiso x86_64 problem

[omran97@localhost livepd]$ sudo ./build.sh -v
[sudo] password for omran97:
cp: cannot stat ‘work/x86_64/root-image/usr/lib/syslinux/*.c32’: No such file or directory
What is wrong?

Check where it is trying to look for the c32 files. With syslinux v6 we now have syslinux bios and syslinux efi. So there is not /usr/lib/syslinux/{bios,efi}/*.c32.
It is pretty trivial to sed a fix into the build.sh. Though I think if you are using [testing], the sane thing to do would be to use archiso-git as djgera suggested above (he is the developer afterall, so you should probably listen to him).
Edit: The archiso-git package uses an outdated method of grabbing the sources. So I updated the PKGBUILD to take advantage of the pacman 4.1 capabilities. Here is the source tarball.
Last edited by WonderWoofy (2013-10-22 23:03:01)

Similar Messages

11g on SLES 10 x86_64 problem

Hi
I'm trying to install Oracle 11g Database (linux.x64_11gR1_database.zip)
on SLES 10 x86_64 SP1 (2.6.16.46-0.12-smp)
And I've got error while linking:
Exception Name: MakefileException
Exception String: Error in invoking target 'ioracle client_sharedlib' of makefile '/opt/oracle/product/11.1/db/rdbms/lib/ins_rdbms.mk'.
See '/opt/oracle/oraInventory/logs/installActions2007-12-27_08-34-26PM.log' for details.
Exception Severity: 1
and make.log last lines is:
/opt/oracle/product/11.1/db/lib//libctx11.a: could not read symbols: File format not recognized
collect2: ld returned 1 exit status
make: *** [opt/oracle/product/11.1/db/rdbms/lib/oracle] Error 1
Any ideas to solve it?

you welcome:
gcc -o /opt/oracle/product/11.1/db/rdbms/lib/oracle -L/opt/oracle/product/11.1/db/rdbms/lib/ -L/opt/oracle/product/11.1/db/lib/ -L/opt/ora
cle/product/11.1/db/lib/stubs/ -Wl,-E /opt/oracle/product/11.1/db/rdbms/lib/opimai.o /opt/oracle/product/11.1/db/rdbms/lib/ssoraed.o /opt
/oracle/product/11.1/db/rdbms/lib/ttcsoi.o -Wl,--whole-archive -lperfsrv11 -Wl,--no-whole-archive /opt/oracle/product/11.1/db/lib/nautab.o
/opt/oracle/product/11.1/db/lib/naeet.o /opt/oracle/product/11.1/db/lib/naect.o /opt/oracle/product/11.1/db/lib/naedhs.o /opt/oracle/produ
ct/11.1/db/rdbms/lib/config.o -lserver11 -lodm11 -lsage11 -lnnet11 -lskgxp11 -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls11 -lcore11 -lsnls11
-lnls11 -lxml11 -lcore11 -lunls11 -lsnls11 -lnls11 -lcore11 -lnls11 -lclient11 -lvsn11 -lcommon11 -lgeneric11 -lknlopt `if /usr/bin/ar tv
/opt/oracle/product/11.1/db/rdbms/lib/libknlopt.a | grep xsyeolap.o > /dev/null 2>&1 ; then echo "-loraolap11" ; fi` -lslax11 -lpls11 -lr
t -lplp11 -lserver11 -lclient11 -lvsn11 -lcommon11 -lgeneric11 `if [ -f /opt/oracle/product/11.1/db/lib/libavserver11.a ] ; then echo "-la
vserver11" ; else echo "-lavstub11"; fi` `if [ -f /opt/oracle/product/11.1/db/lib/libavclient11.a ] ; then echo "-lavclient11" ; fi` -lknlo
pt -lslax11 -lpls11 -lrt -lplp11 -ljavavm11 -lserver11 -lwwg `cat /opt/oracle/product/11.1/db/lib/ldflags` -lncrypt11 -lnsgr11 -lnzjs
11 -ln11 -lnl11 -lnro11 `cat /opt/oracle/product/11.1/db/lib/ldflags` -lncrypt11 -lnsgr11 -lnzjs11 -ln11 -lnl11 -lnnz11 -lzt11 -lztkg11
-lmm -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls11 -lxml11 -lcore11 -lunls11 -lsnls11 -lnls11 -lcore11 -lnls11 -lzt
kg11 `cat /opt/oracle/product/11.1/db/lib/ldflags` -lncrypt11 -lnsgr11 -lnzjs11 -ln11 -lnl11 -lnro11 `cat /opt/oracle/product/11.1/db/li
b/ldflags` -lncrypt11 -lnsgr11 -lnzjs11 -ln11 -lnl11 -lnnz11 -lzt11 -lztkg11 -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls11 -lcore11 -lsn
ls11 -lnls11 -lxml11 -lcore11 -lunls11 -lsnls11 -lnls11 -lcore11 -lnls11 `if /usr/bin/ar tv /opt/oracle/product/11.1/db/rdbms/lib/libknlopt
.a | grep "kxmnsd.o" > /dev/null 2>&1 ; then echo " " ; else echo "-lordsdo11"; fi` -L/opt/oracle/product/11.1/db/ctx/lib/ -lctxc11 -lctx11
-lzx11 -lgx11 -lctx11 -lzx11 -lgx11 -lordimt11 -lclsra11 -ldbcfg11 -lhasgen11 -lcore11 -lskgxn2 -locr11 -locrb11 -locrutl11 -lhasgen11 -
lcore11 -lskgxn2 -loraz -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls11 -lxml11 -lcore11 -lunls11 -lsnls11 -lnls11
-lcore11 -lnls11 -lsnls11 -lunls11 -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls11 -lxml11 -lcore11 -lunls11 -lsnls1
1 -lnls11 -lcore11 -lnls11 -laio `cat /opt/oracle/product/11.1/db/lib/sysliblist` -Wl,-rpath,/opt/oracle/product/11.1/db/lib -lm `cat
/opt/oracle/product/11.1/db/lib/sysliblist` -ldl -lm -L/opt/oracle/product/11.1/db/lib
/opt/oracle/product/11.1/db/lib//libctx11.a: could not read symbols: File format not recognized
collect2: ld returned 1 exit status
make: *** [opt/oracle/product/11.1/db/rdbms/lib/oracle] Error 1
enough or more?

NeverWinterNights x86_64 problem

Hi guys.
I've installed this game with nwn-diaimond package from AUR. Everything went perfect (intro, movies, etc.), I started play the game, but then the game just exits.
Here is, what i got from terminal
ERROR: ld.so: object './nwuser64.so' from LD_PRELOAD cannot be preloaded: ignored.
NOTICE: NWLogger: Version: 20040311.192648
NOTICE: NWLogger: Initializing handles.
NWUPOSSIBLE: Unmatched Path: /etc/passwd -> /etc/passwd
NOTICE: NWUser: Version 20041005.184851 Successfully loaded. (BaseDir = /opt/nwn)
NOTICE: NWLogger: Patch 0 Address: 0x080b8c0f
NOTICE: NWLogger: Patch 1 Address: 0x082ad068
NOTICE: NWLogger: Patch 2 Address: 0x080be2cf
NOTICE: NWLogger: Patch 3 Address: 0x080c44bb
NOTICE: NWLogger: Patch 4 Address: 0x080c466b
NOTICE: NWLogger: PrePatch0 : 53 8b 45 08 ff 70 08
NOTICE: NWLogger: PostPatch0: e9 5c f4 6d ef 90 90
NOTICE: NWLogger: PrePatch1 : 56 53 81 ec c8 00 00 00
NOTICE: NWLogger: PostPatch1: e9 eb af 4e ef 90 90 90
NOTICE: NWLogger: PrePatch2 : 56 53 8b 75 08
NOTICE: NWLogger: PostPatch2: e9 58 9d 6d ef
NOTICE: NWLogger: PrePatch3 : 53 83 ec 10 a1 54 c3 62 08
NOTICE: NWLogger: PostPatch3: e9 cc 3b 6d ef 90 90 90 90
NOTICE: NWLogger: PrePatch4 : 56 53 83 7d 0c 01
NOTICE: NWLogger: PostPatch4: e9 d0 39 6d ef 90
NOTICE: NWLogger: Handles Initialized.
NOTICE: NWMovies(./nwmain): Version: 20090223.080954
NOTICE: Looking up symbols in libSDL.....
NOTICE: NWMovies: Using libSDL via RTLD_NEXT.
NOTICE: SDL Library determined to be: /usr/lib32/libSDL-1.2.so.0
NOTICE: NWMovies: SDL_WM_GrabInput() address: f755b2f0
NOTICE: NWMovies: SDL_GetVideoSurface() address: f75595f0
NOTICE: NWMovies: SDL_WM_ToggleFullScreen() address: f755c6b0
NOTICE: NWMovies: SDL_PollEvent() address: f7537b00
NOTICE: NWMovies: SDL_WM_IconifyWindow() address: f755c680
NOTICE: NWMovies: Patch 0 Address: 0x08077a9d
NOTICE: NWMovies: Patch 1 Address: 0x08077ab1
NOTICE: NWMovies: Patch 2 Address: 0x0815b5f7
NOTICE: NWMovies: Patch 3 Address: 0x0815b611
NOTICE: NWMovies: Patch 4 Address: 0x0807796f
NOTICE: NWMovies: Patch 5 Address: 0x08207835
NOTICE: NWMovies: Patch 6 Address: 0x08207858
NOTICE: NWMovies: PrePatch0: 8b 80 78 02 00 00 5d c3
NOTICE: NWMovies: PrePatch1: 8b 80 7c 02 00 00 5d c3
NOTICE: NWMovies: PrePatch2: e8 68 c5 f1 ff 83 ec 08
NOTICE: NWMovies: PrePatch3: 169+: eb 59 90 83
NOTICE: NWMovies: PostPatch0: b8 00 00 00 00 90 5d c3
NOTICE: NWMovies: PostPatch1: b8 00 00 00 00 90 5d c3
NOTICE: NWMovies: PostPatch2: 90 90 90 90 90 83 ec 08
NOTICE: NWMovies: PostPatch3: 169+: 90 90 90 83
NOTICE: NWMovies: PrePatch4: 56 8d 5d e8 53
NOTICE: NWMovies: PostPatch4: e9 20 d4 72 ef
NOTICE: NWMovies: MoviesPrePatch: 6a 00 53 bf 00 00 00 3f e8 72 4f 2a 00 8b 43 60 8b 10 c7 04 24 00 00 80 3f 57 57 57 50 ff 52 44 83 c4 1c
NOTICE: NWMovies: MoviesPostPatch: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
NOTICE: NWMovies: Initialized.
NOTICE: NWMouse: Version: 20050216.085035
NOTICE: NWMouse: Patch 0 Address: 0x084e9380
NOTICE: NWMouse: Patch 1 Address: 0x084e009c
NOTICE: NWMouse: Patch 2 Address: 0x0863d880
NOTICE: NWMouse: Patch 3 Address: 0x084ffd44
NOTICE: NWMouse: Patch 4 Address: 0x084e3018
NOTICE: NWMouse: Patch 5 Address: 0x084e05b7
NOTICE: NWMouse: Patch 6 Address: 0x084e8440
NOTICE: NWMouse: Stop pointer: 0x084e9380
NOTICE: NWMouse: Table Address: 0x0863d880
NOTICE: NWMouse: Table Length: 89
NOTICE: NWMouse: Render function replaced in secondary table, offset: 6
NOTICE: NWMouse: Texture function replaced in secondary table, offset: 13.
NOTICE: NWMouse: Orientation function replaced in secondary table, offset: 25.
NOTICE: NWMouse: Original Table: 80 d8 63 08
NOTICE: NWMouse: Pushed: 54 2a 7c 08
NOTICE: NWMouse: PreMod1: c7 40 0c 80 d8 63 08
NOTICE: NWMouse: PostMod1: e9 6d 6a 2d ef 90 90
NOTICE: NWMouse: PreMod2: ff 05 68 d8 63 08
NOTICE: NWMouse: PostMod2: e9 99 65 2d ef 08 83
NOTICE: NWMouse: Initialized.
NOTICE: NWLogger: mkdir(/home/jerod/.nwn/./tempclient/, 0777) caught
NOTICE: NWLogger: mkdir(/home/jerod/.nwn/./localvault/, 0777) caught
NOTICE: NWLogger: mkdir(/home/jerod/.nwn/./dmvault/, 0777) caught
NOTICE: NWLogger: mkdir(/home/jerod/.nwn/./servervault/, 0777) caught
NOTICE: SDL_WM_GrabInput(QUERY) called..
NOTICE: SDL_WM_GrabInput(OFF) called..
Please help me, because I have no idea "what the problem is" not even how to fix it.
Thanx
Last edited by Jerod (2012-10-14 12:18:17)

I have the same problem everything work fine but the game crash on certain event for example when i draw my crossbow.

[Solved] archiso UEFI boot doesn't work.

I just followed the instruction on https://wiki.archlinux.org/index.php/UE … B_from_ISO, but it doesn't work as intended. It shows just 3 menu,
Arch Linux archiso x86_64 UEFI USB
UEFI Shell x86_64 v1
UEFI Shell x86_64 v2
I thought, the first option is the way to go, but
Error loading \arch\boot\x86_64\vmlinuz: Not found
In fact, there is no \arch directory. The iso file downloaded was not broken, so I think something's missing either in the article or in the iso file.
edit : I found that, the name of 'arch' directory was changed to something like "?????????". I don't know why, but when I changed it to "arch" again, it works like a charm.
Last edited by kreoso (2012-11-01 16:54:57)

Exactly the same thing happened to me. I think there's some filename encoding issue because I wasn't able to rename ????????? to arch, instead I moved to arch2 then renamed arch2 to arch. Happy to say that worked for me too.
I should add that the same USB stick worked first time with my laptop, it was only when trying to boot my desktop in the same way that I hit this issue, so it seems sensitive to BIOS manufacturer/version.
Last edited by malcolmsparks (2012-11-04 19:46:32)

[SOLVED, kind of] UEFI bootable USB from ISO doesn't start

Hi there,
out of curiosity I wanted to create an UEFI bootable usb stick with the latest Archiso 2013.01.04. I've followed https://wiki.archlinux.org/index.php/UE … B_from_ISO
and created two directories
# mkdir -p /mnt/{usb,iso}
Then I've mounted Archiso to /mnt/iso
# mount -o loop Download/ISO-Images/archlinux-2013.01.04-dual.iso /mnt/iso
After this I used cfdisk to create a FAT32 filesystem /dev/sdb1 on the usb stick, followed by
# awk 'BEGIN {FS="="} /archisolabel/ {print $3}' /mnt/iso/loader/entries/archiso-x86_64.conf | xargs mkfs.vfat /dev/sdb1 -n
Then I've mounted /dev/sdb1 to /mnt/usb and copied all iso-files there:
# mount /dev/sdb1 /mnt/usb
# cp -r /mnt/iso/* /mnt/usb
Followed by:
# umount /mnt/{usb,iso}
# sync
After rebooting and hitting F11 I was presented with the UEFI firmware-tool from which I can choose UEFI (and other) applications to start. I could choose my usb stick in UEFI mode, but - only the screen turned blank for the blink of a second and the UEFI tool was on again.
Because my system is already booting in UEFI mode using rEFInd, I wanted to try rEFInd on the usb stick instead of gummiboot.
Following https://wiki.archlinux.org/index.php/UE … B_from_ISO I've copied /usr/lib/refind/refind_x64.efi (from refind-efi 0.6.4-1) to /mnt/usb/EFI/boot/bootx64.efi and created a /mnt/usb/EFI/boot/refind.conf with this text:
timeout 5
textonly
showtools about,reboot,shutdown,exit
# scan_driver_dirs EFI/tools/drivers_x64
scanfor manual,internal,external,optical
scan_delay 1
dont_scan_dirs EFI/boot
max_tags 0
default_selection "Arch Linux Archiso x86_64 UEFI USB"
menuentry "Arch Linux Archiso x86_64 UEFI USB" {
loader /arch/boot/x86_64/vmlinuz
initrd /arch/boot/x86_64/archiso.img
ostype Linux
graphics off
options "pci=nocrs add_efi_memmap archisobasedir=arch archisolabel=ARCH_201301"
menuentry "UEFI x86_64 Shell v2" {
loader /EFI/shellx64_v2.efi
graphics off
menuentry "UEFI x86_64 Shell v1" {
loader /EFI/shellx64_v1.efi
graphics off
And yes, I've checked the "loader" and "initrd"-Paths - they are correct, as well as the archisolabel
But - again - after rebooting and hitting F11 I could select my usb stick as UEFI boot device, but all that happened was the screen going blank for the glimpse of a second and returning to the UEFI chooser.
Even my last attempt - keeping the original name refind_x64.efi in /mnt/usb/EFI/boot didn't help.
Via efibootmgr I can see:
$ sudo efibootmgr
BootCurrent: 0001
Timeout: 5 seconds
BootOrder: 0001,0002,0007,0005,0006
Boot0001* rEFInd 0.6.4-1
Boot0002* rEFInd_recover
Boot0005* Hard Drive
Boot0006* USB
Boot0007* UEFI: TOSHIBA TransMemory PMAP
with "Boot0007" as my usb stick.
So my question is: Did I miss something or have I found a bug ?
Last edited by swordfish (2013-01-13 12:43:33)

Hm, funny thing - now it's working, but I don't know why
I've tried to convert the partition table of the usb stick from MBR to GPT using cgdisk. There I had a problem with setting the partition type to EF00. It worked under cgdisk, but then I couldn't mount my usb stick (dev/sdb1) anymore to /mnt/usb. Then I've tried to set the partition type to vfat, but couldn't identify what is vfat under cgdisk . I've tried different types of "Windows" but whatever I tried, the usb stick won't mount on /mnt/usb.
Journalctl always says:
Jan 13 12:23:03 sushi sudo[727]: nihonto : TTY=pts/0 ; PWD=/home/nihonto ; USER=root ; COMMAND=/usr/bin/cgdisk /dev/sdb
Jan 13 12:23:03 sushi sudo[727]: pam_unix(sudo:session): session opened for user root by nihonto(uid=0)
Jan 13 12:23:11 sushi sudo[727]: pam_unix(sudo:session): session closed for user root
Jan 13 12:24:00 sushi su[972]: (to root) nihonto on /dev/pts/0
Jan 13 12:24:00 sushi su[972]: pam_unix(su:session): session opened for user root by nihonto(uid=1000)
Jan 13 12:24:18 sushi kernel: loop: module loaded
Jan 13 12:24:18 sushi kernel: ISO 9660 Extensions: RRIP_1991A
Jan 13 12:24:35 sushi kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
Jan 13 12:24:35 sushi kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
Jan 13 12:24:35 sushi kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
Jan 13 12:24:35 sushi kernel: FAT-fs (sdb1): bogus number of reserved sectors
Jan 13 12:24:35 sushi kernel: FAT-fs (sdb1): Can't find a valid FAT filesystem
Jan 13 12:24:35 sushi kernel: ISOFS: Unable to identify CD-ROM format.
So I tried it again with cfdisk which nagged about "unsupported GPT" but kept working. This time I choose "0C W95 FAT32 (LBA)" as partition type - maybe this did the trick because in my earlier attempts I did choose "0B W95 FAT32".
Anyway - after following the advice stated in https://wiki.archlinux.org/index.php/UE … B_from_ISO and installing rEFInd to the usb stick I could boot the usb stick in UEFI mode
But - as I said earlier - I don't know what did the trick
Last edited by swordfish (2013-01-13 12:38:18)

Blue screen when booting from USB drive in UEFI mode (2013.07)

SOLUTION for me was to update the firmware on my ASRock mb as thatu pdate changed the EFI software (by American Megatrends) version from 2.00 to 2.31. However, other users are still experiencing the blue screen.
SHORT VERSION
When I try to boot Arch Linux 2013.07 with an USB drive in UEFI mode (for installation), I get a blue screen (which is rather a literal description and not a hint towards the old Windows' one) with the message
Failed to install override security policy (14): Not found
LONG VERSION
I made an USB installation media (product: Intenso Rainbow) by following this advice on the wiki.
I used the july release of Arch for that. First of, after installing the image to the USB stick I found that I needed to correct the label in the archiso-x86_64.conf file to ARCH_201307 (or was it the label of the usb stick, can't remember right now). (Pretty sure it was the same problem with "Linux Live USB Creator" which I used 3-4 months ago...)
After doing that, I rebooted and selected the entry
UEFI Intenso Rainbow
from this list of entries:
SATA HDJ ... something (the hard drive where Win 7 64 bit is installed with all programs)
SATA something (hard drive which only contains data)
Windows Boot Manager
USB: Intenso Rainbow
UEFI: Intenso Rainbow
It went to a blue screen with a message in white text saying
Failed to install override security policy (14): Not found
Below that was an OK button which had a black rectangle over it.
After I experienced the bluescreen, I tried booting the
USB Intenso Rainbow
entry and the boot process then worked fine, I got to that Arch menu where I could choose
Boot Arch Linux (x86_64)
Boot Arch Linux (i686)
Boot existing OS
Run Memtest...
and so on...
But just to make sure, I then did the check for UEFI mode according to this and only saw a folder acpi and ... something else I can't really remember, but it definitely was not efi. Thing is, I needwant to boot into UEFI mode as I have Win 7 already installed in UEFI mode.
Some info about my motherboard: it's from ASRock and is called H67M. The BIOS is dated to 2011-10-26 and is version 1.7.
So far, I only found a mention of the problem here at superuser.com.
Last edited by jones (2013-07-15 07:15:18)

Ok then, so this thread has also become about the blank screen problem when booting (in this particular case, Arch 2013.06 since 2013.07 seems to be worse).
srs5694 wrote:Typically, you adjust kernel boot options using your boot manager or boot loader. In GRUB, you hit the "e" key to open an editor. In rEFInd, you hit F2 or Insert twice. I don't recall offhand what key does the job for gummiboot (which I'm pretty sure the Arch installer uses), but I'm certain it's got the feature.
You are right. Thanks. I realized I had the gummiboot config right in front of me all the time. It's the file 'archiso-x86_64.conf' in \loader\entries (on Windows).
An addendum: I think the USB: Intenso Rainbow boot option takes me into a GRUB menu. Hitting 'e' in this "big" and fully designed menu didn't do anything IIRC. Hitting 'Tab' did the trick to get into editing the boot command line.
Hitting 'e' worked in the gummiboot menu though.
So I tried booting with the following options (also by combining some of them)
nomodeset
acpi_backlight=vendor
radeon.modeset=0 (I have a Gigabyte 7870 card in this desktop machien)
i915.modeset=0
but it did not help.
To be rather safe than sorry: I should mention that there are two grey-ish bars visible on the top and bottom of the screen after I try to boot the first entry, Arch Linux archiso x86_64 UEFI USB. Always has been with those two older Arch version (2013.05+2013.06). I also found another thread where one user talks about using the VGA port of the monitor, which I am currently not, I am using the DVI one, so that's worth a try too. EDIT It did not help either. What I did was setting the primary graphics adapter in the UEFI north bridge configuration menu to 'onboard' which worked immediately when rebooting (I hit the button labeled "Source" on my monitor and it showed it is using the "Analog" mode), but the problem just stayed the same. Adding aforementioned boot options or a combination thereof did not change anything.
Thanks for the e-mail addresses, I sent one to James Bottomley.
Last edited by jones (2013-07-07 11:12:05)

Lenovo Yoga 2 Pro: endless error(?) messages during installation

I'm trying to install Arch Linux on a Lenovo Yoga 2 Pro. It came pre-installed with Windows 8.1, but all remnants of W8 have been removed. Currently it's running Ubuntu-Gnome.
Using Windows 7, I created a UEFI bootable USB stick using the instructions provided on the wiki (extracting w/ 7zip and renaming the volume label). The UBS stick booted just fine, and I was presented with a menu of about 5 items -- the first being "Arch Linux archiso x86_64 UEFI" After selecting the first item, the screen ran through a bunch of items (too small for me to see with this crazy resolution), but they all said [OK]. Then the screen cleared and I was presented with a shell prompt. This is where the problem begins. Immediately, I start seeing the following lines written to the screen about every 5 seconds...
usb 2-7 unable to read config index 0 descriptor/start: -71
usb 2-7 can't read configurations, error -71
periodically I see this thrown in as well...
unable to enumerate USB device on port 7
Every time I try typing something whatever I'm typing gets blown away by 2 more lines being written to the screen. This never ends. Eventually I end up with thousands rows and I just give up.
Any ideas? Is the hardware too new?
Thanks very much!
Eric

I can completely understand this guy's frustration with the clickpad, it is completely unusuable with the default settings. I played around with the synaptics settings and it is much better now, I just adjusted the FingerHigh and FingerLow options:
synclient FingerHigh=46
synclient FingerLow=46
With these settings, the cursor doesn't twitch around anymore when you try to click something.

SOLVED - modifying the arch .iso

Hi all. Apologies if I'm doing something obviously wrong. I'm trying to copy EFI/BOOT/loader.efi to EFI/BOOT/boot on the downloaded arch iso.
Reason for this is to boot the iso on my lennovo e71 which even with a BIOS update refuses to boot with the following error: 'failed to install override security policy'.
I've followed the steps on the wiki: https://wiki.archlinux.org/index.php/Re … nstall_ISO
Essentially using the command:
"genisoimage -l -r -J -V "ARCH_201209" -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -c isolinux/boot.cat -o ~/arch-custom.iso ~/customiso"
The newly generated iso refuses to boot. Any ideas? (yes I did amend the label to that of the original image.)
Thanks in advance
Ian
Last edited by Hutchism (2014-10-20 21:05:55)

Hutchism wrote:...
"genisoimage -l -r -J -V "ARCH_201209" -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -c isolinux/boot.cat -o ~/arch-custom.iso ~/customiso"
Ian
Are you actually using ARCH_201209?
I know you wrote you had modified the label "ARCH_YYYYMM", but double check it.
EDIT: Did you modify 'archisolabel' in loader/entries/archiso-x86_64.conf or/and in arch/boot/syslinux/archiso.cfg?
I have noticed that the latest ISO (2014-08) has some file names changed in its internal structure. Some files have been moved to other places, too. Perhaps that is why you ISO doesn't boot.
I have modified my script to work with the new structure of the current ISO, and created modified ISO's that successfully start in both BIOS and UEFI configurations on my virtual machine. I can add the copying of those .efis and send you the script to use or to see what it looks like.
EDIT2: No reply, so this information is for those who might look for an arch ISO image starting with a passwordless sshd service on a standard port. I have put my bash script in AUR, arch-headless. The script includes a commented out solution to the original poster's problem, as he suggested in post 3. You can uncomment it and try if it works, I have never done it.
Last edited by dif (2014-08-05 15:09:48)

[SOLVED] Installation on UEFI from usb stick

Greetings,
I'm trying to figure out this uefi thing and install arch on my laptop.
I swear, I've been trying so many times now that I have a headache. My girlfriend too because of all my ranting.
I downloaded the latest arch iso and "burned" it to a usb stick (my laptop lack a cdrom).
I booted with the first option and went through the whole installation progress to the grub installing part MANY times before realizing I was doing it all wrong and I had to start from a UEFI shell.
Now I started from the UEFI shell and I just have no idea what I'm doing, the beginner guide doesn't seem to explain this.
I should probably wait until my headache pass and I'm fresh and ready to start over but I'm one stubborn guyif there is one and I had enough of failing, I want it to work.
What do I do from the UEFI shell?
Do I have to reinstall everything from scratch, partitioning and all or I can just get back to the part where I have to install grub? What do I do?
Thanks in advance and sorry if I'm asking stupid questions or something but, honestly, I failed so many times that my frustration is seriously high.
Last edited by arkindal (2013-08-13 23:13:11)

Hi,
this is basically what I followed and it worked for me:
make an archlinux uefi usb stick (it's a bit different than a normal one). Use a live ubuntu cd or something, so you don't have to use windows:
#format your usb key on /dev/sdXY to fat32 (replace XY with the right device, in the following code too)
sudo su
wget http://mirror.us.leaseweb.net/archlinux/iso/2013.08.01/archlinux-2013.08.01-dual.iso
mkdir -p /mnt/{usb,iso}
mount -o loop archlinux-2013.08.01-dual.iso /mnt/iso
awk 'BEGIN {FS="="} /archisolabel/ {print $3}' /mnt/iso/loader/entries/archiso-x86_64.conf | xargs mkfs.vfat -F32 /dev/sdXY -n
mount /dev/sdXY /mnt/usb
cp -a /mnt/iso/* /mnt/usb
sync
umount /mnt/{usb,iso}
full instructions here: https://wiki.archlinux.org/index.php/Un … B_from_ISO
now you have the instalation usb ready.
When I did this, i could still go to choose my boot device and i had a normal usb key boot option and an uefi shell usb key option, see if you have something like that to be sure you have the uefi boot. you should see an uefi shell and it should boot automatically as a normal archlinux live usb. if it doesn not (happend to me before) run ./start.sh or something like that (it should say in the uefi shell what to run). If that doesn not work, then the uefi usb key didn't work.
okay if you've successfully booted the uefi usb you have to format your drive so it has the uefi boot partition mounted inside the grup folder, so there has to be a ef00 partition on the begining
This is my actuall install script, it will wipe your drive, make 5 partitions (uefi boot, boot, swap, root, home) and then mount them, install arch and then chroot into that
modprobe efivars
#configure this as you wish
SWAPSIZE=4G
ROOTSIZE=50G
DRIVE=sda
#these two lines are horrible, you could manually use gdist and format the drive as you wish, as this will just wipe it clean and make the partion table that I have.
dd if=/dev/zero of=/dev/$DRIVE bs=1M count=1k
echo "2\no\ny\nn\n\n\n+100M\nef00\nn\n\n\n+100M\n\nn\n\n\n+${SWAPSIZE}\n8200\nn\n\n\n+${ROOTSIZE}\n\nn\n\n\n\n\np\nw\ny\n" | gdisk /dev/$DRIVE
mkfs.vfat -F 32 /dev/${DRIVE}1
mkfs.ext2 -L boot /dev/${DRIVE}2
mkswap -L swap /dev/${DRIVE}3
mkfs.ext4 -L root /dev/${DRIVE}4
mkfs.ext4 -L home /dev/${DRIVE}5
swapon /dev/${DRIVE}3
mount /dev/${DRIVE}4 /mnt
mkdir /mnt/home
mount /dev/${DRIVE}5 /mnt/home
mkdir /mnt/boot
mount /dev/${DRIVE}2 /mnt/boot
#this is the magic uefi part for grub
mkdir /mnt/boot/efi
mount /dev/${DRIVE}1 /mnt/boot/efi
pacstrap /mnt base base-devel zsh
genfstab -U -p /mnt >> /mnt/etc/fstab
arch-chroot /mnt
After doing that, you have can install the system as you wish and for the grub I do this:
I had problems a few times if i copy pasted all these lines at once, so now i copy paste them one at a time, (I know it should not make a difference but still, sometimes it didn't work)
# i do this in chmod too, though I'm not sure if it's really necessary
modprobe efivars
mkinitcpio -p linux
echo "installing efi grup thingy"
pacman -S --noconfirm efibootmgr grub-efi-x86_64
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck --debug
mkdir -p /boot/grub/locale
cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
grub-mkconfig -o /boot/grub/grub.cfg
and this is all i have in my install script file and uefi works fine. I hope you'll get it running soon
Last edited by zidarsk8 (2013-08-09 00:25:20)

Trouble with UEFI Vaio

Hi,
I've been struggling with arch and the UEFI laptop. In legacy mode on my laptop, it just complains that there's no OS found in all the cases I've examined. So, I decided to leave it in UEFI mode, which gives the added bonus of being able to boot Win8 if I should ever need it.
So, I've followed these instructions:
https://wiki.archlinux.org/index.php/US … _USB_drive
with the appropriate detour over to : https://wiki.archlinux.org/index.php/UE … B_from_ISO.
Problem 1:
sudo awk 'BEGIN {FS="="} /archisolabel/ {print $3}' /mnt/iso/loader/entries/archiso-x86_64.conf | xargs mkfs.vfat -F32 /dev/sdg1 -n
returns the following:
mkfs.vfat 3.0.12 (29 Oct 2011)
/dev/sdg1: Permission denied
So, I just manually ran
"sudo mkfs.vfat -F32 /dev/sdg1 -n ARCH_201302"
, which appears to work.
Then I complete the mount/copy/sync/umount, and go back to the first page.
So now, I've got a fat32 disk with everything copied in from the ISO, and the label set to ARCH2013_02.
I follow the instructions, and everything seems to go fine (even the sed command to do the uuid stuff, which wasn't working on previous attempts).
...and this time it just tells me OS not found again, when I try to boot. The farthest I've previously gotten was the the "Device didn't show up in 30 seconds", where I get dumped to a root terminal. I've tried symlinking what I think is the correct
device to what it thinks is the correct device, along with doing the mounting for it. The farthest that's ever gotten is to something that tells me to check dmesg | tail, where I found a message complaining about the FAT32 disk having bogus sectors I think.
Does anyone have any ideas for any of these problems? (My current OS not found after redoing some steps, or the problem I'll likely run into if I manage to get past the OS not found)
Thanks.
Last edited by metaf5 (2013-03-04 01:18:47)

Have I understood correctly in thinking that you are trying to create a USB medium from the current Arch .iso which will be bootable in UEFI mode but without overwriting the existing contents of the USB key?
If so, do you know whether that is possible? Those instructions seem to be for legacy/bios booting since they use syslinux which doesn't (except in alpha) support UEFI booting that I know of.
Also, please use [code ][/code ] tags (without the spaces).

[solved}Permanent USB boot and new udev?

I'm always booting from an usb stick on my netbook and the new udev seems to create problems in some cases. A real problem in my case would be that udev makes my usb stick not to be found and the netbook unbootable. However, the stick is fully represented in fstab;
UUID=52523bb8-e3fb-40c7-93a5-afe47fb62a91 /boot ext2 defaults,noatime,nodiratime 0 1
UUID=827d9502-aa52-4989-ba55-2afd2a0ed377 /home ext4 defaults,noatime,nodiratime,commit=60 0 1
UUID=b0ab0cc0-9ab9-4b8b-967d-871788b9f4ab / ext4 defaults,nodiratime,noatime,commit=55 0 1
UUID=cd38656a-f2bb-45c3-a23d-6e0d7c09bbb3 swap swap defaults 0 0
I suspect it's ok to update udev but if it's not i'd like some advice to make a fix beforehand.
EDIT: update worked out OK.
Last edited by swanson (2011-10-26 07:06:30)

Yeah, classic error. "LiLi" was mentioned in the wiki, except that someone decided to remove the information...
https://wiki.archlinux.org/index.php?ti … did=251979
The complete version can be found on the History page, just before the lines were removed:
https://wiki.archlinux.org/index.php?ti … SB_Creator
LiLi changes the label of the USB to MYLINUXLIVE by default but the file archiso-x86_64.conf tell linux to look for installation media named with the month and release date of the file, eg: ARCH_201302 Hence the famous 30 second error.
Anyway, welcome to the forum! Don't forget to mark the topic as solved (by editing the first post) so that other people (including yourself sometimes) may find useful.
Last edited by DSpider (2013-06-25 19:28:59)

[MOOT] UEFI USB Install (from 201306 image) - blank screen during boot

I am trying to install Arch Linux on a Lenovo ThinkPad T431s.
I created a bootable UEFI USB disk image following the instructions on the wiki.
https://wiki.archlinux.org/index.php/UE … B_from_ISO
Attempting to boot from this image I get to a screen that looks like:
Arch Linux archiso x86_64 UEFI USB
UEFI Shell x86_64 v1
UEFI Shell x86_64 v2
After selecting the first option, I get a blank screen.
This appears to be the same (or very similar) to the following issues:
[1] https://bbs.archlinux.org/viewtopic.php?id=151599
[2] https://bbs.archlinux.org/viewtopic.php?id=158530
As suggested by
https://wiki.archlinux.org/index.php/Beginners'_Guide#Preparation
I tried appending a number of things to the initrd line
nomodeset
video=SVIDEO-1:d
i915.modeset=0
with no success (the blank screen was exactly the same).
Some posts in thread [2] indicated that booting in legacy bios mode worked. I created a new disk image (again following the wiki instructions: https://wiki.archlinux.org/index.php/US … ion_Media) and was able to confirm that I could successfully boot from this other image after switching into legacy mode.
In thread [1], there was the suggestion to go into a UEFI shell and try a command like
Shell > fs0:
FS0:\ > cd \arch\boot\x86_64
FS0:\arch\boot\x86_64\ > vmlinuz archisobasedir=arch archisolabel=ARCH_201306 initrd=\arch\boot\x86_64\archiso.img
which I did. After pressing enter nothing happened (the screen did not go blank, all the text remained, no messages appeared).
Eventually in that same thread, a workaround was suggested in this post. I have not tried this because I was unable to understand what exactly was being done, both because of the terse nature of the post and the fact that the referenced article is not in a language which I read (and google translate did not make it clear enough). I was unable to evaluate whether that was a sensible thing to do.
Now, finally, the questions
Firstly, does anyone have any suggestions about how to solve or troubleshoot my blank screen issue?
If not, does anyone have an opinion about which of the workarounds (switching into legacy mode or the one that I don't quite understand yet) would be better? I am not planning to dual boot the system, so I do not need to use UEFI to be win8 friendly, etc.
Last edited by wesphys (2013-06-07 14:36:28)

Auric wrote:
Neri, did you get any further with this? I just got my own Thinkpad Yoga and am facing the same problems. Everything works fine in legacy Boot but the screen stays black on UEFI boot regardless of the known workarounds.
might it help to first install using legacy boot and later on convert to UEFI?
Not really with Arch directly anyways. What you can do is:
1. Use Fedora 20 USB to boot the sucker up
2. Use Archlinux-bootstrap install (download expand etc)
3. Use refind as the bootmanager seems to solve the dual boot issues
ATM i'm fighting a mkinitcpio segfault. But that is after the installation was basically successful. It would be nice if we can find a way to fix the install medium ...
EDIT:
All sorted out. Unfortunately you'll have to bypass the Archlinux Install medium and resort to the fedora 20 installer. I used the XFCE4
version for a smaller download.
Here are the basic steps for a Dual-Boot setup:
In windows (Disk Management) truncate your C: Drive. I ended up making basically what will became /dev/sda4 smaller and didn't not
touch any partition or free space before that. Here's the final Layout:
/dev/sda:
empty space
1. recovery partition
2. ESP
3. reserved
4. windows
5. Linux Root
6. Linux home
7. Swap
The installation happened from within Fedora Live using an Archlinux Boot strap image according to the Wiki for installing from an
existing Linux and the Wiki Installation Guide. I mounted /dev/sda2 (aka. the existing ESP partition) as /boot and installed refind
according to the wiki. Please note, when you install Arch through the archlinux bootstrap method make sure you pacman -S archlinux-keyring
in the bootstrap chroot first before you run the pacstrap command - it will accelerate the process tremendously!
Last edited by neri (2014-01-02 21:40:31)

Installing onto x220t in UEFI mode

I created USB following instructions here: https://wiki.archlinux.org/index.php/UEFI#In_Windows
Booting from USB will arrive to 4 options:
Arch Linux archiso x86_64 UEFI USB
UEFI Shell x86_64 v1
UEFI Shell x86_64 v2
EFI Default Loader
options 1 and 4 goes to some black screen with nothing appearing for some time.
option 3 goes to ASSERT_EFI_ERROR (Status = Device Error)
Option 2 goes to the UEFI Shell, but I don't know what to do from there.
Some info:
UEFI BIOS version 8det61ww (1.31)
UEFI BIOS Date 2012-04-25
Embedded Controller Version 8DHT30WW (1.20)
Machine Type Model 429636U

On top of the fact that UEFI is a bit to wrap your head around at first, you are also facing the issue of having an old UEFI version (1.31). This is why the UEFI shell v2 doesn't work. Though why the installer won't boot, I am not quite sure. But it may be that you are running into the Intel KMS issue that is pretty common. Try editing the kernel command line before booting and adding "nomodeset". If it boots, then you know it is a graphics issue.
Even though UEFI might be hard at first, in my opinion, it becomes much much easier, and ultimately makes a lot more sense than the old bios/MBR way of doing things. I think what made it particularly hard for me at first was the fact that a) like you, I ran into issues, and b) I already understood the basic process of how the old booting method worked (which just confused the hell out of me).
If you continue to have troubles with your system, hopefully srs5694 can swoop in and save the day (sometimes mentioning his name seems to summon him). Otherwise, I am pretty sure that cfr has the same UEFI firmware version as you. If your machine's firmware is the same as his, you might be in for a hard time in getting things working right. I know there were a number of bugs he had to overcome to get his machine working with UEFI.

MacBook Pro Installation - Failed to Mount Real Root

Hi, I've been trying to install Arch on my older MBP for years now (2009 model, I think) with a single-boot configuration. I can successfully boot from the USB, where I get to select from three shells to boot in, being:
Arch Linux archiso x86_64 UEFI USB
UEFI Shell x86_64 v1
UEFI Shell x86_64 v2
Then, I select the first, and stuff just skims by at first, until I end up at something like:
:: Device /dev/disk/by-label/ARCH_201303' mounted successfully
:: Mounting /run/archiso/cowspace (tmpfs) filesystem, size=75%...
:: running late hook [archiso_pxe_common]
:: running cleanup hook [archiso_shutdown]
:: running cleanup hook [udev]
ERROR: Failed to mount real root device
Bailing out, you are on your own. Good luck.
Then I'm stuck with a shell as root with barely any commands to use (no fdisk/gdisk/insert-any-partitioning-tool-here), etc. I'm pretty sure this isn't supposed to happen. Is there any guide on how I can fix this? Googling hasn't exactly worked, and I couldn't find anything on the Arch Wiki too easily.
Thanks for the help!
Important note:
Months ago, I got stupid and did try to install CrunchBang (BIOS boot only, obviously). That erased pretty much everything (that includes the EFI partition, etc.) and left me with a few unbootable partitions. So, uh, that is to say, if any suggestion involves booting up from OS X and doing anything, or using rEFInd/rEFIt, it won't work. Thankfully, however, I am able to do most Linux commands as I am currently on my primary system, Linux Mint.
Last edited by kyeshi_0913 (2013-06-13 23:02:15)

@ the_isz - Thanks for the read, but no help.
@swanson - That usb hook was added, this error happens just after the usb module scans the bus. Listing by-label while in RAMFS shows the USB devices.
Also while in initrd environment:
[RAMFS /]# blkid
/dev/sda1: LABEL="BOOT" UUID="d71a5da8-fbdd-4ab9-ba5a-fa2adcda137b" TYPE="ext2"
/dev/sda2: LABEL="SWAP" UUID="3a437fef-b143-4626-a74c-2332d3a83470" TYPE="swap"
/dev/sda3: LABEL="SYSTEM" UUID="702e29ad-3f8a-4590-9c97-36a4f0b0262b" TYPE="ext4"
/dev/sda4: LABEL="HOME" UUID="2ef17520-7602-4855-acee-331535fdb0c7" TYPE="ext4"
/dev/sdb1: LABEL="USB-BOOT" UUID="3a563c48-850d-410a-afb9-bcd01ed567a5" TYPE="ext2"
/dev/sdb2: LABEL="USB-SWAP" UUID="980f4f7e-24a2-4347-8595-c61d8f72accf" TYPE="swap"
/dev/sdb3: LABEL="USB-SYSTEM" UUID="b6d09c53-aed8-494e-b017-df4c3c66b64b" TYPE="ext2"
lists all partitions, that is USB and hard drive, but attempting to manually mount sdbn (USB partitions) failed.
[RAMFS /]# mount /dev/sdb3 /new_root
mount: mounting /dev/sdb3 on /new_root failed: no such device
Regards,
Brian

[SOLVED] Arch won't start, uefi lenovo B570

Hi, i am trying to install arch on my lenovo B570 laptop. I downloaded the latest iso from the site and used usb universal installer to create usb install media. In the boot options of my laptop i pick the usb as the first boot device and run it. I can see the efi menu and i pick arch_x86_64, but it seems to me that gummiboot is not firing. After this i only see black screen, and the usb stops blinking. After a while (3-4 min) the lap-top restarts. In the options of my bios i can't find anything like secure boot option, i have read on the forum similar issues and someone said that this should be disabled, but i don't see any option like so. My bios is very primitive, there is only boot order to set and nothing else.
Thanks!
Last edited by stefo (2013-01-02 12:08:39)

I prepared the usb inside Lubuntu, i used gpadted to create new msdos partition table (mbr) and removed any partitions.
I created new partition FAT32 with label "ARCH_201212" and formated the drive. I created two folders inside /mnt, one "iso" and one "usb". I mounted the usb and iso like this:
mount /dev/sdb1 /mnt/usb
mount /home/stefo/Downloads/archlinux-2012.12.01-dual.iso /mnt/iso
Then copied everything from the iso to the usb:
cp -r /mnt/iso /mnt/usb
Unmounted and synced:
umount /mnt/{usb,iso}
sync
EDIT: I also tried with fdisk...
When i try to create new partition table with fdisk on my usb i get this:
Building a new DOS disklabel with disk identifier 0x601ad71e.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
EDIT: When i create new partition table and new FAT32 partition with fdisk, and then try to mount like this:
mount /dev/sdb1 -t vfat /mnt/usb
I get this, and the usb is not mounted:
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
dmesg | tail
[ 1678.604687] FAT-fs (sdb1): bogus number of reserved sectors
[ 1678.604696] FAT-fs (sdb1): Can't find a valid FAT filesystem
EDIT: My mistake sorry, i didn't used mkfs.vfat -F32 to format the partition, i forgot to do that
EDIT: When i try this, i get Permission denied:
sudo awk 'BEGIN {FS="="} /archisolabel/ {print $3}' /mnt/iso/loader/entries/archiso-x86_64.conf | xargs mkfs.vfat /dev/sdb1 -n
EDIT: I don't know why the previous command didn't worked but this one worked:
sudo mkfs.vfat -F32 -n `awk 'BEGIN {FS="="} /archisolabel/ {print $3}' /mnt/iso/loader/entries/archiso-x86_64.conf` /dev/sdb1
Just to check i open gparted and i can see my usb /dev/sdb, one partition sdb1 FAT32 label: ARCH_201212. I copied the content from the iso to the usb, unmounted both the iso and usb folders and sycned, and again i get black screen..
Last edited by stefo (2013-01-02 10:53:10)

Archiso x86_64 problem

Similar Messages

Maybe you are looking for