You are not logged in.
yea i was kind of really busy for the past few days so i didn't have time to post. If i do find the solution i will make sure to post it here. Anyway here is my DAEMONS line from /etc/rc.conf
DAEMONS=(syslog-ng network netfs crond)
Offline
That's a normal line, and the fact ifconfig doesn't list eth0 suggests that your network card is not initialized properly.
can you post your entire /etc/rc.conf ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#
# /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"
# 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="localtime"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
#
MODULES=(8139cp 8139too mii slhc ac97_bus snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-ac97-codec snd-intel8x0 soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="arch"
#
# 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
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="dchp"
INTERFACES=(lo 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.0.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-profiles
#
#NET_PROFILES=(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)
# End of file
Offline
If you're using a realtek nic, I will tell you right now their nics can be finicky about drivers, at times. My realtek (a built-in on a laptop) pukes on the 8139cp driver but will work fine with the 8139too driver. So I'd suggest trying this:
first of all, black list the 8139too driver like so:
MODULES=(8139cp !8139too mii....)
Now restart the network services as root like so:
/etc/rc.d/network restart
If you do an "ifconfig -a" & can then ping your router like this:
ping -c 3 192.168.0.1
then you're in business. Keep the module blacklisted or remove it entirely. If this fails, unblacklist the 8139too driver, blacklist the 8139cp driver then repeat the experiment.
MS
Offline
ok tried back listing one, then the other, then both they all give the same error when i try to restart the network
::Stoping Network
dchp: unknow interface: No such device
:: Starting Network
dchp: error fetching interface information: Device not found
and obviously i get this message when i try to ping
connect: Network is unreachable
do i have the proper gateway and router ip setup? I don't think my router uses the default ip. Or does it not matter at this point because arch can't detect my card at all?
Offline
If your gateway is entirely wrong, then you're going to have issues trying to debug why the nic's not seen...these things tend to snowball & you find weirder glitches as you go. So yes find out the routers correct IP address. That will help narrow things down somewhat.
Next time you're in ubuntu you could try something like looking at the /etc/interfaces file & see what it put in there for settings for the router/ip address/dhcp stuff. Then just save it to a text file & copy it to your rc.conf file.
Offline
well this was my /etc/network/interaces in ubuntu
auto lo
iface lo inet loopback
and this was /etc/networks
# symbolic names for networks, see networks(5) for more information
link-local 169.254.0.0
^^^could that be my routers ip? (don't have time atm but will try tomorrow and let you know)
im using the live cd btw.
any other files i should look into?
Offline
ok that was not my routers IP anyother ideas?
Offline