[solved] unload module alx on suspend fails

Hi!
I'm having trouble getting my ethernet card to work properly with  suspend to ram (pm-suspend). Its a Qualcomm Atheros AR8161 Gigabit Ethernet Adapter (builtin ethernet-card of the Asus N56VZ) that I'm running with the alx-module that I build from the compat-drivers (compat-drivers-3.9-rc2-2-su, so version 1.2.3 of the alx module) on kernel 3.8.8-2. The driver works fine except it breaks suspend. A first suspend works fine (see suspend.log, upper part), however, after resuming, NetworkManager does not detect a cable being plugged in. Trying to suspend again fails results in the lower part  of suspend.log. Removing and probing the module again (reload.log) seems to work fine and resets the whole thing (network works, one suspend works, all following do not work)
Logs see https://gist.github.com/anonymous/5467609
I created a file SUSPEND_MODULES="alx" /etc/pm/config.d/modules (rights 644) that as far as I understand is supposed to unload and load the module upon suspend and resume but for some reason this does not seem to work properly. Why is that, am I just missing a typo? How can I fix it?
Any help is appreciated!
  Hannes
PS:
$ lspci -v
04:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)
Subsystem: ASUSTeK Computer Inc. N56VZ
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at f7800000 (64-bit, non-prefetchable) [size=256K]
I/O ports at d000 [size=128]
Capabilities: [40] Power Management version 3
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [c0] MSI: Enable- Count=1/16 Maskable+ 64bit+
Capabilities: [d8] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [180] Device Serial Number [...]
Kernel driver in use: alx
PPS: This bug is related and it has been reported that SUSPEND_MODULES is a workaround: https://bugs.launchpad.net/ubuntu/+sour … ug/1130037. There has just been a bug filled that is kind of related: https://bugs.archlinux.org/task/34971 but I'm not sure if its of any use if I postmy information there.
PPPS: This is also kind of related but does not provide any information http://askubuntu.com/questions/263867/u … -lid-close (I just list it for documentation purpose)
Last edited by HaMF (2013-05-07 14:02:50)

„Sleep hooks
Systemd does not use pm-utils to put the machine to sleep when using systemctl suspend, systemctl hibernate or systemctl hybrid-sleep; pm-utils hooks, including any custom hooks, will not be run. However, systemd provides two similar mechanisms to run custom scripts on these events.” – from wiki, so the sad thing is it's not as easy as in Ubuntu.
But (I guess) it's not impossible. I've got the same problem with ALX so I'm gonna try to make my own hook based on Wiki tips. Currently this Wiki page https://wiki.archlinux.org/index.php/Pm-utilspm is outdated (for Systemd user), so I'll try this section https://wiki.archlinux.org/index.php/Sy … management .

Similar Messages

  • [solved] Unloading modules before suspend to disk

    Hi, I'm trying to get my Asus U36jc to suspend to disk and resume. Suspending seems to go fine, but after resuming I get an unresponsive notebook (no response on key presses or ping) showing a black screen. Then immediately the fan gets louder and the notebook gets warmer.
    Just before the machine goes to sleep, I see this in my screen:
    xhci_hcd 0000:04:00.0: PCI post-resume error -110!
    xhci_hcd 0000:04:00.0: HC died; cleaning up
    xhci_hcd 0000:04:00.0: HC died; cleaning up
    dpm_run_callback(): pci_pm_resume+0x0/0xb0 returns -110
    PM: Device 0000:04:00.0 failed to resume async: error -110
    hda-codec: out of range cmd 0:20:400:fffff7ff
    I found this guide (https://www.kernel.org/doc/Documentatio … ugging.txt) and using that I determined that when I first remove modules ehci_pci, ehci_hcd and xhci_hcd, suspend to disk and resume seem to work fine.
    I found out here (https://wiki.archlinux.org/index.php/Pm … end_to_RAM) how to unload modules prior to suspending to RAM, but that doesn't seem to work for suspend to disk, and I can't find how to unload modules prior to that. Can someone tell me how to do that?
    Thanks for any help!
    Last edited by diederick76 (2013-09-25 20:27:36)

    I'm not sure if pm-utils is deprecated, it doesn't say so here (https://wiki.archlinux.org/index.php/Pm-utils). In any case its a dependency of upower, which is a dependency of kdelibs, so as long as I want to use KDE my harddrive is stuck with it.
    However, I decided to try your suggestion to use systemd:
    # asus36JC.service
    [Unit]
    Description=Script upon suspend/resume
    Before=sleep.target
    StopWhenUnneeded=no
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    ExecStart=/home/diederick/bin/no_modules
    ExecStop=/home/diederick/bin/modules
    [Install]
    WantedBy=sleep.target
    It seemed to work perfectly for a couple of times in a row (modules were there before and afterwards) until I restarted the notebook, when the problem was back. But then I remembered to enable the service and now it works. Thanks a lot!

  • [SOLVED] systemd-modules-load fails

    .. because it cannot find gspca. My log:
    journalctl -xn
    -- Logs begin at Thu 2013-08-22 11:43:18 CEST, end at Mon 2014-06-23 14:26:30 CEST. --
    Jun 23 14:25:21 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop7" has new interfaces: ("org.
    Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop2" has new interfaces: ("org.
    Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop1" has new interfaces: ("org.
    Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop0" has new interfaces: ("org.
    Jun 23 14:26:19 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop0" lost interfaces: ("org.fre
    Jun 23 14:26:30 jiggs 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.
    Jun 23 14:26:30 jiggs systemd-modules-load[3138]: Failed to find module 'gspca'
    Jun 23 14:26:30 jiggs systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
    Jun 23 14:26:30 jiggs 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.
    Jun 23 14:26:30 jiggs systemd[1]: Unit systemd-modules-load.service entered failed state.
    But I have lots of gspca's:
    # ls /lib/modules/`uname -r`/kernel/drivers/media/usb/gspca
    gl860 gspca_kinect.ko gspca_ov534.ko gspca_sonixj.ko gspca_sq905c.ko gspca_topro.ko
    gspca_benq.ko gspca_konica.ko gspca_pac207.ko gspca_spca1528.ko gspca_sq905.ko gspca_tv8532.ko
    gspca_conex.ko gspca_main.ko gspca_pac7302.ko gspca_spca500.ko gspca_sq930x.ko gspca_vc032x.ko
    gspca_cpia1.ko gspca_mars.ko gspca_pac7311.ko gspca_spca501.ko gspca_stk014.ko gspca_vicam.ko
    gspca_etoms.ko gspca_mr97310a.ko gspca_se401.ko gspca_spca505.ko gspca_stk1135.ko gspca_xirlink_cit.ko
    gspca_finepix.ko gspca_nw80x.ko gspca_sn9c2028.ko gspca_spca506.ko gspca_stv0680.ko gspca_zc3xx.ko
    gspca_jeilinj.ko gspca_ov519.ko gspca_sn9c20x.ko gspca_spca508.ko gspca_sunplus.ko m5602
    gspca_jl2005bcd.ko gspca_ov534_9.ko gspca_sonixb.ko gspca_spca561.ko gspca_t613.ko stv06xx
    The only difference I have with respect to a standard installation is that I downloaded an older version of the backport drivers, and in doing so I surely re-installed gspca.
    So my questions are: where is systemd-module-load searching for gspca? How can I persuade it to search in the right directory? And in any case, why is it searching for it in the wrong place to start with?. Just in case,
    # uname -a
    Linux jiggs 3.15.1-1-ARCH #1 SMP PREEMPT Tue Jun 17 09:32:20 CEST 2014 x86_64 GNU/Linux
    Last edited by MariusMatutiae (2014-06-26 09:10:22)

    Problem solved, thanks to both of you guys. For some resason, I had a webcam.conf file in /etc/modules-load.d containing the single line *gspca*, which is not a module: both modprobe and insmod fail, because the correct module name is one of those listed in /lib/modules/`uname -r`/kernel/drivers/media/usb/gspca. They are called gspca_benq.ko       gspca_konica.ko and so on. I simply deleted the file since I  do not need it.
    As for backport drivers: this site, http://drvbp1.linux-foundation.org/~mcg … backports/ has the most recent versions of Linux drivers, backported so that older kernels can install them (I understand this is not a concern for fellow Archers). Whenever I need to upgrade (mostly on Debian) or downgrade (a few times on Arch, because an older version of a driver is free of a newly minted bug) I download these drivers, compile them and install them from source.

  • [Solved] Systemd suspend fails everytime

    Hi,
    I've been using Arch Linux on my laptop for a while now and suddenly my laptop would not go into suspend anymore.
    My laptop is Asus UX32VD.
    Here's the whole journalctl between suspend starting and suspend failing.
    I also get this at bootup:
    [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up
    some while ago the iSSD in my laptop failed but it was later that the computer stopped suspending.
    Does anyone see the problem?
    Thanks.
    Edit: When I try to mount the iSSD partitions I get the same error messages that begin with "ata2.00" so those errors seem to be connected to the iSSD drive. Now, I can't disable the drive in bios, is it possible to make arch linux ignore it all together?
    Edit2: Arch Linux is installed on sda (ata1) and the bad drive is sdb (ata2)
    Edit3: The broken ssd was the culprit. When I write 1 to /sys/block/sdb/device/delete the laptop suspends correctly.
    So I made the following systemd service:
    [Unit]
    Description=Disable my fault ssd drive at suspend
    [Service]
    Type=OneShot
    ExecStart=/bin/sh -c 'echo 1 > /sys/block/sdb/device/delete'
    [Install]
    WantedBy=sleep.target
    Changing status to solved
    Last edited by granra (2014-04-18 23:01:57)

    Rexilion wrote:What is stopping you from taking it out?
    It's soldered to the motherboard.

  • Call of function module "SUBST_START_BATCHJOB" by RFC failed

    Hello Guru's,
    We have the following Issue:
    In Phase PREP_INIT/JOB_RSUPDTEC we get this error from EHPI (Version 710-1)
    Checks after phase PREP_INIT/JOB_RSUPDTEC were negative!
    Last error code set: BATCHJOB RSUPDTEC FAILED: Calling RSUPDTEC failed - repeat phase.
    In the file PSUPDTEC.LOG are the following error:
    4 ETQ260 Starting batchjob "RSUPDTEC"
    4 ETQ230 Starting RFC Login to: System = "E11", GwHost = "sape11", GwService = "sapgw00"
    4 ETQ359 RFC Login to: System="E11", Nr="00", GwHost="sape11", GwService="sapgw00"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
    4 ETQ399 JOBNAME='RSUPDTEC', REPNAME='RSUPDTEC', VARNAME='', BATCHHOST='sape11', IV_SCHEDEVER=' '
    4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded
    4 ETQ399 Returned JOBCOUNT='14230100'
    2EETQ235 Call of function module "SUBST_START_BATCHJOB" by RFC failed (error-status "27")
    2EETQ261 Start of batchjob "RSUPDTEC" failed
    In the Sysem we can see, that the Job RSUPDTEC was created by DDIC but not started.
    We can start (and finish) the job successfully as logged in DDIC.
    We don't know whats the problem. The EHPI stopped every time at this point.
    Need Help...
    regards
    Chris

    Issue solved.
    In /etc/hosts the first entry was SAPE11.
    But it must be sape11, because the instance is sape11_E11_00.
    In SM51 we could see that
    sape11_E11_00     SAPE11     Dialog Batch Update Upd2 Spool Enqueue ICM     active
    We changed the entry and restarted SAP.
    Then the job can be started.

  • Suspends fails the first time, but succeeds the second time

    Hi all,
    I am running Arch Linux on my Dell XPS 15 9530 laptop, and overall I am very happy with the combination. I have however had some issues with suspending.
    The problem is that the first time I try to suspend the machine it seems to go to sleep, but then two seconds later it automatically wakes up again. If I then immediately try again to suspend, it works (it does not wake up automatically). Does anyone know what could be going on, and how this can be fixed?
    Usually I suspend from my gnome 3 desktop, but I have also tried to suspend directly using 'systemctl suspend' without having an X server running, and the result is exactly the same. I have tried a few versions of the vanilla kernel, but also the linux-lts and the linux-ck images, but to no avail.
    Here is the output from dmesg, where suspend fails:
    PM: Syncing filesystems ... done.
    PM: Preparing system for mem sleep
    bbswitch: enabling discrete graphics
    Freezing user space processes ... (elapsed 0.543 seconds) done.
    Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    PM: Entering mem sleep
    Suspending console(s) (use no_console_suspend to debug)
    sd 1:0:0:0: [sda] Synchronizing SCSI cache
    smsc75xx 3-1:1.0 enp0s20u1: entering SUSPEND2 mode
    sd 1:0:0:0: [sda] Stopping disk
    Removing pn544
    PM: suspend of devices complete after 334.544 msecs
    PM: late suspend of devices complete after 0.201 msecs
    ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
    ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
    xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
    PM: noirq suspend of devices complete after 26.944 msecs
    ACPI: Preparing to enter system sleep state S3
    PM: Saving platform NVS memory
    Disabling non-boot CPUs ...
    kvm: disabling virtualization on CPU1
    smpboot: CPU 1 is now offline
    kvm: disabling virtualization on CPU2
    smpboot: CPU 2 is now offline
    kvm: disabling virtualization on CPU3
    smpboot: CPU 3 is now offline
    kvm: disabling virtualization on CPU4
    smpboot: CPU 4 is now offline
    kvm: disabling virtualization on CPU5
    smpboot: CPU 5 is now offline
    kvm: disabling virtualization on CPU6
    smpboot: CPU 6 is now offline
    kvm: disabling virtualization on CPU7
    smpboot: CPU 7 is now offline
    ACPI: Low-level resume complete
    PM: Restoring platform NVS memory
    Enabling non-boot CPUs ...
    x86: Booting SMP configuration:
    smpboot: Booting Node 0 Processor 1 APIC 0x2
    kvm: enabling virtualization on CPU1
    Intel pstate controlling: cpu 1
    CPU1 is up
    smpboot: Booting Node 0 Processor 2 APIC 0x4
    kvm: enabling virtualization on CPU2
    Intel pstate controlling: cpu 2
    CPU2 is up
    smpboot: Booting Node 0 Processor 3 APIC 0x6
    kvm: enabling virtualization on CPU3
    Intel pstate controlling: cpu 3
    CPU3 is up
    smpboot: Booting Node 0 Processor 4 APIC 0x1
    kvm: enabling virtualization on CPU4
    Intel pstate controlling: cpu 4
    CPU4 is up
    smpboot: Booting Node 0 Processor 5 APIC 0x3
    kvm: enabling virtualization on CPU5
    Intel pstate controlling: cpu 5
    CPU5 is up
    smpboot: Booting Node 0 Processor 6 APIC 0x5
    kvm: enabling virtualization on CPU6
    Intel pstate controlling: cpu 6
    CPU6 is up
    smpboot: Booting Node 0 Processor 7 APIC 0x7
    kvm: enabling virtualization on CPU7
    Intel pstate controlling: cpu 7
    CPU7 is up
    ACPI: Waking up from system sleep state S3
    acpi LNXPOWER:01: Turning OFF
    xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
    ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
    ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
    PM: noirq resume of devices complete after 73.424 msecs
    PM: early resume of devices complete after 0.091 msecs
    mei_me 0000:00:16.0: irq 49 for MSI/MSI-X
    snd_hda_intel 0000:00:03.0: irq 50 for MSI/MSI-X
    snd_hda_intel 0000:00:1b.0: irq 53 for MSI/MSI-X
    mei_me 0000:00:16.0: NFC MEI VERSION: IVN 0x1 Vendor ID 0x1 Type 0x1
    Probing NFC pn544
    ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
    usb 3-1: reset high-speed USB device number 2 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
    ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
    ata2.00: configured for UDMA/133
    sd 1:0:0:0: [sda] Starting disk
    usb 3-1: reset high-speed USB device number 2 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
    usb 3-1: reset high-speed USB device number 2 using xhci_hcd
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75180
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd751c0
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75200
    smsc75xx 3-1:1.0 enp0s20u1: resuming from SUSPEND2
    usb 3-4: reset full-speed USB device number 3 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
    usb 3-4: reset full-speed USB device number 3 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
    usb 3-4: reset full-speed USB device number 3 using xhci_hcd
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9ac0
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a80
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a40
    usb 3-6: reset full-speed USB device number 4 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
    usb 3-6: reset full-speed USB device number 4 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
    [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
    usb 3-6: reset full-speed USB device number 4 using xhci_hcd
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddc80
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddcc0
    usb 3-11: reset high-speed USB device number 6 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
    usb 3-11: reset high-speed USB device number 6 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
    usb 3-11: reset high-speed USB device number 6 using xhci_hcd
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9480
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9440
    usb 3-9: reset full-speed USB device number 5 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
    usb 3-9: reset full-speed USB device number 5 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
    pciehp 0000:00:1c.0:pcie04: Link Training Error occurs
    pciehp 0000:00:1c.0:pcie04: Failed to check link status
    dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19
    PM: Device 00:08 failed to resume: error -19
    usb 3-9: reset full-speed USB device number 5 using xhci_hcd
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db000
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db040
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db080
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451e80
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451ec0
    PM: resume of devices complete after 2769.054 msecs
    PM: Finishing wakeup.
    Restarting tasks ...
    iwlwifi 0000:06:00.0: no hotplug settings from platform
    rtsx_pci 0000:07:00.0: no hotplug settings from platform
    done.
    Bluetooth: hci0: read Intel version: 370710018002030d00
    Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
    video LNXVIDEO:00: Restoring backlight state
    video LNXVIDEO:01: Restoring backlight state
    bbswitch: disabling discrete graphics
    ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
    smsc75xx 3-1:1.0 enp0s20u1: link down
    smsc75xx 3-1:1.0 enp0s20u1: link down
    smsc75xx 3-1:1.0 enp0s20u1: kevent 4 may have been dropped
    smsc75xx 3-1:1.0 enp0s20u1: link down
    smsc75xx 3-1:1.0 enp0s20u1: link down
    and here where suspend succeeds:
    smsc75xx 3-1:1.0 enp0s20u1: kevent 4 may have been dropped
    smsc75xx 3-1:1.0 enp0s20u1: link up, 100Mbps, full-duplex, lpa 0xC5E1
    smsc75xx 3-1:1.0 enp0s20u1: link up, 100Mbps, full-duplex, lpa 0xC5E1
    PM: Syncing filesystems ... done.
    PM: Preparing system for mem sleep
    bbswitch: enabling discrete graphics
    Freezing user space processes ... (elapsed 0.412 seconds) done.
    Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    PM: Entering mem sleep
    Suspending console(s) (use no_console_suspend to debug)
    sd 1:0:0:0: [sda] Synchronizing SCSI cache
    smsc75xx 3-1:1.0 enp0s20u1: entering SUSPEND2 mode
    sd 1:0:0:0: [sda] Stopping disk
    Removing pn544
    PM: suspend of devices complete after 780.265 msecs
    PM: late suspend of devices complete after 0.387 msecs
    ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
    ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
    xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
    PM: noirq suspend of devices complete after 26.988 msecs
    ACPI: Preparing to enter system sleep state S3
    PM: Saving platform NVS memory
    Disabling non-boot CPUs ...
    kvm: disabling virtualization on CPU1
    smpboot: CPU 1 is now offline
    kvm: disabling virtualization on CPU2
    smpboot: CPU 2 is now offline
    kvm: disabling virtualization on CPU3
    smpboot: CPU 3 is now offline
    kvm: disabling virtualization on CPU4
    smpboot: CPU 4 is now offline
    kvm: disabling virtualization on CPU5
    smpboot: CPU 5 is now offline
    kvm: disabling virtualization on CPU6
    smpboot: CPU 6 is now offline
    kvm: disabling virtualization on CPU7
    smpboot: CPU 7 is now offline
    ACPI: Low-level resume complete
    PM: Restoring platform NVS memory
    Enabling non-boot CPUs ...
    x86: Booting SMP configuration:
    smpboot: Booting Node 0 Processor 1 APIC 0x2
    kvm: enabling virtualization on CPU1
    Intel pstate controlling: cpu 1
    CPU1 is up
    smpboot: Booting Node 0 Processor 2 APIC 0x4
    kvm: enabling virtualization on CPU2
    Intel pstate controlling: cpu 2
    CPU2 is up
    smpboot: Booting Node 0 Processor 3 APIC 0x6
    kvm: enabling virtualization on CPU3
    Intel pstate controlling: cpu 3
    CPU3 is up
    smpboot: Booting Node 0 Processor 4 APIC 0x1
    kvm: enabling virtualization on CPU4
    Intel pstate controlling: cpu 4
    CPU4 is up
    smpboot: Booting Node 0 Processor 5 APIC 0x3
    kvm: enabling virtualization on CPU5
    Intel pstate controlling: cpu 5
    CPU5 is up
    smpboot: Booting Node 0 Processor 6 APIC 0x5
    kvm: enabling virtualization on CPU6
    Intel pstate controlling: cpu 6
    CPU6 is up
    smpboot: Booting Node 0 Processor 7 APIC 0x7
    kvm: enabling virtualization on CPU7
    Intel pstate controlling: cpu 7
    CPU7 is up
    ACPI: Waking up from system sleep state S3
    acpi LNXPOWER:01: Turning OFF
    xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
    ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
    ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
    PM: noirq resume of devices complete after 73.411 msecs
    PM: early resume of devices complete after 0.097 msecs
    mei_me 0000:00:16.0: irq 49 for MSI/MSI-X
    snd_hda_intel 0000:00:03.0: irq 50 for MSI/MSI-X
    snd_hda_intel 0000:00:1b.0: irq 53 for MSI/MSI-X
    mei_me 0000:00:16.0: NFC MEI VERSION: IVN 0x1 Vendor ID 0x1 Type 0x1
    Probing NFC pn544
    ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
    usb 3-4: reset full-speed USB device number 3 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
    ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
    ata2.00: configured for UDMA/133
    sd 1:0:0:0: [sda] Starting disk
    usb 3-4: reset full-speed USB device number 3 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
    usb 3-4: reset full-speed USB device number 3 using xhci_hcd
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9ac0
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a80
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a40
    usb 3-1: reset high-speed USB device number 2 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
    usb 3-1: reset high-speed USB device number 2 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
    usb 3-1: reset high-speed USB device number 2 using xhci_hcd
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75180
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd751c0
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75200
    smsc75xx 3-1:1.0 enp0s20u1: resuming from SUSPEND2
    usb 3-9: reset full-speed USB device number 5 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
    usb 3-9: reset full-speed USB device number 5 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
    [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
    usb 3-9: reset full-speed USB device number 5 using xhci_hcd
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db000
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db040
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db080
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451e80
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451ec0
    usb 3-6: reset full-speed USB device number 4 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
    usb 3-6: reset full-speed USB device number 4 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
    usb 3-6: reset full-speed USB device number 4 using xhci_hcd
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddc80
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddcc0
    usb 3-11: reset high-speed USB device number 6 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
    usb 3-11: reset high-speed USB device number 6 using xhci_hcd
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
    pciehp 0000:00:1c.0:pcie04: Link Training Error occurs
    pciehp 0000:00:1c.0:pcie04: Failed to check link status
    dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19
    PM: Device 00:08 failed to resume: error -19
    usb 3-11: reset high-speed USB device number 6 using xhci_hcd
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9480
    xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9440
    PM: resume of devices complete after 2801.389 msecs
    PM: Finishing wakeup.
    Restarting tasks ...
    iwlwifi 0000:06:00.0: no hotplug settings from platform
    rtsx_pci 0000:07:00.0: no hotplug settings from platform
    done.
    Bluetooth: hci0: read Intel version: 370710018002030d00
    Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
    video LNXVIDEO:00: Restoring backlight state
    video LNXVIDEO:01: Restoring backlight state
    bbswitch: disabling discrete graphics
    ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
    Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
    systemd[1]: Requested transaction contradicts existing jobs: File exists
    systemd[1]: Service sleep.target is not needed anymore. Stopping.
    smsc75xx 3-1:1.0 enp0s20u1: kevent 4 may have been dropped
    smsc75xx 3-1:1.0 enp0s20u1: link down
    smsc75xx 3-1:1.0 enp0s20u1: link down
    It seems to me like the only real difference has to do with the xhci_hcd errors, perhaps the following:
    xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
    Any input or help would be highly appreciated.

    Rexilion wrote:Maybe you could confirm your suspicion by rmmoding xhci before suspend and modprobing it after resume?
    Thanks for the response. I should have said so, but I had already tried that, but without any luck. It seems like it doesn't change anything.

  • Multiple output modules cause render to fail?

    Is anybody else having trouble with using multiple output modules in after effects?  Let me elaborate:  so I'm working on a 3d film, and my worflow is to simply work with the footage side by side in a single comp (we're at HD, so the comp size is 3840x1080).  Very often, I need to fire off a quick render to show to the director.  Most of the time, I just do the left eye by cropping to that 1920x1080 area in the output module.  Other times I need to deliver both eyes, so instead of cropping to 1920x1080, I resize the frame in the output module to 1920x1080.  Yea, we lose half of our horizontal resolution, but that's not such a big deal for us when just working on approvals.
    Here's the thing: sometimes I like to export multiple variations of this at once (ie one output module for the left eye, one for the right eye, and another for the squished side-by-side left-right video).  Whenever I try to output multiple modules with quicktime, it fails.  Every time.
    When it fails, I get two messages: the first (a warning) says "After Effects warning: last frame was written to one or more output modules, but not all! ( 26 :: 153 )"
    The second message (an error) shows up once for each output module: "After Effects error: Rendering error while writing to file "C:\blahh blah blah\whereIputmyfiles\the_render.mov". An output module failed.  The file may be damaged or corrupted. (-1610153464)."  Once it fails, I cannot output to quicktime AT ALL (multiple output modules, or not) without restarting After Effects.
    I tried outputting multiple modules as a PNG sequence... and that worked just fine (if "slow as hell" can ever be called "fine" .... but it worked! )
    I tried outputting to the multiple formats I wanted with one output module per render item (rather than having one render item with multiple modules) as quicktime, and that worked just fine (of course... it takes N times as long though... for N number of outputs).
    I am on Windows 7 64-bit... running After Effects CC 2014... I never had this trouble back when I was working on the CC version (the not 2014 cc version... that is too confusing...).  However, I just went back and tried it with the older version, and it no longer works there either!  What gives?
    When outputting quicktime, I'm using the h.264 codec.
    And before anybody suggests it, no I can't just use AME because that can't resize video (it forces you to keep the aspect ratio through letterboxing) or crop video.

    >The most likely culprit is the h.264 Quicktime. It should have never been included as an option. It doesn't even work well in Quicktime Pro or in Final Cut...
    I'll come to Apple's (partial) defense here:
    Their H.264 codec was written and released at a time when it was difficult to imagine that mainstream computers would have as many CPUs as they do now, so it's somewhat understandable that the severe failures that this codec has with large numbers of threads occurs. Of course, we may all wish that Apple hadn't decided to end development on the QuickTime platform, since this has meant that bugs like this are likely to persist.
    That said, this is why we increasingly recommend that people use other H.264 codecs and not use QuickTime for such things. See the H.264 options currently in Adobe Media Encoder.

  • LibGL error: dlopen /usr/lib/xorg/modules/dri//i915_dri.so failed

    Hello
    I don't have graphic acceleration in my Dell INSPEIRON 6400 laptop.
    I try this:
    http://wiki.archlinux.org/index.php/Intel_GMA_945
    except the 915resolution and then I still didn't have acceleration.
    $ LIBGL_DEBUG=verbose glxinfo
    name of display: :0.0
    libGL: XF86DRIGetClientDriverName: 1.7.4 i915 (screen 0)
    libGL: OpenDriver: trying /usr/lib/xorg/modules/dri//i915_dri.so
    libGL error: dlopen /usr/lib/xorg/modules/dri//i915_dri.so failed (/usr/lib/xorg/modules/dri//i915_dri.so: undefined symbol: _glapi_tls_Context)
    libGL error: unable to load driver: i915_dri.so
    display: :0 screen: 0
    Full log include lspci:
    http://www.shorttext.com/n0u6r
    thanks for your help
    Nadav

    byte wrote:Did you run pacman -Syu lately? What are your package versions? pacman -Q xf86-video-intel xorg-server
    $ pacman -Q xf86-video-intel xorg-server
    xf86-video-intel 2.1.1-2
    xorg-server 1.4-5
    $ sudo p -Syu
    :: Synchronizing package databases...
    core is up to date
    extra is up to date
    community is up to date
    :: Starting full system upgrade...
    local database is up to date
    Last edited by nadavvin (2007-11-18 17:34:18)

  • Unloading modules in ubuntu

    Hi,
    How can I unload modules in ubunt (e.g., graphics module, keyboard, USB etc)?

    umairalipathan, please post questions about Ubuntu on their forums: http://ubuntuforums.org
    Also see: https://wiki.archlinux.org/index.php/Fo … ow_to_Post
    Closing.

  • Unloading Modules in Flex

    What does the debug trace [Unload SWF] mean?
    As per this blog
    http://blogs.adobe.com/tomsugden/2010/02/how_to_unload_modules_effectively.html
    "This trace indicates that the module have been successfully unloaded"
    Is this true?
    I am unloading a module, I see the [Unload SWF] trace, but after unloading, if I try to create an object of a class contained in the unloaded module (using reflection), I am still able to create it.
    Am I understanding it wrong?
    Thanks!

    That means that the bytes of the SWF have been removed from memory.  I'm not
    sure if you're just getting lucky or if there is some other thing going on.
    Post a simple test case.

  • [SOLVED]suspend fails NVRM: GPU at 0000:01:00.0 has fallen off the bus

    Hi All,
    After a update of my laptop, it does not fully wakes after going into suspend. It does not react to numlock anymore.  I have to push the power button for 10 seconds to shut it down.
    /var/log/everything.log, normal operations:
    Jul 21 03:42:38 localhost dhcpcd[1029]: wlan0: sending IPv6 Router Solicitation
    Jul 21 03:42:38 localhost dhcpcd[1029]: wlan0: sendmsg: Cannot assign requested address
    Jul 21 03:42:38 localhost dhcpcd[1029]: wlan0: no IPv6 Routers available
    Jul 21 03:42:45 localhost dbus[533]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
    Jul 21 03:42:45 localhost dbus[533]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
    Jul 21 03:42:45 localhost acpid: client connected from 1134[0:1000]
    Jul 21 03:42:45 localhost acpid: 1 client rule loaded
    Jul 21 03:42:46 localhost NetworkManager[559]: <info> (wlan0): IP6 addrconf timed out or failed.
    Jul 21 03:42:46 localhost NetworkManager[559]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Jul 21 03:42:46 localhost NetworkManager[559]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Jul 21 03:42:46 localhost NetworkManager[559]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Jul 21 03:42:50 localhost acpid: client connected from 1134[0:1000]
    Jul 21 03:42:50 localhost acpid: 1 client rule loaded
    Jul 21 03:42:55 localhost kernel: [ 48.812457] fuse init (API version 7.18)
    Jul 21 03:42:59 localhost dbus[533]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
    Jul 21 03:42:59 localhost udisksd[1209]: udisks daemon version 1.94.0 starting
    Jul 21 03:42:59 localhost dbus[533]: [system] Successfully activated service 'org.freedesktop.UDisks2'
    Jul 21 03:42:59 localhost udisksd[1209]: Acquired the name org.freedesktop.UDisks2 on the system message bus
    Jul 21 04:01:01 localhost /USR/SBIN/CROND[1363]: (root) CMD (run-parts /etc/cron.hourly)
    Jul 21 04:01:01 localhost anacron[1369]: Anacron started on 2012-07-21
    Jul 21 04:01:01 localhost anacron[1369]: Will run job `cron.daily' in 42 min.
    Jul 21 04:01:01 localhost anacron[1369]: Jobs will be executed sequentially
    Jul 21 04:21:01 localhost -- MARK --
    /var/log/everything.log, after starting suspend:
    Jul 21 04:21:13 localhost kernel: [ 2346.821030] EXT4-fs (sda5): re-mounted. Opts: commit=0
    Jul 21 04:21:13 localhost kernel: [ 2347.000872] EXT4-fs (sda8): re-mounted. Opts: commit=0
    Jul 21 04:25:10 localhost kernel: [ 2349.512404] PM: Syncing filesystems ... done.
    Jul 21 04:25:10 localhost kernel: [ 2349.514874] PM: Preparing system for mem sleep
    Jul 21 04:25:10 localhost kernel: [ 2349.514891] Freezing user space processes ... (elapsed 0.01 seconds) done.
    Jul 21 04:25:10 localhost kernel: [ 2349.526541] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
    Jul 21 04:25:10 localhost kernel: [ 2349.539896] PM: Entering mem sleep
    Jul 21 04:25:10 localhost kernel: [ 2349.539930] Suspending console(s) (use no_console_suspend to debug)
    Jul 21 04:25:10 localhost kernel: [ 2349.573787] sd 0:0:0:0: [sda] Synchronizing SCSI cache
    Jul 21 04:25:10 localhost kernel: [ 2349.611052] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:25:10 localhost kernel: [ 2349.613512] sd 0:0:0:0: [sda] Stopping disk
    Jul 21 04:25:10 localhost kernel: [ 2350.236650] PM: suspend of devices complete after 696.314 msecs
    Jul 21 04:25:10 localhost kernel: [ 2350.236925] PM: late suspend of devices complete after 0.270 msecs
    Jul 21 04:25:10 localhost kernel: [ 2350.237272] r8169 0000:08:00.0: wake-up capability enabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.266603] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.303271] uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.326605] uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.343218] ehci_hcd 0000:00:1a.7: wake-up capability enabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.379942] uhci_hcd 0000:00:1a.2: wake-up capability enabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.403292] uhci_hcd 0000:00:1a.1: wake-up capability enabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.426606] uhci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.426678] PM: noirq suspend of devices complete after 189.749 msecs
    Jul 21 04:25:10 localhost kernel: [ 2350.427140] ACPI: Preparing to enter system sleep state S3
    Jul 21 04:25:10 localhost kernel: [ 2350.519991] PM: Saving platform NVS memory
    Jul 21 04:25:10 localhost kernel: [ 2350.520810] Disabling non-boot CPUs ...
    Jul 21 04:25:10 localhost kernel: [ 2350.623205] CPU 1 is now offline
    Jul 21 04:25:10 localhost kernel: [ 2350.623688] Extended CMOS year: 2000
    Jul 21 04:25:10 localhost kernel: [ 2350.623688] ACPI: Low-level resume complete
    Jul 21 04:25:10 localhost kernel: [ 2350.623688] PM: Restoring platform NVS memory
    Jul 21 04:25:10 localhost kernel: [ 2350.623688] Extended CMOS year: 2000
    Jul 21 04:25:10 localhost kernel: [ 2350.623688] Enabling non-boot CPUs ...
    Jul 21 04:25:10 localhost kernel: [ 2350.630554] Booting Node 0 Processor 1 APIC 0x1
    Jul 21 04:25:10 localhost kernel: [ 2350.641916] NMI watchdog: enabled, takes one hw-pmu counter.
    Jul 21 04:25:10 localhost kernel: [ 2350.645407] CPU1 is up
    Jul 21 04:25:10 localhost kernel: [ 2350.647122] ACPI: Waking up from system sleep state S3
    Jul 21 04:25:10 localhost kernel: [ 2350.653227] uhci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.659889] uhci_hcd 0000:00:1a.1: wake-up capability disabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.666555] uhci_hcd 0000:00:1a.2: wake-up capability disabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.683204] ehci_hcd 0000:00:1a.7: wake-up capability disabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.689888] uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.696556] uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.713204] ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.715075] PM: noirq resume of devices complete after 67.761 msecs
    Jul 21 04:25:10 localhost kernel: [ 2350.715286] PM: early resume of devices complete after 0.105 msecs
    Jul 21 04:25:10 localhost kernel: [ 2350.715344] uhci_hcd 0000:00:1a.0: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715373] usb usb1: root hub lost power or was reset
    Jul 21 04:25:10 localhost kernel: [ 2350.715391] uhci_hcd 0000:00:1a.1: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715421] usb usb2: root hub lost power or was reset
    Jul 21 04:25:10 localhost kernel: [ 2350.715437] uhci_hcd 0000:00:1a.2: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715465] usb usb3: root hub lost power or was reset
    Jul 21 04:25:10 localhost kernel: [ 2350.715480] ehci_hcd 0000:00:1a.7: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715521] uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715540] snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X
    Jul 21 04:25:10 localhost kernel: [ 2350.715550] usb usb4: root hub lost power or was reset
    Jul 21 04:25:10 localhost kernel: [ 2350.715571] uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715601] usb usb5: root hub lost power or was reset
    Jul 21 04:25:10 localhost kernel: [ 2350.715611] uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715623] ehci_hcd 0000:00:1d.7: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715639] usb usb6: root hub lost power or was reset
    Jul 21 04:25:10 localhost kernel: [ 2350.715647] pci 0000:00:1e.0: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715663] ata_piix 0000:00:1f.2: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715667] ata_piix 0000:00:1f.5: setting latency timer to 64
    Jul 21 04:25:10 localhost kernel: [ 2350.715690] r8169 0000:08:00.0: wake-up capability disabled by ACPI
    Jul 21 04:25:10 localhost kernel: [ 2350.723377] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:25:10 localhost kernel: [ 2350.723395] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:25:10 localhost kernel: [ 2350.816609] r8169 0000:08:00.0: eth0: link down
    Jul 21 04:25:10 localhost kernel: [ 2351.111777] ata4: SATA link down (SStatus 0 SControl 300)
    Jul 21 04:25:10 localhost kernel: [ 2351.128460] ata3: SATA link down (SStatus 0 SControl 300)
    Jul 21 04:25:10 localhost kernel: [ 2351.199920] usb 2-1: reset low-speed USB device number 2 using uhci_hcd
    Jul 21 04:25:10 localhost kernel: [ 2351.263475] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Jul 21 04:25:10 localhost kernel: [ 2351.276859] firewire_core 0000:1a:00.0: rediscovered device fw0
    Jul 21 04:25:10 localhost kernel: [ 2351.283960] ata2.00: configured for UDMA/100
    Jul 21 04:25:10 localhost kernel: [ 2351.739942] usb 2-2: reset low-speed USB device number 3 using uhci_hcd
    Jul 21 04:25:10 localhost kernel: [ 2352.129932] usb 8-2: reset high-speed USB device number 2 using ehci_hcd
    Jul 21 04:25:10 localhost kernel: [ 2352.359839] usb 6-1: reset full-speed USB device number 2 using uhci_hcd
    Jul 21 04:25:10 localhost kernel: [ 2352.784239] usb 6-1.1: reset full-speed USB device number 3 using uhci_hcd
    Jul 21 04:25:10 localhost kernel: [ 2352.883229] btusb 6-1.1:1.0: no reset_resume for driver btusb?
    Jul 21 04:25:10 localhost kernel: [ 2352.883233] btusb 6-1.1:1.1: no reset_resume for driver btusb?
    Jul 21 04:25:10 localhost kernel: [ 2352.941243] usb 6-1.2: reset full-speed USB device number 4 using uhci_hcd
    Jul 21 04:25:10 localhost kernel: [ 2352.969919] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Jul 21 04:25:10 localhost kernel: [ 2353.101249] usb 6-1.3: reset full-speed USB device number 5 using uhci_hcd
    Jul 21 04:25:10 localhost kernel: [ 2353.181194] ata1.00: configured for UDMA/133
    Jul 21 04:25:10 localhost kernel: [ 2353.181463] sd 0:0:0:0: [sda] Starting disk
    Jul 21 04:25:10 localhost kernel: [ 2353.436737] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
    Jul 21 04:25:10 localhost kernel: [ 2358.057138] PM: resume of devices complete after 7341.844 msecs
    Jul 21 04:25:10 localhost kernel: [ 2358.057602] PM: Finishing wakeup.
    Jul 21 04:25:10 localhost kernel: [ 2358.057604] Restarting tasks ... done.
    Jul 21 04:25:10 localhost kernel: [ 2358.064234] video LNXVIDEO:00: Restoring backlight state
    Jul 21 04:25:11 localhost kernel: [ 2358.233575] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:25:11 localhost kernel: [ 2358.272368] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:25:11 localhost kernel: [ 2358.309721] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:25:11 localhost kernel: [ 2358.349601] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:25:13 localhost kernel: [ 2360.644416] EXT4-fs (sda5): re-mounted. Opts: commit=0
    Jul 21 04:25:13 localhost kernel: [ 2360.648163] EXT4-fs (sda8): re-mounted. Opts: commit=0
    Jul 21 04:25:13 localhost acpid: client 1134[0:1000] has disconnected
    Jul 21 04:25:13 localhost acpid: client 1134[0:1000] has disconnected
    Jul 21 04:25:13 localhost acpid: client connected from 1134[0:1000]
    Jul 21 04:25:13 localhost acpid: 1 client rule loaded
    Jul 21 04:25:26 localhost kernel: [ 2373.415894] NVRM: Xid (0000:01:00): 8, Channel 0000007e
    Jul 21 04:25:26 localhost kernel: [ 2373.700350] hrtimer: interrupt took 91847280 ns
    Jul 21 04:25:26 localhost kernel: [ 2373.700352] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
    Jul 21 04:28:36 localhost kernel: [ 2563.568752] EXT4-fs (sda5): re-mounted. Opts: commit=0
    Jul 21 04:28:36 localhost kernel: [ 2563.573610] EXT4-fs (sda8): re-mounted. Opts: commit=0
    What does this message mean?
    Jul 21 04:25:26 localhost kernel: [ 2373.700352] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
    What can i do to solve this?
    Best regards,
    Cedric
    Last edited by cdwijs (2012-08-09 18:33:34)

    I did a quick google search. This page suggested that I set my videocard in persistend mode:
    http://scientificlinuxforum.org/index.p … topic=1469
    So i did the following:
    ]# /usr/bin/nvidia-smi -pm 1
    Enabled persistence mode for GPU 0000:01:00.0.
    All done.
    # /usr/bin/nvidia-smi -q
    ==============NVSMI LOG==============
    Timestamp : Sat Jul 21 04:58:55 2012
    Driver Version : 302.17
    Attached GPUs : 1
    GPU 0000:01:00.0
    Product Name : GeForce 9600M GS
    Display Mode : N/A
    Persistence Mode : Enabled
    Driver Model
    Current : N/A
    Pending : N/A
    Serial Number : N/A
    GPU UUID : N/A
    VBIOS Version : 62.94.8D.00.0B
    Inforom Version
    OEM Object : N/A
    ECC Object : N/A
    Power Management Object : N/A
    PCI
    Bus : 0x01
    Device : 0x00
    Domain : 0x0000
    Device Id : 0x064810DE
    Bus Id : 0000:01:00.0
    Sub System Id : 0x02C01028
    GPU Link Info
    PCIe Generation
    Max : N/A
    Current : N/A
    Link Width
    Max : N/A
    Current : N/A
    Fan Speed : N/A
    Performance State : N/A
    Memory Usage
    Total : 511 MB
    Used : 30 MB
    Free : 480 MB
    Compute Mode : Default
    Utilization
    Gpu : N/A
    Memory : N/A
    Ecc Mode
    Current : N/A
    Pending : N/A
    ECC Errors
    Volatile
    Single Bit
    Device Memory : N/A
    Register File : N/A
    L1 Cache : N/A
    L2 Cache : N/A
    Total : N/A
    Double Bit
    Device Memory : N/A
    Register File : N/A
    L1 Cache : N/A
    L2 Cache : N/A
    Total : N/A
    Aggregate
    Single Bit
    Device Memory : N/A
    Register File : N/A
    L1 Cache : N/A
    L2 Cache : N/A
    Total : N/A
    Double Bit
    Device Memory : N/A
    Register File : N/A
    L1 Cache : N/A
    L2 Cache : N/A
    Total : N/A
    Temperature
    Gpu : 61 C
    Power Readings
    Power Management : N/A
    Power Draw : N/A
    Power Limit : N/A
    Clocks
    Graphics : N/A
    SM : N/A
    Memory : N/A
    Max Clocks
    Graphics : N/A
    SM : N/A
    Memory : N/A
    Compute Processes : Not Supported
    This did not solve the issue. The laptop goes into suspend (the power LED starts blinking), but when the power button is then briefly pressed, the machine does power-up, but after hearing 2 clicks from the speaker, i get a black screen, a full-running CPU fan, and no reaction to numlock.
    /var/log/everything.log:
    Jul 21 04:30:13 localhost NetworkManager[565]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Jul 21 04:50:40 localhost -- MARK --
    Jul 21 04:54:46 localhost kernel: [ 1516.765698] EXT4-fs (sda5): re-mounted. Opts: commit=0
    Jul 21 04:54:46 localhost kernel: [ 1516.942964] EXT4-fs (sda8): re-mounted. Opts: commit=0
    Jul 21 04:55:02 localhost kernel: [ 1519.654895] PM: Syncing filesystems ... done.
    Jul 21 04:55:02 localhost kernel: [ 1519.657049] PM: Preparing system for mem sleep
    Jul 21 04:55:02 localhost kernel: [ 1519.657066] Freezing user space processes ... (elapsed 0.01 seconds) done.
    Jul 21 04:55:02 localhost kernel: [ 1519.669943] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
    Jul 21 04:55:02 localhost kernel: [ 1519.683296] PM: Entering mem sleep
    Jul 21 04:55:02 localhost kernel: [ 1519.683337] Suspending console(s) (use no_console_suspend to debug)
    Jul 21 04:55:02 localhost kernel: [ 1519.717139] sd 0:0:0:0: [sda] Synchronizing SCSI cache
    Jul 21 04:55:02 localhost kernel: [ 1519.749832] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:55:02 localhost kernel: [ 1519.786781] sd 0:0:0:0: [sda] Stopping disk
    Jul 21 04:55:02 localhost kernel: [ 1520.410064] PM: suspend of devices complete after 726.343 msecs
    Jul 21 04:55:02 localhost kernel: [ 1520.410337] PM: late suspend of devices complete after 0.266 msecs
    Jul 21 04:55:02 localhost kernel: [ 1520.410678] r8169 0000:08:00.0: wake-up capability enabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.440024] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.476689] uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.500023] uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.516685] ehci_hcd 0000:00:1a.7: wake-up capability enabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.553353] uhci_hcd 0000:00:1a.2: wake-up capability enabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.576688] uhci_hcd 0000:00:1a.1: wake-up capability enabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.603354] uhci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.603426] PM: noirq suspend of devices complete after 193.085 msecs
    Jul 21 04:55:02 localhost kernel: [ 1520.603888] ACPI: Preparing to enter system sleep state S3
    Jul 21 04:55:02 localhost kernel: [ 1520.693403] PM: Saving platform NVS memory
    Jul 21 04:55:02 localhost kernel: [ 1520.694218] Disabling non-boot CPUs ...
    Jul 21 04:55:02 localhost kernel: [ 1520.796623] CPU 1 is now offline
    Jul 21 04:55:02 localhost kernel: [ 1520.797088] Extended CMOS year: 2000
    Jul 21 04:55:02 localhost kernel: [ 1520.797088] ACPI: Low-level resume complete
    Jul 21 04:55:02 localhost kernel: [ 1520.797088] PM: Restoring platform NVS memory
    Jul 21 04:55:02 localhost kernel: [ 1520.797088] Extended CMOS year: 2000
    Jul 21 04:55:02 localhost kernel: [ 1520.797088] Enabling non-boot CPUs ...
    Jul 21 04:55:02 localhost kernel: [ 1520.803951] Booting Node 0 Processor 1 APIC 0x1
    Jul 21 04:55:02 localhost kernel: [ 1520.815303] NMI watchdog: enabled, takes one hw-pmu counter.
    Jul 21 04:55:02 localhost kernel: [ 1520.816608] CPU1 is up
    Jul 21 04:55:02 localhost kernel: [ 1520.818293] ACPI: Waking up from system sleep state S3
    Jul 21 04:55:02 localhost kernel: [ 1520.823322] uhci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.829975] uhci_hcd 0000:00:1a.1: wake-up capability disabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.836638] uhci_hcd 0000:00:1a.2: wake-up capability disabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.853290] ehci_hcd 0000:00:1a.7: wake-up capability disabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.859971] uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.866638] uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.883290] ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.885162] PM: noirq resume of devices complete after 66.681 msecs
    Jul 21 04:55:02 localhost kernel: [ 1520.885372] PM: early resume of devices complete after 0.105 msecs
    Jul 21 04:55:02 localhost kernel: [ 1520.885432] uhci_hcd 0000:00:1a.0: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885432] uhci_hcd 0000:00:1a.1: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885465] usb usb1: root hub lost power or was reset
    Jul 21 04:55:02 localhost kernel: [ 1520.885466] usb usb2: root hub lost power or was reset
    Jul 21 04:55:02 localhost kernel: [ 1520.885487] uhci_hcd 0000:00:1a.2: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885490] ehci_hcd 0000:00:1a.7: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885518] usb usb3: root hub lost power or was reset
    Jul 21 04:55:02 localhost kernel: [ 1520.885549] uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885582] usb usb4: root hub lost power or was reset
    Jul 21 04:55:02 localhost kernel: [ 1520.885582] snd_hda_intel 0000:00:1b.0: irq 48 for MSI/MSI-X
    Jul 21 04:55:02 localhost kernel: [ 1520.885600] uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885629] usb usb5: root hub lost power or was reset
    Jul 21 04:55:02 localhost kernel: [ 1520.885648] uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885653] ehci_hcd 0000:00:1d.7: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885680] pci 0000:00:1e.0: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885679] usb usb6: root hub lost power or was reset
    Jul 21 04:55:02 localhost kernel: [ 1520.885698] ata_piix 0000:00:1f.2: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885713] ata_piix 0000:00:1f.5: setting latency timer to 64
    Jul 21 04:55:02 localhost kernel: [ 1520.885736] r8169 0000:08:00.0: wake-up capability disabled by ACPI
    Jul 21 04:55:02 localhost kernel: [ 1520.890553] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:55:02 localhost kernel: [ 1520.891048] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:55:02 localhost kernel: [ 1520.960285] r8169 0000:08:00.0: eth0: link down
    Jul 21 04:55:02 localhost kernel: [ 1521.281391] ata3: SATA link down (SStatus 0 SControl 300)
    Jul 21 04:55:02 localhost kernel: [ 1521.297666] ata4: SATA link down (SStatus 0 SControl 300)
    Jul 21 04:55:02 localhost kernel: [ 1521.332377] Extended CMOS year: 2000
    Jul 21 04:55:02 localhost kernel: [ 1521.376657] usb 2-1: reset low-speed USB device number 2 using uhci_hcd
    Jul 21 04:55:02 localhost kernel: [ 1521.406940] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Jul 21 04:55:02 localhost kernel: [ 1521.427670] ata2.00: configured for UDMA/100
    Jul 21 04:55:02 localhost acpid: client 1147[0:1000] has disconnected
    Jul 21 04:55:02 localhost acpid: client 1147[0:1000] has disconnected
    Jul 21 04:55:02 localhost kernel: [ 1521.453328] firewire_core 0000:1a:00.0: rediscovered device fw0
    Jul 21 04:55:02 localhost kernel: [ 1521.915219] usb 2-2: reset low-speed USB device number 3 using uhci_hcd
    Jul 21 04:55:02 localhost kernel: [ 1522.303337] usb 8-2: reset high-speed USB device number 2 using ehci_hcd
    Jul 21 04:55:02 localhost kernel: [ 1522.533339] usb 6-1: reset full-speed USB device number 2 using uhci_hcd
    Jul 21 04:55:02 localhost kernel: [ 1522.955078] usb 6-1.1: reset full-speed USB device number 3 using uhci_hcd
    Jul 21 04:55:02 localhost kernel: [ 1523.057065] btusb 6-1.1:1.0: no reset_resume for driver btusb?
    Jul 21 04:55:02 localhost kernel: [ 1523.057070] btusb 6-1.1:1.1: no reset_resume for driver btusb?
    Jul 21 04:55:02 localhost kernel: [ 1523.113342] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Jul 21 04:55:02 localhost kernel: [ 1523.115078] usb 6-1.2: reset full-speed USB device number 4 using uhci_hcd
    Jul 21 04:55:02 localhost kernel: [ 1523.278082] usb 6-1.3: reset full-speed USB device number 5 using uhci_hcd
    Jul 21 04:55:02 localhost kernel: [ 1523.321369] ata1.00: configured for UDMA/133
    Jul 21 04:55:02 localhost kernel: [ 1523.321637] sd 0:0:0:0: [sda] Starting disk
    Jul 21 04:55:02 localhost kernel: [ 1523.613501] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
    Jul 21 04:55:02 localhost kernel: [ 1528.234017] PM: resume of devices complete after 7348.637 msecs
    Jul 21 04:55:02 localhost kernel: [ 1528.234472] PM: Finishing wakeup.
    Jul 21 04:55:02 localhost kernel: [ 1528.234474] Restarting tasks ... done.
    Jul 21 04:55:02 localhost kernel: [ 1528.239320] video LNXVIDEO:00: Restoring backlight state
    Jul 21 04:55:02 localhost acpid: client connected from 1147[0:1000]
    Jul 21 04:55:02 localhost acpid: 1 client rule loaded
    Jul 21 04:55:02 localhost kernel: [ 1528.396372] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:55:02 localhost kernel: [ 1528.433245] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:55:02 localhost kernel: [ 1528.469720] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:55:02 localhost kernel: [ 1528.506634] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
    Jul 21 04:55:03 localhost kernel: [ 1530.007718] EXT4-fs (sda5): re-mounted. Opts: commit=0
    Jul 21 04:55:04 localhost kernel: [ 1530.271879] EXT4-fs (sda8): re-mounted. Opts: commit=0
    Jul 21 04:55:55 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuset
    Jul 21 04:55:55 localhost kernel: [ 0.000000] Initializing cgroup subsys cpu
    Interestingly, the message that the GPU has fallen off the bus is no longer present. Something else is going on as well :-)
    Best regards,
    Cedric

  • [SOLVED] nVidia 87.76 Drivers installer fails to build kernel module

    Hey,
    I have a nVidia GeForce2 Integrated graphics card on my Asus A7N266 motherboard. According to the nVidia site, http://www.nvidia.com/object/IO_32667.html, the most recent driver that supports this is the 96.xx series. Yet as shown here, http://www.nvnews.net/vbulletin/showthread.php?t=87332, many people have found that the 96.xx series drivers cause graphical corruption when using a GeForce2 IGP.
    Before coming to Arch, I had used Xubuntu 7.04 and managed to compile the last known working drivers, version 87.76, following the instructions here: http://kmandla.wordpress.com/2007/03/25 … 20-12-386/
    That all went well but now I'm using Arch. I tried using the nvidia-96.xx driver in the repos just for testing sake but I still got the same graphical corruption.
    Thus I have been trying to install the 87.76 drivers on Arch, but it always fails at the kernel module building stage. I had first applied this patch here, http://www.nvnews.net/vbulletin/showthr … ost1086669, before compling as the plain driver wont compile against recent kernels.
    Here is the output from the installer:
    nvidia-installer log file '/var/log/nvidia-installer.log'
    creation time: Sun Aug 5 11:57:53 2007
    option status:
    license pre-accepted : false
    update : false
    force update : false
    expert : false
    uninstall : false
    driver info : false
    precompiled interfaces : true
    no ncurses color : false
    query latest version : false
    OpenGL header files : true
    no questions : false
    silent : false
    no recursion : false
    no backup : false
    kernel module only : false
    sanity : false
    add this kernel : false
    no runlevel check : false
    no network : false
    no ABI note : false
    no RPMs : false
    no kernel module : false
    force SELinux : default
    force tls : (not specified)
    X install prefix : (not specified)
    X library install path : (not specified)
    X module install path : (not specified)
    OpenGL install prefix : (not specified)
    OpenGL install libdir : (not specified)
    utility install prefix : (not specified)
    utility install libdir : (not specified)
    doc install prefix : (not specified)
    kernel name : (not specified)
    kernel include path : (not specified)
    kernel source path : (not specified)
    kernel output path : (not specified)
    kernel install path : (not specified)
    proc mount point : /proc
    ui : (not specified)
    tmpdir : /tmp
    ftp mirror : ftp://download.nvidia.com
    RPM file list : (not specified)
    Using: nvidia-installer ncurses user interface
    -> License accepted.
    -> No precompiled kernel interface was found to match your kernel; would you li
    ke the installer to attempt to download a kernel interface for your kernel f
    rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: Yes)
    -> No matching precompiled kernel interface was found on the NVIDIA ftp site;
    this means that the installer will need to compile a kernel interface for
    your kernel.
    -> Performing CC sanity check with CC="cc".
    -> Performing CC version check with CC="cc".
    -> Kernel source path: '/lib/modules/2.6.22-ARCH/build'
    -> Kernel output path: '/lib/modules/2.6.22-ARCH/build'
    -> Performing rivafb check.
    -> Performing nvidiafb check.
    -> Cleaning kernel module build directory.
    executing: 'cd ./usr/src/nv; make clean'...
    rm -f -f nv.o nv-vm.o os-agp.o os-interface.o os-registry.o nv-i2c.o nv.o nv
    -vm.o os-agp.o os-interface.o os-registry.o nv-i2c.o nvidia.mod.o
    rm -f -f build-in.o nv-linux.o *.d .*.{cmd,flags}
    rm -f -f nvidia.{o,ko,mod.{o,c}} nv_compiler.h *~
    rm -f -f stprof stprof.o symtab.h
    rm -f -rf .tmp_versions
    -> Building kernel module:
    executing: 'cd ./usr/src/nv; make module SYSSRC=/lib/modules/2.6.22-ARCH/bui
    ld SYSOUT=/lib/modules/2.6.22-ARCH/build'...
    NVIDIA: calling KBUILD...
    make CC=cc KBUILD_VERBOSE=1 -C /lib/modules/2.6.22-ARCH/build SUBDIRS=/home
    /kris/Source/nVidia GLX 87.76 Driver/NVIDIA-Linux-x86-1.0-8776-pkg1/usr/src/
    nv modules
    test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
    echo; \
    echo " ERROR: Kernel configuration is invalid."; \
    echo " include/linux/autoconf.h or include/config/auto.conf are mis
    sing."; \
    echo " Run 'make oldconfig && make prepare' on kernel src to fix it
    echo; \
    /bin/false)
    make[2]: *** No rule to make target `GLX'. Stop.
    NVIDIA: left KBUILD.
    nvidia.ko failed to build!
    make[1]: *** [mdl] Error 1
    make: *** [module] Error 2
    -> Error.
    ERROR: Unable to build the NVIDIA kernel module.
    ERROR: Installation has failed. Please see the file
    '/var/log/nvidia-installer.log' for details. You may find suggestions
    on fixing installation problems in the README available on the Linux
    driver download page at www.nvidia.com.
    Any ideas as to how I can get the kernel module to build?
    I am using 'kernel26 2.6.22.1-4' with the 'kernel-headers 2.6.22.1-1' from the testing repo.
    Last edited by Nameless One (2007-08-10 07:08:38)

    make CC=cc  KBUILD_VERBOSE=1 -C /lib/modules/2.6.22-ARCH/buildSUBDIRS=/home/kris/Source/nVidia GLX 87.76 Driver/NVIDIA-Linux-x86-1.0-8776-pkg1/usr/src/
    The name of the directory you placed the driver in contains spaces. That is  why you get the no rule to make target GLX error.
    It would be better not to circumvent pacman. I am using the following PKGBUILDs for the 8776 driver:
    nvidia-8776:
    pkgname=nvidia-8776
    pkgver=1.0.8776
    _nver=1.0-8776
    _kernver='2.6.22-ARCH'
    pkgrel=1
    pkgdesc="NVIDIA drivers for Arch kernel."
    arch=(i686 x86_64)
    [ "$CARCH" = "i686" ] && ARCH=x86
    [ "$CARCH" = "x86_64" ] && ARCH=x86_64
    url="http://www.nvidia.com/"
    depends=(kernel26 nvidia-8776-utils)
    conflicts=('nvidia' 'nvidia-96xx' 'nvidia-71xx' 'nvidia-legacy')
    install=nvidia.install
    source=(http://download.nvidia.com/XFree86/Linux-$ARCH/${_nver}/NVIDIA-Linux-$ARCH-${_nver}-pkg0.run NVIDIA_kernel-1.0-8776-20061203.diff.txt)
    md5sums=('93ad45fe7b974a5a80348e1890f9b7c9' '70e669f06ee4881c2583261672de292a')
    [ "$CARCH" = "x86_64" ] && md5sums=('f5340e4bbce811add994b1685cdea03b' '70e669f06ee4881c2583261672de292a')
    build()
    # Extract
    cd $startdir/src/
    sh NVIDIA-Linux-$ARCH-${_nver}-pkg0.run --extract-only
    cd NVIDIA-Linux-$ARCH-${_nver}-pkg0
    # Any extra patches are applied in here...
    patch -p0 < $startdir/NVIDIA_kernel-1.0-8776-20061203.diff.txt ||return 1
    cd usr/src/nv/
    ln -s Makefile.kbuild Makefile
    make SYSSRC=/lib/modules/$_kernver/build module || return 1
    # install kernel module
    mkdir -p $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/video/
    install -m644 nvidia.ko $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/video/
    sed -i -e "s/KERNEL_VERSION='.*'/KERNEL_VERSION='${_kernver}'/" $startdir/*.install
    Place the patch (NVIDIA_kernel-1.0-8776-20061203.diff.txt) and nvidia.install in the same directory as the PKGBUILD.
    nvidia-utils:
    pkgname=nvidia-8776-utils
    pkgver=1.0.8776
    _nver=1.0-8776
    pkgrel=1
    pkgdesc="NVIDIA drivers utilities and libraries."
    arch=(i686 x86_64)
    [ "$CARCH" = "i686" ] && ARCH=x86
    [ "$CARCH" = "x86_64" ] && ARCH=x86_64
    url="http://www.nvidia.com/"
    depends=(xorg-server)
    conflicts=('libgl' 'libgl-dri' 'ati-fglrx-utils' 'nvidia-legacy-utils' 'nvidia-71xx-utils' 'nvidia-96xx-utils')
    provides=('libgl' )
    #install=nvidia.install
    source=(http://download.nvidia.com/XFree86/Linux-$ARCH/${_nver}/NVIDIA-Linux-$ARCH-${_nver}-pkg0.run)
    md5sums=('93ad45fe7b974a5a80348e1890f9b7c9')
    [ "$CARCH" = "x86_64" ] && md5sums=('f5340e4bbce811add994b1685cdea03b')
    build()
    # override nvida install routine and do it the long way.
    cd $startdir/src/
    sh NVIDIA-Linux-${ARCH}-${_nver}-pkg0.run --extract-only
    cd NVIDIA-Linux-${ARCH}-${_nver}-pkg0/usr/
    mkdir -p $startdir/pkg/usr/{lib,bin,share/applications,share/pixmaps,man/man1}
    mkdir -p $startdir/pkg/usr/lib/xorg/modules/{extensions,drivers}
    mkdir -p $startdir/pkg/usr/share/licenses/nvidia/
    install `find lib/ -iname \*.so\*` $startdir/pkg/usr/lib/
    install lib/tls/* $startdir/pkg/usr/lib
    install share/man/man1/* $startdir/pkg/usr/man/man1/
    rm $startdir/pkg/usr/man/man1/nvidia-installer.1.gz
    install X11R6/lib/libXv* $startdir/pkg/usr/lib/
    install share/applications/nvidia-settings.desktop $startdir/pkg/usr/share/applications/
    # fix nvidia .desktop file
    sed -e 's:__UTILS_PATH__:/usr/bin:' -e 's:__PIXMAP_PATH__:/usr/share/pixmaps:' -i $startdir/pkg/usr/share/applications/nvidia-settings.desktop
    install share/pixmaps/nvidia-settings.png $startdir/pkg/usr/share/pixmaps/
    install X11R6/lib/modules/drivers/nvidia_drv.so $startdir/pkg/usr/lib/xorg/modules/drivers
    install X11R6/lib/modules/extensions/libglx.so.$pkgver $startdir/pkg/usr/lib/xorg/modules/extensions
    install -m755 bin/nvidia-{settings,xconfig,bug-report.sh} $startdir/pkg/usr/bin/
    cd $startdir/pkg/usr/lib/;
    ln -s /usr/lib/libGL.so.$pkgver libGL.so
    ln -s /usr/lib/libGL.so.$pkgver libGL.so.1
    ln -s /usr/lib/libGLcore.so.$pkgver libGLcore.so.1
    ln -s /usr/lib/libnvidia-cfg.so.$pkgver libnvidia-cfg.so.1
    ln -s /usr/lib/libnvidia-tls.so.$pkgver libnvidia-tls.so.1
    cd $startdir/pkg/usr/lib/xorg/modules/extensions;
    ln -s /usr/lib/xorg/modules/extensions/libglx.so.$pkgver libglx.so
    install $startdir/src/NVIDIA-Linux-${ARCH}-${_nver}-pkg0/LICENSE $startdir/pkg/usr/share/licenses/nvidia/
    find $startdir/pkg/usr -type d -exec chmod 755 {} \;
    # phew :)
    Last edited by kappa (2007-08-09 11:14:42)

  • [Solved] Nvidia module fails to load on lastest kernel (3.6.7-1-ARCH)

    Hi there!
    I have just updated my desktop PC yesterday, as I normally do every week (yaourt -Syu --aur), and today when I rebooted my Xorg refuses to load.
    I've checked the logs, etc, and I think there's a problem with the nvidia module. In fact, I can't even modprobe it.
    I've googled for hours, but I can't find any solution out there...
    Here you have the log: https://dl.dropbox.com/u/1732176/Xorg.0.log
    Any hint will be appreciated...
    Thanks in advance ^^
    Last edited by roobre (2012-11-24 16:18:40)

    falconindy wrote:
    [ 24.672] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
    [ 24.672] (EE) NVIDIA: system's kernel log for additional error messages.
    Perhaps you should look at dmesg.
    Thanks!
    Looking there I found:
    [ 5.371106] NVRM: The NVIDIA GeForce 7100 / nForce 630i GPU installed in this system is
    NVRM: supported through the NVIDIA 304.xx Legacy drivers. Please
    NVRM: visit http://www.nvidia.com/object/unix.html for more
    NVRM: information. The 310.19 NVIDIA driver will ignore
    NVRM: this GPU. Continuing probe...
    I'll try to pacman those drivers and check again...
    [EDIT]
    Yeehaa!
    It works! ^^
    Thank you so much
    Last edited by roobre (2012-11-24 16:18:27)

  • [Solved] tun module was loaded but not in lsmod?

    Hi Everybody,
    I loaded the tun module with "sudo modprobe tun" without any error message but didn't see it anywhere in "sudo lsmod". What might be the problems? I'm using linux-ck and wondering if linux-ck does anything here.
    The reason I want to load the tun module is that I saw this error:
    [root@ArchCustom openvpn]# openvpn --config ibVPN-LU-Luxembourg-\(P2P\).ovpn
    Thu Jan 17 08:03:20 2013 OpenVPN 2.2.2 x86_64-unknown-linux-gnu [SSL] [LZO2] [EPOLL] [eurephia] built on Aug 18 2012
    Enter Auth Username:[email protected]
    Enter Auth Password:
    Thu Jan 17 08:03:30 2013 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
    Thu Jan 17 08:03:30 2013 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
    Thu Jan 17 08:03:30 2013 NOTE: --script-security method='system' is deprecated due to the fact that passed parameters will be subject to shell expansion
    Thu Jan 17 08:03:30 2013 LZO compression initialized
    Thu Jan 17 08:03:30 2013 Control Channel MTU parms [ L:1578 D:138 EF:38 EB:0 ET:0 EL:0 ]
    Thu Jan 17 08:03:30 2013 Socket Buffers: R=[212992->131072] S=[212992->131072]
    Thu Jan 17 08:03:30 2013 Data Channel MTU parms [ L:1578 D:1450 EF:46 EB:135 ET:32 EL:0 AF:3/1 ]
    Thu Jan 17 08:03:30 2013 Fragmentation MTU parms [ L:1578 D:1300 EF:45 EB:135 ET:33 EL:0 AF:3/1 ]
    Thu Jan 17 08:03:30 2013 Local Options hash (VER=V4): '9a22532e'
    Thu Jan 17 08:03:30 2013 Expected Remote Options hash (VER=V4): 'e2a912d8'
    Thu Jan 17 08:03:30 2013 UDPv4 link local (bound): [undef]:1194
    Thu Jan 17 08:03:30 2013 UDPv4 link remote: 212.117.165.18:1194
    Thu Jan 17 08:03:30 2013 TLS: Initial packet from 212.117.165.18:1194, sid=bfe5f406 752fd5e9
    Thu Jan 17 08:03:31 2013 VERIFY OK: depth=1, /C=US/ST=CA/L=SanFrancisco/O=Fort-Funston/CN=Fort-Funston_CA/[email protected]
    Thu Jan 17 08:03:31 2013 VERIFY OK: nsCertType=SERVER
    Thu Jan 17 08:03:31 2013 VERIFY OK: depth=0, /C=US/ST=CA/L=SanFrancisco/O=Fort-Funston/CN=server/[email protected]
    Thu Jan 17 08:03:31 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Thu Jan 17 08:03:31 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Thu Jan 17 08:03:31 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
    Thu Jan 17 08:03:31 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
    Thu Jan 17 08:03:31 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
    Thu Jan 17 08:03:31 2013 [server] Peer Connection Initiated with 212.117.165.18:1194
    Thu Jan 17 08:03:33 2013 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
    Thu Jan 17 08:03:33 2013 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route 10.10.10.0 255.255.255.0 vpn_gateway,show-net-up,route-gateway 10.10.10.1,ping 2,ping-restart 120,ifconfig 10.10.10.18 255.255.255.0'
    Thu Jan 17 08:03:33 2013 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:5: show-net-up (2.2.2)
    Thu Jan 17 08:03:33 2013 OPTIONS IMPORT: timers and/or timeouts modified
    Thu Jan 17 08:03:33 2013 OPTIONS IMPORT: --ifconfig/up options modified
    Thu Jan 17 08:03:33 2013 OPTIONS IMPORT: route options modified
    Thu Jan 17 08:03:33 2013 OPTIONS IMPORT: route-related options modified
    Thu Jan 17 08:03:33 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
    Thu Jan 17 08:03:33 2013 ROUTE default_gateway=192.168.4.1
    Thu Jan 17 08:03:33 2013 Note: Cannot open TUN/TAP dev /dev/net/tun: No such device (errno=19)
    Thu Jan 17 08:03:33 2013 /usr/sbin/ip link set dev up mtu 1500
    Usage: ip link add [link DEV] [ name ] NAME
    [ txqueuelen PACKETS ]
    [ address LLADDR ]
    [ broadcast LLADDR ]
    [ mtu MTU ]
    [ numtxqueues QUEUE_COUNT ]
    [ numrxqueues QUEUE_COUNT ]
    type TYPE [ ARGS ]
    ip link delete DEV type TYPE [ ARGS ]
    ip link set { dev DEVICE | group DEVGROUP } [ { up | down } ]
    [ arp { on | off } ]
    [ dynamic { on | off } ]
    [ multicast { on | off } ]
    [ allmulticast { on | off } ]
    [ promisc { on | off } ]
    [ trailers { on | off } ]
    [ txqueuelen PACKETS ]
    [ name NEWNAME ]
    [ address LLADDR ]
    [ broadcast LLADDR ]
    [ mtu MTU ]
    [ netns PID ]
    [ netns NAME ]
    [ alias NAME ]
    [ vf NUM [ mac LLADDR ]
    [ vlan VLANID [ qos VLAN-QOS ] ]
    [ rate TXRATE ] ]
    [ spoofchk { on | off} ] ]
    [ master DEVICE ]
    [ nomaster ]
    ip link show [ DEVICE | group GROUP ]
    TYPE := { vlan | veth | vcan | dummy | ifb | macvlan | can | bridge }
    Thu Jan 17 08:03:33 2013 Linux ip link set failed: external program exited with error status: 255
    Thu Jan 17 08:03:33 2013 Exiting
    And this is the content of ibVPN-LU-Luxembourg-\(P2P\).ovpn:
    [root@ArchCustom openvpn]# cat ibVPN-LU-Luxembourg-\(P2P\).ovpn
    remote lu1.ibvpn.com 1194 udp
    remote 212.117.165.18 1194 udp
    client
    dev tap
    resolv-retry infinite
    script-security 3 system
    explicit-exit-notify 3
    persist-key
    persist-tun
    mute-replay-warnings
    ca ibvpn.com.crt
    comp-lzo
    verb 3
    mute 20
    ns-cert-type server
    fragment 1300
    route-delay 2
    auth-user-pass
    auth-nocache
    reneg-sec 0
    up "/etc/openvpn/change_resolv_conf.sh up"
    down "/etc/openvpn/change_resolv_conf.sh down"
    Regards.
    Solved: didn't know what happened, installed linux-ck 3.7.3-1-ck, rebooted and everything was fine.
    Last edited by dxxvi (2013-01-20 06:10:47)

    Trilby wrote:
    Isn't this the same issue:
    https://bbs.archlinux.org/viewtopic.php … 1#p1217611
    If so, please search the forums before creating new threads of duplicate issues.
    It looks like the same issue. Actually, I did a search for "tun" in the Networking forum (but not the newbie forum) and still couldn't find an answer.
    My /usr/src/linux-3.7.2-2-ck/.config has CONFIG_TUN=m. Then is there any other reason I cannot load the tun module?
    Thanks.

  • [SOLVED] Stopping openvpn@ service on suspend

    I'm trying to stop any running openvpn@ service either prior to suspend or immediately after resume. I've got a service file enabled:
    [Unit]
    Description=Root suspend actions
    Before=sleep.target
    [Service]
    Type=forking
    ExecStart=-/home/firecat53/.local/bin/suspend.sh
    [Install]
    WantedBy=sleep.target
    and the helper script suspend.sh:
    #!/bin/sh
    # Helper script to stop openvpn on suspend
    /usr/bin/systemctl stop $(/usr/bin/systemctl | grep openvpn@ | awk '{print $1}')
    The helper script works fine when run by itself, but it fails when run from the service file, and openvpn is still running. I've also tried it post-resume, with the same results.
    # journalctl
    Sep 18 19:56:54 scotty suspend.sh[10544]: Failed to issue method call: Invalid argument
    $ systemctl status suspend.sh
    suspend.service - Root suspend actions
    Loaded: loaded (/etc/systemd/system/suspend.service; enabled)
    Active: inactive (dead) since Wed 2013-09-18 19:56:54 PDT; 6min ago
    Process: 10544 ExecStart=/home/firecat53/.local/bin/suspend.sh (code=exited, status=1/FAILURE)
    Am I doing something wrong here, or is there another way to accomplish this?
    Thanks!
    Scott
    Last edited by firecat53 (2013-09-20 03:52:57)

    Thanks for the tip! Solved by extending [email protected] in /etc/systemd/system/[email protected]/suspend_conflict.conf
    [Unit]
    Conflicts=suspend.target sleep.target
    Now it kills the openvpn@ service on suspend and doesn't restart it automatically on resume, which is the behavior I was looking for.
    Scott

Maybe you are looking for

  • How to set the font of label in ColumnChart correctly?

    hello, everybody By flex sdk 4.1.0, 4.5.1, the same source but two effects of font of label of ColumnChart will be displayed. .mxml: <!-- mxml start --> <?xml version="1.0" encoding="utf-8"?> <s:BorderContainer xmlns:fx="http://ns.adobe.com/mxml/2009

  • Got stuck while installing BAM.

    Hi all, I am stuck at the step: DATBASE CONNECT INFORMATION, while installing the BAM. Everytime I try, its giving me error saying that the Installer cannot connect to the database located at parameter #1. Please help me in getting out of this issue.

  • Short Dump LOAD_TYPE_VERSION_MISMATCH

    Hello, We have copied the standard form in HRFORMS to a custom one and made changes, Changes only made in the ADOBE interface and layout. Its working in Development environment. Then we moved the transport to the Quality and we activated the HRFORMS

  • I have uploaded the update but the upload page doesn't close

    This morning as I was opening Firefox to get to our web site, a pop up came asking if I wanted to upgrade Firefox is 4. I clicked yes. That took me to the upload page. I clicked upload and the info says the upload is complete but the page does not cl

  • How can I fix: iPad1 plays back audio podcasts (not music) at double speed?

    How can I fix: iPad1 plays back audio podcasts (not music) at double speed?