Boots to command line...... help

I've reinstalled Tiger (10.4) and other apps on some Ti PowerBooks using erase and install. After applying 10.4.8 Combo Update(directly from network server), all systems boots to command line !!!!! even Safe-Boot doesn't work. putting the "exit" command shows the blue screen and goes back to the commandline.
file permissions and volumes seems ok.
Is there a way to get back to GUI without reinstalling OS X again ?
Thanks in advance.

I am having the same sort of problem. I tried the PRAM startup, but the problem still persists. I've tried to find the problem through the unix command line, but I haven't been successful.
I repaired the permissions, but now when I try to verify the volume through the disk utility, it tells me that there is an error in the directory, that there should be 45 items, but there are only 44. A system check shows that the volume Macintosh HD needs to be repaired. However, when I try to use the {diskutil volumeRepair}, it tells me that the volume could not be unmounted. now, when I verify permissions and unmount the volume, then run the volumeRepair, it still says that the volume could not unmount.
I think that is all. Thank you for your help.

Similar Messages

  • Starting and stopping X + booting into command line rather than GUI

    After installing Arch and struggling a bit to get the gui environment (gnome) to work I am now in a situation where the distro works fine but boots directly into a gnome session.
    I would like to be able to stop X and I have tried various recommended commands. The only one that works seems to be "kill -15 X" (after doing Ctrl+Alt+F2), which ends X but sort of stops mid-process without ever going back to any command line prompt.
    I copied etc/skel/.xinitrc into my home folder and uncommented "exec xterm", while re-commented "exec gnome-session". This did not make any difference at all so perhaps I'm not even using that script?
    As I had some difficulties installing X (or rather get it to work) I may have installed a whole plethora of packages that I may not need. There are references to Wayland for instance, packages I installed. But am I actually using them? How can I find out?
    I would like Arch to boot into a command line environment and then I'd start X from there - if that is what I want!
    Any pointers in any direction regarding the above are welcome!
    Cheers!

    What guide did you follow to install? The beginner's guide and the Xorg page contain the relevant information. Following just them should have allowed you avoid the mess you're in. Just saying that you've installed a whole plethora of packages will not help...it makes it near impossible to help.
    You ought to read this. It sounds like you installed a display manager and set up auto-login?
    Last edited by nullified (2015-02-20 17:26:59)

  • Enterting File to be used at the command line (help!)

    I have this code which works on by loading a .txt which hold a matrix of numbers and doing some maths and the like on it. the problem with this is that it is limited to only being able to read from that one file. i would like to make it possible to enter the name of the .txt file at the command line when running the program
    e.g java FlatCost costs.txt
    heres the code so far (it works).
    import java.io.*;
    import java.util.Vector;
    public class FlatCost
        public static void main(String[] args) throws IOException    {       
            FileInputStream stream = new FileInputStream("costs.txt");
            InputStreamReader reader = new InputStreamReader(stream);       
            StreamTokenizer tokens = new StreamTokenizer(reader);       
            Vector v = new Vector();
            while(tokens.nextToken() != tokens.TT_EOF)        {           
                v.add(new Integer((int) tokens.nval));
                System.out.println(new Integer((int) tokens.nval));        }       
            System.out.println("Enter floor number: ");       
            BufferedReader in = new BufferedReader(new InputStreamReader(System.in));
            String line1 = in.readLine();
            int x = Integer.parseInt(line1);
            if(x > 3) System.out.println("Sorry, out of range");
            System.out.println("Enter no. rooms: ");       
            String line2 = in.readLine();          
            int y = Integer.parseInt(line2);
            if(y > 2) System.out.println("Sorry, out of range");
            int numFloors = v.size()/4;               
            int dest = ((x*4) + y + 1);
            System.out.println("PRICE: " + v.get(dest));   
    }Please help because i dont know how to do it
    Carl

    That's right... specificallyFileInputStream
    stream = new FileInputStream(args[0]);
    Also don't forget make sure the argument was supplied. Otherwise you'll get a runtime array out of bounds.
       if (args.length < 1) {
          System.out.println("Usage: java FlatCost filename");
          System.out.println("   eg: java FlatCost costs.txt");
          // exit or supply default file
       }

  • After upgrading 10.4.10 to 10.4.11, MacPro boots into command line

    the subject line says it all.
    how to boot into the GUI?

    See this discussion thread Apple - Support - Discussions - Booting to Darwin-BSD Screen for a solution. If it doesn't work you will need to do the following:
    How to Perform an Archive and Install
    An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
    1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger) and/or TechTool Pro (4.5.2 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
    3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
    4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
    5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
    6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

  • OSx 10.4.6 - stuck in command line - help

    I have had a nightmare since taking the automatic update.
    after a very long while a 4 restarts my screen has gone to a terminal screen that says:
    Darwin/BSD (Mark-computer.local) (Console)
    Login:
    what am I supposed to do now. Its been years since I used unix so any suggestions please

    Welcome to Apple Discussions!
    Did you backup your data prior to the automatic upgrade? If you did, I'd just restore from backup and follow the procedure recommended for upgrading Macs:
    http://www.macmaps.com/upgradefaq.html
    If you didn't, get Prosoft Data Rescue from http://www.prosofteng.com/ and recover data to an external Firewire hard disk. Once that is done, I'll see about finding an expert who might be able to help you.
    Disclaimer: Reference to links I make to my Macmaps.com website are a for your information only type reference. I do not get any profit from this page, and it is open to the public.

  • Command Line Help!

    Hello:
    When I tried the following:
    SQLPlus sys/<password>@<dbname>, I get the following error:
    ERROR:
    ORA-28009: connection to sys should be as sysdba or sysoper
    Can somebody tell me what the syntax is to log in with the account SYS?
    Thanks.
    Venkat

    connect sys@dbname as sysdba

  • Unable to login. No recovery disk. How can I boot into command line?

    I am unable to login using my Apple ID, using the password reset option does not work. I have no recovery disk. Don't mind wiping it if necessary. Please advise, thanks

    Please carefully read  OS X Mountain Lion: Reset a login password

  • Command line mode bootup

    My mac boots to command line mode ( not sure single user mode or verbose mode ). I've tried following ways to fix but it doesn't help. Can anyone help ?
    - fsck -fy
    - mount -uw /
    - verify disk permission
    Wicky

    If this is not the case: http://support.apple.com/kb/TS4376
    Try resetting PRAM/NVRAM: http://support.apple.com/kb/HT1379

  • Sending image sequence job to compressor in command line : how to set the framerate?

    Hello,
    In Compressor, when you import a image sequence, it's possible to set the framerate and add an audio file before choosing a preset and lauching the encoding task.
    I want to dlo the same thing with command line. I know how to send a compressor job with command line, but no how to add theses settings.
    In the compressor command line help, we've got this :
    Job Info: Used when submitting individual source files. Following parameters are repeated to enter multiple job targets in a batch
              -jobpath <url> -- url to source file.
                                               -- In case of Image Sequence, URL should be a file URL pointing to directory with image sequence.
                                               -- Additional parameters may be specified to set frameRate (e.g. frameRate=29.97) and audio file (e.g. audio=/usr/me/myaudiofile.mov).
    So there are also framerate and audio parameters in command line but i've no idea how to write the command line with theses parameters
    Here is an example of command line for Compressor (by Apple) :
    ./Compressor ‑clusterid tcp://127.0.0.1:51737 ‑batchname myBatch ‑jobpath /Volumes/Source/ShortClips/NTSC24p.mov ‑settingpath /Users/stomper10/Library/Application\ Support/Compressor/PhotoJPEG.setting ‑destinationpath /Users/machinename/Movies/myDestinationFilename.mov.
    Thank you for your help!

    You can see in the command sh running-config command
    show running-config : Displays the current access point operating configuration
    Use the guest-mode SSID configuration mode command to configure the radio interface (for the specified SSID) to support guest mode. Use the no form of the command to disable the guest mode.
    [no] guest-mode .
    Here is the guideline for usage
    The access point can have one guest-mode SSID or none at all. The guest-mode SSID is used in beacon frames and response frames to probe requests that specify the empty or wildcard SSID. If no guest-mode SSID exists, the beacon contains no SSID and probe requests with the wildcard SSID are ignored. Disabling the guest mode makes the networks slightly more secure. Enabling the guest mode helps clients that passively scan (do not transmit) associate with the access point. It also allows clients configured without a SSID to associate.
    Examples
    This example shows how to set the wireless LAN for the specified SSID into guest mode:
    AP(config-if-ssid)# guest-mode
    This example shows how to reset the guest-mode parameter to default values:
    AP(config-if-ssid)# no guest-mode

  • ERROR: -1639 INVALID COMMAND LINE ARGUMENT

    Trying to install software for Shuffle that Santa brought and get this error messsage...
    "Error: -1639 invalid command line argument. Consult the windows Installer SDK for detailed command line help."
    Install stops at this point.
    SOMEONE HELP... My kid is chomping at the bit !
    Thanks.

    Ok I'll do some more searching but I found something in the community forums.
    APPSearch can not return this data into a property, so instead, for some unspeakable reason, returns a value of Null, follwed by another Null. This means that the property is created, and populated with two null characters. Bad news if the property also happens to be a PUBLIC property. All public properties are passed as part of the command line sent in a stream to the background installer process by the Execute Action. Since this stream now contains a double null value in a property, the stream is prematurely terminated. This creates an invalid command line, and thus the 1639 error.
    This user solved it by using the MSi Cleanup installer util.
    EDIT: A little more info...
    This problem is almost impossible to detect through the MSI log files since our friends at Microsoft chose to limit the length of any line in the log. It is impossible to get a dump of the full command line that generates this error.
    EDIT2:Note that error 1639 only ocurrs when the install package is run from removable media. When the package is run from local storage, the behavior is far more obtuse. The background install process, failing to receive a complete command line, is forced to run as if there had been no UI session, which in turn causes the APPSearch action to run again as if the install was running in silent mode. This causes re-evaluation of all properties a second time, destroying the feature selections made in the UI session, and also forcing the install to run under user credentials instead of elevated, even though AdminUser, ALLUSERS and Privleged properties are set. This is a very serious error that causes total failure of the installation.

  • Command line transfer of TM backup to Time Capsule

    I have just purchased a new 3TB Time Capsule to replace my ailing 750GB Firewire drive as my Time Machine Backup drive. However, the 750GB drive has none TM files on it, that I do not want to transfer to the new Time Capsule (see details below)
    file://localhost/Volumes/LaCie%20BackUp/Backups.backupdb/
    file://localhost/Volumes/LaCie%20BackUp/IBM%20DDRS-39130D%20Media/
    file://localhost/Volumes/LaCie%20BackUp/Orphans%20Folder/
    file://localhost/Volumes/LaCie%20BackUp/Files%20from%20Server/
    The reason I am doing it this way is also because my old drive occassionaly goes into a 'pause' that requires me to disconnect it from my MacBook Pro and reconnect it to try again. Thus I need to be able to transfer my backup files in smaller chunks than a whole disk image would entail, so that if the drive stops, I can pick up from the point of failure and carry on rather than start from scratch again.
    Only the Backups.backupdb needs to be transferred to the Time Capsule, so I don't want to use Disk Utility and have been trying to copy the relevant backup directories using Terminal and the 'cp' command as SuperUser. However, I am finding that even so I am getting error messages back stating 'Operation not permitted', mainly to do with cp trying to run 'lchmod'.
    I have read the existing FAQ article https://discussions.apple.com/message/11422415#5 and have all the correct journaling settings, etc. and the data seems to be transferring fine. Just not sure yet if I will have fully functional backups when I have finished.
    Any command line help such as using the appropriate flags, etc. would be helpful.
    Thanks, Russ

    Pondini's notes are quite useful and I tried using SuperDuper and Disk Utility. I transferred my backups from my old 750GB Firewire400 backup drive to my new 3TB Time Capsule using both of them. Each time I tried, the transfer took to an inordinately long time - it failed any time up to a maximum of 18 hours from starting, the best only achieved about 90% transfer!
    Also, I discovered by monitoring my MacBook's performance with Activity Monitor that both these programs are CPU intensive and indicated between 150% to 200% activity (both CPUs virtually maxed out), mostly with Finder activity. This was the limiting factor in the transfer and the process was achieving peak Disk I/O and network transfer rates of 10MB/s. The MacBook's fans were running full-blast during this time just trying to keep the thing cool!
    I eventually found the most efficient method to transfer backups by reading through some of the Unix command manual pages and discovered Apple Software Restore (ASR). This command is used as the underlying tool by both SuperDuper and Disk Utility and does all the actual work. The final transfer tool less than 7 hours.
    Network Transfer Rate 36MB/s (sustained)
    Disk I/O Rate 52MB/s (peak), >32MB/s (sustained)
    CPU activity 20% (peak), <15% (typical)
    Main process is 'diskimages-helper'
    The reason it works much better is that only the essential work is being done and that the command allows you to alter the buffer size to make it more efficient for the larger file transfer method. The whole transfer was therefore limited purely by the maximum transfer speed of the Firewire 400 drive itself. So here is how I did it using terminal:
    $ su
    Password:
    [change to superuser so you don't have problems with passwords and permissions, etc.]
    sh-3.2# nice -n -20 asr restore --source <source drive> --target <target drive> --erase --noprompt --allowfragmentedcatalog --buffers 8 --buffersize 64m --noverify
    Validating target...done
    Validating source...done
    Repartitioning target device...done
    Warning: You may not be able to start up a computer with the target volume.
    Validating sizes...done
    Restoring  ....10....20....30....40....50....60....70....80....90....100
    Remounting target volume...done
    After mounting the resulting Time Capsule BackUp, it had the name of my old drive, which confused me somewhat, so I simply renamed it in the Finder.
    Explanation:
    The 'nice -n -20' command tells the OS X kernal to prioritise the commands that follow by giving them preferential access to CPU time (kind of like putting go-faster-stripes on).
    The <source drive> is selected by dragging the drive icon onto the terminal window.
    The <target drive>  has to have been created first by running an initial Time Machine Backup on the Time Capsule, which creates the .sparsebundle directory. Once this is created, stop Time Machine, then use the finder to log onto the Time Capsule and double click the .sparsebundle file. This will mount a disk called 'Time Capsule Backup'. Drag this image onto the terminal window as the target drive.
    --erase removes any other stuff on the target drive and matches the journaling to the source drive
    --noprompt stops you getting "do you want to continue? messages
    --allowfragmentedcatalog ensures the directory catalogue on the source drive is read as is
    --buffers 8 the default is 8, but I tried it with different numbers of buffers, but it didn't affect transfer speeds much
    --buffersize 64m this made the most difference as the default is 1MB. Changing the buffer size makes the biggest impact as large file transfers work better when you give them large buffers.
    --noverify - I used this as the transfer itself takes so long that I wasn't really wanting to wait for it to verify as well. On the occasions that I left it to verify, that function operated at a VERY slow speed and would have taken more than 100 hours to complete. I did not have the patience to investigate as to why that was, but essentially the data transfer rate during that stage was <2MB/s. Whatever was causing it to run so slow was not limited by any resources on my MacBook Pro or the network connection, so I will let someone else work out what the issue was there.

  • 7410 booting directly to grub command line after forced restart?

    I'm running a 7410 (2x 100gb SSDs and 2x 500gb sata) with a j4400 containing 24 1tb drives. I attempted to create a pool and the bui hung so I went back to the SP and did a stop /SYS. After doing a start /SYS then starting the console, it goes through the bios startup, then initializes the external SAS card and after that immediately drops into the grub command line. There's no grub menu or anything, just the CL. Any idea how I can get back into the 7000 appliance software? As you can undoubtedly tell, I'm kind of a newbie so any help will be greatly appreciated!

    Not much documented and you must know your ak-nas-version
    findroot (system,0,a)
    bootfs system/boot/ak-nas-2009.04.10.5.0_1-1.20
    kernel$ /platform/i86pc/kernel/$ISADIR/unix -B ak_undo=true,zfs-bootfs=system/121,console=ttya,ttya-mode="9600,8,n,1,-"
    module$ /platform/i86pc/$ISADIR/boot_archive
    7xxx kernel$ /platform/i86pc/kernel/$ISADIR/unix -B ak_undo=true,zfs-bootfs=system/77,console=ttya,ttya-mode="9600,8,n,1,-"
    7110 kernel$ /platform/i86pc/kernel/$ISADIR/unix -B ak_undo=true,zfs-bootfs=system/90,console=ttya,ttya-mode="9600,8,n,1,-"
    7410 kernel$ /platform/i86pc/kernel/$ISADIR/unix -B ak_undo=true,zfs-bootfs=system/121,console=ttya,ttya-mode="9600,8,n,1,-"

  • Boot fails / goes straight to grub command line

    Fair warning: this is gonna be the worst request for help ever, but I'm stranded with a phone and a busted laptop.
    So, as the title suggests my laptop goes straight to the grub command line.  Having never dealt with this, I'm not really sure how to go about debugging it.
    Checking dmesg, I don't really see anything that says CATASTROPHIC FAILURE.  Then again I don't really know if dmesg can catch this sort of error.
    It's been a couple weeks since I used this laptop, but I don't think I upgraded or anything.
    I tried mounting the fs and blindly reinstalling stuff like the kernel and systemd but no dice so far.
    I can't post the actual logs right now but I might be able to later if I find an Ethernet cable.
    I think I can probably figure it out myself if someone could just point me in the right direction i.e. what the general debugging process is for this scenario.
    Again, I know this is the worst request for help ever, but if someone could help this damsel in distress it would be greatly appreciated.

    Actually, your request for help is far from the worst I have ever seen.  In fact, it is pretty good.  You tell us the problem, the history, what you see, and what you have tried.  Are you using Grub classic, or Grub 2 ?
    Are you sure?  Any chance you have updated in the last couple weeks?  You may have upgraded to Grub 2 without having built a new configuration on the boot partition.
    Also, are you in the regular shell or the rescue shell ?  https://wiki.archlinux.org/index.php/Gr … mand_shell
    Last edited by ewaller (2013-07-15 03:23:13)

  • Command Line Expert Needed: Deleted hostconfig (+ others) - boots to single user mode only !

    Mac OS X Tiger 10.4.11
    Deleted folders/files when logged in as root user. (don't ask!)
    On restart , wont boot up , get grey screen with white apple logo the black screen with command line: localhost:/ root#
    Started up from install cd - repaired permissions (ran twice) &amp; verified hard drive . All okay.
    Restarted but still goes back into command line with same localhost:/ root prompt
    Tried a bunch of different things as per advice on these boards - discovered that there is no hostconfig file.
    Restarted into verbose mode.
    Here are the lines that i think may reveal exactly what I messed up - and hopefully someone out there has an idea how I can try to fix without having to do an archive/install.
    BSM auditing present
    disabled
    rooting via boot-uuid from /chosen: (here a very long string of numbers and letters looks like a password)
    Then a long line about
    "got boot device = IOService:/MacRISC2PE ........."
    Then, the following
    "BSD root: disk0s3, major 14, minor 2"
    "CSRHIDTransitionDriver::stop"
    "IOBluetoothHCIController::start Idle Time Stopped"
    (AND HERE'S THE BIGGIE:)
    /etc/rc: line 93: /etc/hostconfig: No such file or directory
    Apr  1. 06:01:44 launched: /bin/sh on /etc/rc terminated abnormally, going into single user mode
    localhost:/ root#
    I'm pretty sure I messed thing up pretty well - was mainly network/server folders and files - definitely samba, which I think I deleted, and under "network" in the finder, I also might have deleted my computer from the server list
    As an aside in case this provides any insight, when I go to the terminal app when starting up from install cd, the prompt reads :
    "bash-2.05b"
    I'm also able to see the contents of my hard drive when using disk utility from install cd and and trying to "mount image" ---
    Everything looks intact in terms of folders/files in my user account, but in the /root folder, there's only /library - which is empty.
    Any help, insight, troubleshooting and even scolding - will be welcome! I need this thing booted
    Cheers

    I do not have a backup. Should I back up before I try doing a reinstall of the os x?
    That's also known as shutting the barn door after the horse has bolted.
    It can't hurt, but it's not going to help much.
    Camelot: when you say "apps and user content should stay intact" - doesn't sound very definitive. Are there any variables that come into play?
    No.. generally it's pretty reliable, but yours is an odd situation. I wouldn't expect to lose any user data, just CYA
    I do have a start up disk along with some apps that I created in retrospect many years ago ....(I think it's os x 10.2.8) Can I use this to boot up and then just navigate to my user files so I can get some things done that I need to?
    Unlikely. For one have you even tried restoring from your Retrospect backup? (it's not the most reliable system).
    Secondly, you can't boot from your Retrospect backup, so you'll need to restore that system to boot from it. Have you got a second disk to restore to (you do NOT want to restore 10.2.x over your 10.4.x system).
    in terms of "random deleted files" : not entirely random
    Ok, maybe not entire random, but it's also somewhat unknown. You need to have some idea of what files you're trying to restore, but if you haven't got them in a backup where are you going to get them from?
    You cannot just take old copies from your 10.2.x system and hope they'll work (in case that's what you're thinking).
    The BEST solution is to boot from the 10.4.x installer disk and let it do its thing.
    And for what its worth, Unauthorized access attempts, in and of themselves, are not a cause for concern since they were clearly caught by the OS. It's the access attempts that succeed (and are not logged) which are more of an issue.

  • Command line display disappears during boot [solved]

    I've brought my machine up to date with systemd, and have run into this latest problem.  I boot with syslinux.  My machine has started giving me kernel panics when I boot with the primary configuration, which had
    acpi=off
    in the append line, I believe to address this very problem.  If I boot with the fallback, which does not have this entry, I get a boot that I can access over ssh, but the command line display disappears after running through a few lines.  Commenting out the acpi language in the primary gives the same result as the fallback.
    If I can't boot with it in there, and can't see the screen with it out, what do I do?
    [edit]
    I was looking for some information on the boot process to explain what changes during the boot to cause the screen to go from visible to invisible.  When it used to boot, I remember a font change happening part way through the boot, but don't remember what caused it.  Searching for the boot process on the wiki only gives the systemd page, and I didn't find anything there that was helpful in this regard.
    I am downloading a live iso and will try booting with that to see if the display issues are present using that approach.
    [edit]
    Ok, it had nothing to do with acpi.  I was running the nvidia driver.  My machine has a processor with a gpu, and apparently it decided to hand off to my intel gpu, which has nothing attached to it, instead of sticking with the nvidia.  May have to do with KMS (wiki.archlinux.org/index.php/Kernel_Mode_Setting).  So I deleted the nvidia driver per the wiki instructions and added the nouveau driver, enabled the KMS per the instructions, and now I have a command prompt.
    Last edited by timm (2013-01-11 20:13:01)

    i did  systemd.unit=multi-user.target at the boot loader .  https://wiki.archlinux.org/index.php/Systemd  for more options

Maybe you are looking for