Comment 13 for bug 1618550
Revision history for this message
| Arto Makkonen (arto-o-makkonen) wrote | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
If you are referring to the '"resume-trace" debugging procedure for finding buggy drivers', I'm still evaluating if this is beyond my skills.
In particular I don't understand this paragraph:
"Caveat Emptor: Using the following debug suggestions will radically change the values in your RTC chip, so much so that your file system will think it has been eons since the last fsck. You can avoid a long fsck delay by using 'tune2fs'. For example, 'tune2fs -i 0 /dev/sda1' disables fsck on boot. But first you'll want to use 'tune2fs -l <partition>' to find your current settings - look at the "Check interval" setting."
Do I need to disable something in boot before or after the resume-tracing proceduce? What is the consequence of file system thinking it has been eons since the last fsck?
Sicne I don't wish to mess my computer, it would be great if someone could provide fool proof instructions for this part, including suggested terminal commands in the right order.