Arch 64 or 32 bit?

I have installed arch before on my system about a month ago, but it was kinda slow and sluggish, even though i had a very minimal setup with XFCE.  So I switched back to ubuntu.  However, Ubuntu is giving me a lot of problems right now, and i'm considering going back to arch.  Since I think that the fact that I used a 64 bit arch isntall at first may have caused some compatibility issues, what would you recommend for my system? 
Laptop Specs:
Intel Core2Duo T5250
Intel GMA 965
4GB RAM
Last edited by aznsmartj0ck (2010-08-03 20:18:47)

qchapter wrote:
If you use 32bit only apps like Skype or the Adobe Flash Plugin, the decision is easy: 32bit.  By the way this question has been discussed ad nauseum, please search the forums and the wiki before posting:
https://bbs.archlinux.org/viewtopic.php?pid=502393
http://wiki.archlinux.org/index.php/Arch64_FAQ
This is very wrong. First of all, Skype has a version for 64-bit in the AUR. While it is technically a 32-bit binary, it works. The adobe flash plugin has the last released version in the AUR(although i wouldn't suggest using that for security reasons), or you can use nspluginwrapper at the cost of a little bit of performance, but it also works. You can also use a free version of flash, like lightspark player or gnash. Or you could just use a chroot to install a bundled 32-bit system in your 64-bit version.(Which is what I use.)
But I do agree that you should search the forums and wiki.

Similar Messages

  • [SOLVED] Arch Linux on (32-bit?) ThinkPads?

    Hi all,
    I'm a newbie, looking at getting a ThinkPad netbook, which I hope to run Arch on. What am I looking for?
    # battery life greater than 4 hours
    # price less than $300 USD
    # trackpoint
    # carrying out tasks associated with being a student - browsing email/internet/pdfs, compiling LaTeX documents, maybe running Mathematica or Maple.
    # not concerned about storage, watching videos or playing games.
    # tablet may be nice, but not a major concern.
    I initially considered an X30/X31/X40/X41, but these seem to have 32-bit processors. So I thought Arch would not work. But then I see various Arch Wikis on installing on an X31/X41 etc. Could someone please explain why Arch can be installed on these 32-bit machines, and any considerations I should take into account in doing so?
    As an aside, I then went looking at the X60/X61 options, however these seem to have very bad over-heating problems, so I then considered X200 models. However these are very pricey, and seem like overkill if Arch will run on an X41 for example. Any other recommendations would be much appreciated!
    Many regards,
    Ianhoolihan
    Last edited by ianhoolihan (2011-08-21 10:27:45)

    Arch works just fine on 32-bit if it's a 686 processor. Installing Arch on an nvidia Tegra tablet may not work (try http://archlinuxarm.org/ instead), but anything standard like an Intel or AMD processor is OK.
    Arch will run on even a decade old Pentium III so you don't need a powerful processor, it only depends what apps you want to install.
    I have no idea about power management / heat issues.
    Last edited by karol (2011-08-20 22:48:03)

  • Gnu Arch (CVS replacement) + ABC (Bit Torrent Client)

    begin{edit}
    Sorry, I just noticed that GnuArch is apparently in `STAGING' (http://bbs.archlinux.org/viewtopic.php?t=4529)
    and someone else mentioned ABC previously..
    what a great way to enter the forum... damn..
    end{edit}
    ===========================
    Thanks for the great distribution.
    i'd like to request 2 applications
    the first is GnuArch, a superset of subversion.
    http://www.gnuarch.org/
    Secondly, ABC (yet Another Bit-torrent Client)
    http://pingpong-abc.sourceforge.net/
    it seems to be ok, however its UI is quite slow and the underlying bit torrent client (Bit Tornado) isnt compatible with some of the newer torrent trackers.
    If you know of a better bit torrent client -WITH- a gui capable of queueing multiple torrents at a time then by all means add that instead.
    But i just dont like having to manually restart individual torrents all the time.
    Thanks again.

    Pyqt is in the staging repo: http://xentac.net/~tur/repos.php
    Add this repo to your pacman.conf (instructions on the page) and just install with pacman -S.
    Making qtorrent package of PKGBUILD:
    1. Save the code section from the forum in PKGBUILD file in some build directory (doesn't really matter but the best place is /var/abs/local/qtorrent)
    2. Su to became root.
    3. type makepkg (in the dir where you saved the PKGBUILD)
    4. wait a few seconds :-)
    5. if everything goes well (it should) type pacman -A nameofthegeneratedpackagefile.tar.gz
    That's all. Complicated? I don't think so  8)

  • Mirroring my arch installation?

    I have arch on an old computer that uses an IDE hard drive, just to test it out. Since then I've decided that I like arch so much that I'm considering using it on my primary computer, which uses SATA. I know that I can use a SATA to USB converter to copy my installation to the SATA, but here's where it gets complicated... My main computer is x86_64 or amd64, and my arch computer is i686. Also, the main computer is 64-bit, while the arch computer is 32-bit. Is it possible to get arch on a SATA drive and use it in my main computer or will I have to reinstall from scratch?

    I think it's best to do a fresh install, but have a look at some wiki articles:
    * https://wiki.archlinux.org/index.php/Fu … with_rsync
    * https://wiki.archlinux.org/index.php/Mi … installing

  • Accessibility and (Arch)linux

    From slahdot:
    "The strongest push-back against Massachusetts' effort to institute open, non-proprietary document formats has come from the accessibility community, who claim that Open-Source desktop software lags behind Windows.
    Read on here: http://blogs.sun.com/roller/page/korn/20051113
    Ok, archlinux is not a desktop linux OS as many other distrobutions and is not for newbies to linux. But is it also not an OS for playing Doom on it in dark rooms.
    In my opinion we should do something for the accessibility and usability of archlinux.  I mean, we can´t change gnome (usability below zero) and i don´t want GUIs instead of config scripts. But it´s hard to install and running archlinux if you are handicaped (or just don´t want to go mad). We should have some tools included in the distrobutions with that the accessibility of arch is a little bit better.
    What´s your thoughts to it?

    fun {
    Dear Mr <designer>,
    we like your new Uberproduct, but find its both difficult and cumbersome for us as we both suffer from (physical incapacity/mental illness/WindowsDependency/Arsewipe Deficiency Syndrome) .
    Would you please add/remove/amend/improve the following items, as it would suit us better
    ...<snip>
    We understand that, as this is outside the remit of your design, it would have a dramatic effect on the performance of your product, and impinge on your own personal freetime, by increasing your workload.
    But rather than find a product that suits us better, or work towards contributing a solution ourselves, we feel that we should ask you to amend yours as we feel unfairly discriminated against.
    signed
    A. Goodsuggestion
    }nuf
    Seriously tho, theres plenty of distro's around that specifically cater for disabilities / ease of use / multimedia / science / games / you-name-it.
    Thats the beauty of linux. go find a distro that better suits your needs, and amend it to suit those needs better.
    btw, im missing something here.
    Is your request for Arch to cater (better) for :
    people having trouble with non-proprietary document formats?
    people with disabilities?
    people afraid of installation induced dementia?
    Desktop users, or those who think Arch isn't a suitable desktop environment?
    the gaming community?
    People who have difficulty with Setup in general?
    and is the "we" in "we should do something" a statement of voluntary contribution from your good self or the "royal" we meaning "i'll suggest it, you can do it" ?
    kind regards
    kern

  • Just wondering about 64 vs 32 bit distro

    As far as I can tell, my 64 bit hardware will still run 32 bit distro and 32 bit apps... If I'm wrong, it won't be the first time, but links would help here.
    So, if I'm really struggling to get 64 bit Arch (or any 64 bit distro) running, I could instead just get the more popular 32 bit Arch, is that right?

    That is right.

  • No 3D acceleration with Arch + virtualbox-guest-modules 4.3.24-1

    I've been using Arch happily in 64 bit VirtualBox setup for a few months (under 64bit Win7), but after installing cool-retro-term, realized I have no 3D acceleration. glxinfo shows I'm using unaccelerated Gallium instead of Chromium:
    OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
    I've googled about 100 different bug reports and solution suggestions, but to no avail. Virtualbox forums say that a similar bug was fixed last June, and after that the glxinfo should give a dozen warnings about being unable to load stuff, but report the Chromium drivers. I have the latest version of virtualbox-guest-modules (4.3.24-1) which should contain the fix, but that doesn't help.
    I installed Debian today to test things out, and indeed, I had 3D acceleration out of the box. This was likely because the initial install was Debian stable, and the latest Mesa versions (around early 2014) initially broke the 3D acceleration, so probably Mesa was too stable... Upgrading to Debian Jessie broke the 3D acceleration to same state as my Arch install (Gallium renderer instead of Chromium), which seems to support this hypothesis. HOWEVER, re-compiling the latest guest additions seemed to have the effect the Virtualbox forums suggested there should be -- 3D support was restored, and Chromium once again the renderer in glxinfo.
    Has someone successfully gotten Arch under Virtualbox working with 3D acceleration without downgrading Mesa libraries? The Cinnamon desktop nags me about not having HW acceleration, and cool-retro-term uses 100 % CPU due to software rendering, so I'd rather have acceleration than not.

    I have the same problem (with standard 3.19.2-1 kernel, vbox 4.3.26).
    I tried grabbing an older mesa and mesa-libgl from the arch rollback machine (which worked the last time it stopped working) but version 10.4.6 just crashed my machine when gnome was starting. I'm guessing there are more packages required for that approach to work but i don't know what they are. A complete rollback would be clean but would probably be more annoying lol.

  • Is Arch really becoming unstable?

    I've been having a look around the forums and I've been seeing threads saying "Don't use Arch if you don't want to keep maintaining it"...is Arch becoming what I didn't want it to become? When I switched to Arch, people on the Ubuntu forums were saying "Arch is really easy to maintain. When you've set it up, you won't need to do much more". I hope it isn't, because if I leave Arch, I'll have to drop my website (or convert it to another distro) and leave Shaman behind (I helped with some of it's artwork).
    Also I wish there was something like "Archbuntu" because, to be honest, setting up Arch is getting a bit annoying. I posted this on my blog, and I said my dream distro would
    * Rolling release
    * Uses KDE4 (or lets you choose)
    * Lets me choose what programs to install
    * No extra apps I don't need/want
    * Uses the pacman package manager
    * A good frontend to pacman - otherwise known as Shaman
    * Works well out of the box
    * No need to use the CLI
    Which basically means I would love an easy Arch Linux...I couldn't make a distro like that because I have no idea how to do it, and it would take hours and hours to upload an ISO...

    Well having a GUI would be so much better because I would be able to see the description of apps, with Pacman, I am confronted with confusing names. Let's pick on Eye of Gnome. The Pacman package is called "eog". How exactly am I supposed to know what it is? I would have to do
    pacman -Ss eog
    to get
    extra/eog 2.20.4-1 (gnome-extra)
    Eye of Gnome: An image viewing and cataloging program
    If I had a GUI, I could just click on Gnome, then scroll down to "e" (Pacman orders packages in repo order) then tick the box. Which one sounds easier? I search for burn and it comes up with:
    kde/k3b 1.0.4-20080331
    Feature-rich and easy to handle CD burning application
    extra/dvd+rw-tools 7.1-1
    dvd burning tools
    extra/graveman 0.3.12.5-4
    A CD-burning frontend for mkisofs, cdrecord and friends
    extra/k3b 1.0.4-1
    Feature-rich and easy to handle CD burning application
    extra/nautilus-cd-burner 2.20.0-1 (gnome-extra)
    Adds cd burner functionality to nautilus
    community/bashburn 2.1.2-3
    BashBurn is the new name for the cd burning shell script Magma
    community/brasero 0.7.1-2
    A disc burning application for Gnome
    community/gnomebaker 0.6.2-1
    GnomeBaker is a full featured CD/DVD burning application for Gnome
    community/hacburn 0.3.5-3
    HacBurn is a script written in perl to aid in writing CDs. It is a graphical
    interface (using gtk+) to cdrtools, mpg321 and ogg123.
    community/libburn 0.4.2-1
    Library for reading, mastering and writing optical discs
    community/nrg2iso 0.4-5
    Utility for converting CD or DVD image generated by Nero Burning Rom to ISO
    format
    community/xfburn-svn 26453-1 (xfce4-svn)
    CDROM and DVD burning program for XFCE4
    testing/k3b 1.0.4-2
    Feature-rich and easy to handle CD burning application
    testing/nautilus-cd-burner 2.22.0-1 (gnome-extra)
    Adds cd burner functionality to nautilus
    How am I supposed to find the best burner with that? I'll have to experiment with each one until I find a good one...
    Last edited by miggols99 (2008-03-31 17:36:32)

  • My Arch won't boot anymore something about bad blocks

    It was working fine. I booted it up this morning said it found some bad blocks on some of my Linux partitions. How do I scan the surface of my drives with Archlinux.?. Is that even possible with Linux?. This is my USB drive that has the bad blocks.

    Quicken2k wrote:Boot with ro 1?. I'm new to Arch and need a bit more info. Are you telling me to boot up in read only mode?. How?.
    No worries! Simply, boot your computer and when you get to GRUB, select your Arch install and hit 'e'. Now you can edit the 'kernel' line. Append 1 (one) to the end of the line. Hit enter again, and hit 'b' to boot into single user mode. Now you can login as root, and perform whatever fsck's and debugging. Be sure to report back.

  • Arch does not boot (MacBook Pro, rEFIt)

    Several months ago I installed Arch on my MacBookPro (5.1, late 2008) in dual boot with Mac OS X 10.7 (Lion).
    Everything was fine until last Friday when, after a forced shutdown, ArchLinux refused to boot and showed me a black screen instead (I use rEFIt).
    I followed several forum suggestions, mainly consisting in the reflagging of the boot partition (using both fdisk in Mac OS X and parted in Linux) and in the reinstallation of GRUB. After some work, nothing changed: Mac OS X works fine, whilst Linux still offers me a black screen. After few seconds of black screen, the laptop reboots, and rEFIt shows me the same options.
    Does anyone have any suggestion?
    Thank in advance for any help I can get
    Alessia
    This is the output of the rEFIt Partition Inspector tool:
    *** Report for internal hard disk ***
    Current GPT partition table:
    # Start LBA End LBA Type
    1 40 409639 EFI System (FAT)
    2 409640 200228415 Mac OS X HFS+
    3 200228416 201497951 Mac OS X Boot
    4 207269888 207464447 GRUB2 BIOS Boot
    5 207464448 247463935 Basic Data
    6 247463936 271464447 Basic Data
    7 271464448 488396799 Basic Data
    Current MBR partition table:
    # A Start LBA End LBA Type
    1 1 488397167 ee EFI Protective
    MBR contents:
    Boot Code: GRUB
    Partition at LBA 40:
    Boot Code: None (Non-system disk message)
    File System: FAT32
    Listed in GPT as partition 1, type EFI System (FAT)
    Partition at LBA 409640:
    Boot Code: None
    File System: HFS Extended (HFS+)
    Listed in GPT as partition 2, type Mac OS X HFS+
    Partition at LBA 200228416:
    Boot Code: None
    File System: HFS Extended (HFS+)
    Listed in GPT as partition 3, type Mac OS X Boot
    Partition at LBA 207269888:
    Boot Code: None
    File System: ext2
    Listed in GPT as partition 4, type GRUB2 BIOS Boot
    Partition at LBA 207464448:
    Boot Code: None
    File System: ext4
    Listed in GPT as partition 5, type Basic Data
    Partition at LBA 247463936:
    Boot Code: None
    File System: ext4
    Listed in GPT as partition 6, type Basic Data
    Partition at LBA 271464448:
    Boot Code: None
    File System: ext4
    Listed in GPT as partition 7, type Basic Data

    alesssia wrote:The rEFInd's auto-detection shows a generic Linux OS bootable from a generic HD. When selected, Tux is shown, followed by a grub line (that is "GRUB loading"), then by a black screen. Finally, the rEFInd menu shows up again. This is the same behaviour showed by rEFIt and the reason because I used stanzas.
    That description indicates that you were launching a BIOS-mode version of GRUB, and that it failed for some reason that's almost certainly GRUB-specific (bad configuration file, missing modules, etc.).
    After playing with the EFI shell I was able of fixing the Arch stanza, finally finding an error that should be expected:
    Starting vm-linuz-linux
    Using load options root=UUID=e6db22f2-e5bb-4933-bba7-20be86db00if ro quiet initrd=initramfs-linux.img
    Error: Unsupported while loading vmlinuz-linux
    In fact, I'm using a 32-bit version of Arch on a 64-bit EFI.
    That's the problem, then. On a 64-bit EFI, rEFInd can launch 64-bit kernels but not 32-bit kernels.
    I’m currently trying to fix my hybrid MBR, but despite all my efforts with the gdisk and the gptsync (in rEFInd) tools I always end up with the behaviour described in the first lines of this post: “Grub loading...”, black screen, then rEFInd menu again
    I'm not sure what's wrong with that, but I can say with some certainty that it's a GRUB issue. (That's not to say that the solution is in the GRUB configuration; adjusting the hybrid MBR might fix it, but I'm not sure precisely what to suggest.)
    I have no idea about how to proceed. Perhaps (re)installing the 64-bit version of Arch is the only possible solution, but I’m scared by all the painful configuration steps that will follow a fresh installation...
    As you suspect, installing a 64-bit version of Arch should fix the problem. For that matter, a 64-bit kernel with 32-bit userland should work OK, although that might be tricky to maintain -- I imagine that pacman would try to "upgrade" you to new 32-bit kernels every now and then. Still, it might be worth giving it a try. If you do, I recommend installing a kernel, initrd file, and kernel modules (in /lib/modules) outside of pacman. Install a kernel that's slightly behind whatever is current in pacman. That way, even if pacman upgrades your kernel, your 64-bit kernel will be untouched. You can then upgrade your kernel manually whenever it's convenient or desirable to do so.
    Another option is to install a 64-bit version of EFI-mode GRUB, ELILO, or SYSLINUX, and have it launch a 32-bit kernel. I know this is possible because I've done it in some test installations, but I don't recall offhand which boot loader I used, so I can't promise that all three of the ones I mentioned would work. If you go this route, you'll end up with rEFInd to select OS X or GRUB/ELILO/SYSLINUX, which you can then use to select your Linux kernel (or set a very short timeout to launch the kernel more-or-less immediately). See my Web page on EFI boot loaders for Linux for my thoughts on each of these boot loaders.

  • Problems installing Arch 0.7 base on SATA HDD.

    Hi! I am new to Arch and still a bit of a newbie when it comes to Linux in general. I have a friend who runs Arch who has been trying to help me... to no avail. I am trying to install Arch base 0.7 with an ftp installation on my system. Some of my system is as follows:
    P4 3 GHz, 1024 memory. My HDD setup is:
    Primary IDE Master: [NOT DETECTED] (No drive here!)
    Primary IDE Slave: [Maxtor ide drive] Files
    Secondary Master: [Samsung dvd-rom] (ATAPI)
    Secondary Slave: [CDRW] (ATAPI)
    Third ide Master: [SATA-HDD] OS's Windows and Arch
    My Linux partitioning is as follows:
    sda5 /
    sda2 /boot
    sda7 /home
    sda6 swap
    My Grub file looks like this:
    Linux
    root (hd1,1)
    kernel /vmlinuz26 root=/dev/sda5 devfs=nomount ro
    windows
    rootnoverify (hd1,0)
    makeactive
    chainloader +1
    (I have left out the coad for the title line in this forum)
    My windows loads perfectly but I have troubles booting into Linux, when I add quiet to my Kernel line I get this at bootup:
    Booting command-list
    root (hd1,1)
    filesystem type is ext2fs, partition type 0x83
    kernel /vmlinuz26 root (etc....)
    [linuz-bzimage, setup=0x1c00, size=0x3d08535]
    uncompressing kernel... OK, booting the kernel.
    ACPI: Unable to load the System Description Tables
    and then my system stops loading, reset button to restart!
    My friend is a bit of a Linux whizz but he was unable to help me out... I have changed my fstab to look like sdaX... (he told me to)...
    Any suggestions?
    thx

    Similar problem here.
    Pre-partitionned my single HDD which is a Sata 80Gb, with sda6 5Gb for Arch, sda9 /home & sda11 swap.
    Installed Wombat which recognized the HDD on /dev/discs/disc0, adjusted the conf files as if i was going to use hotplug.
    Installed Grub on to the "/" (sda6) partition as I plan to add others distros.
    Also  installed Grub on a new ext2 formatted Floppy with :
    umount /floppy
    /usr/local/sbin/grub --batch <<EOT
    root (fd0)
    setup (fd0)
    quit
    EOT.
    When I boot with that floppy, grub recognize HDD as hd0 and "/" as 6th partition : I can TAB to "vmlinuz26 without a glinch
    Then it boot ... untill I get this message :
    "sata "kernel panic - not syncing: vfs: unable to mount root fs on unknown-block(0,0)""
    Should I edit /etc/rc/conf with some more modules/daemons that those by default ?
    Presently I'm copying my Arch mirror (current & extra) on to another partition to get last packages. Because my box comes with an ULi network controller that was added to the kernel modules early in October, so I want to chroot into my present install, update to latest kernel, udev, dbus & hal, & see what I can do thereafter.

  • Booting with 3.14.* results in unexpected shutdown

    Problem description: Computer boots normally up until the moment before NVIDIA splash and entering login screen (quiet disabled shows no errors), but upon trying to do so suffers abrupt shutdown.
    Some cases the computer screen goes blank, followed by a short period of nothing until the fans start running at max.
    Adding "acpi=off"  to GRUB stops both above-mentioned events, instead the boot processs is simply halted at the same point with screen not being cleared and nothing else happening.
    The computer is an ASUS G55VW laptop, Intel i7 CPU, NVIDIA GTX660M (without Optimus).
    I'm running the stock kernel and the problem has persisted with all core versions of 3.14.* Downgrading NVIDIA from 337.* to 334.* has had no effect (337 depends on >3.14)
    Relevant journalctl (which tells me nothing): (Alternatively, pastebin link)
    -- Logs begin at Wed 2014-03-05 03:33:14 CET, end at Sun 2014-05-04 17:12:33 CEST. --
    May 01 16:01:14 arch systemd-journal[177]: Runtime journal is using 8.0M (max allowed 397.1M, trying to leave 595.7M free of 3.8G available → current limit 397.1M).
    May 01 16:01:14 arch systemd-journal[177]: Runtime journal is using 8.0M (max allowed 397.1M, trying to leave 595.7M free of 3.8G available → current limit 397.1M).
    May 01 16:01:14 arch kernel: Initializing cgroup subsys cpuset
    May 01 16:01:14 arch kernel: Initializing cgroup subsys cpu
    May 01 16:01:14 arch kernel: Initializing cgroup subsys cpuacct
    May 01 16:01:14 arch kernel: Linux version 3.14.2-1-ARCH (nobody@var-lib-archbuild-testing-x86_64-tobias) (gcc version 4.9.0 (GCC) ) #1 SMP PREEMPT Sun Apr 27 11:28:44 CEST 2014
    May 01 16:01:14 arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7919229d-db26-4075-ac4b-97d2fa5fc984 rw quiet
    May 01 16:01:14 arch kernel: e820: BIOS-provided physical RAM map:
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dd6f5fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000dd6f6000-0x00000000dd6f7fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000dd6f8000-0x00000000dd704fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000dd705000-0x00000000ddd05fff] ACPI NVS
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd06000-0x00000000ddd08fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd09000-0x00000000ddd1ffff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd20000-0x00000000ddd25fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd26000-0x00000000ddd27fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd28000-0x00000000ddd31fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddd32000-0x00000000ddec4fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddec5000-0x00000000ddec8fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddec9000-0x00000000ddf12fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf13000-0x00000000ddf37fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf38000-0x00000000ddf3afff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf3b000-0x00000000ddf3cfff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf3d000-0x00000000ddf53fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf54000-0x00000000ddf59fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf5a000-0x00000000ddf61fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf62000-0x00000000ddf62fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf63000-0x00000000ddf71fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf72000-0x00000000ddf72fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf73000-0x00000000ddf7dfff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf7e000-0x00000000ddf82fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddf83000-0x00000000ddfaefff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfaf000-0x00000000ddfaffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfb0000-0x00000000ddfbffff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfc0000-0x00000000ddfe7fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddfe8000-0x00000000ddffbfff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddffc000-0x00000000ddffcfff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddffd000-0x00000000ddffdfff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ddffe000-0x00000000ddffffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de000000-0x00000000de001fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de002000-0x00000000de006fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de007000-0x00000000de01afff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de01b000-0x00000000de5e2fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de5e3000-0x00000000de862fff] ACPI NVS
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de863000-0x00000000de867fff] ACPI data
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de868000-0x00000000de868fff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de869000-0x00000000de8abfff] ACPI NVS
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000de8ac000-0x00000000decbefff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000decbf000-0x00000000deff3fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000deff4000-0x00000000deffffff] usable
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    May 01 16:01:14 arch kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021f3fffff] usable
    May 01 16:01:14 arch kernel: NX (Execute Disable) protection: active
    May 01 16:01:14 arch kernel: efi: EFI v2.31 by American Megatrends
    May 01 16:01:14 arch kernel: efi: ACPI=0xde839000 ACPI 2.0=0xde839000 SMBIOS=0xf04c0 MPS=0xfd4d0
    May 01 16:01:14 arch kernel: efi: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000008000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem01: type=7, attr=0xf, range=[0x0000000000008000-0x000000000005d000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem02: type=4, attr=0xf, range=[0x000000000005d000-0x0000000000060000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem03: type=3, attr=0xf, range=[0x0000000000060000-0x000000000009f000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem04: type=6, attr=0x800000000000000f, range=[0x000000000009f000-0x00000000000a0000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem05: type=7, attr=0xf, range=[0x0000000000100000-0x0000000001000000) (15MB)
    May 01 16:01:14 arch kernel: efi: mem06: type=2, attr=0xf, range=[0x0000000001000000-0x000000000205b000) (16MB)
    May 01 16:01:14 arch kernel: efi: mem07: type=7, attr=0xf, range=[0x000000000205b000-0x00000000379d4000) (857MB)
    May 01 16:01:14 arch kernel: efi: mem08: type=2, attr=0xf, range=[0x00000000379d4000-0x0000000037ce2000) (3MB)
    May 01 16:01:14 arch kernel: efi: mem09: type=7, attr=0xf, range=[0x0000000037ce2000-0x000000009dbfb000) (1631MB)
    May 01 16:01:14 arch kernel: efi: mem10: type=2, attr=0xf, range=[0x000000009dbfb000-0x00000000d2732000) (843MB)
    May 01 16:01:14 arch kernel: efi: mem11: type=1, attr=0xf, range=[0x00000000d2732000-0x00000000d274f000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem12: type=7, attr=0xf, range=[0x00000000d274f000-0x00000000d276c000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem13: type=4, attr=0xf, range=[0x00000000d276c000-0x00000000d293d000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem14: type=7, attr=0xf, range=[0x00000000d293d000-0x00000000d2949000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem15: type=4, attr=0xf, range=[0x00000000d2949000-0x00000000d29a2000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem16: type=7, attr=0xf, range=[0x00000000d29a2000-0x00000000d2ac9000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem17: type=4, attr=0xf, range=[0x00000000d2ac9000-0x00000000dc390000) (152MB)
    May 01 16:01:14 arch kernel: efi: mem18: type=7, attr=0xf, range=[0x00000000dc390000-0x00000000dc393000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem19: type=4, attr=0xf, range=[0x00000000dc393000-0x00000000dc3cd000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem20: type=7, attr=0xf, range=[0x00000000dc3cd000-0x00000000dc3ce000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem21: type=4, attr=0xf, range=[0x00000000dc3ce000-0x00000000dd07f000) (12MB)
    May 01 16:01:14 arch kernel: efi: mem22: type=7, attr=0xf, range=[0x00000000dd07f000-0x00000000dd6d1000) (6MB)
    May 01 16:01:14 arch kernel: efi: mem23: type=2, attr=0xf, range=[0x00000000dd6d1000-0x00000000dd6dd000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem24: type=3, attr=0xf, range=[0x00000000dd6dd000-0x00000000dd6f6000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem25: type=6, attr=0x800000000000000f, range=[0x00000000dd6f6000-0x00000000dd6f8000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem26: type=3, attr=0xf, range=[0x00000000dd6f8000-0x00000000dd705000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem27: type=10, attr=0xf, range=[0x00000000dd705000-0x00000000ddd06000) (6MB)
    May 01 16:01:14 arch kernel: efi: mem28: type=5, attr=0x800000000000000f, range=[0x00000000ddd06000-0x00000000ddd09000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem29: type=3, attr=0xf, range=[0x00000000ddd09000-0x00000000ddd20000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem30: type=5, attr=0x800000000000000f, range=[0x00000000ddd20000-0x00000000ddd26000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem31: type=3, attr=0xf, range=[0x00000000ddd26000-0x00000000ddd28000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem32: type=5, attr=0x800000000000000f, range=[0x00000000ddd28000-0x00000000ddd32000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem33: type=3, attr=0xf, range=[0x00000000ddd32000-0x00000000ddec5000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem34: type=5, attr=0x800000000000000f, range=[0x00000000ddec5000-0x00000000ddec9000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem35: type=3, attr=0xf, range=[0x00000000ddec9000-0x00000000ddf13000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem36: type=5, attr=0x800000000000000f, range=[0x00000000ddf13000-0x00000000ddf1a000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem37: type=6, attr=0x800000000000000f, range=[0x00000000ddf1a000-0x00000000ddf27000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem38: type=5, attr=0x800000000000000f, range=[0x00000000ddf27000-0x00000000ddf38000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem39: type=3, attr=0xf, range=[0x00000000ddf38000-0x00000000ddf3b000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem40: type=5, attr=0x800000000000000f, range=[0x00000000ddf3b000-0x00000000ddf3d000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem41: type=3, attr=0xf, range=[0x00000000ddf3d000-0x00000000ddf54000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem42: type=5, attr=0x800000000000000f, range=[0x00000000ddf54000-0x00000000ddf5a000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem43: type=3, attr=0xf, range=[0x00000000ddf5a000-0x00000000ddf62000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem44: type=5, attr=0x800000000000000f, range=[0x00000000ddf62000-0x00000000ddf63000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem45: type=3, attr=0xf, range=[0x00000000ddf63000-0x00000000ddf72000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem46: type=5, attr=0x800000000000000f, range=[0x00000000ddf72000-0x00000000ddf73000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem47: type=3, attr=0xf, range=[0x00000000ddf73000-0x00000000ddf7e000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem48: type=5, attr=0x800000000000000f, range=[0x00000000ddf7e000-0x00000000ddf83000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem49: type=3, attr=0xf, range=[0x00000000ddf83000-0x00000000ddfaf000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem50: type=5, attr=0x800000000000000f, range=[0x00000000ddfaf000-0x00000000ddfb0000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem51: type=3, attr=0xf, range=[0x00000000ddfb0000-0x00000000ddfc0000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem52: type=5, attr=0x800000000000000f, range=[0x00000000ddfc0000-0x00000000ddfe8000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem53: type=3, attr=0xf, range=[0x00000000ddfe8000-0x00000000ddffc000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem54: type=5, attr=0x800000000000000f, range=[0x00000000ddffc000-0x00000000ddffd000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem55: type=3, attr=0xf, range=[0x00000000ddffd000-0x00000000ddffe000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem56: type=5, attr=0x800000000000000f, range=[0x00000000ddffe000-0x00000000de000000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem57: type=3, attr=0xf, range=[0x00000000de000000-0x00000000de002000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem58: type=5, attr=0x800000000000000f, range=[0x00000000de002000-0x00000000de007000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem59: type=3, attr=0xf, range=[0x00000000de007000-0x00000000de01b000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem60: type=6, attr=0x800000000000000f, range=[0x00000000de01b000-0x00000000de09c000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem61: type=5, attr=0x800000000000000f, range=[0x00000000de09c000-0x00000000de0b9000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem62: type=6, attr=0x800000000000000f, range=[0x00000000de0b9000-0x00000000de0bf000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem63: type=6, attr=0x800000000000000f, range=[0x00000000de0bf000-0x00000000de0c1000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem64: type=6, attr=0x800000000000000f, range=[0x00000000de0c1000-0x00000000de0e3000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem65: type=0, attr=0xf, range=[0x00000000de0e3000-0x00000000de437000) (3MB)
    May 01 16:01:14 arch kernel: efi: mem66: type=0, attr=0xf, range=[0x00000000de437000-0x00000000de578000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem67: type=0, attr=0xf, range=[0x00000000de578000-0x00000000de57e000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem68: type=0, attr=0xf, range=[0x00000000de57e000-0x00000000de5e3000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem69: type=10, attr=0xf, range=[0x00000000de5e3000-0x00000000de699000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem70: type=10, attr=0xf, range=[0x00000000de699000-0x00000000de863000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem71: type=9, attr=0xf, range=[0x00000000de863000-0x00000000de868000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem72: type=4, attr=0xf, range=[0x00000000de868000-0x00000000de869000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem73: type=10, attr=0xf, range=[0x00000000de869000-0x00000000de8ac000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem74: type=4, attr=0xf, range=[0x00000000de8ac000-0x00000000de9fa000) (1MB)
    May 01 16:01:14 arch kernel: efi: mem75: type=3, attr=0xf, range=[0x00000000de9fa000-0x00000000dec96000) (2MB)
    May 01 16:01:14 arch kernel: efi: mem76: type=4, attr=0xf, range=[0x00000000dec96000-0x00000000deca6000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem77: type=3, attr=0xf, range=[0x00000000deca6000-0x00000000decb8000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem78: type=4, attr=0xf, range=[0x00000000decb8000-0x00000000decbf000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem79: type=6, attr=0x800000000000000f, range=[0x00000000decbf000-0x00000000deff4000) (3MB)
    May 01 16:01:14 arch kernel: efi: mem80: type=4, attr=0xf, range=[0x00000000deff4000-0x00000000df000000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem81: type=7, attr=0xf, range=[0x0000000100000000-0x000000021f400000) (4596MB)
    May 01 16:01:14 arch kernel: efi: mem82: type=11, attr=0x8000000000000001, range=[0x00000000f8000000-0x00000000fc000000) (64MB)
    May 01 16:01:14 arch kernel: efi: mem83: type=11, attr=0x8000000000000001, range=[0x00000000fec00000-0x00000000fec01000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem84: type=11, attr=0x8000000000000001, range=[0x00000000fed00000-0x00000000fed04000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem85: type=11, attr=0x8000000000000001, range=[0x00000000fed1c000-0x00000000fed20000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem86: type=11, attr=0x8000000000000001, range=[0x00000000fee00000-0x00000000fee01000) (0MB)
    May 01 16:01:14 arch kernel: efi: mem87: type=11, attr=0x8000000000000001, range=[0x00000000ff000000-0x0000000100000000) (16MB)
    May 01 16:01:14 arch kernel: SMBIOS 2.7 present.
    May 01 16:01:14 arch kernel: DMI: ASUSTeK COMPUTER INC. G55VW/G55VW, BIOS G55VW.217 11/05/2012
    May 01 16:01:14 arch kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    May 01 16:01:14 arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    May 01 16:01:14 arch kernel: No AGP bridge found
    May 01 16:01:14 arch kernel: e820: last_pfn = 0x21f400 max_arch_pfn = 0x400000000
    May 01 16:01:14 arch kernel: MTRR default type: uncachable
    May 01 16:01:14 arch kernel: MTRR fixed ranges enabled:
    May 01 16:01:14 arch kernel: 00000-9FFFF write-back
    May 01 16:01:14 arch kernel: A0000-BFFFF uncachable
    May 01 16:01:14 arch kernel: C0000-CFFFF write-protect
    May 01 16:01:14 arch kernel: D0000-DFFFF uncachable
    May 01 16:01:14 arch kernel: E0000-FFFFF write-protect
    May 01 16:01:14 arch kernel: MTRR variable ranges enabled:
    May 01 16:01:14 arch kernel: 0 base 000000000 mask E00000000 write-back
    May 01 16:01:14 arch kernel: 1 base 200000000 mask FF0000000 write-back
    May 01 16:01:14 arch kernel: 2 base 210000000 mask FF8000000 write-back
    May 01 16:01:14 arch kernel: 3 base 218000000 mask FFC000000 write-back
    May 01 16:01:14 arch kernel: 4 base 21C000000 mask FFE000000 write-back
    May 01 16:01:14 arch kernel: 5 base 21E000000 mask FFF000000 write-back
    May 01 16:01:14 arch kernel: 6 base 21F000000 mask FFFC00000 write-back
    May 01 16:01:14 arch kernel: 7 base 0E0000000 mask FE0000000 uncachable
    May 01 16:01:14 arch kernel: 8 base 0DFC00000 mask FFFC00000 uncachable
    May 01 16:01:14 arch kernel: 9 disabled
    May 01 16:01:14 arch kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    May 01 16:01:14 arch kernel: e820: update [mem 0xdfc00000-0xffffffff] usable ==> reserved
    May 01 16:01:14 arch kernel: e820: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
    May 01 16:01:14 arch kernel: found SMP MP-table at [mem 0x000fd830-0x000fd83f] mapped at [ffff8800000fd830]
    May 01 16:01:14 arch kernel: Scanning 1 areas for low memory corruption
    May 01 16:01:14 arch kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    May 01 16:01:14 arch kernel: [mem 0x00000000-0x000fffff] page 4k
    May 01 16:01:14 arch kernel: BRK [0x01b39000, 0x01b39fff] PGTABLE
    May 01 16:01:14 arch kernel: BRK [0x01b3a000, 0x01b3afff] PGTABLE
    May 01 16:01:14 arch kernel: BRK [0x01b3b000, 0x01b3bfff] PGTABLE
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x21f200000-0x21f3fffff]
    May 01 16:01:14 arch kernel: [mem 0x21f200000-0x21f3fffff] page 2M
    May 01 16:01:14 arch kernel: BRK [0x01b3c000, 0x01b3cfff] PGTABLE
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x21c000000-0x21f1fffff]
    May 01 16:01:14 arch kernel: [mem 0x21c000000-0x21f1fffff] page 2M
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x200000000-0x21bffffff]
    May 01 16:01:14 arch kernel: [mem 0x200000000-0x21bffffff] page 2M
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x00100000-0xdd6f5fff]
    May 01 16:01:14 arch kernel: [mem 0x00100000-0x001fffff] page 4k
    May 01 16:01:14 arch kernel: [mem 0x00200000-0xdd5fffff] page 2M
    May 01 16:01:14 arch kernel: [mem 0xdd600000-0xdd6f5fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xdd6f8000-0xdd704fff]
    May 01 16:01:14 arch kernel: [mem 0xdd6f8000-0xdd704fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddd09000-0xddd1ffff]
    May 01 16:01:14 arch kernel: [mem 0xddd09000-0xddd1ffff] page 4k
    May 01 16:01:14 arch kernel: BRK [0x01b3d000, 0x01b3dfff] PGTABLE
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddd26000-0xddd27fff]
    May 01 16:01:14 arch kernel: [mem 0xddd26000-0xddd27fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddd32000-0xddec4fff]
    May 01 16:01:14 arch kernel: [mem 0xddd32000-0xddec4fff] page 4k
    May 01 16:01:14 arch kernel: BRK [0x01b3e000, 0x01b3efff] PGTABLE
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddec9000-0xddf12fff]
    May 01 16:01:14 arch kernel: [mem 0xddec9000-0xddf12fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf38000-0xddf3afff]
    May 01 16:01:14 arch kernel: [mem 0xddf38000-0xddf3afff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf3d000-0xddf53fff]
    May 01 16:01:14 arch kernel: [mem 0xddf3d000-0xddf53fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf5a000-0xddf61fff]
    May 01 16:01:14 arch kernel: [mem 0xddf5a000-0xddf61fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf63000-0xddf71fff]
    May 01 16:01:14 arch kernel: [mem 0xddf63000-0xddf71fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf73000-0xddf7dfff]
    May 01 16:01:14 arch kernel: [mem 0xddf73000-0xddf7dfff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddf83000-0xddfaefff]
    May 01 16:01:14 arch kernel: [mem 0xddf83000-0xddfaefff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddfb0000-0xddfbffff]
    May 01 16:01:14 arch kernel: [mem 0xddfb0000-0xddfbffff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddfe8000-0xddffbfff]
    May 01 16:01:14 arch kernel: [mem 0xddfe8000-0xddffbfff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xddffd000-0xddffdfff]
    May 01 16:01:14 arch kernel: [mem 0xddffd000-0xddffdfff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde000000-0xde001fff]
    May 01 16:01:14 arch kernel: [mem 0xde000000-0xde001fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde007000-0xde01afff]
    May 01 16:01:14 arch kernel: [mem 0xde007000-0xde01afff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde868000-0xde868fff]
    May 01 16:01:14 arch kernel: [mem 0xde868000-0xde868fff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xde8ac000-0xdecbefff]
    May 01 16:01:14 arch kernel: [mem 0xde8ac000-0xde9fffff] page 4k
    May 01 16:01:14 arch kernel: [mem 0xdea00000-0xdebfffff] page 2M
    May 01 16:01:14 arch kernel: [mem 0xdec00000-0xdecbefff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0xdeff4000-0xdeffffff]
    May 01 16:01:14 arch kernel: [mem 0xdeff4000-0xdeffffff] page 4k
    May 01 16:01:14 arch kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
    May 01 16:01:14 arch kernel: [mem 0x100000000-0x1ffffffff] page 2M
    May 01 16:01:14 arch kernel: RAMDISK: [mem 0x379d4000-0x37ce1fff]
    May 01 16:01:14 arch kernel: ACPI: RSDP 00000000de839000 000024 (v02 _ASUS_)
    May 01 16:01:14 arch kernel: ACPI: XSDT 00000000de839080 00007C (v01 _ASUS_ Notebook 01072009 AMI 00010013)
    May 01 16:01:14 arch kernel: ACPI: FACP 00000000de849e28 00010C (v05 _ASUS_ Notebook 01072009 AMI 00010013)
    May 01 16:01:14 arch kernel: ACPI: DSDT 00000000de839190 010C93 (v02 _ASUS_ Notebook 00000013 INTL 20091112)
    May 01 16:01:14 arch kernel: ACPI: FACS 00000000de860080 000040
    May 01 16:01:14 arch kernel: ACPI: APIC 00000000de849f38 000092 (v03 _ASUS_ Notebook 01072009 AMI 00010013)
    May 01 16:01:14 arch kernel: ACPI: FPDT 00000000de849fd0 000044 (v01 _ASUS_ Notebook 01072009 AMI 00010013)
    May 01 16:01:14 arch kernel: ACPI: ECDT 00000000de84a018 0000C1 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
    May 01 16:01:14 arch kernel: ACPI: MCFG 00000000de84a0e0 00003C (v01 _ASUS_ Notebook 01072009 MSFT 00000097)
    May 01 16:01:14 arch kernel: ACPI: SLIC 00000000de84a120 000176 (v01 _ASUS_ Notebook 01072009 ASUS 00000001)
    May 01 16:01:14 arch kernel: ACPI: HPET 00000000de84a298 000038 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84a2d0 00066E (v01 AhciR1 AhciTab1 00001000 INTL 20091112)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84a940 00049E (v01 AhciR2 AhciTab2 00001000 INTL 20091112)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84ade0 00090A (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de84b6f0 000A92 (v01 PmRef CpuPm 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: Local APIC address 0xfee00000
    May 01 16:01:14 arch kernel: No NUMA configuration found
    May 01 16:01:14 arch kernel: Faking a node at [mem 0x0000000000000000-0x000000021f3fffff]
    May 01 16:01:14 arch kernel: Initmem setup node 0 [mem 0x00000000-0x21f3fffff]
    May 01 16:01:14 arch kernel: NODE_DATA [mem 0x21f3ef000-0x21f3f3fff]
    May 01 16:01:14 arch kernel: [ffffea0000000000-ffffea00087fffff] PMD -> [ffff880216a00000-ffff88021e9fffff] on node 0
    May 01 16:01:14 arch kernel: Zone ranges:
    May 01 16:01:14 arch kernel: DMA [mem 0x00001000-0x00ffffff]
    May 01 16:01:14 arch kernel: DMA32 [mem 0x01000000-0xffffffff]
    May 01 16:01:14 arch kernel: Normal [mem 0x100000000-0x21f3fffff]
    May 01 16:01:14 arch kernel: Movable zone start for each node
    May 01 16:01:14 arch kernel: Early memory node ranges
    May 01 16:01:14 arch kernel: node 0: [mem 0x00001000-0x0009efff]
    May 01 16:01:14 arch kernel: node 0: [mem 0x00100000-0xdd6f5fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xdd6f8000-0xdd704fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddd09000-0xddd1ffff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddd26000-0xddd27fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddd32000-0xddec4fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddec9000-0xddf12fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf38000-0xddf3afff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf3d000-0xddf53fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf5a000-0xddf61fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf63000-0xddf71fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf73000-0xddf7dfff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddf83000-0xddfaefff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddfb0000-0xddfbffff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddfe8000-0xddffbfff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xddffd000-0xddffdfff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xde000000-0xde001fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xde007000-0xde01afff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xde868000-0xde868fff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xde8ac000-0xdecbefff]
    May 01 16:01:14 arch kernel: node 0: [mem 0xdeff4000-0xdeffffff]
    May 01 16:01:14 arch kernel: node 0: [mem 0x100000000-0x21f3fffff]
    May 01 16:01:14 arch kernel: On node 0 totalpages: 2085210
    May 01 16:01:14 arch kernel: DMA zone: 64 pages used for memmap
    May 01 16:01:14 arch kernel: DMA zone: 28 pages reserved
    May 01 16:01:14 arch kernel: DMA zone: 3998 pages, LIFO batch:0
    May 01 16:01:14 arch kernel: DMA32 zone: 14135 pages used for memmap
    May 01 16:01:14 arch kernel: DMA32 zone: 904636 pages, LIFO batch:31
    May 01 16:01:14 arch kernel: Normal zone: 18384 pages used for memmap
    May 01 16:01:14 arch kernel: Normal zone: 1176576 pages, LIFO batch:31
    May 01 16:01:14 arch kernel: ACPI: PM-Timer IO Port: 0x408
    May 01 16:01:14 arch kernel: ACPI: Local APIC address 0xfee00000
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
    May 01 16:01:14 arch kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
    May 01 16:01:14 arch kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    May 01 16:01:14 arch kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    May 01 16:01:14 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    May 01 16:01:14 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    May 01 16:01:14 arch kernel: ACPI: IRQ0 used by override.
    May 01 16:01:14 arch kernel: ACPI: IRQ2 used by override.
    May 01 16:01:14 arch kernel: ACPI: IRQ9 used by override.
    May 01 16:01:14 arch kernel: Using ACPI (MADT) for SMP configuration information
    May 01 16:01:14 arch kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
    May 01 16:01:14 arch kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
    May 01 16:01:14 arch kernel: nr_irqs_gsi: 40
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdd6f6000-0xdd6f7fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdd705000-0xddd05fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddd06000-0xddd08fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddd20000-0xddd25fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddd28000-0xddd31fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddec5000-0xddec8fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf13000-0xddf37fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf3b000-0xddf3cfff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf54000-0xddf59fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf62000-0xddf62fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf72000-0xddf72fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddf7e000-0xddf82fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddfaf000-0xddfaffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddfc0000-0xddfe7fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddffc000-0xddffcfff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xddffe000-0xddffffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde002000-0xde006fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde01b000-0xde5e2fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde5e3000-0xde862fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde863000-0xde867fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xde869000-0xde8abfff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdecbf000-0xdeff3fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xdf000000-0xf7ffffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
    May 01 16:01:14 arch kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
    May 01 16:01:14 arch kernel: e820: [mem 0xdf000000-0xf7ffffff] available for PCI devices
    May 01 16:01:14 arch kernel: Booting paravirtualized kernel on bare hardware
    May 01 16:01:14 arch kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    May 01 16:01:14 arch kernel: PERCPU: Embedded 29 pages/cpu @ffff88021f000000 s87040 r8192 d23552 u262144
    May 01 16:01:14 arch kernel: pcpu-alloc: s87040 r8192 d23552 u262144 alloc=1*2097152
    May 01 16:01:14 arch kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    May 01 16:01:14 arch kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2052599
    May 01 16:01:14 arch kernel: Policy zone: Normal
    May 01 16:01:14 arch kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7919229d-db26-4075-ac4b-97d2fa5fc984 rw quiet
    May 01 16:01:14 arch kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    May 01 16:01:14 arch kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340
    May 01 16:01:14 arch kernel: Checking aperture...
    May 01 16:01:14 arch kernel: No AGP bridge found
    May 01 16:01:14 arch kernel: Calgary: detecting Calgary via BIOS EBDA area
    May 01 16:01:14 arch kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    May 01 16:01:14 arch kernel: Memory: 7948780K/8340840K available (5229K kernel code, 857K rwdata, 1632K rodata, 1120K init, 1288K bss, 392060K reserved)
    May 01 16:01:14 arch kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
    May 01 16:01:14 arch kernel: Preemptible hierarchical RCU implementation.
    May 01 16:01:14 arch kernel: RCU dyntick-idle grace-period acceleration is enabled.
    May 01 16:01:14 arch kernel: Dump stacks of tasks blocking RCU-preempt GP.
    May 01 16:01:14 arch kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
    May 01 16:01:14 arch kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
    May 01 16:01:14 arch kernel: NR_IRQS:8448 nr_irqs:744 16
    May 01 16:01:14 arch kernel: Console: colour dummy device 80x25
    May 01 16:01:14 arch kernel: console [tty0] enabled
    May 01 16:01:14 arch kernel: allocated 33554432 bytes of page_cgroup
    May 01 16:01:14 arch kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    May 01 16:01:14 arch kernel: hpet clockevent registered
    May 01 16:01:14 arch kernel: tsc: Fast TSC calibration using PIT
    May 01 16:01:14 arch kernel: tsc: Detected 2294.759 MHz processor
    May 01 16:01:14 arch kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4591.74 BogoMIPS (lpj=7649196)
    May 01 16:01:14 arch kernel: pid_max: default: 32768 minimum: 301
    May 01 16:01:14 arch kernel: ACPI: Core revision 20131218
    May 01 16:01:14 arch kernel: ACPI: All ACPI Tables successfully acquired
    May 01 16:01:14 arch kernel: Security Framework initialized
    May 01 16:01:14 arch kernel: Yama: becoming mindful.
    May 01 16:01:14 arch kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    May 01 16:01:14 arch kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    May 01 16:01:14 arch kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
    May 01 16:01:14 arch kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
    May 01 16:01:14 arch kernel: Initializing cgroup subsys memory
    May 01 16:01:14 arch kernel: Initializing cgroup subsys devices
    May 01 16:01:14 arch kernel: Initializing cgroup subsys freezer
    May 01 16:01:14 arch kernel: Initializing cgroup subsys net_cls
    May 01 16:01:14 arch kernel: Initializing cgroup subsys blkio
    May 01 16:01:14 arch kernel: CPU: Physical Processor ID: 0
    May 01 16:01:14 arch kernel: CPU: Processor Core ID: 0
    May 01 16:01:14 arch kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
    May 01 16:01:14 arch kernel: mce: CPU supports 9 MCE banks
    May 01 16:01:14 arch kernel: CPU0: Thermal monitoring enabled (TM1)
    May 01 16:01:14 arch kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
    Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
    tlb_flushall_shift: 2
    May 01 16:01:14 arch kernel: Freeing SMP alternatives memory: 20K (ffffffff819f0000 - ffffffff819f5000)
    May 01 16:01:14 arch kernel: ftrace: allocating 20026 entries in 79 pages
    May 01 16:01:14 arch kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    May 01 16:01:14 arch kernel: smpboot: CPU0: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz (fam: 06, model: 3a, stepping: 09)
    May 01 16:01:14 arch kernel: TSC deadline timer enabled
    May 01 16:01:14 arch kernel: Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
    May 01 16:01:14 arch kernel: ... version: 3
    May 01 16:01:14 arch kernel: ... bit width: 48
    May 01 16:01:14 arch kernel: ... generic registers: 4
    May 01 16:01:14 arch kernel: ... value mask: 0000ffffffffffff
    May 01 16:01:14 arch kernel: ... max period: 0000ffffffffffff
    May 01 16:01:14 arch kernel: ... fixed-purpose events: 3
    May 01 16:01:14 arch kernel: ... event mask: 000000070000000f
    May 01 16:01:14 arch kernel: x86: Booting SMP configuration:
    May 01 16:01:14 arch kernel: .... node #0, CPUs: #1
    May 01 16:01:14 arch kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    May 01 16:01:14 arch kernel: #2 #3 #4 #5 #6 #7
    May 01 16:01:14 arch kernel: x86: Booted up 1 node, 8 CPUs
    May 01 16:01:14 arch kernel: smpboot: Total of 8 processors activated (36730.98 BogoMIPS)
    May 01 16:01:14 arch kernel: devtmpfs: initialized
    May 01 16:01:14 arch kernel: PM: Registering ACPI NVS region [mem 0xdd705000-0xddd05fff] (6295552 bytes)
    May 01 16:01:14 arch kernel: PM: Registering ACPI NVS region [mem 0xde5e3000-0xde862fff] (2621440 bytes)
    May 01 16:01:14 arch kernel: PM: Registering ACPI NVS region [mem 0xde869000-0xde8abfff] (274432 bytes)
    May 01 16:01:14 arch kernel: pinctrl core: initialized pinctrl subsystem
    May 01 16:01:14 arch kernel: RTC time: 14:01:11, date: 05/01/14
    May 01 16:01:14 arch kernel: NET: Registered protocol family 16
    May 01 16:01:14 arch kernel: cpuidle: using governor ladder
    May 01 16:01:14 arch kernel: cpuidle: using governor menu
    May 01 16:01:14 arch kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    May 01 16:01:14 arch kernel: ACPI: bus type PCI registered
    May 01 16:01:14 arch kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    May 01 16:01:14 arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
    May 01 16:01:14 arch kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    May 01 16:01:14 arch kernel: PCI: Using configuration type 1 for base access
    May 01 16:01:14 arch kernel: bio: create slab <bio-0> at 0
    May 01 16:01:14 arch kernel: ACPI: Added _OSI(Module Device)
    May 01 16:01:14 arch kernel: ACPI: Added _OSI(Processor Device)
    May 01 16:01:14 arch kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    May 01 16:01:14 arch kernel: ACPI: Added _OSI(Processor Aggregator Device)
    May 01 16:01:14 arch kernel: ACPI : EC: EC description table is found, configuring boot EC
    May 01 16:01:14 arch kernel: ACPI: Executed 1 blocks of module-level executable AML code
    May 01 16:01:14 arch kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de590018 000853 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: Dynamic OEM Table Load:
    May 01 16:01:14 arch kernel: ACPI: SSDT (null) 000853 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de591a98 000303 (v01 PmRef ApIst 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: Dynamic OEM Table Load:
    May 01 16:01:14 arch kernel: ACPI: SSDT (null) 000303 (v01 PmRef ApIst 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: SSDT 00000000de592c18 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: Dynamic OEM Table Load:
    May 01 16:01:14 arch kernel: ACPI: SSDT (null) 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
    May 01 16:01:14 arch kernel: ACPI: Interpreter enabled
    May 01 16:01:14 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-580)
    May 01 16:01:14 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580)
    May 01 16:01:14 arch kernel: ACPI: (supports S0 S3 S4 S5)
    May 01 16:01:14 arch kernel: ACPI: Using IOAPIC for interrupt routing
    May 01 16:01:14 arch kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    May 01 16:01:14 arch kernel: ACPI: No dock devices found.
    May 01 16:01:14 arch kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
    May 01 16:01:14 arch kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    May 01 16:01:14 arch kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME]
    May 01 16:01:14 arch kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability]
    May 01 16:01:14 arch kernel: PCI host bridge to bus 0000:00
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: root bus resource [mem 0xdfc00000-0xfeafffff]
    May 01 16:01:14 arch kernel: pci 0000:00:00.0: [8086:0154] type 00 class 0x060000
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: [8086:0151] type 01 class 0x060400
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
    May 01 16:01:14 arch kernel: pci 0000:00:14.0: reg 0x10: [mem 0xf7300000-0xf730ffff 64bit]
    May 01 16:01:14 arch kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:14.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
    May 01 16:01:14 arch kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf731b000-0xf731b00f 64bit]
    May 01 16:01:14 arch kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
    May 01 16:01:14 arch kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7318000-0xf73183ff]
    May 01 16:01:14 arch kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
    May 01 16:01:14 arch kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7310000-0xf7313fff 64bit]
    May 01 16:01:14 arch kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
    May 01 16:01:14 arch kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: [8086:1e12] type 01 class 0x060400
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: [8086:1e16] type 01 class 0x060400
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: [8086:1e18] type 01 class 0x060400
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
    May 01 16:01:14 arch kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7317000-0xf73173ff]
    May 01 16:01:14 arch kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1f.0: [8086:1e57] type 00 class 0x060100
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: [8086:1e03] type 00 class 0x010601
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf070-0xf077]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf060-0xf063]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf050-0xf057]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf040-0xf043]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf020-0xf03f]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7316000-0xf73167ff]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.2: PME# supported from D3hot
    May 01 16:01:14 arch kernel: pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
    May 01 16:01:14 arch kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7315000-0xf73150ff 64bit]
    May 01 16:01:14 arch kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf000-0xf01f]
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: [10de:0fd4] type 00 class 0x030000
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x14: [mem 0xe0000000-0xefffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
    May 01 16:01:14 arch kernel: pci 0000:01:00.1: [10de:0e1b] type 00 class 0x040300
    May 01 16:01:14 arch kernel: pci 0000:01:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: [168c:0032] type 00 class 0x028000
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: reg 0x10: [mem 0xf7200000-0xf727ffff 64bit]
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: reg 0x30: [mem 0xf7280000-0xf728ffff pref]
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: supports D1 D2
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:03:00.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xf7200000-0xf72fffff]
    May 01 16:01:14 arch kernel: pci 0000:04:00.0: [1969:1083] type 00 class 0x020000
    May 01 16:01:14 arch kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7100000-0xf713ffff 64bit]
    May 01 16:01:14 arch kernel: pci 0000:04:00.0: reg 0x18: [io 0xd000-0xd07f]
    May 01 16:01:14 arch kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 01 16:01:14 arch kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: PCI bridge to [bus 04]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [mem 0xf7100000-0xf71fffff]
    May 01 16:01:14 arch kernel: acpiphp: Slot [1] registered
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: PCI bridge to [bus 05]
    May 01 16:01:14 arch kernel: acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 12)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 10 12)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 12)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled.
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled.
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 *4 5 6 7 10 12)
    May 01 16:01:14 arch kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *10 12)
    May 01 16:01:14 arch kernel: ACPI: Enabled 3 GPEs in block 00 to 3F
    May 01 16:01:14 arch kernel: ACPI : EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62
    May 01 16:01:14 arch kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    May 01 16:01:14 arch kernel: vgaarb: loaded
    May 01 16:01:14 arch kernel: vgaarb: bridge control possible 0000:01:00.0
    May 01 16:01:14 arch kernel: PCI: Using ACPI for IRQ routing
    May 01 16:01:14 arch kernel: PCI: pci_cache_line_size set to 64 bytes
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdd6f6000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdd705000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddd20000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddd28000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddec5000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf13000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf3b000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf54000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf62000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf72000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddf7e000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddfaf000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddfc0000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddffc000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xddffe000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xde002000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xde01b000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xde869000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdecbf000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0xdf000000-0xdfffffff]
    May 01 16:01:14 arch kernel: e820: reserve RAM buffer [mem 0x21f400000-0x21fffffff]
    May 01 16:01:14 arch kernel: NetLabel: Initializing
    May 01 16:01:14 arch kernel: NetLabel: domain hash size = 128
    May 01 16:01:14 arch kernel: NetLabel: protocols = UNLABELED CIPSOv4
    May 01 16:01:14 arch kernel: NetLabel: unlabeled traffic allowed by default
    May 01 16:01:14 arch kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    May 01 16:01:14 arch kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    May 01 16:01:14 arch kernel: Switched to clocksource hpet
    May 01 16:01:14 arch kernel: pnp: PnP ACPI init
    May 01 16:01:14 arch kernel: ACPI: bus type PNP registered
    May 01 16:01:14 arch kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
    May 01 16:01:14 arch kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    May 01 16:01:14 arch kernel: pnp 00:01: [dma 4]
    May 01 16:01:14 arch kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
    May 01 16:01:14 arch kernel: pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
    May 01 16:01:14 arch kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
    May 01 16:01:14 arch kernel: system 00:04: [io 0x0680-0x069f] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0x1000-0x100f] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0xffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0xffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0x0400-0x0453] could not be reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0x0458-0x047f] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0x0500-0x057f] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: [io 0x164e-0x164f] has been reserved
    May 01 16:01:14 arch kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 01 16:01:14 arch kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
    May 01 16:01:14 arch kernel: system 00:06: [io 0x0454-0x0457] has been reserved
    May 01 16:01:14 arch kernel: system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
    May 01 16:01:14 arch kernel: system 00:07: [io 0x04d0-0x04d1] has been reserved
    May 01 16:01:14 arch kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 01 16:01:14 arch kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0c04 (active)
    May 01 16:01:14 arch kernel: system 00:09: [io 0x0240-0x0259] has been reserved
    May 01 16:01:14 arch kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 01 16:01:14 arch kernel: pnp 00:0a: Plug and Play ACPI device, IDs ETD0101 SYN0a00 SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
    May 01 16:01:14 arch kernel: pnp 00:0b: Plug and Play ACPI device, IDs ATK3001 PNP030b (active)
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed1c000-0xfed1ffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed10000-0xfed17fff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed18000-0xfed18fff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed19000-0xfed19fff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xf8000000-0xfbffffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed20000-0xfed3ffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed90000-0xfed93fff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfed45000-0xfed8ffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xff000000-0xffffffff] has been reserved
    May 01 16:01:14 arch kernel: system 00:0c: [mem 0xfee00000-0xfeefffff] could not be reserved
    May 01 16:01:14 arch kernel: system 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 01 16:01:14 arch kernel: pnp: PnP ACPI: found 13 devices
    May 01 16:01:14 arch kernel: ACPI: bus type PNP unregistered
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [io 0x1000-0x0fff] to [bus 05] add_size 1000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 05] add_size 200000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff] to [bus 05] add_size 200000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: BAR 14: assigned [mem 0xdfc00000-0xdfdfffff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: BAR 15: assigned [mem 0xdfe00000-0xdfffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: BAR 13: assigned [io 0x2000-0x2fff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
    May 01 16:01:14 arch kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xf7200000-0xf72fffff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: PCI bridge to [bus 04]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.3: bridge window [mem 0xf7100000-0xf71fffff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: PCI bridge to [bus 05]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [io 0x2000-0x2fff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0xdfc00000-0xdfdfffff]
    May 01 16:01:14 arch kernel: pci 0000:00:1c.4: bridge window [mem 0xdfe00000-0xdfffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:00: resource 11 [mem 0xdfc00000-0xfeafffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    May 01 16:01:14 arch kernel: pci_bus 0000:01: resource 1 [mem 0xf6000000-0xf70fffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:01: resource 2 [mem 0xe0000000-0xf1ffffff 64bit pref]
    May 01 16:01:14 arch kernel: pci_bus 0000:03: resource 1 [mem 0xf7200000-0xf72fffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:04: resource 0 [io 0xd000-0xdfff]
    May 01 16:01:14 arch kernel: pci_bus 0000:04: resource 1 [mem 0xf7100000-0xf71fffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:05: resource 0 [io 0x2000-0x2fff]
    May 01 16:01:14 arch kernel: pci_bus 0000:05: resource 1 [mem 0xdfc00000-0xdfdfffff]
    May 01 16:01:14 arch kernel: pci_bus 0000:05: resource 2 [mem 0xdfe00000-0xdfffffff 64bit pref]
    May 01 16:01:14 arch kernel: NET: Registered protocol family 2
    May 01 16:01:14 arch kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
    May 01 16:01:14 arch kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    May 01 16:01:14 arch kernel: TCP: Hash tables configured (established 65536 bind 65536)
    May 01 16:01:14 arch kernel: TCP: reno registered
    May 01 16:01:14 arch kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
    May 01 16:01:14 arch kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
    May 01 16:01:14 arch kernel: NET: Registered protocol family 1
    May 01 16:01:14 arch kernel: pci 0000:01:00.0: Boot video device
    May 01 16:01:14 arch kernel: PCI: CLS 64 bytes, default 64
    May 01 16:01:14 arch kernel: Unpacking initramfs...
    May 01 16:01:14 arch kernel: Freeing initrd memory: 3128K (ffff8800379d4000 - ffff880037ce2000)
    May 01 16:01:14 arch kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    May 01 16:01:14 arch kernel: software IO TLB [mem 0xce76c000-0xd276c000] (64MB) mapped at [ffff8800ce76c000-ffff8800d276bfff]
    May 01 16:01:14 arch kernel: RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
    May 01 16:01:14 arch kernel: Scanning for low memory corruption every 60 seconds
    May 01 16:01:14 arch kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
    May 01 16:01:14 arch kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    May 01 16:01:14 arch kernel: zbud: loaded
    May 01 16:01:14 arch kernel: VFS: Disk quotas dquot_6.5.2
    May 01 16:01:14 arch kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    May 01 16:01:14 arch kernel: msgmni has been set to 15880
    May 01 16:01:14 arch kernel: Key type big_key registered
    May 01 16:01:14 arch kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    May 01 16:01:14 arch kernel: io scheduler noop registered
    May 01 16:01:14 arch kernel: io scheduler deadline registered
    May 01 16:01:14 arch kernel: io scheduler cfq registered (default)
    May 01 16:01:14 arch kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
    May 01 16:01:14 arch kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    May 01 16:01:14 arch kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    May 01 16:01:14 arch kernel: efifb: probing for efifb
    May 01 16:01:14 arch kernel: efifb: framebuffer at 0xf1000000, mapped to 0xffffc90004e80000, using 1920k, total 1920k
    May 01 16:01:14 arch kernel: efifb: mode is 800x600x32, linelength=3200, pages=1
    May 01 16:01:14 arch kernel: efifb: scrolling: redraw
    May 01 16:01:14 arch kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    May 01 16:01:14 arch kernel: Console: switching to colour frame buffer device 100x37
    May 01 16:01:14 arch kernel: fb0: EFI VGA frame buffer device
    May 01 16:01:14 arch kernel: intel_idle: MWAIT substates: 0x21120
    May 01 16:01:14 arch kernel: intel_idle: v0.4 model 0x3A
    May 01 16:01:14 arch kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
    May 01 16:01:14 arch kernel: GHES: HEST is not enabled!
    May 01 16:01:14 arch kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    May 01 16:01:14 arch kernel: Linux agpgart interface v0.103
    May 01 16:01:14 arch kernel: rtc_cmos 00:05: RTC can wake from S4
    May 01 16:01:14 arch kernel: rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
    May 01 16:01:14 arch kernel: rtc_cmos 00:05: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
    May 01 16:01:14 arch kernel: Intel P-state driver initializing.
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 0
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 1
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 2
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 3
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 4
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 5
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 6
    May 01 16:01:14 arch kernel: Intel pstate controlling: cpu 7
    May 01 16:01:14 arch kernel: ledtrig-cpu: registered to indicate activity on CPUs
    May 01 16:01:14 arch kernel: TCP: cubic registered
    May 01 16:01:14 arch kernel: NET: Registered protocol family 10
    May 01 16:01:14 arch kernel: NET: Registered protocol family 17
    May 01 16:01:14 arch kernel: registered taskstats version 1
    May 01 16:01:14 arch kernel: Magic number: 14:512:29
    May 01 16:01:14 arch kernel: rtc_cmos 00:05: setting system clock to 2014-05-01 14:01:11 UTC (1398952871)
    May 01 16:01:14 arch kernel: PM: Hibernation image not present or could not be loaded.
    May 01 16:01:14 arch kernel: Freeing unused kernel memory: 1120K (ffffffff818d8000 - ffffffff819f0000)
    May 01 16:01:14 arch kernel: Write protecting the kernel read-only data: 8192k
    May 01 16:01:14 arch kernel: Freeing unused kernel memory: 904K (ffff88000151e000 - ffff880001600000)
    May 01 16:01:14 arch kernel: Freeing unused kernel memory: 416K (ffff880001798000 - ffff880001800000)
    May 01 16:01:14 arch kernel: random: systemd-tmpfile urandom read with 1 bits of entropy available
    May 01 16:01:14 arch systemd-udevd[77]: starting version 212
    May 01 16:01:14 arch kernel: i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    May 01 16:01:14 arch kernel: ACPI: bus type USB registered
    May 01 16:01:14 arch kernel: usbcore: registered new interface driver usbfs
    May 01 16:01:14 arch kernel: usbcore: registered new interface driver hub
    May 01 16:01:14 arch kernel: usbcore: registered new device driver usb
    May 01 16:01:14 arch kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controlle

    There are actually a couple of other topics about this issue. If you are looking for an answer as to what the problem is, then nobody seem to be able to provide an answer. Nvidia claim it is a bug in the kernel acpi calls, but have not been forthcoming to explain that further. There is a lengthy topic on nvidia forums.
    However, for a way to get things working again, read this topic: https://bbs.archlinux.org/viewtopic.php?id=180085

  • Care to play with grub2-graphical?

    UPDATES:
    November 2, 2009:
         1) Added a section to troubleshooting for flickering graphical menus
    October 28, 2009:
         1) Added a section to troubleshooting for failing to parse the block device
         2) Fixed a few outdated pieces and typos
    October 10, 2009:
         1) Added grub2-icons-circlestarts to AUR, a nice set of many different OS icons
             * It will be in the binary repos when I get the chance (and if I don't forget!)
    July 5, 2009:
         1) Troubleshooting section for an error reading /dev/fd0 nag and a small tip on the install section
    OVERVIEW:
    I've been working on (and succeeded in) getting Colin Bennett's code http://grub.gibibit.com/ to run in Arch. I hadn't seen it elsewhere, even from the major distros (except ubuntu's launchpad https://code.launchpad.net/~colinb/grub/gfxmenu ). I've only seen legacy grub wallpaper mods (grub-gfxboot) and animation patches (grub-gfxmenu, which the ubuntu2 theme and my hack theme mimic btw), not THIS grub2 mod. So, I figured I might as well try to get it working. The good news is, it appears to be slowly merging into the official grub2.
    Non-Arch distros: All of this can be done on a non-Arch distro in a similar way. Instead of using the given makepkg commands, you would need to manually handle dependencies listed in my PKGBUILD files (the right Ruby stuff is especially important; it will compile without ruby, but not correctly) and then use the typical "./configure; make; sudo make install" (or your distro's standard packaging method if you want to do that) on the source tarballs listed in the PKGBUILD source=() lines. If you have no idea what any of that jargon means, you should ask on your OS's forums and I'm sure someone will assist you. Non-Arch distros can also grab the theme tarballs from http://hateanthem.dreamhosters.com/arch/build/ and either extract them to /boot/grub/themes/ or package them for your OS if you can (I'm sure others will appreciate it). If you do so, you are welcome to send them to me if you wish and I can put them up on the same server as all of these files. For those of you on Ubuntu, to answer your question: no, Ubuntu's grub2 does not have gfxmenu capabilities yet. Either wait for it to be merged into grub2 or ask someone to package this for you (be sure to mention when you are asking however that grub2-gfxmenu is not the same as just grub, grub2, grub-gfx, grub-gfxboot, or grub-gfxmenu, as there is understandable confusion to the difference). As for troubleshooting, most of the troubleshooting here will also work on other distributions except for pacman commands, which you would need to deal with yourself accordingly (fyi, pacman -U installs a local Arch package; you would sudo make install or dpkg -i somePackage or rpm -i somePackage or whatever in your case).
    Below are the author's default themes (awesome!) and the quick Arch "concept theme" I made (crappy, but works; hence "concept"):
    [EDIT: I removed these screenshots from photobucket.. just see the author's page screenshots for a good idea]
    http://grub.gibibit.com/Themes
    INTRO NOTES:
    A [Assumptions]: This how-to assumes that you already know/have:
        1) Your hard drive device names/numbers (ie /dev/sdXY) for your /boot and / partition(s)
            * See /etc/fstab or the mount command and your grub.cfg/menu.lst
        2) GENERAL Arch Linux experience/knowledge for:
            * PKGBUILDS: http://wiki.archlinux.org/index.php/ABS … he_ABS_way
            * PACMAN: http://wiki.archlinux.org/index.php/Pacman
            * AUR: http://wiki.archlinux.org/index.php/AUR
            * YAOURT: http://wiki.archlinux.org/index.php/Yaourt
            * GRUB: http://wiki.archlinux.org/index.php/GRUB
            * GRUB2: http://wiki.archlinux.org/index.php/GRUB2
               * See your /boot/grub/grub.cfg or /boot/grub/menu.lst
    B [Miscellaneous]: Things you should know before starting:
        1) There are TWO pkgbuilds/packages needed: grub2-gfxmenu-overlay and grub2-gfxmenu
            * The former is mandatory themes, icons, etc. The latter is the grub2 patched with gfxmenu stuff
        2) Grub2's numbering/ordering is different than legacy grub's and, sometimes, your system's
            * Hard drives still start at 0, but partitions start from 1
            * For some, "/dev/sdb" is "hd0" in grub, counter-intuitively
        3) Only try this if you have time/patience/experience/knowledge to fix it
            * However, this is NOT as hard/long/tedious as it looks; I'm very thorough
            * Oh, and for whatever reason, this loads/works PAINFULLY slowly in VirtualBox
               * Don't bother outside of practice..
        4) VERY IMPORTANT: Old posts here use an outdated menuentry format!
            * It can crash grub2
            * NEW, CORRECT lines look like: menuentry "Arch Linux" --class "arch" {
            * OLD, INCORRECT lines look like: menuentry "Arch|class=linuxmint,linux,os" { 
               * Grub2-gfxmenu-bzr used this
            * Grub2-gfxmenu-bzr package is OLD. I use self-contained src pkgs the author provides now
               * Don't use that old stuff any more
    INSTALLATION & SPECIAL SETUP INFO:
    * Split Boot = Separate / and /boot partitions
    * If you're Split Boot, 64 Bit, LVM, some special setup, or confused/lost, see the respective areas before proceeding
    * You can skip Install Steps 1-7 if you use binaries or yaourt a'la Intro Notes A
       * If you have yaourt installed and ready, just yaourt -S grub2-gfxmenu and skip to step 8
       * If you want to use binaries in pacman, add to /etc/pacman.conf and pacman -Sy grub2-gfxmenu:
          * For 32 Bit:
             [archfox]                                                                               
             Server = http://hateanthem.dreamhosters.com/arch/i686
          * For 64 Bit:
             [archfox]                                                                               
             Server = http://hateanthem.dreamhosters.com/arch/x86_64
    Typical Installation (esp. 32 Bit Arch):
        1) See Intro Notes A & B
        2) Back up /boot/grub/grub.cfg, /boot/grub/menu.lst, or whatever you use
        3) Remove your bootloader via pacman -R [grub, grub2, whatever]
        4) Download the grub2-gfxmenu-overlay files:
            * http://aur.archlinux.org/packages/grub2 … u-overlay/
        5) Put them in $HOME/abs/local/grub2-gfxmenu-overlay
        6) Make and install the package via makepkg -c -i -s from that directory
        7) Repeat steps 4-6 for the grub2-gfxmenu files
            * http://aur.archlinux.org/packages/grub2 … 2-gfxmenu/
        8) As sudo/root, run: /sbin/grub-install /dev/sda
            * If you have multiple HD's, change this to the drive you want to boot grub from
        9) Edit /boot/grub/grub.cfg to match your partition setup (if necessary)
       10) Double check your work before rebooting
            * pacman -Qs grub2 should show grub2-gfxmenu-overlay AND grub2-gfxmenu [1-7]
            * ls /boot/grub should show a bunch of "mod" files [8]
            * be sure /boot/grub/grub.cfg points to the right partitions [9]
       :D) Finished!
            * The default themes have a pretty low res, and aren't as cool as some of the others
               * Make sure you have the proper gfxmode for your theme in grub.cfg if you use non-defaults
               * See the latter half of this tutorial for help and custom theme/icon stuff
    Installation on 64 Bit Arch:
        * FYI, I hear grub2 svn, and thus the next version of gfxmenu, adds native 64 bit support
        * For the least hassle, use binaries, then follow Typical Install #8-10:
           * The 64 bit binary repository info is above the Typical Install section
        * Alternatively, if you still want to COMPILE this with makepkg.. [Steps 1-7]
           * You'll need either a 32 bit chroot/environment..
              * http://wiki.archlinux.org/index.php/Arc … _Arch64.3F
           * .. or you can use a regular 32 bit install
           * Either way, change DESTARCH in the pkgbuild to x86_64
        * Further help: Shaika-dzari's posts in this thread may be useful, but using his "-bzr" files is not advised!
           * His syntax and grub2-gfxmenu-bzr are OLD; the former can crash new Grub2! (See Intro Notes B #4)
           * If you're determined to use his -bzr, use the old syntax! If you use the new pkgs, don't use his syntax!
    Notes for a Split Boot, LVM, maybe RAID:
        * All of these users will likely need a similar grub.cfg
           * Example Split Boot cfgs in Troubleshooting and later in this thread
        * You will likely run into multiple problems listed under Troubleshooting; relax and expect it
           * You might spare yourself problems by following Troubleshooting #6 before rebooting
              * ... or cause problems you might not have had! Probably prevent 'em, though :)
        * Split Booters: if that doesn't help, try looking at boriscougar's posts here
           * His syntax is outdated and will crash Grub2, however! (See Intro Notes B #4)
        * LVM/RAIDers:
           * You need the kernel root= parts pointing to /dev/mapper/blahblah
           * See lssjbrolli's posts here, esp. #19, for other grub.cfgs IF you have trouble
              * His syntax is outdated and will crash Grub2, however! (See Intro Notes B #4)
    Notes for Others:
        * If you are lost/confused, please post here
        * If you have another "special case", I'm afraid I probably can't help you
           * You are welcome to try anyway and report your results; it might help someone else
    TROUBLESHOOTING:
    * Check ALL of the instructions and the Intro Notes A & B again
    * Press 't' in graphical mode to switch to text mode, it's more forgiving with errors
    * Press 'e' in text mode to edit an entry. Useful key combinations are shown there
    * See post #78 or #63 for starting over from the Live CD; modify it to restore legacy grub
       * Be sure your device node/name is correct, as per the Intro Notes
    * Here is an example Split Boot grub.cfg menuentry with descriptions:
       # Entry 0 - Arch Linux                                           
       menuentry "Arch Linux" --class "arch" {
           # Below should be /boot, where the kernel/initrd/bootloader is. Here, it's HD 1, Partition 5 
           set root=(hd0,5)
           # Below is /, where most of your installation is. HD 1, partition 6
           # Note the backwards drive lettering/order on my pc!
           # Grub calls my drive "hd0" while Arch labels the drive "/dev/sdb"
           # Yours MAY or MAY NOT do that
           # Also note, BECAUSE this is for a Split Boot, there is no /boot prefix
           # Lastly, some distros seem to fail with /dev/disk/by-label entries, others work fine
           linux /vmlinuz26 root=/dev/sdb6 ro
           initrd /kernel26.img
    1) During grub-install, you get a nag about not being able to read /boot/grub/core.img
        * I think this is fixed in a grub2 svn release, so hopefully the next grub2-gfxmenu will remove this section..
        * Two methods.. both are hackish, but either 'works'.. I prefer Method 2, but it's more work + empty space..
        * METHOD #1:
           * This installs grub to your root partition instead of /boot (method obviously assumes a Split Boot):
              * It will obviously not properly coincide with pacman installs/updates of grub2-gfxmenu stuff normally
                 * You can unmount /boot to upgrade/install grub2-gfxmenu stuff for now with pacman
                 * Re-mount /boot when you're done installing/upgrading said grub2-gfxmenu stuff
                 * If grub2-gfxmenu is updated, try installing again normally WITH /boot mounted first
              * Your old grub folder is still on your /boot partition; I think it may be moved to avoid confusion
              * If you move/remove the grub partition on ROOT (until properly installed of course), grub will break
           1) mkdir /mnt/tmp
           2) umount /dev/sda1 (assuming your /boot is sda1 of course from here)
           3) mount /dev/sda1 /mnt/tmp
           4) cp -r /mnt/tmp/grub /boot
           5) Check ls /boot/grub shows the expected mod files and such, then try /sbin/grub-install /dev/sda again
           6) Edit /boot/grub/grub.cfg before you reboot; follow the tutorial otherwise
           7) Be sure to re-mount /boot if you're not going to reboot after this tutorial / installing gfxmenu stuff
        * METHOD #2:
           * This installs grub2-gfxmenu "correctly", but puts a little empty space in front of your /boot partition
           1) Boot into a LiveCD and resize your /boot partition; graphically (gparted) or CLI if you know how
               * I decreased its size by 10 megs, which is likely MAJOR overkill, but it worked, and I can spare 10mb
           2) Move the resized partition to the right, so the space you freed up is in front of it
           3) Boot into the Arch LiveCD if you aren't there already, and go root
           4) mkdir /mnt/root
           5) mount /dev/sda3 /mnt/root (assuming sda3 is your root partition)
           6) mount -t proc proc /mnt/root/proc
           7) mount -t sysfs sys /mnt/root/sys
           8) mount -o bind /dev /mnt/root/dev
           9) chroot /mnt/root /bin/bash
          10) mount /dev/sda1 /boot   (assuming sda1 is /boot.. you can mount /home now too, if needed)
          11) pacman -U /path/to/grub2-gfxmenu*pkg.tar.gz (only if its the only grub2-gfxmenu pkg there)
          12) pacman -U /path/to/kernel26*pkg.tar.gz (only if its the only kernel pkg there)
          13) Edit /boot/grub/grub.cfg before you reboot; follow the tutorial otherwise
    2) During grub-install, you get a nag about /dev/fd0 or something of the sort
        * Your device map is wrong; edit /boot/grub/device.map accordingly and remove/edit such incorrect entries
           * You may also need to run grub-mkdevicemap BEFORE doing this, but probably not
           * Fd0 is the floppy disk, remove it if you don't actually have such a drive
        * Alternatively, try adding --recheck to the grub-install /dev/yourDevice command
    3) The text menu won't load, and you're dropped to a limited prompt
        * Check that you are using the new/correct grub2-gfxmenu menuentry format (See Intro Notes B #4)
        * You may have run the command incorrectly (or not at all) in Step 8, or your /boot changed numbers/letters
           * You would probably need to start over from a livecd, if so
    4) The graphical menu won't load, but the text one does
        * Check that stuff exists in /boot/grub/themes
        * Check that your set theme= line is properly suited to your system in grub.cfg:
           * Most people need: set theme="/boot/grub/themes/themeName"
           * A Split Boot / LVM / RAID / etc needs: set theme="/grub/themes/themeName/theme.txt"
        * Split Boots / LVM/ RAID/ etc should check that set root= exists near the top and points to /boot
    5) The graphical menu loads, but you have boxes/squares where fonts should be
        * Add this (set to match YOUR /boot) somewhere near the TOP of your grub.cfg:
           * set root=(hd0,5)
        * Your loadfont lines ALL probably need to look like this (no /boot prefix):
           * loadfont /grub/fonts/10x20.pf2
           * This command with sudo/root permissions should be able to do it for you (make a backup!):
              * cd /boot/grub/ && sed -i 's|/boot||g' grub.cfg
              * This -could- affect (good or bad) other things. Fix if needed, before or after rebooting
    6) The graphical menu loads, but when you select the os, it sits at "Press any key to continue"
        * Check that grub.cfg's "set root=" line you have for that menuentry points to /boot
           * Grub numbering has changed in grub2 (See Intro Notes B #2)
           * Try [inc/dec]rementing the [drive/partition] by 1 number/letter
           * Remove /boot from the front of stuff if you are running a Split Boot / LVM / RAID / etc
    7) The graphical menu loads, but you get a nag about a failure to parse the block device
        * Check all of the other troubleshooting first to see if it applies / works first
        * Check that your kernel/initrd lines point to the correct places (remember partitions start from 1 now!)
        * Check /etc/mkinitcpio.conf for hooks you no longer use (like fbsplash perhaps)
           * Packages used by your hooks must be installed, like fbsplash for the fbsplash hook
    8) The graphical menu loads, but you get a nag about finding root / init not found, or a similar error
        * Check that grub.cfg is pointing to the right place in that menuentry's "linux" and "initrd" lines
           * Grub numbering has changed in grub2 (See Intro Notes B #2)
           * Try [inc/dec]rementing the [drive/partition] by 1 number/letter
           * Remove /boot from the front if you are running a Split Boot / LVM / RAID / etc
        * Try running the fallback/failsafe entry
           * If it works, you need to mkinitcpio -p kernel26 from there
    9) The graphical menu loads, but flickers horribly
        * Try changing the resolution, perhaps to a default/1024x768
    10) You're on an eeePC or use an intel 800/900 graphics chipset and can't use your native resolution
        * NOTE: I've had reports that this no longer works or compiles or something recently, so YMMV
        * Workaround until someone tries patching and reporting via grub2-915resolution's patch(es):
           1) Compile (NOT install!) grub2-915resolution from AUR via makepkg (or yaourt and cancelling)
               * Or grab 915resolution.mod from someone/somewhere else, perhaps
           2) Install grub2-gfxmenu
           3) Copy 915resolution.mod from step 1's MAIN source directory to /boot/grub/
               * If you used yaourt and cancelled before installing, try /tmp/yaourt-tmp-yourname
           4) Insert/change the following in grub.cfg [order matters I guess?]:
               * insmod 915resolution
               * 915resolution 34 1024 600 (or whatever else you want)
               * set gfxmode 1024x600 (or whatever else you want)
           5) Edit your theme's theme.txt file to look nice on the new res, if it's not already made for it
    TWEAKING:
    1) Changing the resolution
        * Edit /boot/grub/grub.cfg, it's one of the first lines (set gfxmode=)
           * I'm not sure what it supports, but I got up to 1280x1024 without problems
           * You may need to change your theme's configuration file for it to look decent under a new res
    2) Changing the theme
        * Edit /boot/grub/grub.cfg, it's one of the earlier lines (set theme=)
        * Themes are in /boot/grub/themes
    3) Changing the icons (Thanks to kholddagger post #97)
        * /boot/grub/themes/icons , seemingly PNG only, scaled according to theme/resolution in use
        * Add your OS icon by changing the --class option in your menuentry to MATCH the .png
           * Ie, for /boot/grub/themes/icons/fedora.png:
              * menuentry "Fedora Linux" --class "fedora" {
           * Don't like a default icon, but don't want them overwritten by updates?
              * Make it "distro2". Ie distro2.png and --class "distro2"
        * I am partial to http://gnome-look.org/content/show.php/ … tent=95970 "Circle Starts"
    4) Adding new distros
        * See Tweaking #3 for changing/adding icons
        * Clone Arch's menuentry and tweak it to match your other OS
           * Search your other OS's /boot folder/partition for kernel and init filenames
    5) Advanced theme tweaking
        * See the author's website and documentation:
           * http://grub.gibibit.com/Theme_format
           * http://grub.gibibit.com/gfxmenu_design
    6) Advanced font tweaking
        * See the author's website and documentation:
           * http://grub.gibibit.com/New_font_format
           * The newest version "supports UTF-8 fonts", but I'm not sure what that even means :D
    KNOWN AVAILABLE THEMES:
    * All custom themes so far are set up for 1024x768 and the defaults for 640x480
       * Most of them are made by Xabz, and packaged by me
       * If you have alternate resolution layouts for any of them, PLEASE share!
    * If you make any new ones, PLEASE share! :)
    1) The first two screenshots are defaults
    2) The third blue screenshot is my theme, aftermathblue (previously archfox), a tweak of the defaults
        * It has since been updated to 0.2 and looks a little different; certainly much less hackish
        * The name refers to the wallpaper "Aftermath" from the arch linux wallpapers package, turned blue.
        * The screenshot's icons are tweaked Google Images results for "windows icon" and "arch linux icon"
        * If you have suggestions, post 'em
    3) There are several really nice ones made by a guy in Chile named "xabz":
        * See above "Typical Install" for binary repositories containing these theme packages
           * You can also find them in the AUR; they are prefixed with "grub2-theme-"
        * You can see screenshots of them on page 4 of this thread, post #94
    4) There is another awesome one here by some presumably German person:
        * http://forum.ubuntuusers.de/topic/grub2 … st-1835914
        * I can't seem to find a download link for it, only a picture :(
    Last edited by FrozenFox (2010-04-01 16:41:21)

    set gfxmode=1024x768
    insmod ext2
    insmod biosdisk
    insmod pc
    insmod font
    insmod vbe
    insmod gfxterm
    insmod videotest
    insmod tga
    insmod png
    insmod gfxmenu
    #set menuviewer="terminal"
    set menuviewer="gfxmenu"
    set theme="/grub/themes/ubuntu2/theme.txt"
    #set theme="/boot/grub/themes/ubuntu1/theme.txt"
    #set theme="/boot/grub/themes/winter/theme.txt"
    #set theme="/boot/grub/themes/proto/theme.txt"
    # TODO: fix GRUB script parser -- it doesn't handle a space at the end of the line in a menu entry.
    #### BEGIN MENU ####
    set timeout=8
    set default="0"
    set fallback="0 1"
    menuentry "Arch Linux|class=ubuntu,linux,os" {
    linux /vmlinuz26 root=/dev/mapper/volgroup0-lvolroot ro quiet
    initrd /kernel26.img
    menuentry "Arch Linux Fallback|class=linuxmint,linux,os" {
    set root=(hd0,1)
    linux /vmlinuz26 root=/dev/mapper/volgroup0-lvolroot ro
    initrd /kernel26-fallback.img
    menuentry "Bitmap graphics test" {
    videotest -d bitmaps
    #### END MENU ####
    # Choose the font for gfxterm.
    set gfxterm_font="smoothansi"
    # Load fonts.
    # Generated with:
    # ls *.pf2 | perl -pe 's{^}{loadfont /boot/grub/fonts/}'
    loadfont /grub/fonts/10x20.pf2
    loadfont /grub/fonts/4x6.pf2
    loadfont /grub/fonts/5x7.pf2
    loadfont /grub/fonts/5x8.pf2
    loadfont /grub/fonts/6x10.pf2
    loadfont /grub/fonts/6x12.pf2
    loadfont /grub/fonts/6x13.pf2
    loadfont /grub/fonts/6x13B.pf2
    loadfont /grub/fonts/6x13O.pf2
    loadfont /grub/fonts/6x9.pf2
    loadfont /grub/fonts/7x13.pf2
    loadfont /grub/fonts/7x13B.pf2
    loadfont /grub/fonts/7x13O.pf2
    loadfont /grub/fonts/7x14.pf2
    loadfont /grub/fonts/7x14B.pf2
    loadfont /grub/fonts/8x13.pf2
    loadfont /grub/fonts/8x13B.pf2
    loadfont /grub/fonts/8x13O.pf2
    loadfont /grub/fonts/9x15.pf2
    loadfont /grub/fonts/9x15B.pf2
    loadfont /grub/fonts/9x18.pf2
    loadfont /grub/fonts/9x18B.pf2
    loadfont /grub/fonts/Helvetica-10.pf2
    loadfont /grub/fonts/Helvetica-12.pf2
    loadfont /grub/fonts/Helvetica-14.pf2
    loadfont /grub/fonts/Helvetica-18.pf2
    loadfont /grub/fonts/Helvetica-24.pf2
    loadfont /grub/fonts/Helvetica-8.pf2
    loadfont /grub/fonts/Helvetica-Bold-10.pf2
    loadfont /grub/fonts/Helvetica-Bold-12.pf2
    loadfont /grub/fonts/Helvetica-Bold-14.pf2
    loadfont /grub/fonts/Helvetica-Bold-18.pf2
    loadfont /grub/fonts/Helvetica-Bold-24.pf2
    loadfont /grub/fonts/Helvetica-Bold-8.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-10.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-12.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-14.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-18.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-24.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-8.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-Bold-10.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-Bold-12.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-Bold-14.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-Bold-18.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-Bold-24.pf2
    loadfont /grub/fonts/New_Century_Schoolbook-Bold-8.pf2
    loadfont /grub/fonts/anorexia.pf2
    loadfont /grub/fonts/aqui.pf2
    loadfont /grub/fonts/clR6x12.pf2
    loadfont /grub/fonts/cure.pf2
    loadfont /grub/fonts/drift.pf2
    loadfont /grub/fonts/edges.pf2
    loadfont /grub/fonts/fkp.pf2
    loadfont /grub/fonts/gelly.pf2
    loadfont /grub/fonts/glisp-bold.pf2
    loadfont /grub/fonts/glisp.pf2
    loadfont /grub/fonts/helvR12.pf2
    loadfont /grub/fonts/kates.pf2
    loadfont /grub/fonts/lime.pf2
    loadfont /grub/fonts/mints-mild.pf2
    loadfont /grub/fonts/mints-strong.pf2
    loadfont /grub/fonts/nu.pf2
    loadfont /grub/fonts/smoothansi.pf2
    loadfont /grub/fonts/snap.pf2
    i use 2 hdd. From the first hdd i use a 100MB for /boot with ext2 -> set root=(hd0,1) <- ,
    and the rest from the first hdd and the second is used in a LVM configuration with 2 partitions lvolhome and lvolroot -> root=/dev/mapper/volgroup0-lvolroot <-
    and my fstab
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    #/dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0
    #/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    /dev/mapper/volgroup0-lvolhome /home ext3 defaults,noatime 0 1
    /dev/mapper/volgroup0-lvolroot / ext3 defaults,noatime 0 1
    UUID=1c16c6e9-1459-4547-a4ab-04b8f45daca6 /boot ext2 defaults,noatime 0 1
    UUID=bf143434-eb96-4155-9339-5b83521520d7 swap swap defaults,noatime 0 0

  • A few small issues I can't find fixes for

    Hi everyone, I've been using arch for a little bit now and really enjoying the experience. I have run across 3 small problems and other than that everything thing seems to be running flawlessly. I'd appreciate any help with these, and thanks in advance. I have googled trying to find solutions and searched the wiki but either none of the issues were listed or the fixes for them didn't seem to have an effect, but if I missed something sorry, just if you want to point me in the right direction that'd be appreciated.
    So some specifics about my system first, I'm running on arch linux 64bit using KDE as my desktop environment.
    Okay so problem number 1:
    Sometimes when arch goes to boot it fails to mount /dev/sda2 which is my root partition, This doesn't happen everytime but I'd say 50 or 60 percent of the time, but when it does I give it a restart once or twice and it loads into arch just fine. I can restart my computer if anyone wants the exact wording I get, but it goes along the lines of "failed to mount /dev/sda2 you are now being dropped in to a recovery shell" Now I'm not sure but this might be because of the weird way I set the harddrive partitions up, but it worked in all the distros I used before settling on arch, but to give you an idea, I'm using 2 300gb hard drives, I have them split so that 1 hard drive is completely devoted to my / and /boot partitions, the other one has /usr /tmp /var and swap on it. In addition I have a 1tb drive for storage that is devoted to /home. If it is causing the problem and I have to reformat and go to a more conventional partition scheme I will, but I'd prefer to avoid that if at all possible, just because I am rather settled in to this install.
    Problem number 2:
    Amarok takes forever and a day to load, somewhere in the area of 60+ seconds, when I start it via the terminal I get this output:
    KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
    (amarok:19322): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed
    amarok(19322)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
    amarok(19322)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
    amarok(19322)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
    amarok(19322)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
    amarok(19322)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
    amarok(19322)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
    amarok(19322)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
    amarok(19322)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
    amarok(19322)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
    amarok(19322)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers for "Amarok Script Console"
    amarok(19322)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers for "LyricWiki"
    amarok(19322)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers for "Cool Streams"
    amarok(19322)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers for "Librivox.org"
    ** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: **
    ** amarok --debug                                                                           **
    I thought maybe it was the gstreamer backend because the wiki said it might cause problems and to try using xine instead. However doing this didn't seem to help at all.
    Problem number 3
    Flash is all weird when I use Kwin, when I use compiz it works near flawlessly but my issue with that is then kde doesn't act nearly as smooth as it does without compiz. When I use flashplugin from the repos I can't go fullscreen because it makes everything freeze up, and when I try flashplugin-prerelease from the aur flash is always in the spot where it loaded meaning if I change tabs in firefox it goes through the other tab and if I scroll it stays stationary and everything else scrolls behind it.
    Again I apologize if I missed it in the searches that I ran and these have been solved elsewhere, but thanks in advance for all help given.
    Edit: Installing pulseaudio and using that instead of alsa seems to have fixed amarok starting slowly.
    Last edited by Sinner (2011-03-26 05:05:57)

    milomouse wrote:Maybe you should use UUIDs instead of /dev/sd* to avoid any possible device confusion (type 'blkid' to see your UUIDs), though from your first post about "cannot mount /dev/sda2" it still appears to check for root device correctly.  At any rate, in your grub or lilo or syslinux (whatever bootloader you have) config you could also change root=/dev/sda2 to root=/dev/disk/by-uuid/YOURROOTUUID (however your bootloader can handle it) to help further reduce possible errors.  (helpful link: https://wiki.archlinux.org/index.php/Pe … ice_naming )  Trying to think of what else it could be since it only happens every now and then, which is a little strange.
    Oh my bad I forgot to say I'm using grub, but yeah I went through and did that, That seemed to stop me being loaded into a recovery shell or whatever, but when arch started to boot about 2 out of the 5 times I restarted to test it, it said file systems didn't check and had my log in as root to try to remount the partition. Also I got a COMERROR=-32 after which it said it was doing a comreset and would retry in 8 seconds after doing that 3 times it booted almost every time unless it ran into the filesystem check.
    Last edited by Sinner (2011-03-25 16:29:32)

  • Partitioning travels (and Happy Birthday to me!)

    Next to my avatar, I note that I signed up here 5 years ago today. Not as long as I've been sober,    but still a milestone. I'm quite sure my first Arch install was 0.4...'Voodoo'? The first Linux distro I touched that showed promise of one day "being ready for prime time" - I'm glad I waited for it!
    So, this is a 'slightly' off-topic post (but still quite 'on-topic'), and if the powers that be choose to move it; so be it. No skin off my back. This is (IICC) my 89th post in 5 years. Over the years I've made a couple of gaffes, and found more than a couple of bugs (my 'weird' partitioning schemes, outlined below, may test parts of software that most people don't, I don't know).
    But overall, I'm pretty quiet. I sometimes wait longer than I should for bugs I find annoying to be fixed, but they almost always are, without my involvement, and often as quickly as I could get a "round tuit" filling out a bug report! My own experience has been that unless I think I've found something substantial, early (which I've sortof done twice in the past two days), I don't report it. And if I do, I report it here. It usually shows up in days, if not hours, anyway. Just my experience.
    Anyway, I started checking out a (small number of) distros a few months back, plus I've been piddling with Arch x86_64 installs, so I've been dual-booting (between 32- and 64-bit Arch) even when I only have Arch on the machine! But I've had as many as 5 (Arch 32- and 64-bit, DistroU 32- and 64-bit, and DistroD WTF remembers how many bits it was now).
    For a good while (several years, in some form), I've had a partitioning scheme which I've never seen replicated in any tutorials on the subject, but which I find quite flexible and useful.
    I have several "non-mainstream" methods for handling multi-booting. Feel free to pick and choose anyhing you find useful, free as in beer and free (of) as in warranty, of course. 
    swap belongs on the fastest part of the drive; usually if not always the very beginning (outside) of the drive - IF you only have one installation. In this case, making a 1 GB swap, a  /  of your choice, size-wise, followed by (if you choose) a /home partition that takes the rest of the drive, saving a chunk at the end (40-80 MB) for /boot.
    To do this, when partitioning a new drive, 1st create a 1-2 GB primary ('xdy1'; x='s' or 'h', y='a-z'), for swap. Next, create a 2nd *primary* right behind, physically, xdy1 ('sda1'), xdy2, for  /  . Whatever you need, size-wize, 4-60 GB, I guess...
    NOW, depending on with *fdisk/gparted/whatever you're using, ether create your extended partition (if using an fdisk variant that will let you leave some space at the end); leave 40-80 MB free. Otherwise, create the extended partition first, and leave the last 40-80 MB unused. You should then be able (very likely after a reboot) to re-run *fdisk and create the final primary partition out of that chunk at the end. Your extended partition would've taken xdy3, so the chunk at the end is xdy4 - a *primary* partition.
    You can use this puppy for /boot; /boot BELONGS on the slowest part of the drive. It's very rarely accessed after sysinit. This setup offers 2 advantages: while no BIOS capable of running a 686-optimized Linux system limits you to the first 1024 'cylinders' (sic), some DO require the /boot partition to be on a primary partition. This IS a primary partition. Furthermore, if permanently placed at the end of the drive as a logical partition, every time you added or re-arranged your partitions, it's partition number would most likely change (the partition ID of your BOOT drive - yeah, yeah, I know, UUID's...). With it stuck like glue to 'sda4', it ain't going anywhere, regardless of how (or how many!    ) times you reorganize the extended partition (which is where.I tend to do most of my 'playing').
    You can then use the entire extended partition for /home, if you wish, or carve it up however you like. More on this below.
    When multi-booting, I've found ("developed"???) a sightly more sophisticated set of arrangements that seem to work well together (WHY RedHat didn't think of this in 1996 - it would be a de facto standard today! - I have NO idea...)
    Normally, distros want to install a vmlinuz26, and and a kernel26.img  (and maybe a fallback image, and a config26.gz, and a System.map file), into /boot/. A lot of my older (and some of my newer) machines required bootable partitions to be on a *primary* partition. Install 5 distros like *that*.
    Actually, it's QUITE easy:
    Note: I have a larger-than-normal (for ME) /boot partition (96 MB - and 64 would likely be adequate for 3 distros), but the reason is obvious, and IMX most people have /boot WAY too big, anyway. Right now I have 2 distros loaded (Arch 32- and 64-bit), current and former kernels are both retained for each distro - ie, 4 complete sets of kernels. My 96 MB partition is 32% full.
    For our multi-boot environment,  xdy1 ('sda1') is actually a large (60 GB or so) LVM volume. 'sda2' becomes the extended volume, and 'sda3' is the 40-80 GB /boot volume at the end of the drive. We have the entire extended partition to use *outside* LVM. I generally use a VERY large 'chunk' size in LVM (like 256 MB!), and try to set it up, roughly, as such (on a 250 GB = 236 GB drive):
    sda1 P LVM 64 GB
    sda2 E extended ?
    sda5 L logical ?
    sda4 P /ext2+++ 64 MB
    +++ there is ZERO reason to make a /boot partition ext3 and incur the substantial overhead of a 32 MB journal on a 60-100 MB filesytem! The system runs BEAUTIFULLY with boot mounted ro - that's my normal MO, in fact. I can always remount it rw on the rare occasions I need to update something.
    Rather than using dev-mapper's long naming conventions, I create a Volume Group called vg, and Logical volumes called, say, ar and ah and such:
    ah 4 GB # arch32 /home
    ar 8 GB # arch32 / (root)
    sw 1 GB # swap (shared)
    sd 3 GB # data partition shared between all O/S's on the machine (if desired...).
    br 8 GB # arch64 / (root)
    bh 4 GB # arch64 /home
    You can add more lv's to install additional O/S'es.
    You are NOT forced, in either fstab, GRUB, OR LILO, into using the 40-character-long "dev/dev-mapper/vg01/dm-01" syntax; from above, "dev/vg/at" works great, and reasonably resembles your other partition ID's. 
    Note that no matter HOW many O/S'es we install, we only use ONE /boot partition! I might have to go to a 128 MB or 256 MB partition. 
    While I normally have fstab mount /boot ro, it's easy, of course, to remount it rw on the fly. Since all distros SHARE the same /boot (normally only mounted ro by all concerned), if one distro borks it's grub entries or installs a REALLY crappy kernel, it's quite easy to get to the file in question from another O/S!
    I first installed Arch i686 on this machine (AMD64 XP3500+). I then created a directory at /boot/arch32. I copied (*copied*, NOT moved) all the loose files from the /boot directory (vm*, kern*, Sys* in arch's case) into the /boot/arch32 directory. I then update /boot/grub/menu.lst, replicating all it's primary entries as new options to select, with '/boot/vmlinuz26' becoming '/boot/arch32/linuz26', etc. These come BEFORE the original selections. I leave the loose files in /boot alone; they aren't hurting anything, and, who knows...
    Reboot choosing the 'normal' option (not 'safe'). If the system boots correctly, I leave the 'fall-back' option from the original Arch install as the LAST entry in grub (it's literally the 'last shot', anyway...). Theoretically, it should pick up these 'loose' files, were it to come to that.
    Now, whenever Arch updates the kernel, it (wisely) doesn't do a bunch of checking in /boot/grub/menu.lst or check what files are in /boot; it simply recompiles a full set of files and slaps them into /boot. All I have to do when there is the occasional kernel update is:
    cd /boot
    rm -rf arch32old
    mv arch32 arch32old
    mkdir arch32
    cp vm* kern* Sys* arch32/
    All is ready to go. The next boot will RUN the kernel from the /boot/arch32 directory.
    That's pretty quick-n-easy considering Kernel updates don't NORMALLY (cough cough) come out that often.
    One could even create GRUB entries for the arch32old (and arch64 old) kernels! (easily, basically cut-n-paste w/minor replacements/substitutions). You could have a GRUB menu that takes the entire screen!
    We can now install Arch x86_64, and any other distros that recognize LVM2 and play nice with other distros.
    One last thing I do: in the extended partition (preferably near the end of the drive) I set up 8 GB partitions as ext2, -b4096, -m0, -N16384 (-N65536?). I use these for the /var/cache/pacman in Arch, but other distros have similar (it not as ready for prime time!) arrangements and needs; the routine seems to wear well; I've had at least some of my now-system disk (250 GB) working like this for a good 3 years (including some REALLY substantial, solo, all-night Linux install parties!    ). My current x86_64 install, which is what I'm using now, is a fresh install, but it's not really any faster than a month's-old Arch32 install on the same computer.
    Sorry for the tome. It's my birthday and I'll write if I want to...
    Yes, I know this post is timestamped the day after, but I assure you I started this before midnight! 
    I have no intention of "graduating from" Arch i686. I fully intend to keep both on my system (at a MINIMUM) - if one install gets borked, you can get to it fairly easily from another install on the same machine (of something DIFFERENT - I make sure to update a new kernel to one system for a week before updating the other.
    A single /boot partition for a dozen distros, with a relatively easy (straight-forward, at least) and painless method for handling kernel updates from multiple distros on one machine....shared swapspace...shared storage...
    On the rare chance that someone (a) is still reading, and (b) feels this is a rational start of a Wiki page, I'm willing to maintain...
    Blue Skies...Keith/grndrush
    Last edited by grndrush (2009-01-05 05:30:51)

    Thanks to you both.
    As to the 1024 cylinder limit, again, I think there are very few remaining out there in operation (*I'll* never have one, LOL) with the 1024-cylinder problem, but I HAVE had a few problems with relatively recent (in 'my' terms, which means ancient) hardware where Linux doesn't want to boot using a *logical* partition for /boot - hence the homegrown workaround to get /boot at the end of the disk. You're 100% right - today, it's not worth the time or hassle of doing so. I simply thought like this since BEFORE the days of 20 MB HD's!  .
    Thanks again. Five years using Linux doesn't seem *nearly* as long as five years running Windows (although it DOES seem like a good 5 years since I've used Windows voluntarily). And, of course, these ARE faster machines... 

Maybe you are looking for