You are not logged in.
Pages: 1
Booted up this morning and noticed some weird stuff. I get thrown into CLi halfway through boot up before any modules are loaded. No i dont use the testing repo and i dont play with my conf files regularly either.
Last edited by b0uncyfr0 (2008-06-04 10:57:24)
Offline
Was it after a system update that it did this, or what did you change?
Offline
Im not sure if i did an update but what else could mess it up sp badly??
Offline
Did you do an update recently. If so what did you update (see /var/log/pacman.log)?
Edit: Man I took a long time to hit submit... I blame the House season finale.
Offline
For the past 3 days
[2008-06-01 23:22] upgraded acetoneiso2 (2.0.2-1 -> 2.0.2-2)
[2008-06-01 23:22] installed libxml2 (2.6.32-1)
[2008-06-01 23:22] upgraded libxslt (1.1.23-1 -> 1.1.24-1)
[2008-06-02 00:23] synchronizing package lists
[2008-06-02 00:23] starting full system upgrade
[2008-06-02 08:57] synchronizing package lists
[2008-06-02 08:57] starting full system upgrade
[2008-06-04 19:58] synchronizing package lists
[2008-06-04 20:11] synchronizing package lists
[2008-06-04 20:11] synchronizing package lists
Last edited by b0uncyfr0 (2008-06-04 11:06:10)
Offline
Nothing of interest there... Do a filesystem check (touch /forcefsck).
Offline
Are you getting any errors etc. ?
Offline
I run touch/ forcefsck and nothing.
Yes i think i see an error but i get thrown in cli too quickly to read it. Is there a way to pause...
I picked up one thing ( Fatal:Module sky2 not found)
Last edited by b0uncyfr0 (2008-06-04 11:26:20)
Offline
Sorry, I wasn't clear. If you do a "touch /forcefsck" then on your next reboot it will check the filesystem.
Offline
Look in /var/log/messages.log for the error message.
Offline
There are no errors in messages.log
After a few reboots i was able to write a few things down. Something to do with kdm and /etc/rc.multi line 18. And line 18 is /etc/rc.d/$daemon start
Last edited by b0uncyfr0 (2008-06-04 12:33:28)
Offline
Something to do with kdm and /etc/rc.multi line 18. And line 18 is /etc/rc.d/$daemon start
OK. That line starts the daemons. So, if the problem is with kdm, remove it from the DAEMONS array in /etc/rc.conf and just boot to shell. If that goes well, I would try reinstalling kdm and see if that fixes it.
Offline
Just before i got into shell i saw a similar problem with syslog-ng which is 2nd in the daemon list ( i removed kdm from the list). This time it was something to do etc/rc.d and no such file or directory. I think something is stopping my daemons from being loaded.
Offline
Are the daemon start scripts in /etc/rc.d? Do their permissions look right?
Offline
b0uncyfr0, do you by any chance have more than one SATA hard drive?
Offline
Maybe you have a hard-to-spot typo in /etc/rc.conf
Post it here so we all can take a peak
Stand back, intruder, or i'll blast you out of space! I am Klixon and I don't want any dealings with you human lifeforms. I'm a cyborg!
Offline
(To Allan) Yes the startup scripts are in /etc/rc.d but im in Xp right now so i cant be sure of the permission.
Yep i got two Sata's
Heres 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"
# 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="localtime"
USEDIRECTISA="yes"
TIMEZONE="Australia/Sydney"
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=(sky2 slhc snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# 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="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
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="eth0 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.0.255"
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 crond hal sensors alsa ksensors samba)
Last edited by b0uncyfr0 (2008-06-04 13:46:41)
Offline
Yep i got two Sata's
Then it could be a known issue:
http://bbs.archlinux.org/viewtopic.php?id=47536
http://wiki.archlinux.org/index.php/Per … ice_naming
Offline
Im lost atm. I dont know what to do. Any suggestions?
Offline
Did you try the persistent device naming as suggested by Llama above?
Offline
Im already using uuid for booting and mounting my drives.
Offline
Im going to format today. This has gone on long enough.
Offline
do u need a loopback device in rc.conf? I don't remember if its that important.
Offline
I run touch/ forcefsck and nothing.
Yes i think i see an error but i get thrown in cli too quickly to read it. Is there a way to pause...
CTRL+S freezes the terminal output. CTRL+Q will resume it.
Last edited by Zepp (2008-06-07 01:21:39)
Offline
Pages: 1