[SOLVED] Virtualbox module "vboxdrv" - loading at boot

I can manualy boot the "vboxdrv" module using
sudo modprobe vboxdrv
and this works every time - I can use Virtual box withouth problems. I would really like to load this module at boot time using the "/boot/syslinux/syslinux.cfg" file and then recompile the image using mkinitcpio -p. I edited the file like this, but the module doesn't get loaded.
LABEL arch
MENU LABEL Linux (Arch)
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 rw init=/usr/lib/systemd/systemd vboxdrv
INITRD ../initramfs-linux.img
I have seen that people useing "modeprobe.****=*****" command or something similar in this file to load modules. How should I use this to load vboxdrv module?
Last edited by 71GA (2014-04-13 11:48:36)

halimbo wrote:
I don't see the problem in adding vboxdrv to the initramfs, when he clearly wants to have it loaded anytime he boots.
For the graphics drivers it's supposed in the wiki, too.
So I don't see a problem in adding the driver for virtualbox. but that's just me, i see.
When i follow your argumentation, there is no reason to add graphics drivers in /etc/mkinitcpio.conf because the drivers are not needed to mount the initial filesystem.
It's not only about mounting the real root it's about ensuring a succesfull bootup of the whole system and having graphics modules loaded early helps to do that. On my laptop for example there is a race condition with X11, which wants to start before udev figured out the appropriate graphics driver module to load. So it would boot into terminal and the display manager service would report "failed" as status otherwise.
Last edited by blackout23 (2014-04-13 18:45:14)

Similar Messages

Kernel modules not loading at boot.

~]$ systemctl status systemd-modules-load.service
systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: failed (Result: exit-code) since Tue 2014-03-11 18:34:06 CDT; 4min 53s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 137 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 137 (code=exited, status=1/FAILURE)
Mar 11 18:34:06 arch-m systemd-modules-load[137]: Failed to insert 'vboxguest...
Mar 11 18:34:06 arch-m systemd-modules-load[137]: Failed to insert 'vboxsf': ...
Mar 11 18:34:06 arch-m systemd-modules-load[137]: Inserted module 'vboxvideo'
Mar 11 18:34:06 arch-m systemd-modules-load[137]: Inserted module 'vboxdrv'
Mar 11 18:34:06 arch-m systemd-modules-load[137]: Inserted module 'vboxnetadp'
Mar 11 18:34:06 arch-m systemd-modules-load[137]: Failed to find module 'vbox...
Mar 11 18:34:06 arch-m systemd[1]: systemd-modules-load.service: main proce...RE
Mar 11 18:34:06 arch-m systemd[1]: Failed to start Load Kernel Modules.
Mar 11 18:34:06 arch-m systemd[1]: Unit systemd-modules-load.service entere...e.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Hint: Some lines were ellipsized, use -l to show in full.
Does any one know how to fix this? AFter a while it became annoying.

More importantly, the modules are built for a specific kernel version. So if the kernel gets updated and the virtualbox modules get overlooked somehow, then they are not going to work. You can always rebuild them with makepkg and ABS though.

[SOLVED]Virtualbox drivers not loaded at startup

I followed the wiki and added vboxdrv to my DAEMONS. The only change is that I start it in the background. However, when I start Virtualbox, and then the guest OS within, it gives me an error.
DAEMONS=(syslog-ng @net-profiles @dbus !sshd !netfs @crond @alsa @acpid @ntpd @vboxdrv)
I have to manually
modprobe vboxdrv
in order to start the guest OS. How can I have the vboxdrv started at boot?
also, is there a way to start the guest OS directly, without having to start the Virtualbox console?

Inittab:
# Runlevel 5 starts X environments
x1:5:once:/bin/su work -l -c "/usr/bin/startx -- :11 vt11 > /dev/null 2>&1"
x2:5:once:/bin/su windows -l -c "/usr/bin/startx -- :10 vt10 > /dev/null 2>&1"
x3:5:once:/bin/su windows -l -c "/usr/bin/VBoxManage startvm Ama --type vrdp > /dev/null 2>&1"
The first two start new X sessions, user "work" on vt11 and user "windows" on vt10. The third starts an RDP headless VirtualBox VM as user "windows". When the two X sessions start, they execute ~/.xinitrc (each of ~work/.xinitrc and ~windows/.xinitrc):
#!/bin/sh
# ~/.xinitrc
# Executed by startx
VirtualBox
This starts the VirtualBox GUI so I then switch to vt11 or vt10 and select a VM to run. Note each of ~windows/.VirtualBox and ~work/.VirtualBox are completely separate VB configs owned by the separate accounts.
Note that I don't bother with a window manager because I run the VMs full screen anyway, but you can start one if you want within .xinitrc.
You can change "VirtualBox" in .xinitrc to start a specific VM using VBoxManage startvm "MyVMName"
Hope this helps.
Last edited by starfry (2011-03-29 21:49:33)

[SOLVED] virtualbox-modules: dkms: command not found

$ makepkg -s
==> Making package: virtualbox-modules 4.2.6-4 (Tue Jan 29 15:42:01 EET 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
==> Extracting Sources...
==> Removing existing pkg/ directory...
==> Starting build()...
-> Host modules
/home/yuri/builds/virtualbox-modules/PKGBUILD: line 26: dkms: command not found
==> ERROR: A failure occurred in build().
Aborting...
$ which dkms
which: no dkms in (~/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/vendor_perl:/usr/bin/core_perl)
$ su - -c 'which dkms'
/usr/sbin/dkms
Since makepkg uses fakeroot (and should never be run as root), ...
https://wiki.archlinux.org/index.php/AUR
What is the proper way to make it work? Thank you.
Last edited by x-yuri (2013-01-29 19:33:44)

It's not my PKGBUILD. It's PKGBUILD, downloaded by abs (community/virtualbox-modules):
# $Id: PKGBUILD 82593 2013-01-21 11:10:44Z tpowa $
# Maintainer: Ionut Biru <[email protected]>
# Maintainer: Sébastien Luttringer <[email protected]>
pkgbase=virtualbox-modules
pkgname=('virtualbox-host-modules' 'virtualbox-guest-modules')
pkgver=4.2.6
pkgrel=4
arch=('i686' 'x86_64')
url='http://virtualbox.org'
license=('GPL')
makedepends=('linux-headers'
"virtualbox-host-dkms>=$pkgver"
"virtualbox-guest-dkms>=$pkgver"
'expac'
'bc')
build() {
_kernver=$(expac -Q '%v' linux-headers)-ARCH
# dkms need modification to be run as user
cp -r /var/lib/dkms .
echo "dkms_tree='$srcdir/dkms'" > dkms.conf
# build host modules
msg2 'Host modules'
dkms --dkmsframework dkms.conf build "vboxhost/$pkgver" -k "$_kernver"
# build guest modules
msg2 'Guest modules'
dkms --dkmsframework dkms.conf build "vboxguest/$pkgver" -k "$_kernver"
package_virtualbox-host-modules(){
_kernver=$(expac -Q '%v' linux-headers)-ARCH
_extraver=extramodules-${_kernver%.*}-ARCH
pkgdesc='Host kernel modules for VirtualBox'
depends=("linux>=${_kernver%.*}" "linux<$(echo "${_kernver%.*}+0.1"|bc)")
replaces=('virtualbox-modules')
conflicts=('virtualbox-modules')
install=virtualbox-host-modules.install
install -dm755 "$pkgdir/usr/lib/modules/$_extraver"
cd "dkms/vboxhost/$pkgver/$_kernver/$CARCH/module"
install -m644 * "$pkgdir/usr/lib/modules/$_extraver"
find "$pkgdir" -name '*.ko' -exec gzip -9 {} +
sed -ie "s/EXTRAMODULES='.*'/EXTRAMODULES='$_extraver'/" "$startdir/virtualbox-host-modules.install"
package_virtualbox-guest-modules(){
_kernver=$(expac -Q '%v' linux-headers)-ARCH
_extraver=extramodules-${_kernver%.*}-ARCH
pkgdesc='Guest kernel modules for VirtualBox'
license=('GPL')
depends=("linux>=${_kernver%.*}" "linux<$(echo "${_kernver%.*}+0.1"|bc)")
replaces=('virtualbox-archlinux-modules')
conflicts=('virtualbox-archlinux-modules')
install=virtualbox-guest-modules.install
install -dm755 "$pkgdir/usr/lib/modules/$_extraver"
cd "dkms/vboxguest/$pkgver/$_kernver/$CARCH/module"
install -m644 * "$pkgdir/usr/lib/modules/$_extraver"
find "$pkgdir" -name '*.ko' -exec gzip -9 {} +
sed -ie "s/EXTRAMODULES='.*'/EXTRAMODULES='$_extraver'/" "$startdir/virtualbox-guest-modules.install"
# vim:set ts=2 sw=2 et:
Could it possibly be that this time makepkg must be run as root?

[Solved] tun module was loaded but not in lsmod?

Hi Everybody,
I loaded the tun module with "sudo modprobe tun" without any error message but didn't see it anywhere in "sudo lsmod". What might be the problems? I'm using linux-ck and wondering if linux-ck does anything here.
The reason I want to load the tun module is that I saw this error:
[root@ArchCustom openvpn]# openvpn --config ibVPN-LU-Luxembourg-$P2P$.ovpn
Thu Jan 17 08:03:20 2013 OpenVPN 2.2.2 x86_64-unknown-linux-gnu [SSL] [LZO2] [EPOLL] [eurephia] built on Aug 18 2012
Enter Auth Username:[email protected]
Enter Auth Password:
Thu Jan 17 08:03:30 2013 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Thu Jan 17 08:03:30 2013 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Thu Jan 17 08:03:30 2013 NOTE: --script-security method='system' is deprecated due to the fact that passed parameters will be subject to shell expansion
Thu Jan 17 08:03:30 2013 LZO compression initialized
Thu Jan 17 08:03:30 2013 Control Channel MTU parms [ L:1578 D:138 EF:38 EB:0 ET:0 EL:0 ]
Thu Jan 17 08:03:30 2013 Socket Buffers: R=[212992->131072] S=[212992->131072]
Thu Jan 17 08:03:30 2013 Data Channel MTU parms [ L:1578 D:1450 EF:46 EB:135 ET:32 EL:0 AF:3/1 ]
Thu Jan 17 08:03:30 2013 Fragmentation MTU parms [ L:1578 D:1300 EF:45 EB:135 ET:33 EL:0 AF:3/1 ]
Thu Jan 17 08:03:30 2013 Local Options hash (VER=V4): '9a22532e'
Thu Jan 17 08:03:30 2013 Expected Remote Options hash (VER=V4): 'e2a912d8'
Thu Jan 17 08:03:30 2013 UDPv4 link local (bound): [undef]:1194
Thu Jan 17 08:03:30 2013 UDPv4 link remote: 212.117.165.18:1194
Thu Jan 17 08:03:30 2013 TLS: Initial packet from 212.117.165.18:1194, sid=bfe5f406 752fd5e9
Thu Jan 17 08:03:31 2013 VERIFY OK: depth=1, /C=US/ST=CA/L=SanFrancisco/O=Fort-Funston/CN=Fort-Funston_CA/[email protected]
Thu Jan 17 08:03:31 2013 VERIFY OK: nsCertType=SERVER
Thu Jan 17 08:03:31 2013 VERIFY OK: depth=0, /C=US/ST=CA/L=SanFrancisco/O=Fort-Funston/CN=server/[email protected]
Thu Jan 17 08:03:31 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Jan 17 08:03:31 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Jan 17 08:03:31 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Jan 17 08:03:31 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Jan 17 08:03:31 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Thu Jan 17 08:03:31 2013 [server] Peer Connection Initiated with 212.117.165.18:1194
Thu Jan 17 08:03:33 2013 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Thu Jan 17 08:03:33 2013 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route 10.10.10.0 255.255.255.0 vpn_gateway,show-net-up,route-gateway 10.10.10.1,ping 2,ping-restart 120,ifconfig 10.10.10.18 255.255.255.0'
Thu Jan 17 08:03:33 2013 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:5: show-net-up (2.2.2)
Thu Jan 17 08:03:33 2013 OPTIONS IMPORT: timers and/or timeouts modified
Thu Jan 17 08:03:33 2013 OPTIONS IMPORT: --ifconfig/up options modified
Thu Jan 17 08:03:33 2013 OPTIONS IMPORT: route options modified
Thu Jan 17 08:03:33 2013 OPTIONS IMPORT: route-related options modified
Thu Jan 17 08:03:33 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Jan 17 08:03:33 2013 ROUTE default_gateway=192.168.4.1
Thu Jan 17 08:03:33 2013 Note: Cannot open TUN/TAP dev /dev/net/tun: No such device (errno=19)
Thu Jan 17 08:03:33 2013 /usr/sbin/ip link set dev up mtu 1500
Usage: ip link add [link DEV] [ name ] NAME
[ txqueuelen PACKETS ]
[ address LLADDR ]
[ broadcast LLADDR ]
[ mtu MTU ]
[ numtxqueues QUEUE_COUNT ]
[ numrxqueues QUEUE_COUNT ]
type TYPE [ ARGS ]
ip link delete DEV type TYPE [ ARGS ]
ip link set { dev DEVICE | group DEVGROUP } [ { up | down } ]
[ arp { on | off } ]
[ dynamic { on | off } ]
[ multicast { on | off } ]
[ allmulticast { on | off } ]
[ promisc { on | off } ]
[ trailers { on | off } ]
[ txqueuelen PACKETS ]
[ name NEWNAME ]
[ address LLADDR ]
[ broadcast LLADDR ]
[ mtu MTU ]
[ netns PID ]
[ netns NAME ]
[ alias NAME ]
[ vf NUM [ mac LLADDR ]
[ vlan VLANID [ qos VLAN-QOS ] ]
[ rate TXRATE ] ]
[ spoofchk { on | off} ] ]
[ master DEVICE ]
[ nomaster ]
ip link show [ DEVICE | group GROUP ]
TYPE := { vlan | veth | vcan | dummy | ifb | macvlan | can | bridge }
Thu Jan 17 08:03:33 2013 Linux ip link set failed: external program exited with error status: 255
Thu Jan 17 08:03:33 2013 Exiting
And this is the content of ibVPN-LU-Luxembourg-$P2P$.ovpn:
[root@ArchCustom openvpn]# cat ibVPN-LU-Luxembourg-$P2P$.ovpn
remote lu1.ibvpn.com 1194 udp
remote 212.117.165.18 1194 udp
client
dev tap
resolv-retry infinite
script-security 3 system
explicit-exit-notify 3
persist-key
persist-tun
mute-replay-warnings
ca ibvpn.com.crt
comp-lzo
verb 3
mute 20
ns-cert-type server
fragment 1300
route-delay 2
auth-user-pass
auth-nocache
reneg-sec 0
up "/etc/openvpn/change_resolv_conf.sh up"
down "/etc/openvpn/change_resolv_conf.sh down"
Regards.
Solved: didn't know what happened, installed linux-ck 3.7.3-1-ck, rebooted and everything was fine.
Last edited by dxxvi (2013-01-20 06:10:47)

Trilby wrote:
Isn't this the same issue:
https://bbs.archlinux.org/viewtopic.php … 1#p1217611
If so, please search the forums before creating new threads of duplicate issues.
It looks like the same issue. Actually, I did a search for "tun" in the Networking forum (but not the newbie forum) and still couldn't find an answer.
My /usr/src/linux-3.7.2-2-ck/.config has CONFIG_TUN=m. Then is there any other reason I cannot load the tun module?
Thanks.

[SOLVED] Nouveau Module not starting at boot. Starts with modprobe.

I am currently using 64 bit arch linux along with grub2 for the boot loader. When I boot into arch the nouveau does not look to start. If I run dmesg it has no mention of it. Once I am in the system I can run modprobe nouveau and it starts up fine.
my mkinitcpio.conf has the following for the modules configuration: MODULES="nouveau"
I have rebuilt the image with "mkinitcpio -p linux" and remade the grub configuration with "grub-mkconfig -o /dev/sda" . I also made sure nouveau was not in the modprobe blacklist because I did have the nvidia drivers installed before hand.
Any ideas on why nouveau doesn't start after Grub?
Last edited by PupNSuds (2013-10-18 01:49:41)

Thank you for pointing that out. I did follow that but I forgot I had also tried an older NVIDIA driver 304 to be exact. So instead of running the exact command they had I ran "pacman -Qs nvidia" which displayed the following.
local/libvdpau 0.7-1
Nvidia VDPAU library
local/nvidia-304xx 304.108-8
NVIDIA drivers for linux, 304xx legacy branch
local/xf86-video-nouveau 1.0.9-1 (xorg-drivers xorg)
Open Source 2D acceleration driver for nVidia cards
So knowing the package name I removed it with the same command but with the proper NVIDIA version. "pacman -Rdds nvidia-304xx" . Every thing seems to be working now. Thank you again.

[SOLVED] slim fails to load on boot

Hi,
On boot the system will attempt to load slim, but fails, with no onscreen reason as to why. If I attempt to launch slim from the console, the same thing happens. Here's what systemctl thinks:-
$ systemctl status slim
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: failed (Result: exit-code) since Fri 2014-01-31 20:24:01 GMT; 2h 15min ago
Process: 325 ExecStart=/usr/bin/slim -nodaemon (code=exited, status=1/FAILURE)
Main PID: 325 (code=exited, status=1/FAILURE)
CGroup: /system.slice/slim.service
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension XVideo
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension XVideo-MotionCompensation
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension XFree86-VidModeExtension
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension XFree86-DGA
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension XFree86-DRI
Jan 31 20:23:58 laptop slim[325]: Initializing built-in extension DRI2
Jan 31 20:23:58 laptop slim[325]: Loading extension GLX
Jan 31 20:23:58 laptop slim[325]: (II) [KMS] Kernel modesetting enabled.
Jan 31 20:24:01 laptop systemd[1]: slim.service: main process exited, code=exited, status=1/FAILURE
Jan 31 20:24:01 laptop systemd[1]: Unit slim.service entered failed state.
There's this from journalctl too:-
Jan 31 20:24:01 laptop systemd[1]: slim.service: main process exited, code=exited, status=1/FAILURE
Jan 31 20:24:01 laptop slim[325]: (EE) Server terminated successfully (0). Closing log file.
Jan 31 20:24:01 laptop systemd[1]: Unit slim.service entered failed state.
I should add. If I login to a bash prompt, and launch X with startx, it boots to the desktop.
Last edited by n1md4 (2014-01-31 23:25:39)

pacman -R slim
pacman -S slim

[solved] aesni_intel module not loaded since switch to kmod

Since installing kmod-4-1 as replacement for module-init-tools the AES-NI instruction optimized crypto modules (aesni_intel) don't get loaded automatically anymore.
CPU is a SandyBridge Core-i5 2500K; aes-x86_64 isn't loaded anymore either. The CPU definitely supports AES-NI.
Is this a problem or am I supposed to write those modules down by hand in rc.conf MODULES section?
Kind regards
lynix
Last edited by lynix (2012-02-01 20:57:25)

Nevermind. I found the bug -- I'll make sure this is fixed for kmod5.
tech note for those interested:
A module alias can resolve to many modules -- in this case, the alias 'aes' resolves to "aes_generic", "padlock_aes", "aesni_intel", and "aes_x86_64". modprobe, including the library equivalent, should insist on trying to insert all of these. kmod does, but it makes the mistake of quitting if one of them errors out. To wit:
with module-init-tools:
# modprobe -v aes
insmod /lib/modules/3.2.2-1-ARCH/kernel/crypto/aes_generic.ko.gz
insmod /lib/modules/3.2.2-1-ARCH/kernel/drivers/crypto/padlock-aes.ko.gz
WARNING: Error inserting padlock_aes (/lib/modules/3.2.2-1-ARCH/kernel/drivers/crypto/padlock-aes.ko.gz): No such device
insmod /lib/modules/3.2.2-1-ARCH/kernel/crypto/cryptd.ko.gz
insmod /lib/modules/3.2.2-1-ARCH/kernel/arch/x86/crypto/aes-x86_64.ko.gz
insmod /lib/modules/3.2.2-1-ARCH/kernel/arch/x86/crypto/aesni-intel.ko.gz
WARNING: Error inserting aesni_intel (/lib/modules/3.2.2-1-ARCH/kernel/arch/x86/crypto/aesni-intel.ko.gz): No such device
with kmod:
# modprobe -v aes
insmod /lib/modules/3.2.2-1-ARCH/kernel/crypto/aes_generic.ko.gz
insmod /lib/modules/3.2.2-1-ARCH/kernel/drivers/crypto/padlock-aes.ko.gz
ERROR: could not insert 'padlock_aes': No such device
Last edited by falconindy (2012-02-01 20:54:47)

[solved] AMD Ucode not loading on boot

Its being called twice during the early hooks stage of udev.
i have already googled and found I needed to have installed the AMD Ucode package. I have version 2012.1.17-3 but it is being ignored.
Im getting the error
[unix time stamp i assume] microcode: failed to load file amd-ucode/microcode_amd.bin
twice after a long pause.
How do I fix it?
Last edited by Rhiadratech (2012-09-10 14:10:51)

I have put microcode in there as per instructions, but the word microcode was not in mkinitcpio.conf when I installed the system and started seeing the message. I think I added it on instructions in one of the 2 threads or an arch wiki page on the subject. I'll remove it.
The thing is I HAVE the amd-ucode package installed, and i'm STILL getting the message and associated delay on boot. So I'm looking for how I inform it I have installed it?
Last edited by Rhiadratech (2012-09-08 19:35:07)

[SOLVED] virtualbox modules dependency not met

when upgrading to kernel 2.6.29, is this fixable? or should i wait for the vbox modules to catch up?
Last edited by eldragon (2009-03-25 15:20:27)

If you decide to build VBox modules yourself for 2.6.29, you might want to note this thread:
http://bbs.archlinux.org/viewtopic.php?id=68348

Daemons and modules loaded at boot problem

Hi all, i have a problem with my booting time and modules / daemons loaded at boot
This is my bootchart:
[IMG=http://img195.imageshack.us/img195/4701/bootchartpw.th.png][/IMG]
This 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"
# 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="it_IT.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Rome"
KEYMAP="it"
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=(lib80211_crypt_tkip wl !snd-pcsp !pcspkr)
# 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="neplero"
# 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)
# 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.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 netfs crond hal !dbus !bluetooth @alsa)
How can i modify my modules loaded and daemons to lower some boot time.
And why is that bluetooth is still loaded even if it's !bluetooth? And is it possible to background ntfs-3g?
Thanks all for advices!

Please clarify what you mean. If the bluetooth service is started, then there is a bug or something very very odd. IF on the contrary you mean that the bluetooth-related modules are loaded by udev, this is perfectly normal: udev autoloads modules according to your hardware, not to your services. You need to blacklist the loaded bluetooth-related kernel modules (check them with 'lsmod') and to blacklist them in the MODULES array.
Last edited by patroclo7 (2010-01-30 19:14:51)

[Arch 64 bit] Powernow-k8 not loading at boot, loads fine afterwards

I get the same error.
Has anyone solved it?
Last edited by deadshox (2010-09-22 20:02:36)

Thanks for seperating this topic.
Now 'powernow-k8' is starting fine. I don't no why, but it starts.
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", 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="de_DE.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Berlin"
KEYMAP="de-latin1-nodeadkeys"
CONSOLEFONT="default8x16"
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=(vboxdrv !atl1c !pcspkr !snd-mixer-oss !snd-pcm-oss !snd-hwdep !snd-page-alloc !snd-pcm !snd-timer !snd !snd-hda-codec !snd-hda-intel !soundcore atl1c pcspkr snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-codec snd-hda-intel soundcore lib80211_crypt_tkip wl acpi-cpufreq powernow-k8 cpufreq_ondemand cpufreq_powersave)
# 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="keil"
# 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)
# 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 hal wicd @netfs @alsa laptop-mode)
// Edit
On my Notebook,
HP Compaq 615, 2.6.35-ARCH x86_64 AMD Athlon(tm)X2 DualCore QL-66 AuthenticAMD
i have the same problems with 'acpi-cpufreq' and there is all up to date, too.
Last edited by deadshox (2010-09-23 19:58:57)

Cpufreq_ondemand doesn't load at boot

Hi,
I followed the wiki article for cpu scaling which all worked, but when I rebooted ondemand was not set, however "cpufreq_set -g ondemand" did then work. The article says to add cpufreq_ondemand to the MODULES array in rc.conf which I have done.
The article also says to add acpi_cpufreq to the MODULES array but this resulted in "FATAL: Error inserting acpi_cpufreq (/lib/.../acpi-cpufreq.ko): Device or resource busy" at boot so I took it out. I have though added cpufreq to the DAEMONS array as suggested in another post.
Thanks, Jamie Kitson

I have the same issue, as this one is not solved, I'll continue here…here is my rc.conf followed by cpufreq.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", 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="cs_CZ.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Prague"
KEYMAP="cz-qwertz"
CONSOLEFONT="cp1250"
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 cpufreq_ondemand)
# 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="myhost"
# 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"
wlan0="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 alsa dbus !network !netfs !crond wicd laptop-mode)
# Configuration file for Laptop Mode Tools module cpufreq.
# For more information, consult the laptop-mode.conf(8) manual page.
# CPU frequency scaling and throttling
# Laptop mode tools can automatically adjust your kernel CPU frequency
# settings. This includes upper and lower limits and scaling governors.
# There is also support for CPU throttling, on systems that don't support
# frequency scaling.
# This feature only works on 2.6 kernels.
# IMPORTANT: In versions 1.36 and earlier, these settings were included in the
# main laptop-mode.conf configuration file. If they are still present, they
# overrule the settings in this file. To fix this, simply delete the settings
# from the main config file.
# Enable debug mode for this module
# Set to 1 if you want to debug this module
DEBUG=0
# Should laptop mode tools control the CPU frequency settings?
# Set to 0 to disable
CONTROL_CPU_FREQUENCY="auto"
# Legal values are "slowest" for the slowest speed that your
# CPU is able to operate at, "fastest" for the fastest speed,
# "medium" for some value in the middle, or any value listed in
# /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies.
# The "governor" can be any governor installed on your system, this usually
# includes "ondemand", "conservative", and "performance". The
# "IGNORE_NICE_LOAD" setting specifies that background programs that have
# a low priority ("nice level") should not cause the CPU frequency to
# be increased. (You generally want this to be enabled in battery mode.)
BATT_CPU_MAXFREQ=fastest
BATT_CPU_MINFREQ=slowest
BATT_CPU_GOVERNOR=ondemand
BATT_CPU_IGNORE_NICE_LOAD=1
LM_AC_CPU_MAXFREQ=fastest
LM_AC_CPU_MINFREQ=slowest
LM_AC_CPU_GOVERNOR=ondemand
LM_AC_CPU_IGNORE_NICE_LOAD=1
NOLM_AC_CPU_MAXFREQ=fastest
NOLM_AC_CPU_MINFREQ=slowest
NOLM_AC_CPU_GOVERNOR=ondemand
NOLM_AC_CPU_IGNORE_NICE_LOAD=0
# Should laptop mode tools control the CPU throttling? This is only useful
# on processors that don't have frequency scaling.
# (Only works when you have /proc/acpi/processor/CPU*/throttling.)
# This is only useful on older P4 processors that do not support frequency
# scaling. On such processors, this is the only way to reduce power consumption
# but at the cost of higher performance penalty.
# Enable this only if you have a processor that does not support frequency scaling
# On most new processors, you might want to disable it.
# Set to 0 to disable.
CONTROL_CPU_THROTTLING=0
# Legal values are "maximum" for the maximum (slowest) throttling level,
# "minimum" for minimum (fastest) throttling level, "medium" for a value
# somewhere in the middle (this is usually 50% for P4s), or any value listed
# in /proc/acpi/processor/CPU*/throttling. Be careful when using "maximum":
# this may be _very_ slow (in fact, with P4s it slows down the processor
# by a factor 8).
BATT_CPU_THROTTLING=medium
LM_AC_CPU_THROTTLING=medium
NOLM_AC_CPU_THROTTLING=minimum

[SOLVED]Get [FAIL] when loading user specified modules.

That is it, when the system is booting i get a [FAIL] message when loading user specified modules after upgrading udev, and the kmod new module handling or something as say in the news. I dont have a modprobe.conf or a modprobe.conf.pacsave file either and creating a modprobe.conf file doesn't solve the problem. The strange thing is that the modules are loaded anyways. I mean the ones that are specified in rc.conf. I dont know if the system [FAIL] to load that modules or others...The system works fine for now too.
Thanks.
PD: sorry if you notice my poor english.
Last edited by Hyugga (2012-01-22 23:09:02)

I had the same problem and removing the governor performance from rc.conf solved the problem. I tried however to remove both governors and only leave powernow-k8 (this is the only one that works for me) leaving rc.conf like this:
MODULES=(brcmsmac powernow-k8)
When I boot the laptop and check which governors are available and being used I get the following:
[netlak@soulrebel ~]$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 8.0 us.
hardware limits: 800 MHz - 2.10 GHz
available frequency steps: 2.10 GHz, 1.50 GHz, 800 MHz
available cpufreq governors: performance
current policy: frequency should be within 800 MHz and 2.10 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 2.10 GHz.
This like as if the ondemand governor would not be available but when unplugging the laptop and check again I get this:
[netlak@soulrebel ~]$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 8.0 us.
hardware limits: 800 MHz - 2.10 GHz
available frequency steps: 2.10 GHz, 1.50 GHz, 800 MHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 800 MHz and 2.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
This shows that the ondemand module can be autoloaded when needed, so I leave rc.conf only with powernow-k8.
Thanks for your help.

[SOLVED] Windows 8.1, lost Arch boot loader, cannot reinstall or boot

Hi all,
Apologies but I am only posting as I have exhausted my (admittedly quite limited) knowledge and have spent hours trying to get it back up and running but nothing seems to work at all. This will probably be quite long, apologies if there is something really obvious that I have missed on the Wiki or anywhere, but I'm only posting as I can't seem to get anywhere with it at all despite reading and trying.
Essentially I had a Toshiba Satellite p850-321 laptop (UEFI, secure boot off, fast boot off) which I had dual booting with Windows 8 and Arch using rEFInd. I then had several moments of madness, starting when for some reason - on very little sleep so didn't think - decided to upgrade Windows 8 to 8.1. Unsurprisingly (but a surprise for me at the time), it then booted straight into Windows 8.1, no rEFInd. In hindsight, it had probably just set itself as boot priority but I thought it had overwritten rEFInd with its own bootloader or set it back to default or something so started on a way to try and get it back.
I then spent many hours trying to get my old bootable Arch USB stick to work with no joy, updating it to the latest arch iso and all sorts. It eventually worked when I updated the laptop BIOS. Booted from the USB, chrooted into arch, reinstalled rEFInd, played around, eventually got it to reboot and display rEFInd but Arch wouldn't start. At this point I noticed that my fstab looked strange (devices/labels mixed up from what I expected), so followed the Beginner's Guide again and recreated the fstab. My disk is partitioned as follows (main partitions of note):
/dev/sda2 - Windows EFI partition
/dev/sda4 Windows 8.1
/dev/sda6 arch swap partition (archswap)
/dev/sda7 arch root partition (archroot)
/dev/sda8 arch home partition (archhome)
Couldn't get rEFInd to work so decided to start again with gummiboot. Installed gummiboot, followed Beginner's Guide to install and configure it. Edited arch.conf and after having to mess about with the location of vmlinuz-arch.efi in the conf file, I have the options part looking like this:
options root=/dev/sda7 rw
Now gummiboot loads on startup but all I get on trying to load Arch from gummiboot is the dreaded:
ERROR: device '' not found. Skipping fsck
ERROR: Unable to find root device ''.
I've tried changing the root in options in arch.conf to UUID, PARTUUID and even different partitions (just to see what happened...) - the same. Is it likely to be due to me recreating the fstab and something is messed up there?
Another problem is that now, whatever I do, I cannot boot from the USB again to get in to even try to fix anything. The laptop on boot just hangs for a while and then loads the gummiboot from the disk drive rather than from the USB (I've set the boot priority, everything) and nothing will allow me to boot from the USB. That is probably a secondary issue, I can probably try to reinstall the BIOS again and see if that helps.
If anyone has had anything similar and has any solutions I'd be really grateful - anything. I don't mind being shown to be incredibly stupid, I get that a lot so have a lot of experience! - just anything that can get me back into Arch again without having to reinstall from scratch!
Thanks.
Last edited by pilf (2013-11-02 19:45:44)

Thanks for replying, very much appreciated. The partitions were numbered sequentially, I only posted up the partitions that I thought were of interest to the issue (which wasn't very helpful!). The partitions are as follows:
Partition No Type
1 Win Recover
2 EFI System (EFI partition)
3 Microsoft Reserved
4 Microsoft Basic (Windows 8.1 installation)
5 Windows Recover
6 Linux Swap
7 Microsoft Basic (Arch root partition)
8 Microsoft Basic (Arch home partition)
9 Windows Recover
It looks like I have managed to solve it, but I admit I'm not sure what of the several changes I made that solved it. I managed to boot into the USB arch disk by resetting my BIOS back to defaults and then changing the boot order back, which was the only way it would boot the USB - without resetting back and putting the boot order back exactly how it was before it wouldn't boot from the USB. Anyway...
Checked the partitions with gdisk, no problems. I did sort the partitions as you mentioned, just in case. Changed the partition names using gdisk to the same names I had before (archroot, archhome, archswap). Changed the types from Microsoft Basic to Linux filesystem (partitions 7 and 8) and wrote the partition.
Mounted everything, chrooted, edited the gummiboot arch.conf file and noticed there were some strange characters in it, a forward slash before /root in the options for example. I had edited the arch.conf file from windows by booting into Windows, mounting the EFI partition (mountvol z: /s) and editing it that way, which would have messed up the formatting. It can't have only been that though as it wasn't booting anyway which is why I went into Windows to edit the file in the first place. Corrected the arch.conf file, rebooted and it booted. Some errors on boot which I need to correct but I can work on those as it boots into my arch installation.
So all solved. I thought I'd update just to say thanks for the advice and in case it helps anyone else in the future.

[SOLVED] Virtualbox module "vboxdrv" - loading at boot

Similar Messages

Maybe you are looking for