[SOLVED] mkinitcpio stalled at [autodetect]

I just updated from linux 3.2.2-1 to 3.2.5-1, and mkinitcpio hangs on "Parsing hook: [autodetect]". I have (maybe unwisely) tried killing it and starting it again manually, but have encountered the same problem again.
What should I do? I don't want to end up with an unbootable system...
Last edited by ulke (2012-02-11 20:50:03)

Thanks for your replies, and sorry for not providing more information. I just did not know what might be helpful.
The mkinitcpio.conf diff:
7c7
< MODULES="i915"
> MODULES=""
51,53c51,53
< ## This setup assembles a pata raid array with an encrypted root FS.
< ## Note: See 'mkinitcpio -H raid' for more information on raid devices.
< # HOOKS="base udev pata raid encrypt filesystems"
> ## This setup assembles a pata mdadm array with an encrypted root FS.
> ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
> # HOOKS="base udev pata mdadm encrypt filesystems"
57c57
< HOOKS="base udev autodetect pata scsi sata keymap encrypt lvm2 filesystems resume"
> HOOKS="base udev autodetect pata scsi sata filesystems usbinput"
67a68
> #COMPRESSION="lzop"
The mkinitcpio log is here. Note that just running mkinitcpio without arguments did not work:
# mkinitcpio
==> ERROR: '/lib/modules/3.2.2-1-ARCH/' is not a valid kernel module directory
So I ran this instead (when generating the log):
mkinitcpio -g /boot/initramfs-linux.img -k 3.2.5-1-ARCH
Edited for clarity.
Last edited by ulke (2012-02-10 20:37:02)

Similar Messages

[SOLVED] [mkinitcpio] initramfs "build error" messages since v.18-1

Hi everybody,
Since the update from mkinitcpio 17-1 to 18-1 I get those build error messages while running mkinitcpio:
# mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.15.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
-> Running build hook: [lvm2]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.15.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
-> Running build hook: [lvm2]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
However I can still boot and everything seems mostly fine. I haven't changed anything to my /etc/mkinitcpio.conf, here are the only customized parts:
MODULES="i915 dm_snapshot"
HOOKS="base udev autodetect modconf block keymap encrypt lvm2 filesystems keyboard fsck
I'm using an encrypted root (ext4 over LVM over LUKS) and boot partition is contained in an (unencrypted) LVM logical volume. I also specify a few i915 module options in an /etc/modprobe.d/modprobe.conf file as per the Intel Graphics wiki page:
# Intel graphics driver power-saving option :
options i915 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
Never had any such warnings before, but now it appears each and every time I update or reinstall my kernel (the default one). I went through Mkinitcpio wiki page, tried putting question marks after the listed modules and rebuilding but it didn't change anything... Any ideas?
Btw, I don't use any specific compression option and had the regular lzo name change during the same full system upgrade that updated mkinitcpio and linux.
Thanks
Last edited by Neitsab (2014-08-04 11:51:19)

Yes indeed, removing /etc/modprobe.d/modprobe.conf~ hidden backup file solved the warning issue. Strange but thanks ukhippo, I hadn't thought about checking other subforums!
Last edited by Neitsab (2014-08-04 11:52:08)

[SOLVED] mkinitcpio error during kernel 2.6.37-6 package upgrade

After upgrading to kernel26-2.6.37-6-x86_64, I failed after reboot (couldn't mount root and got dropped to the "you're on your own" prompt). Fortunately, the fallback kernel worked. I didn't look into it at the time (it was late), and I noticed a new kernel package the next day, so I updated again thinking maybe it was a bug that got fixed. Nope. Same problem after reboot, but I paid a little more attention this time and saw the errors below:
sudo pacman -U kernel26-2.6.37.1-1-x86_64.pkg.tar.xz
...snip...
checking package integrity...
(1/1) checking for file conflicts [######################] 100%
(1/1) upgrading kernel26 [######################] 100%
>>> Updating module dependencies. Please wait ...
...snip...
==> Running command: /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
...snip...
:: Generating module dependencies
WARNING: Can't read module /tmp/mkinitcpio.WLY5Kx/lib/modules/2.6.37-ARCH/kernel/drivers/ata/pata_acpi.ko.gz: Exec format error
WARNING: Can't read module /tmp/mkinitcpio.WLY5Kx/lib/modules/2.6.37-ARCH/kernel/lib/libcrc32c.ko.gz: Exec format error
WARNING: Can't read module /tmp/mkinitcpio.WLY5Kx/lib/modules/2.6.37-ARCH/kernel/crypto/crc32c.ko.gz: Exec format error
WARNING: Can't read module /tmp/mkinitcpio.WLY5Kx/lib/modules/2.6.37-ARCH/kernel/arch/x86/crypto/crc32c-intel.ko.gz: Exec format error
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
Since my root partition is btrfs, I require the libcrc32c module on load, and it looks like mkinitcpio couldn't manage to get it (and a few other modules) into my initrd. So I ran:
sudo /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
again by hand, and it worked without errors. (Yeah, I'm a sudo person, in case you were wondering.)
Here are the relevant /etc/mkinitcpio.conf lines:
MODULES="dm_mod dm_mirror btrfs crc32c libcrc32c"
HOOKS="base udev autodetect pata scsi sata dmraid lvm2 filesystems"
I don't know squat about mkinitcpio and why it would work fine when run by hand but choke when run via pacman. Anyone have any ideas?
Last edited by archix (2011-02-21 18:35:46)

According to Ryan Hill's comment on http://bugs.gentoo.org/show_bug.cgi?id=353907#c16 which is sending us to http://lwn.net/Articles/429345/ - it looks like ext4 is also impacted by this bug, not only compressed btrfs!
Chris Mason from Oracle (funny, "magical" coincidence ;P ) said he's got a patch for btrfs and hes testing it. Hope to see it soon...
Edit: ahhh here it is http://www.mail-archive.com/linux-btrfs … 08577.html
Edit2: patches were merged with today's (26.02.2011) mainline kernel snapshot: 2.6.38-rc6-git6
it seems to work fine for me, so i guess it's [SOLVED] now
Last edited by Vi0L0 (2011-02-26 15:51:46)

[SOLVED] Mkinitcpio fails to load every single module...

Hello,
This morning I tried to upgrade my system like every other day, except that this morning, mkinitcpio could not create both fallback and arch images which means I can't boot on my system without a livecd and a chroot now.
Here is the error list :
https://gist.github.com/Depado/5795908
I don't know what happened. I tried to run "pacman -S linux" in chroot but still the same problem.
Is there something I'm doing wrong ? Did I miss an update on the website ? Do I have to rewrite mkinitcpio.conf ?
Thanks...
SOLVED :
Reinstalling kmod, udev and mkinitcpio solved the problem of building the image.
Last edited by Depado (2013-06-17 10:51:22)

I managed to build the image properly. Now I get a "Waiting for device /dev/sda3" issue...
EDIT : I think that's because I didn't mounted /boot when I built the image. Problem solved.
Last edited by Depado (2013-06-17 10:50:07)

[SOLVED] mkinitcpio silently fails to build initramfs image

I faced this annoying problem where mkinitcpio kept generating 20-byte initramfs images (for normal and fallback).
The first symptom was being unable to boot. Kept getting error messages about junk in the initramfs image. I suspected a corrupted file. Used chroot, tried reinstalling the linux package, regenerating using mkinitcpio - didn't solve the problem.
Then, I checked the /boot directory and found that the initramfs images were 20 bytes! mkinitcpio was generating 20-byte images (essentially empty images). It had done so on the last kernel upgrade.
I was able to copy initramfs images from another Arch installation (same architecture, same kernel version) and boot Arch. I was unable to figure out why mkinitcpio was doing so. I tried reinstalling a few core packages (the build tools, grep etc.) but they didn't help.
I gave up and tried the brute force method of reinstalling all packages. It was then that pacman complained about conflicting files for libarchive - libarchive! I remembered that there had been a forced shutdown at some time when packages were being updated. libarchive.so was corrupted/missing and had to be copied from another system (pacman wouldn't function without it). I hadn't reinstalled libarchive then. I did so now, and voila! mkinitcpio worked properly again.
TLDR - If mkinicpio is not generating images properly, some tool it depends on (or mkinitcpio) is failing silently/is missing/is corrupt. Reinstall those things.

I feel silly!
pactree -u mkinitcpio
would have given me the list of packages I needed to reinstall.

[SOLVED] mkinitcpio-0.7-1 update breaks plymouth

Today's update of mkinitcpio-0.7-1 fixes an issue I and others were having with some module errors at the beginning of boot, but has broken plymouth. It only becomes apparent when I first attempt to use mkinitcpio to rebuild my images, which calls the plymouth hook in. It barks about an install function being deprecated in '/lib/initcpio/install/plymouth', that the function should be renamed to 'build' and also complains about the command 'add_device' not being found. If I change the 'install' function name to 'build' that error disappears, but the other error is still present. I tried replacing 'add_device' with 'mknod', as suggested in another post, but this does not work either. Long and short of it, there is currently no way with mkinitcpio to have plymouth get built into the image, at least AFAIK. Here is the top stanza of the '/lib/initcpio/install/plymouth' file which is giving the issue:
# vim: set ft=sh:
install() {
add_device /dev/fb0 c 29 0
add_dir /dev/pts
add_dir /usr/share/plymouth/themes
Last edited by sidneyk (2011-07-07 05:43:19)

sidneyk wrote:
karol wrote:http://mailman.archlinux.org/pipermail/ … 20824.html
I wouldn't call it a workaround - it's the new way.
I was calling it a 'workaround' in the sense that the fix hasn't been incorporated yet into the plymouth-git maintainer's package in the AUR.
Ah, OK.
Thank you for posting the info on the package's page in the AUR.
I think you can mark this thread as solved.

[SOLVED] mkinitcpio (problem with ide and encrypt hooks)

I've installed kernel26-beyond 2.6.19beyond2 and after that mkinitcpio couldn't generate img file. I tried with 2 configs:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="reiser4 ext2 reiserfs"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
# This setup loads an LVM volume group on a usb device.
# HOOKS="base udev usb filesystems lvm"
HOOKS="base udev autodetect ide scsi sata encrypt filesystems"
and
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="reiser4 ext2 reiserfs"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
# This setup loads an LVM volume group on a usb device.
# HOOKS="base udev usb filesystems lvm"
HOOKS="base udev autodetect scsi sata encrypt filesystems"
With the first config mkinitcpio froze when was generating ide hook and with the second froze when generating encrypt hook.
Any idea what might have gone wrong? What should I do?
Best regards,
jasiekd.
Last edited by jasiekd (2007-02-20 14:00:49)

I don't have any experience with the beyond-kernel, but on two of my machines which already use encrypted root with LUKS I have added the following modules into /etc/mkinitcpio.conf
(I use AES for swap & Serpent for the rest, sha256 as essiv-hash)
MODULES="dm-crypt aes-i586 serpent sha256"
Did you switch the Kernel on an already installed/running System or did you make a fresh installation with the beyond-kernel? In case your System is already installed, you could try the mkinitcpio procedure with a life-cd (may be worth a try).
There's also an excellent article in the wiki:
http://wiki.archlinux.org/index.php/Mkinitcpio
In the troubleshooting-section of the article there's also a solution to a problem concerning the beyond-kernel and ide/sata/scsi, which could be just what you are looking for.
Hope it'll be helpfull!

[SOLVED]mkinitcpio command not found!??

Hello all,
I receive the following when trying to rebuild the stock kernel:
[taylor-unix@Legion Desktop]$ sudo mkinitcpio -p kernel26
sudo: mkinitcpio: command not found
[taylor-unix@Legion Desktop]$
The same error occurs even after the re-installation of 'mkinitcpio'.
I've had the same problem with 'hwdetect', regardless of whether I've reinstalled it.
I seem to have commands that do not work on this system, like 'shutdown' for example.. 'shutdown: command not found'. Perhaps I've missed installing a crucial package?
I need help..
My sincerest thanks in advance.
Last edited by edward.taylor89 (2010-11-10 17:39:46)

Here as follows:
mkinitcpio /etc/
mkinitcpio /etc/mkinitcpio.conf
mkinitcpio /etc/mkinitcpio.d/
mkinitcpio /etc/mkinitcpio.d/example.preset
mkinitcpio /lib/
mkinitcpio /lib/initcpio/
mkinitcpio /lib/initcpio/functions
mkinitcpio /lib/initcpio/hooks/
mkinitcpio /lib/initcpio/hooks/btrfs
mkinitcpio /lib/initcpio/hooks/consolefont
mkinitcpio /lib/initcpio/hooks/dmesg
mkinitcpio /lib/initcpio/hooks/keymap
mkinitcpio /lib/initcpio/hooks/memdisk
mkinitcpio /lib/initcpio/hooks/net
mkinitcpio /lib/initcpio/hooks/resume
mkinitcpio /lib/initcpio/hooks/sleep
mkinitcpio /lib/initcpio/hooks/udev
mkinitcpio /lib/initcpio/init
mkinitcpio /lib/initcpio/init_functions
mkinitcpio /lib/initcpio/install/
mkinitcpio /lib/initcpio/install/autodetect
mkinitcpio /lib/initcpio/install/base
mkinitcpio /lib/initcpio/install/btrfs
mkinitcpio /lib/initcpio/install/consolefont
mkinitcpio /lib/initcpio/install/dmesg
mkinitcpio /lib/initcpio/install/dsdt
mkinitcpio /lib/initcpio/install/filesystems
mkinitcpio /lib/initcpio/install/fw
mkinitcpio /lib/initcpio/install/ide
mkinitcpio /lib/initcpio/install/keymap
mkinitcpio /lib/initcpio/install/memdisk
mkinitcpio /lib/initcpio/install/net
mkinitcpio /lib/initcpio/install/pata
mkinitcpio /lib/initcpio/install/pcmcia
mkinitcpio /lib/initcpio/install/resume
mkinitcpio /lib/initcpio/install/sata
mkinitcpio /lib/initcpio/install/scsi
mkinitcpio /lib/initcpio/install/sleep
mkinitcpio /lib/initcpio/install/udev
mkinitcpio /lib/initcpio/install/usb
mkinitcpio /lib/initcpio/install/usbinput
mkinitcpio /lib/initcpio/udev/
mkinitcpio /lib/initcpio/udev/01-memdisk.rules
mkinitcpio /lib/initcpio/udev/load-modules.sh
mkinitcpio /sbin/
mkinitcpio /sbin/mkinitcpio
mkinitcpio /usr/
mkinitcpio /usr/share/
mkinitcpio /usr/share/man/
mkinitcpio /usr/share/man/man5/
mkinitcpio /usr/share/man/man5/mkinitcpio.5.gz

[solved] new xorg not autodetecting touchpad

After I upgraded to to xorg server 1.6, my touchpad doesn't work. Not sure what is going on. There doesn't seem to be any errors in the log. The mouse that is detected is a usb one I found in a corner trying to figure this out.
Any ideas?
Thanks
My xorg.conf is:
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/local/share/fonts"
EndSection
Section "Module"
Load "bitmap"
Load "int10"
Load "vbe"
EndSection
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
Option "DRI" "true"
VendorName "Intel Corporation"
BoardName "Mobile Integrated Graphics Controller"
BusID "PCI:0:2:0"
Option "FramebufferCompression" "true"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Enable"
Option "MIT-SHM" "Yes"
EndSection
Xorg.0.log:
X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH i686
Current Operating System: Linux awalterslaptop 2.6.29-ARCH #1 SMP PREEMPT Wed Apr 8 12:47:56 UTC 2009 i686
Build Date: 15 April 2009 11:09:10AM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 16 11:59:03 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section. Using the first Screen section.
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/local/share/fonts" does not exist.
Entry deleted from font path.
(**) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/75dpi,
/usr/share/fonts/100dpi,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
built-ins
(**) ModulePath set to "/usr/lib/xorg/modules"
(**) Extension "Composite" is enabled
(**) Extension "MIT-SHM" is enabled
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Loader magic: 0x1a40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0@0:2:0) Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xeff00000/524288, 0xd0000000/268435456, 0xefec0000/262144, I/O @ 0x0000eff8/8
(--) PCI: (0@0:2:1) Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xeff80000/524288
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded by default.
(II) "dbe" will be loaded by default.
(II) "glx" will be loaded by default.
(II) "record" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.1.0
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
compiled for 1.6.0, module version = 2.3.2
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, G35, 965Q, 946GZ,
965GM, 965GME/GLE, G33, Q35, Q33, Intel Integrated Graphics Device
(II) Primary Device is: PCI 00@00:02:0
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules//libint10.so
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Reloading /usr/lib/xorg/modules//libvbe.so
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 0.1.0
ABI class: X.Org Video Driver, version 5.0
(II) intel(0): Creating default Display subsection in Screen section
"Screen0" for depth/fbbpp 24/32
(==) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(**) intel(0): Option "DRI" "true"
(**) intel(0): Option "FramebufferCompression" "true"
(II) intel(0): Integrated Graphics Chipset: Intel(R) 945GM
(--) intel(0): Chipset: "945GM"
(--) intel(0): Linear framebuffer at 0xD0000000
(--) intel(0): IO registers at addr 0xEFF00000
(II) intel(0): 2 display pipes available.
(==) intel(0): Using EXA for acceleration
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) intel(0): Output VGA using monitor section Monitor0
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): Output LVDS has no monitor section
(II) intel(0): I2C bus "LVDSDDC_C" initialized.
(II) intel(0): Attempting to determine panel fixed mode.
(II) intel(0): I2C device "LVDSDDC_C:E-EDID segment register" registered at address 0x60.
(II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
(II) intel(0): EDID vendor "SEC", prod id 0
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules//libint10.so
(II) intel(0): initializing int10
(II) intel(0): Bad V_BIOS checksum
(II) intel(0): Primary V_BIOS segment is: 0xc000
(II) intel(0): VESA BIOS detected
(II) intel(0): VESA VBE Version 3.0
(II) intel(0): VESA VBE Total Mem: 7872 kB
(II) intel(0): VESA VBE OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS
(II) intel(0): VESA VBE OEM Software Rev: 1.0
(II) intel(0): VESA VBE OEM Vendor: Intel Corporation
(II) intel(0): VESA VBE OEM Product: Intel(r) 82945GM Chipset Family Graphics Controller
(II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) intel(0): found backlight control method /sys/class/backlight/acpi_video0
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70.
(II) intel(0): No SDVO device found on SDVOB
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72.
(II) intel(0): No SDVO device found on SDVOC
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed.
(II) intel(0): Output TV has no monitor section
(II) intel(0): EDID vendor "SEC", prod id 0
(II) intel(0): Output VGA disconnected
(II) intel(0): Output LVDS connected
(II) intel(0): Output TV disconnected
(II) intel(0): Using exact sizes for initial modes
(II) intel(0): Output LVDS using initial mode 1280x800
(II) intel(0): Monitoring connected displays enabled
(II) intel(0): detected 256 kB GTT.
(II) intel(0): detected 7932 kB stolen memory.
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Will not try to enable page flipping
(==) intel(0): Triple buffering disabled
(==) intel(0): Intel XvMC decoder disabled
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(==) intel(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "exa"
(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules//libexa.so
(II) Module exa: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 2.4.0
ABI class: X.Org Video Driver, version 5.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) intel(0): Comparing regs from server start up to After PreInit
(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd000000a
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x00000000 to 0x80000203
(WW) intel(0): PIPEASTAT before: status:
(WW) intel(0): PIPEASTAT after: status: FIFO_UNDERRUN VSYNC_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): Register 0x71024 (PIPEBSTAT) changed from 0x00000202 to 0x80000242
(WW) intel(0): PIPEBSTAT before: status: VSYNC_INT_STATUS VBLANK_INT_STATUS
(WW) intel(0): PIPEBSTAT after: status: FIFO_UNDERRUN VSYNC_INT_STATUS LBLC_EVENT_STATUS VBLANK_INT_STATUS
(WW) intel(0): Register 0x68060 (TV_SC_CTL_1) changed from 0xc1710087 to 0xc1710088
(WW) intel(0): Register 0x68064 (TV_SC_CTL_2) changed from 0x6b405140 to 0x4e2d1dc8
(II) Loading sub module "dri"
(II) LoadModule: "dri"
(II) Reloading /usr/lib/xorg/modules/extensions//libdri.so
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) intel(0): Kernel reported 810752 total, 1 used
(II) intel(0): I830CheckAvailableMemory: 3243004 kB available
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: drmOpenMinor returns 10
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
(II) intel(0): [drm] framebuffer mapped by ddx driver
(II) intel(0): [drm] added 1 reserved context for kernel
(II) intel(0): X context handle = 0x1
(II) intel(0): [drm] installed DRM signal handler
(**) intel(0): Framebuffer compression enabled
(**) intel(0): Tiling enabled
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
(II) intel(0): [drm] Registers = 0xeff00000
(II) intel(0): [drm] ring buffer = 0xd0000000
(II) intel(0): [drm] mapped front buffer at 0xd1000000, handle = 0xd1000000
(II) intel(0): [drm] mapped back buffer at 0xd4000000, handle = 0xd4000000
(II) intel(0): [drm] mapped depth buffer at 0xd5000000, handle = 0xd5000000
(II) intel(0): [drm] mapped classic textures at 0xd6000000, handle = 0xd6000000
(II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
(II) intel(0): [dri] visual configs initialized
(II) intel(0): Page Flipping disabled
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) EXA(0): Offscreen pixmap area of 31457280 bytes
(II) EXA(0): Driver registered support for the following operations:
(II) Solid
(II) Copy
(II) Composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): [DRI] installation complete
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x01000000 (pgoffset 4096)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x02000000 (pgoffset 8192)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x04000000 (pgoffset 16384)
(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x05000000 (pgoffset 20480)
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x06000000 (pgoffset 24576)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x0061ffff: compressed frame buffer (6144 kB, 0x00000000cf820000 physical
(II) intel(0): 0x00620000-0x00620fff: compressed ll buffer (4 kB, 0x00000000cfe20000 physical
(II) intel(0): 0x00621000-0x0062afff: HW cursors (40 kB, 0x00000000cfe21000 physical
(II) intel(0): 0x0062b000-0x00632fff: logical 3D context (32 kB)
(II) intel(0): 0x00633000-0x00633fff: overlay registers (4 kB, 0x00000000cfe33000 physical
(II) intel(0): 0x007bf000: end of stolen memory
(II) intel(0): 0x01000000-0x01ffffff: front buffer (10240 kB) X tiled
(II) intel(0): 0x02000000-0x03dfffff: exa offscreen (30720 kB)
(II) intel(0): 0x04000000-0x04ffffff: back buffer (10240 kB) X tiled
(II) intel(0): 0x05000000-0x05ffffff: depth buffer (10240 kB) X tiled
(II) intel(0): 0x06000000-0x07ffffff: classic textures (32768 kB)
(II) intel(0): 0x10000000: end of aperture
(WW) intel(0): ESR is 0x00000001, instruction error
(WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled
(WW) intel(0): Existing errors found in hardware state.
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
(II) intel(0): Output configuration:
(II) intel(0): Pipe A is off
(II) intel(0): Display plane A is now disabled and connected to pipe A.
(II) intel(0): Pipe B is on
(II) intel(0): Display plane B is now enabled and connected to pipe B.
(II) intel(0): Output VGA is connected to pipe none
(II) intel(0): Output LVDS is connected to pipe B
(II) intel(0): Output TV is connected to pipe none
(II) intel(0): [drm] dma control initialized, using IRQ 16
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
(**) Option "dpms" "true"
(**) intel(0): DPMS enabled
(II) intel(0): Set up textured video
(II) intel(0): Set up overlay video
(II) intel(0): direct rendering: Enabled
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: drmOpenMinor returns 11
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) AIGLX: enabled GLX_SGI_make_current_read
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: enabled GLX_texture_from_pixmap with driver support
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i915_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) intel(0): Setting screen physical size to 331 x 207
(II) config/hal: Adding input device HID 062a:0000
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.0, module version = 2.2.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(**) HID 062a:0000: always reports core events
(**) HID 062a:0000: Device: "/dev/input/event11"
(II) HID 062a:0000: Found 3 mouse buttons
(II) HID 062a:0000: Found x and y relative axes
(II) HID 062a:0000: Found scroll wheel(s)
(II) HID 062a:0000: Configuring as mouse
(**) HID 062a:0000: YAxisMapping: buttons 4 and 5
(**) HID 062a:0000: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "HID 062a:0000" (type: MOUSE)
(**) HID 062a:0000: (accel) keeping acceleration scheme 1
(**) HID 062a:0000: (accel) filter chain progression: 2.00
(**) HID 062a:0000: (accel) filter stage 0: 20.00 ms
(**) HID 062a:0000: (accel) set acceleration profile 0
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) config/hal: Adding input device Video Bus
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event8"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Video Bus
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event7"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) intel(0): EDID vendor "SEC", prod id 0
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x800"x0.0 71.11 1280 1328 1360 1440 800 802 808 823 -hsync -vsync (49.4 kHz)
(II) intel(0): EDID vendor "SEC", prod id 0
(II) intel(0): xf86BindGARTMemory: bind key 5 at 0x007bf000 (pgoffset 1983)
(II) intel(0): xf86UnbindGARTMemory: unbind key 5
(II) intel(0): EDID vendor "SEC", prod id 0
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x800"x0.0 71.11 1280 1328 1360 1440 800 802 808 823 -hsync -vsync (49.4 kHz)
(II) intel(0): EDID vendor "SEC", prod id 0
(II) intel(0): xf86BindGARTMemory: bind key 5 at 0x007bf000 (pgoffset 1983)
(II) intel(0): xf86UnbindGARTMemory: unbind key 5
exaCopyDirty: Pending damage region empty!
Last edited by amw2320 (2009-05-03 04:45:17)

I hope i won't say anything stupid here, but AFAIUnderstand Xorg has now an autodetect "feature" that fails more often than not, or configures mice with weird defaults.
Try to add this to your /etc/X11/xorg.conf:
Section "ServerFlags"
Option "AutoAddDevices" "false"
Option "DontZap" "false"
EndSection
Section "InputDevice"
Identifier "Touchpad"
Driver "synaptics"
Option "CorePointer"
Option "Device" "/dev/misc/psaux"
Option "Protocol" "auto-dev"
# Option "LeftEdge" "1000"
# Option "RightEdge" "5400"
# Option "TopEdge" "1000"
# Option "BottomEdge" "4900"
# Option "PalmDetect" "0"
# Option "SHMConfig" "true"
# Option "RBCornerButton" "0"
# Option "RTCornerButton" "0"
Option "MinSpeed" "0.9"
Option "MaxSpeed" "1.4"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
Option "VertTwoFingerScroll" "1"
Option "HorizTwoFingerScroll" "1"
# Option "VertEdgeScroll" "1"
# Option "HorizEdgeScroll" "1"
# Option "MaxTapTime" "180"
# Option "MaxTapMove" "2000"
# Option "MaxDoubleTapTime" "360"
# Option "SingleTapTimeout" "360"
# Option "EmulateMidButtonTime" "75"
# Option "HorizScrollDelta" "0"
EndSection
Section "InputDevice"
Identifier "Mouse"
Driver "mouse"
Option "SendCoreEvents" "true"
EndSection
(the "DontZap" option is unrelated to your problem, it allows to kill X with ctrl-alt-backspace)
These touchpad settings are the ones I'm using on my EeePC900, you may want to tweak them. I left some commented options for reference.

[SOLVED] mkinitcpio brings error during install

installing mkinitcpio...
Optional dependencies for mkinitcpio:
installing linux...
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait ...
/sbin/mkinitcpio: line 160: 6596 Segmentation fault mountpoint -q /proc
==> ERROR: /proc must be mounted!
It's happening even before any configuration so I can't imagine what could I did wrong... had some troubles with sources (core newer than extra) but I finally decided to use ftp.archlinux.org so it's irrelevant.
Should I exit the installer and mount /proc? But, well... I don't know what device should I mount there. ;3
Also, when I'm exiting the installer, this errors appear (a lot of times in a row):
[ *number 1*] SQUASHFS error: Unable to read data cache entry [*number 2*]
[ *number 3*] SQUASHFS error: Unable to read page, block *number 2*, size 96ac
and some buffer I/O errors and I can't even "shutdown -r now" and need to use power button... but only after failed installation, without it - everything is okay.
Can it be that the installation media is damaged, like e.g. I did sth wrong during "dd" the iso into the pen drive?
I would appreciate any response.
Last edited by Włóczymyśl (2011-10-11 05:51:50)

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

[solved] mkinitcpio & custom kernels

I have recently started using the custom kernel from repo-ck (ck-core2). I also have the regular linuk kernel installed, but boot (via syslinux) to the ck version.
Today, the regular linux kernel updated & mkinitcpio was run by pacman.....
So to my question...
Do I need to
sudo mkinitcpio -p linux-ck
I did this anyway, but was it required ?
Last edited by flipper T (2013-06-09 18:16:28)

When linux-ck is updated, the linux-ck kernel is downloaded with pacman, 'mkinitcpio -p linux-ck' will be run automatically.
If only the regular linux kernel has been updated, there's no need to run 'mkinitcpio -p linux-ck'.

[SOLVED] mkinitcpio and kernel upgrades without SyncFirst option?

As pacman 4.1 doesn't more provide SyncFirst option how to be sure mkinitcpio will run after linux-headers installation?
for example, in case of
https://wiki.archlinux.org/index.php/Vi … any_kernel
previously, i had
SyncFirst = pacman linux-headers linux-lts-headers linux-pf-headers
Last edited by wild.lumberjack (2013-04-05 19:36:32)

I hat to uninstall yaourt, yail and package-query simply by:
sudo pacman -Rcs yaourt
then run commands:
sudo pacman -Sy
sudo pacman -S linux-headers
sudo pacman -S pacman
sudo pacman -S yaourt
modify ~/.bashrc with this line
alias yaourt='sudo /usr/bin/pacman -Sy linux-headers pacman --needed 2>/dev/null && yaourt'
2>/dev/null suppresses warnings about the skipped reinstalls of linux-headers and pacman
Now use yaourt -Su instead of formerly yaourt -Syu
yaourt -Su
Arch Rulez
JohnDVD
Last edited by JohnDVD (2013-04-06 07:49:38)

Kernel26 locks up on autodetect

Trying to update kernel but it hangs on autodetect:
(1/1) upgrading kernel26 [######################] 100%
>>> Updating module dependencies. Please wait ...
>>> MKINITCPIO SETUP
>>> ----------------
>>> If you use LVM2, Encrypted root or software RAID,
>>> Ensure you enable support in /etc/mkinitcpio.conf .
>>> More information about mkinitcpio setup can be found here:
>>> http://wiki.archlinux.org/index.php/Mkinitcpio
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin dry run
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
output from mkinitcpio -v -g /boot/kernel26
:: Begin dry run
adding dir /lib
adding dir /lib/modules
adding dir /lib/modules/2.6.29-ARCH
adding dir /lib/modules/2.6.29-ARCH/kernel
adding dir /lib/modules/2.6.29-ARCH/kernel/drivers
adding dir /lib/modules/2.6.29-ARCH/kernel/drivers/scsi
adding file /lib/modules/2.6.29-ARCH/kernel/drivers/scsi/scsi_mod.ko
adding dir /lib/modules/2.6.29-ARCH/kernel/drivers/ata
adding file /lib/modules/2.6.29-ARCH/kernel/drivers/ata/libata.ko
adding file /lib/modules/2.6.29-ARCH/kernel/drivers/ata/pata_acpi.ko
adding file /lib/modules/2.6.29-ARCH/kernel/drivers/ata/pata_amd.ko
adding file /lib/modules/2.6.29-ARCH/kernel/drivers/ata/ata_generic.ko
:: Parsing hook [base]
adding dir /proc
adding dir /sys
adding dir /dev
adding node /dev/null
adding node /dev/zero
adding node /dev/console
adding node /dev/mem
adding file /lib/klibc-i5oq3Jxz3fJL_nvxTyXXO41WmGk.so
adding dir /bin
adding file /bin/cat
adding file /bin/chroot
adding file /bin/dd
adding file /bin/dmesg
adding file /bin/false
adding file /bin/fstype
adding file /bin/halt
adding file /bin/ipconfig
adding file /bin/kill
adding file /bin/kinit
adding file /bin/ln
adding file /bin/lodel
adding file /bin/losetup
adding file /bin/lsmod
adding file /bin/mdassemble
adding file /bin/minips
adding file /bin/mkdir
adding file /bin/mkfifo
adding file /bin/mknod
adding file /bin/moddeps
adding file /bin/mount
adding file /bin/mv
adding file /bin/nfsmount
adding file /bin/nuke
adding file /bin/parseblock
adding file /bin/pivot_root
adding file /bin/poweroff
adding file /bin/readlink
adding file /bin/reboot
adding file /bin/replace
adding file /bin/resolve-modalias
adding file /bin/resume
adding file /bin/run-init
adding file /bin/sh
adding file /bin/sleep
adding file /bin/sync
adding file /bin/true
adding file /bin/umount
adding file /bin/uname
adding dir /sbin
adding file /sbin/depmod
adding file /sbin/insmod
adding file /sbin/modinfo
adding file /sbin/modprobe
adding file /sbin/rmmod
adding link /bin/modprobe -> /sbin/modprobe
adding file /init
adding file /config
adding dir /etc
adding dir /etc/modprobe.d
adding file /etc/modprobe.d/usb-load-ehci-first
:: Parsing hook [udev]
adding file /sbin/udevd
adding file /sbin/udevadm
adding dir /lib/udev
adding dir /lib/udev/rules.d
adding file /lib/udev/rules.d/50-udev-default.rules
adding file /lib/udev/rules.d/60-persistent-storage.rules
adding file /lib/udev/rules.d/64-device-mapper.rules
adding file /lib/udev/rules.d/64-md-raid.rules
adding file /lib/udev/rules.d/80-drivers.rules
adding file /lib/udev/firmware.sh
adding file /lib/udev/path_id
adding file /lib/udev/vol_id
adding file /lib/udev/load-modules.sh
adding dir /etc/udev
adding file /etc/udev/udev.conf
adding dir /hooks
adding file /hooks/udev
:: Parsing hook [autodetect]
each time it locks on autodetect.

Same here, every time pacman upgrades the kernel it hangs at parsing hook (autodetect). Problem is it doesn't finish and computer is left in a non-bootable state. Finally cancel and retry, same thing.
Last time (luckily) I had a second Arch partition to boot into and I found solution. Unfortunately it means having to boot into a different partition (or livecd) chrooting into the dead partition, and then running mkinitcpio from there. Check http://bbs.archlinux.org/viewtopic.php?id=64027
I am seriously considering going back to FreeBSD. This is the third time this has happened to me, and I've only been using Arch for about 6 months. Seriously, guys, cant they get this working right?
Edit: found new procedure. If mkinitcpio hangs on autodetect during upgrade then
sudo nano /etc/mkinitcpio.conf
find a line such as HOOKS="base udev autodetect pata scsi sata keymap filesystems"
comment it out and add same line without "autodetect"
save the file
sudo mkinitcpio -p kernel26
basically this creates two failsafe kernel images now instead of a stripped-down one and a failsafe
reboot to upgraded kernel, edit mkinitcpio to uncomment the line with autodetect (comment the secone one) and mkinitcpio again to regenerate the images as they are supposed to be. Once booted into the upgraded kernel the autodetect works fine.
Last edited by NevarMaor (2009-04-25 02:11:47)

[Solved] Pacman -Su stuck at downloading required keys

With updating my system (with pacman -Syu), pacman seems stuck with the last operation "Checking keys in the keyring". What I see is:
(167/167) checking keys in keyring [####################################] 100%
downloading required keys...
After 20 minutes or so I killed the process and initialized the keyring from scratch, following the instructions on the wiki, hoping this would give some clues. Unfortunately, this problem still persists.
Any suggestions on what may be the problem, or how to fix it?
Last edited by Floris (2015-02-12 14:04:31)

Thanks for that hint. The debug showed that it was fetching a key remotely, and then nothing. With that, I was able to find this similar thread on this forum. I followed the suggested procedure:
mauritiusdadd wrote:# rm -R /etc/pacman.d/gnupg/
# rm -R /root/.gnupg/ # only if the directory exists
# gpg --refresh-keys
# pacman-key --init && pacman-key --populate
# pacman-key --refresh-keys
and it solved the stall. I think that the second instruction really helped, because I did rebuild the keychain multiple times today. Apparently something was cached in the .gnupg folder that might have interfered.
Thanks!
Last edited by Floris (2015-02-12 16:54:23)

Solaris TCP Tuning

If you are running Weblogic on Solaris you'll need to change some of the
default TCP configuration parameters.
Sun's default TCP settings are not correct for a web server.
We noticed the server was stalling during certain peak periods. netstat
showed that many sockets opened to port 80 were in CLOSE_WAIT or
FIN_WAIT_2.
The following url is a great resource for tuning Solaris TCP/IP
http://www.rvs.uni-hannover.de/people/voeckler/tune/EN/tune.html
Changing the following TCP params solved our stalling problem. Also make
sure you up the ulimit as stated in the weblogic doc.
# to display the TCP values.
ndd /dev/tcp tcp_close_wait_interval tcp_fin_wait_2_flush_interval
tcp_keepalive_interval
# set tcp_close_wait_interval from 2400000 to 60000
ndd -set /dev/tcp tcp_close_wait_interval 60000
# set tcp_fin_wait_2_flush_interval from 675000 to 67500
ndd -set /dev/tcp tcp_fin_wait_2_flush_interval 67500
#set tcp_keepalive_interval from 7200000 to 300000
ndd -set /dev/tcp tcp_keepalive_interval 300000

Hi Victor,
We are facing similar problems as you are while running load testing using Load runner simulating a load of 100 concurrent users.
We have Oracle 8.1.7.4 client running on WebLogic 6.1 SP4 on Solaris 2.6 connecting to Oracle OPS 8.1.7 running on Solaris 2.6. We are getting core dumps while running stress testing using Load Runner for 100 concurrent users. The performance is very good for a while in the beginning of the test with CPU and memory utilization low and all of a sudden we see requests for connections queueing up on the WLS and the server crashes.
If you have found a solution to your problem Please send us details of it. Also it will be very helpful if you can send us the fix applied.
You can send your reply to my email at [email protected]
Regards,
Raj

[SOLVED] mkinitcpio stalled at [autodetect]

Similar Messages

Maybe you are looking for