HOWTO: Install Arch for Newbies

Hello,
Yesterday was my fist installation of Arch and i've found that the informations are not very well combined for a newbie/new to arch, am not newbie to linux but am new to arch so i've spend quite time to figure out some things or to know some links, due to this fact i've decided to write an easy guide that combine the whole installation from Downloading Till getting an up & running Arch with Gnome
the HOWTO can be found here please i need your opinions/corrections so we can make it as easy as installing ubuntu for newbies

Try my gdm.conf, it's an unchanged one, and normally it would work
# GDM Configuration file. You can use gdmsetup program to graphically
# edit this, or you can optionally just edit this file by hand. Note that
# gdmsetup does not tweak every option here, just the ones most users
# would care about. Rest is for special setups and distro specific
# tweaks. If you edit this file, you should send the HUP or USR1 signal to
# the daemon so that it restarts: (Assuming you have not changed PidFile)
# kill -USR1 `cat /var/run/gdm.pid`
# (HUP will make gdm restart immediately while USR1 will make gdm not kill
# existing sessions and will only restart gdm after all users log out)
# You can also use the gdm-restart and gdm-safe-restart scripts which just
# do the above for you.
# For full reference documentation see the gnome help browser under
# GNOME|System category. You can also find the docs in HTML form on
# http://www.gnome.org/projects/gdm/
# NOTE: Some of these are commented out but still show their default values.
# If you wish to change them you must remove the '#' from the beginning of
# the line. The commented out lines are lines where the default might
# change in the future, so set them one way or another if you feel
# strongly about it.
# Have fun! - George
[daemon]
# Automatic login, if true the first local screen will automatically logged
# in as user as set with AutomaticLogin key.
AutomaticLoginEnable=false
AutomaticLogin=
# Timed login, useful for kiosks. Log in a certain user after a certain
# amount of time
TimedLoginEnable=false
TimedLogin=
TimedLoginDelay=30
# The gdm configuration program that is run from the login screen, you should
# probably leave this alone
#Configurator=/opt/gnome/sbin/gdmsetup --disable-sound --disable-crash-dialog
# The chooser program. Must output the chosen host on stdout, probably you
# should leave this alone
#Chooser=/opt/gnome/libexec/gdmchooser
# The greeter for local (non-xdmcp) logins. Change gdmlogin to gdmgreeter to
# get the new graphical greeter.
#Greeter=/opt/gnome/libexec/gdmlogin
# The greeter for xdmcp logins, usually you want a less graphically intensive
# greeter here so it's better to leave this with gdmlogin
#RemoteGreeter=/opt/gnome/libexec/gdmlogin
# Launch the greeter with an additional list of colon seperated gtk
# modules. This is useful for enabling additional feature support
# e.g. gnome accessibility framework. Only "trusted" modules should
# be allowed to minimise security holes
#AddGtkModules=false
# By default these are the accessibility modules
#GtkModulesList=gail:atk-bridge:/opt/gnome/lib/gtk-2.0/modules/libdwellmouselistener:/opt/gnome/lib/gtk-2.0/modules/libkeymouselistener
# Default path to set. The profile scripts will likely override this
DefaultPath=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/gnome/bin
# Default path for root. The profile scripts will likely override this
RootPath=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/gnome/sbin:/opt/gnome/bin
# If you are having trouble with using a single server for a long time and
# want gdm to kill/restart the server, turn this on
#AlwaysRestartServer=false
# User and group used for running gdm GUI applicaitons. By default this
# is set to user gdm and group gdm. This user/group should have very
# limited permissions and access to ony the gdm directories and files.
User=nobody
Group=gdm
# To try to kill all clients started at greeter time or in the Init script.
# doesn't always work, only if those clients have a window of their own
#KillInitClients=true
LogDir=/var/log/gdm
# You should probably never change this value unless you have a weird setup
PidFile=/var/run/gdm.pid
# Note that a post login script is run before a PreSession script.
# It is run after the login is successful and before any setup is
# run on behalf of the user
PostLoginScriptDir=/opt/gnome/etc/gdm/PostLogin/
PreSessionScriptDir=/opt/gnome/etc/gdm/PreSession/
PostSessionScriptDir=/opt/gnome/etc/gdm/PostSession/
DisplayInitDir=/opt/gnome/etc/gdm/Init
# Distributions: If you have some script that runs an X server in say
# VGA mode, allowing a login, could you please send it to me?
#FailsafeXServer=
# if X keeps crashing on us we run this script. The default one does a bunch
# of cool stuff to figure out what to tell the user and such and can
# run an X configuration program.
XKeepsCrashing=/opt/gnome/etc/gdm/XKeepsCrashing
# Reboot, Halt and suspend commands, you can add different commands
# separated by a semicolon and gdm will use the first one it can find
RebootCommand=/sbin/shutdown -r now "Rebooted from gdm menu."
HaltCommand=/sbin/shutdown -h now "Halted from gdm menu."
SuspendCommand=/usr/bin/apm --suspend
# Probably should not touch the below this is the standard setup
ServAuthDir=/opt/gnome/var/gdm
# This is our standard startup script. A bit different from a normal
# X session, but it shares a lot of stuff with that. See the provided
# default for more information.
BaseXsession=/opt/gnome/etc/gdm/Xsession
# This is a directory where .desktop files describing the sessions live
# It is really a PATH style variable since 2.4.4.2 to allow actual
# interoperability with KDM. Note that <sysconfdir>/dm/Sessions is there
# for backwards compatibility reasons with 2.4.4.x
SessionDesktopDir=/etc/X11/sessions/:/etc/dm/Sessions/:/usr/share/xsessions/:/opt/gnome/share/gdm/BuiltInSessions/:/opt/gnome/share/xsessions/
# This is the default .desktop session. One of the ones in SessionDesktopDir
#DefaultSession=gnome.desktop
# Better leave this blank and HOME will be used. You can use syntax ~/ below
# to indicate home directory of the user. You can also set this to something
# like /tmp if you don't want the authorizations to be in home directories.
# This is useful if you have NFS mounted home directories. Note that if this
# is the home directory the UserAuthFBDir will still be used in case the home
# directory is NFS, see security/NeverPlaceCookiesOnNFS to override this behaviour.
UserAuthDir=
# Fallback if home directory not writable
UserAuthFBDir=/tmp
UserAuthFile=.Xauthority
# The X server to use if we can't figure out what else to run.
StandardXServer=/usr/X11R6/bin/X
# The maximum number of flexible X servers to run.
#FlexibleXServers=5
# And after how many minutes should we reap the flexible server if there is
# no activity and no one logged on. Set to 0 to turn off the reaping.
# Does not affect Xnest flexiservers.
#FlexiReapDelayMinutes=5
# the X nest command
Xnest=/usr/X11R6/bin/Xnest -audit 0 -name Xnest
# Automatic VT allocation. Right now only works on Linux. This way
# we force X to use specific vts. turn VTAllocation to false if this
# is causing problems.
FirstVT=7
VTAllocation=true
# Should double login be treated with a warning (and possibility to change
# vts on linux and freebsd systems for console logins)
#DoubleLoginWarning=true
# Should a second login always resume the current session and
# switch vts on linux and freebsd systems for console logins
#AlwaysLoginCurrentSession=true
# If true then the last login information is printed to the user before
# being prompted for password. While this gives away some info on what
# users are on a system, it on the other hand should give the user an
# idea of when they logged in and if it doesn't seem kosher to them,
# they can just abort the login and contact the sysadmin (avoids running
# malicious startup scripts)
#DisplayLastLogin=false
# Program used to play sounds. Should not require any 'daemon' or anything
# like that as it will be run when no one is logged in yet.
#SoundProgram=/usr/bin/play
# These are the languages that the console cannot handle because of font
# issues. Here we mean the text console, not X. This is only used
# when there are errors to report and we cannot start X.
# This is the default:
#ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh
# This determines whether gdm will honor requests DYNAMIC requests from
# the gdmdynamic command.
#DynamicXServers=false
# This determines whether gdm will send notifications to the console
#ConsoleNotify=true
[security]
# If any distributions ship with this one off, they should be shot
# this is only local, so it's only for say kiosk use, when you
# want to minimize possibility of breakin
AllowRoot=false
# If you want to be paranoid, turn this one off
AllowRemoteRoot=false
# This will allow remote timed login
AllowRemoteAutoLogin=false
# 0 is the most restrictive, 1 allows group write permissions, 2 allows all
# write permissions
RelaxPermissions=0
# Check if directories are owned by logon user. Set to false, if you have, for
# example, home directories owned by some other user.
CheckDirOwner=true
# Number of seconds to wait after a bad login
#RetryDelay=1
# Maximum size of a file we wish to read. This makes it hard for a user to DoS
# us by using a large file.
#UserMaxFile=65536
# If true this will basically append -nolisten tcp to every X command line,
# a good default to have (why is this a "negative" setting? because if
# it is false, you could still not allow it by setting command line of
# any particular server). It's probably better to ship with this on
# since most users will not need this and it's more of a security risk
# then anything else.
# Note: Anytime we find a -query or -indirect on the command line we do
# not add a "-nolisten tcp", as then the query just wouldn't work, so
# this setting only affects truly local sessions.
DisallowTCP=true
# By default never place cookies if we "detect" NFS. We detect NFS
# by detecting "root-squashing". It seems bad practice to place
# cookies on things that go over the network by default and thus we
# don't do it by default. Sometimes you can however use safe remote
# filesystems where this is OK and you may want to have the cookie in your
# home directory.
#NeverPlaceCookiesOnNFS=true
# XDMCP is the protocol that allows remote login. If you want to log into
# gdm remotely (I'd never turn this on on open network, use ssh for such
# remote usage that). You can then run X with -query <thishost> to log in,
# or -indirect <thishost> to run a chooser. Look for the 'Terminal' server
# type at the bottom of this config file.
[xdmcp]
# Distributions: Ship with this off. It is never a safe thing to leave
# out on the net. Setting up /etc/hosts.allow and /etc/hosts.deny to only
# allow local access is another alternative but not the safest.
# Firewalling port 177 is the safest if you wish to have xdmcp on.
# Read the manual for more notes on the security of XDMCP.
Enable=false
# Honour indirect queries, we run a chooser for these, and then redirect
# the user to the chosen host. Otherwise we just log the user in locally.
#HonorIndirect=true
# Maximum pending requests
#MaxPending=4
#MaxPendingIndirect=4
# Maximum open XDMCP sessions at any point in time
#MaxSessions=16
# Maximum wait times
#MaxWait=15
#MaxWaitIndirect=15
# How many times can a person log in from a single host. Usually better to
# keep low to fend off DoS attacks by running many logins from a single
# host. This is now set at 2 since if the server crashes then gdm doesn't
# know for some time and wouldn't allow another session.
#DisplaysPerHost=2
# The number of seconds after which a non-responsive session is logged off.
# Better keep this low.
#PingIntervalSeconds=15
# The port. 177 is the standard port so better keep it that way
#Port=177
# Willing script, none is shipped and by default we'll send
# hostname system id. But if you supply something here, the
# output of this script will be sent as status of this host so that
# the chooser can display it. You could for example send load,
# or mail details for some user, or some such.
Willing=/opt/gnome/etc/gdm/Xwilling
[gui]
# The specific gtkrc file we use. It should be the full path to the gtkrc
# that we need. Unless you need a specific gtkrc that doesn't correspond to
# a specific theme, then just use the GtkTheme key
#GtkRC=/opt/gnome/share/themes/Default/gtk-2.0/gtkrc
# The GTK+ theme to use for the gui
#GtkTheme=Default
# If to allow changing the GTK+ (widget) theme from the greeter. Currently
# this only affects the standard greeter as the graphical greeter does
# not yet have this ability
#AllowGtkThemeChange=true
# Comma separated list of themes to allow. These must be the names of the
# themes installed in the standard locations for gtk themes. You can
# also specify 'all' to allow all installed themes. These should be just
# the basenames of the themes such as 'Thinice' or 'LowContrast'.
#GtkThemesToAllow=all
# Maximum size of an icon, larger icons are scaled down
#MaxIconWidth=128
#MaxIconHeight=128
[greeter]
# Greeter has a nice title bar that the user can move
#TitleBar=true
# Configuration is available from the system menu of the greeter
#ConfigAvailable=true
# Face browser is enabled. This only works currently for the
# standard greeter as it is not yet enabled in the graphical greeter.
Browser=false
# The default picture in the browser
#DefaultFace=/opt/gnome/share/pixmaps/nobody.png
# User ID's less than the MinimalUID value will not be included in the
# face browser or in the gdmselection list for Automatic/Timed login.
# They will not be displayed regardless of the settings for
# Include and Exclude.
MinimalUID=1000
# Users listed in Include will be included in the face browser and in
# the gdmsetup selection list for Automatic/Timed login. Users
# should be separated by commas.
#Include=
# Users listed in Exclude are excluded from the face browser and from
# the gdmsetup selection list for Automatic/Timed login. Excluded
# users will still be able to log in, but will have to type their
# username. Users should be separated by commas.
Exclude=bin,daemon,mail,nobody
# By default, an empty include list means display no users. By setting
# IncludeAll to true, the password file will be scanned and all users
# will be displayed except users excluded via the Exclude setting and
# user ID's less than MinimalUID. Scanning the password file can be
# slow on systems with large numbers of users and this feature should
# not be used in such environments. The setting of IncludeAll does
# nothing if Include is set to a non-empty value.
#IncludeAll=false
# If user or user.png exists in this dir it will be used as his picture
#GlobalFaceDir=/opt/gnome/share/pixmaps/faces/
# File which contains the locale we show to the user. Likely you want to use
# the one shipped with gdm and edit it. It is not a standard locale.alias file,
# although gdm will be able to read a standard locale.alias file as well.
#LocaleFile=/opt/gnome/etc/gdm/locale.alias
# Logo shown in the standard greeter
#Logo=/opt/gnome/share/pixmaps/gdm-foot-logo.png
# The standard greeter should shake if a user entered the wrong username or
# password. Kind of cool looking
#Quiver=true
# The Actions menu (formerly system menu) is shown in the greeter, this is the
# menu that contains reboot, shutdown, suspend, config and chooser. None of
# these is available if this is off. They can be turned off individually
# however
SystemMenu=true
# Should the chooser button be shown. If this is shown, GDM can drop into
# chooser mode which will run the xdmcp chooser locally and allow the user
# to connect to some remote host. Local XDMCP does not need to be enabled
# however
#ChooserButton=true
# Welcome is for all console logins and RemoteWelcome is for remote logins
# (through XDMCP).
# DefaultWelcome and DefaultRemoteWelcome set the string for Welcome
# to "Welcome" and for DefaultWelcome to "Welcome to %n", and properly
# translate the message to the appropriate language. Note that %n gets
# translated to the hostname of the machine. These default values can
# be overridden by setting DefaultWelcome and/or DefaultRemoteWelcome to
# false, and setting the Welcome and DefaultWelcome values as desired.
# Just make sure the strings are in utf-8 Note to distributors, if you
# wish to have a different Welcome string and wish to have this
# translated you can have entries such as "Welcome[cs]=Vitejte na %n".
DefaultWelcome=true
DefaultRemoteWelcome=true
#Welcome=Welcome
#RemoteWelcome=Welcome to %n
# Don't allow user to move the standard greeter window. Only makes sense
# if TitleBar is on
#LockPosition=false
# Set a position rather then just centering the window. If you enter
# negative values for the position it is taken as an offset from the
# right or bottom edge.
#SetPosition=false
#PositionX=0
#PositionY=0
# Xinerama screen we use to display the greeter on. Not for true
# multihead, currently only works for Xinerama.
#XineramaScreen=0
# Background settings for the standard greeter:
# Type can be 0=None, 1=Image, 2=Color
#BackgroundType=2
#BackgroundImage=
#BackgroundScaleToFit=true
#BackgroundColor=#76848F
# XDMCP session should only get a color, this is the sanest setting since
# you don't want to take up too much bandwidth
#BackgroundRemoteOnlyColor=true
# Program to run to draw the background in the standard greeter. Perhaps
# something like an xscreensaver hack or some such.
#BackgroundProgram=
# if this is true then the background program is run always, otherwise
# it is only run when the BackgroundType is 0 (None)
#RunBackgroundProgramAlways=false
# Show the Failsafe sessions. These are much MUCH nicer (focus for xterm for
# example) and more failsafe then those supplied by scripts so distros should
# use this rather then just running an xterm from a script.
#ShowGnomeFailsafeSession=true
#ShowXtermFailsafeSession=true
# Normally there is a session type called 'Last' that is shown which refers to
# the last session the user used. If off, we will be in 'switchdesk' mode where
# the session saving stuff is disabled in GDM
#ShowLastSession=true
# Always use 24 hour clock no matter what the locale.
#Use24Clock=false
# Use circles in the password field. Looks kind of cool actually,
# but only works with certain fonts.
#UseCirclesInEntry=false
# Do not show any visible feedback in the password field. This is standard
# for instance in console, xdm and ssh.
#UseInvisibleInEntry=false
# These two keys are for the new greeter. Circles is the standard
# shipped theme. If you want gdm to select a random theme from a list
# then provide a list that is delimited by /: to the GraphicalThemes key and
# set GraphicalThemeRand to true. Otherwise use GraphicalTheme and specify
# just one theme.
#GraphicalTheme=circles
#GraphicalThemes=circles/:happygnome
GraphicalThemeDir=/opt/gnome/share/gdm/themes/
GraphicalThemeRand=false
# If InfoMsgFile points to a file, the greeter will display the contents of the
# file in a modal dialog box before the user is allowed to log in.
#InfoMsgFile=
# If InfoMsgFile is present then InfoMsgFont can be used to specify the font
# to be used when displaying the contents of the file.
#InfoMsgFont=Sans 24
# If SoundOnLogin is true, then the greeter will beep when login is ready
# for user input. If SoundOnLogin is a file and the greeter finds the
# 'play' executable (see daemon/SoundProgram) it will play that file
# instead of just beeping
#SoundOnLogin=true
#SoundOnLoginFile=
# If SoundOnLoginSuccess, then the greeter will play a sound (as above)
# when a user successfully logs in
#SoundOnLoginSuccess=false
#SoundOnLoginSuccessFile=
# If SoundOnLoginFailure, then the greeter will play a sound (as above)
# when a user fails to log in
#SoundOnLoginFailure=false
#SoundOnLoginFailureFile=
# The chooser is what's displayed when a user wants an indirect XDMCP
# session, or selects Run XDMCP chooser from the system menu
[chooser]
# Default image for hosts
#DefaultHostImg=/opt/gnome/share/pixmaps/nohost.png
# Directory with host images, they are named by the hosts: host or host.png
HostImageDir=/opt/gnome/share/hosts/
# Time we scan for hosts (well only the time we tell the user we are
# scanning actually, we continue to listen even after this has
# expired)
#ScanTime=4
# A comma separated lists of hosts to automatically add (if they answer to
# a query of course). You can use this to reach hosts that broadcast cannot
# reach.
Hosts=
# Broadcast a query to get all hosts on the current network that answer
Broadcast=true
# Set it to true if you want to send a multicast query to hosts.
Multicast=false
# It is an IPv6 multicast address.It is hardcoded here and will be replaced when
# officially registered xdmcp multicast address of TBD will be available
#Multicast_Addr=ff02::1
# Allow adding random hosts to the list by typing in their names
#AllowAdd=true
[debug]
# This will enable debugging into the syslog, usually not neccessary
# and it creates a LOT of spew of random stuff to the syslog. However it
# can be useful in determining when something is going very wrong.
Enable=false
[servers]
# These are the standard servers. You can add as many you want here
# and they will always be started. Each line must start with a unique
# number and that will be the display number of that server. Usually just
# the 0 server is used.
0=Standard
#1=Standard
# Note the VTAllocation and FirstVT keys on linux and freebsd.
# Don't add any vt<number> arguments if VTAllocation is on, and set FirstVT to
# be the first vt available that your gettys don't grab (gettys are usually
# dumb and grab even a vt that has already been taken). Using 7 will work
# pretty much for all linux distributions. VTAllocation is not currently
# implemented on anything but linux and freebsd. Feel free to send patches.
# X servers will just not get any extra arguments then.
# If you want to run an X terminal you could add an X server such as this
#0=Terminal -query serverhostname
# or for a chooser (optionally serverhostname could be localhost)
#0=Terminal -indirect serverhostname
# If you wish to run the XDMCP chooser on the local display use the following
# line
#0=Chooser
## Note:
# is your X server not listening to TCP requests? Perhaps you should look
# at the security/DisallowTCP setting!
# Definition of the standard X server.
[server-Standard]
name=Standard server
command=/usr/X11R6/bin/X -audit 0
flexible=true
# To use this server type you should add -query host or -indirect host
# to the command line
[server-Terminal]
name=Terminal server
# Add -terminate to make things behave more nicely
command=/usr/X11R6/bin/X -audit 0 -terminate
# Make this not appear in the flexible servers (we need extra params
# anyway, and terminate would be bad for xdmcp choosing). You can
# make a terminal server flexible, but not with an indirect query.
# If you need flexible indirect query server, then you must get rid
# of the -terminate and the only way to kill the flexible server will
# then be by Ctrl-Alt-Backspace
flexible=false
# Not local, we do not handle the logins for this X server
handled=false
# To use this server type you should add -query host or -indirect host
# to the command line
[server-Chooser]
name=Chooser server
command=/usr/X11R6/bin/X -audit 0
# Make this not appear in the flexible servers for now, but if you
# wish to allow a chooser server then make this true. This is the
# only way to make a flexible chooser server that behaves nicely.
flexible=false
# Run the chooser instead of the greeter. When the user chooses a
# machine they will get this same server but run with
# "-terminate -query hostname"
chooser=true

Similar Messages

  • How to install Arch for dual-boot with Win 7 (on 2 hard drives)?

    Hello,
    the TLDR first: how exactly should I proceed when setting up GRUB for 2 hard drives to dual-boot Arch (64 bit)and Win 7 (64 bit)?
    Long version: So, I have the following hard drive & partition layout:
    On my first hard drive (250 GB big) I have: Win 7 64 bit, all the programs for Windows and of course the EFI partition
    My second hard drive is 1 TB big and formatted in NTFS and it only contains data. It has 2 partitions, one is about 750 GB big and used for simple storage.
    Sidenote 1: sometimes my disk management (Windows' own gparted) shows either the little disk or the big one as disk 0. Don't know what exactly this means, but I have never ever experienced any problems whatsoever during use.
    Sidenote 2: the UEFI motherboard (ASRock H67M) cannot boot into Legacy mode.
    I want to install Arch on a ~200 GB partition on the second hard drive (the one with 1 TB). (click here if you want to see a screenshot) I am posting this because I am confused with how exactly I should deal with the whole "2 hdds & UEFI" thing.
    So how exactly should I proceed when setting up GRUB for this setup?
    For partitioning I suppose I would have to use fdisk or cgdisk. I used cgdisk before and found it to be straightforward. Then, because I have experienced my fair share of problems with rEFInd, I'd like to use GRUB.
    Last edited by jones (2013-06-29 14:36:56)

    First thing you should do is become familiar with your motherboard.
    http://www.asrock.com/mb/manual.asp?Model=H67M
    This will probably help you out in understanding the sidenote 1 thingie (hdd's on sata3 and/or sata2 connectors)
    As on sidenote 2, according to the manual it seems to be possible to boot legacy mode,  see Storage Configuration.

  • [SOLVED]....install Arch, for the first time, am i doing it right?

    The first try, it failed at grub boot(froze with blank screen), so now I'm going to install for the 2nd time and I need your help to confirm if the grub installation procedure below is correct.. (Thinkpad x61s-64bit machine)
    # mkinitcpio -p linux
    # pacman -S grub-bios bash-completion os-prober
    # grub-install --target=i386-pc --recheck /dev/sda
    # cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
    # grub-mkconfig -o /boot/grub/grub.cfg
    # exit
    # umount -R /mnt
    # reboot
    ..or should i just use Syslinux instead? There won't be any other OS on the disk except there's a partition i made previously(ext 4) that i used for file storage purposes(music,video,docs etc) and the said partition now reside in sda4 and do not want to delete that as ive got so much stuff in it and my external HD is full. so i'll have to install Arch on sda1/2/3.
    my partitioning scheme would be 2g swap, 20g root and 30g home.
    Thank you
    Last edited by MrPotato (2014-01-06 04:46:08)

    MrPotato wrote:
    The first try, it failed at grub boot(froze with blank screen), so now I'm going to install for the 2nd time and I need your help to confirm if the grub installation procedure below is correct.. (Thinkpad x61s-64bit machine)
    # mkinitcpio -p linux
    # pacman -S grub-bios bash-completion os-prober
    # grub-install --target=i386-pc --recheck /dev/sda
    # cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
    # grub-mkconfig -o /boot/grub/grub.cfg
    # exit
    # umount -R /mnt
    # reboot
    ..or should i just use Syslinux instead? There won't be any other OS on the disk except there's a partition i made previously(ext 4) that i used for file storage purposes(music,video,docs etc) and the said partition now reside in sda4 and do not want to delete that as ive got so much stuff in it and my external HD is full. so i'll have to install Arch on sda1/2/3.
    my partitioning scheme would be 2g swap, 20g root and 30g home.
    Thank you
    You could just use syslinux, but i guess you just had a bad timing with your installation there are a few bugs present with grub at the moment, which are actually already fixed upstream, but not yet available from the official arch repositories. Did you notice any bug messages when running "grub-mkconfig" ? There were probably some "syntax-errors", but they can be easily fixed (https://bugs.archlinux.org/task/38234?project=1&cat[0]=31&string=grub); the method with "GRUB_DISABLE_SUBMENU=y" works fine and you could fix it by "chrooting" into your system again from the live-installation-cd/usb. Alternatively you could enable the testing-repos for installing grub; this version works without the syntax errors, but there is another bug with multiple kernel-entries So the first way would be probably the best way to fix grub at the moment.
    Last edited by tumas (2014-01-05 15:57:54)

  • [HOWTO] Installing Arch Linux stable release on Acer Aspire One 522

    [This is a work on progress and my first howto ever]
    These steps will teach you how to install ArchLinux x64 stable release (currently 2010.05) on Acer Aspire One 522 from an existing ArchLinux (your desktop computer)
    As you need a 2.6.37+ kernel to make networking work on the AO522, installing stable release as is won't work.
    This Howto borns with the intention to address this problem.
    You need to be familiarized with Linux internals to follow this howto.
    (Expect this howto to become useless with new stable releases of ArchLinux.)
    Remember to make a backup of your Windows 7 Starter system before installing ArchLinux.
    I did a full raw copy of the harddisk by using systemrescuecd, an external harddisk and dd utility:
    Just boot with systemrescuecd
    Mount your external harddisk on /mnt/floppy for example
    Clone harddisk with: dd if=/dev/sda |gzip -c > /mnt/floppy/ao522.img
    This process took me a lot of time since my external harddisk is USB-1 (almost an entire evening)
    Result image was about 22GB size
    This image will restore partition table, boot sector and all data if things go wrong.
    I followed some of the steps from this guide: https://wiki.archlinux.org/index.php/In … ting_Linux
    If you have some Gentoo Linux experience you will find those steps really familiar.
    You will need 2 USB pendrives or similar storage options.
    One is needed to boot into your netbook, and the other to store our custom archlinux build.
    Making an updated ArchLinux system
    1) Make a local dir on your existing linux system
    # mkdir ./newarch
    2) Install pacman database on it
    # pacman -Sy -r ./newarch
    3) Install base system
    # pacman -S base -r ./newarch
    4) Let's chroot inside
    # cp /etc/resolv.conf ./newarch/etc/
    # cp /etc/pacman.d/mirrorlist ./newarch/etc/pacman.d
    # mount -t proc proc ./newarch/proc
    # mount -t sysfs sys ./newarch/sys
    # mount -o bind /dev ./newarch/dev
    # chroot ./newarch /bin/bash
    5) Edit configuration files
    # nano -w /etc/rc.conf
    # nano -w /etc/hosts
    # nano -w /etc/mkinitcpio.conf
    Forget /etc/fstab for now since you don't know what partitions to use yet
    6) Generate kernel image
    # mkinitcpio -p kernel26
    7) Generate locales
    # nano -w /etc/locale.gen
    # locale-gen
    8) Make a tarball with our custom ArchLinux
    # exit
    # umount ./newarch/proc
    # umount ./newarch/dev
    # umount ./newarch/sys
    # tar -cvpf newarch.tar ./newarch
    9) Copy this tarball to an USB pendrive or external harddisk
    10) Boot your netbook with a Linux bootable USB stick (I used systemrescuecd, and remember to pick the x64 bit kernel at grub screen)
    You can use any linux distribution with usb bootable options. I suppose ArchLinux works too
    To install SystemRescueCD on an USB stick follow this tutorial -> SystemRescueCD on usb stick
    Insert the usb stick on your netbook, switch on, hit F2 to enter BIOS menu, and choose to boot from USB as first option. Save and Exit.
    You should be booting into SystemRescueCD without any problem.
    After initialization you will end in a root prompt.
    11) Let's partition the disk
    You will find 3 partitions if this is your first time:
    /dev/sda1 2048 29362175 14680064 27 Hidden NTFS WinRE
    /dev/sda2 * 29362176 29566975 102400 7 HPFS/NTFS/exFAT
    /dev/sda3 29566976 488397167 229312696 7 HPFS/NTFS/exFAT
    My recomendation is to leave sda1 and sda2 intact, as they have the recovery information to restore Windows 7 Starter
    You have plenty of space with sda3, about 230G.
    So run fdisk/cfdisk and delete /dev/sda3
    Now create a 100M partition for boot
    Now create a Extended partition with all the space left
    Now create a 1GB logical partition for swap
    Now create a 10-15 GB  logical partition for root system
    And finally a logical partition for our home partition with all space left
    Your partition table should look like this:
    /dev/sda1 2048 29362175 14680064 27 Hidden NTFS WinRE
    /dev/sda2 * 29362176 29566975 102400 7 HPFS/NTFS/exFAT
    /dev/sda3 29566976 29771775 102400 83 Linux
    /dev/sda4 29771776 488397167 229312696 5 Extended
    /dev/sda5 29773824 31821823 1024000 83 Linux
    /dev/sda6 31823872 63281151 15728640 83 Linux
    /dev/sda7 63283200 488397167 212556984 83 Linux
    12) Create filesystems
    I choosed ext2 for boot, and reiserfs for root and home partitions.
    # mke2fs /dev/sda3
    # mkreiserfs /dev/sda6
    # mkreiserfs /dev/sda7
    # mkswap /dev/sda5
    13) Mount partitions
    # mkdir arch
    # mount /dev/sda6 arch
    # mkdir arch/boot
    # mount /dev/sda3 arch/boot
    # mkdir arch/home
    # mount /dev/sda7 arch/home
    14) Copy our custom ArchLinux build on it
    # mount /dev/sdb1 /mnt/floppy (for example)
    # cd arch
    # tar -xvpf /mnt/flopy/newarch.tar
    15) Configure /etc/fstab
    Mine is as follows:
    devpts /dev/pts devpts defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid 0 0
    /dev/sda3 /boot ext2 defaults 0 1
    /dev/sda6 / reiserfs defaults 0 1
    /dev/sda7 /home reiserfs defaults 0 1
    /dev/sda5 swap swap defaults 0 0
    16) Chroot in your new system
    # mount -t proc proc ./proc
    # mount -t sysfs sys ./sys
    # mount -o bind /dev ./dev
    # chroot ./ /bin/bash
    17) Install grub
    # grub-install
    Edit /boot/grub/menu.lst to suit your needs
    Mine looks like this:
    timeout 5
    default 0
    color light-blue/black light-cyan/blue
    title Arch Linux
    root (hd0,2)
    kernel /vmlinuz26 root=/dev/sda6 ro
    initrd /kernel26.img
    title Arch Linux Fallback
    root (hd0,2)
    kernel /vmlinuz26 root=/dev/sda6 ro
    initrd /kernel26-fallback.img
    title Windows 7 Recovery
    rootnoverify (hd0,0)
    makeactive
    chainloader +1
    As you see, you can restore Windows 7 Starter from Grub.
    18) Change root password
    # passwd
    19) Add a regular  user account
    # useradd -G video,audio,users -m username
    # passwd username
    20) You're done!
    # exit
    # cd ..
    # umount ./arch/proc
    # umount ./arch/dev
    # umount ./arch/sys
    # umount ./arch/boot
    # umount ./arch/
    # reboot
    Remove the usb stick from your netbook.
    If all went ok, you will be inside your new stable and updated ArchLinux system
    Next post is reserved for software configurations specific to the Acer Aspire One 522
    Last edited by tigrezno (2011-04-20 12:22:38)

    Using acpid to achieve the following:
    - Change screen brightness when operating in battery mode
    - Power off when the power button is pressed
    - Suspend when the lid is down
    - Reduce CPU frequency speed to maximize battery usage
    Remember that system suspend is only supported by ati free driver xf86-video-ati
    1) Install acpid daemon and cpufrequtils
    # pacman -S apcid cpufrequtils
    2) edit acpid handler script
    # nano -w /etc/acpi/handler.sh
    Change the following section:
    ac_adapter)
    case "$2" in
    AC)
    case "$4" in
    00000000)
    echo -n $minspeed >$setspeed
    #/etc/laptop-mode/laptop-mode start
    00000001)
    echo -n $maxspeed >$setspeed
    #/etc/laptop-mode/laptop-mode stop
    esac
    *) logger "ACPI action undefined: $2" ;;
    esac
    for:
    ac_adapter)
    case "$2" in
    ACAD)
    case "$4" in
    00000000)
    echo 3 > /sys/devices/virtual/backlight/acpi_video0/brightness
    cpufreq-set -c 0 -f 800Mhz
    cpufreq-set -c 1 -f 800Mhz
    00000001)
    echo 9 > /sys/devices/virtual/backlight/acpi_video0/brightness
    cpufreq-set -c 0 -f 1000Mhz
    cpufreq-set -c 1 -f 1000Mhz
    esac
    *) logger "ACPI action undefined: $2" ;;
    esac
    Make sure you changed AC) for ACAD)
    Now change this other section:
    button/power)
    #echo "PowerButton pressed!">/dev/tty5
    case "$2" in
    PWRF) logger "PowerButton pressed: $2" ;;
    *) logger "ACPI action undefined: $2" ;;
    esac
    with:
    button/power)
    #echo "PowerButton pressed!">/dev/tty5
    case "$2" in
    PWRF) poweroff ;;
    *) logger "ACPI action undefined: $2" ;;
    esac
    Change:
    button/lid)
    #echo "LID switched!">/dev/tty5
    logger "ACPI group/action undefined: $1 / $2"
    for:
    button/lid)
    pm-suspend && /etc/rc.d/network restart
    logger "ACPI group/action undefined: $1 / $2"
    Network restart is used because wlan0 will disconnect from AP after some time. You can try using iwconfig wlan0 essid <ap> key <key> instead of the network script, but haven't tested it myself.
    3) Start acpid and load modules
    # modprobe powernow-k8
    # /etc/rc.d/acpid start
    Add "acpid" to DAEMONS in /etc/rc.conf to start on boot
    Add "powernow-k8" to the modules sections on /etc/rc.conf to load at boot
    Stopping system freezes due to ethernet driver
    The only way people have found to avoid freezes is by blacklisting atheros kernel drivers.
    To do it at boot just edit /etc/rc.conf and change the MODULES line as this:
    MODULES=(!ath9k !atl1c)
    Reboot and you're done, but remember to not press the Wifi key, because it can freeze your system.
    Correctly starting wireless at boot
    I've found that standard scripts wont load properly my wireless lan. It gave an error telling you to use the WIRELESS_TIMEOUT variable and such.
    To solve this, edit /etc/rc.d/network script and change the wi_up function by adding a second iwconfig command like this:
    wi_up()
    eval iwcfg="\$wlan_${1}"
    [[ ! $iwcfg ]] && return 0
    /usr/sbin/iwconfig $iwcfg
    [[ $WIRELESS_TIMEOUT ]] || WIRELESS_TIMEOUT=2
    sleep $WIRELESS_TIMEOUT
    /usr/sbin/iwconfig $iwcfg
    bssid=$(iwgetid $1 -ra)
    It will do the trick and will start at boot correctly. This is not a solution but a fix.
    Adjust Touchpad to disable false taps
    What I did here is defining an area to be ignored. This area are 3 rectangles on top, left and right of the touchpad.
    This means you can write and press space without having the cursor click out of the window and such.
    # synclient AreaLeftEdge=150
    # synclient AreaRightEdge=1300
    # synclient AreaTopEdge=300
    Also, add it to your /etc/X11/xorg.conf.d/10-evdev.conf:
    Section "InputClass"
    Identifier "evdev touchpad catchall"
    MatchIsTouchpad "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    Option "AreaTopEdge" "300"
    Option "AreaLeftEdge" "150"
    Option "AreaRightEdge" "1300"
    EndSection
    You can play with those values. They just work for me.
    Last edited by tigrezno (2011-04-23 13:49:48)

  • Howto install Arch from iso (without buring CD) -unable to chroot ...

    Hi.
    I have successfully used the method to install from another linux partition in the past -  as outlined  here - http://wiki.archlinux.org/index.php/Ins … ting_Linux
    - However I want to install the X86_64 version and my current machine doesn't have a pre-existing 64bit distro to chroot from....
    I do not want to use floppy or cd to install - I always install from iso now, managed to get Fedora,Ubuntu, Gentoo and opensuse to install without burning the iso - Installing from iso is usually quicker and less prone to errors.........
    I've tried the old method to boot from iso - here - http://wiki.archlinux.org/index.php/Fas … nux_System
    However when I boot I get this
    :: Scanning for boot cdrom device...
    Failed to mount /dev/cd/cdrom-sr0
    Failed to mount /dev/cd/cdrw-sr0
    Failed to mount /dev/cd/dvd-sr0
    ERROR: cannot find booted cdrom device, cannot continue...
    Kernel panic - not syncing: Attempted to kill init!
    Below is my grub menu.lst
    title ArchCD
    kernel (hd0,5)/boot/vmlinuz26 root=/dev/sda6 BOOTMEDIA=cd
    initrd (hd0,5)/boot/archlive.img
    Also tried  (and various other combinations)
    title ArchCD
    kernel (hd0,5)/boot/vmlinuz26 root=/dev/sda6 BOOTMEDIA=cd  lang=en locale=en_US.UTF-8 ramdisk_size=75%
    initrd (hd0,5)/boot/archlive.img
    Has anyone got any ideas ?
    Cheers

    You could try something like UNetbootin.

  • [SOLVED] can't build an AUR package while installing Arch

    So I am nearly there installing Arch for the first time. And I will start with saying that I am really sorry if I missed the answer to my problem but I have had a look around the documentation and the general webz for something regarding this problem and haven't found anything.
    I am trying to set my wireless connection up but I apparently need the AUR b43-firmware package installed for my Broadcom BCM4322 [14e4:432b] to be functional.
    So I follow the documentation to install an AUR package, but I am stuck at the building stage as makepkg does not allow me to build if I am root, and I am root by default while installing/configuring Arch...
    What should I do to build and install that package so I have a wireless connection later on?
    Cheers
    Last edited by chtfn (2015-03-21 14:11:12)

    I am connected to the wired network, and I followed the steps to make it persistent for later, but I just wanted to go through the wireless stuff too to be extra sure I will be able to connect to the Internet later on. As it is the first time I install Arch, I am trying to be extra cautious, and having that security would make me feel more comfortable! Plus, I am keen to learn how to do those things from the command line.
    Isn't there a way to switch to a normal user just for a command, and automatically reverting back to root when that action is finished? Just like sudo but the other way round

  • Install Arch over Mint on laptop

    So I decided to dabble with Arch in Virtualbox and now I've decided that I want to install my .iso of Arch over my Mint partition. So I know there is a tutorial on the wiki on how to make my version into an .iso which shouldn't be an issue for me, but I just want to verify with you folks if I'll be doing this right on my laptop.
    I have 3 partitions right now on a 750GB HDD:
    500(ish)GB Windows 7 partition (sadly, it can't be shrunk anymore)
    15GB to a recovery partition for Windows
    then 100(ish)GB remaining for Linux Mint 16
    My thoughts are to back up any data I want to keep and should I just load up my .iso from a flash drive and install Arch like I would have in a VM? Would cfdisk show all my partitions and give me the chance to just erase my current Linux partition? Not sure how I should go about all of this...or would it be best just to redo the process from scratch? All I have installed really is the base Arch install, alsa, and XFCE.
    EDIT:
    Edited to avoid confusion on my 100GB Linux partition
    Last edited by stratacast1 (2014-01-06 23:00:38)

    karol wrote:You can just use the stock Arch iso.
    How are you expecting to have 2 Linux systems on one partition? I don't recall our wiki saying you could do anything like this :-) Create a new partition, format it and install arch in there.
    Okay I'll do that! I meant to say that I'll be reformatting my Linux Mint partition and putting Arch there instead I could have sworn I read something like that, or at least somewhere on the internet..but either way, I think I'll just do what you said! I think it'd be great to try installing Arch for the 4th time haha! Helps me memorize how to use the OS better!
    Since I'll be running Arch on the actual machine rather than a VM, will I eventually have to install drivers for my wireless NIC? I was thinking I'd install Arch on a wired connection so I didn't have to worry about my slow download speeds

  • Installing Arch on a RAID (for dummies)

    Playing with RAID's is fun for all the family, and makes things go faster.
    this is how I (re)installed Arch Linux, in a simple RAID configuration.
    Ingredients
    ===========
    1. Two 160GB drives
    2. Arch Linux CD (Dont Panic)
    Planning
    ========
    1. root partition on a RAID 1 setup (mirroring)
    2. home partition on a RAID 0 setup (striping)
    3. swap partition on a RAID 0 setup (striping)
    in this kinda setup, one disk can fry, but the system will still boot and function normally.
    home will be lost for ever, but I always back it up anyway (and so should you).
    *Important* - make sure your two IDE drives are not connected to the same cable, setup one as a primary master and the second as a secondary master.
    The works
    =========
    1. Boot the machine using the setup CD.
    2. Using cfdisk, partition the two drives exactly the same:
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *           1        4863    39062016   83  Linux
    /dev/sda2            4864       17021    97659135   83  Linux
    /dev/sda3           17022       17083      498015   82  Linux swap / Solaris
    I chose 40GB for root, 100GB for home (results in 200GB), and 1GB for swap.
    Do exactly the same on the second drive /dev/sdb
    3. create the RAIDs using mdadm:
    modprob raid1
    modprob raid0
    mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1
    mdadm --create /dev/md1 --level=0 --raid-devices=2 /dev/sda2 /dev/sdb2
    mdadm --create /dev/md2 --level=0 --raid-devices=2 /dev/sda3 /dev/sdb3
    4. create filesystems on the partitions:
    mkfs.xfs /dev/md0
    mkfs.xfs /dev/md1
    mkswap /dev/md2
    5. mount the root partition on /mnt
    mount /dev/md0 /mnt
    6. start the setup program
    /arch/setup
    7. select all base packages
    8. install packages
    9. configure:
    choose configure system and then, edit mkinitcpio.conf modules section:
    MODULES="ata_generic ata_piix raid1 raid0 xfs"
    In this line, I only added "raid1 raid0 xfs" to the modules.
    then, edit mkinitcpio.conf hooks section, and add the RAID stuff after that:
    HOOKS="base udev raid autodetect pata scsi sata usbinput keymap filesystems"
    md=0,/dev/sda1,/dev/sdb1
    md=1,/dev/sda2,/dev/sdb2
    md=2,/dev/sda3,/dev/sdb3
    In the hooks line, I have added the raid hook before autodetect
    10. install the kernel
    choose install kernel from the menu.
    11. Install grub
    choose install bootloader then grub
    edit the grub entry to:
    # (0) Arch Linux
    title  Arch Linux  [/boot/vmlinuz26]
    root   (hd0,0)
    kernel /boot/vmlinuz26 root=/dev/md0 ro md=0,/dev/sda1,/dev/sdb1
    initrd /boot/kernel26.img
    install grub to /dev/sda
    when prompted about root partition choose /dev/sda1
    when prompted about RAID stuff choose no
    do exactly the same on /dev/sdb
    12. exit the setup program
    13. fix mdadm.conf
    mdadm -D --scan >>/mnt/etc/mdadm.conf
    14. fix fstab
    add this to /mnt/etc/fstab:
    /dev/md0                /       xfs     defaults                0       0
    /dev/md1                /home   xfs     defaults                0       0
    /dev/md2                swap    swap    defaults                0       0
    15. reboot and install the rest of the system
    16. make sure all is well:
    cat /proc/mdstat
    Personalities : [raid1] [raid0] [linear] [multipath] [raid6] [raid5] [raid4] [raid10]
    md2 : active raid0 sda3[0] sdb3[1]
          995840 blocks 64k chunks
    md1 : active raid0 sda2[0] sdb2[1]
          195318016 blocks 64k chunks
    md0 : active raid1 sdb1[1] sda1[0]
          39061952 blocks [2/2] [UU]
    mount
    /dev/md0 on / type xfs (rw)
    /dev/md1 on /home type xfs (rw)
    make sure swap is on:
    cat /proc/swaps
    Filename                                Type            Size    Used    Priority
    /dev/md2                                partition       995832  0       -1
    17. If things go wrong, you can reassemble the RAIDs after booting from the setup CD, dont recreate them:
    mdadm --reassemble /dev/md0 /dev/sda1 /dev/sdb1
    for more reading, consult the WIKI: http://wiki.archlinux.org/index.php/Ins … AID_or_LVM
    Last edited by daf666 (2008-03-08 20:36:42)

    Sorry for the late reply clickit, I guess you might have fixed it already.
    There is a mistake in the guide, I will correct it now, the types in these lines should be --level=0
    mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sda2 /dev/sdb2
    mdadm --create /dev/md2 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3
    Very sorry about that, but that does not cause your problem, because it would have created a mirror RAID instaed of a stripe.
    Your BIOS has nothing to do with the Linux software RAID, the RAID settings you see in BIOS are probably to enable the on-board RAID controller you have.
    The grub part is tricky, you have to make sure whats in the configuration file is according to the setup that you have (not just copy from the guide).
    Also keep in mind that if you have SATA, things might look different and the setup might need to be different.
    PS - regarding swap, since I wrote the guide I removed the swap space and instead I use a swap file on the RAID0.. I guess it the same because my system  rarely uses swap anyway
    Last edited by daf666 (2007-10-17 21:31:59)

  • Archwiz Script for installing Arch Linux

    I created a new Bash Script Project called Archwiz, located on  github flesh/archwiz ,
    its still in Beta for a few reasons, I never figured out how to get computer translations working in the script so I can Localize it, and I never figured out all the details to get an AUR custom repo working and lastly I didn't get the Asynchronous downloads to work right, so there are all disabled in this script.
    This script was a fork of another script found here Archlinux Ultimate Install Script.
    The Script itself has several files, the wizard.sh is a library, that allow programmers to use this library as an API for writing scripts, so its usefully to anyone that wants an API to write Bash Scripts, but the script itself scripts a script that is saved as configuration files, then executes the script inside itself, so you can look at all the configuration files before running it.
    The script was written for use by anyone, but mostly targets programmers like myself who need to setup a machine to use as a work station and want it set up a certain way every time, although this script is far from finished, I have a lot of tweaking to do to it before it would be completely there, but as it is, I can get up and running on a machine with little effort, so this make it ideal for a Linux Administrator who has to install thousands of OS's and have them configured all the same way, but works great for someone just wanting to install Arch Linux.
    The Project is Self Documenting and Self Localizing, although currently only English works, but the po files are there, so it would be easy enough if you wanted to localize it; but the computer translation function I started would be the correct way to do this.
    The scripts makes use of a custom repo, so remove it when finished, the script should do this for you, but just to let you know, it downloads the core to the flash drive, this way it can install very fast, once you install it one, it has all the files on it to install on another computer without an Internet connection, well at least that was my thinking, I never did get the AUR custom repo to work, but the idea is to have all the files on the flash so you do not need to use up bandwidth installing Arch Linux on a new machine, just install it, then run pacman updates.
    The Idea of a Wizard is to make the life of those installing an OS, much easier, they have the Option to do a Custom install, or a Wizard install, even an Automatic install to pre-configure machines.
    The script determines if you have UEFI Bios or not, and formats and configures the Hard Drive correctly, and gives you full control over the partitioning of the drive, within the bounds of the tools used, so its very flexible, it uses systemd, so boot time on my machine is 10 seconds flat, and that's because I mount a lot of network drives and map them at boot time, I got 2 seconds boot time with mounting, so the packages are not perfect, but they do work.
    I only tested GDM, since I installed every Desktop Manager and configuration for my needs, this was the only one I got to work for all of them, but I normally use KDE or Mate, but I ran into issues with Mate and went back to KDE, so I could get back to work.
    This script was designed to Format the Drive you install it to, so do not use this on a Partitioned Drive,  it will format the hard drive, so you are warned once more during the install, but this could be fixed, I had to abandon the project to finish another, so the script is as it is, but could give someone a great start if they want to folk it and finish it, so fork me.
    See the help.html for details.
    Last edited by Flesh (2013-02-28 00:31:54)

    Moving to Community Contributions...

  • Install arch on a read-only filesystem

    Hi to all, I have an idea about installing arch in a particular way, a way that makes the system more secure.
    I want to install a host archlinux system on a hard disk or ssd but I want no data can be written to the storage. The host system will have a predefined set of programs and should use a ramdisk to store temporary data. It is something very similar to a ISO.
    The real computation will be handled through a series of virtualbox instances of linux ( the virtualbox images will be stored on an external hard disk, a read/write volume ).
    How could I achieve this? Through unionfs? AUFS? or some other thing?
    Last edited by pabloski (2011-02-16 16:18:11)

    I want to mount my sda2 read-only and union it with a tmpfs, so the machine is secure and the file system is the same every boot.
    I installed aufs3 with 3.2.6-1-aufs_friendly, I made a hook (as some-guy94 adviced), but it doesn't work.
    The code is:
    1. mkdir -p /root/ro /root/rw
    2. mount /dev/sda2 /root/ro
    3. mount -t tmpfs root.rw /root/rw
    4. mount -t aufs -o "dirs=/root/rw=rw:/root/ro=ro" root.union /
    At 2. it says: "mount: mounting /dev/sda2 on /root/ro failed: No such file or directory" Both files exist - I can list them just before the mount.
    3. & 4. work, but it doesn't matter as sda2 gets mounted rw on / right after (by initramfs's init, I gues).
    Can you help me with this, or point some useful howtos?
    Btw: is there a better way of debugging a hook, other than making the image and rebooting each change?
    Update: This is how they did it in larch: http://git.berlios.de/cgi-bin/gitweb.cg … cpio/hooks
    mount -t ext3 /dev/sda2 /root/ro works now.
    I used exec /sbin/switch_root as in larch3 hook and for loop from /lib/initcpio/init:109 to move /proc /dev /sys /run to the new root
    So the union mount works just fine now, my sda2/sbin/init & sda2/etc/rc.sysinit run, but the latter fails with following:
    * Mounting Root Read-Only - this is actually quite acceptable
    * Starting UDev Daemon
    * Loading Modules
    * Remounting Root Read/Write - acceptable as well
    After boot X opens and system freezes immediately (no reaction to keyboard, doesn't ping). No useful information in logs. I don't think system can run well without udev/modules. So this is udev not liking / mounted rw (as tmpfs is rw) or maybe /dev /proc /sys /run fault.
    I tried to make union mount only in rc.sysinit when /dev/sda2 is already mounted on /, but mount --move / other-dir fails.
    Any ideas what can be wrong?
    My code:
    run_hook ()
    read -p "Union mount root (y/N)? " answer
    if [[ "$answer" == "y" ]]; then
    modprobe aufs
    ro="/root/ro"
    rw="/root/rw"
    un="/root/un"
    rob="${un}/ro"
    rwb="${un}/rw"
    mkdir -p $ro $rw $un
    mount -t ext3 /dev/sda2 $ro
    mount -t tmpfs -o "size=20%" root.rw $rw
    mount -t aufs -o "dirs=${rw}=rw:${ro}=ro" root.union $un
    mkdir -p $rob $rwb
    mount --bind $ro $rob
    mount --bind $rw $rwb
    mkdir ${un}/media
    mkdir ${un}/sys
    mkdir ${un}/proc
    mkdir ${un}/dev
    /bin/mknod ${un}/dev/console c 5 1
    echo "rootfs / rootfs rw 0 0" >${un}/etc/mtab
    [ -z "${init}" ] && init="/sbin/init"
    if [ -e "${un}/${init}" ]; then
    mount
    read
    for d in proc sys dev run; do
    if [ -d ${un}/${d} ]; then
    mount --move /${d} ${un}/${d}
    else
    umount /${d}
    fi
    done
    exec /sbin/switch_root -c /dev/console ${un} ${init} ${CMDLINE}
    fi
    fi
    Last edited by kaos (2012-02-22 17:14:18)

  • Cannot install Arch on raid0 (kernel panics)

    I followed the Howto in the wiki to install Arch on a Raid 0 array, but when trying to boot I keep getting errors that boil down to "no filesystem could mount root" followed by a kernel panic.
    I modified the howto to my needs:
    - created a Raid 0 array using mdadm from logical partitions /dev/sda7 and /dev/sdb7. /dev/sda6 will be /boot and /dev/sdb6 will be swap (both not in raid, of course)
    - Put filesystems in place (tried Reiserfs and ext3 for the array; ext2 for /boot seems to be fine as the boot does initialize)
    - mounting of array to /mnt
    - Edit configfiles. Mkinitcpio is the important one, I feel:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES="pata_jmicron ata_generic ahci ata_piix sata_sil24 raid0"
    # BINARIES
    # This setting includes, into the CPIO image, and additional
    # binaries a given user may wish. This is run first, so may
    # be used to override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten is already added)
    # BINARIES are dependancy parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in anyway. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options,
    # like so:
    # FILES="/etc/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'modload' may be used in place of 'udev', but is not recommended
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    # This setup specifies all modules in the MODULES setting above.
    # No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    # This setup will autodetect all modules for your system and should
    # work as a sane default
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    # This setup will generate a 'full' image which supports most systems.
    # No autodetection is done.
    # HOOKS="base udev ide scsi sata usb filesystems"
    # This setup assembles an ide raid array with an encrypted root FS.
    # Note: See 'mkinitcpio -H raid' for more information on raid devices.
    # HOOKS="base udev ide raid encrypt filesystems"
    # This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    HOOKS="base udev autodetect pata scsi sata raid usbinput keymap filesystems"
    md=0,/dev/sda7,/dev/sdb7
    I also tried adding reisferfs to 'modules' and using rootfstype=reiserfs as a kernel parameters.
    - Install kernel
    - Chrooting into the basesystem and run mdadm -D -scan >> /etc/mdadm.conf
    - Editing menu.lst of an existing installation (Ubuntu, in which incidentally raid0 runs fine)
    title Arch Linux
    root (hd0,5)
    kernel /vmlinuz26 root=/dev/md0 ro md=0,/dev/sda7,/dev/sdb7
    What am I doing wrong? I know there's something about creating nodes, but I cannot find any useful information on it. Also, perhaps I am simply missing a module?
    Last edited by crakie (2007-06-05 17:31:09)

    Still no dice I cannot find anything out of order.
    lshdw:
    00:00.0 Host bridge: Intel Corporation|Memory Controller Hub (unknown)
    00:01.0 PCI bridge: Intel Corporation|PCI Express Root Port (unknown)
    00:1a.0 USB Controller: Intel Corporation|USB UHCI Controller #4 (unknown)
    00:1a.1 USB Controller: Intel Corporation|USB UHCI Controller #5 (unknown)
    00:1a.7 USB Controller: Intel Corporation|USB2 EHCI Controller #2 (unknown)
    00:1b.0 Audio device: Intel Corp.|ICH8 HD Audio DID (snd-hda-intel)
    00:1c.0 PCI bridge: Intel Corporation|PCI Express Port 1 (unknown)
    00:1c.2 PCI bridge: Intel Corporation|PCI Express Port 3 (unknown)
    00:1c.3 PCI bridge: Intel Corporation|PCI Express Port 4 (unknown)
    00:1c.4 PCI bridge: Intel Corporation|PCI Express Port 5 (unknown)
    00:1c.5 PCI bridge: Intel Corporation|PCI Express Port 6 (unknown)
    00:1d.0 USB Controller: Intel Corporation|USB UHCI Controller #1 (unknown)
    00:1d.1 USB Controller: Intel Corporation|USB UHCI Controller #2 (unknown)
    00:1d.2 USB Controller: Intel Corporation|USB UHCI Controller #3 (unknown)
    00:1d.7 USB Controller: Intel Corporation|USB2 EHCI Controller #1 (unknown)
    00:1e.0 PCI bridge: Intel Corp.|82820 815e (Camino 2) Chipset PCI (hw_random)
    00:1f.0 ISA bridge: Intel Corporation|LPC Interface Controller (unknown)
    00:1f.2 IDE interface: Intel Corporation|SATA Controller 1 cc=IDE (ata_piix)
    00:1f.3 SMBus: Intel Corporation|SMBus Controller (i2c-i801)
    00:1f.5 IDE interface: Intel Corporation|SATA Controller 2 cc=IDE (ata_piix)
    01:00.0 VGA compatible controller: nVidia Corp.|GeForce 7600 GT (vesa)
    03:00.0 Ethernet controller: Realtek Semiconductor|RTL-8168 PCI-E Gigabit Ethernet (r8169)
    04:00.0 Mass storage controller: Silicon Image Inc.|SiI 3132 PCI-X Serial ATA Controller (sata_sil24)
    05:00.0 Ethernet controller: Realtek Semiconductor|RTL-8168 PCI-E Gigabit Ethernet (r8169)
    06:00.0 SATA controller: JMicron Technologies, Inc.|JMicron 20360/20363 AHCI Controller (ahci)
    06:00.1 IDE interface: JMicron Technologies, Inc.|JMicron 20360/20363 AHCI Controller (ahci)
    07:02.0 FireWire (IEEE 1394): Texas Instruments|TSB43AB22 IEEE1394a-2000 OHCI PHY/Link-Layer Ctrlr (ohci1394)
    07:05.0 Multimedia video controller: Conexant Inc.|iTVC15 MPEG Coder (ivtv)
    005:001 USB Hub: Virtual|Hub (hub)
    005:002 USB Human Interface Devices: USB Gaming Mouse [/dev/input/mice] (usbhid)
    002:001 USB Hub: Virtual|Hub (hub)
    007:001 USB Hub: Virtual|Hub (hub)
    006:001 USB Hub: Virtual|Hub (hub)
    001:001 USB Hub: Virtual|Hub (hub)
    004:001 USB Hub: Virtual|Hub (hub)
    003:001 USB Hub: Virtual|Hub (hub)
    ---:--- Mouse: PS/2 Mouse port [/dev/psaux] (msintellips/2)

  • Installing arch on extended partition/logical drive

    hi there. i am a newbie to linux and about to install arch as my first linux installation.
    i am using vaio AR laptop already running xp and would like to keep it and have double boot without reinstalling xp.
    have 200gb hdd with recovery primary partition, system primary partition (where xp installed) and extended partition with one logical drive (D: ) of 100gb.
    i was considering deleting the logical drive (and the extended partition if necessary), which if i understand correctly should give me 100gb of unallocated space.
    i would then like to install arch on the 100gb of unallocated space.
    i would like to know if the way i am planning to go about it is possible, and whether i can install arch completely on one extended partition devided into logical drives.
    any comments or sugestions would be much appreciated...
    Last edited by o12357 (2009-09-04 12:45:18)

    I believe that is correct.  Grub has to have a reference to the md0 raid for booting.
    Please see
    http://bbs.archlinux.org/viewtopic.php?id=79306
    This solution to the boot problem with md0 should be helpful for your case since grub must be modified to accomodate the raid.
    I am not sure the data in your raid0 is appropo for your use in booting archlinux, however.  If I understand correctly, it is windows related data and not applicable to linux.
    If your raid0 is partitioned, it would be possible to establish a boot for each system using grub partition references differing for linux and windows systems.
    Thus, you would have grub entries complete for linux and another set complete for windows.
    I think AFAICT windows has to be first in the usual dual booting but am not an expert on that, not having used dual boot.  It may be somewhat different when using raid for booting dual systems.
    I suggest you read the wiki on dual boots.
    Perhaps you will get advice from others on the subject also.
    EDIT:  Your asumption that all OS'es will recognize the raid0 devices as a single drive does not apply to archlinux which does not autodetect raid arrays but must have initramfs populated with the raid data established by mdadm and initiated into initramfs by mkinitcpio.  Then during boot sequences , the array is assembled and enabled as a single drive,i.e., md0.  The boot sequence assembles all drives having identical UUID's in the raid array.
    Last edited by lilsirecho (2009-09-05 18:23:36)

  • Just installed arch, lots of cryptic errors

    1. logitech mx5000 bluetooth mouse. when i type 'hidd --connect' and the address, i get:
    Can't get device information: Connection timed out
    how can i connect it?
    2. midori errors. when i load midori, i get several 'gtk-warning' errors in the terminal window, e.g., 'error loading theme icon'. how do i fix these errors?
    also, i don't like the default keyboard shortcuts. is there any way i change these, maybe globally? e.g., i'd rather use ctrl + tab and ctrl + shift + tab to change tabs.
    3. wireless setup. i've installed the driver and wicd, but when i type 'wicd-client -n' to load it, i get a whole bunch of lines:
    Traceback (most recent call last):
    File "/usr/lib/wicd/wicd-client.py", line 50, in <module>
    import wicd.gui as gui
    dbus.exception.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.wicd.daemon was not provided by any .service files
    how can i set up my wireless simply and quickly with a gui?
    4. when i load pcmanfm, i get an error:
    GTK+ icon theme is not properly set
    what is an xsettings manager?
    i still have other questions, but i thought i should try to get these resolved first.
    5. also, is there a 'control panel' like in windows where i can edit all the system settings, e.g., touchpad, user accounts, etc.?
    Last edited by anti-destin (2009-05-23 21:26:59)

    1) i don't use bluetooth, so can't help you with that
    2 / 4) it seems you have no default icon theme installed yet, for instance
    pacman -S hicolor-icon-theme
    then you need to set it as default theme, see point 5
    3) wicd is a client-server model which needs a running daemon:
    sudo /etc/rc.d/wicd start
    be aware that you also need to have hal and dbus installed + running to use wicd
    5) that depends on which desktop environment you are using:
    considering you seem to be just starting out with linux/arch, it would recommend installing either gnome or xfce4, which will make these tasks a lot easier for your. gnome is the most newbie-friendly, xfce4 is a bit more minimal and will require more work from your side. if you do decide to go for a more 'hardcore' setup right away (i.e. windowmanager-only), be prepared to get your hands dirty and spend a lot of time trying and figuring things out. most of the questions you ask are quite basic, and would be easy to find out yourself by digging through the wiki and the forums.

  • Howto install broadcom wl with custom kernel

    Hi I am trying to install the broadcom-wl driver from a custom kernel made traditionnal way.
    The makefile they provide give me this :
    KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd`
    make[1]: Entering directory `/home/maxime/kernelbuild/linux-3.10.10'
    Wireless Extension is the only possible API for this kernel version
    Using Wireless Extension API
      CC [M]  /home/maxime/wldriver/src/wl/sys/wl_linux.o
    In file included from /home/maxime/wldriver/src/wl/sys/wl_linux.c:43:0:
    /home/maxime/kernelbuild/linux-3.10.10/arch/arm/include/asm/system.h:3:26: fatal error: asm/compiler.h: No such file or directory
    #include <asm/compiler.h>
                              ^
    compilation terminated.
    make[2]: *** [/home/maxime/wldriver/src/wl/sys/wl_linux.o] Error 1
    make[1]: *** [_module_/home/maxime/wldriver] Error 2
    make[1]: Leaving directory `/home/maxime/kernelbuild/linux-3.10.10'
    make: *** [all] Error 2
    I have change the path in wl_linux.o to include system.h with the full path(as you can see). And it can find it, but I have to change all the path for every <include> wich is very long and i am not sure it s the right way.
    I tried to install the driver with yaourt and it installs the .ko . in my extramodules folder in my /lib/modules/ directory. but modprobe wl report no such file.
    But if i come back to the precompiled kernel it works. I ve tried to change the kernel version to my current version in extramodules in /lib/modules/extramodules-3.10 that the PKGBUILD is looking at and try to install it again with yaourt on my custom kernel but still the same.
    I copied the .ko to my kernel 3.10.10 custom and tried modprob and I got a symlink error.
    As they said i need to modprob the  cfg80211, which i did but I still get the same error.
    Howto build package for my custom kernel and not the default kernel while I am on the custom kernel ??
    Last edited by maxarsys (2013-09-09 21:14:39)

    Sigi wrote:Have you deleted or commented out kernel26 in the file addedpacks?
    oh, thx, i didn't know, that kernel26 is in addedpacks. now, i am building it with  #kernel26
    Sigi wrote:May I ask why you made your own kernel? I'm just wondering... ;-)
    because i wanna change logo in FB, and/or  add splasscreen support.
    or is it possible, add it, to kernel26?
    Sigi wrote:edit: btw, Welcome to the forum!
    oh thx, hello here

  • Problems installing Arch 0.7 base on SATA HDD.

    Hi! I am new to Arch and still a bit of a newbie when it comes to Linux in general. I have a friend who runs Arch who has been trying to help me... to no avail. I am trying to install Arch base 0.7 with an ftp installation on my system. Some of my system is as follows:
    P4 3 GHz, 1024 memory. My HDD setup is:
    Primary IDE Master: [NOT DETECTED] (No drive here!)
    Primary IDE Slave: [Maxtor ide drive] Files
    Secondary Master: [Samsung dvd-rom] (ATAPI)
    Secondary Slave: [CDRW] (ATAPI)
    Third ide Master: [SATA-HDD] OS's Windows and Arch
    My Linux partitioning is as follows:
    sda5 /
    sda2 /boot
    sda7 /home
    sda6 swap
    My Grub file looks like this:
    Linux
    root (hd1,1)
    kernel /vmlinuz26 root=/dev/sda5 devfs=nomount ro
    windows
    rootnoverify (hd1,0)
    makeactive
    chainloader +1
    (I have left out the coad for the title line in this forum)
    My windows loads perfectly but I have troubles booting into Linux, when I add quiet to my Kernel line I get this at bootup:
    Booting command-list
    root (hd1,1)
    filesystem type is ext2fs, partition type 0x83
    kernel /vmlinuz26 root (etc....)
    [linuz-bzimage, setup=0x1c00, size=0x3d08535]
    uncompressing kernel... OK, booting the kernel.
    ACPI: Unable to load the System Description Tables
    and then my system stops loading, reset button to restart!
    My friend is a bit of a Linux whizz but he was unable to help me out... I have changed my fstab to look like sdaX... (he told me to)...
    Any suggestions?
    thx

    Similar problem here.
    Pre-partitionned my single HDD which is a Sata 80Gb, with sda6 5Gb for Arch, sda9 /home & sda11 swap.
    Installed Wombat which recognized the HDD on /dev/discs/disc0, adjusted the conf files as if i was going to use hotplug.
    Installed Grub on to the "/" (sda6) partition as I plan to add others distros.
    Also  installed Grub on a new ext2 formatted Floppy with :
    umount /floppy
    /usr/local/sbin/grub --batch <<EOT
    root (fd0)
    setup (fd0)
    quit
    EOT.
    When I boot with that floppy, grub recognize HDD as hd0 and "/" as 6th partition : I can TAB to "vmlinuz26 without a glinch
    Then it boot ... untill I get this message :
    "sata "kernel panic - not syncing: vfs: unable to mount root fs on unknown-block(0,0)""
    Should I edit /etc/rc/conf with some more modules/daemons that those by default ?
    Presently I'm copying my Arch mirror (current & extra) on to another partition to get last packages. Because my box comes with an ULi network controller that was added to the kernel modules early in October, so I want to chroot into my present install, update to latest kernel, udev, dbus & hal, & see what I can do thereafter.

Maybe you are looking for

  • 10.5.7 update with G4 iMac

    I just read about the new upgrade. I just bought an old G4 iMac today that has 10.5 installed on it for my 85 year old Mom - who has never used a computer. I thought I had read somewhere that the PowerPC chips can't/shouldn't run 10.5. Is this true?

  • Java load library - std::locale::init - SIGBUS

    Hi , I am trying to load a native library using java. This call crashes the jvm. During the static initialization of library error is happening. ---- called from signal handler with signal 10 (SIGBUS) ------ [10] __Crun::ex_rethrow_q(0x0, 0x38, 0x0,

  • Somebody has a few minutes for an alien coming from Windows / PC ?

    Hi, I only used Windows / PC so far and though to give a try to Apple. I got an used iMac and don't know anything about this world. I'd like firs to upgrade from OS X 10.3.9 to 10.4 What's the most convenient (cheap) way to do this. I see there are s

  • Statistical significance of causal factors in Demantra

    Hey everyone, I bet you missed me, well I have another question which is bugging my mind regarding demantra implementations. Say I add a causal factor to my business model, and of course I re-run the analytical engine in order to generate a new forec

  • Event splitting issues

    Trying to split an event into multiple events and iPhoto has booted me out.  Anyone seen this before and know how to resolve