WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Regression in kernel 5.4 leads to inaccessible nvme storage  (Read 338 times)

Offline hoehermann

  • WikiUser
  • *
  • Posts: 6
Regression in kernel 5.4 leads to inaccessible nvme storage
« on: March 17, 2020, 09:11:09 AM »
Hi

In the past weeks, I grew fond of TCL. However, the current kernel seems to suffer regression https://bugzilla.kernel.org/show_bug.cgi?id=205679 and I cannot access the nvme storage in modern systems. Can TCL switch to a more recent kernel or would I compile the kernel myself?

Kind Regards

Online curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10253
Re: Regression in kernel 5.4 leads to inaccessible nvme storage
« Reply #1 on: March 17, 2020, 11:25:30 AM »
You can build a custom kernel fairly easily. The patch at http://lists.infradead.org/pipermail/linux-nvme/2019-December/028243.html seems to only affect a builtin file, so if you build our 5.4.3 version just with that patch, you don't have to build the modules, ours will work. Then you'd replace our vmlinuz with yours.

Some specific vendor's drives being standard incompliant is not really a big enough issue for TC to update the kernel mid-release, though. Especially as it's nvme, not very many TC users with such hw I think.
The only barriers that can stop you are the ones you create yourself.

Offline hoehermann

  • WikiUser
  • *
  • Posts: 6
Re: Regression in kernel 5.4 leads to inaccessible nvme storage
« Reply #2 on: March 18, 2020, 04:45:01 AM »
You can build a custom kernel fairly easily. The patch at http://lists.infradead.org/pipermail/linux-nvme/2019-December/028243.html seems to only affect a builtin file, so if you build our 5.4.3 version just with that patch, you don't have to build the modules, ours will work.

Good idea. After reading http://wiki.tinycorelinux.net/wiki:custom_kernel I managed to integrate the patch and build http://tinycorelinux.net/11.x/x86/release/src/kernel/linux-5.4.3-patched.txz. I somehow managed to end up with the i686 binary although the host I compiled on is amd64. Working fine with the official modules.