You are not logged in.

#1 2007-07-29 08:23:53

Roberth
Member
From: The Pale Blue Dot
Registered: 2007-01-12
Posts: 894

Broken system

Hello, after changing my ath0 network interface to static ip addresses instead of dhcp configuration, my system would no longer boot up, the only thing I could notice while it booted up was that the output consisted of lot of phrases like this "Command not found", and then i entered the bash shell, which was corrupted and the keyboard and the mouse didn't work.
I backed up my wireless in /etc/conf.d/, rc.conf and resolv.conf, I reinstalled my system, and i restored these configurasion files I've backed up, and rebooted my system, and the system was broken again, here is my configurasion files:

/etc/Resolv.conf:

# Generated by dhcpcd for interface ath0

nameserver 192.168.1.1

/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"
# 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="nb_NO.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Oslo"
KEYMAP=no
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=(sk98lin skge) 
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="Magda"
#
# 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="dhcp"
ath0="ath0 192.168.1.101 netmask 255.255.255.0"
INTERFACES=(lo !eth0 ath0)
#
# 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-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 crond hal alsa mpd mpdscribble fam)


# End of file

/etc/conf.d/wireless:

wlan_ath0="ath0 essid internett key a62504c418"

What is wrong?


Use the Source, Luke!

Offline

#2 2007-07-29 12:17:06

veek
Member
Registered: 2006-03-10
Posts: 167

Re: Broken system

I think you need to move ath0 from the INTERFACES array to one called WLAN_INTERFACES.

Offline

#3 2007-07-29 16:50:00

Roberth
Member
From: The Pale Blue Dot
Registered: 2007-01-12
Posts: 894

Re: Broken system

Well I tried a few "shots in the dark" including your suggestion and the issue disappeard when i took the new rc.conf that the arch installer generated and added my custom configurasions to it.


Use the Source, Luke!

Offline

Board footer

Powered by FluxBB