Re: Running Linux on Samsung's ARM Chromebook
On 19/02/14 12:00, toby@dryft.net wrote:
Hi, Samsung have had an ARM-based laptop for a while, sold as a Chromebook. (ie. with an Android-like Linux kernel and the Chrome browser as the whole OS)
The little ARM cpu means the laptop doesn't need much power and can run for quite a while, despite being lightweight and cheap with a small battery.
I was wondering how it'd go running a full version of Linux; just running a bunch of terminal emulators more of the time, and maybe Chromium from time to time.
I've heard of people managing to get Ubuntu or other linux variants installed, but I wondered if anyone here has done it? Was it worth the trouble?
I've run openSUSE on mine as described here: http://en.opensuse.org/HCL:ARMChromebook There's an image you can put on an SD card, then with the Chomebook in developer mode[1], you boot off the SD card (have to hit CTRL-U at each boot to do this). This means you can have a play without trashing or otherwise repartitioning the SSD. Last time I tried this, *something* didn't work (might have been not waking from screensaver? I forget exactly), and I never got around to figuring out what it was. This may well have since been fixed. I ultimately ended up just running my Chromebook in regular ChromeOS mode, as I'm really only using the thing occasionally as a a slightly glorified web browser, and I got sick of it whining loudly at me on every boot about the possible doom associated with being in developer mode. HTH, Tim [1] http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devi...
On 19 February 2014 23:56, Tim Serong <tim@wirejunkie.com> wrote:
On 19/02/14 12:00, toby@dryft.net wrote:
Hi, Samsung have had an ARM-based laptop for a while, sold as a Chromebook. (ie. with an Android-like Linux kernel and the Chrome browser as the whole OS)
The little ARM cpu means the laptop doesn't need much power and can run for quite a while, despite being lightweight and cheap with a small battery.
I was wondering how it'd go running a full version of Linux; just running a bunch of terminal emulators more of the time, and maybe Chromium from time to time.
I've heard of people managing to get Ubuntu or other linux variants installed, but I wondered if anyone here has done it? Was it worth the trouble?
I've run openSUSE on mine as described here:
http://en.opensuse.org/HCL:ARMChromebook
There's an image you can put on an SD card, then with the Chomebook in developer mode[1], you boot off the SD card (have to hit CTRL-U at each boot to do this). This means you can have a play without trashing or otherwise repartitioning the SSD.
Last time I tried this, *something* didn't work (might have been not waking from screensaver? I forget exactly), and I never got around to figuring out what it was. This may well have since been fixed.
I ultimately ended up just running my Chromebook in regular ChromeOS mode, as I'm really only using the thing occasionally as a a slightly glorified web browser, and I got sick of it whining loudly at me on every boot about the possible doom associated with being in developer mode.
Hi Tim, Thanks -- your first-hand experiences were exactly what I was after. I think you've confirmed others' suggestions that the chromebook is going to be more hassle than it's worth to run Linux upon, at least at the moment. -Toby
Toby Corkindale <toby@dryft.net> writes:
Thanks -- your first-hand experiences were exactly what I was after. I think you've confirmed others' suggestions that the chromebook is going to be more hassle than it's worth to run Linux upon, at least at the moment.
ARM devices are always a hassle, because ARM vendors still think every device should be a unique and special snowflake. :-/ Just look at how long devicetree has taken.
Toby Corkindale <toby@dryft.net> writes:
Thanks -- your first-hand experiences were exactly what I was after. I think you've confirmed others' suggestions that the chromebook is going to be more hassle than it's worth to run Linux upon, at least at the moment.
*sigh* The epilogue to this thread goes: I bought a second-hand 11"Intel ultrabook; same kind of size, weight and battery run time as the chromebook. And because it was second-hand, it cost as much (used) as a brand-new chromebook does. It booted up fine once, then never again. No idea why, but the process of taking it home seems to have completely killed the blasted thing. Around that time, I discovered it was already missing some screws from the case, making me think it was a known-dodgy unit that someone had tried fixing and then just on-sold. Going to see if I can get a warranty claim honoured on it, but I feel doubtful about that happening. So now I have no money and no new laptop. :( Kinda wishing I'd either bought a new chromebook (despite hassle of getting Linux onto it) or just not been a tight-arse in buying a cheap used laptop! :/ T
Replying to myself once more.. Still stinging from losing a few hundred dollars on the dud ultrabook, I bought a $199 new C720 chromebook -- but one of the Haswell-based ones, not ARM. After entering into developer mode on the chromebook, one can enable a legacy BIOS boot mode, at which point it's trivial to install a regular Linux distro via bootable USB stick. I've been using this for a bit, with Kubuntu. The C720 only has 2GB of RAM, but that's easily enough to run a few terminal windows, gcc-avr and chrome, which is about all I wanted it for. Suspect this was definitely a better choice than going for an ARM-based chromebook, in terms of easy of installation/maintenance. ChromeOS runs Linux under the hood, so there's decent Linux support for everything on the book-- although of course, you do need either a bleeding-edge kernel version, or be willing to patch an old version yourself. (This will rapidly become less of a problem as time goes by) On 21 February 2014 18:33, Toby Corkindale <toby@dryft.net> wrote:
Toby Corkindale <toby@dryft.net> writes:
Thanks -- your first-hand experiences were exactly what I was after. I think you've confirmed others' suggestions that the chromebook is going to be more hassle than it's worth to run Linux upon, at least at the moment.
*sigh*
The epilogue to this thread goes:
I bought a second-hand 11"Intel ultrabook; same kind of size, weight and battery run time as the chromebook. And because it was second-hand, it cost as much (used) as a brand-new chromebook does. It booted up fine once, then never again. No idea why, but the process of taking it home seems to have completely killed the blasted thing. Around that time, I discovered it was already missing some screws from the case, making me think it was a known-dodgy unit that someone had tried fixing and then just on-sold. Going to see if I can get a warranty claim honoured on it, but I feel doubtful about that happening.
So now I have no money and no new laptop. :( Kinda wishing I'd either bought a new chromebook (despite hassle of getting Linux onto it) or just not been a tight-arse in buying a cheap used laptop! :/
T
-- Turning and turning in the widening gyre The falcon cannot hear the falconer Things fall apart; the center cannot hold Mere anarchy is loosed upon the world
Toby Corkindale <toby@dryft.net> writes:
Still stinging from losing a few hundred dollars on the dud ultrabook, I bought a $199 new C720 chromebook -- but one of the Haswell-based ones, not ARM. After entering into developer mode on the chromebook, one can enable a legacy BIOS boot mode, at which point it's trivial to install a regular Linux distro via bootable USB stick.
I had a look at these, and all the datasheets and reviews say SSD, but I don't believe them -- an eMMC would be more likely, and would still be marketed as "solid state". Can you confirm the onboard storage really is an SSD? Is it soldered to the mainboard? (I'm getting a C720 while I wait for a EFI64 Bay Trail transformer, but not for a week, and I'm curious because my TF101's eMMC is really getting on my nerves.)
On 7 March 2014 17:53, Trent W. Buck <trentbuck@gmail.com> wrote:
Toby Corkindale <toby@dryft.net> writes:
Still stinging from losing a few hundred dollars on the dud ultrabook, I bought a $199 new C720 chromebook -- but one of the Haswell-based ones, not ARM. After entering into developer mode on the chromebook, one can enable a legacy BIOS boot mode, at which point it's trivial to install a regular Linux distro via bootable USB stick.
I had a look at these, and all the datasheets and reviews say SSD, but I don't believe them -- an eMMC would be more likely, and would still be marketed as "solid state".
Can you confirm the onboard storage really is an SSD? Is it soldered to the mainboard?
I haven't actually opened the case to check, but here's a blog post from someone else who has: http://www.androidcentral.com/how-upgrade-ssd-your-acer-c720-chromebook Sounds like it's quite do-able. The RAM, however, is soldered on, I gather.
Toby Corkindale wrote:
On 7 March 2014 17:53, Trent W. Buck <trentbuck@gmail.com> wrote:
Toby Corkindale <toby@dryft.net> writes:
Still stinging from losing a few hundred dollars on the dud ultrabook, I bought a $199 new C720 chromebook -- but one of the Haswell-based ones, not ARM. After entering into developer mode on the chromebook, one can enable a legacy BIOS boot mode, at which point it's trivial to install a regular Linux distro via bootable USB stick.
I had a look at these, and all the datasheets and reviews say SSD, but I don't believe them -- an eMMC would be more likely, and would still be marketed as "solid state".
Can you confirm the onboard storage really is an SSD? Is it soldered to the mainboard?
I haven't actually opened the case to check, but here's a blog post from someone else who has: http://www.androidcentral.com/how-upgrade-ssd-your-acer-c720-chromebook
Sounds like it's quite do-able.
The RAM, however, is soldered on, I gather.
Cheers. Did you find the 4GB unit anywhere? Wikipedia's chromebook page says they exist, but Australian retailers don't mention them.
On 7 March 2014 17:59, Trent W. Buck <trentbuck@gmail.com> wrote:
Toby Corkindale wrote:
On 7 March 2014 17:53, Trent W. Buck <trentbuck@gmail.com> wrote:
Toby Corkindale <toby@dryft.net> writes:
Still stinging from losing a few hundred dollars on the dud ultrabook, I bought a $199 new C720 chromebook -- but one of the Haswell-based ones, not ARM. After entering into developer mode on the chromebook, one can enable a legacy BIOS boot mode, at which point it's trivial to install a regular Linux distro via bootable USB stick.
I had a look at these, and all the datasheets and reviews say SSD, but I don't believe them -- an eMMC would be more likely, and would still be marketed as "solid state".
Can you confirm the onboard storage really is an SSD? Is it soldered to the mainboard?
I haven't actually opened the case to check, but here's a blog post from someone else who has: http://www.androidcentral.com/how-upgrade-ssd-your-acer-c720-chromebook
Sounds like it's quite do-able.
The RAM, however, is soldered on, I gather.
Cheers. Did you find the 4GB unit anywhere? Wikipedia's chromebook page says they exist, but Australian retailers don't mention them.
I didn't see any. I bought mine from Amazon, so maybe try there for a wider range?
On 8 Mar 2014, at 16:34, Toby Corkindale <toby@dryft.net> wrote:
On 7 March 2014 17:59, Trent W. Buck <trentbuck@gmail.com> wrote:
Toby Corkindale wrote:
On 7 March 2014 17:53, Trent W. Buck <trentbuck@gmail.com> wrote:
Toby Corkindale <toby@dryft.net> writes:
Still stinging from losing a few hundred dollars on the dud ultrabook, I bought a $199 new C720 chromebook -- but one of the Haswell-based ones, not ARM. After entering into developer mode on the chromebook, one can enable a legacy BIOS boot mode, at which point it's trivial to install a regular Linux distro via bootable USB stick.
Is there a terminal emulator available in ChromeOS? For web and terminal, maybe the default installation would work just as well
hannah commodore <hannah@tinfoilhat.net> writes:
Is there a terminal emulator available in ChromeOS? For web and terminal, maybe the default installation would work just as well
Yes. When I was fiddling with mine, Ctrl+Alt+T in chrome (after logging in) took me to a tty tab, where "shell" gave me bash and "sudo -i" gave me root. I could also do Ctrl+Alt+F2 (where F2 is labelled →) to get to a bare tty, but I *think* that was after I enabled "developer mode". OTOH, somebody told me that the dirty hack SSH client plugin for chromeos, doesn't support keys! Anyways, I reflashed mine with Debian Jessie within 24h as the Goddess intended, not bothering to keep a copy of chromeos. I won't regret that until I try to get bt working and realize I blew away my only copy of the firmware blob... :-) Most interesting thing so far: the Caps Lock position is *actually* the penguin key, a.k.a. Super. There's no xkb option to swap it with Ctrl, but XKBOPTIONS=altwin:ctrl_win in /etc/default/keyboard makes it another control key. I've clearly been spoilt by the IPS display on my TF101, because on the C720 the blacks are grey, and the viewing angle is bad enough that reading a book sideways, one of my eyes is always outside the angle, so the text "shimmers" unless I close an eye. I had assumed all displays were better than that by now, but I guess not. Far less noticable if you are one of those black-on-white weirdos. The SD card sticks out of the machine, so I can't just leave it in. Didn't realize that was still a thing, either. It has active cooling (which I knew from the pictures), but it's weird to have it slowly baking my thighs -- I've gotten used to having the bottom half of the clamshell being nothing but battery. And as usual, I forgot to account for the padding in my bag, so it was a quarter-inch too big and I needed to buy *another* laptop bag. Bleh. On the plus side, *I can install things!* Like a new kernel! and I have an SSD instead of a dying eMMC that koopses when I try to delete files! Bash starts in under 2s again! In a week or two Stockholm syndrome will kick in and I'll be fine :-P
Some quick recommendations.. Add the couple of lines of touchpad config to xorg.d that people mention here and there -- it really improved the touchpad handling on mine. Enable zram to help with the fairly small amount of available memory, and to reduce thrashing swap on ssd if you have too many browser windows open.. On 11 March 2014 11:56, Trent W. Buck <trentbuck@gmail.com> wrote:
hannah commodore <hannah@tinfoilhat.net> writes:
Is there a terminal emulator available in ChromeOS? For web and terminal, maybe the default installation would work just as well
Yes. When I was fiddling with mine, Ctrl+Alt+T in chrome (after logging in) took me to a tty tab, where "shell" gave me bash and "sudo -i" gave me root.
I could also do Ctrl+Alt+F2 (where F2 is labelled →) to get to a bare tty, but I *think* that was after I enabled "developer mode".
OTOH, somebody told me that the dirty hack SSH client plugin for chromeos, doesn't support keys!
Anyways, I reflashed mine with Debian Jessie within 24h as the Goddess intended, not bothering to keep a copy of chromeos. I won't regret that until I try to get bt working and realize I blew away my only copy of the firmware blob... :-)
Most interesting thing so far: the Caps Lock position is *actually* the penguin key, a.k.a. Super. There's no xkb option to swap it with Ctrl, but XKBOPTIONS=altwin:ctrl_win in /etc/default/keyboard makes it another control key.
I've clearly been spoilt by the IPS display on my TF101, because on the C720 the blacks are grey, and the viewing angle is bad enough that reading a book sideways, one of my eyes is always outside the angle, so the text "shimmers" unless I close an eye. I had assumed all displays were better than that by now, but I guess not. Far less noticable if you are one of those black-on-white weirdos.
The SD card sticks out of the machine, so I can't just leave it in. Didn't realize that was still a thing, either.
It has active cooling (which I knew from the pictures), but it's weird to have it slowly baking my thighs -- I've gotten used to having the bottom half of the clamshell being nothing but battery.
And as usual, I forgot to account for the padding in my bag, so it was a quarter-inch too big and I needed to buy *another* laptop bag. Bleh.
On the plus side, *I can install things!* Like a new kernel! and I have an SSD instead of a dying eMMC that koopses when I try to delete files! Bash starts in under 2s again! In a week or two Stockholm syndrome will kick in and I'll be fine :-P
_______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
-- Turning and turning in the widening gyre The falcon cannot hear the falconer Things fall apart; the center cannot hold Mere anarchy is loosed upon the world
Toby Corkindale wrote:
Some quick recommendations.. Add the couple of lines of touchpad config to xorg.d that people mention here and there -- it really improved the touchpad handling on mine.
I wasn't going to bother trying to get the touchpad working. From my reading, that'll happen automatically when I get 3.14. Last time I fiddled with a touchpad, I grabbed the example synaptics config from https://wiki.debian.org/SynapticsTouchpad And of course "syndaemon -Rdtk" in .xsession to avoid palm-clicks while typing.
Enable zram to help with the fairly small amount of available memory, and to reduce thrashing swap on ssd if you have too many browser windows open..
Good point re zram, I've recently added that to my kiosk farm, hadn't thought about it for personal use. No swap, because swap is for sissies. My 16GB is one big btrfs -- not even a wussy MBR. :-) Now I just need to work out how to use quota groups... After that my main jobs are to fix pm suspend, and go through powertop's suggestions. Biggest unsolved annoyance so far, is epdfview is gone due to lack of upstream maintenance, and evince-gtk doesn't remember its geometry -- I might have to go back to running a WM!
PS: the setup docs mention mem=1536m to get it to boot, presumably because the kernel isn't properly detecting the memory available to it. When I tried mem=2g, it dumped core. When I tried mem=1920m (2G - 128M) it worked fine. I *think* this matters, because "free -m" reports more memory that way. I can't work out how much RAM the GPU is *expected* to steal. It ships with a "Celeron 2955U", which is listed https://en.wikipedia.org/wiki/Chromebook#Acer_C720 => https://en.wikipedia.org/wiki/Celeron_2955U#.22Haswell-ULT.22_.28SiP.2C_22_n... => https://en.wikipedia.org/wiki/Intel_HD_and_Iris_Graphics#Haswell Which STILL doesn't say. OTOH, I've noticed a weird artefact where sometimes -- especially just after booting? -- the screen's blank areas aren't cleared properly. e.g. doing dmesg then ^L in xterm, the dmesg output is still there except at the very top and bottom. Or unmapping the xterm, and the xterm is still there until I make ratpoison popup a dialog in the corner. I tried running compton as well (with default settings), but that just made the whole display stop responding until I hit ^C. Same behaviour with typing my passphrase blind into ssh-askpass-fullscreen, though ssh-askpass-gnome and ssh-askpass (xlib) worked. WEIRD. *Pretty* sure that all started before I added mem=1920m, too.
On 11 March 2014 21:11, Trent W. Buck <trentbuck@gmail.com> wrote:
PS: the setup docs mention mem=1536m to get it to boot, presumably because the kernel isn't properly detecting the memory available to it.
When I tried mem=2g, it dumped core. When I tried mem=1920m (2G - 128M) it worked fine.
I *think* this matters, because "free -m" reports more memory that way.
Oh. Hmm. I've just been using pretty much the defaults that Kubuntu 14.04 has and it's been fine. I didn't need to put the mem= line to boot it up, and it's been reporting around 1875M of memory? It did boot up *faster* once I added some recommended bit about i915 modesetting. I do note that something added "add_efi_memmap" to the boot parameters though.
OTOH, I've noticed a weird artefact where sometimes -- especially just after booting? -- the screen's blank areas aren't cleared properly. e.g. doing dmesg then ^L in xterm, the dmesg output is still there except at the very top and bottom. Or unmapping the xterm, and the xterm is still there until I make ratpoison popup a dialog in the corner.
Hmm, nope, never seen that on mine. Toby
Toby Corkindale <toby@dryft.net> writes:
OTOH, I've noticed a weird artefact where sometimes -- especially just after booting? -- the screen's blank areas aren't cleared properly. e.g. doing dmesg then ^L in xterm, the dmesg output is still there except at the very top and bottom. Or unmapping the xterm, and the xterm is still there until I make ratpoison popup a dialog in the corner.
Hmm, nope, never seen that on mine.
I think I know why. I *think* I'm only seeing this behaviour after a kexec reboot, *not* after a cold power off/power on. That means the issue is probably related to the GPU not being reset properly. Aha! When this occurs, I get this in dmesg (other lines elided): [ 3.1] [drm] Initialized drm 1.1.0 20060810 [ 3.1] [drm] Memory usable by graphics device = 2048M [ 3.1] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 3.1] [drm] Driver supports precise vblank timestamp query. [ 3.2] fbcon: inteldrmfb (fb0) is primary device [ 4.8] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [ 4.9] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 4.9] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 [13.8] [drm] stuck on render ring [13.8] [drm] GPU crash dump saved to /sys/class/drm/card0/error [13.8] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [13.8] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [13.8] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [13.8] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. That'd be why I couldn't find that dmesg this morning -- it was a cold boot.
On 11 March 2014 19:49, Trent W. Buck <trentbuck@gmail.com> wrote:
Toby Corkindale wrote:
Some quick recommendations.. Add the couple of lines of touchpad config to xorg.d that people mention here and there -- it really improved the touchpad handling on mine.
I wasn't going to bother trying to get the touchpad working. From my reading, that'll happen automatically when I get 3.14.
Oh, no, I assumed you already had it working.. It's just that there's a couple of params that fixed the min/max sensitivity for me which made it more pleasant to use. [snip]
After that my main jobs are to fix pm suspend, and go through powertop's suggestions.
I haven't tried powertop myself, but the battery life seems pretty good as standard so far. Really good, in fact. The suspend was a nice surprise, too -- ie. it "just worked" out of the box for me, and resume is near-instant (sub-second). I'm not sure why these things aren't working for you; possibly it's just that I'm on a 3.13 kernel that already had a couple of extra patches applied for Haswell support? I think the Arch Linux wiki had better-organised info for tweaks, if you're looking; but I didn't end up needing too many, which was pleasant. tjc
Toby Corkindale writes:
On 11 March 2014 19:49, Trent W. Buck <trentbuck@gmail.com> wrote:
After that my main jobs are to fix pm suspend, and go through powertop's suggestions.
I haven't tried powertop myself, but the battery life seems pretty good as standard so far. Really good, in fact.
It's better than I expected, but probably par for a haswell ult. I'm used to tegra2, though :-)
I'm not sure why these things aren't working for you; possibly it's just that I'm on a 3.13 kernel that already had a couple of extra patches applied for Haswell support?
3.13 from debian experimental, here.
I think the Arch Linux wiki had better-organised info for tweaks, if you're looking; but I didn't end up needing too many, which was pleasant.
That's what I was working from, yeah.
Toby Corkindale <toby@dryft.net> writes:
After that my main jobs are to fix pm suspend, and go through powertop's suggestions.
I haven't tried powertop myself, but the battery life seems pretty good as standard so far.
FYI most of powertop's suggestions were false positives or not settable on this hardware. I set min_power on both SATA buses, though -- they default to max_performance. # apt-get install sysfsutils (or just use rc.local) # /etc/sysfs.conf - Configuration file for setting sysfs attributes. class/backlight/intel_backlight/brightness = 128 class/scsi_host/host0/link_power_management_policy = min_power class/scsi_host/host1/link_power_management_policy = min_power PS: its suggestions are easier to read from powertop --html=foo.html. Re power, I've had it on from 10AM to 7PM at work and it's has 20% left. Not as good as the TF101, but acceptable. (For comparison, it's at 56%, but 1) its screen has been off all day; and 2) it's an older battery.)
The suspend was a nice surprise, too -- ie. it "just worked" out of the box for me, and resume is near-instant (sub-second).
Still isn't working for me. After trying all the things arch suggests, I can get it to suspend *once* per boot. On resume, it's failing to rebind the EHCI bus to the EHCI driver. (Subsequent suspend requests abort because it can't unbind it when it's not bound. Can't remember what happens if I allow that.) The main symptom of not unbinding EHCI is that after resume dmesg spews complaints about it at top speed -- IIRC not very noticable in X, but destroying the system trying to render all the lines if you're in fbcon. AFAICT nothing is actually *on* the EHCI bus, so I tried blacklisting the EHCI driver in the ramdisk and rootfs, which prevented it loading, but then doing suspend just causes it to immediately resume. Since it's about the only thing we're doing different, I think my suspend problems are touchpad-related—I reckon because I have no driver for it, it's not suspending the touchpad properly. (The actual facts—EHCI bus is empty and EHCI bind fails—don't agree with that theory, but facts aren't really important when I'm bitching.) Toby, does your USB hub match mine? lsusb -t ==> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 4: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
On Tue, 11 Mar 2014, "Trent W. Buck" <trentbuck@gmail.com> wrote:
My 16GB is one big btrfs -- not even a wussy MBR. :-) Now I just need to work out how to use quota groups...
The last time I asked on the BTRFS list (not long ago) they suggested that I not use quota groups because there are already enough known bugs and providing evidence of it failing won't help the developers. Quota groups aren't good enough to use and using them won't help the developers. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
On 11 March 2014 10:15, hannah commodore <hannah@tinfoilhat.net> wrote:
On 8 Mar 2014, at 16:34, Toby Corkindale <toby@dryft.net> wrote:
On 7 March 2014 17:59, Trent W. Buck <trentbuck@gmail.com> wrote:
Toby Corkindale wrote:
On 7 March 2014 17:53, Trent W. Buck <trentbuck@gmail.com> wrote:
Toby Corkindale <toby@dryft.net> writes:
Still stinging from losing a few hundred dollars on the dud ultrabook, I bought a $199 new C720 chromebook -- but one of the Haswell-based ones, not ARM. After entering into developer mode on the chromebook, one can enable a legacy BIOS boot mode, at which point it's trivial to install a regular Linux distro via bootable USB stick.
Is there a terminal emulator available in ChromeOS? For web and terminal, maybe the default installation would work just as well
Yes, there are some terminal emulators available with ssh. I reckon the default install probably will be fine for some people. I wanted to be able to run gcc-avr to compile things for Arduino's and similar microcontrollers though, so I needed a proper Linux install.
Toby Corkindale <toby@dryft.net> writes:
I reckon the default install probably will be fine for some people. I wanted to be able to run gcc-avr to compile things for Arduino's and similar microcontrollers though, so I needed a proper Linux install.
If you only do that occasionally you might prefer a chroot inside cros. I ran across a repo for that on github (off the arch C720 page, IIRC). I wasn't interested so I didn't take a copy.
participants (6)
-
hannah commodore -
Russell Coker -
Tim Serong -
Toby Corkindale -
Trent W. Buck -
trentbuck＠gmail.com