Quicksilver G4 boot straight to OF - RERUN

I already posted this as a reply, but I decided it would deserve a new topic:
Well, I was good for a bit over a month (I was gone most of July). The new board seemed to be working fine except for the built in firewire.
Upon returning from my trip to Asia, the computer started locking up infrequently. Then last night, I tried to burn a DVD from iDVD. It hung. Restarted a couple of times and gave up. Then this morning while surfing the net a bit, it froze again. I shutdown until I got home. Then the worst happened. I got a message when trying to boot from my internal harddrives:
"bad Bus info CRC-16
DEFAULT CATCH!, code=300 at %SRR0: ff84755c %SRR1: 0000b030..."
This is the same error I got in February when I had a similar problem. I was able to run off of my firewire drive for a while, but I just have not gotten to that. I don't know if there is any sense in it.
I tried to use TechTool, but it is not seeing the internal volume and won't work without a volume to select. I tired using the OSX install disc. I was able to see the volume in DiskUtility. It did a repair disk and found nothing wrong. I tried to repair permissions, and each time, it gets about 25% of the way through when it says "Disk Utility Internal Error Disk Utility has lost its connection with the Disk Management Tool and can not continue. Please quite and relaunch Disk Utility."
So, needless to say, I am very frustrated at this point. I had hoped to get a MacBook, but some sort of desktop might be more practical.

I have been running for two days with no booting issues:
After getting OSX installed on my firewire drive. The computer booted and ran fine using only that drive.
For argument sake, I reconnected the internal drives. Letting the computer boot directly from the firewire drive was smooth. Additionally, the internal drives mounted. However, if I have the internal drives conncected and hold down the option key while booting, the computer locks at the selection screen.
In one of my direct firewire boots, I was able to use SilverKeeper to make a copy of my internal drives and create another bootable firewire drive that is identical to what I had the day everything went awry. It did fail two times however before completing successfully. The failures both happened when I was doing some other stuff. Once I let the computer run only that backup, all was fine. I have been using this firewire drive now as my main drive with the internal drives disconnected to avoid any potential problems.
I am thinking the controller on the Mother Board is toast. Everything else seems just as it should be.
Quicksilver dual G4 @ 1.33GHz Mac OS X (10.3.9) Blue & White G3 @ 400MHz for the kids

Similar Messages

  • Quicksilver G4 boot straight to OF...

    I never really knew you could get into open firmware until today. This morning, my son put my G4 into sleep mode which caused it to just freeze up. I had to do a hard shut down. I hate doing that, but that was the only option. Got back this evening and booted the computer up. I got the following message:
    Bad Bus Info CRC-16
    DEFAULT CATCH! code=300 at %SRR0: ff84755c %SRR1: 000b030
    Apple PowerMac 3, 5 4.2.5fl BootROM bult on 08/16/01 at 22:19:35
    Copyright 1994-2001 Apple Computer Inc
    All rights reserved
    Welcome to Open Firmware, the system time and date is 20:55:18 04/14/2006
    To continue booting, type "mac-boot" and press return
    To shut down, type "shut-down" and press return
    If I type mac-boot, I get a screen of black and white stripes. I removed a PCI USB card, and same result, removed the PCI Firewire card, same result. Removed the remaining peripherals (an iSight), and it still goes straight to the OF, but now the first line about a bad bus is gone. All other lines are unchanged.
    Looking at it now, the time seems to be a bit off, or is the GMT? Not really sure what time exactly that I tried the boot that gave me this time. It is now 18:07 here in EDT. Insights?
    Quicksilver dual G4 @ 1.2GHz   Mac OS X (10.3.9)   Blue & White G3 @ 400MHz for the kids

    I have been running for two days with no booting issues:
    After getting OSX installed on my firewire drive. The computer booted and ran fine using only that drive.
    For argument sake, I reconnected the internal drives. Letting the computer boot directly from the firewire drive was smooth. Additionally, the internal drives mounted. However, if I have the internal drives conncected and hold down the option key while booting, the computer locks at the selection screen.
    In one of my direct firewire boots, I was able to use SilverKeeper to make a copy of my internal drives and create another bootable firewire drive that is identical to what I had the day everything went awry. It did fail two times however before completing successfully. The failures both happened when I was doing some other stuff. Once I let the computer run only that backup, all was fine. I have been using this firewire drive now as my main drive with the internal drives disconnected to avoid any potential problems.
    I am thinking the controller on the Mother Board is toast. Everything else seems just as it should be.
    Quicksilver dual G4 @ 1.33GHz Mac OS X (10.3.9) Blue & White G3 @ 400MHz for the kids

  • When I boot up my iMac and hold down ALT it boots straight into windows 7 without giving me the option to boot OSX back up. Have I lost OSX and all my files completely? Please help

    I set up boot camp for my iMac with windows 7. All was fine and it gave me the option to boot into windows.. I then used windows for a few hours and shut down the mac to boot back onto OSX when I was done.. This time my mac booted straight to windows 7 even with me holding down the ALT key it gave me no choice.
    I'm assuming the boot camp set up was wrong somewhere but is there a way to get back on to OSX now?? Please help

    1. Have you tried both Alt keys - maybe your Alt key is dead.
    2. Do you have wireless keyboard? Have you tried to change batteries? USB Keyboard?
    3. If your Win is installed correctly then you have also installed all windows support software.
    There should be Startup manager like on the Mac (next to the clock little bootcamp app or in control pannel) to restart your Mac into the Mac partition.

  • IMac boots straight into Windows 7

    I installed Windows 7 Ultimate x64 using Bootcamp on an iMac 9,1. Now when I turn my computer on, it boots straight into Windows 7 by default. If I hold down Option while booting and select Mac then it does boot correctly into OS X 10.6.1. Is there a way for me to configure the iMac to boot into Snow Leopard by default?

    Use the Startup Disk pane of System Preferences in Mac OS X or the Startup Disk control panel in Windows.
    (48479)

  • My Quicksilver G4 boots up and after a few minutes working shuts down

    My older Quicksilver G4 boots up in a completely normal way and then after a few or more minutes working inadvertedly shuts down.
    I checked out if in sleep or shut down pref's something was changed?
    Is it possible the motherboard battery that fails?

    Hello Ollie,
    Have you blown the dust out lately?
    Especially the Video card, CPUs, RAM, & PSU.

  • MDT 2013 Boot straight to CMD after upgrade?

    Hi,
    I've recently upgraded MDT 2012 to MDT 2013. My images are working if no changes are touched. However, right after I add NIC and other drivers for a new dell model ( e5550) and regenerate the image, all my models boot straight into CMD after the image gets
    picked up via WDS. Very weird.
    I have a snapshot of my deployment server just after the mdt migration so i can always fall back to the original state for my current models, but I need to resolve this to able to add new drivers and new models going forward.
    I'm thinking it had something to do with installing windows 8.1 ADK and perhaps it changed the win PE version? I am new to MDT so there must be something obvious I am overlooking. Has anybody seen this before?
    also, when would I be extracting the Dell WinPE cab to the boot image? And how I know which version to use?

    This is the set-up for my MDT. I dont have a seperate WinPE folder. is this best pratice or now required?
    http://imgur.com/Bs2TnmL

  • Boot straight into KDEmod desktop

    How do I boot straight into the KDEmod desktop, not the login window but the desktop itself (if using kdemod is relevant)?
    I switched to windows from linux and now after 6 months going back to linux so I've kind of forgotten some things.
    Last edited by KCE (2008-02-07 02:36:49)

    I assume you mean bypassing KDM's login screen and going directly into KDE desktop.
    You can use the..
    x:5:once:/bin/su PREFERED_USER -l -c "/bin/bash --login -c startx >/dev/null 2>&1"
    method mentioned in the "Start X at Boot" wiki like you've done but I just thought I  would let you know that
    KDE lets you change this inside control center.
    Control Center --> System Administration --> Login Manager --> Convenience

  • Quicksilver wont boot after using compressed air to clear dust

    Help,
    My Quicksilver was waking from sleep on its own. I opened it up and found it was extremely dusty so I blew all the dust out with compressed air. I was very careful not to touch anything. It booted up but hung up, I couldn't force quit so I shut down using the power button, waited five minutes and restarted. The power light came on but went out again almost immediately. I can hear fans running and peeking inside I see a red light on but no video to monitor.
    There has been a problem from day one with start up hanging but many attempts by apple tech's could never find the problem. They changed out the orig. HD. but It didn't fix the problem. I learned to live with the problem and added external drives for backup. Unfortunately one drive is SATA. I am using my G4 notebook but have no access to the SATA drive.
    I need the Quicksilver back. Does anyone have a suggestion I might try.
    Thanks in advance for your comments.
    BJZTX
    Houston
    G4 Quicksilver   Mac OS X (10.2.x)   G4 Notebook 10.3

    Hi, BJZTX -
    Try resetting the PMU -
    Article #95037 - G4 (AGP) - Resetting PMU
    Note - the procedure in that article applies to all G4s except the )PCI) model; although the location of the PMU button varies, it is generally near the battery.
    Try rolling the battery in its holder, to ensure good contact.
    Check to make sure all internal cables are well-seated - that usually entails breaking and making the connections (do that with the machine powered off and unplugged).
    Some dust can be conductive - make sure no dust clumps got blown into the pins for RAM, CPU, PCI sockets, etc.
    Ditto the jumper pin blocks on the drives. While there, make sure no jumpers got dislodged or blown off.

  • IPhone 4, Home button not working, stuck in recovery mode and boots straight into voice control.

    After trying everything and failing I still cant work out why this is happening.
    I cant restore my phone in itunes, just get an error. My phone boots into voice control for no reason and to top it off the home button stopped working along with all these errors. It cant be a hardware issue. I sent it in and got told I had water damage which is impossible as I treated the phone like gold.
    Does anyone have a reasonable explaination as why this is happening and maybe even a solution?
    Thanks!

    try to put your phone in recovery mode. plug into itunes and hold down the home button and top button until apple logo appears and then let go of the top button only. the phone should display plug into itunes.let go of the home button when this happens. disconnect iphone and plug it back in itunes should recognize it is in recovery mode. hit the restore button on summary page.

  • After trying to backup  my hard drive i can't get my G4 quicksilver to boot. I get the old icon of a folder with a split face that alternetes with a flashing question  mark

    My G4  won't boot. I have tried holding down the c key to boot from a 10.3 disc and it doesn't boot. I keep getting the icon of a folder with a split face that flashes to a question mark. I know that usually means that the startup drive can't be found, but I have 2 good drives i have tried to boot with and it won't start up. Any ideas from out there/ Thanks in advance.

    I doubt it's CCC's fault, possibly a bad DIMM, or slot, or corrosion in the slot.
    How large is the drive? Which G4? Some can only handle 128-123 GB Drives. Is it an old drive?
    So we know more about it...
    At the Apple Icon at top left>About this Mac, then click on More Info, then click on Hardware> and report this upto but not including the Serial#...
    Hardware Overview:
    Model Name: eMac
    Model Identifier: PowerMac6,4
    Processor Name: PowerPC G4 (1.2)
    Processor Speed: 1.42 GHz
    Number Of CPUs: 1
    L2 Cache (per CPU): 512 KB
    Memory: 2 GB
    Bus Speed: 167 MHz
    Boot ROM Version: 4.9.2f1
    If you don't know the model, find the Serial# & use it on one of these sites, but don't post the Serial# here...
    http://www.chipmunk.nl/klantenservice/applemodel.html
    http://www.appleserialnumberinfo.com/Desktop/index.php
    How to find the serial number of your Apple hardware product...

  • Not booting straight to windows help please

    im trying to get a real fast boot time on my pc but i keep geting these 3 screens befor it gose to windows i have the msi 760gma-p34 (fx) mother board i set the ssd raid 0 as boot and it still says cant find any device and then loads the drives then gose to windows idk y please help
    heres a video of what its doing
    here is my computer specs
    Board: 760GMA-P34 (FX)
    Bios: Version 25.0
    VGA: Galaxy GT 430
    PSU: Cooler Master Extreme Power Plus ATX12V v2.3
    cpu: AMD FX-4300 Vishera Quad-Core 3.8GHz (4.0GHz) Socket AM3+ 95W Desktop Processor FD4300WMHKBOX
    MEM:G.SKILL 8GB (2 x 4GB) DDR3 1600 (PC3 12800)
    HDD: Kingston SSDNow V300 Series SV300S37A/120G 2.5" 120GB SATA III Internal Solid State Drive (SSD)
    COOLER: Stock

     How many more times and places in this forum do you plan on posting this same topic? Once is enough and more than once is against the rules. 3 times now is way too many.
     >> Forum Rules <<

  • Quicksilver wont boot up, firewire problems as well.

    A couple days ago, the firewire on my motherboard stopped functioning and no longer showed up in System Profiler. I tried installing a pci firewire card and booted up fine twice showed up on System Profiler but did not funtion, I also added two 128 MB RAM sticks at that time which seemed to work fine, and showed up on System Profiler Now when I turn on the computer gray spinny screen shows for a while than a light blue screen with cursor but nothing else...
    Previously, the main hard drive died and was replaced. I've had no problems except this since then.
    Could someone please help?
    Thanks!

    Try things in Apple doc.#106464 for your startup issue.
    Also, try using Disk Utility to repair your startup disk (hard drive) as shown in Dr.Smokes Resolving Disk, Permission, and Cache Corruption. His link will help walk you thru it.
    I'm throwing alot of stuff at you here. A bad PRAM (also called clock) battery can cause startup issues AND FireWire not to show.
    I would check it first. When mine went, I had no response from my Mac at all; just a light on my power button; absolutely no boot at all.
    Check out things in Texas Mac Mans tutorial on the subject. His tutorial is a little dated (don't believe it even mentions G5's) but the info in it, except SMU not being included, still applies.
    If you still have FW troubles, read on;
    Thought you could use this info about getting FireWire to work!
    First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
    Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
    If that did'nt work, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try. Yours is the 10.3.9 Combo update (that's what your specs. say). Others reading, download the Combo that applies to your system.
    If that still did'nt get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
    For those of you with Macs that are not PowerBooks or iBooks, a bad internal battery can cause FireWire to not be recognized, so make sure it's good!
    Good Luck!
    Cheers!
    DALE

  • Changing Boot Order on Dual Boot Windows 8 and Ubuntu

    Hi there,
    Recently got a HP Pavilion g6 2213sa which came with Windows 8 (spit!) and this disgusting UEFI BIOS replacement (double spit!).
    Anyway, I need to dual boot Ubuntu on my system, so I installed Ubuntu. Normally, on a non UEFI system, a "Grub" bootloader installed by Linux would take over the startup process, and allow you to choose between either Windows 8 or Ubuntu on startup.
    However, on this computer, startup is just booting straight to Windows 8 despite the fact that Ubuntu and Grub IS installed.
    Now, upon startup, if I press F9, then I get to change the boot-device on a one-time basis. I can either select "OS Boot Manager", which loads Windows 8, or "Ubuntu" which loads the Grub bootloader which allows me to select Windows 8 or Ubuntu.
    However, when I press F10 to enter the Bios Setup with the intention of changing the boot order permanently, the Ubuntu option isn't there. Instead it has OS Manager, USB Disk, CD Rom, USB CD Rom and Network Card.
    Thanks, HP for, the crappily designed BIOS.
    Anyway, can anyone PLEASE provide me a way of changing the boot order so that GRUB is loaded first and NOT this crap Windows 8 rubbish (that I would happily bin if I didn't need it for work). 

    There is the same problem in HP 2000 laptops (in my case specifically, HP 2000-2D22DX). I did some investigation using trial and error, and this is what I found out:
    There is some sort of a "recovery feature" or so that on every boot sets the very first UEFI load option to point to one of the two locations, in this order:
    \EFI\Microsoft\Boot\bootmgfw.efi
    \EFI\Boot\bootx64.efi
    This option is displayed as "OS boot Manager" (for the first path) and something akin to "UEFI partition" for the second path, completely ignoring the actual name given to it (when you look at the EFI variables through efibootmgr, you can see that what is displayed as "OS boot Manager" actually is set to the name "Windows Boot Manager"; why anyone would do such renaming is beyond me). If you try to change the boot order so that this slot isn't the first, the UEFI will overwrite the BootOrder variable on next boot and reset it to point to "OS boot Manager" anyway.
    By default, both of the paths above contain the same Microsoft bootloader (if you check the md5sum of both, you'll see they match).
    So, until HP releases an updated UEFI that allows turning this "feature" off or rearranging boot options through the F10 UEFI setup, this is what you can do to get dual boot with the least amount of hackiness:
    In Windows, mount the UEFI partition (mountvol S: /S mounts it as the S: drive) and copy the file \EFI\Microsoft\Boot\bootmgfw.efi to use some other name (for example, I copied it to "\EFI\Microsoft\Boot\bootmgfw.efi~", but you can change the name to anything else).
    In the Windows command prompt, update the Windows UEFI entry to point to the new name: bcdedit /set {bootmgr} path \EFI\Microsoft\Boot\bootmgfw.efi~ (adapt to your set name accordingly).
    Optionally, change the name of the Windows boot loader so that you would be certain that it points to the new file location: bcdedit /set {bootmgr} description "Fixed Windows path"
    Install the other OS. In my case the bootloader was installed into \EFI\opensuse\grubx64.efi.
    Delete the two files, \EFI\Microsoft\Boot\bootmgfw.efi and \EFI\Boot\bootx64.efi.
    Use efibootmgr to delete the "OS boot Manager" entry: sudo efibootmgr -b 0000 -B
    Set the new OS bootloader to be the default bootloader by using efibootmgr with the -o option. In my case, I had an entry called "opensuse" in slot Boot0001 and the updated path Windows entry in slot Boot0002, so I had to do sudo efibootmgr -o 0001,0002
    Update GRUB to point the Windows entry to your renamed file (you'll have to create a new file in /etc/grub.d and rerun grub-mkconfig).
    And that's it, now the UEFI will boot GRUB by default (it won't regenerate the "OS boot Manager" entry since it won't be able to find either of the two hardcoded paths and will "fall back" to properly reading the BootOrder variable), and the F9 menu will still allow choosing to boot Windows directly.

  • HP Touchsmart 23 520-1180a boot up problems

    Hello.
    I have an HP touch smart 23 AIO desktop.
    I am having issues with what I suspect is the HDD.
    I think it is the HDD as the original 1TB hdd drive with windows 7 installed would freeze up at random (during boot or general use).
    It would also not let me install windows 8(it wouldnt get past the setting up screen).
    I then decided to put in another 500gb HDD out of an old media player I had.
    It worked, I could install windows 8 and no random freezing until tonight.
    After not using the PC for about a week I turned it on and it showed a boot error "No boot device detected".
    I have since re started it and it booted in to windows only to freeze up again.
    Before the freeze I managed to open task manager to check the performance, I seen that it was using 100% of the HDD.
    as it is still a fresh installation of windows I have very few processes running.
    I dont know if it is a HDD or a fault on the motherboard.
    I ran a diagnostic test from the BIOS, the cpu passed so did the ram but the HDD failed, the error was that the HDD was not connected.
    I did hear the HDD working through.
    Also after the test ran the PC froze again, so I restarted and ran the bios again the same results showed up, I then restarted again and it started to load windows then froze again.
    I then moved a 2 TB HDD from another All in one PC to the troubled PC and it froze up almost right after turning the PC on.
    I then popped the 500gig HDD from the troubled PC in to the other PC and it booted straight into windows with no problem.
    There is a SATA cable from the HDD to the MoBo, I took the one from the working pc and put it in the troubled pc just to rule out the cable, it still failed the HDD test and froze. 
    So I plugged the HDD cable into the CDROM SATA input and restarted, although it would still get boot error the HDD would pass diagnostics test but would not boot windows it would just go into recovery but still with random freezing.
    I Tried to Boot Herin's boot disk but it froze.
    Just seems to be freezing randomly now, I just dont know what to do it what it could be anymore.
    UPDATE: I have just turned the computer on 3 time and ran diagnostics 3 times and everytime the HDD pass BUT everytime the pc froze.
    Also I tried to reinstall windows and yes yet again it froze.
    This question was solved.
    View Solution.

    Hello,
    I have read your post on how your HDD boots with an error, passes all the tests, and I would be happy to assist you!
    The first step I recommend is to follow this document on Restoring the BIOS. This should help how your computer will boot from the HDD. In addition, I also suggest replacing the SATA cable connecting your HDD to your motherboard. To do this, please follow this document on How to Remove SATA cable.
    If the issue persists, please call our technical support at 1-800-474-6836. If you live outside the US/Canada Region please click the link below to get the support number for your region.
    http://www.hp.com/cgi-bin/hpsupport/index.pl
    I hope this helps!
    Best Regards  
    MechPilot
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

  • HOWTO: Repairing a headless Arch Linux system that fails to boot

    The scenario...
    I have a "headless" (no monitor or input peripherals) Arch Linux computer that is connected to a local network via a wireless adapter, and accessed from other computers via SSH.
    Earlier today I accidentally broke its kernel so it did not boot anymore.
    Idea: Temporarily connect a monitor to the computer, boot from a live CD (like the Arch Linux install CD), then chroot into the system and fix it.
    Problem: I didn't have a compatible monitor at hand.
    Idea: Log in to the live CD session from another computer via SSH.
    Problem: The live CD can't auto-configure the headless computer's wireless connection, and setting it up manually while working "blind" would be a major hassle. A direct LAN connection to the router wasn't available either.
    Idea: Connect directly with a laptop via an Ethernet cable, and then use SSH from the laptop => This solution worked for me!
    If you find yourself in a similar situation, you can follow this tutorial which describes the solution that worked for me in detail...
    You need:
    a copy of the Arch Linux install CD (I used the 2013-05-01 version)
    an Ethernet cable
    a keyboard (might be dispensable, with additional preparation)
    a functional Arch Linux laptop (or other computer within physical range)
    Step 1) Prepare the live CD...
    I used the plain Arch Linux install iso, burnt to CD.
    By creating a carefully customized version of the live CD using Archiso, you might be able to eliminate the need for steps 2 and 4 - however that's not covered in this tutorial.
    Step 2) Prepare the laptop...
    The laptop needs to be configured in such a way, that the live CD's attempt to automatically establish an Ethernet connection with it will succeed:
    a) IP address
    In my case, the Laptop's wireless adapter had an IP address in the range 192.168.1.*, connecting it to the local network and Internet via the central router 192.168.1.1.
    The Ethernet connection between the laptop and the headless computer becomes a separate mini-network, for which I decided to use IP addresses in the range 192.168.0.* (note the different third number). Specifically, I set the IP address of my laptop's Ethernet card to 192.168.0.1. You can do this by running the following as root (replace "eth0" with the name of your Ethernet interface):
    ip link set eth0 up
    ip addr add 192.168.0.1/24 dev eth0
    b) IP forwarding (optional)
    While we're at it, we might as well enable IP forwarding, so that the live CD session on the headless computer will be able to directly use the laptop's outgoing Internet connection (which will make it much more convenient to install/upgrade packages during the repair session). To enable this, run the following as root (replace "eth0" and "wlan0" with the names of your laptop's Ethernet and wireless interfaces, respectively):
    iptables --table nat --append POSTROUTING --out-interface wlan0 -j MASQUERADE
    iptables --append FORWARD --in-interface eth0 -j ACCEPT
    sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
    c) DHCP
    The live CD will assume there's a router on the other side of the Ethernet link, and ask for an IP address via DHCP. So all we need to do, is run a dhcp server on the Laptop that will answer this request. It's surprisingly easy: Just install the package dnsmasq, and put the following in the file /etc/dnsmasq.conf (again replacing "eth0" as appropriate):
    interface=eth0
    dhcp-range=192.168.0.2,192.168.0.2
    By setting the start & end values of dhcp-range to the same IP address, we enforce that this specific IP address will be used by the live CD on the headless computer.
    Then start the daemon by running the following as root:
    systemctl start dnsmasq.service
    Step 3) Connect everything and boot up the live CD...
    Connect the laptop and the headless computer via the Ethernet cable.
    Connect the external keyboard to the headless computer.
    Then put the Arch Linux install CD into the headless computer's drive, and boot. Wait a minute or so to give the CD time to load its boot menu (you should hear the CD drive spin up and settle down again). Then hit ENTER on the connected keyboard, to activate the default menu choice (which will boot straight to a live Arch Linux session with root privileges).
    You can check whether it booted up and successfully initialized the Ethernet connection, by ping'ing the IP address that was specified in step 2c) from the laptop:
    ping -c3 192.168.0.2
    Step 4) Start the SSH server...
    Unfortunately, the Arch Linux install CD doesn't automatically start its SSH server, and also it uses a randomized root password. To make SSH connections possible, you will have to use the connected keyboard to type in some stuff "blindly" (but it's simple enough):
    type "passwd" (without the quotes)
    type in a new password of your choice
    press ENTER
    type in the same password again
    press ENTER
    type "systemctl start sshd" (without the quotes)
    press ENTER
    Step 5) Connect from the laptop via SSH...
    Now you can open an SSH connection, by executing the following on the laptop (when it asks for the password, enter the one you chose in step 4):
    ssh [email protected]
    Step 6) Profit!
    Within this SSH shell on the laptop, you can now do whatever you would usually do to fix an Arch Linux system from a live CD.
    You'll probably want to chroot into your Arch root partition, which is very easy thanks to the arch-chroot tool that is included on the live CD (replace "/dev/sda3" with the name of the headless computer's root partition):
    mount /dev/sda3 /mnt
    arch-chroot /mnt
    If you set up IP forwarding as described in step 2b), then Internet access should magically work in this shell without any further configuration, so you can freely use pacman etc. inside the chroot.
    Enjoy!
    Last edited by sas (2013-07-26 22:17:03)

    It is definitely able to recognize the USB and DVDs as separate drives; it gives the option of booting from USB, and it gives the memory capacity of the USB drive I used as a live USB, and the memory used for the live CD.  But when it comes time to actually boot, something is going wrong.
    I would suspect it is a problem with the BIOS, if not for the fact that I had a similar issue on my previous system, which used a completely different motherboard.  If it is the same issue, it would either have to be a problem with the DVD drive (although I don't know why it would be against loading some live CDs but not others) or perhaps the way I created the live CDs.  Although, again, I don't understand why the Linux Mint 32-bit DVD would work fine, while both 64-bit DVDs would not.
    I will try using a different DVD drive to boot the DVDs, and if that does not work, I'll try creating a new Arch live CD to see if I can resolve the issue.  But if anyone has any ideas, it would still be greatly appreciated.

Maybe you are looking for