• Uncategorized

    Some Basic Chromeos Troubleshooting (Under the hood)

    Chromeos is one of the easier operating systems to use. It’s matured a lot over the years and there are now some great troubleshooting options under the hood. One thing I hate doing is mashing buttons without at least some semblance of proof of a hypothesis about what a problem is. In other words, I like to start troubleshooting with logs. For this let’s use Ctrl+Alt+F2 to bring up a virtual terminal. From there: A standard place for logs since Unix System V has been /var/log. In there are files such as libcros_log, which is where chromium dumps logs from services. /var/log/messages and subdirectories of /var/log/window_manager/chromeos-wm.LATEST and /home/chronos/user/log/chromoeos-wm.LATEST /home/chronos/user/log/chrome_log which…

  • ChromeOS,  Ubuntu,  Unix

    Make Changes to the Chromium rootfs

    By default, the Chromium OS rootfs is read-only. If you boot the system in developer mode, you will be able to disable rootfs verification and modify existing files or write new files into the file system. Before you do this, note that your file system will no longer be verifiable (won’t checksum properly) and you’ll end up needing to restore a recovery image in order to get back to normal mode. So this might be a bit dangerous if you’re not using the device for something like regression analysis (why I needed to do this). To make the file system writeable, first fire up a command prompt via crosh, by using Control-Alt-T…