Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Comment Re:AI? They taught it. (Score 2) 77

If we look at the article, the computer was taught only the specific algorithms to create a jigsaw puzzle arrangement or shuffle a deck of cards. Then the program just ran the data through it to create various optimal results. It didn't have capabilities to expand the concept of the trick, for example.

Comment Re:Why? (Score 4, Interesting) 327

The Linux kernel, for instance, keeps a blacklist for this issue instead

This is true. The blacklist is contained in drivers/ata/libata-core.c for anyone who wants to take a look at it.

To find it, in that file search for: static const struct ata_blacklist_entry ata_device_blacklist []

For SSDs with (queued) TRIM problems, that list seems to contain only Crucial/Micron M500/M550. There is a lot of other devices blacklisted for various reasons. Of course they aren't blacklisted completely but just some features are disabled in them.

Submission + - GTK+ Developers Call for Help to Finish OpenGL Support

jones_supa writes: OpenGL support under GTK is getting into good shape for providing a nice, out-of-the-box experience by default on key platforms for the GTK+ 3.16 / GNOME 3.16 release in March. For a few weeks now within mainline GTK+ has been native OpenGL support and as part of that a new GtkGLArea widget for allowing OpenGL drawing within GTK applications. Since that initial work landed, there's been more GTK+ OpenGL code progressing that right now primarily benefits Linux X11 and Wayland users. While good progress is being made and improvements still ongoing to the GNOME toolkit, GNOME developers are requesting help in ensuring other GTK+ backends can benefit from this OpenGL support. If you are using or planning to use GTK+ 3 on Windows or OS X, and you know how to use OpenGL on those two platforms, please consider helping out the GTK+ developers by implementing the GdkGLContext API using WGL and AppleGL.

Comment Re: Gee thanks. (Score 1) 55

As if Google ever gets anything right. Fail after fail. Their only successes are their acquisitions (Maps, YouTube). It's a wonder how they're even still in business.

Same reason as why Microsoft is still the king of the OS market with their crusty software: for new companies the barrier of entry to the field is too high.

Comment Re:Security? (Score 1) 111

You can probably infer whether the chip is working hard or not, and possibly hear it stepping clock frequencies. Maybe if the frame rate is locked to v-sync, you could also hear a beat frequency synchronous to fps. I don't think you can find out anything more specific than those kind of things. There's a lot of power filtering going on and the chip architecture is extremely complex.

Comment Re:Anybody familiar with the manufacturing side? (Score 1) 111

Because 99.999% of users don't care enough to complain.

That would mean 1 / 100,000 users complain. I think more users care. 99.99% or even 99.9% might be a closer value to the amount of users that don't care.

Of course I'm just nitpicking and past your point, but there's a surprisingly big difference into how many 9s you slap there. :)

Comment Re:don't worry about it (Score 2, Interesting) 178

Same here. I bought two 128GB cards on eBay for $23 each. Only one showed up, and when I tested it with:

# dd if=/dev/zero of=/dev/sdc

it gives I/O error at about 8.2GB. Definitely not worth the aggravation.

No, no, don't do it that way. If you overwrite an SD card starting from the beginning, you will overwrite the Protected Area of the card. Also happens if you use the "format disk" function of an operating system on the card.

The SD Association has a special formatter which avoids this problem.

Maybe try reading the card instead of writing, to test for those cards which have missing flash. Or carefully skip the Protected Area with dd when writing.

Submission + - An Applied Investigation to Graphics Card Coil Whine (hardwarecanucks.com)

jones_supa writes: We all are aware of various chirping and whining sounds that electronics can produce. Modern graphics cards often suffer from these kind of problems in form of coil whine. But how widespread is it really? Hardware Canucks put 50 new graphics cards side-by-side to compare them solely from the perspective of subjective acoustic disturbance. NVIDIA's reference platforms tended to be quite well behaved, just like their board partners' custom designs. The same can't be said about AMD since their reference R9 290X and R9 290 should be avoided if you're at all concerned about squealing or any other odd noise a GPU can make. However the custom Radeon-branded SKUs should usually be a safe choice. While the amount and intensity of coil whine largely seems to boil down to luck of the draw, at least most board partners are quite friendly regarding their return policies concerning it.

Slashdot Top Deals

2.4 statute miles of surgical tubing at Yale U. = 1 I.V.League

Working...