Closed andyandroid closed 8 years ago
Hi Andy,
Does it help if you do
sudo modprobe gennvm
and then try again to initialize the target?
Hi Matias
I have the same result.
andy@andy-MS-7758:~$ sudo modprobe gennvm [sudo] andy 的密码: andy@andy-MS-7758:~$ sudo modprobe null_blk use_lightnvm=1 gb=4 andy@andy-MS-7758:~$ dmesg |grep nvm [ 229.331590] nvm: registered nullb0 [1/1/256/4096/1/1] [ 229.331603] nvm: err (-22) on device initialization [ 229.331674] nvm: registered nullb1 [1/1/256/4096/1/1] [ 229.331682] nvm: err (-22) on device initialization
Hmm, there might be missing a patch for lightnvm that was fixed in the 4.6 cycle.
Could you try installing the latest kernel for ubuntu and see if the problem persist?
http://www.yourownlinux.com/2016/05/how-to-install-linux-kernel-4-6-rc6-in-linux.html
Matias
No err after installing latest kernel, Thanks a lot.
Thanks for testing it.
When Instantiate with the null_blk driver, I hit err (-22), I am not sure it is a err of lnvm,
When Instantiate media manager and target with the cmd, the cmd fail and the dmesg show device has no media manager registered
Below are basic Linux and kernel info lnvm version: 1.0