Trying to Install Arch PPC

Hi
I am trying to install Arch Linux PPC from the ISO on their site. I have run into a problem. When it comes to installing the packages I get and error about "key could not be looked up remotely" with different keys mentioned. I have tried changing the SigLevel  to Never in /etc/pacman.conf but this seems to get over written when I start the package install form the installer (/arch/setup). How can I get round this?
Thanks
Robert

Hi
Thank you for the reply and information. I have gotten further. I am now stuck at installing the boot loader. I get an error that says:
Unable to find OpenFirmware path for boot=/dev/sda2
Please add ofboot=<path> where <path> is the OpenFirmware path to /dev/sda2 to /etc/yaboot.conf
So I have Googled and that ofpath should give me this information. But I then get this error when I run ofpath /dev/sdb2:
Unable to determind controller path!
Am I doing the right thing to find out the OpenFirmware path? Is there anything else I can try?
Thanks
Robert

Similar Messages

  • [SOLVED] Trying to install Arch Linux from harddisk using /dev/sda2

    Hi
    I'm trying to install Arch using my swap partition, following this wiki entry: https://wiki.archlinux.org/index.php/Ha … stallation
    What I've done:
    Downloaded ISO: archlinux-2010.05-netinstall-i686.iso
    Command: swapoff /dev/sda2
    Command: fdisk /dev/sda and changed the system type to 83 (Linux) on /dev/sda2
    Now it looks like:
    Command (m for help): p
    Disk /dev/sda: 250.1 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00017e5b
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 1060289 530144+ 83 Linux
    /dev/sda2 1060290 3164804 1052257+ 83 Linux
    /dev/sda3 3164805 105579179 51207187+ 83 Linux
    /dev/sda4 105579180 488392064 191406442+ 83 Linux
    It complained about device was busy, but it still seemed to have changed the system type, so I did partprobe as it wrote.
    WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
    The kernel still uses the old table. The new table will be used at
    the next reboot or after you run partprobe(8) or kpartx(8)
    Syncing disks.
    [root@swamp ~]# partprobe
    <no output>
    Next I did:
    [root@swamp ~]# dd if=archlinux-2010.05-netinstall-i686.iso of=/dev/sda2
    327680+0 records in
    327680+0 records out
    167772160 bytes (168 MB) copied, 4.3025 s, 39.0 MB/s
    [root@swamp ~]# mkdir /mnt/sda2
    [root@swamp ~]# mount /dev/sda2 /mnt/sda2
    mount: warning: /mnt/sda2 seems to be mounted read-only.
    [root@swamp ~]# ls -al /mnt/sda2
    total 150466
    dr-xr-xr-x 3 root root 240 May 16 15:54 .
    drwxr-xr-x 6 root root 4096 Nov 5 01:40 ..
    dr-xr-xr-x 3 root root 556 May 16 15:52 boot
    -r--r--r-- 1 root root 448 May 16 15:54 isomounts
    -r--r--r-- 1 root root 8192 May 16 15:54 overlay.sqfs
    -r--r--r-- 1 root root 154058752 May 16 15:54 root-image.sqfs
    And unmounted it again.
    The wiki page says to type: fsck -f /dev/sda2fsck, but I get no such file while trying to open sda2fsck.
    [root@swamp ~]# fsck -f /dev/sda2fsck
    fsck from util-linux-ng 2.18
    e2fsck 1.41.12 (17-May-2010)
    fsck.ext2: No such file or directory while trying to open /dev/sda2fsck
    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>
    Can I ignore the above and continue modifying grub?
    Thanks :-)
    Last edited by valvet (2010-11-08 14:49:07)

    fsck -f /dev/sda2fsck makes no sense because /dev/sda2fsck is not a deivce. If the wiki says that, then it is wrong. It's only doing a fsck anyway so probably not really needed. If you are just formatting th swap partition then use, mkfs.ext{234}.
    edit:
    from the wiki
    # fsck -f /dev/sda2fsck 1.40.8 (13-Mar-2008)
    e2fsck 1.40.8 (13-Mar-2008)
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 3A: Optimizing directories
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    /dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
    /dev/sda2: 243/78936 files (8.2% non-contiguous), 310519/314880 blocks
    The first like should just be
    # fsck -f /dev/sda2
    Last edited by sand_man (2010-11-05 06:46:01)

  • Trying to install Arch on a SD card.

    I have an EEE PC 900 and was trying to install arch on a 32gb sd card.
    Every kernel I have tried so far boots then during bootup says it cannot find the root drive. 
    I tried changing the root delay but that didn't work.  So far I tried the defalt kernel and toofisnes's kernel and both came up with the same error.
    Can anyone help point me in the right direction?

    keenerd wrote:Did you enable USB booting when installing the kernel?
    redsteakraw wrote:my bios can boot from the SD fine. Grub also boots fine off of the sd card.  I ran the arch installer from a usb thumb drive. and II am currently running knoppix off of a SD card.
    Good.  Glad to hear that your motherboard supports usb boot.  However, you did not understand my question.
    Think back to when you installed Arch  And it asks if you want to boot from an encrypted/RAID/LVM/USB/etc root partition?  That USB option is pretty important.  (Post-install it is one of the mkinitcpio hooks.)  Without it, your kernel will not have the drivers to read your root partition.
    Reinstall from the Arch iso.  When you get to the kernel step, it will ask "Do you want to boot from USB?"  Select "yes".

  • Trying to install Arch Linux on a HP-dv2000 laptop

    I am able to start up from, the CD no problem. I get the Arch Linux menu. What I think is the problem is maybe a resolution issue because as I go to install it, the screen looks wonky and I can't see the command line properly. I know when I install Ubuntu for example, the installation screen looks off to one side. Only after installing the nvidia driver after successfully installing Ubuntu does the screen look the way it supposed to.
    I think the same think is happening here when trying to install Arch Linux. Any suggestions on how I can resolve this? This is a big deal for me because for the first time, I think I am going to learn a ton of stuff about Arch Linux. I am willing to take the plunge following the beginner's guide along the way.
    Thanks for the help!!

    ArchLinux is designed to run whether in VirtualBox or on a real machine. 
    If you have a TV connector plugged in it will chop some regular lines at the bottom to make up for the difference in TV resolution.
    There are a couple of packages related to nvidia hardware, nouveau is one of them.  Just do a pacman -Ss nvidia for possibilities of things you might need to install.  Your nvidia hardware is a little newer, so probably nvidia is the package you'll need instead of nouveau. 
    Are you using X?  When you install the proper xf86-video-* driver it shouldn't have any problems with X.  If modesetting is turned off, then some resolutions may not be made available (especially in Gnome), so it is best to keep it turned on if at all possible (kernel default).
    Last edited by nomorewindows (2012-03-12 17:19:55)

  • Trying to install arch

    well a while ago I tried installing arch but then gave up on it since I have limited bandwidth and cannot download large packages like GNOME at anytime but now i wanna try again. So i setup my system to install on an external hard drive. I configured all the files and installed the packages but when I went to set the root password i got a bunch of errors i think saying:
    /arch/setup: line 1406 : 30000 Segmentation fault chroot ${DESTDIR} passwd root
    arch/setup: line 1406 : 30000 Segmentation fault chroot ${DESTDIR} passwd root
    arch/setup: line 1406 : 30000 Segmentation fault chroot ${DESTDIR} passwd root
    arch/setup: line 1406 : 30000 Segmentation fault chroot ${DESTDIR} passwd root
    with the 300000 going from 1-about 40000 in a few seconds. it has been doing this for a few mintues waht is the problem? any solution?

    Hi
    Thank you for the reply and information. I have gotten further. I am now stuck at installing the boot loader. I get an error that says:
    Unable to find OpenFirmware path for boot=/dev/sda2
    Please add ofboot=<path> where <path> is the OpenFirmware path to /dev/sda2 to /etc/yaboot.conf
    So I have Googled and that ofpath should give me this information. But I then get this error when I run ofpath /dev/sdb2:
    Unable to determind controller path!
    Am I doing the right thing to find out the OpenFirmware path? Is there anything else I can try?
    Thanks
    Robert

  • Trying to install Arch with Ubuntu hardy already installed

    I have Ubuntu already installed on my system and I want to install Arch on a separate 10gig partition ( which is already made) but when I boot from the Arch cd and go to install Arch only sees the main drive it doesn't see anything else what am I doing wrong. I only want to install arch on the 10 gig partition for now until I am more familiar with Linux
    Last edited by Shadowmeph (2008-05-20 17:35:28)

    I have just read that  it is informative but I am not sure of what that will do inorder for me to be able to install Arch on My tem gig partition, when I am in ubuntu I stat gparted to see what the names of my partitions are and this is what it shows /dev/sda3 swap     1gig /dev/ sda2 reiserfs 10 gigs ( where I want to install Arch)  sda1 / Ubuntu how do I install arch onto dev/sda 2 ) the ten gig partition) if arch doesn't see it? do I have to delete the partition or formaste the 10 gig partition differently? I am pretty new to Linux so I am not sure of how to do this.
    this is what my grub looks like
    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 3
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    hiddenmenu
    # Pretty colours
    #color cyan/blue white/blue
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    # examples
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ## kopt_2_6_8=root=/dev/hdc1 ro
    ## kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=18573b0e-4906-4c7f-8e32-b544fd854ab5 ro
    ## Setup crashdump menu entries
    ## e.g. crashdump=1
    # crashdump=0
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,0)
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ## alternative=false
    # alternative=true
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ## lockalternative=false
    # lockalternative=false
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ## lockold=true
    # lockold=false
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ## altoptions=(recovery) single
    # altoptions=(recovery mode) single
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ## howmany=7
    # howmany=all
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ## memtest86=false
    # memtest86=true
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    ## ## End Default Options ##
    title Ubuntu 8.04, kernel 2.6.24-16-generic
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.24-16-generic root=UUID=18573b0e-4906-4c7f-8e32-b544fd854ab5 ro quiet splash
    initrd /boot/initrd.img-2.6.24-16-generic
    quiet
    title Ubuntu 8.04, kernel 2.6.24-16-generic (recovery mode)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.24-16-generic root=UUID=18573b0e-4906-4c7f-8e32-b544fd854ab5 ro single
    initrd /boot/initrd.img-2.6.24-16-generic
    title Ubuntu 8.04, memtest86+
    root (hd0,0)
    kernel /boot/memtest86+.bin
    quiet
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    ok edit two I think that I have Arch install but I am not sure of which way to use
    Dual booting with other linux distros
    This is done exactly the same way that Arch linux is loaded. Here we assume that the other distro is on partition [s/h]da3.
    title Other Linux
    root (hd0,2)
    kernel /boot/vmlinuz (add other options here as required)
    initrd /boot/initrd.img (if the other kernel uses/needs one)
    [edit] Dual booting with other linux distro (Chainloading)
    To avoid maintenance nightmare, you might want to chainload the GRUB in the MBR to another bootloader you might have installed in the bootrecord of a partition [(hd0,2) in our example] instead of the MBR. This way the auto-magic stuff of some distro will manage the menu.lst on (hd0,2) (if it is grub) for its own distro and you will boot with all the option needed (like the correct last kernel) without the need to copy/paste some part of that menu.lst into yours.
    In our example [1], GRUB is in the MBR and some other bootloader (BL) (be it grub or lilo) is in the Boot Record of (hd0,2).
    |   |           |           |    %   (hd0,2)     |
    | M |           |           | B  %               |
    | B |  (hd0,0)  |  (hd0,1)  | L  %  Other        |
    | R |           |           |    %  Distro       |
    |   |           |           |    %               |
      |                            ^
      |     chainloading           |
    Then, you simply use in your menu.lst:
    title Other Linux distro
    root (hd0,2)
    chainloader +1
    Last edited by Shadowmeph (2008-05-20 17:56:20)

  • Trying to install arch but have a problem please help!

    So I'm trying to install archlinux on my laptop but when I boot of of my flash drive it says
    syslinux 4.07 EDD 2013-07-25 Copyright (C) 1994-2013 H. Peter Anvin et al
    Unknown keyword in configuration file: PATH
    boot/syslinux/whichsys.c32: not a COM32R image
    boot:
    Can someone PLEASE tell me what I'm doing wrong?

    You're not telling us how you created that bootable flash drive.  You're also not using a reasonable title for your thread.  Please revise the title to give an indication on what the problem actually is.

  • Cfdisk error, trying to install Arch

    When it comes to partition my HDD i have one 500GB partition containing Windows, and 500GB free space, yet when i come to manually set up the partitions using cfdisk i get this error:
    FATAL ERROR: Bad primary partition partition ends in the final partial cylinder
    This stops me from continuing the install all together as i can't set up a partition...
    The output of fdisk -l shows everything looking fine except i get this error:
    Partition 2 does not end on cylinder boundary.
    I am trying to set up a partition through an Ubuntu live CD with Gparted so we will see how that goes, but in the mean time does anybody have any idea what is causing this or a way it can get solved?
    Thanks a lot

    Greetings,
    I ran into this issue when setting up my wife's new laptop. It came with windows 7, which she hated, having found linux mch easer for her to use. So She asked me to setup arch linux on her machine, and completely wipe out windows 7.
    Well for some reason windows 7 is set up with an invisible partition. cfdisk seems unable to see this partition, and it completely throws it off. Using gparted (on a puppy linux disk I had laying around) was my way around the partitioning issue.

  • USB Errors while trying to install 64 bit Arch

    I'm trying to install Arch onto some brand new hardware. I am installing using the Arch Netboot environment.
    When I try to install 64 bit Arch, I get the following errors straight after archiso.img is downloaded and the kernel is booted:
    usb 2-5: device descriptor read/64, error -32
    usb 2-5: device descriptor read/64, error -32
    usb 2-5: device descriptor read/64, error -32
    usb 2-5: device descriptor read/64, error -32
    usb 2-5: device not accepting address 4, error -32
    usb 2-5: device not accepting address 5, error -32
    hub 2-0:1.0: unable to enumerate USB device on port 5
    The same lines appear for usb 4-1, 6-5 and 7-1. The only USB device that is plugged in is the USB key that I booted ipxe.lkrn from.
    Googling seems to point to a kernel module that needs to be loaded earlier or a faulty USB controller. I do not know how to change what kernel modules are used during installation, and I'm fairly certain the USB controllers are fine. Its a brand new motherboard and I can access my USB key fine (I can boot from it) in any of the available USB ports.
    I was close to giving up until for some reason I decided to try and install the 32 bit version of Arch instead. This worked as expected and I am sent to the archiso installation prompt without seeing any of the same USB errors.
    Can someone please assist me with this? I would really prefer to have the 64 bit version installed.

    https://bbs.archlinux.org/viewtopic.php?id=158206
    This seems to be related, although my errors are giving error -32 instead of -110.
    Is there a way I can force the installation environment to use kernel 3.7.6? Does the 32 bit installer use a different kernel to the 64 bit installer?
    Is there a way I can use the 32 bit installation environment to install 64 bit as well as the 3.7.6 kernel?

  • Arch PPC, a G4 and a Saturday

    I had some spare time Saturday. Well, actually, I had plenty of stuff
    to do, I just did not want to. I was sitting at my desk thinking of
    anything that I could be doing besides what I should be doing
    A shiny box in the corner of my office caught me eye!
    I have two Apple G4 machines, both are 450MHz (Don't be a hater!)
    My oldest son has one that he plays around with. It has OSX on it.
    The other one was sitting in the corner of my office here at home.
    It had OSX on it also. But it was not being used at all.
    Trying Arch PPC on the G4 had been a plan for a while. The time to try
    it had come. It was placed on "the rack". The shiny G4 was going to be
    a file server!
    The install went very well, and quick. There were only two hangups.
    If I had taken the time to read before installing, the first problem would not
    have been a problem at all. It was the issue with OpenSSH requiring heimdal.
    And heimdal being in extra and not in core.
    The second problem was after the install. The G4 was rebooted and I
    was greeted with a screen full of scrolling text.
    DEFAULT CATCH, code=300 at %SRR0:...
    There was more on the line that I do not remember. That line looped
    forever. My official opinion was "that ain't right". A Google search told
    me that it might be trying the wrong partition and I needed to boot into
    OpenFirmware (OF) and make it manually boot the correct partition.
    Getting in OF was a challenge. Googling for ways to get into it gave
    plenty of hits. After many failed attempts, I finally got in and told it
    what to boot (boot hd:3,yaboot) and Arch PPC was running!
    I had read that running "ybin" would fix the booting error. When the
    system was fully up, ybin was ran. Then the system was rebooted and it came up
    the way it should!
    Then OpenSSH, Samba, ProFTP, and lighttpd was installed.
    The total time it took, from start to finish, was under 45 mins.
    Remember the stuff that I was trying to avoid doing? There was still
    time left to do those things. Not good   I needed to kill more time.
    Why not add X and e17? Although neither of those would be
    used much, if ever, on a file server. So what! I want to see how it
    does with X running.
    I installed X, firefox, thunar, terminal, x11vnc and e17.
    I added 3 more HDs. Now there is a little over 1TB in the G4.
    When everything was installed, startx.
    The screenshot shows the CPU at 7%. That is not accurate. On average,
    with X and e17 running, the CPU stays near 50%. X wont be used anyway.
    The box will run headless. Without X running, the CPU stays at about 1%.
    The G4 was placed in the location it will remain. Booted up (no X.)
    Everything was tested, everything works.
    All that added about 40 mins onto the time (e17 had to be compiled.)
    And I still had plenty of time to mow the lawn

    I'd buy that shirt!
    Also: nicely done! I thought about installing Arch PPC on my iBook but then again, I'd miss Textmate. Maybe on a second partition ... later.
    Last edited by mucknert (2008-05-13 11:56:45)

  • Arch PPC failure on yaboot

    Today i installed arch-ppc on an iBook G4 (ppc).
    It seems that the installation was fine until the yaboot process, i got some problems related to of paths, after 'googling' about yaboot i installed it manually. My problem now is that when i boot the laptop i got the yaboot menu selection ('l', 'x' or 'c'), but choosing 'i' or 'x' gives me a blank white screen and the systems seems to be hung.
    Now to boot macosx i need to press 'alt' key when booting and choose the macosx folder, or to move directly the MacosX partition before the Bootstrap one (where yaboot was installed).
    I can´t try my arch system becouse i can´t boot into it.
    These are my yaboot.conf and my partition scheme:
    yaboot.conf:
    boot=/dev/sda2
    device=/disk@0:
    partition=6
    delay=10
    timeout=40
    install=/usr/lib/yaboot/yaboot
    magicboot=/usr/lib/yaboot/ofboot
    macosx=/dev/sda4
    enablecdboot
    image=/boot/vmlinux26
            label=Linux
            root=/dev/sda6
            initrd=/boot/kernel26.img
            read-only
            partition=6
    Partition scheme:
    /dev/sda1    Apple_partition_map   Apple                    Partition map
    /dev/sda2    Apple_Bootstrap          bootstrap              NewWorld bootblock
    /dev/sda3    Apple_Boot                  eXternal booter    Unknow
    /dev/sda4    Apple_HFS                  Apple_HFS_1      HFS  <--- partition with main volume for macosx
    /dev/sda5    Apple_HFS                  Apple_HFS_2      HFS
    /dev/sda6    Apple_UFS                  Apple_HFS_3      Unknow   <--- partition with linux
    /dev/sda7    Apple_Free
    /dev/sda8    Apple_Free
    /dev/sda9    Apple_Free
    Does anyone have any clue about what is happening and how could i solve this?
    Thanks in advance.
    Last edited by atuin (2010-11-03 01:24:04)

    I tried messing around inside of OpenFirmware but was unsuccessful. I also tried uploading a patched copy of ofboot to my machine as a replacement for the faulty one. I replaced /disk@0: in my yaboot.conf file with hd: (for both the device and ofboot lines). Neither of these strategies worked out for me.
    Would you mind giving the commands you used to solve the problem?
    Edit: Nevermind, apparently my kernel did not install properly, and that's why Yaboot didn't see it.
    Last edited by dmitri (2010-12-18 03:12:50)

  • Installing Arch on Asus Eee, Already Read the Wiki [Solved]

    I'm attempting to install Arch on my Asus Eee 701 (4GB SSD model) and I made a mistake that I'm having trouble correcting.  First, I accidentally wrote the image to my Eee's SSD, instead of my USB drive.  I tried to install Arch with the installer on my SSD, set up the partitions (one for /, one for /boot, and one for /home), but when I issued the command, it told me that the disk was in use.  It was then that I realized what I did.  I used an Ubuntu LiveCD on another computer to burn the image file again, this time to my USB drive.  I booted my Eee from the USB drive and tried to partition my SSD again, but this time, it tells me:
    Device or resource busy
    This disk is currently in use - repartitioning is probably a bad idea.
    Unmount all file systems, and swapoff all swap partitions on this disk.
    Use the --no-reread flag to suppress this check.
    Use the --force flag to overrule all checks.
    When I boot from my SSD, I get the same message, so I'm not even 100% certain that I booted from my USB drive before.  My USB drive's activity light was on though.
    Is there any way to fix this?  Also, given that I have an SSD, what partitions should I set up and how big should they be?  I can't find any concrete numbers in the wiki.
    Thanks in advance for the help.
    Last edited by Tyrian (2008-11-17 04:14:23)

    I'll try that, thanks.  What would happen if I dismounted the SSD with -f if it was in use?
    EDIT:  I just realized that when I go into the installer, it lets me set up partitions manually (I run the installer, pick "Prepare Hard Drive", "Partition Hard Drives", "/dev/sda").  But how should I set them up?  When I test it by just making one 4GB partition, it tells me, "Wrote partition table, but re-read table failed.  Reboot to update table."  So I rebooted, and it appears to work.  So I deleted that partition, made a 512MB one, rebooted, and repeated until I had 3 partitions in ext2, a 512MB (sda1, bootable), 512MB (sda2), and one roughly 2.5GB (sda3).  I then went to "Set Filesystem Mountpoints", said "NONE" for the swap (due to the avoiding pitfalls section of the wiki), picked "/dev/sda1" as "/" in ext2, made "/dev/sda2" as ext2 called "/var", and made "/dev/sda3" in ext2 called "/home", then said "DONE".  When I say "Yes" as the confirmation prompt, I get this message:
    Error creating filesystem: mke2fs /dev/sda1
    I hit enter and get dropped back to the "Prepare Hard Drive" menu.  I followed this section of the Beginner's Guide too.
    Is there any way to fix this?
    Last edited by Tyrian (2008-11-15 18:37:10)

  • Impossible to install arch in UEFI mode on my Acer Aspire S3-391

    Hi there,
    I am trying to install arch-linux on my Acer Aspire S3-391, which came with a pre-shipped Windows 8. I am trying to make a dual boot, so I would like to keep the UEFI mode at startup. However, my computer won't boot on the Arch Linux USB Flash drive when in UEFI mode : when plugged in, the key prevents the computer from loading anything. The "Acer" page keeps on reloading itself, without even letting me access the BIOS menu (In other words, the computer is blocked at "POST" phase when the installation media of arch is plugged in).
    Here's what I did to try and solve the problem  :
    1) of course, I disabled Secure Boot and hibernation in Windows 8.
    2) tried to boot in legacy bios. It works, and i could install arch this way : but as told before, i would like to install it in UEFI mode.
    3) Checked, re-checked and re-rechecked the installation media.
    4) tried to install Ubuntu in UEFI mode. It worked : the bootable key of Ubuntu was loaded, when the bootable key of arch is blocked. Why ? No idea...
    5) Installed Ubuntu, and tried to install Arch in UEFI mode from Ubuntu, following the tutorial "Install_from_Existing_Linux". No luck here : i was blocked at step "Testing if you are booted into UEFI mode" on the beginner's guide : I was not, and I couldn't find any solution in the tutorial.
    Any suggestions on what I should try next ?

    If you've already installed in BIOS/CSM/legacy mode, my recommendation is to install your EFI-mode boot loader and try it out. You'll need to use something else that does boot (such as Ubuntu), install the boot loader using the Windows bcdedit command (assuming you're dual-booting), or install the boot loader as EFI/BOOT/bootx64.efi (if you're setting up for Linux alone) to get it to work, though.

  • Installing Arch on a MacBook Pro Retina

    I've spent many hours trying to install Arch on my macbook pro to no avail (over 14 times I've tried), I've learned a lot through this process, but apparently not enough. I get the system installed and blessed (in OSX), but when I try to boot into it I get stuck on "loading initial ram disk." (Previous errors were a read-only file system, but this one is latest) My hunch tells me it has something to do with the mkinitcpio.conf (I was told to add "ahci" to MODULES and "keyboard" after "autodetect" in "HOOKS") and I know the mkinitcpio -p linux command creates the initial ram disk environment (thanks to the docs).
    Here are my steps, the bash scripts I created to do all this. Does anything look out of the ordinary to anyone?
    cgdisk /dev/sda #(setup partitions as below, sda1-3 not shown)
    #partitions: (sda4 == 128MB Hfs+, sda5 == 256MB Linux (boot), sda6 == 30GB Linux (root), sda7 == 70GB #Linux Home)
    #first script
    mkfs.ext2 /dev/sda5
    mkfs.ext4 /dev/sda6
    mkfs.ext4 /dev/sda7
    mount /dev/sda6 /mnt
    mkdir /mnt/boot && mount /dev/sda5 /mnt/boot
    mkdir /mnt/home && mount /dev/sda7 /mnt/home
    pacstrap /mnt base base-devel
    genfstab -p /mnt >> /mnt/etc/fstab
    arch-chroot /mnt /bin/bash
    #second script
    #install wifi (dmesg | grep firmware still says no firmware tho...)
    pacman -S wget b43-fwcutter
    wget https://aur.archlinux.org/packages/b4/b … are.tar.gz
    tar -zxf b43-firmware.tar.gz
    cd b43-firmware
    makepkg -si --asroot #kosher?
    rmmod b43 && modprobe b43
    echo arch > /etc/hostname
    ln -s /usr/share/zoneinfo/US/Central /etc/localtime
    hwclock --systohc --utc
    useradd -m -g users -G wheel -s /bin/bash dmj && passwd dmj
    sudo pacman -S sudo
    nano /etc/sudoers #comment out wheel portion
    sudo nano /etc/locale.gen #pick locale
    locale-gen
    echo LANG=en_US.UTF-8 > /etc/locale.conf
    export LANG=en_US.UTF-8
    mkinitcpio -p linux #someone said i need "ahci" in modules?
    #make boot loader, copy to usb
    pacman -S grub-efi-x86_64
    grub-mkconfig -o boot/grub/grub.cfg
    grub-mkstandalone -o boot.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg
    mkdir /mnt/usbdisk && mount /dev/sdc1 /mnt/usbdisk
    cp boot.efi /mnt/usbdisk/
    umount /mnt/usbdisk/
    sudo pacman -S dialog wpa_supplicant iw
    exit
    umount /mnt/home
    umount /mnt/root
    umount /mnt/
    sudo reboot
    I finally got a descriptive error message and am very excited to show everyone.
    https://dl.dropboxusercontent.com/u/10021156/arch.jpg
    Moderator Edit:  Converted over sized in-line picture to link - ewaller
    Last edited by dmj (2013-06-25 02:59:00)

    Ok, so I managed to boot into arch. The issue was my fstab. The custom settings I was using were incorrect. Going with the defaults helped. Also, the version of grub I was using was broken. See this link for the fix: https://bbs.archlinux.org/viewtopic.php?id=164101
    So after I tar -xvJf xxx.tar.xz the fixed version I was able to generate a boot.efi, copy it onto the 128MB HFS+ on OSX and then bless and boot.
    A whole new slew of errors occurred.
    First, the video mode error occurs "No suitable video mode" (and something about a font).
    I found a fix for it here: (but it didn't work) https://wiki.archlinux.org/index.php/GR … d.22_error
    I added
    cp /usr/share/grub/unicode.pf2 ${GRUB_PREFIX_DIR}
    Then add:
    UEFI systems:
    insmod efi_gop
    insmod efi_uga
    After that add the following code (common to both BIOS and UEFI):
    insmod font
    if loadfont ${prefix}/fonts/unicode.pf2
    then
        insmod gfxterm
        set gfxmode=auto
        set gfxpayload=keep
        terminal_output gfxterm
    fi
    Gist: Add these few lines to your grub.cfg, result: no luck still this error
    What I'm not sure is if if this is affecting my ability to start the xorg-server.
    Then after that the network became unreachable (which is strange because the ethernet worked ootb on install)
    systemctl enable dhcpcd@enp0s10
    systemctl start dhcpcd@enp0s10
    allows me to ping -c 3 google.com
    Lastly, I cannot start the xorg server. Says the nvidia module is bad. I installed bumblebee, and ran startx (not from root) and I get a black screen. This is after installing: xorg-server xorg-xinit xorg-server-utils xf86-input-synaptics nvidia acpid
    Then running: systemctl enable acpid nvidia-xconfig
    My graphics card is a Geforce 650M and I've read I should be using the nvidia module, not the open source noveau module.
    startx just boots into a blank screen now and I'm unsure why.
    Any speculations, ideas, or thoughts would be gladly welcome.
    Thanks ahead of time!
    Last edited by dmj (2013-06-26 03:05:26)

  • Install arch on emachine laptop

    Hello,
    Here is my problem. I am trying to install arch on an emachines amd64 laptop. The 0.6 install disc boots a working 2.6 kernel from which I can get networking started. If I then install a 2.6 kernel, it freezes loading the kernel at the point where the dmesg says: "NET" Registered protocol family 2". If I install a 2.4 kernel it will boot fine after adding acpi=off and agp=try_unsupported parms. However, I cannot get networking to work with the 2.4 kernel. The modules will load but I will always timeout during network start. I've run network start using bash -x and I am getting the correct parms to dhcpd. It just doesn't want to work. So my question is this. How do I get a 2.6 kernel to boot? I know it will work because install uses it. Is there a way to use the install kernel? Should I try to build a kernel during install and how do I do this?
    Thanks,
    Jason

    Ok, Got the 2.6.3 kernel working. There is an excellent resource here.
    The 3 things which helped me were:
    1.) Using the config file listed on the page linked above as a basic guide.
    2.) Using ext3 as my filesystem.
    3.) Adding "pci=noacpi noapic psmouse.proto=imps" to my kernel boot parms.
    Also on the page linked above there are links to 2 other resources. "thither's page" and a gentoo forum link. Thither's page is worth checking out and the gentoo forum is a long read but provides some background on the problems.
    The link also provides misc patches. I have not tried those yet.
    As far as I know the wireless card does not have working drivers yet and the ati card will not run 3d due to lack of drivers. If I find solutions to either I will post here.
    p.s. Sorry about the OT in the posts above I am the only person I know who can get OT in a dsicussion with themself. 
    Thanks,
    Jason

Maybe you are looking for