Cr-48 Hardware
For those curious exactly how much RAM, HD, and what CPU the Cr-48 has, the chrome://system display is rather helpful. Hit the jump for details.
CPU: Intel(R) Atom(TM) CPU N455 @ 1.66GHz (source: the CPU line 
)
This is actually one of the nicer Atom chips and came out in Q2 2010. It's a 1.66 GHz chip with one core, hyperthreading, and 512kb L2 cache.
Hard drive: 16.0 GB SanDisk SSD
Source: the dmesg line contains this:
[ 1.474388] scsi 0:0:0:0: Direct-Access ATA SanDisk SSD P4 1 SSD PQ: 0 ANSI: 5 [ 1.475174] sd 0:0:0:0: [sda] 31277232 512-byte logical blocks: (16.0 GB/14.9 GiB) [ 1.475422] sd 0:0:0:0: [sda] Write Protect is off [ 1.475436] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1.475564] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
I was actually guessing it would be an 8 gig SSD. 16 gigs, for how the Cr-48 functions, seems like plenty. I can't imagine websites storing 15 gigs of data using HTML5 storage, but eh, who knows, I guess it's just future-proof.
RAM: 1886 MB
Source: meminfo line contains this:
MemTotal: 1931980 kB
Sort of odd -- I presume it's actually 2 gigs, but some percentage isn't being reported to the operating system. Anyway, about 2 gigs of RAM -- which for a netbook, isn't bad at all. With 1 gig of RAM, I suspect most tech-savvy types would have tried going out and buying an upgrade, anyway, even though the manual states the Cr-48 contains "no user-serviceable parts".
Battery: Hewlett-Packard 63 Wh Lithium Ion
Source: devkit-power line:
Device: /org/freedesktop/DeviceKit/Power/devices/battery_BAT0
native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0
vendor: Hewlett-Packard
model: Primary
serial: 00030 11/26/2010
...snip...
battery
...snip...
energy-full: 63.344 Wh
energy-full-design: 63.344 Wh
Eh, it's a battery. Seems to last long enough.
Touchpad: Synaptic
Source: touchpad line
Graphics: Intel Corporation Pineview Integrated Graphics Controller
Source: lspci line:
00:02.1 Display controller: Intel Corporation Pineview Integrated Graphics Controller
See here for a discussion re: the new chipset. It has more components on the die itself, namely the memory controller, DMI link, and graphics core, for overall "betterness", i.e. better battery life/higher performance.
December 11th, 2010 - 20:26
Cool stuff. What’s the full lspci output?
December 11th, 2010 - 20:52
Lots and lots of Intel components! I pasted it here: https://gist.github.com/737860
December 11th, 2010 - 22:06
Nice, thanks for posting this for us! I’m still waiting to see if I get a CR-48, but if I do, now I know its a great netbook. I was hoping for 4GB of storage and maybe a gig of ram, but it sounds like Google did a good job giving it the resources it will need to run for a long time. My guess is that as long as it doesn’t break down, it should last a good number of years. The only thing that might be a downside in the future is if web apps start utilizing serious graphics power, but this thing should be able to handle mos things pretty well. I had a similar configuration on an Acer Aspire One, and it ran Windows 7 really well, with flash content not even glitching. I’m guessing once Google works out the bugs and Adobe and others provide more stable plug ins, this netbook is really going to be worth its use.
December 11th, 2010 - 22:11
Yeah, I was expecting an older Atom, 1 GB of RAM, and an 8 GB SSD, so I was pleasantly surprised by the specs
I’m not sure we’ll be seeing significant discrepancies in graphics performance in the near future, since Chrome OS is designed for mere netbooks…I doubt we’ll ever get anything even remotely as powerful as a dedicated GPU powering a Chrome OS machine. The weekly-updating operating system is cool, too, so hopefully the OS will never be an out-of-date version.
February 9th, 2011 - 14:58
These seem like very good specs compared to what I was expecting based on how fast this computer has been running. It took 10 seconds to load this very simple page. Maybe it’s the network I’m on, though I have 3 out of 4 bars consistently.
February 9th, 2011 - 19:27
Eh, I’m running this blog on a 256mb virt along with a number of other ruby webservices — point being, my server could just be overloaded.