syslinux filesystem size limitation
Hello,
In yocto I find that the live image (hddimg) is generated using
syslinux (in bootimg.bbclass). But, I find there has been no check enforced to find whether the filesystem size exceeds 1 GB. The image will not boot if the hddimg size exceeds 1GB. This is due to the limitation in syslinux.
How to address this issue? Is there any other alternate solution for this? Should I file a bug report for this?
Regards
Signature · 3 lines
Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in
Quoted 9 lines · Joshua Immanuel
Hello,
In yocto I find that the live image (hddimg) is generated using
syslinux (in bootimg.bbclass). But, I find there has been no check enforced to find whether the filesystem size exceeds 1 GB. The image will not boot if the hddimg size exceeds 1GB. This is due to the limitation in syslinux.How to address this issue? Is there any other alternate solution for this? Should I file a bug report for this?
Yes, this sounds worthy of filing a bug. Bonus points for patch submissions to fix it. ;)
Scott
Signature · 3 lines
Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center
Hello Scott,
Quoted 2 lines · Scott Garman
Yes, this sounds worthy of filing a bug. Bonus points for patch submissions to fix it. ;)
I've filed the bug report for it.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2138
Will try to add patch if possible.
Regards
Signature · 3 lines
Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in
Quoted 7 lines · Joshua Immanuel
Hello,
In yocto I find that the live image (hddimg) is generated using
syslinux (in bootimg.bbclass). But, I find there has been no check enforced to find whether the filesystem size exceeds 1 GB. The image will not boot if the hddimg size exceeds 1GB. This is due to the limitation in syslinux.
Where are you getting this information?
From what I can gather, syslinux 2.xx didn't support FAT32, which limited the maximum filesystem size purely due to limitations of FAT16. Syslinux 3.xx supports FAT32. We are building syslinux 4.xx in Yocto.
I'm fairly certain I've built syslinux images larger than 1GB without an issue.
Can you provide a failure case?
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Hello Darren,
Quoted 7 lines · Darren Hart
Where are you getting this information?
From what I can gather, syslinux 2.xx didn't support FAT32, which limited the maximum filesystem size purely due to limitations of FAT16.
Syslinux 3.xx supports FAT32. We are building syslinux 4.xx in Yocto.
Quoted 5 lines
I'm fairly certain I've built syslinux images larger than 1GB without an
issue.Can you provide a failure case?
In order to answer this, I have added my comments on the bug listing
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2138
I guess it would be more appropriate there.
Regards
Signature · 3 lines
Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in
Hello,
Quoted 5 lines · Joshua Immanuel
In yocto I find that the live image (hddimg) is generated
using syslinux (in bootimg.bbclass). But, I find there has been no check enforced to find whether the filesystem size exceeds 1 GB. The image will not boot if the hddimg size exceeds 1GB. This is due to the limitation in syslinux.
For the benefit of others who arrived at this thread via search I am writing this.
Apparently, there is no 1GB limitation with syslinux. The problem was due to mkdosfs tool in poky edison branch. The complete discussions about this can be found in the (long) comments section of this bug.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2138
I would like to thank Darren for helping me in debugging this problem.
Regards
Signature · 3 lines
Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in