-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
opk update issues slowdowns #6
Comments
Hey, @Ninoh-FOX... passing this on from Discord. Not sure if it's related or not... podulatorToday at 8:07 AM To disable this behaviour, you can turn lazy initialisation off when you create the file system, by specifying the extended options lazy_itable_init and lazy_journal_init, and setting them to 0: mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 DEVICE |
Ok, let's update the next build to turn off lazy initialization. people will have to wait longer for that first boot, but they won't see slowdowns. |
Then, you are saiding that we need format the ext4 in the first boot? |
When we do the format, we need to change the command to be this: mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 |
okay so i just flashed v1.5 base again on a 32gb card for internal but did not do no update and picodrive is working fine and no slowdows so its the opk file that is doing something
I will stick to v1.5 for now
The text was updated successfully, but these errors were encountered: