[SOLVED]Arch Linux / UEFI / BTRFS using Grub2 & Windows 8 in a 2nd HDD

PROBLEM:
====================================================================================
Dear fellas
I just purchased an new HP TouchSmart 17.3" laptop that comes with Windows 8.1 pro (1 tb HDD + small SSD for cache only ) and still have space for one more HDD or SSD.
I Google a lot and read a lot but many questions emerged since seems that no one has the same scenario (maybe I pick the wrong choices) like me.
The problem is.. I didn't wish to re-install Windows 8.1 since it came with from factory.. so I purchased a 750 gb hdd and put it into the free slot to install Arch Linux in a different HDD.
As I am not familiar with UEFI what I did was to reorder the hdds. I just put the Windows HDD as second disk and the new disk (For Arch Linux) as primary and changed into Bios from UEFI to compatibility mode and installed Arch Linux into the primary one.
I reaaaally need help to add to grub the correct "path" to Windows 8.1 disk that came with UEFI..
Anyone could please help me?
Thanks in advance!
====================================================================================
SOLUTION:
A huge thanks to @TheSaint and other users for their help and assistance!
More sources:
http://www.kossboss.com/linux---arch-in … -grub-boot
https://www.youtube.com/watch?v=METZCp_JCec#t=146
https://bbs.archlinux.org/viewtopic.php … 1#p1390741
Step by Step Summary:
Use gdisk to create partitions on /dev/sda:
    - 512MB - EF02 type partition (for EFI boot)
    - 690GB - Linux partition for the BTRFS.
- Create an EF00 (ESP) with 512mb
- Create a Linux System partition with the rest of space
Make the FAT 32 system for EFI boot:
# mkfs.vfat -F32 /dev/sda1
Make the BTRFS partition. If it complains about existing filesystems just add a "-f":
# mkfs.btrfs -L arch -f /dev/sda2
We will make out a root subvolume for sda1, this will be a folder called root located at the root of sda2. The way we will design this is that When the system boots we will not see /root, we will be inside root. Inside root you will have all of your etc,sys,proc,whatever folders etc.
# mount /dev/sda2 /mnt
# cd /mnt
# btrfs subvolume create /mnt/root
This should show you your root
# btrfs subvolume list -a /mnt
Something like this: ID 256 gen 5 top level 5 path root
# cd /
# umount /dev/sda2
Now we will mount sda2 root subvolume as /mnt and we will dump the arch system into there with pacman. We will also enable compress to utilize btrfs compress feature.
# mount -o defaults,compress=lzo,subvol=root /dev/sda2 /mnt
NOTE: the command "mount" will not show which subvolume is mounted, to see how subvolumes are mounted you need to look inside proc (cat /proc/self/mountinfo):
# cat /proc/self/mountinfo | egrep sda2
The line for the mount of sda2 looks like this:
43 21 0:34 /root /mnt rw,relatime shared:30 - btrfs /dev/sda2 rw,compress=zlib,ssd,space_cache
We can see that the subvolume /root is mounted to /mnt from the device /dev/sda3
Notice how with regular mount command its missing:
# mount | egrep sda2
/dev/sda3 on /mnt type btrfs (rw,relatime,compress=zlib,ssd,space_cache)
Pacman will dump stuff into a boot folder, so we better mount our sda1 EFI boot partition to it. Or else all of the boot stuff will go to sda3 instead of sda1:
# cd /
# pacstrap -i /mnt base base-devel
Let us create the directory and mount the EFI partition
# cd /mnt
# mkdir -p /mnt/boot/efi
# mount /dev/sda1 /mnt/boot/efi
Let us generate the FSTAB:
# genfstab -p /mnt >> /mnt/etc/fstab
Let us chroot into the arch installation:
# arch-chroot /mnt /bin/bash
Change password:
# passwd
Then pick the right one like this and associate it with a link to /etc/localtime
# ln -s /usr/share/zoneinfo/US/Pacific /etc/localtime
Let us generate the initial RAM disk
# mkinitcpio -p linux
Let us setup the bootloader (GRUB)
# pacman -Syu grub efibootmgr
Let us generate the grub configuration
# grub-mkconfig -o /boot/grub/grub.cfg
Let us install grub into the HDD
# grub-install /dev/sda
# umount -R /mnt
# umount /mnt
# reboot
From this step you can go straight and forward with the https://wiki.archlinux.org/index.php/Beginners%27_guide
Last edited by erickwill (2014-11-21 20:41:06)

TheSaint wrote:As UEFI BIOS is a boot loader itself. You should make on each HDD an ESP.
When you want to start win8 you go to BIOS and chose its entry, so will do for Arch the same.
For this way I suggest you write to boot the kernel directly from the BIOS. It just take some reading on this topic
Other option you set on you second ESP the boot loader of your liking and it will try to find win8 partition.
Thanks for your reply.
For the second option, may I use the compatibility mode and install the booloader into the first partition along with Arch?
Or in case the first option is still the better option, could you pleaaaase give me some directions from the scratch? Do you have Google Hangout?
Thanks in advance.
Last edited by erickwill (2014-11-18 19:54:26)

Similar Messages

  • [SOLVED]Arch Linux, and Windows 8.1 Dual Boot issue

    Hi guys. I recently bought a new laptop, and decided to run Arch Linux and Windows 8.1. I installed Windows 8.1 first as recommended by the beginners guide, and then installed Arch Linux. I made sure UEFI was enabled in my BIOS, and made sure everything was on a GPT partition. The install itself went fine. My laptop loads grub, and Arch Linux shows up and boots, but there is no option to boot into Windows 8.1. The only way I can boot into Windows 8.1 is by accessing my motherboard, and choosing to launch the windows boot manager instead of the grub launcher. How can I get Windows 8.1 to show up in grub? Thanks in advance guys.
    Last edited by Painguy (2014-08-20 20:19:37)

    Painguy wrote:
    -----------Edit------------------
    Yeah just ran this after installing os prober
    grub-mkconfig -o /boot/grub/grub.cfg
    and it works now. Sorry for the crazy posts guys. Thanks for the suggestions and help.
    Yeah I'm sure I'm doing something wrong lol. I did not install OS-Prober. I think that's where the issue is. I'm missing the menu entry in grub.cfg right? Do I just run os prober or do I have to manually edit grub.cfg.
    If that's not the case then here is what I did up until now. What I did was start with a blank SSD drive. I used cgdisk to make the disk use a GPT partitioning scheme. I installed windows 8.1 and checked in windows to make sure it boots into UEFI-GPT mode and it does.  I then installed arch linux using the beginners guide. I made sure to use cgdisk to create any extra partitions, and installed GRUB to the efi partition that windows had created ( I did not format this partition ). I then finished the installation and rebooted, and Grub only shows arch linux. I don't think I'm dealing with anything MBR related. I made sure I used the GPT partitioning scheme....i think lol.
    All you need to do is run os-prober then run grub-mkconfig. It should pick up Windows at that point.

  • [SOLVED]How to install Arch Linux UEFI to dual-boot?

    Hey,
    so I have a Lenovo G50-70 on which I want to have a Windows-Arch dualboot. I followed the Beginner's Guide, installed Arch but ended up with an inaccessible Windows. I could boot into Windows from the BIOS utility, but not from the gummiboot bootloader.
    The guide said if I wanted to dual-boot, I must leave windows EFI partition alone, which I did. I have my Windows partitions set up the Windows way, with the system reserved and EFI and recovery partitions, and I have my Windows partition of course and a data partition. After that I have some unallocated space, on which I made the Arch partitions, /dev/sda6 as an ESP partition for the EFI files, /dev/sda7 as root, /dev/sda8 as swap and /dev/sda9 as /home. The install process went without any error, then I made some configurations and installed dosfstools & efibootmgr. After that, I installed gummiboot and ran "gummiboot --path=/boot install". After that I created the configuration files exactly like in the guide, unmounted the partitions, rebooted and saw that there's no (easy) way getting into Windows. So my question is: how can I install Arch to have a working dual-boot system?
    Thanks for any help in advance!
    Regards, Matteussz
    Last edited by Matteussz (2015-02-11 20:41:37)

    Hey,
    Writing to you on my working dual-boot with ArchLinux (Windows 8.1 64-Bit, UEFI)
    So first step I've done is creating free space of an existing partition in the windows disk management (windows button and r and then type diskmgmt.msc). At this step, you have to record which partition your efi partition is (just take a look at your efi partition and remember the mb of this partition for later)
    Then go into the uefi settings (bios) and disable secure boot as well as fast boot, otherwise it could cause data crash.
    Boot your Arch Live CD and follow the beginners guide all the way along till you reach the disk management.
    If you want to have swap, you can create yours right now, should be a primary partition of about 4gigs.
    Next partition is gonna be your home, system partition (I've didn't created two partitions for home and for the system but you could do this as well as just go with one partition) this partition gonna be formatted in ext4
    Next step, you have to mount your windows-efi partition in /boot/efi but don't format it dont remeber if it asks you how to use the partition but if so, just use as fat32.
    After the disk management go ahead with your arch installation and follow the beginners guide. (Make sure you're using the grub bootloader)
    After finishing the installation, restart your system, hopefully you will recognize the opening grub menu. (but dont scare, windows wont show in the grub menu at this time so you have to boot your arch)
    Arrived in arch linux type the command
    grub-mkconfig -o /boot/grub/grub.cfg
    Reboot and your done with your Arch Linux, Windows 8 dual boot, hopefully

  • [SOLVED] Arch Linux install on UEFI motherboard (Asus UX31A)

    Hello all,
    I am new to Arch Linux (moving over from Mint) and I am having an enormous amount of trouble with booting for UEFI.  I go through all the command line installation steps and get to the step where you install and configure a bootloader.  I have followed everything step-by-step up and cannot seem to get anything to boot, I get the motherboard settings menu instead.  I've tried GRUB, rEFInd, and Gummiboot and all three have not worked for me.  Is there any hope for configuring a bootloader?  I am used to Mint/Ubuntu creating it for me.
    Thanks
    Last edited by somedood (2013-06-09 13:23:51)

    srs5694 wrote:It shouldn't matter from where you launch the EFI shell, although that will affect device names. If you boot a USB flash drive with an EFI shell on it, chances are fs0: will be the USB flash drive itself. Your rEFInd, though, should be installed on your hard disk, and therefore on another device -- probably fs1:, although it could be fs2:, fs3:, or some other number. If the only filesystem you can find is fs0:, then that indicates something is wrong with your hard disk setup -- perhaps your ESP's filesystem is damaged, or maybe there's something wrong with the partition table.
    I followed the steps in the beginners installation guide to create my file system starting with:
    cgdisk /dev/sda1
    I create 4 Linux filesystem partitions with this, then I run:
    mkfs.vfat -32 /dev/sda1
    mkfs.ext4 /dev/sda2
    mkfs.ex4 /dev/sda3
    mkswap /dev/sda4
    I then toggle the boot flag of my FAT32 formatted ESP (/dev/sda1):
    parted
    toggle
    1
    boot
    if it is not turned on according to the output of:
    parted
    print
    After that I mount the drives and turn swap on:
    mount /dev/sda2 /mnt
    mkdir -p /mnt/home
    mount /dev/sda3 /mnt/home
    mkdir -p /mnt/boot/efi
    mount /dev/sda1 /mnt/boot/efi
    swapon /dev/sda4
    I install my base system (without changing /etc/pacman.d/mirrorlist) by running:
    pacstrap -i /mnt base
    Finally I generate my fstab after the Arch installation:
    genfstab -U -p /mnt >> /mnt/etc/fstab
    I then check the fstab and I get the result from my previous post and according to the guide it is ok because everything but my root partition has a 0 or 2.
    somedood wrote:# /dev/sda2
    UUID=264fe719-b816-462d-af5b-1b76c73a875b     /     ext4     rw,relatime,data=ordered     0     1
    # /dev/sda3
    UUID=824c5b36-6bf3-4c66-8878-5c886dadc9dd     /home     ext4     rw,relatime,data=ordered     0     2
    # /dev/sda1
    UUID=49B1-AE7E     /boot/efi     vfat     rw,relatime,fmask=0022, dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro     0     2
    # /dev/sda4
    UUID=426143bf-0cb4-4b7e-8868-e82d6fe7bd8b     none     swap     defaults     0     0
    To clarify, sda2 and sda3 are my root and home partitions respectively, sda4 is my swap, and sda1 is my ESP.
    What could have gone wrong here?  This is quite frustrating to me and I really want to use Arch.

  • [SOLVED] Arch Linux Duke (2007) Fails to Boot

    Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
    I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch.  It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
    After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
    A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
    RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
    RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
    If you have read this far, you are a trooper.  Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
    :: Loading udev events                [Pass]
    :: Mount root Read-only
    :: Checking file systems
    This is where it stops.
    The next thing I see is:
    /dev/sda6
    The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
        E2fsck –b 8193 <device>
    I then get a sort of character based splash screen that says
    **********FILE SYSTEM CHECK FAILED ****************************
    *   Please repair manually and reboot. Note that the root file system
    *   is currently mounted read-only. To remount it read-write, type:
    *   mount –n –o remount,rw /.  When you exit the maintenance
    *   shell, the system will reboot automatically
    Give root password for maintenance
    At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
    /dev/sda6 on / type ext3 (rw)
    This is exactly the root partition that the start up complains about. It is clearly there.  I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
    At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
    Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
    # mknod “/dev/root2” b 3 6   
    (“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
    Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
    All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
    I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
    By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
    image = /boot/vmlinuz26
       root = /dev/sda6
       label = ArchLinux-Duke
       initrd = /boot/kernel26.img
       read-only
    I am stumped. Thanks in advance for any and all pointers you may be able to offer.
    Last edited by mac57 (2014-06-02 17:42:21)

    Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
    At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
    So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
    Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next.  This is my guess anyway.
    I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the  Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
    It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
    Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

  • [solved] Arch linux access point with multiple interfaces for the NAT

    Hi, I have a router running Arch linux. It is connected via LAN (let's call it eth0) to the internet. It has a second LAN interface, eth1, and a wireless interface in master mode, wlan0.
    Now, Everything works perfectly except providing network connectivity on eth1 and wlan0 simultaneously. I followed the guide in the "Internet share" wiki article and use dnsmasq/hostapd for the AP. It appears as if all traffic from the router is sent to the wlan0 interface, even if it came in through eth1 (for example, dhcp requests). I cannot really find information how to solve this. The words "bonding" and "iptables" are floating around, but there is not really an easy to understand tutorial for this.
    What do I need to do to use both the eth1 and wlan0 interface (for different clients!) on my router?
    Best regards, and thank you in advance
    Jan Oliver
    /e: This seems to be my problem: http://www.novell.com/support/kb/doc.php?id=7000318 How do I solve this using the usual iptables? (The way described in the article doesn't work: "RTNETLINK answers: No such process" errors.)
    Last edited by janoliver (2013-09-25 22:24:53)

    Or you could bridge eth1 and wlan0, and make dnsmasq bind/listen on that bridge...

  • [VIDEO TUTORIAL] Installing Arch Linux on GPT/LVM/GRUB2

    Hello everyone,
    I've recently switched over from running my machine on LVM with a MSDOS partition style, and I was tired of the limitations of it. Such as 4 primary partions or 3 primary and 1 extended. It was also hindering my flexibility since I had to make 1 primary partition that was /boot, which forced me to make an initram image if I wanted to put my / inside of the LVM. The only way I could truly fix all my problems was to move away from GRUB-Legacy (Which I love since it's so easy to configure) over to GRUB 2(Which is not as bad as I thought it was).
    I made this video to help people trying to do this combination. I also included the links to further information in the videos' description. It contains a link to GRUB 2 Architecture and moving over to GRUB (on IBM's site), and also ArchWiki resources for further reading.
    I hope you enjoy it.
    http://www.youtube.com/watch?v=69X9ZYA41xU
    After you finish doing this, you will end up with this style:
    GPT Partition Layout w/ Protective MBR.
    /dev/sda1 - BIOS Boot Partition
    /dev/sda2 - Linux LVM (arch is name of LVM)
    --> /dev/arch/boot - ext2
    --> /dev/arch/swap - swap
    --> /dev/arch/root - ext4
    --> /dev/arch/home - ext4

    As a complete newbie to partitioning on Linux I'd like to say how grateful I am to for making this.
    You've kept it clear, clean and simple which I appreciate.
    As most of my ventures into installing Linux is usually accompanied with a graphical installer a great deal of this is fairly alien. It could be nice to have a wiki entry just laying out a few examples for partitioning and setting up arch in various simple and exotic ways.
    Again, thank you for this contribution. (While I quickly transcribe the steps in your video and ready the 'man' command)
    Edit:
    Basic step by step transcription
    [root@archiso ~]# modprobe dm-mod
    [root@archiso ~]# dhcpcd
    [root@archiso ~]# pacman -Syy gptfdisk
    [root@archiso ~]# gdisk /dev/sda
    GPT fdisk (gdisk) version 0.8.1
    Partition table scan:
    MBR: not present
    BSD: not present
    APM: not present
    GPT: not present
    Creating new GPT entries.
    Command (? for help): [n]
    Partition number (1-128, default 1): [RETURN]
    First sector (34-[max], default = 34) or {+-}size{KMGTP}: [RETURN]
    Information: Moved requested sectory from 34 to 2048 in
    order to align on 2048-sector boundries.
    Use 'l' on the experts' menu to adjust alignment
    Last sector (2048-[max], default = [max]) or{+-}size{KMGTP}: [+32MB]
    Current type is 'Linux filesystem'
    Hex code or GUID (L to show codes, Enter = 8300): [EF02]
    Changed type of partition to 'BIOS boot partition'
    Command (? for help): [n]
    Partition number (2-128, default 2): [RETURN]
    First sector (34-[max], default = 67584) or {+-}size{KMGTP}: [RETURN]
    Last sector (2048-[max], default = [max]) or {+-}size{KMGTP}: [RETURN]
    Current type is 'Linux filesystem'
    Hex code or GUID (L to show codes, Enter = 8300): [8E00]
    Changed type of partition to 'Linux LVM'
    Command (? for help): [w]
    Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!!
    Do you want to proceed? (Y/N): [y]
    OK: writing new GUID partition table (GPT).
    The operaton has completed successfully.
    [root@archiso ~]# pvcreate /dev/sda2
    [root@archiso ~]# vgcreate arch /dev/sda2
    [root@archiso ~]# vgdisplay
    [root@archiso ~]# lvcreate -L 100M -n boot arch
    [root@archiso ~]# lvcreate -C y -L 1G -n swap arch
    [root@archiso ~]# lvcreate -L 10G -n root arch
    [root@archiso ~]# lvcreate -l 100%FREE -n home arch
    [root@archiso ~]# lvscan
    [root@archiso ~]# mkfs.ext2 /dev/arch/boot
    [root@archiso ~]# mkfs.ext4 /dev/arch/root
    [root@archiso ~]# mkfs.ext4 /dev/arch/home
    [root@archiso ~]# mkswap /dev/arch/swap
    [root@archiso ~]# /arch/setup
    Prepare Hard Drive
    3 Manually Configure block devices, filesystems andmountpoints
    Partition Access Method
    dev directly by /dev/* (most intuitive but devicefile names can change
    Manage Filesystems
    /dev/sda1 raw - 32MiB N
    /dev/mapper/arch-boot raw - 100MiB N > [IGNORE]
    /dev/mapper/arch-home raw - 91000MiB N > filesystem (re)created? [NO] > ext4 home
    /dev/mapper/arch-root raw - 10240MiB N > filesystem (re)created? [NO] > ext4 root
    /dev/mapper/arch-swap raw - 1024MiB N > filesystem (re)created? [NO] > swap
    Choose bootloader
    [SKIP]
    Configuration
    mkinitcpio > HOOKS="...lvm2..."
    DONE
    Exit
    [root@archiso ~]# mount -o bind /dev /mnt/dev
    [root@archiso ~]# mount -t proc /proc /mnt/proc
    [root@archiso ~]# mount -t sysfs /sys /mnt/sys
    [root@archiso ~]# chroot /mnt /bin/bash
    [root@archiso /]# dhcpcd
    [root@archiso /]# pacman-db-upgrade
    [root@archiso /]# pacman -Syy grub2-bios
    [root@archiso /]# grub_bios-install --boot-directory=/boot --no-floppy --recheck --debug /dev/sda
    [root@archiso /]# grub-mkconfig -o /boot/grub/grub.cfg
    [root@archiso /]# exit
    [root@archiso ~]# reboot
    login
    [root@host ~]# $EDITOR /etc/default/grub
    #GRUB_GFXMODE=auto
    #GRUB_GFXPAYLOAD_LINUX=keep
    #GRUB_COLOR_NORMAL="light-blue/black"
    #GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
    [root@host ~]# chmod -x /etc/grub.d/10_linux
    [root@host ~]# $EDITOR /etc/grub.d/40_custom
    menuentry "Arch Linux" {
    insmod lvm
    set root=(arch-boot)
    linux /vmlinuz-linux root=/dev/arch/root ro
    initrd /initramfs-linux.img
    menuentry "Arch Linux Fallback" {
    insmod lvm
    set root=(arch-boot)
    linux /vmlinuz-linux root=/dev/arch/root ro
    initrd /initramfs-linux-fallback.img
    [root@host ~]# grub-mkconfig -o /boot/grub/grub.cfg
    [root@host ~]# reboot
    Last edited by Earnestly (2012-01-09 11:51:45)

  • [SOLVED] Arch Linux on encrypted luks partition on USB key

    Hi
    I've installed Arch Linux on a USB key following this Wiki page: https://wiki.archlinux.org/index.php/In … _a_USB_key
    I also used dm-crypt as described in this Wiki page: https://wiki.archlinux.de/title/Festpla … iante_1.29
    I installed Arch Linux on the USB key using VirtualBox.
    To do that, I created a "rawvmdk":
    vboxmanage internalcommands createrawvmdk -filename ./usb.vmdk -rawdisk /dev/sdd
    Everything works fine when I'm trying to start the system within VirtualBox.
    Syslinux loads Arch using the following kernel command:
    APPEND cryptdevice=UUID=6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf:main root=/dev/mapper/main-root rw
    /etc/mkinitcpio.conf holds the following "HOOKS" configuration:
    HOOKS="base udev autodetect modconf block keyboard keymap encrypt lvm2 filesystems fsch resume"
    As already mentioned the configuration works within VirtualBox. When I'm trying to boot from the USB key on my real computer, I'm getting an error. Syslinux works fine and loads Linux, but Linux is complaining. Here's the log:
    :: running hoock [encrypt]
    Waiting 10 seconds for device /dev/disk/by-uuid/6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf ...
    ERROR: device '/dev/mapper/main-root' not found. Skipping fschk.
    ERROR: Unable to find root device '/dev/mapper/main-root'.
    You are being dropped to a recovery shell
    I'm not getting prompted for the passphrase since the cryptdevice can not be found. But why? It can be found when I'm booting within VirtualBox. What might be different? I successfully installed other Linux distributions (but without encryption and using GRUB as bootloader) previously within VirtualBox and was able to boot from the USB key on a real machine afterwards.
    Some additional information that might help:
    Here's the "lsblk -f output" for the stick:
    sdd
    ├─sdd1 ext4 usbboot bb45e84e-842e-4209-8c44-1af3c7933389
    └─sdd2 crypto_L 6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf
    When I'm running "lsblk" or "blkid" from the recovery shell after the failure, I'm getting no output. "ls /dev/sd*" returns nothing as well. The directory /dev/disk does not even exists in the recovery shell. (I'm not sure if this is normal or not.)
    Thanks for helping.
    Last edited by The Infinity (2014-08-14 20:26:06)

    I still haven't solved the problem:
    When starting the system on a machine with NVIDIA GTX 560Ti graphics card:
    - X doesn't start using startx or xinit and there are no log entries in /var/log/Xorg.*.log (as I haven't tried to start X).
    - I'm getting the message "Waiting for X server to begin accepting connections .. .. .. ..".
    - I already tried to uninstall xf86-video-nouveau and nouveau-dri with no effect.
    - Additionally: The "default terminals tty1/2/3/..." (which I'm using to start X) from have a poor resolution (I think 640x480 pixel).
    When starting the system on a virtual machine or a machine with an ATI Radeon (mobile) graphics card:
    - X starts and runs without any trouble the XFCE desktop environment.
    - Additionally: The default terminals have a proper resolution (I think the maximal resolution of the display).

  • [SOLVED] Arch Linux won't boot

    Hi,
    I was bad and didn't update my packages often enough, and now my arch installation on a desktop won't boot.
    I've booted off of a usb arch install, mounted all of the appropriate harddrive partitions, and used arch-chroot to switch to the offending hard drive.
    The /boot/syslinux/syslinux.cfg is such:
    # Config file for Syslinux -
    # /boot/syslinux/syslinux.cfg
    # Comboot modules:
    # * menu.c32 - provides a text menu
    # * vesamenu.c32 - provides a graphical menu
    # * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloa
    ders
    # * hdt.c32 - hardware detection tool
    # * reboot.c32 - reboots the system
    # * poweroff.com - shutdown the system
    # To Use: Copy the respective files from /usr/lib/syslinux to /boot/sysli
    nux.
    # If /usr and /boot are on the same file system, symlink the files instea
    d
    # of copying them.
    # If you do not use a menu, a 'boot:' prompt will be shown and the system
    # will boot automatically after 5 seconds.
    # Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
    # The wiki provides further configuration examples
    DEFAULT arch
    PROMPT 0 # Set to 1 if you always want to display the boot: prompt
    TIMEOUT 50
    # You can create syslinux keymaps with the keytab-lilo tool
    #KBDMAP de.ktl
    # Menu Configuration
    # Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
    UI menu.c32
    #UI vesamenu.c32
    # Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
    MENU TITLE Arch Linux
    #MENU BACKGROUND splash.png
    MENU COLOR border 30;44 #40ffffff #a0000000 std
    MENU COLOR title 1;36;44 #9033ccff #a0000000 std
    MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
    MENU COLOR unsel 37;44 #50ffffff #a0000000 std
    MENU COLOR help 37;40 #c0ffffff #a0000000 std
    MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
    MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
    MENU COLOR msg07 37;40 #90ffffff #a0000000 std
    MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
    # boot sections follow
    # TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel l
    ine.
    LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/md0 ro
    INITRD ../initramfs-linux.img
    LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=/dev/md0 ro
    INITRD ../initramfs-linux-fallback.img
    #LABEL windows
    # MENU LABEL Windows
    # COM32 chain.c32
    # APPEND hd0 1
    LABEL hdt
    MENU LABEL HDT (Hardware Detection Tool)
    COM32 hdt.c32
    LABEL reboot
    MENU LABEL Reboot
    COM32 reboot.c32
    LABEL off
    MENU LABEL Power Off
    COMBOOT poweroff.com
    and /etc/mdadm.conf is:
    ARRAY /dev/md0 UUID=3830049a:44459d91:3ad800a8:e77f102f
    ARRAY /dev/md1 UUID=a69afb27:1266d0c2:0c8966db:14500cdb
    ARRAY /dev/md2 UUID=20b0675c:2fcca1a5:0882d652:06324bf6
    ARRAY /dev/md3 UUID=3f0343cb:ff7342c9:fe8e73d4:ba6d61b3
    ARRAY /dev/md4 UUID=287c6b6d:8cbd733c:c6e9d285:a2b14814
    ARRAY /dev/md5 UUID=ccd0d21c:8103251b:2c9a32d1:bc6dcc78
    and it looks to me like this agrees with blkid:
    sh-4.3# blkid
    /dev/sda1: UUID="3830049a-4445-9d91-3ad8-00a8e77f102f" UUID_SUB="932acc3b-f7ba-d443-cf76-9d59b663c651" LABEL="archiso:0" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="9574bd41-8133-4c6a-b5b4-981002a41867"
    /dev/sda2: UUID="a69afb27-1266-d0c2-0c89-66db14500cdb" UUID_SUB="e3de7e2c-8153-0c53-ac5d-ffc678deb269" LABEL="archiso:1" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="fc78d66d-53a4-4c99-a29c-b881d19c1e8d"
    /dev/sda3: UUID="20b0675c-2fcc-a1a5-0882-d65206324bf6" UUID_SUB="36f53577-cd9b-0c4e-4223-58123a6b2426" LABEL="archiso:2" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="b7187772-bf01-4517-99a1-d2aa209aa35b"
    /dev/sda4: UUID="3f0343cb-ff73-42c9-fe8e-73d4ba6d61b3" UUID_SUB="e583cdb9-f523-b4ea-01bb-609779ca3efe" LABEL="archiso:3" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="df9fddd2-762b-4eb3-860c-ef79f545fa77"
    /dev/sda5: UUID="287c6b6d-8cbd-733c-c6e9-d285a2b14814" UUID_SUB="ec1c493a-97f0-48e2-1659-068c25b7aa55" LABEL="archiso:4" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="ba388b64-8f6b-4053-a695-14560832735e"
    /dev/sda6: UUID="ccd0d21c-8103-251b-2c9a-32d1bc6dcc78" UUID_SUB="9b53306f-941d-8048-5780-533ada837e11" LABEL="archiso:5" TYPE="linux_raid_member" PARTLABEL="Microsoft basic data" PARTUUID="6325add3-aa39-4fa2-995c-aacf7165097c"
    /dev/sdb1: UUID="3830049a-4445-9d91-3ad8-00a8e77f102f" UUID_SUB="ec3420f6-d21a-5e69-94f8-d81f277079ec" LABEL="archiso:0" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="9574bd41-8133-4c6a-b5b4-981002a41867"
    /dev/sdb2: UUID="a69afb27-1266-d0c2-0c89-66db14500cdb" UUID_SUB="4b1e7230-ffec-0985-1ac7-a69aec27eec2" LABEL="archiso:1" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="fc78d66d-53a4-4c99-a29c-b881d19c1e8d"
    /dev/sdb3: UUID="20b0675c-2fcc-a1a5-0882-d65206324bf6" UUID_SUB="4d1721b6-d87f-00b6-4bd9-45712592b033" LABEL="archiso:2" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="b7187772-bf01-4517-99a1-d2aa209aa35b"
    /dev/sdb4: UUID="3f0343cb-ff73-42c9-fe8e-73d4ba6d61b3" UUID_SUB="085a16ce-1a7c-d79e-eb92-fed6b1b70365" LABEL="archiso:3" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="df9fddd2-762b-4eb3-860c-ef79f545fa77"
    /dev/sdb5: UUID="287c6b6d-8cbd-733c-c6e9-d285a2b14814" UUID_SUB="10857018-548a-9311-178e-7d2b06e25942" LABEL="archiso:4" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="ba388b64-8f6b-4053-a695-14560832735e"
    /dev/sdb6: UUID="ccd0d21c-8103-251b-2c9a-32d1bc6dcc78" UUID_SUB="d577ff9e-a687-f335-7062-f2f629886a58" LABEL="archiso:5" TYPE="linux_raid_member" PARTLABEL="Microsoft basic data" PARTUUID="6325add3-aa39-4fa2-995c-aacf7165097c"
    /dev/sdc1: LABEL="/dev/sdc1" UUID="de2a5dc6-4b22-466f-819a-86dda839c7e6" TYPE="ext4" PARTUUID="c3072e18-01"
    /dev/sdc2: LABEL="/dev/sdc2" UUID="2909b560-e9b9-48cf-a194-7b7c9c38d312" TYPE="ext4" PARTUUID="c3072e18-02"
    /dev/md127: UUID="3f9ddf01-4f7c-4633-844d-82a1781170a5" TYPE="ext4"
    /dev/md126: UUID="7105ac32-610b-4d4b-935b-675edc71ff32" TYPE="ext4"
    /dev/md125: UUID="90cc6dbe-2d0f-422b-8653-965f103b8e8d" TYPE="ext4"
    /dev/md124: UUID="5fd8960f-6017-49c8-bc7e-c972aa0e2f31" TYPE="ext4"
    /dev/md123: UUID="7B9075B74838729A" TYPE="ntfs"
    /dev/md122: UUID="96468ceb-857b-467e-b9c7-2a37e13fde6f" TYPE="ext4"
    and lsblk is:
    sh-4.3# lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 931.5G 0 disk
    |-sda1 8:1 0 1G 0 part
    | `-md126 9:126 0 1024M 0 raid1 /boot
    |-sda2 8:2 0 24G 0 part
    | `-md122 9:122 0 24G 0 raid1 /
    |-sda3 8:3 0 15G 0 part
    | `-md127 9:127 0 15G 0 raid1 /var
    |-sda4 8:4 0 100G 0 part
    | `-md125 9:125 0 100G 0 raid1 /home/j3doucet
    |-sda5 8:5 0 100G 0 part
    | `-md124 9:124 0 100G 0 raid1 /home/c2hollow
    `-sda6 8:6 0 691.5G 0 part
    `-md123 9:123 0 691.4G 0 raid1 /media
    sdb 8:16 0 931.5G 0 disk
    |-sdb1 8:17 0 1G 0 part
    | `-md126 9:126 0 1024M 0 raid1 /boot
    |-sdb2 8:18 0 24G 0 part
    | `-md122 9:122 0 24G 0 raid1 /
    |-sdb3 8:19 0 15G 0 part
    | `-md127 9:127 0 15G 0 raid1 /var
    |-sdb4 8:20 0 100G 0 part
    | `-md125 9:125 0 100G 0 raid1 /home/j3doucet
    |-sdb5 8:21 0 100G 0 part
    | `-md124 9:124 0 100G 0 raid1 /home/c2hollow
    `-sdb6 8:22 0 691.5G 0 part
    `-md123 9:123 0 691.4G 0 raid1 /media
    sdc 8:32 1 58.9G 0 disk
    |-sdc1 8:33 1 19.5G 0 part /etc/resolv.conf
    `-sdc2 8:34 1 39.4G 0 part
    sr0 11:0 1 1024M 0 rom
    Everything looks fine to me, /dev/sda1 is /boot, which has the same UUID as what mdadm has for /dev/md0, which is what syslinux.cfg has been told to boot off of. I'm not sure what to do from here.
    Last edited by c2hollow (2015-01-02 00:43:56)

    It's long that Arch uses rw argument on kernel command line.
    You should correct your syslinux.cfg as follow.
    LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=LABEL="archiso:1" rw ## <<< Here's the diff
    INITRD ../initramfs-linux.img
    This isn't for the fallback menu entry, you just analyze the differences and do same there.
    I'm not familiar with syslinux, I just suppose you may try to test these options on-the-fly, before write them permanently. So when the syslinux menu will appear at boot time, please find the way to enter in edit mode and apply the correction. That will stay for the time you boot once. But it will ensure if it'll be good enough and do the writing later once you've booted.

  • [SOLVED]Arch Linux running inside GNOME Boxes.

    Hello,
    I wanted to create a vm using GNOME Boxes to run another Arch Linux installation (to test things and avoid to break my main system).
    I did a normal install, then installed gnome-shell and gdm from testing repos. I enabled gdm and NetworkManager and after reboot my box.
    The box don't boot. The main display only see early fsck lines (about /), I can see in the thubnail more lines but can't read messages.
    What is wrong here ?
    Regards,
    Fabien
    Last edited by fbourigault (2014-10-07 11:22:36)

    I can't read it it only show in the thumbnail. I posted here to known if I missed some package installation or if someone already had the problem and solve it !.
    EDIT:
    I installed a new box, using gnome from stable repositories. I installed the same packages but didn't enable anything. I'm starting services by hand to allow me do configuration in the box
    You can find the gdm log here : http://pastebin.com/R5ek3Xwy (full version with multiple failing runs :http://pastebin.com/fCsPxAvb)
    EDIT 2 :
    Problem solved by installing xf86-video-qxl from AUR ! This package should really be in official repos.
    Last edited by fbourigault (2014-10-07 08:41:32)

  • Arch Linux 32x64 bits, Developers and Window Managers Support

    Greetings!
    After having some time issues due to college that prevented me from this, I wish to have again a rolling-release distro in my computer.
    I was in the past a big fan of Gentoo, but now it seems too much work to compile everything from scratch. Also they seemed to have some issues with the developers - the original developer if I understood correctly has quit the project, others were forced to quit due to misbehavior, etc. - and maybe due to some other facts their popularity on distrowatch dropped drastically.
    Then this year I've tried Debian Testing... My goodness, that was messy. Tons and tons of bugs on XFCE, like thunar hanging on load and displaying error messages, gedit not removing the ~lock files properly on close, so I had the myfile and ~myfile, and many others. Really, I gave up.
    I wish to give Arch Linux I try then. Of course that would be quite stupid to ask if arch linux is the best choice in an arch linux forum, but there are some key points that if you could answer would help me a lot to give it a try:
    1. 32x64
    "Should I use 32-bit or 64-bit?" is NOT the intended question. Many still prefer 32-bit-pae on a 64-bit capable machine, others prefer 64-bit. I wish to use 64-bit. Made my mind. But I would like to know if the support of 64-bit on Arch Linux is as good as 32-bit and if it comes by default with cross-libs which makes me able to run 32-bit applications natively right out of the box,
    2. Developers
    About how many and what's their relation with the users? When I've googled for Arch Linux, I've had found a review video on youtube where some guy said in the comments that developer's mind changed a lot in the past 2 years and they introduced many buggy packages that required manual workaround. At the end of his comments, he said "Sympathy? Apologies for the ****? Nope. blame the user for trusting 'pacman -Syu'" Surely I don't know which are these options because I haven't read about pacman yet (just know it's the default package manager) but you get the idea.
    Another key question: Is Arch Linux hiring new developers over the time? Replacing the ones that leaves for the many reasons?
    3. Window Managers Support
    With Gnome3's overall rejection (including mine), we have only two options: Switch to KDE or try other Window Managers. I still wish to have faith on gtk, so the first option is still not considered by me. I don't wish to know "which one is the best", because that's another large discussion just as the 32-bit x 64-bit. Just how good is Arch's support (updated constantly? bug-fixes?) on:
    - XFCE
    - MATE
    - Cinnamon
    (Of course there are others like LXDE, Enlightenment, etc. but I've decided to narrow down to XFCE even having quite bad experiences on Debian Testing.)
    4. Package Manager
    Last, being a rolling-release dist, can I add an option for a specific package to install a specific older version and/or not upgrade when you tell the dist. to upgrade everything? I remember that back on Gentoo I could edit a text file and just type the version of the package I wished to keep and the "update everything" option wouldn't touch the package (worked also to try new versions that were still not stable enough).
    Any replies will be very appreciated. Sorry for the long post.
    Best regards.

    I'll start at the end with #4.  Of course on the arch forums you will get people who are biased towards liking arch - but I think if you ask in other communities you will regularly hear that arch's package management system is its greatest strength.  Pacman is the primary tool for this, but we also have makepkg for things in the Arch User Repository (AUR), and the Arch Build System (ABS) to recompile anything from the main repos with additional/alternate compilation options.
    But for your direct question, there is an option to only upgrade to a particular version of a given package.  There is an option in pacman's configuration file for just this purpose.  However depending on what the package is, this could lead to problems.  Users are discouraged from updating most of their system while keeping some older packages - This can lead to issues with shared dependencies.  Of course if you build the package from source (AUR or ABS) yourself, such issues would be easy to resolve.  Is there a certain package you know you'd want to keep at an older version?  If you tell us what it is, we can give more specific information on how easy/hard it would be to accomplish.
    #3: Arch is a DIY distro.  You choose whatever window manager / DE you want.  I can vouche for XFCE working wonderfully in arch.  There are also numerous archers who use mate and cinnamon.  I have heard of some problems, but (AFAIK) these have nothing to do with compatibility with arch, rather these are due to upstream issues.  In other words, cinnamon, mate, xfce, or any other WM should work just as well on arch as on any other distro.  I'd bet our wiki for installing and configuring those WMs are better than those of the distros that bundle the WM with the core install.  (In addition to package management, you will find the arch wiki is second to none).
    #2: I can't answer with any specifics - other than to say they continue to do an excellent job.  I am not surprised by the youtube video - not because I'd agree with it, quite the opposite.  But as arch is a DIY distro it puts some responsibility on the user to maintain their own system.  If one is not prepared for nor willing to do this, they often become frustrated and end up blaming someone else.  Often this is the developers, sometimes it is the forum moderators, other times it is the whole arch community.  In every case these accusations are absurd.  Your questions on replacement of developers is a good question though - there is a history page on the wiki which might give some insight on this, but I suspect others will have better input on this.
    #1: I use i686 (32bit) on two of my computers and it works perfectly.  It sounds, however, that a majority of the community uses 64bit (which I just updated to on one of my computers).  My 64bit system works perfectly as well, but I don't have any 32bit-only apps.  Occasionally there are forum threads about some issue or another with "multilib" applications which are 32bit programs run in a 64bit system.  Generally these threads seem to be resolved without much hassle.  You can search for some of them yourself: Skype seems to be a common topic of such issues.
    All in all, I'd reiterate arch's strengths in it's package management and wiki/documentation.  Potential weaknesses could be found by users who are unwilling or unable to take responsibility for their own system.  I word this is a bit biased manner - there are many people who have no interest in being responsible for maintaining their own system, a majority of all computer users would fall into this category; most of them would be quite unhappy with arch linux.  If you were happy with gentoo in the past and only want to avoid constant recompiling then you probably would be one who could be very happy with arch.
    Or an even shorter summary: try it out.  If you don't like it, switch.

  • [SOLVED] Arch Linux Guest Virtual Box OSE problem

    So I am installing my Arch Linux as a Guest in my Ubuntu partition, through Virtual Box OSE (3.2.8). I followed the wiki ( https://wiki.archlinux.org/index.php/Ar … lBox_Guest ) but still have an issue:
    sudo pacman -S kernel26-headers xorg gcc make
    sudo mount /dev/cdrom /mnt/cdrom
    sudo /mnt/cdrom/VBoxLinuxAdditions-x86.run
    But It fails on Shared folders, and cannot recognize X:
    :: Building the VirtualBox Guest Additions Kernel Modules [BUSY]
    :: Building the main Guest Additions module [DONE]
    :: Building the shared folder support module [FAIL]
    (Look at /var/log/vboxadd-install.log to find otu what went wrong)
    :: Warning: Unknown version of the X Window System installed. Not installing X Window System drivers.
    :: Installing graphics libraries and desktop services components [Done]
    /var/log/vboxadd-install.log states:
    /tmp/vbox.0/vfsmod.c:406:9: error: unknown field 'clear_inode' specified in initalizer
    /tmp/vbox.0/vfsmod.c:406:9 warning: initalization from incompatible pointer type.
    Which is strange, because as far as I know, clear_inode is part of the linux headers.
    Any idea why this is happening? Do I just need to update VirtualBox to a newer version?
    Last edited by gralamin (2011-03-11 18:22:14)

    Updating Virtualbox fixed the issue.

  • [Solved] Arch Linux in a Solaris branded Zone

    Hello,
    After having read this article at the Genunix WiKi, I 'd very much like to install Arch Linux (http://204.152.191.100/wiki/index.php/I … anded_zone) in a Solaris branded Zone.  However, the Arch Linux file to download is about two years old now, so I 'd like to roll one with a bit more recent kernel.
    I just wonder what might be the procedure to do so.
    a) Is it just unpacking the ISO inside the zone and let it enroll whilst booting?, or
    b) is it advisable to install the old package and upgrade from there?
    I am quite curious to learn how this works.
    TIA, Algey
    Last edited by algernonz (2011-11-28 18:42:31)

    Hi,
    it does indeed sound like an interesting little project. You should, however, revert to your procedure (a) and use one of the recent ISO images the Arch team has updated this year.
    Using that old tar will give you numerous headaches when trying to upgrade. Doing a simple upgrade from that old file will most probably break the system, thats why they took the effort to provide the new ones.
    Good luck.

  • [Solved]Arch Linux Gnome writing to usb disk destination is read only

    Hi
    i Have installed Arch Linux latest image 1-3-2015  not using Evolution Linux or any GUI installer
    i installed Arch Linux using command line
    i have gnome 3.14
    each time i try to write movie to usb flash or usb external hard disk
    the error says
    the destination disk is read only
    how to change this
    Last edited by belal (2015-04-04 20:58:54)

    I'm curious. Is the filesystem on the USB, ntfs ?
    If yes, did you install NTFS-3G ? https://wiki.archlinux.org/index.php/NTFS-3G. Happened to me 8 days ago .
    EDIT - Sorry for the repost using the same solution as my above post. Didn't see his link. Just surfed through the posts for the word "NTFS-3g" and it wasn't there.
    Last edited by newguy (2015-03-31 07:51:48)

  • [SOLVED] Arch Linux is zombie infested !!!

    Sigh !
    I don't know what happened but a few minute before when I rebooted my Arch Linux desktop, it started acting weird.
    First thing I do is to start my torrent client Deluge, look there was no icon in the tray for it but it was shown in System-monitor.
    Then I started Firefox, a few minute later the whole thing logged off. I renter my password and then again it logged of within one minute.
    So I rebooted to see if that changes this time, but this time I could see was that firefox was shown as ZOMBIE process and then when I tried to take the screenshot the system hanged
    Some thing I did today was
    Installed Yaourt
    Then installed nautilus-dropbox plugin
    Dropboxd service runs in background, so is there something fishy about the dropbox service. I tried to kill it but it again restarts.
    Please help me from zombie infestation, I am writing this from Ubuntu
    Last edited by visio159 (2008-09-14 08:41:47)

    No one replied !!! huh
    Well good news is that my RAM module needed a dust cleanup. Probably due to corrupt memory it was behaving bad.
    I am impressed that it (linux) logged me off when it detected that there were memory violation and corruptions to prevent any data damage ! Now can anyone explain this to me ? Is it really a feature or was just random occurring ?
    Case solved, learned a lesson too.
    Last edited by visio159 (2008-09-13 05:44:10)

Maybe you are looking for

  • Why does itunes say my sim card is not supported?

    i have an at&t iphone i just picked up from the apple store yesterday with original at&t sim card that was working until after i restored my phone.  This is the 4th iphone this has happened to in the last month. i wanted to restore my iphone 4 to fac

  • BOM Performance Analysis using SAT or SE30 t-code?

    Hi,     Currently I'm doing performance analysis of BOM to find out the bottlenecks. I'm doing the analysis using SAT or SE30 t-code. From my understanding, BOM performance depends upon 1. no. of BOM items 2. BOM Level 3. BOM Evolution over time Can

  • ATG+ CRS Error in ATGPublishing server, access not allowed to BCC

    Hi, After the installation of ATG 10.0.3 and Commerce Reference Store on Weblogic, using CIM, I started both ATGProduction and ATGPublishing without trouble. I can access the store (http://localhost:7003/crs/storeus) and dynamo administration console

  • Trigger invalidations, how to detect cause?

    Hello, is it possible to somehow detect what causes object(PKG/PRC/FNC/TRG) invalidations? Application users doesn't have righst to compile the object. After invalidation object can be again successfuly recompiled by ALTER XXX COMPILE; command. For e

  • HTML-Mail mit SO_OBJECT_SEND

    Hallo, kann man ueber SO_OBJECT_SEND eine Mail im HTML-Format versenden? Wenn ja, wie? Der Paramter object_type scheint mir ungeeeignet. Danke und Gruß Andreas