You are not logged in.

#1 2011-02-22 21:52:59

rickdg
Member
From: The Lowlands
Registered: 2011-01-01
Posts: 24

[SOLVED] New kernel fails to load modules from rc.conf

Hi guys, peculiar problem here. Since kernel26-2.6.37.6-x86-64 onwards my laptop fails to boot properly. It's unable to start the graphical environment and has lost the ability to mount the /boot partition. So far I've reinstalled the last working kernel (2.6.37-5) and started debugging. Got stuck, hence this topic.

I haven't been able to find the offending errors in the logfiles, but what I remember seeing is along these lines:

[Loading modules]
WARNING: Could not load module /lib/modules/2.6.37-ARCH/kernel/fs/fuse/fuse.ko.gz
WARNING: Could not load module /lib/modules/2.6.37-ARCH/kernel/divers/cpufreq/freq_table.ko.gz
WARNING: Could not load module /lib/modules/2.6.37-ARCH/kernel/divers/cpufreq/cpufreq_stats.ko.gz
WARNING: Could not load module /lib/modules/2.6.37-ARCH/kernel/divers/cpufreq/cpufreq_ondemand.ko.gz
WARNING: Could not load module /lib/modules/2.6.37-ARCH/kernel/divers/cpufreq/cpufreq_powersave.ko.gz
WARNING: Could not load module /lib/modules/2.6.37-ARCH/kernel/divers/cpufreq/cpufreq_performance.ko.gz
WARNING: Could not load module /lib/modules/2.6.37-ARCH/kernel/arch/x86/cpu/cpufreq/acpi-cpufreq.ko.gz

And further down in the booting process, preventing the /boot partition to be mounted

Could not load 'ext2'

From the errors given, my guess is that I have to start looking at the rc.conf, posted below

#
# /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", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# 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.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Amsterdam"
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=(acpi-cpufreq fuse cpufreq_ondemand cpufreq_powersave cpufreq_performance)

# 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="s080655"

# 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 !wlan0)

# 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)
 
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# 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 dbus !network netfs crond @alsa @hpfall @wicd @httpd @mysqld @noip slim )

I have no idea what is actually this problem, any suggestions anyone?

Last edited by rickdg (2011-02-23 10:13:35)

Offline

#2 2011-02-23 07:09:22

loafer
Member
From: the pub
Registered: 2009-04-14
Posts: 1,772

Re: [SOLVED] New kernel fails to load modules from rc.conf

It sounds similar to this thread.  Look at the comments regarding a failed depmod.

https://bbs.archlinux.org/viewtopic.php?id=113777


All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.

Offline

#3 2011-02-23 10:13:08

rickdg
Member
From: The Lowlands
Registered: 2011-01-01
Posts: 24

Re: [SOLVED] New kernel fails to load modules from rc.conf

Yes, a 'depmod -a' right after kernel upgrade seems to have fixed the issue or at least it allows me to boot the latest kernel smile thanks!

Offline

#4 2011-05-22 20:23:28

Archieman
Member
Registered: 2011-01-09
Posts: 25

Re: [SOLVED] New kernel fails to load modules from rc.conf

I have always had vboxdrv, vboxnetadp, vboxnetflt listed in the MODULES section of my rc.conf. Lately I noticed on boot that the "Loading Modules" section fails and I also had this same issue with running virtualbox. Where can I view log file detail for the boot process so I can see exactly what is failing and why?


A good solution applied with vigor now is better than a perfect solution applied ten minutes later. - George S. Patton

Offline

#5 2011-05-23 11:20:20

Lupo
Member
From: Berlin / Europe
Registered: 2011-04-09
Posts: 6

Re: [SOLVED] New kernel fails to load modules from rc.conf

@Archieman:
Virtualbox modules have to be rebuild after a kernel upgrade. This should fix the virtualbox issue for you.

Offline

Board footer

Powered by FluxBB