M.2 not recognised during deploying stage
-
@will said in M.2 not recognised during deploying stage:
Can you confirm that does this special kernel “bzImage-5.10.19-Lexar_M.2” include NIC driver for Realtek 8125B and Intel I225-V?
Looks like Realtek 8125B is supported since Linux kernel 5.9.x and we also added the firmware blobs needed. As well the IGC kernel driver (discussed here) is also included in bzImage-5.10.19-Lexar_M.2. So I would say both should work. Let is know if it doesn’t.
-
@Will Please let us know if this patched kernel fixed the issue.
-
@sebastian-roth Hi, Sebastian I can confirm this special kernel fixed the Lexar M.2 non detecting issue. Thank you.
-
@Will Thanks for the update. Just found that the patch was actually accepted upstream in kernel 5.10.23. As we will update to newer kernel version as we go this will be in the official FOG kernels as well. No extra patching needed.
-
@sebastian-roth i have the same issue when registering the system having the M.2 SSD. How can i upgrade the kernel 5.10.23. can you please help me to register and deploy the windows 10
FYI - I using the latest version of the fog itself 1.5.9.63 and kernel version is ( 5.10.19)
-
@dinesh said in M.2 not recognised during deploying stage:
How can i upgrade the kernel 5.10.23
The devs have not posted that public yet.
FWIW I see the official linux kernels are now at 5.10.28.
-
@Dinesh Right, we have not released a newer kernel version yet but you can still download and use the kernel including the patch until we release a new kernel.
-
@sebastian-roth Can you send me the steps to install the patch(kernels/bzImage-5.10.19-Lexar_M.2)
-
@dinesh said in M.2 not recognised during deploying stage:
Can you send me the steps to install the patch(kernels/bzImage-5.10.19-Lexar_M.2)
sudo -i cd /var/www/fog/service/ipxe/ wget https://fogproject.org/kernels/bzImage-5.10.19-Lexar_M.2 chown www-data:www-data bzImage-5.10.19-Lexar_M.2If you use a RedHat/CentOS Linux then you need to use apache instead of www-data with the last command above.
Now you have the kernel available and just need to set this as default kernel (FOG Configuration -> FOG Settings -> TFTP Server -> TFTP PXE KERNEL change from
bzImagetobzImage-5.10.19-Lexar_M.2)Note that down so you can switch back to
bzImagewhen the next kernel is officially released and you want to use the default again. -
@sebastian-roth Is kernels/bzImage-5.10.19-Lexar_M.2 supports both HDD’s and M.2 variants?
-
@Dinesh said:
Is kernels/bzImage-5.10.19-Lexar_M.2 supports both HDD’s and M.2 variants?
Yes, it’s the standard kernel we use fog HDD, SSD and M.2. I simply added the patch to support the “Lexar NM700 256GB M.2 SSD” drive mentioned in this topic. Nothing more or less.
-
@sebastian-roth But few systems having the Samsung 512 M.2 and 1000 Gb Toshiba HDD having in few more systems. is this Kernel support for that variant?
-
@dinesh This patch only added additional support, it didn’t remove anything that was working previously.
If you encounter other devices that don’t work you can mention them here of course so we can investigate.
-
@dinesh said in M.2 not recognised during deploying stage:
But few systems having the Samsung 512 M.2 and 1000 Gb Toshiba HDD having in few more systems. is this Kernel support for that variant?
I have no idea. As I said, this kernel is very close to the standard 5.10.19 kernel we officially provide - except that it has a patch included that will make the “Lexar NM700 256GB M.2 SSD” work that had an issue on the plain 5.10.19 kernel.
I am not going to answer any more questions about what disk is supported or not. Just try it out or leave it.
-
@sebastian-roth Thanks for your valuable reply…
-
@dinesh Can I ask what exactly you were hoping for here?
Not only do you give very little information, you also seem to assume that we know everything the Linux kernel supports. We don’t. We are not involved with developing the Linux kernel, we only use it as part of FOS.
There are hundreds (if not thousands) different kinds of M.2 Samsung SSDs, nevermind new ones coming out constantly.
There are thousands (if not tens of thousands) different kinds of Toshba Hard Drives, with new ones still coming out.
There are tons of different ways to connect them. They could be behind software raid, hardware raid, connected to some PCIE board, basic SATA connector, SAS connector, U.2 connector, etc
It’s unreasonable to assume we can just know what will work and what will not.
Just try, it either works or not.
-
@quazz Too add on a bit,
If you find something that doesn’t work, let us know. We will most likely request some more technical information so that we can do the research to find out if there’s a way to add it, or a patch we can use to incorporate, or we will find there is nothing we can do currently.
The point here is, you’re absolutely correct: We don’t know what will or will not work. We have some good google fu and only a few developers and testers working to get information so we can be as hardware agnostic as possible. But we aren’t all knowing. We know a new version was released and do our best (granted I’ve been slacking lately I suppose) to keep the kernels updated and including anything that maybe missing that we can add.
If it works, YAY, if it doesn’t, and we say try this kernel, if it works YAY, if it doesn’t let us know. We’ll ask for information and probably even walk through what we need and how to get it. Then we’ll try to find out information and give back whether or not we can do anything, and if we were able to do it, to test out the new thing. If it works, YAY, if it doesn’t rinse and repeat.
