[Solved] Merging boot with root
Hi,
So the job is to merge my Arch's /boot partition with /root.
I have 4 primary partitions; arch /boot (sda1), ubuntu (sda2), arch / (sda3) and Vista (sda4), as you can see with fdisk:
[det@myhost Shortcuts]$ sudo fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf020b972
Device Boot Start End Blocks Id System
/dev/sda1 1 24 192748+ 83 Linux
/dev/sda2 5111 15386 82541970 83 Linux
/dev/sda3 15387 29332 112021245 83 Linux
/dev/sda4 * 29333 60801 252774742+ 7 HPFS/NTFS
Also here's what GParted has to say:
Thanks for everyone .
Last edited by algorythm (2009-07-24 11:52:08)
Yeah thanks, but you guys didn't probably remember that moving /boot also requires reconfiguring grub (/boot/grub/menu.lst).
So what I did:
Old menu.lst
title Arch Linux
rootnoverify (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/e289f40b-c778-4583-8bae-1f0bd769b311 ro
initrd /kernel26.img
title Arch Linux Fallback
rootnoverify (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/e289f40b-c778-4583-8bae-1f0bd769b311 ro
initrd /kernel26-fallback.img
New menu.lst
title Arch Linux
rootnoverify (hd0,2)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/e289f40b-c778-4583-8bae-1f0bd769b311 ro
initrd /boot/kernel26.img
title Arch Linux Fallback
rootnoverify (hd0,2)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/e289f40b-c778-4583-8bae-1f0bd769b311 ro
initrd /boot/kernel26-fallback.img
Last edited by algorythm (2009-07-24 12:06:28)
Similar Messages
-
[SOLVED] Dual boot with ubuntu w/o installing GRUB? (YES)
Hi all -
This is my first shot at arch, tho I've installed a few other linux distros.
So far I really appreciate the excellent documentation, especially compared to other linuxes!
But I can't find a good answer to this question:
I already have ubuntu installed and would like to dual-boot with arch. (I also have Win7 but boot it from a separate disk selected via BIOS, and usually leave this disk disconnected anyway, so it's not an issue; grub doesn't know it exists).
Q: Before installing, can I make a new LOGICAL ext4 partition (say /dev/sda7),
- then install arch on that **w/o installing grub** and **without messing with the MBR**,
- then edit ubuntu's existing menu.lst to add arch to the boot options?
Current $ fdisk -l
/dev/sda1 ext4 primary/boot (/ for ubuntu)
/dev/sda2 extended
--/dev/sda6 linux-swap
--/dev/sda5 NTFS (data - mp3s, etc)
unallocated 480GB --> Create new ext4 partition /dev/sda7, (logical or primary? Prefer logical)
Current menu.lst entry that I normally boot:
title Ubuntu 12.04 LTS, kernel 3.2.0-24-generic REGULAR
uuid UUIDforSDA1 (file has actual UUID number...)
kernel /boot/vmlinuz-3.2.0-24-generic root=UUID=UUIDforSDA1 ro
initrd /boot/initrd.img-3.2.0-24-generic
and add something like this to menu.lst:
title Arch Linux
uuid UUIDforSDA7
kernel /boot/vmlinuz-linux root=/dev/sda7/ARCH ro (??? - from example in arch docs)
initrd /boot/initramfs-linux.img
or
kernel /boot/vmlinuz-linux root=UUID=UUIDforSDA7 ro (??? - like the ubuntu entry)
I'd really like to NOT mess up booting ubuntu! (Another option might be install arch to a separate disk with the ubuntu disk disconnected, then copy the whole install over via a USB adapter...I've done worse!)
TIA for any help!
Edit: so I guess there's three questions:
1 - Can I install arch w/o installing grub & MBR messing-wth?
2 - What's the correct syntax for menu.lst to access and boot arch?
3 - Will this work?
Last edited by Flemur (2012-05-25 15:24:18)Well, it worked and booted up first time - no grub install.
The main hassle was merely creating a new ext4 partitions because "Partition Wizard" boot CD screwed up and I kept getting "Unable to update kernel until reboot" messages until I deleted and rebuilt all the partitions in the extended partition with puppy linux & gparted instead of Partition Wizard.
In case others stumble upon this trhread, here's some info:
The entry in the ubuntu (original) menu.lst was this:
title Arch Linux
uuid af7...etc...9f3c
kernel /boot/vmlinuz-linux root=UUID=af7...etc.f3c ro
initrd /boot/initramfs-linux.img
I'm even posting this from arch/fluxbox/Firefox, although getting X set up with nvidia (PITA!) apparently required using a different pacman source:
File "mirrorlist" now points to
Server = http://mirror.us.leaseweb.net/archlinux/$repo/os/$arch
which wasn't in the original file.
Then
$ pacman -Su --> "/etc/mtab exists" --> delete it and something else broke,
so
$ pacman -Su --force --> worked fine (against official advice)
Also: needed to install nvidia-utils and xorg-xinit
Thanks again! -
[SOLVED] Cannot boot with linux-3.5.3
Edit: Solved, as explained here.
Hello,
after upgrading to linux-3.5.3-1 my boot stopped at
:: running early hook [udev]
I tried upgrading to grub-bios-2.00, removing any customization I had in modprobe.conf and /etc/modules-load.d as well as removing the only module (radeon) from /etc/mkinitcpio.conf (obviously followed by mkinitcpio -p linux), which made me go on to
:: waiting for udev uevents to be processed [BUSY]
I'm not sure it's an actual progress.
My /etc/udev/rules.d is empty and /usr/lib/udev/rules.d only contains pacman-tracked stuff.
I enabled some debugging as described here but couldn't get anything useful - is there any way for such messages to be logged somewhere, so they can be pasted here?
I ended up downgrading to linux-3.4.9, which boots fine.
Any idea to troubleshoot this?
cat /etc/rc.conf
# /etc/rc.conf - configuration file for initscripts
# Most of rc.conf has been replaced by various other configuration
# files. See archlinux(7) for details.
# For more details on rc.conf see rc.conf(5).
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond dbus @networkmanager kdm @cpufreq sshd @cups @supervisor)
# Storage
# USEDMRAID="no"
# USELVM="no"
# Network
# interface=
# address=
# netmask=
# gateway=
cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
pacman -Qo /usr/lib/udev/rules.d/*
/usr/lib/udev/rules.d/10-dm.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/10-vboxdrv.rules is owned by virtualbox 4.1.20-2
/usr/lib/udev/rules.d/11-dm-lvm.rules is owned by lvm2 2.02.97-1
/usr/lib/udev/rules.d/13-dm-disk.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/40-gphoto.rules is owned by libgphoto2 2.4.14-1
/usr/lib/udev/rules.d/40-hpet-permissions.rules is owned by jack2 1.9.8-2
/usr/lib/udev/rules.d/40-usb-media-players.rules is owned by media-player-info 17-1
/usr/lib/udev/rules.d/42-usb-hid-pm.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/50-udev-default.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/53-sane.rules is owned by sane 1.0.23-1
/usr/lib/udev/rules.d/60-cdrom_id.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-pcmcia.rules is owned by pcmciautils 018-4
/usr/lib/udev/rules.d/60-persistent-alsa.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-input.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-serial.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage-tape.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-v4l.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-rfkill.rules is owned by rfkill 0.4-5
/usr/lib/udev/rules.d/61-accelerometer.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules is owned by gnome-bluetooth 3.4.2-1
/usr/lib/udev/rules.d/64-md-raid.rules is owned by mdadm 3.2.5-2
/usr/lib/udev/rules.d/65-kvm.rules is owned by qemu 1.1.1-1
/usr/lib/udev/rules.d/69-cd-sensors.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/69-libmtp.rules is owned by libmtp 1.1.4-1
/usr/lib/udev/rules.d/70-infrared.rules is owned by v4l-utils 0.8.8-1
/usr/lib/udev/rules.d/70-power-switch.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-uaccess.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-udev-acl.rules is owned by consolekit 0.4.6-4
/usr/lib/udev/rules.d/71-seat.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/73-seat-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-net-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-probe_mtd.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-tty-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/77-nm-olpc-mesh.rules is owned by networkmanager 0.9.4.0-6
/usr/lib/udev/rules.d/78-sound-card.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-drivers.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-udisks.rules is owned by udisks 1.0.4-5
/usr/lib/udev/rules.d/80-udisks2.rules is owned by udisks2 1.94.0-2
/usr/lib/udev/rules.d/85-usbmuxd.rules is owned by usbmuxd 1.0.8-1
/usr/lib/udev/rules.d/90-alsa-restore.rules is owned by alsa-utils 1.0.25-3
/usr/lib/udev/rules.d/90-libgpod.rules is owned by libgpod 0.8.2-6
/usr/lib/udev/rules.d/90-pulseaudio.rules is owned by pulseaudio 2.1-1
/usr/lib/udev/rules.d/95-cd-devices.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/95-dm-notify.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/95-keyboard-force-release.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-keymap.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-udev-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-csr.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-hid.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-wup.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules is owned by bluez 4.101-1
/usr/lib/udev/rules.d/99-systemd.rules is owned by systemd-tools 188-2
cat /var/log/pacman.log
[2012-08-28 12:27] Running 'pacman -Sy'
[2012-08-28 12:27] synchronizing package lists
[2012-08-28 14:51] Running 'pacman -S -u'
[2012-08-28 14:51] starting full system upgrade
[2012-08-28 14:53] upgraded gc (7.2.c-1 -> 7.2.d-1)
[2012-08-28 14:53] >>> Updating module dependencies. Please wait ...
[2012-08-28 14:53] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-28 14:53] ==> Building image from preset: 'default'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [autodetect]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] ==> Building image from preset: 'fallback'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] upgraded linux (3.4.9-1 -> 3.5.3-1)
[2012-08-28 14:53] upgraded lirc-utils (1:0.9.0-22 -> 1:0.9.0-26)
[2012-08-28 14:53] In order to use the new version, reload all virtualbox modules manually.
[2012-08-28 14:53] upgraded virtualbox-modules (4.1.20-1 -> 4.1.20-3)
[2012-08-28 14:59] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.3fb/google-chrome-21.0.1180.81-1-x86_64.pkg.tar.xz'
[2012-08-28 14:59] upgraded google-chrome (21.0.1180.57-1 -> 21.0.1180.81-1)
[2012-08-28 15:00] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.MgI/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:00] Running 'pacman -Sy'
[2012-08-28 15:00] synchronizing package lists
[2012-08-28 15:01] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.Vic/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:01] upgraded tunlr (0.1.4-1 -> 0.1.5-1)
[2012-08-28 17:34] Running 'pacman -S extra/kdeedu-kmplot'
[2012-08-28 17:34] installed kdeedu-kmplot (4.9.0-1)
[2012-08-29 10:20] Running 'pacman -Syu'
[2012-08-29 10:20] synchronizing package lists
[2012-08-29 10:20] starting full system upgrade
[2012-08-29 11:07] Running 'pacman -S grub-bios'
[2012-08-29 11:07] removed grub (0.97-21)
[2012-08-29 11:07] Generating grub.cfg.example config file...
[2012-08-29 11:07] This may fail on some machines running a custom kernel.
[2012-08-29 11:08] done.
[2012-08-29 11:08] installed grub-common (2.00-1)
[2012-08-29 11:08] installed grub-bios (2.00-1)
[2012-08-29 11:48] Running 'pacman -Sy'
[2012-08-29 11:48] synchronizing package lists
[2012-08-29 11:48] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -Sy'
[2012-08-29 12:11] synchronizing package lists
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -S -u'
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:15] upgraded firefox (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded firefox-i18n-it (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded gsmartcontrol (0.8.7-1 -> 0.8.7-2)
[2012-08-29 12:15] upgraded libwbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded smbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded samba (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded sane (1.0.22-9 -> 1.0.23-1)
[2012-08-29 12:15] upgraded syslinux (4.05-6 -> 4.05-7)
[2012-08-29 12:15] upgraded thunderbird (14.0-1 -> 15.0-1)
[2012-08-29 12:15] upgraded thunderbird-i18n-it (14.0-1 -> 15.0-1)
[2012-08-29 12:15] -> You can now set custom file descriptor ulimits for Tor in
[2012-08-29 12:15] -> "/etc/conf.d/tor" using the "TOR_MAX_FD" variable.
[2012-08-29 12:15] upgraded tor (0.2.2.37-1 -> 0.2.2.38-1)
[2012-08-29 12:56] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.K10/downgrade-3.0-1-any.pkg.tar.xz'
[2012-08-29 12:56] installed downgrade (3.0-1)
[2012-08-29 12:57] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:04] Running 'pacman -U /var/cache/pacman/pkg/virtualbox-modules-4.1.20-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -R virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rd virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rdd virtualbox-modules'
[2012-08-29 13:06] removed virtualbox-modules (4.1.20-3)
[2012-08-29 13:06] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:06] >>> Updating module dependencies. Please wait ...
[2012-08-29 13:06] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-29 13:06] ==> Building image from preset: 'default'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [autodetect]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:06] -> Running build hook: [sata]
[2012-08-29 13:06] -> Running build hook: [resume]
[2012-08-29 13:06] -> Running build hook: [filesystems]
[2012-08-29 13:06] -> Running build hook: [usbinput]
[2012-08-29 13:06] -> Running build hook: [fsck]
[2012-08-29 13:06] ==> Generating module dependencies
[2012-08-29 13:06] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Image generation successful
[2012-08-29 13:06] ==> Building image from preset: 'fallback'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:07] -> Running build hook: [sata]
[2012-08-29 13:07] -> Running build hook: [resume]
[2012-08-29 13:07] -> Running build hook: [filesystems]
[2012-08-29 13:07] -> Running build hook: [usbinput]
[2012-08-29 13:07] -> Running build hook: [fsck]
[2012-08-29 13:07] ==> Generating module dependencies
[2012-08-29 13:07] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-29 13:07] ==> Image generation successful
[2012-08-29 13:07] upgraded linux (3.5.3-1 -> 3.4.9-1)
[2012-08-29 14:47] Running 'pacman -Sy'
[2012-08-29 14:47] synchronizing package lists
[2012-08-29 14:49] Running 'pacman -S -u'
[2012-08-29 14:49] starting full system upgrade
Last edited by thujone (2012-09-19 12:18:51)because the report opener said that those freezes fixed with the 'futex' patch (included in 3.14-5).
As he says:
for those who have again problems despite the patch it means probably that there are another bugs further in the source code of kernel 3.14, bugs who are not necessarily related to the "futex problem"
i will try a clean profile, thanks.
Last edited by tritonas00 (2014-04-16 13:22:51) -
[SOLVED] Cannot write with root authorization too
Hello,
It's some time that I noticed I can't write in the Windows partition called sda2. Trying with sudo dolphin or sudo mv there aren't changes.
Why?
Thanks for attention,
Grant.
Last edited by Grant (2013-01-15 12:17:31)Please do not mark threads as solved without sharing your solution:
https://wiki.archlinux.org/index.php/Fo … way_Street -
[SOLVED] Dual boot with Windows 8, problems after updating Windows
Hi all,
I have been maintaining a dual boot of arch and Windows 8 for some time. I recently updated Windows to 8.1, and found that the update process had two side effects:
1) The update added a new partition in the middle of my file table, so my /etc/fstab which referenced "/dev/sda6" was wrong because that partition is now "/dev/sda7."
2) The default boot device was switched to the Windows Boot Loader instead of grub. But, this is not a problem because I can work around this by using the "Choose boot device" feature of my bios at start up.
So, neither of these problems are critical for me at the moment. I can fix my fstab and just press a hotkey at startup.
EDIT: I have avoided the /etc/fstab issue by referencing my partitions using UUID as specified in https://wiki.archlinux.org/index.php/Fstab.
How do I set the default boot device back to grub? There is some weirdness here, I think windows is using UEFI booting and my grub uses the old booting system.
Last edited by bjmnbraun (2014-05-14 19:00:36)Rex: I tried that command, got some warning messages regarding blocklists, but no dice.
Loqs: You are right about windows using a ESP and UEFI while my linux is not booting using UEFI. My bios is configured to try "Legacy boot" first before trying UEFI. Getting linux to boot using UEFI seemed like a pain, so...
I went into my BIOS settings and found that the Windows Boot Manager boot device was listed in front of my hard disk (which boots linux). I don't think this used to be the case, so something about the update caused my BIOS to reorder the boot devices (probably because the partitions changed).
Switching my hard disk to be above the Windows Boot Manager in the boot device list now makes me boot into linux by default, and I can boot into windows by pressing a hotkey at bootup and selecting the windows boot manager. -
[SOLVED]dual boot-Failed to mount real root device
Hello,
Here is my drives partition info:
/dev/sda1 2,949,122,048 3,907,028,991 957,906,944 7 NTFS / exFAT / HPFS
/dev/sda2 2,048 901,117,951 901,115,904 83 Linux
/dev/sda3 * 901,117,952 1,925,115,903 1,023,997,952 f W95 Extended (LBA)
/dev/sda5 901,120,000 901,439,487 319,488 83 Linux
/dev/sda6 901,441,536 905,648,127 4,206,592 82 Linux swap / Solaris
/dev/sda7 905,650,176 1,925,115,903 1,019,465,728 83 Linux
/dev/sda4 1,925,115,904 2,949,122,047 1,024,006,144 7 NTFS / exFAT / HPFS
/dev/sdb1 2,048 2,099,199 2,097,152 83 Linux
/dev/sdb2 2,099,200 53,299,199 51,200,000 83 Linux
/dev/sdb3 53,299,200 73,779,199 20,480,000 83 Linux
/dev/sdb4 73,779,200 224,673,791 150,894,592 7 NTFS / exFAT / HPFS
I installed Opensuse 12.1 on /dev/sda5. It is booting with Grub, working with no problems. The computer boots directly to Grub menu.
THEN, I installed Arch linux (last release) on both sda and sdb following these mounting points:
/dev/sdb1 mounted as /boot Ext2
/dev/sdb2 mounted as / BTRFS
/dev/sdb3 mounted as /usr BTRFS
/dev/sda2 mounted as /home BTRFS
Intstallation went smooth until the end. Installed the bootloader.
Now, I am trying to configure GRUB to boot Arch.
Here is what I added on /boot/grub/menu.lst, in sda5 under Opensuse:
title Arch Linux [/boot/vmlinuz-linux]
root (hd1,0)
kernel /vmlinuz-linux root=/dev/sdb1 ro
initrd /initramfs-linux.img
In Opensuse, i can check that vmlinux and grub/menu.lst are indeed in /dev/sdb1
My /etc/fstab is on /dev/sdb2
=============================== sdb2/etc/fstab: ==========
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda2 /home btrfs defaults 0 1
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb2 / btrfs defaults 0 1
/dev/sdb3 /usr btrfs defaults 0 1
With this parameters, i got an message error when booting Arch:
Mounting /dev/sdb1 on /new_root failed: no such device.
Error : failed to mount the real root device.
So, at busybox prompt, I tried this command line :
ramfs # mount -t ext2 /dev/sdb1
Got an error : Can't read /etc/fstab
I tried too to give a uuid adress to sdb1 in my menu.lst file, but it didn't change anything, so I am sure partition number is correct.
It seems to me in fact that GRUB can't find fstab.
Two questions :
-Would it be better in fact to use only 1 GRUB file for both systems? If yes, shall I keep only the grub config from Opensuse?
-What do I wrong with Arch booting? Why can't I boot Arch?
EDIT :1- just realised there is no BOOT flag in my partiton table on /dev/sdb.
2- root is on /dev/sdb2, not sdb1.
1-I toggled my first partition bootable using fdisk
2-changed root to point to /dev/sdb2
Now booting into Arch login
Last edited by gabx (2011-11-22 22:33:09)It was a very simple problem. I used the wrong uuid for my /
Correct entry in 40_custom is:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Arch Linux uuid" {
insmod part_msdos
insmod ext2
search --fs-uuid --no-floppy --set=root 8516fa60-0d45-4f33-b269-817c5290f6cc
linux /vmlinuz26 root=/dev/disk/by-uuid/9f32e668-2548-4ed4-a10b-3fbea66a6d95 ro vga=775
initrd /kernel26.img
Now the boot is working great. Next thing was that my /home and swap was not detected.
That was simply because /etc/fstab was still using /dev/sda etc naming. changing that to uuid solved that part as well.
To use uuid all the way and of cause the correct one solved everything
/Christer
Last edited by agkbill (2011-07-15 16:00:30) -
[SOLVED] Need help with rEFInd boot entry for rsync backup
I made a successful backup my arch install to an other internal SSD disk (from my HDD).
But now I can't figure out how to make a boot entry for this drive. The wiki only mentions GRUB, which I do not use.
This is the fstab for my HDD:
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda5
UUID=c1822e3c-e037-4445-bdd8-b71778237dee / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2 LABEL=SYSTEM_DRV
UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
And this is the fstab on my SSD which I edited:
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb1
UUID=c61a1301-4728-465d-b40b-bde5e084eb50 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2 LABEL=SYSTEM_DRV
UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
But I'm not sure about the /boot entry, do I need something else here?
Afterward I tried updating rEFInd by reinstalling using refind-install, but that did not work.
ps. I dual boot with Windows.
Last edited by Devenda (2014-08-18 07:58:07)I also tried adding the menu entry manually by editing refind.conf but that didn't work. I got:
Invalid loader file!
Error: Not Found while loading vmlinuz-linux
Here is some additional info:
refind.conf:
menuentry "SSD Arch Linux" {
icon /EFI/refind/icons/os_arch.png
volume "ArchSSD"
loader /boot/vmlinuz-linux
initrd /boot/initramfs-linux.img
options "root=/dev/sdb1 ro"
I hope this helps.
blkid
/dev/sda1: LABEL="WINRE_DRV" UUID="7C2ADD1D2ADCD4EC" TYPE="ntfs" PARTUUID="b7137819-2ca6-40fb-9167-b73ac37d8d96"
/dev/sda2: LABEL="SYSTEM_DRV" UUID="D2DF-9F74" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9c77b526-730f-42f9-9904-f9a31b205687"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="f4d5275b-24c1-4847-b937-345bc23bec89"
/dev/sda4: LABEL="Windows 8" UUID="38D6E449D6E408C8" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d777a359-f42c-4629-a07c-cc55316352fe"
/dev/sda5: UUID="c1822e3c-e037-4445-bdd8-b71778237dee" TYPE="ext4" PARTUUID="3d282004-2515-4630-b82e-35ed7f707b89"
/dev/sda6: UUID="F80680CC06808D76" TYPE="ntfs" PARTUUID="575bc623-c7f1-44da-a79e-220ce3c98d9b"
/dev/sda7: LABEL="Lenovo_Recovery" UUID="0898D76B98D75632" TYPE="ntfs" PARTUUID="99bfc6d6-1b71-46d1-887e-2f7e65e3eab1"
/dev/sdb1: LABEL="ArchSSD" UUID="c61a1301-4728-465d-b40b-bde5e084eb50" TYPE="ext4" PARTUUID="e87704a5-01"
lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs WINRE_DRV 7C2ADD1D2ADCD4EC
├─sda2 vfat SYSTEM_DRV D2DF-9F74 /boot
├─sda3
├─sda4 ntfs Windows 8 38D6E449D6E408C8
├─sda5 ext4 c1822e3c-e037-4445-bdd8-b71778237dee /
├─sda6 ntfs F80680CC06808D76
└─sda7 ntfs Lenovo_Recovery 0898D76B98D75632
sdb
└─sdb1 ext4 ArchSSD c61a1301-4728-465d-b40b-bde5e084eb50
sr0
boot tree
/boot
├── BOOT
│ └── boot.sdi
├── BOOTSECT.BAK
├── EFI
│ ├── Boot
│ │ ├── bootx64.efi
│ │ ├── LenovoBT.EFI
│ │ ├── License.txt
│ │ └── ReadMe.txt
│ ├── gummiboot
│ │ └── gummibootx64.efi
│ ├── Lenovo
│ │ └── Boot
│ │ ├── BCD
│ │ ├── BCD.LOG
│ │ ├── BCD.LOG1
│ │ ├── BCD.LOG2
│ │ ├── bg-BG
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── bootmgfw.efi
│ │ ├── bootmgr.efi
│ │ ├── BOOTSTAT.DAT
│ │ ├── boot.stl
│ │ ├── cs-CZ
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── da-DK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── de-DE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── el-GR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── en-GB
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── en-US
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── es-ES
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── et-EE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── fi-FI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Fonts
│ │ │ ├── chs_boot.ttf
│ │ │ ├── cht_boot.ttf
│ │ │ ├── jpn_boot.ttf
│ │ │ ├── kor_boot.ttf
│ │ │ ├── malgun_boot.ttf
│ │ │ ├── malgunn_boot.ttf
│ │ │ ├── meiryo_boot.ttf
│ │ │ ├── meiryon_boot.ttf
│ │ │ ├── msjh_boot.ttf
│ │ │ ├── msjhn_boot.ttf
│ │ │ ├── msyh_boot.ttf
│ │ │ ├── msyhn_boot.ttf
│ │ │ ├── segmono_boot.ttf
│ │ │ ├── segoen_slboot.ttf
│ │ │ ├── segoe_slboot.ttf
│ │ │ └── wgl4_boot.ttf
│ │ ├── fr-FR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── hr-HR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── hu-HU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── it-IT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ja-JP
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ko-KR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── lt-LT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── lv-LV
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── memtest.efi
│ │ ├── nb-NO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── nl-NL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pl-PL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-BR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-PT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── qps-ploc
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Resources
│ │ │ ├── bootres.dll
│ │ │ └── en-US
│ │ │ └── bootres.dll.mui
│ │ ├── ro-RO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── ru-RU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── sk-SK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sl-SI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sr-Latn-CS
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sv-SE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── tr-TR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── uk-UA
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── zh-CN
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── zh-HK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ └── zh-TW
│ │ ├── bootmgfw.efi.mui
│ │ ├── bootmgr.efi.mui
│ │ └── memtest.efi.mui
│ ├── Microsoft
│ │ └── Boot
│ │ ├── BCD
│ │ ├── BCD.LOG
│ │ ├── BCD.LOG1
│ │ ├── BCD.LOG2
│ │ ├── bg-BG
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── bootmgfw.efi
│ │ ├── bootmgr.efi
│ │ ├── BOOTSTAT.DAT
│ │ ├── boot.stl
│ │ ├── cs-CZ
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── da-DK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── de-DE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── el-GR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── en-GB
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── en-US
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── es-ES
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── et-EE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── fi-FI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Fonts
│ │ │ ├── chs_boot.ttf
│ │ │ ├── cht_boot.ttf
│ │ │ ├── jpn_boot.ttf
│ │ │ ├── kor_boot.ttf
│ │ │ ├── malgun_boot.ttf
│ │ │ ├── malgunn_boot.ttf
│ │ │ ├── meiryo_boot.ttf
│ │ │ ├── meiryon_boot.ttf
│ │ │ ├── msjh_boot.ttf
│ │ │ ├── msjhn_boot.ttf
│ │ │ ├── msyh_boot.ttf
│ │ │ ├── msyhn_boot.ttf
│ │ │ ├── segmono_boot.ttf
│ │ │ ├── segoen_slboot.ttf
│ │ │ ├── segoe_slboot.ttf
│ │ │ └── wgl4_boot.ttf
│ │ ├── fr-FR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── hr-HR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── hu-HU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── it-IT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ja-JP
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ko-KR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── lt-LT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── lv-LV
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── memtest.efi
│ │ ├── nb-NO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── nl-NL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pl-PL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-BR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-PT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── qps-ploc
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Resources
│ │ │ ├── bootres.dll
│ │ │ ├── en-US
│ │ │ │ └── bootres.dll.mui
│ │ │ └── nl-NL
│ │ │ └── bootres.dll.mui
│ │ ├── ro-RO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── ru-RU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── sk-SK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sl-SI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sr-Latn-CS
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sr-Latn-RS
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sv-SE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── tr-TR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── uk-UA
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── zh-CN
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── zh-HK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ └── zh-TW
│ │ ├── bootmgfw.efi.mui
│ │ ├── bootmgr.efi.mui
│ │ └── memtest.efi.mui
│ ├── refind
│ │ ├── icons
│ │ │ ├── arrow_left.png
│ │ │ ├── arrow_right.png
│ │ │ ├── boot_linux.png
│ │ │ ├── boot_win.png
│ │ │ ├── func_about.png
│ │ │ ├── func_exit.png
│ │ │ ├── func_firmware.png
│ │ │ ├── func_reset.png
│ │ │ ├── func_shutdown.png
│ │ │ ├── os_altlinux.png
│ │ │ ├── os_arch.png
│ │ │ ├── os_centos.png
│ │ │ ├── os_chrome.png
│ │ │ ├── os_clover.png
│ │ │ ├── os_debian.png
│ │ │ ├── os_ecomstation.png
│ │ │ ├── os_fatdog.png
│ │ │ ├── os_fedora.png
│ │ │ ├── os_freebsd.png
│ │ │ ├── os_freedos.png
│ │ │ ├── os_funtoo.png
│ │ │ ├── os_gentoo.png
│ │ │ ├── os_gummiboot.png
│ │ │ ├── os_haiku.png
│ │ │ ├── os_hwtest.png
│ │ │ ├── os_kubuntu.png
│ │ │ ├── os_legacy.png
│ │ │ ├── os_linuxmint.png
│ │ │ ├── os_linux.png
│ │ │ ├── os_lubuntu.png
│ │ │ ├── os_mac.png
│ │ │ ├── os_mageia.png
│ │ │ ├── os_mandriva.png
│ │ │ ├── os_manjaro.png
│ │ │ ├── os_mythbuntu.png
│ │ │ ├── os_netbsd.png
│ │ │ ├── os_openbsd.png
│ │ │ ├── os_opensuse.png
│ │ │ ├── os_redhat.png
│ │ │ ├── os_refind.png
│ │ │ ├── os_refit.png
│ │ │ ├── os_slackware.png
│ │ │ ├── os_suse.png
│ │ │ ├── os_ubuntu.png
│ │ │ ├── os_unknown.png
│ │ │ ├── os_win.png
│ │ │ ├── tool_apple_rescue.png
│ │ │ ├── tool_memtest.png
│ │ │ ├── tool_mok_tool.png
│ │ │ ├── tool_part.png
│ │ │ ├── tool_shell.png
│ │ │ ├── tool_windows_rescue.png
│ │ │ ├── transparent.png
│ │ │ ├── vol_external.png
│ │ │ ├── vol_internal.png
│ │ │ └── vol_optical.png
│ │ ├── icons-backup
│ │ │ ├── arrow_left.png
│ │ │ ├── arrow_right.png
│ │ │ ├── boot_linux.png
│ │ │ ├── boot_win.png
│ │ │ ├── func_about.png
│ │ │ ├── func_exit.png
│ │ │ ├── func_firmware.png
│ │ │ ├── func_reset.png
│ │ │ ├── func_shutdown.png
│ │ │ ├── os_altlinux.png
│ │ │ ├── os_arch.png
│ │ │ ├── os_centos.png
│ │ │ ├── os_chrome.png
│ │ │ ├── os_clover.png
│ │ │ ├── os_debian.png
│ │ │ ├── os_ecomstation.png
│ │ │ ├── os_fatdog.png
│ │ │ ├── os_fedora.png
│ │ │ ├── os_freebsd.png
│ │ │ ├── os_freedos.png
│ │ │ ├── os_funtoo.png
│ │ │ ├── os_gentoo.png
│ │ │ ├── os_gummiboot.png
│ │ │ ├── os_haiku.png
│ │ │ ├── os_hwtest.png
│ │ │ ├── os_kubuntu.png
│ │ │ ├── os_legacy.png
│ │ │ ├── os_linuxmint.png
│ │ │ ├── os_linux.png
│ │ │ ├── os_lubuntu.png
│ │ │ ├── os_mac.png
│ │ │ ├── os_mageia.png
│ │ │ ├── os_mandriva.png
│ │ │ ├── os_manjaro.png
│ │ │ ├── os_mythbuntu.png
│ │ │ ├── os_netbsd.png
│ │ │ ├── os_openbsd.png
│ │ │ ├── os_opensuse.png
│ │ │ ├── os_redhat.png
│ │ │ ├── os_refind.png
│ │ │ ├── os_refit.png
│ │ │ ├── os_slackware.png
│ │ │ ├── os_suse.png
│ │ │ ├── os_ubuntu.png
│ │ │ ├── os_unknown.png
│ │ │ ├── os_win.png
│ │ │ ├── tool_apple_rescue.png
│ │ │ ├── tool_memtest.png
│ │ │ ├── tool_mok_tool.png
│ │ │ ├── tool_part.png
│ │ │ ├── tool_shell.png
│ │ │ ├── tool_windows_rescue.png
│ │ │ ├── transparent.png
│ │ │ ├── vol_external.png
│ │ │ ├── vol_internal.png
│ │ │ └── vol_optical.png
│ │ ├── keys
│ │ │ ├── altlinux.cer
│ │ │ ├── canonical-uefi-ca.der
│ │ │ ├── fedora-ca.cer
│ │ │ ├── openSUSE-UEFI-CA-Certificate.cer
│ │ │ ├── refind.cer
│ │ │ └── SLES-UEFI-CA-Certificate.cer
│ │ ├── refind.conf
│ │ ├── refind.conf.old
│ │ ├── refind.conf-sample
│ │ └── refind_x64.efi
│ └── tools
├── grub
│ ├── grub.cfg
│ └── grub.cfg.example
├── initramfs-linux-fallback.img
├── initramfs-linux.img
├── loader
│ ├── entries
│ │ └── arch.conf
│ └── loader.conf
├── refind_linux.conf
└── vmlinuz-linux
refind_linux.conf
"Boot with standard options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet "
"Boot to single-user mode" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet single"
"Boot with minimal options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee" -
[SOLVED] RTC and dual booting with Windows 8/8.1
I am planning ahead of installing Arch on a windows 8.1 laptop, and need to understand whether or not the known Windows registry hack to get windows to use UTC for the RTC is still valid for Windows 8/8.1? I have been searching via google and the usual sources of information, but it is not clear to me if there are problems doing this, specifically if arch is dual booted with Windows 8/8.1 rather than older versions of the MS OS. Certainly I have used the technique without any problem in the past when dual booting Windows XP with Arch on several different machines.
Does anyone have personal experience with doing this on a Windows 8 or 8.1 machine and can report here on whether it works successfully or not?
Thanks for any advice.
Last edited by mcloaked (2014-02-11 21:16:21)Since there were no replies at this point I thought I would just go ahead and implement the registry hack on the Windows 8.1 O/S in the laptop and see if Windows behaves. It appears to be OK, with the displayed time being correct after reboot, and time synchronisation remaining fine with no problems seen in the displayed time, although I won't be able to read the RTC directly until I have completed the Arch install in the coming week or two. I now don't foresee any issues with the time synchronisation between booting Arch and Windows 8.1 so I will mark this as solved.
Since the RTC is now in UTC then normal clock config in Arch using chrony should perform normally once the install is done and the new system set up.
Last edited by mcloaked (2014-02-11 21:17:11) -
[Solved] Problem booting root in LVM, which spans two LUKS partitions
Hello,
I recently switched to Arch from OpenSuse, and I'm having a bit of trouble getting my encrypted disks to boot properly. I have two disks, the first is a 4 TB drive set up like this:
MBR partition table
Partition 1 - Windows 7, 200GB
Partition 2 - Linux boot, 200MB
Partition 3 - Luks partition, 1.7TB
Partition 4 - Luks partition, 1.7TB
Within partition 3 and 4 is an LVM volume which spans the two partitions. The reason for that is just that I can't have a 3.4TB partition on an MBR formatted drive (as I understand it). I have the root volume and swap, etc within this LVM. The second hard drive is simply a data drive, also encrypted. My problem is that I don't know how to tell the system to open both of these encrypted partitions at boot, in order to boot the root volume. This worked fine under OpenSuse and I only needed to enter the Luks password once (it is the same for both partitions).
As it is right now, my boot parameters in /etc/default/grub look like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset cryptdevice=/dev/sda3:sda3_crypt root=/dev/mapper/vg_arch-root"
Currently the system boots, asks for the password to /dev/sda3, hangs for roughly 20 seconds and then kicks me into a root prompt. I can manually open /dev/sda4 at this point using cryptsetup and the system will continue booting normally... but I would like to have it set up properly, so I don't need to do that. Considering OpenSuse does this out of the box I figured it should be possible under Arch. Any help would be appreciated.
Thanks
Last edited by keitolainen (2015-06-09 21:56:08)As a quick update in case anyone is reading this, I cleaned up the script a bit and hopefully made it something closer to a "proper" fix.
Rather than editing /usr/lib/initcpio/hooks/encrypt directly, I did the following:
cp /usr/lib/initcpio/hooks/encrypt /etc/initcpio/hooks/
then changed the following section of /etc/initcpio/hooks/encrypt from:
# Ask for a passphrase
if [ ${dopassphrase} -gt 0 ]; then
echo ""
echo "A password is required to access the ${cryptname} volume:"
#loop until we get a real password
while ! eval cryptsetup open --type luks ${resolved} ${cryptname} ${cryptargs} ${CSQUIET}; do
sleep 2;
done
fi
to:
# Ask for a passphrase
if [ ${dopassphrase} -gt 0 ]; then
echo ""
while true ; do
echo -n "A password is required to access the ${cryptname} volume: "
read -sr password
echo $password | cryptsetup open --type luks ${resolved} ${cryptname} ${cryptargs} ${CSQUIET}
if [ $? = 0 ] ; then
break
fi
done
echo $password | cryptsetup open --type luks /dev/sda4 sda4_crypt
echo ""
fi
then edited /etc/mkinitcpio.conf and changed:
FILES=""
to:
FILES="/etc/initcpio/hooks/encrypt"
and ran
mkinitcpio
This is working well for me and I think it's a little cleaner than the solution I posted earlier. Sorry for the awkward bash, if anyone has a more elegant solution please let me know. -
[SOLVED]How to configure pptp vpn start on boot with netcfg?
I've configured 2 profiles:
eth0 and ppp0, where ppp0 is a pptp vpn tunnel.
$ ls /etc/network.d/
eth0 examples interfaces ppp0
$ cat /etc/network.d/ppp0
CONNECTION='ppp'
INTERFACE='ppp0'
PEER='dxt'
PPP_TIMEOUT=10
$ cat /etc/conf.d/netcfg
# Enable these netcfg profiles at boot time.
# - prefix an entry with a '@' to background its startup
# - set to 'last' to restore the profiles running at the last shutdown
# - set to 'menu' to present a menu (requires the dialog package)
# Network profiles are found in /etc/network.d
NETWORKS=(eth0 ppp0)
# Specify the name of your wired interface for net-auto-wired
WIRED_INTERFACE="eth0"
# Specify the name of your wireless interface for net-auto-wireless
WIRELESS_INTERFACE="wlan0"
Manually, I can start up ppp0 correctly.
$ sudo netcfg -u ppp0
:: ppp0 up [ BUSY ] Using interface ppp0
Connect: ppp0 <--> /dev/pts/3
CHAP authentication succeeded
MPPE 128-bit stateless compression enabled
Cannot determine ethernet address for proxy ARP
local IP address 10.100.3.132
remote IP address 10.100.3.1
[ DONE ]
$ ip addr list dev ppp0
8: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1496 qdisc pfifo_fast state UNKNOWN qlen 3
link/ppp
inet 10.100.3.132 peer 10.100.3.1/32 scope global ppp0
But after booting, only eth0 is up. How to configure ppp0 to start on boot with netcfg?
Last edited by rchiang (2012-12-21 01:09:32)Thanks a lot for your instruction.
netcfg works now!
chris_l wrote:
Did you
systemctl enable [email protected] -
[SOLVED] Disabling Bluetooth on boot with systemd
I'm having a nasty-won't-go-away problem with the disabling of the bluetooth module in my Thinkpad X200s.
Resorting to the old Arch way of disabling bluetooth on boot, I added this to my rc.local:
/bin/echo 0 > /sys/devices/platform/thinkpad_acpi/bluetooth_enable
The thing is, this somehow made my boots hit'n'miss: kernel panics every two boots. As soon as I commented that line from my rc.local... no more kernel panics at boot.
I was still using an rc.conf just with daemons, and in troubleshooting the kernel panics got rid of it and used the systemd way of enabling/disabling services. My problem here is that the bluetooth service seems to be impossible to disable.
I first tried the good ol'
systemctl disable bluetooth.service
Which supposedly disabled bluetooth... but didn't. Even
systemctl stop bluetooth.service
Does not work.
Digging around the interwebs, I found that there are "stronger" ways to disable services with systemd, meaning "masking" services - basically links them to /dev/null
So, I tried masking the bugger...
systemctl mask bluetooth.service
Reboot and... the damn bluetooth is still enabled. Only way that works is to echo 0 > /sys/devices/platform/thinkpad_acpi/bluetooth_enable... but I can't do it at boot with rc.local, otherwise I'll get the kernel panics again.
Any ideas?
Last edited by Onyros (2012-08-15 13:10:35)Onyros wrote:
I'm having a nasty-won't-go-away problem with the disabling of the bluetooth module in my Thinkpad X200s.
Resorting to the old Arch way of disabling bluetooth on boot, I added this to my rc.local:
/bin/echo 0 > /sys/devices/platform/thinkpad_acpi/bluetooth_enable
The thing is, this somehow made my boots hit'n'miss: kernel panics every two boots. As soon as I commented that line from my rc.local... no more kernel panics at boot.
I was still using an rc.conf just with daemons, and in troubleshooting the kernel panics got rid of it and used the systemd way of enabling/disabling services. My problem here is that the bluetooth service seems to be impossible to disable.
I first tried the good ol'
systemctl disable bluetooth.service
Which supposedly disabled bluetooth... but didn't.
It disables the bluetooth service which is very different from what your write to sysfs accomplishes. Don't you really just want to blacklist the bluetooth module? Your post is a bit hard to follow... -
[Solved] Unable to find root device
Hi guys,
it's been three days now that my laptop refuses to boot with a message from systemd like this:
ERROR: device 'UUID=xxx...' not found. Skipping fsck.
ERROR: Unable to find root device 'UUID=xxx...'.
You are being dropped to a recovery shell.
That said, keep in mind that I'm saying "three days" just because it's in the past two days that I've spent most of the time searching in the Internet for a solution of what seems just to be a well-known, very common problem, especially when it arises after a kernel upgrade (as in my case).
But believe me, I've been trying this and that through the live Arch Linux environment, but without the slightest improvement: regeneration of the initramfs, regeneration of /etc/fstab, reconfiguration of GRUB (although this was clearly unhelpful, since the problem arises when the kernel has already been booted), small changes in the hooks in /etc/mkinitcpio.conf, small changes to some modules loaded at boot, downgrading linux... Nothing works.
I'm now writing from another computer, so I cannot post the entire output of useful commands now, but if you need to know something I will give you the necessary information.
In the meanwhile, notice that I use Linux LVM partition with logical volumes formatted with Btrfs, without encryption.
It's strange that even with the dowgrade from Linux 3.18.3 (the one after whose installation the system was unusable) to 3.18.2 the problem still remains.
However, the only thing I managed to take from my system is the output of dmesg, obtained from the recovery shell, after having set the debug settings for systemd in the kernel command line before booting.
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.18.4-1-ARCH (builduser@tobias) (gcc version 4.9.2 20141224 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Jan 27 20:45:02 CET 2015
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=345f6168-2ff7-41fd-bf0e-050d4dd6795d systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M rw quiet
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x00000000000913ff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000091400-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000c8c6cfff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000c8c6d000-0x00000000dae8cfff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000dae8d000-0x00000000daeb6fff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000daeb7000-0x00000000db802fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000db803000-0x00000000dbafffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000dd000000-0x00000000df1fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000021edfffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.8 present.
[ 0.000000] DMI: Dell Inc. Latitude E5550/0YM97J, BIOS A03 10/30/2014
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] AGP: No AGP bridge found
[ 0.000000] e820: last_pfn = 0x21ee00 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask 7E00000000 write-back
[ 0.000000] 1 base 0200000000 mask 7FE0000000 write-back
[ 0.000000] 2 base 00E0000000 mask 7FE0000000 uncachable
[ 0.000000] 3 base 00DE000000 mask 7FFE000000 uncachable
[ 0.000000] 4 base 00DD000000 mask 7FFF000000 uncachable
[ 0.000000] 5 base 021F000000 mask 7FFF000000 uncachable
[ 0.000000] 6 base 021EE00000 mask 7FFFE00000 uncachable
[ 0.000000] 7 disabled
[ 0.000000] 8 disabled
[ 0.000000] 9 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820: update [mem 0xdd000000-0xffffffff] usable ==> reserved
[ 0.000000] e820: last_pfn = 0xc8c6d max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [mem 0x000fda70-0x000fda7f] mapped at [ffff8800000fda70]
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff88000008b000] 8b000 size 24576
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] BRK [0x01b36000, 0x01b36fff] PGTABLE
[ 0.000000] BRK [0x01b37000, 0x01b37fff] PGTABLE
[ 0.000000] BRK [0x01b38000, 0x01b38fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x21ec00000-0x21edfffff]
[ 0.000000] [mem 0x21ec00000-0x21edfffff] page 2M
[ 0.000000] BRK [0x01b39000, 0x01b39fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x21c000000-0x21ebfffff]
[ 0.000000] [mem 0x21c000000-0x21ebfffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x200000000-0x21bffffff]
[ 0.000000] [mem 0x200000000-0x21bffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x00100000-0xc8c6cfff]
[ 0.000000] [mem 0x00100000-0x001fffff] page 4k
[ 0.000000] [mem 0x00200000-0x3fffffff] page 2M
[ 0.000000] [mem 0x40000000-0xbfffffff] page 1G
[ 0.000000] [mem 0xc0000000-0xc8bfffff] page 2M
[ 0.000000] [mem 0xc8c00000-0xc8c6cfff] page 4k
[ 0.000000] init_memory_mapping: [mem 0x100000000-0x1ffffffff]
[ 0.000000] [mem 0x100000000-0x1ffffffff] page 1G
[ 0.000000] log_buf_len: 1048576 bytes
[ 0.000000] early log buf free: 519600(99%)
[ 0.000000] RAMDISK: [mem 0x3539c000-0x369c5fff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000000EF280 000024 (v02 DELL )
[ 0.000000] ACPI: XSDT 0x00000000DAE960A8 0000CC (v01 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: FACP 0x00000000DAEA9C60 00010C (v05 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: DSDT 0x00000000DAE96200 013A5B (v02 DELL CBX3 01072009 INTL 20120913)
[ 0.000000] ACPI: FACS 0x00000000DB800F80 000040
[ 0.000000] ACPI: APIC 0x00000000DAEA9D70 000084 (v03 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: FPDT 0x00000000DAEA9DF8 000044 (v01 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: FIDT 0x00000000DAEA9E40 00009C (v01 DELL CBX3 01072009 AMI 00010013)
[ 0.000000] ACPI: MCFG 0x00000000DAEA9EE0 00003C (v01 DELL CBX3 01072009 MSFT 00000097)
[ 0.000000] ACPI: HPET 0x00000000DAEA9F20 000038 (v01 DELL CBX3 01072009 AMI. 00000005)
[ 0.000000] ACPI: SSDT 0x00000000DAEA9F58 0004B5 (v01 SataRe SataTabl 00001000 INTL 20120913)
[ 0.000000] ACPI: UEFI 0x00000000DAEAA410 000042 (v01 00000000 00000000)
[ 0.000000] ACPI: SSDT 0x00000000DAEAA458 000C7D (v02 Ther_R Ther_Rvp 00001000 INTL 20120913)
[ 0.000000] ACPI: ASF! 0x00000000DAEAB0D8 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240)
[ 0.000000] ACPI: SSDT 0x00000000DAEAB178 00051F (v02 PmRef Cpu0Ist 00003000 INTL 20120913)
[ 0.000000] ACPI: SSDT 0x00000000DAEAB698 000B74 (v02 CpuRef CpuSsdt 00003000 INTL 20120913)
[ 0.000000] ACPI: SSDT 0x00000000DAEAC210 0001C7 (v02 PmRef LakeTiny 00003000 INTL 20120913)
[ 0.000000] ACPI: SSDT 0x00000000DAEAC3D8 0003A5 (v02 CppcTa CppcTabl 00001000 INTL 20120913)
[ 0.000000] ACPI: PCCT 0x00000000DAEAC780 00006E (v05 PcctTa PcctTabl 00001000 INTL 20120913)
[ 0.000000] ACPI: SSDT 0x00000000DAEAC7F0 000AC4 (v02 Cpc_Ta Cpc_Tabl 00001000 INTL 20120913)
[ 0.000000] ACPI: SSDT 0x00000000DAEAD2B8 0041AC (v02 SaSsdt SaSsdt 00003000 INTL 20120913)
[ 0.000000] ACPI: SSDT 0x00000000DAEB1468 004508 (v01 DptfTa DptfTabl 00001000 INTL 20120913)
[ 0.000000] ACPI: SLIC 0x00000000DAEB5970 000176 (v03 DELL CBX3 01072009 MSFT 00010013)
[ 0.000000] ACPI: MSDM 0x00000000DAEB5AE8 000055 (v03 DELL CBX3 06222004 AMI 00010013)
[ 0.000000] ACPI: DMAR 0x00000000DAEB5B40 0000B0 (v01 INTEL BDW 00000001 INTL 00000001)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000021edfffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x21ecfa000-0x21ecfdfff]
[ 0.000000] [ffffea0000000000-ffffea00087fffff] PMD -> [ffff880216800000-ffff88021e3fffff] on node 0
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal [mem 0x100000000-0x21edfffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00001000-0x00090fff]
[ 0.000000] node 0: [mem 0x00100000-0xc8c6cfff]
[ 0.000000] node 0: [mem 0x100000000-0x21edfffff]
[ 0.000000] Initmem setup node 0 [mem 0x00001000-0x21edfffff]
[ 0.000000] On node 0 totalpages: 1997309
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 21 pages reserved
[ 0.000000] DMA zone: 3984 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 12786 pages used for memmap
[ 0.000000] DMA32 zone: 818285 pages, LIFO batch:31
[ 0.000000] Normal zone: 18360 pages used for memmap
[ 0.000000] Normal zone: 1175040 pages, LIFO batch:31
[ 0.000000] Reserving Intel graphics stolen memory at 0xdd200000-0xdf1fffff
[ 0.000000] ACPI: PM-Timer IO Port: 0x1808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high dfl lint[0xe4])
[ 0.000000] ACPI: NMI not connected to LINT 1!
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] dfl edge lint[0x35])
[ 0.000000] ACPI: NMI not connected to LINT 1!
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] dfl edge lint[0x4b])
[ 0.000000] ACPI: NMI not connected to LINT 1!
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x59])
[ 0.000000] ACPI: NMI not connected to LINT 1!
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-39
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x00091000-0x00091fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x00092000-0x0009ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xc8c6d000-0xdae8cfff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdae8d000-0xdaeb6fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdaeb7000-0xdb802fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdb803000-0xdbafffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdbb00000-0xdcffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdd000000-0xdf1fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdf200000-0xf7ffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
[ 0.000000] e820: [mem 0xdf200000-0xf7ffffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 30 pages/cpu @ffff88021ea00000 s82880 r8192 d31808 u524288
[ 0.000000] pcpu-alloc: s82880 r8192 d31808 u524288 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1966078
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=345f6168-2ff7-41fd-bf0e-050d4dd6795d systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M rw quiet
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
[ 0.000000] AGP: Checking aperture...
[ 0.000000] AGP: No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 7760140K/7989236K available (5479K kernel code, 908K rwdata, 1720K rodata, 1160K init, 1184K bss, 229096K reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS:8448 nr_irqs:728 0
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] allocated 32505856 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 2593.984 MHz processor
[ 0.000025] Calibrating delay loop (skipped), value calculated using timer frequency.. 5190.13 BogoMIPS (lpj=8646613)
[ 0.000028] pid_max: default: 32768 minimum: 301
[ 0.000032] ACPI: Core revision 20140926
[ 0.020437] ACPI: All ACPI Tables successfully acquired
[ 0.021107] Security Framework initialized
[ 0.021114] Yama: becoming mindful.
[ 0.021531] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.023288] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.024091] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.024099] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.024297] Initializing cgroup subsys memory
[ 0.024302] Initializing cgroup subsys devices
[ 0.024304] Initializing cgroup subsys freezer
[ 0.024305] Initializing cgroup subsys net_cls
[ 0.024307] Initializing cgroup subsys blkio
[ 0.024325] CPU: Physical Processor ID: 0
[ 0.024326] CPU: Processor Core ID: 0
[ 0.024329] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.024329] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.025227] mce: CPU supports 7 MCE banks
[ 0.025238] CPU0: Thermal monitoring enabled (TM1)
[ 0.025247] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
[ 0.025247] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
[ 0.025334] Freeing SMP alternatives memory: 20K (ffffffff81a07000 - ffffffff81a0c000)
[ 0.026009] ftrace: allocating 20921 entries in 82 pages
[ 0.033432] dmar: Host address width 39
[ 0.033434] dmar: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.033442] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c0000020660462 ecap f0101a
[ 0.033443] dmar: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.033447] dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da
[ 0.033448] dmar: RMRR base: 0x000000db9ee000 end: 0x000000db9fcfff
[ 0.033449] dmar: RMRR base: 0x000000dd000000 end: 0x000000df1fffff
[ 0.033571] IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.033572] HPET id 0 under DRHD base 0xfed91000
[ 0.033573] Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.033573] Your BIOS is broken and requested that x2apic be disabled.
[ 0.033573] This will slightly decrease performance.
[ 0.033573] Use 'intremap=no_x2apic_optout' to override BIOS request.
[ 0.033713] Enabled IRQ remapping in xapic mode
[ 0.033713] x2apic not enabled, IRQ remapping is in xapic mode
[ 0.034335] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.067359] smpboot: CPU0: Intel(R) Core(TM) i5-4310U CPU @ 2.00GHz (fam: 06, model: 45, stepping: 01)
[ 0.067366] TSC deadline timer enabled
[ 0.067387] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
[ 0.067404] ... version: 3
[ 0.067405] ... bit width: 48
[ 0.067406] ... generic registers: 4
[ 0.067407] ... value mask: 0000ffffffffffff
[ 0.067407] ... max period: 0000ffffffffffff
[ 0.067408] ... fixed-purpose events: 3
[ 0.067409] ... event mask: 000000070000000f
[ 0.090846] x86: Booting SMP configuration:
[ 0.090848] .... node #0, CPUs: #1
[ 0.105028] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.111723] #2 #3
[ 0.146545] x86: Booted up 1 node, 4 CPUs
[ 0.146548] smpboot: Total of 4 processors activated (20760.53 BogoMIPS)
[ 0.149839] devtmpfs: initialized
[ 0.151742] PM: Registering ACPI NVS region [mem 0xdaeb7000-0xdb802fff] (9748480 bytes)
[ 0.152488] pinctrl core: initialized pinctrl subsystem
[ 0.152525] RTC time: 14:27:35, date: 01/29/15
[ 0.152613] NET: Registered protocol family 16
[ 0.163220] cpuidle: using governor ladder
[ 0.176565] cpuidle: using governor menu
[ 0.176604] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 0.176606] ACPI: bus type PCI registered
[ 0.176607] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.176682] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[ 0.176684] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[ 0.176776] PCI: Using configuration type 1 for base access
[ 0.176783] dmi type 0xB1 record - unknown flag
[ 0.190254] ACPI: Added _OSI(Module Device)
[ 0.190257] ACPI: Added _OSI(Processor Device)
[ 0.190258] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.190259] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.195406] ACPI: Executed 16 blocks of module-level executable AML code
[ 0.527048] ACPI: Dynamic OEM Table Load:
[ 0.527056] ACPI: SSDT 0xFFFF88021322C800 0003D3 (v02 PmRef Cpu0Cst 00003001 INTL 20120913)
[ 0.540534] ACPI: Dynamic OEM Table Load:
[ 0.540541] ACPI: SSDT 0xFFFF8802131E2000 0005AA (v02 PmRef ApIst 00003000 INTL 20120913)
[ 0.553725] ACPI: Dynamic OEM Table Load:
[ 0.553731] ACPI: SSDT 0xFFFF8802131DD200 000119 (v02 PmRef ApCst 00003000 INTL 20120913)
[ 0.607146] ACPI: Interpreter enabled
[ 0.607157] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140926/hwxface-580)
[ 0.607166] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140926/hwxface-580)
[ 0.607184] ACPI: (supports S0 S3 S4 S5)
[ 0.607185] ACPI: Using IOAPIC for interrupt routing
[ 0.607218] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.608649] ACPI: Power Resource [PG00] (on)
[ 0.620317] ACPI: Power Resource [PG01] (on)
[ 0.640702] ACPI: Power Resource [PG02] (on)
[ 1.401836] ACPI: Power Resource [FN00] (off)
[ 1.401913] ACPI: Power Resource [FN01] (off)
[ 1.401986] ACPI: Power Resource [FN02] (off)
[ 1.402057] ACPI: Power Resource [FN03] (off)
[ 1.402127] ACPI: Power Resource [FN04] (off)
[ 1.403037] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[ 1.403043] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 1.403622] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
[ 1.404193] PCI host bridge to bus 0000:00
[ 1.404195] pci_bus 0000:00: root bus resource [bus 00-3e]
[ 1.404196] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 1.404198] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 1.404199] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 1.404200] pci_bus 0000:00: root bus resource [mem 0xdf200000-0xfeafffff]
[ 1.404207] pci 0000:00:00.0: [8086:0a04] type 00 class 0x060000
[ 1.404286] pci 0000:00:02.0: [8086:0a16] type 00 class 0x030000
[ 1.404296] pci 0000:00:02.0: reg 0x10: [mem 0xf7800000-0xf7bfffff 64bit]
[ 1.404301] pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
[ 1.404305] pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]
[ 1.404376] pci 0000:00:03.0: [8086:0a0c] type 00 class 0x040300
[ 1.404383] pci 0000:00:03.0: reg 0x10: [mem 0xf7e3c000-0xf7e3ffff 64bit]
[ 1.404461] pci 0000:00:04.0: [8086:0a03] type 00 class 0x118000
[ 1.404471] pci 0000:00:04.0: reg 0x10: [mem 0xf7e30000-0xf7e37fff 64bit]
[ 1.404565] pci 0000:00:14.0: [8086:9c31] type 00 class 0x0c0330
[ 1.404580] pci 0000:00:14.0: reg 0x10: [mem 0xf7e20000-0xf7e2ffff 64bit]
[ 1.404631] pci 0000:00:14.0: PME# supported from D3hot D3cold
[ 1.404674] pci 0000:00:14.0: System wakeup disabled by ACPI
[ 1.404707] pci 0000:00:16.0: [8086:9c3a] type 00 class 0x078000
[ 1.404725] pci 0000:00:16.0: reg 0x10: [mem 0xf7e46000-0xf7e4601f 64bit]
[ 1.404787] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[ 1.404856] pci 0000:00:19.0: [8086:15a2] type 00 class 0x020000
[ 1.404870] pci 0000:00:19.0: reg 0x10: [mem 0xf7e00000-0xf7e1ffff]
[ 1.404876] pci 0000:00:19.0: reg 0x14: [mem 0xf7e43000-0xf7e43fff]
[ 1.404882] pci 0000:00:19.0: reg 0x18: [io 0xf080-0xf09f]
[ 1.404937] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
[ 1.445821] pci 0000:00:19.0: System wakeup disabled by ACPI
[ 1.445873] pci 0000:00:1b.0: [8086:9c20] type 00 class 0x040300
[ 1.445892] pci 0000:00:1b.0: reg 0x10: [mem 0xf7e38000-0xf7e3bfff 64bit]
[ 1.445956] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 1.446016] pci 0000:00:1b.0: System wakeup disabled by ACPI
[ 1.446062] pci 0000:00:1c.0: [8086:9c10] type 01 class 0x060400
[ 1.446146] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 1.446197] pci 0000:00:1c.0: System wakeup disabled by ACPI
[ 1.446246] pci 0000:00:1c.3: [8086:9c16] type 01 class 0x060400
[ 1.446328] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
[ 1.446379] pci 0000:00:1c.3: System wakeup disabled by ACPI
[ 1.446423] pci 0000:00:1c.4: [8086:9c18] type 01 class 0x060400
[ 1.446505] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[ 1.446555] pci 0000:00:1c.4: System wakeup disabled by ACPI
[ 1.446601] pci 0000:00:1d.0: [8086:9c26] type 00 class 0x0c0320
[ 1.446621] pci 0000:00:1d.0: reg 0x10: [mem 0xf7e42000-0xf7e423ff]
[ 1.446711] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 1.446770] pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 1.446812] pci 0000:00:1f.0: [8086:9c43] type 00 class 0x060100
[ 1.446999] pci 0000:00:1f.2: [8086:282a] type 00 class 0x010400
[ 1.447014] pci 0000:00:1f.2: reg 0x10: [io 0xf0d0-0xf0d7]
[ 1.447021] pci 0000:00:1f.2: reg 0x14: [io 0xf0c0-0xf0c3]
[ 1.447027] pci 0000:00:1f.2: reg 0x18: [io 0xf0b0-0xf0b7]
[ 1.447034] pci 0000:00:1f.2: reg 0x1c: [io 0xf0a0-0xf0a3]
[ 1.447041] pci 0000:00:1f.2: reg 0x20: [io 0xf060-0xf07f]
[ 1.447048] pci 0000:00:1f.2: reg 0x24: [mem 0xf7e41000-0xf7e417ff]
[ 1.447087] pci 0000:00:1f.2: PME# supported from D3hot
[ 1.447164] pci 0000:00:1f.3: [8086:9c22] type 00 class 0x0c0500
[ 1.447177] pci 0000:00:1f.3: reg 0x10: [mem 0xf7e40000-0xf7e400ff 64bit]
[ 1.447196] pci 0000:00:1f.3: reg 0x20: [io 0xf040-0xf05f]
[ 1.449196] pci 0000:01:00.0: [1217:8520] type 00 class 0x080501
[ 1.449218] pci 0000:01:00.0: reg 0x10: [mem 0xf7d01000-0xf7d01fff]
[ 1.449231] pci 0000:01:00.0: reg 0x14: [mem 0xf7d00000-0xf7d007ff]
[ 1.449369] pci 0000:01:00.0: PME# supported from D3hot D3cold
[ 1.449400] pci 0000:01:00.0: System wakeup disabled by ACPI
[ 1.457648] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 1.457653] pci 0000:00:1c.0: bridge window [mem 0xf7d00000-0xf7dfffff]
[ 1.458041] pci 0000:02:00.0: [8086:095a] type 00 class 0x028000
[ 1.458129] pci 0000:02:00.0: reg 0x10: [mem 0xf7c00000-0xf7c01fff 64bit]
[ 1.458420] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[ 1.458511] pci 0000:02:00.0: System wakeup disabled by ACPI
[ 1.462692] pci 0000:00:1c.3: PCI bridge to [bus 02]
[ 1.462697] pci 0000:00:1c.3: bridge window [mem 0xf7c00000-0xf7cfffff]
[ 1.462787] pci 0000:00:1c.4: PCI bridge to [bus 03]
[ 1.464747] acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
[ 1.547152] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
[ 1.547202] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
[ 1.547250] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
[ 1.547296] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *10 11 12 14 15)
[ 1.547342] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 10 11 12 14 15)
[ 1.547388] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 *4 5 6 10 11 12 14 15)
[ 1.547434] ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 10 11 12 14 15)
[ 1.547480] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
[ 1.613841] ACPI: Enabled 3 GPEs in block 00 to 7F
[ 1.613905] ACPI : EC: GPE = 0x27, I/O: command/status = 0x934, data = 0x930
[ 1.614013] vgaarb: setting as boot device: PCI:0000:00:02.0
[ 1.614016] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 1.614019] vgaarb: loaded
[ 1.614020] vgaarb: bridge control possible 0000:00:02.0
[ 1.614099] PCI: Using ACPI for IRQ routing
[ 1.615308] PCI: pci_cache_line_size set to 64 bytes
[ 1.615344] e820: reserve RAM buffer [mem 0x00091400-0x0009ffff]
[ 1.615345] e820: reserve RAM buffer [mem 0xc8c6d000-0xcbffffff]
[ 1.615346] e820: reserve RAM buffer [mem 0x21ee00000-0x21fffffff]
[ 1.615428] NetLabel: Initializing
[ 1.615429] NetLabel: domain hash size = 128
[ 1.615429] NetLabel: protocols = UNLABELED CIPSOv4
[ 1.615438] NetLabel: unlabeled traffic allowed by default
[ 1.615467] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 1.615471] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[ 1.617497] Switched to clocksource hpet
[ 1.621576] pnp: PnP ACPI init
[ 1.621752] system 00:00: [io 0x0680-0x069f] has been reserved
[ 1.621755] system 00:00: [io 0xffff] has been reserved
[ 1.621756] system 00:00: [io 0xffff] has been reserved
[ 1.621758] system 00:00: [io 0xffff] has been reserved
[ 1.621759] system 00:00: [io 0x1800-0x18fe] could not be reserved
[ 1.621761] system 00:00: [io 0x164e-0x164f] has been reserved
[ 1.621763] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 1.621806] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 1.621837] system 00:02: [io 0x1854-0x1857] has been reserved
[ 1.621839] system 00:02: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[ 1.621908] pnp 00:03: Plug and Play ACPI device, IDs PNP0303 (active)
[ 1.621927] pnp 00:04: Plug and Play ACPI device, IDs DLL062c PNP0f13 (active)
[ 1.774372] pnp 00:05: Plug and Play ACPI device, IDs PNP0401 (disabled)
[ 1.774526] system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 1.774529] system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
[ 1.774530] system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
[ 1.774532] system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
[ 1.774534] system 00:06: [mem 0xf8000000-0xfbffffff] has been reserved
[ 1.774536] system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 1.774538] system 00:06: [mem 0xfed90000-0xfed93fff] could not be reserved
[ 1.774539] system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
[ 1.774541] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
[ 1.774543] system 00:06: [mem 0xfee00000-0xfeefffff] could not be reserved
[ 1.774545] system 00:06: [mem 0xf7fe0000-0xf7feffff] has been reserved
[ 1.774547] system 00:06: [mem 0xf7ff0000-0xf7ffffff] has been reserved
[ 1.774549] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 1.774927] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 2.001167] pnp: PnP ACPI: found 8 devices
[ 2.007535] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 2.007540] pci 0000:00:1c.0: bridge window [mem 0xf7d00000-0xf7dfffff]
[ 2.007546] pci 0000:00:1c.3: PCI bridge to [bus 02]
[ 2.007549] pci 0000:00:1c.3: bridge window [mem 0xf7c00000-0xf7cfffff]
[ 2.007555] pci 0000:00:1c.4: PCI bridge to [bus 03]
[ 2.007564] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 2.007566] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 2.007567] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 2.007568] pci_bus 0000:00: resource 7 [mem 0xdf200000-0xfeafffff]
[ 2.007570] pci_bus 0000:01: resource 1 [mem 0xf7d00000-0xf7dfffff]
[ 2.007571] pci_bus 0000:02: resource 1 [mem 0xf7c00000-0xf7cfffff]
[ 2.007594] NET: Registered protocol family 2
[ 2.007754] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
[ 2.007894] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 2.008082] TCP: Hash tables configured (established 65536 bind 65536)
[ 2.008100] TCP: reno registered
[ 2.008108] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[ 2.008140] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
[ 2.008195] NET: Registered protocol family 1
[ 2.008208] pci 0000:00:02.0: Video device with shadowed ROM
[ 2.024532] PCI: CLS 64 bytes, default 64
[ 2.024577] Unpacking initramfs...
[ 2.341540] Freeing initrd memory: 22696K (ffff88003539c000 - ffff8800369c6000)
[ 2.341564] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 2.341567] software IO TLB [mem 0xc4c6d000-0xc8c6d000] (64MB) mapped at [ffff8800c4c6d000-ffff8800c8c6cfff]
[ 2.341712] RAPL PMU detected, hw unit 2^-14 Joules, API unit is 2^-32 Joules, 4 fixed counters 655360 ms ovfl timer
[ 2.341757] microcode: CPU0 sig=0x40651, pf=0x40, revision=0x1c
[ 2.341762] microcode: CPU1 sig=0x40651, pf=0x40, revision=0x1c
[ 2.341766] microcode: CPU2 sig=0x40651, pf=0x40, revision=0x1c
[ 2.341771] microcode: CPU3 sig=0x40651, pf=0x40, revision=0x1c
[ 2.341822] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 2.341843] Scanning for low memory corruption every 60 seconds
[ 2.342043] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 2.342061] Initialise system trusted keyring
[ 2.342314] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 2.343277] zpool: loaded
[ 2.343280] zbud: loaded
[ 2.343434] VFS: Disk quotas dquot_6.5.2
[ 2.343457] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 2.343557] msgmni has been set to 15200
[ 2.343599] Key type big_key registered
[ 2.343749] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 2.343779] io scheduler noop registered
[ 2.343781] io scheduler deadline registered
[ 2.343802] io scheduler cfq registered (default)
[ 2.343967] pcieport 0000:00:1c.0: irq 42 for MSI/MSI-X
[ 2.344096] pcieport 0000:00:1c.3: irq 43 for MSI/MSI-X
[ 2.344214] pcieport 0000:00:1c.4: irq 44 for MSI/MSI-X
[ 2.344282] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[ 2.344283] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[ 2.344286] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
[ 2.344296] pcieport 0000:00:1c.3: Signaling PME through PCIe PME interrupt
[ 2.344297] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
[ 2.344300] pcie_pme 0000:00:1c.3:pcie01: service driver pcie_pme loaded
[ 2.344310] pcieport 0000:00:1c.4: Signaling PME through PCIe PME interrupt
[ 2.344312] pcie_pme 0000:00:1c.4:pcie01: service driver pcie_pme loaded
[ 2.344325] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 2.344337] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 2.344362] vesafb: mode is 1920x1080x32, linelength=7680, pages=0
[ 2.344363] vesafb: scrolling: redraw
[ 2.344364] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 2.344382] vesafb: framebuffer at 0xe0000000, mapped to 0xffffc90004f80000, using 8128k, total 8128k
[ 2.492136] Console: switching to colour frame buffer device 240x67
[ 2.639261] fb0: VESA VGA frame buffer device
[ 2.639278] intel_idle: MWAIT substates: 0x11142120
[ 2.639279] intel_idle: v0.4 model 0x45
[ 2.639280] intel_idle: lapic_timer_reliable_states 0xffffffff
[ 2.639471] GHES: HEST is not enabled!
[ 2.639520] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 2.639854] Linux agpgart interface v0.103
[ 2.639890] rtc_cmos 00:01: RTC can wake from S4
[ 2.640003] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
[ 2.640027] rtc_cmos 00:01: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[ 2.640037] Intel P-state driver initializing.
[ 2.640149] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.640415] TCP: cubic registered
[ 2.640635] NET: Registered protocol family 10
[ 2.641104] NET: Registered protocol family 17
[ 2.641809] Loading compiled-in X.509 certificates
[ 2.641841] registered taskstats version 1
[ 2.642839] Magic number: 15:558:486
[ 2.642991] rtc_cmos 00:01: setting system clock to 2015-01-29 14:27:38 UTC (1422541658)
[ 2.643157] PM: Hibernation image not present or could not be loaded.
[ 2.645133] Freeing unused kernel memory: 1160K (ffffffff818e5000 - ffffffff81a07000)
[ 2.645137] Write protecting the kernel read-only data: 8192k
[ 2.649298] Freeing unused kernel memory: 652K (ffff88000155d000 - ffff880001600000)
[ 2.651088] Freeing unused kernel memory: 328K (ffff8800017ae000 - ffff880001800000)
[ 2.656604] random: systemd-tmpfile urandom read with 6 bits of entropy available
[ 2.656683] systemd-tmpfiles[60]: /dev/mapper created successfully.
[ 2.656691] systemd-tmpfiles[60]: /dev/fuse created successfully.
[ 2.656696] systemd-tmpfiles[60]: /dev/mapper/control created successfully.
[ 2.656700] systemd-tmpfiles[60]: /dev/loop-control created successfully.
[ 2.656704] systemd-tmpfiles[60]: /dev/cuse created successfully.
[ 2.656707] systemd-tmpfiles[60]: /dev/btrfs-control created successfully.
[ 2.657455] systemd-udevd[61]: starting version 218
[ 2.657462] systemd-udevd[61]: hwdb.bin does not exist, please run udevadm hwdb --update
[ 2.657510] systemd-udevd[61]: Load module index
[ 2.657562] systemd-udevd[61]: Created link configuration context.
[ 2.657568] systemd-udevd[61]: timestamp of '/usr/lib/udev/rules.d' changed
[ 2.657608] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/10-dm.rules
[ 2.657685] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/11-dm-initramfs.rules
[ 2.657695] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
[ 2.657733] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
[ 2.657763] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
[ 2.657871] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
[ 2.657981] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules
[ 2.657999] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
[ 2.658057] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules
[ 2.658080] systemd-udevd[61]: Reading rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
[ 2.658089] systemd-udevd[61]: rules contain 24576 bytes tokens (2048 * 12 bytes), 4834 bytes strings
[ 2.658091] systemd-udevd[61]: 641 strings (8077 bytes), 378 de-duplicated (3507 bytes), 264 trie nodes used
[ 2.658106] systemd-udevd[61]: chmod '/dev/fuse' 0666
[ 2.658188] systemd-udevd[61]: Unload module index
[ 2.658212] systemd-udevd[61]: Unloaded link configuration context.
[ 2.658262] systemd-udevd[62]: set children_max to 16
[ 2.660408] systemd-udevd[62]: seq 678 queued, 'add' 'module'
[ 2.660490] systemd-udevd[62]: seq 678 forked new worker [67]
[ 2.660575] systemd-udevd[67]: seq 678 running
[ 2.660618] systemd-udevd[67]: no db file to read /run/udev/data/+module:raid6_pq: No such file or directory
[ 2.660644] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 2.660651] systemd-udevd[67]: seq 678 processed with 0
[ 2.714860] raid6: sse2x1 9342 MB/s
[ 2.771561] raid6: sse2x2 11848 MB/s
[ 2.828260] raid6: sse2x4 13887 MB/s
[ 2.884943] raid6: avx2x1 18356 MB/s
[ 2.941655] raid6: avx2x2 21230 MB/s
[ 2.998344] raid6: avx2x4 24583 MB/s
[ 2.998345] raid6: using algorithm avx2x4 (24583 MB/s)
[ 2.998346] raid6: using avx2x2 recovery algorithm
[ 2.998547] xor: automatically using best checksumming function:
[ 2.998570] systemd-udevd[62]: seq 679 queued, 'add' 'module'
[ 2.998603] systemd-udevd[62]: passed 124 bytes to netlink monitor 0x7f4fb497f0d0
[ 2.998639] systemd-udevd[67]: seq 679 running
[ 2.998659] systemd-udevd[67]: no db file to read /run/udev/data/+module:xor: No such file or directory
[ 2.998678] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 2.998684] systemd-udevd[67]: seq 679 processed with 0
[ 3.031698] avx : 25444.800 MB/sec
[ 3.034144] systemd-udevd[62]: Validate module index
[ 3.034177] systemd-udevd[62]: Check if link configuration needs reloading.
[ 3.034204] systemd-udevd[62]: seq 680 queued, 'add' 'module'
[ 3.034228] systemd-udevd[62]: passed 126 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.034249] systemd-udevd[67]: seq 680 running
[ 3.034275] systemd-udevd[67]: no db file to read /run/udev/data/+module:btrfs: No such file or directory
[ 3.034299] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.034308] systemd-udevd[67]: seq 680 processed with 0
[ 3.034899] systemd-udevd[62]: seq 681 queued, 'add' 'module'
[ 3.034927] systemd-udevd[62]: passed 133 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.034945] systemd-udevd[67]: seq 681 running
[ 3.034964] systemd-udevd[67]: no db file to read /run/udev/data/+module:crc32c_intel: No such file or directory
[ 3.034979] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.034986] systemd-udevd[67]: seq 681 processed with 0
[ 3.035051] systemd-udevd[62]: seq 682 queued, 'add' 'module'
[ 3.035070] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.035087] systemd-udevd[67]: seq 682 running
[ 3.035101] systemd-udevd[67]: no db file to read /run/udev/data/+module:crc32c_generic: No such file or directory
[ 3.035113] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.035118] systemd-udevd[67]: seq 682 processed with 0
[ 3.035756] systemd-udevd[62]: seq 683 queued, 'add' 'slab'
[ 3.035776] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.035790] systemd-udevd[67]: seq 683 running
[ 3.035795] systemd-udevd[62]: seq 684 queued, 'add' 'slab'
[ 3.035810] systemd-udevd[67]: no db file to read /run/udev/data/+slab:btrfs_inode: No such file or directory
[ 3.035830] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.035834] systemd-udevd[67]: seq 683 processed with 0
[ 3.035903] systemd-udevd[62]: seq 684 forked new worker [75]
[ 3.035934] systemd-udevd[62]: seq 685 queued, 'add' 'slab'
[ 3.035948] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.035961] systemd-udevd[67]: seq 685 running
[ 3.035968] systemd-udevd[62]: seq 686 queued, 'add' 'slab'
[ 3.035981] systemd-udevd[67]: no db file to read /run/udev/data/+slab::at-0000144: No such file or directory
[ 3.035981] systemd-udevd[75]: seq 684 running
[ 3.035999] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.036004] systemd-udevd[67]: seq 685 processed with 0
[ 3.036010] systemd-udevd[75]: no db file to read /run/udev/data/+slab::at-0000176: No such file or directory
[ 3.036027] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
[ 3.036031] systemd-udevd[75]: seq 684 processed with 0
[ 3.036065] systemd-udevd[62]: seq 686 forked new worker [76]
[ 3.036107] systemd-udevd[62]: seq 687 queued, 'add' 'slab'
[ 3.036128] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.036146] systemd-udevd[62]: seq 688 queued, 'add' 'slab'
[ 3.036165] systemd-udevd[76]: seq 686 running
[ 3.036166] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.036180] systemd-udevd[75]: seq 688 running
[ 3.036182] systemd-udevd[62]: seq 689 queued, 'add' 'slab'
[ 3.036199] systemd-udevd[75]: no db file to read /run/udev/data/+slab::at-0000088: No such file or directory
[ 3.036206] systemd-udevd[76]: no db file to read /run/udev/data/+slab::at-0000064: No such file or directory
[ 3.036212] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
[ 3.036215] systemd-udevd[75]: seq 688 processed with 0
[ 3.036227] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
[ 3.036231] systemd-udevd[76]: seq 686 processed with 0
[ 3.036257] Btrfs loaded
[ 3.036289] systemd-udevd[62]: seq 689 forked new worker [77]
[ 3.036329] systemd-udevd[62]: seq 690 queued, 'add' 'slab'
[ 3.036351] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.036370] systemd-udevd[62]: seq 691 queued, 'add' 'slab'
[ 3.036378] systemd-udevd[77]: seq 689 running
[ 3.036390] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.036407] systemd-udevd[62]: seq 692 queued, 'add' 'slab'
[ 3.036413] systemd-udevd[77]: no db file to read /run/udev/data/+slab::at-0000280: No such file or directory
[ 3.036434] systemd-udevd[77]: passed -1 bytes to netlink monitor 0x7f4fb498a250
[ 3.036439] systemd-udevd[77]: seq 689 processed with 0
[ 3.036457] systemd-udevd[76]: seq 691 running
[ 3.036474] systemd-udevd[76]: no db file to read /run/udev/data/+slab::at-0000304: No such file or directory
[ 3.036493] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
[ 3.036498] systemd-udevd[76]: seq 691 processed with 0
[ 3.036513] systemd-udevd[62]: seq 692 forked new worker [78]
[ 3.036548] systemd-udevd[62]: seq 693 queued, 'add' 'slab'
[ 3.036563] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.036576] systemd-udevd[76]: seq 693 running
[ 3.036579] systemd-udevd[62]: seq 694 queued, 'add' 'slab'
[ 3.036596] systemd-udevd[76]: no db file to read /run/udev/data/+slab::at-0000096: No such file or directory
[ 3.036597] systemd-udevd[62]: passed 135 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.036615] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
[ 3.036616] systemd-udevd[62]: seq 695 queued, 'add' 'slab'
[ 3.036619] systemd-udevd[76]: seq 693 processed with 0
[ 3.036637] systemd-udevd[77]: seq 694 running
[ 3.036649] systemd-udevd[78]: seq 692 running
[ 3.036655] systemd-udevd[77]: no db file to read /run/udev/data/+slab::at-0000040: No such file or directory
[ 3.036672] systemd-udevd[77]: passed -1 bytes to netlink monitor 0x7f4fb498a250
[ 3.036676] systemd-udevd[77]: seq 694 processed with 0
[ 3.036678] systemd-udevd[78]: no db file to read /run/udev/data/+slab::at-0000160: No such file or directory
[ 3.036694] systemd-udevd[78]: passed -1 bytes to netlink monitor 0x7f4fb498f600
[ 3.036698] systemd-udevd[78]: seq 692 processed with 0
[ 3.036721] systemd-udevd[62]: seq 695 forked new worker [80]
[ 3.036773] systemd-udevd[62]: seq 696 queued, 'add' 'misc'
[ 3.036801] systemd-udevd[80]: seq 695 running
[ 3.036826] systemd-udevd[80]: no db file to read /run/udev/data/+slab::at-0000080: No such file or directory
[ 3.036832] systemd-udevd[62]: passed 192 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.036843] systemd-udevd[80]: passed -1 bytes to netlink monitor 0x7f4fb49913d0
[ 3.036848] systemd-udevd[80]: seq 695 processed with 0
[ 3.036859] systemd-udevd[76]: seq 696 running
[ 3.036904] systemd-udevd[76]: no db file to read /run/udev/data/c10:234: No such file or directory
[ 3.036916] systemd-udevd[76]: handling device node '/dev/btrfs-control', devnum=c10:234, mode=0600, uid=0, gid=0
[ 3.036922] systemd-udevd[76]: preserve permissions /dev/btrfs-control, 020600, uid=0, gid=0
[ 3.036930] systemd-udevd[76]: creating symlink '/dev/char/10:234' to '../btrfs-control'
[ 3.036959] systemd-udevd[76]: created empty file '/run/udev/data/c10:234' for '/devices/virtual/misc/btrfs-control'
[ 3.036987] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
[ 3.036992] systemd-udevd[76]: seq 696 processed with 0
[ 3.037009] systemd-udevd[67]: seq 687 running
[ 3.037027] systemd-udevd[67]: no db file to read /run/udev/data/+slab::at-0000152: No such file or directory
[ 3.037044] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.037048] systemd-udevd[67]: seq 687 processed with 0
[ 3.037063] systemd-udevd[75]: seq 690 running
[ 3.037079] systemd-udevd[75]: no db file to read /run/udev/data/+slab::at-0000424: No such file or directory
[ 3.037093] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
[ 3.037097] systemd-udevd[75]: seq 690 processed with 0
[ 3.037372] udevadm[79]: calling: trigger
[ 3.037397] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/vt'
[ 3.037403] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/xor'
[ 3.037408] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/8250'
[ 3.037412] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/tcp_cubic'
[ 3.037417] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/acpi'
[ 3.037421] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/ipv6'
[ 3.037425] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/cpuidle'
[ 3.037428] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/rcutree'
[ 3.037432] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/block'
[ 3.037436] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/btrfs'
[ 3.037440] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/sysrq'
[ 3.037444] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/zswap'
[ 3.037448] udevadm[79]: device 0x7fbf103cd230 has devpath '/module/crc32c_generic'
[ 3.037453] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/firmware_class'
[ 3.037457] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/workqueue'
[ 3.037461] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/crc32c_intel'
[ 3.037465] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/spurious'
[ 3.037469] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/raid6_pq'
[ 3.037473] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/configfs'
[ 3.037477] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/netpoll'
[ 3.037481] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/pci_slot'
[ 3.037486] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/kernel'
[ 3.037490] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/acpiphp'
[ 3.037494] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/pciehp'
[ 3.037498] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/printk'
[ 3.037502] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/pstore'
[ 3.037507] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/dynamic_debug'
[ 3.037511] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/xz_dec'
[ 3.037515] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/pcie_aspm'
[ 3.037522] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/rcupdate'
[ 3.037526] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/intel_idle'
[ 3.037530] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/keyboard'
[ 3.037534] udevadm[79]: device 0x7fbf103cd500 has devpath '/module/pci_hotplug'
[ 3.037548] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/cpu'
[ 3.037552] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci'
[ 3.037556] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pnp'
[ 3.037559] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/spi'
[ 3.037563] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/xen'
[ 3.037567] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/acpi'
[ 3.037571] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/node'
[ 3.037575] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/clocksource'
[ 3.037579] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/machinecheck'
[ 3.037583] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/event_source'
[ 3.037587] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/workqueue'
[ 3.037591] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/container'
[ 3.037595] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/memory'
[ 3.037599] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci_express'
[ 3.037603] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform'
[ 3.037607] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/clockevents'
[ 3.037611] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/xen-backend'
[ 3.037628] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci/drivers/xen-platform-pci'
[ 3.037633] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci/drivers/pcieport'
[ 3.037638] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci/drivers/ioapic'
[ 3.037642] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci/drivers/serial'
[ 3.037653] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pnp/drivers/rtc_cmos'
[ 3.037658] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pnp/drivers/serial'
[ 3.037662] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pnp/drivers/system'
[ 3.037675] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/acpi/drivers/ec'
[ 3.037680] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/acpi/drivers/hpet'
[ 3.037685] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/acpi/drivers/intel_smart_connect'
[ 3.037691] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/acpi/drivers/hardware_error_device'
[ 3.037716] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci_express/drivers/aer'
[ 3.037721] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci_express/drivers/pcie_pme'
[ 3.037726] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/pci_express/drivers/pciehp'
[ 3.037735] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/alarmtimer'
[ 3.037739] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/efi-framebuffer'
[ 3.037744] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/vesa-framebuffer'
[ 3.037748] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/serial8250'
[ 3.037753] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/syscon'
[ 3.037760] udevadm[79]: device 0x7fbf103cd500 has devpath '/bus/platform/drivers/clk-lpt'
[ 3.037842] systemd-udevd[62]: seq 697 queued, 'add' 'bus'
[ 3.037860] systemd-udevd[62]: passed 119 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.037890] systemd-udevd[67]: seq 697 running
[ 3.037891] systemd-udevd[62]: seq 698 queued, 'add' 'drivers'
[ 3.037906] systemd-udevd[62]: seq 699 queued, 'add' 'drivers'
[ 3.037909] systemd-udevd[67]: no db file to read /run/udev/data/+bus:acpi: No such file or directory
[ 3.037921] systemd-udevd[62]: seq 700 queued, 'add' 'drivers'
[ 3.037923] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.037925] systemd-udevd[67]: seq 697 processed with 0
[ 3.037941] systemd-udevd[62]: seq 701 queued, 'add' 'drivers'
[ 3.037963] systemd-udevd[62]: passed 134 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.037985] systemd-udevd[62]: passed 153 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.037988] systemd-udevd[67]: seq 698 running
[ 3.037999] systemd-udevd[62]: passed 136 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038001] systemd-udevd[67]: no db file to read /run/udev/data/+drivers:ec: No such file or directory
[ 3.038011] systemd-udevd[62]: passed 151 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038013] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.038015] systemd-udevd[67]: seq 698 processed with 0
[ 3.038031] systemd-udevd[62]: seq 702 queued, 'add' 'bus'
[ 3.038053] systemd-udevd[62]: passed 126 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038076] systemd-udevd[67]: seq 702 running
[ 3.038079] systemd-udevd[62]: seq 703 queued, 'add' 'bus'
[ 3.038088] systemd-udevd[67]: no db file to read /run/udev/data/+bus:clockevents: No such file or directory
[ 3.038094] systemd-udevd[62]: passed 126 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038102] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.038106] systemd-udevd[67]: seq 702 processed with 0
[ 3.038111] systemd-udevd[62]: seq 704 queued, 'add' 'bus'
[ 3.038113] systemd-udevd[78]: seq 703 running
[ 3.038126] systemd-udevd[62]: passed 124 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038134] systemd-udevd[78]: no db file to read /run/udev/data/+bus:clocksource: No such file or directory
[ 3.038143] systemd-udevd[80]: seq 704 running
[ 3.038145] systemd-udevd[62]: seq 705 queued, 'add' 'bus'
[ 3.038152] systemd-udevd[78]: passed -1 bytes to netlink monitor 0x7f4fb498f600
[ 3.038156] systemd-udevd[62]: passed 118 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038158] systemd-udevd[78]: seq 703 processed with 0
[ 3.038163] systemd-udevd[80]: no db file to read /run/udev/data/+bus:container: No such file or directory
[ 3.038175] systemd-udevd[62]: seq 706 queued, 'add' 'bus'
[ 3.038177] systemd-udevd[80]: passed -1 bytes to netlink monitor 0x7f4fb49913d0
[ 3.038179] systemd-udevd[80]: seq 704 processed with 0
[ 3.038188] systemd-udevd[62]: passed 127 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038192] systemd-udevd[67]: seq 705 running
[ 3.038201] systemd-udevd[78]: seq 706 running
[ 3.038206] systemd-udevd[62]: seq 707 queued, 'add' 'bus'
[ 3.038209] systemd-udevd[67]: no db file to read /run/udev/data/+bus:cpu: No such file or directory
[ 3.038218] systemd-udevd[62]: passed 127 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038224] systemd-udevd[78]: no db file to read /run/udev/data/+bus:event_source: No such file or directory
[ 3.038225] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.038228] systemd-udevd[67]: seq 705 processed with 0
[ 3.038234] systemd-udevd[62]: seq 708 queued, 'add' 'bus'
[ 3.038243] systemd-udevd[80]: seq 707 running
[ 3.038243] systemd-udevd[78]: passed -1 bytes to netlink monitor 0x7f4fb498f600
[ 3.038246] systemd-udevd[78]: seq 706 processed with 0
[ 3.038254] systemd-udevd[76]: seq 700 running
[ 3.038261] systemd-udevd[80]: no db file to read /run/udev/data/+bus:machinecheck: No such file or directory
[ 3.038272] systemd-udevd[80]: passed -1 bytes to netlink monitor 0x7f4fb49913d0
[ 3.038275] systemd-udevd[80]: seq 707 processed with 0
[ 3.038276] systemd-udevd[76]: no db file to read /run/udev/data/+drivers:hpet: No such file or directory
[ 3.038306] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
[ 3.038310] systemd-udevd[76]: seq 700 processed with 0
[ 3.038325] systemd-udevd[75]: seq 699 running
[ 3.038343] systemd-udevd[75]: no db file to read /run/udev/data/+drivers:hardware_error_device: No such file or directory
[ 3.038360] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
[ 3.038364] systemd-udevd[75]: seq 699 processed with 0
[ 3.038405] systemd-udevd[77]: seq 701 running
[ 3.038419] systemd-udevd[77]: no db file to read /run/udev/data/+drivers:intel_smart_connect: No such file or directory
[ 3.038429] systemd-udevd[77]: passed -1 bytes to netlink monitor 0x7f4fb498a250
[ 3.038432] systemd-udevd[77]: seq 701 processed with 0
[ 3.038531] systemd-udevd[62]: seq 708 forked new worker [81]
[ 3.038591] systemd-udevd[62]: seq 709 queued, 'add' 'bus'
[ 3.038612] systemd-udevd[62]: passed 119 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038623] systemd-udevd[81]: seq 708 running
[ 3.038627] systemd-udevd[67]: seq 709 running
[ 3.038631] systemd-udevd[62]: seq 710 queued, 'add' 'bus'
[ 3.038640] systemd-udevd[62]: passed 118 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038648] systemd-udevd[67]: no db file to read /run/udev/data/+bus:node: No such file or directory
[ 3.038653] systemd-udevd[75]: seq 710 running
[ 3.038655] systemd-udevd[81]: no db file to read /run/udev/data/+bus:memory: No such file or directory
[ 3.038657] systemd-udevd[62]: seq 711 queued, 'add' 'drivers'
[ 3.038666] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.038671] systemd-udevd[62]: seq 712 queued, 'add' 'drivers'
[ 3.038671] systemd-udevd[67]: seq 709 processed with 0
[ 3.038676] systemd-udevd[81]: passed -1 bytes to netlink monitor 0x7f4fb49945b0
[ 3.038678] systemd-udevd[75]: no db file to read /run/udev/data/+bus:pci: No such file or directory
[ 3.038682] systemd-udevd[81]: seq 708 processed with 0
[ 3.038693] systemd-udevd[62]: seq 713 queued, 'add' 'drivers'
[ 3.038695] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
[ 3.038700] systemd-udevd[75]: seq 710 processed with 0
[ 3.038710] systemd-udevd[62]: seq 714 queued, 'add' 'drivers'
[ 3.038721] systemd-udevd[62]: passed 137 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038732] systemd-udevd[62]: passed 139 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038734] systemd-udevd[67]: seq 711 running
[ 3.038753] systemd-udevd[76]: seq 713 running
[ 3.038753] systemd-udevd[67]: no db file to read /run/udev/data/+drivers:ioapic: No such file or directory
[ 3.038779] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.038782] systemd-udevd[76]: no db file to read /run/udev/data/+drivers:serial: No such file or directory
[ 3.038784] systemd-udevd[67]: seq 711 processed with 0
[ 3.038797] systemd-udevd[75]: seq 712 running
[ 3.038799] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
[ 3.038803] systemd-udevd[76]: seq 713 processed with 0
[ 3.038810] systemd-udevd[62]: passed 137 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038815] systemd-udevd[75]: no db file to read /run/udev/data/+drivers:pcieport: No such file or directory
[ 3.038823] systemd-udevd[62]: passed 147 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038841] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
[ 3.038845] systemd-udevd[75]: seq 712 processed with 0
[ 3.038849] systemd-udevd[77]: seq 714 running
[ 3.038856] systemd-udevd[62]: seq 715 queued, 'add' 'bus'
[ 3.038864] systemd-udevd[77]: no db file to read /run/udev/data/+drivers:xen-platform-pci: No such file or directory
[ 3.038871] systemd-udevd[62]: passed 126 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038876] systemd-udevd[77]: passed -1 bytes to netlink monitor 0x7f4fb498a250
[ 3.038878] systemd-udevd[77]: seq 714 processed with 0
[ 3.038891] systemd-udevd[62]: seq 716 queued, 'add' 'drivers'
[ 3.038915] systemd-udevd[62]: seq 717 queued, 'add' 'drivers'
[ 3.038928] systemd-udevd[62]: seq 718 queued, 'add' 'drivers'
[ 3.038941] systemd-udevd[62]: seq 719 queued, 'add' 'bus'
[ 3.038953] systemd-udevd[62]: passed 123 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.038976] systemd-udevd[75]: seq 719 running
[ 3.038977] systemd-udevd[62]: seq 720 queued, 'add' 'drivers'
[ 3.038990] systemd-udevd[75]: no db file to read /run/udev/data/+bus:platform: No such file or directory
[ 3.038991] systemd-udevd[62]: seq 721 queued, 'add' 'drivers'
[ 3.039001] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
[ 3.039004] systemd-udevd[75]: seq 719 processed with 0
[ 3.039005] systemd-udevd[62]: seq 722 queued, 'add' 'drivers'
[ 3.039034] systemd-udevd[62]: seq 723 queued, 'add' 'drivers'
[ 3.039046] systemd-udevd[62]: passed 146 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.039070] systemd-udevd[75]: seq 720 running
[ 3.039078] systemd-udevd[76]: seq 721 running
[ 3.039081] systemd-udevd[75]: no db file to read /run/udev/data/+drivers:alarmtimer: No such file or directory
[ 3.039092] systemd-udevd[75]: passed -1 bytes to netlink monitor 0x7f4fb49879e0
[ 3.039094] systemd-udevd[75]: seq 720 processed with 0
[ 3.039101] systemd-udevd[76]: no db file to read /run/udev/data/+drivers:clk-lpt: No such file or directory
[ 3.039128] systemd-udevd[76]: passed -1 bytes to netlink monitor 0x7f4fb49883b0
[ 3.039133] systemd-udevd[76]: seq 721 processed with 0
[ 3.039146] systemd-udevd[67]: seq 715 running
[ 3.039162] systemd-udevd[67]: no db file to read /run/udev/data/+bus:pci_express: No such file or directory
[ 3.039177] systemd-udevd[67]: passed -1 bytes to netlink monitor 0x7f4fb498c310
[ 3.039181] systemd-udevd[67]: seq 715 processed with 0
[ 3.039188] systemd-udevd[62]: passed 143 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.039200] systemd-udevd[62]: passed 151 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.039221] systemd-udevd[62]: passed 146 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.039224] systemd-udevd[77]: seq 722 running
[ 3.039235] systemd-udevd[78]: seq 723 running
[ 3.039244] systemd-udevd[77]: no db file to read /run/udev/data/+drivers:efi-framebuffer: No such file or directory
[ 3.039244] systemd-udevd[62]: seq 724 queued, 'add' 'drivers'
[ 3.039255] systemd-udevd[78]: no db file to read /run/udev/data/+drivers:serial8250: No such file or directory
[ 3.039257] systemd-udevd[62]: passed 142 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.039263] systemd-udevd[77]: passed -1 bytes to netlink monitor 0x7f4fb498a250
[ 3.039267] systemd-udevd[77]: seq 722 processed with 0
[ 3.039269] systemd-udevd[62]: passed 147 bytes to netlink monitor 0x7f4fb497f0d0
[ 3.039273] systemd-udevd[78]: passed -1 bytes to netlink monitor 0x7f4fb498f600
[ 3.039277] systemd-udevd[78]: seq 723 processed with 0
[ 3.039284] systemd-udevd[75]: seq 717 running
[ 3.039288] systemd-udevd[76]: seq 718 running
[ 3.039298] systemd-udevd[75]: no db file to read /run/udev/data/+drivers:pcie_pme: No such file or directory
[ 3.039306] systemd-udevd[76]: no db file to read /run/udev/data/+drivers:pciehp: No such file or directory
[ 3.039309] sysGuys, I think I've found the strange thing.
First, in the recovery shell, when I type "lvm lvscan", it prints:
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
and then it says that all four my logical volumes root,boot,home and var are inactive.
So I tried to set them up manually, with "lvm vgchange -a y", and guess what happened: I was able to boot!
I still haven't managed to understand the real causes of this problem, but basically it seems that I have the same problem explained here: https://bbs.archlinux.org/viewtopic.php?id=184340.
The only difference is that there the OP says to have solved the problem with an upgrade to Linux 3.15.7, while it appeared to me with the upgrade to 3.18.3, and as I said it doesn't go away neither with a downgrade nor with another upgrade to version 3.18.4
Last edited by rdm (2015-01-29 21:55:44) -
T400s Linux/Windows dual boot with Linux from Esata Flash Drive
This project is about a dual boot Windows/Linux system without using the normal dual boot changes in the bootloader of the windows hard drive. When I started this I found bits and pieces of information on the web but no complete description so I wrote this post.
I have done a dual boot system on my previous Thinkpad where I had partitioned the hard drive between Linux and windows. For this project I wanted to leave the windows hard drive absolutely intact and unaltered, and boot Linux from a flash drive in the esata port on the back of the T400s. Obviously this uses the F12 boot list function key to boot from the flash. The advantage of this is that Windows is totally unaltered and when I need Linux, I plug in the esata flash drive, hit F12 during the boot cycle and select booting from the esata flash drive. The reason for Esata rather than USB is simply speed. I have a nice fast Linux installation.
I used the OCZ esata flash drive but suspect any of the alternatives will work. It did not need the accessory usb cable because the Thinkpad powered the esata flash directly.
To boot from the esata drive I had to make the following changes in the bios
I left the esata flash plugged in as I went into the bios
Bios>config>Serial ATA and changed the Sata controller mode option to compatibility
Restart and back into the Bios
Bios>startup>boot - in my case the esata flash drive showed up as ATA HDD2 and was excluded from the boot order so I had to un-exclude it and move it to the point in the boot order that I wanted.
Next I downloaded a linux installation iso and put it on a CD - in my case opensuse. Then booted from the CD
From now on this instructions are specific to opensuse and yast but can be generalized to whatever Linux is being used.
In my case yast came up with a good set of suggestions for automatically partitioning the flash drive but then crashed during the partitioning itself. So I rebooted and specified the partitions manually.
A fat32 partition left as a partition which both windows and Linux could see (in my case about 20% of the drive) (/dev/sdb1)
An extended partition with the remainder of the drive (/dev/sdb2) which contains the following logical partitions
A linux Swap partition of 2GB (/dev/sdb5)
A linux /home partition –the remainder of the drive (/dev/sdb6)
A linux /root partition of 8GB (/dev/sdb7)
Yast automatically suggested mount points of C,D,E for the windows partitions. Unfortunately because of the way the Thinkpad hard drive was laid out Yast had C assigned the ThinkPad Service partition and D assigned to the SW_Preload (or main windows partition). However there was an edit function that allows for the reversal of those mount points so that the windows C drive is mounted in Linux as Windows/C thereby avoiding confusion. I had already backed up and removed the Thinkpad factory install data so I did not have to deal with that. Yast suggested Windows/E for the mount point of the FAT32 partition on the flash drive, which I accepted.
The yast install configurator made all this manual selection easy, and after the manual configuration the partitioning worked perfectly.
Next step was Linux user configuration which went fine
Next was booting.
In the section management tab
delete the windows 1 and 2 options (since we are not dual booting directly)
In the boot loader installation tab
uncheck boot from mbr ( this stops the install from installing Grub and dual boot on the windows c drive
check boot from root partition (this installs grub and all associated files in the Linux root partition (/dev/sdb6)
I believe that the correct procedure at this point is to click Boot Loader installation details which will bring up the Grub device map. In the device map there will be a line for the fixed hard drive (aka the windows drive) and a line for the esata flash drive. When the installer started up these were in hard drive and esata drive order. However when we boot directly from the flash the esata drive will be grub drive hd0 and the fixed hard drive will be grub hd1. The device map order needs to be changed to reflect this ie the esata drive should be first not second.
I did not do this and ended up initially doing Grub command line editing to boot and later manually editing the grub files using information I had previously learned the hard way and through google.
At this point let the installer go ahead and install Linux. After doing this it should come back and tell you to reboot. Do not do it yet because we need to install the MBR into the flash drive.
I suspect that there is a way of doing this in Yast running from the Live CD but it was not obvious to me so I used the manual method that I have used before.
Open a root terminal
Mount /dev/sdb6 to /mnt/sdb6 (my linux root)
Touch /mnt/sdb6/boot/grub/flag
The purpose of this is when we go looking later at the grub command prompt we need an easy to find unique file
Start grub and do the following
#grub
grub> find /boot/grub/flag
(hd1,5) -- the result of the find in my example
grub> root (hd1,5) -- using the result of the find in my example
grub> setup (hd1) -- install mbr -- my example parameters - if you get this wrong you will trash some other drive!!!
hopefully grub announces success
grub> quit
Reboot and select the flash drive. In my case I still had the grub devicemap wrong and had to edit the grub commands during boot to tell grub how to find the correct partition and then edit them again after booting
Typical linux install issues that we all always seem to have and can be solved with a little (or a lot of) google research.
As I said at the beginning I now have an untouched windows installation and a nice fast Linux installation. I hope that this will be of some use to someone.Hi chrissh
i tried this exact procedure... on the exact same notebook (T400s). However, as soon as I set the
Bios>config>Serial ATA to "compatibility", I cannot use my default Windows installation! I immediately get the "blue screen of death".
I doubt I did anything differently since this is the first step of your procedure and my laptop is brand new!
any idea? -
[SOLVED] Dual-boot Arch/Windows - 2 hard drives
Hi Everyone
I've just installed Arch and I'm having a bit of a problem dual-booting between Arch and Windows XP, which are each on a seperate Hard drive.
I've done this successfully before with Mepis Linux and Windows XP, but for some reason it's not working this time.
The difference is that I've recently purchased a new computer and both Windows and Arch are on SATA drives whereas last time they were both on IDE drives. Also I'm not sure whether or not to enable SATA AHCI mode in the BIOS (apparently it doesn't work with XP anyways), or SATA port 0-3 Native mode. Although I've tried all possible combinations and it doesn't seem to work at all.
Here is my menu.lst file:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/0df05d3b-537c-4576-ad36-1f90a6b01ec0 ro vga=773
initrd /boot/kernel26.img
# (1) Windows
title Windows
rootnoverify (hd1,0)
makeactive
chainloader +1
When I boot into Arch from Grub it works fine, but when I try to boot into Windows from Grub, I get this:
rootnoverify (hd1,0)
makeactive
chainloader +1
and then nothing....No error message or anything. It just hangs. Does anyone have any ideas as to what's happening? Thanks in advance.
edit: It seems I solved the problem by adding these lines to the menu.lst file:
map (hd0) (hd1)
map (hd1) (hd0)
root (hd1,0)
I can now boot into either Arch or Windows from the Grub menu
Last edited by axle (2008-09-30 02:35:54)This is a question that can very easily be answered by doing a simple google serach. Google is your friend. I suggest you start there and come back if you run into issues.
-
[SOLVED] Cloning boot and var partitions to a new drive for booting
Ok first of all here's my setup:
fakeraid (dmraid) / and home on an OCZ Revodrive
boot with GRUB on a flash drive (since fakeraid doesn't support grub)
var and downloads/media folder on a 500GB WD Caviar drive
When I originally installed Arch I had the Caviar drive in my home server in a RAID5 array, so that's why I opted to install boot and grub on a flash drive simply for booting. Now that I have the drive in my desktop I've cloned the flash drive's partitions and MBR using dd:
#dd if=/dev/sde of=~/MBR.img bs=512 count=1
#dd if=/dev/sde1 of=~/boot.img
#dd if=/dev/sdc1 of=~/var.img
I then backed up my downloads/media partition, then removed the partition table, then used dd to put the img files on the Caviar drive.
#dd if=~/MBR.img of=/dev/sdc bs=512 count=1
#dd of=~/boot.img of=/dev/sdc1
#dd of=~/var.img of=/dev/sdc2
I also created labels for the filesystems and put those in fstab.
I'm able to mount both partitions, however I can't boot from the drive. I get a 'grub hard disk error' (no error number) when I put it as my first drive in the BIOS.
I can still use the flash drive as the first hard drive in the BIOS and boot from it, then it mounts the dmraid root partition and boots successfully. It is also able to mount the var and boot partitions in fstab.
Basically the only problem is that the MBR is somehow wrong. I then tried booting back into an Arch live USB and installing GRUB from the prompt:
grub
grub>setup (hd4,0) (in this case the Caviar drive's boot partition was /dev/sde1
So essentially what I'm asking is how GRUB handles the MBR. Is it specific to the partition table of the drive in which it resides when it's originally installed? For instance, since I had an 8GB flash drive with 2 partitions when I installed GRUB, is the backed up MBR no good for a 500GB drive with 3 partitions?
I have everything backed up so I can start with a fresh /boot and /var if need be....I'm just not sure where to start.
Thanks in advance.
Last edited by DarksideEE7 (2011-02-13 23:25:31)Sorry, I forgot to mention that I tried to install GRUB from the GRUB shell in a live Arch USB. It failed on a few non-critical parts, and succeeded on the last part. I'm going to try again shortly, possibly I did something wrong. GRUB is able to find the stage files using:
#grub
grub>find /grub/stage1
grub> find /grub/stage1
(hd0,0)
(hd5,0)
grub>
(hd0,0) is the desired boot drive, while (hd5,0) is the current bootable flash drive with /boot and GRUB installed.
Here is the output of fdisk -l:
WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sde1 1 3907029167 1953514583+ ee GPT
Disk /dev/sdb: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xedb72db9
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 206847 102400 7 HPFS/NTFS
/dev/sdb2 206848 117227519 58510336 7 HPFS/NTFS
Disk /dev/sdd: 40.0 GB, 40018599936 bytes
255 heads, 63 sectors/track, 4865 cylinders, total 78161328 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/sdd doesn't contain a valid partition table
Disk /dev/sdc: 40.0 GB, 40018599936 bytes
32 heads, 32 sectors/track, 76329 cylinders, total 78161328 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb8372fcd
Device Boot Start End Blocks Id System
/dev/sdc1 32 21484543 10742256 83 Linux
/dev/sdc2 21484544 156317695 67416576 83 Linux
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8497e059
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 83 Linux
/dev/sda2 206848 42149887 20971520 83 Linux
/dev/sda3 42149888 976773167 467311640 83 Linux
Disk /dev/dm-0: 80.0 GB, 80035053568 bytes
32 heads, 32 sectors/track, 152654 cylinders, total 156318464 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0xb8372fcd
Device Boot Start End Blocks Id System
/dev/dm-0p1 32 21484543 10742256 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/dm-0p2 21484544 156317695 67416576 83 Linux
Disk /dev/dm-1: 11.0 GB, 11000070144 bytes
255 heads, 63 sectors/track, 1337 cylinders, total 21484512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Alignment offset: 49152 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 69.0 GB, 69034573824 bytes
255 heads, 63 sectors/track, 8392 cylinders, total 134833152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/sdf: 8086 MB, 8086618112 bytes
249 heads, 62 sectors/track, 1023 cylinders, total 15794176 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8497e059
Device Boot Start End Blocks Id System
/dev/sdf1 * 62 200693 100316 83 Linux
/dev/sdf2 200694 15794175 7796741 83 Linux
I'm using dmraid, so just to be clear I've configured the raid using:
#modprobe dm_mod
#dmraid -ay
Then I saw the array stored in /dev/mapper/silXXXXX. I then created partitions for /boot, /, and home. At that time I was hoping to get GRUB working with the AUR package grub2-dmraid. I wasn't able to get it working for some time, so I just went ahead and installed boot and GRUB to a separate USB flash drive.
Here is the output of df -h:
Filesystem Size Used Avail Use% Mounted on
udev 10M 268K 9.8M 3% /dev
/dev/mapper/sil_bgbgdjaddicbp1
11G 5.3G 4.3G 56% /
shm 6.0G 584K 6.0G 1% /dev/shm
/dev/mapper/sil_bgbgdjaddicbp2
64G 38G 23G 63% /home
/dev/sda1 95M 16M 75M 18% /boot
/dev/sda2 19G 142M 19G 1% /var
/dev/sda3 439G 148G 269G 36% /home/l33/Torrents
none 1000M 132K 1000M 1% /tmp
shm 6.0G 584K 6.0G 1% /dev/shm
/dev/sde1 1.8T 1.1T 665G 62% /mnt/Green
and cat /etc/mtab
proc /proc proc rw,nosuid,nodev,noexec,relatime
sys /sys sysfs rw,nosuid,nodev,noexec,relatime
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=1022975,mode=755
/dev/mapper/sil_bgbgdjaddicbp1 / ext4 rw,noatime,barrier=1,stripe=32,data=ordered
devpts /dev/pts devpts rw 0 0
shm /dev/shm tmpfs rw,nosuid,nodev 0 0
/dev/mapper/sil_bgbgdjaddicbp2 /home ext4 rw,noatime 0 0
/dev/sda1 /boot ext2 rw 0 0
/dev/sda2 /var reiserfs rw,noatime 0 0
/dev/sda3 /home/l33/Torrents ext4 rw,noatime 0 0
none /tmp tmpfs rw,nosuid,nodev,noatime,size=1000M,mode=1777 0 0
shm /dev/shm tmpfs rw,nosuid,nodev,size=6G 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
nfsd /proc/fs/nfsd nfsd rw,noexec,nosuid,nodev 0 0
/dev/sde1 /mnt/Green ext4 rw 0 0
Also I don't have a /proc/mdstat. That's only for mdadm RAID setups, right? It's been quite some time since I've used mdadm so I can't remember.
EDIT:
So I booted into a live Arch USB and entered the grub shell. I ran:
#grub
grub> root (hd3,0)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd3)
Checking if "/boot/grub/stage1" exists.....no
Checking if "/grub/stage1 exists.......yes
Checking if "/grub/stage2 exists.......yes
Checking if "/grub/e2fs_stage1_5 exists....yes
Running "embed /grub/e2fs_stage1_5 (hd3)".....25 sectors are embedded.
succeeded
Running "install /grub/stage1 (hd3) (hd3))1+25 p (hd3,0)/grub/stage2 /grub/menu.lst".......succeeded
Done.
Last time I recall more errors than this, then it reporting that one was a non-critical error, so I think the problem may be solved. More to come.
Last edited by DarksideEE7 (2011-02-13 23:18:44)
Maybe you are looking for
-
MDX - Returning the value of a measure at a particular level
I've got the following query which runs against the AdventureWorks 2008R2. It returns the [Internet Sales Amount] for the cities to which the following members belong [Customer].[Customer Geography].[Customer].&[18702] and [Customer].[Customer Geogra
-
When I try disabling colour management in the printer driver, it keeps turning back on
I'm using Lightroom v2.4 and a Canon Pixma Pro 9500 printer with the latest driver. I've just tried to print from Lightroom for the first time since moving to this latest version of Lightroom and when I go into print setup and turn off colour manage
-
Hi , We have some AP posting requirement where we need to Show correct value of VAT in both local and group currency, and then Use the VAT amount in local currency to calculate the amount in group currency (using accounting rate) and Post an excha
-
The cursor won't work in Firefox quite often without my restarting the program
When I am on Firefox quite often the cursor won't highlight anything or allow me to enter any text. I have to quit the program and restart it. Any suggestions? == This happened == A few times a week == 2 weeks ago
-
Can't install new release - Error 2753 Ref pxsetup.exe ?
I ran into problems trying to uninstall Lightroom Beta. In the end, I did a manual delete, followed up by a "regedit" search for anything 'Lightroom' had left behind in the registry. Then I swept the machine using Ccleaner (great free utility at www.