The problem is your hostname in rc.conf. Try changing the capital "G" to a common "g". Don't forget to change your host file also.
I had the same problem as you when installed Arch. My host name was "NicholasArch" and it wouldn't connect to the Internet. However, when I changed it to "Nicholasarch" it worked.
Tried. Doesn't work.
]]>I had the same problem as you when installed Arch. My host name was "NicholasArch" and it wouldn't connect to the Internet. However, when I changed it to "Nicholasarch" it worked.
]]>@tavianator - No I didn't test.
@chilebiker - Will try doing it.
@all -
First when I try with pacman -Syu to see whether the net is working or not, it gives me that /etc/rc.conf is locked & advises me to delete it. After I delete & re-try with pacman -Syu, it goes on with error to fetch packages, transistent error.
]]>As for dbus you don't need to put it in your daemons list, it will be automagically started by hal:
DAEMONS=(syslog-ng network netfs crond portmap fam hal !avahi-daemon)
Here is the output of kill dhcpcd & dhcpcd eth0
Did you test the internet connection after doing that? It looks like it should've worked. Your photo of the initial boot screen shows that it timed out trying to get an IP address, however.
]]>http://wiki.archlinux.org/index.php/HAL … figure_HAL
about hal and dbus.
I've never had an issue with dbus so I just use hal to call it instead of putting both in my DAEMONS array. Each setup is a little different though so look at that and experiment.
It seems there are some redundancies in the wiki. If you look under the HAL wiki page from above it recommends to add both dbus and hal while the Xorg Input Hotplugging wiki (and the old Begginer's Guide I believe) states this:
Besides installing a supported driver, both dbus and hal have to be running. Add the hal daemon to the DAEMONS array in /etc/rc.conf before anything related to X.Org is started. The hal daemon will load the dbus daemon automatically.
Quite confusing if you ask me.
Just a piece of advice I learned. It's best to pick one issue at a time, work through it until you fix that and then move on to the next problem. It save you from pulling your hair out.
]]>1) Boot from the LiveCD.
2) Follow my previous instructions and comment out that option. As root of course.
3) Type /etc/rc.d/network restart then wait for it to restart.
4) Try your connection again to see if it works
As I said I don't know if this is your problem but it's what I have to do every time I boot from the LiveCD and after I first install Arch.
Again, sorry about the omission. I wrote that at four in the mourning and I wasn't quite awake yet. Hopefully that works for you.
]]>BTW guys while Arch is booting I get the following messages. Inspect them & suggest appropriately.
Also here is the content of my /etc/rc.conf;
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Asia/Kolkata"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="CoolG5"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
NETWORKS=(main)
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond portmap fam dbus hal !avahi-daemon)
ROUTES=(!gateway)
I have my linux boxes with a set IP address right now, so can't confirm.
]]>When you have the LiveCD booted immediately type:
vi /etc/dhcpcd.conf
or
nano /etc/dhcpcd.conf
whichever you prefer and find this line:
# Respect the network MTU.
option interface_mtu
Comment out option interface_mtu
so it looks like this:
# Respect the network MTU.
# option interface_mtu
I hope that helps. I have to do it now every time I use the LiveCD. If this is what is causing you the headache then also make sure to set it after install as well.
Good Luck
I hope it helps!
Cool G5 wrote:I've already posted the content of /etc/resolv.conf. Check the screenshots above.
Really? I can't find it... all I see is /etc/rc.conf and the output of ping -c 3 google.com and ifconfig. But looking at ifconfig's output, I just noticed that eth0 doesn't have an IP address. What's the output of "killall dhcpcd; dhcpcd eth0"?
[img=http://imageshack.us/thumbnmail.png]