[Problem disappeared in new kernel] Bad SSD performance

Hello all, I'm an ex-gentoo user turned arch. Looking forward to it!
Anyway, I have a brand new OCZ Vertex SSD -- theoretical 230MB/s read times. In the livecd installer, hdparm gets 210MB/s reads, pretty awesome. However, in my current installation, I am only getting 75MB/s.
My kernel is 2.6.29, the livecd has 2.6.28. I checked, UDMA/133 is enabled on my drive. I (and some generous IRC users) have absolutely no idea what's happening here.
Any help would be appreciated!
[root@wakka jake]# hdparm -i /dev/sda
/dev/sda:
Model=OCZ-VERTEX, FwRev=1370, SerialNo=92M9W154QY80YY06496G
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=12288
BuffType=unknown, BuffSize=32767kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=62533296
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-5,6,7
Last edited by wakkadojo (2009-06-17 13:40:38)

I have been all over google and many other forums, there's really nothing on this. I'm almost certain it's an Arch linux problem of some sort.
I just gave your suggestion a shot. Here's what we get:
# hdparm -t -W 0 /dev/sda
/dev/sda:
setting drive write-caching to 0 (off)
write-caching = 1 (on)
Timing buffered disk reads: 220 MB in 3.02 seconds = 72.96 MB/sec
So no improvement -- but then again it says it turns off write caching when it really does not.
However, I would like to point out that it is probably not write caching that is causing this slowdown, since on the livecd write caching is enabled, and others have not posted anything about disabling write caching to improve ssd performance.
Last edited by wakkadojo (2009-05-31 23:55:24)

Similar Messages

  • ATI display driver fails to work with new kernel

    Hi,
    I've just upgraded from
    OEL kernel-2.6.18-194.11.3.0.1.el5.x86_64
    to most current
    OEL kernel-2.6.18-194.11.4.0.1.el5.x86_64
    and got the problem with ATI display driver. Whenever I perform kernel upgrade, I have to recompile vendor-provided ATI display driver downloadable from AMD/ATI site, because system ATI driver, provided by OEL/RHEL as kernel module, doesn't work properly (too slow). I did that hundred times and never had a problem. This time the problem is that after upgrading to new kernel and recompiling the existing ATI display driver (Revision 10.8), it doesn't work anymore, even though it worked perfectly with previous kernel. I cannot even start X11 (glibc problem reported with stack traces!!!). The newest ATI display driver (Revision 10.9) "works" with new kernel, but display is awfully slow making any serious work impossible. It is even slower than system-provided ATI driver.
    I am pretty sure the problem is in new kernel. As I have no backup of old kernel files and couldn't download the previous OEL kernel files from ULN, neither binary nor source (the files do not exist on ULN anymore, only the recent kernel files), I downloaded the previous kernel source from ftp.redhat.com, compiled the kernel and downgraded to it, recompiled ATI display driver, and everything works properly and fast as before upgrading. I can remember that ULN site used to have all kernel versions prior to actual one and cannot understand why Oracle dropped this practice. As I have an ULN account, I certainly want to have OEL patched kernel.
    My question is: does anybody know how and where I can download the previous OEL kernel-2.6.18-194.11.3.0.1.el5.x86_64 binary rpm files or at least source rpm file?
    Maybe Sergio or Tommy can help?
    Thanks in advance.
    NJ

    I have experienced the same with Ubuntu some years ago - specific feature (hack?) that was implemented in the kernel was deprecated. This was used by the display driver for an onboard Intel graphics chipset. Beryl (which was subsequently merged with Compiz) turned into a horribly slow experience. As far as I recall, a subsequent kernel patch "fixed" things as a number of users were affected, of which many complained very loudly.
    Anyway, I think the lesson here is that OEL is not really the correct distro to use for a desktop. A broken ATI driver for the OEL kernel? Does not really feature in the scheme of things for OEL support. Oracle Grid/RAC/Enterprise/Standard Edition do not care. Oracle's application servers (Apache, Weblogic, etc) do not care. Etc.
    Sure, GUI desktop access to an OEL server is needed (like when running dbca or an installer) - but that can easily and effectively be done using vncserver for example and running twm.
    You may be able to fix/work-around the problem with the current kernel update.. you may be able to roll back the update. But what about the next time when some other component does not work after a patch or an update? Surely it is a lot less stressful and frustrating to rather use a desktop distro, like Ubuntu, instead?

  • Problem with firewire (since kernel-update?) [solved]

    Hi,
    since i have updated my system, i am unable to connect my dv-camcorder to my firewire-card.
    when i power on my dv-camcorder dmesg says:
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: created new fw device fw1 (0 config rom retries, S100)
    ieee1394: raw1394: /dev/raw1394 device initialized
    NOTE: The dv1394 driver is unsupported and may be removed in a future Linux rele
    ase. Use raw1394 instead.
    firewire_core: giving up on config rom for node id ffc1
    If i then disconnect and reconnect it, dmesg says the following:
    firewire_core: BM lock failed, making local node (ffc0) root.
    firewire_core: phy config: card 0, new root=ffc0, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: phy config: card 0, new root=ffc1, gap_count=5
    firewire_core: created new fw device fw1 (0 config rom retries, S100)
    I have tried a canon mv700 as well as a canon xm1, both lead to the same problem. I have tried to connect my camcorder also to my notebook which also runs the latest version of arch, but leads to the same problem too.
    I think there is a problem with the new kernel or something. Two weeks ago, before updating my system, everything works well.
    Any suggestions or ideas?
    Anyone with similar problems?
    Greets,
    smove
    Last edited by smove (2008-05-06 19:32:14)

    I solved this problem. Since kernel 2.6.22 there is a new firewire-stack available called 'juju'. Because of it´s experimental state it is not recommend to use it. In the current kernel-package the old and the new firewire-modules are included but the new instable ones are used by default. To fix the problem you have to blacklist the new firewire-modules.
    Create the following file:
    /etc/modprobe.d/newfw_blacklist:
    blacklist firewire-ohci
    blacklist firewire-sbp2
    Reboot your system and try to use your firewire again. Look if the old modules are loaded instead of the new firewire-* ones. I dont understand why the new firewire-modules are used by default in the new kernel-packages. Refering to http://wiki.linux1394.org/JujuMigration … 857ee71b93 it is not recommended to use the new modules yet.

  • New sys-install: once bad ogl performance, other times good

    hello!
    i have a strange problem. after a new system-install sometimes i got a good opengl-performance, some other installs got a bad performance. i had installed the system exactly like the one before. dri is enabled etc. tuxracer has a very bad performance - no matter wether resolution - 640 or 1024 - still 0-1 fps!
    has someone a idea, how to solve this?
    system: centrino, chipset/graphics i855gm - kernel modul: i915; xorg-modul: i810
    xorg - 6.8.2-2
    kernel26 2.6.12.2-1
    thx for help

    hello!
    i have a strange problem. after a new system-install sometimes i got a good opengl-performance, some other installs got a bad performance. i had installed the system exactly like the one before. dri is enabled etc. tuxracer has a very bad performance - no matter wether resolution - 640 or 1024 - still 0-1 fps!
    has someone a idea, how to solve this?
    system: centrino, chipset/graphics i855gm - kernel modul: i915; xorg-modul: i810
    xorg - 6.8.2-2
    kernel26 2.6.12.2-1
    thx for help

  • Problem with this new version is when i open firefox something change my home page to mozila defalut page and in the new tab open mozila firefox first run page.Sorry for my bad English

    Problem with this new version is when i open firefox something change my home page to mozila defalut page and in the new tab open mozila firefox first run page.Sorry for my bad English

    Sounds like this issue:
    * http://kb.mozillazine.org/Preferences_not_saved
    * [[Preferences are not saved]]

  • OEL 6.2 new kernel new problems

    Hi dears,
    I was very happy about new updates and of course I installed these new update hoping that some
    problems related to incompatibility in my system will be solved, but after I reboot my machine
    I saw this
    http://picfront.de/d/8s0p
    How can I fix this or although rollback to old kernel ?
    Please help.
    old kernel = 2.6.32.100
    new kernel = 2.6.32.300
    OS OEL 6 (PVM) in Oracle VM 3.0.2
    ./thanks in advance

    Avi Miller wrote:
    __OUTSIDER___ wrote:
    How can I fix this or although rollback to old kernel ?The old kernel is still installed -- the upgrade just installs a new one as well. What's happened is that your root device line seems to have changed, though I'm unsure why. There appears to be a /dev/ missing from the root= parameter on the command-line.
    Log into the Dom0 of your Oracle VM Server and start the guest manually and connect to the console using:
    # xm create -c /OVS/Repositories/<UUID>/VirtualMachines/<UUID>/vm.cfg You'll need to work out what the two <UUID> values are, though. The first one is the UUID of the repository that contains your Virtual Machine configuration file. The second is the UUID of the Virtual Machine itself. You can find the repository path by running df -h to see all the mounted repositories on your server. The VirtualMachine UUID is on the Info screen of the Virtual Machine under the "ID" field.
    When you start the guest using the xm command, you'll be presented with the GRUB boot loader screen, which will allow you to chose the previous kernel. When the machine boots, check /boot/grub/grub.conf and ensure that the root= parameter is the same as the previous kernel lines.Thanks Avi for speed of light support (I'm surprised :) )
    Everything as you say I was able to run my old kernel and ssh to machine but root= parameter is fine (I think).
    Can you check please if I am wrong
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title Oracle Linux Server (2.6.32-300.3.1.el6uek.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-300.3.1.el6uek.x86_64 ro root=/dev/mapper/vg_rac1-lv_root rd_LVM_LV=vg_rac1/lv_root rd_LVM_LV=vg_rac1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us
    title Oracle Linux Server (2.6.32-220.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-220.el6.x86_64 ro root=/dev/mapper/vg_rac1-lv_root rd_LVM_LV=vg_rac1/lv_root rd_LVM_LV=vg_rac1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us
    title Oracle Linux Server-uek (2.6.32-100.34.1.el6uek.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-100.34.1.el6uek.x86_64 ro root=/dev/mapper/vg_rac1-lv_root rd_LVM_LV=vg_rac1/lv_root rd_LVM_LV=vg_rac1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us
    initrd /initramfs-2.6.32-100.34.1.el6uek.x86_64.img
    title Oracle Linux Server (2.6.32-131.0.15.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-131.0.15.el6.x86_64 ro root=/dev/mapper/vg_rac1-lv_root rd_LVM_LV=vg_rac1/lv_root rd_LVM_LV=vg_rac1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto rhgb quiet
    initrd /initramfs-2.6.32-131.0.15.el6.x86_64.img

  • New kernel and problems installing nvidia-legacy drivers

    I just compiled new kernel, and I can't install nvidia-legacy drivers properly. Pacman installs them, but the module (nvidia.ko) goes to /lib/modules/2.6.19-ARCH, and I want it to 2.6.19.2.. It doesn't work if I just copy the module..
    I've compiled kernel many times without problems when I was still using Slackware.  So, what do I need to configure to use the new module directory? I Propably made some small/stupid mistake..
    I tried legacy drivers from nvidia.com, but they didnt compile.. weird, gonna try that again too..

    You need to install the nvidia drivers, or any other non-kernel drivers, specifically for the kernel you are using. Arch packages the nvidia drivers to work with the Arch kernel packages, and the "Arch way" to deal with your situation is to modify the appropriate PKGBUILD to match your kernel, create a custom package with makepkg, and install it with pacman.
    You can also use the nvidia installer, but in that case the nvidia files installed on your system will not be under pacman's control.

  • Does Linux do anything About SSD Performance Degradation?

    I have been thinking about getting an SSD for my laptop but just read this article on performance degradation of SSDs: http://www.anandtech.com/show/2738/8
    I typically use ext4. Does anyone know if any of the Linux filesystems/kernels/etc do anything about SSD performance degradation? Has anyone found a solution to this problem? Maybe new SSDs don't have the issue?

    My OCZ Vertex 2 SSDs slowed down just a tiny bit soon after installing them, but TRIM seems to be working well and they don't seem to be slowing down any further. I'm running them on ext4 with journaling enabled, and only the log files are being directed to temp files.  Everything else is going to the SSDs, and they are being used just like regular hard drives.

  • [SOLVED]problem with Bumblebee and Kernel 3.11-1-2

    Hi!
    I'm having problems with Bumblebee from Kernel 3.10 but I read that Kernel 3.11 solved the problem, I searched and tried possible solutions to my problem unsuccessfully
    The message shows me when I run "optirun":
    [ 5454.262739] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) No devices detected.
    [ 5454.262776] [ERROR]Aborting because fallback start is disabled.
    I've tried with wiki's solutions, forums solutions...
    Configurations files:
    /etc/bumblebee/bumblebee.conf:
    # Configuration file for Bumblebee. Values should **not** be put between quotes
    ## Server options. Any change made in this section will need a server restart
    # to take effect.
    [bumblebeed]
    # The secondary Xorg server DISPLAY number
    VirtualDisplay=:8
    # Should the unused Xorg server be kept running? Set this to true if waiting
    # for X to be ready is too long and don't need power management at all.
    KeepUnusedXServer=false
    # The name of the Bumbleblee server group name (GID name)
    ServerGroup=bumblebee
    # Card power state at exit. Set to false if the card shoud be ON when Bumblebee
    # server exits.
    TurnCardOffAtExit=false
    # The default behavior of '-f' option on optirun. If set to "true", '-f' will
    # be ignored.
    NoEcoModeOverride=false
    # The Driver used by Bumblebee server. If this value is not set (or empty),
    # auto-detection is performed. The available drivers are nvidia and nouveau
    # (See also the driver-specific sections below)
    Driver=
    # Directory with a dummy config file to pass as a -configdir to secondary X
    XorgConfDir=/etc/bumblebee/xorg.conf.d
    ## Client options. Will take effect on the next optirun executed.
    [optirun]
    # Acceleration/ rendering bridge, possible values are auto, virtualgl and
    # primus.
    Bridge=virtualgl
    # The method used for VirtualGL to transport frames between X servers.
    # Possible values are proxy, jpeg, rgb, xv and yuv.
    VGLTransport=proxy
    # List of paths which are searched for the primus libGL.so.1 when using
    # the primus bridge
    PrimusLibraryPath=/usr/lib/primus:/usr/lib32/primus
    # Should the program run under optirun even if Bumblebee server or nvidia card
    # is not available?
    AllowFallbackToIGC=false
    # Driver-specific settings are grouped under [driver-NAME]. The sections are
    # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
    # detection resolves to NAME).
    # PMMethod: method to use for saving power by disabling the nvidia card, valid
    # values are: auto - automatically detect which PM method to use
    # bbswitch - new in BB 3, recommended if available
    # switcheroo - vga_switcheroo method, use at your own risk
    # none - disable PM completely
    # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
    ## Section with nvidia driver specific options, only parsed if Driver=nvidia
    [driver-nvidia]
    # Module name to load, defaults to Driver if empty or unset
    KernelDriver=nvidia
    PMMethod=auto
    # colon-separated path to the nvidia libraries
    LibraryPath=/usr/lib/nvidia:/usr/lib32/nvidia
    # comma-separated path of the directory containing nvidia_drv.so and the
    # default Xorg modules path
    XorgModulePath=/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules
    XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
    ## Section with nouveau driver specific options, only parsed if Driver=nouveau
    [driver-nouveau]
    KernelDriver=nouveau
    PMMethod=auto
    XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
    /etc/bumblebee/xorg.conf.nvidia
    Section "ServerLayout"
    Identifier "Layout0"
    Option "AutoAddDevices" "false"
    Option "AutoAddGPU" "false"
    EndSection
    Section "Device"
    Identifier "DiscreteNvidia"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    # If the X server does not automatically detect your VGA device,
    # you can manually set it here.
    # To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
    # as you see in the commented example.
    # This Setting may be needed in some platforms with more than one
    # nvidia card, which may confuse the proprietary driver (e.g.,
    # trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
    BusID "PCI:01:00.0"
    # Setting ProbeAllGpus to false prevents the new proprietary driver
    # instance spawned to try to control the integrated graphics card,
    # which is already being managed outside bumblebee.
    # This option doesn't hurt and it is required on platforms running
    # more than one nvidia graphics card with the proprietary driver.
    # (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
    # If this option is not set, the new Xorg may blacken the screen and
    # render it unusable (unless you have some way to run killall Xorg).
    Option "ProbeAllGpus" "false"
    Option "NoLogo" "true"
    Option "UseEDID" "false"
    Option "UseDisplayDevice" "none"
    EndSection
    lspci |grep NVIDIA:
    01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 640M] (rev a1)
    I hope can help me
    Thanks!
    Last edited by surrealistic (2013-11-04 18:46:35)

    My /var/log/Xorg.8.log:
    [ 337.161]
    X.Org X Server 1.14.4
    Release Date: 2013-10-31
    [ 337.161] X Protocol Version 11, Revision 0
    [ 337.161] Build Operating System: Linux 3.11.6-1-ARCH x86_64
    [ 337.161] Current Operating System: Linux h131h-laptop 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64
    [ 337.161] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=4eb69984-2228-4aba-9863-28a7fa854e51 rw quiet
    [ 337.161] Build Date: 01 November 2013 05:10:48PM
    [ 337.161]
    [ 337.161] Current version of pixman: 0.30.2
    [ 337.161] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 337.161] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 337.161] (==) Log file: "/var/log/Xorg.8.log", Time: Mon Nov 4 14:20:04 2013
    [ 337.161] (++) Using config file: "/etc/bumblebee/xorg.conf.nvidia"
    [ 337.161] (++) Using config directory: "/etc/bumblebee/xorg.conf.d"
    [ 337.161] (==) ServerLayout "Layout0"
    [ 337.161] (==) No screen section available. Using defaults.
    [ 337.161] (**) |-->Screen "Default Screen Section" (0)
    [ 337.161] (**) | |-->Monitor "<default monitor>"
    [ 337.161] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 337.161] (**) | |-->Device "DiscreteNvidia"
    [ 337.161] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 337.161] (**) Option "AutoAddDevices" "false"
    [ 337.161] (**) Option "AutoAddGPU" "false"
    [ 337.161] (**) Not automatically adding devices
    [ 337.161] (==) Automatically enabling devices
    [ 337.161] (**) Not automatically adding GPU devices
    [ 337.161] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 337.162] Entry deleted from font path.
    [ 337.162] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 337.162] Entry deleted from font path.
    [ 337.162] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 337.162] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 337.162] Entry deleted from font path.
    [ 337.162] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 337.162] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 337.162] (++) ModulePath set to "/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules"
    [ 337.162] (==) |-->Input Device "<default pointer>"
    [ 337.162] (==) |-->Input Device "<default keyboard>"
    [ 337.162] (==) The core pointer device wasn't specified explicitly in the layout.
    Using the default mouse configuration.
    [ 337.162] (==) The core keyboard device wasn't specified explicitly in the layout.
    Using the default keyboard configuration.
    [ 337.162] (II) Loader magic: 0x7fdc20
    [ 337.162] (II) Module ABI versions:
    [ 337.162] X.Org ANSI C Emulation: 0.4
    [ 337.162] X.Org Video Driver: 14.1
    [ 337.162] X.Org XInput driver : 19.1
    [ 337.162] X.Org Server Extension : 7.0
    [ 337.162] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 337.162] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 337.162] setversion 1.4 failed
    [ 337.163] (--) PCI:*(0:1:0:0) 10de:0fd2:1025:0648 rev 161, Mem @ 0xb2000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x00002000/128
    [ 337.163] Initializing built-in extension Generic Event Extension
    [ 337.163] Initializing built-in extension SHAPE
    [ 337.163] Initializing built-in extension MIT-SHM
    [ 337.163] Initializing built-in extension XInputExtension
    [ 337.163] Initializing built-in extension XTEST
    [ 337.163] Initializing built-in extension BIG-REQUESTS
    [ 337.163] Initializing built-in extension SYNC
    [ 337.163] Initializing built-in extension XKEYBOARD
    [ 337.163] Initializing built-in extension XC-MISC
    [ 337.163] Initializing built-in extension SECURITY
    [ 337.163] Initializing built-in extension XINERAMA
    [ 337.163] Initializing built-in extension XFIXES
    [ 337.163] Initializing built-in extension RENDER
    [ 337.163] Initializing built-in extension RANDR
    [ 337.164] Initializing built-in extension COMPOSITE
    [ 337.164] Initializing built-in extension DAMAGE
    [ 337.164] Initializing built-in extension MIT-SCREEN-SAVER
    [ 337.164] Initializing built-in extension DOUBLE-BUFFER
    [ 337.164] Initializing built-in extension RECORD
    [ 337.164] Initializing built-in extension DPMS
    [ 337.164] Initializing built-in extension X-Resource
    [ 337.164] Initializing built-in extension XVideo
    [ 337.164] Initializing built-in extension XVideo-MotionCompensation
    [ 337.164] Initializing built-in extension XFree86-VidModeExtension
    [ 337.164] Initializing built-in extension XFree86-DGA
    [ 337.164] Initializing built-in extension XFree86-DRI
    [ 337.164] Initializing built-in extension DRI2
    [ 337.164] (II) LoadModule: "glx"
    [ 337.164] (II) Loading /usr/lib/nvidia/xorg/modules/extensions/libglx.so
    [ 337.172] (II) Module glx: vendor="NVIDIA Corporation"
    [ 337.172] compiled for 4.0.2, module version = 1.0.0
    [ 337.172] Module class: X.Org Server Extension
    [ 337.172] (II) NVIDIA GLX Module 325.15 Wed Jul 31 18:12:00 PDT 2013
    [ 337.172] Loading extension GLX
    [ 337.172] (II) LoadModule: "nvidia"
    [ 337.172] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 337.172] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 337.172] compiled for 4.0.2, module version = 1.0.0
    [ 337.172] Module class: X.Org Video Driver
    [ 337.172] (II) LoadModule: "mouse"
    [ 337.172] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
    [ 337.172] (II) Module mouse: vendor="X.Org Foundation"
    [ 337.172] compiled for 1.14.0, module version = 1.9.0
    [ 337.172] Module class: X.Org XInput Driver
    [ 337.172] ABI class: X.Org XInput driver, version 19.1
    [ 337.172] (II) LoadModule: "kbd"
    [ 337.173] (WW) Warning, couldn't open module kbd
    [ 337.173] (II) UnloadModule: "kbd"
    [ 337.173] (II) Unloading kbd
    [ 337.173] (EE) Failed to load module "kbd" (module does not exist, 0)
    [ 337.173] (II) NVIDIA dlloader X Driver 325.15 Wed Jul 31 17:50:57 PDT 2013
    [ 337.173] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 337.173] (--) using VT number 1
    [ 337.173] (II) Loading sub module "fb"
    [ 337.173] (II) LoadModule: "fb"
    [ 337.173] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 337.173] (II) Module fb: vendor="X.Org Foundation"
    [ 337.173] compiled for 1.14.4, module version = 1.0.0
    [ 337.173] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 337.173] (WW) Unresolved symbol: fbGetGCPrivateKey
    [ 337.173] (II) Loading sub module "wfb"
    [ 337.173] (II) LoadModule: "wfb"
    [ 337.173] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 337.173] (II) Module wfb: vendor="X.Org Foundation"
    [ 337.173] compiled for 1.14.4, module version = 1.0.0
    [ 337.173] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 337.173] (II) Loading sub module "shadow"
    [ 337.173] (II) LoadModule: "shadow"
    [ 337.173] (II) Loading /usr/lib/xorg/modules/libshadow.so
    [ 337.173] (II) Module shadow: vendor="X.Org Foundation"
    [ 337.173] compiled for 1.14.4, module version = 1.1.0
    [ 337.173] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 337.173] (II) Loading sub module "ramdac"
    [ 337.173] (II) LoadModule: "ramdac"
    [ 337.173] (II) Module "ramdac" already built-in
    [ 337.174] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 337.174] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 337.174] (==) NVIDIA(0): RGB weight 888
    [ 337.174] (==) NVIDIA(0): Default visual is TrueColor
    [ 337.174] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 337.174] (**) NVIDIA(0): Option "NoLogo" "true"
    [ 337.174] (**) NVIDIA(0): Option "ProbeAllGpus" "false"
    [ 337.174] (**) NVIDIA(0): Option "UseEDID" "false"
    [ 337.174] (**) NVIDIA(0): Option "UseDisplayDevice" "none"
    [ 337.174] (**) NVIDIA(0): Enabling 2D acceleration
    [ 337.174] (**) NVIDIA(0): Ignoring EDIDs
    [ 337.174] (**) NVIDIA(0): Option "UseDisplayDevice" set to "none"; enabling NoScanout
    [ 337.174] (**) NVIDIA(0): mode
    [ 341.309] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    [ 341.309] (EE) NVIDIA(0): check your system's kernel log for additional error
    [ 341.309] (EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
    [ 341.309] (EE) NVIDIA(0): README for additional information.
    [ 341.309] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
    [ 341.309] (EE) NVIDIA(0): Failing initialization of X screen 0
    [ 341.309] (II) UnloadModule: "nvidia"
    [ 341.309] (II) UnloadSubModule: "shadow"
    [ 341.309] (II) UnloadSubModule: "wfb"
    [ 341.309] (II) UnloadSubModule: "fb"
    [ 341.309] (EE) Screen(s) found, but none have a usable configuration.
    [ 341.309] (EE)
    Fatal server error:
    [ 341.309] (EE) no screens found(EE)
    [ 341.309] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 341.309] (EE) Please also check the log file at "/var/log/Xorg.8.log" for additional information.
    [ 341.309] (EE)
    [ 341.309] (EE) Server terminated with error (1). Closing log file.
    dmesg |grep bbswitch:
    [ 13.570577] bbswitch: version 0.7
    [ 13.570585] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
    [ 13.570591] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
    [ 13.570687] bbswitch: detected an Optimus _DSM function
    [ 13.570741] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
    [ 13.572354] bbswitch: disabling discrete graphics
    [ 261.419114] bbswitch: enabling discrete graphics
    [ 278.445698] bbswitch: disabling discrete graphics
    [ 279.055257] bbswitch: enabling discrete graphics
    [ 286.292315] bbswitch: disabling discrete graphics
    [ 291.911052] bbswitch: enabling discrete graphics
    [ 310.011289] bbswitch: disabling discrete graphics
    [ 336.982794] bbswitch: enabling discrete graphics
    [ 349.526470] bbswitch: enabling discrete graphics
    I used "rcutree" option as shown in the post that you put, but I've deleted all changes made to use default configurations, because the solution of the post didn't work

  • Downloaded Mt Lion.  Now my facetime launches then quits with message that there is a problem with the  C_L Kernel Plugin.  Everything else works just fine. I can get on line etc.

    I have have an early 2008  imac 8,1  It has been a good machine no problems.  UNTIL we downloaded Mt Lion. We can no longer use facetime.  We click on the icon it comes up, tries to connect then it disappears with the message that there was a problem with the C_L Kernel Plugin.  We can go on line without difficulty, everything else seems to be working.  Searching the internet shows that others have had the same problem with Mt Lion. But so far I haven't found a solution.  We have wiped the drive reloaded snow leopard then downloaded Mt Lion again. We put in a NEW hard drive and reloaded snow leopard then Mt Lion. We have changed out ram using apple ram. But we still get the same result. Everything works except for Facetime.  Is there some patch we have missed?  Facetime DOES work on our ipads without a hitch so I doubt it's the internet connection.  We've tried the imac both wirelessly as the ipads run and hardwired and get no where fast.  So any help at all would be appreciated.  We live in the boonies, the nearest mac repair is over 150 miles away so this is pretty nuch a do it myself affair.  We know the machine is old by most standards today. But we pretty much run our machines until they can't power up.  So we'd like to get this one back on its perch so to speak with its face time working.
    Thank you ahead of time for any advise help given.

    A log may help determine what the issue is ...
    Open the Console app located in HD > Applications > Utilites
    Select: System Diagnostic Reports  on the left.
    Copy and paste the most recent kernel panic or crash log in your Reply.

  • NEW KERNEL V47, and a new hope for 720p video play...

    thats right people, after matan's strange disappearing, we now have pali getting us new kernels, and his first kernel with loads of new awesome patches is in the extras devels ( v47 ) , you can try it out, same installation method as the old v46  (or v42 from the extras ), and same overclocking method too .
    and now he is working on a 720p video playback patch, he already got the 720p media codecs (finally) and many users reported that they are able to play 720p mpeg4 videos on the n900 (this patch isn't in the extras devel version....yet ! ) so now we don't have a hardware problem to play 720p videos, the problem is in gstreamer (video player in the default media player) but thank god, we have MohamadAG to work on that openmedia player so we can finally get 720p video playback .
    and if we can play 720p videos, we can shoot them too .
    and i can say that after 40 minutes of hard usage of this new kernel my phone seems a lot smoother and abit faster than the old v46 or v42 with the same overclocking settings .
    Use Hildon Application Manager or via apt-get
    Step 1 Installation:
    In Hildon Application Manager install package: Linux Kernel for power user
    Or via apt-get package: kernel-power-flasher
    Step 2 Multiboot support:
    First see step 1.
    Then in Hildon Application Manager install package: Linux Kernel for power user (boot image)
    Or via apt-get package: kernel-power-bootimg
    this is not for noobs right now, but it will be soon, and it might become a part of the cssu .
    and btw if you get a 400 degrees temprature in conky don't panic, its a false value, its 40
    ORIGINAL THREAD BY PALI AT talk.maemo.org .
    Reality is wrong....dreams are for real... 2pac .
    don't forget to hit that green kudos

    ceroberts75 wrote:
    i am boping we get another community udate soon. the last one brought us a great camera update, but the email is still messed up.
    it will be coming...... its just tat Mag is busy with the new facebook app...... and so far i know that it includes multiple proflies support... and the camera ui has been updated 2-3 times since the last cssu update .
    and for 720 p playback we are porbably going to use open medi pllayer, for anyone that wants to use it, search this forum for "open media player" , its a faster version of the original one, with more effects and smoothness .
    Reality is wrong....dreams are for real... 2pac .
    don't forget to hit that green kudos

  • Bad INSERT performance when using GUIDs for indexes

    Hi,
    we use Ora 9.2.0.6 db on Win XP Pro. The application (DOT.NET v1.1) is using ODP.NET. All PKs of the tables are GUIDs represented in Oracle as RAW(16) columns.
    When testing with mass data we see more and more a problem with bad INSERT performance on some tables that contain many rows (~10M). Those tables have an RAW(16) PK and an additional non-unique index which is also set on a RAW(16) column (both are standard B*tree). An PerfStat reports tells that there is much activity on the Index tablespace.
    When I analyze the related table and its indexes I see a very very high clustering factor.
    Is there a way how to improve the insert performance in that case? Use another type of index? Generally avoid indexed RAW columns?
    Please help.
    Daniel

    Hi
    After my last tests I conclude at the followings:
    The query returns 1-30 records
    Test 1: Using Form Builder
    -     Execution time 7-8 seconds
    Test 2: Using Jdeveloper/Toplink/EJB 3.0/ADF and Oracle AS 10.1.3.0
    -     Execution time 25-27 seconds
    Test 3: Using JDBC/ADF and Oracle AS 10.1.3.0
    - Execution time 17-18 seconds
    When I use:
    session.setLogLevel(SessionLog.FINE) and
    session.setProfiler(new PerformanceProfiler())
    I don’t see any improvement in the execution time of the query.
    Thank you
    Thanos

  • Bad query performance - how to analyze it?

    Hi all,
    since 8 weeks we locate a bad query performance (round about 30% worse than before) in our BW system. At the moment we use a BIA on revision 49 with 4 blades (16GB).
    I have already read note 1318214 and analyzed that the most time is spend on the virtual provider(over 80%!).
    I´ve seen that a lot of time is spend on the "Datamanager":
    For example: It takes 0,76s to select 3.5million items in the relative provider and 78s!!! to select 0 items in the virtual provider.
    information from RSDDSTATTREXSERV:
    RFC Server    BIA client  BIA Kernel    ABAP RFC
    497          464              450               619
    So it seems to be a problem an the BW site, what can we do to improve the performance or analyse the query performance better.
    Best Regards,
    Jens

    Hi Jens,
    A few checks you may consider doing.
    BIA Availability :  Check the BI connection with BIA.
    Check if you need to rebuild BIA indices again. SAP recommends to do this often, to repair the degenerate indices or delete the indice which are not referenced any more.(eg data in the cube was compressed/deleted and the indices are no more needed.)
    Check the if BIA  reorganization is required - This is done to see the indices are evenly distribueded areoss the BIA Landscape.
    Try to find from BI Admin if major administration work was done within these 8 weeks.eg: Copy cube, dimension restructureing, copying data to some copy cube, archiving etc.
    You can use the BIA monitor to peform checks/monitor alerts from BIA servers
    [ BIA monitor|http://help.sap.com/saphelp_nw70/helpdata/en/43/7719d270d81a6ee10000000a11466f/content.htm]
    This link would tell you on the overall status of the BIA and any actions if required.
    Also it has sublinks to other important transaction of BIA monitoring and maintainnance.
    To go to BIA monitor : RSA!---> BIA monitor icon.
    Is your virtual provider reading data from R/3 or BW.
    Generally virtual providers are used to read data from other systems , so it woulfd not have an indices in BIA, I believe if this is the case. except for some applications like BCS wher eyou may be reading data from BW itself.
    Hope this helps
    Bext regards,
    Sunmit.

  • Re-install OSX - good or bad for performance?

    Did a re-install on my brand new MacBook because a got some problem during start up (solved it with Safe boot, thanks Ned Snowing) so my question is - was it a bad idea to re-install the system when there was no use for it? Can it slow down performance on a new MacBook?

    The performance should be exactely the same!
    Sometimes your Macbook will perform a little better after a clean install off OSX.
    If you have used your Mac then all the software installations can cause it to begin performing slower. At least here my Mac performs always a little better after a clean install.
    You can re-install OSX just as much you like. This will not damage your system or something like that.
    Hopefully this is helpfull or solved your problem. (see button's above this message)

  • [solved]Update from kernel 3.3.6 to a newer kernel leads to module fai

    Hello community,
    Back in may 2012 I observed a strange problem: The update from kernel 3.3.6 to kernel 3.3.7 resulted in all modules failing to load. So: No keyboard, no mouse, no network, no graphics, no CPU scaling, maybe no other things that I'm not aware of. So till today I'm forced to use kernel 3.3.6 in order to be able to use the system. The problem persists even after the upgrade of kmod and glibc. But this can't last forever since the old kernel already starts to make some problems e.g. with the new modules path structure after the glibc update. So I wonder how I can diagnose the problem. Some remarks that might be helpful: It's not hardware related because I'm running an old installation which works perfectly. The only differences that I'm aware of between the installations are: 32Bit(working) - 64bit(not working); installed on: HDD (working) - SSD (not working); no external /boot (working) - external /boot (not working); GRUB installed: on the same drive as / (working) - on a different drive as / (not working). Of course some config files might also be different but at least the /etc/rc.conf are very similar (the MODULES and DAEMONS arrays are identical). But the problem is that not only the modules from the MODULES array cannot be loaded but also many other modules.
    Thanks for any hints,
    PhotonX
    Solution: https://bbs.archlinux.org/viewtopic.php … 9#p1134889
    Last edited by PhotonX (2012-07-23 09:36:33)

    mikep wrote:
    Just to confirm that I also have this problem with nfsroot (nfs4 this time) with 3.6.2. Downgrading the kernel does make it go away.
    When it is working normally I do seem to get refused unmount messages at shutdown for some reason
    refused unmount request from 192.168.1.86 for / (/): not exported
    , but the /new_root bit is new and I have no idea where it comes from.
    refused unmount request from 192.168.1.86 for /new_root (/): not exported
    So I wonder if it asking for the wrong path.
    That unmount issue will be solved by FS#32021.
    Unfortunately, that doesn't help with mounting in the first place with 3.6.2

Maybe you are looking for