[solved] Nvidia with custom kernel

Hello,
I just compiled a new custom kernel and the custom kernel headers and then went on to create a custom nvidia kernel module. Somehow that doesn't seem to work. Nvidia is complaining that there is something Xen-ish in my kernel:
Creating directory NVIDIA-Linux-x86_64-260.19.36-no-compat32
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 260.19.36.....................................................................................................................
The kernel you are installing for is a Xen kernel!
The NVIDIA driver does not currently work on Xen kernels. If
you are using a stock distribution kernel, please install
a variant of this kernel without Xen support; if this is a
custom kernel, please install a standard Linux kernel. Then
try installing the NVIDIA kernel module again.
*** Failed Xen sanity check. Bailing out! ***
make[1]: *** [build-sanity-checks] Error 1
make: *** [module] Error 2
Aborting...
As far as I know there is no xen or other vm stuff in the kernel. To verify this I tried to make a new nvidia package for the standard kernel. Again the same error.
Also this makes me wonder how the PKGBUILD works since it the build function just runs:
make SYSSRC=/path/to/current/kernelmodules/build module
and there are no xen sanity checks in that script, that happens in nvidia-installer - which isn't called from the PKGBUILD....
Secondly, when doing a "make module" from the nvidia/kernel dir with the standard kernel there is a difference between the abs package and the extra package. Anyone a clue what is going on in the PKGBUILD and why the difference between the two kernel modules?
Thanks.
Last edited by Ulf (2011-02-04 22:20:51)

Ulf wrote:Yeah that seems to work but still wondering why the PKBUILD calls nvidia-installer
To unpack it. From the PKGBUILD:
sh ${_pkg}.run --extract-only
Note the '--extract-only'
Ulf wrote:and why there is a slight difference in size between the extra package and my own module for the same standard arch kernel
Different cflags? Different compiler version?
Ulf wrote:and why nvidia thinks there is a kernel with Xen (it seems that it is some sort of common bug, not specific to arch but nvidia-ish).
Quite likely false detection. The installer sees something activated in the kernel and thinks it's xen related. Or something.

Similar Messages

[Solved] Building vboxdrv with custom kernel

I noticed a Loading Modules [FAIL] during boot yesterday so I decided to investigate it.
[siegemachine@Siege-LapLinux ~]$ sudo modprobe vboxdrv
Password:
FATAL: Module vboxdrv not found.
[siegemachine@Siege-LapLinux ~]$ sudo /etc/rc.d/vboxdrv setup
:: Removing VirtualBox kernel modules [DONE]
:: Compiling VirtualBox kernel modules [BUSY] Look at /tmp/vbox-install.log to find out what went wrong
Look at /tmp/vbox-install.log to find out what went wrong
Look at /tmp/vbox-install.log to find out what went wrong
[siegemachine@Siege-LapLinux ~]$ yaourt -S kernel26-headers
warning: kernel26-headers-2.6.39.1-1 is up to date -- reinstalling
Now I read in this forum
https://bbs.archlinux.org/viewtopic.php?id=107733
that if I have a custom kernel then I have to have the custom kernel-headers to go with it in order to build the virtualbox driver module. The problem is the kernel I got is from the AUR
[siegemachine@Siege-LapLinux ~]$ yaourt -Qi kernel26-kamal
Name : kernel26-kamal
Version : 2.6.39.1-1
And I've tried searching the AUR and there doesn't appear to be any kernel-headers to match the kernel. When I build the kernel should I build it with the regular name and not with -kamal on the end of the kernel and see if that would work for building the virtualbox modules? Or should I boot off the regular kernel (I have both) and build it there, then reboot on this kernel and see if it works? Or finally, do I need to somehow build the kernel-headers for this kernel myself, install them, and then build the modules?
Last edited by SiegeMachine (2011-06-24 03:47:57)

Aha well my friend noticed in the PKGBUILD for kernel26-kamal actually builds the kernel headers for that kernel but it doesn't isntall them so I just downloaded the PKGBUILD and built it myself again with makepkg instead of using yaourt then I could install the header package and built the module after. In the end all is good.

Flashing with custom kernel

I'm considering reflashing my device as it's still sluggish at times, but i have a custom kernel installed. After flashing all the apps can reinstalled in one go, is this safe with the kernel or should i untick it from the selected list and then after flashing manually reinstall it?
Also, does anyone know if there is a file somewhere on the phone that keeps game scores? I don't want to have to retry getting 3 stars on every angry birds level again...
Solved!
Go to Solution.

the settings don't save the custom widget commands so they need re typing - there might be a way to save them tho, i'll have a look and post back in a few mins
you'll need to download leafpad to restore it, you can open a browser and enter this in the address bar
file:///var/opt/rovio/angrybirds/highscores.lua then enter hover mode and copy/paste it to a text file
if you don't want to dl leafpad straight away
then to restore just open it up in xterm with leafpad and copy the saved file to it, beware it will be a large file - not in kb, just the length of it whilst scrolling

[solved] Compiling A Custom Kernel W/ Same Config

I apologize in advance if this is repetitive but i am just a little confused with a few questions.
What i want to do is be able to pretty much just have the ability to add a module or compile somthing on top of the default linux
kernel. I guess the only way to do that is to recompile a linux kernel with this guide:
https://wiki.archlinux.org/index.php/Ke … ild_System
My questions:
In the guide it says to change PKGBUILD and change:
# pkgname=linux-custom # Build kernel with a different name
to
pkgname=linux-test
I understand that. it also says to disable conflicts if you want two kernels.
is that just comenting "provides" , "conflicts" and "replaces"
like:
#next lines give you problems with nvidia drivers which depend on kernel
#provides=('kernel26')
#conflicts=('kernel26')
#replaces=('kernel26'
Also when i select or uncomment menuconfig and lets say not change anything at all is that going to be the same configuration as it would be if i were to install the kernel with pacman. It should be the same thing i have right now? right?
So i can say add framebuffer support or something like that and compile and install and have the exact same kernel now plus FB support.
Thanks,
Paul
Last edited by paulb787 (2012-06-22 05:50:35)

1.
What i want to do is be able to pretty much just have the ability to add a module or compile somthing on top of the default linux kernel.
You would need linux-headers to do that like this (more or less):
cd your-src/kernel
make SYSSRC=/lib/modules/${current-kernel-version}/build module
If you want to customize your kernel further, change its config options, modify default features, etc., then you need to recompile it entirely as described in the Wiki.
2.
is that just comenting "provides" , "conflicts" and "replaces"
Yes. You also need to create a custom linux-${your-custom-kernel-name}.preset in order to generate initramfs. Of course, you can as well use the default name and change the settings in the config file (via menuconfig, nconfig or whatever tool you choose the achieve this). Then nothing has to be changed as all the add-ons will follow the naming convention reserved for the default kernel.
3.
Also when i select or uncomment menuconfig and lets say not change anything at all is that going to be the same configuration as it would be if i were to install the kernel with pacman?
Yes.
4.
So i can say add framebuffer support or something like that and compile and install and have the exact same kernel now plus FB support.
Basically yes, though I'm wondering for which video board you need extra FB support...
Last edited by bohoomil (2012-06-20 00:41:15)

/lib/firmware conflicts with custom kernel

Hi, I followed the Wiki's guide to ABS building of a custom kernel. Normally I wouldn't care too much if it was maintained by pacman or not, but sadly it HAS to be for the nvidia driver to properly work (and probably my wireless driver's firmware package too..)
It built fine and made the package, but when I go to install it I get file conflicts from kernel26-firmare in /lib/firmware
Do I just disable all kernel firmware in menuconfig and let the kernel26-firmware package handle that?

Please B, because I never boot with arch kernel26, is it safe to just pacman -R kernel26 ???
I'll try it now
:: glibc: requires kernel-headers>=2.6.30.5
I can't remove kernel-headers, I could Rd it but... Please advise
Last edited by combuster (2009-09-07 13:25:31)

[Solved] Lockups with newer Kernels

I noticed frequent lockups where REISUB would still work and I could even still switch workspaces, though nothing would load (sometimes I had a terminal open, but it would never show a prompt). It all started, I think, with the kernels > 3.17.
The lts kernel worked without a problem.
The program that triggered this most of the time is Kodi.
I'm using the -ck kernel from AUR optimized for my CPU, but the regular Arch kernel has the same issue. Recently in one of the other threads about freezes, someone suggested recompiling with, PREEMPT_VOLUNTARY. I did that and the problem was gone.
Now yesterday there was an update to kernel 3.19.3.-2 and now it seems PREEMPT_VOLUNTARY doesn't even cut it. So I checked what the lts kernel uses and it has preemption disabled, so I compiled with that set and am currently checking the results.
My question here really is as to why all that is: has it got to do with my machine?
Here are my specs:
Pentium Core2Duo E6700 3.2 GHz
4 GB Ram
NVIDIA Geforce GT 520
Edit: Solved, since it's not an issue anymore with kernels >4.0
Last edited by th3voic3 (2015-05-13 10:51:53)

I now know it can't be my system's config. Just bootstrapped ipxe.lkrn from syslinux and chose releng 64-bit 2012.08.07_04-00-01. As soon as it finished downloading files and started booting up - kaboom, a cold reboot as if the reset button was pressed.
I wonder if this problem is related to "3.3.5+ power regression still present"
https://bbs.archlinux.org/viewtopic.php?id=146851
EDIT: I've also tried 32-bit install ISO with the same results.
Last edited by MajorTom (2012-08-29 03:50:30)

Two problems with custom kernel

I get two problems with my custom kernel that is not using initrd and otherwise working fine:
1) initscripts does not print anything, i.e., I see the kernel messages and after a short while the login prompt. It seems to start the daemons, however, since my network is working. During shutdown the printout is working as usual.
2) the machine does not power off properly (just hangs/stops after saying that is now powers off).
I am missing some kernel options? Or do I have to configure something differently for not having an initrd?
Thanks, CC

ccom wrote:I now re-compiled with Arch Linux's default settings (except for SCSI, SATA, and filesystem drivers built in) and noinitrd in GRUB. I get the same two problems. What is initrd doing that I missed?
how about display drivers? are you compiling them in the kernel or as external modules?

Booting with custom kernel crashes after update

Hello,
I have a custom 2.6.33 kernel compiled and installed without the use of abs on my system. Some time ago when on one of my updates pacman complained that it cannot install arc's 2.6.33, because the name of the folder it needed for the kernel in /lib/modules already existed(from my kernel). I simply backed mine somewhere else, and then updated with pacman, and overwrote the new folder with the backed one. However, after today's update, my custom kernel won't boot! I noticed that pacman intends to do kernel changes again, so I readied myself for repeating the sequence of actions from the last time, but now pacman did the update without complaining. However, on my next reboot I got a "scsi_mod: module already loaded" error, and boot hanged. After a second try, the error didn't seem to even show up again, but boot would still hang(with a long text ending in "---[ end trace 8336ecf974ba482a]---"). I checked my bzImage, the grub menu file, and there aren't any changes. Any help please?
Last edited by Mitio (2010-04-29 21:26:39)

fsckd: the folders 2.6.27-lts, 2.6.32-ARCH, 2.6.33-ARCH, and the pacman-installed folder I turned to backup 2.6.33-ARCH_back2;
Anyway, I fell back to the 2.6.32 kernel temporary, so this isn't really an urgent matter, but I am still curious what caused this. Oh and karol, I don't believe this is caused by kernel crash, as loading the kernel finishes and then I get the error some time after starting udev and before the services from rc.d(sorry for the misleading topic subject, I corrected it).
Last edited by Mitio (2010-04-29 21:27:56)

Howto install broadcom wl with custom kernel

Hi I am trying to install the broadcom-wl driver from a custom kernel made traditionnal way.
The makefile they provide give me this :
KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd`
make[1]: Entering directory `/home/maxime/kernelbuild/linux-3.10.10'
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
CC [M] /home/maxime/wldriver/src/wl/sys/wl_linux.o
In file included from /home/maxime/wldriver/src/wl/sys/wl_linux.c:43:0:
/home/maxime/kernelbuild/linux-3.10.10/arch/arm/include/asm/system.h:3:26: fatal error: asm/compiler.h: No such file or directory
#include <asm/compiler.h>
^
compilation terminated.
make[2]: *** [/home/maxime/wldriver/src/wl/sys/wl_linux.o] Error 1
make[1]: *** [_module_/home/maxime/wldriver] Error 2
make[1]: Leaving directory `/home/maxime/kernelbuild/linux-3.10.10'
make: *** [all] Error 2
I have change the path in wl_linux.o to include system.h with the full path(as you can see). And it can find it, but I have to change all the path for every <include> wich is very long and i am not sure it s the right way.
I tried to install the driver with yaourt and it installs the .ko . in my extramodules folder in my /lib/modules/ directory. but modprobe wl report no such file.
But if i come back to the precompiled kernel it works. I ve tried to change the kernel version to my current version in extramodules in /lib/modules/extramodules-3.10 that the PKGBUILD is looking at and try to install it again with yaourt on my custom kernel but still the same.
I copied the .ko to my kernel 3.10.10 custom and tried modprob and I got a symlink error.
As they said i need to modprob the cfg80211, which i did but I still get the same error.
Howto build package for my custom kernel and not the default kernel while I am on the custom kernel ??
Last edited by maxarsys (2013-09-09 21:14:39)

Sigi wrote:Have you deleted or commented out kernel26 in the file addedpacks?
oh, thx, i didn't know, that kernel26 is in addedpacks. now, i am building it with #kernel26
Sigi wrote:May I ask why you made your own kernel? I'm just wondering... ;-)
because i wanna change logo in FB, and/or add splasscreen support.
or is it possible, add it, to kernel26?
Sigi wrote:edit: btw, Welcome to the forum!
oh thx, hello here

How to get ati and madwifi to work with custom kernel??

Hi. I just built emission-sources from aur package. How do I get ati-fglrx and madwifi to build against this custom kernel using pacman?
any ideas?

Cerebral wrote:Grab the PKGBUILD files for ati-fglrx or madwifi from abs (or cvs), change the name (to, say, ati-fglrx-emission and madwifi-emission) and change the kernel version variable (_kernver I think) to the output of uname -r when you're running the emission kernel. Then run makepkg, and you've got a shiny new package.
damn. thats sweet and easy.
thanks.

Top and htop segfault with custom kernel

Hi folks,
When I use a kernel I built myself with realtime patches "top" and "htop" segfault immediately when I try to run them.
Could someone please enlighten me as to what the cause of this might be. I'm guessing it's got to be something I missed when configuring the kernel since everything works when I boot the regular Arch kernel.

I just tried "uptime" again and this was dumped in /var/log/messages
Jun 11 14:47:53 rhuidean kernel: PGD 115f1a067 PUD 115ec0067 PMD 0
Jun 11 14:47:53 rhuidean kernel: CPU 0
Jun 11 14:47:53 rhuidean kernel: Modules linked in: nf_conntrack_ftp nf_conntrack_irc ipt_REJECT ipt_LOG xt_limit xt_state xt_tcpudp nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ipv6 iptable_filter ip_tables x_tables ext2 nvidia(P) i2c_core ohci1394 k8temp ieee1394 usbhid hid evdev sg vboxnetflt vboxdrv fuse snd_hda_codec_nvhdmi snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_hda_intel snd_hda_codec snd_pcm_oss snd_pcm snd_timer snd_page_alloc snd_mixer_oss snd soundcore forcedeth ext3 jbd mbcache sd_mod sr_mod cdrom ohci_hcd ehci_hcd usbcore ahci ata_generic pata_amd pata_acpi libata scsi_mod
Jun 11 14:47:53 rhuidean kernel: Pid: 6074, comm: uptime Tainted: P D 2.6.29-rt #3 System Product Name
Jun 11 14:47:53 rhuidean kernel: RIP: 0010:[<ffffffff802f05ae>] [<ffffffff802f05ae>] seq_read+0xee/0x480
Jun 11 14:47:53 rhuidean kernel: RSP: 0018:ffff88011d4a3e48 EFLAGS: 00010246
Jun 11 14:47:53 rhuidean kernel: RAX: 0000000000000000 RBX: 0000000000000083 RCX: 0000000000000001
Jun 11 14:47:53 rhuidean kernel: RDX: 0000000000000001 RSI: 0000000000001000 RDI: ffff88011c2ff01a
Jun 11 14:47:53 rhuidean kernel: RBP: ffff88011e1e7e80 R08: 0000000000000000 R09: 0000000000000004
Jun 11 14:47:53 rhuidean kernel: R10: 0000000000000000 R11: 0000000000000064 R12: ffff88011d4a3f58
Jun 11 14:47:53 rhuidean kernel: R13: 0000000000000001 R14: 00000000000007ff R15: ffff88011d4a3e80
Jun 11 14:47:53 rhuidean kernel: FS: 00007fbfb8d3a6f0(0000) GS:ffff880028055000(0000) knlGS:0000000000000000
Jun 11 14:47:53 rhuidean kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 11 14:47:53 rhuidean kernel: CR2: 000000000000009b CR3: 0000000115eb1000 CR4: 00000000000006e0
Jun 11 14:47:53 rhuidean kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jun 11 14:47:53 rhuidean kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jun 11 14:47:53 rhuidean kernel: Process uptime (pid: 6074, threadinfo ffff88011d4a2000, task ffff88011e45d0c0)
Jun 11 14:47:53 rhuidean kernel: 000000000000afc0 ffff880115f20970 0000000000000000 00000000000007ff
Jun 11 14:47:53 rhuidean kernel: RSP <ffff88011d4a3e48>
Jun 11 14:47:53 rhuidean kernel: ---[ end trace 046ef4ddb8bafba2 ]---
And here's the last few lines from "strace uptime"
open("/proc/loadavg", O_RDONLY) = 4
lseek(4, 0, SEEK_SET) = 0
read(4, <unfinished ...>
+++ killed by SIGKILL +++

Trouble with custom kernel for EeePC 1000H and bluetooth

I believe I've got pretty much everything working on my 1000H except for bluetooth. I can't seem to get the hardware working. The module is loaded, and dmesg has references to bluetooth, but blueman does not list the adapter, and running "hcitool scan" from the command line returns "Device is not available: No such device".
I've enabled every bluetooth-related item I can find in the kernel, so I don't see what I'm missing. I did import the config from the stock kernel, where bluetooth was working fine.
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="America/Los_Angeles"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="no"
#MOD_BLACKLIST=() #deprecated
MODULES=(atl1e rt2860sta rndis_host cdc_ether usbnet rfkill acpi-cpufreq pciehp intel_agp snd-hda-intel !snd-pcsp bluetooth !eeepc_laptop)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="sprice-l"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="dhcp"
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(!eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network @acpid @crond hal networkmanager netfs bluetooth @alsa @openntpd gdm)
dmesg:
Linux version 2.6.32-ARCH (root@sprice-l) (gcc version 4.4.2 20091208 (prerelease) (GCC) ) #5 SMP PREEMPT Tue Dec 29 09:02:31 PST 2009
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e2000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003f7a0000 (usable)
BIOS-e820: 000000003f7a0000 - 000000003f7ae000 (ACPI data)
BIOS-e820: 000000003f7ae000 - 000000003f7f0000 (ACPI NVS)
BIOS-e820: 000000003f7f0000 - 000000003f800000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
DMI present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
last_pfn = 0x3f7a0 max_arch_pfn = 0x100000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-DFFFF uncachable
E0000-EFFFF write-through
F0000-FFFFF write-protect
MTRR variable ranges enabled:
0 base 000000000 mask 0C0000000 write-back
1 base 03F800000 mask 0FF800000 uncachable
2 disabled
3 disabled
4 disabled
5 disabled
6 disabled
7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Scanning 0 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009fc00 (usable)
modified: 000000000009fc00 - 00000000000a0000 (reserved)
modified: 00000000000e2000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 000000003f7a0000 (usable)
modified: 000000003f7a0000 - 000000003f7ae000 (ACPI data)
modified: 000000003f7ae000 - 000000003f7f0000 (ACPI NVS)
modified: 000000003f7f0000 - 000000003f800000 (reserved)
modified: 00000000fee00000 - 00000000fee01000 (reserved)
modified: 00000000fff80000 - 0000000100000000 (reserved)
initial memory mapped : 0 - 01c00000
init_memory_mapping: 0000000000000000-00000000377fe000
0000000000 - 0000400000 page 4k
0000400000 - 0037400000 page 2M
0037400000 - 00377fe000 page 4k
kernel direct mapping tables up to 377fe000 @ 10000-15000
RAMDISK: 3f735000 - 3f78fc32
Allocated new RAMDISK: 00011000 - 0006bc32
Move RAMDISK from 000000003f735000 - 000000003f78fc31 to 00011000 - 0006bc31
ACPI: RSDP 000fb9f0 00014 (v00 ACPIAM)
ACPI: RSDT 3f7a0000 0003C (v01 A_M_I_ OEMRSDT 08000801 MSFT 00000097)
ACPI: FACP 3f7a0200 00084 (v02 A_M_I_ OEMFACP 08000801 MSFT 00000097)
ACPI: DSDT 3f7a05b0 05050 (v01 A1028 A1028000 00000000 INTL 20051117)
ACPI: FACS 3f7ae000 00040
ACPI: APIC 3f7a0390 0005C (v01 A_M_I_ OEMAPIC 08000801 MSFT 00000097)
ACPI: MCFG 3f7a03f0 0003C (v01 A_M_I_ OEMMCFG 08000801 MSFT 00000097)
ACPI: OEMB 3f7ae040 00061 (v01 A_M_I_ AMI_OEM 08000801 MSFT 00000097)
ACPI: HPET 3f7a5600 00038 (v01 A_M_I_ OEMHPET 08000801 MSFT 00000097)
ACPI: SSDT 3f7aeb80 004F0 (v01 PmRef CpuPm 00003000 INTL 20051117)
ACPI: Local APIC address 0xfee00000
127MB HIGHMEM available.
887MB LOWMEM available.
mapped low ram: 0 - 377fe000
low ram: 0 - 377fe000
node 0 low ram: 00000000 - 377fe000
node 0 bootmap 0006c000 - 00072f00
(9 early reservations) ==> bootmem [0000000000 - 00377fe000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
#2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
#3 [0001000000 - 000167a084] TEXT DATA BSS ==> [0001000000 - 000167a084]
#4 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
#5 [000167b000 - 00016821fc] BRK ==> [000167b000 - 00016821fc]
#6 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000]
#7 [0000011000 - 000006bc32] NEW RAMDISK ==> [0000011000 - 000006bc32]
#8 [000006c000 - 0000073000] BOOTMAP ==> [000006c000 - 0000073000]
found SMP MP-table at [c00ff780] ff780
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
Normal 0x00001000 -> 0x000377fe
HighMem 0x000377fe -> 0x0003f7a0
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0003f7a0
On node 0 totalpages: 259887
free_area_init_node: node 0, pgdat c1548600, node_mem_map c1684200
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3951 pages, LIFO batch:0
Normal zone: 1744 pages used for memmap
Normal zone: 221486 pages, LIFO batch:31
HighMem zone: 256 pages used for memmap
HighMem zone: 32418 pages, LIFO batch:7
Using APIC driver default
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0xffffffff base: 0xfed00000
SMP: Allowing 2 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e2000
PM: Registered nosave memory: 00000000000e2000 - 0000000000100000
Allocating PCI resources starting at 3f800000 (gap: 3f800000:bf600000)
Booting paravirtualized kernel on bare hardware
NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
PERCPU: Embedded 13 pages/cpu @c2000000 s29720 r0 d23528 u2097152
pcpu-alloc: s29720 r0 d23528 u2097152 alloc=1*4194304
pcpu-alloc: [0] 0 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 257855
Kernel command line: root=/dev/disk/by-uuid/21e88bd5-5449-4926-8ed4-80fce8263ceb ro
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Initializing HighMem for node 0 (000377fe:0003f7a0)
Memory: 1023012k/1040000k available (4034k kernel code, 16100k reserved, 1396k data, 408k init, 130696k highmem)
virtual kernel memory layout:
fixmap : 0xfff1e000 - 0xfffff000 ( 900 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
.init : 0xc154e000 - 0xc15b4000 ( 408 kB)
.data : 0xc13f08c2 - 0xc154daf8 (1396 kB)
.text : 0xc1000000 - 0xc13f08c2 (4034 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:512
Console: colour VGA+ 80x25
console [tty0] enabled
hpet clockevent registered
HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Fast TSC calibration using PIT
Detected 1596.133 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 3193.27 BogoMIPS (lpj=5320443)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 24K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 5 MCE banks
CPU0: Thermal monitoring enabled (TM2)
using mwait in idle threads.
Performance Events: Atom events, Intel PMU driver.
... version: 3
... bit width: 40
... generic registers: 2
... value mask: 000000ffffffffff
... max period: 000000007fffffff
... fixed-purpose events: 3
... event mask: 0000000700000003
Checking 'hlt' instruction... OK.
ACPI: Core revision 20090903
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping 02
Booting processor 1 APIC 0x1 ip 0x6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 3193.98 BogoMIPS (lpj=5319968)
CPU: L1 I cache: 32K, L1 D cache: 24K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU1: Thermal monitoring enabled (TM2)
CPU1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping 02
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs
Total of 2 processors activated (6386.25 BogoMIPS).
CPU0 attaching sched-domain:
domain 0: span 0-1 level SIBLING
groups: 0 (cpu_power = 589) 1 (cpu_power = 589)
domain 1: span 0-1 level MC
groups: 0-1 (cpu_power = 1178)
CPU1 attaching sched-domain:
domain 0: span 0-1 level SIBLING
groups: 1 (cpu_power = 589) 0 (cpu_power = 589)
domain 1: span 0-1 level MC
groups: 0-1 (cpu_power = 1178)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 63
PCI: Not using MMCONFIG.
PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=5
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 63
PCI: MCFG area at e0000000 reserved in ACPI motherboard resources
PCI: Using MMCONFIG for extended config space
ACPI: EC: GPE = 0x1c, I/O: command/status = 0x66, data = 0x62
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:02.0: reg 10 32bit mmio: [0xf7f00000-0xf7f7ffff]
pci 0000:00:02.0: reg 14 io port: [0xdc00-0xdc07]
pci 0000:00:02.0: reg 18 32bit mmio pref: [0xd0000000-0xdfffffff]
pci 0000:00:02.0: reg 1c 32bit mmio: [0xf7ec0000-0xf7efffff]
pci 0000:00:02.1: reg 10 32bit mmio: [0xf7f80000-0xf7ffffff]
pci 0000:00:1b.0: reg 10 64bit mmio: [0xf7eb8000-0xf7ebbfff]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: PME# disabled
pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.3: PME# disabled
pci 0000:00:1d.0: reg 20 io port: [0xd400-0xd41f]
pci 0000:00:1d.1: reg 20 io port: [0xd480-0xd49f]
pci 0000:00:1d.2: reg 20 io port: [0xd800-0xd81f]
pci 0000:00:1d.3: reg 20 io port: [0xd880-0xd89f]
pci 0000:00:1d.7: reg 10 32bit mmio: [0xf7eb7c00-0xf7eb7fff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.0: quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: region 0480-04bf claimed by ICH6 GPIO
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0380 (mask 0003)
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0290 (mask 0007)
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 0068 (mask 0003)
pci 0000:00:1f.2: reg 10 io port: [0x00-0x07]
pci 0000:00:1f.2: reg 14 io port: [0x00-0x03]
pci 0000:00:1f.2: reg 18 io port: [0x00-0x07]
pci 0000:00:1f.2: reg 1c io port: [0x00-0x03]
pci 0000:00:1f.2: reg 20 io port: [0xffa0-0xffaf]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:03:00.0: reg 10 64bit mmio: [0xfbfc0000-0xfbffffff]
pci 0000:03:00.0: reg 18 io port: [0xec00-0xec7f]
pci 0000:03:00.0: PME# supported from D3hot D3cold
pci 0000:03:00.0: PME# disabled
pci 0000:00:1c.1: bridge io port: [0xe000-0xefff]
pci 0000:00:1c.1: bridge 32bit mmio: [0xfbf00000-0xfbffffff]
pci 0000:01:00.0: reg 10 32bit mmio: [0xfbef0000-0xfbefffff]
pci 0000:01:00.0: PME# supported from D0 D3hot
pci 0000:01:00.0: PME# disabled
pci 0000:00:1c.3: bridge 32bit mmio: [0xf8000000-0xfbefffff]
pci 0000:00:1c.3: bridge 64bit mmio pref: [0xf0000000-0xf6ffffff]
pci 0000:00:1e.0: transparent bridge
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P7._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 7 10 11 12 14 15)
vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: iomem range 0xfed13000-0xfed19fff has been reserved
system 00:08: ioport range 0x25c-0x25f has been reserved
system 00:08: ioport range 0x380-0x383 has been reserved
system 00:08: ioport range 0x400-0x41f has been reserved
system 00:08: ioport range 0x4d0-0x4d1 has been reserved
system 00:08: ioport range 0x800-0x87f has been reserved
system 00:08: ioport range 0x480-0x4bf has been reserved
system 00:08: iomem range 0x8c000000-0x8c01ffff has been reserved
system 00:08: iomem range 0xfed1c000-0xfed1ffff has been reserved
system 00:08: iomem range 0xfed20000-0xfed3ffff has been reserved
system 00:08: iomem range 0xfed50000-0xfed8ffff has been reserved
system 00:08: iomem range 0xffb00000-0xffbfffff has been reserved
system 00:08: iomem range 0xfff00000-0xffffffff could not be reserved
system 00:0a: iomem range 0xfec00000-0xfec00fff could not be reserved
system 00:0a: iomem range 0xfee00000-0xfee00fff has been reserved
system 00:0b: iomem range 0xe0000000-0xe3ffffff has been reserved
system 00:0c: iomem range 0x0-0x9ffff could not be reserved
system 00:0c: iomem range 0xc0000-0xcffff could not be reserved
system 00:0c: iomem range 0xe0000-0xfffff could not be reserved
system 00:0c: iomem range 0x100000-0x3f7fffff could not be reserved
pci 0000:00:1c.0: PCI bridge, secondary bus 0000:04
pci 0000:00:1c.0: IO window: 0x1000-0x1fff
pci 0000:00:1c.0: MEM window: 0x40000000-0x401fffff
pci 0000:00:1c.0: PREFETCH window: 0x00000040200000-0x000000403fffff
pci 0000:00:1c.1: PCI bridge, secondary bus 0000:03
pci 0000:00:1c.1: IO window: 0xe000-0xefff
pci 0000:00:1c.1: MEM window: 0xfbf00000-0xfbffffff
pci 0000:00:1c.1: PREFETCH window: 0x00000040400000-0x000000405fffff
pci 0000:00:1c.3: PCI bridge, secondary bus 0000:01
pci 0000:00:1c.3: IO window: 0x2000-0x2fff
pci 0000:00:1c.3: MEM window: 0xf8000000-0xfbefffff
pci 0000:00:1c.3: PREFETCH window: 0x000000f0000000-0x000000f6ffffff
pci 0000:00:1e.0: PCI bridge, secondary bus 0000:05
pci 0000:00:1e.0: IO window: disabled
pci 0000:00:1e.0: MEM window: disabled
pci 0000:00:1e.0: PREFETCH window: disabled
pci 0000:00:1c.0: enabling device (0104 -> 0107)
pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1c.3: enabling device (0106 -> 0107)
pci 0000:00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
pci 0000:00:1c.3: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 0 io: [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
pci_bus 0000:04: resource 0 io: [0x1000-0x1fff]
pci_bus 0000:04: resource 1 mem: [0x40000000-0x401fffff]
pci_bus 0000:04: resource 2 pref mem [0x40200000-0x403fffff]
pci_bus 0000:03: resource 0 io: [0xe000-0xefff]
pci_bus 0000:03: resource 1 mem: [0xfbf00000-0xfbffffff]
pci_bus 0000:03: resource 2 pref mem [0x40400000-0x405fffff]
pci_bus 0000:01: resource 0 io: [0x2000-0x2fff]
pci_bus 0000:01: resource 1 mem: [0xf8000000-0xfbefffff]
pci_bus 0000:01: resource 2 pref mem [0xf0000000-0xf6ffffff]
pci_bus 0000:05: resource 3 io: [0x00-0xffff]
pci_bus 0000:05: resource 4 mem: [0x000000-0xffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
pci 0000:00:02.0: Boot video device
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 363k freed
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: disabled - APM is not SMP safe.
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1262112860.302:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Slow work thread pool: Starting up
Slow work thread pool: Ready
NTFS driver 2.1.29 [Flags: R/W DEBUG].
fuse init (API version 7.13)
SGI XFS with security attributes, large block/inode numbers, no debug enabled
msgmni has been set to 1744
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pcieport 0000:00:1c.0: irq 24 for MSI/MSI-X
pcieport 0000:00:1c.0: setting latency timer to 64
pcieport 0000:00:1c.1: irq 25 for MSI/MSI-X
pcieport 0000:00:1c.1: setting latency timer to 64
pcieport 0000:00:1c.3: irq 26 for MSI/MSI-X
pcieport 0000:00:1c.3: setting latency timer to 64
ACPI: AC Adapter [AC0] (on-line)
input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
ACPI: Lid Switch [LID]
input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
ACPI: Sleep Button [SLPB]
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
ACPI: Power Button [PWRF]
ACPI: SSDT 3f7ae180 0023C (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
ACPI: SSDT 3f7ae450 00724 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-2 state
Marking TSC unstable due to TSC halts in idle
processor LNXCPU:00: registered as cooling_device0
ACPI: SSDT 3f7ae0b0 000CC (v01 PmRef Cpu1Ist 00003000 INTL 20051117)
ACPI: SSDT 3f7ae3c0 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20051117)
Switching to clocksource hpet
processor LNXCPU:01: registered as cooling_device1
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [TZ00] (53 C)
isapnp: Scanning for PnP cards...
ACPI: Battery Slot [BAT0] (battery present)
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
brd: module loaded
loop: module loaded
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: using broken periodic workaround
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf7eb7c00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000d400
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d480
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000d800
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1d.3: setting latency timer to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000d880
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver libusual
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
Using IPI No-Shortcut mode
registered taskstats version 1
Freeing unused kernel memory: 408k freed
BFS CPU scheduler v0.313 by Con Kolivas.
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
usb 1-5: new high speed USB device using ehci_hcd and address 2
usb 1-5: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
libata version 3.00 loaded.
ata_piix 0000:00:1f.2: version 2.13
ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi1 : ata_piix
scsi2 : ata_piix
ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
usb 1-8: new high speed USB device using ehci_hcd and address 4
ata1.00: ATA-7: ST980811AS, 3.ALC, max UDMA/133
ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 0/32)
elantech.c: assuming hardware version 2, firmware version 2.48
ata1.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access ATA ST980811AS 3.AL PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
usb 1-8: configuration #1 chosen from 1 choice
sd 1:0:0:0: [sda] Attached SCSI disk
elantech.c: Synaptics capabilities query result 0x00, 0x02, 0x64.
usb 5-1: new full speed USB device using uhci_hcd and address 2
input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input5
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with writeback data mode.
usb 5-1: configuration #1 chosen from 1 choice
Driver 'rtc_cmos' needs updating - please use bus_type methods
rtc_cmos 00:03: RTC can wake from S4
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, 114 bytes nvram, hpet irqs
udev: starting version 146
ATL1E 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
ATL1E 0000:03:00.0: setting latency timer to 64
rt2860sta: module is from the staging directory, the quality is unknown, you have been warned.
rt2860 0000:01:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
=== pAd = f825a000, size = 580808 ===
<-- RTMPAllocAdapterBlock, Status=0
rt2860 0000:01:00.0: setting latency timer to 64
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver rndis_host
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Linux agpgart interface v0.103
agpgart-intel 0000:00:00.0: Intel 945GME Chipset
agpgart-intel 0000:00:00.0: detected 7932K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
scsi 0:0:0:0: Direct-Access Single Flash Reader 1.00 PQ: 0 ANSI: 0
sd 0:0:0:0: [sdb] 1984000 512-byte logical blocks: (1.01 GB/968 MiB)
sd 0:0:0:0: [sdb] Write Protect is off
sd 0:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sdb] Assuming drive cache: write through
usb-storage: device scan complete
sd 0:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 0:0:0:0: [sdb] Assuming drive cache: write through
sd 0:0:0:0: [sdb] Attached SCSI removable disk
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
HDA Intel 0000:00:1b.0: setting latency timer to 64
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input6
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
EXT3 FS on sda3, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda2, internal journal
EXT3-fs: mounted filesystem with writeback data mode.
Adding 1951888k swap on /dev/sda1. Priority:-1 extents:1 across:1951888k SS
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
eeepc_laptop: Eee PC Hotkey Driver
eeepc_laptop: Hotkey init flags 0x41
eeepc_laptop: TYPE (2000000) not reported by BIOS, enabling anyway
eeepc_laptop: PANELPOWER (4000000) not reported by BIOS, enabling anyway
eeepc_laptop: Get control methods supported: 0x6101713
input: Asus EeePC extra buttons as /devices/platform/eeepc/input/input7
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
[drm] Initialized drm 1.1.0 20060810
pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:02.0: setting latency timer to 64
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
ATL1E 0000:03:00.0: irq 27 for MSI/MSI-X
RX DESC f6a56000 size = 2048
<-- RTMPAllocTxRxRingMemory, Status=0
--> Error 2 opening /etc/Wireless/RT2860STA/RT2860STA.dat
1. Phy Mode = 0
2. Phy Mode = 0
RTMPSetPhyMode: channel is out of range, use first channel=1
3. Phy Mode = 0
MCS Set = 00 00 00 00 00
<==== RTMPInitialize, Status=0
0x1300 = 00073200
===>rt_ioctl_giwscan. 24(24) BSS returned, data->length = 2895
CPU0 attaching NULL sched-domain.
CPU1 attaching NULL sched-domain.
CPU0 attaching sched-domain:
domain 0: span 0-1 level SIBLING
groups: 0 (cpu_power = 589) 1 (cpu_power = 589)
domain 1: span 0-1 level MC
groups: 0-1 (cpu_power = 1178)
CPU1 attaching sched-domain:
domain 0: span 0-1 level SIBLING
groups: 1 (cpu_power = 589) 0 (cpu_power = 589)
domain 1: span 0-1 level MC
groups: 0-1 (cpu_power = 1178)
ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
===>rt_ioctl_giwscan. 27(27) BSS returned, data->length = 3340
===>rt_ioctl_giwscan. 24(24) BSS returned, data->length = 3033
==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
===>rt_ioctl_giwscan. 33(33) BSS returned, data->length = 4186
===>rt_ioctl_giwscan. 31(31) BSS returned, data->length = 3779
===>rt_ioctl_giwscan. 27(27) BSS returned, data->length = 3232
===>rt_ioctl_giwscan. 26(26) BSS returned, data->length = 3185
ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
===>rt_ioctl_giwscan. 29(29) BSS returned, data->length = 3623
===>rt_ioctl_giwscan. 24(24) BSS returned, data->length = 2955
===>rt_ioctl_giwscan. 21(21) BSS returned, data->length = 2593
===>rt_ioctl_giwscan. 28(28) BSS returned, data->length = 3512
===>rt_ioctl_giwscan. 31(31) BSS returned, data->length = 3816
===>rt_ioctl_giwscan. 32(32) BSS returned, data->length = 3932
exe[2947]: segfault at 5f ip 085642ae sp b6575a50 error 4 in chrome[8048000+20dc000]
exe[2958]: segfault at 1692e8c6 ip b6c174cb sp b64b5a48 error 6 in libstdc++.so.6.0.13[b6bc1000+e8000]
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
===>rt_ioctl_giwscan. 29(29) BSS returned, data->length = 3614
wlan0: no IPv6 routers present
===>rt_ioctl_giwscan. 30(30) BSS returned, data->length = 3706
===>rt_ioctl_giwscan. 22(22) BSS returned, data->length = 2758
===>rt_ioctl_giwscan. 33(33) BSS returned, data->length = 4063
===>rt_ioctl_giwscan. 29(29) BSS returned, data->length = 3631
===>rt_ioctl_giwscan. 30(30) BSS returned, data->length = 3633
NOTE: I load eeepc-laptop via rc.local to save time. I don't have any other hardware issues that I can think of.

Got it. I tried booting with MOD_AUTOLOAD set to yes, and it was working fine. Looks like I needed to specify some more modules in my list.

[Solved]NVIDIA with primusrun slower then integrated Intel ?!

$ vblank_mode=0 primusrun glxspheres64
OpenGL Renderer: GeForce GT 620M/PCIe/SSE2
180.209469 frames/sec - 201.113767 Mpixels/sec
$ vblank_mode=0 glxspheres64
OpenGL Renderer: Mesa DRI Intel(R) Ivybridge Mobile
215.091464 frames/sec - 240.042073 Mpixels/sec
HOW ?!?!?
Last edited by artem.jackson (2015-01-20 09:26:20)

Primusrun has overhead in copying frames from the virtual display to the actual display. You have a very low end Nvidia card and this overhead decimates performance so much the whole thing ends up slower than using the Intel GPU which has no such overhead. Primusrun is still basically a hack, not a proper Optimus solution.
It's also possible that because glxspheres is so simple, this overhead plays a much bigger role than with something more demanding of the GPU. Try a proper demo or an actual game, you might see a different picture then.

Custom kernel 2.6.25 and nvidia

I have compiled a custom kernel the 'traditional' way, that is, make and make modules_install and now I am having trouble getting the nvidia driver to work
I usually just install it through pacman, but that doesn't work with the custom kernel.
So my next step was to follow the wiki.
I changed the kernel names in the PKGBUILD and nvidia.install that i got from my abs tree, and when I install with makepkg -i -c everything goes well.
However, when I try to start X again, it crashes and says it cannot find the NVIDIA kernel module. I don't fully understand everything in the PKGBUILD and it is quite possible there is some other line or path that needs to be changed. Please, I am at my wit's end.
Here are my PKGBUILD and nvidia.install
# $Id: PKGBUILD 356 2008-04-18 22:56:27Z aaron $
# Maintainer : Thomas Baechler <[email protected]>
pkgname=nvidia-DarkTower
pkgver=169.12
_kernver='2.6.25-DarkTower'
pkgrel=2
pkgdesc="NVIDIA drivers for kernel26."
arch=('i686' 'x86_64')
[ "$CARCH" = "i686" ] && ARCH=x86
[ "$CARCH" = "x86_64" ] && ARCH=x86_64
url="http://www.nvidia.com/"
depends=('kernel26>=2.6.24.3-4' 'kernel26<=2.6.25-0' 'nvidia-utils')
conflicts=('nvidia-96xx' 'nvidia-71xx' 'nvidia-legacy')
license=('custom')
install=nvidia.install
source=(http://us.download.nvidia.com/XFree86/Linux-$ARCH/${pkgver}/NVIDIA-Linux-$ARCH-${pkgver}-pkg0.run)
md5sums=('e7aaca79c846e34cfe8111040bfee2d0')
[ "$CARCH" = "x86_64" ] && md5sums=('843a1e8bc1923ba2e4b60f6fab31ad3b')
build()
# Extract
cd $startdir/src/
sh NVIDIA-Linux-$ARCH-${pkgver}-pkg0.run --extract-only
cd NVIDIA-Linux-$ARCH-${pkgver}-pkg0
# Any extra patches are applied in here...
cd usr/src/nv/
ln -s Makefile.kbuild Makefile
make SYSSRC=/lib/modules/${_kernver}/build module
# install kernel module
mkdir -p $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/video/
install -m644 nvidia.ko $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/video/
sed -i -e "s/KERNEL_VERSION='.*'/KERNEL_VERSION='${_kernver}'/" $startdir/*.install
# arg 1: the new package version
post_install() {
KERNEL_VERSION='2.6.25-DarkTower'
depmod -v $KERNEL_VERSION > /dev/null 2>&1
# arg 1: the new package version
# arg 2: the old package version
post_upgrade() {
post_install $1
rmmod nvidia || echo 'In order to use the new nvidia module, exit Xserver and unload it manually.'
# arg 1: the old package version
post_remove() {
KERNEL_VERSION='2.6.25-DarkTower'
depmod -v $KERNEL_VERSION > /dev/null 2>&1
op=$1
shift
$op $*
Last edited by ManOnONeWheel (2008-05-07 00:41:50)

I don't use Arch package for nvidia as script is unable to install modules on several kernels at the same time and I want to boot to X irrelevant of kernel loaded. I never had any problems with custom kernels 2.6.25 and nvidia 169 or 173
current status:
$ find /lib/modules/ -name nvidia.ko
/lib/modules/2.6.25-zen0-GIGUE/kernel/drivers/video/nvidia.ko
/lib/modules/2.6.25-zen1-preview3-FADO/kernel/drivers/video/nvidia.ko
/lib/modules/2.6.25-zen1-SARABANDE/kernel/drivers/video/nvidia.ko
/lib/modules/2.6.25-zen1-GAVOTTE/kernel/drivers/video/nvidia.ko
all boots fine, none crash/freeze. Never patched 169 or 173
Well, it looks like the 169 installer would always put nvidia.ko in the /lib/modules/2.6.24 directory, no matter if i was currentlyusing a different kernel or not so im not sure what is going on there.
must be some quirk on your box. Have not seen this.
Last edited by broch (2008-05-08 01:43:13)

Virtualbox and a custom kernel

Virtualbox works fine with Arch's default kernel, but not with my custom kernel, although it used to. I haven't used it in a month or two, and have done updates since then. The custom kernel I'm using on all three machines I'll be talking about is vanilla 3.0.3 + tuxonice. "Mercury" and "Aesculapius" both had their kernels built with a slightly modified config from "Posidon". At some point in time, VBox has worked on all of them. It is currently broken on Posidon and Aesculapius but works on Mercury. Aesculapius is up to date as of yesterday (April 28th). Posidon was last updated April 20th. Mercury was last updated March 28th.
- It's not (just) the kernel version. I've tried vanilla 3.3.3 with the same config on Aesculapius. VBox was still broken. (VBox worked with Arch's linux 3.3.3 on Aesculapius.)
- It's not (just) the config. Mercury (on which VBox works) has its kernel built from the same config as Posidon (with the processor optimization changed from Intel Dual Core to Intel Atom and a module for an Atheros wireless card and the built-in webcam added. ca0106 is removed and intel-hda is added.) Aesculapius was built from the same config as Posidon (with processor optimization changed from Intel Dual Core to Intel Pentium 4, ca0106 removed and emu101k(?) added, with a few other modules for USB webcams added.)
- I have virtualbox-source installed on all three machines, and the modules were built with no complaint with /usr/bin/vboxbuild since the last updates of any package.
- I have vboxdrv, vboxnetadp, and vboxnetflt modules loaded when attempting to start VMs.
"Broken" means:
- When starting a VM in VBox, a progress bar appears, "Starting virtual machine ..." and hangs at 0%. Soon a second progress bar appears, "Starting virtual machine ... (2/2)" and hangs at 20%. I cannot close the VM window except by killing all instances of VirtualBox, VBoxSVC, and VBoxXPCOMIPCD .
- dmesg contains this:
[ 4639.150180] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 4645.606088] BUG: unable to handle kernel paging request at 19330825
[ 4645.606094] IP: [<f8b7cad9>] VBoxHost_RTR0MemObjGetPagePhysAddr+0x13/0x67 [vboxdrv]
[ 4645.606106] *pde = 00000000
[ 4645.606108] Oops: 0000 [#1] PREEMPT SMP
[ 4645.606112] Modules linked in: fuse lgdt330x cx88_dvb videobuf_dvb cx88_vp3054_i2c nvidia(P) tuner_simple tuner_types tda9887 tda8290 snd_ca0106 snd_ac97_codec tuner cx8800 cx8802 cx88_alsa cx88
xx tveeprom btcx_risc videobuf_dma_sg videobuf_core i2c_algo_bit ac97_bus snd_rawmidi e1000e vboxnetflt vboxnetadp vboxdrv
[ 4645.606131]
[ 4645.606134] Pid: 2481, comm: VirtualBox Tainted: P 3.0.3-toi #5 MapleTronic D975XBX2/D975XBX2
[ 4645.606139] EIP: 0060:[<f8b7cad9>] EFLAGS: 00210212 CPU: 1
[ 4645.606145] EIP is at VBoxHost_RTR0MemObjGetPagePhysAddr+0x13/0x67 [vboxdrv]
[ 4645.606148] EAX: 00000001 EBX: f5142010 ECX: 19330825 EDX: 19331825
[ 4645.606150] ESI: f8848000 EDI: f5133c10 EBP: e649ddcc ESP: e649dd60
[ 4645.606152] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[ 4645.606155] Process VirtualBox (pid: 2481, ti=e649c000 task=f517ce60 task.ti=e649c000)
[ 4645.606157] Stack:
[ 4645.606158] f8c673d8 f49d5110 00000000 00000000 f8cd585c f5142054 eda1b814 f
5a8a270
[ 4645.606164] e67bf480 00000085 0001f50a 0001f50a f514204c f5142054 00025000 00025000
[ 4645.606170] 00000025 f8822000 00000000 000009a0 f517ce60 00200246 00200246 000003b1
[ 4645.606176] Call Trace:
[ 4645.606185] [<c109f394>] ? __free_one_page+0xe4/0x1ba
[ 4645.606191] [<c10a888e>] ? zone_page_state_add+0x12/0x1f
[ 4645.606195] [<c109f510>] ? free_pcppages_bulk+0xa6/0xb6
[ 4645.606201] [<c119e2db>] ? avc_has_perm_noaudit+0x2d0/0x2da
[ 4645.606208] [<f8b7a177>] ? supdrvIOCtl+0x10a7/0x1fee [vboxdrv]
[ 4645.606216] [<f8b7d4c3>] ? rtR0MemAllocEx+0x4a/0x9d [vboxdrv]
[ 4645.606222] [<f8b7624f>] ? VBoxDrvLinuxIOCtl_4_1_12+0xea/0x16b [vboxdrv]
[ 4645.606228] [<f8b76165>] ? SUPR0Printf+0x42/0x42 [vboxdrv]
[ 4645.606232] [<c10cfa49>] ? do_vfs_ioctl+0x42d/0x463
[ 4645.606235] [<c10cfac3>] ? sys_ioctl+0x44/0x65
[ 4645.606239] [<c13c214c>] ? sysenter_do_call+0x12/0x22
[ 4645.606241] Code: 8d 34 8d fc ff ff ff 89 4c 24 04 e9 5c ff ff ff 83 c4 08 5b 5e 5f 5d c3 8b 0f 8b 47 04 8d 91 00 10 00 00 81 fa ff 1f 00 00 76 45
[ 4645.606261] 39 10 12 61 19 75 3d 55 89 e5 57 53 8b 51 08 8d 5a ff 83 fb
[ 4645.606271] EIP: [<f8b7cad9>] VBoxHost_RTR0MemObjGetPagePhysAddr+0x13/0x67 [vboxdrv] SS:ESP 0068:e649dd60
[ 4645.606279] CR2: 0000000019330825
[ 4645.606282] ---[ end trace 41ed8e68e0cd1714 ]---
- The vboxdrv module cannot be unloaded until after a reboot.
- Hibernation (tuxonice) fails back to X.
- Shutdown freezes some time after X is stopped. I see no messages in the console other than those left over from start up.
Here are the packages (and versions) installed on Mercury (VBox works) (pastebinned to cut post length): http://bpaste.net/show/28064/
and for Posidon (VBox is broken): http://bpaste.net/show/28063/
and for your convenience, the diff -u: http://bpaste.net/show/28065/
What package(s) is/are causing the problem? I've already tried downgrading linux-api-headers and glibc to no effect. Alternately, what options should I change on my custom kernels? I can post some kernel configs if that would be helpful.
Last edited by onexused (2012-04-29 19:31:23)

I got the same problem with custom kernel-netbook, vboxdrv is freshly built and loaded, but I got two progress bars, one at 0% other at 20% and zombie unclosable window of hanged VM. Searching for solution...
Got it! Kernel was compiled with GCC 4.6, while modules with GCC 4.7.
Last edited by randomize46 (2012-06-01 08:04:06)

[solved] Nvidia with custom kernel

Similar Messages

Maybe you are looking for