2.6.32-ARCH + p54pci module + firmware

Problem: Setting up p54pci like it should, locks up the computer around +- 30 tcp connections (guesswork based on torrent GUI's)
To set this up in arch you would:
* block the module prism54 from loading so p54pci can load
* install the right firmware for your kernel/hardware http://wireless.kernel.org/en/users/Drivers/p54
on kernel 2.6.32-ARCH this would mean adding 2.13.12.0.arm as isl3886pci in the firmware folder
This worked flawless in Opensuse 11.2 (Ubuntu ships with prism54 firmware, i don't know what they use)
It freezes in ARCH when torrent Gui's report around 30 connections
I am currently using firmware 2.7.0.0.arm renamed to isl3886pci (shouldn't even work, this is for old kernels)
dmesg =>
p54pci 0000:04:05.0: firmware: requesting isl3886pci
phy0: p54 detected a LM86 firmware
phy0: you are using an obsolete firmware. visit http://wireless.kernel.org/en/users/Drivers/p54 and grab one for "kernel >= 2.6.28"!
This is much more stable, but it still crashes occasionaly. and much more random. I can still make it crash by allowing alot of connections in a torrent app combined with high bandwidth saturation
Last edited by yannickkiekens (2010-01-12 04:56:20)

Arm-the-Homeless wrote:OSS isn't working on 2.6.32-ARCH for me.
EDIT: For some reason, the kernel26-headers package wasn't installed. O_O
Whoops.
is the first time when kernel26-headers are splitted from kernel26. our packages have to be fixed as well by adding to makedepends=(kernel26-headers)

Similar Messages

  • Arch update - modules gone!

    I just updated Arch, which resultet in most of my modules went missing. I've read that a lot of people had problems with wireless and the only step needed was modprobe ath5k (which is the card I use) but when I try to do it I get: module ath5k could not be found. The same goes for all my sound modules.
    Any ideas on how to solve this. (My eth0 is gone aswell, so I'm pretty locked down )
    Thanks.
    Martin.

    Thanks for the help.
    But the way I solved it was to visit a pacman mirror and download the kernel and kernel-firmware from there and do pacman -U package.pkg.tar.gz
    It installed the new kernel with the modules and then all my problems were solved.
    Thanks for your time.

  • [SOLVED]3.18.5-1-ARCH + system-modules-load.service on Macbook Pro 9,2

    After upgrading from 3.18.4-1-ARCH to 3.18.5-1-ARCH this weekend, my systemd service system-modules-load fails during bootup. I checked out
    # systemctl status system-modules-load
    and found nothing but a warning that my journal has been rotated and the log output is incomplete. I have not hunted down the log or rooted through dmesg as of yet - I need my system functional while working during the week, so I downgraded my kernel back to 3.18.4 for now (under which system-modules-load loads fine). I will reinstall 3.18.5 next weekend and see if I can locate the problem - this post is just a feeler to see if anyone else is encountering this problem with the latest kernel.
    Last edited by Olorin (2015-02-06 03:08:31)

    Yep. It was my own fault. I had been using the b43 driver for my BCM4331 wifi card, and recently switched to broadcom-wl. However, I still was trying to load b43 in /etc/modules-load even though I had removed the driver and module from my system. Not sure why my system only started complaining in 3.18.5, but in any case removing the offending .conf file solved the problem. Thanks, graysky.

  • HP VC Flex-10 Enet Module Firmware Upgrade.

    Hi All,
    Have just a quick question about the firmware upgrade on the HP VC Flex-10 Enet Module, We have recieved two new C7000 Chassis and I have tryed to upgrade the firmware on the HP VC Flex-10 Enet Module's they started at version 2.33 so I updated them to version 2.34, Now there is a version 3.15 out in the HP web site but each time I try to upgrade the firmware to this it will just sit there and do nothing.
    I'm upgradeing the firmware from the HP Virtual Connect Manager/Tools/Firmware Management and the .bin file is around 120Mb Not to sure if this is too big for the HP Virtual Connect Manager or not.
    If anyone has been able to upgrade to v3.15 can you please let me know how you got it to upgrade and also if there are issues with this version please let me know.
    Thanks for your time.
    lost872

    Yesterday, I just upgraded from 2.33 to 3.16.
    I encountered problems :
         VCM must be in BAY 1
         VCM must me alone in BAY 1 or with a VCM module in BAY 2 (I tryed with GbE2c in BAY 2)
    I used vcsu 1.5.2 and all workded fine.
    Before these upgrades, all the blade and the enclosure (C3000) where in lastest version.
    BIOS : 2010-25-10 B
    iLo2 : 2.05
    OA : 3.21
    Then I plugged the VCM and made the upgrade.

  • MSI Radio module firmware flashing troubles

    Help!!
    I've just tried to flash the radio module with the latest software and possibly beacuse the radio was on at the time, the flashing failed and I'm left with a dead radio.   There's no display, backlight or clock and none of the buttons work. I suspect it's just erased the flash.
    I've tried to reflash from the file I downloaded but it just fails each time.
    Let this be a lesson to you all. Don't upgrade the radio firmware when it's on!!!!  
    Does anyone have any ideas how to solve this?? Is there a jumper link inside to reset the flash???
    Any help is much appreciated!!
    Many thanks,
    Cybermush

    Hi ya,
    same happened to me!
    Here's what I did:
    - Clear the CMOS as described in the manual (Power Off, unplug power, J2 set to 2-3, set to 1-2 again)
    - Power on and do BIOS and radio flash upgrade
    It works again!!

  • Info about the linux-firmware package and rt2780-usb-fw

    Hello,
    I have a have question about the linux-firmware package in the repo.
    Recently there was an update for this package and when I checked its contents I saw that it also updates rt2870usb-fw.
    Maybe I am a bit confused about the all kernel modules / firmware, but since I need to compile the latest kernel (linux-mainline from AUR) to get my buffalo wireless usb work(my rt2870 is supported from rc4), would it be possible to update only this package and use the kernel in the arch repo?
    I can't test it myself because I am out of town for while.
    Thank you

    Hello,
    I have a have question about the linux-firmware package in the repo.
    Recently there was an update for this package and when I checked its contents I saw that it also updates rt2870usb-fw.
    Maybe I am a bit confused about the all kernel modules / firmware, but since I need to compile the latest kernel (linux-mainline from AUR) to get my buffalo wireless usb work(my rt2870 is supported from rc4), would it be possible to update only this package and use the kernel in the arch repo?
    I can't test it myself because I am out of town for while.
    Thank you

  • [SOLVED] Using Apple's UEFI boot menu with Arch

    Hello,
          I've successfully installed arch on my mid-2012 (5,1) 11" Macbook Air, and now I'm trying to get an entry in apple's boot menu (the one that shows when you hold 'option' when starting the computer).  From the author of rEFInd's install instructions (http://www.rodsbooks.com/refind/installing.html#osx) it sounds like I can just add some files to `/dev/sda1` (a vfat directory that contains the stuff needed to boot macos), and then run apple's `bless` command and we're good to go.  Unfortunately I've tried this a bunch of different ways, to no avail.  I think some of my failure is simply because of a misunderstanding of UEFI, here are some questions I (partially) don't understand and my current understanding of them:
    1. Do I even need a bootloader on a pure GPT/UEFI system?  It seems like the answer is no, and I can just use the UEFI firmware and the linux kernel to load Arch (per: https://wiki.archlinux.org/index.php/UE … ux_Kernel).  Note: I'd like to have as little software between the firmware and the os, for speed and simplicity.  However, I'd still like to dual boot, but it sounds like the firmware can handle showing me a menu as long as there are entries pointing to parts of each OS.
    2. Will grub/rEFInd/syslinux do some of the work for me initially/on a kernel update?  I think the answer is yes, which would be motivation (esp when I need to update the kernel) to just use a multibootloader and have it handle arch and the firmware pass control to either that or MacOS
    3. Will `efibootmgr` brick my mac?  https://wiki.archlinux.org/index.php/UE … FI_systems says it will, but I think the `grub-install` command uses `efibootmgr`, so should I not try grub on here (this package: https://www.archlinux.org/packages/core … fi-x86_64/ ).  Also some of the other packages (like rEFInd-efi) depend on efibootmgr, so does that mean any kind of an install from them (a command from the package, not the `pacman -S pkg` command) will also brick my system? (see rEFInd-efi dependencies: https://www.archlinux.org/packages/extr … efind-efi/ )
    I've been searching a bunch of different things, output of the `bless` commands I've been running, and have found the following:
    * https://bbs.archlinux.org/viewtopic.php?id=148647
    * Using OSX to install rEFInd manually (moving the files around and using OSXs `bless` command) http://www.rodsbooks.com/refind/installing.html#osx , I used the rEFInd files from Archs repos: https://www.archlinux.org/packages/extr … efind-efi/ )
    * The Wiki docs on rEFInd https://wiki.archlinux.org/index.php/UE … ing_rEFInd
    To summarize, I'm trying to set up a dual boot between MacOS (installed) and Arch (also installed, there's just no way to boot it on my system yet) using Apple's built in menu that deals with the EFI partition on /dev/sda1 .  Thanks in advance for any help!
    end
    Last edited by enduser (2013-03-18 12:00:17)

    enduser wrote:I've successfully installed arch on my mid-2012 (5,1) 11" Macbook Air, and now I'm trying to get an entry in apple's boot menu (the one that shows when you hold 'option' when starting the computer).  From the author of rEFInd's install instructions (http://www.rodsbooks.com/refind/installing.html#osx) it sounds like I can just add some files to `/dev/sda1` (a vfat directory that contains the stuff needed to boot macos), and then run apple's `bless` command and we're good to go.
    Not quite. That makes a boot loader bootable, but it doesn't add an entry to Apple's boot manager menu. There's a blog post somewhere by Matthew Garrett that describes the steps necessary to add something to Apple's boot manager, but I couldn't find it in a quick Web search. Maybe you'll have better luck, or be able to track down the same information somewhere else. As I recall, it involves using a separate HFS+ volume, creating two or three dummy files, and using "bless" in OS X.
    1. Do I even need a bootloader on a pure GPT/UEFI system?
    Yes, you do need a boot loader. It's important to distinguish between a boot loader and a boot manager, though. The former is a program that loads a kernel, and perhaps associated data, into memory and transfers control to the kernel. A boot manager presents a user interface that enables you to select which OS (or which boot loader) to launch. A boot manager is not strictly necessary, and Apple's EFI implementation includes its own simple boot manager, which is what you've been unsuccessful in configuring.
    Note: I'd like to have as little software between the firmware and the os, for speed and simplicity.  However, I'd still like to dual boot, but it sounds like the firmware can handle showing me a menu as long as there are entries pointing to parts of each OS.
    Many people make do with the firmware's own boot manager, but this can be rather inflexible. I'm not even sure if Apple's boot manager can handle passing options to Linux kernels' EFI stub loaders. This ability is not absolutely required, but without it you must compile your options into your kernel at compile time, which greatly reduces flexibility since you can't modify the options on a per-boot basis -- say, to boot into single-user mode if this is required.
    2. Will grub/rEFInd/syslinux do some of the work for me initially/on a kernel update?
    The usual Arch Linux method of handling kernel updates is to overwrite an old kernel with a new one, so no boot loader/boot manager changes are required. If you want to keep numbered kernels around (as most other distributions do), GRUB provides scripts that can help automate changes, but they are required in the grub.cfg file. rEFInd can auto-detect boot loaders, and if you're using the EFI stub loader, that means that the kernel is its own boot loader, and with a proper configuration, rEFInd can detect new kernels without changing its configuration file.
    SYSLINUX has some very early and very experimental EFI support. The one and only time I tried it (about a month ago), it wouldn't compile for me. (I don't know of a precompiled binary available on the Web -- the support is that new!) I don't recommend trying it unless somebody who's gotten it to work offers to help you personally.
    3. Will `efibootmgr` brick my mac?  https://wiki.archlinux.org/index.php/UE … FI_systems says it will, but I think the `grub-install` command uses `efibootmgr`, so should I not try grub on here (this package: https://www.archlinux.org/packages/core … fi-x86_64/ ).
    There were reports of efibootmgr damaging Mac firmware several months ago (I believe over a year ago). Since then I've seen claims that this problem has been fixed with recent kernels (3.0 and later, IIRC), but I've seen no substantiation one way or the other. Overall, I recommend caution....
    Also some of the other packages (like rEFInd-efi) depend on efibootmgr, so does that mean any kind of an install from them (a command from the package, not the `pacman -S pkg` command) will also brick my system? (see rEFInd-efi dependencies: https://www.archlinux.org/packages/extr … efind-efi/ )
    On a Mac, I recommend installing rEFInd (or any other EFI boot loader) from OS X rather than from Linux. (Note that I'm rEFInd's maintainer, so that's an official recommendation from the software's developer.) Offhand, I don't know if the Arch package for rEFInd runs efibootmgr automatically on boot or just has it as a dependency because efibootmgr is the usual way to register a boot loader on UEFI systems. If the latter, it should be safe to install the Arch package for rEFInd, copy its files, and then reboot to OS X to run bless on it. It would be just as easy, if not easier, to install it completely from OS X, though.

  • Uninstall all CPAN-installed Perl modules

    A while back, there was a large perl upgrade which required rebuilding of manually-installed Perl modules. At the time, I did not take much of any action as I did not use any applications which depended on CPAN-installed modules -- all I did was to uninstall some older Perl apps which I no longer used.
    Unfortunately, that has recently changed.
    Though I know exactly which modules I need to have on my system when all is said and done, I have no idea how to uninstall all of the old ones which came from the CPAN shell. Does anyone know how to do so?

    rowdog wrote:
    Well, modules are just files so, if you're lucky, the easy way is to find the directory where the modules were installed and delete them.
    If you're unlucky, you've intermingled CPAN modules with those installed by Arch. If that's the case, you might be able to delete each module by hand but you need to be careful not to wipe out Arch's modules. This is slow and hazardous work so please be careful.
    My guess would be that the files are installed in /usr/lib/perl5/site_perl, because mine's empty and that's what it's for. The exact location is controlled by whatever you used to install the modules. (cpan probably, but there are others.)
    If you're really lucky, you can get away with
    cd /usr/lib/perl5/site_perl
    rm -rf .
    Yes, I do have such bad luck. I have used the CPAN.pm shell, the AUR, and pacman to install Perl modules. I shall do more research regarding exactly what goes where during a CPAN.pm-based install. I am not at my own computer so I cannot do all of this now. I will get back to you on this tomorrow. Thank you for your response.
    Last edited by Bushman (2011-07-31 13:10:00)

  • [SOLVED] Cannot load the acerhdf module

    Hi all,
    I'm trying to load the acerhdf module that should control the fan-speed for my Acer 1810TZ. I'm following the README.txt and the ArchWiki but after have compiled and installed the module I'm not able to load it.
    [gianluca@gianluca-laptop downloads]$ cd acerhdf_kmod && make
    make -C /lib/modules/2.6.39-ARCH/build SUBDIRS=/home/gianluca/downloads/acerhdf_kmod modules
    make[1]: Entering directory `/usr/src/linux-2.6.39-ARCH'
    Building modules, stage 2.
    MODPOST 1 modules
    make[1]: Leaving directory `/usr/src/linux-2.6.39-ARCH'
    [gianluca@gianluca-laptop acerhdf_kmod]$ sudo make install
    make -C /lib/modules/2.6.39-ARCH/build SUBDIRS=/home/gianluca/downloads/acerhdf_kmod modules
    make[1]: Entering directory `/usr/src/linux-2.6.39-ARCH'
    Building modules, stage 2.
    MODPOST 1 modules
    make[1]: Leaving directory `/usr/src/linux-2.6.39-ARCH'
    [ -d /lib/modules/2.6.39-ARCH/updates ] || mkdir /lib/modules/2.6.39-ARCH/updates
    cp acerhdf.ko /lib/modules/2.6.39-ARCH/updates/
    depmod -a
    [gianluca@gianluca-laptop acerhdf_kmod]$ modprobe acerhdf
    FATAL: Error inserting acerhdf (/lib/modules/2.6.39-ARCH/kernel/drivers/platform/x86/acerhdf.ko.gz): Operation not permitted
    [gianluca@gianluca-laptop acerhdf_kmod]$ sudo modprobe acerhdf
    FATAL: Error inserting acerhdf (/lib/modules/2.6.39-ARCH/kernel/drivers/platform/x86/acerhdf.ko.gz): Invalid argument
    Besides, in the configuration file (the acerhdf.c file that you can find in the sources package) my BIOS (official Acer v1.3314 for the 1810TZ) is supported.
    What am I doing wrong?
    Thank you for your help,
    Gianluca
    Last edited by I am Gianluca (2011-07-13 20:17:43)

    Try using this package instead of building it yourself: http://aur.archlinux.org/packages.php?ID=23686
    When installing the package let it overwrite any existing files as these will all be files that you have created by building it yourself.

  • Dell PowerVault MD3600f - Unable to upgrade firmware - Data validation error

    Upgrade Controller Firmware wizard reports the following error.
    1 problem detected.
    Data validation error: The storage array cannot be upgraded as host port type representation in Controller A did not match with those of Controller B. Contact a technical support representative to resolve this issue.
    What does this mean? and how to fix it.

    Hi,
    yes 100% the error is reported from the dell mdsm software.
    steps.
    1. open mdsm application
    2. right click on powervault md3600f
    3. select upgrade raid controller module firmware
    4. upgrade raid controller module screen apears and refreshes unit(s) status changes to no upgradeable.
    5. error apears in the details window.
    6. press view log.
    [May 17, 2013 9:25:15 AM] [MD3600] [pre-upgrade tests] [pre-upgrade tests start]
    Pre-upgrade tests started
    [May 17, 2013 9:25:37 AM] [MD3600] [pre-upgrade tests] [check RAID controller module state]
    Test passed - RAID controller module 1
    [May 17, 2013 9:25:37 AM] [MD3600] [pre-upgrade tests] [check RAID controller module state]
    Test passed - RAID controller module 0
    [May 17, 2013 9:25:38 AM] [MD3600] [pre-upgrade tests] [check spm database]
    Test passed - RAID controller module 1
    [May 17, 2013 9:25:39 AM] [MD3600] [pre-upgrade tests] [check spm database]
    Test passed - RAID controller module 0
    [May 17, 2013 9:25:39 AM] [MD3600] [pre-upgrade tests] [Physical Disks Unavailable]
    Test passed
    [May 17, 2013 9:25:42 AM] [MD3600] [pre-upgrade tests] [check configuration database]
    Test passed
    [May 17, 2013 9:25:42 AM] [MD3600] [pre-upgrade tests] [check physical disks]
    Test passed
    [May 17, 2013 9:25:42 AM] [MD3600] [pre-upgrade tests] [check disk groups and disk pools]
    Test passed
    [May 17, 2013 9:25:42 AM] [MD3600] [pre-upgrade tests] [check hot spares]
    Test passed
    [May 17, 2013 9:25:42 AM] [MD3600] [pre-upgrade tests] [check current operations]
    Test passed
    [May 17, 2013 9:25:42 AM] [MD3600] [pre-upgrade tests] [check virtual disks]
    Test passed
    [May 17, 2013 9:25:43 AM] [MD3600] [pre-upgrade tests] [check internal data validity]
    Data validation error: The storage array cannot be upgraded as host port type representation in Controller A did not match with those of Controller B. Contact a technical support representative to resolve this issue.
    [May 17, 2013 9:25:44 AM] [MD3600] [pre-upgrade tests] [check event log]
    The event log was cleared within the last 24 hours (event type: 100).
    [May 17, 2013 9:25:45 AM] [MD3600] [pre-upgrade tests] [check event log]
    Test passed
    [May 17, 2013 9:25:45 AM] [MD3600] [pre-upgrade tests] [pre-upgrade tests complete] [0h 0m 30s]
    Pre-upgrade test(s) failure - the storage array cannot be upgraded in its present state

  • Kernel Modules

    I get this output when I run a script finding all my modules:
    agpgart.ko
    amd74xx.ko
    ata_generic.ko
    button.ko
    cdrom.ko
    ehci-hcd.ko
    evdev.ko
    fan.ko
    fb_ddc.ko
    forcedeth.ko
    hid.ko
    i2c-algo-bit.ko
    i2c-core.ko
    i2c-nforce2.ko
    ide-core.ko
    ide-pci-generic.ko
    ieee1394.ko
    k8temp.ko
    libata.ko
    nvidia.ko
    nvidiafb.ko
    ohci-hcd.ko
    ohci1394.ko
    pata_acpi.ko
    pata_amd.ko
    pci_hotplug.ko
    pcspkr.ko
    processor.ko
    sata_nv.ko
    scsi_mod.ko
    sd_mod.ko
    serio_raw.ko
    shpchp.ko
    snd-hda-intel.ko
    snd-hwdep.ko
    snd-page-alloc.ko
    snd-pcm.ko
    snd-pcsp.ko
    snd-timer.ko
    snd.ko
    soundcore.ko
    sr_mod.ko
    thermal.ko
    usb-storage.ko
    usbcore.ko
    usbhid.ko
    vgastate.ko
    So now what do I do? I am trying to compile a custom, slim, bloatless kernel.
    Last edited by haxit (2009-03-01 01:15:01)

    just few pointers regarding this:
    agpgart.ko -- AGP support
    amd74xx.ko -- AMD IDE support
    ata_generic.ko -- generic ATA driver
    button.ko -- power button?
    cdrom.ko -- erm...
    ehci-hcd.ko -- USB
    evdev.ko -- input devices through the kernel
    fan.ko -- fan control/readings via ACPI???
    fb_ddc.ko -- framebuffer support/info reading module?
    forcedeth.ko -- you have an nVidia chipset with an ethernet port, I guess
    hid.ko -- human interface device support (mouse, FI)
    i2c-algo-bit.ko
    i2c-core.ko
    i2c-nforce2.ko -- I2C is a serial bus, and has been used for ages. Apparently your chipset needs it.
    ide-core.ko
    ide-pci-generic.ko -- ??? Not using libata or something?
    ieee1394.ko -- got Firewire?
    k8temp.ko -- Athlon64?
    libata.ko -- the good stuff
    nvidia.ko -- you evil sheep, you! (OK, so I use the binary driver, too...)
    nvidiafb.ko -- new framebuffer.
    ohci-hcd.ko -- USB again?
    ohci1394.ko -- Firewire again?
    pata_acpi.ko
    pata_amd.ko  -- drive controller stuff again
    pci_hotplug.ko -- for all of the three people with big-iron servers that use it? Or is it good for suspend/resume, or something? I dunno, but I don't put it in
    pcspkr.ko -- I disable this one. Only my BIOS should be beeping at me.
    processor.ko
    sata_nv.ko -- again, nVidia drive controller
    scsi_mod.ko -- you need this for all the SATA stuff to work right, I'm pretty sure
    sd_mod.ko -- ditto
    serio_raw.ko -- *shrug* raw serial I/O
    shpchp.ko -- some kind of hotplug thingie?
    snd-hda-intel.ko -- you have HDA sound onboard.
    snd-hwdep.ko
    snd-page-alloc.ko
    snd-pcm.ko
    snd-pcsp.ko -- same as the main kernel one, I leave it out. Sometimes ALSA likes to make it the default, too, for no good reason.
    snd-timer.ko
    snd.ko
    soundcore.ko
    sr_mod.ko -- I *think* this is needed for burners these days. In general, don't skimp in the SCSI support in the config (you don't need tape or media changer support, of course)
    thermal.ko
    usb-storage.ko
    usbcore.ko
    usbhid.ko -- HID again
    vgastate.ko -- usually a dependency for framebuffer stuff, but I'm not sure beyond that
    agpgart.ko -- AGP support
    actually this one is potentially a performance culprit when using nvidia drivers. kernel agp is really bad. If you have installed nvidia binary driver, you don't need this one even with AGP card. If you have PCI/PCIE card, this is a waste.
    nvidiafb.ko -- new framebuffer.
    nope this one is for nVidia Riva128 (pretty old video card)
    ohci-hcd.ko -- USB again?
    there are three different USB controllers: OHCI, UHCi, EHCI
    you can't simply disable one of these. all depends on hardware setup: if you have OHCI and UHCI then you need both. So "again" is not again, but system requirement.
    run
    lspci -v | grep HCI
    to see which controllers do you have
    scsi_mod.ko -- you need this for all the SATA stuff to work right, I'm pretty sure
    no, you don't. But you need to check your hardware dependencies. I have SATA, and the only SCSI stuff loaded is SG and SD
    sometimes you will see several modules which have partially the same name. e.g. firewire or usb or snd. all of these might be required for firewire (Assuming that you are using firewire at all) or sound to work. Sometimes the overlap.
    my modules take only 2.6MB:
    du -sh /lib/modules/2.6.28.7-slim
    2.6M    /lib/modules/2.6.28.7-slim
    without nvidia driver (this one alone is 7.6MB)
    does this speed up kernel? Only to some extend and in fact only particular modules will slow down boot time. In my case PCMCIA is slowing down kernel.
    O.k. so what about disk space?
    Are you kidding? default Arch kernel modules take 69MB and current disks are what? several (tenths, hundreds) GB? So this is no argument really.
    So what about RAM?
    You will be much better off trimming down your DM (KDE or Gnome) than kernel assuming that you are using one of these, however even small WM can be trimmed down. These two (KDE and Gnome) are pigs, but you can easily cut some fat without loosing usability.
    So why I did this? not to gain anything. Out of curiosity really
    there is a lot of tools that may help:
    lspci
    lsusb
    cpuinfo
    for example that may help.
    Last edited by broch (2009-03-02 15:11:07)

  • Mkinitcpio cannot find modules

    I had previously put this up to some kind of minor issue on my box, but now I'm not so certain.
    Since the 3.1 series of the 'linux' package, mkinitcpio has not been able to automatically build new boot images, as it always does when there's an update to the 'linux' package, and oftentimes it doesn't do it manually either.
    Previously, running 'depmod -a' would reveal this was because it was looking in a folder that did not exist, for a previous kernel version. Making a symlink to the folder provided by the new version of the 'linux' package's modules resolved this.
    However now, this workaround is no longer functioning. 'depmod -a' reveals absolutely nothing, and thus 'mkinitcpio -p linux' continues to fail to build the new boot images with the following output:
    ==> Building image from preset: 'default'
    -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    ==> Starting build: 3.2.1-1-ARCH
    ==> ERROR: module not found: `i915'
    -> Parsing hook: [base]
    -> Parsing hook: [udev]
    -> Parsing hook: [autodetect]
    -> Parsing hook: [pata]
    -> Parsing hook: [scsi]
    -> Parsing hook: [sata]
    -> Parsing hook: [filesystems]
    -> Parsing hook: [usbinput]
    -> Parsing hook: [keymap]
    ==> Creating xz initcpio image: /boot/initramfs-linux.img
    ==> WARNING: errors were encountered during the build. The image may not be complete.
    ==> Image generation successful
    ==> Building image from preset: 'fallback'
    -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    ==> Starting build: 3.2.1-1-ARCH
    ==> ERROR: module not found: `i915'
    -> Parsing hook: [base]
    -> Parsing hook: [udev]
    -> Parsing hook: [pata]
    ==> ERROR: module not found: `pata_atp867x'
    ==> ERROR: module not found: `pata_opti'
    ==> ERROR: module not found: `pata_it821x'
    ==> ERROR: module not found: `pata_cmd64x'
    ==> ERROR: module not found: `pata_sis'
    ==> ERROR: module not found: `pata_ns87415'
    ==> ERROR: module not found: `pata_amd'
    ==> ERROR: module not found: `pata_sc1200'
    ==> ERROR: module not found: `pata_ninja32'
    ==> ERROR: module not found: `pata_it8213'
    ==> ERROR: module not found: `pata_rz1000'
    ==> ERROR: module not found: `pata_hpt3x3'
    ==> ERROR: module not found: `pata_efar'
    ==> ERROR: module not found: `pata_jmicron'
    ==> ERROR: module not found: `pata_cs5520'
    ==> ERROR: module not found: `pata_netcell'
    ==> ERROR: module not found: `pata_mpiix'
    ==> ERROR: module not found: `pata_cypress'
    ==> ERROR: module not found: `pata_cs5536'
    ==> ERROR: module not found: `pata_sl82c105'
    ==> ERROR: module not found: `pata_optidma'
    ==> ERROR: module not found: `pata_triflex'
    ==> ERROR: module not found: `pata_atiixp'
    ==> ERROR: module not found: `pata_oldpiix'
    ==> ERROR: module not found: `pata_pdc202xx_old'
    ==> ERROR: module not found: `pata_marvell'
    ==> ERROR: module not found: `pata_radisys'
    ==> ERROR: module not found: `pata_legacy'
    ==> ERROR: module not found: `pata_cs5530'
    ==> ERROR: module not found: `pata_hpt3x2n'
    ==> ERROR: module not found: `pata_pdc2027x'
    ==> ERROR: module not found: `pata_sch'
    ==> ERROR: module not found: `pata_sil680'
    ==> ERROR: module not found: `pata_artop'
    ==> ERROR: module not found: `pata_via'
    ==> ERROR: module not found: `pata_rdc'
    ==> ERROR: module not found: `pata_hpt37x'
    ==> ERROR: module not found: `pata_ali'
    ==> ERROR: module not found: `pata_serverworks'
    ==> ERROR: module not found: `pata_piccolo'
    ==> ERROR: module not found: `pata_ns87410'
    ==> ERROR: module not found: `pata_cmd640'
    ==> ERROR: module not found: `pata_pcmcia'
    ==> ERROR: module not found: `pata_hpt366'
    ==> ERROR: module not found: `pata_acpi'
    ==> ERROR: module not found: `pata_arasan_cf'
    ==> ERROR: module not found: `ata_generic'
    ==> ERROR: module not found: `ata_piix'
    -> Parsing hook: [scsi]
    -> Parsing hook: [sata]
    -> Parsing hook: [filesystems]
    -> Parsing hook: [usbinput]
    -> Parsing hook: [keymap]
    ==> Creating xz initcpio image: /boot/initramfs-linux-fallback.img
    ==> WARNING: errors were encountered during the build. The image may not be complete.
    ==> Image generation successful
    Past experience has taught me that neither of these two images will be bootable, because previous versions displaying the same output were also unbootable.
    Contents of the /lib/modules directory, as reported by 'ls -l'
    drwxr-xr-x 2 root root 4096 Jan 19 17:52 3.1.9-2-ARCH
    drwxr-xr-x 3 root root 4096 Jan 13 05:54 3.2.1-1-ARCH
    drwxr-xr-x 2 root root 4096 Jan 19 17:35 extramodules-3.2-ARCH
    I cannot see the cause nor solution to this problem. Any help?

    @wonder: pata removed. Problem remains unchanged.
    @karol
    I am not using [testing].
    Requested file contents:
    # 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="i915"
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run first, so it may be used to
    # override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten if already added)
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options
    # like so:
    # FILES="/etc/modprobe.d/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect scsi sata filesystems"
    ## This is identical to the above, except the old ide subsystem is
    ## used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev pata mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    HOOKS="base udev autodetect pata scsi sata filesystems usbinput keymap"
    # COMPRESSION
    # Use this to compress the initramfs image. With kernels earlier than
    # 2.6.30, only gzip is supported, which is also the default. Newer kernels
    # support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
    # compression.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    COMPRESSION="xz"
    #COMPRESSION="lzop"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""

  • Systemd system-modules-load error [Solved]

    After recent update of kernel too linux-3.14.4-1I now cannot boot system due too this error
    -- Logs begin at Fri 2014-05-16 11:58:04 BST, end at Fri 2014-05-16 12:00:56 BST. --
    May 16 11:59:33 arch systemd[1]: Starting Graphical Interface.
    -- Subject: Unit graphical.target has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit graphical.target has begun starting up.
    May 16 11:59:33 arch systemd[1]: Reached target Graphical Interface.
    -- Subject: Unit graphical.target has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit graphical.target has finished starting up.
    -- The start-up result is done.
    May 16 11:59:33 arch systemd[1]: Starting Network.
    -- Subject: Unit network.target has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit network.target has begun starting up.
    May 16 11:59:33 arch systemd[1]: Reached target Network.
    -- Subject: Unit network.target has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit network.target has finished starting up.
    -- The start-up result is done.
    May 16 11:59:33 arch systemd[1]: Startup finished in 4.181s (kernel) + 1min 31.543s (userspace) = 1min 35.724s.
    -- Subject: System start-up is now complete
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- All system services necessary queued for starting at boot have been
    -- successfully started. Note that this does not mean that the machine is
    -- now idle as services might still be busy with completing start-up.
    -- Kernel start-up required 4181476 microseconds.
    -- Initial RAM disk start-up required INITRD_USEC microseconds.
    -- Userspace start-up required 91543070 microseconds.
    May 16 12:00:56 arch systemd[1]: Starting Load Kernel Modules...
    -- Subject: Unit systemd-modules-load.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-modules-load.service has begun starting up.
    May 16 12:00:56 arch systemd-modules-load[316]: Failed to lookup alias 'sg': Function not implemented
    May 16 12:00:56 arch systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
    May 16 12:00:56 arch systemd[1]: Failed to start Load Kernel Modules.
    -- Subject: Unit systemd-modules-load.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-modules-load.service has failed.
    -- The result is failed.
    May 16 12:00:56 arch systemd[1]: Unit systemd-modules-load.service entered failed state.
    Might be just that naming of sg has changed have updated and tried to run mkinicpio but it still does not find module?
    Solved put it down to a bad dd clone of drive partition, have rerun and all seems to working now.
    Last edited by Mr Green (2014-05-17 12:20:52)

    Yep. It was my own fault. I had been using the b43 driver for my BCM4331 wifi card, and recently switched to broadcom-wl. However, I still was trying to load b43 in /etc/modules-load even though I had removed the driver and module from my system. Not sure why my system only started complaining in 3.18.5, but in any case removing the offending .conf file solved the problem. Thanks, graysky.

  • [SOLVED] Automatically loading module

    Hi everyone,
    Since I succeeded (with the help of some of you) to get my wi-fi back, I am unable to configure my system in order to automatically load the wi-fi module at boot. I actually read this post and this page of the wiki and so I created a new file : /etc/modules.load.d/brcmsmac.conf.
    This file only contains a line : brcmsmac.
    Despite this, brcmsmac isn't loaded.  Is there something I am missing?
    Last edited by nugetchar (2014-08-10 12:32:33)

    Okay, so here are the permissions :
    [nugetchar@arch ~]$ ls -l /etc/modules-load.d/
    total 4
    -rw-r--r-- 1 root root 8 Aug 10 00:21 brcmsmac.conf
    And here is the part of the journal which might be interesting :
    Aug 10 13:22:28 arch org.a11y.Bus[424]: Activating service name='org.a11y.atspi.Registry'
    Aug 10 13:22:28 arch org.a11y.Bus[424]: Successfully activated service 'org.a11y.atspi.Registry'
    Aug 10 13:22:28 arch org.a11y.atspi.Registry[449]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    Aug 10 13:22:28 arch org.a11y.atspi.Registry[449]: ** (at-spi2-registryd:452): WARNING **: Failed to register client: GDBus.Error:org.freedeskto
    Aug 10 13:22:28 arch org.a11y.atspi.Registry[449]: ** (at-spi2-registryd:452): WARNING **: Unable to register client with session manager
    Aug 10 13:22:30 arch dbus[353]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
    Aug 10 13:22:30 arch systemd[1]: Starting RealtimeKit Scheduling Policy Service...
    Aug 10 13:22:30 arch systemd[1]: Started RealtimeKit Scheduling Policy Service.
    Aug 10 13:22:30 arch dbus[353]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
    Aug 10 13:22:30 arch rtkit-daemon[485]: Successfully called chroot.
    Aug 10 13:22:30 arch rtkit-daemon[485]: Successfully dropped privileges.
    Aug 10 13:22:30 arch rtkit-daemon[485]: Successfully limited resources.
    Aug 10 13:22:30 arch rtkit-daemon[485]: Running.
    Aug 10 13:22:30 arch rtkit-daemon[485]: Watchdog thread running.
    Aug 10 13:22:30 arch rtkit-daemon[485]: Canary thread running.
    Aug 10 13:22:30 arch rtkit-daemon[485]: Successfully made thread 484 of process 484 (/usr/bin/pulseaudio) owned by '1000' high priority at nice
    Aug 10 13:22:30 arch rtkit-daemon[485]: Supervising 1 threads of 1 processes of 1 users.
    Aug 10 13:22:31 arch org.freedesktop.Notifications[424]: ** (notify-osd:496): WARNING **: dnd_is_screensaver_active(): Got error "The name org.g
    Aug 10 13:22:32 arch pulseaudio[484]: Availability of port 'analog-input-headset-mic' is inconsistent!
    Aug 10 13:22:32 arch pulseaudio[484]: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided
    Aug 10 13:22:42 arch org.freedesktop.Notifications[424]: ** (notify-osd:496): WARNING **: dnd_is_screensaver_active(): Got error "The name org.g
    Aug 10 13:22:42 arch org.freedesktop.Notifications[424]: (notify-osd:496): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE
    Aug 10 13:22:54 arch slim[357]: The XKEYBOARD keymap compiler (xkbcomp) reports:
    Aug 10 13:22:54 arch slim[357]: > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    Aug 10 13:22:54 arch slim[357]: > Ignoring extra symbols
    Aug 10 13:22:54 arch slim[357]: Errors from xkbcomp are not fatal to the X server
    Aug 10 13:23:24 arch sudo[545]: nugetchar : TTY=pts/0 ; PWD=/home/nugetchar ; USER=root ; COMMAND=/usr/bin/modprobe brcmsmac
    Aug 10 13:23:24 arch sudo[545]: pam_unix(sudo:session): session opened for user root by nugetchar(uid=0)
    Aug 10 13:23:24 arch kernel: bcma: bus0: Found chip with id 0x4313, rev 0x01 and package 0x08
    Aug 10 13:23:24 arch kernel: bcma: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x24, class 0x0)
    Aug 10 13:23:24 arch kernel: bcma: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x18, class 0x0)
    Aug 10 13:23:24 arch kernel: bcma: bus0: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x11, class 0x0)
    Aug 10 13:23:24 arch kernel: bcma: bus0: Bus registered
    Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: mfg 4bf core 812 rev 24 class 0 irq 17
    Aug 10 13:23:24 arch sudo[545]: pam_unix(sudo:session): session closed for user root
    Aug 10 13:23:24 arch NetworkManager[351]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/bcma
    Aug 10 13:23:24 arch systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill1...
    Aug 10 13:23:24 arch kernel: ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
    Aug 10 13:23:24 arch kernel: ieee80211 phy0: registered radio enabled led device: brcmsmac-phy0:radio gpio: 243
    Aug 10 13:23:24 arch systemd[1]: Started Load/Save RF Kill Switch Status of rfkill1.
    Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): using nl80211 for WiFi device control
    Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): driver supports Access Point (AP) mode
    Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'brcmsmac' ifindex: 3)
    Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/2
    Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    Aug 10 13:23:24 arch systemd-udevd[547]: renamed network interface wlan0 to wlp3s0
    Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): preparing device
    Aug 10 13:23:24 arch dbus[353]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
    Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement)
    Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: brcms_ops_config: change power-save mode: false (implement)
    Aug 10 13:23:24 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
    Aug 10 13:23:24 arch systemd[1]: Starting WPA supplicant...
    Aug 10 13:23:25 arch dbus[353]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
    Aug 10 13:23:25 arch NetworkManager[351]: <info> wpa_supplicant started
    Aug 10 13:23:25 arch systemd[1]: Started WPA supplicant.
    Aug 10 13:23:25 arch NetworkManager[351]: <info> (wlp3s0) supports 4 scan SSIDs
    Aug 10 13:23:25 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: starting -> ready
    Aug 10 13:23:25 arch NetworkManager[351]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20
    Aug 10 13:23:25 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: ready -> disconnected
    Aug 10 13:23:25 arch NetworkManager[351]: <info> (wlp3s0) supports 4 scan SSIDs
    Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Auto-activating connection 'Livebox-B34A'.
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) starting connection 'Livebox-B34A'
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
    Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    Aug 10 13:23:26 arch NetworkManager[351]: <info> NetworkManager state is now CONNECTING
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
    Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0/wireless): connection 'Livebox-B34A' has security, and secrets exist. No ne
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: added 'ssid' value 'Livebox-B34A'
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: added 'scan_ssid' value '1'
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: added 'auth_alg' value 'OPEN'
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: added 'psk' value '<omitted>'
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: set interface ap_scan to 1
    Aug 10 13:23:26 arch kernel: wlp3s0: authenticate with b0:75:d5:87:b3:4a
    Aug 10 13:23:26 arch kernel: wlp3s0: send auth to b0:75:d5:87:b3:4a (try 1/3)
    Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: inactive -> authenticating
    Aug 10 13:23:26 arch kernel: wlp3s0: authenticated
    Aug 10 13:23:26 arch kernel: wlp3s0: associate with b0:75:d5:87:b3:4a (try 1/3)
    Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: authenticating -> associating
    Aug 10 13:23:26 arch kernel: wlp3s0: RX AssocResp from b0:75:d5:87:b3:4a (capab=0x431 status=0 aid=1)
    Aug 10 13:23:26 arch kernel: brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: associated
    Aug 10 13:23:26 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: true (implement)
    Aug 10 13:23:26 arch kernel: wlp3s0: associated
    Aug 10 13:23:26 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
    Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: associating -> associated
    Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: associated -> 4-way handshake
    Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: 4-way handshake -> completed
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled.
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started...
    Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    Aug 10 13:23:26 arch NetworkManager[351]: <info> dhcpcd started with pid 585
    Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete.
    Aug 10 13:23:26 arch dhcpcd[585]: version 6.4.3 starting
    Aug 10 13:23:26 arch NetworkManager[351]: dhcpcd[585]: version 6.4.3 starting
    Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): DHCPv4 state changed nbi -> preinit
    Aug 10 13:23:26 arch NetworkManager[351]: dhcpcd[585]: DUID 00:01:00:01:1b:77:fa:2f:0c:84:dc:63:61:ef
    Aug 10 13:23:26 arch NetworkManager[351]: dhcpcd[585]: wlp3s0: IAID dc:63:61:ef
    Aug 10 13:23:26 arch dhcpcd[585]: DUID 00:01:00:01:1b:77:fa:2f:0c:84:dc:63:61:ef
    Aug 10 13:23:26 arch dhcpcd[585]: wlp3s0: IAID dc:63:61:ef
    Aug 10 13:23:26 arch dhcpcd[585]: wlp3s0: soliciting an IPv6 router
    Aug 10 13:23:26 arch NetworkManager[351]: dhcpcd[585]: wlp3s0: soliciting an IPv6 router
    Aug 10 13:23:27 arch dhcpcd[585]: wlp3s0: rebinding lease of 192.168.1.23
    Aug 10 13:23:27 arch NetworkManager[351]: dhcpcd[585]: wlp3s0: rebinding lease of 192.168.1.23
    Aug 10 13:23:32 arch dhcpcd[585]: wlp3s0: leased 192.168.1.23 for 86400 seconds
    Aug 10 13:23:32 arch dhcpcd[585]: wlp3s0: adding route to 192.168.1.0/24
    Aug 10 13:23:32 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
    Aug 10 13:23:32 arch NetworkManager[351]: dhcpcd[585]: wlp3s0: leased 192.168.1.23 for 86400 seconds
    Aug 10 13:23:32 arch NetworkManager[351]: dhcpcd[585]: wlp3s0: adding route to 192.168.1.0/24
    Aug 10 13:23:32 arch NetworkManager[351]: <info> (wlp3s0): DHCPv4 state changed preinit -> reboot
    Aug 10 13:23:32 arch NetworkManager[351]: <info> address 192.168.1.23
    Aug 10 13:23:32 arch NetworkManager[351]: <info> plen 24 (255.255.255.0)
    Aug 10 13:23:32 arch NetworkManager[351]: <info> gateway 192.168.1.1
    Aug 10 13:23:32 arch NetworkManager[351]: <info> server identifier 192.168.1.1
    Aug 10 13:23:32 arch NetworkManager[351]: <info> lease time 86400
    Aug 10 13:23:32 arch NetworkManager[351]: <info> nameserver '192.168.1.1'
    Aug 10 13:23:32 arch NetworkManager[351]: <info> nameserver '192.168.1.1'
    Aug 10 13:23:32 arch NetworkManager[351]: <info> domain name 'home'
    Aug 10 13:23:32 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    Aug 10 13:23:32 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) started...
    Aug 10 13:23:32 arch NetworkManager[351]: <info> (wlp3s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    Aug 10 13:23:32 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) complete.
    Aug 10 13:23:32 arch NetworkManager[351]: <info> (wlp3s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    Aug 10 13:23:32 arch NetworkManager[351]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    Aug 10 13:23:32 arch NetworkManager[351]: <info> NetworkManager state is now CONNECTED_LOCAL
    Aug 10 13:23:32 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
    Aug 10 13:23:32 arch NetworkManager[351]: <info> NetworkManager state is now CONNECTED_GLOBAL
    Aug 10 13:23:32 arch NetworkManager[351]: <info> Policy set 'Livebox-B34A' (wlp3s0) as default for IPv4 routing and DNS.
    Aug 10 13:23:32 arch NetworkManager[351]: <info> Writing DNS information to /usr/bin/resolvconf
    Aug 10 13:23:34 arch NetworkManager[351]: <info> Activation (wlp3s0) successful, device activated.
    It kind of unreadable so here is the result with a grep :
    Aug 10 13:22:09 arch systemd-modules-load[175]: Module 'brcmsmac' is blacklisted
    Aug 10 13:23:24 arch sudo[545]: nugetchar : TTY=pts/0 ; PWD=/home/nugetchar ; USER=root ; COMMAND=/usr/bin/modprobe brcmsmac
    Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: mfg 4bf core 812 rev 24 class 0 irq 17
    Aug 10 13:23:24 arch NetworkManager[351]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/bcma0:0/ieee80211/phy0/rfkill1) (driver brcmsmac)
    Aug 10 13:23:24 arch kernel: ieee80211 phy0: registered radio enabled led device: brcmsmac-phy0:radio gpio: 243
    Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'brcmsmac' ifindex: 3)
    Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement)
    Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: brcms_ops_config: change power-save mode: false (implement)
    Aug 10 13:23:26 arch kernel: brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: associated
    Aug 10 13:23:26 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: true (implement)
    Aug 10 13:23:32 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
    Aug 10 13:23:32 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
    It appear that brcmsmac is blacklisted, but this is weird because in the /etc/mordprobe.d/modprobe.conf file, it is not :
    [nugetchar@arch etc]$ more modprobe.d/modprobe.conf
    alias floppy off
    blacklist fd0
    blacklist floppy
    blacklist ipv6
    blacklist pcspkr
    blacklist snd_pcsp

  • VMware keeps Rebuilding Kernel Modules [Solved]

    Hi, and thanks. After the last kernel upgrade everytime I start vmware player the first instance to run will rebuild the kernel modules and there is a warning icon next to the "Blocking File System" entry in the build list. I am using the latest kernel 3.4.2.2-Arch, my vmware player is version 4.0.2 build-591240. It runs fine after it rebuilds but the warning icon has me concerned. Does anyone know what this is? Do I have to move up a vmware version?
    thanks in advance for your help.
    --jerry
    Last edited by jk121960 (2012-06-27 20:04:08)

    If anyone is interested, here is the complete console output when I run the player.
    $ vmplayer
    Logging to /tmp/vmware-citmkd/modconfig-9164.log
    HostinfoReadDistroFile: could not open file/etc/redhat-release: 2
    HostinfoReadDistroFile: could not open file/etc/redhat_version: 2
    HostinfoReadDistroFile: could not open file/etc/sun-release: 2
    HostinfoReadDistroFile: could not open file/etc/SuSE-release: 2
    HostinfoReadDistroFile: could not open file/etc/novell-release: 2
    HostinfoReadDistroFile: could not open file/etc/sles-release: 2
    HostinfoReadDistroFile: could not open file/etc/debian_version: 2
    HostinfoReadDistroFile: could not open file/etc/debian_release: 2
    HostinfoReadDistroFile: could not open file/etc/mandrake-release: 2
    HostinfoReadDistroFile: could not open file/etc/mandriva-release: 2
    HostinfoReadDistroFile: could not open file/etc/mandrakelinux-release: 2
    HostinfoReadDistroFile: could not open file/etc/turbolinux-release: 2
    HostinfoReadDistroFile: could not open file/etc/fedora-release: 2
    HostinfoReadDistroFile: could not open file/etc/gentoo-release: 2
    HostinfoReadDistroFile: could not open file/etc/nld-release: 2
    HostinfoReadDistroFile: could not open file/etc/lsb-release: 2
    HostinfoReadDistroFile: could not open file/etc/annvix-release: 2
    HostinfoReadDistroFile: Cannot work with empty file.
    HostinfoReadDistroFile: could not open file/etc/arklinux-release: 2
    HostinfoReadDistroFile: could not open file/etc/aurox-release: 2
    HostinfoReadDistroFile: could not open file/etc/blackcat-release: 2
    HostinfoReadDistroFile: could not open file/etc/cobalt-release: 2
    HostinfoReadDistroFile: could not open file/etc/conectiva-release: 2
    HostinfoReadDistroFile: could not open file/etc/immunix-release: 2
    HostinfoReadDistroFile: could not open file/etc/knoppix_version: 2
    HostinfoReadDistroFile: could not open file/etc/lfs-release: 2
    HostinfoReadDistroFile: could not open file/etc/linuxppc-release: 2
    HostinfoReadDistroFile: could not open file/etc/mklinux-release: 2
    HostinfoReadDistroFile: could not open file/etc/pld-release: 2
    HostinfoReadDistroFile: could not open file/etc/slackware-version: 2
    HostinfoReadDistroFile: could not open file/etc/slackware-release: 2
    HostinfoReadDistroFile: could not open file/etc/e-smith-release: 2
    HostinfoReadDistroFile: could not open file/etc/release: 2
    HostinfoReadDistroFile: could not open file/etc/tinysofa-release: 2
    HostinfoReadDistroFile: could not open file/etc/ultrapenguin-release: 2
    HostinfoReadDistroFile: could not open file/etc/UnitedLinux-release: 2
    HostinfoReadDistroFile: could not open file/etc/va-release: 2
    HostinfoReadDistroFile: could not open file/etc/yellowdog-release: 2
    HostinfoOSData: Error: no distro file found
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): Pango-WARNING **: Failed to load Pango module '/usr/lib/vmware/libconf/lib/pango/1.6.0/modules/pango-basic-fc.so' for id 'BasicScriptEngineFc'
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    (vmware-gksu:9164): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.
    (vmware-gksu:9164): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    Logging to /tmp/vmware-root/modconfig-9275.log
    HostinfoReadDistroFile: could not open file/etc/redhat-release: 2
    HostinfoReadDistroFile: could not open file/etc/redhat_version: 2
    HostinfoReadDistroFile: could not open file/etc/sun-release: 2
    HostinfoReadDistroFile: could not open file/etc/SuSE-release: 2
    HostinfoReadDistroFile: could not open file/etc/novell-release: 2
    HostinfoReadDistroFile: could not open file/etc/sles-release: 2
    HostinfoReadDistroFile: could not open file/etc/debian_version: 2
    HostinfoReadDistroFile: could not open file/etc/debian_release: 2
    HostinfoReadDistroFile: could not open file/etc/mandrake-release: 2
    HostinfoReadDistroFile: could not open file/etc/mandriva-release: 2
    HostinfoReadDistroFile: could not open file/etc/mandrakelinux-release: 2
    HostinfoReadDistroFile: could not open file/etc/turbolinux-release: 2
    HostinfoReadDistroFile: could not open file/etc/fedora-release: 2
    HostinfoReadDistroFile: could not open file/etc/gentoo-release: 2
    HostinfoReadDistroFile: could not open file/etc/nld-release: 2
    HostinfoReadDistroFile: could not open file/etc/lsb-release: 2
    HostinfoReadDistroFile: could not open file/etc/annvix-release: 2
    HostinfoReadDistroFile: Cannot work with empty file.
    HostinfoReadDistroFile: could not open file/etc/arklinux-release: 2
    HostinfoReadDistroFile: could not open file/etc/aurox-release: 2
    HostinfoReadDistroFile: could not open file/etc/blackcat-release: 2
    HostinfoReadDistroFile: could not open file/etc/cobalt-release: 2
    HostinfoReadDistroFile: could not open file/etc/conectiva-release: 2
    HostinfoReadDistroFile: could not open file/etc/immunix-release: 2
    HostinfoReadDistroFile: could not open file/etc/knoppix_version: 2
    HostinfoReadDistroFile: could not open file/etc/lfs-release: 2
    HostinfoReadDistroFile: could not open file/etc/linuxppc-release: 2
    HostinfoReadDistroFile: could not open file/etc/mklinux-release: 2
    HostinfoReadDistroFile: could not open file/etc/pld-release: 2
    HostinfoReadDistroFile: could not open file/etc/slackware-version: 2
    HostinfoReadDistroFile: could not open file/etc/slackware-release: 2
    HostinfoReadDistroFile: could not open file/etc/e-smith-release: 2
    HostinfoReadDistroFile: could not open file/etc/release: 2
    HostinfoReadDistroFile: could not open file/etc/tinysofa-release: 2
    HostinfoReadDistroFile: could not open file/etc/ultrapenguin-release: 2
    HostinfoReadDistroFile: could not open file/etc/UnitedLinux-release: 2
    HostinfoReadDistroFile: could not open file/etc/va-release: 2
    HostinfoReadDistroFile: could not open file/etc/yellowdog-release: 2
    HostinfoOSData: Error: no distro file found
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmnet.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Networking Driver.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    ERROR: Module vmblock not found.
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmci.ko
    supported: external
    license: GPL v2
    version: 9.1.18.0
    description: VMware Virtual Machine Communication Interface (VMCI).
    author: VMware, Inc.
    srcversion: F659B534EA5CC5FFD4A08BF
    alias: pci:v000015ADd00000740sv*sd*bc*sc*i*
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    parm: disable_host:Disable driver host personality - (default=0) (bool)
    parm: disable_guest:Disable driver guest personality - (default=0) (bool)
    parm: disable_msi:Disable MSI use in driver - (default=0) (bool)
    parm: disable_msix:Disable MSI-X use in driver - (default=0) (bool)
    filename: /lib/modules/3.4.4-2-ARCH/misc/vsock.ko
    supported: external
    alias: vmware_vsock
    license: GPL v2
    version: 9.1.1.0
    description: VMware Virtual Socket Family
    author: VMware, Inc.
    srcversion: 5A37036862692504058A712
    depends: vmci
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    Stopping VMware services:
    VMware Authentication Daemon done
    VM communication interface socket family done
    Virtual machine communication interface done
    Virtual machine monitor done
    Blocking file system done
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
    make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
    CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
    LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
    LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko
    make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
    make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
    cp -f vmmon.ko ./../vmmon.o
    make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
    make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
    CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
    CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
    LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o
    LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.ko
    make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
    make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
    cp -f vmnet.ko ./../vmnet.o
    make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
    make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o
    CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c: In function 'FsOpReadSuper':
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:528:4: error: implicit declaration of function 'd_alloc_root' [-Werror=implicit-function-declaration]
    /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:528:15: warning: assignment makes pointer from integer without a cast [enabled by default]
    cc1: some warnings being treated as errors
    make[2]: *** [/tmp/vmware-root/modules/vmblock-only/linux/filesystem.o] Error 1
    make[2]: *** Waiting for unfinished jobs....
    make[1]: *** [_module_/tmp/vmware-root/modules/vmblock-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
    make: *** [vmblock.ko] Error 2
    make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmci-only'
    make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
    CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
    CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
    CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
    CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
    CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
    CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
    CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
    CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
    CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
    CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
    CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
    CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
    CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function '__check_disable_host':
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2498:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function '__check_disable_guest':
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2501:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function '__check_disable_msi':
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2504:1: warning: return from incompatible pointer type [enabled by default]
    /tmp/vmware-root/modules/vmci-only/linux/driver.c: In function '__check_disable_msix':
    /tmp/vmware-root/modules/vmci-only/linux/driver.c:2507:1: warning: return from incompatible pointer type [enabled by default]
    LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
    LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
    make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
    make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
    cp -f vmci.ko ./../vmci.o
    make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vmci-only'
    make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
    Building modules, stage 2.
    MODPOST 1 modules
    make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
    make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
    cp -f vmci.ko ./../vmci.o
    make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
    Using 2.6.x kernel build system.
    make: Entering directory `/tmp/vmware-root/modules/vsock-only'
    make -C /lib/modules/3.4.4-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory `/usr/src/linux-3.4.4-2-ARCH'
    CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
    CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
    CC [M] /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o
    CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o
    CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o
    CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o
    CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o
    LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/vmware-root/modules/vsock-only/vsock.mod.o
    LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko
    make[1]: Leaving directory `/usr/src/linux-3.4.4-2-ARCH'
    make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
    make[1]: `postbuild' is up to date.
    make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only'
    cp -f vsock.ko ./../vsock.o
    make: Leaving directory `/tmp/vmware-root/modules/vsock-only'
    Starting VMware services:
    Virtual machine monitor done
    Virtual machine communication interface done
    VM communication interface socket family done
    Blocking file system done
    Virtual ethernet done
    VMware Authentication Daemon done
    Shared Memory Available done
    filename: /lib/modules/3.4.4-2-ARCH/misc/vmmon.ko
    supported: external
    license: GPL v2
    description: VMware Virtual Machine Monitor.
    author: VMware, Inc.
    depends:
    vermagic: 3.4.4-2-ARCH SMP preempt mod_unload modversions
    No value set for `/system/http_proxy/use_http_proxy'
    No value set for `/system/proxy/mode'
    No value set for `/system/http_proxy/use_http_proxy'
    No value set for `/system/proxy/mode'
    No value set for `/system/http_proxy/use_http_proxy'
    No value set for `/system/proxy/mode'
    $
    Last edited by med1972 (2012-07-01 00:41:46)

Maybe you are looking for

  • How to increase brightness in Windows 7 and for the Option sceen?

    I have an 15" early 2011 MBP with Snow Leopard and reccently installed 64-bit Windows 7 Pro using an upgrade disk I had. Apparently the backup/upgrade disk would allow me to do a clean install despite not having a previous version of windows to base

  • Assigning plant to company code

    Hi All, I have created a company code 3333 copying company code 0001. similarly, I created a new plant AB01 copying plant 0001. Now, When I try to assign the plant AB01 to my company 3333, it displays an error message "Plant AB01 is already assigned

  • Deleting an object in the background

    Looking on the internet it seems I should use a tool called content aware to remove this object; however, I am unable to find that tool in Photoshop Elements 10. How do I remove an object from a picture in this program?

  • Embed video into another site??

    I have just finished creating a website in iweb, and published it to a folder. I am clueless when it come to html or web coding. So my question is, is there any way I can get an embed code to post my video from my site into another site?

  • Wide report causes standard tabs in two-level-tabs to move

    I know that sounds odd. So, if you have a large (wide) report, that spans the browser window, and you resize the window, the tabs will move to the right, eventually right out of the window. Very odd. I have Apex 3.0.0.00.20. I have a simple report re