Quote:
Originally Posted by arrrghhh
I don't know if putting this on a dedicated partition will resolve the SoD or reboot issue TBH - it certainly should be better overall compared to looped filesystems tho, I would imagine.
Also, I don't think this would require Linux - there's tools for Windows that allow you to partition the SD in all sorts of file systems. It's just easier with Linux because a) the tools are built into the system and b) Windows won't be able to read those newly created partitions anyways, without other 3rd party tools  .
Not to take any wind out of your sails, but I wouldn't consider that Linux hacking skills  . Certainly got some geek cred, and it's not easy to do without any prior knowledge - but far from what I would consider hacking . Neopeek builds have required this for quite some time... (a separate ext2 partition that is)
hyc said that running on dedicated partitions did localize his corruption - thus not having to blast out his data.img (or in this case partition) as frequently - that doesn't mean that it eliminated the issue.
In theory it should be a little quicker as well - it might not be significant enough to even be noticeable to the end user.
If there's some demand for it, ndno (or me) can certainly make a how-to do this. The rootfs is already configured to handle it, so AFAIK you just have to setup the partitions and drop the data in - I'm not really sure how much repointing is involved TBH. |
Yeah, I didn't mean to say it will fix the restarts/SOD. Just thought it will may have better data integrity using a native ext2 partition than a data.img mounted on a FAT32 partition; I'm just speculating...
Yeah, it's not really "hacking" skills. I called it hacking because that's what I'm doing, hacking away at the scripts and stuff until it works.
arrrghhh, if you find a good Windows tool that can create Linux EXT2 partitions (EXT4 for GBX0A), let's us know. I didn't know such tools existed so that's why I said a Linux distro is required. I guess I should do some more googling; I just tend to like Linux more so I didn't bother searching.
I didn't realize that neopeek was already doing this; I have never used neopeek. So I guess neopeek is more complicated to set up than the haret builds we have here
Again, I'm just doing this as an experiment for learning purposes so unless there are a lot of PROs for switching to native EXT2 partitions on a SD card, people should just stick to the way haret builds are set up in this forum. Besides, the NAND project is very close (if not yet) to completing and it uses native EXT2 partitions on a faster NAND interface so people should wait for that