You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I solved the ldlinux.c32 error I got this error. I wanted to confirm a few things. The kernel path in the config file is /vmlinuz. Should I change it to my kernel path which is /boot/vmlinuz-6.8.0-52-generic
When I do this the error occurs of cannot find linux data and without this there is an error of no kernel at /vmlinuz.
Does this have to do something with aufs and overlayfs? Because my kernel supports overlayfs as I saw in the config of my kernel but there was no name of aufs in there. And I searched the previous issues to find that kernel above 5.0 doesn't support aufs. So how should I change my scripts to support overlayfs and not aufs. I tried making ISO from linux-live-overlay repo but that was a failure as well. On that I encountered the error of not finding the kernel... @Tomas-M help needed kindly go through my issue once....
The text was updated successfully, but these errors were encountered:
After I solved the ldlinux.c32 error I got this error. I wanted to confirm a few things. The kernel path in the config file is /vmlinuz. Should I change it to my kernel path which is /boot/vmlinuz-6.8.0-52-generic
When I do this the error occurs of cannot find linux data and without this there is an error of no kernel at /vmlinuz.
Does this have to do something with aufs and overlayfs? Because my kernel supports overlayfs as I saw in the config of my kernel but there was no name of aufs in there. And I searched the previous issues to find that kernel above 5.0 doesn't support aufs. So how should I change my scripts to support overlayfs and not aufs. I tried making ISO from linux-live-overlay repo but that was a failure as well. On that I encountered the error of not finding the kernel...
@Tomas-M help needed kindly go through my issue once....
The text was updated successfully, but these errors were encountered: