A Couple of Issues

meo · 2006-11-19 23:22:10

Hi,

I am having a couple of problems in my arch linux.
1) On startup, I have a freeze when the networking daemon starts. I use wireless, my rc.conf is below. It's really annoying, the freeze last for about 10-15seconds, then ends because the daemon fails. I do have internet, so something did work.

2) I am using arch on a laptop, and the power status is not working. It always thinks my AC is plugged in regardless of what it really is. When I load up my computer, it has an error message about ACPI not existing, could that have something to do with it, if so how do I fix it?

3) Finally, is there a guide for how to automatically mount a PSP system? I haven't been able to use the autofs, it hasn't worekd or I have done something wrong.

I am using Arch 0.7.2, the latest kernel (that was released just today / yesterday)

Here is my 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/unimaps
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US"
HARDWARECLOCK="localtime"
TIMEZONE="Asia/Hong_Kong"
KEYMAP="us"
CONSOLEFONT=t
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=(capability)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="meo"
#
# 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="eth0 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
eth1="dhcp"
wlan_eth1="eth1 essid OUROWNNW1 enc ab023028e56443c09091481203"
WLAN_INTERFACES=(eth1)
INTERFACES=(lo eth0 eth1)
#
# 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 netfs sysfs libsensors crond network alsa wifi-radar vmware samba cups gdm)

# End of file

Please let me know!

Jansson · 2006-11-19 23:52:44

The freeze at starup is farely easy to fix. I asume you are using your wireless, and thus don't have a cable pluged in. Thats why it can't start the eth0. So simply remove eth0 from interfaces when you're not using it.

meo · 2006-11-20 05:58:06

Is there any way to stop it from trying to connect at startup, but still have it there?

And also, any help with my other issues?

Thanks for that so far tho

Snarkout · 2006-11-20 14:01:18

2) I am using arch on a laptop, and the power status is not working. It always thinks my AC is plugged in regardless of what it really is. When I load up my computer, it has an error message about ACPI not existing, could that have something to do with it, if so how do I fix it?

What kind of laptop? Many laptops have their own brand-specific acpi module - thinkpads have ibm_acpi, for instance. Also, you could try installing acpid and see if that helps.

Sigi · 2006-11-20 14:21:15

meo wrote:

Is there any way to stop it from trying to connect at startup, but still have it there?
And also, any help with my other issues?
Thanks for that so far tho

You could try two things:
- put an @ in front of network in the daemons array of your rc.conf to load it in the background
- decrease the timeout of dhcpcd in its config file (to about 10s)

broch · 2006-11-20 20:34:07

there is no point of starting network with high priority:
start network and related stuff in the background

this may help

Sigi · 2006-11-20 20:42:08

broch wrote:

there is no point of starting network with high priority:
start network and related stuff in the background
this may help

Am I that difficult to understand?

broch · 2006-11-20 21:29:09

Am I that difficult to understand?

whoa!
some sort of copyrights for the idea?
I only have read first post. So I have made obvious suggestion. I think this (idea) is definitely GPLed or even BSDed.

meo · 2006-11-20 23:11:42

Thankyou both, you were both helpful.

I did put a @ in front, that worked perfectly thankyou.

I also managed to fix the laptop issue, I simply did not have the dbus daemon enabled.

Arch Linux

#1 2006-11-19 23:22:10

A Couple of Issues

#2 2006-11-19 23:52:44

Re: A Couple of Issues

#3 2006-11-20 05:58:06

Re: A Couple of Issues

#4 2006-11-20 14:01:18

Re: A Couple of Issues

#5 2006-11-20 14:21:15

Re: A Couple of Issues

#6 2006-11-20 20:34:07

Re: A Couple of Issues

#7 2006-11-20 20:42:08

Re: A Couple of Issues

#8 2006-11-20 21:29:09

Re: A Couple of Issues

#9 2006-11-20 23:11:42

Re: A Couple of Issues

Board footer