Possible Intel Ssd 25x-m Trim Solution For Mac

Possible Intel Ssd 25x-m Trim Solution For Mac Rating: 3,7/5 5023 votes

Version: 3.0.28 Patch: 00 Date: 2018-11-28 - Changes: - New version, new man. Fixes, enhancements. ARM fix, odroid 1 cpu speeds not showing correctly.

Ansible start fixes. Fringe Battery failures, see Pinebook. Removed null data message 'old system' since that's not always the case. Added support for 1 CPU speeds in systems with 1 CPU. Added isnumeric test for sudo version tests, that was tripping errors in rare cases.

Fine tuned terminal size setting to check that is int to correct the Ansible problem. ARM Pinebook fixes, battery, cpu. This also fixes corner cases where the battery charge state is missing but it is a systme battery. Enhancments: 1. Added more disk ID matches/vendors. Thanks LinuxLite Hardware database!! UKUI, ukwm, ukui-panel added to desktop data.

Possible Intel Ssd 25x-m Trim Solution For Macbook Pro

Possible intel ssd 25x-m trim solution for mac pro

Added PopOS to system base. Ansible/Chef user noted that inxi believes that it is running in IRC when started by Ansible / Chef (not sure about Chef but assuming it's the same). Added flag -tty flag to force inxi to believe it's running in shell no matter what starts it. Note that this fix is not confirmed because the person didn't confirm the fix.

Added Ubuntu disco to ubuntuid. - Harald Hope - Thu, 29 Nov 2018 21:12:14 -0800 Version: 3.0.27 Patch: 00 Date: 2018-10-14 - Changes: - New version, new man. Fixes, stitches, and returns!! As a fix (3), failure to handle spaces in mount source names. More of a fix than a bug, since it was an old issue #63. OSX errors, BSD errors, but not really inxi errors or bugs, more weird data tripping null data or unreadable file errors, but I'll call those bugs since they look like bugs to end users.

See Fixes for more. See Fix 4, this is sort of a bug, inxi failed to return expected values on success/failure.

One of the documented config items, COLSMAXNODISPLAY had not been implemented internally. This is now corrected. Apple OSX was returning errors, those were fixed. Finally handled ancient issue #63, support now there for spaces in remote source name.

This means that both spaces in source block name, and mount point name, are in theory both handled now. This was also to fix an osx issue #164 despite the fact that technically I do not support osx beyond fixing errors, but since in this case the issue was a long standing one, I fixed it for everything. Big fix, I'd completely left undone proper unix type error number returns in inxi, oops. Thanks Unit193 for noticing that and prompting me to fix it. Now inxi returns integer success/error numbers as expected. OSX xml based version info broke, of course, naturally it would, so I added in an osx fallback where if no distro version detected, use fallback unix method, which is what all the other unices use.

Along with space in source name, fixed mapped handling a bit more too for partitions. Added cifs remote file system to disk size used blacklist, and iso9660. Not sure how I'd missed those for so long. OpenBSD vmstat in 6.3 changed the column order for avm/fre, and changed to a, sigh, human readable default format, in M, so to handle this for all bsds, I had to make a dynamic column detection for avm and fre, and use those after, and also i had to add in a M detection, if found,.1024 and strip out M, sigh. OpenBSD, another alternate ordering/syntax issue, the dmesg.boot data for disks does not always use the same order in comma separated list, saw user case where the first item after: was the MB size, not the second. Made detection dynamic.

Due to Android case, found types where no cpu speed data was found, no max speed at least, which tripped an error due to null data for ARM, this is now handled, now cpu speed min/max read permissions in /sys are checked first before trying to read, and default failures are better handled. On man page, added in clarification of the moving of Memory: item from Info: line to ram Memory: line, explaining when it appears where. I am ambivalent about removing the item from -I, I may revert that change, I find it non-intuitive to move the Memory report around. Enhancements: 1. Added display manager Ly, plus Ly version number. Thanks NamedKitten, this closes issues #166 #165 #162 2.

Improved documentation a bit to avoid ambiguity re how to get colors in output. That handles issue #161, thanks fugo for the nudge to improve the documentation. First inxi on Android tests, using termux, which has a debian based apt type installer, got inxi running on at least two devices, including pixel2, but discovered that apparently as of android 5, /sys is now locked up in terms of wildcard reads, but further analysis is required, but as of now, inxi works in termux, but fails to get any Device data for A, G, or N. Thus it also fails to match IF to Device, so none of the IP data shows up. The latter will probably be fixed since Android has ip and ifconfig already, or termux does, but so far I found no way to get device data for ARM in Android 5.x and greater (checked on android 7 and 9 in real phones).

More disk vendors!! Thanks linuxlite / linux hardware database for offering an apparently never ending list of obscure and not so obscure disk vendors and products. While I was unable to get confirmation or documentation on file names for tce repo files, I guessed that localmirrors would be used, but this may be any random text file in /opt at all, no extensions, I'd have to test to confirm or deny possible values. To handle more complex debugger failures, added -debug-no-proc, -debug-no-exit, to skip or enable completion where proc or sys debugger is hanging.

Changed vendor in A, G, and N to -x, not -xxx, this data seems much more useful and reliable than I'd first expected when I made the feature, the -xxx was more an indication of my lack of trust in the method and source, but so far it seems pretty good, so I bumped it up to an -x option. Note that also, it's quite useful to know the vendor of, say, your network or graphics card, not just the actual device internal data, which is all inxi has ever shown previously. Small change, if no partition type data is found, dev, remote, mapped, default now says 'source:' instead of 'dev:' which makes more sense. Note that df calls that column 'source', so I decided to go with their language for the default not found case.

Also changed mapped to say mapped. This was part of a bit of a refactor of the partition type logic, enhanced by adding mapped to existing types, and moved the entire type detection block into the main data generator, and out of the data line constructor.

Optimizations: 1. Tested, and dumped, List::Util first as a possible way to speed up grep searches of arrays, where the goal is just to see if something is in an array. My expectation was that first, returning the first found instance of the search term, would of course be faster since it will always exit the search loop was met with the sad fact that first is about 2 to 4 times SLOWER than grep native builtin. I tested this fairly carefully, and used NYTProf optimizer tool and the results were totally consistent, first was always much slower than grep, no matter what size the array is. I assume this means the core C programming that makes grep is simply much better than the File::Util module programming that makes first. Removed first and now know that nothing will be faster than grep so no need to look there for speed improvements. The moral of the story: just because something should in theory be faster, does sadly not mean it will be faster, for there are bigger things at work, skill of the programmers who made the logic, how perl handles external vs internal tools, and so on.

As an aside, this forms a fairly consistent pattern where I've found Perl by itself to be faster than modules in many cases, that is, it's faster to write the code out than to use a module in many cases that I have tested, so I will always test such ideas and dump every one that is in fact slower than native Perl builtins. - Harald Hope - Sun, 14 Oct 2018 15:24:34 -0700 Version: 3.0.26 Patch: 00 Date: 2018-09-28 - Changes: - New version, new man. If you consider failure to identify a mounted yet hidden partition a bug, then that bug is fixed, but I consider that as more of a fix than a bug.

Added more device pattern ID for odroid C1 and C2, these are now pretty well supported. Inxi failed to handle a certain type of hidden partition, so far only seen with udiskctl mounted TimeShift partitions, but this may be a more general udisk issue, but so far not enough information. The fix is to use the lsblk data to build up missing partitions, so this fix is for non legacy Linux systems only.

The fix works pretty well, but it's hard to know until we get a lot more real world data, but given so far I've received only one issue report on it, I suspect this is not a common situation, but you never know, it would never have shown up in datasets unless I had looked specifically for it, so it may be more common than I think. Cleaned up and simplified new -admin -p and -d logic. Refactored deb822 apt handling due to utter randomness of syntax allowed. Enhancements: 1. For debugging, renamed all user debugger switches to have prefix -debug.

These options are to help debug debugger failures, and so far have been tested and solved the failures, so I'm adding them all to the main man and help menu, thus raising them to the level of supported tools. These were enormously helpful in solving proc or sys debugger hangs.debug-proc.debug-proc-print.debug-no-sys.debug-sys.debug-sys-print 2. Added findmnt output to debugger, that may be useful in the future. Also added df -kTPa to also catch hidden partitions in debugger.

Added in another user level debugger, triggered with -debug-test-1 flag. This will do whatever operation is needed at the time for that user. Some issues can only be resolved by the user on their machine.

More disk vendors and matches!!! Thanks linuxlite/linux hardware database!

- - Harald Hope - Fri, 28 Sep 2018 13:47:03 -0700 Version: 3.0.25 Patch: 00 Date: 2018-09-24 - Changes: - New version, new man. Huge set of changes.

There was a missing main::isint test that in some instances triggered error. This is corrected. More of a fix, but legacy devices were not matching NIC to IF because the /sys path was not a link as it is now. I made a separate function to handle that match test so it could be more readily worked with.

Arch/Manjaro presented yet another Xorg.wrapper path, this time /usr/lib. That to me is a bug, but since if it's not handled in inxi, it makes it look like inxi has a server: -G bug, I worked around it. This creates the bug when you do not use the actual true path of Xorg where Xorg.wrapper complains and will not show -version data. Why move this? Why use that wrapper thing? I don't know, makes no sense to me.

More MIPS data, thanks manjaro ARM people. This made MIPS much better, though it will certainly need more work.

Better ARM support, added in devicetree strings, which helps pad out the Devices IDs, albeit with very little data, but at least the devices are detected. Thanks Manjaro ARM people there again. Removed Upstart init test for arm/mips/sparc devices. This test made MIPS device totally puke and die, killed networking, so since very few upstart running systems will be arm/mips devices, I decided there better safe than sorry. Found another uptime syntax case, MIPS as root does not have the users item.

Many tweaks to SOC data generators, will catch more categories, but the lists will never be done since each device can be, and often is, random re the syntax. SOC types are now filtered through a function to create consistent device type strings for the per device tool to use to assign each to its proper @device array. USB networking failed to test usb type for 'network', which led to failed ids on some device strings. For pciconf/FreeBSD, cleaned up device class strings to get rid of 0x and trailing subsubclass values, this converts it into the same hex 4 item string that is used by GNU/Linux/lspci so I can apply consistent rules to all pci types, no matter what the generator source is, lspci, pcidump, pciconf, and eventually pcictl if I can get netbsd running. Fixed internal -dbg counts for various features, and updated docs for that.

Fixed ARM / MIPS missing data messages, they were redundant. Ongoing, moving excessive source comments to inxi-values.txt and inxi-data.txt. Added unity-system-compositor as mir detection, who knew? I guess that was its production application name all along?

Enhancements: 1. Added basic support for OpenIndiana/Solaris/SunOS as a bsd type. Just enough to make errors not happen. Future proofed unix/bsd detections just to avoid the unset $bsdtype of non BSD unix. Added S6 init system to init tool.

Added OpenBSD pcidump to new DeviceData feature. Includes now message on Device-x: lines if not root. Fully refactored the old pci stuff to DeviceData package/class, due to adding so many types to that, it made sense to make it a single class. Did the same to USBData, because of lsusb, usbdevs, and /sys usb, made sense to integrate the data grabber into one package/class 7. Added speed: item to USB:, it shows in Mb/s or Gb/s 8. Added Odroid C1/C2 handling, which is one big reason I opted to refactor the devices data logic into DeviceData. Added ash shell, not sure if that detection will work, but if it does, it will show.

As part of the overall DeviceData refactor, I moved all per type data into dedicated arrays, like @devicegraphics, @deviceaudio, @devicenetwork, etc, which lets me totally dump all the per device item tests, and just check the arrays, which have already been tested for on the construction of the primary DeviceData set. Moved all per type detections into DeviceData so that is now one complete logic block, and the per type data generators don't need to know about any of that logic at all anymore. Added sway, swaybar, way-cooler as window managers, info items. Not 100% positive about the -version, their docs weren't very consistent, but I think the guess should be right if their docs weren't incorrect. Added vendor: item to network, not sure why I kept that off when I added vendor: to audio and graphics. It made sense at the time, but not now, so now -GNA all have vendor: if detected. More device vendors!!

The list never ends. Thanks linuxlite/linux hardware database, somehow you have users that manage to use every obscure usb/ssd/hdd known to humanity.

Big update to -admin, now has the following: A: partitions: shows 'raw size: ' of partition, this lets users see the amount of file system overhead, along with the available size as usual. B: partitions: show percent of raw in size: C: partitions: show if root, block size of partition file system. Uses blockdev -getbsz D: partition: swap: show swappiness and vfs cache pressure, with (default) or (default default value) added. This apparently can help debugging some kernel issues etc.

Whatever, I'll take someone's word for that. E: Disks: show block size: logical: physical: 15. New option and configuration item: -partition-sort / PARTITIONSORT This lets users change default mount point sort order to any available ordering in the partition item. Man page and help menu show options. Going along with the MIPS fixes, added basic support for OpenWRT, which uses an immensely stripped down busybox (no ps aux, for example), maybe because it only runs as root user/ not sure, anyway, took many fixes. Added Void Linux xbps repos to Repos section. Changed usb: 1.1 to rev: 1.1 because for linux, we have the USB revision number, like 3.1.

Note that this is going to be wrong for BSDs, but that's fine. Changed slightly the output of Memory item, now it follows the following rules: A: if -m/-memory is triggered ( -v4, or -m) Memory line always shows in Memory: item, which makes sense.

Note that -m overrides all other options of where Memory minireport could be located. B: if -tm is triggered, and -I is not triggered, Memory shows in in -tm C: if -I is triggered, and -m is not triggered, Memory: shows in -I line. D: no change in short form inxi no arg output, Memory is there. - Harald Hope - Mon, 24 Sep 2018 15:58:00 -0700 Version: 3.0.24 Patch: 00 Date: 2018-09-10 - Changes: - New version, new man page.

Bug fix, enhancements, fixes. Big bug found on certain systems, they use non system memory memory arrays, inxi failed to anticipate that situation, and would exit with error when run as root for -m when it hit those array types. These arrays did not have modules listed, so the module array was undefined, which caused the failure. Thanks Manjaro anonymous debugger dataset 'loki' for finding this failure. This is literally the first dataset I've seen that had this issue, but who knows how many other system boards will show something like that as well. Related to bug 1, do not show the max module size item if not system memory and size is less than 10 MiB. Assuming there that it's one of these odd boards.

Enhancements: 1. For bug 1, extended Memory: report to include array type if not system memory.

That instance had Video Memory, Flash Memory, and Cache Memory arrays along with the regular System Memory array. Now shows: use: Video Memory for example if not System Memory to make it clear what is going on. Added basic Parrot system base, but for some inexplicable reason, Parrot changed the /etc/debianversion file to show 'stable' instead of the release number.

Who knows, it would be so much easier if people making these derived distros would be consistent and not change things for no good reason. Added a few more pattern matches to existing vendors for disks. As usual, thanks linuxlite/linux hardware database for the endless lists of disk data.

Added internal dmidecode debugger switches, that makes it much easier to inject test dmidecode data from text files using debugger switches internally. Added -Cxx item, which will run if root and -C are used, now grabs L1 and L3 cache data from dmidecode and shows it. I didn't realize that data was there, not sure how I'd missed it all these years, I guess pinxi really is much easier to work on!

This only runs if user has dmidecode permissions from root or sudo. Brought cpu architectures up to date, new intel, new amd. Note there's a slight confusion about what is coffee lake and what is kaby lake.

- Harald Hope - Mon, 10 Sep 2018 15:00:17 -0700 Version: 3.0.23 Patch: 00 Date: 2018-09-07 - Changes: - New version, man page. Fixes, enhancements, changes. AntiX forums, for testing -C -admin, suggestions, always helpful. Added switch to set @psgui, I forgot case where info block was only thing that used psgui (Nitrux kde nomad latte case).

This program runs as a service in the background. Description of IMS Telephone On-Hold Player Telephone on hold messages and music player software for Windows. Features real time mixing of messages and music, message date-time scheduling, automatic online internet updates and much more. Download ims telephone on-hold player for macbook air.

This led to no info: data if other psgui switches not activated. Now each block that can use it activates it. To clarify issue #161 added help/man explanation on how to get colors in cases where you want to preserve colors for piped or redirected output. LMDE 3.0 released, slightly different system base handling, so refactored to add Debian version, see enhancement 2.

Tested on some old vm instances, improved old system Debian system base id, but it's empirical, distro by distro, there is no rule I can use to automatically do it, sadly. 'Motherboard' sensors field name added, a few small tweaks to sensors. This was in response to issue #159, which also raised a problem I was not really aware of, user generated sensor config files, that can have totally random field names. Longer term solution, start getting data from sys to pad out lm-sensors data, or to handle cases where no lm-sensors installed. Fixed kwin11 and kwinwayland compositor print names, I'd left out the , which made it look strange, like there were two compositors or something. Fixed latte-dock ID, I thought the program name when running was latte, not latte-dock.

Inxi checks for both now. Thanks Nitrux for exposing that in vm test.

Posted on