[Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)

2015-05-06 Thread Kendek
Yeah, just use -v option for print number of discarded bytes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)

[Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12

2015-06-24 Thread Kendek
So, I already use the proposed (3.19.0-22-generic) kernel on Vivid Vervet, I installed it days ago. The discard mount option and the fstrim command are works now, without any problem. Please do not drop the path, but move this kernel to the stable repository. -- You received this bug

[Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12

2015-06-24 Thread Kendek
** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338706 Title: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask

[Bug 1511988] [NEW] Boot error with Syslinux (Ubuntu 15.10)

2015-10-31 Thread Kendek
Public bug reported: After I executing the following command on the Ubuntu 15.10 amd64, the Live system on the USB device does not boot with legacy BIOS: sudo syslinux -i /dev/sdXN I get this error message: SYSLINUX 6.03 EDD 20150813 Copyright (C) 1994-2014 H. Peter Anvin et al Boot error If

[Bug 1511988] Re: Boot error with Syslinux (Ubuntu 15.10)

2015-10-31 Thread Kendek
Sorry, this bug is already reported: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1507002 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511988 Title: Boot error with Syslinux (Ubuntu

[Bug 1511988] Re: Boot error with Syslinux (Ubuntu 15.10)

2015-10-31 Thread Kendek
*** This bug is a duplicate of bug 1507002 *** https://bugs.launchpad.net/bugs/1507002 ** This bug has been marked a duplicate of bug 1507002 "boot error" is back! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1507002] Re: "boot error" due to gcc v5 transition

2016-04-14 Thread Kendek
This problem is fixed in the version 6.03+dfsg-11ubuntu1, see the changelog: http://changelogs.ubuntu.com/changelogs/pool/main/s/syslinux/syslinux_6.03+dfsg-11ubuntu1/changelog The new version is working well on the Ubuntu 16.04 LTS, but the available version in the 15.10 (-8ubuntu2) is still

[Bug 1847919] Re: Adiantum cipher cannot be specified in the /etc/crypttab

2019-10-17 Thread Kendek
Since 2:2.0.3-5 you can use ‘cipher=foo\054bar’ to set cryptsetup(8)'s cipher spec string to ‘foo,bar’. ** Changed in: cryptsetup (Ubuntu) Status: New => Fix Released ** Changed in: cryptsetup (Ubuntu) Assignee: (unassigned) => Kendek (nemh) -- You received this bug notifi

[Bug 1847919] [NEW] Adiantum cipher cannot be specified in the /etc/crypttab

2019-10-13 Thread Kendek
Public bug reported: In the /etc/crypttab file the fourth, options field separates each option with a comma. The xchacha12,aes-adiantum-plain64 xchacha20,aes-adiantum-plain64 valid ciphers cannot be specified in the options field, because the comma is misinterpreted. The error message is: >