TRIM Support for AMD sb850

Hi all,
I've just bought an OCZ Octane 128GB SSD, formatted nad created an ext4 partition to host my root filesystem.
When I try to enable TRIM support for root filesystem (putting the discard in mount options) I get the following errors in dmesg
failed command: DATA SET MANAGEMENT
I've a Gigabyte GA-870A-UDE rev2 motherboard, the SSD is attached to one of the sata3 ports (managed by the SB850 Southbridge)
Any Ideas?
Thanks
Luca

Technically, TRIM is not supported by Lion for non-Apple-branded SSDs, but there is a work around for this.
The procedure described here worked beautifully for me: http://digitaldj.net/2011/07/21/trim-enabler-for-lion/

Similar Messages

  • Does arch support for amd 780g matherboard?

    does arch support for amd 780g matherboard?
    3 days ago, I installed the arch 2007.08.02, and I update the system up to date. I installed the xorg, ati driver, gdm, and gnome, but my 22" SAMSUNG LCD displayed error (display the desktop but the colors all wrong, can't see anything clearly), then I downloaded the ati catalyst install package ,  and installed it, the error occured too, so I came here to ask you
    how to deal with it?
    the video card of the matherboard  is radeon hd3200.
    Last edited by xmfs (2008-04-24 03:26:47)

    Sorry for taking this long to reply, I was out of town.
    I finally got it working with the latest catalyst. Video and everything. I am posting my xorg in case anyone finds it helpfull. I haven't done any tweaks and it is far from complete but it is working as base project.
    Section "ServerLayout"
            Identifier     "X.org Configured"
            Screen      0  "aticonfig-Screen[0]" 0 0
            InputDevice    "Mouse0" "CorePointer"
            InputDevice    "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
            RgbPath      "/usr/share/X11/rgb"
            ModulePath   "/usr/lib/xorg/modules"
            FontPath     "/usr/share/fonts/misc"
            FontPath     "/usr/share/fonts/100dpi:unscaled"
            FontPath     "/usr/share/fonts/75dpi:unscaled"
            FontPath     "/usr/share/fonts/TTF"
            FontPath     "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
            Load  "GLcore"
            Load  "xtrap"
            Load  "glx"
            Load  "dbe"
            Load  "extmod"
            Load  "record"
            Load  "dri"
            Load  "freetype"
    EndSection
    Section "InputDevice"
            Identifier  "Keyboard0"
            Driver      "kbd"
    EndSection
    Section "InputDevice"
            Identifier  "Mouse0"
            Driver      "mouse"
            Option      "Protocol" "auto"
            Option      "Device" "/dev/input/mouse1"
            Option      "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
            Identifier   "aticonfig-Monitor[0]"
            Option      "VendorName" "ATI Proprietary Driver"
            Option      "ModelName" "Generic Autodetecting Monitor"
            Option      "DPMS" "true"
            DisplaySize 518 324
    EndSection
    Section "Device"
            Identifier  "aticonfig-Device[0]"
            Driver      "fglrx"
    EndSection
    Section "Screen"
            Identifier "aticonfig-Screen[0]"
            Device     "aticonfig-Device[0]"
            Monitor    "aticonfig-Monitor[0]"
            DefaultDepth     24
            SubSection "Display"
                    Viewport   0 0
                    Depth     24
                    Modes "1920x1200"
            EndSubSection
    EndSection
    Section "DRI"
            Mode         0666
    EndSection

  • Trim support for SSD on Marvel controller?

    I read somewhere that the 6Gbs Marvell 9128 ports do not support trim on an SSD.  Is this true?  I also heard that the RAID support for the Intel P67 ports are much more better than the Marvel Ports.  This is what I am trying to do, and am wondering if it will work.  I have an MSI P67A-GD65.  I want to run Two WD Caviar Black 6Gbs (even though I know they achieve nowhere near that rate) on Sata ports 1 and 2 (the Intel P67 controller ports), in ports 3,4,5,6 (the Intel P67 3 Gbs ports) I would have 2 1TB storage drives, A Bluray drive, A DVD drive, and in the last ports 7 or 8 (the Marvell 9128) controller 6Gbs port) I wanted to have a Crucial C300 128Gb SSD drive as the boot drive.  Would this work, or should I use port 7 and 8 for my RAID setup instead and use port 1 or 2 for the SSD?  Any thoughts are appreciated.  I love this mainboard and can't wait to get it up and running.
    My System:
    MSI P67A-GD65 (B3),  Intel 2600k processor,  XFX Radeon 6950 1GB graphics card,  8 GB G.Skill Ram, 1 Crucial C300 SSD (boot drive), 2 640GB WD Caviar Black in RAID 0,  1 Blu Ray Drive, 1 DVD drive,  Corsair HX850w PS

    Quote
    I read somewhere that the 6Gbs Marvell 9128 ports do not support trim on an SSD.
    Not true. TRIM has nothing to do with the SATA controller, it is dependent on the drive itself, and your operating system.
    See: http://en.wikipedia.org/wiki/TRIM

  • Trim Support for SSD's

    Is Trim Support required for Intel 320 series SSD's?

    We haven't got it installed, so you have to wait to the release

  • TRIM support for SSD in OS X Lion

    Greetings All,
    Have read up on this and apparently not Apple SSDs aren't getting TRIM support. Does anyone have any solid info on this? Also, is there a completely dependable way of switching on TRIM support?
    Any help would be greatly appreciated :-)
    Cheers,
    Edmond
    PS - it's for an OCZ Vertex 3 240Gb Max IOPS drive.

    you welcome )
    But Edmond, trim can NOT cause issues - it just will give you no benefits and slow down SSD, if it is based on SF 2xxx controller. I detailed this here: https://discussions.apple.com/message/15649687#15649687 and even more details in discussion here: https://discussions.apple.com/thread/3194668?start=0&tstart=0

  • TRIM support for Snow Leopard!

    All of you Mac Pro/SSD owners might want to give this thread a look-see!
    http://forums.macrumors.com/showthread.php?t=1125400
    Very neat. Nice simple GUI to enable TRIM on TRIM-supporting SSDs under Snow Leopard.

    As for using hacked ktext, there can be trouble booting which you should know about first.
    As a reminder, TRIM will keep the writing performances of you SSD high. without it, the writing performances decrease rapidly, most notably for the data transfer rate.
    [Update] Some members had problem when rebooting the system.
    How to activate TRIM on any SSD
    +(this seems like it has a lot more in the way of tips and background)+
    Background GC Sand Force based unit with firmware 2.0 (which is what Corsair has shipped with since early December but is ONLY NOW coming to OWC brand)
    http://macperformanceguide.com/blog/2011/20110321_1-OWCSSDHibernate--news.html

  • Trim Support for Lion

    I have a Trim supported SSD and had trim working with Snow Leoprad but with the Lion update system support report says unsupported. Ideas?

    re-run trim enabler

  • TRIM Support For SSD

    How does Arch Linux handle SSD's? Does Arch Linux or the 3.0 kernel natively support TRIM or some equivalent garbage collection mechanism? Is TRIM or whatever it uses enabled by default during an installation of Arch Linux or must I enable this in some way? Just  trying to understand if making the switch to SSD versus traditional spindle drives is smart using Arch Linux.

    Have you read https://wiki.archlinux.org/index.php/SSD ?
    There's e.g.
    DISCARD/TRIM feature is NOT SUPPORTED by device-mapper (but they are working on it, see here. August 2011 news: support will be in Linux 3.1, and involves a userspace dm-crypt update as well
    https://wiki.archlinux.org/index.php/SSD#Mount_Flags
    discard - The discard flag will enable the benefits of the TRIM command so long as one is using kernel version >=2.6.33. It does not work with ext3; using the discard flag for an ext3 root partition will result in it being mounted read-only.
    Last edited by karol (2011-10-13 19:54:22)

  • 10.10.4 update allows enabling of TRIM support for non-Apple SSDs

    Careful with Trim and Samsung SSD's. 
    https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/

    http://arstechnica.com/apple/2015/06/latest-os-x-update-allows-you-to-enable-trim-for-third-party-ss...
    This topic first appeared in the Spiceworks Community

  • LifeLine 4.0: TRIM support for SSD?

    I'm using SSDs as data volume and cache in px6-300d if this matters.

    Quote
    I read somewhere that the 6Gbs Marvell 9128 ports do not support trim on an SSD.
    Not true. TRIM has nothing to do with the SATA controller, it is dependent on the drive itself, and your operating system.
    See: http://en.wikipedia.org/wiki/TRIM

  • Support for AMD Llano APU

    I recently built a new computer to serve as a fileserver and media station. As such, it has tons of hard drives, and just barely enough graphics to play HD video. The important aspects (as far as I know) are as follows:
    Processor and graphics: AMD A4-3400 Llano APU
    OS: plain-old vanilla Arch on kernel 3.3.7-1, x86_64 (all packages up to date as well)
    Bootloader: syslinux
    Desktop: SLIM into Xmonad
    Here's the problem:
    During initial setup, I kept running into a problem where, during the boot process, as soon as it hit the point where it started loading X, my monitor would just go black and everything would be completely uninteractable. After some digging around, I figured out that I needed to add "nomodeset" to my kernel line. As such, my syslinux.cfg file has an entry as follows:
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linx
    APPEND root=/dev/disk/by-uuid/<snip> ro
    INITRD ../initramfs-linux.img nomodeset
    This works. So far, so good. However, it does have a problem -- I'm not able to correctly autodetect the resolution/aspect ratio of the monitor the computer is connected to. As such, I get rather terrible stretching and squishing whenever I hook up to, say, a 16:9 monitor. To rectify this, I tried using xrandr to manually add and set the proper resolution (as described at https://wiki.archlinux.org/index.php/Xr … solutions). However, every time I try to do this I get some errors:
    > xrandr --newmode "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 1034 1063 -hsync +vsync
    xrandr: Failed to get size of gamma for output default
    > xrandr --addmode default "1280x1024_60.00"
    xrandr: Failed to get size of gamma for output default
    > xrandr --output default --mode "1280x1024_60.00"
    xrandr: Failed to get size of gamma for output default
    xrandr: Configure crtc 0 failed
    Again, after some googling and digging I found this page (https://wiki.archlinux.org/index.php/ATI) which explains all about the drivers I should be using. My first thought was that I didn't have the right drivers installed -- wrong, I've got xf86-video-ati. I followed all the instructions on that page regarding setting up KMS properly... and one of the instructions says to make sure you remove "nomodeset" from the kernel line. Well, fine, I did that. And now I'm back where I started.
    TL;DR: I have been unable to find any instructions that will let me both a) have anything display at all (what I was getting via nomodeset) and b) properly load and take advantage of the graphics drivers (what I assume the ATI instructions would have let me do).
    Any advice, tips, or other places to look?
    Thanks,
    Phas

    Here is the long and short of it.
    This bug is in the kernel.
    The bug is not fixed in 3.4
    The bug may be fixed in 3.5 but it is not listed in the drm pull list.  Apparently they fixed the bug around 5/27 and it may or may not have made it into the final pull list.
    This bug concerns the D-sub port.  If you do not use the D-sub connection you can disable it with a kernel opiton.  This should fix the problem.
    If you are using the D-sub port then the bug should be "fixed" in the current kernel if you have no other video conections.  If you are using more then 1 video connection then you are currently screwed.  The D-sub port currently does not work with other active video ports in linux or at least not the framebuffer.  X does work over both D-sub and DVI/HDMI at the same time.
    To disable the D-sub port look in /sys/class/drm/card0 for the name of the D-sub port.  It should be card0-VGA-1.  Add the line video=VGA-1:d to the append line in syslinux.cfg.
    This is what I have been able to piece together from various bug reports/workarounds on the net, and my own experience with the bug.  I stronly suggest you add a line to the append line that either enables (:e) or disables(:d) the VGA port no matter what you do since this greatly speeds up the kernel boot time.  Mine went from 6.5 seconds to 1.5 seconds when I did this.

  • Multi Core Support for AMD 1100T

    I've read through the lists, and I suppose my answer is going to be "it depends", but as you can see from the attached two pics, it looks like Audition is only using 1 of my 6 physical cores.  Every time I look, there's really only one core doing much of anything (and it is the same core) - whether it is handling plugins, exporting/rendering, etc...  Is my answer "it depends on what you're doing"?

    I can't see the core utilisation from these graphs; all the processor information is rolled into the top one. All I can tell from this is that you are using 19% of 6 cores, which sounds about right for what you are doing.
    By and large, no software will use all of the cores - you tend to need at least one dedicated to keeping the computer itself running!

  • MSI FM2-A75IA-E53 and support for AMD (Trinity) Athlon X4 750K

    Hi I just installed everything and notice the Windows bios tool was reading 255c. came to this forum and read threads with the similar issue. someone chimed in on most stating X board only support chips at 95w and the bogus temp readouts is a safe guard. Which make sense to me as I've use hw monitor to confirm the correct temperature. So i bought this chip as it was listed as a supported chip on their specs page. This cpu runs at 100w but they are also running on bios 1.3 which this MB came stock at 1.0/1.1 . So my question if i update to 1.3 will this chip be legitimately supported with all the normal read out or do i try and return the board or the chip?  dont even know what the return policy is on open parts i've just installed everything.
    thanks

    The board's very max supported load ability is 95w TDP. Anything above will cause the board faking overheating to start throtteling which makes the board survive. The faking overheating is the 255°C reading. No bios will change that. That's at least better than the alternative as the board's vrms might burn otherwise.

  • TRIM support available in Mac OS X 10.6.8 update?

    Several Apple fansites are reporting that the recently released Mac OS X 10.6.8 update adds TRIM support for non-third party SSDs, with screenshots as proof. Since I own a MacBook Pro with SSD built in, I was quite excited about this. However, after installing the update and restarting, System Profiler still says TRIM support is not available... My questions to the Community:
    * Did anyone else have this experience? Do you have TRIM support enabled after installing 10.6.8 or not?
    * Did I miss a step somewhere? Should I enable some setting manually?
    Thanks in advance. Cheers!

    Hi,
    same same.
    SSD native on a mbp Q4 2009.
    I was excited to activate TRIM functionality with the 10.6.8 upgrade...no way...
    I heard we still have hope with the final release 10.7
    Apple, you should take care of geeks like us experiencing with SSD before all the others.
    We expect you to fix the TRIM function....
    Thanks,
    Giovanni

  • I now have TRIM support. Now what?

    Since updating to the most recent 10.6.8 Mac OS X update, my 2010 MBA now shows TRIM support for the first time.
    There has been a lot of banter about the messageboards with many people stating that Mac SSD's do not need TRIM, because the pre-existent "garbage collection" functions are all that is needed.
    I'm just wondering now that my Air has TRIM support, what has/will be improved, if anything?
    Will I perceive any short term or long term benefits?
    Moreover, is there anyting I need do to have TRIM perform it's magic? Or is the issuance of appropriate TRIM commands automatic and invisible to the user?

    Click here and request assistance.
    (78089)

Maybe you are looking for