Julian Calaby wrote on 12/29/2015 12:43 PM:
Hi,
On Tue, Dec 29, 2015 at 10:30 PM, U.Mutlu wrote:
After this nigtmare-ish experience I would suggest the debian maintainers
to trash the default jessie kernel 3.16 and replace it with the above
4.2 kernel; otherwise unexperienced users will wonder
Hi,
On Tue, Dec 29, 2015 at 10:30 PM, U.Mutlu wrote:
> After this nigtmare-ish experience I would suggest the debian maintainers
> to trash the default jessie kernel 3.16 and replace it with the above
> 4.2 kernel; otherwise unexperienced users will wonder why their new SSD etc.
> isn't working i
Solved:
By installing a the latest kernel and headers from Debian backports solved the
problem:
apt-get -t jessie-backports install linux-image-amd64 linux-headers-amd64
Info about backports configuration:
http://backports.debian.org/Instructions/
# uname -a
Linux panther 4.2.0-0.bpo.1-amd64
Hi,
I have got 2 different submodels of the SSD Samsung 850 Evo 500 GB.
The first one has DPOFUA=0, the second one has DPOFUA=1 (see below).
That with DPOFUA=0 works fine, but the other with DPOFUA=1 doesn't work
after mounting; it reports errors and switches to read-only mount.
It seems Linux ha
4 matches
Mail list logo