2015-04-13, 21:18
(2015-04-13, 20:09)Byrdi Wrote: But after attemping to use fsck/dev/sda (6 and 7) as stated on the wiki
It said not found:
Code:sh; fsck/dev/sda6: not found
Since then I have even tried to do all sda 1 through 16 still without any luck
Is there any way to fix this without doing a fresh install?
And how do I prevent it in the first place (heard something about shutdown/suspend settings but I didn't quite get it)
you're missing the space between fsck and /dev/sda[#].
the issue is caused most often by an improper shutdown, it just wants you to run a filesystem check to ensure things are good before booting.
(2015-04-13, 20:13)mpednault Wrote: Alright, this may have already been asked but...
The overview in the instructions on the wiki list removing the screw (disabling write protect) and then putting it in developer mode. The Matt lists those steps in opposite order. I'm getting my Chromebox today and am trying to be sure I know and understand the procedures before I get started.
doesn't make a bit of difference. I've edited the OP to be in sync with the wiki (so, remove the screw first).
(2015-04-13, 20:28)hdmkv Wrote: From wiki:
Quote:System-->Settings-->Videos-->Acceleration: Enable HQ Scalers for scalings above:20%What does 20% for scalings do? Re: VC-1, with latest firmware/OE build, should one still deselect VC-1 VAAPI for 1080i (29.97) VC-1 content?
System-->Settings-->Videos-->Acceleration: Use VC-1 VAAPI:Selected (de-select if you have interlaced VC-1 content)
System-->Settings-->Videos-->Acceleration: Prefer VAAPI render method:Selected
it means that it will use HQ (CPU intensive) scaling algorithms when going from say 720p to 1080p, but not when say scaling a 1080p file based on video calibration / overscan compensation.
I'm not aware that interlaced VC-1 is fixed, so yes, deselect it still. This may change with Isengard, in which case I'll update the wiki.